Skip to content

Conversation

@derekvanvliet
Copy link

I added a function that demonstrates issue #456. I'm finding that if I don't specify a rejected callback for the Parse.Config.get() promise's Then method, it never reaches my When method and the function times out. I found this worked in hosted parse but not in the open source version.

I added a function that demonstrates issue parse-community#456. I'm finding that if I don't specify a rejected callback for the Parse.Config.get() promise's Then method, it never reaches my When method and the function times out. I found this worked in hosted parse but not in the open source version.

parse-community#456
result.config = {};

promises.push(Parse.Config.get().then(function(config) {
result.config = config.attributes;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you add return Parse.Promise.as() there, does it changes any thing?

Can you add a Unit test as well so the failure is properly handled and we ensure no regression in the future?

@drew-gross
Copy link
Contributor

This test doesn't seem to fail in travis, it was a different test that failed. Close/open to trigger tests.

@drew-gross drew-gross closed this Feb 19, 2016
@drew-gross drew-gross reopened this Feb 19, 2016
@facebook-github-bot
Copy link

@derekvanvliet updated the pull request.

@flovilmart
Copy link
Contributor

@drew-gross in that PR the function is actually never run...

@drew-gross
Copy link
Contributor

Oops yeah missed that. @derekvanvliet can you add a test case that runs this cloud code?

@facebook-github-bot
Copy link

@derekvanvliet updated the pull request.

@drew-gross
Copy link
Contributor

Looks like there are merge conflicts, I guess you will have to resolve those before travis can run the tests.

# Conflicts:
#	spec/ParseAPI.spec.js
@facebook-github-bot
Copy link

@derekvanvliet updated the pull request.

@drew-gross
Copy link
Contributor

Thanks! This will be very helpful as we attempt to fix the issue.

@flovilmart
Copy link
Contributor

looks like the issue is more around Parse.Config.get() than the promises themselves.

@drew-gross
Copy link
Contributor

Yeah that is true. @derekvanvliet Parse Config in Parse Server is currently in experimental stage, you can enable it with PARSE_EXPERIMENTAL_CONFIG_ENABLED=1 environment variable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants