evm | Emacs Version Manager | Code Editor library

From the comments, you seem to be using some less common libraries. Sometimes, those kinds of libraries are not updated to be compatible with the Java Platform Module System. I think it is probably safe to assume that unless you know otherwise.

Defining a non-modular project

The easiest way to deal with such dependencies is to make your project non-modular: delete the module-info.java.

But JavaFX itself is only supported as modules. So, even though your project and its dependencies are non-modular, you should still place the JavaFX libraries on the module path.

Using a JDK which includes JavaFX

To accomplish such a setup (non-modular application using JavaFX modules), the easiest way is to rely on a JDK or JRE that includes JavaFX modules, for example, the Zulu JDK FX distribution or the Liberica Full JDK distribution. It is important to use the correct distribution as the base JDK distributions for Zulu and Liberica do not include JavaFX.

Using a base JDK which does not include JavaFX

With a bit more work, you can use OpenJDK. You can do this by sourcing the JavaFX modules from either the maven repository with a build tool, or a manual download of the modules and SDK from Gluon. In all your build and execution steps, you need to ensure that all of those modules are on the module path and declared to the module system via either VM arguments or a module-info.java.

Building with Maven

For a Maven build, you need to add each module to the module path individually, as they are all in separate directories in the local .m2 repository (modern Maven systems and some IDEs, such as Idea, will do that automatically, other IDEs such as VSCode may not).

Building with the SDK

Alternately, don't add dependencies on the JavaFX modules via Maven. Instead, download the JavaFX SDK and add the JavaFX modules there via VM arguments --module-path and --add-modules. This process for adding JavaFX modules to OpenJDK is documented in the getting started documentation at openjfx.io.

A note on openjfx.io Maven archetypes

Note that the openjfx.io getting started documentation around this mentions maven archetypes. My advice is not to use those as they are really difficult to work with if you try to use them from IDEs. Instead, use the Idea new JavaFX project wizard, either keeping the module-info.java it generates for a modular project or removing it and manually specifying JavaFX module VM arguments for a non-modular project.

Issues with your project build

In terms of your actual project, I encountered the same error that duffymo pointed out in the comments:

I can't resolve all the dependencies for web3jm-evm from Maven Central. It's pulling in a bunch of JARs from org.hyperledger.besu that aren't in Maven Central.

So I was unable to build or test it.

I recreated (DROP -> CREATE) the PostgreSQL database because prior to adding a new chain within chainlink, it was initially configured to another chain/network id, which seemingly threw these errors.

Call Number.MAX_SAFE_INTEGER and you will find max safe integer value. If you go out of this range, math becomes tricky and you probably won't be happy with results.

Your math must stay in the range of max safe integer to have good results.

Read more here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER

You may explore BigInt but it has it's own caveats just like float point numbers.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt

Read more here: https://www.smashingmagazine.com/2019/07/essential-guide-javascript-newest-data-type-bigint/#the-problem

If you found it useful, please consider upvoting/accepting

Had this issue myself, apparently it's some sort of Ganache CLI error but the simplest fix I could find was to change the network id in Ganache through settings>server to 1337. It restarts the session so you'd then need to change the address and private key variable.

If it's the same tutorial I'm doing, you're likely to come unstuck after this... the code for transaction should be:

find the line "language: Solidity". Please change this to "language": "Solidity". Python recognizes this as a set, not a dictionary.

i had the same issue. i had this compiler setting:

in compile.js

The LOG opcodes are used for emitting event logs.

The value depends on the number of indexed and non-indexed topics of the event. Since the value is limited (currently at 4), there's also a limit of max indexed topics per each event definition (currently 3, so it's possible to process unindexed topics of the same event as well).

Example in Solidity: