forked from project-chip/connectedhomeip
-
Notifications
You must be signed in to change notification settings - Fork 0
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
V1.1 branch mvd master dev cherry pick from 1.0 #13
Closed
erwinpan1
wants to merge
11
commits into
v1.1-branch-mvd-master-dev
from
v1.1-branch-mvd-master-dev_cherry-pick-from-1.0
Closed
V1.1 branch mvd master dev cherry pick from 1.0 #13
erwinpan1
wants to merge
11
commits into
v1.1-branch-mvd-master-dev
from
v1.1-branch-mvd-master-dev_cherry-pick-from-1.0
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
Using --KVS=<kvs file> and --storage-space=<dir path> now we are able to reassing all the configs / counters / data as well as key-value store to folder other than "/tmp/"
In previous commit the chip_counters.ini is wrongly renamed to chip_counter.ini. So this commit is to fix it back
Reverse 0bebe6f in this folder which seems to cause Github CI error
Upgrade the previous zap to the latest zap that 1.1 branch is running on $ zap --version Version: 2023.4.27 Feature level: 96 Hash: 4f2a3d6cc1bf5164013b72b36e625b92cf1619b1 Date: 2023-04-27T21:32:30.000Z Mode: source
Since we include RPC socket in Rpc.cpp, we'll need to set dependecy on it ``` Executing in build environment: ./scripts/build/build_examples.py --target linux-x64-light-rpc-with-ui build INFO Building targets: linux-x64-light-rpc-with-ui INFO Preparing builder 'linux-x64-light-rpc-with-ui' INFO Generating /__w/connectedhomeip/connectedhomeip/out/linux-x64-light-rpc-with-ui INFO Generating linux-x64-light-rpc-with-ui INFO ERROR at //third_party/connectedhomeip/examples/platform/linux/Rpc.cpp:21:11: Include not allowed. INFO #include "pw_rpc_system_server/socket.h" INFO ^---------------------------- INFO It is not in any dependency of INFO //:chip-lighting-app INFO The include file is in the target(s): INFO //third_party/connectedhomeip/third_party/pigweed/repo/pw_rpc/system_server:socket INFO which should somehow be reachable. ```
Disable Job(CI Examples NRFConnect) in workflow (chef.yaml) in this branch since we use "Promise" which is not compliant with nRF SDK
Enable Chef chip_device_enable_port_params to set --secured-device-port for MVD
Revert dda57da which seems to RPC blocking on Linux due to Lambda function hooked to ScheduleWork never running
erwinpan1
pushed a commit
that referenced
this pull request
Oct 10, 2023
…ist". (project-chip#29666) The typical failure there looks like this: ==29620==ERROR: LeakSanitizer: detected memory leaks Direct leak of 88 byte(s) in 1 object(s) allocated from: #0 0x106396e12 in calloc+0xa2 (libclang_rt.asan_osx_dynamic.dylib:x86_64+0x51e12) #1 0x7ff800dc9789 in map_images_nolock+0x24b (libobjc.A.dylib:x86_64h+0x1789) #2 0x7ff800dc94db in map_images+0x42 (libobjc.A.dylib:x86_64h+0x14db) #3 0x113d721fa in invocation function for block in dyld4::RuntimeState::setObjCNotifiers(void (*)(unsigned int, char const* const*, mach_header const* const*), void (*)(char const*, mach_header const*), void (*)(char const*, mach_header const*))+0x112 (dyld:x86_64+0xf1fa) #4 0x113d6d6c8 in dyld4::RuntimeState::withLoadersReadLock(void () block_pointer)+0x28 (dyld:x86_64+0xa6c8) #5 0x113d720e1 in dyld4::RuntimeState::setObjCNotifiers(void (*)(unsigned int, char const* const*, mach_header const* const*), void (*)(char const*, mach_header const*), void (*)(char const*, mach_header const*))+0x51 (dyld:x86_64+0xf0e1) #6 0x113d85d44 in dyld4::APIs::_dyld_objc_notify_register(void (*)(unsigned int, char const* const*, mach_header const* const*), void (*)(char const*, mach_header const*), void (*)(char const*, mach_header const*))+0x4e (dyld:x86_64+0x22d44) #7 0x7ff800dc9343 in _objc_init+0x4fe (libobjc.A.dylib:x86_64h+0x1343) #8 0x7ff800d83992 in _os_object_init+0xc (libdispatch.dylib:x86_64+0x2992) #9 0x7ff800d911b7 in libdispatch_init+0x136 (libdispatch.dylib:x86_64+0x101b7) #10 0x7ff80bd34894 in libSystem_initializer+0xed (libSystem.B.dylib:x86_64+0x1894) #11 0x113d77e4e in invocation function for block in dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const+0xb5 (dyld:x86_64+0x14e4e) #12 0x113d9eaac in invocation function for block in dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const+0xf1 (dyld:x86_64+0x3baac) #13 0x113d95e25 in invocation function for block in dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const+0x22c (dyld:x86_64+0x32e25) #14 0x113d64db2 in dyld3::MachOFile::forEachLoadCommand(Diagnostics&, void (load_command const*, bool&) block_pointer) const+0x80 (dyld:x86_64+0x1db2) #15 0x113d95bb6 in dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const+0xb2 (dyld:x86_64+0x32bb6) #16 0x113d9e603 in dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const+0x1d1 (dyld:x86_64+0x3b603) #17 0x113d77d81 in dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const+0x8f (dyld:x86_64+0x14d81) #18 0x113d7e659 in dyld4::PrebuiltLoader::runInitializers(dyld4::RuntimeState&) const+0x1d (dyld:x86_64+0x1b659) #19 0x113d8b76d in dyld4::APIs::runAllInitializersForMain()+0x25 (dyld:x86_64+0x2876d) #20 0x113d6938c in dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*)+0xd72 (dyld:x86_64+0x638c) #21 0x113d684e3 in start+0x183 (dyld:x86_64+0x54e3)
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Remove stale label or comment or this will be closed in 10 days. |
This stale pull request has been automatically closed. Thank you for your contributions. |
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.
Cherry-pick
from v1.0-branch-mvd-master-dev
to v1.1-branch-mvd-master-dev_cherry-pick-from-1.0
to v1.1-branch-mvd-master