papermc / paperd Goto Github PK

paperd.options will be a file which will allow specifying command line parameters for run and start without having to type them out all the time.

Will also support environment variables using ${ENV_VAR} syntax.

Will resolve #1.

https://papermc.io/ci/view/all/job/paperd/lastSuccessfulBuild/artifact/paperd.tar.xz
(which is used in curl https://papermc.io/ci/view/all/job/paperd/lastSuccessfulBuild/artifact/paperd.tar.xz -o paperd.tar.xz) returns a 404

There are no builds on the Jenkins page

Attempting to compile from source returns the following error

   --> src/lib.rs:145:9
    |
145 |         m_type,
    |         ^^^^^^ expected i32, found i64
    |
help: you can convert an `i64` to `i32` and panic if the converted value wouldn't fit
    |
145 |         m_type: m_type.try_into().unwrap(),
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: could not compile `paperd-jni`.```

Thus, it is impossible to install paperd.

There is the ability to pass java arguments, I would like to also pass arguments to the server, for example --world-dir or --port

Warning: No memory argument provided, automatically determining to use 4440 MB instead. This is not recommended, please specify an amount of memory with -d or --default-args
The specified jar file (/home/admin/Dokumente/1.14.4/paperclip.jar) does not have a protocol version file, it is not compatible with paperd.

However, seems like whilest patching the jar something goes wrong

Hey, I don't know if this is the right channel to report this or if I should post it somewhere else (like in Discord). However it seems to be related to JNI implementation according to thread dump below:

"paperd-Message-Response-Handler-7" #94 prio=5 os_prio=0 cpu=35830,13ms elapsed=42,75s tid=0x00007ff88c00a800 nid=0x1b1d runnable  [0x00007ff7e5c13000]
   java.lang.Thread.State: RUNNABLE
	at com.destroystokyo.paper.daemon.PaperDaemonJni.receiveMessage(Native Method)
	at com.destroystokyo.paper.daemon.PaperDaemon$MessageHandler.run(PaperDaemon.java:448)
	at java.util.concurrent.Executors$RunnableAdapter.call([email protected]/Executors.java:515)
	at java.util.concurrent.FutureTask.run([email protected]/FutureTask.java:264)
	at java.util.concurrent.ThreadPoolExecutor.runWorker([email protected]/ThreadPoolExecutor.java:1130)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run([email protected]/ThreadPoolExecutor.java:630)
	at java.lang.Thread.run([email protected]/Thread.java:832)

I noticed that the paperd daemon inside Paper fully satures the CPU after invoking some commands from the paperd CLI. It spawns multiple threads and each of them get stuck at the line above.

Setup

Maybe it's just my setup. So here is what I tried. I compiled this project natively (without Docker) from the root project directory and Paper using the daemon feature branch. Copied paperclip out of it (soft symlinks would link to the original source) and started the server using the absolute path of paperd (~/[...]/paperd start).

Testing

The issue occurs only after interacting with the daemon. I could reproduce it with the console command as well as the status command. Invoking the latter multiple times causes 100% CPU usage.

BTW:
Nice project idea, especially the console feature is very useful. It extends the feature set from existing tools like tmux.

Hi, I looked on what looks like the old jenkins instance but could not find a build, would it be possible to build a binary on each commit using travis to publish to github releases?

Download links do not work anymore, they redirect to here but paperd is not listed as project in the api.