You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A getValue function name collision occurs when combining the separated uplink decoder and downlink encoder scripts for platform use (e.g., ChirpStack).
The downlink encoder's getValue (value->key lookup, throws error), likely established around commit dfec81b, overwrites the uplink decoder's getValue (key->value lookup).
This causes uplink decoding to fail (e.g., with "not match in {...}" error) as it calls the incorrect helper function.
Recommendation:
Rename the downlink encoder's getValue helper (e.g., to getKeyFromValue or findKeyByValue) to resolve the conflict in combined scripts.
The text was updated successfully, but these errors were encountered:
A
getValue
function name collision occurs when combining the separated uplink decoder and downlink encoder scripts for platform use (e.g., ChirpStack).The downlink encoder's
getValue
(value->key lookup, throws error), likely established around commit dfec81b, overwrites the uplink decoder'sgetValue
(key->value lookup).This causes uplink decoding to fail (e.g., with
"not match in {...}"
error) as it calls the incorrect helper function.Recommendation:
Rename the downlink encoder's
getValue
helper (e.g., togetKeyFromValue
orfindKeyByValue
) to resolve the conflict in combined scripts.The text was updated successfully, but these errors were encountered: