Version 2.6#2359
Open
rolandgeider wants to merge 128 commits into
Open
Conversation
This is needed since the move to vite on the react side
This wasn't working well with when used over the API
This still needs to be clean up (specially the key generation, at the moment we use a new dependency, but all this can be also done with the library we currently use)
most convenient and should be just fine
This is only needed because powersync can't handle joins
This reverts commit c6163de.
- move create publication to core - use ivm entries for the nutrition publications
# Conflicts: # wger/core/static/react/main.js
This is needed in the flutter app to properly be able to set IDs on device, since the regular IDs can only be set by postgres.
# Conflicts: # extras/docker/development/Dockerfile # extras/docker/production/settings.py # requirements.txt # wger/core/api/views.py # wger/nutrition/models/plan.py # wger/urls.py
# Conflicts: # extras/docker/production/settings.py # pyproject.toml # uv.lock # wger/weight/models.py
We don't need the ivm extension
This is needed to use social login, etc. in the app via the browser
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md # pyproject.toml # uv.lock # wger/core/api/serializers.py # wger/core/forms.py # wger/core/tests/test_user_login.py # wger/core/views/user.py
(specially with the upgrade steps)
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| result = handler.dispatch(http_verb, payload=payload, user_id=user_id) | ||
| except Exception as e: | ||
| logger.exception(f'Error processing PowerSync data for table {table}') | ||
| return JsonResponse({'error': str(e)}, status=200) |
Using the full ingredient table for powersync created a spike during the first sync, e.g. the WAL was bloating up to 25GB before returning to a normal size. While this is temporary it would place too big of hard disk requirements for self hoster for basically no gains.
The license author is now non-nullable
We were firing DB queries, which was making the test flaky
rolandgeider
force-pushed
the
feature/version-2.6
branch
from
b80efdc to
caf2fd8
Compare
This writes the new values in chunks instead of having to touch every row
Powersync may send a delete or put request several times because of retries, checkpoint replays etc, so the backend must be able to handle this
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Meta PR with backend incompatible changes