Error opening Spyder with Miniconda on macOS

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[ ] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
When i launch the command conda run spyder from my conda environment (named devPython) I get an error message and I cannot open Spyder. I've already uninstalled miniconda and reinstalled all the stuff (Python packages, environment, ecc.)
 What do you see instead?
The expected output is to get Spyder open, but instead i get this error message:
Paste Traceback/Error Below (if applicable)

ERROR conda.cli.main_run:execute(32): Subprocess for 'conda run ['spyder']' command failed.  (See above for error)
Traceback (most recent call last):
  File "/Users/mariocatuogno/miniconda/envs/devPython/bin/spyder", line 11, in <module>
    sys.exit(main())
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/app/start.py", line 205, in main
    mainwindow.main()
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/app/mainwindow.py", line 3734, in main
    mainwindow = run_spyder(app, options, args)
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/app/mainwindow.py", line 3590, in run_spyder
    main.setup()
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/app/mainwindow.py", line 977, in setup
    'spyder.plugins.{}'.format(plugin_name))
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/plugins/pylint/__init__.py", line 14, in <module>
    from .plugin import Pylint as PLUGIN_CLASS
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/plugins/pylint/plugin.py", line 29, in <module>
    from spyder.plugins.pylint.confpage import PylintConfigPage
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/plugins/pylint/confpage.py", line 16, in <module>
    from spyder.plugins.pylint.widgets.pylintgui import PylintWidget
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/plugins/pylint/widgets/pylintgui.py", line 37, in <module>
    from spyder.plugins.pylint.utils import get_pylintrc_path
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/spyder/plugins/pylint/utils.py", line 16, in <module>
    import pylint.config
  File "/Users/mariocatuogno/miniconda/envs/devPython/lib/python3.7/site-packages/pylint/config.py", line 54, in <module>
    import toml
ModuleNotFoundError: No module named 'toml'

Versions

Spyder version: 4.1.2
Python version: 3.7.7
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version: macOS Catalina 10.15.4

Dependencies

PASTE DEPENDENCIES HERE

Hi @MarioCatuogno , thanks for reporting. This is an issue with latest pylint package that Anaconda release. We have already requested the fix. In the meantime please install toml manually
Open a terminal and enter
conda install toml
Cheers!


Is there a describe method on DataFrame like Polars?

I was trying to generate a summary on the data frame but could not find any relevant methods like describe or summary which can provide this kind of table on the data which Polars data frame has an implementation.
Describe the solution you'd like
A described the method on the data frame &df.describe().await? should return a new summary dataframe with mean, median, and max values for each column. In more advance case metric name can be provided as vec so that it only compute/statistically estimate tose values for example &df.describe(vec!["min", "max", "25%"]).await?

No, this does not currently exist. It would be an excellent addition though.

polars got method to calc result for describe, does datafusion got this method?

count
null_count
mean
std
min
max
quantile

https://github.com/pola-rs/polars/blob/64abfa409355e876e3774521d8cdcdfbe8ee9ddf/polars/polars-core/src/frame/mod.rs#L2452


kubernetes: whitelist fetch entities

Currently when kubeclient\opeshift_client are updated with additional
entities they are automarically fetched by manageiq (e.g secrets)
that calls all_entities. The purpose of this patch is to prevent this.

fyi @simon3z @abonas

@miq-bot add_label providers/containers refactor

@miq-bot add_label providers/containers, refactor

@miq-bot add_label refactoring

@moolitayer you have to fix the vcr tests (by removing the now unused requests in the recordings).

@moolitayer you have to fix the vcr tests (by removing the now unused requests in the recordings).

done, cassette patch is here

@simon3z Please review

@moolitayer tests are still failing.

@moolitayer tests are still failing.

added the openshift cassette

@simon3z tests pass now. please review.

@simon3z we had two ideas to improve this patch and I could not do any of them.
commenting inline

@moolitayer thanks this looks good

inlined method call.

for hashes doesn't work for me with:
undefined method `+' for #Hash:0x00000001ba6bb0

@moolitayer thanks this looks good

@simon3z  lgty? do we have the label in place?

LGTM :+1: cc @chessbyte ready for merge

@miq-bot add_label LGTM

@miq-bot add_label lgtm

@chessbyte please review

My concerns right now are that

fetch_entities is really only for Container refreshers, but is in a mixin included by all refreshers, and
The code in Kubernetes Refresher and Openshift Refresher are really close to being identical and that Openshift Refresher even has a strict dependency on Kubernetes Refresher to collect all of the entities to refresh (something I guess I missed when this was originally merged).

I would rather see this setup so that the Openshift Refresher inherits from the Kubernetes Refresher .. then the fetch_entities could be just in the Kubernetes Refresher and the Openshift Refresher's dependency on Kubernetes could be handled via inheritance instead of looking up a separate class to gather data.
In general, this looks very much like just a builder pattern.  That could probably be applied here to clean up some of the structural duplication.

@miq-bot remove_label refactloring
@miq-bot add_label bug
This is not refactoring, this is currently a bug since we get (authorization) errors on the openshift side when we try to collect secrets. This patch fixes that issue.
@blomquisg I'd move the refactoring discussion to another PR/issue since I disagree on the fact that inheritance is a good solution.

@miq-bot remove_label refactoring

@simon3z, k ... can you put a refactoring goal on your backlog for this then?  It would be good to eventually see this pulled together in some way.


Documentation updates needed

While working through the workshop, I identified the following issues that need to be updated in the documentation:

Step 2(b) in "Setting up Cloud9 IDE": New EC2 console introduced a necessary change. Attaching an IAM role moved to Actions > Security > Modify IAM role in the new EC2 console. Needs updated instructions and a new screenshot.
Step 1(c) in "Prepare and Download packages": Formatting error in cdk command. Use "cdk --version", not "cdk -version".
Step 1(d) in "Prepare and Download packages": There is no untar operation, but the documentation says to ignore errors in the untar command.
Step 1(e) in "Prepare and Download packages": There is no CodeCommit operation, so the CodeCommit access via http link is either not need or is premature.
Step 6 in "CDK Launch": The step says that you deploy the CDKToolkit to trigger the CloudFormation stack to execute. This isn't strictly true. The CDKToolskit stack is deployed when you run "cdk bootstrap", and it simply deploys an S3 bucket to hold assets related to cdk execution. The "cdk deploy" command actually launches 4 new CloudFormation stacks (starting with "CdkStackALBEksBg"), and it doesn't touch the CDKToolkit stack at all.
Step 1(a) in "Access EKS": The line that reads "Now under Load Balance -> Select Instances Tab" should be changed to "Now under Load Balancing -> Target groups, Select the Monitoring Tab".

Hi @paulramsey, apologize for the late response. I have addressed all your documentation points. Thank you for providing the detail & helping us improve our documentation. I will close this Issue now, however, please feel free to re-open / open a new one if you have any feedback to improve the documentation further.
Appreciate your time and efforts.

Hi @paulramsey, apologize for the late response. I have addressed all your documentation points. Thank you for providing the detail & helping us improve our documentation. I will close this Issue now, however, please feel free to re-open / open a new one if you have any feedback to improve the documentation further.
Appreciate your time and efforts.


added swedish translation

Added Swedish translation.
Pre-launch Checklist

[ ] I have updated CHANGELOG.md with my changes
[x] I have run "dart format ." on the project
[ ] I have added/updated relevant documentation

Hey! It looks like formatting is off. Do you format it using flutter format .?

Hey! It looks like formatting is off. Do you format it using flutter format .?

Hey, very new to this. Nope, I missed that part.. I ran it now updated my branch.


Getting Started Go developers page doesn't say Java services is archived

📚 Docs or Wiki Bug Report
Description
The GettingStartedGoDevelopers docs say that Java will be archived in the future, but AFAICT, all of the services except rulesengine have already been archived, so I think the page should be updated to reflect that.
🔬 Minimal Reproduction
What's the affected URL?**
https://docs.edgexfoundry.org/Ch-GettingStartedDevelopers.html

This reference is specifically in the Java developers documentation.
Instead of updating and maintaining this page, it might be better to just remove it entirely. @jpwhitemn @tsconn23 what do you think? Should we ask the full TSC to weight in on that?

Well there's both the reference in the Java developers page, as well as the normal developers page.

Oh, it's in Ch-GettingStartedGoDevelopers.rst, I see it now


fix(runtime-core): app.provide throws a warning when assigning the same value.

If providing the same value to app.provide, no warning should be thrown.

Perhaps the warning needs to be optimized? I think if the same value is assigned, it should only warn the user that the same value already exists, instead of warning the user about overwriting the old value with a new one.

I don't think this is necessary. Providing the same value twice is pointless and should also be avoided if possible so a warning is appropriate.


Error

Hey the error show no number available smshub and i used http proxy

Hey the error show no number available smshub and i used http proxy

Hi . I think your token is expired

How can make new token in smshub please teach me

How can make new token in smshub please teach me

Your token at braindeepjet.online expired


Use reasonably bigger producer queue size in Pulsar to increase throughput with small messages

cc/ @mgodave

@tsypuk This setting was needed to have higher throughput with small messages. It controls the number of in-flight messages between client and broker (It doesn't affect ordering).


There is no access to FileId::zero()

After LineProgram is created, there is no way to access comp_name's FileId. (There is default_directory() for DirectoryId(0) though)

Got confused in convert logic. It's highly internal value --  closing as invalid.


[SPARK-34382][SQL] Support LATERAL subqueries

What changes were proposed in this pull request?
This PR adds support for lateral subqueries. A lateral subquery is a subquery preceded by the LATERAL keyword in the FROM clause of a query that can reference columns in the preceding FROM items. For example:
SELECT * FROM t1, LATERAL (SELECT * FROM t2 WHERE t1.a = t2.c)

A new subquery expressionLateralSubquery is used to represent a lateral subquery. It is similar to ScalarSubquery but can return multiple rows and columns. A new logical unary node LateralJoin is used to represent a lateral join.
Here is the analyzed plan for the above query:
Project [a, b, c, d]
+- LateralJoin lateral-subquery [a], Inner
   :  +- Project [c, d]
   :     +- Filter (outer(a) = c)
   :        +- Relation [c, d]
   +- Relation [a, b]

Similar to a correlated subquery, a lateral subquery can be viewed as a dependent (nested loop) join where the evaluation of the right subtree depends on the current value of the left subtree.  The same technique to decorrelate a subquery is used to decorrelate a lateral join:
Project [a, b, c, d]
+- LateralJoin lateral-subquery [a && a = c], Inner  // pull up correlated predicates as join conditions
   :  +- Project [c, d]
   :     +- Relation [c, d]
   +- Relation [a, b]

Then the lateral join can be rewritten into a normal join:
Join Inner (a = c)
:- Relation [a, b]
+- Relation [c, d]

Follow-ups:

Similar to rewriting correlated scalar subqueries, rewriting lateral joins is also subject to the COUNT bug (See SPARK-15370 for more details). This is not handled in the current PR as it requires a sizeable amount of refactoring. It will be addressed in a subsequent PR (SPARK-35551).
Currently Spark does use outer query references to resolve star expressions in subqueries. This is not lateral subquery specific and can be handled in a separate PR (SPARK-35618)

Why are the changes needed?
To support an ANSI SQL feature.
Does this PR introduce any user-facing change?
Yes. It allows users to use lateral subqueries in the FROM clause of a query.
How was this patch tested?

Parser test: PlanParserSuite.scala
Analyzer test: ResolveSubquerySuite.scala
Optimizer test: PullupCorrelatedPredicatesSuite.scala
SQL test: join-lateral.sql, postgreSQL/join.sql

Test build #137824 has started for PR 32303 at commit 8f6ea0a.

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

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

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

Test build #137824 has finished for PR 32303 at commit 8f6ea0a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ExpandedStar(star: UnresolvedStar) extends Star with Unevaluable
case class LateralJoin(tpe: JoinType) extends JoinType

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

cc @cloud-fan

cc @maropu @viirya

It would be nice to add a page for the literal join in follow-up PRs.

It would be nice to add a doc page for the literal join in follow-up PRs.

Sounds good. Created SPARK-35208 as a follow up task.

scala> sql("SELECT * FROM (VALUES (1), (2)) tx(a), LATERAL (SELECT a FROM tx) ty(a)").show()
org.apache.spark.sql.AnalysisException: Table or view not found: tx; line 1 pos 62;
'Project [*]
+- 'Join LateralJoin(Inner)
   :- SubqueryAlias tx
   :  +- Project [col1#345 AS a#346]
   :     +- LocalRelation [col1#345]
   +- 'SubqueryAlias ty
      +- 'UnresolvedSubqueryColumnAliases [a]
         +- 'Project ['a]
            +- 'UnresolvedRelation [tx], [], false

How bout the case above? The table resolution couldn't work well.

Test build #137967 has started for PR 32303 at commit 07d764a.

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

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

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

scala> sql("SELECT * FROM (VALUES (1), (2)) tx(a), LATERAL (SELECT a FROM tx) ty(a)").show()
org.apache.spark.sql.AnalysisException: Table or view not found: tx; line 1 pos 62;
'Project [*]
+- 'Join LateralJoin(Inner)
   :- SubqueryAlias tx
   :  +- Project [col1#345 AS a#346]
   :     +- LocalRelation [col1#345]
   +- 'SubqueryAlias ty
      +- 'UnresolvedSubqueryColumnAliases [a]
         +- 'Project ['a]
            +- 'UnresolvedRelation [tx], [], false

How bout the case above? The table resolution couldn't work well.

In this case tx in LATERAL (SELECT a FROM tx) will be resolved as a relation instead of a lateral reference. Postgres also raises an error in this case:
SELECT * FROM (VALUES (1), (2)) tx(a), LATERAL (SELECT a FROM tx) ty(a)
relation "tx" does not exist

Both of the following queries will work:
SELECT * FROM (VALUES (1), (2)) tx(a), LATERAL (SELECT a) ty(a)
SELECT * FROM (VALUES (1), (2)) tx(a), LATERAL (SELECT tx.a) ty(a)

Test build #137967 has finished for PR 32303 at commit 07d764a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #137973 has started for PR 32303 at commit af0c3b0.

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

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

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

Test build #137973 has finished for PR 32303 at commit af0c3b0.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #138059 has started for PR 32303 at commit 2e87e18.

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

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

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

Test build #138059 has finished for PR 32303 at commit 2e87e18.

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

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

@maropu @viirya @cloud-fan Thanks for the review! I've addressed the comments and activated some Postgres SQL tests for lateral subqueries. The results also match Postgres' results.

Test build #138764 has started for PR 32303 at commit fe2f941.

Test build #138764 has finished for PR 32303 at commit fe2f941.

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

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

Test build #138817 has started for PR 32303 at commit 8e6cab3.

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

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

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

Test build #138817 has finished for PR 32303 at commit 8e6cab3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #139250 has started for PR 32303 at commit 72facb0.

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

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

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

Test build #139250 has finished for PR 32303 at commit 72facb0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LateralSubquery(
case class LateralJoin(

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

Test build #139269 has started for PR 32303 at commit b83c571.

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

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

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

Test build #139269 has finished for PR 32303 at commit b83c571.

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

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

@maropu @cloud-fan @viirya
I updated the logical plan structure to handle a few cases I found during the test that do not work with the original plan representation. Originally, we directly use the logical Join node with a new join type LateralJoin. This structure can't handle the case when deduping relations, for instance:
'Join
:- LocalRelation [a, b]
+- Join LateralJoin(Inner)
   :- LocalRelation [a, b]  <--- after DeduplicateRelation: LocalRelation ['a, 'b]
   +- Project [outer(a) + outer(b)]  <--- but outer references won't be updated
      +- OneRowRelation

DeduplicateRelation rule will return a new instance of the LocalRelation[a, b], but the current transformUpWithNewOutput won't be able to update the existing outer references in the right subtree. Also, the resolution logic has a lot of overlaps with ResolveSubquery. The new logic unifies the analysis logic for lateral subqueries and existing subqueries. It adds a new unary node LateralJoin and a new subquery expression LateralSubquery to represent a lateral subquery. I've updated the PR description.
Also, I removed the logic to resolve star expressions in subqueries. It is not lateral subquery specific and I've created a new JIRA ticket: SPARK-35618.

Test build #139452 has started for PR 32303 at commit d646720.

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

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

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

Test build #139452 has finished for PR 32303 at commit d646720.

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

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

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44035/

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

Test build #139528 has started for PR 32303 at commit 8f19ab7.

Test build #139535 has started for PR 32303 at commit f00f210.

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

Test build #139540 has started for PR 32303 at commit eb46d13.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44059/

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

Test build #139540 has finished for PR 32303 at commit eb46d13.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #139543 has started for PR 32303 at commit 08385f4.

Test build #139543 has finished for PR 32303 at commit 08385f4.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

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

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

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

Test build #139546 has started for PR 32303 at commit 1b6d8f3.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44064/

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

Test build #139528 has finished for PR 32303 at commit 8f19ab7.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

retest this please

Test build #139562 has started for PR 32303 at commit 1b6d8f3.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44068/

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

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

Test build #139535 has finished for PR 32303 at commit f00f210.

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

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

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

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

Test build #139546 has finished for PR 32303 at commit 1b6d8f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #139562 has finished for PR 32303 at commit 1b6d8f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44089/

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

Test build #139577 has started for PR 32303 at commit 01fa70e.

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

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

The GA failure is in Linters, licenses, dependencies and documentation generation, which is unrelated to this PR. I'm merging it to master, thanks!

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

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


copr: Add vectorize day_of_week

PCP #5751
Signed-off-by: Poytr1<EMAIL_ADDRESS>What have you changed?
Vectorize day_of_week
What is the type of the changes?

Improvement (a change which is an improvement to an existing feature)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?

No
Does this PR affect tidb-ansible?

No

@sre-bot /run-integration-copr-test copr-test=pr/119

/test

/approve

/merge

/run-all-tests

/merge

/merge

/run-all-tests

It looks weird that this PR makes all tests fail. Let me investigate it...

@Poytr1 It seems that you hide the head ref of this PR. So this PR is not synced with the latest master. Could you update your branch so the test can pass?

Hi @sticnarf , sry for the inconvenience. The PR has been opened for a long time and I forgot it and wrongly delete my forked repository...
I opened a new PR for this just now: https://github.com/tikv/tikv/pull/6645. So feel free to close this one, and move on with that PR. Thanks!
Also for another two PRs: https://github.com/tikv/tikv/pull/6385 and https://github.com/tikv/tikv/pull/6386, I will do the same thing, close them and open new twos.

@Poytr1 Really sorry for the late response before.


add st stat

add st thread stat in api summaries

Codecov Report

Merging #2772 (ea2f952) into 4.0release (3eb8fa2) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           4.0release    #2772      +/-   ##
==============================================
- Coverage       60.32%   60.31%   -0.02%
==============================================
  Files             121      121
  Lines           50970    50979       +9
==============================================
  Hits            30747    30747
- Misses          20223    20232       +9

Impacted Files
Coverage Δ

trunk/src/app/srs_app_utility.cpp
24.92% <0.00%> (-0.26%)
:arrow_down:

trunk/src/protocol/srs_service_st.cpp
77.88% <0.00%> (-0.51%)
:arrow_down:

trunk/src/protocol/srs_service_st.hpp
0.00% <ø> (ø)

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 3eb8fa2...ea2f952. Read the comment docs.


boards: arm: add PAN1783A-PA evaluation board

The PAN1783A-PA evaluation board is a development tool for the nRF5340 from Nordic Semiconductor and the third evaluation board variant for the PAN1783 Module. The power amplifier (PA) version includes FEM support.

@anangl & @nordicjm
can we merge after last changes? :-)

@pideu-sj needs rebase

@pideu-sj thanks for stepping up as a maintainer btw! Feel free to claim your Zephyr Maintainer badge here: https://forms.gle/oCw9iAPLhUsHTapc8 :)


vendor/github.com/robfig/cron/logger.go:62:9: undefined: strings.Builder

vendor/github.com/robfig/cron/logger.go:62:9: undefined: strings.Builder
Why I'm getting this error when installing my go-app using dockerfile

It seems you are not using the right version of go.
strings.Builder was introduced in 1.10 https://golang.org/pkg/strings/#Builder

This library requires Go 1.11 at least for Modules support. You could probably use an older version (v1), but I'm not under the impression that there's a major reason to run such old versions of Go.


Create Google Cloud Run Button on Readme

Google Cloud Run Button makes it easy to deploy the current Master branch to GCP with a click of a button for those users that have an account. This may be an easier way for "getting started" with the project.
https://cloud.google.com/blog/products/serverless/introducing-cloud-run-button-click-to-deploy-your-git-repos-to-google-cloud

I just resolved this issue, is it possible to close it?

Yep, thanks again!


add handling each_serializer when expose a collection of object.

For now in the controller if you run
expose User.page(params[:page]||1), serializer: UserSerializer
It will give you an error, if you add :each_serializer it doesn't work.
so add the option when :each_serializer was used, that means user want to regards the object as a collection.

On this issue - i'm seeing serializers not working as well — am i alone on this??
NoMethodError - undefined method `read_attribute_for_serialization' for #<PortIn::ActiveRecord_AssociationRelation:0x007ff819c7af10>:
  activerecord (4.1.9) lib/active_record/relation/delegation.rb:136:in `method_missing'
  activerecord (4.1.9) lib/active_record/relation/delegation.rb:99:in `method_missing'
  active_model_serializers (0.9.0) lib/active_model/serializer.rb:101:in `block (2 levels) in attributes'
  active_model_serializers (0.9.0) lib/active_model/serializer.rb:155:in `block in attributes'
  active_model_serializers (0.9.0) lib/active_model/serializer.rb:154:in `attributes'
  active_model_serializers (0.9.0) lib/active_model/serializer.rb:260:in `serializable_object'
  rocket_pants (1.10.0) lib/rocket_pants/controller/respondable.rb:10:in `serializable_hash'
  rocket_pants (1.10.0) lib/rocket_pants/controller/respondable.rb:71:in `normalise_object'
  rocket_pants (1.10.0) lib/rocket_pants/controller/respondable.rb:92:in `normalise_object'
  rocket_pants (1.10.0) lib/rocket_pants/controller/respondable.rb:132:in `respond_with_object_and_type'
  rocket_pants (1.10.0) lib/rocket_pants/controller/respondable.rb:143:in `collection'
  rocket_pants (1.10.0) lib/rocket_pants/controller/respondable.rb:157:in `exposes'

For now, fixed with:
expose ActiveModel::ArraySerializer.new(@people, each_serializer: PersonSerializer)

You are not alone, @mbhnyc -- and the workaround precludes showing the pagination in the return data:
expose @people.paginate(:page => params[:page])

...
"count": 2,
"pagination": {
    "previous": null,
    "next": null,
    "current": 1,
    "per_page": 30,
    "count": 2,
    "pages": 1
}
...

Hey guys - This isn't forgotten, I need to look back into it again but last time I worked on it I hit similar issues.

fwiw, the easier solution for the moment is:
expose @people, serializer: ActiveModel::ArraySerializer, each_serializer: PersonSerializer

Which should handle pagination etc, child serializers and more. I'm looking at fixing this properly in a build (1.12 likely, if not that 1.13 in the near future) - but hit a few blockers last time I looked into it hence why it's not done yet.

Can you guys take a look at the change on master? I've tested in a few places, and it appears to work - will release in 1.12 shortly (and add credit @hlxwell) - Sorry it's taken so dang long for me to get to this.


Set Roku name to the device name instead of the serial number

Description:
This makes ugly entity IDs like media_player.roku_1gm351013183 into pretty ones using the device name, like media_player.robbies_roku

Should be noted as a breaking change.


Add how to format source code with maven to documentation

:loudspeaker: Type of change

[ ] Bugfix
[ ] New feature
[x] Enhancement
[ ] Refactoring

:scroll: Description
Adding how to format source with maven to readme
:bulb: Motivation and Context
Every time i want to contribute i am struggling with how to format the source code without changing my Intellij settings
:green_heart: How did you test it?
i read it
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[ ] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

@tekener our readme is partially generated from Spring Cloud docs (look at the top of readme file). If you believe this change should be added to other Spring Cloud projects, consider creating a PR to: https://github.com/spring-cloud/spring-cloud-build/blob/main/docs/src/main/asciidoc/contributing.adoc
I am strongly considering migrating away from Spring Javaformat to Spotless

Hi, didn't see that. Horrible documentation 😂 Anyway it was worth a try.


Added branch to git clone execute

Expected by documentation that when the branch is set this wil be checkout

http://deployer.in/stages.html
http://deployer.in/tasks.html#using-input-options

Done.


Update and rename existing 2411.0 TSG to accommodate for the New 2411.1 TSG with the same portal symptom

Rename includes Triggering-deployment-settings-validation-call-results-in-OperationTimeout.md to Triggering-deployment-settings-validation-call-results-in-OperationTimeout-2411-0.md
Article changes include reference to the new issue/article.

PR now includes rename and update to the existing 2411.0 TSG with the same portal symptom as the newly created 2411.1 TSG, as well as the creation of the new 2411.1 TSG.


chore(STONEINTG-836): integration-service to konflux-ci org

Integration-service has been migrated to konflux-ci org
Description
Updating integration-service URL, to avoid pain in future when a version bump will be needed
Issue ticket number and link
Type of change

[ ] 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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/lgtm
/approve


Strip certain variations in a variable font

A full Noto variable font that has 4 masters in weight variation and 2 masters in width variation can be large.
It'll be great if fontmake supports striping certain variations, e.g., the condensed width variation, and/or a master in the weight variation to reduce the size of a variable font.
@jamesgk @brawer @behdad

This definitely will be possible down the road (by cropping variation space; not by discarding listed masters), but IMO this is rather low priority.  Definitely not this quarter..

Duplicate of https://github.com/googlei18n/fontmake/issues/173


Merged declaration of construct signature does not work for function

Bug Report

🔎 Search Terms
typescript declaration merging function

Please see Declaration Merging
🕗 Version & Regression Information
$ yarn tsc --version
Version 4.6.3

This is the behavior in every version I tried, and I reviewed the FAQ for entries about declaration merging

⏯ Playground Link

Playground link with relevant code
💻 Code

// Function class example
interface MyFunctionClass {
    new(): MyFunctionClass; // let's assume here it has a constructor
    myMethod(): void;
}

function MyFunctionClass(this: MyFunctionClass) {
    this.myMethod = Number;
}

const myClassInstance = new MyFunctionClass();
// 'new' expression, whose target lacks a construct signature, implicitly has an 'any' type

🙁 Actual behavior
displays error  'new' expression, whose target lacks a construct signature, implicitly has an 'any' type
🙂 Expected behavior
Since declaration merging should work because it's not the case in Disallowed Merges section.
I should be able successfully create my function class

I don’t see any declaration merging happening here.  Function statements do not  bring type names into scope the way class statements do.  But maybe I’m just confused because the example is so strange.  What kind of class constructor produces instances which are also class constructors? Like, what specifically are you trying to accomplish here?  I think you need to spell it out because it’s not obvious.

@jcalz exactly, I believe the declaration of the interface should be merged with the function declaration of the same name. Otherwise, there is no other way to create a function class as it is supported by javascript itself.

Basically, I just need to make work only this part
function MyFunctionClass(this: MyFunctionClass) {
    this.myMethod = Number;
}

const myClassInstance = new MyFunctionClass();

But looks like typescript does not infer the inner methods of the function, so I need to define them through an interface

@jcalz They’re expecting the function to act as the constructor for the interface.

@3axap4eHko That new() signature won’t work there - that means that, given a MyFunctionClass instance, you can call it with new.

@fatcerberus but in js, it is working as a constructor. A class even transpires to a function if you use something like es5 settings.
class A {}

turns to
var A = /** @class */ (function () {
    function A() {
    }
    return A;
}());

What is the solution to allow the function to act as a constructor?

Why not... an actual class declaration, if you don't need it to be callable?
declare class MyFunctionClass {
  constructor();
  myMethod(): void;
}

function MyFunctionClass(this: MyFunctionClass) {
  this.myMethod = Number;
}

const myClassInstance = new MyFunctionClass();

[ ] CLOSE
Duplicate of #48249

Okay so then there's no bug here, right?  TS is working as intended.  It's certainly interesting to look at how to get a function statement to act as a constructor, but that's a question or maybe a feature request (if declare class is not acceptable for some reason).  So maybe @3axap4eHko should close this unless there's some evidence of a compiler bug here?

@jcalz there is a bug, just take a look. Merged declaration works with function and declare class, it also works with interface and class, but it does not work for interfaceadfunction`

@3axap4eHko Your code is invalid semantic. A constructor is fundamentally different from an instance, so you may want to update your example so as not to confuse others and hide away the real bug. For example, this is a better example:
interface MyFunctionClass {
  new (): MyFunctionClassInstance;
}
function MyFunctionClass(this: MyFunctionClassInstance) {
  this.myMethod = Number;
}

interface MyFunctionClassInstance {
  myMethod(): void;
}

const a = new MyFunctionClass(); // 'new' expression, whose target lacks a construct signature,

Interface declares a type. Function declares a value. There's no overlap.

@MartinJohns
function buildLabel(name: string): string {
  return buildLabel.prefix + name + buildLabel.suffix;
}
namespace buildLabel {
  export let suffix = "";
  export let prefix = "Hello, ";
}

function is a value and namespace is a type, so why does it work here?

@MartinJohns thank you! Now I get it. function does not declare a type, but a value. So this shouldn't work
function A() {}
const a: A = () => {};

But how does it work, if Function is a function but it can be used as a type and it has construct signature?
const a: Function = () => {};
const b = new Function();

@jcalz you are right it's not a bug, but just requires a lot of effort. So to make it work I need to define it like this
interface A {
    (): void;
}

function A() {
    const a = () => 'test';
    a.myMethod = Number;
    return a;
}

declare class A {
    myMethod(value?: any): void;
}

const a = new A();
console.log(a(), a.myMethod(123)); // 'test' 123

Thank you so much, gentlemen, it was a pleasure to talk with you!


Improving resolution and usability of controlled delays in kernel APIs

This issue outlines the current approach to controlled delays in Zephyr, identifies some weaknesses and functional gaps, and serves as a point of discussion of goals and requirements for changes to address those weaknesses.
Existing Approach
Several kernel system APIs allow an application to specify a delay before some operation is initiated or terminated.  These APIs include (delay parameters are in bold type):

k_timer_start(timer, duration, period)
k_timer_remaining_get(timer) => remaining (nb: unsigned)
k_queue_getqueue, timeout) (underlying k_fifo_get, k_lifo_get)
k_futex_wait(futex, expected, timeout)
k_stack_pop(stack, data, timeout)
k_delayed_work_submit_to_queue(queue, work, delay)
k_delayed_work_remaining_get(work) => remaining (nb: signed)
k_mutex_lock(mutex, timeout)
k_sem_take(sem, timeout)
k_{msgq,mbox,pipe}_[block_]{put,get}(store, data, timeout)
k_mem_{slab,pool}_alloc(slab, mem, timeout)
k_poll(events, num, timeout)
k_sleep(ms)
k_usleep(us)
k_busy_wait(us)
k_thread_deadline_set(thread, deadline)
k_uptime_get() and k_uptime_delta(&ms)

In current Zephyr most controlled delays are specified as a signed 32-bit integer counting milliseconds, with helper macros like K_MINUTES(d) to convert from more coarse-grained measures.  Exceptions are:

k_usleep and k_busywait which operate in microseconds;
k_thread_deadline_set which operates in cycles of the hardware clock;
k_uptime_get which operates in s64_t milliseconds clamped to tick increments.

Internally most delays are implemented through struct _timeout which operates on ticks as defined by SYS_CLOCK_TICKS_PER_SEC.  The requested delay is converted to the smallest span of ticks that is not less than the requested delay, except that a duration of zero may be converted to a single tick in some cases.  An exception is k_busy_wait under the influence of ARCH_HAS_CUSTOM_BUSY_WAIT, currently used in-tree only by Nordic.
Functional Gaps
For all APIs but specifically k_timer interrupts between the point the application supplies the relative delay and the point the timer infrastructure inserts it into a processing queue introduces complexity in precise delay maintenance.  To reduce these complexities it is desirable in some cases to specify delays as deadlines rather than relative offsets (#2811).
Use of milliseconds was tolerable as the tick duration has historically been 10 ms.  With the upcoming merge of #16782 decreasing tick duration to 100 us finer grained specification will soon be needed for most if not all APIs.  Arguments have been made to go as fine as nanoseconds (#6498).
Base Requirements and Questions
In a recent telecon @andyross proposed addressing these gaps by changing the way delays are specified, from signed 32-bit millisecond counts to another representation.
The following are positions and questions which I (@pabigot) have summarized and extended based on previous related discussions and experience.  All are open for debate.

Existing code like k_sem_take(&sem, K_MSEC(5))--code that uses helper macros to translate delay durations to a timeout value--must be unaffected by any underlying API changes.
It must be possible to specify timer delays as either relative or absolute delays.
It is TBD whether other delays such as k_poll or k_sleep should allow for absolute deadlines.
It is desirable for the application to be able to retrieve the absolute deadline assigned by the infrastructure when given a relative delay.  Note that returning time remaining does not satisfy this desire.
Precise handling of the order of completion for delays with the same deadline should be defined.  The current implementation is inconsistent when timeouts are scheduled during callbacks or with deadlines that have passed (#12332).  The problem will be exacerbated with the ability to schedule at absolute deadlines (which may have passed).
We should revisit the semantics of passing a relative deadline that has a non-positive value: in some cases converting it to an absolute deadline in the past may be preferable to the existing practice of treating it the same as zero in all cases.
We need to determine the finest resolution that must be supported. Microseconds would handle many cases, but going to nanoseconds may be worth doing for future-proofing and because it has been requested in the past.
We need to determine the maximum relative delay that must be expressible.  With s32_t milliseconds that's currently 2147483.647 s (about 3.5 weeks).  As resolution is increased this delay is reduced significantly unless larger data types are used.
We need to review the clock domain used to control these delays, in particular its resolution and span.  Currently this is the 64-bit system tick clock.  At this time the only public API to read this clock is k_uptime_get* which converts its scale to milliseconds.  New API should be added to access the full precision for use in maintaining absolute deadlines.
We might consider using POSIX clock_gettime() as a model for reading clocks, and whether there's value in specifying delays as being expressed for a specific clock.

cc @andyross @nashif @andrewboie @MaureenHelm @carlescufi @galak @pizi-nordic

One more thing to consider: We should specify clock domains for k_busy_wait() and k_cycle_get32(). and other k_* API. Currently we assume that all are clocked from the same source, but for at least Nordic, this is not true.

Thanks Peter for the detailed summary!
I think the requirements contain all the things which I would need for an IoT application with precise TDMA scheme. I don't have a deep understanding of Zephyr so here are just a few comments from my side:

Resolution - I cannot see yet at the moment the use of nanoseconds resolution. When devices need to synchronize at a such level it would require probably to use a different approach. Compensation techniques for clock drift, temperature, vibration etc. would need to take in account. I am not sure if the overhead and efforts would worth the effort. It would be also difficult to evaluate and maintain that across  platforms.
Absolute time in the past - I think the user should take care of not setting the absolute time in the past.
Delay range - For an IoT application with micro-seconds TDMA a practical update rate would be maximum in tens of minutes range. A longer period is difficult to achieve taking in account the hardware clock sources used on those devices, temperature compensation, etc. So using s32_t or u32_t is probably still fine for most of applications. For longer delays the accuracy of micro-seconds is probably difficult to achieve on medium/low cost devices. For devices at higher cost or where power consumption is not a constrain there are more options to achieve timing accuracy and that can be done outside of the kernel.

@leapslabs Thanks for your comments.  Although synchronization is important, the primary use of this feature is internal to a single device.  System cycle clocks are always above 1 MHz so nanoseconds are necessary to measure deltas.  There are also use cases for setting alarms that will fire months in the future (e.g. preparing for a time zone offset or TAI-UTC delta change).
My tests on boards from four different vendors show the system clock is generally accurate to about 25 ppm, which aggregates 1 ms error in 40 s runtime, or 1 s in about eleven hours, which is consistent with your 10s-of-minutes estimate to coordinate time between devices at the application level, e.g. to synchronize scheduled operations like turning lights on or off.

Existing code like k_sleep(K_MSEC(5))--code that uses helper macros to translate delay durations to a known unit--must be unaffected by any underlying API changes.

It must be possible to specify timer delays as either relative or absolute delays.

It is TBD whether other delays such as k_poll or k_sleep should allow for absolute deadlines.

It is desirable for the application to be able to retrieve the absolute deadline assigned by the infrastructure when given a relative delay.  Note that returning time remaining does not satisfy this desire.

I like both the idea of specifying absolute deadlines as well as fetching deadlines from any kind of kernel API. Looking to @andyross PR the following idea popped in my mind:
 /* Relative */
k_delayed_wrok_submit(..., K_MSEC(10));

/* Absolute */
k_delayed_wrok_submit(..., K_ABS(K_MSEC(10)));

/* Full controll */
struct k_timeout tmo;
k_timeout_set(&tmo, K_MSEC(10)); /* Relative */
k_delayed_wrok_submit(..., K_TMO(&tmo)));
x = k_timeout_remaining_get(&tmo);
x = k_timeout_absolute_get(&tmo);

Question if this idea is really usable is open, but IMHO this might be a step closer to fulfill @pabigot requirements. Moreover, if we are going to change kernel API, there is no better moment than the upcoming Zephyr 2.0 release. Even if not all new features will be available, we might start familiarize users with new API.

Precise handling of the order of completion for delays with the same deadline should be defined.  The current implementation is inconsistent when timeouts are scheduled during callbacks or with deadlines that have passed (#12332).  The problem will be exacerbated with the ability to schedule at absolute deadlines (which may have passed).

This needs discussion. We have to set clear boundaries what will be interpreted as a past.

We should revisit the semantics of passing a relative deadline that has a non-positive value: in some cases converting it to an absolute deadline in the past may be preferable to the existing practice of treating it the same as zero in all cases.

IMHO we should not allow for negative deltas from now. If the user would use "schedule in past" approach we should force him to use absolute timeouts in the API.

We need to determine the finest resolution that must be supported. Microseconds would handle many cases, but going to nanoseconds may be worth doing for future-proofing and because it has been requested in the past.

We need to determine the maximum relative delay that must be expressible.  With s32_t milliseconds that's currently 2147483.647 s (about 3.5 weeks).  As resolution is increased this delay is reduced significantly unless larger data types are used.

That is hard part. I can see the same device needing sub-us precision (for example to implement a radio protocol) and long timeouts (for example run self-check of the controlled machinery each 3 months, remind used about service once per year...).

I can see the same device needing sub-us precision (for example to implement a radio protocol) and long timeouts

long timeouts can always be achieved in application in fragments so i'm not that worried about that. Regarding sub-us if we are talking about kernel infrastructure then if api's are using ticks (and macros for ms2ticks, us2ticks conversion) then nanoseconds are not a problem if nanoseconds-to-ticks macro is added. For lower frequencies that will of course make no sense.

@nordic-krch: You reminded me about one important problem:
The ms2tick and tick2ms conversion is not symmetric (tick2ms(ms2tick(x)) != x) whch causes a lot of troubles in the tests as we have to take under account conversions made in the kernel.
IMHO the Zephyr user will face similar problems, so we should at least consider making such conversion symmetric.

The ms2tick and tick2ms conversion is not symmetric (tick2ms(ms2tick(x)) != x)

Conversion between clock domains is not necessarily both injective (one-to-one) and surjective[https://en.wikipedia.org/wiki/Surjective_function] (onto), which is required to create a total inverse function.  I don't think this expectation can be satisfied, especially these functions don't specify the direction of rounding, and if they both round up the inversion composition might be a monotonically increasing function.

Conversion between clock domains is not necessarily both injective (one-to-one) and surjective (onto), which is required to create a total inverse function.
I don't think this expectation can be satisfied, especially these functions don't specify the direction of rounding, and if they both round up the composition might be a monotonically increasing function.

Ahhh, I missing my math courses :). But you are right. We are working in finite field and we cannot avoid rounding, so there will be no total inversion.
However at the moment, the ms2tick rounds up while tick2ms rounds down, which results in ms2tick(tick2ms(ms2tick(x))) != ms2tick(x). Do you think that this could be fixed?

However at the moment, the ms2tick rounds up while tick2ms rounds down, which results in ms2tick(tick2ms(ms2tick(x))) != ms2tick(x). Do you think that this could be fixed?

Technically, yes; without changing behavior, no.  For the purposes of this PR what I want is something that in its fundamental form could be:
/** Convert a duration from one clock domain to another in which the
 * result duration will be the smallest representable duration that is
 * not shorter than the source duration. */
duration_type clock_duration_convert_upper(duration_type from,
                                        clock_domain_type from_domain,
                                        clock_domain_type to_domain);
/** Convert a duration from one clock domain to another in which the
 * result duration will be the largest representable duration that is
 * not longer than the source. */
duration_type clock_duration_convert_lower(duration_type from,
                                        clock_domain_type from_domain,
                                        clock_domain_type to_domain);

But we're bikeshedding solutions; the intent here is to discuss requirements.  So the requirement the above satisfies is the ability to convert durations between clock domains while controlling the rounding direction.

So the requirement the above satisfies is the ability to convert durations between clock domains while controlling the rounding direction.

And adding this to the list was my goal. Thank you.

We have to use github for design discussions as there isn't anything else available (slack ruled out by TSC), but its single-threaded nature is really inconvenient. So in a couple days what I'd like to do is take into account all comments received so far and post a new version of the Base Requirements and Questions section, including links to relevant comments. Then hide the preceding comments so people can see what the latest consensus looks like without getting bogged down in the supporting discussion.
It'll be ugly.  I don't have a better solution.

Experience in #17155 shows another point of discussion:  Threads, which are initialized at both compile-time and runtime, include an init_delay attribute which is currently s32_t in memory.  Threads need to be constructed by k_thread_create() at run time, and K_THREAD_DEFINE() at compile time.  Encoded timeouts as suggested in that PR cannot be created at compile-time, while using integer milliseconds at runtime would be inconsistent with other timeout parameters.
It may be necessary to make an exception to use milliseconds for k_thread delays as well.

It was discussed a while back that that argument to k_thread_create() is probably not a good idea to have in the API and that a better scheme would be to simply have a "initialize but do not start" flag, allowing the user to do it at an appropriate time via whatever mechanism she likes.

Just wanted to point out that given the documentation of k_thread_start one would believe that K_THREAD_DEFINE(..., K_FOREVER); would work; which as pointed out previously it does not.
But the type int32_t of init_delay leads one to believe that K_THREAD_DEFINE(..., K_TICKS_FOREVER); might work.
But the internal thread struct does not account for CONFIG_TIMEOUT_64BIT, which may result in trying to fit 64-bits of ticks into the 32-bits delay.
It looks like the current way of starting a thread yourself is creating a stack using K_STACK_DEFINE and a local thread struct k_thread and then using the k_create_thread API.

@cfriedt @nordic-krch One more rather old clock-related ticket which now feels more like an RFC than an enhancement request.
@nashif RFC tag + backlock?
Maybe it would be adequate to collect the remaining open RFCs/Enhancement requests in one RFC (I'd propose #40099 as it already is a meta RFC and has the best link collection AFAICS). For someone like trying to understand for the first time what proposals are being made, this would be very handy. Think this would be a good time as the RFC API has just been introduced and @cfriedt is doing all that POSIX work which is related.
Especially in the clock/timing area the number of open stale proposals, abandoned PRs, etc. is really impressive. ;-)

@cfriedt @nordic-krch One more rather old clock-related ticket which now feels more like an RFC than an enhancement request.
@nashif RFC tag + backlog?
Maybe it would be adequate to collect the remaining open RFCs/Enhancement requests in one RFC (I'd propose #40099 as it already is a meta RFC and has the best link collection AFAICS). For someone like trying to understand for the first time what proposals are being made, this would be very handy. Think this would be a good time as the RFC API has just been introduced and @cfriedt is doing all that POSIX work which is related.
Especially in the clock/timing area the number of open stale proposals, abandoned PRs, etc. is really impressive. ;-)

It's being pulled in to the LTSv3 POSIX roadmap / RFC, which does include a lot of non-posix work, ironically.

Pretty sure the subsystem rewrite which this was opened to track and evangelize got abandoned.  Let's close it as stale; certainly there's always going to be room for discussing improvements to core subsystems, but this one seems to have run its course.  We can always reference it later.


New icon: Ed

[x] I have carefully read and followed CONTRIBUTING document.

URL of the site: https://edstem.org/

Proof of the Aegis-compatible 2FA:

Logo / icon info: Adapted from logo on login screen, selector img.start-ed-icon

Background color info: The background is sampled from the middle of the gradient on the original icon.

Proof of the Aegis-compatible 2FA: image

Proof is not good enough, as stated on the issue form:

Documentation link or screenshot should clearly mention that 2FA is (T)OTP / HOTP or any mobile 2FA app (eg. Google Authenticator, Microsoft Authenticator, LastPass Authenticator etc.) or show section of the 2FA setup page with (censored) OTP 2FA QR code image. Otherwise we cannot be sure if 2FA actually is compatible for Aegis.

Please provide screenshot or documentation link that resolves this issue.

Haha, I was hoping I wouldn't have to go through the process of re-enrolling.
Here's a screenshot of the actual 2fa modal (not the original qr code):

Closed as stale.


Does is work for Silvertripe 4.2?

@Lukin-zz no, this does not yet support SilverStripe 4

Thanks for the question; it's been answered so I'll close the issue.


Qwen2.5-0.5B-Instruct quantization with gptq error

xft version：1.8.2
lscpu：
Architecture:             x86_64
CPU op-mode(s):         32-bit, 64-bit
Address sizes:          52 bits physical, 48 bits virtual
Byte Order:             Little Endian
CPU(s):                   16
On-line CPU(s) list:    0-15
Vendor ID:                GenuineIntel
Model name:             INTEL(R) XEON(R) PLATINUM 8576C
CPU family:           6
Model:                207
Thread(s) per core:   2
Core(s) per socket:   8
Socket(s):            1
Stepping:             2
BogoMIPS:             5000.00
Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1
gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x
2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault ssbd ib
rs ibpb ibrs_enhanced fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f avx512dq rdseed adx smap avx512ifma clfl
ushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves avx_vnni avx512_bf16 wbnoinvd arat avx512vb
mi umip waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq cldemote movdiri movdir64b
enqcmd fsrm serialize tsxldtrk amx_bf16 avx512_fp16 amx_tile amx_int8 arch_capabilities
Virtualization features:
Hypervisor vendor:      KVM
Virtualization type:    full
Caches (sum of all):
L1d:                    384 KiB (8 instances)
L1i:                    256 KiB (8 instances)
L2:                     16 MiB (8 instances)
L3:                     280 MiB (1 instance)
NUMA:
NUMA node(s):           1
NUMA node0 CPU(s):      0-15
Vulnerabilities:
Gather data sampling:   Not affected
Itlb multihit:          Not affected
L1tf:                   Not affected
Mds:                    Not affected
Meltdown:               Not affected
Mmio stale data:        Unknown: No mitigations
Reg file data sampling: Not affected
Retbleed:               Not affected
Spec rstack overflow:   Not affected
Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2:             Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI SW loop, KVM SW loop
Srbds:                  Not affected
Tsx async abort:        Not affected
basic_usage_wikitext2.py：
pretrained_model_dir = "/data/models/Qwen2.5-0.5B-Instruct-AWQ"
quantized_model_dir = "/data/models/Qwen2.5-0.5B-Instruct-GPTQ"
root@fbbe4c067b4e:~/xFasterTransformer/3rdparty/AutoGPTQ/examples/quantization# python basic_usage_wikitext2.py
/root/xFasterTransformer/3rdparty/AutoGPTQ/auto_gptq/nn_modules/triton_utils/kernels.py:411: FutureWarning: torch.cuda.amp.custom_fwd(args...) is deprecated. Please use torch.amp.custom_fwd(args..., device_type='cuda') instead.
def forward(ctx, input, qweight, scales, qzeros, g_idx, bits, maxq):
/root/xFasterTransformer/3rdparty/AutoGPTQ/auto_gptq/nn_modules/triton_utils/kernels.py:419: FutureWarning: torch.cuda.amp.custom_bwd(args...) is deprecated. Please use torch.amp.custom_bwd(args..., device_type='cuda') instead.
def backward(ctx, grad_output):
/root/xFasterTransformer/3rdparty/AutoGPTQ/auto_gptq/nn_modules/triton_utils/kernels.py:461: FutureWarning: torch.cuda.amp.custom_fwd(args...) is deprecated. Please use torch.amp.custom_fwd(args..., device_type='cuda') instead.
@custom_fwd(cast_inputs=torch.float16)
CUDA extension not installed.
CUDA extension not installed.
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Token indices sequence length is longer than the specified maximum sequence length for this model (2518423 > 131072). Running this sequence through the model will result in indexing errors
Traceback (most recent call last):
File "basic_usage_wikitext2.py", line 176, in
main()
File "basic_usage_wikitext2.py", line 149, in main
model = AutoGPTQForCausalLM.from_pretrained(pretrained_model_dir, quantize_config)
File "/root/xFasterTransformer/3rdparty/AutoGPTQ/auto_gptq/modeling/auto.py", line 86, in from_pretrained
return GPTQ_CAUSAL_LM_MODEL_MAP[model_type].from_pretrained(
File "/root/xFasterTransformer/3rdparty/AutoGPTQ/auto_gptq/modeling/_base.py", line 604, in from_pretrained
raise EnvironmentError("Load pretrained model to do quantization requires CUDA available.")
OSError: Load pretrained model to do quantization requires CUDA available.

Hi @wcollin thanks for your test.
AutoGPTQ is the 3rd party code for xFT, so xFT only works on load the quantized weights and inference on CPU.
From the error message, your AutoGPTQ installed is CUDA-based. You might need to re-install it by building from source with BUILD_CUDA_EXT=0 to enable CPU.
Several months ago, I already send the CPU pull request to AutoGPTQ. But seems they are not interested on it, the PR is not merged.
You can refer it to check how to quantize LLM on CPU. Majorly comments out the cuda API related code.


Typo in a table: Service Tiers

Hi,
I think there's a small typo in the first table, Service Tiers.
There's a footnote indicator in Storage size, but the footnote it's pointing to says: "Elastic pools for Hyperscale are currently in preview", which, I believe, is about the compute size for Hyperscale tier (it has the same footnote indicator).

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

ID: 8f18e8a8-1260-cf2f-5540-4fd974e69f98
Version Independent ID: 8a77d114-fd9e-0198-4bf2-fbd60c6a1251
Content: vCore purchasing model - Azure SQL Database
Content Source: azure-sql/database/service-tiers-sql-database-vcore.md
Service: sql-database
Sub-service: performance
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

Hi @SQLFinn ,
Thanks for sharing this feedback. We will look into this and update as appropriate.
Hi @WilliamDAssafMSFT,
Could you please look into this request, thanks.


Initial testing... worked great with Postgres

I've been using postgres on my go-to test project lately so I just tried that out of the box... and it worked perfectly.  Had to change the database type to Postgres of course.
ddev get bserem/ddev-adminer && ddev restart then ddev describe to find the port.
I don't recommend using port 8080, recommend using something much less familiar. Lots of people use 8080 for the web server (ddev-router), so this would conflict. How about changing it to 11111 or something?

I have to say you made my day, and it was already a very good day. I think the ddev-get functionality is by far the most important thing in v1.19, and maybe the most important thing added to it in a long time, because it allows curated and maintained things SO MUCH EASIER for people. And to see this just pop up was so wonderful. THANKS!

Also... do you have suggestions for improving https://github.com/drud/ddev-addon-template and its readme, or the main docs? PRs requested.


chore: better ci

Pull Request Test Coverage Report for Build 181

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.179%

Totals

Change from base Build 180:
0.0%

Covered Lines:
63

Relevant Lines:
70

💛  - Coveralls


nodes: Bring the default number of nodes down

With the new vCPU-based SKUs we now support clusters with 2 compute
nodes (for single AZ) and 3 compute node (for multi AZ). The new
minimums are also the defaults for new clusters.

/lgtm


not support tsx file

can you add the support for typescript react

With add typescriptreact language in package.json，the problem has been solved
{         "language": "typescriptreact",         "path": "./snippets/tsx.json" }


A little present for AngularClass. Webpack configuration documentation

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
I spent my time to make a present for you: I've annotated webpack configuration with docs.
Also I've removed unnecessary commas.

What is the current behavior? (You can also link to an open issue here)
It's the same as before;

What is the new behavior (if this is a feature change)?
It's the same as before;

Other information:
Enjoy it!

amazing


Add colorbar toggling based on biases provided

Codecov Report

Merging #116 into master will increase coverage by 2.14%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #116      +/-   ##
=========================================
+ Coverage   78.05%   80.2%   +2.14%
=========================================
  Files          26      26
  Lines        1431    1389      -42
=========================================
- Hits         1117    1114       -3
+ Misses        314     275      -39

Impacted Files
Coverage Δ

dwave_networkx/drawing/qubit_layout.py
12.09% <0%> (+1.06%)
:arrow_up:

dwave_networkx/drawing/chimera_layout.py
25% <0%> (+2.1%)
:arrow_up:

dwave_networkx/drawing/pegasus_layout.py
29.23% <0%> (+2.56%)
:arrow_up:

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 9ea1223...7abb573. Read the comment docs.

@arcondello what do you think of adding ax/cax kwargs? (pushed)


Fixes for Carthage

Fixed and tested all targets for carthage support
Fixes #1

Fixes #1

Wow, thanks a lot!


Conflict with the typescript declaration of qrcode-terminal

When wechaty and qrcode-terminal are installed at the same time, the declarations of qrcode-terminal is overwritten by wechaty

now the type of  function generate  is any;

It is caused by:
https://github.com/wechaty/wechaty/blob/main/src/typings.d.ts#L20
When we start using the qrcode-terminal, perhaps there's no @types/qrcode-termal yet.
A pr to remove this line will be welcome.


feat: support registry basic auth

support pull/push model from/to private oci registry.
relates: https://github.com/ollama/ollama/issues/2745

This would be very nice for my company, since we are using a nexus mirror and proxy.

If this pull request could be merged, it would greatly benefit enterprise users, as they typically cannot use unauthenticated registries. Implementing basic authentication would enable users to manage their models on a private registry more effectively.

I apologize for the direct mention, @jmorganca, but when you have a moment, would you kindly consider reviewing this? Thank you!

Hi @qcu266 thanks so much for the PR. While this is something we'd like to support in the future, Ollama currently supports an authentication scheme based on keypairs. Adding too many alternative authentication schemes might make it harder to evolve Ollama's registry code in the future (e.g. to make it faster), and so for the time being it would be best we stick to one scheme.


Encode escape characters when generating transaction

Description
This PR adds a function to encode characters that are not JSON marshaled by GO when generating signature data.
The characters handled are <, >, &.
See the GO comment below.
https://cs.opensource.google/go/go/+/refs/tags/go1.20.13:src/encoding/json/encode.go;l=46-53

Thank you for the contribution as always @jinoosss 🙏


Feature/estimation result

Added complexity average & final value

I encountered the following error while testing the UI:
After the admin/author presses the "Evaluate!" button and afterward presses the "Submit" button without previously choosing a final complexity value, an unhandled runtime error occurs.
On the "Choose a final value for the Complexity" view the UI renders the "complexity" value:= 1 in a blue color to imply that it's value is set to 1. But the complexity value is not set. You still have to press "1" again before submitting to omit the error.
It seems that a default value initialization is missing.
The rest looks pretty good to me 👍

Thx for the review, I've changed it now!


Event link.

Can we retrieve event link? Then we can use the link as Read more... to go Wikipedia.

The page from which the scraper gets its data does not have a direct link towards each event. However, I can get links to the keywords for each event and scrap them as well. For example:
1797 - French Revolutionary Wars: An Austrian column is defeated by the French in the Battle of Valvasone
Thanks for the suggestion! :)

Yes, It's good. We can use event link in Android app too. In share action menu.


Fix chirps test

Test isn't passing and this changes the tool, which is not a valid way to test this.


add mimetypes

@mtrmac PTAL (again)
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

LGTM, will merge after a rebase.

@mtrmac rebased


Minor bug in crops.py?

Hi,
I might be completely wrong about this but in line 12-13 in crops.py it reads:

xright_pad = max(0, int(round(pos_x + c)) - frame_sz[1])
ybottom_pad = max(0, int(round(pos_y + c)) - frame_sz[0])

From my understanding, the first variable is checking if the crop exceeds the right-hand side limit of the frame (x direction) and second one for bottom (y direction), so shouldn't it instead be:

xright_pad = max(0, int(round(pos_x + c)) - frame_sz[0])
ybottom_pad = max(0, int(round(pos_y + c)) - frame_sz[1])

@YugeTen the code is updated and this part has been fixed. Thanks.


danger local fails to find token in local environment

Report
What did you do?
danger local in my feature branch
What did you expect to happen?
I see dry run of Danger for this branch (or I don't understand local option)
What happened instead?
Running your Dangerfile against this PR - https://github.com/xxx/pull/2333
Turning on --verbose

Local repository was not found on GitHub. If you're trying to test a private repository please provide a valid API token through DANGER_GITHUB_API_TOKEN environment variable.

Even though echo $DANGER_GITHUB_API_TOKEN prints the token
Your Environment
danger 4.3.0

Yes, it's frustrating :-( Unfortunately I had a dig into the Rube code because there is no other way to understand what's going on.

Maybe that's a bug? I don't work on any private repos, so it's possible that it's something I've missed

danger local works fine for me when executed against private repos.
@garnett How do you define your DANGER_GITHUB_API_TOKEN variable? Perhaps you don't export it as an environment variable?
For example, export DANGER_GITHUB_API_TOKEN=123 is how it's done in bash.

What specific permission should this token have @orta


Update sp-addlinkedserver-transact-sql.md

Removed examples related to Microsoft.ACE.OLEDB.12.0 as this provider is not supported for linked server use.

@denniwil : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Will push this change in a different PR that is properly based against master.


GUID of created note on business notebook is null

When a note is created on business notebook, the guid of result note is always null.
How do I get the guid of created note?
The code is below:
session.getClientFactory().createBusinessNoteStoreClientAsync(new OnClientCallback<AsyncBusinessNoteStoreClient>() {
    @Override
    public void onSuccess(AsyncBusinessNoteStoreClient bNoteStore) {
        if (bNoteStore == null) {
            // failed
        } else {
            bNoteStore.createNoteAsync(note, nb, new OnClientCallback<Note>() {
                @Override
                public void onSuccess(Note data) {
                    String guid = data.getGuid();
                    /* guid is null!! but the note is created */
                }
                @Override
                public void onException(Exception exception) {
                    // failed
                }
            });
        }
    }
    @Override
    public void onException(Exception ex) {
        // failed
    }
});

Dict/1204

Could you update the SDK to 2.0.0 and try again? The issue should be fixed.

Thank you


GRPCResponseHeadersFilter does not return grpc-status code properly in the trailing headers

Describe the bug
Spring cloud gateway currently alway returns grpc-status as 0 within the GRPCResponseHeadersFilter.
This results in an incorrect behaviour when the downstream sever returns a grpc-status value other than 0 (OK).
The same bug was reported in (https://github.com/spring-cloud/spring-cloud-gateway/issues/2679) however it seems that the root cause was not properly diagnosed and the fixed provided was quite convoluted.
As far as i understand, the solution is quite simple: GRPCResponseHeadersFilter should properly return the grpc-status as the trailing headers based on the response received from the downstream service. Instead of always returning 0 as the status code.
With this bug its quite difficult using spring-cloud-gateway to route gRPC requests since error status are not properly handled.
Versions:
spring-cloud-gateway version: 3.1.4 based on spring-cloud-starter-gateway 3.1.4
Sample
Base on a previous bug submition regarding this filter i've reproduced this behaviour with a potential fix in this repository:
https://github.com/kkondratov/spring-cloud-gateway-grpc-status-bug

Duplicates #2562


Add hard limit of 30 messages to message queue

This will prevent bugs from filling up memory or spamming the channel if the service is offline for a bit.

This Pull Request has been merged by GitConsensus.
Vote Totals

Yes
No
Abstain
Voters

3
0
0
3

Vote Breakdown

User
Yes
No
Abstain

tedivm
✔

ViezeVingertjes
✔

dragoonreas
✔

Vote Results

Criteria
Result

Has Quorum
True

Has Votes
True


Contract assembly for Microsoft.VisualBasic.dll should define "Empty" _MYTYPE.

Using C# compiler from VS2013 produces no "My" namespace in Microsoft.VisualBasic.Contracts.dll even if _MYTYPE is set to "Windows". This behavior changed in Roslyn and in order to disable My namespace in output assembly _MYTYPE shall be set to "Empty". Setting it to "Empty" in Microsoft.VisualBasic10.vbproj file will fix compilation for VS2015 and at the same time will not change compilation results for VS2013.

Fixed by #43


Ghost Admin does not work in browser with full ES6 support

Issue Summary
Since Ghost-Admin has issue creation disabled so I am opening the issue here.
Ghost-Admin targets only last two versions of browsers . So async functions(an ES7 feature) are not transpiled(to ES6) and thus it leads to the admin not working on Firefox 50 which has full ES6 support but no ES7 support. I agree that there is no need to support IE11 but I believe ghost admin client should support the browsers for at least 5 years (browserlist config last 5 years ). This config would automatically remove support for older browsers every year.
To Reproduce

Open ghost admin on any browser which does not support async functions (data can be obtained from MDN)
The admin does not load and only the spinner is displayed. Now open browser console, check the error message related to ghost.min.js, find the line number& offset corresponding to the error and you will notice that the error is because browser does not understand the async keyword.

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
I expect the admin client to open in a  3 years 9 month old browser.
Technical details:

Ghost Version: 3.12.0 (irrelevant)
Node Version: 10.x (irrelevant)
Browser/OS: Firefox 50/Windows 10
Database: Irrelevant

For the last few years Ghost has only supported the latest few versions of evergreen browsers and we have no plans to change that. If you wish to use Ghost please upgrade to a modern browser.

I generally use Ghost Admin from Edge where it works fine. Just yesterday, I came to across this thing and thought that it is a bug(which isn't since you have no plans to support older browsers). But I would  like to still ask you to support the last 10 versions(~1 year) of browsers like chrome and firefox which have a fast release cycle.


Calling jest.useFakeTimers() before importing Mikro-ORM results in dates not being hydrated properly.

Describe the bug
Title pretty much says it. Moving the call later (after the ORM has been loaded) works ok, otherwise they come through as ISO datestrings.
To Reproduce
import { Entity, ManyToOne, MikroORM, PrimaryKey, Property } from '@mikro-orm/core';
import type { SqlEntityManager } from '@mikro-orm/knex';

@Entity()
export class Trade {

  @PrimaryKey()
  id!: number;

  @Property()
  tradeStart: Date = new Date();

}

describe('GH issue xxxx', () => {

  let orm: MikroORM;

  beforeAll(async () => {
    jest.useFakeTimers({advanceTimers: true});
    orm = await MikroORM.init({
      entities: [Trade],
      type: 'postgresql',
      dbName: 'mikro_orm_test_xxxx',
    });
    await orm.getSchemaGenerator().refreshDatabase();
  });

  afterAll(async () => {
    await orm.close(true);
  });

  test(`GH issue xxxx`, async () => {
    const em = orm.em.fork() as SqlEntityManager;

    const t = em.create(Trade, {tradeStart: new Date()});
    await em.persistAndFlush(t);
    em.clear();

    const trade =  await em.findOne(Trade, {id: t.id});
    expect(trade?.tradeStart instanceof Date).toBeTruthy()
  });

});

Expected behavior
Expected Date fields to be hydrated as dates.
Additional context
Add any other context about the problem here.
Versions

Dependency
Version

node
18.3

typescript
4.4.4

mikro-orm
5.1.2

your-driver
pg

I really doubt this is something to be fixed in MikroORM. Hydration is synchronous just like processing of mapped types.
Tried your repro, it is passing on my end (at least on master, 5.1.2 is out dated version so be sure to update).


Add a PerfKitExplorer dashboard for every benchmark.

Would you mind:

Pretty-printing these (jq does a fine job, as does Python's json.dumps(..., indent=2)).
Naming each JSON file after the benchmark it tracks.

PTAL

In addition to the readme.md in the dashboards directory I think you need to have help in the top level readme.md as well.
Also I think the dashboards should be rooted at the top level vs under tools.

I like them under /tools - keeping the top-level directory uncluttered is nice.

Moved to root directory and renamed the folder to dashboards. Since the next step will be adding integration tests for benchmarks. This will be more than a tool.

PTAL

By the way I am OK with this under tools but my vote is at the top layer.
The reason I don't prefer tools is that these are not a tool... the are a
feature set.
On Jun 23, 2015 10:48 PM, "yuyanting"<EMAIL_ADDRESS>wrote:

PTAL
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/pull/332#issuecomment-114637794
.

This CL is going to move to the PerfKitExplorer project.


option "-o -" results in encoding error

Using the following environment:
$ asciidoctor-pdf -v
Asciidoctor PDF 1.5.0.beta.8 using Asciidoctor 2.0.10 [https://asciidoctor.org]
Runtime Environment (ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]) (lc:US-ASCII fs:US-ASCII in:US-ASCII ex:US-ASCII)

I have observed this behavior:
$ touch foo.adoc
$ asciidoctor-pdf -o - foo.adoc --trace

Traceback (most recent call last):
	22: from /usr/local/bin/asciidoctor-pdf:23:in `<main>'
	21: from /usr/local/bin/asciidoctor-pdf:23:in `load'
	20: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.5.0.beta.8/bin/asciidoctor-pdf:27:in `<top (required)>'
	19: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/cli/invoker.rb:111:in `invoke!'
	18: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/cli/invoker.rb:111:in `each'
	17: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/cli/invoker.rb:128:in `block in invoke!'
	16: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/convert.rb:183:in `convert_file'
	15: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/convert.rb:183:in `open'
	14: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/convert.rb:183:in `block in convert_file'
	13: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/convert.rb:124:in `convert'
	12: from /var/lib/gems/2.5.0/gems/asciidoctor-2.0.10/lib/asciidoctor/document.rb:978:in `write'
	11: from /var/lib/gems/2.5.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf/converter.rb:3556:in `write'
	10: from /var/lib/gems/2.5.0/gems/prawn-2.2.2/lib/prawn/document.rb:378:in `render'
	 9: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/renderer.rb:165:in `render'
	 8: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/renderer.rb:200:in `render_body'
	 7: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/document_state.rb:70:in `render_body'
	 6: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/object_store.rb:70:in `each'
	 5: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/object_store.rb:70:in `each'
	 4: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/object_store.rb:71:in `block in each'
	 3: from /var/lib/gems/2.5.0/gems/pdf-core-0.7.0/lib/pdf/core/document_state.rb:72:in `block in render_body'
	 2: from /usr/lib/ruby/2.5.0/delegate.rb:83:in `method_missing'
	 1: from /usr/lib/ruby/2.5.0/delegate.rb:83:in `<<'
/usr/lib/ruby/2.5.0/delegate.rb:83:in `write': "\x9C" from ASCII-8BIT to UTF-8 (Encoding::UndefinedConversionError)

However
$ asciidoctor-pdf -o /dev/stdout foo.adoc --trace

<finishes with no error>

I suspected this was because my system encoding was not UTF-8, but switching to UTF-8 did not solve it. I've also tried different versions of asciidoctor-pdf, and it does not solve the issue.
It's easy enough to just use /dev/stdout, but I thought it might be good to raise awareness of the issue.

You cannot pipe the terminal. A PDF document has binary streams (always the fonts), so that's not going to work, and it's going to look horrible. You need to pipe to a file or another process.

Our goal is not to observe the output with terminal. We capture the output and write the data independently, which allows us to write to AWS S3 without saving to the local filesystem of a Docker container.

I think I see the problem. The following does not work:
asciidoctor-pdf -o - foo.adoc > to-file.pdf

In the interim, you can have the converter write to the output file:
asciidoctor-pdf -o to-file.pdf foo.adoc

Turns out this is a regression due to a change in Prawn. I've added a test to the PR to make sure it stays working.


Listing Management > isOrgSteward Check (Evan)

780
STR -
login as julia
goTo > listing management
goTo > Ministry Of Love (tab)
RESULTS - Success; able to access tab and contents
EXPECTED RESULTS - Failure; authorization to tab should fail because:
isOrgSteward() : org.ShortName is undefined

Check to see if this is still a problem.

PR Submitted

Merged


[Suggestion] Let the Khendal Knight drop Dirt instead of MagmaCream

https://github.com/SleepyTrousers/EnderZoo/blob/master/src/main/java/crazypants/enderzoo/entity/EntityDireSlime.java#L108

Interesting.. I'll ask the owner if we are outdated.


Scotian Shelf fall and spring are only a few years

Fall and spring data are only 1979-1984. Is this a bug or is this correct? If the fall and spring surveys have ended, we may want to trim them out. Or are we mistakenly splitting one survey into three parts (spring, summer, fall)?

The data are from 1970-2018.  The trimmed_dat table and BY_SPECIES_DATA tables both contain data from 1970-2018.

Sorry, just saw the fine detail that I glazed over earlier.  Yes, it is correct that Fall and Spring surveys only ran from 1979-1984.  Do you want them to be removed from the website?

We should ask Tobias or other Scotian Shelf data provider about the right
way to handle spring and fall data.
On Wed, May 22, 2019 at 10:58 AM Michelle Stuart<EMAIL_ADDRESS>wrote:

Sorry, just saw the fine detail that I glazed over earlier. Yes, it is
correct that Fall and Spring surveys only ran from 1979-1984. Do you want
them to be removed from the website?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mpinsky/OceanAdapt/issues/88?email_source=notifications&email_token=ABQTJZH43NGZMOSQYJOMF2TPWVNS3A5CNFSM4HOUSJ2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7KVAA#issuecomment-494840448,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQTJZCPIIKQ6BWC7EK6DSDPWVNS3ANCNFSM4HOUSJ2A
.

Fall and Spring have been removed from final centroids.

And maps and website GUI? Just checking.
On Fri, May 24, 2019 at 3:01 PM Michelle Stuart<EMAIL_ADDRESS>wrote:

Fall and Spring have been removed from final centroids.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mpinsky/OceanAdapt/issues/88?email_source=notifications&email_token=ABQTJZB5HMF6QR5V2B6QL6DPXA3QBA5CNFSM4HOUSJ2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGKDTI#issuecomment-495755725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQTJZGXUGVWXWV6CDKOMX3PXA3QBANCNFSM4HOUSJ2A
.

--
Please excuse, sent from a device with tiny keys...

Yes, the website now says “Scotian Shelf” and does not give options to select seasons.
On May 28, 2019, at 8:41 PM, Malin Pinsky <notifications<EMAIL_ADDRESS>wrote:
And maps and website GUI? Just checking.
On Fri, May 24, 2019 at 3:01 PM Michelle Stuart <notifications<EMAIL_ADDRESS>wrote:

Fall and Spring have been removed from final centroids.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mpinsky/OceanAdapt/issues/88?email_source=notifications&email_token=ABQTJZB5HMF6QR5V2B6QL6DPXA3QBA5CNFSM4HOUSJ2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGKDTI#issuecomment-495755725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQTJZGXUGVWXWV6CDKOMX3PXA3QBANCNFSM4HOUSJ2A
.

--
Please excuse, sent from a device with tiny keys...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmpinsky%2FOceanAdapt%2Fissues%2F88%3Femail_source%3Dnotifications%26email_token%3DAG664YJA5BMW2N277JQLG5LPXXGMHA5CNFSM4HOUSJ2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWN2S5Y%23issuecomment-496740727&data=02|01|michelle.stuart%40rutgers.edu|6a332435d8b34d63088c08d6e3ce6bb6|b92d2b234d35447093ff69aca6632ffe|1|0|636946873042195591&sdata=NC59hsbrXhXHdiFgcOnyceoGaIRJ6MGfckUEFV2ltSs%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG664YIFYQM5S4XPBNZS2P3PXXGMHANCNFSM4HOUSJ2A&data=02|01|michelle.stuart%40rutgers.edu|6a332435d8b34d63088c08d6e3ce6bb6|b92d2b234d35447093ff69aca6632ffe|1|0|636946873042205588&sdata=w8d35RiV4vLPsdFIdRoG9kzq8lf8sl2b8lIKy6z7WP4%3D&reserved=0.