...
[14:54:21 CST(-0600)] <holdorph> nod
[14:55:01 CST(-0600)] <holdorph> ok, nice. I didn't see any option for 'sharing' permissions, so wanted to make sure it was accessible to public, before posting the link to the mailing list.
[14:55:02 CST(-0600)] <athena> looks like a nice survey
[14:55:13 CST(-0600)] <athena> do we want to maybe ask what the institution is?
[14:55:35 CST(-0600)] <athena> my suggestion would be to add that
[14:55:47 CST(-0600)] <athena> and then maybe a checkbox to decide whether to allow us to list them as a uportal adopter
[14:55:48 CST(-0600)] <holdorph> i was going to just do one question, so people would be more likely to answer it.
[14:55:49 CST(-0600)] <Arvids2> +1 from me
[14:55:52 CST(-0600)] <athena> and then we can make a map of responses
[14:55:59 CST(-0600)] <athena> i know we don't want to add too much
[14:56:13 CST(-0600)] <holdorph> i'm worried there's some relationship to length of survey to number of responses 
[14:56:18 CST(-0600)] <athena> but from a practical standpoint, it'll probably be more useful to those of us doing development and planning to have a sense of which schools are running which versions
[14:56:49 CST(-0600)] <athena> because then we can infer things about institution size, java expertise, etc. that can help us actually do something useful with those responses
[14:56:58 CST(-0600)] <Arvids2> Hmm... portal registration portlet serves for that purpose
[14:57:15 CST(-0600)] <athena> right - we don't need to ask all those questions all over again
[14:57:34 CST(-0600)] <athena> but if we know which institutions are planning to upgrade to uportal 4, we can have a sense of how big they are, etc. from information we already have
[14:57:51 CST(-0600)] <Arvids2> That reminds me that I should fill in that form
[14:58:04 CST(-0600)] <athena> and . . . that's the reason i suggested we maybe add a checkbox too
[14:58:10 CST(-0600)] <athena> then we could create a map, update the public data
[14:58:15 CST(-0600)] <athena> since i think we all know it's really out of date
[15:00:56 CST(-0600)] <Arvids2> btw, there are still two lists of deployments: https://wiki.jasig.org/display/UPC/Deployed+uPortals and http://www.jasig.org/uportal/deployments
[15:01:14 CST(-0600)] <athena> and we also have a google spreadsheet, which should probably replace both those things
[15:01:19 CST(-0600)] <athena> i'll poke the steering committee about that
[15:01:26 CST(-0600)] <holdorph> ok, sent. I know it would be nice to have the institution name, i wanted it as well. But I just worried too much that it might be just enough to cause someone to not fill it out. I rather like the anonymous nature of it, in it's current form.
[15:02:01 CST(-0600)] <athena> i guess - could have been optional
[15:02:32 CST(-0600)] <athena> as a developer i'm worried i won't be able to do much with the resulting data
[15:03:24 CST(-0600)] <holdorph> 'much' sure. i agree. but the idea only occurred to me, in terms of being able to answer Arvids question earlier.
[15:04:23 CST(-0600)] <holdorph> "is anyone else running uPortal 4". Sure I won't be able to say which organization is running it. but at least I'd be able to say "yes, about 4 schools are running it in production" or something like that
[15:05:48 CST(-0600)] <holdorph> wow, already got one response, besides Arvids. nice.
[15:06:04 CST(-0600)] <Arvids2> that was fast
[15:06:16 CST(-0600)] <holdorph> oooh, one more. up to 3. exciting.
[15:06:46 CST(-0600)] <holdorph> 4
[15:07:47 CST(-0600)] <Arvids2> ok, time to sleep. Thank you for your time. Good night I´m looking forward to see those results, because it could speed up some possible bug detection.
[15:08:10 CST(-0600)] <holdorph> g'night. later.
[15:11:24 CST(-0600)] <holdorph> 3 responses so far for up 3.1.x (current), 2 for up 3.2.x. All 5 responses plan to upgrade to up 4.0.x. 3 in jan-march, 1 in april-june, 1 in oct-dec
[15:32:12 CST(-0600)] <holdorph> 12 responses. now with 2 of the 12, saying their plans are upgrading from 3.2.x to 3.2.x. still have the 1 response with no plans to upgrade, the other 9 all plan to upgrade to up 4, this year. currently no one is running up 4 in production.
[16:14:14 CST(-0600)] <pandisaurus> hey I am trying to import some channels into uPortal 4 (the channels should be upgrading from 3.2) and I occasionally get an error (occasionally because I can run the import and get the error, then run it again without changing anything and sometimes no error occurs)
[16:14:34 CST(-0600)] <pandisaurus> the error is: Caused by: org.xml.sax.SAXParseException: cvc-pattern-valid: Value ' dailyUniverseMultimedia ' is not facet-valid with respect to pattern '[\w-_]+' for type 'fname-type'.
[16:14:48 CST(-0600)] <pandisaurus> the value is arbitrary, it changes randomly (that's the name of one of the channels)
[16:14:56 CST(-0600)] <pandisaurus> that is a portlet, in this case
[16:15:24 CST(-0600)] <EricDalquist1> hrm
[16:15:30 CST(-0600)] <EricDalquist1> not sure how that error would just go away
[16:15:51 CST(-0600)] <EricDalquist1> so you're saying that on try 1 the import fails on foo.channel
[16:15:59 CST(-0600)] <EricDalquist1> but then on try 2 foo.channel imports correctly?
[16:16:13 CST(-0600)] <pandisaurus> that is correct
[16:16:21 CST(-0600)] <pandisaurus> and bar.channel fails another time
[16:16:34 CST(-0600)] <EricDalquist1> that is very strange
[16:16:39 CST(-0600)] <pandisaurus> where foo.channel and bar.channel are completely arbitrary because it could be any of the channels
[16:16:43 CST(-0600)] <EricDalquist1> yeah
[16:16:48 CST(-0600)] <pandisaurus> and sometimes it just goes through all of them claiming successful
[16:17:25 CST(-0600)] <EricDalquist1> I'm just about to sign off for the day … could you create a jira issue at issues.jasig.org and paste in the full output of a failed run?
[16:17:31 CST(-0600)] <EricDalquist1> that would help in tracking down the problem
[16:17:40 CST(-0600)] <pandisaurus> I'll note, it says "INFO Importing 104 files of type <channel-definition script="classpath://org/jasig/portal/io/import-channel_v3-2.crn"> " then it does not say upgraded 104 times
[16:17:55 CST(-0600)] <EricDalquist1> ok, that sounds correct
[16:18:14 CST(-0600)] <EricDalquist1> even better if you can also attach the .channel file that failed in the example you post
[16:18:21 CST(-0600)] <EricDalquist1> I realize it is different channel files each time
[16:18:28 CST(-0600)] <EricDalquist1> but having the correlation for one failed run could help
[16:18:56 CST(-0600)] <pandisaurus> I can do that no problem, its just odd
[16:19:06 CST(-0600)] <EricDalquist1> I agree
[16:19:21 CST(-0600)] <pandisaurus> what determines whether it says 'upgraded' next to the channel or not?
[16:19:58 CST(-0600)] <pandisaurus> since I have you here
[16:20:35 CST(-0600)] <EricDalquist1> it should say it for all of them
[16:20:43 CST(-0600)] <EricDalquist1> since you are importing .channel files from 3.2
[16:20:57 CST(-0600)] <EricDalquist1> the XML file has to be transformed into the 4.0 format
[16:20:59 CST(-0600)] <EricDalquist1> and then imported
[16:21:10 CST(-0600)] <EricDalquist1> that transform step is what prints out the upgraded message
[16:21:54 CST(-0600)] <pandisaurus> I'm showing 24 "upgraded" messages, but it says it found 104 files to import (104 should be accurate) is there a way to see what files its skipping and why?
[16:22:08 CST(-0600)] <EricDalquist1> is that after a failure?
[16:22:16 CST(-0600)] <pandisaurus> no I'm counting when its successful
[16:22:19 CST(-0600)] <EricDalquist1> hrm
[16:22:23 CST(-0600)] <EricDalquist1> that sounds like a bug
[16:22:35 CST(-0600)] <EricDalquist1> you should be seeing either the same numbers all the way through
[16:22:40 CST(-0600)] <EricDalquist1> or it should fail with a reason
[16:22:49 CST(-0600)] <EricDalquist1> stuff shouldn't get silently ignored
[16:23:39 CST(-0600)] <pandisaurus> hmmm, that's troublesome because it is silently ignoring. "git checkout" just updates to the most current version of the trunk right? If I'm not specifying a branch?
[16:25:16 CST(-0600)] <EricDalquist1> sorry
[16:25:40 CST(-0600)] <EricDalquist1> "git checkout branch-name" checks out the specified branch
[16:25:41 CST(-0600)] <EricDalquist1> locally
[16:25:50 CST(-0600)] <EricDalquist1> to updates to the branch you are currently on
[16:25:57 CST(-0600)] <EricDalquist1> do "git pull"
[16:26:18 CST(-0600)] <EricDalquist1> which is a shortcut for doing:
[16:26:18 CST(-0600)] <EricDalquist1> git fetch
[16:26:19 CST(-0600)] <EricDalquist1> git merge origin/current-branch-name
[16:26:34 CST(-0600)] <EricDalquist1> you can determine your current branch via "git status"
[16:26:41 CST(-0600)] <EricDalquist1> have to run though