Amit Kumar
Amit Kumar
This should not happen again, it has been fixed.
Let me know, if you need any help from gpu perspective @jeromekelleher
@consideRatio @mbmilligan @rkdarst Is there anything I can do to help with the release? We use `batchspawner` for https://github.com/nebari-dev/nebari-slurm
Yes, indeed. We can upload that as GitHub Artifact and use that in the preview step.
`griffe` looks promising so far: ```python In [1]: import griffe ...: ...: papyri = griffe.load("papyri") In [2]: papyri.functions Out[2]: {'_intro': , 'ingest': , 'install': , 'relink': , 'pack': , 'bootstrap':...
I have not tested it yet. I am testing is right now.
The login endpoint issue is fixed (which is what this issue is about), I am able to login via the proxy url, which takes me to the `/auth`. After login...
I just tried running two separate processes explicitly one for API and another for UI ``` ragna api ``` ``` ragna ui --no-open-browser --no-start-api ``` With this `ragna.toml`: ```toml #...
> @aktech we don't want the API to be publicly accessible right? it should still be behind auth but the hope would be that internally launched tools should be able...
By the way, if you want a no-maintenance method to achieve that, you can use [cirun.io](https://cirun.io) for the same.