forked from dandi/dandi-archive
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT: Staging -> Production #19
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ATM we do not have a single DEBUG level log statement, but I hope that logging would be enriched. Adding such control would also allow to make log less talkative if so desired by setting it to WARNING level. But also would simplify addition and use of new log statements
…rformed While troubleshooting - dandi/dandi-cli#1488 I would like to know if any of those tasks was ran at all. That is conditioned on correct condition to happen first, so it is valuable to add explicit debug level log entry if condition was not met
Co-authored-by: Yaroslav Halchenko <[email protected]>
These instructions are for serving the app using a development server. For building the app, there is the `yarn run build` command.
Co-authored-by: Mike VanDenburgh <[email protected]>
Co-authored-by: Mike VanDenburgh <[email protected]>
These are not needed here, as they are already part of the setting definition (that is, `settings.DANDI_LOG_LEVEL` always exists and has the correct default value if it is not set explicitly).
The [`logging` module docs](https://docs.python.org/3/library/logging.html#logging.Logger.setLevel) explain that `setLevel()` can handle the string representations of the logging levels. This allows the setting value to be directly tied to what is passed in, and `setLevel()` also does a "validation" on the value and will refuse to process levels that don't exist.
Design document for "atpath" endpoint
Co-authored-by: Roni Choudhury <[email protected]>
Add Dandiset star functionality with UI components
Co-authored-by: Roni Choudhury <[email protected]>
Check if dandiset contains zarr assets using asset list endpoint
Add .git-blame-ignore-revs to improve blame view
Fix dandiset ordering icons, default to descending
I did leave some references to DANDI since I thought it would be good at least for now.
EMBER-ify emails. Fix admin email
✅ Deploy Preview for ember-dandi-archive ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Adjust welcome email references to point to both EMBER and DANDI
…m-master 17 Update footer to have only a single support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.