[BUG] mapping values in gun.user does not work properly about gun HOT 10 OPEN

It seems that using await of any kind will cause this error. Again, only when using gun.user -> normal gun does not care.
Without the await in the following example, gun.user will behave as expected.

Example

            for(let i = 0; i < iterations; i++){

                await delay(0) // await for zero seconds, will cause issues as the operation is async
                const group_pair = crypto.randomUUID();
                const user_group = gun_test.get("groups").get(group_pair);

                user_group.get("one").put(Date.now());
                user_group.get("two").put(Date.now());
                user_group.get("three").put(Date.now()); // removing this line will make gun.user() be slightly less bad.

            }

from gun.

your above code in the last comment has a problem

const group_pair = crypto.randomUUID();                
console.log(typeof group_pair.pub)

from gun.

your above code in the last comment has a problem

const group_pair = crypto.randomUUID();                
console.log(typeof group_pair.pub)

You're right. I corrected it. The bigger issue still stands thogh.

from gun.

so.. im not 100% sure, but i think Map/Set are BEST used together and put/on(ce) are BEST used together.. map() use to list out keys ... to map out more data from the graph

https://gun.eco/docs/Frozen#update-immutable-links-to-mutable-user-content

so im asking.. can you check and see if Set and Map fail too?

from gun.

From my understanding map just maps all the values in a node. set is just a wrapper for put, that will give each item a unique key. What I think is odd in this case, is that normal gun maps everything correctly, but gun.user has problems mapping stuff.

Looking at your link, if I understand correctly, the idea is that we put a reference to the user private node a in the normal public gun. Then use gun.user to put our stuff, but gun to map over the stuff. This is cool! <3

Im not sure that this adresses this issue completely. I will have to try, but doing

gun.get(`~${user._.sea.pub}`).map();

will still not work. I think the issue is with the way that gun.put works when authenticated.

from gun.

ok cool... there is like small handful of places where this problem could be. because SEA adds in stuff to check/validate user profiles and hashed content. and that code starts here , https://github.com/amark/gun/blob/master/sea.js#L1321

from gun.

Cool, I will take a look at that. In the mean time for anyone else stumbling upon this, what I am doing currently is having all functions that make use of .put be synchronous. If they depend on awaited variables the functions can still await those internally kinda like so:

            user.get("root").get("foo").map().once(res => console.log(res)); // will log 100 times

            for(let i = 0; i < 100; i++){
                put_something(); // function is synchronous
            }

            function put_something() {
                const prepare = (async () => { return {id: (await SEA.pair()).pub } })();
                prepare.then(({id}) => { user.get("root").get("foo").get(id).put("hi!") });
            }

from gun.

@gustavcorpas this is helpful for helping hunt/track down the bug, thank you. Anyone willing to do a screen call to debug with me?

from gun.

@amark - I've seen you talk about an "intro to gun internals" a few years? ago. Did this ever happen? I would help, but I find it really difficult to find my way though the code.

from gun.