make -C docker release_build FAILED, REGRESSION??

Today,  I got the following error on various environment, My own PC, Azure VM and company server.
When I ran "make -C docker release_build" follow instruction in
https://github.com/NVIDIA/TensorRT-LLM/blob/release/0.5.0/docs/source/installation.md
It used to work for me but not work today.
Repro steps are
apt-get update && apt-get -y install git git-lfs
git clone https://github.com/NVIDIA/TensorRT-LLM.git
cd TensorRT-LLM
git submodule update --init --recursive
git lfs install
git lfs pull
make -C docker release_build
#0 43.10       /usr/local/mpi/bin/mpicc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 -Wl,-Bsymbolic-functions -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.10/src/MPI.o -Lbuild/temp.linux-x86_64-3.10 -ldl -o build/lib.linux-x86_64-3.10/mpi4py/MPI.cpython-310-x86_64-linux-gnu.so
#0 43.10       writing build/lib.linux-x86_64-3.10/mpi4py/mpi.cfg
#0 43.10       Traceback (most recent call last):
#0 43.10         File "/usr/local/lib/python3.10/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
#0 43.10           main()
#0 43.10         File "/usr/local/lib/python3.10/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
#0 43.10           json_out['return_val'] = hook(**hook_input['kwargs'])
#0 43.10         File "/usr/local/lib/python3.10/dist-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
#0 43.10           return _build_backend().build_wheel(wheel_directory, config_settings,
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 404, in build_wheel
#0 43.10           return self._build_with_temp_dir(
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 389, in _build_with_temp_dir
#0 43.10           self.run_setup()
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 311, in run_setup
#0 43.10           exec(code, locals())
#0 43.10         File "", line 644, in
#0 43.10         File "", line 641, in main
#0 43.10         File "", line 492, in run_setup
#0 43.10         File "/tmp/pip-install-8050735a/mpi4py_6482ffe4a2ee4078aa02472ce31c8a15/conf/mpidistutils.py", line 541, in setup
#0 43.10           return fcn_setup(**attrs)
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/init.py", line 103, in setup
#0 43.10           return distutils.core.setup(**attrs)
#0 43.10         File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
#0 43.10           dist.run_commands()
#0 43.10         File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
#0 43.10           self.run_command(cmd)
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/dist.py", line 963, in run_command
#0 43.10           super().run_command(command)
#0 43.10         File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command
#0 43.10           cmd_obj.run()
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/wheel/bdist_wheel.py", line 371, in run
#0 43.10           install = self.reinitialize_command("install", reinit_subcommands=True)
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/init.py", line 216, in reinitialize_command
#0 43.10           cmd = _Command.reinitialize_command(self, command, reinit_subcommands)
#0 43.10         File "/usr/lib/python3.10/distutils/cmd.py", line 305, in reinitialize_command
#0 43.10           return self.distribution.reinitialize_command(command,
#0 43.10         File "/usr/lib/python3.10/distutils/dist.py", line 938, in reinitialize_command
#0 43.10           command = self.get_command_obj(command_name)
#0 43.10         File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
#0 43.10           cmd_obj = self.command_obj[command] = klass(self)
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/init.py", line 174, in init
#0 43.10           super().init(dist)
#0 43.10         File "/usr/lib/python3.10/distutils/cmd.py", line 62, in init
#0 43.10           self.initialize_options()
#0 43.10         File "/tmp/pip-build-env-_y1p3opv/overlay/local/lib/python3.10/dist-packages/setuptools/command/install.py", line 50, in initialize_options
#0 43.10           orig.install.initialize_options(self)
#0 43.10         File "/usr/lib/python3.10/_distutils_system_mod.py", line 33, in initialize_options
#0 43.10           super().initialize_options()
#0 43.10       TypeError: super(type, obj): obj must be an instance or subtype of type
#0 43.10       [end of output]
#0 43.10
#0 43.10   note: This error originates from a subprocess, and is likely not a problem with pip.
#0 43.10   ERROR: Failed building wheel for mpi4py
#0 43.10 Failed to build mpi4py
#0 43.10 ERROR: Could not build wheels for mpi4py, which is required to install pyproject.toml-based projects

Same issue, anyone find a solution?

I got the same error.

same issue, any solution?

we're working on it.

Please refer to https://github.com/mpi4py/mpi4py/pull/431 and patching the code, then pip install from the patched code. Thanks! @josephwnv @Chevolier @defuyun @xinji1
If you have a better solution, please tell us. And will synchronize the fix to main branch on this Friday.

@Shixiaowei02 ran pip with your branch and it seems to be working. thanks!

Please refer to mpi4py/mpi4py#431 and patch the code, then pip install from it. Thanks! @josephwnv @Chevolier @defuyun @xinji1
If you have a better solution, please tell us. And will synchronize the fix to main branch on this Friday.
thanks, this works for me
change docker/common/install_base.sh

#pip install mpi4py
pip install git+https://github.com/Shixiaowei02/mpi4py.git@fix-setuptools-version

Thanks. I'm closing that issue. Feel free to reopen if needed.


Customer headers (with tests)

Had to put the test in it's own file called "header-test."  I will create an issue describing behavior I noticed.

It seems like this block of code is repeated multiple times
if (options && options.reqOptions) {
	reqOptions = options.reqOptions;
	delete options.reqOptions;
}

Should it be moved to a function, maybe in the helpers file?


Accept videos in postcards

Even though the schema allows videos in .medias, a new .videoMedia field was added which we are not currently requesting. So the postcard data we get back does not include videos, so they are not saved.

jhansche/pybirdbuddy#6 adds the videoMedia field to be returned alongside medias, so an automation can be used to download the video files, if one is present. However, I don't know if that is enough to make the collect_postcard service save the video file along with other sighting media.
That change was released in v0.0.11, so if anyone is able to test with their own postcards and report back if video media are now saved into collections, that would be helpful to know. If not, I'll have to wait until I get my next visitor with a video.
I will leave this open until that can be confirmed, because this issue is specifically about saving the video into the BB collections.

Updated in my HA and will wait for a bird to check the new event data, thanks

Finally got a bird today. I can see that we receive the videoMedia field, but it doesn't have the video to collections. It could be used to download the video in the automation though.
I'll disable my auto collection and wait for the next visitor to see if I can debug the app and see what it does. It might just be a separate call to save the mediaId directly.

Got a bird today, I can confirm it is in the event now
videoMedia:
          id: xxx
          createdAt: '2023-02-06T14:36:30.347Z'
          thumbnailUrl: >-
            https://media.app-api-graphql.app-api.prod.aws.mybirdbuddy.com/media/feeder/xxx/media/xxx/THUMBNAIL.jpg?Expires=xxx
          contentUrl: >-
            https://media.app-api-graphql.app-api.prod.aws.mybirdbuddy.com/media/feeder/xxx/media/xxx/CONTENT.mp4?Expires=xxx
          __typename: MediaVideo

This is what I wanted, thanks :)

@jhansche what does the event look like if you get a bird without video, do you have an example by chance?

The same as it always was before - you'll just get the .medias field, either without .videoMedia or videoMedia might be null. You'll want to check that .videoMedia is present before trying to use the contentUrl.
I've paused my collect automation, so that I can research more how the app handles the video, to see how they save the video to the BB collection.

Yeah, I am looking on how to do that in HA :)

Figured out how to save the video from the postcard into BB collections. There's also a new videoMediaId field in sightingReportPostcardFinishInput. So that's an easy fix.

Was this added to HA so that we can grab the video URL? I see entity_picture but not video.

No this does not get exposed as an entity like the recent visitor image does.
To get the video URL you will need to handle the new postcard event and extract the URL from the object as described above (videoMedia.contentUrl).
Or you can wait until after the postcard is collected, and then you will find it in the HA media browser.


Fail to build GUI with breaking changes of Asv.Mavlink 3.10.2

If get the asv.mavlink updated from 3.10.0 to the latest 3.10.2, the build fails.
Asv.Drones.Gui\Services\Mavlink\MavlinkDevicesService.cs
CS1503	Argument 3: cannot convert from 'Asv.Mavlink.RfsaClientDeviceConfig' to 'Asv.Mavlink.RsgaClientDeviceConfig'

where
Asv.Drones.Gui\Services\Mavlink\MavlinkDevicesService.cs

fails Asv.Drones.Gui\Services\Mavlink\MavlinkDevicesService.cs 3.10.2

works Asv.Drones.Gui\Services\Mavlink\MavlinkDevicesService.cs 3.10.0

Hello!
That is indeed the case. Current develop and main branches should use mavlink v3.10.0. Do you need something specific from the new mavlink version that is not supported in 3.10.0?
Best regards,
Aleksandr.

I don't think so, it's rather for purity's sake arvthe moment. The inconsistrncy in the code is obvious and the fix seems easy. 11:00, 2 августа 2024 г., Aleksandr @.***>:
Hello!
That is indeed the case. Current develop and main branches should use mavlink v3.10.0. Do you need something specific from the new mavlink version that is not supported in 3.10.0?
Best regards,
Aleksandr.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
-- Отправлено из мобильного приложения Яндекс Почты

Develop branch has been updated and now supports Asv.Mavlink v3.10.2.
Best regards,
Aleksandr


Updating Mastodon logo

Updating Mastodon logo to reflect the 2022 brand update.
Optimized the shapes & added the new gradient
Closes #693

Much obliged!


add deprecation warning for share module

Please Check :-

https://github.com/facebook/react-native/issues/23313
https://github.com/react-native-community/react-native-simple-share

Summary
As a part of lean core , I have stripped out the share module in react-native to react-native-simple-share. So I have added a deprecation warning in Share module in this repo.
Changelog

Deprecating share  module

added a console.warn statement indicating that the module is deprecated

Test Plan
Only code change is console.warn(DEPRECATION_WARNING);, it will show a warning :

Warning: Share package is deprecated in favour of the lean core (https://github.com/facebook/react-native/issues/23313). Use https://github.com/react-native-community/react-native-simple-share for the exact same feature set or use https://github.com/react-native-community/react-native-share which has a rich feature set

Thanks for your help. I think tis is not quite ready yet and we probably won't remove the share module for quite a while so I'm going to close this PR for now.


Regarding Sparsity of LoRA fine-tuned model.

Hello @pprp,
The lora fine-tuned models cannot be merged as the lora branch is dense. This makes the LoRA fine-tuning not very useful to regain performance lost during pruning. Please let me know if there is any sparse lora fine-tuning that you are employing.

hi, sorry for the late reply.
For lora fine-tuning, we just employ the same method as Wanda, which is not taking the sparsity into consideration.
For sparse lora-finetuning, you can refer to :

LoRAPrune: Structured Pruning Meets Low-Rank Parameter-Efficient Fine-Tuning
Sparse Fine-tuning for Inference Acceleration of Large Language Models
APT: Adaptive Pruning and Tuning Pretrained Language Models for Efficient Training and Inference (ICML24 Oral)


Facebook bots?

Is there any way to make bots ruin trough my facebook acc ?

Hii, I too am experiencing the same problem and hope someone will help me. When I use access token as auth. I still get the warning for all the three cookies (developer says they get overwritten, but they dont) and login doesnt work. When I use the cookie method there is no warning and all my ips connect to the server but none of the bots spawn (gives me an error), keeps on connecting and disconnecting, please please resolve my problem that will be very nice.

1 FB Account = 1 Bot
2 FB Account = 2 Bot
...

wjkh i am getting neither of the fb as well as non fb bots

@pantshobhit I haven't tested it recently because I could connect one bot (I have one FB account). Anyway in the past it wasn't working properly (I was doing the auth step manually) and maybe @davidmann4 could check it and confirm if it's working or not.

ogar does not uses fb bots


Edit assessment to data

Allows the modify_test_view page to pull from data
Allows the view_test_view page to pull from data
Allows the modify_test_view page to save to data
removed several unneeded buttons on modify_test_view and edit_test_view pages

I'm having some trouble fixing the failed test. Have you had the chance to look at this? @hellohouseplant @J-Gilberg

fixed the analyze. Still not sure how to fix the test. I'll keep looking for now.


Ledvance WiFi Smartplug with energy metering

Hi all,
Ive got the smart plug from the Tonic and added it with this ID j0zozzoarutv0nu1 to fhempy.
A test with TinyTuya reveals, that this smart plug doesn't return the "46" Value as we can see in this sample:
set_status() result {'dps': {'1': False, '9': 0, '17': 16, '18': 0, '19': 0, '20': 2269, '21': 1, '22': 1578, '23': 39846, '24': 108000, '25': 380, '26': 0, '38': 'on', '41': '', '42': ''}}
The ID "j0zozzoarutv0nu1" seems the nearest match for this plug and all values other values seems fine.
Is it possible to  add this plug in the mappings.py file as a new "knownSchemas"?
Michael

Hi,
adding the productid to the mappings.py file wouldn't change the behavior. What do you expect to get from DP 46?

Hi Dominic,
no, the Ledvance does not have the DP46 as you can see in the result. For this Ledvance Wifi Plug it should be removed. The j0zozzoarutv0nu1 was the nearest match I’ve found.
So a new product ID is only for other users which don’t know which is they should use for this plug.

Ok, got it. If you provide me the productid of your smart plug, I can add it as a separate schema to mappings.py.

:-) do you have a hint where I can find this ID? I‘ve searched everything, but haven’t found this ID. Is there a command that I can use with tinytuya to help xtract the ID? The „virtual ID“ is the only I’d the Ledvanceapp is showing but that one.
If it helps, this is the define in fhem:
defmod plug_LedvanceMeter1 fhempy tuya 0fHWRe8ULjtmnBNd bffc34ecf456326979mzl0 maskedDeviceIP af4e23037768a2c0

Just set up tuya_cloud as mentioned in the readme. If you provide API_KEY/SECRET the productid is automatically retrieved from the tuya iot cloud.

But I don’t have this Api_Key and secret. Ledvance seems doing it‘s own (hidden) thing and I’ve found no way to use the tuya iot cloud/ App. I can use only the Ledvance App or tinyTuya. Ledvance uses it‘s own cloud :-(

Oh, I didn't know that. How did you retrieve the local key for that device?
I can create a "ledvance_smartplug_with_energy" productid in that case.

The local key was simple. TinyTuya will show it when it scans for devices. I don’t know any way to retrieve the product ID. Perhaps someone with more knowledge can examine the Ledvance app. If tinyTuya can extrakt the ID than I will try it. Otherwise you have to create a new ID yourself if that’s possible.

Ok, I'm going to add a product id ledvance_smartplug_energy, that's the easiest solution.

Thanks a lot. This makes life easier for others if they add this plug or Fhem.

Hopefully final update how to extract ProductKey and localKey for the "Ledvance WiFi smartplug with smart metering"
So, after a lookup at my notes here is the the Way how to Retriever the localkey and the productID from Ledvance:
The script from link https://github.com/FlagX/ha-ledvance-tuya-resync-localkey will extract the devicename, device ID and local key from the Ledvance Cloud. Keep in mind, that your device hold be visible in the LedvanceApp.
Now installiert TinyTuya from here https://pypi.org/project/tinytuya/ and with this command from the Terminal (python -m tinytuya scan) you get a device List. If the Output contains "Found x device(es)" and "Saving device snapshot data to snapshot.json" you can find the proper productkey with cat snapshot.json from the Terminal.
The produktKey for Ledvance WiFi smartplug is "keym9qkuywghyrvs". This shoud be added to the file mappings.py.
Getting the Status of the device with tinyTuya reveals this usedDS (could't be, that there are some more for Countdowns (DPs 9 to 15) but this is unproofed by me.
This is the Status from my device:
Device status: {'dps': {'1': True, '9': 0, '17': 13, '18': 34, '19': 31, '20': 2291, '21': 1, '22': 1578, '23': 39846, '24': 108000, '25': 380, '26': 0, '38': 'memory', '41': '', '42': ''}}
the meaning of all DPs are described here https://github.com/jasonacox/tinytuya#version-33---plug-switch-power-strip-type.
Hopefully someone can check this.

Productid keym9qkuywghyrvs added to mappings.py.
Please check if it works. Thx!

Seems working until now :-)
Thank you very much


Fix selection state not preserved between launches

Fixes #132
I just added the default value nil to both UserDefaults. It compiles successfully with Xcode 13.4.1 and 14b5.

I don't know why this suddenly works, but it does! Thank you very much. Can you please add the following comment above the two lines so that SwiftLint won't complain:
// swiftLint:disable redundant_optional_initialization

I have added the disable and enable line for SwiftLint. I'm not quite sure why a default value is necessary either, since the developer documentation states "Defaults to nil if there is no restored value.".

I'm confused by this as well, especially since this whole thing just worked for literally years. Anyway, thank you very much for finding out and this PR! <3


[New game]: color catcher

🎮 Game Request
The player controls a basket that can move left and right at the bottom of the screen.
Colored balls fall from the top of the screen at random positions and speeds.
The player must catch balls of a specific color while avoiding balls of other colors.
The game increases in difficulty as the player progresses, with more balls falling faster.

Score tracking based on the number of correct color balls caught.
Lives system: the player loses a life for catching the wrong color.
Increasing difficulty as the game progresses.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @aadyagupta44 , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#4508

Hey @aadyagupta44 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @aadyagupta44 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹


[Cosmos] Automatic failover and retry of requests is not working

Package Name: @azure/cosmos
Package Version: 3.11.3, 3.10.6, 3.9.5, 3.8.0
Operating system:
[X] nodejs

version: 12.x.x

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
When I have a multi region cosmos account automatic failover of a read request does not work.
To Reproduce
Steps to reproduce the behavior:

Start a CosmosClient instance connected to an account with multiple regions (single write - multi read).
Do a read request. The request goes to the westeurope fqdn.
Delete the westeurope read region the CosmosClient instance is using as a read endpoint. DO NOT stop the node process that contains the CosmosClient instance.
Do a second read request without recreating the CosmosClient.
The request fails with the following error:

RestError: getaddrinfo ENOTFOUND my-cosmos-account-name-westeurope.documents.azure.com
    at ClientRequest.<anonymous> (*\node_modules\@azure\core-rest-pipeline\dist\index.js:1445:32)
    at ClientRequest.emit (events.js:311:20)
    at TLSSocket.socketErrorListener (_http_client.js:426:9)
    at TLSSocket.emit (events.js:311:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

Expected behavior
The sdk should have caught the error and retried the request against the next prefered location.
Screenshots
none
Additional context
The cosmos account has a private endpoint.
The preferred locations for the CosmosClient instance are: westeurope, centralus, eastus2, eastasia, southeastasia, northeurope
I have opened a support issue about this too. The number is<PHONE_NUMBER>001920 you should be able to find log entries and pictures there.

Hey @gkaniouris, we had a regression in version 3.11.x and above in a subdependency, which was hotfixed. I was using your script to reproduce, let me try again with the new version to see what's going on.

When I downgraded to 3.10.6 last week, the failover was successfully working, but I see you've listed 3.10.6 as a version.

After removing package-lock.json and node_modules and running npm i, I am now correctly failing over once again on v3.11.3

Ok so the problem is most likely a transient dependency that is common across versions. It was locked in and did not change even when I change the cosmos library version.
Below are the dependencies for each version from the commit history:

3.8.0
3.9.5
3.10.6
3.11.3

@azure/core-auth

^1.3.0
^1.3.0

@azure/core-rest-pipeline

^1.0.0

@types/debug
^4.1.4
^4.1.4

debug
^4.1.1
^4.1.1
^4.1.1
^4.1.1

fast-json-stable-stringify
^2.0.0
^2.0.0
^2.0.0
^2.0.0

jsbi
^3.1.3
^3.1.3
^3.1.3
^3.1.3

node-abort-controller
^1.0.4
^1.0.4
^1.2.0
^1.2.0

node-fetch
^2.6.0
^2.6.0
^2.6.0

os-name
^3.1.0

priorityqueuejs
^1.0.0
^1.0.0
^1.0.0
^1.0.0

semaphore
^1.0.5
^1.0.5
^1.0.5
^1.0.5

tslib
^2.0.0
^2.0.0
^2.0.0
^2.0.0

universal-user-agent

^6.0.0
^6.0.0
^6.0.0

uuid
^8.1.0
^8.3.0
^8.3.0
^8.3.0

The commits I pulled that from are: https://github.com/Azure/azure-sdk-for-js/commit/6784b39a2481fe9f45c4320590f217d3252bbd99, https://github.com/Azure/azure-sdk-for-js/commit/70207dc022410506ae8d1209eb9484aceb605c3b, https://github.com/Azure/azure-sdk-for-js/commit/cf85b3e7846376ff41fedb0435546a13d376d71e, https://github.com/Azure/azure-sdk-for-js/commit/638b5fa2a24f389f0f8cb09359d3fba9e648f342
I will have a look at my package-lock and node_modules tomorrow and let you know the specific versions that have locked in.

@zfoster I tested 3.11.3 again and failover did not work. Specifically I completely removed @azure/cosmos from my dependencies and then reinstalled it:
npm remove @azure/cosmos
npm prune
npm install @azure/cosmos

After prune I also committed the changes to package-lock.json so that I can compare them with the after install state.
The following dependencies are added to package-lock.json:

dependency
version

@azure/abort-controller
1.0.4

@azure/core-auth
1.3.0

@azure/core-rest-pipeline
1.0.4

@azure/core-tracing
1.0.0-preview.11

@azure/cosmos
3.11.3

@azure/logger
1.0.2

@opencensus/web-types
0.0.7

@opentelemetry/api
1.0.0-rc.0

@tootallnate/once
1.1.2

agent-base
6.0.2

asynckit
0.4.0

combined-stream
1.0.8

debug
4.3.1

delayed-stream
1.0.0

fast-json-stable-stringify
2.1.0

form-data
3.0.1

http-proxy-agent
4.0.1

https-proxy-agent
5.0.0

jsbi
3.1.4

mime-db
1.48.0

mime-types
2.1.31

ms
2.1.2

node-abort-controller
1.2.1

priorityqueuejs
1.0.0

semaphore
1.1.0

tslib
2.2.0

universal-user-agent
6.0.0

uuid
8.3.2

I also tested it the same way you did (delete package-lock.json and node_modules and do install) but again failover fails.
I have uploaded to the support ticket the two diffs for package-lock.json to check too if you want too.

@azure/core-rest-pipeline was hotfixed in version 1.0.4 which should now show up in your dependency graph when using npm install since we depend on ^1.0.0. When I debugged the issue, this is what I found was causing the addr not found error. I think if you have core-rest-pipeline 1.0.4 in your dep graph you'll no longer receive an error. https://github.com/Azure/azure-sdk-for-js/pull/15426

moving to ICM

This has been resolved in version 3.11.5.
@zfoster thank you very much for your help

thanks for the reproducible scripts @gkaniouris!


Passing Immutable data to rows

Hello,
I have an issue with last version (0.1.0). In our app we are passing down immutable data to our (Sortable)ListView but with last version I got an error on this line:
One of the sources for assign has an enumerable key on the prototype chain.
This is an edge case that we do not support.
This error is a performance optimization and not spec compliant.

Object.assign
polyfills.js:56
Constructor.componentDidUpdate
index.js:35

I assume it's because Immutable uses complex data structures, which have a reference on prototype which is not handled by Object.assign React Native's polyfill (source).

Hi @Bhullnatik,
Ok, the Object.assign is only being used to take a shallow copy of row data for future comparison, which isn't be necessary at all if you are using immutable data. I've pushed a change that will only use this Object.assign if the rowHasChanged prop is defined. I've updated the documentation to reflect this.
I've just released 0.1.1 to npm, and . Let me know how it goes.


wg_engine: separate pipelines ans bind group layouts (refactoring)

The main reason of refactoring is to separate bind group sets and pipelines, and change owning of pipelines to compositor
It will be helpfull for resizing (intermidiate changes)
Should not impact to performance and web player
see: Svg example

@tinyjin this is just a refactoring. any regressions (performance & functionality) by this?


New Dataverse experience breaks all labs in modules 2 and 3

The labs for module 2 and module 3 of PL-200 are significantly broken since the changes released on June 6 as mentioned here https://powerapps.microsoft.com/en-us/blog/announcing-general-availability-of-our-new-dataverse-experiences-on-power-apps/
Many steps are now incorrect as the whole user interface has changed and options renamed
Labs are now taking 3 x longer than they should do because of all the problems learners now face being unable to follow the instructions and getting lost
I expect other later labs are affected as well
Lab 2.1: Create an app
Lab 2.2: Create tables and columns
Lab 2.3: Create relationships
Lab 2.4: Additional table settings
Lab 3.1: Use app designer
Lab 3.2: Modify forms
Lab 3.3: Modify views

Later labs where columns are added to tables are also affected
The biggest problems are around Choice fields, Date/Time fields, and Calculated/Rollup fields plus the App Designer now that it is out of preview and is the default tool for app components and sitemap.


document s&co data package folder better (formatting, install reqs)

Look at it for 30 min and tidy.

improved documentation added in #840


Slug widget: Fix broken slug editor

Fixes:

Wrong method names
Race conditions due to api not being loaded before the widget entry point was called

This commit also includes a rewrite using es2015 to keep it consistent with other widgets.

Would be nice to have a quick summary in the commit msg what's been broken.

@danweDE added the changes in the PR description. Will that suffice?

@zeusdeux Very nice elaborate summary but the best place for it would be the commit message so it's visible when browsing the git log.

@DanweDE done!

Rewrite using ES2015 to keep it consistent with other widgets

nice, but keep in mind that we chose to implement all widgets a little differently to show diverse ways of doing things. So consistency was never a requirement here.

@DanweDE I was talking about this with @floelhoeffel and he suggested that we show one solid way of doing stuff rather than many different approaches so that people can get up and running quicker.
That is also the reason why I am moving our builds to browserify + babelify in most places. Converging it all into an approach that people can follow out of the box.


Fix #704; better open paren whitespace handling in type declarations

The __ is checked in the alternate choice here: https://github.com/DanielXMoore/Civet/pull/796/files#diff-b95b0a26fe57cfe39663405477d1c9cbe418e6ffb2a45b5cdfe47f24d3c68d62L6033


Travis XCode build gives many warnings about missing override and fails

Travis XCode build gives many warnings about missing override and fails.
In file included from /Users/travis/build/SuperElastix/SuperElastix/Modules/Filter/src/selxSuperElastixFilter.cxx:21:
In file included from /Users/travis/build/SuperElastix/SuperElastix/Modules/Core/include/selxNetworkBuilder.h:126:
In file included from /Users/travis/build/SuperElastix/SuperElastix/Modules/Core/include/selxNetworkBuilder.hxx:22:
/Users/travis/build/SuperElastix/SuperElastix/Modules/Core/include/selxSuperElastixComponent.h:56:38: warning: 'GetComponentName' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
virtual const typename std::string GetComponentName();
etc
etc

solved by pull request #263


Cluster Mode Hazelcast Exception No connection found to cluster

Search before asking

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

What happened
In cluster mode, there are three machines that can access port 5801, but sometimes exceptions may occur and one of them cannot be heard.
SeaTunnel Version
seatunnel-2.3.3
SeaTunnel Config
1、hazelcast-client.yaml

hazelcast-client:
  cluster-name: seatunnel
  properties:
    hazelcast.logging.type: log4j2
  network:
    cluster-members:
      - <IP_ADDRESS>:5801
      - <IP_ADDRESS>:5801
      - <IP_ADDRESS>:5801

2、hazelcast.yaml

hazelcast:
  cluster-name: seatunnel
  network:
    rest-api:
      enabled: true
      endpoint-groups:
        CLUSTER_WRITE:
          enabled: true
        DATA:
          enabled: true
    join:
      tcp-ip:
        enabled: true
        member-list:
          - <IP_ADDRESS>
          - <IP_ADDRESS>
          - <IP_ADDRESS>
    port:
      auto-increment: false
      port: 5801
  properties:
    hazelcast.invocation.max.retry.count: 20
    hazelcast.tcp.join.port.try.count: 30
    hazelcast.logging.type: log4j2
    hazelcast.operation.generic.thread.count: 50

3、seatunnel.yaml

seatunnel:
  engine:
    history-job-expire-minutes: 1440
    backup-count: 2
    queue-type: blockingqueue
    print-execution-info-interval: 60
    print-job-metrics-info-interval: 60
    slot-service:
      dynamic-slot: true
    checkpoint:
      interval: 10000
      timeout: 60000
      storage:
        type: hdfs
        max-retained: 3
        plugin-config:
          namespace: /tmp/seatunnel/checkpoint_snapshot
          storage.type: hdfs
          fs.defaultFS: file:///tmp/

Running Command
1、Start Cluster Service

sh seatunnel-cluster.sh

2、Perform configuration tasks

${SEATUNNEL_HOME}/bin/seatunnel.sh --config seatunnel_4_15.conf --deploy-mode cluster

Error Exception
[INFO] 2023-10-23 16:38:38.182 +0800 -  -> 2023-10-23 16:38:37,399 INFO  org.apache.seatunnel.engine.client.job.JobMetricsRunner -
	***********************************************
	           Job Progress Information
	***********************************************
	Job Id                    :<PHONE_NUMBER>23390211
	Read Count So Far         :             4802837
	Write Count So Far        :             4801954
	Average Read Count        :              7546/s
	Average Write Count       :              7531/s
	Last Statistic Time       : 2023-10-23 16:37:36
	Current Statistic Time    : 2023-10-23 16:38:37
	***********************************************

[INFO] 2023-10-23 16:39:55.451 +0800 -  -> 2023-10-23 16:39:51,586 WARN  com.hazelcast.client.impl.connection.tcp.HeartbeatManager - hz.client_1 [seatunnel] [5.1] Heartbeat failed over the connection: ClientConnection{alive=true, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=never, connected server version=5.1}
	2023-10-23 16:39:51,588 WARN  com.hazelcast.client.impl.connection.tcp.TcpClientConnection - hz.client_1 [seatunnel] [5.1] ClientConnection{alive=false, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=2023-10-23 16:39:51.587, connected server version=5.1} closed. Reason: Heartbeat timed out
	com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out to connection ClientConnection{alive=true, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=never, connected server version=5.1}
		at com.hazelcast.client.impl.connection.tcp.HeartbeatManager.lambda$start$0(HeartbeatManager.java:59) ~[seatunnel-starter.jar:2.3.3]
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_381]
		at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_381]
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_381]
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_381]
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_381]
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_381]
		at java.lang.Thread.run(Thread.java:750) [?:1.8.0_381]
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76) [seatunnel-starter.jar:2.3.3]
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102) [seatunnel-starter.jar:2.3.3]
	2023-10-23 16:39:52,541 INFO  com.hazelcast.client.impl.spi.ClientClusterService - hz.client_1 [seatunnel] [5.1]

	Members [2] {
		Member [<IP_ADDRESS>]:5801 - 410ba9af-8faa-4d99-a014-cc7b8f507026
		Member [<IP_ADDRESS>]:5801 - f1bdfdd3-1135-45d8-97a2-31a2431ea6b7
	}

[INFO] 2023-10-23 16:40:00.149 +0800 -  -> 2023-10-23 16:39:59,667 INFO  org.apache.seatunnel.engine.client.job.ClientJobProxy - Job<PHONE_NUMBER>23390211) end with unknown state, and throw Exception: java.util.concurrent.ExecutionException: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
		at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.lambda$waitForJobComplete$0(ClientJobProxy.java:101)
		at org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:48)
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:97)
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:184)
		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: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:339)
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.onConnectionClose(ClientInvocationServiceImpl.java:221)
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.onConnectionClose(TcpClientConnectionManager.java:758)
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnection.close(TcpClientConnection.java:191)
		at com.hazelcast.client.impl.connection.tcp.HeartbeatManager.lambda$start$0(HeartbeatManager.java:59)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at java.lang.Thread.run(Thread.java:750)
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
	Caused by: com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.onConnectionClose(ClientInvocationServiceImpl.java:220)
		... 12 more
	Caused by: com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out to connection ClientConnection{alive=true, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=never, connected server version=5.1}
		... 10 more

	2023-10-23 16:39:59,668 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is SHUTTING_DOWN
[INFO] 2023-10-23 16:40:01.467 +0800 -  -> 2023-10-23 16:40:01,339 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel] [5.1] Removed connection to endpoint: [<IP_ADDRESS>]:5801:15e6f0b8-d596-4824-a903-12ce660ca55d, connection: ClientConnection{alive=false, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=2023-10-23 16:39:51.587, connected server version=5.1}
[INFO] 2023-10-23 16:40:21.989 +0800 -  -> 2023-10-23 16:40:21,874 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel] [5.1] Removed connection to endpoint: [<IP_ADDRESS>]:5801:f1bdfdd3-1135-45d8-97a2-31a2431ea6b7, connection: ClientConnection{alive=false, connectionId=3, channel=NioChannel{/<IP_ADDRESS>:47851->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:39:58.637, lastWriteTime=2023-10-23 16:39:59.209, closedTime=2023-10-23 16:40:01.338, connected server version=5.1}
[INFO] 2023-10-23 16:40:23.320 +0800 -  -> 2023-10-23 16:40:22,755 INFO  com.hazelcast.client.impl.connection.ClientConnectionManager - hz.client_1 [seatunnel] [5.1] Removed connection to endpoint: [<IP_ADDRESS>]:5801:410ba9af-8faa-4d99-a014-cc7b8f507026, connection: ClientConnection{alive=false, connectionId=1, channel=NioChannel{/<IP_ADDRESS>:54089->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:40:21.770, lastWriteTime=2023-10-23 16:40:21.869, closedTime=2023-10-23 16:40:21.874, connected server version=5.1}
	2023-10-23 16:40:22,755 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is CLIENT_DISCONNECTED
	2023-10-23 16:40:22,777 INFO  com.hazelcast.core.LifecycleService - hz.client_1 [seatunnel] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is SHUTDOWN
[INFO] 2023-10-23 16:40:28.397 +0800 -  -> 2023-10-23 16:40:28,347 WARN  org.apache.seatunnel.engine.client.job.JobMetricsRunner - Failed to get job metrics summary, it maybe first-run
[INFO] 2023-10-23 16:40:29.699 +0800 -  -> 2023-10-23 16:40:28,733 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed SeaTunnel client......
	2023-10-23 16:40:28,734 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Closed metrics executor service ......
	2023-10-23 16:40:28,734 ERROR org.apache.seatunnel.core.starter.SeaTunnel -

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

	2023-10-23 16:40:28,734 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Fatal Error,

	2023-10-23 16:40:28,734 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Please submit bug report in https://github.com/apache/seatunnel/issues

	2023-10-23 16:40:28,734 ERROR org.apache.seatunnel.core.starter.SeaTunnel - Reason:SeaTunnel job executed failed

	2023-10-23 16:40:28,738 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: java.util.concurrent.ExecutionException: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:117)
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:184)
		... 2 more
	Caused by: java.util.concurrent.ExecutionException: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
		at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.lambda$waitForJobComplete$0(ClientJobProxy.java:101)
		at org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:48)
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:97)
		... 3 more
	Caused by: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:339)
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.onConnectionClose(ClientInvocationServiceImpl.java:221)
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.onConnectionClose(TcpClientConnectionManager.java:758)
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnection.close(TcpClientConnection.java:191)
		at com.hazelcast.client.impl.connection.tcp.HeartbeatManager.lambda$start$0(HeartbeatManager.java:59)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at java.lang.Thread.run(Thread.java:750)
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
	Caused by: com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.onConnectionClose(ClientInvocationServiceImpl.java:220)
		... 12 more
	Caused by: com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out to connection ClientConnection{alive=true, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=never, connected server version=5.1}
		... 10 more

	2023-10-23 16:40:28,738 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: java.util.concurrent.ExecutionException: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:117)
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:184)
		... 2 more
	Caused by: java.util.concurrent.ExecutionException: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
		at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.lambda$waitForJobComplete$0(ClientJobProxy.java:101)
		at org.apache.seatunnel.common.utils.RetryUtils.retryWithException(RetryUtils.java:48)
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.waitForJobComplete(ClientJobProxy.java:97)
		... 3 more
	Caused by: com.hazelcast.core.OperationTimeoutException: ClientInvocation{clientMessage = ClientMessage{connection=null, length=30, operation=SeaTunnel.WaitForJobComplete, isRetryable=true, correlationId=16, messageType=de0300, isEvent=false, isfragmented=false}, objectName = null, target = uuid 15e6f0b8-d596-4824-a903-12ce660ca55d, sentConnection = null} timed out because exception occurred after client invocation timeout 120000 ms. Current time: 2023-10-23 16:39:54.370. Start time: 2023-10-23 16:27:36.878. Total elapsed time: 737492 ms.
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:339)
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.onConnectionClose(ClientInvocationServiceImpl.java:221)
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.onConnectionClose(TcpClientConnectionManager.java:758)
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnection.close(TcpClientConnection.java:191)
		at com.hazelcast.client.impl.connection.tcp.HeartbeatManager.lambda$start$0(HeartbeatManager.java:59)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at java.lang.Thread.run(Thread.java:750)
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
		at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
	Caused by: com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.onConnectionClose(ClientInvocationServiceImpl.java:220)
		... 12 more
	Caused by: com.hazelcast.spi.exception.TargetDisconnectedException: Heartbeat timed out to connection ClientConnection{alive=true, connectionId=2, channel=NioChannel{/<IP_ADDRESS>:44703->/<IP_ADDRESS>:5801}, remoteAddress=[<IP_ADDRESS>]:5801, lastReadTime=2023-10-23 16:38:46.649, lastWriteTime=2023-10-23 16:39:45.832, closedTime=never, connected server version=5.1}
		... 10 more
[INFO] 2023-10-23 16:40:33.523 +0800 -  -> 2023-10-23 16:40:32,678 INFO  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - run shutdown hook because get close signal
	2023-10-23 16:40:32,679 WARN  org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Task will be closed due to client shutdown.
[INFO] 2023-10-23 16:40:35.465 +0800 -  -> 2023-10-23 16:40:33,805 ERROR org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand - Cancel job failed.
	java.util.concurrent.ExecutionException: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
		at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) ~[?:1.8.0_381]
		at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928) ~[?:1.8.0_381]
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.lambda$execute$1(ClientExecuteCommand.java:164) ~[seatunnel-starter.jar:2.3.3]
		at java.lang.Thread.run(Thread.java:750) [?:1.8.0_381]
	Caused by: com.hazelcast.client.HazelcastClientNotActiveException: Client is shutting down
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.notifyExceptionWithOwnedPermission(ClientInvocation.java:316) ~[seatunnel-starter.jar:2.3.3]
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:209) ~[seatunnel-starter.jar:2.3.3]
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.invoke(ClientInvocation.java:156) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.engine.client.SeaTunnelHazelcastClient.requestAndGetCompletableFuture(SeaTunnelHazelcastClient.java:123) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.engine.client.SeaTunnelHazelcastClient.requestOnMasterAndGetCompletableFuture(SeaTunnelHazelcastClient.java:132) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.cancelJob(ClientJobProxy.java:148) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.shutdownHook(ClientExecuteCommand.java:254) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.lambda$null$0(ClientExecuteCommand.java:161) ~[seatunnel-starter.jar:2.3.3]
		at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640) ~[?:1.8.0_381]
		at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1632) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172) ~[?:1.8.0_381]
	Caused by: java.io.IOException: No connection found to cluster.
		at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.checkInvocationAllowed(TcpClientConnectionManager.java:548) ~[seatunnel-starter.jar:2.3.3]
		at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.checkInvocationAllowed(ClientInvocationServiceImpl.java:294) ~[seatunnel-starter.jar:2.3.3]
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:178) ~[seatunnel-starter.jar:2.3.3]
		at com.hazelcast.client.impl.spi.impl.ClientInvocation.invoke(ClientInvocation.java:156) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.engine.client.SeaTunnelHazelcastClient.requestAndGetCompletableFuture(SeaTunnelHazelcastClient.java:123) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.engine.client.SeaTunnelHazelcastClient.requestOnMasterAndGetCompletableFuture(SeaTunnelHazelcastClient.java:132) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.engine.client.job.ClientJobProxy.cancelJob(ClientJobProxy.java:148) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.shutdownHook(ClientExecuteCommand.java:254) ~[seatunnel-starter.jar:2.3.3]
		at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.lambda$null$0(ClientExecuteCommand.java:161) ~[seatunnel-starter.jar:2.3.3]
		at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640) ~[?:1.8.0_381]
		at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1632) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1067) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1703) ~[?:1.8.0_381]
		at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172) ~[?:1.8.0_381]
[INFO] 2023-10-23 16:40:47.449 +0800 - FINALIZE_SESSION

Zeta or Flink or Spark Version
Zeta
Java or Scala Version
java version "1.8.0_381"
Screenshots

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

+1


Husky lint:fix

I find that sometimes builds fail because of a prettier fix that could have been run automatically, and fixed, but isn't. Since we are using husky for commitlint, I feel like we could also easily use it to run prettier automatically as a pre-commit and fix the basic stuff. cc @hstove @kyranjamie

I don't think we should do this. It gets very frustrating when there's a long delay after creating/amending a commit.
I've tried this before and myself, and the rest of the team, eventually learns to add --no-verify to all their commits, mitigating the value of it anyway.

I agree that a pre-commit hook is undesirable.
I think the only reason Prettier doesn't get auto-fixed is because eslint only checks for .ts/.tsx, whereas the prettier command also checks for .js. We should just update eslint to check .js files.


[Flatpak] Failed to connect to wayland

i'm on fedora 32 silverblue, so i compiled it for flatpak.
i then ran it with
flatpak run com.freerdp.FreeRDP /u:<username> /p:<password> /v:<hostname>
and it outputted
wayland /app/bin/wlfreerdp
[13:59:42:886] [4:4] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[13:59:42:886] [4:4] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[13:59:42:887] [4:4] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[13:59:42:888] [4:4] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[13:59:42:207] [4:4] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized
[13:59:42:222] [4:4] [ERROR][com.freerdp.codec] - Failed to initialize libav parser
[13:59:42:223] [4:4] [ERROR][com.freerdp.core.codecs] - Failed to create h264 codec context
[13:59:42:225] [4:4] [ERROR][com.freerdp.client.wayland] - Failed to connect

you have the ffmpeg runtime installed? I think it should be org.freedesktop.Platform.ffmpeg
Flatpak support is still in early stages at this point, so any fixes are welcome.

ok, well then it should be in the dependencies

installing org.freedesktop.Platform.ffmpeg didn't fix the issue, it's now
[22:00:43:031] [4:4] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[22:00:43:031] [4:4] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[22:00:43:032] [4:4] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[22:00:43:032] [4:4] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[22:00:43:352] [4:4] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized
[22:00:43:369] [4:4] [ERROR][com.freerdp.codec] - Failed to initialize libav parser
[22:00:43:370] [4:4] [ERROR][com.freerdp.core.codecs] - Failed to create h264 codec context
[22:00:43:371] [4:4] [ERROR][com.freerdp.client.wayland] - Failed to connect

working with current build,
create a new issue if you still have problems.


License?

Hi there. I was curious about the license you'll choose to open source with. I maintain the fedi-related lists at https://delightful.club and those track only FOSS projects.

@aschrijver I am currently planning on using the MIT license!

Thank you! I have lined this project up for inclusion on the list (I work from some kind of backlog :)


⚠ ESPN has degraded performance

In c0941d2, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 1672 ms

Resolved: ESPN performance has improved in 07a7092.


Stack overflow on Objective#updateDisplayName and Objective#updateDisplayMode

SpongeVanilla version: 1.16.4-8.0.0 (commit 29d45444b0694c80836dd5298e503f4724188781)
Java version: 8
Operating System: Windows 10
Plugins: Cosmos

Hey, I'm publishing this issue now otherwise I'll forget to do it.
As the title says:
[21:43:47] [Server thread/ERROR] [Sponge/]:  Exception Details:
[21:43:47] [Server thread/ERROR] [Sponge/]:      java.lang.StackOverflowError: null
[21:43:47] [Server thread/ERROR] [Sponge/]:      org.spongepowered.common.adventure.SpongeAdventure.asAdventure(SpongeAdventure.java:190)
[21:43:47] [Server thread/ERROR] [Sponge/]:      net.minecraft.scoreboard.ScoreObjective.handler$zfb000$onSetDisplayName(ScoreObjective.java:1076)
[21:43:47] [Server thread/ERROR] [Sponge/]:      net.minecraft.scoreboard.ScoreObjective.setDisplayName(ScoreObjective.java)
[21:43:47] [Server thread/ERROR] [Sponge/]:      org.spongepowered.common.scoreboard.SpongeObjective.updateDisplayName(SpongeObjective.java:200)
[21:43:47] [Server thread/ERROR] [Sponge/]:      org.spongepowered.common.scoreboard.SpongeObjective.setDisplayName(SpongeObjective.java:86)

Same stack with updateDisplayMode
I'll try to look deeper and make a PR fix in the next days
Thanks for reading this issue.

Does this still happen on the latest versions? Running this code on commit 02135c2a9b6d824725a44813c819de705b6242b9 seems to work fine:
Objective obj = Objective.builder().name("test").displayName(Component.text("Test"))
        .criterion(Criteria.DUMMY).build();
obj.setDisplayName(Component.text("Test 2"));

Hey @JBYoshi
I will be really busy for the next weeks because I'm spending my free time on another project in my job.
I'll not be able to try the latest commit

If you could find some time to provide some more specific instructions on how to reproduce this, or find a longer version of the error trace in your old logs, that could also be helpful.


Fix the maven-publish workflow

This PR fixes(?) an issue that I might indent command lines incorrectly.
I am not sure about the behavior of indenting them one more level so better to make them at the same level.

Just formatting?
Or, the previous way failed?

@feeblefakie
The previous way failed.
https://github.com/scalar-labs/scalar-admin/actions/runs/3993616006/jobs/6850493792#step:4:1
I am not sure if it's problem from indenting so I make it the same as the scalar repository.

@supl Secrets like SIGNING_SECRET_KEY_RING are configured?

@supl Secrets like SIGNING_SECRET_KEY_RING are configured?

@feeblefakie
Ah, sorry, I thought they are set as organization-scoped secrets.
I just add mine to the repository secrets.


x/tools/gopls: error loading workspace: no metadata for ...

What version of Go are you using (go version)?

$ go version
go version go1.14.12 darwin/amd64

Does this issue reproduce with the latest release?
Yes!
What operating system and processor architecture are you using (go env)?
Mac OS 11.0.1
go env Output
$ go env
go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/xxx/Library/Caches/go-build"
GOENV="/Users/xxx/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY="bitbucket.org"
GONOSUMDB="bitbucket.org"
GOOS="darwin"
GOPATH="/Users/xxx/go/"
GOPRIVATE="bitbucket.org"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2q/tjh8ff852379vjlzgz_fww480000gn/T/go-build239085011=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

built the project from the root of the monorepo.

What did you expect to see?
No error from go extension.
What did you see instead?
The error caused the disable of source navigation to definitions/implementations.

[Error - 11:20:37 PM] 2020/12/07 23:20:37 warning: diagnose go.mod: no metadata for bitbucket.org/<monorepo>/type [bitbucket.org/<monorepo>/type.test]
	directory=<GOPATH>/src/goprivate/monorepo
	snapshot=365

VSCode is using root of the monorepo as workspace.

Thanks, @vishalkanaujia--did bitbucket.org/<monorepo>/type or its test get deleted between the branches? There is a bug that will be fixed in v0.6.0 by https://golang.org/cl/275273. Can you please try building gopls with that patch to see if that fixes the issue? You can do so by following these steps.
$ git clone https://go.googlesource.com/tools
$ cd tools
$ git fetch https://go.googlesource.com/tools refs/changes/73/275273/1 && git cherry-pick FETCH_HEAD
$ cd gopls
$ go install

Thanks, @vishalkanaujia -- did bitbucket.org/<monorepo>/type or its test get deleted between the branches? There is a bug that will be fixed in v0.6.0 by https://golang.org/cl/275273. Can you please try building gopls with that patch to see if that fixes the issue? You can do so by following these steps.
$ git clone https://go.googlesource.com/tools
$ cd tools
$ git fetch https://go.googlesource.com/tools refs/changes/73/275273/1 && git cherry-pick FETCH_HEAD
$ cd gopls
$ go install

This didn't fix the issue for me, although it might just be my GOPRIVATE modules affected now.

@takeyourhatoff: If you don't mind, could you file a new issue following the steps here: https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md#capturing-logs? It's usually easier to investigate different issues separately.

Thanks, @vishalkanaujia -- did bitbucket.org/<monorepo>/type or its test get deleted between the branches? There is a bug that will be fixed in v0.6.0 by https://golang.org/cl/275273. Can you please try building gopls with that patch to see if that fixes the issue? You can do so by following these steps.
$ git clone https://go.googlesource.com/tools
$ cd tools
$ git fetch https://go.googlesource.com/tools refs/changes/73/275273/1 && git cherry-pick FETCH_HEAD
$ cd gopls
$ go install

I still get the same errors.
[Error - 12:06:17 PM] 2020/12/08 12:06:17 errors diagnosing workspace: no metadata for bitbucket.org/<monorepo>/mycurrency [bitbucket.org/<monorepo>/mycurrency.test]
	snapshot=37
	directory=file://<$GOPATH>/src/goprivate/xxx

Would you be able to share a complete log (starting from the initialize message)? I understand that might be difficult to anonymize, so if you'd prefer to share it privately, that could work too.
Alternatively, if you're able to reproduce this consistently, maybe you could describe the characteristics of your workspace and see if we can construct a public repro example.

I hit the problem again. I have sent you a mail with log details. The problem disappears after restarting VSCode.

Can you please make sure to add the following to your settings?
"go.languageServerFlags": [
	"-rpc.trace",
]

The logs you attached are missing some detail. Also, it looks like your workspace root is not a module, and it is outside of $GOPATH/src. I would recommend opening a module or a subdirectory of $GOPATH/src.

Thanks for the recommendations. I think the gopls behavior is correct if the monorepo is placed in the $GOPATH/src/ or just the module of the subdirectory is opened in the editor.

Yep, that is correct--gopls doesn't work well if you open your entire GOPATH. More details can be found here: https://github.com/golang/go/issues/36899. Going to close this issue since it's been resolved.


Should use data_migrations table and not scheme migrations

Fixes #6

Sorry about this I already fixed this in version 1.1. See branch 1.1.beta1. I will push an official gem version up shortly.

You mean the rails4 branch right i dont see 1.1 version branch? The testcase reproducing the issue might be still usefull.

I was literally just about to push up the instructions for this today. 1.1.beta1 is pushed to rubygems, so you can do this in your gemfile:
gem 'nondestructive_migrations', "1.1.beta1"
Or, alternatively as you suggest point your gemfile to github and use the rails4 branch.


autoHeight + projections

This is tricky, as there is a chicken and egg problem (the projection definition receives the dimensions of the frame).

#1166 decides on the egg: only named projections are recognized, every other defaults to the golden ratio


error in azure devops commit link

when generating changelog, i seem to have an issue with the commit links for our custom azure devops repo:
* **<<PROJECT>>:** <<COMMIT_MESSAGE>> ([<<HASH>>](https://dev.azure.com/<<REPO_PATH>>/commits/<<HASH>>))
which should be:
* **<<PROJECT>>:** <<COMMIT_MESSAGE>> ([<<HASH>>](https://dev.azure.com/<<REPO_PATH>>/commit/<<HASH>>))
in order to work (no 's' at the end of 'commit')
not sure if it might have anything to do with our custom setup, or if it is a general bug.
if it is a general bug i can create a pr if you wish

Any news ? It seems to be a quick thing to fix. Is there some complications ?


Add a link to GOV.UK's Terms and Conditions to the footer

It was advised that we include this link prominently in the (rare)
event of legal action against us for something on the site.
Related to https://github.com/alphagov/static/pull/714.

:+1:

:thought_balloon: The Tariff actually also has it's own terms, perhaps these should also be on each page...


Beautify the UI Page

Title and Issue number

Title :Beautify the UI Page
Issue No. :#366
Code Stack : HTML CSS
Close #366

Video/Screenshots (mandatory)

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[ ] I have commented my code, particularly in hard-to-understand areas
[X] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?
 GsSOC'24

@Saumyatri want to suggest you to make a separate PR in the same issue . I am not closing the issue Instead please try to submit the PR within 5 days.

Okay will do that.


[BUG]: [NotInParallel] breaks [DependsOn]

Check the following code:
[NotInParallel]
public sealed class Dummy
{
    [Test]
    public void Step1()
    {
        throw new NotImplementedException();
    }

    [Test]
    [DependsOn(nameof(Step1))]
    public void Step2()
    {

    }

    [Test]
    [DependsOn(nameof(Step2))]
    public void Step3()
    {

    }
}

Expected: Step2 will fail since Step1 did not succeeed.
Actual: Step2 passes, but Step3 fails because Step1 has failed.

Struggling to recreate with your code. Must be some race condition or something 🤔

Try:
public class BaseClass;

[ClassConstructor<DummyClassConstructor>]
[NotInParallel]
public sealed class Dummy : BaseClass
{
    [Test]
    public void Step1()
    {
        throw new NotImplementedException();
    }

    [Test]
    [DependsOn(nameof(Step1))]
    public void Step2()
    {

    }

    [Test]
    [DependsOn(nameof(Step2))]
    public void Step3()
    {

    }
}

public class DummyClassConstructor : IClassConstructor
{
    public T Create<[DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicConstructors)] T>(ClassConstructorMetadata classConstructorMetadata) where T : class
    {
        if (typeof(T) != typeof(Dummy))
            throw new NotImplementedException();
        return (T)(object)new Dummy();
    }
}

Still the same for me! Can you confirm it still happens on 0.2.202?

I would, except now VS cannot run the tests; either it spends 2+ minutes trying to find tests before I cancel it, or it runs Step1/Step2 and never completes either of them. I can confirm that running the project under 0.2.195 gave me two fails and one pass, while 0.2.202 gives me three fails, as expected.

The latest version has broken Visual Studio for you?

The latest version has broken Visual Studio for you?

Yes. Was fine under 0.2.195, broken on 0.2.202

@viceroypenguin Can you reproduce it? My test explorer is working fine on the latest version.

Yes. This is what happens currently in VS 17.12 preview 5:

Can you try 0.2.208?

Yes, 0.2.208 works correctly. Thanks!


Adding the ability to have multiple selections on the select widget.

- Do you want to request a feature or report a bug?
This is a feature request.
- What is the current behavior?
Currently the select widget allows for the selection of a single string value with a dropdown menu.
- What is the expected behavior?
Would love to have the option to select multiple strings from an array through a radio selection menu. This functionality would be similar to Wordpress' current category selection menu. It'd be really helpful for posts that can be organized under multiple predefined categories.
The lists widget currently allows for comma separated values but need these values to be predefined.

@erquhart I'd be willing to work on this! Do we want a complete new widget for this or just an option on the current select?

Awesome! Current select was the plan. Just merged a PR to start using the react-select library, so that will help 👍🏼
Sent with GitHawk


Make the local-minimal version runnable again

What does this PR do?

It seems that some new lines have been added and the current local minimal version cannot run successfully. This PR fixes the issue.
Changes:

Traefik port 8080->8081: 8080 is very likely to be in use already;
Commented out BERT-ONNX-worker: Some file is missing. One can add it back when the file is provided;
Corrected comment format in the yaml file: # -> #!;
Generate .env file for model manager.

Before submitting / marking as 'ready to review'

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Who can review?
Feel free to tag members/contributors who may be interested in your PR.

@Rachneet a file is missing: https://github.com/UKP-SQuARE/square-core/blob/49ef708a2193b9057a9b61a12a6b65b63ebe3935/docker-compose.ytt.min.yaml#L218

Does anybody know how to add CI tests for this minimal version? @timbmg @Rachneet We can then make it easier for maintaining


Add option to create symlinks

Is your feature request related to a problem?
A clear description of what the problem is.
No.
Describe the solution
A clear description of what you want.
I would like to be able to create symlinks from within the applications as currently you would have to use the command line with the command mklink.
Describe alternatives you've considered
A clear description of any alternative solutions or features you've considered.
shortcuts, but they do not perform like symlinks as with symlinks they are a direct portal.
Additional comment
Add any other comment or screenshots about the feature request here. What device type/UI layout and app version?

This is already possible in windows explorer via the Link Shell Extension. The only problem I have is that the "Link Properties" is missing in Files.

Merging with #9991


Update minio-go to output new mint log format

minio-go tests are used in mint to test Minio server. minio-go logs need to be updated in the format below so that mint logs can be easily parsed.
{
    "name":"mc", // SDK Name
    "function":"testPresignGetObject", // Test function name
    "description": "test function description (optional)", //  Test function description
    "args":"", // key value map, varName:value. Only arguements that devs may be interested in
    "duration":"", // duration of the whole test
    "status":"", // can be PASS, FAIL, NA
    "alert":"failed to download pre-signed object(optional)", // error related, human readable message. Should be taken care of if present
    "error":"stack-trace/exception message(only in case of failure)" // actual low level exception/error thrown by the program
}

Fixed by #812


ROCKET-153: Log network errors only on debug

Jira: ROCKET-153
Log from this PR was unstructured and logged on every occurrence, so it lead to confusion when I though from CloudWatch logs that this error is unhandled and interrupts the main process.

Moved this to debug level since we throw it anyway and handle on top level.

Missed


Use a different cluster for pr e2e runs

Signed-off-by: Ahmed ElSayed<EMAIL_ADDRESS>
Provide a description of what has been changed
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) (if applicable)
[x] Changelog has been updated

Fixes #

/run-e2e

This is super nice @ahmelsayed !!
Thanks! ❤

thanks @ahmelsayed ! ❤


Bump in-toto dependency.

I noticed that there were some breaking changes in the in-toto version pulled in compared with the version in sigstore.  This updates things to HEAD.

cc @priyawadhwa @dlorenc

Hmm...
tekton-chains-controller-7f4d9cc466-4mrdl   0/1   CrashLoopBackOff   5     5m10s

Hello old friend:
kubectl logs -n tekton-chains      tekton-chains-controller-5bcfbf8484-rmk46
/ko-app/controller flag redefined: log_dir
panic: /ko-app/controller flag redefined: log_dir

Looks like chains is depending on the cli package, which pulls in glog (conflicts with K8s klog).
The two things I found that need to move out to make a depcheck_test pass for chains are:

cli.LoadECDSAPrivateKey
cli.DssePayloadType

I will look into splitting these out in the morning.

Ok, I am optimistic that this will pass, but I had to tweak an e2e test to reflect a change pulled in via the updated deps.

/lgtm

/approve

Merge conflict, fixing it now

Rebased on main and updated deps, but I'll need a fresh /lgtm

/lgtm


publish new version to npm

Hi @mantoni
I'd like to publish my updated version to npm, would you mind adding me as a maintainer of the module ?
My username on npm is: maks

I still use this project occasionally and will maybe need to make changes in the future myself. It would be annoying if the npm package was updated from two different repositories. If you could contribute your changes back to the repo here, we can collaborate on the work and publish from a common code base.

@mantoni yes, I'd be very happy to do that - I only started the fork based on your previous comment that you didn't have time to work on it and that I should maintain it.
I'll open PRs against your repo.

Cool. I actually offered to grant you push access 👍

Oh! Sorry I completely misunderstood, thanks!

I've started putting through the PRs, they are "stacked", so are intended to me merged in order, hope thats ok.


Explore the elementary properties of the MS gate

Create a file with basic information about the MS gate

What are the special gates for specific parameters?
What are the canonical parameter?
Maybe something on two qubit state construction?

The Mølmer-Sørensen gate given by
$$\begin{align} \text{MS}(\theta) =
\begin{pmatrix}
\cos \big(\frac{\theta}{2} \big) & 0 & 0 & i\sin \big(\frac{\theta}{2} \big) \
0 & \cos \big(\frac{\theta}{2} \big) & -i\sin \big(\frac{\theta}{2} \big) & 0 \
0 & -i\sin \big(\frac{\theta}{2} \big) & \cos \big(\frac{\theta}{2} \big) & 0 \
i\sin \big(\frac{\theta}{2} \big) & 0 & 0 & \cos \big(\frac{\theta}{2} \big) \
\end{pmatrix}
\end{align}$$
is identical to the $YY$ gate

I discuss with Yunong about this and here is what he said:

Try to reproduce Optimal synthesis into fixed XX interactions for the Molmer-Sorenson gate family. If it turns out to be new and different, great! Then we continue our plan.
If not, I believe it is also a good practice to get yourself familiarized with the theory and all details, then I have another cool and slightly challenging topic for you: the hardware provider Rigetti exposes two kinds of 2-qubit gate: iSWAP and CPhase. Compilation using these 2 gates together were never explored, it will also be extremely interesting.


Notebook UI - Markdown toolbar - Headings dropdown

Adds heading dropdown to markdown toolbar:

Expected behavior:

User positions their cursor on the line they want the heading changed.
User selects one of four options: Heading 1, Heading 2, Heading 3, Paragraph.
Entire line style changes to match selected heading/paragraph.

Coverage increased (+0.04%) to 34.425% when pulling a4b46261615edb8e477c5bd63e3a0704643bdf89 on notebook-ui-markdown-toolbar-headings into 637bc8d5ba8cc51f8d74e6db87fa7d93c6b2ca3a on main.


juicer docker and awk parallel processing

Hi,
I'm a new user in juicer, I have two request.

when I run juicer, after the bwa mem mapping step I found this step awk -v fname=*.fastq.gz -f=*.awk ... consumed a lot of time but only one process running, I hope this process could run in parallel way.
I'm using juicer docker docker pull aidenlab/juicer there is no Dockerfile on the dockerhub page, could you please share the file on your docker hub page?

Thanks for your great work.
Cheers
WANG

substitute gzip with pigz


dist: pick the right host triple on ARMv7 devices

Uses the "hackish" solution suggested by @alexcrichton in #308.
Check commit messages for details.
r? @brson

updated to use OUT_DIR instead of CARGO_MANIFEST_DIR.

Oh my god it's horrible...


colab

Hi @enhuiz 👋 I am trying to make a simple colab please help me https://github.com/camenduru/vall-e-colab

Please raise specific questions, thanks.

sorry 😔


RUMM-2504: Switch to the SDK v2 storage component

What does this PR do?
This change does a switch to the Storage implementation written earlier. While it is not used as it should be in the feature configuration per SDK v2 plan, this change helps to minimize the diff of the transition and makes a proof that new component works.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1051 (5659de8) into feature/sdkv2 (f913074) will decrease coverage by 0.02%.
The diff coverage is 88.24%.

@@                Coverage Diff                @@
##           feature/sdkv2    #1051      +/-   ##
=================================================
- Coverage          82.83%   82.81%   -0.02%
=================================================
  Files                306      306
  Lines              10080    10077       -3
  Branches            1642     1639       -3
=================================================
- Hits                8349     8345       -4
- Misses              1230     1232       +2
+ Partials             501      500       -1

Impacted Files
Coverage Δ

...id/v2/core/internal/storage/ConsentAwareStorage.kt
96.77% <ø> (-0.03%)
:arrow_down:

.../internal/rum/WebViewRumFilePersistenceStrategy.kt
62.96% <33.33%> (-1.04%)
:arrow_down:

...rnal/persistence/file/batch/BatchFileDataWriter.kt
81.82% <85.71%> (-3.90%)
:arrow_down:

...istence/file/batch/BatchFilePersistenceStrategy.kt
100.00% <100.00%> (ø)

...tadog/android/rum/internal/domain/RumDataWriter.kt
85.71% <100.00%> (+0.53%)
:arrow_up:

.../rum/internal/domain/RumFilePersistenceStrategy.kt
100.00% <100.00%> (ø)

...tadog/android/core/internal/net/CurlInterceptor.kt
80.95% <0.00%> (-2.38%)
:arrow_down:

...rc/main/java/com/datadog/opentracing/DDTracer.java
55.65% <0.00%> (-0.42%)
:arrow_down:

...android/v2/core/internal/DatadogContextProvider.kt
81.97% <0.00%> (ø)

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
88.36% <0.00%> (+1.06%)
:arrow_up:

... and 1 more


Fix unsound problem in Row::row_unchecked

Hi, thanks for your folk of arrow and best wishes first.
We have found a simple unsound problem in ::compute::sort::row::Rows.
The function Rows::row_unchecked is wrongly marked as safe, which would confuse the boundary between safe and unsafe Rust.
Since the repository of arrow2 have been archived, we cannot create any issue report. So we directly open this PR to mark the function row_unchecked as 'unsafe' and add a debug_assert! macro for safety consideration.

Merge in master to fix (most of) CI


Update the link for country code

Link does not work - http://go.microsoft.com/fwlink/?LinkId=615951

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

ID: 4b243c23-4c18-7a05-4856-1fad04318204
Version Independent ID: 56bd83d2-caf0-5e0c-1963-2e5b87810e9a
Content: Search-CsOnlineTelephoneNumberInventory (skype)
Content Source: skype/skype-ps/skype/Search-CsOnlineTelephoneNumberInventory.md
Service: skypeforbusiness-powershell
GitHub Login: @kenwith
Microsoft Alias: kenwith

@Neeraj-6596 Thanks for letting us know. We are working on this.

@tonysmit is helping us track this down and we will get this fixed. Thanks for reporting @Neeraj-6596 ! @nsshommo - we might just be able to update the fwlink to point to the right location or we might need a pull request if there are changes to the docs. Thanks for follow through!

Submitted PR on this one. Trying to find similar articles.

@nsshommo - merged https://github.com/MicrosoftDocs/office-docs-powershell/pull/932 and closing this one until we can get link resolved.


What's new?" on the landing page

Add a link to  the landing page to the latest release and release notes "What's New ?"
latest: https://github.com/splunk/security_content/releases/latest

done :-)


S3 Controller install fails - Issue with the Script - ./scripts/build-controller.sh: line 110: controller-gen: command not found

Describe the bug
make build-controller SERVICE=$SERVICE
go build -tags codegen -o bin/ack-generate cmd/ack-generate/main.go
./scripts/build-controller.sh s3
go: downloading sigs.k8s.io/controller-tools v0.3.1-0.20200716001835-4a903ddb7005
go: found sigs.k8s.io/controller-tools/cmd/controller-gen in sigs.k8s.io/controller-tools v0.3.1-0.20200716001835-4a903ddb7005
go: downloading gopkg.in/yaml.v3 v3.0.0-20190905181640-827449938966
go: downloading golang.org/x/tools v0.0.0-20200616195046-dc31b401abb5
go: downloading github.com/inconshreveable/mousetrap v1.0.0
go: downloading github.com/fatih/color v1.7.0
go: downloading github.com/gobuffalo/flect v0.2.0
go: downloading github.com/mattn/go-colorable v0.1.2
go: downloading github.com/mattn/go-isatty v0.0.8
go: downloading golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543
go: downloading golang.org/x/mod v0.2.0
Building Kubernetes API objects for s3
Generating deepcopy code for s3
./scripts/build-controller.sh: line 110: controller-gen: command not found
Generating custom resource definitions for s3
./scripts/build-controller.sh: line 116: controller-gen: command not found
Building service controller for s3
Generating RBAC manifests for s3
./scripts/build-controller.sh: line 130: controller-gen: command not found
Steps to reproduce
Install the Std. prereq. as per ACK site
Expected outcome
Should be able to install the S3 Controller successfully
Environment
Kind cluster on Mac
kind version
kind v0.8.1 go1.14.4 darwin/amd64

Kubernetes version: 1.18.2
Using EKS (yes/no), if so version? No
AWS service targeted (S3, RDS, etc.) S3
kubectl cluster-info --context kind-kind
Kubernetes master is running at https://<IP_ADDRESS>:52436
KubeDNS is running at https://<IP_ADDRESS>:52436/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

Apparently, running go get to install controller-gen on Mac doesn't place the downloaded/installed controller-gen binary into the PATH. :(

controller-gen is part of k8s controller-tools. Check out https://github.com/kubernetes-sigs/controller-tools.git and install controller-gen under $GOPATH/bin, and then you'll be able to run 'make build-controller SERVICE=$SERVICE' with success.

Can this be incorporated back into the docs as a pre-requisite?

Can this be incorporated back into the docs as a pre-requisite?

Totally.

OK, closing this now (again), it landed in https://aws.github.io/aws-controllers-k8s/dev-docs/testing/

For anyone hitting this problem also ensure the following $GOPATH/bin is part of your $PATH
See https://github.com/actions/setup-go/issues/14 for more information

For anyone hitting this problem also ensure the following $GOPATH/bin is part of your $PATH
See https://github.com/actions/setup-go/issues/14 for more information


Improve deprecation copy

Description
Make copy consistent for all deprecated columns

Put these changes on https://github.com/glideapps/glide-code-columns/pull/164


How can I time cupy function and compare against numpy?

How can I time cupy function and compare against numpy?
In PyTorch, there is a torch.cuda.synchronize() function to wait for all cuda functions to complete before printing time. Is there similar function for cupy so that I can time the function properly?

You can just use timeit -- cupy will block as soon as the same variables (underling arrays on the GPU) are accessed, in which case it behaves like numpy vis-a-vis synchronicity.

The equivalent in CuPy is cupy.cuda.stream.get_current_stream().synchronize().


make command broken out of the box

Steps to reproduce (from the README):
$ git clone https://github.com/wjwwood/serial.git
$ cd serial
$ make

Output:
cd build && cmake -DCMAKE_INSTALL_PREFIX=/tmp/usr/local ..
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is GNU 12.3.0
-- The CXX compiler identification is Clang 15.0.7
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - broken
CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCXXCompiler.cmake:63 (message):
  The C++ compiler

    "/usr/bin/c++"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/loup/projects/_ext/serial/build/CMakeFiles/CMakeScratch/TryCompile-kBMdvf

    Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_11a87/fast && gmake[1]: Entering directory '/home/loup/projects/_ext/serial/build/CMakeFiles/CMakeScratch/TryCompile-kBMdvf'
    /usr/bin/gmake  -f CMakeFiles/cmTC_11a87.dir/build.make CMakeFiles/cmTC_11a87.dir/build
    gmake[2]: Entering directory '/home/loup/projects/_ext/serial/build/CMakeFiles/CMakeScratch/TryCompile-kBMdvf'
    Building CXX object CMakeFiles/cmTC_11a87.dir/testCXXCompiler.cxx.o
    /usr/bin/c++    -MD -MT CMakeFiles/cmTC_11a87.dir/testCXXCompiler.cxx.o -MF CMakeFiles/cmTC_11a87.dir/testCXXCompiler.cxx.o.d -o CMakeFiles/cmTC_11a87.dir/testCXXCompiler.cxx.o -c /home/loup/projects/_ext/serial/build/CMakeFiles/CMakeScratch/TryCompile-kBMdvf/testCXXCompiler.cxx
    Linking CXX executable cmTC_11a87
    /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_11a87.dir/link.txt --verbose=1
    /usr/bin/c++ -rdynamic CMakeFiles/cmTC_11a87.dir/testCXXCompiler.cxx.o -o cmTC_11a87
    /usr/bin/ld: cannot find -lstdc++: No such file or directory
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    gmake[2]: *** [CMakeFiles/cmTC_11a87.dir/build.make:100: cmTC_11a87] Error 1
    gmake[2]: Leaving directory '/home/loup/projects/_ext/serial/build/CMakeFiles/CMakeScratch/TryCompile-kBMdvf'
    gmake[1]: *** [Makefile:127: cmTC_11a87/fast] Error 2
    gmake[1]: Leaving directory '/home/loup/projects/_ext/serial/build/CMakeFiles/CMakeScratch/TryCompile-kBMdvf'

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)

-- Configuring incomplete, errors occurred!
See also "/home/loup/projects/_ext/serial/build/CMakeFiles/CMakeOutput.log".
See also "/home/loup/projects/_ext/serial/build/CMakeFiles/CMakeError.log".
make: *** [Makefile:36: serial] Error 1

Running on the Ubuntu 23.04, with the following versions:
$ cmake --version
cmake version 3.25.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

$ /usr/bin/c++ --version
Ubuntu clang version 15.0.7
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

Did I miss something?

same problem anyone can help?


Migrate all bValues' stringValue implementations

Purpose

Resolve https://github.com/ballerina-platform/ballerina-lang/issues/20886

Approach

Add a new interface method to BValue which would be removed later

Samples

N/A

Remarks

https://github.com/ballerina-platform/ballerina-lang/pull/21205

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #21794 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #21794   +/-   ##
=======================================
  Coverage   14.72%   14.72%
=======================================
  Files          51       51
  Lines        1399     1399
  Branches      214      214
=======================================
  Hits          206      206
  Misses       1177     1177
  Partials       16       16

Continue to review full report at Codecov.

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

 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.


Unknown version numbers?!

I'm a bit mystified by your version numbers in MSFT_xSCSMAPowerShellSetup.
When I download System Center 2016 Orchestrator from MVLS, the version I get for SetupOrchestrator.exe is <IP_ADDRESS>?!? (the other resources are correct - e.g. 7.3.345.0)
Best,
-Brian

This was resolved in PR #21.


Excluding labels doesn't work

Describe the bug
If using cli with -l/--exclude-labels flag, the filtering is not working
To Reproduce
Steps to reproduce the behavior:
Resource labels:
kubectl get pvc -n default pvc-claim-2 -o jsonpath={.metadata.labels}

{"kor/report":"false","reporting":"no"}

Command:
kor -l reporting=no persistentvolumeclaim

Output:
kor version: vdev

  _  _____  ____
 | |/ / _ \|  _ \
 | ' / | | | |_) |
 | . \ |_| |  _ <
 |_|\_\___/|_| \_\

Unused resources in namespace: "default"
+---+---------------+---------------+
| # | RESOURCE TYPE | RESOURCE NAME |
+---+---------------+---------------+
| 1 | Pvc           | pvc-claim-2   |
+---+---------------+---------------+

Expected behavior
The resources shouldn't be matched but the output is the following:
kor --exclude-labels reporting=no persistentvolumeclaim
kor version: vdev

  _  _____  ____
 | |/ / _ \|  _ \
 | ' / | | | |_) |
 | . \ |_| |  _ <
 |_|\_\___/|_| \_\

Unused resources in namespace: "default"
+---+---------------+---------------+
| # | RESOURCE TYPE | RESOURCE NAME |
+---+---------------+---------------+
| 1 | Pvc           | pvc-claim-2   |
+---+---------------+---------------+

OS version, architecture and kor version
Darwin_arm64
Kor version: vdev (brew installation of stable version 0.5.6)

Marking this as a bug
@nemcikjan in the meantime can you try this https://github.com/yonahd/kor?tab=readme-ov-file#ignore-resources
This should help exclude the resource

/assign
Not all resources were refactored with the new filtering interface, I'll create a PR for that.


Fix: Scrollbar fix on modal('hide');

I found a bug when hide the modal with modal('hide') the modal-open will not be removed from the body this will not bring back the scrollbar, fix is
After: Event("hide.bs.modal"),
i add: this.$body.removeClass("modal-open"),
I fixed it in the .min file, so need also fix in normal file :+1:
I think somewhere in Modal.prototype.hide = function (e) {}

What version of Bootstrap are you using?
What OS and browser are you using?
Can you post a JS Fiddle of the bug and describe how to reproduce it?

@jsonjuri Our JS already does what you're suggesting:
https://github.com/twbs/bootstrap/blob/ba1345f144283d579b07cd40b5ae5a5b84d2b2e7/js/modal.js#L174
https://github.com/twbs/bootstrap/blob/ba1345f144283d579b07cd40b5ae5a5b84d2b2e7/js/modal.js#L137

Closing due to lack of response.

Possibly related: https://github.com/twbs/bootstrap/issues/16469


DOC: Corrected word usage in example_pandas.rst

There was a "homophone" (hear instead of here) in the first admonition. I also edited the rest of that sentence to make it read better (in my opinion at least).

Thanks!