amark/gun

welcome to the community chat! :)

Jabis Sevon

@jabis

should clear my peer again some old gunk in there x)

But yes what you said wasn't working gives output anyways

Wasis Haryo Sasoko

@yokowasis

@jabis can you try using gun from jsdelivr.net ? if it doesn't work, then that means gun from jsdelivr is broken and shoudln't be used.

Jabis Sevon

@jabis

I can't it's a live site

Wasis Haryo Sasoko

@yokowasis

can you try it in localhost ? please ?

this is my init.

        const gun = Gun({
                    localStorage : false,
                    axe : false,
                    file : "test",
                })

Jabis Sevon

@jabis

I'm busy with work - you could try changing jsdelivr includes from npm to gh/amark/gun@master/gun.js tho yourself to see

https://cdn.jsdelivr.net/gh/user/repo@version/file

is the format that is

Wasis Haryo Sasoko

@yokowasis

tried within react, using npm install, still doesn't work.

Jabis Sevon

@jabis

both your local and the versions you pull for browser need to be at the same version, to escape possible bugs

Wasis Haryo Sasoko

@yokowasis

I don't use the browser

Wasis Haryo Sasoko

@yokowasis

now it's working. I literally did nothing to the code. I am just too tired. go watch video on youtube. try to running the same code , and it works. I was like wtf 😣

Wasis Haryo Sasoko

@yokowasis

now another problem arise. Instead of grabbing matching criteria, it only grab 1.

anybody have a working gists of

This will grab keys with '2019/06/' matching prefix (grab all chats in July!) up to a limited number of bytes.

like in the docs ? https://gun.eco/docs/RAD#lex

Jabis Sevon

@jabis

Wasis Haryo Sasoko

@yokowasis

Now that I look at it, why '2019/06' is called july

@jabis can you return more than 1 matching results ?

let's say you have a chat from may to june. and you want to return june only

Jabis Sevon

@jabis

@yokowasis https://pastebin.com/H76i6Mzc here's my test script

it's a copy of my other SEA debugging script on node, I created test/ directory inside gun-folder and save that file there and run in the same directory

ie node test2.js in this case

wait I'll add a third result that's in 06 too

Jabis Sevon

@jabis

Wasis Haryo Sasoko

@yokowasis

@jabis thanks

Jabis Sevon

@jabis

@yokowasis there we go, 2 results as expected

https://pastebin.com/cx5s0Xnj here the updated one

Wasis Haryo Sasoko

@yokowasis

I think it's a bug. LEX/RAD able to get the result, but for some reason, it didn't fire the callback. The result is there, it's just the callback is not fired. But when you put something on the node, all of pending callback is get fired at once. @amark does this sound familiar to you ? maybe you heard a bug about the callback not get fired ?

Freddie

@Fredaroo_twitter

Hi guys, I've been playing around with Gun it the past few days. It's great :)
I have a few basic/conceptual questions I wasn't able to get with the docs though. I didn't want to bother you here so I opened it on StackOverflow if you want to have a look: stackOverflow link Hopefully I'm not the only one with such questions

Wasis Haryo Sasoko

@yokowasis

@jabis the reason it's get called only once before, is because I still have your data of 2019/06/22 I put more data something like 2019/06/22:10:10:10.30 2019/06/22:10:10:10.33, etc. it only read your data. the lex is {'.': {'*': '2019/06/22'}, "%" : 5000}

Jabis Sevon

@jabis

is 5000 bytes too low

50000bytes is max

Wasis Haryo Sasoko

@yokowasis

but when i change the lexical to {'.': {'*': '2019/06/22:'}, "%" : 5000} it results multiple of my data

5KB is still a lot for just hello world node.

Jabis Sevon

@jabis

yeah true

I note you have 2019/06/22:10:10:10.33 I don't how lex sorting on multiple : : : would work, that's not a date format imo

Wasis Haryo Sasoko

@yokowasis

can you try my finding :
put something like 2019/06, 2019/06/21, 2019/06/22, 2019/06/23, 2019/06/24

here is my complete data

{
  "2019/05/25:10:10:10.30": {
    "#": "chat/2019/05/25:10:10:10.30"
  },
  "2019/05/21:10:10:10.30": {
    "#": "chat/2019/05/21:10:10:10.30"
  },
  "2019/05/22:10:10:10.30": {
    "#": "chat/2019/05/22:10:10:10.30"
  },
  "2019/05/23:10:10:10.30": {
    "#": "chat/2019/05/23:10:10:10.30"
  },
  "2019/06/23:10:10:10.30": {
    "#": "chat/2019/06/23:10:10:10.30"
  },
  "2019/06/21:10:10:10.30": {
    "#": "chat/2019/06/21:10:10:10.30"
  },
  "2019/06/22:10:10:10.30": {
    "#": "chat/2019/06/22:10:10:10.30"
  },
  "2019/06/24:10:10:10.30": {
    "#": "chat/2019/06/24:10:10:10.30"
  },
  "2019/06/25:10:10:10.30": {
    "#": "chat/2019/06/25:10:10:10.30"
  },
  "2019/06/20:10:10:10.30": {
    "#": "chat/2019/06/20:10:10:10.30"
  },
  "2019/05": {
    "#": "chat/2019/05"
  }
}

gunHeroku.get('chat').get({'.': {'*': '2019/05'}, "%" : 5000}).map().once(s=>{
  console.log (s);  //This only fired once
})

is this an expected result ?

I note you have 2019/06/22:10:10:10.33 I don't how lex sorting on multiple : : : would work, that's not a date format imo

I copied it from the docs.

Wasis Haryo Sasoko

@yokowasis

from the docs :

* prefix match or (2 <) match. If {'*': 'key'} is specified, (2 >) will not match.

what do (2<) and (2>) means ?

Jabis Sevon

@jabis

values I was expecting :)

Wasis Haryo Sasoko

@yokowasis

Hi guys, I've been playing around with Gun it the past few days. It's great :)
I have a few basic/conceptual questions I wasn't able to get with the docs though. I didn't want to bother you here so I opened it on StackOverflow if you want to have a look: stackOverflow link Hopefully I'm not the only one with such questions

@amark , the docs really need some big overhaul.

@jabis what's the query ?

Jabis Sevon

@jabis

you can see it in the first snip

Lorenzo Mangani @qxip

@lmangani:matrix.org

[m]

GUN is opensource, improving docs is a perfectly valid way to contribute back ;)

Jabis Sevon

@jabis

@yokowasis

console.log("testing get {'.':{'>':'2021/06'} expecting 6 output")
  var i = 1;
  var raddy = gun.get(key).get({'.':{'>':'2021/06'},'%':50000}).map(data=>{
    i++;
    console.log("getter found data",data);
    if(i==2) t.equal(data.stuff, "22", "expected result to be `22` correct") 
    if(i==3) t.equal(data.stuff, "23", "expected result to be `23` correct")
    if(i==4) t.equal(data.stuff, "24", "expected result to be `24` correct")
    if(i==5) t.equal(data.stuff, "25", "expected result to be `25` correct")
    if(i==6) t.equal(data.stuff, "31 1.00", "expected result to be `31 1.00` correct")
    if(i==7) t.equal(data.stuff, "31 1.30", "expected result to be `31 1.30` correct")

  }).once();
  t.end();

Wasis Haryo Sasoko

@yokowasis

GUN is opensource, improving docs is a perfectly valid way to contribute back ;)

How can I contribute ? is there a github repo for the docs ?

2 replies

Where communities thrive

People

Repo info

Activity