fix postgres adapter migration extension creation which already exists at this point #2188
Conversation
This file contains 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
odilitime
approved these changes
Jan 12, 2025
odilitime
added a commit
that referenced
this pull request
Jan 12, 2025
* chore: lint and fix pass on develop (#2180) * typo fix: close object * update lockfile * lint fixes * processAtions can't be awaited in non-async function * revert GoPlusType so it can work with switch statement * lint fixes * processAtions can't be awaited in non-async function * revert GoPlusType so it can work with switch statement * bump lock * merge, fix conflicts * convert imageDescriptionsArray from let to const per lint * remove duplicate TOGETHER in case, lint/unused var * bump eslint so it doesn't crash * comment out unused AkashMessage interface * clean up unused var in catch * bump * Add Persian README File * fix path * fix quai deps * fix json format typo * Update types.ts * fix postgres adapter migration extension creation which already exists at this point (#2188) * fix(client-twitter): clean up mention deduplication (#2185) Co-authored-by: Odilitime <janesmith@airmail.cc> * feat(security): Implement comprehensive file upload security measures - Add FileSecurityValidator, file type restrictions, size limits, path traversal prevention, enhanced logging and security documentation (#1753) (#1806) Co-authored-by: Odilitime <janesmith@airmail.cc> * bump version --------- Co-authored-by: Ali <amohammadzadeh@interrodata.com> Co-authored-by: Masterdai <daizhengxue828@gmail.com> Co-authored-by: koloxarto <106516707+web3gh@users.noreply.github.com> Co-authored-by: Nuri Hodges <nhodges@users.noreply.github.com> Co-authored-by: AIFlow_ML <mlstudio@aiflow.ml>
mgunnin
added a commit
to CainamVentures/cainam-agent
that referenced
this pull request
Jan 12, 2025
* main: (704 commits) bump version (elizaOS#2193) feat(security): Implement comprehensive file upload security measures - Add FileSecurityValidator, file type restrictions, size limits, path traversal prevention, enhanced logging and security documentation (elizaOS#1753) (elizaOS#1806) fix(client-twitter): clean up mention deduplication (elizaOS#2185) fix postgres adapter migration extension creation which already exists at this point (elizaOS#2188) Update types.ts fix json format typo fix quai deps fix path Add Persian README File chore: lint and fix pass on develop (elizaOS#2180) bump version to 0,1,8 bump clean up unused var in catch comment out unused AkashMessage interface bump eslint so it doesn't crash remove duplicate TOGETHER in case, lint/unused var convert imageDescriptionsArray from let to const per lint fix: Koloxarto/fix ragknowledge for postgres (elizaOS#2153) fix: fix the chat stuck in infinite loop (elizaOS#1755) fix: remove problematic redundant uuid conversion and add api input param validations to api server (elizaOS#2051) ...
0xpi-ai
pushed a commit
to 0xpi-ai/NayariAI
that referenced
this pull request
Jan 15, 2025
0xpi-ai
pushed a commit
to 0xpi-ai/NayariAI
that referenced
this pull request
Jan 15, 2025
* chore: lint and fix pass on develop (elizaOS#2180) * typo fix: close object * update lockfile * lint fixes * processAtions can't be awaited in non-async function * revert GoPlusType so it can work with switch statement * lint fixes * processAtions can't be awaited in non-async function * revert GoPlusType so it can work with switch statement * bump lock * merge, fix conflicts * convert imageDescriptionsArray from let to const per lint * remove duplicate TOGETHER in case, lint/unused var * bump eslint so it doesn't crash * comment out unused AkashMessage interface * clean up unused var in catch * bump * Add Persian README File * fix path * fix quai deps * fix json format typo * Update types.ts * fix postgres adapter migration extension creation which already exists at this point (elizaOS#2188) * fix(client-twitter): clean up mention deduplication (elizaOS#2185) Co-authored-by: Odilitime <janesmith@airmail.cc> * feat(security): Implement comprehensive file upload security measures - Add FileSecurityValidator, file type restrictions, size limits, path traversal prevention, enhanced logging and security documentation (elizaOS#1753) (elizaOS#1806) Co-authored-by: Odilitime <janesmith@airmail.cc> * bump version --------- Co-authored-by: Ali <amohammadzadeh@interrodata.com> Co-authored-by: Masterdai <daizhengxue828@gmail.com> Co-authored-by: koloxarto <106516707+web3gh@users.noreply.github.com> Co-authored-by: Nuri Hodges <nhodges@users.noreply.github.com> Co-authored-by: AIFlow_ML <mlstudio@aiflow.ml>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to
Risks
Low
Background
What does this PR do?
Fix initial setup of postgres
What kind of change is this?
bug fix
Why are we doing this? Any context or related work?
To make the initial postgres setup work
Documentation changes needed?
My changes do not require a change to the project documentation.
Testing
setup a new postgres database.
Where should a reviewer start?
Detailed testing steps