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

feat(generator): create a toolbox #8295

Open
wants to merge 19 commits into
base: master
Choose a base branch
from
Open

Conversation

fbeauchamp
Copy link
Collaborator

@fbeauchamp fbeauchamp commented Jan 31, 2025

Description

Code written with the goal of being compatible with node 23.6+, no enum nor protected

Review in order :

  • throttle : throttle a generator to limit its speed.
  • timeout : emit an error if a generator fail to answer in time
  • synchronized :
    • fork a generator into multiple forks.
    • All the forks are yielding in sync, to keep memory pressure under control.
    • If the source fais all the forks fails
    • if a forks ends or fail prematurely, it is removed from the fork list
    • if the last fork ends or fails it's also stopping the source generator

Checklist

  • Commit
    • Title follows commit conventions
    • Reference the relevant issue (Fixes #007, See xoa-support#42, See https://...)
    • If bug fix, add Introduced by
  • Changelog
    • If visible by XOA users, add changelog entry
    • Update "Packages to release" in CHANGELOG.unreleased.md
  • PR
    • If UI changes, add screenshots
    • If not finished or not tested, open as Draft

Review process

This 2-passes review process aims to:

  • develop skills of junior reviewers
  • limit the workload for senior reviewers
  • limit the number of unnecessary changes by the author
  1. The author creates a PR.
  2. Review process:
    1. The author assigns the junior reviewer.
    2. The junior reviewer conducts their review:
      • Resolves their comments if they are addressed.
      • Adds comments if necessary or approves the PR.
    3. The junior reviewer assigns the senior reviewer.
    4. The senior reviewer conducts their review:
      • If there are no unresolved comments on the PR → merge.
      • Otherwise, we continue with 3.
  3. The author responds to comments and/or makes corrections, and we go back to 2.

Notes:

  1. The author can request a review at any time, even if the PR is still a Draft.
  2. In theory, there should not be more than one reviewer at a time.
  3. The author should not make any changes:
    • When a reviewer is assigned.
    • Between the junior and senior reviews.

@fbeauchamp fbeauchamp force-pushed the feat_generator_toolbox branch 2 times, most recently from e040772 to e1f9db6 Compare February 2, 2025 15:10
@fbeauchamp fbeauchamp marked this pull request as ready for review February 3, 2025 07:06
@fbeauchamp fbeauchamp force-pushed the feat_generator_toolbox branch from cd49201 to 6d281b3 Compare February 3, 2025 11:10
@fbeauchamp fbeauchamp force-pushed the feat_generator_toolbox branch from 6d281b3 to 6e0a61b Compare February 3, 2025 11:12
const next = this.#source.next().catch(async error => {
const e = new Error(`Error in the source generator ${error.message}`)
// @todo : why can't I set the cause ?
// e.cause = error
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't let commented code if you don't have a solution at the moment

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you know of can I set the cause of an error in typescript ? this looks like a standard property for me https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

throw new Error("Action failed.", { cause: err }); ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Expected 0-1 arguments, but got 2

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it may be my IDE that is misconfigured

} else {
speed = this.#bytesPerSecond
}
assert.ok(speed > 0, `speed must be greate than zero, ${speed} computed`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great -> greater

assert.ok(speed > 0, `speed must be greate than zero, ${speed} computed`)
return speed
}
constructor(speed: number | (() => number)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should set a default speed or force minimal speed, as speed must be greater than zero.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a positive speed is already enforced through assert. How would you do it ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

speed: number = 1234

yield value
}
} finally {
// in case of error : cleanup the timeout
Copy link
Contributor

@stephane-m-dev stephane-m-dev Feb 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In finally it will happen in case or error or success.
I think you could completely remove this comment, it doesn't bring anything to comment the clearTimeout() just after.

assert.strictEqual(Math.round((end - start) / 1000), 2)
})
test('multiple generator test', async () => {
const generator = makeGenerator(1024 * 1024, 10)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couldn't you put it in a beforeEach() ?

export class Timeout<T> implements AsyncGenerator {
#source: AsyncGenerator<T>
#timeout: number
constructor(source, timeout: number) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should set a default timeout value or allow min/max range.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think timeout value is very context dependent, and not setting one should force the user to use something sane in his context
I could force it to be a positive number though

{
"name": "@vates/generator-toolbox",
"version": "0.0.0",
"main": "src/index.mts",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is not supposed to be dist/index.mjs?

"version": "0.0.0",
"main": "src/index.mts",
"license": "MIT",
"private": true,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you set "private": true in your package.json, then npm will refuse to publish it.
https://docs.npmjs.com/cli/v11/configuring-npm/package-json#private

Why?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to be sure this is not published for now . But I will have to remove this flag before merge

Comment on lines +9 to +10
"@tsconfig/node-lts": "^20.1.3",
"@tsconfig/recommended": "^1.0.7",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you add theses dependencies, then you need to extends your tsconfig.json
See: https://www.npmjs.com/package/@tsconfig/recommended

Are these packages really necessary?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"url": "https://vates.fr"
},
"engines": {
"node": ">=8.10"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe node: >=22.3.0?
To match your @types/node version. No?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI is still on 20.x

@MathieuRA MathieuRA self-requested a review February 4, 2025 12:24
@fbeauchamp fbeauchamp force-pushed the feat_generator_toolbox branch from 4fdcfb0 to 90ebbc5 Compare February 5, 2025 13:19
@fbeauchamp fbeauchamp force-pushed the feat_generator_toolbox branch from 90ebbc5 to af16bee Compare February 5, 2025 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants