5 Commits (714fb302a5f1c19dc2fc3973d01210f4e2624a91)

Author	SHA1	Message	Date
Sina Mahmoodi	6135c688b8	eth/tracers: optimize goja buffer conversion (#25156) ... This changes the []byte <-> Uint8Array conversion to use an ArrayBuffer, avoiding inefficient copying of the slice data in Goja. Co-authored-by: Felix Lange <fjl@twurst.com>	2 years ago
Felix Lange	9244d5cd61	all: update license headers and AUTHORS from git history (#24947)	2 years ago
Sina Mahmoodi	ba47d800b1	eth/tracers/js: drop duktape engine (#24934) ... #23773 added a JS tracer which uses Goja as its engine. In this PR I remove the previous tracer which used duktape as well as remove the dependencies. This PR also comes with 2 fixes in the Goja tracer and one small behavioural change: I had handled errors in the native Go functions by panicing. My oversight was that Goja only handles panics with a Goja.Value as argument. The difference is panic(goja.Value) allows JS to catch the exception whereas Interrupt(error) doesn't. There was a race in how I handled Stop. Because of 1. some of the methods that simply return nil on error (like memory.slice) now throw an exception.	2 years ago
Eduard S	310f751639	eth/tracers/js: add memory.length method (#24887)	3 years ago
Sina Mahmoodi	bf693228a3	eth/tracers/js: goja tracer (#23773) ... This adds a JS tracer runtime environment based on the Goja VM. The new runtime replaces the duktape runtime, which will be removed soon. Goja is implemented in Go and is faster for cases where the Go <-> JS transition overhead dominates overall performance. It is faster because duktape is written in C, and the transition cost includes the cost of using cgo. Another reason for using Goja is that go-duktape is not maintained anymore. We expect the performace of JS tracing to be at least as good or better with this change.	3 years ago