Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Remove python minor version dep 0dc4b2d
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Install python reqs 99cf85f
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Add a job which runs the system tests locally 77db736
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Add cacitesting .env file 2b76279
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Combine ccf_sandbox and ccf_sandbox_fast d2a86b4
DomAyre created a comment on an issue on microsoft/azure-privacy-sandbox-kms
This will be covered by #166
takuro-sato pushed 1 commit to takurosato/update-ccf-to.5.0.7 microsoft/azure-privacy-sandbox-kms
- Specify node version to fix unit test a7530ae
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Add some more tests 8a69872
takuro-sato pushed 1 commit to takurosato/update-ccf-to.5.0.7 microsoft/azure-privacy-sandbox-kms
- Add timeout for mccf test 64694cf
takuro-sato created a comment on a pull request on microsoft/azure-privacy-sandbox-kms
CI for integration with B&A: https://github.com/microsoft/privacy-sandbox-dev/actions/runs/11480659917/job/31951377030
DomAyre created a comment on an issue on microsoft/azure-privacy-sandbox-kms
Looking at the implementation it looks like this is deliberate, but I'm going to keep the issue open because I wonder if it would be better to return 200 with an empty list
DomAyre opened an issue on microsoft/azure-privacy-sandbox-kms
Make Endpoints casing consistent
We have a mix of all lower case (`pubkey`, `listpubkeys`) and some camelCase (`keyReleasePolicy`, `unwrapKey`) endpoints
DomAyre opened an issue on microsoft/azure-privacy-sandbox-kms
`/keyReleasePolicy` returns potentially unexpected values
I'm not an expert here, but I've just added a test which adds and then removes the key release policy, when I do that and query the current policy I get something which only looks half removed? ``...
takuro-sato opened a pull request on microsoft/azure-privacy-sandbox-kms
Upgrade CCF to 5.0.7
With current 5.0.4 it gets certificate errors for validating attestation report and returns 500 for /key endpoint. CCF release 5.0.7 fixes it https://github.com/microsoft/CCF/releases/tag/ccf-5.0.7
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Integrate aci into pytest conftest de61ed4
DomAyre pushed 1 commit to system-tests microsoft/azure-privacy-sandbox-kms
- Add target to deploy CCF sandbox 7a68950
dependabot[bot] opened a pull request on microsoft/azure-privacy-sandbox-kms
dependabot: bump cryptography from 43.0.1 to 43.0.3
Bumps [cryptography](https://github.com/pyca/cryptography) from 43.0.1 to 43.0.3. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pyca/cryptography/blob/main/...
dependabot[bot] deleted a branch microsoft/azure-privacy-sandbox-kms
dependabot/pip/setuptools-75.1.0
dependabot[bot] closed a pull request on microsoft/azure-privacy-sandbox-kms
dependabot: bump setuptools from 72.0.0 to 75.1.0
Bumps [setuptools](https://github.com/pypa/setuptools) from 72.0.0 to 75.1.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pypa/setuptools/blob/main/NEWS.r...
dependabot[bot] created a comment on a pull request on microsoft/azure-privacy-sandbox-kms
Superseded by #172.