refactor: rework untyped Component._raw_construct

Summary
Changes the entirely untyped Component._raw_construct implementation, improving typing by adding separate _update methods in concrete components.
Since .ui items need a way to construct a component without a payload dict, they previously called _raw_construct (untyped) with all the attributes, which would just setattr() them based on the type's slots.
Instead, ui items now need to call _raw_construct with just the type, and call _update (properly typed) on the created component with all the attributes, as seen here:
https://github.com/DisnakeDev/disnake/blob/314aa2b12ed176823505424ffd364e99719b5965/disnake/ui/action_row.py#L78-L79
The ideal solution for this would be having __init__(arg1, arg2, ...) and @classmethod from_dict(data) for every component, but I'd really like to avoid breaking changes here; the new implementation is fully typed, but slightly less intuitive to use than a trivial from_dict call.
While the previous implementation works alright, these changes are done in preparation for future updates.
Checklist

[x] If code changes were made, then they have been tested

[ ] I have updated the documentation to reflect the changes
[x] I have formatted the code properly by running task lint
[x] I have type-checked the code by running task pyright

[ ] This PR fixes an issue
[ ] This PR adds something new (e.g. new method or parameters)
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

After continuing to work on this for a bit, I've decided to close this PR, as I'm not happy with the changes. Might try to come up with a better solution at some point, but for now the existing implementation will do.


Fix issue #1509

@jackyq2015 this will fix for any importer ?

This is not to do with the actual memory the data set consumed. It will only take 100 rows as the sample to infer the type. After that it will be gced.
@thadguidry It will apply to all importers.

Oh okay - I had not noticed the copying indeed. So I think this should solve this particular issue - but I am still worried about the overall instability brought by the Data Package PR. What is now clear is that it has introduced bugs that are unrelated to Data Packages.
The risk is high that some of the bugs it has introduced have still not been discovered and could make it into the next release. I tried my best to scrutinize the PR but it was very hard given its poor state. The fact that we have serialization issues is serious - potentially, that could lead to corrupting users' projects and losing data. This is a high risk to pay for a feature that will go mostly unnoticed given the lack of integration in the UI.

@wetneb Besides reverting the PR... what are you proposing to improve the PR ? More tests ?  An alternate form of testing this somehow or seeing the impacts ?  How can we bring confidence to the importers and Data Package / Metadata enhancements ?

Each update of dependency should be made in its own PR, explaining why the update is needed and assessing how the library is currently used in the code. It does not need to be extremely detailed, of course: it's just about assessing what are the sort of changes made in the library (any breaking ones) and see what sort of risk it implies for us. For instance, when we updated Jython it was fairly clear that we were touching a fairly well isolated part of the code base, and we saw that their new release included mostly bug fixes, so that's good. It's just an analysis that needs to be done.
No dead code should be introduced - currently there are loads of constraint checkers that are not exposed at all in the UI: it's much safer just not to include them at all.
iIf the Data Package library we rely on is not quite ripe yet, fix it. Yes, that takes time, but it's necessary to avoid ugly hacks like the use of reflection to handle datatypes.
More unit testing. A lot more.
Commits should reflect logical changes and have meaningful commit messages. That makes reviewing much easier: you can just look at each commit in order, understand its logic and assess it independently of the rest. It's impossible to do that if the PR is crippled with unrelated commits and merges: you have to review the final diff and it's much harder to spot problems.

Generally speaking, just pretending to do some quality software engineering…

@wetneb It is interesting to see that you say it is not related to the data package.  It looks like you are the only guy who can do the quality software work in the world.  I am speechless at your attitude. that's all I can say.

Well, it's related because it was introduced by your PR, but take the standpoint of a user: they just want to import an XML file and they don't care at all about Data Packages. These are two unrelated things for users. What I mean is that it is a lot more serious than any bug in the Data Package exporter for instance (which are not going to disturb any existing user workflow).
Sorry if it sounds like I am trying to teach you a lesson - I was just trying to give concrete points to @thadguidry. I am just trying to point out some elementary principles that could have helped avoid the critical bugs that you have introduced in OpenRefine. Bugs happen, it's a normal thing - but these ones are really serious and you are getting paid for this work. There is just a minimum quality standard that should be met.
I clearly have a lot to learn myself about good practices in software engineering - and I will soon submit a PR for the Wikidata package where your criticism will be valued. I am happy to skype today if you want to discuss things directly.

@jackyq2015 I don't think anyone is displaying an attitude.  Antonin is trying to help improve things and had legitimate concerns as did I, but most of those concerns are removed.  Let's not be too harsh, after all, its only the few of us that I can count on 1 hand. :) right ?  And thanks to both of you for even caring about this little project called OpenRefine that we all work so hard on !
OK, so, let's get to work as the awesome team we are ... we know we need to improve the tests here, around Project Creation and Importers... @jackyq2015 any other areas that you feel would help to assure quality in future PR's around Data Package and Metadata that you can think of ?  Also, Antonin brought up a good point about the Data Package java library...should we invest some time to help fix that up, anything within that concerned you while working with it Jacky ?

The first thing I want to address is that this change is integral part of the data package change. It is NOT unrelated change. Since we need to apply the types infer defined by data package and that has to be done at the import stage. From the QA aspect, I agree we need more UT and that won't solve all the problem. That part of code  is covered by UT and not that that similar test data which can break it. For this particular case, I will write a UT to cover it.

@jackyq2015 Awesome, thanks Jacky. that will help.

@jackyq2015 sorry yes, I should have made clear that I am actually more worried about the other issues #1517 and #1508 than this one…
And just to be clear: the tests that were already in place in OpenRefine are really sparse (the test coverage is so low!), so it really does not help us in our work… typically, this bug should have been caught by an existing test for the XML importer (one that you should not have needed to write)!

@thadguidry The infer only impact the column model, the row model is impacted.


A server command to clear active portals from the servers /dire portal clear

Describe the feature you'd like to have added
Can a server command be added to clear active portals from the server with a basic command as inactive players portals can be problematic?
/dire portal clear
Additional information
No response

The portals are entities, so you should be able to /kill them.  /kill the justdirethings:portalentity type (something like that)

many thanks


feat(dom): overload .event() method using HTMLElementEventMap

The lib.dom.d.ts file contains a mapping where the name of the event type is mapped to the event
type itself (e.g. click -> MouseEvent). Using this mapping on the DOMSource.events() function allows
the correct event stream to be returned.

[ ] I added new tests for the issue I fixed/built
[x] I ran make test FOO for the package FOO I'm modifying
[x] I used make commit instead of git commit

That's cool, I didn't knew that HTMLElementEventMap existed

And overloading is the right move, because we might want to use custom events

Thanks for the PR!!

No problem, happy to help!

Wow, HTMLElementEventMap is great! Thanks for the PR

This is so cool. Just searched for this. Thank you for the PR. Looking forward to a release.

Sweet. Thank you


Can GD2 be described mathematically?

Can GD2 be described mathematically? As of right now, I'm not quite sure what it is for.

I've moved this to TMs and now reference it from assumptions as well. It's more the theoretical idea describing the space limits where the beam can be moved/deflected to.


[Bug]: Install script fails on Ubuntu 23.10

Description
Install script fails on Ubuntu 23.10
Error Message:
ERROR: '24.0.2' not found amongst apt-cache madison results
The error message suggests that the Docker version '24.0.2' is not available in the repository list returned by 'apt-cache madison docker-ce'.

This is due to an error in https://releases.rancher.com/install-docker/24.0.sh - when this error happens, the coolify install script swallows it and continues.
To remedy, assuming version 24.0 for now, wget https://releases.rancher.com/install-docker/24.0.sh change line 88:
-VERSION="24.0.2"
+VERSION="24.0.7"

This 24.0.7 is discovered by running apt-cache madison docker-ce
which outputs
docker-ce | 5:24.0.7-1~ubuntu.23.10~mantic | https://download.docker.com/linux/ubuntu mantic/stable amd64 Packages
This error is also referenced here:
https://github.com/rancher/rancher/issues/38362
Minimal Reproduction (if possible, example repository)
To reproduce run curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
Exception or Error
No response
Version
4

Thanks for the suggestions. I'm closing this issue for now.
If you would like to help to improve Coolify, please reopen this issue with a PR.


Better Errors

Fixes #21

I have addressed your request, will merge it now because I want to continue work and start another PR. In case you find there are other changes needed, I'll address them in a future PR.
bors r+


Feature flags

Feature Description
Have a method to have features merged into master but disable / hidden via a feature flag.
This would allow developers to merge incomplete work while not showing it to users.
Acceptance Criteria
QA Instructions

There seems to be several nom packages providing support for feature flags:
https://www.npmjs.com/package/flagged
https://www.npmjs.com/package/react-feature-flags
flagged is particularly interesting as it provides support for HOC and hooks, and seems more powerful in general.

flagged looks simple enough 👍
Would be trivial to connect this with our build tooling too, i.e. to create ZIP files with certain features enabled for sharing with testers.

I have created a follow up ticket this one to add a UX to feature flags.
https://github.com/google/web-stories-wp/issues/1738


Custom config location

It would be great if we could specify a custom config location so a fallback/default .jsbeautifyrc file could be synced when using https://github.com/atom-community/sync-settings.  Sync settings allows you to sync files located in ~/.atom, so if we could store the .jsbeautifyrc there it could be synced with other settings.
Ideally then you could specify the atom-beautify config location as ~/.atom/.jsbeautifyrc to get your default/fallback synced - emmet works using something similar.  Does that sound like something that's possible?  Thanks for the great plugin - appreciate all of the work that's gone into it.

:+1:!
Atom-Beautify currently supports a .jsbeautifyrc within the user's home directory.
The ~/.atom/.jsbeautifyrc path could also be included by changing https://github.com/Glavin001/atom-beautify/blob/master/src/beautifiers/index.coffee#L435-L444 and/or related parts.


Difficulty getting WebSocket rpcs to work

Do you want to request a feature or report a bug?
Possibly a bug
What is the current behavior?
I have tried different RPC providers:

Moralis
Quicknode
Figment
Chainstack
Getblock

Most of them don't work and fail with either of these:

400 bad request
301 moved permanently
404 not found

which I understand are wildly different error codes, but I can geth attach ws://.... to all of them just fine, so I am guessing there's something wrong here, maybe something to do with TLS or handshake or connection upgrade, not really sure.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Steps to reproduce is just use WebSocket RPC from any of these providers. You may find the logs attached below, I am cutting off the top part where the endpoints are listed for obvious reasons:
Feb 23 14:50:54.889 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-8
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-9
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-10
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-11
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-12
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-13
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-14
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-15
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: bsc-rpc-16
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: avalanche-rpc-0
Feb 23 14:50:54.891 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: mainnet-rpc-2
Feb 23 14:50:54.893 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: mainnet-rpc-3
Feb 23 14:50:54.893 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: arbitrum-rpc-1
Feb 23 14:50:54.893 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: fantom-rpc-4
Feb 23 14:50:54.893 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: fantom-rpc-5
Feb 23 14:50:54.893 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: fantom-rpc-6
Feb 23 14:50:54.893 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: fantom-rpc-7
Feb 23 14:50:54.895 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 43114, provider: avalanche-rpc-0
Feb 23 14:50:54.895 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.896 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.897 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 250, provider: fantom-rpc-4
Feb 23 14:50:54.900 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.900 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.904 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.906 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.910 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.910 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.918 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:54.920 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:54.923 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.927 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.938 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:54.944 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.945 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:54.945 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:54.946 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:54.949 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:54.952 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.952 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:54.960 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.974 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:54.974 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:54.975 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:54.977 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:54.987 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:54.988 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:54.990 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.000 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.001 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.002 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.005 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 56, provider: bsc-rpc-11
Feb 23 14:50:55.005 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.005 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.007 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.008 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.016 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.029 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.035 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.035 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.035 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.038 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.045 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.049 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 250, provider: fantom-rpc-6
Feb 23 14:50:55.051 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.054 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.058 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.069 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.075 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.078 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.079 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.084 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 56, provider: bsc-rpc-15
Feb 23 14:50:55.087 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.087 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.088 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.095 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.103 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.110 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.111 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.111 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.114 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.115 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.121 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.123 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.124 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.128 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.133 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.136 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.140 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.152 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.153 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.160 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 1, provider: mainnet-rpc-2
Feb 23 14:50:55.160 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.167 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.173 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.176 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.187 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.188 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 56, provider: bsc-rpc-16
Feb 23 14:50:55.189 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.189 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.192 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.197 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 42161, provider: arbitrum-rpc-1
Feb 23 14:50:55.199 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.205 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.215 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.222 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.233 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.234 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.239 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.243 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.246 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.248 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.267 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.271 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.272 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.300 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.306 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.320 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.329 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.333 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.356 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.359 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.360 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.360 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.365 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.382 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.383 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.384 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.390 DEBG Trying again after net_version RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:55.393 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #1) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:55.393 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.394 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.408 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.444 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.446 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.449 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.462 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.478 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.478 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.480 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.488 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.527 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.549 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.566 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.578 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.595 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.600 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.607 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.612 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.620 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.664 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.671 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.677 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.679 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.724 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.724 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.751 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.760 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.774 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.777 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.779 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:55.789 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.798 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.811 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.859 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:55.862 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.864 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:55.866 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.885 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:55.891 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:55.895 DEBG Trying again after net_version RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:55.900 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:55.903 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #2) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:55.920 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.949 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:55.967 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:55.998 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:56.052 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:56.071 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:56.087 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:56.114 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:56.130 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:56.148 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:56.174 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:56.185 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:56.187 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:56.272 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:56.275 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:56.294 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:56.301 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:56.338 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:56.351 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:56.408 DEBG Trying again after net_version RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:56.411 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:56.413 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #3) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:56.549 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:56.616 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:56.626 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:56.668 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:56.685 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:56.721 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:56.829 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:56.904 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:56.910 DEBG Trying again after net_version RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:56.922 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #4) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:57.023 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:57.055 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:57.101 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:57.115 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:57.198 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:57.261 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:57.271 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:57.398 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:57.427 DEBG Trying again after net_version RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:57.440 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #5) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:57.444 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:57.467 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:57.636 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:57.638 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:57.723 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:57.822 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:57.847 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:50:57.956 DEBG Trying again after net_version RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:57.972 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #6) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:57.993 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:58.009 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:50:58.089 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:58.207 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:58.240 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:58.454 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:58.470 DEBG Trying again after net_version RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:58.474 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:50:58.527 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:58.538 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #7) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:58.622 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:58.678 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:50:58.853 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:58.854 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:59.029 DEBG Trying again after net_version RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:59.124 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:50:59.142 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #8) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:59.152 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:59.242 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:50:59.495 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:50:59.635 DEBG Trying again after net_version RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:59.650 DEBG Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #9) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:50:59.803 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:50:59.814 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:00.402 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:00.465 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:00.531 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:51:00.555 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:00.563 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:51:00.869 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:01.280 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:01.631 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:01.804 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:51:01.818 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:01.860 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:01.944 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:02.102 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:51:02.118 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:51:02.417 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:51:02.507 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:51:02.565 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:02.611 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:51:02.639 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:03.255 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:03.285 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:51:03.662 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:03.687 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:03.779 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:03.924 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:51:03.959 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:51:04.548 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:51:04.883 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:51:05.290 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:05.499 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:05.720 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:05.834 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:07.018 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:51:08.115 WARN Trying again after net_version RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:51:09.188 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:51:09.464 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:51:09.618 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:10.323 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:10.328 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:11.744 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:51:12.035 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:12.835 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:14.138 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:14.716 WARN Trying again after net_version RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:15.483 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:51:15.677 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:51:16.332 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:51:16.387 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:17.382 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: bsc-rpc-8
Feb 23 14:51:18.642 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: bsc-rpc-12
Feb 23 14:51:18.704 WARN Trying again after net_version RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:18.864 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-13
Feb 23 14:51:20.400 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: fantom-rpc-7
Feb 23 14:51:20.416 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:21.136 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 404 Not Found), provider: fantom-rpc-5
Feb 23 14:51:22.560 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #17) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-10
Feb 23 14:51:23.872 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 402 Payment Required), provider: bsc-rpc-9
Feb 23 14:51:23.953 WARN Trying again after net_version RPC call failed (attempt #17) with result Err(Transport error: Unexpected response status code: 400 Bad Request), provider: mainnet-rpc-3
Feb 23 14:51:24.600 WARN Trying again after net_version RPC call failed (attempt #16) with result Err(Transport error: Unexpected response status code: 301 Moved Permanently), provider: bsc-rpc-14
Feb 23 14:51:24.890 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: bsc-rpc-8
Feb 23 14:51:24.892 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: bsc-rpc-9
Feb 23 14:51:24.892 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: bsc-rpc-10
Feb 23 14:51:24.893 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: bsc-rpc-12
Feb 23 14:51:24.893 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: bsc-rpc-13
Feb 23 14:51:24.893 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: bsc-rpc-14
Feb 23 14:51:24.894 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: mainnet-rpc-3
Feb 23 14:51:24.894 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: fantom-rpc-5
Feb 23 14:51:24.894 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: fantom-rpc-7

P.S.: Ignore the 402 errors they are because I ran out of my getblock.io quota
What is the expected behavior?
Should be able to consume the WebSocket RPCs fine.

Hi @meetmangukiya - I think polling RPCs are recommended for graph-node. Why are you looking to use websockets in particular?

@azf20 just assumed ws connection would land the updates faster as a push/subscription model vs polling model

Also, I think WebSocket rpcs could reduce costs when using third party rpc provider services like alchemy, infura, etc.


Print more error context

Off the back of #114/#115, it'd be great to have more lines/context around errors. Example:
./x-all.json:6:21:
  |
6 |     "message": "{x, bad}"
  |                     ^^^^^^
unexpected "bad}"<newline>  },<newline>  "
expecting "boolean", "date", "number", "plural", "select", "selectordinal", "time", or white space

I can see the line number and the problem itself, which is good, however ideally it'd also show the line above with the translation name. In an ideal world we would always show everything in the object:
./x-all.json:6:21:
  |
5 |   "f": {
6 |     "message": "{x, bad}"
  |                     ^^^^^^
7 |   }
  |
unexpected "bad}"<newline>  },<newline>  "
expecting "boolean", "date", "number", "plural", "select", "selectordinal", "time", or white space

This is relevant to linting output as well as of #179.
It's unclear how well this would scale. The object may be large and the message mayn't be at the top.


Add A Queues Info Command

Fixes MQ-677
Per MQ-677 We need to add a queues info command to Wrangler so that individual queues can be inspected from the command line. This returns basic queue information like queue id, queue name, the names of producer and consumer scripts, and a curl command for http pull consumers (similar to what is in the dashboard).

Tests

[ ] TODO (before merge)
[x] Tests included
[ ] Tests not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[X] Not required because: Changes should not affect anything that requires e2e coverage.

Public documentation

[ ] TODO (before merge)
[x] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/18310
[ ] Documentation not necessary because:

Hi @toddmantell, your tests are failing because we recently removed the --experimental-json-config. Could you help updating the snapshots? Thank you!

@edmundhung Thank you! I was trying to debug what was causing the test failures.  I just made that update.

@toddmantell LGTM!


what is the query format for the Phase 2 Nodes?

https://github.com/maxdemarzi/neography/wiki/Phase-2-Nodes
Neography::Node.find(index, query)
is query a Lucene query or cypher query?

It is a query for the legacy indexes. It can be a simple value or a complex lucene syntax query.  See:
https://github.com/maxdemarzi/neography/blob/afb3a4724e67d6665d79ca280bb709e69814e893/spec/integration/index_spec.rb#L28 and https://github.com/maxdemarzi/neography/blob/afb3a4724e67d6665d79ca280bb709e69814e893/lib/neography/rest/node_indexes.rb#L51
However this does not use Labels or Schema indexes. For those see https://github.com/maxdemarzi/neography/blob/afb3a4724e67d6665d79ca280bb709e69814e893/spec/integration/rest_labels_spec.rb#L109


chore: upgrade pnpm

Current dependencies on/for this PR:

main

PR #210   👈

This comment was auto-generated by Graphite.


Strengthen connections with other communities of practice

Agile Community of Practice
How to help organize/contribute (GAO, OMB), has about 200 people
https://digital.gov/communities/agile-lean/
https://www.agilegovleaders.org/agl-establishes-non-profit-association-serve-government-innovation-community/

Is there a roster of members? I'd like to better understand Guild vs Community of Practice membership.

cc @ecayer

@afomi following up here. I don't know offhand of a roster (we don't have one for the guild as it's more of an "attend and you're a member" sort of thing). We could follow up with the other community to see if they have something.

Closing as stale, on the assumption that the need will resurface if it still exists.


Feature request: Partial run for modified files

Hi! Checking the docs I see that you can specify to run part of the tests specifying the test files or the test directories. However, it would be great if something like this could happen:
Imagine a large project in which the whole unit test suite takes various seconds to run. In this situation, it can be annoying to run the whole suite on each change. Instead, what would be great is to run only the tests related to the code that is being modified. For understanding this better let me put a project structure example:
my-project
 |-my-project
 |   |-source1.py
 |   |-source2.py
 |-tests
     |-ut
         |-test_source1.py
         |-test_source2.py

In this case, when developing, when I modify the source1 or the test_source1 I would like to only run the tests located in test_source1, not the ones in test_source2. I think that naming the tests the same name as the source files prefixed with test_ is a common practice and could help on this.
Do you think that this or a similar approach is possible? I'm open to create a PR myself if you think it is appropriate. This feature would make the development and the TDD cycle much faster 🙂

I added a PR (#78) with an early iteration of support for only running tests on modified files. Feedback appreciated!
cc @joanvila, @scimonster, @lexicality, @mrzmyr


Error when consumed by an addon and not an app

In /lib/index.js, the included hook appears to assume that the passed argument is an app.
This is true if an app is directly consuming ember-browserify. From what I can tell, if an addon is consuming ember-browserify, the passed argument has a property called app, but is not an app object itself. This causes an error on the first line of the included hook because app.options is undefined.
included: function(app){
    var enableSourcemaps = app.options.sourcemaps && app.options.sourcemaps.enabled && app.options.sourcemaps.extensions.indexOf('js') > -1;

    this.app = app;
...
}

Cannot read property 'sourcemaps' of undefined
TypeError: Cannot read property 'sourcemaps' of undefined

This is a problem in general with ember-cli addons. There is not a good API yet. See also https://github.com/ember-cli/ember-cli/issues/3718

I see. Are you opposed to a temp solution like this?
if (typeof app.import !== 'function' && app.app) {
   app = app.app;
}

Tried that locally and it works. If app.import isn't a function, the thing won't work anyways.

I think the reason why this doesn't currently work in ember-cli is because you enter in the "deps of deps" problem and currently there is no way to dedupe.  Your hack may need to do for now.

@asakusuma that seems ok to me.

Great, I will open a PR


[Bug]: KMS verifier flags don't get passed to the policy verifier

At this current moment, KMS verifier flags only apply to the KMS key reference that you supply for verifying the policy signature. When the policy is then read by Witness and used to verify attestation signatures found against the relevant subjects, these flags are ignored. This needs to be fixed as it leads to a confusing experience for the user.

To give an example, let's say I want to utilise insecureSkipVerify when connecting to the AWS KMS API:
witness verify --verifier-kms-ref=awskms:///arn:aws:kms:us-east-1:... --verifier-kms-aws-remote-verify=true --policy=./policy-signed.json
In this scenario, policy-signed.json will have its dsse envelope verified using remote kms verification against the KMS key awskms:///arn:aws:kms:us-east-1:... and with insecureSkipVerify=true in the TLS config as one would expect.
However, let's say that the contents of the policy dsse envelope looks something like:
      "name": "test",
      "attestations": [
        {
          "type": "https://witness.dev/attestations/command-run/v0.1",
          ...
      ],
      "functionaries": [
        {
          "type": "publickey",
          "publickeyid": "awskms:///arn:aws:kms:us-east-2:..."
        }
      ]
    }
  },
  "publickeys": {
    "awskms:///arn:aws:kms:us-east-2:...": {
      "keyid": "awskms:///arn:aws:kms:us-east-2:..."
    }
  }
}

in the functionaries field, there is one functionary that is expected to have signed any Witness collections from the test step.
During the policy verification flow, Witness will (naturally) make another network call to remotely verify the signature of any witness collection found for this step against the KMS key defined for the functionary (awskms:///arn:aws:kms:us-east-2:...). In this scenario, insecureSkipVerify=true will not be inherited from the --verifier-kms-aws-remote-verify=true flag call from the CLI.
This needs to be fixed so that any configuration of the KMS verifier set by CLI flags is inherited when verifying attestation signatures during the policy verification flow.
One way to work around this issue for now is to define the public key in a base64 encoded form in your policy (this is outlined in the documentation). This will also mean that any verifier of the policy will not need to be able to access the KMS key API endpoint, which could even be more optimal for certain users.


Remove feature flag for taints

Issue #, if available:
https://github.com/aws/eks-anywhere/issues/189
Description of changes:
Remove the feature flag for Taints and allow it to be free.
Testing (if applicable):
End-to-end tests for taints have been executed in various configurations.
Extensive manual testing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.7

/lgtm


Update OperationParameterProcessor.cs

ignores parameters that have custom attributes
the reason for this can be seen in issue #546

Running this code may break some scenarios because we cannot know if all parameters with custom attributes must be ignored...

Thanks for reviewing!
You are probably right about my assumption.
On the other hand as of now the code

misinterprets all custom attributed parameters as body parameters and therefore
throws an InvalidOperationException (saying that class XYZ has more than one body parameter) when a parameter with a custom attribute is used alongside another parameter with a FromBody attribute

So I can only think of one scenario where a working setup wouldn't work after my code change:
When someone created a custom attribute that derives from the FromBody attribute. I don't know if somebody did that.