Time
S
Nick
Message
07:02 dataverse-user joined #dataverse
08:06 jri joined #dataverse
09:21 soU joined #dataverse
13:21 donsizemore joined #dataverse
14:53 pdurbin joined #dataverse
15:21 pameyer joined #dataverse
15:32 directxman12 joined #dataverse
15:46 pdurbin
directxman12: welcome!
15:46 Michael92 joined #dataverse
15:47 pdurbin
Michael92: welcome!
15:47 directxman12
pdurbin: thanks!
16:05 pameyer
pdurbin: just FYI, https://jenkins.io/doc/book/managing/cli/ . I'm not sure about authentication (I've only used it with a local jenkins server that I had wide-open); but it might be worth a look for moving jobs from one jenkins server to another
16:08 pdurbin
pameyer: interesting. Thanks. Let's definitely talk this out after standup (or whenever) some day that you're here. I'm trying to picture what the pull request looks like. Maybe an addition to the dev guide.
16:10 pameyer
pdurbin: sounds like a plan
16:40 donsizemore joined #dataverse
16:48 andrewSC
Hey guys, I'm looking at a specific dataset locally and when I try to edit the metadata via the UI I get "XML Parsing Error: not well-formed" within the browser console
16:48 andrewSC
It's an older dataset (deposited last year feb)..
16:48 pdurbin
andrewSC: yuck. What version of Dataverse?
16:49 andrewSC
just upgraded to 4.8.5 but it was also happening in 4.8.4
16:49 andrewSC
it's only this one dataset it seems.. lol
16:49 pameyer
andrewSC: any special characters (or html-formatted text)?
16:49 andrewSC
hmmm lemme see
16:53 andrewSC
the description doesn't stick out as odd but it definitely looks like it could have been copy/pasted so very possible there's a special char in there
16:53 andrewSC
pameyer: do you know which table the descriptions are kept in the db?
16:53 andrewSC
there's a whitespace character at the end of the description i'd like to try and remove and see if that's the issue
16:54 pameyer
andrewSC: not from memory, but I'll take a quick look
16:54 andrewSC
tyty
16:54 pdurbin
andrewSC: should be the "datasetfieldvalue" table: http://phoenix.dataverse.org/schemaspy/latest/tables/datasetfieldvalue.html
16:54 andrewSC
boom
16:54 andrewSC
kk gonna take a look now
16:55 pameyer
pdurbin beat me to it :)
16:55 pdurbin
andrewSC: is there a stacktrace in server.log?
16:55 andrewSC
kinda surprising but I didn't see anything when i loaded the page
16:56 pdurbin
andrewSC: huh. ok. can you please email a screenshot of the XML parsing error to support
16:56 andrewSC
mhmm
16:57 pdurbin
thanks
17:20 andrewSC
yeah there's like form feed chars and crap in this
17:20 andrewSC
lemme clean it up and see if it fixes it
17:25 pdurbin
andrewSC: reminds me a bit of https://github.com/IQSS/dataverse/issues/787
17:27 andrewSC
mhmmm
17:27 andrewSC
yeah that was the fix, just updated the value in the db and refreshed the page
17:28 andrewSC
everythings good again
17:28 pdurbin
nice. good job, andrewSC
17:28 andrewSC
:3
17:28 andrewSC
I'll send the email over to support shortly
17:29 pdurbin
andrewSC: or... you could make a pull request documenting your fix :)
17:29 pdurbin
up to you
18:11 andrewSC
pdurbin: haha welll, my fix was just to do an UPDATE and SET with the data I cleaned by hand.. so there wasn't really any code change? I did save the text that caused an issue though.
18:14 pameyer
andrewSC: I think pdurbin's thinking about seeing if it's fixed, and/or making sure that the text doesn't need to be cleaned by diving into the db
18:14 pameyer
good that it's fixed for you thought :)
18:15 andrewSC
ohhh I see, a PR rather than a GH issue?
18:16 pdurbin
andrewSC: actually a github issue first is better. to describe the problem
18:16 pameyer
more like having the info for a GH issue - it might already be fixed, or it might be something to check
18:16 andrewSC
mmmm gotcha gotcha
18:16 andrewSC
yeah I can definitely do that :)
18:17 pdurbin
you could upload your screeshot to the github issue you create, as long as it's ok that the screenshot is public
18:17 andrewSC
I think it is--it's just the actual error in the web console.. The text with the escape characters I will need to change though.
18:50 donsizemore joined #dataverse
18:51 donsizemore
@pdurbin afternoon - is there a moratorium on documentation updates pending redesign, or may i submit a PR?
18:55 pdurbin
donsizemore: you can *always* send us pull requests. :) What redesign? :)
18:56 donsizemore
@pdurbin er, maybe restructuring. on friday afternoon i did a manual installation from the guide, and there are some things i'd like to make more clear or otherwise tweak. just language and examples, really
18:57 pdurbin
Gotcha. I forget, did I create a new Google doc to start a reorg? Maybe I just talked about the old one.
19:00 andrewSC
https://github.com/IQSS/dataverse/issues/4442
19:01 andrewSC
I believe I followed all the rules within the contributor guidelines--definitely let me know if I need to add something
19:02 pameyer
andrewSC: thanks
19:02 pameyer
interesting - control characters
19:02 andrewSC
mhmmm..
19:02 andrewSC
http://donsnotes.com/tech/charsets/ascii.html
19:02 donsizemore
@pdurbin I thought Derek was doing it? I dunno. Just didn't want to do touch-ups when there's demo on the way
19:02 andrewSC
surprised me tbq
19:02 pdurbin
andrewSC: thanks. The error looks different than I expected. You might want to edit what you wrote and add the version of Dataverse.
19:03 andrewSC
s/tbq/tbqh/
19:03 andrewSC
definitely
19:03 pdurbin
andrewSC: do you know if it's possible to reproduce with a fresh dataset?
19:04 andrewSC
hmmmm
19:17 andrewSC
So I tried it with unicode escape characters and couldn't get it to replicate
19:24 pameyer
that might be a good sign
19:28 pdurbin
So maybe it only applies to data that was added in older versions of Dataverse?
19:33 andrewSC
That's honestly what I'm thinking...
19:48 pdurbin
Ok. I guess we should decide what to do with that issue.
19:48 andrewSC
hahah
19:49 andrewSC
I personally don't think it's entirely unreasonable to just close it out. I feel like if people were experiencing it in a non-marginal way you guys would be seeing it pop up more..
19:52 pdurbin
yeah
19:53 pdurbin
hopefully not too many people are affected
20:07 andrewSC
mhmm
20:11 pdurbin
I mean, we could use that issue to document the fix you applied. In the Admin Guide, maybe. But if it's a rare bug maybe it's not worth documenting.
22:16 andrewSC
yeahh
