{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":101093813,"defaultBranch":"master","name":"go","ownerLogin":"samsarahq","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2017-08-22T18:14:22.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/14863620?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1723170743.0","currentOid":""},"activityList":{"items":[{"before":"887b46fb9199ec612fc38d95e08fe39399261cda","after":null,"ref":"refs/heads/cguenthner/expose-snapshotting-options","pushedAt":"2024-08-09T02:32:23.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cguenthner","name":"Casey Guenthner","path":"/cguenthner","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22801471?s=80&v=4"}},{"before":"9d90fe5b0ca5d938fc07c44538336e9557dbf2f7","after":"78952ca1b8346f6e505ef2c44860e5ed5d61df86","ref":"refs/heads/master","pushedAt":"2024-08-09T02:32:22.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"cguenthner","name":"Casey Guenthner","path":"/cguenthner","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22801471?s=80&v=4"},"commit":{"message":"snapshotter: expose global snapshotting configuration\n\nsnapshotter can run in a few different \"modes\" that determine whether\nit fails tests and/or rewrites snapshots. The mode can be configured\nby command-line arguments and/or environment variables, with some\ncombinations of configuration being invalid. To support more\ncustomizable snapshotting behavior, this exposes the global\nconfiguration used by snapshotter. This will allow callers to\nimplement custom snapshotting behavior while maintaining consistent\nbehavior with respect to the defined snapshotter modes.","shortMessageHtmlLink":"snapshotter: expose global snapshotting configuration"}},{"before":"4497696ea19f184054563c10bb2f64b9677c32ee","after":"887b46fb9199ec612fc38d95e08fe39399261cda","ref":"refs/heads/cguenthner/expose-snapshotting-options","pushedAt":"2024-08-09T02:30:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cguenthner","name":"Casey Guenthner","path":"/cguenthner","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22801471?s=80&v=4"},"commit":{"message":"snapshotter: expose global snapshotting configuration\n\nsnapshotter can run in a few different \"modes\" that determine whether\nit fails tests and/or rewrites snapshots. The mode can be configured\nby command-line arguments and/or environment variables, with some\ncombinations of configuration being invalid. To support more\ncustomizable snapshotting behavior, this exposes the global\nconfiguration used by snapshotter. This will allow callers to\nimplement custom snapshotting behavior while maintaining consistent\nbehavior with respect to the defined snapshotter modes.","shortMessageHtmlLink":"snapshotter: expose global snapshotting configuration"}},{"before":null,"after":"4497696ea19f184054563c10bb2f64b9677c32ee","ref":"refs/heads/cguenthner/expose-snapshotting-options","pushedAt":"2024-08-09T00:49:59.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cguenthner","name":"Casey Guenthner","path":"/cguenthner","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22801471?s=80&v=4"},"commit":{"message":"snapshotter: expose global snapshotting configuration\n\nsnapshotter can run in a few different \"modes\" that determine whether\nit fails tests and/or rewrites snapshots. The mode can be configured\nby command-line arguments and/or environment variables, which some\ncombinations of configuration being invalid. To support more\ncustomizable snapshotting behavior, this exposes the global\nconfiguration used by snapshotter. This will allow callers to\nimplement custom snapshotting behavior while maintaining consistent\nbehavior with respect to the defined snapshotter modes.","shortMessageHtmlLink":"snapshotter: expose global snapshotting configuration"}},{"before":"46203ca3a6d8833702d854820e9301f9939ebea5","after":"9d90fe5b0ca5d938fc07c44538336e9557dbf2f7","ref":"refs/heads/master","pushedAt":"2024-01-18T19:51:59.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"jsm","name":"Jon San Miguel","path":"/jsm","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1446054?s=80&v=4"},"commit":{"message":"go snapshotter: Added a SnapshotFileName method\n\nAdded a SnapshotFileName to snapshotter to allow dtest to get the file name of the snapshot for copying to/from devices\nAdded unit tests to check both named and unnamed Snapshotter file names.","shortMessageHtmlLink":"go snapshotter: Added a SnapshotFileName method"}},{"before":"cdddf789b67a6d3c4eae43a96430ef3f112d0295","after":null,"ref":"refs/heads/mdb/docs-housekeeping","pushedAt":"2023-06-22T16:46:07.453Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"mdb","name":"Mike Ball","path":"/mdb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/184109?s=80&v=4"}},{"before":"189e0ea5a0b46a8122f3b29dfde3a283c5d7528f","after":"46203ca3a6d8833702d854820e9301f9939ebea5","ref":"refs/heads/master","pushedAt":"2023-06-22T16:46:06.100Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"mdb","name":"Mike Ball","path":"/mdb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/184109?s=80&v=4"},"commit":{"message":"docs: clean up whitespace and grammar\n\n* remove trailing whitespace\n* use consistent verb tense\n* consistently use Godoc-style comments\n* correct example code formatting in documentation","shortMessageHtmlLink":"docs: clean up whitespace and grammar"}},{"before":null,"after":"cdddf789b67a6d3c4eae43a96430ef3f112d0295","ref":"refs/heads/mdb/docs-housekeeping","pushedAt":"2023-06-14T21:07:17.917Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"mdb","name":"Mike Ball","path":"/mdb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/184109?s=80&v=4"},"commit":{"message":"docs: clean up whitespace and grammar\n\n* remove trailing whitespace\n* use consistent verb tense\n* consistently use Godoc-style comments\n* correct example code formatting in documentation","shortMessageHtmlLink":"docs: clean up whitespace and grammar"}},{"before":"873dd4867a68aa9f94cc8bc43848ad69478793ab","after":"189e0ea5a0b46a8122f3b29dfde3a283c5d7528f","ref":"refs/heads/master","pushedAt":"2023-06-14T15:02:00.084Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"mdb","name":"Mike Ball","path":"/mdb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/184109?s=80&v=4"},"commit":{"message":"oops: fix test suite\n\nThis fixes the existing test suite for the oops library. The pre-existing tests were a little\nbrittle, relying on the checkout dir when comparing expected stack traces to captured ones.\nAlso, featured a lot of hard-coded comparisons to line numbers in expected stack traces\n\nThe test suite should now run ok regardless of the parent folder structure of the git checkout, also\nit should be tolerant of differening dependencies / go versions that may re-order LOC. Also, when\nadding or removing lines in the test file itself, there should no longer be a need to update the\nhard-coded assertions of line numbers.","shortMessageHtmlLink":"oops: fix test suite"}},{"before":"093969e34653372cede07269ced21469c9fbf1e8","after":"873dd4867a68aa9f94cc8bc43848ad69478793ab","ref":"refs/heads/master","pushedAt":"2023-06-14T10:03:32.736Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"mdb","name":"Mike Ball","path":"/mdb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/184109?s=80&v=4"},"commit":{"message":"CI: limit push to 'master' branch\n\nThis ensures CI is only invoked when...\n\n* opening PRs and pushing to PR branches\n* pushing to master\n\nAs such, it also ensures we don't invoke redundant CI jobs when pushing\nto a branch for which there's an open PR.","shortMessageHtmlLink":"CI: limit push to 'master' branch"}},{"before":"609f7e2558fd8e2550090ee4c0c59485d847b020","after":null,"ref":"refs/heads/jesse/snapshotter-refactor","pushedAt":"2023-05-19T18:04:20.287Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"ChenJesse","name":"Jesse Chen","path":"/ChenJesse","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11747956?s=80&v=4"}},{"before":"2511ff93c4fc2c6b949c8ba5b89e51234d165720","after":"093969e34653372cede07269ced21469c9fbf1e8","ref":"refs/heads/master","pushedAt":"2023-05-19T18:04:19.230Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"ChenJesse","name":"Jesse Chen","path":"/ChenJesse","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11747956?s=80&v=4"},"commit":{"message":"snapshotter: rewriteWithFailOnDiff\n\nPrior to this commit, there were only two options:\nrewrite or verify mode.\n\nIf you are in rewrite mode, we rewrite the snapshots and the unit test\nwill never fail on the Verify() call (unless something goes wrong with\nthe mechanics of writing the snapshots file).\n\nElse, if you are in verify mode (the default mode), we will compare the\nsnapshots with the actual values and fail the unit test if there is any\nmismatch.\n\nThis commit introduces a third option: we first verify, and then we\nrewrite the snapshot. This might be a very specialized use-case, but at\nSamsara, we have developer tooling around making it easier to patch\nthese snapshot diffs, which involve the snapshot diffs being generated\n(so we need rewrite mode) and pushed to our CI artifacts bucket for\nlater application, but we also want the unit test to fail so\nthat our CI flake detection mechanisms can properly flag the test as\nflaky.","shortMessageHtmlLink":"snapshotter: rewriteWithFailOnDiff"}},{"before":"2dce2fbe57c477c34eab53e2203d7f7cd226508f","after":"609f7e2558fd8e2550090ee4c0c59485d847b020","ref":"refs/heads/jesse/snapshotter-refactor","pushedAt":"2023-05-19T16:51:51.694Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ChenJesse","name":"Jesse Chen","path":"/ChenJesse","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11747956?s=80&v=4"},"commit":{"message":"snapshotter: rewriteWithFailOnDiff\n\nPrior to this commit, there were only two options:\nrewrite or verify mode.\n\nIf you are in rewrite mode, we rewrite the snapshots and the unit test\nwill never fail on the Verify() call (unless something goes wrong with\nthe mechanics of writing the snapshots file).\n\nElse, if you are in verify mode (the default mode), we will compare the\nsnapshots with the actual values and fail the unit test if there is any\nmismatch.\n\nThis commit introduces a third option: we first verify, and then we\nrewrite the snapshot. This might be a very specialized use-case, but at\nSamsara, we have developer tooling around making it easier to patch\nthese snapshot diffs, which involve the snapshot diffs being generated\n(so we need rewrite mode) and pushed to our CI artifacts bucket for\nlater application, but we also want the unit test to fail so\nthat our CI flake detection mechanisms can properly flag the test as\nflaky.","shortMessageHtmlLink":"snapshotter: rewriteWithFailOnDiff"}},{"before":"bbbcce312ff9f81619a380b206640490bdb785ff","after":"2dce2fbe57c477c34eab53e2203d7f7cd226508f","ref":"refs/heads/jesse/snapshotter-refactor","pushedAt":"2023-05-19T16:43:32.026Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ChenJesse","name":"Jesse Chen","path":"/ChenJesse","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11747956?s=80&v=4"},"commit":{"message":"snapshotter: rewriteWithFailOnDiff\n\nPrior to this commit, there were only two options:\nrewrite or verify mode.\n\nIf you are in rewrite mode, we rewrite the snapshots and the unit test\nwill never fail on the Verify() call (unless something goes wrong with\nthe mechanics of writing the snapshots file).\n\nElse, if you are in verify mode (the default mode), we will compare the\nsnapshots with the actual values and fail the unit test if there is any\nmismatch.\n\nThis commit introduces a third option: we first verify, and then we\nrewrite the snapshot. This might be a very specialized use-case, but at\nSamsara, we have developer tooling around making it easier to patch\nthese snapshot diffs, which involve the snapshot diffs being generated\n(so we need rewrite mode) and pushed to our CI artifacts bucket for\nlater application, but we also want the unit test to fail so\nthat our CI flake detection mechanisms can properly flag the test as\nflaky.","shortMessageHtmlLink":"snapshotter: rewriteWithFailOnDiff"}},{"before":null,"after":"bbbcce312ff9f81619a380b206640490bdb785ff","ref":"refs/heads/jesse/snapshotter-refactor","pushedAt":"2023-05-18T21:24:21.823Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ChenJesse","name":"Jesse Chen","path":"/ChenJesse","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11747956?s=80&v=4"},"commit":{"message":"snapshotter: add check and rewrite option\n\nPrior to this commit, there were only two options:\nrewrite or verify mode.\n\nIf you are in rewrite mode, we rewrite the snapshots and the unit test\nwill never fail on the Verify() call (unless something goes wrong with\nthe mechanics of writing the snapshots file).\n\nElse, if you are in verify mode (the default mode), we will compare the\nsnapshots with the actual values and fail the unit test if there is any\nmismatch.\n\nThis commit introduces a third option: we first verify, and then we\nrewrite the snapshot. This might be a very specialized use-case, but at\nSamsara, we have developer tooling around making it easier to patch\nthese snapshot diffs, which involve the snapshot diffs being generated\n(so we need rewrite mode) and pushed to our CI artifacts bucket for\nlater application, but we also want the unit test to fail so\nthat our CI flake detection mechanisms can properly flag the test as\nflaky.","shortMessageHtmlLink":"snapshotter: add check and rewrite option"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEldYD_wA","startCursor":null,"endCursor":null}},"title":"Activity · samsarahq/go"}