You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! We have been using the semantic-release/git + the changelog plugin for a few weeks to automatically generate the CHANGELOG.md and we saw this error failed: git ls-files -m -o\nmaxBuffer exceeded' intermittently.
full error message:
Full error message
[5:23:56 PM] [semantic-release] › ℹ Running semantic-release version 23.0.2
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/github"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/changelog"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/git"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/changelog"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/git"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[5:23:56 PM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[5:23:58 PM] [semantic-release] › ✔ Run automated release from branch master on repository https://github.com/org/our-repo-name.git
[5:23:58 PM] [semantic-release] › ✔ Allowed to push to the Git repository
[5:23:58 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/github"
[5:23:58 PM] [semantic-release] [@semantic-release/github] › ℹ Verify GitHub authentication
[5:23:58 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/github"
[5:23:58 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/changelog"
[5:23:58 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/changelog"
[5:23:58 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/git"
[5:23:58 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/git"
[5:23:58 PM] [semantic-release] › ℹ Found git tag v1.4.3 associated with version 1.4.3 on branch master
[5:23:58 PM] [semantic-release] › ℹ Found 1 commits since last release
[5:23:58 PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[5:23:58 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: fix: Something
[5:23:58 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is patch
[5:23:58 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 1 commits complete: patch release
[5:23:58 PM] [semantic-release] › ✔ Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[5:23:58 PM] [semantic-release] › ℹ The next release version is 1.4.4
[5:23:58 PM] [semantic-release] › ℹ Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[5:23:59 PM] [semantic-release] › ✔ Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[5:23:59 PM] [semantic-release] › ℹ Start step "prepare" of plugin "@semantic-release/changelog"
[5:23:59 PM] [semantic-release] [@semantic-release/changelog] › ℹ Update /CHANGELOG.md
[5:23:59 PM] [semantic-release] › ✔ Completed step "prepare" of plugin "@semantic-release/changelog"
[5:23:59 PM] [semantic-release] › ℹ Start step "prepare" of plugin "@semantic-release/git"
[5:24:07 PM] [semantic-release] › ✘ Failed step "prepare" of plugin "@semantic-release/git"
[5:24:08 PM] [semantic-release] › ✘ An error occurred while running semantic-release: MaxBufferError: Command failed: git ls-files -m -o
maxBuffer exceeded
.dockerenv
FAILURE_REASON
bin/arch
bin/ash
...omit many lines in-between...
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/alloc_calls
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/cache_dma
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/cpu_partial
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/cpu_slabs
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/ctor
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/destroy_by_rcu
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/free_calls
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/hwcache_align
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/min_partial
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/object_size
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/objects
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/objects_partial
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/objs_per_slab
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/order
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/partial
17:24:16 sys/kernel/slab/:A-0001024/cgroup/signal_cache(107758:8d0201d2261a3edce188de203f06bb40d386bac659d300d08e5f46996c21d35e)/poison
17:24:16 at PassThrough.<anonymous> �[90m(/u�[39msr/local/lib/node_modules/�[4m@semantic-release�[24m/git/node_modules/�[4mget-stream�[24m/index.js:50:19�[90m)�[39m
17:24:16 �[90m at PassThrough.emit (node:events:530:35)�[39m
17:24:16 �[90m at addChunk (node:internal/streams/readable:559:12)�[39m
17:24:16 �[90m at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)�[39m
17:24:16 �[90m at Readable.push (node:internal/streams/readable:390:5)�[39m
17:24:16 �[90m at node:internal/streams/transform:178:12�[39m
17:24:16 �[90m at PassThrough._transform (node:internal/streams/passthrough:46:3)�[39m
17:24:16 �[90m at Transform._write (node:internal/streams/transform:171:8)�[39m
17:24:16 �[90m at writeOrBuffer (node:internal/streams/writable:564:12)�[39m
17:24:16 �[90m at _write (node:internal/streams/writable:493:10)�[39m {
17:24:16 originalMessage: �[32m'maxBuffer exceeded'�[39m,
17:24:16 shortMessage: �[32m'Command failed: git ls-files -m -o\nmaxBuffer exceeded'�[39m,
CI environment: Jenkins CI
VCS: GitHub
semantic-release version: 23.0.2
semantic-release/release-notes-generator version: 12.1.0
semantic-release/git version: 10.0.1 package.json
Hello! We have been using the semantic-release/git + the changelog plugin for a few weeks to automatically generate the
CHANGELOG.md
and we saw this errorfailed: git ls-files -m -o\nmaxBuffer exceeded'
intermittently.full error message:
Full error message
CI environment:
Jenkins CI
VCS: GitHub
semantic-release version:
23.0.2
semantic-release/release-notes-generator version:
12.1.0
semantic-release/git version:
10.0.1
package.json
package.json
I am wondering if anyone else is also encountering this and if our setting can be improved to avoid the error.
The text was updated successfully, but these errors were encountered: