-
Notifications
You must be signed in to change notification settings - Fork 3
Conversation
Codecov Report
@@ Coverage Diff @@
## master #425 +/- ##
==========================================
- Coverage 59.81% 58.73% -1.09%
==========================================
Files 44 7 -37
Lines 443 126 -317
Branches 87 27 -60
==========================================
- Hits 265 74 -191
+ Misses 165 50 -115
+ Partials 13 2 -11
Continue to review full report at Codecov.
|
@redreceipt this is ready to merge |
@redreceipt the failing migration is a migration that existed way before this body of work :/ I would recommend wiping out your postgres development server and starting from scratch. I'll preempt your question and argue that this is okay ;) If it works from scratch, that will match where most clients are starting from. All of our clients that I checked (newspring and rivervalley) haven't run that migration yet, but also don't have the As for
You are pointing at your local postgres right? You'll also need to run the shovel locally. Or you can swap out your database url for the production postgres URL in the shared.env.enc |
I was pointing at the core production DB for these errors
… On Jul 19, 2021, at 2:47 PM, Vincent Wilson ***@***.***> wrote:
@redreceipt <https://github.com/redreceipt> the failing migration is a migration that existed way before this body of work :/ I would recommend wiping out your postgres development server and starting from scratch.
I'll preempt your question and argue that this is okay ;)
If it works from scratch, that will match where most clients are starting from. All of our clients that I checked (newspring and rivervalley) haven't run that migration yet, but also don't have the personId field. They will not run into issues.
As for
images and content aren't coming through
You are pointing at your local postgres right? You'll also need to run the shovel locally. Or you can swap out your database url for the production postgres URL in the shared.env.enc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#425 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUJJFRBSB3VGHFGOGY77HLTYRXN3ANCNFSM5AG2CWJQ>.
|
@redreceipt Ah - that makes more sense actually. The DB was in a weird state since we were deving with it. I reset it and you should be gtg now. |
@redreceipt My bad again 😬 I didn't backfill people after I wiped the DB, give it another go. No need to change again, just try logging in again. |
haha - I broke it when I wiped the DB (since the config.yml points at IDS in the DB now) Let me fix and confirm and then I'll circle back |
@redreceipt Ready for review again. A few notes...
|
Continue feature being broken ... that's a tough one :/ we'll likely do a follow up PR that fixes that specific case. We will be able to come up with a really robust fix when we port in Interactions into postgres. Edit - by "a tough one", I mean that it's a result of you having completed some items that are now referenced by a different ID. I think we need to filter those results out entirely instead of showing this weird state. |
So safe to assume churches that use Rock events (Willow may be the only one???) can't use the DB until we fix events? |
Correct! Well actually Willow might be fine since their implementation of events is largely custom anyway. I've captured the bugs here in this todo list: https://3.basecamp.com/3926363/buckets/6947926/todolists/3971672104 Anything captured in this list I hope to finish this cycle. I really want to get this PR merged so we have some solid ground to work off of, once this is merged we'll be able to go back to smaller focused PR's instead of trying to work around the monolith :) |
I think it's important we treat this template as a working app with working features. The only reason I'm being a stickler is with more and more apps, the upgrade process needs to be smooth and with some features not working on the DB in the template, that could get very difficult to track. I'm committing to upgrading and releasing an app every eight weeks and need to be able to count on the template app not having accepted bugs in it. |
we decided to fix the obvious bugs before merging this PR, more updates to come... |
Summary of slack huddle: Setting this to draft |
@redreceipt "Series in Progress" empty state is broken on master as well It's actually a bug with the content card. The API is sending over the same response every time, but the front end doesn't render the message type correctly I think?
|
well dang. I hated that feature as I was writing it... |
…into content-item-datasource
@redreceipt Once this release finishes (https://github.com/ApollosProject/apollos-apps/actions/runs/1050109938) this PR will be ready for review again. Taking it back out of draft. |
@redreceipt yahhh this is going to be problamatic. The old config.yml and the new postgres config.yml use different formats. Should we create a |
no it's a network error, I'll track it down. you probably can't reproduce unless you log out in between. i bet it's the config yml thing |
@redreceipt I can reproduce, and it looks like an error in Rock caused by trying to filter by a |
No description provided.