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
[BUG] AtlasMap is stuck after importing CSV on latest Google Chrome 105 #4320
Comments
Root cause And updating ky triggered a fire on outdated frontend toolchain. Since newer ky no longer provides umd module, Jest configuration needs to be updated to work with esm. Also react-scripts conflicts with newer ky.
|
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Sep 8, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
that referenced
this issue
Sep 9, 2022
Fixes: #4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
that referenced
this issue
Sep 9, 2022
Fixes: #4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
that referenced
this issue
Sep 9, 2022
Fixes: #4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
that referenced
this issue
Sep 9, 2022
Fixes: #4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to igarashitm/atlasmap
that referenced
this issue
Oct 6, 2022
Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
igarashitm
added a commit
to jboss-fuse/atlasmap
that referenced
this issue
Oct 6, 2022
#6) Fixes: atlasmap#4320 Google Chrome 105 made a breaking change and made some case fail which used to be working fine with older Chrome. https://developer.chrome.com/articles/fetch-streaming-requests/ ky made a fix for that sindresorhus/ky#450 But since the newer ky no longer provides umd, we had to change the Jest configuration to deal with esm. Also we needed to introduce craco to add @babel/plugin-proposal-nullish-coalescing-operator which is required to update ky.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I import CSV file into AtlasMap version 2.3.18, the UI is stuck on loading page. This happens only in Google Chrome. After that, refresh UI doesn't help and it is still stuck.
Also when I have already imported CSV via Firefox and then try open AtlasMap in Chrome, it is stuck until I delete CSV from in Firefox.
See video:
https://user-images.githubusercontent.com/16251792/188913385-efebc87a-81df-41cb-a59e-57d52e71cce3.mp4
Environment:
Fedora 36
This issue happens only in Google Chrome v 105.0.5195.52 . ( on version 102.0.5005.61 works )
No issue with Firefox 104.0
xref: https://issues.redhat.com/browse/ENTESB-19709
The text was updated successfully, but these errors were encountered: