[BUG] Can't write objects to JSON
See original GitHub issuev3.0.14
import pickle
t = ds.create_tensor(f"t/group/f", htype="json", chunk_compression="lz4")
t.append(pickle.dumps("test")) # pass any pickled object into append gets error
ValueError: Circular reference detected
passing strings and such into this tensor works fine, but for some reason any pickled object or python object that gets pickled gives the above ValueError.
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Problem when writing to file. · Issue #904 · nlohmann/json
I'm trying to write json file to file. ... + ".json"; //party is the root of the json objects json party = json::array();...
Read more >Cannot write to JSON in Nodejs - Stack Overflow
The Database refreshes by reading from the JSON file and I have traced my problem to Nodejs not writing to disk, and I...
Read more >How to write custom converters for JSON serialization - .NET
Learn how to create custom converters for the JSON serialization classes that are provided in the System.Text.Json namespace.
Read more >Read/Write JSON Files with Node.js | heynode.com
JSON.parse takes JSON data as input and returns a new JavaScript object. Otherwise, we would just have a string of data with properties...
Read more >Gson - How to convert Java object to / from JSON - Mkyong.com
But i have to say that the File Reader and Writer need to be closed to work properly. When your create them inside...
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
@nollied thanks for noting the issue! we also observed issues writing under
lz4
compression. Let us take a deeper look at it and get back when this gets fixed.Hey Dyllan! Fixed the issue in #1994, we’ll include it in the next release.