| Time |
S |
Nick |
Message |
| 03:11 |
|
|
matts_ joined #koha |
| 04:49 |
|
|
MarkHofstetter1 joined #koha |
| 05:03 |
|
|
chriss joined #koha |
| 05:56 |
|
|
Noor_ joined #koha |
| 05:59 |
|
Noor_ |
hello there, we are using KOHA 20.05, the reports module is acting strangely. Most of the saved reports are running fine, however, 1 report shows error "This site can’t be reached The connection was reset.". Whenever we try to create a new report and save it, the same error is shown. Kindly advise how to fix this issue |
| 06:01 |
|
Noor_ |
similar error also comes when we try to edit and update any pre-existing report |
| 06:19 |
|
|
marcelr joined #koha |
| 06:19 |
|
marcelr |
hi #koha |
| 06:31 |
|
Joubu |
oleonard: make them depend on 28376 |
| 06:32 |
|
Joubu |
Noor_: did you ask yesterday already? |
| 06:43 |
|
Noor_ |
yes, my colleague asked this question joubu, and your response was to upgrade koha, which may not be possible for us this time. So i have reposted the question again |
| 06:46 |
|
Joubu |
Are you self-hosted? |
| 06:51 |
|
|
alex_a joined #koha |
| 06:51 |
|
alex_a |
Bonjour |
| 06:55 |
|
|
cait joined #koha |
| 06:56 |
|
|
cait1 joined #koha |
| 07:04 |
|
|
lds joined #koha |
| 07:05 |
|
cait1 |
good morning #koha |
| 07:07 |
|
marcelr |
hi cait1 |
| 07:17 |
|
cait1 |
hi marcelr |
| 07:24 |
|
magnuse |
\o/ |
| 08:16 |
|
ashimema |
morning |
| 08:16 |
|
ashimema |
cait1 |
| 08:17 |
|
cait1 |
video conf |
| 08:21 |
|
Noor_ |
yes joubu, self hosted |
| 08:21 |
|
Noor_ |
we have an IT department who manages all servers and applications |
| 08:22 |
|
Joubu |
did you ask them? |
| 08:23 |
|
Noor_ |
yes, unfortunately, they are also unable to figure out this issue |
| 08:23 |
|
Joubu |
I don't think we could help them much |
| 08:24 |
|
Joubu |
Fridolin made you/your colleague a suggestion yesterday, maybe there is a proxy that is filtering request with SQL query in their parameters |
| 08:25 |
|
Joubu |
tell that to your IT team |
| 08:44 |
|
Noor_ |
if proxy may have been an issue, why its running rest of the reports? |
| 08:48 |
|
cait1 |
I missed the beginning... which report is failing? |
| 08:52 |
|
Noor_ |
Hi cait1, the accession register report or any saved reports when i edit or create a new report, the following error "This site can’t be reached The connection was reset." is coming. Interestingly all reports except one reports are running |
| 08:53 |
|
cait1 |
hm ok, don't have any new ideas there I am afraid |
| 08:53 |
|
Noor_ |
no problem cait1:) |
| 08:56 |
|
Joubu |
what's the difference between one report that run and another that does not run? |
| 09:27 |
|
marcelr |
ashimema++ for struggling thru 28883 |
| 09:32 |
|
ashimema |
I keep flip flopping.. I'm really not sure which way to jump here |
| 09:33 |
|
ashimema |
consistency is good.. this bug highlights a pretty massive inconsistency in our code which I've hit before but never had the brain power to fully understand |
| 09:33 |
|
ashimema |
now I understand it.. I'm stuck as to which direction we should aim for consistency wise |
| 09:34 |
|
ashimema |
do context magic on the initial returns as this bug does.. or always return an interator and have as_list to get the array context when needed.. |
| 09:34 |
|
ashimema |
I think I'm slowly coming round to that.. |
| 09:34 |
|
ashimema |
but.. |
| 09:34 |
|
ashimema |
those are huge changes codebase wide |
| 09:35 |
|
ashimema |
it's either introduce lots of uses of Context.Scalar in our templates |
| 09:35 |
|
ashimema |
or drop Context.Scalar entirely and introduce .as_list in a bunch of cases in our templates instead |
| 09:38 |
|
ashimema |
the alternative is to drop Context.Scalar but introduce an _ko or _rs method for each of the relationship accessors we add to any Koha::Object class |
| 09:38 |
|
ashimema |
_ko = koha object, _rs = resultset (the dbic term) |
| 09:41 |
|
marcelr |
sounds easier to only solve a few cases ? |
| 09:43 |
|
ashimema |
problem is.. the cases aren't easy to spot |
| 09:43 |
|
ashimema |
the client just explodes with a 500 if you get it wrong |
| 09:44 |
|
ashimema |
I've found a few already.. but it's not a simple search of the codebase to find them.. we don't have consistency in our relationship names |
| 09:44 |
|
ashimema |
which is totally understandable. |
| 09:44 |
|
ashimema |
but yeah |
| 10:06 |
|
oleonard |
Hi all |
| 10:11 |
|
huginn |
News from kohagit: Bug 28938: Correct Flatpickr's default 12hr time formatting <https://git.koha-community.org[…]48520715c29452f96> |
| 10:11 |
|
huginn |
News from kohagit: Bug 28928: Minor follow-ups to Bug 28376 - Flatpickr introduction <https://git.koha-community.org[…]8d31f9ee1e6089e40> |
| 10:11 |
|
huginn |
News from kohagit: Bug 20529: Remove other occurrences of decodeURIComponent from browser.js <https://git.koha-community.org[…]aa33d98b87a14e746> |
| 10:11 |
|
huginn |
News from kohagit: Bug 20529: Fix "Return to results" link broken by a double quote <https://git.koha-community.org[…]4ee172b9c09d474f0> |
| 10:23 |
|
Noor_ |
Joubu, the report was running 10 days ago, but now its given this error, and the system prevents creation of new reports as well |
| 10:24 |
|
Joubu |
try to create a new report from SQL (not a guided report) with the following content: SELECT COUNT(*) FROM biblio; |
| 10:24 |
|
Joubu |
and try to run it |
| 10:29 |
|
Noor_ |
okay let me do it now |
| 10:30 |
|
Noor_ |
it has saved the report and i was able to run it :) |
| 10:31 |
|
|
Oak joined #koha |
| 10:34 |
|
Joubu |
so what's the one that does not run? Can you paste the content somwhere? |
| 10:35 |
|
Noor_ |
let me copy SQL code and share it here |
| 10:35 |
|
Noor_ |
This is the SQL code of the report which is giving connection was reset error |
| 10:35 |
|
Noor_ |
SELECT items.dateaccessioned,items.barcode,items.itemcallnumber,biblio.author,biblio.title,biblioitems.publishercode,biblioitems.isbn, (SELECT ExtractValue(biblio_metadata.metadata,'//datafield[@tag="650"][1]/subfield[@code="a"]')) AS 'subject heading 1', (SELECT ExtractValue(biblio_metadata.metadata,'//datafield[@tag="650"][2]/subfield[@code="a"]')) AS 'subject heading 2', (SELECT ExtractValue(biblio_metadata.metadata,'//datafield[@tag="650"][3]/subfield[@co |
| 10:36 |
|
Joubu |
because it's taking too much time to finish maybe |
| 10:37 |
|
Joubu |
http://paste.koha-community.org/ |
| 10:37 |
|
Noor_ |
how can i share the full SQL Code with you |
| 10:37 |
|
Joubu |
paste the full query there |
| 10:37 |
|
Joubu |
lunch time here, see you later |
| 10:37 |
|
Noor_ |
Oh okay |
| 10:37 |
|
Noor_ |
Thanks for all your support |
| 10:37 |
|
Noor_ |
and help |
| 10:38 |
|
Noor_ |
i will also get busy in an online session for two hours |
| 10:38 |
|
Noor_ |
will catch you later |
| 10:50 |
|
koha-jenkins |
Project Koha_Master build #1747: FAILURE in 35 min: https://jenkins.koha-community[…]Koha_Master/1747/ |
| 10:52 |
|
koha-jenkins |
Project Koha_Master_D9 build #1757: STILL UNSTABLE in 38 min: https://jenkins.koha-community[…]a_Master_D9/1757/ |
| 10:55 |
|
koha-jenkins |
Project Koha_Master_D10_MDB_Latest build #683: STILL UNSTABLE in 42 min: https://jenkins.koha-community[…]0_MDB_Latest/683/ |
| 10:56 |
|
|
cait joined #koha |
| 11:08 |
|
koha-jenkins |
Project Koha_Master_U_Stable build #250: STILL UNSTABLE in 56 min: https://jenkins.koha-community[…]ter_U_Stable/250/ |
| 11:09 |
|
koha-jenkins |
Project Koha_Master_U20 build #185: STILL UNSTABLE in 55 min: https://jenkins.koha-community[…]a_Master_U20/185/ |
| 11:18 |
|
koha-jenkins |
Project Koha_Master_D10_CPAN build #424: STILL UNSTABLE in 1 hr 4 min: https://jenkins.koha-community[…]ter_D10_CPAN/424/ |
| 11:35 |
|
koha-jenkins |
Project Koha_Master_D11 build #383: STILL UNSTABLE in 40 min: https://jenkins.koha-community[…]a_Master_D11/383/ |
| 11:49 |
|
koha-jenkins |
Project Koha_Master_D10_My8 build #645: STILL UNSTABLE in 59 min: https://jenkins.koha-community[…]ster_D10_My8/645/ |
| 12:00 |
|
MarkHofstetter1 |
hi, is it/how is it possible to access plugin configuration in the API Controllers of a plugin? |
| 12:03 |
|
koha-jenkins |
Project Koha_Master_D10_MDB_Latest build #684: STILL UNSTABLE in 54 min: https://jenkins.koha-community[…]0_MDB_Latest/684/ |
| 12:05 |
|
|
marcelr joined #koha |
| 12:07 |
|
koha-jenkins |
Project Koha_Master_D11 build #384: STILL UNSTABLE in 31 min: https://jenkins.koha-community[…]a_Master_D11/384/ |
| 12:09 |
|
MarkHofstetter1 |
ok, you can always do $plugin = new Koha::Plugin::Bla; $plugin->retrieve_data('foo'); |
| 12:09 |
|
koha-jenkins |
Project Koha_Master_D9 build #1758: STILL UNSTABLE in 1 hr 0 min: https://jenkins.koha-community[…]a_Master_D9/1758/ |
| 12:20 |
|
magnuse |
oops, did paul_p forward to the wrong address? |
| 12:27 |
|
tcohen |
good morning |
| 12:33 |
|
|
alex_a joined #koha |
| 12:36 |
|
|
marie-luce joined #koha |
| 12:39 |
|
|
Dyrcona joined #koha |
| 12:47 |
|
magnuse |
hola tcohen |
| 12:59 |
|
|
khall joined #koha |
| 13:13 |
|
|
khall_ joined #koha |
| 14:09 |
|
|
oleonard joined #koha |
| 14:13 |
|
marcelr |
what cheese can compensate :) |
| 14:26 |
|
marcelr |
bug 28943 |
| 14:26 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=28943 enhancement, P5 - low, ---, koha-bugs, NEW , cleanup_database: Can we make del-exp-selfreg less disastrous ? |
| 14:26 |
|
oleonard |
Love a good hyperbolic bug title XD |
| 14:29 |
|
marcelr |
Yeah :) |
| 14:30 |
|
marcelr |
But when you accidentally delete almost all your patrons, you might think otherwise? I didnt btw |
| 14:31 |
|
oleonard |
Very true |
| 14:54 |
|
|
kidclamp joined #koha |
| 15:42 |
|
|
cait1 left #koha |
| 15:43 |
|
|
cait joined #koha |
| 17:49 |
|
|
oleonard_ joined #koha |
| 17:49 |
|
oleonard_ |
I too am oleonard |
| 18:33 |
|
oleonard_ |
rangi++ |
| 18:40 |
|
|
khall joined #koha |
| 18:51 |
|
|
khall_ joined #koha |
| 20:06 |
|
|
felicia joined #koha |
| 20:07 |
|
|
abneiman joined #koha |
| 20:07 |
|
|
sallyf joined #koha |
| 20:08 |
|
|
akilsdonk joined #koha |
| 20:08 |
|
|
phasefx joined #koha |
| 20:09 |
|
|
rhamby joined #koha |
| 21:00 |
|
|
alphaman joined #koha |
| 21:00 |
|
|
alphaman left #koha |
| 22:54 |
|
|
tcohen joined #koha |
