{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":231068,"defaultBranch":"master","name":"wavefile","ownerLogin":"jstrait","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2009-06-19T02:38:02.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/24006?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1672435980.631517","currentOid":""},"activityList":{"items":[{"before":"fb01c5fdc2eba6c8227346961bb25a06524ebb8c","after":"4175e423b93f47f4799d4f42edd12f27f30f2aa9","ref":"refs/heads/master","pushedAt":"2023-11-09T08:00:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Using better field value in fixtures\n\nPreviously, these fixtures all contained a \"smpl\" chunk that used\na value of 0 for the `sample_nanoseconds` field. (I.e. the field\ncalled \"dwSamplePeriod\" in the spec). However, this value doesn't\nseem conceptually valid. It seems better to use the value 22675,\nwhich the spec calls out as the normal value to use when the\n\"fmt \" chunk has a sample rate of 44100 (which is the case for all\nof these fixtures).\n\nThis field value is intentionally not being changed in the\n\"valid/with_sample_chunk_with_fields_out_of_range.wav\" fixture,\nbecause a value of 0 seems to fit with the \"invalid but won't\ncause an error\" theme of that fixture.","shortMessageHtmlLink":"Using better field value in fixtures"}},{"before":"914411eaeab73a260d4ba8243620c863f8f02b79","after":"f22ce7a69d4ae75e894bebc1614c2f291ae8b6b5","ref":"refs/heads/gh-pages","pushedAt":"2023-09-01T04:48:47.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Adding callout about WAVE_FORMAT_EXTENSIBLE format\n\nIt seems helpful to add a special callout for this format, since\nit works differently than the other formats and is not \"just\nanother format\" as was possibly previously implied.","shortMessageHtmlLink":"Adding callout about WAVE_FORMAT_EXTENSIBLE format"}},{"before":"b9102a65ea67c83eccb76e0c6e78cfe20c39a220","after":"fb01c5fdc2eba6c8227346961bb25a06524ebb8c","ref":"refs/heads/master","pushedAt":"2023-08-23T06:59:56.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Using reference data instead of hard-coded value\n\nThis removes duplication of the standard testing sample data.\nAlso, if the standard sample data changes in the future then in\ntheory this removes the need to update this test.","shortMessageHtmlLink":"Using reference data instead of hard-coded value"}},{"before":"c3cf9a6a9a5e4f345266737aec50b29c6122e203","after":"b9102a65ea67c83eccb76e0c6e78cfe20c39a220","ref":"refs/heads/master","pushedAt":"2023-08-22T06:59:58.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Removing duplication in reference sample data\n\nThis hopefully makes it more clear that the sample data is the\nsame for each of these sample formats, and less likely that they\naccidentally become out of sync.","shortMessageHtmlLink":"Removing duplication in reference sample data"}},{"before":"2bd8c791117cafa4b479034e5ff83dd8b9c12c18","after":"c3cf9a6a9a5e4f345266737aec50b29c6122e203","ref":"refs/heads/master","pushedAt":"2023-08-21T06:58:54.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Closing `Reader` instances in tests, for hygiene\n\nThe underlying files opened by these `Reader` instances should be\nautomatically closed when the instances are garbage collected or\nthe `rake test` task exits, but it seems like a good idea to close\nthem anyway to prevent potential problems.","shortMessageHtmlLink":"Closing <code>Reader</code> instances in tests, for hygiene"}},{"before":"1c917c80044d9cc179b254312c84c84788894c1d","after":"2bd8c791117cafa4b479034e5ff83dd8b9c12c18","ref":"refs/heads/master","pushedAt":"2023-08-18T06:59:22.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Removing duplicated logic for building file names\n\nPreviously the tests that used `exhaustively_test()` were\nresponsible for constructing the file name of each test fixture.\nThis led to the logic for this being duplicated in several places.\nAlso, the `format_chunk_format` block argument was only ever used\nfor constructing file names, and not directly in any tests.\n\nNow the file name is instead constructed inside of\n`exhaustively_test()` and passed to the relevant block, in place\nof `format_chunk_format`. This removes duplication and seems to\nsimplify things.","shortMessageHtmlLink":"Removing duplicated logic for building file names"}},{"before":"4e142731dc3070418c1f529ebdf370ddb60bc985","after":"1c917c80044d9cc179b254312c84c84788894c1d","ref":"refs/heads/master","pushedAt":"2023-08-17T07:00:00.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Adding extra test case for `Writer#total_duration`\n\nSince `exhaustively_test()` is no longer used by this test method\nas of commit d5e00eefd3ab91b6639c36f2c80bedbebde61b92 (i.e. the\ncommit before this one), the `:float` sample format can be\nincluded in the tests to improve coverage.\n\nSince a core benefit of the referenced commit was reducing the\ntest suite's run time, and this commit changes the same set of\ntests, it seems potentially interesting to see how this commit\naffects performance. In short, it makes the test suite slightly\nslower.\n\nBelow are the before and after results of running the command\n`rake test` 10 times using Ruby 3.2.2 on my laptop. Note that the\n\"before\" times are reused from the \"after\" times in commit\nd5e00eefd3ab91b6639c36f2c80bedbebde61b92.\n\nBefore\n=================================================================\nAll times: 2.018493s, 2.053932s, 2.137646s, 1.986374s, 2.089508s,\n           2.078087s, 2.061645s, 2.050618s, 2.098642s, 2.165608s\n-----------------------------------------------------------------\nAverage: 2.074055s\nMin:     1.986374s\nMax:     2.165608s\n\nAfter\n=================================================================\nAll times: 2.208204s, 2.165893s, 2.304464s, 2.214399s, 2.169755s,\n           2.186781s, 2.217551s, 2.083759s, 2.201403s, 2.136662s\n-----------------------------------------------------------------\nAverage: 2.188887s (0.114832s slower, a 1.06x decrease)\nMin: 2.083759\nMax: 2.304464","shortMessageHtmlLink":"Adding extra test case for <code>Writer#total_duration</code>"}},{"before":"73f24f08550919af264f8544bfb35b5303d9d5b0","after":"4e142731dc3070418c1f529ebdf370ddb60bc985","ref":"refs/heads/master","pushedAt":"2023-08-10T06:59:38.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Reading sample data in more flexible way in tests\n\n`read_all_samples_using_read()` is no longer responsible for\nopening (and closing) a `Reader` instance in order to read the\nsample data. Instead it is passed a `Reader` instance.\n\nThis provides more flexibility by allowing tests to test a single\n`Reader` instance before and after reading sample data while also\ntaking advantage of `read_all_samples_using_read()`.\n\nIt also removes the need to repeat file names in more than one\nplace in multiple tests. If this functionality had previously been\nin place, the testing bugs fixed in commit\n73f24f08550919af264f8544bfb35b5303d9d5b0 presumably would have\nbeen prevented. (Using variables to store the repeated file names\nwould have also worked, but the point still stands).","shortMessageHtmlLink":"Reading sample data in more flexible way in tests"}},{"before":"6989b7e519fe662eb33c56803cb4ac0a2c6bc9d4","after":"73f24f08550919af264f8544bfb35b5303d9d5b0","ref":"refs/heads/master","pushedAt":"2023-08-09T06:59:46.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Fixing tests to read from the correct files\n\nPreviously in both of these two tests the first and second parts\nof the test incorrectly read from two different files. Presumably\nthis was due to copy-and-pasting these tests from existing tests,\nand not changing the relevant file name in both required places.\n\nThe tests continue to pass after this commit, so presumably there\nwasn't a bug accidentally being hidden.","shortMessageHtmlLink":"Fixing tests to read from the correct files"}},{"before":"16c9647facfc8fee4d6f45e436ac8e340c99fd99","after":"914411eaeab73a260d4ba8243620c863f8f02b79","ref":"refs/heads/gh-pages","pushedAt":"2023-08-02T21:42:47.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Improving note about lack of `Format` validation","shortMessageHtmlLink":"Improving note about lack of <code>Format</code> validation"}},{"before":"1325281389944aeaef7cff80b1d5ffca09bba121","after":"6989b7e519fe662eb33c56803cb4ac0a2c6bc9d4","ref":"refs/heads/master","pushedAt":"2023-07-31T06:59:59.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Reading files in tests in Windows-compatible way\n\nI believe that when reading binary files on Windows the \"rb\" mode\nneeds to be used instead of \"r\". `File.read` uses \"r\" by default,\nunlike `File.binread` which uses \"rb\".\n\nIn theory this means that some of the `Reader` tests might have\nbeen broken when using Windows. I say \"in theory\" because I\ncurrently don't have a Windows machine to test this out on.","shortMessageHtmlLink":"Reading files in tests in Windows-compatible way"}},{"before":"0f2814c90fdacf412adba69547edad28b3bab3f1","after":"1325281389944aeaef7cff80b1d5ffca09bba121","ref":"refs/heads/master","pushedAt":"2023-07-24T06:59:59.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Using \" instead of ' for consistency","shortMessageHtmlLink":"Using \" instead of ' for consistency"}},{"before":"d734e8a5b13f156d20984b021548465fec984d19","after":"0f2814c90fdacf412adba69547edad28b3bab3f1","ref":"refs/heads/master","pushedAt":"2023-07-17T07:00:04.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Improving fixture generation time ~1.3x\n\nThe \"data\" chunk's sample data is the bulk of most of the *.wav\nfixture files, and this commit makes the process of writing this\nsample data more efficient.\n\nBelow are the before and after results of running the command\n`time rake test:create_fixtures` 10 times using Ruby 3.2.2 on my\nlaptop.\n\nBefore\n=================================================================\nAll times: 0.679sec, 0.648sec, 0.613sec, 0.564sec, 0.545sec,\n           0.549sec, 0.554sec, 0.563sec, 0.546sec, 0.556sec\n-----------------------------------------------------------------\nAverage: 0.582sec\nMin:     0.545sec\nMax:     0.679sec\n\nAfter\n============================================================\nAll times: 0.500sec, 0.454sec, 0.503sec, 0.423sec, 0.407sec,\n           0.411sec, 0.406sec, 0.430sec, 0.415sec, 0.411sec\n------------------------------------------------------------\nAverage: 0.436sec (0.146sec faster, a 1.334x improvement)\nMin:     0.406sec\nMax:     0.503sec\n\nNotes:\n\n* After this commit the average run time is 11.443sec faster than\n  the \"before\" average reported in commit\n  4627006dcb780e0b4e6a0761af9baac1c6e0287a, a 27.246x improvement.\n* The \"before\" times are reused from the \"after\" times in\n  preceding commit 4627006dcb780e0b4e6a0761af9baac1c6e0287a.\n  Immediately after running the performance tests for that commit,\n  the changes in this commit were applied using `git revert` and\n  the \"after\" tests for this commit were conducted. It seems more\n  consistent for the \"before\" times in this commit to be reused\n  from the \"after\" times in the previous commit, to avoid the two\n  commits having arbitrarily different measurements.\n* This commit has the same changes as commit\n  d734e8a5b13f156d20984b021548465fec984d19. That commit had\n  incorrect performance measurements so it was reverted in favor\n  of this commit.","shortMessageHtmlLink":"Improving fixture generation time ~1.3x"}},{"before":"8619ea5c8dd0728f50256fc0fcd7215e0459c58d","after":"d734e8a5b13f156d20984b021548465fec984d19","ref":"refs/heads/master","pushedAt":"2023-07-12T06:59:38.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Improving fixture generation time ~3.3x\n\nThe \"data\" chunk's sample data is the bulk of most of the *.wav\nfixture files, and this commit makes the process of writing this\nsample data more efficient.\n\nBelow are the before and after results of running the command\n`time rake test:create_fixtures` 10 times using Ruby 3.2.2 on my\nlaptop.\n\nBefore\n============================================================\nAll times: 1.466sec, 1.541sec, 1.492sec, 1.473sec, 1.499sec,\n           1.452sec, 1.534sec, 1.522sec, 1.473sec, 1.504sec\n------------------------------------------------------------\nAverage:   1.496sec\nMin:       1.452sec\nMax:       1.541sec\n\nAfter\n============================================================\nAll times: 0.506sec, 0.480sec, 0.429sec, 0.403sec, 0.431sec,\n           0.443sec, 0.462sec, 0.444sec, 0.435sec, 0.454sec\n------------------------------------------------------------\nAverage:   0.449sec (1.047sec faster, 3.332x improvement)\nMin:       0.403sec\nMax:       0.506sec\n\nAlso note that after this commit the average run time is 13.316sec\nfaster than the \"before\" average reported in commit\n8d9ea990f54f32858648be1557d47e344578a852, a 30.657x improvement.","shortMessageHtmlLink":"Improving fixture generation time ~3.3x"}},{"before":"e561db74a49c624c10cf8604d290651176adec5e","after":"8619ea5c8dd0728f50256fc0fcd7215e0459c58d","ref":"refs/heads/master","pushedAt":"2023-07-07T07:00:02.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"More specific variable name to improve clarity","shortMessageHtmlLink":"More specific variable name to improve clarity"}},{"before":"dcbed96c35f1d5ca4b0ba6a23bb7fac9b4be775a","after":"e561db74a49c624c10cf8604d290651176adec5e","ref":"refs/heads/master","pushedAt":"2023-07-06T07:00:01.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Fixing two \"RIFF\" chunk sizing bugs for fixtures\n\nPreviously, if a fixture's YAML config had the \"RIFF\" chunk size\nset to \"auto\" and there was also a \"data\" chunk, two bugs in the\nautomatic sizing calculation cancelled each other out, leading to\nan accidentally correct result. This commit fixes the logic to be\ncorrect for the correct reasons, and removes a possible source of\nerror in the future.\n\nThe first bug was that the \"RIFF\" chunk's FourCC and size fields\nwere erroneously added to the calculated chunk size, leading it to\nbeing 8 bytes too large. The second bug was that the \"data\" chunk\nFourCC and size fields _weren't_ included, leading to 8 bytes not\nbeing accounted for.\n\nIf the fixture had a \"data\" chunk, the extra 8 bytes and missing 8\nbytes cancelled each other out and the \"RIFF\" chunk size was\ncorrect.\n\nIf there wasn't a \"data\" chunk, the \"RIFF\" chunk size was 8 bytes\ntoo large. However, that didn't affect any fixtures because there\naren't currently aren't any that have a \"RIFF\" chunk size of\n\"auto\" and are also missing a \"data\" chunk.\n\nA known issue is that the calculated \"RIFF\" chunk size will be\nincorrect if the \"data\" chunk header is partially complete (i.e.\npresent but less than 8 bytes in size). However, that is a pre-\nexisting issue and also affects the other chunks types. That\ncan be fixed in a different commit.","shortMessageHtmlLink":"Fixing two \"RIFF\" chunk sizing bugs for fixtures"}},{"before":"3366660427b047d71d6a3021fdb79a098acf83af","after":"dcbed96c35f1d5ca4b0ba6a23bb7fac9b4be775a","ref":"refs/heads/master","pushedAt":"2023-07-05T00:19:52.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Fixing \"RIFF\" chunk size in several fixtures\n\nPreviously, the \"RIFF\" chunk size (automatically calculated due to\nthe \"auto\" value in the YAML config) in each of these fixtures was\nsmaller than the number of remaining bytes in the file. This meant\nthat some bytes intended to be part of the main \"RIFF\" chunk\ninstead came after it. The automatic \"RIFF\" chunk size calculation\nonly goes off the sizes that chunks report, so it's not a good fit\nfor fixtures such as these that have chunks with intentionally\nwrong sizes.\n\nIn practice I don't think this caused any testing issues. When\nreading each of these fixtures a problem with the \"fmt \" chunk\nwill cause an error to be raised before the end of the file is\nreached. However, to prevent multiple sources of error, it seems\nlike a good idea for the \"RIFF\" chunk size in each fixture to\naccurately reflect the number of bytes present.","shortMessageHtmlLink":"Fixing \"RIFF\" chunk size in several fixtures"}},{"before":"990ecc3f73d224bc88c1b839096567c2a1753e9c","after":"3366660427b047d71d6a3021fdb79a098acf83af","ref":"refs/heads/master","pushedAt":"2023-07-03T06:59:54.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Fixing \"RIFF\" chunk size in fixture\n\nPreviously, the \"RIFF\" chunk size (automatically calculated due to\nthe \"auto\" value in the YAML config) was 36, 4 bytes larger than\nthe actual number of remaining bytes in the file. The reason was\nthat the automatic \"RIFF\" chunk size calculation doesn't work\nproperly for chunks with a partially complete header. Although the\nautomatic size calculation could be improved, it seems more\nstraightforward to manually set the \"data\" chunk size for now.\n\nThis shouldn't change the results of any tests because both the\nold and new versions of this fixture cause `InvalidFormatError` to\nbe raised with the same \"Unexpected end of file\" message when\nattempting to read it.","shortMessageHtmlLink":"Fixing \"RIFF\" chunk size in fixture"}},{"before":"7a48cb1ac8db000ec30aa71b4d09946c78a0c408","after":"990ecc3f73d224bc88c1b839096567c2a1753e9c","ref":"refs/heads/master","pushedAt":"2023-07-02T07:00:01.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Better variable name `pack_code`->`pack_template`\n\nThe Ruby documentation for `Array#pack` calls the type of value\nheld in this variable a \"template string\", and the relevant\nargument for `FileWriter#write_value` is called `pack_template`.\nThe new variable name is consistent with this terminology.","shortMessageHtmlLink":"Better variable name <code>pack_code</code>-&gt;<code>pack_template</code>"}},{"before":"d8963ce16f6a3142200b7daa21a8a88d29aa3394","after":"7a48cb1ac8db000ec30aa71b4d09946c78a0c408","ref":"refs/heads/master","pushedAt":"2023-06-29T07:00:03.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Removing `channel_format` fixture config field\n\nThis field (part of the \"data\" chunk config) matched the channel\ncount from the \"fmt\" chunk config in all fixtures that have sample\ndata present. Maybe in the future it might be useful to manually\nconfigure the channel count (and sample format, etc.) for cases\nwhere e.g. an invalid fixture has two \"fmt \" chunks. But until\nthen it doesn't need to be present, and in those future cases it\ncan be optional.","shortMessageHtmlLink":"Removing <code>channel_format</code> fixture config field"}},{"before":"15d3b0044a9eac347c980b8e4551efdaf3ccfb10","after":"d8963ce16f6a3142200b7daa21a8a88d29aa3394","ref":"refs/heads/master","pushedAt":"2023-06-27T05:36:30.667Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Skipping missing values when writing fixtures\n\nPreviously, a missing value for most fixture fields would cause\nwriting data to the fixture *.wav file to stop. However, this was\nnot a very flexible approach, because it prevented writing a\npartial chunk followed by other chunks.\n\nIn fact, this caused the `invalid/smpl_chunk_empty.wav` fixture to\nbe inadvertantly missing the \"data\" chunk. This caused the fixture\nto have more than one source of error, which could have led to an\nincorrect test result. (It didn't, but in theory it could have).\n\nAfter this commit, missing fixture field values will always be\nskipped and writing will continue to the next field, except when\nattempting to write sample data with an unsupported format.","shortMessageHtmlLink":"Skipping missing values when writing fixtures"}},{"before":"efc12657d5d89cb047478d7a9b9f4b65cc95073c","after":"15d3b0044a9eac347c980b8e4551efdaf3ccfb10","ref":"refs/heads/master","pushedAt":"2023-06-17T06:59:49.823Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"More accurate size for \"smpl\" chunk in fixture\n\nThe previous \"smpl\" chunk size prevented the (truncated) \"sampler\nspecific data\" field from being included in the chunk. It was\nstill present in the file, but after the end of the \"RIFF\" chunk.\n\nThis commit shouldn't change the semantics of the relevant test\nbecause in both the old and new fixture version the \"sampler\nspecific data size\" field should be too large. However, it seems\nbetter for the fixture to be set up as actually intended.","shortMessageHtmlLink":"More accurate size for \"smpl\" chunk in fixture"}},{"before":"5b77194848c5362d4cdedc396ca4c6f00172c204","after":"efc12657d5d89cb047478d7a9b9f4b65cc95073c","ref":"refs/heads/master","pushedAt":"2023-06-14T06:57:32.736Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Renaming fixture for consistency\n\nThe new name is more consistent both with other fixtures that\ninvolve an invalid \"smpl\" chunk, as well as other fixtures that\ninvolve a chunk being prematurely truncated.","shortMessageHtmlLink":"Renaming fixture for consistency"}},{"before":"02c3d08b47c7de1b709dda7ba9b7c495853fb211","after":"16c9647facfc8fee4d6f45e436ac8e340c99fd99","ref":"refs/heads/gh-pages","pushedAt":"2023-05-12T01:19:36.614Z","pushType":"push","commitsCount":1,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Fixing description of sub format GUID bytes\n\nThe previous description incorrectly implied the 2 byte format tag\ncomes after the other 14 bytes, instead of before.","shortMessageHtmlLink":"Fixing description of sub format GUID bytes"}},{"before":"a3873b6f2023874c0d745a23628b5bbcd729510e","after":"5b77194848c5362d4cdedc396ca4c6f00172c204","ref":"refs/heads/master","pushedAt":"2023-04-04T06:59:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Removing \"valid_\" prefix from fixture file names\n\nThis allows these sometimes long file names to be a little\nshorter, and avoids redundancy since these files are already\ncontained in a folder named \"valid\".","shortMessageHtmlLink":"Removing \"valid_\" prefix from fixture file names"}},{"before":"da3cf6a625bfb7af84f65bfe4acea9ed4edc6dff","after":"a3873b6f2023874c0d745a23628b5bbcd729510e","ref":"refs/heads/master","pushedAt":"2023-04-02T06:59:58.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Debug: Fields incomplete due to EOF are shown\n\nPreviously, if an unexpected end-of-file error prevented some of\nthe bytes for a field from being read, the field would not be\nshown in the output. Now it will be (if at least one byte can be\nread), with missing bytes displayed as \"__\". This matches how\nfields that are prematurely cut off due to overflowing the\ncontaining chunk or chunk subsection are displayed, and helps to\ngive a more accurate view of the file's contents.","shortMessageHtmlLink":"Debug: Fields incomplete due to EOF are shown"}},{"before":"115a277d5989797f76c904e4ea04109a53879a3e","after":"da3cf6a625bfb7af84f65bfe4acea9ed4edc6dff","ref":"refs/heads/master","pushedAt":"2023-03-31T06:59:48.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Debug: Extracting variables","shortMessageHtmlLink":"Debug: Extracting variables"}},{"before":"48fb7783f32f0e455f5eec46c709b11ba3a1c46d","after":"115a277d5989797f76c904e4ea04109a53879a3e","ref":"refs/heads/master","pushedAt":"2023-03-29T07:07:44.341Z","pushType":"push","commitsCount":3,"pusher":{"login":"jstrait","name":"Joel Strait","path":"/jstrait","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24006?s=80&v=4"},"commit":{"message":"Debug: Better location for class definition\n\nThis places `ByteLimitExhaustedError` next to the closely related\n`ByteLimit` class. It also seems better to not place it at the\nbeginning of the class definition, since it is an implementation\ndetail.","shortMessageHtmlLink":"Debug: Better location for class definition"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADqw3T9wA","startCursor":null,"endCursor":null}},"title":"Activity · jstrait/wavefile"}