poking around at this some more trying to reconstruct the specific events - i have been unable to reproduce a crash now (and the checkstack fixes in 2.1.13 may very well have fixed it, iirc you said it was less reproducible after that), but more specifically what occurred is this:
1. while in a ...

a quick look suggests this is the checkstack thing again, in another variation

fwiw, you can still (and always could) enter the sign bit/minint as its actual value, -0x80000000

there's a note somewhere that says it's excluding the ones that just depend on everything

edit: in the hover for "Default"

nevermind i didn't read close enough

i posted a fix for this, pending review fixed for next release

i believe this is distinct from those linked crashes, i will be looking into this deeper shortly; i think it should be a relatively easy fix, but i have to set up some quick tests first to verify i've understood the situation!

it looks like it requested the restart for the mod changes, but some curl task was not yet completed, and failed to cancel

please try this again with factorio 2.1.9 / fmtk 2.1.4 - if it still crashes, i'd also like the DAP trace log you get from adding "trace":true to the launch.json options while reproing

i've submitted a couple patches to help investigate this in more detail (or if we're lucky, maybe just fix it)

mods, if we could adjust the title to "Crash with LuaDebugAdapter when updating breakpoints"

Very strange. It looks like you caused a SetBreakpoints request, which then failed at a completely nonsensical spot as it was looking for the corresponding known source file to (re)validate those breakpoints. Can you tell me more about what you were doing before this happened?

i said this on discord yesterday, but just to have it on the record here in the thread: my conclusion is that require is working as intended and that this was a bug in the mod lua that had merely been hidden by previous quirks of loading that no longer apply, and that the fix is for the mod lua to ...

in 2.0 the package.loaded cache got reset to an earlier state between each top level data stage file, it appears this is no longer the case and it is now more like normal require caching behavior (the main deviation from upstream behavior now is the use of resolved name rather than requested name ...

in inventory sensor data-updates, you do:

require('lib.init')
Framework.post_data_updates_stage()


`lib.init` resolves correctly but is already cached from your earlier call in data, so it does nothing, and you discard the returned reference. You then call into the global var Framework, which ...

yeah i was waiting for it to be merged (which it now has been) to confirm that it's fixed for next release

the dict type option for LuaEntity::neighbours is listed as dictionary[string → array[LuaEntity]], but it appears all the dict-shaped results are actually dictionary[string → LuaEntity]

get_max_inventory_index() on a rocket silo returns 12, but get_inventory(12) seems to always be nil, and the largest defined index is 11:

fuel=1
rocket_silo_input=crafter_input=2
rocket_silo_output=crafter_output=3
rocket_silo_modules=crafter_modules=4
unnamed =5
burnt_result=6
crafter_trash=8 ...

get_inventory(5) on a rocket silo returns an inventory, but that inventory has an empty `name`, and there is no corresponding defines.inventory value. From discussion with Bilka, this seems to be `rocketInventoryIndex`, the inventory of the attached cargo pod.

Just to confirm, the other pr (#7998 re: LuaPlayer.blueprints) does not in fact fix this - but i don't understand this one enough to do anything more helpful

https://lua-api.factorio.com/latest/aux ... cture.html

would be nice to specify the preference when multiple packages of the same mod exist (zipped/unzipped) which one will be loaded

It is now. thank you. also it seems that i cant compile it? it says that trio.h is not found? is there a dependency im missing or something?


we use https://daniel.haxx.se/projects/trio/ for a printf that actually works correctly on every platform (which, amazingly, is not something you can ...