ubiquiti.hexpat? #145
Merged
ubiquiti.hexpat? #145
Conversation
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
|
Hi, thanks a lot! If you can make a smaller test file that would be great, thank you! |
+ Renamed fields in partition struct
|
Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I wrote a pattern file for Ubiquiti firmwares. Do we need such a pattern or firmware patterns in general? Firmware can be downloaded without any authorization from https://fw-update.ubnt.com/api/firmware, so test files may be added as well.
Since those firmware files are not smaller than ~4Mb, I can try to create a custom crafted file with some stubbed entries that can be used for unit testing.