fix-sync-issue-two #41
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
priority
medium
question
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TTK4145/elevator!41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-sync-issue-two"
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?
Depends on #40
Closes #38
Closes #4
WIP: fix-sync-issue-twoto fix-sync-issue-two@ -729,23 +755,6 @@ impl ElevatorCall {}}/// Get the elevator currently assigned to handle this callAre these not used in the set_destination() and fetch_call_id() functions?
The entire "Handling elevator" field has been removed as it only cause de-sync issues without providing any valuable data.
Instead each elevator now tracks which call they are servicing.
As a result the
get_handling_elevatorandset_handling_elevatorno longer have any value.@ -138,3 +160,4 @@info!("Direction of the elevator is set to {:?}", direction);}None => {trace!("Destination of the elevator is set to None",);Double trace, don't need this one
WDYM?
I take it back, resolved in
2dcb396