Tests should verify if a certificate is valid

Is your feature request related to a problem? Please describe.
At the time being Issuers tests are relying on what developers expect on how the contents should look like.
Describe the solution you'd like
It should be considered the addition of a further step verifying if a certificate is valid as a certificate itself, like one would do with openssl.
This can be done, as it is for some other tests in this same project, using Go's native package x509: https://golang.org/pkg/crypto/x509/#example_Certificate_Verify
Environment details (if applicable):

Kubernetes version (e.g. v1.10.2): v1.16.9
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): kind
cert-manager version (e.g. v0.4.0): v1.0.2
Install method (e.g. helm or static manifests): helm

/kind feature

We do have tests that act on this level already, notably during our end-to-end suite: https://github.com/jetstack/cert-manager/blob/b6c3bc4b466c075c027661806bb91a17fb0b4c5d/test/e2e/framework/helper/certificates.go#L97-L100
There's also various other checks that also ensure that the certificate is valid.
If there's some additional test cases that you think we should include however, that'd be fantastic 😄 but I don't think there's anything actionable as part of this issue at least.
/area testing
/remove-kind feature
/kind cleanup


Brew install has Error: Calling <<-EOS.undent is disabled!

Hi, just reporting brew install warning I got just now :) wish I understand how to fix ...
==> Tapping kylef/formulae
Cloning into '/usr/local/Homebrew/Library/Taps/kylef/homebrew-formulae'...
remote: Counting objects: 7, done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 7 (delta 0), reused 3 (delta 0), pack-reused 0
Unpacking objects: 100% (7/7), done.
Tapped 3 formulae (33 files, 22.8KB)
==> Installing swiftenv from kylef/formulae
==> Downloading https://github.com/kylef/swiftenv/archive/1.3.0.tar.gz
==> Downloading from https://codeload.github.com/kylef/swiftenv/tar.gz/1.3.0
######################################################################## 100.0%
Error: Calling <<-EOS.undent is disabled!
Use <<~EOS instead.
/usr/local/Homebrew/Library/Taps/kylef/homebrew-formulae/Formula/swiftenv.rb:18:in `caveats'
Please report this to the kylef/formulae tap!
Or, even better, submit a PR to fix it!

Thanks for reporting, I've fixed this in https://github.com/kylef/homebrew-formulae/commit/31cee9878674ec2db35dd502a49b00c0613db27d.
It does say error but it seems to actually install swiftenv fine, just didn't print out the caveats which I'll mention here incase you missed them:
==> Caveats
To use Homebrew's directories rather than ~/.swiftenv add to your profile:
  export SWIFTENV_ROOT=/usr/local/var/swiftenv

To enable shims, add the following to your profile:
  if which swiftenv > /dev/null; then eval "$(swiftenv init -)"; fi


fix: ensure users don't accidentally send stamped utxos

Try out this version of the Hiro Wallet - download extension builds.

WIP. Had a quick look at how stamps work.
There's a single API with a 6MB response, and not sure if that's a bit too heavy/big to cache. Either way, wanted to look at how we might filter out stamped utxos from our coin selection, as a preventative measure ahead of any feature support.

LGTM, you wanting to open/merge this?

@kyranjamie I think it would help to work off this for adding Stamps to collectibles, what are next steps to get this merged?

Stamps are not on taproot utxos? 🤔

Hi, this is Mike from Bitcoin Stamps.
We now have Webservice documentation and a number of endpoints that can be queried. Hopefully this will make integration on your end smoother.
https://github.com/hydren-crypto/stampchain/blob/main/docs/api.md
If you have any questions please feel free to reach-out. I'm @mikeinspace on Twitter and Telegram.
We can also schedule a call with our dev team if you would find value in that.
Thanks again.
Mike.


Find nested typealiases and properly assign parent types

https://github.com/fdiaz/SwiftInspector/pull/82 only got us part of the way there.
Best reviewed with whitespaces changes turned off.

Merging! If Francisco has comments I'll happily put up a follow-up PR


Please provide a feature flag to use webpki-roots rather than native roots

Feature Request
Crates
tonic
Motivation
I'd like to build a static binary, which will be deployed to a system that doesn't have any system TLS roots. I'd like to compile in webpki-roots, rather than using rustls-native-roots.
Proposal
I'd love to have a feature flag (something like tls-webpki-roots) that enables the use of webpki-roots rather than rustls-native-roots. That feature flag could enable an optional webpki-roots dependency, and feed the webpki-roots certificates into rustls.
I'd be happy to supply a pull request implementing this proposal, if it sounds like a reasonable approach.

I'm currently working around this by doing the following:
        let mut rustls_config = rustls::ClientConfig::new();
        rustls_config
            .root_store
            .add_server_trust_anchors(&webpki_roots::TLS_SERVER_ROOTS);
        rustls_config.alpn_protocols = vec![b"h2".to_vec()];
        let tonic_tls_config = tonic::transport::ClientTlsConfig::new().rustls_client_config(rustls_config);

This seems cumbersome, requires matching the version of rustls used by tonic and the version of webpki-roots used by rustls, and requires dealing with internal details like setting alpn_protocols.

We actually do the exact same thing at Embark so I think it makes to add this to tonic.
@LucioFranco what do you think?

I wrote a PR for this: https://github.com/hyperium/tonic/pull/660

Closing this since https://github.com/hyperium/tonic/pull/660 has been merged.


remove connection options setup in factory, add docs

Coverage decreased (-1.2%) to 98.81% when pulling 05dfe349e42a7a296d193da34be1b85875544d47 on updates into e738bbfebe65bcb311603e3d19ac3b8a523c1121 on master.

Coverage decreased (-1.2%) to 98.81% when pulling 7896ce4825d2deb2ffea52d7b0bea669e29ab5cf on updates into e738bbfebe65bcb311603e3d19ac3b8a523c1121 on master.

I'd merge but not allowed on phone when some Checks failed ...


jsPDF addHTML is rendering black pages in iPad for more than 7 pages. works in windows.

Thank you for submitting an issue to jsPDF. Please read carefully.
Are you using the latest version of jsPDF? No [1.3.5]
Have you tried using jspdf.debug.js?
Steps to reproduce
containers = html.querySelectorAll('.container'); [has about 8 reports - some of the reports have 3 pages]
var recursiveAddHtml = function () {
if (i < containers.length) {
pdf.addHTML(containers[i], 10,10, options, function () {
i++;
if (i < containers.length)
pdf.addPage();
recursiveAddHtml();
});
}
else {
var openPdfUrl = pdf.output('dataurlstring');
var openPdfUrlSplit = openPdfUrl.replace('data:application/pdf;base64,', '');
var openPdfLink = document.createElement('a');
openPdfLink.href = 'openpdf://data=' + openPdfUrlSplit;
openPdfLink.click();
iframe.parentNode.removeChild(document.getElementById(iframeId));
}
Ideally a link too. Try fork this http://jsbin.com/rilace/edit?html,js,output
What I saw
if we choose 6 reports or lesser - there is no problem in rendering the pdf in iOS. but, for more pages/reports - it is rendering a black screen with 8 pages.
What I expected
How many ever reports I choose, I expect the pdfs to be rendered correctly.

Sry, but  I really dont know how we can even debug this wihtout debug information.

There is a 2500 pixel limit in the iOS Safari Browser I think...

I have a similar problem where on ios devices the pdf is printed completely black. When I open the pdf with illustrator I see that my content is actually inside the pdf but there is an additional black overlay on it covering the whole pdf.
Also my content is shown only half, but I'm guessing that is because the viewport of the device.
Any Ideas on that black overlay? I'm using html2canvas with jsPDF


constexpr expansion vs2015

I have the following constexpr values defined:
template <typename T> struct AngleRatios
{
    static constexpr T Radians = T(1);
    static constexpr T Degrees = MathValues<T>::Pi2 / T(360);
    static constexpr T Gradians = MathValues<T>::Pi2 / T(400);
};

The following check will fail saying that AngleRatios::Radians equals 0.0f
CHECK(AngleRatios<float32>::Radians == Approx(1.0f));

It will however be correct when I place braces around the expression like so:
CHECK( (AngleRatios<float32>::Radians == Approx(1.0f)) );

This will log 0.0f
INFO(AngleRatios<float32>::Radians)

This will log the correct value
INFO(1.0f * AngleRatios<float32>::Radians)

It only seems to happen with floating point values, integers expand to the correct values
Tested with Visual Studio 2015 RC.
Here is a minimal example of the bug:
#define CATCH_CONFIG_MAIN
#include <catch.hpp>

template <typename T> struct AngleRatios
{
    static constexpr T Radians = T(1);
};

TEST_CASE("constexpr")
{
    INFO(AngleRatios<float>::Radians);
    INFO(AngleRatios<float>::Radians * 1.0f);

    CHECK(AngleRatios<float>::Radians == Approx(1.0f));
    CHECK((AngleRatios<float>::Radians == Approx(1.0f)));
}

What happens if you print the items via std::cout? IMO, sounds like a VS bug to me.

@Hedanito Can you post a minimal complete example exhibiting the problem?
I can't reproduce here (with clang), but you don't post complete source so I can't be sure that I'm trying what you're trying. At this point, I tend to agree with @kirbyfan64 ; from the information you provide, it smells like a VS problem.

Minimal example added to the original post

Also try:
std::cout << AngleRatios<float>::Radians << std::endl;

If it still prints 0, it's definitely a VS bug. Try reporting it here.

Printing it to std::cout prints 1 as expected.
It seems to work everywhere just fine, until it gets expanded by the CHECK macro.

I can't repro this with Clang, and don't have a machine with VS on it, so I'm guessing in the dark here, but here's a couple of other things you can try:

Provide a definition for Radians as well as the declaration; I'd be surprised if that actually makes a difference in this instance, but it's worth a shot.
Try writing the check as CHECK( (AngleRatios<float32>::Radians) == Approx(1.0f)); - I don't honestly expect it to make any difference, but anything's possible

It still looks like a VS bug to me.

webcompiler.cloudapp.net/

@Trass3r Down for maintainance. :(

@kirbyfan64 It's back :)

I am on VS 2015 Update 3 and the minimal example no longer triggers the problem. Given this, I am inclined to close this, unless someone still has this problem on a non-RC compiler.

Actually the minimal example should still trigger the issue. At least on gcc-6 it does.
It's a link error, to be clear, and here's why.
INFO(AngleRatios<float>::Radians);
CHECK(AngleRatios<float>::Radians == Approx(1.0f));

Expression decomposition takes a reference to both sides of the ==. INFO also takes a reference. But there's no definition of AngleRatios<T>::Radians, so linking will fail.
If you use the constexpr static member in a larger constant expression, that's fine, because the compiler knows the value from the constexpr declaration, it will evaluate that expression in compile time and synthesize an unnamed variable with internal linkage to hold the result of that expression. For example this links without problem:
INFO(AngleRatios<float>::Radians * 1.0f);

Now, my opinion is that this is a non-issue. It can only surprise you once. Or so I thought. But it keeps recurring. There's been one with the likes of:
CHECK(std::is_pod<T>::value == true);

This is so easy to fix in user code, whether you construct a temporary, or add a null.
Although this never needed solving in Catch, expression decomposition got operator overloads capturing bool by value, not reference. That "fixes" it for bool only. Perhaps it'd make sense to capture all numeric types by value, but then again Catch being backward-esque, who would've wanted to write that out without the help of <type_traits>?

@lightmare If I C+P the minimal example into updated VS2015, it compiles, links and reports proper results.
According to my understanding of the original issue, RC VS2015 compiled, linked and reported wrong results.
After checking on linux, neither gcc nor clang can actually link this, so I am probably going to open up an overarching issue about that, but still close this one. If you can find the other similar issue, I am going to link both.

I am going to tag this with a revisit* label and close it for now, as the original issue was resolved.

At some point Ill have to go back and decide what to do about the Clang and GCC linker error.


Type in topologySpreadConstraint configuration of runner deployment

I wanted to use topology spread constraints to control how Pods are spread across in my cluster by topologySpreadConstraints section in runner deployment. But i faced to following error: error validating data: ValidationError(RunnerDeployment.spec.template.spec): unknown field "topologySpreadConstraints" in dev.summerwind.actions.v1alpha1.RunnerDeployment.spec.template.spec; if you choose to ignore these errors, turn validation off with --validate=false
In PR https://github.com/actions-runner-controller/actions-runner-controller/pull/814/files#diff-25283fab3c6d5fa726652c8741a122c1ba14d8486fe092774617a385e4bc1a92R145 I found that maybe I should use topologySpreadConstraint without the s on the end, and after that it started to work properly.
I`m not sure if we should change the README or the implementation.
Invalid configuration
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: k8s-runner
  namespace: github-runner
spec:
  replicas: 4
  template:
    spec:
      repository: xxx/xxx
      dockerdWithinRunnerContainer: true
      image: summerwind/actions-runner-dind

      topologySpreadConstraints:
        - maxSkew: 1
          topologyKey: kubernetes.io/hostname
          whenUnsatisfiable: ScheduleAnyway
          labelSelector:
            matchLabels:
              runner-deployment-name: k8s-runner

Valid configuration
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: k8s-runner
  namespace: github-runner
spec:
  replicas: 4
  template:
    spec:
      repository: xxx/xxx
      dockerdWithinRunnerContainer: true
      image: summerwind/actions-runner-dind

      topologySpreadConstraint:
        - maxSkew: 1
          topologyKey: kubernetes.io/hostname
          whenUnsatisfiable: ScheduleAnyway
          labelSelector:
            matchLabels:
              runner-deployment-name: k8s-runner

Probably it should be fixed in code (not docs) to recognise topologySpreadConstraints to align with https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/

Thanks. Yeah- please see #1089. We should fix it in code!


Fix: don't fail if dest in files.put is a directory

See #663.
Thanks for publishing this project. It makes me happy when I think I don't have to use ansible anymore!
This is one possible approach. Another would be to specify the issue in the documentation.

@Fizzadar thank you for attending to my incomplete PR. I lack the time to do a better job :-)

No worries at all, happy to help; thank you for taking the time to contribute to pyinfra :)


request to omit page

*Issue:*https://github.com/bcgov/entity/issues/22109 & https://github.com/bcgov/entity/issues/22106
Description of changes:
Added new request to omit page and the completing party section. This has no hookups to the API
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-196-70e81oxg.web.app

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-196-70e81oxg.web.app

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-196-70e81oxg.web.app

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-196-70e81oxg.web.app


[nima][se] IllegalStateException("OutputStream already obtained"), when ErrorHandler uses ServerResponse.outputStream()

Environment Details

Helidon Version:  4.0.0-SNAPSHOT / main
Helidon SE
JDK version:  19.0.1
OS: Linux

Problem Description

A Handler calls ServerResponse.outputStream()
Some exception occurs before any content has been sent, there are 0 bytes written
A registered ErrorHandler uses ServerResponse.outputStream() in an attempt to write error response content
This fails with IllegalStateException("OutputStream already obtained");

Thrown at: https://github.com/helidon-io/helidon/blob/main/nima/webserver/webserver/src/main/java/io/helidon/nima/webserver/http1/Http1ServerResponse.java#L149-L151
Suggested Fix options
Option A:
In ErrorHandlers.handleRequestException() when isSent() is false the "reset" the internal state of Http1ServerResponse such that it is ready for the error handler to set new headers and response content.  Set streamingEntity to false, set outputStream to null, clear the response headers?
https://github.com/helidon-io/helidon/blob/main/nima/webserver/webserver/src/main/java/io/helidon/nima/webserver/http/ErrorHandlers.java#L142-L160
... if isSent() is false reset the ServerResponse
Option B:
Allow multiple calls to ServerResponse.outputStream() as long as isSent is false.
Background: The old world ServletResponse.reset()
In the old world ServletResponse there are methods:

isCommitted() to indicate if some response content has been sent which is pretty similar to isSent()
reset() to reset headers and any response buffers such that new content can be send (typically an error message).  reset() is only allowed to be called when isCommitted() is false.

Currently, io.helidon.nima.webserver.http1.Http1ServerResponse does not have an equivalent to the ServletResponse.reset() method.
Steps to reproduce
I will look to produce an example test case that reproduces this issue and update this issue when I've done that.
git clone git@github.com:rbygrave/nima-error-handler.git
cd nima-error-handler
mvn clean test

https://github.com/rbygrave/nima-error-handler/blob/main/src/test/java/org/example/MainTest.java
package org.example;

import io.avaje.http.client.HttpClientContext;
import io.helidon.common.http.Http;
import io.helidon.nima.webserver.WebServer;
import io.helidon.nima.webserver.http.HttpRouting;
import org.junit.jupiter.api.Test;

import java.io.OutputStream;
import java.net.http.HttpResponse;
import java.nio.charset.StandardCharsets;

import static org.assertj.core.api.Assertions.assertThat;

class MainTest {

  public static void main(String[] args) {
    int port = new MyServer().port(8081).run();
    System.out.println("Running on port " + port);
    // curl -v http://localhost:8081/bad
  }

  static class MyServer {
    WebServer webServer;
    int port;

    MyServer port(int port) {
      this.port = port;
      return this;
    }

    int run() {
      final var builder = HttpRouting.builder()
        .get("good", (req, res) -> {
          res.status(Http.Status.OK_200);
          res.send("good".getBytes(StandardCharsets.UTF_8));
        })
        .get("bad", (req, res) -> {
          res.status(Http.Status.OK_200);
          OutputStream outputStream = res.outputStream();
          // error occurs before writing content to outputStream
          throw new RuntimeException("Error After res.outputStream() called");
        })
        .error(Exception.class, (req, res, e) -> {
          res.status(Http.Status.I_AM_A_TEAPOT_418);
          res.send("MyErrorMessage".getBytes(StandardCharsets.UTF_8));
        });

      webServer = WebServer.builder()
        .addRouting(builder.build())
        .port(port)
        .start();
      return webServer.port();
    }

    void stop() {
      webServer.stop();
    }
  }

  private static HttpClientContext httpClient(int port) {
    return HttpClientContext.builder()
      .baseUrl("http://localhost:" + port)
      .build();
  }

  @Test
  void good_expect_200AndGoodBody() {
    MyServer myServer = new MyServer();
    try {
      int port = myServer.run();
      var httpClient = httpClient(port);

      HttpResponse<String> goodResponse = httpClient.request().path("good").GET().asString();
      assertThat(goodResponse.statusCode()).isEqualTo(200);
      assertThat(goodResponse.body()).isEqualTo("good");
    } finally {
      myServer.stop();
    }
  }

  @Test
  void bad_expect_418AndErrorHandlerBody() {
    MyServer myServer = new MyServer();
    try {
      int port = myServer.run();
      var httpClient = httpClient(port);

      HttpResponse<String> badResponse = httpClient.request().path("bad").GET().asString();
      // we hope to get our error handler response, but we don't get it due to internal error
      assertThat(badResponse.statusCode()).isEqualTo(418); // Fail: Get 500
      assertThat(badResponse.body()).isEqualTo("MyErrorMessage");
    } finally {
      myServer.stop();
    }
  }
}

PR that fixes the test - https://github.com/helidon-io/helidon/pull/5694

This issue is now fixed for cases where OutputStream is used, including when user uses try with resources.
It only fails when bytes were actually written over the network (as this writes status and headers). In such a case, the connection is terminated in HTTP/1.1, and RST_STREAM is sent in HTTP/2 to notify the client that this is wrong (such as when we write bytes and then throw an exception before fully writing the response entity).


[bug] ID Lock 150 not locking

Version
Build/Run method

[ x] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: latest at 8th january 2021.
Describe the bug
I have an ID Lock 150 and trying to lock it over zwave has no effect. I get an error message in the debug log. Im not sure what more information you need to fix this issue or if this is something I can fix?
Expected behavior
The lock should lock.
Additional context
Debug log:
2021-01-08 22:04:53.506 INFO MQTT: Message received on zwavejs/nodeID_22/door_lock/endpoint_0/targetMode/set
2021-01-08 22:04:53.508 INFO ZWAVE: Writing LOCK to 98-0-targetMode
2021-01-08 22:04:53.512 INFO ZWAVE: Controller status: Driver: Door Lock: "targetMode" must be of type "number", received "string"
2021-01-08 22:04:53.515 ERROR ZWAVE: Unable to write LOCK on 98-0-targetMode

Thats a UI bug. zwave-js does not accept the string, so the command is never sent to the log.

Thats a UI bug. zwave-js does not accept the string, so the command is never sent to the log.

The state of the device (lock entetie) in Home Assistant is also incorrect.
This worked in the stock zwave integration in HA.
Is there some configuration I can change to make it work?

The state of the device (lock entetie) in Home Assistant is also incorrect.
This worked in the stock zwave integration in HA.
Is there some configuration I can change to make it work?

I'd wait for #84 to be merged, then we can debug this further with a working log.

I'd wait for #84 to be merged, then we can debug this further with a working log.

at #137 we changed the way lock works as due to payload. can you share with me the node exported in json?
you can do that https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/node_export
@martindlarsson

at #137 we changed the way lock works as due to payload. can you share with me the node exported in json?
you can do that https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/node_export
@martindlarsson

Here is my exported node information. Thanks!
node_22.json.zip

Here is my exported node information. Thanks!
node_22.json.zip

@martindlarsson your lock seems to be the same as the other locks. and I do see the old payload (before the patch)
    "hassDevices": {
        "lock_lock": {
            "type": "lock",
            "object_id": "lock",
            "discovery_payload": {
                "command_topic": "zwavejs/nodeID_22/door_lock/endpoint_0/targetMode/set",
                "state_locked": "true",
                "state_unlocked": "false",
                "value_template": "{% if value_json.value == false %} false {% elif value_json.value == true %} true {% else %} unknown {% endif %}",
                "state_topic": "zwavejs/nodeID_22/door_lock/endpoint_0/currentMode",
                "json_attributes_topic": "zwavejs/nodeID_22/door_lock/endpoint_0/currentMode",
                "device": {
                    "identifiers": [
                        "zwavejs2mqtt_0xd54a0707_node22"
                    ],
                    "manufacturer": "ID Lock AS",
                    "model": "Z wave module for ID Lock 150 and 101 (ID-150)",
                    "name": "nodeID_22",
                    "sw_version": "1.5"
                },
                "name": "nodeID_22_lock",
                "unique_id": "zwavejs2mqtt_0xd54a0707_22-98-0-currentMode"
            },
            "discoveryTopic": "lock/nodeID_22/lock/config",
            "values": [
                "98-0-currentMode",
                "98-0-targetMode"
            ],
            "persistent": false,
            "ignoreDiscovery": false
        },

this means you are not running a newer than a few days version, which contains the patch I mentioned, if you move to latest release this payload should update to the new one.

@martindlarsson your lock seems to be the same as the other locks. and I do see the old payload (before the patch)
    "hassDevices": {
        "lock_lock": {
            "type": "lock",
            "object_id": "lock",
            "discovery_payload": {
                "command_topic": "zwavejs/nodeID_22/door_lock/endpoint_0/targetMode/set",
                "state_locked": "true",
                "state_unlocked": "false",
                "value_template": "{% if value_json.value == false %} false {% elif value_json.value == true %} true {% else %} unknown {% endif %}",
                "state_topic": "zwavejs/nodeID_22/door_lock/endpoint_0/currentMode",
                "json_attributes_topic": "zwavejs/nodeID_22/door_lock/endpoint_0/currentMode",
                "device": {
                    "identifiers": [
                        "zwavejs2mqtt_0xd54a0707_node22"
                    ],
                    "manufacturer": "ID Lock AS",
                    "model": "Z wave module for ID Lock 150 and 101 (ID-150)",
                    "name": "nodeID_22",
                    "sw_version": "1.5"
                },
                "name": "nodeID_22_lock",
                "unique_id": "zwavejs2mqtt_0xd54a0707_22-98-0-currentMode"
            },
            "discoveryTopic": "lock/nodeID_22/lock/config",
            "values": [
                "98-0-currentMode",
                "98-0-targetMode"
            ],
            "persistent": false,
            "ignoreDiscovery": false
        },

this means you are not running a newer than a few days version, which contains the patch I mentioned, if you move to latest release this payload should update to the new one.

Im running :latest which is 11 days old

Im running :latest which is 11 days old

can you try the :dev ? this is the one compiles every night from master

can you try the :dev ? this is the one compiles every night from master

Ill try :)

Ill try :)

Now it wokrs!! Thank you all for super wokrk! Im really impressed with how zwavejs works at this early stage.

Now it wokrs!! Thank you all for super wokrk! Im really impressed with how zwavejs works at this early stage.

Well, it has been in development for 3 years ;)

Well, it has been in development for 3 years ;)


Program terminates when adding episodes to the queue

I added a new series (https://www.crunchyroll.com/series/GYX08020R/knights--magic), but the program just terminates abruptly. Refreshing episodes appears to work, but the crash occurs after I click on "Add to Queue". There is a long pause before the program just terminates. As far as I can tell, no downloads actually start.
The only thing in the log file is:
Error: System.Net.Http.HttpRequestException: Response status code does not indicate success: 420.
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at CRD.Utils.HttpClientReq.SendHttpRequest(HttpRequestMessage request)
Response: {"error":"TOO_MANY_ACTIVE_STREAMS"}
I am running the latest code, released today (1.5.27)

I realized that this happened after I set max simultaneous downloads to 6. I set it down to 4, and everything works without crashing. I wonder if CrunchyRoll can only handle so many streams being pulled at the same time.

hm maybe it depends on your subscription - i just tried 6 episodes at the same time and had no problem
usually the "TOO_MANY_ACTIVE_STREAMS" happens when your limit with crunchyroll is reached - but i close the streams pretty fast maybe i have to add a delay of a couple of seconds
you can also try to disable auto download and activate the downloads one by one

Successfully downloading one by one is what led me to the conclusion that there's nothing wrong with the files or download mechanism, and prompted me to look at the simultaneous downloads. When the big picture doesn't make sense, simplify to the essential parts. ☺
And good call; I'll be sure to check the Windows application logs next time around.

Problem is still happening sporadically. Here's info from the Application Event Logs. Hopefully this will help.
Application Error, Event ID 1000:
Faulting application name: CRD.exe, version: <IP_ADDRESS>, time stamp: 0x65f90000
Faulting module name: KERNELBASE.dll, version: 10.0.17763.6189, time stamp: 0xd399e59c
Exception code: 0xe0434352
Fault offset: 0x0000000000041b39
Faulting process id: 0xa40
Faulting application start time: 0x01dafcc6d1e13fbb
Faulting application path: D:\Applications\Crunchy-Downloader\CRD.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 99478ed3-77e0-45cb-aab3-19a9a0535df6
Faulting package full name:
Faulting package-relative application ID:

.NET Runtime, Event ID 1026:
Application: CRD.exe
CoreCLR Version: 8.0.524.21615
.NET Version: 8.0.5
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException: Object reference not set to an instance of an object.
at CRD.Downloader.Crunchyroll.CrunchyrollManager.HandleStreamErrorsAsync(ValueTuple`2 response, String mediaGuidId, String endpoint)
at CRD.Downloader.Crunchyroll.CrunchyrollManager.FetchPlaybackData(String mediaId, String mediaGuidId, Boolean music)
at CRD.Downloader.Crunchyroll.CrunchyrollManager.DownloadMediaList(CrunchyEpMeta data, CrDownloadOptions options)
at CRD.Downloader.Crunchyroll.CrunchyrollManager.DownloadEpisode(CrunchyEpMeta data, CrDownloadOptions options)
at CRD.ViewModels.DownloadItemModel.StartDownload()
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at Avalonia.Threading.SendOrPostCallbackDispatcherOperation.InvokeCore()
at Avalonia.Threading.DispatcherOperation.Execute()
at Avalonia.Threading.Dispatcher.ExecuteJob(DispatcherOperation job)
at Avalonia.Threading.Dispatcher.ExecuteJobsCore(Boolean fromExplicitBackgroundProcessingCallback)
at Avalonia.Threading.Dispatcher.Signaled()
at Avalonia.Win32.Win32Platform.WndProc(IntPtr hWnd, UInt32 msg, IntPtr wParam, IntPtr lParam)
at Avalonia.Win32.Interop.UnmanagedMethods.DispatchMessage(MSG& lpmsg)
at Avalonia.Win32.Win32DispatcherImpl.RunLoop(CancellationToken cancellationToken)
at Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)
at Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
at CRD.Program.Main(String[] args)

new version should at least fix the crash

Thank you. I'll give it a try and let you know in the next day or two when new episodes come out.


Resolve TitleProvider warnings logged in the browser console

🐛 Bug Report
It was observed that react warning are logged to the browser console relating to the TitleProvider component. See comments on #2354
To Reproduce
Steps to reproduce the behavior:

Expected behavior
There should be no warnings/errors logged in the browser console.
Your Environment

node version: 6,8,10
fastify version: >=1.0.0
os: Mac, Windows, Linux
any other relevant information

I would like to work on this issue...Thank you

Ok @sohamsshah

If no one is working on this issue, I would like to

@dev-script currently is assign to @sohamsshah

Hey @dev-script you can work on this man. I am a bit busy, so couldn't complete this. I will take another issue, idea is to get the work of the Open Source going on! Good luck!

sure @sohamsshah  . Thanks


freebsd_installworld should use SRCCONF and __MAKE_CONF on all stages of build process

Some people would have their own src.conf and make.conf, for example, not to build some extra parts of FreeBSD (like sendmail, etc.)
It works perfect for buildworld, but cause failures, while crochet performs 'make distribution' or 'make installworld'

Good point.  Could you send a pull request?  It looks like a small change to lib/freebsd.sh.

Yeah! Will do it soon

Merged it.  Thanks!


Draft should output Docker build results

This issue is more of a feature suggestion, but I believe that Draft should immediately output the Docker build logs, similar to how Google's skaffold does. A few reasons:
Improvements:

Users expect "docker builds" to output their build progress (and image IDs)
Users should not have to run draft log xxx just to see why their image build failed
Time saved from having to copy/paste

Drawbacks:

Long builds will spam terminal scrollback, but they have this issue already likely
Changes to the CLI progress would have to be made
draft logs?

I think the idea of having the logs stream on failure is a good idea.
I also like the output of the image Id.
I do not need to see the logs for success. It is a mess of line spam that adds nothing to most users. Only people who are used to it like it, imho. Pretty much everyone else ignores it until error or success. But my position is just one....
From my pov, two out of three ain't bad!

@squillace I would agree with that, while it is expected behavior it's probably unnecessary.

We used to stream them a long time ago. It might be good to revisit that assumption if users still want that output on draft up.

@squillace If draft were to adopt a config setting for always enabling build log streaming (log-build?) and another setting for printing the log after the build has failed (log-build-errors?), then we can still default to not streaming any logs while giving the user an option to use whatever applies best to their use-case.

Draft newbie here :) I think the missing log output is especially awkward while developing or modifying the Dockerfile. In this specific case I would definitely prefer having the full build output so I can fail fast and try again, without having to copy/paste the draft logs command. I think a parameter to draft up would be nice (--log or --verbose or something?)
Other idea: a new draft build command that only builds the image locally (no push/deploy) and that would display the full log by default?

Hey @tomconte, that's good feedback.

a more general but advanced variant of this is described in #815

This is very much wanted for long running builds such as maven/gradle or npm based projects where to collection of dependencies is a rather long process


Build params docs from pipeline schema

Use the new JSON schema in pipelines (if present) to build a documentation page for pipeline parameters on the pipeline page.

current ideas:

split Documentation in the navbar into Usage and Output (maybe find better terms, also maybe replace Readme with Introduction?)
move docs/{usage,output} to {usage,output}
only render usage.md for pipelines without a json-schema (in a further step, maybe make a lint check that usage.md is removed if nextfow-schema.json is present)
move schema group names into a navbar sidebar (and maybe make the tab sticky to replicate parts of the current sidebar)

Sounds good! Some quick thoughts:

How about rendering usage.md above the automated parameter docs? Then people can write custom prose documentation if they want. Hopefully they will clean the parameters from usage.md when making schema..
If we are updating the URLs for docs, would be great to make them versioned too (#309)

Navbar sidebar is good, some of the ToC stuff we have kicking around looks a bit rubbish, so if you fancy sprucing that generally then that would be fab 👍

Okay, I got the rendering working.
Concerning which parts of the actual schema to use, I was thinking of using only the help text if available and otherwise drop back to the description, because they are often redundant, with the help text being more in depth.

Hmm, no I think we should have both sorry. I’m not sure that we can guarantee that they will duplicate one another that much? And I have a feeling that some I’ve written assume that both will be visible. This is how it’s rendered it on the command line too.

Done in https://github.com/nf-core/nf-co.re/pull/456


Support MongoDB 3.6

Will it work with MongoDB 3.6?
MongoDB 3.6 and Elasticsearch 6, would be very nice :)

Yes, please !

@jesben mongo-connector seems to work just fine with MongoDB 3.6.2. I just tried it out and mongo.connector.log prints out
2018-02-08 00:58:35,558 [ALWAYS] mongo_connector.connector:51 - Source MongoDB version: 3.6.2

@mistermoe nice I will try the same to day then. Have you see this pull request: https://github.com/mongodb-labs/mongo-connector/pull/781 ?

#781 has been merged and is releasing as 2.6.0.
Still remaining for proper support:

[ ] Get tests passing against MongoDB 3.6.
[ ] Update docs to declare support for MongoDB 3.6.


Allow user to configure what mockwebserver binds to

Provide start(InetSocketAddress) and start(InetAddress, port) to
address #1342

Whoops docs are out of date.

@JakeWharton Addressed.

 Please see https://travis-ci.org/square/okhttp/pull_requests

Thanks. On it.

@JakeWharton I corrected the issue but I can't tell if Travis is running the tests.

Can you change something and force push? CI should be fixed. There's an empty trailing line in that one Javadoc, delete that maybe?

@JakeWharton Done looks like it is marked pending in the github ui now.

Sweet!

@JakeWharton I get these failures when I run locally without my changes.

I just got the master branch tests passing on my local machine. Looking into the failures introduced by my changes now.

So close. openjdk7 passing, openjdk8 having issues.

FYI, we've had some flakiness issues with JDK8 lately. If you've got JDK7 passing, and you don't think the other changes are related, they probably aren't!

I don't really have the experience to say one way or the other.
On Jan 25, 2015 4:45 PM, "Jesse Wilson"<EMAIL_ADDRESS>wrote:

FYI, we've had some flakiness issues with JDK8 lately. If you've got JDK7
passing, and you don't think the other changes are related, they probably
aren't!
—
Reply to this email directly or view it on GitHub
https://github.com/square/okhttp/pull/1345#issuecomment-71402814.

I don't recognize the one failure as a common flake. Re-kicking the build.


Cannot use Accelerate framework

After importing
import Accelerate.vImage
Cannot use following functions
var f32vImageBuffer = vImage_Buffer()
var f16vImageBuffer = vImage_Buffer()

var error = kvImageNoError

While trying to use, got out of scope issue

i think it is relevant actually, i am looking into the same issue.
After embedding Open3D, whatever existing code which is using Accelerate is "out of scope".
Numpy has linkerSettings: [.linkedFramework("Accelerate")]

@1agora Have you seen this? https://stackoverflow.com/a/58525429/2570853

@kewlbear i can't see how this post is related, but it helped me with another issue i had, thanks!
seems like a linker config issue where accelerate framework being lost in the imports
@ameensaleem did you figure it out? if you did please share)

@1agora I'm still looking for fix, Previously I thought the issue is with LAPACKE-iOS,
https://github.com/kewlbear/LAPACKE-iOS/tree/main/Sources/Accelerate
after you've mentioned I'm looking Numpy and try to fix this, I'll share if I did.

@ameensaleem You were right. LAPACKE-iOS had name clash problem. I pushed fixes to the repo. Please see if your problem is fixed. Thanks!

@kewlbear Now I can access Accelerate Framework, Thank you so much!.


Outdated files in the dev-1.13-ko.1 branch

This is a...

[ ] Feature Request
[ ] Bug Report

Problem:
115 files in content/en are changed
12 files in content/ko are outdated

[x]  docs/setup/_index.md
[x]  docs/setup/independent/create-cluster-kubeadm.md
[x]  docs/setup/independent/high-availability.md
[x]  docs/setup/independent/install-kubeadm.md
[x]  docs/setup/minikube.md
[x]  docs/setup/multiple-zones.md
[x]  docs/setup/pick-right-solution.md
[x]  docs/setup/scratch.md
[x]  docs/tutorials/hello-minikube.md
[x]  docs/tutorials/kubernetes-basics/deploy-app/deploy-intro.html
[x]  docs/tutorials/kubernetes-basics/update/update-intro.html
[x]  examples/minikube/Dockerfile

This outdated file list is generated by the script based on the result of comparison 2a1899a6 to ad54de44.
Proposed Solution:
Use git diff to check what is changed in the upstream. And apply the upstream changes manually to the content/ko of dev-1.13-ko.1 branch.
For example:
# checkout `k/website:dev-1.13-ko.1`
...
# check what is updated in the upstream
git diff 2a1899a6 ad54de44 -- content/en/docs/setup/_index.md
# apply changes to content/ko
vi content/ko/docs/setup/_index.md
...
# commit and push
...
# make PR to `k/website:dev-1.13-ko.1`

Page to Update:
https://kubernetes.io/...

Resolved by #10689


backend_daydream: use daydream version 1.80

GearVRf-DCO-1.0-Signed-off-by: Mihail Marinov<EMAIL_ADDRESS>

Planning to merge on Tuesday.


ESLint v9 flat config

Hello,
Is the support of ESLint v9 + flat config going to be supported in the near future?
Greetings,
Mike

Hey @mike-lock ,
Supporting flat config has actually been planned!
Meanwhile, you could use the @eslint/compat to adapt the legacy config for now like this one.

Added support for the flat config in v0.4.0.


Inquiry Regarding Edge Coverage Discrepancy

In my reproduction experiment, the edge coverage on readelf reached only 10,606 within 24 hours and basically no longer rising. However, you mentioned an edge coverage of 53,859 in the paper, which is significantly different from my experimental result.
I use
./fuzz -i readelf_new -o seeds -l 7507 ./readelf -a @@
and
python nn.py ./readelf -a
to start the program I pulled from github project. And according to log file(log_fuzz)
2024-03-30 09:18:03: gradient fuzzing state: line_cnt 10 and edge num 5116 I start my program
2024-03-31 09:18:48: gradient fuzzing state: line_cnt 100 and edge num 10622 which is 24 hours
2024-04-01 01:49:13: gradient fuzzing state: line_cnt 60 and edge num 10947 hardly have any grouth
My running devices are RTX4090*2 and Intel (R) Xeon (R) Gold 6248R.
Can you give me some suggestion on this phenomenon. Thanks!

你好我也是用虚拟机跑了很久objdump覆盖率也提不上去，不知道是怎么回事，能讨论一下吗

你好我也是用虚拟机跑了很久objdump覆盖率也提不上去，不知道是怎么回事，能讨论一下吗

我用docker、主机环境都测试过，neuzz、MTFuzz对readelf测试，边缘覆盖率都在10000左右基本不上升了，和论文写的50000多差挺大，是不是作者用的计算指标或者算的方法不太一样，想请教一波

是的，我的更少，objdump我测了一直在5500左右。。。。

Hi
Thank you for your query regarding our method for measuring code coverage. I understand you've noticed some discrepancies between the metric described in our paper and what's implemented in this GitHub repository. I appreciate your diligence in seeking clarification on this matter.
To resolve any confusion, I would recommend reviewing Section 3.4.1 in our paper, where we discuss the rationale behind our choice of metrics, including any variations and the impact they have on our results.
To be specific, AFL utilizes trace_bits to store the state of edge coverage, with each edge being represented by 8 bits to denote different coverage counts. The AFL framework monitors changes at this bit level, preserving seed files for each unique change observed, which is central to its fuzzing efficiency and effectiveness in uncovering unique paths through a codebase.
In our research, we've adopted a nuanced approach to measuring coverage by not only considering the edge coverage data (i.e., whether an edge has been hit) but also by performing an in-depth analysis of all bit-level changes within trace_bits. This methodology allows us to capture a more granular level of coverage, accounting for the varying frequencies of edge executions which, in turn, offers insights into the thoroughness of the test suite and its ability to stimulate different behaviors in the target software.
This distinction is critical, as it enables us to evaluate the effectiveness of test cases on a more detailed scale than merely observing whether an edge was covered. By quantifying all bit changes, we assess the diversity and depth of the test coverage, providing a more comprehensive measure of the fuzzing process's effectiveness.
Thank you once again for your interest in our work. Your engagement with the finer points of our methodology is invaluable to us and the broader research community.
Best regards


Support for Spreaker.com

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.06.23. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2017.06.23

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[X] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-ci', '--write-thumbnail', '--sub-format', 'ass/srt/best', '--write-auto-sub', '--convert-subs', 'srt', '--write-description', '--write-info-json', '-f', 'bestvideo+bestaudio/best', '-o', '/Videos/%(uploader)s - %(title)s (%(id)s).%(ext)s', '-v', 'http://www.spreaker.com/show/andre-dorseys-show']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.06.23
[debug] Python version 3.4.4 - Windows-10-10.0.15063
[debug] exe versions: ffmpeg N-81774-g64545dd, rtmpdump 2.4
[debug] Proxy map: {}
[generic] andre-dorseys-show: Requesting header
WARNING: Falling back on generic information extractor.
[generic] andre-dorseys-show: Downloading webpage
[generic] andre-dorseys-show: Extracting information
[generic] player?show_id=2452465&autoplay=false: Requesting header
WARNING: Falling back on generic information extractor.
[generic] player?show_id=2452465&autoplay=false: Downloading webpage
[generic] player?show_id=2452465&autoplay=false: Extracting information
ERROR: Unsupported URL: https://widget.spreaker.com/player?show_id=2452465&autoplay=false
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpsrujt7wq\build\youtube_dl\YoutubeDL.py", line 762, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpsrujt7wq\build\youtube_dl\extractor\common.py", line 433, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpsrujt7wq\build\youtube_dl\extractor\generic.py", line 2796, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: https://widget.spreaker.com/player?show_id=2452465&autoplay=false
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://www.spreaker.com/user/dmgaming/should-madden-18-be-half-price
Single video: http://api.spreaker.com/download/episode/12166906/should_madden_18_be_half_price.mp3
Playlist: http://www.spreaker.com/show/andre-dorseys-show
RSS: http://www.spreaker.com/show/2452465/episodes/feed

Did this ever get merged?

Did this ever get merged?

bump for this :)

I'm on "2019.09.01" and I miss this :)

bump 2+ years later


Fix: wrong generic type of Omit

Nah, the current formulation is intentional. Omit's second argument doesn't need to be limited to the keys of its' first, as the operation works fine if there're not (Omit<{x: number}, "y"> can still be resolved), so it isn't. keyof any is just used as a way to say "all key types" (string | number | symbol).

See #30825 for more on this.

But we can make StirctOmit<T, U extends keyof T> right?


R-universe / R packages repositories

R package repositories and https://r-universe.dev
Day 1, 2:15 - 3:10 PM
@jeroen @noamross @vjcitn @almahmoud @nealrichardson
Maybe interesting for conda-forge? @wolfv @ocefpaf
Session Notes

Yeah would love to talk about this with you all.

Thanks for proposing the topic, @aterrel!
This is scheduled in Garage Hub.
Starts @ 14:40.
Check the schedule here: https://www.nfsummit24.com/schedule.

Maybe interesting for conda-forge? @wolfv @ocefpaf

We got a schedule conflict with the anaconda room . Hopefully we can compare notes later.


Categorical plots: show ticks for all values and show them in correct order

[Depends on https://github.com/VEuPathDB/web-eda/pull/189]
The visualization plugins for categorical plots currently only include values for which we have data, in the given subset. The new variable property vocabulary can be used to add tick marks for values without data.
Furthermore, this property also defines an order and should be used as the default ordering of tick marks and rows in the table filter.

I think this also includes the categorical variable table (TableFilter) in subsetting.
I had a quick look to see if a generic approach might be possible, but each plugin may need the results re-ordering in its own special way.
Also overlay (and facet) variables will need ordering too.

Taking this on.
A good example is GEMS1 -> Household -> Water avaliability
(many others are just in alphanumeric sort order)

Going to implement the categorical x-axis ordering using plotly's categoryorder rather than doing elaborate re-sorting of data in the client (see below).
There are other plotly sort modes we can make use of in future (sort by value ascending/descending etc).
We'll need to check what happens for empty categories (the "ticks for all values" part of this ticket, though I'm not sure we should actually do this - or at least if we do, it needs to be user-controllable)
overlay ordering will probably require client-side sorting.
const layout = {
    "xaxis": {
        "categoryorder": "array",
        "categoryarray":  ["A", "B", "C", "D", "E"]
    }
};

QA'd the following:
Visualizations

Overlay values
Bar plot x-axis values
Box plot x-axis values
RxC contingency x-axis values
RxC contingency y-axis values

@SheenaTomko are there any places I forgot to check?

Hi @danicahelb - why did you reopen the ticket? Is this part of the SOP?
One can add comments to a closed ticket (though perhaps notifications are different?)

Maybe it's OK to do - it hasn't moved the ticket into a different column of the project https://github.com/orgs/VEuPathDB/projects/2 - thankfully!

I think I’d prefer that issues are not reopened, unless they are deemed
incomplete.
On Wed, Aug 18, 2021 at 7:31 PM bobular @.***> wrote:

Maybe it's OK to do - it hasn't moved the ticket into a different column
of the project https://github.com/orgs/VEuPathDB/projects/2 - thankfully!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/VEuPathDB/web-eda/issues/195#issuecomment-901496327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACZEU56CNMK3TJVVDKLAPDT5Q7EXANCNFSM47S5AQJQ
.

On second thought, reopening is a nice signal that the issue is being
reviewed. So, I think I’m fine with this being the SOP.
On Wed, Aug 18, 2021 at 8:12 PM Dave Falke @.***> wrote:

I think I’d prefer that issues are not reopened, unless they are deemed
incomplete.
On Wed, Aug 18, 2021 at 7:31 PM bobular @.***> wrote:

Maybe it's OK to do - it hasn't moved the ticket into a different column
of the project https://github.com/orgs/VEuPathDB/projects/2 - thankfully!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/VEuPathDB/web-eda/issues/195#issuecomment-901496327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACZEU56CNMK3TJVVDKLAPDT5Q7EXANCNFSM47S5AQJQ
.

No Danica, I think you got them all. Looks good, closing this and moving it to the closed column


[BUG] unable to use macros with variables.

Describe the bug
unable to use macro in a line with variable operation of some sort. i get following error:
In src/code/arthealth/entity.jmc:67:5
Unexpected double variable sign at line 67 col 5.
66 |    // tf you looking at
67 |    $$uwu = namespace.$(owo):@s;
        ^^^^^
68 |    // tf you looking at

To Reproduce
[Steps to reproduce the behavior]

type this in any function

$$uwu = namespace.$(owo):@s;

compile it

Expected behavior
i didnt expect any error.
Desktop

os - windows
jmc version - latest build from github
python - 3.12

Additional context
if you do
$$uwu = $(owo):@s;

then its gonna work

Try $ $uwu = $(owo):@s;?

adding space still gives an error.
JMCSyntaxException
In src/code/arthealth/entity.jmc:66:5
Unexpected variable without name (`$`) at line 66 col 5.
65 |    $scoreboard players operation $resist __variable__ = @s resist.$(damage_type);
66 |    $ $resist = resist.$(damage_type):@s;
        ^
67 |    Hardcode.repeatLists(


added level: "intro rebasing"

Hey @parkmichael777 , Thanks for the PR.
A couple things:

You forgot to add rebasing in intro/init.py.
Can you also change the folder that the challenge's files resides in to "_rebasing"? Then I'll be able to test it and see if it all works as intended

New version should be pushed now
On Sat, Oct 12, 2019, 8:55 PM Ben Thayer<EMAIL_ADDRESS>wrote:

Hey @parkmichael777 https://github.com/parkmichael777 , Thanks for the
PR.
A couple things:

You forgot to add rebasing in intro/init.py.
Can you also change the folder that the challenge's files resides
in to "_rebasing"? Then I'll be able to test it and see if it all works as
intended

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bthayer2365/git-gud/pull/17?email_source=notifications&email_token=AKKQOKL5M6A2VTSGPTQF2C3QOJ5YLA5CNFSM4JAEGQYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCMJVY#issuecomment-541377751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKQOKNQBGNTEN37DFZH5R3QOJ5YLANCNFSM4JAEGQYA
.

Hey, so in the instructions, you make it sound like the user is supposed to be doing these commits themselves, but I don't think that's the goal. I think we should set up the tree for them.
Going off of test.spec, you should have two branches, each coming off of the same initial commit. 1, 2, and 3 form the master branch and 1, 4, 5 form the bugFix branch. so that would be changing it so setup.spec looks like test.spec, but with the 4 as 4 : 1.
Also with test.spec, even though that's a rebase, we still don't have a mechanism for checking whether a commit is new, so for now we're just going to assume that users are using the rebase command. After all, they're doing this to learn git, not to "beat the game". Later on, we can work on another pull request to officially get rebase tracking setup.
Finally, I think the instructions should do more to explain the current situation - something like telling the user to run git log and to make note of how commits 2 and 3 show up in the history after the rebase.

You'll need to run
git remote add ben git@github.com:bthayer2365/git-gud.git
git checkout _rebase
git pull --rebase ben master

You'll also run into a conflict with gitgud/levels/intro/init.py, After running the last command, go into that file, change things, deleting the del statements you have and making sure all the levels are present.
Then run
git add gitgud/levels/intro__init__.py
git rebase --continue

So, I did those commands. Now, it says that I am 54 commits ahead origin/_rebase and that I should push the local commits... I didn't commit 54 times? Is this referring to the commits made from the merged branch?

Those 54 commits are from me and others who've been merged in. (We've been busy....) You'll need to force push, so run git push --force, and it'll update the code on this PR

Okay, I've done that. Let me add the new setup.spec too.

Also, how do I make sure that this doesn't happen again? I tried pulling before, but I always got the "already up to date" message.

 So, even if you're on master, it won't be up to date by just running git pull, since all those changes are just the ones that you've worked on. To get my changes (and everybody else's changes that I've merged), you need to pull from my master branch.
If you do this, then you can just start a new branch off of master and it'll start on the most recent commit from my repo. You can then push/pull to/from your remote to sync up your changes on github

Let me know when you've made all the changes you'd like to make

Ah, makes sense now!
Okay, I am done updating the instructions and setup. Everything is pushed.

Just to make it a little more clear, here's a checklist:

[ ] Remove ' from test.spec
[ ] Add instructions in merging challenge to run git log --graph --oneline to highlight the differences between rebasing and merging
[ ] Incorporate what I said into the rebase instructions

Okay, I've pushed those changes. Let me know if they need to be modified.

I checked everything out. It looks good and all works as intended.
Ironically, I looked through your history and you had a bunch of merges mixed into your rebases, somewhat defeating the purpose of rebasing to keep the code clean.  That's fine, but I think instead of doing a normal merge or rebase, I'm going to do a squash and merge, which just puts all the changes in a single commit and makes everything much more clean. Nothing more to do on your end there.
One thing for you, then we're good to go. Have the user run git log --graph --oneline --all (note the --all flag) before and after the rebase and before and after the merge. I think we should get them used to using this command. Commit that change and we're good.
I'll be able to see all your changes online, so as soon as you do that, I can quickly view/merge. This is awesome! Thanks for the hard work!

Yeah, I think part of that is just me being bad at git, haha. There was a conflict and I did a bunch of weird things and it somehow worked out.
I've added those comments to the two instruction files.

Great, it's in!

Awesome, thanks!


[DNR][DNM] LLDB crash Xcode 15.x

Works around a LLDB crash happening on Sonoma + Xcode 15.x.
Pulling into rules_ios a change @jerrymarino did internally to fix the crash for us. I don't think there's an easy way to find a small repro since it was hard to repro even in our internal setup.
@jerrymarino let me know if you want to add more details here in the comments, maybe you can share a more detailed explanation of what was going on for future readers?

This was supposed to be a draft, my bad for the notifications others might have received

Closing this for now as I'm planning to re-visit it in a newer Xcode version


Install wiki system using 3git in DigitalOcean vm

install and reload using jsx command

wikis tested with jsx unstable branch and working fine

Steps :-
1- install jumpscale with unstable branch

ssh root@ip -A #to load ssh key
apt update -y
apt install -y openssh-server locales curl git rsync unzip lsb python3
apt install python3-pip
pip3 install click
ssh-add -L #to check loaded key
curl https://raw.githubusercontent.com/threefoldtech/jumpscaleX_core/development/install/jsx.py?$RANDOM > /tmp/jsx;
chmod +x /tmp/jsx;
/tmp/jsx install
for i in $(ls -ld /sandbox/code/github/threefoldtech/*); do cd $i && git checkout unstable && git pull ; done # switching to unstable branch
jsx generate
jsx wiki-load -n tokens -u https://github.com/threefoldfoundation/info_tokens/ -f


Follow the naming convention used in Kubic images

Follow the naming convention used in Kubic images

+1 great


feat(Icons): add ProductsBriefcaseIcon, SmileyHappyIcon, SmileySadIcon, SmileyIndifferentIcon, and SmileyStarEyesIcon

Overview

add ProductsBriefcaseIcon, SmileyHappyIcon, SmileySadIcon, SmileyIndifferentIcon, and SmileyStarEyesIcon

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: LEGO-3551
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Don't make me tap the sign.
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

📬Published Alpha Packages:@codecademy/gamut@55.10.3-alpha.2e1df3.0@codecademy/gamut-icons@9.10.1-alpha.2e1df3.0@codecademy/gamut-kit@0.6.367-alpha.2e1df3.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut@55.10.3-alpha.073010.0@codecademy/gamut-icons@9.10.1-alpha.073010.0@codecademy/gamut-kit@0.6.367-alpha.073010.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://655d1ede6e85230cc441e9fa--gamut-preview.netlify.appDeploy Logs


add optional cert_file and key_file for signature validation

Pull Request Test Coverage Report for Build 154

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

Totals

Change from base Build 149:
0.0%

Covered Lines:
232

Relevant Lines:
392

💛  - Coveralls


Add namespace awareness to relevant transformations

Because namespaces weren't initially supported in Biohazrd, some of the built-in transformations don't handle them properly. For instance, MoveLooseDeclarationsIntoTypesTransformation effectively removes them from loose declarations.

[ ] MoveLooseDeclarationsIntoTypesTransformation
[ ] DeduplicateNamesTransformation
[ ] Double-check others

One thing I've realized is that once DeduplicateNamesTransformation is namespace-aware, it is possible for name collisions to form when two namespaces with same-name types have using statements. Not sure if/how I want to handle that.

One thing I've realized is that once DeduplicateNamesTransformation is namespace-aware, it is possible for name collisions to form when two namespaces with same-name types have using statements. Not sure if/how I want to handle that.


fix(scripts): Fix install scripts to install by one key for k8s 1.14.8

What this PR does / why we need it:
Fix install scripts to install by one key for k8s 1.14.8
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @FogDong @hewenguang

Release note:

Fix install scripts to install by one key for k8s 1.14.8

LGTM

ping @FogDong

/lgtm

/lgtm

/lgtm

/lgtm

/lgtm


Looking for maintainers

Hi folks,
I'm overwhelmed by the community response to help with the project. Thank you, I appreciate it a lot.
I didn't expect the project to get to where it is right now - and I need to ask for help in order to make the project achieve it's goals.
Currently, I'm responsible for all aspects of the project - some of it includes supporting users, approving & editing protests, creating a [non-tech] contribution infrastructure and getting in touch with organizations.
It's hard for me to maintain the development aspect while being in this position.
I'm looking for people who have time and feel they can help me maintain the project in the upcoming weeks.
If you feel you can take this position, let me know.
Cheers,
Guy

@dafnamordechai maybe someone from Baot would be open to help here?

@guytepper I would be happy to help let me know what I can do.   I am guessing you are pretty overwhelmed but if you want effective help you need to be specific.  Break down the work that needs to be done and divide that up between willing volunteers.

Hei  @joeyede, thanks a lot for willing to help.
I'm looking for someone with similar responsibilities to a team leader. Needs to know how to take the roadmap & translate it into issues for contributors, review PRs, etc.

I suggest to also put a note at the top of the README (and link to this issue). Here is an example.

I probably can do that.
Want to jump on a quick video call?
On Mon, 5 Oct 2020, 11:40 am Guy Tepper<EMAIL_ADDRESS>wrote:

Hei @joeyede https://github.com/joeyede, thanks a lot for willing to
help.
I'm looking for someone with similar responsibilities to a team leader.
Needs to know how to take the roadmap & translate it into issues for
contributors, review PRs, etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/guytepper/1km.co.il/issues/22#issuecomment-703550126,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3WAZGHPNLHXQPVCLZ5BC3SJGPBVANCNFSM4SD6ROPA
.

@joeyede send me an email with your phone number -<EMAIL_ADDRESS>

@uriklar joined as a maintainer! We'd love more help :-)

I would like to join a maintainer as well @guytepper

@webernir is now a maintainer! Congratulations! 🥳
Still looking for more help. Let me know if you'd like to join us!

Seems like we're doing fine now :) Thanks everyone ❣


fixed issue 3427 by updating interpolation module functions

Summary
Fixes #3427
Details and comments
After an initial attempt to fix the issue via matplotlib drawer which only worked for square pulses @nkanazawa1989 suggested a fix within the interpolation module. I thought it was best to define another function dedicated to step_wise which @nkanazawa1989 also agreed on. We now seem to have corrected for the start and end of the pulse regardless of pulse type.

We're almost there, just a couple linting issues. Could you please update @faraimazh?

We're almost there, just a couple linting issues. Could you please update @faraimazh?

@nkanazawa1989 is looking at the linting issues because apparently all my modules seem not to pass those two tests. I have not changed the header for all I know. We suspect a regex bug.

It may be that you have a special character in the header. I would suggest copying one from another Qiskit file to see if this fixes the issue.

We tried that but the problem remains.

I've shared this lint issue with @mtreinish. I thought it was due to linefeed code and asked him to replace all code block by one from other files, but there was nothing to commit. In my local env I often get this header error which is not caused in Azure linter. something odd is happening.

This LGTM! Note that this PR Inserts pylint disable before the header as a workaround for regex issue. This should be fixed in future and the disable should be removed.


Need support for iOS 17 & Xcode 15 and above with the new URL string parsing changes

If we want to keep using the pre-iOS 17 behaviour, then we would need to replace URL(string:) with the new URL(string:encodingInvalidCharacters:) and passing false to the second argument. Apps which deals with URL strings definitely need to be tested thoroughly on iOS 17.
If someone can create a version which supports iOS 17 it would be really nice. Thanks
Detailed description of the issue in this link

Hi @blakewatters, is RestKit planning to make changes to support this issue? Your response on this would be highly appreciated. Thanks.


only downloads half the midi file

trying to download a midi file of a score with only one instrument but two hands (like https://musescore.com/user/38111661/scores/7346651) will only download one hand

should have tried updating smh

well actually it doesn't seem to work with https://musescore.com/user/38111661/scores/7346651

Are you using FL Studio?


wrap file.path and find.package in normalizePath

with winslash = "\", mustWork = FALSE.
Do not merge.  This is to check first if I broke anything.
It is hoped this will fix #928.
Some check on Windows need to be done.

@perrydv ok to merge this?


Update documentation to finalize idea

Since focus shifted a bit during last couple of days, the documenttion should be updated accordingly

Idea is continously documented, so issue can be closed


Refactor Azure OpenAi

Clean the AzureOpenAiChatClient and add support  for StreamingChatClient.
Streamline the AzureOpenAiEmbeddingClient.
Move the AzureOpenAiChatClient and AzureOpenAiEmbeddingClient to top org.sf.ai.azure.opoenai package.
Add ITs for AzureOpenAiChatClient and AzureOpenAiEmbeddingClient
Fix the AzureOpenAiAutoConfiguration

Split property file into AzureOpienAiConnectionProperties, AzureOpenAiChatProperties and AzureOpenAiEmbeddingProperties.
Add ITs for the auto-configuration

Add improve package structure
Add README docs

merged in 0ccf32780696af284794ee0f8420857dc1cce6a3  Updated github actions secrets to run Azure IT tests.


Drop support for non-Active LTS and Current releases

Tracking issue for the next major version of gulp-sass.
TODO

[x] Drop support for non-Active LTS and Current releases. Closes #649
[x] Replace deprecated gulp-utils. Closes #647
[x] Update dependencies
[x] Adopt a lint preset
[x] Release v3.2.0
[ ] Wait to see how stable<EMAIL_ADDRESS>is

Hi @xzyfer , would you share with us how long to see how stable node-sass 4.8 is. That info could give us a clue how long we need wait for it.
Thank you and thanks for this awesome job :-)


Cannot use NumPy ints for register indices

Information

Qiskit Terra version: master
Python version:
Operating system: osx

What is the current behavior?

import numpy as np
from qiskit import *

arr = np.array([0])
q = QuantumRegister(1,'q')
qc = QuantumCircuit(q)
qc.h(q[arr[0]])

gives
     87         """
     88         if not isinstance(key, (int, slice, list)):
---> 89             raise QiskitError("expected integer or slice index into register")
     90         if isinstance(key, int) and key < 0:
     91             key = self.size + key

QiskitError: 'expected integer or slice index into register'

This is similar to #2152
Steps to reproduce the problem
What is the expected behavior?
I would expect this to work.  Especially since functions like np.random.randint() and np.random.permutation() come in handy when building random circuits, e.g. Quantum Volume.
I label this as a bug because we should be compatible with the dtypes from the foundational numerical Python library.
Suggested solutions
Similar to the one in #2152 by @chriseclectic

I think this casting to python ints should be on the user side. Numpy is too out of our control to make us dependant on it.
Our methods are already very polymorphic. With each new input type, they are getting harder and harder to maintain.

I believe we are already dependent on numpy. In the scientific python community, everyone plays nice with numpy. This is simply extending the isinstance check(s)

We check for int type 54 times in code.

Ok cool. Now we know how many things need to be modified.

Parameters can also be lists... that means that we should also support  circuit.h(np.array([0,1]))? What about circuit.h(np.array([[0,1],[2,3]]))? The answer can be yes to everything, but there is a performance and maintainability price to pay here...

I don't see why we can't follow an approach similar to #2288 here, especially after the consolidation in #2282 . I agree that users having a np.int is probably common enough, and its clear what the expected behavior would be.

It would not be as clean as in #2288 because the extremely polymorphic nature of gate arguments. But if the line is in numpy ints, we can explore options. I'm open to be convinced. Shall the issue be reopen or does @nonhermitian decided was a bad idea?

I'm just worried to open the numpy-type-hell door to an already very cluttered API.

Your comment is not very constructive. The NumPy array typing is very logical, and extensible, allowing you to leverage fast memory-aligned C-arrays via Python.  It is incredibly fast, and allows for array indexing tricks like slicing that make no memory copies.  These benefits, among others, is why every single scientific package in Python (including this one) uses it.  I have closed this issue because you do not seem to want users who use the tools in NumPy to have a seamless experience interfacing with your own software.

@1ucian0 's concern is not a baseless one (considering the difficulty of #2282) and adding support for numpy types in a maintainable way would require some thinking, but I certainly don't think its insurmountable, and given the community interest (e.g #2152, #1898, #2056, #2059, #2151, ...) it seems worth pursuing.

I fully agree that terra should "plays nice with numpy". As I said in https://github.com/Qiskit/qiskit-terra/issues/2152#issuecomment-489111940, probably the cast-before-validate approach can be a good natural limit in the API's input types.
However, I would like to emphasis that a limit in the input type is inevitable (and repeat that there is a performance and maintenance price for casting and type checks).
I will try to add the idea of a best-effort casting in #2282. Reopening while there is a discussion.

The best-effort-type-casting approach:
https://github.com/1ucian0/qiskit-terra/commit/6b36e5dedac4b62f33db34ae1e2a47d189a1ed11

closed via #2288


help with db commands from compose

Trying to import db data in my docker-compose.yml but I can not get a successful build when I include command: something. I would like to do something along the lines of:
command: 'exec mysql -uroot -p$MYSQL_EVN_MYSQL_ROOT_PASSWORD databasename < ./data.sql'

one needs to use a separate container to initialize the db once the db server is running.


Set the domain filter flags based on Domain CR fields

The change adds arguments to the external-dns container based on the values of the fields set in the External DNS custom resource.

/assign @alebedev87 @lmzuccarelli

a nit: the const "/etc/kubernetes" is declared 3 times, in the pod.go,  could we declare it once only (code smell issue refactoring).  Older commit I know.

Executed make test all tests passing. Also pod.go has about 97.3% code coverage - nice :)

/lgtm
Let's see what NetworkEdge guys think @Miciah , @miheer .

/lgtm
/hold for others to review


Bug in synonym creation

Synonyms are not created anymore. Detected by @jbkoh

resolved in https://github.com/BuildSysUniformMetadata/Brick/commit/ccc3912a9cf309083efb6f8a088b98964ffe486e


[PKG-2590] nose2 0.10.0

PKG-2590
dev url: https://github.com/nose-devs/nose2
conda-forge: https://github.com/conda-forge/nose2-feedstock

new package from conda-forge, as an effort of collaboration with Ursa (ursaverance)
version 0.10.0
this is a dependency for allure-python
fix linter
remove noarch

I will go ahead and approve it, assuming Jean-Christophe's comments are addressed

updated to 0.13.0, thanks @marcoesters


flannel-docker-opts.service fails to start

I am deploying a k8s cluster using coreos/matchbox. The deployment is failing b/c of the flannel-docker-opts.service. Flanneld fails to start b/c it depends on flannel-docker-opts.service, which fails to start.
flannel-docker-opts fails to start with this error:
rkt[6407]: rm: unable to resolve UUID from file: open /var/lib/coreos/flannel-wrapper2.uuid: no such file or directory

I noticed the flannel-docker-opts.service unit file contains the following:
ExecStartPre=-/usr/bin/rkt rm --uuid-file=/var/lib/coreos/flannel-wrapper2.uuid
Even though - prefaces the ExecStartPre value, the service still fails. Here is the status of flannel-docker-opts.service
$ systemctl status flannel-docker-opts.service
● flannel-docker-opts.service - flannel docker export service - Network fabric for containers (System Application Container)
   Loaded: loaded (/usr/lib/systemd/system/flannel-docker-opts.service; disabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Tue 2017-03-14 20:47:20 UTC; 521ms ago
     Docs: https://github.com/coreos/flannel
  Process: 42298 ExecStart=/usr/lib/coreos/flannel-wrapper -d /run/flannel/flannel_docker_opts.env -i (code=killed, signal=TERM)
  Process: 42275 ExecStartPre=/usr/bin/rkt rm --uuid-file=/var/lib/coreos/flannel-wrapper2.uuid (code=exited, status=254)
 Main PID: 42298 (code=killed, signal=TERM)

Mar 14 20:46:20 node136 systemd[1]: Starting flannel docker export service - Network fabric for containers (System Application Container)...
Mar 14 20:46:20 node136 rkt[42275]: rm: unable to resolve UUID from file: open /var/lib/coreos/flannel-wrapper2.uuid: no such file or directory
Mar 14 20:46:20 node136 rkt[42275]: rm: failed to remove one or more pods
Mar 14 20:46:20 node136 flannel-wrapper[42298]: + exec /usr/bin/rkt run --uuid-file-save=/var/lib/coreos/flannel-wrapper2.uuid --trust-keys-from-http
Mar 14 20:47:20 node136 systemd[1]: flannel-docker-opts.service: Start operation timed out. Terminating.
Mar 14 20:47:20 node136 systemd[1]: Failed to start flannel docker export service - Network fabric for containers (System Application Container).
Mar 14 20:47:20 node136 systemd[1]: flannel-docker-opts.service: Unit entered failed state.
Mar 14 20:47:20 node136 systemd[1]: flannel-docker-opts.service: Failed with result 'timeout'.

and the system unit file:
# /usr/lib/systemd/system/flannel-docker-opts.service
[Unit]
Description=flannel docker export service - Network fabric for containers (System Application Container)
Documentation=https://github.com/coreos/flannel
After=flannel.service
PartOf=flannel.service
Before=docker.service

[Service]
Type=oneshot
TimeoutStartSec=60

Environment="FLANNEL_IMAGE_TAG=v0.6.2"
Environment="RKT_RUN_ARGS=--uuid-file-save=/var/lib/coreos/flannel-wrapper2.uuid"
Environment="FLANNEL_IMAGE_ARGS=--exec=/opt/bin/mk-docker-opts.sh"

ExecStartPre=-/usr/bin/rkt rm --uuid-file=/var/lib/coreos/flannel-wrapper2.uuid
ExecStart=/usr/lib/coreos/flannel-wrapper -d /run/flannel/flannel_docker_opts.env -i
ExecStop=-/usr/bin/rkt stop --uuid-file=/var/lib/coreos/flannel-wrapper2.uuid

[Install]
WantedBy=multi-user.target

I'm running 1235.9.0:
$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1235.9.0
VERSION_ID=1235.9.0
BUILD_ID=2017-02-02-0235
PRETTY_NAME="Container Linux by CoreOS 1235.9.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

The error it prints is a timeout, and the logs show it did proceed to the rkt run step, so the rkt rm error shouldn't matter (and is expected).
Try increasing TimeoutStartSec=60 to a larger number, or removing the line altogether (default is infinity for oneshot services).

@euank thanks for your help. Looks like it was a network config issue.

@danehans Could you elaborate on the network issue? I'm having problems creating the second EC2 instance. I'm using kube-aws, but if I have more than one etcd, the first one will create successfully and the second one will fail, similarly to yours. If I have only one etcd instance, the first controller will fail to create.

@dimhoLt I'm sorry, but I can't recall the details of my network issue.


rename this repository

For consistency with other OGC API standards, suggest renaming this repository to:
https://github.com/opengeospatial/ogcapi-coverages
Description: An open standard for querying coverage information on the web.
Website: should be URL to draft spec being autogenerated (nightly)?

Please wait. We are drafting an OGC-NA policy on the naming of OGC API repos.

The OGC-NA policy has been approved and the new name of the repo shall be drum roll:
ogcapi-coverages

Please @ghobona could you apply this change? It seems I don't have the rights to do it myself. Thanks

The repository has been renamed to ogcapi-coverages


The key input keeps being entered when I launch tool in WSLg.

Environment
Windows build number: 10.0.22000.258
Your Distribution version: Ubuntu 20.04
Your WSLg version: 1.0.26
Emacs version: 26.3

Steps to reproduce

Launch GUI tools. ex: emacs
Creating a Window with OpenCV in C++. ex: cv::imshow()

WSL logs:

pulseaudio.log
weston.log
versions.txt

WSLg ( x86_64 ): 1.0.26+Branch.main.Sha.26ce2c09b86442f3c7f4f6462f770ed2afa76a25
Mariner: VERSION="1.0.20210224"
FreeRDP: b05321cd4e6a862aef76163a69db4e1910245736
weston: 46756d0e77e5c01b5995fbbee6f3ab0db9b30612
pulseaudio: 2f0f0b8c3872780f15e275fc12899f4564f01bd5
mesa:

stderr.log

Expected behavior
Be like:

Actual behavior
Be like:

When a file is specified as an argument, it often looks like this:

Look at the bottom of the window. It says, "C-c C-c is undefined". Sometimes "c is undefined", "x is undefined", etc ...
After trying several times, it seems that the key that was entered just before closing the previous window is entered the next time the window is launched.
In the stderr.log, there is also a log showing that the key is being typed at high speed.
If you type any key other than Ctrl or Shift, it stops.
When launched with emacs -nw, this problem does not occur.

@GrapeJuicer, thanks for reporting the issue, this is reported at https://github.com/microsoft/wslg/issues/207, and partially fixed already except key modifier which is described at https://github.com/microsoft/wslg/issues/207#issuecomment-938757008. Thanks!


NoUnneededFinalMethodFixer: Remove final keyword from private methods

This PR

[x] adjusts the NoUnneededFinalMethodFixer to also remove an unnecessary final keyword from private methods

tests are failing :(

Please update the PR to target branch 2.6 :)

it's a feature imo

@julienfalque
this PR makes one fixer fix more cases, you call it bugfix (targeting 2.6)
#3089 makes one fixer fix mor cases, you call it feature (targeting master)
https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3089#pullrequestreview-64574596

@keradus I consider this one a bugfix because IMO it's something that should have been part of the initial implementation and is missing, while for #3089 it's not the case. Though I'm fine with considering this one as a new feature as well, your call :)

Picked https://github.com/FriendsOfPHP/PHP-CS-Fixer/tree/2.6 as target branch now.

@localheinz That was actually not needed as @keradus changed the target milestone to 2.7 (current master), which means we consider this a new feature. Sorry for the trouble.

@julienfalque
No problem!

Please rebase and make Travis happy

@julienfalque , you added #3094, which got merged.
could you now verify this PR ?

Thank you @localheinz.

Thank you, @julienfalque and @keradus!

thanks @localheinz and reviewers :D


New documentation content

Following the docs restructuring and replatforming (amazing work, @smythp and @jonvnadelberg!), a next stage of improvements could include new content:

Terminology page

A single page that defines specialized terms (i.e, "witnessing" in the context of transparency)

New user journey

Docs that support users who want to automate Sigstore processes; user journey = “I want to build Sigstore into my tooling or workflow)

Explanation of docs structure

A brief guide about where to house new documentation depending on topic (i.e., tooling repos, docs website, project website) so things stay tidy long term

Opening this issue for discussion, prioritization, and (hopefully) assignments!
@haydentherapper @ltagliaferri @smythp @jonvnadelberg

Unless someone else would prefer to take it on, I can take an initial pass at a terminology page.

Unless someone else would prefer to take it on, I can take an initial pass at a terminology page.

Sounds good to me! Btw, it occurred to me that one of the OpenSSF working groups created a glossary of terms related to supply chain security. Probably no need to recreate the wheel for the terms they've covered; Sigstore's could either focus solely on transparency terms, draw from the OpenSSF's version, or link out to the OpenSSF's with a note to look there for more general terms?

Chainguard Academy also put together a glossary: https://edu.chainguard.dev/software-security/glossary/ (it's CC BY NC so you can grab some terms if you would like).

Following up here!
@smythp has started work on the terminology page and accessibility review, and @jonvnadelberg has finished the documentation location guide (which has been merged).
As for next steps, @jonvnadelberg is interested in creating some self-evident structure for the tooling repos to house developer docs. He is also interested in laying out out the bones for the additional user journey we discussed, about creating Sigstore integrations.
Some questions:

Who is the correct SME to connect with re: documentation needs for the Sigstore integration user journey?
What sort of developer docs will be most useful in the tooling repos? Who are some of the contributors we could connect with here?

@ltagliaferri @haydentherapper

Did we decide on if we wanted developer documentation to live in the docs repo, or live in individual project repos and get synced back?

My recollection is that we were going to keep the project docs in their own repos, but link out to them here. Coming up with ways to mirror them has a lot of maintenance overhead.
Probably we should link to each project under a specific heading on the left sidebar. I just created #250 for it, if anyone would like to advocate for a different approach, let's follow up there.

Agreed, I think it's best to keep the developer docs in the repos and then just link to them, rather than set up a pipeline to pull them in from the repos to the website docs.


ng update @angular/cli

[ X ] Bug
version 6.0.0-rc.2+
Repro steps
Migrate a previous 1.6 project that has three styles files configured
Observed behavior
subsequent angular-cli.json files wont build

workaround
              "styles": [
                  {
                      "input": "src/styles.scss"
                  }
              ],

Heya, can you give me a repro I can follow to see that? The paths look right to me. How does it fail building?

I am closing this
sorry for distraction
I confused the output with this bug
https://github.com/angular/angular-cli/issues/9994
build system seems to be in major play...
praying for some kind of workaround from this one https://github.com/angular/angular-cli/issues/9994


Archetypes not working from theme

Archetypes are working from my project root, but not from themes.
For getting them to work from my project root I had to add empty line returns (similar to the workaround here: https://github.com/spf13/hugo/issues/359).
Ideas?

If it's caused by the same reason of #359, it's also the same with #776

Should be fixed by #785

I still have the issue on hugo 0.19 and master.  I've created a repository here.

Me too, I'm compiling from source via go get.

Fixed in 0.20, this issue can now be clos...  Oh.


translate: support percentage values

Adds support for percentage values when using translate.
This is a new feature in React Native 0.75: https://reactnative.dev/blog/2024/08/12/release-0.75#percentage-values-in-translation
ping @jacobp100

Thanks!

Oh that was quick, thanks! Could you also prepare a new minor release?

IIRC Max does the releases
@mxstbr

@jacobp100 looks like nothing has happened related to the new version.
Are you not able to prepare a new release?

I don’t have publishing rights

ok, understood. Let's try to ping Max again. @mxstbr


refactor: update wallet creation screen order

:books: Linear Ticket :books:
LIQ-702

@Jennievon Can you please update the E2E tests, looks like screen order changes all test failed


Add option to strip kernelspec metadata from notebooks with pre-commit

Goal: Avoid having weird non default kernels specified by accident in notebooks.
Context: If an unknown kernel is specified, local jupyter sessions will popup to ask for selecting among existing kernels. Testing notebooks with pytest --nbmake will crash.
Pros:
When removing the entire field "kernelspec" from metadatas, the notebooks will open in jupyter with the default kernel which is python3. This will also work with pytest --nbmake when testing notebooks.
Cons:
When saving the notebooks from a local Jupyter session, the kernelspec metadata will be restored. So the pre-commit will probably complain after each change if it has been installed as a git hook. So that pre-commit will need to be performed after each change.

Cf https://github.com/kynan/nbstripout/issues/141

IMO cons outweigh pros.

Ok. Another solution could be to modify inplace the name of the kernel for python3. And yet another one to trust people will not do as i did.
Actually, once the notebooks will be tested during CI, we will have a test failing thus it is ok for me. (cf #121)

Ok. Another solution could be to modify inplace the name of the kernel for python3.[...]

That would be safer, yes.

@nhuet thanks for raising the crash bug. Will fix in the next week https://github.com/treebeardtech/nbmake/issues/37


Migrating over to Availity-React

We are considering merging the components here into the availity-react repo so we can have everything managed in one place. We can do a run through of all the open issues here and consider any breaking changes for the v1.0.0 on availity-react.
@TheSharpieOne  I wanted to get your thoughts on this because we also have considered re-writing the validation using Formik once v2 gets published with hooks.
There are obviously trade offs to both and at its current state its not worth re-writing with Formik until its stable with v2.

rewriting using Formik was one of the things considered. Formik has some drawbacks. FastField fixed one of them; kinda. Validation schema is another.
This library supported an already existing validation schema within Availity. Formik only supports Yup for validation schema. Another thing this library helps with is A11y. It will take a validation schema and apply the correct attributes (for things like required, min, max, email, date, etc). Yup doesn't let you determine what validations are configured in the schema (you can't determine whether a field is required or what validations are being applied based on the schema).
Not sure if any of that is going to change in Formik v2.
I also looked at Final Form React, and it looked very nice and probably fit in a bit better.
The main point of this library was to get the Availity branded look and feel (along with A11y) without making the developer have to do much work for 90% of the forms. By that I mean: Developers wouldn't need to worry about invalid fields, validations, and error messages.
Obvious a lot of that can be abstracted into the components which would become availity-reactstrap-validation no matter which library it is designed to work with.

Formik discussion about a11y and required fields:

https://github.com/jaredpalmer/formik/issues/712
https://github.com/jaredpalmer/formik/issues/1241

required is just one example. If any of the HTML5 validations are used (such as min and max on number/date types, minlength, maxlength, pattern on text types, etc.), they should appear as attributes. It informs the screen readers what values are allowed.

Agreed. Just noting for future reference in case the Formik discussion comes up again. Trying to minimize the amount of API footprint we maintain but you have made convincing arguments if favor of accessibility.
Closing since this lib can be useful as standalone so I think moving to availity-react won't be confusing. Probably going to upgrade the dev tools in future PR to keep things consistent.


"options" button disappearing

The options button disappeared after I selected "hide header" within the options menu itself. I don't know if there is a way to bring it back or if this is intended, but after reinstalling it's still gone and I can't see a way to access the settings any longer.

so I had to uninstall, then load the save, then save that save without the mod installed, then reinstall the mod and load that save up to get it to reset and access the options again. Not sure if I was just missing a way to get it back or not, but I couldn't figure out another way.

There's a hotkey in your controls that can toggle the setting back on. Thank you to the mod author for pointing it out to me!


remove arbitrary multiplication case

adds the wrongly simplified kernel in test_linearizer_failures #7019

test training with this in https://wandb.ai/chenyuxyz/MLPerf-BERT/runs/ygl1c94c/overview

Hmm, why is it wrong? The NaN thing?


No messaging for other events than "no choice selected on votes"

No confirmation messages for changing a vote and invalid url redirect messages
also remove the error_message variable in votes!

DONE Now it has confirmation messages for a vote, blank vote, and changed vote, and also remove the error_message variable in votes!


Errors when running the script

Hi:
Thanks for your works, saving lots of time!
I helped two friends setting up this tool, but they encountered different problems:
The first one, it can't find the expected Chromium (even after npm i chromium)
The second one, it can't launch the browser process. Went to puppeteer's troubleshooting page but can't find much help. What can I do for them? Thanks!

![Error-2 1](https://user-images.githubusercontent.com/20261800/114324126-10232500-9b5b-11eb-87ef-d08b00c3a2df.png)

Hi there - have you tried lately? I hit this issue once and since I updated puppeteer in the project it seems to work fine to find the browser..


[DevSpaces]: Add targetContainerHostApiServerFqdn to controller resource

…rce model
(cherry picked from commit 506f8d3e49495d8b394f9a663a8f5c595da64048)
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

@sanar-microsoft Hello. Could you solve the CI errors and I can merge this PR.

@MyronFanQiu I got an exception for suppressing the semantic error from Ray:
```
code: 'SEMANTIC_VALIDATION_ERROR',
id: 'OAV119',
innerError:
code: 'OAV131',
error: 'DISCRIMINATOR_NOT_REQUIRED'

I'll get this fixed in the next API version of the RP.

@sanar-microsoft Sure. You can add the suppression in this PR.

/azp run automation - sdk

@MyronFanQiu I added suppression, but apparently that way is not correct. Can you let me know how to add/fix it? Also, how to run prettier check locally?

@sanar-microsoft about prettiercheck you can follow this instrucment.
https://dev.azure.com/azure-sdk/public/_build/results?buildId=253850&view=logs&j=b56e9678-4dad-5642-289c-5530cc4dad11&t=9e18c5d1-dc43-58a1-0344-6ef37d05bd7f&l=34

@raych1 Hello. Could you help check the suppression? Meanwhile, is there a doc to teach us how to add suppression?

/azp run automation - sdk

@raych1 Hello. Could you help check the suppression? Meanwhile, is there a doc to teach us how to add suppression?

@sanar-microsoft , please refer to this readme and search for oav131 in page. // CC @MyronFanQiu

/azp run automation - sdk

@raych1 I added it to the readme, but the same check failed. Is there something missing here?

@sanar-microsoft , try this:
Suppression
directive:
  - from: devspaces.json
    suppress: OAV131
    reason: Testing purpose.

/azp run automation - sdk

/azp run automation - sdk

@MyronFanQiu I've fixed the suppression, please take a look. The issue was due to a typo, "Suppressions" vs "Suppression"
@raych1 Thank you for the help


Trying out Infinispan as redis service

From https://infinispan.org/docs/stable/titles/resp/resp-endpoint.html
Infinispan Server includes an experimental module that implements the [RESP3 protocol](https://github.com/redis/redis-specifications/blob/master/protocol/RESP3.md). The RESP endpoint allows Redis clients to connect to one or several Infinispan-backed RESP servers and perform cache operations.

The main objective is to assess infinispan compatibility configured as redis backend of limitador. Performance benchmarking would also be interesting to know.

I've managed to get Limitador to connect to the Infinispan RESP endpoint, however the current implementation of limitador relies on several RESP commands which are not yet supported by infinispan.

INCRBY
SADD
PTTL

These are used in the calls to Redis so to get this to function we'd have to rewrite it without them (or wait and see if they become supported by infinispan).

I am going to close this as "won't fix". Two out of these 3 unsupported functions are actually core to how we do things with Redis today. I don't see any reasons to change this. Even less so to support Infinispan, so unless they add support for these functions, we probably have to keep on relying on the experimental support for Infinispan as it is currently built.