Archived
1
0
Fork
You've already forked pipeline
0

Improve seed handling and related object cacheing #43

Open
opened 2026年03月18日 16:49:53 +01:00 by TimTaylor · 2 comments
  • Do we take seed as an argument.
  • Currently we just use the global state but if this is not checked to invalidate the pipeline.
  • What should the default behaviour be here?
- Do we take seed as an argument. - Currently we just use the global state but if this is not checked to invalidate the pipeline. - What should the default behaviour be here?
Author
Owner
Copy link

On first run do we want to record whether a function touches the random number seed and store this? Do we want to go down this track ... sadly I think we do ....

On first run do we want to record whether a function touches the random number seed and store this? Do we want to go down this track ... sadly I think we do ....
TimTaylor added this to the v0.1.0 milestone 2026年03月23日 17:20:39 +01:00
Author
Owner
Copy link

Partial solution via 30cbc2fa06. This improves the situation but when the seed changes cacheing does not help across scenarios. Will require refactoring.

Partial solution via https://codeberg.org/TimTaylor/pipeline/commit/30cbc2fa067a764ef6d09cd260328f2a3498fb68. This improves the situation but when the seed changes cacheing does not help across scenarios. Will require refactoring.
TimTaylor changed title from (削除) How to we handle seeds (削除ここまで) to Improve seed handling and related object cacheing 2026年04月10日 11:19:04 +02:00
Commenting is not possible because the repository is archived.
No Branch/Tag specified
main
hackathon
pages
no-scenarios
seed-handling
constants
fix
attach
refactor
asis
v0.0.0.9165
v0.0.0.9164
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
TimTaylor/pipeline#43
Reference in a new issue
TimTaylor/pipeline
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?