Skip to content

Update mbed-coap to version 5.1.4 #12852

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

Merged
merged 1 commit into from
Apr 24, 2020
Merged

Conversation

anttiylitokola
Copy link
Contributor

Summary of changes

Add also 4.13 (Request Entity Too Large) responses to duplicate info list.

Add client library configurations for DEFAULT_RESPONSE_TIMEOUT and SN_COAP_DUPLICATION_MAX_TIME_MSGS_STORED.

Increased the default timeouts of DEFAULT_RESPONSE_TIMEOUT and SN_COAP_DUPLICATION_MAX_TIME_MSGS_STORED to 300 seconds.
These two are critical parameters for low-bandwidth high-latency networks. The defaults should be more geared towards such networks that are likely to have issues with transmissions.
The increased defaults can increase the runtime HEAP usage when there is a lot of duplicates or retransmissions.

Impact of changes

Migration actions required

Documentation


Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers


@yogpan01 @teetak01

Add also 4.13 (Request Entity Too Large) responses to duplicate info list.

Add client library configurations for DEFAULT_RESPONSE_TIMEOUT and SN_COAP_DUPLICATION_MAX_TIME_MSGS_STORED.

Increased the default timeouts of DEFAULT_RESPONSE_TIMEOUT and SN_COAP_DUPLICATION_MAX_TIME_MSGS_STORED to 300 seconds.
These two are critical parameters for low-bandwidth high-latency networks. The defaults should be more geared towards such networks that are likely to have issues with transmissions.
The increased defaults can increase the runtime HEAP usage when there is a lot of duplicates or retransmissions.
@ciarmcom ciarmcom requested review from teetak01, yogpan01 and a team April 23, 2020 11:00
@ciarmcom
Copy link
Member

@anttiylitokola, thank you for your changes.
@yogpan01 @teetak01 @ARMmbed/mbed-os-maintainers please review.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 23, 2020

@anttiylitokola Can we get this to 5.15 branch as well? I believe this was requested earlier today
cc @JanneKiiskila

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 23, 2020

CI started

@mbed-ci
Copy link

mbed-ci commented Apr 23, 2020

Test run: FAILED

Summary: 1 of 3 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_build-ARM

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 23, 2020

Checkout failed, CI restarted

@mbed-ci
Copy link

mbed-ci commented Apr 23, 2020

Test run: FAILED

Summary: 1 of 6 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_cloud-client-pytest

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 23, 2020

client test passed but did not report back due to login failure, restarted

@0xc0170 0xc0170 merged commit e2c01fa into ARMmbed:master Apr 24, 2020
@0xc0170
Copy link
Contributor

0xc0170 commented Apr 24, 2020

I'll create now 5.15 PR

@mergify mergify bot removed the ready for merge label Apr 24, 2020
@0xc0170
Copy link
Contributor

0xc0170 commented Apr 24, 2020

Done #12859

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants