Apache Allura / Chat

Apache Allura / Chat is hosted on FreeNode IRC channel #allura

Log for 2013-04-25

  • 03:13:40
    allura-ci

    Project allura build #2,068: STILL FAILING in 38 sec: http://engr.geek.net/hudson/job/allura/2068/

  • 13:30:13
    allura-ci

    Project forgehg build #107: UNSTABLE in 1 min 35 sec: http://engr.geek.net/hudson/job/forgehg/107/

  • 13:30:13
    allura-ci

    Tim Van Steenburgh: Consider repo empty if it doesn't exist on disk.

  • 13:35:11
    tvansteenburgh

    does it make sense for a tool to assert what a valid mount point is for itself?

  • 13:35:23
    tvansteenburgh

    or should the platform always be in control of that...

  • 13:35:40
    tvansteenburgh

    trying to think through the best way to implement [#5332]

  • 13:36:19
    tvansteenburgh

    one way is for Application to provide a default mount point pattern

  • 13:36:27
    tvansteenburgh

    and let subclasses override

  • 13:36:51
    tvansteenburgh

    but it seems backwards

  • 13:38:13
    tvansteenburgh

    otoh, i can't think of a better way to do it

  • 13:43:03
    brondsem

    another option could be for the "relaxed" mount point definition to be in the platform, and each Application can toggle that on

  • 13:43:36
    brondsem

    so each App doesn't have to have the full regex nor could an App go crazy and do something really weird

  • 13:45:25
    tvansteenburgh

    ah, i like that

  • 13:49:19
    tvansteenburgh

    cory_fu: have you already started reviewing [#5501]?

  • 13:50:10
    tvansteenburgh

    i just realized that i inadvertently opened up project names also. gonna fix that now

  • 14:12:50
    tvansteenburgh

    ok, that's fixed

  • 15:15:25
    brondsem

    regarding escaping when going into solr and/or when coming out of solr (the text field is used to highlight matches in results)

  • 15:27:10
    ctsai-sf

    They have different contents for comments.

  • 15:27:38
    brondsem

    ooh

  • 15:27:43
    brondsem

    i just saw the comment come in via email

  • 15:27:47
    ctsai-sf

    I guess, if you comment on an old revision, it sticks with that old revision. But if you comment on the latest, it's going to stay with the latest.

  • 15:27:54
    brondsem

    yeah

  • 15:28:11
    brondsem

    every version of a wiki page is itself an Artifact

  • 15:28:26
    ctsai-sf

    Yeah, I saw the email too, but I noticed that the link in the footer had the version.

  • 15:28:29
    brondsem

    we shouldn't allow that

  • 15:28:34
    brondsem

    subject line too

  • 15:37:47
    ctsai-sf

    https://sourceforge.net/p/forge/site-support/3779/ <-- sounds reasonable to me that *auth should get CREATE on tickets by default. What do you all think?

  • 15:38:07
    ctsai-sf

    Currently default is "Developer" for CREATE.

  • 15:39:04
    tvansteenburgh

    brondsem: i'm more a fan of escaping on the way out

  • 15:40:01
    tvansteenburgh

    i like knowing that what's in the date store is the original content

  • 15:40:11
    brondsem

    and my fear is that we might not escape something properly on the way in

  • 15:40:29
    tvansteenburgh

    plus, i think you have to do it that way if you want highlighting to always work

  • 15:40:41
    brondsem

    and re-indexing everything to fix an issue like htat would take forever, whereas fixing the escaping on the way out is just a code push

  • 15:41:19
    tvansteenburgh

    like if you search for "this & that", highlighting won't work if you've escaped on the way in

  • 15:41:35
    brondsem

    yeah

  • 15:41:39
    brondsem

    i think i'll go that route then

  • 17:00:51
    allura-ci

    Project allura build #2,069: STILL FAILING in 47 sec: http://engr.geek.net/hudson/job/allura/2069/

  • 17:39:57
    brondsem

    ctsai-sf: agree on 3779, I would've thought it was like that already

  • 17:44:13
    ctsai-sf

    So, I found where to change the default permissions, but, don't know how to fix the corresponding test.

  • 17:48:32
    brondsem

    which test is it?

  • 17:49:55
    ctsai-sf

    ForgeTracker/forgetracker/tests/unit/test_ticket_model.py

  • 17:51:07
    brondsem

    and how does it fail with your change?

  • 17:54:38
    ctsai-sf

    Just rolled back the fiddling I was doing with that test, and running tests again. Paste incoming shortly.

  • 18:06:22
    ctsai-sf
  • 18:09:09
    brondsem

    ha, that's a big list != to another big list

  • 18:09:35
    tvansteenburgh

    glad to see someone using the vagrant box :)

  • 18:09:43
    ctsai-sf

    :)

  • 18:09:51
    brondsem

    on the import line for assert_equal

  • 18:10:05
    brondsem

    change that to import from datadiff.tools instead of nose.tools

  • 18:10:06
    ctsai-sf

    tvansteenburgh: Oh yeah, I meant to tell you I got that working over the weekend.

  • 18:10:08
    brondsem

    and re-run

  • 18:11:18
    ctsai-sf

    I probably should have asked this earlier. Can I run just that one test? Instead of all the ForgeTracker tests?

  • 18:11:30
    brondsem

    yes :)

  • 18:11:56
    brondsem

    nosetests forgetracker.tests.unit.test_ticket_model:TestTicketModel.test_private_ticket

  • 18:12:03
    brondsem

    note the colon, the syntax is slightly different

  • 18:12:29
    brondsem

    if you install nose-progressive and use that, one of the nice features is that it formats your test results better so you can copy & paste the test names

  • 18:12:32
    brondsem

    to re-run them

  • 18:13:26
    ctsai-sf

    ERROR: Failure: AttributeError ('module' object has no attribute 'test_ticket_model')

  • 18:13:50
    brondsem

    you in the ForgeTracker dir?

  • 18:14:00
    ctsai-sf

    Oh, no. That would probably help.

  • 18:14:30
    brondsem

    and if you install nose-progressive, enable it with this in your ~/.noserc

  • 18:14:35
    brondsem

    [nosetests]

  • 18:14:35
    brondsem

    with-progressive=1

  • 18:18:14
    ctsai-sf

    http://pastebin.com/DUC3DuSP <-- remove "raises" from that import line?

  • 18:19:09
    brondsem

    yeah, i think datadiff only has some assert_* methods, so you'll have to still import 'raises' from nose.tools

  • 18:21:23
    brondsem
  • 18:23:39
    brondsem

    tvansteenburgh: one issue with storing the verbatim text in solr is that it contains markdown formatting

  • 18:24:05
    brondsem

    so the reason we went down the sanitization path (when storing in solr) was to strip the markdown formatting and get plain text

  • 18:24:23
    brondsem

    maybe that can happen on the way out too....

  • 18:25:04
    tvansteenburgh

    hrm, didn't think of that

  • 18:25:38
    tvansteenburgh

    that's tricky b/c you don't really want to search against the markdwn

  • 18:25:40
    brondsem

    process is/was to convert markdown to html, and then strip the tags

  • 18:25:44
    brondsem

    yeah

  • 18:26:06
    brondsem

    it might be ok though, because most markdown is just special chars which solr will ignore

  • 18:27:17
    brondsem

    ctsai-sf: so it looks like that didn't help, because t.acl is a ming-instrumented list (hence the "I" prefix)

  • 18:27:39
    brondsem

    could try converting it to a normal list like list(t.acl) in the assert_equal line

  • 18:41:18
    ctsai-sf

    Hrm, wasn't quite sure what you meant, but I tried using "import q; q(list(t.acl))" in a line just above, and it still has the "I" prefix.

  • 18:44:28
    brondsem

    hm, yeah

  • 18:46:18
    brondsem

    i think you're going to have to compare the big lists by hand

  • 18:46:45
    brondsem

    t.acl._deinstrument() would give you the real "list", but datadiff's assert_equal throws an error on some of the contents of that list

  • 18:47:40
    ctsai-sf

    I see. I'll ticket and poke at this more later. Have regular support stuff I need to work on for now.

  • 18:48:14
    brondsem

    ok. I think it'll end up being an easy change to the test. harder to figure out what the change needs to be :)

  • 18:49:10
    ctsai-sf

    Yeah.

  • 19:15:25
    ctsai-sf

    Is there a reference somewhere for tasks that can be run via /nf/admin/task_manager? (for PROSE docs)

  • 19:17:26
    brondsem

    not published.

  • 19:17:42
    brondsem

    find . -name '*.py' | xargs grep '@task' -A1

  • 19:17:50
    brondsem

    that is all the tasks defined in the code

  • 19:18:39
    brondsem

    and also: find . -name '*.py' | xargs grep ScriptTask

  • 19:20:19
    ctsai-sf

    Hmm, I see. Possibly out of the scope for this doc then. I'll pass that on to them at least though.

  • 19:31:29
    tvansteenburgh

    well only the ScriptTask ones can be run from the web ui

  • 19:31:33
    tvansteenburgh

    fwiw

  • 19:31:44
    ctsai-sf

    Ah, that's helpful.

  • 19:31:48
    brondsem

    not true

  • 19:31:53
    brondsem

    you can run any task

  • 19:32:08
    tvansteenburgh

    mm, you're right

  • 19:32:21
    ctsai-sf

    Hrm, I see.

  • 19:48:12
    ctsai-sf

    http://epics-util.hg.sourceforge.net/hgweb/epics-util/epics-util/ <-- apparently something went wrong with this migration.

  • 19:48:40
    ctsai-sf

    https://sourceforge.net/p/epics-util/code/ref/default~/ <-- says it's empty. And a clone says "no changes found"

  • 19:49:51
    ctsai-sf

    I wonder if the ".bak" copy caused something funky to happen: http://epics-util.hg.sourceforge.net/hgweb/epics-util/

  • 19:51:46
    ctsai-sf

    Hrm, actually, judging by their audit trail. Looks like they migrated 6 months ago. What do you guys think, try a re-clone, then if that doesn't work, just give instructions to push to new location?

  • 19:52:51
    brondsem

    sounds reasonable

  • 19:54:14
    ctsai-sf

    <forgehg.hg_main.ForgeHgApp object="" at="" 0x2aaaacf2bb50=""> does not appear to be a cloned repo

  • 19:54:26
    ctsai-sf

    I guess that means just pushing to new location.

  • 21:08:52
    ctsai-sf

    I think I got that test figured out. Running it again just to make sure. Assuming everything goes well, just need to wait for the push to my fork to finish analyzing then I'll get a merge request in.

  • 21:17:56
    ctsai-sf

    Later.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks