Added physics mc json task

This task is trying to quantify the ability of a model to gain a basic understanding of what a physics word problem is asking, and choose the formula needed to solve that problem.

@googlebot I signed it!

Not a reviewer. @gxywang, thank you for submitting the task!
It seems that your README.md file is in html. I would kindly suggest to use github markdown for it instead, to improve its readability.

Not a reviewer. @gxywang, thank you for submitting the task!
It seems that your README.md file is in html. I would kindly suggest to use github markdown for it instead, to improve its readability in github web interface.

Sorry, I didn't notice it showed up in html format. Thanks for the heads up!

Not a reviewer, but did the intial commit already pass due?

@gxywang We are now requesting that task authors please include an explicit section in the README.md file called "data source", listing exactly where you got your data from (or explicitly state that you made it up yourself). Many thanks!

@MGheini are one of the assigned reviewers for this task.  Please provide feedback and be sure to notify me with a formal accept or does not meet criteria by Tuesday June 22 (if you have not already done so).

@liamb315 are one of the assigned reviewers for this task.  Please provide feedback and be sure to notify me with a formal accept or does not meet criteria by Tuesday June 22 (if you have not already done so).

Hi, I am one of the reviewers. Concerns shared below are based on the checklist here.
First of all, there are some correctness issues that need to be fixed. Please name the JSON file task.json per instructions instead of mc_questions.json. Also, as instructed, add the "physics" keyword here as part of your pull request, as it does not already appear there. Overall make sure, the pull request passes the checks that get run when submitted.
Next, there's no discussion of task difficulty in terms of current models' performance on the task. Is there any evidence showing that current models are indeed not capable of fully solving the task?
Finally, a very important limitation that you also bring up in the README, is that a model may be able to perform well by "memorizing the internet." This is highly undesirable, as also outlined in the review criteria. Please explicitly clarify is this a potential issue with your data based on your data sources (especially, online ones like Khan Academy Material.)
Please let me know if you need more clarifications. Thanks.

@chiafullo does not meet criteria

Hi, I am one of the reviewers. Concerns shared below are based on the checklist here.
First of all, there are some correctness issues that need to be fixed. Please name the JSON file task.json per instructions instead of mc_questions.json. Also, as instructed, add the "physics" keyword here as part of your pull request, as it does not already appear there. Overall make sure, the pull request passes the checks that get run when submitted.
Next, there's no discussion of task difficulty in terms of current models' performance on the task. Is there any evidence showing that current models are indeed not capable of fully solving the task?
Finally, a very important limitation that you also bring up in the README, is that a model may be able to perform well by "memorizing the internet." This is highly undesirable, as also outlined in the review criteria. Please explicitly clarify is this a potential issue with your data based on your data sources (especially, online ones like Khan Academy Material.)
Please let me know if you need more clarifications. Thanks.

Thanks for the review! I fixed the task based on the concerns above. For the last note, I added an explanation of the said limitation for each individual source, but please let me know if any extra clarification is needed, or if there are any extra concerns. Thanks again!

The amount of tasks we received this round is tremendous.  With so many tasks to review we have decided to extend the review period to Tuesday, June 29.
Reviewers: if the submitter has made revisions please be sure to notify me with a formal ”accept” or ”does not meet criteria” by Tuesday, June 29  (if you haven't already done so).
this is an automated message

Hi, I am one of the reviewers. Concerns shared below are based on the checklist here.
First of all, there are some correctness issues that need to be fixed. Please name the JSON file task.json per instructions instead of mc_questions.json. Also, as instructed, add the "physics" keyword here as part of your pull request, as it does not already appear there. Overall make sure, the pull request passes the checks that get run when submitted.
Next, there's no discussion of task difficulty in terms of current models' performance on the task. Is there any evidence showing that current models are indeed not capable of fully solving the task?
Finally, a very important limitation that you also bring up in the README, is that a model may be able to perform well by "memorizing the internet." This is highly undesirable, as also outlined in the review criteria. Please explicitly clarify is this a potential issue with your data based on your data sources (especially, online ones like Khan Academy Material.)
Please let me know if you need more clarifications. Thanks.

Thanks for the review! I fixed the task based on the concerns above. For the last note, I added an explanation of the said limitation for each individual source, but please let me know if any extra clarification is needed, or if there are any extra concerns. Thanks again!

Thanks for applying the changes. Following up on them, I had a few requests/questions:

Can you change the description of the added keyword to something more accurate. After all, it's not like the models are really "solving" the problems. It can be something like "measures the ability of a model to associate a physics problem written in text to the correct relevant formula".
According to what you report, GPT-2 scores 0.214 on the task. That's even worse than random (given that there are four choices, random guess would score ~0.25). Do you have any intuitions why that's the case?

Thanks.

Hi, I am one of the reviewers. Concerns shared below are based on the checklist here.
First of all, there are some correctness issues that need to be fixed. Please name the JSON file task.json per instructions instead of mc_questions.json. Also, as instructed, add the "physics" keyword here as part of your pull request, as it does not already appear there. Overall make sure, the pull request passes the checks that get run when submitted.
Next, there's no discussion of task difficulty in terms of current models' performance on the task. Is there any evidence showing that current models are indeed not capable of fully solving the task?
Finally, a very important limitation that you also bring up in the README, is that a model may be able to perform well by "memorizing the internet." This is highly undesirable, as also outlined in the review criteria. Please explicitly clarify is this a potential issue with your data based on your data sources (especially, online ones like Khan Academy Material.)
Please let me know if you need more clarifications. Thanks.

Thanks for the review! I fixed the task based on the concerns above. For the last note, I added an explanation of the said limitation for each individual source, but please let me know if any extra clarification is needed, or if there are any extra concerns. Thanks again!

Thanks for applying the changes. Following up on them, I had a few requests/questions:

Can you change the description of the added keyword to something more accurate. After all, it's not like the models are really "solving" the problems. It can be something like "measures the ability of a model to associate a physics problem written in text to the correct relevant formula".
According to what you report, GPT-2 scores 0.214 on the task. That's even worse than random (given that there are four choices, random guess would score ~0.25). Do you have any intuitions why that's the case?

Thanks.

Hello! In response to your requests/questions:

I fixed the keyword description to "measure's model's ability to chose the relevant formula for a given physics word problem".
My best guess would be because the context of a given problem could be misleading. For example, if the question asked about gravitational field flux, but the model usually associates gravity with acceleration in kinematics, then the chosen answer would probably be a kinematics formula instead of the correct E&M formula.

Thanks!

@gxywang Thanks for addressing my feedback. I'm gonna update my decision now.

@chiafullo accept

@chiafullo accept

Great! Thanks for your time!

Your task has been accepted in the initial review stage.  The next stage of this process is for us to assign your task a meta-reviewer for final review and merge.  An assigned meta-reviewer will follow-up by commenting on the PR should it need further revisions.

I'm the meta-reviewer for this task. This seems like a nice task, that measures interesting and important capabilities. I like the approach of asking the model to identify the applicable formula. I have a few requests:

right now the task.json file is one extremely long line. This makes it very hard for humans to review. Could you add line breaks between the fields in the task.json file?
right now, it would be very difficult even for a human to understand how they were supposed to answer the questions. Could you add a task prefix ( https://github.com/google/BIG-bench/blob/main/docs/doc.md#optional-fields ) to the beginning of your task.json file, explaining what the task is? For instance, something like:
"task_prefix" : "Identify the physics formula that would be most useful for finding the answer to each of the following word problems.\n\n",

After these changes (* assuming that task.json seems reasonable once I can easily read it), I will merge the task.
Thank you very much for your contribution!

I'm the meta-reviewer for this task. This seems like a nice task, that measures interesting and important capabilities. I like the approach of asking the model to identify the applicable formula. I have a few requests:

right now the task.json file is one extremely long line. This makes it very hard for humans to review. Could you add line breaks between the fields in the task.json file?
right now, it would be very difficult even for a human to understand how they were supposed to answer the questions. Could you add a task prefix ( https://github.com/google/BIG-bench/blob/main/docs/doc.md#optional-fields ) to the beginning of your task.json file, explaining what the task is? For instance, something like:
"task_prefix" : "Identify the physics formula that would be most useful for finding the answer to each of the following word problems.\n\n",

After these changes (* assuming that task.json seems reasonable once I can easily read it), I will merge the task.
Thank you very much for your contribution!

Thanks for the review! I fixed the json file format and added the task prefix above the example inputs. If there are any other concerns, please let us know.

It looks great. Merging.


detail time schedule, a prior knowledge and preparations on README

Time schedule was provided, README updated before the workshop


region_to_gene throws an error in some cases

When I run region_to_gene I often get an error instead of a result. For example:
region_to_gene(region="chr14:105862865-105863058",genome_build = "hg38")
Error in if (!str_detect(genes$chromosome[1], "chr")) { :
  missing value where TRUE/FALSE needed

Thanks for reporting Ryan.
I just had a quick look, and it seems that there are no genes residing inside the specified region (in the example you provided). Could this be the reason that the function "often" fails for you? Regardless, it would be useful to have the function notify the user if there are no genes found within the specified region.
For example, if I expand the region in your example by 2000bp we get this back:
> region_to_gene(region="chr14:105861865-105864058",genome_build = "hg38")
3 gene(s) returned for 1 region(s)
  chromosome     start       end hugo_symbol region_start region_end
1      chr14 105863197 105863258       IGHJ6    105861865  105864058
2      chr14 105863415 105863465      IGHJ3P    105861865  105864058
3      chr14 105863813 105863862       IGHJ5    105861865  105864058

As a note, I have ran in to similar issues when I (mistakenly) provide a region to this function that is in respect to another projection, than what is specified within the call of the region_to_gene function.

Yes, that's likely the cause. Do you think it should throw an error (as it's currently doing) or elegantly return an empty data frame instead? The issue I'm having is that calling this function within another function currently requires the call to be wrapped in a tryCatch().

If we have it return an empty data frame (but also a message so the user would be aware) I would assume that this wouldn't break in a nested environment, like you're describing. So I would vote for this.

The messages should only be used in verbose mode though, right? Currently it's already printing out a message for each region the function is given, which leads to a very verbose output if a function calls it repeatedly.
For example, here's the current output (with just the region being printed in the calling function for debugging purposes):
[1] "chr1:92914901-92915003"
1 gene(s) returned for 1 region(s)
[1] "chr5:10400752-10401894"
1 gene(s) returned for 1 region(s)
[1] "chr14:105773847-105859779"
7 gene(s) returned for 1 region(s)
[1] "chr20:17966979-17967114"
2 gene(s) returned for 1 region(s)
[1] "chr22:22322826-22355878"
7 gene(s) returned for 1 region(s)
[1] "chr6:29810026-29904500"
8 gene(s) returned for 1 region(s)
[1] "chr7:70496350-70496767"
1 gene(s) returned for 1 region(s)
[1] "chrX:1087815-1088665"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr14:64458111-64461841"
2 gene(s) returned for 1 region(s)
[1] "chr5:79031008-79032539"
1 gene(s) returned for 1 region(s)
[1] "chr6:32654870-32754078"
7 gene(s) returned for 1 region(s)
[1] "chr17:13733571-13734989"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr13:88396330-88398128"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr15:40050289-40051291"
1 gene(s) returned for 1 region(s)
[1] "chr18:15656295-15702692"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr22:31226197-31227014"
1 gene(s) returned for 1 region(s)
[1] "chr1:182114358-182114666"
1 gene(s) returned for 1 region(s)
[1] "chr14:105773233-105858897"
6 gene(s) returned for 1 region(s)
[1] "chr2:88860382-88860480"
1 gene(s) returned for 1 region(s)
[1] "chr5:50456310-50468640"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr5:105836364-105839254"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr14:105773387-105859809"
7 gene(s) returned for 1 region(s)
[1] "chr17:49796951-49803952"
1 gene(s) returned for 1 region(s)
[1] "chr1:124945634-124955006"
Here's the original error message:
missing value where TRUE/FALSE needed[1] "chr14:105859052-105859507"
1 gene(s) returned for 1 region(s)
[1] "chr12:11380951-11420570"

Agree! I will provide an update for this function. Thanks for reporting.


Add a bulk select/deselect using text files to the Cases box

The cohort constructor will be the preferred mechanism to build lists of selected patients - but in the interim - we need a mechanism by which AG staff can use their existing techniques. This involves them building a CSV (TSV?) in excel with existing manual matching (doesn't matter as it is just one column I presume) of ids that they want to release.
We should allow them to drag this onto somewhere in the cases Box - and have all the matches specimens/patients be selected.

I would think it probably needs an new TRPC endpoint that accepts a raw text file - and then the backend 'sets' the passed in ids (could be patient id or specimen id - I suggest we match to either).
I would probably suggest that this is not a 'toggle'.. or a 'replace set' of the existing cases. I think it probably should leave whatever is already selected exactly in place - but ensure that everything listed in the input file gets selected.
We could probably add a counterpoint "clear" - that takes from the file a list of specimens to 'unset'. (say they have been given an excel with the ids of 50 patients who have withdrawn).. they would first 'select all'.. and then drag on their CSV

Happy for this to have any limits if they make things easier to implement (e.g. doesn't work with 1Gib text files). Possibly it takes 10- 20 seconds but we don't run it as a background task.
This is an interim feature whilst we build out the cohort builder functionality.

I think they also have non CTRL related datasets that they still manually process - so it may not be until we literally do all the work on cohort building (beacon, ctrl, regular consent, etc) that they could use it in practice. I think this feature is small enough that it worth knocking over now and getting it into prod.
It also might be a feature we leave in - even if we do have cohort building.

It will need to work with patient identifiers (and also probably specimen identifiers). So as a method call we are proposing the backend operation will be like?
releaseKey: "..."
op: "add"
value: [ "BART", "NA128787", "345-345-234-234-453-453" ]
where the passed in values can be either a
specimen edgedb id
a specimen identifier value (from its identifiers array)
a patient identifier value (from its identifiers array) - (which will in turn select all sub specimens)
(possibly a case identifier value (from its identifiers array) - (which will in turn select all sub patients/specimens)
Just some top of the head thoughts - we will need some extra backend to check that we don't manage to "add" the same specimen more than once. I mean that probably automatically is baked into our Edge model that each specimen can only be "in the release" once, but would be good to have a test confirming the correct operation of that (as if we are talking about allowing the specimens to be added to be named in multiple ways)

If you are handling the recursive add/remove (i.e. the ability to specify identifiers at the patient or case level) - then possibly the values accepted should be
specimen edgedb id
a specimen identifier value (from its identifiers array)
patient edgedb id (which will in turn select all sub specimens)
a patient identifier value (from its identifiers array) - (which will in turn select all sub specimens)
case edgedb id (which will in turn select all sub patients/specimens)
a case identifier value (from its identifiers array) - (which will in turn select all sub patients/specimens)
If the backend is able to handle all of those - then we can improve the frontend UI to allow the patient and case checkboxes to be live (at the moment they are read-only)
But understand if you don't want to tackle that in this PR

Yeah whilst in reality I would hope the specimen and patient external identifiers are unique - that really is up to the dataset creator so we can't enforce that.
The CSVs that AG want to use will only consist of patient identifiers (AG study ids). We derive specimen ids to refer to the underlying specimens (from the filenames) but that is not how AG have a record of them

(sorry yes re-reading the initial ticket description I didn't make it clear it needed to work primarily with patient level ids)


Add a print breakpoint

In the responsive object you could add a print breakpoint to disable slick on the print view. That way we could print the content. This is useful when we use slick as a content explorer and would like to stack the content boxes on print view.
$('.js-slick').slick({
	slidesToShow: 4,
	responsive: [
		{
			breakpoint: 1050,
			settings: {
				slidesToShow: 4,
			}
		},
		{
			breakpoint: 'print',
			settings: unslick,
		},
	],
});

Closing due to not following CONTRIBUTING.md


more specific exclude pattern

Since exclude matches the given string on FULL file paths, the exclude pattern io is too general, which may lead to exclude unexpected ones. For example, k-distribution matches the exclude pattern io, so that it excludes all files under the path k-distribution/tutorial/.
Well, the suggested fix io.imp may be still problematic. So, ktest would be better to report explicitly which files are excluded.

@grosu Please review this.

ok with me for now, although we need to redesign ktest, as discussed.

I'm closing and deleting the branch. The change is tiny so it can be recreated easily if needed.
Pasting it here:
k-distribution/tutorial/1_k/4_imp++/lesson_7/exercises/abort/tests/config.xml
-           exclude="io" >  <!-- Because of bug #159-->
+           exclude="io.imp" >  <!-- Because of bug #159-->


Update reflecting latest CI image version required

The UI says that there is a new image version 23.06.30 but this page does not mention it.

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

ID: 85b0e26b-e44d-606b-a22a-50aa8ce42805
Version Independent ID: d5096d6e-628b-ce3e-6d9e-61987814f2d8
Content: Compute instance image release notes - Azure Machine Learning
Content Source: articles/machine-learning/azure-machine-learning-ci-image-release-notes.md
Service: machine-learning
Sub-service: core
GitHub Login: @deeikele
Microsoft Alias: deeikele

@timoklimmer
Thanks for your feedback! We will investigate and update as appropriate.

@deeikele
could you please review this and update as appropriate.

@timoklimmer
I've delegated this to @deeikele, a content author, to review and share their valuable insights.

Updated release notes were just shared with me, and will be published later today. Pasting them here for now:
June 30, 2023
Version: 23.06.30
Main changes:
Azure Machine Learning SDK to version 1.51.0
Purged vulnerable packages
Fixed libtinfo error
Fixed 'conda command not found' error
Main environment specific updates:
tensorflow updated to 2.11.1 in azureml_py38_PT_TF
azure-keyvault-keys updated to 4.8.0 in azureml_py38

Thank you for your feedback. To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.  As part of that transition, we are closing  older issues that we believe have been resolved by subsequent document updates.
If you feel that this issue still persists, please respond and let us know.
#please-close


video thumb

hey, just added video thumb cause I need it in my app, feel free to use it

Thanks for contribution. I'll test it out and merge it into dev.


No usable encoding profile found.

Not sure what is going on here. wl-record says vaapi does not support yuv420 but vainfo says it does?
wl-record v0.1.1 compiled via cargo + git.
[I] root@fedora ~
# wl-screenrec --verbose
Using output DP-1
Opening libva device from DRM device /dev/dri/renderD128
+----------+
|    in    |default--[3840x2160 0:1 vaapi]--Parsed_crop_0:default
| (buffer) |
+----------+

                                                            +--------------+
Parsed_scale_vaapi_1:default--[3840x2160 0:1 vaapi]--default|     out      |
                                                            | (buffersink) |
                                                            +--------------+

                                          +---------------+
in:default--[3840x2160 0:1 vaapi]--default| Parsed_crop_0 |default--[3840x2160 0:1 vaapi]--Parsed_scale_vaapi_1:default
                                          |    (crop)     |
                                          +---------------+

                                                     +----------------------+
Parsed_crop_0:default--[3840x2160 0:1 vaapi]--default| Parsed_scale_vaapi_1 |default--[3840x2160 0:1 vaapi]--out:default
                                                     |    (scale_vaapi)     |
                                                     +----------------------+

[h264_vaapi @ 0x561374eff900] No usable encoding profile found.
failed to open encoder in low_power mode (Function not implemented), trying non low_power mode. if you have an intel iGPU, set enable_guc=2 in the i915 module to use the fixed function encoder. pass --low-power=off to suppress this warning
[h264_vaapi @ 0x561374effcc0] No usable encoding profile found.
failed to create encoder: Function not implemented

[I] root@fedora ~
# wl-screenrec --verbose --no-hw
Using output DP-1
Opening libva device from DRM device /dev/dri/renderD128
[Parsed_scale_vaapi_1 @ 0x55eabd2197c0] Hardware does not support output format yuv420p.
[Parsed_scale_vaapi_1 @ 0x55eabd2197c0] Failed to configure output pad on Parsed_scale_vaapi_1
thread 'main' panicked at src/main.rs:1648:18:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(22: Invalid argument)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[I] root@fedora ~ [101]
# vainfo -a
Trying display: wayland
libva info: VA-API version 1.18.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.18 (libva 2.18.2)
vainfo: Driver version: Mesa Gallium driver 23.1.9 for AMD Radeon VII (vega20, LLVM 16.0.6, DRM 3.54, 6.5.12-200.fc38.x86_64)
vainfo: Supported config attributes per profile/entrypoint pair
VAProfileMPEG2Simple/VAEntrypointVLD
    VAConfigAttribRTFormat                 : VA_RT_FORMAT_YUV420

VAProfileMPEG2Main/VAEntrypointVLD
    VAConfigAttribRTFormat                 : VA_RT_FORMAT_YUV420

VAProfileNone/VAEntrypointVideoProc
    VAConfigAttribRTFormat                 : VA_RT_FORMAT_YUV420
                                             VA_RT_FORMAT_YUV422
                                             VA_RT_FORMAT_YUV444
                                             VA_RT_FORMAT_YUV400
                                             VA_RT_FORMAT_YUV420_10
                                             VA_RT_FORMAT_RGB32
                                             VA_RT_FORMAT_YUV420_10BPP

[I] root@fedora ~
# ls -alh /dev/dri/*
crw-rw---- 1 root video  226,   0 Nov 26  2023 /dev/dri/card0
crw-rw---- 1 root video  226,   1 Nov 26  2023 /dev/dri/card1
crw-rw-rw- 1 root render 226, 128 Nov 26  2023 /dev/dri/renderD128

/dev/dri/by-path:
total 0
drwxr-xr-x 2 root root 100 Nov 26  2023 ./
drwxr-xr-x 3 root root 120 Nov 26  2023 ../
lrwxrwxrwx 1 root root   8 Nov 26  2023 pci-0000:03:00.0-card -> ../card1
lrwxrwxrwx 1 root root  13 Nov 26  2023 pci-0000:03:00.0-render -> ../renderD128
lrwxrwxrwx 1 root root   8 Nov 26  2023 platform-simple-framebuffer.0-card -> ../card0

[I] root@fedora ~
# lspci |grep 03:00
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] (rev c1)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII]

I find it likely that the reason why it works on my other Fedora box is that it uses an Intel GPU and here on the workstation I have a fancy AMD GPU.
The error message "failed to create encoder: Function not implemented" is perhaps not the best, but besides that I do not think there is much you can help me with here.
https://www.reddit.com/r/linux/comments/xpyggi/comment/iq6nkhn/

Hmm, this is encode and that is decode. Other people have reported this working fine on AMD GPUs, but I don't have one to test.
Unfortunately that error is from ffmpeg.

I have happy users with AMD GPU's (#1, #39, #33). What GPU do you have? Does ffmpeg -vaapi_device /dev/dri/renderD128 -f lavfi -i rgbtestsrc=duration=5:size=1280x720:rate=30 -vf hwupload,crop=100:100:200:200,scale_vaapi=format=nv12:w=100:h=100 -c:v h264_vaapi testout.mp4 work?

[I] root@neo ~
# ffmpeg -vaapi_device /dev/dri/renderD128 -f lavfi -i rgbtestsrc=duration=5:size=1280x720:rate=30 -vf hwupload,crop=100:100:200:200,scale_vaapi=format=nv12:w=100:h=100 -c:v h264_vaapi testout.mp4
ffmpeg version 6.1-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil      58. 29.100 / 58. 29.100
  libavcodec     60. 31.102 / 60. 31.102
  libavformat    60. 16.100 / 60. 16.100
  libavdevice    60.  3.100 / 60.  3.100
  libavfilter     9. 12.100 /  9. 12.100
  libswscale      7.  5.100 /  7.  5.100
  libswresample   4. 12.100 /  4. 12.100
  libpostproc    57.  3.100 / 57.  3.100
Unrecognized option 'vaapi_device'.
Error splitting the argument list: Option not found
[I] root@neo ~ [8]
#

[I] root@neo ~
# wf-recorder -f test-vaapi.mp4 -c h264_vaapi -d /dev/dri/renderD128
Output file "test-vaapi.mp4" exists. Overwrite? Y/n: y
using VA-API, trying to enable DMA-BUF capture...
enabled DMA-BUF capture, device /dev/dri/renderD128
selected region 0,0 0x0
Using video filter: scale_vaapi=format=nv12:out_range=full
[h264_vaapi @ 0x7f1168002300] No quality level set; using default (20).
[h264_vaapi @ 0x7f1168002300] Driver does not support some wanted packed headers (wanted 0xd, found 0).
[h264_vaapi @ 0x7f1168002300] Driver does not support packed sequence headers, but a global header is requested.
[h264_vaapi @ 0x7f1168002300] No global header will be written: this may result in a stream which is not usable for some purposes (e.g. not muxable to some containers).
Output #0, mp4, to 'test-vaapi.mp4':
  Stream #0:0: Video: h264 (High), vaapi(pc), 3840x2160 [SAR 1:1 DAR 16:9], q=2-31
^C⏎                                                                                [I] root@neo ~
# wl-screenrec --dri-device /dev/dri/renderD128
Using output DP-1
Opening libva device from DRM device /dev/dri/renderD128
[h264_vaapi @ 0x564efc28fac0] No usable encoding entrypoint found for profile VAProfileH264High (7).
failed to open encoder in low_power mode (Function not implemented), trying non low_power mode. if you have an intel iGPU, set enable_guc=2 in the i915 module to use the fixed function encoder. pass --low-power=off to suppress this warning
[h264_vaapi @ 0x564efc28fac0] Driver does not support some wanted packed headers (wanted 0xd, found 0).
[h264_vaapi @ 0x564efc28fac0] Driver does not support packed sequence headers, but a global header is requested.
[h264_vaapi @ 0x564efc28fac0] No global header will be written: this may result in a stream which is not usable for some purposes (e.g. not muxable to some containers).
[h264_vaapi @ 0x564efc28fac0] Failed to upload encode parameters: 2 (resource allocation failed).
[h264_vaapi @ 0x564efc28fac0] Encode failed: -5.
thread 'main' panicked at src/main.rs:1426:51:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(5: Input/output error)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[I] root@neo ~ [101]
# vainfo
Trying display: wayland
vainfo: VA-API version: 1.20 (libva 2.20.0)
vainfo: Driver version: Mesa Gallium driver 23.2.1-arch1.2 for AMD Radeon VII (vega20, LLVM 16.0.6, DRM 3.49, 6.1.64-1-lts)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
[I] root@neo ~
#

Just to be safe, can you show the output of ffmpeg -hwaccels?
Should look something like this:
Hardware acceleration methods:
vdpau
vaapi
drm
vulkan

(not sure if this has been merged into upstream ffmpeg, but the "Cannot allocate memory" message might be bogus as per<EMAIL_ADDRESS>

It only shows vdpau ... ?

It only shows vdpau ... ?

@hholst80 That is weird, its as if your ffmpeg build does not have vaapi enabled for some reason. vdpau is only for hw accelerated decoding.
Can you check the output of ffmpeg -buildconf | grep -Ei "vdpau|vaapi"?
For me it shows both --enable-vaapi and --enable-vdpau (which correlates to my ffmpeg -hwaccels output)

Is wl-screenrec using the right ffmpeg? lld $(which wl-screenrec)
On Thu, Dec 7, 2023 at 5:30 AM Henrik Holst @.***>
wrote:

Classic "well, this is embarrassing" situation.
ffmpeg version 6.1-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 8 (Debian 8.3.0-6)
[I] @.*** ~
which ffmpeg
/home/root/.local/bin/ffmpeg
mv /home/root/.local/bin/ffmpeg{,-static}

Hardware acceleration methods:
vdpau
cuda
vaapi
qsv
drm
opencl
vulkan
image.png (view on web)
https://github.com/russelltg/wl-screenrec/assets/6200749/b71c095c-e92b-45a7-8365-a6ee2d476acd
—
Reply to this email directly, view it on GitHub
https://github.com/russelltg/wl-screenrec/issues/41#issuecomment-1845260926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWGUORQBOKK3232TS7IUA3YIGZHVAVCNFSM6AAAAAA726IOLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVGI3DAOJSGY
.
You are receiving this because you commented.Message ID:
@.***>

Could wl-screenrec be using the wrong ffmpeg? ldd $(which wl-screenrec)

I don't think so. You're welcome to test this patch against latest main:
diff --git a/src/main.rs b/src/main.rs
index fd62896..a2790ad 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -1423,7 +1423,9 @@ impl EncState {
             .is_ok()
         {
             // encoder has same time base as the filter, so don't do any time scaling
-            self.enc_video.send_frame(&yuv_frame).unwrap();
+            if let Err(e) = self.enc_video.send_frame(&yuv_frame) {
+                eprintln!("Failed to encode: {e}")
+            }
         }

         let mut encoded = Packet::empty();

I'll probably push this patch anyways as it's less nasty than a panic, and I suppose maybe sometimes that error isn't fatal. It's hard to say.
I would be interested in full strace outputs from those two commands to see exactly what is failing.

on git sha 6110ba66495c65b913cf50afb595eab7b992cb34 I get this.
Seems to be the same error message as I got on the "new machine" (called "goblin") in #64
This is on the same hardware as before on my "neo" machine.
[I] root@neo ~
# wl-screenrec --low-power=off --encode-resolution 1920x1080 --audio
Using output DP-1
Opening libva device from DRM device /dev/dri/renderD128
[Parsed_crop_0 @ 0x57ec399cf580] Invalid too big or non positive size for width '3840' or height '2160'
[Parsed_crop_0 @ 0x57ec399cf580] Failed to configure input pad on Parsed_crop_0
thread 'main' panicked at src/main.rs:1706:18:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(22: Invalid argument)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[I] root@neo ~ [101]
#

[I] root@neo ~
# vainfo
Trying display: wayland
vainfo: VA-API version: 1.20 (libva 2.20.1)
vainfo: Driver version: Mesa Gallium driver 24.0.1-arch1.1 for AMD Radeon VII (radeonsi, vega20, LLVM 16.0.6, DRM 3.57, 6.7.5-zen1-1-zen)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
[I] root@neo ~
#

vvv.txt

Aha!
This might be related to non-integer scaling (I am exploring the best way to do HiDPI in a portable way between my many machines.).
If I use an integer scaling, like 2 instead of 2.4 like I am using now on both neo and goblin, I get this more familiar error message:
[I] root@neo ~/Apps/wl-screenrec (main)
# wl-screenrec --low-power=off --encode-resolution 1920x1080 --audio
Opening libva device from DRM device /dev/dri/renderD128
[h264_vaapi @ 0x588bbf9c5cc0] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
[h264_vaapi @ 0x588bbf9c5cc0] Failed to upload encode parameters: 2 (resource allocation failed).
[h264_vaapi @ 0x588bbf9c5cc0] Encode failed: -5.
thread 'main' panicked at src/main.rs:1505:51:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(5: Input/output error)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[I] root@neo ~/Apps/wl-screenrec (main) [101]
#

Reported upstream at https://github.com/hyprwm/Hyprland/issues/4991

It's possible I should handle this better by clamping the size to the dmabuf size...but it's truly unexpected that the dmabuf size is too small...

Does
ffmpeg -vaapi_device /dev/dri/renderD128 -hwaccel vaapi -f lavfi -i testsrc=duration=10:size=1280x720 -filter_complex 'hwupload,scale_vaapi=format=nv12' -c:v h264_vaapi -loglevel 80 test.mp4

work and create a valid video?

i've recorded videos with this program before, but i started having this exact issue some time ago and i'm not sure what caused it.
sarpnt@mime-cube
----------------
OS: Arch Linux x86_64
Kernel: 6.9.2-zen1-1-zen
Uptime: 1 hour, 10 mins
Packages: 1298 (pacman)
Shell: fish 3.7.1
Resolution: 1920x1080
WM: sway
Theme: oomox-darker-than-fusion [GTK2/3]
Icons: breeze-dark [GTK2/3]
Terminal: foot
CPU: Intel i5-4690K (4) @ 3.900GHz
GPU: Intel HD Graphics
GPU: AMD ATI Radeon RX 470/480/570/570X/580/580X/590
Memory: 3708MiB / 11828MiB

sarpnt@mime-cube ~> wl-screenrec
Opening libva device from DRM device /dev/dri/renderD129
[h264_vaapi @ 0x5604f2686d40] No usable encoding entrypoint found for profile VAProfileH264High (7).
failed to open encoder in low_power mode (Function not implemented), trying non low_power mode. if you have an intel iGPU, set enable_guc=2 in the i915 module to use the fixed function encoder. pass --low-power=off to suppress this warning
[h264_vaapi @ 0x5604f2686d40] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
[h264_vaapi @ 0x5604f2686d40] Failed to upload encode parameters: 2 (resource allocation failed).
[h264_vaapi @ 0x5604f2686d40] Encode failed: -5.
thread 'main' panicked at src/main.rs:1564:51:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(5: Input/output error)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

sarpnt@mime-cube ~ [101]> wl-screenrec --no-hw
Opening libva device from DRM device /dev/dri/renderD129
[Parsed_scale_vaapi_1 @ 0x634217b0d580] Hardware does not support output format yuv420p.
[Parsed_scale_vaapi_1 @ 0x634217b0d580] Failed to configure output pad on Parsed_scale_vaapi_1
thread 'main' panicked at src/main.rs:1782:18:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(22: Invalid argument)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

vainfo shows the amd card should work and ffmpeg with vaapi encoding works fine


Remove configuration via 'mocha.opts'

Description
The configuration via mocha.opts has been deprecated in Mocha v7.0.0.
In Mocha v8.0.0 we remove it.
Description of the Change

we remove corresponding code, unit and integration tests
we adapt docs
Mocha does not complain, when an unknown/mistyped option is used. Many user do not read our documentation/release notes, therefore we throw an error when user sets --opts option.

Coverage decreased (-0.06%) to 92.793% when pulling 685182e9381b156b78e6df1dac308cfe11ec643e on juergba/remove-opts into 883ae4b5e1aacd8cf30694da33b391ce58f4cca8 on master.

coverage: the report shows a decrease of -0.06% in lib/options.js. When studying the details there is not one uncovered line of code, and the three newly added lines are covered by tests.
So IMO no need for action.


chore: try shrinking global event buffer pool to a minimum of 32 buffers

Context
Testing different changes to the global event buffer pool, specifically around the size of the buffers themselves as well as the minimum/maximum size of the object pool.
This PR tests changing the minimum size of the object pool to 32 items instead of 64.

This seems to have a positive effect on idle RSS (not as much as the other variants) and has no noticeable impact on the 100MB/s x 250K contexts experiment (while the other two variants do) so I'm going to merge this one.


Fixed #28620. Clear boundfield cached value after setting up inline foreign key field

As I commented on the ticket, I don't think this is needed since iterating over bound fields in Form.__init__() isn't expected.


DE OMAS - Including methods for external source GUID & Name

Issue #1791

@mandy-chessell
Hi Mandy, I have also added few methods of create entity/relationship in RepositoryHandler and SchemaTypeHandler. It would be nice if you can have a quick look as I might not aware some rules of adding new methods on them. Thanks.

Thanks @cong for doing that, I will have a look - but it is ok to merge before I get to see it.


Roadmap button hover effect fixed

@DarshanchGIT, your PR has conflicts that need to be addressed. Please review and resolve any issues. After resolving them, you can proceed to create a pull request. It is essential to resolve these conflicts in the branch.

your PR has conflicts that need to be addressed. Please review and resolve any issues. After resolving them, you can proceed to create a pull request. It is essential to resolve these conflicts in the branch.

@Himanshuch8055 there is an issue on roadmap section i.e there is no change after on clicking the topic button of the roadmap, kindly check it on the main website and fix there issue is on the main website

@Himanshuch8055 there is an issue on roadmap section i.e there is no change after on clicking the topic button of the roadmap, kindly check it on the main website and fix there issue is on the main website

Alright, I will investigate and inform you of the issue.


dbadmin container

Add a simple container called dbadmin containing a DBeaver Cloud instance for working directly with the database.

I'm going to redo this PR and update the nginx config so that it's using https://db.opencdms.org instead of http://db.opencdms.org:8978


Respect Client API options

This pull request rejigs the code slightly so that the options provided to a Validic::Client instance (e.g. organization_id, access_token) are respected over the global defaults. If specific API requests use a custom organization_id or access_token as an option, then that takes priority over the client options.

Hi @pat - Thanks for the PR! Can you talk to us a little more about your use case here?  When we wrote the gem, we tried to take into account organizations and their sub organizations, is that the case you're trying to help with?
If so, I'm curious if you considered something like:
my_parent_og = Validic::Client.new(parent_org_options)
my_other_org = Validic::Client.new(other_org_options)

Hi Anthony - code like that is precisely what we're doing, but it wasn't using the options appropriately.
client = Validic::Client.new(
  organization_id: our_org_id,
  access_token: our_access_token
)

# ignores the client's own value, uses Validic.organization_id, which is nil:
client.provision_user uid: '1'

# uses the specified organization id:
client.provision_user uid: '1', organization_id: our_org_id

The first provision_user call above actually works as expected (using the client's organization_id value) with the 0.4.1 release, but we're currently using the latest commits from your master branch so we can pass through a specific user's authentication token to get_org_apps (which 0.4.1 does not support), and somewhere after 0.4.1, the behaviour changed/broke.

Hi Pat - thank you for the quick reply, I can confirm we introduced this bug as part of PR #25 .  Originally when we instantiated the client, we ran reload_config which was a setter for those class methods.
It worked as such:
class Client
    def initialize(options={})
      @api_url        = options[:api_url].nil? ? 'https://api.validic.com' : options[:api_url]
      @api_version    = options[:api_version].nil? ? 'v1' : options[:api_version]
      @access_token   = options[:access_token].nil? ? Validic.access_token : options[:access_token]
      @organization_id = options[:organization_id].nil? ? Validic.organization_id : options[:organization_id]
      reload_config
    end

    ...

    def reload_config
      Validic.api_url = api_url
      Validic.api_version = api_version
      Validic.access_token = access_token
      Validic.organization_id = organization_id
    end

Moving that one line back appears to fix the problem though it does conflict with your PR since some of the code was removed.
@jjlangholtz @markphelps I'm fine to do away with the reload_config option, I actually think this PR is more explicit but would like your guys input before proceeding.
@pat do you mind squashing your commits down for us?

Squashed and force-pushed.

lgtm. thanks @pat for the PR!

Hi @pat  - Your branch has the right ideas but unfortunately while the REST methods converge on construct_path, we're not consistent with the options passed in so methods like provision_user will need to be redefined.  That will require we relook at how all the methods are interfacing and I don't want to delay a fix for the gem.
I've pushed up a hotfix that reenables the reload_config option so for the time being, please continue to use this convention:
my_parent_og = Validic::Client.new(parent_org_options)
my_other_org = Validic::Client.new(other_org_options)

I would not pass the optional organization_id into any of the methods, or use configure with a  block but instead instantiate a new client for each organization (as illustrated above).  We'll look at making this more consistent though so the interface is clear and so is the documentation.
I'm going to leave this issue open until a more widespread fix is in place.


Stop wrapping exceptions thrown by the retried Callables in ExecutionExceptions

There does not seem to be much point in using ExecutionExceptions, and it makes usage of the Retryer more complicated than it needs to be.
Note that with this change you would be able to more easily use lambdas with the Retryer.

Fixed in commit 01ab471d538cfcdc0365e87bb86a587d5309ebae on a branch, but leaving open until merged to master.


Saving out higher bitrate/resolution video files

Hi kunikunimitanni,
Thanks for creating this very handy tool! I was wondering if there is a way to save out a high(er) resolution / bitrate video? Or perhaps to keep the original procreate canvas dimensions?
It has been so useful to be able to access the time lapse of a procreate file without needing to airdrop the files over to the iPad and back etc. Thanks again, and happy to make a donation to the project if that helps.
Best,
Dave

HI Dave,
I was surprised and delighted to this tool had a user.
I have done some research on the title issue. To save a high resolution video, set a custom canvas when creating a new one in procreate. I believe that increasing the time lapse settings as much as possible will result in a higher quality file.
This tool will extract the video as it is stored in the Procreate file. If the quality of the resulting video is low, the settings in Procreate may help.

HI Dave,
I was surprised and delighted to this tool had a user.
This tool will extract the video as it is stored in the Procreate file. If the quality of the resulting video is low, the settings in Procreate may help.
To save a high resolution video, set a custom canvas when creating a new one in procreate. I believe that increasing the time lapse settings as much as possible will result in a higher quality file.
I hope this helps.

Hello, sorry I missed this reply.

I was surprised and delighted to this tool had a user.
Yup, your biggest fan over here! Ha

That definitely helps. Yeah I think my issue was just that a particular document I was using had low-res settings, as you mentioned. All the rest have been great.
Thanks again, and all the best!


test: stories for dialogs

Adds stories for each of our dialogs. Each dialog has a component, but we interact with them through the DialogContents component. I figured it made sense to test through that interface
Mocking providers
Some of the dialogs need some mocked data from posthog, the demo status, or the demo API call. For the time being I've mocked each of these at the highest point possible, to help with coverage. eg: Mock the tRPC call from the DemoProvider, rather than mocking the DemoProvider itself. These patterns might change in the future as we learn more about storybook and have more tests in place
MSW (Mock Service Worker)
This is the recommended way to mock network requests in storybook. It seems to work really nicely out of the box
Snapshots
You can see the story changes in chromatic

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


Properly fix issue with Lure levels (#54)

The previous fix for #54 (commit: a9952361d2f255895c6add21c171d42f0b09ebcd) only applied the special casing for the Lure enchantment in EnchModule#getEnchInfo and only if the EnchModule.ENCHANTMENT_INFO map didn't already have an entry for it, however, the map is already populated in EnchModule#init so the code block that the special casing is in never executes.
This applies the special casing in EnchModule#init and also applies it to the config so that the config also show the correct values. (The config setting is pretty much pointless, but kept for posterity.)

superseded by 3f483d8111dd8d30248e0cb61e3bd2b72c55e885


Help with Usage

How can you use this with the default configuration of the s.taglist? You could also Include like a Example doc for like naughty or wibar or s.taglist? So it's easier to use.

I don't believe it's possible to use with the default taglist. Most of awesome's default widgets use templates, which doesn't really work with rubato.
That's not to say that it's impossible to make a taglist with rubato--far from it--it's just that the code to do so is likely highly tailored to your individual rice, so an example probably wouldn't be of too much use.
Could you elaborate a little on the example doc though? I don't totally get what you mean by that and it sounds like it may be a good idea

What I mean with example doc would be that there is either a more "in depth" doc which would make the usage more clear / explains the for example "subscribe" function (an how to connect it with awesome signals), or the second way would be to maybe code some examples for like a taglist which has Animation built in or like naughty (awesome notification system), I got rubato to work with a sidebar (the animation plays when you show (toggle) the side bar), many people got it working with a ::toggle function but wirh anything else like a taglist. To some that up maybe give one or two examples which are ready to copy (like a taglist or naughty or maybe even a small widget) and include some notes in that example file or you write a "more" understandable/beginner friendly doc. Hope this Helpes!

Sorry, could you be a little more specific with what exactly is confusing? There isn't really much more to the subscribed functions than what I've already documented.
As far as code examples go, they would most likely just be too large or lacking too much context. If I ever add a wiki page it'd probably be a good fit for that though

I was about to create an issue asking for help. I a pull reference from Github randomly and have been trying to get it working since two days. I though I will ask here before giving up.
Any help is much appreciated. For your reference I have this minimal config and error here in pastebin - https://rentry.co/zsptx
I tried to run it with awmtt and got the error,
error: /home/ragu/.config/awesome/library/rubato/timed.lua:249: attempt to
perform arithmetic on a nil value (local 'value')

What I want is this (+ sliding and bouncing effect)

And what I am getting is this (basically empty)

Here is my awesome config dotfiles (just in case)
I know I am asking little too much, I totally understand if you don't have time for this!
Thanks in advance.

I was about to create an issue asking for help. I pulled a reference from Github randomly and have been trying to get it working since two days. Though I will ask here before giving up.
Any help is much appreciated. For your reference I have this minimal config and error here in pastebin - https://rentry.co/zsptx
I ran it with awmtt and got this error,
error: /home/ragu/.config/awesome/library/rubato/timed.lua:249: attempt to
perform arithmetic on a nil value (local 'value')

What I want is this (+ sliding and bouncing effect)
And what I am getting is this (basically empty)
Here is my awesome config dotfiles (just in case) Only this file and this file are relevant for this specific issue. This is the reference file that I am using which I found on github.
JK
I know I am asking little too much, I totally understand if you don't have time for this!
Thanks in advance.

I'm more than willing to help you debug, but there are a couple notes--one, this probably isn't the best place to ask questions, seeing as it's about a kinda seperate issue, and two, you don't actually include where and how you used my library which makes it difficult for me to actually debug. The aWM discord server (https://discord.gg/BPat4F87dg) might be a better place to ask these kinds of questions--feel free to ping me whenever. If that doesn't work out you can certainly also just open a seperate issue.
With respect to your question, I don't quite understand what you're trying to create here from the two images alone. Interestingly enough, the reference file seems to me my old dotfiles! So if nothing else I should be able to tell you about those lol.

Perfect, let me ping me on discord. Thank you!

in that case I'll probably abstain until I've actually got the wiki going. hopefully that should address everything else too. for now, I'll just close the issue


[typo] Fix typos in comments

Proposed changes
Fix typos in comments
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No)
Has document been added or modified: (No)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM


night vision effect not working?

this should work right? it says it's good but the effect doesnt activate...
im using worldguard 6.2 with latest version and on mc 1.8.9
/rg flag warzone give-effects night_vision 1

Flag is not working:
Make sure you do not have permissions for:
worldguard.region.bypass...
Also make sure you have use-player-move-event set to true in WorldGuard config.
Please also note that if you are OP you have the permissions to bypass any flag.


Fix the build

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

As reported in #81. No new build number since the merged build failed on all platforms.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [37]

For recipe/meta.yaml:

ℹ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12405326084. Examine the logs at this URL for more detail.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12405349294. Examine the logs at this URL for more detail.


feat(aws iam): support aws iam auth for postgresql components

Description
Allow for AWS IAM auth with postgres v2. These changes rotate the authentication token automatically before the 15 minute expiration on the authentication token.
Adding support for v1 and v2 postgres statestore and config and bindings postgres types.
Please note that I removed the master connection string setup I had initially. There is no reason to use aws iam enabled on postgres and a master connection string, as the dapr user could just use the regular postgres connection string auth for that. I now have it setup to where you just use an iam enabled username and the pwd is auto generated based on the aws config file or the secretkey/accesskey for the iam enabled user.
Issue reference
https://github.com/dapr/components-contrib/issues/3254
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

potentially flakey test and unrelated?
--- FAIL: Test_EndToEnd (0.40s)
    --- FAIL: Test_EndToEnd/http+gzip (0.22s)
        --- FAIL: Test_EndToEnd/http+gzip/consoleLog_stdout_and_stderr (0.09s)
            e2e_test.go:91:
                	Error Trace:	/home/runner/work/components-contrib/components-contrib/middleware/http/wasm/internal/e2e_test.go:91
                	            				/home/runner/work/components-contrib/components-contrib/middleware/http/wasm/internal/e2e_test.go:221
                	Error:      	"time=\"2024-02-07T21:16:45.410473385Z\" level=info msg=\"main ConsoleLog\" instance=fv-az736-80 scope=Test_EndToEnd type=log ver=unknown\ntime=\"2024-02-07T21:16:45.411097546Z\" level=info msg=\"main ConsoleLog\" instance=fv-az736-80 scope=Test_EndToEnd type=log ver=unknown\ntime=\"2024-02-07T21:16:45.411[128](https://github.com/dapr/components-contrib/actions/runs/7821189411/job/21337610051?pr=3324#step:9:129)433Z\" level=info msg=\"request[0] ConsoleLog\" instance=fv-az736-80 scope=Test_EndToEnd type=log ver=unknown\ntime=\"2024-02-07T21:16:45.411139224Z\" level=debug msg=\"wasm stdout: main Stdout\\nmain Stdout\\nrequest[0] Stdout\\n\" instance=fv-az736-80 scope=Test_EndToEnd type=log ver=unknown\ntime=\"2024-02-07T21:16:45.41115311Z\" level=debug msg=\"wasm stderr: main Stderr\\nmain Stderr\\nrequest[0] Stderr\\n\" instance=fv-az736-80 scope=Test_EndToEnd type=log ver=unknown\n" does not contain "level=debug msg=\"wasm stdout: main Stdout\\nrequest[0] Stdout\\n\""
                	Test:       	Test_EndToEnd/http+gzip/consoleLog_stdout_and_stderr

also my PR is seeing the below err for a pubsub kafka conformance test err:
go<EMAIL_ADDRESS>read<EMAIL_ADDRESS>stream error: stream ID 4899; INTERNAL_ERROR; received from peer

readyyyyy 😁

@ItalyPaleAle any chance y'all can review again please?

From my PR build. Again, totally unrelated:
=== FAIL: bindings/rabbitmq TestRabbitMQExclusive/rabbitmq_certification (11.91s)
    flow.go:220: Running step: rabbitmqcertification
    dockercompose.go:57: Creating network "rabbitmqcertification_rabbitmq_go_net" with driver "bridge"
        Creating rabbitmq ...
        Creating rabbitmq ... done

    flow.go:228: Completed step: rabbitmqcertification
    flow.go:220: Running step: wait for rabbitmq readiness
    retry.go:33: Failure: Exception (501) Reason: "read tcp [::1]:60818->[::1]:5672: read: connection reset by peer"; Retrying in 1s
    retry.go:35: Success!
    flow.go:228: Completed step: wait for rabbitmq readiness
    flow.go:220: Running step: standardApp
    flow.go:228: Completed step: standardApp
    flow.go:220: Running step: standardSidecar
time="2024-02-08T14:16:17.800355388Z" level=warning msg="The default value for 'spec.metric.http.increasedCardinality' will change to 'false' in Dapr 1.14" instance=fv-az570-300 scope=dapr.runtime type=log ver=unknown
time="2024-02-08T14:16:17.800466546Z" level=error msg="[INIT_FAILURE]: initialization error occurred for metrics: runtime/actor/timers: cannot register view \"runtime/actor/timers\"; a different view with the same name is already registered\nruntime/actor/reminders: cannot register view \"runtime/actor/reminders\"; a different view with the same name is already registered" instance=fv-az570-300 scope=dapr.runtime type=log ver=unknown
time="2024-02-08T14:16:17.800535134Z" level=info msg="Watching directories: [./components/exclusive]" instance=fv-az570-300 scope=dapr.runtime.hotreload.loader.disk type=log ver=unknown
    flow.go:228: Completed step: standardSidecar
    flow.go:230: Fatal error in step standardSidecar: failed to create watcher: failed to add target ./components/exclusive: no such file or directory

also see unrelated pubsub mqtt err:
panic: test timed out after 30m0s
running tests:
	TestMQTT (30m0s)
	TestMQTT/mqtt_certification (30m0s)

goroutine 40599 [running]:
testing.(*M).startAlarm.func1()
	/opt/hostedtoolcache/go/1.21.6/x64/src/testing/testing.go:2259 +0x3b9
created by time.goFunc
	/opt/hostedtoolcache/go/1.21.6/x64/src/time/sleep.go:176 +0x2d

goroutine 1 [chan receive, 30 minutes]:
testing.(*T).Run(0xc0004adba0, {0x2211fab?, 0x588b3c?}, 0x23353b8)
	/opt/hostedtoolcache/go/1.21.6/x64/src/testing/testing.go:1649 +0x3c8
testing.runTests.func1(0x380bfe0?)
	/opt/hostedtoolcache/go/1.21.6/x64/src/testing/testing.go:2054 +0x3e
testing.tRunner(0xc0004adba0, 0xc000529c38)
	/opt/hostedtoolcache/go/1.21.6/x64/src/testing/testing.go:1595 +0xff
testing.runTests(0xc0005a0640?, {0x37d3690, 0x1, 0x1}, {0x418dbf?, 0xc000529cf8?, 0x3809f80?})
	/opt/hostedtoolcache/go/1.21.6/x64/src/testing/testing.go:2052 +0x445
testing.(*M).Run(0xc0005a0640)
	/opt/hostedtoolcache/go/1.21.6/x64/src/testing/testing.go:1925 +0x[63](https://github.com/dapr/components-contrib/actions/runs/7830915945/job/21366093106?pr=3324#step:19:64)6
main.main()
	_testmain.go:[81](https://github.com/dapr/components-contrib/actions/runs/7830915945/job/21366093106?pr=3324#step:19:82) +0x1bf

ping @ItalyPaleAle

ping for review pls

ready

ping @ItalyPaleAle ready :)

ping for review please

ready for review pls

@JoshVanL another one for ya please whenever you're get a chance :)

@ItalyPaleAle this should be ready for rereview please

Ready for rereview please :)

This is ready for review please. Looks to me like the test failures are unrelated

can i get some feedback pretty please cc @JoshVanL @ItalyPaleAle

Thank y'all for the feedback! All feedback has been addressed or additional comments have been provided. cc @berndverst @JoshVanL @ItalyPaleAle

linter issues have been resolved. This should be g2g for merge pls and thank you!

@ItalyPaleAle I think I need your approval on here too for merging please :) Bernd gave the approval yesterday and I've fixed the linter issue.

gentle ping @ItalyPaleAle please 😇

Can I get help/advice on what y'all want for the dependencies pls? From what I see is that the certification tests go.mod dependencies are behind what the main module dependencies are for kit and dapr. However, the main module is using kit:
github.com/dapr/kit](http://github.com/dapr/kit) v0.13.1-0.20240306152601-e33fbab74548

And contrib in main branch also has dependencies on dapr/dapr v1.13.2 bc of fields brought into
http://github.com/forks/dapr/components-contrib/tests/certification/embedded/embedded.go

For:
DaprHTTPMaxRequestSize:    maxRequestBodySize,
DaprHTTPReadBufferSize:    runtime.DefaultReadBufferSize,

How should I proceed with fixing? bc my cert tests still fail but the main module dependencies if I bump the cert tests to are incompatible...

this is ready pls

@sicoyle I mentioned a few times to remove the patch file from your PR please. The 3346.patch file should not be in the PR. I will not approve and merge until this file is gone.

@holopin-bot @sicoyle Enjoy the Dapr components badge!


[HOLD on #15992] [$1000] Focus is not returned to the editor text field when a user opens settings sidebar and closes it

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Hover over an existing comment > click on ‘edit’ icon
Click on profile avatar
Close settings sidebar

Expected Result:
Focus should be returned to the editor text field
Actual Result:
Focus is returned to chat box
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.2.93-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/229302710-6ac50352-e56f-4d5d-ad23-40fcefe44acb.mp4
https://user-images.githubusercontent.com/43996225/229302717-bf2a5360-6e40-4703-b1af-a38fd5bca8ef.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680301816029279
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0151a26bfc95a8613e
Upwork Job ID:<PHONE_NUMBER>957026304
Last Price Increase: 2023-04-04

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Current assignee @garrettmknight is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

Triggered auto assignment to @francoisl (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Maybe we should add this issue on a tracking issue here https://github.com/Expensify/App/issues/15992

@bernhardoj just noticed you posted a similar question ^ to me, which is happening on this slack thread.

Added, putting this on hold similar to the other linked issue in that GH.

Still on hold

Still on hold.

Still on hold.

Still on hold - reassigning since I'm headed OOO. @johncschuster Tracking issue for the fix that might solve this is https://github.com/Expensify/App/issues/15992. Can you keep an eye on it and retest when that gets fixed? Thanks!

Hilariously, I'm going to be less available to work on this while at Expensicon next week. Reassigning as well.

Lol I'm OOO from the 17-23 but I'll check on this early next week before reassigning.

I'm heading OOO from May 17th-23rd. I re-added the Bug label to re-assign. If this is still on hold on May 24th, I'll take it back from you @mallenexpensify.

Still on hold, going to demote to Weekly for the time being.

I'm back from OOO, removing @mallenexpensify

Believe this is still on hold.

Still on hold.

Still on hold.

On hold.

On hold.

On hold.

Hold.

On hold.

On hold

On hold.

Oh hold

On hold.

On hold.

On hold.

Hold

On hold.

hold

Hold

Hold.

Still on hold.

On hold.

On hold.

On hold.

On hold

Not overdue - not sure why the overdue label keeps sticking.

On hold.

On hold.

On hold.

On hold.

On hold.

On hold.

Hold.

Ok, works for me.


Scrollbar is being reset after toggling the Intergrated Terminal

Version: 1.41.0
OS: Linux x64 4.15.0-54-generic
Steps to Reproduce:

Open the integrated terminal
Type something so the document height is big enough and vertical scrollbar is visible
Scroll down to the bottom
Hide the terminal (toggle)
Show the terminal (toggle again)

Expected behavior
The position of scrollbar is the same
Actual behavior
The position of scrollbar is reset to top, but the actual document is scrolled to bottom:

Does this issue occur when all extensions are disabled?: Yes

Just checked on the Windows machine, the same issue is happening there as well
Version: 1.41.1 (user setup)
OS: Windows_NT x64 10.0.18363

I have the same issue on a Windows machine and it`s so annoying

/duplicate https://github.com/microsoft/vscode/issues/84145


address regression with User code, fix RG delete test

Description of changes:

Change User code to be compatible with https://github.com/aws-controllers-k8s/runtime/pull/20
Fix RG deletion test (pytest was complaining about a direct call to a fixture)

Local e2e test run:
============================================================================ test session starts =============================================================================
platform linux -- Python 3.8.10, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
rootdir: /elasticache-controller/tests/e2e
plugins: xdist-2.2.0, forked-1.3.0
[gw0] Python 3.8.10 (default, May  4 2021, 19:07:02)  -- [GCC 10.2.1 20201203]
[gw1] Python 3.8.10 (default, May  4 2021, 19:07:02)  -- [GCC 10.2.1 20201203]
[gw2] Python 3.8.10 (default, May  4 2021, 19:07:02)  -- [GCC 10.2.1 20201203]
[gw3] Python 3.8.10 (default, May  4 2021, 19:07:02)  -- [GCC 10.2.1 20201203]
[gw4] Python 3.8.10 (default, May  4 2021, 19:07:02)  -- [GCC 10.2.1 20201203]
[gw5] Python 3.8.10 (default, May  4 2021, 19:07:02)  -- [GCC 10.2.1 20201203]
gw0 [9] / gw1 [9] / gw2 [9] / gw3 [9] / gw4 [9] / gw5 [9]
scheduling tests via LoadScheduling

tests/test_replicationgroup.py::TestReplicationGroup::test_rg_input_coverage
tests/test_replicationgroup.py::TestReplicationGroup::test_rg_cmd_update
tests/test_replicationgroup.py::TestReplicationGroup::test_rg_delete
tests/test_replicationgroup_largecluster.py::TestReplicationGroupLargeCluster::test_rg_largecluster
tests/test_replicationgroup.py::TestReplicationGroup::test_rg_cmd_fromsnapshot
tests/test_replicationgroup.py::TestReplicationGroup::test_rg_auth_token
[gw5] [ 11%] SKIPPED tests/test_replicationgroup_largecluster.py::TestReplicationGroupLargeCluster::test_rg_largecluster
[gw3] [ 22%] SKIPPED tests/test_replicationgroup.py::TestReplicationGroup::test_rg_auth_token x
[gw1] [ 33%] PASSED tests/test_replicationgroup.py::TestReplicationGroup::test_rg_cmd_fromsnapshot
[gw0] [ 44%] PASSED tests/test_replicationgroup.py::TestReplicationGroup::test_rg_input_coverage
[gw4] [ 55%] PASSED tests/test_replicationgroup.py::TestReplicationGroup::test_rg_delete
tests/test_user.py::TestUser::test_CRUD
[gw1] [ 66%] PASSED tests/test_user.py::TestUser::test_CRUD
tests/test_snapshot.py::TestSnapshot::test_snapshot_kms
[gw2] [ 77%] PASSED tests/test_replicationgroup.py::TestReplicationGroup::test_rg_cmd_update
[gw0] [ 88%] PASSED tests/test_snapshot.py::TestSnapshot::test_snapshot_kms
tests/test_usergroup.py::TestUserGroup::test_user_group_create_update
[gw2] [100%] PASSED tests/test_usergroup.py::TestUserGroup::test_user_group_create_update

================================================================= 7 passed, 2 skipped in 1688.28s (0:28:08) ==================================================================

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/ok-to-test
/test elasticache-kind-e2e

Missed some references to renamed fixtures, addressing those and waiting for tests to pass

previous run failed during Docker build step?
/test elasticache-kind-e2e


"Negative Scale Test" shows a hint of an "X"

Same with "khronos-TextureSettingsTest"

It seems that the offset normal is incorrect - implying also that the "faceNormal" is being computed incorrectly for the planes?

This is a result of the structure of the scene. Two planes are facing eachother - the front one with a red x - which is reflecting off the back face.


init: integration tests

WIP: Porting over existing integration tests

Codecov Report

Merging #318 (8759a62) into main (b191cf3) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 8759a62 differs from pull request most recent head 9bfba76. Consider uploading reports for the commit 9bfba76 to get more accurate results

@@           Coverage Diff           @@
##             main     #318   +/-   ##
=======================================
  Coverage   55.84%   55.84%
=======================================
  Files          46       46
  Lines        3651     3651
=======================================
  Hits         2039     2039
  Misses       1371     1371
  Partials      241      241

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 b191cf3...9bfba76. Read the comment docs.


feat: rename Linkfree to "BioDrop" in the footer section

What feature?
rename Linkfree to "BioDrop" in the footer section
Add screenshots

Record

[X] I have checked the existing issues
[ ] I want to work on this issue

Can I work on this?

fixed #58


Bug in Disappearance of Custom Component

Describe the bug
A clear and concise description of what the bug is.
As shown in Figure 1, the custom component added cannot be loaded in the new version of the code. After comparing the code before and after, it was found that the logic of assigning values to output_types has changed, as shown in Figures 2 and 3. When storing the output_type in the collection at the end, components with the same name are overwritten because output_type is used as the key, as shown in Figures 4 and 5.

Here is the code snippet from the "langflow/src/backend/langflow/interface/custom/directory_reader/directory_reader.py" file, where the assignment of the "output_types" variable has been modified, causing it to be duplicated. Later, when it is added to the set, the objects are overwritten due to the same key, and the corresponding component menu cannot be loaded:
` if validation_result:
try:
output_types = self.get_output_types_from_code(result_content)
except Exception as exc:
logger.exception(f"Error while getting output types from code: {str(exc)}")
output_types = [component_name_camelcase]
else:
output_types = [component_name_camelcase]
        component_info = {
            "name": "CustomComponent",
            "output_types": output_types,
            "file": filename,
            "code": result_content if validation_result else "",
            "error": "" if validation_result else result_content,
        }`


Update for V6

I've update the instructions to use the Theme with Twitterrifc 6 - which uses a new file format. There's also a small fix on some colors in the V6-theme because it seems there were some differences in the fileformat between V5 & V6

Oh wow, I didn't even see this until 4 months later. This looks great - thank you!


Use python_bin_path to check for site packages

This fix tries to fix the issue raised in #12232 where the python invoked the configure.py was used to check the site packages.
However, the site packages should be checked by the provided python_bin_path.
This fix fixes the issue. Below is the output after fix:
ubuntu@ubuntu:~/tmp/tensorflow$ ./configure
You have bazel 0.5.3 installed.
Please specify the location of python. [Default is /usr/bin/python]: python
Invalid python path: python cannot be found.
Please specify the location of python. [Default is /usr/bin/python]: /usr/bin/python3
Found possible Python library paths:
/usr/local/lib/python3.5/dist-packages
/usr/lib/python3/dist-packages
Please input the desired Python library path to use.  Default is /usr/local/lib/python3.5/dist-packages
Do you wish to build TensorFlow with jemalloc as malloc support? [Y/n]:

...
ubuntu@ubuntu:~/tmp/tensorflow$ ./configure
You have bazel 0.5.3 installed.
Please specify the location of python. [Default is /usr/bin/python]:
Found possible Python library paths:
/usr/local/lib/python2.7/dist-packages
/usr/lib/python2.7/dist-packages
Please input the desired Python library path to use.  Default is /usr/local/lib/python2.7/dist-packages
Do you wish to build TensorFlow with jemalloc as malloc support? [Y/n]:

This fix fixes #12232.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Jenkins, test this please.

Thanks @yifeif for the review. The PR has been updated with decode added.

Jenkins, test this please.

Thanks @yongtang! @tensorflow-jenkins test this please.

Looks like an infra failure, but just in case @tensorflow-jenkins test this please.

@tensorflow-jenkins test this please


Virus is in dev branch

I downloaded the StereorKit dev branch. While building it Windows Defender detected a virus.

Just as a note. I first unzipped the code and opened the solution in VS 2022. I dropped all the Android components. I built the solution but had two errors in the configuration related to the maui project and the Android components. Since it was otherwise unmodified I tried to delete the entire unzipped folder. I could not delete the zip created folder. After a reboot it deleted.
I then unzipped the code again and this time did nothing to the solution, just ran the build. That is when the Windows Defender detected the virus.

These files are generated by cmake when compiling a specific tag of the OpenXR Loader, so none of the relevant files are in SK itself. SK will first attempt to invoke the system's cmake, and if none is present, then use Visual Studio's copy of cmake. Based on the postfix in your version number, it looks like you may be using Visual Studio's copy of cmake.
I've scanned my own copy of this file, and Defender gives it a clean bill of health, but I'm using an official build of cmake 3.26.3. My primary guess is that this is a false positive? Use of the temp folder like this helps me a lot for build/clone times with multiple copies of StereoKit, but I could imagine this behavior looking odd to an antivirus. I may consider moving it back into the SK repository folder, I don't do a whole lot with multiple SK copies, so I won't mind the overhead too much.
I'm open to other possibilities, but nothing is jumping out at me.

@maluoi Rather long discussion. I am trying to do this so I can solve my actual problem detailed below.
I loaded the latest CMake on my computer. I scanned my entire computer and removed the virus (phantom or not). I deleted the folder where I had unzipped the SK project. I created a new unzipped folder. I opened the solution in VS2022 and upgraded the project to latest version for Windows 11/VS2022. In configuration manager I unselected the Android project and the Maui projects.
With CMake now installed I ran the build. I did not get a virus hit, but it will not build on my computer. I have included an output build dump. There are lots of errors (58). This is always frustrating to me. I know probably 95% of the people using SK just use the nuget package, I know I have because it is a pain to get it to build locally.
The only reason I am attempting this is because I can't get SK to work in a remoting environment where SK is in a server mode. When the remoting app is closed in the HoloLens 2 (same as X'ing out of a Window), SK.Run() shuts down and terminates. This action causes a network disconnect event in OpenXR. The Microsoft OXR extension then detects the entry into Disconnected state and closes the session and then stops listening for new connections.
What happens in the official sample application is slightly different. The sample has a Win32 app similar to the way SK remoting is effectively the Win32 app. The difference is the sample app does not close the window so the Microsoft extension does not stop listening. I am trying to find a way to not exit the SK.Run() on the close/network disconnect when in the "listen" mode i.e. Server mode.
The user can close the app from the HoloLens 2 main menu by hitting the "Home" button which is effectively the UWP app's X (close). It simply terminates the network connection, no grace here. The remoting HL2 App is unaware of the SK app running on the remoting device. It is entirely up to the server side what should be done on the disconnect event. I am trying to make SK aware of its role as a "server" to detect the three events from the Microsoft OXR extension: disconnected, connecting, connected. I need to handle the SK exit command by not shutting down SK but showing the user a main menu, with possible instructions on how to "end" the app using the HL2 main menu.

@maluoi trying not to give up on this. I got on my regular development machine that did have CMake on it and I updated it to a current version. I followed the same procedure as before with the same result. CMake will not build on a basically out of the box Windows 11 and Visual Studio 2022. There are so many errors that I really don't know where to begin.

It's possible maybe something from earlier caused corrupted in your build folder? I think the "Cannot open compiler generated file" and unable to unlink old issues at the start may be the big clues. I might try nuking the C:/Temp/StereoKitBuild folder and trying again.
Building SK itself will always be trickier that using the NuGet, unfortunately. Cross platform development for C++ is rough, and VS makes it worse by having no idea what dependencies are. I have been working a lot on the build system recently in preparation for CI/CD on GitHub Actions, so the next update may help make things a little smoother.
Regarding the functionality you're trying to solve, I don't know if OpenXR really has a good way to intercept and deny an exit event? I might recommend taking a peek over here though, where SK receives OpenXR's events. It does look like there could be some wiggle room for trying a few things.

@maluoi I did finally get a build on my regular dev box. Undoubtedly there is a difference between the machines. My dev box has been building C++ and SK since SK ver 0.3.0. It may have accumulated some hidden gems through the years that my backup machine does not have. I did update my old CMake to the most recent stable release on this machine.
I took a shot of my configuration so you can see what is getting built and of my solution in VS so you can see the projects. I have not modified anything except to upgrade to the VS Windows 11 SDK that VS offers when it first loads.


Extract message body without headers from envelope?

Hi! What's the straight-forward way to get the only email body out of the envelope, without the headers? There is e.Data but it also contains some header information that I don't need for processing the Body.
I read through the redis db processor example but still couldn't quite figure it out

Figured it out, the header end are the first \n\n


Static libraries

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
This PR ensures that libelf is statically linked when we build with BUNDLED_DEPS.  BUNDLED_DEPS are used when we build for example tar packages so we prefer to have always static libraries in order to ship the package without system dependencies
Moreover this PR adds libbpf as a cmake component since we don't want to use this folder during the packaging phase with cpack
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/hold

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold


Where i can define the username and password?

I cannot find this point in the DOC'S.
As newbie its relay difficult to set up this server without good docs.
ty

I'll have to make a separate doc for it. I'm assuming what you want is to authenticate the API for a remote server (you don't really need to do so on local host).
You need to edit the config file to:
"JSON-API": {
    "Authenticated": true,
    "Password": "2e844ad651c6b9a69cbe8f887b6a74dd3b9fc489aae777701e6e2d0d523a0cfb",
    "Username": "alice"
}

Where the password is the SHA256 has of your password.
You can have it hash your password for you by running:
./openbazaar-go setapicreds
You can also use cookie based authentication by leaving the un and pw fields empty and sending the string found in the .cookie file in the openbazaar2.0 repo in the header of the request.
Unrelated to the API you can also encrypt your db:
./openbazaar-go encryptdatabase

ty - now my shop can be a part of the network!

NODE
The config File is in [home]/.openbazaar2.0

not in the go folder

okay still cannot connect to my serve.
what for configs i have to do, to connect with the client to the go server and run a shop?

@i5heu Please keep in mind this is the 2.0 version which is still in development. For the current stable version check out https://openbazaar.org/download.html
For connecting to the 2.0 server the configs Chris mentioned should be enough. What do you get when you do curl <yourserver>:4002/ob? Make sure your server's firewall is allowing TCP ports 4001 and 4002 ingress.


Wrong REST API link

I think the wrong REST API link is used in this paragraph:
You can access your virtual machines in multiple ways. Run Command can run scripts on your virtual machines remotely by using the VM agent. You use Run Command through the Azure portal, [REST API](https://learn.microsoft.com/en-us/rest/api/compute/virtual-machine-run-commands), or [PowerShell](https://learn.microsoft.com/en-us/powershell/module/az.compute/invoke-azvmruncommand) for Windows VMs.
It currently goes to the Managed Run Command REST API, but it should go here to the Action Run Command API instead:
https://learn.microsoft.com/en-us/rest/api/compute/virtual-machines/run-command
Additionally, can we make it more clear on the separate API pages to distinguish if they're for Action or Managed Run Command? Its very confusing for customers to figure out currently.

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

ID: b3ff94e6-3c1f-b9e1-1a46-b75fe2ffca1b
Version Independent ID: 8f3ca735-ddd4-f4a9-4ee0-189604018784
Content: Run scripts in a Windows VM in Azure using action Run Commands - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/run-command.md
Service: virtual-machines
GitHub Login: @nikhilpatel909
Microsoft Alias: erd

@randolive
Thanks for your feedback! We will investigate and update as appropriate.

@ericd-mst-github
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

This is now fixed. We'll look into the API pages to make a better distinction for Action vs Managed.
#please-close

#please-close


[WINDOWS] Which tvm commit to use?

When I perform git submodule update --recursive following a pull in the nnvm repo, tvm is set to

Submodule path 'tvm': checked out 'eb761f36302d24c740b77281ecdcdddb588edf36'

and not its latest commit, is this the correct commit, because get the following linking error when compiling nnvm in Visual Stuidio 2015

1>compile_engine.obj : error LNK2019: unresolved external symbol "public: virtual bool const __cdecl tvm::Node::_DerivedFrom(unsigned int)const " (?_DerivedFrom@Node@tvm@@ueba?B_NI@Z) referenced in function "public: virtual bool const __cdecl nnvm::compiler::GraphCacheEntryNode::_DerivedFrom(unsigned int)const " (?_DerivedFrom@GraphCacheEntryNode@compiler@nnvm@@ueba?B_NI@Z)
1>graph_fuse.obj : error LNK2001: unresolved external symbol "public: virtual bool const __cdecl tvm::Node::_DerivedFrom(unsigned int)const " (?_DerivedFrom@Node@tvm@@ueba?B_NI@Z)
1>graph_hash.obj : error LNK2001: unresolved external symbol "public: virtual bool const __cdecl tvm::Node::_DerivedFrom(unsigned int)const " (?_DerivedFrom@Node@tvm@@ueba?B_NI@Z)
1>packed_func_ext.obj : error LNK2001: unresolved external symbol "public: virtual bool const __cdecl tvm::Node::_DerivedFrom(unsigned int)const " (?_DerivedFrom@Node@tvm@@ueba?B_NI@Z)
1>compile_engine.obj : error LNK2019: unresolved external symbol "public: static unsigned int __cdecl tvm::Node::TypeKey2Index(char const *)" (?TypeKey2Index@Node@tvm@@saipebd@Z) referenced in function "public: virtual unsigned int const __cdecl nnvm::compiler::GraphCacheEntryNode::type_index(void)const " (?type_index@GraphCacheEntryNode@compiler@nnvm@@ueba?BIXZ)
1>graph_fuse.obj : error LNK2001: unresolved external symbol "public: static unsigned int __cdecl tvm::Node::TypeKey2Index(char const *)" (?TypeKey2Index@Node@tvm@@saipebd@Z)
1>graph_hash.obj : error LNK2001: unresolved external symbol "public: static unsigned int __cdecl tvm::Node::TypeKey2Index(char const *)" (?TypeKey2Index@Node@tvm@@saipebd@Z)
1>packed_func_ext.obj : error LNK2001: unresolved external symbol "public: static unsigned int __cdecl tvm::Node::TypeKey2Index(char const *)" (?TypeKey2Index@Node@tvm@@saipebd@Z)
1>compile_engine.obj : error LNK2019: unresolved external symbol "public: static char const * __cdecl tvm::Node::TypeIndex2Key(unsigned int)" (?TypeIndex2Key@Node@tvm@@sapebdi@Z) referenced in function "public: class tvm::IRFunctor<void __cdecl(class tvm::NodeRef const &,class Halide::Internal::IRPrinter *)> & __cdecl tvm::IRFunctor<void __cdecl(class tvm::NodeRef const &,class Halide::Internal::IRPrinter *)>::set_dispatch(class std::function<void __cdecl(class tvm::NodeRef const &,class Halide::Internal::IRPrinter *)>)" (??$set_dispatch@UGraphFuncNode@compiler@nnvm@@@?$IRFunctor@$$A6AXAEBVNodeRef@tvm@@peavirprinter@Internal@Halide@@@z@tvm@@qeaaaeav01@V?$function@$$A6AXAEBVNodeRef@tvm@@peavirprinter@Internal@Halide@@@z@std@@@z)
1>graph_hash.obj : error LNK2001: unresolved external symbol "public: static char const * __cdecl tvm::Node::TypeIndex2Key(unsigned int)" (?TypeIndex2Key@Node@tvm@@sapebdi@Z)

Have you compiled TVM? You should compile TVM first following the TVM installation guide. If you need Python interface, don't forget to install their Python packages.
Also, as I can remember, you should CMake-build dmlc-core first to build TVM successfully.

I have build tvm, and successfully run the get_started.py without any errors.
Before updating to commit 'eb761f36302d24c740b77281ecdcdddb588edf36' I could also build nnvm without errors as well.  As nnvm seems to point to that commit I was wondering if that is the correct one to use, or should I use the latest one?

TVM should be backward compatible, i.e., new versions of TVM should do the same things as before. So if you want to use a newer version, just go ahead. The commit NNVM locked is simply 'the earliest version of TVM that NNVM will certainly work properly with.'

You should check the update number of your Visual Studio 2015. As the installation guide read, it requires VS2015 Update 3. I tried building it with VS2015 without Update and it failed, for 'unresolved symbols'. Now I am using VS2017, everything goes right.

Thank you, I have build with the latest version of tvm and nnvm with visual studio 2015 update 3 and I now get the following error when running the nnvm get_started.py

Traceback (most recent call last):
File "get_started.py", line 49, in
compute_graph, target="cuda", shape={"x": shape}, dtype="float32")
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm\compil
er\build_module.py", line 237, in build
graph = graph.apply("GraphFusePartition").apply("GraphFuseCompile")
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm\graph.
py", line 234, in apply
check_call(_LIB.NNGraphApplyPasses(self.handle, npass, cpass, ctypes.byref(g
handle)))
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm_base.
py", line 72, in check_call
raise NNVMError(py_str(_LIB.NNGetLastError()))
nnvm._base.NNVMError: TVMCall CFunc Error:
Traceback (most recent call last):
File "C:\Users\b8\Anaconda3\lib\site-packages\tvm-0.1.0-py3.5-win-amd64.egg\tv
m_ffi_ctypes\function.py", line 54, in cfun
rv = local_pyfunc(*pyargs)
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm\top\te
nsor.py", line 14, in _schedule_injective
return topi.generic.schedule_injective(outs)
AttributeError: module 'topi' has no attribute 'generic'

Are you able to run this sample when compiling with visual studio 2017?

Maybe you have missed a step: did you installed topi?

cd topi/python; python setup.py install --user; cd ../..

Thank you, I have recompiled so many times I forgot that step.  All is working now, at least for resnet18_v1 models from mxnet.  With this latest build I am still unable to import any other Gluon models.  For vgg16 I get the following error,

Traceback (most recent call last):
File "from_mxnet.py", line 71, in
graph, lib, params = nnvm.compiler.build(sym, target, shape_dict, params=par
ams)
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm\compil
er\build_module.py", line 216, in build
ishape, _ = graph_util.infer_shape(graph, **shape)
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm\compil
er\graph_util.py", line 28, in infer_shape
graph = graph.apply("InferShape")
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm\graph.
py", line 234, in apply
check_call(_LIB.NNGraphApplyPasses(self.handle, npass, cpass, ctypes.byref(g
handle)))
File "C:\Users\b8\Anaconda3\lib\site-packages\nnvm-0.8.0-py3.5.egg\nnvm_base.
py", line 72, in check_call
raise NNVMError(py_str(_LIB.NNGetLastError()))
nnvm._base.NNVMError: Error in operator dense0: [17:31:57] D:\SSDBackup\Dev\Repo
s\nnvm\src\top\nn\nn.cc:44: Operator dense(units=4096, use_bias=True, name=dense0) expects weight's shape to be [4096,7], but got [4096,25088].

in from_mxnet.py, changing
block = get_model('resnet18_v1', pretrained=True)
to
block = get_model('vgg16', pretrained=True)
should I open up an issue for this?

It seems the shape of the first FC layer in pre-trained VGG16 model doesn't match the deduced one... No idea why it was that.

should I open up an issue for this?

If you have done with the current topic (TVM commit), I think it's nice to close this issue and create another for the new topic.

Thank you for you help.


Automated cherry pick of #5444

Cherry pick of #5444 on release-1.44.
/cc  @enahum

/release-note-none


python couldn't show up when I try to create a virtual environment

The disappeared python can be pulled back in the existing dialog box


Mimes' emotes should be silent

Description

When mime scream or laughs there shouldn't be a sound
Also the emote popup might need to be changed to *screams silently or something similar
Reproduction

Be mime
Scream
Mime with sounds, the horror!

should be fixed by #16062

fixed