Workaround for unintentional reset on UpdateConfiguration#362
Workaround for unintentional reset on UpdateConfiguration#362josesimoes merged 1 commit intonanoframework:mainfrom
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@muenchris I've fixed the checklist for you. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Looking at this makes me think that the root cause should be in the native code when it's executing the UpdateConfig. Some wrong pointer or check or... I guess this will surface again when there is a call to it because of other config change that calls it... |
|
@muenchris thank you again for your contribution! 🙏😄 .NET nanoFramework is all about community involvement, and no contribution is too small. Please edit it and add an entry with your GitHub username in the appropriate location (names are sorted alphabetically): (Feel free to adjust your name if it's not correct) |
Yes, I think so, too, because the System.Net code has not changed since fw 1.12.xx. There might be more "broken" in the native code as reported in issue #1692 |
…)" This reverts commit 1c1908d.
Description
Motivation and Context
How Has This Been Tested?
Screenshots
Types of changes
Checklist: