Update Material UI to v5 and others

Putting this out here for visibility.

Once MUI v5 migration is done, a separate PR could React v18 and other libraries that are still not the latest stable major versions.

Disclaimer: some styles had changed during the upgrade, not all whitespace are equal and some colors have changed. These could be fixed in another PR, while touching the MUI usage as well, to fix few accessibility issues, such as low contrast and focus styles.
Fonts are loaded now locally, not from Google Fonts, so thy work when the environment has no access to the internet.

The issue is now with BulkOperation, and the use of gridExpandedSortedRowEntriesSelector for getting the currently selected rows...
Something to do with the Grid not being available at that point maybe?
Similar issue is with ActionButtons...

Again Codacy has issues with finding any packages that were updated in this PR.

It might also be that I havent really looked what exactly is the use case and rewrite it, as it might be that the earlier usage was very different and the approach might not even exist anymore in the upgraded version.. maybe

It seems like two things were trying to do the same thing once a build has been chose, to update the selected build information.
Commented out the DataGrid state listener, so we could talk here what to do with it...
@pashidlos how to move forward?

The onStateChange is only documented at the version 4 of DataGrid documentation, https://v4.mui.com/components/data-grid/events/#catalog-of-events, and cannot be found in v5 nor v6, while still it does something.
The filtering and sorting seems to work without this, hence removing it.

@paazmaya noticed few issues while testing it

cannot use bulk actions - on selecting item error in console
TestRun details does not contain canvas images
TestRun details. header is not filled entirely

@paazmaya noticed few issues while testing it
* cannot use bulk actions - on selecting item error in console

* TestRun details does not contain canvas images

* TestRun details. header is not filled entirely

could you take a look on those?

@paazmaya noticed few issues while testing it
* cannot use bulk actions - on selecting item error in console

Done, was referencing row data in wrong depth.

* TestRun details does not contain canvas images

Cannot find the cause, suspecting that some of the useEffects is not triggering...

* TestRun details. header is not filled entirely

could you take a look on those?

I am starting to see that it is something to do with react-konva, it does not render at all...

@paazmaya seems we have merge conflicts due to different formatting
do you use VS code with plugin esbenp.prettier-vscode?
could you also squash commits so I could try rebasing on master
or would you prefere do to it?

I removed the Prettier plugin from VS Code, as that plugin was making changes that were then changed again once ran the command line version.
I will do squash rebase today.

Just came across https://mui.com/system/styles/advanced/, while looking at why JSS is not building:

@mui/styles is the legacy styling solution for Material UI. It depends on JSS as a styling solution, which is not used in the @mui/material anymore, deprecated in v5. If you don't want to have both Emotion & JSS in your bundle, please refer to the @mui/system documentation which is the recommended alternative.

and

⚠ @mui/styles is not compatible with React.StrictMode or React 18.

Hence will also migrate away from that within this PR, as there are issues with the build.

docker image is failed to compile
#0 42.29 [vite]: Rollup failed to resolve import "jss-plugin-{}" from<EMAIL_ADDRESS>#0 42.29 This is most likely unintended because it can break your application at runtime.
#0 42.29 If you do want to externalize this module explicitly add it to
#0 42.29 `build.rollupOptions.external`
#0 42.33 error during build:
#0 42.33 Error: [vite]: Rollup failed to resolve import "jss-plugin-{}" from<EMAIL_ADDRESS>#0 42.33 This is most likely unintended because it can break your application at runtime.
#0 42.33 If you do want to externalize this module explicitly add it to
#0 42.33 `build.rollupOptions.external`
#0 42.33     at viteWarn (file:///app/node_modules/vite/dist/node/chunks/dep-abb4f102.js:48051:27)
#0 42.33     at onwarn (file:///app/node_modules/@vitejs/plugin-react/dist/index.mjs:238:9)
#0 42.33     at onRollupWarning (file:///app/node_modules/vite/dist/node/chunks/dep-abb4f102.js:48080:9)
#0 42.33     at onwarn (file:///app/node_modules/vite/dist/node/chunks/dep-abb4f102.js:47814:13)
#0 42.33     at file:///app/node_modules/vite/node_modules/rollup/dist/es/shared/node-entry.js:24066:13
#0 42.33     at Object.logger [as onLog] (file:///app/node_modules/vite/node_modules/rollup/dist/es/shared/node-entry.js:25738:9)
#0 42.33     at ModuleLoader.handleInvalidResolvedId (file:///app/node_modules/vite/node_modules/rollup/dist/es/shared/node-entry.js:24652:26)
#0 42.33     at file:///app/node_modules/vite/node_modules/rollup/dist/es/shared/node-entry.js:24612:26
------
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1

@pashidlos regarding the last commit https://github.com/Visual-Regression-Tracker/frontend/pull/318/commits/09f136a4b1d6c521e7666c2144739167373db468
The reason for me making the styles migration was that jss breaks the build.
While the define global is removed from build configuration, running npm start and using guided tour is broken.
Perhaps we can live momentarily with guided tour being broken, as continuing in this PR gets more complex, and fix the styles migration soon, which would also allow getting rid of jss and then fix guided tour.

@paazmaya now it seems to work both run and build command
sure, we need to migrate that part

Codacy is still blocking this PR...


Deaths with no killer (assist only) do not appear in the death list

Problem
Not all kills shown on tibia.com appear in the deathlog in tibiadata
Expected behavior
all kills are shown, even if some fields cannot be populated
Detail
Any death without any identifiable killer that only has "assists" is omitted from the death list. These deaths can occur when for example a character is killed only by members of their own guild. Presumably these kills are omitted because not all information is available, (Level the death occurred at etc).
I think these deaths should still appear in the deathlist for the character, otherwise this deathlist does not accurately reflect what happened.
Examples
Characters which (currently) serve as examples:

Sir Pixxy
Suedi Baaz

Extra Background
Deaths of this kind are common on retro-hardcore servers where kill selling is widespread, as being in the same guild as the kill seller reduces protection zone block so buyers do not have to wait the full 15 minutes.

I'm looking into this and have stored away the required html to make a fix for this.
The interesting thing with for instance Sir Pixxy is that the level is not present in the death entry. Thats why the regex is not catching that entry in the first place.

yeah - it seems like as it can't be logged as "died at level X by" because it was not classed as a PvE death, and it can't be logged as "killed at level X by" because after they remove "Assist" players from the list of killers, there are none, so it seems it just skips the "cause" part of the log (which is what includes the level) and prints the assists.
You can see this causes similar problems for other fansites too e.g. here: https://www.tibiaring.com/char.php?c=Sir+Pixxy it shows multiple deaths all at the same level because the level is omitted in this situation.
In an ideal world I'd love for Cip to change this behaviour so that the level the character dies at is printed, and it's clarified that it was a PvP death e.g. if the killers list is empty just write something vague "Killed at level X in player combat, Assisted by: Y". I feel like these two data points are "required fields" from the players perspective that should always be conveyed (somehow) in the death log. That's a matter for the proposals forum though!

@tobiasehlert  this bug is still available?


Submission and local evaluation of End-To-End Forecasting

Hi,
I cannot find the tutorials for submission and local evaluaiton of End-to-end forecasting task.
Are you going to release the baseline code of E2E forecasting? So that we can easily understand your evaluation metrics.
Thanks.

Hi @foolhard,
Thanks for your interest in the end-to-end forecasting task. Please check out our baselines at https://github.com/neeharperi/LT3D and let me know if you have any further questions. We'll continue to add additional baselines in the coming weeks.
Neehar

@neeharperi Thanks for your feedback. I will try your baseline code.


-R doesn't accept unicode character

Problematic if user wants to test for example specific part of the request that contains binary data

Fixed in https://github.com/hansmach1ne/LFImap/commit/a69201abc9f3e4b1a58a160201aa25cf4b198b4f.
Open file handle with encoding=latin1


SOLR-16198: Introduce tabbed blocks again

https://issues.apache.org/jira/browse/SOLR-16198
Description
This PR introduces tabbed sections again in the documentation by using @asciidoctor/tabs.
Solution
The changes add a new dependency to @asciidoctor/tabs that is installed during antora setup. The javascript for controlling the tabs (provided by asciidoctor/tabs) is added to the UI bundle via supplemental_files and loaded via the footer-content.hbs. Custom styles are used to better match the current documentation design.
I tried to follow the instructions from Asciidoctor/Tabs - How to Use with Antora.
See https://github.com/apache/solr/commit/643a76c3812984491b341548dec7dccf0765d0b1 for a clearer overview of the changes related to the addition of the library.
Tests
I have reviewed the generated documentation for correctness via the Gradle task buildLocalSite and by enabling the local UI via SOLR_REF_GUIDE_BUILD_LOCAL_UI=true.
Checklist

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ ] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.
[x] I have added documentation for the Reference Guide

Additional Information
Since it is my first time working with ASCIIDoc and the documentation, I am not sure if the necessary changes are sufficient for the dependency to be correctly added and loaded in the public documentation on release. I assume that the task setOfficialAntoraYaml needs also to be run, but I didn't commit any changes made by the task.
I tried to keep the changes minimal, but since it is a notation hassle the changes spread across multiple files.
Additionally, the library supports documentation-wide tab-synchronization via the session, but I didn't tested or turned it on yet.
EDIT: I also tried to keep the IDs the same, so that any existing reference (couldn't find any in the documentation) to the tabs would not break. But due to the way the IDs are assigned to the tabs and the linking / auto-selecting of tabs, it was not possible. So I provided similar IDs to the tab sections. Referencing is still possible, just with different IDs (see dev-guide changes for detials).

Gave this a quick try, using gw buildLocalSite and getting this:

Gave this a quick try, using gw buildLocalSite and getting this:

Are you eventually using the nightly UI bundle? Because this is the default behavior and you need to explicitly enable the use of a local bundle via the env variable SOLR_REF_GUIDE_BUILD_LOCAL_UI=trueor with-Prefguide.buildLocalUI=true` (as stated below) because I made changes in the bundle.
https://github.com/apache/solr/blob/07ff133852545054d4fe13473588343e3e4d33b5/solr/solr-ref-guide/README.adoc#L45

Just reran it with the proper settings, thanks...  The use of the tabs is great, it cuts down on the amount of space used...
One nit, I sort of wish it was even clearer they are tabs.   I tried out a tabs tool on https://docs.querqy.org/querqy/index.html, and you can see it does some more visual stuff:

Regardless of that, this is a nice improvement.    Since I've never touched this type of change to the ref guide, I'd love to see someone else also review this PR.....

I agree, it could be improved. Based on the examples I can update it to look something like below. Better results can be achieved with a thinner border that differ a bit from the usual border of examples. If that is ok, I can update it accordingly.

That looks MUCH better!  I like the thinner line, with the bold header....     This is looking really great.

It sounds like this pr is good to go, hopefully @HoustonPutman will create the jira for adding missing licenses!
We don't normally credit ref guide changes but maybe should with this one since it's improving the tooling.  @malliaridis how do you want to be credited?

We don't normally credit ref guide changes but maybe should with this one since it's improving the tooling. @malliaridis how do you want to be credited?

Your kind offer @epugh is more than enough. You don't have to make an exception for this. 😅

This should absolutely be credited in the changelog!

Okay, I want to commit this.  I believe that when we cut the new ref guide for 9.7, that the changes to the ui bundle will then happen IIUC....

It won't but that's ok, there's a jenkins job to do it manually.


CkIO processor placement options are ignored

Original author: Thomas Quinn
Original issue: https://charm.cs.illinois.edu/redmine/issues/551

The code documentation for Ck::IO::Options describes "basePE", "skipPEs", and "activePEs" to specify which processors are to participate in an IO session.  However, the session array is created without a processor map, so the processors are always allocated with the default map (round-robin?).  Inserting debugging statements into the CkIO code verifies that this is the case.

Original date: 2016-02-26 21:11:18

The use of CkIO::Options does not have a use case as of now. The bug was about the misleading source code documentation for CkIO::Options. This was modified to indicate that CkIO::Options is not a stable interface.(Fix: ~~https://charm.cs.illinois.edu/gerrit/#/c/1092/~~ https://github.com/UIUC-PPL/charm/commit/1b2787598a0918b293fb165127c72248b18ff58d)

Original date: 2016-03-03 19:46:55

Knowing that ChaNGa is actually using CkIO for its output in production runs, we can task someone to study its performance if that's a bottleneck, and make things work as they would actually need to in order to improve that.

Original date: 2016-03-03 22:33:30

It looks like the original bug was addressed in the literal sense.  Phil's change seems to go towards a more fundamental intuition that the bug report was issued due to someone hunting for performance tuning possibilities in the (unsupported) placement schemes.   If there is a use case (perhaps performance related) that requires placement support in CkIO, that should be opened as a new redmine issue, with pertinent details, and refer to this one.


Unmounted component setState fix

This code in TransitionMotion was a source of bug for us in testing.
    if (this.unmounting) {
        return;
    }
    // TODO: when config is {a: 10} and dest is {a: 10} do we raf once and
    // call cb? No, otherwise accidental parent rerender causes cb trigger
    this.animationID = defaultRaf((timestamp) => {
      const propStyles = this.props.styles;
      ...
      this.setState({
        currentStyles: newCurrentStyles,
        currentVelocities: newCurrentVelocities,
        lastIdealStyles: newLastIdealStyles,
        lastIdealVelocities: newLastIdealVelocities,
        mergedPropsStyles: newMergedPropsStyles,
      });
      ...
    }

The problem is that if execution passes the conditional if (this.unmounting), then executes async defaultRaf and after that component unmounts and after that the callback of defaultRaf is called, then setState will be called on unmounted component.
This fix solves the problem.

Thanks. Wouldn't the right fix be having the check in both locations? This way we bail early instead of allocating another callback.

@chenglou Done!


Heapster 1.3.0 failed to gather metrics on openshift v1.3.3

Heapster 1.3.0 failed to gather metrics on openshift v1.3.3.
It misses cpu/limit and cpu/request, memory/limit and memory/request
Environment:
Deployed heapster version: 1.3.0
OpenShift Master: v1.3.3
Kubernetes Master: v1.3.0+52492b4
Heapster output:
I0321 20:55:16.080117       1 heapster.go:72] /heapster --source=kubernetes:https://kubernetes.default.svc:443?useServiceAccount=true&kubeletHttps=true&kubeletPort=10250 --tls_cert=/secrets/heapster.cert --tls_key=/secrets/heapster.key --tls_client_ca=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt --allowed_users=system:master-proxy --metric_resolution=60s --logtostderr=true --sink=influxdb:http://<IP_ADDRESS>:8086/?user=admin&pw=admin&db=cloud_research_openshift_sdntest_netcracker_com&withfields=false
I0321 20:55:16.080159       1 heapster.go:73] Heapster version v1.3.0
I0321 20:55:16.080386       1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default.svc:443" and version v1
...
E0321 20:55:16.291558       1 reflector.go:190] k8s.io/heapster/metrics/heapster.go:322: Failed to list *v1.Pod: unexpected EOF
E0321 20:55:17.336394       1 reflector.go:190] k8s.io/heapster/metrics/heapster.go:322: Failed to list *v1.Pod: unexpected EOF
...and more and more...

@DirectXMan12 can you please investigate?

First of all, I'd reccomend that you match Heapster versions with Kubernetes/OpenShift versions -- Heapster 1.3 is much newer than Kubernetes/OpenShift 1.3.
Please also ensure proper network connectivity from the pod to the master.


Use the same case in proto for properties

Some variables are in lower case, upper case or a mix and it is not consistant through the projets


Icons: Allow Bridge-specified icons

Nice addition, I like it :+1:
Thanks for the PR!

Thanks for maintaining RSS-Bridge!


Enhancement:  Pick map library and implement it in web app

What:

I would like there to be a dynamically rendered map on the page
This should appear after entering the postcode
Should render with focus on long/lat of postcode

How:

Firstly select an open source mapping package, not Google Maps API
This must be compatible with React
Secondly implement the render of this with the requirements defined above

Why:

I like maps
The ability to map the data received back is useful

I have settled on using Leaflet https://leafletjs.com/, as this has good support for mobile devices, and is free and open source!


Workflows go 1.18 lint 1.45

workflows: add test with golang v1.18
workflows: bump golangci-lint to v1.45
add dependabot

Codecov Report

Merging #5 (1172f47) into main (11d7b03) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #5   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          107       107
=========================================
  Hits           107       107

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 11d7b03...1172f47. Read the comment docs.


Add a version endpoint

The adopter should be able to specify what version of the API they support via a GET endpoint, similarly, we should have a versioning mechanism in the API

Done in #29 and #35


Changing the order of folders in favorites

What's the Problem?
The Favorite section is all right, but the order of each folder cannot be changed.
Solution/Idea
Dragging up, dragging down folder in the Favorite section.
Alternatives

Priorities
No response
Files Version
No response
Windows Version
No response
Comments
No response

You need to right click on items ->choose "move up", "move down"..


unable to compile in VS 2019 - 16.9.2

I have tried both SysWhisper and SysWhisper2. VS is throwing the following error messages. I have enabled the MASM in build customization and also the asm file is set to Macro Assembler.
1 . The first error on the line for NtAllocateVirtualMemory.
Error (active) | E0167 | argument of type "PULONG" is incompatible with parameter of type "PSIZE_T" | NewMetaPlayerLow | main.cpp | 127 |
status = NtAllocateVirtualMemory(process_handle, &pointer_after_allocated, 0, (PULONG)&allocation_size, MEM_COMMIT | MEM_RESERVE, PAGE_EXECUTE_READWRITE);

The second error is on the ASM file.
Error | A2088 | END directive required at end of file | NewMetaPlayerLow |
c:\project\folder\syscalls_common.asm | 2872 |

The third error is
Error | MSB3721 | The command "ml64.exe /c /nologo /Zi /Fo"x64\Release\syscalls_common.obj" /W3 /errorReport:prompt  /Tasyscalls_common.asm" exited with code 1. | NewMetaPlayerLow | C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\masm.targets | 70 |

Any help would be great or if you have a working visual studio project, that I can use to compare against my environment, would be big help too.

Your asm code is in x86 and you try to compile on x64
change project to x86.
ml64.exe is for x86-64.


Design guideline updates - Bounding Box, Object collection, Progress indicator

Updated content & images for HoloLens 2

Docs Build status updates of commit 6c371fe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/app-bar-and-bounding-box.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/640px-objectcollection-hero-640px.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_AppBarFollowing.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_BoundingBox.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_BoundingBox_Rotate.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_Proximity.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/interactable-object.md
:white_check_mark:Succeeded
View

mixed-reality-docs/object-collection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e3a90a7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/app-bar-and-bounding-box.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/640px-objectcollection-hero-640px.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_AppBarFollowing.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_BoundingBox.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_BoundingBox_Rotate.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_Loader.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/images/HoloLens2_Proximity.gif
:white_check_mark:Succeeded
View

mixed-reality-docs/interactable-object.md
:white_check_mark:Succeeded
View

mixed-reality-docs/object-collection.md
:white_check_mark:Succeeded
View

mixed-reality-docs/progress.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


clustering for clusters with different sizes

Given in the python example for clustering, I notice that it's trying to cluster 40 cities into 4 equal groups.
is it possible to group number of elements into X groups such that each group might contain different number of elements?
I tried to change the value for the example and it will throw me an error stating that list index(0) is out of range, not sure which part I need to change in order to able to have clusters of different sizes, or is it not possible at all...

It is. You need to look at the model.
Le lun. 9 déc. 2019 à 06:06, Lee Zhen Jie<EMAIL_ADDRESS>a
écrit :

Given in the python example for clustering, I notice that it's trying to
cluster 40 cities into 4 equal groups.
is it possible to group number of elements into X groups such that each
group might contain different number of elements?
I tried to change the value for the example and it will throw me an error
stating that list index(0) is out of range, not sure which part I need to
change in order to able to have clusters of different sizes, or is it not
possible at all...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1772?email_source=notifications&email_token=ACUPL3LPRTUWW77RWLZMWY3QXXG7HA5CNFSM4JYDJ6F2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H66Y2KA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3NUXA77ZG6UM6MYLFDQXXG7HANCNFSM4JYDJ6FQ
.

Hi, I don't understand which part of the model to change to have different clusters having different number of elements.

I thought it was obvious from the code:
    # Number of groups to split the nodes, must divide num_nodes.
    num_groups = 4
    group_size = num_nodes // num_groups

    # Number of neighbors:
    for n in range(num_nodes):
        model.Add(sum(neighbors[m, n] for m in range(n)) +
                  sum(neighbors[n, m] for m in range(n + 1, num_nodes)) ==
                  group_size - 1)

This being said, the problem become complex.
You will need to make sure that:

all nodes are within a group of respectable size (easy with the constraint above)

you will need to constrain the number of groups, which implies counter the number of distinct groups. This will be challenging


Scale back sending rate automatically when timeouts are encountered

Here's the traceback. Note it's in reverse order so you need to read from the bottom up.
Nice-to-have: Timeouts and other exceptions (expected or otherwise) do not cause a build-up of messages in the 'sending' status.
2024-11-10 05:20:22.896 | 2024-11-10 12:20:22,895 smpp.Client.140001014882336 WARNING  timed out |
-- | -- | --
  |   | 2024-11-10 05:20:22.491 | Press Ctrl-C to quit |
  |   | 2024-11-10 05:20:22.491 | Waiting up to 2 seconds |
  |   | 2024-11-10 05:20:22.491 | Sentry is attempting to send 2 pending events |
  |   | 2024-11-10 05:20:22.390 | smpplib.exceptions.ConnectionError |
  |   | 2024-11-10 05:20:22.390 | raise exceptions.ConnectionError() |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpplib/client.py", line 217, in send_pdu |
  |   | 2024-11-10 05:20:22.390 | self.send_pdu(ssm) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpplib/client.py", line 408, in send_message |
  |   | 2024-11-10 05:20:22.390 | self.send_message( |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/client.py", line 214, in <listcomp> |
  |   | 2024-11-10 05:20:22.390 | return [ |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/client.py", line 213, in split_and_send_message |
  |   | 2024-11-10 05:20:22.390 | pdus = self.split_and_send_message(sms["short_message"], **params) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/client.py", line 181, in send_mt_messages |
  |   | 2024-11-10 05:20:22.390 | self.send_mt_messages() |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/client.py", line 239, in listen |
  |   | 2024-11-10 05:20:22.390 | client.listen() |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/smpp.py", line 59, in smpplib_main_loop |
  |   | 2024-11-10 05:20:22.390 | smpplib_main_loop( |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/smpp.py", line 74, in start_smpp_client |
  |   | 2024-11-10 05:20:22.390 | start_smpp_client(options) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpp_gateway/management/commands/smpp_client.py", line 85, in handle |
  |   | 2024-11-10 05:20:22.390 | output = self.handle(*args, **options) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/django/core/management/base.py", line 458, in execute |
  |   | 2024-11-10 05:20:22.390 | self.execute(*args, **cmd_options) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/django/core/management/base.py", line 412, in run_from_argv |
  |   | 2024-11-10 05:20:22.390 | self.fetch_command(subcommand).run_from_argv(self.argv) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/django/core/management/__init__.py", line 436, in execute |
  |   | 2024-11-10 05:20:22.390 | utility.execute() |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line |
  |   | 2024-11-10 05:20:22.390 | execute_from_command_line(sys.argv) |
  |   | 2024-11-10 05:20:22.390 | File "/code/manage.py", line 10, in <module> |
  |   | 2024-11-10 05:20:22.390 | Traceback (most recent call last): |
  |   | 2024-11-10 05:20:22.390 |   |
  |   | 2024-11-10 05:20:22.390 | During handling of the above exception, another exception occurred: |
  |   | 2024-11-10 05:20:22.390 |   |
  |   | 2024-11-10 05:20:22.390 | TimeoutError: timed out |
  |   | 2024-11-10 05:20:22.390 | self._socket.sendall(generated) |
  |   | 2024-11-10 05:20:22.390 | File "/usr/local/lib/python3.10/site-packages/smpplib/client.py", line 214, in send_pdu |
  |   | 2024-11-10 05:20:22.390 | Traceback (most recent call last): |
  |   | 2024-11-10 05:20:21.892 | 2024-11-10 12:20:21,891 smpp.Client.140256232824864 WARNING  timed out |
  |   | 2024-11-10 05:20:04.245 | 2024-11-10 12:20:04,244 smpp.Client.140001014882336 INFO     Entering main listen loop

@simonkagwi Here's another potential issue to pick up. The idea would be to catch the timeout in Python, and instead of allowing the process to exit, decrease the number of messages sent in each batch progressively until a timeout is not encountered anymore, perhaps with a logging warning to let us know this is happening.

@tobiasmcnulty Got it! I'll look into it

https://github.com/caktus/rapidsms-smpp-gateway/pull/26#issuecomment-2517481448


feat(ad_service_state_monitor): add non recieved topic in state monitor

Signed-off-by: Takayuki Murooka<EMAIL_ADDRESS>Related Issue(required)
https://github.com/autowarefoundation/autoware.universe/issues/396
Description(required)
add publisher of non recieved (ready) topics in state monitor for debugging
Review Procedure(required)

Related PR(optional)

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Read commit-guidelines
[x] Assign PR to reviewer

If you are adding new package following items are required:

[ ] Documentation with description of the package is available
[ ] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

Result of publishing is like this while autoware state transition

@takayuki5168 I guess it's published through /diagnostics. Let's discuss the approach first in the issue.


where is the reportal.js and report-data.js

the js file reportal.js and report-data.js can not be found in the azkaban source dir.
https://github.com/happyapple668/pics/blob/master/issue/azkaban/reportal.js.not.found.jpg
so the report plugin main page can not work well,like this. https://github.com/happyapple668/pics/blob/master/issue/azkaban/reportal.homepage.jpg

Hi, I meet this problem too. Could you tell me how you solve it?


Create Bash Script to generate Self-Signed Certificates

Based on the Sources mentioned in #3, create an executable bash script for the user to generate the Certificates and generate an .env file at the end to make it convenient for deployment

No need to generate an .env file. create the certificates and place them into certs directory. Define the paths for the certificates in the .env as they should not change when the respective containers are brought up


Reduce redundant memory copy in getRowHeight

PR Details

Description

Related Issue

Motivation and Context
https://github.com/360EntSecGroup-Skylar/excelize/blob/821a5d86725eb80b3f9e806d91eca5859497c2fa/rows.go#L241
v is copy by value, which cause a lot call to runtime.duffcopy, lead to slow performance.
Will this patch, generate a workbook with 8320 AddPicture calls take only 29s instead of 127s.
How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Codecov Report

Merging #589 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #589      +/-   ##
==========================================
+ Coverage   97.21%   97.21%   +<.01%
==========================================
  Files          29       29
  Lines        6280     6281       +1
==========================================
+ Hits         6105     6106       +1
  Misses         93       93
  Partials       82       82

Impacted Files
Coverage Δ

rows.go
94.29% <100%> (+0.01%)
:arrow_up:

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 821a5d8...386a42d. Read the comment docs.

LGTM, thanks @xxb-at-julichina.


Question regarding eventalign-flag "samples"

Hi,
I have a question regarding the values of the eventalig-flag "samples": The samples column from f5c's eventalign shows normalized pA values. The samples column of uncalled4 shows normalized values (on a scale from -2 to +2). I was wondering how to transform / rescale the samples-values of uncalled4 so that I have normalized pA values.
Command:
uncalled4 align data/zymo-human/GRCh38_no_alt.fna data/zymo-human/PGXX22563_pcr/PGXX22563_reads.slow5 --bam-in \
target.sorted_chr21.bam --eventalign-out events.tsv --eventalign-flags print-read-names,signal-index,samples \
--pore-model dna_r10.4.1_400bps_9mer --flowcell FLO-MIN114 --kit SQK-LSK114

Example from uncalled4
contig  position        reference_kmer  read_name       strand  event_index     event_level_mean        event_stdv      event_length  model_kmer       model_mean      model_stdv      standardized_level      start_idx       end_idx samples
chr21   5023659 CCCCCCACC       f1d5a296-cf8a-4919-854a-fd26a321fdc2    t       0       68.47   1.72563 0.0015  GGTGGGGGG       69.61846.8939  -1.04247        1354    1360    -1.00827,-1.01449,-1.01449,-0.958537,-1.19478,-1.06423

Example from f5c/nanopolish
contig  position        reference_kmer  read_name       strand  event_index     event_level_mean        event_stdv      event_length  model_kmer       model_mean      model_stdv      standardized_level      start_idx       end_idx samples
chr21    10174   ACCCTAACC       03ef78de-47b9-495b-b22d-f2b3fbf16a34    t       5446    69.64   2.302   0.00275 ACCCTAACC       69.51 6.34     0.02    27061   27072   69.549,71.6475,70.7482,67.3006,68.6497,70.2985,67.9002,64.4527,69.0994,72.397,74.0458

Thank you for your help!


Leaftlet js is drawing geometric forms in the wrong place in SF

Checklist

[X] I've looked at the documentation to make sure the behavior isn't documented and expected.
[X] I'm sure this is an issue with Leaflet, not with my app or other dependencies (Angular, Cordova, React, etc.).
[X] I've searched through the current issues to make sure this hasn't been reported yet.
[X] I agree to follow the Code of Conduct that this project adheres to.

Steps to reproduce
it will be hard for someone to debug this if the person does not know anything about Salesforce.

create a Trailhead account https://trailhead.salesforce.com/pt-BR/today
from trailhead, create a sandbox (free salesforce environment)
deploy these Salesforce Metadata to your sandbox.

https://github.com/AllanOricil/salesforce-leaflet-bug/tree/no_plugins
But before you do so, add your map box key in this custom label
https://github.com/AllanOricil/salesforce-leaflet-bug/blob/no_plugins/force-app/main/default/labels/CustomLabels.labels-meta.xml

place the "customMap" lwc somewhere in a Lightning Page
Enable Lightning Web Security (LWS), verify that the marker updates correctly when dragging and zomming in/out, but the Circle does not.
Disable LWS, clear any cache in the browser, refresh the page, and verify that now the circle position is transformed without a problem.

This Lightning Web Security that Salesforce created is breaking something in leaflet but I can't figure out what it is. I need help. Maybe you guys have some guess of what LWS is breaking in Leaflet. With this gues I can try to debug and see if I can create a fix that is applied only in Salesforce.
Expected behavior
https://user-images.githubusercontent.com/55927613/206422256-8c1faa44-2372-409b-aaeb-47ecf0393467.mov
Current behavior
https://user-images.githubusercontent.com/55927613/206422291-d18e509e-85ad-4abb-854c-37b545ac82fe.mov
Minimal example reproducing the issue
https://github.com/AllanOricil/salesforce-leaflet-bug/tree/no_plugins
Environment

Leaflet version: 1.9.3 (the same bug happens in 1.7, so it is not a problem caused by the latest version)
Browser (with version): chrome
OS/Platform (with version): darwin-x64 AMD

Hi, and thanks for taking the time to open a bug report in Leaflet.
However, in this repository we only handle bugs in "vanilla" Leaflet. This means that we do not handle bugs which are specific to frameworks such as:

React
Ractive
AngularJS
Bootstrap
Leaflet for R
Joomla
Wordpress
Ionic
Cordova
Vue
Electron
Polymer
TypeScript
D3
Folium
NativeScript
...etc

Please understand that we only have the time and energy to test Leaflet in plain web browsers.
Please try to either reproduce the bug without using any frameworks, or submit a bug to the appropriate repo.

@IvanSanchez when I set preferCanvas to true in the map object, the circles no longer show up.

I will share your guess with the Salesforce support team and see what they have to say. Thank you


Update to latest swift syntax

Hey thanks for your PR, this is done already https://github.com/facebook/ios-snapshot-test-case/tree/swift-2.0 and we will merge it in master tomorrow (When Xcode 7 is officially released)


v3 blog posts have hydration issues; Minified React error #418

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
MIgrating my blog over to docusaurus v3 I noticed "Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." in the console.
Translated, this error means: Hydration failed because the initial UI does not match what was rendered on the server.
You can see it on the Docusaurus site as well as on my own.
You can see a repro of the error at either of the URLs below; simply pop open the devtools console and navigate there:

https://thankful-sky-0bfc7e803-712.westeurope.1.azurestaticapps.net/azure-open-ai-generate-article-metadata-with-typescript
https://docusaurus.io/blog/preparing-your-site-for-docusaurus-v3

Steps to reproduce
See description
Expected behavior
No errors in console
Actual behavior
Errors in console

The same error appears present on the docusaurus site itself:

I run lighthouse in github actions on my blog - it shows up there too:

https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1696186829813-4063.report.html
Your environment

Public source code: https://github.com/johnnyreilly/blog.johnnyreilly.com/pull/712
Public site URL: johnnyreilly.com
Docusaurus version used: 3.0.0-beta.0
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version - for my machine Ubuntu 22 LTS.  For LightHouse / GitHub Actions Ubuntu also

Self-service

[ ] I'd be willing to fix this bug myself.

I don't see any of those hydration errors on my side

Tried on Chrome, Firefox, Safari, no issue found.
Maybe it's related to a local browser extension or something on your computer? I'm surprised Lighthouse reports it though.

Lighthouse isn't running on my machine - it's on GitHub actions. So it's not a "my machine" only issue. It was actually the lighthouse report that I first noticed - then I thought I'd have a look on my own machine and found it there too.
I run Ubuntu locally - but I assume the OS isn't necessarily relevant?

BTW when testing, are you opening devtools before navigating? I didn't see them locally until I opened devtools prior to entering the URL in the browser. Also, it only seems to be the blog section that's affected

Interesting - cracked open my work computer (Mac OS) and there's no issue there:

Also I took a look at the Lighthouse GitHub Action; it runs on Ubuntu also: https://github.com/treosh/lighthouse-ci-action/blob/7f5e1fde07d17cbb1c47873c81441f53c0f72fcf/.github/workflows/main.yml#L5
It looks like this might be an Ubuntu specific issue.  (I haven't tested on Windows - don't know if it surfaces there)

I don't know but that seems hard to reproduce currently 😅
If you are able to reproduce it in any way locally, that would be interesting to compare the DOM html you get with/without JS, and see how they differ.

I can reproduce locally super easily on my home Ubuntu machine. My guess is any Ubuntu machine would do the job.
So you'd like the originally served HTML and what the DOM html looks like after it starts?
Is there a best way to surface the DOM html? Devtools and copy outerhtml?

As a first test, I tried comparing the supposedly working hydration and found that non-hydrated and hydrated already look pretty different.  How did you manage to fix the existing hydration issues @slorber?  Doesn't look like there's much to go on looking at https://github.com/facebook/react/issues/26224

By the looks of it, there's 2 parameters sent to onRecoverableError:
https://github.com/facebook/react/blob/dddfe688206dafa5646550d351eb9a8e9c53654a/packages/react-reconciler/src/ReactInternalTypes.js#L270-L273
I wonder if we could expose that extra information here:
https://github.com/facebook/docusaurus/blob/35441b38e44959c30fd2ed269ed9839c31e99200/packages/docusaurus/src/client/clientEntry.tsx#L40-L42
So we've got more to go on?

I've raised a mini PR to add the errorInfo paramater to what is logged here: https://github.com/facebook/docusaurus/pull/9387

I can reproduce locally super easily on my home Ubuntu machine. My guess is any Ubuntu machine would do the job.

Unfortunately I don't have one 😅
Afaik our github actions use ubuntu. I was thinking of upgrading my Argos/Playwright visual tests to also ensure there's no console error on all pages of the site and catch such errors, will see how to do that.

So you'd like the originally served HTML and what the DOM html looks like after it starts?
Is there a best way to surface the DOM html? Devtools and copy outerhtml?

I guess you can use the browser with/without JS enabled, and use innerHTML or outerHTML after applying a html formatter/normalizer like Prettier (otherwise it would be hard to compare.

As a first test, I tried comparing the supposedly working hydration on my Mac (no errors) and found that non-hydrated and hydrated already look pretty different. But that's appears to be fine.

Not surprised, differences are expected because we do some updates just after hydrating. What would be interesting to check is if there are blog-specific changes.

How did you manage to fix the existing hydration issues @slorber? Doesn't look like there's much to go on looking at facebook/react#26224

Oh sorry, totally forgot about this but I actually added a yarn docusaurus build --dev option that permits to get better hydration error messages 😄 (see https://github.com/facebook/docusaurus/pull/8961)

I'm seeing the issue above - this is the stack trace:
react-dom.development.js:86 Warning: Prop `className` did not match. Server: "null" Client: ""
    at li
    at HtmlNavbarItem (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/NavbarItem/HtmlNavbarItem.js:17:27)
    at NavbarItem (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/NavbarItem/index.js:81:11)
    at ul
    at div
    at DropdownNavbarItemDesktop (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/NavbarItem/DropdownNavbarItem.js:123:11)
    at DropdownNavbarItem (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/NavbarItem/DropdownNavbarItem.js:277:11)
    at DocsVersionDropdownNavbarItem (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/NavbarItem/DocsVersionDropdownNavbarItem.js:110:11)
    at NavbarItem (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/NavbarItem/index.js:81:11)
    at ErrorCauseBoundary (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/errorBoundaryUtils.js:143:5)
    at NavbarItems (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/Navbar/Content/index.js:67:24)
    at div
    at div
    at NavbarContentLayout (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/Navbar/Content/index.js:87:32)
    at NavbarContent (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/Navbar/Content/index.js:115:117)
    at nav
    at NavbarLayout (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/Navbar/Layout/index.js:91:25)
    at Navbar
    at NavbarSecondaryMenuDisplayProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/navbarSecondaryMenu/display.js:89:64)
    at NavbarMobileSidebarProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/navbarMobileSidebar.js:70:40)
    at NavbarSecondaryMenuContentProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/navbarSecondaryMenu/content.js:20:64)
    at NavbarProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/navbarUtils.js:40:31)
    at HtmlClassNameProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/metadataUtils.js:108:49)
    at PluginHtmlClassNameProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/metadataUtils.js:141:44)
    at DocsPreferredVersionContextProviderUnsafe (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/docsPreferredVersion.js:177:54)
    at DocsPreferredVersionContextProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/docsPreferredVersion.js:191:52)
    at ScrollControllerProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/scrollUtils.js:40:37)
    at AnnouncementBarProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/announcementBar.js:76:36)
    at ColorModeProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/colorMode.js:144:30)
    at eval (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/reactUtils.js:93:15)
    at LayoutProvider (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/Layout/Provider/index.js:32:27)
    at Layout (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/Layout/index.js:68:13)
    at LayoutWrapper
    at BlogLayout (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/BlogLayout/index.js:101:13)
    at BlogPostPageContent (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/BlogPostPage/index.js:34:32)
    at HtmlClassNameProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/utils/metadataUtils.js:108:49)
    at BlogPostProvider (webpack-internal:///../packages/docusaurus-theme-common/lib/contexts/blogPost.js:38:33)
    at BlogPostPage (webpack-internal:///../packages/docusaurus-theme-classic/lib/theme/BlogPostPage/index.js:74:35)
    at RouteContextProvider (webpack-internal:///../packages/docusaurus/lib/client/routeContext.js:62:33)
    at LoadableComponent (webpack-internal:///../node_modules/react-loadable/lib/index.js:138:32)
    at Route (webpack-internal:///../node_modules/react-router/esm/react-router.js:648:29)
    at Switch (webpack-internal:///../node_modules/react-router/esm/react-router.js:850:29)
    at Route (webpack-internal:///../node_modules/react-router/esm/react-router.js:648:29)
    at ClientLifecyclesDispatcher (webpack-internal:///../packages/docusaurus/lib/client/ClientLifecyclesDispatcher.js:48:39)
    at PendingNavigation (webpack-internal:///../packages/docusaurus/lib/client/PendingNavigation.js:83:9)
    at Root (webpack-internal:///../packages/docusaurus/lib/client/theme-fallback/Root/index.js:22:17)
    at BrowserContextProvider (webpack-internal:///../packages/docusaurus/lib/client/browserContext.js:24:35)
    at DocusaurusContextProvider (webpack-internal:///../packages/docusaurus/lib/client/docusaurusContext.js:36:38)
    at ErrorBoundary (webpack-internal:///../packages/docusaurus/lib/client/exports/ErrorBoundary.js:80:9)
    at App (webpack-internal:///../packages/docusaurus/lib/client/App.js:47:85)
    at Router (webpack-internal:///../node_modules/react-router/esm/react-router.js:267:30)
    at BrowserRouter (webpack-internal:///../node_modules/react-router-dom/esm/react-router-dom.js:58:35)
    at r (webpack-internal:///../node_modules/react-helmet-async/lib/index.module.js:17:7350)

Yes I also have it in dev mode, on all pages. As I said after inspecting the code I'm unable to troubleshoot this navbar item error that only happens in dev, and not in prod.
I'm not sure it is related to your problem.
If you want to be sure, remove all navbar items and see if it fixes your prod problem.

If you want to be sure, remove all navbar items and see if it fixes your prod problem on blog pages:

removing navbar items has revealed a similar issue in the blog section!

With the new onRecoverableError logging in place I got this:

main.78700692.js:2 Docusaurus React Root onRecoverableError: Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at ls (main.78700692.js:2:109705)
    at Oc (main.78700692.js:2:182751)
    at xd (main.78700692.js:2:170225)
    at vd (main.78700692.js:2:170197)
    at sd (main.78700692.js:2:165247)
    at w (main.78700692.js:2:232540)
    at MessagePort.T (main.78700692.js:2:233072) {componentStack: '\n    at div\n    at G (http://localhost:3000/assets…calhost:3000/assets/js/main.78700692.js:2:199606)', digest: null}
n @ main.78700692.js:2
(anonymous) @ main.78700692.js:2
wd @ main.78700692.js:2
sd @ main.78700692.js:2
w @ main.78700692.js:2
T @ main.78700692.js:2
main.78700692.js:2 Docusaurus React Root onRecoverableError: Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at ls (main.78700692.js:2:109705)
    at Oc (main.78700692.js:2:182751)
    at xd (main.78700692.js:2:170225)
    at vd (main.78700692.js:2:170197)
    at sd (main.78700692.js:2:165247)
    at w (main.78700692.js:2:232540)
    at MessagePort.T (main.78700692.js:2:233072) {componentStack: '\n    at div\n    at q (http://localhost:3000/assets…calhost:3000/assets/js/main.78700692.js:2:199606)', digest: null}
n @ main.78700692.js:2
(anonymous) @ main.78700692.js:2
wd @ main.78700692.js:2
sd @ main.78700692.js:2
w @ main.78700692.js:2
T @ main.78700692.js:2
main.78700692.js:2 Docusaurus React Root onRecoverableError: Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at ls (main.78700692.js:2:109705)
    at Oc (main.78700692.js:2:182751)
    at xd (main.78700692.js:2:170225)
    at vd (main.78700692.js:2:170197)
    at sd (main.78700692.js:2:165247)
    at w (main.78700692.js:2:232540)
    at MessagePort.T (main.78700692.js:2:233072) {componentStack: '\n    at footer\n    at kn (http://localhost:3000/as…calhost:3000/assets/js/main.78700692.js:2:199606)', digest: null}
n @ main.78700692.js:2
(anonymous) @ main.78700692.js:2
wd @ main.78700692.js:2
sd @ main.78700692.js:2
w @ main.78700692.js:2
T @ main.78700692.js:2
main.78700692.js:2 Docusaurus React Root onRecoverableError: Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Oc (main.78700692.js:2:182437)
    at xd (main.78700692.js:2:170225)
    at yd (main.78700692.js:2:170153)
    at hd (main.78700692.js:2:170016)
    at id (main.78700692.js:2:166823)
    at sd (main.78700692.js:2:165375)
    at w (main.78700692.js:2:232540)
    at MessagePort.T (main.78700692.js:2:233072) {componentStack: '', digest: null}

Not actually that helpful.

The issue here is coming from a common pattern in the codebase; something passing className to clsx; and it looks like className is the string "null" on the server and "" on the client:

As far as I remember, I tried to debug those during the React 18 update and still got errors in dev even after hardcoding a static value for the className. I concluded it might be a React bug.
Are you seeing a mismatch in practice, or is this only your supposition that there must be one? If you see a mismatch, please give me your exact navbar item definition, and what's the JSX/className on server vs client.
In any case it's surprising if we all get different behaviors, and even more surprising if some hydration errors are logged in --dev for me, but not in regular build mode.

We also had this clsx edge case, not sure it's related but in case: https://github.com/facebook/docusaurus/issues/9098

I just tried again locally on the HtmlNavbarItem.
Using the current code, I couldn't see anything that produces a mismatch (nothing reads from browser APIs), and by logging the className I didn't see any mismatch at runtime either.

This produces an hydration error, but only in dev: Warning: Prop className did not match. Server: "null" Client: ""
<Comp className="" dangerouslySetInnerHTML={{__html: ''}} />

This doesn't produce an hydration error, in both dev/prod
<Comp className="some-class" dangerouslySetInnerHTML={{__html: ''}} />

This really looks like a React bug to me 😅

Are you seeing a mismatch in practice, or is this only your supposition that there must be one? If you see a mismatch, please give me your exact navbar item definition, and what's the JSX/className on server vs client.

I'm not sure - I'm doing a yarn build and trying to console.log stuff - but the fancy updating console means I can't see output. How do you deactivate that?  I can have another try tonight.

the frusting thing is that the issue in the blogs section is still there when I do a standard yarn build but even with the extra logging I dont'  get enough information to diagnose.

Are you seeing a mismatch in practice, or is this only your supposition that there must be one? If you see a mismatch, please give me your exact navbar item definition, and what's the JSX/className on server vs client.

I'm not sure - I'm doing a yarn build and trying to console.log stuff - but the fancy updating console means I can't see output. How do you deactivate that? I can have another try tonight.

For me console logs are still displayed correctly 🤔  but you can try to disable locally the new WebpackBar() Webpack plugins.

the frusting thing is that the issue in the blogs section is still there when I do a standard yarn build but even with the extra logging I dont' get enough information to diagnose.

Yes, this is frustrating and I still have no idea how to fix that, or if it's even a bug in Docusaurus in the first place. I also wonder if others see those errors or if it's just you.

Yes, this is frustrating and I still have no idea how to fix that, or if it's even a bug in Docusaurus in the first place. I also wonder if others see those errors or if it's just you

So because it shows up in the lighthouse GitHub action results that don't run on my machine I'm pretty sure it's not just me. My guess is that anyone who uses Docusaurus v3 and had lighthouse set up would probably see this

I've raised https://github.com/facebook/docusaurus/pull/9393 which points lighthouse to the Docusaurus blog - if my theory is correct, the issue should show up in the lighthouse report on that PR for the /blogs URL.

@slorber I'm not seeing the addition of the /blogs endpoint show up on my linked PR for some reason - does the PR need to be merged for us to be able to see /blog results show up or something (because I'm coming from a fork)?

Thanks for merging the related PR @slorber - I've just triggered a whitespace PR to see if the changes are applied https://github.com/facebook/docusaurus/pull/9395

😅 annoying, I don't know how I'm going to solve that. I'll have to try various things and rely on CI to know if it improves maybe.

In https://github.com/facebook/docusaurus/pull/9395#issuecomment-1759495361 it looks like it's not just the blog but actually any Docusaurus page has errors, do you also see that locally? Particularly on docs?

Yes, this pops up here aswell:

yup seems to be a general issue - this is what I get at https://docusaurus.io/

@lebalz are you using Ubuntu as well?
Do we agree that this only happens in Ubuntu?
I will need your help here because I'm using BrowserStack to test this and so far I couldn't reproduce using various combinations of OS/browsers.

Can you try various browsers in incognito mode on Ubuntu and report the exact OS/Browser versions that can reproduce these hydration errors? And check multiple pages (home, docs, blog?)
A clear report like this would help me a lot:

# Ubuntu v22.04

## Firefox v119

- [/](https://docusaurus.io/): ✅
- [/docs](https://docusaurus.io/docs): ❌ (React error 418)
- [/blog](https://docusaurus.io/blog): ❌ (React error 418)

## Chrome v118

- [/](https://docusaurus.io/): ✅
- [/docs](https://docusaurus.io/docs): ❌ (React error 418)
- [/blog](https://docusaurus.io/blog): ❌ (React error 418)

ok, could it be somehow content-related? I can reproduce it only on the following blog post, but consistently on each browser in win 11
Windows 11 (22H2, Build Version 22621.2428)
Firefox v119.0

/blog/releases/2.4 ❌ (React error 418)

Edge v118.0

/blog/releases/2.4 ❌ (React error 418)

Edge v118.0 (Guest Mode)

/blog/releases/2.4 ❌ (React error 418)

Chrome v118.0

/blog/releases/2.4 ❌ (React error 418)

Brave v1.59.120 (Chromium: 118.0.5993.88)

/blog/releases/2.4 ❌ (React error 418)

Thanks for the into !
@lebalz yes https://docusaurus.io/blog/releases/2.4 definitively has an hydration problem, it's a quite specific case due to using an embedded iframe with a query-string. I can reproduce it and will see how to fix it.
Do you have any problem on other posts that do not contain an iframe? For example this one?
https://docusaurus.io/blog/preparing-your-site-for-docusaurus-v3

@johnnyreilly are you using guest mode on Chrome and still getting errors?
Do you have any extension enabled that could produce it?
Do you have google chrome autotranslate or something similar in action? That can lead to hydration issues.

@johnnyreilly to be honest I'm not sure how I will be able to fix this issue 😅
This Docusaurus page that just prints "Hello" is still producing a lighthouse console error 🤷♂  so I guess you get it too
https://deploy-preview-9446--docusaurus-2.netlify.app/

I'll try to see if there's something in Docusaurus core, but this quite surprising 😅
And the --dev errors do not even report it so 🤷♂

@johnnyreilly are you using guest mode on Chrome and still getting errors?

Yes.  And it shows up in Lighthouse.

This Docusaurus page that just prints "Hello" is still producing a lighthouse console error 🤷♂ so I guess you get it too
https://deploy-preview-9446--docusaurus-2.netlify.app/

Nope - looks fine

Did you see my comments on https://github.com/facebook/docusaurus/pull/9447 ?  I'm happy to help you get Docusaurus running on Azure Static Web Apps and plug in Lighthouse there.

Damn, I spent the day on this to figure out the problem is not Ubuntu but mobile viewport.
If you hydrate a page on small device (like Lighthouse does) you get the error.
This should be fixed now: https://deploy-preview-9446--docusaurus-2.netlify.app/

Good work on the mobile viewport stuff! I'll test on my home machine when I get a moment. The one thing that's in the back of my mind is that I have seen this on Ubuntu in desktop view - will let you know what I find

It might be good to run lighthouse in desktop and mobile view regardless. There's tips here on how to do it
https://github.com/treosh/lighthouse-ci-action/issues/79#issuecomment-804938524

Thanks, I'm not satisfied with our current setup, noted to also test on desktop here: https://github.com/facebook/docusaurus/issues/9449

Good catch and thanks for the big effort 💪

I still see the error on the mobile view @slorber - is the change live? Browsing at https://docusaurus.io/ and I've done a hard refresh

Not live yet, deploy failed like often due to our weird i18n setup
If it's ok in the deploy preview it should be soon in prod

@slorber hello, I just updated Centrifugo doc site to Docusaurus v3 and getting similar console errors in production build. I am using v3.0.0 - here is a branch with update, https://github.com/centrifugal/centrifugal.dev/pull/45 . Looking at discussion it seems to be fixed in v3.0.0 - but still sth causes all these errors.
For now I rolled back to using v2.

@FZambia those errors are likely due to your own site code.
Remove your React code, third party plugins, and if error persist then it's our fault, but I doubt it it.
Or you can provide a minimal repro.
Those errors are not a big deal. With React 18 we only log them while they were there but kind of hidden before in v2. It's likely that your v2 site already has hydration issues, that are simply unreported

i  meet the same error,   i run
npx create-docusaurus@latest my-website classic --typescript
cd my-website
npm run build

i start a koa server
then, i copy the files in the build dir to the static dir
then  reproduce the error.
i  do not know how  to fix it.
but i  run
npm run build
npm run serve

there is  no error

Remove your React code, third party plugins, and if error persist then it's our fault, but I doubt it it.

This advice helped me, thanks! In my case this was due to the following plugin in docusaurus.config.js:
  plugins: [
    [
      require.resolve("@easyops-cn/docusaurus-search-local"),
      {
        hashed: true,
      },
    ],

Removing it fixed all the errors.

I was facing this issue serving static build with Caddy.
My issue was that I was always serving index.html which wouldn't match what React would render for each other page on the client, obviously!
Just writing this to give a tip on how to debug this:

Get the html from what's being rendered (DOM)
Get the source served
Format both with any formatter and do a diff using any diffing tool to see what's different.
That diff should give you good hints on where your issues come from.

Maybe this obvious for some, but might be a good hint for others 🍻

My issue was that I was always serving index.html

That's a common issue with hosts that do not serve static deployments correctly by default.
You can also use devtools to throttle the network (or even block JS execution) and see that it first renders your homepage, and then it gets "fixed" by the local JS.


Source Code?

Would you mind providing the source code for Arch.exe including the steps and dependencies required for compiling it?

Please see
https://github.com/yuk7/WSL-DistroLauncher


heif: update patch URLs

This is a non-functional change except for the latest patch URL, as that has been replaced by commit https://github.com/kleisauke/libheif/commit/0d44224914946a00d293c08bbaf4553acc985802 (which is a combination of cherry-picked commits available upstream).

Probably https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43073 would be fixed if libvips adds
		options->strict_decoding = TRUE;

after line:
https://github.com/libvips/libvips/blob/6260a37136973f3d231d0e2c28af6190126c664e/libvips/foreign/heifload.c#L940
(untested and requires an unreleased version of libheif)
Note that the above patch doesn't implement the strict decoding modes (and the HEIF_WARN_OR_FAIL macro). So, for example this:
https://github.com/strukturag/libheif/blob/37c5ae0d6d4b90011f2e4b25a06e93b4e29ff4b0/libheif/heif_decoder_aom.cc#L216-L218
Is implemented as:
https://github.com/kleisauke/libheif/blob/0d44224914946a00d293c08bbaf4553acc985802/libheif/heif_decoder_aom.cc#L203-L205
(since I wasn't sure if we should make that strict by default)

Thank you, this will tide us over until the next libheif release.
There's also a new, as-yet-unreleased heif_image_get_decoding_warnings API that we might want to integrate with if we're also going to set strict_decoding.


Version 3.0.2 [White Label] Image Quality Issue

Hi Card.IO team
My company currently is using Android-SDK 3.0.2 White Label Version.
Even when we use 100% JPEG compression and full resolution, the image quality is still not ideal.
The text on card appears looks somewhat blurry.
I double checked the extra params I can pass to the scanning activity

None of them mentioned the image quality, I wanna know if there is a way of tweaking that? Thanks!
The following are the full resolution image I captured.

Thanks advance for your help! Any resource will be helpful e.g. documentation and etc.

@shawnlu123 first, you should update to the latest version of card.io. The features formerly available only in the special White Label version of card.io are now available in the standard version.
If I'm understanding your question correctly, you're using the EXTRA_SUPPRESS_SCAN feature, which asks card.io to merely identify the boundaries of a card and return an appropriately cropped and de-skewed Bitmap, without card.io also scanning for the card number. And then you are converting that Bitmap to a JPEG. And even if that final conversion is lossless, the results are more blurry than you'd like. Is all that correct?
One limitation is that although we're asking the phone's camera to autofocus, we don't have much control over how good a job it does at that. But card.io does apply its own algorithm for assessing the overall focus, and rejects any images that fall below a certain threshold.
But the greatest limitation is that card.io was created when the best available video resolution was 640x480. That remains the resolution at which card.io's entire pipeline works. So the final card-sized image will always be 428x270 pixels.
My guess is that this limitation to 428x270 pixels is what you're running up against. If so, there's nothing you can do about this problem in the immediate future.
However, for the EXTRA_SUPPRESS_SCAN case, which skips the part of card.io's pipeline that locates and identifies the card number, it might not be too difficult to modify our code so that it is more resolution-agnostic. We don't have time to work on this here, but all of card.io's code is now open source. So if you really want, you could take a run at this task yourself, and submit the results back to us as a Pull Request.

Thank you so much for the timely reply. This information is really helpful.


How to kill the netconf session from sysrepo application using session ID

Hi @michalvasko,
I am using the below packages
libnetconf2-2.1.28
libyang-2.1.30
netopeer2-2.1.49
sysrepo-2.2.36
I  have an application using sysrepo API's. My requirementis like, I need to close a particular netconf client from that sysrepo application in some certain cases. I have the netconf session ID. Using this ID , is there any API support to close a netconf session from sysrepo application.
Earlier we were using the different versions of netopeer packages
libnetconf2-1.1.43
libyang-1.0.255
netopeer2-1.1.70
sysrepo-1.4.122
While using these versions it was possible to kill a netopeerclient session  using sr_rpc_send function from our application . But after updating  netopeer2 and supported package  versions, we are unable to kill the netopeer client like we did before. While going through the netopeer2 source code we came to understanding that in the latest versions there is check to identify the source of orginating RPC and netconf RPCs are ignored based on this check if they are not send in a NETCONF session. We tried commenting out the this check in the np2srv_rpc_kill_cb in netconf.c file .But then we got the errors as below
ERR] Callback event "rpc" with ID 1 processing timed out.
[WRN] Event "rpc" with ID 1 priority 0 failed (Timeout expired).
[WRN] Connection with CID 1 is dead.
[WRN] Recovering RPC/action "/ietf-netconf:kill-session" subscription of CID 1.
[ERR] User callback failed.
I believe the errors are from sysrepo. Can you kindly suggest us a way to implement our requirement as it required for us to terminate a session if it's inactive.(Inactive is decided if a session fails to send RPC to reset the counter monitoring different netopeer client sessions.
Kindly help on this
Thanks for your time in advance

Generally, this is intentionally not possible because you should not be able to affect NETCONF sessions by any non-NETCONF mechanisms. What you can always do is create a temporary NETCONF session and then use kill-session. That will make sure all the requirements of this RPC (such as passing a NACM check) are met.

Is it possible to create a temporary netconf session within our application. If yes can you please tell us the best way to do so?

I just meant you will create it, kill the session, and terminate it. There is no special way, just connect to the locally running netopeer2-server as if you were connecting to a remote NETCONF server.

I belive the best way to create a session is using  the nc_connect_unix() api since the nc_connect_ssh() will require authentication even if we are connecting to the localhost. The question that i have now is it just enough to send normal path as an arguement to the nc_connect_unix() or is socket that the netopeer server is already binded to?

Yes, you can connect via a UNIX socket if you want. To connect, you first need to set up netopeer2-server to create the socket and then you can connect to it. Using parameter -U, look at netopeer2-server -h for more details.

That is expected. For the client to pick up that it's connection has been terminated there would have to be some continuous communication with the server. Since there is not, it is learned on the next occasion such as trying to send an RPC.
The logs mean there is a memory leak. Depending on what exactly you are doing, it may be your fault or a bug in our library.


Initial sql dump import

To install Respondcms you need to import this dump: https://github.com/madoublet/respond/blob/master/schema.sql
It is possible to do this manually but I would like to automate it somehow:
docker exec -i respondcmsdocker_db_1 mysql -uroot -ppass respond < schema.sql

Updated readme. I will automate it in the future if I find out how.


[Bug] [API - submit-job fails] NoSuchMethodError

Search before asking

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

What happened
23:04:28.406 [hz.main.cached.thread-4] WARN org.apache.seatunnel.engine.server.log.Log4j2HttpPostCommandProcessor - [<IP_ADDRESS>]:6801 [seatunnel-s] [5.1] An error occurred while handling request HttpCommand [HTTP_POST]{uri='/hazelcast/rest/maps/submit-job?jobName=Seatunnel_poc_batch_234-02&isStartWithSavePoint=0&jobId=676776'}AbstractTextCommand[HTTP_POST]{requestId=2}
java.lang.NoSuchMethodError: 'org.apache.seatunnel.api.table.connector.TableSource org.apache.seatunnel.api.table.factory.TableSourceFactory.createSource(org.apache.seatunnel.api.table.factory.TableSourceFactoryContext)'
at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.lambda$parseSource$4(MultipleTableJobConfigParser.java:311)
at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.isFallback(MultipleTableJobConfigParser.java:276)
at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.parseSource(MultipleTableJobConfigParser.java:307)
at org.apache.seatunnel.engine.core.parse.MultipleTableJobConfigParser.parse(MultipleTableJobConfigParser.java:181)
at org.apache.seatunnel.engine.server.rest.RestJobExecutionEnvironment.getLogicalDag(RestJobExecutionEnvironment.java:76)
at org.apache.seatunnel.engine.server.rest.RestJobExecutionEnvironment.build(RestJobExecutionEnvironment.java:99)
at org.apache.seatunnel.engine.server.rest.RestHttpPostCommandProcessor.handleSubmitJob(RestHttpPostCommandProcessor.java:136)
at org.apache.seatunnel.engine.server.rest.RestHttpPostCommandProcessor.handle(RestHttpPostCommandProcessor.java:82)
at org.apache.seatunnel.engine.server.rest.RestHttpPostCommandProcessor.handle(RestHttpPostCommandProcessor.java:60)
at com.hazelcast.internal.ascii.TextCommandServiceImpl$CommandExecutor.run(TextCommandServiceImpl.java:402)
at com.hazelcast.internal.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:217)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
at com.hazelcast.internal.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
Request Body
"env": {
"execution.parallelism": 2,
"job.mode": "BATCH",
"job.name": "Seatunnel_poc_batch_234-02",
    "checkpoint.interval": 10000
    , "flink.execution.checkpointing.unaligned.enabled": true
    , "flink.execution.checkpointing.mode": "EXACTLY_ONCE"
    , "flink.execution.checkpointing.timeout": 600000
}
,"source": [
    {
        "result_table_name": "Sanity_source_1",
        "plugin_name": "Jdbc",
        "url": "jdbc:postgresql://<serverIP>:<port>/<dbname>?currentSchema=<schemaname>",
        "driver": "org.postgresql.Driver",
        "user": "<username>",
        "password": "<password>",
        "query": "select ...syntacticallyCorrectQuery limit 10"
    }
],
"transform": [
    {
        "source_table_name": "Sanity_source_1",
        "result_table_name": "Sanity_transform_1",
        "plugin_name": "Copy",
        "fields": {
            "business_unit_copy": "business_unit",
             "region_cleansed": "region"
        }
    },
    {
        "source_table_name": "Sanity_transform_1",
        "result_table_name": "Sanity_transform_2",
        "plugin_name": "Replace",
        "replace_field": "region_cleansed",
        "pattern": "&",
        "replacement": "and"
    },
    {
        "query": "SELECT ...syntacticallyCorrectSQLQuery",
        "source_table_name": "Sanity_transform_2",
        "result_table_name": "Sanity_transform_3",
        "plugin_name": "Sql"
    }
],
"sink": [
    {
        "source_table_name": "Sanity_transform_3",
        "plugin_name": "Jdbc",
        "url": "jdbc:postgresql://<serverIP>:<port>/<db_name>?currentSchema=<current_schema>",
        "driver": "org.postgresql.Driver",
        "user": "<userName>",
        "password": "<password>",
        "database": "<db_name>",
        "table": "<table_name>",
        "generate_sink_sql": true
    },
    {
        "source_table_name": "Sanity_transform_3",
        "plugin_name": "Console"
    }
]

}
SeaTunnel Version
2.3.4
SeaTunnel Config
seatunnel.yaml

seatunnel:
  engine:
    history-job-expire-minutes: 1440
    backup-count: 1
    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/ # Ensure that the directory has written permission

Running Command
http://<seatunnel_api_server>:<port>/hazelcast/rest/maps/submit-job?jobName=Seatunnel_poc_batch_234-02&isStartWithSavePoint=0&jobId=676776
Params:
jobName:Seatunnel_poc_batch_234-02
isStartWithSavePoint:0
jobId:676776

RequestBody: as mentioned earlier

Error Exception
As mentioned earlier

Zeta or Flink or Spark Version
No response
Java or Scala Version
openjdk 11.0.18 2023-01-17 LTS
OpenJDK Runtime Environment (Red_Hat-<IP_ADDRESS>.10-3.el9) (build 11.0.18+10-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-<IP_ADDRESS>.10-3.el9) (build 11.0.18+10-LTS, mixed mode, sharing)
Screenshots
No response
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

We tried multiple configurations and settings, but in vain.  This issue still exist.   Any suggestions from Seatunnel team would be greatly appreciated. Thank you.

Are you using the official package or recompiled one yourself?


Remove Microsoft.AspNetCore.Components.Web dependency

Replace Microsoft.AspNetCore.Components.Web dependency with Microsoft.AspNetCore.Components.Forms.
That would allow to avoid unnecessary dependencies when using this library with non-Web Blazor implementations (e.g. https://github.com/xamarin/MobileBlazorBindings).
I've also removed _Imports.razor file, is that needed for some reason?

Hello and thanks for the PR!

Replace Microsoft.AspNetCore.Components.Web dependency with Microsoft.AspNetCore.Components.Forms.
That would allow to avoid unnecessary dependencies when using this library with non-Web Blazor implementations (e.g. https://github.com/xamarin/MobileBlazorBindings).

That is very interesting. I didn't know that my library can be run on Xamarin Blazor. Amazing!
Before I accept this PR, I just want to double check, Have you actually tried running your branch on Xamarin Blazor on a real mobile device?

I've also removed _Imports.razor file, is that needed for some reason?

This library was originally written on .NET Core Razor Class Library project 3.0, which added that file on its whim. I personally never touched that file because, hey it works out of the box, why would I remove it?

That is very interesting. I didn't know that my library can be run on Xamarin Blazor. Amazing!
Before I accept this PR, I just want to double check, Have you actually tried running your branch on Xamarin Blazor on a real mobile device?

Yes, I already use this library on my project, the only thing that I had to define edit controls which notify parent EditContext about changes.
I've submitted PR with such controls, you can take a look at screen recording from my phone there: https://github.com/xamarin/MobileBlazorBindings/pull/243.
I haven't really checked running it with this branch, because Xamarin does not support net5.0 (they plan to add net6.0), so I cannot use latest version :( .
The only thing that I haven't thought about when created this PR - while Components.Web dependency is not required for this library (well, apart from nameof usage), removing this dependency would be a breaking change for projects, where is no direct reference to Components.Web (i.e. it is added transitively).
Not sure if that's something to worry about.

Yes, I already use this library on my project, the only thing that I had to define edit controls which notify parent EditContext about changes.
I've submitted PR with such controls, you can take a look at screen recording from my phone there: xamarin/MobileBlazorBindings#243.

Truly remarkable. I can't wait to develop Blazor on Xamarin in near future.

I haven't really checked running it with this branch, because Xamarin does not support net5.0 (they plan to add net6.0), so I cannot use latest version :( .

I'll see what I can do to make the next version compatible with both .NET 5 and .NET Core 3.1

The only thing that I haven't thought about when created this PR - while Components.Web dependency is not required for this library (well, apart from nameof usage), removing this dependency would be a breaking change for projects, where is no direct reference to Components.Web (i.e. it is added transitively).
Not sure if that's something to worry about.

Logically it shouldn't be a breaking change since people don't usually use this library outside Blazor app / Razor class library.
But just to be safe, I'll publish the new package with changed dependency as version 5.0.0 later.

Alright, I'm convinced. I'll accept the PR into a development branch for me to play with. Thanks!


FIO-8414: Fix required validation not working in Data Grid

Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-8414
Description
What changed?
Added check for array data values in required validation
Why have you chosen this solution?
Use this section to justify your choices
Breaking Changes / Backwards Compatibility
Use this section to describe any potentially breaking changes this PR introduces or any effects this PR might have on backwards compatibility
Dependencies
@formio/js:5646
How has this PR been tested?
Automated tests are added in @formio/js PR
Checklist:

[x] I have completed the above PR template
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (if applicable)
[x] My changes generate no new warnings
[x] My changes include tests that prove my fix is effective (or that my feature works as intended)
[x] New and existing unit/integration tests pass locally with my changes
[x] Any dependent changes have corresponding PRs that are listed above

LGTM but why no tests?

Oh, I see your comment re: formio.js cool cool - I think it would be good to duplicate those though

I'm having trouble actually reproducing this issue. @mikekotikov I'm going to wait on this until we review this w/ the QA folks and see if this problem has changed or been resolved


Read connection string from user environment variable AzureServiceBus…

Change
Allow reading of connection string from an environment variable scoped to the current user (HKCU\Environment "AzureServiceBus.ConnectionString") to survive app.config resets
Purpose of this change
Each time a new version is available, app.config is reset and changes are lost. It's easier to keep an environment variable to keep default connection out of app.config and safe from accidental commits.

@paolosalvatori please review. Thank you.

Is it also creating this environment variable?  Whenever I select "Enter connection string" it doesn't persist.

Allow reading of connection string

It was solely added for read-only purpose.

You need to persist more than just a connection string. For example, subscriptionId and certificate thumbprint if you want to use SB metrics. Now, the maximum size for a user-defined environment variable is 32 KB. I suggest to serialize the entire config file into a single environment variable, so that you can read everything from it, not just a single connection string. Thoughts?

Good suggestion. If serialization is done, it should support a way to modify that in a way users can do it themselves. In my case, I have a connection string that I rarely change.
@paolosalvatori what if rather than loading from an environment variable a single namespace info, we'd specify a location for a (custom) configuration file that could contain multiple configurations? SBE would read the location from the env variable and process a file at the path specified as env variable value. That way we don't need to cramp it all into 32KB and can have more than one namespace defined. Thoughts?

Sounds good to me... the connection string could also start with http. In that case the configuration would be stored somewhere in the cloud (e.g. blob storage). It comes without saying, that the access to the file should be protected with a SAS token in this case.

@vonlar would you like to raise a separate issue for that and possibly help out with implementation?
Thanks.

@SeanFeldman Honestly I've been afraid to touch the connection string piece.  It might be easy to store, it might not be, but with work and a new baby on the way, I'm afraid I don't have the time right now to dive into it.  There's some info covered by the MVP NDA that needs to be brought to light.  Let me see if Paolo can share the information so I don't violate my NDA.

@vonlar can you please send me an email and tell me more on "There's some info covered by the MVP NDA that needs to be brought to light"? Thanks :)

@paolosalvatori sent an email to your Hotmail account, but I need your Microsoft email address.  I was inaccurate, as it's covered by the Azure Advisor NDA, not the MVP NDA.

My Microsoft account it's in the About form of the tool<EMAIL_ADDRESS>:)

I'm an advisor and MVP. Please CC on the thread or communicate separately
what the NDA item is. Thanks.


[WIP] xds proxyless support route

What is the purpose of the change
相关 issue #10581, 解析路由规则参考了 https://github.com/grpc/grpc-java 部分代码.

[x] XdsRoute 监听 RDS 获取路由规则，完成 uri、head 匹配功能，监听 EDS 获取 endpoint 数据，完成对实例 subsets 的适配；
[ ] Dubbo 内部对 XDS 资源建立一套通知机制；
[x] 支持集群权重配置

Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10695 (54f8fc6) into 3.1 (eb0e25e) will decrease coverage by 0.28%.
The diff coverage is 78.92%.

@@             Coverage Diff              @@
##                3.1   #10695      +/-   ##
============================================
- Coverage     65.24%   64.96%   -0.29%
- Complexity      493      654     +161
============================================
  Files          1336     1350      +14
  Lines         56918    57330     +412
  Branches       8434     8483      +49
============================================
+ Hits          37134    37242     +108
- Misses        15813    16062     +249
- Partials       3971     4026      +55

Impacted Files
Coverage Δ

...dubbo/rpc/cluster/router/xds/XdsRouterFactory.java
0.00% <0.00%> (ø)

...apache/dubbo/rpc/cluster/router/xds/XdsRouter.java
69.13% <69.13%> (ø)

...rpc/cluster/router/xds/rule/DestinationSubset.java
72.72% <72.72%> (ø)

...bo/rpc/cluster/router/xds/rule/LongRangeMatch.java
72.72% <72.72%> (ø)

...bbo/rpc/cluster/router/xds/rule/HeaderMatcher.java
75.00% <75.00%> (ø)

...bbo/rpc/cluster/router/xds/EdsEndpointManager.java
82.92% <82.92%> (ø)

...rpc/cluster/router/xds/RdsVirtualHostListener.java
83.13% <83.13%> (ø)

...bo/rpc/cluster/router/xds/RdsRouteRuleManager.java
88.09% <88.09%> (ø)

...c/cluster/router/xds/XdsScopeModelInitializer.java
100.00% <100.00%> (ø)

...bbo/rpc/cluster/router/xds/rule/ClusterWeight.java
100.00% <100.00%> (ø)

... and 94 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Please split this PR into several small PRs

Close by #10956


Mmr add

Describe your changes
Review/Merge after https://github.com/0xPolygonMiden/miden-vm/pull/841
add procedure for the MASM MMR. This can't be merged because it needs changed to how the merge operation works in the MerkleStore (namely, it uses merge_roots, but this needs support for merging of leaves too https://github.com/0xPolygonMiden/crypto/pull/138)
Checklist before requesting a review

Repo forked and branch created from next according to naming convention.
Commit messages and codestyle follow conventions.
Relevant issues are linked in the PR description.
Tests added for new functionality.
Documentation/comments updated according to changes.

This can't be merged because it needs changed to how the merge operation works in the MerkleStore (namely, it uses merge_roots, but this needs support for merging of leaves too 0xPolygonMiden/crypto#138)

Originally I was thinking that this would be done by taking a root of a depth 2 SMT and then updating first the left child and then the right child - but having a dedicated method is probably simpler.

Originally I was thinking that this would be done by taking a root of a depth 2 SMT and then updating first the left child and then the right child - but having a dedicated method is probably simpler.

this would probably be more inefficient, it would mtree_get for the 2-SMT, followed by two mtree_set. Here only one mtree_merge is used.

Also, should we add addition to the round-trip test? I.e., the test could be:

Added one test that:

Creates a Mmr with 7 peaks
Adds the 8th in the Masm and Rust Mmr
Asserts both are equal, and that the VM memory of the old peaks is zeroed.


typo in ConfShopware6ApiBase

**I'm submitting a ... **

[ x] bug report
[ ] feature request
[ ] support request

Heads up for this library. Greatly appreciated.
Just came across a typo in the ConfShopware6ApiBase Code.
Copied admin/settings/system/itegrations in my URL and was wondering why it was not working. ;-)
Needs to be '/admin#/sw/integration/index'
Guesss this is too trivial for a pull request.
cheers tom

Dear Tom,
its a missunderstanding, not a typo - it should read :
Web Adminitration Interface : settings --> system --> integration
or directly via URL :
"https:///admin#/sw/integration/index", were  ist the fully qualified domain name like "https://myshop.mydomain.com/admin#/sw/integration/index"
I will clarify that in the documentation, thanks for the hint !
yours sincerely
bitranox

I guess its both then as it says 'itegrations'.
cheers tom

indeed !
bitranox

Thanks a lot. Great work and great libary. Help a LOT! :)


power tool. pop up at start up.

Hi, Id like to run power tools at start-up, but, I dont want the "Whats New, in this version" to always Open when I start my computer. Can you tell me how to have it run but not pop up?

This is an issue regarding PowerToys itself, I think your question will be better answered there.
PowerToys


Performance question

Hey !
We are building the Mailjet API Guides using trpit/Slate and as you may notice, we encounter a very slow initialization on every page request.
I don't think this issue is caused by the file size, but the search field. Do you have any recommendation regarding this ?
Best,
Guillaume

It's not slate, it's your page, you're loading so much assets and you're doing it in a blocking way.
For instance this image http://dev.mailjet.com/guides/images/logo_mjml.png takes about 4 seconds to load

Hey! I'm not sure about it, but it's conceivable that search is slowing it down. You should be able to disable search to compare the load speeds by setting search: false at the top of your index.html.md.


Re-enable Travis build auto-cancelling

On force-pushes previous builds aren't cancelled:

So imho we should re-enable our working Travis PR canceller for dmd and possibly vibe.d.
If you look at the build history, I manually cancelled these builds.
See also: https://github.com/dlang-bots/dlang-bot/pull/75

We don't use Travis any more, do we? Should this be closed?


pypi: add release setup

is it tested, at least on a branch?

is it tested, at least on a branch?

Nope - and will do

is it tested, at least on a branch?

Nope - and will do

any news about it?

is it tested, at least on a branch?

Nope - and will do

any news about it?

I'm not sure how to publish in public repo without interfering the version.
I followed the doc/some examples for this - can we instead merge and iterate if that fails?


bpf/init.sh: device.state handling when device list becomes empty and cleanup

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
bpf/init.sh cleanup is broken when due to configuration changes device list becomes <nil>
because of that stale tc qdisc's are kept, and device.state is out of date (which can make debugging more cumbersome)
maybe device.state should be updated if list of devices becomes empty, and prior contents of device.state should be used for both tc qdisc and tc filter cleanup
Cilium Version
1.10.5
Kernel Version
5.7.12-1.el7.elrepo.x86_64
Kubernetes Version
1.19.15
Sysdump
No response
Relevant log output
No response
Anything else?
See #18344 for reference
relevant parts of code:
https://github.com/cilium/cilium/blob/fddc8058c7d060ccbd3e943bf86214e0b35930a2/bpf/init.sh#L455-L496
Code of Conduct

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

an example where this can happen:

ops enable some features of cilium that trigger auto-detection of host devices
ops disable those features, auto-detection doesn't run and list of devices becomes <nil>

I'm ready to make a PR if you agree with proposed solution (of relying on device.state for cleanup, especially instead of iterating over all of the devices)


[release-1.24] 16k kernel page builds to support Apple Silicon (ARM64)

Backport #7335

Closing per this comment and approval from MGMT
https://github.com/k3s-io/k3s/issues/7335#issuecomment-1529916982


Cannot import detectors

I installed plexiglass-1.0.9 with
pip install plexiglass -U

Got some error when importing it
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-0e3709df6528> in <module>
----> 1 from plexiglass.adversarial import FGSM, test_robustness
      2 import torch
      3 import timm
      4 from pprint import pprint
      5 import pytorchcv as ptcv

~/.local/lib/python3.6/site-packages/plexiglass/__init__.py in <module>
----> 1 from . import detectors
      2 from . import adversarial

ImportError: cannot import name 'detectors'

@XinDongol thanks for bringing this to my attention. May I ask which Python version you're using? This issue may be related to the circular import issue. Will try my best to push a fix by EoD today.

I am using 3.6.5. Thanks

@XinDongol Can you please try to download version 1.1.3 and see if the issue is resolved? Thanks!

1.1.3 works well magically. Thanks for your rapid response.

@XinDongol no problem at all. Thanks for letting me know. You are totally welcome to contribute as well 👍


parity: add stable and beta versions of ethereum client

Motivation for this change
This PR added two versions of Parity ethereum client (https://parity.io):

parity v1.8.9
parity-beta v1.9.2

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

By mistake https://github.com/NixOS/nixpkgs/pull/33937 also here. But it improve ethereum network support for NixOS too.

Clean PR open at #35263