| Time |
Nick |
Message |
| 02:16 |
|
tester2 joined #evergreen |
| 02:28 |
|
book` joined #evergreen |
| 04:56 |
|
Rogan joined #evergreen |
| 07:32 |
|
BDorsey joined #evergreen |
| 07:39 |
|
rfrasur joined #evergreen |
| 08:25 |
|
Stompro joined #evergreen |
| 09:01 |
|
bgillap_ joined #evergreen |
| 09:14 |
|
Dyrcona joined #evergreen |
| 09:23 |
|
mantis1 joined #evergreen |
| 09:51 |
|
jvwoolf joined #evergreen |
| 09:53 |
|
sandbergja joined #evergreen |
| 11:07 |
|
BrianK joined #evergreen |
| 11:19 |
|
dguarrac joined #evergreen |
| 12:04 |
|
jihpringle joined #evergreen |
| 12:33 |
mantis1 |
Off topic. Has anyone here used Pheeploop? Would like some thoughts. |
| 12:50 |
jeff |
do you mean PheedLoop, the virtual event (kind of like Hopin) software/platform? |
| 12:51 |
jeff |
(both of those entities would probably object to the comparison) |
| 13:12 |
|
tester2 joined #evergreen |
| 13:33 |
mantis1 |
jeff: yes lol |
| 13:33 |
mantis1 |
spelling errors abound |
| 14:21 |
Dyrcona |
Pheeploop....Blibdoolpoolp's consort? |
| 14:26 |
jonadab |
Yeah, cherry-pick is often easier than rebase. |
| 14:27 |
jonadab |
Though if the code divergence between branches gets profound enough, just looking at how the change works and the rewriting it on the other branch starts to look attractive. |
| 14:31 |
Dyrcona |
I ended up doing some elaborate "scripting" to get the list of files affected by the four relevant commits, then dumped patches of them along with the full contents of the files. There are still some irrelevant changes in the IDL and a few other affected files but it was easier than trying to resolve conflicts that I don't understand. |
| 14:32 |
Dyrcona |
Some stuff I mentioned in my git preconference presentation came in handy. |
| 14:40 |
|
Guest56 joined #evergreen |
| 14:56 |
|
NickG joined #evergreen |
| 14:57 |
NickG |
Hi, anyone that can help me with a permission error? |
| 15:06 |
Dyrcona |
NickG: Just ask you question, if anyone can help, they will. |
| 15:19 |
* Dyrcona |
is getting Launchpad email from yesterday today. Anyone else? |
| 15:22 |
NickG |
Thanks Dyrcona; We worked around it by changing permission level from branch to consortium, however this is what was happening; Went to pay a customers fines and would get a pop-up with the message, " Permission Denied: CREATE_PAYMENT." I've always been able to so it was strange, tried relogging and the same thing would happen after it said the |
| 15:22 |
NickG |
permission override was successful. |
| 15:26 |
|
mantis1 left #evergreen |
| 15:44 |
Dyrcona |
If the patron had fines at another system, Evergreen might have tried to make payments there. I'd have to look into how that works again to be sure. |
| 15:51 |
NickG |
I checked the bill history and it said the item owning library was cedar-eldo, I am at cedar-stockton, that could be it; but I would've thought that would fall under 'branch' in the permission editor? |
| 15:51 |
Dyrcona |
NickG: That would be System if you're using the regular Consortium -> System -> Branch type hierarchy. |
| 15:53 |
NickG |
Okay I see. So in the future should I tell the patron to pay the fine at the library the item was from? |
| 15:54 |
Dyrcona |
It depends on what you want to do. If you give the CREATE_PAYMENT permission at the System level, then they could pay an any branch of the same system. If you do it at Consortium level, then they could pay anywhere. It depends a lot on your local configuration and policies, though, so I can't really make a recommendation without knowing more. |
| 15:55 |
NickG |
Hey that's more info than I expected to get and I appreciate it. Have a good weekend Dyrcona! |
| 15:56 |
Dyrcona |
You, also! |
| 15:57 |
Dyrcona |
Hrm. An API named "renewal" that doesn't actually renew.... |
| 15:58 |
Dyrcona |
It returns information about a patron to be renewed. |
| 16:00 |
Dyrcona |
Naming things is hard. |
| 16:10 |
|
Rogan joined #evergreen |
| 17:09 |
|
jvwoolf left #evergreen |
| 17:50 |
|
Rogan joined #evergreen |
