I have the same problem.Does anyone solve it?
Its likely same problem. Verify integrity isn’t guaranteed to work. Uninstall and reinstall will only work with files that have been removed/overwritten by that process.
That means something that is left over is still corrupted assuming that’s what it is for you. There is potential for other acute things. Also potential for it to be the game/engine code but that is far more unlikely as more people would likely see the problem.
The config files and savegame files will likely need to be moved and try again. I don’t think Windows registry needs any entries removed (though that’s what I would do to have a complete fresh start) but if you don’t know what you’re doing in the registry you could mess up things.
I have the same problem.Does anyone solve it?
This usually pops up on Mac hardware. If you’re *not* on a Mac, contact support@cyan.com and attach a copy of your system’s dxdiag report to the email telling us about the issue.
If you are on a Mac, please try these steps to resolve the crash/serialization error issue:
1. Open Finder, press “command+shift+g”
2. Type in:
/Library/application support/, press enter
3. Open “Epic/Obduction/Saved”
4. Delete “ByteCodeCache.ushadercode” & “DrawCache.ushadercache”
5. Restart your computer
If you the path in the steps above does not show you any of the folders or files, follow these steps instead to clear out the corrupt shader cache:
1. Open Finder, press “command+shift+g”
2. Type in:
Видео моего канала про видео манго брата-Микром.
Рыбалка в Чернобыле ПОРАЗИЛА НАС Мутант УТАЩИЛ .
1.08 target comes, EURUSD Weekly Trend Analyse-.
Смотреть видео. Приколы с животными. Смотри.-Сб.
Korina Kova Pornster Big Boods Video-Dowdy Hot .
Сборник Русские плясовые-Ярослав Мудрый
Арбалетные прицелы для пострелушек-Вячеслав KORIKK
БЫЛО/СТАЛО — ШАПОЧКА И ВАРЕЖКИ С КРАСИВОЙ ВЫШИВ.
Comments
Copy link Quote reply
alexjose commented Aug 25, 2018
I am getting Serialization of ‘Closure’ is not allowed error when trying to queue the action.
Also, how is the memory managed if action is performed on a huge collection of models? Say for example my Select All Matching is around 20K records.
This comment has been minimized.
Copy link Quote reply
patrickbrouwers commented Aug 26, 2018
Doesn’t you stack trace show you what the Closure is that it’s trying to serialize?
About your memory question: the action uses model chunks behind the scenes with a chunk size of 200.
This comment has been minimized.
Copy link Quote reply
calvinmuller commented Sep 4, 2018 •
Getting the same thing
This comment has been minimized.
Copy link Quote reply
jianminLee commented Sep 18, 2018
I have encountered the same error, the registration "Action" can not use “canSee” ，“canSeeWhen” “canRun” authorization, otherwise it will throw the same error
This comment has been minimized.
Copy link Quote reply
rickmacgillis commented Sep 21, 2018
@jianminLee Nice catch. I was wondering why that happened. To take it a step further, the reason it can’t serialize it is because it attaches that closure to the seeCallback and/or runCallback when using those methods.
Team Nova: I suggest allowing those to use the popular Class@method notation as the callback.
This comment has been minimized.
Copy link Quote reply
klepak commented Oct 15, 2018
I also had this issue when using canSee method on my action registrations. Got around it by performing the checks before adding my actions to the return:
This comment has been minimized.
Copy link Quote reply
pix2D commented Nov 26, 2018
So what is the solution when one has to use canRun because of #676 #558?
This comment has been minimized.
Copy link Quote reply
dillingham commented Dec 2, 2018
commenting out the canSee for an action stopped the error. redis / horizon
This comment has been minimized.
Copy link Quote reply
bolechen commented Feb 25, 2019
Issue still present in v1.3.2
This comment has been minimized.
Copy link Quote reply
dkulyk commented Feb 25, 2019
You need to override authorizedToRun method in the action for queued actions instead using can* methods.
This comment has been minimized.
Copy link Quote reply
chuangbo commented Mar 27, 2019
@dkulyk authorizedToRun works for queued action, but it seems to conflict with #114 "Run actions without update authorization". If we add authorizedToRun , nova would still require a model update permission for the action.
This comment has been minimized.
Copy link Quote reply
dav >Apr 5, 2019
Sorry, but we are unable to debug your issue without a reproducible code example. Once you provide that we can open this up again.
This comment has been minimized.
Copy link Quote reply
chescos commented May 18, 2019
Why has this issue been closed? The issue still persists and it’s clearly a bug
This comment has been minimized.
Copy link Quote reply
aaronahearne commented May 29, 2019 •
This seems to be related to the constructor rather than the canSee function specifically. Without looking into the source code, I would take a guess that one of the traits required for queuing actions (probably SerializesModel) is attempting to serialize the entire action (as would be normal for a Laravel job). But maybe the Action class that we are extending contains a closure somewhere. So when the system attempts to serialize the model to enter it into the queue, it fails.
Moving everything into the handle function and removing the constructor solved this for me. but Im not entirely sure why as it would usually be possible to include a constructor within your job definition.
I guess it could be something to do with the way the action needs to be instantiated within a resource when it injects dependencies like: