Comments (15)
I released an official 1.5.2
from igc-xc-score.
Can you pls attach the IGC file, there is probably something in it
The code appears otherwise correct
from igc-xc-score.
Here it is,
I realized It is not exactly a flight. It is rather a blowback incident detected as a flight by my instrument. Maybe the lack of data...
from igc-xc-score.
I can't reproduce the crash? Does it always crash on this file, or is it only when it is used after the first three?
from igc-xc-score.
I ordered files differently and still crashing but on a different file (still the fourth). The complete flow is:
- connecting sqlite3 db containing files;
- querying db;
- for each record, process IGC data stored (including calling igc-xc-score as described before);
Might be a memory issue, the fact that terminal window becomes grey (originally black) could be a clue. I've never met such a behaviour...
from igc-xc-score.
Does a terminal reset fix the issue? Might be related to the ANSI control characters. Can you create a repro with all the files needed?
from igc-xc-score.
Nope, neither reset, neither restart. I noticed flight count may vary before crash occurs. Here is the requested repo, you should use the igc-xc-score-crash branch:
https://github.com/Djang0/IFly
Before running, you might want to adapt config.json to suit your needs. I attached a copy of sqlite db
fly.db.zip
please don't pay attention to the code, this is only a draft.
Here is a screen recording of the described behaviour:
https://youtu.be/cIJEkRY-rxA
Normal behaviour : the terminal shows db close console log.
from igc-xc-score.
I tried both with iTerm 2 and the built-in OSX terminal and cannot reproduce that behavior - the terminal turning grey.
However I get an exception in igc-analyzer.js
after the 3rd flight and once I short-circuited all the thermal analysis the whole program seemed to run normally.
I strongly suspect that this is some problem with the exception coming in the middle of some ANSI sequence for changing terminal colors. Can you try to redirect the output in a file with > stdout
to check if you see something in it?
from igc-xc-score.
I pushed a file called crash.out to my repo. It results from the following command:
node index.js > crash.out
from igc-xc-score.
It is indeed a case of garbled ANSI control sequence
You can see it with node index.js >& crash.out
The reason I was not reproducing it, is that I am using a git checkout. Can you try a git checkout and confirm me that it has been fixed on git? If so, I will release a 1.5.2
from igc-xc-score.
I'm not sure to fully understand your request. Do you want me checkout your latest github repo and replace the content of "node_modules" dir of igc-xc-score ?
Or simply recloning my own repo (I don't really get the ANSI aspect of the checkout operation)?
from igc-xc-score.
cd node_modules
rm -rf igc-xc-score
git clone [email protected]:mmomtchev/igc-xc-score.git
cd igc-xc-score
npm install
npm run build
from igc-xc-score.
Yes! I can confirm you nailed it.
however, I get this error at build time:
> [email protected] www /Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score
> webpack && cp www/index.html www/pacman.svg dist/www
date: illegal option -- I
usage: date [-jnRu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
[-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/cli.js:93
throw err;
^
Error: Command failed: date -I
date: illegal option -- I
usage: date [-jnRu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
[-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
at checkExecSyncError (child_process.js:616:11)
at Object.execSync (child_process.js:652:15)
at Object.<anonymous> (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/webpack.config.js:8:25)
at Module._compile (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:194:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
at WEBPACK_OPTIONS (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/utils/convert-argv.js:114:13)
at requireConfig (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/utils/convert-argv.js:116:6)
at /Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/utils/convert-argv.js:123:17
at Array.forEach (<anonymous>)
at module.exports (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/utils/convert-argv.js:121:15)
at /Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/cli.js:71:45
at Object.parse (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/yargs/yargs.js:576:18)
at /Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/cli.js:49:8
at Object.<anonymous> (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack-cli/bin/cli.js:366:3)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object.<anonymous> (/Users/lreenaers/Documents/code/IFly/node_modules/igc-xc-score/node_modules/webpack/bin/webpack.js:156:2)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12) {
status: 1,
signal: null,
output: [
null,
Buffer(0) [Uint8Array] [],
Buffer(171) [Uint8Array] [
100, 97, 116, 101, 58, 32, 105, 108, 108, 101, 103, 97,
108, 32, 111, 112, 116, 105, 111, 110, 32, 45, 45, 32,
73, 10, 117, 115, 97, 103, 101, 58, 32, 100, 97, 116,
101, 32, 91, 45, 106, 110, 82, 117, 93, 32, 91, 45,
100, 32, 100, 115, 116, 93, 32, 91, 45, 114, 32, 115,
101, 99, 111, 110, 100, 115, 93, 32, 91, 45, 116, 32,
119, 101, 115, 116, 93, 32, 91, 45, 118, 91, 43, 124,
45, 93, 118, 97, 108, 91, 121, 109, 119, 100, 72, 77,
83, 93, 93, 32,
... 71 more items
]
],
pid: 60619,
stdout: Buffer(0) [Uint8Array] [],
stderr: Buffer(171) [Uint8Array] [
100, 97, 116, 101, 58, 32, 105, 108, 108, 101, 103, 97,
108, 32, 111, 112, 116, 105, 111, 110, 32, 45, 45, 32,
73, 10, 117, 115, 97, 103, 101, 58, 32, 100, 97, 116,
101, 32, 91, 45, 106, 110, 82, 117, 93, 32, 91, 45,
100, 32, 100, 115, 116, 93, 32, 91, 45, 114, 32, 115,
101, 99, 111, 110, 100, 115, 93, 32, 91, 45, 116, 32,
119, 101, 115, 116, 93, 32, 91, 45, 118, 91, 43, 124,
45, 93, 118, 97, 108, 91, 121, 109, 119, 100, 72, 77,
83, 93, 93, 32,
... 71 more items
]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] www: `webpack && cp www/index.html www/pacman.svg dist/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] www script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/lreenaers/.npm/_logs/2021-01-14T11_06_44_318Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `rollup -c && npm run nexe_all && npm run www && npm run doc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/lreenaers/.npm/_logs/2021-01-14T11_06_44_357Z-debug.log
➜ igc-xc-score git:(master) ✗
from igc-xc-score.
No, this is only webpack which doesn't work on OS X
Ignore the webpack, it is for the demo website
Run your application with this version
from igc-xc-score.
Ok, thank you.
from igc-xc-score.
Related Issues (16)
- Question about IGC Parser HOT 2
- Box.distance() bug ?
- Possible speedup HOT 2
- Proper rounding procedure HOT 2
- Strip/tree shake debug code HOT 7
- Unhandled exception in 1.7.0 beta with some flights
- FAI-OAR flights report a wrong distance when used without cylinders
- Demo not working in Windows browsers HOT 2
- [Question] Perfomance HOT 3
- FAI Triangle not getting the further points HOT 1
- Scoring is undefined HOT 3
- Cannot read properties of undefined (reading 'heapUsed') HOT 2
- Cannot read property 'r' of undefined HOT 5
- Moving average / flight detection HOT 4
- How to use with FAI scoring rules HOT 79
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from igc-xc-score.