eive/eive-obsw
eive/eive-obsw
13
4
Fork 0
Code Issues 4 Pull Requests 1 Releases 120 Wiki Activity

lets hope this fixes the occasional error #444

Merged
muellerr merged 2 commits from optimize_lock_handling into develop 2023-03-08 00:09:35 +01:00
Conversation 0 Commits 2 Files Changed 2 +23 -18
muellerr commented 2023-03-07 19:37:40 +01:00
Owner
Copy Link

More granular locking used now as well.

More granular locking used now as well.
muellerr added 1 commit 2023-03-07 19:37:41 +01:00
lets hope this fixes the occasional error
Some checks are pending
EIVE/eive-obsw/pipeline/head Build started...
Details
EIVE/eive-obsw/pipeline/pr-develop This commit looks good
Details
c562c4a240
muellerr added this to the v1.36.0 milestone 2023-03-07 21:06:30 +01:00
muellerr added 1 commit 2023-03-08 00:09:29 +01:00
Merge branch 'develop' into optimize_lock_handling
Some checks are pending
EIVE/eive-obsw/pipeline/pr-develop Build queued...
Details
a2d5138c71
muellerr merged commit 8759f86889 into develop 2023-03-08 00:09:35 +01:00
muellerr deleted branch optimize_lock_handling 2023-03-08 00:09:36 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
OPS TODO

Issues identified by OPS

  
api change

API change

  
breaking api change

API change which can break existing code

  
bug

Something is not working

  
documentation

Documentation

  
duplicate

This issue or pull request already exists

  
feature

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
OPS TODO
api change
breaking api change
bug
documentation
duplicate
feature
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
v1.36.0
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: eive/eive-obsw#444
No description provided.
Delete Branch "optimize_lock_handling"

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?