minifab netup doesn't restart all(?)

I have a network (with my own spec.yaml) with 4 Orgs with 2 peers each. When I start it for the first time (even installing my chaincode succesfully) I have no problems. I can even start my apiserver.js through a gateway with and Admin.id identity. But if I turn down (minifab down) the network and then turn it up (minifab netup, according to the docs), I have some errors with calling the chaincode with my apiserver. However, with a minifab cleanup and starting all again i resolve the problem, but i wonder if there's a way or something I miss in order to just turn the network down (without cleanup).
Here are the logs of all above:
minifab netup,create,join,anchorupdate -o org1.example.com -l node -s couchdb -e true

Using spec file: /home/pupi04/mywork/spec.yaml
Minifab Execution Context:
FABRIC_RELEASE=2.3.0
CHANNEL_NAME=mychannel
PEER_DATABASE_TYPE=couchdb
CHAINCODE_LANGUAGE=node
CHAINCODE_NAME=simple
CHAINCODE_VERSION=1.0
CHAINCODE_INIT_REQUIRED=true
CHAINCODE_PARAMETERS="init","a","200","b","300"
CHAINCODE_PRIVATE=false
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=newest
EXPOSE_ENDPOINTS=true
CURRENT_ORG=org1.example.com
HOST_ADDRESSES=<IP_ADDRESS>
WORKING_DIRECTORY: /home/pupi04/mywork
.......
Preparing for the following operations: *********************
verify options, download images, generate certificates, start network, network status, channel create, channel join, anchor update
...................
Running operation: ******************************************
verify options
.
Running operation: ******************************************
download images
............
Running operation: ******************************************
generate certificates
...............................................................................................................................................................................................................................
Running operation: ******************************************
start network
.........................
Running operation: ******************************************
network status
...
Current Minifabric image ID and created at date time ********
2b2a0b6e9999   2021-11-19 12:57:58 +0000 UTC
.....
Docker node status ******************************************
mysite : Up 8 seconds
ca1.org4.example.com : Up 11 seconds
ca1.org3.example.com : Up 15 seconds
ca1.org2.example.com : Up 18 seconds
ca1.org1.example.com : Up 21 seconds
orderer3.example.com : Up 25 seconds
orderer2.example.com : Up 28 seconds
orderer1.example.com : Up 32 seconds
peer2.org4.example.com : Up 35 seconds
peer1.org4.example.com : Up 38 seconds
peer2.org3.example.com : Up 41 seconds
peer1.org3.example.com : Up 45 seconds
peer2.org2.example.com : Up 48 seconds
peer1.org2.example.com : Up 51 seconds
peer2.org1.example.com : Up 54 seconds
peer1.org1.example.com : Up 56 seconds
peer2.org4.example.com.couchdb : Up 59 seconds
peer1.org4.example.com.couchdb : Up About a minute
peer2.org3.example.com.couchdb : Up About a minute
peer1.org3.example.com.couchdb : Up About a minute
peer2.org2.example.com.couchdb : Up About a minute
peer1.org2.example.com.couchdb : Up About a minute
peer2.org1.example.com.couchdb : Up About a minute
peer1.org1.example.com.couchdb : Up About a minute
Fabric network peer and orderer node health status **********
peer1.org1.example.com "OK"
peer2.org1.example.com "OK"
peer1.org2.example.com "OK"
peer2.org2.example.com "OK"
peer1.org3.example.com "OK"
peer2.org3.example.com "OK"
peer1.org4.example.com "OK"
peer2.org4.example.com "OK"
orderer1.example.com "OK"
orderer2.example.com "OK"
orderer3.example.com "OK"
Network Status: 100%
Running operation: ******************************************
channel create
......
Running operation: ******************************************
channel join
...................................................
Running operation: ******************************************
anchor update
......................
STATS *******************************************************
minifab: ok=422 failed=0
real    4m9.360s
user    2m48.033s
sys     0m34.655s

Now I upload in the right dir my chaincode and then:
minifab install,approve,commit,initialize,profilegen,discover -v 1.0 -n fabcar -l node -r true -p '"initLedger"'

Using spec file: /home/pupi04/mywork/spec.yaml
Minifab Execution Context:
FABRIC_RELEASE=2.3.0
CHANNEL_NAME=mychannel
PEER_DATABASE_TYPE=couchdb
CHAINCODE_LANGUAGE=node
CHAINCODE_NAME=fabcar
CHAINCODE_VERSION=1.0
CHAINCODE_INIT_REQUIRED=true
CHAINCODE_PARAMETERS="initLedger"
CHAINCODE_PRIVATE=true
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=newest
EXPOSE_ENDPOINTS=true
CURRENT_ORG=org1.example.com
HOST_ADDRESSES=<IP_ADDRESS>
WORKING_DIRECTORY: /home/pupi04/mywork
.......
Preparing for the following operations: *********************
verify options, cc install, cc approve, cc commit, cc initialize, profile generation, discover
...................
Running operation: ******************************************
verify options
.
Running operation: ******************************************
cc install
................................................
Running operation: ******************************************
cc approve
......
Running operation: ******************************************
cc commit
.............
Running operation: ******************************************
cc initialize
......
Running operation: ******************************************
profile generation
.................................................
Running operation: ******************************************
discover
............................
Discover endorsers results **********************************
Chaincode endorsers file: ./vars/discover/mychannel/fabcar_endorsers.json
Discover orderers results ***********************************
Channel orderers file: ./vars/discover/mychannel/ordererendpoints.json
STATS *******************************************************
minifab: ok=208 failed=0
real    4m50.051s
user    1m38.248s
sys     0m16.751s

And everything works with my apiserver (on port 3000).
Now, if I just minifab down
and then minifab netup

Using spec file: /home/pupi04/mywork/spec.yaml
Minifab Execution Context:
FABRIC_RELEASE=2.3.0
CHANNEL_NAME=mychannel
PEER_DATABASE_TYPE=couchdb
CHAINCODE_LANGUAGE=node
CHAINCODE_NAME=fabcar
CHAINCODE_VERSION=1.0
CHAINCODE_INIT_REQUIRED=true
CHAINCODE_PARAMETERS="initLedger"
CHAINCODE_PRIVATE=true
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=newest
EXPOSE_ENDPOINTS=true
CURRENT_ORG=org1.example.com
HOST_ADDRESSES=<IP_ADDRESS>
WORKING_DIRECTORY: /home/pupi04/mywork
.......
Preparing for the following operations: *********************
verify options, download images, generate certificates, start network, network status
.......
Running operation: ******************************************
verify options
.
Running operation: ******************************************
download images
............
Running operation: ******************************************
generate certificates
..
Running operation: ******************************************
start network
.....................
Running operation: ******************************************
network status
...
Current Minifabric image ID and created at date time ********
2b2a0b6e9999   2021-11-19 12:57:58 +0000 UTC
.....
Docker node status ******************************************
dev-peer1.org4.example.com-fabcar_1.0-ce65be84e70e : Created
dev-peer2.org4.example.com-fabcar_1.0-ce65be84e70e : Created
dev-peer2.org3.example.com-fabcar_1.0-ce65be84e70e : Up 6 seconds
dev-peer1.org3.example.com-fabcar_1.0-ce65be84e70e : Up 7 seconds
mysite : Up 11 seconds
dev-peer2.org2.example.com-fabcar_1.0-ce65be84e70e : Up 11 seconds
ca1.org4.example.com : Up 16 seconds
dev-peer1.org2.example.com-fabcar_1.0-ce65be84e70e : Up 17 seconds
ca1.org3.example.com : Up 21 seconds
dev-peer2.org1.example.com-fabcar_1.0-ce65be84e70e : Up 26 seconds
ca1.org2.example.com : Up 28 seconds
dev-peer1.org1.example.com-fabcar_1.0-ce65be84e70e : Up 28 seconds
ca1.org1.example.com : Up 33 seconds
orderer3.example.com : Up 41 seconds
orderer2.example.com : Up 46 seconds
orderer1.example.com : Up 52 seconds
peer2.org4.example.com : Up 59 seconds
peer1.org4.example.com : Up About a minute
peer2.org3.example.com : Up About a minute
peer1.org3.example.com : Up About a minute
peer2.org2.example.com : Up About a minute
peer1.org2.example.com : Up About a minute
peer2.org1.example.com : Up About a minute
peer1.org1.example.com : Up About a minute
peer2.org4.example.com.couchdb : Up About a minute
peer1.org4.example.com.couchdb : Up About a minute
peer2.org3.example.com.couchdb : Up About a minute
peer1.org3.example.com.couchdb : Up About a minute
peer2.org2.example.com.couchdb : Up About a minute
peer1.org2.example.com.couchdb : Up About a minute
peer2.org1.example.com.couchdb : Up About a minute
peer1.org1.example.com.couchdb : Up About a minute
Fabric network peer and orderer node health status **********
peer1.org1.example.com "OK"
peer2.org1.example.com "OK"
peer1.org2.example.com "OK"
peer2.org2.example.com "OK"
peer1.org3.example.com "OK"
peer2.org3.example.com "OK"
peer1.org4.example.com "OK"
peer2.org4.example.com "OK"
orderer1.example.com "OK"
orderer2.example.com "OK"
orderer3.example.com "OK"
Network Status: 100%
STATS *******************************************************
minifab: ok=75  failed=0
real    2m16.549s
user    0m59.415s
sys     0m12.524s

Now, if i try to make a query/invoke through my apiserver, this is what I get:

2021-12-20T11:41:46.378Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer1.org1.example.com, url:grpcs://<IP_ADDRESS>:7004, connected:false, connectAttempted:true
2021-12-20T11:41:46.379Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer1.org1.example.com url:grpcs://<IP_ADDRESS>:7004 timeout:3000
2021-12-20T11:41:46.379Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer1.org1.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer1.org1.example.com, url:grpcs://<IP_ADDRESS>:7004, connected:false, connectAttempted:true
2021-12-20T11:41:49.382Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer2.org1.example.com, url:grpcs://<IP_ADDRESS>:7005, connected:false, connectAttempted:true
2021-12-20T11:41:49.382Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer2.org1.example.com url:grpcs://<IP_ADDRESS>:7005 timeout:3000
2021-12-20T11:41:49.382Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer2.org1.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer2.org1.example.com, url:grpcs://<IP_ADDRESS>:7005, connected:false, connectAttempted:true
2021-12-20T11:41:52.385Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer1.org2.example.com, url:grpcs://<IP_ADDRESS>:7006, connected:false, connectAttempted:true
2021-12-20T11:41:52.385Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer1.org2.example.com url:grpcs://<IP_ADDRESS>:7006 timeout:3000
2021-12-20T11:41:52.385Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer1.org2.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer1.org2.example.com, url:grpcs://<IP_ADDRESS>:7006, connected:false, connectAttempted:true
2021-12-20T11:41:55.388Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer2.org2.example.com, url:grpcs://<IP_ADDRESS>:7007, connected:false, connectAttempted:true
2021-12-20T11:41:55.388Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer2.org2.example.com url:grpcs://<IP_ADDRESS>:7007 timeout:3000
2021-12-20T11:41:55.388Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer2.org2.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer2.org2.example.com, url:grpcs://<IP_ADDRESS>:7007, connected:false, connectAttempted:true
2021-12-20T11:41:58.390Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer1.org3.example.com, url:grpcs://<IP_ADDRESS>:7008, connected:false, connectAttempted:true
2021-12-20T11:41:58.391Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer1.org3.example.com url:grpcs://<IP_ADDRESS>:7008 timeout:3000
2021-12-20T11:41:58.391Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer1.org3.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer1.org3.example.com, url:grpcs://<IP_ADDRESS>:7008, connected:false, connectAttempted:true
2021-12-20T11:42:01.393Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer2.org3.example.com, url:grpcs://<IP_ADDRESS>:7009, connected:false, connectAttempted:true
2021-12-20T11:42:01.394Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer2.org3.example.com url:grpcs://<IP_ADDRESS>:7009 timeout:3000
2021-12-20T11:42:01.394Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer2.org3.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer2.org3.example.com, url:grpcs://<IP_ADDRESS>:7009, connected:false, connectAttempted:true
2021-12-20T11:42:04.398Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer1.org4.example.com, url:grpcs://<IP_ADDRESS>:7010, connected:false, connectAttempted:true
2021-12-20T11:42:04.398Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer1.org4.example.com url:grpcs://<IP_ADDRESS>:7010 timeout:3000
2021-12-20T11:42:04.399Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer1.org4.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer1.org4.example.com, url:grpcs://<IP_ADDRESS>:7010, connected:false, connectAttempted:true
2021-12-20T11:42:07.400Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer2.org4.example.com, url:grpcs://<IP_ADDRESS>:7011, connected:false, connectAttempted:true
2021-12-20T11:42:07.400Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer2.org4.example.com url:grpcs://<IP_ADDRESS>:7011 timeout:3000
2021-12-20T11:42:07.400Z - info: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer2.org4.example.com due to Error: Failed to connect before the deadline on Endorser- name: peer2.org4.example.com, url:grpcs://<IP_ADDRESS>:7011, connected:false, connectAttempted:true
2021-12-20T11:42:10.402Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Committer- name: orderer1.example.com, url:grpcs://<IP_ADDRESS>:7020, connected:false, connectAttempted:true
2021-12-20T11:42:10.402Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server orderer1.example.com url:grpcs://<IP_ADDRESS>:7020 timeout:3000
2021-12-20T11:42:10.402Z - info: [NetworkConfig]: buildOrderer - Unable to connect to the committer orderer1.example.com due to Error: Failed to connect before the deadline on Committer- name: orderer1.example.com, url:grpcs://<IP_ADDRESS>:7020, connected:false, connectAttempted:true
2021-12-20T11:42:13.404Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Committer- name: orderer2.example.com, url:grpcs://<IP_ADDRESS>:7021, connected:false, connectAttempted:true
2021-12-20T11:42:13.404Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server orderer2.example.com url:grpcs://<IP_ADDRESS>:7021 timeout:3000
2021-12-20T11:42:13.404Z - info: [NetworkConfig]: buildOrderer - Unable to connect to the committer orderer2.example.com due to Error: Failed to connect before the deadline on Committer- name: orderer2.example.com, url:grpcs://<IP_ADDRESS>:7021, connected:false, connectAttempted:true
2021-12-20T11:42:16.406Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Committer- name: orderer3.example.com, url:grpcs://<IP_ADDRESS>:7022, connected:false, connectAttempted:true
2021-12-20T11:42:16.406Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server orderer3.example.com url:grpcs://<IP_ADDRESS>:7022 timeout:3000
2021-12-20T11:42:16.407Z - info: [NetworkConfig]: buildOrderer - Unable to connect to the committer orderer3.example.com due to Error: Failed to connect before the deadline on Committer- name: orderer3.example.com, url:grpcs://<IP_ADDRESS>:7022, connected:false, connectAttempted:true
2021-12-20T11:42:19.448Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: peer1.org3.example.com, url:grpcs://<IP_ADDRESS>:7008, connected:false, connectAttempted:true
2021-12-20T11:42:19.449Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer1.org3.example.com url:grpcs://<IP_ADDRESS>:7008 timeout:3000
2021-12-20T11:42:19.449Z - error: [ServiceEndpoint]: ServiceEndpoint grpcs://<IP_ADDRESS>:7008 reset connection failed :: Error: Failed to connect before the deadline on Discoverer- name: peer1.org3.example.com, url:grpcs://<IP_ADDRESS>:7008, connected:false, connectAttempted:true
2021-12-20T11:42:22.450Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: peer2.org3.example.com, url:grpcs://<IP_ADDRESS>:7009, connected:false, connectAttempted:true
2021-12-20T11:42:22.450Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer2.org3.example.com url:grpcs://<IP_ADDRESS>:7009 timeout:3000
2021-12-20T11:42:22.451Z - error: [ServiceEndpoint]: ServiceEndpoint grpcs://<IP_ADDRESS>:7009 reset connection failed :: Error: Failed to connect before the deadline on Discoverer- name: peer2.org3.example.com, url:grpcs://<IP_ADDRESS>:7009, connected:false, connectAttempted:true
2021-12-20T11:42:22.451Z - error: [DiscoveryService]: send[mychannel] - no discovery results
Failed to evaluate transaction: Error: DiscoveryService has failed to return results

What does my "netup" miss to restart successfully the network?

Try 'minifab discover' before you do a query. I am not really sure, down and netup should do it.

minifab discover

Using spec file: /home/pupi04/mywork/spec.yaml
Minifab Execution Context:
FABRIC_RELEASE=2.3.0
CHANNEL_NAME=mychannel
PEER_DATABASE_TYPE=couchdb
CHAINCODE_LANGUAGE=node
CHAINCODE_NAME=fabcar
CHAINCODE_VERSION=1.0
CHAINCODE_INIT_REQUIRED=true
CHAINCODE_PARAMETERS="initLedger"
CHAINCODE_PRIVATE=true
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=newest
EXPOSE_ENDPOINTS=true
CURRENT_ORG=org1.example.com
HOST_ADDRESSES=<IP_ADDRESS>
WORKING_DIRECTORY: /home/pupi04/mywork
.......
Preparing for the following operations: *********************
verify options, discover
.......
Running operation: ******************************************
verify options
.
Running operation: ******************************************
discover
.........
Run the channel discover script on cli container ************
non-zero return code
failed to create new connection: context deadline exceeded
failed connecting to <IP_ADDRESS>:7005: failed connecting to discovery service: failed to create new connection: context deadline exceeded
STATS *******************************************************
minifab: ok=28  failed=1

Hmmm, discover command even failed. I am not really sure. Can you see after down command if there are still some containers running ?

Down command should remove all the containers. If there are still containers running, it means some thing has gone wrong. Remove these running containers manually and try again.

Checking with "docker ps" (and in Docker Desktop too) I confirm that after minifab down, no containers are running.
Furthermore, don't know if it is relevant, but I got this situation expecially when I run "minifab down", then restart my machine, and "minifab netup". Could the machine restart be correlated to this problem?

Okay I confirm what I said:
CASE 1) minifab down + minifab netup: no problem, everything works successfully.
CASE 2) minifab down + restart the pc/machine + minifab netup: the problem above.
I just tried with my own network and my personal chaincode, don't know if the problem comes even with default network and chaincode.

Hmmm. Do not know if your restart actually somehow reset docker stats.


Add basic usage documentation on searchClient.search()

Pull Request
It is not obvious on how you can use instantMeiliSearch to perform searches programmatically, so I am suggesting to add a short code snippet about that.
What does this PR do?
Adds documentation on how to use searchClient.search().

Hey @niklasfjeldberg thanks a lot for this addition :) Could you add a bit of context before the code-sample to avoid confusing new users?

Hey @niklasfjeldberg
Are you still working on this?

Hi @bidoubiwa, sorry for the late replay. I will get this done soon. First time contributing, so will have to take some time.

No problem :)

Hey @niklasfjeldberg feel free to re-open this PR whenever you come back. Meanwhile I'm closing it as it is stale


Chat history dose not work with Google Authentication

I enabled Chat history and it works well with default authentication (Microsoft Provider). But when i change to use Google the error occurs.

When i check in browser debug, There is an 500 error with api /history/list.
And this is the app service console log.

Hi @tanvlt the chat history feature leverages the Microsoft Identity Provider to get the logged in user's user ID, which is used to store/retrieve/update entries in the CosmosDB for that user. You can see we fetch the user ID from the backend request header in this function: https://github.com/microsoft/sample-app-aoai-chatGPT/blob/main/backend/auth/auth_utils.py#L1
To use another authentication provider, you would need to modify this logic to get a unique user ID for the logged in user from that provider. Then that ID can be used when interacting with the CosmosDB.
Hope that helps!

Hey, Sarah, will this also apply to AAD B2C added as an OIDC auth provider? It seems like the request from AAD B2C should include the same headers used in the application code that you pointed to, yet I experience the same "...CosmosDB is not working..." message. Any advice you can provide on reconciling the chat history feature with AAD B2C would be greatly appreciated by our team and customers!


Add config.defer_model_build to optionally make model building lazy

Change Summary
This proposes a new config flag defer_model_build, when true this means the core schema, schema validator and schema serializer are not constructed for a model when it's defined, instead they're only built when model_rebuild() is called, or when the model is first called.
Two reasons this can be useful:

so models which are only ever used nested or within TypeAdapters don't need all this logic calling - see #6768 and #6748
so that the type namespace used when constructing models can be customised, fixes #6742

Related issue number
fix #6742
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable - somewhat, I'm going to rewrite the docs for ConfigDict anyway, so I'll add more logic then
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @adriangb

Having this as a config flag sounds reasonable to me. For the reasons discussed in https://github.com/pydantic/pydantic/issues/6768 I don’t think it’s good as a default, but for large apps it seems like a reasonable trade-off.
Shouldn’t we make TypeAdapter lazy as well?

Let's rename to defer_build and apply to TypeAdapter too.


Ci rn 810xx

Update dates, CI manager version number, and delegate version number before publishing.

set up test intelligence - Update parallelism steps to reflect UI options. https://6526e6b78769400091848b74--harness-developer.netlify.app/docs/continuous-integration/use-ci/run-tests/set-up-test-intelligence#enable-parallelism-test-splitting-for-test-intelligence:~:text=In the Run,is class timing.
What's new : https://6526e6b78769400091848b74--harness-developer.netlify.app/release-notes/whats-new
CI release notes : https://6526e6b78769400091848b74--harness-developer.netlify.app/release-notes/continuous-integration
Already merged tooltip PR.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Update React peer dependency to v15.0

React v15.0 is released, and is not compatible with the peer dependency listed since it is a major version bump.

See PR: https://github.com/jsdir/react-ladda/pull/28

Fixed with https://github.com/jsdir/react-ladda/pull/30

This needs to go along with a react-ladda patch version bump. As it stands npm isn't using the fix because it's still at 4.0.2

fixed in<EMAIL_ADDRESS>

Thanks @jamalneufeld and @jsdir !


Originally plan module take about 60% cpu, now it takes 250% cpu!!!
Is there any option to reduce the plan module cost?

Thank you for your question. The planning module runs in a single thread, except the reference line smoothing part. Could you let us know how you get the 250% cpu consumption result?

@wobistdu awaiting your response.


Add AccessibilityDependency (UIAccessibility abstraction)

Created dependency module for UIAccessibility framework

Supported features/modes

VoiceOver
Mono audio
Closed captioning
Invert colors
Guided access
Bold text
Button shapes
Grayscale
Reduce transparency
Reduce motion
Reduce motion: prefer cross-fade transitions
Video autoplay
Darker system colors (increase contrast)
Switch control
Speak selection
Speak screen
Shake to undo
Assistive touch
On/Off switch label
Differentiate without color
Hearing device paired ear

Supported UIAccessibility functions

UIAccessibility.convertToScreenCoordinates
UIAccessibility.focusedElement
UIAccessibility.post
UIAccessibility.requestGuidedAccessSession

Accessibility Dependency ddocumentation mirrors UIKit's UIAccessibility documentation

@tgrapperon I'd like to think that I can just slap on some pragmas for iOS and tvOS since I didn't see any UIAccessibility functionality that is platform-specific, but I imagine there's a few functions or variables that are only available in one platform. Is there an easy way for you to compare API between different platforms? What was your process when you were creating the UIApplication or UIDevice abstraction?

Hey @acosmicflamingo! Wow, thanks, very impressive, and something that could definitely be useful. Congrats for getting the ConfigurableProxy and property wrapper stuff that I had not properly documented yet!
I didn't had the time to go through properly, and I'm heading to bed right now, but a few comments:

The library requires iOS 13, etc., so I decided to generally not annotate the availability if <=13, as the symbols are available anyway. The only exception is when we need to specify the availability for a platform of something that was already present for a long time on the other ones. For example, something that was available on iOS 9, but only on watchOS from v8. Nothing wrong with your implementation, but for homogeneity, we would probably remove these annotations if they're not effective.
I don't think there's a lot of value into turning the Notification.Name constant as dependencies. But we can implement the corresponding notifications in the _Notification dependency and get streams of these values.
I don't think that these values should be MainActor, so this can be simplified too.
We should probably expose macOS variants too, and properly install this dependency, as it is currently not built. This is a huge task, so I'll check how to make room for it for a latter PR.

There are many things in the library that I didn't had the time to explain yet, so if that's OK with you, I'll take over from now and I'll update this PR with the changes I have in mind, and I'll let you know once I'm done, so you can check if it still fits what you had in mind.
But this is a great idea and a great working base, and surely something that will be very useful when it'll land. Thanks again!

@acosmicflamingo

When you were creating the UIApplication or UIDevice abstractions, what was your process for finding the functionality that was available in one platform but not the other?

I looked at the documentation and interface files, and the unavailable ones that I missed were caught when trying to build for these platforms.

Hey @acosmicflamingo! Wow, thanks, very impressive, and something that could definitely be useful. Congrats for getting the ConfigurableProxy and property wrapper stuff that I had not properly documented yet!
I didn't had the time to go through properly, and I'm heading to bed right now, but a few comments:

The library requires iOS 13, etc., so I decided to generally not annotate the availability if <=13, as the symbols are available anyway. The only exception is when we need to specify the availability for a platform of something that was already present for a long time on the other ones. For example, something that was available on iOS 9, but only on watchOS from v8. Nothing wrong with your implementation, but for homogeneity, we would probably remove these annotations if they're not effective.
I don't think there's a lot of value into turning the Notification.Name constant as dependencies. But we can implement the corresponding notifications in the _Notification dependency and get streams of these values.
I don't think that these values should be MainActor, so this can be simplified too.
We should probably expose macOS variants too, and properly install this dependency, as it is currently not built. This is a huge task, so I'll check how to make room for it for a another PR.

There are many things in the library that I didn't had the time to explain yet, so if that's OK with you, I'll take over from now and I'll update this PR with the changes I have in mind, and I'll let you know once I'm done, so you can check if it still fits what you had in mind.
But this is a great idea and a great working base, and surely something that will be very useful when it'll land. Thanks again!

@tgrapperon Woohoo! Glad to hear this :) Hahah like isowords, a lot can be learned just by jumping into the deep end so ConfigurableProxy wasn't hard to grasp after looking at how you designed UIDevice & UIApplication. If anything, it felt like plagiarism since UIApplication and UIAccessibility are very similar in structure.
As for your points:

I copied and pasted whatever was in UIKit.UIApplication and thought it'd be better to keep the availability and delete it if requested, than to not include it, and be told that it should be included. Because this library requires iOS 13, then yes we can definitely get rid of those superfluous accessibility decorators
Yeah I can see that. In the same spirit of being more happy to delete functionality than to add it, I created a lot of the Notification.Name constant as dependencies although it does seem a bit silly since they are constants after all. I do see that in the current state of DependenciesAdditions, the right place for these NSNotification.Name values should be in _Notification. With that being said, my only concern is the instance where users import AccessibilityDependency but not _Notification. If Accessibility is really a UIAccessibility abstraction, then I think users would expect these notification names to be available. A great solution to this may be something like this in the AccessibilityGetters, so we don't leave those users behind (and make accessibility as easy as possible for developers to use):

  /// A Boolean value that indicates whether VoiceOver is in an enabled state.
  ///
  /// You can use this function to customize your app’s UI specifically for VoiceOver users.
  /// For example, you might want UI elements that usually disappear quickly to persist
  /// onscreen for VoiceOver users.
  ///
  /// Note that you can also listen for the
  /// ``voiceOverStatusDidChangeNotification`` notification to determine
  /// when VoiceOver starts and stops. In the spirit of utilizing the Dependencies library,
  /// the voiceOverStatusDidChangeNotification property is located within
  /// `@Dependency(\.notification) var notification`, which can be utilized after
  /// importing `_Notification` in your codebase
  @MainActor
  @available(iOS 4.0, *)
  public var isVoiceOverRunning: Bool {
    _implementation.isVoiceOverRunning
  }

I made all those properties MainActor as a result of not trusting the values I get reflecting the app's state if they are retrieved in a background task, but you can thank UIDevice for that ;) looking through UIAccessibility, I think you're right (and I imagine that UIAccessibility needs to be accurate if executed in a background task) so MainActor most likely seems useless here.
Yeah macOS does have its own variants (e.g. iOS's darkColorsEnabled == macOS's increaseContrast) so if we want to support AppKit users, then this PR is certainly incomplete

Yeah I don't have a problem with you taking over from here :) I wanted to do this myself since I imagine you have tons in your backlog already and don't want to be that person who creates a Github issue asking "WHERE IS ACCESSIBILITY DEPENDENCY??? MAKE IT NOW" when I could just write up my implementation and create a PR for it. But yeah, DependencyAdditions is your project so as the maintainer, you do what you want! If you need help with anything though, you can certainly ask and I can do what I can! Thanks @tgrapperon for all your effort in TCA, Dependencies, and open source in general :D

Hey @acosmicflamingo!
I've reworked the PR into something more in line with the other dependencies.

Notifications have been relocated into the _Notification module, so they can be observed directly.
It is available on iOS and tvOS for now. Other platforms will be supported later.
Removed MainActor annotations (I think that is better to only enforce it when required upstream, which was not the case here.
I've also trimmed the documentation to only include the slug line, which is the convention I implicitly followed in other dependencies, as the purpose is mostly to help disambiguating the APIs.
I simplified and moved a little the example from the README, as I feel that Application have a better pedagogical value in this position.

If this is fine with you, we can merge.

@tgrapperon WHOA! You really took it to the next level :D I am all for the changes you had made, and even find it funny that the snippet I wrote in the README in hindsight is pretty useless compared to your more practical one. I also made Accessibility first because I thought the intent was to order it alphabetically but I agree with your decision to move it after Application.
Go ahead and merge this as-is :) thanks for your really constructive feedback and your time to get this to tip-top shape 🥇  Woohoo!!!

Anytime! Sounds good 😃


feat: support raw custom filters

// Comments
{
    "actions": {
        list: {
            before(request) {
                // Find `comment.post.user.id in (1, 2, 3)
               // Target where: { post: { user: { id: In(1, 2, 3) } } }
                request.query['filters.post~~custom.user.id'] = In([1, 2, 3]);
                return request;
            }
        }
    }
}

I have released a version for my own use for this new feature https://www.npmjs.com/package/ @Shiweidu/adminjs typerm, I am using it in a production environment and it is working well!
Original intention: Sometimes we don't want to customize portable handlers for lists because we need to write a lot of code to complete the functionality. But the actual situation is that we need to retrieve and formulate data through TypeORM relationships.

This filtering scenario is actually very common.


Linux azcopy 7.3.0-netcore hangs on azure hosted agent for Azure DevOps pipeline

Hello,
In Azure DevOps a scrip hangs when calling azcopy 7.3.0-netcore (this is shipped with ubuntu-latest vmImage).

Please update to newer azcopy
Please fix the issue in DevOps

Thanks,
Tamas

Thanks for noting this issue.  This is not the right place to log a DevOps issue, I'm sorry.  Before I can help you find the right place, can I check please, is your version of AzCopy shipping with DevOps or with Ubuntu?

If it's a DevOps issue, it looks like the best place is "report a bug" here: https://azure.microsoft.com/en-au/support/devops/
I propose to close this now, because its not an AzCopy v10 bug.  But please do comment below if you have any further questions, or comments, or clarification on whether its a DevOps problem or an Ubuntu image problem.
Finally, AzCopy V10 is just a single executable (no DLLs). That makes it easy to deploy so I guess (I don't know) that there might be a way to get it going yourself in devOps, without waiting for any official upgrade.  I don't know enough about DevOps to know what would be involved in running your own custom exe like that.


nixos/mysql: add extraArguments option for mysqld

Things done

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

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

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

For the author, reviewers, and committers: this PR was scanned and appears to add a use of the deprecated types.string, which emits a warning as of #66346. Before merging, please change this to another type, possibly:

types.str for a single string where merging does not make sense, or cannot work
types.lines for multi-line configuration or scripts where merging is possible
types.listOf types.str for a mergeable list of strings


Allow azuredns serviceprincipal configuration from secret

Is your feature request related to a problem? Please describe.
Currently only the service principal client secret can be configured from a secret. The client-id, tenant-id etc need to be hardcoded. In my environment we provision service principals dynamically and have a mechanism to make all the required values available in kubernetes as a secret. We use this successfully in externaldns to fill the azuredns config file so externaldns can manage our dns zone: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure.md#creating-configuration-file
We cannot use this dynamic mechanism with cert-manager because everything except client-secret needs to be hardcoded.
Describe the solution you'd like
I would like the option to provide a complete config file with all service principal configuration as a kubernetes secret so we can dynamically provision this configuration. In the same way as external-dns can be configured: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure.md#creating-configuration-file
Describe alternatives you've considered
We will probably at some point use pod managed identity, but we are not there yet.
Additional context
https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure.md#creating-configuration-file
/kind feature

Bump

Bump


missing upower

Hi, this is great tool  but I'd suggest you mention somewhere that it needs 'upower' to function on Linux. As that was not installed on my system by default.

An even better strategy is to bundle it as a fallback.
// @gillstrom


[BUG] cleanup timeout does not follow ocp --timeout argument

Output of kube-burner version
$ ./bin/amd64/kube-burner version
Version: latest
Git Commit: c4b3281e0fe65b4d04a492cf0d77be76f4c5a731
Build Date: 2023-03-28-19:10:23
Go Version: go1.18.9
OS/Arch: linux amd64

Describe the bug
I ran a long run, and specifically set --timeout 5h, but the context times out during cleanup before 5h elapsed.
To Reproduce
$ ~/git/kube-burner/bin/amd64/kube-burner ocp node-density-heavy --timeout 5h --metrics-endpoint metrics-endpoint.yml --pods-per-node ... --es-index ... --es-server ...  2>&1 | tee -a kube-burner-$(date +"%F_%H-%M-%S")

Expected behavior
If workload scales up and garbage collects within 5 hours, there is no timeout.
If it exceeds 5h, the context may timeout.
Screenshots or output
Logs from kube-burner below.
The difference between 22:38:04 and 02:01:34 is only 3h23m30s.
time="2023-03-28 22:38:04" level=info msg="Listed nodes after using selector node-role.kubernetes.io/worker=,node-role.kubernetes.io/infra!=,node-role.kubernetes.io/workload!=: 26"
...
time="2023-03-29 00:46:36" level=info msg="Deleting namespaces with label kube-burner-uuid=bda02394-5c2e-404c-84d6-e5bbdcd9e920"
time="2023-03-29 01:13:30" level=info msg="Waiting for namespaces to be definitely deleted"
time="2023-03-29 02:01:34" level=fatal msg="Timeout cleaning up namespaces: Get \"https://api.test887.myocp4.com:6443/api/v1/namespaces?labelSelector=kube-burner-uuid%3Dbda02394-5c2e-404c-84d6-e5bbdcd9e920\": context deadline exceeded"

Additional context
Add any other context about the problem here.

Ok. Thanks for pointing this out.  At the least, we could explain the timeout/4 as part of the timeout flag doc.
The simplest to me is to either use the same timeout for cleanup (i.e. timeout for benchmarking, timeout for GC).
What is intuitive for having a single value (to me, at least) is keeping the entire execution (benchmarking, index, GC) to the same timeout. So, if I set timeout=4h, then I expect kube-burner to terminate in 4h, regardless of where it is in the process.
I suppose introducing a new flag for GC timeout that defaults to timeout/4. Or maybe at the very least explaining this somewhere in the docs, even if it doesn't make it to the CLI help.
I have only hit this a few times ever. So now that I know how it works, I can set my timeout accordingly if I expect GC to take a certain amount of time.

Fixed by https://github.com/cloud-bulldozer/kube-burner/pull/373


User getting a white-screen when trying to add a mentor

"I was able to submit on Brave (chromium); whenever I tried to add my mentor on as a collaborator, though, it would white-screen on me and I'd have to reload the page." - From one of our Open Reviewer Mentees

I notice this similar white screen effect happens when I tried adding a member to a community today.

I believe this is an optimization issue like #330; referencing to update both when ready.


Fix for pinned memory never being used

@szha

I got confused about the order the functions get called. Thanks @ptrendx for the fix.


Collect artifact's usage count: Make current BI board support new application id.

Please check parent issue for more information.

Closing this issue in favor of https://github.com/Azure/azure-sdk-for-java/issues/27103


waitFor passes retryInterval in as retryTimeout

waitFor calls ElementWrapper.elements with three parameters: undefined, retryInterval, and retryTimeout. However, ElementWrapper.elements only takes two, which means that elements is getting called with an undefined value for retryInterval and a retryTimeout equal to whatever the retry interval was.
This results in waitFor not waiting long enough if I have a small retryInterval but a relatively large retryTimeout.
To Reproduce
Steps (or script) to reproduce the behavior:

Run waitFor.test.js mocha test with a breakpoint within the elements method
Observe that retryInterval is undefined, and retryTimeout is equal to what retryInterval should be

Expected behavior
retryInterval will be passed as first argument to ElementWrapper.elements, and retryTimeout will be passed as the second argument.
Screenshots
If applicable, add screenshots to help explain your problem.

Versions:

Taiko: latest commit on master

Current workaround:
const retryInterval = getConfig('retryInterval');
setConfig({ retryInterval: getConfig('retryTimeout') });
await waitFor('whatever it might be that needs waiting');
setConfig({ retryInterval });

waitFor calls elements from match which takes three args (tag, retryInterval and retryTimeout), since tag is not needed from waitFor it is passed as undefined. I could see retryTimeout is applied properly in below example. Can you please verify again and let us know if you seeing something differently ?
(async () => {
    try {
        await openBrowser();
        let startTime = Date.now();
        await waitFor("something").catch(()=>{});
        console.log(Date.now()-startTime);
        await setConfig({retryTimeout:30000});
        startTime = Date.now();
        await waitFor("something").catch(()=>{});
        console.log(Date.now() - startTime);
    } catch (error) {
        console.error(error);
    } finally {
        await closeBrowser();
    }
})();

Output:
 ✔ Browser opened
10018
30007
 ✔ Browser closed

Note after updating retryTimeout second console log shows the updated value.

@nandhae you're right, if the argument is a string :) but if it's a selector, e.g. waitFor(button('Click me')), then it calls ElementWrapper.elements, which doesn't have a tag. I'm sorry that my example code wasn't accurate, I didn't realize that match doesn't return an ElementWrapper.
Here's your example but with a selector instead of a string:
(async () => {
    try {
        await openBrowser();
        let startTime = Date.now();
        await waitFor(text("something")).catch(()=>{});
        console.log(Date.now()-startTime);
        await setConfig({retryTimeout:30000});
        startTime = Date.now();
        await waitFor(text("something")).catch(()=>{});
        console.log(Date.now() - startTime);
        await setConfig({retryInterval:10000}); // as retryInterval is passed as retryTimeout
        startTime = Date.now();
        await waitFor(text("something")).catch(()=>{});
        console.log(Date.now() - startTime);
    } catch (error) {
        console.error(error);
    } finally {
        await closeBrowser();
    }
})();

Output:
✔ Browser opened
3120
3111
13867
 ✔ Browser closed

So, the path through the code that works with a string works fine, but the path through the code that accepts a selector doesn't wait as long.

Yes, thanks for pointing that out :) will be happy to review you a PR


Question: Way to tell if observable changed programmatically

Is there a way to tell if an observable keypath was changed programmatically or by user input?

Not that I am aware of. I would advise either:

putting the listeners directly on the input fields
or use a flag variable before changing it programmatically

No, as far as Ractive is concerned all changes are the same. There may be a way to have the binding say that it's firing an update and then make that available through a context method, but there's no inherent "source" built in to the change propagation.

Not a direct answer to the question but if you have control of your integrations, you can wire up your plugin's events to call Ractive methods.
const Input = Ractive.extend({
  template: '<input type="text" on-change="ractiveTriggered()">',
  onrender(){
    const input = jQuery(this.find('input')).plugin();

    // make the pluginTriggered Ractive method the callback of your plugin's on-change.
    input.plugin('onchange', this.pluginTriggered.bind(this));
  },
  ractiveTriggered(){ /* wired using Ractive's on-change */ },
  pluginTriggered(){ /* wired to the plugin's events */ },

});


Pass const to the QueryBuilder

Delete it

Try using a const FormattableString instead of const string.  The way you're building your FormattableString from a plain string will basically convert the whole statement to a single SqlParameter.


CSS-related changes

Some changes for greater control/flexibility over game style:

Add "game_author" class
Change title and author into blocks rather than rely on line break
Add container around title and author
Remove "toUpperCaseExceptEntities" from the game title and add "text-transform: uppercase" to the "game_title" class (Not sure if this function was used for a specific reason, but it felt better suited for the style sheet)
Break "Exits", "Actions", and "You can also see" sections into separate divs
Break "Ask", "Tell", and "Say" sections  into separate divs
Move ">" from prompt strings into pseudo-element (Allows for alternative characters or styling to be used)

Shouldn't make any noticeable change to appearance or functionality for anyone not touching the style sheet, but will add some options for those who do.

Nice, thank you!


Why split tensor for layers 2, 4 and 5?

Hello Rahul,
I am new to deep machine learning.
I came across your codes AlexNet-Experiments-Keras on Github. Thank you for the well documented guidelines. It really helped me.
However, I cannot understand why you split the tensor first before performing the convolution for layers 2, 4 and 5? (https://github.com/duggalrahul/AlexNet-Experiments-Keras/blob/master/convnets-keras/convnetskeras/customlayers.py)
Also, why is this process not done on layer 3? (https://github.com/duggalrahul/AlexNet-Experiments-Keras/blob/master/Code/alexnet_base.py)
I would be very grateful if you could answer my question.
Looking forward for your response.
Thanking you in advance.
Kind regards..

Hi @G33kyKitty
The split tensor is used to implement the specific AlexNet architecture design specified in the original paper. This was done so that the upper and lower halves of the network (refer to fig. 2 of paper) could be run on separate GPU's. This helped in keeping memory per GPU low (Try calculating the size of the convolution output feature maps for both with and without splitting). Since current GPU's offer much more memory than was available in 2011, the idea of splitting is not as important. The entire AlexNet architecture can fit on most modern GPUs.

@duggalrahul Thank you..


Scrollbar Can't represent a size of<PHONE_NUMBER> in Constraints

Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: Can't represent a size of<PHONE_NUMBER> in Constraints
at androidx.compose.ui.unit.Constraints$Companion.bitsNeedForSize(Constraints.kt:408)
at androidx.compose.ui.unit.Constraints$Companion.createConstraints-Zbe2FdA$ui_unit(Constraints.kt:371)
at androidx.compose.ui.unit.Constraints$Companion.fixed-JhjzzOo(Constraints.kt:319)
at androidx.compose.foundation.Scrollbar_desktopKt$horizontalMeasurePolicy$1.measure-3p2s80s(Scrollbar.desktop.kt:610)
at androidx.compose.ui.node.InnerPlaceable.measure-BRTryo0(InnerPlaceable.kt:55)
at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.measure-BRTryo0(DelegatingLayoutNodeWrapper.kt:131)
at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.measure-BRTryo0(DelegatingLayoutNodeWrapper.kt:131)
at androidx.compose.foundation.layout.PaddingModifier.measure-3p2s80s(Padding.kt:364)
at androidx.compose.ui.node.ModifiedLayoutNode.measure-BRTryo0(ModifiedLayoutNode.kt:39)
at androidx.compose.foundation.layout.FillModifier.measure-3p2s80s(Size.kt:658)
at androidx.compose.ui.node.ModifiedLayoutNode.measure-BRTryo0(ModifiedLayoutNode.kt:39)
at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.measure-BRTryo0(DelegatingLayoutNodeWrapper.kt:131)
at androidx.compose.ui.node.OuterMeasurablePlaceable$remeasure$2.invoke(OuterMeasurablePlaceable.kt:99)
at androidx.compose.ui.node.OuterMeasurablePlaceable$remeasure$2.invoke(OuterMeasurablePlaceable.kt:98)
at androidx.compose.runtime.snapshots.Snapshot$Companion.observe(Snapshot.kt:1798)
at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:121)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui(OwnerSnapshotObserver.kt:88)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeMeasureSnapshotReads$ui(OwnerSnapshotObserver.kt:76)
at androidx.compose.ui.node.OuterMeasurablePlaceable.remeasure-BRTryo0(OuterMeasurablePlaceable.kt:98)
at androidx.compose.ui.node.LayoutNode.remeasure-_Sx5XlM$ui(LayoutNode.kt:1317)
at androidx.compose.ui.node.LayoutNode.remeasure-_Sx5XlM$ui$default(LayoutNode.kt:1313)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.doRemeasure(MeasureAndLayoutDelegate.kt:170)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.remeasureAndRelayoutIfNeeded(MeasureAndLayoutDelegate.kt:228)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.access$remeasureAndRelayoutIfNeeded(MeasureAndLayoutDelegate.kt:38)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.measureAndLayout(MeasureAndLayoutDelegate.kt:201)
at androidx.compose.ui.platform.SkiaBasedOwner.measureAndLayout(SkiaBasedOwner.skiko.kt:245)
at androidx.compose.ui.node.Owner$DefaultImpls.measureAndLayout$default(Owner.kt:182)
at androidx.compose.ui.ComposeScene.render(ComposeScene.skiko.kt:381)
at androidx.compose.ui.awt.ComposeLayer$1$onRender$1.invoke(ComposeLayer.desktop.kt:237)
at androidx.compose.ui.awt.ComposeLayer$1$onRender$1.invoke(ComposeLayer.desktop.kt:236)
at androidx.compose.ui.awt.ComposeLayer.catchExceptions(ComposeLayer.desktop.kt:89)
at androidx.compose.ui.awt.ComposeLayer.access$catchExceptions(ComposeLayer.desktop.kt:70)
at androidx.compose.ui.awt.ComposeLayer$1.onRender(ComposeLayer.desktop.kt:236)
at org.jetbrains.skiko.SkiaLayer.update$skiko(SkiaLayer.awt.kt:441)
at org.jetbrains.skiko.redrawer.Direct3DRedrawer.update(Direct3DRedrawer.kt:54)
at org.jetbrains.skiko.redrawer.Direct3DRedrawer.access$update(Direct3DRedrawer.kt:10)
at org.jetbrains.skiko.redrawer.Direct3DRedrawer$frameDispatcher$1.invokeSuspend(Direct3DRedrawer.kt:28)
at org.jetbrains.skiko.redrawer.Direct3DRedrawer$frameDispatcher$1.invoke(Direct3DRedrawer.kt)
at org.jetbrains.skiko.redrawer.Direct3DRedrawer$frameDispatcher$1.invoke(Direct3DRedrawer.kt)
at org.jetbrains.skiko.FrameDispatcher$job$1.invokeSuspend(FrameDispatcher.kt:33)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at java.desktop/java.awt.event.InvocationEvent.dispatch$$$capture(InvocationEvent.java:318)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Disconnected from the target VM, address: '<IP_ADDRESS>:62502', transport: 'socket'
Process finished with exit code 0

Could you please provide a small sample to reproduce the crash?

As #3799 is closed, I will continue the discussion here.
Setting a string with 300K length to a Text() component would reproduce the constraint issue. Although this limitation is what Compose for Android designed, because it might not (?) make sense to display such volume in an Android mobile device. But in desktop, I think it is a valid use case. It does not make sense that a desktop application cannot handle displaying 1MB data. It is expected Google would reject or put in a very low priority for this issue, but in the desktop world this is a larger issue.
I think an alternative is to provide a LazyText (or make Text lazy) with some care of scrolling API design, or expose the text layout API so that developers can split long strings into multiple Text components embedded in a LazyColumn/Row.
It seems there already exists workaround for other use cases, e.g. giant image - cropped by visible area with nested scrolling, long list - use LazyColumn.

With compose desktop 1.5.2, I only encountered this issue with Text, not scrollbars.
I am able to implement a workaround for long Text composable.
var contentWidthInPx by remember { mutableStateOf<Int?>(null) }
val textStyle = LocalTextStyle.current.copy(
    fontSize = LocalFont.current.bodyFontSize,
    fontFamily = FontFamily.Monospace,
)
val density = LocalDensity.current
val fontFamilyResolver = LocalFontFamilyResolver.current
val numCharsInALine = if (contentWidthInPx != null) {
    remember(contentWidthInPx) {
        Paragraph(
            text = "0".repeat(1000),
            style = textStyle,
            constraints = Constraints(maxWidth = contentWidthInPx!!),
            density = density,
            fontFamilyResolver = fontFamilyResolver,
        ).getLineEnd(0)
    }
} else {
    0
}
val textsSplitted = if (contentWidthInPx != null && numCharsInALine > 0) {
    text.split('\n')
        .flatMap {
            it.chunked(numCharsInALine)
        }
        .withIndex()
        .groupBy { it.index / 100 }
        .map { it.value.joinToString("\n") { it.value } }
} else {
    listOf(" ")
}
LazyColumn(modifier = Modifier.onGloballyPositioned {
    contentWidthInPx = it.size.width
}) {
    textsSplitted.forEach {
        item {
            Text(
                text = it,
                fontFamily = FontFamily.Monospace
            )
        }
    }
}

Problems:

If the long Text is within a lazy container, the composable structure needs to be rewritten to avoid nested scrolling. (Can be very painful!)
Does not work well with SelectionContainer. New line characters are incorrect.
If font family is not monospaced, the text measure step needs to be twisted.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


C++ Module: AudioStreamSample  return data seems to be corrupted

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot master
Issue description:

I am serializing int16_t to an PoolByteArray then to AudioStreamSample
When I call AudioStreamSample.set_data on the resulting PoolByteArray, i cannot get the same data out when I call AudioStreamSample.get_data
Steps to reproduce:
Make an PoolByteArray d with values
Call AudioStreamSample.set_data(d)
AudioStreamSample.get_data() returns a different PoolByteArray I put in.
Expected: The values should be the same
Link to minimal example project:
I have a minimal example project to reproduce the issue.
https://github.com/hungrymonkey/godot/tree/issue11873
here is the code i am testing the issue with
void Summator::reset() {

    int s = 960;
    PoolByteArray d;
    d.resize(2 * s);
    for( int i = 0; i < s; i++ ){
       float p =  Math::sin((((float) i)*2.0*3.14 * 1000.0) / (44100.0)) * 32767;
       int32_t l = p;
       uint32_t a = (uint32_t) l;
       d.set(i*2, a & 0xFF);
       d.set(i*2+1, (a >> 8) & 0xFF);
    }
    Ref<AudioStreamSample> sam = memnew(AudioStreamSample);
    sam->set_data(d);
    sam->set_format(AudioStreamSample::FORMAT_16_BITS);
    sam->set_loop_mode(AudioStreamSample::LOOP_DISABLED);
    const PoolByteArray dat = sam->get_data();
    bool same = true;
    for( int i = 0; i < s * 2; i++){
        if( d[i] != dat[i]){
          print_line("at " + itos(i) + " : array,sample: " + itos(d[i]) + " : " + rtos(dat[i]));
          same = false;
          break;
        }
    }
    if( same)
       print_line("both the get_data and d are the same");
    else
       print_line("both the get_data and d are not the same");
    print_line("at " + itos(100) + " : array,sample: " + itos(d[100]) + " : " + itos(dat[100]));
    count = 0;
}

use the gdscript below
extends MainLoop
func _init():
        var s = Summator.new()
        s.reset()

it outputs
at 2 : array,sample: 42 : 0
both the get_data and d are not the same
at 100 : array,sample: 13 : 231

As a time of writing, DATA_PAD should be 16

I might be wrong since I haven't even used AudioStreamSample, but after briefly checking the code, I found that DATA_PAD in AudioStreamSample::set_data is not applied for AudioStreamSample::get_data.
Here is relevant code from current master:

https://github.com/godotengine/godot/blob/master/scene/resources/audio_stream_sample.cpp#L474
https://github.com/godotengine/godot/blob/master/scene/resources/audio_stream_sample.cpp#L489

maybe small fix like this will work?
PoolVector<uint8_t> AudioStreamSample::get_data() const {

	PoolVector<uint8_t> pv;

	if (data) {
		pv.resize(data_bytes);
		{
			PoolVector<uint8_t>::Write w = pv.write();
			uint8_t *dataptr = (uint8_t *)data;
			copymem(w.ptr(), dataptr + DATA_PAD, data_bytes); // <= DATA_PAD is added here
		}
	}

	return pv;
}

utils: pcm value at 500: -324
utils: pcm value at 700: 184
utils: pcm value at 500: 188 254
before audiostreamsample-set_data: pcm value at 700: 184 0
after audiostreamsample-set_data: pcm value at 500: 188 254
pcm_data1 size :1920
sendaudio: pcm value at 500: 188 254
pcm value at 500: -324

Since I am kinda a newbie, I am not really sure how to play sound in godot. I just using classes as I integrate stuff. It seems to work but I cannot confirm it through playing pcm.

i figure manage to get sound to work in my application. I am going to write a pull request soon. The audio works either way but the pointer off set issue seem to give garbled data.

btw, thanks for the code snippet. I would not thought of it

Hi @hungrymonkey, to tell you the truth, I'm also a noob here and even in gaming program in general.
I hope someone who did audio work in godot can review your PR.
anyway, I'm glad you figure out audio playback!

https://github.com/godotengine/godot/commit/98718ecd63476352f0a6299b2af2dd046ed9d5e3

@akien-mga I am reviewing the code again. I realize I should had not created this pull request.
I made a mistake. AudiostreamSamplePlayback requires a datapad to work.
https://github.com/godotengine/godot/blob/98718ecd63476352f0a6299b2af2dd046ed9d5e3/scene/resources/audio_stream_sample.cpp#L124
Can we just document the behavior that get_data() is padded on both sides.


Sync with Transifex

Update translations from Transifex and regenerate the base template file.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1254   +/-   ##
=======================================
  Coverage   70.23%   70.23%
=======================================
  Files         118      118
  Lines        6356     6356
  Branches      812      812
=======================================
  Hits         4464     4464
  Misses       1730     1730
  Partials      162      162

Continue to review full report at Codecov.

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


Change iterator API to allow moving items in and out

Closes #56, see the discussion there.
For now, this proposes to add the method WriteChunkUninit::populate(), but we might be able to find a better name?
Please note that this method is only available on uninitialized chunks because it would be unnecessary to fill the slots with their Default value just to overwrite them again with the values from the iterator.
I still have to clarify this (and probably some other things) in the docs.

I've updated the documentation (rendered HTML files as ZIP: https://github.com/mgeier/rtrb/suites/3210578459/artifacts/74262447).
I think the iterator API now makes much more sense than before, but I'm still wondering if we can find a better name than populate() ...

As mentioned in https://users.rust-lang.org/t/how-to-name-a-function-that-takes-an-iterator-and-moves-items-into-a-non-growable-container/62522, fill_from_iter() might be a good alternative name.

I've changed populate() (which isn't bad) to fill_from_iter() (which is more explicit). Rendered HTML as ZIP: https://github.com/mgeier/rtrb/suites/3344397678/artifacts/78522609.


Help about print receipt

What is incorrect in this request?
Thanks in advance for any help.
debug.log

Do not add double quotes before and after json opening and closing brackets.
Do not do this: "{ }". Do this { }
Do not escape quotes for fields.
Do not do this: "text": "alabala". Do this "text": "alabala"

Invalid property identifier character: \. Path '', line 2, position 1.
debug2.log

Please do not escape double quotes with backslashes. Folow the json
protocol.
На вт, 25 юни 2019 г., 12:25 StoyanMalchev<EMAIL_ADDRESS>написа:

Invalid property identifier character: . Path '', line 2, position 1.
debug2.log https://github.com/erpnet/ErpNet.FP/files/3324526/debug2.log
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/erpnet/ErpNet.FP/issues/46?email_source=notifications&email_token=AI7G4UX5YRTSYUDZNSEOGQTP4HQAXA5CNFSM4H3FYULKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPTZ7Y#issuecomment-505363711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI7G4UTPABTJEAL6S6H23BLP4HQAXANCNFSM4H3FYULA
.

Thanks!
Now, status is 200.
But ok is false
error code E404 - Illegal command
ResponceText.txt
data.txt

Attach debug.log to analyze this "Error occured while opening new fiscal receipt"

Also, you have another error. Your receipt should have at least one actual type=sale line. You have only comment lines, which is not ok.
Suggestion: Just remove the "isComment" field.

Also, your sale line should have amount. Also - taxGroup.
Like this:
		{
			"text": "По фактура 213232",
			"quantity": 1,
			"unitPrice": 36,
			"taxGroup": 2
		}

debug3.log
data.txt
ResponceText.txt

See the documentation about Tremol here:
Popular Bulgarian Fiscal Printers Setup
https://github.com/erpnet/ErpNet.FP/blob/master/BGFiscalPrinterSetup.md
На вт, 25 юни 2019 г., 13:51 StoyanMalchev<EMAIL_ADDRESS>написа:

debug3.log https://github.com/erpnet/ErpNet.FP/files/3324847/debug3.log
data.txt https://github.com/erpnet/ErpNet.FP/files/3324848/data.txt
ResponceText.txt
https://github.com/erpnet/ErpNet.FP/files/3324850/ResponceText.txt
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/erpnet/ErpNet.FP/issues/46?email_source=notifications&email_token=AI7G4USZU2BCTKMU3XMAOGDP4H2EHA5CNFSM4H3FYULKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYP22BY#issuecomment-505392391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI7G4UUJDPETCQ6OD6AAW4LP4H2EHANCNFSM4H3FYULA
.

Tested on TREMOL S25.
Thanks again!
Stoyan Malchev


HBASE-23075 Upgrade jackson version

Jackson security issues：
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.
https://nvd.nist.gov/vuln/detail/CVE-2019-16335
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
https://nvd.nist.gov/vuln/detail/CVE-2019-14540

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:green_heart:
mvninstall
5m 30s
master passed

:green_heart:
compile
2m 59s
master passed

:green_heart:
shadedjars
4m 30s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
2m 52s
master passed

_ Patch Compile Tests _

:green_heart:
mvninstall
4m 57s
the patch passed

:green_heart:
compile
3m  0s
the patch passed

:green_heart:
javac
3m  0s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:green_heart:
shadedjars
4m 33s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
15m 45s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
2m 51s
the patch passed

_ Other Tests _

:broken_heart:
unit
175m  2s
root in the patch failed.

:green_heart:
asflicense
0m 41s
The patch does not generate ASF License warnings.

229m 28s

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-660/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/660

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux 78532474be7c 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-660/out/precommit/personality/provided.sh

git revision
master / 52f5a85bfc

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-660/1/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-660/1/testReport/

Max. process+thread count
4456 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-660/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


ARROW-10077: [C++] Fix possible integer multiplication overflow

using a literal implies 32-bit integers for some compilers so this could overflow potentially.

Thanks @emkornfield !

Does this correspond to a OSS-Fuzz regresion?

It was found with our internal fuzzer.  Unfortunately do to how it works there are concerns over sharing the actual file.

Ah, thank you. Does it work differently from OSS-Fuzz, or use a different seed corpus?

As it was explained to me, part of the seed corpus comes from the fuzzer binary itself (if I had to guess it swaps random bytes from it) so there is small chance of exposing internal library information if we shared the file.


how can we make deployments faster?

pushing to the repo results in ~10mins of wait until all of the deployments (xyflow-website, reactflow-website, svelteflow-website) are finished. How can we configure turborepo/vercel so that only the changed website gets rebuilt and deployed?

fixed in vercel. we are using the ignored build step feature to detect changes through turbo-ignore now.


Introduction / Wizard on how to use the app

Idea by Licaon_Kter from F-Droid on GitLab

How I understood the idea by Licaon is to give some general information about how to save pins, a reference to some explanation on how it works behind the scenes (see README security details) and that kind of things.

Idea by Licaon_Kter from F-Droid on GitLab

thats not a meaningful way to put it in repos. who knows what may happen to the data at link, at least a summary should be shared here...
title aint much clear to know the context


Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null

Following the 'full example' I get this error once I scroll while the component where react-simple-infinite-scroll lies has been unmount.
I assume the error has to do with not removing the event listener to scroll - which should be done once the component containing the infinite scroll is unmounted. This seems to be coupled with how the sentinel object is handled, which is mentioned in the DOCS. It is unclear how it should be used, however.
This, to me, seems like a DOC issue if anything. I think this issue has been accounted for. It is just not properly communicated in the DOCS.

Hi @hazirmagron
I'm guessing you downloaded the package from npm? If this is true, the problem you are talking about was fixed in https://github.com/jaredpalmer/react-simple-infinite-scroll/pull/1 but was never published to npm, current version in npm is the original version v0.0.1, a lot has changed since then. Let me know if I'm correct.
Either way we have to publish a new version of this module to npm. @jaredpalmer I vote for bumping up from 0.x to 1.0.0 due to the latest updates and then publish.

Hi @pgarciacamou!
Yes, you're very much right. I did install it through npm. Makes sense how you communicated on the DOC then. Yes, update the npm version please. It is a very messy and annoying bug.

@hazirmagron so, I had an idea (sorry in advance 🙉)
I honestly believe that @jaredpalmer is super busy with react itself so, what I would suggest is to fork this repo and install from git. This is what you would need to do:

Fork this repo
Clone the fork to your file system
Remove lib from .gitignore: https://github.com/jaredpalmer/react-simple-infinite-scroll/blob/master/.gitignore#L2
run yarn install && npm run build
commit and push to your git fork (preferably to a descriptive branch like temp-fork
install to your repo via:

npm install --save username/repo#branch-name

# like:
npm install --save pgarciacamou/react-simple-infinite-scroll#temp-fork

Note that I haven't tried this and this is only a temporary solution, but Jared hasn't answered my messages so that is the best I've got.
Let me know if you have any questions.

@pgarciacamou that worked for me, thanks 😄

If anyone's interested, I published the fixed version of this package here: https://www.npmjs.com/package/react-simple-infinite-scroll-patched

If anyone's interested, I published the fixed version of this package here: https://www.npmjs.com/package/react-simple-infinite-scroll-patched

@iest I tried your patch and I'm getting duplicate key issues, meaning that my queries aren't being throttled.  I wasn't having this issue with v.0.0.1.  Any ideas?

It's because v0.0.2 includes this PR was merged in, but it's buggy.


The default installation will use an alternative x:\ProgramData\ssh\administrators_authorized_keys for admin users.

The default sshd_config will check an alternative authorized_keys file for users in the Administrators group. You will need to create this x:\ProgramData\ssh\administrators_authorized_keys file and set permissions appropriately (see for example https://docs.microsoft.com/en-us/windows/iot-core/connect-your-device/ssh )

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

ID: 337c4ea8-1806-92a3-1501-b3ff5dde37bb
Version Independent ID: c411d389-578d-57c6-cd6e-eaca7f2837db
Content: OpenSSH Server Configuration for Windows
Content Source: WindowsServerDocs/administration/OpenSSH/OpenSSH_KeyManagement.md
GitHub Login: @maertendMSFT

I just realized that this document is for Windows Server - I was using it to configure the Windows 10 Pro OpenSSH server optional feature, so my comment may or may not be applicable.

Make sure that the .ssh directory exists in your server's home folder
ssh user1<EMAIL_ADDRESS>mkdir C:\users\user1.ssh\
Use scp to opy the public key file generated previously to authorized_keys on your server
scp C:\Users\user1.ssh\id_ed25519.pub user1@domain1@contoso.com:C:\Users\user1.ssh\authorized_keys
Appropriately ACL the authorized_keys file on your server
ssh --% user1<EMAIL_ADDRESS>powershell -c $ConfirmPreference = 'None';

In my build of Windows Server 2019 (17763), I am unable to log in using the Administrator account unless if I comment out these two lines in the C:\ProgramData\ssh\sshd_config file:
Match Group administrators
AuthorizedKeysFile __PROGRAMDATA__/ssh/administrators_authorized_keys

You might also need to restart the OpenSSH server by executing Restart-Service sshd in Powershell after editing the file.
I attempted to create a duplicate of C:\Users\Administrator\.ssh\authorized_keys under C:\ProgramData\ssh\administrators_authorized_keys but this did not work for me.

@dzmitry-lahoda In order to do that you will probably need to run Powershell as administrator (right click -> Run as administrator) or use the runas command to escalate privileges.

@dzmitry-lahoda I have no idea if this will work (don't have a test setup to try it myself right now) but perhaps you could try this?
runas /user:administrator "powershell Restart-Service sshd"

I have put my key into administrators_authorized_keys, i did delete key from authorized_keys, allowed Match Group administrators group and  did restart of sshd service on server.  Tried on ssh from admin pwsh on client and got refusal to connect by credentials. I will try again with steps and recheck. The idea is next - I need my ssh session into remote to be admin to work with services, but I did no achieve that yet. My ssh connection is not admin now. I do not want to use windows password into remote each time I want to be admin. May be I can make service work to be lower security work instead of being admin.

@dzmitry-lahoda I do agree with you that this is not convenient but this is also very similar to how things work on *nix systems (login as root not allowed, always login as regular user and use sudo to escalate privileges as necessary). I think what Microsoft is trying to do here is in line with what is considered to be best practices.

If you're having issues or working on fixing documentation or scripts, check out https://stackoverflow.com/q/16212816/771768

This is a very English centric windows language centric default and FAILS on windows installations other than English.
They should make it possible, and set it to default, for the group match to check for the Administrators SID instead and not the text string as that can be different depending on the language in use of the windows installation.
Change the current Match rule to something like this:
Match Group *S-1-5-32-544
    AuthorizedKeysFile __PROGRAMDATA__/ssh/administrators_authorized_keys

This would be a much better and windows language installation agnostic setting and should be the default, not a per language adapted string.
And for the DenyGroups settings this should also be allowing it to be done via SIDs and NOT by text strings that change and vary.
( also see https://github.com/PowerShell/Win32-OpenSSH/issues/1324#issuecomment-771506890 and https://github.com/PowerShell/Win32-OpenSSH/issues/1581#issuecomment-771512156 )

#please-close


Switch to tomllib

This allows for clean, in place edits of Cargo.toml that retain all formatting and comments.
Closes #1

Wow this is fantastic! I just noticed this and I'm about to go to sleep. I'll give this a test tomorrow and merge it in. Been meaning to get back to this project but just hasn't been top priority. Thank you so much for sending this. I learned a couple techniques I didn't know about that will make the code cleaner for sure.

Just pushed a small refactoring. Let me know if there's anything else I can do to help get this merged. Thanks!

ping

@wraithan Still interested in getting this merged! Let me know if there's anything I can do to help 😄

I guess I'll get to this soon. You also did rewriting when you made the PR instead of just updating the lib which makes it so I have to double check more stuff, part of what made me put off (then forget) about this PR.

@tshepang Please never do that on one of my repos again, you are not owed my attention.
@lukesteensen I'm merging this now. I didn't back then because it'd been months since I'd thought about the project when you sent the PR, and I've not needed it at all since that point. I'd saw that you rewrote about half the project and that meant vetting it more.

@wraithan Yes, unfortunately, the new library's API was significantly different from the old library and that made the required changes more invasive than I would have liked. I appreciate you taking the time to look at it and get it merged.

Nah, I totally get it now that I've actually read the changes and saw how different the API was (and how bad my code is/was)

This has been published as cargo-bump 1.0.0 on crates.io

Thank you!

@wraithan didn't mean to offend. How do you prefer I should have done it?

If you were hoping to get this merged faster you could say something like "tried this on latest rust and it still works" or w/e since code that isn't landed can bitrot and there is nothing on here saying I'd confirmed it worked. Basically offer to help make something happen. Not offering and just pinging is the same as demanding I do completely free work and I view that as incredibly rude.

I thought it was more how I asked it than what I asked for... e.g. "Hey, any updates on this?" would be preferable to "ping".

BTW I saw that one here https://github.com/rust-lang/rfcs/issues/929#issuecomment-321831050

Rust is a language that is worked on by paid developers, some of which are making pretty good money. It isn't exclusively folks that are paid but they do have paid support. On the other hand I'm not employed and am spending as much of my time as I can on my own projects before I'm forced to take on another job. Asking me for free work without offering anything would bother me, doing it with the self entitled "ping" makes it worse.

Remember you are not talking to an organization, collective, or group. It is just my name on the repo owners, and I'm not paid to maintain this. I got it working as well as I needed at the time. I did owe it to lukesteensen and joelself to investigate and merge this request. But you are neither of them and weren't offering help, just a demand of attention and work.

Deleted my responses.
Honestly, I feel very stressed out and depressed lately and your "ping" rubbed me the wrong way. I took out frustration on you and that's not fair. I don't think you should go around and ping random PRs to get folks to do work for you. I think you should offer help if you'd like something to happen or move along. I've had a few folks try to inject their needs into my projects lately (one person from a company that brings in 100s of millions/year wanted me to add a protocol to a database I was building so they could use it, for example) so you ended up bearing the brunt of my frustration. Sorry about that, and I hope I haven't tainted your open source experience too much.

I feel it is legitimate for one to simply ask for an update, and I've even seen projects encouraging it. It is also legitimate to ask for contributions. The tough thing is trying to not offend people... even asking someone pleading for a feature to implement that feature themselves is not easy, and any response is probably guaranteed to offend someone (e.g. "patches accepted!").
Also, trying not to offend people can be such hard work, and not always worth the effort. But I will from now on just do a "any update?" instead of "ping". Offering to do the work is not always practical... sometimes you ask for an update out of curiosity, and sometimes you may not care enough to do said work. Also, some maintainers do appreciate a ping, for it is some indication of interest, and enough motivation to do said work. I think it's still good to ask people to do work of course... it's worked on me before.

Then we fundamentally disagree, open source is exploitive enough as it is
in my opinion. Folks are expected to write free/open software in order to
get jobs and whatnot, companies use free/open software to make literally
trillions of dollars and almost none of that (statistically) is funneled
back into the actual projects they use. After over a decade+ of open source
work I'm 100% over anyone who isn't going to either pay me to add stuff or
offer too help.
On Aug 13, 2017 6:16 AM, "Tshepang Lekhonkhobe"<EMAIL_ADDRESS>wrote:

I feel it is legitimate for one to simply ask for an update, and I've even
seen projects encouraging it. It is also legitimate to ask for
contributions. The tough thing is trying to not offend people... even
asking someone pleading for a feature to implement that feature themselves
is not easy, and any response is probably guaranteed to offend someone
(e.g. "patches accepted!").
Also, trying not to offend people can be such hard work, and not always
worth the effort. But I will from now on just do a "any update?" instead of
"ping". Offering to do the work is not always practical... sometimes you
ask for an update out of curiosity, and sometimes you may not care enough
to do said work. Also, some maintainers do appreciate a ping, for it is
some indication of interest, and enough motivation to do said work. I think
it's still good to ask people to do work of course... it's worked on me
before.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wraithan/cargo-bump/pull/4#issuecomment-322041620,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFjEhGF9jnQitEIw9FDRDuT1-lJpKoxks5sXvc2gaJpZM4KUVDi
.

It is indeed a sad state that companies mostly contribute nothing to floss they rely on, to the point where the idea is hardly even discussed.

Deleted some discussion that didn't really pertain to the PR to clean things up.


Add automated retries to ss2 tasks (790)

See https://elastc.com/c/dkauyyIF/790-make-ss2-have-cromwell-retries
and related PRs
https://github.com/HumanCellAtlas/pipeline-tools/pull/51
https://github.com/HumanCellAtlas/lira/pull/82

[ ] Added or updated tests
[x] Updated documentation
[x] Applied style guidelines
[x] Considered generalizability beyond our own use case

Hi @rexwangcc - I pushed a new commit to set the default at the workflow level to zero also. The motivation for that is to have mintegration tests run with retries turned off and also for anyone reusing our workflow to have retries turned off unless they deliberately choose to turn them on. Let me know what you think.

It does make sense to me given the generalizability beyond our own use case, as long as we could use the Lira config to control it. Thanks for making the change @dshiga !


collectionView.contentSize.height is always 0, fix bei using ollectio…

…nView.collectionViewLayout.collectionViewContentSize.height
Changes in this pull request
Issue fixed: https://github.com/Instagram/IGListKit/issues/1250
Checklist

[x ] All tests pass. Demo project builds and runs.
[ ] I added tests, an experiment, or detailed why my change isn't tested.
[ ] I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
[ ] I have reviewed the contributing guide

@bluesource can you add a failing unit test that this change passes?
Sent with GitHawk

Since the author never got back to us, I think it's fine to close this now.
@bluesource If you think this PR is still relevant, feel free to re-open. Thanks!


Wrong monetary value

Monetary value disregards the first purchase value. I though that this how it supposed to work, but in documentation it is mentioned that the denominator of the monetary value calculation will differ from the frequency number, implying the the first purchase value and count is included in calculation. Am I understanding it wrong?

Can you link / copy-paste the text in question?

I believe @s4935324 is referring to this section of the CLV Quickstart, which was mostly copy/pasted from lifetimes and could probably benefit from other additions like the utility functions of this library and a mention of how other models like ShiftedBetaGeoModel are used.


legitimate site blocked: www.catholic.com & go.dynamiccatholic.com

Neither www.catholic.com nor go.dynamiccatholic.com should be on this list.
Thanks.

www.catholic.com

www.catholic.com isn't found in the list, but wvw.catholic.com is. Note the wVw.
Details matter.

Hi Ron @KK1L thank you for this.
So we're clear, there are no "legitimate" domains here.
It doesn't matter if a domain belongs to the Holy Sisters relict of Mother Theresa of Calcutta. If the domain employs scum practices, or vehicles crapware or worse, they get listed here.
These domains come to us frum upstream, via the AdguardTeam cname trackers. These are sites that use their domains (like wvw.catholic.com) to serve content from another domain entirely.  Makes it look like it comes from in-house, but it doesn't.  That's not cool here.
The AdguardTeam cname trackers issues are here: https://github.com/AdguardTeam/cname-trackers/issues.  Good luck with that. I'm predicting this isn't going to change.

Closing.


Feature/morphing

@yalania what's the status of this? I know that artists are not doing morphing, but can we merge this?


App crash after requesting camera permission

The allow/deny permission appears, requesting access to the camera. Click 'allow' and the app crashes with the message 'Value cannot be null. Parameter name: handle'.
On a second run through the permission has already been granted and the camera opens correctly.
Anyone else had this happen?

In Android MainActivity.cs , in OnRequestPermissionsResult function , replace
global::ZXing.Net.Mobile.Forms.Android.PermissionsHandler.OnRequestPermissionsResult(requestCode, permissions, grantResults);
with
ZXing.Net.Mobile.Android.PermissionsHandler.OnRequestPermissionsResult(requestCode, permissions, grantResults);
It should be ok now.

Thanks for the reply.
I'm not using Xamarin Forms so I don't have the global line to change.
I installed version 2.3.1 and had the same problem. If I allow Zxing to deal with the permission request itself I get the same "Value cannot be null" message.

I just subscribed to this issue this morning. I can confirm that the workaround suggested by @sbirdius works for XF. I'm using Xamarin Forms <IP_ADDRESS>3944. I downgraded ZXing.Net.Mobile and ZXing.Net.Mobile.Forms from 2.4.1 to 2.3.1 (in my PCL and Android projects) and the issue no longer appears.

I'm having this issue with Xamarin Forms too. I was using 2.4.1 and tried downgrading to 2.3.1, but it didn't fix the problem. Is there anyone maintaining this project?

Im having this same issue with 2.4.1 running Xamarin.Forms 3.1.  Crash after permission request on Android 6 Samsung Galaxy 6.

Thanks for reporting this issue!  Unforunately it took me way too long to respond 😭.  Sorry, I apologize!  Recently the source code for this project was completely refactored to modernize it.  Many PR's were included in this effort, and many bugs were hopefully fixed.  Please try out the latest 3.x series of NuGet packages (currently in prerelease).  To try and make the project more maintainable in my spare time going forward, I've decided to close all existing issues to start with a clean slate.  If you're still experiencing this issue on the newest version, please open a new issue with as much detail as possible.  Thank you for your patience and understanding!  Happy scanning!

I moved on to firebase ML for barcode scanning. Microsoft made bindings nugets for iOS and Android. It works great and is free.


Show select list for crete command

This is a nice feature :+1:

Hey @WSMathias , If you specify exact starterkit using --starterkit, will vega still show the survey prompt?

If possible, then you can try to reuse the code: https://github.com/srijanone/vega/blob/develop/cmd/install.go#L49

@vs4vijay  No, it won't show prompt for exact match and a single match.


[Line Awesome]-> Icons

Line Awesome
is a free alternative for Font Awesome, flat icons that offer complete coverage of the main Font Awesome icon set.
Link: https://icons8.com/line-awesome/
Checklist:

[ ] I have performed a self-review of submitted resource and its follows the guidelines of the project.

This should be in "Icon Font" category

This should be in "Icon Font" category

Sure

this is repeat in Icon Fonts section.
I just realized
I don't know how change file. I going for new pull request