Specifying a new readiness probe using an ops-file doesn't recreate the pod

On KubeCF, when I try to upgrade an existing installation to update a readiness probe, the pod doesn't get recreated.

I tried to reproduce this issue. And desired manifest has added the proper item: quarks.run.healthcheck. But quarks job ig didn't create new version of IG. Maybe it was equal to older one.

Opened a PR: https://github.com/cloudfoundry-incubator/cf-operator/pull/841
Hi, I examined the code changes thru this manifest to update:
https://github.com/cloudfoundry-incubator/cf-operator/blob/92f5724c205f4fc953cb4fb6d2da89e6fe81e86b/docs/examples/bosh-deployment/boshdeployment.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: nats-manifest
data:
  manifest: |
    ---
    name: nats-deployment
    releases:
    - name: nats
      version: "26"
      url: docker.io/cfcontainerization
      stemcell:
        os: opensuse-42.3
        version: 30.g9c91e77-30.80-7.0.0_257.gb97ced55
    instance_groups:
    - name: nats
      instances: 1
      jobs:
      - name: nats
        release: nats
        properties:
          nats:
            user: admin
            password: ((nats_password))
          quarks:
            ports:
            - name: "nats"
              protocol: "TCP"
              internal: 4222
            - name: "nats-routes"
              protocol: TCP
              internal: 4223
            run:
              healthcheck:
                nats:
                  readiness:
                    exec:
                      command:
                      - "echo healthy"

I could see quarksStatefulset changed about readinessProbe:
apiVersion: quarks.cloudfoundry.org/v1alpha1
kind: QuarksStatefulSet
metadata:
...
  name: nats-deployment-nats
  namespace: staging
...
spec:
  template:
    spec:
        spec:
          containers:
          - name: nats-nats
            readinessProbe:
              exec:
                command:
                - echo healthy


Script cannot detect static functions or static variables

static var and static func

static func should work but right now the plugin can indeed not detect static var.
For some reason they are handled different on Godot, there is currently no way to get them for the current script.

I thought the variables are read from the code itself


Update broccoli-caching-writer to use ^3.0.3

Thanks. Why is this required?

@aexmachina just keeping stuff up to date.

👍

Does this require a major version increment of this module?

@aexmachina I don't think it's required, can you release please?

Yes will do when I get off this train :)
On Wed, 17 Aug 2016 at 8:26 AM, huiyuan<EMAIL_ADDRESS>wrote:

@aexmachina https://github.com/aexmachina I don't think it's required,
can you release please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aexmachina/broccoli-sass-source-maps/pull/21#issuecomment-240259108,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP-rEIbdlHPbvAq9kl2riPPjs6X9S7jks5qgjktgaJpZM4Jk06t
.

Pushed v1.8.1.
--
Simon Wade
aexmachina.info
github.com/aexmachina
twitter.com/aexmachina
linkedin.com/pub/simon-wade/1/a34/566
On 17 August 2016 at 08:36, Simon Wade<EMAIL_ADDRESS>wrote:

Yes will do when I get off this train :)
On Wed, 17 Aug 2016 at 8:26 AM, huiyuan<EMAIL_ADDRESS>wrote:

@aexmachina https://github.com/aexmachina I don't think it's required,
can you release please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aexmachina/broccoli-sass-source-maps/pull/21#issuecomment-240259108,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP-rEIbdlHPbvAq9kl2riPPjs6X9S7jks5qgjktgaJpZM4Jk06t
.


restructure solar energy

closes #663

reclassify solar energy as subclass of radiative energy
add solar energy transformation and subclasses thermal energy transformation and photovoltaic energy transformation

Ok, that's really weird. I do always create a new branch and pull from dev, but the program seems to do something different 😮
I thinks it's safer to delete these branches and start over.
I already restored the old wind energy class in #666 btw.

Maybe this helps making clear what happened:

As I understand it, it all started with radiative energy on which wind energy is based. potential energy and solar energy are both based on wind energy, but solar energy is missing the last commit from wind energy(restore old wind energy class). fix secondary energy carrier is based on potential energy, but not on the newest version.
I don't think we have to redo all these branches, we just have to fix some merge conflicts if they arise.


add support for generating test results and coverage

will merge all reports into the same directory in issue #5

merged #4


[VS Code] [Audio] read ECONNRESET

%0A%0A%23%23 Error:%0Aread ECONNRESET%0A%0A%23%23 Steps to Reproduce:%0A1.%0A2.%0A%0A||Version Data|%0A|-:|:-|%0A|**extensionName**|VSLS-Audio|%0A|**extensionVersion**|0.1.51|%0A|**applicationName**|VSCode|%0A|**applicationVersion**|1.35.1|%0A|**platformName**|Windows|%0A|**platformVersion**|18.6.0|

Hi @mengbingchen0214 , thank you for reporting the issue. Would you give us some more information to investigate ? Does this consistently happen for you or happened once ? Also , your logs may provide us with helpful information. You can access them via the "Live Share: Export Logs" command from the command palette (ctrl + shift + p) and attach them to the issue. Adding @jramsay to follow up

@mengbingchen0214: Thanks for reporting this issue! We have made some significant updates to our audio extension with the latest release (0.1.60). I'm going to close this issue but if you're still experiencing problems with the latest extension, it would be helpful for our investigation if you uploaded your logs here. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.


NIFI-5791: Add Apache Daffodil (incubating) bundle

Adds a new daffodil bundle containing two processors (DaffodilParse and
DaffodilUnparse) used to convert fixed format data to XML or JSON using
Apache Daffodil and DFDL schemas.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

[X] Is your initial contribution a single, squashed commit?

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[X] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[X] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[X] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[X] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

First of all this looks like a really thought out contribution and huge thanks for taking the time to create what looks like a well done NOTICE file!
I'm not sure about the naming/intent that is communicated to the user.  And in general we try to name things VerbSubject style.  What are some other names to consider?

Not related to the naming discussions but would it make sense to consider a DFDLReader and a DFDLWriter implementation? Didn't look into the code but since it can parse/unparse into JSON, it should be doable? It would be a nice addition.

I'm not too familiar with the Reader/Writer idiom. From what I can tell, a Reader converts data to a Record, and a Writer converts those Records back to the data format? Is that accurate? My one concern is that although DFDL/Daffodil can handle record oriented data, often times it is much more complex. For example, the daffodil examples page shows two examples of how DFDL can convert data to XML. The first example is CSV data and is clearly record oriented. But the second example is PCAP (used in the above template) which could be seen as records, but is a complex nesting and there's a global header that isn't really a record. Most data formats we've seen DFDL used for a more like the latter.
The SchemaRegistry concept that looks to be used by Readers/Writers seems like a really nice way to provide a DFDL schema (if possible without using the Records?), but I'm not sure how well the Record concept fits in. Does it make sense to keep the XML/JSON output as in the PR, and then if a particular infoset does map well to a Record the user could add a JSON/XMLReader to convert to a record?

Isn't this like the Jolt capability?

From my understanding of Jolt, this capability is pretty different.
Jolt reads JSON data, performs various transformations as described by a JOLT specification, and then writes out back to JSON.
Daffodil/DFDL (Data Format Description Language) on the other hand, reads a wide array of data formats (text, binary, scientific, military, financial, etc.) and parses the data format as described by a DFDL schema (see @DFDLSchemas for some publicly available schemas), and outputs the data to an infoset, which can be projected into XML or JSON for consumption. It is also capable of the reverse, by reading in the XML/JSON infoset and "unparsing" it back to the original data format.
So while JOLT is a transformation from JSON to JSON, Daffodil/DFDL could be considered a transformation from arbitrary data to XML or JSON, as described by a DFDL schema.

What I mean is that from a high level, it is a transformational capability, and may be used as an alternative.

Ah yes, you are correct.

Actually, I should probably add a little more clarification.
It is correct to say that Daffodil could be considered a transformation capability, but I'm not sure it could really be seen as an alternative to Jolt specifically.
One could definitely write a DFDL schema to describe and parse JSON data, similar to what Jolt can do, but the resulting infoset would just be JSON that is probably more generic and less useful that what Jolt would create. Daffodil does not have the same transformational capabilities that Jolt has (e.g. filtering, sorting, reordering). It really just takes a data format that is not natively supported and transforms it to a logically similar representation in a natively supported format (i.e. XML/JSON). If your data is already in something like XML or JSON, it doesn't really make sense to use Daffodil.
So for example, you might take PCAP data, like in the above template, and feed it through Daffodill to transform it to JSON. But there might be extraneous data that Daffodil parsed that you don't need or care about. So you might then feed that JSON through Jolt to to transform it to something that has only the fields you care about, or is reordered/renamed to be something more useful to ones usecase.
So this isn't something that could be viewed as an alternative to Jolt, but more like something that could be used in conjunction with Jolt to allow one to transform JSON data that wasn't originally JSON.

Thanks for taking the time to explain further.  I see what you mean.  Nifi needs a better way to get across to users when to use what processor in general.

This is interesting stuff, I need to read more up on DFDL, might make a good schema definition language as an alternative to Avro schemas. Also at first glance it seems the Daffodil infoset is analogous to a NiFi Record for data, and/or a NiFi RecordSchema for its schema. Having an infoset as the underlying data model seems to overlap a bit with how the NiFi Record stuff works, for example we could have a PCAPReader and any writer such as JSONWriter, then the ConvertRecord processor can convert PCAP to JSON. I think someone was working on a PCAP reader, not sure how they handled the global stuff. If Avro schemas are not sufficient to capture this kind of model, then we should definitely look at DFDL as an alternative (we've been considering XSD as a more expressive alternative).
Quick note about JOLT, the "normal" use case is for JSON-to-JSON conversion, but the underlying library does the transformation on a POJO, not JSON. So the usual entry point for JOLT is to give it a JSON string, it converts to a POJO, runs the transformation, and takes the resulting POJO and writes it out as JSON. In NiFi I wrote JoltTransformRecord, which instead of explicit JSON uses the NiFi Record API, so it gets each record (in whichever format) as a NiFi Record, translates it to a POJO, then runs the JOLT transforms, then translates back into a NiFi Record, which is written out in whatever format is specified by the RecordWriter.

After some research and reading the Avro specification , I'd agree that the DFDL infoset does seem somewhat similar to a Record.
DFDL does support all the primitive types (null, boolean, int, long, float, double, bytes, string) and logical types (date, time, decimal), plus a few others (integer, byte, short, signed/unsigned) . But as far as complex types, it only really supports "records" and arrays. Below is the list of things in Avro that the DFDL infoset does not support:

It sort of supports enums, but only in the sense that it can validate that a primitive type is one of the valid enum values via the xsd:restriction.
Maps. In DFDL, a map would be implemented as a sequence of key/value pairs, so there wouldn't be any enforcement of unique keys.
Unions. Each element in the infoset must have an explicit primitive type. Each element can be optional or nulled, but cannot be a union of multiple primitive types. In DFDL, that is handled by an xs:choice of two different elements with different types and some method (often a discriminator) to determine which branch of the choice.
Namespaces are slightly different, but probably similar enough. DFDL uses XML namespacing.
Aliases are not supported.
Sort order. DFDL outputs infoset elements in the order in which they appear in schema.
The DFDL infoset does not contain the schema. One must keep track of the associated schema outside of the data.
The isn't really a concept of different serializations like Avro looks to have. Instead, the DFDL schema defines the physical data format via DFDL annotations, which are used to determine how to serialize/deserialize data. Theoretically, one could have different schemas with the same logical format but with with different DFDL annotations to describe physical formats, but that isn't a comment use case we've come across.

The Daffodil devs would be happen to discuss the possibility of integrating Daffodil/DFDL as an alternative to Avro. Not sure if any of the above limitations are blockers. The core of Avro and DFDL definitely do seem to have some overlap.

Reading over the comments here, I'm wondering if it would make sense to consider creating a wrapper around our record readers for this instead of going to a straight competition with Avro. For example, I could see potential with the PCAP example reading the PCAP data into JSON and then transforming the JSON into Avro by having a DaffodilReader that could wrap JsonTreeReader and emit JSON to the reader. Thoughts?

That doesn't seem totally unreasonble to me. I'm relatievely new to the Record/Avro concept. It sounds to me like to take that route we would need to convert the DFDL schema to an Avro schema that the wrapped JsonTreeReader would use to parse the Daffodil-created JSON? Daffodil doesn't currently have an API to do that, so we'd need to develop that.
If instead Daffodil were to create Records directly like mentioned in previous comments, would something like that converter still be necessary? Or can one build up records without really having a concept of a schema?

Or can one build up records without really having a concept of a schema?

In 1.9, we can do schema inference, but I wasn't thinking schemaless here. If someone uses Daffodil to convert data the way you did in your sample, they should be able to create an Avro schema that matches the output of Daffodil (at least in most cases).

Yep, but most of the military related scheas have restricted access due to the nature of the formats. The following are current available on DI2E.net if you have access to that, under the "DFDL/Daffodil" project. Some schemas are more complete and more tested than others:

USMTF
VMF
Link16
USCG UCOP
AGNOSC Remedy
Army DRRS
CEF
GMTIF

The MIL-STD-2045 schema is publicly available on GitHub if you want an idea of how something like VMF or Link16 might be described in DFDL.
I haven't heard of ICPUBS--as far as I know a schema for that has not been developed.

@stevedlawrence I think this is a legit download of the PUBS specification. It's a rather comprehensive XML data format with all that that implies and insinuates.

@MikeThomsen DFDL/Daffodil aren't really designed or intended to parse XML data like PUBS. It's theoretically possible, but it's a pain. Generally we reccomend if your data is already in XML then it's beset tod just use one of they XML parsers out there. Where Daffodil really shines is when the data isn't in XML or some readily accessable format. In that case, Daffodil can be used to convert the data to XML so that is is more readily accessable.
Note that often times the XML you get out of of Daffodil doesn't match what you soemtimes want, due to restrcitions on how DFDL schemas are written and how infoset are represented in XML. For example, MTFXML is a standard that tries to describe USMTF data but in a XML format. Daffodil is not able to convert USMTF data directly to MTFXML. If that was the goal, one would describe USMTF data with a DFDL schema, parse it to an XML representation using Daffodil. and then transform that XML to MTFXML via something like XSLT.

closing due to inactivity


Wrong calculation of Reynolds number for non-circular pipes

Reported by A.Taeschner on 10 Nov 2014 12:13 UTC
I found a severe bug in the Fluid library when calculating the pressure drop of noncircular pipes where the cross area A is not given by A=pi/4*d*d anymore. The bug is in line 3422 of Modelica/Fluid/Pipes.mo:
Re :=(4/pi)*abs(m_flow)/(diameter*mu);
This equation is only correct for circular pipes, but for arbitrary pipes it has to be:
Re :=abs(m_flow)*diameter/(crossArea*mu);
This seems to be not the only line where the wrong assumption (A=pi/4*d*d) has been used, but I had no time to investigate this further.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1601

Modified by beutlich on 13 Nov 2014 11:35 UTC

Modified by dietmarw on 17 Dec 2014 09:59 UTC

Comment by A.Taeschner on 5 Jan 2015 10:53 UTC
In the newly attached example two pipes are used to demonstrate the problem:
Both are connected to a pT source (water, 293.15 K, 10 bar) and a mass flow sink (0.1 kg/s inflow).
1.) circular pipe (100 m length, 10 mm diameter)
According to the site http://www.pressure-drop.com/ one would expect a pressure drop of 2.67576 bar leading to an outlet pressure of about 7.324 bar at the end of the pipe. This can be reproduced by the model.
2.) circular ring pipe (100 m length, 5 mm inner diameter, 15 mm outer diameter)
Here one would expect a pressure drop of 0.76932 bar leading to an outlet pressure of about 9.231 bar at the end of the pipe.
The current version of the library gives 7.324 bar and the patched one 9.231 bar.

Comment by rfranke on 6 Jan 2015 14:39 UTC
Thank you for the patch and the example!
Would you mind to add some HTML docu and author info to NonCircularPipes.mo? I'd like to add it to Fluid under Modelica.Fluid.Examples.NonCircularPipes.

Comment by Alexander Täschner on 6 Jan 2015 15:15 UTC
I added a new file with some documentation. Since I was not sure where to add the author info, I simply wrote them in the revision section. If there is another better location please feel free to move this info.

Comment by rfranke on 6 Jan 2015 21:46 UTC
SVN 29a67410d01a196bb2671f3ef4ede06b581ade48 introduces your example and the fix basing on your patch. The default DetailedPipeFlow model works for non-circular pipes now, besides the Laminar and the NoFriction model.
The (LaminarAnd)QuadraticTurbulent models still need to be fixed.

Comment by rfranke on 7 Jan 2015 15:50 UTC
It appears not trivial to support non-circular tubes with the linear laminar and quadratic turbulent flow models. In particular the assumptions about laminar flow would require additional input.
This is why SVN dfd83acde0ac1fc2bcd712cae923738036dfc05a adds assertions and clarifications to the doc strings.
Following the proposal in this ticket, non-circular tubes work with the default DetailedPipeFlow model now.

Comment by beutlich on 7 Jan 2015 21:58 UTC
Ticket was fixed in trunk only but milestone is set to MSL 3.2.1+build.3. Either merge 29a67410d01a196bb2671f3ef4ede06b581ade48, 8c23c5c2b9218141a48e7a50770262198e97fef0 and dfd83acde0ac1fc2bcd712cae923738036dfc05a to MSL 3.2.1 maintenance branch or correct mileston to MSL 3.2.2. First option probably is the preferred one. Thanks.

Comment by rfranke on 8 Jan 2015 15:20 UTC
see e0d5a19cc6a6b1556aa941cecfc35293824a7c34


nixos/less: add configuration assertions

Motivation for this change
Instead of silently overriding values the user has configured for commands, clearDefaultCommands, lineEditingKeys, or envVariables, prevent the system from building a conflicted configuration and tell the user what's causing the conflict.
Addresses https://github.com/NixOS/nixpkgs/pull/38629#commitcomment-33066989
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

Just played around with this locally and pushed a commit that documents this in the release notes. As soon as ofborg has finished its evaluations, we can merge this :+1:

I broke ofborg. Rolling back, deploying, and then will re-evaluate.

@GrahamcOfBorg eval

I don't like this idea for multiple reasons:

When a different nixpkgs module sets e.g. envVariables, and the user wants to override the configFile, you can't do this with this change, as you don't have control over that module to unset envVariables.
We have many more options in NixOS already that "silently" defuse other options, but that's just how the module system works with priorities. You provide some special options that write a config file in a special way, but you also allow configFile if you want to override everything. To me it's clear that such configFile options override other options, and when we put this in the option description, it's even clearer.
These assertions are very bulky and written manually. I don't want to see this all over NixOS modules just for a tiny advantage (which might not even be an advantage, see point 1)

@Infinisil I think you're right. I'm closing this PR.

When a different nixpkgs module sets e.g. envVariables, and the user wants to override the configFile, you can't do this with this change, as you don't have control over that module to unset envVariables.

Isn't it possible to use priorities like this here:
{ lib, ... }:

{
  programs.less = {
    envVariables = lib.mkForce {};
  };
}

We have many more options in NixOS already that "silently" defuse other options, but that's just how the module system works with priorities

Well it makes perfect sense with the concept of priorities, but this isn't used in the less module, right?

To me it's clear that such configFile options override other options, and when we put this in the option description, it's even clearer.

When I remember me while trying to learn NixOS two years ago I screwed a lot of stuff up at first due to some misunderstandings, so I have to admit that I don't understand why we should save 4 options that are potentially helpful, especially for beginners :)

Ah yeah, using mkForce would work, but it's still weird to have to explicitly mkForce {} if you didn't set this option in your own configuration to get rid of an assertion failure.

Well it makes perfect sense with the concept of priorities, but this isn't used in the less module, right?

Oh you're right, the module doesn't use priorities as I thought it would:
https://github.com/NixOS/nixpkgs/blob/c7997510ae9598ef5ace4aa87564a651b64c3246/nixos/modules/programs/less.nix#L9-L11
Usually you'd implement this by using configFile = mkDefault generatedConfigFile, then you wouldn't need nullOr in its type, and people could nixos-option ..configFile to see what the config file is in any case. (I also just noticed that this module uses builtins.readFile on the configFile, which is bad because it disallows config files that depend on derivations)

I have to admit that I don't understand why we should save 4 options that are potentially helpful, especially for beginners :)

In addition to the first point (which should be enough reason on its own), I don't think we should have this because these priority overrides are all over the place in NixOS, and we can't guard against them all (well we could, but that would be a pain). If we had something builtin in the module system to warn us (not error out at least) that would be better (but then again, we have no way to turn off warnings, and you sometimes want to override other options without getting a warning).
Here's some more examples of options overriding other options: systemd.sevices.<name>.serviceConfig.ExecStart overrides systemd.services.<name>.script (and there's many more of such in systemd), many configFile/passwordFile options, environment.etc.<name>.source overrides environment.etc.<name>.text, programs.bash.shellAliases overrides environment.shellAliases, and more.

Ah yeah, using mkForce would work, but it's still weird to have to explicitly mkForce {} if you didn't set this option in your own configuration to get rid of an assertion failure.

I'm afraid I have to disagree here: a hypothetical third-party module for less expects those options to have a certain value to function properly. IMHO explicitly overriding values basically means that you leave a supported "path" and you'll probably experience edge-cases.
I always think twice before using mkForce to achieve something, so I consider such a behavior actually a good thing :sweat_smile:

Here's some more examples of options overriding other options: systemd.sevices..serviceConfig.ExecStart overrides systemd.services..script (and there's many more of such in systemd), many configFile/passwordFile options, environment.etc..source overrides environment.etc..text, programs.bash.shellAliases overrides environment.shellAliases, and more.

I'm probably missing something, but having i.e. ExecStart and script set causes an evaluation error as I'd expect:
error: The unique option `systemd.services.foo.serviceConfig.ExecStart' is defined multiple times, in `<unknown-file>' and `/home/ma27/Projects/nixpkgs/nixos/modules/system/boot/systemd.nix'.

{programs.bash,environment}.shellAliases seem to be merged together, but you're right, single keys might override each other.

Usually you'd implement this by using configFile = mkDefault generatedConfigFile, then you wouldn't need nullOr in its type, and people could nixos-option ..configFile to see what the config file is in any case. (I also just noticed that this module uses builtins.readFile on the configFile, which is bad because it disallows config files that depend on derivations)

Hmm that sounds in fact way better. Another option that came to my mind was to provide some kind of extraConfig, but that would make merging inside the module system harder again.

Yeah the mkForce point is a good one upon second thought. Ah and yeah the script and ExecStart options I didn't check.
If people really want to see more such assertions, I wouldn't mind seeing a small RFC for this that lists advantages/disadvantages and such.


Editor is blank

Just logged on to transcribe and everything I try to see comes up as a black page. I tried Rahmat Khan and Abdul Karim Khan.

@Dard-Neuman Should be fixed now


Fixed App Crash on Tablets

Description
Fixed App Crash on Tablets
Fixes #2766 App Crashing on Tablets
Tests performed
Tested betaDebug on Nexus 9 with API level 28 stock android.

Codecov Report

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

@@          Coverage Diff           @@
##           master   #2787   +/-   ##
======================================
  Coverage    2.84%   2.84%
======================================
  Files         268     268
  Lines       12735   12735
  Branches     1127    1127
======================================
  Hits          362     362
  Misses      12348   12348
  Partials       25      25

Continue to review full report at Codecov.

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

Tested 2.10.1-debug-issue-2766~5e8a57a6e


[DPE-3905] - Large deployment relations - Integration tests

Issue
This PR implements DPE-3905. Namely, this PR implements:

Integration tests for Large deployment relations

I am seeing: https://github.com/canonical/opensearch-operator/issues/287

Proposal: https://github.com/canonical/opensearch-operator/pull/288


[BYOC] Refine DNNL Codegen

With multiple output and merge compiler region support, we can now refine the DNNL codegen to support ops with multiple outputs such as batch_norm. This PR:

Support operators with multiple outputs.
Fix the issue that the second fuse run in VM will go into external functions and decompose batch_norm.
Turn on DNNL batch_norm.
Fix TupleGeItem in DNNL codegen.
Skip MobileNet test because of the constant node issue for now.

cc @zhiics, @masahi.

Thanks @comaniac @zhiics


RangeError: RangeError (index): Invalid value: Only valid value is 0: 1 at completion_ranking.dart:69

RangeError: RangeError (index): Invalid value: Only valid value is 0: 1

at List.[]	(dart:core )
at CompletionRanking.makeRequest	(completion_ranking.dart:69 )
at CompletionRanking.predict	(completion_ranking.dart:91 )
at DartCompletionManager.computeSuggestions	(completion_manager.dart:105 )
at <asynchronous gap>	(async )
at CompletionDomainHandler.computeSuggestions	(domain_completion.dart:125 )
at <asynchronous gap>	(async )
at CompletionDomainHandler.processRequest	(domain_completion.dart:363 )
at <asynchronous gap>	(async )
at CompletionDomainHandler.handleRequest.<fn>	(domain_completion.dart:249 )
at runZoned	(dart:async )
at CompletionDomainHandler.handleRequest	(domain_completion.dart:242 )
at AnalysisServer.handleRequest.<fn>.<fn>	(analysis_server.dart:333 )
at _PerformanceTagImpl.makeCurrentWhile	(utilities_general.dart:258 )
at AnalysisServer.handleRequest.<fn>	(analysis_server.dart:329 )
at runZoned	(dart:async )
at AnalysisServer.handleRequest	(analysis_server.dart:328 )
at ByteStreamServerChannel._readRequest.<fn>	(byte_stream_channel.dart:189 )
at _PerformanceTagImpl.makeCurrentWhile	(utilities_general.dart:258 )
at ByteStreamServerChannel._readRequest	(byte_stream_channel.dart:179 )
at ByteStreamServerChannel.listen.<fn>	(byte_stream_channel.dart:120 )

@lambdabaa @bwilkerson

https://dart-review.googlesource.com/c/sdk/+/126600


Adding support for bicep

Now that bicep is supported we should add support for it.
We should also consider using https://hub.docker.com/_/microsoft-azure-powershell?tab=description as base image we could avoid installing AZ manually.

This should be fixed by #6


The URL used in utils/constants.py is no longer valid

Try to this webpages and this one.

For the following readers: See this for more details.


Add-on fails to start; can't open file '/usr/app/main.py'

After upgrading to version 2.0.8 (latest as of time of writing), the container no longer starts. It looks like the problem is python3: can't open file '/usr/app/main.py': [Errno 2] No such file or directory. Here are the full logs:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun isponsorblocktv (no readiness notification)
s6-rc: info: service legacy-services successfully started
[10:08:24] INFO: Starting...
python3: can't open file '/usr/app/main.py': [Errno 2] No such file or directory
[09:08:25] WARNING: Halt add-on with exit code 2
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Im getting the exact same error. Even a fresh install keeps getting errro “ can't open file '/usr/app/main.py”

Yup I can reproduce this here, there are some changes to the upstream project structure that likely caused this (and the fact I pushed a release without testing it, apologies for that I was attempting to help another user with a different issue)

Simple problem, simple fix. Hopefully this works now. Please let me know if you encounter any more issues.
I'll try and be a bit more careful when rolling a release.

Simple problem, simple fix. Hopefully this works now in 2.0.9 Please let me know if you encounter any more issues.
I'll try and be a bit more careful when rolling a release.

Fixed! Thank you so much for the quick reply. LOVE this addon!


Add option to enable/disable ble service change registration

Add option to enable/disable automatic registration of BLE Gattc
service change notify. Which sends in paralel
(with user message flow) commands to BLE server which
sometime leads to GATT_BUSY.
Solving Issue 1575

Hi @jedi7 ,
Sorry for the delay in getting back to you.
For a new CONFIG_xxx option to be added to ESP-IDF, it will need a corresponding config item and description in the bt Kconfig file. Could you add one to this PR, please?
https://github.com/espressif/esp-idf/blob/master/components/bt/Kconfig
@Yulong-espressif @Weijian-Espressif @TianHao-Espressif Can you please take a look and provide further review comments? Thanks.
Angus

Hi @projectgus, I changed the commit and made reversed logic to make it more clear.

Hi @jedi7 ,
I've rebased this branch and put it into our internal review & merge queue.
Angus

Cherry-picked as 801632d. Thanks again!


Logging routes

Description
This PR is addressing the feature request of adding logs to the endpoints when the app starts.

This PR fixes #599

Hey @carlosm27 👋 Great work! Added a few comments, let me know if something is unclear!

Thank you both @IdoKendo  and @sansyrox  for their reviews and suggestions. I'm going to apply them.

I tried this approach:
logger.info("Logging endpoint: {method: %s, route: %s}", method, route)

But I receive the following error message:

I used f-string instead for the logging:
logger.info(f"Logging endpoint: method: {route[0]}, route: {route[1]}")

logger.info("Logging endpoint: {method: %s, route: %s}", method, route)

@carlosm27 maybe try this Logging endpoint: method: %s, route: %s

logger.info("Logging endpoint: {method: %s, route: %s}", method, route)

@carlosm27 maybe try this Logging endpoint: method: %s, route: %s

Hey @sansyrox  I tried this: logger.info("Logging endpoint: method: %s, route: %s", route_type, endpoint). But I got the same error message.

@carlosm27 , the issue is not with your code but adding that is breaking something else. I can have a look tomorrow 😄

@carlosm27 , I understand what you mean. Our abstraction is not the best right now. We can merge your PR and address that later.
Thank you for the great work! 😄

@carlosm27 , I understand what you mean. Our abstraction is not the best right now. We can merge your PR and address that later.
Thank you for the great work! 😄

Hey @sansyrox thank you for your review and feedback.


[GSSoC'23] Battery Status Tracker Project

Describe the project you want to add with tech stack

Title - Battery Status Tracker
Tech using - HTML, CSS and JS
Expected behavior

Responsive website even for the small devices
Showing the status of the battery of your device.
Attractive looking with glassmorphism effect

Screenshots (optional)

Additional context (optional )

An attractive project and useful project

@MohitGupta121 @pranjay-poddar @Saurabh-kumar09 Sirs, please assign this project to me


Correcting the default value doc for the auth_scheme option

Coverage remained the same at 95.858% when pulling 624322da96bfeff3aa771edea7389df9b916a248 on jochenschneider:patch-1 into 96daaf56765652a5ffc792f645f6b3a4a42ce9bb on intridea:master.

Coverage remained the same at 95.858% when pulling 624322da96bfeff3aa771edea7389df9b916a248 on jochenschneider:patch-1 into 96daaf56765652a5ffc792f645f6b3a4a42ce9bb on intridea:master.

Coverage remained the same at 95.858% when pulling 624322da96bfeff3aa771edea7389df9b916a248 on jochenschneider:patch-1 into 96daaf56765652a5ffc792f645f6b3a4a42ce9bb on intridea:master.

Coverage remained the same at 95.858% when pulling 624322da96bfeff3aa771edea7389df9b916a248 on jochenschneider:patch-1 into 96daaf56765652a5ffc792f645f6b3a4a42ce9bb on intridea:master.


[Bug]: Need to implement Refresh - chokes on them now and they are appearing in some env'ts

Sample
msgext-northwind-inventory-ts
Description
@therealjohn observed errors when placing the adaptive card
We are suddenly receiving Refresh activities. Workaround is to return status code 200 instead of 400 on line 55 of searchApp.ts.
This issue should be resolved properly and we should actually refresh the card when we get these.
Steps to reproduce
Place a card in chat via the ordinary ME interface
You will see an error on the bottom of the card. This is due to the refresh failure.
Expected results
Card should not show an error
Actual results
Card shows an error
Additional Info
No response

UPDATE: This PR contains the workaround: https://github.com/OfficeDev/Copilot-for-M365-Plugins-Samples/pull/115
Keeping this issue open so we properly implement Refresh activity handling in the future...
@rabwill @garrytrinder

Closing issue as #115 has been merged


SpatialMatch not working

While writing test I found that SpatialMatch is not working.
Possible issues

It looks like my graphs might be messed up.
Missing qwerty. . .

fixed with pull request 9


Too easy to trigger over head gesture

Need to reduce size of overhead gesture area or move it further up as pointers sometimes unnecessarily trigger when performing game actions, especially with experimental VR controller based weapons handling.

Fixed in https://github.com/teddybear082/UGVR/commit/ca05b87c56d26070cf038be2c4e68e4e285ecab2


Make Docker automatically update hostname for Swarm node

Signed-off-by: Nishant Totla<EMAIL_ADDRESS>
- What I did
Fix #27173
- How I did it
The Swarm node config (swarmnode.Config) sets hostname and passes it to the node object, which in turn initializes hostname for the agent object. SwarmKit design makes sure that agent hostname always overrides what is reported by the machine. Currently, since the agent hostname is set at the time of node creation, any updates (reported in the future) are automatically discarded.
This PR ensures that the agent hostname is not set by Docker, and instead picked up from the hostname reported by the machine. As a result, SwarmKit's dynamic node update ticker picks up hostname changes and reports the correct hostname in docker node ls and docker node inspect.
- How to verify it
Start a single node Swarm, and check the hostname reported as part of docker node ls. Then change the machine hostname, and run docker node ls again.
- Description for the changelog
Automatically update Swarm node name when machine hostname changes

@stevvooe as you mentioned in earlier discussion, this targets the root cause of the problem, rather than break SwarmKit abstraction.
cc @aaronlehmann @nathanleclaire

LGTM

Should we remove the Hostname field completely?

@aaronlehmann @thaJeztah removed the field, and added a comment.

What I meant to ask was whether the Hostname field should be removed upstream, in swarmkit. If Docker shouldn't be using it, I'm not sure there's any point to having it.

@aaronlehmann in Docker Swarm mode, this field is not useful at all, but one reason to keep it is that it might be useful in the future, as described in https://github.com/docker/swarmkit/pull/1687#issuecomment-255899323

LGTM


feat: added new mixin to modify partial parsing behaviour

This introduces a new mixin which allows us to toggle streaming behaviour.
By using a LiteralPartialMixin, it doesn't allow incomplete strings.
setting=None story=None
setting=None story=None
setting=None story=None
setting=None story=None
setting=None story=None
setting=None story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story='whispers of the leaves'
---------
setting=None story=None
setting=None story=None
setting='' story=None
setting='A' story=None
setting='A tranquil' story=None
setting='A tranquil forest' story=None
setting='A tranquil forest' story=None
setting='A tranquil forest' story=None
setting='A tranquil forest' story=''
setting='A tranquil forest' story='Wh'
setting='A tranquil forest' story='Whispers'
setting='A tranquil forest' story='Whispers of'
setting='A tranquil forest' story='Whispers of the'
setting='A tranquil forest' story='Whispers of the leaves'
setting='A tranquil forest' story='Whispers of the leaves.'
setting='A tranquil forest' story='Whispers of the leaves.'

[!IMPORTANT]
Introduces LiteralPartialMixin to modify partial parsing behavior in streaming, with tests verifying its effect.

Behavior:

Introduces LiteralPartialMixin to toggle streaming behavior in partial.py.
Updates model_from_chunks and model_from_chunks_async to use partial_mode based on LiteralPartialMixin.

Tests:

Adds test_literal_partial_mixin and test_literal_partial_mixin_async in test_stream.py to verify behavior with LiteralPartialMixin.
Ensures field updates are correctly handled with and without the mixin.

This description was created by  for a353547809878030ffea2f3999dd99974b7ab95e. It will automatically update as commits are pushed.

from instructor.dsl.partial import LiteralPartialMixin
from pydantic import BaseModel
from openai import OpenAI
import instructor

client = OpenAI()
client = instructor.from_openai(client)

class Story(BaseModel, LiteralPartialMixin):
    setting: str
    story: str

resp = client.chat.completions.create_partial(
    model="gpt-4o-mini",
    response_model=Story,
    messages=[
        {
            "role": "user",
            "content": "Give me a 1 sentence haiku",
        }
    ],
)

for r in resp:
    print(r)

print("---------")

class Story(BaseModel):
    setting: str
    story: str

resp = client.chat.completions.create_partial(
    model="gpt-4o-mini",
    response_model=Story,
    messages=[
        {
            "role": "user",
            "content": "Give me a 1 sentence haiku",
        }
    ],
)

for r in resp:
    print(r)

setting=None story=None
setting=None story=None
setting=None story=None
setting=None story=None
setting=None story=None
setting=None story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story=None
setting='a quiet forest' story='whispers of the leaves'
---------
setting=None story=None
setting=None story=None
setting='' story=None
setting='A' story=None
setting='A tranquil' story=None
setting='A tranquil forest' story=None
setting='A tranquil forest' story=None
setting='A tranquil forest' story=None
setting='A tranquil forest' story=''
setting='A tranquil forest' story='Wh'
setting='A tranquil forest' story='Whispers'
setting='A tranquil forest' story='Whispers of'
setting='A tranquil forest' story='Whispers of the'
setting='A tranquil forest' story='Whispers of the leaves'
setting='A tranquil forest' story='Whispers of the leaves.'
setting='A tranquil forest' story='Whispers of the leaves.'

why is it not called PartialLiteralMixin

Renamed to PartialLiteralMixin. My original intention was to give users the control over what the parsing mode was for their specific data structure but I realised the modes are unlikely to change so calling it Literal makes more sense


TorGuard Socks5 proxies

I would prefer to use TorGuards socks5 proxies.  Each connection can have its own IP address.  TorGuard is not tor.

Tor proxy is to slow bro. : ) I don't try spawn bots via tor. But i know Tor proxy is too slow.


chore(ci): clean test matrix

We will not run tests on OpenResty <IP_ADDRESS> and <IP_ADDRESS>, since kong gateway are using latest version.
KAG-5215

@chronolaw seems next/2.8.x.x is still using <IP_ADDRESS> https://github.com/Kong/kong-ee/blob/6078d81c22e08b0b5259aa53adf3e3ddf5235d23/.requirements#L4

@chronolaw seems next/2.8.x.x is still using <IP_ADDRESS> https://github.com/Kong/kong-ee/blob/6078d81c22e08b0b5259aa53adf3e3ddf5235d23/.requirements#L4. Better keep it until 2.8 EOL.

lua-resty-events is only available in 3.x, not 2.x.


Contribute isDevModeEnabled in Release upstream

This fork of react-native has refactored such that the compile time #if RCT_DEV constructs are now a runtime settings via [[bridge devSettings] isDevModeEnabled].
This allows a product to allow debugging of react-native in Release builds of the native app.
(internal https://office.visualstudio.com/APEX/_workitems/edit/3237395)

This feature is removed, so I'm closing this.


Release 3.3.1

This release is intended to fix #93

[x] Implement function
[x] Testing
[x] Add a document
[x] Bump version
[x] Release to PyPI

Version 3.3.1 has been shipped to PyPI.
https://pypi.org/project/pip-licenses/3.3.1/


My Stake precision is a little too accurate!

Description
A clear and concise description of what the bug is.
Steps to Reproduce

Go to 'governace app
Click on staking
Connect a wallet
See error

Expected behavior
I dont need to see all these decimal points

We should be clipping it at 2 DP like the other stuff on the page.
Screenshots
See above
Device details
Desktop (please complete the following information):

OS: Windows
Browser Chrome
Version 0.71.4 and 0.12 for dektop wallet

Additional context
Add any other context about the problem here.

Duplicates https://github.com/vegaprotocol/frontend-monorepo/issues/3571


Support videojs 5.2 API

Apparently backend tech has a new way to register itself with vjs 5.2:
VIDEOJS: WARN: The Youtube tech was registered as a component. It should instead be registered using videojs.registerTech(name, tech)

It seems the change implements this:

My submit does implement the registerTech change, but be advised, I haven't tested the AMD wrapper with anything but my own code yet, so your mileage may vary.

Perhaps you can create a separate PR with the registerTech fix?

Note that this API appears to be new in 5.2 only, so if we are to support older version in the mean time, we need to check videojs.VERSION

+1

Can we please see the upgrades for the latest version of video.js? CHEERS +1

+1

This has been fixed. I'm releasing a new version now :)


[FIX] frepple: Export of manufacturing orders

@jdetaeye This is ready to be reviewed. Thanks!

As usual, this varies a bit by odoo release...
For odoo 12 we want to extract "confirmed", "planned", "progress".  So, your pull request is valid.
https://github.com/odoo/odoo/blob/2529ab67e21637b5e56bbb771920db8e4d6fe04c/addons/mrp/models/mrp_production.py#L128
state = fields.Selection([
    ('confirmed', 'Confirmed'),
    ('planned', 'Planned'),
    ('progress', 'In Progress'),
    ('done', 'Done'),
    ('cancel', 'Cancelled')], string='State',
    copy=False, default='confirmed', track_visibility='onchange')

For odoo 13, we want to extract "confirmed", "planned" and "progress"
https://github.com/odoo/odoo/blob/708891a9637e03c8feb895fba3c363ebd0a6004c/addons/mrp/models/mrp_production.py#L139
state = fields.Selection([
    ('draft', 'Draft'),
    ('confirmed', 'Confirmed'),
    ('planned', 'Planned'),
    ('progress', 'In Progress'),
    ('to_close', 'To Close'),
    ('done', 'Done'),
    ('cancel', 'Cancelled')], string='State',
    compute='_compute_state', copy=False, index=True, readonly=True,
    store=True, tracking=True,
    help=" * Draft: The MO is not confirmed yet.\n"
         " * Confirmed: The MO is confirmed, the stock rules and the reordering of the components are trigerred.\n"
         " * Planned: The WO are planned.\n"
         " * In Progress: The production has started (on the MO or on the WO).\n"
         " * To Close: The production is done, the MO has to be closed.\n"
         " * Done: The MO is closed, the stock moves are posted. \n"
         " * Cancelled: The MO has been cancelled, can't be confirmed anymore.")

For odoo 14, we want to extract "confirmed" and "progress".
https://github.com/odoo/odoo/blob/d347eae1646639e2b346d404d1eb68ce9eac005c/addons/mrp/models/mrp_production.py#L167
state = fields.Selection([
    ('draft', 'Draft'),
    ('confirmed', 'Confirmed'),
    ('progress', 'In Progress'),
    ('to_close', 'To Close'),
    ('done', 'Done'),
    ('cancel', 'Cancelled')], string='State',
    compute='_compute_state', copy=False, index=True, readonly=True,
    store=True, tracking=True,
    help=" * Draft: The MO is not confirmed yet.\n"
         " * Confirmed: The MO is confirmed, the stock rules and the reordering of the components are trigerred.\n"
         " * In Progress: The production has started (on the MO or on the WO).\n"
         " * To Close: The production is done, the MO has to be closed.\n"
         " * Done: The MO is closed, the stock moves are posted. \n"
         " * Cancelled: The MO has been cancelled, can't be confirmed anymore.")


Stream no longer working in HA

Since a couple of weeks Webrtc camera stream is no longer workging in my HA. I have tried to rtsp link with the test movie, but that one is also not working, however, when I try to open the stream in VLC it works, also my camera stream works in VLC, but in Homeassistant using Webrtc it does not work. Have there been any changes recently? Like I said, it was working fine for a long time, but now it stopped working and I am not sure where to start with troubleshooting since nothing has changed in my configuration.
Thanks a lot for helping.

same here

Ditto, worked for about 4 Months and just stopped Friday morning...
In VLC I can also see my cameras with the same rtsp link as in HA.

Have there been any changes recently?

Yes. Look at the active issues before posting.
https://github.com/AlexxIT/WebRTC/issues/321

#321


feat: designed new Features section

Summary by CodeRabbit

Refactor

Improved the Features component with a more modern arrow function syntax.
Enhanced the visual layout of the features section using a grid layout for better user experience.

Style

Updated styling and layout of the features display for a more appealing and organized presentation.
Introduced color customization for feature icons based on new colorHex property.

Documentation

Clarified and condensed feature descriptions for better understanding.

New Features

Added a colorHex property to feature objects for dynamic styling.

@coderabbitai review


Reorder log detection sequence.

If one is using flyway from a maven plugin there is no way to control the log sequence. Simply because flyway checks very early if slf4j is present and maven provides SL4J's SimpleLogger out of the box. However to change the SimpleLogger log level's one must go to  ${MAVEN_HOME}/conf/logging/simplelogger.properties and we can't tell every user to change his maven settings.
This pull-request gives priority to detecting if commons-logging is available. This way the user can route commons-logging to whatever their logging implementation of choice is (log4j, log4j2, logback, etc.) and be able to control the log level.

As commons-logging is effectively legacy, this PR would now again favor it over SLF4J for all users. This is I am afraid not an option.
Additionally to cleanly tie into Maven's logging one MUST use slf4j. (Which is not to say I don't feel your pain. See https://issues.apache.org/jira/browse/MNG-5916)

Would it possible to add some more than? Perhaps Log4j2 before the SLF4j?


[SPIKE/RESEARCH] Finalize approach to find usage metrics of Operators/Sensors

Finalize an approach to find out which operators/sensors are most used in astro deployments.
This would be helpful to focus our efforts to build async operators for the most used operators/sensors.
cc @vikramkoka

After checking airflow db found an table task_instance which captures the operator ran and state of the individual tasks.
query used select operator, count(*) as count from task_instance group by operator order by count desc;

sl_no
operator
count

0
DataprocSubmitJobOperatorAsync
35

1
GCSCreateBucketOperator
9

2
GCSDeleteBucketOperator
8

3
DataprocCreateClusterOperatorAsync
7

4
DataprocDeleteClusterOperatorAsync
7

5
BigQueryInsertJobOperatorAsync
5

6
PythonOperator
5

7
PostgresOperator
4

8
DummyOperator
3

9
BashOperator
2

10
BigQueryCreateEmptyDatasetOperator
2

11
BigQueryCreateEmptyTableOperator
2

12
BigQueryDeleteDatasetOperator
2

13
BigQueryInsertJobOperator
1

14
GCSObjectUpdateSensorAsync
1

15
LocalFilesystemToGCSOperator
1

16
BigQueryIntervalCheckOperatorAsync
1

17
BigQueryGetDataOperatorAsync
1

18
BigQueryCheckOperatorAsync
1

19
GCSObjectExistenceSensorAsync
1

20
GCSUploadSessionCompleteSensorAsync
1

21
BigQueryValueCheckOperatorAsync
1

22
BigQueryTableExistenceSensorAsync
1

23
BigQueryTablePartitionExistenceSensor
1

24
GCSObjectsWithPrefixExistenceSensorAsync
1

what if I have a custom operator which inherits from another operator like DataprocSubmitJobOperatorAsync?

Currently, astrolabe is using the query
SELECT
  operator,
  SUM(task_success_count),
  SUM(total_task_count) AS total_task_count,
  COUNT(DISTINCT acct_id) AS distinct_customer_count
FROM dwh.reporting.astro_cust_usage_operators_daily
WHERE date >= '2022-01-01'
GROUP BY 1
ORDER BY (total_task_count * distinct_customer_count) DESC

to fetch the count.
Currently, astrolabe do not have the ability to observe subclassing/inheritance.
Nebula task data is provided by the deployments’ task_instance table in the metadata DB, which does not provide this information.
Astro task data is provided by task instance splunk logs, which do not provide this information.
Unless telemetry supports the listing of parent classes, presumably via MRO we cannot get this information.
To be possible, for the data team to collect the data and provide insight, it would require either:
Splunk task logs to include the inheritance (for Astro)
Airflow Metadb to include in the task instance tables (for Nebula)

If we use dag code to fetch the data then we need to use imports for operators or sensors to get the info

there can be unused imports in dags.
from airflow.operators.dummy import DummyOperator as do
which could cause issues and might not get the proper count.
There can be a separate python file written for inheritance or subclasses are called and imported inside dag file might not get the needed info for us.
Custom operator names used in dag task can be fetched since the task operator which is used is stored in the
task_instance model.

Did you look at the data column in serialized_dag table @rajaths010494 -- check if we store the path to the operator in the serialized json.
Separately, did you manage to find a way of identifying whether an operator was async or not?

Yes i have checked it table contains operator/sensor and module path
"_task_type": "BigQueryGetDataOperatorAsync",
"_task_module": "astronomer.providers.google.cloud.operators.bigquery",

I Checked the trigger table where temporarily data is stored when the task has been deferred but it's not persisted once the task is completed.

When async operator/sensor runs in task_instance table column next_kwargs has been updated with null whereas for sync operators /sensors it is empty.
select operator, count(*) as count from task_instance where next_kwargs is not null group by operator order by count desc;

empty for sync operators
select operator, count(*) as count from task_instance where next_kwargs is null group by operator order by count desc;

Documentation of the findings .(WIP)
https://www.notion.so/astronomerio/Approach-to-find-usage-metrics-of-Operators-Sensors-947dd9d9968444fe984ee34ef6c4a420

Please mention the tabular summary of all the analysis done on this story and the plan ahead.

Findings
Next steps
Notes

Check inheritance of custom operator/sensor
Currently, we don’t readily have data available in the airflow DB.
Add the inheritance /sub classes details in task_instance table and logs for splunk.
Suggestion add op_classpath similar present in sensor_instance in task_instance also to record where the operator/sensor is coming from.

Check for async operator/sensor
From the task_instance table and column next_kwargs when a task is deferred value is added so an non empty column means its async operator/sensor
We can get the async operators count

Check for sync operator/sensor
so an empty column from the task_instance and next_kwargs an empty value means a tasks was not deferred.

airflow also has async operators added in the repo. So we can check from the serialised_dag table and data column to get _task_type  and _task_module  to know the class path for more information.

Thanks @phanikumv , will review

Spike story is complete. Closing the issue.


Initial implementation of polymul function

Hi,
I have added initial code for np.polymul as referenced in #70 .
I am yet to add tests for this because I am not sure what should the format for those and need a bit of guidance in that regard.

Hi,
I am facing some dtypes problems.
Jax's _conv is automatically converting int arguments to floats whereas Numpy is not.
Reproduction of Error:
import numpy as np
import jax.numpy as jnp

x = np.asarray([1,2,3])
y = np.asarray([2,3,4])

np_res = np.convolve(x, y)
print(np_res.dtype)
# int64
jnp_res = jnp.convolve(x, y)
print(jnp_res.dtype)
# float32

Specifically this_line is changing the dtype. Is this expected? If yes, should I change check_dtypes=True to check_dtypes=False for this function

okay yes I will do it.
Thanks

I don't think we should do the same here: jax cannot compile functions with dynamic array shapes (output shapes that depend on the contents of input arrays rather than the shapes of input arrays), so jax code will be more performant if it keeps the leading zeros.
The best approach may be to have a keyword-only argument to the function, something like trim_leading_zeros that is False by default, and recovers the numpy behavior at the expense of jit-compilation.

Hi,
I have tried to incorporate an option trim_leading_zeros. Is this what you had in mind. If it is not proper, please let me know.
If I set the option trim_leading_zeros=True, the shape mismatch test passes.
Thanks

Hi,
I have tried to incorporate all the changes.
Only one test from the test suite is failing, and I am not sure what is the problem. If you would give me some hint regarding that, I could try to fix that too. Thanks
Here is erroneous output
Mismatched elements: 6 / 23 (26.1%)
Max absolute difference: 0.1875
Max relative difference: 0.004757
 x: array([ -0.1649,  -3.74  , -19.72  ,   1.97  ,   5.605 , -18.92  ,
        -2.613 ,   1.042 , -34.25  ,  -3.85  ,  68.3   , -76.56  ,
         1.881 ,   7.816 , -16.81  ,  23.34  , -27.38  ,  20.06  ,
       -11.016 ,   0.7153,   5.617 ,  -0.505 ,   2.85  ], dtype=float16)
 y: array([ -0.1649,  -3.74  , -19.72  ,   1.969 ,   5.605 , -18.92  ,
        -2.611 ,   1.039 , -34.28  ,  -3.857 ,  68.1   , -76.6   ,
         1.886 ,   7.8   , -16.8   ,  23.34  , -27.39  ,  20.06  ,
       -11.016 ,   0.7188,   5.617 ,  -0.505 ,   2.85  ], dtype=float16)

Generally float16 and bfloat16 tolerances need to be adjusted when there are repeated operations, such as with a convolution. I would follow the precedent set in the convolution test, since this is essentially a thin wrapper on convolution: https://github.com/google/jax/blob/71f1c5cafeab50f0358aa194f0a03a0666e4b4db/tests/lax_numpy_test.py#L1343-L1345

Hi,
I again did something wrong with rebasing. Sorry

Awesome - thanks for sticking with it through all the changes and rounds of reviews! Internal tests pass; I think this is ready to merge once the CI is green 🎉

Thanks,
Would you recommend me some resources or some piece of code which I can look into to get in-depth knowledge of JAX.


Duplicate dependency defines components that don't match

[6:26 PM] Alice 🌹: @aevyrie so the problem here is that you have multiple different versions of a dependency in tree, which expose different component types?
[6:26 PM]  Alice 🌹: I know you've talked to me about this problem before, but I want to make sure I get the details right
[6:26 PM]aevyrie: Yes. The only failure mode is components. Resources cause a startup panic because a plugin is responsible for adding them. Components though, silently fail.
[6:27 PM]aevyrie: It also helps codify what plugin is responsible for said component, just like resources already do.
[6:27 PM]aevyrie: There is nuance there, of course.
[6:27 PM]  Alice 🌹: I bet we could inspect the type registry for near-duplicate type paths 🤔
[6:28 PM]  Alice 🌹: Or even look through all of the types that impl Component
[6:28 PM] aevyrie: Basically, queries just silently fail to match, because you are querying a component in one place and adding it in another, but the versions are different, so the types are different.

From a discussion with @aevyrie discussing a long-running pain point on large Bevy projects.

I believe this is a duplicate of #16, but feel free to re-open it if that's not the case!
My thought it to mirror Clippy's Cargo lints and parse the result of cargo metadata for duplicate dependencies that start with the bevy_ suffix or depend on a crate with a bevy_ suffix.

I think #16 should solve most of these problems. We can reopen if something more targeted is warranted.


下载1.3.0后提示无法获取DDRecorder的版本信息，当前版本号: {}，请到https://github.com/AsaChiri/DDRecorder/releases 检查最新版本'.format(CURRENT_VERSION))

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

可能是与github链接不畅导致的，此消息应当不影响正常使用。


[boost] build failure

Host Environment

OS: [e.g. Windows/Linux etc...]
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install xxxx
Failure logs

Cut and paste the appropriate build messages from the console output.
Attach every failure log file mentioned in the console output.

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
Here is my error.

installed english pack.
version check.

I need boost asio pkg, so i installed only boost asio, but i couldn't .  solution please.
c:\git-rep\vcpkg>vcpkg install boost:x64-windows
Computing installation plan...
The following packages will be built and installed:
boost[core]:x64-windows -> 1.81.0#1

boost-accumulators[core]:x64-windows -> 1.81.0#1
boost-algorithm[core]:x64-windows -> 1.81.0#1
boost-align[core]:x64-windows -> 1.81.0#1
boost-any[core]:x64-windows -> 1.81.0#1
boost-array[core]:x64-windows -> 1.81.0#1
boost-asio[core]:x64-windows -> 1.81.0#1
boost-assert[core]:x64-windows -> 1.81.0#1
boost-assign[core]:x64-windows -> 1.81.0#1
boost-atomic[core]:x64-windows -> 1.81.0#1
boost-beast[core]:x64-windows -> 1.81.0#1
boost-bimap[core]:x64-windows -> 1.81.0#1
boost-bind[core]:x64-windows -> 1.81.0#1
boost-build[core]:x64-windows -> 1.81.0#1
boost-callable-traits[core]:x64-windows -> 1.81.0#1
boost-chrono[core]:x64-windows -> 1.81.0#1
boost-circular-buffer[core]:x64-windows -> 1.81.0#1
boost-compatibility[core]:x64-windows -> 1.81.0#1
boost-compute[core]:x64-windows -> 1.81.0#1
boost-concept-check[core]:x64-windows -> 1.81.0#1
boost-config[core]:x64-windows -> 1.81.0#1
boost-container[core]:x64-windows -> 1.81.0#1
boost-container-hash[core]:x64-windows -> 1.81.0#1
boost-context[core]:x64-windows -> 1.81.0#1
boost-contract[core]:x64-windows -> 1.81.0#1
boost-conversion[core]:x64-windows -> 1.81.0#1
boost-convert[core]:x64-windows -> 1.81.0#1
boost-core[core]:x64-windows -> 1.81.0#1
boost-coroutine[core]:x64-windows -> 1.81.0#1
boost-coroutine2[core]:x64-windows -> 1.81.0#1
boost-crc[core]:x64-windows -> 1.81.0#1
boost-date-time[core]:x64-windows -> 1.81.0#1
boost-describe[core]:x64-windows -> 1.81.0#1
boost-detail[core]:x64-windows -> 1.81.0#1
boost-dll[core]:x64-windows -> 1.81.0#1
boost-dynamic-bitset[core]:x64-windows -> 1.81.0#1
boost-endian[core]:x64-windows -> 1.81.0#1
boost-exception[core]:x64-windows -> 1.81.0#1
boost-fiber[core]:x64-windows -> 1.81.0#1
boost-filesystem[core]:x64-windows -> 1.81.0#1
boost-flyweight[core]:x64-windows -> 1.81.0#1
boost-foreach[core]:x64-windows -> 1.81.0#1
boost-format[core]:x64-windows -> 1.81.0#1
boost-function[core]:x64-windows -> 1.81.0#1
boost-function-types[core]:x64-windows -> 1.81.0#1
boost-functional[core]:x64-windows -> 1.81.0#1
boost-fusion[core]:x64-windows -> 1.81.0#1
boost-geometry[core]:x64-windows -> 1.81.0#1
boost-gil[core]:x64-windows -> 1.81.0#1
boost-graph[core]:x64-windows -> 1.81.0#1
boost-hana[core]:x64-windows -> 1.81.0#1
boost-heap[core]:x64-windows -> 1.81.0#1
boost-histogram[core]:x64-windows -> 1.81.0#1
boost-hof[core]:x64-windows -> 1.81.0#1
boost-icl[core]:x64-windows -> 1.81.0#1
boost-integer[core]:x64-windows -> 1.81.0#1
boost-interprocess[core]:x64-windows -> 1.81.0#1
boost-interval[core]:x64-windows -> 1.81.0#1
boost-intrusive[core]:x64-windows -> 1.81.0#1
boost-io[core]:x64-windows -> 1.81.0#1
boost-iostreams[bzip2,core,lzma,zlib,zstd]:x64-windows -> 1.81.0#1
boost-iterator[core]:x64-windows -> 1.81.0#1
boost-json[core]:x64-windows -> 1.81.0#1
boost-lambda[core]:x64-windows -> 1.81.0#1
boost-lambda2[core]:x64-windows -> 1.81.0#1
boost-leaf[core]:x64-windows -> 1.81.0#1
boost-lexical-cast[core]:x64-windows -> 1.81.0#1
boost-local-function[core]:x64-windows -> 1.81.0#1
boost-locale[core]:x64-windows -> 1.81.0#2
boost-lockfree[core]:x64-windows -> 1.81.0#1
boost-log[core]:x64-windows -> 1.81.0#1
boost-logic[core]:x64-windows -> 1.81.0#1
boost-math[core]:x64-windows -> 1.81.0#1
boost-metaparse[core]:x64-windows -> 1.81.0#1
boost-modular-build-helper[core]:x64-windows -> 1.81.0#2
boost-move[core]:x64-windows -> 1.81.0#1
boost-mp11[core]:x64-windows -> 1.81.0#1
boost-mpl[core]:x64-windows -> 1.81.0#1
boost-msm[core]:x64-windows -> 1.81.0#1
boost-multi-array[core]:x64-windows -> 1.81.0#1
boost-multi-index[core]:x64-windows -> 1.81.0#1
boost-multiprecision[core]:x64-windows -> 1.81.0#1
boost-nowide[core]:x64-windows -> 1.81.0#1
boost-numeric-conversion[core]:x64-windows -> 1.81.0#1
boost-odeint[core]:x64-windows -> 1.81.0#1
boost-optional[core]:x64-windows -> 1.81.0#1
boost-outcome[core]:x64-windows -> 1.81.0#1
boost-parameter[core]:x64-windows -> 1.81.0#1
boost-parameter-python[core]:x64-windows -> 1.81.0#1
boost-pfr[core]:x64-windows -> 1.81.0#1
boost-phoenix[core]:x64-windows -> 1.81.0#1
boost-poly-collection[core]:x64-windows -> 1.81.0#1
boost-polygon[core]:x64-windows -> 1.81.0#1
boost-pool[core]:x64-windows -> 1.81.0#1
boost-predef[core]:x64-windows -> 1.81.0#1
boost-preprocessor[core]:x64-windows -> 1.81.0#1
boost-process[core]:x64-windows -> 1.81.0#1
boost-program-options[core]:x64-windows -> 1.81.0#1
boost-property-map[core]:x64-windows -> 1.81.0#1
boost-property-tree[core]:x64-windows -> 1.81.0#1
boost-proto[core]:x64-windows -> 1.81.0#1
boost-ptr-container[core]:x64-windows -> 1.81.0#1
boost-python[core,python3]:x64-windows -> 1.81.0#1
boost-qvm[core]:x64-windows -> 1.81.0#1
boost-random[core]:x64-windows -> 1.81.0#1
boost-range[core]:x64-windows -> 1.81.0#1
boost-ratio[core]:x64-windows -> 1.81.0#1
boost-rational[core]:x64-windows -> 1.81.0#1
boost-regex[core]:x64-windows -> 1.81.0#1
boost-safe-numerics[core]:x64-windows -> 1.81.0#1
boost-scope-exit[core]:x64-windows -> 1.81.0#1
boost-serialization[core]:x64-windows -> 1.81.0#1
boost-signals2[core]:x64-windows -> 1.81.0#1
boost-smart-ptr[core]:x64-windows -> 1.81.0#1
boost-sort[core]:x64-windows -> 1.81.0#1
boost-spirit[core]:x64-windows -> 1.81.0#1
boost-stacktrace[core]:x64-windows -> 1.81.0#1
boost-statechart[core]:x64-windows -> 1.81.0#1
boost-static-assert[core]:x64-windows -> 1.81.0#1
boost-static-string[core]:x64-windows -> 1.81.0#1
boost-stl-interfaces[core]:x64-windows -> 1.81.0#1
boost-system[core]:x64-windows -> 1.81.0#1
boost-test[core]:x64-windows -> 1.81.0#1
boost-thread[core]:x64-windows -> 1.81.0#1
boost-throw-exception[core]:x64-windows -> 1.81.0#1
boost-timer[core]:x64-windows -> 1.81.0#1
boost-tokenizer[core]:x64-windows -> 1.81.0#1
boost-tti[core]:x64-windows -> 1.81.0#1
boost-tuple[core]:x64-windows -> 1.81.0#1
boost-type-erasure[core]:x64-windows -> 1.81.0#1
boost-type-index[core]:x64-windows -> 1.81.0#1
boost-type-traits[core]:x64-windows -> 1.81.0#1
boost-typeof[core]:x64-windows -> 1.81.0#1
boost-ublas[core]:x64-windows -> 1.81.0#1
boost-uninstall[core]:x64-windows -> 1.81.0#1
boost-units[core]:x64-windows -> 1.81.0#1
boost-unordered[core]:x64-windows -> 1.81.0#1
boost-url[core]:x64-windows -> 1.81.0#1
boost-utility[core]:x64-windows -> 1.81.0#1
boost-uuid[core]:x64-windows -> 1.81.0#1
boost-variant[core]:x64-windows -> 1.81.0#1
boost-variant2[core]:x64-windows -> 1.81.0#1
boost-vcpkg-helpers[core]:x64-windows -> 1.81.0#2
boost-vmd[core]:x64-windows -> 1.81.0#1
boost-wave[core]:x64-windows -> 1.81.0#1
boost-winapi[core]:x64-windows -> 1.81.0#1
boost-xpressive[core]:x64-windows -> 1.81.0#1
boost-yap[core]:x64-windows -> 1.81.0#1
bzip2[core,tool]:x64-windows -> 1.0.8#3
expat[core]:x64-windows -> 2.5.0#3
libffi[core]:x64-windows -> 3.4.4
liblzma[core]:x64-windows -> 5.4.1
openssl[core]:x64-windows -> 3.0.7#2
python3[core]:x64-windows -> 3.10.7#5
sqlite3[core]:x64-windows -> 3.40.1#1
zlib[core]:x64-windows -> 1.2.13
zstd[core]:x64-windows -> 1.5.2#3
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
Restored 39 package(s) from C:\Users\류수민\AppData\Local\vcpkg\archives in 4.228 s. Use --debug to see more details.
Installing 1/157 boost-uninstall:x64-windows...
Elapsed time to handle boost-uninstall:x64-windows: 11.46 ms
Installing 2/157 boost-vcpkg-helpers:x64-windows...
Elapsed time to handle boost-vcpkg-helpers:x64-windows: 13.98 ms
Installing 3/157 boost-config:x64-windows...
Elapsed time to handle boost-config:x64-windows: 282.2 ms
Installing 4/157 boost-assert:x64-windows...
Elapsed time to handle boost-assert:x64-windows: 18.07 ms
Installing 5/157 boost-static-assert:x64-windows...
Elapsed time to handle boost-static-assert:x64-windows: 16.7 ms
Installing 6/157 boost-throw-exception:x64-windows...
Elapsed time to handle boost-throw-exception:x64-windows: 18.19 ms
Installing 7/157 boost-core:x64-windows...
Elapsed time to handle boost-core:x64-windows: 76.94 ms
Installing 8/157 boost-array:x64-windows...
Elapsed time to handle boost-array:x64-windows: 16.52 ms
Installing 9/157 boost-preprocessor:x64-windows...
Elapsed time to handle boost-preprocessor:x64-windows: 519.2 ms
Installing 10/157 boost-type-traits:x64-windows...
Elapsed time to handle boost-type-traits:x64-windows: 219.8 ms
Installing 11/157 boost-concept-check:x64-windows...
Elapsed time to handle boost-concept-check:x64-windows: 33.24 ms
Installing 12/157 boost-predef:x64-windows...
Elapsed time to handle boost-predef:x64-windows: 173.2 ms
Installing 13/157 boost-winapi:x64-windows...
Elapsed time to handle boost-winapi:x64-windows: 136.6 ms
Installing 14/157 boost-move:x64-windows...
Elapsed time to handle boost-move:x64-windows: 65.08 ms
Installing 15/157 boost-circular-buffer:x64-windows...
Elapsed time to handle boost-circular-buffer:x64-windows: 24.09 ms
Installing 16/157 boost-mp11:x64-windows...
Elapsed time to handle boost-mp11:x64-windows: 50.51 ms
Installing 17/157 boost-describe:x64-windows...
Elapsed time to handle boost-describe:x64-windows: 41.22 ms
Installing 18/157 boost-container-hash:x64-windows...
Elapsed time to handle boost-container-hash:x64-windows: 36.43 ms
Installing 19/157 boost-detail:x64-windows...
Elapsed time to handle boost-detail:x64-windows: 42.43 ms
Installing 20/157 boost-io:x64-windows...
Elapsed time to handle boost-io:x64-windows: 26.62 ms
Installing 21/157 boost-utility:x64-windows...
Elapsed time to handle boost-utility:x64-windows: 45.85 ms
Installing 22/157 boost-mpl:x64-windows...
Elapsed time to handle boost-mpl:x64-windows: 1.068 s
Installing 23/157 boost-function-types:x64-windows...
Elapsed time to handle boost-function-types:x64-windows: 99.83 ms
Installing 24/157 boost-bind:x64-windows...
Elapsed time to handle boost-bind:x64-windows: 43.77 ms
Installing 25/157 boost-integer:x64-windows...
Elapsed time to handle boost-integer:x64-windows: 32.82 ms
Installing 26/157 boost-type-index:x64-windows...
Elapsed time to handle boost-type-index:x64-windows: 35.48 ms
Installing 27/157 boost-typeof:x64-windows...
Elapsed time to handle boost-typeof:x64-windows: 77.98 ms
Installing 28/157 boost-function:x64-windows...
Elapsed time to handle boost-function:x64-windows: 46.33 ms
Installing 29/157 boost-functional:x64-windows...
Elapsed time to handle boost-functional:x64-windows: 34.64 ms
Installing 30/157 boost-tuple:x64-windows...
Elapsed time to handle boost-tuple:x64-windows: 25.86 ms
Installing 31/157 boost-fusion:x64-windows...
Elapsed time to handle boost-fusion:x64-windows: 1.128 s
Installing 32/157 boost-smart-ptr:x64-windows...
Elapsed time to handle boost-smart-ptr:x64-windows: 127.5 ms
Installing 33/157 boost-conversion:x64-windows...
Elapsed time to handle boost-conversion:x64-windows: 22.73 ms
Installing 34/157 boost-optional:x64-windows...
Elapsed time to handle boost-optional:x64-windows: 39.43 ms
Installing 35/157 boost-iterator:x64-windows...
Elapsed time to handle boost-iterator:x64-windows: 61.65 ms
Installing 36/157 boost-numeric-conversion:x64-windows...
Elapsed time to handle boost-numeric-conversion:x64-windows: 49.57 ms
Installing 37/157 boost-parameter:x64-windows...
Elapsed time to handle boost-parameter:x64-windows: 126.9 ms
Installing 38/157 boost-build:x64-windows...
Elapsed time to handle boost-build:x64-windows: 1.034 s
Installing 39/157 boost-modular-build-helper:x64-windows...
Elapsed time to handle boost-modular-build-helper:x64-windows: 34.19 ms
Installing 40/157 boost-regex:x64-windows...
Building boost-regex[core]:x64-windows...
-- Using cached boostorg-regex-boost-1.81.0.tar.gz.
-- Cleaning sources at C:/git-rep/vcpkg/buildtrees/boost-regex/src/ost-1.81.0-5d02094f20.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/git-rep/vcpkg/downloads/boostorg-regex-boost-1.81.0.tar.gz
-- Using source at C:/git-rep/vcpkg/buildtrees/boost-regex/src/ost-1.81.0-5d02094f20.clean
-- Including C:/git-rep/vcpkg/ports/boost-regex/b2-options.cmake
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: C:/git-rep/vcpkg/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j13
Working Directory: C:/git-rep/vcpkg/buildtrees/boost-regex/x64-windows-dbg
See logs for more information:
C:\git-rep\vcpkg\buildtrees\boost-regex\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
installed/x64-windows/share/boost-build/boost-modular-build.cmake:140 (vcpkg_cmake_install)
ports/boost-regex/portfile.cmake:12 (boost_modular_build)
scripts/ports.cmake:147 (include)
error: building boost-regex:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-regex
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[boost-regex]+Build+error
Include '[boost-regex] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
vcpkg-scripts version: 8e986ec51 2023-02-08 (29 hours ago)

Provide C:\git-rep\vcpkg\buildtrees\boost-regex\install-x64-windows-dbg-out.log first please.
Attach every failure log file mentioned in the console output.

I fixed it. if you using your country language on windows, i think in your user fleder name is your language. you must fix it to englisg. and then done.

i fixed it.
check your windows user name. if your forder name is non alphabet, you cant install to boost not only chinese but also non-alphabetic.

i fixed it.
check your windows user name. if your forder name is non alphabet, you cant install to boost not only chinese but also non-alphabetic.
vcpkg only English in actually alphabet is supported.

i fixed it.
check your windows user name. if your forder name is non alphabet, you cant install to boost not only chinese but also non-alphabetic. vcpkg only English in actually alphabet is supported.

Ah I know this issue, the boost upstream uses %TEMP% to storage the obj files, which caused this issue.


Typo fix: argument to DataFrame is called dsk, not dask

Trivial typo fix to have docstring match call signature.

Thanks @joergdietrich !  Merging.


Fix channels support

Solves #46

Added changes in Aframe component and shader files to support switch between channels.
Added optional value to increase pixel intensity.
Fixed coded that was calling updateTransferTexture twice when a single prop was being updated

Prototype of the shader lib component or the Aframe component?

Also update the package version number. Say 0.2.2 (or 0.3.0 @mcmcgrath13?). Once it's merged with main we can make a new release and we'll be able to update the library in the other repos

This is a new feature, so I'd say 0.3.0

I don't see the package number bumped in package.json, otherwise I think it's good to go.


Bugfix: z.record().parse should not filter out undefined values

When calling .parse on z.record( z.any() ) we should not filter out undefined values. Add the optional 'alwaysSet' to the z.record pairs before passing them to mergeObject to maintain undefined values.
This solves issue #3197

Thanks! Great PR.

This has landed in Zod 3.23.
https://github.com/colinhacks/zod/releases/tag/v3.23.0


Cactbot timeline not appearing even though after i lock the overlay

cactbot timeline not appearing after 4.4

Can you give me some more details about what's not working? What zone is this in?

its fixed with the most recent updates 👍

Excellent.


Issue #316 - documentation for Subsidy and TOPA tables

This PR contains Markdown documentation files for both the 'Subsidy' table and the 'TOPA' table, which partially address the 'Data ingestion' section of Issue #316 .
@NealHumphrey I will defer to you to coordinate with the Filter team if need be to make sure that the JS for the front end picks up these two new files.
There should be a few more documentation files coming from @speedyturkey and @kasao10, per the spreadsheet we set up to divvy up the work: https://docs.google.com/spreadsheets/d/1EcjViJq2SuiHEEiRu9TemVJ29oNrNV7ibC6NofJiXzA/edit#gid=1802468479.
I thought we had accounted for all the datasets that still need documentation in there, but it looks like we may need someone to work on a Markdown file for the census data.  I will do a little more digging and pick that one up myself if need be.

This PR is a mess, I only wanted to include the two most recent commits.  I will close it and submit a cleaner one.


Mention actually required version of svd2rust

Issue #547 mentions this but it would be nice to have this information in this prominent place. Version 0.17.0 works for me.

Thanks! Hopefully we can bump this to the latest version soon, but even then it will make sense to track the required version in the README.

https://github.com/stm32-rs/svdtools/pull/57


Charvi/html

This one should have everything (or i'm just crazy). Again, if you have any inputs on topics to add, remove or reorder, let me know.

Let's change the PR name here to HTML or HTML and CSS if you do both in this PR


3.2: Software Skinning being used despite hardware capability

Godot version:
0a2a93b
OS/device including version:
Windows 10 [10.0.18362.1082]
NVIDIA GeForce RTX 2080 Ti
Driver 452.06
Issue description:
With the new PR that landed, Godot appears to be using software skinning (as evidenced by a new rendering bug) both in a case where I created a new project and in a case where I open an older existing project.
The expected behavior is to whitelist the specific low-end hardware which needs to use software skinning, so as to not degrade performance on high-end systems.
Steps to reproduce:

Make a new project
Import a GLB with blend shapes.
Switching tabs to a model with blend shapes is perceptibly slower (I think about 0.2 seconds, compared with instantaneous) with a new release build compared to 3.2.3.stable. See here for the test project with this model https://github.com/godotengine/godot/issues/42767

Minimal reproduction project:
https://github.com/godotengine/godot/files/5371719/GLTFBug.zip

Regression fixed by #42846. (#37854 is still valid.)


When enabling the -- enable mpeller, the video cannot be displayed

When I use video_player plug to play video and enable --enable-impeller, the video has sound but no image，The playback is normal when the --enable-impeller is turned off

I also can see this issue on video_player: ^2.4.10, using video_player sample code.
When playing the video, the sound is played but no visual.

Demo
https://user-images.githubusercontent.com/104349824/210709477-cba8375d-a285-4352-b1ce-27ce26be078d.mp4

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.3.10 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (13 hours ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.7.0-14.0.pre.39, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.7.0-14.0.pre.39 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision da1a854911 (36 minutes ago), 2023-01-04 22:36:16 -0500
    • Engine revision 35b7dee32b
    • Dart version 3.0.0 (build 3.0.0-85.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

The issue is reproducing on Realme 6, Android 11 but it plays as expected on iPhone 14 Pro Max, iOS 16.1 (emulator). Do you also have this issue on Android?

I didn't test Android devices，my device is iPhone X(IOS 15.6)

when i use video_player sample code I got the same result

Demo
[](https://user-images.githubusercontent.com/30917668/210797578-b91b8625-62be-4ca4-ade4-c1b28f454f3c.mp4)

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.7, on macOS 13.0.1 22A400 darwin-arm, locale zh-Hans-CN)
    • Flutter version 3.3.7 on channel stable at /Users/middou/Library/Android/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e99c9c7cd9 (9 weeks ago), 2022-11-01 16:59:00 -0700
    • Engine revision 857bd6b74c
    • Dart version 2.18.4
    • DevTools version 2.15.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/middou/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • ANDROID_HOME = /Users/middou/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Connected device (3 available)
    • 大魔王 (mobile)    • 55e203e5645c0f1478a5c08dd55ad2a97ed1f52e • ios            • iOS 15.6 19G71
    • macOS (desktop) • macos                                    • darwin-arm64   • macOS 13.0.1 22A400 darwin-arm
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

We don't expect this to work on Android with impeller, or on the last stable with either Android/iOS
Can you please clarify which versions of flutter (including flutter doctor) and which platforms this isn't working as expected on?

@Small-World I can see you are using 3.3.7. I also see it doesn't work on the latest stable 3.3.10. But it works on the latest master 3.7.0 with my device iPhone 7, iOS 15.7.2. Please retry on master channel and confirm this.
And as @jonahwilliams commented above, please also check this as reference: https://github.com/flutter/flutter/wiki/Impeller#availability

Demo (on master)
https://user-images.githubusercontent.com/104349824/210924199-dfe3cbd1-3610-45fd-99e0-4e8bd7fab22e.MP4

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.3.10 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (13 hours ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.7.0-14.0.pre.52, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.7.0-14.0.pre.52 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 507062032f (2 hours ago), 2023-01-06 01:13:18 +0100
    • Engine revision 5bd90d6e77
    • Dart version 3.0.0 (build 3.0.0-85.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Thank you!  i get it