go-vise-0.2.0 #71
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Activity:Doing
Activity:Proposal
Runner
AT
Runner
CLI
Runner
HTTP
cleanup
devops
easypeasy
exchange
l8ter
legacy
optimization
privilege
refactor
smell
support
tooling
ux
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: urdt/ussd#71
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "go-vise-0.2.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR implements go-vise 0.2.0
@lash kindly confirm if all changes have been implemented
I am not sure what the cause is, but now the state is not being persisted as expected:
I did however notice that one of the examples in dev-0.2.0 behaved differently after the last change, and that had to do with async state updates. I'll make this as "need more info" for now, while I investigate.
go-vise-0.2.0to WIP: go-vise-0.2.0WIP: go-vise-0.2.0to go-vise-0.2.0Fixed in go-vise 39b8e4e6b7a6be892be740d3ede34d4d3ccc3b35
Engine persistence was broken, which wasn't picked up by any of the tests in urdt-ussd, but strictly it is not the responsibility of urdt-ussd to do it.
Will make sure have at least one regression test for it upstream. Sorry
resolved by #64