GitLab

This commit should be equivalent, no semantic changes just simplified
the notation.

This is accomplished by updating go-properties-orderedmap with this fix:
https://github.com/arduino/go-properties-orderedmap/commit/05018b28ff6c9492102947be131fd396d74c772e

* make the serial discovery execution atomic

* increase timeout to 10s

* lower debug level

* make the gRPC client a runnable go program again

* say in the readme the the folder exists

* break license preamble

* change the logging setup

* proper handle colors in logs

* use feedback API instead of formatter

* removed unused formatter

* add PrintJSON to the feedback api

* add newline to messages

* remove JSONOrElse

* fix config dump json format

* re-add table in a dedicated package

* do not pollute stdout when json format is selected

* restore output format, make --names work with json too

* fix integration tests

* move output format decision outside command

* port drone to gh actions

Fixes #126

This increase backward compatibility with arduino_builder

The last loop collecting the remaining objectFiles may be run before the
last jobs completes.
This commit replaces the two channels used to fill objectFiles and to
signal error with direct variable access guarded by mutex, this avoids
race conditions at the end and streamlines the whole process.

Also added a 'queue' channel to feed the goroutines, this is not strictly
part of the fix, but helps to fairly distribute the workload.

The issue was due to the peculiar way concurrency and parallelism are handled in go.
We used to set GOMAXPROC to 1 to avoid parallelizing the WaitGroup execution.
This would work, in theory, unless the goroutines sleep.
In that case, another goroutine is allowed to start concurrently (only 1 goroutine running in parallel, so GOMAXPROC is happy).
Since our goroutines sleep (wait) after calling gcc, another task is started, without any hard limit, till the WaitGroup is completely spawned.
On systems with limited resources (as RaspberryPi) and cores with lots of files this can trigger an out of memory condition.

* Add an optional upload step in compile (CLI-35)

* Add few integration tests for compile command

* deprecate latest links

* Update README.md
Co-Authored-By: per1234 <accounts@perglass.com>

* rephrase

* do not hit github api to get latest version

* don't use PCRE

The Raspberry Pi presents itself as an `armv7l` architecture and with this mapping the install script is will download the most appropriate archive for this platform.

* do not expect binary artifacts when preprocess or show-properties

* remove noisy line

* query the backend to get the fqbn

* Update commands/board/list.go
Co-Authored-By: Maurizio Branca <m.branca@arduino.cc>

There is nothing left to do after preprocessing.

It should print ctx.Source.

Also removed the command PrintPreprocessedSource to furhter reduce
boilerplate.

* Upgrade protobuf to v3.9.1 for AppVeyor

We can now switch back to a current version of the protocol since the
PR https://github.com/protocolbuffers/protobuf/pull/5044 has been
merged to master a released.

* Bump drone.io Docker image from 1.0 to 1.1 (#329)

Now we can have the same version on both drone.io and AppVeyor, see PR #329 for the details.

* add install script

* update install instructions

* Update install.sh
Co-Authored-By: Maurizio Branca <m.branca@arduino.cc>

* Update install.sh
Co-Authored-By: per1234 <accounts@perglass.com>

* Update README.md
Co-Authored-By: per1234 <accounts@perglass.com>

* add nightly pipeline

* change trigger to "nightly" tag push instead of cron that is not supported in drone.io SAAS

* clean trigger config

* add exclude filter for nightly in the release pipeline

* remove dist prefix form s3 push key

* add build date to snapshot name template

* exclude goreleaser generated config.yml

* exclude goreleaser generated config.yml hardcoding path

* update checksum template with tag and date prefix

* add Appveyor badge

* update link

* add --additional-urls flag

* add testdata

* add core search test

* no need to pass around the whole request object

* always show available versions on list

* refactor libraries API, let upgrade single libraries

* fixed examples

* forgot

- used blob configuration instead of deprecated s3 one. this requires
adding a AWS_DEFAULT_REGION env var to the drone step (toghether with
the IAM credentials), because this
property is missing in the blob config