tovarchristian21
Hello guys, has anyone ever encountered this kind error with yamerl ?. I’m trying to setup a CD, but I’m having trouble with the following output:
...
* Getting meck (Hex package)
* Getting bunt (Hex package)
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling yamerl
##[error]/home/runner/work/podnation/podnation/deps/yamerl/include/internal/yamerl_constr.hrl:45: Warning: record unfinished_node has field(s) without type information
##[error]/home/runner/work/podnation/podnation/deps/yamerl/include/internal/yamerl_constr.hrl:52: Warning: record node_anchor has field(s) without type information
...
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
Does your build fail because of that? Or is it just printed?
If it’s just printed, you can’t fix it, but might be worth a bug report upstream.
If your build fails because of that, try to build without
:warnings_as_errorsif that helps.wolf4earth
AFAIK will the
:warnings_as_errorsoption ---warnings-as-errorson the CLI - only fail when you have warnings in your current project.I’ve just tested it locally with a project where we also use
yamerland we see the same warnings but the build doesn’t fail.NobbZ
Yeah, warnings as errors should not affect building of dependencies. But it was not clear for me what is actually the problem, therefore I just suggested to try.
tovarchristian21
Thank for the help, it has been solved. Apparently someone added a wrong configuration that could not be handled by the CI runner. Thanks again for checking this issue.