- Sort Score
- Result 10 results
- Languages All
Results 51 - 60 of 407 for comment (6.28 sec)
-
licenses/cloud.google.com/go/longrunning/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Nov 01 23:31:22 GMT 2022 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/auth/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 30 13:56:46 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/gnostic-models/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Jul 24 18:16:35 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Jul 17 20:25:52 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jul 26 01:07:39 GMT 2023 - 11.1K bytes - Viewed (0) -
docs/en/docs/how-to/sql-databases-peewee.md
If you want to check how Peewee would break your app if used without modification, go the `sql_app/database.py` file and comment the line: ```Python # db._state = PeeweeConnectionState() ``` And in the file `sql_app/main.py` file, comment the body of the `async` dependency `reset_db_state()` and replace it with a `pass`: ```Python async def reset_db_state():
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 16 13:23:25 GMT 2024 - 23.6K bytes - Viewed (1) -
LICENSES/vendor/github.com/google/s2a-go/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Wed Oct 25 20:31:21 GMT 2023 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/go-logr/stdr/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Sun Sep 18 01:47:24 GMT 2022 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/distribution/reference/LICENSE
boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Fri Sep 01 01:53:40 GMT 2023 - 11.2K bytes - Viewed (0) -
licenses/github.com/go-logr/stdr/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Jul 17 20:25:52 GMT 2023 - 11.1K bytes - Viewed (0)