Status Open for comments 💬 Author(s) @aktech Date Created 04-04-2024 Date Last updated

When using cirun.io in an organization, quite often you need the ability to control access to runners per repository to control usage, cost and availability. Cirun provides a way to access control runners via the following mechanism: You'd create a repository named .cirun in your organization and create a couple of config files to control access. .cirun.global.yml: This is the file where you'd define all the runner configurations you'd want to use in the organization. The format of this file is same as .cirun.yml, for example: runners: - name: gpu-runner cloud: openstack instance_type: gpu_large

CLI: papyri/__init__.py Meeting Notes: 24 Nov, 202 The parsing is either handled by tree sitter or by numpy doc because function docstrings are not correctly parsed by tree sitter because numpy docs has it's own syntax. I tried to have an AST that is generic enough that it can represent all the documentation. When possible doesn't have too many specifities to how it was written, it's as simple as possible to be able to represent the document. What we tried to do is something that's generic enough, that we don't know after it it completely processed if it was rst or markdown. Another thing we wanted to have delayed link resolution. We dont' use tree sitter AST has too much information about the source, we don't want. Our ast still have too much information, but we can't change the tree sitter ast, but we can change our ast. Another problem with tree-sitter ast is, all the nodes are generic type and to get the actual type you would do something like <node>.kind to get the type of node.