-
Notifications
You must be signed in to change notification settings - Fork 74
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
Exclude bad ipykernel version #1937
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we be sure it is just that one bugfix version? If so, then LGTM. Thanks!
Codecov ReportBase: 91.72% // Head: 91.72% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #1937 +/- ##
=======================================
Coverage 91.72% 91.72%
=======================================
Files 140 140
Lines 14824 14824
=======================================
Hits 13597 13597
Misses 1227 1227 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
FWIW I didn't see problem with ipykernel 6.19.1 that was installed from conda-forge. 🤷 |
.1 and .2 might work, but they will give you a lot of errors in the js console (at least .2), and may not always be stable (we have reports from people on .2 where not all widgets show). |
Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com>
Updated to <6.18 |
Approved. Though just to make sure, @maartenbreddels , you didn't mean Feel free to merge when CI passes. Thanks! |
Yes, it should be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will removing this pin be a part of #1788 or should we create a follow-up issue separately?
Great question. I guess it depends on the timeline of the ipykernel fixes...I'll open a separate issue. |
6.19.4 is just released
On Tue, 20 Dec 2022 at 17:39, rosteen ***@***.***> wrote:
Merged #1937 <#1937> into
main.
—
Reply to this email directly, view it on GitHub
<#1937 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANPEPJN367E2UEIYTJAX4LWOHOL7ANCNFSM6AAAAAATES5G6U>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Maarten Breddels
Software engineer / consultant / data scientist
Python / C++ / Javascript / Jupyter
www.maartenbreddels.com / vaex.io
***@***.*** +31 6 2464 0838 <+31+6+24640838>
[image: Twitter] <https://twitter.com/maartenbreddels>[image: Github]
<https://github.com/maartenbreddels>[image: LinkedIn]
<https://linkedin.com/in/maartenbreddels>[image: Skype]
|
Checked jdaviz with 6.19.4, and it works. |
…7-on-v3.1.x Backport PR #1937 on branch v3.1.x (Exclude bad ipykernel version)
that was pinned in spacetelescope#1937
Thanks! I included the pin upgrade in #1788 . FYI. |
that was pinned in spacetelescope#1937
Jdaviz won't show in the notebook with ipykernel 6.19.3, pinning to avoid that version.