Skip to content
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

Psych::DisallowedClass: Tried to load unspecified class: Time with Psych v4 #520

Closed
jeffblake opened this issue Feb 23, 2022 · 11 comments
Closed

Comments

@jeffblake
Copy link

On psych 4.0, the following error is raised:

Psych::DisallowedClass: Tried to load unspecified class: Time

After accessing a serialized schedule on an AR model, such as:

serialize :schedule, IceCube::Schedule

Works fine with Psych 3.3.2

@pacso
Copy link
Collaborator

pacso commented Feb 24, 2022

Hey @jeffblake, this sounds very much like an issue with Psych 4.0 rather than IceCube.

I'm not sure what you're expecting us to do with this? If you have a failing test for this gem, or a change you want to suggest, then please submit a PR.

@pacso pacso closed this as completed Feb 24, 2022
@jeffblake
Copy link
Author

@pacso
Copy link
Collaborator

pacso commented Feb 24, 2022

Hi again @jeffblake

I've created a new PR for the latest Ruby, and have replicated the issue you've mentioned. Thanks for pointing it out ... will get a fix sorted before the next release.

@pacso pacso reopened this Feb 24, 2022
@pacso
Copy link
Collaborator

pacso commented Mar 2, 2022

@jeffblake - could you possibly test with the branch from PR #521 please?

@jeffblake
Copy link
Author

@pacso My tests pass! Thanks.

@pacso
Copy link
Collaborator

pacso commented Mar 2, 2022

Great, thanks for checking! I'll merge it now :)

@pacso pacso closed this as completed Mar 2, 2022
@Aesthetikx
Copy link

Can we get a rubygems release for this? ❤️

@gustavompo
Copy link

+1 for a release

@jeffblake
Copy link
Author

Bump for release please.

@pacso
Copy link
Collaborator

pacso commented Sep 6, 2022

Hey everyone.

We have a problem in terms of cutting a release at the moment. One of the previous commits fixed a bug, but introduced another. By rolling it back we remove the new bug, but reintroduce the old one. Neither is a viable option really.

I've been struggling for time recently, but should be able to dedicate myself to fixing this soon. Once done we'll cut a new release and get both bugs sorted properly.

Sorry for the delay!

@adfoster-r7
Copy link

It would be great if there was a release available for this; is there anything I can do to help? 🤞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants