-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing issues caused by breaking changes in closql #246
base: master
Are you sure you want to change the base?
Conversation
Thank you for the fix @phelrine. I'm using your |
I too have been using this branch. |
Same here 👍 |
Thank you to @phelrine for this fix! Any idea if this will be merged in anytime? |
@wandersoncferreira this patch resolves a breaking issue introduced in an upstream dependency; would you mind taking a look? |
Thank you for the fix @phelrine! Also for others who encounter this issue with spacemacs:
|
The current main branch is broken, but this pull request works great! |
Not relevant anymore
(closql-db 'code-review-db-database 'code-review-db-connection
code-review-db-database-file t)
UPDATE no.2: |
Hi, the melpa version (20221206.113) doesn't have this fix and breaks with the current melpa magit closql package. |
@wandersoncferreira Any chance of taking a look? |
This pull request resolves an issue caused by breaking changes in closql (#245). The fix was implemented using a commit (magit/forge@af9358d) as a reference.
Furthermore, there was another issue causing test failures due to changes in the return value of
-contains-p
(magnars/dash.el@112aa7c#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197eaR28-R29). This issue has also been resolved in this pull request.