Skip to content

Conversation

@barnabasJ
Copy link
Contributor

@barnabasJ barnabasJ commented Nov 18, 2025

This shows that there is a problem where both calculations loaded the same value because the read action was not checked when checking if the relationships are the same ash-project/ash#2448

And it shows that the sort on the read action was not taking into account (makes the test flaky) ash-project/ash_sql#194

Contributor checklist

Leave anything that you believe does not apply unchecked.

  • I accept the AI Policy, or AI was not used in the creation of this PR.
  • [] Bug fixes include regression tests
  • Chores
  • Documentation changes
  • Features include unit/acceptance tests
  • Refactoring
  • Update dependencies

@barnabasJ barnabasJ force-pushed the test/multi-relationship-problems branch 2 times, most recently from 76e10e3 to 29db3e6 Compare November 18, 2025 12:09
@barnabasJ barnabasJ self-assigned this Nov 18, 2025
@barnabasJ barnabasJ added the bug Something isn't working label Nov 18, 2025
@@ -0,0 +1,124 @@
# SPDX-FileCopyrightText: 2019 ash_postgres contributors <https://github.com/ash-project/ash_postgres/graphs.contributors>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we put these tests in like calculations_test.exs for example?

@zachdaniel
Copy link
Contributor

looks like some conflicts came up.

@barnabasJ
Copy link
Contributor Author

barnabasJ commented Nov 22, 2025 via email

@zachdaniel
Copy link
Contributor

Just released ash, ash_sql and ash_postgres

@barnabasJ
Copy link
Contributor Author

Just released ash, ash_sql and ash_postgres

I can't see the ash release.

@barnabasJ barnabasJ force-pushed the test/multi-relationship-problems branch from e0f0055 to c0df739 Compare November 24, 2025 10:47
@zachdaniel
Copy link
Contributor

just released it sorry.

@zachdaniel
Copy link
Contributor

Looks like the update pointed out some warnings, mind addressing those here?

@barnabasJ
Copy link
Contributor Author

Looks like the update pointed out some warnings, mind addressing those here?

sure thing, sorry about that. I just blindly pushed after changing the ash version.

@zachdaniel zachdaniel merged commit 43e3493 into main Nov 27, 2025
66 of 67 checks passed
rgraff added a commit that referenced this pull request Dec 10, 2025
…tributes

* main: (23 commits)
  fix: do not build query filter with or: [] when all records are successfully inserted, for return_skipped_upsert?: true (#659)
  test: load aggregate with select and sort on from_many relationship (#661)
  test: add failing test for expr(has_one.function_calc) nil poisoning in batch (#660)
  test: aggregate with parent ref in relationship filter and sorting on relationship field (#658)
  test: binding error when loading aggregate (#657)
  chore(deps): bump ash_sql in the production-dependencies group (#656)
  test: multi relationship problems (#654)
  chore: release version v2.6.26
  chore: update ash_sql, use new select binding
  test: add complex calculation tests with filtered aggregates (#652)
  improvement: add generator to tsvector type (#655)
  test: add failing test for aggregate filtering on nested first aggregate (#653)
  chore: update ash_sql and add test
  docs: Mention :define_ecto_repo? option of use AshPostgres.Repo macro in getting started guide (#648)
  improvement: verify check constraint attributes at compile time
  chore: update ash
  chore: reuse compliance
  improvement: update deps for bug fixes
  chore: release version v2.6.25
  test: Add failing test for aggregate with parent() + select() + limit() (#644)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants