parallel build with gnu make 4.4 fails

I seem to get a build issue when using GNU make 4.4 with
'make' 'MAKE_NB_JOBS=0' 'ARCH=x86_64' 'TARGET=ZEN' 'USE_LOCKING=1' 'USE_OPENMP=1' 'USE_THREAD=1' 'libs' 'netlib' 'shared'

with -j16 at the top-level make (openblas is built with a recursive make; not sure if relevant) which fails after some time with
     29      Warning: Possible change of value in conversion from REAL(4) to INTEGER(4) at (1) [-Wconversion]
     30      sgebak.f:253:19:
     31
     32        253 |                K = SCALE( I )
     33            |                   1
     34      Warning: Possible change of value in conversion from REAL(4) to INTEGER(4) at (1) [-Wconversion]
  >> 35      make[2]: *** No rule to make target '../libopenblas_zenp-r0.3.21.a', needed by '../libopenblas_zenp-r0.3.21.so'.  Stop.
     36      make[2]: Leaving directory '/tmp/user/spack-stage/spack-stage-openblas-0.3.21-rqvfhzdue2wzonslpabua3qssw7t6mu2/spack-src/exports'
  >> 37      make[1]: *** [Makefile:125: shared] Error 2
     38      make[1]: *** Waiting for unfinished jobs....
     39      /home/user/spack/lib/spack/env/gcc/gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls -m64 -fopenmp -fPIC -msse3 -msse4.1 -mavx -mavx2 -mavx2 -c -o sgebd2.o sgebd2.f
...

Is there anything that jumps out of the changelog that could explain this? https://lists.gnu.org/archive/html/info-gnu/2022-10/msg00008.html.

Maybe this?

Previously each target in a explicit grouped target rule was considered
individually: if the targets needed by the build were not out of date the
recipe was not run even if other targets in the group were out of date.  Now
if any of the grouped targets are needed by the build, then if any of the
grouped targets are out of date the recipe is run and all targets in the
group are considered updated.

With GNU make 4.3 everything looks fine.

No idea, but the item you quoted reads more like the opposite to me. In your case it seems to tackle "shared" in parallel with the two targets it depends on. (Though judging from the compiler output there could be parts of the static library already on disk). Could there be something else involved that might garble contents or timestamps, like a distributed filesystem or a host filesystem mounted inside a virtual machine ?
Any particular reason why you are calling individual targets instead of a full build ?

Found a hint in the comments to a youtube rant about gmake breaking glibc builds - suggestion was to add --jobserver-style=pipe to the make options (supposedly from a discussion on the LFS mailing list, but apparently this did not work for the author of the video). Could you try ?

Not reproducible so far on openSuSE tumbleweed with gmake 4.4 (though with the caveat that it is a VM with only 10 threads assigned to it, so maybe more&faster cores could change the picture)

Any particular reason why you are calling individual targets instead of a full build ?

It's just to exclude tests

Could there be something else involved that might garble contents or timestamps, like a distributed filesystem or a host filesystem mounted inside a virtual machine ?

It was a regular desktop, with a fast nvme disk

suggestion was to add --jobserver-style=pipe to the make options

Aha, I really picked gmake 4.4 because of its fifo jobserver support, it's much more reliable than pipes.
I'll try to come up with a better reproducer once I have access to the relevant machine again. If it just works for you, maybe it is something machine specific...

I'll try on a bigger system sometime next week.
What's bad about having the tests as part of the build ? Granted they should not fail on fairly common systems but building&running them is not expected to require much time for the potential benefit of catching a bug.

How many processors does actual machine have?
MAKE_NB_JOBS=0 makes openblas override default jobserver. It has to be negative to obey -j99 flag.

@haampie please attach full build logs as spack build bug template suggests. Your guess about not finding file (../libopenblas_zenp-r0.3.21.a) should manifest much earlier when ar is creating that file NOT (or is it there in build dir?)

Got it. You pass -j`nproc` to make and that runs 3 jobs, one for each target, in parallel, no matter MAKE_NB_JOBS setting.
Changed from gmake 4.3. You need to run 3 commands, or patch up default target in makefile to omit tests.
@martin-frbg i have no clue how to work around this, setting dynamic to wait on others still intermixes all 3 parameters.

So the repeater:
upgrade gmake 4.3->4.4
make -j `nproc` list of targets comprising full so file
no longer works.

@haampie actually most other spack packages get built exactly invoking multiple make()-s
e.g.
https://github.com/spack/spack/blob/2516ed181ad05c34a4eb0948ca4bc6bd567a99ba/var/spack/repos/builtin/packages/n2p2/package.py#L84

Nothing specific to OpenBLAS

Question is if this is a regression in GNU make or not.
ELF files are broken/truncated, and if I repeatedly run
make -j `nproc` libs netlib shared

there's ... scary warnings like
ar: warning: ../../libopenblas_zenp-r0.3.21.a(dzsum.o) has a section extending past end of file

out of memory allocating<PHONE_NUMBER>181093428 bytes after a total of<PHONE_NUMBER>2329902304 bytes

:man_facepalming:
I can try and file an issue upstream, to me make all and make [all's prereqs] should be equivalent...

Can you confirm that the default make or make all still works with 4.4 ?

Yeah, make MAKE_NB_JOBS=0 -j16 --shuffle=random works

Ah, if I do make MAKE_NB_JOBS=0 -j16 --shuffle=random libs && make MAKE_NB_JOBS=0 -j16 --shuffle=random shared in that order, it errors:
home/harmen/spack/lib/spack/env/gcc/gcc -O2 -DSMALL_MATRIX_OPT -DMAX_STACK_ALLOC=2048 -Wall -m64 -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=32 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -msse3 -mssse3 -msse4.1 -mavx -mavx2 -mavx2 -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I..  -w -o linktest linktest.c ../libopenblas_zenp-r0.3.21.so -L/usr/lib/gcc/x86_64-linux-gnu/12 -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/12/../../..  -lgfortran -lm -lquadmath -lm -lc  && echo OK.
/usr/bin/ld: /tmp/cct3hvMp.o: in function `main':
linktest.c:(.text.startup+0x536): undefined reference to `iparam2stage_'
/usr/bin/ld: linktest.c:(.text.startup+0x53d): undefined reference to `ilaenv2stage_'
/usr/bin/ld: linktest.c:(.text.startup+0x591): undefined reference to `spotri_'
/usr/bin/ld: linktest.c:(.text.startup+0x5e5): undefined reference to `dpotri_'
/usr/bin/ld: linktest.c:(.text.startup+0x639): undefined reference to `cpotri_'

So maybe there's a prereq missing?
make[1]: *** [Makefile:196: ../libopenblas_zenp-r0.3.21.so] Error 1 shuffle=705871548

Even simpler
$ make clean 1>/dev/null 2>&1 && make shared
/usr/bin/ld: warning: /tmp/ccSsXaW0.o: missing .note.GNU-stack section implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
make[1]: Entering directory '/tmp/harmen/spack-stage/spack-stage-openblas-0.3.21-zwgrfwv5q7nn3icvqos6nuosxohpcyfk/spack-src/exports'
make[1]: *** No rule to make target '../libopenblas_zenp-r0.3.21.a', needed by '../libopenblas_zenp-r0.3.21.so'.  Stop.
make[1]: Leaving directory '/tmp/harmen/spack-stage/spack-stage-openblas-0.3.21-zwgrfwv5q7nn3icvqos6nuosxohpcyfk/spack-src/exports'
make: *** [Makefile:125: shared] Error 2

This also happens with make 4.3

Oh well. Does it work with an added dependeny shared : libs netlib in Makefile line 129 ? (Wonder what having that for something that "could not happen" will break next)


Remove calls to Clear() on protobuf objects that have just been newly constructed

While it is not strictly necessary to call Clear() immediately after constructing a protobuf message object, keep in mind that protobuf message fields are already initialized to their default values during construction. Use Clear() when reusing the same message object to ensure a clean state before setting new data.

Originally posted by @umeirov in https://github.com/eclipse-uprotocol/up-cpp/pull/73#discussion_r1552204185

This will be taken under advisement in the 1.5.8 API rewrite.


MSID: 87092 Version: 2 DOI: 10.1101/2<IP_ADDRESS>8273

MSID: 87092
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>8273
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=87092
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>8273

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/87092v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>8273
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/87092/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [article-title-all-caps] Article title is in all caps - IL-6 SIGNALING EXACERBATES HALLMARKS OF CHRONIC TENDON DISEASE BY STIMULATING REPARATIVE FIBROBLASTS. Please change to sentence case.
error: [journal-ref-article-title] This journal reference (id c1) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c2) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c3) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c4) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c5) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c6) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c7) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c8) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c9) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c10) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c11) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c12) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c13) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c15) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c16) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c17) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c18) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c19) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c20) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c21) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c22) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c23) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c24) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c25) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c26) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c27) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c29) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c30) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c31) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c32) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c33) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c34) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c35) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c36) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c37) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c38) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c39) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c40) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c41) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c42) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c43) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c44) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c45) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c46) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c47) has no article-title element.
warn: [journal-ref-text-content] This journal reference (id c47) has untagged textual content - , NA;, . Is it tagged correctly?
error: [journal-ref-article-title] This journal reference (id c48) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c49) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c50) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c51) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c52) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c53) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c54) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c55) has no article-title element.
warn: [journal-ref-text-content] This journal reference (id c55) has untagged textual content - , jbc. RA118.001987.. Is it tagged correctly?
error: [journal-ref-article-title] This journal reference (id c56) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c57) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c58) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c60) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c62) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c63) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c64) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c65) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c66) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c67) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c68) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c70) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c71) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c72) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c73) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c74) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c75) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c76) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c77) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c78) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c80) has no article-title element.
warn: [journal-ref-text-content] This journal reference (id c80) has untagged textual content - S. KB, L. J, G. JP, M. CL, . Is it tagged correctly?
error: [journal-ref-article-title] This journal reference (id c81) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c83) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c85) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c86) has no article-title element.
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c28) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c69) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c79) has a publication-type='other'. Is that correct?
warn: [mixed-citation-person-group-flag-2] mixed-citation in reference (id=c80) does not have an author person-group. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c84) has a publication-type='other'. Is that correct?
warn: [title-upper-case] Content of  element is entirely in upper case: Is that correct? 'EXPERIMENTAL SECTION'
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplementary File 15: R code file used for the human microarray analysis.'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplementary File 16: ImageJ code file used for the analysis of histological sections from humans.'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplementary File 17: R code file used for the analysis of histological sections from humans.'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplementary File 18: ImageJ code file used for the analysis of histological sections from assembloids.'. Is this correct?
warn: [p-all-bold] Content of p element is entirely in bold - 'Supplementary File 19: R code file used for the analysis of histological sections from assembloids.'. Is this correct?

Complete mess of a reference list, now mostly resolved.


spec: fix regexp

As pointed out by @andaaron in #425, the regular expression proposed there was bogus. It was actually wrong in two different ways. Mea culpa, my apologies.
This fixes it. I wrote a few test cases to check: https://go.dev/play/p/4_iYH4Hao1-
package main

import (
	"regexp"
	"testing"
)

func TestRepoPattern(t *testing.T) {
	r := regexp.MustCompile(`^[a-z0-9]+((\.|_|__|-+)[a-z0-9]+)*(/[a-z0-9]+((\.|_|__|-+)[a-z0-9]+)*)*$`)
	for _, test := range []struct {
		s    string
		want bool
	}{
		{"foo", true},
		{"foo/bar", true},
		{"foo/bar__baz", true},
		{"foo/bar___baz", false},
		{"/foo", false},
		{"foo//bar", false},
		{"foo-------b__x.com", true},
		{"foo-------b__x.com/p----x", true},
		{"foo-", false},
		{"-foo", false},
		{"foo/-bar", false},
		{"foo/bar-", false},
		{"foo-bar", true},
		{"foo----_bar", false},
		{"foo----bar_/x", false},
	} {
		if got, want := r.MatchString(test.s), test.want; got != want {
			t.Errorf("mismatch on %q; got %v want %v", test.s, got, want)
		}
	}
}

Ideally something like the above would be committed for CI testing but perhaps that's a stage too far.

I'm not sure when it happened, but it looks like we've relaxed the restrictions from the Docker spec:

A repository name is broken up into path components. A component of a repository name must be at least one lowercase, alpha-numeric characters, optionally separated by periods, dashes or underscores. More strictly, it must match the regular expression [a-z0-9]+(?:[._-][a-z0-9]+)*.

https://docs.docker.com/registry/spec/api/


Added an explicit support statement for Red forest support

Added an explicit support statement for Red forest support

@rjong999 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Problem with OLED displays

I've build two cornes and have a problem with the OLED displays.
They don't show anything, on both keyboars (all 4 halves). I've tried a swapping them out and switching OLED displays between them. Some of displays are even from a different seller. I noticed, that when I don't have them in, the keyboard reacts a lot slower. All this leads me to the conclusion, that the OLEDs are probably not deffect, and I've done something wrong.
Do you have any troubleshooting advice? Is there a special firmware option, I have to set in QMK to enable the OLED?

Did you solder the jumpers on the top of the PCB?

https://discord.gg/ApVVt6 come join foostan's server for a chat through the issues.

The issue was resolved on the discord servers. The current workaround is to compile the firmware with this fork of qmk . Cause seems to be that the used oled library is incompatible with newer oled modules.
See:

https://github.com/qmk/qmk_firmware/pull/10354;
https://discordapp.com/channels/715899960327012423/742781449731702824/763820765216112650

Please see https://github.com/foostan/crkbd/blob/master/doc/firmware_en.md.


Correcting a typo.

Removing the $.

/close
No response for 2+ months and conflicts not resolved.


[SPARK-48126][Core] Make spark.log.structuredLogging.enabled effective

What changes were proposed in this pull request?

Currently, the spark conf spark.log.structuredLogging.enabled is not taking effect. This PR is to fix it.
Also, this PR enhances the doc for this configuration.
Why are the changes needed?

Bug fix. After the fix, the Spark conf spark.log.structuredLogging.enabled takes effect.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Manual test.
Was this patch authored or co-authored using generative AI tooling?

Generated-by: GPT-4
I used GPT-4 to improve the documents.

cc @panbingkun

Since this PR doesn't have any test coverage, could you elaborate more specifically in the PR description when this doesn't work?

You are right. I just updated the description.

@dongjoon-hyun @HyukjinKwon Thanks for the review. I am merging this one to master


update version of setup-python

GHA shows this warning:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20:
actions/setup-python@v4, jurplel/install-qt-action/action@v3.
For more information see:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Hi! This actions itself is using node.js 16, so we need to do more updates. Please see #222 .

Hi! This actions itself is using node.js 16, so we need to do more updates. Please see #222 .

Why not node20?

Why not node20?

Fixed. I did a wrong modification. @MehdiChinoune , thank you!


Update indicator title for 1.1.1

Thank you!
On Wed, Mar 11, 2020, 9:21 PM brockfanning<EMAIL_ADDRESS>wrote:

Merged #13 https://github.com/OpenDataEnterprise/sdg-metadata/pull/13
into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenDataEnterprise/sdg-metadata/pull/13#event-3121080820,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5WZKSMJTKKMQIDS2AIL6DRHA2H5ANCNFSM4LE5XQSA
.


Update Ruby Supported Versions

the Ruby versions available for a web app for linux are  | Ruby | 2.3.8, 2.4.5, 2.5.5, 2.6.2 |  based on running the command az webapp list-runtimes --linux on Azure CLI

@Ahmad-Al-Ali : Thanks for your contribution! The author, @msangapu, has been notified to review your proposed change.

Hi @Ahmad-Al-Ali. Thank you for the feedback. Due to constant platform updates we don't maintain the revision numbers in this article. I will check with engineering and get back to you.

@Ahmad-Al-Ali : Thanks for your contribution! The author(s) have been notified to review your proposed change. @msangapu

Hi @msangapu-msft  I have removed the revisions. thanks

#sign-off

@msangapu-msft: I'm sorry - only the author of this article, @msangapu, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Array access for higher-order collection operations

I advise to implement real array access for collection items that are arrays, as replacement for the magical #16274.
This PR implements that. :)

/cc @alexbowers

This feels like a terrible hack.
I'd rather we use data_get in __call.
It'll be much nicer syntax too.

Yeah, I prefer the current implementation.

@JosephSilber To be honest, I'm somewhat irritated about that feedback. How is this in any way "dirty" - if anything, the whole feature is dirty. This just follows the implementation of the method and object access proxy feature, and does what we have to do to enable array access - that's a normal PHP feature.
As I've explained in #16274, this is about expectability. If you have objects in your collection, you can access their properties like object properties, and object methods like object methods through the proxy (as if you're dealing with one object, even though it is a whole collection); if you have a collection of arrays, what would be more straightforward then accessing them like you would access a normal array?

this is about expectability

Honestly, there's zero "expectability" here. This is a beautifully magical feature, and you learn to use it the way it was designed.

if you have a collection of arrays, what would be more straightforward than accessing them like you would access a normal array

We've actually had many requests from people to add __get accessors onto the collection, for when the collection contains a single-dimensional associative array (luckily we never did, or we wouldn't have been able to get your delicious higher order operations). Just goes to show people really hate array syntax, and much prefer object syntax (just like the Fluent class).

Doesn't matter whether you call it expectability or consistency. There is a lot of magic going on here, true - that makes it even more important to be consistent with the rest of the language in as many ways as we can - in this case in the way we access the collection items.
Anyway, how do we access array elements with names that aren't allowed as property names now?
$collection->map->field-name; // doesn't work
$collection->map['field_name']; // would work

Anyway, how do we access array elements with names that aren't allowed as property names now?

For those rare cases, you can use curly braces:
$collection->map->{'field-name'};


Allow custom logout handlers when using custom authentication

When using a custom authentication factory:
As of now, one can only select a Logout Success Handler(which is erroneously called logout handler, but I left the old name for compatibility's sake) which is called after the Logout handler was called and the logout was successful.
But custom authentication may need a custom Logout handler.(one may not want to use sessions at all, but custom cookies/etc.)
I've called it logout_clear_data_handler, since it clears data. And by default it should be SessionLogoutHandler();(the prototype for it).

The automatic check has incorrectly failed:
fabbot.io — Some changes should be done to comply with our standards.
I've checked the patch it generated:
It says to remove a newline and then add it again - which obviously is nonsensical statement.

not exactly, it told you to remove the tabs and spaces of those empty lines (if you select the lines you can see there is spaces in your lines and not in the ones added)

Done, thank you for noticing :+1:

The logout handler does not need not need to be configurable, but it should be indeed possible to disable it like it's done in Symfony. So, closing this one in favor of #916 which is more in line with Symfony full-stack behavior.

Wouldn't it be better to do both? I The disabling is important too I think, but choosing a custom logout handler seems a matter of importance. For example I'd rather use custom cookies for my sessions.(I have my reasons).


Iox #489 replace port and process intropection threads with periodic task

Pre-Review Checklist for the PR Author

[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[ ] All checks have passed
[x] Assign PR to reviewer

Notes for Reviewer
This is the first of two PR to replace the thread in the introspection classes with a PeriodicTask and simplify the code. IThe test time with the RouDiEnvironment will also be reduced a little bit (1s posh_modultetests and 2s in posh_integrationtests), since the stopping of the threads is not done by a polling with 100ms period.
The mempool introspection will be done with another PR since it uses an other mechanism without polling and it would take a bit more work to replace it.
Once the tests for the extended PeriodicTask are written, the Draft will be converted in a real PR.
Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior
[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

Post-review Checklist for the Eclipse Committer

[ ] All checkboxes in the PR checklist are checked or crossed out
[ ] Merge

References

Partly closes #489

@dkroenke I will have a look if a monotonic clock is possible with the semaphore.
Regarding the uint64_t getExecutionCount(). In tests, you can always add a counter to the function which will be executed. This could be helpful for other situations though. I would consider it as low prio and create an issue for this. This is a good first issue for a new contributor. Do you agree?

@dkroenke I will have a look if a monotonic clock is possible with the semaphore.
Regarding the uint64_t getExecutionCount(). In tests, you can always add a counter to the function which will be executed. This could be helpful for other situations though. I would consider it as low prio and create an issue for this. This is a good first issue for a new contributor. Do you agree?

@dkroenke regarding the monotonic clock, I just checked the the semaphore documentation and an absolute timeout is required, therefore we cannot use a monotonic clock

@dkroenke regarding the monotonic clock, I just checked the the semaphore documentation and an absolute timeout is required, therefore we cannot use a monotonic clock

Regarding the uint64_t getExecutionCount(). In tests, you can always add a counter to the function which will be executed. This could be helpful for other situations though. I would consider it as low prio and create an issue for this. This is a good first issue for a new contributor. Do you agree?

done with #502

Regarding the uint64_t getExecutionCount(). In tests, you can always add a counter to the function which will be executed. This could be helpful for other situations though. I would consider it as low prio and create an issue for this. This is a good first issue for a new contributor. Do you agree?

done with #502

@elfenpiff 350cb50 has no iox number.

@elfenpiff 350cb50 has no iox number.

oh, and could the one of the reviewer please take care to the reviewer task list ;)

oh, and could the one of the reviewer please take care to the reviewer task list ;)


API 500 errors not reported to console during terraform apply in provider 10.7.1

We have been investigating an incident with JFrog support (case #302187), where 500 errors encountered by the provider were not reported back to the terraform console. Our provider version was 10.7.1.
Instead of console errors, the terraform apply hung with no error output (until we eventually cancelled it and ran it again without errors. Logs are in the referenced case, but we had output like the following):
<snip many entries like the below>
platform_permission.permissions["reponame"]: Still creating... [15m21s elapsed]
platform_permission.permissions["reponame_b"]: Still creating... [1m20s elapsed]
platform_permission.permissions["reponame_c"]: Still creating... [3m20s elapsed]
<no further output, job cancelled>

I see the somewhat recent "Fix http response error handling" commit by @alexhung from March that predates 10.7.1.
If this is still the current behavior of the provider, I hope that we can see API errors propagated to the console in the future. Because apply can apparently hang (like this), it might be helpful to send to console immediately instead of collating errors for later reporting.

@jeidsath The error reporting mechanism is not entirely in the provider's control. The provider is executed as a child process of the Terraform CLI so error reported by the provider is collected through Terraform protocol back to the parent process. It then outputs them to the console, according to its logic.
I'll fix the issue on the provider end but this will not ensure/guarantee realtime reporting of the errors in the logs by Terraform.

@jeidsath Also, if the issue is reproducible then you can set env var TF_LOG=DEBUG to get lots more logging, including detailed HTTP request/response. This may provide you (and us) more clues to why the request is staled.

Thank you, @alexhung I looked over this with the team on Friday, and we're excited to switch to the new provider when it is released.
As the 500 errors are not easily reproducible (we think there was a database connection leak in the prod artifactory), we don't have any immediate testing plans for TF_LOG=DEBUG, but will give it a try if the issue comes up again.
We appreciate the quick followup!


BZ#1501098 Fix for Service UI not taking default language

@miq-bot add_label bug
@miq-bot add_label gaprindashvili/yes
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1501098

Screenshot of fix for navigating to another page after changing language and hitting reload page.  @AllenBW take a look.  Good find by the way.

@chalettu Changes in client/app/core/navigation/navigation-controller.js is conflicting on backport because similar change was made in gaprindashvili PR https://github.com/ManageIQ/manageiq-ui-service/pull/1378. I'm not sure what to take, please clarify.

Second BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1672324
Will take care of the conflict...

Created https://github.com/ManageIQ/manageiq-ui-service/pull/1526 for gaprindashvili


Texture generation ?

Hello, thank you for sharing your work. I have a few questions on your model. My first question is that does your model output obj file?
And my second question is that does your model generate texture ?
Thanks.

Thanks for your interest.

Actually, our model does not output obj file, and we directly render the generated human into the RGB images with Nvdiffrast.
Our model represents the texture field with Texture Tri-planes (see Fig. 2 of the paper).


Routing

can You make a router (plugin or class) for Flextype like Flight php microframwork with regular expresions,named parameters,optional parameters and wildcards ?

Slim Framework implemented


Is there a way to recycle the bitmap

I am having out of memory when using the library. I need to show an image on a single view and when user clicked on the button , I should load a new image using LoadImage on NGraphics. On Android, I usually use image.Recycle and image.dispose before I set image object to null to clear the memory. In this IImage, I can't see a function to recycle teh memory used on the IImage.

Interesting. Just so I understand 100%, what kind of control are you assigning it to and which property? Do you have a little code snippet?


Add support for Load Balancing Policy

What would you like to be added:
The ability for the user to specify the load balancing policy/algorithms used when load balancing requests from the gateway to the upstream / backend.
Why this is needed:
To improve performance/throughput in production.
Examples in Data Plane

Envoy - https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancers
NGINX - https://nginx.org/en/docs/http/load_balancing.html

Examples in Control Plane

Contour - https://projectcontour.io/docs/v1.10.0/config/request-routing/#load-balancing-strategy
Istio - https://istio.io/latest/docs/reference/config/networking/destination-rule/#LoadBalancerSettings

For posterity, this has been brought up a few times. Here's some of the prior art:
#1074 #992 #912
Historically we have landed on policy attachment being the suggested method to handle this, however I'm personally OK with seeing where this goes. @youngnick and @robscott should weigh in.

thanks @shaneutt for surfacing all the prior issues ! would ideally like to see this as a native noun rather than a policy  attachment

I'm with you that this would be good. To make it happen we're going to need someone who's dedicated to championing it, teasing out all the issues and pushing it forward as a GEP. I think getting this right across multiple implementations is going to be a little tricky.

thanks, I see how this feature can be related to the Backend Properties proposal outlined in https://github.com/kubernetes-sigs/gateway-api/pull/1333/files .
From an API perspective, the HTTPBackendRef https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2Fv1beta1.HTTPBackendRef could be a good place to introduce the notion of a backend filter/property to support a load balancing policy.

We don't consider this a blocker for v1.0.0/GA because we have every expectation that it can be done post-GA. We do want this feature, and if any community member is interested in taking it on please do.
/help

We want this feature, but we consider it low priority until v1.0.0/GA is complete and don't believe we will have bandwidth for it until then.


[MB-7047] Wizard Refactor: Orders info & upload

Description
Explain a little about the changes at a high level.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
echo "Code goes here"

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:

It looks like you are attempting to bypass a linter rule, which is not within
security compliance rules.
** Contains a rule that is not in the permitted eslint list. You are free to disable only: (
no-underscore-dangle
,prefer-object-spread
,object-shorthand
,camelcase
,react/jsx-props-no-spreading
,react/destructuring-assignment
,react/forbid-prop-types
,react/prefer-stateless-function
,react/sort-comp
,import/no-extraneous-dependencies
,import/order
,import/prefer-default-export
,import/no-named-as-default
) **
Please remove the bypass code and address the underlying issue. cc: @transcom/Truss-Pamplemoose

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

Messages

:book:
:link: MB-7047

  Generated by :no_entry_sign: dangerJS against 0b3383412699b114493b83d9773e0c5f90a0ee66


Unit tests for within subjects

unit tests for getAllExperimentCondition and markExperimentPoint, simple/factorial individual/group/withinsubject

Is this good to get merged into the branch so we have all of the testing in there in the main PR?

Oh, let me pull in the updates from the branch and make sure it merges successfully


java.util.EmptyStackException In Compiling/Running Tests

In running the tests in https://github.com/lafernando/ideamart, I get the bad/sad error after a while, and it shows an EmptyStackException in "ballerina-internal.log". The log file is attached herewith.
ballerina-internal.log

This issue occurs in Ballerina 0.981.0. if you try to build the project with "ballerina build", you will get the above mentioned issue. Please check and see if the root issue is fixed for the latest version in the compiler.

@lafernando This occurs due to the cyclic import import laf/ideamart; in the test.bal file.
The latest compiler (tested on v1.0-beta) doesn't allow to have cyclic imports. It logs the below error, and continues the compiling all the way up to the  DFAnalyzer phase without crashing.
error: laf/ideamart:0.2.0::tests/test.bal:3:1: cyclic module imports detected 'laf/ideamart:0.2.0 -> laf/ideamart:0.2.0'

Great, thank you for the explanation. So this issue is fixed now.


Generating JavaDoc and Sources for Jitpack

As title and Commits say, I changed the pom.xml to generate a javadoc.jar and a sources.jar for convenience when using JitPack.

Thanks, this will be very helpful.


⚠ ClamAV has degraded performance

In 5b645ef, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in ec0ab66.


fix(cds): return local cluster endpoints per  port

Description:
The getLocalServiceCluster function was returning an xds cluster with endpoints based on Kubernetes service endpoints when it should have been building local cluster endpoints based on the port specified in the service spec. i.e. <IP_ADDRESS>:
As a result, there were 18 extra, duplicate  entries in the envoy local clusters that were being programmed per Kubernetes service endpoints (or Pod replicas)
This PR fixes the getLocalServiceCluster to return a local cluster with endpoints based on the Kubernetes ports rather than the Kubernetes Service endpoints. The tests in the clusters_test.go have been converted from gingko to use the go testing framework and tests for getLocalServiceCluster has been added.
To see the issue exposed in a test, please pull down this branch and checkout the commit sha 9f952062e652ba66d4fb2cc46cb663217bef5088 and run the tests. You can also check out that commit, run the demo, play with the replica count on bookbuyer and inspect the clusters in the envoy admin UI to see the duplicate entries.

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [X ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [X ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution? No

Codecov Report

Merging #2478 (50ddb6e) into main (c863662) will increase coverage by 0.41%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2478      +/-   ##
==========================================
+ Coverage   58.55%   58.97%   +0.41%
==========================================
  Files         153      154       +1
  Lines        6906     7001      +95
==========================================
+ Hits         4044     4129      +85
- Misses       2847     2857      +10
  Partials       15       15

Flag
Coverage Δ

unittests
58.97% <100.00%> (+0.41%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/service/types.go
82.35% <ø> (ø)

pkg/catalog/xds_certificates.go
93.13% <100.00%> (+0.28%)
:arrow_up:

pkg/envoy/cds/cluster.go
98.96% <100.00%> (+2.16%)
:arrow_up:

pkg/catalog/fake.go
82.00% <0.00%> (-6.89%)
:arrow_down:

pkg/injector/patch.go
72.09% <0.00%> (-1.25%)
:arrow_down:

pkg/catalog/mock_catalog.go
0.00% <0.00%> (ø)

pkg/kubernetes/mock_controller.go
0.00% <0.00%> (ø)

pkg/utils/serviceaccount.go
100.00% <0.00%> (ø)

pkg/debugger/proxy.go
5.71% <0.00%> (+0.15%)
:arrow_up:

pkg/kubernetes/client.go
86.71% <0.00%> (+0.75%)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


The selectEntityAction() method signature has the wrong return type

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
When calling the query method selectEntityAction() with no parameters (no EntityActions type provided) the returned type is an EntityAction generic type with the entity type as the inner type, when it should have an inner type of ID[] in the return type.
Essentially, the method signature states that it returns an EntityAction<EntityType>, but in reality it is returning an EntityAction<ID> (similar to the method overload that has an action type parameter supplied as the first parameter, except also wrapped in an EntityAction type to determine the type of EntityAction that occurred).

Expected behavior
The actual data returned in the ids property is the IDs of the entities but they have been given the type of the actual entities themselves which means you have to cast them as any as ID[] in order to work with them.
Minimal reproduction of the problem with instructions

Call the following (with no parameters): query.selectEntityAction().subscribe(action => console.log(action.ids));
Set or update entities in the store.
The console will show a list of IDs, and not a list of objects.

I created a really rough StackBlitz that shows the console.log(action.ids) returning an array of IDs and not a single object as the method return type implies:
https://stackblitz.com/github/rlminqqq
What is the motivation / use case for changing the behavior?
The TypeScript type signature doesn't match the actual type, which is misleading and forces developers to cast as unknown or any and back to the actual type before it can be reliably used.
Environment

Angular CLI version: 7.3.9
Angular Core version: 7.2.15
Akita version: 4.9.3

Browser:
- [x] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

I've just seen that this is fixed in 4.10.x - I'm updating the package now and I'll close it if I can verify that it's fixed.

Yep! It's sorted in 4.10.x, sorry I'll close it now.


add support for specifying badge format

still uses svg by default and adds support for multiple badge formats. I have to use png since I want to show this badge in the README of a Github repo. Github blacklists linking to svg files due to security concerns so I have to use some other image format.

Coverage increased (+0.07%) to 92.241% when pulling 3cad535898d5e7b3a9a31597bd458514295b67b4 on shime:feature/add-format-option into f84bda6093f052ab1b0dbc71b213356e6d3830dd on intuit:master.

@shime thanks for providing that!

@marcellodesales thanks for writing this plugin, it's really useful.


⚠ Bofrost.be has degraded performance

In 38a9712, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1680 ms

Resolved: Bofrost.be performance has improved in 9b47918.


Add Readme for the project

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Environment Variables Missing when Attempting to hit OODT File Manager API

I worked with @chrismattmann on this last night but when I tried to connect first to the OODT Product Service API using DRAT, I ran into two issues:

The Wiki page seems to be out of date (https://cwiki.apache.org/confluence/display/OODT/File+Manager+REST+API) since it says the API URLs are http://host/prodserver, when they now are http://host/fmprod

Several environment variables are missing by default, which cause 500 errors when hitting these URLs:
To use the Product Service APIs for File Manager, you need to set $FMPROD_HOME, which is defined as $DRAT_HOME/webapps/fmprod.

Hi @sfrancus

The Wiki page seems to be out of date (https://cwiki.apache.org/confluence/display/OODT/File+Manager+REST+API) since it says the API URLs are http://host/prodserver, when they now are http://host/fmprod

This has been addressed, I've just updated the wiki. Thank you for the attention to detail.

Several environment variables are missing by default, which cause 500 errors when hitting these URLs:
To use the Product Service APIs for File Manager, you need to set $FMPROD_HOME, which is defined as $DRAT_HOME/webapps/fmprod.

This is not true... I am able to use DRAT no problems with the following set.
124 #DRAT
125 export DRAT_HOME=$USR_LOCAL/drat/deploy
126 export WORKFLOW_HOME=$DRAT_HOME/workflow
127 export FILEMGR_HOME=$DRAT_HOME/filemgr
128 export PGE_ROOT=$DRAT_HOME/pge
129 export PCS_HOME=$DRAT_HOME/pcs

Hope this helps.

Hey @lewismc @sfrancus is trying to use the underlying FMProd OODT service which by default you don't need to run DRAT, but for Proteus is needed to show the UI. @sfrancus can you help us update the wiki?

testing slack integration

Hi @chrismattmann @sfrancus sorry, absolutely no context over and above trying to reproduce this myself and succeeding.
Issue description does not mention Slack but I am VERY interested to hear what you guys have in mind (although now I have an idea).

+1 keep open folks... batter away sorry

@sfrancus if you require write access to OODT wiki then please ask one of us. If not then please fire away and put the use case there. Thanks @chrismattmann for reopening

@lewismc
So this issue occurred since for Proteus we're trying to get the last 20 files ingested by DRAT, which we can access via the File Manager RSS field (something like localhost:8080/fmprod/viewRecent?channel=ALL). However, when I hit that endpoint on my DRAT instance in-browser it returned:
javax.servlet.ServletException: null/rssconf.xml (No such file or directory)
org.apache.oodt.cas.product.rss.RSSProductServlet.init(RSSProductServlet.java:116)
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:542)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProto
@chrismattmann worked with me to resolve the issue and figured out that in one of the context.xml files $FMPROD_HOME was being referenced but was not set as an environment variable. He then told me to copy the relevant files
(mkdir -p $DRAT_HOME/webapps/fmprod
chrismattmann [11:10 PM]11:10
cp -R $DRAT_HOME/tomcat/webapps/fmprod/WEB-INF/classes/*.xml $DRAT_HOME/webapps/fmprod
chrismattmann [11:10 PM]
then set
chrismattmann [11:10 PM]
$FMPROD_HOME to $DRAT_HOME/webapps/fmprod)
And restart Tomcat, which worked.

So... is this a bug?
Do you guys have a branch for Proteus?

Unfortunately we don't have a branch, we forked it. Here's the link:
https://github.com/sfrancus/drat
However we haven't changed any drat-specific code, all our changes are in the folder proteus.

Can you make a branch for drat? Do you want me to?

A branch for Proteus in Drat, or a drat-branch in my Proteus fork?

I am asking if you are working on a local branch which you push to remote @chrismattmann but on a branch apart from master?
Is there now 2 different DRAT codebases?

So my team has been working on a separate DRAT codebase (https://github.com/sfrancus/drat) which I forked a month ago. We have individual branches on that fork. When we had a stable build we planned to merge back to the main DRAT project.

Fantastic. I saw some screen shots and I wondered which codebase they came from. This sounds excellent.

I think so. @chrismattmann hasn't communicated any huge issues about the fork vs branch, and we made it clear that we aren't changing anything in DRAT/OODT (all we require is that there's no breaking changes, we won't use any gotcha hacks, just the promised API).

Sounds grand. Really look forward to seeing a UI in DRAT. Is this ticket an issue anymore?

yeah we're good here - I told them to fork and dev and make pull requests from their fork.

the final home for proteus is here in my DRAT, which is the canonical upstream for the project.

fixed


System get flooded with openvswitch mount points after restarting skydive agent container

I'm reporting a bug.
Version: 0.22
Deployment environment: Skydive cluster running inside Docker containers as part of kolla-ansible deployment
Description: The total number of mount points to /run/openvswitch grows exponentially each time the skydive-agent container restarts
[root@server214 ~]# cat /proc/mounts | grep /run/openvswitch |wc -l
31
[root@server214 ~]# docker restart skydive_agent
skydive_agent
[root@server214 ~]# cat /proc/mounts | grep /run/openvswitch |wc -l
63
[root@server214 ~]# docker restart skydive_agent
skydive_agent
[root@server214 ~]# cat /proc/mounts | grep /run/openvswitch |wc -l
127

Hi,
It seems to be more related to kolla images than Skydive itself. I would suggest to open a bug here: https://launchpad.net/kolla.
Thanks

Yeah, silly me, closing.


Thoughts on interactivity

If the server decides an initial state, how do we serialize this and deliver it to the client?

Do we just not?
Do we assume that client will do its own data fetching? Potentially really wasteful
It's probably too important to discard, the client should really be aware of what its state is so it doesn't have to refetch.

How do we know what our view function is on the client?

pub fn view(model) {
  html.p_text([], "The count is " <> int.to_string(model.count))
}

The count is 0

pub type Document {
  Document(
    doctype: Option(String),
    html_attrs: StringBuilder,
    body_attrs: StringBuilder,
    head: StringBuilder,
    body: DocumentContent,
    scripts: List(String),
  )
}

pub type DocumentUpdate(a) {
  DocumentUpdate(title: String, body: List(html.Node(a)))
}

pub type DocumentContent(model, a) {
  DocumentContent(fn(model) -> DocumentUpdate(a))
}

pub type Document {
  Document(
    doctype: Option(String),
    html_attrs: StringBuilder,
    body_attrs: StringBuilder,
    head: StringBuilder,
    body: DocumentContent,
    scripts: List(String),
  )
}

pub type DocumentUpdate(a) {
  DocumentUpdate(title: String, body: List(html.Node(a)))
}

pub type DocumentContent(model, a) {
  DocumentContent(fn(model) -> DocumentUpdate(a))
}

I'm not sure if Nakai needs to solve this. You can (and probably should) just go the HATEOAS route and just put all of the state into the html. Updates can be done using htmx, AJAX or a plain full page reload.
All "hidden" state that is too important to throw away but is needed on the next request can be encoded just like that.
html.input([
  attrs.type_("hidden"),
  attrs.name("my_secret_data"),
  attrs.value("I like gleam")
])

No matter how you implement interactivity for your application, it is not the responsibility of the html rendering itself.

yeah, I created this issue before lustre existed, so I'm not really that invested in making interactivity nakai's problem anymore. I think embracing htmx would be an interesting direction forward.

0.10 (1.0-rc, sort of) has removed all of the experimental stuff, and no longer provides any sort of interactivity primitives. anyone looking for those would likely be well served by simple inline scripts, something like htmx, or just using lustre instead.


XM_CALLCONV

MSDN:

In addition to the type aliases, you must also use the XM_CALLCONV annotation to make sure the function uses the appropriate calling convention (__fastcall versus __vectorcall) based on your compiler and architecture. Because of limitations with __vectorcall, we recommend that you not use XM_CALLCONV for C++ constructors.

MSDN:

The __vectorcall calling convention specifies that arguments to functions are to be passed in registers, when possible. __vectorcall uses more registers for arguments than __fastcall or the default x64 calling convention use. The __vectorcall calling convention is only supported in native code on x86 and x64 processors that include Streaming SIMD Extensions 2 (SSE2) and above. Use __vectorcall to speed functions that pass several floating-point or SIMD vector arguments and perform operations that take advantage of the arguments loaded in registers.

Given these two documentation snippets, I wonder why XMLoadX (e.g. XMLoadFloat2, etc.) use XM_CALLCONV, since no XMVECTOR or XMMATRIX (or some type aliases) are passed as arguments for these functions?

The load functions are annotated with XM_CALLCONV to take advantage of the __vectorcall register semantics for return values.  This blog post talks a bit about the convention including this comment:

The return value of type HVA/HFA is returned via XMM0(/YMM0): XMM3(/YMM3), one register per element.

The MSDN __vectorcall also states:

Results of __vectorcall functions are returned by value in registers when possible. Results of integer type, including structs or unions of 8 bytes or less, are returned by value in RAX. Vector type results are returned by value in XMM0 or YMM0, depending on size. HVA results have each data element returned by value in registers XMM0:XMM3 or YMM0:YMM3, depending on element size. Result types that don't fit in the corresponding registers are returned by reference to memory allocated by the caller.

TL;DR: Normally in the x64 __fastcall the XMM0L is only used to return float or double values, so vector return types are returned on the stack with RAX pointing to that address. With __fastcall it can return XMVECTOR in XMM0 and XMMATRIX in XMM0:XMM3.

Thanks for the clarification.


fix: block only students

Fixes #144
This PR fixes an issue that was blocking instructors and students from accessing the superset instance.
This PR removes the permissions that don't belong to the Instructor role.
Screenshots

Thanks for the pull request, @Ian2012!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@bmtcril should I remove the instructor access to list the charts and to see saved queries in the home page?
They already don't have access to those assets

@bmtcril should I remove the instructor access to list the charts and to see saved queries in the home page?
They already don't have access to those assets

Makes sense to me, thanks for fixing this up

@bmtcril I wasn't able to remove these permissions without generating a really annoying error message:

Ugh, ok, we'll leave them then.

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


How to remove some buttons from cvat-ui

My actions before raising this issue

[ ] Read/searched the docs
[ ] Searched past issues

Provide a general summary of the issue in the Title above
Expected Behaviour
I wanna remove some buttons from cvat interface like cuboid and elipse
Current Behaviour
I didnt find how to redesign. I don't know what to change in cvat-ui
Possible Solution
Not obligatory, but probably my solution migth  be in there > cvat/cvat-ui
Context
I wanna remove some buttons from cvat user interface as i show in the picture below

how can i remove these buttons from the interface and update cvat-interface
Your Environment
I am using lastest cvat version
Next steps
You may join our Gitter channel for community support.

@nmanovic hi sir. Maybe you can help me about this topic ?

@arcibiyo , at the moment it is possible only with source code modification. It is not configured. Please describe your case in more details. It will give us an idea what is the best strategy to do that.

@nmanovic actually ı wanna just use rectangle button (draw new rectangle) to label ojbects and disable other draw buttons.

@arcibiyo , in this case we know about the request. It was asked a couple of times. We will work to resolve the issue. Current idea is to extend the labels specification. Using the labels specification, it will be possible to restrict UI.


config: warn on wip annotations

This is the second step towards
https://github.com/envoyproxy/envoy/issues/17920.
This change will now warn on any usage of an API that is marked as WIP.
Risk Level: Low
Testing: New unit tests
Docs Changes: N/A (should there be any?)
Release Notes: Added
Platform Specific Features: N/A

/retest


5-parameter deformation model

Hello author:
Thank you very much for your work. I would like to ask if you can tell me the formula of the current 5-parameter deformation model.

Did you read the documentation? Everything is described here:
https://mrcal.secretsauce.net/lensmodels.html


It's really complicated

"The key to success is to break down complex tasks into smaller, more manageable steps. Nothing is ever truly difficult when you approach it this way."
Brian Tracy
Or James Conners version:
Nothing is ever truly difficult you just haven't broken it down into simple enough pieces

https://www.linkedin.com/pulse/power-small-simple-actions-unlocking-progress-martin-jackson-mj0qe/


did you figure this out?

No, but I found a workaround: https://github.com/Menci/vite-plugin-wasm/issues/54#issuecomment-2023825089


Context menu actions not functional on Android Chrome

Describe the bug
Tapping the context menu actions (Reply, Like, three dots) highlights the icon but does not perform the action

Which site: dev.phanpy.social AND phanpy.social
Which instance: mastodon.eroticmohel.com

To Reproduce
Steps to reproduce the behavior:

Go to a post with replies
Tap on the body of a reply post
Tap on the "Reply" or "Comment" or even the three dot icons of the context menu
The icon highlights briefly and then the context menu hides, not actually taking the tapped action

Expected behavior
I expect tapping on the Like action of the context menu to Like the status
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/cheeaun/phanpy/assets/242696/5b6f66fd-e605-41a3-abae-45ba0cf4b885
Smartphone (please complete the following information):

Device: Pixel 6a
OS: Android 14 (UQ1A.240205.002)
Browser: Chrome
Version: 122.0.6261.90

Additional context
Add any other context about the problem here.

This is now working on the Dev site


API: feature request to add author/committer date

Gitea version (or commit ref): 1.11.0+dev-481-g1df701fd1
Git version: 2.17.1 or whatever try.gitea.io runs
Operating system: Ubuntu 16.04 or whatever try.gitea.io runs
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes
[ ] No
[x] Not relevant

Log gist: n/a

Description
This is a feature request for the API allowing to add/update/delete files (and commit it):
/repos/{owner}/{repo}/contents/{filepath}
I would like to be able to specify the author date and commit date, just as git commit on the command line allows (--date argument or GIT_AUTHOR_DATE and GIT_COMMITTER_DATE environment variable).
We should also allow the same date formats that git commit itself allows, so not only a single unix timestamp, but also the time zone offset (or even RFC 2822/ISO8601), so that we can actually use local time zones as opposed to only UTC.
Extending the API with optional parameters does not break backwards compatibility, so this should be fine.
CCing @6543 who recently touched this code.
What do you think about this request? Would this change be complex?

first look: I would extend the body, more exact:
from ...

DeleteFileOptions
CreateFileOptions
UpdateFileOptions
... the Identity type has to be extendet ...

but extending IdentityOptions and Identity with a fild not related to itself is ... mad

GitHub [Link] (https://developer.github.com/v3/repos/contents/#parameters-2) do not have this option so adding a optional in-body-param is the way I would do it

what do you thin of:
{
  "message": "my commit message",
  "committer": {
    "name": "Monalisa Octocat",
    "email"<EMAIL_ADDRESS>  },
  "content": "bXkgbmV3IGZpbGUgY29udGVudHM=",
  ...
  "dates": {
    "author": "2014-11-07T22:01:45Z",
    "committer": "2014-11-07T22:01:45Z"
  },
  ...
}

and

https://github.com/go-gitea/gitea/blob/master/modules/repofiles/update.go#L374
https://github.com/go-gitea/gitea/blob/master/modules/repofiles/temp_repo.go#L190
have to be changed ...


Put attachments first

Looks like that comment was spot-on and some email clients are showing
the attachment (and not even inline; just a link) instead of
displaying either of the actual email parts.

LGTM, but don't consider my +1 to be binding :)

:+1: :+1: Let's try it, thanks @leathekd!


mise failed to activate in nushell 0.99.0

Describe the bug
mise failed to activate in Nushell 0.99.0:

To Reproduce

Install nushell 0.99.0
Add to ~/.config/nushell/env.nu

let mise_path = $nu.default-config-dir | path join scripts mise.gen.nu
^mise activate nu | save --force $mise_path

Add to ~/.config/nushell/config.nu

use mise.gen.nu

Expected behavior
Should not have any error when nu starts.
node -v should also work
mise doctor output
version: 2024.10.7 macos-arm64 (2024-10-14)
activated: no
shims_on_path: no

build_info:
  Target: aarch64-apple-darwin
  Features: DEFAULT, NATIVE_TLS
  Built: Mon, 14 Oct 2024 22:13:17 +0000
  Rust Version: rustc 1.81.0 (eeb90cda1 2024-09-04) (Homebrew)
  Profile: release

shell:
  /opt/homebrew/bin/nu
  0.99.0

dirs:
  data: ~/.local/share/mise
  config: ~/.config/mise
  cache: ~/.cache/mise
  state: ~/.local/state/mise
  shims: ~/.local/share/mise/shims

config_files:
  ~/.config/mise/config.toml

backends:
  cargo
  core
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:

toolset:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
env_vars:
  (none)

settings:
  activate_aggressive = false
  all_compile = false
  always_keep_download = false
  always_keep_install = false
  asdf_compat = false
  cache_prune_age = "30d"
  ci = false
  color = true
  debug = false
  disable_backends = []
  disable_default_registry = false
  disable_hints = []
  disable_tools = []
  experimental = false
  fetch_remote_versions_cache = "1h"
  fetch_remote_versions_timeout = "10s"
  go_default_packages_file = "~/.default-go-packages"
  go_download_mirror = "https://dl.google.com/go"
  go_repo = "https://github.com/golang/go"
  go_set_gopath = false
  go_set_goroot = true
  go_skip_checksum = false
  http_timeout = "30s"
  jobs = 4
  legacy_version_file = true
  legacy_version_file_disable_tools = []
  libgit2 = true
  log_level = "info"
  not_found_auto_install = true
  paranoid = false
  pin = false
  plugin_autoupdate_last_check_duration = "7d"
  python_default_packages_file = "~/.default-python-packages"
  quiet = false
  raw = false
  trace = false
  trusted_config_paths = []
  use_versions_host = true
  verbose = false
  yes = false

  [cargo]
  binstall = true

  [node]

  [pipx]
  uvx = false

  [python]
  default_packages_file = "~/.default-python-packages"
  pyenv_repo = "https://github.com/pyenv/pyenv.git"
  venv_auto_create = false
  venv_stdlib = false

  [ruby]
  default_packages_file = "~/.default-gems"
  ruby_build_repo = "https://github.com/rbenv/ruby-build.git"
  ruby_install = false
  ruby_install_repo = "https://github.com/postmodern/ruby-install.git"

  [status]
  missing_tools = "if_other_versions_installed"
  show_env = false
  show_tools = false
No warnings found
1 problem found:

1. mise is not activated, run mise help activate or
   read documentation at https://mise.jdx.dev for activation instructions.
   Alternatively, add the shims directory ~/.local/share/mise/shims to PATH.
   Using the shims directory is preferred for non-interactive setups.

Additional context
Add any other context about the problem here. Consider running mise with --debug or --trace for extra debug info.

Facing the very same issue, closing the one i had opened here as i didn't realized this is an ongoing issue since over a month

I am assuming this is a bug in nushell 0.99, as the change hasn't been documented in their changelog.

Just for the record, this bug exists on v0.100 as well

I ran into the same issue, I managed to solve it by appending the following at top of the generated file
$env.config = ($env | default {} config).config
$env.config = ($env.config | default {} hooks)
$env.config = ($env.config | update hooks ($env.config.hooks | default {} env_change))
$env.config = ($env.config | update hooks.env_change ($env.config.hooks.env_change | default [] PWD))

This will add the default PWD if it does not exist in env_change, I think adding this to https://github.com/jdx/mise/blob/main/src/shell/nushell.rs should solve the issue but I'm not sure since I'm using nixos to setup mise and nushell
I'm using nixos with home-manager for this, so I'm using the following code
{ config, pkgs, ... }:

let
  miseCmd = "${config.home.profileDirectory}/bin/mise";
in
{
  # mise
  programs.mise.enable = true;
  programs.nushell = {
      extraEnv = ''
        let mise_cache = "${config.xdg.cacheHome}/mise"
        if not ($mise_cache | path exists) {
          mkdir $mise_cache
        }

        $env.config = ($env | default {} config).config
        $env.config = ($env.config | default {} hooks)
        $env.config = ($env.config | update hooks ($env.config.hooks | default {} env_change))
        $env.config = ($env.config | update hooks.env_change ($env.config.hooks.env_change | default [] PWD))

        ${miseCmd} activate nu | save --force ${config.xdg.cacheHome}/mise/mise.nu
      '';
      extraConfig = ''
        use ${config.xdg.cacheHome}/mise/mise.nu
      '';
    };
}


Http.SendJsonAsync failed on 0.7

Hi
we try to follow this tutiorial
https://ankitsharmablogs.com/asp-net-core-crud-using-blazor-and-entity-framework-core/
for CRUD operation on V0.3 of blazor Work perfect
but on our 0.7 version when we try to send data with
await Http.SendJsonAsync(HttpMethod.Post, "/api/Employee/Create", emp);
the data not send to api method create and the nav refresh the blazor app :( (stay on creation page)
thanks for your help

hi
thanks for your answer, with the type "button" we have this error :
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 POST http://localhost:57845/api/SampleData/Create application/json; charset=utf-8 72
'dotnet.exe' (CoreCLR: clrhost) : Chargé 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.1.6\System.Diagnostics.StackTrace.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
'dotnet.exe' (CoreCLR: clrhost) : Chargé 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.1.6\System.Reflection.Metadata.dll'. Chargement des symboles ignoré. Le module est optimisé et l'option du débogueur 'Uniquement mon code' est activée.
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware:Error: An unhandled exception has occurred while executing the request.
System.InvalidOperationException: The SPA default page middleware could not return the default page '/index.html' because it was not found, and no other middleware handled the request.
at Microsoft.AspNetCore.SpaServices.SpaDefaultPageMiddleware.<>c__DisplayClass0_0.b__1(HttpContext context, Func`1 next)
at Microsoft.AspNetCore.Builder.UseExtensions.<>c__DisplayClass0_1.b__1(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request finished in 63.5363ms 500 text/html; charset=utf-8
Microsoft.AspNetCore.Server.Kestrel:Information: Connection id "0HLIKVFJ24QQ0", Request id "0HLIKVFJ24QQ0:00000008": the application completed without reading the entire request body.

"thanks for your answer, with the type "button" we have this error :"
Mate, don't you understand what's wrong with the code...?
You should remove the <form> tag
You should also replace the string "submit" with the string "button" in the type attribute. It should be like that:
 <button type="button" class="btn btn-default" onclick="@(async () => await CreateEmployee())">Save</button>

instead of
 <button type="submit" class="btn btn-default" onclick="@(async () => await CreateEmployee())">Save</button>

When you use type="submit", the SendJsonAsync is not called, the form is submitted to the server. This is basic... When you use type="button"; this allow JavaScript to execute, perform Ajax call (fetch API)to the server, and add your lousy employee data, say to a database.
I don't want to speak ill of others, but you should not visit that web site. You are not the first person who have faced such unnecessary issues just because the author of the tutorial himself is lacking any basic knowledge of what he's teaching...
Learn Blazor here: http://learn-blazor.com/getting-started/what-is-blazor/
But start with HTML and some JavaScript
Hope this helps...

Many thanks for your answer @enetstudio


http-max-request-size is not applied to actor response body size

In what area(s)?
/area runtime
What version of Dapr?

1.13.1
Expected Behavior
An actor should be able to return a response body with a payload up to the size specified by the http-max-request-size argument.
Actual Behavior
An error occurs when an actor response body is > 4 MB irregardless of the value of the http-max-request-size argument.
Note that in my testing, the issue is only with an actor response body....not when sending a large request body.
Steps to Reproduce the Problem
To reproduce the problem, I've cloned the AspireWithDapr project and added an WeatherActor which returns ~ 8 MB of weather forecasts. I've also configured the normal API to also return 8 MB.
I've added the --dapr-http-max-request-size 16 parameter to the dapr sidecar, and I can see it is applied in the sidecar logs,
time="2024-04-03T20:23:06.1058837+01:00" level=info msg="Enabled max body size HTTP middleware with size 16 MB" app_id=web instance=DESKTOP-SE6C36R scope=dapr.runtime.http type=log ver=1.13.1

What I'm seeing is that both the service invocation and actor return an error when the --dapr-http-max-request-size is not specified.
However, when it is set to 16, the service invocation endpoint succeeds, but the actor endpoint returns this error:
time="2024-04-03T20:28:33.8753374+01:00" level=debug msg="{ERR_ACTOR_INVOKE_METHOD error invoke actor method: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (7902254 vs. 4194304)}" app_id=web instance=DESKTOP-SE6C36R scope=dapr.runtime.http type=log ver=1.13.1

I also added a method to the actor to accept an array of weather forecasts, and it seems I can send more than 4 MB request to the actor. So the issue is only when returning a response.
Release Note
RELEASE NOTE:
http-max-request-size argument now applies to actor response body message size.

What SDK are you using to invoke the actor?

I'm using the .NET SDK to both invoke and host the actor. But as noted above, the error is logged in the sidecar, which suggested to me it was not an SDK issue.

Just to add some more information...I've tested the scenario again, this time just using curl.
When I call the actor via it's sidecar, the response is successful.

C:\dapr>curl -vk http://localhost:57403/v1.0/actors/WeatherActor/1/method/GetWeatherAsync > NUL
*   Trying <IP_ADDRESS>:57403...
* Connected to localhost (<IP_ADDRESS>) port 57403 (#0)
> GET /v1.0/actors/WeatherActor/1/method/GetWeatherAsync HTTP/1.1
> Host: localhost:57403
> User-Agent: curl/7.84.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: text/plain; charset=utf-8
< Server: Kestrel
< Traceparent: 00-ce578c6cb3748a2ebddad35ab1169a2b-fe05d3fb9f0dfba9-01
< Date: Wed, 10 Apr 2024 12:04:15 GMT
< Transfer-Encoding: chunked
<
* Connection #0 to host localhost left intact

However, when I call the actor, via the 'client' sidecar, I get the error:
C:\dapr>curl -vk http://localhost:57407/v1.0/actors/WeatherActor/1/method/GetWeatherAsync
*   Trying <IP_ADDRESS>:57407...
* Connected to localhost (<IP_ADDRESS>) port 57407 (#0)
> GET /v1.0/actors/WeatherActor/1/method/GetWeatherAsync HTTP/1.1
> Host: localhost:57407
> User-Agent: curl/7.84.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< Content-Type: application/json
< Traceparent: 00-65c671216607b4039e0f213cd8a4d7f3-b731143ebd15e7b9-01
< Date: Wed, 10 Apr 2024 12:04:22 GMT
< Content-Length: 182
<
{"errorCode":"ERR_ACTOR_INVOKE_METHOD","message":"error invoke actor method: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (7902458 vs. 4194304)"}* Connection #0 to host localhost left intact

C:\dapr>

but again, I do see this in the client's sidecar logs:
time="2024-04-10T12:58:56.9051351+01:00" level=info msg="The request body size parameter is: 16" app_id=web instance=DESKTOP-SE6C36R scope=dapr.runtime type=log ver=1.13.1

Hopefully this helps identify the issue

Just to add some more information...I've tested the scenario again, this time just using curl.
When I call the actor via it's sidecar, the response is successful.

C:\dapr>curl -vk http://localhost:57403/v1.0/actors/WeatherActor/1/method/GetWeatherAsync > NUL
*   Trying <IP_ADDRESS>:57403...
* Connected to localhost (<IP_ADDRESS>) port 57403 (#0)
> GET /v1.0/actors/WeatherActor/1/method/GetWeatherAsync HTTP/1.1
> Host: localhost:57403
> User-Agent: curl/7.84.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: text/plain; charset=utf-8
< Server: Kestrel
< Traceparent: 00-ce578c6cb3748a2ebddad35ab1169a2b-fe05d3fb9f0dfba9-01
< Date: Wed, 10 Apr 2024 12:04:15 GMT
< Transfer-Encoding: chunked
<
* Connection #0 to host localhost left intact

However, when I call the actor, via the 'client' sidecar, I get the error:
C:\dapr>curl -vk http://localhost:57407/v1.0/actors/WeatherActor/1/method/GetWeatherAsync
*   Trying <IP_ADDRESS>:57407...
* Connected to localhost (<IP_ADDRESS>) port 57407 (#0)
> GET /v1.0/actors/WeatherActor/1/method/GetWeatherAsync HTTP/1.1
> Host: localhost:57407
> User-Agent: curl/7.84.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< Content-Type: application/json
< Traceparent: 00-65c671216607b4039e0f213cd8a4d7f3-b731143ebd15e7b9-01
< Date: Wed, 10 Apr 2024 12:04:22 GMT
< Content-Length: 182
<
{"errorCode":"ERR_ACTOR_INVOKE_METHOD","message":"error invoke actor method: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (7902458 vs. 4194304)"}* Connection #0 to host localhost left intact

C:\dapr>

but again, I do see this in the client's sidecar logs:
time="2024-04-10T12:58:56.9051351+01:00" level=info msg="The request body size parameter is: 16" app_id=web instance=DESKTOP-SE6C36R scope=dapr.runtime type=log ver=1.13.1

Hopefully this helps identify the issue

That does help a lot, thanks


NP v1.7.0 - Disabling Horse Armor in Config Gives Errors in Log

If you disable the Netherite horse armor in the config, the game logs errors when you enter a world.
Game / world appears to still function and Netherite horse armor no longer in items list, but not extensively tested.
Latest Log:
latest.log

Ah thanks for letting me know, this should be relatively easy to fix, i just thought it wasnt going to be an issue. Its with the crafting recipes

Might actually be affecting anything from this mod when disabled through the config.
Disabled everything (for science!) and the logged errors are quite a bit longer.
latest.log

yeah definitely crafting

fixed with https://github.com/OroArmor/Netherite-Plus-Mod/commit/0b0282d8b4de1482a45c5b70ae481067475a4c06


How to use in docker environment?

My apologies for my ignorance, this is my first time setting this up in a docker environment.
When I tried to dockerize my application that used the sharp library, I encountered
ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.10.0
I found this issue which should solve the problem, but I am having trouble following this and understanding which script to use and how to install it. I tried running the cross-platform compatible build script in docker, but I'm getting something like
 > [ 5/10] RUN bash -c ./sharp-libvips-8.10.6/build/lin.sh:
lovell/sharp-libvips#8 0.420 mkdir: missing operand
lovell/sharp-libvips#8 0.420 Try 'mkdir --help' for more information

This is my dockerfile:
FROM node:12

RUN curl -OL -o v8.10.6.tar.gz https://github.com/lovell/sharp-libvips/archive/refs/tags/v8.10.6.tar.gz
RUN tar -xzf v8.10.6.tar.gz && rm v8.10.6.tar.gz
RUN chmod +x sharp-libvips-8.10.6/build/lin.sh
RUN ./sharp-libvips-8.10.6/build/lin.sh

# Create app directory
WORKDIR /usr/src/my-app

COPY package.json .
COPY package-lock.json .

RUN npm ci

COPY . .

EXPOSE 3030

CMD [ "npm", "start" ]

I appreciate any help. Thank you!

What is the target device, CPU, OS? Is this on ARMv7 or ARM64v8?
I recommend using the latest version of an up-to-date base OS that matches the minimum glibc/musl requirements at https://sharp.pixelplumbing.com/install#prebuilt-binaries and then you don't need to worry about compiling anything.

Hi @lovell, thanks for your reply. What do you mean by base OS? If I'm using a docker container, there's no OS involved, right? Sorry I'm a bit new to this 🙏

After the
COPY . .
I add the following code:
RUN npm uninstall sharp
RUN npm install sharp
or even:
RUN npm uninstall sharp
RUN npm install sharp --platform=linux --arch=x64 --save
I did this, so can sharp be installed inside the container only and in the right environment.
But nevertheless I always get the same error:
/app/node_modules/sharp/lib/libvips.js:82       throw new Error('${vendorPlatformId}' binaries cannot be used on the '${currentPlatformId}' platform. Please remove the 'node_modules/sharp' directory and run 'npm install' on the '${currentPlatformId}' platform.);             ^ Error: 'win32-x64' binaries cannot be used on the 'linux-x64' platform. Please remove the 'node_modules/sharp' directory and run 'npm install' on the 'linux-x64' platform.
I must say that I am trying to use sharp in nestjs (not that it should matter)

@edrichhans Please can you create a standalone repo with a complete Dockerfile that demonstrates what you're trying to achieve.

I had the same situation, but it was solved.
The version of glibc in buster, which is the stable version of debian, is 2.28.
The only official Docker images for Node.js are the ones that use the stable debian version, and you need to compile libvips and sharp to use sharp directly.
The testing version of debian, bullseye, contains glibc version 2.31.
So I created a Node.js image from bullseye and was able to install sharp.
Note that before installing sharp, you need to run npm install -g npm to increase the version of npm.
https://github.com/malt03/docker-node/tree/main/14/bullseye-slim
https://hub.docker.com/repository/docker/malt03/node
@lovell
This seems to be a problem that many people who use sharp in their Docker images run into.
Can you please add this issue to the README or documentation?

@malt03 Are you using an ARM64 CPU?
The libc (glibc, musl) requirements for the prebuilt binaries are listed at https://sharp.pixelplumbing.com/install#prebuilt-binaries

Yes, I am using ARM64.
Thank you. I understand about the requirements document.
It was somewhat difficult to find out what version of glibc in debian and to discover that I can use bullseye to solve it.
However, I just checked and bullseye is scheduled to be released on August 14, 2021, and I think the official Node.js image will be released accordingly, so I felt there was no need to add it to the README or documentation.

@edrichhans Closing due to inactivity but please feel free to reopen with the requested details if further help is required.


Close Microsoft Authenticator app (Android) and return to browser

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

On an Android phone, when I complete the presentation flow using the deeplink, the Microsoft Authenticator app does not close and the user is NOT returned to the browser.
How can I close the Microsoft Authenticator app and return the user to the browser?
Code:
´´´
window.location.href = respPresentationReq.url;
´´´
Greetings Damien

You have to use the back button top right corner to return to the previous app
Closing old issues as sample is updated


Update SvelteKit SSR integration to include information regarding sameSite: 'lax'

after encountering this problem for the third time when building an app with SvelteKit (I keep forgetting that this is an issue and then spending hours debugging this) - I figured it could be nice to add this comment.
feel free to close if you disagree

Thank you but I think it is better the default to remain to Strict.

sure!
just wanted to point out that I did not actually change the default here - I only added a comment


Combine db tests

This change relocates all (non-proprietary) DB tests into a single module, to reduce the amount of boilerplate. It is envisaged that we can clean up these tests further going forward.
Additionally this PR includes changes to reduce the initial memory consumption of MySQL and MariaDB containers for reliability reasons.

As this PR is completely included in #243 but doesn't include some bugfixes that are in the other PR, I'm going to close this one. Seems more straightforward that way.


only send PATCH request for services when necessary

What this PR does / why we need it: only send PATCH request to Kong when the kongIngress changed, this will solve a problem that may result in high database pressure in Kong.
Which issue this PR fixes : fixes #104

Codecov Report

Merging #107 into master will increase coverage by 0.11%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #107      +/-   ##
==========================================
+ Coverage   32.08%   32.19%   +0.11%
==========================================
  Files          33       33
  Lines        2880     2882       +2
==========================================
+ Hits          924      928       +4
+ Misses       1843     1841       -2
  Partials      113      113

Impacted Files
Coverage Δ

internal/ingress/controller/kong.go
1.24% <0%> (-0.01%)
:arrow_down:

cli/ingress-controller/main.go
22.22% <0%> (+2.61%)
:arrow_up:

Continue to review full report at Codecov.

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


Add processing information to QC report

As part of the QC report, we should include information about processing including software information and versions. This may involve modifying the scpcaTools read functions and attaching this information to the SCE metadata and then grabbing it from the SCE to output during the report.

With the current version of salmon (1.5.1) some of the expected files are not being produced (see https://github.com/COMBINE-lab/salmon/issues/688), which may limit our ability to use the processor file output for tracking this information. We will likely want to have some additional way of tracking the command invocation for steps of our workflow with the output files. This may involve additions to https://github.com/AlexsLemonade/scpca-nf, but we should decide here what fields we would like to include.
We should make this flexible so missing information does not result in failure.
Some initial thoughts:
-pipeline: probably a reference to https://github.com/AlexsLemonade/scpca-nf most of the time, with either a release tag or commit id

reference Ensembl 103, etc.
index
filter (emptydrops etc.)

What else would people want to see?


[interoperator] Enable leaderelection

Pull Request Test Coverage Report for Build 2317

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 88.519%

Files with Coverage Reduction
New Missed Lines
%

common/utils/index.js
1
75.66%

Totals

Change from base Build 2315:
-0.008%

Covered Lines:
8634

Relevant Lines:
9411

💛  - Coveralls


CloudFront Invalidation

Invalidate CloudFront after file has been uploaded to S3 so that we serve latest file at data.nextstrain.org.
(Adding the same CloudFront invalidation in ncov-ingest)

Thank you for your feedback @trvrb! I've added the environment variables to the ingest/README in ea63c7f.
I did the following for testing:

I manually uploaded a metadata.tsv file with only two records to s3://nextstrain-data/files/workflows/monkeypox/branch/cloudfront-invaldiation/metadata.tsv.gz
Then I ran the cloudfront-valdiation branch GH action workflow.
When the pipeline finished, I immediate pulled the metadata TSV from https://data.nextstrain.org/files/files/workflows/monkeypox/branch/cloudfront-invaldiation/metadata.tsv.gz and verified that there metadata file was updated with the latest records.


Add AsyncParsableCommand to README

Update to README and markdown documentation to include easily discovered references to AsyncParsableCommand.

In issue https://github.com/apple/swift-argument-parser/issues/561, I noted that AsyncParsableCommand was not easily discovered. This pull request attempts to remedy this by adding simple references to it in README.md, ArgumentParser.md, and Validation.md. In GettingStarted.md I went so far as to add a new section with an example.
Please note, this only includes documentation changes and does not include any code changes. Therefore, there are no tests for this PR.
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

@swift-ci Please test

This is really hard to discover without documentation. Please merge if possible.

FWIW, the status checks said it was out of date, so I went back to my fork and updated it (while preserving my changes). I hope this helps…

@swift-ci Please test


sidebars: Change to more muted hover/active colors.

The active streams and users should be more muted grey tones than the
greens and blues that they currently are.

Will look on Monday, with other sidebar changes.