A new request with request id 9868 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :

Title : Koha-devel Digest, Vol 198, Issue 12
Category :
Description :
Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Re: dbic --force (Marcel de Rooy)
2. Re: dbic --force (Renvoize, Martin)
3. Zebra hot tip #2047 : memMax (dcook@prosentient.com.au)


----------------------------------------------------------------------

Message: 1
Date: Tue, 17 May 2022 11:14:16 +0000
From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>
To: Tomas Cohen Arazi <tomascohen@gmail.com>, koha-devel
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] dbic --force
Message-ID:
    <AS8PR05MB8710E9419DC936C98014C34DCECE9@AS8PR05MB8710.eurprd05.prod.outlook.com>
    
Content-Type: text/plain; charset="utf-8"

And what does it actually force ? 🙂

Marcel

________________________________
Van: Koha-devel <koha-devel-bounces@lists.koha-community.org> namens Tomas Cohen Arazi <tomascohen@gmail.com>
Verzonden: maandag 16 mei 2022 20:19
Aan: koha-devel <koha-devel@lists.koha-community.org>
Onderwerp: [Koha-devel] dbic --force

Just so you know and because these things frequently go unadvertised: we now have a --force switch in KTD for the `dbic` command.

Enjoy.

--
Tomás Cohen Arazi
Theke Solutions (http://theke.io<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftheke.io%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Ccd86d86ef3d24c018ce408da3768b3a7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637883220385042764%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=wOHM4Ans8pxZ98Vn90Vs1yl7ef7%2F%2BQDzNqupswPvEjI%3D&reserved=0>)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220517/fb11846a/attachment-0001.htm>

------------------------------

Message: 2
Date: Tue, 17 May 2022 23:09:10 +0100
From: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com>
To: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>
Cc: Tomas Cohen Arazi <tomascohen@gmail.com>, koha-devel
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] dbic --force
Message-ID:
    <CAB7SL8DTrRFm2Xk957kmzjPB8hQ44RmAiS=t-wnFVcMXmnbFAA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

It's the same as the force option I introduced in the core script a while
back.

In short, it allows a force refresh of the dbic generated classes, above
the hash.. even if the hash doesn't match what was expected.

It's really useful, but should be used with care. As we have git control,
it should be trivial to diff the output and spot unexpected changes above
the fold.

On Tue, 17 May 2022, 12:14 pm Marcel de Rooy, <M.de.Rooy@rijksmuseum.nl>
wrote:

> And what does it actually force ? 🙂
>
> Marcel
>
> ------------------------------
> *Van:* Koha-devel <koha-devel-bounces@lists.koha-community.org> namens
> Tomas Cohen Arazi <tomascohen@gmail.com>
> *Verzonden:* maandag 16 mei 2022 20:19
> *Aan:* koha-devel <koha-devel@lists.koha-community.org>
> *Onderwerp:* [Koha-devel] dbic --force
>
> Just so you know and because these things frequently go unadvertised: we
> now have a --force switch in KTD for the `dbic` command.
>
> Enjoy.
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io
> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftheke.io%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Ccd86d86ef3d24c018ce408da3768b3a7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637883220385042764%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=wOHM4Ans8pxZ98Vn90Vs1yl7ef7%2F%2BQDzNqupswPvEjI%3D&reserved=0>
> )
> ✆ +54 9351 3513384
> GPG: B2F3C15F
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220517/57efbdc4/attachment-0001.htm>

------------------------------

Message: 3
Date: Wed, 18 May 2022 15:20:17 +1000
From: <dcook@prosentient.com.au>
To: "'Koha-devel'" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Zebra hot tip #2047 : memMax
Message-ID: <071601d86a76$faa3e5c0$efebb140$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Hi all,



While trying to tune Zebra for a large Koha library, I ran into some
problems when throwing memory at the memMax configuration option.



While the documentation says it can use up to half the memory on your
system, I've discovered the practical limit is actually 2047MB.



Why 2047MB? It's because memMax gets puts into a variable with an "int" data
type which is a signed 32 bit integer. If you get to 2048MB or over, you'll
end up with invalid values that cause memory allocation issues and your
indexing will fail.



I've raised an issue with Indexdata to either switch to an unsigned 32 bit
integer, switch to a 64 bit integer, or at least add some error checking:
https://github.com/indexdata/idzebra/issues/34



But I figured I'd share my little discovery with y'all in the meantime.



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220518/d0a96e25/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


------------------------------

End of Koha-devel Digest, Vol 198, Issue 12
*******************************************


NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.