|                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:146:5)

  ● running version in a simple project › when there are multiple changeset commits › should bump releasedPackages

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-psg3pV/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:158:7)

  ● running version in a simple project › when there are multiple changeset commits › should bump multiple released packages if required

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-5ksr0S/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:171:7)

  ● running version in a simple project › when there are multiple changeset commits › should delete the changeset files

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-sMazIQ/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:190:7)

  ● running version in a simple project with workspace range › When there is a changeset commit › should bump releasedPackages

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-sztsyO/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:216:7)

  ● pre › should work

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/0f631048bff19bced5ac1790a8d22a98/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:245:5)

  ● pre › should work with adding a package while in pre mode

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/3a744b1c4a88d570bf00a639759e93f3/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:440:5)

  ● pre › should work for my weird case

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/8ed87c7152b864c8e19a0d9e7f1e3f95/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:500:5)

  ● pre › should work with linked

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/bf694c9566e182ebca7c6ee9938468a5/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:551:5)

  ● pre › should use the highest bump type for between all prereleases for every prerelease

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/7fe829922468c582939cc40849ea9728/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:640:5)

 PASS  packages/get-dependents-graph/src/get-dependency-graph.test.ts
  ● Console

    console.error packages/get-dependents-graph/src/get-dependency-graph.ts:78
      Package "foo" must depend on the current version of "bar": "1.0.0" vs "link:../bar"

 FAIL  packages/pre/src/index.test.ts
  ● enterPre › should throw if already in pre

    expect(received).rejects.toBeInstanceOf(expected)

    Expected constructor: PreEnterButInPreModeError
    Received constructor: PreEnterButInPreModeError

      36 |       preStateForSimpleProject
      37 |     );
    > 38 |     await expect(enterPre(cwd, "some-tag")).rejects.toBeInstanceOf(
         |                                                     ^
      39 |       PreEnterButInPreModeError
      40 |     );
      41 |   });

      at Object.toBeInstanceOf (node_modules/expect/build/index.js:242:20)
      at Object.<anonymous> (packages/pre/src/index.test.ts:38:53)

  ● exitPre › should throw if not in pre

    expect(received).rejects.toBeInstanceOf(expected)

    Expected constructor: PreExitButNotInPreModeError
    Received constructor: PreExitButNotInPreModeError

      57 |   it("should throw if not in pre", async () => {
      58 |     let cwd = f.copy("simple-project");
    > 59 |     await expect(exitPre(cwd)).rejects.toBeInstanceOf(
         |                                        ^
      60 |       PreExitButNotInPreModeError
      61 |     );
      62 |   });

      at Object.toBeInstanceOf (node_modules/expect/build/index.js:242:20)
      at Object.<anonymous> (packages/pre/src/index.test.ts:59:40)

 PASS  packages/write/src/index.test.ts
 PASS  packages/test-utils/src/index.test.ts
 FAIL  packages/apply-release-plan/src/index.test.ts (6.034s)
  ● Console

    console.error packages/apply-release-plan/src/index.ts:154
      Changesets ran into trouble committing your files
    console.error packages/apply-release-plan/src/index.ts:154
      Changesets ran into trouble committing your files

  ● apply release plan › changelogs › should update a changelog for one package

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-pkFsJW/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:291:30)

  ● apply release plan › changelogs › should update a changelog for two packages

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-w7fPYS/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:329:30)

  ● apply release plan › changelogs › should not update the changelog if only devDeps changed

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-4iz6gP/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:367:30)

  ● apply release plan › changelogs › should list multi-line same-type summaries correctly

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-VMrpCL/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:431:30)

  ● apply release plan › should error and not write if › a package cannot be found

    expect(received).toEqual(expected) // deep equality

    Expected: true
    Received: false

      538 |         let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      539 |
    > 540 |         expect(gitCmd.stdout.toString().includes("nothing to commit")).toEqual(
          |                                                                        ^
      541 |           true
      542 |         );
      543 |         return;

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:540:72)

  ● apply release plan › should error and not write if › a provided changelog function fails

    expect(received).toEqual(expected) // deep equality

    - Expected
    + Received

    - no chance
    + Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/failing-functions'
    + Require stack:
    + - /tmp/jest-fixture-2lu9TE/.changeset/noop.js

      569 |         );
      570 |       } catch (e) {
    > 571 |         expect(e.message).toEqual("no chance");
          |                           ^
      572 |
      573 |         let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      574 |

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:571:27)

  ● apply release plan › should get the commit for an old changeset

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-xZ9Lvx/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:688:23)

  ● apply release plan › git › should commit updating files from packages

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      733 |       let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      734 |
    > 735 |       expect(gitCmd.stdout.toString().includes("nothing to commit")).toBe(true);
          |                                                                      ^
      736 |
      737 |       let lastCommit = await spawn("git", ["log", "-1"], { cwd: tempDir });
      738 |

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:735:70)

  ● apply release plan › git › should commit removing applied changesets

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      774 |       let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      775 |
    > 776 |       expect(gitCmd.stdout.toString().includes("nothing to commit")).toBe(true);
          |                                                                      ^
      777 |     });
      778 |   });
      779 | });

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:776:70)

 PASS  packages/errors/src/index.test.ts
 PASS  packages/get-version-range-type/src/index.test.ts
 PASS  packages/cli/src/commands/publish/__tests__/releaseCommand.test.ts
 PASS  packages/cli/src/commands/publish/__tests__/publishPackages.test.ts
  ● Console

    console.info packages/logger/dist/logger.cjs.dev.js:21
      🦋  info pkg-a is being published because our local version (1.0.0) has not been published on npm
    console.info packages/logger/dist/logger.cjs.dev.js:21
      🦋  info pkg-b is being published because our local version (1.0.0) has not been published on npm
    console.info packages/logger/dist/logger.cjs.dev.js:21
      🦋  info Publishing "pkg-a" at "1.0.0"
    console.info packages/logger/dist/logger.cjs.dev.js:21
      🦋  info Publishing "pkg-b" at "1.0.0"

 FAIL  packages/git/src/index.test.ts (7.358s)
  ● git › add › should add a directory

    expect(received).toHaveLength(expected)

    Expected length: 4
    Received length: 6
    Received array:  ["packages/pkg-a/index.js", "packages/pkg-a/node_modules/.pnpm/lock.yaml", "packages/pkg-a/node_modules/pkg-b", "packages/pkg-a/package.json", "packages/pkg-b/index.js", "packages/pkg-b/package.json"]

      111 |         .filter(a => a);
      112 |
    > 113 |       expect(stagedFiles).toHaveLength(4);
          |                           ^
      114 |       expect(stagedFiles[0]).toEqual("packages/pkg-a/index.js");
      115 |       expect(stagedFiles[1]).toEqual("packages/pkg-a/package.json");
      116 |       expect(stagedFiles[2]).toEqual("packages/pkg-b/index.js");

      at Object.<anonymous> (packages/git/src/index.test.ts:113:27)

Summary of all failing tests
 FAIL  packages/read/src/index.test.ts
  ● read changesets from disc › should read a changeset from disc

    could not parse changeset - invalid frontmatter: ---
    "cool-package": minor
    ---

    Nice simple summary

      12 |
      13 |   if (!execResult) {
    > 14 |     throw new Error(`could not parse changeset - invalid frontmatter: ${contents}`);
         |           ^
      15 |   }
      16 |
      17 |   let [, roughReleases, roughSummary] = execResult;

      at parseChangesetFile (packages/parse/dist/parse.cjs.dev.js:14:11)
      at packages/read/src/index.ts:57:17
          at async Promise.all (index 0)
      at getChangesets (packages/read/src/index.ts:61:9)
      at Object.<anonymous> (packages/read/src/index.test.ts:15:24)

  ● read changesets from disc › should ignore a readme file

    could not parse changeset - invalid frontmatter: ---
    "cool-package": minor
    ---

    Nice simple summary

      12 |
      13 |   if (!execResult) {
    > 14 |     throw new Error(`could not parse changeset - invalid frontmatter: ${contents}`);
         |           ^
      15 |   }
      16 |
      17 |   let [, roughReleases, roughSummary] = execResult;

      at parseChangesetFile (packages/parse/dist/parse.cjs.dev.js:14:11)
      at packages/read/src/index.ts:57:17
          at async Promise.all (index 0)
      at getChangesets (packages/read/src/index.ts:61:9)
      at Object.<anonymous> (packages/read/src/index.test.ts:27:24)

  ● read changesets from disc › read a changeset that isn't a three word id

    could not parse changeset - invalid frontmatter: ---
    "cool-package": minor
    ---

    Nice simple summary

      12 |
      13 |   if (!execResult) {
    > 14 |     throw new Error(`could not parse changeset - invalid frontmatter: ${contents}`);
         |           ^
      15 |   }
      16 |
      17 |   let [, roughReleases, roughSummary] = execResult;

      at parseChangesetFile (packages/parse/dist/parse.cjs.dev.js:14:11)
      at packages/read/src/index.ts:57:17
          at async Promise.all (index 0)
      at getChangesets (packages/read/src/index.ts:61:9)
      at Object.<anonymous> (packages/read/src/index.test.ts:41:24)

  ● read changesets from disc › should read many changesets from disc

    could not parse changeset - invalid frontmatter: ---
    "cool-package": minor
    ---

    Nice simple summary

      12 |
      13 |   if (!execResult) {
    > 14 |     throw new Error(`could not parse changeset - invalid frontmatter: ${contents}`);
         |           ^
      15 |   }
      16 |
      17 |   let [, roughReleases, roughSummary] = execResult;

      at parseChangesetFile (packages/parse/dist/parse.cjs.dev.js:14:11)
      at packages/read/src/index.ts:57:17
          at async Promise.all (index 0)
      at getChangesets (packages/read/src/index.ts:61:9)
      at Object.<anonymous> (packages/read/src/index.test.ts:53:24)

  ● read changesets from disc › should return no releases and empty summary when the changeset is emtpy

    expect(received).rejects.toThrow(expected)

    Expected substring: "could not parse changeset - invalid frontmatter: ---·
    \"cool-package\": minor·
    --·
    Everything is wrong"
    Received message:   "could not parse changeset - invalid frontmatter: ---···
    \"cool-package\": minor···
    --···
    Everything is wrong·
    "

          12 |
          13 |   if (!execResult) {
        > 14 |     throw new Error(`could not parse changeset - invalid frontmatter: ${contents}`);
             |           ^
          15 |   }
          16 |
          17 |   let [, roughReleases, roughSummary] = execResult;

          at parseChangesetFile (packages/parse/dist/parse.cjs.dev.js:14:11)
          at packages/read/src/index.ts:57:17
              at async Promise.all (index 0)
          at getChangesets (packages/read/src/index.ts:61:9)

      88 |     const changesetPath = f.find("broken-changeset");
      89 |
    > 90 |     expect(read(changesetPath)).rejects.toThrow(
         |                                         ^
      91 |       outdent`could not parse changeset - invalid frontmatter: ---
      92 |
      93 |       "cool-package": minor

      at Object.toThrow (node_modules/expect/build/index.js:242:20)
      at Object.<anonymous> (packages/read/src/index.test.ts:90:41)

  ● read changesets from disc › should read an old changeset

    could not parse changeset - invalid frontmatter: ---
    ---

      12 |
      13 |   if (!execResult) {
    > 14 |     throw new Error(`could not parse changeset - invalid frontmatter: ${contents}`);
         |           ^
      15 |   }
      16 |
      17 |   let [, roughReleases, roughSummary] = execResult;

      at parseChangesetFile (packages/parse/dist/parse.cjs.dev.js:14:11)
      at packages/read/src/index.ts:57:17
          at async Promise.all (index 0)
      at getChangesets (packages/read/src/index.ts:61:9)
      at Object.<anonymous> (packages/read/src/index.test.ts:103:24)

  ● read changesets from disc › should read an old changeset

    expect(received).toEqual(expected) // deep equality

    - Expected
    + Received

    @@ -5,9 +5,9 @@
            Object {
              "name": "cool-package",
              "type": "minor",
            },
          ],
    -     "summary": "Nice simple summary
    +     "summary": "Nice simple summary
      ",
        },
      ]

      114 |
      115 |     const changesets = await read(changesetPath);
    > 116 |     expect(changesets).toEqual([
          |                        ^
      117 |       {
      118 |         releases: [{ name: "cool-package", type: "minor" }],
      119 |         summary: "Nice simple summary\n",

      at Object.<anonymous> (packages/read/src/index.test.ts:116:24)

 FAIL  packages/cli/src/commands/version/version.test.ts (5.515s)
  ● running version in a simple project › When there is a changeset commit › should bump releasedPackages

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-Sf9sG8/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:112:7)

  ● running version in a simple project › should bump packages to the correct versions when packages are linked

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-C9Myc3/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:128:5)

  ● running version in a simple project › should not break when there is a linked package without a changeset

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-NLTVWX/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:146:5)

  ● running version in a simple project › when there are multiple changeset commits › should bump releasedPackages

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-psg3pV/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:158:7)

  ● running version in a simple project › when there are multiple changeset commits › should bump multiple released packages if required

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-5ksr0S/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:171:7)

  ● running version in a simple project › when there are multiple changeset commits › should delete the changeset files

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-sMazIQ/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:190:7)

  ● running version in a simple project with workspace range › When there is a changeset commit › should bump releasedPackages

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/jest-fixture-sztsyO/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:216:7)

  ● pre › should work

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/0f631048bff19bced5ac1790a8d22a98/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:245:5)

  ● pre › should work with adding a package while in pre mode

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/3a744b1c4a88d570bf00a639759e93f3/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:440:5)

  ● pre › should work for my weird case

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/8ed87c7152b864c8e19a0d9e7f1e3f95/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:500:5)

  ● pre › should work with linked

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/bf694c9566e182ebca7c6ee9938468a5/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:551:5)

  ● pre › should use the highest bump type for between all prereleases for every prerelease

    Cannot find module '/mnt/c/src/changesets/packages/cli/src/changelog'
    Require stack:
    - /tmp/7fe829922468c582939cc40849ea9728/simple-project/.changeset/noop.js

      247 |     changelogOpts = changelogConfig[1];
      248 |     let changesetPath = path.join(cwd, ".changeset");
    > 249 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      250 |
      251 |     let possibleChangelogFunc = require(changelogPath);
      252 |

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at resolveFrom (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:249:25)
      at applyReleasePlan (packages/apply-release-plan/dist/apply-release-plan.cjs.dev.js:157:37)
      at version (packages/cli/src/commands/version/index.ts:54:9)
      at Object.<anonymous> (packages/cli/src/commands/version/version.test.ts:640:5)

 FAIL  packages/pre/src/index.test.ts
  ● enterPre › should throw if already in pre

    expect(received).rejects.toBeInstanceOf(expected)

    Expected constructor: PreEnterButInPreModeError
    Received constructor: PreEnterButInPreModeError

      36 |       preStateForSimpleProject
      37 |     );
    > 38 |     await expect(enterPre(cwd, "some-tag")).rejects.toBeInstanceOf(
         |                                                     ^
      39 |       PreEnterButInPreModeError
      40 |     );
      41 |   });

      at Object.toBeInstanceOf (node_modules/expect/build/index.js:242:20)
      at Object.<anonymous> (packages/pre/src/index.test.ts:38:53)

  ● exitPre › should throw if not in pre

    expect(received).rejects.toBeInstanceOf(expected)

    Expected constructor: PreExitButNotInPreModeError
    Received constructor: PreExitButNotInPreModeError

      57 |   it("should throw if not in pre", async () => {
      58 |     let cwd = f.copy("simple-project");
    > 59 |     await expect(exitPre(cwd)).rejects.toBeInstanceOf(
         |                                        ^
      60 |       PreExitButNotInPreModeError
      61 |     );
      62 |   });

      at Object.toBeInstanceOf (node_modules/expect/build/index.js:242:20)
      at Object.<anonymous> (packages/pre/src/index.test.ts:59:40)

 FAIL  packages/apply-release-plan/src/index.test.ts (6.034s)
  ● apply release plan › changelogs › should update a changelog for one package

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-pkFsJW/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:291:30)

  ● apply release plan › changelogs › should update a changelog for two packages

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-w7fPYS/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:329:30)

  ● apply release plan › changelogs › should not update the changelog if only devDeps changed

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-4iz6gP/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:367:30)

  ● apply release plan › changelogs › should list multi-line same-type summaries correctly

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-VMrpCL/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:431:30)

  ● apply release plan › should error and not write if › a package cannot be found

    expect(received).toEqual(expected) // deep equality

    Expected: true
    Received: false

      538 |         let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      539 |
    > 540 |         expect(gitCmd.stdout.toString().includes("nothing to commit")).toEqual(
          |                                                                        ^
      541 |           true
      542 |         );
      543 |         return;

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:540:72)

  ● apply release plan › should error and not write if › a provided changelog function fails

    expect(received).toEqual(expected) // deep equality

    - Expected
    + Received

    - no chance
    + Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/failing-functions'
    + Require stack:
    + - /tmp/jest-fixture-2lu9TE/.changeset/noop.js

      569 |         );
      570 |       } catch (e) {
    > 571 |         expect(e.message).toEqual("no chance");
          |                           ^
      572 |
      573 |         let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      574 |

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:571:27)

  ● apply release plan › should get the commit for an old changeset

    Cannot find module '/mnt/c/src/changesets/packages/apply-release-plan/src/test-utils/simple-get-changelog-entry'
    Require stack:
    - /tmp/jest-fixture-xZ9Lvx/.changeset/noop.js

      174 |     changelogOpts = changelogConfig[1];
      175 |     let changesetPath = path.join(cwd, ".changeset");
    > 176 |     let changelogPath = resolveFrom(changesetPath, changelogConfig[0]);
          |                         ^
      177 |
      178 |     let possibleChangelogFunc = require(changelogPath);
      179 |     if (possibleChangelogFunc.default) {

      at resolveFileName (node_modules/resolve-from/index.js:29:39)
      at resolveFrom (node_modules/resolve-from/index.js:43:9)
      at Object.<anonymous>.module.exports (node_modules/resolve-from/index.js:46:47)
      at getNewChangelogEntry (packages/apply-release-plan/src/index.ts:176:25)
      at applyReleasePlan (packages/apply-release-plan/src/index.ts:69:37)
      at testSetup (packages/apply-release-plan/src/index.test.ts:86:25)
      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:688:23)

  ● apply release plan › git › should commit updating files from packages

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      733 |       let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      734 |
    > 735 |       expect(gitCmd.stdout.toString().includes("nothing to commit")).toBe(true);
          |                                                                      ^
      736 |
      737 |       let lastCommit = await spawn("git", ["log", "-1"], { cwd: tempDir });
      738 |

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:735:70)

  ● apply release plan › git › should commit removing applied changesets

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      774 |       let gitCmd = await spawn("git", ["status"], { cwd: tempDir });
      775 |
    > 776 |       expect(gitCmd.stdout.toString().includes("nothing to commit")).toBe(true);
          |                                                                      ^
      777 |     });
      778 |   });
      779 | });

      at Object.<anonymous> (packages/apply-release-plan/src/index.test.ts:776:70)

 FAIL  packages/git/src/index.test.ts (7.358s)
  ● git › add › should add a directory

    expect(received).toHaveLength(expected)

    Expected length: 4
    Received length: 6
    Received array:  ["packages/pkg-a/index.js", "packages/pkg-a/node_modules/.pnpm/lock.yaml", "packages/pkg-a/node_modules/pkg-b", "packages/pkg-a/package.json", "packages/pkg-b/index.js", "packages/pkg-b/package.json"]

      111 |         .filter(a => a);
      112 |
    > 113 |       expect(stagedFiles).toHaveLength(4);
          |                           ^
      114 |       expect(stagedFiles[0]).toEqual("packages/pkg-a/index.js");
      115 |       expect(stagedFiles[1]).toEqual("packages/pkg-a/package.json");
      116 |       expect(stagedFiles[2]).toEqual("packages/pkg-b/index.js");

      at Object.<anonymous> (packages/git/src/index.test.ts:113:27)

Test Suites: 5 failed, 17 passed, 22 total
Tests:       30 failed, 3 skipped, 125 passed, 158 total
Snapshots:   13 passed, 13 total
Time:        10.126s
Ran all test suites.
error Command failed with exit code 1.

Seems like most of the issue is due to the reliance on jest-fixtures, which uses not a cross-platform solution to get the temp directory
https://github.com/Thinkmill/jest-fixtures/blob/98944b9579e1cc911d3f5aaa2cff672801ba88f2/index.js#L12


mmdet cannot train with single class dataset

Since PR https://github.com/open-mmlab/mmdetection/pull/4508, single class training has been broken.
I create a new dataset class as:
from .builder import DATASETS
from .coco import CocoDataset

@DATASETS.register_module()
class NewCocoDataset(CocoDataset):

    CLASSES = ('uav')

Then when i start training with ssd512 config, i get this error:
The `num_classes` (1) in SSDHead of MMDataParallel does not matches the length of `CLASSES` 3) in NewCocoDataset
  File "mmdetection\mmdet\datasets\utils.py", line 136, in _check_head
    assert module.num_classes == len(dataset.CLASSES), \

Does CLASSES = ('uav', ) work?
https://github.com/open-mmlab/mmdetection/blob/a616886bf1e8de325e6906b8c76b6a4924ef5520/mmdet/datasets/wider_face.py#L17

@shinya7y yes that works, maybe we can add a warning that tells to add a semicolon at the end, for the single class case.

@shinya7y yes that works, maybe we can add a warning that tells to add a semicolon at the end, for the single class case.

I agree with this warning. We may do that in PR #4973.

@ZwwWayne i updated #4973


Rails with an ember-cli route

The rails secure headers complete blocks the ember js. I tried to SecureHeaders.opt_out_of_all_protection(request) for that controller action. However, it breaks on another module loading becuase it is trying to use nonced_javascript_tag. This results in a Attempted to override an opt-out CSP config. error. Is there a check for the opt-out option that we can use to use a plain javascript_tag if the opt_out is set?

I think I figured it out. I used and after_action callback to opt_out_of_all_protection

It is certainly possible to configure CSP to be compatible with ember and keeping CSP around would fix the issue you ran into. If you look at the developer console on the page with errors, it will pretty much tell you what you need to add to your CSP configuration.

So I don't have to disable it and for the rails action for the ember app and use https://github.com/rwjblue/ember-cli-content-security-policy/ ?

I don't think I understand how your app works. https://github.com/rwjblue/ember-cli-content-security-policy/ affects express servers, secure_headers affects ruby servers. So if you're having to opt out, then I would think https://github.com/rwjblue/ember-cli-content-security-policy/ would have no effect since it sounds like you're using ruby application code to serve the page.


delete repo secret on unregister repository

Signed-off-by: Tathagata Paul<EMAIL_ADDRESS>This PR will automatically delete repository secret on unregistering the repository.

👍


When will chm version of API documentation be available

It is very convenient and fast for offline browsing.

+1000 for this. I've always liked much more the chm format (even in Linux, KchmViewer is an excellent viewer, much better than Microsoft's tool) than the pdf or online version (there are times a internet connection is not available), since it's much more usefull to search and find something very quickly. Please consider providing official support for the chm format.
Thanks.


Integration with Agregore

Hey folks, I'm the maintainer of @AgregoreWeb and have been working on integrating various peer to peer protocols natively with web browsers via custom protocol handlers.
Would you be interested in chatting about speccing out a locutus:// URL scheme as well as protocol handlers in Agregore so we can load apps and send data to contracts natively?
I think there's a lot of potential in mixing locutus with some other protocols like IPFS and having tools for deploying and interacting with Locutus apps right from within Agregore.
It'd be also interesting to talk about integrating it with Agregore Mobile down the line and taking advantage of the ad-hoc mesh network creation functionality we've been working on in there.

Also it'd be interesting to talk about how we could use IPLD Databases in order to handle large volumes of data and have search indexes. https://blog.mauve.moe/posts/peer-to-peer-databases

Not sure we are ready at this point to talk about integrations yet.
@sanity ?
Maybe should move this to ideas.


Contact us

Add endpoint for submitting contact requests that email us.

Thanks!  Note that I did make the email config change on the server for both test and live already.


Allows custom mapping of objects.

Allows one to subclass / reopen FactoryGuyTestMixin and configures a custom object mapping.
For example, Django Tastypie returns:
objects: [ { }, { }, ... ]
meta: { ... }

FactoryGuyTestMixin only returns:
clients: [ ... ]

@pedrokiefer, Did not realize that was issue, so thanks for bringing that up and making pull request for it.  This code is checked in to master, so will work if you using bower to just reload v0.9.6. Let me know otherwise and I will make new patch version.

@danielspaniel great! thanks for the fast response :)


Font rendering overlap on OS X 10.11.6

Visible in screenshot.

Try changing the font offset on y in the config file

Nice, that fixed it.  Maybe the default value for y offset should be 0 in the example config file?

Well -7 seems to work quite well with the default font. Or are you suggesting to hardcode an offset of -7 on top of the specified offset to make the default offset 0 with the default font?

No I don't think a hardcoded offset would be correct.  I was just trying to point out that, out of the box, the default configuration on OS X if a bit confusing and will likely lead to a lot of questions likes this posted in the issues.  Maybe that could be mitigated by changing the default value.

We just added support for installing a default configuration file on the first run. It's installing a slightly different config file for macOS where those offsets are zero and the font family is Menlo. I'll update the instructions in the README to reflect this.

Nice, sounds like a great solution.  I love this project, by the way.  I've often been frustrated by the overhead of using iTerm2 to run tmux.  This may very well become my new go-to terminal on OS X.


Fix dev server and add instructions to run locally

npm run dev appears to be broken currently

Closed by d469b8b79d54c6a92273918e2b9b3e8483c302ea and 6b5740b6b783691eb660274facc9760060bb4202


Fail to execute the "Execute Function Now..." action for the deployed function

OS: Win 10
Build Version: 20230614.4
Repro Steps:

Create a JavaScript project with "HttpTrigger" template.
Deploy this project to a Node Function App.
Expand the above Function App -> Execute "Execute Function Now..." action for the "HttpTrigger" function with the default value.
Check whether succeeds to execute the "Execute Function Now..." action or not.

Expect:
Succeed to execute the "Execute Function Now..." action.

Actual:
Fail to execute the "Execute Function Now..." action with an error.

More Info:

This issue also reproduces for other runtime projects.
This issue does not reproduce on the current released extension v1.11.0.

Does this still reproduce? We think #3727 might fix this.

This issue still reproduces on the latest main branch build 20230629.1.


Provided URL cannot be handled error

handleEmail = () => {
const to =<EMAIL_ADDRESS><EMAIL_ADDRESS>// string or array of email addresses
email(to, {
// Optional additional arguments
cc<EMAIL_ADDRESS><EMAIL_ADDRESS>// string or array of email addresses
bcc<EMAIL_ADDRESS>// string or array of email addresses
subject: 'Show how to use',
body: 'Some body right here'
}).catch(console.error)
}
when using the example it gives the error

I was testing this and if you are using the iOS Simulator the linking cannot be completed because the Email app is not found in the Simulator.
You should use the Android Emulator or a physical iOS Device.

Thanks @SoftARV. @decodez does this resolve your issue?

I'm closing this in the meantime. Please feel free to open the issue again if the problem persists.

I am having the same issue


Scipy seems to be a core dependency

If I read things right, scipy is specified as a dependency of the analysis flavor only. However:
(Pdb) bids.get_collections(level='dataset')
*** ImportError: No module named 'scipy'

Should it get promoted, or is this "analysis"?

Hmm... I don't know what the convention is in a situation like this. The call is through grabbids in this case, but that's just a very thin wrapper for functionality in analysis. And other than that one call, I don't think scipy is needed anywhere. What do you suggest?

I think if we're going to go down this road, we'll need to add numpy, pandas, and nibabel as core dependencies, because those are all used to load variables. But I'm a bit apprehensive about this, because it seems inadvisable to force a user to install all of those packages just for .get_collections. I guess on reflection, I'd prefer to either revert to keeping scipy as a dependency of analysis, or remove the .get_collections convenience wrapper from BIDS_Layout. Thoughts?

@mih, any thoughts/objections? Otherwise I'll probably leave this as-is. (Possibly with a more informative warning if .get_collections is called without the required packages.)

Closing this since I haven't heard anything... feel free to reopen if you want to re-litigate this, @mih ;)

Auto-approved....


Swift version issue

After installing when I opened project, it says SwipeCellKit developed with swift 2.x. I have tried
both branches. My project is in Objective - C
i.e
Get the latest on develop
pod 'SwipeCellKit', :git => 'https://github.com/SwipeCellKit/SwipeCellKit.git', :branch => 'develop'
If you like to live dangerously
pod 'SwipeCellKit', :git => 'https://github.com/SwipeCellKit/SwipeCellKit.git', :branch => 'swift_4.2'

What is your issue?

When I install library usit cocoa pod and started my project, xcode says
swipecellkit is developed in xcode 2.x
On Wed 20 Jun, 2018, 8:54 PM Mohammad Kurabi<EMAIL_ADDRESS>wrote:

What is your issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SwipeCellKit/SwipeCellKit/issues/217#issuecomment-398791447,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APH9iexAIga6DRBKyvECKGqcsZ_WtiQAks5t-mkSgaJpZM4UvG71
.

This project does not support objective-c.


Move filter_batch out of stream_output

We want to consolidate the batch operations all into get_next_batch_to_run, so we move filter_batch from stream_output  to get_next_batch_to_run

@qeternity It should be fixed by #1846 1850


⚠ Bofrost.at has degraded performance

In e3920c9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1355 ms

Resolved: Bofrost.at performance has improved in c6fbce2.


New maintainer needed

Effective today, I am stepping down from maintaining Solo5 and from the core team of MirageOS.
What does that mean?
I will no longer monitor pull requests or issues filed on repositories in the Solo5/ organisation on GitHub, with the exception of this
issue of appointing a new maintainer for Solo5.
Given that MirageOS is the primary downstream of Solo5, I would prefer that members of the MirageOS community step up to continue maintenance of Solo5. Failing that, perhaps there is someone in the wider community who is interested.
For details please see the full e-mail at<EMAIL_ADDRESS>

Firstly, of course, many thanks to Martin for the wonderful maintainership to date.
Moving forwards, I can confirm that I have admin access to the solo5 org, and there is a meeting of the MirageOS core team on the 25th Nov 2021 (tomorrow) in order to find out who has time and interest to step up.

Hi,
We did the meeting with the @mirage/core team and we agreed that @TheLortex and me will maintain & release Solo5. @avsm, @djs55 and @hannesm will keep their eyes on the project to keep the quality of this project made by the Solo5 core team.
From our perspective, #494 will be merged and Solo<IP_ADDRESS> will be released. This is our initial plan with Martin about the release of MirageOS 4. So we will achieve that as soon as possible :+1:. About technical details (I know that NixOS is aware about that), we will not support a retro-compatibility with MirageOS 3. By this way, we can merge #494 without any changes and definitely delete pkg-config from our workflow.
Then, in the way of MirageOS 4, we will continue to maintain and improve Solo5 and we will try to answer the existing issues. In our mind, OpenBSD support (see #495), NixOS support (see #496) and SCSI support. This is our court/middle term goals about Solo5.
I would like to thanks Martin for all of his job on this great project. It help us a lot to provide unikernels and we will continue to improve it to obtain a better experience about virtualization/deployment of unikernels.

First of all, thanks @mato for your impressive work on solo5 (and various other parts of the MiageOS ecosystem) - a system developed in C without much ifdef, very stable across platforms and compilers, nearly bug free (the only one I remember is #460).
Then - about the plan - thanks to @dinosaure and @TheLortex for taking on. My concern with the above plan is the lack of mention of a CI -- I really appreciate the huge matrix of e2e tests and platforms they are executed on. I personally think that such a huge automated coverage is crucial for further development and maintenance of solo5 (before planning releases) - to avoid bitrot and bad changes on some code paths (OpenBSD vmm, the xen code, ...).

Many thanks for volunteering, @dinosaure @TheLortex!  I'll add you both as maintainers now. If you could ensure that the CHANGES file and README remains uptodate I'd appreciate it.


Fix gizmos flickering during fixed update

Objective
Gizmos are immediate mode and thus last only for one frame. When drawing them during FixedUpdate, multiple frames may be drawn before the next fixed update, causing them to flicker.
Solution
Record fixed update gizmos separately and keep them around till the next update. This also works if there are multiple fixed updates in a single frame.
Also expose GizmoBuffer for any custom scheduling not covered by this.

Changelog
Added

GizmoBuffer for recording gizmo draw calls

Fixed

fixed gizmos flickering is drawn in FixedUpdate

Wouldn't it make more sense to have a retained API for gizmos, e.g. Handle<Polyline>, for cases like this?

Wouldn't it make more sense to have a retained API for gizmos, e.g. Handle<Polyline>, for cases like this?

I would say no mostly because I use these things as quick debug tools. Retained mode would add a lot of boilerplate here.

You are only fixing issue for fixed update, it wouldn't work for custom schedules, run_if conditions, and so on.
Perhaps gizmos should be retained {until next system run OR until 1 second is passed}? This solution would make gizmos work in all systems. But I'm not sure about performance implications of this approach.

Wouldn't it make more sense to have a retained API for gizmos, e.g. Handle<Polyline>, for cases like this?

This is sort of the direction that I lean towards. I don't think you should be drawing things to the screen during FixedUpdate at all, especially with an immediate mode API.

This is adding retained mode behavior to an immediate mode API. What if someone uses this expecting the gizmo to draw only on the frames the fixedupdate is running? That's how I would expect this to work, and this change would prevent that. Like, lets say I want to find the exact frame my updates are happening, visually, I would expect the gizmo would only display for the rendered frame the fixed update system is running. I could then record my screen to visually debug precisely when updates are happening.
You can make gizmos work the way you want without any changes:
// scheduled on a fixed update
fn update_pathfinding(mut pathfinding: ResMut<Pathfinding>) {}

// normally scheduled system
fn debug_pathfinding(mut gizmos: Gizmos, pathfinding: Res<Pathfinding>) {}

This is adding retained mode behavior to an immediate mode API. What if someone uses this expecting the gizmo to draw only on the frames the fixedupdate is running? That's how I would expect this to work, and this change would prevent that. Like, lets say I want to find the exact frame my updates are happening, visually, I would expect the gizmo would only display for the rendered frame the fixed update system is running.

The problem I have with this is that now you have boilerplate and friction to just adding debugging utility. I can't just plop a line of code into my gameplay systems at any point and debug it similar to a info!(...). The way I see it is FixedUpdate is where basically all gameplay systems should be, this makes it significantly easier to debug/have deterministic state/network/etc.

I could then record my screen to visually debug precisely when updates are happening.

I'm unsure of the point of that... Even in networking situations I am not using visual feedback.

Ultimately, drawing things, especially in immediate mode, in FixedUpdate is fundamentally questionable. I think that your idea of "just use it like dbg" is good (and that "gameplay systems should be in FIxedUpdate by default"), but there are some real challenges here.
FixedUpdate's behavior is uniquely strange, and with good reason. It may run once, zero or many times for a single frame. Once works fine out of the box. Your solution handles zero times, at the cost of substantial complexity. But what about multiple times? Your solution (and any non-retained solution) will then render multiple copies of the gizmos on the screen simultaneously, if only for a second.
Ultimately, I think that the best solution here is to say "sorry, you can't use immediate mode drawing APIs within FixedUpdate", and then clearly document why and the workaround (split it out into another system that runs in Update).

Ultimately, drawing things, especially in immediate mode, in FixedUpdate is fundamentally questionable. I think that your idea of "just use it like dbg" is good (and that "gameplay systems should be in FIxedUpdate by default"), but there are some real challenges here.
FixedUpdate's behavior is uniquely strange, and with good reason. It may run once, zero or many times for a single frame. Once works fine out of the box. Your solution handles zero times, at the cost of substantial complexity. But what about multiple times? Your solution (and any non-retained solution) will then render multiple copies of the gizmos on the screen simultaneously, if only for a second.
Ultimately, I think that the best solution here is to say "sorry, you can't use immediate mode drawing APIs within FixedUpdate", and then clearly document why and the workaround (split it out into another system that runs in Update).

What if we just replicate the Time stuff here? I don't see why the workaround can't just be the solution here.


C_CPP : Array Rotation in C++

Description 📜
I've completed my issue work , I raised an issue on the Array Rotation in C++.
This documentation will explain Array Rotation in C++ :

It is a beginner friendly documentation of Array Rotation includes a problem and solution in C++ code with proper comments ahead.
Explained functions involved in Array Rotation in the C++ code.

Fixes #4174

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@Saviour1001 @Suvraneel Please review my documentation. 🚀


Fix pageserver metrics names

Try to follow Prometheus style-guide https://prometheus.io/docs/practices/naming/ for metrics names.
Changes:

Use pageserver_ prefix for all pagserver metrics
Specify _seconds unit in time metrics
Use unit as a suffix in other cases, such as _hits, _bytes, _records
Use _total suffix for accumulating counters (note that Histograms append that suffix internally)

Sent review requests to some people who may be affected by this rename. Also note that I'm probably going to rename some metrics in proxy/safekeeper code too.


QuarmTool crashing on start up Release 23 - v<IP_ADDRESS>

Upon starting Quarmtool it opens up my previous windows, freeze, and then crashes with no warning.
Event Viewer logs
.Net Runtime Error
Application: QuarmTool.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
   at MS.Win32.UnsafeNativeMethods.PostMessage(System.Runtime.InteropServices.HandleRef, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
   at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<ChannelSet>)
   at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)
   at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

And
Application Error
Faulting application name: QuarmTool.exe, version: <IP_ADDRESS>, time stamp: 0x8c06bf3a
Faulting module name: KERNELBASE.dll, version: 10.0.19041.4412, time stamp: 0x6d8c3da8
Exception code: 0xe0434352
Fault offset: 0x00140b82
Faulting process id: 0x5b60
Faulting application start time: 0x01dabaa2d6e7ea9d
Faulting application path: C:\Games\EQ\quarm extras\QuarmTool\QuarmTool.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 70cb4a44-cd1b-46c8-9f60-2902a3a4d27f
Faulting package full name:
Faulting package-relative application ID:

Update, I reverted back to the previous version and it still crashed.
Thinking there may be some cache or settings issue I unzipped the latest version to a different folder and started fresh.
The new install worked just fine so there must be something in the old installation directory that's causing this.
Most likely something in the settings or other cache files. I've uploaded my bad install for you to test if you want.
I did note in my previous bug report that the application seemed to stall for a bit then recover so unsure if its related to the previous bug in anyway. So could be a issue from the previous release not necessarily this one.
QuarmTool_Bad.zip

So.. Same issue. The windows are off the screen, position, and size wise.
What resolution is your monitor? Is it 4k? 1440p? 1080p?
Looks like the window loading off the screen causes a loop of resizing, checking the size, resizing, etc..
Gonna see what I can do about it.
That said, it does look like the one you sent me is version <IP_ADDRESS>, and not <IP_ADDRESS>. Not the hugest deal, just mentioning.

I have 3 monitors
Main one is 1440p other two is 1080p

This crash should be sorted out in the next release.
Now if it detects anything off screen it'll push it back on screen correctly, and more importantly, resize it to be within the bounds of your screen.


{redisenterprise} HTML tags aren't allowed in published reference content

Describe the bug
Problem to solve:
HTML tags in source code are causing build warnings in MicrosoftDocs/azure-docs-cli. More importantly, customer-facing reference docs are not instantiating properly -- parameter values formatted with `<>` are missing. Here's an example:

Requested solution:
These values should be escaped with a backtick. Here's an example from az webpubsub.

Related GitHub issues:
This is the same issue as these GitHub issues.
List of HTML tag instances that need update:

File name
Build error

latest/docs-ref-autogen/redisenterprise.yml
HTML attribute 'uuid' on tag 'sub' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise.yml
HTML tag 'resource' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise.yml
HTML attribute 'uuid' on tag 'sub' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise.yml
HTML tag 'resource' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise/database.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/redisenterprise/database.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

Related command
az redisenterprise
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
Azure CLI 2.62.0
Additional context
No response

Thank you for opening this issue, we will look into it.


[typescript] Sintax Highlight breaks when a variable is assigned an object in a new line.

VSCode Version: 1.3.0, 1.3.1 (did not test previous versions)
OS Version: Win10

Steps to Reproduce:

Open Code.
Open the attached example file SintaxHighlightBugReport.ts (inside the zip, github does not support ts attachments)
Observe that the method wronglyHighlitedCode is not correct in terms of highlighted code colors (is all white text).

I've attached a screen grab too, in which I've marked the behavior I'm observing in my PC.

SyntaxHighlightBugReport.zip
Hope this helps!

This issue was moved to Microsoft/TypeScript-TmLanguage#221


ttnn.maxpool2d fails in VGG model

Describe the bug
ttnn.maxpool2d fails to produce result for some test cases in e150 and n300 while working on VGG model.
To Reproduce
Steps to reproduce the behavior:
pick the test from the commit
Run pytest
Expected behavior
As the above shared configuration works in pytorch, it is expected to run in ttnn aswell.
Error

For input shape [1, 256, 56, 56],

E       RuntimeError: TT_THROW @ ../tt_metal/impl/allocator/allocator.cpp:141: tt::exception
E       info:
E       Out of Memory: Not enough space to allocate<PHONE_NUMBER>400 B L1 buffer across 50 banks, where each bank needs to store<PHONE_NUMBER>8 B

For input shape [1, 512, 28, 28]

E       RuntimeError: TT_THROW @ ../tt_metal/impl/allocator/allocator.cpp:141: tt::exception
E       info:
E       Out of Memory: Not enough space to allocate<PHONE_NUMBER>408 B L1 buffer across 56 banks, where each bank needs to store<PHONE_NUMBER>8 B

For input shape [1, 512, 14, 14]

LOW PCC issue
PCC = 0.8859652206760608

@vigneshkeerthivasanx The OOM error bug has been fixed in main (today), please rebase and try those two tests again, they pass for me.
Im now looking into the PCC error test case.

The remaining PCC error is due to a kernel limitation in the width dimension. Opening this feature issue to support wide cases: #12544 . An update should be ready by tomorrow.

@vigneshkeerthivasanx The support for wide channels has been merged to main. These tests all pass now.

@mywoodstock All tests are passing in the VGG model with good PCC.
Thanks.

Closing this issue, as it is resolved.
Thanks, @mywoodstock .


Any plan for aggregation support

Hi Team,
I was exploring the library and looking into it , seems that aggregation functions are minimal supported . What is the otherway which you suggest for implementing aggregation ?

We are currently working on an EntityStreams-like implementation for Aggregations; stay tuned!


Fixes deletion of splitted cookies - Issue #69

This pull requests changes how the cookies are deleted on logout. It changes how the cookie names are
determined.
If you have any questions / suggestions, I'd be glad to add these.
Description
For problem description see Issue #69.
ClearSessionCookie() is changed to search the request cookies for cookies set by this proxy (identified by
name prefix). For each of these a "reset cookie" is generated and set into the response header.
The change only affects the way the cookie names are determined.
Motivation and Context
Fixes Issue #69. A user cannot be logged out in case of splitted cookies.
How Has This Been Tested?
This is tested by unit tests (oauthproxy_test.go - TestClearSplittedCookie, TestClearNotSplittedCookie)
and this is running in our production environment.
Checklist:

[ ] My change requires a change to the documentation or CHANGELOG.
[ ] I have updated the documentation/CHANGELOG accordingly.
[x] I have created a feature (non-master) branch for my PR.

Thanks for your comments. I'll change the code and update the PR.

Hey, can I do anything to get this merged?
Any changes or something?

I'm done

Hi @einfachchr, there's something kinda weird going on here, the diff now is pulling in loads of additional stuff and there's a mass of new commits from other PRs, any idea what happened?
Could you rebase on top of our master branch picking only your commits and then force push again please? I think this should fix it

@JoelSpeed  I did a rebase of master. Maybe a bad idea?
OK, I'll have a look.

@JoelSpeed I did a rebase and force push. Now it looks fine ;-)


It can not run in centos 8

python version 2.7.17

How did you install Python?  It appears as though you have not installed python in a way that it has SSL/HTTPS support.

I download the packages in  python.org
and i compile the package in my vps

Ok, in any case, they are compile wrong.  I'd recommend installing python via dnf on CentOS 8.


Contribution guidelines

It would be nice to have:

a GitHub pull request template, to help guide people submitting apps to the showcase with what required information we need for a proper review.
a CONTRIBUTING.md file in the root of the repo, explaining that app submissions should go via the pull request route.

@jahoni I heard you may have been working on submission guidelines, yes?


Keyboard shortcut "ALT GR" + "G" (prints slash "/") doesn't work

Simply when I use keyboard shortcut ALT GR + G it doesn't print "/".

Thanks for the report! This looks like a duplicate of https://github.com/atom/atom-keymap/issues/35 – please subscribe there for updates.

solved by installing keyboard-localzation atom package (https://github.com/andischerer/atom-keyboard-localization)


Regression with Bluemix logs in v6.22.2 Windows 64 bit

Command
cf logs

What occurred, incl. error and/or stack trace
FAILED Timed out waiting for connection to Loggregator (wss://doppler.ng.bluemix.net:4443).

What you expected to occur
See logs as they were shown with v6.21.1 and before

CLI Version
cf version 6.22.2+a95e24c-2016-10-27

CC API Endpoint Version
API endpoint: https://api.ng.bluemix.net (API version: 2.54.0)

CF Trace, if issue relates to HTTP requests or strange behavior
run the command with -v and paste or attach the trace output

REQUEST: [2016-11-12T13:40:37+02:00]
GET /v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/apps?q=name%3Aserver-staging&inline-relations-depth=1 HTTP/1.1
Host: api.ng.bluemix.net
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Connection: close
Content-Type: application/json
User-Agent: go-cli 6.22.2+a95e24c / windows

RESPONSE: [2016-11-12T13:40:38+02:00]
HTTP/1.1 200 OK
Connection: close
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Date: Sat, 12 Nov 2016 11:40:39 GMT
Server: nginx
X-Backside-Transport: OK OK
X-Content-Type-Options: nosniff
X-Global-Transaction-Id:<PHONE_NUMBER>

1761
{
  "total_results": 1,
  "total_pages": 1,
  "prev_url": null,
  "next_url": null,
  "resources": [
    {
      "metadata": {
        "guid": "488d6a04-a40c-453b-bb43-5f67c7628e01",
        "url": "/v2/apps/488d6a04-a40c-453b-bb43-5f67c7628e01",
        "created_at": "2016-08-03T07:21:00Z",
        "updated_at": "2016-11-12T11:32:17Z"
      },
      "entity": {
        "name": "server-staging",
        "production": false,
        "space_guid": "ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
        "stack_guid": "ac91d31a-86a3-453b-babf-8d49c9d763fc",
        "buildpack": "sdk-for-nodejs",
        "detected_buildpack": null,
        "environment_json": {
          "DEBUG": "ew:*",
          "NODE_ENV": "staging",
          "NODE_MODULES_CACHE": false,
          "NODE_PATH": "."
        },
        "memory": 144,
        "instances": 1,
        "disk_quota": 128,
        "state": "STARTED",
        "version": "9b3dd376-1670-4b72-986e-ff088f1467ea",
        "command": null,
        "console": false,
        "debug": null,
        "staging_task_id": "5d3cd9aa67424b1cbfce7bf95bbdbdc0",
        "package_state": "STAGED",
        "health_check_type": "port",
        "health_check_timeout": null,
        "staging_failed_reason": null,
        "staging_failed_description": null,
        "diego": false,
        "docker_image": null,
        "package_updated_at": "2016-11-12T11:30:30Z",
        "detected_start_command": "./vendor/initial_startup.rb",
        "enable_ssh": true,
        "docker_credentials_json": {
          "redacted_message": "[PRIVATE DATA HIDDEN]"
        },
        "ports": null,
        "space_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
        "space": {
          "metadata": {
            "guid": "ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
            "url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
            "created_at": "2016-06-29T05:25:48Z",
            "updated_at": "2016-06-29T05:27:52Z"
          },
          "entity": {
            "name": "production",
            "organization_guid": "ca7c133f-902b-46ae-92c6-23d35fb0f61b",
            "space_quota_definition_guid": null,
            "allow_ssh": true,
            "organization_url": "/v2/organizations/ca7c133f-902b-46ae-92c6-23d35fb0f61b",
            "developers_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/developers",
            "managers_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/managers",
            "auditors_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/auditors",
            "apps_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/apps",
            "routes_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/routes",
            "domains_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/domains",
            "service_instances_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/service_instances",
            "app_events_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/app_events",
            "events_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/events",
            "security_groups_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff/security_groups"
          }
        },
        "stack_url": "/v2/stacks/ac91d31a-86a3-453b-babf-8d49c9d763fc",
        "stack": {
          "metadata": {
            "guid": "ac91d31a-86a3-453b-babf-8d49c9d763fc",
            "url": "/v2/stacks/ac91d31a-86a3-453b-babf-8d49c9d763fc",
            "created_at": "2015-05-14T05:45:37Z",
            "updated_at": null
          },
          "entity": {
            "name": "cflinuxfs2",
            "description": "Ubuntu 14.04.2 trusty"
          }
        },
        "routes_url": "/v2/apps/488d6a04-a40c-453b-bb43-5f67c7628e01/routes",
        "routes": [
          {
            "metadata": {
              "guid": "947be534-c01c-4870-b3e0-2c54819c268c",
              "url": "/v2/routes/947be534-c01c-4870-b3e0-2c54819c268c",
              "created_at": "2016-08-03T07:21:03Z",
              "updated_at": null
            },
            "entity": {
              "host": "project-server-staging",
              "path": "",
              "domain_guid": "f4b90d7e-2cd3-4d30-b200-f28bbaf6be20",
              "space_guid": "ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
              "service_instance_guid": null,
              "port": null,
              "domain_url": "/v2/domains/f4b90d7e-2cd3-4d30-b200-f28bbaf6be20",
              "space_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
              "apps_url": "/v2/routes/947be534-c01c-4870-b3e0-2c54819c268c/apps",
              "route_mappings_url": "/v2/routes/947be534-c01c-4870-b3e0-2c54819c268c/route_mappings"
            }
          },
          {
            "metadata": {
              "guid": "f738adc5-809b-45cb-bbaa-a019e0637755",
              "url": "/v2/routes/f738adc5-809b-45cb-bbaa-a019e0637755",
              "created_at": "2016-08-03T07:23:49Z",
              "updated_at": null
            },
            "entity": {
              "host": "api-staging",
              "path": "",
              "domain_guid": "0e8e988a-7ce1-47b7-a548-43425484bffd",
              "space_guid": "ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
              "service_instance_guid": null,
              "port": null,
              "domain_url": "/v2/domains/0e8e988a-7ce1-47b7-a548-43425484bffd",
              "space_url": "/v2/spaces/ec2a0b78-5b86-41ed-8738-b9d6ac34c0ff",
              "apps_url": "/v2/routes/f738adc5-809b-45cb-bbaa-a019e0637755/apps",
              "route_mappings_url": "/v2/routes/f738adc5-809b-45cb-bbaa-a019e0637755/route_mappings"
            }
          }
        ],
        "events_url": "/v2/apps/488d6a04-a40c-453b-bb43-5f67c7628e01/events",
        "service_bindings_url": "/v2/apps/488d6a04-a40c-453b-bb43-5f67c7628e01/service_bindings",
        "service_bindings": [

        ],
        "route_mappings_url": "/v2/apps/488d6a04-a40c-453b-bb43-5f67c7628e01/route_mappings"
      }
    }
  ]
}
0

WEBSOCKET REQUEST: [2016-11-12T13:40:38+02:00]
GET /apps/488d6a04-a40c-453b-bb43-5f67c7628e01/stream HTTP/1.1
Host: wss://doppler.ng.bluemix.net:4443
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: [HIDDEN]
Origin: http://localhost
Authorization: [PRIVATE DATA HIDDEN]

WEBSOCKET ERROR [2016-11-12T13:40:59+02:00]
Error dialing trafficcontroller server: dial tcp <IP_ADDRESS>:4443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond..
Please ask your Cloud Foundry Operator to check the platform configuration (trafficcontroller is wss://doppler.ng.bluemix.net:4443).. Retrying...

WEBSOCKET REQUEST: [2016-11-12T13:40:59+02:00]
GET /apps/488d6a04-a40c-453b-bb43-5f67c7628e01/stream HTTP/1.1
Host: wss://doppler.ng.bluemix.net:4443
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: [HIDDEN]
Origin: http://localhost
Authorization: [PRIVATE DATA HIDDEN]

FAILED
Timed out waiting for connection to Loggregator (wss://doppler.ng.bluemix.net:4443).

Platform & Shell Details
Windows 10 64 bit

Hi @kyrylkov
With the deprecated and future removal of the "loggregator" endpoint, the cf CLI is now using the url as advertised by "doppler_logging_endpoint".
Your API endpoint advertises port 443 for the one and 4443 for the other.
Is it possible something is blocking your access to port 4443 (e.g. corporate firewall)?
Else, better file a support ticket with Bluemix.
Please report back how you go.
Cheers,
Dies Koper
CF CLI PM

@dkoper No firewall.  Filed a support ticket with Bluemix.

Update from Bluemix:

This is Meng from Bluemix Support team to assist you. Sorry for the inconvenience, and thanks a lot for raising this ticket.

We are working on Change Request to be deployed to fix the issue.

In the mean time, as a temporary solution and workaround, you can pick up 6.22.1 version from below link:

https://github.com/cloudfoundry/cli/releases

I will check the progress, and update the result to you soon. Thanks.

The problem has been solved by Bluemix.
Bluemix users, be sure to re-login by running: cf login

Thanks for the follow-up @kyrylkov!


query_posts() alternative for pagination with Timber?

The wiki on pagination recommends the use of query_posts() to get pagination working on page templates.
The WordPress Codex on query_posts discourages the use of this function. Is there a way of getting pagination working with Timber without query_posts?

@ashmatadeen you only need to use query_posts when you're using get_pagination for something other than the default query.
As for why vs. WP's recommendation: basically query_posts slaps WordPress across the face with a new query which can have implications for things like pagination ... the very pagination we're looking to exploit!
It's very possible that as WP has been doing better OO organization there's now (or will be) a better way to grab data when assembling the page links. The problem is, that (at time of writing those functions) the links were heavily dependent on nasty globals and such — which are the globals that query_posts is muscling into

... if you can see a better way to get pagination going without using query_posts I'd love to merge it. Again, it's very possible that since I wrote this part (prob. around WP 3.8) things in the internals have gotten better

Thanks for the explanation @jarednova I'll post an update here if I find a way around it.

From what I can see, Timber::get_pagination() is relying on WP's query_posts() for two properties:

$wp_query->found_posts
$wp_query->query_vars['posts_per_page']

Before running Timber::get_pagination() however, Timber has access to both properties when running Timber::get_posts($args). The properties are accessible in TimberQueryIterator->get_posts() as:
$this->_query->found_posts and $this->_query->query_vars['posts_per_page'].
Not sure if this is the best approach but I'm thinking if Timber can keep hold of these two properties to later pass them onto Timber::get_pagination() then Timber::get_pagination() does not have to rely on those being set in global $wp_query? Do you have any insights into how to best achieve this?

how do you use a post class for posts queried with query_posts?

@jarednova
Is it possible to do as @ashmatadeen suggests: add found_posts to the pagination object results? I would also like to extend the suggestion, and make found_posts available to Timber post query output.

So here is what I did just to get around having to user query_posts to return pagination on a custom query. I had a class that was extending WP_Query to add location based sorting options based on meta_values so I had to use WP_query posts.
I just went into @jarednova Pagination.php in the plugin and saw that in the constructor there is a $wp_query object set to null. If null it just uses the global $wp_query object. So I just created a new instance of the Pagination class in my template file and passed it the blank array for the first param and my custom query object as the second everything worked out.
$pagination = 'Timber\Pagination';
$context['pagination'] = new $pagination(array(), $my_query_object);

Is this still something you're actively working on or need addressed? Please respond in two weeks or we'll close this thread


Juvairiya Fathima

Due we close new issues on PR merge and voting is still possible on closed issues I will close this one.


plot_tracks doesn't exist

Hi,
I am trying to use the plot_tracks option and created a command_file.txt where I have 2 plot_pileup commands as instructed in your README.md.
However, I am unable to call squigualiser plot_tracks --shared_x -f ${COMMAND_FILE} -o ${OUTPUT_DIR} as I receive an error of
usage: squigualiser [-h] [-v] {plot,reform,realign,plot_pileup} ...
squigualiser: error: argument command: invalid choice: 'plot_tracks' (choose from 'plot', 'reform', 'realign', 'plot_pileup')

Do I use a wrong version of the tool, perhaps, as I don't have this optional argument?
I would be glad to hear back from you, thank you.

Hello @kaltinel,
Yes, you are using an old version. Can you download the prebuilt binaries, run the test command for the sample dataset and then try your command?
The commands are available here

Hi @hiruna72,
Thank you very much for your answer. I installed it from scratch and now all arguments are complete.


feat: add CompiledPlugin

This adds bindings for ExtismCompiledPlugin, allowing for multiple instances to be created from a single compiled plugin.

Hm, tests are failing with test.zig:41:65: error: expected type 'manifest.Manifest', found 'test.man__struct_19051', but it looks like this is happening on main too - any idea what that might be?

Oh, let's pin the Zig version to 0.13.0 for now. this uses master, and its a bit ahead, may have some different codegen changes that could be impacting this

Thanks, that fixed it!

Nice work!


refactor(arbitrary): rename string and char arbitrary types

Current dependencies on/for this PR:

main

PR #38

PR #41

PR #42

PR #43   👈

This comment was auto-generated by Graphite.


enhance the existing Tuxedo dockerfiles

The following files and folders under OracleTuxedo would be removed after merged.

COPYRIGHT
LICENSE
dockerfiles
samples

This PR is actually about the core folder, then?

@brunoborges, yes, it's for core folder. After the PR is merged, the original folder should be removed.