Quinn

I get this warning in github: ``` Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: cachix/install-nix-action, cachix/cachix-action, cachix/cachix-action ```

`install-iso` collides in `networking` config

1

My config is a standard `networking.networkmanager`, it does not have `networking.wireless`. Here is the log ``` ╰─>$ nix build .#nixosConfigurations.grindenstern.config.formats.install-iso error: … while calling the 'derivationStrict' builtin at /derivation-internal.nix:9:12: 8|...

This started showing up in my CI building the disk-image a few days ago. ``` querying info about missing paths building '/nix/store/p1j6vnp3bpi6snvwpspdcayijzi5yyk7-etc-man_db.conf.drv' error: executing '/nix/store/lm10ywzflq9qfhr4fl0zqxrhiksf28ks-bash-5.2-p15/bin/bash': Exec format error builder for...

`node2nix --help` is not updated with `--nodejs-16` option

3

`node2nix --help` does not inform the user that `16` functionality is there.

nixify

4

one take on this is in https://github.com/ejgallego/pycoq/pull/10 - However, @ejgallego said > I think also that opam2nix should not be used, but start from the coq-serapi derivation which is not...

a `nix` build and testing infra

12

TODO: - fix everything so I can get the thing to run - implement some basic `pytest` stuff.

Give the caller `namedtuple`; factor out the need for dictionaries

1

passing `dict`s is good enough for the machine learning in python community, so it's good enough for us. However, since we don't need _quite_ the flexibility in configs the machine...

return objects should probably be dicts instead of nested 2-tuples

2

```python res = coq.add(some_command, opts) print(dict(res)) ``` ```shell {'Added': (6, {'fname': ('ToplevelInput', None), 'line_nb': 2, 'bol_pos': 1, 'line_nb_last': 2, 'bol_pos_last': 1, 'bp': 66, 'ep': 70}, ('NewTip', None)), 'Completed': None} {'CoqExn':...

let `pytest` and `pytype` know about `pycoq.so` somehow, probably by doing some kind of `dune exec -- pytest`

1

In https://github.com/ejgallego/pycoq/pull/10 I decided to put `if __name__ == "__main__":` blocks in the test suite, instead of using test harness `pytest`, because I couldn't make `pytest` aware of the `pycoq`...