Installation Problem in RStudio

Hi, I tried to instal metaboshiny, but find an error like this. Thanks before for your help.
Downloading GitHub repo UMCUGenetics/MetaboShiny@master
These packages have more recent versions available.
Which would you like to update?
1: All
2: CRAN packages only
3: None
4: impute       (1.58.0 -> 559cacdb6...) [Bioc]
5: pcaMethods   (1.76.0 -> 0ae2f05a1...) [Bioc]
6: siggenes     (1.58.0 -> 3cb3d040a...) [Bioc]
7: globaltest   (5.38.0 -> 14fb0aa8b...) [Bioc]
8: GlobalAncova (4.2.0  -> 40f7cd29a...) [Bioc]
9: Rgraphviz    (2.28.0 -> 947bd0995...) [Bioc]
10: KEGGgraph    (1.44.0 -> 83fad7009...) [Bioc]
11: preproces... (1.46.0 -> 84da519db...) [Bioc]
12: genefilter   (1.66.0 -> cba90ff1b...) [Bioc]
13: SSPA         (2.24.0 -> 52a549f3a...) [Bioc]
14: sva          (3.32.1 -> 814ff269d...) [Bioc]
15: ChemmineR    (3.36.0 -> 1cbe310fa...) [Bioc]
16: KEGGREST     (1.24.1 -> 56d6223ac...) [Bioc]
17: fgsea        (1.10.1 -> 22c00b661...) [Bioc]
18: Rdisop       (1.44.0 -> fdd73a98e...) [Bioc]
19: Biostrings   (2.52.0 -> b8982e78c...) [Bioc]
20: GOSemSim     (2.10.0 -> ed0884a01...) [Bioc]
21: fmcsR        (1.26.0 -> 6176f38ea...) [Bioc]
22: hexbin       (1.27.3 -> 1.28.0      ) [CRAN]
Enter one or more numbers, or an empty line to skip updates:
1
impute       (1.58.0 -> 559cacdb6...) [Bioc]
pcaMethods   (1.76.0 -> 0ae2f05a1...) [Bioc]
siggenes     (1.58.0 -> 3cb3d040a...) [Bioc]
globaltest   (5.38.0 -> 14fb0aa8b...) [Bioc]
GlobalAncova (4.2.0  -> 40f7cd29a...) [Bioc]
Rgraphviz    (2.28.0 -> 947bd0995...) [Bioc]
KEGGgraph    (1.44.0 -> 83fad7009...) [Bioc]
preproces... (1.46.0 -> 84da519db...) [Bioc]
genefilter   (1.66.0 -> cba90ff1b...) [Bioc]
SSPA         (2.24.0 -> 52a549f3a...) [Bioc]
sva          (3.32.1 -> 814ff269d...) [Bioc]
ChemmineR    (3.36.0 -> 1cbe310fa...) [Bioc]
KEGGREST     (1.24.1 -> 56d6223ac...) [Bioc]
fgsea        (1.10.1 -> 22c00b661...) [Bioc]
Rdisop       (1.44.0 -> fdd73a98e...) [Bioc]
Biostrings   (2.52.0 -> b8982e78c...) [Bioc]
GOSemSim     (2.10.0 -> ed0884a01...) [Bioc]
fmcsR        (1.26.0 -> 6176f38ea...) [Bioc]
BioMedR      (NA     -> 1.2.1       ) [CRAN]
hexbin       (1.27.3 -> 1.28.0      ) [CRAN]
fields       (NA     -> 10.0        ) [CRAN]
Skipping 1 packages not available: org.Hs.eg.db
Installing 3 packages: BioMedR, hexbin, fields
There are binary versions available but the source versions are later:
binary source needs_compilation
hexbin 1.27.3 1.28.0              TRUE
fields    9.9   10.0              TRUE
Do you want to install from sources the packages which need compilation? (Yes/no/cancel) Yes
installing the source packages ‘BioMedR’, ‘hexbin’, ‘fields’
essai de l'URL 'https://cran.rstudio.com/src/contrib/BioMedR_1.2.1.tar.gz'
Content type 'application/x-gzip' length 2796519 bytes (2.7 MB)
downloaded 2.7 MB
essai de l'URL 'https://cran.rstudio.com/src/contrib/hexbin_1.28.0.tar.gz'
Content type 'application/x-gzip' length 648771 bytes (633 KB)
downloaded 633 KB
essai de l'URL 'https://cran.rstudio.com/src/contrib/fields_10.0.tar.gz'
Content type 'application/x-gzip' length 3268858 bytes (3.1 MB)
downloaded 3.1 MB

installing source package ‘BioMedR’ ...
** package ‘BioMedR’ correctement décompressé et sommes MD5 vérifiées
** using staged installation
** R
** data
*** moving datasets to lazyload DB
** inst
** byte-compile and prepare package for lazy loading
Erreur : .onLoad failed in loadNamespace() for 'rJava', details:
call: dyn.load(file, DLLpath = DLLpath, ...)
error: impossible de charger l'objet partagé '/Library/Frameworks/R.framework/Versions/3.6/Resources/library/rJava/libs/rJava.so':
dlopen(/Library/Frameworks/R.framework/Versions/3.6/Resources/library/rJava/libs/rJava.so, 6): Library not loaded: /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/lib/server/libjvm.dylib
Referenced from: /Library/Frameworks/R.framework/Versions/3.6/Resources/library/rJava/libs/rJava.so
Reason: image not found
Exécution arrêtée
ERROR: lazy loading failed for package ‘BioMedR’
removing ‘/Library/Frameworks/R.framework/Versions/3.6/Resources/library/BioMedR’
Erreur : Failed to install 'MetaboShiny' from GitHub:
(converti depuis l'avis) installation of package ‘BioMedR’ had non-zero exit status

Hi there, thank you for your interest! Installing rJava is notoriously annoying and the solution seems to differ per computer setup :( Could you try:
install.packages("rJava")
library("rJava")
and see if you can solve the problem with stackOverflow? Or are you on a system that supports Docker? (because that makes things a lot easier, it looks like you are on Mac :) )

I'd also suggest downloading and installing Java JDK 1.2 or higher (see rJava github repository), and update Java (8 or higher). Restart RStudio in Administrator mode, and try reinstalling rJava through
install.packages(" rJava", dependencies = TRUE)
library(rJava)


Why, just why?

Type of issue
Missing information
Description
[Enter feedback here]
please define the use of the parameter refreshToken - Why would you ever call a function called GetAccessToken that would not ever return a valid token? Why would there ever be a need for a parameter that asks for a refresh? Doesn't it make way more sense for this function to ALWAYS return something useable? Why would you ever need a parameter called refreshToken?  I do. Better yet, change the function so that it does what it says without any ambiguity.
Page URL
https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.services.appauthentication.azureservicetokenprovider.getaccesstokenasync?view=azure-dotnet-legacy
Content source URL
https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/xml/Microsoft.Azure.Services.AppAuthentication/AzureServiceTokenProvider.xml
Document Version Independent Id
ada30632-2508-a4ef-17a8-7a44bc820930
Article author
@azure-sdk
Metadata

ID: 40552281-44f9-b086-61f5-423b2bfcf0b2

Hi @vinceweeks-69.  Thanks for reaching out and we regret that you're experiencing difficulties.  The Microsoft.Azure.Services.AppAuthentication package reached end-of-life in March 2023 and is no longer published nor supported by Microsoft.  It is strongly advised that you not use this package, as it has known vulnerabilities that will not be patched.
As the library is unsupported, the Azure SDK team is unable to assist with this inquiry.


Outline buttons acting strange

I've recently updated my module from buttons to button. The button module is behaving funny when using the outline style which I prefer.  Your documentation doesnt state I need to update my style.cscss with "@import button;".  So I left the "@Import buttons;" alone.  On the grid view homepage, buttons are working as they should.
Following your instructions, the following occurs when I try to use a button with an outline style in a post

(not all the outline is working the button should have a full blue outline on my test, but its missing the bottom line)
In addition to this button text isnt changing with the theme, to white, like it should when I hover over the button.

Params are set as they should be.

Hey @jonniehack, I am sorry to hear that. can you tell me on which theme you are using this module?

Hey @jonniehack, Sorry to hear that. in your theme, search for .content class (maybe in the _common.scss file). and in that class, you will find styles for a tag. just replace the a with a:not(.btn), it will solve your issue.


fio-d: roles should include commands to drop caches

fio best practice is (generally) to sync and drop caches with every iteration/sample. This is usually done with:
sync; echo 3 > /proc/sys/vm/drop_caches

We could add this as a bash command to each test sequence, or we could include it directly in the fio job file with:
exec_prerun=sync; echo 3 > /proc/sys/vm/drop_caches

Might be worthwhile to make this optional in the CR for the off chance someone wants to test without this.

after the conversation earlier about pr #213 , this looks like outside scope of ripsaw, and more specific to snafu so closing this out.


Don't show latest tag

Also don't default to it: https://github.com/spark/particle-dev-local-compiler/issues/24#issuecomment-203885013


Recieving this error when deploying:  ENOSPC: no space left on device, write

when we remove the plugin details, it works fine.  Is adding the serverless-oneagent plugin adding too much to take up space?
plugins:
    - '@dynatrace/serverless-oneagent'

Deploying to AWS Lambda using Node version v10.18

We were able to get past this issue by adding this to the serverless.yml file
package:
  individually: true
  exclude:
  - tmp/**
  - .git/**


QC: Test mod_ParticipantMetricSummary_UI

QC Details
Implement testing, and make sure this file and any functions it contains are properly named.
Additional Comments

Implemented in #199.


Discrepancy in Documentation - Availability Set Back End Pool

You mention "Availability Zones" in the title, and in the documentation it references that "availability sets" can be targets of the backend pools for a Standard SKU load balancer, but this seems like that's no longer the case.
Can we confirm that either the documentation is wrong, or that there is an issue when setting the backend pool of a load balancer via the Azure portal?

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

ID: 9461e901-80bd-8dbb-b866-76dd7f7fcef4
Version Independent ID: 06daf40b-6a98-57bb-768d-6d296567f100
Content: Azure Standard Load Balancer and Availability Zones - Azure Load Balancer
Content Source: articles/load-balancer/load-balancer-standard-availability-zones.md
Service: load-balancer
GitHub Login: @asudbring
Microsoft Alias: allensu

@josh-gregory Thank you for your feedback . We will investigate and update this thread.

@josh-gregory , When you deploy a VM, you can either deploy it in an availability sets or Availability zones or standalone VM.  The new experience with Azure portal is to select the IPconfig for a selected Virtual Network. You just need to select the ipconfig of the VM which can be either part of availability set or availability zones or standalone VM.
Let me know if you have any further questions.

@josh-gregory , Do you have any update on this issue?

@josh-gregory , please tag me if you have any further questions.


Possible incorrect selection of TFL scans for NYU subjects

For each subject, we have a anat and famp TB1TFL scan. For MGH and MNI subjects, the bids_conversion.py script determines which scan is the anatomical scan and which scan is the flip-angle map scan by searching for the tokens anatomical image and flip angle map in the ImageComments attribute of the JSON. However, NYU subjects do not have this attribute in their JSON, and the information on what kind of TFL scan it is does not seem to appear anywhere in the JSON file. Since for MGH and MNI subjects, the anat scan is usually the first, and the famp scan is usually the third, this is what the bids_conversion.py script selects for NYU subjects. It is however likely that this is a mistake.
How should we differentiate TFL scans in NYU subjects to determine which one of them are the famp/anat scans?

The NYU scans are acquired with a scanner of a different generation, so it's not surprising that there are some differences. I have looked at both TFL scans (anat and fmap) and both appear to be flip angle maps. My guess is that one is distortion corrected and the other is not (I do not know which would be which, they are too noisy to tell). There also appears to be slight differences in the noise (perhaps anat is noisier). @alanseifert Can you weigh in?

I can only comment on what we get on our system (VB17): only a single
image, which is the flip angle map.
On Mon, Feb 19, 2024 at 9:14 AM evaalonsoortiz @.***>
wrote:

The NYU scans are acquired with a scanner of a different generation, so
it's not surprising that there are some differences. I have looked at both
TFL scans (anat and fmap) and both appear to be flip angle maps. My guess
is that one is distortion corrected and the other is not (I do not know
which would be which, they are too noisy to tell). There also appears to be
slight differences in the noise (perhaps anat is noisier). @alanseifert
https://github.com/alanseifert Can you weigh in?
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1952538399,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2H7B6VBJJCIF3VKIY3YUNM3VAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSGUZTQMZZHE
.
 The turboFLASH scans all have two images, both of which appear to be flip angle maps. There are not identical. They are very noisy, so it's hard to tell, but my best guess is that one is distortion corrected and one is not. Could you perhaps verify with one of the datasets you have? It could be any one of the 3 subjects, they all have the 2 FSL images.

I’m almost sure there’s more than 3 TFL scans outputted by the scanner for each NYU subject. The only reason there’s only 2 in the dataset I uploaded on the Google Drive is because my script naively assumes the first and third scans are the anat and famp scans respectively.
Since it has been verified by @evaalonsoortiz that they are both flip-angle maps, I will upload later today the other TFL scan not included in the dataset, and we can verify that this missing one is the anat scan. I will then modify the bids_conversion.py script to include that one instead of the other flip-angle map scan.

Hi Everyone,
I'm having a lot of trouble understanding the question.  Could you please
clarify what you're asking?
And you're asking about Mount Sinai data, not NYU, correct?  If this is
about the traveling spine study, NYU is not a member of that study.
On Mon, Feb 19, 2024 at 11:28 AM Kyota @.***> wrote:

I’m almost sure there’s more than 3 TFL scans outputted by the scanner for
each NYU subject. The only reason there’s only 2 in the dataset I uploaded
on the Google Drive is because my script naively assumes the first and
third scans are the anat and famp scans respectively.
Since it has been verified by @evaalonsoortiz
https://github.com/evaalonsoortiz that they are both flip-angle maps, I
will upload later today the other TFL scan not included in the dataset, and
we can verify that this missing one is the anat scan. I will then modify
the bids_conversion.py script to include that one instead of the other
flip-angle map scan.
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1952823120,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2E4Y2JZUNREKDL5QSDYUN4RZAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSHAZDGMJSGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @alanseifert,
Yes, I'm referring to Mount Sinai data. For some reason @dpapp86 stored all Mount Sinai data under an "NYU" label on our servers. @dpapp86 Was this a mistake? I had not realized Mount Sinai is not affiliated with NYU, so that's probably what he did. We will change the label.
Here's a screenshot of some of your TFL dicom data, converted to nifti. As you can see, two images are output.

When looking at those nifti images in FSL, both appear to be flip angle maps (see screenshots below).
We haven't identified any header labels to help us differentiate between the two images.

That looks different from the data I have locally.  Perhaps we used
different versions or command line options with dcm2niix?  I also have two
nifti's, but one has the two slice groups concatenated and another has only
one slice group (they must be manually re-interleaved).  See attached.
My only recommendation would be to investigate by starting again from
the DICOMs.
On Mon, Feb 19, 2024 at 12:06 PM evaalonsoortiz @.***>
wrote:

Hi @alanseifert https://github.com/alanseifert,
Yes, I'm referring to Mount Sinai data. For some reason @dpapp86
https://github.com/dpapp86 stored all Mount Sinai data under an "NYU"
label on our servers. @dpapp86 https://github.com/dpapp86 Was this a
mistake? I had not realized Mount Sinai is not affiliated with NYU, so
that's probably what he did. We will change the label.
Here's a screenshot of some of your TFL dicom data, converted to nifti. As
you can see, two images are output.
Screen.Shot.2024-02-19.at.12.03.27.PM.png (view on web)
https://github.com/spinal-cord-7t/coil-qc-code/assets/6652194/c120f952-7c0d-4b69-89ce-219ad280e0d9
When looking at those nifti images in FSL, both appear to be flip angle
maps (see screenshots below).
We haven't identified any header labels to help us differentiate between
the two images.
Screen.Shot.2024-02-19.at.12.04.15.PM.png (view on web)
https://github.com/spinal-cord-7t/coil-qc-code/assets/6652194/6ac9facf-925f-49c3-988d-4494883faa1c Screen.Shot.2024-02-19.at.12.04.31.PM.png
(view on web)
https://github.com/spinal-cord-7t/coil-qc-code/assets/6652194/0dcda0d2-04ca-4533-9f61-220892c4d4df
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1952894006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2GSKP4PBHOUGXHKVF3YUOBBFAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSHA4TIMBQGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I’m almost sure there’s more than 3 TFL scans outputted by the scanner for each NYU subject. The only reason there’s only 2 in the dataset I uploaded on the Google Drive is because my script naively assumes the first and third scans are the anat and famp scans respectively.
Since it has been verified by @evaalonsoortiz that they are both flip-angle maps, I will upload later today the other TFL scan not included in the dataset, and we can verify that this missing one is the anat scan. I will then modify the bids_conversion.py script to include that one instead of the other flip-angle map scan.

@Kyota-exe I think you might be referring to something else. In the screenshot I included above, you can see that there are 4 types of TFL scans that were acquired. Two are with different saturation flip angles (60 vs. 90), and two with different reference voltages.
The 90 degree saturation flip angle is the scan we want. The 60 degree saturation flip angle was acquired for another project. @alanseifert Can you confirm? Was the 60 degree saturation flip angle acquired for the fMRI or qMRI project?
@Kyota-exe Once it is confirmed that the 60 degree saturation flip angle images are for another project, we will select between the two voltages. We want the image acquire with an "optimized" reference voltage. You can find what that reference voltage should be in table 2 here: https://docs.google.com/document/d/1rfxDTc-coK96GMKsx5_sBK_srCyuKY7BY51qRYrDmig/edit
The table indicates that the subject "Daniel" was scanned with voltages 450V and 680V, which does not correspond to the 300V and 450V shown in the screenshot (the screenshot is for subject Daniel).  @alanseifert Can you weigh in on which voltage we should be going with for assessing the flip angle map? This will likely come up again for other subjects.

In my last e-mail I responded to the fact that there's two nifti's in each
of the 3-4 presatTFL directories, but yes, the different
presatTFL directories and separate acquisitions with the noted voltages and
saturation flip angles.  In some subjects (Daniel especially), the true
reference voltage is so high as to be impossible to acquire with saturation
FA = 90 and a correctly calibrated reference voltage, so in some cases, I
acquired with a decreased saturation FA = 60.
In your view, I also see that the scan directories have their acquisition
numbers stripped, which makes it more difficult to interpret which
presatTFLs are for which arm of the study.  Here, two are from the coilQA
arm, and one is from the fMRI arm.  There's probably also at least one
presatTFL from the qMRI arm as well, but I haven't merged the two sessions
in my local copy of the data.
Remember that I follow the green boxes in the SOP.  I'm unable to
automatically calibrate RefV, so I start with RefV = 300V and run a
presatTFL, then based on that, I calculate the actual calibrated RefV,
apply it, and re-acquire another presatTFL.  In this case, the calibrated
RefV was unachievable, so I used 450V, and at 450V, FA = 90 was
unachievable, so I used FA = 60.  It's up to you which one you want to use,
but because of these limitations, neither is exactly what your script is
probably expecting.
On Mon, Feb 19, 2024 at 12:26 PM evaalonsoortiz @.***>
wrote:

I’m almost sure there’s more than 3 TFL scans outputted by the scanner for
each NYU subject. The only reason there’s only 2 in the dataset I uploaded
on the Google Drive is because my script naively assumes the first and
third scans are the anat and famp scans respectively.
Since it has been verified by @evaalonsoortiz
https://github.com/evaalonsoortiz that they are both flip-angle maps, I
will upload later today the other TFL scan not included in the dataset, and
we can verify that this missing one is the anat scan. I will then modify
the bids_conversion.py script to include that one instead of the other
flip-angle map scan.
@Kyota-exe https://github.com/Kyota-exe I think you might be referring
to something else. In the screenshot I included above, you can see that
there are 4 types of TFL scans that were acquired. Two are with different
saturation flip angles (60 vs. 90), and two with different reference
voltages.
The 90 degree saturation flip angle is the scan we want. The 60 degree
saturation flip angle was acquired for another project. @alanseifert
https://github.com/alanseifert Can you confirm? Was the 60 degree
saturation flip angle acquired for the fMRI or qMRI project?
@Kyota-exe https://github.com/Kyota-exe Once it is confirmed that the
60 degree saturation flip angle images are for another project, we will
select between the two voltages. We want the image acquire with an
"optimized" reference voltage. You can find what that reference voltage
should be in table 2 here:
https://docs.google.com/document/d/1rfxDTc-coK96GMKsx5_sBK_srCyuKY7BY51qRYrDmig/edit
The table indicates that the subject "Daniel" was scanned with voltages
450V and 680V, which does not correspond to the 300V and 450V shown in the
screenshot (the screenshot is for subject Daniel). @alanseifert
https://github.com/alanseifert Can you weigh in on which voltage we
should be going with for assessing the flip angle map? This will likely
come up again for other subjects.
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1952922277,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2GIERTDZCUHHJCDV2DYUODNXAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSHEZDEMRXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

That script is the one to recombine when a 56-slice scan is output, where
the two slices packets are concatenated side-by-side, and need to be
re-interleaved.  I've never encountered the case where two scans, each
having 28 slices, is output.
All of my preSatTFL scans have two nifti's output.  I think there's
something different between your nifti generation and mine, so I don't have
much confidence in recommending any specific method to interpret or
re-interleave them.  I think you'll have to open your nifti's, look at what
they contain, and determine from there what needs to be done.
On Mon, Feb 19, 2024 at 1:07 PM evaalonsoortiz @.***>
wrote:

Ok, thanks @alanseifert https://github.com/alanseifert.
Following some more investigations, I've found the following: for subject
"Daniel", there are 4 TFL scans.
Screen.Shot.2024-02-19.at.1.01.19.PM.png (view on web)
https://github.com/spinal-cord-7t/coil-qc-code/assets/6652194/30009e20-6c0b-4b3e-86ee-813a5cfcc50a
dcm2niix generates two TFL scans for
preSatTFL_sag_2p5mm_FOV320_RefV300V_satFA90
dcm2niix generates one TFL scan for
preSatTFL_sag_2p5mm_FOV320_RefV450V_satFA60
dcm2niix generates two TFL scans for
preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V
dcm2niix generates one TFL scan for
preSatTFL_satFA90_sag_2p5mm_FOV320_RefV300V
When dcm2niix outputs two TFL scans, they each have 28 slices. When one
TFL scan is output, it has 56 slices. Therefore we should combine the
slices when two scans are output. @alanseifert
https://github.com/alanseifert is this
https://github.com/spinal-cord-7t/coil-qc-code/blob/main/combine_slice_groups.sh
the script you would usually use?
To continue on the multiple reference voltage and flip angle discussion:
@Kyota-exe https://github.com/Kyota-exe if you could summarize which
voltages and flip angle combinations are available for each subject, and
the voltages recorded in
https://docs.google.com/document/d/1rfxDTc-coK96GMKsx5_sBK_srCyuKY7BY51qRYrDmig/edit
we can then proceed to select the most appropriate combination to keep for
each subject.
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1952971149,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2CTLW35XQD2MKXMLK3YUOIHBAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSHE3TCMJUHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Optimal reference voltages for each subject in MtSinai:
Daniel: 680V
Laura: 350.3V
Rob: 436.9
The number of slices and the FA are taken from the .json, while the voltages are taken from the filenames.
Daniel:
2x28 slices, FA 90, 300V - (preSatTFL_sag_2p5mm_FOV320_RefV300V_satFA90)
1x56 slices, FA 60, 450V - (preSatTFL_sag_2p5mm_FOV320_RefV450V_satFA60)
1x56 slices, FA 60, 450V - (preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V)
1x56 slices, FA 90, 300V - (preSatTFL_satFA90_sag_2p5mm_FOV320_RefV300V)
Laura:
ERROR - (preSatTFL_sag_2p5mm_FOV320_RefV300V_satFA90)
ERROR - (preSatTFL_sag_2p5mm_FOV320_RefV354V_satFA80)
1x56 slices, FA 79, 365V - (preSatTFL_sag_2p5mm_FOV320_RefV365V)
2x56 slices, FA 80, 350V - (preSatTFL_satFA80_sag_2p5mm_FOV320_RefV350V)
Rob:
ERROR - (preSatTFL_sag_2p5mm_FOV320_RefV300V_satFA90)
ERROR - (preSatTFL_sag_2p5mm_FOV320_RefV440V_satFA60)
1x56 slices, FA 60, 450V - (preSatTFL_sag_2p5mm_FOV320_RefV450V_SatFA60)
1x56 slices, FA 60, 450V - (preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V)
1x56 slices, FA 80, 350V - (preSatTFL_satFA80_sag_2p5mm_FOV320_RefV350V)
Whenever it says ERROR, it's because dcm2niix fails to make the conversion and gives this error:
Warning: Interslice distance varies in this volume (incompatible with NIfTI format).
Unable to equalize slice distances: slice order not consistently ascending.
First spatial position repeated 1 times
Error:  Recompiling with '-DmyInstanceNumberOrderIsNotSpatial' might help.

My guess would be that the "Error" comes from the two slice packages of the acquisition not being properly offset. For example, if you move the FOV of slice group 1, but don't  move it for slice group 2, that could cause it.
If you open the "error" scans in a dicom viewer, is the inter-slice distance (the difference between the "position" values of the slices) constant?

@dpapp86 I can confirm that for Laura's preSatTFL_sag_2p5mm_FOV320_RefV354V_satFA80 scan, that seems to be the case. I haven't checked the other scans that give errors.
@dpapp86 and @alanseifert In order to sort through all the refV and FA combinations and choose between them, it would be helpful to have the input of whomever acquired each scan.
Here's where I'm at (whoever scanned the subject in question, please let me know your thoughts):
Subject: Daniel
As per Alan's previous comments, I think it makes sense to keep the 450V and FA60 scan.
There are two identical scans with those paramters:
preSatTFL_sag_2p5mm_FOV320_RefV450V_satFA60 Can be discarded as it was acquired with an incorrect offset
preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V has the correct offset, but there are two dicom series associated with this scan. One has a series number 3, the other 37. There are very slight differences between the two, described in a post above (https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1952894006). Note that I am inspecting the DICOMS not the niftis this time.
Subject: Laura
preSatTFL_satFA80_sag_2p5mm_FOV320_RefV350V is the scan with refV that is closest to the calibrated value, I would perhaps go with this. However, this scan also has two series associated with it (series 2 and 3). Just like the preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V scan for Daniel, both series has two slice groups, with the correct offset, and minimal differences between the two.
Subject: Rob
These scans come with the following note:
Calculated RefV was 491, used 450 instead... but I realized later that this calculation was incorrect because I assumed nominal saturation FA of 900, whereas it was actually 800.  The actual calculated RefV was 436.9 V, but I had already completed the entire protocol at RefV=450 by the time I realized this.  Scans are labeled with the reference voltage actually used.
I suppose it makes sense to keep the 450V/FA60 scan, given that everything else was acquired with 450V:
However, there are two seemingly identical scans to choose from. Why were two acquired? Both appear to have the correct slice thickness and slice gap.
preSatTFL_sag_2p5mm_FOV320_RefV450V_SatFA60
preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V

I don't think I ever drove the scanner at Mt sinai, so I have to leave the issue to @alanseifert

Some presatTFLs are for coilQA, some are for fMRI, and some are for qMRI.
You can check which series names correspond to which arms of the study by
looking at the PDF protocol exports.
I see the problem now for the qMRI presatTFL in Daniel's dataset.  There
must have been an errant click.  Slice group 1 has orientation S > T1.7,
slice group 2 is Sagittal.  Luckily there are so many presatTFLs to choose
from, and the ones in the coilQA and fMRI dataset don't have this issue.
Again, the answer to "why were two acquired" is because you have the entire
dataset, including two sessions, where one session is coilQA+fMRI and the
other is qMRI.  It looks like I used the ones that start with
preSatTFL_satFA60 in the coilQA+fMRI session, and the ones that start with
preSatTFL_sag_2p5mm in the qMRI session.
On Wed, Feb 28, 2024 at 6:26 AM dpapp86 @.***> wrote:

I don't think I ever drove the scanner at Mt sinai, so I have to leave the
issue to @alanseifert https://github.com/alanseifert
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1968780444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2H46FCLTNRWCITGX63YV4H67AVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYG44DANBUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Kyota-exe Here is my conclusion for what we should keep (ie, convert to nifti and include in the BIDS formatted dataset):
Daniel
preSatTFL_sag_2p5mm_FOV320_RefV450V_Sat60 : this scan was not acquired in sagittal orientation (S>T1.7). Both slice groups appear to have the same orientation.

The alternative scan (preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V) has the issue I've documented above (here and here. I have not been able to identify the cause of the issue, so I will discard the preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V scan for now.

I see the problem now for the qMRI presatTFL in Daniel's dataset. There must have been an errant click. Slice group 1 has orientation S > T1.7, slice group 2 is Sagittal.
…

I believe you are describing the preSatTFL_sag_2p5mm_FOV320_RefV450V_Sat60 scan, whereas I am talking about the preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V scan.
Laura
preSatTFL_satFA80_sag_2p5mm_FOV320_RefV350V : there are two scans with this exact same name, both are part of the coilQA leg of the study. One is series 2, the other series 3. Since they appear to be identical, we can arbitrarily go with series 2.
Rob
preSatTFL_satFA60_sag_2p5mm_FOV320_RefV450V : This was an easier choice, there are more scans to choose from for this subject and all appear to be acquired with the correct parameters.

Thank you. For Mt_Sinai subjects we won't have any anatomical TFL scans then?

I'm still not sure what you mean by TFL anatomicals.  Our TFL sequence
produces only a map.
On Thu, Mar 7, 2024 at 11:20 PM Kyota @.***> wrote:

Thank you. For Mt_Sinai subjects we won't have any anatomical TFL scans
then?
—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1985015295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH77D2FQQE3FYKGEZW2YGALYXE4AVAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBVGAYTKMRZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

But on Terra systems, you also get an anatomical, GRE-like contrast image,
not just the B1+ maps. I'm guessing this is what Kyota is looking for
On Fri., Mar. 8, 2024, 12:25 Alan Seifert, @.***> wrote:

I'm still not sure what you mean by TFL anatomicals. Our TFL sequence
produces only a map.
On Thu, Mar 7, 2024 at 11:20 PM Kyota @.***> wrote:

Thank you. For Mt_Sinai subjects we won't have any anatomical TFL scans
then?
—
Reply to this email directly, view it on GitHub
<
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1985015295>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AH77D2FQQE3FYKGEZW2YGALYXE4AVAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBVGAYTKMRZGU>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1985525317,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATDM6U2I2INHZB46CM4BVYDYXGN2PAVCNFSM6AAAAABDN3Z222VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBVGUZDKMZRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

This issue has been resolved as per https://github.com/spinal-cord-7t/coil-qc-code/issues/13#issuecomment-1981499263


Add Authentication Support

This is most of the code for #2.
There still remains testing and UX/UI stuff, but it is shippable.

Merged master in to resolve conflicts, but there are a couple tweaks to make before this should be merged.

@frogrammer I've added some documentation to this and moved the hard-coded values out into the config file, so this is ready to merge unless you have concerns. I'll post the Google API keys to Slack.

Oh wait, I forgot to put everybody else in the admin list.

@lverns I still see some hard-coded localhost in a few places but we can change them later?

Yeah, I just noticed that and am fixing that right now.

okay, I think I got them all

Seems good. Let me merge it.


Hires parameters

Added new parameters to Hires fix:
hr_prompt
hr_negative_prompt
hr_checkpoint_name
hr_sampler_name
hr_scheduler

They are relative to these interface elements:

can any of the main devs finish reviewing this so it can be merged into the main? these API parameters are too important to ignore

I think the PR changes are already in the main branch:
https://github.com/mix1009/sdwebuiapi/pull/183/conflicts
The default parameters are different. If they make a difference please inform me.

I guess the link is temporary or only available to reviewers.
Here's the capture of the changes with the current main thread:


fix: demo bug

Unix Timestamp (milliseconds) show the wrong demo

this means to parse a timestamp
+dayjs(1548381600000)  =<PHONE_NUMBER>000

I'll close this issue since it's been a while since it's been opened. Feel free to reopen if you have updates on this


Add two new APIs: getTrainsferIDs/postTransferIDs to deal with transfer IDs

Fixes #9198
Status
not-tested
Description
Add two new APIs to deal with transfer IDs
We need a new transferids database in CouchDB to store this data.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
#9198
External dependencies / deployment changes
no

@amaltaro , this PR introduce new APIs to fetch and store transfer IDs doc. For that we need to create a new DB in couch. I called transferids. Please review and make comments. Once this APIs will be in place I'll move forward with using them in MS (see #9276 )

Alan, please post which APIs should be used. We need not only APIs how to fetch IDs/subscription but also APIs where we can get info about transfers. The requestinfo Phedex API returns IDs, but it is unclear how we can use those IDs, while subscriptions API returns details of subscription and its records contains percentage info which we need. For the reference, the Unified code use the later (subscriptions API).

@amaltaro , Alan please review and merge this PR

This code would need a new transferinfo REST API to be created.
Besides that, I'd like to discuss (maybe on the Monday chat) how we'll handle those transfer-related data. My initial idea was the simplest possible, which is:

we store transfer-related data in a single document in CouchDB, making it much easier to manage and GET and PUT any new data in.
however, for that to work, we'd have to make updates in bulk. E.g., the transferor thread would handle X requests (100?), once transfers are all done, then it would update this document. The problem on this approach is that if the thread/node crashes in the request number 99, then we lose everything that has been done up to that point, and the thread needs to run the same thing again in the next cycle.
same applies to the monitor thread, it would have to update in-memory the status of X requests/transfers and once all of those were updated, then we trigger a CouchDB document update to persist that information.

In short, besides the eventual document conflicts that we'd hit (and we need to handle that problem), we could as well lose part of the work done by the thread, having to wait until the next cycle to try again.
SO, my second suggestion would be to create one transfer document for each workflow in the system, such that having problems with one request has no effect at all on the overall thread execution.
The drawback on this case is that we need to have additional micro management of the documents, it has more network and REST API calls and it's likely going to be slower.

Superseeded by https://github.com/dmwm/WMCore/pull/9307


Figure out how to maintain versions of test containers

Our ContainerResourceLifecycleManager implementations often reference container versions. We have no process/tool in place that would ensure that the versions stay up to date, esp. that the version of the given container is close enough to the version of the respective library.
One possible solution that comes to my mind is to maintain the versions in the top pom.xml either using the same property as the respective library or using a separate property, but placing it along with the lib version prop, so that any discrepancy gets noticed when the lib is upgraded.
Any other ideas?

FWIW, there is a test-infra in Camel we could try to leverage so at least version can be aligned at Camel, of course we sometime need to override versions and in such case we can use the mechanic you described

You mean we should start using Camel test-infra instead of our custom ContainerResourceLifecycleManagers? Can test-infra set the environment for the test that runs in a separate JVM?

We should at least investigate if we can use test-infra since it is used by camel and camel-kafka-connector.
AFAIK each test-infra set some system properties so we probably need to wrap them in with a ResourceLifecycleManager but I guess it is doable

Slightly related, we may want to think about which base images we use, because it seems we're starting to run low on disk space in CI. Something I noticed in the Camel 3.8 upgrade PR:
Caused by: java.lang.RuntimeException: Unable to start Quarkus test resource org.apache.camel.quarkus.component.vertx.kafka.it.VertxKafkaTestResource@64e05a38
	at io.quarkus.test.common.TestResourceManager.start(TestResourceManager.java:57)
	... 44 more
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: Check failed: Docker environment should have more than 2GB free disk space
	at org.apache.camel.quarkus.component.vertx.kafka.it.VertxKafkaTestResource.start(VertxKafkaTestResource.java:45)
	at io.quarkus.test.common.TestResourceManager.start(TestResourceManager.java:52)
	... 44 more
Caused by: java.lang.IllegalStateException: Check failed: Docker environment should have more than 2GB free disk space
	at org.testcontainers.DockerClientFactory.check(DockerClientFactory.java:298)

IIRC we can disable those checks if we really need to.

I think we should have these versions in the top level pom.xml and pass them to surefire/failsafe via properties.
Having them in top level pom.xml somewhere near the related Maven artifact versions would make it easier to maintain both at some near/compatible versions. In some cases, the versions will be the same, in others they will be the same major.minor or similar.

pass them to surefire/failsafe via properties

That's a pain for platform integration though. Because you have to do the same change(s) there.
What I was thinking, is that we could define the versions as Maven properties, and then generate a META-INF/microprofile-config.properties for each test-jar. That would you let you use the ConfigProvider to resolve the container image names / tag versions. You'd get enablement of overrides via system properties or environment variables for free.
I could put together a POC to see if it's viable.


Error on exit: not properly closed all its desktop references

When exiting eovim, it returns the following error:
ERR<9093>:efreet_cache lib/efreet/efreet_cache.c:396 efreet_cache_shutdown() This application has not properly closed all its desktop references!
What does it mean? Is it a problem?

eovim --version: eovim <IP_ADDRESS>-5a69a50
nvim --version | head -n1: NVIM v0.2.2-41-gee031eb52
edje_cc --version: 1.20.7

sorry for the delayed answer.
It may either be a problem of the EFL (the underlying framework) or its use by Eovim. You can consider this as an "internal" message of the EFL (unfortunately, it is quite verbose). I think there is nothing wrong with you :)
Note that it may also vary depending on the versions of EFL (I do not see the message with my installation).

Since I still cannot reproduce with "recent" EFL (at least the ones provided with Fedora 29), I'm not sure this is related to eovim. Feel free to re-open this issue if you happen to still have the problem.


Tidy up changes and tweaks to improve messaging

A mixture of formatting fixes (some of the command lines looked different to others because of whitespace) and improved language explaining why an ISO image is a bad idea.

@timsneath,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/install/install-vs-inconsistent-quality-network.md
:white_check_mark:Succeeded

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.


Assignment-4 6ITA Darsh Kalani

2 task hosted successfully
issue #231

Errata:
@Darshkalani28

Please ensure that after form is submitted, the name is shown on the page

#231


update smoke tests, include ability to fetch latest version from dev feed

/azp run java - smoke-tests

/azp run java - smoke-tests

/azp run java - smoke-tests

@danieljurek It seems like the README is failing the verification. Honestly, does this even need a readme or should there be an exemption listing in the eng/.docsettings.yml under the known_presence_issues

A readme file is helpful here (provided its instructions stay relevant to the tool) but maintaining a specific schema for it is not that interesting. I'll add an exclusion in https://github.com/Azure/azure-sdk-for-java/blob/master/eng/.docsettings.yml ... We're getting this error because the smoke tests moved from the eng folder to common


Update to bevy 0.14

The bevy-egui dependency still needs to be updated when they release a new version

bevy_egui has been updated 0.28 supports bevy 0.14.

I'll update my PR in a couple of hours, feel free to modify it if you want to merge before.

0.19 released


Support custom XAResourceProducer implementations in ResourceLoader

The ResourceLoader is hard-coded to support two types of XAResourceProducer implementations: the PoolingDataSource for a JDBC XADataSource and the PoolingConnectionFactory for a JMX XAConnectionFactory.
We have our own custom XAResourceProducer implementations and currently we need to manually register them with the transaction manager (ResourceRegistrar). This is inconvenient.
I would like to request the ResourceLoader be enhanced to support custom XAResourceProducer implementations. Maybe it can recognize a "resource.name.producerClassName" property in the properties file and if (optionally) specified use that?

Interesting. This could be done, but only if you're willing to spend the time doing it yourself as well as handling all the release work.
Please contact me privately if you feel like it.


Fixing "You cannot serialize or unserialize PDO instances" when serializing the query object

I am experiencing a pdo exception "You cannot serialize or unserialize PDO instances" when i want to serialize the query object, this should be fixed by unsetting the ->connection member.

Thank you for your contribution.
Could you send this PR to main repository then we can split it to this subtree?
https://github.com/ventoviro/windwalker

Ok.. Should have read the READ ONLY sign ;-)


STORM-3086: Add documentation for invoking static factory methods fro…

…m Flux
https://issues.apache.org/jira/browse/STORM-3086

The examples are slightly adjusted versions of some code that appears in the flux-core tests https://github.com/apache/storm/blob/master/flux/flux-core/src/test/resources/configs/config-methods-test.yaml#L40


DisplayName is null

Hi, I try read file name on webdev and displayname is null??

It's not clear if this is the issue of the library or the WebDAV server configuration.
What HTTP request are you sending? What HTTP response are you getting?
A good starting point is too use a tool like Fiddler to capture HTTP/HTTPS traffic between the application and the WebDAV server and see what kind of response the WebDAV server returns.
If the field is not present in the HTTP response of WebDAV server then it's the expected behavior of the library; otherwise you can send me the WebDAV response and I can investigate if it's a bug in the lib.
To proxy WebDAV calls through Fiddler you need to pass a WebProxy instance to WebDavClient like explained here.


Port vserver to ngshare

Port vserver to ngshare

I have finished porting vserver to ngshare. Please test and review code (leave your comments here (#31)). Instructions are in https://github.com/lxylxy123456/ngshare#vngshare . @aalmanza1998  and @Lawrence37  if you can switch to ngshare instead of vserver, I will abandon vserver before fixing #36 .


Fix Twitter user info endpoint

profile_image_url is missing from the response unless we provide parameter include_entities=true

:+1:


Raise IOError when providing an invalid path to a CA bundle or …

Use IOError whenever invalid paths are used for ssl certificates (#3926)

Codecov Report

Merging #3927 into master will increase coverage by 1.71%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #3927      +/-   ##
=========================================
+ Coverage   87.88%   89.6%   +1.71%
=========================================
  Files          15      15
  Lines        1940    1943       +3
=========================================
+ Hits         1705    1741      +36
+ Misses        235     202      -33

Impacted Files
Coverage Δ

requests/adapters.py
92.78% <100%> (+3.03%)
:white_check_mark:

requests/models.py
93.42% <0%> (+2.26%)
:white_check_mark:

requests/_internal_utils.py
100% <0%> (+6.25%)
:white_check_mark:

requests/__init__.py
93.33% <0%> (+10%)
:white_check_mark:

requests/compat.py
100% <0%> (+35.13%)
:white_check_mark:

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 552ab7a...af01a21. Read the comment docs.

Thanks for the review. In addition I also ported the definitions you provided for the verify parameter to the other methods that were getting this argument for consistency

I'm happy to help :) Just by curiosity, is it a good practice to squash the commits into one?

It depends very much on the project. For my part, I generally allow people to work the way they feel most comfortable unless the number of commits vastly outweighs the complexity of the change. Other projects may ask you to do so: it's polite to do what they want. But if no-one asks, then you're totally safe. :smile:

Ok good to know, thanks


ForwardAuth middleware not working with Keycloak

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
latest
What version of Traefik are you using?
latest
What did you do?
I deployed traefik and keycloak on kubernetes. I created a client on keycloak and I want keycloak to protect access to my application. I created ingressroute, where my application is exposed, and that ingressroute is using middleware which is doing forwardauth to keycloak address (let's name it address1):
https://mykeycloakURL/auth/realms/RELMNAME/protocol/openid-connect/auth?scope=openid&response_type=code&client_id=CLIENTID&redirect_uri=https://myprotectedapplicationURL/&prompt=consent
When I just enter this address1 to browser, proper login screen appears. But when I access my https://myprotectedapplicationURL , traefik does forwardauth toaddress1, but since login page returns status code 200 when loaded, traefik automatically navigates to https://myprotectedapplicationURL without waiting for successful authentication. How to fix this?
What did you see instead?

What is your environment & configuration?
k8s
Additional Information
No response

You cant use keycloak directly with forward auth as far as I know. You need to use something like oauth-proxy in between.

Hello @MarjanJordanovski
I think this is not related to the Helm Chart itself, I would encourage you to ask that question on our community forum.
Thank you,


add start/end date range search for /meta

In the frontend we'll be filtering by predefined ranges (last 7 days, last month, ...).
These ranges will be converted to dates and used with the api.


Update Propeller-IDE-Getting-Started.md

I'm not a fan of adding repository to sources.list and leaving them active once they have served their purpose. In this case, at thispoint in time they would enforce upgardes of the follwoing on my system:
libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 raspberrypi-bootloader
maybe I'm funny and all that but I'm not keen on it ;-)

Oh I absolutely agree and think I observed a problem with this on my own Pi. Thank you!

furthermore I'm not sure you need libftdi1 for propman, it seem sto work fine without?


Can't load from test/resources

I have this config lying in test/resources/sample.conf
sample {
user=foo
}
I have these tests in /test/.../SampleConfigFactoryTest.scala which are trying to pull the above configuration from the test/resources location but they are failing.
"happy path" should {

    "load resources/sample using default ClassLoader" in {
        val config = ConfigFactory.load("sample")
        if(config.hasPath("sample.user"))  {

        } else {
            fail("cannot find path!")
        }
    }

    "load resources/sample using default ClassLoader of AppConfigLoaderTest" in {

        val config = ConfigFactory.load(classOf[AppConfigLoaderTest].getClassLoader, "sample")
        if(config.hasPath("sample.user"))  {

        } else {
            fail("cannot find path!")
        }
    }

}
This is a Play app and the top level folders are
/app
/conf
/test/resources
"show test:resources" yields:
[info] List(/Users/xxxx/workspaces/dev/sampleapp/test/resources, /Users/xxxx/workspaces/dev/sampleapp/test/resources/sample.config)
The tests all fail with "cannot find path!".
Any help would be appreciated.
I am using:
Play 2.4.x
scalaVersion := "2.11.6"
"com.typesafe" % "config" % "1.3.0"

BTW, resources folder is under the test folder, the indentation is lost in the above.

Try -Dconfig.trace=loads to see the paths it tries to load and it may be clear. I expect you need to either add something to classpath or use a different resource name.
It's best to ask stuff like this on stackoverflow; here you get only me and I don't really know in detail what play does with classpaths for example. On stackoverflow with the playframework tag and typesafe config tag you might get a few more helpful people.

Closing this due to inactivity and assumption that it was a project configuration mistake rather than a bug.


Peek window custom size

Description of the new feature / enhancement
Make peek remember the last window size for better viewing workflows for PDFs and images etc.
Scenario when this would be used?
Especially useful for viewing certain type of PDFs that require the window to have a specific size for ideal viewing experience.
Supporting information
No response

consolidating peek windowing requests /dup https://github.com/microsoft/PowerToys/issues/29198


[Addition]: Suave Bronze Tadpole  -  some strange stuff

Hotspot b58 Addresses
1127Bxa5RuVkMnbfevCqwzLfn3kvCcavm6f9GSe78dp9TX93GQxP

Discord Handle
No response
Reason(s)
How is this even possible?
https://explorer.helium.com/txns/rn8juXpGmytS0apTD6QOweGe_UP-j5XPDqFU0KUyrSA

Long range over mountainous terrain

Invalid Witness: Witness RSSI too high

https://explorer.helium.com/txns/ZpODv-PuRiYDIDltRXGBmdXwKrLAmxRWskaFvFrl8_Q
Invalid Witness: witness_too_far

https://explorer.helium.com/txns/wiPyQJAreiZqENXMONkk63Mw13tPPRaW2Q69pdXSLXQ

I still don't understand how he is making 200 hnt monthly...


game crash

Some of our users experience game crash if overlay is enabled.
Faulting application name: TERA.exe, version: <IP_ADDRESS>, time stamp: 0x59642b52
Faulting module name: dx9_overlay.dll, version: <IP_ADDRESS>, time stamp: 0x593d24ee
Exception code: 0xc0000005
Fault offset: 0x00022995
Faulting process id: 0xff4
Faulting application start time: 0x01d3034328773cd4
Faulting application path: D:\GameforgeLive\Games\GBR_eng\TERA\Client\Binaries\TERA.exe
Faulting module path: C:\Users\DAMNBOI\Documents\shinrameter\ShinraMeterV2.03\dx9_overlay.dll

(Using unicode one from https://github.com/shadowlif/DX9-Overlay-API/tree/unicode/bin )

Can you provide more data (maybe an crash dump)?
Atm the Fault offset is inside an function, that raises an exception.

That's not on my system, and even this log was hard to explain how to get for that user.

got some logs from one of our users https://www.mediafire.com/?3922f3hzm29a17e

Checked one dump.
The crash happens here https://github.com/agrippa1994/DX9-Overlay-API/blob/a8251c181d14ab0e08dd654d443981863897c1cd/src/dx9_overlay/Game/Game.cpp#L34
This happens because d3d9.dll reserves just 0x2F000 bytes of memory.
Why this happens? The process loaded two d3d9 modules.
One is in the game folder (where the exe is). The other one is in the Windows System32 folder.
I looks like, that the d3d9 module inside the game folder is (maybe) not valid. Try to rename it (like d3d9_backup.dll) so just the real one get loaded.

Removing dll works like a charm, added this info to FAQ, thanks.

Probably that dll is from https://sfx.thelazy.net/downloads/ project
Is there any way of interoperability with that thing?

It's "SweetFX 1.5 | by CeeJay.dk - Version 1.5.1"?
I can try it in another branch, but I don't know atm how SweetFX is internally designed. Maybe it works with new Patterns, maybe not.


potential nosql injection with recommended command execution elixir syntax "~w(SET mykey foo)"

Elixir syntax for creating lists of words could become potential injection point if used in production with no user input escaping.
Example:
Redix library user follows how-to examples and using syntax like:
~w(SET mykey foo)
At some point he's using string interpolation like:
~w(SET mykey #{foo_var})
where foo_var is user input.
Given there is no proper escaping of user input, attacker could successfully execute the following:
assuming foo_var = "1 DEL mykey"
~w(SET mykey #{foo_var})
becomes:
["SET", "mykey", "1", "DEL", "mykey"]
Since Redis usually treated as "safe to NoSQL injections" by engineers (http://redis.io/topics/security), that beautiful syntax could have unexpected outcome.
So that's not a security hole in the library itself. But I'd suggest to edit how-to section accordingly.

@alecnmk hey there, thanks for the issue :D I briefly looked into this and:
iex> Redix.command!(conn, ["SET", "mykey", "1", "DEL", "mykey"])
** (Redix.Error) ERR syntax error

As I expected, it seems that you cannot execute multiple commands in a single "command" (a list of binaries) that you pass to Redix.command(!)/2. If you were using pipeline(!)/2 instead, you would have a list of "commands" (that is, a list of lists of binaries) like [~w(SET mykey 1), ~w(DEL mykey)] and it would still be impossible to inject into each of the commands. Am I missing something? 😕

@whatyouhide, hey!
Could you please run this example:
    IO.inspect Redix.command!(conn, ~w(SET A 10))
    IO.inspect Redix.command!(conn, ~w(SET B 20))
    IO.inspect Redix.command!(conn, ~w(DEL B DEL A))
    IO.inspect Redix.command!(conn, ~w(GET A))
    IO.inspect Redix.command!(conn, ~w(GET B))

I'm getting this result:
"OK"
"OK"
2
nil
nil

just to be clear, I'm not stating that library has vulnerability.. that's only about recommended way of executing commands in the project readme:
Redix.command(conn, ~w(SET mykey foo))
#=> {:ok, "OK"}
Redix.command(conn, ~w(GET mykey))
#=> {:ok, "foo"}

@alecnmk yeah definitely, I get that the problem would be in userland, not the library :). And yeah actually running your DEL B DEL A example appears to work, I'm not sure why. Do you have other examples of multiple commands working as a single one? For example:
iex> Redix.command!(conn, ~w(SET foo 1 GET foo))
** (Redix.Error) ERR syntax error
iex> Redix.command!(conn, ~w(SET x 1 SET y 2))
** (Redix.Error) ERR syntax error

which makes sense to me 😕 In any case I'm dragging the discussion because I want to know what the hell is going on with Redis but yes we should update the README to mention this clearly. Do you feel like submitting a PR or should I take care of it? :)

@whatyouhide I didn't get into deep investigation. But my first guess is that Redis allows to pass multiple keys to DEL command:
DEL key1 key2 key3
So, second DEL is interpreted as non-existing key and that doesn't raise error.
I'll think of other possible outcomes of that issue and make PR later tonight or tomorrow during the day.

Ah good point, yes it must be because it interprets DEL as another key to delete, so it's still safe. Interesting, for sure :) Anyways, awesome, thanks in advance for the PR. 👍

Ping @alecnmk?

hey @whatyouhide, sorry, when I stuck on that issue I was in the middle of release and had no time during next few days to do deeper research and update readme. I'll add a note about DEL command tomorrow

No worries @alecnmk, just wanted to check and see if I needed to take care of this. Take your time!

@alecnmk ping again? :)

Gonna close this for inactivity. I will look into maybe adding a warning to the README or something similar. Thanks for the report @alecnmk! 💟


QueryRoutePredicateFactory not work when WeightRoutePredicateFactory is configured

spring:
  cloud:
    gateway:
      routes:
       - id: test-server-1
         predicates:
         - Path=/test/**
         - Weight=test-server,50
         - Query=foo
         uri: http://<IP_ADDRESS>:9089
       - id: test-server-2
         predicates:
         - Path=/test/**
         - Weight=test-server,50
         uri: http://<IP_ADDRESS>:9088

config  like this,is it means that when request /test/xxx?foo=111 should be routd to test-server-1? but it don't work

They are evaluated in order. Weigh needs to be last, otherwise if the weight didn't match it would never even test the query parameter.

Put it at the end of the predicate list

@spencergibb
you mean like this:
predicates:
- Path=/test/**
- Query=foo
- Weight=test-server,50
but it don't work too

configuration like this:
spring:
cloud:
gateway:
routes:
- id: test-server-1
predicates:
- Query=foo
- Path=/test/**
- Weight=test-server,50
uri: http://<IP_ADDRESS>:9089
- id: test-server-2
predicates:
- Path=/test/**
- Weight=test-server,50
uri: http://<IP_ADDRESS>:9088
it means, the test-server-1 only response the request contained a foo query parameter.It can't guarantee that all the  requests contained a foo query parameter only be routed to test-server-1


Color contrast between codeblock and background negligible

The color contrast between the background and the code block is almost negligible. I believe the original intent of having different colors is that users can differentiate between the code example and the normal text.

/cc @ahmadabdolsaheb

On a related note, there used to be more space between the lines or code sections, so when code sections were stacked on top of each other, there was still some vertical space between them to avoid looking like below:

@raisedadead can I get this one to fix?

Yes, please but please take a moment to go thru out guidelines for contributing


Update Test.ps1

Summary of the pull request
This pull request addresses [briefly describe the issue or enhancement]. It includes improvements to the PowerShell script for running Dev Home tests.
References and relevant issues
[Link to the related issue or mention any relevant context]
Detailed description of the pull request / Additional comments
[Provide a more detailed description of the changes made in the pull request. Highlight any major modifications or improvements. If there are specific decisions or considerations made during the update, mention them here.]
Validation steps performed

[x] Tested the script on [specify the environments or scenarios tested].
[x] Ensured that WinAppDriver installation works as expected.
[x] Verified the functionality of Dev Home tests after the script update.
[x] [Any other validation steps performed]

PR checklist

[x] Closes #[issue number]
[x] Tests added/passed
[x] Documentation updated

`param (
[string]$Platform = "x64",
[string]$Configuration = "debug",
[switch]$IsAzurePipelineBuild = $false,
[switch]$Help = $false
)
$StartTime = Get-Date
if ($Help) {
Write-Host @"
Copyright (c) Microsoft Corporation and Contributors.
Licensed under the MIT License.
Syntax:
Test.cmd [options]
Description:
Runs Dev Home tests.
Options:
-Platform
Only build the selected platform(s)
Example: -Platform x64
Example: -Platform "x86,x64,arm64"
-Configuration
Only build the selected configuration(s)
Example: -Configuration release
Example: -Configuration "debug,release"
-Help
Display this usage message.
"@
Exit
}
$env:Build_SourcesDirectory = (Split-Path $MyInvocation.MyCommand.Path)
$env:Build_Platform = $Platform.ToLower()
$env:Build_Configuration = $Configuration.ToLower()
$vstestPath = &"${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -latest -prerelease -products * -find '**\TestPlatform\vstest.console.exe'
$ErrorActionPreference = "Stop"
$isInstalled = Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall* | Where-Object { $_.DisplayName -like "Windows Application Driver" }
if (-not $IsAzurePipelineBuild) {
if ($isInstalled) {
Write-Host "WinAppDriver is already installed on this computer."
} else {
Write-Host "WinAppDriver will be installed in the background."
$url = "https://github.com/microsoft/WinAppDriver/releases/download/v1.2.99/WindowsApplicationDriver-1.2.99-win-x64.exe"
$outpath = Join-Path $env:Build_SourcesDirectory "temp"
    if (-not (Test-Path -Path $outpath)) {
        New-Item -ItemType Directory -Path $outpath | Out-Null
    }

    Invoke-WebRequest -Uri $url -OutFile (Join-Path $outpath "WinAppDriverx64.exe")

    Start-Process -Wait -FilePath (Join-Path $env:Build_SourcesDirectory "temp\WinAppDriverx64.exe") -ArgumentList "/S" -PassThru
}

Start-Process -FilePath "C:\Program Files\Windows Application Driver\WinAppDriver.exe"

}
function ShutDownTests {
if (-not $IsAzurePipelineBuild) {
Stop-Process -Name "WinAppDriver" -ErrorAction SilentlyContinue
}
$TotalTime = (Get-Date) - $StartTime
$TotalMinutes = [math]::Floor($TotalTime.TotalMinutes)
$TotalSeconds = [math]::Ceiling($TotalTime.TotalSeconds)

Write-Host @"
Total Running Time:
$TotalMinutes minutes and $TotalSeconds seconds

"@ -ForegroundColor Cyan
}
if (-not (Test-Path -Path "AppxPackages")) {
Write-Host "Nothing to test. Ensure you have built via the command line before running tests. Exiting." -ForegroundColor Yellow
Exit 1
}
try {
foreach ($platform in $env:Build_Platform.Split(",")) {
foreach ($configuration in $env:Build_Configuration.Split(",")) {
# TODO: UI tests are currently disabled in the pipeline until signing is solved
if (-not $IsAzurePipelineBuild) {
$DevHomePackage = Get-AppPackage "Microsoft.DevHome" -ErrorAction SilentlyContinue
if ($DevHomePackage) {
Write-Host "Uninstalling old Dev Home"
Remove-AppPackage -Package $DevHomePackage.PackageFullName
}
Write-Host "Installing Dev Home"
Add-AppPackage (Join-Path "AppxPackages" "$configuration\DevHome-$platform.msix")
}
        $vstestArgs = @(
            "/Platform:$platform",
            "/Logger:trx;LogFileName=DevHome.Test-$platform-$configuration.trx",
            "test\bin\$platform\$configuration\net8.0-windows10.0.22000.0\DevHome.Test.dll"
        )
        $winAppTestArgs = @(
            "/Platform:$platform",
            "/Logger:trx;LogFileName=DevHome.UITest-$platform-$configuration.trx",
            "uitest\bin\$platform\$configuration\net8.0-windows10.0.22000.0\DevHome.UITest.dll"
        )

        & $vstestPath $vstestArgs
        # TODO: UI tests are currently disabled in the pipeline until signing is solved
        if (-not $IsAzurePipelineBuild) {
            & $vstestPath $winAppTestArgs
        }

        foreach ($toolPath in (Get-ChildItem "tools")) {
            $tool = $toolPath.Name
            $vstestArgs = @(
                "/Platform:$platform",
                "/Logger:trx;LogFileName=$tool.Test-$platform-$configuration.trx",
                "tools\$tool\*UnitTest\bin\$platform\$configuration\net8.0-windows10.0.22000.0\*.UnitTest.dll"
            )

            $winAppTestArgs = @(
                "/Platform:$platform",
                "/Logger:trx;LogFileName=$tool.UITest-$platform-$configuration.trx",
                "tools\$tool\*UITest\bin\$platform\$configuration\net8.0-windows10.0.22000.0\*.UITest.dll"
            )

            & $vstestPath $vstestArgs
            # TODO: UI tests are currently disabled in the pipeline until signing is solved
            if (-not $IsAzurePipelineBuild) {
                & $vstestPath $winAppTestArgs
            }
        }
    }
}

} catch {
$formatString = "n{0}nn{1}n`n"
$fields = $, $.ScriptStackTrace
Write-Host ($formatString -f $fields) -ForegroundColor Red
ShutDownTests
Exit 1
}
ShutDownTests
`

@SleepTheGod please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{Taylor Christion Newsome}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

I agree


Translate services-networking/network-policies.md in Korean.

This is a Feature Request
What would you like to be added
Translate services-networking/network-policies.md in Korean.
Why is this needed
The following files are not translated into Korean.

[ ] /en/docs/concepts/services-networking/network-policies.md

Comments
Page to update: https://kubernetes.io/docs/concepts/services-networking/network-policies/
I am translating this document.
The translated document will be submitted to dev-1.17-ko.2 branch.
/language ko

/assign


Create the base folder structure

Description
Create the spec and TCK folder structure for the project

[ ] Application user
[X] Specification implementer

...I need to be able to:
Provide the base folder structure
...which enables me to:
Start to work on the spec

implemented by https://github.com/eclipse/microprofile-telemetry/pull/9


Log exceptions

In RuleAdapter.mapFactsToProperties exceptions are swallowed. They should be logged to get a better view on the initial problem.

Branch off the develop branch and issue a PR. Agreed that logging could be more robust.

@Clayton7510 can you add me as collaborator pls? I'm not able to create branches at the moment.

Thanks for the PR! I'll complete the review after work today.
You don't need to create a branch. You can just fork, make updates and then issue a PR. Actually, that's the route I am going to follow going forward, too.
Prior to release, I will, however, update the collaborators in the Maven POM to include you as a collaborator so that credit is attributed to your contribution.


Updated conda env for windows development

We could probably have some common environment for both platforms and small additions that exist/required on specific platforms (e.g. folly currently exists only on Linux in conda-forge).

I suggest that we murge this PR while we think on the best way to synchronize multi-platform conda env. This is the last PR that is holding windows build from running CI.

I suggest that we merge this PR while we think on the best way to synchronize multi-platform conda env. This is the last PR that is holding windows build from running CI.

I think we should merge this ASAP, as this is a separate file and do not interfere with Linux builds.


Autogenerate all acb_* .pxd files

Follows gh-215

I have separated the flintlib .pxd files into two subdirectories:

flint.flintlib.types contains all structs and typedefs and is all hand-written code.
flint.flintlib.functions contains all the functions and is generated by scraping the docs.

This means that you do e.g.:
from flint.flintlib.types cimport fmpz_t
from flint.flintlib.function cimport fmpz_is_one

We also need to add macros and some undocumented functions into the hand-written code. Possibly it would be better to change the doc-scraping script so that it has a hard-coded list of macros to recognise and declare as functions. The undocumented functions should be fixed upstream.
Some of the .pxd files in functions still need to be rearranged: remove the struct definitions and place in a new .pxd in the types directory. Then they can be auto-generated as well.
About half of modules used in python-flint are now auto-generated by a single script:
$ bin/all_rst_to_pxd.sh ../flint/doc/source/
Processing acb_calc
Processing acb_dft
Processing acb_dirichlet
Processing acb_elliptic
Processing acb_hypgeom
Processing acb_mat
Processing acb_modular
Processing acb_poly
Processing acb
Processing acb_theta
Processing arb_fmpz_poly
Processing arb_hypgeom
Processing arb_mat
Processing arb_poly
Processing arb
Processing arf
Processing arith
Processing bernoulli
Processing dirichlet
Processing fmpz_factor
Processing fmpz_lll
Processing fmpz_mat
Processing fmpz_poly_factor
Processing fmpz_poly
Processing fmpz
Processing fmpz_vec
Processing mag
Processing partitions
Processing ulong_extras

Status is:
https://github.com/flintlib/python-flint/blob/627bb8cff64bf12c0f3b4fc0c12c0eb6a931c330/bin/all_rst_to_pxd.sh#L13-L83

The diff here is now large because all of the flintlib.pxd files have been moved. I'm going to merge this shortly to get it in before merge conflicts arise.

Okay, I've made it so that all the .pxd files in flintlib.functions are generated automatically. That applies to all of the FLINT modules that are actually used in python-flint. I made a full list of all FLINT modules here so you can see which are being used and easily uncomment the others when needed:
https://github.com/flintlib/python-flint/blob/a51dc42da20b7c498a4774892cae434b791bee42/bin/all_rst_to_pxd.sh#L13-L146


Install icon

I wanted to send a newsboat-branded notification and found out the logo isn't installed in any standard location to be used.
This puts it in a standard location so any program that wants to reference newsboat can find it.

It looks like all paths are prefixed with $(DESTDIR)/, so please do that.

Also, I didn't even realize there is central location for icons (though in hindsight, it doesn't surprise me at all; it's only logical to put all icons in a single place). Thank you for the PR and edification :)

It looks like all paths are prefixed with $(DESTDIR)/, so please do that.

Whoops, missed that. I saw that datadir included prefix and completely neglected destdir.

This turned into a death by a thousand papercuts as I changed the path and forgot to update the uninstall location, and in combination with your comment and a few others.
So I did a force push to avoid having 5 commits for a 2 line change :)

Coverage decreased (-0.01%) to 57.05% when pulling 7c64013e3c9d24be3706c1bf4258270ff2dbb98e on tsipinakis:install-icon into dc1d68032c8dc656f4271d23e50707cab1023b5d on newsboat:master.

CI doesn't test make install, and this PR doesn't change any compiled sources, so I'll merge it without waiting for CI to finish. Thank you once again, @tsipinakis  :+1:


Oc 139 adjust manual for vagrant procedure

Updated documentation with Vagrant procedure

 You should sign our Contributor License Agreement in order to get your pull request merged.

All is well.

All is well.


ConcurrentTimedRotatingFileHandler deprecated delay warning

When the ConcurrentTimedRotatingFileHandler is used without specifying the delay parameter, the following warning is shown:

DeprecationWarning: concurrent_log_handler parameter delay is now ignored and implied as True, please remove from your config.

This seems to be due to the default value of False, while it is None  for ConcurrentRotatingFileHandler.
I'm guessing either the default value should change, or this check should be (None, False):
if delay not in (None, True):
    warnings.warn(
        "concurrent_log_handler parameter `delay` is now ignored and implied as True, "
        "please remove from your config.",
        DeprecationWarning,
        stacklevel=3,
    )

Fixed in master branch; I may wait a little bit before putting out a new release. Thanks for the report.


Add Publisher Verification for cypress-io

Cypress is amazing and vouched for by developers around the world! What are the odds of getting this organization verified by GitHub? Is there anything we can help with?
https://docs.github.com/en/developers/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization

Totally agree with @atsai1220! Would love to see cypress be officially verified by GitHub as well. Best E2E testing framework I've experienced 🥳

Is this what you were looking for?

Closing on the assumption that the request has been satisfied.


Fixed an issue where tiledefinition persistence was failing for more than 1 tile in the code

Fixed an issue where tiledefinition persistence was failing for more than 1 tile in the code

For clarity sake, this issue comes about when using non-Mongo/JSON based persistence structures, such as Postgres.  Based on initial tests, I didn't see any foreseeable issues.  Merging.


⚠ Bofrost.si has degraded performance

In e25818f, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 1940 ms

Resolved: Bofrost.si performance has improved in c728ef4 after 6 minutes.


Spread Chart Pandas Attribute Error

Versions

Python: 3.10.5

Pandas: 2.0.2

Plotly: 5.14.1

Cufflinks: 0.17.3

Issue

When running the following:

df[['A','B']].iplot(kind='spread')

I get the following error:

File ~\datasci\lib\site-packages\cufflinks\plotlytools.py:849, in _iplot.<locals>.<lambda>(x)
    847 if kind=='spread':
    848 	trace=self.apply(lambda x:x[0]-x[1],axis=1)
--> 849 	positive=trace.apply(lambda x:x if x>=0 else pd.np.nan)
    850 	negative=trace.apply(lambda x:x if x<0 else pd.np.nan)
    851 	trace=pd.DataFrame({'positive':positive,'negative':negative})

AttributeError: module 'pandas' has no attribute 'np'

Pandas deprecated pandas.np in 1.0.0 and removed in 2.0.0

I just downloaded the plotlytools.py from the Cufflinks GitHub site:
https://github.com/santosjorge/cufflinks/tree/master/cufflinks
Copy it into my pkg directory.
If you do not know where your cufflinks is installed, use
pip install -U cufflinks to find out.

File ~\datasci\lib\site-packages\cufflinks\plotlytools.py:849, in _iplot.<locals>.<lambda>(x)
    847 if kind=='spread':
    848 	trace=self.apply(lambda x:x[0]-x[1],axis=1)
--> 849 	positive=trace.apply(lambda x:x if x>=0 else pd.np.nan)
    850 	negative=trace.apply(lambda x:x if x<0 else pd.np.nan)
    851 	trace=pd.DataFrame({'positive':positive,'negative':negative})

AttributeError: module 'pandas' has no attribute 'np'

faced the same thing today, took a look at the code and thought "ta hell?".
this is actually fixed as of today, but the fix hasn't been pushed to pipy so the version u get get from pip install is broken.
I would suggest using pip install cufflinks1

Took me a while to find this! Very helpful thank you!

File ~\datasci\lib\site-packages\cufflinks\plotlytools.py:849, in _iplot.<locals>.<lambda>(x)
    847 if kind=='spread':
    848 	trace=self.apply(lambda x:x[0]-x[1],axis=1)
--> 849 	positive=trace.apply(lambda x:x if x>=0 else pd.np.nan)
    850 	negative=trace.apply(lambda x:x if x<0 else pd.np.nan)
    851 	trace=pd.DataFrame({'positive':positive,'negative':negative})

AttributeError: module 'pandas' has no attribute 'np'

faced the same thing today, took a look at the code and thought "ta hell?".
this is actually fixed as of today, but the fix hasn't been pushed to pipy so the version u get get from pip install is broken.
 Should it saw pd.nan or np.nan here? im a bit of a noob in this and following a course and it fails here.

I edited mine to get it to work, it looks like this:


Installation via Chocolatey is broken

I've tried installing the terminal via cmd using Chocolatey but I get an error:
PS C:\WINDOWS\system32> choco install microsoft-windows-terminal
Chocolatey v0.10.11
Installing the following packages:
microsoft-windows-terminal
By installing you accept licenses for the packages.
microsoft-windows-terminal not installed. The package was not found with the source(s) listed.
 Source(s): 'https://msazure.pkgs.visualstudio.com/_packaging/Bootstrap/nuget/v2/;https://vstfdt/tfs/CEDialtone/_packaging/Bootstrap/nuget/v2'
 NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify `--pre`,
 the package may not be found.
Please see https://chocolatey.org/docs/troubleshooting for more
 assistance.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - microsoft-windows-terminal - microsoft-windows-terminal not installed. The package was not found with the source(s) listed.
 Source(s): 'https://msazure.pkgs.visualstudio.com/_packaging/Bootstrap/nuget/v2/;https://vstfdt/tfs/CEDialtone/_packaging/Bootstrap/nuget/v2'
 NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify `--pre`,
 the package may not be found.
Please see https://chocolatey.org/docs/troubleshooting for more
 assistance.

It looks like your list of chcolatey sources is corrupted.

What is the relevant source? I think you could be a little more helpful

Sorry, trying to process these quickly. You know how triage goes.
Your choco error included the following:
Source(s): 'https://msazure.pkgs.visualstudio.com/_packaging/Bootstrap/nuget/v2/;https://vstfdt/tfs/CEDialtone/_packaging/Bootstrap/nuget/v2'

The default chocolatey source looks like (suggested by me running choco sources)
C:\Users\Dustin>choco sources
Chocolatey v0.10.15

chocolatey - https://chocolatey.org/api/v2/ | Priority 0|Bypass Proxy - False|Self-Service - False|Admin Only - False.

I'm not sure whether it lists only non-default sources in the error, but if it lists all sources it looks like your default's been removed. I'm not sure why/how that'd happen, unfortunately.

try enabling your chocolatey source choco source enable -n chocolatey


add feature with JindoRuntime dataloader

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #764 (1a5b5a4) into master (76e4509) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #764      +/-   ##
==========================================
- Coverage   12.65%   12.55%   -0.10%
==========================================
  Files          93       93
  Lines        4236     4269      +33
==========================================
  Hits          536      536
- Misses       3640     3673      +33
  Partials       60       60

Impacted Files
Coverage Δ

pkg/ddc/jindo/cache.go
0.00% <ø> (ø)

pkg/ddc/jindo/runtime_info.go
0.00% <ø> (ø)

pkg/ddc/jindo/shutdown.go
0.00% <0.00%> (ø)

pkg/ddc/jindo/transform.go
0.00% <0.00%> (ø)

pkg/ddc/jindo/utils.go
0.00% <0.00%> (ø)

pkg/utils/docker/image.go
14.54% <0.00%> (-1.79%)
:arrow_down:

pkg/ddc/alluxio/master.go
0.00% <0.00%> (ø)

pkg/ddc/alluxio/transform.go
0.00% <0.00%> (ø)

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 76e4509...1a5b5a4. Read the comment docs.


add proposal of static pod upgrade model

Signed-off-by: hxcGit<EMAIL_ADDRESS>
What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

What this PR does / why we need it:
Proposal for static pod upgrade model
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm
/approve


Add capability to acs-engine to provision and destroy agent pools

Is this a request for help?:
No
Is this an ISSUE or FEATURE REQUEST? (choose one):
FEATURE REQUEST
What version of acs-engine?:
v0.12.5

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.8+ in my case
Request:
As an automation engineer, I want to automatically provision and destroy Kubernetes agent pools using native acs-engine commands.
Use cases:
1 - Add performance testing to an automated CI pipeline....
Several development teams share a k8s cluster for general build/test/deploy activities.  A team wants to periodically load test their application without interferring with other teams' work.
Desire:  Add a step to the CI pipeline where development teams can deploy an isolated performance testing environment, run tests, then destroy the environment to save compute expenses.
Ask:  Add capability to acs-engine to provision a new (temporary) agent pool.  Add capability to acs-engine to remove an agent pool.
2 - Underlying VM sizing changes.....
I want to provision a new agent pool with the latest, greatest or most deeply discounted VMs, move my workload to the new agent pools/VMs, then destroy to old agent pool.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Is there any update on this? Planned?
I would really use such a feature in my production cluster.


TechJam Instana section 2-1 typo and missing text

Under section Instana 2-1, of the lab documentation a typo on the first line, says "backand" should read backend.
Missing text is at the end of the first bullet point, text reads "Of course, on-premise could be deployed into a public cloud, but is not a"
end abruptly, no doubt some text is missing at the end of that sentence

Thanks, fixed.


[otp_ctrl] Remove CSR test exclusions

We need to revert commit #12969 once alias registers are supported in chip-level sims.

The exclusions have been removed in https://github.com/lowRISC/opentitan/pull/13947.


Fix Percona logrotate script

Fix Percona logrotate script to properly rotate logs.

Can your reference in the commit where this change is coming from?

This PR failed due to a bad state of our apt mirror. Once you make the commit change it should go through testing again.

retest

retest


conditions The task node adds a background color to distinguish succe…

Codecov Report

Merging #2712 into dev-1.3.0 will increase coverage by 0.70%.
The diff coverage is 1.23%.

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


[3258] Missing unary operator with Template implicit operator

Fixes #3258

The same test case, if turned into integers, results the next code in the following Javascript output. The negative result is kept nevertheless (as the bitwise or does nothing to already integer numbers).
int j = 1;
O x = -j;
O y = -(j);
O z = (-(j));

Outputs this:
var j = 1;
var x = (-j) | 0;
var y = (-(j)) | 0;
var z = (((-(j)) | 0));

This probably relates to keeping an integer an integer under bridge by this stackoverflow discussion.


Add auto merge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/dmba-feedstock#3.


Chartist 0.9, Redux

Let's try this again.
TODO

[x] Verify this is working with a production app
[ ] Review Chartist change logs to ensure we didn't miss any edge cases
[ ] ???

@tylergaw I'm fairly certain this works, but I only have a single app to test this with. Would you have some time over the coming week to give this branch a try with a sample app? Lastly, I don't believe any action is required on our part with the upgraded version of Chartist (i.e. no public APIs seem to have changed). Is this also true to the best of your knowledge?


State and block execution

Codecov Report

:exclamation: No coverage uploaded for pull request base (tzdybal/aggregation@9b41822). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##             tzdybal/aggregation      #58   +/-   ##
======================================================
  Coverage                       ?   54.14%
======================================================
  Files                          ?       15
  Lines                          ?      977
  Branches                       ?        0
======================================================
  Hits                           ?      529
  Misses                         ?      383
  Partials                       ?       65

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 9b41822...f31dce6. Read the comment docs.

It's definitely not 100% done, but I'm closing PR as is. More changes and tests will be implemented with #82.


JsonStrategy should not set content-transfer-encoding response header

As of zendframework/zendframework#3483, JsonStrategy adds the Content-Transfer-Encoding header when using UTF-16 or UTF-32. I believe doing so is incorrect, as Content-Transfer-Encoding is a MIME header, not an HTTP header.
https://tools.ietf.org/html/rfc7231#appendix-A.5:

HTTP does not use the Content-Transfer-Encoding field of MIME.
Proxies and gateways from MIME-compliant protocols to HTTP need to
remove any Content-Transfer-Encoding prior to delivering the response
message to an HTTP client.

Apparently the confusion originated with a comment on that pull request, which is probably due to a misunderstanding of the poorly described "encoding considerations" of https://tools.ietf.org/html/rfc4627#section-6. The confusing reference to content-transfer-encoding was removed in the RFC that replaced it.
See issue #61, which was also introduced by zendframework/zendframework#3483.

This repository has been closed and moved to laminas/laminas-view; a new issue has been opened at https://github.com/laminas/laminas-view/issues/25.


Add push/post/fetch/pull methods

Signed-off-by: Eric Windisch<EMAIL_ADDRESS>

Coverage remained the same at 10.891% when pulling 481d08e1f8a3fa246344ef3267bc6e8db282e7fc on ewindisch:registry into 3ac09228bf49687c4fbb03e42bb16196f68dd0e2 on iopipe:master.

@ewindisch what would you like to do with this PR?


feat: make default credentials for auth customizable

The current implementation defaults to username: admin and password: zwave when enabling auth. However, it can also be beneficial to make this customizable so that it can avoid some additional steps in updating these values.This is completely backwards compatible as well.
@robertsLando I didn't see any contributing guidelines, but if there's anything missing, please let me know.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 21.084%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
3924

Relevant Lines:
19787

💛  - Coveralls


keybindings change when exiting zsh (ssh session) via ctrl-d, but not via "exit"

When I log on to a remote machine via ssh (with the same .oh-my-zsh settings) I can use exit and the keybinding for ALT-LEFT stay ^[^[[D and my keybind to backward-word still works as before.
When I exit the remote session via ctrl-d, the keybinding changes to ^[^[OD and backward-word doesn't work anymore.
I use the newest git version on both computers and the same .zshrc.
zsh is the same version on both computers: zsh 5.2 (x86_64-suse-linux-gnu), on OpenSuSE Tumbleweed.
Any idea what could be the reason?

What's the output of infocmp on both systems? Do they use the same OMZ version?
Finally, could you try this PR #5113 to see if it solves the problem?

Thank you so much for the hint with infocmp! I'm so much intimidated by this terminfo issues.... I don't understand why this is so hard and so complicated and so hard to agree on...

I installed urxvt from source some weeks ago, as some bugfix came along. This overwrote the file:
/usr/share/terminfo/r/rxvt-unicode-256color
When I force reinstall the terminfo-base, everything is fine again....
So, this is a terminfo <-> urxvt issue, not related to zsh. Sorry for bothering you!
Why this only happens with ctrl-d and not with exit also puzzles me :-)
But I'm really happy now! Thanks again!

That's probably that CTRL+D outputs that key binding which messes up the terminal in some way. The exit command doesn't output key bindings, it just exits.
Glad you found your problem!

@mcornella Sorry to just randomly pop in here. I'm rather desperate… I'm having the same issue, CTRL+D is breaking a keybinding of mine, while exit does not. I've also compared the infocmp output and it differs, but I don't quite know how to proceed know, as I don't have any other terminfo-related problems like @michaeltraxler did. Is there any way to find out what exactly CTRL+D is emitting that is causing this problem?

Hello everyone, I once found a way to fix the affect Ctrl-D:
echo -n -e '\e[?1l\e>' # $(tput rmkx)

I have forgotten what it means, though it does works on my "bash of Git for Windows" and "bash of WSL 1".


Setting Sec-WebSocket-Protocol header on response to ws request fails

The standard (and Cloudflare) require that if Sec-WebSocket-Protocol request header is sent in a websocket connection request, the server must acknowledge it by setting a response header with the same value.
If you do this in miniflare, however, the response fails:
  // While Sec-WebSocket-Protocol is just being used as a mechanism for
  // sending `auth` since custom headers are not supported by the browser
  // WebSocket API, the Sec-WebSocket-Protocol semantics must be followed.
  // Send a Sec-WebSocket-Protocol response header with a value
  // matching the Sec-WebSocket-Protocol request header, to indicate
  // support for the protocol, otherwise the client will close the connection.
  //
  // THIS MAKES MINIFLARE SAD
  responseHeaders.set("Sec-WebSocket-Protocol", encodedAuth);

  const response = new Response(body, {
    status,
    statusText,
    webSocket,
    headers: responseHeaders,
  });
  return response;

2.3.0
On Fri, Mar 4, 2022 at 10:10 AM MrBBot @.***> wrote:

Hey! 👋 Thanks for raising this and apologies for the delayed response. I
might be misunderstanding this, but I would've thought this code that copys
headers from the Response to the WebSocket response added in 2.1.0 would
solve this:
https://github.com/cloudflare/miniflare/blob/b887877810a745f2a458d20da0a3dbd9f8a58cf4/packages/http-server/src/index.ts#L353-L363
Which version of Miniflare are you using?
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/miniflare/issues/179#issuecomment-1059481558,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATUBGDAKCUZU2IC7ZJEWDU6JU25ANCNFSM5OWVZZIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

I realize this isn't a reduced test case and I apologize. It's possible we are doing something wrong.
What we found was that in order for a web socket connection to succeed in CF's environment, if the request included the header Sec-WebSocket-Protocol: foo then we needed to manually add the response header Sec-WebSocket-Protocol: foo as well.
But that if we added that response header to Miniflare then ... something bad happened. I can't remember what the bad thing was, maybe an error, or maybe the connection just failed in some way.
It actually wasn't me who found this on our team. I'll poke the person and see if he can remember what the failure mode was.

Miniflare appears to automatically set the Sec-WebSocket-Protocol response header to match the Sec-WebSocket-Protocol request header (while CF Worker does not).  This test appears to assert this behavior https://github.com/cloudflare/miniflare/blob/92d98c9ac8636853dfb266f3ac5013fd3858d52b/packages/web-sockets/test/fetch.spec.ts#L86
When we set the Sec-WebSocket-Protocol response header on miniflare, we end up with two headers like:
Sec-WebSocket-Protocol: foo
sec-websocket-protocol: foo

The browser does not like receiving these duplicate headers and fails the connection upgrade.
Chrome won't show the response headers with this type of failure, but you can see them in Firefox:

Thanks @mrbbot.  Thanks for the suggested workaround, that is exactly what we are doing for now.


Automated Greeting Workflow

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository.  The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."
Please assign this issue to me.

@sanmarg The issue has been assigned to you, please start working on it.

I want to work in this issue. Please assign me this task.


Rendering markdown from variable results in escaped HTML

I want to pass markdown to a WebC component via an attribute. Here’s how I’m trying to do it:

<my-component text='This is text with [a link](/some-path) and **strong text**.'></my-component>

  <x webc:nokeep @html="`<y webc:type='11ty' 11ty:type='md'>${text}</y>`"></x>

The resulting HTML looks like this:

  <p>This is text with <a href="/some-path">a link</a> and <strong>strong text</strong>.</p>

I expected to get this:

This is text with a link and strong text.

So I have two questions:

Is escaped HTML the expected output of my sample code above?
Is there a better way to render Markdown that is passed to a WebC component in an attribute?

Leaving a note here for my future self: I spent an embarrassingly long amount of time today attempting to add functionality to make webc parse @html with whatever webc:type is set, so that this would work as expected:

  <x webc:nokeep webc:type='11ty' 11ty:type='md' @html='text'></x>

i.e. Use 11ty’s Markdown parser to process the value passed to @html.
This feels like the right solution, but I have not been able to make that happen.


fix rtl languages paragraph sentences issue

In a RTL language, the paragraphs lengths are reversed. In a normal paragraph the shortest sentence is the last sentence but this was the opposite in here.
Before:

After:

Hi, I was looking your code, but I think you reverse all text including when you have not RTL language.
Could you confirm me that code works on RTL language and none RTL languages ?

Please check the new implementation of rtl language support, I am not really sure if it's ok, I based in this PR to make changes.  I don't merge this because not all text was affected and break ltr languages.