tag:github.com,2008:https://github.com/vanadium/core/releases Tags from core 2023-04-17T21:08:08Z tag:github.com,2008:Repository/62972285/v0.2.0 2023-05-10T05:15:25Z v0.2.0 cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.21 2022-12-13T23:17:48Z v0.1.21 cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.20 2021-09-25T19:49:52Z v0.1.20 cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.19 2021-07-29T00:31:13Z v0.1.19 <p>Merge commit '297ba726332cf327c72722a51079cee9205efc6e' into release-…</p> <p>…v0.1.18</p> cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.18 2021-06-21T17:14:03Z v0.1.18 cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.17 2021-06-09T05:32:05Z v0.1.17 cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.16 2021-02-11T02:12:08Z v0.1.16 <p>x/ref/runtime/internal/rpc: ensure that a proxied server expands to u…</p> <p>…se all available proxies (<a class="issue-link js-issue-link" href="https://github.com/vanadium/core/pull/186">#186</a>)</p> <p>Prior to this PR, a server using the 'all' proxy policy would expand the set of proxy instances that it used when it encountered an error with any of existing proxy instances. This PR changes the behavior so that servers will monitor the set of available proxy instances and expand to use all available ones ahead of any errors being encountered.</p> <p>Also, include a fix for big sur whereby the error messages for connection refused appears to have changed.</p> cosnicolaou tag:github.com,2008:Repository/62972285/__test 2021-02-11T02:03:38Z __test <p>x/ref/runtime/internal/rpc: ensure that a proxied server expands to u…</p> <p>…se all available proxies (<a class="issue-link js-issue-link" href="https://github.com/vanadium/core/pull/186">#186</a>)</p> <p>Prior to this PR, a server using the 'all' proxy policy would expand the set of proxy instances that it used when it encountered an error with any of existing proxy instances. This PR changes the behavior so that servers will monitor the set of available proxy instances and expand to use all available ones ahead of any errors being encountered.</p> <p>Also, include a fix for big sur whereby the error messages for connection refused appears to have changed.</p> cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.15 2020-12-10T21:34:36Z v0.1.15 <p>x/ref/lib/security: explicitly create a read lock file if it does not…</p> <p>… exist already (<a class="issue-link js-issue-link" href="https://github.com/vanadium/core/pull/179">#179</a>)</p> <p>* x/ref/lib/security: explicitly create a read lock file if it does not exist already</p> cosnicolaou tag:github.com,2008:Repository/62972285/v0.1.14 2020-11-28T17:22:56Z v0.1.14 <p>x/ref/runtime/internal: use aws imds v1 first and then v2 (<a class="issue-link js-issue-link" href="https://github.com/vanadium/core/pull/174">#174</a>)</p> <p>AWS' instance meta data service cannot be accessed from a docker container running in bridge mode. This PR changes the behaviour to use the v1 service first and only if that fails, to use the v2 service. This fallback is required since it's possible to configure aws instances to allow v2 only.</p> cosnicolaou