Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Utilities Failing to Import through Spring Tool Suite

See original GitHub issue

Description

As a Core Developer Apprentice for the Ethereum Foundation, I’m using the Teku build as reference in order to build a prototype for the Altair Minimal Light Client (https://github.com/jeyakatsa/Altair----Minimal-Light-Client-Prototype). Yet, I’m having issues in regards to the utilities needed to be imported in order for the packages (and classes/interfaces within the build) to be error free…

Steps to Reproduce (Bug)

Git Pull Teku folder into OS
Open Spring Tool Suite 4
Go to [File] -> [Open Projects From File System] and choose Teku folder from files

Expected behavior: No Errors packages, classes and interfaces

Actual behavior: Errors on all packages, classes and interfaces.

Image Reference Teku Build Import Utility Issues

Frequency: All the time

Versions

Software version: [Unsure... Forked and Pulled the Teku Repo on Wednesday 9/29/21.]
Java version: [jdk-15.0.1.9-hotspot]
OS Name & Version: [Windows 10]
Virtual Machine software & version: [Spring Tool Suite 4, Version: 4.7, Release: 2020]

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

ajsuttoncommented, Oct 4, 2021

I’m not at all familiar with spring tools suite but it looks like it’s built on Eclipse. It looks like Eclipse is having issues again because it doesn’t separate test, test support and production code trees in the same way gradle does so it hits a dependency cycle where gradle and IntelliJ have no issues.

Eclipse isn’t giving me very useful error messages to point out where it thinks the cycle is either unfortunately. We’ll have to do some further analysis to work it out and then how to restructure things to make Eclipse happy.

1reaction

rolfyonecommented, Oct 4, 2021

Thanks for raising. I’m assuming that you’re importing the rest api definition?

There’s been a couple of reports of specific issues due to automated importing of the rest api, and previously I’ve suggested importing the standard api which is written by hand… The standard api can be found here. Admittedly ‘teku specific’ api’s are missing from that definition, but all of the key api’s are defined : https://ethereum.github.io/beacon-APIs/

Last time I checked it was difficult to fix due to external dependencies of several libraries, I’ll schedule some time to see if it’s in a state to attempt to resolve yet…