Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Embark Bot
    @embarkbot_gitlab

    michaelsbradleyjr@discord when attempting to listen to a channel I get:

    Error: Returned error: Invalid params: invalid type: string "messages", expected struct FilterRequest.

    Jo@discord Quite possible that Parity doesn't support Whisper
    Embark Bot
    @embarkbot_gitlab

    michaelsbradleyjr@discord it seems to; included in parity --help:

    Whisper Options:
        --whisper
            Enable the Whisper network.
    
        --whisper-pool-size=[MB]
            Target size of the whisper message pool in megabytes. (default: 10)

    in any case, at least latest parity is mostly viable for embark v4 users. I could poke at getting geth 1.9 working w/ embark v4, but I think it would either involve a fragile workaround for the simples problem or replacing the guts of the proxy

    michaelsbradleyjr@discord it seems to; included in parity --help:

    Whisper Options:
        --whisper
            Enable the Whisper network.
    
        --whisper-pool-size=[MB]
            Target size of the whisper message pool in megabytes. (default: 10)

    in any case, at least latest parity is mostly viable for embark v4 users. I could poke at getting geth 1.9 to work w/ embark v4, but I think it would either involve a fragile workaround for the simples problem or replacing the guts of the proxy

    Jo@discord > but I think it would either involve a fragile workaround for the simples problem or replacing the guts of the proxy
    might not be worth it then
    Embark Bot
    @embarkbot_gitlab
    michaelsbradleyjr@discord looks like parity's RPC for whisper, i.e. shh_* calls, varies a bit from geth's
    Jo@discord That's no good
    Rahul Buddhdev
    @rahulthakkar796
    @jrainville Hi, I'm using v 4.0.2 , actually sometimes it's not regenerating artifacts for new deployed contracts, so i need to run 'embark run' command 3-4 times to make it work.
    Jonathan Rainville
    @jrainville
    @rahulthakkar796 Do you have an error when it doesn't generate?
    Rahul Buddhdev
    @rahulthakkar796
    @jrainville No , No errors at all. I just need to run embark run again and again.
    Jonathan Rainville
    @jrainville
    Very weird. Do you have a repo we could look at to see if we can reproduce and identify the problem?
    Rahul Buddhdev
    @rahulthakkar796
    @jrainville yeah it's weird, because i have started face this issue from last 2-3 days. actually it's a private project so i can't share code but i will make a repo of necessary files so that u can check it out.
    Embark Bot
    @embarkbot_gitlab
    michaelsbradleyjr@discord looks like parity's RPC for whisper, i.e. shh_* calls, varies a bit from geth's
    note: maybe not, I think I was comparing old docs
    Embark Bot
    @embarkbot_gitlab
    barryg@discord Has anyone dealt with account changes for dapps running in Status?
    Jo@discord Not sure we ever tested that for Teller.
    Jo@discord Have you? Does it behave weirdly?
    barryg@discord testing now, works on MM not on status
    barryg@discord at least for me
    Embark Bot
    @embarkbot_gitlab
    Jo@discord Haven't tried account switching much on Status. Don't you have to relogin when doing it?
    Embark Bot
    @embarkbot_gitlab
    barryg@discord perhaps, but any dapp that uses that listener will break in status
    Jo@discord Break as in that code never triggers, or it just throws when reaching that code?
    Jo@discord Ah, I can see it throwing, since it uses ethereum
    Embark Bot
    @embarkbot_gitlab
    barryg@discord > Does the Status wallet support window.ethereum.on('accountsChanged' ?
    no because on account change we refresh dapp and clear data
    barryg@discord probably just have to wrap it in a try catch, probably the way to go for most ethereum listeners since it's hard to know which wallet supports what
    Embark Bot
    @embarkbot_gitlab
    Andrey@discord hey team i'm working on eip-1193 in status, does embark support it ?
    Embark Bot
    @embarkbot_gitlab
    PascalPrecht@discord We have a ticket for it but it's not being worked on as of now
    PascalPrecht@discord Right now we're busy stabilizing Embark V5
    Andrey@discord kk thanks
    Andrey@discord regarding your question window.ethereum.send({jsonrpc:"2.0",method:"eth_accounts","params":[],"id":1}, console.log)
    Andrey@discord i'll fix that but there will be a Promise with empty array
    Embark Bot
    @embarkbot_gitlab
    rramos@discord cooltastic, dude! thanks!
    Embark Bot
    @embarkbot_gitlab
    Andrey@discord i'll change this as well, should it return empty array instead?
    Andrey@discord btw if you call ethereum.send({jsonrpc:"2.0",method:"eth_accounts" you will not have an error
    Andrey@discord error will be only for sendAsync({jsonrpc:"2.0",method:"eth_accounts"
    Andrey@discord after my changes both send and sendAsync will work the same , and i'll make a change for "eth_accounts" , it will return empty account instead of error
    rramos@discord I was not aware of the send/sendAsync difference
    Embark Bot
    @embarkbot_gitlab
    michaelsbradleyjr@discord @Andrey what's the underlying mechanism for the synchronous .send (assuming it's synchronous)?
    Andrey@discord there is no synchronous .send anymore
    Andrey@discord "all" send return promise
    michaelsbradleyjr@discord nice, okay, that's what I was wondering about
    Andrey@discord i mean in status beta it's still synchronous, but in v1 it will return promise according to eip
    Jo@discord sendAsync is mostly deprecated I think too, but both are async anyway
    michaelsbradleyjr@discord synchronous XHR used to be a thing, but gladly is a thing of the past, though I guess some runtimes still support it