woshilapin / codingame-connector Goto Github PK

View Code? Open in Web Editor NEW

5.0 5.0 0.0 208 KB

JavaScript 96.70% Shell 3.30%

codingame-connector's People

Contributors

Stargazers

Watchers

codingame-connector's Issues

cg-watch doesn't understand all the incoming messages

codingame-connector has been developed based on one specific exercise of Codingame (Temperatures). This exercise is only comparing the output to the expected result. However, some game have a game-loop, like Mars Lander. In this case, the returned result is the list of frames. Actual version of codingame-connector doesn't work for Mars Lander (and all similar games).

Display the stdout and stderr informations

When launching a test, it's necessary to see the debugging information.

[v0.6.0] Cannot launch cg-watch

module.js:471
    throw err;
    ^

Error: Cannot find module './codingame/api.js'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/woshilapin/.dot/nvm/versions/node/v6.9.1/lib/node_modules/codingame-connector/lib/utils.js:27:12)
    at Module._compile (module.js:570:32)
    at Module._extensions..js (module.js:579:10)
    at Object.require.extensions.(anonymous function) [as .js] (/home/woshilapin/.dot/nvm/versions/node/v6.9.1/lib/node_modules/codingame-connector/no
de_modules/babel-register/lib/node.js:152:7)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)

Give the possibility to run a command to get the username and password

Would be nice to have the username and password configurable in 2 ways:

if string, just as it is
if array, treat the array of strings as a command and keep output as the result

For example, [ "echo", "${PASSWORD}"].

Have a plugin system that runs the bundlers

It would be nice that the bundle file is automatically generated. And it would be nice that cg-watch is triggering this bundler automatically.

The '--version' command line option doesn't work

This option works if you run it from the development environment with npm run start -- --version because the file package.json is present and because the relative path ./package.json is correct. However, it doesn't work from the npm global installation because the file package.json is not installed.

Add ESlint in the project

Doesn't work when built with Babel but run with 'babel-node'

Cannot describe it better than babel/babel#4783. Nasty bug!

Add JSDoc for documentation

Display name of tests in output

When displaying the result of tests, only number of the test is displayed but in Codingame, each test has also a name which would be nice to display.

An in-range update of nock is breaking the build 🚨

Version 9.0.9 of nock just got published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.0.8
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nock is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 4 commits .

5b1a8d8 9.0.9: Revert PR #802
51809e1 Merge pull request #840 from node-nock/revert-802-fix-754
0a083f6 Revert "Fix request timeout no working"
3728a1f Changelog v9.0.8

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Error when the bundle file is not found.

This is the error being thrown up.

(node:9010) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: watch bundle.py ENOENT

An in-range update of nock is breaking the build 🚨

Version 9.0.4 of nock just got published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.0.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nock is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits .

8f20a6d 9.0.4: Fix bug where only single set-cookie header would be returned
3bae02d Merge pull request #820 from node-nock/bug-818-multiple-set-cookie
189894e Merge pull request #813 from node-nock/greenkeeper-tap-10.0.0
20dceeb Bug #818 Assert mutiple set-cookie headers are included in object
6b54bdb Bug #818 Send back multiple headers if multiple present
c4c5e0f chore(package): update tap to version 10.0.0

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

Version 7.2.1 of babel-eslint just got published.

Branch	Build failing 🚨
Dependency	babel-eslint
Current Version	7.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits .

3cda62e 7.2.1
5626de1 Remove left over eslint 2 estraverse code (#452)
b5fb53b Fix type param and interface declaration scoping (#449)
f1cee0f Remove lodash dependency (#450)
eb05812 Format non-regression errors for legibility (#451)
7972a05 Update README.md with codeFrame option (#448)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Remove usage of fs.stat() [not recommended]

Using fs.stat() is reading the file so modifying it in some way. Anyway, in NodeJS documentation, usage of fs.stat() is not recommended to test for existence of a file.

semantic-release doesn't work

Configuration is probably incomplete, in Travis log, there is complains about Github token and npm token.

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

allowUncaught added to commandline as --allow-uncaught (and bugfixed)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

7554b31 Add Changelog for v3.4.0
9f7f7ed Add --trace-warnings flag
92561c8 Add --no-warnings flag
ceee976 lint test/integration/fixtures/simple-reporter.js
dcfc094 Revert "use semistandard directly"
93392dd no special case for macOS running Karma locally
4d1d91d --allow-uncaught cli option
fb1e083 fix allowUncaught in browser
4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

(node:5270) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: ENOENT: no such file or directory, open '.codingame.json'

Cannot load the configuration file

This is a serious bug that forbid the whole program to run, never finding the configuration file. Probably due to the new commander module to parse options.

Ability to login with other accounts that Codingame (Google, Facebook)

It's probably about implementing OAuth authentication.

woshilapin / codingame-connector Goto Github PK

codingame-connector's People

Contributors

Stargazers

Watchers

codingame-connector's Issues

Version 9.0.9 of nock just got published.

Version 9.0.4 of nock just got published.

Version 7.2.1 of babel-eslint just got published.

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

Recommend Projects

Recommend Topics

Recommend Org