Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2017-03-19

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:14 jeltsch joined #darcs
01:29 pointfree[m] darcs-devel/darcs issues is getting spammed with Quickbooks spam.
01:30 pointfree[m] The spammer's username is "Bear"
01:31 pointfree[m] also, wiki spam: http://darcs.net/_diff/Dial%2018005641194%20cisco%20customer%20service%20technical%20support?to=f2bbacf5de291b16deb2e41475fa3681f1aa6198
01:36 jeltsch lambdabot: @messages
01:38 jeltsch sm, pointfree: An example for block quotes not being considered is the page that I have shown to you before: http://hub.darcs.net/jeltsch/ucs. The section “Frequently asked questions” contains the questions as block quote.
02:46 mizu_no_oto joined #darcs
02:47 ilbot3 joined #darcs
02:47 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.12.5 is out http://darcs.net/Releases/2.12
03:17 mizu_no_oto joined #darcs
03:30 mizu_no_oto joined #darcs
07:19 Heffalump bah, there seem to be a whole load of spam users on the wiki again
10:10 Riastradh joined #darcs
11:12 jeltsch joined #darcs
15:29 jeltsch joined #darcs
15:37 jeltsch lambdabot: @messages
15:37 lambdabot You don't have any messages
16:32 IRCFrEAK joined #darcs
17:58 leg joined #darcs
19:06 jeltsch joined #darcs
19:09 mizu_no_oto joined #darcs
20:18 jeltsch joined #darcs
20:25 pointfree[m] sm: http://hub.darcs.net/simon/darcsden/issue/140#comment-20170319T200153
20:28 pointfree[m] Not sure if it's worth the effort to reintroduce an insecure kex for the sake of avoiding an upgrade.
20:33 pointfree[m] curve25519-sha256 was introduced in openssh 6.5
20:33 pointfree[m] https://www.openssh.com/txt/release-6.5
20:53 pointfree[m] thielema is probably using Mac OSX, which ships with ancient versions of all the unix tools.
21:17 bfrk joined #darcs
21:18 bfrk while hacking on darcs i oticed something i cannot explain
21:18 bfrk s/oticed/noticed/
21:19 bfrk there is this function withRepoLockCanFail
21:20 bfrk it is only used by log and annotate and only to call attemptCreatePatchIndex
21:22 bfrk the two commands pass YesUpdateWorking flag which IMO makes no sense, they both should not update the working tree, and creating the patch index should neither
21:23 bfrk now when i pass NoUpdateWorking for the log command, the result is that log.sh test fails when calling darcs add on a file that has been 'darcs moved'd away. WTF?
21:36 bfrk Heffalump: are you listening?
21:45 * Heffalump appears
21:46 Heffalump I can't remember anything very relevant about that code, except I remember it mostly being a mess of options/different entry points to "with a repository" code
21:47 Heffalump and the patch index stuff was probably somewhat bolted in. Presumably the overall goal is for a mutating operation (patch index creation) to happen even on a notionally read-only operation
22:05 bfrk Hi thanks
22:06 bfrk digging deeper I see that the flags is used to decide which things to revert when calling revertRepositoryChanges
22:06 maerwald joined #darcs
22:07 bfrk it looks as if passing NoUpdateWorking leaves the repo in a somewhat wrong state; perhaps this code path isn't used often
22:09 sm @tell jeltsch thanks, I looked at that a little today but it needs more debugging. It's an odd one
22:09 lambdabot Consider it noted.
22:09 sm @tell feel free to open an issue
22:09 lambdabot Consider it noted.
22:09 jeltsch lambdabot: @messages
22:09 sm oops hi jeltsch
22:10 jeltsch sm: Hi!
22:10 jeltsch So in principle, block quotations should work.
22:10 jeltsch And there is just a bug here.
22:10 bfrk Heffalump: the patch index stuff iself is pretty clean but you are right about the repo job story
22:11 jeltsch sm: Where should I open an issues?
22:11 sm jeltsch: I think so. It works for me on the front page or at command line, not sure why it's failing there
22:11 sm the darcsden issue tracker, linked from front page
22:11 bfrk Heffalump: I think the bug here is that patch index creation doesn't need all this revertRepo stuff since it doesn't try to change anything, just adds the patch index
22:12 jeltsch sm: Have you tried with the same Markdown file (the README.markdown from ucs)? Maybe there is some subtlety in the particular Markdown source.
22:12 sm yes, the file looks fine
22:29 jeltsch sm: Did I overwrite your changes to the issue description? What happens if people concurrently edit issues?
22:41 sm jeltsch: no you didn't, I was just commenting. It prevents that I believe.

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary