K-ballo 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/
hkaiser has joined #ste||ar
shahrzad has quit [Quit: Leaving]
hkaiser has quit [Quit: bye]
bita_ has joined #ste||ar
bita has quit [Ping timeout: 240 seconds]
bita_ has quit [Ping timeout: 260 seconds]
hkaiser has joined #ste||ar
akheir has joined #ste||ar
bita_ has joined #ste||ar
shahrzad has joined #ste||ar
<gonidelis[m]> why did we replace `util::invoke()` ??
<K-ballo> internally you mean?
<gonidelis[m]> yes
<K-ballo> util::invoke() is still there to be used
<K-ballo> the macro creates one less call frame, the better to debug it, and is slightly lighter at compile time
<gonidelis[m]> huh? why does the compiler hit me then?
<gonidelis[m]> sec
<K-ballo> we have not replaced util::invoke, we've replaced some calls in internal implementations
<gonidelis[m]> do i need to include `functional/invoke.hpp` or `functional/detail/invoke.hpp` in order to invoke the macro?
<K-ballo> detail for the macro
<gonidelis[m]> hm... sounds like time to rebase
<K-ballo> ideally you would rebase early or so, but why does it matter here?
<K-ballo> how did the compiler hit you into using the macro?
<gonidelis[m]> the compiler hit me on using `util::invoke()` from a PR that is open since september
<K-ballo> doesn't sound like something that would be related to the macro
<gonidelis[m]> it's not
<gonidelis[m]> it's related to `util::invoke()`
<K-ballo> ok, *how* is the compiler hitting you on `util::invoke()`?
<gonidelis[m]> sec
<gonidelis[m]> libs/parallelism/algorithms/include/hpx/parallel/util/transform_loop.hpp:126:46: error: no matching function for call to `xinvoke(hpx::parallel
<gonidelis[m]> 126 | *dest = hpx::util::invoke(std::forward<F>(f), first);
<K-ballo> xinvoke is definitely not a thing
<gonidelis[m]> it's stupid nano things
<gonidelis[m]> it means just invoke
<K-ballo> well then, it's not a macro thing, it's not an include thing
<K-ballo> sounds like `f` isn't callable with `first`
<K-ballo> the real compiler message would say
khuck has joined #ste||ar
<gonidelis[m]> btw any good suggestion on how to read compiler output when on ssh
<gonidelis[m]> ?
<khuck> is Hartmut completely offline due to the storm?
<K-ballo> I just copy the whole history and read it locally
<gonidelis[m]> khuck: he was active a few hours back
<gonidelis[m]> K-ballo: how do you transfer the text ;p ?
<K-ballo> uhm right click, copy all to clipboard
<gonidelis[m]> K-ballo: lol...
<gonidelis[m]> I mean it's terminal
<gonidelis[m]> I tried redirecting output to a file
<K-ballo> the tool I use has a "copy all to clipboard" terminal option included
<K-ballo> I don't redirect to any files, I let it go to the terminal, then copy all to clipboard
<gonidelis[m]> tool?
<K-ballo> I happen to be using putty here
<K-ballo> traditional terminals have select all / copy options too
<zao> If you have clipboards sufficiently forwarded, you can pipe into xsel or xclip, or you could use a command line tool to make a private GitHub gist.
<zao> Or if you trust VS Code, use its remote SSH connectivity to browse files.
<zao> If you want to see interactive output from a program but also store stdout to file, there's the "tee" command.
<gonidelis[m]> zao: I am using the ssh through vs code
<zao> So you could do something like "blargh 2>&1 | tee persistent.log | ..."
<K-ballo> now that you mention it, I've used scp when dealing with some header tools that would output hundreds of mb of output too
<gonidelis[m]> but the error lines might be a lot and vs refuses to open the file
<gonidelis[m]> K-ballo: now we are talking
<K-ballo> come on, template error messages are bad, but not hundreds of mb of output bad
<gonidelis[m]> might that be the case
<zao> If it was local, you could use the terminal in VS Code and pipe into 'code -' which would open the output as a file in the editor, but not sure if that also works remotely.
<K-ballo> it's not
<gonidelis[m]> but my errors are not just template errors
<zao> Shouldn't you have some build system integration in Code anyway?
<gonidelis[m]> they are rookie tamplate errors
<zao> Still proud over the 500 MiB of template instantiation error I got out of Spirit Classic back in the early 00s.
<K-ballo> that I can believe
<zao> (this one compiles, but during development of it)
<zao> No attributes anywhere, just a ton of semantic actions ^_^
<K-ballo> oh god that table
<K-ballo> all the symbols
<zao> :D
<K-ballo> imagine doing it in x3 and not splitting parsers into rules, kinda like the monster parser
<gonidelis[m]> just scp-ed. its 22 Mb :D
<gonidelis[m]> long way to reach zao though
<gonidelis[m]> (the warnings stack up in thousands though)
<K-ballo> it takes an experienced professional to produce hundreds of mb of template error messages
<zao> If you want a tool that handles large logs, I use `glogg` occasionally.
<gonidelis[m]> i don't know whether I can load all those tools on rostam though
<zao> Has a neat little results window and regex support, and doesn't choke on large files like editors might.
<zao> It's graphical so you'd run it locally on your copied log file.
<gonidelis[m]> oh ok
<gonidelis[m]> zao: thanks a lot
<zao> otherwise, learn to love and use `less` and `grep` :)
<gonidelis[m]> hm... didn't know less. already using `grep` a lot
<gonidelis[m]> thanks
<gonidelis[m]> !
<zao> The interactive commands of less are super unobvious but reasonably powerful.
<zao> -S to make it not wrap lines, -I to make searches case insensitive, etc.
<hkaiser> khuck: what's up?
<khuck> hkaiser: just making sure you saw the emails from NSF
<khuck> I didn't know if you were offline for a meeting, or because of the storm
<khuck> no worries, all good now
<gonidelis[m]> hkaiser: what's the situation? is everything fine???
<hkaiser> gonidelis[m]: yes, it's raining a bit, nothing serious
<gonidelis[m]> hkaiser: glad to heat
<gonidelis[m]> hear *
<gonidelis[m]> stay safe B)
<hkaiser> gonidelis[m]: thanks!
<K-ballo> in all my time in baton rouge I dont ever remember it raining "a bit"
<hkaiser> K-ballo: yah, you usually need a boat if it rains ;-)
<hkaiser> but today it's really just raining slightly
<gonidelis[m]> K-ballo: wow! you 've been to BR?
<K-ballo> I lived there back in late 2013
<gonidelis[m]> wow! were u studying or sth?
<K-ballo> working on hpx
<gonidelis[m]> awesome
<gonidelis[m]> plz tell me you were not a gsoc student
<gonidelis[m]> ;p
<K-ballo> no
<gnikunj[m]> hkaiser Another storm in Baton Rouge?
<hkaiser> gnikunj[m]: not really here, 100 miles east
<gnikunj[m]> Whoa, I thought the storm season was over...
<gnikunj[m]> Stay safe!
<hkaiser> thanks