- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 175 for raising (0.19 sec)
-
docs/en/docs/tutorial/handling-errors.md
The benefit of raising an exception over `return`ing a value will be more evident in the section about Dependencies and Security. In this example, when the client requests an item by an ID that doesn't exist, raise an exception with a status code of `404`:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-with-yield.md
### Always `raise` in Dependencies with `yield` and `except` If you catch an exception in a dependency with `yield`, unless you are raising another `HTTPException` or similar, you should re-raise the original exception.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Feb 24 23:06:37 GMT 2024 - 14.1K bytes - Viewed (0) -
RELEASE.md
* Fixes vulnerabilities arising from incomplete validation in MKL requantization ([CVE-2021-37665](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37665)) * Fixes an undefined behavior arising from reference binding to nullptr in `RaggedTensorToVariant` ([CVE-2021-37666](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37666)) * Fixes an undefined behavior arising from reference binding to nullptr in
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Mon Apr 29 19:17:57 GMT 2024 - 727.7K bytes - Viewed (8) -
docs/en/docs/release-notes.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri May 03 23:25:42 GMT 2024 - 388.1K bytes - Viewed (1) -
CREDITS
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ================================================================ aead.dev/mem https://aead.dev/mem
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 26 06:31:35 GMT 2024 - 1.6M bytes - Viewed (0) -
licenses/cel.dev/expr/LICENSE
negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 08 17:05:56 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/LICENSE
negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all
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) -
licenses/sigs.k8s.io/yaml/goyaml.v2/LICENSE
negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 19:53:28 GMT 2023 - 11.1K bytes - Viewed (0) -
LICENSE
negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Jan 23 11:07:23 GMT 2024 - 23.1K bytes - Viewed (0) -
licenses/github.com/felixge/httpsnoop/LICENSE.txt
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Dec 15 21:30:37 GMT 2023 - 1.1K bytes - Viewed (0)