-
Updated
Jul 25, 2021 - JavaScript
object-storage
Here are 217 public repositories matching this topic...
-
Updated
Jul 25, 2021 - Go
-
Updated
Jul 24, 2021 - Go
Currently lakeFS register openapi handlers and handle all specific routes.
In case of a call to /api/v1/test, the unknown path under the API prefix, the mux will serve the request by the UI handler and return a valid HTML (UI) page.
The expected behaviour is to return a non-2xx status code with JSON error - prefered the internal error format, so the developer will handle an error and not fai
-
Updated
Jul 23, 2021 - JavaScript
-
Updated
Jul 24, 2021 - Java
-
Updated
Jul 19, 2021 - Python
Better link to ICS
-
Updated
Jul 21, 2021 - Go
-
Updated
Jul 23, 2021 - JavaScript
-
Updated
Nov 12, 2019 - Go
-
Updated
Aug 7, 2020 - Go
-
Updated
Oct 30, 2016
This is a feature request.
Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers and Access-Control-Allow-Credentials header is required to satisfy https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin.
-
Updated
Mar 9, 2021 - Go
-
Updated
Mar 19, 2019 - Go
-
Updated
Sep 24, 2020 - Go
-
Updated
Jul 2, 2021 - Java
-
Updated
Jul 30, 2018 - Go
-
Updated
Jul 25, 2021 - Go
-
Updated
May 16, 2021 - Shell
Right now the extension function returns the second part of the filename after splitting by ..
Instead the last part should be returned so that the extension for the file cat.meme.jpg is returned as jpg and not as meme.
-
Updated
Mar 24, 2021 - Go
-
Updated
Dec 16, 2019 - Python
-
Updated
Aug 6, 2020 - JavaScript
-
Updated
Mar 22, 2021 - Haskell
Improve this page
Add a description, image, and links to the object-storage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the object-storage topic, visit your repo's landing page and select "manage topics."
Best I can tell, all executables produce 0 as a Linux exit code, regardless how wrongly they were invoked. That's a problem, e.g. when attempting to run the gateway as a systemd.service.
Specific use case:
storj-gateway.servicerunsgateway_xxx_yyy --config-dir does-not-exist. Systemd happily reports that everything is fine -- which of course it is not, but it cannot tell unless the exit co