-
-
Notifications
You must be signed in to change notification settings - Fork 500
Improve docker-tools for build --single
#2049
Improve docker-tools for build --single
#2049
Conversation
Links development-only files only in dev mode. Docs: Improve docs on .env.prototype
b9843e1 to
926b023
Compare
|
@bnmnetp. OK works for me after testing. Test failures may be OK; the tests need to be re-run. |
|
Tests are failing to start -- missing the runestone_test db !! What would cause that? |
|
tracking back a little further it is trying to run rsmanage but |
|
This is so weird, I can't even find anyplace in our code where we try to import cli from rsmanage. Running the tests locally on my dev build and all is fine, so it seems to be something in the setup for the tests. Any ideas??? |
|
I'm guessing this is something new/broken with Poetry 1.4.0. In which is probably where the import of |
|
OK, testing a fix now... |
|
looks like it somehow lost the docker-tools test command... |
|
I'm seeing this message: So something is going wrong with the import from |
|
Some real backward incompatibility in poetry 1.4? I see it was just released on the 2/27. I had rebuilt locally a few days before. Looking at the changelog I didn't see see anything to indicate such major changes. Looking at recent issues on github for poetry it seems there are a few that might be related... Do you think we should maybe stick with poetry 1.3.2 for a while? |
|
I had all of the tests passing as long as I used Now I see that my fixes are on my python 3.10 branch. If you think it is better to stick with 1.4.0 then maybe we should merge this and I can merge my 3.10 branch because that has more test fixes... |
|
That makes sense to me -- these fixes remove a lot of Poetry bug fix/workaround stuff, so I think it's a good step forward. Let's merge this, then you merge your 3.10 branch. Hopefully, that will get us back to all tests passing again! |
|
Do you want to merge this, or shall I? |
|
I'm on it. |
This implements ideas in #2048. Not much testing yet.
Fix:
Docs: