atomix/atomix issues and pull requests

#1132 - Crosscluster raft

Pull Request - State: closed - Opened by kirazero17 3 months ago

#1131 - ONOS-Umbrella cannot push data to more than one Atomix RaftStore

Issue - State: open - Opened by kirazero17 4 months ago - 1 comment

#1130 - Black retourn

Issue - State: open - Opened by Gallo127 4 months ago

#1129 - add circle ci pipeline

Pull Request - State: closed - Opened by ubogdan 6 months ago

#1128 - add circle ci pipeline

Pull Request - State: closed - Opened by ubogdan 6 months ago

#1127 - Cannot install atomix-runtime using helm and kubeversion 1.26.5-gke.2700

Issue - State: open - Opened by hamidrezatelus 10 months ago

#1126 - Add failsafe-go

Pull Request - State: open - Opened by jhalterman 11 months ago

#1125 - Prueba

Issue - State: open - Opened by GaboAlfaroCR 12 months ago

#1124 - Web

Issue - State: open - Opened by GaboAlfaroCR 12 months ago

#1123 - Defer lock.

Issue - State: open - Opened by fud 12 months ago

#1122 - fix: upgrade typo

Pull Request - State: open - Opened by testwill about 1 year ago

#1121 - pod: atomix-runtime-controller always crash with latest version

Issue - State: open - Opened by wangzheng00 about 1 year ago - 1 comment

#1120 - chore: slice append replace loop

Pull Request - State: open - Opened by testwill about 1 year ago

#1119 - Use write lock when deleting watchers in local network driver

Pull Request - State: closed - Opened by kuujo over 1 year ago
Labels: bug

#1118 - Use write lock when deleting watchers in local network driver

Pull Request - State: closed - Opened by kuujo over 1 year ago
Labels: bug

#1117 - Fix race condition in local network driver

Pull Request - State: closed - Opened by kuujo over 1 year ago
Labels: bug

#1116 - Fix race condition in local network driver

Pull Request - State: closed - Opened by kuujo over 1 year ago
Labels: bug

#1115 - Fix race condition in local network driver

Pull Request - State: closed - Opened by kuujo over 1 year ago
Labels: bug

#1114 - atomix-consensus-node permission denied at pod start writing to data with persistent volume block storage on Google Cloud

Issue - State: open - Opened by jallenkj over 1 year ago

#1113 - Atomix docker 3.1.5

Issue - State: open - Opened by first-vc over 1 year ago

#1112 - Atomix charts breaking SD-RAN deployment

Issue - State: open - Opened by sofianinho over 1 year ago - 1 comment

#1111 - Update certs scripts

Pull Request - State: closed - Opened by adibrastegarnia over 1 year ago

#1109 - RFC: Distributed Semaphore

Issue - State: open - Opened by debuggerpk over 1 year ago

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1107 - raft.getCluster().getMember(*).memberId() could Result in an NPE

Issue - State: closed - Opened by zhaoyangyingmu about 2 years ago
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1096 - Leak on server shutdown while still awaiting other nodes to join

Issue - State: closed - Opened by franz1981 over 3 years ago - 1 comment
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1093 - Nodes are constantly joining and leaving with DnsDiscoveryProvider

Issue - State: closed - Opened by kmrozek-shareablee over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1092 - Error is not getting printed when an Channel could not connect to an address

Issue - State: closed - Opened by ashishmittal19 over 3 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1090 - Is the repository open to take PRs for open issues?

Issue - State: closed - Opened by the123saurav almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy

#1088 - onos to atomix get timeout

Issue - State: closed - Opened by xinchengwuxian almost 4 years ago
Labels: archived, legacy