larvit/smpp-js
3
0
Fork 0
Code Issues Pull Requests Actions Activity

Pin that maxOctets refuses Infinity, and say refuse where the changelog said drop
Test / lint (pull_request) Successful in 20s
Details
Test / test (18) (pull_request) Successful in 30s
Details
Test / test (20) (pull_request) Successful in 29s
Details
Test / test (22) (pull_request) Successful in 31s
Details
Test / test (24) (pull_request) Successful in 28s
Details
Test / test (26) (pull_request) Successful in 30s
Details
Mirror / push (push) Successful in 4s
Details

Browse Source
This commit was merged in pull request #24.
This commit is contained in:
Lilleman auf Larv
2026-09-24 00:06:22 +02:00
parent 80f77afa0f
commit c5ef4c4703
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+2 -2
View File
@@ -35,8 +35,8 @@
- An `alert_notification` or an `outbind` from the peer is logged and left unanswered, as SMPP 3.4
gives neither a response. Each one used to emit `sessionError`, `"alert_notification" has no
response command`.
- `server()` refuses a `maxOctets` below 1 or not a whole number, like its other limits.
`server({ maxOctets: 0 })` used to start and then drop every multipart message.
- `server()` refuses a `maxOctets` below 1 or not a whole number, `Infinity` included, like its
other limits. `server({ maxOctets: 0 })` used to start and then refuse every multipart message.
## 0.5.0