Debezium 0.7.1 Connector - debezium-aws-rds-config-scripts

In this guide, I will share my experience on integrating AWS RDS PostgreSQL and Debezium Kafka
Connector. So we will be able to stream data from AWS RDS PostgreSQL to an another standlone
PostgreSQL DB on AWS EC2 Server.

Hi @fatihmehmetkose, I was wondering, are you still interested in publishing this as a post on the Debezium blog? I think it's good contents and if you addressed those remarks above, we could put it out next week for instance. Let me know what you think. Thanks!

Hi Gunnar,
Yes, I'm still interested in the post and debezium. We as a startup company
are trying to launch a product
2 weeks later ahead. This is why I'm late on responses recently. Sorry for
that.
I think I can fix the article as your recommendations at this
weekend, and let you know.
Is this suitable for you?
Have a nice day.
Fatih Kose
Fairbit, CA, USA
On Thu, Feb 15, 2018 at 5:22 AM, Gunnar Morling<EMAIL_ADDRESS>wrote:

Hi @fatihmehmetkose https://github.com/fatihmehmetkose, I was
wondering, are you still interested in publishing this as a post on the
Debezium blog? I think it's good contents and if you addressed those
remarks above, we could put it out next week for instance. Let me know what
you think. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium.github.io/pull/109#issuecomment-365925571,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZufZAHvu-H4RpBsodR448v3mRL6xC7Vks5tVC-lgaJpZM4RjwI_
.

Yes, I'm still interested in the post and debezium.

Excellent, looking forward to the post very much.

This is why I'm late on responses recently

No worries, good luck with your launch!

I think I can fix the article as your recommendations at this weekend, and let you know. Is this suitable for you?

Yepp, that sounds great. Just ping me here if you've pushed an update. Thanks!

Hi Gunnar,
Sorry to tell you that due to my family health problems, my wife and my kid
got severe flu for one week,
and heavy workload, I could not work on debezium article.
As I said before, I really want to contribute to the project, but current
situation, including coming product launch time at my work,
prevent it from happening.
It seems I can do it after the product launch time, the first week of
March, if it is ok for you.
Thank you for your understanding.
Have a nice day.
Fatih Kose
Fairbit
On Fri, Feb 16, 2018 at 12:10 AM, Gunnar Morling<EMAIL_ADDRESS>wrote:

Yes, I'm still interested in the post and debezium.
Excellent, looking forward to the post very much.
This is why I'm late on responses recently
No worries, good luck with your launch!
I think I can fix the article as your recommendations at this weekend, and
let you know. Is this suitable for you?
Yepp, that sounds great. Just ping me here if you've pushed an update.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium.github.io/pull/109#issuecomment-366169070,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZufZHUx6hpagOSIO2Ii9wqBOVvI5IK_ks5tVTfbgaJpZM4RjwI_
.

Hey @fatihmehmetkose, no worries, all the best to you and your family.  It'd still be nice to have this published. Thanks!

Hey @fatihmehmetkose, just came across this one. I'm not sure whether you're still interested in polishing it so we can put it up to the blog? Would be cool to have it, if not, let's close it so to have a clean slate. Also I hope your family is doing well and the health issues have been sorted out. All the best!

Hi Gunnar,
Thank you for your good wishes for my family, I hope everything is fine on
your side.
Although my company still uses microservices with Java-vertx on Kubernetes,
and the need for debezium for data replication still exists, they have
postponed the data replication parts of our projects at a time in the
future at the last minute,  and I had to close the debezium environment. I
cannot say when they can raise the topic again.
So, we can close my part, really sorry to spend your time and keep you
waiting.
Have a nice day.
Fatih Kose
Fairbit
On Mon, Jun 11, 2018 at 6:54 AM Gunnar Morling<EMAIL_ADDRESS>wrote:

Hey @fatihmehmetkose https://github.com/fatihmehmetkose, just came
across this one. I'm not sure whether you're still interested in polishing
it so we can put it up to the blog? Would be cool to have it, if not, let's
close it so to have a clean slate. Also I hope your family is doing well
and the health issues have been sorted out. All the best!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium.github.io/pull/109#issuecomment-396251461,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZufZFZU33FDCVRGpAFC2_HKNy0BXkNiks5t7nargaJpZM4RjwI_
.

Closing, as it's obsoleted by now. Thanks nevertheless for your efforts, @fatihmehmetkose! Note that by now there are also instructions for running the PG connector test suite against RDS, so it's mostly covered. Thanks again!

It was a pleasure for me to work with you on debezium.
I hope to contribute to the project in the future.
I wish you luck and success on your project
Have a nice day
Fatih Kose
On Fri, Sep 6, 2019 at 1:21 AM Gunnar Morling<EMAIL_ADDRESS>wrote:

Closing, as it's obsoleted by now. Thanks nevertheless for your efforts,
@fatihmehmetkose https://github.com/fatihmehmetkose! Note that by now
there are also instructions
https://github.com/debezium/debezium/blob/master/debezium-connector-postgres/RDS.md
for running the PG connector test suite against RDS, so it's mostly
covered. Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium.github.io/pull/109?email_source=notifications&email_token=AGNZ6ZAHVTK4TZEXBV57OO3QIIHIJA5CNFSM4EMPAI72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6CECVA#issuecomment-528761172,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGNZ6ZH3SVFRS6ULQVKJOMDQIIHIJANCNFSM4EMPAI7Q
.


New category image upload - file name length

Attempted to upload a .png file for new category. File name was 68 characters long, which resulted in a 500 error.
From log file:
PHP Fatal error:  Uncaught exception 'PDOException' with message 'SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'categories_image' at row 1' in /home/somewebsite/public_html/2point4/includes/OSC/OM/DbStatement.php:97
Stack trace:
#0 /home/somewebsite/public_html/2point4/includes/OSC/OM/DbStatement.php(97): PDOStatement->execute(NULL)
#1 /home/somewebsite/public_html/2point4/includes/OSC/OM/Db.php(273): OSC\OM\DbStatement->execute()
#2 /home/somewebsite/public_html/2point4/admin/categories.php(96): OSC\OM\Db->save('categories', Array, Array)
#3 {main}
thrown in /home/somewebsite/public_html/2point4/includes/OSC/OM/DbStatement.php on line 97

🍺  fixed in #535


Correct spacing

Use same spacing in all examples.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Error while finetuning with custom dataset

Describe the bug
Error while finetuning with custom dataset
To Reproduce
Please provide a code snippet of a minimal reproducible example for the error.

python -m uni2ts.data.builder.simple texas TexasTurbineYearly.csv --offset 8640

python -m cli.finetune run_name=my_lsf_run model=moirai_1.0_R_small data=texas val_data=texas

Placed the below yaml  in this folder( uni2ts/cli/conf/finetune/val_data)
_target_: uni2ts.data.builder.ConcatDatasetBuilder
_args_:
  _target_: uni2ts.data.builder.simple.generate_eval_builders
  dataset: texas_eval
  offset: 8640  # Same as _lsf_dataset.py
  eval_length: 2880  # Same as _lsf_dataset.py
  prediction_lengths: [96, 192, 336, 720]
  context_lengths: [1000, 2000, 3000, 4000, 5000]
  patch_sizes: [32, 64]

Expected behavior
Followed the instructions here to fine-tune on custom dataset.
https://github.com/SalesforceAIResearch/uni2ts?tab=readme-ov-file#fine-tuning
Error message or code output
ine 238, in load_dataset
transform=transform_map[self.dataset](
TypeError: MoiraiFinetune.train_transform_map..default_train_transform() got an unexpected keyword argument 'offset'
put error or undesired output here

Environment

Operating system: MacOS
Python version: 3.10
PyTorch version: 2.3.3
uni2ts version (have you pulled the latest version?) latest

what about the yaml file in uni2ts/cli/conf/finetune/data?

Same as the yaml placed under this folder( uni2ts/cli/conf/finetune/val_data)
_target_: uni2ts.data.builder.ConcatDatasetBuilder
_args_:
  _target_: uni2ts.data.builder.simple.generate_eval_builders
  dataset: ETTh2_eval
  offset: 8640  # Same as _lsf_dataset.py
  eval_length: 2880  # Same as _lsf_dataset.py
  prediction_lengths: [96, 192, 336, 720]
  context_lengths: [1000, 2000, 3000, 4000, 5000]
  patch_sizes: [32, 64]

Hi @jpmc216, in the current version, the config format of finetuning data and validation data is different. For the fine-tuning data, you can follow this example https://github.com/SalesforceAIResearch/uni2ts/blob/main/cli/conf/finetune/data/etth1.yaml . You can find that it does not have offset attribute, which raise the error


getting quota-available-bytes on PROPFIND

is it possible to get a quota-available-bytes property in wsgidav responses?

No, this is currently not implemented.
(See https://greenbytes.de/tech/webdav/draft-ietf-webdav-quota-05.xml)


cmake version check fails cmake ver >= 3.10.x (e.g. Ubuntu 18.04)

The current Tools/check_cmake.sh identifies cmake 3.10.2 (e.g. standard on ubuntu 18.04) as cmake 3.1 and throws a fit.
This is the offending line
if [[ $cmake_ver == *" 2.8"* ]] || [[ $cmake_ver == *" 2.9"* ]] || [[ $cmake_ver == *" 3.0"* ]] || [[ $cmake_ver == *" 3.1"* ]]
I don't have cmake 3.1 around and can't reference that version string, perhaps it should say $cmake_ver == *" 3.1."* ]]?

We dropped that script a couple releases ago. Now cmake checks the cmake version.
Can you try newer PX4 stable (v1.8.0)?

Aha, I knew I was missing something. Yep, thanks for that note.


Toast is always displayed in the bottom

Seems like position is ignored and toast is always displayed in the bottom:
self.view.makeToast(message, duration: 3.0, position: .top);
Is there anything I can do to show it in center or on top?
pod 'Toast-Swift', '3.0.1'
swift 4.1
Xcode 9.3.1

Works fine the sample project so I don't believe this is an issue with the library.


Docker image currently broken (ghcr.io/hound-search/hound:latest)

Hi,
The image is currently not working:
2023/05/07 09:24:26 Searcher started for Hound
2023/05/07 09:24:27 All indexes built!
2023/05/07 09:24:27 running server at http://localhost:6080
panic: open .build/ui/index.tpl.html: file does not exist

goroutine 1 [running]:
main.main()
	/go/src/github.com/hound-search/hound/cmds/houndd/main.go:187 +0x445

I guess it got published with the CI run of https://github.com/hound-search/hound/pull/459
Pushing a new docker image should probably not happen with pull requests, but only for new releases?

Hey @moson-mo
I suggested a permanent fix to this issue in PR #463
You can use these images in the meantime, there are no changes apart from the improved pipeline steps
https://github.com/oscrx/hound/pkgs/container/hound

resolved by https://github.com/hound-search/hound/pull/460 and thank a million!

Is #460 related?
Closing #463 does not help I guess...

I agree with @oscrx
The issue that the image is built is still there. Imho PR #463 should be re-opened and rebased.
My PR #460 only addressed the go::embed change, but not that "image publish on pull request" problem.

I'll rebase it when I'm home. But I'm not sure I can reopen the PR by myself

apologies if premature closed.  I did test the docker image and did not see this error.  I'll reopen now and please let me know when you've retested yourself and what the results were.  Cheers.


Chatpulldown

General items:

[ ] I have updated the relevant documentation files under docs/
[ ] My code follows the:

[ ] Google Java style guide (for .java files)
[ ] Google JavaScript style guide (for .js files)

[ ] ant tests passes on my machine

If your code changes how something works on the device (i.e., it affects the companion):

[ ] I branched from ucr
[ ] My pull request has ucr as the base

Further, if you've changed the blocks language or another user-facing designer/blocks API (added a SimpleProperty, etc.):

[ ] I have updated the corresponding version number in YaVersion.java
[ ] I have updated the corresponding upgrader in YoungAndroidFormUpgrader.java (components only)
[ ] I have updated the corresponding entries in versioning.js

For all other changes:

[ ] I branched from master
[ ] My pull request has master as the base

What does this PR accomplish?

Description

Fixes # .

Resolves # .

Note: This commit has two temporary commits, which duplicate #3233 which will be removed when that PR is merged and this PR rebased onto master

Rebased on master and temporary commits removed.

The change I just pushed up rebases this PR on master, it doesn't address any of the review comments. There will be a follow-up change pushed today that does. I've done this in two steps to make it easier to see the changes I make without the changes from the rebase getting in the way.

I just changed the base from master to ucr because I'm about to change the blocks language version (and YAVERSION as a result)


Add docker

When trying out rust-stainless, I found it hard to setup. So I built a docker image out of the instruction, that will probably help new users using it before really installing it.

from a debian image as it needs both rust and java (and alpine uses musl with isn't working with some deps)
add a CI pass to build it
lock some deps version

it seems that your main branch fails to build currently
some deps doesn't work with choosen toolchain

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[BUG] Temp.zip cannot be accessed

Describe the issue
Whenever I attempt to customize sunsetHUD and then install it, I get the following error message:
An error occurred while installing sunsethud. Access to the path C:\Users\Sauce\Documents\tf2-hud-editor\temp.zip is denied.
Steps to reproduce
Steps to reproduce the issue:

Open the HUD Editor
Customize sunset HUD then install it

Screenshots
Can't upload for some reason.
Desktop (please complete the following information):

OS: Windows 10 x64
App Version: 2.4 (Latest on Gamebanana)
Selected HUD: sunsethud

Just so you know, creating a folder of any kind does not fix this issue.
Also, the button used to visit the github (in the editor) doesn't work for some reason. Neither do the Huds.tf, discord, steam, documentation, report an issue, buttons work.

Does it work if you run the app as administrator?

No, nothing I do works.

Does it work if you run the app as administrator?

It would be nice to know if you're working on a fix for this since this makes the program completely unusable for me.

It would be nice to know if you're working on a fix for this since this makes the program completely unusable for me.

Right now we're trying to reproduce the error to then find the root cause of the issue. Until then you're just gonna have to wait.

I have not been able to reproduce any of the issues you've reported nor have I had anyone else report something similar regarding sunset Hud or other HUDs supported by the editor. My advise would be to download the latest version here: https://github.com/CriticalFlaw/TF2HUD.Editor/releases/latest extract the folder into somewhere accessible like Desktop and try again. The only thing that makes sense is that you have limited access to your machine and it's preventing you from using the affected features.

My SSD is dying right now so this'll have to wait until I get my new SSD.

Any update on reproducing this issue?


Missing version from manifest

Version is required and will be enforced in future versions.
https://developers.home-assistant.io/docs/creating_integration_manifest/#version
2021-05-11 13:15:14 WARNING (MainThread) [homeassistant.loader] You are using a custom integration vantage which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-05-11 13:15:14 ERROR (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'vantage'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'vantage'

Already fixed.


Not working on WinXP

Hello. Tried to run your game - got an error: "G_SIM.exe is not Win32 application"

Did you compile from source? If not, where did you get the executable from? Obviously XP is not supported anymore so compiler settings often need a fiddle to get games to work on XP


[Idea for testing scenario] drag & drop

https://twitter.com/uninen/status/1479811616699043840

1.13 release introduced programmatic drag-and-drop support via the page.dragAndDrop(source, target[, options]) API.


python311Packages.aiohttp-socks: 0.8.3 -> 0.8.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.aiohttp-socks is: SOCKS proxy connector for aiohttp
meta.homepage for python311Packages.aiohttp-socks is: https://github.com/romis2012/aiohttp-socks
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.3 with grep in /nix/store/xgfslipfksdgxwp6w3mbjws8bqjsgsr2-python3.11-aiohttp-socks-0.8.3
found 0.8.3 in filename of file in /nix/store/xgfslipfksdgxwp6w3mbjws8bqjsgsr2-python3.11-aiohttp-socks-0.8.3

Rebuild report (if merged into master) (click to expand)

16 total rebuild path(s)

16 package rebuild(s)

First fifty rebuilds by attrpath
electrum
electrum-grs
electrum-ltc
maigret
matrix-commander
mirage-im
opsdroid
pantalaimon
pantalaimon-headless
python310Packages.aiogram
python310Packages.aiohttp-socks
python310Packages.matrix-nio
python311Packages.aiogram
python311Packages.aiohttp-socks
python311Packages.matrix-nio
weechatScripts.weechat-matrix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xgfslipfksdgxwp6w3mbjws8bqjsgsr2-python3.11-aiohttp-socks-0.8.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.aiohttp-socks https://github.com/r-ryantm/nixpkgs/archive/00a9d54648c07378ed5c558241055f40648a9e8b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xgfslipfksdgxwp6w3mbjws8bqjsgsr2-python3.11-aiohttp-socks-0.8.3
ls -la /nix/store/xgfslipfksdgxwp6w3mbjws8bqjsgsr2-python3.11-aiohttp-socks-0.8.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

16 packages built:

electrum
electrum-grs
electrum-ltc
maigret
matrix-commander
mirage-im
opsdroid
pantalaimon
pantalaimon-headless
python310Packages.aiogram
python310Packages.aiohttp-socks
python310Packages.matrix-nio
python311Packages.aiogram
python311Packages.aiohttp-socks
python311Packages.matrix-nio
weechatScripts.weechat-matrix

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.aiohttp-socks is: SOCKS proxy connector for aiohttp
meta.homepage for python311Packages.aiohttp-socks is: https://github.com/romis2012/aiohttp-socks
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.4 with grep in /nix/store/0lggd33idc6834vkp056p4aif7h238ql-python3.11-aiohttp-socks-0.8.4
found 0.8.4 in filename of file in /nix/store/0lggd33idc6834vkp056p4aif7h238ql-python3.11-aiohttp-socks-0.8.4

Rebuild report (if merged into master) (click to expand)

15 total rebuild path(s)

15 package rebuild(s)

First fifty rebuilds by attrpath
electrum
electrum-grs
electrum-ltc
home-assistant-component-tests.matrix
matrix-commander
mirage-im
opsdroid
pantalaimon-headless
python310Packages.aiogram
python310Packages.aiohttp-socks
python310Packages.matrix-nio
python311Packages.aiogram
python311Packages.aiohttp-socks
python311Packages.matrix-nio
weechatScripts.weechat-matrix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0lggd33idc6834vkp056p4aif7h238ql-python3.11-aiohttp-socks-0.8.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.aiohttp-socks https://github.com/r-ryantm/nixpkgs/archive/7ce93173d7fb9625e8bff1b945288e1afc949ceb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7ce93173d7fb9625e8bff1b945288e1afc949ceb#python311Packages.aiohttp-socks

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0lggd33idc6834vkp056p4aif7h238ql-python3.11-aiohttp-socks-0.8.4
ls -la /nix/store/0lggd33idc6834vkp056p4aif7h238ql-python3.11-aiohttp-socks-0.8.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings

https://github.com/NixOS/nixpkgs/pull/259006 may be the better upgrade.

Already on staging-next: https://github.com/NixOS/nixpkgs/commit/df2813e2d2882d7e2977be602a684a03afd2bc9f


Add support for alternate volume storage controllers

You might have to bare with me on this one!
This PR adds support for changing the type of storage controller that is added by beaker-vagrant when using the "volumes" support. This is necessary because not all vagrant boxes support IntelAHCI (the type that beaker-vagrant was using).
This PR adds support for LSILogic, PIIX, USB and retains the existing support for IntelAHCI. If you select USB as the controller type, it also ensures that USB is enabled on the VM (without enabling EHCI or XHCI, both of which may require a license from Oracle for the extension pack if you use them).
It also adds some unit tests for volumes support. I'd love to add some integration tests for this too, but that started to blow my mind, and there are currently none for "volumes" anyway.

Can one of the admins verify this patch?

Jenkins, test this please

@ericwilliamson do you need me to do anything else to this before it can be merged?

the code looks good @beezly 👍 . To match our contributor guidelines, please pre-pend your git commit message with (MAINT), then you should be ready for merging!

@kevpl thanks :) That's done.

👍

@beezly Thanks for the contribution! The gem has been released as 0.3.0:
https://github.com/puppetlabs/beaker-vagrant/releases/tag/0.3.0
https://rubygems.org/gems/beaker-vagrant/


After adding angle constraints, the drone orientation will stuck on certain value.

When hit the boundary, I will manually set the rpy-rate to zero. But now it seems that the rpy rate has kept to zero for a long time.

Problem: does not control the yaw angle of the robot.

Problem resolved: by enabling the angular velocity to adapt to a larger value.


[Bug] [Seatunnel Engine] Unable to get S3 Source in local mode

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I'm fetching data from S3 with Seatunnel local engine, but I'm facing the following issue,
The log is repeatedly reported ↓
2023-02-15 09:22:23,813 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1]
***********************************************
     CoordinatorService Thread Pool Status
***********************************************
activeCount               :                   0
corePoolSize              :                   0
maximumPoolSize           :<PHONE_NUMBER>
poolSize                  :                   0
completedTaskCount        :                   0
taskCount                 :                   0
***********************************************

SeaTunnel Version
2.3.0
SeaTunnel Config
env {
  execution.parallelism = 1
  job.mode = "STREAMING"
}

source {
  S3File {
        path = "/Database/dfs/news_daily_202302021200"
        type = "parquet"
        access_key = "xxxx"
        secret_key = "xxxx"
        bucket = "s3a://com.xxx.data.prd"
      }

}

transform {

}

sink {
  Console{}
}

Running Command
./bin/seatunnel.sh --config ./config/seatunnel.streaming.conf.template -e local

Error Exception
JAVA_OPTS:  -Dhazelcast.client.config=/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast-client.yaml -Dseatunnel.config=/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/seatunnel.yaml -Dhazelcast.config=/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast.yaml -Dlog4j2.configurationFile=/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/log4j2_client.properties -Dseatunnel.logs.path=/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/logs -Dseatunnel.logs.file_name=seatunnel-starter-client-1676424120000
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Loading configuration '/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/seatunnel.yaml' from System property 'seatunnel.config'
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Using configuration file at /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/seatunnel.yaml
二月 15, 2023 9:22:02 上午 org.apache.seatunnel.engine.common.config.SeaTunnelConfig
信息: seatunnel.home is /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Loading configuration '/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast.yaml' from System property 'hazelcast.config'
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Using configuration file at /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast.yaml
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Loading configuration '/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/seatunnel.yaml' from System property 'seatunnel.config'
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Using configuration file at /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/seatunnel.yaml
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Loading configuration '/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast.yaml' from System property 'hazelcast.config'
二月 15, 2023 9:22:02 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Using configuration file at /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast.yaml
2023-02-15 09:22:02,989 WARN  com.hazelcast.instance.AddressPicker - [LOCAL] [seatunnel_default_cluster-171793] [5.1] You configured your member address as host name. Please be aware of that your dns can be spoofed. Make sure that your dns configurations are correct.
2023-02-15 09:22:02,994 INFO  com.hazelcast.instance.AddressPicker - [LOCAL] [seatunnel_default_cluster-171793] [5.1] Resolving domain name 'localhost' to address(es): [<IP_ADDRESS>, 0:0:0:0:0:0:0:1]
2023-02-15 09:22:02,994 INFO  com.hazelcast.instance.AddressPicker - [LOCAL] [seatunnel_default_cluster-171793] [5.1] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [localhost/<IP_ADDRESS>, localhost/0:0:0:0:0:0:0:1]
2023-02-15 09:22:03,023 INFO  org.apache.seatunnel.engine.server.SeaTunnelServer - SeaTunnel server start...
2023-02-15 09:22:03,024 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Based on Hazelcast IMDG version: 5.1.0 (20220228 - 21f20e7)
2023-02-15 09:22:03,024 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Cluster name: seatunnel_default_cluster-171793
2023-02-15 09:22:03,024 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1]

 _____               _____                             _
/  ___|             |_   _|                           | |
\ `--.   ___   __ _   | |   _   _  _ __   _ __    ___ | |
 `--. \ / _ \ / _` |  | |  | | | || '_ \ | '_ \  / _ \| |
/\__/ /|  __/| (_| |  | |  | |_| || | | || | | ||  __/| |
\____/  \___| \__,_|  \_/   \__,_||_| |_||_| |_| \___||_|

2023-02-15 09:22:03,024 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Copyright © 2021-2022 The Apache Software Foundation. Apache SeaTunnel, SeaTunnel, and its feather logo are trademarks of The Apache Software Foundation.
2023-02-15 09:22:03,024 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Integrity Checker is disabled. Fail-fast on corrupted executables will not be performed.
To enable integrity checker do one of the following:
  - Change member config using Java API: config.setIntegrityCheckerEnabled(true);
  - Change XML/YAML configuration property: Set hazelcast.integrity-checker.enabled to true
  - Add system property: -Dhz.integritychecker.enabled=true (for Hazelcast embedded, works only when loading config via Config.load)
  - Add environment variable: HZ_INTEGRITYCHECKER_ENABLED=true (recommended when running container image. For Hazelcast embedded, works only when loading config via Config.load)
2023-02-15 09:22:03,027 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] The Jet engine is disabled.
To enable the Jet engine on the members, do one of the following:
  - Change member config using Java API: config.getJetConfig().setEnabled(true)
  - Change XML/YAML configuration property: Set hazelcast.jet.enabled to true
  - Add system property: -Dhz.jet.enabled=true (for Hazelcast embedded, works only when loading config via Config.load)
  - Add environment variable: HZ_JET_ENABLED=true (recommended when running container image. For Hazelcast embedded, works only when loading config via Config.load)
2023-02-15 09:22:03,583 INFO  com.hazelcast.system.security - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Enable DEBUG/FINE log level for log category com.hazelcast.system.security  or use -Dhazelcast.security.recommendations system property to see 🔒 security recommendations and the status of current config.
2023-02-15 09:22:03,639 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Using TCP/IP discovery
2023-02-15 09:22:03,639 WARN  com.hazelcast.cp.CPSubsystem - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
2023-02-15 09:22:03,802 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Created new BusWork :<PHONE_NUMBER>
2023-02-15 09:22:03,806 WARN  org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed send heartbeat to resource manager, will retry later. this address: [localhost]:5801
2023-02-15 09:22:03,807 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1]
***********************************************
     CoordinatorService Thread Pool Status
***********************************************
activeCount               :                   0
corePoolSize              :                   0
maximumPoolSize           :<PHONE_NUMBER>
poolSize                  :                   0
completedTaskCount        :                   0
taskCount                 :                   0
***********************************************

2023-02-15 09:22:03,814 WARN  org.apache.seatunnel.common.utils.RetryUtils - Failed to execute due to null. Retrying attempt (1/20) after backoff of 1000 ms
2023-02-15 09:22:03,855 INFO  com.hazelcast.internal.diagnostics.Diagnostics - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
2023-02-15 09:22:03,869 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] [localhost]:5801 is STARTING
2023-02-15 09:22:03,911 INFO  com.hazelcast.internal.cluster.ClusterService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1]

Members {size:1, ver:1} [
	Member [localhost]:5801 - db486095-d8c6-4073-9a10-d5339a429d4f this
]

2023-02-15 09:22:03,921 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] [localhost]:5801 is STARTED
二月 15, 2023 9:22:03 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Loading configuration '/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast-client.yaml' from System property 'hazelcast.client.config'
二月 15, 2023 9:22:03 上午 com.hazelcast.internal.config.AbstractConfigLocator
信息: Using configuration file at /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/config/hazelcast-client.yaml
2023-02-15 09:22:03,997 INFO  com.hazelcast.client.impl.spi.ClientInvocationService - hz.client_1 [seatunnel_default_cluster-171793] [5.1] Running with 2 response threads, dynamic=true
2023-02-15 09:22:04,017 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel_default_cluster-171793] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is STARTING
2023-02-15 09:22:04,017 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel_default_cluster-171793] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is STARTED
2023-02-15 09:22:04,026 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel_default_cluster-171793] [5.1] Trying to connect to cluster: seatunnel_default_cluster-171793
2023-02-15 09:22:04,028 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel_default_cluster-171793] [5.1] Trying to connect to [localhost]:5801
2023-02-15 09:22:04,052 INFO  com.hazelcast.client.impl.protocol.task.AuthenticationMessageTask - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Received auth from Connection[id=1, /<IP_ADDRESS>:5801->/<IP_ADDRESS>:54634, qualifier=null, endpoint=[<IP_ADDRESS>]:54634, remoteUuid=df25825c-3c65-49a9-9c36-921735b759bd, alive=true, connectionType=JVM, planeIndex=-1], successfully authenticated, clientUuid: df25825c-3c65-49a9-9c36-921735b759bd, client name: hz.client_1, client version: 5.1
2023-02-15 09:22:04,057 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel_default_cluster-171793] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is CLIENT_CONNECTED
2023-02-15 09:22:04,057 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel_default_cluster-171793] [5.1] Authenticated with server [localhost]:5801:db486095-d8c6-4073-9a10-d5339a429d4f, server version: 5.1, local address: /<IP_ADDRESS>:54634
2023-02-15 09:22:04,058 INFO  com.hazelcast.internal.diagnostics.Diagnostics - hz.client_1 [seatunnel_default_cluster-171793] [5.1] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
2023-02-15 09:22:04,065 INFO  com.hazelcast.client.impl.spi.ClientClusterService - hz.client_1 [seatunnel_default_cluster-171793] [5.1]

Members [1] {
	Member [localhost]:5801 - db486095-d8c6-4073-9a10-d5339a429d4f
}

2023-02-15 09:22:04,080 INFO  com.hazelcast.client.impl.statistics.ClientStatisticsService - Client statistics is enabled with period 5 seconds.
2023-02-15 09:22:04,213 INFO  org.apache.seatunnel.engine.client.job.JobExecutionEnvironment - add common jar in plugins :[file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/aws-java-sdk-s3-1.11.1000.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/aws-java-sdk-bundle-1.12.262.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-client-2.10.2.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-aws-3.3.4.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-aws-2.10.2.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/jdbc/lib/postgresql-42.5.2.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-common-3.3.4.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-client-3.3.4.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/aws-java-sdk-core-1.11.1000.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-shaded-guava-1.1.1.jar, file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/plugins/hadoop-common-2.10.2.jar]
2023-02-15 09:22:04,215 INFO  org.apache.seatunnel.core.starter.config.ConfigBuilder - Loading config file: ./config/seatunnel.streaming.conf.template
2023-02-15 09:22:04,249 INFO  org.apache.seatunnel.core.starter.config.ConfigBuilder - parsed config file: {
    "env" : {
        "execution.parallelism" : 1,
        "job.mode" : "STREAMING"
    },
    "source" : [
        {
            "bucket" : "s3a://com.xxxx.data.prd",
            "hadoop_s3_properties" : {
                "fs.s3a.aws.credentials.provider" : "org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider"
            },
            "path" : "/Database/dfs/news_daily_202302021200",
            "secret_key" : "3doxxxxxxxxOH3W",
            "access_key" : "AKxxxxx",
            "type" : "parquet",
            "plugin_name" : "S3File"
        }
    ],
    "transform" : [],
    "sink" : [
        {
            "plugin_name" : "Console"
        }
    ]
}

2023-02-15 09:22:04,269 INFO  org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery - Load SeaTunnelSource Plugin from /Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/connectors/seatunnel
2023-02-15 09:22:04,286 INFO  org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery - Discovery plugin jar: S3File at: file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/connectors/seatunnel/connector-file-s3-2.3.0.jar
2023-02-15 09:22:04,300 INFO  org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery - Load plugin: PluginIdentifier{engineType='seatunnel', pluginType='source', pluginName='S3File'} from path: file:/Users/xiehang/Desktop/developer/apache-seatunnel-incubating-2.3.0/connectors/seatunnel/connector-file-s3-2.3.0.jar use classloader: sun.misc.Launcher$AppClassLoader
2023-02-15 09:22:04,567 WARN  org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2023-02-15 09:22:04,820 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] This node become a new active master node, begin init coordinator service
2023-02-15 09:22:04,841 WARN  org.apache.hadoop.metrics2.impl.MetricsConfig - Cannot locate configuration: tried hadoop-metrics2-s3a-file-system.properties,hadoop-metrics2.properties
2023-02-15 09:22:04,875 INFO  org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Scheduled Metric snapshot period at 10 second(s).
2023-02-15 09:22:04,875 INFO  org.apache.hadoop.metrics2.impl.MetricsSystemImpl - s3a-file-system metrics system started
2023-02-15 09:22:05,002 INFO  com.hazelcast.internal.partition.impl.PartitionStateManager - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1] Initializing cluster partition table arrangement...
2023-02-15 09:22:05,880 INFO  org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received new worker register: [localhost]:5801
2023-02-15 09:22:13,818 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1]
***********************************************
     CoordinatorService Thread Pool Status
***********************************************
activeCount               :                   0
corePoolSize              :                   0
maximumPoolSize           :<PHONE_NUMBER>
poolSize                  :                   0
completedTaskCount        :                   0
taskCount                 :                   0
***********************************************

2023-02-15 09:22:23,813 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel_default_cluster-171793] [5.1]
***********************************************
     CoordinatorService Thread Pool Status
***********************************************
activeCount               :                   0
corePoolSize              :                   0
maximumPoolSize           :<PHONE_NUMBER>
poolSize                  :                   0
completedTaskCount        :                   0
taskCount                 :                   0
***********************************************

Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Change the job.mode from STEAMING to BATCH

Change the job.mode from STEAMING to BATCH

After modifying the job.mode I got another error about package dependency.
I want to know which jar packages I need to get the S3 source.
this is the jar package I put in the lib directory
aws-java-sdk-bundle-1.12.262.jar                hadoop-aws-2.10.2.jar                           hadoop-shaded-guava-1.1.1.jar
aws-java-sdk-core-1.11.1000.jar                 hadoop-client-2.10.2.jar
aws-java-sdk-s3-1.11.1000.jar                   hadoop-common-2.10.2.jar                        seatunnel-hadoop3-3.1.4-uber-2.3.0-optional.jar

Exception in thread "main" java.lang.NoSuchMethodError: com.amazonaws.http.HttpResponse.getHttpRequest()Lorg/apache/http/client/methods/HttpRequestBase;
	at com.amazonaws.services.s3.internal.S3ObjectResponseHandler.handle(S3ObjectResponseHandler.java:57)
	at com.amazonaws.services.s3.internal.S3ObjectResponseHandler.handle(S3ObjectResponseHandler.java:29)
	at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:69)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1794)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleSuccessResponse(AmazonHttpClient.java:1477)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1384)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1157)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:814)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:781)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:755)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:715)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:697)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:561)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:541)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5445)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5392)
	at com.amazonaws.services.s3.AmazonS3Client.getObject(AmazonS3Client.java:1519)
	at org.apache.hadoop.fs.s3a.S3AInputStream.reopen(S3AInputStream.java:169)
	at org.apache.hadoop.fs.s3a.S3AInputStream.lazySeek(S3AInputStream.java:305)
	at org.apache.hadoop.fs.s3a.S3AInputStream.read(S3AInputStream.java:330)
	at java.io.FilterInputStream.read(FilterInputStream.java:83)
	at org.apache.seatunnel.shade.connector.file.org.apache.parquet.io.DelegatingSeekableInputStream.read(DelegatingSeekableInputStream.java:61)
	at org.apache.seatunnel.shade.connector.file.org.apache.parquet.bytes.BytesUtils.readIntLittleEndian(BytesUtils.java:83)
	at org.apache.seatunnel.shade.connector.file.org.apache.parquet.hadoop.ParquetFileReader.readFooter(ParquetFileReader.java:548)
	at org.apache.seatunnel.shade.connector.file.org.apache.parquet.hadoop.ParquetFileReader.<init>(ParquetFileReader.java:777)
	at org.apache.seatunnel.shade.connector.file.org.apache.parquet.hadoop.ParquetFileReader.open(ParquetFileReader.java:646)
	at org.apache.seatunnel.connectors.seatunnel.file.source.reader.ParquetReadStrategy.getSeaTunnelRowTypeInfo(ParquetReadStrategy.java:209)
	at org.apache.seatunnel.connectors.seatunnel.file.s3.source.S3FileSource.prepare(S3FileSource.java:96)
	at org.apache.seatunnel.engine.core.parse.ConnectorInstanceLoader.loadSourceInstance(ConnectorInstanceLoader.java:60)
	at org.apache.seatunnel.engine.core.parse.JobConfigParser.sampleAnalyze(JobConfigParser.java:314)
	at org.apache.seatunnel.engine.core.parse.JobConfigParser.parse(JobConfigParser.java:125)
	at org.apache.seatunnel.engine.client.job.JobExecutionEnvironment.getLogicalDag(JobExecutionEnvironment.java:129)
	at org.apache.seatunnel.engine.client.job.JobExecutionEnvironment.execute(JobExecutionEnvironment.java:121)
	at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:91)
	at org.apache.seatunnel.core.starter.Seatunnel.run(Seatunnel.java:39)
	at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:31)

https://seatunnel.apache.org/docs/2.3.0/connector-v2/source/S3File

https://seatunnel.apache.org/docs/2.3.0/connector-v2/source/S3File

This guide only adds two jar packages( hadoop-aws.jar、hadoop-client.jar),  but it is not enough to actually run it, the following are the packages I have added to {seatunnel_home}/lib or {seatunnel_home}/plugins
aws-java-sdk-bundle-1.12.262.jar                hadoop-aws-2.10.2.jar                           hadoop-shaded-guava-1.1.1.jar
aws-java-sdk-core-1.11.1000.jar                 hadoop-client-2.10.2.jar
aws-java-sdk-s3-1.11.1000.jar                   hadoop-common-2.10.2.jar                        seatunnel-hadoop3-3.1.4-uber-2.3.0-optional.jar

cc @EricJoy2048 @CalvinKirs

Have you solved it yet?

Hi, has nearly the same error with s3 test.
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2023-11-29 23:06:48,734 WARN  org.apache.seatunnel.core.starter.seatunnel.args.ClientCommandArgs$MasterTypeValidator -
******************************************************************************************
-e and --deploy-mode deprecated in 2.3.1, please use -m and --master instead of it
******************************************************************************************
нояб. 29, 2023 11:06:48 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Loading configuration '/Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/seatunnel.yaml' from System property 'seatunnel.config'
нояб. 29, 2023 11:06:48 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Using configuration file at /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/seatunnel.yaml
нояб. 29, 2023 11:06:48 PM org.apache.seatunnel.engine.common.config.SeaTunnelConfig
INFO: seatunnel.home is /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3
нояб. 29, 2023 11:06:48 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Loading configuration '/Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/hazelcast.yaml' from System property 'hazelcast.config'
нояб. 29, 2023 11:06:48 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Using configuration file at /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/hazelcast.yaml
нояб. 29, 2023 11:06:49 PM com.hazelcast.instance.impl.HazelcastInstanceFactory
WARNING: Hazelcast is starting in a Java modular environment (Java 9 and newer) but without proper access to required Java packages. Use additional Java arguments to provide Hazelcast access to Java internal API. The internal API access is used to get the best performance results. Arguments to be used:
 --add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
2023-11-29 23:06:49,150 WARN  com.hazelcast.instance.AddressPicker - [LOCAL] [seatunnel-611685] [5.1] You configured your member address as host name. Please be aware of that your dns can be spoofed. Make sure that your dns configurations are correct.
2023-11-29 23:06:49,150 INFO  com.hazelcast.instance.AddressPicker - [LOCAL] [seatunnel-611685] [5.1] Resolving domain name 'localhost' to address(es): [<IP_ADDRESS>, 0:0:0:0:0:0:0:1]
2023-11-29 23:06:49,151 INFO  com.hazelcast.instance.AddressPicker - [LOCAL] [seatunnel-611685] [5.1] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [localhost/<IP_ADDRESS>, localhost/0:0:0:0:0:0:0:1]
2023-11-29 23:06:49,205 INFO  org.apache.seatunnel.engine.server.SeaTunnelServer - SeaTunnel server start...
2023-11-29 23:06:49,207 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel-611685] [5.1] Based on Hazelcast IMDG version: 5.1.0 (20220228 - 21f20e7)
2023-11-29 23:06:49,207 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel-611685] [5.1] Cluster name: seatunnel-611685
2023-11-29 23:06:49,207 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel-611685] [5.1]

 _____               _____                             _
/  ___|             |_   _|                           | |
\ `--.   ___   __ _   | |   _   _  _ __   _ __    ___ | |
 `--. \ / _ \ / _` |  | |  | | | || '_ \ | '_ \  / _ \| |
/\__/ /|  __/| (_| |  | |  | |_| || | | || | | ||  __/| |
\____/  \___| \__,_|  \_/   \__,_||_| |_||_| |_| \___||_|

2023-11-29 23:06:49,207 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel-611685] [5.1] Copyright © 2021-2022 The Apache Software Foundation. Apache SeaTunnel, SeaTunnel, and its feather logo are trademarks of The Apache Software Foundation.
2023-11-29 23:06:49,207 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel-611685] [5.1] Integrity Checker is disabled. Fail-fast on corrupted executables will not be performed.
To enable integrity checker do one of the following:
  - Change member config using Java API: config.setIntegrityCheckerEnabled(true);
  - Change XML/YAML configuration property: Set hazelcast.integrity-checker.enabled to true
  - Add system property: -Dhz.integritychecker.enabled=true (for Hazelcast embedded, works only when loading config via Config.load)
  - Add environment variable: HZ_INTEGRITYCHECKER_ENABLED=true (recommended when running container image. For Hazelcast embedded, works only when loading config via Config.load)
2023-11-29 23:06:49,210 INFO  com.hazelcast.system - [localhost]:5801 [seatunnel-611685] [5.1] The Jet engine is disabled.
To enable the Jet engine on the members, do one of the following:
  - Change member config using Java API: config.getJetConfig().setEnabled(true)
  - Change XML/YAML configuration property: Set hazelcast.jet.enabled to true
  - Add system property: -Dhz.jet.enabled=true (for Hazelcast embedded, works only when loading config via Config.load)
  - Add environment variable: HZ_JET_ENABLED=true (recommended when running container image. For Hazelcast embedded, works only when loading config via Config.load)
2023-11-29 23:06:49,613 INFO  com.hazelcast.system.security - [localhost]:5801 [seatunnel-611685] [5.1] Enable DEBUG/FINE log level for log category com.hazelcast.system.security  or use -Dhazelcast.security.recommendations system property to see 🔒 security recommendations and the status of current config.
2023-11-29 23:06:49,683 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-611685] [5.1] Using TCP/IP discovery
2023-11-29 23:06:49,684 WARN  com.hazelcast.cp.CPSubsystem - [localhost]:5801 [seatunnel-611685] [5.1] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
нояб. 29, 2023 11:06:49 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Loading configuration '/Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/seatunnel.yaml' from System property 'seatunnel.config'
нояб. 29, 2023 11:06:49 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Using configuration file at /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/seatunnel.yaml
нояб. 29, 2023 11:06:49 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Loading configuration '/Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/hazelcast.yaml' from System property 'hazelcast.config'
нояб. 29, 2023 11:06:49 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Using configuration file at /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/hazelcast.yaml
2023-11-29 23:06:49,872 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-611685] [5.1] Created new BusWork :<PHONE_NUMBER>
2023-11-29 23:06:49,872 WARN  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-611685] [5.1] The Node is not ready yet, Node state STARTING,looking forward to the next scheduling
2023-11-29 23:06:49,908 WARN  org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - failed send heartbeat to resource manager, will retry later. this address: [localhost]:5801
2023-11-29 23:06:49,913 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel-611685] [5.1]
***********************************************
     CoordinatorService Thread Pool Status
***********************************************
activeCount               :                   0
corePoolSize              :                   0
maximumPoolSize           :<PHONE_NUMBER>
poolSize                  :                   0
completedTaskCount        :                   0
taskCount                 :                   0
***********************************************

2023-11-29 23:06:49,941 INFO  com.hazelcast.internal.diagnostics.Diagnostics - [localhost]:5801 [seatunnel-611685] [5.1] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
2023-11-29 23:06:49,946 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5801 is STARTING
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5820 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5825 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5822 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5815 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5804 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5819 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5810 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5817 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5808 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5813 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5802 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5821 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5823 is added to the blacklist.
2023-11-29 23:06:49,992 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5812 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5829 is added to the blacklist.
2023-11-29 23:06:49,992 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5811 is added to the blacklist.
2023-11-29 23:06:49,992 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5807 is added to the blacklist.
2023-11-29 23:06:49,992 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5809 is added to the blacklist.
2023-11-29 23:06:49,991 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5806 is added to the blacklist.
2023-11-29 23:06:49,992 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5803 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5828 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5824 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5826 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5814 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5816 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5805 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5818 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5827 is added to the blacklist.
2023-11-29 23:06:49,993 INFO  com.hazelcast.internal.cluster.impl.TcpIpJoiner - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5830 is added to the blacklist.
2023-11-29 23:06:50,987 INFO  com.hazelcast.internal.cluster.ClusterService - [localhost]:5801 [seatunnel-611685] [5.1]

Members {size:1, ver:1} [
	Member [localhost]:5801 - 17cac56e-7734-452f-a5e9-9a0a20dd0cc1 this
]

2023-11-29 23:06:50,997 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5801 is STARTED
нояб. 29, 2023 11:06:50 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Loading configuration '/Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/hazelcast-client.yaml' from System property 'hazelcast.client.config'
нояб. 29, 2023 11:06:50 PM com.hazelcast.internal.config.AbstractConfigLocator
INFO: Using configuration file at /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/config/hazelcast-client.yaml
2023-11-29 23:06:51,042 INFO  com.hazelcast.client.impl.spi.ClientInvocationService - hz.client_1 [seatunnel-611685] [5.1] Running with 2 response threads, dynamic=true
2023-11-29 23:06:51,053 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-611685] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is STARTING
2023-11-29 23:06:51,053 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-611685] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is STARTED
2023-11-29 23:06:51,058 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-611685] [5.1] Trying to connect to cluster: seatunnel-611685
2023-11-29 23:06:51,059 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-611685] [5.1] Trying to connect to [localhost]:5801
2023-11-29 23:06:51,071 INFO  com.hazelcast.client.impl.protocol.task.AuthenticationMessageTask - [localhost]:5801 [seatunnel-611685] [5.1] Received auth from Connection[id=1, /<IP_ADDRESS>:5801->/<IP_ADDRESS>:59440, qualifier=null, endpoint=[<IP_ADDRESS>]:59440, remoteUuid=f5ef88f3-edc9-485b-8e36-4a4cdd9de4c1, alive=true, connectionType=JVM, planeIndex=-1], successfully authenticated, clientUuid: f5ef88f3-edc9-485b-8e36-4a4cdd9de4c1, client name: hz.client_1, client version: 5.1
2023-11-29 23:06:51,073 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-611685] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is CLIENT_CONNECTED
2023-11-29 23:06:51,073 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-611685] [5.1] Authenticated with server [localhost]:5801:17cac56e-7734-452f-a5e9-9a0a20dd0cc1, server version: 5.1, local address: /<IP_ADDRESS>:59440
2023-11-29 23:06:51,075 INFO  com.hazelcast.internal.diagnostics.Diagnostics - hz.client_1 [seatunnel-611685] [5.1] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
2023-11-29 23:06:51,081 INFO  com.hazelcast.client.impl.spi.ClientClusterService - hz.client_1 [seatunnel-611685] [5.1]

Members [1] {
	Member [localhost]:5801 - 17cac56e-7734-452f-a5e9-9a0a20dd0cc1
}

2023-11-29 23:06:51,100 INFO  com.hazelcast.client.impl.statistics.ClientStatisticsService - Client statistics is enabled with period 5 seconds.
2023-11-29 23:06:51,250 INFO  org.apache.seatunnel.engine.client.job.JobExecutionEnvironment - add common jar in plugins :[]
2023-11-29 23:06:51,264 INFO  org.apache.seatunnel.core.starter.utils.ConfigBuilder - Loading config file from path: /Users/yuriygavrilov/git_project/SeaTunnel/data/seatunnel1.template
2023-11-29 23:06:51,311 INFO  org.apache.seatunnel.core.starter.utils.ConfigShadeUtils - Load config shade spi: [base64]
2023-11-29 23:06:51,347 INFO  org.apache.seatunnel.core.starter.utils.ConfigBuilder - Parsed config file: {
    "env" : {
        "execution.parallelism" : 1,
        "job.mode" : "BATCH"
    },
    "source" : [
        {
            "bucket" : "s3a://test",
            "path" : "/seatunnel/",
            "secret_key" : "XXX",
            "file_format_type" : "parquet",
            "access_key" : "XXX",
            "fs.s3a.aws.credentials.provider" : "org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider",
            "plugin_name" : "S3File",
            "fs.s3a.endpoint" : "XXX"
        }
    ],
    "transform" : [],
    "sink" : [
        {
            "plugin_name" : "Console"
        }
    ]
}

2023-11-29 23:06:51,371 INFO  org.apache.seatunnel.api.configuration.ReadonlyConfig - Config uses fallback configuration key 'plugin_name' instead of key 'factory'
2023-11-29 23:06:51,372 INFO  org.apache.seatunnel.api.configuration.ReadonlyConfig - Config uses fallback configuration key 'plugin_name' instead of key 'factory'
2023-11-29 23:06:51,376 INFO  org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery - Load SeaTunnelSink Plugin from /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/connectors/seatunnel
2023-11-29 23:06:51,381 INFO  org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery - Discovery plugin jar: Console at: file:/Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/connectors/seatunnel/connector-console-2.3.3.jar
2023-11-29 23:06:51,385 INFO  org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser - start generating all sources.
2023-11-29 23:06:51,386 INFO  org.apache.seatunnel.api.configuration.ReadonlyConfig - Config uses fallback configuration key 'plugin_name' instead of key 'factory'
2023-11-29 23:06:51,400 INFO  org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery - Load SeaTunnelSource Plugin from /Users/yuriygavrilov/git_project/SeaTunnel/apache-seatunnel-2.3.3/connectors/seatunnel
2023-11-29 23:06:51,408 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-611685] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is SHUTTING_DOWN
2023-11-29 23:06:51,411 INFO  com.hazelcast.internal.server.tcp.TcpServerConnection - [localhost]:5801 [seatunnel-611685] [5.1] Connection[id=1, /<IP_ADDRESS>:5801->/<IP_ADDRESS>:59440, qualifier=null, endpoint=[<IP_ADDRESS>]:59440, remoteUuid=f5ef88f3-edc9-485b-8e36-4a4cdd9de4c1, alive=false, connectionType=JVM, planeIndex=-1] closed. Reason: Connection closed by the other side
2023-11-29 23:06:51,411 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel-611685] [5.1] Removed connection to endpoint: [localhost]:5801:17cac56e-7734-452f-a5e9-9a0a20dd0cc1, connection: ClientConnection{alive=false, connectionId=1, channel=NioChannel{/<IP_ADDRESS>:59440->localhost/<IP_ADDRESS>:5801}, remoteAddress=[localhost]:5801, lastReadTime=2023-11-29 23:06:51.259, lastWriteTime=2023-11-29 23:06:51.258, closedTime=2023-11-29 23:06:51.409, connected server version=5.1}
2023-11-29 23:06:51,411 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-611685] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is CLIENT_DISCONNECTED
2023-11-29 23:06:51,413 INFO  com.hazelcast.client.impl.ClientEndpointManager - [localhost]:5801 [seatunnel-611685] [5.1] Destroying ClientEndpoint{connection=Connection[id=1, /<IP_ADDRESS>:5801->/<IP_ADDRESS>:59440, qualifier=null, endpoint=[<IP_ADDRESS>]:59440, remoteUuid=f5ef88f3-edc9-485b-8e36-4a4cdd9de4c1, alive=false, connectionType=JVM, planeIndex=-1], clientUuid=f5ef88f3-edc9-485b-8e36-4a4cdd9de4c1, clientName=hz.client_1, authenticated=true, clientVersion=5.1, creationTime=1701288411069, latest clientAttributes=lastStatisticsCollectionTime=1701288411100,enterprise=false,clientType=JVM,clientVersion=5.1,clusterConnectionTimestamp=1701288411060,clientAddress=<IP_ADDRESS>,clientName=hz.client_1,credentials.principal=null,os.committedVirtualMemorySize=0,os.freePhysicalMemorySize=210055168,os.freeSwapSpaceSize=0,os.maxFileDescriptorCount=0,os.openFileDescriptorCount=0,os.processCpuTime=0,os.systemLoadAverage=2.26611328125,os.totalPhysicalMemorySize=34359738368,os.totalSwapSpaceSize=0,runtime.availableProcessors=12,runtime.freeMemory=1006044032,runtime.maxMemory=1073741824,runtime.totalMemory=1073741824,runtime.uptime=3271,runtime.usedMemory=67697792, labels=[]}
2023-11-29 23:06:51,414 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel-611685] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is SHUTDOWN
2023-11-29 23:06:51,414 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed SeaTunnel client......
2023-11-29 23:06:51,414 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5801 is SHUTTING_DOWN
2023-11-29 23:06:51,416 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-611685] [5.1] Shutting down connection manager...
2023-11-29 23:06:51,418 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-611685] [5.1] Shutting down node engine...
2023-11-29 23:06:51,422 INFO  org.apache.seatunnel.engine.server.SeaTunnelServer - master node check interrupted
2023-11-29 23:06:53,638 INFO  com.hazelcast.instance.impl.NodeExtension - [localhost]:5801 [seatunnel-611685] [5.1] Destroying node NodeExtension.
2023-11-29 23:06:53,638 INFO  com.hazelcast.instance.impl.Node - [localhost]:5801 [seatunnel-611685] [5.1] Hazelcast Shutdown is completed in 2223 ms.
2023-11-29 23:06:53,638 INFO  com.hazelcast.core.LifecycleService - [localhost]:5801 [seatunnel-611685] [5.1] [localhost]:5801 is SHUTDOWN
2023-11-29 23:06:53,639 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed HazelcastInstance ......
2023-11-29 23:06:53,639 ERROR org.apache.seatunnel.core.starter.SeaTunnel -

===============================================================================

2023-11-29 23:06:53,639 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Fatal Error,

2023-11-29 23:06:53,639 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Please submit bug report in https://github.com/apache/seatunnel/issues

2023-11-29 23:06:53,639 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Reason:SeaTunnel job executed failed

2023-11-29 23:06:53,640 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Exception StackTrace:org.apache.seatunnel.core.starter.exception.CommandExecuteException: SeaTunnel job executed failed
	at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:191)
	at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
	at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34)
Caused by: java.lang.RuntimeException: Plugin PluginIdentifier{engineType='seatunnel', pluginType='source', pluginName='S3File'} not found.
	at org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery.createPluginInstance(AbstractPluginDiscovery.java:223)
	at org.apache.seatunnel.engine.core.parse.ConnectorInstanceLoader.loadSourceInstance(ConnectorInstanceLoader.java:61)
	at org.apache.seatunnel.engine.core.parse.JobConfigParser.parseSource(JobConfigParser.java:81)
	at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.parseSource(MultipleTableJobConfigParser.java:317)
	at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.parse(MultipleTableJobConfigParser.java:179)
	at org.apache.seatunnel.engine.core.job.AbstractJobEnvironment.getLogicalDag(AbstractJobEnvironment.java:109)
	at org.apache.seatunnel.engine.client.job.JobExecutionEnvironment.execute(JobExecutionEnvironment.java:73)
	at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:143)
	... 2 more

2023-11-29 23:06:53,641 ERROR org.apache.seatunnel.core.starter.SeaTunnel -
===============================================================================

Exception in thread "main" org.apache.seatunnel.core.starter.exception.CommandExecuteException: SeaTunnel job executed failed
	at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:191)
	at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
	at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34)
Caused by: java.lang.RuntimeException: Plugin PluginIdentifier{engineType='seatunnel', pluginType='source', pluginName='S3File'} not found.
	at org.apache.seatunnel.plugin.discovery.AbstractPluginDiscovery.createPluginInstance(AbstractPluginDiscovery.java:223)
	at org.apache.seatunnel.engine.core.parse.ConnectorInstanceLoader.loadSourceInstance(ConnectorInstanceLoader.java:61)
	at org.apache.seatunnel.engine.core.parse.JobConfigParser.parseSource(JobConfigParser.java:81)
	at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.parseSource(MultipleTableJobConfigParser.java:317)
	at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.parse(MultipleTableJobConfigParser.java:179)
	at org.apache.seatunnel.engine.core.job.AbstractJobEnvironment.getLogicalDag(AbstractJobEnvironment.java:109)
	at org.apache.seatunnel.engine.client.job.JobExecutionEnvironment.execute(JobExecutionEnvironment.java:73)
	at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:143)
	... 2 more


Make online version work in old browsers.

Fixes #371.

Depends on https://github.com/hildjj/node-inspect-extracted/issues/22

OK, I think we're there.  @polkovnikov-ph double check, please?


Added Metadata Plugin and documentation.

The Metadata Plugin adds SEO metadata, Open Graph metadata (the metadata most social platforms including Facebook use) and Twitter Cards specific metadata. The documentation is provided. So far I tested it with many different combinations of header data and keyword argument combinations. They all worked as intended.
Some notes on implementation:
The plugin activation needs to keyword arguments:
:twitter keyword argument sets "site" property of Twitter. (That is the Twitter account the Card is going to be bound to.)
Twitter Card specific metadata will be omitted if this property is not set because this option is mandatory.
:card keyword argument sets the type of Twitter card created.
Possible types are :summary and :image. Defaults to :summary.
The og:url property doesn't currently seem essential in coleslaw because a post has only one address. og:url (or twitter:url which defaults to og:url actually) is important when there are multiple url's to same post. But I added it as well just to make sure it is there when it becomes important.
I've seen your comment about twitter:url on twitter-summary-cards plugin which made me think if there is a pitfall to the seemingly obvious approach to getting the url. I would be happy to check my method and inform me if I am doing something wrong here: (concatenate 'string (domain *config*) "/" (namestring (page-url post)))
As with the twitter:url, some other properties like twitter:description are intentionally omitted, because those default to Open Graph tags that are already provided, which prevents duplication.
The description for Open Graph metadata is created from post content if not explicitly stated in post header because some platforms make it mandatory. But it is omitted from SEO description when not stated by user. Because Google is does a better job of crawling description strings from content than me. :) And also it is better SEO practice to not provide a description tag at all than coming up with a possible bad one. The content is stripped of markup tags and quotation marks first before added to metadata because Facebook doesn't hide tags when they explicitly exist in the description and quotations in the description break HTML file.
The SEO keywords are created from tags when they are not explicitly stated in post header.
The image to be used in sharing is either and absolute URL or a root-relative URL like /static/image.png
This plugin also makes the twitter-summary-card plugin unnecessary because it handles both summary card and summary card with large image types but you might want to keep it around in case it is already in people's configurations.

As can be seen from this plugin, plugins need to be able to add extra keywords to content classes. My method works in this context but things will get complicated when the number of content types increase and same plugin adds functionality to multiple content types.
A possibly more modular approach would be redefining content classes that are manipulated by the plugin from inside the plugin. But then if a user creates posts while using the plugin and then disable it, the parser is going to error for Invalid initialization argument for keywords that exist in post headers but absent from class description.
In that case we need to make parser more forgiving against post headers, which will cause coleslaw to skip typo errors in headers as well, which is bad.
So my best bet is to create a coleslaw:*valid-header-tags* variable that holds the list of all possible keywords that are used for all content types. Example:
(defvar *valid-header-tags*
             '((content . (:url :date :tags :text))
               (post . (:title :author :format :keywords :description :image :card :creator)
               (page . (:title :author)
               (shouts . (:title :author :format :link :image)))))

Every new plugin can register their respective header tags to this variable. The error checking for post headers can be done explicitly using this variable, first checking possible tags for content superclass, then the respective subclass.
This approach would possibly make it eaiser to add/delete/modify plugins in repository.

Hi thanks for the pull request. From my perspective, this is a feature that I would like to see in Coleslaw.
The main issue with the PR is that it modifies the post class instead of extending it, which there currently is no mechanism for.
One way to to allow the plugins to register 3rd party content classes would be to modifying discover. Currently discover takes the extension of the file as the name of the corresponding content class. We could add an extra layer of indirection by having a mapping between extensions. This would conflict with the current implementation of discover. So I propose the following changes:

Add an export a variable named file-extension-content-class. It would be an alist that maps file-extensions to classes.
The default discover method would iterate for all the extensions map to the doc-type.
Make construct a generic-function and export it, to have it as an extension point(?)
Maybe do the same for add-document (?).

If @kingcons amenable to the PR I'm willing the implement the aforementioned changes and update the PR to use it..
On a more general note consider adding docstrings to functions and variables. I'll comment on other specific details in the file as well.
my 2c and Thank you again for your interest in Coleslaw

Thank you very much for the warm welcome! :) My interest is not new tho, I've been using coleslaw for a years now. :)) Great piece of software really.
And thank you for the comments! Especially for the line-by-line review. I'll revise the PR accordingly.
Even though I am a huge fan of literate programming practices (as can be seen here) I feel like it is a little overkill adding docstrings to functions defined in this commit. Their functionality is obvious from the function names and none of them are exported. The docstrings will look like function names. But generally, I actually love docstrings. :)
About the modifying class problem, that was exactly my point in my second comment to the PR. But as you mentioned there is no extension mechanism right now, and even if there was, file-extension content-class mapping mechanism is not the only change that is needed for making it work. Parser should also be modified to accept all possible keywords that are provided in content extension plugins instead of only the ones that are enabled. I am 100% with you on the need to have a formal way of extending content classes (again, my second comment) but I think doing this properly is going to take some more planning.
Meanwhile, the PR doesn't break anything, the functionality is complete, and the protocol is pretty solid. So it is not going to break anything if we isolate it from the post class when the content class extension mechanism is added. The PR modifies the class directly only by extending it. It doesn't touch any of the already available functionality. And all the slots that are added by the PR are completely optional. They break neither past content created by users nor risk breaking compability in the future.
So I would say we merge it, and we can simply cut paste the added slots to extension mechanism in the plugin file when we add the extension mechanism.

As a side note, about the one-legged if: I can change it if that is the convention of the repository but I generally consider ifto be much more suitable (even when it is one-legged and nil return is not explicitly stated) than when in situations where return value (not side-effects) is essential to the expression. A when macro implies side-effects, it is specifically created to support eval of multiple statements when the condition is true. Even the name of the macro doesn't seem fitting inside a setter.
I think I will make if return nil for false explicitly instead of switching to when.

Btw, I am only a collaborator, so I don't want my comments to come off as unnecessarily antagonistic. The final decision is in hands of @kingcons

I feel like it is a little overkill adding docstrings to functions

This goes against my experience. When I'm other peoples code, the absence of docstrings complicates the initial understanding. Sure I can use slime-xref functionality to see where the variable or function is used and understand its purpose but the docstring can save time an facilitate the understanding of the codebase. As Coleslaw strives for being easy to hack, docstring coverage should aim for 100% imho.
I forgot to add that your valid header tags suggestion is spot on. I'll try to implement it asap.
Regarding the if, I prefer to use when/unless for one branch statements as the reader does not have to read the forms to know if there is an else form.

A when macro implies side-effects,

That is not an assumption I've seen when reading CL code in the wild, although when/unless is common when writing imperative code.

So I would say we merge it, and we can simply cut paste the added slots to extension mechanism in the plugin file when we add the extension mechanism.

I'll defer that decision to @kingcons, My goal was to give you prompt feedback so that you don't feel that your contribution is not ignored.

I felt no antagonism at all. Sorry if I sound offended. I wasn't. I think it is great that you are pushing for perfect commits. I was just stating the reasoning behind my decisions for the code. Actually you made me change my mind. I am writing a content extension system right now. It is shaping up pretty nicely IMHO.
So I suggest delaying this PR just a little bit more so I can see if the extension system works as expected. If it does, I will make a PR out of it so we can discuss if it makes sense. If it gets accepted I will also modify this branch for the extension system. If it doesn't then we can talk about if we should wait for the extension system or not.

Hey all, sorry I'm late to this thread.
@kenanb This is valuable work and thank you for writing good documentation and a well-explained PR! :tada: :cake: :cocktail:
@PuercoPop Thanks for giving this a first look over and providing Kenan with good feedback.
I'll ask one question up front and then follow up on the three major points of contention I've noticed. (If there are others I've missed, please say so!)
My question: Should this supersede/replace the existing twitter-summary-cards plugin or should they coexist? I assume this is a complete superset of the functionality, is that right?

As Coleslaw strives for being easy to hack, docstring coverage should aim for 100% imho.

I love this goal but I'm willing to relax it a bit in the case of plugins. I do think it's worth every function in the core src having a docstring, no matter how "self-explanatory" the code may be.

A when macro implies side-effects,

I'm actually surprised to see this and had either missed or forgotten this distinction between when and a one-legged if. I will say I strongly prefer when where possible. In light of this new information though, if you must use one-legged if I would omit the explicit nil/false branch or (even better) restructure the code to not depend on the return value of the if perhaps. I think I'm just biased against one-legged ifs. :)

The main issue with the PR is that it modifies the post class instead of extending it.

I happen to agree with this point. Doubling the size of the built-in slots on the post class to accommodate an optional plugin is something I'm not comfortable with. That being said, we do need a real mechanism for plugins that require arbitrary data to be kept with content objects.
Perhaps we should have all documents have a "extra-args" slot that contains any initargs which go unused? That sounds tricky but I bet if I dug into my copy of Keene it would be doable without too much nastiness. I'm open to suggestions on this point.

This code is the essence of what I have in mind to allow the user to extend the document type
I still have to add the extended headers processing. Will do that tomorrow hopefully. We could provide a generic function {read,parse}-content with a different implementation for each document type which would allow maximum flexibility but I think it would be overkill and tedious for the user doing the extension. Using @kenanb's idea and hiding it behind an :additional-headers keyword argument in register-content-class would probably be the better idea.

Perhaps we should have all documents have a "extra-args" slot that contains any initargs which go unused? That sounds tricky but I bet if I dug into my copy of Keene it would be doable without too much nastiness. I'm open to suggestions on this point.

Voila! I created a complete content extension system in PR https://github.com/kingcons/coleslaw/pull/96 and revised metadata plugin as an example to that. I also revised post content type to fit in the new system. The system is fully backwards compatible with the past user content. And I must say I am liking it. I hope you like it too. @kingcons @PuercoPop

I forgot to answer the following:

My question: Should this supersede/replace the existing twitter-summary-cards plugin or should they coexist? I assume this is a complete superset of the functionality, is that right?

This plugin subsumes the functionality of the twitter-summary-card plugin. Maybe we could add a warning pointing to the metadata plugin when loading the twitter-summary plugin.


Crash report from console

Description
[21:07:26 INFO]: [LuckPerms] Loading configuration...
[21:07:27 INFO]: [LuckPerms] Loading storage provider... [H2]
[21:07:27 WARN]: [LuckPerms] [DB Upgrade] Found an old (v1) H2 database file. LuckPerms will now attempt to upgrade it to v2 (this is a one time operation).
[21:07:27 INFO]: [LuckPerms] [DB Upgrade] Stage 1: Exporting the old database to an intermediary file...
[21:07:27 INFO]: [LuckPerms] [DB Upgrade] Stage 2: Importing the intermediary file into the new database...
[21:07:27 WARN]: [LuckPerms] Something went wrong whilst upgrading the LuckPerms database. Please report this on GitHub.
org.h2.jdbc.JdbcSQLSyntaxErrorException: Sequence "SYSTEM_SEQUENCE_31A0FE7F_1347_4E6F_8AA7_EC1E88FA018E" already exists; SQL statement:
CREATE SEQUENCE "PUBLIC"."SYSTEM_SEQUENCE_31A0FE7F_1347_4E6F_8AA7_EC1E88FA018E" START WITH 398 BELONGS_TO_TABLE [90035-214]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:632) ~[?:?]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:477) ~[?:?]
at org.h2.message.DbException.get(DbException.java:223) ~[?:?]
at org.h2.message.DbException.get(DbException.java:199) ~[?:?]
at org.h2.command.ddl.CreateSequence.update(CreateSequence.java:53) ~[?:?]
at org.h2.command.ddl.SchemaOwnerCommand.update(SchemaOwnerCommand.java:33) ~[?:?]
at org.h2.command.CommandContainer.update(CommandContainer.java:169) ~[?:?]
at org.h2.command.Command.executeUpdate(Command.java:252) ~[?:?]
at org.h2.command.dml.RunScriptCommand.execute(RunScriptCommand.java:108) ~[?:?]
at org.h2.command.dml.RunScriptCommand.update(RunScriptCommand.java:70) ~[?:?]
at org.h2.command.CommandContainer.update(CommandContainer.java:169) ~[?:?]
at org.h2.command.Command.executeUpdate(Command.java:252) ~[?:?]
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:252) ~[?:?]
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:223) ~[?:?]
at me.lucko.luckperms.common.storage.implementation.sql.connection.file.H2ConnectionFactory$MigrateH2ToVersion2.run(H2ConnectionFactory.java:144) ~[?:?]
at me.lucko.luckperms.common.storage.implementation.sql.connection.file.H2ConnectionFactory.init(H2ConnectionFactory.java:68) ~[?:?]
at me.lucko.luckperms.common.storage.implementation.sql.SqlStorage.init(SqlStorage.java:162) ~[?:?]
at me.lucko.luckperms.common.storage.Storage.init(Storage.java:114) ~[?:?]
at me.lucko.luckperms.common.storage.StorageFactory.getInstance(StorageFactory.java:87) ~[?:?]
at me.lucko.luckperms.common.plugin.AbstractLuckPermsPlugin.enable(AbstractLuckPermsPlugin.java:201) ~[?:?]
at me.lucko.luckperms.bukkit.LPBukkitBootstrap.onEnable(LPBukkitBootstrap.java:175) ~[?:?]
at me.lucko.luckperms.bukkit.loader.BukkitLoaderPlugin.onEnable(BukkitLoaderPlugin.java:50) ~[LuckPerms-Bukkit-5.4.120.jar:?]
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:287) ~[paper-api-1.20.4-R0.1-SNAPSHOT.jar:?]
at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:188) ~[paper-1.20.4.jar:git-Paper-451]
at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:104) ~[paper-1.20.4.jar:git-Paper-451]
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:507) ~[paper-api-1.20.4-R0.1-SNAPSHOT.jar:?]
at org.bukkit.craftbukkit.v1_20_R3.CraftServer.enablePlugin(CraftServer.java:639) ~[paper-1.20.4.jar:git-Paper-451]
at org.bukkit.craftbukkit.v1_20_R3.CraftServer.enablePlugins(CraftServer.java:550) ~[paper-1.20.4.jar:git-Paper-451]
at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:275) ~[paper-1.20.4.jar:git-Paper-451]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1131) ~[paper-1.20.4.jar:git-Paper-451]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:319) ~[paper-1.20.4.jar:git-Paper-451]
at java.lang.Thread.run(Thread.java:840) ~[?:?]
[21:07:28 INFO]: [LuckPerms] Loading internal permission managers...
[21:07:28 INFO]: [LuckPerms] Performing initial data load...
[21:07:28 INFO]: [LuckPerms] Successfully enabled. (took 3317ms)
Reproduction Steps
I sent everything above and now LuckPerms must help me fix the plagins fault. If it is on me, tell me how to fix that.
Expected Behaviour
I sent everything above and now LuckPerms must help me fix the plagins fault. If it is on me, tell me how to fix that.
Server Details
paper-1.20.4-45.jar
LuckPerms Version
5.4.102
Logs and Configs
No response
Extra Details
No response

Quoting Luck on #3676, the suggested course of action here is to:

Roll back to the last installed version of LuckPerms that worked, and do a /lp export.
Stop the server.
Delete (create a backup / move it somewhere else) the old database file.
Start the server and run /lp import.

Quoting Luck on #3676, the suggested course of action here is to:

Roll back to the last installed version of LuckPerms that worked, and do a /lp export.
Stop the server.
Delete (create a backup / move it somewhere else) the old database file.
Start the server and run /lp import.

it doesnt work


Cannot read property 'syntaxProfiles' of null

[Error - 1:32:12 PM] Request textDocument/completion failed.
  Message: Request textDocument/completion failed with message: Cannot read property 'syntaxProfiles' of null
  Code: -32603

This doesn't seem to be resolved
Every time I enter a word, this exception will be thrown

https://user-images.githubusercontent.com/9758711/126886964-da9dc8fc-7d7f-4bc5-8658-aa5962b96909.mov


global option

I do not know double _notd could not be ...

Umm I'm not sure about this. We can just have a global for the dl instead of doing it for each handle. I'll revisit this later and send a review or a PR with the suggestions! I agree about using globals but we can simplify the code

@MatejMagat305 created this PR using yours as base https://github.com/vlang/vsl/pull/139


feat(dep-check): add 'metro-babel' capability

Description
Adds to the profiles the capability for the metro-react-native-babel-preset under the name "metro-babel".
This is one of the few "core" capabilities that I could see missing still ;)
Test plan
N/A

Dependencies are potentially misaligned – run yarn rnx-dep-check locally for more details

https://github.com/microsoft/rnx-kit/blob/a2de7dffb14137e9cae1af0c98defb024c4ec20b/package.json#L46
https://github.com/microsoft/rnx-kit/blob/a2de7dffb14137e9cae1af0c98defb024c4ec20b/packages/babel-preset-metro-react-native/package.json#L27

You can ignore this. I'll take care of it.

Dependencies are potentially misaligned – run yarn rnx-dep-check locally for more details

https://github.com/microsoft/rnx-kit/blob/467ba52e61230f1d25d645efbb7f12bdc0e05d07/package.json#L43-L49
https://github.com/microsoft/rnx-kit/blob/467ba52e61230f1d25d645efbb7f12bdc0e05d07/packages/metro-resolver-symlinks/package.json#L30
https://github.com/microsoft/rnx-kit/blob/467ba52e61230f1d25d645efbb7f12bdc0e05d07/packages/metro-serializer-esbuild/package.json#L36
https://github.com/microsoft/rnx-kit/blob/467ba52e61230f1d25d645efbb7f12bdc0e05d07/packages/metro-serializer/package.json#L31
https://github.com/microsoft/rnx-kit/blob/467ba52e61230f1d25d645efbb7f12bdc0e05d07/packages/metro-service/package.json#L47-L52

These should go away once we move to react-native 0.66. Which should happen any time soon now…