GitLab

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

* use crossbuild as base image

* add drone step

* add how to contribute

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

* add convention to func names

* move sketch copy ops out of legacy into new API

* removed dead code

* sync board list to avoid race conditions

* properly unlock mutex

* added a monitor service

* added generic monitor type and its serial impl

* added monitor service implementation

* gracefully handle connection errors

* more idiomatic definition

* keep directory structure from the archive

* move default value closer to the function using it

* test the serial monitor

* bump monkey

This patch falls back to the `BoardsManifest` when the `Boards` is not
available.

When the `Boards` are not installed, hence unavailable, the produced
gRPC instance won't contain the `FQBN` but the `Name` only.
Signed-off-by: Akos Kitta <kittaakos@typefox.io>

* removed unused file

* make Arduino15 the default data dir on OSX

* skip tests we cannot run on Drone

* convert to bool before returning

* updated README.md download links with linuxarm32 and linuxarm64 links

* Updated binary usage instructions, from now on the binary inside the archive is always named `arduino-cli`

* Add ctags tool config to add support for arm64

The cli automatically downloads this tool during its initial
configuration step The ctags tool provided by Arduino was missing for
download, causing the cli to breaks with a `downloading
builtin:ctags@5.8-arduino11 tool: tool not available for your OS` error.
This commit fixes the error defining pointers to Arduino downloads server

* updated macosx ctags package flavour metadata to download 64bit os tool version