You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if
resourceContainerizerMode = true
you get multiple cases issue of resource restart/(stop -> start) issues
there are present in CDN and none CDN mode
the example is for the JS resource but related to the source of the issue, it will happen in c# too but not tested.
if you stop and start or restart a changed JS resource you get this cases in this Scenarios
type jsb (bytecode resource)
if you restart a changed bytecode resource (like the example that contains only a log message that get changed)
the restarted bytecode is 1:1 the before resource no errors , simply the old code (still working)
you are not able in this case to use the new resource, you will be on the before resource.
type js resource
first start (connect)
[22:59:31] Loading resource test
[22:59:31][js] [V8] Starting script client/index.js
[22:59:31][js] Message to change
[22:59:31][js] [V8] Started script client/index.js
[22:59:31] Loaded resource test
then you change the message to "Message to1 change"
use "restart test" or "stop test, start test"
[22:59:51] Skipping integrity check for resource test
[22:59:51] Downloaded and validated resource test succesfully
[22:59:51] Finished downloading all resources
[22:59:51] Stopping resource test
[22:59:51] Stopped resource test
[22:59:51] Loading resource test
[22:59:51][js] [V8] Starting script client/index.js
[22:59:51][Error][js] [V8] Exception at test:client/index.js:3
[22:59:51][Error][js]
[22:59:51][Error][js] SyntaxError: Invalid or unexpected token
at <bootstrapper>:18:19
[22:59:51][Error][js] SyntaxError: Invalid or unexpected token
[22:59:51][Error][js] [V8] Unhandled promise rejection at test:[unknown] (Error: Failed to start file)
[22:59:51][Error][js] [V8] Exception at test:<bootstrapper>:18
[22:59:51][Error][js] if(!alt.isWorker) __internal_start_file(mainPath);
[22:59:51][Error][js] Error: Failed to start file
at <bootstrapper>:18:19
[22:59:51][Error][js] Error: Failed to start file
[22:59:51][Error] Failed to load resource test
if you change back the index.js (remove the added "1")
[23:00:35] Skipping integrity check for resource test
[23:00:35] Downloaded and validated resource test succesfully
[23:00:35] Finished downloading all resources
[23:00:35] Loading resource test
[23:00:35][js] [V8] Starting script client/index.js
[23:00:35][js] Message to change
[23:00:35][js] [V8] Started script client/index.js
[23:00:35] Loaded resource test
do bottom test like above
start this resource , change the message ba add something
restart or stop+start
with type jsb (exmaple) you get 0 errors but remain on the old resource
if you change client type to js
you get errors on not matching before resource on restart
Expected behaviour
refresh the resource and let them start with the new content
Additional context
No response
Operating system
Windows/Linux
Version
16.2.25-rc.5 + current release
Crashdump ID
No response
Confirmation of issue's presence
By submitting this ticket, I affirm that I have verified the presence of this issue on the latest RC (Release Candidate) version available at the time of writing this ticket.
The text was updated successfully, but these errors were encountered:
Description of the problem
if
resourceContainerizerMode = true
you get multiple cases issue of resource restart/(stop -> start) issues
there are present in CDN and none CDN mode
the example is for the JS resource but related to the source of the issue, it will happen in c# too but not tested.
if you stop and start or restart a changed JS resource you get this cases in this Scenarios
type jsb (bytecode resource)
if you restart a changed bytecode resource (like the example that contains only a log message that get changed)
the restarted bytecode is 1:1 the before resource no errors , simply the old code (still working)
you are not able in this case to use the new resource, you will be on the before resource.
type js resource
first start (connect)
then you change the message to "Message to1 change"
use "restart test" or "stop test, start test"
if you change back the index.js (remove the added "1")
it goes back to work
Reproduction steps
use the demo resource
test.zip
do bottom test like above
start this resource , change the message ba add something
restart or stop+start
with type jsb (exmaple) you get 0 errors but remain on the old resource
if you change client type to js
you get errors on not matching before resource on restart
Expected behaviour
refresh the resource and let them start with the new content
Additional context
No response
Operating system
Windows/Linux
Version
16.2.25-rc.5 + current release
Crashdump ID
No response
Confirmation of issue's presence
The text was updated successfully, but these errors were encountered: