Continuous builds with Gradle!
A parser for C-programs, using a dynamic list-implementation and an abstract machine. This work is done for an exercise.
An elegant not so bright snazzy-ui-theme as supplement to atom-snazzy-syntax
Helps developers maintain consistent coding styles between different editors
Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support
Assets management for Lotus
The hackable text editor
Atom-package to provide an API to the Java-environment for Atom-packages.
A fantastic atom-pane! Wrap your content with ease and rainbows.
An elegant not so bright snazzy-syntax-theme for Atom -- based on https://github.com/sindresorhus/iterm2-snazzy
issue commentelixir-lang/elixir
`mix test –cover` crashes with a `FunctionClauseError`
Thank you for your work!
comment created time in an hour
issue closedelixir-lang/elixir
`mix test –cover` crashes with a `FunctionClauseError`
Environment
Erlang/OTP 23 [erts-11.1.5] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [hipe]
Elixir 1.11.3 (compiled with Erlang/OTP 23)
macOS 11.1 (20C69)
Current behavior
On a project I am maintaining I get the following error when running mix test --cover:
Cover compiling modules ...
** (exit) an exception was raised:
** (FunctionClauseError) no function clause matching in :cover."-patch_code1/2-lc$^0/1-1-"/1
cover.erl:2181: :cover."-patch_code1/2-lc$^0/1-1-"(2)
cover.erl:2181: :cover.patch_code1/2
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:2191: :cover.patch_code_tuple/5
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:1649: :cover.transform/4
cover.erl:602: :cover.call/1
(mix 1.11.3) lib/mix/tasks/test.coverage.ex:142: anonymous fn/2 in Mix.Tasks.Test.Coverage.cover_compile/1
(elixir 1.11.3) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3
(mix 1.11.3) lib/mix/tasks/test.coverage.ex:141: Mix.Tasks.Test.Coverage.cover_compile/1
(mix 1.11.3) lib/mix/tasks/test.coverage.ex:122: Mix.Tasks.Test.Coverage.start/2
(mix 1.11.3) lib/mix/tasks/test.ex:336: Mix.Tasks.Test.do_run/3
(mix 1.11.3) lib/mix/task.ex:394: Mix.Task.run_task/3
(mix 1.11.3) lib/mix/task.ex:439: Mix.Task.run_alias/5
08:53:12.591 [error] Process #PID<0.3787.0> raised an exception
** (FunctionClauseError) no function clause matching in :cover."-patch_code1/2-lc$^0/1-1-"/1
cover.erl:2181: :cover."-patch_code1/2-lc$^0/1-1-"(2)
cover.erl:2181: :cover.patch_code1/2
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:2191: :cover.patch_code_tuple/5
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:2183: :cover."-patch_code1/2-lc$^1/1-0-"/2
cover.erl:1649: :cover.transform/4
Expected behavior
The mix task should finish without an error and generate a coverage report.
closed time in 2 hours
ckruse
issue commentelixir-lang/elixir
`mix test –cover` crashes with a `FunctionClauseError`
Thanks for the isolation, it helped a ton. PR to OTP sent here: https://github.com/erlang/otp/pull/2997
Please rename the function for now. :)
comment created time in 2 hours
startedAbstractMachinesLab/mix_caramel
started time in 2 hours
pull request commentphoenixframework/phoenix
heroku.md: Remove unnecessary "longpoll: false"
:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:
comment created time in 4 hours
push eventphoenixframework/phoenix
commit sha fdafd8563c16ed997a2b8a4ec7d73de62b52c238
heroku.md: Remove unnecessary "longpoll: false" (#4147) Per https://hexdocs.pm/phoenix/Phoenix.Endpoint.html#socket/3, this is already the default.
push time in 4 hours
PR merged phoenixframework/phoenix
Per https://hexdocs.pm/phoenix/Phoenix.Endpoint.html#socket/3, this is already the default, so perhaps not worth mentioning.
Unless I'm missing something and this setting is extra important in the context of Heroku – if so, perhaps the docs could say a bit more about that.
pr closed time in 4 hours
push eventphoenixframework/phoenix
Niels Kristian Hansen Skovmand
commit sha 32c906fc96d030113d95e0e8be49299b640c7b1f
Use consistent naming of Node.js in Phoenix, also to distinguish from a node in the elixir sense (#4150)
push time in 4 hours
pull request commentphoenixframework/phoenix
Use consistent naming of Node.js in docs
:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:
comment created time in 4 hours
push eventphoenixframework/phoenix
Niels Kristian Hansen Skovmand
commit sha d8f2f90fcd85b4a3b1cf214be292cdb77c7271f1
Use consistent naming of Node.js in Phoenix, also to distinguish from a node in the elixir sense (#4150)
push time in 4 hours
PR merged phoenixframework/phoenix
Across the Phoenix docs, Node.js is spelled differently as e.g. "node", "NodeJS", "Node.JS", etc, but the correct spelling is Node.js. This is corrected across the project in this PR.
The term "node" is also easy to confuse with erlang nodes, so it improves the clarity to use Node.js.
References for Node.js being the correct spelling:
- https://nodejs.org/en/
- https://github.com/nodejs/node/pull/33088
pr closed time in 4 hours
push eventphoenixframework/phoenix
commit sha acdfcadb84a8b6a7b86bc79da3982692262158cc
Update @unsent Plug.Conn states (#4159)
push time in 4 hours
pull request commentphoenixframework/phoenix
Update `@unsent` Plug.Conn states to include `:set_chunked` and `:set_file`
:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:
comment created time in 4 hours
PR merged phoenixframework/phoenix
We use @unsent to raise an AlreadySentError if trying to change the view or the layout after a response is sent. This updates the module variable to include the other unsent states from https://github.com/elixir-plug/plug/blob/40efbe4680f98eb063ea1e17f079c4243b6593cf/lib/plug/conn.ex#L258
It might be nicer to expose unsent?/sent? as functions on Plug.Conn itself. What do you think?
pr closed time in 4 hours
pull request commentphoenixframework/phoenix
Fix phx.gen.auth confirm_account test arity description
Thank you, @aaronjensen! Here is the PR for phx_gen_auth: https://github.com/aaronrenner/phx_gen_auth/pull/109
comment created time in 5 hours
fork yyx990803/cypress-realworld-app
A payment application to demonstrate real-world usage of Cypress testing methods, patterns, and workflows.
fork in 5 hours
issue commentphoenixframework/phoenix_live_view
External upload not finished when `consume_uploaded_entries` is called
Opened #1321 with your snippet 👍
comment created time in 7 hours
startedCraigFe/progress
started time in 11 hours
startedmafintosh/autoname
started time in 11 hours
startedmafintosh/autoname
started time in 13 hours
created repositorymafintosh/autoname
Auto naming of objects for easier debugging
created time in 13 hours