Am I reading this wrong or is it buggy/glitchy? If I have 541 edits today (what are the numbers in the () btw?) then shouldnt past 7 days and All time be higher/different?
ie: today: 541, past 7D: 800, All time: 1000 ?
This looks like it has just copied the same number on all 3 categories.
cells being zero makes sense since unlike FW/BANC so far in pyr we arent able to declare cells complete somehow. (Iām guessing thatāll change in future datasets?)
I have the same bugs as nik and kfay
another bug i have is: If i try to merge something and get it wrong (too close to the edge) when i then remove the points i have tried to merge. My 2D / 3D goes black when howering over any segment. To fix this i need to refresh the page.
Singlehandedly the worst bug for me is the ā2D image refresh stallā where it just gets a very blurry jpeg of the 2D or nothing at all, and then shuts down the render pipeline for it. I know a refresh isnāt a big deal but when youāre in the zone itās enough to pull you out.
Well, this was weird, I had several segments merging into 1 cell/branch (one of those that go straight line across the dataset w/o forking etc) they merged, they vanished from the segments list and 2D/3D, then refresh and/or undelete isnt bring the merged result backā¦(and I didnāt have 2D axis right on the segment so Idk where it isā¦)
Just as an addendum to this in case it helps identify -why- it keeps happeningā¦ Iāve noticed when I lose the ability to load 2D, itās always accompanied by an error in the Dev Console of āAbortError: The operation was aborted.ā
Whatās interesting is that continuing to try and explore still shows the download happening, but itās like the Download Managerās been detached from the layer, and so all that new data just goes into a buffer somewhere and is never āconsumedā.
Zooming in or out in the 2D layer generates a whole bunch more of the AbortErrors.
Interestingly, when I try to create a new layer to āmimicā zheng_ca3 (image), I still donāt get anything to load on the new layer, so this feels like itās a bug in the GrapheneChunkedGraphChunkSource download function, rather than with the layer.
yeah not sure for how long, but it have been slower.
i am also getting this message that i canĀ“t remember to have seen before. second try with same points worked.
yep, itās been slower since 1 or 2 days. i had to modify latence of my macros to add 3 secs more for waiting for loads.
Also, more problems with merges very slows and cuts that failed more imo