Errors for element concentrations

Squid3 (as well as Squid2.5) does not report errors on U, Th, Pb_rad and any custom element (e.g. Hf,) concentrations for UPb routine analysis. Indeed, natural inhomogeneities of RMs are much greater than an errors measured in unknowns, yet I need to indicate its in my report table!

Hello @NickRodionov and welcome!
I think the main reason Ken Ludwig omitted measurement uncertainties from elemental concentrations in SQUID 2.50 (and Squid3) is as you suggest, and that he did not want users to think that the high precision of individual elemental spot-measurements meant that those individual measurements were accurate, or repeatable/reproducible. I think he envisaged elemental concentrations being used primarily as a relative indication of abundance, within a single session in which all elemental concentrations had been derived from the same set of concentration RM measurements. Useful as a parameter by which data-rows might be sorted, for example.
But it is still an interesting question, because people might wish to quantify the relative contributions of spot-uncertainty vs. the 'spot-to-spot' error required to account for the full range of observed variation in elemental concentrations. So I am going to share what I have learnt about how Ludwig coded this in SQUID 2.50 (replicated in Squid3), using U (ppm) as an example. I have made use of User-defined equations in SQUID 2.50 to make the relevant calculations (which Ludwig hid from users) more transparent, in the hope that this will help users customise the equations/expressions for their own use (in SQUID 2.50 or Squid3), such as generating spot-uncertainties for Hf concentrations, for example.
My Task is named "Zircon 09pk exp=2 Rodionov" and it is attached in this ZIP, along with the SQUID 2.50 workbook I made with it (using my own Prawn XML file), and a 'frozen' version of the workbook in case it is useful and/or something goes wrong with the 'live' workbook:
Rodionov_Uppm_Task+SQ2.50books.zip
The Task resembles the classical U-Pb data-reduction routine developed by ANU as far as possible, although users should note that the attached version actually has 10 peaks (including mass 270), in order to match the only Prawn XML file I have in hand today. For 9-peak users, mass 270 can be deleted from the Task without affecting its function. Here are the Special U-Th-Pb expressions, following ANU:

And here are the Reduce Data settings I used. Note that this exercise uses Harvard reference zircon 91500 as both the Isotopic RM and the Concentration RM, because that was the smoothest way to formulate the user-defined expressions. There is no reason why my expressions could not be adapted to use a Concentration RM that differs from the Isotopic RM; there would just be a few extra expressions involved:

Conceptually, the key is to think in terms of "concentration constants", which are evaluated the same way as the "calibration constants" we are all much more familiar with. Both are evaluated using NU-enabled expressions, so both have a %err (at spot-level) generated by "numeric perturbation" of the mass-peaks involved in the expression, using Ludwig's built-in algorithms. I have exposed some of the detail of the "concentration constant" calculation, by replicating the "Special U-Th-Pb expression for uranium concentration" as a User-defined expression ("U_Concen|Constant") in my Task (user-defined expression 7 below; in all cases, the vertical bar is used only to denote a position where a line-break is desired, for labelling purposes):

There are four important user-defined expressions in this set:
The first is expression 7, which has ST and SA both switched off, so it is evaluated for every spot on each of the StandardData and SampleData sheets. An intermediate step in the calculations can be observed on the "Within-Spot Ratios" worksheet of the SQUID-book, which contains the Dodson-interpolated inter-scan values (and times) for all the isotopic ratios, as well as NU-switched expressions. Note that the inter-scan values for my expression "U_Concen|Constant" are identical to those obtained from the expression "ppmU" derived from Ludwig's Special U-Th-Pb expressions:

However, when we move to the StandardData and SampleData sheets, our "U_Concen|Constant" values and their %errs appear in full (StandardData!AV:AW, and SampleData!AJ:AK), whereas the identical "ppmU" data calculated by Ludwig's built-in expressions does not appear at all. Our new columns are analogous to the calibration-constant columns labelled either "Uncorr|Pb/U|const" (StandardData!BY:BZ) or "206Pb/|238U|calibr.|const" (SampleData!AN:AO): they contain the same type of data, but for a different, concentration-related expression.
The second is expression 9, which embodies what SQUID 2.50 and Squid3 actually do with respect to calculating a "U concentration constant" from measurements of the Concentration RM: a simple arithmetic mean of the StandardData U_Concen|Constant values, which ignores their %errs completely. This can be confirmed by comparing the Task-generated "U_Norm|Factor" (StandardData!AZ7) with the ConcStdConst value (labelled "Std mean U const.") at StandardData!CR13.
The third is expression 12, which generates the U (ppm) values for each and every spot, via the equation:
UCC[spot] / UNormFactor = HandUppm[spot] / Uppm[RM]

expressed as:
HandUppm[spot] = Uppm[RM] * UCC[spot] / UNormFactor

where Uppm[RM] in this case is 81 ppm (Wiedenbeck et al,, 1995), UCC[spot] is the spot-specific output of global expression 7, and UNormFactor is the single-value output of RM-based expression 9. Our hand-calculated output (StandardData!BC, and SampleData!AL) compares extremely well to the values calculated from Ludwig's built-in algorithm (StandardData!BN, and SampleData!BA):

I have expanded the full range of significant figures on StandardData for illustration. (Some values show minor differences at the final significant figure, and this is a good example of the numerical "noise" I talked about at the Zoom workshops. Column BC was calculated using Task equations in a front-end Excel spreadsheet, whereas column BN was evaluated by the SQUID 2.50 code in the back-end VBA 6 environment, and the answers are not always identical.)
The fourth is expression 13, which simply converts the %errs associated with U_Concen|Constant, to absolute uncertainties (1sigma, ppm) associated with Hand|Uppm. I think these are the numbers @NickRodionov wanted.
The remaining expressions (8, 10 and 11) were included to assess the relative contributions of (a) the measurement uncertainties and (b) the spot-to-spot error, to the total observed dispersion of spot U (ppm) values in the Concentration RM. Note that the measured %err values on U_Concen|Const for Harvard 91500 are of the order of 1–2% (1sigma).
The first approach is covered by expression 8, which calculates an inverse-variance weighted mean of the U_Concen|Constant values, with output uncertainties expressed as percentages, and auto-rejection of spots forbidden. Ludwig's WtdAv (and sqWtdAv) functions include a maximum-likelihood estimator, the most visible expression of which is the estimation of the most likely constant spot-to-spot error (1sigma, percent) needed to yield MSWD ~ 1 for the population, taking into account the measurement uncertainties.
It is obvious to the naked eye that the data are dispersed far beyond the measurement uncertainties, and sqWtdAv quantifies that: each of the measured 1sigma spot uncertainties (which are of the order of 1–2%), must be supplemented (in quadrature) by a constant spot-to-spot error of 14.5% (1sigma) before the MSWD of the population will be 1.
The second approach spans expressions 10 and 11 (because it seems necessary to do these calculations as separate steps in SQUID 2.50). Expression 10 evaluates the standard deviation of the of the U_Concen|Constant values for 91500 as an absolute value, and expression 11 converts it to a percentage.
The classical standard deviation can be thought of as an "end-member" type of Ludwig's maximum-likelihood estimator, in which the measurement uncertainties are completely disregarded (because their magnitudes are considered totally insignificant, relative to the spot-to-spot error, which the standard deviation approximates), and the value of 15.1% obtained from expression 11 compares well to the value of 14.5% returned by expression 8. This indicates that the approximation obtained by simply applying StDev directly is a good one, in this case (and for U (ppm) in general, I suspect).
Finally, I would say that we can use these data to make guesses about the real sources of spot-uncertainties in U (ppm), and their magnitudes. Expressions 8, 10 and 11 indicate that the true spot-errors on U concentration in this 91500 dataset are ~15%. What are the possible components?

Counting statistics: We already know that measurement uncertainties make up 1–2% of that.
SHRIMP-related reproducibility: Here, we can look at the 206/238 calibration constants for clues regarding the SHRIMP-specific component of repeatability. If we assume that 91500 is truly uniform in 206/238, and we note that the spot-to-spot error of 0.97% (StandardData!BF26) matches well with the individual spot-errors of the 204-corrected calibration constants (StandardData!BF), it seems reasonable to assume that a similar relationship might hold for U (ppm), if 91500 was truly uniform in U (ppm). In that hypothetical scenario, a further 1–2% of the U (ppm) uncertainty (i.e. matching the measurement uncertainties) would come specifically from SHRIMP's inability to reproduce measurement values from spot to spot, even in perfectly homogeneous materials (e.g. Stern & Amelin, 2003).
True heterogeneity of RM: The two lots of 1–2% above still leaves us well short of the 'true' U (ppm) spot-errors of ~15%, and it seems likely that the remaining 10+% has nothing to do with the SHRIMP at all (not counting statistics, not repeatability/reproducibility), but instead purely reflects true variation in the U (ppm) of the RM itself, as we probably already knew.

Hello @NickRodionov and welcome!
I think the main reason Ken Ludwig omitted measurement uncertainties from elemental concentrations in SQUID 2.50 (and Squid3) is as you suggest, and that he did not want users to think that the high precision of individual elemental spot-measurements meant that those individual measurements were accurate, or repeatable/reproducible. I think he envisaged elemental concentrations being used primarily as a relative indication of abundance, within a single session in which all elemental concentrations had been derived from the same set of concentration RM measurements. Useful as a parameter by which data-rows might be sorted, for example.
But it is still an interesting question, because people might wish to quantify the relative contributions of spot-uncertainty vs. the 'spot-to-spot' error required to account for the full range of observed variation in elemental concentrations. So I am going to share what I have learnt about how Ludwig coded this in SQUID 2.50 (replicated in Squid3), using U (ppm) as an example. I have made use of User-defined equations in SQUID 2.50 to make the relevant calculations (which Ludwig hid from users) more transparent, in the hope that this will help users customise the equations/expressions for their own use (in SQUID 2.50 or Squid3), such as generating spot-uncertainties for Hf concentrations, for example.
My Task is named "Zircon 09pk exp=2 Rodionov" and it is attached in this ZIP, along with the SQUID 2.50 workbook I made with it (using my own Prawn XML file), and a 'frozen' version of the workbook in case it is useful and/or something goes wrong with the 'live' workbook:
Rodionov_Uppm_Task+SQ2.50books.zip
The Task resembles the classical U-Pb data-reduction routine developed by ANU as far as possible, although users should note that the attached version actually has 10 peaks (including mass 270), in order to match the only Prawn XML file I have in hand today. For 9-peak users, mass 270 can be deleted from the Task without affecting its function. Here are the Special U-Th-Pb expressions, following ANU:

And here are the Reduce Data settings I used. Note that this exercise uses Harvard reference zircon 91500 as both the Isotopic RM and the Concentration RM, because that was the smoothest way to formulate the user-defined expressions. There is no reason why my expressions could not be adapted to use a Concentration RM that differs from the Isotopic RM; there would just be a few extra expressions involved:

Conceptually, the key is to think in terms of "concentration constants", which are evaluated the same way as the "calibration constants" we are all much more familiar with. Both are evaluated using NU-enabled expressions, so both have a %err (at spot-level) generated by "numeric perturbation" of the mass-peaks involved in the expression, using Ludwig's built-in algorithms. I have exposed some of the detail of the "concentration constant" calculation, by replicating the "Special U-Th-Pb expression for uranium concentration" as a User-defined expression ("U_Concen|Constant") in my Task (user-defined expression 7 below; in all cases, the vertical bar is used only to denote a position where a line-break is desired, for labelling purposes):

There are four important user-defined expressions in this set:
The first is expression 7, which has ST and SA both switched off, so it is evaluated for every spot on each of the StandardData and SampleData sheets. An intermediate step in the calculations can be observed on the "Within-Spot Ratios" worksheet of the SQUID-book, which contains the Dodson-interpolated inter-scan values (and times) for all the isotopic ratios, as well as NU-switched expressions. Note that the inter-scan values for my expression "U_Concen|Constant" are identical to those obtained from the expression "ppmU" derived from Ludwig's Special U-Th-Pb expressions:

However, when we move to the StandardData and SampleData sheets, our "U_Concen|Constant" values and their %errs appear in full (StandardData!AV:AW, and SampleData!AJ:AK), whereas the identical "ppmU" data calculated by Ludwig's built-in expressions does not appear at all. Our new columns are analogous to the calibration-constant columns labelled either "Uncorr|Pb/U|const" (StandardData!BY:BZ) or "206Pb/|238U|calibr.|const" (SampleData!AN:AO): they contain the same type of data, but for a different, concentration-related expression.
The second is expression 9, which embodies what SQUID 2.50 and Squid3 actually do with respect to calculating a "U concentration constant" from measurements of the Concentration RM: a simple arithmetic mean of the StandardData U_Concen|Constant values, which ignores their %errs completely. This can be confirmed by comparing the Task-generated "U_Norm|Factor" (StandardData!AZ7) with the ConcStdConst value (labelled "Std mean U const.") at StandardData!CR13.
The third is expression 12, which generates the U (ppm) values for each and every spot, via the equation:
UCC[spot] / UNormFactor = HandUppm[spot] / Uppm[RM]

expressed as:
HandUppm[spot] = Uppm[RM] * UCC[spot] / UNormFactor

where Uppm[RM] in this case is 81 ppm (Wiedenbeck et al,, 1995), UCC[spot] is the spot-specific output of global expression 7, and UNormFactor is the single-value output of RM-based expression 9. Our hand-calculated output (StandardData!BC, and SampleData!AL) compares extremely well to the values calculated from Ludwig's built-in algorithm (StandardData!BN, and SampleData!BA):

I have expanded the full range of significant figures on StandardData for illustration. (Some values show minor differences at the final significant figure, and this is a good example of the numerical "noise" I talked about at the Zoom workshops. Column BC was calculated using Task equations in a front-end Excel spreadsheet, whereas column BN was evaluated by the SQUID 2.50 code in the back-end VBA 6 environment, and the answers are not always identical.)
The fourth is expression 13, which simply converts the %errs associated with U_Concen|Constant, to absolute uncertainties (1sigma, ppm) associated with Hand|Uppm. I think these are the numbers @NickRodionov wanted.
The remaining expressions (8, 10 and 11) were included to assess the relative contributions of (a) the measurement uncertainties and (b) the spot-to-spot error, to the total observed dispersion of spot U (ppm) values in the Concentration RM. Note that the measured %err values on U_Concen|Const for Harvard 91500 are of the order of 1–2% (1sigma).
The first approach is covered by expression 8, which calculates an inverse-variance weighted mean of the U_Concen|Constant values, with output uncertainties expressed as percentages, and auto-rejection of spots forbidden. Ludwig's WtdAv (and sqWtdAv) functions include a maximum-likelihood estimator, the most visible expression of which is the estimation of the most likely constant spot-to-spot error (1sigma, percent) needed to yield MSWD ~ 1 for the population, taking into account the measurement uncertainties.
It is obvious to the naked eye that the data are dispersed far beyond the measurement uncertainties, and sqWtdAv quantifies that: each of the measured 1sigma spot uncertainties (which are of the order of 1–2%), must be supplemented (in quadrature) by a constant spot-to-spot error of 14.5% (1sigma) before the MSWD of the population will be 1.
The second approach spans expressions 10 and 11 (because it seems necessary to do these calculations as separate steps in SQUID 2.50). Expression 10 evaluates the standard deviation of the of the U_Concen|Constant values for 91500 as an absolute value, and expression 11 converts it to a percentage.
The classical standard deviation can be thought of as an "end-member" type of Ludwig's maximum-likelihood estimator, in which the measurement uncertainties are completely disregarded (because their magnitudes are considered totally insignificant, relative to the spot-to-spot error, which the standard deviation approximates), and the value of 15.1% obtained from expression 11 compares well to the value of 14.5% returned by expression 8. This indicates that the approximation obtained by simply applying StDev directly is a good one, in this case (and for U (ppm) in general, I suspect).
Finally, I would say that we can use these data to make guesses about the real sources of spot-uncertainties in U (ppm), and their magnitudes. Expressions 8, 10 and 11 indicate that the true spot-errors on U concentration in this 91500 dataset are ~15%. What are the possible components?

Counting statistics: We already know that measurement uncertainties make up 1–2% of that.
SHRIMP-related reproducibility: Here, we can look at the 206/238 calibration constants for clues regarding the SHRIMP-specific component of repeatability. If we assume that 91500 is truly uniform in 206/238, and we note that the spot-to-spot error of 0.97% (StandardData!BF26) matches well with the individual spot-errors of the 204-corrected calibration constants (StandardData!BF), it seems reasonable to assume that a similar relationship might hold for U (ppm), if 91500 was truly uniform in U (ppm). In that hypothetical scenario, a further 1–2% of the U (ppm) uncertainty (i.e. matching the measurement uncertainties) would come specifically from SHRIMP's inability to reproduce measurement values from spot to spot, even in perfectly homogeneous materials (e.g. Stern & Amelin, 2003).
True heterogeneity of RM: The two lots of 1–2% above still leaves us well short of the 'true' U (ppm) spot-errors of ~15%, and it seems likely that the remaining 10+% has nothing to do with the SHRIMP at all (not counting statistics, not repeatability/reproducibility), but instead purely reflects true variation in the U (ppm) of the RM itself, as we probably already knew.

Hi guys,
I had a quick look at this, and I would like to point out that all the repeat measurements on grains (2.2, 7.2, 10.2) are generally within 5% of the initial value, suggesting that grain-to-grain variability is the main factor in differing U concentration here.
cheers,
Chuck

Hi guys,
I had a quick look at this, and I would like to point out that all the repeat measurements on grains (2.2, 7.2, 10.2) are generally within 5% of the initial value, suggesting that grain-to-grain variability is the main factor in differing U concentration here.
cheers,
Chuck

@cwmagee true, although it is really "fragment-to-fragment" variability, because 91500 is a single (albeit huge) crystal.

@cwmagee true, although it is really "fragment-to-fragment" variability, because 91500 is a single (albeit huge) crystal.

thank you all for the comments!
It took me a long time to carefully understand everything. For this, respectively, I needed to refresh my memory a lot about Squid-2. Many thanks to @sbodorkos for your perfect clarifications! I just have to find out how to update your task relatively to Temora. We are just measuring Temora + 91500 as primary and additionally M257 as a secondary standard (of both ratio and concentration). Usually mount has more than two fragments of each concentration standard - both 91500 and M257. Therefore, having received at least 4 analyzes of them per session, I have long observingintercross variations in the influence of their inhomogeneity on the concentration value.
Simon, please don't close this discussion, untill I may be asking some clarifying questions.

Hi @NickRodionov, if I updated the Task so that 91500 is the concentration standard (and the errors in Uppm were propagated to all other analyses) even when Temora is selected as the ratio standard, would that help?

Hi @sbodorkos,  for the above, are you talking about propagating errors from sources 1, 2 from above only?  Or also 3 (true heterogeneity)?  Without the latter, I think this gives a false sense of security on the error magnitude, and really we need a long terms sense of what the heterogeneity for a specific CRM is.  This can be monitored if labs export their CRM data as individual cvs and/or the weighted mean of 238/196 for a given session and track the variability over time to assess heterogeneity.  I would be worried about building the error propagation into a task and then it getting used indiscriminately (and without proper assessment of heterogeneity) vs as a separate expression.

... I would be worried about building the error propagation into a task and then it getting used indiscriminately (and without proper assessment of heterogeneity) vs as a separate expression.

Hi @NicoleRayner! Indeed, I also share your concern. But the situation in our laboratory is such that we must demonstrate the entire sequence of obtaining each uncertainty. Actually this complete information will be provided only to an expert-metrologist: uncertainty = measured error + the averaged uncertainty in the corresponding CRM data + a notional inter-mount systematic uncertainty + etc. Really customer will get and see the total of them only! I see no other way, I will be happy if you advise me anything.

Hi @NickRodionov, if I updated the Task so that 91500 is the concentration standard (and the errors in Uppm were propagated to all other analyses) even when Temora is selected as the ratio standard, would that help?

Hi @sbodorkos, that would be great!

Hi @NickRodionov  - maybe I am missing something here but my thought was that Simon (or you, or me?) could write the expression, save it as an xml and post it here.  They you/me/whoever else wants it could import that expression into their preferred task, save the entire task (including that new uncertainty expression) as a Custom squid3 task, then use that in their lab moving forward.  So the calculation is there and exposed but only for those who choose to use it (and I am assuming those would be fairly advanced users and thus less likely to abuse the propagation).

@NicoleRayner, I comletelly agree!

Perfect!  I think writing this as a stand alone expression, not a task is the way to go. You can then bring this expression into whatever task you need.

Hi guys,
This is just a personal observation from trying to run trace elements last year, but our supply of 91500 has a much larger chip-to-chip variation than our M127 or M257 supplies. G7 and G8 also seem to be more homogenous.
cheers,
Chuck

@NicoleRayner My component of uncertainty no. 2 is essentially a theoretical construct - I can't think of any way it could be quantified experimentally, because we would need a material (ideally a zircon-like matrix) that was homogeneous chemically (rather than just isotopically) within and between SHRIMP-pits, and I am not sure how such a material could be sourced/verified.
So I have proceeded on the basis that only no. 1 is real, and that all other sources of error must be attributed to no. 3. I will upload my updated SQUID 2.50 Task (in Task form because SQUID 2.50 needs between 6 and 10 user-defined Equations to do the work, depending on whether the Concentration RM is the same as the Isotopic RM or not) and some documentation to a subsequent post.
Streamlining this Task for use in Squid3 would be useful and educational (I myself don't yet have a good feel for how to do it), but it's a job I am not going to get to any time soon... in the short term, I leave it as an exercise for interested users :)

Hi Simon,
We get good estimates of uncertainty #2 from repeat measurements on single chips for concentration standards, since zoning in most of them is gradual on the tens of microns scale. We should have a discussion of this in the trace element part of Cate's paper, if I ever get that far in the writeup.
Sneak preview says that it's small for those trace elements with enough counts for counting stats not to dominate.

@cwmagee it is a good point, I guess if you used one of these Sri Lankan gem zircons and mounted a bunch of large chips (15?), and then you did a set number of analyses (20?) on each chip, in a proper round-robin to minimise instrument-related factors, you could probably generate 15 estimates of SHRIMP-based spot-to-spot uncertainty, and you could compare those to each other somehow... And you could probably say something about chip-to-chip variation at the same time.

@NickRodionov here is an updated Task. This one is set up to use 91500 as the concentration standard, but it explicitly assumes that 91500 is NOT the ratio standard (instead, that can be whatever you like, and I have used TEMORA2 in this example). In that sense, this Task is complementary to my original Task (which explicitly assumes 91500 is both standards). The ZIP contains the SQUID 2.50 Task, a 'condensed' version of the Prawn XML file I used for testing (to save you sourcing your own), as well as 'live' and 'frozen' versions of the SQUID 2.50 workbook containing the results.
SquidTask_Zircon 09pk exp=2 91500ConcOnly.Bodorkos.zip
Here are the 'Reduce Data' settings I used (note that some of the user-defined expressions are explicitly coded to only function on Sample-analyses prefixed '915'):

And here is the set of user-defined Equations (3–4 and 7–13) that do the work:

Equation 3 calculates U Concentration Constants (and their numerically-perturbed %err values) solely for the designated concentration standard (here prefix 915). Equation 4 calculates then the simple arithmetic mean of the spot-values (following the practice of SQUID 2.50 and Squid3).
Equations 5 and 6 are purely to illustrate that the StDev-based solution @NickRodionov is already using to address this issue is both simple and effective (as the ensuing calculations demonstrate).
Equations 7 calculates the spot-to-spot (external) error based on the 91500 dataset. Unfortunately, the sqWtdAv function does not output MSWD, which is annoying. I guess I could derive it from the probability-of-fit and the number of analyses, if it would be useful/informative. Equation 8 isolates the external error (1sigma, %), which is necessary in SQUID 2.50 to enable the value to be used across both the StandardData and SampleData sheets in subsequent calculations.
Equation 9 duplicates the U Concentration Constants calculation (and their numerically-perturbed %err values), but this time for every spot in the StandardData and SampleData sheets. Equation 10 augments the numerically-perturbed %err value for each spot, by quadratic addition of the external error (1sigma, %) value derived from the 91500 measurements. This process is analogous to how we calculate 206Pb/238U ages for SampleData rows, using a single external error derived from the StandardData set.
Equation 11 converts the spot-specific concentration constants into U (ppm) values, by reference to the average value determined on 91500 (equation 4), and the "true" U (ppm) val;ue for 91500 (81 ppm; included in this Task as a Constant). Equations 12 and 13 simply convert each spot-specific numeric %err and expanded %err into 1sigma absolute values, with units of ppm.
Equations 14–16 are purely to illustrate the role of the external error when applied back to the 91500 dataset from which it was derived in the first place. Calculating the weighted mean of the 91500 analyses with expanded uncertainties should give a result with an MSWD ~ 1 (because this is the basis of Ludwig's maximum-likelihood estimator, which he built to approximate external errors). And it does work, although the effect is spoiled slightly by the failure of sqWtydAv to return an MSWD value. Hopefully the probability-of-equivalence value (~0.37) is familiar enough for people to recognise that the associated MSWD would be close to 1.

Simon, the 91500 chip to chip concentration variation is up to 50% (as, indeed, are the various literature values for Hf concentration), and the intra spot uncertainty is 0.5 to 1%, so you don't need very many spots to see the effect there. The various Nasdala RZs are better, but I think you can still pick chip to chip differences by eye off of a weighted mean.

@NickRodionov - are we ready to close this issue?

@bowring - yes, thanks to all


Inconsistency in EvalAI-ngx.

I'm submitting a
(Check one with "x" from given options)

[x] Bug report
[ ] Feature request

Current behavior
I noticed that in the EvalAI-ngx sometimes "state-of-the-art" is used, other times "state of the art" is used.
Expected behavior
Either "state of the art" or "state-of-the-art" should be used.
Which one should we use so we don't make it look inconsistent and I can make a pull request for it?

@Sanji515 @pushkalkatara @vkartik97 @Ram81 @RishabhJain2018

@nsjcorps Are you talking about the line "state of the art" that is shown at homepage . because i dont see line like "state-of-the-art" in the repo

state-of-the-art was used in :
about.component.html line 10
get-involved.component.html line 11
home.component.html line 3
state of the art was used in
footer.component.html line 6
homemain.component.html line 3
auth.component.html line 27
@Suryansh5545

Yea i Saw Now.

@nsjcorps thanks for reporting this. If you are interested in fixing this issue, please let me know.

I created a PR for it already @vkartik97
https://github.com/Cloud-CV/EvalAI-ngx/pull/261

I think you should also take a look at  https://github.com/Cloud-CV/EvalAI-ngx/pull/256 @vkartik97


[Impex] Importing Product Types does not work

Support reference number
SUPPORT-3157
Description
A client has reported that they cannot import productType after exporting the productType in Impex and trying to import it again using CSV. The error is "Cannot read the property "name" of undefined"
Expected Behavior

Current Behavior
Steps to duplicate:
export any product type ( via a predicate ) or all of them ( no predicate ), then use the import tool.
1- Using the ProductTypeExport to export all product types on a project.
2- Downloading the zip file and extracting it.
3- Opening the Product Type Import then choosing "tkaupat-dev" project.
4- Put the "attributes.csv" file in "Product Type attributes as CSV" section on the right.
5- Put the "products-to-attributes.csv" file in "Product Type template as CSV" to the left.
6- Run Command.

Fixed in this release


Unify parameter name between udp and syslog plugins

in_syslog is widely used so using message_length_limit is better for users.

@tagomoris Could you check this?

I will merge this patch tomorrow.


Fix Tika configuration

Currently at startup this gets logged:
Nov 15, 2017 10:17:30 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.

We should exclude the sqlite parser - don't think we need it :)

See https://tika.apache.org/1.17/configuring.html#Load_Error_Handling


Expand logic around H5Literate2 data structure use.

Fixes #2976

Note to self, tested against HDF5 1.10.10 and 1.14.4 to check logic around the presence and absence of H5Literate2.


Update nf-audioclient-iaudioclient2-getbuffersizelimits.md

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


DeadObjectElimination: fix a bug which caused wrong inserted release instructions.

This bug triggered an "instruction isn't dominated by its operand" verifier crash.
Or - if the verifier doesn't run - a crash later in IRGen.
rdar://94376582

@swift-ci smoke test linux

@swift-ci smoke test linux

@swift-ci test linux

@swift-ci test


Why is https://prod-api.outsyde.app/packagestyles.css used

Hi, thanks for creating this package.
I wanted to ask, is there any reason you are using https://prod-api.outsyde.app/packagestyles.css? Seems to be from a company that is not related at all to development?
I think this was added 2 weeks ago by @hxf31891

Hey @NderimPlanA great question.
Next compatibility with node module projects css files had been giving me fits. That domain belongs to another little side project of mine (feel free to check it out on the app store 😂) and I deployed the styles there as a work around. Now that I write this it makes a lot more sense to bundle them with the demo project and I will update there in the next version. Other than being un-usual does this create an issue for you?


read config file before checking for existence of datadir

Fixes #241
The code was checking for the existence of the datadir before reading and processing the config file. This means that when the datadir was only specified in the config file, we ended up checking whether the default dir existed, which it does, and then reading in a nonexistent datadir after that, causing later code (which assumes this check has already been performed and passed) to have erratic behavior.
So the fix is just to move the "read config" code up higher so it happens first. I think in general reading the config file should be as high as possible in this function, or maybe even up higher in the call tree? Not sure how the GUI mode interacts with the conf file yet though.

@jeffgran It looks like Core addressed this issue in https://github.com/bitcoin/bitcoin/pull/11829.
The core fix has the advantages of exiting sooner and prefixing the error message (via thrown exception) with "Error reading configuration file:".  What do you think of changing your branch into a cherry-pick of the core change?  (another advantage is making future cherry-picks easier.)

Thanks for debugging this. I agree that @dgenr8's suggestion to move the check into ReadConfigFile and throw to get the error prefix is a slightly better.

@xt-bot add to whitelist

Just getting back to this. Thanks for the comments.
I disagree that their fix is better -- it duplicates the check that already exists in the AppInit into another place, and that second place is a function named ReadConfigFile -- I think it's strange to check the validity of just this one config setting inside the read-config subroutine.
However, to argue against myself, I do take your point that cherry-picking core's commits makes it easier to cherry pick others later, and this obviously isn't a super important change so I'll update this to take core's fix a little later.

@jeffgran You make a good argument. Thank you!


feat(migrate-getsubgraphswaps): Migrated getsubgraphswaps logic

What this PR does / why we need it:

Migrated the getSubgraphSwaps logic from legacy-api to whale-api to quickly improve over the wire performance of v1/getsubgraphswaps API without investing in a full-fledge indexer

Which issue(s) does this PR fixes?:

Fixes #1483

Additional comments?:

A direct HTTP call from legacy-api to whale-api is made (instead of invoking whale-api-client) as the new endpoint in the latter is meant for exclusive use by the former
[Important]: The getsubgraphswaps endpoint in legacy-api (https://api.defichain.com/v1/getsubgraphswaps) is now dependent on a whale-api endpoint (https://ocean.defichain.com/v0/mainnet/legacy/getsubgraphswaps) that does not exist at this moment. Therefore, the new endpoint in whale-api has to be deployed before the changes in legacy-api can be tested and deployed as well

legacy-api poolpaircontroller test is failing - can we mock the response from ocean?


"No training configuration found in the save file"

In 64pix2pix after running the last bit of code under "save the model" it says:
tensorflow:Compiled the loaded model, but the compiled metrics have yet to be built. model.compile_metrics will be empty until you train or evaluate the model.
and in model_img2LUT it says:
WARNING:tensorflow:No training configuration found in the save file, so the model was not compiled. Compile it manually.
Did anyone find a solution this problem?

Hi, thanks for your comment. Are you going to retrain a loaded mode? I guess indeed I never tried out to retrain a pretrained model. If you not trying to retrain I guess these messages could be ignored

I'm training a new model, the thing is that at the end of this page:
https://github.com/andjoer/AI_color_grade_lut
it says:
Wait until you see the generated .cube file in the content folder
Download the .cube file and apply it in any program that can apply LUTs (Photoshop, Premiere, Resolve etc.)
But no .cube file is ever generated all I got is the warning messages from above, I trained a new model 20 mins ago but now I also get this at the end of the model_imgLUT colab:
ValueError: Input contains NaN, infinity or a value too large for dtype('float32').
I will try it again with the 128pix2pix maybe that one will work?
(Also for anyone that gets a problem at the "Read the files" stage, there is this bug where when it extracts the "pictures.zip" the "train" and "test" folders get moved to the root and the "pictures" folder gets deleted so you have to create a new folder called "pictures" and move the "test" and "train" folders back in.)

it has been a while since I worked on this. But what I see is that the parameter img_size needs to be set manually in order to fit the trained model. so if you trained 64px it needs 64. Could you maybe try to model_img2LUT with a 128pix model that I published?

I just tried it with wallstreet.h5
it gave me this error:
ValueError                                Traceback (most recent call last)
 in ()
14
15
---> 16 output = processing(advanced, max_factor, model_path, file_path, reverse, size)
8 frames
 in processing(advanced, max_factor, model_path, image_path, reverse, img_size)
209         LUT = img_to_lut_adv(input_image[0], target[0], max_factor)
210       else:  # create the LUT in standard mode
--> 211         LUT = img_to_lut(input_image[0], target[0])
212     filename, file_extension = os.path.splitext(image_path)
213     output = filename + '.cube'
 in img_to_lut(input_image, target_image)
94     interpolation = neighbors.KNeighborsRegressor(40, weights='distance')
95     LUT = np.asarray(LUT)
---> 96     tRp = interpolation.fit(icolor, tR).predict(LUT)
97     tGp = interpolation.fit(icolor, tG).predict(LUT)
98     tBp = interpolation.fit(icolor, tB).predict(LUT)
/usr/local/lib/python3.7/dist-packages/sklearn/neighbors/_regression.py in fit(self, X, y)
211         self.weights = _check_weights(self.weights)
212
--> 213         return self._fit(X, y)
214
215     def predict(self, X):
/usr/local/lib/python3.7/dist-packages/sklearn/neighbors/_base.py in _fit(self, X, y)
398         if self._get_tags()["requires_y"]:
399             if not isinstance(X, (KDTree, BallTree, NeighborsBase)):
--> 400                 X, y = self._validate_data(X, y, accept_sparse="csr", multi_output=True)
401
402             if is_classifier(self):
/usr/local/lib/python3.7/dist-packages/sklearn/base.py in _validate_data(self, X, y, reset, validate_separately, **check_params)
579                 y = check_array(y, **check_y_params)
580             else:
--> 581                 X, y = check_X_y(X, y, **check_params)
582             out = X, y
583
/usr/local/lib/python3.7/dist-packages/sklearn/utils/validation.py in check_X_y(X, y, accept_sparse, accept_large_sparse, dtype, order, copy, force_all_finite, ensure_2d, allow_nd, multi_output, ensure_min_samples, ensure_min_features, y_numeric, estimator)
977     )
978
--> 979     y = _check_y(y, multi_output=multi_output, y_numeric=y_numeric)
980
981     check_consistent_length(X, y)
/usr/local/lib/python3.7/dist-packages/sklearn/utils/validation.py in _check_y(y, multi_output, y_numeric)
988     if multi_output:
989         y = check_array(
--> 990             y, accept_sparse="csr", force_all_finite=True, ensure_2d=False, dtype=None
991         )
992     else:
/usr/local/lib/python3.7/dist-packages/sklearn/utils/validation.py in check_array(array, accept_sparse, accept_large_sparse, dtype, order, copy, force_all_finite, ensure_2d, allow_nd, ensure_min_samples, ensure_min_features, estimator)
798
799         if force_all_finite:
--> 800             _assert_all_finite(array, allow_nan=force_all_finite == "allow-nan")
801
802     if ensure_min_samples > 0:
/usr/local/lib/python3.7/dist-packages/sklearn/utils/validation.py in _assert_all_finite(X, allow_nan, msg_dtype)
114             raise ValueError(
115                 msg_err.format(
--> 116                     type_err, msg_dtype if msg_dtype is not None else X.dtype
117                 )
118             )
ValueError: Input contains NaN, infinity or a value too large for dtype('float32').

sorry, I currently don't have the time to debug myself. But could you try to set advanced = 0? this has less parameters so less could go wrong

"advanced" was already set to false, I set it to = 0 (maybe there is a difference?) just now it didn't work. Don't worry about it, somebody else might come up with a solution.


Basic changes

Some code reorganization (not sure how this worked previously on your system). Also, removed import * from most places.
However, you can still import * if you wish. You will have to change how you import the package in any of your code to
from pulseblaster.PBInd import PBInd
from pulseblaster.spinapi import *

It shouldn't break anything.

Hey! Just saw you merged this in. Glad the changes seemed to be okay with you. Next step will be to start using the pulse blaster on the confocal system.

Yup they were great, a lot more readable and works well. Exciting stuff!!
On Wed, Sep 7, 2022 at 4:39 PM G Adam Cox @.***> wrote:

Hey! Just saw you merged this in. Glad the changes seemed to be okay with
you. Next step will be to start using the pulse blaster on the confocal
system.
—
Reply to this email directly, view it on GitHub [github.com]
https://urldefense.com/v3/__https://github.com/zeeshawnkazi/pulseblaster/pull/1*issuecomment-1240023133__;Iw!!K-Hz7m0Vt54!m2jhXzsDma4UU97R0Tgx5QY4JJLie8qM54_sz2zsmvbKj-WSY1_Ks3cCsF5UPeplPGt6eX6naZUtnLMwibYG-jkn$,
or unsubscribe [github.com]
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AKNJ2FHYG5ISJL74HSP45TTV5ERRLANCNFSM53JMBP2Q__;!!K-Hz7m0Vt54!m2jhXzsDma4UU97R0Tgx5QY4JJLie8qM54_sz2zsmvbKj-WSY1_Ks3cCsF5UPeplPGt6eX6naZUtnLMwiUIQ6V8w$
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


3 rare things that I don't know the reason

Hi devs,
1) Im trying to create a yml doc with some array, the doc get created but inside the doc there is --- at the begin of the file, what is this?
$acceptance = [
	'class_name' => 'AcceptanceTester',
];

string(...) "--- <------- WHAT IS THIS?
class_name: AcceptanceTester
"

2) I would like to create something like this:
class_name: AcceptanceTester
modules:
    enabled:
        - PhpBrowser
        - WebHelper

This is my code:
$enabled = "- PhpBrowser \n- WebHelper";
$acceptance = [
	'class_name' => 'AcceptanceTester',
	'modules' => [
		'enabled' => $enabled,
	]
];

But instead I get:
---
class_name: AcceptanceTester
modules:
    enabled: | <------------ WHY IS THIS HERE?
        - PhpBrowser
        - WebHelper

With a pipe( | ) and the previous --- that I previously explained
3) Im trying to create a field with this format:
 url: 'http://someurl.com'

This is the code:
$module = [
	'modules' => [
		'config' => [
			'PhpBrowser' => [
				'url1' => $domain,
				'url2' => "'$domain'",
				'url3' => "$domain",
				'url4' => '\'$domain\''
			]
		]
	]
];

And I get:
modules:
    config:
        PhpBrowser:
            url1: http://someurl.com
            url2: "'http://someurl.com'"
            url3: http://someurl.com
            url4: "'$domain'"

Any solution, Thank you very much in advance!

is correct, that's how YAML indicates the beginning of a document.

is also correct, the | indicates that the following is a string. It should probably look like this:

$acceptance = [
    'class_name' => 'AcceptanceTester',
    'modules' => [
        'enabled' => array(
            'PhpBrowser',
            'WebHelper'
        ),
    ]
];

(I think, I haven't tested it.)

Either of these should work (again, haven't tested)

$module = [
    'modules' => [
        'config' => [
            'PhpBrowser' => [
                'url1' => "'" . $domain . "'",
                'url2' => "'{$domain}'",
            ]
        ]
    ]
];


View not redrawing when State/Binding data changes

  .bottomSheet(bottomSheetPosition: $bottomSheetPosition,
                     switchablePositions: [.dynamic, .hidden],
                     title: NSLocalizedString("Set up Social Login", comment: "")) {

//Updating binding In child view
            LinkAccountProviderView()
                .padding([.horizontal, .vertical])
                .padding([.bottom])

        }

Binding updates never trigger the view to redraw.

Hello @Dave181295,
I don't understand your issue and can't reproduce it with the provided code. Please make sure that you handle view updates and state management/observation correctly. If you share more details on the issue, I will revisit and reopen it if applicable.


how can we release for multiple environments?

as for now, we have main, test, qa, dev environments?

let's park this until we agree on a release process, maybe we should just release mainnet plugin only?

Suggestion:

Release only (say main branch) is always aligned with mainnet version
Development branche(s) are aligned with other networks (devnet, and qanet)
Developers can checkeout dev branches to work against the network of choice
We create releases only for mainnet


multiline edit text widget

Can be implemented as List of text labels and one InputField where the cursor is.

For rich text it is enough to set font aliases and colors and then only set font and color for text block

rich text is not needed for simple multiline widget

implement utility function to fit text to width

move text variable to TextWidget and keep it as vector of lines. Single line widget will only use 1st line


Uncaught TypeError: Cannot read property 'type' of null

[Enter steps to reproduce below:]

...
...

Atom Version: 0.165.0
System: Mac OS X 10.10.2
Thrown From: color-picker package, v1.5.0
Stack Trace
Uncaught TypeError: Cannot read property 'type' of null
At /Users/Sayyad/.atom/packages/color-picker/lib/ColorPicker-view.coffee:383

TypeError: Cannot read property 'type' of null
  at ColorPickerView.module.exports.ColorPickerView.refreshColor (/Users/Sayyad/.atom/packages/color-picker/lib/ColorPicker-view.coffee:383:60)
  at HTMLBodyElement.<anonymous> (/Users/Sayyad/.atom/packages/color-picker/lib/ColorPicker-view.coffee:215:29)
  at HTMLBodyElement.handler (/Applications/Atom.app/Contents/Resources/app/src/space-pen-extensions.js:112:34)
  at HTMLBodyElement.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at HTMLBodyElement.elemData.handle (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)

Commands
     -38:07.1 core:confirm (input.hidden-input)
     -30:00.0 core:cancel (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-seti-syntax.theme-atom-dark-ui)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "seti-syntax"
    ]
  }
}

Installed Packages
# User
autocomplete-plus, v2.1.3
color-picker, v1.5.0
css-snippets, v0.5.0
emmet, v2.3.4
linter, v0.10.1
seti-syntax, v0.2.1

# Dev
No dev packages

/cc @atom/core

Hi, please update Atom and try again.

ok thanks


Unknown word tailwind.config.js build

CssSyntaxError MYPROJECTFOLDER/tailwind.config.js:4:27: Unknown word
Is displayed when I build the file, however, if the file is blank it still runs with the same error with the same line.
here is my webpackfile
`const mix = require('laravel-mix');
require('mix-tailwindcss');
/*
|--------------------------------------------------------------------------

Mix Asset Management

Mix provides a clean, fluent API for defining some Webpack build steps

for your Laravel application. By default, we are compiling the Sass

file for the application as well as bundling up all the JS files.

*/

mix.js('resources/js/app.js', 'public/js')
.sass('resources/sass/app.scss', 'public/css')
.tailwind('tailwind.config.js');
`
Any help is much appreciated.

What is require('mix-tailwindcss'); supposed to do? I haven't seen or used that before. Could that maybe be causing the issue?
If you're using https://github.com/JeffreyWay/laravel-mix-tailwind, I believe that it should be require('laravel-mix-tailwind');.


Manual driving UI

User Story:
As a user I want the application to allow me to drive the car so that I can make it reach a certain location successfully.
Acceptance Criteria:
Given the user is in manual control mode,
When the user uses the manual controls,
Then the car will move per commands given via controls.

This is not a vertical User Story as it deals solely with the UI and thus, is marked as invalid and is being closed.


cherry-pick-branch property doesnt work

Hi,
I have tried using this action and noticed that setting your own branch name does not work. It always takes that default predefined format. Or maybe i am doing something wrong?
`jobs:
cherry_pick_release_v1_0:
  if: contains(github.event.pull_request.labels.*.name, 'release-v1.0') && github.event.pull_request.merged == true

  runs-on: ubuntu-latest

  steps:
    - name: Checkout

      uses: actions/checkout@v2

      with:

        fetch-depth: 0

  - name: Delete branch

    run: |

      git push origin --delete cherry-pick-to-release-v1.0

    continue-on-error: true

  - name: Cherry pick into release-v1.0

    uses<EMAIL_ADDRESS>
    with:

      branch: release-v1.0

      labels: cherry-pick

      cherry-pick-branch: cherry-pick-to-release-v1.0

    if: always()`

but it always create a branch in such format:
cherry-pick-5abd4075611de29302836741aeec1efc0a4ce69c

oh after further investigation i see that it even says that its not valid input in logs even though in documentation listed as valid input

but logs says:
Warning: Unexpected input(s) 'cherry-pick-branch', valid inputs are ['token', 'committer', 'author', 'branch', 'labels', 'assignees', 'reviewers', 'team-reviewers']

i see in code there is such input, so most likely you guys should just update your documentation as in documentation it says to use 1.0.1 version, but i see in marketplace there is 1.0.9 already, so will try that version to see if it will work with this cherry pick branch input

yeah everything works with 1.0.9, so closing this issue.


Cannot run on Arch with .NET 7 installed

I'm running Arch Linux where dotnet by default has the .NET 7 runtime. I can install the .NET 6 runtime as well, but even then the extension gives the error message

/usr/bin/dotnet is not a compatible dotnet file. Dafny requires the ASP.NET Core Runtime 5.0 or 6.0, got Microsoft.AspNetCore.App 7.0.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.12 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Can the IDE force dotnet to use version 5 or 6 if installed? Or to provide a path to the desired SDK/runtime rather than the dotnet binary? As far as I can tell there's no easy way on Arch to get the dotnet binary to use version 6 by default, and that would interfere with other installed packages that depend on dotnet anyway.

After looking at the source code for the plugin and seeing exactly what pattern it's looking for, I figured out the issue. I have NETCore.App 6 but not ASP.NET Core 6. Installing aspnet-runtime-6.0 solved the problem. Sorry for the noise!


'Anchor word not in word column labels provided to CorEx:

How to skip if anchor words not in topic and still produce results for those words available

Hi Srujana,
Would you be able to clarify what your question?  And what words and results do you want to see results for?

I am using anchor words like this
topic_model.fit(X, words=words, anchors=[['dog','cat','animal'], ['home','interior', 'furniture'], ['beauty', 'cosmetic'], anchor_strength=3)]
If I want to fit this model (with same parameters) for a new data (X) and if it doesn't have a word 'cosmetic' then I am getting error 'Anchor word not in word column labels provided to CorEx:'
I want same topics for new dataset but it is hard to change anchor words every time I fit the model
Is it that anchor words must be present in the data we provide?

Yes, right now the code is structured such that the anchor words must be present in the data that is provided. This is to help alert the user that the words they are trying to anchor cannot be anchored.
@gregversteeg, do you think this should raise a warning instead? The error that's thrown is here, in preprocessing the anchors.

Yes, a warning would do the job and still produce the results with words that can be anchored.
Thanks!!

Thanks for your patience @srujana-tak. I've made the update so that CorEx throws a warning instead of an error if the anchor is not in the vocabulary. Let me know if you have any further issues.
I've also updated CorEx on pip, so if you installed it via pip then you should be able to update it using pip install corextopic --upgrade

Thank you!


Require Pigeon to verify message already included in block before sending next message

Background
Pigeon is sending messages too quickly for Paloma to process. As such, Paloma is unable to come to consensus on adding attestation and other chain information. We want Pigeon to check messages are submitted to Paloma and included in a block before sending another message.
Done when

[ ] Pigeon Protos are all verified as sent/included in a block before the next message is sent.
[ ] Pigeon will not sign and broadcast more than one message per key per block
[ ] Pigeon will have a second key for singing messages that

@byte-bandit is this already resolved?

We already wait for messages to be included in a block.
We're using the legacy lens-based client, that uses broadcastTx to communicate with paloma, which calls BroadcastTxSync and then polls Tx until the transaction is confirmed. I added a delay in paloma, which increased the time we spent polling.
Also, the lock in the wrappers SendMsg means we wait until one message is fully processed before sending the next one.
We could optimize this, but the client is still highly integrated with a single key, e.g. here, and is not prepared for concurrent requests. I tried changing some of those to a dynamic key but still had issues, so we would need a larger effort to refactor the client.

Thanks @maharifu for the deep dive. So the good news is, this ticket is already done. We may want to explore non-blocking pigeon calls in the future though, as this might potentially become a bottleneck in the future.

Closing as fixed.


Assignment2-Exercise-List

Hey There.MLCC Guys..!!! I have solved the problem..check it out. I have used the function to iterate in the
the dictionary containing the keys and their corresponding frequencies.

List Exercise: Completed
Complete Numpy Exercise and Numpy Examples!

Here...I am submitting my Numpy_Exercise_1 exercise.


Create Jupyter notebook

PR: https://github.com/chanzuckerberg/aurora-scratch/pull/7

Issue moved to chanzuckerberg/aurora-scratch #8 via ZenHub


fine tuning on other LM models

Thanks for your great work！

Can I fine tuning in other LM models, eg. GPT 、 GPT-2？


Suggestion - Otto

If you want to build your apps in way that they have loose coupling between blocks, which could be switched in very easy way you definitely have to read about Otto!.
In short, Otto is an event bus designed to decouple different parts of your application.
I would enjoy contributing to a guide about this. Let me know if you have an interest.

@petzel might be working on a guide for this!

The limitations and considerations given the lifecycle of fragments/activities documented here would be a big plus here..

First draft started: https://github.com/codepath/android_guides/wiki/Communicating-with-an-Event-Bus

Looks like a great start @rogerhu, thanks for getting this going


Add Replicate demo and API for textdiffuser-2

Hi @JingyeChen 👋,
Awesome work on textdiffuser-2!
This pull request makes it possible to run textdiffuser-2 on Replicate (https://replicate.com/cjwbw/textdiffuser-2) and via API (https://replicate.com/cjwbw/textdiffuser-2/api). Also happy to transfer the demo page to microsoft so you can make modifications easily :)

Hi chenxwh, many thanks for your contribution and your interest in TextDiffuser-2. Hope the replicate demo will help improve the user experience!


Windows JupyterLab failing to launch after setting python executable to WSL python

I was excited to try JupyterLab on WSL/Ubuntu and maybe the support is not there yet.
Tried installing the Windows version, it asked me where's my python executable, I pointed it to the pyenv python (on WSL).  Relaunching the app returns nothing.  No error message, just silent failure.
Also tried installing the .deb package, nothing happens after launching jlab.

@liquidcarbon Thank you for your report! To help diagnose this issue, can you please provide logs?
Start the application from command line as jlab --verbose 4, wait until it settles.
Copy-paste the logs from the following location:
on Linux: ~/.config/jupyterlab-desktop/logs/main.log
on macOS: ~/Library/Logs/jupyterlab-desktop/main.log
on Windows: %USERPROFILE%\AppData\Roaming\jupyterlab-desktop\logs\main.log
(In the case of WSL, I'm not sure whether the Linux or the Windows location will be used.)

Oh i forgot about the $DISPLAY part
 jlab --verbose 4
[469:0223/120817.435188:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
[469:0223/120817.435251:ERROR:env.cc(255)] The platform failed to initialize.  Exiting.
Segmentation fault

I set display as follows: export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0
(I do not know what I'm doing on this one).
Then the next launch jlab --verbose 4 launch take forever to respond with the same message.
On Windows:
[2023-02-21 18:11:57.289] [error] Failed to create free server Error: No default environment found!
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
[2023-02-21 18:11:57.292] [error] (node:16172) UnhandledPromiseRejectionWarning: Error: No default environment found!
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
(Use `JupyterLab --trace-warnings ...` to show where the warning was created)
[2023-02-21 18:11:57.292] [error] (node:16172) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-21 18:13:01.608] [error] Failed to get environment info at path '\\wsl.localhost\Ubuntu\home\a\.pyenv\shims\python3.10'. Error: spawn UNKNOWN
    at ChildProcess.spawn (node:internal/child_process:413:11)
    at spawn (node:child_process:737:9)
    at Object.execFile (node:child_process:338:17)
    at t.<computed> [as execFile] (node:electron/js2c/asar_bundle:2:2218)
    at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:671:49
    at new Promise (<anonymous>)
    at Registry._runCommand (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:670:16)
    at Registry.getEnvironmentInfo (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:276:43)
    at Registry._resolveEnvironment (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:158:32)
[2023-02-21 18:13:02.317] [error] SyntaxError: Unexpected token 'E', "EXEC:ERROR" is not valid JSON
    at JSON.parse (<anonymous>)
    at Registry.getEnvironmentInfoSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:305:30)
    at Registry._resolveEnvironmentSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:168:26)
    at new Registry (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:70:33)
    at new JupyterApplication (C:\JupyterLab\resources\app.asar\build\out\main\app.js:175:26)
    at C:\JupyterLab\resources\app.asar\build\out\main\main.js:202:22
[2023-02-21 18:14:09.594] [error] SyntaxError: Unexpected token 'E', "EXEC:ERROR" is not valid JSON
    at JSON.parse (<anonymous>)
    at Registry.getEnvironmentInfoSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:305:30)
    at Registry._resolveEnvironmentSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:168:26)
    at new Registry (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:70:33)
    at new JupyterApplication (C:\JupyterLab\resources\app.asar\build\out\main\app.js:175:26)
    at C:\JupyterLab\resources\app.asar\build\out\main\main.js:202:22
[2023-02-21 18:14:35.967] [error] SyntaxError: Unexpected token 'E', "EXEC:ERROR" is not valid JSON
    at JSON.parse (<anonymous>)
    at Registry.getEnvironmentInfoSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:305:30)
    at Registry._resolveEnvironmentSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:168:26)
    at new Registry (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:70:33)
    at new JupyterApplication (C:\JupyterLab\resources\app.asar\build\out\main\app.js:175:26)
    at C:\JupyterLab\resources\app.asar\build\out\main\main.js:202:22
[2023-02-21 18:16:51.339] [error] SyntaxError: Unexpected token 'E', "EXEC:ERROR" is not valid JSON
    at JSON.parse (<anonymous>)
    at Registry.getEnvironmentInfoSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:305:30)
    at Registry._resolveEnvironmentSync (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:168:26)
    at new Registry (C:\JupyterLab\resources\app.asar\build\out\main\registry.js:70:33)
    at new JupyterApplication (C:\JupyterLab\resources\app.asar\build\out\main\app.js:175:26)
    at C:\JupyterLab\resources\app.asar\build\out\main\main.js:202:22

@mbektas Is there a tracking issue for "Make JupyterLab Desktop work on WSL"? If not, should we create one? Should we update the docs to indicate that Windows users should download the Windows installer rather than try to install via WSL?

@JasonWeill we don't have an issue tracking WSL support. feel free to create one. thanks.

@mbektas Done; just opened #666 :smiling_imp:


I have written code for how to check if a connected graph is bipartite

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

We don't accept PRs without any corresponding Issue. Also use Git CLI instead of Github Web UI


Updates contribution guidelines with git-format git am method

Description

Updates git-diff method which unfortunately does not quite work with new git-format + git am method which I have used successfully and works pretty well.

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

@emanic Can we close this PR?


Small fix for the pretrain issue

Many models don't need the pretrain functionality and this small fix allows it to be left out in the respective configs. I only tested it vaguely though.

@XgamerTV Do we sill need this and if so: please resolve the merge conflict.

I believe the addition is not really needed anymore but it shouldn't hurt if wanting to allow model configs/models that don't use pretrain info. I merged main into it and did a test run :)


ikea KADRILJ blinds are included in domoticz zigbee2mqtt plugin?

Dear friend,
I have seen in the devices that support their plugin zigbee2mqtt for domticz and the FYRTUR blind is included, but the KADRILJ blind is not included.
I am thinking of buying a KADRILJ blind. Do you know if it would also work directly with zigbee2mqtt without using the TRÅDFRI gateway? because I understand that the FYRTUR blind works directly with zigbe2mqtt without using TRADFRI. I'm right?
I am getting rid of all the gateways and I would not like to have one more
Would you be kind enough to clarify these doubts for me before making the purchase of the blind and in the event that KADRILJ is not supported by zigbee2mqtt, could you include it in the plugin?
Thank you very much, nobody knows how to answer these questions.
A cordial greeting
Best regards

Hi,
KADRILJ is already supported by the plugin. This is the same behavior as FYRTUR.
I confirm that you don't need the TRADFRI gateway. You only need a zigbee2mqtt adapter:
https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html

thanks,
Best regards


bug of moving to photo overlay at story telling

Describe the bug
moving to photo overlay at story telling, camera will stops on the way.
To Reproduce
Put photo overlay layer and set overlay image.
Add story telling widget and set photo overlay layer on stories list.
When moving to photo overlay layer by clicking button of story telling, camera will stops and photo overlay image will be shown on the way without reaching photo overlay layer .
Expected behavior
if clicking button of story telling to move to photo overlay layer, overlay image will shown after camera reach to the layer without moving camera is stopped.
Screenshots

Desktop (please complete the following information):

OS: [ iOS]
Browser [ chrome

Temporary solution:

Set StoryTelling General Duration  to smaller then 2 s


Javadoc cleanup across the project

Went through and cleaned up the various java doc generation errors across the project.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jcampb012 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add copy svg code plugin to README

Description
Add the Copy SVG Code plugin!
Related Issue

Motivation and Context

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] I have read the CONTRIBUTING document.

Awesome :-) merging in!


Improvements

Codecov Report

Merging #65 (95a2805) into master (75b1043) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #65   +/-   ##
=======================================
  Coverage   99.65%   99.66%
=======================================
  Files          33       36    +3
  Lines         876      901   +25
  Branches      108      108
=======================================
+ Hits          873      898   +25
  Partials        3        3

Impacted Files
Coverage Δ

...I/SoftAPIClient/Implementations/XmlDeserializer.cs
100.00% <ø> (ø)

...nt/Implementations/DataContractJsonDeserializer.cs
100.00% <100.00%> (ø)

...mplementations/DataContractJsonObjectSerializer.cs
100.00% <100.00%> (ø)

...ftAPIClient/Implementations/XmlObjectSerializer.cs
100.00% <100.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 75b1043...95a2805. Read the comment docs.


change runParameters.xml to RunParameters.xml

I had to make this change for the latest batch of data.
A better solution would be to allow lowercase r or uppercase R in the filename.
I haven't tested to see if this pull request would make previous jobs fail, but it probably would.
Without this change, I get this error:
Traceback (most recent call last):
  File "/home/ks38/.conda/envs/jupyter/bin/alto", line 11, in <module>
    load_entry_point('altocumulus', 'console_scripts', 'alto')()
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/__main__.py", line 19, in main
    cmd.main(command_args)
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/commands/run.py", line 122, in main
    not args.no_cache)
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/commands/run.py", line 53, in submit_job_to_terra
    alto.upload_to_google_bucket(inputs, workspace, False, bucket_folder, out_json)
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/commands/upload.py", line 180, in upload_to_google_bucket
    input_path, is_changed = transfer_sample_sheet(input_path, input_file_to_output_gsurl, gsurl_gen, dry_run)
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/commands/upload.py", line 140, in transfer_sample_sheet
    transfer_data(value, sub_gs_url, dry_run = dry_run, flowcells = flowcells)
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/commands/upload.py", line 106, in transfer_data
    transfer_flowcell(source, dest, dry_run, lanes)
  File "/projects/kamil/work/github.com/klarman-cell-observatory/altocumulus/alto/commands/upload.py", line 76, in transfer_flowcell
    assert os.path.exists('{0}/RTAComplete.txt'.format(source)) and os.path.exists('{0}/runParameters.xml'.format(source))
AssertionError

This will make some other jobs fail, as runParameters.xml is in the MiSeq output standard, while RunParameters.xml is in NextSeq.
I think the only way to fix this is to cover both cases.

Hi @slowkow,
Thanks for reporting! We have added test and upload for both runParameters.xml and RunParameters.xml.
Best,
Bo


M3-3681 Improve Graphs UX

M3-3681 Improve Graphs UX

if we use transparency on any bg color we get wrong superposition hex values
If we stack (or if we don’t) we need the order right to get to display the right things

By adding our own legend we lost an important feature of GraphJS, which is clicking on the legend to toggle the graphs. This PR adds this, remove the stacked option so now some lines may be hidden behind others, but with the option to toggle people may now see very small data on a relative scale, which is great.
I duplicated the styles from the MetricStyles in order to keep the legacy legend as this is more of a POC, but hopefully we can get rid of MetricDisplay if this is a go. I only replaced them in LinodeSummary
note: on LineGraph implementation, data and legendRows props must have the same data order in order to display in the right row.
Type of Change

Non breaking change ('update', 'change')

Note to Reviewers
I upgraded chartsjs which allowed us to remove the patch.
run yarn up to get the chartsjs update.

FWIW, I don't know if removing the patch was the right move.
Here's a screenshot I took on develop from 9:20AM EST time (but my timezone in Cloud is GMT):

And here's a screenshot on this branch from 9:22AM EST (but my timezone in Cloud is GMT):

So the issue here is that the second screenshot is not observing my timezone because it's not set to New_York, but still telling me the last stat in east coast time.

@Jskobos @martinmckenna reverted the bump version and re-added the patch for now to avoid introducing regressions to other charts and keep the time display timezone-accurate.
Also improved typing

Still getting some regressions from the x axis when showToday is true:
Here's develop branch:

And then this PR:

Looking good. The selectable legends work well.
I noticed a regression when selecting "Last 30 days" (or per-month) options on Linode Summary:


docs: Release graph-node v0.35.0 to Arbitrum-One and Ethereum-Mainnet indexers

Changes

Update suggested graph-node version to v0.35.0 for the Arbitrum-One and Ethereum-Mainnet protocol networks

Old, closing


upgrade gradle version  4.1.2 -> 7.4.2

@alphonse-va @KasemJaffer any updates, can you please merger this PR ?


publish / build release binary app

What are the steps to build the app to run w/out dotnet installed?
Normally you'd run:
dotnet publish -c Release -r win-x64 --self-contained
then click and run bin\Release\netcoreapp3.1\win-x64\crossplatdemo.exe
Running:
dotnet run in the crossplatdemo after doing a dotnet restore does work fine

ok it did finally startup, but closing and reopening still takes a few minutes. is there no way to make it start running faster?

Unless it is downloading CEF binaries, I do not see why it will take minutes to restart. Not my experience. I just timed a restart now - about 35 secs.
You can check to see your VS or VSC settings to see whether you are set to rebuild every time.


How to use the fast rcnn model?

How to use the fast rcnn model?
thank you！

Which Deep Learning engine you would like to use for FastRCNN? Any code to share?


Automate profiling dashboard generation

Description of changes:
What was changed?
Created a CF template to generate the profiling dashboard on Cloudwatch
Why was it changed?
To simplify the process of creating dashboards
How it was changed?
Added a template that would take in a label and dashboard name as parameter and generate the dashboard when the CF stack is deployed
Testing:
Tested on AWS account and verified the dashboard was indeed generated with the required metrics
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can we update the readme (somewhere) to let users know how to apply the cloud formation template, what it does, requirements, etc?

Can we update the readme (somewhere) to let users know how to apply the cloud formation template, what it does, requirements, etc?

Missed the README. My bad. Will update.


Workload identity doesn't appear to work with GKE SAs

I have created a k8s service account and added the annotations to it in order to bind it to a service account that has monitoring viewer, but when I try to save the configuration using the the default GCE account, it gives the error "missing credentials".
I'm assuming the support for workload identity only works on GCE instances, but maybe I'm doing something wrong?

n/m, I found the problem.


Update requirements.txt

As indicated in #1 kenlm is from github. scikit-learn is also needed.

Merged, thanks very much for this pull request!


Failure count

Track failures, abort right away if more than a certain number of consecutive failures in a backoff window.

Still needed?


Demo Extension : Generic dataset

Datasets should include
Projects
    Project questions should make sense
Products
Product Categories
Orders
Services
Wizard Questions
In general
    Use variable length Lorem ipsum text for descriptions. Something like one to 5 paragraphs should do.
    Tags for things should make sense
    Alerts for various objects
        Alerts should make sense and should not be assigned arbitrarily.
    Answers for various objects
        Answers should make sense and should not be assigned arbitrarily.

To Do List:

[x] Create new Rails plugin
[ ] Add "Generic" Compnents:

[ ] ProviderType
[ ] ProductType
[ ] Product
[ ] Project?
[ ] Service?
[ ] Provider
[ ] Product

[ ] Customize remaining products in dataset
[ ] Strip sample:demo dependencies from core

Closed by https://github.com/projectjellyfish/jellyfish-demo/pull/8.


feat: Could I make a call or webhook to chatwoot server to make it send a specific message when the user make certain action in the app?

@engmsaleh thanks for the feedback. We can expose methods to add labels or custom fields from the Flutter SDK. based on that you can configure automation in chatwoot dashboard .

@sojan-official thanks for the reply, Did this already done or still?

@engmsaleh  it isn't available yet. We will share further updates on this issue once we have someone working on it.


Self tests fail on postprocessors-> thumbnails

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.08.19 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Building yt-dlp from source using aur package yt-dlp-git, self-test sequence fails at test/test_postprocessors.py::TestConvertThumbnail::test_escaping, preventing correct instalation.
 As such, output of yt-dlp commands will be associated with last version that managed to build, instead of the one creating the issues.

My environment is able to pass this test
$ pytest test/test_postprocessors.py -k test_escaping
========================================= test session starts ==========================================
platform linux -- Python 3.9.13, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 --<EMAIL_ADDRESS>cachedir: .pytest_cache
rootdir: /home/lesmi/yt-dlp, configfile: setup.cfg
plugins: parallel-0.1.0, timeout-1.4.2
collected 55 items / 54 deselected / 1 selected

test/test_postprocessors.py::TestConvertThumbnail::test_escaping PASSED                          [100%]

=================================== 1 passed, 54 deselected in 0.76s ===================================

Probably ffmpeg in your environment can't handle webp files, since yt-dlp uses ffmpeg to convert thumbnails

Same issue as https://github.com/yt-dlp/yt-dlp/issues/4604

Issue with self-test, preventing further installation of yt-dlp.

You will need to talk to the package maintainer about skipping the test during installation if needed


Update promaster-tutorial.md

Requested by management to remove all mention of CUSTOM DOMAINS because they're not relevant to our new, rebranded product.

Hello all
I'd just like to confirm that the update is still pending a review, is this correct?
Regards
Chad
From: Courtney Wales @.>
Sent: Thursday, April 25, 2024 1:38 AM
To: MicrosoftDocs/entra-docs @.>
Cc: Chad Edwards @.>; Mention @.>
Subject: Re: [MicrosoftDocs/entra-docs] Update promaster-tutorial.md (PR #707)
@jeevansdhttps://github.com/jeevansd
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/entra-docs/pull/707#issuecomment-2075239626, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BG6J5HMWBOAI73SDSCFB5YTY67GUHAVCNFSM6AAAAABGWIBOBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVGIZTSNRSGY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, please notify the sender immediately.

Hi @chadinlogik, that's correct.
@jeevansd - Can you review the proposed changes to your article?

@Chadinlogik, we're creating a separate PR for this request in our private repo to avoid content validation errors, the changes will merge within 2-3 working days.
#please-close

Hi All
Just checking in on the below. Should I create a new request?
Regards
Chad
From: Courtney Wales @.>
Sent: Friday, May 3, 2024 12:19 AM
To: MicrosoftDocs/entra-docs @.>
Cc: Chad Edwards @.>; Mention @.>
Subject: Re: [MicrosoftDocs/entra-docs] Update promaster-tutorial.md (PR #707)
Hi @Chadinlogikhttps://github.com/Chadinlogik, that's correct.
@jeevansdhttps://github.com/jeevansd - Can you review the proposed changes to your article?

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/entra-docs/pull/707#issuecomment-2090614585, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BG6J5HLAZJYAJ5PY2LQJAFDZAJDPDAVCNFSM6AAAAABGWIBOBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQGYYTINJYGU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error, please notify the sender immediately.

@Chadinlogik, It was already updated as per the request, please check the article again and let us know-


basic operations documentation

In GitLab by @franzi233 on Aug 18, 2021, 10:50
Finish documentation of how to do the basic operations on the nodes.

In GitLab by @franzi233 on Aug 18, 2021, 10:50
assigned to @franzi233

In GitLab by @franzi233 on Aug 18, 2021, 10:50
marked this issue as related to #1


[FLINK-15067][table] Pass configuration to the underlying ExecutionEnvironment from TableEnvironment

What is the purpose of the change
After this PR the TableEnvironment passes configuration to the underlying StreamExecutionEnvironment. It allows configuring options such as e.g. autoWatermarkInterval, globalJobParameters etc.
It is possible to do it as follows:
StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment();
StreamTableEnvironment tEnv = StreamTableEnvironment.create(env);
	tEnv.getConfig().addConfiguration(
		new Configuration()
			.set(CoreOptions.DEFAULT_PARALLELISM, 128)
			.set(PipelineOptions.AUTO_WATERMARK_INTERVAL, Duration.ofMillis(800))
			.set(ExecutionCheckpointingOptions.CHECKPOINTING_INTERVAL, Duration.ofSeconds(30))
	);

Verifying this change
Added tests for blink and flink planners
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

This looks good, once Travis is green!
I had one comment, but it's more for my understanding.

@aljoscha Could you have another look?
@sunjincheng121 Could you have a look at the python part? This is not the perfect solution as users can override the pipeline.global-job-parameters setting. I created https://issues.apache.org/jira/browse/FLINK-15096 to track improving that.

Hi @dawidwys, We should rebase the code when merging this PR if the #10477 merge first.  It seems the we do not need the Python changes in this PR anymore.
Best,
Jincheng


HTTPS_re-encrypt test flake

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/46553/integ-pilot-multicluster_istio/1691782056792559616
We create a SIMPLE DR, but the EDS still shows cross-network endpoints: https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio/46553/integ-pilot-multicluster_istio/1691782056792559616/artifacts/pilot-989dd9a91575412f97742d3ec/TestTraffic/gateway/HTTPS_re-encrypt/to_b.echo/from_cross-network-primary/_test_context/istio-state31148159/cross-network-primary/istio-ingressgateway-54486f7956-mf6v2_proxy-config.json
Not sure why, at first glance code looks ok. Maybe a caching issue. cc @stevenctl

https://github.com/istio/istio/blob/93758c226683acea24867e365386ab4da567444f/pilot/pkg/xds/endpoints/mtls_checker.go#L52-L60
SIMPLE doesn't affect the filtering.

huh, I skipped right over that.
It should, right?

I'm pretty sure we can support this if SIMPLE still sends the correct SNI and the server is permissive.

I think it needs the Istio ALPN as well which we shouldn't be setting for SIMPLE.

Or MUTUAL for that matter right?


Support rlp==0.4.7

Version: 3.7.2
Python: 2.7
OS: osx

What was wrong?
https://github.com/ethereum/pydevp2p requires rlp==0.4.7 (here), but web3.py requires rlp>=0.4.6,<0.4.7. This causes headaches when a project requires both packages as well as rlp independently.
I've created a repo with updated requirements here: https://github.com/karlfloersch/web3.py, but I haven't verified that everything is working properly.
Cute Animal Picture

Thank you!

3.8.0 is now available which now pins rlp>=0.4.7.  If you are also using eth-testrpc you should update to 1.2.0 as well.

Awesome thank you! 😄


Error: global leak detected in chrome

Hi,
running the example found at https://github.com/adomokos/mocha-in-browser.git that is a simple mocha setup in browser.
http://sandbox.dev/mocha-in-browser/spec/runner.html run fine in safari and firefox but generate an error in chrome...
Error: global leak detected: script1339717561999     at Runner.checkGlobals (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3139:21)     at Runner.<anonymous> (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3054:44)     at Runner.emit (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:235:20)     at http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3360:14     at Test.run (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3003:5)     at Runner.runTest (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3305:10)     at http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3349:12     at next (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3233:14)     at http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3242:7     at next (http://sandbox.dev/mocha-in-browser/spec/lib/mocha.js:3192:23)
this error shows on the first test that is fired (if you comment out the first one, the second generates the error)

I think @bentruyman might be right. I wasn't able to reproduce the issue after cloning and running https://github.com/adomokos/mocha-in-browser.git

Closing this for now, since it's been a couple years since the last reply. Feel free to re-open and provide additional details if this still happens.
Thanks!


our own not-imported geographic classes should be deleted

Description of the issue
I'd like to delete the GeographicRegion classes for now as they'll be externally replaced:

AdditionalToAdress, City, Continent, Country, FederalState, LoadArea, Sea, Land, Ocean

Ideas of solution

delete them

Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[x] I already read the latest version of the workflow for this repository
[x] The goal of this ontology is clear to me

I am aware that

[x] every entry in the ontology should have an annotation
[x] classes should arise from concepts rather than from words
[x] class or property names should follow the UpperCamelCase

also delete: GeographicCoordinate, duplicate of cartesian spatial coordinate item
(see definition sheet)

I am no expert for the geography topics. Maybe @han-f or @christian-rli have an opinion?

I think I suggested deleting GeographicCoordinate in our last ontology meeting, so I'm in favour of that.
As to the GeographicRegion classes, it's dfficult for me to assess the right approach from an ontology perspective, but from what I've learned about geo-ontologies is that they are a already a big field, so better to adapt to something that others already found reasonable than create our own.


Not able to communicate with mock server from app when mock server is in secure comunication(https)

HI,
ngapimock is  hosted/running in express server over https, by refering the below link im able to up mockserver in https.
https://timonweb.com/posts/running-expressjs-server-over-https/
But after that not able to connect to mockserver while runnig protractor tests . getting error
Ignoring uncaught error Error: socket hang up
App is able to communicate to the real backend with https and by default it communicates through https. but only with mock, its throwing error
below is the error log:
a7a509ef-ad2a-4da1-840f-c8c5e8ff669f
selectScenario: user/me : a7a509ef-ad2a-4da1-840f-c8c5e8ff669f
selectScenario: employee/{code}/ : a7a509ef-ad2a-4da1-840f-c8c5e8ff669f
[09:43:47] W/launcher - Ignoring uncaught error Error: socket hang up
[09:43:47] W/launcher - Ignoring uncaught error Error: socket hang up
[09:43:50] W/launcher - Ignoring uncaught error UnableToSetCookieError: unable to set cookie
(Session info: chrome=77.0.3865.120)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'TVMLT0558', ip: '<IP_ADDRESS>', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_221'
Driver info: driver.version: unknown
[09:43:50] W/launcher - Ignoring uncaught error Error: socket hang up
[09:43:54] I/launcher - 0 instance(s) of WebDriver still running
[09:43:54] I/launcher - chrome #01 failed 1 test(s)
[09:43:54] I/launcher - overall: 1 failed spec(s)
[09:43:54] E/launcher - Process exited with error code 1
[09:43:54] gulp-angular-protractor - We will stop the Protractor engine
[09:43:57] gulp-angular-protractor - Webdriver standalone server will be closed
Java terminated  SUCCESS: The process "java.exe" with PID 124396 has been terminated.

@lakshmi-236 can you provide a dummy setup so I can have a look?

@lakshmi-236 ng-apimock has a new version, which is modular.
I have just released a new version of the base-client (1.0.15) that supports https.
Please let me know if you run into any problems


Lookup: Add Variants to Key-based

As we've tried to use Key lookups it has become clear that it needs the same variant matching capability as extracts. Otherwise, the user has to create and maintain an equivalent extract and run it before the lookup.   Seems like it might be easy to add using our exsiting code.

After our discussion yesterday (July 1), seems like we should try to make it easy to keep an Extract-Lookup pair in sync vs briing over all of the extract functionality. So for now let's drop this for now.


Documentation enhancements

https://github.com/purescript-contrib/purescript-js-bigints/issues/11

Thank you too !


java and c#: can incompletely implement abstract class

:bug: Bug Report
In this code:
https://github.com/rix0rrr/jsii-test-drive/blob/master/java/extends-abstract-class/src/main/java/com/myorg/MyCode.java
The subclass of Code is not complete. It is missing an implementation of public abstract readonly isInline: boolean.
This class should have been needed to be marked abstract, but it it isn't.

This feels wrong-- the abstract-ness of a member should be mirrored into the JSII bindings.

Same problem affecting c# - https://github.com/rix0rrr/jsii-test-drive/blob/master/dotnet/serverless/src/Serverless/Program.cs

Accessing the "abstract" member results in a predictable JSII exception:
Unhandled exception. Amazon.JSII.Runtime.JsiiException: Got 'undefined' for non-optional instance of {"abstract":true,"docs":{"stability":"stable","summary":"The name of the function."},"immutable":true,"locationInModule":{"filename":"lib/function-base.ts","line":148},"name":"functionName","overrides":"@aws-cdk/aws-lambda.IFunction","type":{"primitive":"string"}}
   at Amazon.JSII.Runtime.Services.Client.TryDeserialize[TResponse](String responseJson)
   at Amazon.JSII.Runtime.Services.Client.ReceiveResponse[TResponse]()
   at Amazon.JSII.Runtime.Services.Client.Send[TRequest,TResponse](TRequest requestObject)
   at Amazon.JSII.Runtime.Services.Client.Get(GetRequest request)
   at Amazon.JSII.Runtime.Services.Client.Get(ObjectReference objectReference, String property)
   at Amazon.JSII.Runtime.Deputy.DeputyBase.<>c__DisplayClass9_0`1.<GetInstanceProperty>b__0(IClient client)
   at Amazon.JSII.Runtime.Deputy.DeputyBase.GetPropertyCore[T](JsiiPropertyAttribute propertyAttribute, Func`2 getFunc)
   at Amazon.JSII.Runtime.Deputy.DeputyBase.GetInstanceProperty[T](String propertyName)
   at Amazon.CDK.AWS.Lambda.FunctionBase.get_FunctionName()
   at Serverless.Program.Main(String[] args) in /Users/nija/workplace/cdk/jsii-test-drive/dotnet/serverless/src/Serverless/Program.cs:line 36

This is actually a duplicate of #240


eloquent  with closure exec builder select

when i use select, it can't return anything. like this

return  file_lists empty

i solve it


Remove deferred anti-pattern

http://stackoverflow.com/questions/23803743/what-is-the-explicit-promise-construction-antipattern-and-how-do-i-avoid-it/23803744#23803744

You're changing the original promise which we would rather pass through.
Have a look at the v2 branch for an alternative solution to this problem.

Whenever you then a promise you're already returning a new promise. You're not "passing through" anyway when you return new Promise.

I understand the crux of your argument, and while I would agree in other cases, I'm not sure the deferred promise anti-pattern would apply here.
I would remember promises are state machines (that is, complex objects that hold a state).
Here, the promise returned by the request function holds the the state of one HTTP request. There are four possible outcomes (or "settled") states for this promise:

Rejected: the server sent an erroneous response
Rejected: the request is missing url parameter
Rejected: the request is missingoptions parameter
Fulfilled: the server sent a successful, 200 OK, response

Currently, the request function returns one promise that can vary to describe each of these outcomes.
You have proposed that the request function should return one of three promises, each describing a different outcome. To break this down:
// possible Promise #1 that could be returned
if (!url) return Promise.reject(...)

) // possible Promise #2 that could be returned
if (!options) return Promise.reject(...)

// possible Promise #3  that could be returned
return fetch(...)

With this proposed change, the promise doesn't describing the state of the entire request, but rather, parts of the request.

In the end, I don't really see one as being objectively better than the other, but in terms of syntax and my mental model of the code, I would prefer the original solution.
And for what it's worth, this is just an example. There is a lot of code missing that one might normally use in production.

Whenever you then a promise you're already returning a new promise. You're not "passing through" anyway when you return new Promise.

I'm not saying anything contrary to this. Also I pointed out the v2 branch for an alternative solution but I guess you didn't going from what you said.

I'm not sure the deferred promise anti-pattern would apply here.

It definitely does. You're wrapping a promise with another promise manually and manually taking care of all edge cases.

You have proposed that the request function should return one of three promises, each describing a different outcome. To break this down

A promise itself is just the value it resolves to. The fact it's "three different promises" is mostly irrelevant.

In the end, I don't really see one as being objectively better than the other

Your library - your call. I'd probably opt for:
export default async (url, options) => {
  if(!url) throw new Error("URL parameter required")
  if(!options) throw new Error("Options parameter required")
  const response = await fetch(url, options).then(x => x.json());
  if(response.errors) throw response.errors; // todo: wrap in real error
  return response;
};

@pburtchaell hey was this fixed?


Inverse operation for CALL sqlite_attach(db_name)

There doesn't appear to be any documented way to detach a SQLite database from DuckDB CLI that was attached using CALL sqlite_attach(db_name)

There is indeed none at the moment

The new ATTACH syntax has a corresponding DETACH. We won't implement an inverse for sqlite_attach as it is mostly kept around for backwards compatibility reasons at this point.