Eldair started a new conversation How To Stop/return From Queued Slack Route Notification
This is how I dispatch notification
Notification::route('slack', $slackHook)->notify(new SomeNotification($companyId));
Since the notification is going through the queue it can happen for the company whose ID was sent to be deleted in the meantime. I couldn't find how to stop
toSlack method in those cases since it requires
SlackMessage as the return type and throwing an exception is just going to retry job.
Hello, @pdcmoreira I can include your steps into accepted post or set it as accepted, even though I haven't tried it, it is easier solution (: Is virtualbox 5.0.1 now working correctly? I don't wish to update/loose my currently working setup if it's not completely ready :/
@bogdanus try to reinstall virtualbox, because it should have created one during installation. If not, try installing as admin. @vnobre the :8000 can be avoided if you change default port forwarding 80 => 80 instead of 80 => 8000 in homestead.rb or go to settings of your box -> network settings -> adapter 1 (nat) and port forwarding option, and there you will see port 80 forwarded to port 8000, change it to 80 and that's it.
Hi @vnobre, to me it seems like you haven't commented out lines in action.rb and homestead.rb. You should do that and manually set networks for existing box after which homestead up should work (with mapping from homestead.yaml file).
And it's working (: Cheers
In order to stop it from clearing existing network config you should comment line 64
in file action.rb located in ~\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.3\plugins\providers\virtualbox\action.rb
Hope this helps. P.S. even with this I couldn't setup Homestead on windows 10 with virtualbox 5 due to some error with mounting shared folders.. Still looking for some solution.
Hi, I managed to use Vagrant for VB5 and to install it as suggested. When I start the box from Virtualbox gui it runs until "waiting for network.." message and stops there (via Vagrant - same error as above).
I am having issues running homestead via virtualbox on Windows 10 TP 10130 with error code
Progress state: E_FAIL VBoxManage.exe: error: Failed to create the host-only adapter VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available) VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp
I am aware it is a common issue but was curious if someone has found a workaround?