Different output for medium between openai/whisper and this

Hi,
First, let me start by saying great job. This is awesome! It's crazy how much faster this is than openai/whisper. I really appreciate the effort here.
I am running into a few issues and just want to better understand.
I am on the latest ctranslate2==3.6.0 and am using the medium model both with a beam_size=5 set. On faster-whisper, I get:
 ______ available?î Yeah. Speaker? ______, this is

And on openai/whisper I get:
I am using [NAME] here.
 __________ Hello. __________ Hello, is [NAME] available? __________ Yes, speaking. __________ Hi,

I have other examples of this as well but need to redact the text before I can post them.
I've also noticed non-English characters in the translation as well for faster-whisper for English-only audio. And even on 3.6.0, I still appear to get the beginning of my audio chopped off as well (but not all the time). It's seemingly random.
Is it normal to have some differences? Is there come config difference I am missing between the two?
While the speed increases are great, the inconsistencies are enough that we can't really use this over openai/whisper for our tasks. Anything I can do to help debug, let me know.
As a side note, I've been testing medium.en and the random characters seem to not happen and accuracy appears to be better for faster-whisper compared to the multi language model for faster-whisper where as medium for openai/whsiper appears to work fine.
Thanks in advanced!

Hi,
Differences are expected for segments that trigger the "temperature fallback", which is based on random sampling. This is likely what you are observing here since you noticed non-English characters in the output.
Can you try without the temperature fallback? For faster-whisper you can set temperature=0, for openai/whisper you can run with --temperature_increment_on_fallback None.
If you are observing difference after that, it would be great if you can provide a way to reproduce it.
But in general it's almost impossible to guarantee the same output. Even openai/whisper will not be consistent with itself when run on another device or system.

Hi,
Differences are expected for segments that trigger the "temperature fallback", which is based on random sampling. This is likely what you are observing here since you noticed non-English characters in the output.
Can you try without the temperature fallback? For faster-whisper you can set temperature=0, for openai/whisper you can run with --temperature_increment_on_fallback None.
If you are observing differences after that, it would be great if you can provide a way to reproduce it.
But in general it's almost impossible to guarantee the same output. Even openai/whisper will not be consistent with itself when run on another device or system.

Perfect, thank you. I'll try on Monday and get back to you. For now, it seems the medium.en model is doing much better for faster-whisper

You can also consider trying the large model in faster-whisper. It will still be faster and use less memory than the medium in openai/whisper.

When using temperature=0, I just get a bunch of silence:
Estimating duration from bitrate, this may be inaccurate
Detected language 'en' with probability 0.995432
[0.00s -> 30.00s]  __________________________________________________________
[30.00s -> 32.00s]  __________________________________________________________________
[60.00s -> 62.00s]  __________________________________________________________________
[90.00s -> 92.00s]  ______________________________________________________________

I will try large next and see what happens w/o changing the temperature.

Thanks for the feedback.
I reproduced a similar issue with the medium model and found this to be related to FP16 execution.
Can you help testing a change that makes some operations run in higher precision? Go to the build page, download the artifact "python-wheels", extract the archive, and install the appropriate wheel.
Hopefully this change will fix the transcription failures you are observing. There may be other small differences with the openai/whisper output, but I believe this is fine as long as the overall quality is preserved.

Thanks for the feedback.
I reproduced a similar issue with the medium model and found this to be related to FP16 execution.
Can you help testing a change that makes some operations run in higher precision? Go to the build page, download the artifact "python-wheels", extract the archive, and install the appropriate wheel.
Hopefully this change will fix the transcription failures you are observing. There may be other small differences with the openai/whisper output, but I believe this is fine as long as the overall quality is preserved.

Sure I can test this out today, thank you!

@guillaumekln With this w/ large, I am getting some weird output still.
libcode.exe is not available in this session for example shows up in the beginning of my text.
As well as 。 vpng for another audio file.

You should still set this compute type argument to "float16". The compute type mentioned in the PR is related to an external library.
"auto" is resolved to "int8_float16" on GPU which is no longer comparable to openai/whisper.
Can you retry with the "float16" compute type?

float16

Will do!

"auto" is resolved to "int8_float16" on GPU which is no longer comparable to openai/whisper.

Would this also explain beginnings of the audio being cut still as well?

Okay, so with large and float16, still get weird results:
                                                         Okay, so now do you have a complete bar kit? Not yet, no.

I am trying one last thing to be super sure. I am using pip install --no-deps to make sure the old ctranslate2 is not being installed somehow and explicitly setting all the dependencies.

Thanks for all the tests.
So what happens if you set compute_type="float"? Do you get the expected outputs?

Thanks for all the tests.
So what happens if you set compute_type="float"? Do you get the expected outputs?

Of course :) I actually did do that (I saw your other PR) and I am still seeing all those issues.
The loop from above, for example, is using float:
They will be asked questions on how to do certain tasks and will be asked questions on how to do certain tasks and will be asked questions on how to do certain tasks and will be asked questions on how to do questions on how to do certain tasks and will be asked questions on how to do certain tasks and will be asked questions on how to do сл

For completeness, could you post the command line that you used to convert the model and the code snippet you use to get the transcription from faster-whisper?

For completeness, could you post the command line that you used to convert the model and the code snippet you use to get the transcription from faster-whisper?

!ct2-transformers-converter --model openai/whisper-large --output_dir whisper-large-ct2 --quantization float16
Should I switch this to float as well now that I am using float?
segments, info = self.transcription_model.transcribe(filename, initial_prompt=self.prompt)
logger.info("detected language '%s' with probability %f" % (info.language, info.language_probability))
full_text = ""
for segment in segments:
    logger.info("transcribed [%.2fs -> %.2fs]" % (segment.start, segment.end))
    full_text += segment.text  # remove double whitespace, etc
logger.info(f"finished transcription for: {filename}")

Something I've noticed is, at least for that loop, that includes some of my initial_prompt text I am passing down. With openai/whisper it doesn't loop with the same prompt.

Sorry to keep bugging you with updates but I switched to openai/whisper for a few hours to just to sanity check and sometimes it skips beginning of audio, etc as well. Is this something where really I should have a process to re-run transcription when it looks like it failed?
I'm thinking maybe I just need a different approach where I detect bad/missing text and then re-run. Thoughts?

The "temperature fallback" that was proposed by the authors is already a mechanism that re-runs the transcription when it is considered failed. So I'm not sure it is useful to add another fallback layer.
Also, I just realized that the "large" model in openai/whisper is actually the new large-v2 version: https://github.com/openai/whisper/blob/9f7aba609971434b9de2a8d34ca2de766976904d/whisper/init.py#L28-L29
The large-v2 version is a separate model in the Hugging Face Hub, so you should convert openai/whisper-large-v2 when comparing the large size.

The "temperature fallback" that was proposed by the authors is already a mechanism that re-runs the transcription when it is considered failed. So I'm not sure it is useful to add another fallback layer.
Also, I just realized that the "large" model in openai/whisper is actually the new large-v2 version: https://github.com/openai/whisper/blob/9f7aba609971434b9de2a8d34ca2de766976904d/whisper/init.py#L28-L29
The large-v2 version is a separate model in the Hugging Face Hub, so you should convert openai/whisper-large-v2 when comparing the large size.

Will do! Thanks. I assume this still won't fix some of the other issues we've been seeing?

I have very limited results so far but with large-v2 and the latest master wheel from ctranslate2, things seem a lot better. Thank you so much. I'll keep you posted if I notice anything strange.

Thanks for the info.
As I get more feedback, I'm finding more small differences with the reference implementation. I'm not sure how impactful they are, but it's good to address them:

When computing the average log prob, they add a "+ 1" to the sequence length that we did not do. Fixed in https://github.com/guillaumekln/faster-whisper/commit/e47e00910a0c985be0f63bb7d6ba5f11fbaa9d39
The leading space should be removed before computing the compression ratio. Fixed in https://github.com/guillaumekln/faster-whisper/commit/4b8237da1bb9ef6ad7c2ef858af9e6d05c8cd93b
I read the reference code incorrectly and wrongly assume the EOS score was not included in the greedy search score. Fixed in https://github.com/OpenNMT/CTranslate2/pull/1096

Thanks for the info.
As I get more feedback, I'm finding more small differences with the reference implementation. I'm not sure how impactful they are, but it's good to address them:

When computing the average log prob, they add a "+ 1" to the sequence length that we did not do. Fixed in e47e009
The leading space should be removed before computing the compression ratio. Fixed in 4b8237d
I read the reference code incorrectly and wrongly assumed the EOS score was not included in the greedy search score. Fixed in Also include the EOS score in Whisper greedy search OpenNMT/CTranslate2#1096

This is great, thank you so much for all your work. Any way you can cut a new release soon for 3.6.1?

I just published the version 3.7.0 with the latest changes.

I just published ctranslate2==3.7.0 with the latest changes.

Thank you!

Hi @emhagman, do you think we can close this issue? Or are there still important differences with openai/whisper?

Hello,
I have a problem for Italian language. I was testing some samples from fleur dataset with small - int8 quantized model, beam_size=1, on windows. For some audios, it fell into a loop and it doesn't generate output. I tried with temperature 0 and it didn't change.
I attached a sample here.
I appreciate it if you could help me fix this.
https://user-images.githubusercontent.com/26019580/228672893-24edf894-9bb4-4a98-b5cd-d1de11252a71.mp4

Hi,
Thank you for sharing the audio! This example helped me find another small difference with openai/whisper. This requires an update of the model configuration to disable the generation of the task tokens <|transcribe|> and <|translate|>.
The new configuration is automatically downloaded if you load the model from a model size like:
WhisperModel("small", compute_type="int8")

If you converted the model yourself, you can either download the updated config.json or manually set the suppress_tokens argument:
model.transcribe(..., suppress_tokens=[-1, 50358, 50359])

Note that the temperature fallback seems helpful for this example, so you should remove temperature=0 before testing again.

Great! Thank you very much!

Oh sorry, they are:
small quantized model, compute_type="int8_float16" , beam_size=1, on windows, using cuda. BTW, when I use int8 for compute type, it works fine, the problem is only for "int8_float16".
Thanks.


Interactive container working differently than automatic execution

As a short preface, the interactive container is not really needed for this study, it's just a shell entry point with possible utility for debugging.
This issue came to my attention via a user relying on the opfvta-reexecution container as a way to gain containerized access to SAMRI (since there's no SAMRI container yet).
SAMRI uses nipype, and as part of running the preprocessing analysis nipype is imported.
That works fine (at the beginning I quit as soon as the preporcessing started, but it would continue going).
However, if I enter the container and try to import either nipype or analogous submodules of nipype which SAMRI imports, that fails:
[deco]~/docsrc/opfvta-reexecution ❱ make analysis-oci OCI_BINARY=podman
podman run \
	-it \
	--rm \
	-v /home/chymera/docsrc/opfvta-reexecution:/opt \
	-v /home/chymera/docsrc/opfvta-reexecution/inputs/opfvta_bidsdata:/usr/share/opfvta_bidsdata \
	-v /home/chymera/docsrc/opfvta-reexecution/inputs/mouse-brain-templates/mouse-brain-templates:/usr/share/mouse_brain_atlases \
	-v /home/chymera/docsrc/opfvta-reexecution/scratch:/root/.scratch \
	-v /home/chymera/docsrc/opfvta-reexecution/code/empty:/opfvta/ \
	--workdir /opt/code \
	docker.io/centerforopenneuroscience/opfvta:2.0.0-alpha \
	./produce-analysis.sh podman
/opt/code/opfvta /opt/code
rubber --clean article.tex
removing tree pythontex-files-article
removing tree pythontex-files-article
rm _minted-article -rf
rubber --clean pitch.tex
removing tree pythontex-files-pitch
removing tree pythontex-files-pitch
rm _minted-pitch -rf
rubber --clean review.tex
removing tree pythontex-files-review
rm _minted-review -rf
pushd prepare && ./run.sh
/opt/code/opfvta/prepare /opt/code/opfvta
!!! Repository 'gentoo' has sync-uri attribute, but is missing sync-type attribute
Failed to import duecredit due to No module named 'duecredit'
/usr/lib/python3.10/site-packages/bids/grabbids/__init__.py:6: FutureWarning: grabbids has been renamed to layout in version 0.6.5, and will be removed in version 0.8
  warnings.warn("grabbids has been renamed to layout in version 0.6.5, and will be removed in version 0.8", FutureWarning)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:283: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:296: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
/usr/lib/python3.10/site-packages/samri/pipelines/utils.py:335: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
  res_df = res_df.append(_df)
                                                   path modality subject session   task acquisition        acq  run  type scan_type
1365  /root/.scratch/opfvta/bids/sub-6257/ses-ofM/fu...      cbv    6257     ofM   CogB         EPI        EPI    0  func
1367  /root/.scratch/opfvta/bids/sub-6257/ses-ofM/an...            T2w    6654   ofMr1    NaN   TurboRARE  TurboRARE  NaN  anat
265   /root/.scratch/opfvta/bids/sub-6655/ses-ofM/fu...      cbv    6655     ofM   CogB         EPI        EPI    0  func
269   /root/.scratch/opfvta/bids/sub-6655/ses-ofMr1/...      cbv    6655   ofMr1  CogBr         EPI        EPI    0  func
267   /root/.scratch/opfvta/bids/sub-6655/ses-ofM/an...      T2w    6655     ofM    NaN   TurboRARE  TurboRARE  NaN  anat
272   /root/.scratch/opfvta/bids/sub-6655/ses-ofMr1/...       Is the docker daemon running?.
See 'docker run --help'.
make: *** [Makefile:89: analysis-oci-interactive] Error 125
[deco]~/docsrc/opfvta-reexecution ❱ make analysis-oci-interactive OCI_BINARY=podman
podman run \
	-it \
	--rm \
	-v /home/chymera/docsrc/opfvta-reexecution:/opt \
	-v /home/chymera/docsrc/opfvta-reexecution/inputs/opfvta_bidsdata:/usr/share/opfvta_bidsdata \
	-v /home/chymera/docsrc/opfvta-reexecution/inputs/mouse-brain-templates/mouse-brain-templates:/usr/share/mouse_brain_atlases \
	-v /home/chymera/docsrc/opfvta-reexecution/scratch:/root/.scratch \
	-v /home/chymera/docsrc/opfvta-reexecution/code/empty:/opfvta/ \
	--workdir /opt/code \
	docker.io/centerforopenneuroscience/opfvta:2.0.0-alpha \
	/bin/bash
f3444f102fb7 /opt/code # python
Python 3.10.10 (main, Mar 26 2023, 17:29:04) [GCC 12.2.1 20230121] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import nipype
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.10/site-packages/nipype/__init__.py", line 101, in <module>
    BaseInterface._etelemetry_version_data = check_latest_version() or "n/a"
  File "/usr/lib/python3.10/site-packages/nipype/__init__.py", line 85, in check_latest_version
    import etelemetry
ModuleNotFoundError: No module named 'etelemetry'

Any ideas what could be going on @yarikoptic @asmacdo

Though you call python from /opt/code, its looking for nipype in /usr/lib/python3.10/site-packages/nipype
Check the output of which python
It looks like you are using -v /home/chymera/docsrc/opfvta-reexecution:/opt \ to use your local python environment inside the container, so I don't think this should be relying on /usr/lib/ python env.

My first guess is this looks like a nipype bug to me, theres some unusual magic happening in nipype with etelemetry
https://github.com/nipy/nipype/blob/master/nipype/__init__.py#L75-L89
Maybe try setting NIPYPE_NO_ET
https://github.com/nipy/nipype/blob/056b48f23c896bed0fce1c571f33bb01922a1713/nipype/__init__.py#L96C47-L96C59

Since nipype is doing some unusual load logic, maybe try import nipype.interfaces.io as nio like how samri does it.
https://github.com/IBT-FMI/SAMRI/blob/1f1443973d1bcf123aa81456d80d27863d8b8d71/samri/pipelines/preprocess.py#L12C1-L12C35

sorry -- too much text.. what is the problem exactly?
meanwhile followed up on https://github.com/IBT-FMI/SAMRI/issues/119#issuecomment-1967917509

@asmacdo oh god. Thank you so much for bringing up that variable, I now remember everything. So yes, nothing is broken, I just forgot some finer points regarding how to use it:
f3444f102fb7 /opt/code # source /etc/profile
f3444f102fb7 /opt/code # python
Python 3.10.10 (main, Mar 26 2023, 17:29:04) [GCC 12.2.1 20230121] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from nipype.interfaces import fsl
>>>
KeyboardInterrupt
>>>
f3444f102fb7 /opt/code # cat /etc/env.d/98nipype
export NIPYPE_NO_ET=1

We need to run source /etc/profile for NIPYPE_NO_ET to be loaded. Our produce_analysis.sh script has that command.
But now that I hit this snag (again), maybe we could do something about it?
On a normal Gentoo system, you only need that if you want to have the environment variables loaded in currently open sessions.
Each new session will auto-load the environment variables on startup via source /etc/profile.
Any idea why OCI images don't auto-do it when you start your shell?


Update portfolio README to say that it's for the portfolio.

Testing making changes to your repo.

so do i still need to merge this?  or is this rejecting the PR?


widget-builder -h error

I'm using:

Node 18.16.0
Npm 9.5.1

After I run command npm run install-cli-win on Windows OS it works fine.
But when I run the command widget-builder -h I get error like below:
$ widget-builder -h
E:\widget-builder-1.0.0\dist\cli\run\init.js:10
const inquirer_1 = __importDefault(require("inquirer"));
                                   ^

Error [ERR_REQUIRE_ESM]: require() of ES Module E:\widget-builder-1.0.0\node_modules\inquirer\lib\inquirer.js from E:\widget-builder-1.0.0\dist\cli\run\init.js not supported.
Instead change the require of inquirer.js in E:\widget-builder-1.0.0\dist\cli\run\init.js to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (E:\widget-builder-1.0.0\dist\cli\run\init.js:10:36)
    at Object.<anonymous> (E:\widget-builder-1.0.0\dist\cli\index.js:12:32) {
  code: 'ERR_REQUIRE_ESM'
}

Node.js v18.16.0

@nguyenphuochien97 seeing the same thing - did you find a fix for this? On Mac 22.3.0 Darwin Kernel Version 22.3.0:.

If I roll back to https://github.com/bigcommerce/widget-builder/tree/6de3e1f18eedc74a133febf68f8e812e302d3ab4 - then npm run install-cli the app builds as expected.

@nguyenphuochien97 seeing the same thing - did you find a fix for this? On Mac 22.3.0 Darwin Kernel Version 22.3.0:.

Everything worked fine when I used the command npm install --save<EMAIL_ADDRESS>


Girlscript Summer of Code Introduction/Tracking

👋 Hi @HimanshuNarware ,
I am Sanjay, program Manager Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.
As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you :octocat:

[x] #5
[x] #6
[x] #7

@sanjay-kv  Done


Prevent synchronous writes when using Razor

Do not perform synchronous writes to the Response TextWriter after a Razor FlushAsync
Use ViewBuffer to perform async writes to the response when using ViewComponentResult

Related to #6397

/* No comments for this PR. */
Any updates for #9015?

Any updates for #9015?

I split this one off as a separate PR just because I realized it had mostly unrelated changes. I'll get the other one updated soon

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=156375&view=logs&jobId=2fe95fc5-ae3d-58fd-c2b8-46bb81541875

This comment was made automatically. If there is a problem contact ryanbrandenburg.
I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/2277


Toolbar implementation

A WIP. Getting my feet wet with this module/the win32 API/ctypes. I've been (slowly) trying to get toga-demo working.

So I opened this PR to get a preliminary look, since I'm not so familiar with ctypes & win32. On the right track?

This is fantastic - I haven't had a chance to fire this up on a Win32 box, but by inspection it definitely looks like you're on the right track!
The only cautionary note that I'll flag is that I'm in the process of changing the Cassowary-based layout to using a CSS-based scheme. This won't change the bulk of the widgets - a button is still going to be a button, and so on - but the mechanism for determining the size and position of that button will be changing a bit.
This shouldn't affect you in the short term; once I've got a better handle on the CSS stuff I should be able to assist on any migration that is required.

Groovy, FYI I'm still working on this, I just have less time now that I'm back in real life.

I'm going to close this PR; firstly, we've now found a way to access .NET APIs directly instead of using Win32; and secondly, we've transitioned to CSS-based layout which would require major changes to this PR.
Apologies for taking so long to respond to this, and even though we're not going to use the patch, thanks for the contribution.


Added Chi Square Calculator

Fixes Issue🛠

Closes # #1577
Description👨💻
Added Chi Square Calculator
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)
[x] New feature (non-breaking change which adds functionality)
[ ] Style (non-breaking change which improves website style or formatting)
[ ] Documentation (non-breaking change which updates or adds documentation)
[ ] Responsiveness (non-breaking change which improves UI/UX on different screen sizes)

Checklist✅

[x] I am an Open Source contributor
[x] I have performed a self-review of my code
[x] My code follows the style guidelines of this project
[x] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

@Damini2004, UI needs to be improved. Also, add your calculator in alphabetical order in main index.html file of the project.

@Nihal4777  Changes done
KInldy review and merge it.

@Rakesh9100 This PR is reviewed & can be merged.


register_device crashes when device already exists

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Running register_device with a device that already exists in the Apple team causes fastlane to crash. This appears to have just started happening recently (upgraded from 2.161.0 to 2.166.0). I would expect register_device to handle a 409 Conflict by ignoring it, or maybe an option as to whether a Conflict should be ignored or crash?
Command executed
fastlane run register_device
Complete output when running fastlane, including the stack trace and command used

Running 'fastlane run register_device name:TestDevice udid:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<EMAIL_ADDRESS>team_id:"XXXXXXXXXX"'...Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
-----------------------------
--- Step: register_device ---
-----------------------------
Login to App Store Connect<EMAIL_ADDRESS>Login successful
{
"errors" : [ {
"id" : "bef36781-0ef9-4302-b23a-a53433a1d16f",
"status" : "409",
"code" : "ENTITY_ERROR",
"title" : "There is a problem with the request entity",
"detail" : "A device with number 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' already exists on this team."
} ]
}
Looking for related GitHub issues on fastlane/fastlane...
Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
Run fastlane env to append the fastlane environment to your issue
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane_core/lib/fastlane_core/ui/interface.rb:129:in crash!': [!] Failed to register new device (name: TestDevice, platform: IOS, UDID: 7e0895d87c25a5e7b8aa8c4f1a2b9ee9792f39aa) (FastlaneCore::Interface::FastlaneCrash) from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/actions/register_device.rb:33:in rescue in run' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/actions/register_device.rb:29:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:229:in chdir'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:229:in execute_action' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/one_off.rb:42:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/one_off.rb:22:in execute' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/commands_generator.rb:224:in block (2 levels) in run'
from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/commands_generator.rb:352:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/bin/fastlane:23:in <top (required)>' from /usr/local/bin/fastlane:23:in load'
from /usr/local/bin/fastlane:23:in <main>' /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/spaceship/lib/spaceship/connect_api/api_client.rb:188:in handle_response': { (Spaceship::UnexpectedResponse)
"errors" : [ {
"id" : "bef36781-0ef9-4302-b23a-a53433a1d16f",
"status" : "409",
"code" : "ENTITY_ERROR",
"title" : "There is a problem with the request entity",
"detail" : "A device with number '7e0895d87c25a5e7b8aa8c4f1a2b9ee9792f39aa' already exists on this team."
} ]
}
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/spaceship/lib/spaceship/connect_api/provisioning/client.rb:73:in proxy_post' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/spaceship/lib/spaceship/connect_api/provisioning/client.rb:37:in post'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/spaceship/lib/spaceship/connect_api/provisioning/provisioning.rb:88:in post_device' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in post_device'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/spaceship/lib/spaceship/connect_api/models/device.rb:53:in create' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/actions/register_device.rb:30:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:229:in chdir'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/runner.rb:229:in execute_action' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/one_off.rb:42:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/one_off.rb:22:in execute' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/commands_generator.rb:224:in block (2 levels) in run'
from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/commands_generator.rb:352:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.166.0/bin/fastlane:23:in <top (required)>' from /usr/local/bin/fastlane:23:in load'
from /usr/local/bin/fastlane:23:in `'

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.4

Ruby
2.6.3

Bundler?
false

Git
git version 2.26.0

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.4 (19E266)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.3.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.166.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.6

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.15.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.73.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday
1.0.1

faraday_middleware
1.0.0

fastimage
2.1.7

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.10.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

naturally
2.2.0

simctl
1.6.8

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.14.1

signet
0.14.0

memoist
0.16.2

os
1.1.0

googleauth
0.11.0

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.3.1

google-cloud-errors
1.0.0

google-cloud-core
1.5.0

digest-crc
0.5.1

google-cloud-storage
1.26.0

emoji_regex
1.0.1

jmespath
1.4.0

aws-partitions
1.295.0

aws-eventstream
1.0.3

aws-sigv4
1.1.1

aws-sdk-core
3.93.0

aws-sdk-kms
1.30.0

aws-sdk-s3
1.61.2

bundler
2.1.4

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

webrick
1.4.2

generated on: 2020-11-11

Based on https://github.com/fastlane/fastlane/issues/17429 I rolled back to fastlane 2.162.0 and it works again - I'm able to run register_device with a device that I've already registered without fastlane crashing.

Hey @crooke ! 👋
Thanks for taking time to report this to us, and for providing valuable information 🙌  I've investigated this issue and opened a PR to fix it: https://github.com/fastlane/fastlane/pull/17799
If you could test it, it'd be much appreciated 🎉
I hope this helps!


Alert the user if imports/requires are missing, and add an -r flag to automatically insert them.

This adds a warning mechanism if you are using classes from your project that aren't imported. Have a look at the pictures:
Warning mode (default): http://i.imgur.com/MFFhg.jpg
Automatic insertion mode (-r, --require): http://i.imgur.com/H7dy7.jpg
The first simply gives you a warning when it finds missing imports/requires, while the latter inserts the missing imports automatically to the beginning of the files where the class(es) are referenced.
I hope you find it useful.

Closing as this wouldn't work in 0.9.


Cmd + K, Cmd + I should trigger custom hover in settings editor

Testing #153351
When the user triggers the custom hover in this way we should pass focus to the hover.
That way it is aligned with the editor and other vs code parts and it would be more accessible.
fyi @Tyriar for custom hover since we had similar discussions

Also ran into this. I could not find a way to open the hover using just the keyboard

Closing in favour of https://github.com/microsoft/vscode/issues/159088


Support all headers and properties exposed by ServiceBusReceivedMessage

Resolve https://github.com/Azure/azure-sdk-for-java/issues/27620

API changes have been detected in com.azure.spring:spring-messaging-azure-eventhubs. You can review API changes here

API changes have been detected in com.azure.spring:spring-messaging-azure-servicebus. You can review API changes here

API changes have been detected in com.azure.spring:spring-messaging-azure-storage-queue. You can review API changes here

API changes have been detected in com.azure.spring:spring-integration-azure-eventhubs. You can review API changes here

API changes have been detected in com.azure.spring:spring-integration-azure-servicebus. You can review API changes here

API changes have been detected in com.azure.spring:spring-cloud-azure-stream-binder-eventhubs. You can review API changes here

API changes have been detected in com.azure.spring:spring-cloud-azure-stream-binder-eventhubs-core. You can review API changes here

API changes have been detected in com.azure.spring:spring-messaging-azure. You can review API changes here


Remove requestAnimationFrame

Solves https://github.com/cornerstonejs/cornerstone/issues/276
Currently Cornerstone draw function is called using requestAnimationFrame that is 60 times a second (see
https://github.com/cornerstonejs/cornerstone/blob/master/src/enable.js#L77-#L94)
This is unneeded is very inefficient, draw should only be called once per need  which is what this PR ensures.
Further, drawImageSync is now throttled so that if multiple calls to draw the same element arrive within 1000/60 ms only the last one will be executed.

At first we were redrawing multiple times per frame which was very inefficient. I used the RAF mechanism because 1) it supports any refresh rate whereas this PR assumes a rate of 60hz (I am typing this on a 100hz monitor) and 2) it allows the browser to make smart decision on when to skip a rendering frame on heavy load.
This will result is bad frame pacing which will probably be noticeable while panning/zooming and might result in bad performance if the render time is about 16ms.
I didn't anticipate to have much more than 9 active elements at the same time and I can see how this solution not great for those use cases. However, I think leveraging RAF is still the best option and it would probably be best to find a way to debounce based on this trigger than assuming a 16ms refresh rate and a <16ms render time.

Thanks jpambrun !
One big issue with is RAF is that it just keeps running even when there has been no change, imgine a single change to the image - you want a single draw not 60 draws per second.

I only glanced quickly over the PR. EVENTS.PRE_RENDER was meant to be called on each browser frame in order to determined whether the elements needs re-rendering. In that case the even handler (from a tool, for CINE, etc.) would set needsRedraw. If I understand correctly, this PR will break this behavior and apps that depend on it.

To be fair, on my system the check and event trigger takes only ~50us per element.. Like I said on the issue, I didn't anticipate 200+ elements.. IIRC, I was disabling that somehow on thumbnails to reclaim some precious ms on a earlier project.

ok thx
if this was the intention I don't see it documented anywhere. EVENTS.PRE_RENDER is just triggered from CS but never cought. Does that mean the intention was for the refresh check to be done externally ? I don't recall any example doing that and wouldn't it make more sense for CS to determine that internally ?

I know for sure EVENTS.PRE_RENDER is used in a product I work on. I put it there for that reason. I was using it for multiple reasons including an improved CINE with more accurate frame pacing and timing.
A quick search reveal it's not used in csTools, but it might be by some users just like I did. I suppose the tools could register to RAF themselves, but it's a bit risky to change without a significant version bump.
All of that doesn't change the issue with the display rate and render time assumptions this PR made. There must be a simple-ish way to debouce those render calls based on RAF instead of a fixed 16ms timer?

(to me RAF is for animation - images that constantly change at a high rate - which is not our case here)

When you pan, zoom, une a measurement tool, change the voi, enable CINE you
are changing image at high rates, at animation rates. This is what RAF is
for really.
Furthermore, the timestamp becomes extremely important in CINE if you want
playback at the correct rate, for cardiac XA for instance.
On Thu., Feb. 28, 2019, 11:18 p.m. Kofifus<EMAIL_ADDRESS>wrote:

(to me RAF is for animation - images that constantly change at a high rate

which is not our case here)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cornerstonejs/cornerstone/pull/363#issuecomment-468536820,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAr2MOYUgd_BbYdB7A6LotSqMid0LcERks5vSKoKgaJpZM4bYFws
.

perhaps a better solution can be to dbounce cancelAnimationFrame()  ?

I am closing this now
The code works well but a better solution is in https://github.com/cornerstonejs/cornerstone/pull/374


[bug]: Can't find variable React

Description
I've imported '@walletconnect/modal-react-native' and included in the the react native app. I get this error which says can't find variable React. This error occurs only on android
WalletConnect Modal SDK version
1.0.0
Output of npx react-native info
System:
OS: macOS 13.5.2
CPU: (10) arm64 Apple M1 Pro
Memory: 98.06 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 16.15.0
path: ~/.nvm/versions/node/v16.15.0/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 8.19.4
path: ~/mobile-app-old/mobile-app/node_modules/.bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.12.0
path: /Users/shanthan/.rvm/gems/ruby-2.7.6/bin/pod
SDKs:
iOS SDK:
Platforms:

DriverKit 23.0
iOS 17.0
macOS 14.0
tvOS 17.0
watchOS 10.0
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9014738
Xcode:
version: 15.0/15A240d
path: /usr/bin/xcodebuild
Languages:
Java:
version: <IP_ADDRESS>
path: /usr/bin/javac
Ruby:
version: 2.7.6
path: /Users/shanthan/.rvm/rubies/ruby-2.7.6/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: ^18.2.0
react-native:
installed: 0.72.8
wanted: ^0.72.4
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: false
newArchEnabled: false

Expo Version (if applies)
No response
Steps to reproduce
Import the package into a react native project running on react-native ~ 0.72.4 and run it on android device
Snack, code example, screenshot, or link to a repository

@ignaciosantise

Hi @shan-c 👋 can you check if this solution works for you? https://github.com/WalletConnect/modal-react-native/issues/30#issuecomment-1631083948


Pegging not accurate

Price pegger not accurate, currently an offer of 1 USD costs 2690.10 SYS

isn't 1 USD 2690.1 sys in the price peg?

it's not but I'll close #37 since it was discussed on chat that it's currently set to that and will be updated.


Add rultor

@rultor hello

@rultor hello

@rultor hello

@levbagryansky Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)


Upload Attribute里的data参数要怎么用

Upload Attribute里的data参数要怎么用。

ElementUI version

OS/Browers version

Vue version

Reproduction Link

Steps to reproduce
What is Expected?
What is actually happening?

参照ajax post请求参数用法


Access violation in Rust 1.38

I made a new project to test this crate, here is my main.rs:
fn main() {
    use jwalk::WalkDir;

    for entry in WalkDir::new(".").sort(true) {
        println!("{}", entry.unwrap().path().display());
    }
}

On Windows, it returns error: process didn't exit successfully: target\release\test2.exe (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)
This only happens in a release build. In a debug build, it's fine.

I don't have windows to test on... generally that code seems to work on my MacOS machine in both debug and release mode... of course the content of . is maybe a deciding factor. What if you take out the forced .unwrap()?

Still doesn't work.
use jwalk::WalkDir;

fn main() {
    for dir_entry in WalkDir::new(".").sort(true) {
        if let Ok(entry) = dir_entry {
            println!("{}", entry.path().display());
        }
    }
}

Same exact error. It also occurs on nightly (I am using nightly-2019-10-04-x86_64-pc-windows-msvc)

I just ran it and for the first time got a different error message:
(exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)

If I set num_threads to 1, everything works fine.

If you set num_threads to 1 then it takes a different codepath that doesn't use Rayon. Sorry I don't know why the Rayon path wouldn't work on windows, I've only tested macOS.

I just released 0.5 which fixes some issues with rayon and I "think" fixes this issue. Though I can't be sure since I couldn't recreate it. Please reopen if not fixed.


Support forward testing

I love zipline, but I want to be able to forward test (paper trade) my algorithms using it, with some (or no) broker.
There is zipline-live, but that doesn't seem actively supported and hasn't been updated since August, 2019. Could that be because no zipline release has been made since?
If zipline will not be supporting forward testing itself, is there any other recommendation that should work?

There are multiple tentatives for paper trading (pylivetrader by Alpaca is the most recent one)
Zipline is a backtester and supports running scenarios in walk forward mode in the past. From my perspective, supporting paper trading falls outside of its functional scope and deserves to be an outside initiative.
Disclaimer I would recommend being careful when using any live or paper trading solution. Usually, the available packages are not clear enough about the risks involved.

I agree forward testing/paper trading should be an outside initiative, but I was unable to find one that seemed reliable or even actively supported that worked with zipline, leading me to believe the way forward (for me) was the either fork zipline to do that, or ask you guys for help :smile:
I can't find any mention of pylivetrader in the zipline docs, maybe it could be added as a recommendation for those wanting to paper trade their strategies?
I'll close this, now, as my my problem is solved at least.

@daraul , I think for the same reasons that you mentioned before on packages not being maintained and taking into account the risks involved in paper or live trading, endorsing a package doesn't serve Zipline's community.


Feedly and YouTube: some feeds are missing in macOS version, are visible in the iOS version (and in Feedly online)

Good morning.
I'm using NNW 6 and NNW 5 on macOS Bigsur, and NNW on iOS. All of them sync with my Feedly account.
I'm following a few YouTube channels, and mostly all of them are visible in both iOS and macOS versions of NNW.
One of them is never visible in the macOS version.
I have added the channel in Feedly using the following URL:
https://www.youtube.com/c/GemBoyOfficial/videos
How can I help to debug more this issue?
Thank you very much.

Duplicate of #2538


Handle user email ambiguity in exchangeSystemKeyForUserAuthByEmail

Description

See https://github.com/dust-tt/dust/issues/6669.
We identified the root cause of the registry lookup calls that would fail if we enforced permission checks tomorrow. It has been associated with Slack. Currently, we set a special header when creating a conversation or posting a message from the Slack endpoint. This header is used to exchange the auth object for a user-linked auth object, allowing us to 1. associate the user message with the correct user and 2. use the appropriate access when querying a data source.
The issue arises with the exchangeSystemKeyForUserAuthByEmail function, which selects the first user that matches the email address. This is problematic because we don't have a unique constraint on the email column in our table, potentially missing the correct user, the one with an active membership in the workspace.
This fix accounts for this possibility and fetch all matching users to narrow down to the ones with an active membership and takes the one with the oldest membership.
Although this is an edge case, we have 658 users with duplicated email addresses. This fix is not perfect, and we need a more reliable approach since debugging as an admin could be quite challenging once the permission check is enforced. We could consider using a user-id header, but this would only shift the logic to the connectors to map email to user, and the same issue would arise if two users within one workspace have the same email address.
Risk

Tested locally, worst case it does not use the right groups/users. We will monitor through here. Safe to rollback.
Deploy Plan

PMRR.


Problem with (@await func()).field

Looks like that the code like the following
var f = (@await func()).field;

is compiled into the following in python
f = await func().field

which raises exception AttributeError 'coroutine' object has no attribute 'field'

Should be fixed now


Monitor SSH private key for change

If the Kubernetes secret containing the SSH private key is updated externally, the change is eventually (potentially after several minutes) reflected inside the container tmpfs mount. We should monitor for this event with inotify and update fluxd state accordingly.

Do we not use the SSH key by referring to the file?

The private key yes; the public key & fingerprints are extracted from the private key and kept in memory.

It's possible the rewrites have fixed this; review at some point.

Is there a simple test-case for this?

Is there a simple test-case for this?

Start fluxd and let it generate an SSH
Ask for the public key with fluxctl identity
Generate a fresh key locally, and overwrite the secret that's mounted in fluxd
Wait for ten minutes so Kubernetes has had copious time to update the file in the container
Ask for the public key again -- did it change to reflect the key change?

I used kubectl exec <..> -- sh and ssh-keygen -t -rsa -f <..> to update the key. The output of fluxctl identity after waiting 10 mins was the same as before.

What were the exact arguments to ssh-keygen, and did you do anything else?

Only this:
[daniel@reef flux (⎈ |minikube:default)]$ kubectl exec -it flux-7bf686479d-5xqt4 -- sh
/home/flux # ssh-keygen -t rsa -f /var/fluxd/keygen/..weave-keygen473400537/iden
tity
Generating public/private rsa key pair.
/var/fluxd/keygen/..weave-keygen473400537/identity already exists.
Overwrite (y/n)? y
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /var/fluxd/keygen/..weave-keygen473400537/identity.
Your public key has been saved in /var/fluxd/keygen/..weave-keygen473400537/identity.pub.

I also had same problem, after patched k8s secret flux-ssh, then run fluxctl identity, it returns old public key

Flux v2, based on the GitOps Toolkit does monitor the SSH secret and uses the latest version every time it runs a git action.


Feat:Dockerize the app

Describe the feature
As you write we need this python version and also need to make virtual environment but many user feel difficulty in doing this and also for running your app may be some user may have not that python version so we have to dockerize the app

it helps in making virtual environment according to your given configuration in one line
it is not depend in mac or windows it works in all operating system
through one line command user can run your app easily

Add ScreenShots
no screenshot
Record

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

@agarwalhimanshugaya dockerizing for such smaller applications not worth it and also not everyone well aware about devOps so instead of dockerizing that way is more preferable by the majority.

@anurag6569201 yes u r right i thought in expect of doing all these steps in docker we run app with one command so that i suggest


[Bug]: Cannot run test runner with yarn test-storybook

Describe the bug
When I run yarn test-storybook in storybook version 7.0.26, I get this error.

But when running the interaction test via storybook manually, as in go to that component and let it run, they pass though.
To Reproduce
No response
System
System:
    OS: macOS 13.4.1
    CPU: (8) arm64 Apple M2
  Binaries:
    Node: 20.3.1 - /opt/homebrew/bin/node
    Yarn: 3.6.1 - /opt/homebrew/bin/yarn
    npm: 9.6.7 - /opt/homebrew/bin/npm
  Browsers:
    Edge: 114.0.1823.82
    Safari: 16.5.1
  npmPackages:
    @storybook/addon-a11y: ^7.0.26 => 7.0.27
    @storybook/addon-actions: ^7.0.26 => 7.0.27
    @storybook/addon-docs: ^7.0.26 => 7.0.27
    @storybook/addon-essentials: ^7.0.26 => 7.0.27
    @storybook/addon-interactions: ^7.0.26 => 7.0.27
    @storybook/addon-links: ^7.0.26 => 7.0.27
    @storybook/addon-mdx-gfm: ^7.0.26 => 7.0.27
    @storybook/addon-postcss: ^2.0.0 => 2.0.0
    @storybook/addon-styling: ^1.3.2 => 1.3.3
    @storybook/addons: ^7.0.26 => 7.0.27
    @storybook/api: ^7.0.26 => 7.0.27
    @storybook/blocks: ^7.0.26 => 7.0.27
    @storybook/components: ^7.0.26 => 7.0.27
    @storybook/core-events: ^7.0.26 => 7.0.27
    @storybook/jest: ^0.1.0 => 0.1.0
    @storybook/manager-api: 7.0.26 => 7.0.26
    @storybook/nextjs: ^7.0.26 => 7.0.27
    @storybook/react: ^7.0.26 => 7.0.27
    @storybook/test-runner: ^0.11.0 => 0.11.0
    @storybook/testing-library: ^0.2.0 => 0.2.0
    @storybook/theming: ^7.0.26 => 7.0.27

Additional context
Tried upgrading to 7.0.27, still the same error.

@yannbf Hi, thank you for your reply. We don't seem to be encountering this issue anymore. Should this come up again, I'll reopen this issue and attach a reproducible snippet. For now I'll close this issue.


Picasso.with() has been renamed to Picasso.get()

This form is for reporting issues in the Twitter Kit Android library. For all other developer questions/issues about Twitter please visit Twitter Community.
We welcome your contributions to improve the SDKs — whether adding new features, creating your own library that uses Twitter Kit, or fixing bugs you find in the code. We'd love to work with you so that Twitter Kit grows with your needs.
You are currently using an older version of Picasso. The Picasso.with() method has been deprecated and the Picasso.get() method is the new version. This is only a problem in applications that are already using an updated version of the Picasso library.
We work constantly to fix bugs, tweak functionality and improve device support. Providing detailed feedback will help us to quickly resolve your issue.

Steps to reproduce the problem (include logs and/or sample code where appropriate):
Implement the current version of the Picasso library, using the .get() method
Expected behavior:
The application compiles
Android API Version:
compileSdkVersion 27
minSdkVersion 21
Android Device (include Model and Manufacturer):
Essential PH-1 (test device)
Artifact Versions (run ./gradlew :app:dependencies):

Feature Request
If you have anything you'd like to contribute, we recommend discussing it with the core team before writing it.

Describe feature in as much detail as possible:
Include sample usage where appropriate:

Note: Twitter kit in no longer being actively developed. But if you submit a PR I can review and merge.

@efrohnhoefer I created a pull request for this: https://github.com/twitter/twitter-kit-android/pull/152

I am getting the minify warning that Picasso.with(context) is not present.
When the update to use the latest Picasso will get released?


some problems about mDenseSize in PaXoS

It seems that there are some data overflow problems in the code of PaxosImpl.h , as mDenseSize is not always less than 64, for example when mWeight=2 and mDt=binary. However, some operations such as the variable denseMasks, the function decode32 and backfillBinary, appear to assume that mDenseSize is less than 64. I also noticed the assert statement, but it doesn't seem to be working due to the "-DNDEBUG" setting. When I removed this setting, I saw the following error message.

If you could respond to this issue, I would greatly appreciate it.

Perhaps segmenting the data or continuing to use the BitIterator can help with this problem.

Why do you want to use w=2?

I just happened to come across and discovered this phenomenon while studying the algorithm and conducting tests, without any particular reason to use it, just for the purpose of testing.


cherry-pick: oadp-1.3: Add support for VSL name and labels (#1523)

(cherry picked from commit b5291301ff444e689e1384602f3b73de663a170f)
Why the changes were made
This is a cherry pick to 1.3 -> Add support for VSL name and labels
How to test the changes made
By using make deploy-olm and using name and labels in VSL

/retest
post restore flake


I don't understand how use "responsive"

Please, give an examples what should the object look like

Hi @leran, you use the same settings just within the media query you want, like this:
{
  top: 20,
  responsive: {
    1024: {
      top: 0
    }
  }
}

So this means, the sticky will have the top set to 0 below the 1024px of the screen width.
And you also use mobileFirst if you want the direction of the queries to go from lover to higher.
So you could write it like this:
{
  top: 0,
  mobileFirst: true,
  responsive: {
    1024: {
      top: 20
    }
  }
}

Or you can use it to disable the plugin for specific resolutions (I didn't include this in the readme, will update it):
{
  responsive: {
    1024: {
      disable: true
    }
  }
}

So with this the plugin will be disabled below 1024px screen width.


Domain Specific Texts of Multi Label Classification sample data should be modified

While working on quickstart of Multi-label classification, I found some file names of the sample data from this section contain domain-specific characters ( from German, French, and Spanish maybe?), which were shown garbled in my local laptop.
I could not train the multi-class classification model with the sample data as it is (See attached image) and needed to modify those file names. It was a bit dull.
Since we need to download the dataset on local PCs, I think such domain-specific names should be dealt with for a comfortable quick start for everyone.
Below are garbled titles that I found:

Das_schreckliche_Mädchen
Lucía,_Lucía
Mortelle_randonnée

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

ID: 61a20f08-a246-05be-0c99-b03d049a9bf5
Version Independent ID: b46fedb0-c2fa-2210-9c81-127ea1282192
Content: Quickstart: Custom text classification - Azure Cognitive Services
Content Source: articles/cognitive-services/language-service/custom-text-classification/quickstart.md
Service: cognitive-services
Sub-service: language-service
GitHub Login: @aahill
Microsoft Alias: aahi

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

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

Thank you for the immediate action!

Thanks @nawta for letting us know about this issue. I'll update these file names shortly!
#please-close


LUTECE-2209: upgrade javassist 3.1.12.GA to 3.23.1-GA to fix errors o…

…n java8 constructs (e.g. Method Reference)

Also, according to https://github.com/jboss-javassist/javassist/releases/tag/rel_3_19_0_ga java 8 support seems to be available starting from 3.19


Update editions-cloud-app-security-gcc.md

Sentinel supports MDA on all gov clouds.

Sentinel supports MDA on all gov clouds.
#sign-off

Sentinel supports MDA on all gov clouds.

Sentinel supports MDA on all gov clouds.
#sign-off

Sentinel supports MDA on all gov clouds.


bump timeout for deploy

Timeout fails sometimes in busy regions as 20 min is not enough for RP to gradually finish

quite extensive bump..

/lgtm
Useful. Today's eastus timedout during deploy.


Update LLVM/Clang to v4.0.0

To update to llvm 3.8:

Download the pre-build binary of LLVM 4.0.0 with Clang for Mac OS X.
Extract the content of the package (/usr/local/lib is a good candidate for a destination folder)
Include the path to {llvm-root}/bin/llvm-config or symlink to it in your PATH
Reset the cmake cache of the metadata generator project. This way the generator will be linked with the new version of Clang/LLVM.

Hi Ivan, I am the person that reported this to Sebastian, so I appreciate your support on this. What would you say the time estimate on this is?


Unexpected cls_targets results for short segments in label_points_single_video

Hello.
In the label_points_single_video method, when the integer parts of the segment's start and end values are the same (e.g., from 4.1 to 4.3) (this refers to segments, not timestamps), all elements of inside_gt_seg_mask become False, resulting in all elements of cls_targets being 0. Is this a bug? If this behavior is as intended, could you explain why it is implemented this way?
For example, in the case of gt_segment = (4.1, 4.3), I believe cls_targets[5, 0] should be 1. However, with the current implementation, all values become 0.
I also have a similar question. For instance, in the case of gt_segment = (3.3, 4.7), I think both cls_targets[4, 0] and cls_targets[5, 0] should be 1, but only cls_targets[5, 0] becomes 1. Am I misunderstanding something? Could you explain why it is implemented this way?

For the groundtruth assignment stage, you can refer to the center sampling paragraph in the paper. In short, short actions may be ignored and do not have groundtruth cls_target and reg_targets.


Dataset Viewer issue for openclimatefix/goes-mrms

Link
No response
Description
No response
Owner
No response

Closing, see #2385


pull request for e2e test at 01/23/2017 14:56:09

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Csrf does not work unless unit test are run

Laravel Version
Latest
PHP Version
8.2.10
Database Driver & Version
Mariadb 10.24
Description
Csrf check using sanctum endpoint will not work unless i modify this in vendor/laravel/framework/sec/illuminate/fondation/http/middleware/VerifyCsrfToken.php
I added a ! On Line this->runningTestUnit

Steps To Reproduce
None

Are you using Axios on your front end to make requests? If so check the Axios version you are using. If it is >= 1.6.0 the issue might be that Axios fixed a CVE which resulted in them no longer reading the XSRF-TOKEN cookie set by Sanctum and therefore the X-XSRF-TOKEN header is missing on your post requests which would be read by your VerifyCsrfToken middleware.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Hello
Ok i will do that
Thanks you
Le mar. 14 nov. 2023, 18:36, Dries Vints @.***> a
écrit :

Hi there,
Thanks for reporting but it looks like this is a question which can be
asked on a support channel. Please only use this issue tracker for
reporting bugs with the library itself. If you have a question on how to
use functionality provided by this repo you can try one of the following
channels:

Laracasts Forums https://laracasts.com/discuss
Laravel.io Forums https://laravel.io/forum
StackOverflow https://stackoverflow.com/questions/tagged/laravel
Discord https://discordapp.com/invite/KxwQuKb
Larachat https://larachat.co
IRC https://web.libera.chat/?nick=laravelnewbie&channels=#laravel

However, this issue will not be locked and everyone is still free to
discuss solutions to your problem!
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/49000#issuecomment-1810774682,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF233BREAWZDVSG7C45T6V3YEOT2NAVCNFSM6AAAAAA7KVMC6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQG43TINRYGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I do use axios superior to 1.6
I do get the XsrfToken on thé Reply in a cookie en en though thé status
code ils a 419.
I looked all over thé net for a solution. I tried retrieving the token from
thé cookie and stick it in a axios X XsrfToken header. It still sent me a
419 back.
Maybe i am missing some kind of configuration. I read today a Guy who had
it working bye setti g the option ''encrypted'' to TRUE bue i have not
tried that yet.
When i did the change inside the verifycsrftoken code as I described in thé
screenshot i get everything working properly using normal axios with auto
headers
Looking at the code i read it as it will check the token only if the method
''runingUnitTest'' returns TRUE... Which I found strange.  So I put a NOT
in front of that condition and it started working liké a charm
Sorry i have a french autocorrector on m'y phone and it really IS a pain....
😂
Le mar. 14 nov. 2023, 13:09, Ben @.***> a écrit :

Are you using Axios on your front end to make requests? If so check the
Axios version you are using. If it is >= 1.6.0 the issue might be that Axios
fixed a CVE https://github.com/axios/axios/releases/tag/v1.6.0 which
resulted in them no longer reading the XSRF-TOKEN cookie set by Sanctum
and therefore the X-XSRF-TOKEN header is missing on your post requests
which would be read by your VerifyCsrfToken middleware.
—
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/49000#issuecomment-1810086739,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF233BWFM5F35L7OO6RTYJ3YENNRBAVCNFSM6AAAAAA7KVMC6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQGA4DMNZTHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello!! update: I tested with axios 1.6.2.  which did not solve the problem... you have any news bout this issue?


missing analog and digital pin configuration of BBC Micro:Bit

Dear OpenRoberta Team,
I am learning the first steps of programming and have started yesterday with a BBC Micro:Bit at your homepage lab.open-roberta.org . Yesterday evening the Micro:bit produced a failure and I have seen no mistake in programming code.
Today I have tried the code again and it works. Then I wanted to make a new programming code. Now I am missing the choiceable analog and digital pins! I have to add them manually to the robotic configuration. There are only sensors, buttons and the buzzer ( no analog and digital pins ).

Go to https://lab.open-roberta.org/ and choose MicroBit as robotic
Click on Robotic configuration MICROBITbasis
See error: missing pin configuration. This has the effect, that I cannot choose a pin under Action/PIN/"Write analog/digital value on PIN "x"

Expected behavior
I have expected, that in the configuration are listed the pins! But there are no pins configurated!

Device information

Type: Desktop PC
OS: Windows 10 64-Bit Pro
Browser Microsoft Edge and Chrome

Was the failure yesterday around 21:00 CEST? That's when we created the new release, so that might be the cause.
Do you remember what exactly the error was?
As for the pins, you'll have to add them to the configuration yourself, you can drag them from the toolbox on the left.
We are working on the English documentation for the new configuration, for now here's the German one with some pictures, which might help.

Hi, thanks for response.
The failure has been at approximately 4pm o'clock yesterday.
At 11am o'clock I have tried the code again and it works.
But instead of PIN(0) there has been for example PIN(P0).
Yesterday I had not to configure the interfaces of BBC Micro:Bit.
All interfaces ( Pins, Sensors, Actuator ) has been available without anything.
I am thinking, that it is not well thought out for beginners like primary school students.
The basic configuration with all interfaces is more helpful for the entrance of coding.
If someone want to rename the Pins to more meaningful names, he could change them in the robotic configuartion.
When a beginners starts with questions like "How I can choose the PIN 0/1/2", it is not helpful in my opinion.
Can you change the basic robotic config of BBC Micro:Bit like before update?

Thanks a lot for the feedback, in our train of thought the pins are more of an advanced feature for more experienced users. That's why they are not in the default configuration.
Let's say you connect an LED to pin 0, you can name it redLed and have only the configured actor available in the program, instead of pins 0 to 20 without any context.
With this "configure first, program second" approach the programs can be a lot clearer.
For young students the configuration may be predetermined by the teacher, and the students just have to change the program.
But as you said it might make sense to have the more prominent pins 0, 1 and 2 in the default configuration, we'll discuss this.

We follow the "configure first, program second" approach.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg d481724...80c511a:
  > 80c511a Wait for reconciler/controllers to return prior to exiting the process (# 2437)
bumping knative.dev/hack a8ef7b6...cf8cbc0:
  > cf8cbc0 Fix the regex used for matching GitHub Actions files (# 156)

/lgtm
/approve


Is there any option to randomize a string once and use it across several templates?

Basically i want to generate a random string, and use it across several yaml templates (let's say, a deployment that expects it, and a secret that expects it as well).
Thanks

A Secret or Configmap is a way of doing this.

@arielb135 Probably best ask something like this out on the Helm users Slack channel.

A Secret or Configmap is a way of doing this.

i'll explain myself, i want to create a random string, then use it in multiple yaml files.
for example, if i could define in the helpers:
$password := (randAlphaNum 24 | nospace)
then use it it in several yaml files:
{{ {{ template "myapp.password" . }}

Here is a little example...
Define in helper template:
{{- define "chrt-6456.password" -}}
{{- randAlphaNum 24 | nospace -}}
{{- end -}}

and then reference it as:
data:
  password: {{ include "chrt-6456.password" .}}

It will not work as every time you call the template, new value will be generated, eventually I had to put both yamls on one file

ok, I see. You get caught with random as it regenerates . on each call unfortunately.

As explained above, if you want to share a randomized string being generated between multiple templates, then the templates need to be in the same file. See https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments for a usage example. I'll resolve this issue at this time; thanks for noting this. I've submitted a docs update: https://github.com/helm/helm-www/pull/877.

How is this going to work if I need to generate a random password for the initial admin user, use it in a post-install hook to set it and then display it in NOTES.txt so the admin user can log in? It seems ridiculous having to save the password in a secret which is never going to be used later (not to mention a potential security issue).

my 2 cents, a Helm chart called "my-apps" to deploy argocd apps, our use case is to prefix all Application resources with the SAME random string:
# templates/argocd-apps.yaml
{{- range .Values.apps -}}
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: {{ .Values.randomPrefix }}-{{ .name }}
  ....

The workaround:
I created another Helm chart that create a parent argocd app:
# templates/argocd-app-parent.yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: my-demo-web
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
  labels:
    helm.sh/chart: petal-apps-0.1.17
    app.kubernetes.io/name: petal-apps
    app.kubernetes.io/instance: release-name-petal-apps
    app.kubernetes.io/version: "0.1.17"
    app.kubernetes.io/managed-by: Helm
    random: MvHpm2zvzNJIVNap1L6PxTUm
  annotations:
    argocd.argoproj.io/sync-wave: "3"
spec:
  destination:
    ....
  project: my-demo
  source:
    ...
    helm:
      values: |
        fullnameOverride: web
        randomPrefix: {{- randAlphaNum 24 | nospace -}}

Note: I could also use Helm controller, and deploy a Helm release from another Helm release:
# templates/helm-release-parent.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  ...
spec:
  chart: stable/nginx-ingress
  targetNamespace: nginx-ingress
  valuesContent: |-
    randomPrefix: {{- randAlphaNum 24 | nospace -}}

Actually I have found something really cool!
The solution:
 helm install . will use a generated name aka {CHART_NAME}-{TIMESTAMP} referenced as .Release.Name


Numeric data causing error in tables

When I take away the numeric company Id the errors go away, All the codepens seem to work with numeric data so I am wondering if anyone has found a solution?
                  mdt-row="{
                            'data': filteredItems,
                            'table-row-id-key': 'company_id',
                            'column-keys': [
                              'company_id',
                              'company_name',
                              'position'
                            ]
                            }">
          <mdt-header-row>
            <mdt-column align-rule="left">Id</mdt-column>
            <mdt-column align-rule="left">Company Name</mdt-column>
            <mdt-column align-rule="right">Position</mdt-column>
          </mdt-header-row>
              <mdt-custom-cell column-key="position">
                <mdt-custom-cell-button ng-click="clientScope.c.selectPositionPrompt(rowId)">{{mdt-row.table-row-id}}</mdt-custom-cell-button>
              </mdt-custom-cell>
        </mdt-table>```

Looking into I think it may be a bug with JQlite. Is jQuery a dependency? http://stackoverflow.com/questions/37699741/using-jqlite-in-angularjs-to-append-text

Yes it is. Did it solve your problem?

Helped me alot @coopernewby
Thank you!


Destroy method

Is there currently a way to destroy and then re-instantiate instant search?
I'm trying switch the index of the instant search instance but can't get it work

Hello, there's currently no destroy method, we might create one and this issue would be the start of it.
About your need: do you just want to keep all the widgets but change the index? If so you could do it with a custom widget. Let me know so that I can guide you doing so.

Hello again
We're be using (ideally) one search input with 4 different search indices and different widgets per index.
I was planning to instantiate and then destroy the instant instance when the user changed tab but ideally we wouldn't do that.

So yes to do so maybe the best option would be to:

create one instantsearch per tab
each instantsearch has his own searchbox
show/hide the corresponding searchbox based on the selected tab
show/hide the corresponding widgets based on the selected tab (from what I see, the widgets will be different: no price slider for news)
create a custom widget that you add to every instance of instantsearch and that will update the counts next to each tab
create a custom widget that you add to every instance of instantsearch and that will update the query (helper.setQuery) every time the widget goes from hidden/shown then redo a search to update the interface (helper.search())
on tab change, show the right widgets, update the query (instance.helper.setQuery)

This is rather complex but what you are trying to do is very advanced and requires this coding. Let me know what you think

As a quick solution, just doing a new pageload on tab change is also feasible, since the whole interface is updating.

The first approach has worked quite well.
I've gone about implementing it by listening for the helper result event and then using setQuery to  change the query for the other instances. I've used the stats widget to output the count for each instance. Obviously it triggers a lot of queries/renders though so not sure how performant it will be.
The only outstanding issue is that the searchbox is not updating when the query changes. Is there a way to trigger a re-render or manually set it?

Awesome! Do you feel like writing a tutorial that we would publish on our blog? This seems to be like one of the most advanced usages of instantsearch.js that we did. Contact me at<EMAIL_ADDRESS>if interested.

Obviously it triggers a lot of queries/renders though so not sure how performant it will be.

Yes indeed that's why I proposed a solution where only the count is updated. We might have to re-think about this usecase once we have more feedback from you to see what could be done.

The only outstanding issue is that the searchbox is not updating when the query changes. Is there a way to trigger a re-render or manually set it?

Yes this is a known issue that I fixed yesterday, should be released soon (see #886)
In the meantime you can update the value of the input manually with DOM:
document.querySelector('#search-box input').value = ..;
helper.setQuery(..).search();

Does that makes sense?

I'd be happy to. The code is still a bit rough and we've still got a way to go with the formatting of the content but will get in touch once we've progressed it a bit further.
Cheers for the heads up on the search box.
How would you recommend creating a widget that just handles the count? I was thinking of using the 'resultevent to triggerAlgoliaSearchHelper.searchOnce` for the other indices.

How would you recommend creating a widget that just handles the count? I was thinking of using the result event to trigger AlgoliaSearchHelper.searchOnce for the other indices.

Yes that was the point of my

create a custom widget that you add to every instance of instantsearch and that will update the counts next to each tab

which was not enough detailed but you could create this widget and use the render() method to get an event when the search was really updated for the underlying instantsearch instance.
Then call otherInstances.helper.searchOnce(callback) and extract in the callback the number of hits for the hidden widgets.
Is that more clear?

destroy method will be implemented via #1065


Making @Column annotations in Bean types optional

The @Column annotations annotations in Bean types can be made optional since they are currently only descriptive metadata

Column export can now be enabled via setColumnAnnotations(true) and validation annotations setValidationAnnotations(true). Both are by default false.

Released in 2.3.0


feat: Initial support for SwiftUI

Hey there! I'd like to start using the BMAC badge in my SwiftUI project, but did not see support for it.
I somewhat implemented it in this PR and it seems to work (in the simulator) with IAP.
Would love some feedback as this would be my first PR on this Pod and I'm not sure they style you are looking for. This doesn't implement the fallback() mechanism fully and I know there are likely some other issues. I'm not super knowledgeable about Swift idioms but just looking to learn!
Here is a screenshot:

Let me know if we can collaborate and get this pushed through!
Related to https://github.com/appcraftstudio/buymeacoffee/issues/5
Signed-off-by: campionfellin<EMAIL_ADDRESS>

Hi there :)
Thank you very much for your work, I have to take a look at it because I don't understand why there is so much duplicated code. Why creating new color & font enum for SwiftUI and not extending the existing ones?
Moreover, regarding your screenshot, I'm not sure the button fit the Buy Me a Coffee guidelines (no round corners, no horizontal insets, and the shadow should be applied on the button itself, not its content.

Hey! Thanks for taking a look!
I haven't spent a ton of time developing with Swift, so I fully expect there to be issues.
I'll start with your suggestion about fixing the Color and Font enums so don't worry about reviewing that for now.
Good callouts on the styling! I'll see what I can do to make it look closer to the current button.

New screenshot:

Hey @frboulais any other big comments on this one?

Thanks for the feedback! I know there's a lot of issues with it, but this really helps! I'll continue iterating

Getting fairly close here. Pared most changes down to just the new BMCButtonUI file


add title attribute to link

Currently links generated by https://buttons.github.io/ have an aria-label but lack a title attribute. I suggest adding a title and giving it the same content as aria-label. This will allow a tooltip to display on mouseover in browsers like Chrome.
The main advantage of doing this is to let users determine where the button will take them before they click it. Yes, they could look in the lower left corner of the browser as they hover over it, but displaying a URL in the corner only occurs when you hover over links, and most users probably won't look down there because this project has gone through some great effort to make the button look like a button.

Initially it was decided to not add a title to the anchor to be consistent with twitter button.
Related to #35 / #32: To address these issues, a user specified title option was added to <iframe> or shadowRoot to help screen readers.
So currently there is a title option that explicitly set the title on <iframe> or shadowRoot. Honestly I do not know if both <iframe> and the anchor inside have title, what would happen to either regular devices, touch devices, or screen readers.

In v2.8.0 release, the behavior of setting title has changed:

The button link will has its title set.The shadow root will not have

The generator behavior will not change, which means user has to explicitly add a title attribute.


Add compatibility with Doctrine Collection interface

Is your feature request related to a problem? Please describe.
On our projects we use strictly typed collections for Doctrine. I think it will be nice if AbstractCollection class can implement methods from Doctrine Collection interface.
Describe the solution you'd like
I suggest to add methods to AbstractCollection and/or AbstractArray that will be compatible with Collection

public function removeElement($element)
public function containsKey($key)
public function get($key)
public function getKeys()
public function getValues()
public function set($key, $value)
public function key()
public function current()
public function next()
public function exists(Closure $p)
public function forAll(Closure $p)
public function partition(Closure $p)
public function indexOf($element)
public function slice($offset, $length = null)

Then user of the library can do something like this.
class ConcreteClassCollection extends Ramsey\Collection\AbstractCollection implements Doctrine\Common\Collections\Collection {
    public function getType(): string
    {
        return ConcreteClass::class;
    }
}

Describe alternatives you've considered
Maybe better approach is to add a trait?
class ConcreteClassCollection extends Ramsey\Collection\AbstractCollection implements Doctrine\Common\Collections\Collection {
    use DoctrineCollectionTrait;

    public function getType(): string
    {
        return ConcreteClass::class;
    }
}

If your goal is to have a Doctrine Collection compatible interface, why not use that package instead?

@shadowhand because there are no strictly typed collections in Doctrine package (no classes like AbstractCollection or AbstractMap) and we have to implement this intermediate logic in our projects. I like this library and I think it is good example of OOP.

A trait would be a reasonable approach, if the maintainers think this is a good idea.

I would be open to accepting a trait to make it compatible with Doctrine.

@strider2038, the best way is to create your own class Collection (inherit it from Ramsey\Collection\AbstractCollection) and add the necessary methods to it.

+1 to this!

I noticed some incompatibilities between this library and doctrine/collections and have raised an issue on Doctrine's side: https://github.com/doctrine/collections/issues/378


changes to open workshops cfp

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cdd3797). Click here to learn what that means.
The diff coverage is 58.33%.

@@            Coverage Diff            @@
##             master      #25   +/-   ##
=========================================
  Coverage          ?   60.62%
=========================================
  Files             ?       22
  Lines             ?      419
  Branches          ?       22
=========================================
  Hits              ?      254
  Misses            ?      165
  Partials          ?        0

Impacted Files
Coverage Δ

conference/cfp/workshop_urls.py
0% <0%> (ø)

conference/cfp/models.py
97.67% <100%> (ø)

djangocon_europe/settings.py
90.41% <100%> (ø)

conference/cfp/views.py
52.94% <55.55%> (ø)

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 cdd3797...a4bbcc1. Read the comment docs.


Add support to yaml files in addition to jsons

Referencing #124

+1
Any chances this will get merged any time soon?

Replied there. For now if needed you'll have to have your custom tap:i18n package in /packages with this PR merged.


Webview2 OpenDefaultDownloadDialog not working.

Describe the bug
Calling OpenDefaultDownloadDialog in Webview2 doesn't open the download dialog. Downloading File also doesn't open the default download dialog. The only time download dialog is opened when clicking on "Save as" in the context menu of WebView2.
Steps to reproduce the bug
call web.CoreWebView2.OpenDefaultDownloadDialog();
where web is WebView2 control.
Expected behavior
It should open the Default Download Dialog when calling OpenDefaultDownloadDialog();
Screenshots
No response
NuGet package version
1.0.0
Packaging type
Packaged (MSIX)
Windows version
Windows 10 version 21H2 (19044, November 2021 Update)
IDE
Visual Studio 2022
Additional context
No response

I opened this issue as https://github.com/MicrosoftEdge/WebView2Feedback/issues/2525 in the WebView2 repo, since it looks like an issue there.


Is it possible to use with Mistral or Zephyr models?

Mistral 7B and the finetuned version Zephyr 7B both use sliding window attention. Is there support for training this kind of models?

Hi,
I think it should be all right to train these models with LongLoRA. But I currently do not have enough machines and time to do so. It would be much appreciated that if you can contribution this with PR.
Regards,
Yukang Chen


Add CI/CD for Aarch64 pip wheels using GitHub Actions

Added GitHub workflow to build, test and publish Aarch64 pip wheels for Python versions 3.7, 3.8, 3.9 and 3.10
Workflow jobs run on a self-hosted runner on an AWS Graviton instance and triggers for:

Pull requests against r2.9 branch
New commits to r2.9 branch
New tags starting with v2.

Following tests currently fail and are skipped using tag no_aarch64:

tensorflow/python:nn_grad_test_cpu
tensorflow/python/eager:forwardprop_test_cpu
tensorflow/python/framework:node_file_writer_test_cpu
tensorflow/python/grappler:memory_optimizer_test
tensorflow/python/keras/engine:training_arrays_test
tensorflow/python/kernel_tests/linalg:linear_operator_householder_test_cpu
tensorflow/python/kernel_tests/linalg:linear_operator_inversion_test_cpu
tensorflow/python/kernel_tests/linalg:linear_operator_block_diag_test_cpu
tensorflow/python/kernel_tests/linalg:linear_operator_block_lower_triangular_test_cpu
tensorflow/python/kernel_tests/linalg:linear_operator_kronecker_test_cpu
tensorflow/python/kernel_tests/math_ops:batch_matmul_op_test_cpu
tensorflow/python/kernel_tests/nn_ops:conv_ops_test_cpu
tensorflow/python/kernel_tests/nn_ops:conv2d_backprop_filter_grad_test_cpu
tensorflow/python/kernel_tests/nn_ops:conv3d_backprop_filter_v2_grad_test_cpu
tensorflow/python/kernel_tests/nn_ops:atrous_conv2d_test_cpu
tensorflow/python/ops/parallel_for:math_test_cpu

Also, I think this should be opened on master?

I think the use of no_aarch64 tag to exclude tests that fail when TF_ENABLE_ONEDNN_OPT=1 is not the best thing to do. The flag is currently used to exclude tests that can never work on AARCH64. This would add a group of tests that we hope are only temporarily broken and so would have their no_aarch64 tag removed at some later point. It also stops those tests being run at all on AARCH64 even for the Eigen build, where they currently pass. I think some other mechanism would be better.

This is not the right way to temporarily exclude these tests. It hides the exclusion away in multiple places and also prevents these tests from being run for the default Eigen build where they are passing.

Hi @elfringham , I agree with your concern. We can introduce a new tag like no_aarch64_onednn_acl and use it to exclude these tests. Do you think that's an acceptable solution?

Could they not simply be listed explicitly in TF_TEST_TARGETS with the other test exclusions?

Hi @mihaimaruseac , I have signed the Google Individual CLA.

Also, I think this should be opened on master?

I have only tested this change on r2.9 branch as of now. I was thinking after the release, we can cherry-pick it into master.
Are you suggesting we do it the other way around - create this PR on master branch and when it gets merged, cherry-pick into r2.9 branch?

Yes please. We never cherrypick from release branch back into master.

Yes please. We never cherrypick from release branch back into master.

@mihaimaruseac I have opened another PR on master branch #56097 . Will close this PR and will cherry-pick into r2.9 later.