GitLab

Setting that flags return all installed and installable platforms,
including installed manually by the user in their Sketchbook hardware
folder.

* Do not try to export binaries if --only-compilation-database is set

otherwise an empty "build/fqbn/..." folder is created if "always-export-binaries"
option is set via config file.

* slightly simplify function call

* [skip changelog] Add integration test
Co-authored-by: Silvano Cerza <silvanocerza@gmail.com>

* [skip changelog] Fix platform loading legacy tests

* [skip changelog] Moved local.txt files used for testing

* Fix loading of sketches with folder and main file mismatched casing

* [skip changelog] Fix legacy tests

* Fix gRPC interface function to merge configs

This fix adds the possibility to set empty values with the Merge gRPC
function, previously they would have been ignored.

Because of this change I had also to modify the GetValue() function
since it would first check if the value was set using the
Viper.InConfig() function that wouldn't check for values set with
Viper.Set().

* [skip changelog] Add clearer example to client_example

* [skip changelog] Simplified some code and enhance a test

The current release process uses git to get the tag at the current
commit. It might happen that are are multiple tags when calling that
command, in cases the rc and the final release are done on the same
commit, that would make the build process to fail.

This fixes that issue by taking only one tag.

* Compile command now works with sketches containing .pde files

* Upload command now works with sketches and builds from .pde files

* Archive command now works with sketches containing .pde files

* [skip changelog] Add test to verify debug command works with pde sketches

* Fix lib examples not showing sketches with .pde files

* [skip changelog] Remove duplicated code and enhance tests

* Always report buildpath (even in case of build failed)

* Always write a correct compilation database

Even if the Contents field is empty.

* Skip dependency detection if library is fully precompiled

Precompiled bits of a library should not depend on any link time dependency (we cannot assure ABI stability).
Fixes https://github.com/arduino/ArduinoCore-mbed/issues/119

* Add output when skipping deps detection for precompiled libs
Co-authored-by: Silvano Cerza <silvanocerza@gmail.com>

* [skip changelog] Ditch goreleaser in favor of a new release process

* [skip changelog] Fix version output test

* [skip changelog] Fix some workflows issues

* [skip changelog] Fix panic when running integration tests

* [skip changelog] Remove extra chars from package name prefix

* Fix lib list --all not returning library includes in json output

* [skip changelog] Enhance integration test

* Add gRPC interface function to write settings to file

* Add example of gRPC config write

Previously installing from a zip file would extract the content directly
into the user library folder, this could have caused problem if the zip
file wasn't structured correctly.

To handle this we now extract to a temp directory to verify that the zip
is structured correctly and to infer the name of the library being
installed. If everything is fine we then copy it over to the user
library folder to finalize the installation.

Installing from a git repository has been enhanced too, after
cloning the repository to the user library folder we delete the .git
folder to make it a plain folder. Cloning should be faster too since we
now clone using depth of one commit to avoid downloading useless files.

Both when installing from a zip file or from a git repository we delete
the installed library folder if one with the same name is already
installed.

* Fix lib install with git url

* Better git url handling

* Precompiled libraries: only select a folder if it contains files

* Restore precompiled tests

* slightly refactored directoryContainsFile function

* [skip changelog] Fix compile tests

* [skip changelog] Fix compile test
Co-authored-by: Cristian Maglie <c.maglie@arduino.cc>
Co-authored-by: Silvano Cerza <silvanocerza@gmail.com>

Previously overwriting a file will not truncate it, so if the download
size was less than the file size already on disk then the resulting file
will end up with a "corrupted" piece at the end.

* Don't archive preexisting archives if commandline is too long

Fixes https://github.com/arduino-libraries/ArduinoIoTCloud/runs/1693000682?check_suite_focus=true#step:7:277
Should revert https://github.com/arduino-libraries/ArduinoIoTCloud/pull/222

* Added test
Co-authored-by: Cristian Maglie <c.maglie@arduino.cc>

The terms "cache" and "clean" might bring compilation to mind, but the `arduino-cli cache clean` command has nothing to
do with compilation. Many users will likely not even be aware of the existence or purpose of the `directories.downloads`
folder. For this reason, it's important to make the purpose of this command clear.

Previously, the Arduino library specification required the library.properties `name` field value to start with a letter.
Before Arduino IDE 1.8.4, library folder names starting with a number were not supported. Because the library folder for
Library Manager installations is named according to the library.properties name value, it was necessary to apply the
same restriction to the name value. It was determined that enough time has passed since the Arduino IDE 1.8.4 release to
reflect this change in the Arduino library specification.

Previously the name of the specification was "package_index.json specification". Only the primary official package index
is allowed to be named package_index.json, but this specification applies to all package indexes. So "Arduino package
index specification" (shortened to "Package index specification" in the documentation navigaion pane) is less likely to
cause confusion and also easier to remember and talk about.

This feature allows to selectively "override" the content of a sketch.
Overridden files will not be read from disk as usual but fetched directly
from gRPC paramaters (if the cli is running as daemon) or from a .json
file containing the new source code (if running from command line).

For example if we have bossac 1.7.1 and 1.9.0 installed, this will
result in the following properties available during upload:

{runtime.tools.bossac-1.7.0-arduino3.path} => /path/to/bossac/1.7.0
{runtime.tools.bossac-1.9.0-arduino3.path} => /path/to/bossac/1.9.0
{runtime.tools.bossac.path} => /path/to/bossac/1.9.0

some platforms fails to correctly specify the version of the tool in the
package_index.json but they do the correct specification in the recipes.
This patch allows to not fail in this latter case.

Fix #1040