[BGP Group][Direct Session] No jinja2 filter to remove subnet mask from session.local_ip_address value

Peering Manager version
v.1.6.2
Python version
3.10
Steps to Reproduce
Using the below template snippet for generating JUNOS config for bgp groups with a {{ session.local_ip_address }} defined results in an IPv6/IPv4 address including the CIDR mask. I tried {{ session | local_ips(family) }} as well with the same result.
The issue being JUNOS expects the local session ip address provided without a CIDR mask. Hence the deployment to the router fails whenever the local session ip is defined as local_ip_address/mask due to only local_ip_address being accepted.

https://peering-manager.readthedocs.io/en/stable/templating/filters/
https://peering-manager.readthedocs.io/en/stable/templating/examples/juniper-junos/

I've been through the docs multiple times. Not being able to find a documented jinja2 filter that can filter out the CIDR mask in the final output for the {{ session.local_ip_address }} value.
The session causing the issue is a multihop EBGP session, ttl = 255.
        {%- for group in bgp_groups %}
        {%- for family in (6, 4) %}
                replace: group ipv{{ family }}-{{ group.slug }} {
                    description "Group: {{ group.name | safe_string }}";
                    type external;
                    multipath;
                    advertise-inactive;
            {%- if group | iter_import_policies %}
                    import [ {{ group | iter_import_policies('slug') | join(' ') }} ];
            {%- endif %}
                    family inet{% if family == 6 %}6{% endif %} {
                        unicast;
                    }
            {%- if group | iter_export_policies %}
                    export [ {{ group | iter_export_policies('slug') | join(' ') }} ];
            {%- endif %}
            {%- for session in router | direct_sessions(family=family, group=group)  %}
            {%- if session.enabled %}
                    neighbor {{ session | ip }} {
                        description "Peering: AS{{ session.autonomous_system.asn }} - {{ session.autonomous_system.name }}{% if session.service_reference %} - Service Reference: {{ session.service_reference | safe_string }}{% endif %}";
            {%- if family == 6 and session.autonomous_system.ipv6_max_prefixes > 0 %}
                        family inet6 {
                            unicast {
                                prefix-limit {
                                    maximum {{ session.autonomous_system.ipv6_max_prefixes }};
                                }
                            }
                        }
            {%- endif %}
            {%- if family == 4 and session.autonomous_system.ipv4_max_prefixes > 0 %}
                        family inet {
                            unicast {
                                prefix-limit {
                                    maximum {{ session.autonomous_system.ipv4_max_prefixes }};
                                }
                            }
                        }
            {%- endif %}
            {%- if session | iter_import_policies or session.autonomous_system | iter_import_policies %}
                        import [ {{ session | merge_import_policies | iterate('slug') | join(' ') }} ];
            {%- endif %}
            {%- if session | iter_export_policies or session.autonomous_system | iter_export_policies %}
                        export [ {{ session | merge_export_policies | iterate('slug') | join(' ') }} ];
            {%- endif %}
            {%- if session.encrypted_password %}
                        authentication-key "{{ session.encrypted_password }}";
            {%- elif session.password %}
                        authentication-key "{{ session.password }}";
            {%- endif %}
            {%- if session.multihop_ttl > 1 and session.multihop_ttl <= 255 %}
                        multihop {
                            ttl {{ session.multihop_ttl }};
                        }
            {%- endif %}
            {%- if session.local_ip_address %}
                        local-address {{ session.local_ip_address }};
            {%- endif %}
                        peer-as {{ session.autonomous_system.asn }};
            {#- Start Passive: Check both tags for ASN and the individual BGP session #}
            {%- for tag in session.autonomous_system.tags.all() %}
            {%- if tag.slug == "passive-session" %}
                        passive;
            {%- endif %}
            {%- endfor %}
            {%- for tag in session.tags.all() %}
            {%- if tag.slug == "passive-session" %}
                        passive;
            {%- endif %}
            {%- endfor %}
            {#- End Passive #}
                    }
            {%- endif %}
            {%- endfor %}
                }
        {%- endfor %}
        {%- endfor %}
            }
        }

Remote Juniper router is running junos 18
Expected Behavior
A configuration diff (preview) statement as provided by peering manager
Observed Behavior
[{'severity': 'error', 'source': None, 'edit_path': None, 'bad_element': '2001:DB8:0:0:1D7A:CCDE:5A76:4732/128', 'message': 'invalid ip address or hostname: 2001:DB8:0:0:E6E0:7FD7:28ED:313D/128'}, {'severity': 'error', 'source': None, 'edit_path': None, 'bad_element': '<IP_ADDRESS>/32', 'message': "invalid input at '/32' in ip address '<IP_ADDRESS>/32'"}]
(real IP's substituted with dummy ones, subnet mask values not edited)

@jlixfeld Am I missing something?
Modifying the statement to
            {%- if session.local_ip_address %}
                        local-address {{ session.local_ip_address | ipaddr('address') }};
            {%- endif %}

Results in the following output when I go to the tab to see the configuration output, https:///routers//configuration/
No filter named 'ipaddr' found.

Even after installing the package,
$ /opt/peering-manager/venv/bin/python3 -m pip install ipaddr
Requirement already satisfied: netaddr in ./venv/lib/python3.10/site-packages (0.8.0)
Collecting ipaddr
  Downloading ipaddr-2.2.0.tar.gz (26 kB)
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: ipaddr
  Building wheel for ipaddr (setup.py) ... done
  Created wheel for ipaddr: filename=ipaddr-2.2.0-py3-none-any.whl size=18296 sha256=ec176473e268db11defb2a1655f557cf06b957b82a2fcf555d64c7efc457b1b2
  Stored in directory: /opt/peering-manager/.cache/pip/wheels/c2/49/2d/2e543df29f26e139e69ead8af8a4aa151513e17fd48830b3c4
Successfully built ipaddr
Installing collected packages: ipaddr
Successfully installed ipaddr-2.2.0
WARNING: There was an error checking the latest version of pip.

That I don't know.  I'm not sure if there's any nuance to giving Django some clue about an additional module.

Tried the new addition in 1.6.1 >= using JINJA2_TEMPLATE_EXTENSIONS = [ "netaddr" ] or JINJA2_TEMPLATE_EXTENSIONS = [ "ipaddr" ] just causing peering-manager to not wanting to start. :|

An example for how the JINJA2_TEMPLATE_EXTENSIONS Conf knob is properly used would be wonderful, when I find out how to use it. :sweat_smile:


[BUG] Control Plane Provider sets incorrect providerID

Rancher Server Setup

Rancher version: v2.7-head

Describe the bug

According to the upstream CAPI docs, the providerID is intended to be a cloud provider ID identifying the machine. According to the infrastructure machine docs:

This field is expected to match the value set by the KCM cloud provider in the Nodes. The Machine controller bubbles it up to the Machine CR, and it’s used to find the matching Node. Any other consumers can use the providerID as the source of truth to match both Machines and Nodes.

As such, we need to be rendering the providerID. An example from upstream can be found here: https://github.com/kubernetes-sigs/cluster-api-provider-digitalocean/blob/015bb7e7c459650348a2703d46cdafacaf00b5eb/templates/cluster-template.yaml#LL40-L42C74
To Reproduce

Provision a node driver cluster on rke2
Navigate to the downstream cluster nodes and view the yaml
Node will have the following yaml:

spec:
  providerID: <NODE_NAME>

Navigate to the local cluster and view the capi machine object for the same node
Machine will have the following yaml:

spec:
  providerID: <NODE_NAME>

Result
ProviderID is incorrect
Expected Result

ProviderID should be of the form <CLOUD_PROVIDER>://<INSTANCE_ID>
Screenshots

Additional context

This should not interfere with cloud provider integration, a similar mechanism to https://github.com/kubernetes-sigs/cluster-api-provider-digitalocean/blob/015bb7e7c459650348a2703d46cdafacaf00b5eb/templates/cluster-template.yaml#LL40-L42C74 should be used if it's not possible to render this flag for each infrastructure provider.
SURE-6263
SURE-6639

Initial testing seems to show that rendering it down as a kubelet arg is a viable option:
	providerId := entry.Machine.Spec.ProviderID
	if providerId == nil {
		return nodePlan, config, ErrWaitingf("Waiting for provider ID to be set for %s/%s", entry.Machine.Namespace, entry.Machine.Name)
	}

	providerIdFlag := fmt.Sprintf("provider-id=%s", *entry.Machine.Spec.ProviderID)
	if kubeletArg, ok := config["kubelet-arg"]; ok {
		kubeletArgSlice := kubeletArg.([]string)
		config["kubelet-arg"] = append(kubeletArgSlice, providerIdFlag)
	} else {
		config["kubelet-arg"] = []string{providerIdFlag}
	}

This also allows the corresponding node to join the cluster successfully when using the upstream CAPI infrastructure providers. Some further investigation is required to determine how this should be driven per cloud-provider, and if exposing the kubeletExtraArgs in the RKEControlPlane object similar to the upstream control plane implementation is sufficient.

I've just come across a similar issue when attempting to implement Autoscaler on v1.23.14+rke2r1. I use Terraform to spin-up tiers of nodes using AWS ASGs using the node registration command output from the rancher2_cluster_v2 resource.
The error from Autoscaler POV:
E0501 08:53:18.915503       1 static_autoscaler.go:285] Failed to get node infos for groups: wrong id: expected format aws:///<zone>/<name>, got rke2://ip-x-x-x-x.region-x.compute.internal

The machine spec indeed has the providerID as rke2://ip..., which seems to be the cause of Autoscaler grumbling because its aws provider cannot then marry-up nodes.

@samjustus , same as https://github.com/rancher/rancher/issues/41021#issuecomment-1624308419, clearing security-required.

Adding release-note label to document potential workaround once it's confirmed. @jakefhyde

@lomasger Would you be willing to share a sanitized version of your terraform configuration? Also are you using the in tree or out of tree aws cloud provider?

@lomasger Would you be willing to share a sanitized version of your terraform configuration? Also are you using the in tree or out of tree aws cloud provider?

Hi @jakefhyde, I think you'll be able to achieve a similar setup with the rancher/quickstart terraform as I did, but using ASGs for the nodes. Instead of using a cloud provider/cloud credentials in Rancher to provision a cluster, you get the ec2 nodes to self-register as custom nodes using the terraform providers, essentially launching clusters of nodes that phone home to Rancher. Specifically, the cluster resource returns the registration token needed by nodes in this configuration.


[Thermostat] Groups Cluster Missing (CON-760)

Describe the bug
Matter Device Library V1.1 mentioned that the Thermostat Endpoint required the Groups cluster. The Groups cluster is mandatory for 'Awake' device, which a lot of thermostat devices are.
However, the SDK did not include the Groups cluster in release/v1.1 for the Thermostat Endpoint.

In Window Covering Endpoint, Group is an optional cluster, but the SDK is still included.

So, could I copy the Groups cluster from the Window Covering Endpoint to the Thermostat Endpoint? like below:

Thank you for your attention.
Environment

ESP-Matter Commit Id: 548ef58b604ef1df208e4a040803a4218e213103
ESP-IDF Commit Id: cbce221e88d52665523093b2b6dd0ebe3f1243f1
SoC (eg: ESP32 or ESP32-C3): ESP32-S3
Host Machine OS: Linux

While you are waiting for a fix, you can add this cluster with one line of code in your app.
  groups::create(endpoint, &ext_config.groups, CLUSTER_FLAG_SERVER);


Question: How does this project relate to https://github.com/microsoftgraph/msgraph-sdk-python?

I just came across the set of projects under https://github.com/microsoftgraph and see what looks to be a very similar Python SDK.  Should I be using one over the other?  Are they kept in sync?
Thank you,
Clark

The Graph API is a different API than the OneDrive API. Graph provides access to many different resources that can be accessed within Microsoft, such as an Outlook inbox, in addition to OneDrive resources. Essentially, you should use Graph unless there is something supported in the OneDrive SDK that is not supported in the Graph SDK (for example, if you want to authenticate to SharePoint On Prem, which is not compatible with Graph authentication).

Are the two projects kept in sync?  My concern is that, looking at the code, issue #45 here also seems to be present in the the Graph API as well.  Do I need to open an issue there, or do changes here get made there as well?

They are generated from the same templates, so when that issue is fixed in one, it will also be fixed in the other. However, the release cadences are a bit different so the fixes may not get released quite at the same time.


Android : Deep Link navigation clearing the previous activities from the stack.

Hi Team,
Android Deep linking works with SingleTask as launch mode. But if we use this launch mode, it clears previous activities as explained in below example.
Ex: Imagine there are 3 activities A, B & C.
A ->B ->C ->Home -> A (Not showing C) - Clearing B,C activites
A ->B ->C -> Home -> C (Expected Behavior)
With SignleTask, not be able to achieve expected behavior. Other than this launch modes, Application has come up with multiple instances and other issues.
FYI: Sample example     --   http://imgbin.org/images/15515.gif
How should I work with SingleTask with preserving previous activities and is it necessary to use SingleTask with branch?
Regards,
Vijay

@vijayMmenlo  Branch  doesn't need SingleTask mode for its operation but unfortunately Android  opens a new instance of the app if you don't have SingleTask mode to your deep linking activity.
(Also you may find  others issues if you are not setting SingleTask mode, e.g. app appears like opened inside the app from which the link clicked  )
One option is to move your deep linking code  to an activity that is not filtering the deep link schemes. This way you can maintain the state of the Activity stack when launched from background.
In your case can you handle deep link in any other activity  than A?

@vijayMmenlo did the above help to solve the issue? For quicker response on integration issues can you please write to our awesome integration team integrations @branch.io


Align input field and search button

I just added a CSS rule (vertical-align: middle) to align the input and button elements that have a default display of inline-block. It seems to fix the problem :smile: (which I came across a lot online when searching on Google!)

Awesome!!


<EMAIL_ADDRESS>Cannot find module './deprecated'.

Description
After updating to 5.1.0-1 I get the following error:
/.../node_modules/typesafe-actions/dist/index.d.ts
TypeScript error in /.../node_modules/typesafe-actions/dist/index.d.ts(17,39):
Cannot find module './deprecated'.  TS2307
15 | export { isActionOf } from './is-action-of';
16 | export { Types, ActionType, StateType, TypeConstant, Action, Reducer, EmptyAction, PayloadAction, PayloadMetaAction, ActionCreator, EmptyActionCreator, PayloadActionCreator, PayloadMetaActionCreator, ActionCreatorTypeMetadata, ActionBuilder, ActionCreatorBuilder, AsyncActionCreatorBuilder, } from './type-helpers';

17 | export { default as deprecated } from './deprecated';
|                                       ^
18 |

After deleting that line manually everything seems to work after changing my code to the new API.

Just released v5.1.0 with the fix!

Still not work.
node_modules/typesafe-actions/dist/index.d.ts:17:39 - error TS2307: Cannot find module './deprecated'.


Update AWS SAM CLI to version 1.24.1

Tool information

Tool name: AWS SAM CLI
update
Desired version: 1.24.1

Area for Triage:

Virtual environments affected

[ ] Ubuntu 16.04
[x] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Bug:
The current version of SAM CLI is failing with the current error:
ModuleNotFoundError: No module named 'configparser'

The only way to solve this is with the version 1.24.1
https://github.com/aws/aws-sam-cli/issues/2927
Can this tool be installed during the build?
The tool could be upgraded during build time but as per the AWS SAM CLI doc, both upgrade command doesn't work on the pipeline.
sudo ./sam-installation/install --update

brew upgrade aws-sam-cli

Temporary solution
use Ubuntu-16.04 which is still using the version 1.23.0

@benjaminfiliatrault Ubuntu 18&20 images have been updated with aws-sam-cli 1.24.1 ob board.
I'm going to close the issue. Please feel free to contact us if you have any concerns.
Thank you!


Update operator-insights-faq.yml (Typo "Azure Open AI"→"Azure OpenAI")

https://learn.microsoft.com/en-us/azure/operator-insights/operator-insights-faq
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-insights/operator-insights-faq.yml
#PingMSFTDocs

@rcdun
Can you review the proposed changes? (See Azure OpenAI Service)
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off


urlPrefix should be called on document changes

It seems urlPrefix is never called on document changes, which prevents the prefix from being updated without refreshing the page.
Let's say I declare the input with the following code:
{
      name: 'slug_function_path',
      type: 'slug',
      inputComponent: SlugInput,
      options: {
        urlPrefix: (document) => `https://site.url/${document.lang}`,
        isUnique: isUniqueAccrossPages(slug, options),
      },
},

Updating the lang field of the document will call isUniqueAccrossPages, but not the urlPrefix function, thus won't update the value of the prefix accordingly.

Sorry for the wait, Léo!
This is being fixed the the Sanity v3 version of the plugin (^2.0.0), thank you for reporting! Keep in mind there's an upstream where input components can't access the freshest version of the document, so your prefix will always be one edit behind the document.


Larger corpus

It would be interesting to consolidate various language data repos into this one maybe, so we can use it in e.g. regression testing, as a source of words and sentences to test-shape for a font. Real-world data to use for testing.
Data sources could be the Android Open Source Project UI strings, all of Wikipedia, the Universal Declaration of Human Rights, etc.

Superseded by #48.


Improve security for ROLE_DISPO

Only support and manager related functions are "secured" using the following statements:
if (false === $this->get('security.context')->isGranted('ROLE_MANAGER')) {
throw new AccessDeniedException();
}
Extend this to all other requests using ROLE_DISPO.

This is not necessary because all routes are secured with "is_authenticated_fully". This enforces the user to be autheticated with ROLE_DISPO at least. Only roles with higher hierarchy needs to be checked explicitly. The setting can be found in app/config/security.yml

faustos: This is not necessary because all routes are secured with "is_authenticated_fully". This enforces the user to be autheticated with ROLE_DISPO at least. Only roles with higher hierarchy needs to be checked explicitly. The setting can be found in app/config/security.yml

Carmelo
Thanks. I’ve closed the issue.
Kind regards, Martin
Martin Jonasse
Seemattstrasse 38
6333 Hünenberg See
Privat:   041 780 76 12
Mobile: 079 832 69 10
Am 25.06.2016 um 09:41 schrieb faustos<EMAIL_ADDRESS>
This is not necessary because all routes are secured with "is_authenticated_fully". This enforces the user to be autheticated with ROLE_DISPO at least. Only roles with higher hierarchy needs to be checked explicitly. The setting can be found in app/config/security.yml
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


IOS Build Failed

It was working well several months ago, but now the build for ios failed with this error:
Plugins/org.chromium.sockets.tcpserver/ChromeSocketsTcpServer.m:268:60: error: use of undeclared identifier 'SOMAXCONN'
socket->_backlog = [NSNumber numberWithInteger:SOMAXCONN];
1 error generated.

After updating to iOS 10.2 my build failed with the same compile time error.
The build works fine again if you add #import <sys/socket.h> to ChromeSocketsTcpServer.m.
So I guess this import is required for the latest iOS version.


create new menu link 'WormBase AFP Webinar' with link to video

https://www.youtube.com/embed/ZONK4qe_-w8?start=86&end=1011

this looks good. I was wondering if we need to put some info on when the Webinar was held? We can talk about  this on Friday, putting on the  agenda


Rationalize quoting configs + properties

Describe the feature
Picks up from issues like #2468 and #2975, which are narrower in scope and offer more straightforward near-term fixes

Why do we call it quoting when configuring database/schema/identifier names, but then quote when describing properties of column names?
Why does each adapter have to implement its quoting character sort-of twice? (#2243)
There's also quote_columns, which is a seed-only config item that lives on its own level but surely belongs inside the quoting config item (or will it be quote?!) as columns
Not to mention quoted, which while not itself a config, returns the quoted version of a column name from a Relation based on the configs above

Instead, we should have a single config/property, and I think it should be quote. This would take over from the current project-level quoting config:
quote:
  database: true|false    # or `project` on dbt-bigquery
  schema: true|false      # or `dataset` on dbt-bigquery
  identifier: true|false
  columns: true|false

The quote: {columns: true} would also replace quote_columns as a bespoke config for seeds. If that config is specified in dbt_project.yml, it can be superseded by:

setting quote: {} inside the config() block for a specific moel
quote: true|false set for a specific column in models/*.yml (it's implied that this really means quote: {column: true}
in a post-#2401 world, a model can set its quote: {} config within models/*.yml, too

If quote is not set, it falls back to the default behavior of the adapter plugin, which also sets the character used for quoting (almost always " or `).
Questions
Here's what we have in the docs FAQs today for sources:

By default, dbt will not quote the database, schema, or identifier for the source tables that you've specified.

Should sources start respecting project-level quote settings? Or they continue to act independently, but we should enable turning this config-property on or off for all sources in dbt_project.yml:
sources:
  quote:
    schema: true

Describe alternatives you've considered
Retaining all of these configs/properties/adapter methods and documenting them exceptionally well so as to avoid confusion
Additional context
This isn't specific to any one database, though it is likely most helpful on databases that support special characters if quoted (Postgres, Redshift) or are particularly sensitive to quoting (Snowflake).
There's a round-up of all the known documentation related to quoting in https://github.com/dbt-labs/docs.getdbt.com/issues/3518.

Keep accepting the old way but don't advertise (don't break how users are currently using it)
Tricky- getting the inheritance to work
Related to the configs vs properties battle

What is the exit criteria for this issue?

A new project-level config called "quote" that matches the behavior of the current quote and quoting configs.
It can be used in config blocks to override project-level quote settings in old or new style.

What are the high-level items of the work that need to be done (i.e. create x, split out y, etc.)

Add a new config to yaml parsing.
Add a new config to the internal config logic
Make sure overrides work (we probably don't get this for free.)
Testing

What are the open questions on this issue that still need answers?

Are is there anything this would do beyond what's expressible today or is it just ergonomic? A: Just ergonomic.
would we deprecate the old way of doing these things or just let them both ride? A: Not initially.
How do we want to handle sources? (question in ticket since they seem to work independently)

Are there blockers/prerequisites to starting this work?

I think it could be started.
It's related to configs vs property work so make sure those don't overlap. neat inheritance of these configs would need to take into account that some quoting stuff is dbt configs. some quoting stuff is dbt properties.

I still care about this one :)

I really care about this one!
All I want to do is ensure that dbt quotes all column names that I reference or create (via sql selects) and my only option right now is to explicitly define every single column in every single model. I've not actually tried doing that but I suspect that will only quote OUTPUT columns in a model, not columns that I select during my sql.

And another:

https://github.com/dbt-labs/dbt-core/issues/9752

this is in adapters now, but also adding that seeds are not consistently quoted and it would be cool if they were also a config option under the proposed quote config.
dbt-labs/dbt-adapters/issues/178

See also:

https://github.com/dbt-labs/dbt-snowflake/pull/1107

as_case_sensitive is a proposed addition to the SnowflakeRelation class

https://github.com/dbt-labs/dbt-snowflake/issues/1111

Adding ~quoting related issue for snapshots. https://github.com/dbt-labs/dbt-core/issues/10356  cc: @jeremyyeo

Hello, everyone.
I have encountered the following problem, and I believe it can be resolved with some changes outlined in this issue.
About the problem
When using a case-sensitive database like Snowflake, it becomes challenging to use a mix of ASCII-only model names and non-ASCII model names.
Example:
models
└  only_ascii_char.sql
└  ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ.sql

To run the model "ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ," the identifier needs to be enclosed in double quotes. The only current option is the project-level quoting parameter, so I configure it as follows:
# dbt_project.yml
quoting:
  identifier: true

However, this causes even the only_ascii_char model to have its identifier enclosed in quotes after compilation, which means that in Snowflake, the table can only be used in lowercase:
create or replace table database.schema."only_ascii_char" ...

When attempting to avoid this by using an alias, a different issue arises:
# ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ.yml
models:
  - name: ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ
    alias: '"ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ"'

At runtime, this results in an error due to ambiguous model name detection:
Compilation Error in model ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ (models/ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ.sql)
  When searching for a relation, dbt found an approximate match. Instead of gussing
  which relation to use, dbt will move on. Please delete database.schema."ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ", or rename it to be less ambiguous.
  Searched for :  database.schema."ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ"
  Found: "database"."schema"."ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ"

For people like myself who use a non-ASCII native language, it’s important to provide models in their business language (i.e., the ubiquitous language). I would like to contribute to adding this feature! Where would be the best place to start tackling this issue?
As outlined in this linked issue, is it necessary to consolidate or organize the quote options?

Hello, everyone. (@dbeatty10 Apologies if I mentioned the wrong person.)
I have encountered the following problem, and I believe it can be resolved with some changes outlined in this issue.
About the problem
When using a case-sensitive database like Snowflake, it becomes challenging to use a mix of ASCII-only model names and non-ASCII model names.
Example:
models
└  only_ascii_char.sql
└  ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ.sql

To run the model "ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ," the identifier needs to be enclosed in double quotes. The only current option is the project-level quoting parameter, so I configure it as follows:
# dbt_project.yml
quoting:
  identifier: true

However, this causes even the only_ascii_char model to have its identifier enclosed in quotes after compilation, which means that in Snowflake, the table can only be used in lowercase:
create or replace table database.schema."only_ascii_char" ...

When attempting to avoid this by using an alias, a different issue arises:
# ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ.yml
models:
  - name: ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ
    alias: '"ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ"'

At runtime, this results in an error due to ambiguous model name detection:
Compilation Error in model ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ (models/ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ.sql)
  When searching for a relation, dbt found an approximate match. Instead of gussing
  which relation to use, dbt will move on. Please delete database.schema."ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ", or rename it to be less ambiguous.
  Searched for :  database.schema."ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ"
  Found: "database"."schema"."ｎｏｎ＿ａｓｃｉｉ＿ｃｈａｒｓ"

For people like myself who use a non-ASCII native language, it’s important to provide models in their business language (i.e., the ubiquitous language). I would like to contribute to adding this feature! Where would be the best place to start tackling this issue?
As outlined in this linked issue, is it necessary to consolidate or organize the quote options?
https://github.com/dbt-labs/docs.getdbt.com/issues/3518
(I have also heard that non-ASCII characters cannot be used in unit tests. That may also be related to this one, however, I believe this should be addressed in a separate issue, so I will create a new one for that.)

Thanks for reaching out and providing such a nice example @t0momi219 !
It sounds like your goal has two parts:

Be able to write queries in Snowflake that include double quotes for the ubiquitous language (that contains non-ASCII characters):
select * from database.target.schema."注文"

Be able to write queries in Snowflake that do not include double quotes for other models (that only contain ASCII characters):
select * from database.schema.lowercase_ascii

So you're seeking a way to configure quoting identifier: true | false on a per-model basis rather than a project-wide basis.
Does that sound correct?

Hi @dbeatty10,

you're seeking a way to configure quoting identifier: true | false on a per-model basis rather than a project-wide basis.

Exactly. Being able to override the quoting setting specified at the project level on a per-model basis would increase flexibility and be ideal.

From @jtcohen6:

IIRC - the reason why this hasn't been supported historically is that it makes operating on the relational cache very tricky, because dbt would need cache entries & lookups to be case-sensitive depending on each object’s quoting config (rather than on/off overall for all cached relation names).

@t0momi219 Thanks for you interest in working on this! This feature is tricky enough that we'd need to invest a significant amount of time and effort regardless if a community member works on it or if we do it ourselves (see below for some details). In those cases, we'd want to do it ourselves rather than accept community contributions. Unfortunately, this isn't a priority for us in the near-term, so we don't plan on tackling it anytime soon.


Optimize task sequence

Optimize task sequence when some tasks are not defined in config
Add general options in task-config to configure and speed up tasks (e.g. cleanFirst, reportSizes, ...)

This is good work, and I generally like the changes. I'm going to hold off on merging this for the moment - I think I want to incorporate these ideas at the same time I work on #352
I'll fix the missing merge-stream issue. Good catch.


MRG: BEM model and solution in Python

Closes #2190.
I translated all the code but haven't tested it at all. In fact I know it will not work. But the current plan for usage is something like this:
from mne import make_bem_model, make_bem_solution
subject = 'sample'
model = make_bem_model(subject)  # puts surfaces and conductances together
solution = make_bem_solution(model)  # does the potential computations

It seems to be working for me now, but it is horribly slow. Hopefully I can speed it up tomorrow.

You are awesome! I am so excited for this!

FYI I added a couple more files to the testing dataset. BEMs have now been created for ico-2 surfaces (320 instead of 5120 or 1280) which is much faster.
The code at this point seems to work for homog 1-layer, I just need to track down a bug in the 3-layer case. Speed isn't too much worse than C for small shells (<= 1280) and actually faster for standard size (5120) because, while calculating the matrix coefficients is slower in Python, the inversion is much faster:
ico       type    layers  time
2 (320)   C       1       0.0300931930542
2 (320)   Python  1       0.250679969788
2 (320)   C       3       0.347531795502
2 (320)   Python  3       2.41311502457
3 (1280)  C       1       0.621548891068
3 (1280)  Python  1       2.16235113144
3 (1280)  C       3       12.2742669582
3 (1280)  Python  3       21.4681899548
4 (5120)  C       1       24.4842910767
4 (5120)  Python  1       27.2853899002
4 (5120)  C       3<PHONE_NUMBER>34
4 (5120)  Python  3<PHONE_NUMBER>12

Just need to track down where that bug is, which I probably won't get to until next week.

Okay, 1- and 3-layer model and solution computation works now. Ready for review/merge from my end.

Ping @agramfort @dengemann this is ready for review

@Eric89GXL amazing! How fast is it compared to the original code?

See comment above, faster for normal use case (3-layer 5120)

There might be additional ways of optimizing it, too, if there is interest

here might be additional ways of optimizing it, too, if there is interest

I'm already very impressed. Eric what do we need here, any testing desired?

Hopefully the unit tests are sufficient to make us confident in using it. But sure, if you want to test it out and make comments, it's welcome.

But sure, if you want to test it out and make comments, it's welcome.

I will trust you if you're confident ;)

Check out the tests, hopefully those will make us confident :) If they don't, then they can be expanded.

@dengemann comments addressed. FYI you asked about speed, and that made me optimize a bit more:
2 (320)  1       C       0.283627033234
2 (320)  1       Python  0.291443109512
2 (320)  3       C       0.465950012207
2 (320)  3       Python  2.45959687233
3 (1280)  1       C       0.660896062851
3 (1280)  1       Python  1.62492084503
3 (1280)  3       C       12.4721641541
3 (1280)  3       Python  11.3650319576
4 (5120)  1       C       24.9352688789
4 (5120)  1       Python  11.2639200687
4 (5120)  3       C<PHONE_NUMBER>25
4 (5120)  3       Python<PHONE_NUMBER>1

Great!!! I will recompute all my BEMs to enjoy the speedy drive :)

On 09 Jul 2015, at 18:31, Eric Larson<EMAIL_ADDRESS>wrote:
@dengemann comments addressed. FYI you asked about speed, and that made me optimize a bit more:
2 (320)  1       C       0.283627033234
2 (320)  1       Python  0.291443109512
2 (320)  3       C       0.465950012207
2 (320)  3       Python  2.45959687233
3 (1280)  1       C       0.660896062851
3 (1280)  1       Python  1.62492084503
3 (1280)  3       C       12.4721641541
3 (1280)  3       Python  11.3650319576
4 (5120)  1       C       24.9352688789
4 (5120)  1       Python  11.2639200687
4 (5120)  3       C<PHONE_NUMBER>25
4 (5120)  3       Python<PHONE_NUMBER>1
—
Reply to this email directly or view it on GitHub.

please update what's new, rebase and +1 for merge !
thanks awesome !

Rebased and updated, I'll merge once Travis comes back happy

Sounds good

Thanks for the reviews @dengemann @agramfort

Super cool, Eric -- amazing!
On Mon, Jul 13, 2015 at 10:01 PM, Eric Larson<EMAIL_ADDRESS>wrote:

Thanks for the reviews @dengemann https://github.com/dengemann
@agramfort https://github.com/agramfort
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/2193#issuecomment-121038488
.


Custom menu action strange behaviour related to input toolbar

@jessesquires I am not sure if it's a bug or a feature. If it's a feature, then it would be nice to know how to disable it. Thanks!

see #1010


[Go live][Dec 07]

Push to live

Docs Build status updates of commit 22f1bf3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/action-commands/define-action-command.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-reference.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 22f1bf3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/action-commands/define-action-command.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-reference.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Needs new parameters added

AS of the 2002 release (maybe earlier), there are parameters for -DriverManufacturer and -DriverModel that are missing.

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

ID: 2b20651c-820b-ecff-b2fe-2be9ccdcb286
Version Independent ID: f18c03cb-e617-81cf-0d67-402e20a31ca6
Content: New-CMDriverPackage (ConfigurationManager)
Content Source: sccm-ps/ConfigurationManager/New-CMDriverPackage.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @rbreneman, literally working on that update now. Hope to have it (and many others) published in the next week or so.


Fix merge conflicts + SoundHelper + fix incorrect names / packages

inGameHud is wrong
moved Overlay to the gui package instead of the render package because it is gui related and extends DrawableHelper
Mapped SmokeRenderer, SoundHelper
Moved PlayerInventoryScreen to client package

P.S. using save as will remove duplicate mappings introduced with merge conflicts like Packet and AbstractPacket for ki, etc

Alright fixed.


[Bug]: Can't update git-versioning based crates on shuttle

What happened?
Description
I'm facing a deployment issue with Rust and Shuttle. I'm developing an Axum server that serves output from an external library that uses git-based versioning. When I run cargo update locally, it updates the git-based crates to the latest commit, which is what I want. However, when deploying using Shuttle, the commit heads of the crates seem to remain pinned to the initial deployment's commit, unless there is an actual version change in the library.
I tried using cargo shuttle clean and made sure the Cargo.lock is updated, but the issue persists. I've discussed this  in Discord and we suspect it might be a caching issue, but we're not sure how to resolve it.
Is there a way to force Shuttle to update git-based crates to the latest commit during deployment?
How can I ensure that my deployed server uses the latest version of the library with git-based versioning?
Any insights or advice on how to resolve this issue would be greatly appreciated.
Ongoing Discord Discussion: https://discord.com/channels/803236282088161321/1165786552392224799
Steps to reproduce
Here are the steps to reproduce the bug on your local system
Fork https://github.com/zenlang-rs/zen-lang
git clone https://github.com/zenlang-rs/backend.git
cd backend
# In cargo.toml file, Change the git link to a repo that you have hosted in (forking etc)
cargo build && cargo shuttle deploy

Now, go back and run these commands
git clone https://github.com/<your-username>/zen-lang.git
cd zen-lang
# make some changes in output of get_version() output and commit and push

Now, again redeploy
cd backend
cargo update
cargo shuttle run # this works as expected, chanegs are reflected here locally
cargo shuttle deploy # the output remains unchanged, as the new commit head is not reflected on server

Extra Info

Backend Repo : https://github.com/zenlang-rs/backend
Library Link: https://github.com/zenlang-rs/zen-lang

Expected Output : https://zenlang.shuttleapp.rs/api/health should have given version to be testv3 for Compiler Version (based on the one in zen-lang repo in lib)
Version
v0.29.1
Which operating system(s) are you seeing the problem on?
In deployment
Which CPU architectures are you seeing the problem on?
In deployment
Relevant log output
No response
Duplicate declaration

[X] I have searched the issues and there are none like this.

Making  cargo shuttle clean also clean the cargo cache might solve this, but the building process will soon be revamped anyways #1547.
To force cargo to re-fetch you can use the rev = "..." field to point to a specific commit.

So sorry for the late reply!

Making cargo shuttle clean also clean the cargo cache might solve this, but the building process will soon be revamped anyways https://github.com/shuttle-hq/shuttle/issues/1547.

Actually as discussed earlier on discord, cargo shuttle clean didn't fixed the issue for me. It might be for reasons as lock file won't update to latest commit with cargo shuttle clean (which is intended, not a bug).
As till now, I was able to solve that using cargo update for local checks and commit pinning as you too mentioned in for deployed one! I believe builder service might possibly fix those thing for me.
I am really excited for what the New Builder Service has to offer, will patiently wait for that! Thanks :-)

The new builder on shuttle.dev builds from scratch and uses docker layer caching with cargo-chef. This should no longer be an issue on there.


Support outbound roles in JWT outbound

JwtProvider line 376 - we should allow adding roles to the outbound both when propagating and when impersonating.

We support the groups claim in JWT on authentication, we should also support it in outbound


[SP-5866] Backport of PDI-18724 - Kitchen/Pan client does not release…

… the control when the specified "directory" does not have read/write permission. (8.3 Suite)
Original PR: pentaho-kettle#7829
@ssamora @bcostahitachivantara @pentaho-lmartins

:white_check_mark: Build finished in 31m 18s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3658, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Is it possible to make multiple tasks in one row?

I want to display tasks in one row. This functionality will be used to show let say  some deadlines are extended. I want to show it with the same title but show it like different task

any movement on this?

@rundro I came up with this issue and tried alternatives, see my demo project git@github.com:detongz/react-gantt-one-rowa.git

any movement on this?

Not yet

@detongz Kindly can you point out where to modify on this project?


IPFS CID pin orchestration through cluster into private swarm

Task Summary
📅 Due date: N/A
🎯 Success criteria: Be able to take encrypted archives and pin them across private swarm in staging.
[@YurkoWasHere to fill]
Files to store:

/mnt/integrity_store/starling/internal/{org_id}/{collection_id}/action-archive/*.encrypted (NOT *.zip)

To Do

[ ] Research ipfs-cluster and how pins are orchestrated
[ ] Implement ipfs/ipfs-cluster pinning in backend

Here are several links Storj shared in our last call that'd be helpful to go over as we investigate cross-pinning onto their storage network:

https://demo.storj-ipfs.com
https://docs.storj.io/dcs/concepts/access/
https://docs.storj.io/dcs/concepts/access/access-management-at-the-edge/

Here's the script that @YurkoWasHere  shared during the last sync:
diff --new-line-format="" --unchanged-line-format="" <(ipfs pin ls --type=recursive | cut -f1 -d' ' | ipfs cid format -b base32 -v 1 | sort | uniq) <(ipfs-cluster-ctl pin ls | cut -f1 -d' ' | ipfs cid format -b base32 -v 1 | sort | uniq) | parallel ipfs-cluster-ctl pin add --no-status {}

If I understand correctly, the script finds objects that are pinned to local storage but not in the cluster and pins them in the cluster. Could you let me know where we intend to use it? I couldn't find it myself in the repos I have access to.
If it is to make sure that everything we add to ipfs is pinned in ipfs-cluster as well then I think replacing ipfs add with ipfs-cluster-ctl addshould do the trick since the latter adds stuff to ipfs, pins it there and pins it in the cluster as well (btw, I couldn't find where we add toipfs` either so any links would be helpful - unless that's not implemented yet in which case I can try jumping on it).

If I understand correctly, the script finds objects that are pinned to local storage but not in the cluster and pins them in the cluster.

Yes, this essential syncs pins on ipfs into an ipfs-cluster. It started off as 3 lines and got turned into this crazy thing :) I was just looking at what is possible and how ipfs-cluster actaully works.

If it is to make sure that everything we add to ipfs is pinned in ipfs-cluster as well then I think replacing ipfs add with ipfs-cluster-ctl add should do the trick since the latter adds stuff to ipfs, pins it there and pins it in the cluster as well

This is my understanding as well.

(btw, I couldn't find where we add toipfs` either so any links would be helpful - unless that's not implemented yet in which case I can try jumping on it).

This function does not yet exist. Currently the only time we invoke IPFS is to generate the CID
https://github.com/starlinglab/integrity-backend/blob/59061993d980980258143e6d0548f84fc0fcddb7/starlingcaptureapi/file_util.py#L244
For example
https://github.com/starlinglab/integrity-backend/blob/dev/integritybackend/actions.py#L117
I would imagine the adding to IPFS would happen at the bottom of the action.
https://github.com/starlinglab/integrity-backend/blob/dev/integritybackend/actions.py#L161
@benhylau ^^ is there another action your thinking of pinning or this good?

It may be in Archive Action
https://github.com/starlinglab/integrity-backend/issues/67

TODO @galargh:

[ ] Check out https://demo.storj-ipfs.com/
[ ] Describe findings from publicly available storj resources

Axis to consider for the documentation:
- Geofencing
  - 1st level being US vs. EU (via IP address or KYC)
  - 2nd level being by country (via IP address or KYC)
- Whitelisting of specific storage providers
  - 1st level being that nodes have a persistent identity on the network, can be pseudonymous
  - 2nd level being we have contact information via some KYC process that we can “call a node operator” to sort issues
  - 3rd level being established orgs (like Internet Archive, etc.) are the only node operators (similar to how Lit imagines their validator network)
- Access
  - 1st level being data everywhere, encryption key is only protection
  - 2nd level being a static shared key to gate access of actual encrypted content (e.g. private ipfs swarm key)
  - 3rd level being a dynamically provisioned, ACL-based, or revokable key to gate access of content (so leak keys have remedy)
- Erasure
  - a programatic way to signal an erasure of content on the network

Sync follow-up:

Because of holiday in-between I redirected my efforts a bit. I caught up on previous Slack convos with Storj and set up a repository for hosting documentation: the repository, the documentation site hosted with GitHub Pages.

I'll move my markdowns to wiki instead 🚀  and I'll work on them there 🥳

@benhylau I think as far as IPFS goes, all we need is to decide where exactly to do ipfs-cluster-ctl add (i.e. the answer to this https://github.com/starlinglab/integrity-backend/issues/86#issuecomment-1095725292) + make sure that we init ipfs and ipfs-cluster on the machines.


MCG: Make Pipeline property non-virtual in generated SCM-based clients

This is already generated non-virtual. In the OpenAI library a custom Pipeline property is added that is virtual.

Thanks!  Do we make it virtual in Azure clients?  (Mostly just curious here, for updating my mental model)

In autorest.csharp, yes it looks like it is generated as virtual. In the Azure plugin to MGC I don't think it would be changed to virtual.


vue-language-server: 2.0.29 -> 2.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for vue-language-server is: Official Vue.js language server
meta.homepage for vue-language-server is: https://github.com/vuejs/language-tools#readme
meta.changelog for vue-language-server is: https://github.com/vuejs/language-tools/releases/tag/v2.1.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.1.2 with grep in /nix/store/zcngl2828vk15qkl4mxim49w44h4k8kk-vue-language-server-2.1.2
found 2.1.2 in filename of file in /nix/store/zcngl2828vk15qkl4mxim49w44h4k8kk-vue-language-server-2.1.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

vue-language-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zcngl2828vk15qkl4mxim49w44h4k8kk-vue-language-server-2.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A vue-language-server https://github.com/r-ryantm/nixpkgs/archive/2b7b439e9f756f6fedb75ffa69cd890b089366dd.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2b7b439e9f756f6fedb75ffa69cd890b089366dd#vue-language-server

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zcngl2828vk15qkl4mxim49w44h4k8kk-vue-language-server-2.1.2
ls -la /nix/store/zcngl2828vk15qkl4mxim49w44h4k8kk-vue-language-server-2.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

vue-language-server

Maintainer pings
cc @friedow for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Do not deprecate access to unparsed user_agent

I also made the test more explicit to ensure that everything that's deprecated actually needs to trigger a deprecation warning

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

I added some tests that the old imports show deprecation warnings too.


Consider adding more specific actions for location changes

In addition to LOCATION_CHANGE, would it be possible to add more specific identifiers for a location change, such as PATHNAME_CHANGE, QUERY_CHANGE etc?
I've made an attempt at this using a redux middleware which dispatches a custom action on detecting pathname changes. While it works, it's not reliable since things like changing the order of the actions has some undesirable side effects on the back/forward browser history. It would be better if that was offered by this module.

I don't see why you would want to do this. If your state changes depending on a particular property, then you can use a selector to only watch that section of the location descriptor.

Well in most cases when the query bit of a location descriptor changes it means the user is still on the same page (for instance on a search page), while a change in the pathname means they navigated away from that page. There are use cases for wanting to differentiate between the two cases. For instance, if you show UI errors in a "global" component you might want to clear errors relating to the page the user was on when they navigate away from that page.
In order to figure out if only the pathname was changed inside a reducer, you would need store.getState to get locationBeforeTransitions, which unless I'm mistaken, you don't.


Update qualification tool to remove DECIMAL 128 as potential problem

We now support decimal 128 and decimals are on by default (as of 22.02). The qualification tool shouldn't report them as potential problem anymore.
Tests updated to reflect this.
fixes https://github.com/NVIDIA/spark-rapids/issues/4748
Signed-off-by: Thomas Graves<EMAIL_ADDRESS>

actually there is probably doc updates I need here too.

build


[Crash] Unknown crash in Chrome.dll (AccessViolation). Provide "strippeddown" pdb file to debug crashes on XP x86 machines.

Unknown crash in Chrome.dll after starting and clicking on GUI interface with mouse.
AccessViolation at some location.
Its happened with latest v122."Hotfix2"
But earler versions -- v121, v122 -- same situation.

As I mentioned here #338, its need to provide stripped-down pdb file while linking. Or with postrprocess pdbcopy tool.
To debug crashes on XP x86 machines. (and elsewhere).
We just cant use this huge pdb file to debug. And to view Callstack at least.
But there are no reaction.
The issue described here #323 was "fixed", But some wrong way. Because now it dont creates CrashDump's at all. And creates no logs at all. :)  :)
This is CallStack from VisualStudio, where we can't see Function names, without adequate PDB  :

UPD: I have now some callstack of the crash, but for ver v.121-dbg,
for which I have created strippeded pdb, as I described here: #338
This is callstack,
And then the crash..
No linenumber info, But some better result

UPD: @win32ss, I have seen additional pdb's you have uploaded here
https://github.com/win32ss/supermium/releases/tag/v122-hf
It contains only information about object modules. And no other info, including function names. Its only 5 Mb. And useless.
Can you upload this #338 ?, as we discussed at the bottom, so I will ty.

UPD: got the SallStack using new updated PDB. Pdb is ok for now.
Callstack is near some as I got before for v121-dbg
So what about the bug ?
@win32ss, What do you think about this Call Stack of functions?

I see some garbage, called from function. at 0x0211e200 :

While the code crashes, while calling Win32 API CreateWindowExW()  ??
@win32ss, What is inside win32 here ?

I'm got more precise results:

Its a CallStack:

Its a function mixed code, where problem occured: register edi has garbage :

Its a function source code:

Its a function, which called in normal situation (OnWndProc) :

But instead called some garbage from 0x0211e200...
So "window" pointer or its fields have garbage. I can't see fields contents, because VS2010 dont show it. (Dont know about other VS versions (later), they are not compatible w/remote debug on XP)

Any idea if these failed calls came from WM_NCCREATE or not?
I wonder if the WindowUserData got overwritten with garbage after the window was created, as the WindowImpl is inherited by HWNDMessageHandler, and the pointer to that instance of WindowImpl is passed to CreateWindowExW as the lParam value, which is then set as WindowUserData on the WM_NCCREATE message. Is there anything that could be hooking the windows and potentially overwriting the WindowUserData?

The bug was found by me and fixed.


SilhouetteGenerator: See if sorting can help with performance

Also see if we can check whether the triangle is crossing existing edges or not

Yes - sorting largest -> smallest can help in the general case.


missing zsh completions

Some derivations install completions for zsh to ${out}/share/zsh/site-functions/ but there is no common place where they're linked (like default /usr/local/share/zsh/site-functions or /usr/share/zsh/site-functions).
As workaround I've added:
    zsh.interactiveShellInit = ''
      fpath=(
       ${pkgs.systemd}/share/zsh/site-functions/
       ${pkgs.mpv}/share/zsh/site-functions/
       ${pkgs.pulseaudioLight}/share/zsh/site-functions/
       $fpath
      )
    '';

Another problem is: there is no completion for man command.
nixos-version: 15.09.615.af3774a (Dingo)

man completion solved by adding systemPackages = [ ... man_db] and environment.etc."man_db.conf".text = "MANDATORY_MANPATH /run/current-system/sw/share/man";

zsh completions/site-functions enabled in  #11251 and #11271
@wedens Could you open another issue regarding the MANPATH so this one could be closed?

I guess it's useless pleading for enabling completion as default?

manpath seems to work on current NixOS unstable:
~ (master ⚡=) manpath
/home/.nix-profile/share/man:/run/current-system/sw/share/man

Closing this, please reopen if the issue still occurs.


Update fidlgen to keep current with upstream.

The Syzkaller IR upstream has been updated, so we can properly update
consts/fidl descriptions now.

The buildbot failures look real. Go 1.11?

Good call; bots look good now.

@dvyukov Anything else needed to get this merged?


Please allow selfsigned ca-certs for S3 source

I get SSL / CA-CERT errors
'SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain '

When trying to connect a non-AWS S3, the boto3-client requires its own CA certificate.
It would be best if all source connections had a custom cert path opportunity (e.g. /etc/ssl/certs/ca-certificates.crt).

Yes it is still an issue.
I used the following image (version).
acryldata/datahub-actions:v0.0.4
I also believe it could be just a few lines of code.
Only the "cafile" / "verify" parameter would have to be passed to the S3 client.

Hi @semmjon
Could you please add detail for the issue you are facing, like the recipe, DataHub version, and which container is raising the above error?

Hi,
it's been a while now, which is why i hadn't tried it again with the new version. Test case was the following:

private S3 object storage (with selfsigned certificate) (in my case Ceph, but I think it doesn't matter which S3 storage)
One of the most recent Helm charts on a K3s cluster
The error appeared when scheduling the S3 ingestion
Probably in the boto3 module in the acryldata/datahub-actions container (then v0.0.4 , but probably not fixed yet in newer)
To fix the error, a cafile would have to be given when creating the S3 client.

@shirshanka I noticed you approved the PR. However this issue happens for all the ingestion sources when we use self-signed ssl certificates in internal networks.
I think having a general param for all of the ingestions to set verify to false would solve this issue.


Adds Objects

Not placed in exact areas but still have collision bodies and can function as items that we will be able to pick up

Adding Peoples


docs: update CONTRIBUTING.md

Resolves: N/A
Description

This PR replaces the existing CONTRIBUTING.md with a new, simplified version.
Checklist

[ ] If my changes require tests, I added them.
[ ] If my changes affect backward compatibility, it has been discussed.
[x] If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

https://github.com/prismicio/prismic-client/blob/aa/docs/CONTRIBUTING.md

How to QA [^1]

Read through CONTRIBUTING.md and let me know what you think.

[^1]:
Please use these labels when submitting a review:
:question: #ask: Ask a question.
:bulb: #idea: Suggest an idea.
:warning: #issue: Strongly suggest a change.
:tada: #nice: Share a complement.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.97%. Comparing base (f141026) to head (fb57311).
Report is 2 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #340   +/-   ##
=======================================
  Coverage   99.97%   99.97%
=======================================
  Files          61       61
  Lines        6899     6911   +12
  Branches      381      381
=======================================
+ Hits         6897     6909   +12
  Misses          2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

The typos were fixed and PULL_REQUEST_TEMPLATE.md was removed in favor of the org-level version. We should be good to merge!


Make configuration consistent

Description
Some configuration options have been inconsistent in the past, this PR fixes that
Motivation and Context
Some options did not fit the pattern and I would like to make some future changes that automate some of this stuff, so having consistency will make this easier
Fixes #49
How Has This Been Tested?
It hasn't, but it's minor and shouldn't need testing
Checklist:

[x] My change requires a change to the documentation or CHANGELOG.
[x] I have updated the documentation/CHANGELOG accordingly.
[x] I have created a feature (non-master) branch for my PR.

@syscll @steakunderscore @kskewes I've fixed up all the comments on this PR now, are you all happy for me to merge?


#29 Update Badges

We still need to update the DOI badge. Adding this comment as a placeholder for the change.


Add support for Jsonnet

Hi,
First, many thanks for this priceless tool :pray:
One of the hottest in my crate ! :fire:
Now for the request, as spoiled by title, it'd be great to support Jsonnet.
This language has many "dynamic" features (variables, conditionals, etc.) that set it apart of the crowd, FTW.
Python bindings are already there so hopefully this may not be to much of a burden...
Thanks in advance
TY
J

Can you explain a use case for this? From my very light understanding of Jsonnet, IMO, jinja2-cli is an alternative to this, and I'm not sure how or why you'd use them together.
I'm down to add it as optional support, I would just like to see the use case you're thinking of.

For my use case, DevOps projects, where config data files may be consumed by several languages as well as templating engine, having just enough smartness at data level may help maintain a SSoT and stay DRY by avoiding repeating the same parsing and manipulations for each consumer.
Thanks a lot for caring
Have a beautiful day
J


#124 Github dependabot has flagged critical vulnerabilities with golang.or…

…g/x/net
and its associated packages.
This commit upgrade the affected packages.

Merging  to immediately address high severity security vulnerabilities


Upgrade @tabler/tabler-icons to version 1.97

Hey Ben,
This is my first PR to an open-source repo, so apologies in advance if I have missed anything! Thank you for your hard work on this so far!
This is just a branch from your current dev branch, which bumps the Tabler icon library to 1.97, which released earlier today. If you would rather I branched off master instead, just let me know - I'm happy to do this again if it gets the icon library updated sooner. 👍
To update the library, I just updated the package.json version for @tabler/tabler-icons, then ran your build process (as per the contributing guidelines). I then tested on a local project using npm link, as per the contributing guidelines.
I have tested icons from all of the releases that are new to tabler-icons-svelte, and everything appears to be working.
Thanks,
Sam

I realised I had selected a merge directly into Master, so have changed that to merge into the Dev branch, as I can see you have other commits on the Dev branch waiting to merge into Master.

Tabler have now released their own icon library: https://github.com/tabler/tabler-icons/tree/master/packages/icons-svelte
Closing this PR as the the additional icons are now available there.


OCPBUGS-21885: CVE-2023-39325 - Bump golang.org/x/net to v0.17.0 - 4.10

Force merging this since this image is not actually supported (Power VS was introduced as a Tech Preview in 4.13). This will ensure that it doesn't trip security scans.


Gets stuck on saving and gives no errors when picking a folder instead of a document as the inbox

Problem
This was a bit confusing at first. When I installed the extension I thought you could select a Dynalist folder and it would create a file for you with the highlights. Then I realized it had to be a document, but it wasn't very clear.
Here's the structure that I have on Dynalist right now:

Here's how I see it on the extension settings:

So it's kind of hard to distinguish which is a folder or document if they have the same name.
When you select a folder and click Save highlights, the button changes to Saving but it gets stuck there. I opened the chrome console and saw an error:

Here's the snippet from the code:
for (const highlight of highlights) {
    await dynDocument.post("/edit", {
      token: key,
      file_id: fileid,
      changes: [
        {
          action: "insert",
          parent_id: response.data.new_node_ids[0], // this is the line giving the error
          index: -1,
          content: turndown.turndown(highlight.getRange().toHtml())
        }
      ]
    });
  }

Proposed solution
Now, there are multiple solutions to this but the easiest one would be to just add a note on the settings that the inbox MUST be a document, instead of a folder. Silly mistake but I can imagine it can happen to other people.

Hello Vivian,
That's a problem that went under the radar since I never tested the use of the extension with folders.
I also see the possibility to check the response and remove folders from the selection but include the Folder name in parentheses. That way you see all the files and to which folder they belong.
The example in your case would look like this: Highlights (Highlights) 🤔

That’s a nice solution. Definitely go for it.
On Feb 14, 2020, 2:50 AM -0500, Daniel Wirtz<EMAIL_ADDRESS>wrote:

Hello Vivian,
That's a problem that went under the radar since I never tested the use of the extension with folders.
I also see the possibility to check the response and remove folders from the selection but include the Folder name in parentheses. That way you see all the files and to which folder they belong.
The example in your case would look like this: Highlights (Highlights) 🤔
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Small update here: I think I will put in the next sprint to put in multiple features. But I don't know yet when I will take some focused time for a small sprint.

Sounds good, no worries 😄 . I know we all lead busy lives and right now the extension works without issues.


Doesn't build under VS2017 when using allocate_s

fifo.hpp fails to build when using this code:
auto c(output["sum"].template allocate_s<string>());
There use of __attribute__((__unused__)) is GCC only and doesn't compile under MSVC.  I would suggest replacing all of these attributes with a macro (like RAFTLIB_UNUSED), which can be blank under MSVC.

seems to work for me, however, I have a lot of custom defines. Any chance you can create a pull request for this option? I will happily check it out and approve.
Thanks!


Create Send Assets Modal / transaction

Create the modal triggered by the button on the Treasury page that facilitates a proposal to send assets out of the Treasury.
https://www.figma.com/file/nKTAQ6bivtHMwc3O5FG47l/📚-Fractal-Design-Handoff-|-Approved-Pages-|-October-2022?node-id=2252%3A20558


ha-icon-button no longer supports icon="" in 2021.11

After updating to 2021.11 I noticed that all icons were missing from this integration.
I created an issue on the Home Assistant Frontend repository, only to find that ha-icon-button has changed behavior. This is not listed in the official update's "breaking changes" section, because using ha-icon-button is technically wrong, since it's a Home Assistant component/element, that should not be used by developers. Read more on my issue here: https://github.com/home-assistant/frontend/issues/10521

until it's fixed, you can manually edit vacuum-card.js and modify the following lines:
line 409:
replace:

with:

line 421:
replace:

with:

and the whole code from line 394 to 419:
      ><ha-icon icon="${icon}"></ha-icon></ha-icon-button>
    `;
  }
);

return html`
  <div class="toolbar">
    <ha-icon-button
      icon="hass:power"
      class="${state === 'on' ? 'active' : ''}"
      title="${localize('common.toggle_power')}"
      @click="${() => this.callService('fan.toggle')}"
    ><ha-icon icon="hass:power"></ha-icon>

You must maintain the spacing (just replace the code from the line with the new code without deleting the space before it).
Clear browser or app cache and it should work.

Thanks for reporting!


aql/go: NewQuery

Separates query building from the client. The separation of concerns is easier to understand, and it also allows queries to be created, built, validated, reused, exported, etc. without being tied to a specific client (or even needing to create one).

closes #52


generalize mutect2 wdl and json for users external to the broad

@davidbenjamin I removed hardcoded file paths in the mutect2 wdl for users outside of the Broad as suggested by @LeeTL1220 in #834. Also, the file paths in .json were replaced with with $__parameter_name__.  Lastly, I removed files that are of interest only to members of DSDE-methods (e.g. mutect2-dream-eval-sge.wdl) from this repo. They will go to the palantir repo.

Looks good!


Option to keep sign column always open

Add option to keep sign column open event when there is no signs to show.
I found this works better for me since It stops sign columns from constantly pushing text left and right.

Hmm, I'll think about it.


os: add tectonic smoke tests against nightly job

Marking WIP while I get it working on the jenkins as a test job first

good to merge from my end.


feat: project updates table

Describe your changes
Added DB schema, API endpoints, and basic table view for application project updates.
Issue ticket number and link
https://pins-ds.atlassian.net/browse/BOAS-876
Maybe also be a ticket on the FO board.
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[x] I have made corresponding changes to the documentation
[x] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

I've added fields to Project Updates that aren't used yet, but should allow for future features (e.g. setting a title to use internally, and welsh content).


Throughput counts affected by not querying liboboe

re: this discussion
liboboe should be queried on every request to make sure we get proper throughput counts:
https://github.com/appneta/ruby-traceview/blob/master/lib/oboe_metal.rb#L118

We currently don't call sampleRequest under the following conditions:

Tracing mode == through (and no AVW flag)
Tracing mode == never
Request is for a static asset (AKA do not trace list)

thanks for digging into this @pglombardo - when it comes to static assets, I believe we don't try to call liboboe or count those ... basically the liboboe counting is supposed to be for all dynamic requests.  I'm not sure that complicates this?

That makes it easier actually since we check if it's a static asset early as possible to avoid any unnecessary CPU cycles.

This has been released in gem 3.8.2.


[Clojure] - Add Clojure to the main website docs install

Currently Clojure doesn't appear as an option on the main install page of MXNet https://mxnet.incubator.apache.org/install/index.html?platform=Linux&language=Scala&processor=CPU

But the default install option should be almost exactly like Scala since it is a maven package
https://search.maven.org/search?q=clojure mxnet
The documentation to be modified is found here https://raw.githubusercontent.com/apache/incubator-mxnet/master/docs/install/index.md
To test out the results of the change and see what it looks like seehttps://github.com/apache/incubator-mxnet/tree/master/docs/build_version_doc
There is also a Dockerfile to build the website that might be useful
https://github.com/apache/incubator-mxnet/blob/master/docs/build_version_doc/Dockerfile

@gigasquid - I have submitted https://github.com/apache/incubator-mxnet/pull/13393 and in the description, I have requested readers to review MXNet Scala Setup guide as well before using Clojure dependency.

Awesome! Thank you 💯


[14.x] ISPN-15214 Do not instantiate TriangleOrderManager if not required.

https://issues.redhat.com/browse/ISPN-15214

Thanks @pruivo


[CSL-1798] Move definition of Block into cardano-sl-core

I will approve after @neongreen approves.


added support for VNC Authentication using OpenSSL

Concerning password/servername: bot are global settings and can't differ between servers or clients - at least not with the implementation provided. Then I would prefer not to copy them to every instance and use the getter of the VNC namespace, when needed. Makes the code IMHO more readable.

The implementation of encrypt_rfbdes looks like being copied from some project implemented in C. If true we need to be aware of its license.
But in the end it is not that important - I will reimplement the sequence in a in a more C++ anyway.

Did a quick check of the Qt code if we can get rid of having to deal with different OpenSSL versions. All I found is QCryptographicHash ( https://codebrowser.dev/qt5/qtbase/src/corelib/tools/qcryptographichash.cpp.html ). Might be useful for authentications available >= RFB V3.7 but not for DES en/decryption.

Concerning password/servername: I refectored the code so that the client refers to the server instead of keeping a copy of the name/passwort itself.

Concerning password/servername: I refactored the code so that the client refers to the server instead of keeping a copy of the name/password itself.

Why having the copies in the server - name/password are available from the VNC namespace. Do you have a future use case in mind, where you need different settings for different windows ( = servers ) ?

The code for encrypt_rfbdes was taken from
https://github.com/LibVNC/libvncserver/blob/master/src/common/crypto_openssl.c#L72
But thats just how the OpenSSL API works. I wrote my own implementation before, but after Update to OpenSSL v3 it failed because DES isn't supported anymore out of the box. So you have to load the "legacy" provider explicitly.

Concerning password/servername: I refactored the code so that the client refers to the server instead of keeping a copy of the name/password itself.

Why having the copies in the server - name/password are available from the VNC namespace. Do you have a future use case in mind, where you need different settings for different windows ( = servers ) ?

Do you mean that the client should reference the password/name by using the global Vnc::password()/Vnc::name() function?

The code for encrypt_rfbdes was taken from https://github.com/LibVNC/libvncserver/blob/master/src/common/crypto_openssl.c#L72

This is GPL code what is more restrictive than the BSD license of vnc-eglfs. Usually no problem as it is no library but as the code is a triviality I would prefer not to use it.
Should be easy to replace it with a C++ implementation, where a helper class is used, that does the deconstructions in its destructor - instead of using gotos.

Concerning password/servername: I refactored the code so that the client refers to the server instead of keeping a copy of the name/password itself.

Why having the copies in the server - name/password are available from the VNC namespace. Do you have a future use case in mind, where you need different settings for different windows ( = servers ) ?

Do you mean that the client should reference the password/name by using the global Vnc::password()/Vnc::name() function?

Yes exactly - or did I miss something ?

I refactored to code to use the global Vnc::password()/Vnc::name() functions.
The refactoring of the encrypt_des function is up to you.

Thanks a lot for this valuable contribution. Will merge the pull request in the next days.


Index of Terms (Glossary)

Updating and making externally availably our internal glossary could help users understand CockroachDB more easily. e.g. node, cluster, ranges

I came to create this ticket, glad to see it exists!
A specific way this could make things better for users (in addition to providing the info, ofc) is that we could perhaps build the glossary from includes to ensure that all definitions are using the best possible version in all places.
E.g., a term could have the following structure (say):

Short description, suitable for includes
Longer example with diagrams (shown only on main glossary page).  Diagrams are pretty key to understanding this stuff IMO (and we use them in a bunch of presos so I think we agree).

Working on #2282 and would find this useful for linkable definitions of range, range lease, leaseholder, etc.

Thanks for resurrecting this, @rmloveland. This sounds like a good project and approach. Is this something you'd like to take a shot at now?
You're right that we do have some basic definitions in a few places already. This is probably the closest to the beginnings of a glossary: https://www.cockroachlabs.com/docs/stable/architecture/overview.html#glossary

Is this something you'd like to take a shot at now?

Sure, my assumption is it will slot in behind the current prio items #2282 and #2729  - let me know if that works!

Let's make this a 2.1 project (that can already be started). Note that we have a large internal glossary that an external contributor made early on in the project. I don't think we want to emulate it, but it's probably good to check out.

@lhirata to link to another internal example.

This is the glossary I was thinking of: https://github.com/cockroachdb/cockroach/wiki/Jargon
Covers a lot of stuff and is good for database noobs (like myself). Not sure if all of it should be included in the new glossary though.

Officially moving this out of scope, given that we're half-way through the release cycle and will need time for other higher priority docs projects and product work.

References:

https://wiki.crdb.io/wiki/spaces/CRDB/pages/73072850/Jargon+CockroachDB+words+for+non-tech+people
https://docs.google.com/document/d/1JCU0A8ut5nF_lsB-NPkq3OpV07RPERFvwvrFeT1KhTk/edit

Glossary tooltips: https://docs.echo-security.co/mydoc_adding_tooltips.html

Using data file for tooltips: https://idratherbewriting.com/documentation-theme-jekyll/mydoc_adding_tooltips.html
Using same data file to create glossary entries: https://idratherbewriting.com/documentation-theme-jekyll/mydoc_glossary.html

Closing for now. Adding a glossary is a big project. If it becomes a priority, we'll open a new issue.


[Suggestion] Highlight the skill with most DPS

To make builds crystal clear for people who click on a D3Planner link, highlight in some way the skill which has the most important DPS among all skils.
So people can easily tell : "Ok, this is how you make damage with this build"
Examples of highlighting:

Colored border
Colored font
Colored background
Star icon at the start of the DPS line
...etc.

Or, alternative suggestion, indicate percentage of total DPS this skill is providing.
So player knows that skill A does 89% of the total DPS in this build.

I'll most likely change numbers to show as x,xxxT similar to how the game shows it (as an option). Not sure if highlighting the main skill is going to be reliable.


debug

/chat: Can Linux trace a packet and tell where the packet is dropped?

/chat: I want to trace a packet already reached the linux kernel, and show which function the packet is dropped


Fix the Firefox extension popup content not visible

With the introduction of the possibility of opening the extension as the Side Panel the Firefox from version 129.0.1 stopped to display the extension - the window pops up but it's empty or only the header is visible at the middle of the popup.

LGTM


Docs.MS Release Updates for azure-event-hubs

Update docs metadata and targeting for release of azure-event-hubs

Docs Build status updates of commit a00352c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/preview/event-hubs-readme.md
:warning:Warning
View (azure-node-preview)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/preview/event-hubs-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


feat(KONFLUX-1503): Set some requests and limits so pods can spread across cluster nodes

IMO this needs to happen before https://github.com/redhat-appstudio/infra-deployments/pull/4249
Some support for these values: https://docs.google.com/document/d/1SvR7AP1UCU67bV0UvYhn6b8U30LCoPu9zcD5Wd1uAxk/edit?pli=1#heading=h.7kx4nf5n5g

Fixed a typo found by PR checks

please add resource request only to the task and not steps for sake of all us :)

Hello @rcerven . For sake of me, please could you give more info on why? I assume you meant this functionality: https://tekton.dev/docs/pipelines/compute-resources/#task-level-compute-resources-configuration but it is marked as Beta, so not sure if it is OK to use it. I think it is better to use more granular settings. You are concerned about maintainability of these settings?
If I read the docs for Task-level resources feature correctly:

If users specify a Task-level resource limit, no Step may use more than that amount of resources.

all the containers will run with whatever I configure on Task-level, so if I would use 1/2Gi requests (as that is biggest one used for build step), it will run all the containers with that, these 9 build pod containers would account for 9/18Gi requests that might be a significant hit for cluster resources (at least compared to what we have now). With limits, we would run out of node size.
I'm happy to do so as it will just mean more compute plane nodes created by node autoscaler and better distribution of tasks, but I thought what I propose is already big change. Also I would like to be sure it is a general consensus before doing these changes.

FYI rebased.


Code to convert cw20 to bank denom and vice versa

Cw20 ↔ Bank denom conversion
This PR extends Cw20 base contract with functionality to convert Cw20 tokens into Bank denom  and vice versa.
Advantages

Cw20 tokens can be used as native tokens on the cosmos chain.
Cw20 tokens can be transferred through IBC to other cosmos chains.
Cw20 tokens  can be transferred to Ethereum if the bridge from Cosmos to Ethereum exists. etc

Implementation
To achieve this, the CW20-base contract should be extended with two new functions

[x]  bank_to_cw20

User can invoke this function to convert bank denom to cw20 tokens. Upon invocation,

the CW20 contract should verify the user bank balance.
transfer the bank denom to CW20 contract address from user balance.
Mint equal amount of CW20 tokens for user address.

[ ]   cw20_to_bank

User can invoke this function to convert cw20 tokens to bank denom. Upon invocation,

the CW20 contract should verify the user cw20 balance.
Burn cw20 tokens of the user
transfer equal amount of bank denom to user from CW20 contract address.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing due to inactivity and lack of relevance to the cw20 specification.
The cw20-base contract is meant to demonstrate how to implement the cw20 specification only.


fix: Fix Duplicate InstanceID Batching Bug

Fixes #
Description
Fixes a bug where passing the same instance ID in two separate calls in the same batch would result in an empty output which would throw off the callers to the EC2 API and result in panics. This occurred because we were only looking at the last index that represented an instance ID rather than looking at ALL the indexes that request that instance ID
How was this change tested?

make presubmit

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

Release Note

None

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

All tests pass
:white_check_mark: utilization-pr-3717-gvqnt tests passed
:white_check_mark: ipv6-pr-3717-l7mcc tests passed
:white_check_mark: drift-pr-3717-6xnlb tests passed
:white_check_mark: interruption-pr-3717-54sxb tests passed
:white_check_mark: chaos-pr-3717-lznsj tests passed
:white_check_mark: consolidation-pr-3717-vrccv tests passed
:white_check_mark: integration-pr-3717-5z6qm tests passed
:white_check_mark: upgrade-pr-3717-lzm2w tests passed


Streamline docker image build/distribution

Motivation for changes:
Reduce build time and distribution size for updates to docker image. #3748
Alternate implementation to #3749
Detailed changes:

Split release requirements from dev requirements to make sure nothing extra is pulled in docker image
Optimize layers of docker images such that dep and webui layers don't need to be rebuilt/distributed when deps haven't changed
Add a cache to github actions so that reused docker layers don't need to be rebuilt.  Hopefully a lot, because with the cross-arch building that step takes a full hour to do without caching.

Addressed issues/feature requests:

Fixes #3748

To Do:

[ ] Figure out if this actually does what I think it does and makes things better

Okay, latest changes eliminate the need for cryptography (which required rust and to be compiled on many platforms) and has reduced the full build time down from an hour to about 17 minutes. With the layer cache now being stored in github actions, full build should be rare, and normal builds much shorter.


Updated pocketcast to 1.2.2

Thank you for the contribution. It was merged directly as 9a0b51a1272e93a7eb8b32a84be1921a449e1957 to keep commit history cleaner. Your contribution is still credited to you.


The code on this page is broken.

There are problems with the DomainMapper being recognized in .NET 4.5 in Visual Studio 2017. The code, as it stands, has problems once the DomainMapper object is mentioned. The first try block is entirely non-functional as is.

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

ID: 202e3f9f-a12a-53de-9069-fd469e3dbebc
Version Independent ID: fd3699bb-4881-b6b4-1275-43eed3d5f626
Content: How to verify that strings are in valid email format
Content Source: docs/standard/base-types/how-to-verify-that-strings-are-in-valid-email-format.md
Product: dotnet-fundamentals
GitHub Login: @adegeo
Microsoft Alias: adegeo

Hi @im-a-lebowski,
The code is not broken. It is a C# 7 feature, and since you're using .NET 4.5 - it should work. Since you're using Visual Studio 2017, you'll need to add <LangVersion>7.3</LangVersion>.
See:

https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/configure-language-version#defaults
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/local-functions


Resend now function doesn't work on canceled upload file

To reproduce:

Take a picture in a room
Cancel the upload: photo upload is cancel.
Take another photo and upload it

The second upload works, but "Messages not sent. Resend now" appears. Nothing happens when I hit Resend now.
If you kill and restart the application, there will be an empty red frame corresponding to the first upload. The resend now function won't work.
To get rid of this msg, you have to delete the canceled upload file.

fixed, wait for validation

Validated.


Dockerfile that build smaller image

Love your application, I have written a Dockerfile that optimizes the storage using node-prune and also multi stage to keep only the necessary file within docker.
Also... the node 18.14.1 version will have npm install error so I will revert back to node 14 for the time being.

This is the part of the error I see when using node 14 via (docker logs ), no idea whether higher node version will fix it.
src/Pages/ForgotPassword.jsx
  Line 4:8:    'Cookies' is defined but never used  no-unused-vars
  Line 74:20:  Expected '===' and instead saw '=='  eqeqeq
  Line 94:20:  Expected '===' and instead saw '=='  eqeqeq

src/Pages/Login.jsx
  Line 5:26:  'toast' is defined but never used  no-unused-vars

src/Pages/Popular.jsx
  Line 2:10:  'Helmet' is defined but never used  no-unused-vars

src/Pages/Profile.jsx
  Line 7:26:    'toast' is defined but never used
                                                                                no-unused-vars
  Line 19:10:   'userImg' is assigned a value but never used
                                                                                no-unused-vars
  Line 20:10:   'comp' is assigned a value but never used
                                                                                no-unused-vars
  Line 20:16:   'setComp' is assigned a value but never used
                                                                                no-unused-vars
  Line 35:3:    React Hook useEffect contains a call to 'setUserId'. Without a list of dependencies, this can lead to an infinite chain of updates. To fix this, pass [navigate] as a second argument to the useEffect Hook  react-hooks/exhaustive-deps
  Line 47:6:    React Hook useEffect has a missing dependency: 'getDetails'. Either include it or remove the dependency array                                                                                react-hooks/exhaustive-deps
  Line 97:24:   Expected '!==' and instead saw '!='
                                                                                eqeqeq
  Line 167:17:  Redundant alt attribute. Screen-readers already announce `img` tags as an image. You don’t need to use the words `image`, `photo,` or `picture` (or any specified custom words) in the alt prop              jsx-a11y/img-redundant-alt

src/Pages/Register.jsx
  Line 77:21:  Expected '===' and instead saw '=='  eqeqeq
  Line 97:21:  Expected '===' and instead saw '=='  eqeqeq

src/Pages/Stream.jsx
  Line 89:24:   Expected '===' and instead saw '=='
                                                            eqeqeq
  Line 133:6:   React Hook useEffect has a missing dependency: 'addHistory'. Either include it or remove the dependency array                                                  react-hooks/exhaustive-deps
  Line 143:6:   React Hook useEffect has missing dependencies: 'addHistory', 'getComments', 'getDetails', and 'getStream'. Either include them or remove the dependency array  react-hooks/exhaustive-deps
  Line 226:25:  Expected '!==' and instead saw '!='
                                                            eqeqeq
  Line 249:59:  Expected '===' and instead saw '=='
                                                            eqeqeq
  Line 335:46:  Expected '===' and instead saw '=='
                                                            eqeqeq

src/Pages/genre.jsx
  Line 24:6:  React Hook useEffect has a missing dependency: 'fetchData'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
  Line 28:6:  React Hook useEffect has a missing dependency: 'fetchData'. Either include it or remove the dependency array  react-hooks/exhaustive-deps

webpack compiled with 1 warning

Thanks for generating an optimised version of docker file, seems like the warnings are caused because of the unused code left in some files i will try to patch it up asap


In Step 2, add Project Coordinator and Principal Investigator

Changes
In Step 2, add “Project Coordinator and Principal Investigator”.  If a Principal Investigator is selected, it should be populated in the “PI” field in the first table for the FWF template. If a Principal Investigator or Project Coordinator is selected, it should be populated in the “Project coordinator, Principal Investigator” field under the Project details table for the SE template.  Where should it go in the HE template?
Screenshot

Sub issue of #260