Trunk nightly

[another_commander]

It should be already fixed in cim's server. But keep a note for the future, no punctuation in the file size please

[Cody]

Got one of these just now:

Code: Select all

[script.javaScript.exception.unexpectedType]: ***** JavaScript exception (Oolite Defense Ship AI 1.79): TypeError: leader is null

[cim]

Thanks - should be fixed in tonight's build. (I'm guessing: destruction of a station?)

[Cody]

I'm guessing: destruction of a station?*

Not that I was aware of. I was running a cross-chart bunch of parcels, alternating between rock hermits and main stations.

*Can that happen in the core game?

[cim]

Can that happen in the core game?

To rock hermits, sometimes. A ship fleeing on injectors not looking where it's going will easily do enough damage to shatter one.

[Cody]

To rock hermits, sometimes.

<nods> Ah yes - I don't usually think of rock hermits as stations.

[Cody]

Got three sets of these just now:

Code: Select all

21:36:20.850 [gnustep]: 2014-03-07 21:36:20.850 oolite[1256] File NSData.m: 1564. In -[NSData writeToFile:options:error:] Rename ('D:\Oolite-Trunk/oolite.app/GNUstep/Defaults/.GNUstepDefaultsa00832' to 'D:\Oolite-Trunk/oolite.app/GNUstep/Defaults/.GNUstepDefaults') failed - Access is denied.



21:36:20.850 [gnustep]: 2014-03-07 21:36:20.850 oolite[1256] Failed to write defaults database to file: D:\Oolite-Trunk/oolite.app/GNUstep/Defaults/.GNUstepDefaults

One time only - no errors on subsequent launches.
I had been re-setting the joystick axes config thingy - related or not, I know not.

[another_commander]

Does this happen every time you try fiddling with joystick axes or was it a one-off? Can you try again what you were doing with the joystick config and let us know whether this is repeatable or not?

[Cody]

No, as stated, it was a one-off - not seen it before nor since (and I have just tinkered with the joystick thingy again to check).

[Cody]

Ah... I've been able to reproduce the errors, using the trunk/atmos install and tinkering with the deadzone and spline functions for the first time.
Subsequent tinkering is fine - no errors, so only on the first occasion, it seems.

[another_commander]

So, if you just delete the joystick settings from .GNUstepDefaults and try to set up the joystick profiles again, it should be reproducible, right? If so, please let me know, I may have a fix.

[Cody]

With my normal nightly build, deleting the .GNUstepDefaults joystick settings, then tinkering, does not seem to reproduce the errors.
However, with the trunk/atmos build it does reproduce the errors. <scratches head> I need coffee!

[another_commander]

I wonder if this is also reproducible on Linux. It would be great if one of our joystick using Linux guys could try to reproduce this by deleting the joystick settings from .GNUstepDefaults and trying to set them up again.

[kanthoney]

I wonder if this is also reproducible on Linux.

Nothing on mine, either on my not-quite-trunk branch or on the shady atmospheres branch. I've tried deleteing the joystick profiles bit, deleting all the joystick bit including the buttons, and deleting the whole file.

[another_commander]

This may be related to the Windows Search indexer service. I've just found an article in Stack Overflow which seems to be describing the exact situation we are seeing. GNUstep uses MoveFileExW when updating the defaults database so I am leaning towards believing that this might be the culprit. If this is the case, it may also mean that we may not be able do much about it. Thankfully, noticing it just now means that it may be rare enough for us to be able to live with it.