Feature request: Support relative paths in history.push

Hi! Do you think that would make sense to support relative paths in history.push? So we can do stuff like that:
browserHistory.push('../'); // go to parent
browserHistory.push('../sibling'); // go to sibling

You'll be happy to know that we already do support relative pathnames :)
If you're not seeing this you may be using an older version.

Looks like we are on outdated version.
We use RR 2.5.3 which uses history ^2.0.1 and there's no LocationUtils there. Looks like there's no way we can get this in v2: v2.8.2 uses history 2.1.2.
Thank you!

I have a question related to relative path
When I call browserHistory.push('posts')
path e.g. /user/1 goes to /user/posts
path /user/1/ goes to /user/1/posts
It was unexpected to me at first, but then I supposed it might be the correct behavior
Is there a config to always append a trailing slash? Or a way to go to the deeper level from the first path?
In general what would you recommend?
I'm using universal-router, and currently trailing slash doesn't matter in my routes, so /user/1 and /user/1/ resolve to the same page


Add GenAI policy

What problem does your feature request solve?

With GitHub Copilot now being available at the Met Office, we should have an explicit Generative AI policy.
Describe the solution you'd like

The official guidance is on SharePoint, and the main new thing is that we should have an attribution in the README. I think we should go a bit further and to per-PR attributions, so as to allow keeping track of what code contains AI generated content. We should probably also record the model used, as this would be relevant for any IP issues that arise.
Describe alternatives you've considered

We could ban GenAI entirely. That would avoid any potential issues with AI generate code, but we would also miss out on any benefits. As the wider corporate strategy at the Met Office seems to be embracing AI, we should probably follow. Also, if AI is banned, it may be used clandestinely, which would make it impossible to track.
I personally have minimal experience with Generative AI development tools currently, so I am not well placed to comment on their effectiveness. We may find that because we attract a particular kind of contribute audience we are less affected by many of the issues affecting the wider open source ecosystem.

A


tried to register two views with the same name rndatetimepicker

Environment

System:
OS: macOS 10.15.7
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 117.45 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.6.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.1, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 12.1/12A7403 - /usr/bin/xcodebuild
Languages:
Java: 14.0.2 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-40.0.1.tar.gz => 0.63.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Platforms

Both iOS and Android
Versions

Android:
iOS: 12
react-native-modal-datetime-picker:
react-native-community/datetimepicker:
react-native: 0.63.2
react: 16.13.1

Description

I get this error
"tried to register two views with the same name rndatetimepicker"
I swap react-native-datetime-picker with react-native-community/datetimepicker to check if the problem persists, and yet it still exists.

Hii any update on this issue.


empty Response in case of invalid Token

if im sending an invalid token i get an empty response, but i would expect some "Invalid Credentials" Response like i get when there is no token provided.
any idea what might be wrong i dont see an obvious error in my app...authentication works

I'm getting the same problem here too.

Hi,
It is indeed not the expected behavior. Have you looked at the sandbox ? Specifically the CLI testing section ? If i submit a wrong password I receive a 401 with a code and message in the response body.
Could you show us your security.yml  ? Along with Symfony version and JWT bundle version you are using ?

Hey using Symfony 3.0.1, 1.4.2 of your bundle, security looks as follows:
security:
    providers:
        in_memory:
            memory:
              users:
                  %api.user%:
                      password: %api.password%
                      roles: 'ROLE_USER'
    encoders:
        Symfony\Component\Security\Core\User\User: plaintext

    firewalls:
        dev:
            pattern: ^/(_(profiler|wdt)|css|images|js)/
            security: false

        doc:
            pattern: ^/$
            security: false

        token:
            pattern:  ^/token$
            stateless: true
            gfreeau_get_jwt: ~

        api:
            pattern:   ^/
            stateless: true
            lexik_jwt:
                query_parameter:
                    enabled: true
                    name:    token

    access_control:
        - { path: ^/login, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/_profiler, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/,       roles: IS_AUTHENTICATED_FULLY }

Hi @digitalkaoz did you find the cause of the problem ?

Nope
Nicolas Cabot<EMAIL_ADDRESS>schrieb am Mi., 27. Jan. 2016
18:57:

Hi @digitalkaoz https://github.com/digitalkaoz did you find the cause
of the problem ?
—
Reply to this email directly or view it on GitHub
https://github.com/lexik/LexikJWTAuthenticationBundle/issues/124#issuecomment-175770955
.

@slashfan To reproduce the problem, you need to send an invalid token, not submit a bad password. Try to make an authenticated request, and for example remove one or more characters in your token. You'll get an empty Response. Fixed in #142

Fixed by PR #142


Docker Machine 0.1.0-rc5

Added Docker Machine v0.1.0-rc5 command line tool.
Project URL: https://github.com/docker/machine

This is in core (now).


[WIP] 进程数据趋势堆信息完善

https://github.com/X-Profiler/xprofiler-console/commit/cb0dcb22e8108dc3a72c22cf103fbfb50683872e

Done.


Add more debugging to activeSync startSync and stopSync

Currently when a user's request to startSync and stopSync fails, very little information is printed because the exception printing happens after a fatal error. Adding this to help with debugging in the future.

Currently when a user's request to startSync and stopSync fails, very little information is printed because the exception printing happens after a fatal error.  Adding this to help with debugging in the future.
@gpang PTAL, thanks.

adding debug information to help root causing issue #9648

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4988/
Test FAILed.

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4991/
Test PASSed.

@yuzhu if these will not be spammy, then maybe warn is more appropriate than info

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5049/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5168/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5169/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5170/
Test PASSed.

@gpang PTAL

@gpang Can we merge this PR and cherry-pick to branch 2.0?

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.0 please

Thanks!


Input & Label stories crash

The stories for Input & Label are crashing on latest version. Not sure if the bug is caused by component or something in story.
Fix this before releasing #1584

Looks like it's the same thing as @pomfrida  fixed the other day

Looks like it's the same thing as @pomfrida fixed the other day

Jepp, removing <code> from description did the trick! Thanks for the heads up :)  @wenche


avoid recursive imports for index

Client had an import to index which in turn exports Client. This can cause some real weird errors.

There is nothing wrong with having Client import from '../index', it is the technique used all across this project. However the Client has references to LoggingBuilder and LoggingBuilder does not have dependencies on anything else from the '../index' module, hence it should be the first export in the index.ts file.
I cannot suggest the changes, but the fix would be for these to switch places
export { Client, ClientBuilder } from './Client';
export { LoggingBuilder, LoggingBuilderCallback, WinstonOptionsCallback } from './LoggingBuilder';

The dependencies and the order of when they are imported and exported is of high significance. The index files should serve as pure module definitions taking full control over the importing and exporting of modules

I would argue it would be a good practice to within a module to include explicitly what it needs instead of going through index, that way you have full control of it all within the module.

That would also give you the option of not having to export everything.

Adding to this a bit more; to me it seems that having to maintain the correct order in index for all scenarios within a module seems like a coupling that makes it harder to maintain, rather than being explicit about your imports. Then ordering doesn't matter. For circular dependencies, when those cases occurs - which I think are more of an edge case, we probably need to go through something like index or other composition.

I would argue it would be a good practice to within a module to include explicitly what it needs instead of going through index, that way you have full control of it all within the module.

I would argue the opposite, importing files directly gives you the least amount of control since you have no control over what the thing you import imports itself.

Adding to this a bit more; to me it seems that having to maintain the correct order in index for all scenarios within a module seems like a coupling that makes it harder to maintain, rather than being explicit about your imports. Then ordering doesn't matter. For circular dependencies, when those cases occurs - which I think are more of an edge case, we probably need to go through something like index or other composition.

From my experience and understanding the order does matter either way, and in that case it's my opinion that someone needs to take control over the importing. And yes, it certainly does not make it easier to maintain, but it makes it much easier to debug when your project has 100+ files and it builds but when you run the application and you suddenly get a Super expression must either be null or a function, not undefined or something obscure like that. Then it becomes hard to find and fix the problem.
I see writeups that tackles this problem by having these index and internal files that takes charge over the module importing and exporting https://medium.com/@daveperipatus/heres-how-to-scale-this-pattern-to-larger-projects-8227eb45e1cc

That would also give you the option of not having to export everything from the module.

There are patterns that eliminates this issue by having "internal" files that takes the importing / exporting responsibility and index files which represents the public interface of the modules

It's not like I like those patterns, in fact I do detest them 🤣

The article proposes what I proposed:
The rules are this:

add an index file per folder of files, which exports all files
within a folder, you MUST import siblings directly
outside a folder, you SHOULD import from the target folder’s index

Huh, maybe I read it wrong as well. I based it mostly of the parent article that's on top of that article which is the one I meant to copy 😄 . https://medium.com/visual-development/how-to-fix-nasty-circular-dependency-issues-once-and-for-all-in-javascript-typescript-a04c987cf0de

I don't really understand the seocond rule there, but if it works I won't complain. That gives us the benefit of not having to export everything publically.
Maybe we can try that strategy? It is pretty much what we're doing already, except from the import siblings directly part.
But either way, we should do the suffle on the export in the index file since given the ordering it makes sense the the LoggingBuilder is exported first

I quite like those 3 simple rules. And yes, we need to keep an eye on ordering and keep them logically as dependencies.
Are we good with this with the reordering I've done then??

I like those three rules, but also just to clarify (then we can put these rules into contributing guidelines at some point) - these rules apply internally in a package right?
And then when importing things from another package, do we allow importing from specific folders within the package, or just the package index?
About the order, I didn't think that it mattered as the modules are only loaded once? Or is this some way to avoid circular imports?

I like the rules - they're simple and I think they cover 99% - circular dependencies is a nightmare, but I think that is more the edge case.
With those rules I don't think ordering matters for the most part.
I would say the rules are for within a package.
For consumers, they should rely on what is publically exported IMO. But for 3rd parties using our stuff, we can't enforce that in anyway.
It makes sense to have something like this in our contrib guidelines.

I wasn't thinking about how we use external packages (as we don't always have a choice) - or how consumers use our packages. But most of our code is split over multiple packages, like the SDK.

I think it makes sense to still be relying on what is exported from index.

I wasn't thinking about how we use external packages (as we don't always have a choice) - or how consumers use our packages. But most of our code is split over multiple packages, like the SDK.

We use yarn workspace for our development environment, but in the end these things are really independent packages published to npm and should be treated that way.
I think that when referencing from external modules should always just import the main index file of that package


No text preview is displayed on pasting emoji name and colon

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app on web chrome or web safari
Open any report
Copy emoji name and colon eg: stuck_out_tongue:
In compose box, enter colon and paste the text and observe the app does not display the text and directly display emoji
Repeat same steps on android app and slack

Expected Result:
App should display text for a second as preview before changing it to emoji as it does on android app and slack
(on slack, there is text preview for 1 seconds, we have similar text preview on our android app)
Actual Result:
App directly displays emoji without text preview
NOTE : In android app,  xiaomi mi 11x and redmi note 10 pro able to see the text for a moment
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.0
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681456360777079
View all open jobs on GitHub

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@johncschuster Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

Working on reproducing this now

I don't think this behavior is a bug. I'm going to close the issue.


Problem transfering file with particular FXP destination server

FTP Server OS: Embedded
FTP Server Type:** Vsftpd
Client Computer OS: Windows
FluentFTP Version: <IP_ADDRESS>
Framework: .NET core 3.1
Hi,
I need some help regarding FXP support in FluentFTP.
My application has incorporated FXP transfer since two years. (fluentFTP lib)
Nothing out of the ordinary and everything is working just fine. FXP transfers are running between ServerA and ServerB.
Where serverA is an isilon/powerScale storage device
and serverB is an proprietary storage device with no access to the underlying Os.
This setup is currently working just fine.
My problems start since i try to FXP between ServerA and a new destination Server. (also a proprietary media device , vsftpd implementation)
If i try to manually FXP with for example flashFXP then i can successfully transfer a file between the two servers.
[L] = new problematic destination server
[R] = ServerA
[09:13:33] [R] SIZE test.bin
[09:13:33] [R]<PHONE_NUMBER>7788
[09:13:33] [R] MDTM test.bin
[09:13:33] [R]<PHONE_NUMBER>9115027
[09:13:33] [L] SIZE test.bin
[09:13:33] [L] 550 Could not get file size.
[09:13:33] [L] PASV
[09:13:33] [L] 227 Entering Passive Mode (10,211,208,221,39,115).
[09:13:33] [R] PORT 10,211,208,221,39,115
[09:13:33] [R] 200 PORT command successful. Consider using PASV.
[09:13:33] [L] STOR test.bin
[09:13:33] [R] RETR test.bin
[09:13:33] [R] 150 Opening BINARY mode data connection for test.bin<PHONE_NUMBER>8 bytes).
[09:13:33] [L] 150 Ok to send data.
[09:14:24] [R] 226 Transfer complete.
[09:14:24] [L] 226 Transfer complete.
[09:14:24] FXP: test.bin 9.63 GB in 51 seconds (194.75 MB/s)

However, when i try to do this with FluentFTP it keeps failing.
I embedded the fluentFTP logs into my application so i am very sorry for the messy log. What i can tell after inspecting and comparing several logs is that after initiating the file transfer there are messages about Closing/Disposing FtpSocketStream(data connection)s.
After that  the RETR /TestWF/private/test.bin command to ServerA is send ans answered with
Response: 150 Opening BINARY mode data connection for /TestWF/private/test.bin (796625 bytes).
However, when the STOR /fs/Data/test.bin is send to the destination server it always responds with:
425 Use PORT or PASV first. [1ms]
If i log in manually with for example ftp.exe on the destination ftp server and issue a STOR /fs/Data/test.bin manually then i get the same 425 Use PORT or PASV first response.  If i first send a quote PASV then the STOR command is accepted.
I tried setting different FtpDataConnectionTypes but it doesn't seem to matter much. Outcome is always the message 425 Use PORT or PASV first.  What am i doing wrong here? Any help or ideas are appreciated.
Logs :
The problematic ftp server in the log below has ip: <IP_ADDRESS>.
===> 19:51:13  Init FXP module v1.0
===> 19:51:13  >         Connect(False)
===> 19:51:13  FluentFTP <IP_ADDRESS>
===> 19:51:13  Connecting to IP #1= <IP_ADDRESS>:21
===> 19:51:13  Waiting for a response
===> 19:51:13  Response: 220-PowerScale OneFS <IP_ADDRESS>
===> 19:51:13  Response: 220
===> 19:51:13  Command:  USER DOMAINTX\nlsftpwf
===> 19:51:13  Waiting for response to: USER DOMAINTX\nlsftpwf
===> 19:51:13  Response: 331 Please specify the password.
===> 19:51:13  Command:  PASS ***
===> 19:51:13  Waiting for response to: PASS ***
===> 19:51:13  Response: 230 Login successful.
===> 19:51:13  Command:  FEAT
===> 19:51:13  Waiting for response to: FEAT
===> 19:51:13  Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
===> 19:51:13  Response: 211 End
===> 19:51:13  Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
===> 19:51:13  Command:  OPTS UTF8 ON
===> 19:51:13  Waiting for response to: OPTS UTF8 ON
===> 19:51:13  Response: 200 Always in UTF8 mode.
===> 19:51:13  Command:  SYST
===> 19:51:13  Waiting for response to: SYST
===> 19:51:13  Response: 215 UNIX Type: L8
===> 19:51:13  Listing parser set to: Unix
===> 19:51:13  Command:  PWD
===> 19:51:13  Waiting for response to: PWD
===> 19:51:13  Response: 257 "/"
===> 19:51:13  >         GetFileSize("/TestWF/private/test.bin", -1)
===> 19:51:13  Command:  SIZE /TestWF/private/test.bin
===> 19:51:13  Waiting for response to: SIZE /TestWF/private/test.bin
===> 19:51:13  Response: 213 796625
===> 19:51:13  >         SetWorkingDirectory("/TestWF/private")
===> 19:51:13  Command:  CWD /TestWF/private
===> 19:51:13  Waiting for response to: CWD /TestWF/private
===> 19:51:13  Response: 250 Directory successfully changed.
===> 19:51:13  Command:  PWD
===> 19:51:13  Waiting for response to: PWD
===> 19:51:13  Response: 257 "/TestWF/private"
===> 19:51:13  >         Connect(False)
===> 19:51:13  FluentFTP <IP_ADDRESS>
===> 19:51:13  Connecting to IP #1= <IP_ADDRESS>:21
===> 19:51:13  Waiting for a response
===> 19:51:13  Response: 220 Welcome to this FTP service.
===> 19:51:13  Command:  USER username
===> 19:51:13  Waiting for response to: USER username
===> 19:51:13  Response: 331 Please specify the password.
===> 19:51:13  Command:  PASS ***
===> 19:51:13  Waiting for response to: PASS ***
===> 19:51:13  Response: 230 Login successful.
===> 19:51:13  Command:  FEAT
===> 19:51:13  Waiting for response to: FEAT
===> 19:51:13  Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
===> 19:51:13  Response: 211 End
===> 19:51:13  Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
===> 19:51:13  Command:  OPTS UTF8 ON
===> 19:51:13  Waiting for response to: OPTS UTF8 ON
===> 19:51:13  Response: 200 Always in UTF8 mode.
===> 19:51:13  Command:  SYST
===> 19:51:13  Waiting for response to: SYST
===> 19:51:13  Response: 215 UNIX Type: L8
===> 19:51:13  Listing parser set to: Unix
===> 19:51:13  Command:  PWD
===> 19:51:13  Waiting for response to: PWD
===> 19:51:13  Response: 257 "/"
===> 19:51:13  >         SetWorkingDirectory("/fs/Data")
===> 19:51:13  Command:  CWD /fs/Data
===> 19:51:13  Waiting for response to: CWD /fs/Data
===> 19:51:13  Response: 250 Directory successfully changed.
===> 19:51:13  Command:  PWD
===> 19:51:13  Waiting for response to: PWD
===> 19:51:13  Response: 257 "/fs/Data"
===> 19:51:13  >         GetFileSize("/fs/Data/test.bin", -1)
===> 19:51:13  Command:  SIZE /fs/Data/test.bin
===> 19:51:13  Waiting for response to: SIZE /fs/Data/test.bin
===> 19:51:13  Response: 550 Could not get file size.
===> 19:51:13  >         TransferFile("/TestWF/private/test.bin", FluentFTP.AsyncFtpClient, "/fs/Data/test.bin", Binary, False, Overwrite, None)
===> 19:51:13  >         FileExists("/TestWF/private/test.bin")
===> 19:51:13  >         GetNameListing("/TestWF/private")
===> 19:51:13  Command:  TYPE I
===> 19:51:13  Waiting for response to: TYPE I
===> 19:51:13  Response: 200 Switching to Binary mode.
===> 19:51:13  >         OpenDataStreamAsync("NLST /TestWF/private", 0)
===> 19:51:13  >         OpenPassiveDataStreamAsync(PASVEX, "NLST /TestWF/private", 0)
===> 19:51:13  Command:  PASV
===> 19:51:13  Waiting for response to: PASV
===> 19:51:13  Response: 227 Entering Passive Mode (10,211,24,75,208,255).
===> 19:51:13  Connecting to IP #1= <IP_ADDRESS>:53503
===> 19:51:13  Command:  NLST /TestWF/private
===> 19:51:13  Waiting for response to: NLST /TestWF/private
===> 19:51:13  Response: 150 Here comes the directory listing.
===> 19:51:13  +---------------------------------------+
===> 19:51:13  Listing:  /TestWF/private/test.bin
===> 19:51:13  Closing/Disposing FtpSocketStream(data connection)
===> 19:51:13  >         CloseDataStream()
===> 19:51:13  Waiting for response to: NLST /TestWF/private
===> 19:51:13  Response: 226 Directory send OK.
===> 19:51:13  +---------------------------------------+
===> 19:51:13  Closing/Disposing FtpSocketStream(data connection)
===> 19:51:13  Command:  TYPE I
===> 19:51:13  Waiting for response to: TYPE I
===> 19:51:13  Response: 200 Switching to Binary mode.
===> 19:51:13  Command:  PASV
===> 19:51:13  Waiting for response to: PASV
===> 19:51:13  Response: 227 Entering Passive Mode (10,211,208,211,39,107).
===> 19:51:13  Command:  PORT 10,211,208,211,39,107
===> 19:51:13  Waiting for response to: PORT 10,211,208,211,39,107
===> 19:51:13  Response: 200 PORT command successful. Consider using PASV.
===> 19:51:13  >         FileExists("/fs/Data/test.bin")
===> 19:51:13  >         GetNameListing("/fs/Data")
===> 19:51:13  >         OpenDataStreamAsync("NLST /fs/Data", 0)
===> 19:51:13  >         OpenPassiveDataStreamAsync(AutoPassive, "NLST /fs/Data", 0)
===> 19:51:13  Command:  EPSV
===> 19:51:13  Waiting for response to: EPSV
===> 19:51:13  Response: 229 Entering Extended Passive Mode (|||10094|).
===> 19:51:13  Connecting to IP #1= <IP_ADDRESS>:10094
===> 19:51:13  Command:  NLST /fs/Data
===> 19:51:13  Waiting for response to: NLST /fs/Data
===> 19:51:13  Response: 150 Here comes the directory listing.
===> 19:51:13  +---------------------------------------+
===> 19:51:13  Listing:  /fs/Data/file1.bin
===> 19:51:13  Listing:  /fs/Data/Archive
===> 19:51:13  Listing:  /fs/Data/Archive_XML
===> 19:51:13  Listing:  /fs/Data/file2.bin
===> 19:51:13  Listing:  /fs/Data/Production
===> 19:51:13  Closing/Disposing FtpSocketStream(data connection)
===> 19:51:13  >         CloseDataStream()
===> 19:51:13  Waiting for response to: NLST /fs/Data
===> 19:51:13  Response: 226 Directory send OK.
===> 19:51:13  +---------------------------------------+
===> 19:51:13  Closing/Disposing FtpSocketStream(data connection)
===> 19:51:13  >         GetFileSize("/TestWF/private/test.bin", -1)
===> 19:51:13  Command:  SIZE /TestWF/private/test.bin
===> 19:51:13  Waiting for response to: SIZE /TestWF/private/test.bin
===> 19:51:13  Response: 213 796625
===> 19:51:13  Command:  RETR /TestWF/private/test.bin
===> 19:51:13  Waiting for response to: RETR /TestWF/private/test.bin
===> 19:51:13  Response: 150 Opening BINARY mode data connection for /TestWF/private/test.bin (796625 bytes).
===> 19:51:13  Command:  STOR /fs/Data/test.bin
===> 19:51:13  Waiting for response to: STOR /fs/Data/test.bin
===> 19:51:13  Response: 425 Use PORT or PASV first.
===> 19:51:13  Socket has stale data - prior to command execution
===> 19:51:13  The stale data was:
===> 19:51:13  Stale:    426 Failure writing network stream.
===> 19:51:13  Reconnect needed due to stale data present on control connection
===> 19:51:13  Command stashed: QUIT
===> 19:51:13  Closing/Disposing FtpSocketStream(control connection)
===> 19:51:13  >         Connect(True)
===> 19:51:13  Reconnect (Count: 1)
===> 19:51:13  FluentFTP <IP_ADDRESS>
===> 19:51:13  Connecting to IP #1= <IP_ADDRESS>:21
===> 19:51:13  Waiting for a response
===> 19:51:13  Response: 220-PowerScale OneFS <IP_ADDRESS>
===> 19:51:13  Response: 220
===> 19:51:13  Command:  USER DOMAINTX\nlsftpwf
===> 19:51:13  Waiting for response to: USER DOMAINTX\nlsftpwf
===> 19:51:13  Response: 331 Please specify the password.
===> 19:51:13  Command:  PASS ***
===> 19:51:13  Waiting for response to: PASS ***
===> 19:51:13  Response: 230 Login successful.
===> 19:51:13  Command:  FEAT
===> 19:51:13  Waiting for response to: FEAT
===> 19:51:13  Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
===> 19:51:13  Response: 211 End
===> 19:51:13  Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
===> 19:51:13  Command:  OPTS UTF8 ON
===> 19:51:13  Waiting for response to: OPTS UTF8 ON
===> 19:51:13  Response: 200 Always in UTF8 mode.
===> 19:51:13  Command:  SYST
===> 19:51:13  Waiting for response to: SYST
===> 19:51:13  Response: 215 UNIX Type: L8
===> 19:51:13  Listing parser set to: Unix
===> 19:51:13  Command:  TYPE I
===> 19:51:13  Waiting for response to: TYPE I
===> 19:51:13  Response: 200 Switching to Binary mode.
===> 19:51:13  >         SetWorkingDirectory("/TestWF/private")
===> 19:51:13  Command:  CWD /TestWF/private
===> 19:51:13  Waiting for response to: CWD /TestWF/private
===> 19:51:13  Response: 250 Directory successfully changed.
===> 19:51:13  Command:  PWD
===> 19:51:13  Waiting for response to: PWD
===> 19:51:13  Response: 257 "/TestWF/private"
===> 19:51:13
===> 19:51:13  Executing stashed command
===> 19:51:13
===> 19:51:13  Command:  QUIT
===> 19:51:13  Waiting for response to: QUIT
===> 19:51:13  Response: 221 Goodbye.
===> 19:51:13  Closing/Disposing FtpSocketStream(control connection)
===> 19:51:13  FXP destination ftp client error.Fault:"Code: 425 Message: Use PORT or PASV first."

I would like a log of a similar transfer of the

This setup is currently working just fine

just to compare.

One thing that comes to mind is that you are using FluentFTP Version: <IP_ADDRESS>. That is a version within the range that had an interesting quirk, or bug if you wish: In some cases (yours), it would resolve "FileExists" by using a NLST command, instead of using the much quicker SIZE command. NLST has an additional disadvantage: It uses a data connection and the associated EPSV command might have thrown the FXP logic of the server out of sync.
Be nice if you could use 49.0.1 instead? If that works, then the FXP logic is basically unable to handle an unexpected PASV/NLST command (for the "FileExists" resolution) interspersed in the command sequence.

@FanDjango ,
You where right with insinuating that it might be related to version <IP_ADDRESS>. Although i had upgraded the fluentFTP nuget package in my lib project to the latest version, somehow the fluentftp.dll was not automatically upgraded in my release folder. So i was still using the older v46 dll. After copying it over the fxp file transfer worked.
Here is the proof:
2024-01-07 13:50:56.658 +01:00    Init FXP module v1.0
2024-01-07 13:50:56.675 +01:00    >         Connect(False)
2024-01-07 13:50:56.676 +01:00    FluentFTP <IP_ADDRESS>(.NET Standard 2.1)
2024-01-07 13:50:56.686 +01:00    Connecting to IP #1= <IP_ADDRESS>:21
2024-01-07 13:50:56.698 +01:00    Waiting for a response
2024-01-07 13:50:56.727 +01:00    Response: 220-PowerScale OneFS <IP_ADDRESS>
2024-01-07 13:50:56.728 +01:00    Response: 220
2024-01-07 13:50:56.738 +01:00    Command:  USER DOMAINTX\nlsftpwf
2024-01-07 13:50:56.740 +01:00    Waiting for response to: USER DOMAINTX\nlsftpwf
2024-01-07 13:50:56.741 +01:00    Response: 331 Please specify the password.
2024-01-07 13:50:56.745 +01:00    Command:  PASS ***
2024-01-07 13:50:56.745 +01:00    Waiting for response to: PASS ***
2024-01-07 13:50:56.803 +01:00    Response: 230 Login successful.
2024-01-07 13:50:56.809 +01:00    Command:  FEAT
2024-01-07 13:50:56.810 +01:00    Waiting for response to: FEAT
2024-01-07 13:50:56.812 +01:00    Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
2024-01-07 13:50:56.815 +01:00    Response: 211 End
2024-01-07 13:50:56.826 +01:00    Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
2024-01-07 13:50:56.827 +01:00    Command:  OPTS UTF8 ON
2024-01-07 13:50:56.831 +01:00    Waiting for response to: OPTS UTF8 ON
2024-01-07 13:50:56.832 +01:00    Response: 200 Always in UTF8 mode.
2024-01-07 13:50:56.833 +01:00    Command:  SYST
2024-01-07 13:50:56.834 +01:00    Waiting for response to: SYST
2024-01-07 13:50:56.836 +01:00    Response: 215 UNIX Type: L8
2024-01-07 13:50:56.838 +01:00    Active ServerHandler is: None
2024-01-07 13:50:56.839 +01:00    Listing parser set to: Unix
2024-01-07 13:50:56.842 +01:00    Command:  PWD
2024-01-07 13:50:56.842 +01:00    Waiting for response to: PWD
2024-01-07 13:50:56.846 +01:00    Response: 257 "/"
2024-01-07 13:50:56.849 +01:00    >         GetFileSize("/TestWF/private/test2.bin", -1)
2024-01-07 13:50:56.851 +01:00    Command:  SIZE /TestWF/private/test2.bin
2024-01-07 13:50:56.852 +01:00    Waiting for response to: SIZE /TestWF/private/test2.bin
2024-01-07 13:50:56.853 +01:00    Response:<PHONE_NUMBER>280
2024-01-07 13:50:56.856 +01:00    >         SetWorkingDirectory("/TestWF/private")
2024-01-07 13:50:56.857 +01:00    Command:  CWD /TestWF/private
2024-01-07 13:50:56.858 +01:00    Waiting for response to: CWD /TestWF/private
2024-01-07 13:50:56.863 +01:00    Response: 250 Directory successfully changed.
2024-01-07 13:50:56.864 +01:00    >         Connect(False)
2024-01-07 13:50:56.865 +01:00    FluentFTP <IP_ADDRESS>(.NET Standard 2.1)
2024-01-07 13:50:56.867 +01:00    Connecting to IP #1= <IP_ADDRESS>:21
2024-01-07 13:50:56.869 +01:00    Waiting for a response
2024-01-07 13:50:56.872 +01:00    Response: 220 Welcome to this FTP service.
2024-01-07 13:50:56.873 +01:00    Command:  USER username
2024-01-07 13:50:56.874 +01:00    Waiting for response to: USER username
2024-01-07 13:50:56.878 +01:00    Response: 331 Please specify the password.
2024-01-07 13:50:56.879 +01:00    Command:  PASS ***
2024-01-07 13:50:56.880 +01:00    Waiting for response to: PASS ***
2024-01-07 13:50:56.912 +01:00    Response: 230 Login successful.
2024-01-07 13:50:56.913 +01:00    Command:  FEAT
2024-01-07 13:50:56.914 +01:00    Waiting for response to: FEAT
2024-01-07 13:50:56.915 +01:00    Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
2024-01-07 13:50:56.917 +01:00    Response: 211 End
2024-01-07 13:50:56.918 +01:00    Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
2024-01-07 13:50:56.919 +01:00    Command:  OPTS UTF8 ON
2024-01-07 13:50:56.921 +01:00    Waiting for response to: OPTS UTF8 ON
2024-01-07 13:50:56.925 +01:00    Response: 200 Always in UTF8 mode.
2024-01-07 13:50:56.926 +01:00    Command:  SYST
2024-01-07 13:50:56.927 +01:00    Waiting for response to: SYST
2024-01-07 13:50:56.929 +01:00    Response: 215 UNIX Type: L8
2024-01-07 13:50:56.930 +01:00    Active ServerHandler is: None
2024-01-07 13:50:56.931 +01:00    Listing parser set to: Unix
2024-01-07 13:50:56.932 +01:00    Command:  PWD
2024-01-07 13:50:56.935 +01:00    Waiting for response to: PWD
2024-01-07 13:50:56.937 +01:00    Response: 257 "/"
2024-01-07 13:50:56.938 +01:00    >         SetWorkingDirectory("/fs/Data")
2024-01-07 13:50:56.939 +01:00    Command:  CWD /fs/Data
2024-01-07 13:50:56.940 +01:00    Waiting for response to: CWD /fs/Data
2024-01-07 13:50:56.951 +01:00    Response: 250 Directory successfully changed.
2024-01-07 13:50:56.952 +01:00    >         GetFileSize("/fs/Data/test2.bin", -1)
2024-01-07 13:50:56.955 +01:00    Command:  SIZE /fs/Data/test2.bin
2024-01-07 13:50:56.956 +01:00    Waiting for response to: SIZE /fs/Data/test2.bin
2024-01-07 13:50:56.957 +01:00    Response: 550 Could not get file size.
2024-01-07 13:50:56.963 +01:00    >         TransferFile("/TestWF/private/test2.bin", FluentFTP.AsyncFtpClient, "/fs/Data/test2.bin", Binary, False, Overwrite, None)
2024-01-07 13:50:56.966 +01:00    >         FileExists("/TestWF/private/test2.bin")
2024-01-07 13:50:56.968 +01:00    Command:  SIZE /TestWF/private/test2.bin
2024-01-07 13:50:56.969 +01:00    Waiting for response to: SIZE /TestWF/private/test2.bin
2024-01-07 13:50:56.970 +01:00    Response:<PHONE_NUMBER>280
2024-01-07 13:50:57.034 +01:00    Command:  TYPE I
2024-01-07 13:50:57.035 +01:00    Waiting for response to: TYPE I
2024-01-07 13:50:57.037 +01:00    Response: 200 Switching to Binary mode.
2024-01-07 13:50:57.038 +01:00    Command:  TYPE I
2024-01-07 13:50:57.039 +01:00    Waiting for response to: TYPE I
2024-01-07 13:50:57.041 +01:00    Response: 200 Switching to Binary mode.
2024-01-07 13:50:57.042 +01:00    Command:  PASV
2024-01-07 13:50:57.045 +01:00    Waiting for response to: PASV
2024-01-07 13:50:57.047 +01:00    Response: 227 Entering Passive Mode (10,211,208,211,39,112).
2024-01-07 13:50:57.048 +01:00    Command:  PORT 10,211,208,211,39,112
2024-01-07 13:50:57.049 +01:00    Waiting for response to: PORT 10,211,208,211,39,112
2024-01-07 13:50:57.050 +01:00    Response: 200 PORT command successful. Consider using PASV.
2024-01-07 13:50:57.052 +01:00    >         FileExists("/fs/Data/test2.bin")
2024-01-07 13:50:57.053 +01:00    Command:  SIZE /fs/Data/test2.bin
2024-01-07 13:50:57.056 +01:00    Waiting for response to: SIZE /fs/Data/test2.bin
2024-01-07 13:50:57.057 +01:00    Response: 550 Could not get file size.
2024-01-07 13:50:57.058 +01:00    >         GetFileSize("/TestWF/private/test2.bin", -1)
2024-01-07 13:50:57.060 +01:00    Command:  SIZE /TestWF/private/test2.bin
2024-01-07 13:50:57.061 +01:00    Waiting for response to: SIZE /TestWF/private/test2.bin
2024-01-07 13:50:57.062 +01:00    Response:<PHONE_NUMBER>280
2024-01-07 13:50:57.064 +01:00    Command:  RETR /TestWF/private/test2.bin
2024-01-07 13:50:57.067 +01:00    Waiting for response to: RETR /TestWF/private/test2.bin
2024-01-07 13:50:57.068 +01:00    Response: 150 Opening BINARY mode data connection for /TestWF/private/test2.bin<PHONE_NUMBER> bytes).
2024-01-07 13:50:57.069 +01:00    Command:  STOR /fs/Data/test2.bin
2024-01-07 13:50:57.070 +01:00    Waiting for response to: STOR /fs/Data/test2.bin
2024-01-07 13:50:57.076 +01:00    Response: 150 Ok to send data.
2024-01-07 13:50:57.078 +01:00    Waiting for a response
2024-01-07 13:50:57.079 +01:00    Waiting for a response
2024-01-07 13:51:14.459 +01:00    Response: 226 Transfer complete.
2024-01-07 13:51:14.546 +01:00    Response: 226 Transfer complete.
2024-01-07 13:51:15.234 +01:00    FXP transfer of file /TestWF/private/test2.bin has completed
2024-01-07 13:51:15.236 +01:00    Command:  NOOP
2024-01-07 13:51:15.237 +01:00    Command:  NOOP
2024-01-07 13:51:15.252 +01:00    transferring file succeeded
2024-01-07 13:51:15.254 +01:00    Control connection has stale data - prior to command execution of "QUIT"
2024-01-07 13:51:15.255 +01:00    The stale data was (length = 14):
2024-01-07 13:51:15.257 +01:00    Stale:    200 NOOP ok.
2024-01-07 13:51:15.257 +01:00    Reconnect needed due to stale data present on control connection
2024-01-07 13:51:15.271 +01:00    Command stashed: QUIT
2024-01-07 13:51:15.272 +01:00    Closing/Disposing FtpSocketStream(control connection)
2024-01-07 13:51:15.273 +01:00    >         Connect(True)
2024-01-07 13:51:15.274 +01:00    Reconnect (Count: 1)
2024-01-07 13:51:15.276 +01:00    FluentFTP <IP_ADDRESS>(.NET Standard 2.1)
2024-01-07 13:51:15.277 +01:00    Connecting to IP #1= <IP_ADDRESS>:21
2024-01-07 13:51:15.278 +01:00    Waiting for a response
2024-01-07 13:51:15.289 +01:00    Response: 220-PowerScale OneFS <IP_ADDRESS>
2024-01-07 13:51:15.290 +01:00    Response: 220
2024-01-07 13:51:15.291 +01:00    Command:  USER DOMAINTX\nlsftpwf
2024-01-07 13:51:15.292 +01:00    Waiting for response to: USER DOMAINTX\nlsftpwf
2024-01-07 13:51:15.293 +01:00    Response: 331 Please specify the password.
2024-01-07 13:51:15.294 +01:00    Command:  PASS ***
2024-01-07 13:51:15.295 +01:00    Waiting for response to: PASS ***
2024-01-07 13:51:15.335 +01:00    Response: 230 Login successful.
2024-01-07 13:51:15.336 +01:00    Command:  FEAT
2024-01-07 13:51:15.337 +01:00    Waiting for response to: FEAT
2024-01-07 13:51:15.339 +01:00    Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
2024-01-07 13:51:15.340 +01:00    Response: 211 End
2024-01-07 13:51:15.341 +01:00    Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
2024-01-07 13:51:15.342 +01:00    Command:  OPTS UTF8 ON
2024-01-07 13:51:15.344 +01:00    Waiting for response to: OPTS UTF8 ON
2024-01-07 13:51:15.345 +01:00    Response: 200 Always in UTF8 mode.
2024-01-07 13:51:15.346 +01:00    Command:  SYST
2024-01-07 13:51:15.347 +01:00    Waiting for response to: SYST
2024-01-07 13:51:15.348 +01:00    Response: 215 UNIX Type: L8
2024-01-07 13:51:15.349 +01:00    Active ServerHandler is: None
2024-01-07 13:51:15.350 +01:00    Listing parser set to: Unix
2024-01-07 13:51:15.352 +01:00    Command:  TYPE I
2024-01-07 13:51:15.353 +01:00    Waiting for response to: TYPE I
2024-01-07 13:51:15.354 +01:00    Response: 200 Switching to Binary mode.
2024-01-07 13:51:15.355 +01:00    >         SetWorkingDirectory("/TestWF/private")
2024-01-07 13:51:15.356 +01:00    Command:  CWD /TestWF/private
2024-01-07 13:51:15.357 +01:00    Waiting for response to: CWD /TestWF/private
2024-01-07 13:51:15.363 +01:00    Response: 250 Directory successfully changed.
2024-01-07 13:51:15.364 +01:00
2024-01-07 13:51:15.365 +01:00    Executing stashed command
2024-01-07 13:51:15.366 +01:00
2024-01-07 13:51:15.367 +01:00    Command:  QUIT
2024-01-07 13:51:15.368 +01:00    Waiting for response to: QUIT
2024-01-07 13:51:15.369 +01:00    Response: 221 Goodbye.
2024-01-07 13:51:15.371 +01:00    Closing/Disposing FtpSocketStream(control connection)
2024-01-07 13:51:15.372 +01:00    Control connection has stale data - prior to command execution of "QUIT"
2024-01-07 13:51:15.373 +01:00    The stale data was (length = 14):
2024-01-07 13:51:15.374 +01:00    Stale:    200 NOOP ok.
2024-01-07 13:51:15.378 +01:00    Reconnect needed due to stale data present on control connection
2024-01-07 13:51:15.379 +01:00    Command stashed: QUIT
2024-01-07 13:51:15.380 +01:00    Closing/Disposing FtpSocketStream(control connection)
2024-01-07 13:51:15.381 +01:00    >         Connect(True)
2024-01-07 13:51:15.382 +01:00    Reconnect (Count: 1)
2024-01-07 13:51:15.383 +01:00    FluentFTP <IP_ADDRESS>(.NET Standard 2.1)
2024-01-07 13:51:15.384 +01:00    Connecting to IP #1= <IP_ADDRESS>:21
2024-01-07 13:51:15.386 +01:00    Waiting for a response
2024-01-07 13:51:15.389 +01:00    Response: 220 Welcome to this FTP service.
2024-01-07 13:51:15.392 +01:00    Command:  USER username
2024-01-07 13:51:15.393 +01:00    Waiting for response to: USER username
2024-01-07 13:51:15.394 +01:00    Response: 331 Please specify the password.
2024-01-07 13:51:15.395 +01:00    Command:  PASS ***
2024-01-07 13:51:15.397 +01:00    Waiting for response to: PASS ***
2024-01-07 13:51:15.437 +01:00    Response: 230 Login successful.
2024-01-07 13:51:15.438 +01:00    Command:  FEAT
2024-01-07 13:51:15.440 +01:00    Waiting for response to: FEAT
2024-01-07 13:51:15.441 +01:00    Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
2024-01-07 13:51:15.442 +01:00    Response: 211 End
2024-01-07 13:51:15.443 +01:00    Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed
2024-01-07 13:51:15.444 +01:00    Command:  OPTS UTF8 ON
2024-01-07 13:51:15.446 +01:00    Waiting for response to: OPTS UTF8 ON
2024-01-07 13:51:15.447 +01:00    Response: 200 Always in UTF8 mode.
2024-01-07 13:51:15.448 +01:00    Command:  SYST
2024-01-07 13:51:15.449 +01:00    Waiting for response to: SYST
2024-01-07 13:51:15.450 +01:00    Response: 215 UNIX Type: L8
2024-01-07 13:51:15.451 +01:00    Active ServerHandler is: None
2024-01-07 13:51:15.457 +01:00    Listing parser set to: Unix
2024-01-07 13:51:15.459 +01:00    Command:  TYPE I
2024-01-07 13:51:15.460 +01:00    Waiting for response to: TYPE I
2024-01-07 13:51:15.461 +01:00    Response: 200 Switching to Binary mode.
2024-01-07 13:51:15.462 +01:00    >         SetWorkingDirectory("/fs/Data")
2024-01-07 13:51:15.463 +01:00    Command:  CWD /fs/Data
2024-01-07 13:51:15.464 +01:00    Waiting for response to: CWD /fs/Data
2024-01-07 13:51:15.466 +01:00    Response: 250 Directory successfully changed.
2024-01-07 13:51:15.467 +01:00
2024-01-07 13:51:15.468 +01:00    Executing stashed command
2024-01-07 13:51:15.471 +01:00
2024-01-07 13:51:15.472 +01:00    Command:  QUIT
2024-01-07 13:51:15.474 +01:00    Waiting for response to: QUIT
2024-01-07 13:51:15.475 +01:00    Response: 221 Goodbye.
2024-01-07 13:51:15.476 +01:00    Closing/Disposing FtpSocketStream(control connection)
As a side note,  this version also solves another annoying issue for me. I have an ftp destination that has 50k files in one folder. So i noticed that in the v<IP_ADDRESS> release of fluentFTP it took a very long time when using a "FileExists" command and my logs where flooded with a 50k+ file listing. So nice to see that has been upgraded too.

That's great. In your log I see a few other (small) issues also, that will be fixed - but these don't detract from successful transfers.


[python-package] [dask] add type annotations on dask._HostWorkers

Contributes to #3756.
Contributes to #3867.
Split from #5765.
Proposes replacing the use of collections.namedtuple for one internal class in the Dask module with a regular Python class, so that informative type annotations can be added.
This makes it a bit clearer, when reading the code, what the values of that class's attributes should be (unlike namedtuple, which is just a collection of attribute names).
I chose to use a regular Python class instead of dataclasses.dataclass to preserve support for Python 3.6 (https://github.com/microsoft/LightGBM/pull/5765#issuecomment-1454861675), and chose to avoid typing.NamedTuple (https://stackoverflow.com/a/50038614/3986677) to reduce the risk of incompatibilities caused by future updates to typing.

thanks @jmoralez !


p14

what happened to this is this merged.Can I use comet with maui p14 ?

I was never able to get CI to setup and build correctly. RC is coming so we will just Target that.


FunctionID: signatures with xrefs

FLIRT signatures have a feature of identifying of imported/external references too (a signature stores an offset and a name to the external symbol). Does FunctionID support that? If no - is it possible to add a support?

FunctionID doesn't have the feature of identifying of imported/external references. But Ghidra does, I think. Read README file and see contains of the directory.

IDA also uses xrefs to identify functions.
For example, if a function only have a jump to EXP_FUNC, it will also be identified. But Ghidra can't do that, because it uses a different approach.

So, I think the issue should be marked as Enhancement.

Yep.

So, to clarify:
it would be great to add a posibility to identify functions by xrefs in it.
Example (now it won't be identified):
func some_sig_func:
    call some_xref_func
    ret

But, if FunctionID will also use xrefs info to identify a function, it can be marked.


pull request for e2e test at 11/27/2016 05:26:05

:white_check_mark: Validation status: passed
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.


Fixing the mimeType description to 'output'

Just changed the config typo #584

Thank you for your contribution! 👍

Hey @SebasRomero , would you mind to re-open the PR? We have to merge it on our side first to include it into the code base. I didn't merge right away as I wanted to give others time to comment.

It doesn't let me to re open it, it's okay if I do a new PR?

It doesn't let me to re open it, it's okay if I do a new PR?

Totally, just open a new one.


"Găneasa", "Cozieni", "Moara Domnească", "Șindrilița" and "Piteasca" are listed in the drop-down menu

Description:
"Găneasa", "Cozieni", "Moara Domnească" and "Piteasca" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Găneasa" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Găneasa, ILFOV (Găneasa)" and "Comuna Găneasa, ILFOV".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Cozieni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Cozieni, ILFOV (Găneasa)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Moara Domnească" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Moara Domnească, ILFOV (Găneasa)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Piteasca" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Piteasca, ILFOV (Găneasa)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Type "Șindrilița" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Șindrilița, ILFOV (Găneasa)".


Usage with fullcalendar css

Hi, I tried using this boilerplate with a standard fullCalendar view, it renders the calendar and fetches events normally but it does not load fullcalendar.min.css that comes within the calendar node module.
How can I import the fullcalendar.min.css to within a calendar component or the global css scope?

See #394!

hi @mrisoli can you possibly share a snippet on how you added fullcalendar to react-boilerplate? I have been having a hard time integrating it to the boilerplate.


The password in the Prometheus configuration file needs to support encrypted storage.

Proposal
The basic authentication information for monitoring targets in the Prometheus startup configuration file prometheus.yml is stored in plaintext, which is sensitive to customers with high security requirements, causing them to be unable to use the Prometheus service. Is there any solution from the official Prometheus to address this issue?
scrape_configs:

basic_auth:
password: xxxxxxxxxxxxxx
username: pushgateway
honor_labels: true
job_name: pushgateway
scrape_interval: 30s
scrape_timeout: 20s
static_configs:

labels:
instance: <IP_ADDRESS>:9091
targets:

<IP_ADDRESS>:9091

Yes, you can use password_file and store the password on another filesystem.

@roidelapluie How can I separate the basic_auth authentication information for monitoring targets in the prometheus.yml file into a separate file? And how can Prometheus associate and read this password file when loading the prometheus.yml file during startup? It seems not feasible, as the authentication I mentioned is not the basic authentication of Prometheus itself, but the basic authentication information for Prometheus monitoring targets.

Here's how to separate basic authentication information using password_file in Prometheus:

Create Password File:

Create password.txt containing:your_password

Update prometheus.yml:
global:
  scrape_interval: 15s

scrape_configs:
  - job_name: 'example'
    static_configs:
      - targets: ['example.com']
    basic_auth:
      username: 'your_username'
      password_file: '/path/to/password.txt'

Secure Password File:
chmod 600 /path/to/password.txt
chown prometheus:prometheus /path/to/password.txt

Reload Prometheus Configuration:
curl -X POST http://localhost:9090/-/reload

This separates the password securely into a file and updates the Prometheus configuration to use it.

@roidelapluie thanks very much，but this method merely isolates the password into a separate file, however, this password file cannot be encrypted, which still fails to meet security requirements. I am wondering if the Prometheus team could modify the code to support encrypted transmission of basic authentication passwords for these jobs. It would be much anticipated for the official support to be in place.

If the password is encrypted, Prometheus would still need to decrypt it at runtime, which means the decryption key or method would also need to be accessible to Prometheus. This would ultimately not improve security, as the key could also be a target for attackers.
The best practice in such cases is to ensure that the password file is stored securely, with strict access controls and auditing in place to monitor any access to it...

@xiaoyuan2019 I thought TLS is for sending the password (and everything else) encrypted
https://prometheus.io/docs/operating/security/#authentication-authorization-and-encryption

Maybe the work here is relevant: https://github.com/prometheus/prometheus/pull/13955
(Unfortunately, this PR seems to have stalled…)

Also see https://docs.google.com/document/d/1EqHd2EwQxf9SYD8-gl3sgkwaU6A10GhiN7aw-2kx7NU/edit
This really looks like what is requested here, so I'm closing this as duplicate.


Calculate vouchers using base prices

I want to merge this change because...

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

@stnatic Can you confirm that the new flow takes into account a discount?

@korycins this PR does not change the flow yet, discount amount is included in the "base calculations" for checkout's total. some additional math might be needed later on if taxes/discounts are swapped places inside of fetch_checkout_prices_if_expired

@stnatic Have you checked this changes with https://github.com/saleor/saleor-plugin-avatax-excise ?

I haven't tested end to end with the excise plugin yet, but it seems to override the same PluginManager methods as the original Avatax plugin. The renamed method for calculating subtotal was introduced recently in a shipping-related ticket, so it isn't really used anywhere across Saleor yet


how to make my own dataset

hi dude, could u explain how to define the dump1 and dump2 in the dataset? went through your code, it's hard to understand everything without comments
cheers

Dump1 and dump2 are not used. You can just put any number there. It is indeed tedious to go through the Torch code. I recently uploaded a PyTorch version which should be much easier to try and achieve similar performance.

thanks, dude, could u tell me where is the PyTorch version???

Hi! I changed the dump1 and dump2 2 of doors by 1 1, 1 2, 2 1 and 2 2. But I am getting the following error.


Publish binaries

It is possible to attach any file as an asset to any github release. That should be good enough - there's a test image

Binaries will be tags and live in binaries branch


"combined Workspace and CopyBook Folders to search" should only contain workspace folders with relevant files

Because of a setup that has multiple relative and one absolute path - and the same workspace definition being used for both Windows and GNU/Linux with different absolute paths (see https://github.com/microsoft/vscode/issues/105290 to get the idea) I currently see the following output (/projects/project1 is the directory where the workspace definition is):
  Combined Workspace and CopyBook Folders to search:
   => /projects/project1/src
   => /projects/project1/src/subProject1
   => /projects/project1/src/subProject2
   => /projects/project1/src/subProject3
   => /projects/project1/X:/common
   => /home/all/common
   => /projects/project1/sql
   => /projects/project1/config

I'd expect /projects/project1/X:/common not to be in there as a check should raise ENOENT for that folder. /projects/project1/sql and /projects/project1/config _may be removed there, too as it does not contain any files that are evaluated by the extension and checking this once should provide better performance than checking all files in there each time.

No validation is done on workspace folders, if they are present it assumes they are valid or will become valid.
The directory is technically a valid Linux directory, it just does not exist.

No validation is done on workspace folders, if they are present it assumes they are valid or will become valid.

I understand that this is the current approach, this issue  is about the suggestion to change that,

Not sure that is a good idea as the folder may appear late r and monitoring auto mountable areas is not nice.
Why not use links/junctions to resolve the issue?

The issue is that at least one of the out-of-tree path is actually user-specific and there's no option to use {env:USER} in the folder definition currently. But if you find it to be not reasonable to "skip" the folders that currently don't contain sources relevant to this extension that's of course your decision to take (which should result in closing that issue then).
I'm not sure about this after your explanation "may be there later" but would tend to: if added later then a cleanup of the meta data should fix that issue; better not monitor folders which contain only unrelated files (or even do not exist [yet]). That part is the "more general" issue in this discussion so I'll rename it.

In any case I invite you to vote for the referenced vscode issue which is now in the backlog...

Yes, I will.

Closed as this is unlikely to be adjustded.


Remove usage of non-standardised Reflect.decorate

Reflect.decorate is not on a standards track and has no active proposal being championed in TC39.
We have no idea if Reflect.decorate will get added to the language, even if it does, we have no guarantee it will be the implementation we are assuming it to be.
By having this condition in the code, we are likely preventing Reflect.decorate from ever existing in the language, just like Array.prototype.flatten had to get a different name because MooTools would attempt to use it if it existed and it was not the implementation they assumed it would be.

Fixes #

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


Fix fallout from gcc/gfortran-10 update

The latest update of gcc and gfortran to version 10 caused some packages to break due to stricter code checking:

[x] bagel https://github.com/markuskowa/NixOS-QChem/pull/185
[ ] amd-scalapack
[ ] exatensor
[ ] iboview
[ ] mcdth
[ ] mesa-qc
[ ] molcas-18.09
[ ] molden
[ ] orient
[ ] pegamoid
[ ] siesta
[ ] wfoverlap

See also Porting to GCC 10.

I am currently a little bit short on time, but will try to fix mine as soon as I find a free time slot.

I've tried also fixing Molden. The issue would probably simply be solved by switching to Molden7.0. Unfortunately fetchurl and curl in general refuse connecting to the site due to some SSL certificate errors. Also had no success with just switching to http there.

Molden may require more work. I have tried to update it several times, but ran into a variety of issues (changes in the build system, segfaults in the final binary).
Molden 7.1 is now available (put online two days ago). I will give it another try.

Lesson learned: some fixes broke the build against gfortran-9, but updating the nixpkgs pinning of course broke the rest that wasn't yet fixed. In the future, I will make a staging branch for such "major breakage" situations. PRs will then go on the staging branch first until everything is fixed. This will guarantee that we have a fully "green" master at all times.


Support Kubernetes 1.17 in tests

Feature Request
Molecule test framework for operator-sdk uses bsycorp/kind image, that did not release 1.17 version. This makes us unable to test against kubernetes > 1.16
We could evaluate if we can use kindtest:node images instead of custom ones.

It looks like their CI failed for 1.17: https://travis-ci.org/bsycorp/kind/builds/648677096?utm_source=github_status&utm_medium=notification

Hi @glothriel,
The plan is to upgrade the SDK to use 1.17 k8s api. However, it has dependencies with OLM then, we need to wait for OLM be upgraded first. Note that the 1.17 still not supported yet.
PS: By checking your errors in https://travis-ci.org/github/bsycorp/kind/jobs/648677100#L403 I am not sure if the 1.17 is properly set up in your test env too.

Hi @camilamacedo86

PS: By checking your errors in https://travis-ci.org/github/bsycorp/kind/jobs/648677100#L403 I am not sure if the 1.17 is properly set up in your test env too.

This isn't my test env, it's a build that builds bsycorp/kind images, that are used by OperatorSDK molecule test framework. So even if OperatorSDK itself had support for 1.17, we are unable to ship molecule tests, as there are no bsycorp/kind:1.17 images.

The default Kube version is 1.16. See; https://github.com/operator-framework/operator-sdk/blob/ff657078952b44bf46fbfd9bf30ed84b500f1973/doc/ansible/dev/testing_guide.md#L95

Oke my upstream issue seems to be resolved: https://github.com/bsycorp/kind/issues/29

Just, to register we are working to upgrade the SDK to use the upper version 1.17 and it will probably be shipped with the next release.


[1.12] Bump Mesos to nightly 1.7.x 71685b5

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/80d42b9a2c9223665a82bbaaf3cbc222a094e2ef...71685b5c807e4d4d1a5ebe33a3c3c0a2f824b9b4

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review


Support ash 0.27.1 to 0.29.0

Thanks! Instead of bumping the max version, I just removed it in v0.1.7 which I just released.


Fix remote URLs that contain query strings returning invalid extensions.

There were 2 issues with the previous code:
1 - The file path was encoded so checking for ? would fail as it should actually be checking for %3F.
2 - The pathinfo() would also return an invalid extension if the file path contained a query string. For example, if the image was foo.jpg?query then the pathinfo extension would be jpg?query.
By moving the query string detection before the pathinfo, it solves the previous 2 issues.

Any update on this?


fix: correct pkg name

fixes package name in readme - will likely have repercussions on package site

I'm not sure this warrants a version bump/news update ...

Thank you @jcken95!


Unable to save file

We have written the needed data into your clipboard because it was too large to send. Please paste.

We have written the needed data into your clipboard because it was too large to send. Please paste.

You needed to paste in the report you wrote up.


Unreachable feeds

Thank you for the app.
I see the following message on exit:
1 unreachable feeds found. See `cleanup-on-quit` in newsboat(1) for details.
Run " cleaning" but apparently there is some kind of error.
newsboat --cleanup
Starting Newsboat 2.36.0...
Loading configuration...done.
Opening cache...done.
Loading URLs from /Users/oleg/.newsboat/urls...done.
Loading articles from cache...done.
Cleaning up cache...Caught newsboat::DbException with message: database disk image is malformed

How exactly can one find out what is meant by "1 unreachable feeds found"? Which feed exactly?
As far as I understand some url from rss_feed table doesn't match what should be in feedurl from rss_item table, is that right??
newsboat -v
Newsboat 2.36.0 - https://newsboat.org/
Copyright (C) 2006-2015 Andreas Krennmair
Copyright (C) 2015-2024 Alexander Batischev
Copyright (C) 2006-2017 Newsbeuter contributors
Copyright (C) 2017-2024 Newsboat contributors

Newsboat is free software licensed under the MIT License. (Type `newsboat -vv' to see the full text.)
It bundles:
- JSON for Modern C++ library, licensed under the MIT License: https://github.com/nlohmann/json
- optional-lite library, licensed under the Boost Software License: https://github.com/martinmoene/optional-lite
- expected-lite library, licensed under the Boost Software License: https://github.com/martinmoene/expected-lite

Newsboat 2.36.0
System: Darwin 23.3.0 (arm64)
Compiler: g++ Apple LLVM 15.0.0 (clang-15<IP_ADDRESS>)
ncurses: ncurses 6.0.20150808 (compiled with 6.0)
libcurl: libcurl/8.4.0 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.58.0 (compiled with 8.4.0)
SQLite: 3.43.2 (compiled with 3.43.2)
libxml2: compiled with 2.9.13

Thx!

Okay, this can be found via the error-log.

In the logs:
[2024-06-27 02:57:03] Unreachable feed found: exec:~/.newsboat/suffix.sh https://site.com/rss/hubs/ 3
But _https://site.com/rss/hubs/_ is not in urls or in the database. Don't understand where that address is coming from.
Managed to get rid of the error in newsboat --cleanup, but it still doesn't help, it's still "1 unreachable feeds found. ...".

To best of my knowledge unreachable means that the feed is no longer found in the urls file, but exists in the database. Either rssurl in rss_feed table, or feedurl in rss_item table, if I'm not mistaken. You could check those columns in the database to see if it's there.
The "database disk image is malformed" error is bit concerning, that message comes from the sqlite3 database. I'm not sure why the cleanup doesn't work, but malformed database might explain it.

Thanks for the reply.
I used https://sqlitebrowser.org/ to replace the text in the base and it looks like this is what broke it.
sqlite3 ./cache.db
SQLite version 3.43.2 2023-10-10 13:08:14
Enter ".help" for usage hints.
sqlite> SELECT * FROM "rss_item" WHERE feedurl LIKE '%habr.com/rss%';
sqlite> PRAGMA integrity_check;
row 4804 missing from index idx_guid
row 28618 missing from index idx_guid
row 36152 missing from index idx_guid
row 81911 missing from index idx_guid
wrong # of entries in index idx_feedurl
wrong # of entries in index idx_guid
sqlite> PRAGMA foreign_key_check;
sqlite> PRAGMA quick_check;
ok

But if you execute the query from the program, the result is different, but the program also does not show the string.

DELETE FROM "rss_item" WHERE feedurl LIKE '%habr.com/rss%'; also doesn't help.
Don't understand at all what is this "invisible" string and how to fix the problem.

This looks like a problem on the sqlite side. I would suggest taking a backup, and then trying to restore the corrupt database.
You could check https://sqlite.org/recovery.html, and try the .recover sqlite command. Or stackoverflow has some discussion e.g. https://stackoverflow.com/questions/18259692/how-to-recover-a-corrupt-sqlite3-database.

@jonuts thx, it did help.
sqlite3 cache.db ".dump" | sqlite3 new.db


Incorrect command for adding REG_MULTI_SZ

The correct example to add REG_MULTI_SZ  is
reg add HKLM\Software\MyCo /v MRU /t REG_MULTI_SZ /d fax\0mail\0
instead of
reg add HKLM\Software\MyCo /v MRU /t REG_MULTI_SZ /d fax\0mail\0\0

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

ID: bd817f1d-e494-af38-4a10-86360d63c195
Version Independent ID: 11fcbf91-6c28-9ae8-045a-35ea97444dfe
Content: reg add
Content Source: WindowsServerDocs/administration/windows-commands/reg-add.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

#assign:xelu86

Hey @SaurabhGautam,
Thanks again for contacting Microsoft. We value your feedback.
A documentation change has been made correcting this issue and will be live after the next business day. We will now be closing this thread.
Thank you and have a most pleasant day. #please-close


Help me chatbot

from time import sleep
from selenium.webdriver.common.by import By
from selenium import webdriver
from selenium.webdriver.common.keys import Keys
from selenium.webdriver.support import expected_conditions as EC
from selenium.common.exceptions import TimeoutException
from selenium.webdriver.support.ui import WebDriverWait
import socket
#import csv
message_text='Ola essa é uma mensagem automatizada de Whats App.' # message
no_of_message = 1 # no. of time
moblie_no_list = [5551981440050,<PHONE_NUMBER>05] # list of phone number
#moblie_no_list= open('entrada.csv', 'r')
def element_presence(by,xpath,time):
element_present = EC.presence_of_element_located((By.XPATH, xpath))
WebDriverWait(driver, time).until(element_present)
def is_connected():
try:
# connect to the host -- tells us if the host is actually
# reachable
socket.create_connection(("www.google.com", 80))
return True
except :
is_connected()
driver = webdriver.Chrome(executable_path="D:\Programas\Aulas\scripts\Projetos\whatsautomatico\chromedriver.exe")
driver.get("http://web.whatsapp.com")
sleep(10) #wait time to scan the code in second
def send_whatsapp_msg(phone_no,text):
driver.get("https://web.whatsapp.com/send?phone={}&source=&data=#".format(phone_no))
try:
#driver.switch_to_alert().accept()#alterar a linha ou comenta#
driver.switch_to_alert.accept()
#driver.switch_to_alert().accept()
except Exception as e:
pass
try:
    element_presence(By.XPATH,'//*[@id="main"]/footer/div[1]/div[2]/div/div[2]',30)
    txt_box=driver.find_element(By.XPATH , '//*[@id="main"]/footer/div[1]/div[2]/div/div[2]')
    global no_of_message
    for x in range(no_of_message):
        txt_box.send_keys(text)
        txt_box.send_keys("\n")

except Exception as e:
    print("invailid phone no :"+str(phone_no))

for moblie_no in moblie_no_list:
try:
send_whatsapp_msg(moblie_no, message_text)
except Exception as e:
    sleep(10)
    is_connected()

I need help in this code the list in line 13 only read the first phone number and in the second occuried an error.
Please help me


ArtifactBar Code

Why close?

I closed this and some of the others because I was finally able to get the code for the HonorWatchBar done and figured it would be easier to just do both at the same time.


Issue creating image: missing release files

On a mac, fresh install of docker:
Erics-MacBook-Pro:Delphin$ docker build -t logon image
Sending build context to Docker daemon  4.096kB
Step 1/15 : FROM ubuntu:18.10
18.10: Pulling from library/ubuntu
8a532469799e: Pull complete
32f4dcec3531: Pull complete
230f0701585e: Pull complete
e01f70622967: Pull complete
Digest: sha256:7d657275047118bb77b052c4c0ae43e8a289ca2879ebfa78a703c93aa8fd686c
Status: Downloaded newer image for ubuntu:18.10
---> 9dc19675e327
Step 2/15 : RUN dpkg --add-architecture i386
---> Running in a56ce690bada
Removing intermediate container a56ce690bada
---> a92ccd3b9031
Step 3/15 : RUN apt-get update -q
---> Running in e9a09139fa83
Ign:1 http://archive.ubuntu.com/ubuntu cosmic InRelease
Ign:2 http://security.ubuntu.com/ubuntu cosmic-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu cosmic-updates InRelease
Err:4 http://security.ubuntu.com/ubuntu cosmic-security Release
404  Not Found [IP: <IP_ADDRESS> 80]
Ign:5 http://archive.ubuntu.com/ubuntu cosmic-backports InRelease
Err:6 http://archive.ubuntu.com/ubuntu cosmic Release
404  Not Found [IP: <IP_ADDRESS> 80]
Err:7 http://archive.ubuntu.com/ubuntu cosmic-updates Release
404  Not Found [IP: <IP_ADDRESS> 80]
Err:8 http://archive.ubuntu.com/ubuntu cosmic-backports Release
404  Not Found [IP: <IP_ADDRESS> 80]
Reading package lists...
E: The repository 'http://security.ubuntu.com/ubuntu cosmic-security Release' does not have a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic Release' does not have a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic-updates Release' does not have a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic-backports Release' does not have a Release file.
The command '/bin/sh -c apt-get update -q' returned a non-zero code: 100

Hi @EricZinda , hope this last commit solves this problem.  I will wait your feedback to close this issue.

Thanks so much @arademaker !  That fixed it


Storage Explorer Extensibility Preview

Hello everyone! We're looking for developers who would be interested in creating Storage Explorer extensions.
We want to preview the writing of Storage Explorer extensions to those who are interested. For this preview, you would be able to create extensions that build on top of existing Storage Explorer features and experiences. For example, adding an action to the context menu of the blob explorer. Clicking the action would trigger your extension and allow you to run your code against your data in Azure Storage.
If you are interested in being a part of this preview, please take this survey: https://aka.ms/storageexplorer/extensibilityprivatepreviewsurvey
FAQ:

What languages are extensions written in?

Extensions are primarily written using JavaScript and HTML.

Do I need to know how to code to participate in the preview?

Yes. We are looking for those with existing coding experience.

Do I need to have an existing idea for an extension?

Yes. We will not be providing ideas for you.

What types of extensions are you looking for?

We're looking for extensions that build on top of existing Storage Explorer features and experiences. For example:

Adding actions to the blob explorer context menu
Adding actions to the blob container context menu
Doing something after an upload/download finishes

@fhljys @kamrankamaei @albertleigh @dikokob @jbunifi @evagelos21 and others, the survey for the extensibility preview is now live here: https://aka.ms/storageexplorer/extensibilityprivatepreviewsurvey

Are there any updates on providing an extensibility mechanism for Azure Storage Explorer?  I'm willing to sign up for a preview/code camp, etc.

Are there any updates for 2024?

Any updates? We would like to be able to properly search our azure blob storage by prefix, postfix, wildcard etc.


feat: make regeneration not override nodes by default

can add a new keybind to do overriding
https://twitter.com/spring_stream/status/1640824513213652992?s=20

Correct me if wrong but if changing the prompt of a node in the middle of a tree creates new children nodes, once regeneration occurs the history / lineage of the previous ones is not going to be accurate anymore (also related to #7). This could lead to confusion or incorrect assumptions.
Note that this is already the case for:

nodes further down the tree, when a regeneration with override happens
more in general, any node whose prompt has been edited regardless of regeneration

So thinking it might be desirable to:

highlight "outdated" nodes in the UI, by storing lineageAtGeneration and detecting when it differs from current lineage
highlight "edited" nodes, and exposing a command to revert to their original state
add a command and shortcut to regenerate all outdated nodes

And going back to the issue at hand, if we don't want to partially invalidate the tree while regenerating without overriding, the ideal solution should be

Create a new sibling node with the edited prompt
Trigger generation from that node

Correct me if wrong but if changing the prompt of a node in the middle of a tree creates new children nodes, once regeneration occurs the history / lineage of the previous ones is not going to be accurate anymore

yup this is definitely the case, but i'd consider this more of a design choice than a bug or something to be addressed with a lot of complexity. flux is a power tool for power users. there are valid cases where you might want to retroactively edit and prune the tree, even if that means the tree as it stands is not reproducible/deterministic. we provide people with all the tools to do things like this and make adjacent nodes for branching, overriding, etc if that's the behavior they want.
so in terms of this:

if we don't want to partially invalidate the tree while regenerating without overriding, the ideal solution should be
if prompt hasn't been edited
Generate more nodes, instead of overriding
if prompt has been edited
Create a new sibling node with the edited prompt
Trigger generation from that node

i do think this is one path we could go, but personally i think we should make this a path users can take if they want (by creating a new sibling node themselves with the new prompt, etc) but not force it upon them.
willing to reconsider down the line, but this is my take rn

Yes I agree. It definitely feels secondary, so not worth the increase in complexity and edge cases to handle this would come with.


Added The 11th Hour to use scummvm-latest

A small change to support "The 11th Hour" using scummvm-latest.

Sorry for the delay, it is already done!


Clickhouse 19.5.3 revision 54417 left join speeds about 10 times slower than ClickHouse server version 18.16.0 revision 54412

Hello, everyone, I upgrade the clickhouse from 18.16.0 to 19.5.3, then test the same sql with the same data. The result is not good, like this:
ClickHouse server version 18.16.0 revision 54412
SELECT count(0) FROM test.local a left JOIN test.test_local b ON _id = b._id;
┌─count(0)─┐
│   719930 │
└──────────┘
1 rows in set. Elapsed: 0.009 sec. Processed 719.93 thousand rows, 5.76 MB (83.56 million rows/s., 668.49 MB/s.)

Clickhouse 19.5.3 revision 54417
SELECT count(0) FROM test.local a left JOIN test.test_local b ON _id = b._id;
┌─count(0)─┐
│   719930 │
└──────────┘
1 rows in set. Elapsed: 0.050 sec. Processed 719.93 thousand rows, 5.76 MB (14.53 million rows/s., 116.27 MB/s.)
I appreciate that you guys can pay attention to this problem.

Test (<IP_ADDRESS>2):
create table jt(A Int64, S0 String, S1 String, S2 String, S3 String) Engine=MergeTree order by A;
insert into jt select number, toString(arrayMap(x->x, range(100))) s, s, s, s from numbers(500000);
select count() from jt left join jt using A;
Elapsed: 0.030 sec.
select count() from jt a left join (select A from jt) b on a.A=b.A;
Elapsed: 0.309 sec.
18.16.0
select count() from jt left join jt using A;
Elapsed: 0.027 sec.

@zhang2014 has fixed the issue.


Stat to indicate a connection reuse?

Is there a stat that indicates that a new HTTP stream is reusing an existing upstream connection rather than creating a new one?
Will appreciate guidance if this info can be inferred from existing stats, otherwise please mark as help-wanted.

cc: @jmarantz


Suggestion: add UUID library support and an api to generate sha1 digest and

This PR suggests adding UUID library support to package/std.
UUID is useful for managing something in gaming contracts or collection contracts, especially corporate with external servers or services.
This UUID generation uses UUID v5 for deterministic generation and the seed message for sha1 is concatenated bytes of contract address, block height, and an incremental number saved in the contract storage.
UUID v5 uses sha1 internally, and this PR suggests adding an API to calculate sha1 digests.
This API takes a little shorter time and a little cheaper gas to generate a UUID than calculating a digest in WASM native operators.
If the message size gets longer, it gets much faster and takes much cheaper gas than calculating with WASM native.
If this suggestion looks good (even if only the sha1 part), I will modify the gas cost after taking a benchmark with circle CI. (It looks like it is not usable circle ci bench workflow in my GitHub repo)
Only the sha1 part is merged, I will publish the uuid feature in my repository.

CI fails because of adding a new API.

Thanks for the PR, but after discussing it internally a bit, we think that we don't want to add hash functions to the API interface.
Reasons are listed here in a similar issue.
The points essentially boil down to:

there are a lot of hash functions, adding one kinda opens the floodgates if you get what I mean
hash functions are generally rather quick and therefore gas efficient
it would add maintainance burden for us, especially since your use-case of SHA-1 for UUID generation is a little more exotic.

Also WASM code execution is rather quick, so the need to add native functions, especially for digests such as SHA-1, isn't as pressing as with other VMs.

As a suggestion for your use-case, if the gas cost for SHA-1 is too high, you could use RNGs such as WyRand, Mersenne Twister, etc. to stretch an input to the length you need.
Since they do not attempt to be cryptographically secure in any way, you might achieve higher throughput.

@aumetra Thank you for considering and kindly replying. I understand that you will not add hash functions and I agree with the reason.
I close this issue. Thank you!


UPDATE_ROLLBACK_FAILED state and can not be updated when pushing changes

Describe the bug
Getting the following error when I try to amplify push changes from the CLI. I'm using the CLI because my amplify console build is also failing.
Stack:arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190222141121/a3ea3540-36d5-11e9-8a22-121328bc7b22 is in UPDATE_ROLLBACK_FAILED state and can not be updated.

To Reproduce
Steps to reproduce the behavior:
I recently attempted to change the PAY_PER_REQUEST to PROVISIONED DynamoDBBillingMode in parameters.json and when that failed I switched back. Then I added two new fields to my schema which also caused my amplify console build to fail.
I'm experiencing intermittent build errors in the amplify console for over a week and have someone looking into that well. I mention it because it could be related. I also upgraded to the latest cli last week.
Expected behavior
Ability to push schema changes without error.
Desktop (please complete the following information):

OS: macOS
Version 1.6.3

@aireater could you include the additional lines from the CloudFormation output.

@yuth this is all i get from the cli:
⠼ Updating resources in the cloud. This may take a few minutes..✖ An error occurred when pushing the resources to the cloud

Stack:arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190222141121/a3ea3540-36d5-11e9-8a22-121328bc7b22 is in UPDATE_ROLLBACK_FAILED state and can not be updated.

and here's the log from the amplify console failed build (latest):
2019-04-29T19:40:31.674Z [INFO]: Git SSH Key acquired
2019-04-29T19:40:31.773Z [INFO]: Cloning repository: git@bitbucket.org:modernutility/modern-app.git
2019-04-29T19:40:31.951Z [INFO]: Agent pid 69
2019-04-29T19:40:31.975Z [WARNING]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2019-04-29T19:40:32.111Z [WARNING]: Cloning into 'modern-app'...
2019-04-29T19:40:32.369Z [WARNING]: Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2019-04-29T19:40:35.498Z [INFO]: Switching to commit: ee2766820e04791899e5a5368b83f3ed33ba8361
2019-04-29T19:40:35.594Z [WARNING]: Note: checking out 'ee2766820e04791899e5a5368b83f3ed33ba8361'.
                                    You are in 'detached HEAD' state. You can look around, make experimental
                                    changes and commit them, and you can discard any commits you make in this
                                    state without impacting any branches by performing another checkout.
                                    If you want to create a new branch to retain commits you create, you may
                                    do so (now or later) by using -b with the checkout command again. Example:
                                    git checkout -b <new-branch-name>
                                    HEAD is now at ee27668... format change
2019-04-29T19:40:35.594Z [INFO]: Checking for Git submodules at: /codebuild/output/src782203504/src/modern-app/.gitmodules
2019-04-29T19:40:35.626Z [INFO]: Retrieving cache...
2019-04-29T19:40:47.150Z [INFO]: Extracting cache...
2019-04-29T19:41:38.730Z [INFO]: Extraction done...
2019-04-29T19:41:38.928Z [INFO]: Retrieving environment cache...
2019-04-29T19:41:46.247Z [INFO]: ## Starting Backend Build
                                 # Starting phase: build
                                 # Executing command: amplifyPush --simple
2019-04-29T19:41:46.250Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache
2019-04-29T19:41:46.279Z [INFO]: # Start initializing Amplify environment: dev
2019-04-29T19:41:46.280Z [INFO]: STACKINFO={
                                 "awscloudformation": {
                                 "AuthRoleName": "modernapp-20190222141121-authRole",
                                 "UnauthRoleArn": "arn:aws:iam::473356752602:role/modernapp-20190222141121-unauthRole",
                                 "AuthRoleArn": "arn:aws:iam::473356752602:role/modernapp-20190222141121-authRole",
                                 "Region": "us-east-1",
                                 "DeploymentBucketName": "modernapp-20190222141121-deployment",
                                 "UnauthRoleName": "modernapp-20190222141121-unauthRole",
                                 "StackName": "modernapp-20190222141121",
                                 "StackId": "arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190222141121/a3ea3540-36d5-11e9-8a22-121328bc7b22"
                                 },
                                 "categories": {
                                 "auth": {
                                 "cognito5cc85e6d": {}
                                 }
                                 }
                                 }
                                 # Importing Amplify environment: dev (amplify env import)
2019-04-29T19:41:56.739Z [INFO]: Successfully added environment from your project
2019-04-29T19:41:56.796Z [INFO]: # Initializing existing Amplify environment: dev (amplify init)
2019-04-29T19:41:58.251Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2019-04-29T19:42:01.157Z [WARNING]: - Initializing your environment: dev
2019-04-29T19:42:01.805Z [WARNING]: ✔ Initialized provider successfully.
2019-04-29T19:42:02.250Z [INFO]: GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/src782203504/src/modern-app/amplify/backend/api/ModernApp/schema.graphql or place .graphql files in a directory at /codebuild/output/src782203504/src/modern-app/amplify/backend/api/ModernApp/schema
2019-04-29T19:42:25.648Z [WARNING]: - Updating resources in the cloud. This may take a few minutes...
2019-04-29T19:42:25.921Z [WARNING]: Error updating cloudformation stack
2019-04-29T19:42:25.923Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
2019-04-29T19:42:25.923Z [WARNING]: ✖ There was an error initializing your environment.
2019-04-29T19:42:25.923Z [INFO]: init failed
2019-04-29T19:42:25.927Z [INFO]: { ValidationError: Stack:arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190222141121/a3ea3540-36d5-11e9-8a22-121328bc7b22 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
                                 at Request.extractError (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/protocol/query.js:50:29)
                                 at Request.callListeners (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
                                 at Request.emit (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
                                 at Request.emit (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/request.js:683:14)
                                 at Request.transition (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/request.js:22:10)
                                 at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/state_machine.js:14:12)
                                 at /root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/state_machine.js:26:10
                                 at Request.<anonymous> (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/request.js:38:9)
                                 at Request.<anonymous> (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/request.js:685:12)
                                 at Request.callListeners (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
                                 message: 'Stack:arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190222141121/a3ea3540-36d5-11e9-8a22-121328bc7b22 is in UPDATE_ROLLBACK_FAILED state and can not be updated.',
                                 code: 'ValidationError',
                                 time: 2019-04-29T19:42:25.919Z,
                                 requestId: 'ea3ab9c0-6ab6-11e9-b81f-7744bf87e756',
                                 statusCode: 400,
                                 retryable: false,
                                 retryDelay: 63.69543174526875 }
2019-04-29T19:42:25.934Z [ERROR]: !!! Build failed
2019-04-29T19:42:25.934Z [ERROR]: !!! Non-Zero Exit Code detected
2019-04-29T19:42:25.935Z [INFO]: # Starting environment caching...
2019-04-29T19:42:25.935Z [INFO]: Uploading environment cache artifact...
2019-04-29T19:42:26.099Z [INFO]: # Environment caching completed
Terminating logging...

Hey, @aireater, you will need to go to the AWS CoudFormation Console and look for the events of your stacks to find out what caused the UPDATE_ROLLBACK_FAILED. The logs of the Amplify Console doesn't help.

Thanks, @kstro21 I looked at the cloud formation console and I can see that UPDATE_ROLLBACK_FAILED is from Mon, 15 Apr.
The error is
Subscriber limit exceeded: Update to PayPerRequest mode are limited to once in 1 day(s). Last update at Mon Apr 29 17:25:33 UTC 2019. Next update can be made at Tue Apr 30 17:25:33 UTC 2019 (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: LimitExceededException;

We are now past that time and I still can't push changes.

Use the option Continue update rollback in the stack. The state of the stack needs to be UPDATE_ROLLBACK_COMPLETE until you can update the stack again.

@kstro21 they are all nested stacks in UPDATE_ROLLBACK_FAILED state. The only non nested fail is from February.

@aireater, sorry it was not clear in my last comment. You can use the option Continue update rollback in the root stack. The state of the stack needs to be UPDATE_ROLLBACK_COMPLETE until you can update the stack again.

@kstro21 Thanks! That worked. Closing.

Whoops. Just had this problem and the failed ones were all real old but I hit continue rollback and after like 30 mins it still said in progress. Then I just decided they were so old I could probably just hit delete. Well I deleted my whole app accidently along with the 400 users I had gotten. Well there are good days and there's today. Time to restart. Be careful here


File doc/a1645191.txt contains ‘XXXXXXX’

Hi Dave
Thanks for your project, I seem to have found and issue in the text file - a1645191.txt
Actual:
Line 3
dream XXXXXXX COUNTRY light XXXXXXX stock. identify role for who XXXXXXX lose detail. CUSTOMER finish nearly AS economic investment source.
Expected
Line 3
dream COUNTRY light stock. identify role for who lose detail. CUSTOMER finish nearly AS economic investment source.
I will be submitting a pull request soon
Thank you
Dee

Yes that is definitely a problem, hope to fix soon


TamilUltra TV

Source name
TamilUltra TV
Source URL
https://tamilultra.team
Package type
bangumi
Source language
en
Other details
Indian Live TV (mainly on Tamil Language)
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

https://github.com/LikDev-256/likdev256-tamil-providers/blob/master/TamilUltraProvider/src/main/kotlin/com/likdev256/TamilUltraProvider.kt


Update custom-formatters.md

Fixes #10103

Thanks, Rick. You have one typo; “Aample” should be “Sample”, I believe.

@jfoshee 	Thanks! Fixed.
Thanks for bringing this to our attention.


Refactor exec node interface part 1

Hi @steiler
I propose to make the following changes in the part1 of the review.
Here I rename the Node interface methods to RunExecs and RunExec
RunExecs take a list of string commands to work on, whereas RunExec take an ExecCmd (renamed).
I have changed the commands used for different kinds from slice to string type, as it is easier for humans to check what the command is about visually.
PS. I plan to do more renaming in the following PRs, but before I wanted to clear this major change with you first

Beware, that this way you will specifically need to make sure, no one is providing execs to the config of a bridge or ova...
In my implementation these kinds would just overwrite these functions and no special handling would be needed... you are reintroducing specal code for these kinds of nodes by doing the following:

@steiler I am not sure I understand your comment
Here is a lab I used to test the implementation
name: linux

topology:
  nodes:
    l1:
      kind: linux
      image: alpine
      exec:
        - ash -c 'cat /etc/os-release | grep NAME' # correct cmd
    l2:
      kind: linux
      image: alpine
      exec:
        - 'echo "l2 node"' # correct cmd
    test-bridge: # should exist for this lab to run
      kind: bridge
      exec:
        - "ip link" # should be a noop, since execs have no meaning

  links:
    - endpoints: ["l1:eth1", "l2:eth1"]

The test-bridge node has exec config provided, but since this node has RunExecs func, it is being called and the warnings are emitted. Here is the output from this lab run. What am I missing here?
❯ dclab dep -c -t private/exec.clab.yml
INFO[0000] Containerlab v0.0.0 started
INFO[0000] Parsing & checking topology file: exec.clab.yml
INFO[0000] Destroying lab: linux
INFO[0000] Removed container: clab-linux-l2
INFO[0000] Removed container: clab-linux-l1
INFO[0000] Removing containerlab host entries from /etc/hosts file
INFO[0000] Removing /root/container-lab/clab-linux directory...
INFO[0000] Creating lab directory: /root/container-lab/clab-linux
INFO[0000] Creating container: "l1"
INFO[0000] Creating container: "l2"
INFO[0001] Creating virtual wire: l1:eth1 <--> l2:eth1
INFO[0002] Adding containerlab host entries to /etc/hosts file
WARN[0002] Exec operation is not implemented for kind "bridge"
WARN[0002] Failed to exec commands for node "test-bridge"
INFO[0002] Executed command 'echo l2 node' on l2. stdout:
l2 node
INFO[0002] Executed command 'ash -c cat /etc/os-release | grep NAME' on l1. stdout:
NAME="Alpine Linux"
PRETTY_NAME="Alpine Linux v3.17"
INFO[0002] 🎉 New containerlab version 0.33.0 is available! Release notes: https://containerlab.dev/rn/0.33/
Run 'containerlab version upgrade' to upgrade or go check other installation options at https://containerlab.dev/install/
+---+---------------+--------------+--------+-------+---------+----------------+----------------------+
| # |     Name      | Container ID | Image  | Kind  |  State  |  IPv4 Address  |     IPv6 Address     |
+---+---------------+--------------+--------+-------+---------+----------------+----------------------+
| 1 | clab-linux-l1 | 8c9d5d506006 | alpine | linux | running | <IP_ADDRESS>/24 | 2001:172:20:20::2/64 |
| 2 | clab-linux-l2 | 53fa5b6e4a96 | alpine | linux | running | <IP_ADDRESS>/24 | 2001:172:20:20::3/64 |
+---+---------------+--------------+--------+-------+---------+----------------+----------------------+

Sorry, yes you are right! no RunExecConfig will not come with no RunExec... in that way we're back on track...


row click except one field

Hi. I want my row when clicked doing some function, but i want another field of row doing something else when clicked. Is It possible?
Consider the exception field as button.
Thanks for your attention.

If you would put the button into the field, you could just return false from the click handler
$("<button>").click(function() {
    // some action
    return false;
});

If you wish to handle the click on the entire table cell, you could redefine rowClick in grid config:
rowClick: function(args) {
    var $target = $(args.event.target);

    if($target.closest(".your-field-css-class").length) {
       // handle cell click
    }

    // otherwise handle row click
    if(this.editing) {
        this.editItem($target.closest("tr"));
    }
},

Yes, returning false on click works, Thank you very much for your support.