Cachet: Trait 'AltThree\TestBench\ValidationTrait' not found after upgrading 2.4

[krollebol]

I run Cachet 2.4 from git, it worked fine before. But last week I updated to latest git version following the upgrade procedure:

• php artisan down
• git pull
• composer install --no-dev -o --no-scripts
• php artisan app:update

At this stage I get an error:

PHP Fatal error:  Trait 'AltThree\TestBench\ValidationTrait' not found in /var/www/Cachet-dev/app/Models/Taggable.php on line 24

In Taggable.php line 24:

  Trait 'AltThree\TestBench\ValidationTrait' not found  

After 'php artisan up' the site works, but the incidents are not showing when "Only show days containing incidents in the timeline? " is activate in settings. Notting is shown in "Past incidents". "Stickied incidents" shows the incidents that are stickied.

Could this be related to the error?

On your demo site it still works as expected.

Thanks!

[welcome[bot]]

:wave: Thank you for opening your first issue. I'm just an automated bot that's here to help you get the information you need quicker, so please ignore this message if it doesn't apply to your issue.
If you're looking for support, you should try the Slack group by registering your email address at https://cachethq-slack.herokuapp.com. Alternatively, email [email protected] for our Professional support service (please note, this a paid service.
If you're issue is with documentation, you can suggest edits by clicking the Suggest Edits link on any page, or open an issue at https://github.com/CachetHQ/Docs

[RyoshiKayo]

@krollebol I had the same issue; I was able to remedy this by running composer require alt-three/testbench

Perhaps this is missing from composer.json?

Update: I am able to view the components in /dashboard/components/<number>, but assigning a tag or group to the component causes an error. The changes are save, minus the Tag and Group fields, which go back to being empty.

[JordyvanDortmont]

This is because you installed with the no-dev flag. Unfortunately a development package is now required for deployment of production and this is rather confusing, because the documentation also indicates that you should use the no-dev flag.

[support[bot]]

We use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with the project. You can signup to our Slack channel at https://cachethq-slack.herokuapp.com/

[jbrooksuk]

Looks like this is now resolved, thanks @JordyvanDortmont.

[ilogus]

Hello I have the same problem but I did not understand how to correct it can you help me please?

[jbrooksuk]

You need to run composer install -o --no-dev

[ilogus]

After this command, I had 2 errors 500. May be I need to reinstall composer?

[jbrooksuk]

Composer won't be the issue. What's in the log file?

[ilogus]

laravel-2018-04-28.log

I want to send the log file on pastebin but I get time out.
Now I have only 1, 500 error : b732b542-78f7-43b7-a10b-b68c44077296