pipedream
                                
                                 pipedream copied to clipboard
                                
                                    pipedream copied to clipboard
                            
                            
                            
                        [BUG] Github - Create a Pull Request async options fails to load
Describe the bug
Any Github source using async options to populate props is infinitely loading when attempting to search:
https://share.descript.com/view/NGTVLNu161n
Reproduction steps
- Create a new workflow
- Create a Github New Pull Request (Instant) trigger
- Connect your Github account
- Attempt to search in the Repository prop
- See infinite load
Expected behavior I expect async options to work properly.
Additional context
- 
This issue seems to be happening with Bitbucket as well, not sure if it's an underlying system or devops problem. 
- 
The code for this New Pull Request (Instant) source is missing from the githubcomponent in the registry it seems.
@ctrlaltdylan It's working correctly for me. Is this happening just with one user, or are there more reports about it?
@vellames-turing a teams customer and myself have experienced the bug. The initial loading of options works, but searching seems to be broken.
@vellames-turing a teams customer and myself have experienced the bug. The initial loading of options works, but searching seems to be broken.
Oh, got it! I was able to reproduce it now, tks!
@vellames-turing great! Thanks for taking a deeper look.
Another customer may have found a similar bug on the instant commit source as well:
https://pipedream.com/community/t/github-organization-repos-not-showing-up/2889/2
Maybe it's the same bug?
Hello there @vellames-turing, as this is pending in Doing for a while, do you have bandwidth to work on this now? Also, could you take a look at the issue Pierce mentioned?
Hey, yeah, I will jump on it today
Need some clarification to move ahead. I am not able find the code related to this source. I just pinged @dylburger asking some help :)
I'll bring this up with the team during our triage process and we'll investigate. Feel free to move on to the next task @vellames-turing .
Closing this issue as I'm not able to replicate, looks like this one was fixed!