Time |
Nick |
Message |
06:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
08:14 |
|
kmlussier joined #evergreen |
08:53 |
|
rlefaive joined #evergreen |
09:03 |
|
_adb joined #evergreen |
09:07 |
|
bos20k joined #evergreen |
09:19 |
|
yboston joined #evergreen |
09:29 |
Bmagic |
Anyone else care to address Nidheesh? I was about to ask for some logs |
09:40 |
|
roycroft joined #evergreen |
10:00 |
|
krvmga joined #evergreen |
10:01 |
* csharp |
sees "Greeting from Koha - Invalid Password" alert box in the video Nidheesh attached to the bug |
10:01 |
krvmga |
does anyone know of any issues between the current version of opensrf and python 2.6? |
10:01 |
csharp |
oh - I see - he says that |
10:02 |
csharp |
reading++ |
10:02 |
csharp |
csharp-- |
10:02 |
kmlussier |
"Invalid project name for branch merge: Evergeen" Do you know how long I had to stare at that message before I knew what the problem was? |
10:03 |
csharp |
krvmga: are you trying to use OpenSRF's python bindings? those are super old and probably nonfunctional as far as I know |
10:03 |
jeff |
kmlussier: nice. What tool gives that error? |
10:04 |
krvmga |
csharp: we have syrup running on a machine and upgraded both opensrf and evergreen and now i'm getting Exceptions where i didn't have them before. |
10:04 |
krvmga |
quelle frustrate |
10:04 |
kmlussier |
jeff: It's the script tsbere created to build the build the MassLNC sandboxes. |
10:04 |
jeff |
In general I'd try to avoid Python 2.6 as being ancient itself, but I can make no assertions one way or the other as to its suitability with OpenSRF/Evergreen Python libs. |
10:05 |
kmlussier |
jeff: What version of python do you use with Syrup? |
10:05 |
csharp |
(though it would be great to get them updated since perl is the most hated of all languages: http://www.zdnet.com/article/most-loathed-programming-language-heres-how-developers-cast-their-votes/) |
10:05 |
krvmga |
2.6 |
10:05 |
jeff |
kmlussier: Probably 2.7, but I'll verify. |
10:05 |
krvmga |
kmlussier: we're using 2.6 |
10:05 |
jeff |
Python 2.7.9 |
10:05 |
kmlussier |
krvmga: Yes, I saw you stated that above. |
10:06 |
* csharp |
forgets that syrup exists |
10:06 |
kmlussier |
krvmga: I'm fairly sure NOBLE runs Syrup on an older version of OpenSRF than they do on their Evergreen servers. They also don't install Evergreen on their Syrup server. |
10:06 |
* krvmga |
wishes he could forget it. :) |
10:06 |
* csharp |
pokes a hole in his PINES/public library bubble |
10:07 |
kmlussier |
krvmga: What's the problem? |
10:07 |
krvmga |
Value Error....Exception Value: too many values to unpack when trying to add something from the catalog |
10:07 |
berick |
i'd wager opensrf is the problem instead of python |
10:08 |
|
jvwoolf joined #evergreen |
10:08 |
berick |
it doesn't understand the 2.5-era bundling stuff |
10:09 |
jeff |
We're using OpenSRF 2.4.2 with Syrup. |
10:10 |
jeff |
But I needed to make adjustments to make things work. At least one was a similar exception. |
10:10 |
* jeff |
looks for a branch |
10:12 |
jeff |
we also upgraded to a less decrepit version of Django, I believe. |
10:12 |
jeff |
(by no means current, just less-not-current) |
10:13 |
jeff |
this Syrup instance is running against Evergreen 2.11.x, also. |
10:13 |
krvmga |
jeff: we just upgraded from 2.10 -> 2.12 |
10:13 |
jeff |
Can you paste more of the exception somewhere, or relate which line in which file is triggering it? |
10:14 |
jeff |
Looks like the similar exception I had was related to reverting items, not adding them. I have the diff, but not my commit message handy. |
10:15 |
pastebot |
"krvmga" at 64.57.241.14 pasted "Python error in Syrup" (14 lines) at http://paste.evergreen-ils.org/911 |
10:16 |
|
rlefaive_ joined #evergreen |
10:17 |
jeff |
Ah. I do have a change for that which worked for us. One moment. |
10:18 |
jeff |
hrm. doesn't look like Syrup has a working repo or a clone on github. Guess I'll push one! |
10:20 |
kmlussier |
jeff: Yes, I've previously thought it would be a good idea to have a working repo. I think I had a change once before, and I just e-mailed artunit and asked him to add it for me. A working repo would be nice. |
10:29 |
jeff |
krvmga: this was how we approached that issue, I believe: https://github.com/tadl/Syrup/commit/6f8283e231214384a9dd3b0bd53b67aca1973a4e |
10:34 |
csharp |
jeff++ |
10:35 |
kmlussier |
jeff++ |
10:38 |
krvmga |
jeff++ |
10:59 |
Bmagic |
berick: I have an EDI vendor that wants to change "NAD|SU|9::92" TO: "NAD|BY|XXXXXX:91" - I believe that is a JEDI change? I can't seem to connect the dots from JEDI to EDI message |
11:02 |
berick |
Bmagic: which message type? |
11:03 |
Bmagic |
order |
11:07 |
berick |
Bmagic: yes, JEDI template change. buyer id-qualifier |
11:08 |
|
rlefaive joined #evergreen |
11:08 |
berick |
Bmagic: beware this would require changing the new EDIWriter code when/if you move to that. It doesn't have a toggle for buyer 91 vs 92. It assumes 92. |
11:08 |
berick |
first i've heard of a vendor requiring that |
11:09 |
Bmagic |
yeah, strange |
11:09 |
Bmagic |
Currently, our Order EDI spits out nothing between the colons on the NAD+SU....92 clause |
11:11 |
berick |
it should spit out org unit san and vendcode or vendacct |
11:13 |
Bmagic |
"vendor":[ "XXXXXXX", {"id-qualifier": 92, "id":"9"} ], |
11:13 |
Bmagic |
that is in action_trigger.event_output |
11:13 |
Bmagic |
I suppose it does spit out "9" - but they want it to be NAD+BY instead of NAD+SU |
11:16 |
berick |
oops, nad+su should show the seller internal ID, not the SAN, etc. I mentioned above. |
11:16 |
berick |
the san, etc. is part of nad+by |
11:17 |
berick |
well, arg, it does include the vendor san (the xx's) |
11:17 |
berick |
i don't think i'm helping at this point :) |
11:17 |
berick |
just causing confusion |
11:18 |
Bmagic |
lol |
11:21 |
Bmagic |
berick: ok, so which clause in JEDI makes the NAD+SU ? |
11:22 |
|
rlefaive joined #evergreen |
11:23 |
Bmagic |
vendor":[ "XXXXXXX", {"id-qualifier": 92, "id":"9"} ], CREATED "NAD+SU+9::92'" ? Why didn't it put XXXXX in there? Instead I have another clause in my EDI that looks like this: NAD+SU+XXXXXX::31B' |
11:23 |
|
Christineb joined #evergreen |
11:24 |
csharp |
@decide The Last Jedi or The Last PO JEDI |
11:24 |
pinesol_green |
csharp: go with The Last Jedi |
11:24 |
Bmagic |
@loves JEDI |
11:24 |
pinesol_green |
Bmagic: JEDI doesn't seem to love anything. |
11:24 |
Bmagic |
ha, wrong syntax but still funny |
11:25 |
* berick |
chuckles |
11:25 |
berick |
Bmagic: XXXX is the seller's SAN (not the org unit san)? |
11:25 |
csharp |
@quote add < pinesol_green> JEDI doesn't seem to love anything. |
11:25 |
pinesol_green |
csharp: The operation succeeded. Quote #181 added. |
11:25 |
berick |
acq.provider.san |
11:26 |
Bmagic |
berick: yes, that is the seller san |
11:27 |
csharp |
so... bringing my guitar to the hackaway... worth it, you think? |
11:27 |
Bmagic |
csharp: YES |
11:27 |
csharp |
ok - will do |
11:27 |
Bmagic |
charp: Are you driving? If not, maybe we could rent one |
11:27 |
csharp |
Bmagic: flying - but I'm willing to check it |
11:28 |
Bmagic |
I'm down |
11:30 |
|
jvwoolf joined #evergreen |
11:30 |
berick |
Bmagic: if you want NAD+SU+XXXXX::92 -- try modifying the "vendor" chunk. replace target.provider.id with VENDOR_SAN. |
11:30 |
berick |
and wrap it in a IF VENDOR == test |
11:31 |
berick |
or rather IF VENDOR_FOO test |
11:31 |
Bmagic |
ok, I was coming to the same conclusion... except they want it to be 91 and not 92 |
11:31 |
berick |
then change the id-qualifier |
11:31 |
berick |
too |
11:32 |
Bmagic |
I am stumbling because NAD+SU+XXXXXX::31B != NAD+SU+9::92 Two different EDI clauses that I can't connect to the JEDI exactly |
11:33 |
berick |
Bmagic: the 31B may be coming from the "recipient" attribute. |
11:33 |
berick |
i forget |
11:34 |
Bmagic |
I think you gave me something to play with anyway! I really appreciate your time |
11:34 |
Bmagic |
berick++ |
11:51 |
|
khuckins joined #evergreen |
11:55 |
|
sandbergja joined #evergreen |
12:19 |
|
rlefaive joined #evergreen |
12:47 |
|
jihpringle joined #evergreen |
12:49 |
|
khuckins_ joined #evergreen |
13:04 |
|
hbrennan joined #evergreen |
13:21 |
Bmagic |
berick: it turned out they could live with the message formatted the same as we do for BT - IF target.provider.edi_default.vendcode && (target.provider.code == 'BT' || target.provider.name.match('(?i)^BAKER & TAYLOR') |
13:22 |
Bmagic |
berick: so I added one more on the end there || target.provider.name.match('(?i)^Vendor') |
13:27 |
berick |
Bmagic: oh good, that'll work fine w/ the new edi stuff |
13:28 |
|
khuckins__ joined #evergreen |
13:39 |
miker |
Bmagic: can you share the vendor so other customers might be able to avoid your pain? |
13:40 |
miker |
customers of [Vendor], I mean (perhaps obv) |
15:29 |
Bmagic |
miker: oh sure, it's Recorded Books |
15:48 |
|
Dyrcona joined #evergreen |
16:19 |
|
Jillianne joined #evergreen |
16:51 |
kmlussier |
Wheee! I guess I know what I'll be testing next week. :) |
16:51 |
kmlussier |
gmcharlt++ |
16:56 |
gmcharlt |
kmlussier: stuff, I'm sure |
16:56 |
gmcharlt |
and things |
16:56 |
gmcharlt |
;) |
16:57 |
kmlussier |
gmcharlt: A week ago, I had no plans for what I was going to work on at the hack-a-way. Now I have a big long list that will require me to stay there for 2 weeks. |
16:58 |
gmcharlt |
same |
17:08 |
|
jvwoolf left #evergreen |
18:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |