BDSX form bug?

Describe the bug (Required)
BDSX forms.
In doing so, I have set up images on the simple form, but some of the images are not displaying properly.
To Reproduce (Required)
Simply set the following, "available" URLs as images and create the form.
URL:

https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/oak_boat.png
https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/acacia_boat.png
https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/dark_oak_boat.png
https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/spruce_boat.png
https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/birch_boat.png
https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/jungle_boat.png
https://raw.githubusercontent.com/kaito02020424/bedrock-items/main/dist/textures/mangrove_boat.png

Expected behavior
An image of the boat is normally displayed.
Error logs
No error log
Environment

Server: Windows 10
BDSX commit: latest

Additional context

Here is the image in question.
Normal images, such as boats with chests, are shown.

Other images etc. can be used as usual, but for some reason only this URL does not work.

BDSX sends the form JSON to the client and the client loads the image URL itself.
There is nothing BDSX can do.


Impossible to transform from a discriminated union to another using a different discriminant field

It does not seem to be possible to change the discriminant from one property to another and have that recognised as the proper type.

TypeScript Version:  3.8.0-dev.20191116

Search Terms: discriminated union, discriminant, kind, type
Code
interface Car {
  kind: 'car'
  trunkSize: number
}

interface Bike {
  kind: 'bike'
  handlebarColor: string
}

interface ApiCar {
  type: 'car'
  trunkSize: number
}

interface ApiBike {
  type: 'bike'
  handlebarColor: string
}

type Vehicle = Car | Bike

type ApiVehicle = ApiCar | ApiBike

const unknown = {
  type: 'car',
  trunkSize: 5
}

function makeVehicle(vehicle: ApiVehicle): Vehicle {
  return { ...vehicle, kind: vehicle.type }
}

Expected behavior:
Object returned by makeVehicle should successfully be interepreted by the compiler as a Vehicle
Actual behavior:
Does not compile with the following error:
Type '{ kind: "car" | "bike"; type: "car"; trunkSize: number; } | { kind: "car" | "bike"; type: "bike"; handlebarColor: string; }' is not assignable to type 'Vehicle'.
  Type '{ kind: "car" | "bike"; type: "car"; trunkSize: number; }' is not assignable to type 'Vehicle'.
    Type '{ kind: "car" | "bike"; type: "car"; trunkSize: number; }' is not assignable to type 'Car'.
      Types of property 'kind' are incompatible.
        Type '"car" | "bike"' is not assignable to type '"car"'.
          Type '"bike"' is not assignable to type '"car"'.(2322)

Playground Link:
http://www.typescriptlang.org/play/?ts=3.8.0-dev.20191115&ssl=31&ssc=36&pln=30&pc=53#code/JYOwLgpgTgZghgYwgAgMJysg3gKGcga1ABMAuZAcgQwr2TCgFcQCBlYALwnJEYFsARtBwBfHDlCRYiFACFgBFLnxEQZSgIURa+ABZw1AGwgCMqAPaHzUcgGcGoAOajxk6PCTIAggAdg6TGV6AE8fbkpqKB16JhZ2Lh5+ISgXCXB3GW8-eUVsOjBQ8IpNRWj9IxMzS2s7BxBnMRwCsOQANQhdYARjZABeNAxkAB8AApyIcWaUX2B2zu6UfpmA4azgcfEEcxB7ZGYCEHMAdxA+vPwp8ioaABp82LZOcIBWVJhmBDBgbeQ+OEU5l1jAAKABuHSB4RmgIWAEpyDCekEoBAwIwoKcsMgAHS48HzYw3Qgkcj4yHYqbIMQiIA

Yeah, this is admittedly a weird problem, but it’s a known design limitation. I was looking for similar reports and the team pointed me to #31445, though I feel like I’ve seen simpler cases. The problem is that when you do { ...vehicle, kind: vehicle.type }, the type system is essentially tracking two types:

vehicle, which is ApiCar | ApiBike, and
vehicle.type, which is 'car' | 'bike'

but the type system can’t tell that these two types are dependent upon each other because they both originate from vehicle—doing so appears intuitive and easy here, but in practice it would get extraordinarily complex and expensive to track these relationships. So TypeScript sees this as trying to combine “either an ApiCar or an ApiBike” with a kind of “either 'car' or 'bike',” which is unsafe. E.g., TS thinks there’s a possibility that { ...vehicle could be a car but vehicle.type could be 'bike'.
You can get a working solution if you discriminate on type first, because then the type system does know the narrowed type of vehicle (and of course the type of vehicle.type), but you end up writing code that you’d never write in vanilla JS:
function makeVehicle(vehicle: ApiVehicle): Vehicle {
  if (vehicle.type === "car") return { ...vehicle, kind: vehicle.type };
  return { ...vehicle, kind: vehicle.type };
}

Personally, I think this is an appropriate place for a type assertion:
function makeVehicle(vehicle: ApiVehicle): Vehicle {
  return { ...vehicle, kind: vehicle.type } as Vehicle;
}

“TypeScript can’t know this is sound, but I know this is sound.”

Thank you for the detailed explanation @andrewbranch ! I don't think the type assertion is even needed, just copying the property from type to kind was enough for me to have the object inferred as the right type.
Closing as this is already an aknnowledged limitation


At least X feature

@uglyog, I'm not super keen on the way the current implementation of the 'at least' feature means we have to string parse the match value to work out how many items need to match.
https://github.com/bethesque/pact-specification/blob/version-2/testcases/request/body/array with at least two elements expected.json
Also, it seems that this would be better named "starting with". I was confused as to why this example was a failure until I realised that order mattered: https://github.com/bethesque/pact-specification/blob/version-2/testcases/request/body/array with at least one element but the element is different.json
I'm also not sure why we need to put in the number, as I'm pretty sure you pointed out that the number of elements in the expected array indicates how many we need to match?

That was the initial idea I tried. Please refer to the discussion on #14

Closed as it's been included in #14


En-Dash special character support

https://datametica.atlassian.net/browse/RSFB-3189

Looks good to me!


Support old and new git release tag formats

Description
Update the flutter version determination logic to support both old and new tag formats.
Old Tags

v1.2.3
v1.2.3+hotfix.1

New Tags

1.2.3
1.2.3-dev.4.5

Related Issues
Fixes https://github.com/flutter/flutter/issues/53688
Tests
Updated existing unit test to verify both old and new style tag format.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

It might be simpler to try to parse it twice - once using the old regexp and one using the new.  And then to add new fields to the GitTagVersion class for the dev.([0-9]+).([0-9]+) values (e.g. devRevision, patchNumber?)

Firebase test lab failure looks to be infra related, following up in infra chat.


implement holiday api

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

31 of 123 (25.2%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-24.04%) to 70.241%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

holidays-api/holiday/holidays.go
0
24
0.0%

holidays-api/holidaysapi.go
31
99
31.31%

Totals

Change from base Build<PHONE_NUMBER>:
-24.04%

Covered Lines:
262

Relevant Lines:
373

💛  - Coveralls


Issue with custom azure policy definition

[Enter feedback here]
I have created a custom Azure policy definition that should enforce mandatory tag names and be applied at the resource group scope. The parameter names and values are defined, and the mode is set to "All" since the scope is applied at the resource group with a "deny" effect. Once the policy definition was created, I assigned the policy to one of the management groups, which contains several subscriptions. Here, the non-compliance value is specified with a message.
In a scenario where a user attempts to create a resource group without the mandatory tags, the deployment should fail, and the error message mentioned in the non-compliance field should be displayed. However, in my case, it did not appear. To address this, I attempted to include the "message" under the "details" section within an if condition but encountered an error stating that the policy mode is "All."
How can I communicate to the end user that the resource group deployment failed for some reason?
"then": {
  "effect": "deny",
  "details": {
    "message": "This resource does not comply with the specified policy. Please review the policy requirements and make the necessary changes.",
  }
}

See the error message in the picture, there is no navigation which is pointing to the non-compliance message or raw error.

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

ID: 07fab47b-3b7a-c02e-c863-2c60f0e06f94
Version Independent ID: f1643e7a-14eb-c372-8099-2f412c954717
Content: Overview of Azure Policy - Azure Policy
Content Source: articles/governance/policy/overview.md
Service: azure-policy
GitHub Login: @davidsmatlak
Microsoft Alias: davidsmatlak

#assign:davidsmatlak

#assign:davidsmatlak

@boinisk
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@boinisk To get your question routed to the correct support team, open an Azure support case.

#please-close


[@kie-tools-core/uniforms-patternfly] Add description icon

In Kaoto a description icon is shown to explain what the field's purpose is.

This is done by injecting a property directly into the field object that later on gets passed to the underlying patternfly component. You can see it here.
The goal for this issue is to explore if this feature might be of interest to the library and if so, how to make it optional, so the existing behavior is kept.
The data from this button comes from the schema.description property from JSON schemas

The first idea that comes to my mind is to create a react Provider that will serve not only as an enabler of the feature but also as the locator for the information.
const fn = (field: string) => {
  // get the description for the field somehow using the field name
};

<DescriptionProvider locatorFunction={fn}>
    <AutoForm .../>
</DescriptionProvider>

Then later on, the compatible fields can check whether the DescriptionProvider exists or not, and if so, use the provided function to retrieve the description.

@ljmotta may I ask your input on this one? :)

I've created a PR with this change. Please take a look when you have time!

Thanks a lot @ljmotta for checking this out. I'll check the PR and try to apply it also to the fork that uses patternfly v5

@lordrip The footer value comes from which property from the JSON schema?

@ljmotta from the default property.
https://json-schema.org/understanding-json-schema/reference/annotations
Here's an example: https://github.com/apache/camel/blob/camel-4.2.x/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L407-L412

@lordrip Oh, ok. It looks like a good idea to add this to the labelInfo too... But what happen when you don't have a description and you have a default value? You render the help icon too?
Looking at the images you posted the help icon has a border which is not present on my PR, maybe it's related to the PF5?

@ljmotta mmm, you're raising a good point, If we don't have description I think we don't show anything. IMHO that's not good (talking at least Kaoto side), I need to check on my side to confirm.
I think the default should be shown even in case there's no description, my reasoning is the user might set a value, hence removing the possibility to see the default value in the placeholder, we could still see it in the popup

I'm wondering if would be useful to allow custom views for those popup.


remove extraneous NL

see https://github.com/adhocore/please/releases/tag/0.0.9
the release note which is composed of commits looks like
fix(please): silence npm, show version after bump

docs: update usage

but it should be:
fix(please): silence npm, show version after bump
docs: update usage

i.e without extra NL between two commits.
where to fix: https://github.com/adhocore/please/blob/master/please#L207

done in https://github.com/adhocore/please/releases/tag/0.1.0


[#7142] fix sender

add vo sender package
arrange Rule getter/setter method
change method naming triggerWebhook -> sendWebhook
change class naming SpringWebhookSender -> WebhookSenderImpl
arrange webhookEnable check method in WebhookSender
add email,phonenumber,countrycode to UserMember

머지 하겠슴돠~


Deprecation warning for snowflake.StageGrant uses TF name

What happened?
Creating a resource of type snowflake.StageGrant gives the user a deprecation warning that references the TF name:
Diagnostics:
  snowflake:index:StageGrant (snowpipe-stage-grant):
    warning: urn:pulumi:dev::snowflake-pulumi-search-export-py::snowflake:index/stageGrant:StageGrant::snowpipe-stage-grant verification warning: This resource is deprecated and will be removed in a future major version release. Please use snowflake_grant_privileges_to_role instead.

Expected Behavior
n/a
Steps to reproduce
n/a
Output of pulumi about
CLI
Version      3.74.0
Go Version   go1.20.5
Go Compiler  gc

Plugins
NAME       VERSION
aws        5.41.0
command    0.7.2
python     unknown
snowflake  0.29.0

Host
OS       darwin
Version  13.3.1
Arch     arm64

This project is written in python: executable='/Users/jkodroff/src/pulumi/examples/snowflake-py-pulumi-search-export/venv/bin/python3' version='3.11.4
'

Current Stack: jkodrofftest/snowflake-pulumi-search-export-py/dev

TYPE                                                   URN
pulumi:pulumi:Stack                                    urn:pulumi:dev::snowflake-pulumi-search-export-py::pulumi:pulumi:Stack::snowflake-pulumi-search-export-py-dev
pulumi:providers:aws                                   urn:pulumi:dev::snowflake-pulumi-search-export-py::pulumi:providers:aws::default
pulumi:providers:aws                                   urn:pulumi:dev::snowflake-pulumi-search-export-py::pulumi:providers:aws::default_5_41_0
aws:iam/role:Role                                      urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:iam/role:Role::lambda-role
aws:s3/bucket:Bucket                                   urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:s3/bucket:Bucket::pulumi-search-export
aws:ssm/parameter:Parameter                            urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:ssm/parameter:Parameter::pulumi-token
pulumi:providers:command                               urn:pulumi:dev::snowflake-pulumi-search-export-py::pulumi:providers:command::default_0_7_2
pulumi:providers:snowflake                             urn:pulumi:dev::snowflake-pulumi-search-export-py::pulumi:providers:snowflake::default_0_29_0
snowflake:index/storageIntegration:StorageIntegration  urn:pulumi:dev::snowflake-pulumi-search-export-py::snowflake:index/storageIntegration:StorageIntegration::snowflake-storage-integration
aws:iam/rolePolicyAttachment:RolePolicyAttachment      urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:iam/rolePolicyAttachment:RolePolicyAttachment::lambda-execute-policy
aws:iam/policy:Policy                                  urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:iam/policy:Policy::snowflake-storage-integation-policy
aws:iam/policy:Policy                                  urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:iam/policy:Policy::pulumi-search-export-to-s3-policy
aws:iam/role:Role                                      urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:iam/role:Role::snowflake-integration-role
aws:iam/rolePolicyAttachment:RolePolicyAttachment      urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:iam/rolePolicyAttachment:RolePolicyAttachment::ssm-params-attachment
snowflake:index/database:Database                      urn:pulumi:dev::snowflake-pulumi-search-export-py::snowflake:index/database:Database::pulumi-snowflake-integration
snowflake:index/schema:Schema                          urn:pulumi:dev::snowflake-pulumi-search-export-py::snowflake:index/schema:Schema::pulumi-snowflake-integration
snowflake:index/table:Table                            urn:pulumi:dev::snowflake-pulumi-search-export-py::snowflake:index/table:Table::pulumi-search-exports
command:local:Command                                  urn:pulumi:dev::snowflake-pulumi-search-export-py::command:local:Command::vendor-deps
aws:lambda/function:Function                           urn:pulumi:dev::snowflake-pulumi-search-export-py::aws:lambda/function:Function::pulumi-search-export-to-s3

Found no pending operations associated with dev

Backend
Name           pulumi.com
URL            https://app.pulumi.com/jkodroff
User           jkodroff
Organizations  jkodroff, oracle-workshop, jkodrofftest, zephyr, demo, pulumi

Dependencies:
NAME              VERSION
pip               23.1.2
pulumi-aws        5.41.0
pulumi-command    0.7.2
pulumi-snowflake  0.29.0
setuptools        67.6.1

Pulumi locates its logs in /var/folders/5m/4n1x3f8151s35wc80w06z5k80000gn/T/ by default

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thanks for reporting this @jkodroff. The fix will be in the bridge, so I opened https://github.com/pulumi/pulumi-terraform-bridge/issues/1297 to track.

Hi there,
I also got this message. In this case, what is the recommended action from our end?

You will need to switch to a non-deprecated resource. The Pulumi token is "snowflake:index/grantPrivilegesToRole:GrantPrivilegesToRole". This corresponds to:
CSharp:
https://github.com/pulumi/pulumi-snowflake/blob/2434685933e63909217a3f720f9d018e14ca2998/sdk/dotnet/GrantPrivilegesToRole.cs#L109
Python:
https://github.com/pulumi/pulumi-snowflake/blob/2434685933e63909217a3f720f9d018e14ca2998/sdk/python/pulumi_snowflake/grant_privileges_to_role.py#L287
Typescript:
https://github.com/pulumi/pulumi-snowflake/blob/2434685933e63909217a3f720f9d018e14ca2998/sdk/nodejs/grantPrivilegesToRole.ts#L105
Go:
https://github.com/pulumi/pulumi-snowflake/blob/2434685933e63909217a3f720f9d018e14ca2998/sdk/go/snowflake/grantPrivilegesToRole.go#L119
Java:
https://github.com/pulumi/pulumi-snowflake/blob/2434685933e63909217a3f720f9d018e14ca2998/sdk/java/src/main/java/com/pulumi/snowflake/GrantPrivilegesToRole.java#L120

Is there any example?

Sorry, one more question, does it make the grant stop working?

@rvasconcelossilva

Does it make the grant stop working?

Not entirely sure if this is what you're asking, but the StageGrant resource still works, it's just that you get a deprecation warning. I was not able to figure out the syntax for granting to a Stage using GrantPrivilegesToRole when I filed this issue and just continued using StageGrant. The code I was working on will eventually be publicly available (maybe even this week). I'll post the example I was working on if you let me know you want to see it.
However, I think that the docs might've gotten updated since I originally filed the issue, because it looks like GrantPrivilegesToRole.onSchemaObject is the right way to specify a grant to a STAGE: https://www.pulumi.com/registry/packages/snowflake/api-docs/grantprivilegestorole/#grantprivilegestoroleonschemaobject
Good luck, and please post your code if you get something working! I'll do the same if I can get GrantPrivilegesToRole working with a STAGE.

Is there some where I can see the change? I believe there are changes in the arguments and many other things right? I believe any deprecated resource should have a how to migrate to the new one. Is there a way to help with that?


accept major minor version for cluster upgrade

./rosa upgrade cluster -c 1t9qanso4h9ch0n0du5af0htdk177qqv --version 4.10
I: Ensuring account and operator role policies for cluster '1t9qanso4h9ch0n0du5af0htdk177qqv' are compatible with upgrade.
I: Account and operator roles for cluster '1t9qanso4h9ch0n0du5af0htdk177qqv' are compatible with upgrade
? Are you sure you want to upgrade cluster to version '4.10.20'? (y/N)
pvasanth@localhost: (acceptmajorminorforclusterupgrade *) $ ./rosa upgrade cluster -c 1t9qanso4h9ch0n0du5af0htdk177qqv --version 4.9
E: Expected a valid version to upgrade to
pvasanth@localhost: (acceptmajorminorforclusterupgrade *) $ ./rosa upgrade cluster -c 1t9qanso4h9ch0n0du5af0htdk177qqv --version 4.8
E: Expected a valid version to upgrade to
pvasanth@localhost: (acceptmajorminorforclusterupgrade *) $ ./rosa upgrade cluster -c 1t9qanso4h9ch0n0du5af0htdk177qqv --version 4.9.40
I: Ensuring account and operator role policies for cluster '1t9qanso4h9ch0n0du5af0htdk177qqv' are compatible with upgrade.
I: Account and operator roles for cluster '1t9qanso4h9ch0n0du5af0htdk177qqv' are compatible with upgrade
? Are you sure you want to upgrade cluster to version '4.9.40'? (y/N)
pvasanth@localhost: (acceptmajorminorforclusterupgrade *) $ ./rosa upgrade cluster -c 1t9qanso4h9ch0n0du5af0htdk177qqv --version 4.8.40
E: Expected a valid version to upgrade to
https://issues.redhat.com/browse/SDA-6119

@oriAdler  PTAL this is a minor enhacement which allows to specify just major and minor during cluster upgrade

@ciaranRoche @zgalor  PTAL

/lgtm


Combine setting mode and ODR functions.

Combine setting mode and ODR into one function so that we can properly determine the correct delay.

@eldruin, can you have a look at this? Thanks!

Would it be possible to add some tests for these combinations?

These are actually all tested, e.g. https://coveralls.io/builds/52363719/source?filename=src%2Faccel_mode_and_odr.rs#L205.
Added a changlog entry and a test covering the other function.


Added code examples for missing APIs (for Node, Python, Java and cURL)

Not all endpoints were available in all SDKs

@gustavo-bertoldi it looks good to me, could you just resolve the conflicts? :) it seems we both have added the same file xD

Done :) @tsolakoua


Added space bar to trigger use action

Laptop users were having issues with the mouse click triggering the event.

Forgor to stage, oops

I enjoy spamming spacebar more than I enjoy spamming click. I approve.


Notebook for spinal cord analysis

Context
The purpose of this issue is to come up with a plan for presenting/formatting the output of the spinal cord analysis on the notebook.
Suggestion 1
Use results from the latest release, eg: here
Display one plot per metric. Each tick in the abscissa corresponds to one subject. Given that some subjects have multiple sessions, we could show the result of each session with a single plot. This plot could be interactive (ie: value is shown when passing cursor on it). For inspiration, see spine-generic.

📌 Demo
Example notebook:  anat-processing-book/01/1-test.ipynb


grouping exogenous shocks into collection

As per discussion in #757, try combining the exogenous shock distributions (and/or processes) into a collection and finessing the data types in the cases where they are age or state varying.

I think we should talk about this (and AgentType stuff) right now on call.
On Thu, Jul 16, 2020 at 10:31 AM Sebastian Benthall <
<EMAIL_ADDRESS>wrote:

As per discussion in #757 https://github.com/econ-ark/HARK/pull/757,
try combining the exogenous shock distributions (and/or processes) into a
collection and finessing the data types in the cases where they are age or
state varying.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/760, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFJIZGQTFNQ3IOCKWB3R34FKLANCNFSM4O4LJN7Q
.

Fixed with #803


re-add alert groups endpoint

requested in #868
this contains a lot that is open to discussion, including:

what the definition of the returned struct/struct members for the alert groups endpoint should be
the implementation of finding the groups, particularly the weird bit with the giving the EnrichedAlert a reference to a slice of its receivers. staticcheck isn't happy about how I went about doing this, either.
all the naming (like EnhancedAlert), and the path name /alerts/groups

I decided to wait on writing any tests until we can figure out what it is we want to have in this pr

PR that removed alert groups originally: https://github.com/prometheus/alertmanager/pull/1525/files

Aw, if I accept your suggestions they fail because they have no DCO

Made a lot of changes based on @simonpasquier 's suggestions, when you have a chance take a look. Did some rough manual testing and it seems to be working.

ptal when you two have a chance

Logic in dispatch looks very clean! Just small comments, nothing major.
Given that this could fix the compatibility issues with karma, @prymitive do you have thoughts on this as well?

In general this seem to make it easier for me, for example karma already has a concept of alert group, I don't see anything that could be problematic for me in any obvious ways. That being said I'm currently traveling so I'm not gonna pretend that I've put a lot of effort into reviewing this or trying to use this code.

Added a test

FYI I'll be back home next week and I'll be able to do some integration tests agains this PR for karma, if that's helpful

Definitely! would love to hear if this is useful for you, or if there's anything you would like to add/change

Can this PR be progressed?
Thanks

Can this PR be progressed?

Waiting for some feedback from @prymitive, and if there are any more questions/comments from @mxinden and @simonpasquier

I hope to get some work done today evening

I was able to get it working easily with those changes and it seems to be working perfectly 🎉
I used the alert generator I have on http://karma-demo.herokuapp.com and I got exact same set of alerts via the v2 API 🎉
It also looks like I could kill some of the ugly code I have in the backend if I would drop support for non openapi alertmanager versions.
There's really not much feedback I can provide other than "it works" since all karma is doing is pulling all silences and alerts, so it's a very basic use of the API provided.
Thanks! Great work!

great to hear! once I get a final :+1: from @mxinden and @simonpasquier this will be merged

@stuartnelson3 You got a chance to look at Max's comment ? Would be great to have this merged in soon. Thanks for your work on this :)

@stuartnelson3 You got a chance to look at Max's comment ? Would be great to have this merged in soon. Thanks for your work on this :)

thanks for the ping, i missed his message!

Other than #1791 (comment) this looks good to me. Thanks @stuartnelson3!

sorry for missing that log line, I added it to the alert groups endpoint but not the normal alerts endpoint. hopefully now this PR is good to go

@mxinden Are you happy with the latest changes?

Once this PR is merged, when do you think the next alertmanager version is going to be released?

I plan on releasing 0.17.0 next week, which will include this PR.


tag_retry is slow

When doing retry on thousands of events, I noticed the method is slow.
Maybe we can switch to Cursor.executemany instead of Cursor.execute for the Batch._flush_retry implementation.
... and measure if it gives some benefit.

This is still the case with pgqueue 0.5,  PgQ 3.2.6.
For example I measured on my workstation:

insert_event for 40000 events : between 9.3 and 19.0 seconds
no-op loop on next_events for 40000 events : ~ 1.8 seconds
tag_retry for 40000 events : ~320 seconds

If I switch the implementation of tag_retry to use pgq.event_retry_raw(...), it seems much faster : ~13 seconds

Fixed with pgqueue 0.6 just released


ClientUpdateMachineAuth not working

Describe the bug
using email auth account , sentry event not emit
logOnOptions is  {dontRememberMachine: false}
Versions
4.28.9

have u fixed it ? I have same problem

Steam isn't using sentry files anymore. 4.29.0 has a fix for this.

Steam isn't using sentry files anymore. 4.29.0 has a fix for this.

thanks :)


Support decorators

This is needed to write Angular2 apps. Need to include TypeScript from head, or package the 1.5 beta when it is out.

@alexeagle they should be working. We are already post alpha TypeScrit 1.5 alpha: https://github.com/TypeStrong/atom-typescript/blob/master/package.json#L37

Atom-TypeScript is now up to date with TypeScript master by 3 days. :rose:

Thanks, it was indeed working, I think we had some miscommunication about the rebuild we did for --emitDecoratorMetadata but the emit from Atom does look right.
We plan to promote the plugin to Angular users! (along with WebStorm and Sublime Text)

We plan to promote the plugin to Angular users!

Thanks!


work with scnView

Hi
this is work with SCNView ?

Hi, yes it is. It supports both ARSCNView and SCNView, with Metal or OpenGL. Look at the example.

thanks


Added option to set font family for FlowElement

What's so good about this feature?
This feature give you the ability to show colorful emojis on the Flow Element using unicodes as shown below when used with a proper font such as Noto Color Emojis. Given the limitations of high level customization of the flow element, I think this is pretty neat 😃

Why is this feature neat
This feature give you the ability to show colorful emojis on the Flow Element as shown below when used with a proper font such as Noto Color Emojis. Given the limitations of high level customization of the flow element, I think this is pretty neat 😃

Thanks again!! If I remember well, it was a bit messy to add a TextStyle parameter because it must be entirely converted to json for the save and load functionality.

Yes your memory is right.
This workaround will not let you allow to use something like the google_fonts package but at least you'll be able to use custom fonts instead


Themekit unable to install

Problem
User Yarn unable to install.
Replication steps
Binary is fine

><EMAIL_ADDRESS>postinstall D:\Desktop\Shopify theme\Noostop\node_modules\@shopify\themekit
> node ./lib/cli.js install
\

More Information
Node version may not be able to download and compile

Could you provide additional information about your environment?

yarn version
node version
operating system

Could you provide additional information about your environment?

yarn:  v1.22.4
node:  v12.16.1
operating system : windows

I think was down to an AWS issue at the time. I remember having this and I ended up doing a brew install themekit and you could see it was taking minutes just to get 0.1% of a download. I think it being through NPM was masking this for the node variant

@Noostop I'll close this, bt please let us know if you run into this problem again.


spell-check and re-word beginning of covid-19 dungeon for readability

#112 fixed spelling. The route had an option to just "go into the dungeon" which didn't make sense if you were chained to a post, but another route has you break the chain after getting strong, so I don't know what we should do.

Fixed linking issue that @paulsonjpaul spotted, then resolved merge conflict with #123 that fixed WIP link

Good. Now it makes sense. Add some emojis 😉

Hi @Gborgman05 and @paulsonjpaul,
Any update?

@ming-tsai , @paulsonjpaul , just added some emojis to spice up the route. I'd love any feedback!

Nice work @Gborgman05


docs(content): remove aio stuff

I removed angular related content. Maybe we have to recover some of the example generation parts later on, but for now I would remove it to make the repository clearer

Coverage increased (+0.2%) to 96.947% when pulling 62b77e8f114a8879b9ecb469bd46ee6a532a7ff1 on JWO719:refactoring/remove_unused_stuff into 37c5c090c04a4bd1bfa31fbfc289c825e8e2a81e on ReactiveX:master.


Adds color labs settings and schema, plus updates org file to add genabio to the production settings

This PR adds color labs settings and schema, plus updates org file to add genabio to the production settings.
Test Steps:

Include steps to test these changes

Changes

Adds a schema for color labs
Adds a settings file for genabio and color
Adds a settings to the org file for genabio ad color

Email from Genabio: @MauriceReeves-usds
To Whom It May Concern:
This is Juehua Yu from Genabio. We are working on report submission by CDC ReportStream system. We have generated EC384 key by following "Step 1:  Prior to submission, send your public key to ReportStream" in the doc "ReportStream-Programmers-Guide-v2.3-updated.docx". The public key has been sent to ReportStream team and had notification back. However, in the following sections at that doc and the github site(https://github.com/CDCgov/prime-reportstream/tree/master/prime-router/examples/generate-jwt-python/
prime-reportstream/prime-router/examples/generate-jwt-python at master · CDCgov/prime-reportstream
Contribute to CDCgov/prime-reportstream development by creating an account on GitHub.
github.com
), only RSA256 is used. So we just wonder whether we can use our old one public key or have to regenerate a new key by RSA256.
Your kindly help will be appreciated!
Sincerely
Juehua


Add support for auto-detecting video content (#277)

Here's a first cut at auto-detecting video content. Let me know what you think of this approach.
If the attached file has an mp4 or webm extension, we'll generate a <video> tag instead of an img tag. The tests are probably the best demonstration of that.
Right now, this is not configurable or overridable. I will try to use image attributes so that {type=image} or {type=video} forces the tag type but my best solution so far feels pretty hacky... (AttributeProvider.setAttributes wants to extend attributes and know the tag name... but I don't have the attributes to extend or know the tag name because I need type to know that - Ignoring those problems, the solution works, it just feels dirty)

Have you looked at how hard it is to implement this without changes in commonmark-java?

I haven't tried that. Given that there doesn't seem to be any standard syntax for generating an embedded video, maybe that's the best option.

Ok 👍. Yeah I wish there was a commonly accepted syntax, then it would be a no-brainer to implement that.


Possible fixes #8 compilation failed regex too large

Signed-off-by: Abdul Malik Ikhsan<EMAIL_ADDRESS>

Q
A

Bugfix
yes

Description
This is a possible quick fix for #8 . I am not sure if it is correct, but hostname with @ seems invalid.

@ac-dc @Thaix could you verify if this patch works for you ?

Yes, it works on my machine!
Before:
` $ php -a
Interactive mode enabled
php > include 'vendor/autoload.php';
php > var_dump((new Laminas\Validator\Hostname())->isValid('tapi4457@hsoqvf.biz'));
PHP Warning:  preg_match(): Compilation failed: regular expression is too large at offset 156184 in /home/apidev/current/vendor/laminas/laminas-validator/src/Hostname.php on line 2104
bool(false)
After php -a
Interactive mode enabled
php > include 'vendor/autoload.php';
php > var_dump((new Laminas\Validator\Hostname())->isValid('tapi4457@hsoqvf.biz'));
bool(false)
`

@weierophinney do we have list of known-bad characters for hostname?

do we have list of known-bad characters for hostname?

I think part of the complexity of the regex is a list of characters to exclude, IIRC. :smile:

How about merge for now?

@weierophinney I think we can merge as is for now, as concrete solution seems not imaginable right now.


Fix main call to actions.

Fix style to match design
send button should always be present to avoid confusion. Error for no funds should be presented on sending view.

zpl.io/Vk5m4DZ

https://media.giphy.com/media/xT9DPr4VjeCgeiLoMo/giphy.gif


Workshop updates

@jmejco  , @tamara-h  ,
Workshop site should be update to reflect the following changes once v3.1.7 is merged

Added support for customer managed policies
Added support for permissions boundary
Validated functionality with delegated admin support

Workshop is now updated


[EBPF] gpu: compute utilization based on active GPU

What does this PR do?
This PR enables multi-gpu support in the utilization calculations.
Motivation
Up until now, the calculation defaulted to the first GPU device found. After multi-GPU support has been added, we can rely on the actual device.
Describe how you validated your changes

Unit test included.
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Error 3160009: No wast file found

user@ubuntu:~/eos/build/contracts/eosio.token$ ls CMakeFiles           eosio.token.abi      eosio.token.cpp.bc  eosio.token.wast cmake_install.cmake  eosio.token.abi.hpp  eosio.token.s       eosio.token.wast.hpp CTestTestfile.cmake  eosio.token.bc       eosio.token.wasm    Makefile user@ubuntu:~/eos/build/contracts/eosio.token$ cleos -u http://jungle.cryptolions.io:18888 set contract linlibinieos eosio.token Reading WASM from eosio.token/eosio.token.wasm... Error 3160009: No wast file found Error Details: no wasm file found eosio.token/eosio.token.wasm user@ubuntu:~/eos/build/contracts/eosio.token$
why No wast file found?

@StupidStudentInSchool did you manage to solve this?

have you try manually @rohanagarwal94  using https://github.com/EOSIO/eosio.cdt
eosio-wasm2wast  test.wasm -o test.wast

I tried to upload the contract through cleos set contract hello.code ../hello -p hello.code@active but it didn't find the wast file. Whereas the wasm file is there in the folder.

@rohanagarwal94  Create a hello directory，Enter the directory，touch hello.cpp file , then eosiocpp this file. It will create wasm and wast .abi .Return to previous directory. upload

Alright figured it out. The problem is that cleos was actually an alias to a docker container. So of course the path is not found.
alias cleos='docker exec -it eosio /opt/eosio/bin/cleos'

It works if you deploy from within the container
docker exec -it eosio bash

root@dbfc4a4d2c0f:/# cd hello

root@dbfc4a4d2c0f:/# ls -1
hello.cpp

root@dbfc4a4d2c0f:/hello# eosiocpp -o hello.wasm hello.cpp

root@dbfc4a4d2c0f:/hello# eosiocpp -g hello.abi hello.cpp

root@dbfc4a4d2c0f:/hello# ls -1
hello.abi
hello.cpp
hello.wasm

root@dbfc4a4d2c0f:/hello# cd ..

root@dbfc4a4d2c0f:/# cleos -u http://api.kylin.alohaeos.com set contract helloworld54 hello/ -p helloworld54@active
Reading WASM from hello/hello.wasm...
Publishing contract...
executed transaction: 0179a18622035f2c26149cef5cce7b7d6a640338ab621b6753435363576307d4  1800 bytes  439 us
#         eosio <= eosio::setcode               {"account":"helloworld54","vmtype":0,"vmversion":0,"code":"0061736d01000000013b0c60027f7e006000017e6...
#         eosio <= eosio::setabi                {"account":"helloworld54","abi":"0e656f73696f3a3a6162692f312e30000102686900010475736572046e616d65010...
warn  2018-10-28T21:37:45.193 thread-0  main.cpp:482                  print_result      warning: transaction executed locally, but may not be confirmed by the network yet

root@dbfc4a4d2c0f:/hello# cleos -u http://api.kylin.alohaeos.com push action helloworld54 hi '["bob"]' -p helloworld54@active
executed transaction: c6645daf43f7253e190b6fcab1d5db77b3d5aadf749e5ee36cb7d8a7fe8de027  104 bytes  176 us
#  helloworld54 <= helloworld54::hi             {"user":"bob"}
warn  2018-10-28T21:59:18.515 thread-0  main.cpp:482                  print_result       warning: transaction executed locally, but may not be confirmed by the network yet

Success!

@miguelmota when i try to run eosiocpp -o hello.wasm hello.cpp this command in docker bash
its showing me error eosiocpp command not found, can you please help me out in this?

@shikhars371 Add commands to environment variables

how to do that?

I moved the code to eosio.cdt, but still same error. Any suggestions?

I encountered similar error : Error 3160009: No wast file found Error Details: no wasm file found
Solution:
When starting docker container image using the command below, make sure the to have full-colon before project folder i.e  $(pwd):/your_project_directory
This allows you to move around your project folders and access files.
docker run -it --name waxdev -v $(pwd):/project_directory waxteam/dev bash


Can't decode ber-wrapped PEM private key

Hello, I am trying to use this library (well, actually /x/djwt) to sign a JWT token for a Google Cloud service account. It seems Google Cloud gives a PEM payload that this library cannot read.
> deno run --allow-read mod.ts
error: Uncaught (in promise) TypeError: Unsupported key format
  throw new TypeError("Unsupported key format");
        ^
    at rsa_import_pem (import_key.ts:135:9)

The incompatibility seems to stem from the Google header being -----BEGIN PRIVATE KEY----- (no RSA).
The raw bytes of the PEM look like this:
Uint8Array(1219) [
   48, 130,   4, 191,   2,   1,  0,  48,  13,   6,   9,  42, 134,  72, 134,
  247,  13,   1,   1,   1,   5,  0,   4, 130,   4, 169,  48, 130,   4, 165,
    2,   1,   0,   2, 130,   1,  1,   0, 171,  42, 121,  18,  39, 251, 180,
  173,  40, 219,  42,  81,  41, 49, 181,   1,  41, 111, 240,  24,  66, 159,
  124, 230, 138, 215,  74,  60, 62, 183, 185,  66, 147, 203, 226,  13, 116,
  198, 175, 202, 119,  70, 175, 35, 132, 216, 125, 242, 182, 177, 151, 176,
  102,  39,  28, 193, 131, 173, 33, 173, 103,   6,
  ... 1119 more items
]

I noticed that ber_decode shows a similar inner payload:
{
  totalLength: 1219,
  type: 48,
  length: 1215,
  value: [
    { totalLength: 3, type: 2, length: 1, value: 0n },
    { totalLength: 15, type: 48, length: 13, value: [
      { totalLength: 11, type: 6, length: 9, value: "1.2.840.1135<IP_ADDRESS>" },
      { totalLength: 2, type: 5, length: 0, value: null }
    ] },
    {
      totalLength: 1197,
      type: 4,
      length: 1193,
      value: Uint8Array(1193) [
         48, 130,   4, 165,   2,   1,   0,   2, 130,   1,   1,   0, 171,  42,
        121,  18,  39, 251, 180, 173,  40, 219,  42,  81,  41,  49, 181,   1,
         41, 111, 240,  24,  66, 159, 124, 230, 138, 215,  74,  60,  62, 183,
        185,  66, 147, 203, 226,  13, 116, 198, 175, 202, 119,  70, 175,  35,
        132, 216, 125, 242, 182, 177, 151, 176, 102,  39,  28, 193, 131, 173,
         33, 173, 103,   6, 222, 100, 147, 243, 119, 237,  68,  20, 207, 134,
        118,  18, 210,  67, 165, 251, 219,  88, 227,  46, 241, 127,  18,  69,
        102, 248,
        ... 1093 more items
      ]
    }
  ]
}

1.2.840.1135<IP_ADDRESS> seems to mean RSA encryption.
I was able to extract and re-encode the inner PEM, rewrite my Google service account file with that payload, and then sign a JWT. It seems this library needs to be improved to be able to read this key structure in order to be immediately applicable to JWT signing. #11
Here is a similar key I requested and then immediately deactivated so I can attach it safely:
-----BEGIN PRIVATE KEY-----
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQCVZ6og4XGxLAHH
ZwHm27AtUMP6+8wFqllvup0Tr0V21YvxzPxWjav2+mLOIM8upa7pzvcpc5EiCH58
denmLJsygqo0r2B8WhzHY+rCIWJfV2YSZxjzpvSAHfzLJrDphXgqgnCNxEjRsuyC
YAiGLIMK0huY90A5MMMArgUzkx8kMd/fq/Gd9Xt5iI+F7NlylJ+arnJc306pgGHK
3NN2GBX1vnSuCB280SUXkZfTBeykyDZ6YrAq0XpnCNV9JyHqLQ4EmjEhc2yUo3aN
RyXNMBddZx3HCLFcxwZCVAp0tQkAd7ErsUD5P5DR8RIJ3frklSUUZB6EkDw8G7KL
WKVcNQ2FAgMBAAECggEABVqkmOQ4s2PzlgkDDdofxJFL+KhXMyPGlo+uNd32hA/v
4YTaTSLAv8t7c3jEW/RW4ezyDrj5bD9i2FnPEu8pyk6u7qTon67eBaeMapO7h1Wl
5DEazo5+3WwrBT+4ICI8QG+8vK6E+ojU23DkFU+D4a/OX+C1GzzmsWqgZ+z/inKL
aMwS6rsWROUlgA1x5zNSoqC3SJFllVXXew5UyANTsBjvQ5J2Mmb9g8CEaAOn+xMk
xNlwTlDot+09nFJ9vvAWirUkZdsYNnlY+zrDQoPT7Am5jtKTHmMI1KfWNfmznyji
RltdnWfd8Bg0H7VtwrhWMWGs8QkATUAE+fC3qS144QKBgQDNFLk8eMwK6koMoNmY
vsRAf1Y6Xdd+LUN+TJqkZiUEySaKy8NLi71IBbzK7zKqbYXDPUFCbNJFhOlluKOw
bsKPkwBjR0JfoXVzbUdE+2tM2YccswaJe7iinZxr0wHGXIvJL0HNVIzmNggS7+Zm
rEsdCyFXnTT/83o1wVW3E/lspQKBgQC6gBVyYCP7AxYHTSRDCgcpsTO7HyzuY92t
aYOhRJFC7HNbzJbVdVsfnbtQH/Epe8ySk91GyFZ1dSJrxetcLhHsS2TMrkYUmY4x
bJnqzJTh7cgWBP9DuWYvSJxPooSpFwbh2L12vQ2ADpwwoAZMLkAagaGlY9MZz821
XY+KkOLnYQKBgQCQ49lTTgzqkUirz2Cst+qznsNvDSnYbWZH7xs6lygET5E5cmiS
ETIzlkoiHgjvu91LaRWYNoYAs7yqL18Godo30aXufkP4iHwQht5ZcEAI1Y7NyfYO
YCi8SxpeW3/fgzcHdqnIxbmeVAI0TuW7GHMhG+H8oob1ZjGrlOJYLHaGOQKBgDLO
vgkAxAyYFKI8k8pnqvfivJMXtSfksPmTKzb99QzkWbEClXzlkcOVNvhnG04P2fV8
ruWfol4xYQU3UB02t89F4toYCCOIicJRMcVToqPCIaZOCjSrB3mOMHdJcRaXnVpd
r4/vhQQD9u0QS2bpmrEd66mg/lujzwi/ymEXg5lBAoGAacrPblD+G/DAmTUt3tZw
GLdIvw4BeDyCvzxkJx1Z04rMZH71EEyBDPMBByZNPtjpTuzgAZE71MiD3BVLxj/H
dqEjUVQSjuOUyiJKe5GiGF25Xhe3/1VawurCdHfrv6Xmze+lRDHZuEOcV1FrM+zn
KQXlkpPbL3lU2CpgGFFKlFU=
-----END PRIVATE KEY-----

This workaround isn't pretty but works for the moment if anyone else is in the same boat:
import * as Base64 from<EMAIL_ADDRESS>import { ber_decode } from<EMAIL_ADDRESS>
// workaround for https://github.com/invisal/god_crypto/issues/16
function stripKeyWrapping(originalKey: string) {
  const originalData = originalKey.split('\n').filter(x => x && x[0] !== '-').join('');
  const decoded = ber_decode(Base64.toUint8Array(originalData));
  if (decoded.type !== 48) return false;
  const [_, header, body] = decoded.value as any[];
  if (header?.type !== 48) return false;
  if (body?.type !== 4) return false;
  if (header.value[0]?.value !== '1.2.840.1135<IP_ADDRESS>') return false; // RSA key
  if (!(body.value instanceof Uint8Array)) return false;
  const innerBytes: Uint8Array = body.value;
  return [
    '-----BEGIN RSA PRIVATE KEY-----',
    Base64.fromUint8Array(innerBytes),
    '-----END RSA PRIVATE KEY-----\n',
  ].join('\n');
}

Thanks for reporting. I have added the PKCS8 private key support now. It will be release soon.

I have released the fixed.
https://github.com/invisal/god_crypto/releases/tag/v1.4.4

Hello, I just plugged this new version into a djwt fork and it can understand the Google Cloud keys now. However it seems like there's some incorrect offset in the PEM parsing for PKCS8. I get this error when used as-is: DataDecodeError: The string to be decoded is not correctly encoded. I added some extra bytes onto the key (key = credential.private_key + "    ") and it's a successful workaround.
I'm looking at the test case added here and I'm not sure why it is being less picky. I can delete up to half of the base64 data arbitrarily and it can parse the key ok. But in my actual application, the same base64 string causes atob to throw.
Thanks for your action here!

Interesting. It would be nice if we can more test case. I will investigate more.

I apologize for the lack of reproducability in my above report, I didn't take the time to investigate a root cause further.
It looks like the actual problem is the private key string given by Google includes a final trailing newline. If I un-indent the key in the testcase, and add a trailing newline, it throws the same error:

Deno.test("RSA - Import Private Key (PKCS8)", () => {
  const raw = `-----BEGIN PRIVATE KEY-----
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQCVZ6og4XGxLAHH
ZwHm27AtUMP6+8wFqllvup0Tr0V21YvxzPxWjav2+mLOIM8upa7pzvcpc5EiCH58
denmLJsygqo0r2B8WhzHY+rCIWJfV2YSZxjzpvSAHfzLJrDphXgqgnCNxEjRsuyC
YAiGLIMK0huY90A5MMMArgUzkx8kMd/fq/Gd9Xt5iI+F7NlylJ+arnJc306pgGHK
3NN2GBX1vnSuCB280SUXkZfTBeykyDZ6YrAq0XpnCNV9JyHqLQ4EmjEhc2yUo3aN
RyXNMBddZx3HCLFcxwZCVAp0tQkAd7ErsUD5P5DR8RIJ3frklSUUZB6EkDw8G7KL
WKVcNQ2FAgMBAAECggEABVqkmOQ4s2PzlgkDDdofxJFL+KhXMyPGlo+uNd32hA/v
4YTaTSLAv8t7c3jEW/RW4ezyDrj5bD9i2FnPEu8pyk6u7qTon67eBaeMapO7h1Wl
5DEazo5+3WwrBT+4ICI8QG+8vK6E+ojU23DkFU+D4a/OX+C1GzzmsWqgZ+z/inKL
aMwS6rsWROUlgA1x5zNSoqC3SJFllVXXew5UyANTsBjvQ5J2Mmb9g8CEaAOn+xMk
xNlwTlDot+09nFJ9vvAWirUkZdsYNnlY+zrDQoPT7Am5jtKTHmMI1KfWNfmznyji
RltdnWfd8Bg0H7VtwrhWMWGs8QkATUAE+fC3qS144QKBgQDNFLk8eMwK6koMoNmY
vsRAf1Y6Xdd+LUN+TJqkZiUEySaKy8NLi71IBbzK7zKqbYXDPUFCbNJFhOlluKOw
bsKPkwBjR0JfoXVzbUdE+2tM2YccswaJe7iinZxr0wHGXIvJL0HNVIzmNggS7+Zm
rEsdCyFXnTT/83o1wVW3E/lspQKBgQC6gBVyYCP7AxYHTSRDCgcpsTO7HyzuY92t
aYOhRJFC7HNbzJbVdVsfnbtQH/Epe8ySk91GyFZ1dSJrxetcLhHsS2TMrkYUmY4x
bJnqzJTh7cgWBP9DuWYvSJxPooSpFwbh2L12vQ2ADpwwoAZMLkAagaGlY9MZz821
XY+KkOLnYQKBgQCQ49lTTgzqkUirz2Cst+qznsNvDSnYbWZH7xs6lygET5E5cmiS
ETIzlkoiHgjvu91LaRWYNoYAs7yqL18Godo30aXufkP4iHwQht5ZcEAI1Y7NyfYO
YCi8SxpeW3/fgzcHdqnIxbmeVAI0TuW7GHMhG+H8oob1ZjGrlOJYLHaGOQKBgDLO
vgkAxAyYFKI8k8pnqvfivJMXtSfksPmTKzb99QzkWbEClXzlkcOVNvhnG04P2fV8
ruWfol4xYQU3UB02t89F4toYCCOIicJRMcVToqPCIaZOCjSrB3mOMHdJcRaXnVpd
r4/vhQQD9u0QS2bpmrEd66mg/lujzwi/ymEXg5lBAoGAacrPblD+G/DAmTUt3tZw
GLdIvw4BeDyCvzxkJx1Z04rMZH71EEyBDPMBByZNPtjpTuzgAZE71MiD3BVLxj/H
dqEjUVQSjuOUyiJKe5GiGF25Xhe3/1VawurCdHfrv6Xmze+lRDHZuEOcV1FrM+zn
KQXlkpPbL3lU2CpgGFFKlFU=
-----END PRIVATE KEY-----
`;

  const key = RSA.parseKey(raw);
  assertEquals(key.e, 65537n);
  // ... other assertions
});

failures:

RSA - Import Private Key (PKCS8)
DataDecodeError: The string to be decoded is not correctly encoded
    at atob (deno:op_crates/web/08_text_encoding.js:106:13)
    at base64_to_binary (helper.ts:60:29)
    at rsa_import_pem_private_pkcs8 (import_key.ts:106:16)
    at rsa_import_pem (import_key.ts:160:43)
    at rsa_import_key (import_key.ts:179:37)
    at Function.importKey (mod.ts:104:23)
    at Function.parseKey (mod.ts:91:17)
    at rsa.import_key.test.ts:83:19
    at asyncOpSanitizer (deno:cli/rt/40_testing.js:36:13)
    at Object.resourceSanitizer [as fn] (deno:cli/rt/40_testing.js:70:13)

failures:

	RSA - Import Private Key (PKCS8)

So .trim() is a cleaner workaround for this issue, but it still seems specific to these keys; I tried the same changes to the RSA - Import Certificate PEM test and it still passed.

Sure. I will make parsing key more forgiving. I will work on this one after I finish optimize the RSA decryption algorithm to use Chinese Remainder Theorem. So the in meantime, you can trim on your application until the next release.

Sounds good. Trimming is a non intrusive workaround. Thanks for your attention on this, i believe this issue can be closed.


Ghidra 10.1.4 - Does not connect to defined shared ghidra server

Describe the bug
After reopening last shared project it does not connect to right server. Instead it connnects to this one always.

Even browsing repo with correct server address connects to this one instead

Also it appears that numbers in address are randomized somehow

Ghidra 10.1.4
Windows 10

The hostname that your screenshot shows is a google server's ip address.  (anything 1e100.net is google)
any-in-2415.1e100.net points to <IP_ADDRESS>.  Is that the server you were trying to connect to?  (it seems like you redacted a part of your screenshot that shows the hostname you were connecting to).
Did this work previously and just stop?  Did it work with previous version of Ghidra?  Have you tried connecting to your Ghidra server from a different workstation?
What configuration options are used in the Ghidra server's server.conf?

Seems like issue is on our end. Our domain is not pointing to correct ip address anymore.
I'll close issue since its not an ghidra issue really.


Adding config file for SDM120M

Thanks for making modpoll - it looks like a great tool!
I have been trying to configure it for a Eastron SDM120M and looked at SDM72D-M.csv as an example.
They are very similar but I couldn't get the configuration in the example file to work.
Do you know if SDM72D-M.csv has ever been tested?
Although the documentation refers to Input Register 30001. I think you actually have to read from 0 for the voltage:

This seems to be confirmed by this Python implementation:
https://github.com/nmakel/sdm_modbus/blob/master/src/sdm_modbus/sdm.py
Is it possible to specify addresses in hex? Or only decimal?

Hi @njh , thanks for your interest in modpoll tool.
I have double checked the config and vendor's document, I think the current config file is only a direct translation of vendor's register map following some kind of Modbus conventions, however the vendor obviously implements it in a different way.
I think the below updated config shall work with the meter,
device,eastron001,1,,,
poll,input_register,0,36,BE_BE,
ref,PHASE_1_LINE_TO_NEUTRAL_VOLTS,0,float32,r,V
ref,PHASE_2_LINE_TO_NEUTRAL_VOLTS,2,float32,r,V
ref,PHASE_3_LINE_TO_NEUTRAL_VOLTS,4,float32,r,V
ref,PHASE_1_CURRENT,6,float32,r,A
ref,PHASE_2_CURRENT,8,float32,r,A
ref,PHASE_3_CURRENT,10,float32,r,A
ref,PHASE_1_ACTIVE_POWER,12,float32,r,W
ref,PHASE_2_ACTIVE_POWER,14,float32,r,W
ref,PHASE_3_ACTIVE_POWER,16,float32,r,W
ref,PHASE_1_APPARENT_POWER,18,float32,r,VA
ref,PHASE_2_APPARENT_POWER,20,float32,r,VA
ref,PHASE_3_APPARENT_POWER,22,float32,r,VA
ref,PHASE_1_REACTIVE_POWER,24,float32,r,VAR
ref,PHASE_2_REACTIVE_POWER,26,float32,r,VAR
ref,PHASE_3_REACTIVE_POWER,28,float32,r,VAR
ref,PHASE_1_POWER_FACTOR,30,float32,r,
ref,PHASE_2_POWER_FACTOR,32,float32,r,
ref,PHASE_3_POWER_FACTOR,34,float32,r,

Please feel free to modify it for your actual needs.
Welcome your PR once you confirm it on your end :)
Regarding your suggestion to allow specify addresses in hex, I think it is definately a good one and will add it in the coming release. Stay tuned. Thanks.

Got it working 🙂
Poll time is pretty long (24sec) - even with baud rate increased to 9600.
I will submit a PR for this to contrib.
I will delete the things I don't actually need on my setup.
Device: SDM120M
+------------------------------------+-----------+-----------+
| Reference                          |     Value | Unit      |
+------------------------------------+-----------+-----------+
| voltage                            |     244.1 | Volts     |
| current                            |     0.054 | Amps      |
| power_active                       |       5.9 | Watts     |
| power_apparent                     |      7.54 | VA        |
| power_reactive                     |       0.0 | VAr       |
| power_factor                       |       0.7 |           |
| phase_angle                        |       0.0 | Degrees   |
| frequency                          |      50.0 | Hz        |
| import_energy_active               |   342.284 | kWh       |
| export_energy_active               |       0.0 | kWh       |
| import_energy_reactive             |     0.054 | kWh       |
| export_energy_reactive             |   132.226 | kWh       |
| total_demand_power_active          |     5.128 | Watts     |
| maximum_total_demand_power_active  |  2736.674 | Watts     |
| import_demand_power_active         |     5.128 | Watts     |
| maximum_import_demand_power_active |  2736.674 | Watts     |
| export_demand_power_active         |       0.0 | Watts     |
| maximum_export_demand_power_active |     0.033 | Watts     |
| total_demand_current               |     0.054 | Amps      |
| maximum_total_demand_current       |    11.211 | Amps      |
| total_energy_active                |   342.284 | kWh       |
| total_energy_reactive              |    132.28 | kVArh     |
| demand_time                        |       1.0 | Seconds   |
| demand_period                      |      60.0 | Seconds   |
| relay_pulse_width                  |      60.0 | Millisecs |
| network_parity_stop                |       0.0 |           |
| meter_id                           |       1.0 |           |
| baud                               |       2.0 |           |
| pulse1_output_mode                 |       4.0 |           |
| display_scroll_timing              |         0 | Seconds   |
| pulse1_divisor                     |         0 |           |
| measurement_mode                   |         2 |           |
| indicator_mode                     |       0.0 |           |
| meter_code                         |        32 |           |
| software_version                   |       516 |           |
+------------------------------------+-----------+-----------+
2024-11-05 20:47:34,564 | I | modpoll.main |  === Modpoll is polling at rate:10.0s, actual:24.136957s ===

Great to hear it's working now :)
BTW, you can optimize the poll time by adjusting --interval argument (default: 1s), which set the interval between each poll for device to response the previous query), so for example, if you are sure your device can response within 200ms, then it's safe to set --interval 0.2.

Aha! I didn't realise that. I can actually set it to --interval 0 and it works fine!
Device: SDM120M
+------------------------------------+-----------+-----------+
| Reference                          |     Value | Unit      |
+------------------------------------+-----------+-----------+
| voltage                            |     244.1 | Volts     |
| current                            |      0.19 | Amps      |
| power_active                       |       9.3 | Watts     |
| power_apparent                     |    43.114 | VA        |
| power_reactive                     |     -42.2 | VAr       |
| power_factor                       |     0.211 |           |
| phase_angle                        |       0.0 | Degrees   |
| frequency                          |      50.0 | Hz        |
| import_energy_active               |   355.601 | kWh       |
| export_energy_active               |       0.0 | kWh       |
| import_energy_reactive             |     0.057 | kWh       |
| export_energy_reactive             |   133.053 | kWh       |
| total_demand_power_active          |   541.338 | Watts     |
| maximum_total_demand_power_active  |  2736.674 | Watts     |
| import_demand_power_active         |   541.338 | Watts     |
| maximum_import_demand_power_active |  2736.674 | Watts     |
| export_demand_power_active         |       0.0 | Watts     |
| maximum_export_demand_power_active |     0.033 | Watts     |
| total_demand_current               |     2.287 | Amps      |
| maximum_total_demand_current       |    11.211 | Amps      |
| total_energy_active                |   355.601 | kWh       |
| total_energy_reactive              |    133.11 | kVArh     |
| demand_time                        |       1.0 | Seconds   |
| demand_period                      |      60.0 | Seconds   |
| relay_pulse_width                  |      60.0 | Millisecs |
| network_parity_stop                |       0.0 |           |
| meter_id                           |       1.0 |           |
| baud                               |       2.0 |           |
| pulse1_output_mode                 |       4.0 |           |
| display_scroll_timing              |         0 | Seconds   |
| pulse1_divisor                     |         0 |           |
| measurement_mode                   |         2 |           |
| indicator_mode                     |       0.0 |           |
| meter_code                         |        32 |           |
| software_version                   |       516 |           |
+------------------------------------+-----------+-----------+
2024-11-06 21:10:26,119 | I | modpoll.main |  === Modpoll is polling at rate:10.0s, actual:10.001245s ===


Text extraction performance fix.

I've been looking into text extraction algorithm and it seems the single most time consuming is following part:
prune_unwanted_nodes(one_of_the_trees, OVERALL_DISCARD_XPATH), since OVERALL_DISCARD_XPATH is very long "selector".
The same pruning process is called 4 times on (sometimes) different trees, when precision is required.
Am i wrong, but this is used in all paths of extraction (in case, where precision preference is required)?
It would be nice, to do it only once if possible.
When i tried to prune the trees only once in function
bare_extraction()
, just before line:
cleaned_tree_backup = deepcopy(cleaned_tree)
, it seems it does save almost half of execution time for precision preference extractor run.
I'm not sure, if i havent overlooked something, but i think its working still as intended.

Hi @majcl, the problem is that bulk removal of certain sections can impact recall. Maybe I missed something though, if the tests pass feel free to draft a pull request, I can then look into it.


[BUG] loading images into k3d with Skaffold takes ages (kind does it nearly instantly)

What did you do
I use Skaffold to start a Docker image in my k3d cluster.
This is the corresponding log output:

Loading images into kind cluster nodes...

eu.gcr.io/tools-org-veroo/party-service:75f7ed6465b22c5d8dd3d898e55e3a843cadde9ff051534b7442a31b4444c059 -> Loaded
eu.gcr.io/tools-org-veroo/party-service-flyway:7729370e127ad323294df235500d12326065e6c61e7a1a54713880a9393c8ef0 -> Found

Unfortunately, loading the new image into the cluster takes ages (30 seconds, 40 seconds) with k3d.
Loading it into a kind cluster is much faster. With kind it is loaded nearly instantly.
Is there a way to load an image with k3d as fast as with kind? Is there a way to speed up this process?

How was the cluster created?

k3d cluster create --switch-context

What did you do afterwards?

skaffold dev

What did you expect to happen
Fast loading of image into the cluster.
Which OS & Architecture

macOS Catalina

Which version of k3d
k3d version v3.1.5
k3s version latest (default)

Which version of docker
Client: Docker Engine - Community
 Cloud integration  0.1.18
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 16:58:31 2020
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:07:04 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.3.7
  GitCommit:        8fba4e9a7d01810a393d5d25a3621dc101981175
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Hi @ErolPeel , thanks for opening this issue!
The import time is completely dependent on the images that you use.
In the end, we're only doing docker save and ctr image import, so there's not much we can optimize here.
For me it just took <20s to import 3 images in a fresh cluster (k3d-proxy, k3d-tools and k3d-dind images).
Can you paste some timings here for a fresh k3d and a fresh kind cluster?

Actually, I just had a look into the kind code and they're doing exactly the same thing (docker save -> ctr image import).
Did you do multiple runs? For k3d, the first run may take a little longer, as we're going a little different route using an extra k3d-tools container (first time, needs to pull the image and start the container):

kind runs docker save directly on your host into some temp folder, while k3d starts a k3d-tools container and runs docker save in there, saving into a shared docker volume
kind runs opens the saved tar for every node and "streams"  the content to the node containers, exec'ing ctr image import in the node containers, while k3d runs ctr image import in the nodes, directly reading the file from the shared volume

@iwilltry42 Thank you very much for looking into this issue.
We are using k3d in our GitHub Actions Workflow, so speeding up the image loading process would save us time.
Is there a way I can help? Would logs with timestamps still be helpful?

@ErolPeel , in the GH Actions workflow, you can probably improve already, by calling the k3d image import command once and pass it all the images instead of calling it per-image (in case you're currently doing it like skaffold does).
Timestamped logs are not needed anymore, thank you!


CLI: Build error: 'BaseRequestBuilder' does not contain a constructor that takes 0 arguments

With latest source, and generating a client from https://github.com/microsoft/kiota-samples/blob/main/get-started/quickstart/posts-api.yml, the generated client class and request builder classes fail to compile.
C:\Source\Repos\kiota-samples\get-started\quickstart\cli\src\Client\PostsClient.cs(46,32): error CS1729: 'BaseRequestBuilder' does not contain a const
ructor that takes 0 arguments [C:\Source\Repos\kiota-samples\get-started\quickstart\cli\src\KiotaPostsCLI.csproj]
C:\Source\Repos\kiota-samples\get-started\quickstart\cli\src\Client\Posts\PostsRequestBuilder.cs(135,81): error CS1729: 'BaseRequestBuilder' does not
contain a constructor that takes 0 arguments [C:\Source\Repos\kiota-samples\get-started\quickstart\cli\src\KiotaPostsCLI.csproj]
C:\Source\Repos\kiota-samples\get-started\quickstart\cli\src\Client\Posts\Item\PostItemRequestBuilder.cs(158,84): error CS1729: 'BaseRequestBuilder' d
oes not contain a constructor that takes 0 arguments [C:\Source\Repos\kiota-samples\get-started\quickstart\cli\src\KiotaPostsCLI.csproj]
    0 Warning(s)
    3 Error(s)

All of these classes inherit from BaseRequestBuilder, and have constructors like:
public PostsRequestBuilder(Dictionary<string, object> pathParameters) : base() {
}

The base() is what's causing the error.
Dependency versions
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="7.0.0" />
<PackageReference Include="Microsoft.Extensions.Hosting" Version="7.0.1" />
<PackageReference Include="Microsoft.Kiota.Abstractions" Version="1.1.0" />
<PackageReference Include="Microsoft.Kiota.Cli.Commons" Version="0.1.13-preview.1" />
<PackageReference Include="Microsoft.Kiota.Http.HttpClientLibrary" Version="1.0.1" />
<PackageReference Include="Microsoft.Kiota.Serialization.Form" Version="1.0.1" />
<PackageReference Include="Microsoft.Kiota.Serialization.Json" Version="1.0.3" />
<PackageReference Include="Microsoft.Kiota.Serialization.Text" Version="1.0.1" />

@baywet , I did a little bit of bisecting and it looks like that #2406 has pretty much broken all of the IT tests with a compatible error, e.g. in Java:
cannot find symbol
[ERROR]   symbol:   class BaseRequestBuilder
[ERROR]   location: package com.microsoft.kiota

I believe this is because the references to the abstractions package are not up to date in the case of most languages. Would you mind trying to update them please?

Confirm the error is reproduced in CI:
https://github.com/microsoft/kiota/actions/runs/4552882786/jobs/8028823760#step:14:14

Go and Ruby are manifesting the same issue, should we open separate issues?

please do


MAIN B-20810

INT PR
Agility ticket
Summary
Now that we have the GSR work knocked out, we can add the implementation of seeing it in the audit log/move history.
Since we weren't tracking the evaluation reports or anything, I had to add a migration file to let the audit history table listen for changes to the gsr_appeals table.
This PR does the following:

adds migration to add gsr_appeals action to the audit_history table
updates the move_history_fetcher.sql file to pull data from the gsr_appeals table and related data needed for the history log
adds event templates for both GSR appeal actions (violations & serious incidents)

How to test

You'll need to ensure the GSR flag is on in your .envrc
Log in as a QAE and create an evaluation report with violations and a serious incident
Log in as a GSR and leave some appeals on everything - APPEAL EVERYTHING
Go in the move history tab and you should see all the crap you appealed

Screenshots

This can be merged - I will be OOO tomorrow & Monday, but feel free to merge this into main and update the build number in Agility as well as move to complete. Thanks team! @transcom/mountain-movers


[WIP] Fix: AppInstances goes to error state after coming online.

Issue: We noticed Appinstance going to error or halted state after coming online. This behaviour was sporadic and noticed mostly after we rebooted the device or the appInstance.
Reason: While checking status of an appInstance in verifyStatus(), xen-info returned empty state for the appInstance which led to one of the 12bda8cb-1424-409b-b036-0097f5e6accc tasks has crashed (info: domain e300-da-turnstile-app-sync_capacity_data.4 reported to be in unexpected state )
Fix: Added a defence in xen-info which keeps checking for the appInstance's status for 60s  in case if both "STATUS" and "/dev/status" are empty. If we couldn't find the status even after 60s, xen-info will return exit 1 with an appropriate message, instead of just returning empty STATUS.
NOTE: I noticed that even after adding the above mentioned check, I saw the same error again reported to be in unexpected state I suspected that the tee we use in the script might not be forwarding the STATUS to STDOUT. Removed the tee and explicitly writing to the file and STDOUT (echo).
Signed-off-by: adarsh-zededa<EMAIL_ADDRESS>

I don't buy the argument that tee is broken. Thus there is still some bug here.

I have reverted my changes and added back tee.
WIP because I'll run an image with the current changes (including tee in xen-info) over the weekend. If I don't see undermined status error, then I'll add a comment in this PR and remove WIP.

That is literally it. Everything and anything else needs to be handled at the domainmgr level.

+1

This is expected to be per-domU (or better yet per Task as our new terminology suggests).
As I explained with Loaders -- each loader gets a brand new Task (and container behind it created). They are based on a single template (xen-tools for now) but they all get brand new tmpfs mounted for /dev, etc. The only shared bits are shared explicitly via /run /config /persist bind-mounted into the newly created task.
IOW, when you see a task running via ctr --namespace eve-user-apps t ls you can nsetner into its namespace and see what's inside -- all the stuff in /dev is private

LGTM.


Add OOPs cheatsheet

Do assign me this issue so I can work on it.

We already have this topic included in the cpp-basic-cheatsheet. You can work on any other issues having some major changes!


Tag for Mattermost 3.2?

Am I right in thinking commit d130c09abbc7c765f5ee3e6e32999778102b6145 is the best version to use to support Mattermost 3.2.0?
Thanks!

Hi, you can use mattermost_bot==1.0.17 (ef0647b69e2c5c57eed51a21b4dda0d7c88c14e0)


Adding Kafka as a broker

Any comments are more than welcome!
While testing this, I found that there are update events where the oldobj and newobj are equal, so the data sent contains "duplicates". Do you know why?

Tks for the PR @kaboing.

While testing this, I found that there are update events where the oldobj and newobj are equal, so the data sent contains "duplicates". Do you know why?
It may be due to the Reconcile event that happens overtime even if an object is not updated. This is part of the controller runtime. The best way to test if the are really the same is by checking the "ResourceVersion" fields.


[Bug]: copy / paste (all) buggy (macOS)

Contact Details
issue
What happened?
There's mixed behavior with the copy paste functionality between cells.

In Firefox, I always get the error navigator.clipboard.readText is not a function upon paste and paste all; independent of how many cells I copy

In Safari, after copying multiple cells, both paste and paste all only past one cell

paste / paste all work fine in MS Edge and inside ARCitect

What did you expect?
No response
Host
Standalone
Host Details
macOS

Browser Safari
Browser Firefox

Swate version
v1.0.0-alpha.15

Ahh yes, firefox only supports it in a alpha version

For Safari could you pls paste the your copied cells into excel or any .txt file? This way we can find out if there is something fishy about the copy or the paste

Ugh, apparently I cannot. Can't reproduce the error in Safari. All fine now.

Copy / paste to txt or excel also works fine.


One tab for each language and all form tranlslated fields

For now each field has own locale tabs
Eg.
en es de
title
en es de
subtitle
...
Is it possible to have one language tab for all fields
en es de
title
subtitle

At this moment the bundle doesn´t offer a view for achieve that but you can overwrite the template simettric/doctrine-translatable-form-bundle/Resources/views/Form/fields.html.twig in your app directory and then implement your own UI.


CCTexture2D setTexParameters(CCTexParams) behavior

Is there any special reason why applyTexParameters is not called with this method, while it is called in setTexParameters(int, int, int, int)?

Thanks, I didn't understand why my texture didn't repeat.
But I don't have an answer at your question :p


Making use of the new string-interp library

The string-interp library is a small library that codifies the rules for placeholders in confirmations and formatted messages. We can now use it everywhere, and replace the mix of C-style format strings and inconsistent formatting.
This is both a cleanup (of some ugly code) and an enhancement, as all now confirmations have feature-parity with formatted strings (previously, no options were supported), and formatted strings have the ability to mark some parts as optional and differentiate on enums and numbers.

Pull Request Test Coverage Report for Build 767

219 of 265 (82.64%)  changed or added relevant lines in 11 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 82.132%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/i18n.js
2
3
66.67%

lib/runtime/formatter.js
23
26
88.46%

lib/ast/slots.js
17
31
54.84%

lib/describe.js
156
184
84.78%

Files with Coverage Reduction
New Missed Lines
%

lib/runtime/format_objects.js
1
92.45%

Totals

Change from base Build 760:
-0.07%

Covered Lines:
7046

Relevant Lines:
8343

💛  - Coveralls


Update snippets

Stack:

#32 ⬅
#31
#30
#29
#22

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

Please rename this PR to Update test-support/cairo-snippets.gen.ts. If you just write snippets it strongly suggests you're updating https://github.com/software-mansion/vscode-cairo/tree/main/snippets


Patched version in microsoft windows

I'm stuck with windows at work, I tried your patched branch, but without luck, Mintty refuses to see the patched fonts, there is no chance to use them or there is another way to patch them?

@lcorsini I don't know what to say, I don't use windows since '95, but I'll leave this issue open in case someone comes with an answer :smile:

I would be glad to ditch windows but I can't atm.
The problem seems to be that Mintty desn't see the font as monospaced so it doesn't show in mintty options

There are ways to trick windows into thinking it is monospaced. I haven't quite figured that out yet.

The thing is I haven't even been able to get the regular powerline patched fonts to recognize all symbols. And I haven't seen anyone who has.

I'm trying to do this too for the all new Windows Linux Subsystem.
I'll update my progress here.

In the meantime, here are some useful resources:

https://www.herebedragons.io/bashing-windows
https://www.reddit.com/r/Windows10/comments/4orqn6/setting_up_powerline_for_bash_on_windows/
http://askubuntu.com/questions/283908/how-can-i-install-and-use-powerline-plugin?newreg=c6b15c8c64e24e3fac09b8ac411b2807

The Linux subsystem should be an unmodifed ubuntu Linux userspace, so if
you install an X-server and a graphical terminal like terminator you could
use fontconfig fallback strategy
Il giorno 3 gennaio 2017 @ 11:07:24, oneezy<EMAIL_ADDRESS>ha
scritto:

I'm trying to do this too for the all new Windows Linux Subsystem.
I'll update my progress here.
In the meantime, here are some useful resources:

https://www.herebedragons.io/bashing-windows

https://www.reddit.com/r/Windows10/comments/4orqn6/setting_up_powerline_for_bash_on_windows/
http://askubuntu.com/questions/283908/how-can-i-install-and-use-powerline-plugin?newreg=c6b15c8c64e24e3fac09b8ac411b2807
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gabrielelana/awesome-terminal-fonts/issues/12#issuecomment-270082658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbq6v-BpRqoPrAFpg0DrqQPL5x4q8iDks5rOh3cgaJpZM4FJHBM
.

I installed the ConEmu Terminal and it's looking 1000x better!
Well, a LOT better then what it was. The icon fonts still aren't showing but some of the special characters are. Still messing around w/ it...
But ConEmu is amazing.

@oneezy Did you managed to install these icon fonts? With ConEmu?

Not yet @naramsim
But I'll be sure to report back here when i do

As a side note, you can use patch fonts on mintty (installed along with MSYS2).
However, it will not give you the option to choose the font in the configuration GUI as windows does not consider it to be a "monospace" font.
But, you can still choose it by manually edit the .minttyrc configuration file.
Anyway the renderring is really bad, I've openned an issue (#37) regarding that.

@oneezy So that's ConEmu using the new Linux Subsystem for Windows? That's cool - although I've heard you cannot use the arrow keys in vim while using ConEmu.

@DanielGGordon yes, that's what the screenshot is. I haven't tested the arrow keys in vim yet

@oneezy How is the speed? If you just press Enter and get the terminal back - how long does that take? When I had zsh on Babun (Windows 7), it would take 2-3 seconds sometimes. When I was doing this, I remember that Meslo was one of the only fonts that worked correctly. I'm hopefully upgrading my Windows 7 work laptop to Windows 10 today and should give this a whirl.

@DanielGGordon , I found ZSH to be pretty slow, but further investigating led me to realizing it had a lot to do with the order i wrote the settings in.
Also, I went through a LOT of trial and error to get the Windows Subsystem for Linux working to mimic my previous development workflow. You'll need to get in the Windows Insider Program (it's free) and so you can install the most recent build that allows for interopability (the current version of WSL doesn't have it).

There's a great article you should read on this topic called Bashing Windows that gives the exact approach I took (read my comments below also).
Good luck! Let me know how it turns out for you.


fixed showMetaData not reading from hugo.toml / config.toml.

Previously would always be default of true

Hi @cpeth this is intended. The idea is that you can disable metadata on page by page bases by adding showMetadata = false to post frontmatter. There is currently no option to disable it globally, however it is a good idea to have it. You could update your PR to allow for both .Site.Params and .Params so both global option and frontmatter option work. If you decide to do this, can you also please update README section about Post metadata?


Created Cloud Build Triggers for automated image building.

Script must be run manually by someone with permissions to set up for the first time. Does not need to be re-created unless it's deleted somehow.
Note: This is different from the cloud build yamls that we used to have. This is the triggers themselves. These triggers are currently maintained manually, but now are at least represented as code.

This change is

/lgtm

/lgtm
/approve

/retest

/retest

/retest

This needs a rebase to get prow fix

This needs a rebase to get prow fix

Done

Weird errors that are unrelated in cicd
/retest

The flakes.
failed to start the controlplane. retried 5 timesFailed to start testing panel
/retest

/retest

/lgtm


Disable version mismatch warning when doing tab autocompletion

The warning was always printed and was messing up the autocompletion. Now we explicitly disable the warning when doing autocompletion. There is still a chance that an out-of-sync client can fail to do the autocompletion but it's better to let it try than break completely.

I was unable to reproduce this issue but I guess I'd need to build epinio CLI from the commit just before merging this PR. Previous epinio-1.3.0 CLI doesn't contain the warning yet for the version mismatch:
⚠  Epinio server version (v1.3.0) doesn't match the client version (v1.4.0)

The autocomplete script works as expected in epinio release 1.4.0 under bash.
$ source <(epinio completion bash)
$ epinio c<TAB><TAB>
client-sync    completion     configuration


migrate and collectstatic on deploys

AWS Apprunner just builds the container and then runs it, as far as I can tell. I think this will run the migrations and staticfile collection when deploying to either staging or production, but I am not 100% sure. Hard to test locally.
before running this in staging, validate that the staticfiles & database used in staging ARE NOT the production staticfiles location or database.

this is wrong

wait I read the documentation wrong. Maybe this will work? idk


[Evernote] Tag hierarchy/structure is not imported

Hey there!
I have created an .enex file with Evernote Legacy v. 7.14.1 on my Mac.
I work exclusively with tags in Evernote and have built up a very extensive tag structure.
Unfortunately, this structure (nested tags) is lost when importing. Only the tags that are actually assigned to notes appear in Obsidian. This means that the tag headings, which are only for the overview and are not assigned to any notes, are not present in Obsidian.
Is there a workaround for this?
Thanks for your support!

Supported in Importer 1.6.0 but requires some work in Evernote to prepare for import, see documentation
https://help.obsidian.md/import/evernote


Better testbed

I feel a need for a QUnit-powered testbed improvement. QUnit alone will stay - supported by my other open source Quny it works very well indeed. What I'd especially like is to better suit it for continuous testing running on a separate machine (maybe even virtual one, small screens even) with very clear UI with strong peripheral readability with a automatic respawn capability, nicer looks.
That's what I'd like, that's what I've written in past few days and that's where just commit/push up here to Github is missing.

Some new features:

There's the already existing jq=X.Y URL param accepting valid version of jQuery. It allows the obvious - to choose particular jQuery version to test agains. There also is a UI control in the upper left corner listing supported jQuery versions.

New param respawn=X accepts time (in seconds), which must elapse since testing started for the tests to be automatically respawned. In order to prevent stuck test relays, the respawn (essentially a page reload) happens in sincere disrespect to the actual testrun results. This is perfect for continuous testing (I have it running and continuously respawning on a secondary screen during developing).
Be aware, that unlike jq this param isn't preserved after clicking a link.

Now all test run receipts without exception are handed over to the server for analysis/storage and additionally carry also the host property.

And there's the new color-ful/-coded looks. Yay! :D

This may not work out-of-the-box until properly merged into development.
Some ideas for some day:

Add respawn UI element and take care of param(s) persistence.
Report respawn-when-not-done.
Enhanced module selection (with Shift/Ctrl) including indication.


Error with "lonlatdepth_dtype=np.float64" in ParticleSet when particles are released with "delay"

Hello,
First of all, I have to thank you for developing this tool and making everything open source! I've been able to learn and fix most issues I encountered through GitHub issues and repositories linked to OceanParcels, and that has been very helpfull :)
I encountered a bug in the lonlatdepth_dtype parameter of ParticleSet.
My Fieldset is a SummedField of ROMS ocean circulation and stokes drift. Sigma depths were already converted to actual depth (m), and horizontal coordinates are on a A-grid. The field is loaded with the following function:
def get_roms(path, beaching = False, start_date=0, finish_date=-1):
    # setting vertical velocities at surface to 0
    def compute(fieldset):
        fieldset.W[0].data[:, 0, :, :] = 0.
        fieldset.W[1].data[:, 0, :, :]=fieldset.W[1].data[:, 0, :, :].clip(min=0)

    fdir=sorted(glob(path + '*.nc'))
    len_path=len(path)

    if type(start_date) == datetime:
        start_date_str=start_date.strftime("%Y%m%d")
        finish_date_str=finish_date.strftime("%Y%m%d")
        for i, e in enumerate(fdir):
            if start_date != finish_date and e.find(str(start_date_str),len_path) > 0:
                start_index = i
            elif start_date != finish_date and e.find(str(finish_date_str),len_path) > 0:
                finish_index = i
            elif start_date == finish_date and e.find(str(start_date_str),len_path) > 0:
                start_index = i
                finish_index = i

    if start_date > finish_date:
        nc_filenames = fdir[finish_index:start_index+1]
    else:
        nc_filenames = fdir[start_index:finish_index+1]

    nc_grid=pre_path+'roms_grid_Zlev.nc'

    filenames = {'U': {'lon': nc_grid, 'lat': nc_grid, 'depth': nc_grid, 'data': nc_filenames},
                 'V': {'lon': nc_grid, 'lat': nc_grid, 'depth': nc_grid, 'data': nc_filenames},
                 'W': {'lon': nc_grid, 'lat': nc_grid, 'depth': nc_grid, 'data': nc_filenames}}

    variables_roms = {'U': 'u',
                      'V': 'v',
                      'W': 'w'}

    variables_stokes = {'U': 'u_stokes',
                        'V': 'v_stokes',
                        'W': 'w_stokes'}

    dimensions = {'lon': 'longitude',
                  'lat': 'latitude',
                  'depth': 'depth',
                  'time': 'time'}

    fieldset_roms = FieldSet.from_netcdf(filenames, variables_roms, dimensions, vmax = 10, vmin=-10)
    fieldset_stokes = FieldSet.from_netcdf(filenames, variables_stokes, dimensions, vmax = 10, vmin=-10)

    fieldset_roms.W.set_scaling_factor(-1)
    fieldset_stokes.W.set_scaling_factor(-1)

    fields_W = {'W': fieldset_roms.W + fieldset_stokes.W}
    fields_U = fieldset_roms.U + fieldset_stokes.U
    fields_V = fieldset_roms.V + fieldset_stokes.V

    fieldset_final=FieldSet(fields_U, fields_V, fields_W)
    fieldset_final.compute_on_defer = compute
    return fieldset_final

My simulation releases a group of 5 particles in different locations from 12 to 12 hours. Following your suggestion of setting the ParticleSet coordinates to double precision in order to prevent uncontrolled particle beaching due to numerical rounding errors, I set lonlatdepth_dtype = np.float64:
def get_particle_set(fieldset, locs):
    class PlasticParticle(JITParticle):
        age = Variable('age', dtype=np.float64, initial=0)
        beached = Variable('beached', dtype=np.float64, initial=0)

    repeatdt = timedelta(hours=12).total_seconds()  # release from the same set of locations every day
    pset = ParticleSet(fieldset, PlasticParticle,
                   lon=locs[:, 1],
                   lat=locs[:, 0],
                   depth=locs[:, 2],
                   repeatdt = repeatdt, # this is the line where we set a release interval
                   lonlatdepth_dtype=np.float64) # double the coordinate precision to np.float64 to prevent uncontrolled particle beaching, due to numerical rounding errors
    return pset

It did manage to create and save the coordinates of the first set of particles as np.float64, but the second set of particles released 12h later were saved as np.float32. This returns the following error:
INFO: Compiled PlasticParticleAdvectionRK4_beachingBeachTestingAgeing ==> /tmp/parcels-1000/31216d591c72e6060fa8591ebe6953c2.so
 22% (39600.0 of 172800.0) |##           | Elapsed Time: 0:00:21 ETA:   0:01:59Traceback (most recent call last):

  File "<ipython-input-1-52dacf0e2935>", line 429, in <module>
    execute_run(pset, kernel, start_date, finish_date, output_file)

  File "<ipython-input-1-52dacf0e2935>", line 371, in execute_run
    output_file=output_file)

  File "/home/ccardoso/miniconda3/lib/python3.6/site-packages/parcels/particleset.py", line 416, in execute
    self.add(pset_new)

  File "/home/ccardoso/miniconda3/lib/python3.6/site-packages/parcels/particleset.py", line 258, in add
    self._particle_data = np.append(self._particle_data, particles_data)

  File "/home/ccardoso/miniconda3/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4694, in append
    return concatenate((arr, values), axis=axis)

TypeError: invalid type promotion

I believe this happens because the linear interpolation method in the Fieldset (fieldset.U.interp_method = ‘linear') sets the coordinates to np.float32 by default. In order to fix this, I added lonlatdepth_dtype=self.lonlatdepth_dtype to line 410 in particleset.py, and now it works perfectly!
Cheers,
Cláudio

Hi Cláudio,
Thanks for your interest, your kind words and of course for pointing out and solving this issue!
We'll fix it asap!
Cheers,
Philippe

We've just checked the code. This problem has actually been fixed in PR #569. (It is that one you mean, right?)
Maybe you were using conda's Parcels v2.0.0b2 and not the last master version? We'll release a newer version 2.0 very soon!

Hi Philippe,
Thank you for the replies! You are right, I'm using the V2.0.0b2 because of the issue reported in #547 ..
I see that there is a new master version in conda forge a few hours ago, I will install it!
Cheers,
Cláudio


[perl] Update to 5.33.0

Signed-off-by: Steven Marshall<EMAIL_ADDRESS>

closing in favor of #11


Set up user profile creation, renamed some files

Set up user profile creation scene that prompts the user for their username and profile pin number

Renamed some files for better readability and format

Wrote script UserTable where its methods send SQL queries and commands to the user table in DB

Wrote script WelcomeGreeting to get the current sessions user name and display it

Wrote script CreateProfile that takes in input of a username and user pin then stores it onto the DB

TO IMPLEMENT in the future: a log-in feature to make use of the create profile and user pin

Fixed conflicting files - can be merged again


New release please?

Sure. I'll do it tomorrow, so you can get rid of your pins.

I'll have to postpone it until the weekend. sorry.

No worries :D

The 1.1.0 release with your changes is now on its way: https://github.com/ocaml/opam-repository/pull/13961


#124: backport<EMAIL_ADDRESS>(closes #124)

Closes #124
Test Plan

CI should be happy

tests performed

A Test Plan is used to show what you tested to make sure your code works fine. You should write here all that you did to test, and provide some results of your testing.

These results can be screenshots, query results, or even just pointers to unit tests that successfully passed.}

tests not performed (domain coverage)

At times not everything can be tested, and writing what hasn't been tested is just as important as writing what has been tested.

An example of partial test is a field displaying 4 possible values. If 3 values are tested, with screenshots, and 1 is not, then it should be mentioned here.}

@giogonzo CI is failing

error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=4.3.0 < 5.0.0 || >= 5.10".
error Found incompatible module


avc stream t2 is supposed to be avc3 but is in fact avc1

AVC stream t2 is supposed to be "All AVC content options different from stream 1" specifically;
with and without picture timing SEI message: Without
with and without VUI timing information.: With
Sample entry, see CMAF clause <IP_ADDRESS>: avc3 sample entry type (in-band parameter sets) without parameter sets within the CMAF header
CMAF Fragment durations: 5s
Initialization Constraints: Single initialization constraints, see CMAF clause <IP_ADDRESS> and <IP_ADDRESS>
Fragments containing one or multiple moof/mdat pairs: Fragment contains multiple chunks (p-frame to p-frame with b-frames)
Resolution: 1920x1080
Frame rate (2.0=100/120,1.0=50/59.94/60, 0.5=25/29.97/30, 0.25=12.5/15): 0.5
It has been noted by @Lis-TV in HbbTV that if you do the following;
wget<EMAIL_ADDRESS>mp4box -diso<EMAIL_ADDRESS>If you then look in<EMAIL_ADDRESS>(attached), it says avc1 ...

<AVCSampleEntryBox Size="199" Type="avc1" Specification="p15" Container="stsd"  DataReferenceIndex="1" Width="1920" Height="1080" XDPI="4718592" YDPI="4718592" BitDepth="24">

mp4box output:
<SequenceParameterSet size="30" content="data:application/octet-string,6764002AACD940780227E5C05A808080A0000003002000000641E30632C0"/> <PictureParameterSet size="5" content="data:application/octet-string,68EBECB22C"/>
seems to be not in line with requirement:
Sample entry, see CMAF clause <IP_ADDRESS>: avc3 sample entry type (in-band parameter sets) without parameter sets within the CMAF header

Thanks. I can reproduce on the latest version (https://dash.akamaized.net/WAVE/vectors/avc_sets/12.5_25_50/t2/2022-01-17/croatia_L1_1920x1080@25_60_dash_track1_init.mp4), I'll have a look when processsing the next batch.

Seems t12 is also affected.

Should be solved by 32f04dd34d8f701edd7f4be068d5522e22a5cb9b.

Resolved in the latest test content, see https://github.com/cta-wave/Test-Content/issues/40#issuecomment-1310031376.
I believe this issue can be closed.

2022-11-22: Closed based on Nicholas' validation testing of 2022-10-17 test vectors release.


[gui]: missing log message cause

Issue details
https://github.com/skylot/jadx/blob/4d8a5d66713a198704af7c8b07e9e9a62fd1d713/jadx-plugins/jadx-smali-input/src/main/java/jadx/plugins/input/smali/SmaliConvert.java#L43
Is the grammar of the warning message wrong?
Is it correct to write it as below?
https://github.com/skylot/jadx/blob/4d8a5d66713a198704af7c8b07e9e9a62fd1d713/jadx-plugins/jadx-smali-input/src/main/java/jadx/plugins/input/smali/SmaliConvert.java#L40
Many messages are written in the same way as the first type, so the message is missing.
Jadx version
latest
Java version
17
OS

[ ] Windows
[X] Linux
[ ] macOS

LOG.error("Smali process error", e);

Yes, this is a correct call to log throwable with slf4j, reference from javadoc:
    /**
     * Log an exception (throwable) at the ERROR level with an
     * accompanying message.
     *
     * @param msg the message accompanying the exception
     * @param t   the exception (throwable) to log
     */
    public void error(String msg, Throwable t);

@RuffaloLavoisier if you are not sure how method works please check docs, if still unclear write a simple test code to verify it, like this:
public class Test {
	private static final Logger LOG = LoggerFactory.getLogger(Test.class);

	public static void main(String[] args) {
		try {
			throw new RuntimeException("Test");
		} catch (Exception e) {
			LOG.error("Error", e);
		}
	}
}

will output:
ERROR - Error
java.lang.RuntimeException: Test
	at Test.main(Test.java:11)

@skylot
Thanks,
The parameter was 'Throwable'. I missed it.


Revert "MWPW-147299"

Reverts adobecom/nala#368. The corresponding milo PR isn't merged yet.

@Dli3 @skumar09 corresponding PR is merged now!


Upgrade React

Likely to be able to handle the nteract component upgrades (#5), we'll need to upgrade React to 16.8.x. We may or may not have to upgrade next.js for this as well.

Adding a link to merged PR#76 from stash.
@rgbkrk, since the PR has been merged, can we close this issue?

Done deal!


Only run Travis tests for plugins either added or modified by PR

In the interest of reducing blocking test time for Brain-Score domain repositories (especially language), this moves from running all tests on Travis for every plugin on every PR to only running tests for plugins added or modified by the PR on Travis.
The gap in test coverage introduced by this PR is intended to be closed by instead having each PR initiate a non-blocking Jenkins run for all plugin and integration tests (possibly in conjunction with BSL issue #172).
Note: parse_plugin_changes.py will replace parse_changed_files.py in BSL.

let's also add marker documentation here if we end up going with those


Migrate from serde-xml-rs to quick-xml

The xml-rs crate used by serde-xml-rs seems to be
unmaintained [1, 2] and has received an active RUSTSEC advisory [3] due to unfixed parsing issues [4].
Luckily, XML usage in the crates here is minimal
and can be one-to-one migrated to the recommended
quick-xml [5]. The download stats on crates.io show that quick-xml is currently being favoured.
[1] https://github.com/netvl/xml-rs/issues/219
[2] https://github.com/RReverser/serde-xml-rs/issues/180
[3] https://rustsec.org/advisories/RUSTSEC-2022-0048
[4] https://github.com/rustsec/advisory-db/issues/1121
[5] https://crates.io/crates/quick-xml

@durch would be great to get this merged. Currently, I cannot use this crate because it pulls in the insecure xml dependency flagged by RUSTSEC! Thanks!

@dspicher, amazing, thank you, was hoping someone will contribute this

Had to fix an interesting edge case with multipart uploads, quotes were getting doubled up...

Published as 0.33-beta5

Published as 0.33.0-beta5

@durch It looks 0.33.0-beta5 on crates.io still pulls in aws-creds = "0.34" which pulls in serde-xml-rs


[Bug] Stylebot editor does not open on pcgamingwiki.com

Describe the bug
The Stylebot editor does not open on https://www.pcgamingwiki.com
Browser

Vivaldi 7.0.3495.15 (Stable channel) (64-bit)
Windows 11 23H2

To Reproduce
Steps to reproduce the behavior:

Go to https://www.pcgamingwiki.com
Click on the Stylebot extension icon
Nothing happens

Expected behavior
The Stylebot editor should display.

I'm seeing the same issue.  Works on other sites.  Click on extension icon, then "Open Stylebot".  The panel should slide in, but nothing happens.  If you click on the extension icon again, the option "Close Stylebot" is correctly shown, so it did register the initial click and thinks the panel is open.  Works fine on other sites.  Disabling uBlock has no effect.
Latest Win10 Pro
Latest Chrome - Version 131.0.6778.70 (Official Build) (64-bit)
Latest Stylebot - Version 3.1.4 (with access set to all sites)
Latest uBlock Origin Lite v2<IP_ADDRESS>1

You can manually write code for that website from Stylebot extension options

Donot open on that website instead open Stylebot extension page
here is page link
chrome-extension://oiaejidbmkiecgbjeifoejpgmdaleoha/options/index.html