Calling config.set asynchronously not working
See original GitHub issueI’m trying to call config.set
asynchronously in my configuration function. Doing this because we use a tool that finds an available port asynchronously, so we don’t have all the configuration at the time the call to our configuration function is made. It appears as though the function never gets called.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:4
- Comments:18 (2 by maintainers)
Top Results From Across the Web
Spring @Async Not Working - Stack Overflow
I've got <task: annotation-driven /> in my config, and the call to the method is coming from outside of the class so the...
Read more >Asynchronous calls in Spring Boot using @Async annotation
In spring boot, we can achieve asynchronous behaviour using @Async annotation. But just @Async annotation will not work.
Read more >Working with Async | Home Assistant Developer Docs
If you need to call an async function that is a coroutine, your task must also be a coroutine.
Read more >[Solved] IIS Configuration settings and async Silverlight calls
I am working on an application that uses Silverlight. The issue is based around the update process. The update uses delegates (via InvokeAsync) ......
Read more >Async/Await - Best Practices in Asynchronous Programming
In particular, it's usually a bad idea to block on async code by calling Task.Wait or Task.Result. This is an especially common problem...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
i am having same problem, but not for port checking but rather parsing some environment configs with shell-source which only works async. so our webpack config is actually a promise but karma does not accept that.
Would it? It seems like currently, JS Karma config files export plain objects. They could be backward-compatibly distinguished from thenables (terminology from here) by the presence of a
then
function-valued property. Supposing it’s safe to say that no function-valuedthen
properties might currently be used for anything…