Code

Dear author, hello! After reading your article and finding it very meaningful, I would like to ask when you can upload your code. If it is useful to me, I will reference your article later. Thank you very much!

Thanks for your recognition of our work. In fact, our  We will release our code as soon as the paper appears in the conference proceedings.


unable to understand VpcEndpointId

Once this template make sure you edit the TGW subnet we create with VpcEndpointId
please suggest what is VpcEndpointId

After deployment network firewall creates gateway load balance endpoint in the subnet that was selected for provisioning. This template creates subnet TGW-Subnet-AZ2.  There is a network interface placed in this subnet which is nothing but vpc-endpoint. So the whole setup doesn't work because there is a route missing the routing table that's associated with this subnet. To make it working you'll need to create a route that's pointing traffic to the vpc-endpoint, otherwise it wouldn't know how to reach network firewall.


can't stop ranging/monitoring in android 6,7 on Bluetooth turning off

Hi,
i'm trying to stop ranging and monitoring to improve battery performance but it can't working, it giving me these logs,
i can't understand what's going in,
need help, thanks
09-26 14:40:55.853 13229-13229/... I/EstimoteSDK: BeaconManager.stopRanging:694 Not stopping ranging, not connected to service
09-26 14:40:55.853 13229-13229/seronic.telenor I/EstimoteSDK: BeaconManager.stopRanging:694 Not stopping ranging, not connected to service
09-26 14:40:55.853 13229-13229/.. I/EstimoteSDK: BeaconManager.stopRanging:694 Not stopping ranging, not connected to service
09-26 14:40:55.853 13229-13229/... I/EstimoteSDK: BeaconManager.stopRanging:694 Not stopping ranging, not connected to service
09-26 14:40:55.853 13229-13229/... I/EstimoteSDK: BeaconManager.stopRanging:694 Not stopping ranging, not connected to service
09-26 14:40:55.853 13229-13229/..... I/EstimoteSDK: BeaconManager.stopRanging:694 Not stopping ranging, not connected to service
09-26 14:40:55.853 13229-13229/...I/EstimoteSDK: BeaconManager.stopMonitoring:941 Not stopping monitoring, not connected to service
09-26 14:40:55.853 13229-13229/.... I/EstimoteSDK: BeaconManager.stopMonitoring:941 Not stopping monitoring, not connected to service
09-26 14:40:55.853 13229-13229/.... I/EstimoteSDK: BeaconManager.stopMonitoring:941 Not stopping monitoring, not connected to service
09-26 14:40:55.863 13229-13229/... I/EstimoteSDK: BeaconManager.stopMonitoring:941 Not stopping monitoring, not connected to service
09-26 14:40:55.863 13229-13229/.....I/EstimoteSDK: BeaconManager.stopMonitoring:941 Not stopping monitoring, not connected to service
09-26 14:40:55.863 13229-13229/... I/EstimoteSDK: BeaconManager.stopMonitoring:941 Not stopping monitoring, not connected to service
09-26 14:40:55.863 13229-13229/... I/Bluetooth: Bluethoot Turned Off.........

Hey!
I just wanted you to know that we are in the process of moving our SDK for Android to a completely new architecture. We won't be publishing any updates to our old (current master) SDK for a while.
But don't worry - there is an ALPHA version of our FRESH PROXIMITY SDK available now!
It uses a completely new scanning mechanism and will work on new Android versions like a charm (6.0, 7.0, 8.0).
We did a great job with renovating our ecosystem to cut off the old, messy code, full of hacks for Android KitKat an Jellybean. This is why working with BeaconManager was so frustrating by the way.
Plan for the next couple of weeks:

ProximitySDK beta release - our own tag-based proximity. Use it to achieve the same behaviour as using iBeacon (monitoring/ranging). It is uses our own packets called Estimote Location and is backed-up by our own data-science. Read more here -> http://blog.estimote.com/post/166007374930/the-most-reliable-proximity-tech-now-with-a
ScanningSDK beta release - a separate core library dedicated for raw scanning - it will handle the scanning on all android versions for you, battery efficiency, background/foreground, and will deliver raw stream of packet data (Such as iBeacon, Eddystone, EstimoteLocation, EstimoteTelemetry, etc).

I encourage you to try it out - there is a ready made app for you to show the possibilities of our completely new SDK -> https://github.com/Estimote/Android-SDK/tree/proximity-sdk
Let us know what you think!
I will keep you updated about the progress.


React Automatic Runtime was not really supported before

Description
At the moment it's impossible to use React Automatic Runtime out of the box. The reason is:
  function getSource(source, importName) {
    switch (importName) {
      case "Fragment":
        return `${source}/${development ? "jsx-dev-runtime" : "jsx-runtime"}`;
      case "jsxDEV":
        return `${source}/jsx-dev-runtime`;
      case "jsx":
      case "jsxs":
        return `${source}/jsx-runtime`;
      case "createElement":
        return source;
    }
  }

Babel doesn't use source as... source. It adds a magic string jsx-runtime to the given library name, and there's no such thing as jsx-dom/jsx-runtime
Well, long story short: after this PR, jsx-dom and jsx-dom/min will become valid jsxImportSource values
P.S. - Referencing jsx-dom as an external library from */jsx-runtime is intentional. This was made to avoid duplication of functionality in a bundle of a dependent project that uses React Automatic Runtime and sometimes imports something like Component, useText etc directly from jsx-dom

Published as<EMAIL_ADDRESS>


Different colours in ClinVar stars

Describe the bug
ClinVar stars have different colours if they are 0 stars (black) than if they are 1-4 stars (blue)
Observed behaviour
ClinVar stars are coloured black if there are 0 stars and blue if there are 1-4 stars.

Expected behaviour
ClinVar stars should have consistent colours.

Also present in variant page https://genetics--ot-platform.netlify.app/variant/12_6333477_C_T


[7.x] Add Publish State permission

Matching the canManagePublishState from core and replicating this PR: https://github.com/statamic/cms/pull/10424

@duncanmcclean let's talk about this one, as I believe we'd need a migration script otherwise it's breaking.

let's talk about this one, as I believe we'd need a migration script otherwise it's breaking.

Yes, we'd either need to ship with an upgrade script or include this PR in the next breaking changes release (which'll have the nested fields fix).


feat: support fetching specific asset version with URN

Closes #190

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

29 of 39 (74.36%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.05%) to 86.123%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/store/postgres/asset_repository.go
25
35
71.43%

Files with Coverage Reduction
New Missed Lines
%

internal/store/postgres/asset_repository.go
1
77.62%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
5002

Relevant Lines:
5808

💛  - Coveralls


Umbrella issue: fix broken links in zh docs

When running make serve with docker locally, the following links are broken:

@windsonsea

WARNING  -  Documentation file 'download/modules/insight.md' contains a link to 'insight/intro/release-notes.md' which is not found in the documentation files.
WARNING  -  Documentation file 'download/modules/kcollie.md' contains a link to 'kcollie/intro/release-notes.md' which is not found in the documentation files.
WARNING  -  Documentation file 'download/modules/kcoral.md' contains a link to 'kcoral/intro/release-notes.md' which is not found in the documentation files.
WARNING  -  Documentation file 'kangaroo/space/index.md' contains a link to 'kangaroo/images/space02.png' which is not found in the documentation files.
WARNING  -  Documentation file 'kangaroo/space/reclaim.md' contains a link to 'kangaroo/images/space01.png' which is not found in the documentation files.
WARNING  -  Documentation file 'mspider/user-guide/mesh-config/component-hpa.md' contains a link to 'mspider/intro/comp-and-archi/cp-component.md' which is not found in the documentation files.
WARNING  -  Documentation file 'mspider/user-guide/service-mesh/README.md' contains a link to 'mspider/images/create-mesh02.png' which is not found in the documentation files.
WARNING  -  Documentation file 'storage/solutions/ceph-dashboard.md' contains a link to 'insight/best-practice/import-dashboard.md' which is not found in the documentation files.

@Michelle951

WARNING  -  Documentation file 'kairship/workload/deployment.md' contains a link to 'kairship/images/deploy12.png' which is not found in the documentation files.
WARNING  -  Documentation file 'kpanda/user-guide/security/hunter.md' contains a link to 'kpanda/user-guide/images/security01.png' which is not found in the documentation files.
WARNING  -  Documentation file 'kpanda/user-guide/security/cis/config.md' contains a link to 'kpanda/user-guide/images/security01.png' which is not found in the documentation files.
WARNING  -  Documentation file 'kpanda/user-guide/security/cis/policy.md' contains a link to 'kpanda/user-guide/lusters/create-cluster.md' which is not found in the documentation files.
WARNING  -  Documentation file 'middleware/mongodb/user-guide/logs.md' contains a link to 'middleware/mongodb/images/logs01.jpg' which is not found in the documentation files.
WARNING  -  Documentation file 'middleware/mongodb/user-guide/logs.md' contains a link to 'middleware/mongodb/images/logs02.jpg' which is not found in the documentation files.
WARNING  -  Documentation file 'middleware/mongodb/user-guide/logs.md' contains a link to 'middleware/mongodb/images/logs03.jpg' which is not found in the documentation files.
WARNING  -  Documentation file 'skoala/best-practice/gateway01.md' contains a link to 'skoala/images/br-gw09.png' which is not found in the documentation files.
WARNING  -  Documentation file 'videos/kairship.md' contains a link to 'kairship/workload/README.md' which is not found in the documentation files.

@Jeanine-tw

WARNING  -  Documentation file 'network/performance/cni-performance.md' contains a link to 'images/network-pod-bandwidth.png' which is not found in the documentation files.
WARNING  -  Documentation file 'network/performance/cni-performance.md' contains a link to 'images/network-svc-bandwidth.png' which is not found in the documentation files.
WARNING  -  Documentation file 'network/performance/cni-performance.md' contains a link to 'images/network-long-connection.png' which is not found in the documentation files.
WARNING  -  Documentation file 'network/performance/cni-performance.md' contains a link to 'images/network-short-connection.png' which is not found in the documentation files.

Fixed:

Download

WARNING  -  Documentation file 'download/modules/insight.md' contains a link to 'insight/intro/release-notes.md' which is not found in the documentation files.
WARNING  -  Documentation file 'download/modules/kcollie.md' contains a link to 'kcollie/intro/release-notes.md' which is not found in the documentation files.
WARNING  -  Documentation file 'download/modules/kcoral.md' contains a link to 'kcoral/intro/release-notes.md' which is not found in the documentation files.

Kangaroo

WARNING  -  Documentation file 'kangaroo/space/index.md' contains a link to 'kangaroo/images/space02.png' which is not found in the documentation files.
WARNING  -  Documentation file 'kangaroo/space/reclaim.md' contains a link to 'kangaroo/images/space01.png' which is not found in the documentation files.

Mspider

WARNING  -  Documentation file 'mspider/user-guide/mesh-config/component-hpa.md' contains a link to 'mspider/intro/comp-and-archi/cp-component.md' which is not found in the documentation files.
WARNING  -  Documentation file 'mspider/user-guide/service-mesh/README.md' contains a link to 'mspider/images/create-mesh02.png' which is not found in the documentation files.

Storage

WARNING  -  Documentation file 'storage/solutions/ceph-dashboard.md' contains a link to 'insight/best-practice/import-dashboard.md' which is not found in the documentation files.

local build in zh directory: no link errors


fix: coalesce variantid to assign a studylocusid

closes #3151

Codecov Report

Merging #253 (9528c13) into main (634c410) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #253   +/-   ##
=======================================
  Coverage   86.74%   86.75%
=======================================
  Files          80       80
  Lines        1833     1834    +1
=======================================
+ Hits         1590     1591    +1
  Misses        243      243

Files
Coverage Δ

src/otg/dataset/study_locus.py
96.00% <100.00%> (+0.05%)
:arrow_up:


IPv6 OOB does not work

Hi,
the issue with IPv6 out-of-band connectivity stems from the line cfg.Sysctls["net.ipv6.conf.all.disable_ipv6"] = "1" in rare.go.
I believe it’s unnecessary to enforce this setting within the kind itself, as disabling IPv6 within the container should suffice.
To fix this, we could remove the line cfg.Sysctls["net.ipv6.conf.all.disable_ipv6"] = "1" from the kind configuration. Additionally, in the hwdet-mgmt.sh script, we should update the following:
from:
IPv4=`hostname -i | awk '{print $1}'`
IPv6=`hostname -i | awk '{print $2}'`

to:
IPv4=`hostname -i | awk '{print $2}'`
IPv6=`hostname -i | awk '{print $1}'`

BR
Takalele

That's a valid feedback. The general approach is that during installation freeRtr takes full control of the networking stack. As you have already noticed, freeRtr can run and be connected to different dataplane. In containerlab flavor, software dataplane is used. The reason ipv6 has been disabled is to let freeRtr full control on the IPv6 stack. In that context, one solution is to disable ipv6 for all interface except the OOB interface. Feel free to submet a PR. I'd be glad to merge it.
All welcome to freeRtr networking community !

during my testing, I found that the only change needed to get IPv6 OOB working again is to comment out line 41 in the rare kind. It is sufficient to disable IPv6 via sysctl during the container build process, as done by lines 43 and 44 in the install-rtr.sh script. With this change, Docker is still able to delegate the IPv6 address to the container, as the hostname -i command returns both IPv4 and IPv6 addresses, even though IPv6 remains globally disabled.
Is there anything I might have overlooked?
If this solution is acceptable to you, I would be happy to make the necessary commits in both the containerlab and freeRtr-containerlab repositories.
Alternatively, one could try to modify rare.go to disable IPv6 via cfg.Sysctls for all interfaces except eth0. However, it is unclear whether this is possible and would work as expected.
Also, thank you for the rare SOHO blog – it was very helpful for getting started with FreeRTR three years ago!
takalele@ct-labs:~$ docker ps
CONTAINER ID   IMAGE                         COMMAND                  CREATED      STATUS      PORTS     NAMES
bf5dffe4b0ae   freertr-containerlab:latest   "/bin/sh -c /rtr/sta…"   3 days ago   Up 3 days             clab-rtr-l2transport-internet
74afc881a493   freertr-containerlab:latest   "/bin/sh -c /rtr/sta…"   3 days ago   Up 3 days             clab-rtr-l2transport-rtr1
18ec8dab6a87   alpine:latest                 "/bin/sh"                3 days ago   Up 3 days             clab-rtr-l2transport-n2
cba7511f8f85   alpine:latest                 "/bin/sh"                3 days ago   Up 3 days             clab-rtr-l2transport-n1
4581ec359ab2   freertr-containerlab:latest   "/bin/sh -c /rtr/sta…"   3 days ago   Up 3 days             clab-rtr-l2transport-rtr2

takalele@ct-labs:~$ docker exec -it clab-rtr-l2transport-internet bash
root@rtr1:~# sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1
root@rtr1:~# hostname -i
2001:172:20:20::2 <IP_ADDRESS>

root@rtr1:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:42:ac:14:14:02  txqueuelen 0  (Ethernet)
        RX packets 36820  bytes 2938278 (2.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 29233  bytes 2666730 (2.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether aa:c1:ab:eb:1a:19  txqueuelen 0  (Ethernet)
        RX packets 239845  bytes 47982296 (45.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 444002  bytes 69025459 (65.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether aa:c1:ab:97:e1:56  txqueuelen 0  (Ethernet)
        RX packets 17441  bytes 2310696 (2.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17439  bytes 2310536 (2.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth3: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether aa:c1:ab:85:9c:6e  txqueuelen 0  (Ethernet)
        RX packets 17439  bytes 2310536 (2.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17441  bytes 2310696 (2.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth4: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether aa:c1:ab:53:b5:a3  txqueuelen 0  (Ethernet)
        RX packets 1518  bytes 343347 (335.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20398  bytes 2745908 (2.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65535
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 841505  bytes 158500268 (151.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 841505  bytes 158500268 (151.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

takalele@ct-labs:~$ telnet clab-rtr-l2transport-rtr1
Trying 2001:172:20:20::2...
Connected to clab-rtr-l2transport-rtr1.
Escape character is '^]'.
welcome
username:rare
password:
line ready
rtr1#show ipv6 interface
interface    state  address                    netmask
ethernet1    up     fe80::a8c1:abff:fe58:3c95  ffff:ffff:ffff:ffff::
ethernet255  up     2001:172:20:20::2          ffff:ffff:ffff:ffff::

rtr1#ping 2001:172:20:20::1 vrf OOB
pinging 2001:172:20:20::1, src=null, vrf=OOB, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 2, min/avg/max/dev rtt=0/0.2/1/0.1, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0

@frederic-loui I've made updates to the rare kind to disable IPv6 at runtime, first for all interfaces and then globally. This gives Docker enough time to assign the IPv6 address to the container, ensuring that the hostname -i command captures the correct address. If this approach is acceptable to you, I would like to proceed with creating a pull request in the containerlab repository.
the updated rare kind

I would not modify rare kind and leave the current containerlab internal behavior WRT OOB management interface.
In the bash script, I'd rather:
1- List all interfaces explicitely eth[0-9]+
ls -d /proc/sys/net/ipv6/conf/eth*

2- For all eth* interfaces disable IPv6 except eth255:
echo 1 | sudo tee /proc/sys/net/ipv6/conf/eth*/disable_ipv6
echo 0 | sudo tee /proc/sys/net/ipv6/conf/eth255/disable_ipv6
# ... Or use sysctl equivalent or sysctl.conf

Well this is a suggestion ! Maybe I might have overlooked another problem.
PS: Thanks for the feedback regarding the blog. The project is still alive and kicking but moving at a lower pace because of various reasons. However, your feedback is invaluable as we don't know who is using our work/stuff and somehow we think that our doc is "not read"😄 Obviously, please do not hesitate to provide suggestion, improvement. We are always willing to help. It is just that we are helping at the pace we can follow at some point in time. We plan to refresh these articles with current technology, things are evolving so fast that the docs updates cannot keep up... 😞

I’ve tested this, but unfortunately, I haven’t found a way to get IPv6 OOB working without modifying the rare kind.
The simplest solution would be to comment out line 41: cfg.Sysctls["net.ipv6.conf.all.disable_ipv6"] = "1". In my opinion, there’s no need to disable net.ipv6.conf.all.disable_ipv6 using the Docker sysctl flag, as IPv6 will be disabled by hwdet-all.sh during FreeRTR startup. Since IPv6 is disabled within the container and not via Docker, the Docker daemon is able to assign an IPv6 address to the container. How do we want to procced?
Regarding the blog, where would you like me to submit some suggestions or feedback? Do you have an email address or a contact form I can use?

Thanks @Takalele for your feedback and tests. We should keep it simple as you suggested. Feel free to submit a PR re-enabling back IPv6. WRT to the blog, you reach me via email<EMAIL_ADDRESS>

merged


Add test scripts

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master      #5   +/-   ##
======================================
  Coverage    13.2%   13.2%
======================================
  Files          21      21
  Lines        1636    1636
======================================
  Hits          216     216
  Misses       1410    1410
  Partials       10      10

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 ac1dc39...36cf6a1. Read the comment docs.


Send telemetry about creating/deleting sandbox connections

To get information about usage would be good to have information about how often create page is:

opened/canceled
opened/submitted/sucessfully created sandbox connection
opened/submitted/failed to create sandbox connection

Duplicated issue opened with more info. closing


RDK-35331: RDKShell - Key Repeat Updates

@mateusz-hobgarski-red - Pls resolve conflicts since PR 2809 got merged.

Closing older PRs. Pls bring changes to latest sprint.


Convert to build-type Simple

Oh, cool. Thanks @hvr . The other thing I was pulling out of the custom Setup.hs was the package version number used for the User-Agent: HTTP header. Any idea where I can get that at build time?

@afcowie for that you have two options: either the Paths_ module which gives you a version :: Version,  or just use VERSION_http_streams, which is a CPP macro (provided by Cabal and GHC) that expands into a string-literal like "1.2.3"

Huh. Turns out I lost the User-Agent setting code ages ago when I refactored out http-common from http-streams. Oops. Well, I'll restore that, but in another branch. Merging.


feat: create input component [draft]

This PR resolves []
Description

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

add input component - mounir

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (add input component - mounir)

  Generated by :no_entry_sign: dangerJS against 765ccbaced81e0d604ef2bd6ec0e15c82ab8f168


[sw] Bring back debug symbols in ELF files

ELF files did get their debug symbols stripped by our linker script. That's not really intended; we want to use the ELF files for debugging, and the ELF loader should take care that only required sections will end up being loaded. Thankfully the build id section was already removed with a linker flag, so the linker script part was unnecessary. Revert that commit and add a couple more cleanups along the way.

@silvestrst can you try this PR to see if debugging works for you now?

Note: previous discussion on this was happening in #1002 and #966. The discussion indicates that having only the DISCARD linker file  patch doesn't work, but having only --build-id=none should work (and it does in my testing).

I guess the main point of having DISCARD is to only have the specified sections in the output. So another option would be to explicitly specify that we want to have the debug symbols included by naming them.
But I agree that we need debug symbols.
Default linker script elf32riscv.x does:
  /* DWARF debug sections.
     Symbols in the DWARF debugging sections are relative to the beginning
     of the section so we begin them at 0.  */
  /* DWARF 1 */
  .debug          0 : { *(.debug) }
  .line           0 : { *(.line) }
  /* GNU DWARF 1 extensions */
  .debug_srcinfo  0 : { *(.debug_srcinfo) }
  .debug_sfnames  0 : { *(.debug_sfnames) }
  /* DWARF 1.1 and DWARF 2 */
  .debug_aranges  0 : { *(.debug_aranges) }
  .debug_pubnames 0 : { *(.debug_pubnames) }
  /* DWARF 2 */
  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
  .debug_abbrev   0 : { *(.debug_abbrev) }
  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end) }
  .debug_frame    0 : { *(.debug_frame) }
  .debug_str      0 : { *(.debug_str) }
  .debug_loc      0 : { *(.debug_loc) }
  .debug_macinfo  0 : { *(.debug_macinfo) }
  /* SGI/MIPS DWARF 2 extensions */
  .debug_weaknames 0 : { *(.debug_weaknames) }
  .debug_funcnames 0 : { *(.debug_funcnames) }
  .debug_typenames 0 : { *(.debug_typenames) }
  .debug_varnames  0 : { *(.debug_varnames) }
  /* DWARF 3 */
  .debug_pubtypes 0 : { *(.debug_pubtypes) }
  .debug_ranges   0 : { *(.debug_ranges) }
  /* DWARF Extension.  */
  .debug_macro    0 : { *(.debug_macro) }
  .debug_addr     0 : { *(.debug_addr) }
  .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }

The ELF contents shouldn't matter, as "ELF" is not the "output" format we're caring about; the loader needs to take care to only put relevant sections into memory. The loader in our case (currently) is either the ELF -> VMEM conversion tooling, or the Verilator ELF loader.

But doesn't the ELF content matter as the placement of the sections in ELF will influence the values of relative addresses? Not sure if objcopy does any update here.
I am not trying to say we should specify everything, because if something unexpected like the build ID does come up it will "just" result in an error which can then be fixed.

Yes, that's true. So would we be OK with only the /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) } line?

Well, I think it only makes sense to discard all or just leave it as you proposed in this PR.
Sorry for the noise, I just wanted to raise awareness to the fact that discarding might make sense, but this is not a necessity. And to be honest I do not know all the impacts /DISCARD/ could have as to suggest its safe usage.

Phillip, could you break up this PR into two? One to fix up the .ld format, one to actually make the linker script changes.
Also, seeing as we're apparently having an opinion on .ld format... is it worth it to write like, a paragraph of .ld style guide?

@mcy Sure #1114 created


docs(NavbarToggler): add info about placement

Also updated the placement of the docs toggler itself.

👍


Add method for hashing connected graphs

In preparation for some future work, it would be convenient to be able to calculate the hash of a connected graph, assuming no directivity in edges. That is, if we query for all nodes connected to a node using django-postgresql-dag's connected_graph() method, we should be able to calculate a hash value of the current state of all connected elements. While potentially expensive to compute †, this should allow guaranteed identification of changes to the graph.
It is possible to have multiple DAGs using django-postgresql-dag. For this issue, we want to calculate the hash of a particular DAG, not all nodes/graphs within the project. To do this, we might approach the problem in the following manner:

Initially treat the DAG as an undirected graph (which is done with the connected_graph() query) to retrieve all nodes in the current graph.
For each identified node within the QuerySet, annotate the node with a sorted list of the parent id values of that node.
Sort the QuerySet by node id.
Convert the resulting QuerySet to a tuple of tuples (which contains the id and parents for each node).
Iterate through the tuple, calculating the combined hash all elements.
Return the calculated hash value.

Recommendations for improvement are welcome. There's likely a more memory-friendly approach that will still get the job done.
Alternative approaches considered: NetworkX Provides a weisfeiler_lehman_graph_hash() function, but it doesn't work well on graphs that are not isomorphic. The graphs produced with django-postgresql-dag are likely to be non-isomorphic.
† Potentially expensive in time and memory. The tuple we use to calculate the hash contains the id of every node in the graph, and for each node, the ids of the parent nodes. Using hashllib's blake2s hash will probably be a speedy approach, but the entire process of querying, converting, and iterating to calculate the hash will take a certain amount of time.

The graphs produced with django-postgresql-dag are likely to be non-isomorphic.

What is meant by this sentence? isomorphism AFAIK is a property of a pair of graphs ( graph X is isomorphic to graph Y ), and not a stand alone property of a graph.


how to use webpack-dev-middleware in a  OrchardCore CMS with the HMR (Hotmodule reloader) connected

how to use webpack-dev-middleware in a  OrchardCore CMS with the HMR (Hotmodule reloader) connected
I use Microsoft.AspNetCore.SpaServices

Please use stackoverflow or gitter for question, configuration depends on many things, better open issue in OrchardCore CMS


Masqueraded hosts don't appear in the API

We have an internal ticket for this assigned to @keymone, but I figured I would make it public because (believe it or not) there are other people using this fork (or just our patch).
cc @roobert
I know exactly why. The way the API works is that it iterates over clients
https://github.com/sensu/sensu/blob/cec0044ca96221709d4bbecf45c6f5f1133214b2/lib/sensu/api.rb#L471
This works for sensu because the clients table is pruned, and guaranteed to be up to date.
I don't have a super solution to this except scan over the clients table and a new sources table?
It's a hack, but I agree this is a serious limitation of this fork.
cc @portertech in case he is curious. This problem would have to be solved upstream too if they ever decided to allow this.

Hi Kyle,
I initially tried your suggestion of creating a 'source' entry in redis along with source: entries to track masqueraded clients separately from normal clients but it quickly became complicated.
I found just adding client entries for the masqueraded hosts to redis seems to work quite well: https://github.com/roobert/sensu/commit/f50ceffb82fc1c3be9ac7b29df06e53af34c83c6
Everything looks good in Uchiwa and the masqueraded host ends up with duplicated keepalive data from it's original source host, too.

I don't understand how it would have duplicate data?
Also, does this entry in redis get reaped when the sensu server prunes stale clients?

Keepalives are generated for each client in the client list and then published to rabbitmq here: https://github.com/sensu/sensu/blob/master/lib/sensu/server.rb#L573 - The block compares Time.now to the client[:timestamp] value stored in the client data in redis. Every time event data is processed it gets rewritten to redis as client:real_host and client:masquerading_host with an updated timestamp value (the duplicated data).
Masquerading clients do get pruned as they are treated like any other client.
I hope this makes sense.

I guess we need to solve both problems.

Sensu server should not setup keepalives for masqueraded hosts? (to stop duplicates)
Sensu server should not purne masqueraded hosts from the client table? (but that leads to long term stale clients in the client view right?)

I'm not sure that either of these things are a problem.
The checks are running on an actual machine so it makes sense that the masquerading host has a keepalive even if the keepalive is the same as the real host. It makes sense to me that the masquerading host behaves in the same way as any other host.
Regarding pruning: I mistakenly confused pruning and stale state determination, apologies. I've done some testing removing and stopping clients and everything seems to work OK. I was under the impression that sensu-server doesn't remove data from Redis and I can't see any relevant calls to @redis.del or equivalent in server.rb. Which pruning would you be referring to?

In my use case, I'm sending masqueraded events on an intermittent basis. I don't actually want them to have keepalives and that stuff :( (I think?)
You are right about pruning. I confused it with pruning aggregates. Stale clients are detected and then you get the keepalive timeouts.
But I don't think I want a keepalive timeout for a masqueraded event, again for my use case.

I'd be interested to hear your concerns regarding why you'd prefer to remove keepalives for masqueraded clients. When using Nagios service groups to organise checks it's pretty standard to just set the service host IP to <IP_ADDRESS>. The keepalives still get sent to the service hosts but obviously they never actually trigger an alert.
It may be as simple as adding next if client[:original_source] under line 575: https://github.com/sensu/sensu/blob/master/lib/sensu/server.rb#L575
I'll do some testing since I'm not what effects removing keepalives for a client may have.

(context: I work with @solarkennedy)
Reading this thread, I'm thinking that the problems we're running into mostly stem from the fact that keepalive checks are special: they are the only ones for which the sensu server determines staleness.  I propose that if we generalize the concept of staleness to all checks, this problem gets easier.
My idea is that individual checks would gain a 'timeout' parameter.  determine_stale_clients would become determine_stale_checks, and would have the same function: the sensu server would periodically iterate over all checks and create check results for any which are over their configured timeout values.
By default, clients would not have a keepalive check associated with them.  For backwards compatibility, messages received over the keepalive queue would automatically set up a keepalive check, with timeout_warn = 120 and timeout_crit = 180.  Thus, behavior for existing clients would remain the same.  For situations where an independent process (i.e. not a Sensu agent) is intermittently sending events (which I believe is @solarkennedy's use case), keepalives would not be set up.  However individual checks could specify their own timeouts, which would make it really easy to monitor that check results are actually being submitted.
This solves the original issue by demoting clients from first class citizens into mere bundles of metadata.  The list of all clients returned from the API would be the set of all clients with at least one check defined on them.  Clients with keepalives would be included because (naturally) they have a keepalive check defined, and all other clients would be included from the moment the first check is defined on them.
Hopefully what I've said makes some amount of sense.  It's a big refactor, but I think it's the "right" architecture.  I think @roobert's suggestion of adding that single line to determine_stale_clients makes a lot of sense.  It would allow us to (basically) define clients that don't have keepalives, which is a nice first step towards the architecture I'm proposing.

Hi Josh! Welcome to the fray :)
Are you saying you'd like to send check data directly to sensu-server rather than via sensu-agent or the sensu-agent socket?
You could send check data to a sensu-agents socket running on the sensu server (or anywhere) and at that point you wouldn't need to worry about making what sound like some pretty complicated changes.
I'm not sure I really understand what benefit such a large overhaul would have considering that from a functional standpoint we get all the benefits of the existing system with only these few minor changes.. perhaps I'm missing something? :)
Meanwhile, I've tested this change and keepalives now no-longer exist for masqueraded clients:
https://github.com/roobert/sensu/commit/6a111cd89f821c53cdc9a4a9b396d4fa8d6b4ad7 - I'm still not sure if removing the keepalive is a good idea since now when a collection of checks fail you'd have to go and check the status of the real hosts keepalive in order to establish if it's the cause of the problem.
Perhaps @portertech could weigh in as he may have thought about solutions to this problem, too?

@roobert and I had a very nice chat in IRC about this.  The next step will be a post on the mailing list.

We could add POST /clients and disable keepalives for clients registered w/ the API. We could then apply check "masquerade" to the result "client", before doing validation and processing etc. We would have a real client, w/ real history, that can be interacted w/ as normal.

@solarkennedy Thoughts on the "solution" above?

@portertech that makes it a tad harder to add new "fake" hosts on the fly.
Adding the POST endpoint sounds fine, but it seems that the fake host should be setup automatically, just like a real host is automatically created when it starts sending events?
if check[:source] do
  # fake source detected, add it if it doesn't exist already
  create_client_no_keepalives(:source)
  # apply masquerade logic
  ...

I think @hashbrowncipher said it best when we should treat them all as "sources", it is just sources from the stock sensu client get keepalives? But the sources themselves should be first class citizens.

I've started implimenting some of the suggestions by @portertech here: https://github.com/roobert/sensu/compare/sensu:master...master
By no means finished but so far I've:

moved @solarkennedy's masquerading stuff before the validation code
created API end point for client creation with JSON validation
added :no_keepalive which skips keepalives if set in client data

You can use this to test adding a client:
https://gist.github.com/roobert/585ae4b2a6b04a1e2c67

@solarkennedy hi there! :wave:
We're on a mission to get caught up on all outstanding issues for Sensu (including the Sensu documentation and underlying libraries), and in our ongoing triage I came across a link to this issue. I wonder if this can be closed now that support for "JIT Clients" was introduced in Sensu 0.18 (released in May 2015) (NOTE: we are now starting to call these "Proxy Clients").
/cc @portertech

@calebhailey Totally!

\o/


flutter repo pub.dev, outdated version

Could you please update library version that published in pub.dev? Now it's only 2.1.0 with outdated dependency
Because yandex_geocoder >=2.1.0 depends on http ^0.13.5 and app_flutter depends on http ^1.1.0, yandex_geocoder >=2.1.0 is forbidden.
So, because app_flutter depends on yandex_geocoder ^2.1.0, version solving failed.

It's ok with your last version 2.2.0, it would be great to see it in pub.dev.

Updated in https://github.com/MadBrains/Yandex-Geocoder-Flutter/pull/14


MNT: Re-rendered with conda-smithy 2.2.2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

We have jumped ahead to 1.6.0 and added Python 3.6 in PR ( https://github.com/conda-forge/pykwalify-feedstock/pull/3 ). So am going to close this out.
Hopefully that addresses your concerns, @lexual. If not, please feel free to let us know.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2058 ms

Resolved: Bofrost.at performance has improved in 481e4ba.


happy Rubocop

I don't know why but it became failing on Travis CI, locally everything was fine even with the latest version of Rubocop :thinking:

Doesn't make any sense anymore

Oh I didn't see this! Fixed in #2060.


[INLONG-421] Propose web portal to manage tube cluster Phase-II

JIRA link - [INLONG-421] created by yuanbo

Closed due to TubeMQ manager has merged


Malloc: *** error for object,...

I forgot to mention, that i left running keyhunt for cca 2 days, after error ParsePublicKeyHex: Error invalid public key specified (Not lie on elliptic curve), i get keyhunt(5673,0x70000253d000) malloc: *** error for object 0x600006aaeeb0: pointer being freed was not allocated
keyhunt(5673,0x70000253d000) malloc: *** set a breakpoint in malloc_error_break to debug

To be able to solve this i need to reproduce the behavior. Can you share the exact command that you used? Also list of target that you are using.
Without those two  i can't reproduce the error to debug it.

To be able to solve this i need to reproduce the behavior. Can you share the exact command that you used? Also list of target that you are using.
Without those two i can't reproduce the error to debug it.

I use the commend: ./keyhunt -m bsgs -f 64.txt -R -k 128 -r<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000:fffffffffffffffffffffffffff1111ebaaedce6af48a03bbfd25e8cd0364140 -q -t 8
File of pub. keys:
64.txt


Is it possible to create a network connection to a running vcontrold raspberry pi instance

Hi - I found your project via the Synology NAS Docker application and I wanted to start it there, but I didn succeeded in the first place. Before troubleshotting this, I want to know, if it is possible to grab the data also from a remote (same network) running raspberry pi with already configured vcontrold, running since a couple of years, instead of the local usb connection Thanks a lot,
Mark

Basically this would work as the vclient can also be configured to read the data from a vcontrol server other than localhost. See line: https://github.com/michelde/openv-vcontrold-docker/blob/56f76d04cc70ae8aafe46c63132a7f3c5f029250/startup.sh#L26
But of course you would need to change some things in the startup script.

Thanks a lot for the feedback.
I actually got the docker running and copied my vito,xml and vacontrold.xml into the config folder.
I then installed nano and modified the startup.sh and started it with . startup.sh again.
Every 90 seconds(which I set as interval) I see this error message:

Do you know what additional things need to be changed in the startup script to get this working?
If I have this, I can try to make a copy of the repository and change it for my needs - never done that ;-) and I must see how I can get this than working in the Synology docker instance.

Why you're copying the xml files to the config folder? These are only needed for the vcontrold server. As you're just interested to read the values, you just need to focus on vclient --> https://github.com/openv/vcontrold/blob/master/doc/man/vclient.rst. Just get this running separately and you're almost good to go.


decide whether to perform actions smartly

add options to enabling/disabling wifi or any other state depending on whether
the last state change was initiated by Omnidroid.

This idea came as solution for enabling wifi by Omnidroid when power is plugged
only if it was disabled for bsttery going low by Omnidroid itself.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 7 Nov 2011 at 4:54

Is it possible that triggers could raise flags to vote for a state - 'on', 'off', 'no-vote' - then a task could poll all flags & act accordingly. User would choose 'unanimous' or 'majority' to change state, possibly different for each state.
Eg: WiFi could be controlled by battery level, charging & NFC with User choosing 'majority' to turn on & 'unanimous' to turn off


implements device_state_attributes error

Hi,
getting the error below: case is of an intel iGPU slot not working under folding at home which reports the slot as broke.
I have another FHA instance on another PC (1 slot only) and no issue reported, logging below is not reported for the slot 00 on <IP_ADDRESS>
Logs
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:549
First occurred: 25 dicembre 2021, 23:21:13 (63 occurrences)
Last logged: 25 dicembre 2021, 23:21:13

Entity sensor.192_168_1_92_01_work_server (<class 'custom_components.foldingathomecontrol.sensor.FoldingAtHomeControlSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.192_168_1_92_01_collection_server (<class 'custom_components.foldingathomecontrol.sensor.FoldingAtHomeControlSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.192_168_1_92_01_attempts (<class 'custom_components.foldingathomecontrol.sensor.FoldingAtHomeControlSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.192_168_1_92_01_time_per_frame (<class 'custom_components.foldingathomecontrol.sensor.FoldingAtHomeControlSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.192_168_1_92_01_basecredit (<class 'custom_components.foldingathomecontrol.sensor.FoldingAtHomeControlSensor'>) implements device_state_attributes. Please report it to the custom component author.

Should be resolved in the latest version.

Please reopen the issue if it persists


Signal error when attempting to checkout version out of bounds

What's the reason to accept a version arg which is larger than this.core.length?

It's perfectly reasonable to checkout a future version, for quite a few use cases. For example:

I know that a hyperbee has version 1000, and want to work with it
I checkout version 1000, and try to get a block. Locally I'm at version 900, because I haven pulled in the latest changes yet, so I wait for it
I connect with a peer who knows the hyperbee's length is 1000, and my local length updates
I get the block, and the request resolves

If your application does not want to work with 'future' versions, you can add a check before doing the checkout. But IMO it indicates an incorrect access pattern. For most use cases, either you care about a particular version you already know (so you use a checkout), or you care about the latest version (so you register a watcher to receive continuous updates)

@HDegroote Thank you for the clear explanation!


Send parameters as request body in query and ec2 protocol

issue: #1058
~(This changeset is based on #1059's re-format )~ rebased after #1059 was merged
I've tested with ec2:RequestSpotFleet and iam:ListRoles.

I haven't forgotten about this one!
The code changes look great, I'm running the integration tests just now, and will merge if green!

Unfortunately the SQS integration tests are failing, because they can't delete the message after it has been received:
thread 'sqs_roundtrip_tests' panicked at 'Couldn't delete message: ReceiptHandleIsInvalid("The input receipt handle is invalid.")', tests/sqs.rs:100:22

Maybe this be an issue with the form/url encoding?

That's because the "+" character is replaced with "%2B" in serializer (#824) and re-encoded to "%252B" by serde_urlencoded...
I'm trying to find the right solution for both  #821 and #1058 .

I've noticed that all operations in query/ec2 protocol use POST method.
I removed workaround for the "+" issue because no operations use query string now.

Now that we've gotten 0.33 out of the door, we should try and get this PR over the finish line. /cc @matthewkmayer
@eagletmt Apologies for the long delay here, have we lost your interest or is this still something you're willing to drive? I'm happy to lend a hand in resolving these conflicts as well!

I believe this is done in https://github.com/rusoto/rusoto/pull/1094 which is a rebase of this work. Thanks! 😄


feat: ToPrimitive split into ToFloatPrimitive and ToIntegerPrimitive

Problem
Some restricted VMs/hosts/environments:

Zero knowledge
Multi Party Computation
Embedded
Deterministic Networking Game Engines, consensuses and BFT protocols
Banking

Does not have floating point numbers implemented and their validators/loaders (of code or compiled binary) complain or/and fail to handle code referencing f64/f32
Solution

Split trait into 2, so that downstream crates,
Or feature gate disabling floats

I would be happy to PR it solution has chances to be accepted

Other option is to gate all float methods behind float feature

I have no plans to start making breaking changes. For now, I think if you have such restricted needs, it might be better to just fork into a new crate for your environment.

Thanks for response.
Forking is not good option as will need fork whole crate tree built on top.
Smallest breaking change can be made by making disable of floats only if no default no-floats features is defined.
So if default features are defined on some already existing, all will be as before.
Only issue would be if all-features are used. So I doubt I saw it wide usage.

Features are meant to be additive. If crate A uses num-traits with some current features and uses floats, and crate B turns on the no-float feature, and then both are used as dependencies in some larger project, then A will be broken by B's choice. That's not acceptable.

Forking is not good option as will need fork whole crate tree built on top.

API changes also require the whole tree to adapt, and this crate has thousands of dependents.
You may be able to [patch] in a replacement crate, but overall I'd say that your specialized/restricted needs call for specialized crates.

Features are meant to be additive. If crate A uses num-traits with some current features and uses floats, and crate B turns on the no-float feature, and then both are used as dependencies in some larger project, then A will be broken by B's choice. That's not acceptable.

It looks very desired behavior. If somebody enables "disabling" feature, it will break all float usage in other crates, compilation will fail, which is right. Nobody to use floats.

API changes also require the whole tree to adapt, and this crate has thousands of dependents.

that is clear, anyway just tried to propose :)  so need to adapt on forks or via gate(both likely).

You may be able to [patch] in a replacement crate

Patch will patch crate for all deps, so if any dep will impl float methods, they will fail to compile. So will need to patch all other crates built on top. Num based crates about fractions(ratio) and big integers(bigger than 128) are of interest.

but overall I'd say that your specialized/restricted needs call for specialized crates.

Thank you for response. I understand.
So my understanding (and usage), there are core::ops traits to be used in any context/need/vm. I just peek traits what work for me.  num-traits has a lot of good traits generic enough and I use them a lot (Zero/One/ops).
But To/FromPrimitive are not generic enough, I cannot use to integer vs float primitives. Floats leaks to compilation result as part of format/display/debug routines, which breaks specialized environments.
I can use core::ops without touching float code, but I cannot do that with num-trait, which would be possible num-traits would be generic enough to be used in any context (so basically this states that breaking thousands of dependents is right thing to do  to make num-trait as generic as core::ops). And after that num-rational and num-big and many other crates conforming from num-traits will work out of box for some(my) use cases.

Another possible breaking change tbh can be done accopanying any breaking change
https://docs.rs/num/latest/num/traits/trait.Zero.html
Zero forces to have Add which limits Zero usage. I can have Zero without ability to add.
One is also useful without ability to Mul.
Also some part of num-traits is already splits float to float mod, so To/From primitive looks like just tech dept to split.
Closing for now so.


CORS error, Loading css externally.

In firefox, Many people (like me) enable security.fileuri.strict_origin_policy because of the security (and privacy) implications. However this makes the app inaccissable because it tries to load css file from https://rsms.me/inter/inter.css inside app.blade.php file . I think it is good idea to add this file locally and load it from there.

Ok, am going to change that

any update?

I already pushed it to the dev branch a while back so you can try it out if you want or you have to wait a little while longer until I merge it with the master branch (when the rest of my changes are stable enough).

Is now part of the master branch.

Thanks, works great!


seaborn library requirement breaks Terra

Information

Qiskit Terra version: 0.11.0
Python version:  3.6.7
Operating system: Ubuntu 16.04.6 LTS

What is the current behavior?
Aqua travis is failing due to missing library "seaborn":
ile "/tmp/qiskit-terra-master/qiskit/execute.py", line 24, in
from qiskit.compiler import transpile, assemble

File "/tmp/qiskit-terra-master/qiskit/compiler/init.py", line 35, in
from .transpile import transpile

File "/tmp/qiskit-terra-master/qiskit/compiler/transpile.py", line 19, in
from qiskit.transpiler import Layout, CouplingMap

File "/tmp/qiskit-terra-master/qiskit/transpiler/init.py", line 69, in
from .passmanager import PassManager

File "/tmp/qiskit-terra-master/qiskit/transpiler/passmanager.py", line 19, in
from qiskit.visualization import pass_manager_drawer

File "/tmp/qiskit-terra-master/qiskit/visualization/init.py", line 107, in
from .gate_map import plot_gate_map, plot_circuit_layout, plot_error_map

File "/tmp/qiskit-terra-master/qiskit/visualization/gate_map.py", line 24, in
import seaborn as sns

ModuleNotFoundError: No module named 'seaborn'
Steps to reproduce the problem
Just add the statement: "from qiskit.execute import execute"
What is the expected behavior?
Seaborn should not be required since it is part of optional visualization feature
Suggested solutions
Do not throw exception if seaborn is not present.

It is imported in the has matplotlib block, and listed as part of the same visualization extras package.

The gate_map.py change seems to hinge on a single flag as to whether matplotlib is installed and if set assumes it can import seaborn. So if a system has matplotlib installed, but not seaborn, as they installed matplotlib but not via the Terra visualization option on pip install, which gets other stuff including seaborn, then things fail as reported. So if they have matplotlib but do not even use Terra visualization this would end up forcing such a user to install seaborn too.

Yeah I think we need to revisit the optional import blocks in gate map this same thing actually has been blocking the benchmarking runs at https://qiskit.github.io/qiskit the benchmark runs have all been failing with a seaborn import error since #3508 merged and no updates have been pushed.


Automatically terminate when pinger goroutine fails

Hi - I've spent some time trying to use graphping and been debugging it for a while (also trying to refresh my limited knowledge of Go).
Basically, I got graphping running, but it wasn't sending any data to statsd. I eventually got this error printed out which indicated why pinging wasn't working: "listen ip4:icmp : socket: operation not permitted"
However, that message wasn't logged, so it wasn't obvious that there was a probblem. Also, graphping itself stayed running, even though the pinger goroutines had ceased execution - so it gave the impression that it was active, even though all that graphping was doing waiting for a keyboard interrupt to terminate it.
I've made changes such that any error message in the pinger which causes it to fail will be returned to graphping; graphping will log that message, and then cause graphping itself to terminate.

Thanks so much for your contribution. This project needs a bit of love, so I'll try refactor and clean the code up to make it easier to use as well


Logo Design

Greetings!
This might be a great opportunity to tell you that I am offering logo designs for GitHub projects. And it would be an honor to offer this to you if you wanted me to do so, just mention me. Thanks!

Thanks for your offering. But I don't need it for now. Thinks again.

Do you have a small description of OKsocket wikis? or maybe put some an idea about your perspective output of the logo?
@xuuhaoo

OkSocket is a Java library project designed to solve lightweight Socket communication, in order to enable developers to focus more on business logic, rather than TCP communication principles and some protocols. Make Socket communication more beautiful, suitable for large, medium and small Project, the rapid development of stable, maintainable, reliable Socket connection.
About logo, in my opinion, maybe more cheerful, sunny, professional, and not too complicated. People can remember at a glance

I already have an idea, I hope you will like it. Ill comment it here soon

I dunno if I made it right, I made two designs

I also have a design to be presented later, don't worry.  And I have a question about the logo.

What does that logo mean in your design?

I am very grateful for your contribution. And looking forward to your design.

@xuuhaoo
How about this one?

This version of a lot better. Thank you for your contribution, but I think there are some areas that can be improved. For example, can the overall logo be slightly wider?

How about this one @xuuhaoo

if you have any color ideas, please tell me. So that I can have that variations.

Could you provide this one png part by part

sorry for responding late @xuuhaoo , ill be starting making your request. Have a nice day!


refactor single thread raftstore

Currently the raftstore is single thread model, the single thread handle a lots of jobs, in some cases the single thread will be the bottle neck of whole system. So the one coordinator thread + a worker pool model is more reasonable, coordinator thread handle jobs like synchronous states and schedule, and the worker pool handle the actual jobs.

Multi thread may introduce complexity (especially for merge later), and it is not easy to do it with our current architecture.
We can first using batch for append and apply, then consider using asynchronous apply. This may be more easy to do now. (Of course, maybe the asynchronous apply is also complex and has no big performance improvement. :sob: )


Refresh split min-width on window resize.

Hello! First of all, thanks for provinding this utility.
I'm using Split.js in a simple web app where it's very common to open the developer console, thus resizing the window. I need my left pane to keep a minimum width since otherwise the layout breaks.
Looks like there is no refresh/ fitMin method exposed to be called on window.onresize. Perhaps this could be added for another release?
For now I'm manually triggering click events and somehow it works, although it's pretty ugly and not very efficient :sweat_smile: :
var refreshSplit = function() {
  var mousedown = new CustomEvent('mousedown');
  var mousemove = new CustomEvent('mousemove', {bubbles: true});
  var mouseup = new CustomEvent('mouseup', {bubbles: true});
  var gutter = document.querySelector('.gutter-horizontal');

  mousemove.clientX = gutter.getBoundingClientRect().left;

  gutter.dispatchEvent(mousedown);
  gutter.dispatchEvent(mousemove);
  gutter.dispatchEvent(mouseup);
};

And then throttling that:
var lock;
window.onresize = function() {
  clearTimeout(lock);
  lock = setTimeout(refreshSplit, 100);
};

Great idea. I'll add it to the roadmap.

+1
I'm reading that accomplishing this via timeout could lead to poor performance... how about this:
https://github.com/sdecima/javascript-detect-element-resize

I think this should be fixed in v1.2.0, please test.

@nathancahill I got some time to update to 1.2.0 now, but I'm not sure how this is fixed. Is there any new method to call on window resize? Couldn't find anything and still need to do what I posted originally. Anyway, thanks for the updates! Things like collapse() are really useful :+1:
P.S: About the "semi breaking change", I got the same behavior with some extra code, perhaps you could add something like this to the readme for other users having the same problem:
  var vw = window.innerWidth; // if it's fullscreen
  var minPerc = Math.ceil((minPx + gutterSize) * 100 / vw);

  ... sizes: [minPerc, 100 - minPerc],
  ... minSize: [minPx, 0],


use conventions instead of hardcoded strings

Description:
Refactoring code to use collector conventions

Codecov Report

Merging #2 into main will increase coverage by 0.24%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
+ Coverage   73.39%   73.63%   +0.24%
==========================================
  Files           2        2
  Lines         109      110       +1
==========================================
+ Hits           80       81       +1
  Misses         24       24
  Partials        5        5

Impacted Files
Coverage Δ

locl/config.go
85.26% <100.00%> (+0.15%)
:arrow_up:

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 86af7d6...c243cca. Read the comment docs.


local to public ip change

cvat tool works fine in localhost:8080 in ubuntu 18.04 but when try to change it to public ip it won't do anything, i followed all the instruction given in installation page. i did override yml file likes this
# docker-compose.override.yml
version: "2.3"

services:
  cvat_proxy:
    environment:
      CVAT_HOST: '<IP_ADDRESS>'
    ports:
    - "80:3365"

  cvat:
    environment:
      ALLOWED_HOSTS: '*'

@vasanththangavel Hi
format of ports option should be your public port:80 i.e., you should not change the internal port.
cvat_proxy:
    environment:
      CVAT_HOST: '<IP_ADDRESS>'
    ports:
    - "3365:80"

Please use gitter for such questions in the future, also this guide my be usefull https://docs.docker.com/compose/networking/

@azhavoro i tried that also still not working

Please provide more information about your issue:

what kind of error did you get in the browser?
Please attach logs docker logs cvat and docker logs cvat_proxy

Cvat log attached but there is nothing in cvat_proxy and in google chrome this page is not working somewhat like that error came and there is no console error
cvat log:
`2020-05-18 12:54:59,844 INFO RPC interface 'supervisor' initialized
2020-05-18 12:54:59,844 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-05-18 12:54:59,844 INFO supervisord started with pid 1
2020-05-18 12:55:00,848 INFO spawned: 'ssh-agent' with pid 8
2020-05-18 12:55:00,851 INFO spawned: 'rqscheduler' with pid 9
2020-05-18 12:55:00,855 INFO spawned: 'runserver' with pid 10
2020-05-18 12:55:00,857 INFO spawned: 'rqworker_low' with pid 11
2020-05-18 12:55:00,860 INFO spawned: 'rqworker_default_0' with pid 12
2020-05-18 12:55:00,863 INFO spawned: 'rqworker_default_1' with pid 15
2020-05-18 12:55:00,865 INFO spawned: 'git_status_updater' with pid 17
2020-05-18 12:55:00,866 DEBG 'ssh-agent' stdout output:
SSH_AUTH_SOCK=/tmp/ssh-agent.sock; export SSH_AUTH_SOCK;
echo Agent pid 14;
2020-05-18 12:55:00,867 DEBG 'ssh-agent' stderr output:
debug2: fd 3 setting O_NONBLOCK
2020-05-18 12:55:00,871 DEBG 'rqscheduler' stderr output:
wait-for-it.sh: waiting for redis:6379 without a timeout
2020-05-18 12:55:00,876 DEBG 'runserver' stderr output:
wait-for-it.sh: waiting for db:5432 without a timeout
2020-05-18 12:55:00,878 DEBG 'rqscheduler' stderr output:
wait-for-it.sh: redis:6379 is available after 0 seconds
2020-05-18 12:55:00,879 DEBG 'rqscheduler' stderr output:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2020-05-18 12:55:00,881 DEBG 'rqworker_low' stderr output:
wait-for-it.sh: waiting for redis:6379 without a timeout
2020-05-18 12:55:00,882 DEBG 'rqworker_default_0' stderr output:
wait-for-it.sh: waiting for redis:6379 without a timeout
2020-05-18 12:55:00,883 DEBG 'runserver' stderr output:
wait-for-it.sh: db:5432 is available after 0 seconds
2020-05-18 12:55:00,885 DEBG 'rqworker_default_1' stderr output:
wait-for-it.sh: waiting for redis:6379 without a timeout
2020-05-18 12:55:00,887 DEBG 'runserver' stderr output:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2020-05-18 12:55:00,887 DEBG 'rqworker_low' stderr output:
wait-for-it.sh: redis:6379 is available after 0 seconds
2020-05-18 12:55:00,887 DEBG 'git_status_updater' stderr output:
wait-for-it.sh: waiting for redis:6379 without a timeout
2020-05-18 12:55:00,889 DEBG 'rqworker_low' stderr output:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2020-05-18 12:55:00,889 DEBG 'rqworker_default_0' stderr output:
wait-for-it.sh: redis:6379 is available after 0 seconds
2020-05-18 12:55:00,891 DEBG 'rqworker_default_0' stderr output:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2020-05-18 12:55:00,891 DEBG 'rqworker_default_1' stderr output:
wait-for-it.sh: redis:6379 is available after 0 seconds
2020-05-18 12:55:00,894 DEBG 'rqworker_default_1' stderr output:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2020-05-18 12:55:00,894 DEBG 'git_status_updater' stderr output:
wait-for-it.sh: redis:6379 is available after 0 seconds
2020-05-18 12:55:00,896 DEBG 'git_status_updater' stderr output:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2020-05-18 12:55:00,970 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:00,974 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:00,974 DEBG 'ssh-agent' stderr output:
debug1: type 11
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:00,979 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:00,980 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:00,982 DEBG 'rqworker_low' stderr output:
Identity added: /home/django/.ssh/id_rsa (/home/django/.ssh/id_rsa)
2020-05-18 12:55:00,982 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:00,985 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:00,987 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:00,988 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:00,991 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
debug1: type 11
2020-05-18 12:55:00,992 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:00,994 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:00,996 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:01,000 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:01,003 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:01,004 DEBG 'ssh-agent' stderr output:
debug1: type 11
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:01,004 DEBG 'rqscheduler' stderr output:
12:55:01 Registering birth
2020-05-18 12:55:01,009 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:01,010 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:01,014 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:01,018 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:01,019 DEBG 'ssh-agent' stderr output:
debug1: type 11
2020-05-18 12:55:01,019 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:01,023 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:01,027 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:01,031 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:01,036 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:01,036 DEBG 'ssh-agent' stderr output:
debug1: type 11
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:01,999 DEBG 'rqworker_low' stderr output:
12:55:01 RQ worker 'rq:worker:c853b5325824465b90d65336432d805c' started, version 1.0
2020-05-18 12:55:01,999 INFO success: ssh-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:01,999 INFO success: rqscheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:01,999 INFO success: runserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:01,999 INFO success: rqworker_low entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:01,999 INFO success: rqworker_default_0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:02,000 INFO success: rqworker_default_1 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:02,000 INFO success: git_status_updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-05-18 12:55:02,000 DEBG 'rqworker_low' stderr output:
12:55:01 *** Listening on low...
2020-05-18 12:55:02,000 DEBG 'rqworker_low' stderr output:
12:55:02 Cleaning registries for queue: low
2020-05-18 12:55:02,001 DEBG 'rqworker_default_1' stderr output:
12:55:02 RQ worker 'rq:worker:0fe3b0308b3b44f880574ba7699f4566' started, version 1.0
2020-05-18 12:55:02,001 DEBG 'rqworker_default_1' stderr output:
12:55:02 *** Listening on default...
2020-05-18 12:55:02,002 DEBG 'rqworker_default_1' stderr output:
12:55:02 Cleaning registries for queue: default
2020-05-18 12:55:02,015 DEBG 'rqworker_default_0' stderr output:
12:55:02 RQ worker 'rq:worker:ffc05f35eed14251a98f93f50fc2c49d' started, version 1.0
2020-05-18 12:55:02,016 DEBG 'rqworker_default_0' stderr output:
12:55:02 *** Listening on default...
2020-05-18 12:55:02,816 DEBG 'runserver' stdout output:
Operations to perform:
Apply all migrations: account, admin, annotation, auth, authtoken, contenttypes, engine, git, sessions, sites, socialaccount
Running migrations:
No migrations to apply.
Your models have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
2020-05-18 12:55:03,147 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:03,151 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:03,153 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:03,158 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:03,158 DEBG 'ssh-agent' stderr output:
debug1: type 11
2020-05-18 12:55:03,158 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:03,676 DEBG 'runserver' stdout output:
0 static files copied to '/home/django/static', 386 unmodified.
2020-05-18 12:55:03,866 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:03,870 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:03,874 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:03,878 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:03,879 DEBG 'ssh-agent' stderr output:
debug1: type 11
2020-05-18 12:55:03,879 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:04,765 DEBG 'runserver' stdout output:
Successfully ran command.
Server URL         : http://localhost:8080/
Server Root        : /tmp/mod_wsgi-localhost:8080:1000
Server Conf        : /tmp/mod_wsgi-localhost:8080:1000/httpd.conf
Error Log File     : /dev/stderr (INFO)
Request Capacity   : 5 (1 process * 5 threads)
Request Timeout    : 60 (seconds)
Startup Timeout    : 15 (seconds)
Queue Backlog      : 100 (connections)
Queue Timeout      : 45 (seconds)
Server Capacity    : 20 (event/worker), 20 (prefork)
Server Backlog     : 500 (connections)
Locale Setting     : C.UTF-8
2020-05-18 12:55:04,810 DEBG 'runserver' stderr output:
[Mon May 18 12:55:04.810256 2020] [mpm_event:notice] [pid 10:tid<PHONE_NUMBER>75328] AH00489: Apache/2.4.18 (Ubuntu) mod_wsgi/4.6.2 Python/3.5 configured -- resuming normal operations
[Mon May 18 12:55:04.810325 2020] [mpm_event:info] [pid 10:tid<PHONE_NUMBER>75328] AH00490: Server built: 2019-10-08T13:31:25
[Mon May 18 12:55:04.810331 2020] [core:notice] [pid 10:tid<PHONE_NUMBER>75328] AH00094: Command line: 'apache2 (mod_wsgi-express) -f /tmp/mod_wsgi-localhost:8080:1000/httpd.conf -D MOD_WSGI_MPM_ENABLE_EVENT_MODULE -D MOD_WSGI_MPM_EXISTS_EVENT_MODULE -D MOD_WSGI_MPM_EXISTS_WORKER_MODULE -D MOD_WSGI_MPM_EXISTS_PREFORK_MODULE -D FOREGROUND'
2020-05-18 12:55:04,811 DEBG 'runserver' stderr output:
[Mon May 18 12:55:04.810261 2020] [wsgi:info] [pid 244:tid<PHONE_NUMBER>75328] mod_wsgi (pid=244): Starting process 'localhost:8080' with threads=5.
2020-05-18 12:55:04,811 DEBG 'runserver' stderr output:
[Mon May 18 12:55:04.811093 2020] [wsgi:info] [pid 244:tid<PHONE_NUMBER>75328] mod_wsgi (pid=244): Python home /usr.
[Mon May 18 12:55:04.811143 2020] [wsgi:info] [pid 244:tid<PHONE_NUMBER>75328] mod_wsgi (pid=244): Initializing Python.
2020-05-18 12:55:04,837 DEBG 'runserver' stderr output:
[Mon May 18 12:55:04.837078 2020] [wsgi:info] [pid 244:tid<PHONE_NUMBER>75328] mod_wsgi (pid=244): Attach interpreter ''.
2020-05-18 12:55:04,839 DEBG 'runserver' stderr output:
[Mon May 18 12:55:04.839738 2020] [wsgi:info] [pid 244:tid<PHONE_NUMBER>75328] mod_wsgi (pid=244): Imported 'mod_wsgi'.
[Mon May 18 12:55:04.839778 2020] [wsgi:info] [pid 244:tid<PHONE_NUMBER>75328] mod_wsgi (pid=244, process='localhost:8080', application=''): Loading Python script file '/tmp/mod_wsgi-localhost:8080:1000/handler.wsgi'.
2020-05-18 12:55:05,016 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
2020-05-18 12:55:05,020 DEBG 'ssh-agent' stderr output:
debug1: type 17
2020-05-18 12:55:05,024 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
2020-05-18 12:55:05,030 DEBG 'ssh-agent' stderr output:
debug2: fd 4 setting O_NONBLOCK
debug1: type 11
2020-05-18 12:55:05,030 DEBG 'ssh-agent' stderr output:
debug1: XXX shrink: 3 < 4
`

cvat log looks ok
empty cvat_proxy log indicate that nginx doesn't receive any request
Could you please describe what do you mean as page is not working? What do you see in the browser?

@azhavoro i attached the screenshot for ur reference

seems there is a network issue, could you open chrome devtools and find the failed request to the server and attach details?

@azhavoro there is no response in the console and in network tab nothing info just my ipaddress with failed.

Could you please check that network is ok with base nginx docker image?
 docker run --rm -d -p your_port:80 nginx
note: stop cvat_proxy container before.

Error response from daemon: driver failed programming external connectivity on endpoint sad_bell (35bbd03d9d79acf18293b6ff76476930b272c961d4f105c5b10ff3eb3c33fa24): Error starting userland proxy: listen tcp ip_address: bind: cannot assign requested address.

hmmm, what exact command did you use?

docker run --rm -d -p your_port:80 nginx and before that i stopped cvat_proxy

You should not use IP with -p option, for you case it will be docker run --rm -d -p 3365:80 nginx

@azhavoro after running docker run --rm -d -p 3365:80 nginx i got result like this
docker: Error response from daemon: driver failed programming external connectivity on endpoint mystifying_bell (aad7bdbce2a3e230c1f7e278147ab0fae6aa6b7298b79e2b1815bcb0f44d002c): Bind for <IP_ADDRESS>:3365 failed: port is already allocated.

@azhavoro i just reinstalled everything and do the same following steps, now it's working. Thanks for ur valuable time.

@azhavoro I met the same issue too. And after running docker run --rm -d -p 8080:80 nginx, I got welcom nginx. But the cvat still cannot work normally. Then how to fix this problem?  Thank you~

@MrDiudiu could you please attach your compose config?


Missing built-in datatype: "String"

The css syntax matcher is missing a built-in type: "string"..
➜  gosub-engine git:(main) cargo run -r --bin renderer https://news.ycombinator.com
    Finished `release` profile [optimized] target(s) in 0.27s
     Running `/home/jthijssen/cargobuild/release/renderer 'https://news.ycombinator.com'`
Adapter: AdapterInfo { name: "llvmpipe (LLVM 15.0.7, 256 bits)", vendor: 65541, device: 0, device_type: Cpu, driver: "llvmpipe", driver_info: "Mesa 23.2.1-1ubuntu3.1~22.04.2 (LLVM 15.0.7)", backend: Vulkan }
Adapter: AdapterInfo { name: "D3D12 (Intel(R) UHD Graphics)", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "OpenGL", driver_info: "4.1 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1~22.04.2", backend: Gl }
Parse error: ParseError { message: "expected-doctype-but-got-start-tag", location: (1:27) }
Parse error: ParseError { message: "link element with rel attribute 'icon' is not supported in the body", location: (2:41) }
Parse error: ParseError { message: "link element with rel attribute 'alternate' is not supported in the body", location: (3:91) }
Parse error: ParseError { message: "anything else not allowed in after body insertion mode", location: (169:71) }
thread 'main' panicked at crates/gosub_styling/src/syntax_matcher.rs:307:18:
Unknown built-in datatype: "string"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

My temporary fix was to just don't let it panic at that point :-)

Can't reproduce with the latest version


Update CONTRIBUTORS.md

@dragonsea0927 Thanks for your contribution! I have invited you to the organisation

@all-contributors please add @dragonsea0927 for content


bug(storage): panic: inserted new level is not the newest

Describe the bug
Log: https://us-east-1.console.aws.amazon.com/cloudwatch/home?region=us-east-1#logsV2:log-groups/log-group/$252Fri[…]843c94eb.log$3Fstart$3D1683474600000
To Reproduce
Can be steadily reproduced by running longevity test for more than 8 hours
Expected behavior
No response
Additional context
See more discussions in Slack: https://risingwave-labs.slack.com/archives/C034TRN6A49/p1683509737106699

relevant fix: #9600

fixed by #9600


Feature: Ability to change the border thickness of the statistical button (including 0)

Fixed by a10cd87 commit


[Enhancement]: use kubeconfig in bootstrap_git resource

Description
As a platform builder managing multiple clusters,
I need to create, manage and destroy multiple dynamic clusters without instantiating multiple flux providers, while using a kubeconfig provided from a data or resource source.

Given the complexities of Terraform providers in modules, it would allow ease of use to provide a kubeconfig on bootstrap.
TLDR;
provide kube_config and kube_config_path fields in bootstrap_git if not given in provider config.
Affected Resource(s) and/or Data Source(s)
bootstrap_git
Potential Terraform Configuration
resource "flux_bootstrap_git" "this" {
  path             = "clusters/${var.cluster}"
  components_extra = ["image-reflector-controller", "image-automation-controller"]
  kube_config      = some_provider.kubernetes.kubeconfig # OR
  kube_config_path = "./some/path/here"
}

References
No response
Would you like to implement a fix?
None

What's wrong with multiple Flux providers ? Is it because lack of "for_each" on a list of providers ?

What's wrong with multiple Flux providers ? Is it because lack of "for_each" on a list of providers ?

@JordanP, providers are only available outside of modules. Having multiple providers per-cluster where the kubeconfig (or values) is fed through outputs into the top-level flux provider for that cluster is clunky.
like this (example)
module "cluster-somek8s" {
  source = "./modules/a-cluster-config"
}

provider "flux" {
  alias = "somek8s"
  kubernetes = {
    host                   = module.somek8s.host
    client_certificate     = module.somek8s.cert
    client_key             = module.somek8s.key
    cluster_ca_certificate = module.somek8s.ca
  }
}

module "flux-somek8s" {
  source = "./modules/a-flux-deploy"
  provider = {
    flux = flux.somek8s
  }

  depends_on = [module.cluster-somek8s] # NOTE afaik this is hard to make this module depend on the cluster being up
}

I'd like to be able to have a module for a cluster where defining a cluster also includes Flux, without top-level config needing to be added. This limiting the number of steps to get components up.
Please correct me if you think there's a better way to use the tooling.
If this were possible, it could be able to do something like this (example)
provider "flux" {}

variable "github-token" {}

module "cluster" {
  for_each = toset(["sfo", "syd", "fra"])
  source = "./modules/a-cluster-config-with-flux"

  region = each.key
  github-token = var.github-token

  provider = {
    flux = flux
  }
}

Let me know your thoughts.

@BobyMCbobs I've previously solved this issue using the following approach:

Create a Terraform module called k8s-bootstrapped.
This module does two things:
a. Constructs the Kubernetes cluster (using its own k8s module).
b. Uses the output from the k8s module to feed into the Flux bootstrap process.

This approach is similar to the examples in this repository
To implement this solution, you would use the k8s-bootstrapped module as the main calling module in your Terraform configuration.

@swade1987, thank you for your message. Apologies for the late response.
From what I understand, and please correct me if I'm wrong, the case is that in order to use such a module a new Flux provider will need to be instantiated each time a new cluster is created. The Flux provider will then need to be passed through and this like
module "cluster-1" {
  ...
}
provider "flux" {
  alias = "cluster-1"
  kubernetes = {
    host                   = module.cluster-1.kubeconfig_host
    client_certificate     = base64decode(module.cluster-1.kubeconfig_client_certificate)
    client_key             = base64decode(module.cluster-1.kubeconfig_client_key)
    cluster_ca_certificate = base64decode(module.cluster-1.kubeconfig_ca_certificate)
  }
  git = {
    url =<EMAIL_ADDRESS>    ssh = {
      username    = "git"
      private_key = tls_private_key.flux.private_key_pem
    }
  }
}
module "flux-bootstrap" {
  providers = {
    flux = flux.cluster-1
  }
}

What I'm really after is
module "cluster-1" {
  ...
  provider = {
    flux = flux
  }
}
provider "flux" {}

where the Flux provider kubernetes values can be specified in the flux_bootstrap_git resource.

has there been any movement on this. as a platform engineer I too would like to move the cluster config out of the providers block.  as my provider does not know what my cluster configuration is due to the config being in a tfvars file.  This is creating a blocker for my implementation of Flux CD.


hello the dataset url is unavailable

said like title~

Hello Leeable,
I just check the link. It still works. I suggested you can try again.
https://drive.google.com/drive/folders/1ODov2r_fhO_gzTMeCm9-hZ8DeLMr7pzs?usp=sharing

Can you post the url you used? I just tried and the link is correct.


Convert To ES6 Class Refactoring Creates Unclosed JSDoc comments

TypeScript Version:  2.4.1-insiders20170615
Code
/**
 */
function Wagon(numberOxen) {
    this.numberOxen = numberOxen
}

new Wagon(1)

Trigger the convert to es6 class refactoring on Wagon in new Wagon(1)
Expected behavior:
Refactored to
/**
 */
class Wagon {
    constructor(numberOxen) {
        this.numberOxen = numberOxen;
    }
}

new Wagon(1)

Actual behavior:
Refactored to
/**
class Wagon {
    constructor(numberOxen) {
        this.numberOxen = numberOxen;
    }
}

new Wagon(1)

Here's the tsserver trace
[Trace  - 10:22:03 AM] Sending request: getApplicableRefactors (46). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/zoo/src/ox.js",
    "startLine": 7,
    "startOffset": 5,
    "endLine": 7,
    "endOffset": 10
}
[Trace  - 10:22:03 AM] Response received: getApplicableRefactors (46). Request took 1 ms. Success: true
Result: [
    {
        "name": "Convert to ES2015 class",
        "description": "Convert function to an ES2015 class",
        "actions": [
            {
                "description": "Convert function to an ES2015 class",
                "name": "convert"
            }
        ]
    }
]
[Trace  - 10:22:05 AM] Sending request: getEditsForRefactor (47). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/zoo/src/ox.js",
    "refactor": "Convert to ES2015 class",
    "action": "convert",
    "startLine": 7,
    "startOffset": 5,
    "endLine": 7,
    "endOffset": 10
}
[Trace  - 10:22:05 AM] Response received: getEditsForRefactor (47). Request took 5 ms. Success: true
Result: {
    "edits": [
        {
            "fileName": "/Users/matb/projects/zoo/src/ox.js",
            "textChanges": [
                {
                    "start": {
                        "line": 2,
                        "offset": 1
                    },
                    "end": {
                        "line": 6,
                        "offset": 1
                    },
                    "newText": ""
                },
                {
                    "start": {
                        "line": 6,
                        "offset": 1
                    },
                    "end": {
                        "line": 6,
                        "offset": 1
                    },
                    "newText": "class Wagon {\n    constructor(numberOxen) {\n        this.numberOxen = numberOxen;\n    }\n}\n"
                }
            ]
        }
    ]
}

@sandersn, shall I assign this to you?

Yes, I'll try to fix it with the new "convert JSDoc to types" refactoring. Well, it'll really be a workaround until trivia handling is fixed.

This is fixed now.


Label from abstract classes are not persisted to Neo4j

Abstract classes are not recognized as sources for labels anymore, while labels are still added to a node if the super class can be instantiated. Bellow we can see that a ConstructorDeclaration node has the labels MethodDeclaration and FunctionDeclaration but is missing the important Declaration label. This prevents queries to identify by the abstract types Statement, Expression, Declaration, Type, etc.

Closed by #1374


The data with lon and lat  can be processed?

Hello, i really want to know that how to process the data with lon and lat  . do i have to transport it to Projection coordinatesystem?  thank you

There's a kwarg in the OK class to use lat/lon, it's the coordinates_type kwarg (see the doc string). Currently I believe that's only supported for 2D ordinary kriging, so if you want to use lat/lon for UK you'll have to project the coordinates yourself...

With the v1.4 release (now on PyPI), you can use the coordinate_type kwarg in the OK class. It shouldn't be too difficult to extend this to the other kriging classes.


ResponseMetadata missing in AdminInviteRequestsResponse

[ ] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[x] slack-api-client (Slack API Clients)
[x] slack-api-model (Slack API Data Models)
[ ] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Requirements
Response for AdminInviteRequests is missing "ResponseMetadata" field

Hi, @Dunkhell! Thank you for submitting this! 😄
Looking through the admin.InviteRequests response here and in the other SDKs and I'm noticing response_metadata is not present in any of those or other admin.invite* responses. In the API docs, there's also not really any example responses, so it's harder to tell whether this is intentional.
I'm going to check with the team to see if this is by design or not and will submit an update! 😄

@Dunkhell Thanks for flagging this! You're right that the response_data.next_cursor is missing in the response classes. Will resolve it quickly and ship a new patch version including the change.


Possible memory leak on scrolling virtual flow

I use virtual flow - and I noticed that on scrolling used java memory added 200 MB. Firstly I thought that something was wrong with my code, but the same problem I found using RichTextFX.
This is test code:
public class JavaFxTest10 extends Application {

    @Override
    public void start(Stage stage) throws IOException {
        var path = Paths.get("/home/pavel/Temp/RichTextFX/richtextfx/src/main/java/org/fxmisc/richtext/GenericStyledArea.java");
        String content = Files.readString(path, StandardCharsets.UTF_8);
        var codeArea = new CodeArea(content);
        var scrollPane = new VirtualizedScrollPane(codeArea);
        VBox.setVgrow(scrollPane, Priority.ALWAYS);
        Scene scene = new Scene(new VBox(scrollPane), 500, 200);
        stage.setScene(scene);
        stage.show();
        codeArea.selectRange(30, 200);

    }

    public static void main(String[] args) {
        launch(args);
    }
}

And this is the result (system monitor + test application):

As I understand that with virtual flow same row instances are used for all text lines, then why used memory increased so significantly?

Can you drill down and see what's taking up the memory ?


ci: migrate to github actions

This migrates the build and release process to GitHub Actions.
JSDoc was bumped because a nested dependency was throwing an error.
Fix: https://jira.dhis2.org/browse/TECH-513

i was hoping we could make this non-breaking with the exports field in package.json which is supported by webpack@5, but react-scripts is still on webpack@4 :-(

I worry a bit about this... we use (unfortunately) deep imports from d2 all over the place.  We could, as you suggested @varl, move d2 to @dhis2/legacy-d2 or something (I hesitate to squat yet another d2 2-character package name for one we want to get rid of sooner than later) and restart versioning at 1.0.0, but there are some implicit server-version dependencies that might get tricky if we end up needing to go in and fix support for them within the library itself, as those would also be "breaking changes" but require branching...
I think probably the cleanest thing to do is just to keep everything as it was here.... I know it's ugly, but could we build into the ./ directory into ./build so as not to mess with deep imports/

I think probably the cleanest thing to do is just to keep everything as it was here.... I know it's ugly, but could we build into the ./ directory into ./build so as not to mess with deep imports?

I found the last fragment of this sentence a bit tricky, but if you meant "build ./ into the ./build", that still means that we need to run the release command from inside the ./build directory which is what the release script does not support.
We could do it the other way around (maybe this is what you meant), and build everything into ..

  I meant "build into the ./ directory instead of ./build (your "other way around")

I guess we previously built into build but made a temporary build package.json there?

I guess we previously built into build but made a temporary build package.json there?

Correct.

Got it... yeah building into ./ would work, and there aren't currently any conflicts, but it is pretty gross

Result from the resulting yarn pack:
varl@veronika:~/tmp/package$ ls --group-directories-first -1
analytics
api
current-user
datastore
docs
geofeatures
i18n
lib
logger
model
pager
period
src
system
CHANGELOG.md
LICENSE
README.md
config.js
config.js.map
d2-browser.js
d2-browser.js.map
d2-browser.min.js
d2-browser.min.js.map
d2.js
d2.js.map
defaultConfig.js
defaultConfig.js.map
package.json
uid.js
uid.js.map
webpack.config.dev.js
webpack.config.prod.js

It's not perfect; src/ and webpack.config.*.js are included, but I think that .gitignore and files are reasonably clean and self-explanatory ... even if they aren't self-evident.


Change datepicker Cancel/OK buttons text (Android)?

React Native version: latest
Steps To Reproduce

Create new app
Try using Datepicker in Android
Try to change cancel/ok button's text

Describe what you expected to happen:
I could not find any related documentation about it, is there any way to do it?
Snack, code example, screenshot, or link to a repository:

I'm still waiting for answer and solution stale (be a good bot and remove the label)

Hi @dehghani-mehdi datetime picker has been moved to https://github.com/react-native-community/react-native-datetimepicker, try out that module and see if the issue persists.
Otherwise, open the issue there.
cc @TheSavior to close


Depend on linfa-clustering by path

This makes no difference for people getting it from crates.io but simplifies local development greatly.
See Specifying path dependencies in the Cargo Book.

I did this originally, but I moved to depending on a version to release linfa on crates.io. I'd be interested to see if cargo publish is happy with this when I try to release the next version (path + version).
Anyway, we can get it in for ease of local development and we'll sort it out when we need to get a release out.
Thanks for filing this 👍

It works because Cargo rewrites the Cargo.toml file to only have the version, when it packages into a crate (if you run cargo package you can see this crate, it has a different Cargo.toml and yours as Cargo.toml.orig). They are pretty smart :+1:


Let submit.py accept a json config file for input args

User story
scripts/cluster/submit.py currently requires typing out the arguments manually. We should add support for parsing a single json config file with all the parameters (either using argschema or something else)
Acceptance criteria

[ ] This is something that can be verified to show that this user story is satisfied.

Sprint Ready Checklist

[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
[ ] 6. Ticket is prioritized and sized

Notes
Add any helpful notes here.

no longer an issue


Implement dependency injection

I'm submitting a ...

[x] feature request
[ ] support request

Expected Behavior

With dependency injection, the code modularity can be increased
Actual Behavior

What is the motivation / use case for changing the behavior?

Your Environment

App version used:

Device Name and version:

Operating System and version:

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

add dagger 2 in the project and synced successfully

the android dagger has been implemented


OverrideCursor not being cleared

When a drag is released over itself or some other item that is not a valid drop target the Mouse.OverrideCursor is never cleared out like it is on a successful drop.  I overrode the DragCancelled function in my program to do this but it should probably get cleared out somewhere in the default handler as well so the cursor isn't stuck as an arrow.  Something like,
public virtual void DragCancelled()
{
if (Mouse.OverrideCursor != null)
{
Mouse.OverrideCursor = null;
}
}

@Trakcf Can you create a sample which shows this issue? With which version does this happen?


docker: sign container images pushed to GHCR with GitHub OIDC tokens

What does this PR change? What problem does it solve?

This allows users to verify the authenticity and integrity of Restic Docker images before using them.
This provides users with a verifiable record of how, when and where an artifact was built.

Refer:

https://github.blog/security/supply-chain-security/safeguard-container-signing-capability-actions/
~~https://github.com/sigstore/cosign-installer~~
Generation of SLSA3+ provenance for container images

[Edit]
Changes made to the GitHub Workflow:

installing cosign v2.4.0
add new step to sign all the images generated during the build and push step
the id-token of the GitHub Actions workflow will be used for image signing
replace branch-based tagging with SHA-based tagging since, branch names are mutable, SLSA provenance requires immutable tagging
use official SLSA framework Github Reusable workflow
[\Edit]

Was the change previously discussed in an issue or on the forum?
Closes #4983
Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[x] I have added documentation for relevant changes (in the manual).
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

@MichaelEischer need some more time to test. facing some issue during the slsa verification.

@MichaelEischer I guess you can do a final review and merge this.
As for

I am not sure how the build-and-push steps work to upload to Dockerhub. Let me see if I can make this a generic solution which would work for any repository, not limited to Dockerhub and GHCR.

I will pick it up in a separate issue.