Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

EIP-1193-compliant providers #2558

Closed
szgyuszi1 opened this issue Mar 8, 2022 · 1 comment
Closed

EIP-1193-compliant providers #2558

szgyuszi1 opened this issue Mar 8, 2022 · 1 comment
Labels
error better issue indicates improvement to error messaging good first time contribution priority3 🔧

Comments

@szgyuszi1
Copy link

Ganache forking only supports EIP-1193-compliant providers. Legacy support for send is currently enabled, but will be removed in a future version without a breaking change. To remove this warning, switch to an EIP-1193 provider. This error is probably caused by an old version of Web3's HttpProvider (or ganache < v7)

how i can switch to EIP-1193 provider on terminal?

@davidmurdoch
Copy link
Member

That message should probably be removed, at least for a few years, as Web3's stable version is not currently an EIP-1193 provider (it was for a brief moment when this code was originally written) and we need to keep compatibility with web3 verisons for a long time.

@davidmurdoch davidmurdoch added error better issue indicates improvement to error messaging priority3 🔧 good first time contribution labels Mar 8, 2022
gnidan added a commit that referenced this issue Apr 8, 2022
As per #2558, remove warning about non-EIP-1193 providers
tenthirtyone added a commit that referenced this issue May 5, 2022
* feat: create version-check package

* attempt CI fix

* fix

* Add some missing colors

* small refactor

* chore(release): publish v7.0.4

ganache@7.0.4

* perf: improve performance of the persistent cache used in forking (#2811)

No change in behaviour, but makes working with local forks ever so slightly faster.

* chore: remove outdated warning about EIP-1193 fork providers (#2856)

closes #2558

* ci: automated release improvements (#2892)

* add vX.x.x tag on release

* merge master into develop after successful publish

* add action to import TrufBot GPG keys for signed commits

* squashme - VersionChecker class plated

* squashme stub unit tests

* feat: create version-check package

* attempt CI fix

* fix

* Add some missing colors

* small refactor

* squashme unit test start

* squashme semver unit tests

* squashme fetch wired up

* squashme cleaning up a bit

* comment out failing semvers

* log unit tests

* test e2e, add semver package

* snipe errant branches

* replace init race condition test with sinon spy

* fail silently if server unavailable

* final preflight before squash and PR

* add constructor and config types

* disable if in CI

* logVersionMessage for --version

* remove the disable in CI... because it actually disables in CI... for everything ::facepalm::

* add to ganache, fix versionMesage string for yargs

* add version-check back to cli

* handle invalid semver

* only setLatestSemver if valid semver

* clean up my testing changes that were accidentally committed

* bump @ganache/colors, shrinkwrap

* add clean and validate function, reduce function checks

* disable if currentVersion is not valid semver

* validate and clean semver at entry

* sparse config test

* alpha and beta, v strings

* Update src/packages/version-check/index.ts

Co-authored-by: Micaiah Reid <micaiahreid@gmail.com>

* move banner to end of CLI, before starting message

* fix session being held open after stopping in vs code

* remove scope from package.json

* fix startGanache banner log location. Add to README

* fix req.end holding a connection open that prevents starting multiple instances

Co-authored-by: Robot <robot@trufflesuite.com>
Co-authored-by: jeffsmale90 <6363749+jeffsmale90@users.noreply.github.com>
Co-authored-by: g. nicholas d'andrea <gnidan@users.noreply.github.com>
Co-authored-by: Micaiah Reid <micaiahreid@gmail.com>
Co-authored-by: tenthirtyone <alexsherbuck@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
error better issue indicates improvement to error messaging good first time contribution priority3 🔧
Projects
None yet
Development

No branches or pull requests

2 participants