A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)

docker run  -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=BB@@bb@123" -e "MSSQL_PID=Express" -p 1433:1433  mcr.microsoft.com/mssql/server:2017-latest-ubuntu
docker run --rm -it --name sql_server_thib -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=BB@@bb@123" -p 1433:1433 microsoft/mssql-server-linux
sqlcmd -S  <IP_ADDRESS>  -U sa   -P BB@@bb@123
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login failed for user 'sa'..

They have  changed thr port without documentation ....its 1434
docker run --rm -it  --name sqlserver  -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=1StrongPwd!!" -e "SA_PASSWORD=1StrongPwd!!" -p 1434:1434 microsoft/mssql-server-linux
But wait theres more even after that you will be greated with
TITLE: Connect to Server
Cannot connect to <IP_ADDRESS>,1434.

ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft SQL Server&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476

An existing connection was forcibly closed by the remote host

BUTTONS:
OK

Same here with docker image server:2017-CU18-ubuntu-16.04 and docker 2.203 stable version, the only solution is to reinstall docker when this error start to appear.

I had to use Docker for Windows version <IP_ADDRESS> to solve this. And the problem never showed again.

I've cleaned the mssql data folder and made a docker system prune and rebooted my machine and it started to work again.

I was able to repro this issue, I think the problem is you are trying to connect to fast. SQL Server is probably still starting when you hit the SQLCmd session.
Withouth waiting:
[dba mastery] $  docker run --name sql_server_thib \
> -e "ACCEPT_EULA=Y" \
> -e "SA_PASSWORD=BB@@bb@123" -e "MSSQL_PID=Express" \
> -p 1433:1433 \
> -d mcr.microsoft.com/mssql/server:2017-latest-ubuntu
04eddb8956bfc021b716f8a13e88bd20dafc74cc88b4f5b5852a36c883a9495f

[dba mastery] $  sqlcmd -U sa -P 'BB@@bb@123'
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server..

5 seconds waiting:
[dba mastery] $  docker run --name sql_server_thib \
> -e "ACCEPT_EULA=Y" \
> -e "SA_PASSWORD=BB@@bb@123" -e "MSSQL_PID=Express" \
> -p 1433:1433 \
> -d mcr.microsoft.com/mssql/server:2017-latest-ubuntu
7f8484891adbd4b373447956ef5e927c5b4dea0b410a03bdd59b561f411b86d7

[dba mastery] $  sleep 5
[dba mastery] $

[dba mastery] $  echo "Checking the container logs to make sure SQL is up"
[dba mastery] $  docker logs sql_server_thib -f
2020-03-10 06:20:33.74 spid21s     Service Broker manager has started.
2020-03-10 06:20:33.82 spid6s      Recovery is complete. This is an informational message only. No user action is required.
2020-03-10 06:20:34.17 spid10s     The default language (LCID 0) has been set for engine and full-text services.
^C
[dba mastery] $  sqlcmd -U sa -P 'BB@@bb@123'
1> exit

You can always use the docker logs command to make sure SQL Server completed the recovery successfully and then connect using SQLCMD.
Regards,

We have the same problem on travis-ci. Sometimes it works, often not:
sudo docker run --name=mssql-server -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=S3c0r3P4ss' -p 1433:1433 -d mcr.microsoft.com/mssql/server:2017-latest && sudo docker cp sqlserver.sql mssql-server:sqlserver.sql && sudo docker exec -it mssql-server /opt/mssql-tools/bin/sqlcmd -S <IP_ADDRESS> -U SA -P 'S3c0r3P4ss' -i sqlserver.sql; fi
Unable to find image 'mcr.microsoft.com/mssql/server:2017-latest' locally
2017-latest: Pulling from mssql/server
Status: Downloaded newer image for mcr.microsoft.com/mssql/server:2017-latest
c489a696045690bef9da36c72c2c0d6ec905dccd075aed1374fe76a6d875363c
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login failed for user 'SA'..
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

Sleeping for 5 seconds doesn't help.

Thought I scarpped it out and switched to alternatives  ..but for me i waited more than 5 minutes ...yet the problem perssted

@dbamaster Thought I scarpped it out and switched to alternatives ..but for me i waited more than 5 minutes ...yet the problem perssted

I see, can you please copy the content of the SQL container log. In case your container name is still sql_server_thib:
docker logs sql_server_thib

Also, have you considered trying with a different SQL Server image?
The latest image for Ubuntu 18.04 was released a week ago, maybe you want to give it a try: mcr.microsoft.com/mssql/server:2019-CU3-ubuntu-18.04
Regards,

Same issue on 2017-latest.  Luckily I am able to switch to 2019-latest which didn't have the problem.

I got this error because I didn't meet password validation requirements. Make sure your password is at least 8 characters and contains a number and a special character.
Stupid mistake I know...

I got this error because I didn't meet password validation requirements. Make sure your password is at least 8 characters and contains a number and a special character.
Stupid mistake I know...

I confirm that my issue was that. @microsoft has to make the error message more explicit.

I got this error because I didn't meet password validation requirements. Make sure your password is at least 8 characters and contains a number and a special character.
Stupid mistake I know...

I also can confirm this on SQL Server 2019 version 15.0 (RHEL).
Added some specials chars to the passwords and now the error doesn't occur anymore.

In my opinion, the source of this issue is an inaccurate error message. I'm getting the same message like this, but my mistake was incorrect port.

I got this error because I didn't meet password validation requirements. Make sure your password is at least 8 characters and contains a number and a special character.
 Thanks a lot, @GeoffreyFook


The term COG is used but the abbreviation is not defined.

A sentence reads "Programmatic ingestion is optimized for reducing ingestion costs (COGs), by minimizing storage transactions during and following the ingestion process". I've looked everywhere, but I can't find a definition for the abbreviation COG.

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

ID: 7c758ab8-a66a-0d9d-af7a-a0fbe43ec6f4
Version Independent ID: c03b112b-7c1d-3b3e-a452-779f902ce273
Content: Azure Data Explorer data ingestion
Content Source: articles/data-explorer/ingest-data-overview.md
Service: data-explorer
GitHub Login: @orspod
Microsoft Alias: orspodek

@michaeldaw Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@orspod Hi Ornat, could you please check this issue and update the document as necessary? Thank you.

@michaeldaw, thanks very much for your feedback.  COGS is "cost of goods sold". The term doesn't add to the understanding of the text. I will remove it.

#please-close

Thanks everyone.


Replace esperanto with rollup

Since esperanto is deprecated consider switching to rollup.

We switched entirely to Babel, master of cli is already using this.


Command-W on macOS doesn't close About window

VSCode Version: Code 1.11.1 (d9484d12b38879b7f4cdd1150efeb2fd2c1fbf39, 2017-04-06T14:00:34.044Z)
OS Version: Darwin x64 16.4.0
Extensions: none

Steps to Reproduce:

Open the About window
Execute command-W key combo

The actual open editor tab closes, instead of the active window (the About window). Command-W on macOS always closes the active window, and this is not how VSC behaves.

Darwin x64 16.4.0  mac?

That's the kernel version.

hey，that's key shortcuts description { "key": "cmd+w","command":"workbench.action.closeActiveEditor" },,that only close active window.I think all key shortcuts only work in workbench,and the about window is Independent :)

You can use Esc.


Implement 'booking search' endpoint

See ticket #971 on the CAS3 Trello board.

This PR implements the GET /bookings/search endpoint introduced by the OpenAPI specification changes from #533. This enables the delivery of the "find a booking" feature in the Temporary Accommodation service.
Changes in this PR:

The X-Service-Name header in the GET /bookings/search endpoint has been added as a required header. This is a formality from the frontend client's point of view as it's already provided for all API requests by default, but allows the API to filter bookings by service type, avoiding the possibility of reporting bookings for the wrong service.
The BookingSearchRepository class has been introduced to perform the actual query against the database for bookings. It allows for optionally filtering the results by booking status and probation region, but is not responsible for sorting the results (see below).
The BookingSearchService class has been introduced. The service determines the user's probation region if the calling service is Temporary Accommodation and queries the repository using the provided or derived filters. It then iterates over the results to retrieve the name of the person the booking is for by calling the Community API using their CRN. Finally, it sorts according to the specified sort field and order - which must happen at this stage rather than in the SQL query as the person's name is required to be one of the sort fields, and is not available any earlier than this.
The BookingSearchResultTransformer class has been introduced to map the results of the BookingSearchService to the API model.
The BookingSearchController class has been introduced to handle the API endpoint. It provides default values for the search order and field if they are not provided by the client before delegating to the BookingSearchService.

Might be worth adding indexes on status and probation region?

@brownbearsoftware I've requested a re-review as there's been some rework following a discussion in the CAS3 team about using the same statuses in the search as are used in the bookings themselves. I've also added the suggested indices to the tables in a Flyway migration.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Different install technology.
Brief description of your issue
New Version of GnuWin32.Grep , version 3.5.0, has changed its Installation Technology from .exe Setup Install, to .zip (Portable) Install.
Can't Upgrade Package without Uninstalling it first.

[!NOTE]
I'm unsure if this's a problem to be reported in this repo, or winget-cli repo, any guidance will help, thanks in advance 😄

Steps to reproduce

Have Version 2.5.4 of GnuWin32.Grep Package Installed on your system.
run winget upgrade GnuWin32.Grep in a Terminal running as Admin.
See The following error:

A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

Actual behavior
winget won't upgrade GnuWin32.Grep Package from 2.5.4 to the newer version 3.5.0 when running winget upgrade GnuWin32.Grep
Expected behavior
GnuWin32.Grep Package upgrades successfully
Environment
Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3296
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Enabled

Screenshots and Logs

Hi @og-mrk,

A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

This error means that you installed with one installer type (maybe MSI) but the installer in the repo is another type (maybe Inno or InstallShield) and it's not recommended to have 1 installer install something and another installer upgrade/modify/uninstall, as unexpected situations might result.
The path forward is to uninstall the previous version before using the package manager to install the current version. There was a feature request to automate this uninstall, but it hasn't been impleemented yet to my knowledge.


Document recent changes to allow non-inclusive ranges as quantifiers

Recent changes allowed 1^..^10 non inclusive range syntax as general quantifiers in regexes. These were documented.

Thanks. Would you fix a tpo tho: carat -> caret (Unless "carat" is a Perl 6 term I'm not familiar with)

@zoffixznet Fixed that typo

Thanks a lot!


Feature request: Hide a closure from search results

Hey there! I sometimes use nix-tree to solve issues with duplicate Python dependencies, and it can be quite hard to keep track of which specific versions of a dependency I've already checked out (especially if there are many different versions in the closure).
It would be great if there was a keybind to hide/"cross out" the currently selected closure for the remainder of the session (or perhaps until restored through a keybind) so that it or anything it closes over does not show up in search results anymore. That would really help a lot!

Ooh, this is interesting. Thanks for bringing this up :).
First, here's another issue with a vaguely similar concern that this functionality might also help: https://github.com/utdemir/nix-tree/issues/29
Here's what I am thinking right now:

It would be great if there was a keybind to hide/"cross out" the currently selected closure for the remainder of the session

I'd be against hiding things as I feel like it would be too easy to trigger it mistakenly which would cause the program to show "incorrect" results for the rest of the session. But "Crossing out" is interesting. I can see how it would be useful.
I also initially thought it might even be more possible to implement it as a "flag" feature where you could mark things with their dependencies with differently coloured flags. So it would also be possible to have common transitive dependencies showing both of the flags. And we can show the flags everywhere we show a store path (why depends, search etc.).
Both for the "crossing out" and "flags", we'd need to think about a good UX. As:

We probably want to show somewhere whether the feature is enabled, and which derivation it is targeted.
Likely triggering the shortcut again would toggle it.
We should word it in a way that is clear what it is doing.

I'll sleep on it for a bit, but I do think this will be a useful addition. "Marking something alongside with all their transitive deps" seems like a useful thing to be able to do. But I want to think more about it and find other use cases to see if it is generally useful.


Add Shodipo Ayomide to list

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[x] 👩🏽🦱 Adding new developer
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Shodipo Ayomide works at Fleek as a Senior Developer Advocate who is based in Lagos, Nigeria, he runs quite a number of projects around Africa which includes unStack Africa which is present in 6 African countries and his loves sharing knowledge through all the work he does for the community.

Yo! @Developerayo thanks for the PR. Can you open this via the GitHub Issue instead, thanks 🙏🏾
https://github.com/bdougie/awesome-black-developers/issues/new/choose

Definitely bro!


Stuck at "Trying to initialize the sensor..."

I have it wired up properly and my i2c address is showing as 0x6A which I changed, but it is not getting past
sensor = Driver(0x6A)
Any advice on what is going on? Anything to inspect or see? I am trying this on a Raspberry Pi 4.
Thank you

This seems to be a little bit complicated to debug on github issues
If you want you can contact me on discord : lefuturiste#5297 or https://discord.gg/XwmtNuUG2w
I will also make a report here for others people.

My BMI160 was faulty. Thank you for the follow up.

no problem


Force Prefect rebuild

PR to rebuild due to Prefect failures.

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_05owlouuxy/clone/recipe/meta.yaml:49: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_05owlouuxy/clone/recipe/meta.yaml:49: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_7bwl8ncvrd/clone/recipe/meta.yaml:49: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_7bwl8ncvrd/clone/recipe/meta.yaml:49: missing_license_url: The recipe is missing a license_url
Warnings were found


Pandas: replace append method with concat because its deprecated

Describe the bug
append method to append dataframes is deprecated and needs to be replaced with concat.
Steps To Reproduce
Run any of the scrape functions
Expected behavior
No warning message
Relevant log output
WhereDoIHaveAnAccount/scraper.py:64: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  email_header_df = email_header_df.append([{'from': msg.from_, 'subject': msg.subject}])

Anything else?
No response

fixed


Add more notes to escape semicolons in PowerShell

There were already a few of these notes in the page, so I just went ahead and added them to any other PowerShell examples that use a semicolon.
Closes #763

Thanks for tackling this, but  the update doesn't address the gist of #763, which wasn't about how to prevent PowerShell from interpreting a ; meant to be interpreted by wt.exe, but the inverse:
How to prevent wt.exe from interpreting a ; meant for a different program - such as the PowerShell CLI - for which a command line is being passed.
Such ; characters must be escaped as \;, irrespective of what program is being invoked and - that's the surprising part - this escaping is even necessary for ; characters inside "...."-enclosed arguments.
E.g.:
# From PowerShell
# From cmd.exe, the ` (backtick) would have to be removed.
wt.exe powershell -NoExit -Command "Get-Date\; `$PROFILE"

Note how ; must be escaped as \; in order for wt.exe to pass it through to powershell.exe, despite being inside a double-quoted string.
From PowerShell's perspective, ; does not require escaping inside "..." or '...'.


disconnect frequently on linux while stays connected on mac

Hi @sandeepmistry
I noticed that after connecting to the peripheral, discovering services, reading one characteristics, i would get disconnect event after some time on linux.
However on macbook, the connection stay open until i disconnect the central manually.
Is this a know behavior to get disconnects when the connection is idle?
btw, thanks for the awesome lib.

Hi @chirag04,
Please share the following:

bleno app you are using
debug logs: sudo DEBUG=* node <file>.js
HCI dump capture: sudo hcidump -t -x
kernel version: uname -a


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: istio-testing
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
0d541ecb8233842c3c3f747f9f3e7d5bee435e4c
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Moving from city built on top of railroad to railroad tile costs movement points

In Civilization, if a city is built on top of a railroad, the railroad remains and moving from or to that tile from or to a railroad tile does not cost movement points.

Are you sure? I'm pretty sure you lose 1/3 moves after exiting a city.

This is specifically a city built on top of a railroad; that is, one that already had a railroad on the tile before the city was built.  The city does not destroy that railroad tile and you get the full benefit from it.  The city only adds irrigation.

I made a little demonstration video with one of my old saves.  It shows building a city on top of a railroad area, moving around on it without losing movement points, and that "RailRoad" is displayed in the tile information when the unit is on it.  The version depicted is 475.01.
http://lex.clansfx.co.uk/requested/CivOnerailroadcity.mkv

Oh, the video also shows that the city tile gains the extra resources benefit from the railroad improvement, gaining 4 food per turn instead of 3.

I noticed another component of this issue is that cities with railroad connected to them say "RailRoad" when a unit is standing on them, even if a railroad was not built on that tile before the city was founded.

It's an observation misinterpretation on my side, I'm looking at the best way to solve this... I believe the eventual solution will be less complex that the current implementation.

I'm sure this would be solved with your simpler implementation, but I've just observed that another symptom is that a city with railroad built beside them that die leave railroad behind, even if no railroad was built there.


http: add Kill Request HTTP filter

Add a KillRequest HTTP filter which can crash Envoy when receiving a Kill request. It will be used to fault inject kill request to Envoy and measure the blast radius.
The new KillRequest filter will be disabled at build time by default in Envoy by comment out the KillRequest filter extension in extensions_build_config.bzl
@htuch
PS: Original PR #14039 was closed due to being accidentally messed up.
Risk Level: Low, new feature.
Testing: Unit/integration tests.
Docs Changes: Added
Release Notes: Added
Issue: #13978

/retest-circle

/retest

LGTM modulo two small nits

Thank you Harvey for the review!

/retest

LGTM, thanks!

Thank you Harvey! All Required CI test has been passed.


chore: release

🤖 New release

rustsat: 0.5.0 -> 0.6.0
rustsat-tools: 0.3.0 -> 0.3.1
rustsat-minisat: 0.3.0 -> 0.3.1
rustsat-cadical: 0.3.0 -> 0.3.1
rustsat-kissat: 0.2.0 -> 0.2.1
rustsat-glucose: 0.3.0 -> 0.3.1
rustsat-ipasir: 0.1.0 -> 0.1.1

Changelog
rustsat

[0.6.0] - 2024-06-11
Features

Incremental precision in DPW
Format vars and lits nicely with debug

Testing

Fix warnings

rustsat-tools

[0.3.1] - 2024-06-11
Features

Incremental precision in DPW

rustsat-minisat

[0.3.1] - 2024-06-11
Miscellaneous Tasks

Updated the following local packages: rustsat

rustsat-cadical

[0.3.1] - 2024-06-11
Miscellaneous Tasks

Updated the following local packages: rustsat

rustsat-kissat

[0.2.1] - 2024-06-11
Miscellaneous Tasks

Updated the following local packages: rustsat

rustsat-glucose

[0.3.1] - 2024-06-11
Miscellaneous Tasks

Updated the following local packages: rustsat

rustsat-ipasir

[0.1.1] - 2024-06-11
Miscellaneous Tasks

Updated the following local packages: rustsat

This PR was generated with release-plz.

The only breaking change (without the internal feature) is #108, which we will not treat as breaking. Hence this will be release 0.5.1


Mergeback (v3.3.x)

Update main with changes to v3.3.x.
NOTE: Should be merged without squashing.

This looks great. I've just asked @stephenworsley to also regenerate the lock-files, since both v3.3.x and main have had their own lock-file updates at different times, and I don't want to risk any confusion.

From further discussion: we have worked out that the lock-files on v3.3x were updated more recently than main, so there is no risk. Will merge as is.


Remove enabled attribute for now

What
Remove the enabled attributes from the output configurations.  Prior to filebeat 1.0.0 being released you could set the enabled flag to true or false to turn an output on of off.  The feature was removed and at the moment you need to completely comment out or remove an output stanza to turn it off.
How
Removed from the README file and the commented out attributes.  No effective change to how the recipe works but folks like myself won't go down the path of using the attribute only to find it doesn't work as expected.
Reference
Hopefully this will be added back to libbeat in the future as it is a super useful flag to have - especially in configuration management where you may want to override an output depending on role or environment.
https://github.com/elastic/beats/issues/1589

@drenalin23 👍


[Snyk] Upgrade next from 14.0.4 to 14.1.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade next from 14.0.4 to 14.1.4.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 155 versions ahead of your current version.
The recommended version was released a month ago, on 2024-03-20.

Release notes

Package name: next

14.1.4 - 2024-03-20NoteThis release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Update React from 60a927d04 to 4b84f11 (#63476) @ ztanner
fix revalidation issue with route handlers (#63213) @ ztanner
ensure mpa navigations to the same URL work after restoring from bfcache (#63155) @ ztanner
Ensure PromiseLikeOfReactNode is not included in .d.ts files (#63185) @ timneutkens
Fix metadata url cases should not append with trailing slash (#63050) @ huozhi
feat: add deploymentId config (#63198) @ styfle
fix: bump<EMAIL_ADDRESS>(#61538) @ styfle
fix x-forwarded-port header (#63303) @ Ethan-Arrowood
fix: x-forwarded-port header is 'undefined' when no port in url (#60484) @ yuvalotem

Test Changes

test: switch order of tests to avoid flakniess (#63482) @ huozhi
fix broken create-next-app tests (#63019) @ ztanner

14.1.3 - 2024-03-06

14.1.2 - 2024-03-04

14.1.2-canary.7 - 2024-03-04

14.1.2-canary.6 - 2024-03-04

14.1.2-canary.5 - 2024-03-04

14.1.2-canary.4 - 2024-03-04

14.1.2-canary.3 - 2024-03-03

14.1.2-canary.2 - 2024-03-02

14.1.2-canary.1 - 2024-03-01

14.1.2-canary.0 - 2024-03-01

14.1.1 - 2024-02-29

14.1.1-canary.82 - 2024-02-29

14.1.1-canary.81 - 2024-02-29

14.1.1-canary.80 - 2024-02-29

14.1.1-canary.79 - 2024-02-28

14.1.1-canary.78 - 2024-02-28

14.1.1-canary.77 - 2024-02-27

14.1.1-canary.76 - 2024-02-27

14.1.1-canary.75 - 2024-02-27

14.1.1-canary.74 - 2024-02-26

14.1.1-canary.73 - 2024-02-26

14.1.1-canary.72 - 2024-02-24

14.1.1-canary.71 - 2024-02-23

14.1.1-canary.70 - 2024-02-22

14.1.1-canary.69 - 2024-02-21

14.1.1-canary.68 - 2024-02-21

14.1.1-canary.67 - 2024-02-21

14.1.1-canary.66 - 2024-02-21

14.1.1-canary.65 - 2024-02-20

14.1.1-canary.64 - 2024-02-20

14.1.1-canary.63 - 2024-02-20

14.1.1-canary.62 - 2024-02-19

14.1.1-canary.61 - 2024-02-19

14.1.1-canary.60 - 2024-02-18

14.1.1-canary.59 - 2024-02-17

14.1.1-canary.58 - 2024-02-17

14.1.1-canary.57 - 2024-02-16

14.1.1-canary.56 - 2024-02-15

14.1.1-canary.55 - 2024-02-15

14.1.1-canary.54 - 2024-02-14

14.1.1-canary.53 - 2024-02-14

14.1.1-canary.52 - 2024-02-13

14.1.1-canary.51 - 2024-02-12

14.1.1-canary.50 - 2024-02-12

14.1.1-canary.49 - 2024-02-12

14.1.1-canary.48 - 2024-02-11

14.1.1-canary.47 - 2024-02-10

14.1.1-canary.46 - 2024-02-09

14.1.1-canary.45 - 2024-02-09

14.1.1-canary.44 - 2024-02-08

14.1.1-canary.43 - 2024-02-07

14.1.1-canary.42 - 2024-02-07

14.1.1-canary.41 - 2024-02-07

14.1.1-canary.40 - 2024-02-06

14.1.1-canary.39 - 2024-02-06

14.1.1-canary.38 - 2024-02-06

14.1.1-canary.37 - 2024-02-06

14.1.1-canary.36 - 2024-02-05

14.1.1-canary.35 - 2024-02-05

14.1.1-canary.27 - 2024-01-31

14.1.1-canary.26 - 2024-01-31

14.1.1-canary.25 - 2024-01-31

14.1.1-canary.24 - 2024-01-30

14.1.1-canary.23 - 2024-01-30

14.1.1-canary.22 - 2024-01-30

14.1.1-canary.21 - 2024-01-29

14.1.1-canary.20 - 2024-01-29

14.1.1-canary.19 - 2024-01-29

14.1.1-canary.18 - 2024-01-28

14.1.1-canary.17 - 2024-01-27

14.1.1-canary.16 - 2024-01-27

14.1.1-canary.15 - 2024-01-26

14.1.1-canary.14 - 2024-01-26

14.1.1-canary.13 - 2024-01-26

14.1.1-canary.12 - 2024-01-26

14.1.1-canary.10 - 2024-01-24

14.1.1-canary.9 - 2024-01-24

14.1.1-canary.7 - 2024-01-23

14.1.1-canary.6 - 2024-01-22

14.1.1-canary.5 - 2024-01-21

14.1.1-canary.4 - 2024-01-20

14.1.1-canary.3 - 2024-01-20

14.1.1-canary.2 - 2024-01-19

14.1.1-canary.1 - 2024-01-19

14.1.1-canary.0 - 2024-01-18

14.1.0 - 2024-01-18

14.0.5-canary.68 - 2024-01-18

14.0.5-canary.67 - 2024-01-18

14.0.5-canary.66 - 2024-01-18

14.0.5-canary.65 - 2024-01-17

14.0.5-canary.64 - 2024-01-17

14.0.5-canary.63 - 2024-01-17

14.0.5-canary.62 - 2024-01-17

14.0.5-canary.61 - 2024-01-17

14.0.5-canary.60 - 2024-01-16

14.0.5-canary.59 - 2024-01-15

14.0.5-canary.58 - 2024-01-14

14.0.5-canary.57 - 2024-01-14

14.0.5-canary.56 - 2024-01-13

14.0.5-canary.55 - 2024-01-12

14.0.5-canary.54 - 2024-01-12

14.0.5-canary.53 - 2024-01-11

14.0.5-canary.52 - 2024-01-11

14.0.5-canary.51 - 2024-01-11

14.0.5-canary.50 - 2024-01-10

14.0.5-canary.49 - 2024-01-10

14.0.5-canary.48 - 2024-01-10

14.0.5-canary.47 - 2024-01-10

14.0.5-canary.46 - 2024-01-09

14.0.5-canary.45 - 2024-01-08

14.0.5-canary.44 - 2024-01-08

14.0.5-canary.43 - 2024-01-07

14.0.5-canary.42 - 2024-01-06

14.0.5-canary.41 - 2024-01-05

14.0.5-canary.40 - 2024-01-05

14.0.5-canary.39 - 2024-01-04

14.0.5-canary.38 - 2024-01-04

14.0.5-canary.37 - 2024-01-04

14.0.5-canary.36 - 2024-01-03

14.0.5-canary.35 - 2024-01-02

14.0.5-canary.34 - 2024-01-01

14.0.5-canary.33 - 2023-12-31

14.0.5-canary.32 - 2023-12-30

14.0.5-canary.31 - 2023-12-29

14.0.5-canary.30 - 2023-12-29

14.0.5-canary.29 - 2023-12-27

14.0.5-canary.28 - 2023-12-26

14.0.5-canary.27 - 2023-12-25

14.0.5-canary.26 - 2023-12-24

14.0.5-canary.25 - 2023-12-23

14.0.5-canary.24 - 2023-12-22

14.0.5-canary.23 - 2023-12-21

14.0.5-canary.22 - 2023-12-20

14.0.5-canary.21 - 2023-12-20

14.0.5-canary.20 - 2023-12-20

14.0.5-canary.19 - 2023-12-19

14.0.5-canary.18 - 2023-12-18

14.0.5-canary.17 - 2023-12-17

14.0.5-canary.16 - 2023-12-16

14.0.5-canary.14 - 2023-12-15

14.0.5-canary.13 - 2023-12-14

14.0.5-canary.12 - 2023-12-13

14.0.5-canary.11 - 2023-12-13

14.0.5-canary.10 - 2023-12-13

14.0.5-canary.9 - 2023-12-13

14.0.5-canary.8 - 2023-12-12

14.0.5-canary.7 - 2023-12-11

14.0.5-canary.6 - 2023-12-11

14.0.5-canary.5 - 2023-12-09

14.0.5-canary.4 - 2023-12-08

14.0.5-canary.3 - 2023-12-08

14.0.5-canary.2 - 2023-12-08

14.0.5-canary.1 - 2023-12-08

14.0.5-canary.0 - 2023-12-07

14.0.4 - 2023-12-07

    from next GitHub release notes

Commit messages

Package name: next

f1fc357 v14.1.4
e6a117b (backport) Update React from 60a927d04 to 4b84f1161 (#63476)
c227315 update assertion due to stack trace change
3aae252 test: switch order of tests to avoid flakniess (#63482)
4804982 fix broken create-next-app tests (#63019)
81114f3 fix revalidation issue with route handlers (#63213)
944a84c ensure mpa navigations to the same URL work after restoring from bfcache (#63155)
21e11f1 Ensure PromiseLikeOfReactNode is not included in .d.ts files (#63185)
531cdb5 Fix metadata url cases should not append with trailing slash (#63050)
a3707f5 feat: add `deploymentId` config (#63198)
f904dcd fix: bump `<EMAIL_ADDRESS>(#61538)
9e99811 fix `x-forwarded-port` header (#63303)
5b16b59 fix: x-forwarded-port header is 'undefined' when no port in url (#60484)
fc38ee1 v14.1.3
85a5c4d fix type
4b059bc Upgrade to latest @ edge-runtime packages (#62955)
b10a610 Fix output: export with custom distDir (#62064)
960b738 Migrate locale redirect handling to router-server (#62606)
2f210d4 update release workflow
f564dee v14.1.2
a85519e Fix sitemap generateSitemaps support for string id (#61088)
0a2d775 Fix: generateSitemaps in production giving 404 (#62212)
400b57c Fix redirect under suspense boundary with basePath (#62597)
714020f fix: Add stricter check for "use server" exports (#62821)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Its broken with next 14. We dont really need to keep this up to date anyway 😓


Module gke-cluster misses master_global_access_config option

The module cke-cluster misses the option private_cluster_config.master_global_access_config which allows to reach private master endpoints from other regions from where the masters live

Thanks for flagging, we did not yet update the module. Want to send a PR?


Values provided for authorization endpoint and token endpoint is wrong . Please

[Enter feedback here]

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

ID: 836ec1be-7675-d0f1-c861-0520dc3ea01e
Version Independent ID: c6a2a6f6-57fd-20ae-36f7-b6db1987ebe5
Content: Request an access token - Azure Active Directory B2C
Content Source: articles/active-directory-b2c/access-tokens.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@doctorRush Thank you for pointing this out. We will review and have this rectified.

@doctorRush  As this issue seems to be duplicate of #65218 , we will close this issue at this point and work on the other related issue. #65218


Add deploy script for mainnet

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


pantheon: manage user session with systemd

(Edited on 2 Dec, 2021)
Should work™ (successfully reaches<EMAIL_ADDRESS>pantheon-session-x11.target and gala-x11.target and desktop launches for me)
Drafting to see if there are further actions from upstream and we probably don't want to ship this in NixOS 21.11 and 22.05 unless tested by upstream (https://github.com/NixOS/nixpkgs/issues/101817#issuecomment-933261317).
Motivation for this change
Hope this fixes #101817

https://github.com/elementary/session-settings/pull/55
https://github.com/elementary/gala/pull/1255
https://github.com/elementary/gala/pull/1256

Things done

Built on platform(s)

[x] x86_64-linux

[x] Fits CONTRIBUTING.md.

Is this ready to test? Asking because it's marked as draft.

Is this ready to test?

Yes, I am using this on my physical machine.

@ofborg test pantheon

This seem to work.
Tested:

booting several times
login
lock screen
suspend, resume
start applications

I updated the PR description. I guess I should close this for now to avoid confusions, I don't plan to merge this for now. I will re-open this or reflect this changes in other PR when ready.

I noticed today that i can't always click, for example moving windows or make a different video active by clicking on it don't work. Also, hotkeys for screenshot does not work anymore. Screenshots using the app work. Nothing related in logs.

I can reproduce the keyboard keys issue but not other yet. I guess it will be nice to report the issue upstream as I don't know how to deal with these downstream currently. Anyway I am tracking this in https://github.com/NixOS/nixpkgs/projects/21#card-73471036 so we can make sure we revisit this when doing Pantheon 7 update.

The described problems are actually not related to systemd session. They also occur with latest stable NixOS 21.11.334139.1bd4bbd49be.

For me, at least the keyboard keys issue happens only with --builtin removed...
Filechooser portal should work fine on chromium and for your information the filechooser has been redesigned in Pantheon 6.0.4.

@ofborg test pantheon

@ofborg test pantheon

(Let's see when gnome-session!93 will go live :upside_down_face:)

https://github.com/elementary/session-settings/pull/73 has been merged, I would like to land this soon


Setting Maintenance Expectations

I would like to set some clear expectations for those using or looking to use this project. This is based on my experience with it as a maintainer over the last 4 months.
This project - the only viable open source video solution for RN outside of Expo - is severely under resourced. Despite many good intentions, it is currently unsustainable. It has exhausted every person who tried to maintain it or contribute over the past few years because with very few exceptions, the community has failed to contribute back.
To demonstrate - a few months ago we put a governance system in place where most decisions are made democratically. This means a PR can get merged with approval from 1-3 people very quickly. Reviews are open to anyone, not just maintainers. However, in contrast to the dozens or people who show up to complain, no one has volunteered a review. We have 8 open pull requests that are almost ready to be merged and all waiting for someone to validate them.
IF YOU WANT TO HELP please don't just reply to this issue and make promises because that's pointless. Instead start actually contributing:

Test out a pull request and either post feedback or approve it. You don't even need to understand the code - you just need to run it in a real app and confirm it is working as expected and doesn't break anything.
Help triage an issue. There are over 30 open issues waiting for someone to confirm them: https://github.com/react-native-video/react-native-video/issues?q=is%3Aissue+is%3Aopen+label%3A"triage+needed". Again, you just need to spend some time reproducing it and report back if the issue is real.
Answer some questions. Most issues are closed after a few months because no one bothers to chime in. If you are using this module, you must have figured out how to overcome some problems - why not share that knowledge with others?
Help with housekeeping. Review issues and pull requests and try to make sense of them. Look for similar issues and link them. Ask people for more information to save time on follow ups. I was able to help for 4 months without having any understanding of native code by simply contributing to the process and helping with housekeeping.
Test the latest v6 alpha release and master and report back of any problems - or that it's working well! So far only a handful of people reported anything at all.

If you show up asking for help without contributing something back, you are the problem.  If you only care about the one issue you are having, you are making it worse and hurting those trying to maintain it.

Unfortunately, the project I was working on that used react-native-video is no longer in active development and I cannot justify spending more time on this module. I will stick around to help with a transition if someone else steps forward but will no longer work on issues or release new versions. I am happy to give admin access to those who show up and put real effort.
I'd like to sincerely thank @cobarx, @freeboub, @nickfujita, and @armadilio3 for their significant efforts and contributions over the past 4 months. Any progress made in the last few months has only been achieved because of their contributions - I was just the admin.

It's sad.

Thank you so much on your help with this module over the past months @hueniverse !
@freeboub
Also, sorry I haven't responded to the latest tags in some of the issues, as I'm in the middle of a role transition. So unfortunately I'm also no longer working on a project actively using this module, so will not be able to dedicate time here.
Please contact @cobarx for assistance, as his team is still working on the project which is actively making improvements to this repo ✌🏼

I am working on a two project which heavily depends on video module.
Now I have some ideas to keep it alive.
First thing I did was to start upgrading examples, specifically migrating to RNTA for better testing and development.

let close this issue and follow up in the other pin ticket and in discussion section. thank you @hueniverse


Coverter magic

If i use .ckpt model that:
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte

Okay. But i have diff folder after the launch attempt! Just use a
--hf_model_id=\"D:\\Neirotrash\\StableDiffusionUI-Shark-AMD\\data\\models\\anything-v4.0\"

....
Saved vmfb in D:\Neirotrash\StableDiffusionUI-Shark-AMD\data\models\vae1_64_384_384_fp16_D_Neirotrash_StableDiffusionUI_Shark_AMD_data_models_anything_v4_0_vulkan-00000000-0300-0000-0000-000000000000.vmfb.
0it [00:00, ?it/s]
1it [00:01,  1.41s/it]
2it [00:02,  1.39s/it]
3it [00:04,  1.38s/it]
4it [00:05,  1.38s/it]
5it [00:06,  1.38s/it]
6it [00:08,  1.37s/it]
7it [00:09,  1.37s/it]
8it [00:11,  1.37s/it]
9it [00:12,  1.37s/it]
10it [00:13,  1.37s/it]
11it [00:15,  1.37s/it]
12it [00:16,  1.37s/it]
13it [00:17,  1.37s/it]
14it [00:19,  1.37s/it]
15it [00:20,  1.37s/it]
16it [00:21,  1.37s/it]
17it [00:23,  1.37s/it]
18it [00:24,  1.37s/it]
19it [00:26,  1.37s/it]
20it [00:27,  1.37s/it]
21it [00:28,  1.37s/it]
22it [00:30,  1.37s/it]
23it [00:31,  1.37s/it]
24it [00:32,  1.37s/it]
25it [00:34,  1.37s/it]
25it [00:34,  1.37s/it]
  0%|          | 0/1 [00:00<?, ?it/s]
100%|##########| 1/1 [00:02<00:00,  2.04s/it]
100%|##########| 1/1 [00:02<00:00,  2.04s/it]

Magic!

Hi @ForserX
Can you please give a detailed log using along with the exact run command you're using?
Use --enable_stack_trace flag in your run command.
The magic is expected when you pass the extracted checkpoint data's location to hf_model_id - no issues here. The issue seems to be at the ckpt_loc - will need the detailed log along with the run command to investigate.


'Request failed with status code 500' when trying to 'Run sample tests' or 'Attempt'

A few things to check first:
Is the issue you are filing related to a specific kata?
If so then please file an issue on the discourse page of the kata. You can do so by creating a comment and marking it as an issue. Only issues related to site functionality should be filed here.
Is the issue you are filing related to how a specific language behaves when being executed?
If so then it will likely be better to file the issue on our github.com/Codewars/codewars-runner-cli/issues repo, which is where we have our open source code execution functionality. You also may want to look into forking that repo and fixing the issue yourself if you have the means.
Otherwise delete all of this text and file your issue. Make sure to include steps to reproduce the issue, including which pages/kata you found the issue on, and your Codewars username if its related to your account.

it's ok on the "other" site : https://preview.codewars.com

Thanks for help!

Closing this as the outage is resolved. Sorry for the inconvenience.


Add possibility to set true color for layer

Hello, I wanted to be able to set any color for a layer, and as dxf supports true color, I added support for it in your lib.

Hi Jonathan,
Great, thanks.
Would you mind to add an example, e.g. "true_color.js" to the example folder?
Regards, Ognjen

Ok done, I also added a setTrueColor on the Drawing class that acts on the active layer as it seems to be the standard way to do things in the library.


Closes: #1

Usernames must begin with a letter to be valid
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!

This is a fantastic update!


HDFS-14750. RBF: Support dynamic handler allocation in routers

Description of PR
Add a DynamicRouterRpcFairnessPolicyController class that resizes permit capacity periodically based on traffic to namespaces.
How was this patch tested?
Unit tests and local deployment.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

@kokonguyen191 Thanks. It's a good feature.
@fengnanli could you please review this PR?

It seems that we can not know how many handlers are assigned to every nameservice after resizing. It's better to update the configuration, right?

It seems that we can not know how many handlers are assigned to every nameservice after resizing. It's better to update the configuration or add metrics, right?

It's already in getAvailableHandlerOnPerNs?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 26s

trunk passed

+1 :green_heart:
compile
0m 53s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
0m 54s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 43s

trunk passed

+1 :green_heart:
shadedclient
23m 47s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 41s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project/hadoop-hdfs-rbf: The patch generated 9 new + 1 unchanged - 0 fixed = 10 total (was 1)

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

-1 :x:
javadoc
0m 38s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

+1 :green_heart:
javadoc
0m 55s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 27s

the patch passed

+1 :green_heart:
shadedclient
23m 34s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
30m 44s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

135m 49s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.security.TestRouterSecurityManager

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4199

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 7e1ed08abaf8 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0f020905d0189fd612b81f9463856ae595c570ec

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/2/testReport/

Max. process+thread count
2225 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 16s

trunk passed

+1 :green_heart:
compile
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 58s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 51s

trunk passed

+1 :green_heart:
mvnsite
1m  0s

trunk passed

+1 :green_heart:
javadoc
1m  6s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 13s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 52s

trunk passed

+1 :green_heart:
shadedclient
24m  9s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 44s

the patch passed

+1 :green_heart:
compile
0m 47s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 47s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 27s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project/hadoop-hdfs-rbf: The patch generated 3 new + 2 unchanged - 0 fixed = 5 total (was 2)

+1 :green_heart:
mvnsite
0m 45s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 44s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
1m 37s
/new-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.html
hadoop-hdfs-project/hadoop-hdfs-rbf generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
shadedclient
22m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
23m 34s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

130m 28s

Reason
Tests

SpotBugs
module:hadoop-hdfs-project/hadoop-hdfs-rbf

org.apache.hadoop.hdfs.server.federation.router.RBFConfigKeys.DFS_ROUTER_FAIR_MINIMUM_HANDLER_COUNT_DEFAULT isn't final but should be  At RBFConfigKeys.java:be  At RBFConfigKeys.java:[line 359]

Failed junit tests
hadoop.hdfs.server.federation.security.TestRouterSecurityManager

hadoop.hdfs.server.federation.router.TestRBFConfigFields

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4199

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 4da96cee138f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0f83aa37fc8e24752323ffb701fac94964e4c096

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/4/testReport/

Max. process+thread count
2753 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 58s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 23s

trunk passed

+1 :green_heart:
compile
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
0m 54s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m  7s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 40s

trunk passed

+1 :green_heart:
shadedclient
24m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 41s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 23s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project/hadoop-hdfs-rbf: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
mvnsite
0m 40s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 38s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 56s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 27s

the patch passed

+1 :green_heart:
shadedclient
23m 22s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
32m 10s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

138m 31s

Reason
Tests

Failed junit tests
hadoop.fs.contract.router.web.TestRouterWebHDFSContractCreate

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4199

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 7c6c5c98801b 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 60f7b03ce490200cfeafec292c1138b96b319cff

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/5/testReport/

Max. process+thread count
2221 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Failed test is not related. For the issue with total number of permits not staying constant, it will be initial total handler count <= total number of permits <= initial total handler count + number of namespaces, which seems to me to be an acceptable range of error for performance purposes.

@kokonguyen191 Thanks for updates, please take a look at the checkstyle and can raise a new ticket to add document referring to static controller.
If no other comments, I will merge it.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 12s

trunk passed

+1 :green_heart:
compile
0m 55s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 42s

trunk passed

+1 :green_heart:
mvnsite
0m 54s

trunk passed

+1 :green_heart:
javadoc
1m  0s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m  7s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 47s

trunk passed

+1 :green_heart:
shadedclient
24m 11s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 41s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 22s

the patch passed

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 38s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 27s

the patch passed

+1 :green_heart:
shadedclient
23m 34s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
30m 43s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

137m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4199

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 6eb815a6f090 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8f31e0806dc88220c534a15bf74cfd599c6dbeca

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/6/testReport/

Max. process+thread count
2223 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4199/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Add list option for all messages.

Task

[ ] Add list option for all messages.

Before
message: "test\ntest"

After
message:
- "test"
- "test"

Also added to 3.10.0 wiki which messages are supported


App not loading on M365 android app, no changes were done on tab or app

Asking on behalf of partner Jira, tab is not loading on Android M365 app without making any changes to the app. Please reach out to<EMAIL_ADDRESS>for more details on the problem

@ktcodebite - Thanks for reporting your issue. Could you please share the error which you are getting while loading the tab?
Are you trying to add static tab or configurable tab?

@ktcodebite - We have followed steps which is mentioned in below document for Installing Microsoft 365 apps in test environment
https://learn.microsoft.com/en-us/microsoftteams/platform/m365-apps/prerequisites#mobile
Tested with below manifest. The static tab is loading fine at our end.
manifest.zip

We have tested this on Android 12 and Microsoft 365 version 1.0.1(16.0.16227.20032) by joining the beta program.
Could you please follow the document for installing Microsoft 365 apps in test environment and check again.

Hi @Nivedipa-MSFT
the content context is working without any issues, but dialog.open() called from the tab is not working at all, and task module is not opened...

@vbatr - Is this duplicate of issue https://github.com/MicrosoftDocs/msteams-docs/issues/8234?

@Wajeed-msft nope, that is two separate issues. #8234 is failing on trying to get auth token (await microsoftTeams.authentication.getAuthToken({ silent: true }) ) in Outlook desktop client for task modules. But if we do an upgrade to 2.8.0+ version of the library we have another issue with the same symptoms like in current case
#8235 is related to dialog.open() on Microsoft 365 Androind app (for the lib v 2.6.0 +)

Thanks for clarification.
@Nivedipa-MSFT - could you please test dialog.open() on Microsoft 365 Android app using SDK v2.6.0?

@ktcodebite - We have tested dialog.open() on Android 12 and Microsoft 365 version 1.0.1(16.0.16227.20032) by joining the beta program. using SDK v2.6.0.
https://user-images.githubusercontent.com/92150070/222714315-2e6cb2b0-0c4f-4e62-9e49-2af4e9a626cd.mp4
We are able to repro your issue. We have raised a bug for the same. We will let you know once we have any updates on it.

@ktcodebite - We got an update from engineering team saying that dailog.open() is not currently supported in Android mobile.


docs: improve postTargets option behavior documentation

Since the postTargets option uses runExecutor under the hood, it would be nice to indicate the expected behavior to the users. runExecutor is not the same as running the target on the Nx CLI; it calls the target as it, without running any dependency or taking Nx Cache into account.
That behavior is not documented, but according to the Nx Team that's the expected behavior.

runExecutor runs a specific executor. It doesn't spawn the task orchestrator or any of that, so dependencies are not ran and caching is not considered.

Thanks @dianjuar!


⚠ Bofrost.at has degraded performance

In 451ffae, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1801 ms

Resolved: Bofrost.at performance has improved in b72ae0b after 6 minutes.


Llama.cpp running twice when it is run alone

siddhesh@desktop:~/Desktop$ langflow
[18:57:38] INFO     [18:57:38] - INFO - Logger set up with log      logger.py:28
level: 20(info)
INFO     [18:57:38] - INFO - Log file: logs/langflow.log logger.py:30
[2023-04-26 18:57:38 +0530] [38894] [INFO] Starting gunicorn 20.1.0
[2023-04-26 18:57:38 +0530] [38894] [INFO] Listening at: http://<IP_ADDRESS>:7860 (38894)
[2023-04-26 18:57:38 +0530] [38894] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2023-04-26 18:57:38 +0530] [38906] [INFO] Booting worker with pid: 38906
[2023-04-26 18:57:38 +0530] [38906] [INFO] Started server process [38906]
[2023-04-26 18:57:38 +0530] [38906] [INFO] Waiting for application startup.
[2023-04-26 18:57:38 +0530] [38906] [INFO] Application startup complete.
llama_model_load: loading model from '/home/siddhesh/Desktop/vicuna.bin' - please wait ...
llama_model_load: n_vocab = 32001
llama_model_load: n_ctx   = 512
llama_model_load: n_embd  = 4096
llama_model_load: n_mult  = 256
llama_model_load: n_head  = 32
llama_model_load: n_layer = 32
llama_model_load: n_rot   = 128
llama_model_load: f16     = 2
llama_model_load: n_ff    = 11008
llama_model_load: n_parts = 1
llama_model_load: type    = 1
llama_model_load: ggml map size = 4017.70 MB
llama_model_load: ggml ctx size =  81.25 KB
llama_model_load: mem required  = 5809.78 MB (+ 2052.00 MB per state)
llama_model_load: loading tensors from '/home/siddhesh/Desktop/vicuna.bin'
llama_model_load: model size =  4017.27 MB / num tensors = 291
llama_init_from_file: kv self size  =  512.00 MB
AVX = 1 | AVX2 = 1 | AVX512 = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 0 | SSE3 = 1 | VSX = 0 |
llama_model_load: loading model from '/home/siddhesh/Desktop/vicuna.bin' - please wait ...
llama_model_load: n_vocab = 32001
llama_model_load: n_ctx   = 512
llama_model_load: n_embd  = 4096
llama_model_load: n_mult  = 256
llama_model_load: n_head  = 32
llama_model_load: n_layer = 32
llama_model_load: n_rot   = 128
llama_model_load: f16     = 2
llama_model_load: n_ff    = 11008
llama_model_load: n_parts = 1
llama_model_load: type    = 1
llama_model_load: ggml map size = 4017.70 MB
llama_model_load: ggml ctx size =  81.25 KB
llama_model_load: mem required  = 5809.78 MB (+ 2052.00 MB per state)
llama_model_load: loading tensors from '/home/siddhesh/Desktop/vicuna.bin'
llama_model_load: model size =  4017.27 MB / num tensors = 291
llama_init_from_file: kv self size  =  512.00 MB
AVX = 1 | AVX2 = 1 | AVX512 = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 0 | SSE3 = 1 | VSX = 0 |
[2023-04-26 18:59:20 +0530] [38894] [INFO] Handling signal: winch
llama_print_timings:        load time =  1667.92 ms
llama_print_timings:      sample time =    48.17 ms /   128 runs   (    0.38 ms per run)
llama_print_timings: prompt eval time =  1667.88 ms /     8 tokens (  208.48 ms per token)
llama_print_timings:        eval time = 16544.15 ms /   127 runs   (  130.27 ms per run)
llama_print_timings:       total time = 18273.72 ms
It looks like it tries to load the first time and is unsuccessful but runs the second time. This happens everytime.

Interesting. I haven't been able to test it thoroughly yet. Could you elaborate? When does that happen?

Interesting. I haven't been able to test it thoroughly yet. Could you elaborate? When does that happen?

Hi,
I have this problem as well, just by running llama.cpp. I don't think it's a langflow issue.


Change loaded font behavior

Hi, I took liberty with two main things:

The scope for Helmet #13
The use of attribute instead of classname

Helmet only prints classes to its target. This means that it can overwrite other classes that can be there. Using attributes makes sure that nothing is overwritten.

New CSS use:
html[wf-helvetica-now-display=loaded]: {}

Also, since it's already a breaking change, I felt that we might not need an option to choose the scope from body or html

I backtracked a little bit...
I think adding the classes without Helmet is a better solution, and that way it's not a breaking change.

Implemented the scope option

I backtracked a little bit...
I think adding the classes without Helmet is a better solution, and that way it's not a breaking change.

Implemented the scope option

Hi @fcisio , thanks for your contribution. I have reviewed the PR and I have some comments. I had made some modifications and pushed the changes, hope you don't mind. This PR has provided a good idea and a solid foundation for the improvements that I've made.
I like the idea of replacing Helmet. However, I've had to refactor this to a custom hook since the component didn't return anything anymore and had to create a separate wrapper component that calls the hook. This structure makes more sense for this case.
I've refactored the className to classList since it handles adding classnames much better - avoids duplicated classNames, leading and trailing whitespaces, etc. Docs for the classList: https://developer.mozilla.org/en-US/docs/Web/API/Element/classList
Check out the changes and let me know if they work for you. If everything is okay, I'll plan the release early next week after I give it one more look.

Hi @fcisio , thanks for your contribution. I have reviewed the PR and I have some comments. I had made some modifications and pushed the changes, hope you don't mind. This PR has provided a good idea and a solid foundation for the improvements that I've made.
I like the idea of replacing Helmet. However, I've had to refactor this to a custom hook since the component didn't return anything anymore and had to create a separate wrapper component that calls the hook. This structure makes more sense for this case.
I've refactored the className to classList since it handles adding classnames much better - avoids duplicated classNames, leading and trailing whitespaces, etc. Docs for the classList: https://developer.mozilla.org/en-US/docs/Web/API/Element/classList
Check out the changes and let me know if they work for you. If everything is okay, I'll plan the release early next week after I give it one more look.

I love the refactoring you did, looks awesome!
Tested it on my end, and it works perfectly.
I pushed a new commit, simply adding a "wf-all--loaded" class to allow for simple CSS selectors when we don't need specificity (while we're at it).
Thanks!

I love the refactoring you did, looks awesome!
Tested it on my end, and it works perfectly.
I pushed a new commit, simply adding a "wf-all--loaded" class to allow for simple CSS selectors when we don't need specificity (while we're at it).
Thanks!

I don't think the final class name for all loaded fonts is needed since the individual class names can be concatenated in a CSS selector for the same effect. If I see a valid use-case, I'll consider implementing it. At this point, I'm not sure if there is any.
If you revert that recent part of the PR today, I'll finalize it and merge it tomorrow.
I appreciate the contribution. Thank you!

I don't think the final class name for all loaded fonts is needed since the individual class names can be concatenated in a CSS selector for the same effect. If I see a valid use-case, I'll consider implementing it. At this point, I'm not sure if there is any.
If you revert that recent part of the PR today, I'll finalize it and merge it tomorrow.
I appreciate the contribution. Thank you!

Hey @codeAdrian ,
Are we still looking into releasing this soon?
Thanks

Hey @codeAdrian ,
Are we still looking into releasing this soon?
Thanks


improve guidance on response (status code) documentation

The guidance on error documentation is partially contradictory. On one side API designers are required to document all errors, on the other side they are allowed to omit technical errors as well as functional errors that do not differ from the default semantic.
To improve the guidance a default pattern is introduced that that solved this conflict and the documentation is extended to successful status codes.

:+1:

:+1:


ci: Remove build.gradle.ktx from .releaserc.

Changes introduced in #998 and #1010 required that the release workflow match on a file named build.gradle.kts. These changes were done as a way to simplify managing multiple Android repos in our org. Unfortunately, it looks like semantic release will fail if one of the enumerated files is not found and so it is necessary to create a separate .releaserc for Groovy repos and another .releaserc for Gradle Kotlin DSL (will handle that in the .github repo separately).
Fixes #1012 🦕

Also, I think https://github.com/googlemaps/android-maps-utils/pull/1014 can be closed as a duplicate of this PR?


Handling duplicate records

We are using the latest build to read messages from a multi-shard Kinesis stream using workers running across multiple EC2 instances and write them to S3. In this context, please see the following doc:
http://docs.aws.amazon.com/kinesis/latest/dev/kinesis-record-processor-duplicates.html
It talks about cases where we can end up with reading duplicate records from the stream.  The S3Emitter uses the buffer.firstSeqNumber and buffer.lastSeqNumber to determine the S3 filename. In the case of retries, this approach might not guarantee duplicate removal as the buffer can be filled differently with a different size or count. The approach suggested by the doc does not work in the case of S3Emitter as there is no way to control the exact number of records in the buffer (due to the emit being based on count, time OR size). Any thoughts on how we can overcome this limitation?
Thanks.

Any thoughts/updates on this?

Would it be possible for you to configure the time and size thresholds to large enough values where the emit is triggered by counts alone?
Sincerely,
Gaurav

Hi Gaurav,
Thanks for the response. Even if we configure the time & size thresholds in such a way that only the counts matter, the fact that the counts are not always exact would still be a problem. That is, configuring a value of "n" for count does not guarantee only "n" records are buffered for emit and can always go slightly higher depending on the processRecords call. Hence this strategy does not always help, right?

I'm not convinced you need the fixed record count. Let's say you're consuming from a relatively slow-moving stream and you get, say, 15 records (number 10001 - 10015). You write these out into a file with the start ID in its name (my-data-10001) then you fail to checkpoint because you crash. When you restart (or another worker picks up this shard), it will also get a batch starting at 10001. It may get the same 15 records or it may get a few more. Let's say it now gets 17 records (10001 - 10017). It (over-)writes these to the my-data-10001 file. That file has all the data it had previously, plus a bit more. We now checkpoint at 10017, and the next batch starts at 10018 ready to go into the next file.
I can't see the need for the fixed record count.
What I can see the need for that isn't exposed from the connector library, is the shard ID. Without writing my own KinesisConnectorRecordProcessorFactory and having it return a subclass of KinesisConnectorRecordProcessor which overrides initialize and captures its own copy of shardId, I can't see any way of accessing the shard ID. And even then, I'm not sure how you'd get it to the emitter.

What happens when the order of these operations are reversed - that is, we got 17 records the first time, but only 15 the next time (assuming we set recordCount=15)? In that case, we will have two duplicate records in S3.

Why would you get fewer records on the subsequent call? And even if you did, you'd replace your 17 record file with a 15 record file and then your next call would presumably include the missing two records so they'd go into the next file. In any case, you have to cope with duplicates in the S3 files anyway because if you're using the Kinesis Client Library (which the Connector Library does), it can (briefly) have multiple workers subscribed to the same shards. So this whole scheme is just an exercise trying to reduce the number of duplicates, not completely eliminating them.

Why would you get fewer records on the subsequent call?

I did not mean the call to processRecords here, but the number of records that are in the buffer when the file is emitted to S3. Since the "recordCount" variable is not exact, there is a chance for the buffer to hold less or more records depending on when the emit was triggered.

you have to cope with duplicates in the S3 files anyway because if you're using the Kinesis Client Library (which the Connector Library does), it can (briefly) have multiple workers subscribed to the same shards. So this whole scheme is just an exercise trying to reduce the number of duplicates, not completely eliminating them

Does this mean the only way to ensure unique records is through mechanisms available in the consuming system (say an RDBMS)?

That's my belief, yes.


Attempt at new API with Lemminx

This is just an expositional diff, it should not be merged as I haven't taken versioning into account. See https://github.com/sublimelsp/LSP/pull/979

Is there anything of use here that isn't already on master?


ROX-17814: Show a simple vulnerability reports table

Description
This PR adds a simple version of the table to be used to display the reports. I added one report to the table to show an example of what will be displayed. The error icon in the "Last run status" column will display a tooltip with the error message. If, for some reason, no error message is populated then we'll use a generic error message. Also, note that we will be merging the report configuration with the last run report status and the report status to display in the table. I added types for each and a merged type as well

/retest-required

Bump @vjwilson @dvail


Move CosmosAuthorizationTokenResolver To Implementation

Move CosmosAuthorizationTokenResolver to implementation, and remove public setter of CosmosAuthorizationTokenResolver  from CosmosClientBuilder

PR merged into master.


14 2 1

Automation of 14-2-1 is complete, It is giving me the expected csv file and QA.html document. Please review it carefully as its my first time and I don't wat to mess anything. There is one confusion, the review form will be completed by me or the reviewer ?

Yes, as Atanaska says it's for the reviewer to do. I can do later this week.

The review form is to be completed by the reviewer, you just need to respond to any comments they may have :)

Thanks Atanaska

Yes, as Atanaska says it's for the reviewer to do. I can do later this week.

Thanks Micheal

Addressed the QA comment

Changes all made and approved. Well done Abhishek, you can click the green "merge pull request" button above.


ElectronicCats

Please, before reporting any issue

Make sure your board it's in good condition.
Make sure your PN7150 it's in good condition.
Verify that it really is a library problem and not a hardware problem.
Avoid to submit a GitHub issue for project troubleshooting.

Any feedback/suggestions should be discussed on the feedback section:

Just click on New Issue and select the correct category.

When reporting any issue, please try to provide all relevant information to help on its resolution.
Describe the bug
A clear and concise description of what the bug is.
The more detailed this is, the easier we can come up with a solution.
To Reproduce
Complete source code which can be used to reproduce the issue. Please try to be as generic as possible.
No extra code, extra hardware, etc.
If you think it is absolutely necessary to add this, mention in detail the connections in case it is necessary hardware and also indicate the part of code that was added and how it was added.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
To help us to understand your situation, we would like to ask you for the following additional information::

Which board are you using?
What Operating System and version are you using (e.g. Windows 11, macOS 12.0, Linux)?
In case you are using the Arduino IDE, What version of the Arduino IDE?
Did it work before?, If it worked before, what were the parameters that you modify?

Additional context
Add any other context about the problem here that you think will help us to solve your problem.

Ok

Prueba


refactor: tweak tab index saving

Move activeTab variable to auth model
Drop CupertinoTabController and use auth.activeTab as the single source of truth
Move setActiveTab method from build to account select handler
Comment GhGistsScreen temporarily since it is not submitted yet

move everything to auth.dart

Because we have to access the activeAccount.platform variable in auth model to save the tab index with corresponding.
It seems the provider lib has a ProxyProvider which could combine multiple providers, while we don't use it yet currently.


i2c_ll_stm32_v1: I2C_CR1:STOP is not cleared

Describe the bug
I am using STM32F415RG with I2C_2 (OLED), PWM (Buzzer), ADC, USART_1 (IrDA), SPI_1 (M-RAM).
There is a phenomenon that data of I2C is not output properly in random situation.
In this case, if i check the register of I2C, I2C_CR1:STOP bit is set.(0x00000200)
(gdb) x /10x 0x40005800
0x40005800:	0x00000200	0x0000002a	0x00000000	0x00000000
0x40005810:	0x00000078	0x00000000	0x00000000	0x00008023
0x40005820:	0x0000000d	0x00000000

In this case, the address of i2c_slave is not output when using i2c_write().
So only START Condtion and STOP Condtion are output.
From then on, this output is repeated.
The I2C_CR1:STOP bit is not cleared and remains set.

I look at the I2C_DR register, it contains 0x78, which is the slave address of SSD1306, 0x3C.
In my case OLED does not work because I2C write fails.
To Reproduce
I haven't found a definite condition to reproduce yet.
Currently, symptoms occur randomly.(< 10minutes)
Expected behavior
I2C should be written as usual.
Impact
In this case, no data can be written to the corresponding I2C channel.
Only START Condition and STOP Condtion are displayed.
Screenshots or console output
gdb step I2C waveform.
(gdb) continue
Continuing.

^C
Program received signal SIGINT, Interrupt.
k_cpu_idle () at /work/zephyrproject/zephyr/arch/arm/core/cpu_idle.S:139
139		bx lr
(gdb) x /10x 0x40005800
0x40005800:	0x00000000	0x0000002a	0x00000000	0x00000000
0x40005810:	0x00000000	0x00000000	0x00000000	0x00008023
0x40005820:	0x0000000d	0x00000000
(gdb) continue
Continuing.

^C
Program received signal SIGINT, Interrupt.
k_cpu_idle () at /work/zephyrproject/zephyr/arch/arm/core/cpu_idle.S:139
139		bx lr
(gdb) x /10x 0x40005800
0x40005800:	0x00000200	0x0000002a	0x00000000	0x00000000
0x40005810:	0x00000078	0x00000000	0x00000000	0x00008023
0x40005820:	0x0000000d	0x00000000
(gdb) set {int}0x40005800 = 0
(gdb) x /10x 0x40005800
0x40005800:	0x00000000	0x0000002a	0x00000000	0x00000000
0x40005810:	0x00000078	0x00000000	0x00000000	0x00008023
0x40005820:	0x0000000d	0x00000000
(gdb) continue
Continuing.

Environment (please complete the following information):

OS: Ubuntu 18.04
Toolchain (e.g Zephyr SDK, ...)
Commit SHA: 6a01db3be062be27454e98dd29497099ead9feb5

Additional context
What I don't understand in this state is that STOP Condtion is output, but I2C_CR1: STOP is not cleared.
In this situation, clear I2C_CR1 to work normally.
(gdb) x /10x 0x40005800
0x40005800:	0x00000200	0x0000002a	0x00000000	0x00000000
0x40005810:	0x00000078	0x00000000	0x00000000	0x00008023
0x40005820:	0x0000000d	0x00000000
(gdb) set {int}0x40005800 = 0

I2C_CR1:STOP needs to be checked but there are currently no LL driver functions to check.
So I tested with the following modifications.
This change has confirmed that I2C can recover from a problem.
--- drivers/i2c/i2c_ll_stm32_v1.c_ori	2019-08-09 21:06:59.036586163 +0900
+++ drivers/i2c/i2c_ll_stm32_v1.c	2019-08-09 21:04:57.184586163 +0900
@@ -326,6 +326,11 @@

ARG_UNUSED(next_msg_flags);

+	if (READ_BIT(i2c->CR1, I2C_CR1_STOP)) {
+		CLEAR_BIT(i2c->CR1, I2C_CR1_STOP);
+		return -EIO;
+	}
+
LL_I2C_AcknowledgeNextData(i2c, LL_I2C_ACK);

if (msg->flags & I2C_MSG_RESTART) {

I'm sorry I do not have enough English. :)
Thank you.

Hi @KwonTae-young,
could you please test with the latest master to check if the issue still exists?

@ydamigos
I will test and share the results as soon as possible.

@ydamigos
Some problems occurred when merging master's source to my current working source.
I will reopen this issue once the simple sample code is ready.


exit if request failed

this PR contains the following changes:

If the requests failed exit without going further
switching from %s to an f string

I have read the CLA Document and I hereby sign the CLA

recheck

recheck


[BUG] app_full limits the video vertical resolution to 1080

Describe the bug
app_full.py limits the video vertical resolution to 1080
Expected behaviour
Is it possible to enable the full resolution of the sensor?

Hardware :
Pi 5
HQ camera
Thanks!

Hi, yes, I suppose it's a bit inconsistent that the height is limited to 1080 but the width isn't limited to 1920. I suppose I could see an argument for doing both or neither!
But really, this code here is simply an example for you to look at, understand, and copy for your own purposes. We're not providing it as an application that does something terribly useful exactly as it is. So please feel free just to grab the file and do whatever you want with it. The line in question that you'd want to change would be this one.

Glad you're managing to figure it all out! Obviously you have the command line apps for (rpicam-still, rpicam-vid) for simple capture operations. There's also a nice little web UI to the camera that someone wrote here, that might make for a useful interface as well.


Email is case sensitive

When registering an email with<EMAIL_ADDRESS><EMAIL_ADDRESS>doesn't match when requesting a forgotten password

@martijnvdgrift Is there an easy fix for this?

@martijnvdgrift This also seems to be a problem when logging in.

@helloniklas I don't have a PR or anything for this since I've just been glancing at the project, but a way to fix this would be to always apply .toUpperCase() to the input email address and store it in the database in all caps. So, regardless of how the user inputs the email address, it's going to be converted to (and compared in) uppercase.
I believe there's a risk with this approach when it comes to internationalization, however, and some Unicode characters.


Files are not always written to mounted storages

Environment
Windows build number: 19041
Your Distribution version: Ubuntu 18.04
WSL version: 1

Steps to reproduce
Write a file to an external storage device.
Expected behavior
Files written to external storage devices should not be put in the internal storage.
Actual behavior
When a removable storage device is auto-mounted by WSL in /mnt (e.g. /mnt/d), writing to this drive may not actually write to it but to a temporary directory instead. When the device is removed and connected to another computer, changes are gone.
By going to WSL's folder (e.g. %LOCALAPPDATA%\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs) we can see the writed files (e.g. %LOCALAPPDATA%\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs\mnt\d\folder\some-written-file).
This does not happen all the time, but randomly. Also it never happens with /mnt/c.
The only solution I've found until now is to force re-mounting the device through a remount function:
remount () {
        sudo umount /mnt/${1:l} 2> /dev/null
        sudo mkdir /mnt/${1:l} 2> /dev/null
        sudo mount -t drvfs "${1:u}:" /mnt/${1:l}
}

remount d # or whatever drive we want

I'll try to see if this happens on WSL 2, but this will be harder to debug as the files are stored inside a virtual storage file.

If you can find the written files inside the WSL root directory, the drive was never mounted. WSL will not mount removable storage attached during a running session; you must do that yourself.

The problem is that the drives are mounted as I can read any file that is on these drives. I have an external hard drive of 5 TB and I can read any file from it without any problem, including ones taht are far larger than my internal drive ; but sometimes when I write to it the files go to WSL's /mnt/d directory instead of going to the external drive itselF.

The problem is that the drives are mounted as I can read any file that is on these drives. I have an external hard drive of 5 TB and I can read any file from it without any problem, including ones taht are far larger than my internal drive ; but sometimes when I write to it the files go to WSL's /mnt/d directory instead of going to the external drive itself.


The Error Manager should use its own config (ini) file

The Error Manager should use its own config (ini) file. That config file should contain a number of settings that the end-user (the LabVIEW programmer) can use to tailor the behaviour of the EM to their application. For example, the following settings should be used:

Whether the New Error Dialogue is Modal or Floating. Default: Floating.

Other settings:

The Default Behaviour for displaying Error Window. Options: Always, For new error, For new error code, Never
Log To File? Full Error Details, Error Codes Only, Do not log to file
Whether the Error Window is Modal, Floating, or Default


Callback functions parameter passing support

Thanks for the pull request, I will be able to look at it in the next few days 🙏


gotop: 1.2.9 -> 1.5.0

Motivation for this change
Package update
Things done

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

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

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

This builds for me on NixOS/aarch64 and Darwin, but my attempts on NixOS/x86_64-linux are causing my nix-daemon to spin at 100% cpu.

builds and runs fine on my local x86_64-linux box.

but my attempts on NixOS/x86_64-linux are causing my nix-daemon to spin at 100% cpu.

Since the build succeeded on two other machines, I'd suspect this is some local issue of your system.

I can no longer reproduce the issue on the two hosts I was testing on.


An exception dialog related to the SetFeature of Honeycomb Joystick during startup

Describe the bug
An exception dialog related to the SetFeature of Honeycomb Joystick
Not sure how to reproduce

Steps To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
A clear and concise description of what you actually happens.
Details

MobiFlight Version: [e.g. 8.2.0]
FlightSim: [e.g. MSFS2020]
AddOn: [e.g. Default Aircraft]

Additional context
Add any other context about the problem here.

Closed... not reproduced since refactoring


Client cannot see other clients

I have been trying to create a shooting system for a while now and have run into an odd but completely game-breaking bug. When I call NetworkManager.Singleton.ConnectedClients, the only client on the Dictionary is the local client.
For testing purposes, I added a GUI Button that would print the ConnectedClients whenever it was clicked instead of it being only printed on NetworkStart. When I clicked it for the client, the same thing happened. It only showed that the ConnectedClients list had only the local player, but when I clicked it for the host, it showed both the host and the connected clients. This is a serious bug...
I also tried testing it on two different versions of Unity and I get the same result.
To Reproduce

Set up the "Your First Networked Game 'Hello World'" and the "Building on 'Hello World'" in the mlapi documentation.
Attach this script to the player: https://gist.github.com/PutterBeanut/275e1380424bb0c8e7cc76365aed55cf
Build an instance of the game and set it as the host, then run the game in the Unity editor as a client.

Actual outcome
There should be the ID of the host and the client, but there is only the ID of the client that gets printed.
Expected outcome
Both the host and client IDs should be printed to console
Environment (please complete the following information):

OS: Windows 10
Unity Version: 2021.1.7f1 & 2020.3.9f1
MLAPI Version: 0.1.0

For the record, this is by design. A client does not see other clients or the host in the connected clients dictionary.


custom export csv folder location

Is there a way to provide the destination folder for the csv to be exported using export csv option.

I'm not sure whether we can control the download path via blob, but this feature is also minor to me, I think I'll not support this feature in near future, but PR is welcome 👍

Hi @AllenFang. I am using react-bootstrap-table in a project and I need the above mentioned feature in the table. So I am interested to work on this. We can add this feature later on to react-bootstrap-table2 as well.

@ananthshenoy  PR is welcome for react-bootstrap-table, thanks