profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/alehed/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

alehed/SyntaxKit 39

TextMate-style syntax highlighting

nsg-ethz/synet-plus 18

Practical Network-Wide Configuration Synthesis with Autocompletion

alehed/aslutils 5

Python package to parse ARM Specification Language code

alehed/rex 4

A DSL for deterministic finite state machines

nsg-ethz/tekton 3

A library to create networks and to generate network configurations

alehed/janus-go 0

janus gateway golang api

alehed/mra_tools 0

Tools to process ARM's Machine Readable Architecture Specification

alehed/oapi-codegen 0

Generate Go client and server boilerplate from OpenAPI 3 specifications

alehed/objective-git 0

Objective-C bindings to libgit2

issue commentmatangover/mypy-vscode

Python executable from venv is not used

Since the last update I also can't reproduce the issue any more. I am not in the 'pythonDeprecatePythonPath' experiment group.

alehed

comment created time in a month

issue commentNixOS/nixpkgs

Black screen on boot in nixos 21.05

I can supply the core dump of the sddm crash, if that is of any use.

alehed

comment created time in 2 months

issue openedNixOS/nixpkgs

Black screen on boot in nixos 21.05

Describe the bug After updating to nixos 21.05, nixos only shows a single _ in the top left corner on startup and nothing else. Removing all xorg related things from the configuration.nix causes it to boot normally.

It seems that this is because sddm crashes on startup, so the login screen is not presented. The journalctl log can be found here.

This issue might be related to #119822.

To Reproduce My nix configuration is here.

  1. Build the nix configuration in the current nixos-21.05 channel with nixos-rebuild switch --upgrade
  2. Reboot

Expected behavior The login screen is shown on boot.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context My machine is a Lenovo ThinkPad T470p.

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.108, NixOS, 20.09.3707.46ba1c34583 (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(alex): `""`
 - channels(root): `"nixos-21.05.876.60cce7e5e1f, nixos-unstable-21.11pre294109.fbfb79400a0"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Note that this is run when booted from 20.09 via booting into a previous version.

created time in 2 months

issue commentmatangover/mypy-vscode

Python executable from venv is not used

This is correct, after I save a file, the warnings disappear.

The output says:

Mypy extension activated, version 0.2.0
Registering listener for interpreter changed event
Waiting for Python extension to load
Python extension loaded
Listener registered
[1] Check workspace: ${workspaceFolder}
[1] Using config file: mypy.ini
[1] Received python path from Python extension: /usr/bin/python3
[1] Running dmypy in folder ${workspaceFolder}
${workspaceFolder}/env/bin/dmypy --status-file /home/alex/.config/Code/User/workspaceStorage/c75fa14f80a26f7dcd6661af27693d09/matangover.mypy/dmypy-80690f3ce6c54e9de14878ef29f8a83a93369fd9.json run --log-file /home/alex/.config/Code/User/workspaceStorage/c75fa14f80a26f7dcd6661af27693d09/matangover.mypy/dmypy-80690f3ce6c54e9de14878ef29f8a83a93369fd9.log -- . --show-column-numbers --no-error-summary --no-pretty --no-color-output --config-file mypy.ini --python-executable /usr/bin/python3
[1] Mypy output:
Daemon started
<Some import errors>

Document saved: ${workspaceFolder}/something.py
[2] Check workspace: ${workspaceFolder}
[2] Using config file: mypy.ini
[2] Received python path from Python extension: ${workspaceFolder}/env/bin/python
[2] Running dmypy in folder ${workspaceFolder}
${workspaceFolder}/env/bin/dmypy --status-file /home/alex/.config/Code/User/workspaceStorage/c75fa14f80a26f7dcd6661af27693d09/matangover.mypy/dmypy-80690f3ce6c54e9de14878ef29f8a83a93369fd9.json run --log-file /home/alex/.config/Code/User/workspaceStorage/c75fa14f80a26f7dcd6661af27693d09/matangover.mypy/dmypy-80690f3ce6c54e9de14878ef29f8a83a93369fd9.log -- . --show-column-numbers --no-error-summary --no-pretty --no-color-output --config-file mypy.ini --python-executable ${workspaceFolder}/env/bin/python
[2] Mypy output:
Restarting: configuration changed
Daemon stopped
Daemon started

I can reproduce this issue consistently.

I'm on Ubuntu 20.04 with vscode version:

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T16:45:26.313Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Linux x64 5.8.0-53-generic

Python version 2021.5.842923320 and pylance version 2021.5.3.

The problem with reproducing it, I guess, is that the python version can only be set by clicking the interpreter version button which is entirely managed by the python extension and is not super reproducible (I use a workspace, so there it asks me to set it for the workspace or the folder, I think I set it for both, but there is no way to check what the current setting is...).

Is there any consequence in not setting the --python-executable command line option? One can even set it in the mypy.ini, if needed.

alehed

comment created time in 2 months

issue openedmatangover/mypy-vscode

Python executable from venv is not used

For some reason the mypy extension doesn't recognize my python executable in a venv.

The log output shows

Mypy extension activated, version 0.2.0
Registering listener for interpreter changed event
Waiting for Python extension to load
Python extension loaded
Listener registered
[1] Check workspace: ${workspaceFolder}
[1] Using config file: mypy.ini
[1] Received python path from Python extension: /usr/bin/python3
[1] Running dmypy in folder ${workspaceFolder}
${workspaceFolder}/env/bin/dmypy --status-file /home/alex/.config/Code/User/workspaceStorage/c75fa14f80a26f7dcd6661af27693d09/matangover.mypy/dmypy-80690f3ce6c54e9de14878ef29f8a83a93369fd9.json run --log-file /home/alex/.config/Code/User/workspaceStorage/c75fa14f80a26f7dcd6661af27693d09/matangover.mypy/dmypy-80690f3ce6c54e9de14878ef29f8a83a93369fd9.log -- . --show-column-numbers --no-error-summary --no-pretty --no-color-output --config-file mypy.ini --python-executable /usr/bin/python3

The --python-executable /usr/bin/python3 is the problem here. It should be ${workspaceFolder}/env/bin/python

The mypy settings are

{
    "mypy.configFile": "mypy.ini",
    "mypy.dmypyExecutable": "${workspaceFolder}/env/bin/dmypy",
    "mypy.targets": ["."]
}

Interestingly, the python extension outputs the following logs, showing that it runs pylance with the system python, but the linters with the venv one:

...
Python interpreter path: /usr/bin/python3
Starting Pylance language server.
> conda --version
Python interpreter path: ${workspaceFolder}/env/bin/python
... (invocations of flake8 and pycodestyle)

Unfortunately, it is not possible in vscode to specify the python path manually (for security reasons). Setting "run using active interpreter" tries to run everything using using the system python which is also not what I want.

created time in 2 months