kowainik / kowainik/stan

stan returns with `Killed`

Open
#393 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
597
Forks
53
PR merge metrics
No merged PRs in 30d

Description

I am surprised not to find an issue already opened since stan dies regurlaly

I call it on a several thousand line projets
```
$ stan report --hiedir=/home/teto/.cache/ghcide/main-2d340f680c4d95b43cd7de12b6004129b058bf21
ⓘ Checking environment variables and CLI arguments for default configurations file usage...
Fiasco:
* [Error ] No STAN_USE_DEFAULT_CONFIG Env Variable is set
* [Error ] No CLI option specified for no-default

ⓘ The following Configurations are used:

Result:

With the following warnings:
* [Warning] TOML Configurations file doesn't exist: /home/teto/nova/jinko2/.stan.toml
* [Warning] TOML Configurations file doesn't exist: /home/teto/.stan.toml
* [Warning] No CLI option specified for: checks
* [Warning] configChecks is set through the source: Default
* [Warning] TOML Configurations file doesn't exist: /home/teto/nova/jinko2/.stan.toml
* [Warning] TOML Configurations file doesn't exist: /home/teto/.stan.toml
* [Warning] No CLI option specified for: remove
* [Warning] configRemoved is set through the source: Default
* [Warning] TOML Configurations file doesn't exist: /home/teto/nova/jinko2/.stan.toml
* [Warning] TOML Configurations file doesn't exist: /home/teto/.stan.toml
* [Warning] No CLI option specified for: ignore
* [Warning] configIgnored is set through the source: Default

Killed
```
The version (not very helpful, it's pulled from a recent nixos-unstable)
```
stan --version
Stan v0.0.0.0
➤ Git revision: UNKNOWN
➤ Commit date: UNKNOWN
```
Let me know if/how I can help troubleshoot the issue.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `stan report --hiedir=/home/teto/.cache/ghcide/main-2d340f680c4d95b43cd7de12b6004129b058bf21` on the reported several-thousand-line project and observe the process around the `Killed` output. Determine the relevant resource or execution condition and confirm the issue with a focused reproduction; done means the failure is explained and addressed or its required limits are clearly reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.