[FEATURE] Support Cross Cluster Search in SQL/PPL

Is your feature request related to a problem?
Currently, SQL/PPL does not support cross cluster search (CCS) because CCS does not support fetch index mapping from remote cluster
What solution would you like?
Support CCS in SQL/PPL

Yes, I would like to have this feature to get the CCS capability with my old SQL queries.

1 Introduction
We will allow any node in an opensearch cluster to execute search requests against other opensearch clusters using PPL and SQL.
2 Background
2.1 Cross Cluster Search (CCS) in OpenSearch
OpenSearch supports cross cluster search using the following syntax:
# Search index_1 on remote cluster cluster_1
GET cluster_1:index_1/_search

# Search index_1 on both the local cluster and remote cluster cluster_1
GET index_1,cluster_1:index_1/_search

# Search index_1 on both the remote clusters cluster_1 and cluster_2
GET cluster_1:index_1,cluster_2:index_1/_search

# Search index that matches the name pattern on remote cluster cluster_1
GET cluster_1:index_*/_search

# Search all indices on all remote clusters; local cluster NOT included
GET *:*/_search

2.2 SQL Search
SQL syntax for querying multiple indices isn’t using the comma syntax. We can use the UNION keyword.
-- This is NOT supported
SELECT * FROM index_1,index_2

-- This is supported
SELECT * FROM index_1
UNION
SELECT * FROM index_2

Using the asterisk character (*), we can still query multiple indices that match the expression. However, we do not support searching only using an asterisk.
-- This is supported
SELECT * FROM index_*

-- This is NOT supported
SELECT * FROM *

2.3 PPL Search
Both asterisk in index names and comma-separated multi-index search are supported. However, we do not wupport searching only using an asterisk.
# These are supported
search source=index_*
search source=index_1,index_2

# This is NOT supported
search source=*

3 User Interface (RFC)
3.1 Query Option 1: Colon syntax
This option uses the same identifier syntax as that of CCS in OpenSearch.
3.1.1 Identifiers
Identifiers should match one of the following syntax:

<index-identifier> for local cluster query
<cluster-identifier>:<index-identifier> for remote cluster query

Both <index-identifier> and <cluster-identifier> can contain asterisks (*) for pattern matching.
3.1.2 Examples
PPL
search source=cluster_1:index_1
search source=index_1,cluster_1:index_1,cluster_2:index_1

SQL
SELECT * FROM cluster_1:index_1
SELECT * FROM index_1 UNION SELECT * FROM cluster_1:index_1

3.1.3 Pros and Cons
Pros

Match the user experience with OpenSearch query, which also uses the <cluster>:<index> syntax
No ambiguity in resolving names, as index identifiers must not contain colons (:)
Could forward resolving logic of cluster name expression to OpenSearch, as it’s a syntax that OpenSearch recognizes

Cons

RFC

3.2 Query Option 2: Dot syntax
This option provides the same user experience with federated query engine with datasources. In short, with datasources, users can provide the name and connector for an external datasource, and use the following PPL search to refer an entity from the datasource as a table:
# the entity as a table is provided by the abstraction designed by the connector
search source=<datasource-name>.<entity> | <piped-commands>

The goal of this option is to encapsulate cross clusters as datasources using the same notion.
3.2.1 Identifiers
Identifiers should match one of the following syntax:

<index-identifier> for local cluster query
<cluster-identifier>.<index-identifier> for remote cluster query

Both <index-identifier> and <cluster-identifier> can contain asterisks (*) for pattern matching.
3.2.2 Examples
PPL
search source=cluster_1.index_1
search source=index_1,cluster_1.index_1,cluster_2.index_1

SQL
SELECT * FROM cluster_1.index_1
SELECT * FROM index_1 UNION SELECT * FROM cluster_1.index_1

3.2.3 Pros and Cons
Pros

Provide a unified query user experience with datasources

Cons

Ambiguity in resolving name expressions, as index identifiers could contain dots (.)
No support for multi-indices syntax in PPL

search source=index_1,cluster_1.index_1 this syntax isn’t a normal use case for federated query

Need extra work for cluster name expression matching when it contains asterisks (*), as this also diverges from the federated query use case

3.3 Pure wildcard matching (RFC)
Do we want to support this: search source=*:* (only an asterisk for identifier expression)?
Or is search source=c*:i* (asterisk + any other character) good enough?
3.4 Response formats
Response formats are exactly the same as a regular local cluster search. They are described here: https://opensearch.org/docs/latest/search-plugins/sql/response-formats/
4 Limitations (RFC)
We impose the following limitations for PPL/SQL cross cluster search:

All indices in a query should have the same index mappings (schemas)
The index mappings (schemas) should be present on the local cluster

The concrete rules are subject to change, but the idea is that we should be able to find the mapping locally for at least one index:
# Use index mapping of index_1 at local cluster
search source=cluster_1:index_1

# Use index mapping of index_1 at local cluster
search source=index_1,cluster_1:index_1

# Use index mapping of index_1 at local cluster
# Both indices are assumed to have the same index mapping
search source=cluster_2:index_2,index_1

# Use index mapping of index_1 or index_2 at local cluster
# Both indices are assumed to have the same index mapping
search source=cluster_1:index_1,cluster_2:index_2

Reasoning
We impose these limitations because currently, OpenSearch does not support cross cluster query for index mapping, which the jdbc response format requires.
The most common use case for this CCS feature is to search for data across multiple cluster shards. Within a single search query, it’s reasonable to assume that the schema is the same across all indices, so that the query response makes sense, and it’s easier for post-processing.
If either of the limitation is violated, we might either

attempt to union the index mappings of multiple indices. This is our current approach for local cluster search when multiple indices are queried. When there is conflict in a field, we pick one arbitrarily.
throw an error

Caveat
One thing to note is that if the user wants to search only a single index on a single remote cluster, and that the same index name doesn’t also exist on the local cluster, we do not allow such search. A workaround for this is that the user create a mapping table for that index on the local cluster. It does not need to be an index that stores data. It contains only the schema. This way, we could search the data on the remote cluster, and combine it with the schema stored at the local cluster, to make a query response.
Remove Limitation
We could remove such restrictions once cross cluster index mapping query is supported in OpenSearch core.

Remote cluster shouldn't be data sources. Today's concepts of cross cluster exists independent of data sources

I would prioritize PPL work over sql. It's would be always good to have both/ but we have many users asking for ppl soon.

Tasks

[ ] Development

[ ] modify grammar for ppl
[ ] search field mapping at local cluster

[ ] Testing

[ ] unit test (full coverage)
[ ] integration test (need cross cluster setup)
[ ] piped commands should work with ccs
[ ] security plugin and cross cluster credentials

[ ] Communication to customer about feature, and more importantly, the restriction

[ ] build a dev version to share with customer
[ ] documentation in project
[ ] documentation on OpenSearch website


git clone

cd 007-TheBond
python -m venv venv
source venv/bin/activate

what are you trying to say?

I don't understand this is

after cloning the  file go to the cloned directory, and use this command
bash setup.sh
then
cd src
after that
python3 007.py

Ooo
I don't understand
Can you me explain in more detail.
Where exactly should I go? Where to press?
I'm from Russia.
 You understand me?

yep . after setup.sh
cd src
python3 007-thebond.py

What program to work in?

python


Set observedGeneration under condition Ready

Is your feature request related to a problem? Please describe.
Currently, observedGeneration is only set in status level for al resource. It would be helpful to set observedGeneration under conditions as well. To reliably rely on kubectl wait command for ready condition to be met.
If the previous condition was ready for HR resource then, sometime kubectl wait will confirm to soon as condition met based on previous Ready condition.
Describe the solution you'd like
observedGeneration should be set under condition.
Describe alternatives you've considered
We have are sleeping for 30 secs hoping the status will be updated in the mean time.

Has been implemented by PR #226


Research docs impact of geo-spatial

AT: https://airtable.com/tblD3oZPLJgGhCmch/viwJAeQYJPyTNLctb/recMNcrvFLgiUiX62?blocks=hide
Initial GH issues:

https://github.com/cockroachdb/cockroach/issues/19313
https://github.com/cockroachdb/cockroach/issues/21286

Planning/research docs:

https://docs.google.com/document/d/1s20-udCs4pftaAOiPXqHr3pao9U7M-Pr4coMk6Qddr0/edit?ts=5dcc4d1b#heading=h.km6dbq8se2y2
https://docs.google.com/document/d/1CCb5jabCG2iFZELBSV56mNECKsKl2_aPX8zQ49Ume5c/edit?ts=5d8d03aa#heading=h.3s6s8g4cnifq

PostGIS docs: https://postgis.net/docs/
Questions:

What reference docs do we need? (e.g., SQL statements, data types, new index type, etc.)
What developer guidance do we need? (e.g., loading geo-spatial, querying geo-spatial , troubleshooting, etc.)
What third-party tools do we want to call out or document?
What end-to-end tutorials would be helpful?

Calling this one done now that we have a plan for spatial docs for 20.2 which is available to view as a prioritized list of Spatial Docs issues.


Response objects are not immutable in miniflare

Response objects are not immutable in miniflare, headers can be set while an opaque error will be generated in production deployments.
Replication
Run this repo in miniflare
https://github.com/Immortalin/vite-plugin-ssr-cloudflare-pages-demo
There is no error in development, however, in production the worker will return the usual 1101 exception.
Commenting out the headers code here solves the problem.

Dupe of #242


Manipulate string before copy?

hiya! I am using your script to copy table rows using  data-clipboard-target="#export"
It's great because I can paste the copied results into a spreadsheet.  The problem for me is: I need to trim the leading whitespace before copying i.e..
copiedstring.replace(/^\s/, '')
Can you point me to where I could do that?

Sure, see: https://github.com/zenorocha/clipboard.js#advanced-options


Take picture options

Added logic so that we can send some basic options to the takePicture call.
const options = { width: 1200, height: 1200, quality: 0.8 };
this.refs.camera.takePicture(options).then(
        uri => {
          console.log(uri);
        },
        error => {
          console.error(error);
        }
      );

I am not able to run PR at the moment, but it looks OK to me. Merging.

Here is an example how to use it
https://github.com/RobertSasak/react-native-openalpr/blob/master/example/App.js


Security Contact role

[Enter feedback here]
Are there plans to add a custom role as well as the Owner on the email notifications options? "If a security issue requires direct action taken by subscription admins/owners, or critical and sensitive resource information needs to be shared, we send an email notification to subscription admins/owners."
Currently, setting a custom role via API fails.

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

ID: 4790207d-b57b-cb24-14fb-c8599b705512
Version Independent ID: b5e8146d-0b66-8b4f-27f8-a5afa5e55ca0
Content: Stay informed about Azure security issues - Azure Service Health
Content Source: articles/service-health/stay-informed-security.md
Service: service-health
GitHub Login: @rboucher
Microsoft Alias: robb

@pthomas848
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for your dedication to our documentation. This issue has been moved to an internal work item for triage and prioritization. Thanks in advance for your understanding as we investigate to provide the most accurate documentation updates. #please-close
Internal work item: https://dev.azure.com/msft-skilling/Content/_workitems/edit/271098
Please also note that GitHub documentation issues are being phased out completely. For more information, see: https://aka.ms/ContentUserFeedback.
Our support team is available to assist you if you have any pressing questions or problems that need to be resolved. You can create a support ticket by visiting the following link: https://azure.microsoft.com/support/create-ticket/
You may also ask support questions in our Q&A forums.


[e2e]: go tag branch1 config-ldflags-assets slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.719
Run: https://github.com/slsa-framework/example-package/actions/runs/12327831530
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.719
Date: Sat Dec 14 07:07:17 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.720
Run: https://github.com/slsa-framework/example-package/actions/runs/12336724711
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.720
Date: Sun Dec 15 07:07:05 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.721
Run: https://github.com/slsa-framework/example-package/actions/runs/12347588054
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.721
Date: Mon Dec 16 07:08:23 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.722
Run: https://github.com/slsa-framework/example-package/actions/runs/12368017706
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.722
Date: Tue Dec 17 07:08:00 UTC 2024

related: https://github.com/softprops/action-gh-release/issues/556

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.723
Run: https://github.com/slsa-framework/example-package/actions/runs/12388012803
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.723
Date: Wed Dec 18 07:08:08 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.724
Run: https://github.com/slsa-framework/example-package/actions/runs/12407886039
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.724
Date: Thu Dec 19 07:08:15 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.725
Run: https://github.com/slsa-framework/example-package/actions/runs/12427081339
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.725
Date: Fri Dec 20 07:07:47 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.726
Run: https://github.com/slsa-framework/example-package/actions/runs/12443153249
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.726
Date: Sat Dec 21 07:07:31 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.727
Run: https://github.com/slsa-framework/example-package/actions/runs/12452145991
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.727
Date: Sun Dec 22 07:07:47 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v15.0.728
Run: https://github.com/slsa-framework/example-package/actions/runs/12462752604
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.branch1.config-ldflags-assets.slsa3.yml
Trigger: push
Branch: v15.0.728
Date: Mon Dec 23 07:07:31 UTC 2024


Clear command and details

Description

Added a /clear command like the vanilla one
Fixed a typo in KillCommand
Added /version alias for /pumpkin
Changed message format for unimplemented packet id to match the protocol documentation from wiki.vg

Testing

[x] Clear command on self, player, players with and without stuff in inventories from client and console
[x] Version command from client and console

Checklist

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings cargo clippy

Thanks @solvictor

Clear command on self, player, players with and without stuff in inventories from client and console

why clearing empty inv?

At the moment each item is cleared individually

Clear command on self, player, players with and without stuff in inventories from client and console

why clearing empty inv?


Get CD benchmarks in?

@nhenriksen - we just got Germano's bromodomain stuff merged in, so would now be a good time for you to proceed towards getting your cyclodextrin stuff merged in as well? It seems like it will likely become important to do so fairly soon since it's potentially being used for the Yank paper (cc #41 ). Since we're done working on the bromodomain stuff now it should be possible to proceed towards merging without having to resolve conflicts multiple times.
Or, are there other things you need to do first?

Yes, I'm finishing up some text about "previous studies" right now.  I've already got tables and figure updated.  Hoping to have something for us to start discussing by tonight.

I've finished adding text, tables, references to the manuscript and merged in the latest changes from master (see f85a8ae1c9a4bb7a9c20f5a2da156bb905ddd6b1).  So it should be ready to start editing!

@nhenriksen - can you open a [WIP] PR? I like to do edits/discuss changes on a PR which is open. :)


[FLINK-11553] Create an empty fencing tokens queue instead of using null in DispatcherHATest.testFailingRecoveryIsAFatalError

What is the purpose of the change
DispatcherHATest.testFailingRecoveryIsAFatalError fails because it tries to instantiate HATestingDispatcher with fencingTokens = null which is annotated as @Nonnull.
The PR suggests to create an empty fencing tokens queue instead of using null.
Brief change log

fix DispatcherHATest.createDispatcher
small style fixes in DispatcherHATest

Verifying this change
run DispatcherHATest locally, e.g. in IDE Idea
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@flinkbot approve all


[2.x] Repeater component getting console error

Package
filament/forms
Package Version
v2
Laravel Version
v8
Livewire Version
No response
PHP Version
PHP 8.1
Bug description
When I remove element from Repeater component I am getting console error.

Steps to reproduce
Video
Relevant log output
No response

Couldn't replicate, as mentioned on Discord.


[bug] QAM immediately closes when using the "Guide + X" Controller combo

Device: GPD Win 4 6800u
Version: ChimeraOS 43-1
Bios: v3.06
Occasionally, ChimeraOS seems to enter an odd state where pressing "Guide +  X" will briefly open the QAM, only for it to immediately close. YT video of the bug: https://www.youtube.com/watch?v=I-5n0l_meTY
It usually eventually resolves itself if I press the "Guide" button by itself several times, the QAM combo starts working again.

Note, I suspect the issue might be related to handycon.
I'm going to test with the handycon service disabled, all controller buttons seem to be working fine on the Win 4 even with it disabled, and the back buttons weren't mapped to anything in ChimeraOS 43-1.

There was a bug in the win4 code shipped in v43-1 due to some bad data. Can you see if the problem exists with the latest version?
sudo frzr-unlock
sudo pikaur -Sy handygccs-git
reboot

Then try the program with sudo handycon

hrm, build with pikaur failed. investigating a bit more

had to temporarily change to SigLevel = Never in the /etc/pacman.conf file
after installing updated handycon, I was still able to replicate the issue.

edit: also, noticed that the left back button triggers screenshots on desktop, but doesn't seem to do anything in gamepadui.

It's still taking screenshots, steam broke the toast notification for screenshots in game mode.

It's still taking screenshots, steam broke the toast notification for screenshots in game mode.

hrm, I've definitely pressed the back buttons before in gamepadui, but there are no screenshots in my media folder. the QAM back button also never worked for me in gamepadui

note, after disabling the handycon service, I haven't been able to reproduce the issue.

Without a device in hand it will be challenging for me to figure out the solution here. Can you clone the repo and enable debug in the logger under src/handycon/handycon.py to get more logs. There might be something in there.

Without a device in hand it will be challenging for me to figure out the solution here. Can you clone the repo and enable debug in the logger under src/handycon/handycon.py to get more logs. There might be something in there.

I can try when I have some time, but as an update, I was able to replicate the issue with an external controller. I was using a dualsense with handycon disabled, and it triggered the problem.
perhaps this could be a steam client issue, i'll investigate a bit more when I have some time.

There have been some improvements to the "niceness" and efficiency to HandyGCCS recently. Is this still an issue with the latest hanygccs-git?

There have been some improvements to the "niceness" and efficiency to HandyGCCS recently. Is this still an issue with the latest hanygccs-git?

It's worth noting I run into the same issue on the Steam Deck. It's probably just the Steam client.

Oh they said it worked with Handycon disabled. So maybe not.

I updated handygccs, i'll test it out and see if I can replicate the issue.
Side note, the back buttons still aren't working in gamepadui.

I updated handygccs, i'll test it out and see if I can replicate the issue.
Side note, the back buttons still aren't working in gamepadui, but I can report that handycon now seems to properly register tapping the power button for suspend.

Can you open an issue on the HandyGCCS GH for that? Not having a gpd device makes fixing this a challenge and I'll need a dedicated thread to figure it out.

Can you open an issue on the HandyGCCS GH for that? Not having a gpd device makes fixing this a challenge and I'll need a dedicated thread to figure it out.

Sure, can do. meanwhile, i can report that i haven't been able to reproduce this issue yet. I'll keep this issue open for a bit longer, but assuming I can't replicate the issue, I'll close it.

note, seems that this bug w/ an external controller is a steam client issue, as seen on this Steam Deck reddit thread


Remove concurrency primitives from Scala.js RingBuffer

This PR resolves #393.

@jdegoes as far as I see there are no tests for javascript version. I propose either to add them in this PR, or merge the changes and I'll follow-up with tests in the next one. What do you think?

@mijicd I'll merge this one and we can get that in a followup. Thank you!


目标服务存在认证绕过漏洞

Describe the bug
通过访问URL:http://ip:port/user/save，获取目标内容如下:{"success":true,"data":null,"message":null},请问官方准备增加鉴权吗？我看源码其他接口也存在类似问题
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Environment

PowerJob Version: [e.g. 3.0.0]
Java Version: [e.g. OpenJDK 8]
OS: [e.g. CentOS 8.1]

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

重复issue，保留 #941


Cannot send message to kafka on windows with Sasl and Kerberos

Description
We are currently trying to run a .net kafka client on windows connecting to a kafka instance running in linux. However it appears we are having issues when authenticating with sasl and kerberos.
It seems as though we are authenticating from both the client and the broker but when the message is attempted to be sent we are getting authentication errors saying we cannot AUTH anymore. See below for details:
When running it appears we authenticate correctly to the instance when building the producer:
%7|1581026931.587|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Initializing SASL client: service name kafka_dev, hostname host.domain.com, mechanisms GSSAPI, provider Win32 SSPI
%7|1581026931.587|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Acquired Kerberos credentials handle (expiry in<PHONE_NUMBER>.-322922497s)
%7|1581026931.587|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Send SASL frame to broker (2556 bytes)
%7|1581026931.590|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Received SASL frame from broker (112 bytes)
%7|1581026931.590|SASLAUTH|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Initialized security context
%7|1581026931.590|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Send SASL frame to broker (0 bytes)
%7|1581026931.591|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Received SASL frame from broker (36 bytes)
%7|1581026931.591|SASLAUTH|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Validated server token
%7|1581026931.592|SASLAUTH|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Sending response message for user<EMAIL_ADDRESS>%7|1581026931.592|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Send SASL frame to broker (53 bytes)
%7|1581026931.592|SASLAUTH|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Authenticated
%7|1581023958.832|STATE|rdkafka#producer-1| [thrd:sasl_ssl://host.domain.com:9093/bootstrap]: sasl_ssl://host.domain.com:9093/bootstrap: Broker changed state AUTH -> UP

Our Broker Appears to be validating with the following:
INFO Successfully authenticated client<EMAIL_ADDRESS><EMAIL_ADDRESS>(org.apache.kafka.common.security.authenticator.SaslServerCallbackHandler)
However when trying to send the message we get the following error:
%7|1581023960.857|STATE|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: Broker changed state AUTH_HANDSHAKE -> AUTH
%7|1581023960.857|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: Initializing SASL client: service name kafka_dev, hostname host, mechanisms GSSAPI, provider Win32 SSPI
%7|1581023960.857|SASL|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: Acquired Kerberos credentials handle (expiry in<PHONE_NUMBER>.-322922497s)
%7|1581023960.857|BROKERFAIL|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: failed: err: Local: Authentication failure: (errno: Invalid argument)
%3|1581023960.857|FAIL|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: Failed to initialize SASL authentication: InitializeSecurityContext failed: Target unknown (0x80090303) (after 0ms in state AUTH)
%3|1581023960.857|ERROR|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: Failed to initialize SASL authentication: InitializeSecurityContext failed: Target unknown (0x80090303) (after 0ms in state AUTH)
%7|1581023960.857|STATE|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: Broker changed state AUTH -> DOWN
%7|1581023960.857|TOPPAR|rdkafka#producer-1| [thrd:sasl_ssl://host:9093/3]: sasl_ssl://host:9093/3: lob-app-result-evt-global [0] 1 message(s) queued but broker not up

How to reproduce
Our current configuration is the following:
var config = new ProducerConfig {
	BootstrapServers = "host.domain.com:9093",
	SaslMechanism = SaslMechanism.Gssapi,
	SecurityProtocol = SecurityProtocol.SaslSsl,
	SslCaLocation = "C:\\ca.pem",
	SslCertificateLocation = "C:\\ca.pem",
	SaslKerberosServiceName = "kafka_dev",
	Debug = "protocol,broker,protocol,msg,queue,security"
};

var schemaRegistryConfig = new SchemaRegistryConfig
{
	Url = "http://registry.domain.com:8081"
};

using (var schemaRegistry = new CachedSchemaRegistryClient(schemaRegistryConfig))
using (var p = new ProducerBuilder<AvroKey, AvroValue>(config)
	.SetKeySerializer(new AvroSerializer<AvroKey>(schemaRegistry))
	.SetValueSerializer(new AvroSerializer<AvroValue>(schemaRegistry))
	.Build())
{
	AvroValue val = new AvroValue
	{
		testValue = "testValue"
	};
	var key = Guid.NewGuid().ToString();
	await p.ProduceAsync(KAFKA_TOPIC, new Message<key, AvroValue> { Key = new AvroKey{ testKey = key}, Value = val });
}

Nuget version: 1.3.0.
OS: Win 10
Checklist
Please provide the following information:

[X] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[X] Confluent.Kafka nuget version.
[X] Apache Kafka version.
[X] Client configuration.
[X] Operating system.
[X] Provide logs (with "debug" : "..." as necessary in configuration).
[X] Provide broker log excerpts.
[ ] Critical issue.

InitializeSecurityContext failed: Target unknown

This implies that we are requesting a service ticket for a principal which does not exist in the KDC. My initial suspicion would be that there is not an SPN matching the broker's advertised hostname. The client will attempt to obtain a service ticket for<EMAIL_ADDRESS>There must be an SPN (or principal if this is a stand alone KDC on the linux box) otherwise an error like the one you see now will be returned.
You should also verify that all users in the exchange have strong encryption(AES) enabled for their accounts. This is a manual step and it is not enabled by default. The problem arises when the session key is negotiated and one of the peers does not support the default RC4 enc type.


contrib_bots: Fix typos and repetitions in the readme.

This PR fixes some minor issues with the readme file:

The structure at the beginning at the file was a bit repetitive.
There were some double spaces "hiding" in the text.
Titles now follow the same standards as in the rest of our docs.

Automated message from Dropbox CLA bot
@YagoGG, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @YagoGG!


How to get OV2640_2MP_PLUS to return a BMP image instead of JPEG

I am on an Arduino Leonardo r3. I am able to get the image to display in jpeg using the ArduCAM_Mini_2MP_Plus_VideoStreaming project. However, I would like to get a bitmap version of it since it is easier to work with in image processing.

The sketch you referenced demonstrates the various features of the ArduCAM, but the following two lines set the camera format to bitmap:
myCAM.set_format(BMP);
myCAM.InitCAM();
If your application is for bitmap only, these should appear in the sketch setup().


  This is the expected behavior of the build system.

OPS Build status updates of commit c2d40b4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix C-style cast in Cache subsystem

Will be rebased when other cleanup PRs are merged.

Nice catch! My clang-tidy and clangd missed them. I'll fix them.


Refactor Test-Connection

PR Summary
Refactor the Test-Connection cmdlet according to https://github.com/PowerShell/PowerShell-RFC/pull/172
PR Context
Resolves #6768
NOTE: Currently this changes the pattern from Ping.Send() to Ping.SendAsync() with a manual event handler. This is due to a bug that was only recently resolved (see https://github.com/dotnet/corefx/issues/38770#issuecomment-507788270)
We can return to the simpler Ping.Send() pattern once we hit .NET Core 3-preview8 per the comment in that issue. 🙂
TODO:

Cleanup verbose messages
Add tests

Additional suggestions:

Add sequence numbers or timestamps to the standard PingStatus items so it's easy to see the order they were received in. https://github.com/PowerShell/PowerShell-RFC/pull/172#issuecomment-507719725 - @bobfrankly
Add the ability to ping all IP addresses in a given CIDR range (DDoS concerns maybe?) - @Romero126

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Not sure it even makes sense to split style changes to be honest as this changen a heck of a lot that I would cover in a style PR anyway.
We're still blocked on preview6 so I'm leaving the temp fix in for now so we can trust test results. When we get preview8 it isn't difficult to switch the pattern back.

Have pity!😭 We have open about 50 PRs...

I know. But is one of these better, or four for the same thing? 😕
If you'd really rather extra style PRs I can probably look to trim some of that out, but in a lot of ways the style changes are kind of tied into the rest of the changes. Let me know what you'd prefer.

@vexx32 You will spend some time for temporary PRs but save a lot of time of reviewers.
It's incredible that someone can view more than 400-500 changes at a time.
After PR exeeds 100 changes, any style change significantly slows down the code review and begins to annoy.
While the PR draft you could make temporary PRs. I see many renames.
Also you could split functional changes too, ex. separate ping, traceroute and etc. to different PRs.
As for async, we get Preview7 in 5 weeks. I suppose we have nowhere to hurry.

Yeah, I guess that makes sense.
I'll look to do a style pass and see how I can split it out from there. Thanks! 💖

Closing this as this has been superceded by #10697


Consider changing zoom plugins to allow mobile zoom

Won't fix, removed zoom as it's not very useful anyway


Template repositories for common arfc repo types.

I'm submitting a ...

[x] feature request

Expected Behavior
There is a way to create templates for new repositories in one's GitHub organization, so that each new repository contains what is expected as soon as it is created.
https://help.github.com/en/articles/creating-a-template-repository
This is a great opportunity to improve our workflow for new repositories. I suppose there should be template repository for :

[x] presentations
[x] journal articles
[ ] technical reports
[ ] conference papers
[ ] software projects

It's possible that the first four could be captured in a single template with subfolders that can be deleted by the user during the first moment.
Ideally, all repositories in this org should have a handful of key things (readme, license file, contributors document, proper issue labels, etc.). Presentations should stem from the arfc presentation template (maybe that repository should just become the template for others?)
Actual Behavior
no templates exist.
How can this issue be closed?
This issue can be closed when template repositories are available which can generate repositories with all the expected stuff in them.
Steps:

[ ] Understand templates repositories
[ ] Determine a checklist of things that each repository template type requires (work with Prof. Huff)
[ ] Create templates for each type
[ ] Make a PR to this repository adding an arfc manual guide for using these templates.
[ ] close this issue when your PR is merged.

Maybe an undergraduate would be interested in doing this work (@kipk49 @aruzzo @datw0258 @nathanb01 )

Same hopes, new summer! @datw0258 @Dayvis7 @nsryan2 ... anyone interested? The presentations and journal articles templates have been created. Now it's time to think about conference papers, etc.

Maybe someone who is considering submitting an ANS summary (@samgdotson @robfairh @ZoeRichter?) would be interested in making an ANS summary template with the ANS .cls file, etc....

I have a couple templates that I was working on for the Student Conference 2021 (before it was changed to 2022), I think they would fit the purpose that this issue describes. They are currently .docx files (I think), but I can format them into LaTex and make a template repository from them.

@nsryan2 No need to create a format in LaTex from a word document. ANS has a LaTeX template that we can just turn into a repository. In fact, I already have.
This is closed by #1 in ans-abs-template

Awesome, I'm looking at your pull request right now

There is a report-template repository, and from what I can tell it seems to align with the technical report template requested in this issue. Would adding instructions on how to initialize it to the ARFC report page, and the README.md in the repository file be a good next step?

Seems appropriate to me.


REQUEST: Dump of *Google.com orgs and  CLA Manager

Googlers who have not signed the CLA have reported multiple google orgs listed and CLA managers that don't exist or have names like "vegemite cheese toast". I would like a dump of orgs and active CLA managers to audit.

Hi @mrbobbytables, thanks for reporting this issue. Allow me review all Google information in our systems and will update you with my findings.

@jarias-lfx thanks! something definitely seems fishy with the primary google one right now...only 4 CLA Managers and 3/4 aren't Googlers.

@mrbobbytables do you mind if I contact you directly at<EMAIL_ADDRESS>to handle this information?. This to avoid exposing private information. Thanks.

Thanks!
Dump was provided and current CLA Managers updated.
There is some follow up to learn how some of these folk became CLA Managers, but that's a separate issue.


Messaging: UI Improvements

What does this pull request aim to achieve? 💯
please check #1878
Please be concise and link any related issue(s):
closes #1878
closes #1884

[x] I have checked that no one else is working on similar changes.
[x] I have read the latest README and understand the development workflow.
[x] The name of this branch is: feature/<branch_name>, or hotfix/<branch_name> if this is a hotfix, where <branch_name> briefly describes the issue(s) resolved and is prefixed with the issue number(s) (e.g. 1127-1130-update-git-branching-model). The branch is created in a cloned version of this repo, not a forked repo.
[x] This branch is rebased/merged with the latest staging (or the latest production if it is a hotfix).
[x] There are no merge conflicts.
[x] There are no console warnings and errors.
[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".
[x] The title describes the issue(s) being addressed using format: <issue_numbers> - <brief_issue_description> (e.g. #1127/#1130 - Update Git Branching Model)

Unlogged user not able to messenge to the user through profile. #1884 is fixed and works as expected.


Support packed tests

Some developers may write their tests in the docstrip format, for example to unify common setup code for multiple tests. (You may look at a simple exemplary use case here.)
l3build.lua does currently support this quite poorly. testfiledir can be set to unoackdir to make generated lvt files be found, but then build.lua save stores the tlgs into unpackdir where they are soon to be deleted.
This patch looks for lvts in unpackdir, too, but still stores tlgs into testfiledir, where they persist.
I read that you do not apply patches directly at github. If you favor to receive this patch in any other way, please leave a comment.

I'd imagine someone packing their .lvt files into a source might also pack the .tlg files. Should that be supported too, at least from the 'where to look for results' part? (Clearly the 'save the results' part is going to be limited in what in can do under such circumstances.)

Aside:  Pull requests don't really 'work' here because the Git repo is only a mirror of the 'real' one (Subversion). That means it's more-or-less read-only.

As pull requests cannot be merged directly, can you direct me to a more appropriate way to submit patches?
Packing .tlg files is indeed a sensible idea, so I incorporated it. The "save" command can still be used, but it shows a warning when masking a generated file.

The recent commits also look for sourcefiles to unpack in testdir, but only for the commands dealing with tests. This keeps things neatly assorted. I also added documentation and a simple example to the testfiles directory showing how to use packed tests.  The latter have dashes in their name and will work with patch #205.

I'm working through the various changes: one or two seem to cause issues at my end and I want to be sure I understand them all! Will check something in over the next day or so.

I've integrated the idea so will close (hope this the right way to handle pull requests!).

@dffischer BTW, thanks very much for this and other suggestions :-)

hope this the right way to handle pull requests

The ideal way would be to mark it as merged instead of closed, but I don't know whether this is possible in a mirror.
Thanks for the quick processing.

@dffischer  As I say, we can't merge (it would alter the GitHub version of the mirror but thus be out-of-sync with the SVN)


Bump dependencies : micrometer, centraldgoma, brave..

Motivation
Match dependencies set with the recently upgraded spring-boot version and generally keep the build up-to-date
Transitive changes

Micrometer 1.6.6 -> 1.7.5

Breaking changes (https://github.com/micrometer-metrics/micrometer/releases/tag/v1.7.0) : support for prometheus-simpleclient < 0.10 is dropped.
See other release notes for minor changes

Brave 5.12.6 -> 5.13.3 ( bitter release notes: https://github.com/openzipkin/brave/releases/tag/5.13.2 )
Centraldogma 0.49 -> 0.52 ( nothing major for our use case : https://github.com/line/centraldogma/releases )

looks good, thanks!


build: Update to header 1.3.285

CI Vulkan-Tools build # 1447 failed.

CI Vulkan-Tools build # 1447 failed.

CI Vulkan-Tools build queued with queue ID 184535.

CI Vulkan-Tools build # 1448 running.

CI Vulkan-Tools build # 1448 passed.


Cop idea: use all_day instead of manually creating the day range

Is your feature request related to a problem? Please describe.
I've seen (and wrote) a lot of the .where(some_date_field: date.beginning_of_day..date.end_of_day) code.
Today I learned there is .all_day shortcut for that.
Describe the solution you'd like
A cop to promote the above would be nice

Implementation note: Available since Rails 5.1

There’s also all_week, all_month and all_year (And all_quarter but it’d be harder to autocorrect to that reliably)

Related materials:

https://github.com/rails/rails/pull/24930
https://github.com/rails/rails/pull/9685


validate inputs already declared (i.e an input with the same fullpath must not be declared twice) (think declaring the same variable twice in the same scope in java)

Fixed in https://github.com/oracle/helidon-build-tools/pull/623


Unaligned access in SRCREADPIXEL (16 bpp) in bitmap_decode.c

Hello,
I am porting FreeRDP to an older ARM processor which would genereate an exception on unaligned access. This could occur when using the SRCREADPIXEL in 16bpp session.
See the proposed patch:
https://gist.github.com/ptsekov/40f2aeb71b9883f20423

Color conversion has been rewritten in 3c7cc555a5a5f02366918be7eb935bb1f22115ef


HDDS-7243. Remove POST_PROCESSOR from OzoneManagerRequestHandler echoRPC method

What changes were proposed in this pull request?
The way this is written the method echoRPC should only run for older clients, but older clients do not have the echo rpc.
Thus, we need to remove POST_PROCESSOR from OzoneManagerRequestHandler's echoRPC method.
Also, remove echoRPC method from going through RATIS for now.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-7243
How was this patch tested?
Freon robot tests.

cc. @kerneltime @errose28

@DaveTeng0 any update to this one?

@DaveTeng0 any update to this one?

Yes! This is still working in progress! I was deviated to other thing, and I'll try to get back to this maybe after a week or two!

The updated PR is in https://github.com/apache/ozone/pull/4051
Closing this one!


need if_is_bitmap and if_is_enum support underneath zcl_event_fields

Trying the below
switch (TLV::TagNumFromTag(reader.GetTag()))
{
{{#zcl_event_fields}}
case to_underlying(Fields::k{{asUpperCamelCase name}}):
#ifdef CHIP_USE_ENUM_CLASS_FOR_IM_ENUM
{{#if_is_enum type}}
ReturnErrorOnFailure(Check{{type}}({{asLowerCamelCase label}}));
{{/if_is_enum}}
#endif
{{#if_is_bitmap type}}
ReturnErrorOnFailure(Check{{type}}({{asLowerCamelCase label}}));
{{/if_is_bitmap}}
ReturnErrorOnFailure(DataModel::Decode(reader, {{asLowerCamelCase name}}));
break;
{{/zcl_event_fields}}
default:
break;
}
it seems if_is_enum and if_is_bitmap cannot work underneath zcl_event_fields
it seems it is working with command and attribute, thanks
needs this to unblock one IM thing, https://github.com/project-chip/connectedhomeip/issues/19334

@yunhanw-google is there an enum or bitmap type which is not detected as one with the above template?

@brdandu : this doesn't seem to work within 'events'. I was planning to take a look, but I suspect that when querying for the Matter "events" we don't properly populate stuff that those if helpers need.

@brdandu : this doesn't seem to work within 'events'. I was planning to take a look, but I suspect that when querying for the Matter "events" we don't properly populate stuff that those if helpers need.

There might be an issue in ON   EVENT_FIELD.EVENT_REF = EVENT.EVENT_ID because of EVENT_FIELD.EVENT_REF instead of EF.EVENT_REF

@yunhanw-google :
I created a new unit test template that looks like this:
List of all events.

{{#zcl_events}}
>> Event: {{name}}
{{#zcl_event_fields}}
    > Field: {{name}} {{#if_is_enum type}}[ENUM]{{/if_is_enum}}{{#if_is_bitmap type}}[BITMAP]{{/if_is_bitmap}}
{{/zcl_event_fields}}
{{/zcl_events}}

So simple iteration across all events and then over fields.
I see that the enums are detected, and I don't think there is any bitmaps in my XML files anyway, so I get:
List of all events.

>> Event: AccessControlEntryChanged
    > Field: AdminNodeID
    > Field: AdminPasscodeID
    > Field: ChangeType [ENUM]
    > Field: LatestValue
    > Field: AdminFabricIndex
>> Event: AccessControlExtensionChanged
    > Field: AdminNodeID
    > Field: AdminPasscodeID
    > Field: ChangeType [ENUM]
    > Field: LatestValue
    > Field: AdminFabricIndex
>> Event: StateChanged
    > Field: ActionID
    > Field: InvokeID
    > Field: NewState [ENUM]
>> Event: ActionFailed
    > Field: ActionID
    > Field: InvokeID
    > Field: NewState [ENUM]
    > Field: Error [ENUM]
>> Event: StartUp
    > Field: SoftwareVersion
>> Event: ShutDown
>> Event: Leave
>> Event: ReachableChanged
    > Field: ReachableNewValue
>> Event: StateTransition
    > Field: PreviousState [ENUM]
    > Field: NewState [ENUM]
    > Field: Reason [ENUM]
    > Field: TargetSoftwareVersion
.
.
.

See the "[ENUM]" thingies, which is printed because of "if_is_enum" in the template.

If I temporarily change one of the types in my test files to bitmap, then I also see "[BITMAP]" printed out.
So at this point I am not sure I understand what is not working here.
@yunhanw-google :
can you post a complete template here, please, including the outer "{{zcl_events}}" tag?
Your snippet starts with "zcl_event_fields", and that has to exist within an outer "zcl_events" anyway, so I would like to see the complete template.

Draft pull request: https://github.com/project-chip/zap/pull/574
adds these unit tests if you want to check.

let me have a try, thanks

i see, thanks


Callout Autocomplete Pop-up

#249 More an FYI than an issue on the autocomplete pop-up for callouts. I initially thought the feature wasn't working. If you don't put a space between > and [ the autocomplete doesn't show-up. If it's a quick fix it would be nice if the space wasn't necessary.

I didn’t even know this was possible! Thanks, I’ll update it.


:package: documented integration

Closes #24

Pull Request Test Coverage Report for Build 309

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

Totals

Change from base Build 307:
0.0%

Covered Lines:
44

Relevant Lines:
47

💛  - Coveralls


Add text-based filter in members page for Job title

Changes proposed ✍
What
Fixes #1241

🤖 Generated by Copilot at abef4fc
Added a new filter for job title to the member filters on the frontend. Modified frontend/src/modules/member/config/filters/main.ts to import and use the new filter configuration from frontend/src/modules/member/config/filters/jobTitle/config.ts.

🤖 Generated by Copilot at abef4fc

Filter by jobTitle
A new string attribute
Autumn of careers

Why
How

🤖 Generated by Copilot at abef4fc

Add a new filter for job title of members (link)
Include the job title filter in the member filters object (link)

Checklist ✅

[ ] Label appropriately with Feature, Improvement, or Bug.
[ ] Add screehshots to the PR description for relevant FE changes
[ ] New backend functionality has been unit-tested.
[ ] API documentation has been updated (if necessary) (see docs on API documentation).
[ ] Quality standards are met.

@joanagmaia updated :)

Hey @peoray just merged 2 of your PRs 😄
Can you resolve conflict so that I can also merge this one after? Thanks!

@joanagmaia resolved :)


Sort definitions in SCSS files to make them pass validators

I came across asciidoctor-epub3 some time ago and use it for my own projects. Back then I already noticed that the CSS files placed into the resulting *.epub file were causing many warnings and errors in validators.
So, after using it for some years now, I finally got the time to fix all the issues. I verified my changes with the hardware I have at hand here (read:  Calibre 7.6.0 and my dusty Kobo GloHD with firmware version 3.19.5761 from December 2015). Both readers don't show any differences in the tests I did, but I can't cover all devices out there, of course.
There have been no changes in the semantics, just changes in the order of the individual CSS definitions.
I would kindly ask to review my changes and get them integrated at some point, but I also noticed that the files follow a more visual approach in the order they define the individual styles: from top to bottom. Header and chapter definitions come first in the files, then the stuff which goes into the content area (tables, paragraphs, images, ...) and finally there are definitions for footers. So I would also understand if my changes are not considered an improvement and keeping the current order being favored.

Hi, my main question here is: what validator you use (and how) and whether we can integrate it into asciidoctor-epub3 testsuite to make sure CSS stays valid in the future. We already use EPUBCheck, but it doesn't report any issues in current CSS.

I used the validator integrated into Calibre (its "eBook Editor"). From the menu it can run checks on the whole book and came up with a total of 70+ issues.

Ah, that's the bit I was missing, thanks.
WRT EPUBCheck: asciidoctor-epub3 has builtin support for that. You install epubcheck-ruby gem, make sure java is available on PATH and simply pass -a ebook-validate argument to asciidoctor-epub3. It is true that EPUBCheck does not have a strong CSS validation.

Talking about automation for testing:
I just did a search on this matter, but it looks like the Calibre editor has no option to perform these checks from command line. Also, I guess, it would require some UI in order to start. So that's not an option. However, maybe the foundation of the Calibre applications is something which could be integrated into asciidoctor-epub3 as well (like some sort of CSS LINT library).


Allow setting a custom output file which will contain all types, fixes #9

Adding a new flag to set a custom output file will allow you to set a single file for all the code to go into which essentially works around the problem in issue #9, one other possible solution is to clear the buffer at the end of the loop but it all depends on how you want this program to work (I can see reasons both individual files or a file for each one).

I signed it!
That being said it's not letting me put the email address i use for git commits in as an alternative saying it's associated with another account

@campoy any chance you can look at this, just noticed this has been sitting around


Remove ros2_control tag from package (and move it to ur_robot_driver)

There definitively is a need for using the robot description without the ros2_control tag in general e.g. when simply viewing the robot model (also see #52).
This commit removes the dependency to the ros2_control tag from the macro instantiating a robot and adds new files describing the control mechanisms of the individual joints and sensors.
These files can be included in ros2_control files setting up a specific control structure (e.g. hardware driver, mock hardware, gazebo).
This change would require packages like driver, gazebo startup, etc. to provide their own descriptions with their own ros2_control tags but I personally don't see this that negative. As also raised in https://github.com/UniversalRobots/Universal_Robots_ROS2_Description/pull/52#issuecomment-1511073354 users will have to provide their own ros2_control tag for their own configuration as soon as there is more than only the (or more than one) UR involved.
I think the approach from this PR leaves a simple to use UR macro, a standalone (non-control) description and a couple of helper macros to create your own ros2_control tag.

I personally see a lot of value in a well-tested, officially supported ros2_control tag that comes with the robot's description files. If I had to deploy a UR-based system, I'd always try using the official tags once I'm past the prototyping stage.
Speaking of which, many tools used for prototyping may want to supply/generate their own ros2_control tag content (or not technically need it at all) which should also be supported somehow. I'm wondering if this could not be achieved with a much simpler new required parameter that turns ros2_control support on-off.
  <xacro:macro name="ur_robot" params="
    name
    tf_prefix
    parent
    *origin
    joint_limits_parameters_file
    kinematics_parameters_file
    physical_parameters_file
    visual_parameters_file
    generate_ros2_control_tag
    ...
  >

Please tell me if this is outlandishly oversimplified :D

I personally see a lot of value in a well-tested, officially supported ros2_control tag that comes with the robot's description files. If I had to deploy a UR-based system, I'd always try using the official tags once I'm past the prototyping stage.
Speaking of which, many tools used for prototyping may want to supply/generate their own ros2_control tag content (or not technically need it at all) which should also be supported somehow. I'm wondering if this could not be achieved with a much simpler new required parameter that turns ros2_control support on-off.

One issue I have with keeping this inside here is that the whole hardware interface parametrization is piped through the description. In my point of view that carries mainly two negative implications:

The description contains a wall of parameters that are only relevant if it is ought to be used in conjunction with the ur_robot_driver. Even more we have to define bogus default values since we cannot pass empty values to the hardware interface (which I realize while writing this is no longer true).
Extending the driver's functionalities with new data being used in controllers requires a change on the description and the driver simultaneously (such as #110 / https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/856)

I am not 100% sure about the cleanest solution and I know that this discussion has been done before, never coming to a final solution which I want to change with this PR.
So thank you for joining the discussion I hope that we find a solution that everybody can agree on. I'm not a huge fan of at-mentioning people, but since we had this discussion before, I would love to get input from @ipa-cmh, @destogl, @gavanderhoorn, @RobertWilbrandt  on this suggestion.
To not seem like I am ignoring input from previous discussions:

I did not create a separate package for the ros2_control tag mainly because of the two points raised above. The biggest part of the existing tag is parametrizing the ur_robot_driver's hardware interface. From my point of view this part should live with the driver.
Although the title says "remove" more appropriately it should probably say "move to driver", see https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/877
I would like to minimize code duplication, hence I've created the helper files here.

Thanks for the great writeup!
What can the user expect to change on their side?
Going from the current
  <xacro:ur_robot
    name
    tf_prefix
    parent
    *origin
    joint_limits_parameters_file
    kinematics_parameters_file
    physical_parameters_file
    visual_parameters_file
    ... (one gazillion potentially irrelevant parameters)
  >

to
  <xacro:ur_robot
    name
    tf_prefix
    parent
    *origin
    joint_limits_parameters_file
    kinematics_parameters_file
    physical_parameters_file
    visual_parameters_file
    ... only description-relevant parameters
  >

  <xacro:ur_ros2_control
    ... relevant parameters for real HW driver or SIM
  >

or if you don't want ros2_control at all, to simply
  <xacro:ur_robot
    name
    tf_prefix
    parent
    *origin
    joint_limits_parameters_file
    kinematics_parameters_file
    physical_parameters_file
    visual_parameters_file
    ... only description-relevant parameters
  >

I quite like this :point_up:

Here's my next question: could this be made part of Humble in any way?
Perhaps for backward compatibility you could add the new macro to the driver there (same as w rolling) and a define_ros2_control_tag boolean param to the main macro?

Here's my next question: could this be made part of Humble in any way?
Perhaps for backward compatibility you could add the new macro to the driver there (same as w rolling) and a define_ros2_control_tag boolean param to the main macro?

Yes, that sounds reasonable. Nobody plans to actively break Humble anyway 8-)

This move sounds reasonable to me also. In few more recent drivers we started to split things  in similar way. We are even adding "ros2_control_support" packages with all ros2_control-related things and then this package can load description of a robot needed. Since here you have only ros2_control as driver, moving this to driver is good.
Only things to consider to not get lost. We have to update gazebo and igniton packages  add add those two URDF snippets for those there. For now I would be happy with just a draft PR adding this somewhere. Those two packages needed anyway some more attention (at least when I checked them last time - and I feel responsible for that, but...)


Only message skeleton in folder (race condition?)

Expected behavior
I want to see the whole message. Not only a skeleton.
Actual behavior
I guess there is a race condition where only a skeleton of the message gets down loaded.
In rare conditions k9 thinks it has already downloaded the whole message.
Steps to reproduce
Open the folder, open the first file. Do this in a folder you have not opened since some weeks.
First I thought, k9 will detect this and download the message later. But even on the next day the display is like on the screenshots below. The message is ok in thunderbird.
Environment
K-9 Mail version: 5.010
Android version: 4.1.2
Account type (IMAP, POP3, WebDAV/Exchange): IMAP
I attach two screenshots.

Duplicate description to #1541. Can you provide the source of emails that aren't shown.

@philipwhiuk I think it does not make sense to provide the message source. The message is an automated message which I receive every month. The message can be read with thunderbird. I validated my assumption like this: I renamed the folder (in thunderbird), then reloaded the folder list (in k9) and opened the mail in the new folder name. K9 thinks this is a new folder and loads the messages headers, then I open the same message ... and it works.
This underlines my assumption: The message source does not matter. This is a race condition. Somewhere inside k9 the message gets the flag "downloaded" before the message is finally fetched.
What do you, with more insight to the k9 internals think?

That's a good theory.
However we'd need logs to confirm it.

Probable duplicate #1243

This could probably happen if sync is interrupted and downloading the meta data finished, but not downloading the message body.

This should no longer be an issue.


"Restart" kernel button for notebook keeps disappearing even though the kernel is active?

This one is a bit hard to articulate, but I've been facing it for a few weeks now, so I'm going to give it my best attempt.
Environment data

VS Code version: Version: 1.88.0-insider
Jupyter Extension version (available under the Extensions sidebar): v2024.3.2024030101 (pre-release)
Python Extension version (available under the Extensions sidebar): v2024.2.1
OS (Windows | Mac | Linux distro) and version: Mac
Python and/or Anaconda version: 3.12.x
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local

Expected behaviour
I would expect the "Restart" button at the top of the notebook to always appear when the Notebook kernel is active.
Actual behaviour
But frequently, the kernel is running for a Notebook (as I've a cell that just executed a result), but the Restart button never appears.

If I try to use the "Notebook: Restart Kernel" from command palette

I even noticed the Jupyter tab does not show any variables, almost like it's lost its connection to the kernel temporarily.
Steps to reproduce:
This bit is tricky. I've noticed this happens especially when I switch between file tabs, or if the Notebook is opened in a separate window. When I switch to-fro between two notebooks, it tends to reappear (I use this as a workaround for now). So maybe the best way to repro is:

In a workspace, create a new notebook.
Move notebook to separate window, and run a cell. The restart button should appear.
Now switch a few times between the notebook window and a file tab inside your workspace, you will notice when you go back to the notebook, the restart button disappears. A few more times, and it reappears.

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

I did switch to verbose, restarted vs code, and repro the issue. Below is the log.. and you can see in screenshot the 'Restart' button is not appearing, even though I just executed a cell successfully moments before.

00:10:58.215 [debug] Kernel output: NOTE: When using the `ipython kernel` entry point, Ctrl-C will not work.

To exit, you will have to explicitly quit this process, by either sending
"quit" from a client, or using Ctrl-\ in UNIX-like environments.

To read more about this, see https://github.com/ipython/ipython/issues/2049

To connect another client to this kernel, use:
    --existing kernel-v2-31057R5cJOXCwBj22.json

00:10:58.548 [debug] Waiting for Raw Session to be ready in postStartRawSession
00:10:58.548 [debug] Waiting for Raw session to be ready, status: connected
00:10:58.548 [debug] Raw session connected
00:10:58.548 [debug] Waiting for Raw session to be ready
00:10:58.552 [debug] Waited for Raw session to be ready & got status: connected
00:10:58.552 [debug] Successfully waited for Raw Session to be ready in postStartRawSession
00:10:58.552 [debug] Kernel status is 'unknown' before requesting kernel info and after ready
00:10:58.552 [debug] Sending request for kernelInfo
00:10:58.750 [debug] Got response for requestKernelInfo
00:10:58.750 [debug] Successfully completed postStartRawSession after 1 attempt(s) in 198ms
00:10:58.751 [debug] Executing silently Code (idle) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys
00:10:58.766 [debug] Executing silently Code (completed) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys with 1 output(s)
00:10:58.766 [debug] End sendTelemetryForPythonKernelExecutable after 15ms
00:10:58.766 [debug] Started running kernel initialization for ~/code/###redacted###/src/app/notebooks/foo_collector.ipynb
00:10:58.766 [debug] Executing silently Code (idle) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy
00:10:58.818 [debug] Executing silently Code (completed) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy with 1 output(s)
00:10:58.818 [debug] Determined IPyWidgets Version as 8
00:10:58.818 [debug] Version of IPyWidgets 8 determined after 5.523s
00:10:58.828 [debug] Executing silently Code (idle) = def __VSCODE_inject_module():\ndef __VSCODE_call_function(function, callback, data=None):
00:10:58.845 [debug] Executing silently Code (completed) = def __VSCODE_inject_module():\ndef __VSCODE_call_function(function, callback, data=None): with 2 output(s)
00:10:58.846 [debug] Requesting Kernel info
00:10:58.847 [debug] Got Kernel info
00:10:58.847 [debug] End running kernel initialization, now waiting for idle
00:10:58.847 [debug] Waiting for idle on (kernel): 9f6f1726-ba1d-481c-a362-43f1e909f8b5 -> idle
00:10:58.848 [debug] Finished waiting for idle on (kernel): 9f6f1726-ba1d-481c-a362-43f1e909f8b5 -> idle
00:10:58.848 [debug] End running kernel initialization, session is idle
00:10:58.854 [info] Registering Kernel Completion Provider from kernel .conda (Python 3.12.2) for language python
00:10:58.855 [debug] IPyWidgetScriptSource.initialize
00:10:58.855 [debug] IPyWidgetMessageDispatcher.initialize
00:10:58.876 [debug] getDataDirsImpl, Class name = Vr (started execution), Arg 1: "~/code/###redacted###/src/app/notebooks/foo_collector.ipynb", Arg 2: "~/code/###redacted###/.conda/bin/python"
00:10:58.876 [debug] Get Custom Env Variables, Class name = Um (started execution), Arg 1: undefined, Arg 2: "RunPythonCode"
00:10:58.877 [debug] Get Custom Env Variables, Class name = Um, completed in 1ms, has a truthy return value, Arg 1: undefined, Arg 2: "RunPythonCode"
00:10:58.877 [debug] Jupyter Paths :
00:10:58.879 [info] Process Execution: ~/code/###redacted###/.conda/bin/python ~/.vscode-insiders/extensions/ms-toolsai.jupyter-2024.3.2024030101-darwin-arm64/pythonFiles/printJupyterDataDir.py
00:10:58.938 [warn] Got a non-existent Jupyter Data Dir file://~/.local/share/jupyter
00:10:58.939 [debug] getDataDirsImpl, Class name = Vr, completed in 63ms, has a truthy return value, Arg 1: "~/code/###redacted###/src/app/notebooks/foo_collector.ipynb", Arg 2: "~/code/###redacted###/.conda/bin/python", Return Value: <Uri:~/Library/Jupyter>, <Uri:~/code/###redacted###/.conda/share/jupyter>, <Uri:/usr/local/share/jupyter>, <Uri:/usr/share/jupyter>
00:10:59.379 [debug] IPyWidgetMessageDispatcher.initialize
00:10:59.379 [debug] Web view is ready to receive widget messages
00:10:59.465 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
00:10:59.465 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
00:10:59.465 [debug] IPyWidgetMessageDispatcher.initialize
00:10:59.465 [debug] IPyWidgetMessageDispatcher.initialize
00:10:59.484 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
00:10:59.484 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
00:10:59.599 [debug] Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net~/.vscode-insiders/extensions/ms-toolsai.jupyter-2024.3.2024030101-darwin-arm64/temp/scripts/2f2dd93ffeb4c9c0acff03512bfd4d8dd83285f125b6d275e355e9146008e35f/jupyter
00:10:59.599 [debug] Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net~/.vscode-insiders/extensions/ms-toolsai.jupyter-2024.3.2024030101-darwin-arm64/temp/scripts/2f2dd93ffeb4c9c0acff03512bfd4d8dd83285f125b6d275e355e9146008e35f/jupyter
00:11:00.044 [debug] Refreshed Environments
00:11:01.045 [info] End refreshing Kernel Picker<PHONE_NUMBER>095)
00:11:36.277 [info] Handle Execution of Cells 0 for ~/code/###redacted###/src/app/notebooks/foo_collector.ipynb
00:11:36.282 [debug] Cell Index:0 sent to kernel
00:11:36.288 [debug] Start cell 0 execution @<PHONE_NUMBER>288 (clear output)
00:11:36.288 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>288
00:11:36.861 [info] End cell 0 execution after 0.572s, completed @<PHONE_NUMBER>860, started @<PHONE_NUMBER>288
00:11:36.861 [debug] Cell 0 executed successfully

One thing I noticed is if I click on the kernal name in the top right of the notebook - the 'Restart' button appears (even without me selecting/changing the kernel from the input/dropdown that appears near the command palette)

and there are no logs produced in the Jupyter output panel when this error dialog appears...

Please can you open your developer tools using the command Toggle Developer Tools, then go into the console window and see if there are any errors there
Thanks

Duplicate of https://github.com/microsoft/vscode/issues/200896#issuecomment-1980063937

Please can you open your developer tools using the command Toggle Developer Tools, then go into the console window and see if there are any errors there Thanks

Attached developer tools console... I don't see much activity in the console when I repro this issue, except for the 2 log messages in this file. hope that helps?
vscode-app-1709710996542.log

@DonJayamanne anything more I can help with here? it's causing a lot of pain in my workflows .. :(

@Yoyokrazy /cc


Is there a way to reduce the echoing?

What is the feature that you would like to see in the app? Please describe.
A way to automatically remove echo or reduce background noise
Is your feature request related to a problem? Please describe.
Sometimes there is a ton of echoing in my video calls, which makes the experience horrible.
Describe alternatives you've considered
Having people use a third party application like krisp.ai

That's a good question @RusseII!
I'm wondering if you could please elaborate on the kind of noise that you are hearing? Is it fan noise from a laptop? Or is it crosstalk between the user's output device and their input device? Also, are there certain devices or browsers that experience noise more than others?  Any additional details that you can provide would be very helpful.
It could be useful to check that the noiseSuppression and echoCancellation constraints are enabled.  The noiseSuppression feature is not supported in Safari, so users that use Safari will have more background noise in their audio tracks.

Thanks for the info @timmydoza
The noise was crosstalk between the users output device/input device - specially the user who was having the issue was using a Google Pixel 2 XL with google chrome.
I'll check on the noiseSuppression and echoCancellation.

Thanks for the info! I did some googling, and there are a number of people reporting the same echo issue on Pixel 2's.
If the issue isn't present on any other devices, then I'm inclined to think that this is a hardware issue and not a problem with this application.

Closing due to inactivity. I'd be happy to open again if this can be traced to an app problem.

Hi Team,
We are using the app on Desktop / Chrome for video call. We are observing ECHO most of the time during the call from Chrome
Since it is not reported by anyone so far, we are wondering if we have missed anything.
Could you please help

Hi @timmydoza and the Twilio team,
Could we please re-open this issue or should I create a new one?
I'm also facing this issue. When I'm connected to a room, and somebody connects to the same room from Chrome with turned on music or video, I hear this noise very loud. Is there any way to cancel this noise?
Also, you've mentioned noiseSuppression and echoCancellation, but I didn't get how to pass it to Twilio

@timmydoza please help with the above query

@aditya-protonn @Black-Stork it's been a while since you asked but we just came across this issue and ended up implementing it this way:
import Video from 'twilio-video'
// https://github.com/twilio/twilio-video-app-react/issues/143
// https://developer.mozilla.org/en-US/docs/Web/API/Media_Streams_API/Constraints#example__constraint_exerciser
let constraints = {}

try {
  let supportedContraints =
    window.navigator.mediaDevices.getSupportedConstraints()
  // https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackSettings/echoCancellation
  if (supportedContraints.echoCancellation) {
    constraints.echoCancellation = true
  }
  // not supported on Safari iOS
  // https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackSettings/noiseSuppression
  if (supportedContraints.noiseSuppression) {
    constraints.noiseSuppression = true
  }
} catch (error) {}

let track = await Video.createLocalAudioTrack(constraints)

Alternatively, this may work too:
track.mediaStreamTrack.applyConstraints({ echoCancellation: true, noiseSuppression: true })


MTDSA-13459: TYS changes for Amend a Foreign Property Income & Expenses Period Summary

I have updated the code based on the comments, thanks


Can't add cluster

Describe the bug
It fails to add cluster
To Reproduce

Try to add cluster context

Expected behavior
Cluster context added
Screenshots

Environment (please complete the following information):

Lens Version: 4.2.4
OS: macOS
Installation method (e.g. snap or AppImage in Linux): dmg(FYI. Download Link)

Logs:
I can't find Lens.app executable
Maybe... This one?
info: üîå Starting LensProxy
info: [LENS-PROXY]: Proxy server has started at http://localhost:61741
info: üîé Testing LensProxy connection ...
info: ‚ö° LensProxy connection OK
info: üñ•Ô∏è  Starting WindowManager
info: üß© Initializing extensions
info: [EXTENSION-DISCOVERY] loading extensions from /Users/beleap/Library/Application Support/Lens
info: [EXTENSION-INSTALLER] installing dependencies at /Users/beleap/Library/Application Support/Lens
info: [WINDOW-MANAGER]:¬†Loading Main window from url: http://localhost:61741 ...
info: [EXTENSION-INSTALLER] dependencies installed at /Users/beleap/Library/Application Support/Lens
info: [EXTENSION-DISCOVERY] watching extension add/remove in /Users/beleap/.k8slens/extensions
info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/extension-store/lens-survey/preferences-store.json
info: [EXTENSION]: enabled<EMAIL_ADDRESS>error: [EXTENSIONS-LOADER]: can't load extension main at /Users/beleap/Library/Application Support/Lens/node_modules/lens-telemetry/dist/main.js: Error: Command failed: ioreg -rd1 -c IOPlatformExpertDevice
/bin/sh: ioreg: command not found
 {"extension":{"id":"/Users/beleap/Library/Application Support/Lens/node_modules/lens-telemetry/package.json","absolutePath":"/Applications/Lens.app/Contents/Resources/extensions/telemetry","manifestPath":"/Users/beleap/Library/Application Support/Lens/node_modules/lens-telemetry/package.json","manifest":{"name":"lens-telemetry","version":"0.1.0","description":"Lens telemetry","main":"dist/main.js","renderer":"dist/renderer.js","lens":{"metadata":{},"styles":[]},"scripts":{"build":"webpack -p","dev":"webpack --watch","test":"jest --passWithNoTests --env=jsdom src $@"},"dependencies":{},"devDependencies":{"@k8slens/extensions":"file:../../src/extensions/npm/extensions","@types/analytics-node":"^3.1.3","analytics-node":"^3.4.0-beta.3","jest":"^26.6.3","mobx":"^5.15.5","node-machine-id":"^1.1.12","react":"^16.13.1","ts-loader":"^8.0.4","typescript":"^4.0.3","universal-analytics":"^0.4.23","webpack":"^4.44.2"}},"isBundled":true,"isEnabled":true},"error":{"status":127,"signal":null,"output":[null,{"type":"Buffer","data":[]},{"type":"Buffer","data":[47,98,105,110,47,115,104,58,32,105,111,114,101,103,58,32,99,111,109,109,97,110,100,32,110,111,116,32,102,111,117,110,100,10]}],"pid":38009,"stdout":{"type":"Buffer","data":[]},"stderr":{"type":"Buffer","data":[47,98,105,110,47,115,104,58,32,105,111,114,101,103,58,32,99,111,109,109,97,110,100,32,110,111,116,32,102,111,117,110,100,10]}}}
info: üì° Checking for app updates
info: Checking for update
info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/lens-cluster-store.json
info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/lens-extensions.json
info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/lens-filesystem-provisioner-store.json
info: [CLUSTER-STORE] requesting initial state sync
info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/lens-workspace-store.json
info: [WORKSPACE-STORE] requesting initial state sync
info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/lens-user-store.json
info: [CLUSTER-STORE] start to listen (1)
info: [WORKSPACE-STORE] starting to listen state events
info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [STORE]: LOADED from /Users/beleap/Library/Application Support/Lens/extension-store/lens-survey/preferences-store.json
info: [EXTENSION]: enabled<EMAIL_ADDRESS>error: [EXTENSIONS-LOADER]: can't load extension main at /Users/beleap/Library/Application Support/Lens/node_modules/lens-telemetry/dist/renderer.js: Error: Command failed: ioreg -rd1 -c IOPlatformExpertDevice
/bin/sh: ioreg: command not found
 {"extension":{"id":"/Users/beleap/Library/Application Support/Lens/node_modules/lens-telemetry/package.json","absolutePath":"/Applications/Lens.app/Contents/Resources/extensions/telemetry","manifestPath":"/Users/beleap/Library/Application Support/Lens/node_modules/lens-telemetry/package.json","manifest":{"name":"lens-telemetry","version":"0.1.0","description":"Lens telemetry","main":"dist/main.js","renderer":"dist/renderer.js","lens":{"metadata":{},"styles":[]},"scripts":{"build":"webpack -p","dev":"webpack --watch","test":"jest --passWithNoTests --env=jsdom src $@"},"dependencies":{},"devDependencies":{"@k8slens/extensions":"file:../../src/extensions/npm/extensions","@types/analytics-node":"^3.1.3","analytics-node":"^3.4.0-beta.3","jest":"^26.6.3","mobx":"^5.15.5","node-machine-id":"^1.1.12","react":"^16.13.1","ts-loader":"^8.0.4","typescript":"^4.0.3","universal-analytics":"^0.4.23","webpack":"^4.44.2"}},"isBundled":true,"isEnabled":true},"error":{"status":127,"signal":null,"output":[null,{"type":"Buffer","data":[]},{"type":"Buffer","data":[47,98,105,110,47,115,104,58,32,105,111,114,101,103,58,32,99,111,109,109,97,110,100,32,110,111,116,32,102,111,117,110,100,10]}],"pid":38013,"stdout":{"type":"Buffer","data":[]},"stderr":{"type":"Buffer","data":[47,98,105,110,47,115,104,58,32,105,111,114,101,103,58,32,99,111,109,109,97,110,100,32,110,111,116,32,102,111,117,110,100,10]}}}
info: [PROTOCOL ROUTER]: internal registering /preferences
info: [PROTOCOL ROUTER]: internal registering /
info: [PROTOCOL ROUTER]: internal registering /landing
info: [PROTOCOL ROUTER]: internal registering /landing/:workspaceId
info: [PROTOCOL ROUTER]: internal registering /cluster
info: [PROTOCOL ROUTER]: internal registering /cluster/:clusterId
info: [PROTOCOL ROUTER]: internal registering /cluster/:clusterId/settings
info: [PROTOCOL ROUTER]: internal registering /extensions
info: [PROTOCOL ROUTER]: internal registering /extensions/install/:LENS_INTERNAL_EXTENSION_PUBLISHER_MATCH(@[A-Za-z0-9_]+)?/:LENS_INTERNAL_EXTENSION_NAME_MATCH
info: [WINDOW-MANAGER]: Main window loaded
error: Can't find working API for the Kubernetes resource ingresses
info: Update for version 4.2.4 is not available (latest version: 4.2.4, downgrade is disallowed).

Kubeconfig:
kubeconfig was created by awscli, so I don't think it's wrong.
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: <<***censored***>>
    server: https://<<***censored***>>.ap-northeast-1.eks.amazonaws.com
  name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
- cluster:
    certificate-authority-data: <<***censored***>>
    server: https://<<***censored***>>.ap-northeast-1.eks.amazonaws.com
  name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
- cluster:
    certificate-authority-data: <<***censored***>>
    server: https://<<***censored***>>.ap-northeast-1.eks.amazonaws.com
  name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
contexts:
- context:
    cluster: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
    user: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
  name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
- context:
    cluster: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
    user: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
  name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
- context:
    cluster: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
    user: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
  name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
current-context: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
kind: Config
preferences: {}
users:
- name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - --region
      - ap-northeast-1
      - eks
      - get-token
      - --cluster-name
      - <<***censored***>>
      command: aws
- name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - --region
      - ap-northeast-1
      - eks
      - get-token
      - --cluster-name
      - <<***censored***>>
      command: aws
- name: arn:aws:eks:ap-northeast-1:<<***censored***>>:cluster/<<***censored***>>
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - --region
      - ap-northeast-1
      - eks
      - get-token
      - --cluster-name
      - <<***censored***>>
      command: aws

I don't know why but it resolved


Does not respect .eslintrc files in directory tree

I stumbled upon #21 (and #40) while using an older version of eslint-loader (something circa v0.13 / 0.14, right when these features hit).
I've updated both eslint-loader and eslint to the latest releases, but it seems webpack is still spewing out warnings for files that eslint proper does not warn about (as it should not warn about, due to .eslintrc files in the directory tree).
Should this be working as I expect, or is there still some work to be done?  The sentiment I got from #21 is that this should be working.
I didn't want to comment on the old issue as I'm not sure how that works out with closed issues.

Sorry for the noise; this is working fine.  As per the ESLint documentation, if you specify an ESLint configuration file when invoking the linter, it disables this hierarchical inheritance-based configuration functionality.  Removing this from the webpack configuration block for eslint does the trick...


As a user of Otomi CE, I want a change in my k8s ConfigMap and Secret detected automatically, so I can spend less time on managing team jobs

User story
This story is split from #204.
The relevant chart is otomi-core/chart/jobs.
Tasks
core:

[ ] Propose values-schema.yaml modification (if necessary)
[ ] Refactor out the boolean logic and replace it with the computation of a hash function which will detect whether a k8s ConfigMap or Secret has been modified.
[ ] Add the runPolicy key as an annotation in the job spec.
[ ] Remove the logic for cronJob, because it has no meaning there.

api:

[ ] Look at the example here so you don't need to reinvent the wheel.

Definition Of Done

[ ] Tasks are done
[ ] (Unit) Tests are added to code
[ ] (Architecture) Design Record(s) have been added as adr/*.md and appended to list in adr/_index.md
[ ] Specs and demo files have been updated to reflect code changes
[ ] Documentation has been updated
[ ] Functionality, code, and/or documentation has been peer reviewed
[ ] Relevant team members have been notified

same...close and integrate in your open PR

same...close and integrate in your open PR


Firestore Memory Persistence outdated docs

Description
Hello,
Firestore documentation shows code example using isPersistanceEnabled property:
https://firebase.google.com/docs/firestore/manage-data/enable-offline?hl=en&authuser=0#configure_offline_persistence
This property has been deprecated in recent Firebase SDK versions and this code will show a warning in Xcode, but the docs has not been updated.
Could you please tell how to rewrite following code to disable persistance with latest SDK version?:
let settings = FirestoreSettings()
settings.isPersistenceEnabled = false
let db = Firestore.firestore()
db.settings = settings

Thank you.
Reproducing the issue
No response
Firebase SDK Version
10.9
Xcode Version
14.3
Installation Method
CocoaPods
Firebase Product(s)
Firestore
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
No response
If using CocoaPods, the project's Podfile.lock
No response

Hi,
This block of code should be rewritten as
let settings = FirestoreSettings()
settings.cacheSettings = MemoryCacheSettings()
let db = Firestore.firestore()
db.settings = settings

And we are working on updating the documentation.

Hello @cherylEnkidu ,
Thank you for your message.
Could you please tell if settings.isPersistenceEnabled = false and settings.cacheSettings = MemoryCacheSettings() do exactly the same internally? I'm asking because we wanna know whether we need to re-test the app after making this change. Or can we just replace this line and be sure that it will work just like as before?

Hi @wu-hui @cherylEnkidu ,
I see that the docs has been updated now, but instead of MemoryCacheSettings(), which you suggested above, it uses MemoryCacheSettings(garbageCollectorSettings: MemoryLRUGCSettings()).
(https://firebase.google.com/docs/firestore/manage-data/enable-offline?hl=en&authuser=0#configure_offline_persistence)
Could you please tell what is the difference and what is the best option to use?
Thanks.

MemoryCacheSettings() uses a default GC strategy where documents are deleted from memory as soon as they are no longer used by any active queries. MemoryLRUGCSettings() overrides this behavior to use a LRU based gc, so documents will stay longer after they are not used, and when they are needed again SDK will have to re-fetch.
There are scenarios where either of these are useful, and it is hard to recommend a best option for all cases.


Add Argo to Built on Electron section

Thanks.

Argo is an open source trading platform, based on HTML5 technology, connecting directly with OANDA through the powerful API to develop trading strategies.
Website: http://argo.js.org/
Repo: https://github.com/albertosantini/argo

I prefer to resubmit the PR: no "icon" word in alternate text and no traling slash in the url.


Make the info overlay be fixed

This fix will make the view of the information be not affected by the decorators positioning, that can be applied to the story.
Can be the solution for this issues: https://github.com/storybooks/react-storybook-addon-info/issues/137 and https://github.com/storybooks/react-storybook-addon-info/issues/40

Hey @Kiwka
Thank you so much for this PR! We're moving over to a mono-repo, since that makes a lot of sense for a project like this.
We would ❤ it if you could create a PR here: https://github.com/storybooks/storybook
That'd be awesome, thanks!

@ndelangen wow! cool! I have created the new pull-request in the storybook https://github.com/storybooks/storybook/pull/914


Instruction in Docker part should be upgraded.

The instruction in Docker install is too old to run Cachet properly.
I use sqlite for DB_DRIVER, and when I run php artisan migrate, an error showed up to me with the following thing:
DB_DRIVER not configured
and it cannot read the db as well (but the database file is exist and configured)

Are you using the docker-compose instructions or the manual docker run method?

Actually I just realized you said sqlite - I only have tested the Docker setup using a MySQL Database driver.
I think we could add support for sqlite to the docker image by creating the touch storage/database.sqlite file and unsetting DB_HOST with -e DB_HOST
I will give this a test run and see how it works.

Looks like may be a little more difficult than I thought.  For now I would just stick with using a MySQL database, going to need to do a bit more testing to get sqlite supported for the Docker image.

@n0mer since you  seem to be doing most the new docker stuff:
Do we want to do the needful to make sqlite work in docker? Or just stick with SQL for now?

You may also need to clear the config if you've changed it?

@rtrauntvein, i use remote MySQL server (Amazon RDS).
Sorry, have no idea what sqlite is :)

Cool, I use RDS also in production ;)
I have no experience with sqlite either, so I think for now we should just say that if you are using the docker version of Cachet, you should be using MySQL database.
(Unless someone does a PR and documents how to use sqlite, of course)

@wfjsw, in order to ensure that your settings were properly applied - i would suggest you the following hack:

start Cachet with debug enabled
open non-existing page (like "http://:port/123") and observe debug output.

Ensure that DB_DRIVER is set sqlite, and other DB-related environment variables are set as well (if any).
If this is fine  - then execute docker -it cachet /bin/bash and explore container filesystem.
You might want to install additional software , let's say apt-get -qy update && apt-get install file mc

@jbrooksuk , do you think that admin webpage that displays basic
<?php phpinfo(); ?>

would help with troubleshooting like this?
It is always possible to put this line in the ./publis/index.html, but this is yet another hack :)

Something like that would be cool, a debug menu that we can show.

yeah, at least values for configuration variables like DB_HOST etc.
For v2.0/3.0 it would be handy to allow modifications of those values, but for now - just read-only display would help as well in configuration troubleshoot situations like this

I build my own Docker Image to include my .env. Web interface gives out No such file warnings but I have touched that.
I will test @n0mer 's idea in 3 days

We're looking for some new documentation for Docker on our documentation.
If your latest image is older than timestamp at https://registry.hub.docker.com/u/cachethq/cachet/builds_history/122451/
then please pull newer image via
docker pull cachethq/cachet:latest
And, this 'latest' tag is okay, but @jbrooksuk please ask someone responsible for this docker build, to create "1.1"  tag on Docker Hub.

also, in spirit of being 'good citizen' - please pay attention to #872

@wfjsw
proper way of seeding database (at least that worked for me) that uses external database (w/out docker images for mysql)

run Cachet image

!important! go inside container

$ docker exec -it cachet /bin/bash

and then
3. seed database like this
root@dc16dcd7a725:/var/www/html# php artisan migrate --force

@n0mer Hmm successed

@n0mer we're planning on handing off Docker support to someone else. We're waiting on two things:

New GitHub org permissions.
Release 2.0.0

Basically we're going to split out the Docker and Vagrant support and let someone/a couple of people support it for us.

It should be easy if things don't change much

@wfjsw , a little bit of off-topic - but how did you do this?? :)

i mean "hello world" :)

@n0mer It was generated with the GitHub Contributions generator.

@wfjsw we'll be keeping the core Cachet code and the Vagrant/Docker features separate :)

so now we should suggest user using bash to migrate databases?
I didn't test the sqlite situation but I think it is the same issue.

I can review the docket instructions. I really only tested the docker-compose setup
Sent from my iPhone

On Aug 5, 2015, at 8:52 PM, jsw<EMAIL_ADDRESS>wrote:
so now we should suggest user using bash to migrate databases?
I didn't test the sqlite situation but I think it is the same issue.
—
Reply to this email directly or view it on GitHub.

@wfjsw , if you are not using database driver directly , that you'll use bash anyway )

If you could, please submit suggestions to https://docs.cachethq.io/docs/get-started-with-docker, thanks!

" the various Redis drivers" - what does it mean? What drivers other than Predis is it possible to use? What is the finite list of drivers

Copy and paste from the README.

@jbrooksuk this page https://github.com/nrk/predis/blob/v1.0/README.md does not contain line "various Redis drivers"

@n0mer our README, see 1.1


Fix UnicodeDecodeError exception on decoding bytes body in init method

Codecov Report

Merging #8 into master will increase coverage by 0.52%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   68.39%   68.92%   +0.52%
==========================================
  Files          22       22
  Lines        1060     1078      +18
  Branches       74       74
==========================================
+ Hits          725      743      +18
+ Misses        297      296       -1
- Partials       38       39       +1

Impacted Files
Coverage Δ

ansq/tcp/protocol.py
89.33% <ø> (ø)

ansq/tcp/types/message.py
89.79% <100.00%> (+2.04%)
:arrow_up:

tests/test_read_messages.py
96.92% <100.00%> (+0.49%)
:arrow_up:

ansq/tcp/connection.py
60.40% <0.00%> (-0.41%)
:arrow_down:

Continue to review full report at Codecov.

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


Semantic update to userAddress auth-context state value

Up until now the default value for user address has been the string value none,
This is used by many components to assess if the user was logged in or not.
With this change, the default is now undefined (type undefined) and the components that utilize the userAddress value (conditional rendering etc) have all been updated to recognize this change
This change not only makes the code more legible but I believe it is just a better practice

@Kmoneal Does changing the default state of userAddress from "none" to undefined cause any breaking changes on the backend? If not, i'd like to merge this change. Not a huge priority though, so if it does cause any hassle on backend - we can delay.