profile
viewpoint
Santiago Sanchez Guisanpea Málaga, Spain Long term student, my passion is computer science and learning. Humility, patience

Guisanpea/dotfiles 5

My dotfiles to share with the world

ConsejoInfUMA/Hackers-Week-3.0 2

Página en desarrollo de la sexta edición de la Hackers<>Week

Guisanpea/A-to-Z-Resources-for-Students 0

Curated list of resources for college students :octocat: Show your :heart: by giving a :star:

Guisanpea/agenda 0

Simple Agenda

issue commentelixir-lsp/elixir-ls

How to change MIX_ENV in debugger?

Hello! After some findings I was thinking that I was using test env because I saw some errors of the type

Started ElixirLS debugger v0.8.1
Elixir version: "1.12.3 (compiled with Erlang/OTP 22)"
Erlang version: "24"
ElixirLS compiled with Elixir 1.12.2 and erlang 24
(Debugger) Initialization failed because an exception was raised:
    ** (RuntimeError) could not lookup Ecto repo HelloWorld.Repo because it was not started or it does not exist
        Elixir.Ecto.Repo.Registry.erl:19: Ecto.Repo.Registry.lookup/1
        Elixir.Ecto.Adapter.erl:127: Ecto.Adapter.lookup_meta/1
        Elixir.Ecto.Adapters.SQL.Sandbox.erl:538: Ecto.Adapters.SQL.Sandbox.lookup_meta!/1
        Elixir.Ecto.Adapters.SQL.Sandbox.erl:435: Ecto.Adapters.SQL.Sandbox.mode/2

03:35:15.217 [error] Process #PID<0.117.0> raised an exception
** (RuntimeError) could not lookup Ecto repo HelloWorld.Repo because it was not started or it does not exist
    Elixir.Ecto.Repo.Registry.erl:19: Ecto.Repo.Registry.lookup/1
    Elixir.Ecto.Adapter.erl:127: Ecto.Adapter.lookup_meta/1
    Elixir.Ecto.Adapters.SQL.Sandbox.erl:538: Ecto.Adapters.SQL.Sandbox.lookup_meta!/1
    Elixir.Ecto.Adapters.SQL.Sandbox.erl:435: Ecto.Adapters.SQL.Sandbox.mode/2

Then I found out that the issue was the same as the one pointed in https://github.com/elixir-lsp/elixir-ls/issues/451. So the solution was that by default the included files were

"requireFiles": [
    "test/**/test_helper.exs",
    "test/**/*_test.exs"
]

Which made the sandbox to try to be launched. Now setting the requireFiles nil as

(dap-register-debug-template
  "Task Get Main DB"
  (list :type "Elixir"
        :name "mix get_data_from_main_db"
        :env '(("MIX_ENV" . "dev"))
        :task "get_data_from_main_db"
        :requireFiles nil
        :request "launch"))

everything works as a charm. Thanks for the help and apologies for the confusion!

Guisanpea

comment created time in 13 days

issue closedNixOS/nix

Create a bottom up tutorial on Nix

Is your feature request related to a problem? Please describe. I have been through the last days trying to understand Nix better. Concretely, what I have been trying to achieve is to make i3-gnome work After an attempt of tying to do it in the past.

I feel that there are a lot of concepts that I don't really fully grasp. Why does nix need a /nix/store path What is the purpose of the Nix DB? How does a derivation really work? What does support NixOS /etc/nixos/configuration.nix and makes it work?

I expected the How Nix works guide to teach me all this stuff, but I feel that more than showing how it works it teaches me the principles behind me and how it works

Describe the solution you'd like I would like to have a guide that teaches Nix from first principles so that every concept that is seen can be understood by its own or by using previously seen lessons

Describe alternatives you've considered The alternative I have used is to go through several videos/pages that explain all that concepts and trimming the manuals and wiki until I get more or less how everything works. Nevertheless I feel that I don't really understand Nix/NixOS and the foundations of my knowledge are very poor (thus I cannot create that package)

Additional context I really want to learn NixOS. I feel that all the concepts behind it is what I expect from my desirable OS experience, nevertheless my experience has been that at the beginning I have to accept that I won't be able to use my desired environment (i3 + Gnome) because no one has created it before and I have to use Nix to understand Nix.

It's good that a lot of things are abstracted in documentation because no one wants to understand the internals of software in order to use it, but at the end there will be something that is very low level which hasn't been abstracted and in order to be able to perform that task you really need to understand the details and I feel that it is the missing piece in the Nix documentation.

At least that is my feeling, maybe (and probably) I have missed something

closed time in 13 days

Guisanpea

issue commentelixir-lsp/elixir-ls

How to change MIX_ENV in debugger?

@lukaszsamson I already added the environment indeed. This is my config (emacs)

  "Task Get Main DB"
  (list :type "Elixir"
        :name "mix get_data_from_main_db"
        :env '(("MIX_ENV" . "dev"))
        :task "get_data_from_main_db"
        :request "launch"
        :program nil
        :name "Get Main DB"))```
        
Nevertheless I have tried and it looks like it is still using lsp env which is `test`. I will nevertheless try `:preferred_cli_env` instead. I think that it would be nice to configure the env for lsp
Guisanpea

comment created time in 13 days

issue openedelixir-lsp/elixir-ls

How to change MIX_ENV in debugger?

Environment

  • Elixir & Erlang versions (elixir --version):
Started ElixirLS v0.8.1
Elixir version: "1.12.3 (compiled with Erlang/OTP 22)"
Erlang version: "24"
ElixirLS compiled with Elixir 1.12.2 and erlang 24
  • Operating system: Ubuntu 20.04
  • Editor or IDE name (e.g. Emacs/VSCode): Emacs
  • Editor Plugin/LSP Client name: dap-mopde

Logs

When launching the debugger in lsp-log I see the following:

MIX_ENV: test
MIX_TARGET: host

I want to debug my system with the dev environment. How can I do it?

Thanks for your work. ElixirLS is an amazing project

created time in 13 days

push eventGuisanpea/dotfiles

Santi

commit sha 25d67da6133d596409954f84acb8003747166eaa

Added .Xresources

view details

push time in 19 days

create barnchGuisanpea/nixfiles

branch : master

created branch time in 21 days

created repositoryGuisanpea/nixfiles

created time in 21 days

push eventGuisanpea/dotfiles

Santi

commit sha 391cd5c0b9548da07a86b1d164dfe852fa9ae404

Removed autocd from zsh

view details

push time in 21 days

pull request commenttpolecat/doobie

remove quill integration

I firmly believe that we should respect library authors deciding not to maintain a project any longer, regardless of the impact it may have on the community.

Open source contributors are regular people who choose to spend their spare time creating something good for the rest of us. The time they are contributing to their projects is time they are not dedicating to their personal life.

Even if you don't care about library authors, if they work on something they are not comfortable with, they are less likely to make it great.

And I think that it is not a big deal if doobie-quill stops being developed by @tpolecat. It can still be developed by other people who really feel like doing it. That's the good thing about functional programming, we can compose things. Doobie is a lego piece and Quill is another lego piece, if the maintainer of one of those is not a maintainer of the combination it is not that big of a deal.

If we want a healthy open source community let maintainers be free and make their decisions without consequences

tpolecat

comment created time in 24 days

startedjarun/nnn

started time in 25 days

starteddbeaver/dbeaver

started time in a month

issue openedNixOS/nix

Create a bottom up tutorial on Nix

Is your feature request related to a problem? Please describe. I have been through the last days trying to understand Nix better. Concretely, what I have been trying to achieve is to make i3-gnome work After an attempt of tying to do it in the past.

I feel that there are a lot of concepts that I don't really fully grasp. Why does nix need a /nix/store path What is the purpose of the Nix DB? How does a derivation really work? What does support NixOS /etc/nixos/configuration.nix and makes it work?

I expected the How Nix works guide to teach me all this stuff, but I feel that more than showing how it works it teaches me the principles behind me and how it works

Describe the solution you'd like I would like to have a guide that teaches Nix from first principles so that every concept that is seen can be understood by its own or by using previously seen lessons

Describe alternatives you've considered The alternative I have used is to go through several videos/pages that explain all that concepts and trimming the manuals and wiki until I get more or less how everything works. Nevertheless I feel that I don't really understand Nix/NixOS and the foundations of my knowledge are very poor (thus I cannot create that package)

Additional context I really want to learn NixOS. I feel that all the concepts behind it is what I expect from my desirable OS experience, nevertheless my experience has been that at the beginning I have to accept that I won't be able to use my desired environment (i3 + Gnome) because no one has created it before and I have to use Nix to understand Nix.

It's good that a lot of things are abstracted in documentation because no one wants to understand the internals of software in order to use it, but at the end there will be something that is very low level which hasn't been abstracted and in order to be able to perform that task you really need to understand the details and I feel that it is the missing piece in the Nix documentation.

At least that is my feeling, maybe (and probably) I have missed something

created time in a month

startedjavmarina/Switch-Signaling-Server

started time in a month

more