8000 chore(deps): update module github.com/alitto/pond to v2 by renovate-rancher[bot] · Pull Request #1810 · neuvector/neuvector · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(deps): update module github.com/alitto/pond to v2 #1810

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate-rancher[bot]
Copy link
Contributor
@renovate-rancher renovate-rancher bot commented Feb 7, 2025

This PR contains the following updates:

Package Type Update Change
github.com/alitto/pond require major v1.9.2 -> v2.3.4

Release Notes

alitto/pond (github.com/alitto/pond)

v2.3.4

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.3.3...v2.3.4

v2.3.3

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.3.2...v2.3.3

v2.3.2

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.3.1...v2.3.2

v2.3.1

Compare Source

Pull requests

Changes

  • Ensure closed atomic bool is toggled and checked while holding the mutex to avoid race conditions.
  • Ensure workersWaitGroup.Add() is always called while holding the mutex to avoid race conditions.
  • Improve comments on submit methods to clarify the behavior when the pool is stopped.
  • Refactor trySubmit method to make it simpler and more clear.
  • Centralize worker launch in a new method called launchWorker.
  • Replace subpoolSubmit with subpoolWorker method.
  • Add methods to submit individual task 8000 s in a non-blocking fashion (TrySubmit and TrySubmitErr). Requested in https://github.com/alitto/pond/issues/103
  • Expose new DroppedTasks metric that reflects the number of tasks that were not executed because the queue was full. Issue reported in https://github.com/alitto/pond/issues/100
  • SubmittedTasks metric now includes dropped tasks and it stops being updated once the pool is stopped.

Fixes

  • Decrement workerCount counter when the pool context is cancelled.
  • Resize() now supports setting maxConcurrency to 0 (no limit)

Full Changelog: alitto/pond@v2.3.0...v2.3.1

v2.3.0

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.2.0...v2.3.0

v2.2.0

Compare Source

What's Changed

  • feat(pool): add option to bound task queue (v2) by @​alitto in https://github.com/alitto/pond/pull/99
    • Add support to create bounded pools by specifying a queue size (WithQueueSize option).
    • Add support to choose how to deal with tasks submitted when the queue is full (WithNonBlocking option).
    • Ensure RunningWorkers() method in subpools reflect the actual number of workers running tasks belonging to the subpool.
    • Allow overriding pool options when creating a subpool via NewSupool.
    • Simplify pool submission logic and remove dispatcher goroutine.
    • Simplify subpool implementation.

Full Changelog: alitto/pond@v2.1.6...v2.2.0

v2.1.6

Compare Source

What's Changed

New Contributors

Full Changelog: alitto/pond@v2.1.5...v2.1.6

v2.1.5

Compare Source

What's Changed

New Contributors

Full Changelog: alitto/pond@v2.1.4...v2.1.5

v2.1.4

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.1.3...v2.1.4

v2.1.3

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.1.2...v2.1.3

v2.1.2

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.1.1...v2.1.2

v2.1.1

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.1.0...v2.1.1

v2.1.0

Compare Source

What's Changed

  • feat(taskgroup): improve task group functionality by @​alitto in https://github.com/alitto/pond/pull/81
    • Added a new method to the pool to create a task group associated with a context (pool.NewGroupContext(ctx))
    • Added new methods to task groups:
      • group.Done(): returns a channel that is closed when all tasks in the group finish or the first error is returned.
      • group.Stop(): stops the task group. Queued tasks will be discarded but running tasks will complete their execution.
    • Added a new example showcasing the new pool.NewGroupContext(ctx) method.

Full Changelog: alitto/pond@v2.0.4...v2.1.0

v2.0.4

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.0.3...v2.0.4

v2.0.3

Compare Source

What's Changed

Full Changelog: alitto/pond@v2.0.2...v2.0.3

v2.0.2

Compare Source

Changes

  • Expose Stopped() bool method in pools to indicate whether the pool has been stopped or its associated context has been cancelled.

Fixes

  • Ensure ErrPoolStopped error is always returned when attempting to submit a task to a pool that has been stopped or its associated context cancelled.

v2.0.1

Compare Source

Fixes

  • Avoid launching workers that exit immediately without running any tasks.
  • Prevent task group Wait() from returning eagerly when tasks are executed before submitting the last one of the group.

v2.0.0

Compare Source

What's new in v2?

Version 2 of pond introduces many improvements and new features:

  • Unbounded Task Queues: Task queues are now unbounded by default, simplifying pool creation.
  • Task Submission with Results: New APIs allow tasks to return results, enhancing flexibility.
  • Awaitable Task Completion: Tasks can now be awaited, providing better control over task execution.
  • Type Safe APIs: Improved type safety for tasks that return errors or results.
  • Panics Recovery: Panics during task execution are captured and returned as errors, allowing graceful error handling.
  • Subpools: Create subpools with a fraction of the parent pool's workers for specific tasks.
  • Default Pool: A global default pool is available for task submission without explicit pool creation.
Migration from v1 to v2

There have been a significant number of breaking changes in v2, so please make sure to read the migration guide if you are upgrading from v1.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@holyspectral
Copy link
Collaborator
holyspectral commented Feb 7, 2025

Hi @jeffhuang4704 , could you take a look to see if it's okay to upgrade to v2? Note: v1.9.2 is released on Sep 1, 2024.

8000
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 4 times, most recently from 75c9080 to a81864b Compare February 14, 2025 05:18
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 3 times, most recently from 4a15c10 to 406d1d5 Compare February 20, 2025 06:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 4 times, most recently from 76c22e4 to 68a8922 Compare February 27, 2025 04:37
@renovate-rancher renovate-rancher bot changed the title chore(deps): update module github.com/alitto/pond to v2 Update module github.com/alitto/pond to v2 Feb 27, 2025
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 4 times, most recently from 5102860 to cbb976c Compare March 5, 2025 04:37
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch from cbb976c to a8e5ebc Compare March 8, 2025 04:37
@renovate-rancher renovate-rancher bot changed the title Update module github.com/alitto/pond to v2 chore(deps): update module github.com/alitto/pond to v2 Mar 8, 2025
Copy link
Contributor Author
renovate-rancher bot commented Mar 8, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: mod upgrade --mod-name=github.com/alitto/pond -t=2
could not load package: err: exit status 1: stderr: go: inconsistent vendoring in /tmp/renovate/repos/github/neuvector/neuvector:
	github.com/alitto/pond/v2@v2.3.4: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt

	To ignore the vendor directory, use -mod=readonly or -mod=mod.
	To sync the vendor directory, run:
		go mod vendor


@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 2 times, most recently from 18b8a31 to fd8c6c5 Compare March 12, 2025 18:02
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 2 times, most recently from 05acd28 to d5ed8a2 Compare March 22, 2025 04:40
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch 2 times, most recently from 2f214e8 to c56c06d Compare April 5, 2025 04:38
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch from c56c06d to 5f75713 Compare May 2, 2025 04:41
@renovate-rancher renovate-rancher bot changed the title chore(deps): update module github.com/alitto/pond to v2 Update module github.com/alitto/pond to v2 May 2, 2025
@renovate-rancher renovate-rancher bot changed the title Update module github.com/alitto/pond to v2 chore(deps): update module github.com/alitto/pond to v2 May 7, 2025
@renovate-rancher renovate-rancher bot force-pushed the renovate/github.com-alitto-pond-2.x branch from 5f75713 to efc49ea Compare May 9, 2025 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0