test-unit | test-unit - An xUnit family unit testing framework for Ruby | Unit Testing library

The @Mock annotation must be the reason that Spring doesn't use the config class "BeanConfiguration". which makes sence after all.

This is not an official solution. I'm sure the rbenv devs are working on an actual solution but this workaround should help others who are setting up their ruby environments on the new M1 chips for Mac.

• Make sure your Terminal is using Rosetta. You can find how to do that using Google.

• Uninstall your current rbenv following these instructions Removing rbenv. Be sure you also remove all the downloaded versions of ruby if you have any (minus the system default) located in /Users//.rbenv/versions/.

• Uninstall the ARM version of Homebrew with: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall.sh)"

• Install the x86_64 version of Homebrew with: arch -x86_64 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

• If you run brew install rbenv should produce output saying "Error: Cannot install in Homebrew on ARM processor in Intel default prefix (/usr/local)!". This is expected.

• You want to tell brew to install the older architecture x86_64 arch -x86_64 brew install rbenv

• Then finally install the version you want using arch -x86_64 rbenv install x.x.x (x = some number i.e. 2.7.2)

From there you just need to remember to tell brew arch -x86_64 when installing other versions of Ruby.

Once an actual fix comes through you'll be able to switch back to the newer architecture and not have to use the arch argument. You also don't have to do this all the time with brew either, just rbenv.

Your symptom implies that $ErrorActionPreference = 'Stop' is in effect at the time function
Test-Validation executes. (Temporarily) set it to 'Continue' to fix your problem - which in future versions will hopefully no longer required (see below).

The reason for the observed behavior is that, as of PowerShell 7.1, using an error-stream redirection (2>) makes PowerShell route an external program's stderr output through PowerShell's error stream (see about_Redirection), and $ErrorActionPreference = 'Stop' therefore throws a script-terminating error once the first stderr line is received.

This behavior is unfortunate, because stderr output from external programs cannot be assumed to represent an error condition, given that external programs in effect use stderr, the standard error stream, for anything that other than data, which includes status information, for instance.

The preview versions of PowerShell 7.2 (7.2 hasn't been released yet as of this writing) have an experimental feature named PSNotApplyErrorActionToStderr, which changes this behavior for the better: stderr output is no longer routed through PowerShell's error stream, which means that:

• Stderr lines are (fortunately) no longer collected in the automatic $Error variable.

• Preference variable $ErrorActionPreference no longer has any impact on stderr output from external programs.

• The automatic $? variable, which indicates the success status of the most recently executed statement, is no longer incorrectly set to $false when the process exit code is 0 and there also happens to be stderr output - though note that you can always infer success vs. failure of external programs via the automatic $LASTEXITCODE variable

Note:

• In preview versions of PowerShell all experimental features are turned on by default, whereas they're off by default in release candidates and officially released versions.

• An experimental feature is not guaranteed to become an official feature; whether it will is determined based on user feedback and usage data. At least formally, the change at hand represents a breaking change.

This is a RubyMine bug. Nothing we can fix on the Cucumber end.

You can either consult a non-recommended monkeypatch / hack. Or downgrade to an early version of Cucumber5.

See https://youtrack.jetbrains.com/issue/RUBY-27294 for more information, including other possible workarounds and a time-frame for the fix from Jetbrains.

Luke - Cucumber Ruby committer.

I finally solved the issue through:

• Removing USER ciuser from the Dockerfile so that the runner is starting with the root user again
• Changing the test command as follows sudo -H -u ciuser bash -c "npm install && npm run test:cobertura" so that it is executed by the ciuser as it is described in this post.

As you just removed the files instead of using apt-get or dpkg to uninstall the package, the package management is not aware of your manual removal, and so apt-get and dpkg still think the newest version is already installed, and so do nothing.

apt-get --reinstall install vagrant

should solve this.

I could install the plugin manually via vagrant plugin install vagrant-disksize command.

Via Vagrant itself, it is still not working.

This question has a lot in common with mine, maybe even a dupe. This answer took me a couple reads, but it led me to read the node documentation (gasp!). I inferred that package authors build and publish to npm (which is obvious), but that npm install doesn't actually go to git to grab the files, instead they have a tar from the publishing process. That was the missing part for me. Anyway, if you want to have your own personal package built on install, use prepare.

Rather than using /usr/bin/ruby which is the system installed Ruby, use the hashbang