Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update main for v2.0.x #616

Merged
merged 204 commits into from
Jan 31, 2025
Merged

Update main for v2.0.x #616

merged 204 commits into from
Jan 31, 2025

Conversation

adrianstevens
Copy link
Contributor

No description provided.

ctacke and others added 30 commits March 27, 2024 17:23
bug fix for reading large files. bug fix for no local file name
fix id parameter in generated provisioning command
Remove Themes from Serilog output, so it works in both light and dark…
On some systems where the ILLinker fails to trim, the CLI trim command was hanging.

This was caused because stderror was redirected but we never began reading from it.  We can't just `ReadToEndAsync()` on stderror because then we get a hang because of stdout.  So in order to work around this, use the `OutputDataReceived` and `ErrorDataReceived` functions to reading, and used `BeginErrorReadLine()` and `BeginOutputReadLine()` to execute reading of the buffers.

While this fixed the hang, it immediately claimed that trimming was successful even though the process failed with a non-zero exit code. There were two reasons for this:

1. Any exception in `ILLinker.RunILLink()` gets read by `MeadowLinker.TrimMeadowApp()`'s catch statement and then disregarded, and no error code or anything else bubbles up
2. The `_logger?.LogError()` call doesn't execute because `_logger` is null, thus no output is ever seen (anywhere in the app really).

So to fix these two issues I made `MeadowLinker.TrimMeadowApp()` bubble up the exception.  This not only allows us to exit the cli for the IL Link failure (and not consider it a success), but it also shows the user ILLink output so they can diagnose the failure.
Fix trim hanging and incorrect status results.
Validate firmware before running or trimming + minor cleanup
Updated cloud package command to include non-assembly files + cleanup
Refactor nuget references
Add subfolder reading, writing, deleting and deployment
Fix file and folder sanitization for file-related commands
ctacke and others added 29 commits December 24, 2024 09:28
* Do not turn off 'aggressive' prematurely, before the Meadow is known to re-connect.
Update Newtonsoft.Json
Remove CLI v1 code. remove old scripts, move CLI v2 to source folder
support device config read and write
@adrianstevens adrianstevens merged commit 80cb122 into main Jan 31, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants