unset optional or repeated messages with required child fields show up on decode
Bug #1181026 reported by
toby schneider
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Dynamic Compact Control Language |
Fix Released
|
High
|
toby schneider | ||
| Goby |
Won't Fix
|
High
|
toby schneider | ||
Bug Description
message Info {
required int32 state = 1 [(dccl.field) = { min: 0 max: 10 }];
}
message Data {
option (dccl.msg).id = 10;
option (dccl.msg)
optional Info info = 6;
}
Even if "info" is not set, it shows up on decoded messages (due to the required field "state" inside "Info").
I believe that fixing this bug will require changing the wire protocol of DCCLDefaultMess
Related branches
lp:~dccl-dev/dccl/3.0
- Nathan Knotts: Pending requested
- Diff: 0 lines
| summary: |
- optional or repeated messages with required child fields show up on - decode + unset optional or repeated messages with required child fields show up + on decode |
| description: | updated |
| description: | updated |
Revision history for this message
| toby schneider (tes) wrote | #1 |
| Changed in dccl: | |
| importance: | Undecided → High |
| assignee: | nobody → toby schneider (tes) |
| milestone: | none → 3.0.0 |
| Changed in goby: | |
| status: | New → Won't Fix |
| Changed in dccl: | |
| status: | New → In Progress |
| Changed in dccl: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This will be resolved in DCCL v3, which Goby 2.1 will depend on.