-
Notifications
You must be signed in to change notification settings - Fork 1
Copybara/push 2d5727eb 19a1 4386 aebc f309fb54f2de #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copybara/push 2d5727eb 19a1 4386 aebc f309fb54f2de #5
Conversation
GitOrigin-RevId: f1ac199d0a99e0455ce1739dd194784f5b79d20b
…p namespace declaration and improved handling of empty IDs GitOrigin-RevId: f93511204ae7364d1b6e081e26b9fa70174c10c4
GitOrigin-RevId: 237659c5055f2599c012034e9813aa2207cd6943
GitOrigin-RevId: 0d22c861b6eb1215472ee1c52e28f90d94f8a1e6
GitOrigin-RevId: c282785406d364f5836644be90951c364a3ed96f
GitOrigin-RevId: 3b066a3a94f030c8db110ec8cd13c9381c4f9de1
…using 011 as the default GitOrigin-RevId: 7084f86786bfd836be9b879fdebecd1dda0d05cd
… internal API types to a reserved namespace and replaced const references with plain object copies GitOrigin-RevId: 03b4e068603ad862051cdec62d027506899fe4a8
GitOrigin-RevId: 947891dce945e30598545784fe673c708bb9c2e1
GitOrigin-RevId: 9a7ec6a7b06880336811650894d1b0fb1f777de5
GitOrigin-RevId: a11fcd662c5134f3c0c6fe2a5e6668d52fb2ca0b
…he options, to reuse the code in other parts GitOrigin-RevId: c9c5930808076e4a6238d34ea292ffd2f469d81a
GitOrigin-RevId: f2e0f228c66e5717eb53e5badc9f48c62cd27423
GitOrigin-RevId: 8bff0186f4d2821f209ebfe2b748afe057c7c620
GitOrigin-RevId: e754a09ba63b6cea88cf5c6b6e37d4e56841476a
GitOrigin-RevId: b5e7d1cbbdfb7c624cd4e2d1bdb17f4d85ba4833
GitOrigin-RevId: 58f97eeae47d938ded8d4c185a2add705d61c2a9
GitOrigin-RevId: 97dc081ba0dd9302cce1686eb0ecbf6ab8b2a0f7
…dates GitOrigin-RevId: ac67566a4fc4a7892c3c48146e8298d355385bbf
…upstream version GitOrigin-RevId: a8118687386a1bb02daa7cf213b760504c861549
GitOrigin-RevId: 46e5ae8aee578f8bdfaa211d0b52291aa662470e
…ly instantiate the value type on 0.12 GitOrigin-RevId: f1fd688fa9e52d6367723184f2ab97c4e1490934
GitOrigin-RevId: 708a76806d9321c8ec727ffdef4dcee6af678746
…ame from .12 GitOrigin-RevId: dcb1916b22231d25a84c78539010b63ba5c1c117
…on .12 GitOrigin-RevId: c6d877afb3a12059020103cbdf841778d1d2267e
…ted name from .12 GitOrigin-RevId: df785f09dc5ab5090352ee71eae9093451364bdc
…ch the updated name from .12 GitOrigin-RevId: 946c833c2e159983040407e2d456e4a15c69398e
…ted name from .12 GitOrigin-RevId: 14892f0c3c66fe1c46c6448c750624144c6c892c
…all operations GitOrigin-RevId: 185c0367a3f9c534ec8b00a33e1552f3224ea310
GitOrigin-RevId: 847dd18dc542b90e5f2ac7613d12483333bf3618
GitOrigin-RevId: b1ef47d39df347174aedefe8385d54dbfdcef747
…ing config file Relates: ENTMQCL-1002 Update Qpid Proton C++ (aac3) clients to work with connection config file(s) GitOrigin-RevId: 9438b00bf43793b94eca7b40ba7f55725abb7bbf
…perly Relates: ENTMQCL-1002 Update Qpid Proton C++ (aac3) clients to work with connection config file(s) GitOrigin-RevId: 176441a04a9f99d3482eb149f710c3d2e58bcb58
Cause: Non-uniform clients' options. Consequence: Unable to test all clients by the same/similar commands. Fix: New option --conn-urls for connection URLs, removed option --failover-url. Result: Clients have more uniform options now. ~~ Relates: ENTMQCL-1191 [aac3] Change parameter from --failover-url to --conn-urls GitOrigin-RevId: b969cf1f48449d4ccdbbf0eb2c41fb407e3f176b
…id Proton libraries on Windows Relates: ENTMQCL-1168 Support Windows 2016 Server ENTMQCL-1169 Support Windows 10 Pro GitOrigin-RevId: 9a3fa6859298318d68d8b743d8860e7200e7a2bd
…om common to connector GitOrigin-RevId: ee0136c50e94af921bfaeb6e39191cc12dad1e92
…ow of receiver Relates: ENTMQCL-1176 [cpp] Drain gets stuck on GitOrigin-RevId: 2c9c198c75cc7357228f1f393a186a69f418fd19
…oton C++ (aac3) receiver Relates: ENTMQCL-1176 [cpp] Drain gets stuck on GitOrigin-RevId: 77bd26d5d3b03bba4f12cbf02644003bee49e2ff
…aac3) clients Relates: ENTMQCL-1295 Update QE clients with change from cli-proton-python GitOrigin-RevId: 2aed8871c991796c6f2f617221dd438254977baa
Relates: ENTMQCL-1346 [aac0] Size is not in apostrophes when printed as dict GitOrigin-RevId: 63c502aaeac0d9db26283c77e7f38455ab40d525
GitOrigin-RevId: 81c835321a1adc2af2210fe2225665fab94361c8
GitOrigin-RevId: 1740f698fb75243371117c3563a54247dc72ce2a
GitOrigin-RevId: 0bdd1ad6c38a603c8f5200bbe34ba1d404465850
Relates: ENTMQCL-1335 Support for SSL in aac3 clients GitOrigin-RevId: 9b448685f609ce5b88b35ff21fb60f3e64909409
CMake Warning (dev) at CMakeLists.txt:44 (set): implicitly converting 'String' to 'STRING' type. This warning is for project developers. Use -Wno-dev to suppress it. GitOrigin-RevId: 1338d7e8b51af82dc1c5d7a11fcfc78c3a3c1186
… C++ connector client GitOrigin-RevId: b0c3cfa4c96e42ba3dcf02b2ffe02ee41fdfe89c
Relates: ENTMQCL-1730 [dtests][aac3] Review SSL cli options GitOrigin-RevId: 8ac4a0df7abdb9ac4dfd93447e289860636b97b5
Relates: ENTMQCL-1731 Improve UriParser to support full URI GitOrigin-RevId: 0bfd3d2ebe9ac81ae02a287ca90ffc91caaf23da
Relates: ENTMQCL-1754 Add support for fragment into UriParser GitOrigin-RevId: d8bdf1f98acb0944a41c7a0d953e6e652e4a34f7
Relates: ENTMQCL-1753 Add support for query into UriParser GitOrigin-RevId: c4a528d2c2f4e94873ec42a7a692fb343a5ec7ed
Relates: ENTMQCL-1755 Add support for IPv6 into UriParser GitOrigin-RevId: ff14ec1a4502672ab0e9095a7482db0918dbf312
|
What a big merge request :D |
|
I did not do any changes. This is what's running in internal CI. There is fixed branch that Dominik created, but that is hopelessly out of date at this point. The advantage of doing it this way (Copybara, one of the options in #1) is that it is easy to keep internal and external versions in sync. (When I resolve the GH auth, it can even run automatically in CI.) |
|
OK, we can try to merge everything what we want and then wait for the result. |
|
Not sure how to deal with internal commit messages etc. |
|
Internal commit messages. That is easy, push everything in single squashed commit, without commit message, or tell copybara to override it with blank commit message... Is there anything worrying in the commit messages? My initial solution was to just push it, nobody cares anyways, and there is nothing truly secret in the commit messages. Maybe irrelevant (such as internal Jira numbers) but not secret) I realized I probably want to move the files out of dtests/node_data... though. The cpp directory should be root of this repo. |
|
New PR, for the changed paths. #6 |
No description provided.