{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":732507303,"defaultBranch":"master","name":"node-coap","ownerLogin":"edrose","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-12-16T22:40:48.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/6173903?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1702811139.0","currentOid":""},"activityList":{"items":[{"before":"0a11715e60d698060f7848218caca4af0d9492b2","after":null,"ref":"refs/heads/packet-size","pushedAt":"2023-12-17T11:05:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"}},{"before":"58b1c43c95a8bab44b90b49799edf36ec75f6648","after":"0a11715e60d698060f7848218caca4af0d9492b2","ref":"refs/heads/master","pushedAt":"2023-12-17T11:05:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}},{"before":"fb6df4c561e15c1ae081454f6604a01956e5cfc3","after":"0a11715e60d698060f7848218caca4af0d9492b2","ref":"refs/heads/packet-size","pushedAt":"2023-12-17T11:01:32.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}},{"before":null,"after":"fb6df4c561e15c1ae081454f6604a01956e5cfc3","ref":"refs/heads/packet-size","pushedAt":"2023-12-17T10:59:06.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}},{"before":"a45ec8ef0f1fc0df8a673c60bec0f2ac8fceb1dd","after":"58b1c43c95a8bab44b90b49799edf36ec75f6648","ref":"refs/heads/master","pushedAt":"2023-12-17T10:03:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}},{"before":"9fc00d70b2b51fe688dc93ec318c20de44e6d1a8","after":"a45ec8ef0f1fc0df8a673c60bec0f2ac8fceb1dd","ref":"refs/heads/master","pushedAt":"2023-12-17T09:37:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}},{"before":"9ea6b95afc5e106e39caad7ab8de8765a6703732","after":"9fc00d70b2b51fe688dc93ec318c20de44e6d1a8","ref":"refs/heads/master","pushedAt":"2023-12-16T22:49:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}},{"before":"5014206e0d0effcfc465b41c19a3083911fa3d0a","after":"9ea6b95afc5e106e39caad7ab8de8765a6703732","ref":"refs/heads/master","pushedAt":"2023-12-16T22:45:39.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"edrose","name":"Ed Rose","path":"/edrose","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6173903?s=80&v=4"},"commit":{"message":"Perform extra checks on CoAP message size\n\nThis fixes the logic for checking the maximum CoAP message size. The\ncheck is actually performed in the coap-packet repository in a default\nparameter on the `generate()` function, however the default value is not\nappropriate for all (if any) cases.\n\nThe maximum size that a CoAP message can be is the IP MTU, minus the IP\nheader and  minus the UDP header. The value is not constant across all\nIP network stacks, so the CoAP specification recommends a maximum of 1152\nbytes for cases where it is not known. The only way to know for sure is\nMTU path discovery, which is way outside of the scope of the project.\n\nThis commit creates a parameter that allows the max packet size to be\nadjusted as a server parameter for cases where (for example) the server\nis running on a 6LoWPAN/Thread network and needs a lower maximum message\nsize.\n\nNote that the logic for enforcing the size is just to throw an error and\ncrash the server. However, since the maximum payload size is enforced a\nsituation like that should never occur.","shortMessageHtmlLink":"Perform extra checks on CoAP message size"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMi0xN1QxMTowNTozOS4wMDAwMDBazwAAAAPMNbC-","startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMi0xN1QxMTowNTozOS4wMDAwMDBazwAAAAPMNbC-","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMi0xNlQyMjo0NTozOS4wMDAwMDBazwAAAAPMB2Pk"}},"title":"Activity · edrose/node-coap"}