Fixes #3717

[felipeandradebezerra]

This fixes PR #3717. Sending push with [email protected] returns error
504 GATEWAY_TIMEOUT. This happens when push_time is not set (default).

[flovilmart]

Can you address the lint issues?

[flovilmart]

We should also probably add a test for that just in case it ends up in production :)

[felipeandradebezerra]

Kkkkkk... Lint?! How can I check that?

[flovilmart]

Running npm test will run the lint first :)

[felipeandradebezerra]

I'm getting used to work with parse-server :-)

[felipeandradebezerra]

HI @flovilmart Did I miss anything? :-)

[codecov]

Codecov Report

Merging #3824 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3824      +/-   ##
==========================================
+ Coverage   90.16%   90.17%   +0.01%     
==========================================
  Files         114      114              
  Lines        7532     7534       +2     
==========================================
+ Hits         6791     6794       +3     
+ Misses        741      740       -1

Impacted Files	Coverage Δ
src/Controllers/PushController.js	95.52% <100%> (+0.13%)	⬆️
src/RestWrite.js	93.26% <0%> (+0.19%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17a2d26...11e2a9f. Read the comment docs.

[flovilmart]

Looking good, it is working well for you?

[felipeandradebezerra]

@flovilmart I think it is, will double check. Anyway, I sent you an email early this week with some questions concerning running and testing parse-server.

[flovilmart]

Yes! I've been pretty busy this week, I'll get back to you soon :) I'll double check also alongside the fix you provided in Parse-server

[felipeandradebezerra]

Everything is working in this PR.

[felipeandradebezerra]

I think we also need to improve parse-server's CONTRIBUTING.MD with a handy guide for debugging our own stuff, so that we can work on it and test it iteratively without having to continually rebuild (see Parse-Dashboard example).

I've used the following steps to work on Parse-Server.

Step 1 — Install Parse Server app example

Retrieve the repository with git:
$ git clone https://github.com/ParsePlatform/parse-server-example.git

Step 2 - Declare your local dependencies in package.json
https://github.com/parse-community/parse-server-example/blob/master/package.json#L15
change to
"parse-server": "file:/Users/Colubris/Learning/parse-server",

Step 3 - Install and Run
Use npm to install dependencies, including your parse-server, in the parse-server-example directory:
$ npm install

Use npm to start the service. In this case, it runs node index.js:
$ npm start

Please, let me know if I'm following the right path. Thanks!

[flovilmart]

You should just have cloned Parse-server and run npm start :)

[felipeandradebezerra]

Hahaha... I think I'm getting older :-/

parse-server path/to/config.json