{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":47433928,"defaultBranch":"v2","name":"gomaasapi","ownerLogin":"juju","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2015-12-04T23:27:09.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/4604548?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1697095168.0","currentOid":""},"activityList":{"items":[{"before":"7b1b159fa8955c44485e09f369b78e963b5b0b0c","after":"39eac57c45517eb3ab12aa7c7172169a52051872","ref":"refs/heads/v2","pushedAt":"2023-10-12T07:18:54.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jujubot","name":"Juju bot","path":"/jujubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7779494?s=80&v=4"},"commit":{"message":"Merge pull request #104 from r00ta/lp-2039105\n\nhttps://github.com/juju/gomaasapi/pull/104\n\nBugfix for https://bugs.launchpad.net/maas/+bug/2039105. \n\nThe bug is that in case of retry, the oauth headers are duplicated in the requests and MAAS nginx reject the request with 400. The fix is actually to use `http.Header.Set` instead of `http.Header.Add` in order to set or replace the \"Authentication\" header.","shortMessageHtmlLink":"Merge pull request #104 from r00ta/lp-2039105"}},{"before":"5277155400b573e2f26504b2ffe2ae765c38e895","after":"7b1b159fa8955c44485e09f369b78e963b5b0b0c","ref":"refs/heads/v2","pushedAt":"2023-09-11T09:01:33.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jujubot","name":"Juju bot","path":"/jujubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7779494?s=80&v=4"},"commit":{"message":"Merge pull request #101 from r00ta/lp-2034014-add-retry-policy-for-409-responses\n\nhttps://github.com/juju/gomaasapi/pull/101\n\nThis PR aims to retry on MAAS responses with status code equal to 409. \n\nIn particular we observed that in some cases it is possible that the client calls MAAS endpoints in parallel and due to some MAAS internals the requests need to be remade by the clients. \n\n[Link to the original bug](https://bugs.launchpad.net/maas/+bug/2034014)\n\n[Link to MAAS core merge proposal to add the `Retry-After` header in 409 responses](https://code.launchpad.net/~r00ta/maas/+git/maas/+merge/450867)","shortMessageHtmlLink":"Merge pull request #101 from r00ta/lp-2034014-add-retry-policy-for-40…"}},{"before":"fee803278897a7853e3a41e3c04d3f6267a731f2","after":"5277155400b573e2f26504b2ffe2ae765c38e895","ref":"refs/heads/v2","pushedAt":"2023-03-17T11:04:14.263Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"jujubot","name":"Juju bot","path":"/jujubot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7779494?s=80&v=4"},"commit":{"message":"Merge pull request #99 from SimonRichardson/optional-hardware-info\n\nhttps://github.com/juju/gomaasapi/pull/99\n\nUnfortunately, HardwareInfo isn't always available for every MAAS version. The prior PR[1] expected that hardware_info was available. The fix is simple, just make it optional when attempting to validate it with the schema coercing.\n\nAdditionally, I've added a few more tests to ensure that we're testing various scenarios of hardware_info being omitted. Lastly, it felt like there was a missing check for TestReadMachines for validating the hardware info for a given machine response.\n\nThis should fix[2] in Juju.\n\n 1. https://github.com/juju/gomaasapi/pull/96\n 2. https://bugs.launchpad.net/juju/+bug/2009064","shortMessageHtmlLink":"Merge pull request #99 from SimonRichardson/optional-hardware-info"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADlUOHhgA","startCursor":null,"endCursor":null}},"title":"Activity · juju/gomaasapi"}