Remoting test

The PR shows and example of how we might run a remote test. It is based on the RemoteBenchmark example code.
PR adds:

Proto.Remote.Tests.Messages - .proto messages for the tests
Proto.Remote.Tests.Node - a console app that acts as a remote node
Proto.Remote.Tests - the xunit test project

The test works by launching the Proto.Remote.Tests.Node console app via System.Diagnostics.Process using "dotnet " and then sends a message and awaits a reply. This is used in an xunit fixture so shared amongst tests (note this might have to change if we add tests that start killing the remote process).
I've also added an xunit Trait (Category=Remote) so it can be run separately from the other unit tests as it is more of a system level test - probably best to have CI run unit tests followed by Remote tests
Tested xplatform on win10 and mac, but it would be good to have other people checkout and verify it works.
Requires Proto.Remote.Tests.Node to be built first (solution should do this)
What are people's thoughts on this way of testing Proto.Remote? Any better ideas?
@cpx86 - what tests need writing for remote?

This is brilliant! love it


feat(doc):update contributing docker command

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/riccardoperra/codeimage/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

Docs

What kind of change does this PR introduce?

I have setup the repo and I found an old version command of the docker compose, as defined here since January the v1 is not more supported.
I have checked for the listed command and I realized checking in package.json history that the current one is obsolete, so I updated it

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[X] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[X] No

Other information

Thanks 😊


Hot fix for finding exactMatch of degC

When trying to parse something like 10 °C, the parsed quantity value becomes 10 K. The preferred units force the temperature units into K. This removes that perferred unit logic, and checks if any units directly matched the targetted unit

This points out a real bug, but fixes it incorrectly.


get_coordinates(point) is 4x faster than (point.x, point.y)

At this moment, this is not a bug report nor a feature request. I primarily want to highlight the fact that get_coordinates(point) is approximately 4x faster than using point.x, point.y.
I believe this matters substantially as the point.x, point.y pattern is very popular for retrieving Python float numbers for a given point. It is also quite often present in hot loops.
A search on GitHub for 'shapely ("point.x, point.y" OR "p.x, p.y")' returns 1.5k code results, many of which are inside of for loops.
Benchmark
Python 3.12.1
shapely 2.0.3

python -m timeit -s "from shapely import Point" -s "a = Point(12,34)" "a.x, a.y"
# 20000 loops, best of 5: 11.3 usec per loop

python -m timeit -s "from shapely import Point, get_coordinates" -s "a = Point(12,34)" "get_coordinates(a)[0]"
# 100000 loops, best of 5: 2.98 usec per loop

Yeah this has been on my mind for a while. We use shapely a lot for work, and when we do our optimization passes, we always go through and just do x = point.x and then use x whenever we need the value. I wasn't aware of get_coordinates()
I do struggle to understand why a calculation needs to be done at all for x and y and why they aren't just stored. Perhaps i'm missing something basic, but operations aren't done in place that I can think of, so I don't fully get why you would need a calculation - but I also haven't dove into the GEOS library to see.
It definitely should at the very least be a note in the docs as it can be a significant slowdown to codebases.

Given what shapely is doing here is calling respective GEOS functions here, the question boils down to why GEOSGeomGetX_r, GEOSGeomGetY_r is slower than GEOSGeom_getCoordSeq_r within GEOS itself.
Also note that the comparison above is not precise as  doing a.x, a.y is calling get_x first and then get_y, while get_coordinates does only a single pass. I see two actionable items:

Follow up with GEOS in https://github.com/libgeos/geos and ask the same question there.
Use get_coordinates internally in Point.x and Point.y. At the same time, we should try to steer users towards get_coordinates or get_x when they need coordinates and do the loop as the performance boost of the vectorized operation will be much higher than the internal refactoring.

FWIW, it is mostly the ufunc machinery that adds a (relatively speaking) significant overhead when called for a single geometry object (and get_coordinates is not a ufunc, so I suppose it has less of this overhead).
See https://github.com/shapely/shapely/issues/1021 for a general issue about the ufunc overhead and performance of  scalar methods/attributes
I quickly tried what it would take to specifically optimize the Point coord access attributes, see https://github.com/shapely/shapely/pull/2035, which gets the .x down to ~200ns.
While it might be worth doing that for .x et al, because this is often used for code that works with scalar objects, we also don't want to encourage this kind of code too much, as often there are even more performant options available when rewriting your code to fully leverage the new vectorized capabilities of shapely >= 2.

Wow - that's quite the speed up.
I don't fully understand how to use the ufunc functionality yet (I plan to learn it) but to me that seems like a very good improvement. Does that change make it so that it is no longer possible to use ufuncs for .x?
One thing I did notice while trying to understand the codebase (I'm still a far ways out) is that getX() in Point.cpp in geos checks isEmpty() {
throw error
}
get coordinate
However, getCoordinate() also checks isEmpty
I tried to setup a custom version of GEOS to test it but I'm doing something wrong and my python instance ends up not being able to find shapely.lib, so I need to try some more.
But I would think that removing one of those isEmpty checks should also give a nice speed up

Does that change make it so that it is no longer possible to use ufuncs for .x?

No, the change is separate from the ufuncs, it just adds a specialized implementation for just the .x attribute that doesn't need to handle an array of geometries (which is what the ufuncs are good at)

One thing I did notice while trying to understand the codebase (I'm still a far ways out) is that getX() in Point.cpp in geos checks isEmpty() {

My guess is that this isEmpty check is very cheap onthe GEOS side and won't make that much of a difference.


Fix: Cannot read nodeId of null

Somehow, while scanning https://github.com/npm/cli, item is null while iterating over the parent[key] array. Adding this guard seems to fix it.

This has been resolved in v1.2.1


Pl also expose the escape function from helpers on the main object

To be able to require('ldap-filter').escapeFilterValue() which is basically helpers.escape().
We use a filter template to search if an user is present in LDAP like '(uid={userId})' and replace {userId} with user id programatically. Exposing the escape function would help in this case.
For now I can do require('ldap-filter/lib/helpers').escape() but my code could break if you rearrange the files with in the package.

One of the main objectives of this library is to for consumers to stop doing any plain-text manipulation of LDAP-style filters. How does something like this fail to cover your use-case?:
var filter = new ldapfilter.EqualityFilter({ attribute: 'uid', value: <your value>});

If you're parsing a user-provided filter and performing substitutions, the filter.forEach() function would allow you to walk the tree and replace values directly without having to edit the string "by hand".


homemade AIS receiver with OpenCPN

I know we don't prefer the -git versions of things, give me a few days and I will commandeer the non-git opencpn package and update it to a modern version.
(see
https://www.reddit.com/r/RTLSDR/comments/1mcikt/for_the_nautical_set_rtlsdr_with_grais_and_opencpn/)

The mapping tag is redundant. We already apply it to the whole role.

Ah cool, fixed up radio role tags too.


Get rid of forced reflows inside of animation loop

Something (I think in DOMMatrix) is causing a forced reflow, which takes precious time.

Why in the heck did I think it was in DOMMatrix before? How can that possibly cause reflows if it's not doing anything to any DOM elements.
I believe it is due to size calculations (using getComputedStyle).

This will be solved along with #56

closed in b8672eb


[React Native] [Thirdweb V4] : JSON value '' of type NSNull cannot be converted to NSString warning

I am getting this warning while connecting my wallet in React Native,
Basically What I am doing is...
I am using the ConnectWallet component in the React native project.
whenever I try to connect the wallet using the ConnectWallet component I get "JSON value '' of type NSNull cannot be converted to NSString" this warning.
it doesn't affect the app in development mode but in release mode the app crashes.
I tried using custom UI to connect wallet but it throws the same warning.
Here is the picture of the warning that I got in Xcode:

Here is the dependency version:
"@thirdweb-dev/chains": "^0.1.116",
"@thirdweb-dev/react-native": "0.7.3",
"@thirdweb-dev/react-native-compat": "0.7.3",
"@thirdweb-dev/sdk": "4.0.6",

Thank you

have you tried upgrading to the new thirdweb@^5 package? we recently added support for react native and is going to be the only supported version moving forward.
It has everything to build custom connection UI already, and prebuilt connect UI components are in the works (you can follow along in this PR #3246

Hi @joaquim-verges Thanks for the reply
No, I've not tried upgrading to V5 yet.
In v4, it was working perfectly fine but somehow it suddenly started crashing on iOS only, in the release build.
Here I'm attaching the screenshot of crashlytics, please have a look:

which wallet are you connecting in this case? looks lit might be sending a null value via WalletConnect websocket

@joaquim-verges
I'm trying to connect the "Meta Mask" mobile wallet, through the ConnectWallet component.
Here is the code snippet:

Hi @joaquim-verges
Is there any progress on this issue?
Thanks!

does it happen with other wallets? one thing i would check is making sure the metamask app is updated to the latest version

Hey @joaquim-verges I've the latest meta mask app installed but it is not working and the same issue.
PS: this issue is on iOS only, it is working fine in android

Hi @gregfromstl & @joaquim-verges
is there any progress / update on this issue?
Thanks!

Hey @jimit-raval-sf, the v4 SDK is deprecated and we'd recommend upgrading to v5. Please let me know if you have any questions regarding the migration


Task list and inconsistent column widths

We are using the new version of the task list with embedded helper text.  However, depending on the length of the helper text, the statuses all have different widths - and it doesn't look great.  Is this intentional or should we set a minimum width for the status column?

A bit more context from the discussion we had on Slack about this...
Every row is one li with two divs. The list items are styled like their own table (with display: table) and the divs are styled like table cells (with display: table-cell). What you might generally expect is that the whole list is styled like a table and the list item like a table row. That way this wouldn't happen.
@frankieroberto mentioned:

It was kind-of deliberate, so that the 'divide' between the title and the status is flexible, so that if you have a row with a long task name and a short status and a row with a short task name but a long status, then they'd both still use the maximum available space.

An example that illustrates this behaviour:

One way to fix this within a service without fixing the whole component is to use  s between words in a status.
But I'd like to look into pros and cons of fixing it for the whole component on the Design System side.


Hanwood Shropshire

Great Hanwood has been added to the gazetteer. It is the same place and coordinates as Hanwood.
Please move both Great Hanwood and its search records to the original Hanwood entry.
Geoff

Done


Arc-1215 - post-github-configuration - Replace Octokit with Github client

Use Github client instead of Octokit for Github configuration post

BTW, issue keys are case-sensitive ;) these won't work


feat/gateway-v2_clob-serum

Adding documentation for CLOB (Central Limit Order Book), Solana, and Serum.

Thanks for the docs! We'll make some revisions based on some structural changes contained in https://github.com/hummingbot/hummingbot-site/pull/93.


Fix issue with annotations and nested extensions

Previously any annotations on a nested extension would be ignored.  The code will now properly propagate the annotations to the types created by the extensions.

Can we add another test case for something like this?
domain foo {
    resource bar {}

    @alias(baz)
    extend bar {}
}

And make sure the alias applies appropriately

Merged, thanks!


NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN (MGUS_1) terminated with an error exit status (1)

Description of the bug
When running the nf-core i get to this step NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN process within the workflow, a critical error is encountered. The error occurs during the execution of the hisat2 command
Command used and terminal output
i used this script
#!/bin/bash
#! How many whole nodes should be allocated?
#SBATCH --nodes=1
#! How many (MPI) tasks will there be in total? (<= nodes*56)
#SBATCH --ntasks=56
#! How much wallclock time will be required?
#SBATCH --time=36:00:00
#SBATCH --partition=compute
#SBATCH --account=omics_core-rqyo8fdrbpw-DEFAULT-CPU
eval "$(conda shell.bash hook)"

conda activate bioinfo
folder_out="$1"
path="$2"
$CACHE_DIR="/home/rachid.elfermi/lustre/omics_core-rqyo8fdrbpw/rachid.elfermi/singdir/job_$folder_out"
mkdir -p "$CACHE_DIR"
export NXF_SINGULARITY_CACHEDIR="$CACHE_DIR"

cd $path
echo $path

nextflow run nf-core/rnaseq -r 3.12.0 -name $folder_out -profile singularity -params-file nf-params.json

rm -rf "$CACHE_DIR"

the error was

executor >  local (19)
[36/2b6a6d] process > NFCORE_RNASEQ:RNASEQ:PREPAR... [100%] 1 of 1 ✔
[09/aa88ec] process > NFCORE_RNASEQ:RNASEQ:PREPAR... [100%] 1 of 1 ✔
[22/50b781] process > NFCORE_RNASEQ:RNASEQ:PREPAR... [100%] 1 of 1 ✔
[d8/8ed8d5] process > NFCORE_RNASEQ:RNASEQ:PREPAR... [100%] 1 of 1 ✔
[73/0e6c03] process > NFCORE_RNASEQ:RNASEQ:PREPAR... [100%] 1 of 1 ✔
[8e/338e3e] process > NFCORE_RNASEQ:RNASEQ:PREPAR... [100%] 1 of 1 ✔
[12/689d52] process > NFCORE_RNASEQ:RNASEQ:INPUT_... [100%] 1 of 1 ✔
[-        ] process > NFCORE_RNASEQ:RNASEQ:CAT_FASTQ -
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[d7/4f39e0] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... [100%] 3 of 3 ✔
[59/fbf824] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... [100%] 3 of 3 ✔
[85/e510a8] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... [  0%] 0 of 3
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:FASTQ_... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_MA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_MA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_MA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_MA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_MA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:STRING... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:SUBREA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:MULTIQ... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BEDTOO... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BEDGRA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BEDGRA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BEDGRA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BEDGRA... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUALIM... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:DUPRADAR  -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:BAM_RS... -
[a2/41ccd0] process > NFCORE_RNASEQ:RNASEQ:QUANTI... [ 66%] 2 of 3
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUANTI... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUANTI... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUANTI... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUANTI... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUANTI... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:QUANTI... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:DESEQ2... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:CUSTOM... -
[-        ] process > NFCORE_RNASEQ:RNASEQ:MULTIQC   -
ERROR ~ Error executing process > 'NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN (MGUS_1)'

Caused by:
  Process `NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN (MGUS_1)` terminated with an error exit status (1)

Command executed:

  INDEX=`find -L ./ -name "*.1.ht2" | sed 's/\.1.ht2$//'`
  hisat2 \
      -x $INDEX \
      -1 MGUS_1_1_val_1.fq.gz \
      -2 MGUS_1_2_val_2.fq.gz \
       \
      --known-splicesite-infile genes.splice_sites.txt \
      --summary-file MGUS_1.hisat2.summary.log \
      --threads 12 \
      --rg-id MGUS_1 --rg SM:MGUS_1 \
       \
      --no-mixed \
      --no-discordant \
      --met-stderr --new-summary --dta \
      | samtools view -bS -F 4 -F 8 -F 256 - > MGUS_1.bam

  if [ -f MGUS_1.unmapped.fastq.1.gz ]; then
      mv MGUS_1.unmapped.fastq.1.gz MGUS_1.unmapped_1.fastq.gz
  fi
  if [ -f MGUS_1.unmapped.fastq.2.gz ]; then
      mv MGUS_1.unmapped.fastq.2.gz MGUS_1.unmapped_2.fastq.gz
  fi

  cat <<-END_VERSIONS > versions.yml
  "NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN":
      hisat2: 2.2.1
      samtools: $(echo $(samtools --version 2>&1) | sed 's/^.*samtools //; s/Using.*$//')
  END_VERSIONS

Command exit status:
  1

Command output:
  (empty)

Command error:
  INFO:    Environment variable SINGULARITYENV_TMPDIR is set, but APPTAINERENV_TMPDIR is preferred
  INFO:    Environment variable SINGULARITYENV_NXF_DEBUG is set, but APPTAINERENV_NXF_DEBUG is preferred
  WARNING: Skipping mount /var/apptainer/mnt/session/etc/resolv.conf [files]: /etc/resolv.conf doesn't exist in container
  (ERR): mkfifo(/tmp/45.inpipe1) failed.
  Exiting now ...
  [main_samview] fail to read the header from "-".

Work dir:
  /srv/lustre01/project/omics_core-rqyo8fdrbpw/rachid.elfermi/Test-RNA/split/batch_1/work/61/447cb638f20bd72b89552d923b98fa

Tip: you can replicate the issue by changing to the process work dir and entering the command `bash .command.run`

 -- Check '.nextflow.log' file for details

Relevant files
No response
System information
i working on HPC with node of 56 cpu and 180 GEGA o ram
i have a home directory of 100 G which 40 gega is free  and the working dir is 20 Tera

Hi @rachidelfermi ! Did you manage to find a solution to this? It appears to be an issue with your HPC. Maybe the tmp space on your cluster filled up?
  (ERR): mkfifo(/tmp/45.inpipe1) failed.

Will close this because it looks like an infra issue and not pipeline related. Please feel free to join the nf-core Slack Workspace for any future questions/issues. We have an #rnaseq channel where you can get more real-time help.

Hello, I seem to be having a similar problem, here is my error log that:
nf-core/rnaseq execution completed unsuccessfully!
The exit status of the task that caused the workflow execution to fail was: 1.

The full error message was:

Error executing process > 'NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN (pituitary_stage3-1)'

Caused by:
  Process `NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN (pituitary_stage3-1)` terminated with an error exit status (1)

Command executed:

  INDEX=`find -L ./ -name "*.1.ht2" | sed 's/\.1.ht2$//'`
  hisat2 \
      -x $INDEX \
      -1 pituitary_stage3-1_1_val_1.fq.gz \
      -2 pituitary_stage3-1_2_val_2.fq.gz \
       \
      --known-splicesite-infile aaa_genomic.filtered.splice_sites.txt \
      --summary-file pituitary_stage3-1.hisat2.summary.log \
      --threads 8 \
      --rg-id pituitary_stage3-1 --rg SM:pituitary_stage3-1 \
       \
      --no-mixed \
      --no-discordant \
      --met-stderr --new-summary --dta \
      | samtools view -bS -F 4 -F 8 -F 256 - > pituitary_stage3-1.bam

  if [ -f pituitary_stage3-1.unmapped.fastq.1.gz ]; then
      mv pituitary_stage3-1.unmapped.fastq.1.gz pituitary_stage3-1.unmapped_1.fastq.gz
  fi
  if [ -f pituitary_stage3-1.unmapped.fastq.2.gz ]; then
      mv pituitary_stage3-1.unmapped.fastq.2.gz pituitary_stage3-1.unmapped_2.fastq.gz
  fi

  cat <<-END_VERSIONS > versions.yml
  "NFCORE_RNASEQ:RNASEQ:FASTQ_ALIGN_HISAT2:HISAT2_ALIGN":
      hisat2: 2.2.1
      samtools: $(echo $(samtools --version 2>&1) | sed 's/^.*samtools //; s/Using.*$//')
  END_VERSIONS

Command exit status:
  1

Command output:
  (empty)

Command error:
  WARNING: Skipping mount /usr/local/var/singularity/mnt/session/etc/resolv.conf [files]: /etc/resolv.conf doesn't exist in container
  (ERR): mkfifo(/tmp/53.inpipe1) failed.
  Exiting now ...
  [main_samview] fail to read the header from "-".

Work dir:
  ~/project/work/f2/3c12bc9bf0e4ae9ae09f6ca2a68a96

Tip: when you have fixed the problem you can continue the execution adding the option `-resume` to the run command line

I use an offline command line to execute the commands, here is my command line code：
nextflow run -qs 8 -profile singularity -bg /home/huyan/software/nf-core/rnaseq/nf-core-rnaseq_3.14.0/3_14_0/ --email<EMAIL_ADDRESS>--input ./samplesheet.csv --fasta /new_data/AcaLat_SV/assembly/aaa_genomic.fna --gtf /new_data/AcaLat_SV/assembly/aaa_genomic.gtf --aligner hisat2 --skip_qualimap --save_reference --outdir ./00_test --max_memory 40.GB --max_cpus 8

Could you plz tell me what should I do next so that I can continue the pipeline with the -resume parameter as suggested without errors?☺


Newkaku dimming not working properly with Home Assistant

Hi
I utilize the Sonoff RF Bridge with the RFLink32 image for this device. I control my 433MHz devices using Home Assistant (HA) through the Sonoff Bridge. All my devices operate on the Newkaku protocol ([Plugin_003.cpp]). The on/off switches works perfectly. However, when sending dimming commands from HA, the behavior is somewhat erratic (for instance, when using the dimming slider in HA). I've verified the approximate percentage signal sent from HA and its corresponding signal received at the RF bridge. It's important to note that the Newkaku protocol has 15 dimming levels.
1% = 00
7% =  01
13% = 02
20% = 03
27% = 04
33% = 05
40% = 06
47% = 07
53% = 08
60% = 09
67%  = 00
73% = 01
80% = 02
87% = 03
93% = 04
100%  = 05
On the other hand, if I manually send codes via MQTT to the RF bridge using HEX codes, it works fine (the first column is the code sent to the bridge, the second column is the reply from the bridge):
1 = 1
2 = 2
3 = 3
4 = 4
5 = 5
6 = 6
7 = 7
8 = 8
9 = 9
a = 10
b = 11
c = 12
d = 13
e = 14
f = 15
(For info, codes sent look like this as an example: 10;NewKaku;ID=00b23dea;SWITCH=4;SET_LEVEL=a; )
However, Home Assistant does not send hex code to the RF bridge. The optimal solution might be to modify the RFLink32 code so that it correctly interprets the code sent from Home Assistant. I have attempted to review parts of the code, but lack the expertise to determine the necessary corrections. Could someone guide me in the right direction? Thank you.

Sorry, posted this the wrong place. Closed.

Closed


Create mod compat

Describe your suggestion:
Shields can be powered by compressed air tanks worn by the player (or sitting in their inventory) or rotational force "winding them up". Would be an interesting addition for a lot of lower tech packs.

Definitely keen! Need to make some textures and set it up

Will be coming in 1.19.2 version 3.1


Scenarios Management menu is not visible

I installed tock from docker from https://github.com/theopenconversationkit/tock-docker & run the docker command "Run the Bot API stack: docker-compose-bot.yml", Login from admin everything is working fine but one menu "Scenarios Management" is not visible. Please guide me, how can I visible "Scenarios Management" menu?

Hello,
Scenario are "stories" in tock : https://doc.tock.ai/tock/fr/user/concepts/#scénario-ou-story

If you're talking about the new Scenario management feature, it hasn't yet joined the repo : https://github.com/theopenconversationkit/tock/pull/1483

Development of this feature has been abandoned. Resources have been entirely redirected towards AI generative features.


Support MySQL as a backend

Motivation
Datasette is an amazing frontend UI that only officially supports sqlite. With datasette-parquet, a DuckDB backend works pretty well. But DuckDB is also capable of attaching a live MySQL connection with:
INSTALL mysql;
LOAD mysql;
ATTACH 'host=... user=... passwd=... port=... database=...' AS mysql_db (TYPE MYSQL);
USE mysql_db;

This opens the door to Datasette over live MySQL, which would be very attractive for many people with an existing MySQL database.
Proposal
Add a mysql config option (similar to file and directory) that takes all the config needed to create a MySQL connection string in DuckDB (e.g. db_host, ...), so that datasette works with a live MySQL connection.

I got this working as a proof of concept with many hacks, which I could clean up into a PR.
Getting a MySQL connection is not hard, but then it's available at <alias>.<mysql_db_name> instead of being the default db, which means you need to add USE statements in front of every cursor creation/execution to make it run cleanly.
In my current proof-of-concept, Datasette fails on / path, works on /<db> path and all queries, but fails on /<db>/<table> path for browsing.
Incidentally, it's amazing to me to have gotten this far in just an hour or two, and I'm super impressed that you put this plugin together. Nice work 🙌


Schema is not updated after authorization headers is added

Our GraphiQL endpoint needs an "Authorization" header.
If I add it manually to the Headers tab, it works for the query. But of course I want to use the "Documentation Explorer". But this shows only a "Error fetching schema" message. Hitting the "Re-fetch GraphQL schema" is using the header too (I can see request with a 200 response in the network tab) , but the schema is not updated and the Docs still show the same error message.
Using the search suggestions/autocomplete is working, but clicking on a suggestion still shows the error message.
Clearing the storage doesn't change it too.
Reloading the page in the browser removes the Header, while the query and the variables are kept.  (Maybe a different bug)
GraphiQL version: 2.0.4

Hey @pitgrap 👋 this sounds indeed like it should be fixed with #2653. Can you check if you still see the problem in<EMAIL_ADDRESS>

Reloading the page in the browser removes the Header

By default headers are not persisted as a security measure (they might contain sensitive tokens). There is a prop called shouldPersistHeaders that toggles this behavior, are you using this prop?

Hi @thomasheyenbrock , we're using graphiql provided by stellate.co. So they need to update it and I cannot say, if it is possible to change the property. I will check it and will also try to test it locally.

Ah, good that I work at Stellate 😜 will see that we bump the version in our next release!

@thomasheyenbrock perhaps this would be a good candidate for a new user definable setting? that way, other frameworks can use the safer option by default, and users can choose this riskier opt in
it seems excessive, but once we reported our first CVE that would have allowed this data to be exfiltrated by non-permissioned phishing attacks in some cases, we had to keep it this way as part of our CVE resolution that we worked on with Cure53, and it protected against another CVE that allowed users to exfiltrate this data if the option was enabled 🥵

I think shouldPersistHeaders should be a user definable setting. So stellate can keep it disabled by default, but I can enable it in my browser.

@thomasheyenbrock in the user settings dialog! the one we use for light/dark toggle

Ah gotcha! Very interesting proposal, worth exploring 👍

Just retestet with 2.0.8 and the problem in this ticket has been fixed. -> Closing.
For the idea of a user definable setting for persisted headers you should create a new issue.

We also just fixed this at Stellate, we're now also using GraphiQL 2.0.8 👌
I opened a follow-up issue about the user-facing setting: https://github.com/graphql/graphiql/issues/2793


fix(schema-reference): adding empty line after added schema reference

For keeping distance from other content.
If the string # yaml-language-server: $schema=values.schema.json is found, helm-schema will still not add the schema reference when called with --add-schema-reference, avoiding cases where it would be added twice for values.yaml touched by previous helm-schema versions.
If it isn't found, it will get added with an additional empty line:
# yaml-language-server: $schema=values.schema.json

# -- Some comment
foo: bar

fixes #48

I was also wondering about the \r\n detection in the same function - this requires a file to end with \r\n for it to be recognized.
Could just do strings.Contains instead, using Windows line endings as soon as one is found anywhere in the document?
https://github.com/dadav/helm-schema/blob/c1f9118bd9610700468948d204f6c601b8b95155/pkg/util/file.go#L47-L50


AS3 Conversion Bug Declaration shortened to Dec

Environment

ACC Version: 1.18
AS3 Version: 3.34
BIG-IP Version: 16.1.0

Summary
When converting TMOS config w/ ACC I get this:
"$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/latest/as3-schema.json",
"class": "AS3",
"dec": {

instead of
"$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/latest/as3-schema.json",
"class": "AS3",
"declaration": {

Steps To Reproduce
Steps to reproduce the behavior:

Convert following config:
ltm virtual /Common/test-vs {
creation-time 2022-02-14:05:39:44
destination /Common/<IP_ADDRESS>:80
ip-protocol tcp
last-modified-time 2022-02-14:05:39:44
mask <IP_ADDRESS>
pool /Common/test-pool
profiles {
/Common/serverssl-insecure-compatible {
context serverside
}
/Common/tcp { }
}
serverssl-use-sni disabled
source <IP_ADDRESS>/0
source-address-translation {
type automap
}
translate-address enabled
translate-port enabled
}
ltm pool /Common/test-pool {
members {
/Common/f5.com:443 {
address <IP_ADDRESS>
}
}
monitor /Common/gateway_icmp
}
ltm node /Common/f5.com {
address <IP_ADDRESS>
}
Conversion:
{
"$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/latest/as3-schema.json",
"class": "AS3",
"dec": {
"class": "ADC",
"schemaVersion": "3.34.0",
"id": "urn:uuid:534d5b96-bf64-480d-b747-059d02c8b28a",
"label": "Converted Declaration",
"remark": "Generated by Automation Config Converter",
"Common": {
"class": "Tenant",
"Shared": {
"class": "Application",
"template": "shared",
"test-vs": {
"layer4": "tcp",
"pool": "test-pool",
"translateServerAddress": true,
"translateServerPort": true,
"class": "Service_TCP",
"clientTLS": {
"bigip": "/Common/serverssl-insecure-compatible"
},
"profileTCP": {
"bigip": "/Common/tcp"
},
"virtualAddresses": [
"<IP_ADDRESS>"
],
"virtualPort": 80,
"persistenceMethods": [],
"snat": "auto"
},
"test-pool": {
"members": [
{
"addressDiscovery": "static",
"servicePort": 443,
"serverAddresses": [
"<IP_ADDRESS>"
],
"shareNodes": true
}
],
"monitors": [
{
"bigip": "/Common/gateway_icmp"
}
],
"class": "Pool"
}
}
}
}
}

this bug affects the vscode extension, which looks for the "declaration" object to inject the atc agent and does successfully process with AS3.  AS3 post error below;
{
    "id": "22db6901-ed06-4ebf-aeef-397b94dc479b",
    "results": [
        {
            "message": "for action \"deploy\", a declaration is required.",
            "code": 400
        }
    ],
    "declaration": {}
}

With the help of @p-semenov-f5, we found that this is happening in vscode.  I will have a fix out shortly.
Tracked here:  https://github.com/f5devcentral/f5-conx-core/issues/20
Will close everything once fixed

fixed in vscode-f5 pending v3.6.1 release.  please close


[Pretty Trivial] Adjust some comments

I think it is better to just say "something", shorting it isn't that valuable imo and makes the code look less professional. The scripted diff is not verifying locally, and I'm not sure why... The verification script isn't seeing this as a scripted diff.
Also, a typo is fixed

@PastaPastaPasta there must be an empty line between the commit subject and comment body. Otherwise the script is not recognized.

@PastaPastaPasta please rebase this on develop after #3256 has been merged. Otherwise the script checks are not run on Gitlab.

rebased stuff and fixed scripted-diff


Make all peers submit genesis

As described in https://github.com/hyperledger/iroha/issues/4225#issuecomment-2087976958

Currently we have following behaviour:

GenesisTransaction is provided to Leader peer
Leader peer signs it and creates SignedBlock
Leader peer sends SignedBlock to all peers
Finally all peers have same SignedBlock (signed only by Leader peer)

Initially I planned to implement this task as follows:

GenesisTransaction is provided to all peers
Each peer extract executor and parameters from GenesisTransaction (they should be first and second instructions)
Leader peer signs GenesisTransaction and creates SignedBlock
Leader peer sends SignedBlock to all peers
Peers receive SignedBlock and check that block payload equals to GenesisTransaction they have
Finally all peers have same SignedBlock (signed only by Leader peer)

We discussed with @Erigara and found problem with this approach: all peers have all necessary data (GenesisTransaction), but still have to wait SignedBlock from the Leader. So we agreed on the following approach:

kagami genesis sign will produce SignedBlock instead of GenesisTransaction. To do so topology field will be added to genesis.json
SignedBlock is provided to all peers. All peers will use that SignedBlock directly as a first block without any communication. Note that first block will not be signed by any peer, that is SignedBlock::signatures will be empty.

@mversic @0x009922 what do you think?

kagami genesis sign will produce SignedBlock instead of GenesisTransaction. To do so topology field will be added to genesis.json

yes, this is also better because it hardcodes the initial topology

SignedBlock is provided to all peers. All peers will use that SignedBlock directly as a first block without any communication. Note that first block will not be signed by any peer, that is SignedBlock::signatures will be empty.

why does it have to be provided to all initial peers and can't be also circulated via block sync? what happens when a new peer is added to the network?

why does it have to be provided to all peers and can't be also circulated via block sync? what happens when a new peer is added to the network, how does it get genesis?

This is according to https://github.com/hyperledger/iroha/issues/4225#issuecomment-2087976958. @0x009922 did you propose to provide genesis to all peers including peers that are not in initial topology (added to the network later), or did I misunderstand your comment?

why does it have to be provided to all peers and can't be also circulated via block sync? what happens when a new peer is added to the network, how does it get genesis?

This is according to https://github.com/hyperledger/iroha/issues/4225#issuecomment-2087976958. @0x009922 did you propose to provide genesis to all peers including peers that are not in initial topology (added to the network later), or did I misunderstand your comment?

We need to have block sync work even for genesis block. What must be given to all peers is hash of the genesis block. Genesis block must be provided to at least one peer but can be provided to multiple at the same time. We don't want either of these to be treated as an error. From the perspective of any peer it doesn't matter how it receives the block, whether given on startup or delivered after startup (through block sync)


DO NOT MERGE! Fast Forward stable to 96750f21d86e4a8d71d9c519145b5963d9c0e9b2.

This PR will be merged automatically once checks are successful.

Jenkins job manager/postsubmit passed


[squid:S2864] "entrySet()" should be iterated when both the key and value are needed

This pull request is focused on resolving occurrences of Sonar rule
squid:S2864 - “"entrySet()" should be iterated when both the key and value are needed ”.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S2864
Please let me know if you have any questions.
Ayman Abdelghany.

I find that this change produce less readable code, so I would not merge it.


I haven't used it by myself but there is a plugin for that: https://www.npmjs.com/package/style-ext-html-webpack-plugin


codec_image_transport: 0.0.2-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository codec_image_transport to 0.0.2-0:

upstream repository: https://github.com/yoshito-n-students/codec_image_transport.git
release repository: https://github.com/yoshito-n-students/codec_image_transport-release.git
distro file: melodic/distribution.yaml
bloom version: 0.7.2
previous version for package: null

codec_image_transport
* Initial release

Holding for sync


Add demosaic.py to pipeline to convert stereo images to image files

Plan to deploy this extractor this week.

I have a VM with this extractor installed and dependencies updated, I think ready to run.
Outstanding question is whether we should support writing resulting JPG to /derived_data directory accessible via Globus, or deploy now and handle that later.

@robkooper before starting up the extractors, we need to mount the Roger /sites directory to the VMs they are going to run on. Then we can write extractor outputs to the /sites/ua-mac/derived_data/Level1/ directory.

You will need to send the IP address of the VM to JD, then I'll show how to mount the drive.

@jdmaloney the VM for the demosaic extractor I created has floating IP <IP_ADDRESS>. Can you do whatever is required to allow mounting of roger to it?
I think in general we want to mount READ ONLY
/projects/arpae/terraref/sites/ua-mac/raw_data

Don't want to limit it to a particular sensor in this case because it triggers from several sensors.
Then mount for WRITE it should be tailored to the specific extractor that VM.
/projects/arpae/terraref/sites/ua-mac/Level_1/demosaic

Under /demosaic the extractor can replicate the directory structure of the source dataset, probably from the  level down.

@max-zilla I've created those exports (and the Level 1 demosaic directory).  Make sure the user doing the writing on the VM has the id: 47852 so it can have permission to write.  Let me know if that would be a problem and we can work it a different way, but having that specific uid for that user is preferred if possible.

Extractor is now in this repo: https://github.com/terraref/extractors-stereo-rgb
I updated it to leverage the local-mount ROGER code.

This has been deployed. Results accumulating in /ua-mac/Level_1/demosaic.


Form history glitch: requesting "edit" action for non-existent forms

See console for 404 errors when you click on history button. This is because the ResourceView should not be making /edit/ requests for previous versions.

Related issue: diffs not being represented in IGT display.


feat(touch-backend): add option to begin drag after delayed start

This essentially allows to trigger the start of a drag operation without requiring the user to move after he has pressed/touched for a certain amount of time.

This looks reasonable, I may change the config name on merge

@aomader Apologies for getting to this late. It looks like the touch backend has configuration options for supporting touch delays (e.g. delay, delayTouchStart, and delayMouseStart). IIRC, if these are set to values greater than zero you can support delays on dragging. And I believe the delay attribute will configure delayTouchStart and delayMouseStart at once.
Does this PR expand upon this in some way? Were those configuration values insufficient?

@darthtrevino The current configuration only ensures that a drag operation is started if some time has passed between start and first movement. The important bit is that the drag operation is started after the movement. I.e., just pressing/holding something is not sufficient.
This is why I added this option, which allows to specify the additional behaviour to trigger the drag after the delay* amount without requiring an extra movement. I would argue that this is actually the intuitive behaviour. If I touch down on something and wait for the specified time, I would want to see a drag indication (which is only possible to visualize after the drag operation has started) when that time has passed, rather than when I start moving.


fix setup and run instead of run only for madara

Hey @TedZy829, I added a first round of review. We should also probably add a check to prevent users from using older versions of Madara. So a lower limite on the version select drop down,

noted, will try to do so thanks!


metrics_format doesn't honor field variable names

metrics_format => "team.infra.poller.%{host}.*"

Results in a actual directory on the graphite filesystem of %{host}.  What's expected is the value of that field.

Mmmm, this should be a simple matter of adding a call to sprintf to that field

Released in version 1.0.2
Thanks for filing the report @blysik !

Tested and confirmed works.  Thanks!

@blysik I'm really interested in what it is you're putting together. Is there any chance you'll be putting this info up as a blog post? If so, I'd love to reshare it both on my network and with the logstash team!


timeouts

I might use superagent for a mobile project, so I need interrupts to deal with shoddy mobile networks.
Experimented a bit over the weekend. I have some working code in my fork that works like this:
request('GET', '/slow')
    .interruptAfter("1.5s")
    .end(function(res){
        if (req.interrupted) { do stuff  and return }
        else { whatever }
    })

There's also a interruptEvery. The time argument can be a number of millis or a string of the form "300ms" or "1.5s".
Any opinons. Not entirely sure about the API. I'd be happy to fix up my branch and submit pull request if we could come up with a reasonable API.

I would definitely prefer .timeout(ms) personally

And what is default timeout for requesr? Can't find this info!

I also can't find it. I want to create a longer timeout for a particular request.

By default there is no timeout (superagent will wait for the response forever). You set timeout with .timeout method, e.g. to wait up to 5 seconds: request.post('/foo').timeout(5000).end();

Okay, thanks. That's good to know.


Sixel background select when scrolling

This is an issue that's been raised a couple of times since Windows Terminal added sixel support. What happens when you specify a background select area that extends beyond the bottom of the screen, and then output sixel content that triggers a scroll? How much of the screen is ultimately filled by that background select?
My assumption is that the background select is a distinct operation that happens at the start, and is clamped to the boundaries of the screen. If you output enough sixels to force the screen to scroll, it's not going to fill any more of the background at that point, because it's already done with the background select.
I'm fairly confident that my understanding is correct, but I've been wrong before, so it would be good to get some confirmation of the correct behavior. So if you ever get back to testing on your VT340 again, I'd appreciate you giving this test script a run:
#!/bin/bash

# Test the effect of Background Select when an image scrolls.

CSI=$'\e['			# Control Sequence Introducer
DCS=$'\eP'			# Device Control String
ST=$'\e\\'			# String Terminator

echo -n ${CSI}'!p'
echo -n ${CSI}'H'
echo -n ${CSI}'J'

# Enable reverse screen mode so the background is white
echo -n ${CSI}'?5h'

# Position the cursor 3 rows from the bottom
echo -n ${CSI}'22;35H'

# Fill 120x120 of the background in black (clamped to 3 rows, 60 pixels)
echo -n ${DCS}'q"1;1;120;120'

# Render a 60x60 square in blue on the bottom 3 rows
echo -n '#1!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-'

# Render a 60x60 square in red, scrolling up another 3 rows
echo -n '#2!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~'

# Apply a bunch of graphic new lines to scroll the image up to the middle
echo -n '------------------------------'

# End the image sequence
echo -n ${ST}

# Move the cursor back to home
echo -n ${CSI}'H'

If my understanding is correct, this should render three equally sized squares in an r pattern like this:

If I'm wrong, the bottom right corner of that pattern may be filled in black as well.

I am amidst the whirlwind, but have touched down briefly at home. I will try to test today.

Seems it is slightly more complex than expected.

I haven't investigated, but offhand this looks like something that is due to the  VT340's peculiar interaction between foreground and background text with the sixel color palette and may not be something that any modern terminal emulator will want to replicate.

Wow! That was not what I was expecting at all. But thanks for the quick test. I'll have to see how easy that is to replicate. My current implementation is definitely not what users are expecting, so if it's not technically correct, there's no justification for leaving it as it is.

Background color switching on the VT340 is indirect; it does not change color 0 (text background) in the colormap. Since the text color and graphics colormap are shared on the VT340, the sixel image's background is not going to look correct.
I think it'd be justified to omit this feature on any terminal which does not tie  the text colormap to the sixel colormap. (I believe your Microsoft implementation decided to not do things that way, right?)

I was thinking about how to demonstrate that the background of the screen is not the same as the background of the sixel image and I realized, you can almost get the image you had expected by doing something silly.  Change the line which draws the blue square to:
# Render a 60x60 square in blue on the bottom 3 rows, omit final newline
echo -n '#1!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~'
# Paint background as a 1x1 black pixel, send newline. (Kludge-o-rama!)
echo -n '";;1;1-'

That results in:

I get that the graphics background isn't the same as the text, but that's exactly the problem modern terminals have. If they shared the same color table (as they do on the VT340), it's unlikely anyone would even notice the effect of this (you'd have to be using reverse screen mode like I did in the test above). But modern terminals can have weird color schemes, where the text background can be quite different from the default black of the graphics palette, so when we get this wrong it's immediately obvious.
As a common example, a transparent gif in img2sixel is rendered with the background filled, and then only the non-transparent pixels drawn on top of that. If you output that at the bottom of the screen, we only do the background fill for one row, because that's the maximum area it can cover at the point the raster attributes are interpreted. But then the remaining lines of the image don't have a background.
So you get something like this:

The first image was output in the middle of the screen, but second image was at the bottom, and triggered a scroll. If I matched the VT340 behavior correctly, those should both look the same I think.

The thing I'm not sure about now is how far the VT340 does actually fill in these circumstance. It's clearly not paying any attention to the specified raster attributes height, but does that mean it fills the full height of any text row that scrolls when it's active? Or is it only the height of the sixel rows that have been output? If it's the former, then we're still going to end up with situations where a scrolled image looks different from one that didn't scroll.
I need to go to bed and think about this some more tomorrow.

I've got my implementation working with the two examples above, but there are so many edge cases that I'm not at all confident that what I'm doing is correct. So I've now made an extended version of the test which will hopefully reveal some more details of the VT340's implementation. If I've managed to match it on this test, I'll consider my code good enough to ship.
#!/bin/bash

# Test the effect of Background Select when an image scrolls.

CSI=$'\e['			# Control Sequence Introducer
DCS=$'\eP'			# Device Control String
ST=$'\e\\'			# String Terminator

echo -n ${CSI}'!p'
echo -n ${CSI}'H'
echo -n ${CSI}'J'

# Enable reverse screen mode so the background is white
echo -n ${CSI}'?5h'

# Background select with varying width and aspect ratio
echo -n ${CSI}'19;20H'
echo -n ${DCS}'q"20;1;240;240'
echo -n '#1!120~'
echo -n '"10;1;120;1--'
echo -n '#2!60~'
echo -n '"5;1;60;1--'
echo -n '#3!30~'
echo -n ${ST}
echo -en '\b\b>\n\n'

# Background height exactly fits, and is a multiple of 6.
echo -n ${CSI}'22;37H'
echo -n ${DCS}'q"1;1;120;60'
echo -n '#1!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~-!60~----'
echo -n ${ST}
echo -en '\b\b>'

# Background height extends beyond the bottom margin.
echo -n ${CSI}'24;50H'
echo -n ${DCS}'q"1;1;60;21'
echo -n '#2!30~-!30~-!30~-!30~-!30~'
echo -n ${ST}
echo -en '\b\b>\n'

# Background height exactly fits, but isn't a multiple of 6.
echo -n ${CSI}'24;58H'
echo -n ${DCS}'q"1;1;40;20'
echo -n '#3!20~-!20~-!20~-!20B----------'
echo -n ${ST}
echo -en '\b\b>'

# Move the cursor back to home
echo -n ${CSI}'H'

For reference, this is what I'm hoping the above test will look like:

The first test is looking at the effects of the raster attributes width and aspect ratio on the background fill when scrolling. The part I'm most unsure of is the last block, which scrolls a sixel band that isn't a multiple of the row height. If the background is filled with a multiple of the row height (rather than the sixel band height), the black part won't align with the green.

The second test is checking whether the background continues to be filled when the image scrolls if the initial raster height fits on screen. The image is output with a height of 60px when there is exactly enough space for 60px, but then adds a few more graphic new lines to force a scroll. I'm assuming that additional area is not filled, but if it is, the black part won't align with the blue.

The third test is checking how much of the background is filled when the initial raster height doesn't fit on screen. The image is output with a height of 21px, when there is only enough space for 20px. A 30x30px block is then output which triggers a scroll. I'm assuming that will result in an additional 10px of the background being filled. But if it always fills a multiple of the row height (i.e. 20px), the black part won't align with the red.

The fourth test is similar to the second, checking that the background doesn't fill when scrolling if the initial raster height fits on screen. In this case, though, the initial height (20px) is not a multiple of 6, which might make a difference to the result.

The > characters are just showing where the cursor position ends up after each test. I'm not anticipating any unexpected behavior there, but it's possible this'll uncover some new complication I wasn't previously aware of.


fix pcd labels projection bug

What changes are proposed in this pull request?
Add location, dimensions, and rotation to the Detection label. While these fields are only relevant to the 3D label, not having them in the schema means they get omitted when fo.SelectFields view stage is applied (for instance in _project_pagination_paths, which runs as part of paginateSamplesQuery in the grid), which in turn can have unintended side effects like 3D labels not being projected in the grid.
Since the impetus for this PR is 3D labels not being projected in the grid, an alternative approach - if we're opposed to adding these fields in the schema - is to add a conditional logic in _project_pagination_paths that ~passes meta_filters to  fo.SelectFields() if the media type for the current view is point-cloud so that location, dimensions and rotation fields aren't excluded.~
Yet another approach is to use a different label class, nominally Detection3D, for 3D detections.
before:

after:

Don't know the context but plus one for separate 3d objects types, if we could make that work

@brimoor Good points! And thank you for the added context. I updated the _get_default_sample_fields method.
@swheaton separate 3d objects types would be nice, but Brian raises an important point:

The problem is (was) that grouped datasets share the same schema, so it wouldn't be easy to have a dataset whose ground_truth field contains Detections for image slices and Detections3D for point cloud slices.

The following gif makes it clear:

Without same field for detection, I suppose we'd either have to offer an API to "link" the two detections, or change the app UI and offer multiple toggles for 2D and 3D.

I think the initial changes adding the fields to the label type are reasonable. If it affects import/export significantly, perhaps it is not viable. But in terms of the sidebar and unwanted aggregations, we already exclude bounding_box here. The same can be done for these new fields

Good point about how the App excludes bounding_box 👍 this would be an analogous case where we have more list fields that aren't appropriate for in App filtering.
Maybe I'm being overly cautious but I was also hoping to avoid print(fo.Detection()) showing three more attributes that aren't applicable in many cases...
The ideal would really be a Detection3D class, just don't know how to achieve it...

@sashankaryal @benjaminpkane can we go with https://github.com/voxel51/fiftyone/pull/3761 instead to fix this?

good with me

@sashankaryal @benjaminpkane can we go with #3761 instead to fix this?

Works for me.


Fix newline behvaior

Fixes br with children
Uncaught (in promise) Error: br is a void element tag and must neither have children nor use dangerouslySetInnerHTML. Check the render method of EntryMarkdownView.
This is an example for the text that causes problem:
**[\u200e8/\u200e18/\u200e2016 10:53 AM] kuku: **
Hi Mike. I saw your ticket about suspicious activity. Is there any background you can give me into why something is suspected?
[\u200e8/\u200e18/\u200e2016 11:01 AM] kuku:
Hi kiki, keke has resolved the issue with the help of Travis. It was a sync issue with Sophos SafeGuard. The ticket # is 7777.  I was not able to login after I lock my computer when I walked away.  I kept trying the new password I setup this morning an it would not let me in. I decided to restart and the message I received was that if I restarted the other users using my machine would be logged off.  So at that point I shut down the computer.
[\u200e8/\u200e18/\u200e2016 11:02 AM] koko:
Ok, sounds good. Thanks for info.

This is not a correct fix


sync up victory boilerplate with formidable boilerplate

cc/ @ryan-roemer
does what it says on the tin

@boygirl -- LGTM. Thanks!


Popup is not shown

I cannot seem to get it to work, the pop-up does not seem to come up on my version although I would not like this to happen. is it possible that i can put my own API server side which everyone on the website uses? Regarding the first issue, i have renamed the index HTML to bot.html due to it being a redirect from the index, but i dont think this would be the issue. Apart from that i have just pasted the Index and the 2 files into my website.
Please help me, thanks!

i was told i can not use this code on an online website? is this true and if so is there anything else server side you have? if its not true can you provide me with help on how to get it into my server


feat: separate VPN configurations and ccd folders

Follow-up of https://github.com/jenkins-infra/azure-net/pull/10
The goal of this PR is to be able to use/generate config for several VPNs.
Ref: https://github.com/jenkins-infra/helpdesk/issues/2844

Is there any documentation updates required as part of this?

Yes, I shouldn't have put this PR in "ready for review", switching to draft again.
Essentially the changes will concern admin instructions, so the ccd are stored in "default" and/or "private"

Is there any documentation updates required as part of this?

Once it will be finished: yes \o/ (but now, no effort on the documentation as this is a set of moving parts)


JLink images have broken https support

Summary
This error does not happen with all URLs. Only happens in JLink images.
This URL is affected: https://launchermeta.mojang.com/v1/packages/fd990561a3502903a819815ca63b7ac13110a84c/21w44a.json
Steps to reproduce

Clone this: https://github.com/XakepSDK/jlink-bug
Run mvn package in root
Unpack package from target/test-load-1.0-SNAPSHOT.zip
Run bin/launcher

Expected results
It works
Actual results
It does not work
Exception in thread "main" javax.net.ssl.SSLProtocolException: Received close_notify during handshake
        at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129)
        at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
        at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:357)
        at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:313)
        at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:304)
        at java.base/sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:250)
        at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:203)
        at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:172)
        at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1500)
        at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1415)
        at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
        at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
        at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:580)
        at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:183)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1665)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589)
        at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224)
        at java.base/java.net.URL.openStream(URL.java:1161)
        at test.load/dk.xakeps.testload.Main.main(Main.java:10)

Triaging info
Java version:
On windows 10 amd64:
openjdk version "17.0.1" 2021-10-19 LTS
OpenJDK Runtime Environment (build 17.0.1+12-LTS)
OpenJDK 64-Bit Server VM (build 17.0.1+12-LTS, mixed mode)

On Arch Linux:
openjdk version "17.0.1" 2021-10-19
OpenJDK Runtime Environment (build 17.0.1+12)
OpenJDK 64-Bit Server VM (build 17.0.1+12, mixed mode)

What is your operating system and platform?
Windows, Arch Linux
How did you install Java?

Temurin installer on windows
Form Arch repos on Linux

Did it work before?
I don't know
Did you test with other Java versions?
No

Fixed it. If anybody encounters it, add module jdk.crypto.ec. It can't find right crypto algorithms.

A quick note on this - the blog entry about creating your own jlinked runtime explicitly mentions that the jdk.crypto.ec doesn't get picked up properly with jdeps, so it's not just you who has encountered this :-)

Adding for Google-Fu:
BCXDHPublicKey cannot be cast to class XECPublicKey

... same cause, different error. 🍻


standardize _factory_type_name

Pull Request
This pull request addresses #76

[ ] make sure you are pulling from a dev branch on your fork
[ ] check for code linting

Is this complete? Or should I give it a bit more time? 😉

Very much complete! A solid one-liner:satisfied:


Add an estimation of available models

Can those +100k ML models be used with the inference API?

From my estimations, yes (at least 2/3 of the 150k public models)


N44: add screen ball and battle city games

Part of #1317
Thanks.

Ah, I used to play BC a lot on Dandy back in the middle of the nineties :D
Thanks for the PR!

Cool, thanks. Feel free to tweak the content.


Forbid password reuse

When:

change password in admin
change password on auth
reset password via email

Codecov Report

Merging #377 (7e1fb0e) into 2022.3.x (eca14bf) will increase coverage by 0.15%.
The diff coverage is 39.12%.

@@             Coverage Diff              @@
##           2022.3.x     #377      +/-   ##
============================================
+ Coverage     43.26%   43.42%   +0.15%
============================================
  Files           766      773       +7
  Lines         75548    76775    +1227
============================================
+ Hits          32687    33337     +650
- Misses        38221    38725     +504
- Partials       4640     4713      +73

Impacted Files
Coverage Δ

automation/service/session.go
50.00% <0.00%> (-0.23%)
:arrow_down:

compose/rest/request/chart.go
15.43% <0.00%> (-2.98%)
:arrow_down:

compose/service/locale.gen.go
5.36% <0.00%> (-0.52%)
:arrow_down:

compose/service/locale.go
0.00% <0.00%> (ø)

federation/service/service.go
54.00% <ø> (ø)

pkg/api/server/handlers.go
0.00% <0.00%> (ø)

pkg/auth/token_issuer.go
50.34% <0.00%> (-1.05%)
:arrow_down:

pkg/envoy/builder.go
86.53% <0.00%> (-3.47%)
:arrow_down:

pkg/envoy/resource/api_gateway.go
57.57% <ø> (ø)

pkg/envoy/resource/types.go
73.00% <0.00%> (-9.96%)
:arrow_down:

... and 129 more

Continue to review full report at Codecov.

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


Refactor with some tools

These tools are used with gometalinter.
Notice that gofmt fixes codes automatically but other tools alert but don't fix codes.
I have fixed codes manually according to alerts.

gofmt
go vet
gosimple
misspel
nakedret
unconvert

This looks like all valid and welcome cleanup to me. LGTM.

@suzuki-shunsuke sure thing, TBH I squash merge for the same reason you don't want me to. easier to revert a single commit than go through and figure out which individual one causes it.
Many people don't put effort into the individual commits, as a result you'll get commits that can't be reverted cleanly etc. So its easier on my end to just squash.

@james-lawrence
Thank you for your reply.
I see.


filebot: 5.1.4 -> 5.1.5

Description of changes
Supersedes #336827
Updates filebot to 5.1.5, migrates it to pkgs/by-name & reformats the file with nixfmt-rfc-style.
Changelog: https://www.filebot.net/forums/viewtopic.php?t=13578
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Is there any specific need for a backport? We don't usually backport unless there is a good reason to do so.

According to CONTRIBUTING.md backwards-compatible changes are allowed to be backported and among the specific examples it lists:

✔ Package version updates

✔ Patch versions with fixes
✔ Minor versions with new functionality, but no breaking changes

They are indeed permitted but the question is whether it makes sense to do so.
For unstable, the mantra is to get all packages to the newest stable upstream releases on a best-effort basis with no regard for timing other than inter-compatibility.
In stable release however, you generally keep everything as is and only backport important fixes or updates that must be made available to stable users or else they will have a really bad time (i.e. security, critical bugfixes). This is realised through an explicit branch-off.
My question is whether you want to backport this because it fixes an important bug that users would definitely want to see fixed quickly (i.e. a critical bug) or whether it's merely for the sake of keeping stable up to date with the newest small fixes and features. The latter contradicts the goal of the stable release; IMV it's supposed to be the unchanged initial state released in May with the minimal set of updates that are necessary.

@Atemu thank you for clarifying.
My only reason for backporting this PR was to include the new features & improvements and there are no security fixes mentioned in the changelog. Therefore I'm good with not backporting it.
I'll keep this in mind for future PRs.


installed via npm is not working

Hi @Alperengozum
i used your packege and i found if you download the 0.2.1
then it show the Error: Cannot find native module 'ExpoAlarm'
you need to download the 0.2.0 version for perfect use
can you add .showAlarms();
return a array of all alarms.

Hi @biplabroy-1,
I just tested 0.2.1 with my open source project, and it works fine. Sleepwell Github URL
Also, there is no difference between 0.2.0 and 0.2.1; it was just a fix for the README.md issue for the NPM package.
Could you test with remove node_modules, remove existing app on emulator, and fresh install it?

can you add .showAlarms();
return a array of all alarms.

Unfortunately, Android AlarmClock does not provide us with a list of all alarms.
It only shows alarms and the reason that I implemented it like that.
Android AlarmClock Reference


:lipstick: Update bit manipulation style

Further explains how bit modify should be used in the code base, such as
preferring to use the APIs with bit mask template arguments to ensure
the call knows the bit mask at compile time.
Also provides a carve out for concatenating bits together. In the case
where the developer simply needs to combine a set of bits together with
an OR operation, these are simple enough to read and understand and do
not require the bit APIs to be used.
Resolves https://github.com/libhal/libhal.github.io/issues/53

note from the conversation in person about updating the friend classes and function section:
Friend functions and classes should be placed in the section that matches the access modifier of their declaration. It has no effect on the compiler but is there to have consistency of where to put friend functions and classes.

Thanks for the input @MichaelYKersey


[Bug]: TG anything above 1 outputs lots more KW.

Contact Details
No response
VRM portal ID
d41243cd7f0b
Country / region
Sweden - SE3 (se-3)
B max
20
TB max
5
FB max
9
TG max
2
FG max
11
Battery costs
0.0001
Buy price
(p+0.06+0.00)*1.25
Sell price
(p-0.00+0.01)*1.25
feed-in possible
yes
feed-in possible
yes
Version
0.1.5
What happened?
When setting TG variable to anything other than 1 the systems starts to feed in to grid over 3 Kw totally.
Tried setting TG to 2, 3, 1.5 and nothing worked, it was always selling more to grid than allowed. When setting it back to 1 it worked, now its steady at -640 W, even though the setpoint is -1000 W.
3 Phase install
Relevant log output
No response
Screenshots
![DESCRIPTION](LINK.png)

Can you try running the latest candidate Venus software (3.20~4) and check if that resolves this?

A sorry, didn't think of that - I even read the release notes for 3.20~4 :-(.
Will try, the next window for selling is currently tomorrow during the day so cant verify until then.

One question, should the value under ESS in the Cerbo change when the TG max is changed? Currently it seems fixed to -1000 but that might be my Homey control loop that left it like that when I disabled that for testing D-ESS.

3.20~4 fixed the problem so this can be closed.


feature: 作业平台调用支持业务集 (closed #493)

Codecov Report

Merging #495 (a2d192e) into V2.2.1-rc (561387e) will decrease coverage by 0.00%.
The diff coverage is 87.50%.

@@              Coverage Diff              @@
##           V2.2.1-rc     #495      +/-   ##
=============================================
- Coverage      70.64%   70.64%   -0.01%
=============================================
  Files            286      286
  Lines          20556    20564       +8
=============================================
+ Hits           14522    14527       +5
- Misses          6034     6037       +3

Impacted Files
Coverage Δ

apps/backend/components/collections/job.py
90.43% <ø> (ø)

apps/backend/components/collections/plugin.py
81.87% <ø> (ø)

apps/node_man/periodic_tasks/update_proxy_file.py
91.58% <ø> (ø)

apps/node_man/constants.py
98.20% <83.33%> (-0.33%)
:arrow_down:

apps/backend/api/job.py
81.81% <100.00%> (+0.23%)
:arrow_up:

apps/node_man/periodic_tasks/utils.py
34.04% <100.00%> (+1.43%)
:arrow_up:

apps/backend/subscription/steps/plugin.py
48.63% <0.00%> (-0.64%)
:arrow_down:

apps/backend/views.py
83.23% <0.00%> (+0.57%)
:arrow_up:

Continue to review full report at Codecov.

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


[Request] Ability to Sort A->Z

Ability to sort IP configs alphabetically

Hi friend,
I have in mind to add new features to the program. but I can't find the time right now. If you are interested in programming, you can fork the source codes from the link. https://github.com/esen2202/SNlibrary-Projects ,
I plan to add new features in the near future.
*Multiple IP adding, pinging, sorting include


Package request for postgis support

Please add postgis, postgresql-9.3-postgis-2.1, postgresql-9.3-postgis-scripts.
Thank you.

do you need them for a specific distro ?

Ubuntu 14.04 LTS.
Thank you.

hi they are already available

I'm sorry. It was my fault. Now it's works.


[no-duplicates] regression: normal and inline-type-specifier imports are not detected

Input:
import { A } from "./mod";
import { type B } from "./mod";

Output:
// 2.26
import { A, type B } from "./mod";

// 2.27
import { A } from "./mod";
import { type B } from "./mod";

Duplicate of #2675; there's no need for more than one issue to cover no-duplicates with inline type specifiers.


[RabbitMQ] Multiple connections consuming one queue

I am trying to setup the monitoring and pushing of config changes to clients on the spring cloud bus (http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html#_push_notifications_and_spring_cloud_bus). I have been able to successfully setup my config server along with a number of other applications. Within my RabbitMQ management UI I can see that there is multiple connections to RabbitMQ (one for each application):

As well I can see that the springCloudBus exchange has been setup:

As well a queue is setup for the springCloudBus:

I have used RabbitMQ for couple other projects and something has me a bit confused. From my understanding the cloud bus is meant for applications to send events between each other. I see that is how the exchange has been setup with the "fanout" type. The problem I see is that the exchange is only fanning out the message to the one queue where all 8 consumers are listening. The message then is consumed by one of the connections and the remaining connections don't even know there was a message trying to be broadcast. This is what RabbitMQ classifies as a "Worker Queue" (http://www.rabbitmq.com/tutorials/tutorial-two-java.html). What I would have thought would be setup is more like the "Publish / Subscribe" model (http://www.rabbitmq.com/tutorials/tutorial-three-java.html). This would show up as each application have a temporary queue created and bound to the exchange such that the "fanout" would put a message into each queue and then each application can choose to act on the message or not.
Looking at the application logs for the config service I see that it identified that refresh for "hello-service" and broadcast that event but the logs within the hello-service show no message being received. I do see the message being sent through RabbitMQ as the exchange and queue shows an increment on the number of messages processed.
12/21 15:53:38.13 [APP|0] 2015-12-21 23:53:38.132  INFO 11 --- [nio-8080-exec-2] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring FrameworkServlet 'dispatcherServlet'
12/21 15:53:38.13 [APP|0] 2015-12-21 23:53:38.133  INFO 11 --- [nio-8080-exec-2] o.s.web.servlet.DispatcherServlet        : FrameworkServlet 'dispatcherServlet': initialization started
12/21 15:53:38.16 [APP|0] 2015-12-21 23:53:38.161  INFO 11 --- [nio-8080-exec-2] o.s.web.servlet.DispatcherServlet        : FrameworkServlet 'dispatcherServlet': initialization completed in 28 ms
12/21 15:53:38.23 [APP|0] 2015-12-21 23:53:38.232  INFO 11 --- [nio-8080-exec-2] o.s.c.c.monitor.PropertyPathEndpoint     : Refresh for: hello-service
12/21 15:53:38.24 [APP|0] 2015-12-21 23:53:38.244  INFO 11 --- [nio-8080-exec-2] o.s.i.codec.kryo.CompositeKryoRegistrar  : registering [40, java.io.File] with serializer org.springframework.integration.codec.kryo.FileSerializer
12/21 15:53:38.27 [APP|0] 2015-12-21 23:53:38.271 DEBUG 11 --- [nio-8080-exec-2] o.s.a.r.c.CachingConnectionFactory       : Creating cached Rabbit Channel from AMQChannel(amqp://sclark@<AWS public IP>:5672/,2)
12/21 15:53:38.27 [APP|0] 2015-12-21 23:53:38.271 DEBUG 11 --- [nio-8080-exec-2] o.s.amqp.rabbit.core.RabbitTemplate      : Executing callback on RabbitMQ Channel: Cached Rabbit Channel: AMQChannel(amqp://sclark@<AWS public IP>:5672/,2)
12/21 15:53:38.27 [APP|0] 2015-12-21 23:53:38.272 DEBUG 11 --- [nio-8080-exec-2] o.s.amqp.rabbit.core.RabbitTemplate      : Publishing message on exchange [binder.topic.springCloudBus], routingKey = [null]
12/21 15:53:38.27 [APP|0] 2015-12-21 23:53:38.275 TRACE 11 --- [nio-8080-exec-2] o.s.a.r.c.CachingConnectionFactory       : Returning cached Channel: AMQChannel(amqp://sclark@<AWS public IP>:5672/,2)
12/21 15:53:38.68 [APP|0] 2015-12-21 23:53:38.689  INFO 11 --- [nio-8080-exec-2] nfigurationApplicationContextInitializer : Adding cloud service auto-reconfiguration to ApplicationContext
12/21 15:53:38.69 [APP|0] 2015-12-21 23:53:38.690  INFO 11 --- [nio-8080-exec-2] o.s.boot.SpringApplication               : Starting application on 8g3egh059ji with PID 11 (/home/vcap/app/lib/spring-boot-1.3.0.RELEASE.jar started by vcap in /home/vcap/app)
12/21 15:53:38.69 [APP|0] 2015-12-21 23:53:38.690  INFO 11 --- [nio-8080-exec-2] o.s.boot.SpringApplication               : The following profiles are active: lattice-aws,cloud
12/21 15:53:38.71 [APP|0] 2015-12-21 23:53:38.714  INFO 11 --- [nio-8080-exec-2] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@1c7f3c12: startup date [Mon Dec 21 23:53:38 UTC 2015]; root of context hierarchy
12/21 15:53:38.78 [APP|0] 2015-12-21 23:53:38.785  INFO 11 --- [nio-8080-exec-2] urceCloudServiceBeanFactoryPostProcessor : Auto-reconfiguring beans of type javax.sql.DataSource
12/21 15:53:38.78 [APP|0] 2015-12-21 23:53:38.789  INFO 11 --- [nio-8080-exec-2] urceCloudServiceBeanFactoryPostProcessor : No beans of type javax.sql.DataSource found. Skipping auto-reconfiguration.
12/21 15:53:38.79 [APP|0] 2015-12-21 23:53:38.793  INFO 11 --- [nio-8080-exec-2] bbitCloudServiceBeanFactoryPostProcessor : Auto-reconfiguring beans of type org.springframework.amqp.rabbit.connection.ConnectionFactory
12/21 15:53:38.79 [APP|0] 2015-12-21 23:53:38.795  INFO 11 --- [nio-8080-exec-2] bbitCloudServiceBeanFactoryPostProcessor : No beans of type org.springframework.amqp.rabbit.connection.ConnectionFactory found. Skipping auto-reconfiguration.
12/21 15:53:38.80 [APP|0] 2015-12-21 23:53:38.801  INFO 11 --- [nio-8080-exec-2] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
12/21 15:53:38.83 [APP|0] 2015-12-21 23:53:38.838  INFO 11 --- [nio-8080-exec-2] trationDelegate$BeanPostProcessorChecker : Bean 'configurationPropertiesRebinderAutoConfiguration' of type [class org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$58db619] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
12/21 15:53:38.96 [APP|0] 2015-12-21 23:53:38.965  INFO 11 --- [nio-8080-exec-2] o.s.boot.SpringApplication               : Started application in 0.65 seconds (JVM running for 28.945)
12/21 15:53:39.38 [APP|0] 2015-12-21 23:53:39.387  INFO 11 --- [nio-8080-exec-2] nfigurationApplicationContextInitializer : Adding cloud service auto-reconfiguration to ApplicationContext
12/21 15:53:39.38 [APP|0] 2015-12-21 23:53:39.388  INFO 11 --- [nio-8080-exec-2] o.s.boot.SpringApplication               : The following profiles are active: lattice-aws,cloud
12/21 15:53:39.39 [APP|0] 2015-12-21 23:53:39.396  INFO 11 --- [nio-8080-exec-2] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@288d95a1: startup date [Mon Dec 21 23:53:39 UTC 2015]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext@1c7f3c12
12/21 15:53:39.41 [APP|0] 2015-12-21 23:53:39.412  INFO 11 --- [nio-8080-exec-2] urceCloudServiceBeanFactoryPostProcessor : Auto-reconfiguring beans of type javax.sql.DataSource
12/21 15:53:39.41 [APP|0] 2015-12-21 23:53:39.416  INFO 11 --- [nio-8080-exec-2] urceCloudServiceBeanFactoryPostProcessor : No beans of type javax.sql.DataSource found. Skipping auto-reconfiguration.
12/21 15:53:39.41 [APP|0] 2015-12-21 23:53:39.419  INFO 11 --- [nio-8080-exec-2] bbitCloudServiceBeanFactoryPostProcessor : Auto-reconfiguring beans of type org.springframework.amqp.rabbit.connection.ConnectionFactory
12/21 15:53:39.42 [APP|0] 2015-12-21 23:53:39.420  INFO 11 --- [nio-8080-exec-2] bbitCloudServiceBeanFactoryPostProcessor : No beans of type org.springframework.amqp.rabbit.connection.ConnectionFactory found. Skipping auto-reconfiguration.
12/21 15:53:39.42 [APP|0] 2015-12-21 23:53:39.423  INFO 11 --- [nio-8080-exec-2] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
12/21 15:53:39.44 [APP|0] 2015-12-21 23:53:39.443  INFO 11 --- [nio-8080-exec-2] o.s.boot.SpringApplication               : Started application in 1.16 seconds (JVM running for 29.422)
12/21 15:53:39.44 [APP|0] 2015-12-21 23:53:39.444  INFO 11 --- [nio-8080-exec-2] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@288d95a1: startup date [Mon Dec 21 23:53:39 UTC 2015]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext@1c7f3c12
12/21 15:53:39.44 [APP|0] 2015-12-21 23:53:39.446  INFO 11 --- [nio-8080-exec-2] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@1c7f3c12: startup date [Mon Dec 21 23:53:38 UTC 2015]; root of context hierarchy
12/21 15:53:40.88 [APP|0] 2015-12-21 23:53:40.880  INFO 11 --- [nio-8080-exec-2] o.s.c.n.eureka.InstanceInfoFactory       : Setting initial instance status as: STARTING
12/21 15:53:40.91 [APP|0] 2015-12-21 23:53:40.913  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-SERVICE/709924db-f872-4f89-4dbd-4f05b07fb7a5 - deregister  status: 200
12/21 15:53:40.93 [APP|0] 2015-12-21 23:53:40.936  INFO 11 --- [nio-8080-exec-2] c.n.e.EurekaDiscoveryClientConfiguration : Unregistering application config-service with eureka with status DOWN
12/21 15:53:40.95 [APP|0] 2015-12-21 23:53:40.955  INFO 11 --- [nio-8080-exec-2] c.n.d.provider.DiscoveryJerseyProvider   : Using encoding codec LegacyJacksonJson
12/21 15:53:40.95 [APP|0] 2015-12-21 23:53:40.955  INFO 11 --- [nio-8080-exec-2] c.n.d.provider.DiscoveryJerseyProvider   : Using decoding codec LegacyJacksonJson
12/21 15:53:41.26 [APP|0] 2015-12-21 23:53:41.262  INFO 11 --- [nio-8080-exec-2] c.n.d.provider.DiscoveryJerseyProvider   : Using decoding codec LegacyJacksonJson
12/21 15:53:41.26 [APP|0] 2015-12-21 23:53:41.262  INFO 11 --- [nio-8080-exec-2] c.n.d.provider.DiscoveryJerseyProvider   : Using encoding codec LegacyJacksonJson
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.391  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Single vip registry refresh property : null
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.391  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Disable delta property : false
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.391  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Force full registry fetch : false
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.391  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Application is null : false
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.391  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Registered Applications size is zero : true
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.392  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Getting all instance registry info from the eureka server
12/21 15:53:41.39 [APP|0] 2015-12-21 23:53:41.392  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Application version is -1: true
12/21 15:53:41.40 [APP|0] 2015-12-21 23:53:41.401  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : The response status is 200
12/21 15:53:41.40 [APP|0] 2015-12-21 23:53:41.404  INFO 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Starting heartbeat executor: renew interval is: 30
12/21 15:53:41.40 [APP|0] 2015-12-21 23:53:41.404  INFO 11 --- [nio-8080-exec-2] c.n.discovery.InstanceInfoReplicator     : InstanceInfoReplicator onDemand update allowed rate per min is 4
12/21 15:53:41.40 [APP|0] 2015-12-21 23:53:41.406  INFO 11 --- [nio-8080-exec-2] c.n.e.EurekaDiscoveryClientConfiguration : Registering application config-service with eureka with status UP
12/21 15:53:41.40 [APP|0] 2015-12-21 23:53:41.407  WARN 11 --- [nio-8080-exec-2] com.netflix.discovery.DiscoveryClient    : Saw local status change event StatusChangeEvent [current=UP, previous=DOWN]
12/21 15:53:41.40 [APP|0] 2015-12-21 23:53:41.408  INFO 11 --- [nio-8080-exec-2] o.s.cloud.bus.event.RefreshListener      : Received remote refresh request. Keys refreshed []
12/21 15:53:41.42 [APP|0] 2015-12-21 23:53:41.421  INFO 11 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-SERVICE/709924db-f872-4f89-4dbd-4f05b07fb7a5: registering service...
12/21 15:53:41.44 [APP|0] 2015-12-21 23:53:41.449  INFO 11 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-SERVICE/709924db-f872-4f89-4dbd-4f05b07fb7a5 - registration status: 204
12/21 15:53:41.32 [RTR|0] config-service.<AWS public IP>.xip.io - [21/12/2015:23:53:37 +0000] "POST /monitor HTTP/1.1" 200 18 17 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36" <IP_ADDRESS>:59959 x_forwarded_for:"-" x_forwarded_proto:"-" vcap_request_id:85a5b087-f50a-403d-437e-5f8ed98af136 response_time:3.358991989 app_id:config-service

12/21 15:53:42.01 [APP|0] 2015-12-21 23:53:42.016  INFO 11 --- [nio-8080-exec-3] o.s.boot.SpringApplication               : Starting application on 8g3egh059ji with PID 11 (/home/vcap/app/lib/spring-boot-1.3.0.RELEASE.jar started by vcap in /home/vcap/app)
12/21 15:53:42.01 [APP|0] 2015-12-21 23:53:42.016  INFO 11 --- [nio-8080-exec-3] o.s.boot.SpringApplication               : The following profiles are active: lattice-aws,cloud
12/21 15:53:42.02 [APP|0] 2015-12-21 23:53:42.024  INFO 11 --- [nio-8080-exec-3] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@23d7e3ae: startup date [Mon Dec 21 23:53:42 UTC 2015]; root of context hierarchy
12/21 15:53:42.05 [APP|0] 2015-12-21 23:53:42.052  INFO 11 --- [nio-8080-exec-3] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
12/21 15:53:42.06 [APP|0] 2015-12-21 23:53:42.062  INFO 11 --- [nio-8080-exec-3] o.s.boot.SpringApplication               : Started application in 0.695 seconds (JVM running for 32.041)
12/21 15:53:42.06 [APP|0] 2015-12-21 23:53:42.064  INFO 11 --- [nio-8080-exec-3] o.s.c.c.s.e.NativeEnvironmentRepository  : Adding property source: file:/home/vcap/app/C:/Users/sclark/AppData/Local/Temp/config/application.yml#lattice-aws
12/21 15:53:42.06 [APP|0] 2015-12-21 23:53:42.064  INFO 11 --- [nio-8080-exec-3] o.s.c.c.s.e.NativeEnvironmentRepository  : Adding property source: file:/home/vcap/app/C:/Users/sclark/AppData/Local/Temp/config/hello-service.yml
12/21 15:53:42.06 [APP|0] 2015-12-21 23:53:42.064  INFO 11 --- [nio-8080-exec-3] o.s.c.c.s.e.NativeEnvironmentRepository  : Adding property source: file:/home/vcap/app/C:/Users/sclark/AppData/Local/Temp/config/application.yml
12/21 15:53:42.06 [APP|0] 2015-12-21 23:53:42.065  INFO 11 --- [nio-8080-exec-3] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@23d7e3ae: startup date [Mon Dec 21 23:53:42 UTC 2015]; root of context hierarchy

Based on this I am currently stuck on trying to get the config server to broadcast out any changes. If there is any additional logging that you would like me to include to give more details then please let me know and I can provide them.

I believe this is a duplicate of #21 which will be fixed in M4 which should come shortly.

Thanks for that link @spencergibb. I had tried searching through past issues to see if this has been addressed. I will monitor that issue and see if it resolves this issue as well.

I have just verified that M4 does indeed have the fix. I now see a queue per instance of the application and a binding to the exchange, that is now a topic exchange, and the routing key is # which allows all queues to get all messages. I tested that when I trigger a config change on the config-server that the appropriate service gets the message and restarts its context.


[1.9] Stones of creation during crafting give zero item then disapear

Minecraft version? RCrops version? You gotta give me some information.

Latest Forge and Resourceful Crops for 1.9.


scanner: migrate to quick-xml

@vberger Thank you for this - it will help wgpu clean up our cargo audit output once we get a new wayland-scanner release, and a winit release following that.
When is the next wayland-scanner crate release expected?

We are on the final track to release 0.30, you can track what's remaining here: https://github.com/Smithay/wayland-rs/milestone/5


Ability to move Windows Terminal by garbing an empty area of the tab region.

Description of the new feature/enhancement
Allow Windows Terminal to be moved across screen easier by allowing more grab points.  Right now only clicking and dragging on a small section of the top bar allows you to move the window.  I keep on trying to click and drag on the empty portion of the tab selection to move the window.  This section is from far right most open tab to the + sign used to open a new terminal.
Proposed technical implementation details (optional)
N\A

Please make sure to search before filing a new issue.


support uploading of advanced column types

[ ] date
[ ] boolean
[ ] array types:
[ ] set
[ ] boxplot
[ ] map types
[ ] ordinal
[ ] hierarchy

wontifx


Missing dist/cli.js from create-waku

It seems the last release is broken.

Thanks for reporting.
Seems like I broke something around build.
See #167

create-waku v0.6.2 is published.


Star icon has gray background

Still happening with 5.0.5 build 55, released Oct 29.

iPad running 14.2:

no issue

iPhone running 14.1:

Background shows when app is launched in Light Mode.
Background doesn’t show when app is launched in Dark Mode and is then switched to Light Mode.

Weird.


Fix data-frame-to-json test

This test fails, though the data-frame-to-json function can be shown to work, both at the REPL and by reading in and writing out a JSON file and then diff'ing the two. I suspect something with clunit and the internal quotes in the strings.

These functions have been moved to the plot system


@comment.inner not working as expected

Describe the bug
When using the @comment.inner text object, nothing gets selected.
@comment.outer works fine.
To Reproduce

Add this to your treesitter config.

            textobjects = {
                select = {
                    enable = true,
                    lookahead = true,
                    include_surrounding_whitespace = true,
                    keymaps = {
                        ["ac"] =<EMAIL_ADDRESS>                        ["ic"] =<EMAIL_ADDRESS>                    },
                },
            },

open cpp file
go to line with comment "// ..."
use command "cic"
nothing happens

Expected behavior
Line in beginning:
// Change<cursor> this comment
Line after cic:
// <cursor>
Output of :checkhealth nvim-treesitter
nvim-treesitter: require("nvim-treesitter.health").check()

Installation ~
- OK `tree-sitter` found 0.22.5 (parser generator, only needed for :TSInstallFromGrammar)
- OK `node` found v20.12.2 (only needed for :TSInstallFromGrammar)
- OK `git` executable found.
- OK `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
  Version: cc (GCC) 14.1.1 20240522 (Red Hat 14.1.1-4)
- OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

OS Info:
{
  machine = "x86_64",
  release = "6.8.9-300.fc40.x86_64",
  sysname = "Linux",
  version = "#1 SMP PREEMPT_DYNAMIC Thu May  2 18:59:06 UTC 2024"
} ~

Parser/Features         H L F I J
  - bash                ✓ ✓ ✓ . ✓
  - c                   ✓ ✓ ✓ ✓ ✓
  - cmake               ✓ . ✓ ✓ .
  - cpp                 ✓ ✓ ✓ ✓ ✓
  - csv                 ✓ . . . .
  - gitignore           ✓ . . . .
  - glsl                ✓ ✓ ✓ ✓ ✓
  - html                ✓ ✓ ✓ ✓ ✓
  - lua                 ✓ ✓ ✓ ✓ ✓
  - markdown            ✓ . ✓ ✓ ✓
  - python              ✓ ✓ ✓ ✓ ✓
  - rust                ✓ ✓ ✓ ✓ ✓
  - vim                 ✓ ✓ ✓ . ✓
  - vimdoc              ✓ . . . ✓
  - yaml                ✓ ✓ ✓ ✓ ✓

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang} ~

Output of nvim --version
NVIM v0.10.0
Build type: RelWithDebInfo
LuaJIT 2.1.1707061634
Run "nvim -V1 -v" for more info

Additional context
@comment.outer works fine and like expected:
Line in beginning:
// Change<cursor> this comment
Line after cac:
<cursor>

This is a limitation with the parser, right now block and line comments are parsed as the same node, and there is no distinction exposed between // and comment content

@comment.inner is just not defined for C and it can be added for more languages.
Currently the implementation is simple without a comment parser. It selects comment.outer with an offset.


type issue on  "@nuxtseo/module": "^2.0.0-beta.44",

Describe the bug

seems to be used by the og image component
No response

Operating System: Darwin
Node Version:     v18.10.0
Nuxt Version:     3.8.1
CLI Version:      3.9.1
Nitro Version:    2.7.2
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      modules, site, css, turnstile, sitemap, robots, ogImage, schemaOrg, linkChecker, head, routeRules, typescript, sourcemap, devServer, htmlValidator, image, runtimeConfig, nitro, appConfig, ignore, hooks, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

No response

The module doesn't use strict dependency versions so you could have fixed this by removing your lock file + node_modules and re-installing.
I've bumped the dependencies either way though so should be fixed in latest version.


Release version 2.3.0

This is a component issue for 2.3.0.
Coming from opensearch-build#2447. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue

This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on 2.x branch to 2.3.0 for Min/Core, and <IP_ADDRESS> for components. Otherwise, keep the version number unchanged for both.

Preparation

[x] Assign this issue to a release owner.
[x] Finalize scope and feature set and update the Public Roadmap.
[x] All the tasks in this issue have been reviewed by the release owner.
[x] Create, update, triage and label all features and issues targeted for this release with v2.3.0.

CI/CD

[x] All code changes for 2.3.0 are complete.
[x] Ensure working and passing CI.
[x] Check that this repo is included in the distribution manifest.

Pre-Release

[x] Update to the 2.3 release branch in the distribution manifest.
[x] Increment the version on the parent branch to the next development iteration.
[x] Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
[x] Confirm that all changes for 2.3.0 have been merged.
[x] Add this repo to the manifest for the next developer iteration.

Release Testing

[ ] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
[ ] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
[ ] Sanity Testing: Sanity testing and fixing of critical issues found.
[ ] File issues for all intermittent test failures.

Release

[ ] Complete documentation.
[ ] Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

[ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
[ ] Add this repo to the manifest of the next eventual security patch version.
[ ] Suggest improvements to this template.
[ ] Conduct a retrospective, and publish its results.

Job scheduler updated in manifest from 2.x to 2.3 as part of https://github.com/opensearch-project/opensearch-build/pull/2566

Job scheduler version bump happened as part of https://github.com/opensearch-project/job-scheduler/commit/df154b89d4542528dd1b2775a86768713152260f

Proceeding with release notes

On 2.x version bump happened on Aug 2 https://github.com/opensearch-project/job-scheduler/commit/6d298ff5f442b769f8d7de053f676006986c83f1

Performance number comparison report updated on parent issue
https://github.com/opensearch-project/opensearch-build/issues/2447#issuecomment-1244303910

I will handle this issue.


Create a tekton task out of pde2e-builder image for extended portability on openshift pipelines

PR https://github.com/odockal/pde2e-builder/pull/2


Overhaul API and add cross platform hole punching

Closes #1.

@mafintosh This is ready for review.

Looks amazing!