@manxam said in Sodium Storage NaN Bug:

The strange part is that mine has been fine all day. Previously I was seeing either a duplicate C: or "Not available" "NaN".

Today? just E: and C:

Awesome! That is actually not so strange as I did clear up some storage issues. Scott's issue is likely completely unrelated to yours. Yours was cleared up as I reconstructed how we were storing our data. As soon as I did that your issue was resolved (it was the driving force behind the change but it is a huge upgrade to our backend so it was needed). As for Scott's issue, this is an issue with what is being sent to us from the agent. The last line is actually the return code which I just need to filter out, that's nothing. However the D drive not showing it's information is intriguing. The agent obviously couldn't get a read on the drive. I'll be looking into this one later today.

@ccwtech said in Sodium Notes:

That sounds familiar! Would be a great feature.

Already have it approved by product management, will hopefully start on it this week (if I can get everything done for MangoCon quick enough to allow time for it!)

@scottalanmiller said in Sodium Application Enumeration Failure on Deepin Linux:

Running the latest Deepin Linux 15.4.1 for testing, Sodium installs fine with the apt-get installer and data collection works, but the applications get collected with a number rather than the name of the application. Screen shot here:

@QuixoticJeremy

Interesting, the agent must be returning in a slightly different format for deepin linux. I'll have to write a separate parser for that response. Thanks for the notice!

GParted

@jaredbusch Sure thing

@manxam said in Sodium App bug:

Oh, so that was you in that video..

Often, yes.

@manxam said in Sodium System Status:

@QuixoticJeremy, I installed the agent on a Windows 10 system a few days ago but Sodium does not show any information beneath "Applications" for it.

Also, it enumerated the DVD drive (E:) but shows "Not Available" for all of the data. Could you do a quick WMI check on drives to determine if they're ROM and, if empty (isReady = False), show "Empty" or something along those lines?

[IO.DriveInfo]::GetDrives() | where { $_.DriveType -eq 'CDRom' }

Name : E:
DriveType : CDRom
DriveFormat :
IsReady : False
AvailableFreeSpace :
TotalFreeSpace :
TotalSize :
RootDirectory : E:
VolumeLabel :

Hi @manxam! Thanks for posting/helping us test. Yep, you are 100% right, the applications not showing is indeed a known issue and I'm actually working on it as we speak. (It was reported on Friday but we've had some crisis situations that prevented me from getting to it until now). As for the storage side of things I'm making note of that and will check into that right after I fix the app bug. Thanks again!

And the evening of deployments begins.....

Hopefully we will see some new stuff tonight. Fingers crossed.

@DustinB3403 said in Applications Disappear:

@scottalanmiller Did you turn it off and on again? :P

Ironically that is exactly what he's going to do lmao. He'll turn it on again for data collection and then off again to verify that the hotfix did it's job. Which it will have :)

@dustinb3403 Which client is this? send me a message