dmarc-metrics-exporter: 0.8.0 -> 0.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for dmarc-metrics-exporter is: Export Prometheus metrics from DMARC reports
meta.homepage for dmarc-metrics-exporter is: https://github.com/jgosmann/dmarc-metrics-exporter
meta.changelog for dmarc-metrics-exporter is: https://github.com/jgosmann/dmarc-metrics-exporter/blob/v0.8.1/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.1 with grep in /nix/store/i9hkr5ckl18ifpi8bqpdjsy3f0jqch21-dmarc-metrics-exporter-0.8.1
found 0.8.1 in filename of file in /nix/store/i9hkr5ckl18ifpi8bqpdjsy3f0jqch21-dmarc-metrics-exporter-0.8.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
dmarc-metrics-exporter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i9hkr5ckl18ifpi8bqpdjsy3f0jqch21-dmarc-metrics-exporter-0.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i9hkr5ckl18ifpi8bqpdjsy3f0jqch21-dmarc-metrics-exporter-0.8.1
ls -la /nix/store/i9hkr5ckl18ifpi8bqpdjsy3f0jqch21-dmarc-metrics-exporter-0.8.1/bin

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

1 package built:

dmarc-metrics-exporter

Maintainer pings
cc @Ma27 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for dmarc-metrics-exporter is: Export Prometheus metrics from DMARC reports
meta.homepage for dmarc-metrics-exporter is: https://github.com/jgosmann/dmarc-metrics-exporter
meta.changelog for dmarc-metrics-exporter is: https://github.com/jgosmann/dmarc-metrics-exporter/blob/v0.9.0/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.0 with grep in /nix/store/wddrwr8mbxn57yd7bf2w98jvrmj94v7h-dmarc-metrics-exporter-0.9.0
found 0.9.0 in filename of file in /nix/store/wddrwr8mbxn57yd7bf2w98jvrmj94v7h-dmarc-metrics-exporter-0.9.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
dmarc-metrics-exporter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wddrwr8mbxn57yd7bf2w98jvrmj94v7h-dmarc-metrics-exporter-0.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wddrwr8mbxn57yd7bf2w98jvrmj94v7h-dmarc-metrics-exporter-0.9.0
ls -la /nix/store/wddrwr8mbxn57yd7bf2w98jvrmj94v7h-dmarc-metrics-exporter-0.9.0/bin

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

1 package built:

dmarc-metrics-exporter

Maintainer pings
cc @Ma27 for testing.


Support for Athena and Trino dialect

Athena is Trino's managed solution in the AWS ecosystem. Trino (and therefore Athena) support ANSI dialect but there are some syntax variations.
Considering athena and trino are widely adopted, it will be nice to support them fully, and allow people to replace the widely used sqlfluff with sqruff.

Totally agree! Thanks for flagging.

need this too

A start https://github.com/quarylabs/sqruff/pull/690

And for athena https://github.com/quarylabs/sqruff/pull/696

Athena is done and being deployed right now.

There's also Trino coming through right now.

I am marking this as done, as the new version has been pushed everywhere. Please let us know if you have any problems with it!


fix: [M3-7079] - Resolve "Incomplete string escape or encoding" alert in changeset.mjs

Description 📝
Resolve codeQL alert due to not escaping backslashes
Major Changes 🔄

add check for backslashes in regex

Preview 📷
looks like the alert for the changeset script (last alert in the before picture) is gone! (I installed the codeQL extension on VSCode + set it up and ran it). Note: the other alerts aren't part of this PR. They aren't showing up in the Security tab, and seem to be for build files, so I'm unsure if we'll need to create tickets for them (?)

Before
After

(this doesn't actually affect the changeset, just the commit message if you're committing the changeset)

How to test 🧪

If you have the codeQL extension on VSCode, you can set up a codeQL database for the manager repo and run the IncompleteSanitization.ql query (from the codeql repo - javascript >> ql >> src >> Security >> CWE-116 >> IncompleteSanitization.ql) on the manager database. Instructions for setting up the extension here: https://codeql.github.com/docs/codeql-for-visual-studio-code/setting-up-codeql-in-visual-studio-code/ (+ I also installed the CLI). I found this guide pretty helpful for setting up the db too
If you don't have the codeQL extension, you can try running the changeset script and inputing \ with ` characters into the description, and then committing those files. You may need to log the escapedDescription to verify that the ` characters are correctly escaped there or push the commits to verify the commit message

Thanks Alban! Am definitely not a regex expert either 😅 -- I'd come across someone having a similar problem here and was trying to think about how to defensively program against the issue described there. However I'm now thinking that my attempt inadvertently gets rid of backslashes that we may want to keep. Will test out your regex!
(also random but fun -- the issue I linked is 7079 for the codeql repo, and this ticket is also 7079 😆)


Log streaming file for Amazon Linux 2

Hi!
Please can we get an Amazon Linux 2 specific file for streaming logs to cloudwatch? The current file contains commands that do not work on AMI2 environments.
The documentation reflects this here.

Any update?  I am facing same issue...
https://github.com/awsdocs/elastic-beanstalk-samples/issues/109

I looked at the differences from the docs and was able to solve my issue with a file with contents similar to this:
###################################################################################################
#### Copyright 2016 Amazon.com, Inc. or its affiliates. All Rights Reserved.
####
#### Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file
#### except in compliance with the License. A copy of the License is located at
####
####     http://aws.amazon.com/apache2.0/
####
#### or in the "license" file accompanying this file. This file is distributed on an "AS IS"
#### BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
#### License for the specific language governing permissions and limitations under the License.
###################################################################################################
###################################################################################################
#### The following file installs and configures the AWS CloudWatch Logs agent to push logs to a Log
#### Group in CloudWatch Logs.
####
#### The configuration below sets the logs to be pushed, the Log Group name to push the logs to and
#### the Log Stream name as the instance id. The following files are examples of logs that will be
#### streamed to CloudWatch Logs in near real time:
####
#### /var/log/messages
#### /var/log/dmesg
####
#### You can then access the CloudWatch Logs by accessing the AWS CloudWatch Console and clicking
#### the "Logs" link on the left. The Log Group name will follow this format:
####
#### /aws/elasticbeanstalk/<environment name>/<full log name path>
####
#### Please note this configuration can be used additionally to the "Log Streaming" feature:
#### http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/AWSHowTo.cloudwatchlogs.html
###################################################################################################
packages:
  yum:
    awslogs: []

option_settings:
  - namespace: aws:elasticbeanstalk:cloudwatch:logs
    option_name: StreamLogs
    value: true
  - namespace: aws:elasticbeanstalk:cloudwatch:logs
    option_name: DeleteOnTerminate
    value: false
  - namespace: aws:elasticbeanstalk:cloudwatch:logs
    option_name: RetentionInDays
    value: 3

files:
  "/etc/awslogs/awscli.conf" :
    mode: "000600"
    owner: root
    group: root
    content: |
      [plugins]
      cwlogs = cwlogs
      [default]
      region = `{"Ref":"AWS::Region"}`

  "/etc/awslogs/config/logs.conf" :
    mode: "000600"
    owner: root
    group: root
    content: |
      [/var/log/messages]
      log_group_name = `{"Fn::Join":["/", ["/aws/elasticbeanstalk", { "Ref":"AWSEBEnvironmentName" }, "var/log/messages"]]}`
      log_stream_name = {instance_id}
      file = /var/log/messages

      [/var/log/dmesg]
      log_group_name = `{"Fn::Join":["/", ["/aws/elasticbeanstalk", { "Ref":"AWSEBEnvironmentName" }, "var/log/dmesg"]]}`
      log_stream_name = {instance_id}
      file = /var/log/dmesg

commands:
  "01":
    command: systemctl enable awslogsd.service
  "02":
    command: systemctl restart awslogsd

The difference is that AMI2 uses a different start system, so the commands use systemctl instead.

I also struggled with this issue. I can confirm that @opeyemi-paystack's solution works and would like to see an updated file for the AWS Linux v2 AMI.

Thanks @opeyemi-paystack . I modified the commands in the example per your fix, and kept the legacy version as logs-streamtocloudwatch-linux-alami.config.
I only modified the commands, and didn't make your other changes, as they might be specific to what you need. I wanted to keep the example as close as possible to the original, only adapting for the AL2 OS changes.

I'm a bit confused about this one. I'm using Amazon Linux 2 with EB Docker 3.0.3 platform and it doesn't use the old awslogsd agent but amazon-cloudwatch-agent. Logs stream fine except for the Docker logs (which is basically what we want): https://forums.aws.amazon.com/thread.jspa?threadID=324227&tstart=0

For anyone else arriving here, AL2 on Docker no longer needs a custom config in order to stream logs.
By default, all logs go to:
/aws/elasticbeanstalk/{your-env-name}/var/log/eb-docker/containers/eb-current-app/stdouterr.log


Support for RG351MP?

Hi, any plans to support the newly released RG351MP? Thanks!

I'm supposed to be receiving a unit soon.  Provided the hardware is good and Anbernic makes sources available, I may release ArkOS for it.  Just waiting until I get my unit so I can further review possibilities.

ArkOS 2.0 Test Release 1.0 for the Anbernic RG351MP is now available
Google Drive: https://drive.google.com/file/d/1iRGotglxeqiAAUChE_lIvWmwvhUeh0mt/view?usp=sharing
Mega: https://mega.nz/file/nFJgmLgA#il82b4JQOUaqQCLZcVkZ3ZUZoG_Na2lnvdOLuUOeaJI
FAQ: https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG351MP
Changelog: https://github.com/christianhaitian/arkos/raw/main/changelogs/rg351mp-changelog
Important Notes

Only authentic Sandisk and Samsung cards are supported and recommended.

In my initial testing of my 2 units, 1 unit failed to boot with a PNY sd card flashed with ArkOS.  The same unit would occassionally experience corruption with a Gigastone sd card.  The other unit seemed to boot the same PNY card without issue.  Didn't test Gigastone on it.  TO MINIMIZE ON POTENTIAL FRUSTRATION, ONLY USE AN AUTHENTIC SAMSUNG OR SANDISK SD CARD

Follow the instructions from the wiki to properly loading this image: https://github.com/christianhaitian/arkos/wiki#instructions-for-loading
Initial boot and preparation can take about 8 minutes to complete due to the themes being copied.  Be patient!
Be sure during initial boot, Only have the OS SD card in slot 1 (TF1/INT.) during the initial boot!.  Do not put an SD card in slot 2 (TF2/Ext.) during the initial boot!  Failure to follow this may result in strange behavior during the intial boot preparation process.
Once the initial boot has completed and you're at the Emulationstation menu, you can insert your second sd card into slot 2 (TF2/Ext.).
To make use of your second sd card for your games, go to options/Advancec/Switch to SD2 for ROMS.  For more information, see: https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---rg351mp#q-how-do-i-make-use-of-the-second-sd-slot-for-roms-and-games
There's no boot logo currently due to the unavailability of an updated uboot source code.  Hopefully this will be resolved in the near future.
Hotkey information: https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG351MP#q-what-are-the-global-event-keys-and-emulator-event-keys-in-ArkOS

Make sure to check for Updates online via the Options section for the latest fixes and features as they become available.  There's already 2 updates already.

Excellent job getting it out so quickly, everything seems to work except Atari Lynx none of which load regardless of which core and emulator I select......other than that all good and perfect timing as I received my RG351MP yesterday!


WIP: Portal Enclaves

An emerging idea on how to deal with DOS/eclipse/etc in portal.

closing as this isn't an active area of research.


Issue with User Stupidity Denying Permissions

Problem: If the user selects "Do Not Remind Again" when going through the permissions and then presses Deny on the permission, the user will be stuck on the Permissions screen forever. The user is unable to grant the permission and Material Intro does not allow the user to advance.
Solution: Blame the user? Not the most elegant solution but it seems appropriate here. Is there a better way though?

You can use addonNavigationBlockLoistener and if the user is on setting slide then check for
ActivityCompat.shouldShowRequestPermissionRationale(CONTEXT,PERMISSION) if this returns false
show user snackbar with action to open settings of your app
Intent myAppSettings = new Intent();
myAppSettings.setAction(Settings.ACTION_APPLICATION_DETAILS_SETTINGS);
Uri uri = Uri.fromParts("package", getActivity().getPackageName(), null);
myAppSettings.setData(uri);
startActivityForResult(myAppSettings, appsettingReqCode);
this will take him to your apps setting panel from where user can provide permissions.

As @sunil19822701 said...
Check out https://github.com/HeinrichReimer/material-intro/blob/3100a7ca893db446d5d68d361dbf81b1c1cb1980/library/src/main/java/com/heinrichreimersoftware/materialintro/app/IntroActivity.java#L1143

Make sure you are calling this method with the right arguments: https://developer.android.com/reference/android/support/v4/app/ActivityCompat.html#shouldShowRequestPermissionRationale(android.app.Activity, java.lang.String)

Link seems to be broken by markdown so here is the working link: [ActivityCompat.shouldShowRequestPermissionRationale(Activity, String)](https://developer.android.com/reference/android/support/v4/app/ActivityCompat.html#shouldShowRequestPermissionRationale(android.app.Activity, java.lang.String))


Yolov5 Quantization Aware Training Error in Vitis AI

I am trying to quantize a custom yolov5 model using quantization aware training method. I have applied all the model adjustments as provided in the vitis ai user guide v3.0 and wrote the QAT code based on the resnet example provided in vitis ai examples: https://github.com/Xilinx/Vitis-AI/blob/v3.0/src/vai_quantizer/vai_q_pytorch/example/resnet18_qat.py
However, I am getting  an error with QatProcessor function from pytorch_nndct library.
The error is illustrated in the figure below:
Traceback (most recent call last):
File "yolov5_QAT.py", line 484, in
main()
File "yolov5_QAT.py", line 450, in main
qat_processor = QatProcessor(model, inputs)
File "/opt/vitis_ai/conda/envs/vitis-ai-pytorch/lib/python3.7/site-packages/pytorch_nndct/quantization/quant_aware_training.py", line 190, in init
if self._graph.node(node).has_bound_params():
AttributeError: 'NoneType' object has no attribute 'has_bound_params'

The error you're encountering, 'NoneType' object has no attribute 'has_bound_params', typically indicates that the node object in your quantization-aware training (QAT) code is None, and you're trying to access the has_bound_params() method on it. This error often occurs when there's an issue with your model or the way it's being processed during quantization-aware training.
To debug and resolve this issue, you can try the following steps:
Check Model Compatibility: Ensure that your custom YOLOv5 model is compatible with the QAT process. Not all models can be quantized without modifications. Check if there are any layers or operations in your custom model that are not supported by the quantization framework you are using.
Input Data: Verify that the inputs you're passing to the QatProcessor function are correctly formatted and are compatible with your model's input requirements.
Layer Names: Make sure the layer names or node names in your custom model match what the QAT code expects. The error might occur if a required layer is missing or named differently.
Check Dependencies: Ensure that you have installed the required dependencies for your QAT code and that they are compatible with your PyTorch version. Also, verify that you are using a compatible version of Vitis AI and the pytorch_nndct library.
Model Debugging: You can try to print the model's architecture and investigate if there are any irregularities or issues with layer names, shapes, or attributes. This can help you pinpoint where the NoneType error is originating.
Update Library: It's possible that there might be a bug in the version of pytorch_nndct you are using. Check for updates or try using a different version of the library to see if the issue is resolved.
Consult Documentation: Review the documentation for the specific version of Vitis AI you are using. There may be updates, changes, or specific requirements for the QAT process that are not covered in the example you linked.
Debugging Tools: You can use debugging tools such as print statements and Python's debugger (pdb) to trace the flow of your code and identify where the None value is coming from.
Community/Support: If you are still unable to resolve the issue, consider reaching out to the Vitis AI community or support channels. They may be able to provide specific guidance or solutions based on the version you are using and any known issues.

The error you're encountering seems to be related to the QatProcessor trying to access the has_bound_params() method on a NoneType object. This typically indicates that the _graph attribute of the QatProcessor is not properly initialized or set to None. Without seeing your specific code, it's a bit challenging to pinpoint the exact issue, but I can provide some general guidance on how to troubleshoot and resolve this type of error.
Here are some steps you can take:
Check Model and Inputs:
Ensure that your model and input tensors are properly defined and constructed. The model should be a valid PyTorch model, and the input tensors should have the correct shape and data type.
Check PyTorch Version:
Make sure that you are using a compatible version of PyTorch with the version of the pytorch_nndct library. Incompatibility between versions could lead to issues.
Check QatProcessor Initialization:
Verify that the QatProcessor is being initialized correctly. Ensure that you are passing the correct arguments to the constructor, including a valid PyTorch model and input tensors.
Review Custom Model Adjustments:
Double-check the adjustments you made to your custom YOLOv5 model. Ensure that any modifications you made for quantization are valid and do not introduce errors.
Look for Example Code:
Review the example code you referred to in the Vitis-AI user guide and the ResNet example from the Vitis-AI examples repository. Ensure that you are following the structure and procedures outlined in these examples.
Check for Updates:
Check for any updates to the Vitis-AI library or the pytorch_nndct library. It's possible that there have been updates or bug fixes that address the issue you're facing.
Debugging:
Insert print statements or use a debugger to inspect the state of variables and objects at different points in your code. This can help you identify where the NoneType error is originating.
Consult Documentation and Forums:
Check the official documentation for Vitis-AI and the pytorch_nndct library. Additionally, consider looking for forums or community discussions related to Vitis-AI where others may have encountered similar issues.
If the issue persists and you are unable to identify the root cause, consider reaching out to the support channels provided by Xilinx or the community forums for assistance. They may be able to provide more specific guidance based on the details of your implementation.

Hi @IkrameBeggar , I am encountering the same issue as you, by any chance did you managed to solve this problem?
Thanks!

Hi @IkrameBeggar , I am encountering the same issue as you, by any chance did you managed to solve this problem?
Thanks!

Hello, I didn't manage to solve it. Yet, I figured out that the problem with the model architecture.
I added a print statement to check the value of "node" in the quant_aware_training.py code to compare it with the one of the resnet18 model provided as an example in the Vitis AI Github Repository.

The node value for yolov5 contains a single layer of the model. However, for resnet18, the node value is updated by the next layer after each iteration of the for loop.
I hope this will be helpful for you to solve the error. In case you did, please let me know how did you manage to solve it.


Fix doc bug

I think it's better to get the extra "plt.show()" removed since it dangles below the land-sea mask image created by the first "plt.show()" statement.

Thanks!

You are welcome. Shall I open another pull request on gh-pages to reflect the change on the documentation site?

actually, no, I don't think that is where it needs to be done. I only
recently taken over this project, so I am still trying to figure out
exactly how deployment of the docs are done. I think it is all being
handled through ReadTheDocs, which I have zero experience with, nor do I
have an account on.
On Thu, Feb 4, 2016 at 8:15 AM, Li Jiapeng<EMAIL_ADDRESS>wrote:

You are welcome. Shall I open another pull request on gh-pages to reflect
the change on the documentation site?
—
Reply to this email directly or view it on GitHub
https://github.com/matplotlib/basemap/pull/258#issuecomment-179825660.


[Build Error] [CMake] Cannot find hip

What is the expected behavior

Including rocfft in a cmake project like find_package(rocfft) should be successful.

What actually happens

When using find_package(rocfft), it fails since it cannot find hip, even though hip is installed.

CMake Error at /usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
  By not providing "Findhip.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "hip", but
  CMake did not find one.

  Could not find a package configuration file provided by "hip" with any of
  the following names:

    hipConfig.cmake
    hip-config.cmake

  Add the installation prefix of "hip" to CMAKE_PREFIX_PATH or set "hip_DIR"
  to a directory containing one of the above files.  If "hip" provides a
  separate development package or SDK, be sure it has been installed.
Call Stack (most recent call first):
  /opt/rocm/rocfft/lib/cmake/rocfft/rocfft-config.cmake:89 (find_dependency)
  cmake/public/LoadHIP.cmake:131 (find_package)
  cmake/public/LoadHIP.cmake:169 (find_package_and_print_version)
  cmake/Dependencies.cmake:995 (include)
  CMakeLists.txt:411 (include)

FindHIP.cmake is installed on the system but Findhip.cmake is not.
How to reproduce

Call find_package(rocfft) in a cmake project.

Environment

Hardware
description

GPU
device string

CPU
device string

Software
version

ROCK
v3.5.1

ROCR
v3.5.0

HCC
N/A

Library
v0.0

ROCFFT
v3.5.0

Downstream issue: https://github.com/pytorch/pytorch/issues/41886

Closing this issue since this does not directly pertain to this repo but rather the lack of functionality in FindHIP.cmake in the HIP package.


iOS app failing to run after I upgraded the package to version 2.2.8

Target Platform

iOS
Android

Target Application
React Native app
Problem Description
When starting the RN mobile app in a iOS simulator the error below is thrown:
Error: Unable to resolve module AccessibilityInfo from node_modules/adaptivecards-reactnative/node_modules/react-native/Libraries/react-native/react-native-implementation.js: AccessibilityInfo could not be found within the project.
See the screenshot below:
Screenshot

Card JSON
Please provide the JSON of the Card that is being rendered
Sample Code
Please provide any relevant code samples to help reproduce the issue
Version of SDK
React: v. 16.13.1
React Native: v. 0.63.3
adaptivecards-reactnative: v. 2.2.8
npm: v. 7.7.6

Please note the we are getting similar error message when building the app on MS App Center. See below:
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.182.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
Generating script.
========================== Starting Command Output ===========================
[command]/bin/bash --noprofile --norc /Users/runner/work/_temp/4208411b-cf16-4cac-aced-ad4cd05a3b7d.sh
Found index.js for ReactNative index.
warning: the transform cache was reset.
Welcome to React Native!
Learn once, write anywhere
error Unable to resolve module AccessibilityInfo from node_modules/adaptivecards-reactnative/node_modules/react-native/Libraries/react-native/react-native-implementation.js: AccessibilityInfo could not be found within the project.
If you are sure the module exists, try these steps:

Clear watchman watches: watchman watch-del-all
Delete node_modules: rm -rf node_modules and run yarn install
Reset Metro's cache: yarn start --reset-cache
Remove the cache: rm -rf /tmp/metro-*. Run CLI with --verbose flag for more details.
Error: Unable to resolve module AccessibilityInfo from node_modules/adaptivecards-reactnative/node_modules/react-native/Libraries/react-native/react-native-implementation.js: AccessibilityInfo could not be found within the project.

If you are sure the module exists, try these steps:

Clear watchman watches: watchman watch-del-all
Delete node_modules: rm -rf node_modules and run yarn install
Reset Metro's cache: yarn start --reset-cache
Remove the cache: rm -rf /tmp/metro-*
at ModuleResolver.resolveDependency (/Users/runner/work/1/s/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:186:15)
at ResolutionRequest.resolveDependency (/Users/runner/work/1/s/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
at DependencyGraph.resolveDependency (/Users/runner/work/1/s/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
at Object.resolve (/Users/runner/work/1/s/node_modules/metro/src/lib/transformHelpers.js:267:42)
at /Users/runner/work/1/s/node_modules/metro/src/DeltaBundler/traverseDependencies.js:434:31
at Array.map ()
at resolveDependencies (/Users/runner/work/1/s/node_modules/metro/src/DeltaBundler/traverseDependencies.js:431:18)
at /Users/runner/work/1/s/node_modules/metro/src/DeltaBundler/traverseDependencies.js:275:33
at Generator.next ()
at asyncGeneratorStep (/Users/runner/work/1/s/node_modules/metro/src/DeltaBundler/traverseDependencies.js:87:24)
##[error]Bash exited with code '1'.

@IbrahimSulai Could you take a look at this one? Thanks!

@RebeccaAnne, @IbrahimSulai
Please note that as an interim solution, I am deleting the node_modules folder within the adaptivecards-reactnative package folder post install:
"postinstall": "rm -rf ./node_modules/adaptivecards-reactnative/node_modules"

Hi @UncleZen - the ReactNative renderer is an open-source project. In order to get help, please open the bug in the repo for that project specifically. Thanks!
https://github.com/bigthinkcode/adaptivecards


Components containing Sass

I get a parse error if one of my components contains sass/scss. Is there a way to have either sveld preprocess or just ignore the styles section?

Why even is the css being parsed?

This should be working now in 0.8.0. The style block gets stripped away using regex before parsing. Feel free to reopen if it's still not working for you. Thanks!


[Unified Recorder] Created recordings are owned by root user on Linux (WSL 2)

Operating system: Linux <IP_ADDRESS>-microsoft-standard-WSL2 # 1 SMP x86_64 GNU/Linux
Does not appear to be an issue on Codespaces

Describe the bug
When recordings are created using the Unified Recorder docker image (e.g. using dev-tool run...) they are owned by root instead of the user that ran the command initially.
To Reproduce
Steps to reproduce the behavior:

In the testing-recorder-new package, clean out the recordings directory, then run TEST_MODE=record rushx test:node to generate new recordings.
Observe that everything in the recordings folder is owned by root

Expected behavior
The created recordings are owned by the current user.
Additional context
This issue can most likely be fixed by specifying a user and group ID when dev-tool calls docker run on Linux only (and maybe macOS?).

When the test-proxy container is run as a non-root user, the server can't access the HTTPS dev certificates and so fails to start, so fixing this will be a bit more involved than I expected and may require changes to the test-proxy docker image.


Add intresting CSS animation project

1. Description of the Feature Request
A CSS project idea for creating a "cigarette rolling form." This project could serve as a creative exercise for students to practice layout, styling, and form creation skills using CSS. It would offer hands-on experience with CSS properties for form styling and could make learning more engaging.
2. Acceptance Criteria

[ ] A project description that explains the objective (creating a cigarette rolling with text) is available.
[ ] Instructions for students on how to structure the HTML and CSS for the form are included.
[ ] CSS styling tips for form aesthetics, layout, and interactive elements are provided.

3. Additional Information
This project could be added to the curriculum under CSS exercises. It would allow students to explore unique form designs, enhancing their understanding of CSS styling in creative ways.

@TheOdinProject/html-css Can someone take a look please

ok

this assignment would look great if Odin Project Approves :)


Support on adding new decoding tables for NFT Trades in Solana

Provide the example query you'd like to add
I want to contribute and planning to add example NFT trade in Solana here. 2 largest marketplaces like MagicEden & Tensor.
There are a few decoded instruction_calls(call in dune) I would love to add here, hence my first question, is there any plans to add decoded tables?
If so, how can for instance I can help to add these decoded calls into CryptoHouse as well?
Tensor
TSWAPaqyCSx2KABk68Shruf4rp7CxcNi8hAsbdwmHbN

v1: buyNft
v1: buySingleListing
v1: sellNftTokenPool

TCMPhJdwDryooaGtiocG1u3xcYbRpiJzb283XfCZsDp
4. v2: takeBidFullMeta
5. v2: takeBidMetaHash
6. v2: buy
Does the view need a materialized view?
Not Sure

We have plans on adding the instructions table first, then we can look into decoded tables after (possible with a materialized view)
the ideal would be to be able to do decoding right in clickhouse through a UDF


Taylor/exact type

:tada: This PR is included in version 6.0.69 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


laggy rpi zero 2 w

Tested the image with the Pi4 and works perfectly. But the image for the rpi zero 2 w it's laggy making it non functional.
Is there anything I can do to improve the performance?

using a OnePlus 12 with latest android version, 14.

Same. Mine was very hot and eventually started to boot loop faster and faster.

Yeah, multiple people have reported similar issues with RPi 2 W. Someone with the issues need to debug what's going on. #66 has some more discussion around an similar issue.

Tested with another car, this time is a Volkswagen Polo and works by far better.
The first car was a Volkswagen Scirocco, newer by a couple of years, I was expecting to work better on a newer car.
So, I'd say it's something related to the car, maybe the power supply?

Tested with another car, this time is a Volkswagen Polo and works by far better. The first car was a Volkswagen Scirocco, newer by a couple of years, I was expecting to work better on a newer car.

I'm running mine on a 2017 VW Golf R. It has the MIB 2.0 system. https://imgur.com/2tKXyQ6

If it helps, 0.31 didn't have the same issues. It had more issues connecting but once connected it was rock solid stable. 0.40 connected much more reliably but it's often virtually unusable on my pi zero 2 w. I can cope with the lag, it's the choppy audio that makes it unusable. So far using a pi 4 seems much better.
(Using a mg5 EV)

I tested 0.31 and works way more better with the same setup, without extreme lag, so now it's usable!

This is very curious. Can you try latest main branch version? I'd like to pinpoint if the reason is because of the use of "dongle mode" or some other change that went in between? It'd help a lot if we can identify that.

Sure. I'll give it a try and I'll let you know

Sorry not in a position to compile this at the moment, but happy to try a prebuilt version.

You can use rha artifacts from https://github.com/nisargjhaveri/WirelessAndroidAutoDongle/actions/runs/9421948282

I'm flashing it and will test it on my 1 hour drive :) (today)

The image seems to not be properly configured:

On Windows with raspberry img burner tool it flashes just fine

Just drove for an hour and i could feel no lag.
Touch was fine and audio also.
Was using Maps and Spotify

3the test and laggy. Dont know what has been changed 🤷
Laggy interface and laggy audio

Tested a couple of times; way more fluid than the v.0.4.0 but still laggy. Some chunks get lost and spotify is not fluid. Still usable, but not fluid enough to finish a song without any jump.
Second time had a better experience than the first.
May the temperature be related?

Okay, this is getting even more interesting. I went through the changes since 0.3.1 and nothing apparent is coming to mind that can cause this. If you have consistent lag in newer versions and no lag 0.3.1 consistently, you can try bisecting to figure out the change that causes this. This may require multiple trials and multiple builds though, I don't think all the builds would still be available in Github Actions. https://github.com/nisargjhaveri/WirelessAndroidAutoDongle/compare/v0.3.1...v0.4.0 should show all the changes between the two versions.

Tried this version, for a couple of hours long journeys and it seems to work fine. There may be a slight lag compared to a cable but it is useable and there is no choppy audio.

Glad that the latest version seems to be better. I'll create a new release.
Btw, between 0.4.0 had the dongle mode as default. Both 0.3.1 and the latest main have phone-first connection as default. Maybe that is messing something and causing the lag?


Support pagination in GET /users API

Coverage increased (+0.02%) to 56.135% when pulling 539c0375a1b43b10b873514b5f0a7733ca9cc010 on ywk253100:170612_user into 83be92f1f04cb4058cee8b780a7948141716feb0 on vmware:master.


[BUG] Building v1.3.x images failed

Describe the bug (🐛 if you encounter this issue)
Building v1.3.x images failed because the repository is gone.
Expected behavior
Build v1.3.x images successfully.
Log or Support bundle
https://drone-pr.longhorn.io/longhorn/longhorn-instance-manager/362/1/3
Related issue:
https://github.com/longhorn/longhorn/issues/4191

https://download.opensuse.org/repositories/devel:/tools:/scm/
15.3 is removed

IIRC @yangchiu fixed this before, so probably this repo just missed.

15.3 was removed because it's end of life according to https://suse.slack.com/archives/C02D1374S3V/p1675818735801259
To figure out what packages we need in devel:tools:scm, I tried to remove this repo from both Dockerfile and Dockerfile.dapper, but dapper ci can succeed without any error after the removal.
So remove devel:tools:scm first and see if there's any errors in the daily regression

@yangchiu thanks for the quick analysis and fix!

@mantissahz Please close this if all images working fine. Thanks.

According to daily build https://ci.longhorn.io/job/public/job/v1.3.x/job/v1.3.x-longhorn-tests-sles-amd64/287/, the images should work fine.

Should the changes also go into the master branch?

Should the changes also go into the master branch?

Yes, @yangchiu is on that.


time: Parse does not cover all valid RFC1123Z dates

What version of Go are you using (go version)?

$ go version
go version go1.12.9 linux/amd64

Does this issue reproduce with the latest release?
Probably, as I got the same behavior at Playground.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/bodqhrohro/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/opt/gone"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go-1.12"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.12/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/data/progs/go/smstree/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build184744936=/tmp/go-build -gno-record-gcc-switches"

What did you do?

https://play.golang.org/p/aaUf5zpzKXj
What did you expect to see?
According to the standard, a one-digit day is valid.
      5.2.14  RFC-822 Date and Time Specification: RFC-822 Section 5

         The syntax for the date is hereby changed to:

            date = 1*2DIGIT month 2*4DIGIT

What did you see instead?
parsing time "Mon, 5 Aug 2019 17:21:53 +0300" as "Mon, 02 Jan 2006 15:04:05 -0700": cannot parse "5 Aug 2019 17:21:53 +0300" as "02"

RFC822 also allow day to be one or two digits:
date        =  1*2DIGIT month 2DIGIT        ; day month year

For date fix is trivial but we don't have placeholder for 2 or 4 digits year.
On another way RFC1123 say:
  All mail software SHOULD use 4-digit years in dates, to ease
         the transition to the next century.

So maybe its not needed to implement it.

This is unfortunate, but it's been that way since CL 196090, 9½(!) years ago.
CC @robpike, but I don't think we can change the constant now — at best, perhaps we could add a new constant and document the difference.

FWIW, you can define your own constant without the zero padding. That can parse both zero padded and single digit days. https://play.golang.org/p/gTZHbhp7J5C

@agnivade I already did https://github.com/bodqhrohro/smstree/commit/5f28f5b794faa7a8c70dd1b375f4df72e94b146a

I think the compatibility guidelines make it hard to fix this constant. We could add another one, but I don't think it's worth it. As already said, it's easy to write one's own.

Okay, but it would be good to add a notice to documentation, that the constants don't completely conform the standards and should be used with caution. I was lucky to discover it this early, but others may be less lucky.

This seems related to #20869.
Note that the documentation already explicitly says "RFC3339, RFC822, RFC822Z, RFC1123, and RFC1123Z are useful for formatting; when used with time.Parse they do not accept all the time formats permitted by the RFCs." (https://golang.org/pkg/time/#pkg-constants).
I don't really see anything else to do here.

the documentation already explicitly says

Didn't notice that, sorry. Then yes, there's nothing to do right now. Though, would it be added in the roadmap for a next major release, if it is planned already?

Then yes, there's nothing to do right now.

Given that at least three of us chimed in on this issue without noticing the documentation, I'd say that the documentation is not very discoverable — that particular section is so verbose that this (perhaps important) detail ended up buried.
That said, I don't see a way to make it more concise without dropping something equally important, so closing.


Issue: Open input Device

2015-01-11 20:17:29.697 Floadt[35194:2459976] Error open input device
I repeatedly get this issue after closing the RRMessageController after the first time. It works swimmingly the first time but after that it fails to open and shows this issue. This is on the iOS simulator.

Hi, that à normal, because i use avfoundation do you need à real device with à caméra. I Will make my possible to fix it.


How to debug golang code?

Hi Guys,
Hover is great tool, I use vscode on windows11 and now I can debug dart code, my vscode debug profile
tasks.json
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "hover build windows",
            "type": "shell",
            "command": "hover build windows --debug",
            "problemMatcher": [
                "$go"
            ]
        }
    ]
}

launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Flutter Desktop App",
            "type": "dart",
            "request": "launch",
            "program": "lib/main_desktop.dart",
            "args": [
                "--use-application-binary",
                "go/build/outputs/windows-debug_unopt/test.exe"
            ],
            "preLaunchTask": "hover build windows"
        }
    ]
}

Is there a way to debug goloang code?
Thanks

Humm not realy,
I'm using this when working on the golang embedder: https://github.com/go-flutter-desktop/go-flutter/wiki/Setting-up-hover-to-use-a-home-made-version-of-'go-flutter'.
I've never tried to make to make the go code "debug-able" in vscode


Funky Boy[GSSOC'23]

Title and Issue number

Funky Boy
Issue no. #3626
https://github.com/pranjay-poddar/Dev-Geeks/assets/114172928/01b7a945-3416-495f-b93f-e47f676ad50f
Please assign me the issue
Close #3626

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

@MohitGupta121 @TusharKesarwani @pranjay-poddar Please take a review of my PR & merge it.


Remove failing ci job & update with upstream

Description
Remove failing build step that builds a test version to a private repo.
It's not needed as that developer is absent and the deploy step fails.
Also added the following misc fixes/changes into this PR:

Fix the play on Jellyfin/Emby button after previous merge
Only request Tautulli watch data for Plex media servers (to avoid error in logs)
Updated with latest upstream

Screenshot (if UI-related)
To-Dos

[x] Successful build yarn build

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

v1.2.0
GitHub release

Your semantic-release bot :package::rocket:


Traffic is not being distributed

I am not sure what I am doing wrong. I've followed the documentation and setup each of my instances as I understand they should be setup. I am exporting the following:
        export CLUSTER_DISCOVERY_URL=$MONGO_URL
        export CLUSTER_SERVICE="web"
        export CLUSTER_BALANCER_URL=$ROOT_URL

I have even tried exporting the following:
       export CLUSTER_ENDPOINT_URL=$ROOT_URL
       export CLUSTER_SELF_WEIGHT="0.333"

I have tried changing the service name and the weight. Kadira is seeing the different hosts just fine but the traffic isn't being distributed. I've tried loading the app in the browser, removing the cluster cookie and refreshing the browser, but no matter how many times I do this I keep getting the same endpoint hash.
I've also tried hitting the server with a load test using meteor down and according to Kadira all the traffic is being handled by the primary app server, the server that sits at the primary domain.
Any insight on this would be great. Thanks in advance

Even setting:
       export CLUSTER_SELF_WEIGHT="0"

doesn't force the traffic to be proxied to another instance.

Seems like it was an nginx issue. If I run the meteor-down test against one of the other servers in the cluster it distributes the traffic just fine.
My apologies for filing a false issue.

@fredevery what was the nginx issue and how did you solve it?


C4GT Community: Basic Details of [Devansh Verma]

Ticket Contents
Description
Please provide the following basic details to help us understand your background and context better.

Name:
GitHub Username:
LinkedIn Profile:
College/University:
If you feel comfortable, you can also provide additional information such as your area of expertise or any specific information you'd like to share.

Goals
Name: Devansh Verma
GitHub Username: https://github.com/Invincible1602/C4GT
LinkedIn Profile: https://www.linkedin.com/in/devansh-verma-74aa16283/
College: IIIT Lucknow
Implementation Details
To implement the changes in the Community.md file on the GitHub repository (https://github.com/Code4GovTech/C4GT/blob/main/Community.md), follow these steps:

Fork the Repository:

Visit the repository (https://github.com/Code4GovTech/C4GT).
Click the "Fork" button in the upper right corner to create a fork of the repository in your GitHub account.

Clone Your Fork:

Open a terminal or command prompt.
Run the following command to clone your fork to your local machine:

     git clone https://github.com/your-username/C4GT.git

Navigate to the Repository:

Change into the repository directory:

    cd C4GT

Edit the Community.md File:

Open the Community.md file in a text editor. You can use any code editor or a simple text editor.
Locate the existing table and replace the details with your own:

        Name
        Your Name

        GitHub
        https://github.com/your-username

        LinkedIn
        https://www.linkedin.com/in/your-linkedin

        College
        Your College/University

Save Changes:

Save the changes to the Community.md file.

Click on the "New pull request" button.
Ensure the base repository is Code4GovTech/C4GT and the base branch is main.
Ensure the head repository is your fork and the compare branch is main.
Click "Create pull request" and provide a meaningful title and description.
Click "Create pull request" again to submit the pull request.
Your changes will now be submitted as a pull request to the original repository, and the maintainers can review and merge them.

Product Name
C4GT
Organisation Name
C4GT
Tech Skills Needed
Markdown
Mentor(s)
@Shruti3004
Complexity
Beginner
Category
Documentation

Can you assign this ?


Icons Needed

@nicolasmroberts We need icons for Pet, Other Features, Fabrics, Sed Strat Section and Sed Interval.
Also note you have SedStructure_pressed & SedStructure_pressed_1 instead of simpleySedStructure.
Even though we don't have pages for these yet I'm using the buttons in the Spot List to show the info that has been filled out, as is in SS1 and @panamint55 requested, in downloaded project. See #121

@nicolasmroberts Still missing icons for the following - mostly just the transparent icon
other_features
pet
fabrics
strat_section
sed interval
sed lithologies
sed bedding
sed structures
sed diagenesis
sed fossils
sed interpretations

@jessicagood Here are the new icons you asked for, including a Button, Button_pressed, _pressed, and _transparent version of each.
StraboIcons_v7.zip

@nicolasmroberts

Can you name LineButton_pressed copy something like LineFreehandButton_pressed instead? And the associated files.
There are also a lot of PolygonFreehandButton copy files where the icon looks like the strat column. These could be removed.
You added some Artboard files which I don't think we need either.
I see you added Sed to the beginning of the file names for sed icons but it looks like you still have Bedding, Lithologies_pressed, Fossil, and Diagenesis files which can now be removed.
SedInterpretation_1, SedStructure_1: Shouldn't they not have the _1?

I want to get to the point where I can just drop in your icon zip files if icons are changed or added so that's why we need the changes made in your master file, not just in ours.

@nicolasmroberts Can I also get an icon that will go in the Notebook panel footer which will pop up a list of additional pages? Thanks.

@jessicagood new set of icons with all the comments you had above.
Changes to name:
Freehand line symbol is now called “LineFreehandButton” and “LineFreehandButton_pressed”
Strat spot symbols are called “StratPolygon_pressed”, “StratLine_pressed”,”StratPoint_pressed” “StratLayer_pressed”
"OtherFeature" family of symbols is now called "MoreTools" -- this is the symbol in the notebook page to access the other tools not in the notebook toolbar. There is currently no symbol anymore for "OtherFeature". Working on that.
"VelumButton" has been completely redrawn in anticipation of that feature.
StraboIcons_v8.zip

@nicolasmroberts Ok, don't think I saw this. Will check out it out. There is a close button but still need a button to open the spot in the notebook page from the image gallery slideshow. Or maybe this should just be the notebook icon?

In v8 icons all of the Buttons have a white background instead of transparent. I think we need it transparent.

That's an export error on my part from illustrator. And RE: #78, they are in there -- they are called "StratPoint_pressed", "StratLine_pressed", "StratPolygon_pressed"

StraboIconV8_Transparent.zip

@jessicagood the .zip folder attached above should fix the issue

@nicolasmroberts Ok, great! And what about point, lines and polys mapped on an image baseamps (also from #78)? I had separate icons for them too in SS1. Do you want those in SS2? And are they already in the icon zip as well?

@jessicagood ah right. Here is a new version with those included: "ImageLine_pressed", "imagePoint_pressed", etc.
StraboIcons_v8_transperant2.zip

@nicolasmroberts I added these with commit 3bc912a but still see the following problems:

Missing icons for Other Features
Missing icons for Sed Interval
layersButton starts with a lowercase where as the rest start with a capital
SedBeding_pressed misspelled
SedStrabColumn misspelled

StraboIcons_v8.2.zip
Here are corrections:

all spelling listed was corrected
StratLayer family of buttons was changed to 'SedInterval' to better fit the naming scheme
OtherFeatures family of buttons was added.

@nicolasmroberts Artboard snuck back in there but I just deleted those files so no need a for new version at this point. Looking good so closing this issue.


Corrupted outfile

I converted a y4m into vvc using vvenc, and then I tried to decode it back to yuv to make sure it had encoded correctly.
The outputted yuv is corrupted, and I have been unable to fix it. Also, I have tried encoding the vvc from a normal rawvideo yuv and had the same result.
Does anyone have any recommendations or solutions? Are there any test files I can use for reference?
Thank you,
Any help would be appreciated.
Link to zip with all of the video files: https://drive.google.com/file/d/1_RpywgLN7A9U6lEP34_WLHzUdRAYWCXb/view?usp=sharing

Hallo,
Can you post some screenshots of the corrupted files?
Did you have a look at the following issue #4?
vvenc does not understand y4m, so you'd need at least need to strip the header to convert it to raw yuv.
We might add bitrate conversion into the decoder as it seems to cause alot of confusion, but for now please check if you properly interpret the output format (yuv420p or yuv420p10le).

Here are screenshots of the corrupted output files. I will try again with a raw yuv and see if anything changes.

It looks alot like you're trying to view a yuv420p10le (10 bit-depth packad into 2 bytes) as yuv420p (8 bit-depth packed into a byte).
How are you viewing the files? ffmpeg (and, by extension, ffplay), should understand yuv420p10le.
If you really need the output to be 8-bit, you could encode the file with 8 bit internal bit-depth, but this only works in the full featured encoder right now (fix coming soon). Otherwise you could use ffmpeg to convert from yuv420p10le to yuv420p.

I am viewing the files in YUView. When you said that it was viewing in 8 bit, I changed it to viewing in 10 bit and got this.

which is closer but still corrupted.

The rest of the problem should be the y4m/yuv. Could you give it a try?

I just finished encoding and decoding using a raw yuv, and it worked great! Thank you very much for the assistance.


[Snyk] Security upgrade setuptools from 40.5.0 to 70.0.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):

sdk/python/v1beta1/requirements.txt

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Control of Generation of Code ('Code Injection')
[//]: # 'snyk:metadata:{"customTemplate":{"variablesUsed":[],"fieldsUsed":[]},"dependencies":[{"name":"setuptools","from":"40.5.0","to":"70.0.0"}],"env":"prod","issuesToFix":[{"exploit_maturity":"Proof of Concept","id":"SNYK-PYTHON-SETUPTOOLS-7448482","priority_score":768,"priority_score_factors":[{"type":"exploit","label":"Proof of Concept","score":107},{"type":"freshness","label":true,"score":71},{"type":"fixability","label":true,"score":214},{"type":"cvssScore","label":"7.5","score":375},{"type":"scoreVersion","label":"v1","score":1}],"severity":"high","title":"Improper Control of Generation of Code ('Code Injection')"}],"prId":"2e6c3ed0-c311-4c65-9138-bfa8f124d57d","prPublicId":"2e6c3ed0-c311-4c65-9138-bfa8f124d57d","packageManager":"pip","priorityScoreList":[768],"projectPublicId":"789a9fab-670a-4ddd-bb4d-44930a7e37e3","projectUrl":"https://app.snyk.io/org/ryanhammerdick/project/789a9fab-670a-4ddd-bb4d-44930a7e37e3?utm_source=github&utm_medium=referral&page=fix-pr","prType":"fix","templateFieldSources":{"branchName":"default","commitMessage":"default","description":"default","title":"default"},"templateVariants":["updated-fix-title","priorityScore"],"type":"auto","upgrade":[],"vulns":["SNYK-PYTHON-SETUPTOOLS-7448482"],"patch":[],"isBreakingChange":false,"remediationStrategy":"vuln"}'

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 72.974%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
3116

Relevant Lines:
4270

💛  - Coveralls


createServer doesn't apply all my config

Starting by port, that i had to specify manualy when i call to listen method, other configs like open, appIndex and others doesn't apply... why?
This is my config
const configServer = {
	open: true,
	appIndex: 'demo/index.html',
	watch: true,
	nodeResolve: true,
	plugins: [], //Assigned later
	fileExtensions: ['.scss', '.less', '.styl'],
	moduleDirs: ['node_modules', 'vendor'],
}

So when I use createServer (config) my server doesn't work the way I want, with startServer it works!

What are you expecting createServer to do with the port? It doesn't start the server, so it can't set up a listen with the port. That's what startServer is for. Opening the browser is also something which just startServer does. If that's what you need, I recommend using that instead.

My opinion is: createServer and startServer should only be different because the first function only creates and configures the server and the second one also starts it, but the full configuration must be applied and the server will be ready to listen, waiting for the manual request

We can't apply the port configuration if the server did not start yet, that's the point of the separate functions. We can't change how node's HTTP server works unfortunately.


[Bug] Cloudwatch datasource with "Assume Role ARN" doesn't work in Openshift

Describe the bug
Getting these logs during Cloudwatch datasource with "Assume Role ARN" configuration in Openshift:
failed to call cloudwatch:ListMetrics: NoCredentialProviders: no valid providers in chain\ncaused by: EnvAccessKeyNotFound:
failed to find credentials in the environment.\nSharedCredsLoad: failed to load profile, .\nEC2RoleRequestError:
no EC2 instance role found\ncaused by: RequestError:
send request failed\ncaused by: Get \"http://<IP_ADDRESS>/latest/meta-data/iam/security-credentials/\":
dial tcp <IP_ADDRESS>:80: connect: connection refused"

<IP_ADDRESS>:80 is available from Openshift node, but not from Grafana pod/container.
The problem could probably have been solved using the hostNetwork: true:
https://bugzilla.redhat.com/show_bug.cgi?id=1745720
but there is no option to configure it (or configuration is ignored ?).
e.g. I tried to define it as:
spec:
  deployment:
    securityContext:
      hostNetwork: true

and
spec:
  securityContext:
    hostNetwork: true

The deployment, replicaset, pod were re-deployed, but there was no hostNetwork option.
It looks like the securityContext option is ignored.
Expected behavior
Cloudwatch datasource with "Assume Role ARN" works in Openshift.
Runtime (please complete the following information):

OS: Linux
Grafana Operator Version: 3.9.0
Environment: Openshift in AWS

Additional context
The same configuration (IAM role, grafana-operator, without hostNetwork: true) perfectly works in AWS EKS cluster.

I was able to rebuild operator and fix it.
Added hostNetwork option to deployment configuration.
hostNetwork: true should be used with DNSPolicy: ClusterFirstWithHostNet (pod default DNSPolicy is ClusterFirst)

Closing, fixed in #380, Thanks for contributing @alrf ! :+1:


[Bug]: Matcher error: received value must be a mock or spy function

Version
28.1.1
Steps to reproduce
Steps:

Clone my repo https://github.com/neophyt3/jest-esm-demo
npm install
node --experimental-vm-modules  ./node_modules/.bin/jest
You should see the error

Expected behavior
I expected the test to pass
Actual behavior
Received error: received value must be a mock or spy function
cli output:
pradeep@DESKTOP:~/workspace/nodejs/jest-esm$ node --experimental-vm-modules  ./node_modules/.bin/jest
(node:8724) ExperimentalWarning: VM Modules is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 FAIL  mods/__tests__/modA.test.js
  ✕ should call some service (3 ms)

  ● should call some service

    expect(received).toBeCalled()

    Matcher error: received value must be a mock or spy function

    Received has type:  function
    Received has value: [Function default]

      16 | it('should call some service', async () => {
      17 |   await modA();
    > 18 |   expect(someService).toBeCalled();
         |                       ^
      19 | });
      20 |

      at Object.<anonymous> (mods/__tests__/modA.test.js:18:23)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        0.237 s, estimated 1 s

Additional context
This is related to https://github.com/facebook/jest/issues/10025 I believe
I tried different variants below but none were helpful
// jest.mock('../../services/someService', () => ({
//   __esModule: true,
//   default: jest.fn(),
// }));

// jest.mock('../../services/someService');

jest.unstable_mockModule('../../services/index.js', () => ({
  someService: jest.fn(),
}));

Environment
pradeep@DESKTOP:~/workspace/nodejs/jest-esm$ uname -a
Linux DESKTOP <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
pradeep@DESKTOP:~/workspace/nodejs/jest-esm$ node -v
v18.3.0
pradeep@DESKTOP:~/workspace/nodejs/jest-esm$ npm -v
8.11.0
pradeep@DESKTOP:~/workspace/nodejs/jest-esm$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal

Closing this.. thnx to @mrazauskas  for the fix


DevDB 23Q2 Corrections

Starting this issue as a log for anything that arises during this correction cycle

[ ] Per SL, remove all logic around assigning manual corrections if "% test %" or "%bis%test%" in job_dec

I’m gathering our first round of corrections as we speak, but I noticed something in the manual corrections table. There are 18 corrections deleting records because the “job_desc suggest this is a test record.” I think I’ve found this issue before. These records are actually not test records and the code that is removing them from the database should be deleted. The existence of the phrase “test” in the job description is not sufficient to classify something as a test record.

Per SL

Another issue just popped up. I’m compiling all of the manual corrections that the team did last week and found that there are a bunch of records that were flagged as having geography issues, but that had been previously corrected. In fact, many of them had been corrected multiple times, but they were not being applied and weren’t in the corrections_not_applied.csv. Is there any reason why this would be happening for the following records?

Seems that in_water function is broken. Looking at corrections_geom table in latest build in edm-data, in_water column is only either true or NULL. This results in corrections not being applied even if bbl is null (one of that and in_water must be true) when geom is not in_water, and in corrections not being logged as applied or not when not in_water


how to add app roles using powershell core?

Hi,
I can't seem to find any official documentation on how to add the app roles with Powershell Core to my app registration. Could you maybe help me in the right direction? My results end up in unworking code until now.

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

ID: 9939fc33-8762-3104-eae0-08250c508100
Version Independent ID: 9c6fa664-df37-40aa-f46e-9e59f79ae215
Content: Add app roles in your Azure Active Directory-registered app and receive them in the token - Microsoft identity platform
Content Source: articles/active-directory/develop/howto-add-app-roles-in-azure-ad-apps.md
Service: active-directory
Sub-service: develop
GitHub Login: @kkrishna
Microsoft Alias: kkrishna

Thank you for your feedback, currently we're looking into this issue and will get back to you as soon as possible,
@santo2

hey @santo2 is this documentation what you're looking for? https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/roles-assign-powershell
you'll need to use the azure ad powershell module, but the process for assigning role assignments will be the same as the process for assigning custom role definitions.
See this cmdlet for more information on how to get role assignment information.

Hi FrankHu, thanks for your reply, does this also work with Powershell Core? It's getting very hard to find the correct way of working with powershell these days. I can't use the AZ modules with powershell 5, I can't use AzureADPreview with Powershell Core 6? :)
On import, I'm getting this error
Import-Module AzureADPreview
Could not load file or assembly 'System.Windows.Forms, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.

If that is the case in regards to powershell core then you may need to upgrade your powershell version as the azuredpreview version is the only one that supports this.
If you want to try to utilize the microosft graph api with rest you can do that. That will be much more involved, but that is the only path if you need to use powershell core. Note that this method is unsupported and not the recommended way, it is recommended to use the azuread powershell cmdlets using a supported veresion of powershell.
https://www.michev.info/Blog/Post/2339/azure-ad-powershell-module-with-support-for-powershell-core
https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/roles-assign-graph
Please let us know if you have anymore questions, if it's related to troubleshooting please put it in the forums here : https://docs.microsoft.com/answers/index.html I will be now closing this issue by end of day today.

I'm sorry, what do you mean with upgrading my powershell version? You mean going back to the older windows powershell 5, and running it from there? Because I did try to use the AzureADPreview, but that didn't seem to add anything useful in powershell core.

@santo2 if you're still having trouble with this please open a Q&A thread for troubleshooting there, I'm not having any issues utilizing the aad powershell module with my version of windows powershell
Please include your powershell version in the Q&A post using $PSVersionTable at the link : https://docs.microsoft.com/answers/index.html


Add wallet_hasPlugin or similar method

There's no dedicated way for domains to check if a plugin is installed. We should add an external wallet_ RPC method to check whether a plugin is installed, and potentially get metadata about e.g. the version and so on.

This could be a privacy leak. When is it valuable to detect a plugin without just asking permission to interact with it?

This suggestion originally came from @oed. The goal is for consumers of our API to have a means of checking whether a plugin is installed without initiating the installation or permission request flow. This would enable better UX, e.g. by not displaying the Connect button if the desired version of the plugin is installed (down the line when we make versioning info available.)
Always reinstalling the plugin when the permission for it is requested is (as discussed internally) a stopgap measure. However, using wallet_requestPermissions to check if a plugin is installed  would still re-request the permission for the plugin. Whether we'll change that behavior in the necessary timeframe or at all is an open question.
Furthermore, in the future we'll want to let API consumers know what version of a plugin is installed, and we'll need something like wallet_getPluginManifest to accomplish that. Alternatively, we could add that information the plugin permission itself, but that seems like poor separation of concerns.
Finally, this would not cause any privacy leaks because we already allow API consumers to call wallet_getPermissions.

@danfinlay Right now when you ask for permission the install plugin is always displayed. If in the future that is only displayed if you have not yet been granted permission I think that would be fine as well. At least for my use case.

Right now when you ask for permission the install plugin is always displayed. If in the future that is only displayed if you have not yet been granted permission I think that would be fine as well. At least for my use case.

Yes I agree this is fine. We could already easily do a check: If the plugin is installed, only ask the user to connect to it. Right now we always re-install really just as a developer convenience feature, but we should probably replace it as soon as we have a reasonable plugin-update mechanism (maybe the mm-plugin serve API could host a websocket that notifies it to reload for now).

Furthermore, in the future we'll want to let API consumers know what version of a plugin is installed

I'm not certain how we'll address this, but it may be more like a dependency graph: Let dapps/plugins specify the versions they want. Maybe updates are always hosted at new addresses, or maybe we define a special wallet-plugin ENS content type that includes a map of versions, so that a plugin origin can specify a variety of versions that can be referenced.

Yes I agree this is fine. We could already easily do a check: If the plugin is installed, only ask the user to connect to it.

This is fine if: The user is only asked the first time they use app A that uses plugin B. The second time the user comes to app A they should not have to reaffirm that app A can use plugin B (it's fine if there is some timeout here).

what is currently the best way to check whether a user has previously granted a given permission for the current domain?

@awalias I'll make sure this is added to the Wiki where appropriate but for now:

We follow the spec we've made: EIP 2255

To know whether you have a certain permission, send a wallet_getPermissions request and search over the returned array of permissions objects.

The permission name is indicated by the parentCapability field.
You can also attempt to call the corresponding method. If you don't have the permission, an EIP 1193 Unauthorized error will be returned, with error.code === 4001.
These methods will not tell you if you've previously granted the permission and it's later been removed.

If you need to know if you've previously granted the permission at all - even if it's been removed - you have to keep track of that information.

Does this answer your question?

thanks @rekmarks , I eventually got wallet_getPermissions to work - my problem was that simply having import Web3 from 'web3'<EMAIL_ADDRESS>in react was causing the ethereum.send with wallet_getPermissions to return undefined. I'm assuming it does something to the provider, but definitely not playing nice together atm. I switched to ethers.js for now and seems to be working ok.

This issue has been updated to say that plugins must be "installed and permitted" in order to be returned by the soon-to-be-implemented wallet_getPlugins method.


Update README.md

I found some of this text confusing to read and saw your commit message asking for help on updating this text, so thought I would suggest some changes.

Thanks for PR. Merged.

Thanks for PR. Merged.


Some Tailwind CSS classes seem to be excluded from stylesheet generation

Environment
Nuxt project info:

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.7.2
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Version
v2.10.0
Reproduction
https://stackblitz.com/edit/nuxt-ui-mjvv7w?file=app.vue
Description
In the playground above the aspect-square class does not apply. You can change it to aspect-[1/1] and see that that custom selector does get picked up.
Additional context
Came across this issue from a user reporting that the FormKit Regenesis theme was not working in their Nuxt application. It seems that some TW classes (I have not been able to determine a pattern) are not being parsed / picked up by Tailwind when using Nuxt UI.
This is the original user's demo showing the broken theme: https://stackblitz.com/edit/github-buke4g-se4kia
When I switched out @nuxt/ui for @nuxt/tailwindcss the classes were all parsed correctly: https://stackblitz.com/edit/github-buke4g-f6wytu?file=nuxt.config.ts
Logs
No response

This seems to be a duplicate of #571.

Did you manage to fix your issue by either specifying the base aspectRatio config or by using the ones from the plugin?

I'm going to dig around and see if there are other failing classes. There was certainly more missing in the reproduction we got from one of our users than just the aspect-ratio missing but I don't know off hand what those classes are. I'll get back to you.
I also commented in #571 — I don't know that legacy Safari usage is high enough to justify not using the core aspect-ratio classes. We will not be shipping plugin-dependent ones in our 1st-party themes but I understand that "significant usage" is relative per project and Nuxt may have a lower usage threshold that needs to be considered.

Ok, it actually is just an issue with the aspect-ratio classes so this is a duplicate of #571 and can be closed. Before and after screenshots of a find and replace in the theme for aspect-square with aspect-[1/1].
Before

After


Fix: Add dependabot alerts for security-related issues only

This change is

Let's close this - we'll open a new one when we've decided exactly how to move forward.


Runner.tags() Does Not Execute Scenarios Marked @ignore

In version 1.1.0 and higher, Runner.tags("@MyTest") will not execute scenarios that are tagged with both @MyTest and @ignore.  The result is that any scenario marked @ignore can never be executed.
This appears to be a change in behavior between 1.0.0 and 1.1.0.  In 1.0.0 and earlier, using Runner.tags("@MyTest") would execute all scenarios with @MyTest, even those that were also marked @ignore.
Impact
Our team uses @ignore to mark scenarios that should not be run during standard functional testing.  With 0.9.6, we are able to run those same scenarios during specialized testing - for example by marking them @Performance and invoking Runner.tags("@Performance"). This approach is no longer working as of 1.1.0.
Testing

Download and unpack karate-ignore.zip
Execute mvn test -Dtest=WithTags

Expected: The scenario is executed because the tag on the scenario matches the tag specified by the Runner
Actual: The scenario is skipped because it is marked @ignore

Execute mvn test "-Dkarate.options=--tags @MyTest" -Dtest=WithoutTags

Expected: The scenario is executed because the tag on the scenario matches the tag specified by the CLI options
Actual: The scenario is skipped because it is marked @ignore

Execute mvn test "-Dkarate.options=--tags @@ignore" -Dtest=WithoutTags

Expected: The scenario is executed because the tag on the scenario matches the tag specified by the CLI options
Actual: The scenario is skipped because it is marked @ignore

karate-gatling has similar behavior but is inconsistent.  Using karateFeature("classpath:mock/cats.feature@name=getAllCats") will execute all scenarios tagged @name=getAllCats, even those marked @ignore.  However, karateFeature("classpath:mock/cats.feature", "@name=getAllCats") will not execute scenarios tagged @ignore.  Even though those two statements seem to indicate the same intent, they result in different behavior.
Testing

Download and unpack karate-gatling-ignore.zip
Execute mvn clean test-compile gatling:test -Dgatling.simulationClass=mock.CatsKarateWorkingSimulation

Expected: The scenario is executed because the tag on the scenario matches the tag specified by karateFeature
Actual: The scenario is executed, and the test completes successfully

Execute mvn clean test-compile gatling:test -Dgatling.simulationClass=mock.CatsKarateBrokenSimulation

Expected: The scenario is executed because the tag on the scenario matches the tag specified by karateFeature
Actual: The scenario is skipped because it is marked @ignore and the test fails because no scenarios were executed

@packleader yes this is an intentional behavior change implemented in 1.1.0 / #1592 and I am closing this as a duplicate of #1817 - the solution should be simple. just choose another name instead of @ignore e.g. @skip and things will work the way they used to

Ah, that makes sense.  Thanks.


How to update dependencies

First of all, Thank you! This is the missing demo I have been searching for. Great job.
How do I update/add to the vendor dependencies in this project? dep ensure updates the existing dependencies and cause the build to fail.

dep ensure is the correct way to update dependencies. Perhaps a note in the README would help here.
So long as the Gopkg.lock and Gopkg.toml are in sync, this should not cause any changes. Running dep ensure -update will update existing dependencies (potentially causing failures).


Support deletion of SageMaker Notebook Instances

This addresses the merge conflict in https://github.com/gruntwork-io/cloud-nuke/pull/282 so that it can be merged.

Failing test is unrelated / known flaky.

Thanks for review! merging now!


[question] How to set top offset/margin - scrolling page?

Can I create "illusion" of scrolling by passing top offset/margin params? Eg. top: 200px.

If you know the width/height can you use clipRect to achieve this?
The instructions appear to be wrong, it looks like it should be top,left,width,height, so something like this might work.
clipRect=200%2C0%2C1024%2C2000


No default route when overriding mac with the tuning plugin

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I'm trying to use a macvlan-based network with a mac overridden using the tuning plugin. It kind of works, but there is no default route in the container. Simply removing the mac setting from the conflist (while leaving the tuning plugin reference) fixes the default route.
I don't think this is a problem in CNI, because cnitool shows identical output for both conflists (the only difference is the mac address).
Steps to reproduce the issue:
Run container with the following conflist:
{
    "cniVersion": "0.3.0",
    "name": "mynet",
    "plugins": [
      {
        "type": "macvlan",
        "master": "eth0",
        "ipam": {
          "type": "static",
          "addresses": [
            {
              "address": "<IP_ADDRESS>/24",
              "gateway": "<IP_ADDRESS>"
            }
          ],
          "routes": [
            { "dst": "<IP_ADDRESS>/0" }
          ]
        }
      },
      {
        "type": "tuning",
        "mac": "ba:c8:2b:a5:5c:50"
      }
    ]
}

Describe the results you received:
# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>   <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 eth0

Describe the results you expected:
# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>         <IP_ADDRESS>   <IP_ADDRESS>         UG    0      0        0 eth0
<IP_ADDRESS>   <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 eth0

Output of podman version:
Version:            1.4.4
RemoteAPI Version:  1
Go Version:         go1.10.3
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.10.3
  podman version: 1.4.4
host:
  BuildahVersion: 1.9.0
  Conmon:
    package: podman-1.4.4-2.el7.centos.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 0.3.0, commit: unknown'
  Distribution:
    distribution: '"centos"'
    version: "7"
  MemFree: 189935616
  MemTotal:<PHONE_NUMBER>6
  OCIRuntime:
    package: runc-1.0.0-64.rc8.el7.centos.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 12
  hostname: hostname
  kernel: 3.10.0-957.10.1.el7.x86_64
  os: linux
  rootless: false
  uptime: 967h 51m 55.78s (Approximately 40.29 days)
registries:
  blocked: null
  insecure: null
  search:
  - registry.access.redhat.com
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.centos.org
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 8
  GraphDriverName: overlay
  GraphOptions: null
  GraphRoot: /podman
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 61
  RunRoot: /var/run/containers/storage
  VolumePath: /volumes

@mccv1r0 Any clues here? We're not doing anything that would affect this part of CNI on the Podman end.

Using that conflist, every container using mynet will get the same mac address (assuming it even works; I've never tried it... I point it out in case someone in the future happens to find this issue.)  The runtime (i.e. podman) is meant to supply a unique mac address (which it gets from e.g. bash command line or some per-container config.)
I've reproduced the overall problem with macvlan and other (e.g. bridge) CNI plugins.  When the mac is specified, the default (and possibly other) routes don't seem to be set in the container.

FYI:
https://stackoverflow.com/questions/21018729/generate-mac-address-in-go

https://github.com/containernetworking/plugins/pull/364

Fixed upstream in plugins, so I think we're good to close


Subheadings in the class description not working

Hello! I'm trying to write long descriptions for the classes in the gem I'm working on, so I'd like to add section breaks to increase readability.
I had a look at the code for YARD itself and a couple of other gems to find out how to add subheadings. This turned out to be a RDoc style == tag. Unfortunately, nothing happens when I try the same in my repo.
Here's my code:
module SnowplowTracker
  # Creates the correctly structured JSONs for sending context or
  # self-describing events.
  #
  # == Usage
  # blah blah
  #
  # @api public
  # == Namespaced Tags
  #
  # In YARD 0.8.0+, tags can be namespaced using the '.' character.
  class SelfDescribingJson

Gemfile:
source 'https://rubygems.org'
gemspec

gem 'redcarpet', require: false
gem 'rubocop', '~> 0.57.0', require: false
gem 'simplecov', require: false
gem 'simplecov-lcov', require: false
gem 'yard', require: false

and my .yardopts:
--markup-provider=redcarpet
--markup=markdown
--no-private

Steps to reproduce
Running yard doc --no-private or yardoc --api public
Actual Output
This is the generated HTML:

Overview

Creates the correctly structured JSONs for sending context or
self-describing events.

== Usage
blah blah

== Namespaced Tags

In YARD 0.8.0+, tags can be namespaced using the '.' character.

Expected Output
I thought that the lines marked with == would become headers.

Overview

Creates the correctly structured JSONs for sending context or
self-describing events.

Usage

blah blah

Namespaced Tags

In YARD 0.8.0+, tags can be namespaced using the '.' character.

Environment details:

OS: Mac OS 11.6
Ruby version (ruby -v): 3.0.1
YARD version (yard -v): 0.9.26
Relevant software dependency/versions:

[Any 3rd party libs required to reproduce, omit if none]

I have read the Contributing Guide.
Thanks for your help!

I have just discovered that markdown does work to create subheadings! When I'd tested that, I'd used ###, which made the heading bold but not underlined like the other headings, so I thought it wasn't working.
I'm still not sure why the == syntax doesn't work, but at least my subheadings are here now. Happy for you to close this :).


tests for valid messages now also check the id of that message is cor…

added this for @bl0x to ensure that the test data covered the legacy hashing quirks for message ids.
as mentioned in this issue: https://github.com/ssbc/ssb-server/issues/696
test/data/test_messages.json now includes an id property, which is what the id should be. there is also hash field, which is the sha256 hash of the bytes of the stringification. If the message contains non-ascii these will be different, as they are in the case of the last message.

@dominictarr : The commit removes all the 'cap' entries. Was that intentional? Now one cannot verify the signatures in all cases.

oh dear. because the tests are passing... they shouldn't be passing if they are ignoring the cap.
good spotting @bl0x !
the false positive was because it was calling validate(state, cap, msg) but validate actually expects a validate(state, cap, feed_id) it was acting as if it was an unknown feed id. added a commit to make that throw.
also, fixed the tests, they definitely check the signatures now, and caps are preserved.

weird the travis build failed with:
npm ERR! Error: No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! ["1.1.1"]
npm ERR!     at installTargetsError (/home/travis/.nvm/v0.8.28/lib/node_modules/npm/lib/cache.js:719:10)
npm ERR!     at /home/travis/.nvm/v0.8.28/lib/node_modules/npm/lib/cache.js:641:10
npm ERR!     at saved (/home/travis/.nvm/v0.8.28/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR!     at Object.oncomplete (fs.js:302:15)

hmm, I notice the deps are a bit weird too

okay everything should be good now

uh no it has some problem with npm... but it's a really old npm, just gonna update it...

I mean drop old versions of node

@dominictarr Great! Now I can validate all messages accordingly taking their IDs into account. Thanks for fixing this up.

@bl0x no problem, please keep us posted how your implementation is going!

Cool! Is this ready for a review? Couldn't tell by the comments and wanted to make sure it was ready before diving in.


Fix module path component 1.4.x

Add tests to 1.4.x to test generation code from a sub-directory. These are the same tests that are already in master.

Heya, in 1.4 we're moving the blueprints to https://github.com/angular/devkit. These tests are moving there as well I think. @Brocco can you confirm?


Easey Design System Updates

Update Easey Design System with new features, shared components, and anything the EPA brings up

Add Sans Serif Font into the design system

duplicate see #2012


Consider isort as linter

Some of __init__.py imports are getting out of control, we should consider using https://pycqa.github.io/isort/ as hard linter and/or suggestion.

We recently opted to use ufmt as code formatter. It combines black and usort. AFAIK, isort had some issues on FB architecture. cc @NicolasHug
The final vote is still out, but if we go for it, I can send a PR adopting it here too.

Yes, ufmt was specifically made to match fb's internal arc lint.
If we expect pytorch/data to be modified from withing fbcode from time to time, I think it's much safe to keep fbcode linting and github linting in sync

Thanks to @pmeier , we have added pre-commit hook to run auto formatter. ufmt is also included to make everything sorted.
Closing this Issue.


#3019: try out golangci-lint action

Signed-off-by: warber<EMAIL_ADDRESS>

Superseeded by PR https://github.com/keptn/keptn/pull/3920


[question] Zwave network stall after pressing Zwave remote button

Using a Zwave remote to send a "Central Scene" to Home Assistant.  After pressing any button on the remote, HA sees the scene and sends a command back to zwavejsmqtt to turn on or off a light.  The problem is the command to toggle the light is stalled until these response attempts messages timeout.  Sometimes it's stalled/delayed, sometimes the command is just never executed.  Is there a way to avoid trying to update these remote devices after receiving the wake up notification?
Log sample when the button is pressed, but no other command during and/or after can be executed:
2021-02-20 20:08:35.307 INFO ZWAVE: Node 52: value notification: 91-0-scene-001 0
20:08:35.309 CNTRLR « [Node 052] received CentralScene notification {
"nodeId": 52,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0x8a0001"
}
20:08:35.334 CNTRLR « [Node 052] received wakeup notification
2021-02-20 20:08:35.337 INFO ZWAVE: Node 52 is now awake
20:08:35.343 CNTRLR [Node 052] The node is now awake.
2021-02-20 20:08:35.399 INFO ZWAVE: Node 52: value updated: 132-0-wakeUpInterval 0 => 0
2021-02-20 20:08:35.401 INFO ZWAVE: Node 52: value updated: 132-0-controllerNodeId 1 => 1
2021-02-20 20:08:35.452 INFO ZWAVE: Node 52: value updated: 132-0-wakeUpInterval 0 => 0
2021-02-20 20:08:35.453 INFO ZWAVE: Node 52: value updated: 132-0-controllerNodeId 1 => 1
20:08:39.603 CNTRLR [Node 052] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-02-20 20:08:42.634 INFO ZWAVE: Node 52: value notification: 91-0-scene-001 0
20:08:42.636 CNTRLR « [Node 052] received CentralScene notification {
"nodeId": 52,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0x8b0001"
}
20:08:42.661 CNTRLR [Node 052] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
20:08:42.666 CNTRLR « [Node 052] received wakeup notification
20:08:47.280 CNTRLR [Node 052] The node did not respond after 3 attempts.
It is probably asleep, moving its messages to the wakeup queue.
2021-02-20 20:08:47.282 INFO ZWAVE: Node 52 is now asleep
20:08:47.292 CNTRLR [Node 052] The node is now asleep.

node_52.json.txt
node_53.json.txt

I'm guessing that the driver is trying to refresh values from the remote. Since the device is a sleeping one, these have priority over all other messages because it won't be awake long.
As long as the device has been interviewed once before, the issue should be gone with https://github.com/zwave-js/node-zwave-js/pull/1787 - you might want to test that branch.

fixed in https://github.com/zwave-js/node-zwave-js/pull/2030

Hello,
Unfortunately the issue still exist.  If I press the button on the zwave remote, I get the logs below.  When the "Failed to execute controller command after 1/3 attempts" comes up, no other zwave devices can be controlled the whole network stalls for several seconds every press.  On the dashboard all the remotes show as "sleep" and "complete" under status and interview stage.
2021-03-28 09:45:11.186 INFO ZWAVE: Node 52 is now awake
2021-03-28T13:45:11.189Z CNTRLR [Node 052] The node is now awake.
2021-03-28T13:45:11.195Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-03-28 09:45:11.348 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 12 => 32
2021-03-28 09:45:11.362 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 32 => 32
2021-03-28T13:45:12.191Z CNTRLR » [Node 052] Sending node back to sleep...
2021-03-28 09:45:15.935 INFO ZWAVE: Node 52: value notification: 91-0-scene-002 0
2021-03-28T13:45:15.937Z CNTRLR « [Node 052] received CentralScene notification {
"nodeId": 52,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0x3c0002"
}
2021-03-28T13:45:15.960Z CNTRLR [Node 052] The node did not respond after 1 attempts.
It is probably asleep, moving its messages to the wakeup queue.
2021-03-28 09:45:15.963 INFO ZWAVE: Node 52 is now asleep
2021-03-28T13:45:15.971Z CNTRLR [Node 052] The node is now asleep.
2021-03-28T13:45:15.990Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-03-28T13:45:15.999Z CNTRLR « [Node 052] received wakeup notification
2021-03-28 09:45:16.001 INFO ZWAVE: Node 52 is now awake
2021-03-28T13:45:16.005Z CNTRLR [Node 052] The node is now awake.
2021-03-28 09:45:16.128 INFO ZWAVE: Node 50: value updated: 38-0-currentValue 0 => 0
2021-03-28 09:45:16.183 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 32 => 52
2021-03-28 09:45:16.197 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 52 => 52
2021-03-28T13:45:17.008Z CNTRLR » [Node 052] Sending node back to sleep...
2021-03-28T13:45:21.156Z CNTRLR [Node 052] The node did not respond after 1 attempts.
It is probably asleep, moving its messages to the wakeup queue.
2021-03-28 09:45:21.158 INFO ZWAVE: Node 52 is now asleep
2021-03-28T13:45:21.162Z CNTRLR [Node 052] The node is now asleep.

Honestly that looks like something different. Can you please open a new issue including a full logfile?

Hi AlCalzone,
No problem I'll open a new issue, especially since this one is closed but it's not something different.  My same nodes (Zwave remotes) on the same zwave networks and the logs are actually the same except the time stamps.

Well, it's not the same logs:
old: [Node 052] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
new: Failed to execute controller command after 1/3 attempts. Scheduling next try in 100 ms.

My apologies, I incorrectly implied that the text was word for word exactly the same.  Correction, the wording of the logs have changed, but the meaning remains the same.
"Hey there's a node that went from asleep to awake/alive, let me update it's settings while we're here. Oh no it's not responding [at this point the remote is back asleep, it's only up to activate the scene] lets schedule another attempt to see if it responds."
While this is happening, I can't control any other node on the network.
edit: just got your message on the new issue, I'll move over there.


Offer web download without npm

Not everyone likes npm or even has it installed. Maybe someone would also just like to quickly use your lib or so and therefore it would be nice if the JS file(s) could also be offered as a simple download.
When doing this e.g. via CDNs or simply GItHub Pages one can even directly include it in the HTML page.

Maybe we can use https://github.com/cdnjs/cdnjs ?
Would you be interested in doing this request ?

GitHub pages would be enough IMHO, but it's your decision. I think there is not much to do except uploading… depending on where you publish it.

I second this. I don't want any node.js or NPM stuff to bloat my host, so I had to build this inside a Docker container just to get the .js file out. Here's how I did it:
$ docker run --rm -it -v "$(pwd):/buildresult" node:7 bash
$ git clone https://github.com/edi9999/jsqrcode.git /work \
	&& cd /work \
	&& npm install || npm install -g acorn \
	&& npm run build \
	&& cp dist/index.js dist/index.js.map /buildresult

yeahh do that easy like /LazarSoft/jsqrcode  js files ready to be uploaded to the server  no NPM or composer etc

Generated files do not belong in a git repository, the real solution is to use cdnjs, they are specialised in hosting js files for the browser

Generated files don't belong in the repo I agree, but there should be a
link to the built file. Or use Github releases for that (just like for
compiled binaries)
On Jul 8, 2017 10:23, "Edgar Hipp"<EMAIL_ADDRESS>wrote:
Generated files do not belong in a git repository, the real solution is to
use cdnjs, they are specialised in hosting js files for the browser
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/edi9999/jsqrcode/issues/38#issuecomment-313840149, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmdh7mNYk0sh6fIzswY1o0VDnuj57pmks5sLy6DgaJpZM4Mr8uv
.


Add Dueling Layer and 'none' nonlinearity for future development

This pull request introduces 'dueling' layer for testing as well as a none as a nonlinearity to simplify code complexity of RainbowAgent which is under development.
The pull request will recognize the following network:
Network as list of layers
network_spec = [
    dict(type='dense', size=32, activation='tanh'),
    dict(type='dense', size=32, activation='tanh'),
    dict(type='dueling', size=10, activation='none')
]

Thanks for the PR, @Mazecreator! It seems to me this dueling layer might actually be more appropriately understood as a Distribution implementation, but have to think about this more.

I was thinking the same thing as the Paper seems to imply it is the output layer which you say really can't be done from the Network layer.  I am thinking it can stay as a layer but maybe we rename it to something like ValueAdvantage or something like that so it isn't confused as a "Dueling Layer" implementation.

I think it's fine for now, after all it links to the paper. But it might be we move it at some point to the distributions -- it's something to be thought about a bit more anyway... ;-)


Registering kills server

Rancher Versions: 3/8
Steps to Reproduce:

Create a new account and click on link in email.
Put in new password

Results: Stuck at loading

version - 3/27
Verified fixed