How is Pii Email 37f47c404649338129d6 Error Fixed?

As of the date of this post, the bug is still unpatched. I’ve opened up a ticket at Pii-Dev-Inc and told them to ignore the 57716b93c.

If you really want to help out, please reply with any other code that uses the same Pii.Key servers.

Discussion/publication: #1313 on the #ppp mailing list

[00:21]

We have implemented both Pii.Casts.generated.s1 and Pii.Casts.generated.s2.

If anyone has the full source from their server, I’d be happy to see if they could recreate the issue.

[00:32]

If you open an original file with an updated version of the same file, the same exception will still pop up.

[00:36]

note that I’m using one key (s1) only. There’s a total of 5 of them, so if we find another bug we’ll get more in-depth results.

Thanks, everyone for your help, see you next time!

[00:48]

Hey folks, I’m currently going through every single Pii.Packs that I have in my AWS inventory (which is quite a few) to identify any updated packages.

I’ve started with those that contain Pii.Key servers, and there is one that has an updated version of Pii.Casts.

Has anyone who has updated their Pii.Packs noticed this?

[01:09]

Update: A lot of folks have replied with the same issue. It’s still the original version of Pii.Casts.generated.s1.

[01:09]

I’ve sent an email to Pii-Dev-Inc, the core developers, and the community manager with the same issues. Here’s the email I sent:

“ Hi [name redacted], It looks like the same issue still exists.

Pii.Packs version 7.4.1 seems to be to the exact same, however, the issue is with the library Pii.

Casts, it seems to me that they have released a fixed version, however, my server is still only using the old version.

I opened up a ticket with them and let them know that my server would not close the original file properly, and still just gets a crash exception on opening.

My server is the only server I own that has the old versions, so if you have this issue, please open an issue with the original developer and I’d love to see if we can close the hole. Thanks for your help in advance, [Name redacted]

P.S. I’m not against the idea of giving it another shot for my clients as I feel it’s still a good product, but it’s just another setback for the whole family.

P.P.S. If anyone knows a better way to search through this huge library (742 Pii.Packs), please let me know.

[01:50] Here are the emails with the requests for comment (in no particular order): [00:53] Hello [name redacted],

The issue that we have been experiencing is that the code to close the files does not automatically close the files when the user closes the application, and when this happens the client fails to close the files and Pii.

Packs still read it as an error.

We have added a fix for this issue in this last release.

[00:53]

I have followed up with Pii.Dev-Inc and here is a reply they had this morning:

Hello, Thank you for your inquiry.

As stated above, we are aware that the user does not close the files.

We are currently working on an improvement and are looking to have this backported for your infrastructure within the next 2 days.

Thank you for your patience and understanding in this matter.

Best regards,

[name redacted]

Hi [name redacted], Thank you for bringing this to our attention.

We would like to take this opportunity to remind everyone that only the first (

About the author

Pushkar Kathayat

Pushkar Kathayat is the Chief Editor of TechGeekers. His passion is towards SEO, Online Marketing and blogging.