[Security] Bump rails from 4.2.9 to 4.2.11

Pull requests into Bonnie require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] This PR is into the correct branch.
[x] JIRA ticket for this PR: https://jira.mitre.org/browse/BONNIE-1825
[x] JIRA ticket links to this PR
[x] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] If UI changes have been made, google WAVE plug-in has been executed to ensure no 508 issues were introduced.
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[x] Test fixtures updated and documented as necessary ( see internal wiki )
[x] Code coverage has not gone down and all code touched or added is covered.

In rare situations, this may not be possible or applicable to a PR. In those situations:

Note why this could not be done or is not applicable here:
Add TODOs in the code noting that it requires a test
Add a JIRA task to add the test and link it here:

Branch
Back End Coverage
Front End Coverage

bonnie-v3.1
[Paste Output Here]
[Paste Screenshot Here]

rails_4.2.11_update
2226 / 2487 LOC (89.51%) covered.

[x] Automated regression test(s) pass N/A

If JIRA tests were used to supplement or replace automated tests:

[x] JIRA test links:
[x] Justification for using JIRA tests:
[x] JIRA tests have been added to sprint

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[x] JIRA tests have been run and pass
[x] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[x] JIRA tests have been run and pass
[x] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Teaspoon timing out but tests pass locally.


Update submodule version for Chakra to the lastest

Summary
ASTRA-Sim currently uses an outdated version of Chakra as its external module, resulting in improper support for newer Chakra traces.
Two specific issues have been identified:

Chakra does not encode involved_dim in the trace, but ASTRA-Sim requires it.
The is_cpu_op() method in the ET feeder node always returns '0' after Chakra's schema update (This commit from Chakra Repo).

This PR addresses these issues by:

Updating the submodule version for Chakra to the latest (July 17th).
Updating the include paths according to the latest Chakra structure.
Ensuring that involved_dim always includes all GPU nodes.

Test Plan
Resnet-50 (newly collected)
resnet-50.zip
Batch 16
./build/astra_analytical/build/bin/AstraSim_Analytical_Congestion_Unaware --workload-configuration=/home/un-gpu/Project/jpark/astra-sim/resnet-50/result-batch16/rank --system-configuration=./inputs/system/Ring.json --network-configuration=./inputs/network/analytical/Ring.yml --remote-memory-configuration=./inputs/remote_memory/analytical/no_memory_expansion.json

Batch 32
./build/astra_analytical/build/bin/AstraSim_Analytical_Congestion_Unaware --workload-configuration=/home/un-gpu/Project/jpark/astra-sim/resnet-50/result-batch32/rank --system-configuration=./inputs/system/Ring.json --network-configuration=./inputs/network/analytical/Ring.yml --remote-memory-configuration=./inputs/remote_memory/analytical/no_memory_expansion.json

Batch 64
./build/astra_analytical/build/bin/AstraSim_Analytical_Congestion_Unaware --workload-configuration=/home/un-gpu/Project/jpark/astra-sim/resnet-50/result-batch64/rank --system-configuration=./inputs/system/Ring.json --network-configuration=./inputs/network/analytical/Ring.yml --remote-memory-configuration=./inputs/remote_memory/analytical/no_memory_expansion.json

inputs/network/analytical/Ring.ym
 # 64 NPUs
 npus_count: [ 2 ]  # number of NPUs

Result
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
sys[0] finished, 297912000 cycles
sys[1] finished, 305405000 cycles

ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
sys[1] finished, 570182000 cycles
sys[0] finished, 571099000 cycles

ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
ring of node 0, id: 0 dimension: local total nodes in ring: 2 index in ring: 0 offset: 1total nodes in ring: 2
sys[1] finished,<PHONE_NUMBER> cycles
sys[0] finished,<PHONE_NUMBER> cycles

Following this PR (https://github.com/astra-sim/astra-sim/pull/196), I have updated cleanup code in build.sh
./build/astra_analytical/build.sh -l

One more: Do you know the history behind changing how attribute values are fed in et_feeder?
For example, for the attribute comm_size, we used to be able to feed all the values regardless of whether attr.value was uint64 or int64, or int32, etc (link). But now, if the value is not a type int64, et_feeder will feed in a value of 0 (link)
I'm not sure what the python profiler uses, but both the et_generator and SGT uses type uint64.
The key takeaway is that unless we have a way to force all trace producing tools to use uint64 for comm_size, this will be a problem.

Split this item into a new comment:
Unfortunately, with 2D, 3D communication, involved_dim needs to be [True, True] or [True, True, True], instead of just [True]. This current fix will only result in a 1D communication. I'll have to think of a way to go around this.

Hi,
1.

Hi @JoongunPark , thanks for the update!

I editited your PR description to include the commit link where the is_cpu_op schema has been updated.
Did you make any changes in the codebase to address the issue No.2 in the PR description? (issue of is_cpu_op always returning 0)
Maybe this belongs to a separate thread. Do you think et_feeder_node.cpp should not set is_cpu_op to 1 as default? (here) As far as I can see, with the curren state, et_feeder will always force is_cpu_op to 1  (link). Even if the Chakra node is a COMM node, if is_cpu_op is set to 1, astra-sim's workload layer will treat this as a COMP node. Traces created through pytorch converter is okay, but those created with other tools (MSCCL->Chakra, SGT, etc.) need to continuously mark is_cpu_op to 0 .
One quick fix to the above item could be to adjust the order of if statements in Workload.cc so that comm comes before comp.

Thanks for the update!
Yes. The error stems from different type between trace ETFeeder. Updating ETFeeder will solve the problem.
Semntaically 'Comm' should not be is_cpu_op=true . You can check it here that only gpu_op can be COMM nodes (https://github.com/mlcommons/chakra/blob/d5c68023eac8147bad3c9bda8a8d93545b8961fa/src/converter/pytorch_converter.py#L329).
I haven't seen such case yet. As we can see in the 3. That should not happen. I prefer to report that as a bug to Chakra and fix that if that happens.

One more: Do you know the history behind changing how attribute values are fed in et_feeder? For example, for the attribute comm_size, we used to be able to feed all the values regardless of whether attr.value was uint64 or int64, or int32, etc (link). But now, if the value is not a type int64, et_feeder will feed in a value of 0 (link) I'm not sure what the python profiler uses, but both the et_generator (link) and SGT (link) uses type uint64. The key takeaway is that unless we have a way to force all trace producing tools to use uint64 for comm_size, this will be a problem.

Yes. That is the similar problem that I mentioned with is_cpu_op(). The root cause is strong typing in ETFeeder. In order to fix this, we can update schema in Chakra or some additional logic that enforce operations to have expected type. One immediate solution is giving the expected data type from other upstream projects (MSCCL->Chakra, SGT, etc.).

Split this item into a new comment:
Unfortunately, with 2D, 3D communication, involved_dim needs to be [True, True] or [True, True, True], instead of just [True]. This current fix will only result in a 1D communication. I'll have to think of a way to go around this.

I think this is really good point. Using involved_dim=[true] doesn’t make sense in those cases.
We may consider providing users with the option to choose either involved_dim or ProcessGroup until we fully implement PG support in ASTRA-Sim.

Just checked, LGTM!

Leaving behind a bit of summarized history for the history diggers:

ET producing tools (et_converter, et_generator, SGT, etc.) were using, e.g., uint64 as the attribute type for comm_size when generating binary protobuf ET files. Previously, the ET Feeder had a separate logic to parse this using soft type conversion, so that a uint64 comm_size in protobuf binary would be converted into the ETFeederNode class' int comm_size member variable. However, since an update in ETFeeder, we now have strong type conversion, the uint64 value was silently ignored. Our resolution was to fix this in the ET producing tool stage, not at the ETFeeder stage or the ASTRA-sim stage

Because the new ETFeeder supports get_other_attr(), even if ET producers encode a custom attribute (i.e. involved_dim), the ASTRA-sim code is able to use the function ETFeeder.get_other_attr() to access the involved_dim attribute.


Question about  Code for  resnet50, vgg16, and MobileNetV3

Hi，author！
Thank you for your outstanding contribution! Recently, I want to learn more about your work by running the code.
May I ask if you could upload the resnet50, vgg16, and MobileNetV3 code for reproducing ImageNet? I would greatly appreciate it for this.
Thanks！

Thank you for your attention in our work.
We upload the evaluation code for ImageNet with those architectures.


bbl-up task doesn't work with specified Docker image

We tried to use the bbl-up task with the Docker image it specifies, and got a huge error message when bbl drove bosh-init to do something involving Ruby.
Adding:
RUN apt-get install -y build-essential zlibc zlib1g-dev \
        ruby ruby-dev openssl libxslt-dev libxml2-dev \
        libssl-dev libreadline6 libreadline6-dev libyaml-dev \
        libsqlite3-dev sqlite3

to the Dockerfile and using that custom image fixed things.  That apt-get command matches the bosh-init installation docs.
Since the pipeline jobs in runtime-ci are not triggered by anything, including daily or weekly resources, it appears this error may never have been caught.
/cc @fushewokunze-pivotal @dsabeti @anEXPer

Hey @Amit-PivotalLabs,
Can you please share the error message you saw?  We just re-ran the task against one of our environments and it succeeded at running bbl up against the existing environment (which I thought should fail if bosh-init weren't properly installed).
Thanks!
Josh

https://gist.github.com/Amit-PivotalLabs/bfbae8b57686bedf3ddb0e821d1dc48c
On Sun, Feb 19, 2017 at 5:35 PM, Josh Aresty<EMAIL_ADDRESS>wrote:

Hey @Amit-PivotalLabs https://github.com/Amit-PivotalLabs,
Can you please share the error message you saw? We just re-ran the task
https://runtime.ci.cf-app.com/teams/main/pipelines/cf-deployment/jobs/setup-infrastructure-fresh/builds/53
against one of our environments and it succeeded at running bbl up
against the existing environment (which I thought should fail if bosh-init
weren't properly installed).
Thanks!
Josh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/cf-deployment-concourse-tasks/issues/7#issuecomment-280968086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC9t3veyIUYKKXVpgUCooGXmGFK8zN_iks5reO37gaJpZM4MFpNP
.

Ok, I just tried this from the docker image on my own and it worked just fine. However, I did notice that most local package compilation gets skipped, including the ruby package:
Started validating
  Downloading release 'bosh'... Finished (00:00:27)
  Validating release 'bosh'... Finished (00:00:12)
  Downloading release 'bosh-google-cpi'... Finished (00:00:13)
  Validating release 'bosh-google-cpi'... Finished (00:00:05)
  Validating cpi release... Finished (00:00:00)
  Validating deployment manifest... Finished (00:00:00)
  Downloading stemcell... Finished (00:00:00)
  Validating stemcell... Finished (00:00:00)
Finished validating (00:01:00)

Started installing CPI
  Compiling package 'golang/b7c20853a73ad56fad8d60b980503e22d3ac7f43'... Finished (00:00:30)
  Compiling package 'bosh-google-cpi/2334a22dc4536f3bd86a8cd97e0127a5dfb86249'... Finished (00:00:23)
  Installing packages... Finished (00:00:04)
  Rendering job templates... Finished (00:00:00)
  Installing job 'google_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:59)

Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-google-kvm-ubuntu-trusty-go_agent/3312.15'... Finished (00:01:05)

Started deploying
  Creating VM for instance 'bosh/0' from stemcell 'stemcell-6634af8a-ef43-40d4-4a66-e46d5f187590'... Finished (00:01:00)
  Waiting for the agent on VM 'vm-ec4e42a1-b6ab-498b-498c-017f6776bf19' to be ready... Finished (00:00:22)
  Creating disk... Finished (00:00:03)
  Attaching disk 'disk-dc58dcd1-cf70-43c0-6c09-dfd4926e4ed0' to VM 'vm-ec4e42a1-b6ab-498b-498c-017f6776bf19'... Finished (00:00:23)
  Rendering job templates... Finished (00:00:05)
  Compiling package 'ruby/589d4b05b422ac6c92ee7094fc2a402db1f2d731'... Skipped [Package already compiled] (00:00:02)
  Compiling package 'golang/b7c20853a73ad56fad8d60b980503e22d3ac7f43'... Finished (00:00:55)
  Compiling package 'mysql/b7e73acc0bfe05f1c6cbfd97bf92d39b0d3155d5'... Skipped [Package already compiled] (00:00:02)
  Compiling package 'libpq/09c8f60b87c9bd41b37b0f62159c9d77163f52b8'... Skipped [Package already compiled] (00:00:02)
  Compiling package 's3cli/8cbc6ee1b5acaac18c63fafc5989bd6911c9be83'... Skipped [Package already compiled] (00:01:20)
  Compiling package 'davcli/5f08f8d5ab3addd0e11171f739f072b107b30b8c'... Skipped [Package already compiled] (00:00:01)
  Compiling package 'nats/0155cf6be0305c9f98ba2e9e2503cd72da7c05c3'... Skipped [Package already compiled] (00:00:05)
  Compiling package 'health_monitor/6f71f76cfa6e85f14fe22a2114f6b3de73fe531d'... Skipped [Package already compiled] (00:00:07)
  Compiling package 'nginx/21e909d27fa69b3b2be036cdf5b8b293c6800158'... Skipped [Package already compiled] (00:00:01)
  Compiling package 'bosh-google-cpi/2334a22dc4536f3bd86a8cd97e0127a5dfb86249'... Finished (00:00:21)
  Compiling package 'postgres/4b9f6514001f7c3f7d4394920d6aced9435a3bbd'... Skipped [Package already compiled] (00:00:02)
  Compiling package 'registry/cf4e7bab4ca7d90bb18efa1451d7fa264b0b015b'... Skipped [Package already compiled] (00:00:06)
  Compiling package 'director/3b9f26bdc74c7b6b439577c1e4b2cf1941fe58c3'... Skipped [Package already compiled] (00:00:08)
  Updating instance 'bosh/0'... Finished (00:00:18)
  Waiting for instance 'bosh/0' to be running... Finished (00:00:16)
  Running the post-start scripts 'bosh/0'... Finished (00:00:00)
Finished deploying (00:05:51)

It seems to me that it's totally possible that we have a regression in this image, but that we haven't seen this in our pipelines because we end up skipping ruby compilation.
@cppforlife: When bosh-init says Skipped [Package already compiled], how can I find out where the package is cached? Keep in mind, this inside of a fresh docker image, so it seems like it couldn't be on the local file system. Is there a way to force bosh-init to re-compile the package?
Also, @Amit-PivotalLabs, what IaaS were you using? AWS? Another thing I'm noticing is that the GCP CPI is written golang, but the AWS CPI is written in Ruby. It could be an important factor as well. I'll take another stab at this tomorrow.

AWS. Good catch, that may be it. Do any cf-deployment jobs happen to be on
AWS?
Amit
On Sun, Feb 19, 2017 at 7:26 PM David Sabeti<EMAIL_ADDRESS>wrote:

Ok, I just tried this from the docker image on my own and it worked just
fine. However, I did notice that most local package compilation gets
skipped, including the ruby package:
Started validating
Downloading release 'bosh'... Finished (00:00:27)
Validating release 'bosh'... Finished (00:00:12)
Downloading release 'bosh-google-cpi'... Finished (00:00:13)
Validating release 'bosh-google-cpi'... Finished (00:00:05)
Validating cpi release... Finished (00:00:00)
Validating deployment manifest... Finished (00:00:00)
Downloading stemcell... Finished (00:00:00)
Validating stemcell... Finished (00:00:00)
Finished validating (00:01:00)
Started installing CPI
Compiling package 'golang/b7c20853a73ad56fad8d60b980503e22d3ac7f43'... Finished (00:00:30)
Compiling package 'bosh-google-cpi/2334a22dc4536f3bd86a8cd97e0127a5dfb86249'... Finished (00:00:23)
Installing packages... Finished (00:00:04)
Rendering job templates... Finished (00:00:00)
Installing job 'google_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:59)
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-google-kvm-ubuntu-trusty-go_agent/3312.15'... Finished (00:01:05)
Started deploying
Creating VM for instance 'bosh/0' from stemcell 'stemcell-6634af8a-ef43-40d4-4a66-e46d5f187590'... Finished (00:01:00)
Waiting for the agent on VM 'vm-ec4e42a1-b6ab-498b-498c-017f6776bf19' to be ready... Finished (00:00:22)
Creating disk... Finished (00:00:03)
Attaching disk 'disk-dc58dcd1-cf70-43c0-6c09-dfd4926e4ed0' to VM 'vm-ec4e42a1-b6ab-498b-498c-017f6776bf19'... Finished (00:00:23)
Rendering job templates... Finished (00:00:05)
Compiling package 'ruby/589d4b05b422ac6c92ee7094fc2a402db1f2d731'... Skipped [Package already compiled] (00:00:02)
Compiling package 'golang/b7c20853a73ad56fad8d60b980503e22d3ac7f43'... Finished (00:00:55)
Compiling package 'mysql/b7e73acc0bfe05f1c6cbfd97bf92d39b0d3155d5'... Skipped [Package already compiled] (00:00:02)
Compiling package 'libpq/09c8f60b87c9bd41b37b0f62159c9d77163f52b8'... Skipped [Package already compiled] (00:00:02)
Compiling package 's3cli/8cbc6ee1b5acaac18c63fafc5989bd6911c9be83'... Skipped [Package already compiled] (00:01:20)
Compiling package 'davcli/5f08f8d5ab3addd0e11171f739f072b107b30b8c'... Skipped [Package already compiled] (00:00:01)
Compiling package 'nats/0155cf6be0305c9f98ba2e9e2503cd72da7c05c3'... Skipped [Package already compiled] (00:00:05)
Compiling package 'health_monitor/6f71f76cfa6e85f14fe22a2114f6b3de73fe531d'... Skipped [Package already compiled] (00:00:07)
Compiling package 'nginx/21e909d27fa69b3b2be036cdf5b8b293c6800158'... Skipped [Package already compiled] (00:00:01)
Compiling package 'bosh-google-cpi/2334a22dc4536f3bd86a8cd97e0127a5dfb86249'... Finished (00:00:21)
Compiling package 'postgres/4b9f6514001f7c3f7d4394920d6aced9435a3bbd'... Skipped [Package already compiled] (00:00:02)
Compiling package 'registry/cf4e7bab4ca7d90bb18efa1451d7fa264b0b015b'... Skipped [Package already compiled] (00:00:06)
Compiling package 'director/3b9f26bdc74c7b6b439577c1e4b2cf1941fe58c3'... Skipped [Package already compiled] (00:00:08)
Updating instance 'bosh/0'... Finished (00:00:18)
Waiting for instance 'bosh/0' to be running... Finished (00:00:16)
Running the post-start scripts 'bosh/0'... Finished (00:00:00)
Finished deploying (00:05:51)
It seems to me that it's totally possible that we have a regression in
this image, but that we haven't seen this in our pipelines because we end
up skipping ruby compilation.
@cppforlife https://github.com/cppforlife: When bosh-init says Skipped
[Package already compiled], how can I find out where the package is
cached? Keep in mind, this inside of a fresh docker image, so it seems like
it couldn't be on the local file system. Is there a way to force bosh-init
to re-compile the package?
Also, @Amit-PivotalLabs https://github.com/Amit-PivotalLabs, what IaaS
were you using? AWS? Another thing I'm noticing is that the GCP CPI is
written golang, but the AWS CPI is written in Ruby. It could be an
important factor as well. I'll take another stab at this tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/cf-deployment-concourse-tasks/issues/7#issuecomment-280979532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC9t3oZUSXW--1zl_ey8G93fdCR7tJ-Lks5reQfRgaJpZM4MFpNP
.

Yeah, but we haven't run that job in a month: https://runtime.ci.cf-app.com/teams/main/pipelines/cf-deployment/jobs/setup-infrastructure-upgrade/builds/15.
My guess is that if we re-bootstrapped that environment, it would fail.

I just built a test pipeline for this and it does fall on AWS.
2017年2月19日(日) 19:29 David Sabeti<EMAIL_ADDRESS>
Yeah, but we haven't run that job in a month:
https://runtime.ci.cf-app.com/teams/main/pipelines/cf-deployment/jobs/setup-infrastructure-upgrade/builds/15
.
My guess is that if we re-bootstrapped that environment, it would fail.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/cf-deployment-concourse-tasks/issues/7#issuecomment-280979938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQMNEAZKVzlOpddpPnYfweunYEWb2uwks5reQingaJpZM4MFpNP
.

This story was accepted a while ago, so I'll close this issue.


cla: accepted by MatthewLeboffe

Current behavior

Proposed changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

@MatthewLeboffe Thank you for sending this PR. We require that CLA commits must be signed and verified by github.
The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a new PR, this will mark the commit in the new PR as verified.

closing in favor of https://github.com/build-trust/ockam/pull/7088


add profanity check spec example

I just played around with the spec and created one example.
We ask the LLM to translate a statement into English language and using spec we want to ensure the translated statement is profanity-free

@devenbhooshan can you also update setup.py to add alt-profanity-check as an optional dependency?

I have added the required changes @ShreyaR
I don't think I have access to merge the PR.

Ah gotcha, I'll merge the PR in!


Verbose logging

Add in verbose logging option .. along with build times

:+1:

Added verbose logging to the builder.
You can enable it by setting verboseOutput: true in the config.


Problem with path on Azure DevOps

There is a problem with resolving relative path on azure devops from config file.

Azure DevOps linux client is case sensitive. That was the issue. Closing.


Rule: comprehension-term-assignment

Somewhat similar to the unconditional-assignment rule, and also in the style category. I think it would be good to have Regal help simplify comprehensions where the last expression is a simple assignment to a term variable, and suggest moving the value directly to the comprehension head instead.
Avoid
to_string(ref) := concat(".", [path |
    some part in ref
    path := part.value
])

Prefer
to_string(ref) := concat(".", [part.value | some part in ref])

Note that while it's often possible to move a lot of code in that direction, like function calls — I don't think that helps readability at all, and so we should stick to recommend this for simple assignment like the example shown above.

Renamed from "tail" assignment to "term" assignment, as detecting simple assignment of a term var elsewhere involves the same check more or less, just peformed over all the expressions. So something like this should be flagged just the same:
Avoid
to_string(ref) := concat(".", [path |
    some part in ref
    path := part.value
    part.type == "string"
])

Prefer
to_string(ref) := concat(".", [part.value |
    some part in ref
    part.type == "string"
])


CreateTable in HIVE connector

Syntax:
CREATE TABLE table_name (col_name data_type, ...)
This feature is disabled by default for the Hive connector.
Enable by setting 'hive.allow-create-table' to 'true'.

@electrum thank you. I've split the PR into 3 commits. comments addressed

@electrum thank you, updated PR

@arhimondr thank you, get comment addressed

Thanks! I made a few changes and put up a new PR: #2622
I removed the allow-create-table setting since we already support creating tables in the Hive connector. Also, creating a table cannot destroy data, so I see no reason for a flag. We only do that for the other features since they can destroy data. If you need this flag, please let me me know and I can put it back.

@electrum thank you. Sure, no need for the flag


Add OneDeploy endpoint for AzureRmWebAppDeployment

Add the logic to send deployment requests to the OneDeploy API for AzureRmWebAppDeployment to consume.

@vincentdass  @vsebesta  @rvairavelu

@dannysongg  we have Azure-rest-rm as a separate common package [https://github.com/microsoft/azure-pipelines-tasks-common-packages/blob/main/common-npm-packages/azure-arm-rest/azure-arm-app-service-kudu.ts]. Can you incorporate the changes here as well ?

@manolerazvan

@dannysongg, please bump the package minor version to 235(current sprint) in both azure-arm-rest and azurermdeploycommon package.json file and Inside package folder build it with "npm i && npm run build".
Thank you.


Transpiled JS file in same DIR is not found in explorer

VSCode Version: 1.1.1
OS Version: Windows 7

Steps to Reproduce:

Created a folder and file ../spec/config/element.spec.ts
Transpiled to same dir via gulp so I now have ../spec/config/element.spec.js:

gulpfile.js
gulp.task("transpile:test", function () {
  var tsResult = tsProjectTest
    .src()
    .pipe(plug.typescript(tsProjectTest))

    tsResult.js
    .pipe(plug.ngAnnotate())
    .pipe(gulp.dest("/spec/"));

  return tsResult.js
    .pipe(gulp.dest("/spec/"));
});

tsconfig.json
{
  "compileOnSave": true,
  "compilerOptions": {
    "noEmitOnError": true,
    "noImplicitAny": false,
    "removeComments": false,
    "outDir": "/spec/",
    "sourceMap": false,
    "target": "es5",
    "watch": true,
    "preserveConstEnums": true
  },
 "exclude": [
    "node_modules",
    "typings/main",
    "typings/main.d.ts"
  ]
}

I can see the JS file in windows explorer and I can search for it (search only found it after exiting VS code and coming back in. A refresh did not work.), but the JS file does not show up in VS code's explorer (I can only see the TS file)

@jmzagorski do you have an files.exclude filter in your settings file that hides *.js files?

well that was dumb of me ha. I must have set that when I was taking the tutorial on VS code way back when. Sorry!


Request for help in identifying objects with "hidden" property in the XML annotation files

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Hi all, I am interested in exporting annotations/labels in the form of PASCAL VOC format and then structure the images with annotations in order to pass the images and labels for training. I am writing a script now to remove annotations with "occluded" and "outside" property flag (mentioned as "occluded" in the annotations files with different formats)
After looking into the cvat documentation, it seems like the "hidden" flag is for visualization purpose, i.e. maybe the bounding box is blocking something else, so the annotator wants to hide it. The hidden flag will not change any property of the annotation. Is it possible to remove the objects that have chosen as "hidden" in the frames ? Is there any property that the objects with "hidden" property has that can enable me to ignore those particular objects in the frames?

Operating System and version (e.g. Linux, Windows, MacOS):
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

After looking into the cvat documentation, it seems like the "hidden" flag is for visualization purpose, i.e. maybe the bounding box is blocking something else, so the annotator wants to hide it. The hidden flag will not change any property of the annotation.

Exactly. Hidden flag on UI is only for best UX of annotators, when they have temporary hide an object. If you update a page, the shape becomes visible.

Is there any property that the objects with "hidden" property has that can enable me to ignore those particular objects in the frames?

From the piece of annotation you provided, I see that you are annotation a video (frame_000001, ...). In this case you need to use Tracks and their outside property. It shows that an object disappears from a frame.
If you are using Shapes to annotate your videos, you need to delete these shapes from corresponding frames in UI.
Do you see any problems with this approach?


GitHub action verified, on market place and available in the tool list

Make our GitHub action a verified action and publish it on market place

See https://github.com/ossf/scorecard/issues/1074#issuecomment-963530845

Done.


Discard devices which have already configured with battery notes in drop-down for adding new device

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
Having many battery-powered devices and adding the last ones, the already configured devices are not relevant here and do 'hide' the not-configured ones.
Describe the solution you'd like
See title
Describe alternatives you've considered
NA
Additional context
NA

Great minds... I suggested this same enhancement to Andrew over on Mastodon yesterday and here's his response: "Unfortunately I don’t get to control that list, it’s built into HA and there’s limited scope for filtering."

As Mike has said, unfortunately I can't fix this, agree it would be really nice to filter it down.  I think it would be hard for HA to provide hooks to that list easily to ever be able to implement this.

Hi,
Maybe you can use this tiny template, witch gives the device_id's of all devices with 'battery_notes' to remove them from the list ?
{{ integration_entities('battery_notes') | map('device_id') | unique | list}}
This gives me the list of all devices witch are linked to battery_notes:
[   "ba0d067b70cd50cd97bcd53ad14cfe5",   "bf1a7cb3305809d2626cd412f84b50",   "373b8ee56e45c00f6f91fe562d6c4a9",   "6c444f5025b886b9255fec07fc827d4",   "a726d5f47dbfc42f8110e1e6a010d05",   "dd37cee8bf63f5e773569b83e0e3ad6",   "0f7dae314b7f36c3a398e2160a4e5b3",   "a20f40cad7cd3d836af48504e58f1c8",   "2aacb8fcb277a5f0277026e7e94d759",   "b5f3cf597f8026590a1464bae9d1d7d",   "1cc94c52d3a35ba6f668f56792cbb99",   "fde3da16c1bf97acf9a06333d001576",   "fd6e33aaf4421fde895a0e2a69f85e4",   "7a36cf72b53cb117ced091fd3849493" ]
I am not at the level of trying this on code level yet, so I propose this to you.

Unfortunately the issue isn't identifying the devices with battery notes but excluding them from the list.
Home Assistant does not support a method to provide a list of device id's to exclude from the devices selector.

@andrew-codechimp Could you be so kind as to point me to the code where you present the devices selector list?
Thanks!

It's here, just above is the definition for all devices if you have that config option set.
https://github.com/andrew-codechimp/HA-Battery-Notes/blob/7363117f22b54c44a45779650662c0f5327d82a4/custom_components/battery_notes/config_flow.py#L58
You'll see it being conditionally used here
https://github.com/andrew-codechimp/HA-Battery-Notes/blob/7363117f22b54c44a45779650662c0f5327d82a4/custom_components/battery_notes/config_flow.py#L161
I've looked into this twice and although entity selector allows exclusions, device selection doesn't, it's an annoying omission from Core.

Okay so this code:
        vol.Required(CONF_DEVICE_ID): selector.DeviceSelector(
            config=selector.DeviceSelectorConfig(
                entity=[
                    selector.EntityFilterSelectorConfig(
                        domain=Platform.SENSOR,
                        device_class=SensorDeviceClass.BATTERY,
                    ),
                    selector.EntityFilterSelectorConfig(
                        domain=Platform.BINARY_SENSOR,
                        device_class=SensorDeviceClass.BATTERY,
                    ),
                ]
            )
        ),

builds a list of sensor & binary_sensor entities whose device_class is battery, correct?
I'm by no means a python programmer but is there not a way to build that list as list_all, then build a list of battery_notes integration entities as list_configured and then use sets subtraction? like new_list=list(set(list_all) - set(list_configured)) and use that new set in the vol.Required(CONF_DEVICE_ID): selector.DeviceSelector() function call?

You can use sets:
main_list = list(set(list_2) - set(list_1))
Output:

list_1=["a", "b", "c", "d", "e"]
list_2=["a", "f", "c", "m"]
set(list_2) - set(list_1)
set(['m', 'f'])
list(set(list_2) - set(list_1))
['m', 'f']
Per @JonClements' comment, here is a tidier version:

list_1=["a", "b", "c", "d", "e"]
list_2=["a", "f", "c", "m"]
list(set(list_2).difference(list_1))
['m', 'f']

So this...
config=selector.DeviceSelectorConfig(
                entity=[
                    selector.EntityFilterSelectorConfig(
                        domain=Platform.SENSOR,
                        device_class=SensorDeviceClass.BATTERY,
                    ),
                    selector.EntityFilterSelectorConfig(
                        domain=Platform.BINARY_SENSOR,
                        device_class=SensorDeviceClass.BATTERY,
                    ),
                ]
            )

might become something like this???
config=selector.DeviceSelectorConfig(
entity=
  list( set( [
              selector.EntityFilterSelectorConfig(domain=Platform.SENSOR, device_class=SensorDeviceClass.BATTERY,),
              selector.EntityFilterSelectorConfig(domain=Platform.BINARY_SENSOR,device_class=SensorDeviceClass.BATTERY,),
             ] ) - set( [BATTERY_NOTES_CONFIGURED_ENTITIES_LIST] )
      )
)

I think it might be doable using the list(set_1 - set_2)!  But then again, I don't know python!

I've had a look into this in more detail, your python suggestion was sound, it's the implementation of DeviceSelectorConfig thats the problem.
The entity parameter does not take a list of entities (it's naming is very confusing), but rather a list of EntityFilterSelectorConfig's, this is a small class which only allows filter definitions that are very limited in scope (integration, domain, device class and supported features), which is what I'm using to filter to only devices with batteries.
The options available to integrations mirrors what is available to blueprints here, you'll see that further down the entity selector has specific parameters for included_entities and excluded_entities, this is what is missing from the device selector, that or included/excluded device id's which I could also make work, but device id's are not user friendly so understand why they are omitted.
I'll always keep an eye on whether these methods change in core, but for now there's no way to filter these.

Thank you for trying, again!  Based on your comment above, I looked at the code again with a different view of things and I can see now that it's like a closed black box into which you're passing which domain and device_class you want it to present.  That's pretty restictive for the programmer to select what should be displayed and, in this case, results in too broad of a selection list that the user should see.
DEVICE_SCHEMA = vol.Schema(
    {
        vol.Required(CONF_DEVICE_ID): selector.DeviceSelector(
            config=selector.DeviceSelectorConfig(
                entity=[
                    selector.EntityFilterSelectorConfig(
                        domain=Platform.SENSOR,
                        device_class=SensorDeviceClass.BATTERY,
                    ),
                    selector.EntityFilterSelectorConfig(
                        domain=Platform.BINARY_SENSOR,
                        device_class=SensorDeviceClass.BATTERY,
                    ),
                ]
            )
        ),
        vol.Optional(CONF_NAME): selector.TextSelector(
            selector.TextSelectorConfig(type=selector.TextSelectorType.TEXT),
        )
    }
)

I'm looking now though at the Home Assistant Device Selectors documentation and I can see the options are very limited.
What we need is either an entity_exclude variable , a filter_out variable, or just a single exclude variable with all possible conditions of integration, domain, device_class, supported_features, manufacturer, model.


bug: tags are not clickable

Expected
Tags provide a descriptive and easy way for users to find the sounds they are looking for without having to click through a track list and reading a description. That being said, tags should be clickable.
How To Reproduce Bug

Click on any track on the Home Page.
Click on the tags displayed below the Sound Title (nothing happens when you do)

To-Do

[x] Make tags clickable.

I believe #280 fixed this.


Redirect url?

The installation instructions stipulate:

Enter http://localhost:5000/login/authorized as the Redirect URL, and then choose Save.

but I only get the following three options:

home page url
conditions url
privacy url

I tried to home page url but this did not work.
Am I missing something?
Thanks

Ok found it: the redirection url field is part of the actual web app settings created under

Under Platforms, choose Add platform > Web.

It might help to switch steps 7 and 8 in the current installation.md.


Implement kubernetes caching backend

Fixes #3
Tested with azure-resourcemanager-exporter, using k8scm://opsstack/azure-resourcemanager-exporter-cache/
Kubernetes v1.22 is required as minimum here, since I'm using Server-Side-Apply to managed the data fields separately to resolve any concurrency issues.
Logs:
2023-05-16T16:51:27.523Z        info    collector/cache.go:177  restoring state from cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/resourceHealth.json   {"collector": "resourceHealth"}
2023-05-16T16:51:27.524Z        info    collector/cache.go:177  restoring state from cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/quota.json    {"collector": "quota"}
2023-05-16T16:51:27.524Z        info    collector/cache.go:177  restoring state from cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/general.json  {"collector": "general"}
2023-05-16T16:51:27.527Z        info    collector/cache.go:215  restored state from cache: "k8scm://opsstack/azure-resourcemanager-exporter-cache/general.json" (expiring 2023-05-16 16:51:46.131671796 +0000 UTC)        {"collector": "general"}
2023-05-16T16:51:27.527Z        info    collector/cache.go:215  restored state from cache: "k8scm://opsstack/azure-resourcemanager-exporter-cache/quota.json" (expiring 2023-05-16 16:51:50.984695132 +0000 UTC)  {"collector": "quota"}
2023-05-16T16:51:27.528Z        info    collector/cache.go:215  restored state from cache: "k8scm://opsstack/azure-resourcemanager-exporter-cache/resourceHealth.json" (expiring 2023-05-16 16:51:47.856535755 +0000 UTC) {"collector": "resourceHealth"}
2023-05-16T16:51:27.528Z        info    collector/cache.go:177  restoring state from cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/resource.json {"collector": "resource"}
2023-05-16T16:51:27.535Z        info    collector/cache.go:215  restored state from cache: "k8scm://opsstack/azure-resourcemanager-exporter-cache/resource.json" (expiring 2023-05-16 16:51:46.646073796 +0000 UTC)       {"collector": "resource"}
2023-05-16T16:52:27.591Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/general.json (expiring 2023-05-16 16:53:27.532214593 +0000 UTC)       {"collector": "general"}
2023-05-16T16:52:28.017Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/resource.json (expiring 2023-05-16 16:53:27.968933969 +0000 UTC)      {"collector": "resource"}
2023-05-16T16:52:30.334Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/resourceHealth.json (expiring 2023-05-16 16:53:30.188369511 +0000 UTC)        {"collector": "resourceHealth"}
2023-05-16T16:52:32.828Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/quota.json (expiring 2023-05-16 16:53:32.816557471 +0000 UTC){"collector": "quota"}
2023-05-16T16:53:27.674Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/general.json (expiring 2023-05-16 16:54:27.600089385 +0000 UTC)       {"collector": "general"}
2023-05-16T16:53:28.437Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/resource.json (expiring 2023-05-16 16:54:28.376659594 +0000 UTC)      {"collector": "resource"}
2023-05-16T16:53:33.319Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/resourceHealth.json (expiring 2023-05-16 16:54:33.269111721 +0000 UTC)        {"collector": "resourceHealth"}
2023-05-16T16:53:33.363Z        info    collector/cache.go:241  saved state to cache: k8scm://opsstack/azure-resourcemanager-exporter-cache/quota.json (expiring 2023-05-16 16:54:33.324268304 +0000 UTC){"collector": "quota"}

The Kubernetes RBAC role can be restricted to that ConfigMap only and doesn't need higher permissions
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: azure-resourcemanager-exporter
rules:
- apiGroups:
  - ""
  resourceNames:
  - azure-resourcemanager-exporter-cache
  resources:
  - configmaps
  verbs:
  - get
  - patch
  - create
  - update
  - delete

Limitation: The total amount of "cache" is limited to 1MB.

@mblaschke this is ready to review, i tested this on a local build with the latest azure-resourcemanager-exporter-cache from main


WIP - New Benchmarks

@jlandrews This seems like it might be useful - is there anything in particular preventing it from being merged?


Pages shouldn't be statically referenced

Instead of referencing every page manually in the main.go use an automated system like in NextJS.

Fixed by https://github.com/Jaedotmoe/go-jae.fi/commit/e5972ce69d86afba8eb39a8712313c3950c3322f.

Fixed by https://github.com/Jaedotmoe/go-jae.fi/commit/e5972ce69d86afba8eb39a8712313c3950c3322f.


view pdf file online

@Weichao-Chen
The Pull Request title should be more specific than "update service.py and article.html".
It is more interesting to know what you updated than which files you updated.
Hui

@spm2020spring @Weichao-Chen
Please check this pull request by Ward, and verify that both changes aren't the same.


Fix: winuser | DestroyWindow

This PR updates the Windows winuser Drop implementation to use winuser::DestroyWindow(...) instead of winuser::CloseWindow(...). According to the docs, CloseWindow() "Minimizes (but does not destroy) the specified window.".  This should allow the Window to be properly destroyed once it falls out of scope.
I have also added a small example cargo run --example drop that tests the behavior. Feel free to remove this if not needed. Have left it there in case it was helpful to quickly test this behavior across other OS.

Thanks! I think I will remove the example as it isn't really needed.


Development with ng serve gets "stuck" with $localize error when using i18n attributes and localize option set to sourceLocale

Which @angular/* package(s) are the source of the bug?
localize, Don't known / other
Is this a regression?
Yes
Description
Calling ng serve with a configuration that uses the "localize" option set to the sourceLocale (mine is 'de-AT'),
for example ng serve  --browserTarget=my-app:build:development,locale-de-at
will lead to a false $localize error message and forces you to delete .angular cache and restart ng serve.
Worked in v13.0.3 but will only show incorrect error message during development in v13.1.0+
Please provide a link to a minimal reproduction of the bug
https://gist.github.com/reifi/a7528447fb5aca26b34097d2ef03f46f
Please provide the exception or error you saw
ERROR Error: It looks like your application or one of its dependencies is using i18n.
Angular 9 introduced a global `$localize()` function that needs to be loaded.
Please run `ng add @angular/localize` from the Angular CLI.
(For non-CLI projects, add `import '@angular/localize/init';` to your `polyfills.ts` file.
For server-side rendering applications add the import to your `main.server.ts` file.)
    localize Angular
    consts app.component.html:4
    Angular 18

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 13.1.2
Node: 16.13.0
Package Manager: npm 8.1.0
OS: win32 x64

Angular: 13.1.1
... animations, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1301.2
@angular-devkit/build-angular   13.1.2
@angular-devkit/core            13.1.2
@angular-devkit/schematics      13.1.2
@angular/cli                    13.1.2
@schematics/angular             13.1.2
rxjs                            7.4.0
typescript                      4.4.4

Anything else?
After updating to from angular v13.0.3 to v13.1.1 the $localize error appeared every time I accidentally made a mistake during development with ng serve and did not go away until I deleted the .angular directory and restarted ng serve.
I was able to reproduce it with a newly generated app I updated to v13.1.1.
https://gist.github.com/reifi/a7528447fb5aca26b34097d2ef03f46f

Add i18n @angular/localize to newly generated app (I upgraded from 13.0.3 to 13.1.1)

configure i18n with localize profiles in  angular.json

    "i18n": {
      "locales": {
        "it": {
          "translation": "messages.it.xlf"
        }
      },
      "sourceLocale": {
        "code": "de-AT"
      }
    },
    ...
   "configurations": {
          "locale-it": {
            "localize": [
              "it"
            ]
          },
          "locale-de-at": {
            "localize": [
              "de-AT"
            ]
          }
   },....

add some tag with i18n attribute or use this app.component.html

Start development with ng serve  --browserTarget=my-app:build:development,locale-de-at
Change something that leads to an error in app.component.html and save it so error will be shown in browser
Change it back and fix error -> $localize error will be shown in console and can only be fixed by deleting .angular directory.

Using ng serve  --browserTarget=my-app:build:development,locale-it (using localize 'it') works, probably because it's not the sourceLocale.
Workaround:
Using ng serve  --browserTarget=my-app:build:development,locale-de-at (using localize 'de-AT') does not work, but omitting the 'localize' option like  ng serve  --browserTarget=my-app:build:development does - although probably ignoring additional configuration like baseHref in i18n.
Found differences in cache
The cached content in  .angular/cache/babel-dev-server-i18n/ will change from (for example)
... else {\n      i18n_0 = \"Unter dieser Url ist noch kein websms Partner aktiv\";\n    }
to
... else {\n      i18n_0 = $localize`:@@view.not_found.paragraph.reseller_not_found:Unter dieser Url ist noch kein websms Partner aktiv`;
which leads to the error because "$localize" is not needed during runtime

Trying the obvious to disable the cache as per the documentation does not fix the issue
https://angular.io/cli/cache#enabling-and-disabling-the-cache

@Joren-Thijs-KasparSolutions,
I wasn't able to reproduce the issue using the provided steps
➜  my-app ng serve  --browserTarget=my-app:build:development,locale-de-at
✔ Browser application bundle generation complete.

Initial Chunk Files   | Names         |  Raw Size
vendor.js             | vendor        |   1.95 MB |
polyfills.js          | polyfills     | 339.87 kB |
styles.css, styles.js | styles        | 212.85 kB |
main.js               | main          |   8.15 kB |
runtime.js            | runtime       |   6.85 kB |

                      | Initial Total |   2.50 MB

Build at: 2022-01-10T10:09:52.833Z - Hash: cfc167436488072b - Time: 8570ms

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

✔ Compiled successfully.
✔ Browser application bundle generation complete.

Initial Chunk Files | Names   | Raw Size
main.js             | main    |  8.30 kB |
runtime.js          | runtime |  6.85 kB |

3 unchanged chunks

Build at: 2022-01-10T10:09:53.486Z - Hash: a92f761eb1d3a40a - Time: 347ms

Error: src/app/app.component.html:9:1 - error NG8001: 'uncomment-save-and-comment-save' is not a known element:
1. If 'uncomment-save-and-comment-save' is an Angular component, then verify that it is part of this module.
2. If 'uncomment-save-and-comment-save' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.

9 <uncomment-save-and-comment-save></uncomment-save-and-comment-save>
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  src/app/app.component.ts:5:16
    5   templateUrl: './app.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component AppComponent.

✖ Failed to compile.
✔ Browser application bundle generation complete.

Initial Chunk Files | Names   | Raw Size
main.js             | main    |  8.20 kB |
runtime.js          | runtime |  6.85 kB |

3 unchanged chunks

Build at: 2022-01-10T10:09:59.503Z - Hash: 3e3adaf1c77e6b12 - Time: 133ms

✔ Compiled successfully.

Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

This is the newly created app I used for my step by step descripton:
https://github.com/reifi/my-app


Nuxt-Community Starter Template Fails to Build

Version
1
Reproduction link
https://cl.ly/rr5G
Steps to reproduce
Using node 8.11.2, literally just follow the instructions in the installation guide (https://nuxtjs.org/guide/installation):

vue init nuxt-community/starter-template
cd
npm install
npm run dev

Bam. Errors. Won't load in browser.
What is expected ?
It should build without errors and serve me the default start page at http://localhost:3000
What is actually happening?
I get several build errors stating "Module build failed: Error: No parser and no file path given, couldn't infer a parser" and the site won't load.
Additional comments?
This starter template is surprisingly old considering how much activity has happened with both Nuxt and Vue over that same span of time, particularly with vue-clie@3. I might be speaking out of line, but does this thing need to be updated?

This bug report is available on Nuxt.js community (#c51)

@dohomi hello ,I also have the same problem,
I am in China，Today suddenly initialized template error

https://github.com/vuejs/component-compiler-utils/issues/15
i guess its already fixed
https://www.npmjs.com/package/@vue/component-compiler-utils
1.3.1 43 minutes ago

Thanks @aldarund! I didn’t see that. Happy to see that this has traction on a holiday weekend. Some use the time to BBQ and celebrate with family (I am fortunate to be in this camp), and others either “working” by choice, or the less fortunate being forced to work through this minutiae. Whatever the case is for @pwang2, thank you!

@albanm I still have a mistake

@warriorBrian reinstall packages

@aldarund I tried to remove node_modules, but it still does not work, so I changed module:npm install<EMAIL_ADDRESS>to version 1.12.1. I don't know whether this should be the case all the time.

@warriorBrian using @vue/component-compiler-utils 1.3.1 instead of previous version will work too

@aldarund Thank you, although I can't successfully apply @vue/component-compiler-utils to solve this problem, but I hope the official can give the latest solution. Thank you.

Hi.
I reinstall all of packages everywhere and I still have error, but if I install prettier 1.12 it works. This need to fix.

Same issue here, reinstalling packages didn't help.
Seems like this commit was the fix vuejs/component-compiler-utils@598224dbddc607b8a834f80e991548959a8a19e9 , but even though vue-loader package was updated 8 hours ago the issue still persists.
Tried cleaning npm cache with npm cache clean --force didn't help.
Maybe it's npm's server internal cache.
If you search node_modules for line from the commit with the fix
      code = prettier.format(code, { semi: false })

you'll find it in file node_modules/vue-loader/lib/template-compiler/index.js line 80
replacing it with this
      code = prettier.format(code, { semi: false, parser: 'babylon' })

will fix all errors.

@n1kk  @sadrbox
https://github.com/nuxt/nuxt.js/issues/3385#issuecomment-392569463
https://github.com/nuxt/nuxt.js/issues/3385#issuecomment-392588152

😀. @brandonaaskov  I was surprised to be mentioned here.  For my case, I was enjoying some peaceful time since I have backup to take care of my 👶🏻boy over the weekend and it was an 100F hot humid afternoon.
The issue has affected a few tools, projects in the eco system.  AFAIK, there are

projects using vue-cli
projects using nuxt
project using vue-loader (v14 and v15)

You might want to see my latest update here.
vue-loader v14/v13 also need to be updated with an explicit parser in code.  I have send 2 more simple PR to vue-loader to fix this.

hi @brandonaaskov, the submodules have been fixed :)
Can you recheck your issue and close if solved ?

@NicoPennec, confirmed! Thanks again all!

Hi, I've just done a fresh install like the OP did. There's no error now, but there are a lot of warning messages repeating the following text:
No parser and no filepath given, using 'babylon' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be inferred.
The same messages repeat a lot of times and almost filled up all my screen. However, the compile was successful without error.
Is anyone seeing the same warning message? Is it harmful or can we safely ignore them?

@ausir0726 Thanks. Thought it was the template problem so I didn't checkout the nuxt issue. Very excited about the 2.0 release.

I have this issue as well. Have used nuxt previously without any issue. I've used nuxt in prior projects, but am working on a fresh one and just got faced with this error when running npm run start for the first time:
Stephens-MacBook-Pro-2:CLIENT_DIR stephentetreault$ npm run start

><EMAIL_ADDRESS>start /Users/stephentetreault/git/ORG/CLIENT/CLIENT_DIR/CLIENT_PROJECT
> nuxt start

/Users/stephentetreault/git/ORG/CLIENT/CLIENT_DIR/CLIENT_PROJECT/node_modules/nuxt/lib/core/middleware/nuxt.js:72
      const policies = this.options.render.csp.policies ? {...this.options.render.csp.policies} : null
                                                           ^^^

SyntaxError: Unexpected token ...
    at createScript (vm.js:74:10)
    at Object.runInThisContext (vm.js:116:10)
    at Module._compile (module.js:533:28)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/stephentetreault/git/ORG/CLIENT/CLIENT_DIR/CLIENT_PROJECT/node_modules/nuxt/lib/core/renderer.js:19:24)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `nuxt start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Misc:
Node: v8.2.1
NPM: v6.1.0

@tetreault  node >=8.4 is required for Nuxt
your current version doesn't support spread operator.

Yes i see why now @NicoPennec and I've remedied my issue. In a prior comment on another issue thread for nuxt i also asked this question: is it wise for nuxt to require a higher version of node than the current Node LTS? The nodejs site recommends v8.11.2 for current LTS, so why not peg your compatibility to the current LTS of node, rather than one just slightly higher than the LTS. You'd sure have more reach this way. Just some food for thought.

@NicoPennec you edited your comment to refer me to the latest LTS for node, which is 8.11.2, which by your own words doesnt support the spread operator.


[OPT] 1-D OPT model with fused MHA

This PR adds an 1-D OPT model implementation. See test_1d.py for model inputs and output.
Some highlights:

The model uses the fused kernel from ft_mha. The corresponding repo should be included in alpa-project, but it's not publicly available now.
With the fused MHA kernel, we still have to update the attention cache. I haven't implemented it because I haven't figured out how.
Currently I verified that the output of a batch of prompts from both 1D and 2D model are identical, so does the cache shape. However, based on 2, I commented out the cache value checking.

Tested with 1d-mmha-op commit 50847e4.
1D Batch 1 (prompt * 3) done
2D Batch 1 (prompt * 3) done
Verifying results...passed
1D Batch 2 (prompt * 2, decoding * 3) done
2D Batch 2 (prompt * 2, decoding * 3) done
Verifying results...passed
1D Batch 3 (decoding * 5) done
2D Batch 3 (decoding * 5) done
Verifying results...passed
1D Batch 4 (decoding * 5) done
2D Batch 4 (decoding * 5) done
Verifying results...passed
1D Batch 5 (decoding * 5) done
2D Batch 5 (decoding * 5) done
Verifying results...passed
1D Batch 6 (decoding * 5) done
2D Batch 6 (decoding * 5) done
Verifying results...passed
1D Batch 7 (decoding * 5) done
2D Batch 7 (decoding * 5) done
Verifying results...passed

@comaniac since this is non-interruptive for any existing code/service, let's merge it first.
The only problem with this PR is that it will trigger JAX JIT each time when it starts

@comaniac please rebase and merge


stylize doesn't support windows

I suggest to use https://pypi.org/project/clang-format/ and https://pypi.org/project/black/ (or https://pypi.org/project/yapf/ if you prefer) for formatting directly. Both can be pip installed and don't require further apt or brew installs since clang-format offers wheels with the necessary binaries.

pre-commit supports formatting with clang-format and black https://github.com/pablocael/pynear/pull/36
makefile still uses stylize however


prost_build does not work on no_std

Hi
I am trying to use prost in a no_std target. Everything works great, except that build.rs, which uses prost_build::compile_protos, does not work as it relies on std:
error[E0463]: can't find crate for `std`
 --> src/vendor/getrandom/src/error_impls.rs:8:1
  |
8 | extern crate std;
  | ^^^^^^^^^^^^^^^^^ can't find crate
  |

(via prost-build -> tempfile -> rand -> getrandom).
The funny thing is that compiling the .proto files does not actually depend on my target, as it's a build-step and could be done on std.
In fact this is how I currently work around it: I can compile the .proto files fine if I compile my project on a standard std target, and then copy the resulting .rs files from the build directory and add it directly to my project.
It would be really good to fix up prost-build to run on no_std also, OR to provide a CLI tool which I can run to manually generate the .rs file outside of build.rs.

I assume you are using unreleased prost from git?  Anyway, this is more-or-less expected.  I don't do much no-std work with Rust, but my understanding was that most of the time you cross-compiled to the target platform, as getting rustc and/or cargo to run in the no-std environments was next to impossible.  When cross-compiling I don't think it should matter that a build dependency requires std?

I assume you are using unreleased prost from git?

Yes exactly.

When cross-compiling I don't think it should matter that a build dependency requires std?

This is what I expected, and yet it seems that build.rs also uses no_std if I cross compile to a no_std target, somehow.
Anyway, in this case I guess I'll close this and just use a handrolled CLI tool that calls prost_build::compile_protos(), and run this outside of Rust's build.rs infrastructure. Thanks.

When cross-compiling I don't think it should matter that a build dependency requires std?

This is what I expected, and yet it seems that build.rs also uses no_std if I cross compile to a no_std target, somehow.

For the record, this is a bug and tracked here:
https://github.com/rust-lang/cargo/issues/7915
It is resolved on nightly with an unstable feature. Let's hope it will stabilize soon.

I am also experiencing this issue.  I am trying to use prost in an embedded application (ARM M4), and have to build the data structures in a separate script.  The issue is still there with nightly.  Do I need something special in my Cargo.toml file to tell Cargo it can use std in the build dependencies?


Add experimental xfn using Crossplane composition format to manage "iterable" resources

I got a link to https://github.com/negz/xfns/pull/1 after posting a question on the Crossplane Slack.  So here it goes. 😸 My goal is not to get this PR merged. Partly because the function is far from feature complete, and was built to solve a particular use case in our organization. But the main reason is that we would love to avoid having to use a composition function to do this, and hope that our use case someday will be possible to fulfill with standard Crossplane compositions. But for now, this experimental function might serve as an inspiration to the community.
The function implementation is not pretty code. It was written to work in our use case, and that's it. Still very fresh, and developed as part of our ongoing POC using Crossplane to provision Kafka topics in our multi-tenant setup. Not production ready!
Since the function uses the standard Crossplane composition format to control the composition of resources, we could probably reuse more code from Crossplane. But we are not that familiar with the Crossplane codebase, and some code is kept internal to Crossplane (for good reasons) and impossible to reuse here.

@negz I know you are very busy, but did you have a chance to take a look at this? Could it make sense to create an issue (in Crossplane) proposing "nested compositions" for iterable/array fields in XRD/XRC? It would probably require a design document, but I don't want to waste time on something that will probably never be accepted by Crossplane maintainers. I ask because I have a feeling iterations were intentionally left out of the initial Crossplane composition design. What is your gut feeling?

I ask because I have a feeling iterations were intentionally left out of the initial Crossplane composition design. What is your gut feeling?

Yes, they were. I think it's unlikely we'll ever extend the P&T implementation to support iteration. We get a lot of feedback about how hard to use P&T Compositions are, and I think turning them into even more of a programming language will only make that worse.
That said, I am personally excited about implementing contemporary P&T style Composition as a function, which would allow folks to experiment with features like this without needing changes to Crossplane core.


Issues with TLS inside dlite virtual machine.

I started to investigate this after my gem install failed in my docker build with dlite:
ERROR:  Could not find a valid gem 'rspec' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read server session ticket A (https://api.rubygems.org/specs.4.8.gz)

Then I tried https in dlite:
$ ssh<EMAIL_ADDRESS>DhyveOS version 2.2.0
Docker version 1.10.0, build 590d5108
$ wget https://rubygems.org/
Connecting to rubygems.org (<IP_ADDRESS>:443)
wget: can't execute 'ssl_helper': No such file or directory
wget: error getting response: Connection reset by peer

dlite has been working perfectly until today I started to see these errors. I can't even use:
ADD https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2 /tmp/

in my dockerfiles.

Your base image probably lacks CA certificates. Try installing
"ca-certificates", "libssl" or "openssl".
On Thursday, March 3, 2016, Onni Hakala<EMAIL_ADDRESS>wrote:

I started to investigate this after my gem install failed in my docker
build with dlite:
ERROR:  Could not find a valid gem 'rspec' (>= 0), here is why:
Unable to download data from https://rubygems.org/ - SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read server session ticket A (https://api.rubygems.org/specs.4.8.gz)
Then I tried https in dlite:
$ ssh<EMAIL_ADDRESS>DhyveOS version 2.2.0
Docker version 1.10.0, build 590d5108
$ wget https://rubygems.org/
Connecting to rubygems.org (<IP_ADDRESS>:443)
wget: can't execute 'ssl_helper': No such file or directory
wget: error getting response: Connection reset by peer
dlite has been working perfectly until today I started to see these
errors. I can't even use:
ADD https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2 /tmp/
in my dockerfiles.
—
Reply to this email directly or view it on GitHub
https://github.com/nlf/dlite/issues/130.

--
Rui Marinho

My baseimage might have issues as well but this seems to be related in dlite. The same dockerfile was building perfectly in hub.docker.com.

Even destroying the box and starting a new one didn't resolve this for me.
$ docker-compose build
db uses an image, skipping
Building web
Step 1 : FROM alpine:edge
Pulling repository docker.io/library/alpine
ERROR: Service 'web' failed to build: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/alpine/images. You may want to check your internet connection or if you are behind a proxy.

Sorry for the noise, This seems to be issue related in our office network. Closing for now


Sentinel analytics health

Hi,
Please provide me with KQL queries for no incidents triggered in the last 90 days in the incident tab.
Thanks,

Hi @shipothana, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 11-10-2023. Thanks!

Hi @shipothana, based on the issue description, we are sharing the query -

For Check number of incident in 90days-

SecurityIncident
| where TimeGenerated > ago(90d)

For Checking the incident in Security Alert table -

SecurityAlert
| where TimeGenerated > ago(90d)
| where  IsIncident == "False"
| project TimeGenerated,DisplayName,AlertSeverity,AlertName,Description,VendorName

Hope this help,
if you have concern, please describe the more information about this issue.
Thanks!

Hi thanks for sharing the query!.
We have 300+ use cases, but only out of 20% are we triggering an incident, but I want to know which use cases have not triggered an incident in the last 90 days.

Hi @shipothana, just want to know, the above shared query work for you?

Working for me.. but I want to know which use cases have not triggered an incident in the last 90 days query

Hi @shipothana, thanks for sharing response, we are checking the KQL query, and we will update you by 13-10-2023 Thanks!

Hi @shipothana, we are sharing the query in which AlertName is referring to your use cases which not triggered an incident in last 90 days.
SecurityAlert
| where TimeGenerated > ago(90d)
| where  IsIncident == "False"
| project AlertName

if you want more details for use cases(AlertName), please refer below query -
SecurityAlert
| where TimeGenerated > ago(90d)
| where  IsIncident == "False"
| project AlertName, AlertSeverity, TimeGenerated, Description

Thanks!

Hi, thanks for sharing the query! ,
I want the SecurityIncident table to not trigger an incident in the last 90 days.

Hi @shipothana, all the Incidents that are triggered saved under SecurityIncident table, could you please explain what are the use cases which is not trigger?

Hi,
Please find the use cases are trigger.
RunningRAT request parameters
Create incidents based on Microsoft Defender for Endpoint alerts
Mercury - Domain, Hash and IP IOCs - August 2022
Azure VM Run Command operation executed during suspicious login window
AV detections related to Europium actors
Changes to PIM Settings
Correlate Unfamiliar sign-in properties and atypical travel alerts
DSRM Account Abuse
SEABORGIUM C2 Domains August 2022
Dev-0228 File Path Hashes November 2021
Dev-0530 IOC - July 2022
Authentication Method Changed for Privileged Account
Addition of a Temporary Access Pass to a Privileged Account
CreepyDrive request URL sequence
AdminSDHolder Modifications
Missing Domain Controller Heartbeat
Dev-0270 WMIC  Discovery
Known Barium domains
THALLIUM domains included in DCU takedown
AV detections related to SpringShell Vulnerability
AV detections related to Dev-0530 actors
TEARDROP memory-only dropper
AV detections related to Hive Ransomware
Admin promotion after Role Management Application Permission Grant
Authentication Methods Changed for Privileged Account
AV detections related to Tarrask malware
Correlate Unfamiliar sign-in properties & atypical travel alerts
Dev-0228 File Path Hashes November 2021
Dev-0270 Malicious Powershell usage
Dev-0270 Registry IOC - September 2022
Dev-0270 WMIC  Discovery
DSRM Account Abuse
Dumping LSASS Process Into a File
Europium - Hash and IP IOCs - September 2022
Identify Mango Sandstorm powershell commands
Identify SysAid Server web shell creation

Hi @shipothana, thanks for sharing the use cases with us, we are investigating the issue, and we'll let you know by 19-10-2023 Thanks!

Hi @shipothana, we are working on the KQL query, and we will update you by 20-10-2023. Thanks!

Hi @shipothana, could you please check the below query and let us know you got the result. we have different use cases in our workspace.
SecurityAlert
| join kind=fullouter  (SecurityIncident) on Status
| where IncidentNumber >= 0 and TimeGenerated > ago(90d)
| project IncidentNumber, AlertName , AlertSeverity ,TimeGenerated, Description, Title

Thanks for your query. I'm looking here for no incident triggered in sentinel use case details

Hi @shipothana, thanks for response, we will check the query and share with you. Thanks!

Hi @shipothana, thank you for being with us. could you please run the below KQL query in your workspace and let us know you got the result which you are expecting. Actually, we have different use cases in our workspace.
SecurityAlert
| join kind=fullouter  (SecurityIncident) on Status
| where TimeGenerated > ago(90d)
| where  IsIncident == "True"
| project IncidentNumber, AlertName , AlertSeverity ,TimeGenerated, Description, Title

Please let us know if the issue persists so that we can set up a call.
Thanks!

Please set up a call.
From: v-sudkharat @.>
Sent: Friday, October 27, 2023 2:59 PM
To: Azure/Azure-Sentinel @.>
Cc: Sivaramakrishna, Pothana @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] Sentinel analytics health (Issue #9170)
CAUTION: This email originated from outside of Alcon. Always verify the sending address and use caution when opening links or opening attachments unless you recognize the sender and know the content is safe.

Hi @shipothanahttps://github.com/shipothana, thank you for being with us. could you please run the below KQL query in your workspace and let us know you got the result which you are expecting. Actually, we have different use cases in our workspace.
SecurityAlert
| join kind=fullouter  (SecurityIncident) on Status
| where TimeGenerated > ago(90d)
| where  IsIncident == "True"
| project IncidentNumber, AlertName , AlertSeverity ,TimeGenerated, Description, Title
Please let us know if the issue persists so that we can set up a call.
Thanks!

Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/issues/9170#issuecomment-1782596911, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6QAT5RCTOBLB4VDB42UU4TYBN5HBAVCNFSM6AAAAAA5V5LELOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGU4TMOJRGE.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @shipothana, could you please let us know you convenient time so we can set up a call.
And please share you mail id with us.
Thanks!

Hi @shipothana, We are waiting for your response. Thanks!

Hi
 My working hours in the IST time zone, please send me a meeting invitation.

@shipothana, Could you please share your mail id with us? so, we can send a meeting invitation. Thanks!

I am free now please send me the meeting invite<EMAIL_ADDRESS>

Hi @shipothana, we sent an invite, please check. Thanks

Hi @shipothana, Could you please run the below query and check you got the expected results  .
SecurityIncident
| join kind= fullouter (SecurityAlert) on $left.Title==$right.AlertName
| where AlertIds !contains SystemAlertId
| project AlertName, SystemAlertId, AlertIds, IncidentName, IncidentNumber

We tested this query in our workspace, in which an analytic rule is created but we disabled the Incident creation for query testing -

After running the query, we got the Analytic rule which is created but not triggered an Incident.

Earlier, same analytic rule the incident is triggered.

Thanks!

Hi @shipothana, could you please have a look on above comment? and share response with us. Thanks!

Hi,
Still not working as for exapted.
Regards
Siva Pothana
Senior SOC Engineer ,IT Security Service Operations
Alcon Laboratories (India) Private Limited
M: +91-9177313529
<EMAIL_ADDRESS>@.https://www.alcon.com/ @.
From: v-sudkharat @.>
Sent: Monday, November 6, 2023 1:54 PM
To: Azure/Azure-Sentinel @.>
Cc: Sivaramakrishna, Pothana @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] Sentinel analytics health (Issue #9170)
CAUTION: This email originated from outside of Alcon. Always verify the sending address and use caution when opening links or opening attachments unless you recognize the sender and know the content is safe.

Hi @shipothanahttps://github.com/shipothana, could you please have a look on above comment? and share response with us. Thanks!

Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/issues/9170#issuecomment-1794296325, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6QAT5WZPH7WQBXFXV7HKCDYDCNB3AVCNFSM6AAAAAA5V5LELOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJUGI4TMMZSGU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@shipothana, what result you got? after running below query -
SecurityIncident
| where TimeGenerated > ago(90d)
| join kind= fullouter (SecurityAlert) on $left.Title==$right.AlertName
| where AlertIds !contains SystemAlertId
| project AlertName, SystemAlertId, AlertIds, IncidentName, IncidentNumber

Could you please share the query result with us?
You can share in Our Team's group as well.
Thanks!

Hi @shipothana, Could you please share the screenshot of what issue you are facing in AnalyticsEfficiency.json workbook? it would be helpful for us to more investigate.
Additionally, we have same workbook in SOC Handbook solution, could you please install the latest solution from Content Hub and check the workbook.
Sharing the screenshot for reference-

Please let us know still you are getting same issue. Thanks!

Hi @shipothana ,Could you please check the above mentioned steps and update issue as resolved or not?

Hi @shipothana, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 22-11-2023 date, we will be closing this issue.
Thanks!

Thanks for supporting us!
could you please elaborate more details about SOC Handbook solution for Microsoft Sentinel?

Hi @shipothana, Sure, we are pleased to elaborate on this SOC Handbook solution. with the reference of solution description, The SOC Handbook Microsoft Sentinel solution is a collection of resources designed to assist SOC Analysts. and these resources help to a analysts gain a better understanding of the security status of an organization's resources at any given time.
For Example - the SOC Handbook solution includes an AnalyticsEfficiency workbook. This workbook provides detailed information about Analytic rules in the form of charts.
In reference to your problem statement, the AnalyticsEfficiency workbook allows you to select the Analytic rules (Use Cases) which created in your subscription or workspace. However, these rules require attention because they either didn't create any alerts during the selected period, or they are auto disabled.
As shown in the screenshot below, we have selected a few Rules (Use Cases) that were created and enabled in the workspace. However, these rules appear in the "Rules that require attention" section in the workbook because they did not generate any alerts during the selected time frame (e.g., 1 day, 7 days, or 90 days).

Select your Subscription and Workspace -

Select the Analytic rules -

We hope this provides a satisfactory answer to your question.
If you are facing any issue in that workbook, please let us know, so we can connect via call. It would be helpful for us to understand the issue.
Thanks!

Hi @shipothana, Could you please have a look at above comment? and share response with us. Thanks!

Hi @shipothana, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 28-11-2023 date, we will be closing this issue.
Thanks!

Hi @shipothana, since we have not received a response in the last 5 days, we are closing your issue #9170 as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.


[BEAM-3041] Support various pip based dependency options for python sdk

Adds a package for doing common pip installation scenarios. (Along the lines of https://beam.apache.org/documentation/sdks/python-pipeline-dependencies/). Is this the right place to add the utility?
After this, I will update https://github.com/apache/beam/blob/master/sdks/python/container/boot.go to use this. (boot.go will reference this as a github import, is it possible to update both in the same PR?)
R: @herohde

For now, I'd suggest to just place the file next to boot.go (and change the package to main). These helpers are python specific and could just be local helper functions, similarly to the ones already there: https://github.com/apache/beam/blob/master/sdks/python/container/boot.go#L112/.
Multiple files are fine and you can change boot.go at the same time.

retest this please

@herohde PTAL. I tested this with a job.
(Python failure is unrelated to this change. There is no python sdk change in this PR.)


"Open Folder before change configurations" on every new VS Code Window

Every time I open a new VS Code window I get an info saying "Open folder before change Configurations".  This stack overflow question seems to indicate the message is coming from the vscode-database extension.

If I disable vscode-database the message no longer appears.
VS Code version: 1.20
vscode-database version: 1.3.0
OS: OSX Sierra (10.12.6)

Version 1.4.0 fix this issue ;)


[HUDI-1058] Make delete marker configurable

What is the purpose of the pull request
users can specify any boolean field for delete marker and _hoodie_is_deleted remains as default.
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@nsivabalan can you please take a pass once CI is passing

Looks like there are 2 options here.
Option1: Change interface for combineAndGetUpdateValue and getInsertValue to take in delete field.
check https://github.com/apache/hudi/pull/1792 on why we need to fix getInsertValue as well.
Option2: Approach taken in the patch, where in expose a setDeleteField method in OverwriteWithLatestAvroPayload and this will be set while generating HoodieRecords from GenericRecord.
Since making changes in getInsertValue will touch lot of files, guess we can go with Option2 with some changes.
Instead of exposing a new method, why can't we add an overloaded constructor. When HoodieSparkSqlWriter calls into
DataSourceUtils.createHoodieRecord(gr,
                orderingVal, keyGenerator.getKey(gr), parameters(PAYLOAD_CLASS_OPT_KEY))

we could also pass in a delete field optionally which inturn will be passed into constructor of OverwriteWithLatestAvroPayload. If delete field is set by user, then we take that else we resort to "_hoodie_is_deleted".
Let me know your thoughts.

@nsivabalan actually what i commented here is the 3rd option

@shenh062326 Maybe we shouldn't do the check in the payload class itself. Maybe org.apache.hudi.io.HoodieMergeHandle#write is better for this job. After
https://github.com/apache/hudi/blob/2603cfb33e272632d7f36a53e1b13fe86dbb8627/hudi-client/src/main/java/org/apache/hudi/io/HoodieMergeHandle.java#L222-L223
we check combinedAvroRecord against the delete field defined in the configs and convert it to Option.empty() if appropriate. As this feature is config-related, whoever owns the configs should do it. Need more inputs from @nsivabalan

Basically it is about shifting the responsibility of converting records to Option.empty() to HoodieMergeHandle. WDYT?

@xushiyan  It seems good for OverwriteWithLatestAvroPayload. But for AWSDmsAvroPayload, users need to define not only the deletion column, but also the processing method of deleting the column. Where is the new method should be? If it continue to stay in combineAndGetUpdateValue, then combineAndGetUpdateValue has the processing delete logic, and the calling method also has the delete logic, will it be repeated?

@xushiyan : nope. As I have mentioned above, we need it in getInsertValue() as well which is called from lot of classes. Hence I suggested to add it as part of constructor.

@shenh062326 @nsivabalan got it. yup, making it through the constructor looks good. thanks for clarifying.

I don't see any tests being added as part of the patch. Would be nice to have some tests covering the new code that was added at all levels.

WriteClient
Datasource if there is an existing suite of tests for other write operations
Deltastreamer

Done.

@xushiyan : do you plan to review? Or can I go ahead and merge this.

@nsivabalan no, please feel free to merge. there has been thorough reviews :) thanks

Folks, I see a performance/efficiency problem with the approach here. We added a string field to every payload object, which will get increase the shuffle size in the write path. We would be just sending the same string with each and every object.
Can we rework this so that we introduce a new PayloadConfig object which we can hand to the payload methods at runtime, instead of adding this to constructor? We need to introduce new methods without breaking existing Custom payload implementations.
cc @nsivabalan @shenh062326 @xushiyan

makes sense. sorry about the oversight.
I will take up the rework by using a payloadConfig class.

makes sense. sorry about the oversight.

I can rework it.
Let me confirm the how to do it first, adding PayloadConfig, and then calling PayloadConfig in OverwriteWithLatestAvroPayload to get deleteMarkerField, is that right?

@shenh062326 : appreciate your help. We are looking to have a release by this weekend and so I am reverting this patch for now. I will work with you with the right fix for configurable delete marker. if we can get it in by this weekend well and good, even if not, we can land it later once we cut the release for 0.6.0.

@vinothchandar : if I am not wrong, we added an additional overloaded constructor to OverwriteWithLatestAvroPayload. so shouldn't have broken any existing implementations. Only if someone wants to leverage user defined col, they might have to use the new constructor. Anyways, your perf reasoning is convincing, hence going ahead w/ reverting.

@nsivabalan my concern is more on the overhead of the extra field on the payload serialization. No matter what constructor is called. there is a string field that will be serialized, right?

I see it now. got it.

Let me confirm the new implementation again, adding a field containing transient to OverwriteWithLatestAvroPayload, like below:
  private transient String deleteMarkerField = null;

  public void setDeleteMarkerField(String deleteMarkerField) {
    this.deleteMarkerField = deleteMarkerField;
  }

And set the deleteMarkerField before HoodieMergeHandle.write call OverwriteWithLatestAvroPayload.combineAndGetUpdateValue, right?

nope. we need to create a new class called PayloadConfig which will hold the deleteMarkerField col name. Similar to how we pass in Schema to OverwriteWithLatestAvroPayload#combineAndGetUpdateValue and OverwriteWithLatestAvroPayload#getInsertValue, we have to pass this payloadConfig as well. Hope you get the gist.
@vinothchandar : can you confirm if this is the right approach.

It seems there are two implementations.
(a) If we add new methods like below to HoodieRecordPayload, since HoodieRecordPayload is an interface, it will incompatible will custom payload implementations.
public Option<IndexedRecord> combineAndGetUpdateValue(IndexedRecord currentValue, Schema schema, PayloadConfig payloadConfig)
public Option<IndexedRecord>  getInsertValue(Schema schema, PayloadConfig payloadConfig)

(b) If we add this method to OverwriteWithLatestAvroPayload,  when we call  HoodieRecordPayload.combineAndGetUpdateValue and HoodieRecordPayload.getInsertValue,  we need to check whether it's OverwriteWithLatestAvroPayload or not, if it's OverwriteWithLatestAvroPayload, we need to call getInsertValue(Schema schema, PayloadConfig payloadConfig); if it's not  OverwriteWithLatestAvroPayload,  we need to call getInsertValue(Schema schema). But there are many places will call HoodieRecordPayload.getInsertValue.

@vinothchandar  @nsivabalan  Can you take a look at this PR?

@shenh062326 : sorry for late reply. Can you check #1704 patch on how to add new apis. Infact, we need to coordinate both these patches. I mean, land one and rebase other one and re-use the new apis added as part of first patch. @bhasudha : wrt your patch, What is your take on adding a PayloadConfig instead of a Map<>. I understand map is very flexible, but for payload class, hudi controls what goes in.

Sure, I will check it.


⚠ Bofrost.at has degraded performance

In a391a4a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1819 ms

Resolved: Bofrost.at performance has improved in 60f438e.


Gyro reference (comparison and adjustment)

Define it at 0
Comparison - check current value against initial 0
Adjustment - turn robot based on comparison

[] Basic gyro function (find one online, should be pretty simple)
[] Adjustment based on angle


Live preview on Brackets not working / can't fix it

Hello everyone, I have a problem with Brackets.
It worked fine but suddenly the live preview cant start. I tried everything from the troubleshooting site.
I am working on a PHP project and everytime i click the live preview button a Chrome site opens and it is Waiting... and then a pop-up appears saying Connecting to Browser... See the image below.
http://prntscr.com/kem1ec
Please help, I dont want to switch to other code editor as Brackets is very good one.

Same here. After update it opens the page waits a little and is shut down. Don't know if it is Chrome doing some weirdness or if it's brackets.


Fix Ubuntu 22.04 SSH authentication failed

Fix Ubuntu 22.04 SSH authentication failed
For https://github.com/longhorn/longhorn/issues/4320
Signed-off-by: Yang Chiu<EMAIL_ADDRESS>

Probably need to update to other distros as well, because this will possibly happen to them in the future.

Probably need to update to other distros as well, because this will possibly happen to them in the future.

The correct solution should be updating terraform version to let it support newer ssh key algorithms, then we don't have to modify distros to make them support old ssh algorithms. I've created PR https://github.com/longhorn/longhorn-tests/pull/1072 for this.


Hide annotate cells should toggle

Hide annotate cells should probably be a toggle that goes "hide" -> "show" annotated cells and changes it's label based on button state, as it was a little unclear to me how it functioned. If you are in "hide mode" I'd probably at most show the last edited cell (so you can keep interacting with it), but then as soon as you label a new one that last one disappears. I imagine that auto disappearing will be very satisfying!

I feel like I'd also have "hide" make the points, invisible instead of just the cell outlines. Will help reduce clutter. You can do this by hijaking the alpha value of the face and edge color, which can be done with something like
viewer.layers['infected-vs-control'].edge_color[indices_of_annotated_cell, -1] = 0
viewer.layers['infected-vs-control'].face_color[indices_of_annotated_cell, -1] = 0
viewer.layers['infected-vs-control].refresh()

If you want them to appear again you can just set it to 1. Note you need the refresh here to tigger the update as you are editing the array in place

Let me know if you run into problems with this, I'm sure I could help out

Hide annotate cells should probably be a toggle that goes "hide" -> "show" annotated cells and changes it's label based on button state, as it was a little unclear to me how it functioned. If you are in "hide mode" I'd probably at most show the last edited cell (so you can keep interacting with it), but then as soon as you label a new one that last one disappears. I imagine that auto disappearing will be very satisfying!

Yes, I agree. That would be even better than the current implementation.
I am not quite sure how to implement this through the QButton though.
Any pointers would be very welcome ;).

I feel like I'd also have "hide" make the points, invisible instead of just the cell outlines. Will help reduce clutter.

I agree and I tried to implement this using your suggestion:
https://github.com/hci-unihd/covid-if-annotations/blob/master/napari_covid_if_annotations/_key_bindings.py#L103-L112
However, this doesn't quite work as expected, it only hides the edges, not the faces, see screenshots of normal / "hidden" mode:

Ah yes, my mistake, this is because the face color is being set through the face_color_cycle property. You should be able to do
viewer.layers['infected-vs-control'].edge_color[indices_of_annotated_cell, -1] = 0
viewer.layers['infected-vs-control'].face_color_cycle[1:, -1] = 0
viewer.layers['infected-vs-control'].refresh_colors()

Where here you are making the "non white" colors invisible. You could also use an edge_color_cycle which had 4 colors for your 4 states - starting all black, but then toggling those edited 3 to invisible. It would bring a bit more symmetry to the code above, but up to you!
I will look into the if layer.visible: guard you put in to fix #23, I think we should be able to figure out another solution

I can make a PR with this fix and also swap the QPushButton to a QCheckBox right now


Add possibility to enable and test PMU feature

@lorc, @firscity  thank you for your review comments. I released a new version of PR that includes the following changes:

Removed overriding compatible field;
Added more details about enabling PMU feature.

Please, take a look at the new version.

@lorc @firscity thank you for your reviews. Added acked-by tags.


Problem with fetch tries

I´ve set my fetch tries to 10 on network errors, but log shows  me serposcope ending task with only three.
This is a bug or I´m missing something?
proxy:bind://#OBF#proxy-ip#/ try 1
[2018-05-30 08:14:06,548] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[200] exception=[none]
[2018-05-30 08:14:06,566] [google-0] TRACE c.s.s.s.g.s.GoogleScraper - sleeping 64410 milliseconds
[2018-05-30 08:15:11,013] [google-0] INFO  c.s.s.t.g.GoogleTaskRunnable - search "#OBF#search-190#" | try 1 | total search done : 16/37
[2018-05-30 08:15:11,014] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.com/search?q=#OBF#search-190#&gl=br&num=100 via proxy:bind://#OBF#proxy-ip#/ try 1
[2018-05-30 08:15:11,483] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[403] exception=[none]
[2018-05-30 08:15:12,483] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.com/search?q=#OBF#search-190#&gl=br&num=100 via proxy:bind://#OBF#proxy-ip#/ try 2
[2018-05-30 08:15:12,977] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[403] exception=[none]
[2018-05-30 08:15:14,977] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.com/search?q=#OBF#search-190#&gl=br&num=100 via proxy:bind://#OBF#proxy-ip#/ try 3
[2018-05-30 08:15:15,531] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[403] exception=[none]
[2018-05-30 08:15:18,532] [google-0] WARN  c.s.s.t.g.GoogleTaskRunnable - scrap failed for #OBF#search-190# because of ERROR_NETWORK
[2018-05-30 08:15:18,533] [google-0] INFO  c.s.s.t.g.GoogleTaskRunnable - search "#OBF#search-190#" | try 2 | total search done : 16/37
[2018-05-30 08:15:18,533] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.com/search?q=#OBF#search-190#&gl=br&num=100 via proxy:bind://#OBF#proxy-ip#/ try 1
[2018-05-30 08:15:19,218] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[403] exception=[none]
[2018-05-30 08:15:20,218] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.com/search?q=#OBF#search-190#&gl=br&num=100 via proxy:bind://#OBF#proxy-ip#/ try 2
[2018-05-30 08:15:20,858] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[403] exception=[none]
[2018-05-30 08:15:22,859] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.com/search?q=#OBF#search-190#&gl=br&num=100 via proxy:bind://#OBF#proxy-ip#/ try 3
[2018-05-30 08:15:23,616] [google-0] INFO  c.s.s.s.g.s.GoogleScraper - GOT status=[403] exception=[none]
[2018-05-30 08:15:26,617] [google-0] WARN  c.s.s.t.g.GoogleTaskRunnable - scrap failed for #OBF#search-190# because of ERROR_NETWORK
[2018-05-30 08:15:26,617] [google-0] WARN  c.s.s.t.g.GoogleTaskRunnable - no more proxy, stopping the thread
[2018-05-30 08:15:26,617] [google-0] INFO  c.s.s.t.g.GoogleTaskRunnable - google thread stopped
[2018-05-30 08:15:26,636] [Thread-13] WARN  c.s.s.t.g.GoogleTask - 2 proxies failed during the task
[2018-05-30 08:15:26,636] [Thread-13] WARN  c.s.s.t.g.GoogleTask - 21 searches have not been checked
[2018-05-30 08:15:26,637] [Thread-13] INFO  c.s.s.t.AbstractTask - task done for module GOOGLE

Made a clean install of 2.7.1, and found same behavior, check the logs here ->  https://pastebin.com/1PwLq4xP
I already have raised my bids, but, for now, I can´t complete one single run without errors. Getting NETWORK_ERRORS every 20 words.
90 - 120 secs pause
2 ips,  (extension planned )
only one captcha service (extension planned)
10 fetch retries
100 keywords (slowing increasing until 1000)
Maybe something with intervals or network load? Is I´m missing something into my infra, not the tool. Any toughts?


TST: hide explicit MDS imports

This allows re-use of tests  without requiring pymongo

This should fix portable mds issues.

Current coverage is 89.70% (diff: 100%)

Merging #251 into master will not change coverage

@@             master       #251   diff @@
==========================================
  Files             4          4
  Lines           476        476
  Methods           0          0
  Messages          0          0
  Branches         75         75
==========================================
  Hits            427        427
  Misses           34         34
  Partials         15         15

Powered by Codecov. Last update a60773f...a46c393


Enable link time optimizations and improve dead code elimination

Ouch, this PR turns out to be redundant, the flags are already there.