SDRplay API sometimes stops working, enhancement request

Bug: The tests aren't giving the API enough time to release the SDR before the next test starts, causing occasional failures of the script when testing as the API and SDR are still being claimed by the previous instance of dumphfdl.
Enhancements: show current sate and time when the script runs, rotate hfdl.log daily at midnight

GitHub isn't letting me create a pull request. Here's the diff I was going to submit.
--- ./hfdlscript1.sh	2022-04-10 15:36:38.311890589 +0800
+++ ./hfdlscript2.sh	2022-04-10 15:14:15.698009781 +0800
@@ -1,5 +1,9 @@
 #!/bin/bash

+# shows the date and time this script ran
+currentDate=`date`
+echo $currentDate
+
 trap 'echo "[ERROR] Error in line $LINENO when executing: $BASH_COMMAND"' ERR

 ##############################################################
@@ -8,11 +12,11 @@

 #this script is written for use with an sdrplay sdr on a computer with a fast #multicore processor running linux. At least a Raspberry Pi 4 or a mini PC recommended. Modify the script as needed for use with an airspy hf+ discovery sdr (consult your sdr's documentation for sampling rate, gain and other settings information.)

-#you must specify the testing duration for each array of frequencies from the command line when you run the script, for example ./dumphfdl.sh 2m or ./dumphfdl.sh 90s. Choose the lowest duration that still gives you a good representative sample of current activity on the frequencies.
+#you must specify the testing duration for each array of frequencies from the command line when you run the script, for example ./hfdl.sh 2m or ./hfdl.sh 90s. Choose the lowest duration that still gives you a good representative sample of current activity on the frequencies.

-#the script may be automatically run at intervals as a cron job if you wish. Example: run crontab -e and at the end of the file add 0 * * * * cd /home/pi/dumphfdl && ./dumphfdl.sh 2m
+#the script may be automatically run at intervals as a cron job if you wish. Example: run crontab -e and at the end of the file add 0 * * * * /home/pi/dumphfdl/hfdl.sh 2m  > /home/pi/hflog/cron.log 2>&1 (which will also log the output of the script plus any error messages)

-#to close dumphfdl after running the script, run pkill -9 -f dumphfdl in another terminal window
+#to close dumphfdl after running the script, run pkill dumphfdl in another terminal window

 ###############################################################

@@ -20,10 +24,19 @@
 LOGFILE="/home/pi/hflog/hfdl.log"
 ERRORLOG="/home/pi/hflog/hfdl.error.log"

+# rotates the hfdl log daily
+currentTime=`date +%H:%M`
+currentDate=`date +%F`
+if [ $currentTime == "00:00" ] && [ -f "$LOGFILE" ];
+then
+			pkill dumphfdl;
+			sleep 5
+			mv "$LOGFILE" "/home/pi/hflog/hfdl_${currentDate}.log"
+fi
+sleep 5

 # use tail -f /home/pi/hflog/hfdl.log to follow the output when the decoder is running

-
 #name for the frequency group
 fname=()

@@ -40,23 +53,23 @@
 #include an optimal sampling rate, gain settings, a count 0 and a friendly name for each frequency group if you have changed them to add more groups

 # group 1
+fname+=("11M13M")
+freq+=("11306 11312 11318 11321 11327 11348 11354 11384 11387 11184 11306 13264 13270 13276 13303 13312 13315 13321 13324 13342 13351 13354")
+samp+=("3000000")
+gain+=("IFGR=53,RFGR=2")
+
+# group 2
 fname+=("5M6M")
 freq+=("5451 5502 5508 5514 5529 5538 5544 5547 5583 5589 5622 5652 5655 5720 6529 6535 6559 6565 6589 6619 6661")
 samp+=("2000000")
 gain+=("IFGR=45,RFGR=4")

-# group 2
+# group 3
 fname+=("8M10M")
 freq+=("8825 8834 8843 8851 8885 8886 8894 8912 8921 8927 8936 8939 8942 8948 8957 8977 10027 10060 10063 10066 10075 10081 10084 10087 10093")
 samp+=("2000000")
 gain+=("IFGR=53,RFGR=2")

-# group 3
-fname+=("11M13M")
-freq+=("11306 11312 11318 11321 11327 11348 11354 11384 11387 11184 11306 13264 13270 13276 13303 13312 13315 13321 13324 13342 13351 13354")
-samp+=("3000000")
-gain+=("IFGR=53,RFGR=2")
-
 # group 4
 fname+=("17M")
 freq+=("17901 17912 17916 17919 17922 17928 17934 17958 17967")
@@ -87,11 +100,14 @@
 dumpcmd+=( --output decoded:basestation:tcp:mode=server,address=<IP_ADDRESS>,port=29109 )

 # output data into VRS, add # in front of the line to deactivate
-dumpcmd+=( --output decoded:basestation:tcp:mode=server,address=<IP_ADDRESS>,port=20003 )
+dumpcmd+=( --output decoded:basestation:tcp:mode=server,address=<IP_ADDRESS>,port=20005 )

 # output data into experimental adsbexchange aggregation (not shown on main page for the moment)
 dumpcmd+=( --output decoded:basestation:tcp:mode=server,address=feed.adsbexchange.com,port=32600 )

+# use your local basestation database to look up aircraft details or add a # in front of the line to not use a basestation database
+dumpcmd+=( --bs-db /home/pi/dumphfdl/Basestation.sqb --ac-details verbose )
+
 # change the LOGFILE variable at the top to modify where the more permanent logfile is
 dumpcmd+=( --output "decoded:text:file:path=$LOGFILE")

@@ -117,13 +133,13 @@
 trap 'echo "[ERROR] Error in line $LINENO when executing: $BASH_COMMAND"' ERR

 #this kills any currently-running dumphfdl and tail tasks. (If you tail or multitail the hfdl.log, not killing tail tasks will leave several zombie tail processes running which could impact your computer's performance.)
-pkill -9 -f dumphfdl || true
-pkill -9 -f tail || true
+pkill dumphfdl || true
+pkill tail || true
 sleep 5

-#sdrplay api is sometimes unstable so this restarts it to be sure it's working. You will be prompted to enter your password unless you have edited your /etc/sudoers file with visudo to allow the command to run without your password which is needed to run the script automatically in cron. Example: "pi     ALL=(ALL) NOPASSWD: /bin/systemctl restart" sdrplay
-sudo systemctl restart sdrplay
-sleep 5
+# if the sdrplay api sometimes becomes unresponsive remove the # from the front of the next two lines. You will be prompted to enter your password unless you have modifed /etc/sudoers.
+#sudo systemctl restart sdrplay
+#sleep 5

@@ -162,6 +178,7 @@
     printf "%-20s%-15s%-25s%-26s%-18s\n" "${fname[$i]}" "score: ${score[$i]}" "stationMessages: ${stationMessages[$i]}" "aircraftMessages: ${aircraftMessages[$i]}" "positions: ${positions[$i]}"
     echo --------
     (( i += 1 ))
+    sleep 10
 done

@@ -189,7 +206,7 @@

 #this ends the script and runs dumphfdl using the above parameters and the most-acive frequency array using its gain reduction settings and sampling rate

-#NOTE: if something is wrong with your script it will always default to using the first frequency array
+#NOTE: if something is wrong with your script or if no messages were received it will always default to using the first frequency array

 longcmd=( "${dumpcmd[@]}" --gain-elements ${gain[$k]} --sample-rate ${samp[$k]} ${freq[$k]} )

And the comments about the changes.
1. Added: Print current date and time to stdout. Useful when saving the script's output to a logfile when running it in cron to make sure your cron job is running as the cron.log file will show the date and time that the script last ran at the top

2. Added: Rotate hfdl.log daily at midnight, appending the current date to the filename, to prevent hfdl.log from getting too big over time while still retaining all of the old logs for those who wish to refer back to them

3. Moved 11M13M to group 1 (if dumphfld receives no messages on any frequency group during the short testing duration it will default to using the first group. 5M6M are dead during daytime while 11M13M may have some activity at any time of day or night as they're neither too low nor too high, so it's a better choice for a default group than 5M6M)

4. Changed pkill -9 -f dumphfdl to pkill dumphfdl to do a graceful shutdown of dumphfdl rather than abruptly force-killing the process, to ensure that the API is properly released by dumphfdl and doesn't hang

5. Added a 10 second delay after each test to give sdrplay time to release the stream and API prior to running the next test. This is what caused the "buggy" behavior of the API where it would sometimes not work and hfdl.error.log would say "could not open SoapySDR device: no available RSP devices found", because the RSP1A and the sdrplay API are slow to release the stream after the SDR application software has been closed.

6. Added and edited various comments to reflect the above changes

7. Changed the default VRS port number from 20003 to 20005 to match the port shown in the example screenshot in the dumphfdl readme, showing how to configure a push receiver for HFDL in VRS as most people will probably use that port


[CROSSDATA-187] [SERVER] JMX Metrics moved to Server

JMX Metrics were in the core and were move to server.
Also, some renaming from crossdata.catalog to crossdata-core.catalog in conf files

+1

+1


[release-1.25] Nodes joined with kubeadm-style bootstrap tokens cannot automatically rejoin when the node object is deleted

https://github.com/k3s-io/k3s/issues/7797 backport

Validated on Version:
-$ k3s version v1.25.11+k3s-f7ab577c (f7ab577c)

Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu 22.04
Windows 2019
Cluster Configuration:
2 node cluster
1 server
1 agent
Steps to validate the fix

Generate token 24h on server
Used the token generated to join the agent node
Deleted agent node after stopping agent service
Deleted password file on agent node
After starting the agent service now, agent refuses to join the cluster with below logs on server and agent
Check kubectl get nodes
Check kubectl get pods -A

Validation Results:

$ k3s -v
    k3s version v1.25.11+k3s-f7ab577c (f7ab577c)

$ k3s token create --ttl 24h

$ k get nodes
    NAME               STATUS   ROLES                       AGE     VERSION
    ip-172-31-27-176   Ready    control-plane,etcd,master   5m57s   v1.25.11+k3s-f7ab577c
    ip-172-31-30-209   Ready    <none>                      2m34s   v1.25.11+k3s-f7ab57

~$ k delete node ip-
        node "ip-" deleted

~$ k get nodes
        NAME               STATUS   ROLES                       AGE     VERSION
        ip-172-31-27-176   Ready    control-plane,etcd,master   6m46s   v1.25.11+k3s-f7ab577c

On agent:

$ sudo rm -rf /etc/rancher/node/

Rejoin agent restarting service:

$ sudo systemctl restart k3s-agent

On server:

$ k get nodes
        NAME               STATUS   ROLES                       AGE   VERSION
        ip-172-31-25-175   Ready    <none>                      11s   v1.25.11+k3s-f7ab577c
            ip-172-31-27-176   Ready    control-plane,etcd,master   68m   v1.25.11+k3s-f7ab577c

~$ kgp -A
            NAMESPACE     NAME                                      READY   STATUS      RESTARTS      AGE
            kube-system   coredns-8b9777675-twhj4                   1/1     Running     1 (67m ago)   69m
            kube-system   helm-install-traefik-8tbqn                0/1     Completed   1             69m
            kube-system   helm-install-traefik-crd-hrgkc            0/1     Completed   0             69m
            kube-system   local-path-provisioner-69dff9496c-rn5wf   1/1     Running     2 (66m ago)   69m
            kube-system   metrics-server-854c559bd-4r4qw            1/1     Running     2 (66m ago)   69m
            kube-system   svclb-traefik-83ef5f0f-7cghh              2/2     Running     2 (67m ago)   69m
            kube-system   svclb-traefik-83ef5f0f-9q4pb              2/2     Running     0             3m30s
            kube-system   traefik-66fd46ccd-br76c                   1/1     Running     1 (67m ago)   69m

        ```


Solved right-click, droppable.accept only once called

Solved right-click: #16
If you do removeEventListener, you need to pass same args as you do addEventListener.
Solved #15

droppable.accept function is only for first check in order to activate the droppable;
Deactivate the useless droppables and set canUse to false;
Added a canUse variable in the constructor of each droppable and when it is activated you set it on true, it means you can use that specific droppable with the draggable;

The accept method of a droppable instance needs to check the incoming draggable/sortable against the 'accept' option of that droppable that can be either a function or a CSS selector. The behavior cannot be removed since it breaks an existing functionality.
The fix on the removeEventListener call for the 'contextmenu' event will be incorporated.


Bump to 0.12.6

Also add myself as a maintainer.

@oblute Any chance you could review please?

LGTM

@mariusvniekerk I'm one of the founders of wandb.  We would love to find a way to update this feedstock whenever we cut new releases to pypi.  Would that be something you would be open to?

@vanpelt you can add yourself as a maintainer to this feedstock

Hi, just curious why your meta.yaml looks so different from the default one generated by conda skeleton?  Namely requirements.host and test.
Here is what I got when I ran conda skeleton
{% set name = "wandb" %}
{% set version = "0.12.7" %}

package:
  name: "{{ name|lower }}"
  version: "{{ version }}"

source:
  url: "https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz"
  sha256: d1c2a6cd3fc57b5a75ff18d4bb69f088d0bd1d0ad22c98005a37e037c85442c7

build:
  number: 0
  entry_points:
    - wandb=wandb.cli.cli:cli
    - wb=wandb.cli.cli:cli
  script: "{{ PYTHON }} -m pip install . -vv"

requirements:
  host:
    - click >=7.0,!=8.0.0
    - configparser >=3.8.1
    - docker-pycreds >=0.4.0
    - gitpython >=1.0.0
    - pathtools
    - pip
    - promise >=2.0,<3
    - protobuf >=3.12.0
    - psutil >=5.0.0
    - python
    - python-dateutil >=2.6.1
    - pyyaml
    - requests >=2.0.0,<3
    - sentry-sdk >=1.0.0
    - shortuuid >=0.5.0
    - six >=1.13.0
    - subprocess32 >=3.5.3
    - yaspin >=1.0.0
  run:
    - click >=7.0,!=8.0.0
    - configparser >=3.8.1
    - docker-pycreds >=0.4.0
    - gitpython >=1.0.0
    - pathtools
    - promise >=2.0,<3
    - protobuf >=3.12.0
    - psutil >=5.0.0
    - python
    - python-dateutil >=2.6.1
    - pyyaml
    - requests >=2.0.0,<3
    - sentry-sdk >=1.0.0
    - shortuuid >=0.5.0
    - six >=1.13.0
    - subprocess32 >=3.5.3
    - yaspin >=1.0.0

test:
  imports:
    - wandb
  commands:
    - wandb --help
    - wb --help
  requires:
    - mock >=2.0.0
    - tox-pyenv >=1.0.3

about:
  home: "https://github.com/wandb/client"
  license: MIT
  license_family: MIT
  license_file:
  summary: "A CLI and library for interacting with the Weights and Biases API."
  doc_url:
  dev_url:

extra:
  recipe-maintainers:
    - your-github-id-here


Final group capstone - Book an Appointment- Frontend

Pull Request: Frontend Implementation
Description
This pull request represents the frontend implementation for the website. It introduces the following key features:

User login with proper authentication.
Navigation panel with links to various sections.
Display of a list of items selected as a theme.
Details page for each item.
A responsive design for both mobile and desktop versions.

Features Implemented
User Authentication

Implemented proper user authentication, allowing users to log in using their email and password.

Navigation Panel

Added a navigation panel with links to the following sections:

Trades.
"Reserve" form.
"My Reservations."
"Add Trade" (visible to admin users).
"Delete Trade" (visible to admin users).

Item Listing

On the main page, displayed a list of trades.

Item Details

Implemented a details page for each item, where users can view the full description and reserve the item by clicking the "Reserve" button.

Responsive Design

Created a responsive design that adapts to both mobile and desktop versions, ensuring a seamless user experience on different devices.

Additional Features (For Teams with 3-4 & 5 Members)

Added the ability for users to delete items from the navigation panel, which marks the selected item as removed and hides it from the main list.
Implemented a reservation system where users can select a date and city for their appointments, with autofilled username and selected item.
Used a design similar to "Book a Vespa Test-Ride" for the reservation page, including all necessary inputs.
Provided a "Reserve" link in the navigation panel for quick access to the reservation page, with autofilled username.

My Reservations

Users can view a list of their reservations in the "My Reservations" section, displaying item names, dates, and cities.

Documentation

Added comprehensive documentation for the frontend implementation, including any API-related details.

Additional Features (For Teams with 5 Members)

Implemented proper user authentication from the frontend to the server.
Ensured that "Add Item" and "Delete Item" links are accessible only by users with admin privileges.

Purpose
This pull request enhances the frontend of the website, making it more user-friendly, responsive, and feature-rich. It enables users to browse, view details, reserve items, and manage their reservations efficiently.
Checklist

[x] Implemented user authentication via username.
[x] Added a navigation panel with links to relevant sections.
[x] Displayed a list of theme-based items on the main page.
[x] Created a responsive design for both mobile and desktop versions.
[x] Implemented item details pages with reservation functionality.
[x] Added the ability to delete items (for teams with 3-4 & 5 members).
[x] Implemented a reservation system (for teams with 3-4 & 5 members).
[x] Documented the frontend implementation comprehensively.
[x] Implemented proper user authentication (for teams with 5 members).
[x] Ensured restricted access to admin-related links (for teams with 5 members).

Testing
The frontend implementation has been thoroughly tested to ensure functionality, responsiveness, and security. Test cases cover user authentication, navigation, item listing, details pages, and additional features as applicable.
Documentation
Comprehensive documentation for the frontend implementation has been provided. Reviewers and team members can refer to the documentation for insights into the implementation details.
Backend API PR
You can review the details of these changes in the Backend API Pull Request.
Please feel free to leave any feedback or suggestions related to the integration of the frontend with these backend changes.

This pull request represents the frontend enhancements for the website. Your feedback and input are valuable in ensuring the quality and functionality of these improvements. Thank you!


The DynamicThreadPool does not seem to revive new workers after they are killed

We currently used DynamicThreadPool with min: 2, max: 8 workers.
The workers start with 2 worker and after we used several workers, they scale up to 8 as expected. (maxInactiveTime)
After 60 seconds of idle-time, they scale down and the exit-handler is fired. (worker.on('exit', ...)
But if we then request some new workers after they were killed, it seems they don't scale up to 8 again :thinking:
We started to modified the code in node_modules and tried to just remove worker from this.workers, but it seems that this wasn't enough to let it know to respawn new workers after they were killed
https://github.com/pioardi/poolifier/blob/5806029f3bdc6bc31d8cc8a611f77f5f3d2c1c88/lib/dynamic.js#L44-L49
The worker.on('online', ... event wasn't fired again after the 8 workers scaled down to 2 and expected to re-scale up
I'm interested to help on this issue/bug, but currently you may know your code better and therefore could potentially identify the real problem more quickly

Wow this Is really interesting, I am currently from my phone ( and a Little busy this week in general) , but I will try to replicate the issue and let you know ASAP

So I replicated the issue and maybe I have a fix , I need a more deep test before to merge :
on the file dynamic.js , after the line 47 we need to add :
      const myIndex = this.workers.indexOf(worker)
      const removed = myIndex > -1 ? this.workers.splice(myIndex, 1) : false
      console.log(this.workers.length)

and we are done , I did a quick test and is working . Going to fix this as soon as I can and if you want to do a test or a PR on your own I would be really happy !!!!
Thanks to catch this !

We have already tried this (maybe not well enough)
But I think this isn't enough, because the workers doesn't scale up again
Seems to have to do something with
https://github.com/pioardi/poolifier/blob/5806029f3bdc6bc31d8cc8a611f77f5f3d2c1c88/lib/dynamic.js#L38
And tasks
https://github.com/pioardi/poolifier/blob/5806029f3bdc6bc31d8cc8a611f77f5f3d2c1c88/lib/dynamic.js#L27
So I think we also need to clean the workers from the tasks map
This we havn't tried yet

Yes I guess we are near to fix it , I did a quick and basic test but seems to work properly it start from 2 , then go to 8 , then on 2 and then to 8  and so on...
For the tasks map , would be good to clean the entry but is not mandatory , I will do that anyway to clean the memory :)

@Shinigami92  I fixed this issue and added a unit test about this , use the version 1.2.1 and see if works well also for you.
I will keep this open for today, hoping you are able to take your test today :)
Thank you much to catch this issue , I wanted to fix it as soon as I can .
Note: For the other issues I will need a little more time

Thank you and yes I will try to test it today but today is meeting day :wink:, so maybe I don't find the time within working hours
So could be late or could be tomorrow
I will look into your (code-)changes right now :eyes: and do a kinda review :cat:

Thanks @Shinigami92  , I would like to connect with you on linkedin ( I post something on poolifier sometimes there )

Sorry I don't have LinkedIn :sweat_smile:
But if you want contact me outside of GitHub, you can see some possibilities in my GitHub profile like Twitter or EMail

Test will more be tomorrow :slightly_frowning_face:, sorry

Is ok, take your time :)

We at adSoul are happy to inform you that everything is working now :tada:


test(transform): action will only runs the first handler

Motivation
The first time action.run(handler) is called, action.activeScenario will be assigned. And there is no way to reset action.activeScenario to null because activeScenario is private and there's no method for updating it. The added test is to make this behavior clear.
class BaseAction {
  // ...

  private activeScenario:
    | SyncScenarioForAction<TAction>
    | AsyncScenarioForAction<TAction>
    | null = null;

  public run(handler) {
    if (!this.activeScenario) {
      this.activeScenario = handler.call(this);
      this.activeScenarioNextResults = [];
    }

    // ...
  }

  // ...
}

Summary

Add a new test case for clarifying how action runs multiple handlers.
Test plan

Hi @wtlin1228
Action is not designed to run against more than one scenario. Could you please explain how you encountered this issue?

Hi @Anber
I was just trying to understand how transform works. Then I saw Action and found it only run the first handler it gets. It makes sense if Action is designed this way. No wonder all the test cases in BaseAction.test.ts use the same handler. Please feel free to close this PR if you think it's unnecessary or kind of misleading.

@wtlin1228 Your investigation highlighted a problem that could lead to issues with HMR in Webpack and probably some other tricky bugs. Thank you!


Run make serve and make initdb simultaneously?

At the NYC Python/PyLadies mini-sprint, one of the attendees was following the instructions in the documentation to set up his development environment.  He was confused about whether make serve and make initdb should be run sequentially or simultaneously.
I have always been running the commands simultaneously (I run make serve, and while that is printing things to stdout I run make initdb in another terminal window). It's always worked for me. Should we tell people to run the commands simultaneously in the documentation?

Maybe we just need to ditch the "Quickstart for Developers with Docker experience" section entirely? The detailed instructions are pretty clear about this particular step.

That would probably fix some of the confusion.
Out of curiosity, when you are setting up your environment, do you run make serve and make initdb simultaneously?

The database needs to be up before it can be initialized, so the correct thing to do would be to run make serve in one terminal, and once the database is up, run make initdb in another (since make serve will run indefinitely`).


feat: support create multi oss client

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

1.8.0


More sophisticated smoothing

Currently smoothing is achieved by discarding close points. This method is not "shape aware" so points significant to the course of the route are as likely to be lost as those that lie in a straight line. A better smoothing algorithm might at minimum check whether candidate discard points lie in line with their neighbors. Moving points to preseve shape while minimizing point count is another option. Research existing simplification algorithms.

The distFilter function in ScanPoints looks at a "current" point and the previous retained point to determine segment length and whether to keep the current point. Lookback a few points to get recent average direction vector. Consider current segment divergence..

Use the [Visvalingam](http://web.cs.sunyit.edu/~poissad/projects/Curve/about_algorithms/whyatt] algorithm. Various js implementations exist.


Removed locks from internal queue.

The queue is accessed in outer strand.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.53%. Comparing base (9921906) to head (2934f76).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   89.53%   89.53%
=======================================
  Files          97       97
  Lines       10470    10471    +1
=======================================
+ Hits         9374     9375    +1
  Misses       1096     1096

Files
Coverage Δ

include/async_mqtt/util/ioc_queue.hpp
100.00% <100.00%> (ø)


Plugin version in the project file shows not accurate

With: 0.19.2
See: $ operator-sdk init -h
--plugins strings          Name and optionally version of the plugin to initialize the project with. Available plugins: ("go.kubebuilder.io/v2")
See: $ operator-sdk init --plugins=go.kubebuilder.io/v2:
$ cat PROJECT
domain: my.domain
layout: go.kubebuilder.io/v2
repo: github.com/example-inc/memcached-operator
version: 3-alpha
plugins:
  go.operator-sdk.io/v2-alpha: {}

With master c9348b5e9800c30817e979c5e5234c355c919d0c:
See: $ operator-sdk init -h
      --plugins strings          Name and optionally version of the plugin to initialize the project with. Available plugins: ("ansible.sdk.operatorframework.io/v1", "go.kubebuilder.io/v2", "helm.sdk.operatorframework.io/v1")
 $ cat PROJECT
domain: example.com
layout: go.kubebuilder.io/v2
projectName: memcached-operator
repo: github.com/example-inc/memcached-operator
version: 3-alpha
plugins:
  go.sdk.operatorframework.io/v2-alpha: {}

Concerns

It is scaffolding  go.operator-sdk.io/v2-alpha: {} or  go.sdk.operatorframework.io/v2-alpha: instead of "go.kubebuilder.io/v2"
master and 0.19.2 are with diff plugins versions for GO
Ansible and Helm plugins are with the domain sdk.operatorframework.io when just go is showing as go.kubebuilder.io

Any reason we aren't in the v1 version for this given we're going for v1.0.0 and there's no previous version of this plugin?

@joelanford I updated this one.

Hi @joelanford,
I  updated this one with all my thought and checks.  Feel free to re-check. Regards
Any reason we aren't in the v1 version for this given we're going for v1.0.0 and there's no previous version of this plugin?
I think we could use v1 as well to align it with 1.0 release. But for the other side, the advantage of using v2 would be follow up the kb plugins versions in order to make more intuitive that the sdk plugin version X is based on the upstream plugin version X as well.

the advantage of using v2 would be follow up the kb plugins versions in order to make more intuitive that the sdk plugin version X is based on the upstream plugin version X as well.

Agreed, but I'm not sure there will always be a need for us to update our plugin version when KB updates the base Go plugin.
Right now our plugin:

Adds some extra lines to the Makefile
Adds a kustomization.yaml file to config/samples

Unless something drastically changes between versions of KB plugins, these things should continue to work.

Why we should the plugin as "go.kubebuilder.io/v2" when actually we are scaffolding the sdk one? PS.: IMO it is not 100% the kb one since we perform customizations for OLM and Scorecard on top.

We're trying to be forward compatible with eventual phase 2 plugins. What we're doing right now for go is effectively the same as calling init --plugins=go.kubebuilder.io/v2,go.sdk.operatorframework.io/v2-alpha, where the KB plugin is the base plugin (what shows up in the layout) and our extras are a "phase 2" plugin that show up in the plugins section.
We're effectively just reserving the name AND putting something in the plugins section to show that we've made some changes in the scaffolded project on top of what's provided by the KB plugin.

Hi @joelanford,
So, following what in POV needs to be addressed here:

[ ] Decide if we will keep go.sdk.operatorframework.io/v2-alpha. Should it be alpha?
[ ] PR against 0.19 in order to ensure that projects generated with will scaffold PROJECT files with the same plugin name E.ggo.sdk.operatorframework.io/v2-alpha

We're keeping this as is for operator-sdk v1.0. v2-alpha gives us flexibility to make breaking changes before releasing a v2 version of the plugin (at that point, we would deprecate v2-alpha for the duration of SDK v1, and then remove it in SDK v2)


set temp dir

@Samuelopez-ansys I thought so but in Design.py we already have the property temporary_directory (to get the temp dir path) so I thought to put it here too :)


Option to skip downloading and merging audio for files that already have audio in them

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running youtube-dl version 2019.11.28
[x] I've searched the bugtracker for similar feature requests including closed ones

Description

Say I want to download all videos from a YouTube channel that have a format code 22 or less.
I use a command like this:
youtube-dl -i -f 22/135+140 -o "i:/Downloads/%(uploader)s%(title)s.%(ext)s" https://www.youtube.com/user/booksofscience/videos
Problem is, when it finds a video with the format code 22 which is a single 720p file with audio already in it, it still downloads a separate .m4a audio file and than merges it with the corresponding video file. This is redundant and there should be an option to skip it. It should ONLY download audio for files that are video only, such as the ones with the format code 135.

-f 22/135+140 will not download separate m4a audio is 22 is available.


Separate devices for  "battery" and "voltage"

Some of my sensors have "battery" and "voltage" e.g.
"battery":100,"voltage":3045
I guess that "battery" is a percentage.

Yes, battery is percentage and it is displayed in battery column on Devices page (see screenshot)

Additionally plugin creates own device for voltage data to be able to have log.

Thanks for the info!
Is this new behaviour?
My version of the plugin doesn't do it.

I'd say this functionality is available for pretty long period of time.


How to filter using DateTime?

No docs! Where is docs?
Why the following not working?
query {
    auditLogs(type: 3) {
        oldValues newValues type affectedTableName affectedRecordKey
        time
    }
}

Also how to paging? sorting? if not implemented using client side graphql, this lib wasted our time 2 weeks

This library doesn't solve everything for you. If you see no value in it, move on.
There are no fancy docs, the API is pretty small, the readme covers most of it. There is a tiny example of paging on a field in the readme also the demo has an example of paging more based on how others do it by adding a paging object
Which way suits you best is up to you and your application.
Regarding your error, I can't do anything with your query. Can you provide the error you are getting, what your schema looks like, anything that would actually help figure out what is going wrong?
As for the title of the issue, filtering is up to you to implement how it fits your application. Given a schema with a type MyRecord that has a Created field on it as a DateTime type you can replace the generated field with one with an argument (note the FromObject is just a helper).
var schema = SchemaBuilder.FromObject<MyDbContext>();
//...
// below we add a field with an argument, the argument defaults to null and is not required
schema.ReplaceField("myRecords", new { createdAfter = (DateTime?)null }, (db, args) => db.MyRecords.WhereWhen(r => r.Created >= args.createdAfter.Value, p.createdAfter.HasValue), "My description");

Now you can query
query All {
    myRecords { created ... }
}

query Filtered {
    myRecords(createdAfter: "2020-01-01") { created ... }
}

Closing as I have no information on the problem query. Reopen with more information if still an issue.


[Improvement] Idefics2 almost matching prompts

wip

may I ask why we don't use original instruction suffix and adjust it to be another one for idefics2 only? it seems like all other models share the same original instruction. thanks. cc @kennymckormick @VictorSanh

may I ask why we don't use original instruction suffix and adjust it to be another one for idefics2 only? it seems like all other models share the same original instruction. thanks. cc @kennymckormick @VictorSanh

Hi, @gyin94, it's OK for the original author to modify the implemented VLM and add custom prompt templates to align with the reported performance.


Command for querying balance in tokens of an address

Related to #828 and #825
$ zos balance $ADDR --erc20 $TOKENADDR/$TOKENNAME
> 100 ZEP

Resolved in https://github.com/zeppelinos/zos/pull/834.


ForgeModLoader crash [Server build]

ForgeModLoader 1.18.2-40.1.0
ServerSyncForgeLoader: 2.1.0
ClientSide:

I placed this mod in the mods folder.
GameLauncher crashed

ServerSide:

I placed this mod in the mods folder.
Server crashed

ServerLog:
debug.log
latest.log
serversync-SERVER.log
ClientLog:
latest.log
serversync-CLIENT.log

Looks like forge changed the mod loading rules again, will need an update to work on 1.18

I will most likely eventually get to updating this for 1.17-current, I have very little time at the moment to re-learn all the forge setup needed though, it is unfortunately not the simplest devkit to work with.

I am not sure.
But maybe this can help you.
Semantic - 2.0
Semantic Versioning Specification
And here is what most people use to setup multiversions and more.
pahimar
Equivalent-Exchange-3
I hope this can help you, to build a automation.

Have you got read the latest comment?

I've made it for 1.18.2: #11
I hope this is fine and runs stable

ok. I'll testing it at the weekend. Maybe you can do it for 1.19 too.
Have you got paypal?

I don't think any further changes to the code are necessary for this, but unfortunately I can't test this myself for 1.19 at the moment. I first created a pre-release in my fork so you can test it.
https://github.com/Ramb0N05/serversync-forge-loader/releases/tag/1.19.2-3.0.0-dev

ERROR by 1.19.2-3.0.0-dev
[11:25:19] [Server thread/ERROR] [se.fo.lo.ServerSyncLoader/]: Failed to find ServerSync, have you added it to your minecraft folder?
Maybe I didn't understand, how to install this mod.
I putted the mod into the mods folder. Right?
But I don't know, why I must install the ServerSync mod, too.

I think you can do it simplier.

An server and client side mod in the mods folder will syncronized by login to any server.
The mod is creating a server mod folder e.g. - .minecraft/mods/server_name
saving the server mod list in the config file eg. - .minecraft/config/serversync_forge_loader.toml
an client side massage "Please restart your launcher to enable all updates"

Or I didn't understand how to install you plugin.

The forge loader is only a loader for serversync via forge, you need serversync as that is the actual software that does anything.

ok


FEATURE - Delete Space

The owners(admins) of the spaces shall have the ability to delete the space.

Delete Space functionality has been added. #115


Does it work for 1.9 to 1.19?

Does this library work for all versions from 1.8 to 1.19? And is there support on Discord or some forum or something? Thx

Yesm, it should work on all those versions.
You can join the Discord through https://mattstudios.me/discord ;p


Add examples for other IPLD formats

Figuring this out feels like a subtask of https://github.com/ipfs-shipyard/ipld-explorer/issues/55 – cc @jessicaschilling

Right now only three formats are demoed at https://explore.ipld.io (and in ipfs-webui):
ipld-dag-pb (unixfvs1), ipld-git and ipld-ethereum:

The app itself imports more codecs, most of them remain unused, which also makes it harder to detect any regressions:
https://github.com/ipfs-shipyard/ipld-explorer/blob/56de6933669fb7e1dd7422616f265c3392ee9a24/src/bundles/index.js#L10-L16
@mikeal @vmx would appreciate your thoughts on:

Would it be beneficial to IPLD project if https://explore.ipld.io provided more examples?

Do you have good/preferred examples of CID for each format?

What is the canonical term for IPLD formats?
(I've seen people mentioning "IPLD format", "codec", "multicodec"  and even "block type", clarifying this in IPLD Explorer would make it easier for folks to use a single term)

+1 to this. Looking forward to hearing from @mikeal and @vmx 😊

@rvagg if we can pin the bitcoin dataset we should include it here as well, and zcash and eth once they are imported.

What is the canonical term for IPLD formats?

The terminology we solidified about a year ago is “codec.” We only use “format” when talking about the internal format of a codec.

The terminology we solidified about a year ago is “codec.”

I was asked a similar thing recently and answered: "I haven't used the word 'format' for for a long time". Which is a sign that we indeed use "codec" these days.

We could build a bitcoin block explorer with this, but we'd need to pin some blocks in IPFS to make it usable. Probably shouldn't pin the entire blockchain because we're talking about many millions of IPLD blocks but we can have a selection for example purposes. (Although, if we did a good enough job and made a decent block explorer that people wanted to use we could store them locally and load them outside of IPFS, but maybe that's another user story to consider later).
How would we go about pinning a set of blocks (I have them in CAR files and can add them somewhere), is that managed here?
Also ... @mikeal, the new BTC work depends on the new multiformats work, which is not what's being used here, so it might be a bit of a rabbit hole to try and integrate it, no?

I propose we focus on things that are actually useful to people, namely adding examples for  raw and dag-cbor.
raw is easy (echo -n "hello" | ipfs add --cid-version) but unsure what would  be a good example for dag-cbor – any prior art? If not, I can create dag-cbor with fake NFT metadata  or something.


MULTI-GITTER PR: migration github-config-and-gitignore-changes

Summary by Sourcery
Revise contribution guidelines and issue templates to improve clarity and process efficiency. Update CI workflows to enhance testing and deployment processes, including a new demo deployment workflow.
CI:

Modify the testPublish.yml workflow to ensure it triggers on push or pull request events for the main and beta branches, and adjust the node-version matrix.

Deployment:

Introduce a new workflow publishDemo.yml to deploy demos on pull requests to the main branch.

Documentation:

Update the CONTRIBUTING.md to include more detailed guidelines for submitting issues and pull requests, emphasizing the importance of consulting with the Auro team before starting work on a pull request.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement TV event longSelect for Android (#232)

Summary
Implement the longSelect TV remote control event for Android TV (this already exists on Apple TV).
Test Plan
Tested with the RNTester TVEventHandler example.

How do you use longSelect? I have it this way but it doesn't work.
        <Pressable
          onFocus={() => {} }
          onBlur={() =>{} }
          style={{
            padding: 15
          }}
          onLongSelect = {() => {
            alert("funciona");
          }} ....


rm: add function and tests

This adds onyo rm as a subcommand (rm.py, and modifications in
main.py and init.py), and adds onyo rm to the tests.
close #73

LGTM!


Suggestion: Rename repo

optimint is misleading as it sounds it only supports optimistic rollups
Suggestions:

mint-roll or mintroll
rollmint
Makisu (it makes the rolls; suggested by @tzdybal and my favourite so far)

Or rollmint

I have no preferences, and the name won't be very visible (there's no binary).
Total brainstorm (random order):

celestia-roller
roller
pulley
librollup
celestia-rolling-kit
celestia-rollup-kit


Refactor update_model() API to be more flexible

Refactor update_model() API to be more flexible
See The last part of https://github.com/lastmile-ai/aiconfig/issues/503
This greatly makes the update_model() API way more flexible. Instead of needing to set the entire ModelSettings (which can be annoying because you have to first retrieve the settings from the prompt to even set the modelMetadata to pass into your argument), you can now do each part individually:

Set both the model name and model settings: update_model(name="my_name", settings="my_settings") --> pass in prompt_name arg to update at prompt-level, do not pass to update at AI-Config level
Set the model name only: update_model(name="my_name") --> pass in prompt_name arg to update at prompt-level, do not pass to update at AI-Config level
Set model settings only: update_model(settings="my_settings", prompt_name="my_prompt") --> must pass in prompt_name otherwise this will error since AI-Config can have multiple models so we don't know which model to update

Imo, this is much cleaner and makes working with everything a lot easier, preserving the existing settings/name for model metadata if it already exists!

test plan
Updated and ran the automated tests


Bump external-snapshotter to 6.2.2

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

Did the go version change? If not, I’ll lgtm

@kschumy no change in the golang version


FRQ 1 - APCalendar

Backend

APCalendar.java
CalendarApiController.java
Year.java

Postman Testing
isleapYear Testing

firstDayOfYear

dayOfYear

numberOfLeapYears

dayOfWeek

Testing w/ CURL

Testing w/ Browser

2.7


Migration to landscape2

Issue to track some tasks related to the migration to landscape2:

[ ] Merge #3679.
[ ] Stop landscape1 periodic jobs that commit to this repo (i.e. automated Crunchbase update by CNCF bot).
[ ] Netlify GitHub app is no longer needed in this repository.

(please feel free to add more as needed, this is a work in progress)
We need to coordinate these tasks with the switch to landscape2.
/cc @caniszczyk @AndreyKozlov1984

Let me cancel all periodic updates here for a landscape1 08.01.2024, 14:44, "Sergio Castaño Arteaga" @.>: Issue to track some tasks related to the migration to landscape2:Merge #3679.Stop landscape1 periodic jobs that commit to this repo (i.e. automated Crunchbase update by CNCF bot).Netlify GitHub app is no longer needed in this repository.(please feel free to add more as needed, this is a work in progress)We need to coordinate these tasks with the switch to landscape2./cc @caniszczyk @AndreyKozlov1984—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>


Laravel + Redis, putting a integer number to cache is not working as well.

Laravel Version: 5.7, 5.8
PHP Version: 7.1.32
Database Driver & Version: Redis version 3.2.12 and predis version p1.1.1

Description:
If I put a value to cache like this:
Cache::put($cacheKey, 1, now()->addSeconds(30));
The value return by Cache::get($cacheKey) is null (the value in the redis is nil)
If I change
Cache::put($cacheKey, '1', now()->addSeconds(30));
It works fine.
For the same key, if I put the string value first, and then put the integer. It's Ok. crazy
Steps To Reproduce:

For the new key, put a integer by
Cache::put($cacheKey, 1, now()->addSeconds(30));
Get the value by Cache::get($cacheKey), you may see the result is null.

Can you try upgrading to Laravel 6.0 and see if the problem continues?

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We'll help you out and re-open this issue if so.
Thanks!


Revert "Define Cython language_level explicitly. (#394)"

Description

Current builds of RAPIDS are not compatible with this language level setting yet.
Checklist

[x] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.
[ ] The cmake-format.json is up to date with these changes.
[ ] I have added new files under rapids-cmake/

[ ] I have added include guards (include_guard(GLOBAL))
[ ] I have added the associated docs/ rst file and update the api.rst

I suspect that setting a value of 3 will also work, but I would want to test that locally on a few repos before pushing a change like this during code freeze.

I suspect that setting a value of 3 will also work, but I would want to test that locally on a few repos before pushing a change like this during code freeze.

This and the original PR target 23.06 so we shouldn't need to worry about code freeze.

Ah yes of course, you are right. I am experimenting with the new setting locally and should at least be able to validate a few repos today. That said, I would still advocate reverting the change for now and then making the fix in a subsequent PR because the current state of rapids-cmake blocks development of other repos on 23.06. Once I have the time to do enough local builds I can make a follow-up, I just don't know that I can promise that today.

Thanks @vyasr for picking this up. We should use 3str and not 3, but only because 3str is the default language level in Cython and we have no reason to differ from the default. This setting is only meant to squash warnings about the fact that the default value has changed in Cython 3 (the warnings go away when setting it manually).

Thanks @vyasr for picking this up. We should use 3str and not 3, but only because 3str is the default language level in Cython and we have no reason to differ from the default. This setting is only meant to squash warnings about the fact that the default value has changed in Cython 3 (the warnings go away when setting it manually).

Is there any reason not to try switching to 3? We shouldn't be relying on Python 2 string semantics in any way.

Based on the Cython documentation 3str and 3 should be identical when running on Python 3 instead of Python 2. I suspect that the current issue is a Cython bug in 0.29.x that is fixed in Cython 3.

/merge

I figured out why this was causing issues. We are in fact already using 3, not 3str, because that is the scikit-build default. Since that's being provided on the command line, it's overriding the Cython default. The cudf builds failed because as I mentioned before we are already doing things that are incompatible with Python 2 strings, namely using object types inside nogil blocks where they must be contextually convertible to C/C++ types. The lack of consistency in string types in Python 2 makes code like this invalid with Python 2 strings.
Cython defaults to 3str, I assume, because strings are the single largest change from Python 2 to Python 3, and they didn't want to break backward compatibility that extensively because Cython is so widely used. We should be comfortable moving to 3.


How to pass command line arguments to the built app?

I can't seem to find how to pass command line arguments to the built app?
Is there a way to do this?

Use bash. http://melpon.org/wandbox/permlink/CF9mxfWYH4yHxQe6
Alternatively, if you are using API, you can specify runtime-option-raw.

Actually I was wondering how to do it on the web site.

To avoid complex UI, Wandbox on the web is hiding the textbox.

Can't a single line editbox be added just above the stdin edit box?
I wanted to live demonstrate a command line parsing library but I cannot do this without having the option to pass such arguments!

Implemented.
However, runtime arguments is rarely used.
So it is hard to see.

I see it now!
But ut seems that all the params are passed in as a single argument:

The arguments are spited by line break. http://melpon.org/wandbox/permlink/D28bAnVd9rnU5ES2
(It is design error, but can not change for compatibility)

I am not an expert, but looking at the commit, it seems that the underlying code requires the line break - that you should not change.
However, you could make the UI have only a single like edit-box and use JS to split on spaces and construct the line-break representation desired by the command processor.
This would also take case of arguments with leading and trailing spaces which cannot happen in real command lines since the shell strips these as well.

It is not impossible, but...

Old permanent-link arguments will be invalidated, so rewrite their saved data.
Wandbox has JSON API. So I should implement splitting command line arguments on C++.
Splitting command line arguments such as a shell is difficult. (Quote a string includes spaces, tabs and line-break, escaping characters, processing punctuation characters ();<>|& and a comment character #, and more...)

How many old links are there? Didn't you just add this feature in the last commit?
well... maybe just the web interface is a first step?
True. I didn't mean a full-fledged shell parse. Just split on spaces (and trim them)

All permanent-links are alive, 20,000 over. I didn't commit this feature. see below.
I can.
I need to include spaces in an argument, so I want to implement quote. but It needs a many time.

About the 1,
Compile-time and Run-time arguments is saved to Wandbox database (using SQLite).
The arguments is string that is input on UI and including line-break on now implementation.
On the new UI, The arguments form will be changed to not include line-break and split on spaces.
On the new UI, Wandbox should process old form arguments and new form arguments.
It needs a many time, so I thought I convert old form arguments to new form arguments in advance. (that is, rewrite their saved data)

I see. Well, I hope you do get around to doing this when you have the time.
Thanks for the great site!


Postgresql driver download failed

Im using the DBeaver community edition 7.1.4
At first open I was prompted to download psql driver which failed.
Any thing else I need to setup?

I cannot reproduce it. Which OS do you use?

ubuntu 18.04.1 LTS
Btw, I resolved it by manually downloading the jar file and added it from Driver manager.
I was just curious about the Maven error

Hi,
Same error here on windows 10 with a fresh install.


MTP-1537: remove dependencies already in mtp-common

Bump mtp-common to ~11.0.1~ 11.1.0 and remove the dependencies already
requested there.
This is to reduce duplication and the risk of packages versions conflicts.
Ticket: https://dsdmoj.atlassian.net/browse/MTP-1537

Thanks @ushkarev for this review and the one on the bank-admin ☺ !


Make text size consistent in the app engine application creation dialog

Fixes #1664

@etanshaul
Are the text now the same size? I can't tell anymore lol

I think so! definitely looks better than before

@nbashirbello could update this? Last I remember that the fix wasn't consistent across platforms right? If its not the correct fix then we can close the PR.

I think so, but I'll verify and update PR.

Fix on linux machine:

Works well on linux without fix.

Text variation only occurs on mac and this fix isn't top-notch.


Implement Authentication as an GitHub App

Implement the authentication as an App to the GitHubAppBase. This should generate the JWT to perform REST API calls.

Use the package GitHubApps to implement authentication as a GitHub App or a GitHub Installation.


Height of the slots on the ribs doesn't change with modified material thickness

When changing the material thickness, the slots on the sides get narrower, but the slots on the ribs are not adapted to the new thickness:

Seems to be a refresh-issues. Reloading the page using f5 updates the height

Thanks @and-hus ! I seem to have introduced this when I introduced properties for holeWidth and holeHeight to reduce the amount of magic numbers in the design. Unfortunately, these properties currently are only set once in Bar's construtor and then never update. PR welcome! :) I can also fix this as part of the PR I'm preparing for issue #4


put concurrency_set() back

2.x is missing a stub for concurrency_set.
See https://github.com/jcupitt/ruby-vips/issues/88#issuecomment-336020741

Add something for vector_set as well.
See https://github.com/jcupitt/ruby-vips/issues/142

OK, in 2.0.8. Thanks for pointing out this dumbness!


Linebreak for json_to_sheet

Hi! I'm trying to perform a linebreak in some cells for an specific column, I'm not sure if this is supported by the community edition, so I'm asking if it is or it is only for Premium versions.
Thanks!

By default Excel renders newline characters as a space.  The option to force a newline to be rendered as a separate line is controlled by "Wrap Text" option, which is a style on the cells and is covered in our Pro builds

@IsaacEB1 @SheetJSDev
Can you please add line of code to implement this
I am trying for long time
kindly help


AddToGroupAsync throws a TimeoutException exception when MapHub is called twice for the same hub

Describe the bug
Groups.AddToGroupAsync() throws a TimeoutException approximately half the time when MapHub is called twice for the same hub. This issue is caused by changes introduced in #1779. It can be reproduced with Microsoft.Azure.SignalR version 1.21.3 or later works fine with version 1.21.2.
I'm unsure if calling MapHub twice for the same hub is allowed. If it isn't, this behavior should be documented.
To Reproduce
Update the ChatRoom sample project as follows:
Program.cs
app.MapHub<ChatSampleHub>("chat");
app.MapHub<ChatSampleHub>("chat/v2");

ChatSampleHub.OnConnectedAsync
await Groups.AddToGroupAsync(Context.ConnectionId, $"{Guid.NewGuid()}");
Exceptions (if any)
fail: Microsoft.AspNetCore.SignalR.HubConnectionHandler[1]
Error when dispatching 'OnConnectedAsync' on hub.
System.TimeoutException: Ack-able message Microsoft.Azure.SignalR.Protocol.JoinGroupWithAckMessage(ackId: 1) timed out.
at Microsoft.Azure.SignalR.AckHandler.HandleAckStatus(IAckableMessage message, AckStatus status)
at Microsoft.Azure.SignalR.ServiceConnectionContainerBase.WriteAckableMessageAsync(ServiceMessage serviceMessage, CancellationToken cancellationToken)
at Microsoft.Azure.SignalR.MultiEndpointMessageWriter.<>c__DisplayClass10_0.<b__0>d.MoveNext()
Further technical details

Your Azure SignalR SDK version - 1.21.3
.NET Version: 8

### Tasks

Thanks for reporting the issue, yes I can consistently repro the issue, please allow me to take a further look.

To double confirm, the behavior, as the same as self-host SignalR, is that although they map to different endpoints chat and chat/v2, these clients are actually sharing the same Hub, a sendToAll message send to all these clients despite they connect to different endpoint.
Curious about the usage, is it for rolling update the client logic?

In our project, we used something like chat/v1 and chat/v1.0 to follow different conventions for clients. We faced issues after updating from version 1.21.2 to the latest one and spent a lot of time figuring out what was wrong. Right now, we definitely don't need to register the hub for two URLs. We removed it and are happy with the update, but I believe it would be nice to fix or document this limitation, as someone else might face the same issue in the future.

Thanks for sharing Sasha, the next release will fix the issue.


Stale check no longer works on generated items

The stale check seems to be failing on items I create in the Rules file since I upgraded to nanoc 4.1.
I removed my output dir, did a clean build, and immediately after nanoc check stale fails:
output/blog/page10/index.html:
    [ ERROR ] stale - file without matching item

This item is created with @items.create in the preprocess step.

Can you try reproducing the problem with the release-4.1.x branch? I believe this issue is fixed and will be part of 4.1.1.

The check seems fixed in the release-4.1.x branch. However, my site no longer compiles with that one. Not sure if it's my fault, or whether I should file another issue:
Nanoc::Int::ItemRepRouter::IdenticalRoutesError: The item representations <Nanoc::Int::ItemRep name="default" binary=false raw_path="output/index.html" item.identifier="/index.html"> and <Nanoc::Int::ItemRep name="default" binary=false raw_path="" item.identifier="/index.html"> are both routed to /index.html.

It seems the preprocess block is run twice, and I add that item in the preprocess block.

I created #787 for this!


Neccessary whitespace in @supports removed

Why is issue #52  closed?
Minification and Optimization removes neccessary whitespace after or.
// CSS
@supports ((position: -webkit-sticky) or (position: sticky)) {
	.element {
		position : -webkit-sticky
		position : sticky;
	}
}

// Result
@supports((position:-webkit-sticky) or(position:sticky)){.element{position:-webkit-sticky;position:sticky}}

Without this whitespace, the @support rule is broken and is not interpreted by the browser.
Best Regards

Same for media queries.
Example with this :
@media only screen and (min-width:768px) {
Become like that after uglify :
@media only screen and(min-width:768px){

Any progress on this issue? Is there any known work around available ?

This issue happens when defining a media-query inside an id block.
this:
@media screen and (min-width: $size) {
  #id {
    ...
  }
}

becomes:
@media screen and (min-width: $size){#id {...}}

where {# corresponds to a comment token on some CRM tools such as Hubspot.


Padding layout

pls padding of layout content deleted because i want to following align top and bottom of other content

I've remove the padding. Please check and confirm. I'll close this issue then ;)

mantap


raise an error samgraph/commonn/cpu/cpu_device.cc:39 Check failed: e == cudaSuccess || e == cudaErrorCudartUnloading CUDA: os call failed or operation not supported on this OS when running /gnn_lab/example/samgraph/train_gcn.pyon papers100M dataset

Hey, I got an error samgraph/commonn/cpu/cpu_device.cc:39 Check failed: e == cudaSuccess || e == cudaErrorCudartUnloading CUDA: os call failed or operation not supported on this OS when running /gnn_lab/example/samgraph/train_gcn.pyon papers100M dataset, however, this python script runs successfully on other datasets such as ognb_products and reddit. How can I fix it? Looking forward to your help. Thanks!

I fix this bug when decreasing the cache_percentage from 0.21 to 0.001. However I am curious on how to realize the cache ratio of 0.21 reported in your paper? Increasing the pin-memory limit or others?

Can you provide more information about your setup? E.g., the number of GPUs, GPU memory, batch size, the script and parameters you use, how you generate the dataset.

Yeah, I use 2 3090 GPUs with 24GB device memory, 1 for sample and 1 for train, the training batch size is 8000,  hidden dim is 64 and I generate the dataset as the code(gnn_lab/utility/data-process/dataset/papers100M.ipynb) you provided. The script I run is /gnn_lab/example/samgraph/train_gcn.py.

Then 24GB memory should be enough for 21% cache rate, since the entire feature is around 55GB. We need more information to indentify the root cause, e.g., the call stack when the error raises. You may sleep several seconds right after the trainer process launches, print pid, and attach GDB to it.

Thanks! I will try to print the more detailed information.


Fix dependencies submodule initialization

Until now, the submodules of dependencies are fetched at the clone time, and are nor updated after changing branch to the required version. This lead to wrong versions of submodules being used and cause issues.
Fix:
Initialize submodules after changing branch to use submodules version of the required branch.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This repository is no longer maintained as Kong is now built by Bazel: https://github.com/Kong/kong/tree/master/build


Build problem

Hi, your latest modification are missing a correct RISE-V2G-Shared version number update in PARENT, EVCC and SECC: actual Shared version is 1.2.5, but in the latter still reference 1.2.4, so it does not compile.
As a suggestion maybe you can modify Shared reference version number with:
<project.version>${project.version}</project.version>
Regards.

Hi @FabioTerrile, thanks for the hint. I updated the latest release. Could you please try again and let me know whether you still have build problems or the issue is now resolved?

Resolved!
Thank you!


Synthesize and prioritize user feedback

Aubrey and Tracey will meet and synthesize the research. From this, we hope to get a priority list for feature requests and areas that need further design exploration.

Sythesis: https://ibm.box.com/s/q0gcjfipgdwv1trzz5zpl1baxzirp8iy
Issue list draft: https://ibm.box.com/s/bo2t4po3cu3hoie0o5435saycyh1m8qw


cca.users.count is zero even after logging in.

This problem happens sometimes but not all the time. My organization has AD FS. I run F5, successfully login and stop debugging from VS. Sometimes even after successful login, cca.Users count in readmail shows zero. After logging out and logging in, the problem disappears. Is the problem due to having AD FS? It's been driving me crazy for a couple of months and any insight will be helpful. I have tried virtually all samples using openidconnect and they all have the same issue.

It's the same for me, except I don't have AD FS, but I use Azure AD. I created a forum discussion on my issue.

you probably want to have a look at this sample: https://github.com/Azure-Samples/active-directory-dotnet-webapp-openidconnect-aspnetcore


Host our own NuGet feed for packages that we need that aren't elsewhere yet

We think its gross to keep giant binary blobs in our dependencies folder for nuget packages that aren't hosted properly yet.
So we get an Azure Blob Storage account and put it there using Sleet.
This removes the package in the repo and makes NuGet get it off of our feed instead.

Closes #1951


completely change lcz tif file check

Overall function that tests the LCZ integrity, including:

check LCZ classes, change if needed (see issues)
check projection system, change if needed (see issues)
check extent (using rxr this time)

Result is new lcz_clean.tif file, that is saved to folder.
This is then used throughout script, and removed when ready.

Ok, I have tested these changes against the original Shanghai data files, and all seems to work.
The changes:

convert LCZ labels 101-107 to 11-17, if they exist (see #36 )
checks the projection. Re-projected to EPSG: 4326 if needed (see #37 )

were added to the lcz extent check, and all integrated into one routine.
Tests were added to make sure the behaviour is as expected.
Please have a look @theendlessriver13, and you can merge if all is fine.

I got a nodata warning when testing on our sample_data. This is fixed now ...


Updation in CONTRIBUTING.md file. Addition of some rules before raising issue to avoid duplicates issue.

In current CONTRIBUTING.md, their are steps on how a person can make an open source contribution, but people are not checking current running issues and are not reading code bases, which is why there are multiple duplicate issues raised. I am emphasizing points such as checking existing issues to avoid duplicates and reading the base documentation before raising new issues. And  work on only assigned issues.
Contributing to [Project Name]
First off, thanks for taking the time to contribute! 🎉
The following is a set of guidelines for contributing to [Project Name]. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Reporting Issues
Before You Submit an Issue

Check the existing issues to see if your issue has already been reported. Duplicate issues clutter the issue tracker and make it harder for us to prioritize issues.
Search through open and closed issues to see if your issue has already been addressed.
Review the project documentation to ensure your issue hasn't already been covered.

How to Submit an Issue

Use a clear and descriptive title for the issue to identify the problem.
Describe the exact steps to reproduce the problem. Include code snippets or links to a repository, if applicable.
Explain the expected behavior and what actually happens.
Include any relevant logs or screenshots that can help us understand and reproduce the issue.
Mention the version of the software you're using and the environment (e.g., operating system, browser) where the issue occurs.

Pull Requests
Before You Submit a Pull Request

Ensure that your changes are aligned with the project's goals and codebase.
Write clear and concise commit messages.
Test your changes thoroughly.
Update the documentation if your changes require it.
Ensure there are no merge conflicts with the base branch.

In current CONTRIBUTING.md, their are steps on how a person can make an open source contribution, but people are not checking current running issues and are not reading code bases, which is why there are multiple duplicate issues raised. I am emphasizing points such as checking existing issues to avoid duplicates and reading the base documentation before raising new issues. And work on only assigned issues.
Contributing to [Project Name]
First off, thanks for taking the time to contribute! 🎉
The following is a set of guidelines for contributing to [Project Name]. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Reporting Issues
Before You Submit an Issue

Check the existing issues to see if your issue has already been reported. Duplicate issues clutter the issue tracker and make it harder for us to prioritize issues.
Search through open and closed issues to see if your issue has already been addressed.
Review the project documentation to ensure your issue hasn't already been covered.

How to Submit an Issue

Use a clear and descriptive title for the issue to identify the problem.
Describe the exact steps to reproduce the problem. Include code snippets or links to a repository, if applicable.
Explain the expected behavior and what actually happens.
Include any relevant logs or screenshots that can help us understand and reproduce the issue.
Mention the version of the software you're using and the environment (e.g., operating system, browser) where the issue occurs.

Pull Requests
Before You Submit a Pull Request

Ensure that your changes are aligned with the project's goals and codebase.
Write clear and concise commit messages.
Test your changes thoroughly.
Update the documentation if your changes require it.
Ensure there are no merge conflicts with the base branch.

Hello @ArtiGaund , Go for it
All the Best


Add paper

Pull Request Test Coverage Report for Build 306

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

Totals

Change from base Build 301:
0.0%

Covered Lines:
2212

Relevant Lines:
2257

💛  - Coveralls


Can not render ReactPIXI component inside ReactRouter handler

I'm using ReactRouter with Flux and ReactPIXI.
I started by forking the following repo: https://github.com/jaketrent/demo-react-router-flux and I'm trying to display a stage/container inside a route-handler component (file: books/show.js in our case).
I get the following error message, even though the ReactPIXI component is valid:

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router.
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.


OCaml <=14.12 doesn't support glibc>=2.34

Operating System: Arch Linux
Revery Version: 0.32.0 (currently on master)
OCaml version: 14.12
Native, Bytecode, or JS build: no idea

I am trying to build revery on Arch Linux, but it fails when compiling OCaml. I found this comment on an OCaml repository's issue (https://github.com/ocaml/ocaml/issues/10250#issuecomment-785251413) that completely seems related to the problem. The glibc is at version 2.35 on my system, but OCaml <14.12 doesn't support glibc>=2.34. The wiki doesn't seem to mention that compatibility issue.

This should have been fixed in opam in https://github.com/ocaml/opam-repository/pull/19855 and for esy in
https://github.com/esy-ocaml/ocaml/pull/60, both back in January.
You can try removing the esy.lock directory and rebuilding, but otherwise the error description "fails when compiling OCaml" isn't very actionable.
The bigger problem seems to be that esy-sdl2 is broken (https://github.com/revery-ui/esy-sdl2/issues/21) and needs to be updated. But it's been forked in such a backwards way that I'm not sure how to go about doing so. It's been done before though (by @zbaylin) so should be possible.

There are also build problems with GCC 12, e.g. I get this on Fedora 37:
    interp.c: In function 'caml_interprete':
    interp.c:253:21: error: storing the address of local variable 'lbl_ACC0' in 'caml_instr_base' [-Werror=dangling-pointer=]
      253 |     caml_instr_base = Jumptbl_base;
          |                     ^
    interp.c:51:26: note: 'lbl_ACC0' declared here
       51 | #  define Instruct(name) lbl_##name
          |                          ^~~~
    interp.c:323:5: note: in expansion of macro 'Instruct'
      323 |     Instruct(ACC0):
          |     ^~~~~~~~
    In file included from interp.c:25:
    caml/fix_code.h:38:15: note: 'caml_instr_base' declared here
       38 | extern char * caml_instr_base;
          |               ^~~~~~~~~~~~~~~

Which got fixed here in 4.14.x: https://github.com/ocaml/ocaml/pull/11379/commits/f280aaa4845ae2381977264c37b5573959cea87e
Although FWIW I can install 'OCaml 4.12.1' from opam... is there a way to tell esy to use the OCaml compiler installed by OPAM or the system compiler?

https://github.com/revery-ui/revery/blob/141f70f69d6abd69674b46d805a783411b38cd79/package.json#L71
"ocaml" package version 4.12.x is hosted on this branch https://github.com/esy-ocaml/ocaml/tree/4.12.1+esy
You should open a PR (or I can) to this branch by cherry-picking the commit you cited.
After that you need to wait for someone to review and merge your PR and publish it.
In the meantime you can consume your own fork with esy resolution syntax.
You have an example just above
https://github.com/revery-ui/revery/blob/141f70f69d6abd69674b46d805a783411b38cd79/package.json#L68

Thanks for the hints (I wasn't familiar with how esy works, just opam).
I had to use resolutions to pin my fork (otherwise the solver failed thinking the version is not <4.13). Also for future reference the json here is quite picky: you can't have trailing , for example, and the part after # has to be a commit hash, it cannot be a branch or git describe output:
+  },
+  "resolutions" : {
+    "ocaml": "edwintorok/ocaml#c9af44073b"
   }

PR here https://github.com/esy-ocaml/ocaml/pull/64

FWIW revery itself still doesn't build, even with that 4.12.1 bugfix, but it gets further and fails here:
  (cd _build/default && /var/home/edwin/.esy/3_______________________________________________________________/i/ocaml-009b8de8/bin/ocamlc.opt -w -9 -g -bin-annot -I src/api/.ppx_deriving_api.objs/byte -I /var/home/edwin/.esy/3_______________________________________________________________/i/ocaml-009b8de8/lib/ocaml/compiler-libs -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ocaml_compiler_libs-opam__c__v0.12.4-b4b6b35f/lib/ocaml-compiler-libs/common -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ocaml_compiler_libs-opam__c__v0.12.4-b4b6b35f/lib/ocaml-compiler-libs/shadow -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ocaml_migrate_parsetree-opam__c__1.8.0-f7b9c475/lib/ocaml-migrate-parsetree -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ppx__derivers-opam__c__1.2.1-01696764/lib/ppx_derivers -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ppxlib-opam__c__0.15.0-13a3ac19/lib/ppxlib -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ppxlib-opam__c__0.15.0-13a3ac19/lib/ppxlib/ast -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ppxlib-opam__c__0.15.0-13a3ac19/lib/ppxlib/print_diff -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ppxlib-opam__c__0.15.0-13a3ac19/lib/ppxlib/stdppx -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__ppxlib-opam__c__0.15.0-13a3ac19/lib/ppxlib/traverse_builtins -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__result-opam__c__1.5-945f851c/lib/result -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__sexplib0-opam__c__v0.14.0-02514ae2/lib/sexplib0 -I /var/home/edwin/.esy/3_______________________________________________________________/i/opam__s__stdlib_shims-opam__c__0.3.0-b081998e/lib/stdlib-shims -intf-suffix .ml -no-alias-deps -o src/api/.ppx_deriving_api.objs/byte/ppx_deriving.cmo -c -impl src/api/ppx_deriving.pp.ml)
    File "ppx_deriving.cppo.ml", line 673, characters 28-74:
    Error: Unbound module Migrate_parsetree.OCaml_current.Ast.Ast_helper
    Hint: Did you mean Ast_mapper?

It looks like esy install has updated esy.lock/ quite significantly: 57 files changed, 761 insertions(+), 3114 deletions(-),  however esy build won't work without esy install (claims no lockfile)

The following change to package.json gets me a bit closer to being able to build it (the versions in package.json appeared to be too old to work with 4.12.1):
diff --git a/package.json b/package.json
index cae6b349..627ce5eb 100644
--- a/package.json
+++ b/package.json
@@ -37,15 +37,15 @@
   "dependencies": {
     "@opam/bos": "0.2.0",
     "@opam/ctypes": "0.15.1",
-    "@opam/dune": "^2.5.0",
+    "@opam/dune": ">=2.5.0 <4",
     "@opam/dune-configurator": "*",
     "@opam/reason": "^3.6.2",
     "@opam/lru": "bryphe/lru:lru.opam#2708c70",
     "@opam/lwt": "^5.0.0",
     "@opam/lwt_ppx": "^1.1.0",
     "@opam/markup": "0.8.2",
-    "@opam/ppx_deriving": "*",
-    "@opam/ppx_optcomp": "v0.14.0",
+    "@opam/ppx_deriving": "5.2.1",
+    "@opam/ppx_optcomp": ">=v0.14.0 <=v0.16.0",
     "@opam/omd": "ocaml/omd:omd.opam#1535e3c",
     "@opam/uucp": "*",
     "@opam/uutf": "*",
@@ -70,6 +70,9 @@
   "devDependencies": {
     "ocaml": "4.12.x",
     "esy-astyle": "zbaylin/esy-astyle#59bc21a",
-    "@opam/ocaml-lsp-server": "*"
+    "@opam/ocaml-lsp-server": "^1.9.0"
+  },

And then I get to the SDL2 build error you mentioned

The next error is a missing rapidjson repository, fixed in esy-skia master, so updating the package.json entry fixes that:
subprocess.CalledProcessError: Command '['git', 'clone', '--quiet', 'https://skia.googlesource.com/external/github.com/Tencent/rapidjson.git', 'third_party/externals/rapidjson']' returned non-zero exit status 128

"esy-skia": "revery-ui/esy-skia#29349b9279ed24a73ec41acd7082caea9bd8c04e",

Which then goes on a bit further, but fails to build here:
../../src/core/SkCubicClipper.cpp:83:9: error: variable 'iters' set but not used [-Werror,-Wunused-but-set-variable]
        int iters = 0;
            ^
    1 error generated.

Looks like there are too many things that need to be updated to get revery to build on Fedora36, but I hope that the above helps someone pick up where I left off.

Thanks for you works on this. I can merge PR to revery-ui so I will try to review esy-sdl2 PR this week.
For the error you showed you only need to remove the like at the specified location.

The following change to package.json gets me a bit closer to being able to build it (the versions in package.json appeared to be too old to work with 4.12.1, OTOH with ocaml-lsp-server we need to be careful to avoid pulling in the 5.0 version which 'opam' knows how to avoid, but 'esy' doesn't and I had to work that around by adding a ^1.9.0 in the devDependencies):
diff --git a/package.json b/package.json
index cae6b349..63eefd69 100644
--- a/package.json
+++ b/package.json
@@ -37,7 +37,7 @@
   "dependencies": {
     "@opam/bos": "0.2.0",
     "@opam/ctypes": "0.15.1",
-    "@opam/dune": "^2.5.0",
+    "@opam/dune": ">=2.5.0 <4",
     "@opam/dune-configurator": "*",
     "@opam/reason": "^3.6.2",
     "@opam/lru": "bryphe/lru:lru.opam#2708c70",
@@ -45,7 +45,7 @@
     "@opam/lwt_ppx": "^1.1.0",
     "@opam/markup": "0.8.2",
     "@opam/ppx_deriving": "*",
-    "@opam/ppx_optcomp": "v0.14.0",
+    "@opam/ppx_optcomp": ">=v0.14.0 <=v0.16.0",
     "@opam/omd": "ocaml/omd:omd.opam#1535e3c",
     "@opam/uucp": "*",
     "@opam/uutf": "*",
@@ -70,6 +70,9 @@
   "devDependencies": {
     "ocaml": "4.12.x",
     "esy-astyle": "zbaylin/esy-astyle#59bc21a",
-    "@opam/ocaml-lsp-server": "*"
+    "@opam/ocaml-lsp-server": "^1.9.0"
+  },

And then I get to the SDL2 build error you mentioned

The bound on dune should be correct before your modification 🤔 If you send a PR to revery that add upper bound you found I can merge this quickly (one file to review)
Also the issue you got with resolutions is on our end we wasn't strict enough on version.
If you show next error I can help you solving the issue.

I pushed what I have here: https://github.com/edwintorok/esy-skia/commits/master but as soon as I fix one error there are others, some of which have upstream commits to backport (and some do not because the code got deleted/changed substantially upstream):
../../src/core/SkLineClipper.cpp:169:43: error: argument 'pts' of type 'const SkPoint[]' with mismatched bound [-Werror,-Warray-parameter]
int SkLineClipper::ClipLine(const SkPoint pts[], const SkRect& clip, SkPoint lines[],
                                          ^
../../src/core/SkLineClipper.h:31:39: note: previously declared as 'const SkPoint[2]' here
    static int ClipLine(const SkPoint pts[2], const SkRect& clip,
                                      ^
../../src/core/SkLineClipper.cpp:169:78: error: argument 'lines' of type 'SkPoint[]' with mismatched bound [-Werror,-Warray-parameter]
int SkLineClipper::ClipLine(const SkPoint pts[], const SkRect& clip, SkPoint lines[],
                                                                             ^
../../src/core/SkLineClipper.h:32:33: note: previously declared as 'SkPoint[4]' here
                        SkPoint lines[kMaxPoints], bool canCullToTheRight);
                                ^
2 errors generated.
[486/1230] compile ../../src/core/SkMaskBlurFilter.cpp

I don't think it is worth continuing down this route: upstream must've fixed these build errors in newer versions, so updating to the latest upstream might be best (although that might imply updating some OCaml bindings for skia too?), however there are a lot of conflicts (are there some local changes to skia that were not upstream?)


Initial version for scoop support.

Added pathing for scoop directories, script will check for scoop install before
a normal Windows Store install.
I tested on two machines; one with the terminal installed using scoop, one with the Windows Store version.  Both seem to be working okay.
I'm new to Powershell so any feedback is appreciated.  Let me know how it works!

Just revised #19 .
Now I think that this repo should have a smaller scope to only cover Windows 10 store version of Windows Terminal. That's what I use personally.
Chocolatey or Scoop users should use different scripts, which can be derived from this repo but tested/maintained by others (like you).
I plan to close this pull request and instead forward Scoop users to your repo, if you like.

Okay great, that sounds good to me.  Thank you!


why not make the description the readme?

The description page @DragaDoncila made here is lovely.  why not just make it the readme?   There's nothing in there that isn't generally applicable to the plugin, and it would make for a much nicer presentation on github, pypi, etc...

I don't think there's any particular reason @tlambert03! 😊 I think back when she made it we couldn't have mp4s render in READMEs? 🤷

Also, this description page is not included anywhere in the main docs at https://jni.github.io/affinder/ I think it should be included there too.
If you actually do make the description be the readme, perhaps that takes care of that problem (since the README is copied into the docs website).

And can I just say how much I hate having napari-hub require a separate description file, instead of using the README. You inevitably end up with this type of problem, where one is better than the other and only some of the information is in certain places.
I've heard all the arguments about how they're supposed to be two different documents aimed at different audience, but it just never seems to actually work out better in practice.

Also, this description page is not included anywhere in the main docs at https://jni.github.io/affinder/ I think it should be included there too.

It is included under usage but the home page needs attention to make this obvious. I think I remember @jamesyan-git working on this and having to jump through a bunch of hoops to just include the DESCRIPTION.md doc rather than having to duplicate the information.
I'm actually +1 to just getting rid of the DESCRIPTION.md and making it the README. Like Genevieve says, the original argument that you'd maintain a separate description for the napari hub is maybe, nice, but I don't think it's nicer than having complete documentation on the docs website and on the repo. Keeping both in sync manually is a nightmare, so I think if the napari-hub wants to be able to display "subsets" of the information in the plugin's docs or README, there should be a mechanism to mark existing documentation as hub-relevant or something, rather than having to maintain a separate doc.

And can I just say how much I hate having napari-hub require a separate description file, instead of using the README.

The napari hub btw does use the README if one is available and no DESCRIPTION file is present.

And can I just say how much I hate having napari-hub require a separate description file, instead of using the README.

you could add your voice to the hub discussion over in their repo :joy:   more core devs saying this might actually make them budge a bit

And can I just say how much I hate having napari-hub require a separate description file, instead of using the README.

The napari hub btw does use the README if one is available and no DESCRIPTION file is present.

The napari hub linter tool (or preview tool? I don't know what you call it) absolutely complains at you if there is no description file present. It's absolutely considers my plugins "unfinished" for the napari hub in that respect.

And can I just say how much I hate having napari-hub require a separate description file, instead of using the README.

you could add your voice to the hub discussion over in their repo 😂 more core devs saying this might actually make them budge a bit: https://github.com/chanzuckerberg/napari-hub/discussions/627

Ok, done: https://github.com/chanzuckerberg/napari-hub/discussions/627#discussioncomment-5668469

The napari hub linter tool (or preview tool? I don't know what you call it) absolutely complains at you if there is no description file present. It's absolutely considers my plugins "unfinished" for the napari hub in that respect.

Perhaps. But a README is always used if available and there's no DESCRIPTION file. If you find that's not the case, that's a bug.

The napari hub linter tool (or preview tool? I don't know what you call it) absolutely complains at you if there is no description file present. It's absolutely considers my plugins "unfinished" for the napari hub in that respect.

Perhaps.

There's no perhaps about it, I'm telling you what the behaviour is.

But a README is always used if available and there's no DESCRIPTION file. If you find that's not the case, that's a bug.

Yes, I already know this happens. That's slightly off-topic from the point I made here though.


ISPN-14960 IRAC: use BitSet to track updates

https://issues.redhat.com/browse/ISPN-14960

CI crashed with unrelated stuff, I'll check that. Replaying it.

Integrated into main, thanks @pruivo!


refactor: faster

Summary
Make Interchaintest fast like zooooooooooooooomies.
NOTE: this requires PollForProposalStatus delta time to be increased to account for faster blocks (else proposals are still in vote period)
This PR is currently just slop, adding things as I find / can improve
Other

Also does a little logger touch up to fix a visual bug

Benchmarks
IBC 6 nodes + relayer
go clean -testcache && go test -timeout 3000s -run ^TestLearn$ github.com/strangelove-ventures/interchaintest/v8/examples/ibc -v
Time to beat:
 - Before this PR: 103.31s
 - With faster blocks (in this PR) & faster relayer polling: 70.39s / 67.03s
 - Without startup Locks: 60 / 62.8s
 - Misc caches (59 / 61s)

IBC-Go simd (v8.0.0) 1 val, build then exit
Performance checks for fast iteration with docker changes
go clean -testcache && go test -timeout 3000s -run ^TestSingleValBenchmark$ github.com/strangelove-ventures/interchaintest/v8/examples/cosmos -v
Time to beat:
- 11.74s (11.335517782s build)
- 10.45s (faster poll on Status to start)
- 10.14s / 10.02s (cached Exec container)
- 8.85s (cache isSDKv47 genesis call)
- 8.12s (key addressCache, doubles for getting mnemonics from keys created to the keyring directly with CreateKey)

Build (including relayer setup) takes 50s of the total 60s test time. If we can speed up the ic.Build we could get test down to an absolute best case of ~15s (down from 103s)

https://github.com/strangelove-ventures/interchaintest/issues/1153 is probably the next big performance improvement. Getting relayers to auto provision for planned testing is ideal, lot of dead time waiting.
We already know the chain configs to chains add, rly keys restore, and rly paths new (config). Then we just rly tx link as soon as the chain is at height capable.
Must allow relayers pre ic.Build() standalone

ideas from Andrew:

sleep inifinite then just exec into the container on start

export genesis state after IBC start, then can load back from that in future runs

I have been taking things from this PR and putting into others as it seems right.


[FEATURE REQUEST] Allow for custom Terraform scripts

Is your feature request related to a problem? Please describe.
Currently when Epicli is run it cleans out all *.tf Terraform template files. This restricts the ability of the user to add any kind of custom Terraform scripts to a deployment outside of what Epiphany generates.
Describe the solution you'd like
Only remove the Terraform templates from the build directory that are actually generated by Epiphany with the following regex:
'''[0-9][0-9][0-9]_*.tf'''
And document the steps for people to add custom Terraform templates to a deployed cluster.
Describe alternatives you've considered
None
Additional context
None

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

The ability to add custom terraform scripts has been tested. The functionality seems to be working fine. Created and removed additional resources in AWS and Azure with epicli.


Add auto-baseline main pipeline config for core

This should address the baseline PRs coming in for every pipeline

/azp run js - core


Refactor notification banners

Context
Refactor the way flash messages are rendered so it’s possible to provide both a heading and body content for the notification banner.
Changes proposed in this pull request
1. Restructure the flash hash
Change the structure of the hash so it more closely resembles the options accepted by the notification banner component.
This is passed through to the view where corresponding changes have been made to the way we read the flash variable now that it has different keys.
2. Update translation keys to differentiate ‘heading’ and ‘body’
The convention has been to use the translation key .success for the flash message content. These have now been renamed to ".success_heading".
Later, we’ll be able to use .success_body to define the body content for flash messages that need it.
3. Move rendering to a view partial
4. Tidy up: unnecessary flash rendering in the component preview layout
The component_preview.html.erb layout does not need to render flash messages so code has been removed.
Guidance to review

Related frontend changes for review are detailed in PR#1073.

Link to Trello card
https://trello.com/c/CunVgrTw/820-refactor-flash-messages-to-support-heading-and-body-content
Screenshots

See screenshot video on banner content changes (PR#1073).

I'm closing this PR as it has been combined into the overall way finding PR #1071.


Could not find method beforeSettings() for arguments [...] on build of type org.gradle.invocation.DefaultGradle.

Hi. I just tried adding this action to one of my action files to speed up the pipelines by caching all the downloaded dependencies.
Pretty unexpectedly I get the following error message when any gradle task is invoked.
FAILURE: Build failed with an exception.

* Where:
Initialization script '/home/runner/.gradle/init.gradle' line: 6

* What went wrong:
A problem occurred evaluating initialization script.
> Could not find method beforeSettings() for arguments [init_eiwz59vorj50r19wcr0ymhsxm$_run_closure1@415a204d] on build of type org.gradle.invocation.DefaultGradle.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3s
Error: A problem occurred evaluating initialization script.
> Could not find method beforeSettings() for arguments [init_eiwz59vorj50r19wcr0ymhsxm$_run_closure1@415a204d] on build of type org.gradle.invocation.DefaultGradle.

Full log: https://github.com/AuraDevelopmentTeam/InvSync/runs/1623878392?check_suite_focus=true

This is due to this line: https://github.com/burrunan/gradle-cache-action/blob/61348edb3ed90fd775bd9738ac6535163f5b8c4b/cache-proxy/src/main/kotlin/com/github/burrunan/gradle/proxy/CacheProxy.kt#L122
beforeSettings was only added in Gradle 6. Compare Javadoc 6.7.1 with Javadoc 5.6.4
beforeProject might be an appropriate alternative.

just curious: does this mean that gradle-cache-action requires a minimum gradle version?

just curious: does this mean that gradle-cache-action requires a minimum gradle version?

Appears like it.

Appears like it.

ok thank. unfortunately it looks like i'm stuck with an old version for now. this could be the straw that breaks my back to upgrade ;-)

ok thank. unfortunately it looks like i'm stuck with an old version for now. this could be the straw that breaks my back to upgrade ;-)

v1.8 (a61b505b54af16ffe2d1d1f2388b46516a8f0f32) should work with Gradle 5


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL: HTTPS://bitbytecoin.net
JustList Name: BBC
Link to the official homepage of the JustList manager:

Dear Sir,
List bitbytetoken in just swap

List Bit Byte Coin in just swap

Sorry, your issue will be closed as you did not submit your information in the correct format.