Sjoerd de Vries

Results 120 issues of Sjoerd de Vries

With the recent update in scratch and fingertipping, it must be made sure that local transformations are indeed still executed locally. A low-level test must be added. In addition, it...

medium priority
performance

```python ctx.tf = lambda a, b: a + b ctx.tf.a = 4 ``` will give a CacheMissError for "4" This may or may not be a bug. This can be...

bug
high priority

This can be disastrous if both processes are compiling the same C code, or building the same modules. Solution: look up tempfile.gettempdir() in the Seamless code and change it.

bug
not urgent

To indicate the name of the conda environment in which the command is to be executed. Must be known to the assistant/deployment machine(s). Most assistants should be able to deal...

not urgent
new feature

"huge" as being too big to fit comfortably in memory. They are already well supported by bash transformers, because of file zones. For Python, there is currently no alternative for...

not urgent
new feature

Something like `SEAMLESS_SCRATCH_DIR=/scratch` . On the long term, perhaps multiple scratches controlled by `scratch_level`: pyramid of RAMdisk, SSD, rotating disk, etc.

not urgent
new feature
good first issue
performance

For the non-trivial environments, collate all environments in to a "multi" field, and give it to the assistant to handle. micro-assistant will flat-out refuse.

new feature
low priority

Seamless databases are expected to be shared freely among the community. It is needed to document the security risks of fingertipping from a malicious database. Fingertipping from expression or structured...

high priority

Mixed-style Seamless is expected to be in demand, especially in case of compiled transformers, which must always be part of a workflow, in combination with imperative syntaxes. For the 0.12...

not urgent
apifix
new feature
good first issue

Right now, Python module objects can be directly added. Seamless module objects can also be directly added, but only from a workflow. What is needed is a nice imperative syntax...

enhancement
apifix
new feature
good first issue