-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Change burn
task to Upgrade by default
#682
Open
jjcarstens
wants to merge
1
commit into
main
Choose a base branch
from
mix-burn-upgrade
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
defmodule Mix.Nerves.FwupStream do | ||
@moduledoc """ | ||
IO Stream for Fwup | ||
|
||
This functions the same as IO.Stream to push fwup IO to stdio, but | ||
it also captures the IO for cases where you want to check the | ||
output programatically as well. | ||
""" | ||
|
||
defstruct device: :standard_io, line_or_bytes: :line, raw: true, output: "" | ||
|
||
def new(), do: %__MODULE__{} | ||
|
||
defimpl Collectable do | ||
def into(%{output: output} = stream) do | ||
{[output], collect(stream)} | ||
end | ||
|
||
defp collect(%{device: device, raw: raw} = stream) do | ||
fn | ||
acc, {:cont, x} -> | ||
case raw do | ||
true -> IO.binwrite(device, x) | ||
false -> IO.write(device, x) | ||
end | ||
|
||
[acc | x] | ||
|
||
acc, _ -> | ||
%{stream | output: IO.iodata_to_binary(acc)} | ||
end | ||
end | ||
end | ||
end |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This messages comes from whatever the user puts in their
fwup.config
, so it seems fragile. Does this work with a FAT-formatted MicroSD card? Like one that you get fresh from a store?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, didn't think about that. I will try with a fresh card shortly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am getting the same message on a newly FAT formatted microSD and USB drive.
I'm wondering if they change here is to not be automatic and just prompt again asking for a confirmation to run the
complete
task? Or...we just always run complete if theupgrade
task fails?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically, even the task can be defined by the user as well and there may not even be an
upgrade
orcomplete
task. Maybe this is considered a pure convenience and the only support for this "auto" work is with what's defined in official systems which all have this message and these tasks?