Backport [SPARK-5847] Allow for configuring MetricsSystem's prefix

This is a backport of #14270. Because the spark.internal.config system
does not exists in branch 1.6, a simpler substitution scheme for ${} in
the spark.metrics.namespace value, using only Spark configuration had to
be added to preserve the behaviour discussed in the tickets and tested.
This backport is contributed by Criteo SA under the Apache v2 licence.
What changes were proposed in this pull request?
Adding a new property to SparkConf called spark.metrics.namespace that allows users to
set a custom namespace for executor and driver metrics in the metrics systems.
By default, the root namespace used for driver or executor metrics is
the value of spark.app.id. However, often times, users want to be able to track the metrics
across apps for driver and executor metrics, which is hard to do with application ID
(i.e. spark.app.id) since it changes with every invocation of the app. For such use cases,
users can set the spark.metrics.namespace property to any given value
or to another spark configuration key reference like ${spark.app.name}
which is then used to populate the root namespace of the metrics system
(with the app name in our example). spark.metrics.namespace property can be set to any
arbitrary spark property key, whose value would be used to set the root namespace of the
metrics system. Non driver and executor metrics are never prefixed with spark.app.id, nor
does the spark.metrics.namespace property have any such affect on such metrics.
How was this patch tested?
Added new unit tests, modified existing unit tests.

Can one of the admins verify this patch?

Please ignore AppVeyor test here. (Please refer https://github.com/apache/spark/pull/15022#issuecomment-245884867) it seems it happens only in other branchs as they don't have appveyor.yml and try to refer the configuration in the web (although I have to test this). I'd be great if any of auhorized one sets the branch to test to master brunch only as described in https://github.com/apache/spark/blob/master/dev/appveyor-guide.md#specifying-the-branch-for-building-and-setting-the-build-schedule

We don't generally backport features to maintenance releases. Pinging @marmbrus who I believe is currently doing RM for the 1.6 line.

I'm aware that features are not generally back-ported. The point is, for us this is a bug, preventing a deployment in production. We thus back-ported the fix internally and now propose to share it with the community as the work is already done.

Thanks for spending the time to backport this, but it does seem a little risky to include changes to the configuration system in a maintenance release.  As such, I'd probably error on the side of caution and close this PR unless there are a lot of 1.6 users clamoring for this functionality.

This is perfectly understandable, Just in the same way that we err on the side of caution by not switching to 2.0 branch for prod just now :-)

Test build #3262 has started for PR 15023 at commit c1c57fb.

Test build #3262 has finished for PR 15023 at commit c1c57fb.

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

Thanks for understanding!  I do hope you guys upgrade eventually, there's a lot of good stuff and 2.0.1 should be out in the near future.  Please do report any issues you see :)


Generated site: introduce sidebar/detail view

Currently
There's top navigation that has links to Feature, Segments, Attributes, and History.
Docs: https://featurevisor.com/docs/site/
Problem
It does not quickly give you an overview of the total number of Features, Segments, and Attributes that exist in the Featurevisor project.
Solution
We can change the UI to be sidebar-based, where top nav becomes sidebar nav.
And the links in sidebar can also show total number of items, like:

Features (10)
Segments(4)
Attributes(5)
History

Technical notes
More info: https://featurevisor.com/docs/site/
All components found here: https://github.com/fahad19/featurevisor/tree/main/packages/site/src/components
Local development tips
$ npm ci
$ npm run bootstrap

Make changes in packages/site, then do:
$ (cd ./packages/site && npm run build)

See the changes in example app:
$ (cd ./examples/example-1 && npm start)

Do you have any examples that illustrates your proposal? Maybe some other documentation site that has sidebar-based UI?

@1e9y: this can be a good example of the sidebar/detail view https://tailwindui.com/components/application-ui/navigation/sidebar-navigation


Provide access to the main(String[] args) at the Container and msc service levels.

I wanted to access the command line args passed into the swarm main(String[]) method inside my service activator, so this change looked like the simplest way to accomplish that. I have an update to the wildfly-swarm-example-msc example as well.

Looks good. Hadn't even thought of that. I may follow similarly for other muck I've been pushing around as properties or files inside of deployments.


CPPSDK: ensure array has enough data before trying to access

This issue is identified while testing new setup

:tada: This PR is included in version 3.0.0-next.3 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: added hmac option

Description
Added the ibm_sm_service_credentials_secret.source_service.parameter HMAC option with corresponding variable.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

Dont forget to then expose this in https://github.com/terraform-ibm-modules/terraform-ibm-secrets-manager/tree/main/modules/secrets once merged.
Can you please link the tracking issue in the PR?

Corresponding issue: https://github.ibm.com/GoldenEye/issues/issues/10804

Upgrade test failed because the change causes a delete and create of the ibm_sm_service_credentials_secret

@kierramarie Why would upgrade test fail if we have not enabled HMAC? Can you paste the output?

/run pipeline

/run pipeline

@ocofaigh
Should be false
        	Test:       	TestRunUpgradeExample
        	Messages:   	Resource(s) identified to be destroyed
        	            	Name: service_credentials_secret
        	            	Address: module.secret_manager_service_credential.ibm_sm_service_credentials_secret.service_credentials_secret[0]
        	            	Actions: [delete create]

TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:   # module.secret_manager_service_credential.ibm_sm_service_credentials_secret.service_credentials_secret[0] must be replaced
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185: -/+ resource "ibm_sm_service_credentials_secret" "service_credentials_secret" {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ created_at              = "2024-10-01T14:18:48Z" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ created_by              = "IBMid-666000KAO3" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ credentials             = (sensitive value)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ crn                     = "crn:v1:bluemix:public:secrets-manager:us-south:a/abac0df06b644a9cabc6e44f55b3880e:79c6d411-c18f-4670-b009-b0044a238667:secret:8663a154-c35c-f741-939f-5a0e550e9ef8" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ custom_metadata         = {} -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ downloaded              = true -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ expiration_date         = "2024-12-30T14:18:50Z" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ id                      = "us-south/79c6d411-c18f-4670-b009-b0044a238667/8663a154-c35c-f741-939f-5a0e550e9ef8" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ locks_total             = 0 -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:         name                    = "sm-secret-module-upg-wdje4u-service-credentials"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ next_rotation_date      = "2024-12-29T14:18:48Z" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ secret_id               = "8663a154-c35c-f741-939f-5a0e550e9ef8" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ secret_type             = "service_credentials" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ state                   = 1 -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ state_description       = "active" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ updated_at              = "2024-10-01T14:18:50Z" -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       - version_custom_metadata = {} -> null
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ versions_total          = 1 -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:         # (7 unchanged attributes hidden)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:       ~ source_service {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:           ~ iam          = [
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:               - {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                   - apikey    = [
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                       - {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                           - description = "Auto-generated for key crn:v1:bluemix:public:cloud-object-storage:global:a/abac0df06b644a9cabc6e44f55b3880e:ab759ee7-3f9f-4a6a-af04-943d76026509:resource-key:c25b4c0f-c1e3-41ba-aa07-1d58521cf554"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                           - name        = "sm-secret-module-upg-wdje4u-service-credentials"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                         },
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                     ]
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                   - role      = [
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                       - {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                           - crn = "crn:v1:bluemix:public:iam::::serviceRole:Writer"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                         },
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                     ]
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                   - serviceid = [
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                       - {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                           - crn = "crn:v1:bluemix:public:iam-identity::a/abac0df06b644a9cabc6e44f55b3880e::serviceid:ServiceId-1e8a0df6-bebd-4e0a-8524-c00c3c631323"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                         },
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                     ]
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                 },
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:             ] -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:           ~ parameters   = { # forces replacement
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:               + "HMAC" = "false"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:             }
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:           ~ resource_key = [
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:               - {
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                   - crn  = "crn:v1:bluemix:public:cloud-object-storage:global:a/abac0df06b644a9cabc6e44f55b3880e:ab759ee7-3f9f-4a6a-af04-943d76026509:resource-key:c25b4c0f-c1e3-41ba-aa07-1d58521cf554"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                   - name = "sm-secret-module-upg-wdje4u-service-credentials"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:                 },
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:             ] -> (known after apply)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:             # (2 unchanged blocks hidden)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:         }
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:         # (1 unchanged block hidden)
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:     }
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185: Plan: 1 to add, 0 to change, 1 to destroy.

Oh wow, this is actually a breaking change:
~ parameters   = { # forces replacement
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:               + "HMAC" = "false"
TestRunUpgradeExample 2024-10-01T14:19:19Z command.go:185:             }

We may need to implement this in a different way. We may need to code it so that if service_credentials_source_service_hmac is false, we don't pass any parameters, (as I assume this is the default). And if its set to true, only then pass the value in the parameters block.
I also think this should not be a breaking change, so can I ask you to try and reproduce using the provider directly with a simple piece of code using the ibm_sm_service_credentials_secret resource, and then create a provider bug with the details. Thanks

/run pipeline

Going to create an issue for creating the provider bug.

/run pipeline

I have created a provider bug.

/run pipeline

/run pipeline

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


qkey release v1.12

qkey release v1.12 and quick_led release v1.02

https://github.com/RT-Thread/packages/suites/13297090873/artifacts/725956049

pid的软件包分类请调整为signalprocess分类下


[#1964] Migrate reach & versatile damage for non-weapons

Creates additional DamageActivity for items that aren't weapons but have versatile damage
Migrates range.value to range.reach for melee waepons without the thrown property
Adjust the API of refreshCompendium to call migrateCompendium first with proper error handling if the migration fails

Adjust the API of refreshCompendium to call migrateCompendium first with proper error handling if the migration fails

I take this to mean it will no longer be needed for a module author to call both, but simply loop over all their packs and calling refreshCompendium?


HOTFIX BUG: circular import

Fixes:
Traceback (most recent call last):
  File "./deepy.py", line 25, in <module>
    from megatron.config_monster import ConfigMonster
  File "/home/mchorse/gpt-neox/megatron/config_monster.py", line 10, in <module>
    from megatron.utils import obtain_resource_pool
  File "/home/mchorse/gpt-neox/megatron/utils.py", line 34, in <module>
    from megatron.checkpointing import save_checkpoint
  File "/home/mchorse/gpt-neox/megatron/checkpointing.py", line 35, in <module>
    from megatron.utils import natural_sort
ImportError: cannot import name 'natural_sort' from partially initialized module 'megatron.utils' (most likely due to a circular import) (/h

Is this actually going to fix the circular import? By moving the import inside the function call doesn't that delay rather than prevent the problem?

No it solves the issue. It’s the standard way to prevent circula imports and I’ve tested it.


⚠ AGEG website (prod) has degraded performance

In 9874dae, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 1485 ms

Resolved: AGEG website (prod) performance has improved in 25cfa0a.


Graph Isomorphism Network

Do you plan to support Graph Isomorphism Network (GIN)?

HOW POWERFUL ARE GRAPH NEURAL NETWORKS?

Currently, we don't plan to support it. However, it's not difficult to customize and pr is welcomed :) !

Ok, I will try to look into it.

@nashid Thanks for your attention to the library! We are not planning to support GIN in the short term because we rarely see GIN applications on NLP tasks. Please let us know if you are aware of any interesting NLP applications using GIN.
Closed the issue as of now. Please feel free to reopen it or send a PR.


I found official documents of OCP 3.11
https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html
apiServerArguments:
  event-ttl:
  - "15m"

In OCP 4.3, same as OCP 3.11, I think that I can change event-ttl by editing CRD of "kubeapiservers.operator.openshift.io".
# oc get kubeapiservers.operator.openshift.io/cluster -o yaml
apiVersion: operator.openshift.io/v1
kind: KubeAPIServer
metadata:
  annotations:
    release.openshift.io/create-only: "true"
  creationTimestamp: "2020-03-18T23:46:56Z"
  generation: 3
  name: cluster
  resourceVersion: "428767"
  selfLink: /apis/operator.openshift.io/v1/kubeapiservers/cluster
  uid: 927aefc8-04e6-437b-9965-5404dd5da7e8
spec:
  logLevel: ""
  managementState: Managed
  observedConfig:
    apiServerArguments:
      feature-gates:
      - RotateKubeletServerCertificate=true
      - SupportPodPidsLimit=true
      - NodeDisruptionExclusion=true
      - ServiceNodeExclusion=true
      - SCTPSupport=true
      - LegacyNodeRoleBehavior=false

Is my understanding right?

ObservedConfig is maintained by the operator. No way to change that by the user. UnsupportedConfigOverrides would do, but as the name states: without support. It will block upgrades.

Hi, @sttts
I'm very thankful for your prompt reply.
I understood editing event-ttl is unsupported and Operator blocks upgrades.
My question has been resolved.
regards,
Daiki


auths/AuthProvider: bind Generic to Auth

Description
Fix the type hint for auths/AuthProvider (fixes #1776)
Checklist

[ ] Created tests which fail without the change (if possible)
Did not see any tests/CI for mypy
[ ] All tests passing
[x] Added a changelog entry

I can't see how my minor change has broken the tests that badly. Smells like a dependency got upgraded since the last run.
Dep diff between my run (https://github.com/schemathesis/schemathesis/actions/runs/6394405625/job/17357198626?pr=1777) and HEAD (https://github.com/schemathesis/schemathesis/actions/runs/6318163361/job/17156548761)
-cffi==1.15.1
+cffi==1.16.0
-charset-normalizer==3.2.0
+charset-normalizer==3.3.0
-coverage==7.3.1
+coverage==7.3.2
-fastapi==0.103.1
+fastapi==0.103.2
-hypothesis==6.87.0
+hypothesis==6.87.1
-packaging==23.1
+packaging==23.2
-pydantic==2.4.1
+pydantic==2.4.2
-schemathesis @ file:///home/runner/work/schemathesis/schemathesis/.tox/.tmp/package/1/schemathesis-3.19.7.tar.gz#sha256=1cca2baff393404aa4486d3c3a18aa1af6a02c7184cf89f0f6bcc651b89e5bea
+schemathesis @ file:///home/runner/work/schemathesis/schemathesis/.tox/.tmp/package/1/schemathesis-3.19.7.tar.gz#sha256=e334b5e32ff5af7a9558d11eb1bb1aea6a0dc98c7efe3c5efa4a67ff7d4b4c01
-strawberry-graphql==0.209.2
+strawberry-graphql==0.209.5
-urllib3==2.0.5
+urllib3==2.0.6
-Werkzeug==2.3.7
+Werkzeug==3.0.0

Thanks for the PR, I’ll check it in details later on during this week


fix: Don't load account 1 balances when first opening wallet

This PR includes a collection of findings from @SK-Sam @alexandreaco and myself.
The original UI was not handling changes to the activeAccount vue ref in the useWallet composable on the wallet overview.  This meant that when the initWallet function was called and it switched accounts there was a race condition that resulted in conflicting activeAccount values. I think.
This PR fixes these problems by updating the WalletOverview to delay displaying values until half a second after the balances observable has emitted an event.  This gives the UI enough time to correctly calculate and render the real balance values while the wallet switches and persists account values to the store and does... other things.

fwiw I don't think the changes to useTokenBalances are necessary but I like the cleaner type references. 👍🏼

Closing this in favor of https://github.com/radixdlt/olympia-wallet/pull/459


Fix #2655: NumericRange.{min|max} for Doubles

As a side-effect, this fixes min/max for arbitrary integral types (which is currently broken in Scala JVM).
This copies the upstream fix for SI-10086 (scala/scala@738ac6d7d3902767cc4cd5820fe83632e558f049).

Review by @sjrd

If the fix is so easy and is in an override, IMO we should also submit the patch to scala/scala (targeting 2.11.x).

Yes, I'll do that. There might be performance concerns on Scala JVM due to the additional lambda though.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3519/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4635/
Test FAILed.

Also see: https://github.com/scala/scala/pull/5575
I propose to put this on hold, until the upstream PR is resolved. We can merge it just before the 0.6.14 release, if the upstream PR is not merged. Otherwise we can align this with the upstream PR.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3522/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4639/
Test PASSed.

https://github.com/scala/scala/pull/5575 was merged, so this PR can now be updated with the final code from there.

Updated.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3552/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4680/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3554/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4682/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3553/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4681/
Test FAILed.

Ugh... This happens when you push code tired :P Updated.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3555/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4685/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3556/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4686/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3557/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4687/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3558/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4688/
Test FAILed.

Dear Jenkins, retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3561/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4691/
Test FAILed.

[info] Test org.scalajs.testsuite.scalalib.RangesTest.NumericRange_with_arbitrary_integral started
[error] Test org.scalajs.testsuite.scalalib.RangesTest.NumericRange_with_arbitrary_integral failed: java.lang.AssertionError: expected:<A(9)> but was:<A(2)>, took 0.001999872 sec
[error]     at org.scalajs.testsuite.scalalib.RangesTest.NumericRange$undwith$undarbitrary$undintegral(/localhome/jenkins/a/workspace/scalajs-task-worker/test-suite/js/target/scala-2.12/file:/localhome/jenkins/a/workspace/scalajs-task-worker/junit-runtime/src/main/scala/org/junit/Assert.scala:56)
[error]     at org.scalajs.testsuite.scalalib.RangesTest$scalajs$junit$bootstrapper$.invoke(/localhome/jenkins/a/workspace/scalajs-task-worker/test-suite/js/target/scala-2.12/scalajs-test-suite-test-fastopt.js:252259)
[error]     ... 3 more

Updated (the test was buggy).

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3564/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4694/
Test PASSed.


Script tries to downagrade .NET Standard 2.1 Targeting Pack

Issue Title
Script tries to downgrade .NET Standard but it fails.
General
Your instalator script fails when trying to install packages on deb-based distro - Mint 19.4.
You missed there --allow-downgrades, so it can downagrade to older .NET Standard Targeting Pack package of version 2.1.
As far as I remember .NET 3.1 was able to use .NET Standard 2.2 so why are you downgrading to 2.1 on .NET 5?
Preview image of an issue
Correct me if I am mistaken.
Greetings.

.NET Standard 2.1 is the latest version, and .NET Standard 2.2 shouldn't exist. If 2.2 did exist, it would actually install side-by-side with 2.1 and not cause any conflict, because they have different package names, netstandard-targeting-pack-2.1 and netstandard-targeting-pack-2.2. I think what's actually happening for you is a difference between the version of netstandard-targeting-pack-2.1 you have installed vs. the version that's included with the 5.0 preview tar.gz files. (We redistribute the latest version so that the tar.gz contains everything you need to install the 5.0 preview.)
@Arkasian can you provide some more detail, such as the Linux distro you're using, which package you have installed before running the script, and more complete console output? (Copy paste is much more preferable than a screenshot!)
/cc @leecow @NikolaMilosavljevic

Sorry, dont have an output, didnt have it at the time of writing the issue either, because I closed terminal just after the fact. There was nothing more than what I showed, just standard log for every installation of .NET Core, and then it printed out what I showed.
I had installed there .NET Core 2.2.402 SDK and compatible runtime.
dotnet-sdk-2.2, aspnet-runtime-2.2 dotnet-runtime-2.2 and those are all I had installed on my system. I will try reproduce that error again, but Im not sure if I will be able to.

I just had the same issue crop up on TravisCI: https://travis-ci.org/github/demystifyfp/FsToolkit.ErrorHandling/builds/686310362
My current .travis.yml file:
language: csharp

sudo: false # use the new container-based Travis infrastructure
dist: xenial
dotnet: 3.1.200

before_script:
  - nvm install 10.15.0
  - nvm use 10.15.0
  - npm install
  - mkdir $HOME/dotnet_install && cd $HOME/dotnet_install
  - "curl -H 'Cache-Control: no-cache' -L https://aka.ms/install-dotnet-preview -o install-dotnet-preview.sh"
  - sudo bash install-dotnet-preview.sh

script:
  - dotnet --info
  - ./build.sh RunFableTests

Had this same issue on Debian 10 when trying to upgrade preview 5 to 6, and again now when I tried upgrading preview 6 to 7.
I run both .net core 3.1 application and preview 5.0 application on same machine
Here's the first output:
root@vps:~/dotnetinstall# bash install-dotnet-preview.sh
1

*** Checking required system dependencies for detected OS: Debian GNU/Linux 10 (buster) ...
***     tar is already installed.
***     gzip is already installed.
***     curl is already installed.

*** Setting package type to deb.
*** Download source: dotnet-5.0.0-preview.7-deb.tar.gz

*** Downloading https://dotnetcli.blob.core.windows.net/dotnet/release/install-preview/5.0.0-preview.7/dotnet-5.0.0-preview.7-deb.tar.gz to /root/dotnetinstall ...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 85.5M  100 85.5M    0     0  3134k      0  0:00:27  0:00:27 --:--:-- 3193k

*** Unpacking dotnet-5.0.0-preview.7-deb.tar.gz ...

dotnet_packages/
dotnet_packages/dotnet-hostfxr-5.0.0-preview.7.20364.11-x64.deb
dotnet_packages/dotnet-host-5.0.0-preview.7.20364.11-x64.deb
dotnet_packages/aspnetcore-runtime-5.0.0-preview.7.20365.19-x64.deb
dotnet_packages/aspnetcore-targeting-pack-5.0.0-preview.7.20365.19.deb
dotnet_packages/dotnet-targeting-pack-5.0.0-preview.7.20364.11-x64.deb
dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
dotnet_packages/dotnet-apphost-pack-5.0.0-preview.7.20364.11-x64.deb
dotnet_packages/dotnet-runtime-5.0.0-preview.7.20364.11-x64.deb
dotnet_packages/dotnet-sdk-5.0.100-preview.7.20366.6-x64.deb
dotnet_packages/dotnet-runtime-deps-5.0.0-preview.7.20364.11-x64.deb

Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'aspnetcore-runtime-5.0' instead of '/root/dotnetinstall/dotnet_packages/aspnetcore-runtime-5.0.0-preview.7.20365.19-x64.deb'
Note, selecting 'aspnetcore-targeting-pack-5.0' instead of '/root/dotnetinstall/dotnet_packages/aspnetcore-targeting-pack-5.0.0-preview.7.20365.19.deb'
Note, selecting 'dotnet-apphost-pack-5.0' instead of '/root/dotnetinstall/dotnet_packages/dotnet-apphost-pack-5.0.0-preview.7.20364.11-x64.deb'
Note, selecting 'dotnet-host' instead of '/root/dotnetinstall/dotnet_packages/dotnet-host-5.0.0-preview.7.20364.11-x64.deb'
Note, selecting 'dotnet-hostfxr-5.0' instead of '/root/dotnetinstall/dotnet_packages/dotnet-hostfxr-5.0.0-preview.7.20364.11-x64.deb'
Note, selecting 'dotnet-runtime-5.0' instead of '/root/dotnetinstall/dotnet_packages/dotnet-runtime-5.0.0-preview.7.20364.11-x64.deb'
Note, selecting 'dotnet-runtime-deps-5.0' instead of '/root/dotnetinstall/dotnet_packages/dotnet-runtime-deps-5.0.0-preview.7.20364.11-x64.deb'
Note, selecting 'dotnet-sdk-5.0' instead of '/root/dotnetinstall/dotnet_packages/dotnet-sdk-5.0.100-preview.7.20366.6-x64.deb'
Note, selecting 'dotnet-targeting-pack-5.0' instead of '/root/dotnetinstall/dotnet_packages/dotnet-targeting-pack-5.0.0-preview.7.20364.11-x64.deb'
Note, selecting 'netstandard-targeting-pack-2.1' instead of '/root/dotnetinstall/dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb'
The following packages will be upgraded:
  aspnetcore-runtime-5.0 aspnetcore-targeting-pack-5.0 dotnet-apphost-pack-5.0
  dotnet-host dotnet-hostfxr-5.0 dotnet-runtime-5.0 dotnet-runtime-deps-5.0
  dotnet-sdk-5.0 dotnet-targeting-pack-5.0
The following packages will be DOWNGRADED:
  netstandard-targeting-pack-2.1
9 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
E: Packages were downgraded and -y was used without --allow-downgrades.

Here's a simple repro command for Debian 10 isolated in Docker, if it helps, @NikolaMilosavljevic @leecow. It uses the artifacts directly rather than running through the full script for simplicity.
The versions being exactly the same (2.1.0-1) yet still causing this error is surprising and doesn't match up to my theory above... not sure what's going on here but perhaps the error message shouldn't necessarily be trusted:
docker run -it --rm debian:10 bash -c '
  set -x
  apt update
  apt install -y wget
  wget https://packages.microsoft.com/config/debian/10/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
  dpkg -i packages-microsoft-prod.deb
  apt update
  apt install -y netstandard-targeting-pack-2.1
  apt info netstandard-targeting-pack-2.1
  wget https://dotnetcli.blob.core.windows.net/dotnet/release/install-preview/5.0.0-preview.7/dotnet-5.0.0-preview.7-deb.tar.gz
  tar -xf dotnet-5.0.0-preview.7-deb.tar.gz
  mv ./dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb netstandard.deb
  chmod g+r netstandard.deb
  apt info ./netstandard.deb
  apt install -y ./netstandard.deb'
...
+ apt info netstandard-targeting-pack-2.1
Package: netstandard-targeting-pack-2.1
Version: 2.1.0-1
...
+ apt info ./netstandard.deb
Package: netstandard-targeting-pack-2.1
Version: 2.1.0-1
...
+ apt install -y ./netstandard.deb
...
The following packages will be DOWNGRADED:
  netstandard-targeting-pack-2.1

Again, bumped into this on Debian Buster and discovered this GitHub issue. With the packages from .NET Core 3.1 SDK installed, I get this exact error and can reproduce the error easily:
Using apt - fails as above
$ sudo apt install -y ./dotnet_packages/*.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'aspnetcore-runtime-5.0' instead of './dotnet_packages/aspnetcore-runtime-5.0.0-preview.8.20414.8-x64.deb'
Note, selecting 'aspnetcore-targeting-pack-5.0' instead of './dotnet_packages/aspnetcore-targeting-pack-5.0.0-preview.8.20414.8.deb'
Note, selecting 'dotnet-apphost-pack-5.0' instead of './dotnet_packages/dotnet-apphost-pack-5.0.0-preview.8.20407.11-x64.deb'
Note, selecting 'dotnet-host' instead of './dotnet_packages/dotnet-host-5.0.0-preview.8.20407.11-x64.deb'
Note, selecting 'dotnet-hostfxr-5.0' instead of './dotnet_packages/dotnet-hostfxr-5.0.0-preview.8.20407.11-x64.deb'
Note, selecting 'dotnet-runtime-5.0' instead of './dotnet_packages/dotnet-runtime-5.0.0-preview.8.20407.11-x64.deb'
Note, selecting 'dotnet-runtime-deps-5.0' instead of './dotnet_packages/dotnet-runtime-deps-5.0.0-preview.8.20407.11-x64.deb'
Note, selecting 'dotnet-sdk-5.0' instead of './dotnet_packages/dotnet-sdk-5.0.100-preview.8.20417.9-x64.deb'
Note, selecting 'dotnet-targeting-pack-5.0' instead of './dotnet_packages/dotnet-targeting-pack-5.0.0-preview.8.20407.11-x64.deb'
Note, selecting 'netstandard-targeting-pack-2.1' instead of './dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb'
aspnetcore-runtime-5.0 is already the newest version (5.0.0~preview.8.20414.8-1).
aspnetcore-targeting-pack-5.0 is already the newest version (5.0.0~preview.8.20414.8-1).
dotnet-apphost-pack-5.0 is already the newest version (5.0.0~preview.8.20407.11-1).
dotnet-host is already the newest version (5.0.0~preview.8.20407.11-1).
dotnet-host set to manually installed.
dotnet-hostfxr-5.0 is already the newest version (5.0.0~preview.8.20407.11-1).
dotnet-runtime-5.0 is already the newest version (5.0.0~preview.8.20407.11-1).
dotnet-runtime-deps-5.0 is already the newest version (5.0.0~preview.8.20407.11-1).
dotnet-sdk-5.0 is already the newest version (5.0.100-preview.8.20417.9-1).
dotnet-targeting-pack-5.0 is already the newest version (5.0.0~preview.8.20407.11-1).
The following packages will be DOWNGRADED:
  netstandard-targeting-pack-2.1
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 62 not upgraded.
E: Packages were downgraded and -y was used without --allow-downgrades.

Using dpkg - works fine
If I instead switch to using dpkg instead of apt (which feels more natural with local packages IMHO), it works flawlessly:
$ sudo dpkg -i ./dotnet_packages/*.deb
(Reading database ... 229589 files and directories currently installed.)
Preparing to unpack .../aspnetcore-runtime-5.0.0-preview.8.20414.8-x64.deb ...
Unpacking aspnetcore-runtime-5.0 (5.0.0~preview.8.20414.8-1) over (5.0.0~preview.8.20414.8-1) ...
Preparing to unpack .../aspnetcore-targeting-pack-5.0.0-preview.8.20414.8.deb ...
Unpacking aspnetcore-targeting-pack-5.0 (5.0.0~preview.8.20414.8-1) over (5.0.0~preview.8.20414.8-1) ...
Preparing to unpack .../dotnet-apphost-pack-5.0.0-preview.8.20407.11-x64.deb ...
Unpacking dotnet-apphost-pack-5.0 (5.0.0~preview.8.20407.11-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../dotnet-host-5.0.0-preview.8.20407.11-x64.deb ...
Unpacking dotnet-host (5.0.0~preview.8.20407.11-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../dotnet-hostfxr-5.0.0-preview.8.20407.11-x64.deb ...
Unpacking dotnet-hostfxr-5.0 (5.0.0~preview.8.20407.11-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../dotnet-runtime-5.0.0-preview.8.20407.11-x64.deb ...
Unpacking dotnet-runtime-5.0 (5.0.0~preview.8.20407.11-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../dotnet-runtime-deps-5.0.0-preview.8.20407.11-x64.deb ...
Unpacking dotnet-runtime-deps-5.0 (5.0.0~preview.8.20407.11-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../dotnet-sdk-5.0.100-preview.8.20417.9-x64.deb ...
Unpacking dotnet-sdk-5.0 (5.0.100-preview.8.20417.9-1) over (5.0.100-preview.8.20417.9-1) ...
Preparing to unpack .../dotnet-targeting-pack-5.0.0-preview.8.20407.11-x64.deb ...
Unpacking dotnet-targeting-pack-5.0 (5.0.0~preview.8.20407.11-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb ...
Unpacking netstandard-targeting-pack-2.1 (2.1.0-1) over (2.1.0-1) ...
Setting up dotnet-apphost-pack-5.0 (5.0.0~preview.8.20407.11-1) ...
Setting up dotnet-host (5.0.0~preview.8.20407.11-1) ...
Setting up dotnet-hostfxr-5.0 (5.0.0~preview.8.20407.11-1) ...
Setting up dotnet-runtime-deps-5.0 (5.0.0~preview.8.20407.11-1) ...
Setting up dotnet-targeting-pack-5.0 (5.0.0~preview.8.20407.11-1) ...
Setting up netstandard-targeting-pack-2.1 (2.1.0-1) ...
Setting up aspnetcore-targeting-pack-5.0 (5.0.0~preview.8.20414.8-1) ...
Setting up dotnet-runtime-5.0 (5.0.0~preview.8.20407.11-1) ...
Setting up aspnetcore-runtime-5.0 (5.0.0~preview.8.20414.8-1) ...
Setting up dotnet-sdk-5.0 (5.0.100-preview.8.20417.9-1) ...
This software may collect information about you and your use of the software, and send that to Microsoft.
Please visit http://aka.ms/dotnet-cli-eula for more information.
Welcome to .NET!
---------------------
Learn more about .NET: https://aka.ms/dotnet-docs
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. The data is anonymous and doesn't include command-line arguments. The data is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

Configuring...
--------------
A command is running to populate your local package cache to improve restore speed and enable offline access. This command takes up to one minute to complete and only runs once.
Processing triggers for man-db (2.8.5-2) ...

If someone points me to the install-dotnet-preview.sh script, I can file a pull request to get this fixed. (or by all means, fix it yourself if you feel so inclined)

Update: I discovered the --verbose-versions flag in apt, which gives us this, shedding some further light on this weird, weird issue:
$ sudo apt install --verbose-versions  -y ./dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'netstandard-targeting-pack-2.1' instead of './dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb'
The following packages will be DOWNGRADED:
   netstandard-targeting-pack-2.1 (2.1.0-1 => 2.1.0-1)
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 62 not upgraded.
E: Packages were downgraded and -y was used without --allow-downgrades.

This almost feels like a bug in apt-get to me. If someone feels like it, it would make sense to report this to Debian upstream as well.

If I instead switch to using dpkg instead of apt (which feels more natural with local packages IMHO)

I don't think we can just do this: dotnet-runtime-deps-5.0 depends on distro-provided library packages that need to be installed from the distro repositories for .NET to be able to run. My understanding is that dpkg would just complain, then you'd have to install all those packages manually and run the script again, or something like that.
This is interesting though, and maybe a hybrid/more complex approach would be a viable workaround.

If someone points me to the install-dotnet-preview.sh script

AFAIK this script isn't maintained on GitHub, but I believe @leecow and @rbhanda own it and may accept a patch anyway.

I don't think we can just do this: dotnet-runtime-deps-5.0 depends on distro-provided library packages that need to be installed from the distro repositories for .NET to be able to run.

Very good point. I agree, flawed logic on my behalf. :see_no_evil:
I looked a bit more now and here is the URL to the "official", released version of this package (coming from packages.microsoft.com):
$ sudo apt-get -f install --print-uris
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  netstandard-targeting-pack-2.1
The following NEW packages will be installed:
  netstandard-targeting-pack-2.1
0 upgraded, 1 newly installed, 0 to remove and 62 not upgraded.
Need to get 1,474 kB of archives.
After this operation, 20.2 MB of additional disk space will be used.
'https://packages.microsoft.com/debian/10/prod/pool/main/n/netstandard-targeting-pack-2.1/netstandard-targeting-pack-2.1.0-x64.deb' netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb 1474124 MD5Sum:83005b6765f03ca8c6d07d9b01b3ad71

Do note the MD5 checksum there at the end (83005b6765f03ca8c6d07d9b01b3ad71).
But if I check with the package being downloaded from this script:
$ sudo md5sum dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
d87876ad63b5f8fddf1ec78acbae2de3  dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
$ sudo ls -l dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
-rwx------ 1 501 staff 1476016 apr 23 21:06 dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb

...it's something completely different. The file size is different also.
The package in the distribution seems to be built at 2019-09-18:
$ sudo dpkg-deb -c dotnet_packages/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
drwxr-xr-x root/root         0 2019-09-18 01:46 ./
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/doc/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/doc/netstandard-targeting-pack-2.1/
-rw-r--r-- root/root       194 2019-09-18 01:46 ./usr/share/doc/netstandard-targeting-pack-2.1/changelog.Debian.gz
-rw-r--r-- root/root      1498 2019-09-18 01:46 ./usr/share/doc/netstandard-targeting-pack-2.1/copyright
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/dotnet/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/dotnet/packs/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/dotnet/packs/NETStandard.Library.Ref/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/
drwxr-xr-x root/root         0 2019-09-18 01:46 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/data/
[...]

...while the package provided from packages.microsoft.com seems to be slightly more recent:
$ sudo dpkg-deb -c /var/cache/apt/archives/netstandard-targeting-pack-2.1_2.1.0-1_amd64.deb
drwxr-xr-x root/root         0 2019-10-11 17:19 ./
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/packs/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/data/
-rw-r--r-- root/root     25681 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/data/FrameworkList.xml
-rw-r--r-- root/root      3177 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/data/PackageOverrides.txt
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/
drwxr-xr-x root/root         0 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/
-rw-r--r-- root/root     14200 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/System.Linq.Parallel.dll
-rw-r--r-- root/root     14712 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/System.Net.Primitives.dll
-rw-r--r-- root/root     13688 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/System.Buffers.dll
-rw-r--r-- root/root     14200 2019-10-11 17:19 ./usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/System.Text.RegularExpressions.dll
[...]

As for the checksums being different, I guess it could be that apt (which is a more recent, high-level tool) is more strict here than dpkg; dpkg can be seen as the more "raw" utility here, with capabilities to fully destroy your system if you just give it the right parameters. :smirk: Different MD5 checksums/older content => it could be that it's smart enough to understand that this is somehow a "downgrade" perhaps? (even though "downgrade" is not technically 100% accurate...)
Anyway, re-publishing a package with the exact same version number but with different content seems a bit odd on our behalf. Given these facts, I will not proceed with reporting this to Debian at this point. Could someone with enough insight into this try to dig in and figure out where the .deb package inside https://dotnetcli.blob.core.windows.net/dotnet/release/install-preview/5.0.0-preview.8/dotnet-5.0.0-preview.8-deb.tar.gz is coming from? And try to update it with the correct, officially released version of this package.

PTAL @rbhanda

Ping @rbhanda, any updates on this?

Are you still seeing this issue with .NET 5 RC 1 update?

Works for me now on .NET 5 RC 1

@rbhanda Trying it now. (As a side note, the dotnetcli.blob.core.windows.net host is horribly slow btw, I get download speeds in the 2-3 Mbit/s range - would be great to get proper CDN acceleration on these builds as well.)
Anyway, looks much better on the new version (except for the notice at the end):
Full install log
*** Checking required system dependencies for detected OS: Debian GNU/Linux 10 (buster) ...
***     tar is already installed.
***     gzip is already installed.
***     curl is already installed.

*** Setting package type to deb.
*** Download source: dotnet-5.0.0-rc.1-deb.tar.gz

*** Downloading https://dotnetcli.blob.core.windows.net/dotnet/release/install-preview/5.0.0-rc.1/dotnet-5.0.0-rc.1-deb.tar.gz to /home/per/dotnet_install ...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 88.4M  100 88.4M    0     0   277k      0  0:05:26  0:05:26 --:--:--  289k

*** Unpacking dotnet-5.0.0-rc.1-deb.tar.gz ...

dotnet_packages/
dotnet_packages/dotnet-host-5.0.0-rc.1.20451.14-x64.deb
dotnet_packages/dotnet-hostfxr-5.0.0-rc.1.20451.14-x64.deb
dotnet_packages/dotnet-targeting-pack-5.0.0-rc.1.20451.14-x64.deb
dotnet_packages/aspnetcore-targeting-pack-5.0.0-rc.1.20451.17.deb
dotnet_packages/dotnet-sdk-5.0.100-rc.1.20452.10-x64.deb
dotnet_packages/._netstandard-targeting-pack-2.1.0-x64.deb
dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb
dotnet_packages/dotnet-apphost-pack-5.0.0-rc.1.20451.14-x64.deb
dotnet_packages/aspnetcore-runtime-5.0.0-rc.1.20451.17-x64.deb
dotnet_packages/dotnet-runtime-deps-5.0.0-rc.1.20451.14-x64.deb
dotnet_packages/dotnet-runtime-5.0.0-rc.1.20451.14-x64.deb

Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'aspnetcore-runtime-5.0' instead of '/home/per/dotnet_install/dotnet_packages/aspnetcore-runtime-5.0.0-rc.1.20451.17-x64.deb'
Note, selecting 'aspnetcore-targeting-pack-5.0' instead of '/home/per/dotnet_install/dotnet_packages/aspnetcore-targeting-pack-5.0.0-rc.1.20451.17.deb'
Note, selecting 'dotnet-apphost-pack-5.0' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-apphost-pack-5.0.0-rc.1.20451.14-x64.deb'
Note, selecting 'dotnet-host' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-host-5.0.0-rc.1.20451.14-x64.deb'
Note, selecting 'dotnet-hostfxr-5.0' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-hostfxr-5.0.0-rc.1.20451.14-x64.deb'
Note, selecting 'dotnet-runtime-5.0' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-runtime-5.0.0-rc.1.20451.14-x64.deb'
Note, selecting 'dotnet-runtime-deps-5.0' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-runtime-deps-5.0.0-rc.1.20451.14-x64.deb'
Note, selecting 'dotnet-sdk-5.0' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-sdk-5.0.100-rc.1.20452.10-x64.deb'
Note, selecting 'dotnet-targeting-pack-5.0' instead of '/home/per/dotnet_install/dotnet_packages/dotnet-targeting-pack-5.0.0-rc.1.20451.14-x64.deb'
Note, selecting 'netstandard-targeting-pack-2.1' instead of '/home/per/dotnet_install/dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb'
netstandard-targeting-pack-2.1 is already the newest version (2.1.0-1).
netstandard-targeting-pack-2.1 set to manually installed.
The following packages will be upgraded:
  aspnetcore-runtime-5.0 aspnetcore-targeting-pack-5.0 dotnet-apphost-pack-5.0 dotnet-host dotnet-hostfxr-5.0
  dotnet-runtime-5.0 dotnet-runtime-deps-5.0 dotnet-sdk-5.0 dotnet-targeting-pack-5.0
9 upgraded, 0 newly installed, 0 to remove and 67 not upgraded.
Need to get 0 B/91.3 MB of archives.
After this operation, 17.8 MB disk space will be freed.

Preparing to unpack .../0-dotnet-runtime-deps-5.0.0-rc.1.20451.14-x64.deb ...
Unpacking dotnet-runtime-deps-5.0 (5.0.0~rc.1.20451.14-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../1-dotnet-host-5.0.0-rc.1.20451.14-x64.deb ...
Unpacking dotnet-host (5.0.0~rc.1.20451.14-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../2-dotnet-hostfxr-5.0.0-rc.1.20451.14-x64.deb ...
Unpacking dotnet-hostfxr-5.0 (5.0.0~rc.1.20451.14-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../3-dotnet-runtime-5.0.0-rc.1.20451.14-x64.deb ...
Unpacking dotnet-runtime-5.0 (5.0.0~rc.1.20451.14-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../4-aspnetcore-runtime-5.0.0-rc.1.20451.17-x64.deb ...
Unpacking aspnetcore-runtime-5.0 (5.0.0~rc.1.20451.17-1) over (5.0.0~preview.8.20414.8-1) ...
Preparing to unpack .../5-dotnet-targeting-pack-5.0.0-rc.1.20451.14-x64.deb ...
Unpacking dotnet-targeting-pack-5.0 (5.0.0~rc.1.20451.14-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../6-aspnetcore-targeting-pack-5.0.0-rc.1.20451.17.deb ...
Unpacking aspnetcore-targeting-pack-5.0 (5.0.0~rc.1.20451.17-1) over (5.0.0~preview.8.20414.8-1) ...
Preparing to unpack .../7-dotnet-apphost-pack-5.0.0-rc.1.20451.14-x64.deb ...
Unpacking dotnet-apphost-pack-5.0 (5.0.0~rc.1.20451.14-1) over (5.0.0~preview.8.20407.11-1) ...
Preparing to unpack .../8-dotnet-sdk-5.0.100-rc.1.20452.10-x64.deb ...
Unpacking dotnet-sdk-5.0 (5.0.100-rc.1.20452.10-1) over (5.0.100-preview.8.20417.9-1) ...
Setting up dotnet-host (5.0.0~rc.1.20451.14-1) ...
Setting up dotnet-runtime-deps-5.0 (5.0.0~rc.1.20451.14-1) ...
Setting up dotnet-hostfxr-5.0 (5.0.0~rc.1.20451.14-1) ...
Setting up dotnet-apphost-pack-5.0 (5.0.0~rc.1.20451.14-1) ...
Setting up dotnet-targeting-pack-5.0 (5.0.0~rc.1.20451.14-1) ...
Setting up aspnetcore-targeting-pack-5.0 (5.0.0~rc.1.20451.17-1) ...
Setting up dotnet-runtime-5.0 (5.0.0~rc.1.20451.14-1) ...
Setting up aspnetcore-runtime-5.0 (5.0.0~rc.1.20451.17-1) ...
Setting up dotnet-sdk-5.0 (5.0.100-rc.1.20452.10-1) ...
This software may collect information about you and your use of the software, and send that to Microsoft.
Please visit http://aka.ms/dotnet-cli-eula for more information.
Welcome to .NET!
---------------------
Learn more about .NET: https://aka.ms/dotnet-docs
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

Configuring...
--------------
A command is running to populate your local package cache to improve restore speed and enable offline access. This command takes up to one minute to complete and only runs once.
Processing triggers for man-db (2.8.5-2) ...
N: Download is performed unsandboxed as root as file '/home/per/dotnet_install/dotnet_packages/dotnet-runtime-deps-5.0.0-rc.1.20451.14-x64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

An apt-get notice
(Notices are probably mostly harmless, but could still be worth investigating what is causing this:)

N is for notices. A notice is something that the program wants you to be aware of but that is not a warning. A typical notice from apt is N: There is 1 additional version. Please use the '-a' switch to see it.

As for the contents of the archive, it does look a bit dubious still:
Archive contents
$ tar tvf dotnet-5.0.0-rc.1-deb.tar.gz
drwxr-xr-x rahulbhandari/staff 0 2020-09-12 02:27 dotnet_packages/
-rwx------ rahulbhandari/staff 52306 2020-09-11 21:44 dotnet_packages/dotnet-host-5.0.0-rc.1.20451.14-x64.deb
-rwx------ rahulbhandari/staff<PHONE_NUMBER>-09-11 21:44 dotnet_packages/dotnet-hostfxr-5.0.0-rc.1.20451.14-x64.deb
-rwx------ rahulbhandari/staff 1873794 2020-09-11 21:45 dotnet_packages/dotnet-targeting-pack-5.0.0-rc.1.20451.14-x64.deb
-rwx------ rahulbhandari/staff 1169878 2020-09-11 21:44 dotnet_packages/aspnetcore-targeting-pack-5.0.0-rc.1.20451.17.deb
-rwx------ rahulbhandari/staff 56616970 2020-09-11 21:46 dotnet_packages/dotnet-sdk-5.0.100-rc.1.20452.10-x64.deb
-rw-r--r-- rahulbhandari/staff      686 2020-09-12 02:22 dotnet_packages/._netstandard-targeting-pack-2.1.0-x64.deb
-rw-r--r-- rahulbhandari/staff  1474124 2020-09-12 02:22 dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb
-rwx------ rahulbhandari/staff  3406392 2020-09-11 21:45 dotnet_packages/dotnet-apphost-pack-5.0.0-rc.1.20451.14-x64.deb
-rwx------ rahulbhandari/staff  6005130 2020-09-11 21:44 dotnet_packages/aspnetcore-runtime-5.0.0-rc.1.20451.17-x64.deb
-rwx------ rahulbhandari/staff     2642 2020-09-11 21:45 dotnet_packages/dotnet-runtime-deps-5.0.0-rc.1.20451.14-x64.deb
-rwx------ rahulbhandari/staff 22027756 2020-09-11 21:44 dotnet_packages/dotnet-runtime-5.0.0-rc.1.20451.14-x64.deb

Note the strange dotnet_packages/._netstandard-targeting-pack-2.1.0-x64.deb entry there. Seems like a mistake?
$ file dotnet_packages/._netstandard-targeting-pack-2.1.0-x64.deb
dotnet_packages/._netstandard-targeting-pack-2.1.0-x64.deb: AppleDouble encoded Macintosh file

The rahulbhandari/staff ownerships there also looks a bit odd, compared to the root/root in the previous example. I guess this archive was manually created by you @rbhanda, after inspecting the contents of the files or something?
The netstandard-targeting-pack-2.1.0-x64.deb file
As for the dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb file itself, it looks much better this time. It's definitely the same file as coming from packages.microsoft.com:
$ ls -l dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb
-rw-r--r-- 1 501 staff 1474124 sep 12 02:22 dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb
$ md5sum dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb
83005b6765f03ca8c6d07d9b01b3ad71  dotnet_packages/netstandard-targeting-pack-2.1.0-x64.deb

So, bottom line: the bigger problem has been resolved AFAICT. These minor issues pointed out here are more of an annoyance than anything else; it doesn't affect the end-user experience of being able to install/not install the packages => much better than in the Preview version. If I was maintaining the install experience, I would still give it a look though, to avoid the install looking slightly "weird" to more experienced users.


ADD: Cache HTTP downloads for faster builds

When an ADD http resource takes more than a few seconds to download, it really slows down the build. Could Docker cache these, e.g. in ~/.docker/downloads, so that repeated builds are faster and Dockerfile experimentation becomes more enjoyable?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Thanks for suggesting, this looks like a duplicate of https://github.com/docker/docker/issues/15717, so I'll close this one. Please subscribe to that issue (using the "subscribe" button) to keep up to date on progress


Sin/Cos canvas path

Hello. I was considering implementing a wave-like motion. so I need some sin or cos path. I have tried to implement it and make a pr to flutter engine and I need some help.
here at painting.dart file in flutter engine, at line 2355: there is some native keyword. and is referencing to Path_conicTo. I could not find any documentation about this native keyword. and could you please help me how can I add sin/cos path functions?
Thanks in advance.

there is some native keyword. and is referencing to Path_conicTo

The native keyword from what I understand, means that the implementation of that method is deferred to a native call. Kindly see https://dart.dev/server/c-interop-native-extensions for more information.
The actual implementation of void conicTo(double x1, double y1, double x2, double y2, double w) can be found in
https://github.com/flutter/engine/blob/c797abff336f96a5cb9ae027ed6b34d0b6131bbf/lib/ui/painting/path.cc#L150-L153
In the future, kindly visit any of the communities in https://flutter.dev/community#community-grid for asking these kinds of questions.
Closing as this is neither a feature request nor a bug report.
Thank you


clusterrole wrong apigroup or wrong list/get

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
22.2.0
What version of Traefik are you using?
2.9.10
What did you do?
Update chart from 21.2.0 to 22.2.0 with argocd
What did you see instead?
After upgrade no ingress works and  I can see these logs (traefik pods):
[traefik-rg8wm] W0425 09:32:21.141862       1 reflector.go:424] k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: failed to list *v1alpha1.TLSOption: tlsoptions.traefik.io is forbidden: User "system:serviceaccount:traefik:traefik" cannot list resource "tlsoptions" in API group "traefik.io" at the cluster scope
[traefik-rg8wm] E0425 09:32:21.143198       1 reflector.go:140] k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: Failed to watch *v1alpha1.TLSOption: failed to list *v1alpha1.TLSOption: tlsoptions.traefik.io is forbidden: User "system:serviceaccount:traefik:traefik" cannot list resource "tlsoptions" in API group "traefik.io" at the cluster scope
[traefik-6dblq] W0425 09:32:21.513794       1 reflector.go:424] k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: failed to list *v1alpha1.ServersTransport: serverstransports.traefik.io is forbidden: User "system:serviceaccount:traefik:traefik" cannot list resource "serverstransports" in API group "traefik.io" at the cluster scope
[traefik-6dblq] E0425 09:32:21.513832       1 reflector.go:140] k8s.io/client-go@v0.26.3/tools/cache/reflector.go:169: Failed to watch *v1alpha1.ServersTransport: failed to list *v1alpha1.ServersTransport: serverstransports.traefik.io is forbidden: User "system:serviceaccount:traefik:traefik" cannot list resource "serverstransports" in API group "traefik.io" at the cluster scope

What is your environment & configuration?

k3s v1.26.3+k3s1
traefik values.yaml (stripped down)

deployment:
  kind: DaemonSet

priorityClassName: cluster-critical

providers:
  kubernetesCRD:
    enabled: true
    allowCrossNamespace: true
    allowExternalNameServices: true

  kubernetesIngress:
    enabled: true
    allowExternalNameServices: true
    publishedService:
      enabled: true

globalArguments: []

ports:
  web:
    port: 8080
    redirectTo: websecure
  websecure:
    expose: true
    port: 8443
    tls:
      enabled: true

tlsOptions:
  default:
    minVersion: VersionTLS12

tlsStore:
  default:
    defaultCertificate:
      secretName: wildcard-cert

service:
  spec:
    loadBalancerIP: "x.x.x.x"
    externalTrafficPolicy: Local

Additional Information
No response

Hello @brightdroid,
This is not coming from Helm Chart v22.2.0 but from Traefik v2.10.
We have already made some PRs. A new release of this Chart is coming.
=> This should work with Helm Chart v22.3.0

@brightdroid v22.3.0 is here.
Please follow carefully documentation about specifics on CRDs upgrade and that should work.

Thank you :+1:


Validation message hard to understand

I tried to add a new phenopacket where I entered only the information for the "Individual" section. I get this validation message. After pondering for awhile perhaps it means I must enter at least something on one of the other sections? Can the message be clearer? I also note that it looks like I can click the "complete" button. Is that okay, i.e. the message is only a warning?

I tried using the "complete" button and now I have my new phenopacket listed. I saved the json. Then I tried clicking the yellow "validation" button. That brings up the same message as shown above.
When I clicked on OK, my phenopacket has vanished, it is no longer listed. --- update, I can't duplicate this, my best guess is I accidentally managed to click on the delete icon.
I tried uploading the json and nothing happens, it is not uploaded. This I can duplicate, the json must be malformed since it had the error shown above. I am able to upload the json for other phenopackets. Should the user be able to save the json for a phenopacket with warnings?

could you upload on this issue the json of the created phenopacket?

@belkassaby This is what won't upload:
{
"id": "Beth test 1 on Wed",
"subject": {
"id": "sqa testing",
"alternateIds": [],
"sex": "FEMALE",
"karyotypicSex": "XX",
"vitalStatus": {
"status": "ALIVE"
}
},
"phenotypicFeatures": [],
"measurements": [],
"biosamples": [],
"interpretations": [],
"diseases": [],
"medicalActions": [],
"files": [],
"metaData": {
"createdBy": "Anonymous undefined",
"submittedBy": "Anonymous undefined",
"resources": [],
"created": "2023-06-14T13:39:42.714Z",
"externalReferences": [],
"phenopacketSchemaVersion": "2.0"
}
}

Weird... seems to work for me : the upload of that json:

I give up, it would not upload, I closed the browser tab and started again and it did upload. So there was something odd happening. I will put in an issue if I can figure it out.
Meanwhile, is there a way to improve the messages from the validator?

@belkassaby @BethSundberg this is actually a bug on the validator side and a false positive error. The validator is complaining about missing metadata > resource elements. However, based on created phenopacket, there is no need for a resource element. Thank you for pointing it out, I will fix the validator.
Let's keep this issue open until I update the validator, use it in PhenopacketLab and verify that the input does not raise any errors.

This exact scenario does not occur anymore.


Unlisted uploads still visible on Google

Not sure how it's happening or how to prevent it but unlisted uploads should preferably not be indexed by Google etc

robots.txt with relevant rules on the page of unlisted video
require an account to view unlisted videos and redirect anyone not meeting the criteria to the signup page
XML sitemap

The first one will be relatively simple, but won't help against aggressive crawlers which don't honor the rules.
The second one requires some redirection setups, but will defend against aggressive crawlers.
The third one is the hardest, but also will help with general SEO immensely.


Optimize assets/images

Compressed all image assets with TinyPNG to save ~65%

Amazing, thanks for this contribution!


Revert binary incompatible change

Otherwise, it is not possible to use this snapshot with sqldelight without patching sqldelight too.
Only effects sqldelight snapshots using the unshaded dependencies.

I think this is a little bit useless, coz there are many source-breaking changes too.


Doesn't work when more than one space in a name

Hi, cool extension!
Just a note, it doesn't work when a professor has more than one space in their name. This is because of how the extension handles names on Testudo. Here are the relevant lines: https://github.com/MatthewFoulk/UMDProfessorRatings/blob/master/content.js#L60-L63

Thanks for the feedback! I've added some minor changes to handle multi-spaced names. Once the updated version is approved by the Chrome Web Store, it should be good to go.


Fatal NI connect error 12170

I have an oracle database 19.3 docker container (created from original image) on an ubuntu machine, and it was working just fine up until a few weeks before. But one day out of nowhere (literally without  even touching the server) something happened:
The applications on the server itself (which is running ubuntu) cannot connect to the database with the following error, but the windows machines can connect to the database like always. I checked the container logs and the startup is completely successful (with the "DATABASE IS READY TO USE! message") but after that, it gives the following error every few seconds.
The error:
Fatal NI connect error 12170, connecting to:
 (ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=47372))

  VERSION INFORMATION:
	TNS for Linux: Version <IP_ADDRESS>.0 - Production
	Oracle Bequeath NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
	TCP/IP NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
  Version <IP_ADDRESS>.0
  Time: 28-DEC-2020 17:40:31
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12535

TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
2020-12-28T17:40:31.183746+00:00
opiodr aborting process unknown ospid (9220) as a result of ORA-609
2020-12-28T17:40:36.537932+00:00

I searched the web and I found a suggestion, to add the following line to the sqlnet.ora:
SQLNET.INBOUND_CONNECT_TIMEOUT=300

I did but it didn't help.

After changing the SQLNET.INBOUND_CONNECT_TIMEOUT to 300, did the clients connection failed 300 seconds after initiating the connection?  If not, the server needs to be recycled after the changing the parameter.

After changing the SQLNET.INBOUND_CONNECT_TIMEOUT to 300, did the clients connection failed 300 seconds after initiating the connection?  If not, the server needs to be recycled after the changing the parameter.

+1
Had the same problem. Database was running fine for 4 weeks then stopped accepting external TNS connections without warning.

Hi @pgoldtho
I am still not sure why it happened on my servers, but this blog saved me from endless debugging. https://franckpachot.medium.com/19c-instant-client-and-docker-1566630ab20e
I set the DISABLE_OOB=ON and everything worked again. I hope that solves your issue as well

Thanks @sandorzelei
Adding DISABLE_OOB=ON to the client's sqlnet.ora did resolve the connection issue. That said, we decided to abandon our Docker deployment project based on this and other issues we encountered.

I am also getting this issue now with the 21c image. What is the workaround - I am really confused?

Thanks @sandorzelei
Adding DISABLE_OOB=ON to the client's sqlnet.ora did resolve the connection issue. That said, we decided to abandon our Docker deployment project based on this and other issues we encountered.

Thanx for the tip, adding DISABLE_OOB=ON at worked for me, short INFO for those who needed badly i used the following repo "https://hub.docker.com/r/oracledb19c/oracle.19.3.0-ee"


Variable 'cap' collides with the 'builtin' function

We'd better rename the variable cap to avoid unnecessary troubles.
/kind cleanup

/assign


Show incorrect message in case add new provider

Describe the bug
Show incorrect message in case add new provider
To reproduce the behavior
Steps:

Go to the add new provider screen
Input the invalid provider (provider of another network)
Click on save button then observe the message displayed

Actual: Show incorect message

Message: This chain has already been added

Expect: Show message: This provider is not for this network

Version test: https://file.cdmteck.com/s/DB9JLAnjJczopcC/download?path=%2F&files=SubWalletMobile-build-221-1044-merge-2023-09-27T11-14-57.ipa
Device test: IP 11
@Quangdm-cdm Please re-check this issue: Show incorrect message in case add an existing provider
Actual: Show message "This provider is not for this network"
Expect: Show message "This provider has already been added"

Version test: https://file.cdmteck.com/s/DB9JLAnjJczopcC/download?path=%2F&files=SubWalletMobile-build-221-1044-merge-2023-09-28T08-39-06.apk
Device test: Samsung S20 FE 5G
Validation passed.


[BUG] docker version does not match giga_connectome version

$ docker run -it --rm  bids/giga_connectome:0.5.0 --version
0.5.1.dev0+gd97c669.d20240412

pretty sure this is because some files tracked by git are not dockerignored and thus appear as 'deleted' inside the container so hatchling gives it a dirty version number

yup that seems to be the issue:
docker run -it --rm --entrypoint /bin/bash bids/giga_connectome:0.5.0
root@4ccc46ca6884:/code# git status
HEAD detached at 0.5.0
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..."


Conflict - Anima tree not replantable

The anima trees are no longer replantable following one of the additions (either pruning, ritual def, or cultivation)
Loading extraction mods further down the load order doesn't resolve issue

confirmed this is an issue caused by the Ragnarok mod specifically

fixed by fc0681ee4c32f07eefe5fe4bb2efa7e03ac192ed
Turns out rimrim uses <harvestTag>Wood</harvestTag> to determine if something is a tree so the harvesting made it not a tree; adding <forceIsTree>True</forceIsTree> resolves this


drivers: modem: wistron kconfig separation

Separates Wistron Kconfig to a separate file.
This makes it cleaner for the future modem drivers and follows the same structure as every other driver category.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #13386   +/-   ##
=======================================
  Coverage   48.64%   48.64%
=======================================
  Files         319      319
  Lines       46540    46540
  Branches    10757    10757
=======================================
  Hits        22638    22638
  Misses      19316    19316
  Partials     4586     4586

Continue to review full report at Codecov.

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


TypeError when trying to connect to a remote repository

This happened out of the blue recently. No updates to attic have been done.

 attic check sshbackup:mybackup.attic
Traceback (most recent call last):
  File "/usr/bin/attic", line 3, in <module>
    main()
  File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 715, in main
    exit_code = archiver.run(sys.argv[1:])
  File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 705, in run
    return args.func(args)
  File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 69, in do_check
    repository = self.open_repository(args.repository, exclusive=args.repair)
  File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 32, in open_repository
    repository = RemoteRepository(location, create=create)
  File "/usr/lib64/python3.4/site-packages/attic/remote.py", line 118, in __init__
    version = self.call('negotiate', 1)
  File "/usr/lib64/python3.4/site-packages/attic/remote.py", line 127, in call
    for resp in self.call_many(cmd, [args], **kw):
  File "/usr/lib64/python3.4/site-packages/attic/remote.py", line 173, in call_many
    for type, msgid, error, res in self.unpacker:
TypeError: 'int' object is not iterable

In fact the unpacker's next method returns ints...

see PR #229.


No module named cPickle

Hello,I meet the problem “No module named cPickle” how to solve it？thanks！

i think u use Python3.5，try2.7

I just modified the code to support python3 for human_play. You can pull the new code and it should directly work for python3 now.


SpaceVim is by no means an editor

In the text editor section, SpaceVim is listed, which is misleading. SpaceVim is just a config for Vim or Neovim, it is not the editor itself. It makes not sense to list SpaceVim in the text editor section and make it the peer of Neovim/gvim etc.

SpaceVim is by no means a desktop editor. It's more like a Vim distribution with key bindings and plugins for supporting programming languages.


the datatable has no reaction to my actions

hi please, i try to use your component but unfortunately i have no reaction when i do actions like sort ( i don't use mokeData, and i don't no what i have to put in the handler), thank you

did you read the doc?


Refactor program prepend and postpend values out of EditorTabState

Description
On hindsight, the prepend & postpend values (i.e., code that is inserted at the start and end when evaluating Source programs) should be on a per-workspace basis instead of a per-editor tab basis so that they affect the entire program. This PR refactors the Redux store state to reflect this change.
Related to #2265. Part of the refactoring for #2176.
Type of change
None of the below.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test
There should not be any change in behaviour.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 21 (38.1%)  changed or added relevant lines in 5 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.002%) to 34.404%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/sagas/WorkspaceSaga.ts
2
3
66.67%

src/commons/editingWorkspace/EditingWorkspace.tsx
0
4
0.0%

src/commons/editingWorkspaceSideContent/EditingWorkspaceSideContentProgrammingQuestionTemplateTab.tsx
0
4
0.0%

src/pages/academy/grading/subcomponents/GradingWorkspace.tsx
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/pages/academy/grading/subcomponents/GradingWorkspace.tsx
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
4535

Relevant Lines:
12258

💛  - Coveralls

Seems like there's still one case of prependValue and postpendValue remaining in src/pages/playground/__tests__/Playground.tsx. Should this be refactored as well?

Seems like there's still some usages of prependValue and postpendValue left in src/pages/playground/__tests__/Playground.tsx and src/commons/sagas/__tests__/WorkspaceSaga.ts. Should these be refactored as well?

Oops, thanks for the catch!


Fix bug in AndroidManifest that prevented play store from displaying Zulip to certain user as an installable app.

Fixes: #4722
All of the relevant documentation is given in https://developer.android.com/guide/topics/manifest/uses-feature-element, it explains how play store filtering works and what a developer can do to control that.
gist is explained in the commit message of https://github.com/zulip/zulip-mobile/commit/199b73b6a72fe4f3c74fdba6e5a305bea13b67c1 of this PR.

Google Play filters which app to display to a user based on uses-sdk,
uses-permission and uses-feature tags.

In case uses-feature is not declared uses-permission is used to do
this filtering, and by default it treats the permission it needs as a
compulsory requirement for the app. Hence our app will not show in play
store for devices without the hardware of concern.

With uses-feature we override the filtering done by uses-permission
and by setting the required attribute to false we say that our app isn't
dependent on the hardware of concern to work properly (camera in case of
this commit).

Why did I specifically add android.hardware.camera and android.hardware.camera.autofocus in uses-feature?
Table 2 at https://developer.android.com/guide/topics/manifest/uses-feature-element#permissions gives a list which hardware requirements are affected by which specific permission. I am speculating here that without android.hardware.camera.autofocus an android device with camera but without autofocus hardware won't be shown our app as well.
I am wondering now what exactly will happen if a user without camera does press the button to access camera in our app, and if something like checking hardware availability be required?

Well spotted, thanks!
Looks like that ineffective android:required="false" on the uses-permission element was added in a836e7442 / #1843 (back in 2018), with the explanation that it was to make the app support Chromebooks. I wonder if anyone actually tested at the time that the change had any effect for Chromebooks.

In case uses-feature is not declared uses-permission is used to do
this filtering, and by default it treats the permission it needs as a
compulsory requirement for the app.

Yuck. Thanks for debugging this.
I took a look at that table:
https://developer.android.com/guide/topics/manifest/uses-feature-element#permissions
and compared it to the permissions in our manifest, to see if there are any others we should take care of in the same way. It looks like there's one more: ACCESS_WIFI_STATE, which implies feature android.hardware.wifi.

That one isn't in our own source code for the manifest, but I found it from looking through the manifest of the built app as installed on my device, using the handy Dexplorer app.
Dexplorer is good for browsing through all the different apps you have installed, but then if you open up our AndroidManifest.xml source file in Android Studio, and choose the "Merged Manifest" tab at the bottom, you get another view of the manifest of the built app:

including a handy cross-reference to what source file contributed any given bit of the manifest. So in that "Merging Log" section in the bottom right of that screenshot, we can see that three different libraries all asked for that permission in their own AndroidManifest.xml fragments: @react-native-community/netinfo, rn-fetch-blob, and Flipper. (The blue bits of text are links, and if you follow them it opens up the actual source files in question.)
I definitely recommend opening up that view in Android Studio and browsing around it a bit. There turns out to be quite a lot in our manifest that isn't in our own AndroidManifest.xml source files (and comes instead from various libraries), and it's educational to look around and get an idea of what's there and where it comes from.

There probably are very few Android devices indeed that don't have wifi. But the app should work fine without it -- it just needs some other way to talk to the Internet. So as long as we're here, we should probably make that feature optional too. Want to do that as a quick followup?

I am wondering now what exactly will happen if a user without camera does press the button to access camera in our app, and if something like checking hardware availability be required?

Good question. I agree with Wesley that I'd sure hope that would be treated as if the user had denied permission. I'm not finding docs addressing that question, but there is a mention here:
https://developer.android.com/training/permissions/requesting#handle-denial
that "[i]n certain situations, the permission might be denied automatically, without the user taking any action." Hopefully this is just one of those situations.
I think ideally we would indeed check hardware availability, and just not show the "camera" icon in the first place if there isn't a camera to use. Not a priority, though -- it'd be just a small polish issue, and only for very few users. If we were writing against the native Android SDK in the first place, I'd want to do that (because it'd be just a couple of lines of code); but because we'd have to wire that up through RN to the JS side, I think it won't be worth it.

OK, and merged! Thanks again.
I made a few small changes before merge:

Added a short comment explaining the new uses-feature elements; also deleted the blank line between them, in order to visually group them together and group them with the comment.
Added a bit more to the first commit message.
s/redundant/meaningless/ in the first commit message -- I would interpret "redundant" as meaning that there was already something else doing the same job, whereas the story here is more like that this attribute can't possibly do anything in the first place, and in fact nothing was successfully doing the job this attribute was intended to do.

See also the suggested followup above about feature android.hardware.wifi.


label_sync failing to create labels

label_sync prowjob is currently failing to create labels for a specific set of controllers (suspecting the same set of controllers mentioned in #1901 )
Sample logs: https://prow.ack.aws.dev/view/s3/ack-prow-logs/logs/label-sync/1702735092562006016

Fixed by adding the missing permissions to @ack-bot
/close


Images being used to display fonts in documentation.

Just wondering if this has been noted, and it could probably be easily cleaned up all at once? Perhaps the image is being used to display the text moving forward? As a legacy type display thing? It is however blurry as can be.

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

ID: 066e3064-216a-ec82-0a23-6bb572dc08db
Version Independent ID: ab853639-424f-a547-6dc8-f21cb73204b9
Content: Gill Sans MT Condensed font family - Typography
Content Source: typographydocs/font-list/gill-sans-mt-condensed.md
Product: typography
GitHub Login: @mijacobs
Microsoft Alias: mijacobs

I like the idea of keeping it an image so it natural to its appearance. Allowing people to look back on it in 15 years if needed. But the images do need to be cleaned up.
Perhaps something to dig into?

Thank you for pointing this out we will investigate this on our end.


Agents idle timer with --disconnect-after-idle-timeout disconnecting while running jobs on other spawns

Looks like https://github.com/buildkite/agent/issues/985 and https://github.com/buildkite/agent/issues/1003 were resolved, but now have a weird issue with disconnecting an agent while there is still a job running on one of my other spawned agents. The likelyhood is less likey than the above 2 jobs but can still occur and cause scaling issues.
Here is a log output of what occurs:
INFO   build.linux-i-0f7ff5055498a6746-1 Agent has been idle for 600 seconds
INFO   build.linux-i-0f7ff5055498a6746-3 Agent has been idle for 600 seconds
INFO   build.linux-i-0f7ff5055498a6746-3 Gracefully stopping agent. Since there is no job running, the agent will disconnect immediately
INFO   build.linux-i-0f7ff5055498a6746-4 Agent has been idle for 600 seconds
INFO   build.linux-i-0f7ff5055498a6746-3 Disconnecting...
INFO   build.linux-i-0f7ff5055498a6746-4 Process with PID: 7360 finished with Exit Status: 0
INFO   build.linux-i-0f7ff5055498a6746-4 Finished job 123456-6cd9-459a-bd73-9ff882bfe0db
INFO   build.linux-i-0f7ff5055498a6746-4 Job finished. Resetting idle timer...

Looks like the idle timer should maybe be reset for the internal agent when the job is picked up not when the job has finished?

Thanks for this, it looks like there are still some race conditions we haven't caught. Will dig into it!


Cannot open tau3mu_mixed.pkl

Hi, after downloading tau3mu_mixed.pkl, I came across this error when trying to open it. Specifically, at this line of code,
df = pd.read_pickle(self.raw_dir + '/tau3mu_mixed.pkl'), the following error was reported:
AttributeError: Can't get attribute '_unpickle_block' on <module 'pandas._libs.internals' from '/home/zhaowentao/anaconda3/envs/torch2/lib/python3.8/site-packages/pandas/_libs/internals.cpython-38-x86_64-linux-gnu.so'>
My pandas version is 1.3.5, the same as the one specified in requirements.txt. I also tried to load it directly using pickle.load(), but the same error occured. Since I need to modify the process(self) function to add some attributes to Data object, I have to download raw file and process it by myself instead of using the processed file provided (However, I was able to download the processed file and open it). Can you help me with this error? Many thanks.

Hi @WtaoZhao,
I just tested with pandas 1.4.1, and it works well. Can you upgrade the pandas and try it again?
-siqi


FangCunWuChang.dvmt 3.0.1

Microsoft Reviewers: Open in CodeFlow

This app must be installed with admin privilege
microsoft/winget-cli#970


cannot login from another computer

Expected behavior
Should be able to login from another computer
Actual behavior
For instance, https://busy.org
I can login from one computer, but not with others.
I've already deleted cookies. didn't work.
Steps to reproduce the behavior

just log in from another computer to, for instance, https://busy.org

Are you using steemconnect website or desktop / chrome app? If it's not the website, which version are you using (see in "About" section)?.

It's desktop Version: 0.1.2
It seems 0.1.3 was released two weeks ago, I'll test with it and let you again. Thanks.

Working with 0.1.3!
It'd be great if there is an auto update or update notification. Thanks.


My GPU doesn't support CUDA

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 8.1
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): (I've use this) pip install --upgrade https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-1.12.0-py3-none-any.whl
TensorFlow version: 1.12.0
Python version: 3.8
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory: GeForce GTX 745

When I want to run test code I get error "ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'"
I know that it is caused by lack of CUDA, but my GPU doesn't support it. What can I do with it?
Traceback (most recent call last):
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
    fp, pathname, description = imp.find_module('_pywrap_tensorflow_internal', [dirname(__file__)])
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\imp.py", line 296, in find_module
    raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
    import _pywrap_tensorflow_internal
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:/Users/Ja/PycharmProjects/tf/tf.py", line 10, in <module>
    import tensorflow as tf
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\__init__.py", line 24, in <module>
    from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\__init__.py", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 74, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
    fp, pathname, description = imp.find_module('_pywrap_tensorflow_internal', [dirname(__file__)])
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\imp.py", line 296, in find_module
    raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Users\Ja\AppData\Local\Programs\Python\Python38-32\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
    import _pywrap_tensorflow_internal
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'

Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/errors

@kacpo55,
I recommend you to uninstall older tensorflow and python version and install new tensorflow 1.12 and python. It worked for many users. Some time when you have installed different versions of python and tensorflow, there will be some modules that could affect reinstalling of TF. Follow the official website to install Tensorflow. Let us know if that resolves. Thanks!

@kacpo55,
If your GPU doesn't support CUDA. You can install CPU version of Tensorflow. Thanks!

I thought that I installed CPU version. I fixed it by unistalling python and tensorflow and then installing newer version of tensorflow. Now I'm using tensorflow 2.0.2.
Thanks @gadagashwini


Added background style to all headings containing emphasis tag

What is the context of this PR?

Runner needs to be able to put highlight styling on h1 and h2 headings without adding the "highlight" class.  (as it causes issues for translation)
There is no specific classes on the general template in runner to target, so we would have to style any heading that contained an <em>

How to review

Check any heading containing an <em> is styled as the 'highlight' pattern specifies
Check no other content containing an <em> is styled as the 'highlight' pattern specifies

 Allow headings to use highlight styling without em class


Summarize the content using the current conversation model

Fix bug: #4587
The bug comes from: app/constant.ts
export const SUMMARIZE_MODEL = "gpt-3.5-turbo";
export const GEMINI_SUMMARIZE_MODEL = "gemini-pro";

The problem of writing the summary model to death will result in the failure to summarize when using a non-GPT-3.5-turbo model
I changed it to:
export const UsedModel= `{{model}}`;

export const SUMMARIZE_MODEL = UsedModel;
export const GEMINI_SUMMARIZE_MODEL = UsedModel;

This automatically selects the model used for summarization

错误上传了分支（😭）
一会我再重新提交pr


Add caption and name options to output blocks

I would like to be able to caption and reference program-output and command-output block like literalinclude directives.
As such, this PR is heavily inspired from what is already done for literalinclude.
It adds the :name: option to be able to reference the output block from elsewhere, and the :caption: option to set a caption to the output block.
Thanks in advance for looking at it.

Thanks for this PR! I don’t see any reason not to add this functionality.
This is a great start. The PR will need a few things before it can be merged:

[ ] Thorough tests
[ ] compatible syntax
[ ] No new linter errors
[ ] documentation, plus a note in CHANGES.rst

Let me know if I can assist with any of those things.

Hi!
I have documented the options in the manual and added a note in the CHANGES.rst.
I have also added some tests which required to modify a bit the TestDirective's method assert_output.
The linter detects an error in the src/sphinxcontrib/programoutput/tests/__init__.py for Python3. I did not modify this file, so was this an existing issue ?
I let you review the code and make any modification.
Thanks.

so was this an existing issue ?

Yes, an update to pylint added a new warning. I've taken care of it.
Thanks!


Cow: Watch taxidermys.com

Cow requests the watch of the watch_keyword taxidermys\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

taxidermys\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Encoding is not applied to content added via $message->addPart()

I'm sending a message with HTML and plain text content, and I would like to use 8bit encoding instead of quoted printable, so I do:
$message->setEncoder(Swift_Encoding::get8BitEncoding())
Later on I set the content:
$message->setBody('hello', 'text/html');
$message->addPart('hello', 'text/plain');

The email sent has the HTML part encoded as 8bit but the plain text part is still encoded as quoted printable. If I set the body with the plain text content and the HTML as a part, then only the text part is 8bit encoded.
That means, the encoding set in the message only applies to the body, not to the parts. I would expect it to apply to both of them.
I'm using Swift-5.2.1 from composer.
EDIT: this seems to be a rather old bug: https://github.com/swiftmailer/swiftmailer/issues/69
The problem didn't happen in version 3.3.2, but it happens in version 4 and 5

Closing as a duplicate of #69


Add nginx proxy_max_temp_file_size configuration option

What this PR does / why we need it:
This adds a configmap / annotations option to configure Nginx proxy_max_temp_file_size http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_max_temp_file_size
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

How do these settings normally get tested? Can we let it soak somewhere to see how it does under load?