Mark Logging.Abstractions as CLSCompliant

Only change is to mark Logging.Abstractions assembly as CLSCompliant.
Background:
We have some .NET Framework projects that we want to port to .NET Standard. All these projects are marked as CLSCompliant. So this change would help a lot to make a step-by-step migration much easier.
This resolve issue #500

For the reasons mentioned in the issue, plus https://github.com/aspnet/Home/issues/2689#issuecomment-354693946, we are not planning to mark these types as CLSCompliant.


trim-galore/fastqc crash, error 0

Hello there,
I'm trying to run the nf-core/rnaseq pipeline on my local machine but it seems to keep crashing after read trimming with trim-galore when trying to run fastqc on trimmed reads.
I'm not sure what causes the issue and I've pasted the output of pipeline_report.txt below.
I would appreciate any help how to fix it.
Many thanks in advance!
----------------------------------------------------
                                        ,--./,-.
        ___     __   __   __   ___     /,-._.--~\
  |\ | |__  __ /  ` /  \ |__) |__         }  {
  | \| |       \__, \__/ |  \ |___     \`-._,-`-,
                                        `._,._,'
  nf-core/rnaseq v1.4.2
----------------------------------------------------

Run Name: awesome_gates

####################################################
## nf-core/rnaseq execution completed unsuccessfully! ##
####################################################
The exit status of the task that caused the workflow execution to fail was: 0.
The full error message was:

Error executing process > 'trim_galore (FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70)'

Caused by:
  Missing output file(s) `*_fastqc.{zip,html}` expected by process `trim_galore (FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70)`

Command executed:

  trim_galore --paired --fastqc --gzip      FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1.fq.gz FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2.fq.gz

Command exit status:
  0

Command output:
  (empty)

Command error:
  81	4	0.7	1	0 4
  82	3	0.7	1	1 2
  83	8	0.7	1	1 7
  84	3	0.7	1	2 1
  85	7	0.7	1	3 4
  86	2	0.7	1	1 1
  87	1	0.7	1	0 1
  88	1	0.7	1	0 1
  89	1	0.7	1	0 1
  91	2	0.7	1	0 2
  92	4	0.7	1	3 1
  94	1	0.7	1	0 1
  95	2	0.7	1	1 1
  96	2	0.7	1	0 2
  97	3	0.7	1	0 3
  98	5	0.7	1	1 4
  99	26	0.7	1	2 24
  100	116	0.7	1	25 91

  RUN STATISTICS FOR INPUT FILE: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2.fq.gz
  =============================================
  50284169 sequences processed in total
  The length threshold of paired-end sequences gets evaluated later on (in the validation step)

  Validate paired-end files FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz
  file_1: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz, file_2: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz

  >>>>> Now validing the length of the 2 paired-end infiles: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz <<<<<
  Writing validated paired-end read 1 reads to FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_val_1.fq.gz
  Writing validated paired-end read 2 reads to FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_val_2.fq.gz

  Total number of sequences analysed: 50284169

  Number of sequence pairs removed because at least one read was shorter than the length cutoff (20 bp): 225 (0.00%)

    >>> Now running FastQC on the validated data FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_val_1.fq.gz<<<

  Error: LinkageError occurred while loading main class uk.ac.babraham.FastQC.FastQCApplication
  	java.lang.ExceptionInInitializerError: null

    >>> Now running FastQC on the validated data FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_val_2.fq.gz<<<

  Error: LinkageError occurred while loading main class uk.ac.babraham.FastQC.FastQCApplication
  	java.lang.ExceptionInInitializerError: null
  Deleting both intermediate output files FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz

  ====================================================================================================

Work dir:
  /Users/janstrauss/Desktop/Sync_Folder/RNA-seq_data/RNA-seq_Plasmodium_/RNAseqdata_7G8_project/work/3c/7653e3b655da54a979085f3ae583e2

Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named `.command.sh`

####################################################
## nf-core/rnaseq execution completed unsuccessfully! ##
####################################################
The exit status of the task that caused the workflow execution to fail was: 0.
The full error message was:

Error executing process > 'trim_galore (FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70)'

Caused by:
  Missing output file(s) `*_fastqc.{zip,html}` expected by process `trim_galore (FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70)`

Command executed:

  trim_galore --paired --fastqc --gzip      FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1.fq.gz FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2.fq.gz

Command exit status:
  0

Command output:
  (empty)

Command error:
  81	4	0.7	1	0 4
  82	3	0.7	1	1 2
  83	8	0.7	1	1 7
  84	3	0.7	1	2 1
  85	7	0.7	1	3 4
  86	2	0.7	1	1 1
  87	1	0.7	1	0 1
  88	1	0.7	1	0 1
  89	1	0.7	1	0 1
  91	2	0.7	1	0 2
  92	4	0.7	1	3 1
  94	1	0.7	1	0 1
  95	2	0.7	1	1 1
  96	2	0.7	1	0 2
  97	3	0.7	1	0 3
  98	5	0.7	1	1 4
  99	26	0.7	1	2 24
  100	116	0.7	1	25 91

  RUN STATISTICS FOR INPUT FILE: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2.fq.gz
  =============================================
  50284169 sequences processed in total
  The length threshold of paired-end sequences gets evaluated later on (in the validation step)

  Validate paired-end files FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz
  file_1: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz, file_2: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz

  >>>>> Now validing the length of the 2 paired-end infiles: FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz <<<<<
  Writing validated paired-end read 1 reads to FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_val_1.fq.gz
  Writing validated paired-end read 2 reads to FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_val_2.fq.gz

  Total number of sequences analysed: 50284169

  Number of sequence pairs removed because at least one read was shorter than the length cutoff (20 bp): 225 (0.00%)

    >>> Now running FastQC on the validated data FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_val_1.fq.gz<<<

  Error: LinkageError occurred while loading main class uk.ac.babraham.FastQC.FastQCApplication
  	java.lang.ExceptionInInitializerError: null

    >>> Now running FastQC on the validated data FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_val_2.fq.gz<<<

  Error: LinkageError occurred while loading main class uk.ac.babraham.FastQC.FastQCApplication
  	java.lang.ExceptionInInitializerError: null
  Deleting both intermediate output files FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz

  ====================================================================================================

Work dir:
  /Users/janstrauss/Desktop/Sync_Folder/RNA-seq_data/RNA-seq_Plasmodium_/RNAseqdata_7G8_project/work/3c/7653e3b655da54a979085f3ae583e2

Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named `.command.sh`

The workflow was completed at 2019-11-04T15:41:23.775903+01:00 (duration: 1h 51s)

The command used to launch the workflow was as follows:

  nextflow run nf-core/rnaseq -profile docker --reads 'Rohdaten/volunteer_samples/M1-013/*{1,2}.fq.gz' --reverseStranded --fasta 'https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/fasta/data/PlasmoDB-45_Pfalciparum7G8_Genome.fasta' --gtf 'https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/gff/data/PlasmoDB-45_Pfalciparum7G8.gff' --gff 'https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/gff/data/PlasmoDB-45_Pfalciparum7G8.gff' --max_memory 8.GB --max_cpus 4

Pipeline Configuration:
-----------------------
 - Pipeline Release: master
 - Run Name: awesome_gates
 - Reads: Rohdaten/volunteer_samples/M1-013/*{1,2}.fq.gz
 - Data Type: Paired-End
 - Strandedness: Reverse
 - Trimming: 5'R1: 0 / 5'R2: 0 / 3'R1: 0 / 3'R2: 0 / NextSeq Trim: 0
 - Aligner: STAR
 - Fasta Ref: https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/fasta/data/PlasmoDB-45_Pfalciparum7G8_Genome.fasta
 - GTF Annotation: https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/gff/data/PlasmoDB-45_Pfalciparum7G8.gff
 - GFF3 Annotation: https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/gff/data/PlasmoDB-45_Pfalciparum7G8.gff
 - Remove Ribosomal RNA: false
 - Biotype GTF field: gene_biotype
 - Save prefs: Ref Genome: No / Trimmed FastQ: No / Alignment intermediates: No
 - Max Resources: 8.GB memory, 4 cpus, 10d time per job
 - Container: docker - nfcore/rnaseq:1.4.2
 - Output dir: ./results
 - Launch dir: /Users/janstrauss/Desktop/Sync_Folder/RNA-seq_data/RNA-seq_Plasmodium_/RNAseqdata_7G8_project
 - Working dir: /Users/janstrauss/Desktop/Sync_Folder/RNA-seq_data/RNA-seq_Plasmodium_/RNAseqdata_7G8_project/work
 - Script dir: /Users/janstrauss/.nextflow/assets/nf-core/rnaseq
 - User: janstrauss
 - Config Profile: docker
 - Date Started: 2019-11-04T14:40:32.743034+01:00
 - Date Completed: 2019-11-04T15:41:23.775903+01:00
 - Pipeline script file path: /Users/janstrauss/.nextflow/assets/nf-core/rnaseq/main.nf
 - Pipeline script hash ID: efd50c97fd77bdc6b6161e3ee76f7ddd
 - Pipeline repository Git URL: https://github.com/nf-core/rnaseq.git
 - Pipeline repository Git Commit: 3b6df9bd104927298fcdf69e97cca7ff1f80527c
 - Pipeline Git branch/tag: master
 - Docker image: nfcore/rnaseq:1.4.2
 - Nextflow Version: 19.10.0
 - Nextflow Build: 5170
 - Nextflow Compile Timestamp: 21-10-2019 15:07 UTC

--
nf-core/rnaseq
https://github.com/nf-core/rnaseq

This looks like the relevant bit:
  Error: LinkageError occurred while loading main class uk.ac.babraham.FastQC.FastQCApplication
  	java.lang.ExceptionInInitializerError: null
  Deleting both intermediate output files FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_1_trimmed.fq.gz and FCHKJJVBBXX_L6_RDWHPLAzarEABFRAA-70_2_trimmed.fq.gz

@s-andrews - have you ever seen this with FastQC before? Nasty error if FastQC then deletes all of the input FastQ files 😆 🙈

Hi @janstrauss1 - how do you run the pipeline?  Can you post the commandline you used here ?

Hi @apeltzer,
I ran the pipeline with the following commandline (as taken from the pipeline_report.txt output above):
  nextflow run nf-core/rnaseq -profile docker --reads 'Rohdaten/volunteer_samples/M1-013/*{1,2}.fq.gz' --reverseStranded --fasta 'https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/fasta/data/PlasmoDB-45_Pfalciparum7G8_Genome.fasta' --gtf 'https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/gff/data/PlasmoDB-45_Pfalciparum7G8.gff' --gff 'https://plasmodb.org/common/downloads/Current_Release/Pfalciparum7G8/gff/data/PlasmoDB-45_Pfalciparum7G8.gff' --max_memory 8.GB --max_cpus 4
P.S.: I'm aware that I'm using a gff file to define --gtf, because I actually think that it is a gtf file

FastQC doesn't ever delete anything - it literally doesn't contain rm anywhere in the code (I know because we got accused of deleting someone's home directory before :-)).  If intermediate files are being deleted then it must be the logic in the pipeline which does that.  FastQC doesn't make any intermediate files - it just streams from the input data and builds in-memory data structures.
I've never come across a linkage error, but from the docs it sounds like it's a problem which comes from having a mix of files compiled at different times in the same codebase.  I'm pretty sure that all of the files we've distributed for FastQC are part of a common compilation block, so has any part of nf-core recompiled the java source?  Could the person running the pipeline have copied in files from somewhere else?

Looks like this is using docker, with the nfcore/rnaseq:1.4.2 image. So shouldn't be anything funky with the FastQC compilation.. 🤔 What's weirder is that this FastQC run was at the end of TrimGalore!, so presumably the first FastQC on the raw files completed successfully..
@janstrauss1 - could you post the terminal logs that you got when running the pipeline please? Or if you don't have them any more, the hidden .nextflow.log file (you'll need to rename it to .txt to attach it to this issue).
Have you ever run this pipeline successfully before? This version or others? Have you ever run any other nf-core pipelines successfully?

@ewels - yes, I can confirm that the first FastQC run completes successfully but it crashes during the trim-galore step.
I've attached the renamed .nextflow.log file here nextflow.txt.
No, unfortunately I have never run this (or other nf-core) pipeline successfully before. I just started to use it and this is my first try.

Hmm. And what do you get if you list your docker containers / images? docker ps -a / docker image ls

for docker ps -a I get
(base) cssbbnitm026:RNAseqdata_7G8_project janstrauss$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                   PORTS               NAMES
0039c7cc8a6e        hello-world         "/hello"            13 days ago         Exited (0) 13 days ago                       sharp_thompson

and for docker image ls
(base) cssbbnitm026:RNAseqdata_7G8_project janstrauss$ docker image ls
REPOSITORY               TAG                 IMAGE ID            CREATED             SIZE
janstrauss1/cheers2019   latest              26d9d9da3688        13 days ago         4.01MB
<none>                   <none>              8cfc8a105e61        13 days ago         356MB
nfcore/rnaseq            1.4.2               cb2f7c99d53e        3 weeks ago         3.27GB
golang                   1.11-alpine         e116d2efa2ab        2 months ago        312MB
hello-world              latest              fce289e99eb9        10 months ago       1.84kB

Interesting.. The Image ID that you have for nfcore/rnaseq:1.4.2 is different to that on docker hub:
683625354fdc - 1.22 GB
DIGEST: sha256: 683625354fdcdefaad1a2710e4ba0517ac5316e47dddd6148aa8d685282a857b
You have cb2f7c99d53e which is 3.27GB.
However, when I pull the image I get the same as you:
$ docker pull nfcore/rnaseq:1.4.2
1.4.2: Pulling from nfcore/rnaseq
c5e155d5a1d1: Already exists
a5eecf513b48: Already exists
a2f1f1a8c0a9: Already exists
f827e546ce31: Already exists
7eb6a47b847d: Already exists
dc2074d8d880: Pull complete
a389bc5a8d18: Pull complete
Digest: sha256:683625354fdcdefaad1a2710e4ba0517ac5316e47dddd6148aa8d685282a857b
Status: Downloaded newer image for nfcore/rnaseq:1.4.2
docker.io/nfcore/rnaseq:1.4.2

$ docker image ls
REPOSITORY                TAG                 IMAGE ID            CREATED             SIZE
nfcore/rnaseq             1.4.2               cb2f7c99d53e        3 weeks ago         3.27GB

So I think that should be fine. And the fact that FastQC runs successfully prior to TrimGalore! + FastQC suggests that it should be fine.
I'm at a loss here. @nf-core/core - anyone have any ideas?
Phil

This looks pretty weird to me :-( And I don't really have an idea either...

heisenbug

Love it :laughing:
Really sounds  a bit like a memory issue then :-(

Hi @janstrauss1 ! Did you manage to get to the bottom of this issue? I suspect the files not being present is a by-product of not having enough memory on your compute to run FastQC in the first place, and so Nextflow sees this as missing output files. Will close for now but feel free to re-open if the problem persists.


Datepicker format not working

I switched month and day and it's not working.

@driskull
We tried switching day, month, date and datepicker was working fine.
But if we use 'mm' for month instead of 'MM' then date picker will not work because 'mm' stands for minutes.
Can you provide the date format where date picker is not working, so we can test and get back to you?
Thanks!!

I'll send one soon. I just tried switching month and day order and it didn't work for me.

Matt

On Feb 17, 2015, at 11:45 PM, CTDisasterManagement <notifications<EMAIL_ADDRESS>wrote:
@driskullhttps://github.com/driskull
We tried switching day, month, date and datepicker was working fine.
But if we use 'mm' for month instead of 'MM' then date picker will not work because 'mm' stands for minutes.
Can you provide the date format where date picker is not working, so we can test and get back to you?
Thanks!!
—
Reply to this email directly or view it on GitHubhttps://github.com/Esri/geoform-template-js/issues/418#issuecomment-74824909.

Verified this is working.

Thanks @driskull


Outdated Files version installed from winget. Unknown Files version installed from msstore

What's the Problem?
Installing Files from winget installs Files <IP_ADDRESS>. Installing Files from msstore installs latest Files, but with unknown Files version information in msstore (not in the Files app)
Solution/Idea

Update Files in winget
Tag proper version in msstore

Alternatives
No idea
Priorities

Capability
Priority

This proposal will allow developers to have better package management in package repositories
Must

Files Version
v2.0.13
Windows Version
Microsoft Windows [Version 10.0.22000.194]
Additional comment
Install log:
PS C:\Users\ayams> winget install files --source winget
Found Files - Preview [Files-Community.Files] Version <IP_ADDRESS>
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.

PS C:\Users\ayams> winget install 9NGHP3DX8HDX --source msstore
Found Files - File Manager for Windows [9NGHP3DX8HDX] Version Unknown
This package is provided through Microsoft Store. winget may need to acquire the package from Microsoft Store on behalf of the current user.
Version: Unknown
Publisher: Yair A
Publisher Support Url<EMAIL_ADDRESS>Description: Files is a powerful and efficient file manager. Its has features like multiple tabs, panes, columns, shell extensions and tags.

Thanks for the report, a PR is currently open in the WinGet repo, just waiting for it to be merged 👍

Maybe could you link the PR here so we can see the progress?

Maybe could you link the PR here so we can see the progress?

https://github.com/microsoft/winget-pkgs/pull/29281

Seems like it's not passing the pipeline https://github.com/microsoft/winget-pkgs/pull/29281#issuecomment-933112787


Mocking GHIssueComment for UnitTests

Hi is there an Example how to mock GHIssueComment everytime I try:
var ghComment = mock(GHIssueComment.class);
when(ghComment.getId()).thenReturn(123L);

I get:
java.lang.NullPointerException: Cannot invoke "java.lang.Long.longValue()" because the return value of "org.mockito.internal.creation.bytebuddy.MockMethodInterceptor$DispatcherDefaultingToRealMethod.interceptSuperCallable(Object, org.mockito.internal.creation.bytebuddy.MockMethodInterceptor, java.lang.reflect.Method, Object[], java.util.concurrent.Callable)" is null

/cc @yrodiere

Personally I gave up on trying to understand why that kind of problems arise. I upgraded to JDK 17+ and it seems to have solved it.

Oh wait, that's a different problem. Probably an inconsequent Mockito setting that result in incorrect default answers... maybe the problem is on our side, maybe it's in your app, I'd have to check.
I'd recommend using this as a workaround:
doReturn(123L).when(ghComment).getId();

Oh wait, that's a different problem. Probably an inconsequent Mockito setting that results in incorrect default answers... maybe the problem is on our side, maybe it's in your app, I'd have to check.
I'd recommend using this as a workaround:
doReturn(123L).when(ghComment).getId();

Doesn't work also:
org.mockito.exceptions.misusing.WrongTypeOfReturnValue:
Long cannot be returned by getId()
getId() should return String

When I use a string I get again:
java.lang.NullPointerException: Cannot invoke "java.lang.Long.longValue()" because the return value of "org.mockito.internal.creation.bytebuddy.MockMethodInterceptor$DispatcherDefaultingToRealMethod.interceptSuperCallable(Object, org.mockito.internal.creation.bytebuddy.MockMethodInterceptor, java.lang.reflect.Method, Object[], java.util.concurrent.Callable)" is null

For more information used JDK (release from SDK MAN):
openjdk 17.0.5 2022-10-18
OpenJDK Runtime Environment GraalVM CE 22.3.0 (build 17.0.5+8-jvmci-22.3-b08)
OpenJDK 64-Bit Server VM GraalVM CE 22.3.0 (build 17.0.5+8-jvmci-22.3-b08, mixed mode, sharing)
installed via: sdk install java 22.3.r17-grl
Maven version from IntelliJ:
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Quarkus version: 2.16.5.Final
Mockito Core: 4.11.0

org.mockito.exceptions.misusing.WrongTypeOfReturnValue: Long cannot be returned by getId() getId() should return String

That's interesting... @gsmet looks like the removal of bridge methods doesn't work as intended, at least not in this case:
https://github.com/quarkiverse/quarkus-github-app/blob/df81e198613e027270b4cf5cd7f0a8e43621adb7/deployment/src/main/java/io/quarkiverse/githubapp/deployment/GitHubAppProcessor.java#L190-L219
getId is annotated with the expected annotations, as far as I can tell, so the bridge methods should have been removed:
https://github.com/hub4j/github-api/blob/61a959bfc4569ebd0b7fe371b0b625199f209c27/src/main/java/org/kohsuke/github/GHObject.java#L138-L141

@kanimaru which version of Quarkus GitHub App are you using?
If you have a reproducer, that would be very welcome.

<quarkus-github-app.version>1.16.0</quarkus-github-app.version>
Meanwhile I stopped writting unit test and started with integrations tests instead.

@kanimaru yes please attach a project as a zip in this issue. You can upload file in comments (see the Attach files... bar just below the comment text field)

Hmmm. There's something fishy, I will have a look.

OK so the issue is that you are testing things completely outside of our test infrastructure so Quarkus isn't even started. Thus the bridge methods from the GitHub API are not removed from the GitHub API and Mockito gets all confused.
You need to write your tests as Quarkus tests and that will install the proper infrastructure. That explains why we didn't have failures in our own tests.
You should have plenty of examples here: https://github.com/quarkusio/quarkus-github-bot/tree/main/src/test/java/io/quarkus/bot/it .

Let me know if that answers your question, my guess it that we can close this issue.

Thanks for your feedback.

BTW, just to be clear, the Mockito issue with GitHub API is not caused by Quarkus. The GitHub API generates bridge methods that have the same parameters but different return types (you cannot write this in your IDE but it's actually valid bytecode) to keep binary backward compatibility with the old versions.
It confuses Mockito and that's why in Quarkus GitHub App, we remove the bridge methods from the bytecode so that Mockito can work as expected.
It comes with the price that you might have to update your applications from time to time when upgrading the GitHub API but it doesn't come up that often.


datagen: failed to generate mapillary testing set

The following command throws an error:
python deeposlandia/datagen.py -D mapillary

It seems that the problem comes from the testing set generation, as the algorithm tries to creates preprocessed version of labelled images (which do not exist for testing set).

Solved by PR #58 . I close.


Feature/transaction sessions

Description

add payload.mongooseConnection
instrument globals, collections, and versions operations with session
instrument globals and collections local API with session
add PayloadRequest.session and instrument operations to use it

Passing session explicitly:
const session = await payload.mongooseConnection.startSession();
await session.withTransaction(() => {
  const user = payload.findById({
    session,
    collection: 'users',
    id: '...',
  });
  payload.update({
    session,
    collection: 'users',
    id: user.id,
    data: {...},
  });
});
await session.endSession();

Passing session implicitly on req is also possible; it will be picked up if not overridden by the explicit session parameter. This allows straightforward transaction-per-request with an Express middleware. I have a plugin ready for release after this is merged.
This 100% needs docs and tests.

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Related

https://github.com/payloadcms/payload/discussions/1487
https://github.com/payloadcms/payload/pull/1527

This work is being taken up in the database adapter work, closing PR.
Transactions will be available in the 2.0 release.


Question: How to use with Rails 6 and Webpacker?

When using Rails 6 with Webpacker for application.js, my attempts to use require the javascript dependencies have failed. Do you think you will unbundle the Javascript and support adding the JS dependencies via yarn?

I got around this adding sprockets back alongside my existing Webpacker setup.

Add //= link_directory ../javascripts .js to app/assets/config/manifest.js
Create app/assets/javascripts/application.js and put the two requires for this gem
Add javascript_include_tag alongside javascript_path_tag in <head>

Sorry for not advertise this gem, but you can achieve this functionality by adding a package
yarn add js-cookie

and create javascript file
// app/javascript/browser_timezone_cookie.js
import Cookies from 'js-cookie'

// https://github.com/kbaum/browser-timezone-rails/blob/master/app/assets/javascripts/browser_timezone_rails/set_time_zone.js.erb
Cookies.set(
 "browser.timezone",
  Intl.DateTimeFormat().resolvedOptions().timeZone,
  {
    expires: 365,
    path: '/'
  }
);

include it in main application pack file
// app/javascript/packs/application.js
import 'browser_timezone_cookie'

and use the cookie in around action in application controller
# app/controllers/application_controller.rb
  prepend_around_action :use_time_zone
  def use_time_zone(&action)
    Time.use_zone(Time.find_zone(cookies['browser.timezone'].presence) || Time.zone, &action)
  end


Update partners and users of Harbor

Coverage increased (+0.006%) to 64.529% when pulling 9af063a5fdd683bc9a14effe5987198d7d8e0692 on ywk253100:180611_partners into 9b5cd7d046575c009108431a6ba82ad9f56f5fed on vmware:master.


We need .gitignore

as title says, some unnecessary files are uploaded

You're right. We do need this feature to ensure our project clear.

solved in #7


The client can handle more than 3 toast messages properly

More than 3 active toast are queued in a waiting room. This can cause a specific toast to fail due to a missing ID (can be fixed with reload but not ideal)


Narrow function unions based on argument count

Search Terms
narrow union type
function arguments
Suggestion
TypeScript could narrow a union of callable types when code inspects the "length" property of the function.
Use Cases
Playing with Express which uses middleware with (up to) 3 arguments for regular handlers, and (exactly) 4 arguments for error handlers. Code on top of this that wants to do something for the different types of handlers usually checks "handler.length" to distinguish error handlers.
Examples
function test(handler: express.RequestHandler | express.ErrorRequestHandler, ...args: any[]) {

  // ignore error handlers
  if (handler.length === 4) { return; }

  ...

  // here, TypeScript could narrow "handler" to "express.RequestHandler", but gives error 2349
  handler(...args);
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

I suppose this is a breaking change, as the length value may disagree with the type:
let f: (a: number) => void = (a: number, b?: string) => { };

console.log(f.length); // 2

let g: (a: number, b: undefined) => void = (a: number) => { };

console.log(g.length); // 1

I suppose this is a breaking change, as the length value may disagree with the type:

Hm, maybe I am too naive with my expectations :)

I suppose this is a breaking change, as the length value may disagree with the type:

Hm, maybe I am too naive with my expectations :)

Duplicate of #18422 (and #20866)


Camera.instance should be async to initialize with real values

Right now the Camera.instance singleton creates an instance of a camera that is initialized using default values. Recently the default camera mode was changed to third person. The problem with that is that not only the camera mode was hardcoded, but also it has race conditions that may only be resolved after the user changes the camera mode leading to possible scene bugs.
The approach for the ECS 7.0.0 is that the camera, input and other singleton elements will be started asynchronously to prevent race conditions.

No longer valid. Camera is an entity now


docs(v2): Move sidebar content to its own page

Motivation
Related to #3893 and #3894.
TOCs or sidebars are extremely important in any docs website.
In the current version, the sidebar info is inside the intro page and the sidebar sections are from H3 and deeper, meaning they do not appear in the right-hand TOC making it difficult to browse and understand.
With this PR, the sidebar info is in its own page. It appears in the sidebar, and the on-page TOC is useful again.
I've touched up the content a little bit to reduce word count, also see the Test plan section below.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Please take a solid look at the Understanding sidebar items section.
Task-oriented docs are generally much better for new users, so I've reworked the titles and description to tell us what each type does immediately, instead of telling us the name of each type first (also helps with SEO).
Let me know if this is correct or if needs improvements, I'll take care of it swiflty.
The rest has only changed a little.

Thanks, that looks like a good idea to me, but will be easier to review if the deploy preview works :)

@ArtFlag there is now a problem in the deploy preview:
https://deploy-preview-3899--docusaurus-2.netlify.app/classic/docs/sidebar

Also, can you comment in this PR the parts of the doc you modified?
As the content is both moved/updated, highlighting the major doc changes would be helpful, but overall it looks good

Thanks for fixing the issues!
I've mostly modified the section about the type property.
The rest of the page has seen some modifications but mostly to reduce word count.
For example, for the shorthand note that you mentioned: we used to give the shorthand first and then explain what the "normal" version is.
I flipped it around because we talk about the side item object in this page, so didactically, we should probably show the non-shorthand version first... which actually shows the sidebar item object 😉
No content has been deleted.

Thanks
Can you fix the git conflict and the admonition mistake so that I can merge this?

It should be fine now.
FYI I couldn't push my docs update because pre-commit thought it was an empty commit. Not sure if this update came from my rebase on master, but if there's a way to fix (ignore docs?) that would be nice 👍

thanks
not sure what you are talking about but that looks fine to merge :)


[AF-1509] Bump zendesk_apps_support to 4.12.4

:v:
/cc @zendesk/vegemite
Peremptory cautionary imperative and cursory preamble
⚠ *** DO NOT MERGE EVEN WITH 2 +1s *** ⚠
This change requires devqa first.
Description
There was a need to bump a dependency in zendesk_apps_support to address a security alert.  This change is to bump zendesk_apps_support in zendesk_apps_tools to make sure that the patched version of zas is being used in zat.
References

JIRA: https://zendesk.atlassian.net/browse/AF-1509
https://github.com/zendesk/zendesk_apps_support/pull/220
https://github.com/zendesk/zendesk_apps_support/compare/f5166cf783b726f0f96a3e6c9972def99312182c...90dbafcf1b8cb9b6fc5f4e14c1143c9b9021e2a8

Risks

Medium: Significant bump of zas in zat.  zas has not been bumped in about a year.  Could cause zat to break in unknown ways due to accumulated changes over said period.

devQA 👍

The following actions have now been taken:

zendesk_apps_tools has been bumped to 2.13.0
zendesk_apps_tools-2.13.0 has been published to RubyGems


V2 - Remote Data example doesn't render correctly.

http://semantic-ui.com/introduction/new.html
Using latest version of Chrome on Windows 8.1

Type into the favourite animal, click an item:

This is a regression in 2.0.1 ugh..

Resolved will patch today.


Added support for disabling of automatic view flag updates

This fixes #225.
My initial tests shows that this is working properly. Let me know if I should make any adjustments.

Thanks!


[TAS parser] Even amount of numbers in movement or angle field is wrongly considered valid

version 6
start now

0>0 0 0 0||||

+50>

is a valid script, when it really shouldn't be.
Only the last pair of numbers will take effect.

Resolved by 64137af. Check if everything's fine and then we can close this.

No idea why this issue remained open for this long. Closing.


Support new programming model

This PR implements the new programming model of Azure Functions.
Tasks

[ ] Update packages
[ ] Update code to support v4 programming model
[ ] Rewrite to use class instead?

Closes #13

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (19a8d76) to head (adf247b).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #27   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           20        20
  Lines          554       556    +2
  Branches        60        58    -2
=========================================
+ Hits           554       556    +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Metadata editing button not present for raster resource types for new landing page layout

Testing on alpha I am unable to edit a raster resource type due to the edit button not being present on the landing page

@dtarb Do you mean you tested it on dev since raster resource type is not present on alpha yet? I am able to see edit button for raster resource type and able to edit it as expected. Can you elaborate a bit on how I can reproduce the issue you are seeing as I cannot reproduce the problem?

@dtarb Just realized you might have tested it on sandbox since the permissions for raster resource type have not been added for HydroShare Author group on sandbox yet. If this is indeed the case, you can test on sandbox again. It should work now after I assigned these raster resource type specific permissions to the group.

Yes I tested on sandbox (sorry for the slip).  It is working on sandbox now.

We are still waiting for  a REST API to set resource-specific metadata, SWATModel Instance for us. Is it possible to know the current status?


jlab app server installation fails, Win11, v3.6.1-1

Description
JupyterLab installation succeeded but the built-in app server installer does not. It first shows some package error, that you can ignore (or retry but that doesn't help), and it then fails with:

Reproduce

uninstall old jlab and jupyter
download 3.6.1-1 for windows
install
start jupyter
click on the built-in installer in the footer of the new welcome screen
install "just for me"

Expected behavior
Successful install
Context

Operating System and version: Win11 10.0.22621 Build 22621, x64
JupyterLab-Desktop version: v3.6.1-1
Installer: .exe

Logs (required for issues with loading, server and startup)

[2023-02-19 16:49:04.120] [info]  In production mode
[2023-02-19 16:49:04.127] [info]  Logging to file (C:\Users\xxx\AppData\Roaming\jupyterlab-desktop\logs\main.log) at 'false' level
[2023-02-19 16:49:04.194] [error] (node:13108) DeprecationWarning: findLogPath() is deprecated and will be removed in v5.
(Use `JupyterLab --trace-deprecation ...` to show where the warning was created)
[2023-02-19 16:49:22.890] [verbose] Starting application in workspace: "default"
[2023-02-19 16:52:16.235] [error] Failed to create free server Error: No default environment found!
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-19 16:52:16.238] [error] (node:23332) UnhandledPromiseRejectionWarning: Error: No default environment found!
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use `JupyterLab --trace-warnings ...` to show where the warning was created)
[2023-02-19 16:52:16.238] [error] (node:23332) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
[2023-02-19 16:54:32.429] [error] Error: Installer Exit: 2
    at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\app.js:470:50)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-19 16:54:40.169] [error] Failed to create free server Error: No default environment found!
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-19 16:54:40.173] [error] (node:17788) UnhandledPromiseRejectionWarning: Error: No default environment found!
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use `JupyterLab --trace-warnings ...` to show where the warning was created)
[2023-02-19 16:54:40.174] [error] (node:17788) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
[2023-02-19 16:54:56.518] [error] (node:17788) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead

I just tested on a Windows 11 virtual machine but couldn't reproduce the issue. Can you provide more info about your system? Is it an Intel CPU?

@mbektas

AMD Ryzen 7 PRO 5850U with Radeon Graphics        1.90 GHz

I can include a screenshot of the first error (warning, actually) if that helps. It doesn't seem right, that you can hit "ignore" on that first error.

Can you try running the server installer directly and when JupyterLab Desktop is closed. possibly with elevated permissions if regulat user permissions doesn't work.
It is located at C:\JupyterLab\resources\env_installer\JupyterLabDesktopAppServer-3.6.1-1-Windows-x86_64.exe

@mbektas
Same behaviour wenn running unprivileged (don't want to install it for all users):

I notice that @black-snow is running a German version of Windows — are we sure we're using localized directory names in the installer? Windows sometimes uses different directory names in different language versions of the OS.

True.
3.5 worked fine, btw.

I notice that @black-snow is running a German version of Windows — are we sure we're using localized directory names in the installer? Windows sometimes uses different directory names in different language versions of the OS.

in the top screenshot installation directory is shown. It doesn't have any special characters.
@black-snow do you see an install.log file in your server installation directory? (...Roaming\jupyterlab-desktop\jlab_server), if so can you check if that provides any details on the error?

@mbektas there's no log there ...

@mbektas What other info might help to triage this issue?

@black-snow does the full path to jlab_server contain any spaces or non-english characters?
can you try installing to another directory like C:/jlab_server.

@mbektas nope, nothing special there - just my Win home dir and my username is just ASCII letters.
On vacation atm so I can't give it a try.

@black-snow Any updates on this?

Tried 3.6.1-1:

and

Reinstalled "for all users" to c:\jlab_server and the install went through. JupyterLab now ain't seem to pick up the installation though - always displays the footer.

@black-snow did you set the Python executable in your installation path as the custom environment as described here?

@mbektas I don't get the question. I run the installer, then start up jupyter lab and hit "Install using the bundled installer" here:

@black-snow I meant setting the installation at c:\jlab_server as the default Python environment. In the footer area of your screenshot, you can see Change the default Python environment. You can click that, go the server tab and select python executable (must be in c:\jlab_server\python.exe) as shown here for macOS and restart.

Will give it a fresh shot with the new 3.6.3-2.

glad to hear that!


Patient is an invalid profile configuration

I am using Asymmetrik's FHIR server core in conjunction with Firebase Cloud Functions to manage patient data and healthcare functionality in my application. I'm currently facing an issue while running the command "firebase emulators:start." Specifically, I'm encountering the following error: "Error: Patient is an invalid profile configuration."
I've taken some initial steps to address this issue, primarily focusing on resolving a mismatch between the resource type name "Patient" (uppercase "P") in my FHIR server configuration and the resource type name "patient" (lowercase "p") in my code.
Additionally, I've ensured that the "patient.metadata.js" file correctly exports a "profiles" object containing a "patient" object. You can access my GitHub repository for your review at the following link: https://github.com/legacyunlimited/medical-clinic-referral/tree/patient_config_error
Full error log: [debug] [2023-09-19T14:02:02.811Z] Got response code 400; body Failed to generate manifest from function source: Error: Patient is an invalid profile configuration, please see the wiki for instructions on how to enable a profile in your server, https://github.com/Asymmetrik/node-fhir-server-core/wiki/Profile
[error] ⬢ functions: Failed to load function definition from source: FirebaseError: Functions codebase could not be analyzed successfully. It may have a syntax or runtime error {"metadata":{"emulator":{"name":"functions"},"message":"Failed to load function definition from source: FirebaseError: Functions codebase could not be analyzed successfully. It may have a syntax or runtime error"}}
Please advise on a solution. Thanks in advance.

commenting out the code I had in patient.metadata.js and the reference to it in index.js fixed the issue but I am unsure why it did.


UI: Fix secret scanning alerts

Fix all secret scanning alerts under the GitHub Security tab. Most of it is in the globalConfigs.js.

Deleted the globalConfigs file in pucar-ui

As discussed with the @TusharKatiyar2002 , the issues is completed and the file changes were done. Did a quick testing of flow to make sure any dependency change didn't affect anything. It's working fine

Hi @subhashini-egov  This alert resolved and taken care


Unable to access LegacyIAccessible pattern properties in WinAppDriveer.

@darshanls Remove IAccessible from the property name
for "LegacyIAccessible.State", use "LegacyState"

@darshanls Remove IAccessible from the property name
for "LegacyIAccessible.State", use "LegacyState"


Multilanguage Files under the same folder.

Hello,
In academic theme documentation, for multilanguage, the content directory is separated based on directory. I do not want do that. Hugo multilanguage documention states with leaf bundle setup the posts translated different languages can stay in the same folder. File names can be post-file-name.en.md post-file-name.fr.md etc. The translated files are distinquished by file name suffixes not by location. Is it possible to do this in Academic Theme?  I do not want to keep whole content directory divide based on language...I would like provide all files with proper extensions and keep all assets with in the relevant directory hierarchy.
Is this currently doable or needs work?
Thanks in advance…

These issues are for bug reports and feature requests. For support, see https://github.com/gcushen/hugo-academic/blob/master/.github/support.md

The forum https://discourse.gohugo.io/c/themes  does not provide feedback or support, that is why I raised issue here. I do not think you are monitoring that forum as well. I will try chat link...Otherwise I will keep raising questions here..


WIP Creates mostly static manager dashboard

Issue #685
We're going to require lang file work and then translations after dev.
Please see the issue and my copious amounts of notes for guidance.

@gobyrne French translations required:

[ ] resources/lang/fr/manager/job_index.php

Translation added

Lighthouse report for the URL: http://localhost:8000/en

Click here to open results 📉

Category
Score
Threshold
Pass

performance
46
0
✅

pwa
27
0
✅

accessibility
100
100
✅

best-practices
80
0
✅

seo
80
0
✅

Lighthouse report for the URL: https://talent.canada.ca/en

Click here to open results 📉

Category
Score
Threshold
Pass

performance
57.99999999999999
0
✅

pwa
54
0
✅

accessibility
100
100
✅

best-practices
73
0
✅

seo
90
0
✅


Add license info for workload cluster docs

Issue #, if available: #3843
Description of changes:
Add step for assigning a support license for workload clusters on a vSphere or CloudStack EKS Anywhere provider.

/test eks-anywhere-docs-presubmit

/cherry-pick release-0.12


100% cpu when syncing a single file on my local machine

I can easily get dat-cli (and my own applications using dat-node) to peg the cpu to 100% and eventually not receive updates.
I am reporting:

[x] a bug or unexpected behavior

node v11.7.0, dat 13.11.5
Steps to reproduce:
mkdir -p test/{local,remote}
cd test/local
edit test.txt
# in a second terminal
cd test/local
dat share
# in a third terminal
cd test/remote
dat clone dat://<output of dat share from second terminal>
cd <output of dat share from second terminal>
dat sync
# in a fourth terminal
watch -n1 cat test/remote/<output of dat share from second terminal>/test.txt
# now make lots of edits to test.txt (like 1 a second for about 30 seconds)

The first few updates are snappy, but soon each update will peg the node process to 100%, and will take longer and longer to sync, and eventually stop syncing (or take over 10 minutes so I cannot tell if they eventually sync).
Video https://vimeo.com/324228171

Thanks, I've been able to reproduce and start identifying where the bug is coming from. It appears something in the hyperdrive._trackLatest is unnecessarily looping. This code hasn't been changed for two years and I'm pretty sure this bug hasn't been out there this entire time.
I've created a basic test case for @mafintosh here: https://gist.github.com/joehand/ad9d3a3dc7f7d7ab611307d396025fbe.

Interesting enough, when I switched to v10 and changed 'syncing' to 'update', things look okay:
dest syncing
  dest version: 290
  source version: 290
dest syncing
  dest version: 291
  source version: 291
dest syncing
  dest version: 292
  source version: 292
dest syncing
  dest version: 293
  source version: 293
dest syncing
  dest version: 294
  source version: 294
dest syncing
  dest version: 295
  source version: 295
dest syncing
  dest version: 296
  source version: 296
dest syncing
  dest version: 297
  source version: 297
dest syncing
  dest version: 298
  source version: 298
dest syncing
  dest version: 299
  source version: 299

So it seems to work as expected with node version 10 (and 8)

sorry, I meant node 11, but the v10 branch of hyperdrive

@jedahan the latest release of hyperdrive 9.14.3 may address this issue. Can you see if updating it has fixed that for you?

closing, feel free to reopen if the bug persists. Thank you for reporting!

confirmed that test case is fixed, thank you all!


Is there an example or demo that shows how to deploy manticoresearch on multiple servers(machines)?

For the docker image - I'm afraid not, but perhaps these links will be helpful:

https://play.manticoresearch.com/replication - interactive course about Manticore replication
https://manual.manticoresearch.com/Creating_a_cluster/Setting_up_replication/Creating_a_replication_cluster#Creating-a-replication-cluster - about creating and joining a replication cluster
https://manual.manticoresearch.com/Server_settings/Searchd#listen - about listen = ...:replication

Docker is just a wrapper for Manticore Search in this case, what's needed on top of what Manticore does is to just make replication ports accessible.

ok. got it. thank you for your response!


Error on createVis with no_cdn option

With 3.15, when loading a vizjson from an on-premise and using the no_cdn:true option the library returns an error. Same code with 3.14 works as expected.

More details at SB/6251218

could you post some sample code?

<!doctype html>

        <meta charset="utf-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
        <link rel="shortcut icon" href="http://cartodb.com/assets/favicon.ico" />
        <meta name="viewport" content="width=device-width, initial-scale=1">

        <link rel="stylesheet" href="http://libs.cartocdn.com/cartodb.js/v3/3.15/themes/css/cartodb.css" />

Changing the version to 3.14 this code works.

The problem here is that the viz.json served by the on-premise instance is "not compatible" with cartodb.js 3.15. There's a disconnection between the version of CartoDB running on that instance and the version of cartodb.js :(. I can think of two possible solutions:

Update CartoDB in the instance so that the viz.json works with cartodb.js 3.15.
Point to cartodb.js 3.14 instead of 3.15.


How important is it to merge building silvers?

As per current guidelines, we tell importers to manually fix building silvers before upload.

Check for small building parts that should be joined to the main building. We've already found a few examples of these in the data (see issue #19), so make sure you keep an eye out for these. To join small parts, select both polygons and select Tools > Join overlapping Area.

Given that the silvers affect less than 1% of the buildings, not sure if it makes sense to spend as much as double the time it takes for conflation to merge silvers. Rather a more efficient approach might be to detect all such silvers post import and attempt to merge them as a separate project?
My suggestions is for the guideline to mention that merging silvers is not the focus of the task, so should not be grounds to invalidate blocks.
cc @jschleuss  @maning

Great point. The slivers are a result of a lower quality property file cutting across the building file. I'm up for debate on whether or not we should focus on merging the slivers. The San Fernando Valley has been covered in those slivers and it's a great irritation.
I think they should be merged, but I don't see a reason for that to invalidate a block. Whoever is doing validation can very quickly scan the area for any areas needing to be merged.

Import is done for LACity, we will do a cleanup task to fix this.


(JS-0241) Consider using arrow functions for callbacks

Description
It is recommended to use arrow functions as callbacks.
Occurrences
There are 4 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/deepsourcelabs/good-first-issue/issue/JS-0241/occurrences/

CAN you assign this to me?

How can l take it and submit changes because I already fixed the issue

Hey is anyone assign to it?


Missing id field causes full update to fail

Source JSON records are assumed to have an id field but LDP does not handle the missing field correctly.  A report by  @brichardEbsco of failing updates appears to be triggered by this problem.

This is hopefully fixed in release 1.1.9: https://github.com/library-data-platform/ldp/releases/tag/1.1.9


Console error after creating project from default template.

Do you want to request a feature or report a bug?
Bug
What is the current behaviour?
A freshly created project has console errors.
If the current behaviour is a bug, please provide the steps to reproduce.

Create a new project preact create default my-project
Run npm start in the project directory.
Access http://localhost:8080 in a web browser.

The following error appears in the browser dev tools console:
Undefined component passed to preact.h() <undefined path="/" url="/" matches="[object Object]" />

What is the expected behaviour?
No console errors
Please mention other relevant information.

Node version
9.5.0
npm version
5.6.0
Operating system
macOS 10.13
CLI version
2.1.1
Browser
Chrome and Safari

This was addressed in #484 & I believe it solves this error too. The patch hasn't gone out yet, but if you could verify for us that this fixes your error, that'd be great! Thanks!

I guess it is fixed in v2.1.3 (latest patch release)

Have updated and still same issue with 2.1.3.

@DiegoGLagash I would clear cache and install everything again. Make sure you're updating global install if you have it too.

Confimed. It works after upgrading global installation. Thanks !


Improve graph execution stats reporting

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[ ] Bug Fix
[x] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[x] Yes
[ ] No, because:

Have you updated all relevant documentation?

[x] Yes: N/A
[ ] No

Description
This PR makes the following improvements to the graph execution stats reporting:

Report graph execution wall time in addition to node execution time.
Fix a bug in the reporting of the RAM diff from this line: RAM used by InvokeAI process: 4.10G (+1.439G). Previously, the diff only reflected the diff during the last node of the graph. Now the diff reflects the entire graph execution.
Improve general code readability by removing the StatsContext layer.
Reduce the number of unnecessary calls to graph_execution_manager.get(graph_id). This is called many times during graph execution and takes a significant amount of time. It was previously being called in the stats service for every node invocation. It is now only called on rare occasions from the stats service (during pruning of stale stats). There are still a number of other places making excessive calls to graph_execution_manager.get(graph_id), but this is a step in the right direction at least.

QA Instructions, Screenshots, Recordings
Stats log before change:
[2024-01-11 15:27:06,090]::[InvokeAI]::INFO --> Graph stats: d29ccfd6-ebba-4f93-905f-4acb80a45f70
[2024-01-11 15:27:06,090]::[InvokeAI]::INFO -->                           Node   Calls  Seconds  VRAM Used
[2024-01-11 15:27:06,090]::[InvokeAI]::INFO -->              main_model_loader     1     0.007s     0.000G
[2024-01-11 15:27:06,090]::[InvokeAI]::INFO -->                      clip_skip     1     0.009s     0.000G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO -->                         compel     2     1.212s     0.246G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO -->                          noise     1     0.007s     0.244G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO -->                denoise_latents     1     3.661s     2.040G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO -->                  core_metadata     1     0.006s     1.858G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO -->                            l2i     1     0.495s     3.156G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO -->               linear_ui_output     1     0.010s     2.152G
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO --> TOTAL GRAPH EXECUTION TIME:    5.406s
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO --> RAM used by InvokeAI process: 4.05G (+0.000G)
[2024-01-11 15:27:06,091]::[InvokeAI]::INFO --> RAM used to load models: 1.99G
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO --> VRAM in use: 2.152G
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO --> RAM cache statistics:
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO -->    Model cache hits: 2
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO -->    Model cache misses: 5
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO -->    Models cached: 5
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO -->    Models cleared from cache: 0
[2024-01-11 15:27:06,092]::[InvokeAI]::INFO -->    Cache high water mark: 1.99/8.00G

Stats log after change:
[2024-01-11 15:31:07,088]::[InvokeAI]::INFO --> Graph stats: 9b8f974e-e65c-451e-be10-6574c4fe6251
                          Node   Calls  Seconds  VRAM Used
             main_model_loader     1     0.008s     0.000G
                     clip_skip     1     0.013s     0.000G
                        compel     2     1.225s     0.246G
                         noise     1     0.009s     0.244G
               denoise_latents     1     3.692s     2.040G
                 core_metadata     1     0.006s     1.858G
                           l2i     1     0.465s     3.156G
              linear_ui_output     1     0.010s     2.152G
TOTAL GRAPH EXECUTION TIME:   5.427s
TOTAL GRAPH WALL TIME:   5.591s
RAM used by InvokeAI process: 4.08G (+1.947G)
RAM used to load models: 1.99G
VRAM in use: 2.152G
RAM cache statistics:
   Model cache hits: 2
   Model cache misses: 5
   Models cached: 5
   Models cleared from cache: 0
   Cache high water mark: 1.99/8.00G

Things to note:

TOTAL GRAPH WALL TIME is reported. It is 0.164s longer than the TOTAL GRAPH EXECUTION TIME in this case.
The diff in RAM used by InvokeAI process: 4.08G (+1.947G) represents the entire graph.

Performance Tests
I ran a simple scalar addition workflow with an iterate node for 100 iterations. Before this change it took ~13secs of wall time, after the change it took ~11secs of wall time. Not as big of a gain as I had hoped. There's still lots of overhead to adress in the graph engine.
Added/updated tests?

[ ] Yes
[x] No

The diff in RAM used by InvokeAI process: 4.08G (+1.947G) represents the entire graph.

How does the diff represent the entire graph? Like, we were at ~2GB baseline and another ~2GB was used during execution?

The diff in RAM used by InvokeAI process: 4.08G (+1.947G) represents the entire graph.

How does the diff represent the entire graph? Like, we were at ~2GB baseline and another ~2GB was used during execution?

ram_change = last_node.end_ram_gb - first_node.start_ram_gb
It would be more informative if we could report peak RAM, but I'm not aware of a way to record that without impacting performance. This at least seemed better than just reporting last_node.end_ram_gb - last_node.start_ram_gb.


IOS 12.2/12.3: Text field in an iframe not focusing on tap

I am facing an issue on focusing an input field under an iframe. It only focuses when I long press on an input field. Here is the link of the video

The public repository link is https://github.com/TarekSalahUddinMahmud/webviewTest. Hope you guys can reproduce this issue here.
I have updated my iPhone 7 plus from 11.3 to 12.2. After updating I am facing this problem. I have updated my cordova-plugin-ionic-webview version 3.1.2 to 4.0.1. But the problem persists. This problem also occurs on iPhone 6s v12.3. We are currently using cordova-plugin-ionic-keyboard v2.1.3. We upgraded it from ionic-plugin-keyboard v2.2.1.
Previously I faced the same issue when I updated my phone to 11.3. I was using ionic-plugin-webview at that time. Moving to cordova-plugin-ionic-webview version 3.1.2 solved the problem at that time.
Here is my Ionic info:
Ionic:
ionic (Ionic CLI)  : 4.0.1
Ionic Framework    : ionic-angular 3.9.2
@ionic/app-scripts : 3.1.8
Cordova:
cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>Cordova Platforms     : ios 4.5.5
System:
Android SDK Tools : 26.1.1
ios-deploy        : 1.9.2
ios-sim           : 6.1.2
NodeJS            : v10.15.3 (/usr/local/bin/node)
npm               : 6.4.1
OS                : macOS High Sierra
Xcode             : Xcode 10.1 Build version 10B61
Environment:
ANDROID_HOME : /Users/bs221/Library/Android/sdk

I can reproduce in your app, but I can't reproduce in this iframe that just shows a regular input text field. <iframe width="100%" height="300" src="https://jsfiddle.net/drewnoakes/eqemx218/embedded/result/" allowfullscreen="allowfullscreen" allowpaymentrequest frameborder="0"></iframe>
So might be something on the iframed app's logic preventing the focus.
I also was able to programmatically focus on the field by calling .focus() after inspecting it's id.

Ok, I've been able to reproduce by running ionic serve and opening in safari, so that leaves the webview plugin out of the problem too.
As you have also duplicated the issue on https://github.com/ionic-team/ionic-v3/issues/1012, let's continue there, but looks like an Apple bug or some problem on your forms.


Update feedback.rs

The origin code paniced on my computer
thread 'main' panicked at 'Failed to get default format: StreamTypeNotSupported', src\libcore\result.rs:997:5
stack backtrace:

When I changed it, it goes well. But I'm not very sure is it right.

I'm guessing the source of this issue is that many commercial devices like laptops only have monophonic microphone input, but the vast majority also have stereo output. Thus, when we request to try and open an input stream using the default output format it would panic as it's not possible to open a stereo stream with a monophonic input. I agree that this fix will likely improve the situation. A better fix might be to use the min channels between both the input and output formats. If anyone would like to do a PR for that in the future, feel free!


Provide a method checking if tapscript contains OP_SUCCESSx

When writing a new smart contract using Taproot I came across a use case that I suspect may be more common as tapscript gains adoption: if the counterparty is supposed to provide a script for fallback scenario (presumably it will contain pre-defined conditions such as timelock at the beginning and follow up with arbitrary conditions) then the counterparty can bypass the conditions by adding not-yet-soft-forked OP_SUCCESSx. Thus these have to be checked before accepting such script.
Having a method to scan the script would help. I intend to send a PR but it might be better to reach decision on #1324 first.

concept ACK.
For this particular usecase, it's worth observing that if you parse the arbitrary conditions as Miniscript, and it succeeds, this guarantees that there are no OP_SUCCESx, and will also guarantee more generally that the "arbitrary conditions" can't override any surrounding context.
I also believe that any failed VERIFY opcodes will kill the script even if a SUCCESSx appears later. So if you have <n> CHECKSEQUENCEVERIFY DROP <arbitrary script> you should also be safe.

I also believe that any failed VERIFY opcodes will kill the script even if a SUCCESSx appears later. So if you have  CHECKSEQUENCEVERIFY DROP  you should also be safe.

This is not the case.

Oh, miniscript already supports taproot? I didn't expect that!

more generally that the "arbitrary conditions" can't override any surrounding context.

Can you give an example? It can increase the time lock but not decrease it which is what I care about (but surely could be interesting in other cases). Is there anything else?

This is not the case.

Heh, glad I double-checked before posting. :) I think this footgun may be an oversight of OP_SUCCESSx design.

Oh, miniscript already supports taproot? I didn't expect that!

Heh, I believe rust-miniscript supports Taproot, but we haven't nailed down a specification for this so it's subject to change as we experiement with it.

Can you give an example?

Sure. So, firstly, aside from use of SUCCESS, if you do a VERIFY check, there is nothing that subsequent code can do to override that. But

If you do a non-override check, e.g. a CHECKSIG, then later code could add a NOT to invert success/failure, or even just DROP the result.
If the extra code comes before, or surrounds, your known code, it can wrap it in an IF/ENDIF and bypass all of your code entirely

These are about security (can the coins be moved when you don't expect). For correctness (can the coins be moved when you do expect) the situation is much worse, because arbitrary code anywhere in your script is able to rearange the stack or do other "non-local" things that will mess up your state.

I think this footgun may be an oversight of OP_SUCCESSx design.

I think it might've been deliberate, to make things like aggregate signatures possible without a hardfork (or a whole new script version). I tend to agree that we should've made the other decision, and that not many people thought carefully about it.

Oh, great. For my use case it's simply X OP_CHECKSEQUENCEVERIFY DROP to which the desired script will be appended. so the security is OK. The coins should be freely spendable by the party providing the script after the timelock so they could only attack themselves as long as there's no OP_SUCCESSx.


[Update] Inventory Movement Get Date From I Document & Fix Offset

Coverage increased (+0.008%) to 77.656% when pulling a3d706065e6b004847b9093dce7b225608987207 on jackyruslymoonlay:dev into ce2bac492949af89ebd63bfea8ab9eb0b9be67d7 on danliris:dev.


feat: value field in execution context should be u256, not felt

Feature Request
Describe the Feature Request

change the field value in the execution context to be a u256, not a felt
update the codebase where meaningful (we used to split_felt and then cast into u256 where suitable)
some tests of execution context might need adding a new felt for dw/asserting the initial execution context
make sure all tests pass

If the feature request is approved, would you be willing to submit a PR? Yes
/ No (Help can be provided if you need assistance submitting a PR)

Can i hop on this

Can i hop on this

sure !

Can i hop on this

This change might have a lot of downstream changes, this'll take quite a while, since the type will change "everywhere" ->
every single value check, every single creation of context, every test, etc.

Okay great, thanks for reaching out, i'd hop right on it and let you know if I need any clarifications

Hello @Eikix please can a clearer context of this task be added, am i meant to correct every cairo contract, or just tests or ..., can you please help me understand this task properly, thanks

hey @faytey I'm sorry but the codebase is currenly under massive refactoring so not the best time to pick a good first issue.

Thank you so much
On Wed, 13 Dec 2023 at 18:40, Clément Walter @.***>
wrote:

hey @faytey https://github.com/faytey I'm sorry but the codebase is
currenly under massive refactoring so not the best time to pick a good
first issue.
—
Reply to this email directly, view it on GitHub
https://github.com/kkrt-labs/kakarot/issues/773#issuecomment-1854432450,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRN2SA63TNAFBU3NSGOX63YJHSBFAVCNFSM6AAAAAA6PB5WASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGQZTENBVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


test: e2e tests for Github CI

Fixes #237
Modifications
Add e2e tests to Github CI. Currently runs functional-e2e test but can support multiple when implemented.
Added check to Makefile when running e2e tests to install Numaflow CRDs if not already present.
Verification
Multiple runs of e2e test on CI.

Converting to draft while testing different Makefile changes.

@juliev0 I'm good with the change, do you want to take another look?


[GOBBLIN-760] Improve retrying behavior of throttling client, add more informative …

…logs.
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-XXX

Description

[ ] Here are some details about my PR, including screenshots (if applicable):

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@autumnust @htran1 could you review?

+1


Permission error on web platform after flutter 3.10 upgrade

Handling the permissions doesn't work on web anymore after upgrading to Flutter 3.10.
The library appears to be not able to gather the permissions
You get a warning saying ... even if the permissions are manually added in the browser's page settings.
mobile_scanner: MobileScannerException: code permissionDenied, message: TypeError: Cannot read properties of undefined (reading 'BrowserMultiFormatReader')
Tested on chrome and safari browsers
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.0, on macOS 13.3.1 22E772610a darwin-x64, locale en-CH)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] IntelliJ IDEA Community Edition (version 2022.3)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

Same here

https://github.com/juliansteenbakker/mobile_scanner/issues/622#issuecomment-1544908494

Awaiting resolution. Thanks in advance

@Solutionstbd @Amphaal @MBjoern @fernandolop I'm closing this one in favor of #622


Use translated panel names on frontend

Description:
Use the newly available translation keys for the remaining built in panels. Depends on https://github.com/home-assistant/home-assistant-polymer/pull/539

I'm not sure if hass.io can have a translation?

My concern is that if we allow it to be translated, we now have to keep an eye out to see if people are translating it (they should not). Let's keep Hass.io not be translatable until the need from a language arises.

If this will be a problem we can hide strings from translators at lokalise.co and also add placeholders.

I'm good with that. I'll take it out for now, and it's easy to add back in if we find a need.


refactor: Enable default values for retryCount and retryDelay

Summary
I have refactored the code so that retryCount and retryDelay specified in DefaultQueryOptions are used in each API :dog:
final queryClient = QueryClient(
  defaultQueryOptions: DefaultQueryOptions(
    retryCount: 2,                          //  <--  The values specified on this line will be treated as the default values.
    retryDelay: const Duration(seconds: 2), //  <--  Same above.
  ),
);

References

Resolves #29

It will be reviewed soon.
Thanks for the PR 👍.
Your contribution is very welcome.

@all-contributors please add @wadackel  for bugs, and code

Hi @41y08h :raised_hands:
Has this change been released on pub.dev?
It looks like the latest change hasn't been released, so I’d like to check the status!

I am waiting for this released also..

This will be released in 24-48 hours. Apologies for the delay

A new version has been released v1.5.0-beta.1.


hanging after 3 container creation jobs consistently

when applying the plan, 4 containers get created, only 3 ever return succesfully, the 4th gets created, but apparently that never percolates back to the provider.
my terraform-provider-proxmox and terraform-provisioner-proxmox were built and installed today from master branch, and my terraform version is:
❯ terraform version
Terraform v0.12.16
+ provider.proxmox (unversioned)

I'm able to consistently repeat this using a 'for loop' type construct (I'm relatively new to TF) below:
resource "proxmox_lxc" "inf-wkr" {
  count = 7
  features {
    nesting = true
  }
  hostname = "inf-wkr-0${count.index + 1}"
  ostype = "debian"
  cores = 4
  memory = 4096
  network {
    name = "eth0"
    bridge = "vmbr0"
    ip = "<IP_ADDRESS>${count.index + 3}/24"
  }
  ostemplate = "net-storage:vztmpl/debian-10.0-standard_10.0-1_amd64.tar.gz"
  password = "REDACTED"
  pool = "thwap"
  storage = "local-lvm"
  unprivileged = true
  target_node = "${count.index % 2 == 0 ? "pve01" : "pve02"}"
}

proxmox_lxc.inf-wkr[2]: Creating...
proxmox_lxc.inf-wkr[2]: Still creating... [10s elapsed]
proxmox_lxc.inf-wkr[2]: Creation complete after 10s [id=pve01/lxc/100]
proxmox_lxc.inf-wkr[0]: Creating...
proxmox_lxc.inf-wkr[0]: Still creating... [10s elapsed]
proxmox_lxc.inf-wkr[0]: Creation complete after 10s [id=pve01/lxc/101]
proxmox_lxc.inf-wkr[5]: Creating...
proxmox_lxc.inf-wkr[5]: Still creating... [10s elapsed]
proxmox_lxc.inf-wkr[5]: Creation complete after 15s [id=pve02/lxc/102]
proxmox_lxc.inf-wkr[4]: Creating...
proxmox_lxc.inf-wkr[4]: Still creating... [10s elapsed]
proxmox_lxc.inf-wkr[4]: Still creating... [20s elapsed]
proxmox_lxc.inf-wkr[4]: Still creating... [30s elapsed]
proxmox_lxc.inf-wkr[4]: Still creating... [40s elapsed]
proxmox_lxc.inf-wkr[4]: Still creating... [50s elapsed]

for the record, even with -parallelism=5 only 4 get created, none ever return successfully

I've the same problem. Any progress?

I've the same issue:
terraform version
Terraform v0.12.26

provider.proxmox (unversioned)

The creation log keep going albeit the CT is up and running (created in about 20 seconds)
proxmox_lxc.nfs-storage[0]: Creating...
proxmox_lxc.nfs-storage[0]: Still creating... [10s elapsed]
proxmox_lxc.nfs-storage[0]: Still creating... [20s elapsed]
proxmox_lxc.nfs-storage[0]: Still creating... [30s elapsed]
proxmox_lxc.nfs-storage[0]: Still creating... [40s elapsed]
proxmox_lxc.nfs-storage[0]: Still creating... [50s elapsed]
proxmox_lxc.nfs-storage[0]: Still creating... [1m0s elapsed]
proxmox_lxc.nfs-storage[0]: Still creating... [1m10s elapsed]
------- maint.tf -------
resource "proxmox_lxc" "nfs-storage" {
count             = 1
hostname          = "nfs-storage"
target_node       = "proxmox"
ostemplate        = "local:vztmpl/debian-10.0-standard_10.0-1_amd64.tar.gz"
cores             = 1
memory            = 1024
rootfs = "local-lvm:10"
storage = "G1-thin"
start             = true
network {
name = "eth0"
bridge = "vmbr0"
ip = "<IP_ADDRESS>${count.index + 1}/24"
firewall = false
gw       = "<IP_ADDRESS>"
tag      = 501
}
lifecycle {
ignore_changes  = [
network,
ostemplate,
ssh_public_keys,
password
]
}
password       = "testtest"
unprivileged = true
}

before banging your head on this problem, remember that the order of creation is not linear, so if the element numbee 7 gets creared, the ip string becomes that
ip = "<IP_ADDRESS>${count.index + 3}/24"
ip = "<IP_ADDRESS>0/24"
i dont think that ip octet can reach 410 :)

Exact same issue here!

resource "proxmox_lxc" "lxc-test" {
    hostname = "lxc-test-host"
    cores = 1
    memory = "1024"
    swap = "2048"
    network {
        name = "eth0"
        bridge = "vmbr0"
        ip = "<IP_ADDRESS>/24"
        firewall = true
    }
    ostemplate = "local:vztmpl/ubuntu-18.04-custom.tar.gz"
    password = "<secure password>"
    pool = "terraform"
    rootfs = "local-lvm2:8"
    storage = "local-lvm2"
    target_node = "proxmox"
    unprivileged = true
}

Same

I am facing the same issue. You have to ensure that your virtual machine image has qemu-guest-agent. Otherwise, it can't exchange information between the host and guest. Still creating...
https://pve.proxmox.com/wiki/Qemu-guest-agent


Old 3ds Failed to update Luma 10.1.3

What model of system are you using?

[x] Old 3DS
[ ] Old 3DS XL
[ ] 2DS (non-XL)
[ ] New 3DS
[ ] New 3DS XL
[ ] New 2DS XL

What is your current Luma3DS version?
If you are running an hourly version of Luma3DS, please manually update to a stable version as I will no longer deal with people who are using hourlies.

[ ] Luma3DS v7.1 + boot9strap v1.0/v1.1
[x] Luma3DS v8.0 + boot9strap v1.2+
[ ] Luma3DS v8.1 + boot9strap v1.2+
[ ] Luma3DS v8.1.1 + boot9strap v1.2+
[ ] Luma3DS v9.0 + boot9strap v1.2+
[ ] Luma3DS v9.1 + boot9strap v1.2+
[ ] Luma3DS v10.0+ + boot9strap v1.2+

What version of Luma Updater are you using?

[ ] v2.0
[ ] v2.1
[ ] v2.1.1
[ ] v2.1.2
[ ] v2.2
[ ] v2.3
[x] v2.4
[ ] v2.5

How are you running Luma Updater?

[x] .cia
[ ] .3dsx + HBL/Rosalina

What problems are you experiencing?
Please tell us what problems you are facing.
DOWNLOAD FAILED
What is the exact error code you are receiving?
Please give the exact error code the app gives you.
ded92
Steps to reproduce

Run Luma Updater .cia
Dont update (to v2.5) and continue
Install stable version (10.1.3)

#53

To solve this problem, first unistall the current luma updater v2.4 and download luma 2.5 zip

Copy and paste to your 3d sd memory (copy the files from inside "3ds" binder of the .zip to the binder "3ds" of the sd, and the another files of the .zip copy and paste to the root of your 3ds sd)  Extract the sd and put on your 3ds, turn it on, and go to FBI for install the cia file. When its done, go to the luma updater icon and run the app and follow the steps to update Luma. Thanks.


question about the algorithm 1

I have a question about the algorithm 1 Dirichlet. Why there is a factor 2 in line 4? I do not see it in Lemma 1.
Would you like to explain it to me? Thank you very much.

You can look at Theorem-2 proof for this in the paper. See Sec-C.2.1 in the Appendix


Added myself :)

If we waited around for other people to give us credit, we'd be waiting a long time :D
Thanks for making this repo <3

If we waited around for other people to give us credit, we'd be waiting a long time :D
Thanks for making this repo <3

Well said @snipe! 😄


Fix for console table without headers

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
-

Merged. Thank you!


alevin-fry quant fails bc of mismatch  in number of tx present vs number of tx in tg-map

Hi, I was testing out alevin-fry and got up to the quant step, and got this error message
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `140992`,
 right: `141131`: The tg-map must contain a gene mapping for all transcripts in the header', libradicl/src/quant.rs:467:5

I'm using the same file for --tg-map that I used for --tgMap in my salmon alevin command. the tx in this file also match up to the fasta I used for my salmon index command.  I commented out the assertion causing the failure, rebuilt, and it ran okay. If I had to guess, the few transcripts that are removed for various reasons(too short?) during salmon index will be in my tg-map but not in the downstream data. Maybe change the assertion to fail only if there transcripts in the rad file that are not in the tg-map file

Hi @vinay-swamy,
Thanks for reporting this issue.  Somehow, I'd not been notified from your initial posting of the issue so I apologize for taking so long to get back to you here.  I think that short transcripts should still appear in the header (though I will check).  I wonder if the transcripts that were removed were sequence duplicates.  Would you get this error if you indexed with --keepDuplicates?
Thanks,
Rob

Hi @vinay-swamy,
After some more testing, I'm fairly sure this is due to the use of an index with decoys in it during the generation of the RAD file.  When you have a chance, can you please confirm this?  We've further clarified in the documentation that this is not supported in the current alevin-fry pipeline.
Thanks,
Rob

Hi @vinay-swamy,
After doing testing, I'm fairly certain this is the result of mapping upstream with decoy sequences in the index which isn't supported.  Nonetheless, we've just pushed v0.2.0 which has some otherwise nice new features and performance improvements.  I'm going to close this for now, but please feel free to reopen if you encounter this issue and it seems not to be caused by decoys.

Hi, sorry to re-open this but I have encountered the same error and I'm a bit at my wits' end. I also get the same issue at the quant step of alevin-fry (salmon alevin, alevin-fry generate-permit-list, and alevin-fry collate run smoothly).
Here's the last step with error message. Like vinay-swamy I used the same --tg-map here as the --tgMap in salmon alevin
$ alevin-fry quant -i $outDir --tg-map $tsv -t 30 -r cr-like -o $outDir
2023-10-17 14:57:08 INFO quantifying from uncompressed, collated RAD file File { fd: 4, path: "/project/MDL_monaco/analysis/04_scComparisons/04_ateAlb_musMus/02_musMus_soloRun/outs/mpimg_L29135-1_D1-D2-Mmu-E14-5_S5_L003/map.collated.rad", read: true, write: false }
2023-10-17 14:57:08 INFO paired : false, ref_count : 227,777, num_chunks : 123,914
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `227111`,
 right: `227777`: The tg-map must contain a gene mapping for all transcripts in the header', src/utils.rs:235:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I first checked that the tsv and the fasta I used for the index had the same amount of transcripts, and that there were no "holes" in my tg-map:
$ wc -l $tsv
227777
$ grep ">" mm10.GRCm38.txp.clean.fa | wc -l
227777

$ cut -f1 $tsv | wc -l
227777
$ cut -f2 $tsv | wc -l
227777

The transcript names are also in the same order between tsv and fasta headers (you never know). I just assigned the fasta to file1 and the tsv to file2 here.
$ grep ">" $file1 | head
>ENSMUST00000162897
>ENSMUST00000159265
>ENSMUST00000070533
>ENSMUST00000161581
>ENSMUST11000161581
>ENSMUST00000192692
>ENSMUST00000194643
>ENSMUST00000192427
>ENSMUST11000194643
>ENSMUST11000192427
$ head $file2
ENSMUST00000162897      Xkr4
ENSMUST00000159265      Xkr4
ENSMUST00000070533      Xkr4
ENSMUST00000161581      Gm1992
ENSMUST11000161581      Gm1992
ENSMUST00000192692      Gm19938
ENSMUST00000194643      Gm37381
ENSMUST00000192427      Gm37381
ENSMUST11000194643      Gm37381

So I tried to find those 666 (ha) lines that are not in both files, but that didn't work out: it just spits back all the lines one by one (I don't vouch for my "seeker" code, could be absolute rubbish).
$ while IFS= read -r line; do
>     if [[ $line =~ \>(.*) ]]; then
>         substring="${BASH_REMATCH[1]}"
>         found_match=0
>
>         for item in "${file2_array[@]}"; do
>             if [[ "$item" == "$substring" ]]; then
>                 found_match=1
>                 break
>             fi
>         done
>
>         if [ "$found_match" -eq 0 ]; then
>             echo "No match found in File2 for: $substring"
>         fi
>     fi
> done < "$file1"
No match found in File2 for: ENSMUST00000162897
No match found in File2 for: ENSMUST00000159265
No match found in File2 for: ENSMUST00000070533
No match found in File2 for: ENSMUST00000161581
No match found in File2 for: ENSMUST11000161581
No match found in File2 for: ENSMUST00000192692
No match found in File2 for: ENSMUST00000194643
No match found in File2 for: ENSMUST00000192427
^C

I also made a brand new index for this quantification, in the past I had an incompatibility with using an index made with an older version of salmon, so this is not the case here.
Any help or troubleshooting tips are strongly appreciated!

Cc @DongzeHE.

Hi @AnnaAMonaco,
First, sorry you are seeing this frustrating issue. Hopefully, its its something simple but subtle. Is there any portion of this data you could share to help us debug? Specifically, the rad, reference and t2g files would be the most useful.
Thanks!
Rob

@rob-p, thank you for the offer!
Would the first unique 100 transcripts from the rad file + corresponding txp.fasta and tgMap suffice?

As long as that triggers the error, for sure!
--Rob


MVP

In order to validate the design and gain understanding of the shortcomings, we will put together an MVP. This SHOULD cover an end-to-end implementation of the business logic based on #15 for three services (S3, IAM, DynamoDB) incl. install procedure and testing.
The MVP will depend on #3 #4 #5 #6 and #14.

We would like to see RDS and Redis(Elasticache) added to this MVP if possible. We have customers who are interested in these two services right now.

We would like to see RDS and Redis(Elasticache) added to this MVP if possible. We have customers who are interested in these two services right now.

SQS

@mhausenblas it looks like the latest master branch of kubebuilder supports multi-group support, so it's completely possible to have s3.amazonaws.com and dynamodb.amazonaws.com groups now. The original discovery document from PR 15 probably needs updating and, if this change has any impact on DIY code-generator vs. kubebuilder it should be re-assessed before things get too far down the line.

Cool, thanks a lot @daviddyball! CC: @jaypipes

@daviddyball ack, thx for the heads up. feel free to push a PR that updates the code-generation.md doc if you'd like!

@jaypipes https://github.com/aws/aws-service-operator-k8s/pull/26 :+1:

Services we would likely use this for:

CloudWatch Alarms
S3
PostgreSQL RDS
IAM Roles
Redis Elasticache
Kinesis
DynamoDB

Here's a list of services that we would love to see:

S3
Aurora/RDS
DynamoDB
Redis Elasticache

Not sure if ACM is also a viable candidate for a first service here. An operator for ACM certificates and storing them into a secret would be great though. Cert-manager.io isn't supporting ACM and isn't likely to support it anytime soon (judging by https://github.com/jetstack/cert-manager/issues/333)

It raises the question in my head if IAM support is not essential for other services? Whenever any other service is created, IAM will come into play.

@sfzylad The topic of IAM in the context of this particular issue is really just about whether we will have the controller support creation/management of IAM Roles and PermissionSets via a Kubernetes CRD. If we do not support this, we would require that IAM roles and permission sets be pre-created/managed by an administrator.
Clearly, having the AWS Service Operator controller have the ability to create new IAM roles or modify IAM role permission sets is a giant security consideration, which is why we are hesitant to include it into ASO's initial set of managed services...

Here's a list of services that we use on a daily basis, that would fit these requirements (these are now endpoints in our Kubernetes cluster, but we'd rather have them available as services as it would ease our development life-cycle):

S3
Aurora/RDS
DynamoDB (+ DAX)
Redis ElastiCache
Elasticsearch Service
Simple Email Service
Simple Notification Service
Simple Queue Service
Amazon Rekognition
Amazon Textract

The targeted AWS services in scope for the MVP will be:

Amazon S3
Amazon SNS
Amazon SQS
Amazon ECR
Amazon DynamoDB
Amazon API Gateway V2

Consider my use-case, which I believe is reasonably ubiquitous:
Manage infrastructure assets via Terraform (or CloudFormation)
Manage application assets via k8s manifests/helm charts
Under this approach I already have support for creating things like queues, topics, databases, etc. These assets are then available for integration by applications. What I lack support for is cloud assets that fall under the scope of applications -- essentially application assets that I want to declare in manifests that belong to the application helm chart. For example: Route53 records and CloudFront distros. These are the most desired services for me to be supported in this operator.
I guess my perspective is different, but I was hoping this operator would provide the ability to declare typical application assets in my application's helm chart. Considering I don't anticipate creating queues, topics and databases as part of an application release (they are usually shared infra services, IMO), I don't expect to gain much value from the MVP as defined. Adding Route53 and CloudFront would provide much more value. I'd love to contribute toward these implementations once the groundwork is laid.

@adamrbennett Not sure you're aware of this, but generic Route53 entries can be managed using external-dns. Which works well also with Ingress & Service resources (Nginx Ingress controller, NLB in tree on services, ALB Ingress controller). Cert manager has it's own integration into Route53 for ACME dns0 validation. However, I don't have an answer for managing CloudFront from inside kubernetes, I manage that through Pulumi upfront. Those resources are also far less dynamic, so it hasn't proven to be a huge drawback to not have it as a kubernetes resource. It does however require that you provision ephemeral environments the same way, they don't just get automatically provisioned when deploying the resources but are an additional step upfront (I guess it would also be possible to wrap the Pulumi run in a controller similar to https://github.com/rancher/terraform-controller).

For those reading this issue now or if you're subscribed and waiting for an update: please help us testing the MVP, see details in https://aws.github.io/aws-controllers-k8s/dev-docs/testing/

I am surprised I do not see Route 53

Closing as this information has become largely out of date, and superseded by other issues.


Setup fork of ping.pub

Setup fork of ping.pub for current testnets.

https://github.com/ping-pub/explorer


Problem installing with build

When trying to build or using get, always this error of some package that is not in GOROOT
golang_org/x/net/lex/httplex: package golang_org/x/net/lex/httplex is not in GOROOT (/usr/lib/go-1.7/src/golang_org/x/net/lex/httplex)
I'm not sure if the error is on my side.
If possible, please update the release file, in order to reflect https://github.com/dwisiswant0/go-dork/issues/12
Thank you very much and great job, once again :)

Hi, you just only need to run go build . to build from source, and we didn't realize that our binary releaser is broken. But, now it's live on https://github.com/dwisiswant0/go-dork/releases/tag/v1.0.2. Thanks!


Multimeter Widget device selection does not persist

Joulescope model
JS220, JS110
UI version
1.0.35
What OS are you seeing the problem on?
Windows 11
What happened?
The Multimeter Widget (which shares the Value Widget implementation) has does not persist the device selection.  If you switch to a different view and return or restart the UI, the Multimeter Widget reverts to the default device.
What was expected?
The Multimeter Widget should persist the device and use it, assuming it is still available.  If the device is no longer available, it should use the default device.
How to reproduce?

Open the Multimeter View
Use the Device dropdown to select the device
Open the Oscilloscope View
Open the Multimeter view
Observe that the device dropdown shows "default", not the previously selected device.

Extra information
No response

Fixed in 1.0.45 (currently alpha)