Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[workerpool] Ensure that the promise typing is PromiseLike #45399

Merged

Conversation

forivall
Copy link
Contributor

@forivall forivall commented Jun 10, 2020

Please fill in this template.

  • Use a meaningful title for the pull request. Include the name of the package modified.
  • Test the change in your own code. (Compile and run.)
  • Add or edit tests to reflect the change. (Run with npm test.)
  • Follow the advice from the readme.
  • Avoid common mistakes.
  • Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If changing an existing definition:

  • Provide a URL to documentation or source code which provides context for the suggested changes: N/A, Add promises-aplus tests for the promise library josdejong/workerpool#159 (it conforms to the standard promiselike type definition at least, so my changes are valid)
  • If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
  • Include tests for your changes
  • If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

@typescript-bot
Copy link
Contributor

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊
master #45399 diff
Batch compilation
Memory usage (MiB) 66.7 66.3 -0.5%
Type count 9327 9417 +1%
Assignability cache size 1783 1798 +1%
Language service
Samples taken 176 179 +2%
Identifiers in tests 176 179 +2%
getCompletionsAtPosition
    Mean duration (ms) 356.7 358.1 +0.4%
    Mean CV 10.2% 9.8%
    Worst duration (ms) 422.2 431.1 +2.1%
    Worst identifier nodeWorker nodeWorker
getQuickInfoAtPosition
    Mean duration (ms) 356.4 361.3 +1.4%
    Mean CV 9.9% 10.4% +4.8%
    Worst duration (ms) 423.6 449.0 +6.0%
    Worst identifier wp nodeWorker

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

@typescript-bot typescript-bot added the Perf: Same typescript-bot determined that this PR will not significantly impact compilation performance. label Jun 10, 2020
@typescript-bot
Copy link
Contributor

typescript-bot commented Jun 10, 2020

@forivall Thank you for submitting this PR!

This is a live comment which I will keep updated.

Code Reviews

Because you edited one package and updated the tests (👏), I can help you merge this PR once someone else signs off on it.

Status

  • ✅ No merge conflicts
  • ✅ Continuous integration tests have passed
  • ❌ Most recent commit is approved by type definition owners, DT maintainers or others

Once every item on this list is checked, I'll ask you for permission to merge and publish the changes.

Inactive

This PR has been inactive for 11 days — waiting for a DT maintainer!


Diagnostic Information: What the bot saw about this PR
{
  "type": "info",
  "now": "-",
  "pr_number": 45399,
  "author": "forivall",
  "owners": [
    "Alorel",
    "sgkim126"
  ],
  "dangerLevel": "ScopedAndTested",
  "headCommitAbbrOid": "eb2bc52",
  "headCommitOid": "eb2bc520609a1cd2a53f8abcd08fc3195048d06c",
  "mergeIsRequested": false,
  "stalenessInDays": 11,
  "lastPushDate": "2020-06-23T00:04:37.000Z",
  "lastCommentDate": "2020-06-28T06:05:16.000Z",
  "maintainerBlessed": false,
  "reviewLink": "https://github.com/DefinitelyTyped/DefinitelyTyped/pull/45399/files",
  "hasMergeConflict": false,
  "authorIsOwner": false,
  "isFirstContribution": false,
  "popularityLevel": "Well-liked by everyone",
  "anyPackageIsNew": false,
  "packages": [
    "workerpool"
  ],
  "files": [
    {
      "path": "types/workerpool/index.d.ts",
      "kind": "definition",
      "package": "workerpool"
    },
    {
      "path": "types/workerpool/workerpool-tests.ts",
      "kind": "test",
      "package": "workerpool"
    }
  ],
  "hasDismissedReview": false,
  "ciResult": "pass",
  "reviewersWithStaleReviews": [],
  "approvalFlags": 0,
  "isChangesRequested": false
}

@typescript-bot
Copy link
Contributor

🔔 @Alorel @sgkim126 - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

It seems like the current maintainers are absent
@elibarzilay
Copy link
Contributor

Re-ping @Alorel @sgkim126

@typescript-bot typescript-bot added the Unmerged The author did not merge the PR when it was ready. label Jul 8, 2020
@weswigham weswigham merged commit 0c32e6a into DefinitelyTyped:master Jul 10, 2020
ngbrown pushed a commit to ngbrown-forks/DefinitelyTyped that referenced this pull request Jul 11, 2020
…yTyped#45399)

* [workerpool] Ensure that the promise typing is PromiseLike

* [workerpool] add forivall to maintainers

It seems like the current maintainers are absent
danielrearden pushed a commit to danielrearden/DefinitelyTyped that referenced this pull request Sep 22, 2020
…yTyped#45399)

* [workerpool] Ensure that the promise typing is PromiseLike

* [workerpool] add forivall to maintainers

It seems like the current maintainers are absent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Perf: Same typescript-bot determined that this PR will not significantly impact compilation performance. Unmerged The author did not merge the PR when it was ready.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants