Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:23
    scissorsneedfoodtoo commented #205
  • 08:27
    SomeDer opened #205
  • 07:08
    huyenltnguyen labeled #36654
  • 07:08
    huyenltnguyen opened #36654
  • 05:28
    RandellDawson commented #36609
  • 02:55
    huyenltnguyen commented #36644
  • 02:18
    thecodingaviator commented #36609
  • 02:09
    scissorsneedfoodtoo review_requested #36653
  • 02:09
    scissorsneedfoodtoo review_requested #36653
  • 02:09
    scissorsneedfoodtoo opened #36653
  • 01:39
    cmccormack commented #36267
  • 01:20
    scissorsneedfoodtoo commented #98
  • Aug 20 22:25
    ahmadabdolsaheb closed #36649
  • Aug 20 22:25
    ahmadabdolsaheb closed #36648
  • Aug 20 22:25
    ahmadabdolsaheb commented #36649
  • Aug 20 21:43
    P1xt closed #17589
  • Aug 20 21:43
    P1xt commented #17589
  • Aug 20 21:27
    99init commented #17589
  • Aug 20 21:24
    moT01 edited #36645
  • Aug 20 21:24
    moT01 labeled #36645
Pier Paolo Ippolito
@pierpaolo28
I have sent an email to get it published, does anyone know how long is it going to take more or less?
nik
@nikrb
hopefully this will answer your question: https://gitter.im/FreeCodeCamp/Contributors?at=5d4ae03b1dadc42a112b2c2d and https://gitter.im/FreeCodeCamp/Contributors?at=5d4b085f1db76d0ffe8f852e . I'm new so apologies if the links don't work :)
Ottomaddix
@Ottomaddix
Hi everyone
nik
@nikrb
hi otto. sorry forgot to tag @pierpaolo28 for the links above.
Pier Paolo Ippolito
@pierpaolo28
Hi @nikrb thank you for your help! I am looking forward to hearing from Quincy for updates!
Randell Dawson
@RandellDawson
@moT01 @ojeytonwilliams @thecodingaviator What do you think about https://github.com/freeCodeCamp/freeCodeCamp/issues/34617#issuecomment-494946407? I think we should suggest this as the fix for the reported issue and then request someone to create a PR for it.
Oliver Eyton-Williams
@ojeytonwilliams
@RandellDawson that comment nails it, in my opinion. I'll say something to that effect on the issue.
Randell Dawson
@RandellDawson
Maybe we should tag the user d-evans and see if there would be any interest in creating a PR with this suggestion.
xyozio
@xyozio
Hello everyone :) I would like to work on the radio. I would appreciate if someone can take a look on a few PR's and issues that I've opened.
Oliver Eyton-Williams
@ojeytonwilliams
I did tag d-evans, but it might be worth you confirming that that is what we want.
Randell Dawson
@RandellDawson
I wanted to test out starting from scratch with the latest version of master and after deleting my local and cloning my fork and rebasing appropriately and doing all the prep work (cp sample.env .env and npm run seed), when I run npm run develop, it errors out. Not sure why this is happening. Any ideas?
image.png
Christopher McCormack
@cmccormack
@RandellDawson looks like yesterday the start script changed from babel-node server/index.js to node production-start.js. However, my guess is your error is due to windows not supporting setting environment variables that way. Usually cross-env is used prior to setting the variables so it works on windows as well, but it seems the environment variable setting has been used without cross-env for at least a years so not sure why you are only seeing the error now.
Randell Dawson
@RandellDawson
@cmccormack Isn't the npm-run-all ensure-env -p develop:* where it fails? I validated the node-modules folder has npm-run-all installed. If I try to run npm-run-all ensure-env -p develop:* by itself, I get bash: npm-run-all: command not found
Randell Dawson
@RandellDawson
Would someone else using Windows attempt to clone the repo (without using Docker) and see if you get the same issue. If not, then I am at a loss of what to do next.
Christopher McCormack
@cmccormack
you usually can't run them directly like that @RandellDawson did you try something like ./node_modules/.bin/npm-run-all ensure-env -p develop:*?
or maybe npx npm-run-all ...
mrugesh
@raisedadead
That's on me. I may have inadvertently broken this for windows users.
We need cross-env in there. Can someone make a quick fix:
For the api-server's scripts
Randell Dawson
@RandellDawson
Working on it.
Thanks
mrugesh
@raisedadead

Usually cross-env is used prior to setting the variables so it works on windows as well, but it seems the environment variable setting has been used without cross-env for at least a years so not sure why you are only seeing the error now.

I do not think it was ever called in development mode

mrugesh
@raisedadead

@/all

Announcement:

Beta site is now live at https://www.freecodecamp.dev

Learn more about this in: freeCodeCamp/freeCodeCamp#34872
QA Checklist is available at: freeCodeCamp/freeCodeCamp#35475

Please note:

  • The above is not exhaustive and we need to find any broken parity in features and edge cases on the development instance.
  • Please go thru the known limitations on the issue thread before reporting issues.

Thanks a lot for all your patience and happy contributing. We can't wait for you to test this out before we ship it out.

Randell Dawson
@RandellDawson
When will the new chic look be added?
Ahmad Abdolsaheb
@ahmadabdolsaheb
@RandellDawson I will work on it until Monday and merge it then.
mrugesh
@raisedadead
We are doing a 1 week sprint of fixes and updates. Everything is up for grabs. Feel free to find bugs and raise PRs directly
I also think we all could meet up on a call for contributors sometime this Saturday?
Randell Dawson
@RandellDawson
I can meet this Saturday, but it would need to be in the late afternoon or evening for me (PST).
Ent Wickler
@entwicklerfr
Hello, I'm new here. It seems you are all very busy but I'm currently diving in the freeCodeCamp code and I'm interested in improving acceptance tests for a few challenges. I saw that the description of these tests has changed. There is no json file (like es6.json for example) anymore. Are these tests defined in the 'yml' part of the *.english.md (seems amazing to me) or I'm totally wrong ? Thx.
Randell Dawson
@RandellDawson
@entwicklerfr Yes, that is where the tests are for each challenge file.
Herman Fassett
@HermanFassett
@entwicklerfr hey I'm new to this codebase myself, looks like the magic is the tools/challenge-md-parser used in getChallenges.js
Anyone know why running local with mock local auth set true I get Unauthorized?
Ent Wickler
@entwicklerfr
Ok. Fine. Thx a lot @RandellDawson and @HermanFassett .
Herman Fassett
@HermanFassett

Anyone know why running local with mock local auth set true I get Unauthorized?

FYI I see someone else had this issue earlier when they hadn't run the seed correctly. I have the seed run but I'm using a mongodb atlas cluster and I'm also on a public network.
I've verified whitelisted IP and the seed worked, but I'll test later with local db and hopefully that fixes it.

Oliver Eyton-Williams
@ojeytonwilliams
@raisedadead I should have to meet tomorrow. When where you thinking?
nik
@nikrb
"To test as an existing user, we would require the permission of a user ..." am I misreading this or do you need our permission somewhere/somehow to test as existing user?
Tom
@moT01
Where does it say that @nikrb? Pretty sure it means that fCC needs permission from a user to copy their info from the production database to the dev database.
Otherwise you just have to make a new account for the dev site
Randell Dawson
@RandellDawson
@raisedadead Not sure why, but after #35278 was merged, new PRs are failing Travis with the following error:
> @freecodecamp/curriculum@0.0.0-next.4 lint /home/travis/build/freeCodeCamp/freeCodeCamp/curriculum
> gulp lint
> @freecodecamp/freecodecamp@0.0.1 prettier /home/travis/build/freeCodeCamp/freeCodeCamp
> prettier "**/*.css" "--check"
Checking formatting...
[05:23:51] Using gulpfile ~/build/freeCodeCamp/freeCodeCamp/curriculum/gulpfile.js
[05:23:51] Starting 'lint'...
[05:23:58] Finished 'lint' after 7.56 s
client/src/templates/Guide/components/calculators/CodingBootcampCostCalculator/CodingBootcampCostCalculator.css
Code style issues found in the above file(s). Forgot to run Prettier?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @freecodecamp/freecodecamp@0.0.1 prettier: `prettier "**/*.css" "--check"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @freecodecamp/freecodecamp@0.0.1 prettier script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
mrugesh
@raisedadead
Thanks @RandellDawson for letting me know. I am already subscribed to notifications from Travis. I saw it too. Will have it reverted. @QuincyLarson merged the PR but that's fine. We should be able to revert the changes
nik
@nikrb
@moT01 my bad, it's the old .rocks QA checklist #35475. I thought I got there from a link from the new dev post but I'm mistaken. Don't know how I ended up there now, so ignore me please :)
Parth Parth
@thecodingaviator
Could someone tell me what this file is doing?
mrugesh
@raisedadead
Its right there in the commit.
Making patch.
Oliver Eyton-Williams
@ojeytonwilliams
@thecodingaviator it was to deal with this error: https://github.com/freeCodeCamp/freeCodeCamp/pull/35733#issuecomment-478996142
As I understand it (which is to say, loosely) this patch stops npm from trying to delete dirs which are currently in use.