i came looking to debug a global pointer, found this unrelated subject, you helped me understand a very usefull go routines skill, very concise and not annoying precise to the point explanations. Thank you man 🙏🏼
Your style of teaching is the best I've ever seen, you can tell you know this stuff instead of regurgutating the documentation like every other channel. I'll buy your microservices course as soon as I can
Good explanation. Do you really need to duplicate the code for ctx cancel handling? Can't you have it in a separate function? Your function naming in the example is kind of bad.
@kantancoding thanks for nice visualisation my requirement is that main spawns multiple child (go routines) and if some thing goes wrong in any of the child then all child must abort right at the point what ever they are doing now and reported back to parent is errGroup coupled with context-with-cancel works in this scenario? if there exists any existing library it wud be really great, if not wanna make one to help dive deeper
Great video, but what happens when you DO want to cancel a parent context from a child. I have this exact scenario and in this case I pass in the parents cancel to the child gr. this works fine but this seems to be going against the grain. How do you cancel the parent without passing cancel func? What is wrong with this?
I can’t think of any valid scenario where you’d cancel the parent from a child goroutine. I’d say the fact that you want/need to do this points out a fundamental design flaw in your application. I can help more if you tell me WHY you feel it is necessary to cancel the parent from the child.
@@kantancoding great thanks. I knew it was wrong but I couldn’t figure out how to fix it properly. I have designed a worker pool. The worker pool exposes an optional output channel that the client can read from for results. But if the client doesn’t define a consumer for the channel, then the pool will lockup. So I decided to introduce a feature that would timeout and allow the pool exit gracefully. I do this by allowing the worker to cancel the parent context so the whole pool including other workers to exit gracefully. Only the worker knows when the timeout occurs not the parent. How can I fix this? (gh/snivilised/lorax/boost/issues/68)
@@dawnrazorif you’re just using a timeout mechanism, just set the timeout in the context that you pass from the parent to the children using WithTimeout() (I explained how to use it in the video). Hope that helps!
@@kantancoding hi again, actually I don’t think your approach will work and the reason is this. The worker is running a task and there is no way to know how long the task will take. So what value do you set for the timeout in the parent context. There is no sensible value that you could come up with. And besides, the timer should only start at the point when the worker has attempted to sent to the output channel. Am I wrong about this?
@@kantancoding just wanna say thanks for making me realise that trying to cancel a parent from a child was totally wrong. I’m junking my entire worker pool and starting again with a better design
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Become a Golang Expert With This Hands-On Golang Course 👉 kantancoding.io
Could someone link the “previous video required viewing?
@@thisisreallyme3130 this video is part of a series on Go Concurrency
ruclips.net/p/PL7g1jYj15RUNqJStuwE9SCmeOKpgxC0HP
i came looking to debug a global pointer, found this unrelated subject, you helped me understand a very usefull go routines skill, very concise and not annoying precise to the point explanations. Thank you man 🙏🏼
Your style of teaching is the best I've ever seen, you can tell you know this stuff instead of regurgutating the documentation like every other channel. I'll buy your microservices course as soon as I can
Hey, thank you so much for your kind words and support! It really motivates me to keep going :)
Very interesting !! Thank you !
thanks for the mini series, really solidified my understanding around concurrency in go. lets GOOOO!
Thanks mate. I've enjoyed your video series on concurrency in GO. Nice and clear explanation. Very helpful. Keep on the good work.
Hey! Thanks for the encouragement. I’m glad you enjoyed it 😊
Amazingly structured comprehensive video! Thank you very much
Thank you! Happy to help 😊
Why we are not passing the address of context and stream to generic functions? Isn’t it creating new variables every time we call it?
Great teaching I am going to buy the course.
Wonderful! I hope it is useful for you 😊
🙏
Very well motivated and well explained.
Glad you're back to making Go videos man... They're super useful
Thank you! More to come!
Good explanation. Do you really need to duplicate the code for ctx cancel handling? Can't you have it in a separate function? Your function naming in the example is kind of bad.
Thanks! Happy to help 🙂
11:40 Did u mean leaf go routines?
@kantancoding thanks for nice visualisation
my requirement is that main spawns multiple child (go routines) and
if some thing goes wrong in any of the child then all child must abort right at the point what ever they are doing now
and reported back to parent
is errGroup coupled with context-with-cancel works in this scenario?
if there exists any existing library it wud be really great, if not wanna make one to help dive deeper
Nicely explained 👏
Thanks for watching 😊
can you do a video on ticker package and go sarama package. Both of them doesn't have any good resources on youtube.
not sure at the moment but I will keep it in mind! ☺️
really good explanation
This was really good. Thanks
Excellent!
Glad you liked it!
Sir upload go tutorial for beginners
Hmm I have quite a few geared towards beginners. Is there anything specific you want to see?
@@kantancoding yes, I am beginner in programming. Golang is my first programming language
Introduction to Programming Using Go
ruclips.net/video/08Blkpo1F8I/видео.html
Great video, but what happens when you DO want to cancel a parent context from a child. I have this exact scenario and in this case I pass in the parents cancel to the child gr. this works fine but this seems to be going against the grain. How do you cancel the parent without passing cancel func? What is wrong with this?
I can’t think of any valid scenario where you’d cancel the parent from a child goroutine. I’d say the fact that you want/need to do this points out a fundamental design flaw in your application.
I can help more if you tell me WHY you feel it is necessary to cancel the parent from the child.
@@kantancoding great thanks. I knew it was wrong but I couldn’t figure out how to fix it properly. I have designed a worker pool. The worker pool exposes an optional output channel that the client can read from for results. But if the client doesn’t define a consumer for the channel, then the pool will lockup. So I decided to introduce a feature that would timeout and allow the pool exit gracefully. I do this by allowing the worker to cancel the parent context so the whole pool including other workers to exit gracefully. Only the worker knows when the timeout occurs not the parent. How can I fix this? (gh/snivilised/lorax/boost/issues/68)
@@dawnrazorif you’re just using a timeout mechanism, just set the timeout in the context that you pass from the parent to the children using WithTimeout() (I explained how to use it in the video). Hope that helps!
@@kantancoding hi again, actually I don’t think your approach will work and the reason is this. The worker is running a task and there is no way to know how long the task will take. So what value do you set for the timeout in the parent context. There is no sensible value that you could come up with. And besides, the timer should only start at the point when the worker has attempted to sent to the output channel. Am I wrong about this?
@@kantancoding just wanna say thanks for making me realise that trying to cancel a parent from a child was totally wrong. I’m junking my entire worker pool and starting again with a better design
hey man, welcome back, I'll watch your vid.
Thank you for watching! More to come 😊
The content is superb but if you allow me a small critique:
don't repeat yourself that much. It's a video. People can go back if unclear.
Yeah good point. Sometimes I forget that I already explained something and then I notice it while editing 😂
This explanation is worth paying time for
Thank you! I’m glad it helped 🙂
Super helpful. Thanks!
Happy to help 🙂
hiii, we missed you
Hello!! Me too!!
beast
Go is Google
You alllll get a context 😂
😂🤣
Honest feedback, it was bit verbose and was lacking clarity unlike other tutorials. Thanks anyway for the effort.
Thanks for watching! 🙂