v0.12 TypeError
See original GitHub issueDescribe the bug The following assertion worked until v0.12. Now it returns a TypeError.
To Reproduce
import sparse
import numpy as np
a = np.random.rand(1000,1000)
a[a<.9] = np.nan
a = sparse.COO(a, fill_value=np.nan)
a.fill_value = 0.0
a = sparse.COO(a)
assert a == a
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
v3.9.0+ breaks on node v0.12 · Issue #933 · zloirock/core-js
require('core-js') breaks in node v0.12 with: TypeError: Cannot convert a Symbol value to a string at String (native) at Object.
Read more >Input 'split_dim' of 'Split' Op has type float32 that does not ...
Update: If you cannot update the underlying libraries, then you should use the previous/older/pre-v0.12 signature for tf.split :
Read more >TypeError: t.test is not a function - support - HUGO
This began after upgrading from 0.97.3 to 0.99.1. Made sure the extended version is installed, and tried installing the packages mentioned in the...
Read more >Node-Red TypeError - Raspberry Pi Stack Exchange
This one is already open issue in Node red community. Open state: https://github.com/node-red/node-red/issues/565. Specific to the error is in closed state.
Read more >FAQ — MMDetection3D 0.12.0 documentation
TypeError : expected dtype object, got 'numpy.dtype[bool_]'. please downgrade numpy to < 1.20.0 or install numba == 0.48 from source, ...
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

Another bit of unsupported behaviour there is
a == a. You should really writeassert (a == a).all().The best way would be to construct a new
COOwith the same coords and data, but a new fill-value. AFAIK this won’t incur copies.