| Time |
Nick |
Message |
| 00:13 |
|
dbwells_ joined #evergreen |
| 00:13 |
|
remingtron__ joined #evergreen |
| 00:17 |
|
yboston joined #evergreen |
| 02:43 |
|
dbwells__ joined #evergreen |
| 02:45 |
|
ejk joined #evergreen |
| 03:21 |
|
alynn26 left #evergreen |
| 06:31 |
pinesol_green |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live> |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 07:39 |
|
dwgreen joined #evergreen |
| 08:20 |
csharp |
my npm issues yesterday seem to have been solved by one of the following: 'npm rebuild', 'npm update', then re-running 'npm install' and finally 'npm run build-prod' |
| 08:20 |
csharp |
I think 'rebuild' was the key |
| 08:21 |
|
collum joined #evergreen |
| 08:49 |
pinesol_green |
[evergreen|Morkor Quarshie] Docs: Update Authorities.adoc - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=7c98f74> |
| 08:51 |
|
Dyrcona joined #evergreen |
| 09:04 |
berick |
csharp: good to know re: rebuild. not familiar w/ that option. |
| 09:08 |
Dyrcona |
csharp: Still using npm 5.7.1? |
| 09:30 |
pinesol_green |
[evergreen|Remington Steed] Docs: Fix AsciiDoc list formatting - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=122ad1b> |
| 09:39 |
csharp |
Dyrcona: yea 5.7.1 |
| 09:40 |
Dyrcona |
OK. Just checking... |
| 09:46 |
|
jvwoolf joined #evergreen |
| 09:47 |
|
yboston joined #evergreen |
| 09:54 |
|
kmlussier joined #evergreen |
| 10:20 |
|
terran joined #evergreen |
| 10:25 |
gmcharlt |
dbwells: before I merge it, do you have any concerns about bug 1693036 going into both master and rel_3_0; it straddles the line between a bugfix and an enhancement |
| 10:26 |
pinesol_green |
Launchpad bug 1693036 in Evergreen "Web Staff Client: Missing Print Functionality on Patron Form" [Undecided,Confirmed] https://launchpad.net/bugs/1693036 - Assigned to Galen Charlton (gmc) |
| 10:32 |
terran |
It's definitely a big enhancement over the way it was in the xul client. |
| 10:39 |
gmcharlt |
yeah, I'm on the fence - I'm personally fine with putting a release notes entry together and just putting it in master for inclusion in 3.1-rc, if dbwells is OK with it |
| 10:43 |
kmlussier |
It's an improvement over xul printing, but, from terran's screenshots, I would say the current print functionality in web client patron registration is not very usable. |
| 10:43 |
kmlussier |
I know it's not up to me, but I just wanted to offer another viewpoint in favor of bug fix. :) |
| 10:45 |
kmlussier |
I find the bug vs. feature question is more difficult with the web client, mainly because of feature parity issues. |
| 10:47 |
terran |
It is really both. |
| 10:48 |
terran |
Bug fix with benefits. |
| 10:49 |
terran |
(We've already patched it onto our 3.0.2 version so I have nothing invested either way.) |
| 10:57 |
gmcharlt |
yeah, I still remain on the fence. I've punted in LP, but will merge once dbwells weighs in (or, I suppose, if @eightball weighs in) |
| 11:23 |
|
Christineb joined #evergreen |
| 11:28 |
|
yboston joined #evergreen |
| 11:36 |
|
mmorgan joined #evergreen |
| 11:40 |
|
Jaswinder joined #evergreen |
| 11:41 |
Jaswinder |
Hey Guys, I am trying to find out API calls to basic search and how it is being perform under the hood. Any thoughts? Also which schema is used for basic search? |
| 11:44 |
berick |
Jaswinder: this is the API used by the catalog for bib record searching: |
| 11:44 |
berick |
http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/Application/Search/Biblio.pm;h=ca3f85a27f00431343cece893abef754b8872bfb;hb=HEAD#l773 |
| 11:49 |
berick |
that's jumping right into the deep end. you can see how clients call the API by searching for occurrences of open-ils.search.biblio.multiclass.query |
| 11:58 |
Jaswinder |
Thanks berick |
| 11:58 |
Jaswinder |
btw, do you know which schema/tables are being hit during the basic search |
| 11:59 |
berick |
Jaswinder: quite a few tables are referenced. bib record stuff, indexes, holdings data, etc. |
| 11:59 |
Jaswinder |
how about schema? |
| 12:00 |
berick |
if you log postgres queries, you'll see a nice big search query come through when searching the catalog |
| 12:00 |
berick |
Jaswinder: it crosses multiple schemas |
| 12:01 |
Jaswinder |
Thanks for the tip. I am going to do that. |
| 12:01 |
|
beanjammin joined #evergreen |
| 12:02 |
Jaswinder |
I basically need to get to API input and parameters |
| 12:09 |
Jaswinder |
*input and output fields |
| 12:13 |
Dyrcona |
Jaswinder: Have you read any of the introduction to OpenSRF/Evergreen links I shared with you? |
| 12:15 |
Jaswinder |
I believe so but I couldn't find input values and output structure in there |
| 12:16 |
Dyrcona |
Jaswinder: If you do the denials workshop and play with the examples, it will begin to make sense. |
| 12:18 |
Jaswinder |
Can you please share that link again? |
| 12:18 |
Dyrcona |
There's no all-encompassing API documentation at the moment. |
| 12:18 |
Dyrcona |
http://evergreen-ils.org/~denials/workshop.html |
| 12:19 |
Dyrcona |
dbs++ |
| 12:19 |
|
khuckins joined #evergreen |
| 12:19 |
Dyrcona |
You can also query specific APIs with srfsh's introspect command. |
| 12:19 |
Dyrcona |
This is dependent on the API doc comments being accurate. |
| 12:21 |
Jaswinder |
thanks! |
| 12:25 |
Dyrcona |
Jaswinder: This might be more helpful for search if you run it on the server where Evergreen is installed: perldoc OpenILS::Application::Search::Biblio |
| 12:28 |
Jaswinder |
okay. |
| 12:29 |
Jaswinder |
let me go through the exercises and see if I can make sense of how I can consume external APIs and do other modifications |
| 12:29 |
Jaswinder |
:q |
| 12:37 |
mmorgan |
Anyone here use the "Mark Item as Missing Pieces" functionality for items that need to go in transit home? |
| 12:40 |
mmorgan |
When the item goes in transit, the status applied when it was marked missing pieces is lost. This is the xul client. |
| 12:41 |
kmlussier |
mmorgan: What status does it have when you mark missing pieces at home? |
| 12:42 |
mmorgan |
Well, we created a status "Incomplete" and set that in the library setting. But I also reverted that setting so they get "Damaged" |
| 12:42 |
|
jihpringle joined #evergreen |
| 12:43 |
kmlussier |
Whatever I have previously learned about that feature has slowly dissipated from my memory. |
| 12:43 |
mmorgan |
Both are lost when the item goes in transit. |
| 12:43 |
mmorgan |
TBH the functionality has always seemed awkward to me. |
| 12:44 |
kmlussier |
mmorgan: If that setting is left Unset, I'm guessing 'lost' is the default status the item gets? |
| 12:45 |
|
beanjammin joined #evergreen |
| 12:45 |
mmorgan |
Part of the missing pieces process renews the item or re-checks it out to the last patron. To get it in transit, you have to check it in, and it gets the transit records the copy_status as "Reshelving" |
| 12:45 |
mmorgan |
kmlussier: If it's unset, the item gets "Damaged" |
| 12:46 |
kmlussier |
Oh, ok. Well then that doesn't make sense at all. :) |
| 12:49 |
* kmlussier |
might call that a bug. |
| 12:59 |
ngf42 |
happy pi day, #evergreen :-) https://i.imgur.com/Ph7flFx.gif |
| 13:00 |
|
rlefaive joined #evergreen |
| 13:08 |
jeff |
while we've adjusted things locally with regard to missing pieces, i'm fairly certain that we avoid this specific issue by not marking it missing pieces until it arrives at its transit destination. |
| 13:10 |
abneiman |
mmorgan: Tina Ji drafted a good potential (future) workflow for handling complexities with missing pieces -- see comment #4 on bug 1257910 |
| 13:10 |
pinesol_green |
Launchpad bug 1257910 in Evergreen " Errors on marking item as missing pieces" [Undecided,Confirmed] https://launchpad.net/bugs/1257910 |
| 13:11 |
mmorgan |
jeff: So how do staff at the transit source generally communicate the issue to the destination? |
| 13:12 |
jeff |
mmorgan: i have some theories, but I'll ask and let you know. |
| 13:12 |
* mmorgan |
takes a look at the bug |
| 13:12 |
mmorgan |
:) |
| 13:17 |
jeff |
mmorgan: we inspect, if there are missing pieces we place a physical note on the item and check in to place the item in transit. receiving library then marks it missing pieces when they get it. |
| 13:18 |
jeff |
mmorgan: some libraries don't inspect our items and we know that so we inspect them when we receive them. |
| 13:18 |
kmlussier |
If I clear all of my browser local storage for an Evergreen server, I find that I have trouble trying to log back in again. Initially, it makes me register a workstation, which I understand. But when I then return to the login page, I get a white screen. I'm wondering if anyone else has seen this or is it just me? |
| 13:18 |
jeff |
mmorgan: i'm not sure if we re-inspect all items or just those from libs that we already don't expect to inspect. |
| 13:19 |
Dyrcona |
kmlussier: Chrome? I cleared everything in Firefox recently, and things worked as if I was connecting brand new. |
| 13:19 |
kmlussier |
Workflows that require pen and paper make me sad. |
| 13:19 |
jeff |
mmorgan: and the open question i have is how we handle missing pieces items that aren't going home for reshelving but are being captured for a hold. |
| 13:19 |
kmlussier |
Dyrcona: Yes, Chrome. |
| 13:19 |
Dyrcona |
kmlussier: Did you also clear the IndexedDB? |
| 13:19 |
kmlussier |
Dyrcona: When I couldn't get past the blank screen, yes, I then cleared IndexedDB. Still no luck. |
| 13:20 |
jeff |
kmlussier: probably a slip (laminated or no) and no pen, and a rubber band, but I think I get your sentiment. :-) |
| 13:20 |
Dyrcona |
I haven't seen that, but I use Chromium and so have different issues. :) |
| 13:20 |
kmlussier |
Possibly unhandled rejection: undefined for vendor.bundle.js shows in the Console. |
| 13:21 |
Dyrcona |
Hm... Haven't seen that, either. |
| 13:21 |
Dyrcona |
I cleared Chromium for one of my VMs recently, too. It still worked. |
| 13:21 |
kmlussier |
Rejection makes me sad. |
| 13:21 |
mmorgan |
jeff: methinks items with missing pieces should be sent home rather than sent to fill a hold. Maybe retarget the hold? |
| 13:21 |
Dyrcona |
:) |
| 13:21 |
jeff |
kmlussier: the missing pieces workflow used to be many pens and many papers and many manual phone calls. i'll be re-visiting what we have experimented with locally as we move toward webby being widespread. |
| 13:22 |
jeff |
mmorgan: likely something like mark damaged + retarget, then check in to return home where it will then be marked missing pieces. |
| 13:22 |
Dyrcona |
kmlussier: I'm building a new branch based on 3.0 today. I'll clear the settings for that vm and see what happens in Chromium, but your problem may be specific to master. |
| 13:23 |
kmlussier |
Dyrcona: Possibly. |
| 13:24 |
* mmorgan |
had not thought of marking damaged as a first step for items with missing pieces that need to go home. That has possibilities. |
| 13:25 |
kmlussier |
mmorgan: The next status alert could work, but, IIRC, there were still potential issues with holds. Because it's likely the hold would be captured before you added that Next Status alert. |
| 13:27 |
mmorgan |
kmlussier: okay, will keep that in mind. |
| 13:27 |
* mmorgan |
has a few things to explore now. Thanks for the input! |
| 13:27 |
mmorgan |
jeff++ |
| 13:27 |
mmorgan |
abneiman++ |
| 13:27 |
mmorgan |
kmlussier++ |
| 13:34 |
|
beanjammin joined #evergreen |
| 13:37 |
berick |
pinesol_green: entertain me while LP is busted |
| 13:37 |
pinesol_green |
berick: git diff origin/hamster |
| 13:37 |
berick |
thanks, i needed that |
| 13:40 |
Dyrcona |
@who wants to commit the hamster branch |
| 13:40 |
pinesol_green |
dbwells wants to commit the hamster branch. |
| 13:40 |
mmorgan |
:) |
| 13:42 |
* dbwells |
did have a killer Habitrail setup as a kid |
| 13:47 |
Dyrcona |
:) |
| 13:49 |
|
abowling1 joined #evergreen |
| 14:16 |
berick |
dbwells++ |
| 14:25 |
csharp |
still not sure what fixes the npm issue (this time on npm 3.10.10/node 6.11.3), but something between 'npm rebuild', 'npm update', then 'npm install' before 'npm run build-prod' does it |
| 14:25 |
csharp |
'npm rebuild' on its own didn't do it |
| 14:55 |
|
rlefaive joined #evergreen |
| 15:05 |
|
yboston joined #evergreen |
| 15:08 |
|
abowling joined #evergreen |
| 15:34 |
kmlussier |
For the logs (and for myself when I most likely do this again at some future date), the issue I encountered earlier occurred because I cleared local storage while still logged in. Once I removed eg.auth.time and eg.auth.token from my cookies, I got the login screen. |
| 15:35 |
kmlussier |
mmorgan figured it out. |
| 15:35 |
kmlussier |
mmorgan++ |
| 15:36 |
Dyrcona |
mmorgan++ |
| 15:37 |
Dyrcona |
kmlussier++ # Teachable moment. :) |
| 15:37 |
* kmlussier |
now tries to remember what she wanted to test that required the removal of local storage. :) |
| 15:39 |
mmorgan |
rabbit-holes-- |
| 15:46 |
|
collum joined #evergreen |
| 16:00 |
kmlussier |
dbwells: Are you okay with me treating bug 1691263 as a bug fix? |
| 16:00 |
pinesol_green |
Launchpad bug 1691263 in Evergreen "webclient wishlist: wrap long fields in MARC editor" [Medium,Confirmed] https://launchpad.net/bugs/1691263 |
| 16:18 |
dbwells |
kmlussier: please do! |
| 16:18 |
kmlussier |
dbwells: Thanks! |
| 16:47 |
pinesol_green |
[evergreen|Cesar Velez] LP#1691263: make webstaff MARC editor wrap long fields - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=11cbc1f> |
| 16:47 |
pinesol_green |
[evergreen|Galen Charlton] LP#1691263: discourage input of newlines in MARC editor - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=5a5d759> |
| 16:54 |
|
Dyrcona joined #evergreen |
| 17:05 |
|
mmorgan left #evergreen |
| 17:24 |
|
jvwoolf left #evergreen |
| 17:26 |
Bmagic |
I'm struggling to figure this out. I am getting an error with xul on oils_rpt_folder_window.js. The console reports TypeError: res is null on line 513. EG 2.12.7 stock. This only occurs when opening report template folders with greater than 68 listings. |
| 17:26 |
Bmagic |
I have moved some reports from folder to folder, reducing the number from 250 listings down to 68 and then it starts working. So it has something to do with the volume of data |
| 17:30 |
Bmagic |
The final line on the logs when it works is "POST /osrf-gateway-v1 HTTP/1.1" 200 523375 |
| 17:30 |
Bmagic |
compared to when it fails: "POST /osrf-gateway-v1 HTTP/1.1" 200 491 |
| 17:30 |
dbwells |
Bmagic: Are you sure it wasn't a problem with report #69, whatever it was? |
| 17:31 |
Bmagic |
I had that thought too. I am moving the reports around using a DB query with limit 5. Not sure it's picking the same 5 every time |
| 17:34 |
csharp |
we're seeing a white screen of death on Firefox and "cannot connect to offline db" in the console - I'm assuming that's referring to the "offline" Indexed DB right? |
| 17:34 |
csharp |
anyone had to troubleshoot that before? |
| 17:36 |
Bmagic |
csharp: doesn't ring a bell |
| 17:36 |
Bmagic |
does it matter where you navigate? |
| 17:37 |
csharp |
not sure - I'm troubleshooting from a distance (I'm at home - terran is in the office with the issue) |
| 17:37 |
csharp |
I'll know more tomorrow |
| 17:38 |
csharp |
terran deleted the offline DB and it works now |
| 17:38 |
terran |
I just deleted the offline db and it got rid of the white screen. |
| 17:38 |
csharp |
jinx |
| 17:38 |
terran |
jinx |
| 17:38 |
terran |
Damn it! |
| 17:38 |
csharp |
heh |
| 17:38 |
* csharp |
is too far away to punch terran's arm |
| 17:40 |
terran |
small blessings |
| 17:41 |
|
abowling1 joined #evergreen |
| 17:41 |
terran |
* terran tries to figure out how to include this in troubleshooting guidelines for the libraries |
| 17:42 |
Bmagic |
"Press F12, then navigate to "Application" and sometimes that is hidden behind double arrows... then click.. and then.... oh hell, just forget it!" |
| 17:42 |
Bmagic |
dbwells: I found the error message in gateway.log |
| 17:42 |
Bmagic |
dbwells: It's a timeout threshold being hit |
| 17:43 |
Bmagic |
Returning NULL from app_request_recv after timeout: open-ils.reporter.folder_data.retrieve |
| 17:44 |
csharp |
Bmagic: exactly (re instructions) |
| 17:44 |
Bmagic |
dbwells: perhaps I just need to expand a timeout threshold somewhere. opensrr_core.xml ? |
| 17:44 |
dbwells |
Bmagic: is this still the "show all is a white screen" problem you were looking a few days ago? |
| 17:44 |
dbwells |
Well, not white screen, but you know what I mean. |
| 17:45 |
Bmagic |
csharp: yeah, been there man! "Did you say EF twelve? What is that?" |
| 17:45 |
Bmagic |
dbwells: yeah, the report template never loads |
| 17:45 |
Bmagic |
template folder* |
| 17:45 |
Bmagic |
if you can isolate the interaction on a test machine, I found the error hiding in gateway.log |
| 17:49 |
Bmagic |
I might have tracked the line down in osrf_app_session.c |
| 17:51 |
dbwells |
Bmagic: I think as berick indicated, that timeout could still be an upstream symptom, not the actual problem. The default timeouts are pretty long, but for whatever reason that interface dies pretty quickly, so the timeout could be just an eventual giving up after not knowing the other end died. I am interested to see how it all works out. |
| 17:54 |
Bmagic |
dbwells: it looks like it might be getting the config from whatever this returns apacheGetFirstParamValue |
| 17:54 |
kmlussier |
terran / csharp: It would be good to nail down why that problem occurs so that users don't have to figure out how to delete Indexed DB. |
| 17:55 |
kmlussier |
Having said that, it probably isn't easy to nail down that issue. |
| 17:55 |
Bmagic |
well, maybe not, it should have been reported in the logs osrfLogDebug(OSRF_LOG_MARK, "Client supplied timeout of %d", timeout); |
| 17:55 |
csharp |
kmlussier: yeah - it's intermittent |
| 17:56 |
csharp |
I barely use the web client as an end user, so I have to depend on my colleagues for this kind of thing |
| 17:57 |
terran |
I've encountered the white screen numerous times on both firefox and chrome, but this is the first time I've head to delete that database. Clearing cookies has resolved the problem every other time. |
| 17:57 |
Dyrcona |
Bmagic: Have you gotten the Overdrive integration to work? |
| 17:57 |
Bmagic |
Dyrcona: Havn't tried since November |
| 17:57 |
Bmagic |
sorry :( - I saw you talkkng about it |
| 17:58 |
Dyrcona |
OK. I'm having a heckuva time and Overdrive support hasn't been that helpful. They mostly just point me at their documentation. |
| 17:58 |
Dyrcona |
I really didn't want to have to learn the code, but looks like I have no choice. |
| 17:58 |
kmlussier |
csharp / terran: I've encountered it before, but I *think* the times I've encountered it is on test systems where I've replaced a stock Concerto VM with a totally different database with different OUs. It's not likely to occur in everyday use. |
| 17:58 |
Bmagic |
Dyrcona: I do have some information that may or may not be useful. At one point I found something in the logs that suggested that we are asking their API a bad question |
| 17:59 |
Dyrcona |
Doesn't help that the official documentation disagrees with some of the things that their dev is telling me. |
| 17:59 |
Bmagic |
I will have to dig it out of my email. Tomorrow if you don't mind? |
| 17:59 |
Dyrcona |
Bmagic: Well, I've seen similar log messages. I'll look into it more tomorrow. |
| 18:00 |
Dyrcona |
I think it is a question of my getting the endpoint for circulation correct, they list 2 in their docs, and making sure the patron oauth is happening correctly. |
| 18:00 |
* kmlussier |
diverts her attention to see if she can catch glimpses of her son on the local news. |
| 18:00 |
terran |
kmlussier: every white screen I've gotten has been on production |
| 18:00 |
terran |
kmlussier: news??? |
| 18:00 |
kmlussier |
terran: walkout |
| 18:01 |
Bmagic |
right on! |
| 18:01 |
terran |
kmlussier: good boy! |
| 18:01 |
Bmagic |
Dyrcona: I did get it working as far as availability. And I walked though placing a hold in the EG OPAC which was pretty cool |
| 18:01 |
csharp |
my son walked out today too |
| 18:02 |
csharp |
not on the news though, I think they were probably at the capitol |
| 18:02 |
Dyrcona |
walked out? gun violence protest? |
| 18:02 |
csharp |
Dyrcona: yeah |
| 18:05 |
Dyrcona |
Bmagic: I had it showing availability, and I *think* I had it showing something that I had checked out through their testing site, but I've made changes since then. |
| 18:07 |
|
abowling joined #evergreen |
| 18:10 |
kmlussier |
terran: I wonder if it's the auth cookies that fixed it for you when it previously happened. That's what I found today. I deleted local storage while still logged in, and it resulted in a white screen. I had to delete the cookies related to authentication to fix it. |
| 18:10 |
* kmlussier |
imagines closing and opening the browser would have worked too. |
| 18:13 |
terran |
kmlussier: that could be |
| 18:14 |
terran |
(but still doesn't explain what caused it) |
| 18:26 |
jeffdavis |
Dyrcona: I'm about to sign off but feel free to bug me tomorrow about Overdrive stuff if you want |
| 18:31 |
pinesol_green |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live> |
| 18:40 |
dbwells |
Bmagic: Give this a whirl when you get a chance. Works for me! http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/dbwells/stream_reporter_retreive_by_folder |
| 18:53 |
|
beanjammin joined #evergreen |
