pilot nextflow pipeline with MISO and QAPA and nextflow template

I have tested the pipeline with the mouse cortex sample I processed last week, and here is the run (I copied whatever showed up on my command line):
$ nextflow main.nf --input samplesheet.csv
N E X T F L O W  ~  version 21.01.0-edge
Launching `main.nf` [zen_jones] - revision: e83f681ad1
executor >  local (3)
[d4/7b914f] process > CHECK_SAMPLESHEET (samplesheet.csv) [100%] 1 of 1 ✔
[87/497999] process > MISO (test)                         [  0%] 0 of 1
[1c/dced51] process > QAPA (test)                         [100%] 1 of 1 ✔
Threads = 2
Vertex length = 31
Hash functions = 5
Filter size = 536870912
Capacity = 2
executor >  local (3)
[d4/7b914f] process > CHECK_SAMPLESHEET (samplesheet.csv) [100%] 1 of 1 ✔
[87/497999] process > MISO (test)                         [100%] 1 of 1 ✔
[1c/dced51] process > QAPA (test)                         [100%] 1 of 1 ✔
Indexing GFF...
  - GFF: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/gencode.vM26.primary_assembly.annotation.gff3
  - Outputting to: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
Through 0 genes...
Through 5000 genes...
Through 10000 genes...
Through 15000 genes...
Through 20000 genes...
Through 25000 genes...
Through 30000 genes...
Through 35000 genes...
Through 40000 genes...
Through 45000 genes...
Through 50000 genes...
Loaded 53700 genes
  - Loading of genes from GFF took 128.29 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456210.1
  - Chromosome serialization took 0.09 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrY
  - Chromosome serialization took 0.36 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrX
  - Chromosome serialization took 1.04 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr13
  - Chromosome serialization took 1.05 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr12
  - Chromosome serialization took 1.07 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr11
  - Chromosome serialization took 1.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr10
  - Chromosome serialization took 1.39 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr17
  - Chromosome serialization took 1.50 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr16
  - Chromosome serialization took 0.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr15
  - Chromosome serialization took 1.11 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr14
  - Chromosome serialization took 1.21 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr19
  - Chromosome serialization took 0.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr18
  - Chromosome serialization took 0.75 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrM
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456233.2
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456212.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456211.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584295.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456221.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584304.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456354.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584303.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr7
  - Chromosome serialization took 2.43 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr6
  - Chromosome serialization took 1.60 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr5
  - Chromosome serialization took 1.97 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr4
  - Chromosome serialization took 1.67 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr3
  - Chromosome serialization took 1.42 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr2
  - Chromosome serialization took 2.47 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr1
  - Chromosome serialization took 1.90 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr9
  - Chromosome serialization took 1.76 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr8
  - Chromosome serialization took 1.39 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584298.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584297.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456219.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584296.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584299.1
  - Chromosome serialization took 0.00 seconds
Outputting gene records in GFF format...
  - Output file: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/genes.gff
  - Serialization of genes from GFF took 31.94 seconds
Indexing of GFF took 160.23 seconds.
MISO (Mixture of Isoforms model)
Probabilistic analysis of RNA-Seq data for detecting differential isoforms
Use --help argument to view options.

Using MISO settings file: /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
Computing Psi values...
  - GFF index: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
  - BAM: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam
  - Read length: 37
  - Output directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs
Checking your GFF annotation and BAM for mismatches...
Checking if BAM has mixed read lengths...
Found reads of length 37 in BAM.
Mapping genes to their indexed GFF representation, using /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
Searching for /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/genes_to_filenames.shelve..
  - Found shelved file.
Preparing to run 4 batches of jobs...
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-0_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-0
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-1_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-1
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-2_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-2
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-3_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-3
Waiting on 4 threads...
MISO (Mixture of Isoforms model)
Summarize MISO output to get Psi values and confidence intervals.
Use --help argument to view options.

Loading events from: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs
Writing summary to: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/summary_output/summary/unsummarized_outputs.miso_summary
  - Summarized a total of 12808 events.

executor >  local (3)
[d4/7b914f] process > CHECK_SAMPLESHEET (samplesheet.csv) [100%] 1 of 1 ✔
[87/497999] process > MISO (test)                         [100%] 1 of 1 ✔
[1c/dced51] process > QAPA (test)                         [100%] 1 of 1 ✔
Indexing GFF...
  - GFF: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/gencode.vM26.primary_assembly.annotation.gff3
  - Outputting to: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
Through 0 genes...
Through 5000 genes...
Through 10000 genes...
Through 15000 genes...
Through 20000 genes...
Through 25000 genes...
Through 30000 genes...
Through 35000 genes...
Through 40000 genes...
Through 45000 genes...
Through 50000 genes...
Loaded 53700 genes
  - Loading of genes from GFF took 128.29 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456210.1
  - Chromosome serialization took 0.09 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrY
  - Chromosome serialization took 0.36 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrX
  - Chromosome serialization took 1.04 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr13
  - Chromosome serialization took 1.05 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr12
  - Chromosome serialization took 1.07 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr11
  - Chromosome serialization took 1.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr10
  - Chromosome serialization took 1.39 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr17
  - Chromosome serialization took 1.50 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr16
  - Chromosome serialization took 0.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr15
  - Chromosome serialization took 1.11 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr14
  - Chromosome serialization took 1.21 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr19
  - Chromosome serialization took 0.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr18
  - Chromosome serialization took 0.75 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrM
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456233.2
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456212.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456211.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584295.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456221.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584304.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456354.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584303.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr7
  - Chromosome serialization took 2.43 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr6
  - Chromosome serialization took 1.60 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr5
  - Chromosome serialization took 1.97 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr4
  - Chromosome serialization took 1.67 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr3
  - Chromosome serialization took 1.42 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr2
  - Chromosome serialization took 2.47 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr1
  - Chromosome serialization took 1.90 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr9
  - Chromosome serialization took 1.76 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr8
  - Chromosome serialization took 1.39 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584298.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584297.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456219.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584296.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584299.1
  - Chromosome serialization took 0.00 seconds
Outputting gene records in GFF format...
  - Output file: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/genes.gff
  - Serialization of genes from GFF took 31.94 seconds
Indexing of GFF took 160.23 seconds.
MISO (Mixture of Isoforms model)
Probabilistic analysis of RNA-Seq data for detecting differential isoforms
Use --help argument to view options.

Using MISO settings file: /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
Computing Psi values...
  - GFF index: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
  - BAM: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam
  - Read length: 37
  - Output directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs
Checking your GFF annotation and BAM for mismatches...
Checking if BAM has mixed read lengths...
Found reads of length 37 in BAM.
Mapping genes to their indexed GFF representation, using /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
Searching for /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/genes_to_filenames.shelve..
  - Found shelved file.
Preparing to run 4 batches of jobs...
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-0_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-0
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-1_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-1
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-2_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-2
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-3_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-3
Waiting on 4 threads...
MISO (Mixture of Isoforms model)
Summarize MISO output to get Psi values and confidence intervals.
Use --help argument to view options.

Loading events from: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs
Writing summary to: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/summary_output/summary/unsummarized_outputs.miso_summary
  - Summarized a total of 12808 events.

Done!

executor >  local (3)
[d4/7b914f] process > CHECK_SAMPLESHEET (samplesheet.csv) [100%] 1 of 1 ✔
[87/497999] process > MISO (test)                         [100%] 1 of 1 ✔
[1c/dced51] process > QAPA (test)                         [100%] 1 of 1 ✔
Indexing GFF...
  - GFF: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/gencode.vM26.primary_assembly.annotation.gff3
  - Outputting to: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
Through 0 genes...
Through 5000 genes...
Through 10000 genes...
Through 15000 genes...
Through 20000 genes...
Through 25000 genes...
Through 30000 genes...
Through 35000 genes...
Through 40000 genes...
Through 45000 genes...
Through 50000 genes...
Loaded 53700 genes
  - Loading of genes from GFF took 128.29 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456210.1
  - Chromosome serialization took 0.09 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrY
  - Chromosome serialization took 0.36 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrX
  - Chromosome serialization took 1.04 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr13
  - Chromosome serialization took 1.05 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr12
  - Chromosome serialization took 1.07 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr11
  - Chromosome serialization took 1.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr10
  - Chromosome serialization took 1.39 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr17
  - Chromosome serialization took 1.50 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr16
  - Chromosome serialization took 0.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr15
  - Chromosome serialization took 1.11 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr14
  - Chromosome serialization took 1.21 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr19
  - Chromosome serialization took 0.95 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr18
  - Chromosome serialization took 0.75 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrM
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456233.2
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456212.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456211.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584295.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456221.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584304.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456354.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584303.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr7
  - Chromosome serialization took 2.43 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr6
  - Chromosome serialization took 1.60 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr5
  - Chromosome serialization took 1.97 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr4
  - Chromosome serialization took 1.67 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr3
  - Chromosome serialization took 1.42 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr2
  - Chromosome serialization took 2.47 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr1
  - Chromosome serialization took 1.90 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr9
  - Chromosome serialization took 1.76 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chr8
  - Chromosome serialization took 1.39 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584298.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584297.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrGL456219.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584296.1
  - Chromosome serialization took 0.00 seconds
Making directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/chrJH584299.1
  - Chromosome serialization took 0.00 seconds
Outputting gene records in GFF format...
  - Output file: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/genes.gff
  - Serialization of genes from GFF took 31.94 seconds
Indexing of GFF took 160.23 seconds.
MISO (Mixture of Isoforms model)
Probabilistic analysis of RNA-Seq data for detecting differential isoforms
Use --help argument to view options.

Using MISO settings file: /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
Computing Psi values...
  - GFF index: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
  - BAM: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam
  - Read length: 37
  - Output directory: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs
Checking your GFF annotation and BAM for mismatches...
Checking if BAM has mixed read lengths...
Found reads of length 37 in BAM.
Mapping genes to their indexed GFF representation, using /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed
Searching for /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/indexed/genes_to_filenames.shelve..
  - Found shelved file.
Preparing to run 4 batches of jobs...
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-0_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-0
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-1_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-1
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-2_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-2
Running batch of 13425 genes..
  - Executing: python /usr/local/lib/python2.7/dist-packages/misopy/run_miso.py --compute-genes-from-file "/home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs/batch-genes/batch-3_genes.txt" /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/Aligned.out.sorted.bam /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs --read-len 37  --paired-end 250.0 15.0 --settings-filename /usr/local/lib/python2.7/dist-packages/misopy/settings/miso_settings.txt
  - Submitted thread batch-3
Waiting on 4 threads...
MISO (Mixture of Isoforms model)
Summarize MISO output to get Psi values and confidence intervals.
Use --help argument to view options.

Loading events from: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/unsummarized_outputs
Writing summary to: /home/wanyk/Downloads/APAeval/nextflow/work/87/497999d7d12f8a62221f6ce9b47cbe/summary_output/summary/unsummarized_outputs.miso_summary
  - Summarized a total of 12808 events.

Done!
WARN: To render the execution DAG in the required format it is required to install Graphviz -- See http://www.graphviz.org for more info.
Completed at: 04-May-2021 21:39:01
Duration    : 1h 13m 31s
CPU hours   : 1.3
Succeeded   : 3

Here are the outputs from the pipeline (the tar.gz results directory can be downloaded here):
$ ls -lh results/*
results/miso:
total 12K
drwxr-xr-x 38 wanyk wanyk 4.0K May  4 21:39 indexed
drwxr-xr-x  3 wanyk wanyk 4.0K May  4 21:38 summary_output
drwxr-xr-x 32 wanyk wanyk 4.0K May  4 21:39 unsummarized_outputs

results/pipeline_info:
total 2.9M
-rw-r--r-- 1 wanyk wanyk 2.8M May  4 21:39 execution_report.html
-rw-r--r-- 1 wanyk wanyk 6.0K May  4 21:39 execution_timeline.html
-rw-r--r-- 1 wanyk wanyk  481 May  4 21:38 execution_trace.txt
-rw------- 1 wanyk wanyk  976 May  4 21:39 pipeline_dag.dot
-rw-r--r-- 1 wanyk wanyk  479 May  4 20:25 samplesheet_reformat.csv

results/qapa:
total 61M
-rw-r--r-- 1 wanyk wanyk 2.4K May  4 20:27 mm39.fa.fai
-rw-r--r-- 1 wanyk wanyk  57M May  4 20:27 output_sequences.fa
-rw-r--r-- 1 wanyk wanyk 4.3M May  4 20:27 pau_results.txt
drwxr-xr-x 5 wanyk wanyk 4.0K May  4 20:27 salmon_results
drwxr-xr-x 2 wanyk wanyk 4.0K May  4 20:27 utr_library

The results/pipeline_info/execution_trace.txt gives a summary of execution time and other computation resources usage of each process:
task_id	hash	native_id	name	status	exit	submit	duration	realtime	%cpu	peak_rss	peak_vmem	rchar	wchar
1	d4/7b914f	3963	CHECK_SAMPLESHEET (samplesheet.csv)	COMPLETED	0	2021-05-04 20:25:31.071	95ms	33ms	78.3%	3.2 MB	12.6 MB	590.4 KB1.8 KB
3	1c/dced51	4073	QAPA (test)	COMPLETED	0	2021-05-04 20:25:31.222	1m 35s	1m 35s	315.0%	645.4 MB	1.7 GB	8.8 GB	445.8 MB
2	87/497999	4082	MISO (test)	COMPLETED	0	2021-05-04 20:25:31.231	1h 13m 28s	1h 13m 27s	356.2%	12.7 GB	14.1 GB	153.6 GB	2.9 GB

I guess it will be great if a new branch can be created to merge this pull request.
Thanks!

Hi @ninsch3000, thank you for the suggestions! I have addressed all of them!


@mui/material-nextjs has failed installing on 15.0.1

Steps to reproduce
pnpm i @mui/material-nextjs@latest --strict-peer-dependencies=false
 WARN  6 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Already up to date
Progress: resolved 526, reused 500, downloaded 0, added 0, done
 WARN  Issues with peer dependencies found
.
└─┬ @mui/material-nextjs 6.1.5
└── ✕ unmet peer<EMAIL_ADDRESS>|| ^14.0.0": found 15.0.1
Done in 2.4s
Current behavior
pnpm i @mui/material-nextjs@latest --strict-peer-dependencies=false
 WARN  6 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Already up to date
Progress: resolved 526, reused 500, downloaded 0, added 0, done
 WARN  Issues with peer dependencies found
.
└─┬ @mui/material-nextjs 6.1.5
└── ✕ unmet peer<EMAIL_ADDRESS>|| ^14.0.0": found 15.0.1
Done in 2.4s
Expected behavior
Success installation with 15.0.1 version and above
Context
No response
Your environment
System:
OS: Windows 11 10.0.22631
Binaries:
Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.12.1 - C:\Program Files\nodejs\pnpm.CMD
Browsers:
Chrome: Not Found
Edge: Chromium (127.0.2651.74)
npmPackages:
@emotion/react: ^11.13.3 => 11.13.3
@emotion/styled: ^11.13.0 => 11.13.0
@mui/icons-material: ^6.1.5 => 6.1.5
@mui/lab: 6.0.0-beta.13 => 6.0.0-beta.13
@mui/material: ^6.1.5 => 6.1.5
@mui/material-nextjs: ^6.1.5 => 6.1.5
@mui/system: ^6.1.5 => 6.1.5
@types/react: 18.3.12 => 18.3.12
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
typescript: 5.6.3 => 5.6.3
Search keywords: material-nextjs nextjs mui

Duplicate of https://github.com/mui/material-ui/issues/44203


This document needs to explain that trigger paths are case sensitive

Lost a lot of time figuring this out :(

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

ID: f5673ec1-c7d1-e0ac-043a-8fc3d5b226a9
Version Independent ID: b4872831-51c0-6cf8-1c56-de20beb38a80
Content: Build pipeline triggers - Azure Pipelines
Content Source: docs/pipelines/build/triggers.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

@judemars I'm sorry that you ran into trouble, I will make a note to call that out.

Next set of updates to this doc will have this note.

@samrueby -- Sam, thank you for your follow-up.  I am investigating.

@vijayma -- Vijay, please review this update in private PR 4623.

Will it surprise anyone to hear that the document was last updated in Jan 2023, and as at 10 Feb 2023 it STILL does not mention that trigger paths are case sensitive!
@steved0x  @vijayma  @WilliamAntonRohm
What's going on? Seems like it can't be that hard to update this?

I just lost so much time on this. How is this not done. Is this something I can change?

@PapaDers -- thank you for your followup.  Are you referring to documenting this behavior, or changing it in the product?  If this is product-related, please add it there:

Developer Community

@WilliamAntonRohm @PapaDers  the issue (as I understand it) is that ADO runs on Linux, which is case sensitive, ergo files and branches are case sensitive.
I think we can all cope with that but the internal hosting arrangements for SaaS platforms can't be known to its users and so can't be used to anticipate these behaviours, which is why the documentation is so important.

@richardhauer -- Richard, this article now has a Note following the initial paragraph; please let me know if there are other places in the documentation that could use this Note:

Thanks @WilliamAntonRohm  I did see the update - that's very prominent!
I do try to provide feedback where I spot things - I think that the MS documentation is amongst the best across the many systems that I have to use, so it's great to be able to contribute here and there when I can.

@richardhauer -- Richard, thank you for your interest and that compliment!

@richardhauer -- Richard, this article now has a Note following the initial paragraph; please let me know if there are other places in the documentation that could use this Note:

This is perfect! Thank you. I spent far too long digging into the nuances of why a pipeline trigger wasn't behaving correctly over a capitalization mistake. The reason I was so upset is I dug through the Microsoft docs for hours trying to figure out what the issue was.


[bug] NextJS i18n config is being ignored

Describe the bug
Use NextJS i18n config in your starter and you'll see that the config is not active with the current setup of NextJS
To Reproduce
Add a i18n config to the starter and try to access a translated route.
I think its related to the next-compose-plugin but its hard to tell. I tried to change the config without the plugin but that breaks especially the sheet component of Tamagui.
It would be great to remove the plugin from the next.config.js to reduce the complexity of the starter setup.
Based on https://github.com/cyrilwanner/next-compose-plugins/issues/59#issuecomment-1192523231 it seems that the plugin is not maintained any longer.

@natew I updated the tamagui-extras to showcase this:
https://github.com/dohomi/tamagui-kitchen-sink/blob/master/apps/next/next.config.js#L68
You can call /de or /fr on the root of the website and it will result in 404 because the config is not been forwarded correctly The main suspect of this is next-compose-plugin, I tried to remove it in my config. The i18n was back but I had very weird UI issues with popovers and sheets.

after removing next-compose-plugin the issue is gone


[SYM-4767] Runtime Connector Module Version 2 Upgrade Guide

Summary

Adds an upgrade guide for Version 2 under docs/
Links to this upgrade guide from the main README.md

Current dependencies on/for this PR:

main

PR #7   👈

This comment was auto-generated by Graphite.

the implication here being that this is an optional migration and nothing will break if you keep it as it is currently. Is that correct?

Hmm good call out. Theoretically there is nothing wrong with declaring the sym_integration.runtime_context and the sym_runtime.this explicitly. Though if you don't remove the sym_integration.runtime_context and use the one built into the module, you will need to refactor the settings because the module no longer has a settings output.
I'll reword this to recommend using the sym_integration output by the module, since the permission_context settings a pretty confusing to declare explicitly.


setting "verify: true" is causing alexa app to timeout from echo devices

When I set the flag for verify to be true it works when I try to check my endpoint from a non-echo device.  It properly returns a 401 error message:
{
  "status": "failure",
  "reason": "The signaturecertchainurl HTTP request header is invalid!"
}

However, when I try to test the app from the Amazon Alexa dev website or any echo devices, it throws an error that the requested skill has taken too long to respond.
Switching the flag back to false or removing completely and it goes back to working from echo devices but obviously it is going to fail certification.

I don't think middlewares are being handled correctly. There seems to be a lot of conflicting bodyparser related activity in the code:
https://github.com/alexa-js/alexa-app-server/blob/master/index.js#L166
this line declares a body parser before pulling in the raw body (https://github.com/alexa-js/alexa-app-server/blob/master/index.js#L171)
there is also installation of the alexa-verifier-middleware on line 85, which overlaps with line 171:
https://github.com/alexa-js/alexa-app-server/blob/master/index.js#L85
This is kind of a mess. I suspect this is why @cpup22 is having problems. Seems also possibly related:
https://github.com/alexa-js/alexa-app-server/issues/21

#35 might also be related?

Another thing to note, for some reason, the alexa-verifier-middleware is loaded after the url and json body parsers are loaded.

@tejashah88 are you available to chat on google or skype or slack? this will be too hard over github messaging.

Yes, I'm available to chat. I can do either slack or google.

I just pinged you on gchat

@cpup22 I have am incomplete fix in https://github.com/alexa-js/alexa-app-server/pull/64, and I have been using a test project from https://github.com/dblock/alexa-app-server-hello-world running on Heroku for testing this. If you want to see quickly if it solves your problem, you can try
  "dependencies": {
    "alexa-app-server": "dblock/alexa-app-server#a-little-closer-56"
  }

@dblock I updated and did an npm install and see the following...
lisaseacat@meanstack-bno-vm:/opt/bitnami/apps/myapp$ npm install
<EMAIL_ADDRESS>/opt/bitnami/apps/myapp
└─┬<EMAIL_ADDRESS>(git://github.com/dblock/alexa-app-server.git#fb76557626c72ee23bd2be8a1a5ee226ac28604b)
  ├──<EMAIL_ADDRESS>(git://github.com/dblock/alexa-app.git#5fa10102b03b4a67448846f2f3d4c1ca0d104a23)
  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>No repository field.
lisaseacat@meanstack-bno-vm:/opt/bitnami/apps/myapp$ npm start

><EMAIL_ADDRESS>start /opt/bitnami/apps/myapp
> node app.js

serving static content from: public
loading server-side modules from: server
   loaded /opt/bitnami/apps/myapp/server/login.js
loading apps from: apps
/opt/bitnami/apps/blindnightout/apps/helloworld/node_modules/alexa-app/index.js:491
    express.post(endpoint, function(req, res) {
            ^

TypeError: express.post is not a function
    at Object.express (/opt/bitnami/apps/myapp/apps/helloworld/node_modules/alexa-app/index.js:491:13)

Looks like the error is coming form alexa-app/index.js  Maybe I didnt' get the changes?? It looks based on the console log that it pulled from your github repo.

Doesn't look like it's using the right alexa-app code, try adding alexa-app: "dblock/alexa-app#test-app-schema-utterances" explicitly to package.json? If you ook at https://github.com/dblock/alexa-app/blob/test-app-schema-utterances/index.js#L491 which it's complaining about it doesn't have this code, but the shipped 2.4.0 version in https://github.com/alexa-js/alexa-app/blob/v2.4.0/index.js#L491 does.

Also, the good news is that #64 has an otherwise failing test for this issue that reproduces the same hang, so once we fix this we're not going to reintroduce a regression in future versions.


Minor: ex5p, ex9p

Two minor changes:

ex5p: description mentioned BlockMatrix but implementation uses BlockOperator
ex9p: the TimeDependentOperator initialization used M_.Height() from ParBilinearForm &M_ which returns GetVSize; semantically, the correct initialization should be TimeDependentOperator(M_.ParFESpace()->GetTrueVSize()). In this particular example, it shouldn't matter since it is a DG space but for a user trying to adopt the example to another FE space in their own implementation it will potentially not work then since the operator should be initialized with TrueVSize.

If the reviewers agree with the change in ex9p, it should also be changed in the same way in examples/sundials/ex9p and examples/hiop/ex9p.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3914
@stefanhenneking
@tzanio
@acfisher + @cjvogl
10/10/23
⌛due 10/24/23
⌛due 10/31/23

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Good catch! I'm attempting to mentally store this in my catalogue of reasons to revisit some of MFEM's inheritance approach.

This looks good
Could also include changes to examples/hiop/ex9p, examples/sundials/ex9p and examples/petsc/ex9p in this PR

Could also include changes to examples/hiop/ex9p, examples/sundials/ex9p and examples/petsc/ex9p in this PR

@stefanhenneking, do you want to do that?

@tzanio Yes, I'll add that change tomorrow.

I've made the same changes to ex9p in examples/sundials and examples/petsc. In examples/hiop, the operator inititation uses Height() of the HypreParMatrix which should be consistent already.
I also made the same changes in examples/ex9 and examples/sundials/ex9 for the same reason.
Note that I didn't run any tests with the sundials or petsc examples since I didn't install mfem locally with those dependencies.

Merged in next for testing...


Feat: Want to change the UI of the Contributors Page and fix dark mode for that

Describe the feature
I want to change the UI of the contributors page which looks more good then current
Like i will show the contributors cards into circles and will add fade up animation to it
I will also fix the dark mode for this page
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@hustlerZzZ  OK


WHERE IS DOWNLOAD LINK!!!????

Where is the download link. ? I have a job to do. don't make my life more complex

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

ID: 45daf2f0-bb22-338f-062b-a9fabcb71a92
Version Independent ID: b6e909fe-15d9-c1cf-c018-d4f6f36ff31f
Content: Download SQL Server Management Studio (SSMS) - SQL Server
Content Source: docs/ssms/download-sql-server-management-studio-ssms.md
Product: sql
Technology: ssms
GitHub Login: @dnethi
Microsoft Alias: dinethi

The download links are the Available Languages section.  Click the name of the language you want SSMS localised in.

Thank you . That gives me 32 bit version. Where is the options to select 64 bit.?

Click on 'Download SSMS' heading above

@NishSG  Thank you for the question.
This was recently updated with large blue syntax near the top of the article.  64-bit is the default.

Please comment below if there are additional questions.

@msebolt Just because the text is blue doesn't mean I think it's a hyperlink. I thought it was just a big heading that had an incorrect style applied to it. I imagine most users don't expect blue heading-sized text to be links. Please add an affordance ( https://uxplanet.org/ux-design-glossary-how-to-use-affordances-in-user-interfaces-393c8e9686e4 ) that makes it an obvious hyperlink by adding an underline or style it as a button.

Or just wording as Click here to Download SSMS :-)  ... sad to say I had to look at comments to get the download link too!

@msebolt Its not 64bit by default, default is 32bit. Please add 64bit download option.

Yeah -- pretty weird. When I couldn't find the download link in the obvious places, I just looked at doing it in another language I knew and saw that English was an option there - how very counter-intuitive. The "Download SSMS" definitely doesn't look like a link and I didn't go anywhere near it.

Kindly improve your instructions on how to Download, just because it is hyperlink no one could assume that clicking there would download the software. Kindly improve the texting like "click here to download SSMS to your local computer".

It's insane that in the year 2020 the people responsible by this page have zero knowledge of the basic principles of usability. This is the type of arrogance that the IT guys are associated with that make the rest of the world waste a huge amount of time (multiply that by the number of downloads of the SSMS) just because someone thought the way he thinks is the "correct" one. Fix the link and don't use one in the title for a section where people expect to have instructions on how to download. Absolutely surreal.


PicklingError When Running helloworld Script

Hi everyone 👋,
I'm encountering a problem when trying to run the helloworld script. The error message I receive is a PicklingError related to multiprocessing. It seems that the issue is because I'm trying to pickle a function (book_ride) which can't be pickled since it's not the same object as services.booking_service.booking.book_ride.
I've attached an image of the error message below for reference.
Steps to Reproduce:
Clone the repository.
Navigate to the helloworld directory.
Run the script using the command python helloworld.py.
Error Message:

PicklingError: Can't pickle <function book_ride at 0x...>: it's not the same object as services.booking_service.booking.book_ride
Additional Context:
From my investigation, it appears that the function book_ride is being referenced incorrectly in the context of multiprocessing, leading to the pickling issue.
Environment:
Python version: 3.10.14
Operating system: W10
Any other relevant details:  conductor-python==1.1.5
Any help to resolve this issue would be greatly appreciated.
Thank you!

I encountered the same issue and found a workaround. Here’s what I did:
    workers = [
        HelloWorker(task_definition_name='hello_task')
    ]
    configuration = Configuration()
    with TaskHandler(workers=workers, configuration=configuration) as task_handler:
        task_handler.start_processes()
        task_handler.join_processes()


Require http-registry URLs to end with a '/'

The url crate normalizes URLs with no path component to end in a trailing slash. This causes the current implementation to use urls containing two slashes for registries without a path component (such as https://index.crates.io//config.json).
This PR resolves the issue by requiring http registry URLs to end in a slash and generating paths by concatenating. A new error message is emitted for http registry URLs that do not end in a slash.
r? @Eh2406

This only affects sparse URLs, as they are not yet stable this isn't a breaking change.
Thank you for the fix!
@bors r+

:pushpin: Commit 2622074d43e256a6b15be16be72f72a7d66b9899 has been approved by Eh2406

:hourglass: Testing commit 2622074d43e256a6b15be16be72f72a7d66b9899 with merge e7c8ba7753bbfc2015754422d6d65bb59c30ea56...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing e7c8ba7753bbfc2015754422d6d65bb59c30ea56 to master...


HuggingFace DEMO运行失败

text to music.
Input: "exciting music"
Output：Error

text to music.
Input: "exciting music" Output：Error

Now the huggingface demo is unstable, we're working on it, stay tuned.


chore: Organize some search components

What's the purpose of this pull request?
It's to address some of the visual inconsistencies in the search components History, SuggestionsTopSearch, and Suggestions.
How does it work?
Fix clickable areas, unnecessary duplicated CSS, padding, fonts, etc.

Before
After

How to test it?
Check the stories for these components here.

Well done 💯 🥳
I've noticed that svg issue on safari is still there. How about we replacing this component?

Well done 💯 🥳 I've noticed that svg issue on safari is still there. How about we replacing this component?

Thaaanks! Replaced it here. It's now working on Safari.


Can i apply the effect ripple_horizontal on the colorLayer or  the node?

Can i apply the effect ripple_horizontal on the colorLayer or  the node?

sorry for late reply, i'm afraid you should try it by your self. note that EffectNodes is just some demos, not implemented in a very general way. so i think it is not a ready-to-use thing, but for reference and inspiration.


Running a gateway?

I don't see any docs on running a gateway for the Firefox extension, nor any command line options in dat. Is there currently a way to do this?

There is a built in http server if you run with --http but not sure of the compatibility with dat firefox extension. There is a gateway listed in the instructions of dat-fox: https://github.com/sammacbeth/dat-fox. Hopefully that one works!

How do you kill the http server after running --http flag?


Anchor Platform: Update RequestOnchainFunds RPC doc

This updates the description of the amount_out field in the RequestOnchainFunds RPC documentation.

Preview is available here:http://developers-pr904.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr904.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr904.previews.kube001.services.stellar-ops.com

Actually I think you'd need to re-do this PR based off the versioned commit


Incorrect Skill Cost calculation

The way discounts are calculated now are giving incorrect values.
Using Revolution's Chance as an example.
In-Game:

cost = Math.round(skill.cost * (1 - discount))
cost = Math.round(30 * (1 - 0.66))
cost = Math.round(30 * (0.34))
cost = Math.round(10.2)
cost = 10
Builder:

cost = skill.cost - Math.floor(discount * skill.cost)
cost = 30 - Math.floor(0.66 * 30)
cost = 30 - Math.floor(19.8)
cost = 30 - 19
cost = 11
And in the inverse case, where the value before rounding is 10.5 or higher, the game would round up to 11 instead of 10.

But, this also seem to be proven wrong by Tenacious Speed being a cost of 10 becoming 4...

Yeah, that's what I meant with Math.round. For most skills, it'll be fine, but some outliers just seem to ignore proper rounding rules in-game?
Here are the in-game costs using this build:
6_42-270-103-208-91-312-131-220-324-158-94-98-321-99-315-102-271-96-92-218-160-21-272-90-16-149-104-95_999

The notable skills that are incorrect here when using Math.ceil are:

Revolution's Chance [10] -66%
Cubelia [18] -66%
Blind Spot Passage [1] -66%

I was really hoping it was us and not the game's poor rounding, but, it looks like you're right.  I can't seem to find a consistent method.  I guess most accurate way would be to add initialCost and classCost fields for every skill.  That's a lot of effort, though.

Could just stick with Math.round and only add initial/class costs for the outliers

Not a bad idea.  I'll probably swap to Math.round, and then end up using getSkillDiscountedCost on all the skills to set default initial/class costs on all the skills.  Then the outliers can be updated as they are found.

Since the outliers are consistent (eg. every 29 base skill cost skill with a class discount ends up costing 10) I ended up adding a skill-cost.json file that contains a map with the base skill costs and their associated initial and class cost discounts.  This file covers all the base skill costs, and is only missing 3 skill cost tiers -- 28 (Gifted), 53 (Asceticism, Double Wide) and 70 (Eclipse, Stargazer) -- because I have not yet gotten a character with those three class-discounted skills.

I can check on those skills later today

For class costs, it is:
28 (Gifted) - 10
53 (Asceticism, Double Wide) - 18
70 (Eclipse, Stargazer) - 24

Thanks, I've updated with these changes.


Overwrite canonical without html with sphinx extension

What changed, and why it matters
To resolve issue #1691 , canonical url updated to
/index.html -> /
and the rest of the pages without .html
Solution
Create a custom Sphinx extension that adds a HTML context event to override the pageurl variable, which is used by Furo to generate the canonical URL.
Demo
https://overwrite-canonical-without.devportal.pages.dev/
<link rel="canonical" href="https://docs.aiven.io/">
https://overwrite-canonical-without.devportal.pages.dev/docs/platform
<link rel="canonical" href="https://docs.aiven.io/docs/platform">

Hi @angelinekwan!
I did the following:

Navigated to https://docs.aiven.io/docs/products/redis/concepts/high-availability-redis and confirmed the incorrect canonical URL, https://docs.aiven.io/docs/products/redis/concepts/high-availability-redis.html
Navigated to https://overwrite-canonical-without.devportal.pages.dev/docs/products/redis/concepts/high-availability-redis and confirmed the correct canonical URL, https://docs.aiven.io/docs/products/redis/concepts/high-availability-redis.

This LGTM!


Google Admob Mediation Is not Showing, Adapter Has Installed

I am trying to show Audience Network ad, AdColony, AppLovin through my admob mediation. However, the only ad which showing are Admob. The rest is not showing properly. AppLovin has ~1% match rate, the rest is 0%
Plugin Version
3.0.0
Steps To Reproduce
Adding adapters to build.gradle
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    implementation 'com.google.ads.mediation:facebook:<IP_ADDRESS>'
    implementation "com.google.ads.mediation:applovin:<IP_ADDRESS>"
    implementation "com.google.ads.mediation:adcolony:<IP_ADDRESS>"
}

I also have set network_security_config.xml
<domain-config cleartextTrafficPermitted="true">
    <domain includeSubdomains="true"><IP_ADDRESS></domain>
    <domain includeSubdomains="true">dsimlife.com</domain>
    <domain includeSubdomains="true">id1.dsimlife.com</domain>
</domain-config>

Here is the log for adapters
com.google.android.gms.ads.MobileAdsAdapterInitializationState.ready
com.google.ads.mediation.facebook.FacebookMediationAdapterAdapterInitializationState.ready
com.google.ads.mediation.applovin.AppLovinMediationAdapterAdapterInitializationState.ready
com.google.ads.mediation.adcolony.AdColonyMediationAdapterAdapterInitializationState.ready

I have no clue why the only ad showing is Admob ad only. I have set everything fine.

Configuring Ad Unit Mapping in mediation
Setting waterfall
Adapter installed successfully

Does this plugin does not support mediation?

Hi @flameblue59
Mediation has been supported. You can take a look at these resources::

Documentation: https://developers.google.com/admob/flutter/mediation/get-started
Sample code: https://github.com/googleads/googleads-mobile-flutter/tree/main/samples/admob/mediation_example

If you have issues during implementation, you can search for the issue at this repository as well, for eg: mediation filter. Please take a look at it and check if there is any useful information.
Also, regarding match rate, it depends on many other factors of production data. If there's no more information that can identify if this is a plugin issue, it's not easy for us to investigate.

This is so similar to my previous #issue845  We also see the most drops on mediation networks.


test.utils.assert_verbose_allclose has multiple bugs

🐛 Describe the bug
False when diff is nan
https://github.com/linkedin/Liger-Kernel/blob/ce71d59b0b0894f9f3e7512f5a3bf3780c5a1499/test/utils.py#L59
condition is False when num_mismatched is 1.
https://github.com/linkedin/Liger-Kernel/blob/ce71d59b0b0894f9f3e7512f5a3bf3780c5a1499/test/utils.py#L71
I found these bugs when tweaking current test files. Some implementations might be wrong if those tests are relied on this function.
For example, KLDiv can't pass the unit test if we simply replace assert_verbose_allclose with assert torch.allclose()
Reproduce
No response
Versions
❯ python -m liger_kernel.env_report
Environment Report:
-------------------
Operating System: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35
Python version: 3.10.12
PyTorch version: 2.4.0+cu121
CUDA version: 12.1
Triton version: 3.0.0
Transformers version: 4.44.2

ooops thanks for catching this bug, please feel free to draft a PR! Is KLDiv the only test failing or there are some others too?

I haven't tried others. I'll just make a pr to test them.

ooops thanks for catching this bug, please feel free to draft a PR! Is KLDiv the only test failing or there are some others too?

@yundai424 only KLDiv it seems

@Tcc0403 Can you please check if #262 fixes the issue?


Set library list

Hi
I realise that we may need to update the setLibraryList API to work with all the connections in a pool.
What do you think?
Liam

Current workaround. No idea if it's wise or not.
  for (var i = 0; i < pool.connections.length; i++) {
    await pool.connections[i].connection.setLibraryList(['QIWS', 'QXMLSERV']);
  }

@worksofliam
So After creating the pool you would like to set the library list for each connection, right?
If so, I think what you have would do the trick.
A similar approach is taken for adding connection attributes for each connection in the pool.
See pool.setConnectionAttribute().

Although with the above approach if your pool creates new connections in the case where all other connections are busy, the new connection will not have the library list set.

I think we need a callback that is invoked every time a new connection is created (either in the DBPool class or the underlying connector). That would allow the application to reliably set the library list in one code spot, and would also allow the application to do any other job setup (for instance using QCMDEXC to run CHGJOB)

This would be good because I also need to change the CCSID of a job for testing purposes 💯

@ThePrez
That makes sense.
How about we make the pool inherit from the EventEmitter class.
That way users can listen for a "newConnection" event and perform what ever setup they want on the connection.

So how would i use this event "new connection". I do not see any updated documentation to use change library list with a DBPool?

When will the IBM#46 feature be added to the production branch.  I would like to use this in my project.

@beckhamrryyaann
Currently testing and ensuring new Event Emitter features works as expected.
Once the PR lands will update this comment.


Fix ip rule/route flush for ebpf redirection

Please provide a description of this PR:
Fix ip rule/route flush hanlder for ebpf redirection mode for case istio-cni restart after ztunnel running.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[x] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@PlatformLC: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
deb89d4d578b14b3887cc79c7b0985b4bdc2d1b4
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes


Cleanup Duplicated Code in fragment shaders

There is a fair bit of duplicated code between the vr and the data renderers both in the class itself and in the generated code. Further in one getIntensity has been factored out as a function whereas in the other it has not been.

Yes - as you mentionned getIntensity is a good example of things that should be cleaned up and moved out in a helper all shaders can used. In general I do not like very much way shaders codes is implemented and open to suggestions! The main requirement is that we want to be able to generate "custom" shaders "on-demand". (I can detail later if you are interested)

FYI we use to use glslify to generate shaders, that worked great but didn't allow us to build "custom" shaders "on demand".
Custom shaders
If we pass a 16 bits datasets to the shaders, the "unpack" function would by default unpack 16 bits.
Main reason is performance, to cut out as many as possible unnecessary checks.
# before:
unpack (packedValue) {
  if (dataType = 8) {
    unPacked = ...
  } else if (dataType == 16) {
    unpacked = ...
  } ...

  return unPacked;
}

# now:
unpack (packedValue) {
  unpacked = ...
  return unPacked;
}

On demand
That is tightly related to the custom shaders: we do not know we type of data will be loaded, which kind of interpolation the user wants to apply, etc. before hand so we do need to generate the shader code on the client side, once the parameters have been defined.

I'm not sure I follow what the limitations of glslify were. It looks like st the very least parameter exist in require statements https://github.com/glslify/glslify/blob/master/README.md#passing-references-between-modules

So the initial main limitation was that "glslify" was (is?) not able to generate the GLSL code on the fly, in the client, but had to compile the shaders before hand while compiling AMI. That didn't allow us to generate "custom shaders" on the fly in the client. If that is now possible that is a big win and we should definitely look back into it -
Makes sense?

Yes that makes sense. That being said, what is the issue with that limitation? Ie how much customization of the shaders occurs?

So the only reason really was to reduce the number of "else/if" statements in the shaders code in attempt to make it run faster (especially the volume rendering with interpolation ON).
Performance improvement was never formally tested though. (it "seemed" faster)
On the other hand GLSL code is now much less readable so honestly the more I think about it the more it makes sense to switch back to GLSLIFY.
In your experience are the else/if statements expensive in the "raycasting VR" context?


Enabling ipsec encryption in EKS causes node to node traffic to break

Bug report
General Information

Cilium version: 1.8.2
Kernel version: 4.14.186-146.268.amzn2.x86_64
Orchestration system version in use: v1.17.9-eks-4c6976

Enabling ipsec encryption causes node to node traffic to break. This happens in both aws-eni mode, and in cni-chaining mode. Disabling encryption restores connectivity between the nodes.
How to reproduce the issue
Create the cilium-ipsec-keys Secret
kubectl create -n kube-system secret generic cilium-ipsec-keys --from-literal=keys="3 rfc4106(gcm(aes)) $(echo $(dd if=/dev/urandom count=20 bs=1 2> /dev/null| xxd -p -c 64)) 128"

Install cilium with the following Helm chart values.yaml onto an EKS cluster
global:
  masquerade: false

  tunnel: disabled

  cni:
    chainingMode: aws-cni

  encryption:
    enabled: true
    nodeEncryption: false

  nodeinit:
    enabled: true

Enabling nodeEncryption doesn't resolve the issue.
The connectivity test shows something strange (there are no Network Policies other than those created by the test)
NAME                                                     READY   STATUS    RESTARTS   AGE
echo-a-58dd59998d-xhrff                                  1/1     Running   0          3m47s
echo-b-865969889d-77b96                                  1/1     Running   0          3m46s
echo-b-host-659c674bb6-fdwkn                             1/1     Running   0          3m46s
host-to-b-multi-node-clusterip-6fb94d9df6-sjsp9          1/1     Running   0          3m46s
host-to-b-multi-node-headless-7c4ff79cd-x6p2k            1/1     Running   0          3m46s
pod-to-a-5c8dcf69f7-765vz                                1/1     Running   0          3m46s
pod-to-a-allowed-cnp-75684d58cc-bl59z                    0/1     Running   0          3m46s
pod-to-a-external-1111-669ccfb85f-xfj2l                  1/1     Running   0          3m45s
pod-to-a-l3-denied-cnp-7b8bfcb66c-qcx2v                  1/1     Running   0          3m46s
pod-to-b-intra-node-74997967f8-rjvhp                     1/1     Running   0          3m46s
pod-to-b-intra-node-nodeport-775f967f47-ggld7            1/1     Running   0          3m46s
pod-to-b-multi-node-clusterip-587678cbc4-nmgts           1/1     Running   0          3m45s
pod-to-b-multi-node-headless-574d9f5894-xbpkr            1/1     Running   0          3m45s
pod-to-b-multi-node-nodeport-7944d9f9fc-sh9qh            1/1     Running   0          3m45s
pod-to-external-fqdn-allow-google-cnp-6dd57bc859-h76jk   1/1     Running   0          3m44s

cilium-health status suggests things are fine
Nodes:
  ip-10-1-155-156.eu-central-1.compute.internal (localhost):
    Host connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=114.537µs
      HTTP to agent:   OK, RTT=187.031µs
  ip-10-1-30-74.eu-central-1.compute.internal:
    Host connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=894.978µs
      HTTP to agent:   OK, RTT=917.123µs
  ip-10-1-69-144.eu-central-1.compute.internal:
    Host connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=573.843µs
      HTTP to agent:   OK, RTT=751.594µs

cilium-sysdump-20200821-102421.zip
The sysdump shows the 2 Gateway Pods in the openfaas namespace are in CrashLoop. They attempt to connect to the nats service on startup, but fail because they are on different Nodes to the nats Pod. The queue-worker Pod also connects to nats on startup, but in this case succeeds because it is on the same Node as the underlying nats Pod
This is a test cluster so we're able to do whatever is needed to investigate further.

@allanyung Are you still able to reproduce with v1.9.7 or v1.10.0? We have fixed a lot of IPsec issues when running EKS in the recent versions.

It seems I missed before that the issue happens in chaining mode. This is expected as IPsec is not supported in that setup, as documented at https://docs.cilium.io/en/latest/gettingstarted/encryption-ipsec/#limitations.


Windows doesn't allow renaming files that are open (attempt 2)

This is a replacement for #121. All the tests now pass and the changes have been rebased to a recent version of the develop branch.

@Fydon will pull it in.

@cppforlife Should there be a defer close in provider.go to ensure that downloadedFile is always closed? In its current state could there be a resource leak?
Should I make defer close execute where I've added close? It seems that I could do this by splitting part of the function into another function or using embedded functions. The reason I ask this is that it might be confusing to have two close calls in the same function for the same resource, i.e. defer close and close.


[HUDI-6236] write hive_style_partitioning_enable to table config in D…

…eltaStreamer entrypoints
Change Logs
In Hudi 0.10.X, Hudi assumes that hoodie table properties contains the hoodie.datasource.write.hive_style_partitioning configuration value.
As such hoodie.properties should contain this config for all Hudi tables created by Hudi > 0.10.X. However, in DeltaStreamer entrypoints, this configuration is not written to hoodie.properties, which will cause incorrect query results via Spark.
This PR fixes the aforementioned assumptions by ensuring that  hoodie.datasource.write.hive_style_partitioning  is written to hoodie.properties.
Impact
Describe any public API or user-facing feature change or any performance impact.
None
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@boneanxs for visibility

Also, we may need add an improvement for how tables are initialised in the future so that all entrypoints will use a common HoodieTableMetaClient initialiser.
Instead of the current implementation where all entrypoints are dictating their own means of creating a HoodieTableMetaClient.
Once that is done, we will also need a configuration validation component to check the configs of a table.

According the the code in HoodieSparkSqlWriter, there are few more config when building HoodieTableConfig.
https://github.com/apache/hudi/blob/720c9d76c1d281b7a1305a205d195a4f179ce36a/hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieSparkSqlWriter.scala#LL203C13-L203C13
I think it's better we can align DeltaSync according to HoodieSparkSqlWriter.
BTW: totally agree, we should use a unique entrypoint for this HoodieTableConfig builder.

According the the code in HoodieSparkSqlWriter, there are few more config when building HoodieTableConfig.
https://github.com/apache/hudi/blob/720c9d76c1d281b7a1305a205d195a4f179ce36a/hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieSparkSqlWriter.scala#LL203C13-L203C13
I think it's better we can align DeltaSync according to HoodieSparkSqlWriter.
BTW: totally agree, we should use a unique entrypoint for this HoodieTableConfig builder.

Missing configs that are in HoodieSparkSqlWriter.scala, but not in DeltaSync.java.
In initializeEmptyTable()
.setCommitTimezone()
.setDatabaseName()
.set(timestampKeyGeneratorConfigs)

In readFromSource()
.setCDCEnabled()
.setCDCSupplementalLoggingMode()
.setCommitTimezone()
.setDatabaseName()
.setPreCombineField()
.setRecordKeyFields()
.set(timestampKeyGeneratorConfigs)

Apologies again.
Fixed the checkstyle violations and re-executed a mvn clean install on my end.

@hudi-bot run azure


(PUP-6229) Fix unclear error when dynamic expressions used in aliases

A Puppet Type Alias expression may not contain dynamic expressions. The
error issued when it did was not very informative since the actual
source of the dynamic expression was left out. This commit ensures that
it is included in the error message.

Good to merge once travis/appveyor goes green.

CLA signed by all contributors.


Add Versioning

Hi @antoniomika,
can you add versions to your binaries and Docker images to track changes?

@dpishchukhin are you looking for something more than tagging images based on commit hash? Main reason I ask is because I don't distribute binaries other than for docker (but I could look into adding those if you think they'd be worthwhile).

@antoniomika docker image tags are good. It would be great to add sish version command to see a version. the version could be a timestamp from my point of view.

@dpishchukhin I just added auto-building for sish (go binaries added to releases as well as versioned docker images). The docker images are tagged based on git version tag as well as commit hash. I've also added a -sish.version flag to print binary version information. Let me know if you have any other issues!

@antoniomika great! thank you!


Can you upload the trained model

Hello,
I have read the paper and I have found that your model requires at least 48GB of memory to train with RTX 6000 GPU. Is that possible to upload the trained model for cars or chairs dataset ?
Thanks !

Currently training & coming soon!

While the models have to train for a bit more, I've uploaded the current status (~180k iterations in): https://drive.google.com/open?id=1IdOywOSLuK6WlkO5_h-ykr3ubeY9eDig
I'll update the models with the final ones once they're done training!


End of input error iter 0

Looks good but I'll let @applegrain take a look.

Thanks @weilandia!
The sales_analyst shouldn't actually be required on the top level. The SalesEngine can exist without the sales_analyst but the sales_analyst is dependent on the SalesEngine to exist.
Could you please remove it from the spec_helper.rb as well as the pry that's left in the spec file? You can make the changes on your branch and the PR will update when you push.

@applegrain I agree--Wouldn't this mean that we would need to require 'sales_analyst' in the spec in order for the test that's copied below to run?  Otherwise, we'd have to require 'sales_analyst' in our 'sales_engine' file...
    let(:sales_analyst) { SalesAnalyst.new(engine) }

    it "#average_items_per_merchant returns average items per merchant" do
      expected = sales_analyst.average_items_per_merchant

      expect(expected).to eq 2.87
      expect(expected.class).to eq Float
    end```

Waiting for update to send new pull


[Problem] very low recall_rcnn_* on my custum dataset

@sshaoshuai  Thank you for your valuable advice in #24 , i did found some bugs and fixed them !
And i modified the PartA2.yaml configs to fit my custum dataset.

But, the recall_rcnn_* and recall_roi_* still very low when i eval on test sub-dataset. Could you help to provide some more suggestions ? Looking forward to your reply .

In addition, our pointclouds is labeld all 360 degrees, without 2d images. So, i set POINT_CLOUD_RANGE to  [-60, -60, -1.5, 60, 60, 2.5].
Because without 2d bboxes, i'm modifying kitti_object_eval_python/eval.py, so can't provide the mAPs now .
The tensorboard graphs :

detailed experimental control:

I could not help much with the limited information, maybe you should first try a simpler one-stage method like SECOND or PointPillar to achieve normal results.

Thank you so much. Could you provide some suggestions on how to check the quality of rpn rois ?
Does low recall_roi_* relative to voxels and spconv ?

There could be many problems which causes the low performance. Some suggestions are as follows:
(1) Draw the output of your model to see if it is as expected.
(2) Check your labels to see if it is same with KITTI dataset. Especially double check that the input of gt_boxes to the network should be (x, y, z, w, l, h, ry) in the KITTI LiDAR coordinate, here the (x, y, z) is the bottom center of the object.

Thank you very much !

I will visualize points, model input and output soon.
Ours coordinates different from KITTI, so i modified lots of codes (include spconv)  to transfer coords. But, keeped voxels generators and models architecture codes as origin.

@sshaoshuai I have retrained PartA^2 with Pseudo-LiDAR data instead of the original Velodyne data. I am getting very bad results. My initial assumption is that your proposed framework relies on actual LiDAR data (eg. Velodyne) and doesn't perform well with peudo-lidar data. I tested my pseudo-lidar data with SECOND and the results were reasonable. I'd appreciate to have your opinion about this.

@asadnorouzi Sorry I never tested it with the Pseudo-LiDAR. Since the Pseudo-LiDAR is denser and has more noises, the point-based refinement of RCNN stage may not perform well enough. But it is still strange for the very bad results since the RCNN stage should get better results after refine the RPN proposals. I think it may need more time to tune on the Pseudo-LiDAR.

@sshaoshuai Thank you for your reply. I was thinking to let it train longer than 80 epochs. Maybe 160 or even 240 epochs. What do you think?

I don't think more epochs will work well if 80 epochs doesn't work at all, but you could have a try.

@xzswater how did u make your own dataset, can you share something for this? thanks.

@asadnorouzi抱歉，我从未使用伪激光雷达对其进行过测试。由于 Pseudo-LiDAR 更密集且噪声更多，因此 RCNN 阶段的基于点的细化可能表现得不够好。但是非常糟糕的结果仍然很奇怪，因为在改进 RPN 建议之后，RCNN 阶段应该会得到更好的结果。我认为可能需要更多时间来调整 Pseudo-LiDAR。

I custom my own data to train the second model. But I get very low recall ,too. I want to ask how do you solve this problem? Looking forward to your reply！

@clytze0216 What is your custom data? My data was based on pseudo-lidar points. These points were generated by depth map estimator and then fed into the SECOND model. The accuracy will be much lower than lidar-based points, but this low accuracy is expected for pseudo-lidar points.

@asadnorouzi
My custom data is the point cloud information collected and annotated by myself.
I only have 3D XYZ and HWL information and YAW.I've commented out all the code for the 2D coordinate information and any other data that I don't have.I found that the test. PKL file I generated during the data processing phase was very small, around 40KB, and the recall in the eval result was very low, around 20.
Could you give me some advice?This is very important to me. I am looking forward to your reply. Thank you!


Ability to change multiple bytes at once

Hey! Excellent work on doing this extension!
It'd be awesome the ability to change multiple bytes at once, like using ctrl+v to paste a binary content inside a file for example. Is there any effort on this?

Editing the values in place could easily be feasible.
The workflow would be

Select the region to edit.
Hit Shift+Enter - Edit Value.
Paste the hexadecimal content, in a single line, into the dialog prompt.

As for intercepting the Ctrl+V command from the editor, it might not be easy. The editor is in read-only mode, because it doesn't make sense to edit the Address or Offset regions, and it would be hard to enforce the formatting this way.
Another way would be to change the read-only editor for a dynamic HTML page displaying in a WebView, but I don't what to go this way. At least, not for now.

I think the ctrl+v could be initially inside the dialog prompt whereas it changes all selected bytes.

Thanks to @J1T0 and PR #45 we now have a way to edit multiply bytes at the time.
Hit Shift-Enter where you want to start editing, and use the input box to enter or paste a hexadecimal string as long as you want.


[material-ui][Alert] Deprecate composed classes

Part of https://github.com/mui/material-ui/issues/40417
Deprecate 12 composed classes by introducing four atomic ones.

Deprecate Alert's composed classes
Add codemod
Add migration guide

Hey @ZeeshanTamboli! May I ask you to help us review some of these PRs related to the standardization efforts in #40417?


Update integration tests to use TLS enabled DB/storage

The issue resolved by this Pull Request:
Resolves https://issues.redhat.com/browse/RHOAIENG-4254
Description of your changes:

Generated certs for Minio and MariaDB external. Stored these certs in secrets and configmaps, and added them to respective deployments as volumes and volume mounts, so that both Minio and MariaDB are TLS enabled.
Stored the signing certificate in a configmap and applied that in the namespace where DSPA with external connections is being deployed.

Testing instructions

Follow steps in the GH workflow and accordingly deploy and set up changes from this PR on your cluster. Make sure all DSPA resources come up correctly, check DSPO pod logs to ensure connection to TLS enabled Minio and MariaDB is established.
Checklist

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

refactor of secrets can be in a follow up pr
/lgtm
/approve


simplifying country codes

Trying to simplify country code management started in this PR: https://github.com/onomojo/i18n_country_select/pull/18

What's happening with that PR?

Its merged now

Yay! :tada: Thank you 😄

No problem


fix: scanner permissions

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #535 Fixes #534

is this for local scanning?

Codecov Report

Merging #538 (cd7a13d) into main (8844458) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #538   +/-   ##
=======================================
  Coverage   14.92%   14.92%
=======================================
  Files          13       13
  Lines        1501     1501
=======================================
  Hits          224      224
  Misses       1249     1249
  Partials       28       28

Flag
Coverage Δ

unittests
14.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Delay the approval process

Apparently, Porch requires some delay to reflect package revisions, this workaround will give time to mitigate that issue.
google_compute_instance.e2e_instances[0] (remote-exec): + kpt alpha rpkg propose -n default regional-8bcf50b42723a4f7462e1d41264515cdc7546d1b
google_compute_instance.e2e_instances[0] (remote-exec): regional-8bcf50b42723a4f7462e1d41264515cdc7546d1b proposed
google_compute_instance.e2e_instances[0] (remote-exec): + kpt alpha rpkg approve -n default regional-8bcf50b42723a4f7462e1d41264515cdc7546d1b
google_compute_instance.e2e_instances[0]: Still creating... [30m0s elapsed]
google_compute_instance.e2e_instances[0] (remote-exec): regional-8bcf50b42723a4f7462e1d41264515cdc7546d1b failed (Internal error occurred: packagerevs.config.porch.kpt.dev "regional-8bcf50b42723a4f7462e1d41264515cdc7546d1b" not found)
google_compute_instance.e2e_instances[0] (remote-exec): Error: errors:
google_compute_instance.e2e_instances[0] (remote-exec):   Internal error occurred: packagerevs.config.porch.kpt.dev "regional-8bcf50b42723a4f7462e1d41264515cdc7546d1b" not found

Note: This should be fixed later with k8s_wait_exists function

/approve
/lgtm


[WIP] Patch Source Install

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

/platform_tests ref=patch_source_install

/platform_tests ref=suzhoum:patch_source_install

/platform_tests ref="suzhoum:patch_source_install"

/platform_tests


Help me pls

Describe your bug here.
what should i do if i import a character on fnf psych engine and it says "ERROR: No animation found"?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

add the animations

You have to add the Animations, there's literally a tab named "Animation" inside the Character Editor


chore(deps): replace fast-glob with tinyglobby

Summary
Tinyglobby is a fast and minimal alternative to globby and fast-glob.
Related Links
https://github.com/SuperchupuDev/tinyglobby?tab=readme-ov-file#api
Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

Some test cases failed and no plans to go deeper yet.


[BUG] the fields repeat every time I open obsidian

Every time I open Obsidian the fields that I have configured using FileClass are repeated. I have results like the following:

The code that always worked for me is the following
Status:: {"type":"Formula","options":{"autoUpdate":true,"formula":"(current.PagesTotal === current.PagesRead) ? 'FINISHED' : ((current.PagesRead > 1) ?  'FINISHED' : ((current.PagesRead > 1) ? 'READING' : 'WITH STARTED');"}}
this file manage for Query based FileClass settings

What is the version of your plugin currently? this fileClass definition is a legacy one


HomePage enhancement

Is your feature request related to a problem? Please describe.
The homepage of the webpage is quite simple and a lot can be done to make it more engaging and interesting

Describe the solution you'd like
The whole webpage can be designed based on your readme part with the following additions

Addition of front image showing title and suitable background image
Addition of text showing features, demo, technology, and a video player will be added
Animated button (beat animation or similar) for connecting the wallet
Carousel for screenshots
Footer which will directly lead the user to the GitHub page for star

Describe alternatives you've considered
No response
Additional context
No response

#49 already exist for this


Automatically Shut Down the Tree when something is Faulty

Feature Request
Description
When there is an Error in performing the tick, like an unset input, it would be nice if the tree could immediately go into shutdown so one could start fixing the error without first shutting down the tree. The current behaviour is still helpful for debugging but is used less often, so maybe we could make this configurable?

After review, the current behaviour seems fine. Due to some fixes regarding node state transitions, the number of issues when transitioning from ERROR -> SHUTDOWN is significantly reduced, making the current behavior bearable.


"Signature extraction failed"

When trying to download playlists almost I am greeted with this error
Signature extraction failed: Traceback (most recent call last):   File "/usr/local/lib/python3.5/dist-packages/youtube_dl/extractor/youtube.py", line 1191, in _decrypt_signature     video_id, player_url, s   File "/usr/local/lib/python3.5/dist-packages/youtube_dl/extractor/youtube.py", line 1102, in _extract_signature_function     res = self._parse_sig_js(code)   File "/usr/local/lib/python3.5/dist-packages/youtube_dl/extractor/youtube.py", line 1163, in _parse_sig_js     jscode, 'Initial JS player signature function name', group='sig')   File "/usr/local/lib/python3.5/dist-packages/youtube_dl/extractor/common.py", line 796, in _search_regex     raise RegexNotFoundError('Unable to extract %s' % _name) youtube_dl.utils.RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.  (caused by RegexNotFoundError('Unable to extract \x1b[0;34mInitial JS player signature function name\x1b[0m; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
This happens for almost every song. Has anyone else ran into this problem?

Please, just search existing (closed) issues: https://github.com/ritiek/spotify-downloader/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aclosed
Duplicate of:

https://github.com/ritiek/spotify-downloader/issues/341
https://github.com/ritiek/spotify-downloader/issues/385
https://github.com/ritiek/spotify-downloader/issues/388

Update youtube-dl.


BAEL-1868

hey @jzheaux
I did not get this part "What would you think about removing the parent pom directly here? Is the extra layer necessary?"
Let me try removing the logback.xml
Also, adding the module to parent.
Expect the changes by tomorrow.

Hi @jzheaux
I have done the below changes:
Removed the logback.xml
Added the module to parent.


feat(types): Add banner to DiscordPartialGuild

Add banner to DiscordPartialGuild
On a side note: Why do we even have this type? wouldn't it be the same as using Partial<DiscordGuild>? It would also be a better idea to do so because it doesn't seem that discord documents explicitly what are the props that this method will return

upstream: https://github.com/discord/discord-api-docs/pull/6982
fixes #3755

closed in favor of #3768


Fix bug when  extract multiple adjacent words from a string without word boundaries

Dear developers：
There is no doubt that flashtext is an excellent string matching tool. I have already used it on a large number of occasions. But recently I found it in a string without word boundaries (such as a Chinese sentence),
If two words that need to be extracted happen to be adjacent, then it will only be able to extract the first word.
So I made some modifications: when matching words, the index for the next iteration will start at the end of the last matched word.
I have added a new use case  and  It passed all unit tests.

邮件已收到。

@vi3k6i5  Hello,  dear owner . Is this repo still maintained  ？ I found that this repo hasn't updated its code for a long time . If it is no longer maintained, I will no longer wait for the merge of the MR.