Wojtek Mach
@wojtekmach.bsky.social
Updated, thanks. Please send PRs for any further edits you'd like to see.
October 28, 2025 at 3:52 PM
Updated, thanks. Please send PRs for any further edits you'd like to see.
Can this result in the problem mentioned here? elixirforum.com/t/why-does-e...
Why does Ecto require the use of is_nil/1?
Imagine you write this query: from User, where: [api_token: ^params["token"]], limit: 1 Now if someone passes no token, you will accidentally login as any of the users without a token.
elixirforum.com
July 24, 2025 at 3:34 AM
Can this result in the problem mentioned here? elixirforum.com/t/why-does-e...
Looks cool!
Consider calling it EctoRelation, Ecto.* is by convention reserved for the Ecto project.
"Dynamically" defined get_by_* and find_by_* are interesting, does get_by_this_and_that also works for a compound index? Have you considered find_by(fields) and warn (not error!) on missing index?
Consider calling it EctoRelation, Ecto.* is by convention reserved for the Ecto project.
"Dynamically" defined get_by_* and find_by_* are interesting, does get_by_this_and_that also works for a compound index? Have you considered find_by(fields) and warn (not error!) on missing index?
July 9, 2025 at 7:57 AM
Looks cool!
Consider calling it EctoRelation, Ecto.* is by convention reserved for the Ecto project.
"Dynamically" defined get_by_* and find_by_* are interesting, does get_by_this_and_that also works for a compound index? Have you considered find_by(fields) and warn (not error!) on missing index?
Consider calling it EctoRelation, Ecto.* is by convention reserved for the Ecto project.
"Dynamically" defined get_by_* and find_by_* are interesting, does get_by_this_and_that also works for a compound index? Have you considered find_by(fields) and warn (not error!) on missing index?
This was a compiler regression that has been fixed since. You got super unlucky.
That's why I was thinking about only testing against bleeding edge on nightly/weekly/etc builds and not on PRs. I.e. it's a signal mechanism to report upstream bugs but it shouldn't block downstream projects.
That's why I was thinking about only testing against bleeding edge on nightly/weekly/etc builds and not on PRs. I.e. it's a signal mechanism to report upstream bugs but it shouldn't block downstream projects.
May 28, 2025 at 8:27 AM
This was a compiler regression that has been fixed since. You got super unlucky.
That's why I was thinking about only testing against bleeding edge on nightly/weekly/etc builds and not on PRs. I.e. it's a signal mechanism to report upstream bugs but it shouldn't block downstream projects.
That's why I was thinking about only testing against bleeding edge on nightly/weekly/etc builds and not on PRs. I.e. it's a signal mechanism to report upstream bugs but it shouldn't block downstream projects.
hexpm/bob manages docker hub images under hexpm username and Ubuntu builds used by eg GHA. erlef/otp_builds manages macOS builds used by elixir-lang.org/install.sh.
Both are community projects outside of OTP and Elixir core teams, ie no need to wait for their stamp of approval.
Both are community projects outside of OTP and Elixir core teams, ie no need to wait for their stamp of approval.
May 22, 2025 at 8:20 PM
hexpm/bob manages docker hub images under hexpm username and Ubuntu builds used by eg GHA. erlef/otp_builds manages macOS builds used by elixir-lang.org/install.sh.
Both are community projects outside of OTP and Elixir core teams, ie no need to wait for their stamp of approval.
Both are community projects outside of OTP and Elixir core teams, ie no need to wait for their stamp of approval.
You can do that with erlef/setup-beam too, set elixir-version: main, otp-version: master.
Bonus points for running nightly/weekly/etc job so tests run even if repo is calm. If this catches intended or unintended breakage, it’s so much better to find out immediately than on RC or final release.
Bonus points for running nightly/weekly/etc job so tests run even if repo is calm. If this catches intended or unintended breakage, it’s so much better to find out immediately than on RC or final release.
May 22, 2025 at 8:13 PM
You can do that with erlef/setup-beam too, set elixir-version: main, otp-version: master.
Bonus points for running nightly/weekly/etc job so tests run even if repo is calm. If this catches intended or unintended breakage, it’s so much better to find out immediately than on RC or final release.
Bonus points for running nightly/weekly/etc job so tests run even if repo is calm. If this catches intended or unintended breakage, it’s so much better to find out immediately than on RC or final release.