CFP: make cilium ingress work on bare metal without any extra components

Cilium Feature Proposal
Thanks for taking time to make a feature request for Cilium! If you have usage questions, please try the slack channel and see the FAQ first.
Is your feature request related to a problem?
Currently, the docs state:

The ingress controller creates a service of LoadBalancer type, so your environment will need to support this.

Other ingress controllers running on bare metal can make use of hostPort (e.g. ingress-nginx w/ cilium as CNI works like that). Cilium requires a load-balanced service which, in turn, requires extra components (e.g. metallb).
Describe the feature you'd like
For trivial setups it'd be great if cilium listened on the host network's tcp80 and tcp443 and served as an ingress without any extra component requirements.
(Optional) Describe your proposed solution
Given that envoy already runs in the host network, it should be only the matter of listening on the relevant ports.

cc @youngnick

I was just looking at how to run the ingress without a LoadBalancer service as well and found this issue. I agree that it would be nice if we could configure some hostPorts for envoy to listen on at all times, then a user could direct traffic to these hostPorts through whatever mechanisms they have available in their environment.

I agree that this would be a great feature, but I think the problems we need to incorporate solutions for into a design are:

How do you request the behavior, and target specific ports? For Ingress, this will need to be annotations, but we should really also be thinking about how to do a similar thing for Gateway API objects (which is harder because they include the port the client should connect on in the listener definition, not any intermediate ports, which is what we have here).
How do you keep track of what port is assigned to what Ingress/Gateway/whatever? If the port is being used by some external (possibly not k8s-aware) system, then it probably needs to be statically defined, rather than dynamically allocated. But dynamic allocation also seems like it would be useful (otherwise you're stuck keeping track of hostPorts on a spreadsheet somewhere or something).

However, doing this will mean that we can give people TCPRoute and UDPRoute Gateway API support of some sort on bare metal, which seems very useful.

Hmm, I think this is still worth doing, but it may be a while before we get to it.


How to get the Certificate onto Nodes for people who are not using ARM templates to create/configure Clusters

Maybe I'll save someone a couple of hours of R&D.
a. Import it into the Fabric's own Key Vault.  BEWARE, it needs to go into the Settings/Secrets section, not Settings/Certificates.
b. - Log into the htpps://resources.azure.com site.
- Drill down to the resourceGroups entry in which your Cluster is located.
- Expand the provider/Microsoft.Compute node.
- Click on the virtualMachineScaleSets/<VM name> node.
- Hit the Edit button in the right panel.
- Find the "vaultCertificates" array and add the Certificate
- Hit the PUT button.
- Log into 1-2 VMs and verify that the Certificate is present in the Certificates - Local Computer/ Personal/ Certificates location

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 65744c73-e7a2-6d5b-004c-22f980730bd0
Version Independent ID: d3366f95-1038-0e0c-4f98-9ce25b96c928
Content: Set up an encryption certificate and encrypt secrets on Azure Service Fabric Windows clusters
Content Source: articles/service-fabric/service-fabric-application-secret-management-windows.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

@eugen-nw thanks for this! I will take a look and see if we can find a good place to put this into the documentation (or a new doc possibly)

You are more than welcome!
In exchange, can you please show on the https://docs.microsoft.com/en-us/azure/service-fabric/configure-existing-cluster-enable-managed-identity-token-service page how to stitch in the resources.azure.com JSON, an instance of Microsoft.ManagedIdentity/userAssignedIdentities into a Microsoft.ServiceFabric/clusters instance?

Noted! I will take a look at that as well. Likely won't get to anything until Monday but it's assigned to me so will look and see what we can do.

@eugen-nw I am assigning this to @peterpogorski who is one of the Service Fabric PMs. We can add this work to the backlog and work offline to find the best place to address it in the docs :)

Hi @eugen-nw!
Thank you for your feedback on the documentation! The steps that you have outlined would work to update the certificate on a cluster where you do not have access to the ARM template, however this is not a best practice that we want to recommend to customers.
When updating the certificate through resources.azure.com, the configuration of the cluster will become out of sync with any local resources you may have. It is then possible for customers to end up redeploying and creating other issues with their cluster.
If you have any other concerns or feedback, feel free to reopen this issue.
#please-close

As long as people have the option of creating SF clusters through the Azure portal, they will create SF clusters through the Azure portal.  In the circumstances, Microsoft needs to design solutions that those people can use.
Startups tend not to have admin-type people who have ARM template expertise and may not be willing to take the long and frustrating route of using often times incomplete/outdated ARM templates that are provided as samples.


feat: setup dotnet CI

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.54%. Comparing base (17f36e9) to head (5ab3fd9).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #771      +/-   ##
==========================================
- Coverage   70.54%   70.54%   -0.01%
==========================================
  Files         297      297
  Lines       43515    43515
==========================================
- Hits        30698    30697       -1
- Misses      12817    12818       +1

Components
Coverage Δ

crashtracker
44.83% <ø> (-0.03%)
:arrow_down:

crashtracker-ffi
8.41% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
89.09% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
83.46% <ø> (ø)

ddcommon-ffi
69.12% <ø> (ø)

ddtelemetry
59.05% <ø> (ø)

ddtelemetry-ffi
22.13% <ø> (ø)

dogstatsd
89.45% <ø> (ø)

dogstatsd-client
79.77% <ø> (ø)

ipc
82.76% <ø> (ø)

profiling
84.30% <ø> (ø)

profiling-ffi
77.46% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
38.01% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
93.47% <ø> (ø)

trace-mini-agent
72.36% <ø> (ø)

trace-normalization
98.23% <ø> (ø)

trace-obfuscation
95.77% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.29% <ø> (ø)


How to use plugins as a class member

hi:
how to use plugins such as Telemetry in a user-defined class?

Did you have a look at the examples?

@JonasVautherin thanks, I found the way to use it.


Text displays as URL friendly in Home and RequestViewer

Text such as line breaks, quotation marks, and other things display as URL friendly string.

fixed with HttpUtility.HtmlDecode


repo: Improve key signing of binaries

This:

switches to using a securefile rather than env var for the gpg key
adds a key password
improves error handling in asset publishing code

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@mattklein123 as soon as this lands we will need to update the keys to match the changed expectations


bump to 1.1.5

resolves #

Description

Checklist

[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the README.md file

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@fead66f). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             develop      #62   +/-   ##
==========================================
  Coverage           ?   43.77%
==========================================
  Files              ?       22
  Lines              ?      546
  Branches           ?       41
==========================================
  Hits               ?      239
  Misses             ?      307
  Partials           ?        0


Create an image for the mod and add it to the README

The instructions for publishing a mod say the following:

The first image in your README file will be used as the mod's thumbnail on the website, to insert an image, simply paste it inside of the editor. Make sure it's at the very top of your document.

We should create an image for the mod and insert it in our README.

I added an image, waiting for folks feedback before I mark this done

fixed kerning issue folks pointed out, closing


New turnip

Update rutabaga to handle new version of turnip jnicklas/turnip and test on newer rubies and rspecs.

@joshuafleck please sign off. I've tested against chopin (version of master) and latest turnip (1.3.1) which allows us to use standard parallel_tests instead of a fork.

signed-off-by: @joshuafleck


Current State Node: Override/Keep current message

Is your feature request related to a problem? Please describe.
I would like to be able to stop the Current State node from overriding the input message (as is present (albeit not working pending a pull request) in the original fork).
Describe the solution you'd like
The solution present in the original fork.
Describe alternatives you've considered
I tried using the original fork but there are problems with some of the nodes, and the status feedback in this fork is pretty!
Additional context
N/A.

 Didn't realise it wasn't working because the msg.payload structure has changed between forks.
Thanks again, this fork is great!


IOSender crash when start with door opened.

Using the feature 'OPTION(SafetyDoor "Safety door enable" ON)' if you start iosender and this condition is true, it crash.

The latest edge version 2.0.43p2 should be ok - you can try it?

The latest edge version 2.0.43p2 should be ok - you can try it?

Hi Terje.
Yes, off course i can.

The crash problem has solved, but another strange think is happening.
After the process the IOsender is reporting in inches, but is not his my option.
Look the pictures bellow , the sequence of open, reset and jog.
If I start with door closed IOsender do not report in inches.
Thank you.

Oops, door close behaves differently depending on parking mode on/off. I have uploaded a new edge version that hopefully works...

Oops, door close behaves differently depending on parking mode on/off. I have uploaded a new edge version that hopefully works...

Worked perfectly... Thank you Again.
Will new version of IOsender come with this correction ?
Regards,
Reinaldo de Souza

Will new version of IOsender come with this correction ?

Yes, edge versions are prereleases.


web - drop createAppUri in favor of openExternal

//cc @jrieken @mjbvz

Sorry, another attempt: https://github.com/microsoft/vscode/pull/83055


feat: replace create with button

Proposed behaviour
This PR adds in a new transform to replace the deprecated Create component with the Button component.
Current behaviour
This functionality does not currently exist.
Checklist

[x] Release notes (Conventional Commits)
[x] Unit tests
[x] Readme updated

Additional context
Testing instructions
Follow the instructions on the readme and run the codemod over a test repository

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Customize su-exec

The user-spec (e.g. user, user:, user:group) is now read from an
environment variable, SU_EXEC_USERSPEC.
Numeric user/group IDs are no longer supported, for simplicity.
If a user/group doesn't exist, it is a fatal error, instead of
silently continuing as root.

This allows it to be safely used in a docker image with /etc/passwd and
/etc/group bind-mounted from the host machine, and without a user
needing to provide all of the args to the process if they use a
different user.

This change is

I see that you are changing the braces style :). I wouldn't agree with changing the style.
Less important, I wouldn't agree with the style chosen either.
After changing the code quite enough, I miss that you did not change the while(1) loop...

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

su-exec.c, line 38 at r1 (raw file):

	// It's not safe to access the environment if running suid, so use
	// secure_getenv to prevent that.

Style. I reckon it is more common to use /* */ for multi-line comments. Yet, this code specifically uses it in all cases, also for single lines.

su-exec.c, line 56 at r1 (raw file):

	if (pw == NULL) {
		errx(2, "Unknown user '%s'", user);
        }

indentation

su-exec.c, line 111 at r1 (raw file):

}

// vim: noet sw=8

is this really needed?

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions.

su-exec.c, line 38 at r1 (raw file):
Previously, sgmonroy (Sergio Gonzalez Monroy) wrote…
Style. I reckon it is more common to use /* */ for multi-line comments. Yet, this code specifically uses it in all cases, also for single lines.

Done.

su-exec.c, line 56 at r1 (raw file):
Previously, sgmonroy (Sergio Gonzalez Monroy) wrote…
indentation

To answer your question re: the vim modeline, this is exactly why that is needed :) This file uses a very different indentation style from everything else we have, and so a normal editor config will screw it up.

su-exec.c, line 111 at r1 (raw file):
Previously, sgmonroy (Sergio Gonzalez Monroy) wrote…
is this really needed?

Discussed above.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


query "select @rid as @rid, name from ouser" returns error

I use an override of field because i want receive the same result for different queries.
when i use query "select from ouser", I receive RIDs in field "@RID"
orientdb {db=test}> select from ouser
----+----+------+------+-------------------------------------------------------------------------+------+-----
#   | @RID| @ CLASS|name  |password                                                                 |status|roles
----+----+------+------+-------------------------------------------------------------------------+------+-----
0   |#5:0|OUser |admin |{SHA-256}8C6976E5B5410.....415BDE90|ACTIVE|[1]
1   |#5:1|OUser |reader|{SHA-256}3D0941964AA3EBDCB00CCE....D5AEC7F31090A0FB30|ACTIVE|[1]
2   |#5:2|OUser |writer|{SHA-256}B93006774CBDD4B299389A03...11A909FBA5|ACTIVE|[1]
----+----+------+------+-------------------------------------------------------------------------+------+-----
3 item(s) found. Query executed in 0.008 sec(s).
but if I use query with projections, I receive RIDs in field "RID"
orientdb {db=test}> select @rid, name from ouser
----+------+----+------
#   | @ CLASS| rid |name
----+------+----+------
0   |null  |#5:0|admin
1   |null  |#5:1|reader
2   |null  |#5:2|writer
----+------+----+------
3 item(s) found. Query executed in 0.006 sec(s).
so I use override of the field to get a similar result
orientdb {db=test}> select @rid as @rid, name from ouser
----+----+------+------
#   | @RID| @ CLASS|name
----+----+------+------
0   |#5:0|OUser |admin
1   |#5:1|OUser |reader
2   |#5:2|OUser |writer
----+----+------+------
3 item(s) found. Query executed in 0.005 sec(s).
the top code worked in version 2.0.13 but in version 2.1.0 the query "select @rid as @rid, name from ouser" returns error
orientdb {db=test}> select @rid as @rid, name from ouser
Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error on parsing command at position #0: Encountered " <RECORD_ATTRIBUTE> "@
rid "" at line 1, column 16.

Hi @Ivanov-Yuriy
@ field names are not valid aliases in 2.1, but it's actually quite easy to support.
@lvca shall we support it?

What is rather interesting - it works in "old style" with 2.1 too, but only if your database was created in 2.0.X version.
Does it mean that ODB has different logic for different file formats? If file structure changed for 2.1 - may new logic hurt our (just copied to new version, not imported) data files then?
Sorry for off-topic.

Hi @a-unite
it was made for backward compatibility. Old databases maintain the old behavior (no strict SQL), while newly created dbs have strict validation enabled by default

@luigidellaquila thank you!
I understand it is safe to move to 2.1 in production then, and re-import after all parser tests are settled. This issue with @ sign is quite important for us now. I think, that if first query is still returns '@rid', then it is quite obvious, that you will need to have aliases with same name (@ included) one day, i.e. for API consistency.
Another way to solve this - is to use projections in every other query.

Another way to solve this - is to use projections in every other query.

or always return service field with sign "@"
or never return service field with sign "@"

not important, only the service field would have the same name always

@Ivanov-Yuriy Sorry, my suggestion was kind of sarcastic, yours makes sense, while could raise compatibility issues (might be solved with another config parameter introduced, though).
@luigidellaquila, @lvca just curious - were there reasons, to strip @ from system fields names in projection queries' results?

I have similar question about this.
Assume a class A has several value properties(a to g) and LINK property(link).
I cannot get 'partial' document with @rid property(with @ prefix):
select @rid, @version, e, f, g, link.value as value from A
@ prefix will be stripped out, anything else is good enough.
But I can get partial document like this:
select *, link.Value as value from A fetchplan a:-2 b:-2 c:-2 d:-2
It doesn't strip the @ sign, and works good.
So technically, there's no problem to make partial document as a result.
For now, I can go with second way. However it's uncomfortable and inefficient, I think.
Why don't you support both ways. Is there any cases that could be a problem

As I understand presence of system field in server answer should tell us, that we have original object (with @rid, @type and other system fields in place) as result.
Absence of such special fields somehow indicates, that we have synthetic answer from the server (projection, in general, is synthetic set of fields).
As for me it should be clear from particular fields, though. E.g. conjunction of @type, @rid and @version fields, as it is formed now. While I, personally, will be glad to have special indicator\answer property, something like @answerType.
Anyway, we are going off track here.
Support of old behavior is essential for us. Improvements are very much welcomed.

Dear @luigidellaquila, @lvca  haven't you come with any decision on original issue?

for me very important understand, this behaviour will stay the same and I must change my code or will you change this behaviour?
please answer me, thank you

@lvca I need your comment on this, there is no technical reason to allow or deny this behavior.
It's just a matter of consistency, shall we allow fields with @ in projections?

Look guys, it was strange to have different results for projection and "natural" query before 2.1
Example from the initial issue looks weird:
select @rid as @rid, name from ouser
Now it is getting even more strange, when even as @rid doesn't work....
Why don't we return field names as is for new (strict) requests mode? I hope we should use that chance to add good sense to the syntax, not vice versa.

Could you please tell if you are going to come or not with your verdict for this issue anytime soon?
Any answer will be accepted.
Our development cycle is stuck with this matter. Normally we use any workaround which have a common sense or logic behind it, but here situation is quite binary.

The right solution is to do whatever it takes to be consistent.
Scott

Scott,
please, don't stop here.
What solution do you think is best for consistency?

Hehe...unfortunately, I am not experienced enough with ODB to give specific suggestions. But, I know from my experience with quality management, being consistent is a core part of being professional.
From my less experienced ODB perspective, the "@" is the problem.
Scott

Thanks.
My thoughts:

Since as @rid was working before - it looks like there are no any dependencies on that kind of field presence in result set for ODB logic.
If one is asking for @ property - we could return it as is, with @ sign, no surprises.
It might be useful to provide some flag in database for next hot-fix version, to switch that behavior on.
This might be default behavior from version 2.2 (flag is on by default for all newly create databases)
Based on statistics, this flag could be omitted completely from version 2.3
Mention that in documentation and keep issues 4 and 5 for upcoming major releases.

Best regards,
Ata

As a workaround, did you try to unset the strictSql property?
ALTER DATABASE custom strictSQL=false

@giastfader, yes we did and this is how our production version works for now.
But I still hope we could switch to current (proper) query parser soon.

Hi guys,
I just pushed a fix on branch 2.1.x, could you please verify that it completely fixes your use case?
Thanks
Luigi
ps. please comment but keep this issue open, I have to port the issue to develop

Hey Luigi.
Thanks for the quick fix. I call that great support. What should we expect to see?
Scott

Hi @smolinari
just the fix for the original issue, so the same behavior you had in 2.0.
I'm also planning to return @ alias as is (without removing @), but I have to share it with the team and be sure that nothing breaks
Thanks
Luigi

Hi, @luigidellaquila
Looks like it works as previous (@rid as @rid).
Thank you very much!
You could close this issue, though, I'm still wander if we need aliasing @rid -> rid at all.
Hope you will have chance to discuss and decide on this with team.
Will you open another issue, or we could track this one for the progress with it?
WBR, Ata


feat: runTransaction support

Add runTransaction support like here:
https://firebase.google.com/docs/firestore/solutions/aggregation#solution_cloud_functions

Published as 1.0.0-dev.15.0


DD sink should send deltas for counters

Details on: https://docs.google.com/document/d/11ORtaMFBD_jxKrwd6Dj__nFt8pTrU5lyw60u_pfWAJo/edit#heading=h.apxh14sfucxy
tldr; Update the Datadog sink to send deltas for counter metrics rather than sending a current value of the counter.
This was working in SFX because SFX has a cumulative counter type, whereas Datadog expects deltas.

@Areson Applied your feedback, PTAL 🙏

This generally looks good to me. I'm going to see if I can do some integration checking on my end.

Thanks for testing it out @Areson . I will work on documenting it today.


DropdownMenu doesn't work interact well with full-screen switching

If a menu item within a Dropdown menu initiates a full-screen switch, then subsequent menus don't appear.
This is because the DropdownMenuPortal element is implicitly created within the DropdownMenuContent component and cannot therefore be given an appropriate container element. By default the DropdownMenuPortal component is created in the body of the document and it doesn't seem to be possible to make this the target of the full-screen request.
The DropdownMenuPortal element is exported and it is therefore possible to use that with a container element, however the DropdownMenuPortal created within the DropdownMenuContent needs to then be suppressed.
So the work-around is to comment out the DropdownMenuPortal item in the DropdownMenuContent and then explicitly add one with container={document.getElementById("root")} for instance

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

I faced a similar problem as well. It is not only issue in dropdownmenu, tooltip doesn't work as well in fullscreen mode

for me it was a parent div with a fixed position style, so i change it, and it works for me


Automated cherry pick of #5128: huawei userdata fix

Cherry pick of #5128 on release/3.1.
#5128: huawei userdata fix

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/3.1@4b6d010). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             release/3.1   #5129   +/-   ##
=============================================
  Coverage               ?   6.74%
=============================================
  Files                  ?     545
  Lines                  ?   95276
  Branches               ?       0
=============================================
  Hits                   ?    6431
  Misses                 ?   88306
  Partials               ?     539

Flag
Coverage Δ

#aFlag
6.74% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/guestdrivers/huawei.go
9.09% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4b6d010...bfc1f01. Read the comment docs.

/lgtm

/lgtm

/approve


TikTok Source still has issues

Description
When trying TikTok urls, it still doesn't play anything.
Version info
Client used: Poru
Output of java -version:
openjdk version "19.0.2" 2023-01-17
OpenJDK Runtime Environment Temurin-19.0.2+7 (build 19.0.2+7)

2023-08-07 13:31:58.678  WARN 26 --- [back-1-thread-1] c.s.d.l.t.p.LocalAudioTrackExecutor      : Suspicious exception for playback of<PHONE_NUMBER>630754054
com.sedmelluq.discord.lavaplayer.tools.FriendlyException: The audio codec used in the track is not supported.
at com.sedmelluq.discord.lavaplayer.container.mpeg.MpegAudioTrack.loadAudioTrack(MpegAudioTrack.java:65) ~[lavaplayer-1.5.0.jar!/:na]
at com.sedmelluq.discord.lavaplayer.container.mpeg.MpegAudioTrack.process(MpegAudioTrack.java:41) ~[lavaplayer-1.5.0.jar!/:na]
at com.sedmelluq.discord.lavaplayer.track.DelegatedAudioTrack.processDelegate(DelegatedAudioTrack.java:25) ~[lavaplayer-1.5.0.jar!/:na]
at com.dunctebot.sourcemanagers.Mp3Track.loadStream(Mp3Track.java:58) ~[skybot-lavalink-plugin-1.4.2.jar!/:na]
at com.dunctebot.sourcemanagers.tiktok.TikTokAudioTrack.loadStream(TikTokAudioTrack.java:90) ~[skybot-lavalink-plugin-1.4.2.jar!/:na]
at com.dunctebot.sourcemanagers.tiktok.TikTokAudioTrack.process(TikTokAudioTrack.java:76) ~[skybot-lavalink-plugin-1.4.2.jar!/:na]
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:104) ~[lavaplayer-1.5.0.jar!/:na]
at com.sedmelluq.discord.lavaplayer.player.DefaultAudioPlayerManager.lambda$executeTrack$1(DefaultAudioPlayerManager.java:346) ~[lavaplayer-1.5.0.jar!/:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[na:na]
at java.base/java.lang.Thread.run(Thread.java:1589) ~[na:na]
Suppressed: com.sedmelluq.discord.lavaplayer.tools.exception.EnvironmentInformation:
lavaplayer.version: 1.5.0
os.arch: amd64
os.name: Linux
os.version: 5.15.0-78-generic
java.vendor: Eclipse Adoptium
java.version: 19.0.2
java.runtime.version: 19.0.2+7
java.vm.version: 19.0.2+7

What is the plugin version you are using?

I use thé latest, v1.4.2

You need to use the pre release version.
https://github.com/DuncteBot/skybot-lavalink-plugin/releases/tag/PRE_1.5.0_22

Works btw! I had to manually download the file though, since "PRE_1.5.0_22" & "1.5.0" doesn't work yet when trying what you said here:
https://github.com/DuncteBot/skybot-lavalink-plugin#adding-to-lavalink
Otherwise, thank you!