jemc changed the topic of #ponylang to: Welcome! Please check out our Code of Conduct => https://github.com/ponylang/ponyc/blob/master/CODE_OF_CONDUCT.md | Public IRC logs are available => http://irclog.whitequark.org/ponylang | Please consider participating in our mailing lists => https://pony.groups.io/g/pony
Matthias247 has quit [Read error: Connection reset by peer]
jemc has joined #ponylang
jemc has quit [Ping timeout: 265 seconds]
jemc has joined #ponylang
Praetonus has quit [Quit: Leaving]
rurban has joined #ponylang
rurban has quit [Client Quit]
cjgajardo has joined #ponylang
c355e3b has quit [Quit: Connection closed for inactivity]
graaff has joined #ponylang
rurban has joined #ponylang
amclain has quit [Quit: Leaving]
jemc has quit [Ping timeout: 265 seconds]
dinfuehr has quit [Ping timeout: 248 seconds]
dinfuehr has joined #ponylang
cjgajardo has quit [Ping timeout: 260 seconds]
_andre has joined #ponylang
rurban has quit [Quit: Leaving.]
TonyLo has joined #ponylang
c355e3b has joined #ponylang
rurban has joined #ponylang
rurban has quit [Quit: Leaving.]
[CBR]Unspoken has quit [Ping timeout: 245 seconds]
[CBR]Unspoken has joined #ponylang
jemc has joined #ponylang
rurban has joined #ponylang
graaff has quit [Quit: Leaving]
amclain has joined #ponylang
Praetonus has joined #ponylang
rurban has left #ponylang [#ponylang]
TonyLo has quit [Ping timeout: 260 seconds]
_andre has quit [Quit: leaving]
<SeanTAllen> jemc: would you agree that serialization memory leak is high priority and we should do a release?
<jemc> in my mind, the key deciding question in general would be - "is someone in need of / asking for a release?"
<jemc> if you guys are using serialization in prod, I'm guessing the answer to that is "yes"
<SeanTAllen> if anyone other than us is, they are probably tearing their hair out
<SeanTAllen> i'll cut a release tonight
<SeanTAllen> i could use a mental break from crushing bugs and memory leaks in ours
<jemc> I personally haven't even played with serialization at all yet
<SeanTAllen> that is how i found the serialization problem
<SeanTAllen> i hooked up a couple machines together which talk over serialization
<SeanTAllen> and boom 500 gigs used
<SeanTAllen> hehe
<jemc> just note that this release will have a few breaking changes in it too
<SeanTAllen> yup
<SeanTAllen> i checked
<SeanTAllen> saw that
<SeanTAllen> CHANGELOGs are awesome
jemc has quit [Ping timeout: 250 seconds]
TwoNotes has joined #ponylang
TwoNotes has left #ponylang [#ponylang]
jemc has joined #ponylang
rurban has joined #ponylang
Matthias247 has joined #ponylang
rurban1 has joined #ponylang
rurban has quit [Ping timeout: 260 seconds]
rurban1 has quit [Quit: Leaving.]
Perelandric has joined #ponylang
Xe has quit [Ping timeout: 260 seconds]
<Perelandric> Thanks to the C name fix from Praetonus, I can now link to a Pony project from a Go app...
<Perelandric> but there's one more problem...
<Perelandric> defining a string argument in the Pony method causes a segfault when run.
<Perelandric> Not a string, but a `Pointer[U8 val] tag`
Xe has joined #ponylang
<Perelandric> The corresponding CGo type is `C.CString`, which is a pointer to the `char` at the start of the strings.
<Perelandric> Any thoughts on what could be wrong?
<Praetonus> Perelandric: That's strange
<Praetonus> Could you get a debugger call trace at the moment of the crash?
<Perelandric> Praetonus: I'll give it a try. Not too strong on the debugging tools, especially in a Go app.
<Perelandric> Praetonus: I added some info to to the bottom of the gist.
<Perelandric> Let me know if there's anything else I can provide.
<Praetonus> Thanks, I think I know what's happening
<Praetonus> When sending a message, you must be in the context of an existing actor
<Praetonus> If you call pony_become() with the actor you created before sending the message, it should work
<Perelandric> Praetonus: I don't see that in the generated header. Is there another library I need to link for that?
<Praetonus> It's in pony.h
<Perelandric> Ah, I see. I just need to figure out about pony_ctx_t...