You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2019. It is now read-only.
When using the Flickr.authenticate method, everything behaves as expected (authentication, making API calls) but the Node process won't exit by itself.
Here's a sample application that reproduces the behaviour:
varhabitat=require('habitat')varenv=habitat.load(__dirname+'/../.env');// based on the sample .env filevarFlickr=require('flickrapi')Flickr.authenticate(env.get('flickr'),function(err,flickr){if(err)throwerr;flickr.photos.search({user_id: flickr.options.user_id,page: 1,per_page: 20,extras: ['description','license','url_m'],authenticated: true},function(err,result){if(err)throwerr;result.photos.photo.forEach(function(photo){console.log(photo)})});});
The text was updated successfully, but these errors were encountered:
I'm using Flickr.tokenOnly(...) but I've also had the process not exit by itself. But I figured out that if I disable the progress bar in the options it exits correctly.
So maybe it's the progress bar that keeps the process running? I haven't tried Flickr.authenticate() though.
I can also confirm that this is related to setting the progress param in flickrOptions when calling tokenOnly. I was debugging stalled tests and was led to flickrapi, set progress: true (true accidentally), and the tests stopped hanging. I would like to propose setting the default option to false so as to minimize unexpected logging.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using the
Flickr.authenticate
method, everything behaves as expected (authentication, making API calls) but the Node process won't exit by itself.This seems similar to what @cheapsteak was experiencing in #71 here
Here's a sample application that reproduces the behaviour:
The text was updated successfully, but these errors were encountered: