pike issueshttps://git.lysator.liu.se/pikelang/pike/-/issues2018-05-03T07:21:29Zhttps://git.lysator.liu.se/pikelang/pike/-/issues/8087Former QA task of PIKE-84 (#8084). See it for details.2018-05-03T07:21:29ZPeter BortasFormer QA task of PIKE-84 (#8084). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-87
Reported by Roxen Scrum Team <roxenscrumteam@roxen.com>
Blocking [PIKE-84](#8084)Imported from https://youtrack.roxen.com/issue/PIKE-87
Reported by Roxen Scrum Team <roxenscrumteam@roxen.com>
Blocking [PIKE-84](#8084)https://git.lysator.liu.se/pikelang/pike/-/issues/8086Former Fix task of PIKE-84 (#8084). See it for details.2018-05-02T14:55:13ZPeter BortasFormer Fix task of PIKE-84 (#8084). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-86
Reported by Roxen Scrum Team <roxenscrumteam@roxen.com>
Blocking [PIKE-84](#8084)Imported from https://youtrack.roxen.com/issue/PIKE-86
Reported by Roxen Scrum Team <roxenscrumteam@roxen.com>
Blocking [PIKE-84](#8084)https://git.lysator.liu.se/pikelang/pike/-/issues/8085Former Investigate task of PIKE-84 (#8084). See it for details.2018-05-02T14:53:49ZPeter BortasFormer Investigate task of PIKE-84 (#8084). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-85
Reported by Roxen Scrum Team <roxenscrumteam@roxen.com>
Blocking [PIKE-84](#8084)Imported from https://youtrack.roxen.com/issue/PIKE-85
Reported by Roxen Scrum Team <roxenscrumteam@roxen.com>
Blocking [PIKE-84](#8084)https://git.lysator.liu.se/pikelang/pike/-/issues/8083Filesystem.Monitor: Fix inotify race conditions2018-04-05T13:23:49ZPeter BortasFilesystem.Monitor: Fix inotify race conditionsImported from https://youtrack.roxen.com/issue/PIKE-83
Reported by Martin Karlgren <marty@roxen.com>Imported from https://youtrack.roxen.com/issue/PIKE-83
Reported by Martin Karlgren <marty@roxen.com>https://git.lysator.liu.se/pikelang/pike/-/issues/8082Former Merge to Pike 8.0. task of PIKE-79 (#8079). See it for details.2018-03-12T11:48:29ZPeter BortasFormer Merge to Pike 8.0. task of PIKE-79 (#8079). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-82
Reported by @grubba
Blocking [PIKE-79](#8079)Imported from https://youtrack.roxen.com/issue/PIKE-82
Reported by @grubba
Blocking [PIKE-79](#8079)https://git.lysator.liu.se/pikelang/pike/-/issues/8081Former QA task of PIKE-79 (#8079). See it for details.2018-03-12T09:16:54ZPeter BortasFormer QA task of PIKE-79 (#8079). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-81
Reported by @grubba
Blocking [PIKE-79](#8079)Imported from https://youtrack.roxen.com/issue/PIKE-81
Reported by @grubba
Blocking [PIKE-79](#8079)https://git.lysator.liu.se/pikelang/pike/-/issues/8080Former Fix task of PIKE-79 (#8079). See it for details.2018-03-01T13:46:11ZPeter BortasFormer Fix task of PIKE-79 (#8079). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-80
Reported by @grubba
Blocking [PIKE-79](#8079)Imported from https://youtrack.roxen.com/issue/PIKE-80
Reported by @grubba
Blocking [PIKE-79](#8079)https://git.lysator.liu.se/pikelang/pike/-/issues/8079Unicode.normalize() in NFC mode is a noop for narrow strings.2020-03-05T17:27:31ZPeter BortasUnicode.normalize() in NFC mode is a noop for narrow strings.Imported from https://youtrack.roxen.com/issue/PIKE-79
Reported by @grubba
Optimize the case where `Unicode.normalize()` is called in *NFC* mode on an 8-bit string.Imported from https://youtrack.roxen.com/issue/PIKE-79
Reported by @grubba
Optimize the case where `Unicode.normalize()` is called in *NFC* mode on an 8-bit string.https://git.lysator.liu.se/pikelang/pike/-/issues/8077Former QA Web.decode_jwt() et al fix. task of PIKE-76 (#8076). See it for det...2018-02-23T10:15:05ZPeter BortasFormer QA Web.decode_jwt() et al fix. task of PIKE-76 (#8076). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-77
Reported by @grubba
Blocking [PIKE-237](#8237)Imported from https://youtrack.roxen.com/issue/PIKE-77
Reported by @grubba
Blocking [PIKE-237](#8237)https://git.lysator.liu.se/pikelang/pike/-/issues/8075Former Revert and fix. task of PIKE-63 (#8063). See it for details.2018-02-13T15:18:57ZPeter BortasFormer Revert and fix. task of PIKE-63 (#8063). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-75
Reported by @grubba
Blocking [PIKE-63](#8063)Imported from https://youtrack.roxen.com/issue/PIKE-75
Reported by @grubba
Blocking [PIKE-63](#8063)https://git.lysator.liu.se/pikelang/pike/-/issues/8074Former Fix task of PIKE-72 (#8072). See it for details.2018-02-13T15:14:32ZPeter BortasFormer Fix task of PIKE-72 (#8072). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-74
Reported by @grubba
Blocking [PIKE-72](#8072)Imported from https://youtrack.roxen.com/issue/PIKE-74
Reported by @grubba
Blocking [PIKE-72](#8072)https://git.lysator.liu.se/pikelang/pike/-/issues/8073Former Investigate task of PIKE-72 (#8072). See it for details.2018-02-13T15:12:34ZPeter BortasFormer Investigate task of PIKE-72 (#8072). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-73
Reported by @grubba
Blocking [PIKE-72](#8072)Imported from https://youtrack.roxen.com/issue/PIKE-73
Reported by @grubba
Blocking [PIKE-72](#8072)https://git.lysator.liu.se/pikelang/pike/-/issues/8072Nettle warning2020-03-05T17:25:40ZPeter BortasNettle warningImported from https://youtrack.roxen.com/issue/PIKE-72
Reported by Marcus Wellhardh <wellhard@roxen.com>
Latest build 6.2.84 gives the following warning:
```
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Not a va...Imported from https://youtrack.roxen.com/issue/PIKE-72
Reported by Marcus Wellhardh <wellhard@roxen.com>
Latest build 6.2.84 gives the following warning:
```
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Not a valid object type.
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Expected: function(void | mixed ... : object) | object | program.
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Got : mixed.
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:532: Warning: Invalid type.
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:532: Warning: Expected: function(void | mixed ... : object) | object | program | type(mixed).
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:532: Warning: Got : mixed.
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:593: Warning: Invalid type.
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:593: Warning: Expected: function(void | mixed ... : object) | object | program | type(mixed).
pike/lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:593: Warning: Got : mixed.
```https://git.lysator.liu.se/pikelang/pike/-/issues/8071WhiteFish: Detect and repair corrupted entries.2020-03-06T09:40:01ZPeter BortasWhiteFish: Detect and repair corrupted entries.Imported from https://youtrack.roxen.com/issue/PIKE-71
Reported by @grubba
The search engine causes performance issues because of high I/O-load partly because the compactor has nut run for a long time (corrupted blobs). Re-indexing is ...Imported from https://youtrack.roxen.com/issue/PIKE-71
Reported by @grubba
The search engine causes performance issues because of high I/O-load partly because the compactor has nut run for a long time (corrupted blobs). Re-indexing is not an option, takes too long time and the user can not search during the time. The fastest fix is probably to make the compactor handle corrupted blobs and fix them on the fly.
The search compactor exits with the following error, fix it!
```
Real len out of sync for word "10103"; 64 != 17
Real len out of sync for word "10107"; 128 != 28
Real len out of sync for word "10137"; 64 != 7
*** Error in `/usr/local/roxen/server-6.1.215/bin/roxen': free(): invalid next size (fast): 0x00000000025102d0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7c619)[0x7f65e4284619]
/usr/local/roxen/server-6.1.215/pike/lib/modules/_WhiteFish.so(+0x7fc9)[0x7f65d9e56fc9]
/usr/local/roxen/server-6.1.215/pike/lib/modules/_WhiteFish.so(+0x71c5)[0x7f65d9e561c5]
...
```https://git.lysator.liu.se/pikelang/pike/-/issues/8070Former Fix over aggressive constant folding in '.'-operator. task of PIKE-63 ...2018-02-12T10:49:20ZPeter BortasFormer Fix over aggressive constant folding in '.'-operator. task of PIKE-63 (#8063). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-70
Reported by @grubba
Blocking [PIKE-63](#8063)Imported from https://youtrack.roxen.com/issue/PIKE-70
Reported by @grubba
Blocking [PIKE-63](#8063)https://git.lysator.liu.se/pikelang/pike/-/issues/8069Former Merge [Pike-62] to Pike 8.0. task of PIKE-62 (#8062). See it for details.2018-02-21T10:32:23ZPeter BortasFormer Merge [Pike-62] to Pike 8.0. task of PIKE-62 (#8062). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-69
Reported by @grubbaImported from https://youtrack.roxen.com/issue/PIKE-69
Reported by @grubbahttps://git.lysator.liu.se/pikelang/pike/-/issues/8068Former QA [Pike-62] task of PIKE-62 (#8062). See it for details.2018-02-20T09:16:22ZPeter BortasFormer QA [Pike-62] task of PIKE-62 (#8062). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-68
Reported by @grubbaImported from https://youtrack.roxen.com/issue/PIKE-68
Reported by @grubbahttps://git.lysator.liu.se/pikelang/pike/-/issues/8067Consider backporting Inotify add_watch() initialization fix to Pike 8.02020-03-10T09:23:45ZPeter BortasConsider backporting Inotify add_watch() initialization fix to Pike 8.0Imported from https://youtrack.roxen.com/issue/PIKE-67
Reported by Marcus Wellhardh <wellhard@roxen.com>
commit 046e084434a24384350f7c95487c7fc2e0e16550\
Author: Henrik Grubbström (Grubba) <grubba@grubba.org>\
Date: Wed Jun 14 11:59:...Imported from https://youtrack.roxen.com/issue/PIKE-67
Reported by Marcus Wellhardh <wellhard@roxen.com>
commit 046e084434a24384350f7c95487c7fc2e0e16550\
Author: Henrik Grubbström (Grubba) <grubba@grubba.org>\
Date: Wed Jun 14 11:59:04 2017 +0200
Inotify: Improved initialization in add_watch().
Make sure that the backend is woken up after scheduling the
artifical initialization events. Otherwise they may stay
pending indefinitely.
https://git.lysator.liu.se/pikelang/pike/-/issues/8066Former QA task of PIKE-65 (#8065). See it for details.2018-02-08T10:41:57ZPeter BortasFormer QA task of PIKE-65 (#8065). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-66
Reported by @grubbaImported from https://youtrack.roxen.com/issue/PIKE-66
Reported by @grubbahttps://git.lysator.liu.se/pikelang/pike/-/issues/8065register_path() doesn't reschedule the backend_check() call_out.2020-03-05T17:23:49ZPeter Bortasregister_path() doesn't reschedule the backend_check() call_out.Imported from https://youtrack.roxen.com/issue/PIKE-65
Reported by @grubba
If the newly added monitor ends up at the head of the `monitor_queue`, the `backend_check()` call_out likely needs to be rescheduled.Imported from https://youtrack.roxen.com/issue/PIKE-65
Reported by @grubba
If the newly added monitor ends up at the head of the `monitor_queue`, the `backend_check()` call_out likely needs to be rescheduled.