[Question/Bug] Missing script files in manifest prevent entire resource startup

[AdrianIsBored]

Summary

On legacy artifacts, missing script files that are referenced in manifest only appear to log a warning and continue loading anyways.

On enhanced artifact, a missing script prevents the resource from running entirely. This behavior is quite annoying in development as for example a single renamed file will cause your entire script to not work.

Is this intentional?

Issue type

Server

Repro rate

Always

Server build version

b90

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Reference a script that doesn't exist in manifest

Expected Behavior

The resource should start despite the missing script

Actual Behavior

The resource doesn't start at all

Evidence

Failed to start resource test. Error: The reference file "@test/nothing.lua" does not exists.

also.. minor typo on "exists", should be "exist"

Additional Context

No response

[wolfram-cfx]

Thanks, we are looking into this.

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!