Neues Release von Yacy?

Hallo,

ich habe nach langer Zeit mal wieder Yacy installiert. Das letzte Release ist 1.92/9000 und ungefähr 2 Jahre alt. Es gab doch schon einige Commits , doch leider findet er bei mir keine Updates zum installieren.

Grüße

Hallo bbtuxi, willkommen (zurück!) hier im neuen Forum!

Also ich hab mir fest vorgenommen in den nächsten Tagen beim #cccamp19 ein neues Release zu machen, und ggf. auch mal anständige Docker container zu bauen… Und wenn ich mich ganz doll zusammenreisse kommt vielleicht noch ein CI/CD dazu um automatisiert dev-releases zu deployen.

Aber es kann auch sein… na hoffentlich nicht.

1 Like

Hello @Orbiter
I think this is related.
Last release in 2016? I see commits, but no new release.

Well I actually worked on the release and published it at the new yacy.net home page, but without setting a release tag. At https://yacy.net/download_installation/ the version http://latest.yacy.net/yacy_v1.922_20191013_9964.tar.gz is now available, I wanted to silently test out if that is working for everyone (after I tested it on a large set of OS). Next step is only to increase the version number to 1.93 and set a release tag.

1 Like

@Orbiter
Sorry to be that late. I did not received any e-mail notification.
Thank you for the links and your hard work.
To help you and YaCy, please consider, flatpak and liberapay.



Thanks again!

Hi,

using v1.922/9964 the following exception is thrown:

W 2019/11/25 19:06:53 ConcurrentLog java.io.IOException: Negative seek offset java.io.IOException: Negative seek offset at java.io.RandomAccessFile.seek(RandomAccessFile.java:572) at net.yacy.kelondro.io.CachedFileWriter.seek(CachedFileWriter.java:143) at net.yacy.kelondro.blob.Heap.add(Heap.java:153) at net.yacy.kelondro.blob.Heap.insert(Heap.java:356) at net.yacy.kelondro.blob.BEncodedHeap.insert(BEncodedHeap.java:395) at net.yacy.kelondro.blob.BEncodedHeap.update(BEncodedHeap.java:413) at net.yacy.kelondro.blob.Tables.update(Tables.java:406) at net.yacy.search.Switchboard.storeDocumentIndex(Switchboard.java:3473) at net.yacy.search.Switchboard.storeDocumentIndex(Switchboard.java:3355) at net.yacy.search.Switchboard$6.process(Switchboard.java:1043) at net.yacy.search.Switchboard$6.process(Switchboard.java:1039) at net.yacy.kelondro.workflow.InstantBlockingThread.job(InstantBlockingThread.java:72) at net.yacy.kelondro.workflow.AbstractBlockingThread.run(AbstractBlockingThread.java:82) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522) at java.util.concurrent.FutureTask.run(FutureTask.java:277) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.lang.Thread.run(Thread.java:818)

it happens during the usage of the ‘Re-crawl index documents’ function. What’s happening? Are some of my BLOBs corrupted? If so, is there a method to repair them?

Greetings

LA_FORGE

Kompletter Stacktrace