chef-provisioning bootstrap fails

* machine[chef-test] action converge[2015-06-04T13:49:51-04:00] INFO: Processing machine[chef-test] action converge (chef-provisioning-aws::default line 76)
[2015-06-04T13:49:51-04:00] INFO: HTTP Request Returned 404 Not Found: Object not found: chefzero://localhost:8889/nodes/chef-test
[2015-06-04T13:49:52-04:00] INFO: [AWS EC2 200 0.047598 0 retries] describe_images(:filters=>[{:name=>"image-id",:values=>["ami-96a818fe"]}])

[2015-06-04T13:49:52-04:00] INFO: [AWS EC2 200 0.110825 0 retries] describe_subnets(:subnet_ids=>["subnet-b91f8e92"])

[2015-06-04T13:49:52-04:00] INFO: [AWS EC2 200 0.090261 0 retries] describe_security_groups(:filters=>[{:name=>"group-name",:values=>["chef-security"]}])

[2015-06-04T13:49:52-04:00] INFO: [AWS EC2 200 0.088226 0 retries] describe_security_groups(:filters=>[{:name=>"group-id",:values=>["sg-d2bab1b6"]}])

[2015-06-04T13:49:52-04:00] INFO: [AWS EC2 200 0.620739 0 retries] run_instances(:client_token=>"92037a52-01ec-407e-85ea-398787253b31",:image_id=>"ami-96a818fe",:instance_type=>"t2.micro",:key_name=>"chefmaster",:max_count=>1,:min_count=>1,:security_group_ids=>["sg-d2bab1b6"],:subnet_id=>"subnet-b91f8e92")

[2015-06-04T13:49:53-04:00] INFO: [AWS EC2 200 0.154175 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:49:53-04:00] INFO: [AWS EC2 200 0.366351 0 retries] create_tags(:resources=>["i-0b0eafa2"],:tags=>[{:key=>"Name",:value=>"chef-test"}])

    - Create chef-test with AMI ami-96a818fe in us-east-1[2015-06-04T13:49:53-04:00] INFO: Processing chef_node[chef-test] action create (basic_chef_client::block line 57)
[2015-06-04T13:49:53-04:00] INFO: HTTP Request Returned 404 Not Found: Object not found: chefzero://localhost:8889/nodes/chef-test

    - create node chef-test at chefzero://localhost:8889
    -   add normal.tags = nil
    -   add normal.chef_provisioning = {"reference"=>{"driver_version"=>"1.2.1", "allocated_at"=>"2015-06-04 17:49:53 UTC", "host_node"=>"chefzero://localhost:8889/nodes/", "image_id"=>"ami-96a818fe", "instance_id"=>"i-0b0eafa2", "key_name"=>"chefmaster"}, "driver_url"=>"aws::us-east-1"}[2015-06-04T13:49:53-04:00] INFO: [AWS EC2 200 0.241184 0 retries] describe_instances(:filters=>[{:name=>"instance-id",:values=>["i-0b0eafa2"]}])

[2015-06-04T13:49:53-04:00] INFO: [AWS EC2 200 0.074512 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:49:53-04:00] INFO: [AWS EC2 200 0.087611 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:49:54-04:00] INFO: [AWS EC2 200 0.091764 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:49:54-04:00] INFO: [AWS EC2 200 0.076079 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

    - waiting for chef-test (i-0b0eafa2 on aws::us-east-1) to be ready ...[2015-06-04T13:49:54-04:00] INFO: [AWS EC2 200 0.099122 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

    - been waiting 0/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be ready ...[2015-06-04T13:50:04-04:00] INFO: [AWS EC2 200 0.159721 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

    - been waiting 10/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be ready ...[2015-06-04T13:50:14-04:00] INFO: [AWS EC2 200 0.203543 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

    - been waiting 20/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be ready ...[2015-06-04T13:50:24-04:00] INFO: [AWS EC2 200 0.180368 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:50:24-04:00] INFO: [AWS EC2 200 0.06454 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

    - chef-test is now ready[2015-06-04T13:50:25-04:00] INFO: [AWS EC2 200 0.288192 0 retries] describe_instances(:filters=>[{:name=>"instance-id",:values=>["i-0b0eafa2"]}])

[2015-06-04T13:50:25-04:00] INFO: [AWS EC2 200 0.072165 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:50:25-04:00] INFO: Reading key chefmaster from file /root/chef-repo/.chef/keys/chefmaster.pem
[2015-06-04T13:50:25-04:00] INFO: [AWS EC2 200 0.08972 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:50:25-04:00] INFO: [AWS EC2 200 0.094943 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:50:25-04:00] INFO: [AWS EC2 200 0.06982 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:50:25-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - waiting for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable (transport up and running) ...[2015-06-04T13:50:35-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 0/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:50:55-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 10/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:51:15-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 20/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:51:35-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 30/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:51:55-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 40/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:52:15-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 50/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:52:35-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 60/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:52:55-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 70/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:53:15-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 80/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:53:35-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 90/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:53:55-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 100/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...[2015-06-04T13:54:15-04:00] INFO: Executing sudo pwd on<EMAIL_ADDRESS>
    - been waiting 110/120 -- sleeping 10 seconds for chef-test (i-0b0eafa2 on aws::us-east-1) to be connectable ...
    - chef-test is now connectable[2015-06-04T13:54:35-04:00] INFO: Reading key chefmaster from file /root/chef-repo/.chef/keys/chefmaster.pem
[2015-06-04T13:54:35-04:00] INFO: [AWS EC2 200 0.136261 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:54:35-04:00] INFO: [AWS EC2 200 0.05966 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:54:35-04:00] INFO: [AWS EC2 200 0.070748 0 retries] describe_instances(:instance_ids=>["i-0b0eafa2"])

[2015-06-04T13:54:35-04:00] INFO: Processing chef_node[chef-test] action create (basic_chef_client::block line 57)
[2015-06-04T13:54:35-04:00] INFO: Executing sudo cp /etc/chef/client.pem /tmp/client.pem.722010487 on<EMAIL_ADDRESS>[2015-06-04T13:54:45-04:00] ERROR: Unable to download /etc/chef/client.pem to /tmp/client.pem.722010487 on<EMAIL_ADDRESS>-- execution expired
[2015-06-04T13:54:45-04:00] INFO: Executing sudo rm /tmp/client.pem.722010487 on<EMAIL_ADDRESS>[2015-06-04T13:54:55-04:00] WARN: Unable to clean up /tmp/client.pem.722010487 on<EMAIL_ADDRESS>-- execution expired
[2015-06-04T13:54:55-04:00] INFO: Processing private_key[in_memory] action create (basic_chef_client::block line 78)

    - generate private key (2048 bits)[2015-06-04T13:54:55-04:00] INFO: Executing sudo ls -d /etc/chef/client.pem on<EMAIL_ADDRESS>
    ================================================================================
    Error executing action `converge` on resource 'machine[chef-test]'
    ================================================================================

    Chef::Provisioning::Transport::SSH::InitialConnectTimeout
    ---------------------------------------------------------
    execution expired

    Resource Declaration:
    ---------------------
    # In /root/chef-repo/.chef/local-mode-cache/cache/cookbooks/chef-provisioning-aws/recipes/default.rb

     76: machine 'chef-test' do
     77:   machine_options(
     78:     lazy do
     79:       {
     80:         bootstrap_options: {
     81:           image_id: 'ami-96a818fe',
     82: 	  key_name: 'chefmaster',
     83: 	  instance_type: 't2.micro',
     84: 	  subnet_id: 'DMZ-CHEF',
     85:           security_group_ids: ['chef-security']
     86:         }
     87:       }
     88:     end
     89:   )
     90: end

    Compiled Resource:
    ------------------
    # Declared in /root/chef-repo/.chef/local-mode-cache/cache/cookbooks/chef-provisioning-aws/recipes/default.rb:76:in `from_file'

    machine("chef-test") do
      action :converge
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      chef_server {:chef_server_url=>"chefzero://localhost:8889", :options=>{:client_name=>"administrator", :signing_key_filename=>"/root/chef-repo/.chef/administrator.pem"}}
      driver "aws::us-east-1"
      machine_options #<Chef::DelayedEvaluator:0x0000000bf4ce18@/root/chef-repo/.chef/local-mode-cache/cache/cookbooks/chef-provisioning-aws/recipes/default.rb:78>
      declared_type :machine
      cookbook_name "chef-provisioning-aws"
      recipe_name "default"
    end

[2015-06-04T13:55:05-04:00] INFO: Running queued delayed notifications before re-raising exception

Running handlers:
[2015-06-04T13:55:05-04:00] ERROR: Running exception handlers
Running handlers complete
[2015-06-04T13:55:05-04:00] ERROR: Exception handlers complete
[2015-06-04T13:55:05-04:00] FATAL: Stacktrace dumped to /root/chef-repo/.chef/local-mode-cache/cache/chef-stacktrace.out
Chef Client failed. 7 resources updated in<PHONE_NUMBER>55 seconds
[2015-06-04T13:55:05-04:00] ERROR: machine[chef-test] (chef-provisioning-aws::default line 76) had an error: Chef::Provisioning::Transport::SSH::InitialConnectTimeout: execution expired
[2015-06-04T13:55:07-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

I have used an ami of CentOS but its taking an ubuntu user to login. how i change that. Machine has been created with all the parameters its only failing at the bootstrap, coz its using a diff user.
please suggest.
thank you.

Hey @kothapallyn - please see the ssh_username key from https://github.com/chef/chef-provisioning#machine-options for how to specify an SSH user.  And re-open or file another issue if this doesn't fix your issue!


Can it block erotic text?

I am especially interested in furry, gay porn, nipples, feets, chest

No it does not


Fixing argument for cosmos_db_trigger decorator

Fixing argument for cosmos_db_trigger decorator.

@ggailey777
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

emailed GG

emailed author

sent reminder to ggailey777

sent reminder to ggailey777

emailed author

Pull requests can't be reviewed when there are merge conflicts. After you resolve the conflicts, you can sign off again.  The file in question is concepts-single-to-flexible.md.
For help with resolving merge conflicts, refer to the Contributor Guide, or try the Platform Support channel in Teams.

The file structure has changed and it looks like this PR is no longer valid.


Update code for SKLL 2.5+

This PR resolves #72, resolves #73, and resolves #74.

To use SKLL 2.5+, we made the following changes:

Modify prune_model() to operate correctly and includes the StandardScaler() estimator in the pruning process.
Use the updated API signature for Learner.predict() to get class probabilites.
Replace the deprecated log field in SKLL configuration files with its new name logs.

Other  changes:

Return the correct number of empty lists when no trees are specified (Issue: #74). Update the corresponding test to match.
Updated environment.yaml file to pin SKLL to v2.5+.
Drop support for Python 3.6 and adding support for Python 3.9. Updated .gitlab-ci.yml as well as the files under .ci_support.
Update ETS-internal CI bamoo build plan to use Python 3.8 and pinned SKLL to exactly v2.5 as that’s what we are still using at ETS.
Minor changes to the codebase to resolve flake8 and pydocstyle errors.

Not sure why this isn’t updating but the builds have passed just fine: https://gitlab.com/EducationalTestingService/rstfinder/-/pipelines

@damien2012eng @bndgyawali please re-approve.


Admin interface for Benitlux and fixes

This PR adds a RESTful admin interface to the Benitlux server. This interface is used to trigger sending out the daily menu notifications from an external program / cron.
As a fix to the diff showing everything as new on the menu, the server now standardizes the received dates to the format expected by SQLite. There is also a small fix to the library used by the code generated by nitrestful to correctly check for errors.

+1

:shipit:

Reroll to fix tests.


New issue Tab key not working after opening two Sweet Alert Modals in a row

As mentioned in t4t5/sweetalert#127. Tab key is screwed up if opening two swal modals in a row.
This https://github.com/t4t5/sweetalert/issues/127#issuecomment-136958062 workaround works.

Can't reproduce this bug. Please specify steps to reprodyce so I can fix it or send pull request :)


Can we fix the failing module.yaml change

Can we fix the failing module.yaml change

its fixed, but failing test, due to common services issue on the cluster. I've already raised an issue https://github.ibm.com/gsi-labs/industry-cloud-planning/issues/820 to recreate the cluster.

Fixed the common services issue on CP4I cluster, now ES passed successfully.


Autostaking script can batch up a lot more transactions

Currently we send one TX per delegator, which includes a single MsgExec TX with the two messages inside to withdraw and delegate.
There's no reason we can't send multiple MsgExec in a single transaction. Just need to work out how many is reasonable to include in a single batch

This will speed up the script a lot if we can do 10x or bigger batches, and should also save validator gas fees

If we can do this in one TX we can track when the validator last ran it, and even validate each delegator had their autostake run.
We can kinda do that anyway but it'll be a lot more reliable with one TX. Surely we must hit a block limit eventually so need to work out batch size + analytics from there

Chain max gas limit param is what we need here, should be able to get this from the API

100x batches added in #293


chore(deps): update common-dev-assets digest to e492ef5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
b208c35 -> e492ef5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


print command not working on IPython console

From<EMAIL_ADDRESS>on 2015-01-12T05:59:30Z
Spyder Version:  2.3.2
Python Version:  2.7.6
Qt Version    :  4.8.6, PyQt4 (API v2) 4.10.4 on Linux
pyflakes >=0.5.0:  0.8.1 (OK)
pep8 >=0.6      :  1.4.6 (OK)
IPython >=0.13  :  1.2.1 (OK)
zmq >=2.1.11    :  14.0.1 (OK)
pygments >=1.6  :  1.6 (OK)
pandas >=0.13.1 :  0.15.2 (OK)
sphinx >=0.6.6  :  1.2.2 (OK)
psutil >=0.3    :  1.2.1 (OK)
rope >=0.9.2    :  0.9.2 (OK)
matplotlib >=1.0:  1.4.2 (OK)
sympy >=0.7.0   :  <IP_ADDRESS> (OK)
pylint >=0.25   :  1.1.0 (OK)
What steps will reproduce the problem?
Printing anything using "print 'Foo'"
What is the expected output? What do you see instead?
Normally the printed argument should appear on the IPython console as it did before I updated to version 2.3.2.. But nothing appears..
Please provide any additional information below
. If I address objects directly on the console, let's say a pandas dataframe object with "df.head()" everything works fine..
OS: Ubuntu 14.04
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2110

From ccordoba12 on 2015-02-08T10:38:39Z
No idea what could be the problem, but it seems pretty weird. I'd suggest you to report it with the IPython guys because we just embed IPython, with some minimal changes.
Status: WontFix


Doesn't work with terraform v1.12

Using the latest version of both terraform (1.12.4) and the dd-cloud provider (2.2.2).
After performing a terraform init, a terraform plan displays the following error
$ ./terraform plan -out tf.plan

Error: Failed to instantiate provider "ddcloud" to obtain schema: Incompatible API version with plugin. Plugin version: 4, Client versions: [5]```

Worked successfully with older version of terraform (1.11.14)

terraform v1.12 not supported at this stage. works required.

Hi. @samuelchong  Can you please give an update. It's November and Terraform is now up to v1.12.16.     I'd prefer to be using a version of 1.12.x instead of 1.11.x

I will get to that when I have bandwidth.

@adrianvolpe - Theres an open PR for this now - but if you want to test it right now, feel free to build the provider yourself. I've run it through acceptance tests with no major issues.

Thx @nwright-nz. I've released a beta build. v3.0.1.


which dotnet core is required?

i am on macos
do i need dotnet core 5.0 or 3.1?

currently i have this installed:

We have build the API in NETStandard 2.0 this should be part of both, but for the unit tests we used NET Core 3.1
https://github.com/dotmog/SubstrateNetApi/blob/61ae33321d0b3ac369bd704c3b4db97645308e6d/SubstrateNetApi/SubstrateNetApi.csproj#L4
https://github.com/dotmog/SubstrateNetApi/blob/61ae33321d0b3ac369bd704c3b4db97645308e6d/SubstrateNetApiTest/SubstrateNetApiTests.csproj#L4
So I would suggest .NET Core 3.1


How to use a new type of plug-in to customize charts?

The old type plug-in dependency viz.py returns data, but the new type plug-in no longer depends on it (adding a new class to it is invalid). Can you provide us with some solutions so that we can achieve our previous goal?

The codebase on this repo has been moved to the main Apache Superset repo, and consequently the repo is in the process of being archived. See the Superset Improvement Proposal for details: https://github.com/apache/superset/issues/13013 . While all currently open issues and PRs will be closed, we encourage you to reopen this issue on the main repo if it is still relevant.


Lowercase scopes fix 2.0

This PR addresses the same issues as in PR #1945 . Msal-common currently converts scopes from the user to lowercase for caching and for network requests. This behavior can cause issues with some backends that have case-sensitive audience validation.
This PR ensures that scopes in ScopeSet are trimmed without being converted to lowercase, while used for requests, and intersection and union functions. Caching of scopes continues to be in lowercase.

Coverage increased (+0.004%) to 81.005% when pulling efcde2d658b52f534ffade5e1749470f3a8a46ed on lowercase-scopes-fix-2.0 into 4569e412729a927f697a7b5f735a5cee2eac161f on dev.


ReuseExchange will not be used in Physical Plan when cache enabled for Parquet format

For tpcds Q2, Q47, Q59, there will duplicated table scan and additional join. After check Physical Plan, there's no ReuseExchange optimization. This issue only occur when cache enable and use parquet.

@JkSelf
Would  you help track this issue?

@LuciferYang @ivoson
Have you encountered this issue?
Thanks.

I haven't noticed that, but I think  we can use an existing test suite of spark to check this

@zhixingheyi-tian We also found this problem in the tpc-ds test

"""
test("reuse exchange") {
withSQLConf("spark.sql.autoBroadcastJoinThreshold" -> "2",
OapConf.OAP_PARQUET_BINARY_DATA_CACHE_ENABLED.key -> "true") {
val data: Seq[(Int, String)] = (1 to 300).map { i => (i, s"this is test $i") }
data.toDF("key", "value").createOrReplaceTempView("t")
sql("insert overwrite table parquet_test select * from t")
val df = sql("select * from parquet_test")
val join = df.join(df, "a")
val broadcasted = broadcast(join)
val join2 = join.join(broadcasted, "a").join(broadcasted, "a")
join2.explain()
assert(
join2.queryExecution.executedPlan
.collect { case _: ReusedExchangeExec => true }.size == 4)
}
}
"""
This test suite will failed when  OapConf.OAP_PARQUET_BINARY_DATA_CACHE_ENABLED.key is true，and success when OapConf.OAP_PARQUET_BINARY_DATA_CACHE_ENABLED.key is false

@zhixingheyi-tian Oap can not hit ReusedExchangeExec optimization because the equals method is not overridden in OptimizedParquetFileFormat,OptimizedOrcFileFormat and OapFileFormat


Issue when unlocking/locking a VC

Describe the bug
When trying to lock a VC i get the screen for passcode (works OK) and then the screen for OTP. When entering OTP (111111) nothing happens and I remain on the same screen, the only way to exit is to close and reopen the app. After reopening the app the VC has been unlocked, so operation has worked.
To Reproduce
Steps to reproduce the behavior:

Go to VC
Click on three dots and select "Unlock"
Enter passcode
Enter OTP
Note that nothing happens
Close and reopen app
Enter VC, click three dots and note that it now says "Unlock"

Expected behavior
App should proceed when OTP has been entered
Reproduced on
0.3.0 RC1

Verified on test build. Working as expected.


Radio buttons in repeaters 'stealing' selected status from each other

Reproduction
https://formkit.link/ac50f9736dc092ca2dfea003ccb95258
Describe the bug
Here's a quick screen recording of the issue:
https://github.com/formkit/formkit/assets/8395303/f7b33fe2-7eca-4cb3-bc0a-8f85ba04e836
With radio buttons in repeaters, the radios seem to 'steal' the selected state of a different repeater child's radio of the same name. I'm pretty sure I've got everything setup correctly in the playground.
To reproduce:

add a repeater item so there's more than one item
select a radio button in the first repeater
select a radio from a different repeater item's radio: there will be a single radio showing as selected

Interestingly, the data / conditional fields relying on the input remain as they should, so I'm hopeful this is more of a visual issue.
There's a further issue viewable in the playground - if you re-order a repeated item that has conditionals attached, toggling the radio impacts a different repeater to the one changed. I presume this is due to the way I'm using the $index in the ID, but would be interested in hearing your thoughts on how this could be overcome. Think this is a bug or something I'm doing wrong in my code?
One final note, I've not found any docs on how to handle conditionals within repeaters. In our real world case, we've got nested repeaters, with conditions relying on both the inner and outer data. It's proving tricky ascertaining how to get ahold of what and where, and it would be lovely to read a bit more on how to tackle this (apologies if I've missed in the docs) :) In the case in the playground, I've used the $index in the IDs, but I'm not sure that's a great idea, and it wouldn't allow to access any outer repeater scope? All advice welcomed graciously.
Environment
• OS: Ventura 13.5.1
• Browser Chrome Version 119.0.6045.159
• Version Formkit 1.3

Not sure why this isn't being done automatically which It is supossed to do on repeaters, but for radios you need a unique name so we have a internal altName property for these specific cases, for now as a workaround you can do this simple plugin: https://formkit.link/2a83c9feba9c926bd313c41b61dde836

Brilliant, thanks @fenilli - that solves the first part!
Still got an issue with the second part though, e.g. https://formkit.link/ac50f9736dc092ca2dfea003ccb95258.
To reproduce:

Select option 'Two'
Add a repeater
Use the controls to move the first repeater down (or second repeater up)

The result is that the new first item acts as if the condition is met for 'Two' being selected, despite there being no selection, while the new second item acts as if nothing is selected.
Any advise on this one / how to handle IDs for conditionals in repeaters?

When inside a scope you can just do $value.rad instead, if you "bake" the index into it when you change it might have some strange behaviours.

Thanks @fenilli - agree having the index in the identifiers doesn't seem the way to go, though I was lacking for any other solution.
Sounds like $value.rad will be what I need then, but I can't find any info / documentation on what it does - are you able to point me in the right direction please?

This 100% should just work. We’ll look into it.

Resolved in 1.4.0 👍


Fix reconnection and rebase bugs in PropertyDDS

Description
This PR fixes three bugs in the PropertyDDS:

When a client goes offline and reconnects later, it could happen that messages are submitted which reference previous changes that are no longer within the collaboration window have been pruned in the last summary. With this patch, we will now submit a rebased version of these old operations to make sure the reference operation is within the collaboration window.
There is a scenario, where the rebased local operations do not exactly match the received remote operation. This can happen when changes in the base cancel out (i.e. if there is a remove/insert combination). In this case, if you rebase across the squased changeset within the remote changes, a modification will be preserved. However, if you rebase separately across remove and then insert a modification will be lost. We did not correctly take this into account in the function that removes local operations, once they have been confirmed from the server. We just assumed that they will always be exactly the same, now we perform a rebase if necessary.
There was a bug in the rebased code, that did not correctly handle the case when a modification was rebased with respect to a insert/remove operation. This case was supposed to remove the modification (because it was assumed to apply to the removed entry and might make no sense in the new context any longer). Due to the bug, the modification was not correctly removed.

Breaking Changes
I modified the MockContainerRuntimeFactoryForReconnection to take into account that a client that is no longer connected will not be considered when computing the minimum sequence number on the server. I think this behaviour is more realistic and at least in my case it was necessary to reproduce the bug. Still, this will also affect other tests that are based on this class and introduce this modified behaviour in those tests. If this is not desired, we could make this optional.
A second aspect to consider here is, that this PR changes the behaviour of the rebase for the third of the cases described above. So if multiple clients on the same documetn are using different versions of the DDS, they might get out of sync, since they resolve the rebases differently. How should we handle such a situation?
Reviewer Guidance
The review process is outlined on this wiki page.

The change to the testing utities leads to several failed tests in the sequence calls. I am not entirely sure, but I think this could indicate that the sequence DDS also has a bug where reconnects are not correctly handled if a change falls out of the collaboration window. Could anybody who knows the internals of the sequence class investigate this?

TypeError: Cannot read properties of undefined (reading 'left') (seed 4) looks like a known issue involving local reference positions. Work for this is scheduled for this month.
The 0x54e assert failing is new to me, but does look like a bug in sequence, unrelated to the above issue.
At least in the case of the first issue, it's possible to reproduce the bug without reconnects.

I would skip the specific failing seeds for now. I'll add a note to the ticket to visit these tests when the bug is fixed in sequence.
Support for skipping specific seeds was added in https://github.com/microsoft/FluidFramework/pull/16270 (you may have to merge main), and there's example usage here https://github.com/microsoft/FluidFramework/pull/16258/files#diff-f3bafbcb0a4abc3257ff8b1eb844878dd0a14ebb1b3e53a2ead4dd89e7a86cb3R283

I would skip the specific failing seeds for now. I'll add a note to the ticket to visit these tests when the bug is fixed in sequence.
Support for skipping specific seeds was added in #16270 (you may have to merge main), and there's example usage here https://github.com/microsoft/FluidFramework/pull/16258/files#diff-f3bafbcb0a4abc3257ff8b1eb844878dd0a14ebb1b3e53a2ead4dd89e7a86cb3R283

I have added skips for the failing tests.

@connorskees Hi Connor, is there still anything to be done in this PR? Could it be merged?

The sequence changes seem fine to me, but I'll ping @CraigMacomber who I think might have more context on merging these sorts of changes.

Regarding:

A second aspect to consider here is, that this PR changes the behaviour of the rebase for the third of the cases described above. So if multiple clients on the same documetn are using different versions of the DDS, they might get out of sync, since they resolve the rebases differently. How should we handle such a situation?

Generally, the approach to take for things like this is to version the DDS's protocol such that if old client encounter the new behavior, they will error. There are two ways I see to do this:

Have a protocol version (or equivalently an op write format) for the dds, following the patterns covered in https://github.com/microsoft/FluidFramework/blob/main/packages/dds/SchemaVersioning.md . Then you get to choose if you want to support the cross version collab (which ideally you would) and thus support some legacy compat mode concurrently with the new mode and let the write format pick which policy is used, and use an op to coordinate updating the policy across all collaborators. Alternatively, you could not support the cross version collab, and update the write format on first edit if needed, and cause old clients to error out. Of course this requires you to have the versioning in place necessary to actually do this: if not you can cheat by using a different data format with is known to crash if you don't have an explicit version number.
Ensure the specific ops which exhibit this difference, if they occur, will cause old clients to error out somehow. I'm not sure if this is practical since the difference is in rebase policy, but sometimes its a valid option (ex: maybe just make all ops in a new format which crashes old clients, though thats really just a alternative way to do the non collaborating version of 1 above).
Hope the desync doesn't happen. Maybe add some mechanism to try and detect if it would have happened to old clients and if so kick them from the document somehow?

@ruiterr I have tried to implement all suggestions from @CraigMacomber, you can find them in https://github.com/ruiterr/FluidFramework/pull/1.
The only thing I didn't work out, as I think it's very important and should be decided by you, is how should we handle a backward incompatibility. Personally, among suggestions from Craig I'd prefer this way

to support the cross version collab and thus support some legacy compat mode concurrently with the new mode and let the write format pick which policy is used, and use an op to coordinate updating the policy across all collaborators.

which seems for me to be the most robust and maintenance-free way of doing this, but of course it's the most costly one. So, up to you.


can't create new post

on arcs-live, select the Write posts, show post list, edit a post, and show details about post. suggestion.
a new arc is created. the text Get started by naming your miniblog and creating your first post! appears, but there is no + button to create a new post.
Weirdness: it's somewhat flaky, it did appear once, but never since.

I believe you but I can't reproduce in ten reloads on Linux.
It's hard coded to 600px wide. Is your window smaller than that?


Implement PipeManagerMaster/Worker

For stream processing, we need to implement PipeManagerMaster and PipeManagerWorker for managing Pipe instead of Block.
Pipe has the following properties and assumptions:

Created when Job starts, cleared when Job completes.
Data transferred via Pipe doesn't remain at the sender side when transferred.

Moved to https://issues.apache.org/jira/browse/NEMO-8.


AKP on F-Droid or IPFS?

Where can I download the Android APK package without Google Store? Can you please add it to F-Droid and/or IFPS?

they won't add it. you must download from Play Store. that's how the app gets more popular

I understand that the app can become more popular on the PlayStore, but you can upload the app ALSO on different place, especially for people that doesn't want to have the google services on their phone for security reason.
I would love to see the app on F-Droid


pmd-ndctl.go: Add start-time check for writable /sys

In Devicemode_direct (alias ndctl), the driver can operate
only if /sys is mounted in read-write mode.
It has been seen however that sometimes container gets
deployed in such a way that /sys is mounted read-only.
It makes sense to detect writable /sys at start-time
and refuse to run, instead of stumbling to that later in operation.

This implements one of two checks proposed in #172

For Devicemode:LVM, we could add similar check in startup phase of pmem-ns-init which needs writable /sys in LVM mode. But, two points suggest we can perhaps skip adding:

pmem-ns-init runs as initContainer, and I haven't yet seen case when /sys is not writable there
if we still hit read-only /sys, initContainer running before actual driver, either:

gets "read-only system" error at namespace creation attempt and exits (clear enough indication),
or, it does not need to create namespaces (set of namespaces exists) and plugin is able to operate in LVM mode on top of existing set of namespaces.

so I think in LVM mode we can live without such start-up stage check

the log in "rw" case is bit of in extra-for-debug-only style, as is also the "check mounts:" trace log above. In final version those two logs could both go away. But do we delete those right here or later, our decision.

Having few log lines once during startup is not too noisy, could provide valuable info about mounts from inside container, so lets keep them and merge.


Describe metrics helpers

Coverage increased (+0.2%) to 85.833% when pulling f8332229d3a774c30797a5f7afbafa8c70dd8dc7 on dissoupov into bcffd8c88e0811dbd5554c06745282cfa8e2e25d on main.


Cannot resolve scoped service 'FluentValidation.IValidatorFactory' from root provider

I'm using ASPNET Core 2.0 on Development environment. If I set ASPNETCORE_ENVIRONMENT to a different value (e.g. Staging) it will work fine.
Here's my current Startup.cs
services.AddMvc()              .AddFluentValidation(options => options.RegisterValidatorsFromAssemblyContaining<Startup>())

Please upgrade to the latest beta release on nuget - that should fix this.

Okay thanks. I just saw Issue#474, would there be an issue if I'll add the factory manually?

That's fine.


Get section from static mesh - crash - Blueprint

Get section from static mesh causes a crash when there is a static mesh applied to the static mesh input. Also, create mesh section causes crash if vert and uv arrays are not the same length (A simple check before creating mesh prevents this)

Hello,
All existing issues for RMCv2 are being closed as RMCv2 is no longer being supported.  RMCv3 is in beta here : https://github.com/Koderz/RuntimeMeshComponent/tree/Version3Dev
If you encounter this or any new issues in v3 please feel free to open a new issue!
Thanks!
-Koderz


Complete Audio Distortion (Static Noise)

It's had been about a month since I last used the program and the last time I used it; it was working perfectly. So today I was using it to cast my phone on my laptop and when I played an audio it started distorting. When I say distorting, I mean when there should be some audio playing, I only hear static noise. I use a GUI called 'guiscrcpy' so I ran the program without the GUI and the results were the same. I was also screen recording the shared window on my laptop and while rewatching the recorded video, there was no distortion.
So, I started searching if there was a new version and found out that scrcpy-v2.1 was out about 3 weeks ago. So, I downloaded the zip file, extracted it and ran the program, but the audio is still distorted.
Any suggestion on how to solve this issue?
If needed, my phone is "Realme 9 pro+" and it is currently running Stable Android 13.
This was recorded from my phone and you can hear the level of audio distortion. (Forward to 6 seconds)
https://github.com/Genymobile/scrcpy/assets/117034077/ae45f12f-2256-4607-9a59-f0e3c1e47193
This is the recorded screen of my phone from my laptop and you can hear that there is no distortion. (Forward to 3 Seconds)
https://github.com/Genymobile/scrcpy/assets/117034077/fbb1601e-8fcb-47f4-b91e-b83ae4d59adb

Is it better with scrcpy --audio-output-buffer=10? (#3793)

Is it better with scrcpy --audio-output-buffer=10? (#3793)

Thanks that solved the issue.

Because the video is in H.265 that your browser cannot play. However, if you download the video and play it with a player with H.265 support, it works.

Thanks, I didn't know that so I re-uploaded the video in H.264.


Rancher suggests users upgrade the k3s-packaged Traefik chart, breaking ingress

Copied from https://github.com/rancher/partner-charts/issues/220 for visibility.
A recent PR added a Traefik chart to partner-charts:

https://github.com/rancher/partner-charts/pull/205

K3s also packages Traefik. If you go into Installed Apps in Apps and Marketplace, there is an option to update it:

If the user clicks through the new version, the chart upgrade will succeed, but the traefik pod will go into ImagePullBackoff because the tag used by version 10.6.0 of the chart (v2.5.3) is not mirrored in the rancher Docker Hub org. This will leave the ingress broken and (if it is being used to access Rancher) lock the user out of Rancher. At this point the user would have to either restart k3s (so that the packaged chart is reinstalled), use kubectl to fix the deployment image tag, or helm to roll back the chart update.
I believe that the Rancher UI should not offer upgrades to K3s or RKE2 packaged components. Especially not on the local cluster.
Originally reported on Users Slack at https://rancher-users.slack.com/archives/C3ASABBD1/p1634871651031000

@brandond do you have any repro steps for getting to a state where kube-system traefik will prompt for update? I'm having issues replicating, but I suspect that I'm missing something in my setup

Shouldn't take anything more than simply installing Rancher 2.6 on K3s.

@brandond per https://github.com/rancher/dashboard/pull/4621#issuecomment-976954111, the UI team would like a new annotation so that this would work without having to update this chart with workarounds:

It looks like k3s added [ab]using the bundle-id annotation to the k3s charts, so why do we need to add looking at hidden? I don't love forever abusing both of these to have a new meaning of "it's not really fleet but we want it to be treated as not-upgradable" vs adding a new descriptive annotation to explicitly disable upgrade.

There are other ways to handle the existing installs, like applying a new annotation to the apps you're worried about during the upgrade, or just ignoring the problem of existing ones and fixing it going forward.

Is that doable at the backend? If so, would you like an issue filed to work on that?

Filed https://github.com/rancher/rancher/issues/36350 with backend since no update from question in comments.
@MKlimuszka I put an area2 label on that item with 2.6.4 as the milestone. Hopefully this is as easy as what's in the other charts though I know it's a longstanding thing that's been around.

Hey @gaktive - just a heads up, team 2 is going to be @Sahota1225. I am talking with her now and she is going to triage it with the team and consider it for v2.6.4.

This has been fixed for the single chart that K3s packages, but on the RKE2 side our chart building process is a bit more complex and it hasn't been addressed yet.

Backend work moved over to Team 3.

Based on discussion, we should expect 2 new tickets: one for k3s to create a new annotation (catalog.cattle.io.managed=true or something of that ilk), which should unblock UI work, and another for RKE2 to take that annotation to then edit the bundled charts.
@PennyScissors will do the k3s ticket, which would then spawn the rke2 work via @brandond

Verified on v2.6-head https://github.com/rancher/rancher/commit/a478def06ee49ff6f36c37c0444c550ef82a9c67.
ENVIRONMENT DETAILS

Linode Ubuntu 20.04 VM
Docker install: 20.10
Rancher version: v2.6-head https://github.com/rancher/rancher/commit/a478def06ee49ff6f36c37c0444c550ef82a9c67
K3s version: v1.22.8+k3s1

TEST RESULT
PASS
VERIFICATION STEPS

Setup Rancher v2.6-head and navigated to Rancher UI home page > Create.
Toggled RKE1 to RKE2/K3s and chose Linode node driver to create a K3s cluster.
Navigated to top-left dropdown menu > newly created K3s cluster > Apps > Installed Apps.
Verified that Rancher is not prompting upgrades for any of the installed K3s apps:

Repeated steps 2-5, but for a Rancher-created RKE2 cluster. I see the below:

As noted in the earlier comments, there will be separate issues to address adding annotations to further enhance this experience, but the original issue has been addressed and verified.


breadcrumbs

because there is no hierarchical structure in the wiki, it would be nice to have a line of breadcrumbs of last visited pages that could help switching back to "upper" pages.

The next version of Jingo will very probably have directories support. But this is also a good idea.

Iam not very sure if directories are a good idea, of course to have the option is always good. But from my experiences with a dokuwiki, I decided in the end to "flatten" all the structure again because it was too complex for many users to keep an overview. I guess it depends very much of the team itself, but considering the wikipedia, there aren't directory structures

That was my idea too when I started the project, but some kind of structure is one of the most requested features. The biggest problem is when you want Jingo to serve/edit a set of documents that already have a structure.
Technically – I believe – the solution would just be just consider the directory as part of the name of the page. We'll see.


label rule for 1.8

invalid value "docker-bench-security" for flag --label: poorly formatted environment: variable 'docker-bench-security' is not a valid environment variable
$ docker version
Client:
 Version:      1.8.0-dev
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   8c7cd78
 Built:        Tue Jul 14 23:47:18 UTC 2015
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.8.0-dev
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   8c7cd78
 Built:        Tue Jul 14 23:47:18 UTC 2015
 OS/Arch:      linux/amd64
 Experimental: true

https://github.com/docker/docker/blob/master/opts/envfile.go
EnvironmentVariableRegexp = regexp.MustCompile("^[[:alpha:]_][[:alpha:][:digit:]_]*$")

Signed-off-by: Thomas Sjögren<EMAIL_ADDRESS>

LGTM


Keyboard input prototype [🕔2d]

Allow the user to type the date using the keyboard (separate feature from the existing keyboard navigation).
Initial specs from which we can start prototyping:

It feels there isn’t a way to split this up into smaller, incremental features, unfortunately.

Just to make sure... there is no way to allow the user to just type a date in the input field, and see that date as "set" in the calendar. Is that correct?
if that is the case, doesn't it make more sense, at least for the time being, NOT to make the input field editable at all?
Right now a user might type a date, submit the form, and... end up with an empty date in the database!

The input field is currently not editable (read-only).
In the proposed design, the user can type a date in the input field, and a valid matching date is indicated in the dropdown with some visual style. Then, if the user leaves the field (blur, submit, etc.) or presses enter, that date would be set as the value of the field.

I can edit the field using Chrome! Just click on the date, open up the
picker, and press escape. You can change the date although the change has
no effect... Which is confusing to the user!
On 28 Aug 2016 5:27 PM, "Jouni Koivuviita"<EMAIL_ADDRESS>wrote:

The input field is currently not editable (read-only).
In the proposed design, the user can type a date in the input field, and a
valid matching date is indicated in the dropdown with some visual style.
Then, if the user leaves the field (blur, submit, etc.) or presses enter,
that date would be set as the value of the field.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vaadin/vaadin-date-picker/issues/196#issuecomment-242965089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACB7XodMqDY7t5rA0Zt3DuM4UtKvF3SYks5qkVSegaJpZM4I3Ghd
.

Then that sounds like a bug. I can’t reproduce that myself of OS X Chrome. Could you open a new issue for it, and provide steps how to reproduce it? Thanks for reporting!

Sorry for the noise here, I didn't think it was a bug -- I actually thought it was the intended behaviour, and that it already did set the date from the textbox...!
Opening a bug now.

Well... I might not need a pointer in the code after all.
It looks like just changing:
readonly$="[[readonly]]"

Into:
readonly

Totally fixes the issue. And it makes a lot of sense too.
If it makes sense to you too, I will do a PR, But, it would me a monumental waste of noise, network, database entries in Github, and log entries in your git repo... you might as well just press backspace 16 times on your editor!

No problem at all @mercmobily! This was an important catch, quite a serious bug, which was introduced in some 1.1.x version. I was testing it on vaadin.com/elements page, where we have some older version in use, and it didn’t show there. For future reference, the bug is tracked in #226.

My 2c about this very issue (that is, Keyboard input).
Right now, the element offers a way to visualise a date in several formats -- which is great. However, if/when you do implement this feature, you will need to make sure you allow users to enter the date in the same format it's displayed. It's not an easy problem, because I might decide to display dates as YYYY-DD-MM and expect that as input. Or the display format (and therefore the input format) might depend on locale etc...

There's a working prototype at https://github.com/vaadin/vaadin-date-picker/tree/feature/keyboard-input (Make sure to run bower install as the branch introduces a new dev dependency).
The proto doesn't really take mobile into account that much except that it does some naive user input prevention at the moment (will enforce later).
Current implementation covers the states defined in the plan but makes some assumptions with behaviour in some situations that were left undefined in the design.
There's a demo of the feature in the advanced.html demo page. Needs user/developer testing so we can proceed with the actual feature implementation.

I would be more than happy to help testing this.
Where would you like me to add comments though, now that the ticket is marked as closed...?

@mercmobily thanks, and sorry about the delay in response!
I created a new issue for the real implementation, you can add any comments there: #238


Problem with the SSL CA cert

I have just downloaded the portable binary version 006 and run this but getting a FileTransferError. I installed ca-certificates through Arch linux package manager but it didn't solve the issue.
$ nix run 'github:nixos/nixpkgs#hello'
error: --- FileTransferError --------------------------------------------------- nix
unable to download 'https://api.github.com/repos/nixos/nixpkgs/commits/HEAD':
Problem with the SSL CA cert (path? access rights?) (77)

Distro: Arch Linux

When I manually export SSL_CERT_FILE it works
$ export SSL_CERT_FILE=$HOME/.nix-portable/store/idzb3c9hwh354gdqnalzrg79g5cp9cqc-nss-cacert-3.56/etc/ssl/certs/ca-bundle.crt
$ nix run 'github:nixos/nixpkgs#hello'
Hello, world!

I think the problem occurs because of specifying the wrong path, isn't it?
### setup SSL
# find ssl certs or use from nixpkgs
debug "figuring out ssl certs"
if [ -z "$SSL_CERT_FILE" ]; then
  debug "SSL_CERT_FILE not defined. trying to find certs automatically"
  if [ -e /etc/ssl/certs/ca-bundle.crt ]; then
    debug "found /etc/ssl/certs/ca-bundle.crt"
    export SSL_CERT_FILE=$(realpath /etc/ssl/certs/ca-bundle.crt)
  elif [ ! -e /etc/ssl/certs ]; then
    debug "/etc/ssl/certs does not exist, using certs from nixpkgs"
-    export SSL_CERT_FILE=/nix/store/idzb3c9hwh354gdqnalzrg79g5cp9cqc-nss-cacert-3.56/etc/ssl/certs/ca-bundle.crt
+    export SSL_CERT_FILE=$HOME/.nix-portable/idzb3c9hwh354gdqnalzrg79g5cp9cqc-nss-cacert-3.56/etc/ssl/certs/ca-bundle.crt
  else
    debug "certs seem to reside in /etc/ssl/certs. No need to set up anything"
  fi
fi

Hey, the script using the /nix/store/... certs should be fine, since inside the wrapped environment, this path will exist. I think the problem lies elsewhere in the nix-portable logic. Could you run it again with NP_DEBUG=1 and post the log?

I see. So, this is creating some kind of virtual environment and /nix/store/ become available, right?
Debug output
❯ NP_DEBUG=1 nix run nixpkgs#hello
figuring out ssl certs
SSL_CERT_FILE not defined. trying to find certs automatically
certs seem to reside in /etc/ssl/certs. No need to set up anything
figuring out which runtime to use
bwrap executable: /home/ihsan/.nix-portable/bin/bwrap
proot executable: /home/ihsan/.nix-portable/bin/proot
bwrap doesn't work on this system -> will use proot
creating bind args for /etc/ssl
needGit: false
git already installed or not required
running command: /home/ihsan/.nix-portable/bin/proot -R /home/ihsan/.nix-portable/emptyroot -b
/home/ihsan/.nix-portable/store:/nix/store -b /home/ihsan/.nix-portable/store/7fryg0wgx7zs5rfz0
0mi6kf755diakc5-busybox-1.31.1/bin/:/bin -b /boot:/boot -b /srv:/srv -b /root:/root -b /tmp:/tm
p -b /lost+found:/lost+found -b /usr/bin:/bin -b /usr/lib:/lib -b /usr/lib:/lib64 -b /run:/run
-b /usr:/usr -b /usr/bin:/sbin -b /home:/home -b /opt:/opt -b /dev:/dev -b /mnt:/mnt -b /proc:/
proc -b /var:/var -b /sys:/sys -b /etc/host.conf:/etc/host.conf -b /etc/hosts:/etc/hosts -b /et
c/passwd:/etc/passwd -b /etc/group:/etc/group -b /etc/nsswitch.conf:/etc/nsswitch.conf -b /run/
systemd/resolve/resolv.conf:/etc/resolv.conf -b /usr/share/zoneinfo/UTC:/etc/localtime -b /etc/
ssl:/etc/ssl /home/ihsan/.nix-portable/store/p8d4qqiqcmx935m2b5a1gsmr6sp1ihsn-nix-2.4pre2020120
1_5a6ddb3/bin/nix run nixpkgs#hello
warning: error: --- FileTransferError ---------------------------------------------------------
----- nix
unable to download 'https://github.com/NixOS/flake-registry/raw/master/flake-registry.json': Pr
oblem with the SSL CA cert (path? access rights?) (77); using cached version
warning: error: --- FileTransferError ---------------------------------------------------------
----- nix
unable to download 'https://api.github.com/repos/NixOS/nixpkgs/commits/HEAD': Problem with the
SSL CA cert (path? access rights?) (77); using cached version
Hello, world!

I'm also experiencing this issue on the arch based Arco linux
[jk@arco nix]$ NP_DEBUG=1 nix-portable nix-build -A container
figuring out ssl certs
SSL_CERT_FILE not defined. trying to find certs automatically
certs seem to reside in /etc/ssl/certs. No need to set up anything
figuring out which runtime to use
bwrap executable: /usr/bin/bwrap
proot executable: /home/jk/.nix-portable/bin/proot
bwrap doesn't work on this system -> will use proot
creating bind args for /etc/ssl
loading new store paths
running command: /home/jk/.nix-portable/bin/proot -R /home/jk/.nix-portable/emptyroot -b /home/jk/.nix-portable/store:/nix/store -b /home/jk/.nix-portable/store/7fryg0wgx7zs5rfz00mi6kf755diakc5-busybox-1.31.1/bin/:/bin -b /usr/lib:/lib64 -b /dev:/dev -b /boot:/boot -b /opt:/opt -b /proc:/proc -b /usr/bin:/sbin -b /var:/var -b /run:/run -b /lost+found:/lost+found -b /srv:/srv -b /root:/root -b /swapfile:/swapfile -b /sys:/sys -b /tmp:/tmp -b /mnt:/mnt -b /usr/bin:/bin -b /usr/lib:/lib -b /home:/home -b /usr:/usr -b /etc/host.conf:/etc/host.conf -b /etc/hosts:/etc/hosts -b /etc/passwd:/etc/passwd -b /etc/group:/etc/group -b /etc/nsswitch.conf:/etc/nsswitch.conf -b /etc/resolv.conf:/etc/resolv.conf -b /usr/share/zoneinfo/Europe/London:/etc/localtime -b /etc/ssl:/etc/ssl /home/jk/.nix-portable/store/p8d4qqiqcmx935m2b5a1gsmr6sp1ihsn-nix-2.4pre20201201_5a6ddb3/bin/nix-store --load-db
needGit: false
git already installed or not required
running command: /home/jk/.nix-portable/bin/proot -R /home/jk/.nix-portable/emptyroot -b /home/jk/.nix-portable/store:/nix/store -b /home/jk/.nix-portable/store/7fryg0wgx7zs5rfz00mi6kf755diakc5-busybox-1.31.1/bin/:/bin -b /usr/lib:/lib64 -b /dev:/dev -b /boot:/boot -b /opt:/opt -b /proc:/proc -b /usr/bin:/sbin -b /var:/var -b /run:/run -b /lost+found:/lost+found -b /srv:/srv -b /root:/root -b /swapfile:/swapfile -b /sys:/sys -b /tmp:/tmp -b /mnt:/mnt -b /usr/bin:/bin -b /usr/lib:/lib -b /home:/home -b /usr:/usr -b /etc/host.conf:/etc/host.conf -b /etc/hosts:/etc/hosts -b /etc/passwd:/etc/passwd -b /etc/group:/etc/group -b /etc/nsswitch.conf:/etc/nsswitch.conf -b /etc/resolv.conf:/etc/resolv.conf -b /usr/share/zoneinfo/Europe/London:/etc/localtime -b /etc/ssl:/etc/ssl /home/jk/.nix-portable/store/p8d4qqiqcmx935m2b5a1gsmr6sp1ihsn-nix-2.4pre20201201_5a6ddb3/bin/nix-build -A container
these 4 derivations will be built:
  /nix/store/dhkjkl5xg9albnvwhh71na9ls8053pbf-container-config.json.drv
  /nix/store/f5w2ngfzcqrmk3p0ykwkp5as01fnkrnv-docker-layer-container.drv
  /nix/store/hn65jy7wyyniwyshmgj8q374fn6r1ph7-runtime-deps.drv
  /nix/store/fjvf8cj8b0n9lgdjxcf1wlm424dw2hy5-docker-image-container.tar.gz.drv
these 40 paths will be fetched (105.62 MiB download, 457.02 MiB unpacked):
  /nix/store/0gc9dr71ldp79cla2qbl3kwdd4ig46pi-linux-headers-5.5
  /nix/store/1bz5a2gqkij0ny2w0qbgzwc437z1h11k-gawk-5.1.0
  /nix/store/1dgwqqp9v3j9q0vpkz4f4m1wds45nh35-perl5.32.0-IO-Tty-1.14
  /nix/store/2c360zxn9dzpvpg991c4bl8m6nyjw21q-perl-5.32.0
  /nix/store/3pl1nfvldwpblhj68939k3wzd8z4ww86-gnumake-4.3
  /nix/store/404gjzymcnns6jyi6q7zyv4ppz6n2xw2-bzip2-<IP_ADDRESS>.1-bin
  /nix/store/4nn6jyxv5dw0x4zbcwfhd47m9yvrsbs6-pcre-8.44
  /nix/store/5c1b2g7ijmwrn468s60i1n6la3kpcbhf-tarsum
  /nix/store/5cjd962ig8azhp45l7h95hl4jzkyzqv0-go-1.15.8
  /nix/store/5im2467j9cpfpn5gsc4jw5f5aki1wh92-pigz-2.4
  /nix/store/6lrvwc4p79acm6153mqd3cg4qa38gqgw-stdenv-linux
  /nix/store/8hpjdv1mgsdi7vqgdf9av1yv9w97ws0v-jshon-20170302
  /nix/store/99fj9fhaxb7pr418pqjmjgrz503k9dc1-jansson-2.13.1
  /nix/store/c1jimp9m5s7h828dnmfdamkb6jfc6dgl-perl5.32.0-TimeDate-2.33
  /nix/store/cf7ivvr1ixwv6ii6l5hdkb5319dv1xf1-gzip-1.10
  /nix/store/cpslkppacy54psy0xhayq1xasp5im0v1-rsync-3.1.3
  /nix/store/cvgwgkd4kp38mrw7i05rrv1q0szy9a3v-gnused-4.8
  /nix/store/cyywvk6hlc9b0g449z8vcp155v2v2sys-coreutils-8.31
  /nix/store/fghkdb08p1dazdk8w43sz0caq37jy8bw-patchelf-0.12
  /nix/store/g1lzcwaac2fdm6rpxx1wxh6mi2z7dcw9-popt-1.16
  /nix/store/gcxdmp6bx78zxp9j8piz8cgxcv64530l-patch-2.7.6
  /nix/store/gg8cwjghgk2fx2isflr843xyjkmissdw-ed-1.16
  /nix/store/gz01vlpf2qmmzaa25swafy8xkc30g6a9-perl5.32.0-Time-Duration-1.21
  /nix/store/hmxf44b080bwbp7wkx0gywk82a61i8hb-jq-1.6-lib
  /nix/store/ifnmhjrvk3f0hbz3f25s3izlb9yk8x0f-iana-etc-20200729
  /nix/store/jbrzh85vix2xbkmvkr28wqs30ah5jjdq-gnutar-1.32
  /nix/store/krahd646dkpafajaaac48abc0adj2iff-diffutils-3.7
  /nix/store/mx6mq6xnkp25zjnxp69g5w824vcvybgq-glibc-2.31-74-dev
  /nix/store/n4b5vcq11xpajpjmssci3vwyn6n9bmbb-moreutils-0.63
  /nix/store/qsqiiy23dy7yjrnzazhivwp07z3784nj-findutils-4.7.0
  /nix/store/r2wvgnr54vmwnjvzyqdixv8xbn362jgh-mailcap-2.1.48
  /nix/store/r95258ayg6bpjn4liswlmbab0wipmgs0-tzdata-2020c
  /nix/store/sy5ld2yvpm1nja95443sp5ay3b6dmz3b-glibc-2.31-74-bin
  /nix/store/vc5w45h64j1srxbmpqyzas82rn2l3y0j-jq-1.6-dev
  /nix/store/w5pm891bv6npy67qdn0ajbsdlrl3fysz-jq-1.6-bin
  /nix/store/wmsbkyp09jbgp4p9ki62sb44b7ly418v-hello-2.10
  /nix/store/wp9vzkgq7816hil5bg2kkrc76rp49hlh-xz-5.2.5-bin
  /nix/store/wsfj3d19gadj46gqplsmk4cnpxl9ny6p-onig-6.9.5_rev1
  /nix/store/y7d4rrrg11q4p4v2gjz9g26d3l30amiw-perl5.32.0-IPC-Run-20200505.0
  /nix/store/zhazc5rmyp5yd38pz9cvfrmpzs79kd2j-gnugrep-3.4
copying path '/nix/store/gz01vlpf2qmmzaa25swafy8xkc30g6a9-perl5.32.0-Time-Duration-1.21' from 'https://cache.nixos.org'...
error: --- FileTransferError --------------------------------------------------------------------------------------------------------------------- nix-build
unable to download 'https://cache.nixos.org/nar/0vxfcg19s5gr1jhj3w05iwac3pkcgcibjaflfb57vvpjwx3pg96c.nar.xz': Problem with the SSL CA cert (path? access rights?) (77)
error: --- Error --------------------------------------------------------------------------------------------------------------------------------- nix-build
some substitutes for the outputs of derivation '/nix/store/vr3xxdspgdmgcbpc21cq0l2jrp87rap0-moreutils-0.63.drv' failed (usually happens due to networking issues); try '--fallback' to build derivation from source
copying path '/nix/store/404gjzymcnns6jyi6q7zyv4ppz6n2xw2-bzip2-<IP_ADDRESS>.1-bin' from 'https://cache.nixos.org'...
error: --- Error --------------------------------------------------------------------------------------------------------------------------------- nix-build
1 dependencies of derivation '/nix/store/fjvf8cj8b0n9lgdjxcf1wlm424dw2hy5-docker-image-container.tar.gz.drv' failed to build

exporting to the crt file in the nix store like @ihsanturk, or export SSL_CERT_FILE="/etc/ssl/certs/ca-certificates.crt" also resolves the issue

On a separate note after that's resolved I'm getting error: getting sandbox mount namespace: No such file or directory, I'll add logs to the other issue

Hey guys. I have improved the ssl cert handling part in the newest release. Could you test and let me know if your problem is resolved?

It looks like it's finding the cert fine and it would probably work but it's failing with Fatal error: nix is unable to build packages
[jk@arco nix]$ NP_DEBUG=1 nix-portable nix-build -A container --option sandbox false
installing files
figuring out ssl certs
SSL_CERT_FILE not defined. trying to find certs automatically
found /etc/ssl/certs/ca-certificates.crt which is a symlink to /etc/ca-certificates/extracted/tls-ca-bundle.pem
figuring out which runtime to use
bwrap executable: /usr/bin/bwrap
proot executable: /home/jk/.nix-portable/bin/proot
bwrap doesn't work on this system -> will use proot
Testing if nix can build stuff without sandbox
Fatal error: nix is unable to build packages

The result is the same with or without the --option sandbox false flag. Also shows up when running nix-portable nix-collect-garbage

The SSL problem solved for me and I can use it without any errors. Thanks!

@06kellyjac Could you try again with version 008 ?
If it still doesn't work, please set NP_DEBUG=2 and post the log. Thanks

I pulled the new version and still had the issue. Tried to rm -rf ~/.nix-portable but I didn't have permission, Did a sudo rm -rf ~/.nix-portable and after the nix-portable nix-build -A container --option sandbox false worked fine
Did another sudo rm -rf ~/.nix-portable and tried nix-portable nix-build -A container without the sandbox false flag and it also worked!!! :tada:
Is there a better way to delete the nix store when using nix-portable? :)

Nice that it finally works for you without any extra tweaks.
I have noticed the issue with the store as well. Somehow some files end up with root ownership. I haven't had time to debug this so far. It's probably either because the initial tar.gz nix store is unpacked the wrong way or something goes wrong with the store paths created while using nix inside the wrapped environment.

If I try and rm -rf the store and pick a random line, e.g. coreutils/mv couldn't be deleted, if I then check it out
ls -al ~/.nix-portable/store/blah-coreutils/mv it's under my user and group linked to coreutils ls -al ~/.nix-portable/store/blah-coreutils/coreutils is also under my user and group. The access rules are r-xr-x-r-x. chmod-ing it to 666 still stops me from rm-ing it :thinking:
If it was owned by root shouldn't it show when I ls the file??

I just played around with the permission issue a bit. The problem is not the file ownership. Your user owns all files and directories. But the user does not have write permissions on the directories. If you want to delete a file in linux you need to have write permissions on the parent directory. Since you're the owner of the directory you can just give yourself the permission via chmod +w without sudo. But it is inconvenient I have to admin.
I mean, it's kind of by design. Nix want's the store to be read only. We could add some cleanup command to nix-portable, to do the magic.

Ah yeah I guess I needed +w the whole way down to coreutils

Maybe we should put a subcommand for self uninstall
nix-portable self-uninstall

what do you think?

That sounds like a good idea


test time is too high

When testing, if I change the size of the input image, the test time on the GPU will be very long, without changing the size of the image, the second start time will be normal; this problem was not found on the CPU; is this a problem for tensorflow?

can you tell me how do you change the dataset? i want to use my own image. thank you!


Adds rel-me to social links

rel="me" is a commonly used way to show that that two websites or social media accounts are the same, and is used for authentication and proving site ownership in a variety of ways.

Thank you, learned from this PR 👍


August 11 - Learning Data Science Concepts through the Lens of Space Exploration

Event Information

Category
Details

Reactor Topic
Data Science and Machine Learning

Monthly Topic (if applicable)
N/A

Weekly Topic (if applicable)
N/A

Stream Topic
Vinnie will walk through the new NASA Learning Paths on MS Learn

Stream Date
August 11, 2020

Stream Time
9:15am PT

Stream Duration
60 minutes

Title
To Infinity and Beyond! Using Data Science Concepts for Space Exploration

Description
Data science is a field that influences all aspects of our scientific community, including space exploration. In partnership with NASA, Microsoft Intern Vincent Angellotti has developed new content for analyzing space rocks and determining the likelihood of a successful rocket launch into space. Join this session to explore this data and to perhaps develop your own space exploration study using Visual Studio Code and a bit of Python. This session recommends a basic understanding of Visual Studio Code and Python programming.

Speaker
@angevin17

Moderator
@sguthals

SharePoint ID
7882

Additional Resources:

Event Checklist
10 Weeks Prior

[x] Reactor Content Team (RCT) or Speaker opens a new issue for an upcoming stream filling in the Event Information table. Both RCT and Speaker are marked as assignees.
[x] RCT and Speaker discuss details of the event in the comments of this issue. RCT adds a confirmed-event label and global-twitch-event tag to the issue and adds event to the Global Live Streams project. Issue will appear in the Upcoming Streams column
[x] Speaker adds a ready-for-marketing-edit label so the RCT can review title and description

8 Weeks Prior

[x] RCT does a review of title and description and removes the ready-for-marketing-edit label
[x] RCT moves the issue to the Ready for SharePoint column
[x] RCT informs the Reactor Marketing Team of the new event information
[ ] RCT provides speaker with assets (e.g. slides, overlays) and the survey data for the event
[x] RCT moves the issue to the MONTH Streams Prep column (according to the month it will be streamed in)

2 Weeks Prior (Done in /microsoft/Reactors)

[ ] Speaker opens a PR with the new content for the stream on the customer-facing Reactor repository and adds the content-development and global-twitch-event tag to the PR.
[ ] Speaker adds to the same PR a modification to the Streaming README to include their stream information.
[ ] Speaker adds the RCT assigned to the issue as the reviewer when it is ready for review/merge
[ ] RCT reviews, approves, and merges the changes

1 Week Prior

[ ] Speaker and Moderator test setup for streaming (instructions coming soon)
[ ] RCT checks in with the speaker and moves the issue to the Ready to Stream column

During and After Stream

[ ] Speaker and Moderator run the stream
[ ] RCT submits recording to be uploaded to the Reactor YouTube and to be made available on LearnTV
[ ] RCT moves issue to the Stream Complete column

@KimberlyBolton1 -> Here is a one-off event that we will be running in August, needs your attention 😄

FYI @sguthals & @angevin17 , Sharepoint won't let us schedule at 15 mins, it has to be on the hour or half hour, so i have put this stream in from 9a - 10:30 LMK if I should update that.

Ah.... @mebaumb -> Will that be confusing though? There is just something on Ch9 the ends at 9am and starts at 10am.
If we can double check with Ch9 on whether we can have 15 minute start times too - and then also if we cant if we are OK to start right at 9am.

It might be a little confusing, yes. Let me know what works for you guys!

@sguthals Here's the edit, let me know your thoughts:
To Infinity and Beyond! Using Data Science Concepts for Space Exploration
Data science is a field that influences all aspects of our scientific community, including space exploration. In partnership with NASA, Microsoft Intern Vincent Angellotti has developed new content for analyzing space rocks and determining the likelihood of a successful rocket launch into space. Join this session to explore this data and to perhaps develop your own space exploration study using Visual Studio Code and a bit of Python. This session recommends a basic understanding of Visual Studio Code and Python programming.

@KimberlyBolton1 - Looks great to me! 🚢

@mebaumb abstract final and moved to Ready for Sharepoint.

This has been published to SharePoint/Meetup (7/15)

@mebaumb - should I add the "confirmed event" label?

@mebaumb - should I add the "confirmed event" label?

Sorry @sguthals! I have added all the right labels! I don't know why I forgot to do that!

No worries! I just got paranoid 😆

Totally understandable! I just confirmed it's published in Sharepoint and good to go on that end! :)

Session recorded and uploaded to YouTube: https://www.youtube.com/watch?v=xmz51LmjI8U&t=1s. Closing issue.


Universal Layout support for iPad

This updates the Maps app to support running on an iPad.
https://github.com/ArcGIS/open-source-apps/issues/405

@esreli I made the changes, please re-review.


bash will not install

When i start bash for the first time, nothing happens, and nothing installs.

Please resubmit following the template in particular detailed logs.


Possibility to turn off building searchable options

If I know my plugin does not contain any configurables, I can speed
up its build by turning off the searchable options builder.

I think it can be disabled as task: buildSearchableOptions.enabled=false?

updated FAQ: https://github.com/JetBrains/gradle-intellij-plugin/blob/master/FAQ.md#how-to-disable-building-searchable-options


Cannot read property 'getState' of undefined

I'm trying to load react-native-ble within android using this require function.
var noble = require('noble');
I'm experiencing this error. Would you know what would be causing this error
Thanks,
Moses

How did you solve it?

@nielsswinkels This is what happens when the native module isn't set up properly. If the problem is on android then go into MainApplication.java and add the necessary RNBLE calls. (You can check the example for how they did it). If it's iOS then you go to build properties for the project and add the libRNBLE.a file.


binary hangs

wow open issue #52! :D
i am using the precompiled binary on a fresh kali 2020.1 box. running aquatone domain.com just hangs forever. appending -debug does nothing.

I see this in GDB -
27      /usr/local/go/src/syscall/asm_linux_amd64.s: No such file or directory.

Perhaps this app requires some specific Go version????

The latest binary release also hangs on a Fedora release 31 machine.
Perhaps you could include system requirements for folks who want to use your software? The instructions of "download binary and add to PATH" seems outdated. Especially with 50+ open issues.

The file it cant find is located at /usr/lib/golang/src/syscall/asm_linux_amd64.s on default Go installs.

So oddly enough, I fixed my issue by removing golang from my system. Very weird!

I've also noticed the binary hangs

Thread 1 "aquatone" hit Temporary breakpoint 1, main.main () at /Users/michael/go/src/github.com/michenriksen/aquatone/main.go:46
warning: Source file is more recent than executable.
46	func main() {
(gdb) c
Continuing.
aquatone v1.7.0 started at 2020-04-01T02:55:05-07:00

[Detaching after vfork from child process 40110]
^C
Thread 1 "aquatone" received signal SIGINT, Interrupt.
runtime.futex () at /usr/local/go/src/runtime/sys_linux_amd64.s:536
536	/usr/local/go/src/runtime/sys_linux_amd64.s: No such file or directory.
(gdb) where
#0  runtime.futex () at /usr/local/go/src/runtime/sys_linux_amd64.s:536
#1  0x0000000000429c5b in runtime.futexsleep (addr=0xcce288 <runtime.m0+328>, val=0, ns=-1) at /usr/local/go/src/runtime/os_linux.go:46
#2  0x000000000040a381 in runtime.notesleep (n=0xcce288 <runtime.m0+328>) at /usr/local/go/src/runtime/lock_futex.go:151
#3  0x0000000000431961 in runtime.stopm () at /usr/local/go/src/runtime/proc.go:1936
#4  0x0000000000432aba in runtime.findrunnable (gp=0xc000024500, inheritTime=false) at /usr/local/go/src/runtime/proc.go:2399
#5  0x00000000004336dc in runtime.schedule () at /usr/local/go/src/runtime/proc.go:2525
#6  0x00000000004339f1 in runtime.park_m (gp=0xc000001380) at /usr/local/go/src/runtime/proc.go:2605
#7  0x0000000000455bdb in runtime.mcall () at /usr/local/go/src/runtime/asm_amd64.s:299
#8  0x0000000000455af9 in runtime.rt0_go () at /usr/local/go/src/runtime/asm_amd64.s:201
#9  0x0000000000000000 in ?? ()
(gdb) continue
Continuing.
^C
Thread 1 "aquatone" received signal SIGINT, Interrupt.
runtime.futex () at /usr/local/go/src/runtime/sys_linux_amd64.s:536
536	in /usr/local/go/src/runtime/sys_linux_amd64.s
(gdb) where
#0  runtime.futex () at /usr/local/go/src/runtime/sys_linux_amd64.s:536
#1  0x0000000000429c5b in runtime.futexsleep (addr=0xcce288 <runtime.m0+328>, val=0, ns=-1) at /usr/local/go/src/runtime/os_linux.go:46
#2  0x000000000040a381 in runtime.notesleep (n=0xcce288 <runtime.m0+328>) at /usr/local/go/src/runtime/lock_futex.go:151
#3  0x0000000000431961 in runtime.stopm () at /usr/local/go/src/runtime/proc.go:1936
#4  0x0000000000432aba in runtime.findrunnable (gp=0xc000026a00, inheritTime=false) at /usr/local/go/src/runtime/proc.go:2399
#5  0x00000000004336dc in runtime.schedule () at /usr/local/go/src/runtime/proc.go:2525
#6  0x00000000004339f1 in runtime.park_m (gp=0xc000060300) at /usr/local/go/src/runtime/proc.go:2605
#7  0x0000000000455bdb in runtime.mcall () at /usr/local/go/src/runtime/asm_amd64.s:299
#8  0x0000000000455af9 in runtime.rt0_go () at /usr/local/go/src/runtime/asm_amd64.s:201
#9  0x0000000000000000 in ?? ()
(gdb) c
Continuing.


refactor(store,sync)!: drop NewStoreWithHead

Overview
Drop store.NewStoreWithHead. Replace it with a test helpers where appropriate. store package now has newStoreWithHead, sync has newTestStore. Both now require tb testing.TB as a 1st param which simplifies usage for the future tests and benchmarks.
Fixes #188

Marking with break even though mostly "unused"


feat(Jobs): use search text for advanced querying.

Enhances the search text field in the admin area.
It is possible to search with keyword prefixes.
With this commit, the 'job' keyword is implemented.
Search with "job:[,]" can be performed.
[ closes #589 ]

Coverage decreased (-0.02%) to 40.875% when pulling e60479d7b9e748e7685bf10ec5e5a1442b9301e7 on TiSiE:589-jobs_improve_admin_search into 19528c5556eef54ba0cdb2fd2966b5bf539be628 on cross-solution:master.


Port break & continue to all backends

Motivation
We can port the new user-defined break and continue into all backends.
Resolves #314
Questions

Can this break some benchmarks we use? => It would be nice to benchmark this before merging.
Relates to #309: can we share this and similar code among backends without needing to copy it into every backend separately?
Do we even want this change? Is this a design we're happy with?

I am a big fan of this, since it shows that effects cannot only be used the high-level but also for very low-level things like jumps.

Can this break some benchmarks we use? => It would be nice to benchmark this before merging.

Breaks running the benchmarks => That's a severe problem (we should have CI for this!)
Breaks performance => I don't care (then we should fix the performance to support these kinds of programs)

can we share this

Yes! We need a solution for this... ASAP

Do we even want this change? Is this a design we're happy with?

I'd say just merge and redesign later ;) Things to concider:

break with a value (requires Control[T])
how to break out of nested loops

@marzipankaiser @phischu could you briefly check whether this breaks the benchmarks?

Breaks neither build nor performance for the benchmarks using the ml backend


Expand tests: test multiple object files in same archive

Added tests for multiple objects within the same archive.
Note that Big AIX hit an issues since llvm-ar generated 64-bit symbol tables, but ar_archive_writer doesn't support this yet.

Thanks!


Update intro-windows-in-kubernetes.md

Updating the docs to indicate that MountPropagationHostToContainer is not supported on windows
fixes https://github.com/kubernetes/kubernetes/issues/75906
/sig windows

/LGTM
I'm not sure why the travis-ci build failed. It looks unrelated to this change.

Building sites … ERROR 2019/03/30 10:18:51 [en] REF_NOT_FOUND: Ref "/docs/concepts/overview/what-is-kubernetes": "/home/travis/gopath/src/github.com/kubernetes/website/content/en/_index.html:11:24": page not found

ERROR 2019/03/30 10:18:51 [en] No resource bundle found. Create an empty headless bundle; create content/en/_common-resources/index.md with "headless: true" in front matter. See https://gohugo.io/content-management/page-bundles/#headless-bundle

ERROR 2019/03/30 10:18:51 [en] No case-studies section found. Create content/en/case-studies/_index.md

/LGTM
I'm not sure why the travis-ci build failed. It looks unrelated to this change.

Building sites … ERROR 2019/03/30 10:18:51 [en] REF_NOT_FOUND: Ref "/docs/concepts/overview/what-is-kubernetes": "/home/travis/gopath/src/github.com/kubernetes/website/content/en/_index.html:11:24": page not found

ERROR 2019/03/30 10:18:51 [en] No resource bundle found. Create an empty headless bundle; create content/en/_common-resources/index.md with "headless: true" in front matter. See https://gohugo.io/content-management/page-bundles/#headless-bundle

ERROR 2019/03/30 10:18:51 [en] No case-studies section found. Create content/en/case-studies/_index.md

that's weird. @jimangel any idea on this CI failure?

@michmike Looks like we hit some transient problems at CI. Can you help rebase this onto master followed by a 'git push -f'?

@tengqm i created a new PR to fix this.
please take a look at https://github.com/kubernetes/website/pull/13739

/close


PyCall not working with Julia v0.4

I am not sure if this is the same as #157, using PyCall with v0.4 gives me the error:
ERROR: LoadError: TypeError: apply_type: in first parameter of NTuple, expected Int64, got Type{Type{T}}
 in include at ./boot.jl:254
 in include_from_node1 at ./loading.jl:133
 in reload_path at ./loading.jl:157
 in _require at ./loading.jl:69
 in require at ./loading.jl:52
while loading /home/theodore/.julia/v0.4/PyCall/src/PyCall.jl, in expression starting on line 381

If you are using Julia v0.4-dev, you typically have to use the master versions of many packages.  Try Pkg.checkout("PyCall").    In general, v0.4-dev is mainly for developers at this point.


Persistent App url

🚀 Feature
A persistent app url that I can share with friends, colleagues, customers or the world.
Motivation
When I create an App its not only for my self. Its for my friends, colleagues, my customers or the world. As far as I can see the App url I get from clicking the "Open url" or "Share" buttons is not persistent. From when I have seen it will change when I

redeploy
delete and re-create the app

I would really like the name to be uniquely determined by the Username (MarcSkovMadsen) and the app name (panel-lightning-basic).

Hi @MarcSkovMadsen!
As you point out, the URL is currently only persistent across stop/start, but I agree we should consider making it at least persistent across redeploys. For delete + re-create one might argue that deleting something also means getting a fresh URL, so I don't have to worry about whom I shared it with. But I see your point, and probably making the URL stable for a given app name under my-apps even across deletes could make things more convenient overall.
Predictable URLs for apps (username + app name) are definitely on the radar, although I can anticipate this won't land imminently.
For others eventually reading the issue: sharing your work in Lightning takes two forms

sharing a link to a running app (for real-time collaboration - users will share the app state)
make apps available for others to Clone and Run (essentially equivalent to what you do in the gallery today - no state shared among users, users get their fresh app instance on their compute resources)

We will make 2 more convenient in the near future. Especially for apps requiring significant compute, 2 is the most natural way to enable people to leverage your work.


[Feat]: Adopt OTel Semantic Conventions for Resource Attributes

🚀 What's the Problem?
The application name and instrumentation library are currently included in each span and metric as attributes (gen_ai.application_name, telemetry.sdk.name), which is a non-standard strategy to name and deliver such information.
💡 Your Dream Solution
OpenTelemetry provides a service.name standard attribute to hold the application name. It's included in the resource attributes instead of span attributes. See: https://opentelemetry.io/docs/specs/semconv/resource/#service. It's actually present in the spans produced by OpenLit, but it's set to default rather than to the application name. About the metrics, having the service.name as a resource attribute instead of metric attribute is also the standard strategy. See: https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/#resource-attributes
About the instrumentation library name (telemetry.sdk.name), it's currently included as a span attribute, as a resource attribute, and as a metric attribute. Is it required to have it as a span attribute and metric attribute? Would it work having it just as a resource attribute, as defined in the semantic conventions? See: https://opentelemetry.io/docs/specs/semconv/resource/#telemetry-sdk. It's also required to provide telemetry.sdk.language and telemetry.sdk.version to fullfill the conventions.
📖 Additional Context
I really like OpenLit, congratulations on such a great library and thanks for following the OpenTelemetry path. It makes it possible to integrate even more systems with OpenLit. I'm currently working on integrating Java applications with OpenLit, and thanks to the OpenTelemetry adoption is more approachable. The challenge I'm experiencing is about the application name and telemetry SDK, which is why I raised this issue.

Thanks a lot for the reply, @patcher9, it helped clarifying things. I understand now why both pieces of information are included as span and metrics attributes. Also, I hadn't realised I could pass the application name via the openlit.init() method, I should have read the documentation more carefully :)
If I instrument an application via OpenTelemetry directly, would the OpenLit UI work if the application name was only included as a service.name resource attribute and the telemetry.sdk.name was only included as a resource attribute and set to opentelemetry?
I have joined the OpenLit Slack, so if you prefer we can continue the conversation there. I'm looking into the observability instrumentation for the two main LLM Java frameworks (Spring AI and LangChain4j), and I'm trying to understand to what extent I can support OpenLit on top of the standard observability foundation Java applications usually have.

Thanks for the additional info, much appreciated. I'll join the conversation on Slack.

fyi @ThomasVitale, @patcher9 has been making good progress on the emerging otel GenAI semantics, in case you are interested in those as well https://github.com/openlit/openlit/issues/342#issuecomment-2262063994


error creating libvirt storage pool: operation failed: Storage source conflict with pool: 'default'

System Information
Linux distribution
 NAME="Arch Linux"
Terraform version
$ terraform version
Terraform v1.9.6
on linux_amd64
+ provider registry.terraform.io/dmacvicar/libvirt v0.8.0

Description of Issue/Question
Setup
$ cat *.tf
resource "libvirt_pool" "base" {
	name = "base"
	type = "dir"
	path = "/var/lib/libvirt/images"
}

resource "libvirt_volume" "alpine_iso" {
	name = "alpine_disk.qcow2"
	pool = libvirt_pool.base.name
	source = "https://dl-cdn.alpinelinux.org/alpine/v3.20/releases/x86_64/alpine-virt-3.20.3-x86_64.iso"
}
provider "libvirt" {
	uri = "qemu:///system"
}
terraform {
	required_providers {
		libvirt = {
			source = "dmacvicar/libvirt"
		}
	}
}

Steps to Reproduce Issue
$ terraform apply

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # libvirt_pool.base will be created
  + resource "libvirt_pool" "base" {
      + allocation = (known after apply)
      + available  = (known after apply)
      + capacity   = (known after apply)
      + id         = (known after apply)
      + name       = "base"
      + path       = "/var/lib/libvirt/images"
      + type       = "dir"
    }

  # libvirt_volume.alpine_iso will be created
  + resource "libvirt_volume" "alpine_iso" {
      + format = (known after apply)
      + id     = (known after apply)
      + name   = "alpine_disk.qcow2"
      + pool   = "base"
      + size   = (known after apply)
      + source = "https://dl-cdn.alpinelinux.org/alpine/v3.20/releases/x86_64/alpine-virt-3.20.3-x86_64.iso"
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

libvirt_pool.base: Creating...
╷
│ Error: error creating libvirt storage pool: operation failed: Storage source conflict with pool: 'default'
│
│   with libvirt_pool.base,
│   on libvirt_pool.tf line 1, in resource "libvirt_pool" "base":
│    1: resource "libvirt_pool" "base" {
│
╵

There are already .qcow2 files in the specified path for the storage pool:
$ ls /var/lib/libvirt/images
alpine_x86_64.qcow2  archlinux.qcow2  freebsd-x86.qcow2

But the default pool has a different target path:
# pool-dumpxml default
<pool type='dir'>
  <name>default</name>
  <uuid>c70b93dc-5b04-4958-83da-5654bd12a1da</uuid>
  <capacity unit='bytes'>125425360896</capacity>
  <allocation unit='bytes'>63068778496</allocation>
  <available unit='bytes'>62356582400</available>
  <source>
  </source>
  <target>
    <path>/home/myuser/.local/share/libvirt/images</path>
    <permissions>
      <mode>0711</mode>
      <owner>1000</owner>
      <group>998</group>
    </permissions>
  </target>
</pool>

So I don't understand the conflict here.
All other pools also do not have the specified path.

Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration?
$ sestatus
bash: sestatus: command not found

$ systemctl status firewalld
○ firewalld.service - firewalld - dynamic firewall daemon
     Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; preset: disabled)
     Active: inactive (dead)
       Docs: man:firewalld(1)

Hi, I think there might be confusion about system and user libvirt sessions. It looks like from Terraform you are using system one but when you show XML for default storage pool, it looks like it might be user one.


Replace Resampler macros with implementations generic over a Sample

Note: this is built on top of #13, so it should be merged before this. This also conflicts w/ #12 - but assuming this is accepted I'd happily rework either of those PRs.
This removes the macros responsible for building sampler implementations w/ generic sampler implementations over a Sample trait (which is quite wordy). And since we're now generic over the Sample trait, the vectorised interpolation support also needed to be reworked.
Each kind of vectorized operation has their own Sample trait (ex SseSample). Which defines all the necessary operations in order to operate over a specific kind of sample. This has at least one benefit in that it allows us to remove the PhantomData associated with all the interpolators and use a single generic sincs field.
All of these traits are implemented by the Sample trait, and if a platform is not supported the trait is replaced by a macro with a dummy implementation that does nothing. In that sense, it's like an optional supertrait.
The feature detection has also been moved into a single place. The constructor of the interpolator kind being built. And feature errors are now runtime errors of the kind MissingCpuFeatures which describes exactly which features are missing. This can be either be formatted as an error, or simply unwrapped to get the same level of diagnostics as the panic.
Benefits include:

Improved IDE and formatter support. Completions, jump to definitions, and so forth are all a bit wonky when the entire impl is inside of a macro.
A user of the library can be generic over the Sample type.

The Sample trait is a bit wordy to say the least with a lot of super traits! This can in my estimate be reduced quite heavily be removing a large amount of repeated code in the future. But I decided to take this route right now to reduce the amount of refactoring done in a single patch. I'm personally not bothered by this. But it does mean that for each kind of operation added work needs to be done to the Sample trait.
Finally, I've modified the build configuration to build on all platforms supported by Github Actions for free. I've also removed the check build stage, because it's superfluous when doing the other build steps.

I also noticed one minor change I've been working on slipped through that I didn't intend to. Instead of having updating an async sampler be a runtime error it is now part of the trait, so there's two kinds of resamplers:

Resampler
AsyncResampler - which has the set_* methods.

I intended to put it in a separate PR, but hey. I'll remove it if it's not wanted here.

Oh, and I don't have an aarch64 environment I can test this on. So not sure if the neon impl still compiles :)

I also noticed one minor change I've been working on slipped through that I didn't intend to. Instead of having updating an async sampler be a runtime error it is now part of the trait, so there's two kinds of resamplers:
* `Resampler`

* `AsyncResampler` - which has the `set_*` methods (link: https://github.com/HEnquist/rubato/pull/15/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759R205).

I intended to put it in a separate PR, but hey. I'll remove it if it's not wanted here.

In the application I mainly wrote this for, it's much easier if there is a single resampler type. The set_ methods are useless on the synchronous one yes, but having two different resampler traits means I will need to add a lot of extra stuff to handle that.

Overall I'm happy with these changes and I will merge once we sort out the few things I found.
Since there will be breaking changes, a new major version is needed. I think I'll skip to 1.0.0, that 0.x.y looks ugly.
There was a new version of num recently, and that will give new versions of several dependencies, including my own realfft. I think it makes sens to wait for all that to land before making a new rubato release. Hopefully doesn't take very long.

In the application I mainly wrote this for, it's much easier if there is a single resampler type. The set_ methods are useless on the synchronous one yes, but having two different resampler traits means I will need to add a lot of extra stuff to handle that.

I'll resurrect the error type if that's what you want. I didn't intend it to be in here anyways!

In the application I mainly wrote this for, it's much easier if there is a single resampler type. The set_ methods are useless on the synchronous one yes, but having two different resampler traits means I will need to add a lot of extra stuff to handle that.

I'll resurrect the error type if that's what you want. I didn't intend it to be in here anyways!

Resampler trait you mean?

Resampler trait you mean?

Yeah. But I meant the error that was returned in case it's not supported. It's done in the last patch.

So lot's of clippy lints that came alive when I switched from num_traits::Float::from to T::coerce(..). I'll fix them.

Resampler trait you mean?

Yeah. But I meant the error that was returned in case it's not supported. It's done in the last patch.

Ah alright, sure!

So lot's of clippy lints that came alive when I switched from num_traits::Float::from to T::coerce(..). I'll fix them if that's all right w/ you?

Sure! Nice to keep clippy happy.

@HEnquist that's the last open comment I see which is open. Feel free to merge whenever you're comfortable and preferably squash. Or not ;)
This also closes #13 since this one includes it.

Looks good now! I will test it a bit more to make sure the resample results are all good. The tests only catch quite big problems, small issues can still sneak through. I don't expect any problems, and I'll merge as soon as I'm done.

I have run all my tests now and all the results look good. Merging!


[SPARK-32084][PYTHON][SQL] Expand dictionary functions

What changes were proposed in this pull request?

[x] Expand dictionary definitions into standalone functions.
[ ] Group and sort definitions within groups.
[x] Fix annotations for ordering functions.

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Existing tests.

Test build #130218 has started for PR 30143 at commit ae98400.

Test build #130218 has finished for PR 30143 at commit ae98400.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130218/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34818/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34818/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34818/
Test FAILed.

Nice, @zero323. Thanks for working on this.

Add proper NumPy-style docstrings to expanded functions.

Oh, let's don't do this in this PR. It should add some dependencies into GitHub Actions, fix the script about numpydoc, etc. We could add a dedicated PR for numpydoc only later. Actually I am working (and thinking) on making an initial PR to start this numpydoc style.

Test build #130230 has started for PR 30143 at commit 738fdde.

Test build #130231 has started for PR 30143 at commit 79fd14e.

Test build #130230 has finished for PR 30143 at commit 738fdde.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130230/
Test PASSed.

Test build #130231 has finished for PR 30143 at commit 79fd14e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130231/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34830/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34831/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34831/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34831/
Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34830/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34830/
Test PASSed.

Add proper NumPy-style docstrings to expanded functions.

Oh, let's don't do this in this PR.

OK. Shall we extend existing docstrings here at all?
And what about the remaining points? Right now functions are in groups, some are not, some ordered by name, some not. Since we introduce quite a few defs here, I thought it might be a good idea to sort this stuff.

Yeah, I think we can just keep docstrings as-is. For grouping stuff, I think it's okay to don't change since it's mainly for code readers. There were similar changes proposed (and abandoned) before, e.g.) https://github.com/apache/spark/pull/27976.

The current changes look pretty good to go. Let me know when you think it's ready. I'll take one more look and merge it in.

Test build #130261 has started for PR 30143 at commit 9d4fdc4.

Test build #130263 has started for PR 30143 at commit 2c99821.

Test build #130261 has finished for PR 30143 at commit 9d4fdc4.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130261/
Test FAILed.

Yeah, I think we can just keep docstrings as-is. For grouping stuff, I think it's okay to don't change since it's mainly for code readers.

That's true, though I'd argue that it matters, given the size of the module (it is large enough, so log defined twice, once through dict and once through def, went unnoticed for years) Not to mention it was clearly the original intention, things just diverged a bit over time.

There were similar changes proposed (and abandoned) before, e.g.) #27976.

Fair enough. Let's not complicate things here, but I'll allow myself another PR later to see if I can make the case :)

Jenkins, retest this please.

Test build #130267 has started for PR 30143 at commit 2c99821.

Test build #130263 has finished for PR 30143 at commit 2c99821.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130263/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34861/

Test build #130267 has finished for PR 30143 at commit 2c99821.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130267/
Test PASSed.

Merged build finished. Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34861/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34861/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34863/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34863/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34863/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34866/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34866/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/34866/
Test PASSed.

Merged to master.

Merged to master.

Thanks!