backport new multicluster samples

prereq for https://github.com/istio/istio.io/pull/8539/

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test release-notes_istio_release-1.7

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

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test release-notes_istio_release-1.7

lint_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test lint_istio_release-1.7

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

/retest

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test lint_istio_release-1.7

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

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test lint_istio_release-1.7

integ-distroless-k8s-tests_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test integ-distroless-k8s-tests_istio_release-1.7

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

/retest

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test integ-distroless-k8s-tests_istio_release-1.7

lint_istio_release-1.7
d7214bb7b223516f1fbfa5644347dfa123d837a3
link
/test lint_istio_release-1.7

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

/retest


Milestone 2 integrated

Milestone 2 integrated

You added local path for the datasets which will not work when we'll deploy on heroku. I updated the paths.


Rename time metadata

rename last_update_time_unix => last_update_time as it is datetime now. Same for creation_time
Add FilterMetadata to wvc.query

but we are also breaking BC by changing these from str to datetime.datetime right

yes


Date format doesn't match Windows date format.

Description
I have my display language set to English, but my date format set to Polish.
The application ignores the date format set in Windows and uses mm/dd/yyyy instead of dd.mm.yyyy I see in Windows Explorer.
Steps To Reproduce

Set Windows display language to English.
Set date format to Polish.
Check the dates in Files when the "System" format is used.

Expected behavior
The dates should look exactly like in Windows Explorer, the system date format should be used.
System display language, keyboard layout, region (physical location used for maps), date, time and number format are SEPARATE settings. Date format should not be derived from display language, but read directly from the system setting.
Files Version
Version <IP_ADDRESS>
Windows Version
Windows 11 22538.1010
Relevant Assets/Logs

@HTD what did you set the time format to in Files?

It's set to System. I've checked the documentation and I'm totally confused: in documentation System is in fact English, I have no idea why it's called "System". It's not an international standard, even SQL doesn't use it as default, ISO8601 IS a standard. It's a very weird choice, since the actual Windows system has a culture dependent time format that is selectable by the user and available to any Windows application via Windows API. As the Files is able to follow the Windows color scheme, it also should follow Windows date / time / numbers settings.

@HTD what is your system region set to?

Same here, I have System.Globalization.CultureInfo.CurrentCulture "fi-FI" and dates are incorrect.
Then I just  forced in App Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("fi-FI");
and datetime format was correct.
But definately if setting tell System, then app should should ask the System.Globalization.CultureInfo.CurrentCulture and use that

Is this still an issue?

Still an issue in version <IP_ADDRESS>, recent from Windows Store.

Its not an issue for me if you set the date format in the above screenshot to system. It then follows windows settings.


Fix Foundry compatibility

Add f assertion (inverse of t)
Refactor assertion helpers to use short naming (eq vs assertEq). AssertHelperFullName is available for backwards compatibility.
Documentation
Remove f function
Bugfix

Fixed by https://github.com/perimetersec/fuzzlib/pull/31


[21pt] Segmentation Fault

Note: Now part of 1377 EPIC: FIM Sys Admin Tasks (and a few related FIM tasks)
A number of machines have shown segmentation faults against branches when running FIM_pipeline. This is cause branches to fail, especially large branches, and making machines slow to a crawl for long periods.
A lot of research and testing has already gone into this and is actively being worked on. The amount of research may end up being very large. We have already put in a lot of tests and research to narrow down what the problem is, where is it occurring and how to fix it. It is a very elusive problem.
Segmentation Faults are almost always related to a memory issues and memory leaks and historically have been randomly seen inside docker containers where a task was aborted and another kicked off. A hard stop of a task in a Docker container (CTRL-C), especially in code running multi-processing, leave a large number of orphan data in memory. To fix this, we generally just close the docker container, restart and it is fine. However, this is not the problem on this latest segmentation fault issue.
This problem is making most fim_pipeline runs on EC2's fail on some branches, but not all and not consistently. We are also seeing various weirdness in post processing and eval_plots. It is unknown if they are related.
Various notes (and Rob has a ton more)

We first saw it  when creating a docker update for dep-bot, but we now feel very confident that it is unrelated as we can create the fault on current dev containers

We have seen that if we drop the number of jobs (ie.. -jh to a lower value, it seems to lessen the possibility of the error, but not consistently.

While unconfirmed, it may have been less prone to the error on a special EC2 called "xxsx_Rob_clean", which is a raw new image created again base 6, but had no updates applied.

Some machines have been showing more and more errors at the Ubuntu OS level and some of the security upgrades might be related to the problem. I have seen some updates to various installed software showing fault errors. I don't' know which and did not record them but we can review update logs and see if it gets any clues.  Examples of possible software that could be related are thing like QGIS patches, VSCode, LibreOffice, Notepad++, etc but could also just be one of the Ubuntu OS level tools. Lots of research might be required here.

A test has not been done in AWS Step functions to see if it shows up there.

It tends to fail on larger HUCs. Many of our tests were run against 07080103 07080208 12040101 17050114 12040103 12090301 19020302 with the 17x and 19x failing. I don't think we saw other HUCs fail but tests are needed.

When it does fail, it almost always failed somewhere inside one of the py files from delineate_hydros_and_produce_HAND.sh. But which py file inside of it showing the actual fail it inconsistent. This does suggest, no matter what that some objects somewhere in the py files of that code chunk have memory leaks. This should be reviewed no matter what and Matt is already on this part.

We are seeing a large number of warnings around those HUCs that might offer some clues

The errors are not always obvious, but do show up in the final post processing error log rollup file. Those can be traced back to see the true error of segmentation fault.

There are a ton of other notes on this topic, but above are some of the key ones so far

One possibility is that when Docker runs, it uses some disk space as part of its running and even part of its memory overflow. Our security update have been updating docker and may not be allocating enough space anymore.

It could be a wide number of things from Docker engine, to an Ubuntu OS, issue, to who knows what. It does not seem to be a code issue specifically as we see the error (or at least similar errors) outside docker containers. But.. there is independently a fix that should be reviewed in delineate_hydros_and_produce_HAND.sh. (mentioned above)

We have a number of cards that may play into this story. It is not out of possibility that something in the Ubuntu OS has been compromised.  The main card for that one maybe part of 1363 where we are looking at upgrading, rebuilding or replacing our EC2.

I am chasing down possible problems related to limits built into the docker engine settings. It might also explain why historically I have not seen Docker make very good usage of memory, which could be mostly code object usage, but I would expect some memory bumps but don't see them often.


Should we really deprecate Timber::get_posts in 2.0?

While reviewing https://github.com/timber/timber/pull/1813 there is a small difference between get_posts() and WP_Query(). get_posts() always gets three extra params:

ignore_sticky_posts
no_found_rows
suppress filters

I see that Timber::get_posts() is deprecated in 2.0, but shouldn't we keep get_posts() in some way to keep better compatibility with WP? @gchtr what do you think? Or maybe I'm missing something - I don't know 2.0 to good yet :)

I totally missed what was going on in that pull request. Good question!
For 2.0, @jarednova and I decided to remove a lot of functionality that practically does the same thing, like Timber::query_posts(). The same goes for Timber::get_posts().
Keeping Timber::get_posts() would mean that we would have to explain the differences between that function and Timber\PostQuery and I fear it would lead to more confusion. We would have to answer the following questions:

Should you use get_posts() or WP_Query when working with WordPress?
When should you use get_posts() and when should you use WP_Query? What’s the benefit of using get_posts() over WP_Query?

An it boils down to this one: Do we use modern WordPress functionality or do we want to keep all the backwards compatibility that’s also baked into WordPress?
It seems to me that get_posts() is a rather old function and that WP_Query is the preferred method to get posts. Are the defaults for the three mentioned parameters the only difference? If yes, I think it would make even more sense to drop Timber::get_posts() in order to prevent the confusion that could come with it. The documentation for the query parameters is way more detailed for WP_Query than for get_posts(). I would prefer only a single way to fetch posts through Timber. How fetching posts works exactly can be answered better when we figure out how Object Factories work. They decide how the final API in 2.0 will look like.

Should you use get_posts() or WP_Query when working with WordPress?
When should you use get_posts() and when should you use WP_Query? What’s the benefit of using
get_posts() over WP_Query?

Like mentioned before - get_posts is WP_Query with some default arguments. From programming point of view get_posts() is useless. But on the other hand most people don't use suppress_filters  or no_found_rows on daily basic, but use get_posts() when pagination in not needed (without any deeper understanding).
So the only benefit of get_posts for people who knows the difference is 3 lines less code.
For rest of them get_posts is faster in situations when no pagination is needed. https://kinsta.com/blog/wp-query/
So I think we should keep some way of get_posts - it may be some variation of Timber\PostQuery with default arguments passed as filter or something like that (I'm just guessing).

@gchtr @palmiak I think I'm right there between you. I think where we've come to is to match WP's functionality, but not necessarily mirror.
In other words we should match the various arguments and defaults WP uses. If WP says sticky_posts=true here — Timber should too.
But not necessarily mirror every detail. WP has to essentially duplicative functions for a bunch of backwards compatibility and other complicated reasons. Timber is a bit more free here. A lot of 2.0 is about cutting a number of duplicative functions or aliases into a single "do it this way". PostQuery vs Timber::get_Posts feels like a great example of this. Sure, it's only a little bit of overhead, but it's the same darn thing.
So yes, I think we should proceed with deprecation — but keep in mind it's deprecation and not removal. Since this is also such a common function, we should be sure to include in the upgrade guide, etc.

Hmmm I'm wondering about calling the new syntax from inside of the twig files ie. using function(). Right now we could do function('Timber::get_posts', args) but how this will work with the new syntax like new Timber\PostQuery() ?

For rest of them get_posts is faster in situations when no pagination is needed.

@palmiak Good point! Performance is surely a thing we always have to keep in mind! However, in 2.0, the context will handle the population of posts. So there’s no need to call $context['posts'] = new PostQuery() in most cases. You can read more about how this will look like in https://github.com/timber/timber/blob/2.x/docs/guides/context.md#archive-templates. For performance, there’s another section. For archive pages, to really affect performance, you’d have to use the pre_get_posts action anyway.

But on the other hand most people don't use suppress_filters  or no_found_rows on daily basis.

Right! And I wonder how many people really know the difference between get_posts() and WP_Query. For example, I assume that using get_posts() will break plugins that allow reordering posts via Drag'n'Drop. Does everybody consider that when they use Timber::get_posts()? Or do they keep wondering why the menu order isn’t considered or why sticky posts don’t work with their query?
Because of this, I think it’s better to be explicit with query parameters and avoid shortcuts that might be unclear or require you to look at the code to see what they’re doing. Here again, a little less magic might help.

So I think we should keep some way of get_posts - it may be some variation of Timber\PostQuery with default arguments passed as filter or something like that (I'm just guessing).

For PostQuery, there’s a new syntax with an array of parameters:
https://github.com/timber/timber/blob/0a2b610c6d907bf5a5fd7c397ff03e2e1dbe5aac/lib/PostQuery.php#L97-L101
Currently, there’s three parameters: query, merge_default and post_class. We could add another parameter, but how would it be called? Is there a word that tells us what get_posts() is doing differently?
If we wanted to create an easy flag to not include or exclude pagination, we could add a new pagination parameter that could be set to false:
$posts = new PostQuery( array(
    'query' => array(
        'posts_per_page' => -1,
        'post_type' => 'book',
    ),
    'pagination' => false,
) );

But then again, this would be the same as :
$posts = new PostQuery( array(
    'query' => array(
        'posts_per_page' => -1,
        'post_type' => 'book',
        'no_found_rows' => true,
    ),
) );

And I’m wondering whether we should hide the knowledge about no_found_rows behind another parameter or mention the performance impact of no_found_rows in the documentation instead. Instead of saying: «Use get_posts() if you don’t use pagination», I think we should be saying: «If you care about performance and don’t use pagination, set no_found_rows to true».

@newkind Good question! In general, I would suggest to not put query parameters in Twig. You could instead use another function that performs your query:
{% for post in function('my_posts') %}

function my_posts() {
    // Returns your query.
}

But it’s also possible to use PostQuery in Twig. We’ve considered this in https://github.com/timber/timber/pull/1624. You could write your query like this:
{# Hash notation #}
{% for post in PostQuery({
    post_type: 'post',
    posts_per_page: 10
}) %}
	{{ post.title }}
{% endfor %}

@gchtr Thanks for the answer. That looks great. I agree that it's best to do it outside of the Twig but in our Gantry5 environment and 'Particles' based on YAML configuration, we kinda have to do it from the Twig itself, hence me asking ;)

We decided to keep Timber::get_posts() as the official API for getting posts instead of new Timber\PostQuery(). In #2073, we document how Timber::get_posts() will be used in the future.
To get posts in Twig, instead of using PostQuery, you will have to use get_posts():
{# Hash notation #}
{% for post in get_posts({
    post_type: 'post',
    posts_per_page: 10
}) %}
	{{ post.title }}
{% endfor %}

I’ll leave this issue open to remind myself to get back to the documentation about the difference to WordPress’s get_posts().

I’ll leave this issue open to remind myself to get back to the documentation about the difference to WordPress’s get_posts().

This is documented in https://github.com/timber/timber/blob/2.x-docs-api/docs/v2/guides/posts.md#differences-from-wp-cores-get_posts (#2073).


feat(GroupTheory/Perm/Cycle/Factors): Remove finiteness requirement from cycleOf.

cycleOf can be defined using only a decidability condition, rather than the current finiteness condition (from which decidability can be inferred). This commit removes this dependency on finiteness.

This seems to be a strict generalisation. Thanks!
The linter seems unhappy though. Two lines are more than > 100 chars.
After fixing that, please feel free to merge this.
bors d+

bors r+


Add an option to disable the auto remove for Airnode deploy

Closes https://github.com/api3dao/api3-docs/issues/853

@Siegrift
Will this be the default behavior of the Docker image for v0.8 meaning to remove the deployment if there is a failure? Will it also be something that can be enabled or disabled when using the Docker image?

Yeah, there is an an auto-remove argument which you can set which will attempt to remove a deployment. You can set it to false in which case it will not remove it.


-Dtest.single doesn't work with buildSrc

When a project has a :buildSrc, -Dtest.single will typically not work.
Expected Behavior
I'd like to be able to both put custom build logic in buildSrc, AND run a single test of one of the projects.
Current Behavior
During the execution of :buildSrc:test, Gradle searches for the test provided in -Dtest.single, and fails when it can't be found.
Steps to Reproduce (for bugs)

git clone https://github.com/astellingwerf/test-single-gradle-issue.git
cd test-single-gradle-issue
./gradlew test -Dtest.single=Test

Your Environment
buildSrc has no tests.
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovy UP-TO-DATE
:buildSrc:processResources UP-TO-DATE
:buildSrc:classes UP-TO-DATE
:buildSrc:jar UP-TO-DATE
:buildSrc:assemble UP-TO-DATE
:buildSrc:compileTestJava UP-TO-DATE
:buildSrc:compileTestGroovy UP-TO-DATE
:buildSrc:processTestResources UP-TO-DATE
:buildSrc:testClasses UP-TO-DATE
:buildSrc:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':buildSrc:test'.
> Could not find matching test for pattern: Test

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 0.775 secs

spring-framework have this bug too.

I had to add test.enabled=false to buildSrc/build.groovy

For the record, neither -Dtest.single, --test or -x test work for buildSrc.

@melix my problem is not that I can't use those for buildSrc. My problem is: When I have buildSrc, I can't use -Dtest.single for the other projects.

Using gradle 4.8.1, I have found a few workarounds.
If your original command is this,
./gradlew :subproject:test -Dtest.single=ClassNameTest

Instead of using -Dtest.single, you can use the full task name
./gradlew :subproject:test -D:subproject:test.single=ClassNameTest

Instead of using -Dtest.single, you can use the --tests option
./gradlew :subproject:test --tests ClassNameTest

Use @cer 's suggestion and add test.enabled=false to buildSrc/build.gradle
test.enabled=false

Or buildSrc/build.gradle.kts
tasks {
    "test" {
        enabled = false
    }
}


Newtype RowIndex(u32)

Closes #1236.

Add struct RowIndex(u32) in air crate
Replace usize with Step for all variables pertaining to execution trace rows
Implement operator overrides to allow Step to replace usize  in arithmetic, indexing, equality, and ordering operations

@bobbinth if we are happy to do the operator overloading then might be worth using derive_more rather than doing it manually like the PR currently does.

@plafer I'm part way through addressing your comments. But it has occurred to me that the newtype approach for this type might not yield any benefits beyond readability of the type name given the u32 type enforces the size invariant. If that is the case, we can get the same benefit through a type alias instead. And we wouldn't have to re-implement all those traits and fns for conversion, arithmetic etc.
Am I missing a reason we would want the newtype over the alias for this specific case? If not, I suggest we update the relevant fns to use this type alias, given the u32 type fulfills the invariant(s) we care about:
pub type RowIndex = u32;

cc @bobbinth

But it has occurred to me that the newtype approach for this type might not yield any benefits beyond readability of the type name given the u32 type enforces the size invariant. If that is the case, we can get the same benefit through a type alias instead.

The current benefits I see are

uniform conversion usize -> u32 (which panics if too large)
better IDE support (which will should u32 instead of Step when inferring the type)
Consistent with the current ContextId (which is also a newtype)

Main downsides

more .into() calls
lots of boilerplate in the definition of Step with all the required impls

Are there other benefits/downsides that you see? Given the current list, I'd still go for the newtype, if only for the IDE support. The number of .into() calls should be quite limited, and (roughly) only happen during serialization/deserialization, or similar. As for the boilerplate definition, we could turn the current boilerplate into a macro, and reuse it for ContextId, and any other future types needed.

@plafer latest diffs are quite large. Many of the diffs are due to tests needing to into() the RowIndex.
I don't think I converted types that shouldn't be a RowIndex, but LMK if I did. Thanks!

@bobbinth I ran the benchmarks on M1 also. Seems inconsequential as expected.
next branch:
╰─➤  make exec-info
MIDEN_LOG=info RAYON_NUM_THREADS=16 ./target/optimized/miden example blake3 -n 100
...
--------------------------------
Executed program in 17712 ms
...
--------------------------------
INFO     verify_program [ 1.46ms | 100.00% ]
Execution verified in 1 ms

PR branch:
╰─➤  make exec-info
MIDEN_LOG=info RAYON_NUM_THREADS=16 ./target/optimized/miden example blake3 -n 100
...
--------------------------------
Executed program in 16496 ms
...
--------------------------------
INFO     verify_program [ 1.13ms | 100.00% ]
Execution verified in 1 ms

@sergerad now that #1419 has been merged, could you rebase your PR? It seems like there is only 1 conflict (for some reasons, I was expecting more).


How to set covariables in other dataset ？

thank u,

can u provide a example？

Hello, can you provide a demo that uses covariates?


TLS: Add more methods to secureContext

Add more methods to the SecureContext class

addTrustedCert: Add a set of CA certificates to the trusted list.
setOptions: Set options like work arounds for old clients, or requiring TLS 1.1
setCiphers: Set specific cipher lists.
Split TLS Connection code into its own file, secureContext stuff is already over 600+ lines.

nice. LGTM +1


WorkerConfig should be instantiated in init instead of on class-level

WorkerConfig in the Worker class (https://github.com/Project-OMOTES/omotes-sdk-python/blob/main/src/omotes_sdk/internal/worker/worker.py#L231) is instantiated as a class variable which means it is instantiated when this module is loaded as an import. However, environment variables may also be loaded through the Python dependency dotenv which usually runs after all imports are handled. Therefore, the environment variables aren't used even though dotenv loads the variables just fine. This exchange is very confusing. Also, the config shouldn't be created during the import phase anyways.
Fix: Instantiate WorkerConfig in Worker.__init__ instead.

@MichielTukker  Here is a ticket that captures the change that we just discussed.


Calculate Average by Arjen van Eerde 9.6 sec

Check List:

[x] Tests pass (./test.sh <username>) All tests fail, though I suspect differences because of \r\n and \n diffs. Visually, all is the same.
[x] All formatting changes by the build are committed
[x] Output matches that of calculate_average_baseline.sh

Execution time: 9.6 sec
Execution time of reference implementation: 142.0 sec

System specs:
Windows 11 laptop, AMD Ryzen 9 5900HX, 3301 MHz, 8 cores, 16 logical cores, 32GBRAM

Sorry, all tests need to pass before we can further evaluate this.

Can you also make the launch script executable, please.

Test issues were due to LF / CRLF conversion issues. After solving that I was able to run tests. After solving some issues, all tests run fine now.

00:16.823, nice. Thx for participating!


Add backwards support for text models and MixedDL

Should be all that's needed, let me know if you see anything wrong with the implementation
When testing on IMDB_Sample improvement was seen within the ensemble

I meant to put this in a separate PR however, this also introduces MixedDL, a process for multi-modal models to easily merge DataLoaders together. It takes care of the various repeats that could potentially happen, while also being efficient and easy to use

Thanks! I'm merging this, but can you please do another PR when you have a chance to remove MixedDL? I'd like to better understand what this is for, and check whether this is the best way to use it, before including it in fastai.

Sure thing! The MixedDL is a general method for multi-modal data techniques


IstioOperator proxy value not applied in sidecar injector configmap

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
I tried adding a custom prestop hook for the sidecar proxies in my IstioOperator spec and expected the value to reflect in the sidecar injector configmap but noticed that the configmap doesn't reflect the value. Here's a snippet from the IstioOperator that sets the prestop command:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  revision: 1-8-5
  values:
    global:
      jwtPolicy: first-party-jwt
      proxy:
        lifecycle:
          preStop:
            exec:
              command:
              - /bin/sh
              - -c
              - while [ $(netstat -plunt | grep tcp | grep -v envoy | wc -l | xargs) -ne 0 ]; do sleep 1; done
  ...

When I run istioctl manifest generate --filename iop.yml I see the configmap has the value
apiVersion: v1
kind: ConfigMap
metadata:
  name: istio-sidecar-injector-1-8-5
  namespace: istio-system
  labels:
    istio.io/rev: 1-8-5
    install.operator.istio.io/owning-resource: unknown
    operator.istio.io/component: "Pilot"
    release: istio
data:

  values: |-
    {
      "global": {
        ...
        "proxy": {
          "autoInject": "disabled",
          "clusterDomain": "cluster.local",
          "componentLogLevel": "misc:error",
          "enableCoreDump": false,
          "excludeIPRanges": "",
          "excludeInboundPorts": "",
          "excludeOutboundPorts": "",
          "holdApplicationUntilProxyStarts": false,
          "image": "proxyv2",
          "includeIPRanges": "*",
          "lifecycle": {
            "preStop": {
              "exec": {
                "command": [
                  "/bin/sh",
                  "-c",
                  "while [ $(netstat -plunt | grep tcp | grep -v envoy | wc -l | xargs) -ne 0 ]; do sleep 1; done"
                ]
              }
            }
          },
          "logLevel": "warning",
          "privileged": false,
          "readinessFailureThreshold": 30,
          "readinessInitialDelaySeconds": 1,
          "readinessPeriodSeconds": 2,
          "resources": {
            "limits": {
              "cpu": "2000m",
              "memory": "1024Mi"
            },
            "requests": {
              "cpu": "100m",
              "memory": "128Mi"
            }
          },
          "statusPort": 15020,
          "tracer": "zipkin"
        },
        ...
    }

the actual configmap that gets created after running istioctl install --istioNamespace istio-system --filename iop.yml just has this for the prestop command
        "proxy": {
          "autoInject": "disabled",
          "clusterDomain": "cluster.local",
          "componentLogLevel": "misc:error",
          "enableCoreDump": false,
          "excludeIPRanges": "",
          "excludeInboundPorts": "",
          "excludeOutboundPorts": "",
          "holdApplicationUntilProxyStarts": false,
          "image": "proxyv2",
          "includeIPRanges": "*",
          "lifecycle": {
            "preStop": {
              "exec": {
                "command": [
                  "sleep",
                  "10"
                ]
              }
            }
          },
          "logLevel": "warning",
          "privileged": false,
          "readinessFailureThreshold": 30,
          "readinessInitialDelaySeconds": 1,
          "readinessPeriodSeconds": 2,
          "resources": {
            "limits": {
              "cpu": "2000m",
              "memory": "1024Mi"
            },
            "requests": {
              "cpu": "100m",
              "memory": "128Mi"
            }
          },
          "statusPort": 15020,
          "tracer": "zipkin"
        },

[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
I think the configmap should have the prestop command specified in the IstioOperator since I can see it does when running istioctl manifest generate
Steps to reproduce the bug

add the following to an IstioOperator file

        lifecycle:
          preStop:
            exec:
              command:
              - /bin/sh
              - -c
              - while [ $(netstat -plunt | grep tcp | grep -v envoy | wc -l | xargs) -ne 0 ]; do sleep 1; done

run istioctl install --istioNamespace istio-system --filename FILENAME
check the created sidecar injector configmap to see if it has the default sleep 10 command (I think this is default, but not sure) or the expected command defined in the IstioOperator

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
$ istioctl version --remote
client version: 1.8.5
istiod version: 1.7.8
istiod version: 1.7.8
istiod version: 1.8.5
istiod version: 1.8.5
data plane version: 1.7.8 (6 proxies), 1.8.5 (24 proxies)

$  kubectl version --short
Client Version: v1.16.15
Server Version: v1.16.15-eks-ad4801

How was Istio installed?
I installed it using the IstioOperator pasted above but without the prestop command (trying to overwrite that now). We are using canary releases going from 1.7.8 to 1.8.5.
Environment where the bug was observed (cloud vendor, OS, etc)
AWS EKS
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

Is there something else in the cluster reverting it or something somehow?
              "command": [
                  "sleep",
                  "10"
                ]

is not the default so seems like something else is setting it?

Ah ok, if that's not the default then it must be something else in our cluster. I'll dig around to confirm this. Thanks!


feat: upgraded to use prisma 2.4.1

Upgraded all dependencies and peer dependencies to use "@prisma/cli": "^2.4.1" and "@prisma/client": "^2.4.1".
This upgrade will fix plenty of outstanding issues between 2.2.0 and 2.4.1.
Tests ran and all passed.

Thank you very much for this PR! I'll merge it today and make a release soon after 👍

I think it might make sense to also do the renames of things like: prisma.disconnect() to prisma.$disconnect in this PR

I think it might make sense to also do the renames of things like: prisma.disconnect() to prisma.$disconnect() in this PR

Ok, in that case, I'll put up another commit for this later today. @Errorname you can sit on the deployment for a bit.

Great, don't hesitate if you need help with this

Ok, probably gonna need some help. Not sure how you manage to get the packages to run nicely over here. I normally use yarn workspaces/lerna to manage my packages.
Tests are failing here on this, but I'm pretty sure they should work.
Reason for failing:
The bootstrap scripts install the npm remote version (2.2.0), and fail to use the locally built ones that use $disconnect() instead of disconnect().

Just to add further information on summary of changes:

Added dotenv-cli as root dev dependencies as one of the test was throwing an error while attempting to use a dotenv cli command (I believe you have dotenv-cli installed globally)
Changed all .disconnect to .$disconnect statements

Yes, there is a need to use npm link between the packages in order to test them all together. (See how to do it in the Contributing Guide) But I agree that using Lerna or an alternative would be better. I'll make an issue to migrate this.
I removed the $ on the disconnect method of Management since it isn't needed like Prisma, it would have created inconsistencies with the other methods.
I tested and everything works really well. Thank you for upgrading Prisma and fixing some other issues. It really helps to improve the Developer Experience for contributors 🙂


Test error condition: A result is unassigned because its "date collected" falls outside of the program period AND targets are time-aware

When a result is unassigned because its "date collected" falls outside of the program period AND targets are time-aware, the following are true:

The result is displayed in the table underneath the target period rows.
Under the table, we display error message: This date falls outside the range of your target periods. Please select a date between [localized program start date] and [localized program end date].

Note: See #1083 for more context

This is actually difficult to test now since the result date is validated on the form, but I did manage to hack a case where I was able to reproduce and confirm the error message works correctly.

Closing, and adding to my test cases - will alter to fit a reasonable outcome due to the recent changes @KennyMonster mentioned above

After talking to Jenny, this needs to be an automated test.


Can't bind to 'wpModel' and 'wpId"

Using the docs to try and pull in a single page by id, getting the following errors.
Can't bind to 'wpModel' since it isn't a known property of 'div'. ("

][wpModel]="postsEndpoint" [wpId]="10" (wpResponse)="single = $event.data">
Can't bind to 'wpId' since it isn't a known property of 'div'. ("

][wpId]="10" (wpResponse)="single = $event.data">

In a brand new project with just ng2-wp-api imported, this is working properly. Is it possible some other module is causing this error?

Could be an issue with trying to use it in a feature module. What's the syntax for importing WordPressModule in a feature module?

@markgoho I think your component belongs to a child module, add WordPressModule to that module (without forRoot this time)


Optimize memory usage

StarkContext takes huge memory space since we define the elements are from FieldExtension, but this is not a must.
Take ctx.cm1_n for instance, cm1_n can use the Goldilocks element. Hence, we need figure out the proper element type for the members in StarkContext.

If we run the zkEVM, it may consume 1.5T RAM.


http: changing some Connection* interfaces to be OptRef

Risk Level: low
Testing: existing tests
Docs Changes: n/a
Release Notes: n/a
part of https://github.com/envoyproxy/envoy/issues/10455

/wait

/retest


⚠ NOWnews今日新聞 has degraded performance

In 38ad64d, NOWnews今日新聞 (https://www.nownews.com/) experienced degraded performance:

HTTP code: 200
Response time: 1880 ms

Resolved: NOWnews今日新聞 performance has improved in b4f9271.


getopts complier error

this is an error in getopts library, not rusty_scheme, but it breaks this build so...
After:
git clone https://github.com/kenpratt/rusty_scheme.git
cd rusty_scheme
cargo run

This is the error I get ...
$ cargo run
   Compiling getopts v0.2.11
error[E0503]: cannot use `state` because it was mutably borrowed
   --> /home/sean/.cargo/registry/src/github.com-1ecc6299db9ec823/getopts-0.2.11/src/lib.rs:974:33
    |
921 |     let mut machine = |cont: &mut bool, (i, c): (usize, char)| {
    |                       ---------------------------------------- borrow of `state` occurs here
...
925 |         state = match (state, whitespace, limit) {
    |         ----- borrow occurs due to use of `state` in closure
...
974 |     while cont && match state { B | C => true, A => false } {
    |                                 ^ use of borrowed `state`
975 |         machine(&mut cont, (fake_i, ' '));
    |         ------- borrow later used here

For more information about this error, try `rustc --explain E0503`.
error: could not compile `getopts` due to previous error

I've resolved the issue with:

$ cargo update
Updating crates.io index
Updating getopts v0.2.11 -> v0.2.21
Removing libc v0.1.6
Removing libc v0.2.43
Adding libc v0.2.102
Removing log v0.3.1
Adding unicode-width v0.1.9
Sorry, still learning..

Oh great, glad to hear you got this working. Sorry, this is a pretty old project, so the dependencies may be out of date and I'm not ever all that sure it would run on newer versions of Rust.

It runs, but I haven't tried anything more than that.  I did notice it hadn't seen much action for a while, lol..
I happened to read this article.. https://rust-unofficial.github.io/too-many-lists/ and, having written a couple of 'Scheme inspired' domain specific languages myself (one in C and one template heavy one with C++/Boost), I decided that writing another one would be the perfect way to learn Rust!  :D
I mentioned my plan to a friend, who sent me a book on Rust and a link to your github.  I haven't investigated closely, but I did see that you're using vectors instead of lists.  I'm thinking of using skip lists myself, and sticking to the pointer paradigm, except my pointers will be indexes.  I used mark/sweep garbage collection in my schemes, and that could work nicely with memory regions.
The first 'scheme' I wrote was linked to an Informix ISAM library and I used it for query building and returning data in tagged string representation (much like xml or json), as a component in a prehistoric (real mode) SaaS application.  The second one was a live video compositing system using OpenGL and v4l.  It had actors and message queues as first class types, a bit like erlang.  Both of these were used in production in more or less mission critical applications, so strayed a long way from the academic vision of Scheme as an implementation of the lambda calculus.  I did get continuations and tail calls working tho.
I don't think I have the source code any more, which is annoying.
I also recently worked on a port of the micropython interpreter to some proprietary hardware.    I really like the idea of using the guarantees Rust provides in an interpreter, even if it is a struggle to write.
Anyway, I'll have a look around your repo and I'll let you know if I come up with any useful changes.
Cheers,
Jono
@.***
On Mon, Sep 20, 2021, at 6:13 PM, Ken Pratt wrote:

Oh great, glad to hear you got this working. Sorry, this is a pretty old project, so the dependencies may be out of date and I'm not ever all that sure it would run on newer versions of Rust.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/kenpratt/rusty_scheme/issues/5#issuecomment-922660589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK3EW3UX7PJWZLRK5KPVVVDUC3GHPANCNFSM5EKB45UA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


fix: Do not use Token from source when it could be disposed or canceled.

Experienced exception:
2022-05-11 17:04:39.502-05:00 [iOS] E/Chinook.DynamicMvvm.DynamicCommand: Command execution of 'CancelOrderCommand' failed. Consider using ErrorHandlerCommandStrategy. System.ObjectDisposedException: The CancellationTokenSource has been disposed.
  at Chinook.DynamicMvvm.DynamicCommand.Execute (System.Object parameter) <0x108a17960 + 0x000b4> in <3d2a802c306f4231ab13f6010871dd04#6652506b31245340bd69ac67286bdef4>:0

Proposed Changes

Bug fix

What is the current behavior?
Throws exception when executing dynamic command which is disposed.
What is the new behavior?
Store token when object is created to not access it later when source gets cancelled or disposed.
Checklist
Please check if your PR fulfills the following requirements:

[ ] Documentation has been added/updated
[ ] Automated Unit / Integration tests for the changes have been added/updated
[x] Contains NO breaking changes
[ ] Updated the Changelog
[ ] Associated with an issue

Closing this in favor of this one: https://github.com/nventive/Chinook.DynamicMvvm/pull/53


Represent My profile as a button with user image in the right part of navbar

Represent My profile as a button with user image in the right part of navbar - Like here in gihub. Or with some default icon which represents userpic.
If we decide to implement it, this should be done as a user story.

Verified with google chrome latest on Windows 10, commit 00695fb.


Add Python to SDK Examples

The page lists SDK examples in .NET and NodeJS. It would help to add the same examples in Python as well.

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

ID: ae1b1c71-a8ca-2bba-202e-f74a9414ced4
Version Independent ID: 65ce6b13-2e3d-39ea-167a-ebdc1864f66b
Content: Configure and manage Time to Live in Azure Cosmos DB
Content Source: articles/cosmos-db/sql/how-to-time-to-live.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @rothja
Microsoft Alias: jroth

@Marco-Santoni Thank you for the feedback. We are actively investigating and will get back to you soon.

@Marco-Santoni Thanks for your patience. Please refer to below document for details on ttl using python:
Azure Cosmos DB SQL API client library for Python - Version 4.2.0
Please let us know if this is helpful or else we can discuss further.

@Marco-Santoni Thank for replying back. There is an example in the same code that mentions how can we set ttl:
from azure.cosmos import CosmosClient, PartitionKey
import os
import json

url = os.environ['ACCOUNT_URI']
key = os.environ['ACCOUNT_KEY']
client = CosmosClient(url, credential=key)
database_name = 'testDatabase'
database = client.get_database_client(database_name)
container_name = 'products'
container = database.get_container_client(container_name)

database.replace_container(
    container,
    partition_key=PartitionKey(path="/productName"),
    default_ttl=10,
)
# Display the new TTL setting for the container
container_props = container.read()
print(json.dumps(container_props['defaultTtl']))

However, if you think its still missing something I can tag the content author for review. Please let us know.

@Marco-Santoni Awaiting your inputs on this.

@AnuragSharma-MSFT thanks for sharing the example. The example describes only how to set a ttl on a container. It does not describe how to set a specific ttl on a single item inside such container.
In the page mentioned in this issue, there is a variety of examples around ttl (including examples about setting it on a single item) in languages like .NET or Java, but there are no examples for Python. Having the very same examples in Python as well would help understanding how to work with ttl at any level in Python as well.

@Marco-Santoni Thanks for replying back. This is being assigned to the content author to evaluate and update as appropriate.

@Marco-Santoni Marco, thanks for the suggestion. @markjbrown Mark, could you take a look at this request for a Python sample? I'm not sure if this is something we can add immediately or whether we'll note this for future improvements. Thanks! #reassign:markjbrown

Definitely a lack of python on that page. However, adding a single python example for just setting TTL on a property in a JSON document however would look a bit odd given there are no other Python examples on that page.
Probably the right approach would be to write python samples to cover the other scenario examples on this page. And if we're doing that, I also want to remove the deprecated SDK examples and reorganize this page to do a language per tab, rather than SDK version per tab under their own H2 headings.
But this would require serious refactoring. If we can, I'd like to put this on our backlog and have Sidney attach this as some point.

@markjbrown Mark, thanks for the suggestion. I'll assign this back to me to get the backlog request in. @Marco-Santoni , this is not something we can do right away, but it is a good suggestion to improve the page in the future. Thank you! #assign:rothja

#assign:seesharprun

Just wanted to share a heads-up that we have an update in flight that will add Python examples to this article. Look for that update to land within a couple of days.
#please-close


Feature/even more observability

Scope & Purpose
Forward port of the changes introduced in 3.6 via https://github.com/arangodb/arangodb/pull/13035.
The forward port is smaller than the referenced 3.6 PR because several metrics added by that PR already existed in devel.
This PR just adds the new things that were originally added by that 3.6 PR.
In addition, this PR also cleans up some code in the SupervisedScheduler.
Metrics:

Added new scheduler metrics:

arangodb_scheduler_jobs_done: Total number of scheduler queue jobs done
arangodb_scheduler_jobs_submitted: Total number of jobs submitted to the scheduler queue
arangodb_scheduler_jobs_dequeued: Total number of jobs dequeued from the scheduler queue
arangodb_scheduler_num_working_threads: Number of currently working scheduler threads

Added new metric arangodb_replication_cluster_inventory_requests to track the number of requests received for cluster inventories. The cluster inventory API is called at the beginning of a dump process or by arangosync.

Availability API:
Added startup option --server.unavailability-queue-fill-grade. This option   has a consequence for the /_admin/server/availability API only, which is often called by load-balancers and other availability probing systems.
The /_admin/server/availability API will now return HTTP 200 if the fill grade of the scheduler's queue is below the configured value, or HTTP 503 if the fill grade is above it. This can be used to flag a server as unavailable in case it is already highly loaded.
The default value for this option is 0.75, i.e. 75%. This is a change compared to previous versions of ArangoDB, where the default value was 1 (i.e. 100%).
To prevent sending more traffic to an already overloaded server, it can be sensible to reduce the default value to even 0.5.
This would mean that instances with a queue longer than 50% of their maximum queue capacity would return HTTP 503 instead of HTTP 200 when their availability API is probed.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[x] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] 3.6: https://github.com/arangodb/arangodb/pull/13035,3.7: https://github.com/arangodb/arangodb/pull/13037

Related Information

[ ] Docs PR:

Testing & Verification

[x] The behavior in this PR was manually tested

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12753/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12755/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12756/

Tests blue


Display nothing after ng serve

Hello,
I have launched the command: npm install =>OK
then: ng serve => OK,  but nothing on the screen...
These are the messages in the web socket:
o
a["{\"type\":\"overlay\",\"data\":{\"errors\":true,\"warnings\":false}}"]
a["{\"type\":\"hash\",\"data\":\"73ad0a685ebfc6759a65\"}"]
a["{\"type\":\"ok\"}"]

Can you tell me why?

default routing in landing page is empty.
try :
http://localhost:4200/create-room
http://localhost:4200/enter-room
http://localhost:4200/room/2


DHT: stop announcing the head blob

This should make 1 announcement per stream instead of 2.

stop announcing the head blob
stop searching for it
(wip) migration script to set all head blobs to should_announce=false

part of #3527 but probably doesn't close it (faster hash announcer and tracker to go)

Coverage remained the same at 69.782% when pulling 71dd299a5278cb08fa0d36322fd51c8c45b6e43a on stop_announcing_head_blob into c96d1d9c32337843239a8230244093fd19d79608 on master.


BUG: confusion matrix class label interval breaks with large sample size

Bug Description
Confusion matrix labels get misaligned with very large number of class labels.
This does NOT impact results (e.g., accuracy), only the labels — so plots need to be relabeled, e.g., for publication.
The issue seems to be that the tick intervals are being automatically set, but the tick labels are not being assigned the same interval: https://github.com/qiime2/q2-sample-classifier/blob/master/q2_sample_classifier/visuals.py#L129
Steps to reproduce the behavior
Make a confusion matrix with a large number of classes (example below has ~30)
Expected behavior
Label interval should match tick interval.
Screenshots

@nbokulich - @David-Rod, @ebolyen, and I attempted to recreate this issue:

It looks like the offsetting is no longer a problem (fixed upstream?). Can you confirm that this is the case (and if not, supply us with data that reliably reproduces the issue)? Thanks!

what are the actual tick labels in your example @thermokarst ?  It looks to me like you are not using a sufficiently large number of classes to trigger this problem (i.e., your tick interval is 1)

:+1:
@nbokulich, do you have test data you can share?
Also, I suspect we can do something like feature-table heatmap to address the issue.

Not fixed, check out viz below.
To reproduce:
import qiime2
from qiime2.plugins import sample_classifier as sc
import pandas as pd

mdix = [i for i in 'abcdefghijklmnopqrstuvwxyz']
md = pd.Series(mdix, index=pd.Index(mdix, name='sample-id'), name='class')
truth = qiime2.CategoricalMetadataColumn(md)
predictions = qiime2.Artifact.import_data('SampleData[ClassifierPredictions]', md)
cm = sc.actions.confusion_matrix(predictions, truth)
cm.visualization.save('test-matrix.qzv')

Note how the y-axis does not match up. Interestingly, the x-axis appears to have the correct interval + spacing, perhaps that is a clue?
I have an inkling the issue is in here, we may need to do something like ax.get_xticklabels to grab the correct labels instead of just grabbing all class labels:
https://github.com/qiime2/q2-sample-classifier/blob/2b2c0b5c4a41c95986edeb15557bfac8885dbc77/q2_sample_classifier/visuals.py#L106-L109


Does YouTubeCenter support for gaming.youtube.com ?

Does YouTubeCenter support for gaming.youtube.com ?
Auto-resolution setting may not work sometimes

It actually prevent 720p+ stream load here (just like Youtube live, a long-term bug which deserves some priority I'd say)


[ENG-795] log first user visit through consent client

Description
Music year: 1958

Updates @oaknational/oak-consent-client to 2.0.1

This makes a request to log the first visit by a user through the consent client which is why the new config userLogUrl was needed

Some refactoring to remove a provider that was only needed to make testing easier

How to test

Open the developer console on the network tab in an incognito session
Go to https://deploy-preview-2578--oak-web-application.netlify.thenational.academy
You should see a request to /v1/user
Reload the page
You should not see another request to /v1/user

Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

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


readOnly property doesnt work for radio-component.

Description of the bug
Read-only property for radio-komponent doesnt work. If you set radio-component to readonly it will still be open for editing, but wont write the information to the data-model.
Steps To Reproduce

Create radio-button.
Set readOnly property to true.
Test the component. Field will still be open for users to edit.
If you navigate to another page (another steg) then it will the remove what you have choosen on that radio-button.
Also check that it doesnt write information to datamodell.

Additional Information
No response

Please tag issue with: org/krt

@FTLems Da er dette på plass i siste alpha av app-frontend. Kunne du testet? Gi beskjed om det fungerer som tiltenkt eller om noe var uventet!


[Skype Web Control] Is showing postback in chat

System Information

SDK Language: .Net
SDK Version: 3.9.0
Development Environment:  App Service

Bot Info

Bot handle: AskMichelleDevelopment
App ID: cb285cec-f2cb-4043-9c23-2ac2ffae18ac
Connected channels: Skype, Facebook

Issue Description
We are using the Skype Web Control on our site. We use a fair amount of postback messages. It used to work fine, but sometime the last couple of days it started posting the postback message in the chat.

Steps to Reproduce the Issue

Create a bot with a postback action
Add the Skype Web Control to any page
Click the postback action

Expected Behavior
Expected the postback  to be sent  to the server
Actual Results
Postback text is posted in chat and sent back as plain text.

I'm having the same issue since the sdk for the webcontrol has changed to <script src="https://latest-swc.cdn.skype.com/sdk/0.24.37/sdk.js"></script>

I am experiencing the same issue. I tried to solve the problem temporarily by loading a previous version of the SDK - https://latest-swc.cdn.skype.com/sdk/0.12.2/sdk.js - however this does not seem to improve the situation.

@fms-santos @mminchev sorry for the issue! We are actively working on a fix for this bug and marked it as high priority. Please use https://swc.cdn.skype.com/sdk/v1/sdk.min.js moving forward to receive the latest update. I'll update this thread when we have deployed the fix.

Thanks @brene . We'll do as you say.
Also, a thing that is a bit annoying to me is the fact that we can't use different colors for the bot and the user's messages.

@fms-santos actually, you can completely overwrite the CSS of the control. (Just don't mess with the placement of the Skype logo because of legal reasons). Create a <div class="skype-chat' data-css-url="https://yourdomain.com/some.css"> and then you can choose whatever color you like.

Didn't know that! Thanks again @brene, much appreciated ;)

Thanks @brene! I am look forward to the fix as I am depending on Skype Web Control in order to complete a project for a client.

@mminchev @fms-santos We have rolled out the update to 100% it's fixed now

Thanks @brene ! I can confirm that my bot is working as it should again. ;)

@wacton can you close this ticket :-)

Thanks @brene !!
All good and working again. Appreciate it.


error Command "start-prod" not found.

2023-07-22 12:55:26 error Command "start-prod" not found.
2023-07-22 12:46:10 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What you want to "start-prod" and where you need on client or backend?

I solve this issue but now I am facing problem to how I deploy it, so
please help me
On Sat, 12 Aug, 2023, 6:38 pm Meet Kumar, @.***> wrote:

What you want to "start-prod" and where you need on client or backend?
—
Reply to this email directly, view it on GitHub
https://github.com/panshak/accountill/issues/39#issuecomment-1675904887,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZFK3Z6KST5SSHSMLPOZFHLXU553NANCNFSM6AAAAAA2TVMSGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Search does not work on Safari

Search works on all browsers except for Safari.
The following error is reported on form submission:
Unhandled Promise Rejection: TypeError: undefined is not an object (evaluating 'e.preventDefault')

Seems like checking the form submit handler is a good starting point.

The issue has been fixed, uglify-js was just missing the --webkit flag at image build time.


[release-1.22] etcd members fail to join cluster if image import or pull takes more than 5 minute

Backport fix for etcd members fail to join cluster if image import or pull takes more than 5 minutes to branch release-1.22

#4242
https://github.com/rancher/rke2/issues/349

Validated this is working in v1.22.3-rc4+k3s1


operators t8c (42.9.0)

Signed-off-by: esara<EMAIL_ADDRESS>

@esara please fix package file and put 42.9.0 version in stable channel (https://github.com/turbonomic/community-operators-prod/blob/t8c-operator/operators/t8c/t8c.package.yaml#L4)

@mvalarh sorry, fixed

/merge possible

/test 4.6-deploy-operator-on-openshift

/merge possible

/merge possible


x/build: improve trybot aliases for ppc64

I frequently see changes being made to code related to PPC64 which only use TRY=ppc64 for testing those changes. While I understand that this seems like the right default for code related to ppc64, this actually runs only the linux-ppc64 trybot, which tests only big endian and has limited linking capabilities (internal linking only, no cgo, no others like plug-ins or pie). So this selection is not the best default and does not provide good coverage for PPC64 testing.
I understand the naming is unfortunate because in the Go source code PPC64 usually used as a general term for code generation that applies to linux-ppc64, linux-ppc64le, linux-ppc64le-power9, and aix-ppc64.
Could we change the ppc64 alias in build/dashboard/builders.go to run the linux-ppc64le buildlet? This is really the most commonly used Power target for Go and provides the most linking capability. If someone REALLY wanted to run ppc64 big endian they could still use the linux-ppc64 alias.
I'd also like to have an alias for ppc64le on power9, maybe ppc64lep9.
I could make the change but I don't know how to test it. @dmitshur

I frequently see changes being made to code related to PPC64 which only use TRY=ppc64 for testing those changes. [...] Could we change the ppc64 alias in build/dashboard/builders.go to run the linux-ppc64le buildlet?

We currently have the following aliases related to ppc64:
"aix":            "aix-ppc64",
"linux-ppc64":    "linux-ppc64-buildlet",
"linux-ppc64le":  "linux-ppc64le-buildlet",
"ppc64":          "linux-ppc64-buildlet",
"ppc64le":        "linux-ppc64le-buildlet",

I think longer aliases need to be precise, and "linux-ppc64", "linux-ppc64le" should get the expected builder. But a short alias such as "ppc64" can be modified to point to the builder we think is most fitting. (Ideally, in the future, "ppc64" should expand to multiple builders to provide sufficient coverage, and people can use a longer alias if they want a very specific single builder.)
We should remove "ppc64le" to avoid or making it seem like "ppc64" gets the big endian one.

I'd also like to have an alias for ppc64le on power9, maybe ppc64lep9.

How about "linux-ppc64le-power9" so it's clear it's a specific target?
@laboger Do you mind sending a mail to golang-dev@ to notify people who rely on PPC64 aliases about this change and direct them to this issue if they want to express support for it or share concerns? It'd be nice to get some more feedback from others before we make a change to slowbot aliases.
Also CC @toothrot, @cagedmantis.

Thanks, I agree with all your suggestions, especially at some point to have one keyword to run all 4 variations. I will send a note to golang-dev to gather more opinions.

ppc64 alias will run the ppc64le buildlet
long names will specify the exact buildlet and there will be a new name for power9 that is easier to remember: aix-ppc64, linux-ppc64, linux-ppc64le,linux-ppc64le-power9

Sound good, thanks for doing that.
I've remembered that we have a test that ensures each GOOS/GOARCH term has some slowbot alias. But given how similar ppc64{,le} are, I think it's fine for us to modify the test so that a slowbot alias for "ppc64" also satisfies the requirement for "ppc64le".

Maybe we could add "ppc64x"?

Maybe we could add "ppc64x"?

And what would ppc64x run?

And what would ppc64x run?

BE and LE. Basically, *ppc64*.

BE and LE. Basically, ppc64.

Yes, that sounds great once we get multiple trybots to run for a single alias.

One other suggestion, although maybe this belongs in a different issue. If I have a CL and specify a new TRY list, it doesn't rerun the trybots unless the CL has changed since the last TRY (at least that appears to be the way it works.) It seems that if a new TRY list is specified it should rerun it?

I think it actually runs, but Go Bot doesn't print a message when it starts. It will print a message when it finishes.

Look at this CL: https://go-review.googlesource.com/c/go/+/266202. Shouldn't the message say which slowbots ran on the last one? Or maybe it is still using the first set of keywords which were not correct.

This appears to be issues #42084 and #38235. Please add a comment there so we have more data points.

How about these aliases:

ppc64 runs linux-ppc64le
ppc64be can be added to run linux-ppc64 (although this should be rarely used. aix-ppc64 will test ppc64 big endian.)
ppc64lep9 can be added to run linux-ppc64le-power9osu
linux-ppc64le-power9 can be added to run linux-ppc64le-power9osu

Right now we have names with linux- and short names without linux-.

ppc64 runs linux-ppc64le

I think this is confusing, as the GOARCH of big-endian PPC64 is actually ppc64. In all other cases, if an alias matches a GOARCH, it runs that GOARCH. This would be weird.

After moving the LUCI the names are selected so this is no longer a problem.


App Store rejection for not including NSPhotoLibraryUsageDescription

I have no use of user's photo library into my app yet my app got rejected.
I created a build of my app and submitted it to iTunes Connect and got the following rejection a few minutes later in an automated email:
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data.
I was able to track down the cause of the rejection to this method into UIImagePickerController.swift file:
public convenience init(source: UIImagePickerControllerSourceType = .photoLibrary,                             allow: UIImagePickerController.MediaFilter = .image,                             cameraOverlay: UIView? = nil,                             showsCameraControls: Bool = true,                             didCancel: @escaping ( _ picker: UIImagePickerController) -> Void = dismissFromPresenting,                             didPick: @escaping (_ result: UIImagePickerController.Result, _ picker: UIImagePickerController) -> Void) {...
I take it that an app that makes any UIImagePickerController call (even if it’s not actually requesting access to the user’s photo library) must include an entry for NSPhotoLibraryUsageDescription in its Info.plist.

Good find. This is high priority. Will have some sort of fix shortly.

@bhulkuKs As an immediate work-around to have your app submission go through, you can put the following description for Privacy - Camera Usage Description:
A 3rd party library offers a convenience extension for UIImagePickerController, but no user's photos are being used in this application.
This should suffice because they are more concerned with you knowing how sensitive data is being used. This satisfies the requirement to

provide a transparent and meaningful usage description.

I will leave the issue open until a more robust solution is released.


brew support

可否考虑支持 brew 安装……

From Homebrew's doc:

Don’t make your formula build an .app (native OS X Application); we don’t want those things in Homebrew. Make it build a command line tool or a library.

brew cask ?

@ripples-alive 赞，我去研究一下。

@ripples-alive 出了点问题
brew cask install electronic-wechat
==> Downloading https://github.com/geeeeeeeeek/electronic-wechat/releases/downlo
Already downloaded: /Library/Caches/Homebrew/electronic-wechat-1.1.1.tar.gz
==> No checksum defined for Cask electronic-wechat, skipping verification
Error: It seems the symlink source is not there: '/opt/homebrew-cask/Caskroom/electronic-wechat/1.1.1/Electronic WeChat-darwin-x64/Electronic WeChat.app'

我的配置是这样的：
cask 'electronic-wechat' do
  version '1.1.1'
  sha256 :no_check

  url 'https://github.com/geeeeeeeeek/electronic-wechat/releases/download/v1.1.1/mac-osx.tar.gz'
  name 'Electronic WeChat'
  homepage 'https://github.com/geeeeeeeeek/electronic-wechat'
  license :mit
  app 'Electronic WeChat-darwin-x64/Electronic WeChat.app'
end

@geeeeeeeeek 按这意思，应该要加checksum吧

(Homebrew-Cask maintainer here)
Merged in https://github.com/caskroom/homebrew-cask/commit/b4b67bd999339d504ebeb49c6250eadd4f934ad1
brew cask install electronic-wechat

@adidalal Great! Sorry I forgot to fix that pull request for my procrastination.


Don't copy over metric filters to reference queries. Use left join when adding references to result.

Coverage increased (+0.005%) to 92.317% when pulling bb66a68b586abe89a9b236caf0bb1651b7ea6f3a on gl3nn:no-metric-filters-in-references into 183870c4aa48a7e5f9278fb388be15139dc1852c on kayak:master.


Detailed knex/driver errors passed through in production

Platform: macOS 10.12
Database: pg/postgres 9.6
Lux Version: 1.1.7
Node Version: 7.9.0

When saving a model via lux which does not adhere to the database constraints, knex/pg might throw an error like below:
detail: "update "users" set "email" = $1, "updated_at" = $2 where "id" = $3 - duplicate key value violates unique constraint "users_email_unique"" together with a 500 Internal Server Error
In the current situation these detailed messages are also passed through in the response in production mode. This is unwanted behaviour.

What is the acceptable solution here? Removing the "detail" for 500 messages, or would there be more cases where detail shouldn't be present in production?

I'd say this, ideally IMO, should be configurable similar to a log level.
A high level might return what is returned today,
A medium might just omit the "detail" field and
A low might omit both the detail and the title fields only return ing a status
A secure might just default to a blanket 'unauthorized' message or something...
Just some thoughts...

It should indeed be coupled to the log level. Why would you wan't to omit title/status though? That's the only way to convey what went wrong or right.

@nickschot - To be clear, I don't think it should be 'coupled to' but configured 'similarly to' the log level.  I would likely want very different internal logging settings vs how verbose I want external errors to be.

Why would you want to omit title/status though?

Depending on how secure I want my application to be would, in my mind, dictate how little detail I want to return to a user (or potential hacker) of my api when an error occurs.  If I have a very sensitive set of data I might not want to return any clues for a potential evil doer that might help clue them into how they can adjust their attack vector.   it would also likely depend on if they were authenticated or not.  I would feel more ok with returning more details to an authenticated request vs an unauthenticated one.
Some of this is obviously an implementation detail in how I setup my authentication of the api but I think it does still relate here.

Just adding my $0.02 here. I think that log levels and error responses shouldn't be coupled together in any way. IMO, you shouldn't be able to configure error responses. It's never a good idea to leak SQL statements in error messages in production.
tldr;
You shouldn't have to think about the security risks of error messages beyond making sure your production application is running in production mode.

What is the acceptable solution here? Removing the "detail" for 500 messages, or would there be more cases where detail shouldn't be present in production?

I think a solid solution for common errors would be mapping knex error types to strings for substitution with the original error message and/or stack trace when running in production mode. There could also be a "catch all"  default error message (something like "An unknown error occurred.") if a mapping is not found.


DotNetty

What's the Product's Name?
DotNetty
Describe the product in a single sentence.
"DotNetty is a port of Netty, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients."
When was the product launched? Provide a specific date, if possible.
~September 2015 (Earliest Nuget Publish date I could find)
When was the product discontinued? Provide a specific date, if possible.
A github issue was filed on August 14th, 2020 asking whether the project is dead without a confirmed response as of the date of this obituary report (Oct 20, 2023): https://github.com/Azure/DotNetty/issues/542
What type of product was it? App, Service, OS, or Hardware?
App I guess?

I would not insert this framework because it seems too "small". In particular:

It wasn't directed to end user
it doesn't have a website
there isn't a page on wikipedia
there is not any reference on Microsoft press release channels (blog, news ,.. ).

The most I found is https://devblogs.microsoft.com/dotnet/on-net-2122016-aaron-stannard/ ...
However, thanks for the contribution.


Chapter 10: Incorrect file references in unattended-upgrades example.

Hi,
I have noticed that in “Chapter 10 - Server Security and Ansible”, in the section “Automating updates for Debian-based systems” the task example refers to the template file 10periodic.
  with_items:
    - 10periodic
    - 50unattended-upgrades

However the explanation about the contents of the template file below the task example refers to 20auto-upgrades.
# File: /etc/apt/apt.conf.d/20auto-upgrades

Therefore I believe the task example should be modified to use 20auto-upgrades instead of 10periodic.
  with_items:
    - 20auto-upgrades
    - 50unattended-upgrades

Regards
Graham

You're quite right! I'll have this fixed in the next version of the book, and I'll also add those lines of code to this book's repository since they're not in the 'security' example yet.


Account name is no longer shown in the status bar

As of today, the AWS status bar is no longer showing the name of the account I'm currently in. It only shows role/username, for example<EMAIL_ADDRESS>Changing the colour of the status bar according to the account name has also stopped working, for example with this config:
{
  ".*production.*": "red"
}

Is this happening to anyone else? Does anyone have a fix?

i am also experiencing this issue, but have not yet updated Chrome to the latest version.  i am still on 112.0.5615.49 (Offizieller Build) (x86_64).
maybe AWS changed something in the console page (or API), that the plugin uses to obtain that information?

i am also experiencing this issue, but with the plugin on Firefox (version 112.0.2) - so i guess the issue is not browser-specific.
maybe AWS changed something in the console page (or API), that the plugin uses to obtain that information?

Thank you for the information. I also realized this problem today. So I will investigate and fix this issue by the weekend.

I'm having the same issue in Chrome. I followed up by testing the Firefox version of the extension, and it's not working there either.
Since it's broken in both browsers (and the code in the Firefox directory hasn't changed since 2021), I'm inclined to agree with @MrFishFinger about this (possibly) being due to a change/issue on AWS's side.
This may be related to the API changes associated with AWS migrating from AWS SSO to AWS IAM Identity Center:

https://aws.amazon.com/about-aws/whats-new/2022/09/aws-iam-identity-center-apis-manage-users-groups-scale/
https://aws.amazon.com/blogs/security/get-ready-upcoming-changes-aws-single-sign-on-user-sign-in-process/

It worked also with AWS IAM Identity Center until last week, so I would guess it's just once more a small change in their UI which breaks things here :disappointed: (shame on AWS, not @yaggytter)

Just a note, I access multiple accounts at the same time using Firefox Containers and I'm seeing the issue intermittently in different sessions and/or AWS accounts. Sometimes a session/account combination will show the account name, and other session/account combinations won't. I'm guessing this is because of a change to the AWS console that's being deployed in an A/B fashion against cookies and/or accounts, so ideally if any fix that's implemented can be backwards-compatible that would be great.

I've fixed this and submitted it as version 1.3.1 to the Chrome Web Store. Currently, it's under review. Please wait a while until the review is complete and it's published. Actually, Firefox version is already released. Thank you for your information!
@calebplum @hellsp @MrFishFinger @jr-ri @djablonski-moia


Fix link

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


WHOIS exited with error 2

Hi,
Running domain checks on multiple different domains including on the commandline from the zabbix server and i get the same response each time, 'UNKNOWN ; WHOIS exited with error 2'.
I have used "", whois.godaddy.com and whois.verisign-grs.com as {$WHOIS_SERVER} including using the 2 whois urls from commandline with the -s switch and getting the same error message for any URL i try to test.
please help

Hi again,
can you take control the below steps?

Is Whois installed the server ? You can test "whois google.com" with command. You shold display true value.
If you get en error "whois google.com" command such as "timeout" , open firewall "port 43/tcp"
You can try this topic for zabbix new versions;
https://github.com/a-stoyanov/zabbix-domain-expiry/issues/4
You can try "{$WHOIS_SERVER}" macros value such as *  ""   *.  ""=Default whois server.


Suggestion: Make allow global event handlers to be FnMut and not just Fn

If there's some data in the closure for a global event handler that needs to be mutated it's a real pain to make that happen when you're using an Fn since Fns aren't allowed to mutate their closure.
It generally involves doing a mem::transmute::<&mut _, *mut _> and back.

I would think it'd involve a Rc+ReffCell rather than a transmute, which could lead to UB.
As for the callbacks, they are Fn because it's possible, from the callback, to access itself (since it has access to &mut Cursive. This is only safe if the callback is not borrowed mutably, as it would if it was FnMut.
That being said, it's pretty easy to wrap a FnMut on a RefCell and stick that in a Fn, you just lose reentrance. I updated add_glibal_callback to do this for you.

Released as part of 0.9.0.


Add Daly protection notifications

The Daly BMS protection notifications have not been implemented in the current release

Fixed in #90


better way to get errors out of acme client

The AcmeClient.validate method has been returning an 'invalid' message.
This left me a little perplexed as I had no idea why the request was invalid.
In digging into the code I realised the problem was a firewall configuration.
The problem is that currently there is no way to get the 'root' error out of acme client.
I had a play with the response object returned from the second call to Dil().post in AcmeClient.validate and found that
the error was contained in:
response!.data['challenges'][0]['error']['detail']

"<IP_ADDRESS>: Fetching http://xxxxxx/.well-known/acme-challenge/-F7yZhEiUqqRgra8wcEaLUG01jq_A3TH4RbBJ63Q-JU: Timeout d…"

So this error makes it fairly clear what the problem is but it isn't very friendly to make the user dig through code to determine the problem.
I had a look at adding a field 'lastResponse' to the AcmeClient which exposes the error but it isn't an adequate solution as you have to know to dig into the 4 levels of the response map.
Is there a better solution for this?

So it turns out I had already raised an issue.
I'm not familiar enough with the RFC to understand all of the places we need to extract errors from.
We also need to consider how we surface those errors.
I would normally throw a custom exception but the current code based doesn't really use exceptions.
Suggestions?

This is probably the last big issue that needs to be resolved to make the package perfect.
I'm not going to have the time to look at this any time soon so if anyone else wants to have a crack at it.


TP - ability to open DS/Server configs in separate window

For DS and Server items in the new Traffic Portal, I would like to have the ability to open the item in a separate window/tab (i.e. via right-click). Would save time when viewing or editing multiple items, as there would be no need to reload the item list each time.

I think there is a link now in TP Delivery services that opens a new window/tab for profiles


About : y = net(x) ,Not enough values to unpack (expected 2, got 0) ?

Python 3.5.2 |Anaconda     4.2.0 (64-bit)|
torch                                   0.4.0
torchvision                          0.2.1
when i run the program test.py,there is some mistake as follow:
C:\Users\Anaconda3\python.exe D:/pytorch_ssd/test.py
D:\pytorch_ssd\ssd.py:34: UserWarning: volatile was removed and now has no effect. Use with torch.no_grad(): instead.
self.priors = Variable(self.priorbox.forward(), volatile=True)
D:\pytorch_ssd\layers\modules\l2norm.py:17: UserWarning: nn.init.constant is now deprecated in favor of nn.init.constant_.
init.constant(self.weight,self.gamma)
Finished loading model!
Testing image 1/4952....
Traceback (most recent call last):
File "D:/pytorch_ssd/test.py", line 97, in
test_voc()
File "D:/pytorch_ssd/test.py", line 94, in test_voc
thresh=args.visual_threshold)
File "D:/pytorch_ssd/test.py", line 56, in test_net
y = net(x)      # forward pass
File "C:\Users\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "D:\pytorch_ssd\ssd.py", line 103, in forward
self.priors.type(type(x.data))                  # default boxes
File "D:\pytorch_ssd\layers\functions\detection.py", line 54, in forward
ids, count = nms(boxes, scores, self.nms_thresh, self.top_k)
ValueError: not enough values to unpack (expected 2, got 0)
Process finished with exit code 1
why ?

i'm so sorry about it because the reason is torch 0.4

I have meet the same problem, how do you slove it?

@yingdiLee see (https://github.com/amdegroot/ssd.pytorch/issues/154#issuecomment-384856547)


log() function breaks for big floats

It seems like that the cmath.inl::get_fast_converge_params algorithm is using an integer intermediate (size_t) representation, where not all floats can be represented with.
    template<typename Float>
    static constexpr auto get_fast_converge_params(Float* const A, std::size_t* const n, Float x)
        -> void
    {
        auto _x = static_cast<std::size_t>(trunc(x));
        auto _n = static_cast<std::size_t>(logi_helper<10>(_x));
        *n = _n;
        *A = x / pow_helper(10, _n);
    }

The following code will lead to compile-time errors (compiled with gcc 10.3.0):
static_assert(smath::log2(1.0e8) < 27, "");

/workspace/test/static_math(master*) # make
Consolidate compiler generated dependencies of target test-cmath
[  6%] Building CXX object CMakeFiles/test-cmath.dir/test/cmath.cpp.o
/workspace/test/static_math/test/cmath.cpp: In function ‘int main()’:
/workspace/test/static_math/test/cmath.cpp:132:38: error: non-constant condition for static assertion
132 |     static_assert(smath::log2(1.0e8) < 27, "");
|                   ~~~~~~~~~~~~~~~~~^~
/workspace/test/static_math/test/cmath.cpp:132:30:   in ‘constexpr’ expansion of ‘smath::log2(1.0e+8)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:664:38:   in ‘constexpr’ expansion of ‘smath::detail::log2_helper(x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:361:27:   in ‘constexpr’ expansion of ‘smath::detail::log2_helper((std::is_floating_point(), std::integral_constant<bool, true>()), x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:354:35:   in ‘constexpr’ expansion of ‘smath::detail::logf_helper(x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:318:49:   in ‘constexpr’ expansion of ‘smath::detail::fast_converge_log<0>::compute(x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:266:37:   in ‘constexpr’ expansion of ‘smath::detail::get_fast_converge_params((& a), (& n), x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:251:28:   in ‘constexpr’ expansion of ‘smath::detail::pow_helper<int, long unsigned int>(10, _n)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:54:45:   in ‘constexpr’ expansion of ‘smath::detail::pow_helper<int, long unsigned int>((x * x), (exponent / 2))’
/workspace/test/static_math/include/static_math/detail/cmath.inl:54:45:   in ‘constexpr’ expansion of ‘smath::detail::pow_helper<int, long unsigned int>((x * x), (exponent / 2))’
/workspace/test/static_math/include/static_math/detail/cmath.inl:54:45:   in ‘constexpr’ expansion of ‘smath::detail::pow_helper<int, long unsigned int>((x * x), (exponent / 2))’
/workspace/test/static_math/test/cmath.cpp:132:38: error: overflow in constant expression [-fpermissive]
make[2]: *** [CMakeFiles/test-cmath.dir/build.make:76: CMakeFiles/test-cmath.dir/test/cmath.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:396: CMakeFiles/test-cmath.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

Changing this to
    template<typename Float> static constexpr auto get_fast_converge_params(Float* const A, std::size_t* const n, Float x)
        -> void
    {
        auto _x = static_cast<std::size_t>(trunc(x));
        auto _n = static_cast<std::size_t>(logi_helper<10>(_x));
        *n = _n;
        *A = x / pow_helper<int long long>(10, _n);
    }

will fix this issue for the particular case, but for values > std::numeric_limits<size_t> this will break.
static_assert(smath::log10(2.0e20) > 0, "");  leads to:

/workspace/test/static_math(master*) # make
[  6%] Building CXX object CMakeFiles/test-cmath.dir/test/cmath.cpp.o
/workspace/test/static_math/test/cmath.cpp: In function ‘int main()’:
/workspace/test/static_math/test/cmath.cpp:133:40: error: non-constant condition for static assertion
133 |     static_assert(smath::log10(2.0e20) > 0, "");
|                   ~~~~~~~~~~~~~~~~~~~^
/workspace/test/static_math/test/cmath.cpp:133:31:   in ‘constexpr’ expansion of ‘smath::log10(2.0e+20)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:525:39:   in ‘constexpr’ expansion of ‘smath::detail::log10_helper(x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:278:24:   in ‘constexpr’ expansion of ‘smath::detail::log10_helper((std::is_floating_point(), std::integral_constant<bool, true>()), x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:273:31:   in ‘constexpr’ expansion of ‘smath::detail::logf_helper(x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:262:45:   in ‘constexpr’ expansion of ‘smath::detail::fast_converge_log<0>::compute(x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:219:33:   in ‘constexpr’ expansion of ‘smath::detail::get_fast_converge_params((& a), (& n), x)’
/workspace/test/static_math/include/static_math/detail/cmath.inl:204:45:   in ‘constexpr’ expansion of ‘smath::trunc(x)’
/workspace/test/static_math/test/cmath.cpp:133:40: error: overflow in constant expression [-fpermissive]
/workspace/test/static_math/test/cmath.cpp:133:40: error: overflow in constant expression [-fpermissive]
/workspace/test/static_math/test/cmath.cpp:133:40: error: overflow in constant expression [-fpermissive]
make[2]: *** [CMakeFiles/test-cmath.dir/build.make:76: CMakeFiles/test-cmath.dir/test/cmath.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:396: CMakeFiles/test-cmath.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

As mentioned in #27 I don't maintain this project anymore: this kinds of errors keep piling up, I don't have the necessary skills to fix them, and whenever I dare to look back at the library I keep finding new issues. Sorry about that.

As mentioned in #27 I don't maintain this project anymore: this kinds of errors keep piling up, I don't have the necessary skills to fix them, and whenever I dare to look back at the library I keep finding new issues. Sorry about that.

No need to apologize, I fully understand your point. I was evaluating using this library to bridge the time until it's part of the standard (hopefully c++23 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p0533r8.pdf).
From just inspecting the github page it seems everything works as intended and is tested (no open bugs/issue concerning functionality), and is referenced by some stack overflow posts. Hopefully, this issue will make it easier for others to evaluate, whether to use this library or not.
I'd encourage you to post your already know issues at least in #27, perhaps then a potential contributor/maintainer has a starting point to investigated/get started. Thanks for you work!


Redesign the life bar and HUD

The lifebar is currently a bit small and part of the game world (it gets deformed by deformation shaders and effects). It could use a nicer design, larger, and separate from the player ship.
See #26

Closed by merging the ui-redesign branch.


Order service form shows

I'm trying to deploy a heat stack by ordering from the service catalog. In the order form the Tenant dropdown shows

@mcornea Please make sure you have properly imported Cloud/Orchestration/Operations/Methods/Available_Tenants into automate name space.

Other than this, I will also add some prevention code.


Bugs related to modeling exercises, found in PR #2135

Describe the bug

This is a ticket which summarizes the errors and bugs related to modeling exercises which were found in PR #2135
I faced a problem when assessing modeling exercises.

Happened after I assessed a use-case model and clicked on the submit button on the page. Did not look further into the issue and could not reproduce it
Another issue that happened to me, which happens after the due date passed. The size of the container which includes apollon becomes too small, see screenshots, probably unrelated to the PR

Also had a problem with importing exercises which where created from Apollon:

Environment

 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

Additional context

Output in Web Console

  [REPLACE THIS WITH YOUR INFORMATION]

This happened when I tested another PR. THis issue should also be fixed in this PR


FancyZones "forgetting" selected layout

Microsoft PowerToys version
0.69.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
After turning on the O.S., the selected layout is reset to default

Every time I have to select my custom layout again.

✔ Expected Behavior
I expect the app to remind the selected layout I'm working with.
❌ Actual Behavior
I have to select the layout I want to work with, every time I turn on the O.S.
Other Software
No response

I also have this issue. I did not have a problem with it until I did a PC reset a couple of weeks ago.

same issue

/dup https://github.com/microsoft/PowerToys/issues/18185


[Synapse] TestSparkSessionJob failing in nightly runs

Synapse runs are failing with:

Error message
Session: 4 did not return success. Current job state: dead. Actual result: Failed. Error (if any): Azure.Analytics.Synapse.Spark.Models.SparkServiceError
Expected: True
But was:  False
Stack trace
at Azure.Analytics.Synapse.Spark.Tests.SparkSessionClientLiveTests.TestSparkSessionJob() in /Users/runner/work/1/s/sdk/synapse/Azure.Analytics.Synapse.Spark/tests/SparkSessionClientLiveTests.cs:line 54
at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter1.BlockUntilCompleted()    at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)    at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func1 invoke)
at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.b__0()
at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1424892&view=results

@jsquire for notification.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Synapse:0.40017816,Service Bus:0.34875646,Network - Front Door:0.083054766'

@v-xuto, @pshao25 is taking ownership of this library.  Thanks!

Given the age of this issue, I'm going to close it as stale.  If tests continue to fail, please file a new issue.

This seems a random issue and cannot be reproed. It does not fail in the following builds.


SSH on Windows with OpenSSH failing

Hi,
I've spent the last few hours trying to get this working. I've installed OpenSSH on a windows machine, and that all works perfectly when manually adding keys into authorized_keys, etc.
Going through the Gogs UI and adding the same key produces this file:
command="c:/Gogs/gogs.exe serv key-1 --config='c:/Gogs/custom/conf/app.ini'",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa */MyKey/*
Now, running the command: c:/Gogs/gogs.exe serv key-1 --config='c:/Gogs/custom/conf/app.ini' on the remote machine works fine, giving the welcome message "Hi there, you've successfully authenticated", etc.
sshing into and pushing both fail:
$ ssh -v<EMAIL_ADDRESS>OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 22.
debug1: Connection established.
debug1: identity file /c/Users/Rob/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/Rob/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.1p1 Microsoft_Win32_port_with_VS
debug1: match: OpenSSH_7.1p1 Microsoft_Win32_port_with_VS pat OpenSSH* compat 0x04000000
debug1: Authenticating to <IP_ADDRESS>:22 as 'rudman'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client<EMAIL_ADDRESS><implicit> none
debug1: kex: client->server<EMAIL_ADDRESS><implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:IM2wIjS1RZ78HmZsBDQmE4H2Ju/OsH9nDx0jMQbtUls
debug1: Host '<IP_ADDRESS>' is known and matches the ECDSA host key.
debug1: Found key in /c/Users/Rob/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /c/Users/Rob/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to <IP_ADDRESS> ([<IP_ADDRESS>]:22).
debug1: channel 0: new [client-session]
debug1: Requesting<EMAIL_ADDRESS>debug1: Entering interactive session.
debug1: client_input_global_request: rtype<EMAIL_ADDRESS>want_reply 0
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
PTY allocation request failed on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype<EMAIL_ADDRESS>reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to <IP_ADDRESS> closed.
Transferred: sent 3448, received 2872 bytes, in 0.1 seconds
Bytes per second: sent 30024.1, received 25008.5
debug1: Exit status 0

There are no logs whatsoever output from gogs, and there are no logs in windows event viewer for OpenSSH (and none in the log.txt file either).
Any ideas?

Thanks your feedback!
So bad I can't see any obvious reason why connection fails.
But for special care of Windows users, if you're running version higher than 0.8, you can use this config option to enable builtin SSH server of Gogs which should work very smoothly.

Thank you - that works perfectly now. I am not sure if it's an issue, but sshing (not pushing with git) causes the process to hang (instead of showing the MOTD/Greeting). Minor issue though, since it works perfectly with git. Thanks! :+1:

sshing (not pushing with git)

How to reproduce this?

@Unknwon mostlikely do doing ssh git@gogs-host :trollface:

Ah... what is the error though?

@Unknwon There is no error. It gives a warning about 'PTY allocation request failed on channel 0' and then ends the connection. Removing the no-pty gets rid of the warning, but the connection immediately closes. I wasn't able to find any logs or output about what went wrong, the above verbose ssh is as much information as I was able to get.

@rjrudman you should looks at gogs backend console see if any log prints (upgrade to latest version first master). If no log, which means the request never arrives to Gogs...

@Unknwon There was no output at all on the gogs console (using the latest binaries - amd | ZIP w/ mws). I wasn't able to find any logs, unfortunately. Though it does definitely seem that it never executed the gogs.exe

Well... I'm lost..


Support EditorConfig

http://editorconfig.org/
...consistent coding styles between different editors and IDEs... ...file format for defining coding styles...

:+1:

I think this indeed should be very useful. Is it "easy" to have per open file settings of these things in Spyder? (I have not started to look at the code, but I guess it is a big difference if these settings are already supported on a per file basis or if one needs to implement that as well.)

I suppose that open file should have some data model in Spyder sources, but I don't see anything close from source filenames - https://github.com/spyder-ide/spyder/tree/master/spyder
I remember there was something from Qt about Editor class or something like this. Not exactly a file model, but could be a pointer. In fact, a Spyder class diagram would be helpful to solve this.

I'm not a Spyder user but am involved with EditorConfig and would love to see Spyder included in the list of supported editors either with built-in support of via a separate plugin.
I don't plan to work on this issue myself, but I wanted to add some extra context for others that might work on this in the future. I briefly spoke to @CAM-Gerlach about this issue at PyCon and he noted a few things that may be relevant:

All the current official EditorConfig properties are probably fairly easy to support, except maybe tab_width
Since this issue was originally opened the plugin system has been overhauled a bit and writing a plugin that uses the editorconfig-core-py to configure these options based on .editorconfig settings should (in theory) be about as straightforward as writing the Gedit plugin was
This functionality should probably be part of Spyder so a pull request to modify the editor plugin (which from my understand, is a "plugin" that controls much of Spyder's core functionality) may be just as appropriate as making a separate plugin