pygmt error kills kernel and exits
See original GitHub issueWhen trying to make a pygmt figure, I apparently entered some unexpected values. However, even though a useful error message was thrown to the terminal, the python kernel was killed exited.
In [36]: fig = pygmt.Figure()
In [37] : fig.basemap(projection='A0/90/5i', region=[0, 360, -90, 90], frame='afg')
basemap [ERROR]: South boundary cannot be -90.0 for north polar Lambert azimuthal projection
pygmt version: 0.1.1 python 3.7.7 os: macOS
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
My jupyter notebook kernel often dies from this pygame code
I stopped running it on jupyter and run it now on VS code. So far there's no issue here. so it might be...
Read more >Bug listing with status RESOLVED with resolution TEST ...
0.10) leaves stale semaphore" status:RESOLVED resolution:TEST-REQUEST severity: ... Bug:381833 - "media-libs/mesa-7.11 will kill xorg on hardened kernels" ...
Read more >Slicer and jupyter kernel dies repeatedly, problem with ...
When I install SlicerJupyter and run it, it tries to connect and the dies. The messsage ist: “The kernel appears to have died....
Read more >Hunting territories and land use overlap in sedentarised Baka ...
A significant number of Baka Pygmies in Cameroon have been sedentarised in roadside villages, in contrast to their nomadic hunter-gatherer ...
Read more >7 CFR Part 301 -- Domestic Quarantine Notices - eCFR
Prior to leaving the packinghouse, the truck or container must be secured with a ... use of the restricted use pesticides Spray N...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Always good to get positive reinforcement that drudgery re-coding has a positive effect on others!
The issue was fixed in GMT 6.1.0. Although we can add a test to check it, but it seems unnecessary to me, since the same issue most likely won’t happen in GMT again.
Closing the issue.