Host does not have enough reserved CPU available, cannot allocate to this host

ISSUE TYPE

Bug Report

COMPONENT NAME
API
CLOUDSTACK VERSION
4.15
OS / ENVIRONMENT
Centos7 system based on arm64 architecture
SUMMARY

Host does not have enough reserved CPU available, cannot allocate to this host
Hosts's actual total CPU: 128000 and CPU after applying overprovisioning: 128000
systemvmtemplate:
https://download.cloudstack.org/rpi4/systemvmtemplate/systemvmtemplate-<IP_ADDRESS>-kvm-arm64.qcow2
management-server.log

@ggsyu , you are really not giving enough information about;

how you installed
what you did
which template you are installing
unfortunately InsufficientServerCapacityException is a very generic exception.
nice to see arm arch be used btw.

@ggsyu，您确实没有提供足够的信息；

您如何安装
你做了什么
不幸的InsufficientServerCapacityException是，您要安装哪个模板是一个非常普遍的例外。
很高兴看到臂弓被用来顺便说一句。

@ggsyu，您确实没有提供足够的信息；

您如何安装
你做了什么
不幸的InsufficientServerCapacityException是，您要安装哪个模板是一个非常普遍的例外。
很高兴看到臂弓被用来顺便说一句。

centos arm64 system，rpmbuild cloudstack
yum localinstall -y cloudstack*.rpm

2021-04-20 13:45:07,019 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-136:ctx-f4569da1 job-1728/job-66347 ctx-ce4e7acb) (logid:edd1fb7d) No suitable hosts found under this Cluster: 2
2021-04-20 13:45:07,021 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-136:ctx-f4569da1 job-1728/job-66347 ctx-ce4e7acb) (logid:edd1fb7d) Could not find suitable Deployment Destination for this VM under any clusters, returning.

@DaanHoogland your problem is on the agent it seems:
2021-04-19 09:42:27,317 INFO  [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-2:ctx-2bc0da48 job-1728/job-56251 ctx-81ae4a1f) (logid:edd1fb7d) Unable to start VM on Host[-3-Routing] due to internal error: qemu unexpectedly closed the monitor: qemu-system-x86_64: -realtime mlock=off: warning: '-realtime mlock=...' is deprecated, please use '-overcommit mem-lock=...' instead

not on the management server. Can you look in the agent logs to see if anything sticks out there?

@ggsyu we haven't tested CloudStack with a CentOS7 based arm64 env, I however have tested a toy setup/env with rpi4+Ubuntu 20.04 (https://rohityadav.cloud/blog/cloudstack-rpi4-kvm). First please check if KVM (/dev/kvm) is enabled/available on your arm64 host. You may tune the host.reserved.mem.mb in the /etc/cloudstack/agent/agent.properties of the KVM arm64 host(s) to make more RAM available. Is your env using Raspberry Pi4 or some other arm64 variant?
Arm64/RaspberryPi4 is an experimental setup (not officially supported) and I think other than my experiment (with rpi4+Ubuntu 20.04) I'm not sure who may be using it. You may want to try starting the VM/qcow2 directly using virt-manager to check if it (kvm and the qcow2 image) actually works on your arm64 setup, I had tried a few distros before going with Ubuntu where it mostly worked out of the box.

@ggsyu can you try testing using 4.16 RC3 pkgs here: http://download.cloudstack.org/arm64/4.16/

ping @ggsyu Have you verified with 4.16 pkgs?

Ping @ggsyu

Closing this due to inactivity, I think the issue may not happen in latest 4.16/4.17 releases. Thanks for the report @ggsyu pl re-open if you reproduce this with latest releases.


Demo not working on ios

I tried demo page on safari but it continuously gives an error saying "Cross-origin image load denied by Cross-Origin Resource Sharing policy" please refer image below

can you suggest me how to fix this issue?

This was a croppie issue. You can update the croppie source code by including Croppie v2.1.1, and removing v1.0.3 from ng-croppie.js.

Hey thanks!  I'll make sure to update this source code when I get the chance =D

Hey Allen, can you update your code for supporting it in safari.

This issue is resolved by v1.2.1
Tested on Safari 11


meson: add Rust cross support

Motivation for this change
See commit messages.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Also, I see how I factored this stuff out in https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/rust/lib/default.nix so we don't need to refer to a specific version of rustc.
CC @dcbaker is there something we can do better than just sneaking in a --target ... flag? It would be great if we could embed the target platform json in the cross file more declarative. c.f. how the Nix platform description includes it.

No better way than to slip —target in somewhere. Ideas welcome for a better way

@Ericson2314 I really want to avoid any more build-system specific builder functions, because they don't compose, and make it difficult to handle packages with multiple build systems.  (buildRustPackage is a prime example of this and I'd really like to be rid of it one day.)
What's the problem with a target-sensitive Meson?  It's tiny and builds in seconds.

I hear you, but setup hooks are really frighteningly complex / "false modularity" to me, and I would like to move away from them.
I would appreciate if we could just fix this issue in the current style, and then discuss what to do for Meson and CMake, doing whatever we choose consistently for both of them.

The reason I changed it was that the rust functions were inaccessible in make-derivation.nix.  Are you saying there's a way to use them there?

Yeah I pulled out https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/rust/lib/default.nix, analogous to the Haskell lib. I suppose we should import it somewhere accessible from the top-level, and use it.
(More broadly, It would be nice to establish some clearer conventions around language infra. E.g. some Haskell stuff should probably move to pkgs/build-support and the two language libs should be named similarly.)

(More broadly, It would be nice to establish some clearer conventions around language infra. E.g. some Haskell stuff should probably move to pkgs/build-support and the two language libs should be named similarly.)

Keep language-specific infrastructure next to language-specific folders. If a tool is overly lang-specific, it is more discoverable inside the lang, not outside of it.

Well I just want us to be consistent :). I personally like distinguishing Haskell/Cabal support from Hackage, Rust/Cargo from Crates.io, etc. etc. but it's not important I'll go with the flow

Well I just want us to be consistent :). I personally like distinguishing Haskell/Cabal support from Hackage, Rust/Cargo from Crates.io, etc. etc. but it's not important I'll go with the flow

Stack/Cabal are rarely used outside Haskell. No one would download a truckload GHC just to compile a C library that otherwise can be build with Autotools or Meson.

Yes, but people might do Haskell without Hackage, or Rust without crates.io. That's the distinction I was making.


Mediapipe is providing two pairs of bounding box coordinates for single hand in a frame, how to resolve it?

I have written out the code for getting "hand_rects" from Mediapipe python implementation:
Ubuntu OS18.04:
Python 3:
Solution "Hand":

While getting the bounding box coordinates from the images passed to mediapipe, sometimes for single hand present in the frame, it would predict out 2 sets of bounding box coordinates. I have updated the mediapipe package for providing out 'hand_rects' after pip install mediapipe
It should predict only 1 set of bounding box coordinates for 1 hand present per frame.
How to resolve this issue?

Hi @amitbohra1234, Can you provide issue details or screenshots to understand the issue and investigate further.  Thanks!

Hi @sgowroji, This is one of the screenshot, I cannot share the rest of the data and code due to privacy issues. Please help in resolving this issue. It cannot be differentiated are these two sets of bounding box coordinates per frame, of single hand or 2 hands visible, i.e cannot eliminate the 2nd set of bounding box coordinates as there could be either 1 or 2 hands visible per frame.

Any updates, what could be the potential issue?

That can happen due to prediction inaccuracy. Also you can specify how many hands you would like to track. So for single hand - it would be sorted out automatically.
For the case with 2 and more hands tracked, we filter out duplicates by iou threshold between bounding boxes. If two different hands have IOU bigger than certain threshold, we filter out one of them as duplicate. So, you can update this threshold in the graph. Or implement such filtering on your end.


FlutterTester.app is failing for me (seems to be running Dart 1.0)

On Mac I'm trying to build the engine and run FlutterTester.app, but it seems to be running Dart 1.0 and so it fails with the newer Flutter apps which use Dart 2.0.
Steps to reproduce:
Step 1: Build the engine on Mac as described here
./flutter/tools/gn --unoptimized
then
ninja -C out/host_debug_unopt
2. Create a new flutter app:
flutter --local-engine=host_debug_unopt create custom3
3. Create the flutter_assets directory:
flutter --local-engine=host_debug_unopt build bundle
4. Run FlutterTester like this from out/host_debug_unopt directory (replace mark with your username)
./FlutterTester.app/Contents/MacOS/FlutterTester --dart-main=/Users/mark/dev/custom3/lib/main.dart --flutter-assets-dir=/Users/mark/dev/custom3/build/flutter_assets --packages=/Users/mark/dev/custom3/.packages
Here's the error output:
'package:flutter/src/services/system_channels.dart': error: line 30 pos 43: initializer is not a valid compile-time constant
  static const MethodChannel navigation = MethodChannel(
                                          ^

#0      new BindingBase (package:flutter/src/foundation/binding.dart:53:5)
#1      new BindingBase&GestureBinding (package:flutter/src/gestures/binding.dart:19:1)
#2      new BindingBase&GestureBinding&ServicesBinding (package:flutter/src/services/binding.dart:19:1)
#3      new BindingBase&GestureBinding&ServicesBinding&SchedulerBinding (package:flutter/src/scheduler/binding.dart:189:1)
#4      new BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding (package:flutter/src/painting/binding.dart:15:1)
#5      new BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&RendererBinding (package:flutter/src/rendering/binding.dart:24:1)
#6      new BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&RendererBinding&WidgetsBinding (package:flutter/src/widgets/binding.dart:241:1)
#7      new WidgetsFlutterBinding (package:flutter/src/widgets/binding.dart:920:1)
#8      WidgetsFlutterBinding.ensureInitialized (package:flutter/src/widgets/binding.dart:935:11)
#9      runApp (package:flutter/src/widgets/binding.dart:727:25)
#10     main (/Users/mark/dev/custom3/lib/main.dart:3:16)
#11     _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:286)
#12     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:169)

Here is my Flutter doctor output:
[✓] Flutter (Channel master, v0.5.9-pre.84, on Mac OS X 10.13.6 17G65, locale en-AU)
    • Flutter version 0.5.9-pre.84 at /Users/mark/dev/flutter
    • Framework revision 3ae5ecebea (2 days ago), 2018-08-19 06:25:00 -0400
    • Engine revision 03f8ba51e3
    • Dart version 2.1.0-dev.0.0.flutter-be6309690f

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/mark/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.1, Build version 9B55
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] IntelliJ IDEA Community Edition (version 2018.1.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 25.0.2
    • Dart plugin version 181.4892.1

[!] Connected devices
    ! No devices available

! Doctor found issues in 1 category.

Thanks for the bug report! FlutterTester.app was removed in flutter/engine#6314. Please open a new issue if you're still seeing issues with the flutter_tester binary.


[INFRA] add dependabot

relates to https://github.com/neurobagel/project/issues/73
Changes made

adds dependabot to update github action versions on a weekly basis

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
254

Relevant Lines:
280

💛  - Coveralls

thanks @alyssadai


[Extra] Write blog about internship at DDT (ying)

[x] Introduction (About me).
[x] What I like.
[x] What gone wrong. (Or what I don't like)
[x] What I learn. (Tools and stacks)
[x] Summary. (Should including perspective about careers)

Closed<EMAIL_ADDRESS>


Utilise HPC for Data Generation Scripts

User story

As a data engineer
I want/need to run data generation scripts on HPC
So that we can have the Q&A pairs training data ready for model training and fine-tuning

Acceptance criteria

Run the scripts for the Q&A pairs data generation on HPC

Ensure the output data is ready for further LLM training and fine-tuning

Store the Q&A pairs on HuggingFace

Definition of done (DoD)

Bill of Materials in the planning document has been updated
All the complex logics have been tested
All feature branches have been merged and closed
New feature code has been documented
Potential new licenses have been checked
All GitHub Actions are passing
The requirement.txt is updated

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

added DoD


Add whitelabel build capability for javascript tracker (closes #161)

Description
Add ability for whitelabel build. Clients would be able to build the JavaScript tracker providing their own namespace to avoid conflicts in conditions described in #161.
Usage
cd trackers/javascript-tracker
rushx build --whitelabel=SomeNamespace

The above will:

Create sp.js and sp.lite.js in the dist folder with the modified namespace
Modify the tags/tag.js as needed for the client to use as the tracker loader.

The client is notified during the build process, once for every target:

Notes

The replace is straightforward, replacing every instance of the string.
The change on tags/tag.js is again straightforward.

If we deem it necessary, we can opt for using a parser directly.
closes #161
This will come with an additional guide in the docs.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

Yeap done!
Added tag.min.js and updated the message and process accordingly 👍


Update cluster alert plugins

Fixes #147 Fixes #148

@sadlil (check the event list api call) @aerokite need a code review of this.


Fix panic on WAL replay

Fixes https://github.com/prometheus/prometheus/issues/9846
The added unit test detects the race. I would have expected this change to fix the race, but the race seems to be still present. Investigating.

Superseded by https://github.com/prometheus/prometheus/pull/9856


Bans unit tests

This PR adds unit test for the banning behavior.

Good news, the test works.

The fact that this PR adds a mock for the session interface means that we can use the code I added to test a lot of other behaviors.

What other behaviors do you think would be useful to test in this way?

What other behaviors do you think would be useful to test in this way?

I wanted for some times to change the config yaml to let admins have more than one keys. It would be very convenient for Elitedino or Epic. But this kind of heavy change would benefit for tests to do TDD.


Can it be applied to other fields as a general normalization method?

Thank you very much for your work. I would need some channel selective normalization on other tasks as well, but this training strategy might not be straightforward to apply. Is it possible to insert CSNorm without the training strategy mentioned in the paper?

We are pleased to see the versatile applicability of CSNorm, if anyone is interested in integrating it into their tasks.
Kindly note that one of the core steps of using CSNorm is to find the distinct component (e.g., lightness in our task), and design proper targets to drive the optimization of CSNorm.


Add stanford dog dataset

This PR is for adding dataset, related to issue #4504.
We are adding Stanford dog breed dataset. It is a multi class image classification dataset.
Details can be found here - http://vision.stanford.edu/aditya86/ImageNetDogs/
Tests on dummy data is failing currently, which I am looking into.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Hi @khushmeeet, thanks for you contribution.
But wouldn't it be better to add this dataset to the Hub?

https://huggingface.co/docs/datasets/share
https://huggingface.co/docs/datasets/dataset_script

Great, so I guess we can close this issue, as the dataset is already available on the Hub.

OK I read the discussion on:

#4504

Currently, priority is adding datasets to the Hub, not here on GitHub.
If you would like to contribute the loading script and all the metadata you generated (README + JSON files), you could:

Either make a PR to the existing dataset on the Hub
Create a new dataset on the Hub:

Either under your personal namespace
or even more professionally, under the namespace stanfordSVL (Stanford Vision and Learning Lab: https://svl.stanford.edu/)

You can use the Community tab to ping us if you need help or have any questions.


Unit test TXT content splitting

I believe there are bugs in that code and it should be unit-tested and corrected.

I added proper checks. I found the bugs: "\" "" \"

Closing as @sargun did the work for me 👍  . Thank you!


No Windows support?

There's only Zephyr and Linux support.  Someone else already asked about macOS, so here's a Windows one.
So yeah, are there any plans for supporting Windows?  And how much of the C++ standard library, if any at all, does this already support?
WASI is still a work in progress and it doesn't support C++ yet, but hopefully both projects will do so at some point and work together if possible.

@DragonOsman there is no plan to add support Windows now, but we appreciate contributions from community to add Windows support. It should not be difficult.

WAMR interpreter for windows 32b-it and windows 64-bit, and AOT for windows 32-bit are supported now. Seems that we can close issue.


VSCode should have option to hide bottom output panel when typing in editor area

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:13:05.928Z)
OS Version: Darwin x64 16.4.0
Extensions:

Extension
Author
Version

output-colorizer
IBM
0.1.1

material-icon-theme
PKief
2.0.9

numbered-bookmarks
alefragnani
0.10.0

workbench
andrew-lis
0.1.6

pgsql
doublefint
0.0.8

golang-tdd
joaoacdias
0.0.9

Go
lukehoban
0.6.62

railscasts
mrded
0.0.4

csharp
ms-vscode
1.10.0

vscode-icons
robertohuertasm
7.9.0

vscode-apielements
vncz
0.6.6

Steps to Reproduce:

Type in the editor area.
The bottom output area should autohide when typing in the editor and autoshow when we run or debug.

This would free up valuable screen real estate for editing, especially on a laptop.

Dup of https://github.com/Microsoft/vscode/issues/22653


Feature/#50 統計量をまとめて計算するメソッドを追加

Codecov Report

Merging #51 (8dbb9c1) into develop (8c6efbf) will decrease coverage by 4.74%.
The diff coverage is 21.79%.

@@             Coverage Diff             @@
##           develop      #51      +/-   ##
===========================================
- Coverage    85.38%   80.64%   -4.75%
===========================================
  Files           28       29       +1
  Lines          951     1028      +77
===========================================
+ Hits           812      829      +17
- Misses         139      199      +60

Impacted Files
Coverage Δ

kabutobashi/method/adx.py
79.48% <0.00%> (ø)

kabutobashi/utilities.py
31.32% <10.00%> (-19.84%)
:arrow_down:

kabutobashi/method/fitting.py
31.42% <31.42%> (ø)

kabutobashi/__init__.py
100.00% <100.00%> (ø)

kabutobashi/method/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


AB React

What does this change?
Adds the ab-react package to provide react specific functions for using ab tests

Ah ok, so you're still using lerna here rather than published

Ah ok, so you're still using lerna here rather than published

Yes, although not my intention it has advantages so I'm willing to go with the tide


[BUG] Enable to  see Shard* Metrics in performance-analyzer API

Hello,
I'm opening this issue because I think I have a weird behaviour with performance-analyzer.
Previously, in opendistro-for-elasticsearch:1.13.3 just after starting a docker container and enabling performance-analyzer plugin I was able to see metrics.
What is the bug?
Just after I've setup opensearch with docker for benchmark, I'm unable to visualize the Shard* Metrics with PerformanceAnalyzer.
How can one reproduce the bug?
Steps to reproduce the behavior:

Create a docker-compose.yml file with this content

version: '3'
services:
  opensearch-node1: # This is also the hostname of the container within the Docker network (i.e. https://opensearch-node1/)
    image: opensearchproject/opensearch:latest # Specifying the latest available image - modify if you want a specific version
    container_name: opensearch-node1
    environment:
      - cluster.name=opensearch-cluster # Name the cluster
      - node.name=opensearch-node1 # Name the node that will run in this container
      - discovery.type=single-node
      - plugins.security.ssl.http.enabled=false
      - bootstrap.memory_lock=true # Disable JVM heap memory swapping
      - "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # Set min and max JVM heap sizes to at least 50% of system RAM
    ulimits:
      memlock:
        soft: -1 # Set memlock to unlimited (no soft or hard limit)
        hard: -1
      nofile:
        soft: 65536 # Maximum number of open files for the opensearch user - set to at least 65536
        hard: 65536
    ports:
      - 9200:9200 # REST API
      - 9600:9600 # Performance Analyzer
    networks:
      - opensearch-net # All of the containers will join the same Docker bridge network
  opensearch-dashboards:
    image: opensearchproject/opensearch-dashboards:latest # Make sure the version of opensearch-dashboards matches the version of opensearch installed on other nodes
    container_name: opensearch-dashboards
    ports:
      - 5601:5601 # Map host port 5601 to container port 5601
    expose:
      - "5601" # Expose port 5601 for web access to OpenSearch Dashboards
    environment:
      OPENSEARCH_HOSTS: '["http://opensearch-node1:9200","http://opensearch-node2:9200"]' # Define the OpenSearch nodes that OpenSearch Dashboards will query
    networks:
      - opensearch-net

volumes:
  opensearch-data1:

networks:
  opensearch-net:

Start the containers with the command : docker-compose up -d
Then enable the plugin performance-analyzer like it's mentionned here : https://opensearch.org/docs/2.3/monitoring-plugins/pa/index/#install-performance-analyzer

curl -XPOST localhost:9200/_plugins/_performanceanalyzer/cluster/config -H 'Content-Type: application/json' -d '{"enabled": true}' -u 'admin:admin'

Normally at this steps the performance analyzer should be up and running
Create an index and documents data with the Documents API bulk operation

POST _bulk
{ "index": { "_index": "movies", "_id": "tt1979320" } }
{ "title": "Rush", "year": 2013 }
{ "index": { "_index": "movies", "_id": "tt1979322" } }
{ "title": "Rush2", "year": 2013 }
{ "index": { "_index": "movies", "_id": "tt1979323" } }
{ "title": "Rush3", "year": 2013 }
{ "index": { "_index": "movies", "_id": "tt1979324" } }
{ "title": "Rush4", "year": 2013 }
{ "index": { "_index": "movies", "_id": "tt1979325" } }
{ "title": "Rush5", "year": 2013 }

Here is the output of the creation

{"took":187,"errors":false,"items":[{"index":{"_index":"movies","_id":"tt1979320","_version":1,"result":"created","forced_refresh":true,"_shards":{"total":2,"successful":1,"failed":0},"_seq_no":0,"_primary_term":1,"status":201}},{"index":{"_index":"movies","_id":"tt1979322","_version":1,"result":"created","forced_refresh":true,"_shards":{"total":2,"successful":1,"failed":0},"_seq_no":1,"_primary_term":1,"status":201}},{"index":{"_index":"movies","_id":"tt1979323","_version":1,"result":"created","forced_refresh":true,"_shards":{"total":2,"successful":1,"failed":0},"_seq_no":2,"_primary_term":1,"status":201}},{"index":{"_index":"movies","_id":"tt1979324","_version":1,"result":"created","forced_refresh":true,"_shards":{"total":2,"successful":1,"failed":0},"_seq_no":3,"_primary_term":1,"status":201}},{"index":{"_index":"movies","_id":"tt1979325","_version":1,"result":"created","forced_refresh":true,"_shards":{"total":2,"successful":1,"failed":0},"_seq_no":4,"_primary_term":1,"status":201}}]}

Then try to get the Shard* Metric from performance-analyzer like this

GET localhost:9600/_plugins/_performanceanalyzer/metrics?metrics=ShardEvents,ShardBulkDocs,CPU_Utilization&dim=Operation&nodes=all&agg=sum,sum,max

Here is the output

{
    "90CFxK7zTi28rLkUpQiSpA": {
        "timestamp":<PHONE_NUMBER>000,
        "data": {
            "fields": [
                {
                    "name": "Operation",
                    "type": "VARCHAR"
                },
                {
                    "name": "ShardEvents",
                    "type": "DOUBLE"
                },
                {
                    "name": "ShardBulkDocs",
                    "type": "DOUBLE"
                },
                {
                    "name": "CPU_Utilization",
                    "type": "DOUBLE"
                }
            ],
            "records": [
                [
                    "GC",
                    null,
                    null,
                    0.0
                ],
                [
                    "flush",
                    null,
                    null,
                    0.0
                ],
                [
                    "generic",
                    null,
                    null,
                    0.0
                ],
                [
                    "get",
                    null,
                    null,
                    0.0
                ],
                [
                    "management",
                    null,
                    null,
                    0.0
                ],
                [
                    "other",
                    null,
                    null,
                    0.0020006279656433657
                ],
                [
                    "refresh",
                    null,
                    null,
                    0.0
                ],
                [
                    "search",
                    null,
                    null,
                    0.0
                ],
                [
                    "shardbulk",
                    null,
                    null,
                    0.0
                ],
                [
                    "transportWorker",
                    null,
                    null,
                    0.0
                ],
                [
                    "write",
                    null,
                    null,
                    0.0
                ]
            ]
        }
    }
}

What is the expected behavior?
I guess I should be able to see something instead of null values for the Shard metrics.
Do you have any advise how to proceed to be able to view those metrics ?
Example in opendistro-for-elasticsearch:1.13.3 I have this output
GET http://localhost:9600/_opendistro/_performanceanalyzer/metrics?metrics=Latency,CPU_Utilization,ShardBulkDocs,ShardEvents&agg=avg,max,sum,sum&dim=Operation&nodes=all

{
    "7LlEWVNVSL28JkYmWc8YqA": {
        "timestamp":<PHONE_NUMBER>000,
        "data": {
            "fields": [
                {
                    "name": "Operation",
                    "type": "VARCHAR"
                },
                {
                    "name": "Latency",
                    "type": "DOUBLE"
                },
                {
                    "name": "CPU_Utilization",
                    "type": "DOUBLE"
                },
                {
                    "name": "ShardBulkDocs",
                    "type": "DOUBLE"
                },
                {
                    "name": "ShardEvents",
                    "type": "DOUBLE"
                }
            ],
            "records": [
                [
                    "GC",
                    null,
                    0.0,
                    null,
                    null
                ],
                [
                    "bulk",
                    10.5,
                    null,
                    null,
                    null
                ],
                [
                    "flush",
                    null,
                    0.0,
                    null,
                    null
                ],
                [
                    "generic",
                    null,
                    0.0,
                    null,
                    null
                ],
                [
                    "management",
                    null,
                    0.0,
                    null,
                    null
                ],
                [
                    "other",
                    null,
                    0.0019996000799840027,
                    null,
                    null
                ],
                [
                    "refresh",
                    null,
                    0.0,
                    null,
                    null
                ],
                [
                    "shardbulk",
                    10.0,
                    0.0,
                    2.0,
                    2.0
                ]
            ]
        }
    }
}

What is your host/environment?

OS: docker
Version opensearch latest version 2.3.0
Plugins embedded by default in the docker image

Thank you very much for your help.
Best regards,

Thank you very much @dblock for transferring the issue.
But is it really a performance-analyzer repo issue and not an opensearch issue ?
As I mentionned in the issue, with OpenDistro 1.13.3 I have seen the same behavior / issue. And in performance-analyzer or performance-analyzer-rca I haven't see any major changes. I noticed that all the namespaces has changed because of migrating from OpenDistro -> Openseach...  So I has guessing changes in opensearch...
As a clue, If I comment the where clause in the method fetchLatency() from https://github.com/opensearch-project/performance-analyzer-rca/blob/main/src/main/java/org/opensearch/performanceanalyzer/reader/ShardRequestMetricsSnapshot.java#L179
I'm able to see some values so I suppose it's showing that the issue is elsewhere ? I'm not really sure.
I don't know how to debug more in opensearch of performance-analyzer plugin.
Do you have in advise to give me ?
Thank you very much.

@dblock it looks like the initial code moved to the repo performance-analyzer-rca now and has been reworked from what it was initially.
Maybe an issue with the rework

This was being taken care as part of this PR - https://github.com/opensearch-project/performance-analyzer-rca/pull/283.
Closing this issue


Doesnt work with latest version of react native

Unable to find a matching configuration of project :react-native-wifi-hotspot:
getting this error


Upgrade Linux Kernel for flatcar-4012 from 6.6.43 to 6.6.47

Subject says it all.

Closing in favor of: https://github.com/flatcar/scripts/pull/2235.


FW_FR launch failed

Hi,
In our votp-host, we have tried to deploy a VM of FW_FR which was defined by a xml file with content like the one attached below.
FW_FR.txt
Status IP:
votp-host:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
2: enp0s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:75:72:67 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s9
valid_lft 2174sec preferred_lft 2174sec
3: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:7d:8d brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s10
valid_lft 2174sec preferred_lft 2174sec
4: enp0s11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:55:72:67 brd ff:ff:ff:ff:ff:ff
5: enp0s12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:09:a6:2d brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s12
valid_lft 2175sec preferred_lft 2175sec
6: enp0s13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:0e:75:2d brd ff:ff:ff:ff:ff:ff
7: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:50:1c:ab brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s3
valid_lft 34574sec preferred_lft 34574sec
8: gre0@NONE:  mtu 1476 qdisc noop state DOWN group default qlen 1000
link/gre <IP_ADDRESS> brd <IP_ADDRESS>
9: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: sit0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit <IP_ADDRESS> brd <IP_ADDRESS>
And the interface enp0s9 was defined with virsh net-define enp0s9.xml.
enp0s9.txt
But when we tried to launch it, we got:
votp-host:~$ sudo virsh net-start enp0s9
error: Failed to start network enp0s9
error: cannot write to /proc/sys/net/ipv6/conf/virbr0/disable_ipv6 to enable/disable IPv6 on bridge virbr0: Read-only file system
And, it seems that the VM FW_FR can't be launched for it:
votp-host:~$ virsh start FW_FR
error: Failed to start domain FW_FR
error: Requested operation is not valid: network 'enp0s9' is not active
Then, we tried to add virbr0 and enp0s9 in OVS like below:
votp-host:~$ sudo ovs-vsctl show
e6638c18-7855-46e0-ae42-f0574d61302f
Bridge virbr0
Port virbr0
Interface virbr0
type: internal
Port enp0s9
Interface enp0s9
ovs_version: "2.15.2"
The error message of 'net-start' was changed like:
votp-host:~$ sudo virsh net-start enp0s9
error: Failed to start network enp0s9
error: error creating bridge interface virbr0: File exists
So, could you please help us to figure out how to fix it ?
Thanks in avance.
Best regards
Peng

Hi,
The syntax in enp0s9.txt and FW_FR.txt are both incorrect.
There are two ways to use an OVS with libvirt:

create the bridge port outside libvirt and use the  to attach it  in libvirt (this is what is done in SEAPATH by default)
let libvirt create the ports

Here you have mixed the two ways.
SEAPATH only support the first way, if you want libvirt create the ports you have to remove
"ProtectKernelTunables=yes" in /lib/systemd/system/libvirtd.service.

Hi Mathieu,
Just, how to attach the bright port outside libvirt for this VM, please ?
Thanks.

I have added this 5 lines in my FW_FR.xml, and defined with virsh define.
But when I tried to start this VM, I got an error below:
votp-host:~/stockage_pool$ virsh start FW_FR
error: Failed to start domain FW_FR
error: Unable to create tap device enp0s9: Invalid argument

Hi Mathieu,
Could you please give us a little help to launch this VM proprely ?
So, I just reopen it for a moment.
Thanks in avance.
Peng

Close as outdated


daisy: fix uploading sources from subworkflows

Fix regressing introduced by #403
Don't check w.Sources before calling uploadSources, this funcions
already deals with empty sources and also upload sources from
subworkflows

/ok-to-test


fade effect dosnt work with autoplay

This is a (multiple allowed):

[ ] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

Live Link or JSFiddle/Codepen or website with isssue: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP).

Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.
Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.
Before you open an issue, please check if a similar issue already exists or has been closed before.

swiper slider bag with fade effect


Cannot use master as branch

Expected behaviour
When either having master as the default branch or specifying it with the ?ref=master notation when running repo bootstrap it should use that branch to commit the bootstrapping files
Actual behaviour
Regardless of how I try to execute it, having tried (I think) all the possible combinations of having the branch defined in .gitconfig, using it as ?ref=master, toying with the default branch name in GitHub, with and without the -b flag, I have been unable to get to a different result other than FATAL failed to initialize repository: a branch named "refs/heads/master" already exists
Additional comments

This may very well be a duplicate of #198 but I still wanated to create a new issue as I think it not as a readme issue, but as a failure of now available flags
I have also noticed that a main branch is always created regardless of the default defined either in GitHub or in .gitconfig
Is there any way to bootstrap to master?

Before: https://github.com/argoproj-labs/argocd-autopilot/pull/333, we used to always prefer main because we did not check the provider for the default branch.
Because of the way we did stuff before this PR, you actually ended up with a repository with both main and master (empty branch). So this is the reason you see this:
FATAL failed to initialize repository: a branch named "refs/heads/master" already exists

However, if you create another repo with the latest autopilot version you should have only a single branch and it should hopefully be the default branch based on your github account settings.
Closing this issue now, let me know if it doesn't work for you yet.

I can confirm it is now working as I initially expected. Just for the sake of completion, this is what I'm running
docker run --rm -v ~/.kube:/home/autopilot/.kube -v ~/.gitconfig:/home/autopilot/.gitconfig -it quay.io/argoprojlabs/argocd-autopilot:v0.4.2 repo bootstrap --repo REPO --git-token TOKEN

Without specifying the ?ref=master
Thanks!


when the page number of the pdf file is bigger then 300,  the extract_pages(f) is very slow

中国神华：中国神华2023年度报告.PDF
code is very simple
from pdfminer.high_level import extract_pages
file_path = "***.pdf"
with open (file_path, "rb") as f:
for page in extract_pages(f):
page_index = page.pageid
print(page_index)
it cost about 10 minutes.

Well, extract_pages is actually doing layout analysis on every page, so one might expect this to be slow!  Do you find that it gets slower with each successive page?


HEP: support RWX volume to downstream cluster

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:
Add HEP for RWX volume support
Solution:
Add HEP for RWX volume support
Related Issue:
https://github.com/harvester/harvester/issues/1992

Hi guys, please help to review it again.
I have some updates for the above discussion.


Fix FPS Lycaon Controller

Lycaon's character displacement controller is clunky

Jumping only works once in a while, yet it's essential, mobility must be reliable for Lycaon to survive.
We need to take one of the pre-existing assets from Unity's learn courses and use that instead.

This is sort off fixed. We now detect when the player is Grounded by using collisions with a floor layer which yields far more reliable jumping.

After extensive testing, it's perfectly playable, animations are quite wonky often but it'll do.


[Task]: Update bigquery dependency for python SDK

What needs to happen?
The package google-cloud-bigquery was released on Mar 29 earlier this year and the beam package has yet to upgrade this dependency to the latest version and is explicitly pinned to a lower version:
https://github.com/apache/beam/blob/ddfb6907288369bfc71c3a310cb9ceb717a4d3a0/sdks/python/setup.py#L283
This dependency was last updated in https://github.com/apache/beam/commit/efaea052733ba41c1023fac2d29eab473c8488b8
Issue Priority
Priority: 2
Issue Component
Component: dependencies

Looks like this got updated in https://github.com/apache/beam/commit/bb7468ff13683dd82cfe97dff31d82c5a34024c6


Bump version to expose WM_CLASS fix in winit

winit 0.6.4 fixes https://github.com/tomaka/winit/pull/168, which in turn fixes #879.
Depends on https://github.com/tomaka/winit/pull/171.

Closing this as there's no reason to do a PR in glutin. Running cargo update will fix the bug.


MSOutput: decide which custodial site to use for data placement

Impact of the new feature
MSOutput
Is your feature request related to a problem? Please describe.
It looks like the we have overlooked the custodial output data placement. Custodial means that data is subscribed to Tape/MSS storage endpoints.
Right now, the output data placement in MicroServices does a data placement against any disk RSE (either DDM or Rucio will decide what the final location will be). So we need to change it to actually perform a custodial data placement (where MS needs to decide the final Tape location for DDM; with luck, Rucio can define it itself).
Describe the solution you'd like
We need to go through the checkor code:
https://github.com/CMSCompOps/WmAgentScripts/blob/master/Unified/checkor.py#L1009
and make/extract an algorithm for how the custodial site is defined within Unified. Once we know how it's done, we can either implement it in MSOutput or create a better way of identifying the final location.
Note that the Unified configuration is also used to define what goes or not to Tape (and maybe a few other parameters).
In short, this issue requires three actions:

study how custodial location is selected by Unified - AND make a clear specification in this issue
implement those requirements in the MSOutput
evaluate whether we really need to have standard non-custodial output data placement done by MSOutput (given that workflows are already assigned with NonCustodial parameters, where WMAgent takes care of the output data placement).

Describe alternatives you've considered
Given that WMAgents can perform the output data placement - if workflows are assigned as such - it might be that the current MSOutput implement could actually be dropped, and no nonCustodial data placement needs to be performed.
Additional context
none

@vlimant Jean-Roch, if you can spare a couple of minutes on this issue. Do you see any need for nonCustodial data placement to be done by Unified (and soon by MSOutput)? Given that workflows are already assigned with NonCustodial information - thus output gets placed by WMAgent.

The feedback I got from Eric was that sites need to create/assign tape families, or make all the directories a dataset will live in. This means that Tape rules might take a while until they get approved (is it possible they would get disapproved?).
Of course, it does not explain why unified has only 25 campaigns configured with custodial location (out of 150 campaigns)...
@todor-ivanov I'm afraid you will need to carry this discussion, agree on a final decision and get whatever comes out of it implemented in MSOutput.

As discussed over the #wmagent-dev slack channel. Eric has prepared a prototype API that would select a weighted random TAPE RSE, code can be found here: https://github.com/ericvaandering/CMSRucio/blob/weighted_rucio_choice/src/pick_rse.py
We are now discussing other final details and what else needs to be considered for this choice, but once we agree on a final logic, the idea is to add it to the WMCore Rucio wrapper:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/Services/Rucio/Rucio.py

If you take the existing logic and make the weight variable a configuration parameter for the MSOutput module, then you could start implementation right away. We can work on the rucio side to construct the appropriate weight.

@ericvaandering @nsmith- if we want to make this pick_rse function generic enough. How about we pass the data volume (bytes) as input to this function, such that it can evaluate whether the RSE it's going to select can host that data or not (as part of the internal logic)?

Yeah I was going to make that an option

Reopening it because we still have to figure out how to deal (and where to transfer) with the custodial data placement in the pre-Rucio era.
For the Rucio DM, Eric has already provided (which is now merged) a method to pick a random site based on an rse attr.


Upgrade windows code signing certificate

Description
Currently, windows users experience while installing Monokle, an annoying pop-up that warns them that the code may be malware. In order to solve that, we need a certificate with Extended Validation (EV). For that, to be generated, the Private Key must reside in an HSM (Hardware Security Module) or a pendrive, that ensures the key doesn't leave the storage.
A solution is to use an HSM on the cloud. Cloud HSM might be a good solution.
The keys were already generated in the HSM. Ask @chlete about it.
Criteria

[ ] Create an CSR with the Private Key stored in the HSM (How-to here)
[ ] Submit the CSR to a company that will sign the certificate (for example https://secure.ssl.com/ or https://trustzone.com/)
[ ] Sign Windows binary with the certificate
[ ] Install Monokle and check the warning is gone

Resources
https://www.ssl.com/guide/supported-cloud-hsms-document-signing-ev-code-signing/#google

CSR has been generated in Azure. Next step is to generate a certificated signed by a valid CA.


joint_cmd is not valid

Hi,
Thanks for developing such a great product and user-friendly environment.
The issue happened when I launched the simulated xArm with the gazebo. The gazebo is launched, and the robotic arm model is loaded. However,  when I opened the gazebo_ros2_conrol plugin, the console shows:
[gzclient-2] Topic [/data://world/default/model/UF_ROBOT/plugin/gazebo_ros2_control/joint_cmd] is not valid.
My environment is:
OS: ubuntu 22.04
ROS: Humble (All packages are updated)
I also compiled the gazebo_ros2_control and the error is the same.
The full log:
[INFO] [launch]: All log files can be found below /home/px172/.ros/log/2024-07-18-15-29-41-441470-ismblab-205879
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [gzserver-1]: process started with pid [205881]
[INFO] [gzclient-2]: process started with pid [205883]
[INFO] [robot_state_publisher-3]: process started with pid [205885]
[INFO] [spawn_entity.py-4]: process started with pid [205887]
[robot_state_publisher-3] [INFO] [1721287781.983235174] [robot_state_publisher]: got segment link1
[robot_state_publisher-3] [INFO] [1721287781.983301976] [robot_state_publisher]: got segment link2
[robot_state_publisher-3] [INFO] [1721287781.983307582] [robot_state_publisher]: got segment link3
[robot_state_publisher-3] [INFO] [1721287781.983310768] [robot_state_publisher]: got segment link4
[robot_state_publisher-3] [INFO] [1721287781.983313619] [robot_state_publisher]: got segment link5
[robot_state_publisher-3] [INFO] [1721287781.983316314] [robot_state_publisher]: got segment link6
[robot_state_publisher-3] [INFO] [1721287781.983319002] [robot_state_publisher]: got segment link_base
[robot_state_publisher-3] [INFO] [1721287781.983321718] [robot_state_publisher]: got segment link_eef
[robot_state_publisher-3] [INFO] [1721287781.983324351] [robot_state_publisher]: got segment world
[spawn_entity.py-4] [INFO] [1721287782.222606619] [spawn_entity]: Spawn Entity started
[spawn_entity.py-4] [INFO] [1721287782.222812135] [spawn_entity]: Loading entity published on topic robot_description
[spawn_entity.py-4] /opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/qos.py:307: UserWarning: DurabilityPolicy.RMW_QOS_POLICY_DURABILITY_TRANSIENT_LOCAL is deprecated. Use DurabilityPolicy.TRANSIENT_LOCAL instead.
[spawn_entity.py-4]   warnings.warn(
[spawn_entity.py-4] [INFO] [1721287782.223883562] [spawn_entity]: Waiting for entity xml on robot_description
[spawn_entity.py-4] [INFO] [1721287782.235055887] [spawn_entity]: Waiting for service /spawn_entity, timeout = 30
[spawn_entity.py-4] [INFO] [1721287782.235253309] [spawn_entity]: Waiting for service /spawn_entity
[spawn_entity.py-4] [INFO] [1721287782.737832251] [spawn_entity]: Calling service /spawn_entity
[spawn_entity.py-4] [INFO] [1721287782.977986695] [spawn_entity]: Spawn status: SpawnEntity: Successfully spawned entity [UF_ROBOT]
[gzserver-1] [INFO] [1721287783.034207956] [gazebo_ros2_control]: Loading gazebo_ros2_control plugin
[gzserver-1] [INFO] [1721287783.036218748] [gazebo_ros2_control]: Starting gazebo_ros2_control plugin in namespace: /
[gzserver-1] [INFO] [1721287783.036348772] [gazebo_ros2_control]: Starting gazebo_ros2_control plugin in ros 2 node: gazebo_ros2_control
[gzserver-1] [INFO] [1721287783.038230249] [gazebo_ros2_control]: connected to service!! robot_state_publisher
[gzserver-1] [INFO] [1721287783.039812318] [gazebo_ros2_control]: Received urdf from param server, parsing...
[gzserver-1] [INFO] [1721287783.040174369] [gazebo_ros2_control]: Loading parameter files /tmp/launch_params_a4bcwcx1
[gzserver-1] [INFO] [1721287783.050922727] [gazebo_ros2_control]: Loading joint: joint1
[gzserver-1] [INFO] [1721287783.051028652] [gazebo_ros2_control]: 	State:
[gzserver-1] [INFO] [1721287783.051051136] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051215266] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051283870] [gazebo_ros2_control]: 	Command:
[gzserver-1] [INFO] [1721287783.051290832] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051488468] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051615386] [gazebo_ros2_control]: Loading joint: joint2
[gzserver-1] [INFO] [1721287783.051624514] [gazebo_ros2_control]: 	State:
[gzserver-1] [INFO] [1721287783.051629283] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051635494] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051640482] [gazebo_ros2_control]: 	Command:
[gzserver-1] [INFO] [1721287783.051644914] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051658315] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051665551] [gazebo_ros2_control]: Loading joint: joint3
[gzserver-1] [INFO] [1721287783.051670188] [gazebo_ros2_control]: 	State:
[gzserver-1] [INFO] [1721287783.051674241] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051679229] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051683434] [gazebo_ros2_control]: 	Command:
[gzserver-1] [INFO] [1721287783.051687655] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051696712] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051702266] [gazebo_ros2_control]: Loading joint: joint4
[gzserver-1] [INFO] [1721287783.051706575] [gazebo_ros2_control]: 	State:
[gzserver-1] [INFO] [1721287783.051710460] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051717355] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051721801] [gazebo_ros2_control]: 	Command:
[gzserver-1] [INFO] [1721287783.051726190] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051736321] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051743053] [gazebo_ros2_control]: Loading joint: joint5
[gzserver-1] [INFO] [1721287783.051747419] [gazebo_ros2_control]: 	State:
[gzserver-1] [INFO] [1721287783.051753148] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051800138] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051806190] [gazebo_ros2_control]: 	Command:
[gzserver-1] [INFO] [1721287783.051810818] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051820500] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051826552] [gazebo_ros2_control]: Loading joint: joint6
[gzserver-1] [INFO] [1721287783.051830944] [gazebo_ros2_control]: 	State:
[gzserver-1] [INFO] [1721287783.051834800] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051838881] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.051842930] [gazebo_ros2_control]: 	Command:
[gzserver-1] [INFO] [1721287783.051846825] [gazebo_ros2_control]: 		 position
[gzserver-1] [INFO] [1721287783.051853735] [gazebo_ros2_control]: 		 velocity
[gzserver-1] [INFO] [1721287783.052013827] [resource_manager]: Initialize hardware 'gazebo_ros2_control/GazeboSystem'
[gzserver-1] [INFO] [1721287783.052627138] [resource_manager]: Successful initialization of hardware 'gazebo_ros2_control/GazeboSystem'
[gzserver-1] [INFO] [1721287783.052764808] [resource_manager]: 'configure' hardware 'gazebo_ros2_control/GazeboSystem'
[gzserver-1] [INFO] [1721287783.052771747] [resource_manager]: Successful 'configure' of hardware 'gazebo_ros2_control/GazeboSystem'
[gzserver-1] [INFO] [1721287783.052776841] [resource_manager]: 'activate' hardware 'gazebo_ros2_control/GazeboSystem'
[gzserver-1] [INFO] [1721287783.052780300] [resource_manager]: Successful 'activate' of hardware 'gazebo_ros2_control/GazeboSystem'
[gzserver-1] [INFO] [1721287783.053045669] [gazebo_ros2_control]: Loading controller_manager
[gzserver-1] [INFO] [1721287783.061613887] [gazebo_ros2_control]: Loaded gazebo_ros2_control.
[INFO] [spawn_entity.py-4]: process has finished cleanly [pid 205887]
[gzclient-2] Topic [/data://world/default/model/UF_ROBOT/plugin/gazebo_ros2_control/joint_cmd] is not valid.

Hi @px172, please provide detailed procedures to replicate your issue. What is the launch script you use and the arguments given, and what is the particular operation to trigger that error message ?


Missing Dialog style class

All my dialogs have some kind of generated class in it like this:

and I can style them with less files.
Now all of a sudden I got dialog with just "s-TemplatedDialog" class:

I would like to have it specific styles as other dialogs have (s-Orders-OrderDialog). Any idea what is wrong???

All of a sudden, you should check what is different than other dialogs, for example @registerClass

thx @volkanceylan!
it seems
@Serenity.Decorators.panel()
was missing for some reason


Apex deploy not idempotent in either config or code

Apex version 0.10.2
Apex platform: Go
Mac OSX Yosemite 10.10.5
When I try to apex deploy new versions of the code are always deployed, the config is detected as if it has changed as well.  Even in back-to-back calls to apex deploy functions and configs are updated.  I also deployed 2 different versions, downloaded the zip files from the lambda UI and diffed the files - they did not differ.
** Info I am not sure whether it is relevant or not **

I didn't notice this when I did the apex hello world example
I do not have a function.json file
".go" files are apexignored
I am running in a VPC
I have 2 "instances" of apex running on my AWS account in order to isolate different IAM roles necessary
I have added custom defined policies to my lambda role
I have all of my lambda functions connected to CloudWatch events

Project.json
{
  "name": "infra",
  "description": "This is a set of functions that will be used to manage infra",
  "runtime": "golang",
  "memory": 128,
  "timeout": 120,
  "role": "arn:aws:iam::AWS_ACCOUNT_ID:role/infra_lambda_function",
  "environment": {},
  "vpc": {
    "securityGroups": [
      "sg-SG1"
    ],
    "subnets": [
      "subnet-A",
      "subnet-B",
      "subnet-C"
    ]
  }
}

.apexignore
.*go

apex deploy trigger_buildbot -l debug
   • loading functions in functions
   • loading function in functions/trigger_buildbot
   • deploying 1 functions
   • deploying                 function=trigger_buildbot
   • creating build            function=trigger_buildbot
   • injecting prelude         function=trigger_buildbot
   • hook                      command=GOOS=linux GOARCH=amd64 go build -o main *.go function=trigger_buildbot hook=build
   • adding env                env=map[LAMBDA_FUNCTION_NAME:infra_trigger_buildbot APEX_FUNCTION_NAME:trigger_buildbot] function=trigger_buildbot
   • add shim                  function=trigger_buildbot
   • add file to zip           file=main function=trigger_buildbot
   • created build (2.6 MB)    function=trigger_buildbot
   • fetching config           function=trigger_buildbot
   • config changed            function=trigger_buildbot
   • updating config           function=trigger_buildbot
   • updating function         function=trigger_buildbot
   • updated alias current     function=trigger_buildbot version=20
   • function updated          function=trigger_buildbot name=infra_trigger_buildbot version=20
   • cleaning up version: 10   function=trigger_buildbot
   • cleaning 1 functions
   • hook                      command=rm -f main function=trigger_buildbot hook=clean
   • conditional flush         above_duration=24h0m0s above_size=500 age=38m33.282169122s size=73
   • close

I also notice this warning in Lambda:

Yeah, I noticed the issue with Config changing causing a deployment of the code as well when I was going through and testing some things. It appears to be related to this code block where having the config dirty also redeploys the code.
What happens is that it updates the configuration and then Updates the function. This update function blindly deploys the function instead of checking the hash, which I think should be done instead via the DeployCode function so that the hash is checked. Following that it will then create/update the alias.
I'm not sure if there was a reason to have both "Update" and "DeployCode" with similar code for deploying a function, but hopefully @tj can shed some light on it if there was.

Ah, that makes sense why the code keep being deployed - thanks. I believe the problems is that the canonical representation of the security groups and subnets on AWS doesn't respect the order in which apex sends them necessarily.
Although the type is an array, it really represents a set.  I'll take a stab at fixing this in a PR.  Thanks for the help!
https://github.com/apex/apex/blob/263e85b1e922e1398ad3c9078499dd50eea304bd/function/function.go#L748-L758


"cloudflare" npm package does not work with this package - ECONNREFUSED <IP_ADDRESS>:443

When using both cloudflare and do-wrapper npm packages, all requests sent from do-wrapper will fail.
This is the error seen:
(node:16361) UnhandledPromiseRejectionWarning: RequestError: connect ECONNREFUSED <IP_ADDRESS>:443
    at ClientRequest.<anonymous> (.../node_modules/do-wrapper/node_modules/got/dist/source/core/index.js:956:111)
    at Object.onceWrapper (events.js:422:26)
    at ClientRequest.emit (events.js:327:22)
    at ClientRequest.origin.emit (.../node_modules/@szmarczak/http-timer/dist/source/index.js:39:20)
    at TLSSocket.socketErrorListener (_http_client.js:469:9)
    at TLSSocket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)

All I did was npm init and npm i cloudflare do-wrapper
and this is the code used to reproduce the error:
import DigitalOcean from 'do-wrapper';
import Cloudflare from 'cloudflare';

const DO_ACCESS_TOKEN = '...';

const DO = new DigitalOcean.default(DO_ACCESS_TOKEN);

DO.regions.getAll().then(regions => console.log(regions.length));

Are there any quick workarounds?

This is my package.json
  "dependencies": {
    "cloudflare": "^2.7.0",
    "do-wrapper": "^4.4.1"
  },
  "type": "module"


Call reportFullyDrawn for performance

Idea Description
It makes the app fast because it is used app optimization.
Reference images and links
https://github.com/android/nowinandroid/blob/c67812563be5a710ea8a57b0580f6436599df8a5/feature-foryou/src/main/java/com/google/samples/apps/nowinandroid/feature/foryou/ForYouScreen.kt#L153

I'll try this!

Thanks!! Assigned 😊


Use ip address for internal communication #907

(#907)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yanshiguang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


MS Inverter not working when upgraded to v0.9.3

Thanks for the integration!
I am having an issue with the MS Inverter GW8500-MS when upgraded to the v0.9.3 version.
I had it configured to automaticaly discover the inverter type and was working fine on the v0.9.1:
"  - platform: goodwe
ip_address: <IP_ADDRESS>"
i tried the configuration bellow after upgrading and also it did not work:
"  - platform: goodwe
ip_address: <IP_ADDRESS>
#network_timeout: 1
#network_retries: 3
#scan_interval: 30
inverter_type: MS           # One of ET, EH, ES, EM, DT, NS, XS, BP or None to detect inverter type automatically
#comm_address: 247           # Inverter communication address, 247 for ET/EH inverters 127 for DT/D-NS/XS inverters
#sensor_name_prefix: GoodWe
#include_unknown_sensors: false"
I get this error on the Log:
#Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:164
Integration: Sensor (documentation, issues)
First occurred: 17:06:01 (1 occurrences)
Last logged: 17:06:01
The goodwe platform for the sensor integration does not support platform setup. Please remove it from your config.#
Could you take a look if that is something that needs attention please?
Thanks.

After v0.9.3 you should actually remove (or at least comment out) the setup in the yaml file and everything needs to be done via UI only. (It means you have to manually add the inverter via UI after upgrade).
If you did that, is there anything else relevant in the log files ?


Cleanup a few PR Comments

Test plan

Changelog

#5916  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RXminuS and the rest of your teammates on  Graphite


Pace display of "at limit" notifications when wallet is locked or iconified.

When using the mining wallet and it is first syncing up, a whole bunch of notifications get displayed for a fairly long period of time. If the wallet is locked or iconified, the "at limit" notification message displays fairly frequently which can be somewhat annoying. So once the notification queue limit is reached, pace the display of the "at limit" notification so it will be displayed less frequently.

Implemented an internal counter so that once the notification queue limit of 25 is reached, we don't display the "at limit" message again until another 25 messages have been received. Note these "at limit" messages are only displayed when the wallet is locked or iconified.

Closing this ticket.


Why is the inference speed of models trained on custom datasets much slower than YOLOV11

the size of the model trained on my own data is about 165M, and the inference time, including post-processing, is approximately 237ms

Is the speed measured in the environment of TensorRT? Why is the model so big, and what has been modified? In addition, I don't think it's appropriate to compare the 165M model to the YOLO11.

It is normal for checkpoint to have 165Mb because it contains the original model weights, EMA model weights, Optimizer, etc. If you need to convert to the model size we provided, pls use :

reference/ convert_weigh.py

In addition, the YOLO11 official onnx code does not include NMS post-processing. I submitted the relevant issue before
All official speeds are based on TensorRT, like other works. The inference code we presented uses the CPU for inference by default and is not comparable~

Thank you for your kind answer. I did not compare on TensorRT, but only conducted inference testing on touch and onnx. It was my mistake

You're welcome. We provide speed comparison code in tools/benchmark/trt_benchmark.py, which can be used by any other network when converted to engine. The YOLO series suffers a significant drop in performance after adjusting NMS parameters, and if you really need to make a completely fair comparison, Please refer to https://github.com/Peterande/D-FINE/blob/master/tools/deployment/export_yolo_w_nms to export YOLO11 with NMS and set - score_threshold to 0.001


Add benchmark highlighting the costs of failed calls to FromPyObject::extract.

This was brought up in #2278 and probably affects quite a bit of code that does a case-by-case analysis of argument types:
enum_from_pyobject      time:   [644.87 ns 648.64 ns 653.16 ns]
list_via_cast_as        time:   [3.4474 ns 3.4668 ns 3.4808 ns]
list_via_extract        time:   [4.3715 ns 4.3785 ns 4.3896 ns]
not_a_list_via_cast_as  time:   [3.4952 ns 3.5034 ns 3.5094 ns]
not_a_list_via_extract  time:   [284.42 ns 284.79 ns 285.12 ns]
not_a_list_via_extract_enum
                        time:   [289.56 ns 289.78 ns 289.98 ns]

The overhead itself mostly comes from this
/// Convert `PyDowncastError` to Python `TypeError`.
impl<'a> std::convert::From<PyDowncastError<'a>> for PyErr {
    fn from(err: PyDowncastError<'_>) -> PyErr {
        exceptions::PyTypeError::new_err(err.to_string())
    }
}

conversion.
I find it especially troubling that the rather nice way of using an enum is also affected.

I pushed a commit adding PyDowncastErrorArguments to at least delay the actual call into the formatting machinery but I am not happy about duplicating the format string and it only improves thing to one order of magnitude slower instead of two:
enum_from_pyobject      time:   [669.27 ns 672.85 ns 676.48 ns]
list_via_cast_as        time:   [3.4959 ns 3.4966 ns 3.4975 ns]
list_via_extract        time:   [3.0602 ns 3.0628 ns 3.0659 ns]
not_a_list_via_cast_as  time:   [3.2751 ns 3.4409 ns 3.5769 ns]
not_a_list_via_extract  time:   [45.943 ns 46.069 ns 46.255 ns]
not_a_list_via_extract_enum
                        time:   [44.261 ns 44.301 ns 44.344 ns]

So IMHO, this still seems to be a performance foot gun, especially in derived code.

How about changing the FromPyObject trait itself?
pub trait FromPyObject<'source>: Sized {
    type Error;
    /// Extracts `Self` from the source `PyObject`.
    fn extract(ob: &'source PyAny) -> Result<Self, Self::Error>;
}

Where the Error type would be PyDowncastError for a Python type and PyErr otherwise.
(note: if we start changing conversion traits we should probably consider all of them)

How about changing the FromPyObject trait itself?

I think we should consider this, but this could be in a maintenance release helping existing deployments without obstructing such a change to FromPyObject, couldn't it?
Regarding adding an associated Error type to FromPyObject, I think we would need to consider the problem of composition, i.e.
#[derive(FromPyObject)]
struct Foo {
  bar: Bar,
  qux: Qux,
}

must derive an Error type that can be construct from either <Bar as FromPyObject>::Error and <Qux as FromPyObject>::Error. Do we create ad-hoc error types for this? Or do we require a trait bound and box them up?

How about changing the FromPyObject trait itself?

There's a very old thread at #426 suggesting a rework. That thread is probably very out of date; it might be worth killing and starting a new discussion.
For what it's worth, the idea in #1308 would also change FromPyObject, by adding a separate lifetime (one becomes the lifetime of the data, the second the lifetime of the GIL).

Please add a Changed CHANGELOG entry documenting the performance tweak and then feel free to merge +1

Done. Will give it some time if anyone fancies a look and merge in the afternoon.


Update request: osu-lazer 2024.731.0 → 2024.817.0

Package name: osu-lazer
Latest released version: 2024.817.0

Current version on the unstable channel: 2024.731.0
Current version on the stable/release channel: 2024.521.2

[x] Checked the nixpkgs pull requests

Notify maintainers
@gepbird
@thiagokokada

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Done in https://github.com/NixOS/nixpkgs/pull/335097 and https://github.com/NixOS/nixpkgs/pull/335262. Please wait a few hours/days for these to reach unstable.

Done in #335097 and #335262. Please wait a few hours/days for these to reach unstable.

Sorry, I was tired and forgot to check closed issues as well. Thanks for the clarification.
Closing this issue.

Closing this issue.


LicenseRegistry.licenses doesn't complete during Driver tests

The following code:
void _start() async {
    var contents = <LicenseItem>[];

    await for (final LicenseEntry license in LicenseRegistry.licenses) {
      final paragraphs = license.paragraphs.map((p) => p.text).toList();
      contents.add(LicenseItem(
        title: license.packages.join(', '),
        body: paragraphs.join('\n\n'),
      ));
    }

    if (disposed) return;
    _itemsController.add(contents);
  }

works fine when running the app (debug/release).
However during Flutter Driver tests, it never completes. It should complete in a matter of seconds, but it never completes.

Logs
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.0, on Mac OS X 10.15.3 19D76, locale en-TH)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)

• No issues found!

Hi @chris-rutkowski
could you please run flutter upgrade --force
if the issue persists
please provide a "runnable" minimal code sample
Thank you

I've just upgraded the Flutter with force flag, however I experience this issue for long time already on multiple stables and beta channels.
[✓] Flutter (Channel stable, v1.17.1, on Mac OS X 10.15.3 19D76, locale en-TH)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)

@iapicca here is the demo project
https://github.com/chris-rutkowski/flutter-license-driver-failure
If you run the project on Android Emulator, this is the result:

also check the console log:
I/flutter ( 7334): started
I/flutter ( 7334): next item
I/chatty  ( 7334): uid=10133(com.example.licenses) Thread-2 identical 442 lines
I/flutter ( 7334): next item
I/flutter ( 7334): completed
I/flutter ( 7334): Snapshot data length: 444

If you run driver tests flutter drive --target=test_driver/app.dart
This is the result:

and the console log:
VMServiceFlutterDriver: Connecting to Flutter application at http://<IP_ADDRESS>:51600/OnqxMZ5AiIc=/
VMServiceFlutterDriver: Isolate found with number:<PHONE_NUMBER>967499
VMServiceFlutterDriver: Isolate is paused at start.
VMServiceFlutterDriver: Attempting to resume isolate
VMServiceFlutterDriver: Waiting for service extension
I/flutter ( 7695): started
VMServiceFlutterDriver: Connected to Flutter application.
00:01 +0: licenses

VMServiceFlutterDriver: waitFor message is taking a long time to complete...

Duplicate of https://github.com/flutter/flutter/issues/24703


Detect not working on Android

Opening an QR code in iOS works fine but for Android less so; it's not able to find the QR code in the image. I've attached it for testing. This image is fake data and does not represent a real person. The image below comes in as base64 encoded which I pass into detect; Like I said above, iOS nails it 100% of the time so I believe my RN code to be valid.

Hi @jleach .
Currently android cannot detect large QR codes


separated css/html/js

moved codes from inline to external files

edited files to be as individual external css/js


Dsd 231 checkbox

Fixes https://jira.nypl.org/browse/DSD-231
This PR does the following:
-Adds a new checkbox component which matches the approved Figma design.

Refactors the color variables so that there are both CSS variables (custom properties) and SASS variables, which were needed for some preprocessing operations.
Removes linter plugin which is no longer necessary since we are now creating the CSS vars dynamically.

Front End Review:

[ ] View the example in Storybook

Is there a reason why the "older" component version is being kept around? I'm not sure if the "deprecated" label in storybook or the appended "old" in the component name really work. The Checkbox component went through some updates but the changes are not vastly different in what it renders or how its styles that there should be an "old" version of it. If the new designs are approved, the older version shouldn't still be allowed to be used.
The LCA, for example, implements the Checkbox component. When I update to the version of DS that includes this change, I would expect the styling to be updated and that I need to include new props. But I would not switch to the CheckboxOld component if it goes against what Figma has approved for styling.
All of this to say that it seems safe to remove the "old" files.

Also, I'm not sure if it's this PR but something is wrong with the Hero component in Storybook -- the homepage link in this PR throws an error: https://deploy-preview-547--stoic-murdock-c7f044.netlify.app/

Is there a reason why the "older" component version is being kept around? I'm not sure if the "deprecated" label in storybook or the appended "old" in the component name really work. The Checkbox component went through some updates but the changes are not vastly different in what it renders or how its styles that there should be an "old" version of it. If the new designs are approved, the older version shouldn't still be allowed to be used.
The LCA, for example, implements the Checkbox component. When I update to the version of DS that includes this change, I would expect the styling to be updated and that I need to include new props. But I would not switch to the CheckboxOld component if it goes against what Figma has approved for styling.
All of this to say that it seems safe to remove the "old" files.

@EdwinGuzman thanks for your thoughts on this! @bigfishdesign13 is still mulling how we might deprecate components so I created the "deprecated" section more as a POC of one way we could do it, but that's not set in stone!  We should probably do a team discussion on this.

Also, I'm not sure if it's this PR but something is wrong with the Hero component in Storybook -- the homepage link in this PR throws an error: https://deploy-preview-547--stoic-murdock-c7f044.netlify.app/

NB: @bigfishdesign13

Also, I'm not sure if it's this PR but something is wrong with the Hero component in Storybook -- the homepage link in this PR throws an error: https://deploy-preview-547--stoic-murdock-c7f044.netlify.app/

@kaplanmichael
I am not seeing this issue in any other builds.  What about your local build?

@kaplanmichael
I am also noticing that the Docs tab in Storybook is throwing an error for Checkbox.  Are you seeing the same?

Is there a reason why the "older" component version is being kept around? I'm not sure if the "deprecated" label in storybook or the appended "old" in the component name really work. The Checkbox component went through some updates but the changes are not vastly different in what it renders or how its styles that there should be an "old" version of it. If the new designs are approved, the older version shouldn't still be allowed to be used.
The LCA, for example, implements the Checkbox component. When I update to the version of DS that includes this change, I would expect the styling to be updated and that I need to include new props. But I would not switch to the CheckboxOld component if it goes against what Figma has approved for styling.
All of this to say that it seems safe to remove the "old" files.

@EdwinGuzman and @kaplanmichael
I think Edwin is spot on with this.  Especially so, considering we are still in a pre-release/beta mode.  I will send out a note to the #design-system Slack channel to annopunce that this change is coming.  I will also make note of this change once the release is completed.

Also, I'm not sure if it's this PR but something is wrong with the Hero component in Storybook -- the homepage link in this PR throws an error: https://deploy-preview-547--stoic-murdock-c7f044.netlify.app/

@kaplanmichael
I am not seeing this issue in any other builds. What about your local build?

I don't have any problems locally.


fix(tabs): center the tab label to be horizontally aligned with the icon

Short description of what this resolves:

Labels should be horizontally aligned with icons.
Ionic Version: 4.0.0-beta.3
Fixes: #15273

Closing in favor of #15286


use base64+zstd for account data encoding by default, add ping support and make recv cancellation safe

Sorry I squeezed the fixes for #17 #19 and a base64+zstd fix into the same PR.
The first commit in the PR fixes the following problem.
The jsonParsed encoding won't work if the account data can be parsed by the RPC node. For example, the spl-token account will be actually parsed! The notification from WS becomes
{
    "jsonrpc": "2.0",
    "method": "accountNotification",
    "params": {
        "result": {
            "context": {
                "slot": 114915064
            },
            "value": {
                "lamports": 2039280,
                "data": {
                    "program": "spl-token",
                    "parsed": {
                        "info": {
                            "isNative": false,
                            "mint": "USDhTjkUXFfigLELiFpbBnpLmEm4aXHvdY2kDSadJDH",
                            "owner": "8dyR4YwFHzh2Pxmgs9TPst5Mu4kkES5tu8w6SuhdEyUG",
                            "state": "initialized",
                            "tokenAmount": {
                                "amount": "5771086231612606",
                                "decimals": 9,
                                "uiAmount": 5771086.231612606,
                                "uiAmountString": "5771086.231612606"
                            }
                        },
                        "type": "account"
                    },
                    "space": 165
                },
                "owner": "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA",
                "executable": false,
                "rentEpoch": 266
            }
        },
        "subscription": 10447
    }
}

and cannot be deserialized into the AccountRepresentation struct.
Choosing base64+zstd because it is compressed and should save network bandwidth theoretically (which is the bottleneck).
The rest two commits fixes #17 and #19.

@boymaas @karim-agha

@dovahcrow let us know when it’s ready

@dovahcrow let us know when it’s ready

It's ready.

@boymaas @oeble ping

Looks good, a keep alive and base64+zstd. Approved from my part


installable from Qubes repository / refactoring

This I find bad...
qvm-run -p "$resources_qube" "cd ${resources_dir%/*} && git clone https://github.com/elliotkillick/qvm-create-windows-qube"

echo -e "${BLUE}[i]${NC} Please check for a \"Good signature\" from GPG..." >&2
qvm-run -q "$resources_qube" "gpg --keyserver keys.openpgp.org --recv-keys 018FB9DE6DFA13FB18FB5552F9B90D44F83DD5F2"
qvm-run -p "$resources_qube" "cd '$resources_dir' && git verify-commit \$(git rev-list --max-parents=0 HEAD)"

...because it runs commands that require networking from dom0, relies on networking and successful gpg verification.
feature request: please design this script form the perspective of already being installed in Qubes dom0 without any networking/extra gpg verification required. Packaging, so this could be reviewed by @QubesOS and installed in dom0 using qubes-dom0-update.

I do realize this potential MITM vulnerability, however, I removed the reminder to verify out-of-band due to #7.
Either way, this project should be packaged for streamlined and more secure Qubes installation. I've never done any type of packaging before so I'll have to figure that out but it is on the way!

I've decided to re-add the reminder to verify out-of-band in https://github.com/elliotkillick/qvm-create-windows-qube/commit/5f7fb111bb9b726b7d57c0093a07177b012e2383!

It looks like this work is not necessary anymore due to the great work of @fepitre (thank you!) creating qubes-mgmt-salt-windows-mgmt. I see an rpm_spec folder in there so that looks like packaging and the SaltStack does all the work creating the windows-mgmt VM so I think that's this issue closed. Is this correct @fepitre?


The operation-post-201-202-status-code rule does not correspond to Trimble API Standard

The operation-post-201-202-status-code rule does not correspond to Trimble API Standard which allows 200 also: https://api-standards.trimble-pnp.com/api-standard/http/#successful-responses-2xx

Totally agree and hasn't gone unnoticed. Will make sure this makes it onto the list of rule to create/update
Thanks Alexey


Update README.md

@suvhradipghosh07 please sign CLA

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


Debug Console: "Copy All" results in [object Object] in the buffer

VSCode Version: Insiders Latest
OS Version: Mac OS

Steps to Reproduce:

Debug any program that prints something in the debug console (e.g. console.log("test"); in JS)
Right click the console, do "Copy All"
-> List of [object Object] is in the buffer instead of the actual console output.

If text is manually entered in the console (not when debugging), it is copied in the buffer correctly.

Does this issue occur when all extensions are disabled?: Yes

@michelkaporin great catch, thanks!

Verified but opened https://github.com/Microsoft/vscode/issues/46919


Bad padding

TryteString.from_string has bad padding. If you run:
tag = TryteString.from_string("tagname")

It won't return a string that is 27 characters long, which creates issues with other functions. Need to make ugly hacks, that add 9's up to the 27 lenght requirement.
Example structure it was generating issues with:
transfers=[

                ProposedTransaction(

                    address=Address("JEMEHHS9EEASH9UFOLYAKBCTNKGBADCLTKCEOEKPZVILIGTZOGYMFMWKQABVVNKHGHBHTJNRVDDMMUQOX"),

                    value=0

                ),

                ProposedTransaction(

                    address=Address("LORKNNVSBTILWAUZBK9RTMVFPJOWAU9KOIINNGYISJQ9P9AFBFH9OJNXBILBFRPVHGVNIBB9LYGUHCESB"),

                    value=0,

                    message=TryteString.from_string("First transaction"),

                    tag=TryteString.from_string("xCarx")

                )

    ],

Hey @lukzmu ProposedTransaction should automatically convert the TryteString into a Tag object, which automatically pads the sequence to 27 trytes.
Alternatively, try using Tag instead of TryteString, or in a pinch, you can specify a padding length when initialising a TryteString.

Scheduled for release: 2.0.5
Thanks @rpitonak !


[Feature] .withRecursive() for models with self associations

I have a model like the following one:
class Person extends Model {
  static entity = 'people'
  static fields () {
    return {
      id: this.attr(),
      name: this.string(),
      parentId: this.string(),
      parent: this.belongsTo(Person, 'parentId')
    }
  }
}

And I need a getter iterating through the ancestors of one person:
get fullName () {
  return this.parent ? `${this.name} son of ${this.parent.fullName}` : this.name
}

Now, vuex-orm has a method: withAllRecursive, but I have two reasons not to use it for this scenario:

Say, Person model has other relations, but I only need this one
withAllRecursive goes only to a specified depth (defaulting to 3) but I don't know how many ancestors there are for a given Person.

I suggest a new query method withRecursive with the following usage:
Person.query().withRecursive('parent').find(123).fullName

Any thoughts on this?

Sorry for the late response! Yeah this makes sense. Let's mark this as an enhancement issue 👍


Newly created iOS app fails to build - Xcode 13 - macOS 12

I've Googled (I think) almost everything and nothing has worked so far.
Steps to Reproduce

flutter create my_app
cd my_app
code .
flutter clean (just to start clean)
rm -rf ~/Library/Developer/Xcode/DerivedData (and just to be sure)
Set device to "iPhone 13 mini (ios simulator)"
flutter run

Logs

Logs

Running "flutter pub get" in my_app...                             560ms
Launching lib/main.dart on iPhone 13 mini in debug mode...
Running Xcode build...
Xcode build done.                                            3.7s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    /Users/jaredible/Desktop/my_app/ios/Runner/Runner-Bridging-Header.h:1:9: note: in file included from
    /Users/jaredible/Desktop/my_app/ios/Runner/Runner-Bridging-Header.h:1:
    #import "GeneratedPluginRegistrant.h"
            ^
    /Users/jaredible/Desktop/my_app/ios/Runner/GeneratedPluginRegistrant.h:10:9: error: 'Flutter/Flutter.h' file
    not found
    #import <Flutter/Flutter.h>
            ^
    1 error generated.
    <unknown>:0: error: failed to emit precompiled header
    '/Users/jaredible/Library/Developer/Xcode/DerivedData/Runner-aqexqrhcixiavnfixtmqcujfcevb/Build/Intermediate
    s.noindex/PrecompiledHeaders/Runner-Bridging-Header-swift_17NGLEZEEN237-clang_3S7KALCZBNI0I.pch' for
    bridging header '/Users/jaredible/Desktop/my_app/ios/Runner/Runner-Bridging-Header.h'
    /Users/jaredible/Desktop/my_app/ios/Runner/Runner-Bridging-Header.h:1:9: note: in file included from
    /Users/jaredible/Desktop/my_app/ios/Runner/Runner-Bridging-Header.h:1:
    #import "GeneratedPluginRegistrant.h"
            ^
    2 errors generated.
    error: generate-pch command failed with exit code 1 (use -v to see invocation)
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in dependency order

Could not build the application for the simulator.
Error launching application on iPhone 13 mini.

[✓] Flutter (Channel stable, 2.8.1, on macOS 12.1 21C52 darwin-x64, locale en-US)
    • Flutter version 2.8.1 at /Users/jaredible/bin/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (7 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/jaredible/Library/Android/sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
    • Java version Java(TM) SE Runtime Environment (build 1.8.0_311-b11)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] IntelliJ IDEA Community Edition (version 2021.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (2 available)
    • iPhone 13 mini (mobile) • 3AAE3D8C-96F7-4C3F-B3C8-386C11A6EF87 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
    • Chrome (web)            • chrome                               • web-javascript • Google Chrome 98.0.4758.80

• No issues found!

@jaredible
Can you provide flutter run --verbose log in a text file ?
Also provide Runner.xcodeproj/project.pbxproj and ios/podfile.

@jaredible Can you provide flutter run --verbose log in a text file ? Also provide Runner.xcodeproj/project.pbxproj and ios/podfile.

Please, let me know if this is correct.
verbose_run.txt
verbose_run_other.txt
project_pbxproj.txt
No podfile exists

@jaredible
From the verbose log you shared, it's failing due to:

`Target debug_universal_framework failed: ProcessException: Process exited abnormally:

ld: building for iOS Simulator, but linking in .tbd file`

Which is similar to this open issue: https://github.com/flutter/flutter/issues/84788, so please follow-up in it for further updates.
Closing this as a duplicate.

Ultimately, this helped me understand fundamentally the source of the problem: https://stackoverflow.com/a/64139830


Windows ATP Alerts extremely slow to come in

I'm using ATP in a test lab, and alerts are very slow to come in. It's a defender ATP instance hooked up to one machine. Using EICAR test files and the PowerShell script to trigger alerts will create a new alert in the ATP dashboard, but they can take up to hours to show up.
Is there anything I can do to speed that up?
(The VM I'm running is on gigabit fiber, so I don't think this is a network speed issue).

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

ID: 578a2a0c-d8ec-de9f-0a2a-450d1087ecf7
Version Independent ID: 14b80f24-ed8e-9b63-d3f6-85852467b679
Content: Manage Microsoft Defender Advanced Threat Protection alerts - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/manage-alerts.md
Product: w10
Technology: windows
GitHub Login: @mjcaparas
Microsoft Alias: macapara

Depending on how much time it takes for any useful reply & follow-up from a topic-savvy MS Docs team member to arrive here, you may want to consider joining and posting your question in the Tech Community section for Microsoft Defender Advanced Threat Protection: https://techcommunity.microsoft.com/t5/microsoft-defender-advanced/ct-p/MicrosoftDefenderAdvanced
I also hope you are aware that this repository is originally intended as a reporting instance for errors, improvement suggestions, or update/modernization requests for the Microsoft documentation pages.
I know, sometimes you may get a useful answer from one of the team members, but it is also a very good chance that this can take a lot of time, depending on the importance of your issue ticket content compared to the existing documentation content and any need for it to be updated or changed, based on the resulting outcome of your question.
Disclaimer: I am not affiliated with Microsoft or the Microsoft Docs teams here on GitHub.

@jmcadams-r7
As mentioned by illfated, Please consider sending your input via the Feedback Hub so that it gets addressed via the proper channels:
Send feedback to Microsoft with the Feedback Hub app
The issues section of this repository is for content fixes regarding documentation. Feel free to re-open in case you would like to suggest improvements to the article itself.
Thanks again.


stick to parent size?

Is it possible to limit element movements by a parent container size?

@probil  thanks for pushing that on. I have found bounds property on the original moveable documentation site. https://daybrush.com/moveable/release/latest/doc/Moveable.html#bounds
But it seems to not be yet ported ? Or I am using that not correctly? Could you help please?
I try like that:
<Moveable
.....
:bounds="{ left: 220, right: 1000, top: 0, bottom: 1000}">
.....

Directly related to #31

Released as part of v1.0.0


Podfile error when pod install

I am trying to build the project. And I got an error when I try to pod install.
Here it is:
Analyzing dependencies
[!] The version of CocoaPods used to generate the lockfile (1.2.0) is higher than the version of the current executable (1.1.0.beta.1). Incompatibility issues may arise.
Fetching podspec for `SwiftMatrixSDK` from `../matrix-ios-sdk`
[!] No podspec found for `SwiftMatrixSDK` in `../matrix-ios-sdk`

This should be fixed with 5632efa6d7a3247591dfaba7414ce43c0aa50771


Please remove our business domain name from the Blacklist

Brightedge Technologies is a legitimate business based in US, and we have over 1700 customers worldwide.  We found out that our domain name has been added to the Ultimate.Hosts.Blacklist.
Please remove our domain (brightedge.com) and all our hosts from this list, as this is undermining our domain reputation, and causing problems in our business operation.
We also would like to know how our domain name had been added to the blacklist, as we would like to prevent this problem from occurring again in the future.  So please provide us with all records related to our domain and our hosts.
Thanks.

/play wups

:balloon:

/move to Ultimate-Hosts-Blacklist/whitelist