Conversation
Vighnesh-V
approved these changes
Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A strange bug got reported on Discord (and unfortunately they never made a ticket here) where durations that the user got from
@lute/fswould ultimately behave incorrectly when@lute/timewas not imported into that script. The underlying cause is that the metatable was not initialized when@lute/timewas not imported, and therefore the code that constructs the durations in@lute/fswould look for a duration metatable that did not exist and just set the metatable tonil. We fix this by making initialization of the duration library idempotent and then invoking that initialization for@lute/fsas well.