Merge branch 'master' into stablelm

Author: Bond099

.github/pull_request_template.md

@@ -0,0 +1,19 @@
+## Description of the change
+<!--- Describe your changes in detail. -->
+
+
+## Reference
+<!--- Link to the reference implementation, research paper, and GitHub issue. -->
+
+## Colab Notebook
+<!-- If adding any new API, attach a colab showing the high-level usage. If adding a model, please also include numerics verification against a reference implementation.-->
+
+## Checklist
+<!--- Please make sure all checkboxes are ticked before submitting this PR for review. -->
+
+- [ ] I have added all the necessary unit tests for my change.
+- [ ] I have verified that my change does not break existing code and works with all backends (TensorFlow, JAX, and PyTorch).
+- [ ] My PR is based on the latest changes of the main branch (if unsure, rebase the code).
+- [ ] I have followed the Keras Hub [Model contribution guidelines](https://github.com/keras-team/keras-hub/blob/master/CONTRIBUTING_MODELS.md) in making these changes.
+- [ ] I have followed the Keras Hub [API design guidelines](https://github.com/keras-team/keras-hub/blob/master/API_DESIGN_GUIDE.md) in making these changes.
+- [ ] I have signed the [Contributor License Agreement](https://cla.developers.google.com/about).

.kokoro/github/ubuntu/gpu/build.sh

@@ -16,15 +16,16 @@ fi
 set -x
 cd "${KOKORO_ROOT}/"
 
-PYTHON_BINARY="/usr/bin/python3.9"
+PYTHON_BINARY="/usr/bin/python3.10"
 
 "${PYTHON_BINARY}" -m venv venv
 source venv/bin/activate
 # Check the python version
 python --version
 python3 --version
 
-export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:"
+# setting the LD_LIBRARY_PATH manually is causing segmentation fault
+# export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:"
 # Check cuda
 nvidia-smi
 nvcc --version
@@ -56,8 +57,8 @@ pip install huggingface_hub
 if [ "${RUN_XLARGE:-0}" == "1" ]
 then
    pytest keras_hub --check_gpu --run_large --run_extra_large \
-      --cov=keras-hub
+      --cov=keras_hub
 else
    pytest keras_hub --check_gpu --run_large \
-      --cov=keras-hub
+      --cov=keras_hub
 fi

.kokoro/github/ubuntu/gpu/jax/continuous.cfg

@@ -30,5 +30,5 @@ before_action {
   }
 }
 
-# Set timeout to 60 mins from default 180 mins
-timeout_mins: 60
+# Set timeout lower from default 180 mins
+timeout_mins: 120

.kokoro/github/ubuntu/gpu/jax/presubmit.cfg

@@ -30,5 +30,5 @@ before_action {
   }
 }
 
-# Set timeout to 60 mins from default 180 mins
-timeout_mins: 60
+# Set timeout lower from default 180 mins
+timeout_mins: 120

.kokoro/github/ubuntu/gpu/tensorflow/continuous.cfg

@@ -30,5 +30,5 @@ before_action {
   }
 }
 
-# Set timeout to 60 mins from default 180 mins
-timeout_mins: 60
+# Set timeout lower from default 180 mins
+timeout_mins: 120

.kokoro/github/ubuntu/gpu/tensorflow/presubmit.cfg

@@ -30,5 +30,5 @@ before_action {
   }
 }
 
-# Set timeout to 60 mins from default 180 mins
-timeout_mins: 60
+# Set timeout lower from default 180 mins
+timeout_mins: 120

.kokoro/github/ubuntu/gpu/torch/continuous.cfg

@@ -30,5 +30,5 @@ before_action {
   }
 }
 
-# Set timeout to 60 mins from default 180 mins
-timeout_mins: 60
+# Set timeout to 120 mins from default 180 mins
+timeout_mins: 120

.kokoro/github/ubuntu/gpu/torch/presubmit.cfg

@@ -30,5 +30,5 @@ before_action {
   }
 }
 
-# Set timeout to 60 mins from default 180 mins
-timeout_mins: 60
+# Set timeout lower from default 180 mins
+timeout_mins: 120

CONTRIBUTING.md

@@ -9,7 +9,7 @@ development.
 Before contributing code, please review our [Style Guide](STYLE_GUIDE.md) and
 [API Design Guide](API_DESIGN_GUIDE.md).
 
-Our [Roadmap](ROADMAP.md) contains an overview of the project goals and our
+Our [Roadmap](https://github.com/keras-team/keras-hub/issues/1836) contains an overview of the project goals and our
 current focus areas.
 
 We follow
@@ -20,10 +20,10 @@ We follow
 The fastest way to contribute it to find open issues that need an assignee. We
 maintain two lists of github tags for contributors:
 
- - [good first issue](https://github.com/keras-team/keras-hub/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22):
-   a list of small, well defined issues for newcomers to the project.
- - [contributions welcome](https://github.com/keras-team/keras-hub/issues?q=is%3Aissue+is%3Aopen+label%3A%22contributions+welcome%22):
-   a larger list of issues that may range in complexity.
+- [good first issue](https://github.com/keras-team/keras-hub/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22):
+  a list of small, well defined issues for newcomers to the project.
+- [contributions welcome](https://github.com/keras-team/keras-hub/issues?q=is%3Aissue+is%3Aopen+label%3A%22contributions+welcome%22):
+  a larger list of issues that may range in complexity.
 
 If you would like propose a new symbol or feature, please first review our
 design guide and roadmap linked above, and open an issue to discuss. If you have
@@ -69,7 +69,7 @@ The agreement can be found at
 
 ### Step 5. Code review
 
-CI tests will automatically be run directly on your pull request.  Their
+CI tests will automatically be run directly on your pull request. Their
 status will be reported back via GitHub actions.
 
 There may be several rounds of comments and code changes before the pull
@@ -97,7 +97,7 @@ recommend using `conda` to set up a base environment, and `pip` to install
 python packages from PyPI. The exact method will depend on your OS.
 
 **Note**: Be careful not to use mix pre-packaged tensorflow and jax libraries in
-`conda` with PyPI packages from `pip`. We recommend pulling *all* KerasHub
+`conda` with PyPI packages from `pip`. We recommend pulling _all_ KerasHub
 dependencies via `pip` as described below.
 
 ### Linux (recommended)
@@ -226,4 +226,11 @@ git add .
 git commit -m "<message>" # This will not get logged as a duplicate commit.
 ```
 
+In case you want to run the above manually on all files, you can do the
+following:
+
+```
+pre-commit run --all-files
+```
+
 KerasHub uses [Ruff](https://docs.astral.sh/ruff/) to format the code.

RELEASE_PROCESS.md

@@ -48,7 +48,7 @@ Use the following steps to create an `X.Y.0` release.
    of the package. Development releases will have version numbers like
    `X.Y.0.dev0`, and critically will never be installed by default by `pip`.
 
-   On the relase branch, check the version in `src/version_utils.py`. If the
+   On the relase branch, check the version in `src/version.py`. If the
    current version is not `X.Y.0.dev0`, make a PR following [this template](https://github.com/keras-team/keras-hub/pull/1638)
    to update the our version number fo look like `X.Y.0.dev0`. This PR should
    base off our new release branch instead of the master branch. You can use the
@@ -164,7 +164,7 @@ to push certain fixes out to our users.
    of the package. Development releases will have version numbers like
    `X.Y.Z.dev0`, and critically will never be installed by default by `pip`.
 
-   On the relase branch, check the version in `src/version_utils.py`. If the
+   On the relase branch, check the version in `src/version.py`. If the
    current version is not `X.Y.Z.dev0`, make a PR following [this template](https://github.com/keras-team/keras-hub/pull/1638)
    to update the our version number fo look like `X.Y.Z.dev0`. This PR should
    base off our new release branch instead of the master branch. You can use the