Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

web3.eth.Contract.getPastEvents doesn't support "allEvents" anymore #2316

Closed
mistersandman opened this issue Feb 3, 2019 · 0 comments · Fixed by #2332
Closed

web3.eth.Contract.getPastEvents doesn't support "allEvents" anymore #2316

mistersandman opened this issue Feb 3, 2019 · 0 comments · Fixed by #2332
Labels
Bug Addressing a bug In Progress Currently being worked on

Comments

@mistersandman
Copy link

mistersandman commented Feb 3, 2019

Expected behavior

Using "allEvents" as event name in web3.eth.Contract.getPastEvents should be accepted and return all events matching the specified options according to the docs.

Actual behavior

An exception "Error: Event with name "allEvents" does not exists." is thrown.

Steps to reproduce the behavior

Call getPastEvents on a contract with the first argument (event name) set to "allEvents".

Error Logs

Error: Event with name "allEvents" does not exists.
    at _callee$ (h:\****\node_modules\web3-eth-contract\dist\web3-eth-contract.cjs.js:959:28)
    at tryCatch (h:\****\node_modules\regenerator-runtime\runtime.js:62:40)
    at Generator.invoke [as _invoke] (h:\****\node_modules\regenerator-runtime\runtime.js:288:22)
    at Generator.prototype.(anonymous function) [as next] (h:\****\node_modules\regenerator-runtime\runtime.js:114:21)
    at asyncGeneratorStep (h:\****\node_modules\@babel\runtime\helpers\asyncToGenerator.js:3:24)
    at _next (h:\****\node_modules\@babel\runtime\helpers\asyncToGenerator.js:25:9)
    at h:\****\node_modules\@babel\runtime\helpers\asyncToGenerator.js:32:7
    at Promise (<anonymous>)
    at h:\****\node_modules\@babel\runtime\helpers\asyncToGenerator.js:21:12
    at h:\****\node_modules\web3-eth-contract\dist\web3-eth-contract.cjs.js:978:23
    at Promise (<anonymous>)
    at AbstractContract.getPastEvents (h:\****\node_modules\web3-eth-contract\dist\web3-eth-contract.cjs.js:949:14)

Versions

Observed on Windows 10 with NodeJS v8.1.2 using [email protected].
This used to work on the same setup with [email protected].

@nivida nivida added Bug Addressing a bug In Progress Currently being worked on labels Feb 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Addressing a bug In Progress Currently being worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants