summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorAlexander Kabui2022-03-18 12:14:23 +0300
committerAlexander Kabui2022-03-18 12:14:23 +0300
commit08ec9efd4a6c6ac5c6bf0b1f14f202fd7c319303 (patch)
tree60417fa6625219aec071a8a7298620a7c847d6ec /issues
parent7f9bacc3f79f3af1f26042cf1282aeb8895f5cd7 (diff)
downloadgn-gemtext-08ec9efd4a6c6ac5c6bf0b1f14f202fd7c319303.tar.gz
update metadata caching issue
Diffstat (limited to 'issues')
-rw-r--r--issues/metadata-caching-bug20
-rw-r--r--issues/remove_gn2_gn3_network_dependency.gmi4
2 files changed, 22 insertions, 2 deletions
diff --git a/issues/metadata-caching-bug b/issues/metadata-caching-bug
index eea4a31..4fb382d 100644
--- a/issues/metadata-caching-bug
+++ b/issues/metadata-caching-bug
@@ -1,3 +1,5 @@
+# metadata caching bug
+
A user recently notified me of an error when doing a correlation of a BXD phenotype trait against other BXD phenotypes.
The error is somehow being caused by the metadata caching (it's an error when loading the cached metadata JSON file), but it's not clear to me what the issue is (and I'm not sure how to locate it within such a large file, since the error message only gives the character position).
@@ -32,3 +34,21 @@ return _default_decoder.decode(s)
File "/gnu/store/p5fgysbcnnp8b1d91mrvjvababmczga0-python-3.9.6/lib/python3.9/json/decoder.py", line 340, in decode
raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 1 column 6765450 (char 6765449)
+
+
+
+
+## Tags
+
+* assigned: alex, zachs
+* keywords: correlation,caching,metadata
+* type: bug
+* status: completed
+* priority: medium
+
+
+
+## Tasks
+
+* [X] fix for caching empty json files
+* [X] delete invalid files and recreate new ones \ No newline at end of file
diff --git a/issues/remove_gn2_gn3_network_dependency.gmi b/issues/remove_gn2_gn3_network_dependency.gmi
index 0a2262a..4f59762 100644
--- a/issues/remove_gn2_gn3_network_dependency.gmi
+++ b/issues/remove_gn2_gn3_network_dependency.gmi
@@ -2,8 +2,8 @@
occasionally while sending requests from gn3 from gn2
for tools like ctl and wgcna users run into network
-errors if the gn3 server is down or other related issues
-
+errors if the gn3 server is down or other issues.Idea
+is to use gn3 as library to avoid the above
## Tags