irs-cybersec / ctf_platform Goto Github PK

Step 4/10 : RUN npm ci --only=production
---> Running in c0a2aff4b53e
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
之后一直卡住不动

This line:

does absolutely nothing. You need to insert

ENV NODE_ENV production

to make it work.

I have no idea why your code works in spite of this

Application has a feature which teams can use to send invite link to other team member by clicking on "Copy Invite link" button. However, this feature is not working as expected.

Step to Reproduce:

1. Click on "copy invite link" button and check that link is not getting copied.
   

配置邮箱信息后应该在哪里保存，点击测试连接 会显示与服务器连接错误

If I want to change some pictures, do you recommend me to change them through docker or bare metal?
Thanks ！！！

作者您好，我对得分页面上有新的想法：

在同一页通过不同的category展示不同的category user 排行

目前只能选择单一category，展示单一排行，希望能增添至两个排行榜（数据展示自由度更高）。

Thx！！

steps to reproduce:

0. login to account with permissions >= 2
1. create a challenge with a required challenge
2. try to remove that requirement

bug source

In step 2, the frontend will fetch /v1/challenge/edit over here:

https://github.com/IRS-Cybersec/ctf_platform/blob/master/client/src/AdminPanel/adminChallengeEdit.js#L93-L111

When the value of an attribute is undefined, JSON.stringify will remove the attribute altogether.

https://github.com/IRS-Cybersec/ctf_platform/blob/master/api/api.js#L1022-L1025

The backend calls updateOne() with $set; because updateObj contains no requires attribute, the challenge requirement remains in the db

CTF platform has feature where challenges can be enabled after solving certain challenges. Users have to solve the required challenge to unlock next challenge however, it is not showing which challenge to solve.

Hey there.
I really love this platform and is something i really need!. I'm willing to pay as well if I have this version as is now and permanently. Any e-mail for contact? Thanks

Issue

This application fails to function when being deployed for the first time (ie MongoDB is empty)

The error is as follows

(node:15516) UnhandledPromiseRejectionWarning: MongoError: ns does not exist: ctf.challs
    at MessageStream.messageHandler (ctf_platform\api\node_modules\mongodb\lib\cmap\connection.js:272:20)
    at MessageStream.emit (events.js:375:28)
    at processIncomingData (ctf_platform\api\node_modules\mongodb\lib\cmap\message_stream.js:144:12)
    at MessageStream._write (ctf_platform\api\node_modules\mongodb\lib\cmap\message_stream.js:42:5)
    at writeOrBuffer (internal/streams/writable.js:358:12)
    at MessageStream.Writable.write (internal/streams/writable.js:303:10)
    at Socket.ondata (internal/streams/readable.js:726:22)
    at Socket.emit (events.js:375:28)
    at addChunk (internal/streams/readable.js:290:12)
    at readableAddChunk (internal/streams/readable.js:265:9)

The issue seems to be introduced in 3ebb595

The file startupChecks.js attempts to add the validator option to three collections on line 10-12.

Although the collections were created in mongDB.js, MongoDB only attempts to create the collection when a document is inserted.
As such, the collection is not created, and when startupChecks.js attempts to apply the validator option, the referenced collection does not exist and the application fails.

Solution

Apply the validator when creating the collection (aka in mongoDB.js rather than in the startupChecks.js)?

I'll open a PR if you think this is a valid solution

failed to solve: executor failed running [/bin/sh -c npm ci --only=production]: exit code: 1