-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The notify() function in a WSL environment #102
Comments
Hey, WSL user too, can you provide some information about version of Windows and WSL ? See a little discussion here about WSL 2 notification : jolicode/castor#334 I had the same problem before, but now it works, but I'm on WSL pre-release (W11). |
Strange, you have an older version of WSL, I think. Can you attempt to run Which distribution do you use? |
I'm using Windows 11. It's a professionnal computer delivered by my company in which I have limited rights. But yeah, you have probably right : my system seems to not be up to date. I have just few seconds ago activated the necessary additionnal options in Windows Update (as described on the provided screenshot) and I'm waiting for the update to complete. This will probably resolve the issue. I was sure that WSL was already managed by Windows Update, but this is not the case and probably the reason behind this notification command not working. When done, i'll reply to this thread in order to close it or give your more details about the issue. |
Well, wsl 2 is now fully updated, but the notification just doesn't appear when the function is launched. Because I'm on a locked system (limited Windows privileges), I don't know if I should close the ticket or if you would like to investigate further. Maybe the issue is not related to these system limitations and a real issue could really exists in the base code, but maybe not. [EDIT] When doing a wsl --version (which works now), I have this output : As you can see, WSL is up to date. But I have just noted a weird information : the Windows version. I'm on Windows 11 for 2 years on this PC, and I wonder why it says it's in v10.0.22631.3374 |
Ok good to known, you have been updated to latest and higher Windows version 😄 But the strange thing is that on my professional PC I have no problem running Except that on my personal PC it doesn't work, and all versions are up-to-date except Windows. I got an error about the missing sonartoast. But it appeared once and then disappeared. Now, castor plays the script without errors, but no notification is displayed 😞 What is your use case compared to mine? Error throwed with linux phar/binary (only one time): When using Windows phar/binary: EDIT: Okay, I've figured out my error, I've used the repo's castor.php with the deps installed, that makes it resolve snoretoast and show me the notifications properly. I'll try to find a fix for this case. Because even the windows phar doesn't seem to fix the problem on my side. @lyrixx, @pyrech Did you have any confirmation that the use of Windows phar fix notifications internally at your company ? |
For the record, I have moved the issue from castor to jolinotif. |
I have exactly the same behavior. |
Since JoliNotif 2.7 was released with a better support of WSL, I'm going to close the issue as completed. JoliNotif has also been updated inside Castor, so notification support should be quite better in the next release of Castor. Thanks everyone |
Hello,
I'm in a WSL2 environment under Windows 11 in order to launch my Castor commands and with the Castor.PHAR archive for Windows (since it's this one to take even for WSL). I just tried your notification function but it doesn't trigger any notification.
I have checked my notifications options btw, and everything is properly configured. I wonder the reason behind this : is this a WSL related issue which can't communicate properly with Windows ?
The text was updated successfully, but these errors were encountered: