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

ThreadStackManagerImpl cannot read active dataset #14174

Closed
woody-apple opened this issue Jan 25, 2022 · 0 comments · Fixed by #15400
Closed

ThreadStackManagerImpl cannot read active dataset #14174

woody-apple opened this issue Jan 25, 2022 · 0 comments · Fixed by #15400
Assignees
Labels
commissioning Involves placing devices on the network, initial setup linux todo 🗒️ V1.0

Comments

@woody-apple
Copy link
Contributor

required for gdbus to caching properties.


// TODO: The following code does not works actually, since otbr-posix does not emit signals for properties changes. Which is
// required for gdbus to caching properties.
std::unique_ptr<GVariant, GVariantDeleter> value(
openthread_io_openthread_border_router_dup_active_dataset_tlvs(mProxy.get()));
if (value == nullptr)
{


This issue was generated by todo-issue based on a TODO comment in e169fcf.
@tcarmelveilleux tcarmelveilleux added commissioning Involves placing devices on the network, initial setup and removed v1_triage_split_3 labels Jan 31, 2022
@tcarmelveilleux tcarmelveilleux changed the title The following code does not works actually, since otbr-posix does not emit signals for properties changes. Which is ThreadStackManagerImpl cannot read active dataset Jan 31, 2022
@erjiaqing erjiaqing added linux commissioning Involves placing devices on the network, initial setup and removed commissioning Involves placing devices on the network, initial setup labels Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
commissioning Involves placing devices on the network, initial setup linux todo 🗒️ V1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants