hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
Amy1 has quit [Ping timeout: 250 seconds]
Amy1 has joined #ste||ar
jaafar_ has joined #ste||ar
<Yorlik>
Finally the repl starts taking shape - what a pain - and still full of bugs: https://imgur.com/a/Fvvze8K
<Yorlik>
Crazy how much time you can spend on trivial stuff if you know crap about it .. :)
jaafar_ has quit [Quit: Konversation terminated!]
jaafar has joined #ste||ar
jaafar has quit [Quit: Konversation terminated!]
jaafar has joined #ste||ar
jaafar has quit [Quit: Konversation terminated!]
K-ballo has quit [Quit: K-ballo]
<hkaiser>
Yorlik: \o/
<Yorlik>
Hey!
* Yorlik
waves with a 50 poind curses manual ...
<Yorlik>
Wow - pdcurses managed to crash with a heap corruption on a window resize ...
hkaiser has quit [Quit: bye]
Amy1 has quit [Ping timeout: 250 seconds]
Amy1 has joined #ste||ar
Abhishek09 has joined #ste||ar
Abhishek09 has quit [Ping timeout: 256 seconds]
adityaRakhecha has quit [Ping timeout: 256 seconds]
Abhishek09 has joined #ste||ar
nikunj has quit [Ping timeout: 258 seconds]
nikunj has joined #ste||ar
jaafar has joined #ste||ar
jaafar has quit [Client Quit]
jaafar has joined #ste||ar
kshitija has joined #ste||ar
kshitija has left #ste||ar [#ste||ar]
jaafar has quit [Client Quit]
jaafar has joined #ste||ar
kshitija has joined #ste||ar
kshitija has left #ste||ar [#ste||ar]
Abhishek09 has quit [Ping timeout: 256 seconds]
jaafar has quit [Ping timeout: 246 seconds]
Abhishek09 has joined #ste||ar
Abhishek09 has quit [Ping timeout: 256 seconds]
<zao>
SIGWINCH is fun.
K-ballo has joined #ste||ar
Abhishek09 has joined #ste||ar
<Abhishek09>
is anyone here?
Abhishek09 has quit [Ping timeout: 256 seconds]
hkaiser has joined #ste||ar
eschnett has quit [Quit: eschnett]
Abhishek09 has joined #ste||ar
jaafar has joined #ste||ar
eschnett_ has joined #ste||ar
Abhishek09 has quit [Quit: Page closed]
eschnett_ has quit [Quit: eschnett_]
jaafar has quit [Quit: Konversation terminated!]
Abhishek09 has joined #ste||ar
<Abhishek09>
hello guys
jaafar has joined #ste||ar
eschnett_ has joined #ste||ar
<K-ballo>
hello
Abhishek09 has quit [Ping timeout: 256 seconds]
hkaiser has quit [Ping timeout: 250 seconds]
eschnett_ has quit [Quit: eschnett_]
Abhishek09 has joined #ste||ar
<Abhishek09>
hello
mdiers_1 has joined #ste||ar
mdiers_ has quit [Ping timeout: 272 seconds]
mdiers_1 is now known as mdiers_
<K-ballo>
hello Abhishek09, are you there?
<Abhishek09>
yes
<K-ballo>
ok
hkaiser has joined #ste||ar
eschnett_ has joined #ste||ar
Abhishek09 has quit [Quit: Page closed]
<Yorlik>
hkaiser: How complicated would it be to have component id_types be persistent over store/reload cycles?
<Yorlik>
I am thinking not waiting for that or trying to implement it and instead use an independent id, directly mapping to the current locality of a component, similar to an object dictionary service.
<Yorlik>
Pne problem I see is, what happens if a source locality of a migrated component is down?
<Yorlik>
e.g. a 4 locality cluster, objects scattered all over the place and you restart with three localities only.
<Yorlik>
data shouldn't be toed to a locality.
<Yorlik>
s/toed/tied/g
<hkaiser>
Yorlik: if this is something absolutely necessary for you we can make it happen
<Yorlik>
hkaiser: Can we talk about this really quick in voice? Just to have the problem clearly defined and communicated?