Denver issues

Results 15 issues of


                                            Denver

[enhancement] Model directory under the domain directory

Thanks for the great project btw. It is really nice and neat structure, and I'm really enjoying develop project with this architecture. How would you go about putting some depth...

의존성 이슈 - bs4

안녕하세요. `import FinanceDataReader as fdr` 구문을 실행하면 아래와 같이 `No module naemd 'bs4'` 에러가 발생합니다. 저의 경우 `pip install bs4`를 사용 중인 환경에 별도로 설치해서 이 이슈를 해결했는데 제 생각엔...

Fix data type of TransformedData.fields

The real type of Transfromed.fields is `Object`, not string. Currently we cannot use official example. ```js const { ElasticsearchTransformer } = require('winston-elasticsearch'); const esTransportOpts = { transformer: (logData) => {...

Distinguish whether error is consensus error or vmError occurred during EVM execution.

During state transition, Ethereum distinguishes whether error is consensus error or vmError occurred during EVM execution. For this Ethereum developed [ExecutionResult](https://github.com/ethereum/go-ethereum/blob/fb3a6528cfa49f623570575c4fe9e8a716cfcdf7/core/state_transition.go#L82-L88). This feature looks great for improving DX(Development Experience) Because...

Story

Native Tracer and Javascript Tracer have different outputs

There are two tracers in Klaytn. * [JavaScript Call Tracer](https://github.com/klaytn/klaytn/blob/dev/node/cn/tracers/tracer.go) * [Native Go Tracer](https://github.com/klaytn/klaytn/blob/dev/blockchain/vm/internaltx_tracer.go) Currently both tracers have different outputs for same transaction. For example **LegacyTransaction** ``` > debug.traceBlockByHash("0x7df8834c7884e7b14ab0ceb831aa7214260f75f37cad36891275ee010faf5831", {tracer:...

Update SimulatedBackend to handle test cases for eth namespace APIs

As we add various eth namespace APIs for [v1.8.0](https://github.com/klaytn/klaytn/milestone/3), we need to update SimulatedBackend to make various tests for newly added `eth` namespace APIs. Most of APIs uses already implemented...

Update docs content of createAccessList

Currently [caver.rpc.klay.createAccessList](https://docs.klaytn.com/dapp/sdk/caver-js/api-references/caver.rpc/klay#caver-rpc-klay-createaccesslist) describes parameter as `callObject` which is mapped with [CallArgs](https://github.com/klaytn/klaytn/blob/dev/api/api_public_blockchain.go#L255-L263) in Klaytn. But the actual parameter is [SendTxArgs](https://github.com/klaytn/klaytn/blob/5dd7b936e002a61cb68951e333f8d498247d6e98/api/tx_args.go#L107-L135), so it looks like the content needs to be updated.

Denver