-
Notifications
You must be signed in to change notification settings - Fork 10
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
Set the $schema
key with the schema dialect
#236
Conversation
For each generated schema
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #236 +/- ##
==========================================
- Coverage 97.58% 91.83% -5.76%
==========================================
Files 16 16
Lines 1701 1727 +26
==========================================
- Hits 1660 1586 -74
- Misses 41 141 +100
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@yarikoptic @satra Adding the |
I think it is indeed would be desired. Please add an explanation as well as you did in 09e50e1 |
although may be we should just set it upon adding a PR which has |
@yarikoptic I updated the |
let's drop last commit and proceed without releasing for now
|
a783271
to
862f25f
Compare
5841e4e
to
862f25f
Compare
@yarikoptic I trimmed this PR down to the only essential commit. However, for some reason, some of the cli tests failed at the following.
That error is only included in dc15401 which is not yet merged with this PR. How does this come about? The other error is
It seems that Python 3.8 is no longer available for the latests macOS version. |
|
it seems also for 3.9 . But note that it is looking at our dump of logs we keep on drogon:
so it flipped around 18th... but the fail there is not what you quoted, it is again about this new aspect of requiring email for contact person including the last one from today:
which adds to the insult of me missing all those fails while merging... Do you think you could look into them asap or should I? re arm64, I see it emerged only today in this PR:
and that flipped today -- before that it was
let's see if |
Those errors are very strange, but I think will try to resolve dandi/dandi-cli#1430 first. |
This PR closes #216.