-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
allowed_providers
/blocked_providers
no longer work if only one is given
#913
Comments
Thank you for reporting this issue! I certainly did make a mistake by not following up and re-enabling those tests. We plan to perform a release early next week (within 3-4 days), so I'll see if I can come up with a patch by then. Feel free to work on this issue in parallel as well if you'd like. |
The bug is in ipython/traitlets#908. It would be trivial to revert the problematic change but might be hard to solve cleanly. I spent a lot of time debugging this and might not have time to work on a fix anytime soon. In any case the only thing to do in |
This also affects other |
|
I think that maybe we can fix it in jupyter-ai by specifying |
Yes, one week after #415 was merged. And on November 8th the test was disabled in #446, which I suspect was liekly because it was not passing locally because someone may have had the new version of |
Description
allowed_providers
/blocked_providers
no longer work if only one is given. This is a pretty severe regression for administrators of tightly controlled deployments.Reproduce
with traitlets
5.13.0
and5.14.3
:with traitlets
5.12.0
With all versions of traitlets:
Expected behavior
When adding this feature I added tests which would have caught it (#415). Subsequently these were disabled (#446).
I would appreciate if these tests could be restored.
Context
Extension 2.19.1 and earlier.
The text was updated successfully, but these errors were encountered: