marcel | Marcel : One docker CLI to rule | Continuous Deployment library

ModuleNotFoundError: Module not found: Error: Can't resolve '@popperjs/core' suggests that you need to install @popperjs/core.

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

I was porting my existing app to heroku, so I created a separate branch called heroku to make the changes. I wanted to test first-time deployment to heroku before merging with my main branch.

So I was running $ git push heroku main expecting to push my local heroku branch to Heroku. Instead, it was pushing my main branch, which did not have the updated Rails gems.

Lesson learned, running $ git push heroku main pushes your main branch even if you are currently on a different branch.

I went into the settings for my Heroku app and did a manual build/deploy from Github of my heroku branch. App built and deployed successfully.

That passw.lower is a method, the method itself, you may call it to have the password in lowercase. Also remove passw != passw2 in second ìf that's mandatory True

Here's a slightly modified approach to count those words:

Yup, this looks fine to me.

If you want something to be unique, you should use that as the ID of your documents in a collection, which you're doing in your usernames collection.

That also ensures that you only need to read/check for the existence of a single document to determine if a username is already in use, which is the minimum number of document reads that is possible for such an operation.

Edited answer. See if this works for you

For each [FIN] it finds the largest [Laufleistung in km] from all prior rows, and compares the value to the current [Laufleistung in km] to see if they are at least 30 different

Gemfile.lock is a file generated from Gemfile. As such, instead of trying to merge the two branches, it's simpler and more accurate to generate a new one from its canonical source. This might result in slightly different versions, but these should cause no trouble; any version restrictions should be defined in your Gemfile.

Normally one does not commit generated files, they can change in trivial ways, but Gemfile.lock is a special case where you do want this to be the same for all builds.

Resolve any conflicts in the Gemfile. Regenerate Gemfile.lock. Add it.

for some reason he copied the code and added it himself

This is a good opportunity to explain to them why this is a bad practice when working with a team. It might be easy for them, but it's causing trouble for you. They might need instructing in how to update their work in progress. Or you might need to extract some changes into their own branch and get that merged.

You could change the storage of the values a bit by taking an object with roman signs as keys and decimal values.

For crating a recursive function, you could add an exit condition which is here just a check for an empty string and return zero in this case.

Then check if two character are in the object and if so take the value and add the result of calling the function again with the rest of the string.

If not take only the first character and the value and call the function again for getting the rest of the string.