Testers needed for the new Sloeber version

[jantje]

I've been working over a year now on a new Sloeber version. Though it looks pretty much the same there have been a huge number of changes under the cover.
I can run unit tests for lots of functionality but there are holes in the unit tests and user interface is hard to test.
Therefore I would like experienced users to jump in and test the new Sloeber.
I prefer experienced user who know what to expect from Sloeber.
Please reply below if you want to help out testing.

[ArminJo]

Hi Jaintje,
Thanks for giving us the Sloeber plugin 🥇 !!!
I would like to contribute and are willing to test the new version.
Best regards
Armin

[jantje]

An update.
I finally have sloeber working and issue #1126 solved.
That means testing can be done but I would to see more helping hands and #1625 fixed.
#1625 is important as I have missed many changes in the arduino framework so all the new stuff is likely to fail.

If you are not used to installing Sloeber from the actions feel free to get the "nightly" and start it to see how far you get. That is basically the first thing to test.

I propose to create issue with the name V5.0 testing
The main aim of the testing is to see everything still works from the gui perspective. Lots of stuff is tested with JUnit tests but that does not guarantee the GUI works.
Note that Version 5 is incompatible with the previous versions.
That means the configuration files created by Sloeber (and CDT in a way as I rewrote managedbuild that is part of CDT) are named different and/or have a different content.
The default behavior is also different.
Code is now (by default you can change it when creating a project) in the src folder and not in the root.
The build result is (by default you can change it in the project properties) in bin/${configName}
The default builder is the internal builder (no make required) but for some functionality (like burning the bootloader) make is still used. But that should be seamless from a user perspective.
Sloeber now adds the include directives automagically to the build commands.
At this point in time (I still need to find a way to do this better) the discovery will always open a command window.

Please join the testing and thanks for helping out.

[jantje]

Also changed
Better support for configuration changes.
The arduino folder now is arduino${configName}
That means that the libraries and cores remain available when switching configurations.

[ArminJo]

I istalled Sloever 4.4.3, ran check for updates, and restarted sloeber.
Then I added http://eclipse.baeyens.it/update/V4/nightly to Available Software sites checked it and ran check for updates again.
The only update I saw was Nebula Oscilloscope Widget 1.4.0.202406291220 , which throws the error:

An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Can't download artifact osgi.bundle,org.eclipse.nebula.widgets.oscilloscope,1.4.0.202406291220 required by org.eclipse.nebula.widgets.oscilloscope[1.4.0.202406291220], org.eclipse.jetty.logging[12.0.9], org.eclipse.nebula.widgets.oscilloscope.feature.feature.group[1.4.0.202406291220], org.eclipse.nebula.widgets.oscilloscope[1.4.0.202406291220] from any of the following repositories: 
file:/E:/Sloeber5/p2/org.eclipse.equinox.p2.core/cache/
file:/E:/Sloeber5/configuration/org.eclipse.osgi/550/data/listener_1925729951/
file:/E:/Sloeber5/.eclipseextension
file:/E:/Sloeber5/
https://download.eclipse.org/tools/cdt/releases/latest
https://download.eclipse.org/releases/latest/
https://download.eclipse.org/justj/jres/17/updates/release/latest/
https://download.eclipse.org/nebula/releases/latest/
https://eclipse.baeyens.it/update/V4/stable/
http://eclipse.baeyens.it/update/V4/nightly
https://download.eclipse.org/eclipse/updates/latest
Can't download artifact osgi.bundle,org.eclipse.nebula.widgets.oscilloscope.source,1.4.0.202406291220 required by org.eclipse.nebula.widgets.oscilloscope.source[1.4.0.202406291220], org.eclipse.nebula.widgets.oscilloscope.feature.feature.group[1.4.0.202406291220], org.eclipse.nebula.widgets.oscilloscope.source[1.4.0.202406291220] from any of the following repositories: 
file:/E:/Sloeber5/p2/org.eclipse.equinox.p2.core/cache/
file:/E:/Sloeber5/configuration/org.eclipse.osgi/550/data/listener_1925729951/
file:/E:/Sloeber5/.eclipseextension
file:/E:/Sloeber5/
https://download.eclipse.org/tools/cdt/releases/latest
https://download.eclipse.org/releases/latest/
https://download.eclipse.org/justj/jres/17/updates/release/latest/
https://download.eclipse.org/nebula/releases/latest/
https://eclipse.baeyens.it/update/V4/stable/
http://eclipse.baeyens.it/update/V4/nightly
https://download.eclipse.org/eclipse/updates/latest
Can't download artifact org.eclipse.update.feature,org.eclipse.nebula.widgets.oscilloscope.feature,1.4.0.202406291220 required by org.eclipse.nebula.widgets.oscilloscope.feature.feature.jar[1.4.0.202406291220], org.eclipse.nebula.widgets.oscilloscope.feature.feature.jar[1.4.0.202406291220], org.eclipse.nebula.widgets.oscilloscope.feature.feature.group[1.4.0.202406291220] from any of the following repositories: 
file:/E:/Sloeber5/p2/org.eclipse.equinox.p2.core/cache/
file:/E:/Sloeber5/configuration/org.eclipse.osgi/550/data/listener_1925729951/
file:/E:/Sloeber5/.eclipseextension
file:/E:/Sloeber5/
https://download.eclipse.org/tools/cdt/releases/latest
https://download.eclipse.org/releases/latest/
https://download.eclipse.org/justj/jres/17/updates/release/latest/
https://download.eclipse.org/nebula/releases/latest/
https://eclipse.baeyens.it/update/V4/stable/
http://eclipse.baeyens.it/update/V4/nightly
https://download.eclipse.org/eclipse/updates/latest

This is the installed version:
Nebula Oscilloscope Widget 1.4.0.202402011804 org.eclipse.nebula.widgets.oscilloscope.feature.feature.group Eclipse Nebula

And I saw no new sloeber packages / version.
This is the Version installed:
sloeber 4.4.3.202402080117 io.sloeber.product null

Do I have the 5.0 version now?

[jantje]

You do not have Sloeber 5.0.
You can not install sloeber 5.0 with the nightly.
I'll create a discussion on how to install "the nightly" and link it here once I've done that.
Note there are some build issues (weird things I can not reproduce locally) I hope to get fixed soon; until then all reported V5 issues remain unfixed in the nightly build.

[jantje]

Seems the build issues have magically disappear.
V5 is up and running again.

[jantje]

Here is how to install the "V5/nightly/actions" build #1663

[jantje]

UPDATE:
I'm working on the migration code and I would like to get some projects to test.
Preferably "complicated projects" like with multiple configurations and compile options.
Note: only provide publicly available code
In your woirkspace rightclick the project you want to "donate" and select export->general->Archive file ....

[ArminJo]

An ESP32 project.
https://www.dropbox.com/scl/fi/1ij16fxylshcn1btl2pcp/IRremote_ESP32.zip?rlkey=450ka1p3uqu90eyzb7ps1dw5m&dl=0

[jantje]

I tried to upgrade the project and the result did not build.
So I tired to import it into Sloeber V4 and after plenty of issues I came to the conclusion I hit the same problem in Sloeber V4.
This is the board and the error I get

The IR remote library I used is 4.4.0

FYI It seems to me this is a project to test the library (examples)? on multiple boards. In my book it is way easier to do so with a test script.

[ArminJo]

Sorry, this project was for testing the new 4.4.1 version, which is released now.
I use gihub actions for CI testing, but in case of error or ESP32 development, I require this Sloeber project.

[jantje]

No need for sorry
I'll try the new 4.4.1 version

[jantje]

Update: I've been distracted by stuff in the real world demanding my attention. Then I got ill and I'm still recovering. My brain functionality is still lower than usual making it hard to code.
Still the "convert to sloeber project" works (probably plenty of bugs but for simple projects it works)
Stuff I decided not to support is the "exclude from build" as it is to hard to identify the exclusions.
What should work:
1)the board is identified and used (if it exist in the new install)
2)Support for multiple configs

[jantje]

Another update.
Having had multiple problems with ESP32 and other weird things I think I finally think nailed it.
I also added support for libraries in the convert to Sloeber project.
It should be available to you if the latest action is successfully build.
Left to do:
1)Fix reported bugs
2)update the visuals from V4 beryllium to V5 boron.

[TrippyLighting]

I am not really qualified enough to be a tester, but I downloaded and installed V5 on my 2017 Intel MacBook Pro anyway.
Do I just post an issue, or what's the best way to report "findings" for V5?

[jantje]

I am not really qualified enough to be a tester

In my book you are very qualified.
I do lots of testing based on scripts but that does not represent the user experience.
For instance: Though all test are successful I noticed that when creating a project in a new Sloeber install the project was created wit "no file" instead of "ino file". This results in a bad user experience as default should work. (I still need to fix this)
As you have lots of experience with Sloeber and know "how it used to work" you can easily notice different behavior. Whenb the different behavior is not due to fixed stuff it is regression and a potential issue.
Also you have a mac :-)

Do I just post an issue, or what's the best way to report "findings" for V5?

I propose to create issue with the name V5.0 testing

[JWindy]

Hey Jantje,

first and for all thank you so much for all your effort. I haven been using Sloeber about five years ago and was very happy to get proper IDE functionalty byond the Arduino IDE but without missing out on all the benefits of the Arduino framework. Now it's time for another project, which will run on an esp32 and which moste likely will keep me bussy for a few months. I setup V4 a week ago and I'm impressed, how much has been improved and how little I had to configure. I might be slightly late, but I'll gladly give V5 a try and share found issues:D

Since I haven't been working with Sloeber lately, it might make sense to run V5 as well as V4 in parallel to see if an issue is a bug or just a problem caused by the user :D You wrote above "that Version 5 is incompatible with the previous versions.". I assume this is for sure the config files, whiche are stored in .metadata, so I should create a new folder for V5. There seem to be also changes on the project files itself. E.g. source files in source folder. Can I work with V4 and V5 on the same project-folder? I assume the answer is no. Can I migrate the V4 projects to V5? Worst case would be to create another Workspace, copy the source file and use the "Convert to Sloeber project" function. If I have to go back to V4, I'll do this quick and dirty somewhere outside my tidy workspace:D

Johannes

[jantje]

First of all thanks for testing.
I think I fixed all reported issue and I would like to release V5.
Anyone thinks there are still open issues please point them out to me.

[ArminJo]

Hi Jaintje,
Thanks for your effort!

If I do Window > Perspective >reset the C/C++ Perspective in Beryllium I have this (customize Perspective menu entry)

In Boron I have this

Both have the same Eclipse base (latest updates all installed except Nebula widget).
And therefore configurations are not available in Boron 😢.

[jantje]

I have the following in boron in a fresh install

And therefore configurations are not available in Boron

This is only the selection of availability of action sets in the gui for the default C/C++ perspective. IMHO "configurations are not available in Boron" is therefore not correct.
To me it looks like you should be able to simply activate the action set.

Can you check the oomph preferences?

In the product oomph is 100% disabled/removed (so you can not find the preferences).

[ArminJo]

I have no oomph preferences available in my boron.
How do I make a fresh install? Just CDT and Repository.zip, or 4.4.3 and Repository.zip?

[ArminJo]

I fresh install (CDT + Repository.zip) fixed at least this problem.

[jantje]

A fresh install is taking the zip/tar (available in actions for testing or nightly) of your platform and uncompressing it.

I have no oomph preferences available in my boron.

good.

[ArminJo]

If I open an existing 4.4 project the platform folder settings are lost, but still in .sproject.
Instead the last platform choosen on another project before the update is always selected.
If I set the platform and board, then I get

**** Build of configuration _ReceiveDemo for project IRremote_Leonardo ****
Nothing to build for project IRremote_Leonardo

even after "clean project".

[jantje]

If I open an existing 4.4 project

You need to do a convert to sloeber project

[ArminJo]

You need to do a convert to sloeber project

How do I do it? manually?

[jantje]

yes. file->new->other->sloeber->convert to Sloeber project

[ArminJo]

After converting a multi configuration project, all 3 cpp are enabled.
After removing the old libraries directory manually and disabling 2 of the cpp with "resouce Configuration" > "Exclude from Build" it worked.

And the old entry Config._ReceiveDemo.compile.sloeber.size.type=ARDUINO_WAY is "converted" to _ReceiveDemo.extension.sloeber.size.type=RAW_RESULT.

I know, programming the converting sucks and is tedious, but this also holds for me, doing it manually for all my projects. Its a dilemma.

But at least, it works and starting ESP32 compilation is way faster than with 4.4.3 😀
T H A N K S

[jantje]

Converting the size command seemed hardert than one would expect.
Anyway the newest version "should do it".
Still testing needed.
Defaults to Arduino way.

[darek-i-rafal-i-zbychu]

I installed Sloeber 5 and plugins. Compilation works fine, but there is a problem with transferring files to the microcontroller.
The incorrect programmer is entered, because it should be "jtag2updi". The correct programmer is entered in the configuration. I have recently noticed that errors appear in the interpretation of data set by the user. Especially in the avrdude command line for sending data to the microcontroller.

Starting upload
Uploading project "Tiny816Blink" with "avrdude"

Launching: D:\Progel\Sloeber5_1\arduinoPlugin\packages\arduino\tools\avrdude\6.3.0-arduino17/bin/avrdude -CC:\Users\US3\Documents\Arduino\hardware\megaTinyCore2\megaavr/avrdude.conf -pattiny816 -cstk500v1 -PCOM5 -b19200 -Uflash:w:D:\Progel\Sloeber5_1\Projekty\Tiny816Blink\bin\Release/Tiny816Blink.hex:i
Output:
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x03
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x03
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x03
avrdude: stk500_recv(): programmer is not responding