zapek / xeres Goto Github PK

A Peer-to-Peer (Friend-to-Friend), decentralized, encrypted and secure application designed for communication and sharing.

Home Page: https://xeres.io

License: GNU General Public License v3.0

Java 99.14% HTML 0.05% CSS 0.33% Python 0.49%

p2p decentralization retroshare java chat f2f peer-to-peer friend-to-friend distributed decentralized

xeres's People

Contributors

Stargazers

Watchers

Forkers

jdrouet temawi eyedeekay adamswhales christianwol-ff

xeres's Issues

Add the location name in the windows

When several Xeres window are open, this is useful, especially when doing remote UI.

Investigate possible currency usage

Having an own currency could be useful, but it shouldn't be wasteful and preferably should promote the usage of the application.

Here are some ideas. Proof of work is out of the question.

Add a shutdown menu in remote UI mode

This is useful to shutdown the other end. We already have an actuator endpoint for that.

Add Groovy as a scripting language

Some scriptable events could benefit from using Groovy. For example:

receiving a chat message when idle
finished downloading a file (to transcode it or move it somewhere)
removing peers who didn't connect for a long time

Make sure the location name is handled by discovery

Someone should check if the location name is properly updated by discovery.
If it isn't, handle it.

How to test:

add a friend
after the connection, his location name should change to something else than "[locationId]".

Add support for unix-domain sockets to avoid hogging a local port for the UI

Xeres by default uses localhost:1066 for communication with the UI. This prevents from easily running 2 instances. It would be more useful to use a local domain unix socket.

They're supported in JDK 17: https://openjdk.java.net/jeps/380

And it seems Netty supports them too: https://github.com/dandaso/netty_uds/blob/master/src/main/java/UdsEchoServer.java

Contrary to their name, they should work in Windows too.

Add direct friend request

It should be possible to allow friend requests without exchanging Short Invites first. This is possible because:

the PGP id is in the SSL certificate's issuer field
if the PGP key was gathered through discovery, we can show the profile's name and information
don't forget to verify the signature with the PGP key that we have, otherwise don't even show the requester

Investigate emoji support

See https://github.com/vdurmont/emoji-java

Add support for nick completion using tab key

When typing , complete by using the first nickname in the list. Pressing tab again uses the next nickname.

Also works when typing S -> Somenick:
Pressing tab again switches to another nickname that starts with 'S' and so on. Then cycles back.

Improve the database backups strategy

Right now a backup is done on each shutdown and it overwrites the previous one.
Find a better strategy.

Should backups be done each X time? For example each hour.
Should backups be performed each X shutdowns? For example each 5 times.
How many previous backups to keep?
Should all of the above be configurable?
Should the software respond to backup tools?
Should the backup be encrypted?

Creating a chat room should join automatically

When creating a local chat room, the client should join automatically. Right now, the other peer can join the chat room but the creating peer cannot join it then. This might be just an UI refresh bug too.

Support inline images

Add support for inline images.

Add support for URLs

Add support for URLs in the chat.

Maybe put some warning if the URL is an outside URL, though this is annoying. Right now Xeres doesn't have built in URLs.

Mark unread messages in the chat rooms

Description

On the left side, a chat room which is not the current chat room should indicate there are new messages in it, for example using a bold font or some icon.

Allow generic sets to be serialized

Currently a Set is considered as EnumSet, but there could be Set or so...

When a set is encountered, we should try to get its type (ParameterizedType has it I think) then use another path if it's not an EnumSet. That way we avoid having to put a special value in the annotation.

On second thought, that only works for deserialize() as it has a Field parameter, serialize() will have to be redesigned somehow (grmbl).

Adding a friend should connect to him immediately

Right now it waits for the connections job, which happens each minute.

Protocol error when someone pasts images

When someone pasts images from Retroshare (Xeres cannot paste images yet), one gets the following:

io.netty.handler.codec.DecoderException: java.net.ProtocolException: Packet 3651 has too many slices (17)
    at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:98) ~[netty-codec-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:324) ~[netty-codec-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:311) ~[netty-codec-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:432) ~[netty-codec-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) ~[netty-codec-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:370) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) ~[netty-common-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) ~[netty-common-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) ~[netty-transport-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) ~[netty-common-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.65.Final.jar:4.1.65.Final]
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.65.Final.jar:4.1.65.Final]
    at java.base/java.lang.Thread.run(Thread.java:831) ~[na:na]
Caused by: java.net.ProtocolException: Packet 3651 has too many slices (17)
    at io.xeres.app.net.peer.pipeline.ItemDecoder.decodeNewPacket(ItemDecoder.java:85) ~[main/:na]
    at io.xeres.app.net.peer.pipeline.ItemDecoder.decode(ItemDecoder.java:48) ~[main/:na]
    at io.xeres.app.net.peer.pipeline.ItemDecoder.decode(ItemDecoder.java:35) ~[main/:na]
    at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88) ~[netty-codec-4.1.65.Final.jar:4.1.65.Final]

ItemDecoder has a MAX_SLICES set to 16 but I don't know if this is some limit I set myself. Investigate a bit and possibly raise it, even though I don't handle images yet.

Discovery doesn't request the peer's full PGP key on the first connection

Connecting twice works. This is caused by:

java.lang.IllegalArgumentException: Type 4208 does not match 4209

So implement that address decoding.

Create nightly builds and automated releases

See:

Remove RsCertificate support

Check what the Retroshare team thinks about this but I think the certificate system can go away.

External IP address is wrong when UPNP fails

What happened?

If UPNP fails, the previous external IP address is displayed.

How to reproduce

Go to a location when UPNP works
Shutdown then go to a location when UPNP doesn't work (off in the router, public NAT, etc...)
Go to the UI/Settings. The previous external IP address is displayed

This happens because the IP is fetched from the database. It should be stored as runtime.
Beware though! Make sure we don't break certificate generation as it's still useful to have a working IP.
Maybe add a "runtime/now" parameter to the controller.

Version

0.5.3

Which OS are you running?

Windows

Relevant log output

No response

Identity image auto update

When a new identity joins a channel, its image is set to blank (because it's not found). there should be a way to try to update it later.

Add created and updated fields for some entities

Some entities (i.e. location or profile) could have a created/updated field for housekeeping purposes.

Spring supports @CreatedDate and @LastModifiedDate. Find out what they could be used for.

Connect first to a preselected IP address when adding a friend

When adding a friend, the list of the IPs in its RSId are displayed and selectable from a ChoiceBox. Unfortunately, the selection has no effect yet. Ideally the first connection should be made to the IP preselected.

Related to 9aee663.

Investigate memory usage and which GC to use for the release version

For a standalone version, memory usage should be optimized.

A good candidate might be ZGC because it returns unused memory to the OS.

Add gradle toolchain support

If JDK 17 is not installed on the local machine (but an earlier release), the compilation with gradle will fail.

https://blog.gradle.org/java-toolchains
https://docs.gradle.org/6.7/userguide/toolchains.html#sec:auto_detection

IDEA seems to support those locations as well.

Use styles instead of setting margins manually

Instead of setting the margins manually, try to use a CSS style. That way it'll be possible to have various looks in the future.

See https://docs.oracle.com/javafx/2/layout/style_css.htm

Finish implementing the DHT

Currently the DHT works but isn't being used for anything. It has to be able to find peers.

Retroshare doesn't store any IP in the DHT, I think it's something like the hash of LocationId and Profile's PGP id.

Doesn't start on MacOS

What happened?

Reported by AdamH:

Once the DMG is installed, the executable starts with the following error:
"Xeres.app is damaged and can't be opened"

This seems to be because the bundled JRE is signed but not Xeres itself or something. More details available at:
https://bugs.openjdk.java.net/browse/JDK-8276150

Possible solutions:

wait for the next JDK (LTS)
sign the executable
tell users to use 'xattr'

How to reproduce

Install the DMG and run the executable.

Version

0.3.1

Which OS are you running?

MacOS

Relevant log output

No response

Write tests for repositories

Many tests are missing for the repositories.

Profiles without PGP public key should be highlighted in the list

Right now it's impossible to visually distinguish them. Either put a different color or add a column.

Note: a profile without a PGP public key is a profile that was imported from a Short Invite but was never connected to.

Make it possible to invite friends when creating a room

Add debug menu

For example a way to trigger a garbage collection manually to check if there are netty leaks.

Investigate code signing

On Windows, and possibly MacOS, there's a code signing warning when running .exe files, in this case, the installer.

Investigate if there are some Open Source friendly signing certificates, like for example:
https://shop.certum.eu/open-source-code-signing-code.html

Discussion:

https://stackoverflow.com/questions/252226/signing-a-windows-exe-file

Tools:

https://ebourg.github.io/jsign/

Process:

https://mkaz.blog/code/code-signing-a-windows-application/

Note that all of this doesn't remove the Smartscreen filter warning.

Fix possible N + 1 queries

Check if there's some N + 1 queries left, see https://www.sipios.com/blog-tech/eliminate-hibernate-n-plus-1-queries for the non trivial ones.

Sometimes the scheduler will still run while the app is being shutdown

2020-12-31 19:17:01.411 INFO 8428 --- [lication Thread] io.xeres.app.application.Startup : Shutting down...
2020-12-31 19:17:01.411 INFO 8428 --- [lication Thread] io.xeres.app.net.upnp.UPNPService : Stopping UPNP...
2020-12-31 19:17:01.411 DEBUG 8428 --- [lication Thread] i.x.app.net.peer.bootstrap.PeerServer : Shutting down netty server (fast)...
2020-12-31 19:17:01.415 DEBUG 8428 --- [lication Thread] i.x.app.net.peer.bootstrap.PeerClient : Shutting down netty client (fast)...
2020-12-31 19:17:01.518 DEBUG 8428 --- [ecutorGroup-3-1] i.x.app.net.peer.pipeline.PeerHandler : Closing connection with /11.11.11.11:1234
2020-12-31 19:17:04.507 DEBUG 8428 --- [MessageBroker-2] i.x.app.net.peer.PeerConnectionManager : Attempting to connect to 11.11.11:1234 ...

The last line shouldn't happen.

Add a way to migrate between H2 versions

H2 doesn't support upgrades when migrating from one version to the next. Right now the current version seems to work well but it could be a problem for further releases.

The following script is interesting: https://github.com/manticore-projects/H2MigrationTool

Investigate usage of GraalVM

GraalVM is an improved JVM with fast startup times and better performances.

What is needed is:

current support for all OSes
support for Spring Boot
support for JavaFX

Oracle still recommends JDK 17. See when they start recommending GraalVM.

Detect when we're idle to change our status

Some implementations:

In download/fiatlux-source-archive.zip there's an os/time folder with JNI time detection. Read the Core Java JNI chapter then try to use it. The project is at https://code.google.com/p/fiat-lux/source/browse/Fiat+Lux/src/fiatlux/os/time/

Also https://ochafik.com/p_98 and net.java.dev.jna:jna:5.7.0 in maven.

And also https://github.com/java-native-access/jna

Upgrade H2 database

Blocked by flyway/flyway#3334

Allow to set the trust of the peer when importing a Short Invite

In the import UI, put a cycle widget to be able to set the trust level (defaults to unknown).

Message broadcasts are nowhere to be received

There's nothing to receive broadcast messages...

Implement Modern Standby support

See how the software behaves under Modern Standby and check if we have to do something particular about it.

See API docs.

Add support for actuator in the UI

Some endpoints the UI could use:
/actuator/health (returns status: UP)
/actuator/info (returns the name, build time and version)

Custom info contributor could also be written to expose some configuration, which will be shown in the UI.

Implement a per service preference system

Right now everything is stored in the database but it requires a model and JPA repositories.
We should add a way for services to define their own things (i.e. saving/loading data) for more modularity and possible plugins later on.

Finish the implementation of the packet splitting and grouping

The receiving part is done but not the sending part.

This is quite tricky though. Netty doesn't directly support it.

Spurious warnings by tomcat upon exit

What happened?

When exiting, I get the following warnings in the logs.

This happens since Spring Boot 2.7.3 and because of the following commit: spring-projects/spring-boot@45ad155

Tomcat has some memory leaks detection that kicks in on shutdown.

This doesn't happen when using --no-gui and it's caused by:

The STOMP web sockets (clientInbouldChannel-* and clientOutboundChannel-1 threads)
The SSE notifications (CompletableFutureDelayScheduler thread)

I'm still unsure of why it happens. Case 1 should be handled by Spring Boot IMHO and case 2 becomes needlessly complicated when putting an own executor and shutting it down (there's not even a way to have it done before tomcat shuts down).

How to reproduce

Run Xeres in UI mode
Select "Exit" in the menu

Version

0.5.2

Which OS are you running?

Windows

Relevant log output

2022-09-25 18:03:59.373  INFO 24112 --- [lication Thread] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2022-09-25 18:03:59.375  INFO 24112 --- [lication Thread] o.a.c.c.C.[Tomcat].[localhost].[/]       : Destroying Spring FrameworkServlet 'dispatcherServlet'
2022-09-25 18:03:59.378  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.379  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.379  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.380  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientOutboundChannel-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.381  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.382  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.383  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.384  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [CompletableFutureDelayScheduler] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
 [email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3464)
 [email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3435)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
 [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1170)
 [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.385  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.386  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-8] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:03:59.387  WARN 24112 --- [lication Thread] o.a.c.loader.WebappClassLoaderBase       : The web application [ROOT] appears to have started a thread named [clientInboundChannel-9] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
 [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:460)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1061)
 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [email protected]/java.lang.Thread.run(Thread.java:833)
2022-09-25 18:04:01.481  INFO 24112 --- [lication Thread] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default'
2022-09-25 18:04:01.485  INFO 24112 --- [lication Thread] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
2022-09-25 18:04:01.592  INFO 24112 --- [lication Thread] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.

Support more recent installer arguments

Description

Latest jpackage (JDK19) has some improvements:

petr-panteleyev/jpackage-gradle-plugin@d0bb304

Once Gradle 7.6 is released, switch to JDK 19 and try.

Prefer direct connections for clients on the same LAN

When a peer has the same external IP address as us, prefer its LAN IP address. Using the external one still works most of the time but it's less efficient.

Short Invites include the LAN IP and there's Broadcast Discovery too.

Identities aren't transferred properly from Xeres to Retroshare

Using discovery, the following transfers work:

Retroshare -> Retroshare
Retroshare -> Xeres
Xeres -> Xeres

but the following fails:

Xeres -> Retroshare

To reproduce, simply connect 2 clients together. Check the logs on Xeres' side then notice that the identities never show up on Retroshare's contacts UI.

Maybe check with the Retroshare team if they have a better idea of which debugging output should be enabled to find out which part if failing.

zapek / xeres Goto Github PK

xeres's People

Contributors

Stargazers

Watchers

Forkers

xeres's Issues

Description

What happened?

How to reproduce

Version

Which OS are you running?

Relevant log output

What happened?

How to reproduce

Version

Which OS are you running?

Relevant log output

What happened?

How to reproduce

Version

Which OS are you running?

Relevant log output

Description

Recommend Projects

Recommend Topics

Recommend Org