Powershell

All tags

Powershell cmdlets with dynamic param AND $args don't work

Over the weekend I tried to implement auto completion in Elixir’s mix (in Windows). Unfortunately I didn’t make it without introducing some problems. So I didn’t committed my changes to upstream. Currently I try to reach some of the more renowned Elixir/Windows contributors, to discuss the changes . Motivation Under normal circumstances I don’t use more mix tasks then test, phoenix.server and release but sometimes you need this weird command, you just can’t remember.

Elixir, Phoenix and Windows: No faster responses than 1000 microseconds?

If you read around phoenix developers you often hear stuff like “Awesome, requests served in under xxx microseconds!”. Yet if I try the Phoenix framework, I only have this results: [info] GET / [debug] Processing by GettingStartedPheonix.PageController.index/2 Parameters: %{} Pipelines: [:browser] [info] Sent 200 in 1000┬Ás [info] JOIN rooms:lobby to GettingStartedPheonix.RoomChannel Transport: Phoenix.Transports.WebSocket Parameters: %{} [info] Replied rooms:lobby :ok With special emphasis on [info] Sent 200 in 1000┬Ás .

Elixir, Windows and Chocolatey: Updates

Recently I ran in a problem with Elixir on Windows, installed via Chocolatey: After an update of the Elixir package: choco upgrade elixir (or a Windows update or something similar) I couldn’t use iex.bat anymore. Every time I tried to open iex.bat I got an crash_dump: {error_logger,{{2015,12,3},{22,35,15}},crash_report,[[{initial_call,{supervisor_bridge,user_sup,['Argument__1']}},{pid,<0.22.0>},{registered_name,[]},{error_info,... (That said, mix still worked…) After several attempts on reinstalling Elixir (and Erlang, just to be sure) I found this comment on the Elixir package on Chocolatey.

Elixir, postgres and chocolatey

You try to use the phoenix getting started guide on windows and the task “mix ecto.create” fails with an useless error? Chances are your postgresql database isn’t available with the ecto default credentials “postgres”:“postgres”. Try to logon to the database with the credentials “postgres”:“Postgres1234” and change the password for the user to “postgres”. Also, don’t forget to change the password of the Windows user “postgres”. Update 15.11.2015: You also have to change the logon information for the service, otherwise postgresql won’t start after an restart.