https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
j

jeggy

01/14/2020, 6:27 PM
I'm trying to execute a coroutine in a specific Context, but if I have understood it correctly, when using the
withContext
function, it waits for that coroutine to finish before continuing. But I want to launch multiple coroutines into another context and then later on, I will call join on that coroutine when I know I'm finished. How would I achieve something like this? I wrote a bare minimum example of what I'm trying to achieve here: https://pl.kotl.in/Ns6Hwa_8u
o

octylFractal

01/14/2020, 6:30 PM
is
launch(coroutineContext)
not good enough?
c

Casey Brooks

01/14/2020, 6:37 PM
withContext
is usually used to change the Dispatcher, so the coroutines execute on a different thread. The lambda of that function is packed and tossed in a queue on the specified dispatcher, and the parent coroutine will continue executing in its original context. Since you’re using
runBlocking
as the parent context, the
join()
will wait for the
doLaunch
calls to complete. But since
runBlocking
is single-threaded, it cannot exit the parent context and process the new jobs added to the queue from the
withContext
call. It’s deadlocked.
So, the problem here is with using
runBlocking
, not
withContext
j

jeggy

01/14/2020, 6:43 PM
Alright that wasn't the best example. The problem I'm having is that I'm doing recursive coroutines and somehow some of them are not waited for. I will write a new example with bit more complicated code.
c

Casey Brooks

01/14/2020, 6:48 PM
Like a fork-join approach? You’d need to launch the sub-tasks on a different, async dispatcher. It is based on both the parent and child contexts you’re launching in. If you launch child-jobs from
Dispatchers.Main
onto
<http://Dispatchers.IO|Dispatchers.IO>
, you’ll be just fine, and you can safely join the child jobs to the parent in the
Main
context. But launching from
Main
onto
Main
will cause problems, again, because it is single-threaded, and the queue cannot complete the parent task to start executing the child-tasks
j

jeggy

01/14/2020, 7:06 PM
kotlinx.serialization isn't supported on the playground, but this is exactly what I'm trying to achieve: https://pl.kotl.in/7p7j_A47S
o

octylFractal

01/14/2020, 7:27 PM
why are you doing
withContext
before
async
? that doesn't really affect anything,
async
isn't a suspend function so
withContext
doesn't affect it
j

jeggy

01/14/2020, 7:40 PM
If I change it to only
async(this.coroutineContext)
instead of
withContext(this.coroutineContext){async(this.coroutineContext){block(..)}}
all data get's lost
o

octylFractal

01/14/2020, 7:48 PM
what do you expect this playground code to do with
loadAllAtOnce(it).await()
? you never complete any of the deferreds, so of course that suspends forever?
oh, nvm, in index = 2
this is a little confusing 🙂
c

Casey Brooks

01/14/2020, 7:51 PM
The logic here is a bit off. The
DeferredJsonMap
is a map of objects, but you’re initializing it with deferred objects. That means at any given node in that tree, it’s going to synchronously wait for all objects in that node to be ready before continuing to populate the rest. But you’re awaiting a result in the middle that won’t be completed until later. Or, if you run the jobs async, the tree will be fully constructed before they get executed, and so cannot be added to the tree when they finish. What you need to do is first construct a tree of purely deferred objects. Once all the entire deferred tree has been constructed, then go through the entire thing and join to wait for the results of all of them to be finished. I’ve updated your example to populate the tree with deferreds first, and then complete. I think this is doing what you’re wanting. I’ve also added some logging traces which help illustrate how it’s executing https://pl.kotl.in/-BRc6p9wD
o

octylFractal

01/14/2020, 7:52 PM
the core problem here is that
withContext
provides a
CoroutineScope
as
this
as well, so
withContext { async {} }
will suspend until the async block completes, rather than launching on the
DeferredJsonMap
scope
that's probably also why removing
withContext
changes things up
c

Casey Brooks

01/14/2020, 8:06 PM
My previous link wasn’t entirely correct. I’ve added more logging and updated the example. It’s now clear exactly when things are set up and when they are executed, and the result should be as you expect https://pl.kotl.in/ap0xJOw0y
❤️ 1
j

jeggy

01/14/2020, 10:19 PM
@Casey Brooks Thanks a lot! 🤩 I will try this out and report back 👍
If you could help me with one more thing that would be perfect! I need to work with arrays also. Thinking something like this:
"someArray" toDeferredValue listOf(25, 50, 100).asDeferredArray { num ->
    delay(100)
    "id" toValue JsonPrimitive(num)
}
c

Casey Brooks

01/15/2020, 1:40 AM
It’s mostly the same, but create a
DeferredJsonArray
class which holds its data in lists instead of maps, and set it up similar to the Map one. And then add a
toDeferredArray
method to the map class which will create the builder for it. Here’s an updated example (it could probably be cleaned up/abstracted a bit, but it looks like it works just fine) https://pl.kotl.in/FUE07Z7Lu
👍 1
j

jeggy

01/15/2020, 9:19 AM
Thanks for everything! We should make this code to a library 😉