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

zpc: Fix tests #46

Closed
rzr opened this issue Feb 20, 2025 · 0 comments
Closed

zpc: Fix tests #46

rzr opened this issue Feb 20, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@rzr
Copy link
Collaborator

rzr commented Feb 20, 2025

Related tasks:

@rzr rzr changed the title API Analysis zpc: Fix testsystem Feb 20, 2025
@rzr rzr changed the title zpc: Fix testsystem zpc: Fix tests Feb 20, 2025
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Feb 25, 2025
…otocol-controller SiliconLabsSoftware#46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Bug-SiliconLabs: SWPROT-8953
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
@rzr rzr added the bug Something isn't working label Mar 6, 2025
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 6, 2025
…otocol-controller SiliconLabsSoftware#46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Bug-SiliconLabs: SWPROT-8953
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 7, 2025
…otocol-controller SiliconLabsSoftware#46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Bug-SiliconLabs: SWPROT-8953
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
SiliconLabsSoftware#46

This test was previously bypassed, it is now working as expected.

The reason it was failing is because mktime use timezone
to set the tm structure that will be returned to the next step of step.

Setting timezone to UTC (+0) solves the problem

Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
SiliconLabsSoftware#46

This test was previously bypassed, it is now working as expected.

The reason it was failing is because mktime use timezone
to set the tm structure that will be returned to the next step of step.

Setting timezone to UTC (+0) solves the problem

Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Origin: SiliconLabsSoftware#69
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
SiliconLabsSoftware#46

This test was previously bypassed, it is now working as expected.

The reason it was failing is because mktime use timezone
to set the tm structure that will be returned to the next step of step.

Setting timezone to UTC (+0) solves the problem

Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Origin: SiliconLabsSoftware#69
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
Not this is not latest version but it aligned to the version used at zwa,
may unify-core align to it and synchronize all projects accordingly,
or reconsider the archtecture.

Bug-SiliconLabsSoftware: SiliconLabsSoftware#60
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
…otocol-controller SiliconLabsSoftware#46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Bug-SiliconLabs: SWPROT-8953
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
…: Removed as not part of z-wave-protocol-controller

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#36
Bug: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 17, 2025
…est SiliconLabsSoftware#46

Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
@rzr rzr self-assigned this Mar 18, 2025
rzr added a commit that referenced this issue Mar 18, 2025
#46

This test was previously bypassed, it is now working as expected.

The reason it was failing is because mktime use timezone
to set the tm structure that will be returned to the next step of step.

Setting timezone to UTC (+0) solves the problem

Bug-SiliconLabsSoftware: #46
Origin: #69
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
Not this is not latest version but it aligned to the version used at zwa,
may unify-core align to it and synchronize all projects accordingly,
or reconsider the archtecture.

Bug-SiliconLabsSoftware: SiliconLabsSoftware#60
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
…otocol-controller SiliconLabsSoftware#46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Bug-SiliconLabs: SWPROT-8953
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
…: Removed as not part of z-wave-protocol-controller

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#36
Bug: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
…est SiliconLabsSoftware#46

Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
Not this is not latest version but it aligned to the version used at zwa,
may unify-core align to it and synchronize all projects accordingly,
or reconsider the archtecture.

Bug-SiliconLabsSoftware: SiliconLabsSoftware#60
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 18, 2025
…otocol-controller SiliconLabsSoftware#46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Bug-SiliconLabs: SWPROT-8953
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…protocol-controller SiliconLabsSoftware#60

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#60
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…ntroller SiliconLabsSoftware#55

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#55
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…ller SiliconLabsSoftware#55

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#55
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
Origin: SiliconLabsSoftware#70
Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…est SiliconLabsSoftware#46

Origin: SiliconLabsSoftware#70
Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
Origin: SiliconLabsSoftware#70
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…5.3-g9d092898" SiliconLabsSoftware#60

This reverts commit 9865caa.

Bug: SiliconLabsSoftware#46
Origin: SiliconLabsSoftware#36
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…Software#60

Patches from unify may land elsewhere

Origin: SiliconLabsSoftware#36
Bug: SiliconLabsSoftware#55
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
Origin: SiliconLabsSoftware#36
Bug: SiliconLabsSoftware#55
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…libs2/TestFramework/cmock: Removed as not part of z-wave-protocol-controller SiliconLabsSoftware#60

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#60
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…protocol-controller SiliconLabsSoftware#60

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#60
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…ntroller SiliconLabsSoftware#55

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#55
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…ller SiliconLabsSoftware#55

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: SiliconLabsSoftware#70
Bug: SiliconLabsSoftware#55
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
Origin: SiliconLabsSoftware#70
Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
…est SiliconLabsSoftware#46

Origin: SiliconLabsSoftware#70
Bug-SiliconLabsSoftware: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit to rzr/z-wave-protocol-controller that referenced this issue Mar 19, 2025
Origin: SiliconLabsSoftware#70
Relate-to: SiliconLabsSoftware#46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
Not this is not latest version but it aligned to the version used at zwa,
may unify-core align to it and synchronize all projects accordingly,
or reconsider the architecture.

Since UnifySDK also depends on CMock, indirect dep will be privileged,
May those lines be removed in later cleanup changes.

Origin: #70
Bug-SiliconLabsSoftware: #60
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…otocol-controller #46

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

Docs should be regenerated from sources, but not stored along sources.

More cleanup might be desirable for 1.7.

Origin: #70
Bug-SiliconLabs: SWPROT-8953
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…: Removed as not part of z-wave-protocol-controller #60

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: #70
Bug: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…5.3-g9d092898" #60

This reverts commit 9865caa.

Bug: #46
Origin: #36
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
Patches from unify may land elsewhere

Origin: #36
Bug: #55
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
Origin: #36
Bug: #55
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…libs2/TestFramework/cmock: Removed as not part of z-wave-protocol-controller #60

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: #70
Bug: #60
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…protocol-controller #60

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: #70
Bug: #60
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…ntroller #55

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: #70
Bug: #55
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…ller #55

This component is maintained at UnifySDK (v1.7+ aka core),

This change deduplicate code, to ensure a single source of truth
and enable a more sustainable developement model
without overhead of monorepo.

This change may be not atomic,
but has been done in a way one component could be reverted
if it justify a downstream (double) maintainance or experimental works.

For the record this component was imported from:
https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.6.0

If this component should be re-introduced it would be preferable to
consider the code where it is maintained eg:

https://github.com/SiliconLabs/UnifySDK/releases/tag/ver_1.7.0 (or later)

Bug-SiliconLabs: SWPROT-8953
Origin: #70
Bug: #55
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
Origin: #70
Bug-SiliconLabsSoftware: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
…est #46

Origin: #70
Bug-SiliconLabsSoftware: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
rzr added a commit that referenced this issue Mar 19, 2025
Origin: #70
Relate-to: #46
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
@rzr rzr closed this as completed Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants