TurbSim Problem

hello everyone,
I found that the TurbSim V2.0  can support the user  time series.  I have  mearsured 9 Node data in the rotor plane around the complex nature by LIDAR  like below
Node7  10.8m/s-------------Node8  11.5m/s------------Node9  12.5m/s
Node4  9.6m/s----------------Node5  12.18m/s---------Node6  10.5m/s
Node1  9.5m/s----------------Node2  4.5m/s-------------Node3  0.2m/s
the data show the mean wind speed ,the first line represent the rotor top and last line is the rotor  bottom .
TurbSim didn't work  and some errors occurred when I input the measured data except we delete the Node2 and Node3.  I think the two nodes data can affect the coherence matrix.
There are a small mountain (Node2,Node1)before the turbine .I want to produce the similar turbulence wind like measured.
Could the Turbsim get the wind file like that, or how to fix the coherence parameters to meet the condition?
Hope your reply!
Best Regard!

Dear @RuiliangWang,
So, what error(s) did you receive?
The user time-series option of TurbSim does not derive the coherence from the specified user time series (although TurbSim does derive the mean wind profile and the wind spectra at each height by the specified user time series).  Instead, you must choose which user-time series point is used to establish the wind at other points in the wind domain bsaed on the internal coherence model.
Best regards,

Dear Jason
The error like below

C:\Users\Chinawindey>D:\Turbsim\simulation\TurbSim_x64.exe D:\Turbsim\simulation\UserTimeSeries.inp
Running TurbSim (v2.00.07a-bjj, 14-Jun-2016).
Reading the input file "D:\Turbsim\simulation\UserTimeSeries.inp".
Reading the user-defined time-series input file "D:\Turbsim\simulation\Test2.TimeSer".
Found 12000 lines of time-series data.
Calculating the spectral and transfer function matrices:
u-component matrices (general coherence model)
CalcFourierCoeffs:CalcFourierCoeffs_General:Error in Cholesky factorization: LAPACK_SPPTRF:
Leading minor order           21 of A is not positive definite, so Cholesky factorization could
not be completed.
The error occurred in the u-component coherence matrix at frequency 1 (1.66667E-03 Hz) Check the
input file for invalid physical properties or modify the coherence.
Aborting TurbSim.

My time series is below:
--------------TurbSim v2.00.* User Time Series Input File-----------------------
Time series input from Y:/wind/windweb/MetData/135mData/M4Twr/20Hz/mat/2014/01/13/01134_16_40_00_013.mat. Using rotated series
--------------------------------------------------------------------------------
          3  nComp    - Number of velocity components in the file (1=u component only; 2=u & v components; 3=u,v,w) [if < 3 other components will be generated using values from input file]
          5  nPoints  - Number of time series points contained in this file (-)
          2  RefPtID  - Index of the reference point (1-nPoints)
Pointyi     Pointzi    ! listed in order of increasing height
  (m)         (m)
    59.00000    22.00000
    -59.00000    22.00000
    0.00000    80.00000
    59.00000    137.00000
    -59.00000   137.00000  !    0.00000   131.00000
--------Time Series-------------------------------------------------------------
 Elapsed Time     Point01u_015m Point01v_015m Point01w_015m Point02u_030m Point02v_030m Point02w_030m Point03u_050m Point03v_050m Point03w_050m Point04u_076m Point04v_076m Point04w_076m Point05u_100m Point05v_100m Point05w_100m Point06u_131m Point06v_131m Point06w_131m
          (s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)         (m/s)
0	8.05E+00	1.75E+00	1.75E+00	2.72E-01	3.02E-02	3.02E-02	1.28E+01	1.42E+00	1.42E+00	1.05E+01	2.00E+00	2.00E+00	1.19E+01	1.80E+00	1.80E+00
0.05	8.11E+00	1.77E+00	1.77E+00	2.71E-01	3.05E-02	3.05E-02	1.28E+01	1.58E+00	1.58E+00	1.06E+01	2.05E+00	2.05E+00	1.19E+01	1.86E+00	1.86E+00
0.1	8.13E+00	1.80E+00	1.80E+00	2.70E-01	3.04E-02	3.04E-02	1.29E+01	1.80E+00	1.80E+00	1.07E+01	2.05E+00	2.05E+00	1.19E+01	1.83E+00	1.83E+00
0.15	8.09E+00	1.79E+00	1.79E+00	2.69E-01	3.08E-02	3.08E-02	1.30E+01	1.98E+00	1.98E+00	1.06E+01	1.89E+00	1.89E+00	1.22E+01	1.59E+00	1.59E+00
0.2	8.20E+00	1.72E+00	1.72E+00	2.68E-01	3.10E-02	3.10E-02	1.28E+01	2.08E+00	2.08E+00	1.06E+01	1.73E+00	1.73E+00	1.22E+01	1.65E+00	1.65E+00
0.25	8.33E+00	1.68E+00	1.68E+00	2.68E-01	3.02E-02	3.02E-02	1.29E+01	2.11E+00	2.11E+00	1.06E+01	1.68E+00	1.68E+00	1.21E+01	1.75E+00	1.75E+00
0.3	8.47E+00	1.67E+00	1.67E+00	2.70E-01	3.07E-02	3.07E-02	1.31E+01	2.11E+00	2.11E+00	1.06E+01	1.67E+00	1.67E+00	1.20E+01	1.67E+00	1.67E+00
0.35	8.26E+00	1.83E+00	1.83E+00	2.70E-01	3.11E-02	3.11E-02	1.32E+01	2.09E+00	2.09E+00	1.06E+01	1.72E+00	1.72E+00	1.20E+01	1.54E+00	1.54E+00
0.4	8.22E+00	1.86E+00	1.86E+00	2.67E-01	3.10E-02	3.10E-02	1.31E+01	2.17E+00	2.17E+00	1.07E+01	1.86E+00	1.86E+00	1.21E+01	1.48E+00	1.48E+00
0.45	8.33E+00	1.76E+00	1.76E+00	2.66E-01	3.00E-02	3.00E-02	1.30E+01	2.29E+00	2.29E+00	1.06E+01	1.65E+00	1.65E+00	1.20E+01	1.60E+00	1.60E+00
0.5	8.26E+00	2.07E+00	2.07E+00	2.64E-01	2.96E-02	2.96E-02	1.30E+01	2.41E+00	2.41E+00	1.04E+01	1.51E+00	1.51E+00	1.18E+01	1.71E+00	1.71E+00
0.55	8.29E+00	2.16E+00	2.16E+00	2.61E-01	3.00E-02	3.00E-02	1.31E+01	2.23E+00	2.23E+00	1.03E+01	1.51E+00	1.51E+00	1.17E+01	1.89E+00	1.89E+00
0.6	8.38E+00	2.10E+00	2.10E+00	2.60E-01	3.06E-02	3.06E-02	1.31E+01	2.25E+00	2.25E+00	1.04E+01	1.73E+00	1.73E+00	1.17E+01	2.14E+00	2.14E+00
0.65	8.42E+00	2.19E+00	2.19E+00	2.59E-01	3.14E-02	3.14E-02	1.33E+01	2.36E+00	2.36E+00	1.04E+01	1.80E+00	1.80E+00	1.18E+01	2.24E+00	2.24E+00
0.7	8.42E+00	2.45E+00	2.45E+00	2.60E-01	3.24E-02	3.24E-02	1.35E+01	2.39E+00	2.39E+00	1.05E+01	1.75E+00	1.75E+00	1.19E+01	2.45E+00	2.45E+00
0.75	8.38E+00	2.71E+00	2.71E+00	2.60E-01	3.28E-02	3.28E-02	1.35E+01	2.38E+00	2.38E+00	1.04E+01	1.77E+00	1.77E+00	1.19E+01	2.75E+00	2.75E+00
0.8	8.33E+00	2.49E+00	2.49E+00	2.60E-01	3.28E-02	3.28E-02	1.34E+01	2.37E+00	2.37E+00	1.03E+01	1.78E+00	1.78E+00	1.18E+01	2.70E+00	2.70E+00
0.85	8.19E+00	2.52E+00	2.52E+00	2.60E-01	3.27E-02	3.27E-02	1.35E+01	2.45E+00	2.45E+00	1.03E+01	1.78E+00	1.78E+00	1.19E+01	2.56E+00	2.56E+00
0.9	8.02E+00	2.56E+00	2.56E+00	2.61E-01	3.36E-02	3.36E-02	1.35E+01	2.44E+00	2.44E+00	1.05E+01	1.77E+00	1.77E+00	1.20E+01	2.40E+00	2.40E+00
0.95	7.86E+00	2.35E+00	2.35E+00	2.62E-01	3.33E-02	3.33E-02	1.34E+01	2.43E+00	2.43E+00	1.05E+01	1.64E+00	1.64E+00	1.19E+01	2.66E+00	2.66E+00
1	8.06E+00	2.27E+00	2.27E+00	2.62E-01	3.26E-02	3.26E-02	1.32E+01	2.42E+00	2.42E+00	1.05E+01	1.45E+00	1.45E+00	1.18E+01	2.69E+00	2.69E+00

I use the node1,node3,node5,node7,node9. Did I set the parameter wrong or the time series uncorrect?
the first input file :
---------TurbSim v2.00.* Input File------------------------
for user-defined time series input
---------Runtime Options-----------------------------------
False         Echo            - Echo input data to <RootName>.ech (flag)
      43456   RandSeed1       - First random seed  (-2147483648 to<PHONE_NUMBER>)
"RanLux"      RandSeed2       - Second random seed (-2147483648 to<PHONE_NUMBER>) for intrinsic pRNG, or an alternative pRNG: "RanLux" or "RNSNLW"
False         WrBHHTP         - Output hub-height turbulence parameters in binary form?  (Generates RootName.bin)
False         WrFHHTP         - Output hub-height turbulence parameters in formatted form?  (Generates RootName.dat)
False         WrADHH          - Output hub-height time-series data in AeroDyn form?  (Generates RootName.hh)
False          WrADFF          - Output full-field time-series data in TurbSim/AeroDyn form? (Generates RootName.bts)
True         WrBLFF          - Output full-field time-series data in BLADED/AeroDyn form?  (Generates RootName.wnd)
False         WrADTWR         - Output tower time-series data? (Generates RootName.twr)
False         WrFMTFF         - Output full-field time-series data in formatted (readable) form?  (Generates RootName.u, RootName.v, RootName.w)
False         WrACT           - Output coherent turbulence time steps in AeroDyn form? (Generates RootName.cts)
False         Clockwise       - Clockwise rotation looking downwind? (used only for full-field binary files - not necessary for AeroDyn)
          0   ScaleIEC        - Scale IEC turbulence models to exact target standard deviation? [0=no additional scaling; 1=use hub scale uniformly; 2=use individual scales]

--------Turbine/Model Specifications-----------------------
          17   NumGrid_Z       - Vertical grid-point matrix dimension
          17   NumGrid_Y       - Horizontal grid-point matrix dimension
       0.05   TimeStep        - Time step [seconds]
        600   AnalysisTime    - Length of analysis time series [seconds] (program will add time if necessary: AnalysisTime = MAX(AnalysisTime, UsableTime+GridWidth/MeanHHWS) )
"ALL"         UsableTime      - Usable length of output time series [seconds] (program will add GridWidth/MeanHHWS seconds unless UsableTime is "ALL")
         80   HubHt           - Hub height [m] (should be > 0.5*GridHeight)
         119   GridHeight      - Grid height [m]
         119   GridWidth       - Grid width [m] (should be >= 2*(RotorRadius+ShaftLength))
          0   VFlowAng        - Vertical mean flow (uptilt) angle [degrees]
          0   HFlowAng        - Horizontal mean flow (skew) angle [degrees]

--------Meteorological Boundary Conditions-------------------
"TIMESR"      TurbModel       - Turbulence model ("IECKAI","IECVKM","GP_LLJ","NWTCUP","SMOOTH","WF_UPW","WF_07D","WF_14D","TIDAL","API","USRINP","TIMESR", or "NONE")
"Test2.TimeSer"    UserFile        - Name of the file that contains inputs for user-defined spectra or time series inputs (used only for "USRINP" and "TIMESR" models)
          1   IECstandard     - Number of IEC 61400-x standard (x=1,2, or 3 with optional 61400-1 edition number (i.e. "1-Ed2") )
"C"           IECturbc        - IEC turbulence characteristic ("A", "B", "C" or the turbulence intensity in percent) ("KHTEST" option with NWTCUP model, not used for other models)
"NTM"         IEC_WindType    - IEC turbulence type ("NTM"=normal, "xETM"=extreme turbulence, "xEWM1"=extreme 1-year wind, "xEWM50"=extreme 50-year wind, where x=wind turbine class 1, 2, or 3)
"default"     ETMc            - IEC Extreme Turbulence Model "c" parameter [m/s]
"default"     WindProfileType - Velocity profile type ("LOG";"PL"=power law;"JET";"H2L"=Log law for TIDAL model;"API";"USR";"TS";"IEC"=PL on rotor disk, LOG elsewhere; or "default")
"unused"      ProfileFile     - Name of the file that contains input profiles for WindProfileType="USR" and/or TurbModel="USRVKM" [-]
         80   RefHt           - Height of the reference velocity (URef) [m]
      10   URef            - Mean (total) velocity at the reference height [m/s] (or "default" for JET velocity profile) [must be 1-hr mean for API model; otherwise is the mean over AnalysisTime seconds]
        350   ZJetMax         - Jet height [m] (used only for JET velocity profile, valid 70-490 m)
"default"     PLExp           - Power law exponent [-] (or "default")
"default"     Z0              - Surface roughness length [m] (or "default")

--------Non-IEC Meteorological Boundary Conditions------------
"default"     Latitude        - Site latitude [degrees] (or "default")
       0.05   RICH_NO         - Gradient Richardson number [-]
"default"     UStar           - Friction or shear velocity [m/s] (or "default")
"default"     ZI              - Mixing layer depth [m] (or "default")
"default"     PC_UW           - Hub mean u'w' Reynolds stress [m^2/s^2] (or "default" or "none")
"default"     PC_UV           - Hub mean u'v' Reynolds stress [m^2/s^2] (or "default" or "none")
"default"     PC_VW           - Hub mean v'w' Reynolds stress [m^2/s^2] (or "default" or "none")

--------Spatial Coherence Parameters----------------------------
"default"     SCMod1           - u-component coherence model ("GENERAL","IEC","API","NONE", or "default")
"default"     SCMod2           - v-component coherence model ("GENERAL","IEC","NONE", or "default")
"default"     SCMod3           - w-component coherence model ("GENERAL","IEC","NONE", or "default")
"5.310901, 0.000341"    InCDec1          - u-component coherence parameters for general or IEC models [-, m^-1] (e.g. "10.0  0.3e-3" in quotes) (or "default")
"2.638217, 0.001692"    InCDec2          - v-component coherence parameters for general or IEC models [-, m^-1] (e.g. "10.0  0.3e-3" in quotes) (or "default")
"1.633211, 0.005484"    InCDec3          - w-component coherence parameters for general or IEC models [-, m^-1] (e.g. "10.0  0.3e-3" in quotes) (or "default")
          0   CohExp           - Coherence exponent for general model [-] (or "default")

--------Coherent Turbulence Scaling Parameters-------------------
".\EventData"    CTEventPath     - Name of the path where event data files are located
"les"         CTEventFile     - Type of event files ("LES", "DNS", or "RANDOM")
true          Randomize       - Randomize the disturbance scale and locations? (true/false)
          1   DistScl         - Disturbance scale [-] (ratio of event dataset height to rotor disk). (Ignored when Randomize = true.)
        0.5   CTLy            - Fractional location of tower centerline from right [-] (looking downwind) to left side of the dataset. (Ignored when Randomize = true.)
        0.5   CTLz            - Fractional location of hub height from the bottom of the dataset. [-] (Ignored when Randomize = true.)
         10   CTStartTime     - Minimum start time for coherent structures in RootName.cts [seconds]

====================================================
! NOTE: Do not add or remove any lines in this file!
====================================================

Best Regards!

Dear @RuiliangWang,
An error in the Cholesky factorization results from having too high (i.e., unphysical) coherence.
Just a few comments/questions:

Is there a reason you set RefPtID = 2 (near the corner of the grid)?  I would normally recommend deriving the spatial coherence from a user time-series point near the center of the grid (in this case, RefPtID = 3).
When TurbModel = TIMESR, the coherence model defaults to GENERAL, which means the user-specified values of InCDec1-3 are used.  How did you derive/set the values of InCDec1-3?
The GENERAL coherence model of TurbSim was changed in OpenFAST...see: https://github.com/OpenFAST/openfast/pull/104.  So, I would recommend using TurbSim from OpenFAST v2.1 to see if your problem is resolved with the newest version of TurbSim.

Best regards,

Dear Jason,
I have recompiled the TurbSim from OpenFAST ,It worked ,But the result make me confused.
The input five actual wind speed curve like below:

The Red curve shows the Node3; the result .wnd file show the wind speed of five  point like below

The node3 wind speed between the input and output have so large difference.  That means .wnd file  can not represent the actual wind speed in the Node3.
Can you give me some advices about how to  get the actural wind speed like Node3 ?
Best Regrads!

Dear @RuiliangWang,
My understanding is the top plot corresponds to your five user-specified time series and the bottom plot is the output created by TurbSim...is that correct?
Do you mean that the red curve in the top plot is user-specified point 2 (not 3)?  Why does the red curve differ so much from the other four?
Which of these five points are you using as the reference point for coherence (RefPtID = ?)  I would guess you are using point 3 (Y=0,Z=80) because the turquoise blue curve (0,78.3499), which is very close to point 3, have very similar time series...is that correct?
The coherence on the TurbSim-calculated grid points is only derived from one of the user-specified time series points (corresponding to RefPtID).  If you have other user-specified time series, the wind at the TurbSim-calculated grid points will not necessarily be coherent to those.
Best regards,

Point 3 (what you are calling node5) should be the exact time series entered because it is defined at (0m,80m), which is exactly on a point on TurbSim's output grid. This does not depend on which point is used as the reference for the coherence model. The other 4 points that you have specified don't actually land on TurbSim's output grid, so they will be used only to determine the wind profile (mean wind speed/direction). These wind profiles depend only on height, so it will use averaged values where you have defined multiple values per height.
Since you've specified point 2 (node3) as the reference point, TurbSim is using its phases to add coherence to the other simulated points on the grid (not point 3). I am a little confused about the position labels on your time series since those don't seem to align with what your input file would indicate are the locations of TurbSim grid points.
If you want all 5 of your measurement points on the TurbSim grid, you will have to adjust the position locations or adjust the TurbSim grid specification so that the measurement points align with the regular grid that TurbSim outputs.

Dear @jjonkman and @bjonkman
Thank you for your relpy in time.
I want to explain why the Node3  is different with the the other Nodes. Our  real turbine was set up in the complex terrain. The main direction of the wind was blocked by the mountain in front of the turbine. So the Node 3 was affect so largely.
I have adujst the Nodes position to align the turbSim grids . But the point 2(Node 3) is not what I input. The wind profile  looks not right.
The node1 and Node3 have same height ,But mean wind speed is different. I can not  get the real  wind  in  the two Nodes about same height. They  always have same mean wind speed  if the two point  have same height because of the wind profile in z dircetion .
Could the TurbSim  get  the diffenert  mean wind speed in the same height?
I have upload my files .Please help me to check the file if you are free.
simulation.zip
Best Regards

The current implementation of TurbSim uses a velocity profile that is only a function of height. It does not take the lateral position into account. If you are using the time-series wind profile, and you have specified two points at the same height, the profile will depend on the order that those points are entered. It linearly interpolates between adjacent heights, but doesn't check if there are multiple points at the same height. So, if you had entered node 3 before node 1, then the mean for node 1 would be off, while the mean for node 3 would be okay.
Having 2D wind profiles is something you could add if you wanted to, though.

Thank you very much ,It is helpful.


ci: Add fixes for upload script

Attaching the standalone client needs to happen on main runs, like the other clients
GitHub can't seem to find the release. I suspect the GITHUB_REPOSITORY var is unneeded.

Looks like it's working now:
https://github.com/firezone/firezone/actions/runs/12536649718

Spoke too soon. Need to debug further.

Issue was it needed contents: write permissions on the github token.


reorg docs

as titled.

Codecov Report

Merging #2407 (2e00662) into main (b0f7323) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2407   +/-   ##
=======================================
  Coverage   39.95%   39.95%
=======================================
  Files          88       88
  Lines        9757     9757
=======================================
  Hits         3898     3898
  Misses       5859     5859

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 dab0741...2e00662. Read the comment docs.


Update Management

Scenario which you are working on
Trying to create update management for the Azure Arc Server to perform patching using update management using the below link:  https://azurearcjumpstart.io/azure_arc_jumpstart/azure_arc_servers/day2/arc_updatemanagement/
Describe the bug
was able to deploy update management on a test Azure Arc ON-Perm Server but the Runbooks, Log analytics solutions didn't get created even though the automation account, Log Analytics workspace got created successfully, also deployment says successful.
To Reproduce
Steps to reproduce the behavior:

clone the azure arc repository
open the Azure CLI and cd to the azure_Arc_Servers_Jumpstart\updateManagement folder
execute az deployment group create --resource-group  --template-file law-template.json --parameters law-template.parameters.json
See error

Expected behavior
As per the documentation I did expected to see the runbooks and the update management solution mentioned in the documentation link https://azurearcjumpstart.io/azure_arc_jumpstart/azure_arc_servers/day2/arc_updatemanagement/ after successful deployment.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
as the update management solution is not available i was not able to move to the next steps in the documentation, please provide troubleshooting steps.

@vparna can you please provide some details:
What Azure region are you using?
Provide the error message from the deployment where the Update Management solution is failing.

i am currently using West US 2 region., i dont see any error message on the Azure portal or on the Azure CLI command prompt. the deployment succeeded but the runbooks, update management solutions aren't created in the resource group.

If the deployment is succeeding and not showing any error, then the resources should be created including the Update Management solution.
Is the resource group where your Azure Arc-enabled server resides the same resource group you are using to deploy the law-template.json from the Update Management scenario?

I was able to reproduce this. I will update the thread when I understand the root cause and have a fix.

This has been addressed. Note that in the updated version, the runbooks are no longer deployed with the template as they are not necessary for the scenario.

thank you for the updating the documentation. but I don't see the log Analytics solution created. can you check ?

There is a screenshot in this link that shows the Log Analytics workspace, automation account, and update management solution.
https://azurearcjumpstart.io/azure_arc_jumpstart/azure_arc_servers/day2/arc_updatemanagement/


not supported srv 2022: 10.0.20348.380

Same

same here, that would be nice.. if srv 2022 got be supported!! Needed

Supported https://github.com/sebaxakerhtc/rdpwrap.ini/commit/19e5361c58372d4158ba1299a21c650704cdceaf


feature request: nav links on the left

What problem does this feature solve?
Position the sidebar links on the left.
What does the proposed API look like?
// .vuepress/config.ts
export default {
    nav: [
      { text: "Left1", link: "/guide/api-page", position: "left" },
      { text: "Left2", link: "/guide/configuration", position: "left" },
    ],
 }

How should this be implemented in your opinion?
N/A
Are you willing to work on this yourself?
Yes

closed by https://github.com/piajs/vt/pull/74


[BEAM-1218] Move google specific io clients to vendor directory.

R; @sb2nov

LGTM, thanks.

Coverage increased (+0.003%) to 69.197% when pulling 219254961e7a1425a5888a2fff4a541ab020ab42 on aaltay:beam into 01de255753f5417b7241e8c883ca26b51dfaf6f5 on apache:master.

Coverage increased (+0.003%) to 69.197% when pulling 219254961e7a1425a5888a2fff4a541ab020ab42 on aaltay:beam into 01de255753f5417b7241e8c883ca26b51dfaf6f5 on apache:master.


feat(placeholder): add placholder component and service

update modal.service to use placeholder.service
update dialog.service to use placeholder.service
add BaseModal and deprecate @Modal
add deprecation notices to modal-placeholder and dialog-placeholder

closes #22

It's the type, you'd still name the variable placeholder: PlaceholderService and keep the naming consistent.

Yeah I know, but then that's breaking the service injection convention

I don't understand why we need to deviate from our conventions in this case at all. What makes this so special?

It's really not ... I just wasn't satisfied with the XService naming ... it's PlaceholderService now though


opensnitch: 1.6.4 -> 1.6.5, opensnitch-ui: 1.6.4 -> 1.6.5

Description of changes

update opensnitch and opensnitch-ui to 1.6.5
make rules path Rules.Path configurable
drop DefaultDuration option, it's deprecated
make `Ebpf.ModulesPath configurable
dynamic config file path
remove static paths to ebpf modules
move opensnitch packages to pkgs/by-name

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

dont know how to fix this error yet
       error: attribute 'services' missing

       at /nix/store/g98g0sg6w7jcak14cckfwdc9hnq5ppj7-nixos/modules/services/security/opensnitch.nix:6:9:

            5| let
            6|   cfg = config.services.opensnitch;
             |         ^
            7|   format = pkgs.formats.json {};
Cacheable portion of option doc build failed.
Usually this means that an option attribute that ends up in documentation (eg `default` or `description`) depends on the restricted module arguments `config` or `pkgs`.

Rebuild your configuration with `--show-trace` to find the offending location. Remove the references to restricted arguments (eg by escaping their antiquotations or adding a `defaultText`) or disable the sandboxed build for the failing module by setting `meta.buildDocsInSandbox = false`.

error: builder for '/nix/store/n9qmydpszxdn9x1fxbqg26n6px19p6hf-lazy-options.json.drv' failed with exit code 1;
       last 10 log lines:
       >
       >             5| let
       >             6|   cfg = config.services.opensnitch;
       >              |         ^
       >             7|   format = pkgs.formats.json {};
       > Cacheable portion of option doc build failed.
       > Usually this means that an option attribute that ends up in documentation (eg `default` or `description`) depends on the restricted module arguments `config` or `pkgs`.
       >
       > Rebuild your configuration with `--show-trace` to find the offending location. Remove the references to restricted arguments (eg by escaping their antiquotations or adding a `defaultText`) or disable the sandboxed build for the failing module by setting `meta.buildDocsInSandbox = false`.
       >
       For full logs, run 'nix log /nix/store/n9qmydpszxdn9x1fxbqg26n6px19p6hf-lazy-options.json.drv'.
error: 1 dependencies of derivation '/nix/store/y6b23j3hkh1w2m7nhw5l43xqym0zs4vm-options.json.drv' failed to build
error: 1 dependencies of derivation '/nix/store/g34z9z09xb5vxzh2ib90npji76zc9hrp-nixos-manual-html.drv' failed to build
Error: Process completed with exit code 1.

Does someone know how to fix this? @wegank @happysalada ?

Try setting meta.buildDocsInSandbox = false in nixos/modules/services/security/opensnitch.nix?

Thank you @wegank, was able to fix it :)


configurechains for Sepolia testnet with alchemyProvider

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
@wagmi/chains version "0.2.19",
Current Behavior
Trying to configure Sepolia with AlchemyProvider gives error "Error: unsupported network (argument="network", value={"name":"sepolia","chainId":11155111,"ensAddress":null}, code=INVALID_ARGUMENT, version=providers/5.7.2)". Page continuously reloads
Error doesn't happen with publicProvider or with other chains.
Expected Behavior
configuring sepolia to add to client without error
Steps To Reproduce
import { sepolia } from '@wagmi/core/chains';
import { alchemyProvider } from 'wagmi/providers/alchemy'
const { provider, webSocketProvider } = configureChains([sepolia], [  alchemyProvider({ apiKey: process.env.NEXT_PUBLIC_ALCHEMY_API_KEY }) ]);
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

Same with v0.12.12. Work around it by using v0.12.11.

Ethers v5 doesn't support Sepolia yet. Will need to use the jsonRpcProvider as a workaround and enter the URL manually.

Ethers v5 doesn't support Sepolia yet. Will need to use the jsonRpcProvider as a workaround and enter the URL manually.

Tysm @jxom  🙌
Question  :  Any reason why this breaks in 0.12.0 and not in  0.11.7 (last 0.11.x version) ?
Because I see even 0.11.x was also using ethers v5 .
The reason why I said it breaks at 0.12.0 is because I tried incrementally upgrading wagmi version starting from 0.11.6 and it started breaking at 0.12.0.
My assumption: In 0.11.x it would go to the next provider provided in an array... in our case  its publiProvider() but  something was changed in  0.12.0 which is breaking it, its not fallbacking
Thanks again 🙌


Exception during hydration phase is not handled correctly

Bug report
Describe the bug
If an unhandled exception occurs in render() method during hydration phase, the error handling logic of nextjs doesn't unmount/clear the markup received from a server. It's for production build, not dev mode.
More details:
Say you have page with a React component that throws an unhandled exception on client-side only. It's rendered correctly on server-side. After browser has loaded HTML&JS, hydration phase begins. The component throws an exception in render(); nextjs catches it and renders default error page, but the markup originated from server is not cleared. As a result user is faced with inconsistent page state: SSR'ed page without JS attached and default error page below it.
To Reproduce
Full source code to reproduce the bug: https://github.com/Mikhail-Fiadosenka/nextjs-rehydration-exception
Expected behavior
Default error page. Markup from server should be removed.
Screenshots
Actual result is on the screenshot below.

System information

<EMAIL_ADDRESS><EMAIL_ADDRESS>is subject to this bug too
<EMAIL_ADDRESS>
Additional context
I've debugged nextjs sources and found out that ReactDOM.hydrate is invoked twice
in client/index.js@renderReactElement(). My conclusion is that hydration process is aborted by exception, the flag isInitialRender is not set to false and the markup/React tree is not unmounted before error page is rendered.

I wonder if fixing this is as simple as doing:
try {
  ReactDOM.hydrate(reactEl, domEl)
} finally {
  isInitialRender = false
}

finally makes sure it's always executed regardless of an error being thrown
I'd have to debug this more to be certain though.

Hm, I've just tried this - it still hydrates twice, because it doesn't exit from first hydrate call, but goes deeper.
Log statements:
renderReactElement
Error: fake client-side error
renderReactElement
renderReactElement finally block
renderReactElement finally block

console.log('renderReactElement');
try {
    _reactDom.default.hydrate(reactEl, domEl);
} catch (e) {
    console.log('exception during hydration', e);
} finally {
    console.log('renderReactElement finally block');
    isInitialRender = false;
}

I'm going to close this issue as it's been open for almost a year and no other community members ran into the same issue, it seems like an edge case at this point.

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.


mock().CheckExpectations with LOCATION

Hello,
Currently when a mock expectation fails, the test fails with no line to track it.
It could be a nice enhancement to create a macro MOCK_CHECK_EXPECTATION() where FILE and LINE are used to make the failure report richer.
With this macro, user could have better control to debug mock failures.
What do you think?
Best,

Why? Usually a test has only one checkExpectations. So, it ain't hard to find it as it does show the file and line of the test that failed, right?
Considering that the line/file would be in the MockSupportPlugin most of the time, I'd guess it to be mostly useless.

Depends on the style of test you're writing.  I've found myself using multiple calls to checkExpectations() on occasion to verify that a certain method has definitely been called (and the expectation met) prior to calling something subsequent, since otherwise tests don't really make any guarantees about calling order, and sometimes the distinction is important.
Though if over-used it can lead to brittle tests, which is why the general recommendation is to make the minimum number of asserts possible per test (ideally one, in arrange-act-assert fashion).  (I also have a hard time doing that.)
Having said that, I'm not sure tracking the line would be particularly useful.  Generally to diagnose expectation failures you need to use a debugger anyway, so crashOnFailure() is your best friend in those cases instead.

I have done what @uecasm is suggesting a few times myself.  I found it useful when working with a state machine and I need to ensure exactly how many function calls it takes to cycle through certain states and make the calls to my mocked functions.  This became especially complicated when wanting to see how the system reacts to multiple cycles of the state machine.  Not really an ideal test by any means and there probably is a better way to handle what we're doing, but it works.  If I remember though, I was usually somewhat able to discern which checkExpectations() call failed by looking at the list it printed out of successful and missing mock calls.

From everybody I know that do some form of unit testing, only a very very few follow the "one check per test" rule. In practice, we see unit testing style is strongly coupled to the developer experience with testing, the most experienced of them, shall go the easier and simpler way (the hacker way), not the over engineered way.
Best,

Most people actually use the mock().crashOnFailure(). The reason for that is that you can get a stack trace. At least for me, when debugging mock failures, one of the most important info has been the stack trace and not the location of the checkExpectations.

@bas That's new for me. It will certainly solve my issues. Thanks.
On Thu, 12 Jan 2017 at 22:56 Bas Vodde<EMAIL_ADDRESS>wrote:

Most people actually use the mock().crashOnFailure(). The reason for that
is that you can get a stack trace. At least for me, when debugging mock
failures, one of the most important info has been the stack trace and not
the location of the checkExpectations.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cpputest/cpputest/issues/1075#issuecomment-272331238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEsiO2Hf8nSe0BzfMz6NemHLAAUh1pKTks5rRsvHgaJpZM4Lgvtj
.
--
Enviado do Gmail para celular


Multiwriter Hyperdrive (hyperdb backend)

Still missing APIs but close to all functionality is here now. Added a bunch more tests as well.
Multiwriter is provided by switching to hyperdb as the backend instead of append-tree. This also fixes most of our known scaling issues in term of storing lots of files in a single directory and more.
Prob the main thing missing is testing that our files-as-files storage still work and "latest" file tracking (mainly just porting this over from master)
/cc @joehand

Oh and docs for multiwriter are missing hehehe.
Mainly involves calliing archive.authorize(otherKey)

I see:
Hyperdrive.prototype.authenticate = function (key, cb) {
  this.db.authenticate(key, cb)
}

But hyperdb has no .authenticate() method. Was this intended to be .authorize() ?

Closing since this is a Hyperdrive 9 PR


support "Show Contents of a Dataverse" (/api/dataverses/$id/contents)

Please support the "Show Contents of a Dataverse" API.
At http://guides.dataverse.org/en/4.15/api/native-api.html#show-contents-of-a-dataverse it is documented like this:

Lists all the DvObjects under dataverse id.
GET http://$SERVER/api/dataverses/$id/contents

As a workaround for now I'm using api.get_request: https://github.com/IQSS/dataverse-sample-data/blob/ed52c316f530229b0c40463dc18c5f16d07cf11d/destroy_all_dvobjects.py#L30

Implemented in https://github.com/AUSSDA/pyDataverse/commit/10bb74a4452ee532b0fd242b5a2d4814d8ef25ec.


Bring in a number of default ignores / remove one that was duplicated

This list probably could grow forever.  I added most common ones I run into over 500+ repos at my day job.  I'm sure there are many more and this is just the tip of the iceburg.  Let me know what you think.
On the '.idea' one, I have been getting reports that 3.0 is licensing files in the folder so I suspect since this was only one not in the typical style as others it was likey some user error but see no harm in ensuring any .idea folder elsewhere is also ignored.
The xls entry was in the file already under docs.

Nice! Thanks a lot!
I will merge as soon as I see a successfy build.

@mathieucarbou Sorry I forgot to commas.  Fixed that.  I also added /node/ to be skipped.  Same reason as node_modules.  Thanks.
After this is in, is it possible for you to run a RC2?  I have a number of people that want to try this out.  More so for the .idea change as it was confirmed to me that idea will stick the idea folder into any folder that contains node/node modules so it will show up many times.
Beyond that I think I have a few more things but need to run some wide testing before I suggest more.  Appreciate it!

@mathieucarbou  Ping!

sounds good! thanks a lot!


**HERE’S!! WAY TO WATCH Indianapolis Colts vs Buffalo Bills LIVE Streams Free ON TV CHANNEL 10 NOV 2024

The Indianapolis Colts host the Buffalo Bills in NFL Week 10 action, with the teams heading in different directions. Explore the interactive widget below to discover the current spread, total, and moneyline betting odds and probabilities for the Bills-Colts matchup at Lucas Oil Stadium.
Bills quarterback Josh Allen has been the heart of this Bills squad, throwing for 2,001 passing yards, 17 touchdowns, and keeping turnovers to a minimum with just two interceptions. His improved decision-making has transformed this offense into a well-oiled machine that's tough to stop.
Meanwhile, the Colts are facing a challenging matchup, but they're not to be counted out. Veteran quarterback Joe Flacco brings experience to the offense, and they will be poised to pull off an upset. Indianapolis has a spark in running back Jonathan Taylor, who's been a bright spot with 502 rushing yards and five touchdowns this season.
The Colts (4-5) have lost two straight games and are dealing with a quarterback crisis. Joe Flacco will start in place of Anthony Richardson, but neither has exceled this season. The Colts are last in the NFL in passing accuracy (54.7%) and time of possession (25:41).
The Indianapolis Colts (4-5) return home to Lucas Oil Stadium on Sunday after consecutive road games, as they host the Buffalo Bills (7-2).
The Colts have dug themselves a hole, sitting a game under .500, but still only a game back of the final AFC playoffs spot, while the Bills only look ahead of them at the Kansas City Chiefs (8-0) in the AFC playoffs standings.
Injuries will play a role for both offenses, as each team ruled out a starting wide receiver on Friday: Michael Pittman Jr. (back) for the Colts and rookie Keon Coleman (wrist) for the Bills. The Bills also listed fellow starting receiver Amari Cooper (wrist), fullback Reggie Gilliam (hip), and linebacker Baylon Spector (calf) as questionable. Both Cooper and Gilliam were made inactive, and Spector was placed on Injured Reserve on Saturday.
The Colts should be hungry after a recent quarterback shift and embarrassing loss on primetime. The Bills have been a much more successful team this season and have a marquee matchup next week with those aforementioned Chiefs. Does this become a trap game for the favored Bills (-4)?
The Bills (7-2) seek their fifth straight win behind one of the NFL's most efficient quarterbacks, Josh Allen (64.1% completions, 2,001 yards, 17 touchdowns, 2 interceptions).
The Colts are the first team in NFL history to have played all one-possession games through Week 9. The Bills' average winning margin is 9.7 points, with four wins by at least three touchdowns, as well as one blowout loss.

ghjtgyj

cvb


misc lint/style improvements

we should write our own linter

[ ] figure out how to check for unused links in RTD and build test for it
[ ] add test to docs to check for trailing whitespace
[ ] clarify the situation with line-wrapping in docs
[ ] figure out how to properly handle images and standardize this everywhere (_static folders)
[ ] go through and clean up paragraph formatting in all docs
[ ] decide on the use of "consult" or "see" (e.g., https://github.com/docker-library/docs)
[ ] fix up all historic instances of "fix" vs "fixed" in the changelog (and other related imperative mood changes)
[ ] replace "table_ident" in docs with "my_table"
[ ] go through all docs and replace references to "documents" (Lucene jargon)
[ ] replace all :doc: statements with :ref: statements
[ ] standardize docs reference string nomenclature
[ ] (possibly) rewrap docs to match line width of GitHub diff comments so no ugly wrapping
[ ] go through all repos, including docker-docs, and update "the project documentation" in the readme to drop the "the" from the hyperlink for consistency
[ ] standardise header level of "Limitations" section at end of some docs

all lint checks should be documented in the style guide

needs splitting up


[CT-535] To use BigQuery TEMP table instead of native interim one for "insert_overwrite" strategy

Describe the feature
Currently, when DBT performs insert_overwrite strategy, it creates native interim table (with 12h expiration) within the same dataset as target table.
Describe alternatives you've considered
Whereas insert_overwrite strategy implemented as single BigQuery script, it looks more relevant to use real BigQuery temporary table via create or replace temp table statement. It will let keep clear target dataset, decrease complexity of model resource graph (table name can be constant cos BigQuery will just use it as postfix for under-the-hood script related dataset) and will be under native BigQuery temp tables expiration management.
Additional context
Additional impact on different macros (e.g.  snapshot etc.) should be additionally investigated to avoid unexpected behaviour.
Are you interested in contributing this feature?
Yes, I'm in.

^ ^ ^ ^ ^
@jtcohen6

Thanks for opening @xemuliam!
For context, BigQuery only supports real temporary tables within the context of a multi-statement query ("scripting"). This makes sense, since BQ otherwise doesn't have a notion of sessions or transactions. The temp table naturally expires at the end of the script.
Given that limitation, dbt creates "fake" temp tables when the create_table_as() macro is called with `temporary=True. These are real permanent tables that are set to expire after 12 hours:
https://github.com/dbt-labs/dbt-bigquery/blob/5253bf1579653c3f335de0f2d9e5558a748e7b8b/dbt/adapters/bigquery/impl.py#L711-L713
When enough weird edge cases collide, it can result in an issue like https://github.com/dbt-labs/dbt-bigquery/issues/154.
There are three cases I'm aware of in which dbt creates "temp" tables on BigQuery:

Incremental models with insert_overwrite strategy + on_schema_change = 'ignore'. dbt uses a real script (multi-statement query for this); the "temp" table is created as part of the script, and this could be a real temp table without any other changes. We could also then remove the cleanup in step 4.
Incremental models with insert_overwrite strategy + an "active" mode of on_schema_change — the "temp" table must be created earlier, in order to assess and handle column schema changes. Those schema changes could move into the
Snapshots (BigQuery uses the core default materialization), which call build_snapshot_staging_table in order to assess and handle column schema changes before running the atomic merge.

In an ideal world, dbt-bigquery would use scripts for all of those, including the column schema processing (alter statements) needed by 2 + 3, so that all of them could use "real" temp tables. That would be a much bigger lift, and it would require us to either duplicate or significantly refactor a lot of macro code from dbt-core.
In the meantime, let's find a non-invasive way to use a real temp table in the first scenario. We need some way to plumb through a new conditional argument, "real" temp table vs. fake-temp / "interim" table, and to make that intervention as surgically as possible.
I think there are two potential approaches:

A totally separate macro, create_temp_table_as. This would make sense if the arguments and options of create_table_as don't make much sense, and it's not a huge duplication of SQL between them.
If we're creating the temp table within the script, adjust tmp_relation to set its project/database + dataset/schema to None. (Temp tables should have identifiers only.) Then, in bigquery__create_table_as, add some logic that checks for whether temporary=True and the project/database + dataset/schema are None. If so, create temp table {{ tmp_relation.identifier }}.

Curious to hear which of those resonates with you more.


Adds env vars on container startup if id passed in

This PR adds some helper env vars when you pass a cluster ID as startup.  Otherwise this is not run but available.

er...
/lgtm


build_environment: add Linux-specific environment variables

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew tests with your changes locally?

supersedes #3341
Add Linux-specific environment variables to build_env_keys method:

LD_LIBRARY_PATH
LD_RUN_PATH
LD_PRELOAD
LIBRARY_PATH

CC @sjackman @MikeMcQuaid

Thanks again @maxim-belkin (and @sjackman for input)


[Safari] Files grid jumps when clicking a row for the first time upon page load

Steps

Sign into osf.io in Safari
Go to one of your projects
In either the project overview page or the files page, click on any row in the files grid (project name, add-on name, file, etc.)
Click on another row
Repeat this in any other browser (Chrome, FF, IE)

Expected behavior
I expected that the first click in Safari would behave like all the other browsers.

Actual behavior
The files grid jumps for a fraction of a second. It's very noticeable, but quick. After this first click upon the page load, clicking another row (Step 4) does not cause a flash.
(I couldn't capture it in a gif due to the low frame rate of my usual mov-gif converter.)

@nanchen47  I can look at it, thanks!

You got it!

After playing around for a while, I find it happens in two other situations. Firstly, go to the project with admin right.

changing the selection from osf-storage icon to github icon for the project with
changing the selection from osf-storage icon to the file under that osf-storage icon

@lbanner  after discussing with @caneruguz, we suggest to defer this bug. Firstly, it doesn't hurt any functionality and only happens on Safari. And also it is hard to debug.

Deferred!

Will be considered when refine the file grid.


Rescan when importing mnemonic

This PR fixes a bug which prevented a wallet to scan an already existing chain for old transactions when importing a mnemonic.
By default, the wallet will look for all the transactions from the Genesis block. This can be changed using importmnemonicfromtime=<timestamp> in order to save scanning time and to look for transactions in a concrete period.
### What to test
Importing a mnemonic from a wallet with transactions existing prior to the import time should show the complete transaction list and right balance.

Tested on devnet and imported wallet still not showing past transactions.

A new build of f0297ca372593e37631711324e114f599bbc4531 has completed succesfully!
Binaries available at https://build.nav.community/binaries/rescan-after-mnemonic

Tested on Windows 10

[x] Importing wallet and verify past tx appear correctly
[x] Creating a new wallet with seed phrase
[x] Client boots normally when a wallet.dat already exists


Make table title configurable or based on step name

On one of my workflows, I run component and afterward E2E tests. The summary produces two tables with the identical heading "Cypress Results". I'd like to have the step name, a custom specified name or maybe just the hint if those are E2E/component tests in the table headers.

@alex1701c
This enhancement would be nice to have!
The example-chrome workflow has two steps calling Cypress in one job and the results are not clear since only the job name, not the step names, is shown:

The first result summary is actually from the step Chrome headless and the second result summary is from the step Chrome headed.
The results summary is produced using @actions/core and the best description I found was on https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/.
I may have overlooked something, but I couldn't see any obvious way to add the step name into the summary. It may need an enhancement to  @actions/core.summary to add the step name.

@alex1701c
The most flexible solution would be to introduce a parameter to override the default heading "Cypress Results" of the Job Summary. If there were implemented, then the above Job Summary could be changed for instance like this:

I plan to submit a PR to implement this suggestion.

See PR https://github.com/cypress-io/github-action/pull/1056 for solution

I may have overlooked something, but I couldn't see any obvious way to add the step name automatically into the summary. It may need an enhancement to @actions/core.summary to add the step name automatically.

I couldn't find one either.

Thanks a lot!


Unstick heatmap filters and make row/column labels sticky

Description
The heatmap filters are no longer sticky; users can scroll the page so the heatmap is the only thing shown on the page.

The sample titles, taxon titles, and metadata fields are now sticky on the heatmap.
Scrolled to the bottom of the heatmap.

Zoomed in, scrolled to the middle and far right of the heatmap.

Notes

To prevent double scrolling (both the page and the heatmap scrolling), the page will not scroll if the mouse is hovering over the heatmap unless the heatmap has already been scrolled to the top/bottom.
Since the metadata fields (including their labels) are grouped together, the metadata labels and Add metadata button aren't sticky.

Tests

Verified that scrolling works as expected for different heatmaps.
Verified that the heatmap scrolling is bounded (i.e. the heatmap can't be scrolled off the page).
Verified that zooming still works as expected.

This is awesome!
Quick question looking at the screenshot: when scrolling horizontally, doesn't the current behavior mean that cells will line up with the wrong metadata?

doesn't the current behavior mean that cells will line up with the wrong metadata

I think they are aligned... What was confusing is that the labels and the cells that are now out of the heatmap did not disappear. We should either place a white rectangle in top left corner or apply clipping (https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Clipping_and_masking) to the g elements that hold the row  labels and metadata cells. Does the same happen with column labels?

Hey Julie! This looks great!
My one big concern is that with this implementation, it looks like the only way to scroll horizontally is with the mouse wheel. There's no horizontal scrollbar. For users without a mouse that supports horizontal scrolling, they might not be able to scroll horizontally at all. Maybe @happyimadesignr can weigh in on whether that would be an issue.

Right now, it's only possible to scroll over the heatmap cells, not the heatmap labels. Would it be hard to enable scrolling on the labels as well?
For the pathogen name labels, only vertical scrolling would need to be enabled. And for sample name, only horizontal scrolling.

I see a little visual artifact (the gray line) above "Collection Location". Maybe one of the background rects is a couple pixels off?

Could we change the cursor to the "move" cursor when dragging is happening? (see https://developer.mozilla.org/en-US/docs/Web/CSS/cursor)

While I had a few comments, this PR looks really good overall! Thanks for taking the time to go through all the different iterations. Your final approach was easy to understand, which is a great accomplishment given that the Heatmap code has been historically tough to work with! Awesome job.


Error [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]SSL Provider: [error:140A90A1:SSL routines:SSL_CTX_new:library has no ciphers]

.+Please check the FAQ (frequently-asked questions) first. If you have other questions or something to report, please address the following:
+## PHP Driver version or file name

5.6.1
+## SQL Server version
SQL Server 2016
+## Client operating system
SUSE Linux Enterprise Server 15
+## PHP version
7.2.5
+## Microsoft ODBC Driver version
ODBC Driver 17
+## Table schema
Not Relevant
+## Problem description
+$connectioninfo=array("UID" => $DB_user, "PWD" => $DB_pass, "Encrypt" => false, "Datab
ase"=>$DB_dbName);
$conn=sqlsrv_connect( $DB_host, $connectioninfo);
if  ( $conn  === FALSE)
{
echo "There has been an error connecting to the back-end sy
stems supporting the Online directory.";
die( print_r( sqlsrv_errors(), true));
}

The connection to the database on the command line works fine using sqsh from FreeTDS.
+## Expected behavior and actual behavior
+
+## Repro code or steps to reproduce

Forgot to say we are using openssl 1.1 instead of openssl-1.0.2 see issue #680

@rachid-c This is a known bug which is fixed in an upcoming release, so please stay tuned!

Many thanks David

@rachid-c The latest release of the ODBC driver (version 17.4) should fix this problem. Please upgrade your msodbcsql17 installation using your package manager and let us know if the problem is fixed.

Closing issue due to inactivity. Please reopen if necessary.


No such module 'SwiftyOnboard' in Xcode 9

Hi guys, why did I get this error No such module 'SwiftyOnboard' in Xcode 9? I'm installing SwiftyOnboard using pod and import SwiftyOnboard in ViewController . Thanks in advance

same here

Here's a StackOverflow post that might help. In case it doesn't work can you please let me know how you installed the framework?

i just installed the pod and try using swift 3.2, it's look like the error is compability version. can you take a look at this ? https://imgur.com/a/7BquL


mx.nd.save function can't be used to save into S3 bucket with periods in bucket name

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System:
Ubuntu 16.04
Compiler:
gcc
Package used (Python/R/Scala/Julia):
Python
MXNet version:
0.7
Or if installed from source:
Yes
MXNet commit hash (git rev-parse HEAD):
487c22a50541686cc3fd207ad4656dbd2f9fa969
If you are using python package, please provide
Python version and distribution:
2.7
If you are using R package, please provide
R sessionInfo():
Error Message:

MXNetError                                Traceback (most recent call last)
 in ()
----> 1 mx.nd.save("s3://imagetraining.xxxx.com/testing/a",[a,b])
/home/ubuntu/.local/lib/python2.7/site-packages/mxnet-0.7.0-py2.7.egg/mxnet/ndarray.pyc in save(fname, data)
1082                                   mx_uint(len(handles)),
1083                                   c_array(NDArrayHandle, handles),
-> 1084                                   keys))
1085
1086 def imdecode(str_img, clip_rect=(0, 0, 0, 0), out=None, index=0, channels=3, mean=None):
/home/ubuntu/.local/lib/python2.7/site-packages/mxnet-0.7.0-py2.7.egg/mxnet/base.pyc in check_call(ret)
75     """
76     if ret != 0:
---> 77         raise MXNetError(py_str(_LIB.MXGetLastError()))
78
79 if sys.version_info[0] < 3:
MXNetError: [03:32:57] src/io/s3_filesys.cc:682: Check failed: num_retry < max_error_retry_  maximum retry time reached
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
Create a new Jyputer notebook, run the following Python , make sure that the bucket name of S3 has period in it:
a = mx.nd.zeros((100, 200))
b = a+1
mx.nd.save("s3://imagetraining.xxx.com/testing/a",[a,b])
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

Start Jupyter.
Create a notebook with the sample code above
Run it and then will fail

What have you tried to solve it?

Tried another S3 bucket without period in the bucket name. It worked.
In the document of S3: http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html, found the following description:

When using virtual hosted–style buckets with SSL, the SSL wild card certificate only matches buckets that do not contain periods. To work around this, use HTTP or write your own certificate verification logic.

Looked into the source code dmlc-core/src/io/s3_filesys.cc:682, found that the source code is using virtual host style url to access S3, as the following code shows:

surl << "https://" << path_.host << ".s3.amazonaws.com" << '/'
<< RemoveBeginSlash(path_.name) << args;
This virtual host style method will fail because of SSL issue when the target bucket has period in the bucket name.

@mli

One PR was created to resolve this issue:
https://github.com/dmlc/dmlc-core/pull/203
Please help to review it and check whether it is a proper fix.


x/build/cmd/coordinator: make all logs URLs permanent

No matter what scary text I put in the URL, people still link to farmer.golang.org's emphemeral build logs.
Perhaps farmer.golang.org should start recording all its streamed state to GCS and make sure that all emphemeral build log URLs have enough information in them to fetch the old logs from GCS if the build is not currently in progress.

I'll close this 2015 issue in favor of #34119, which supersedes it.
This issue describes fairly low level implementation details, and coordinator may have changed since 2015. We can open new specific issues to track this work as needed.


Error on call of function plot

Hi!
Im trying to run the first code in readme. Probably Im doing something wrong.. Could you help ?
Im using a MacBook pro. Ive installed everything with miniconda (some packages I needed to install globally because miniconda does not have support for some packages to OSx64).
Then a ran in jupyter a test.py with the commands in readme. Also, I`ve downloaded a .ply sample.
The command print(scene) works fine, but when I call the .plot(), an error happens:
Traceback (most recent call last):
File "test1.py", line 8, in
scene.plot()
File "/Users/lrodrigues/miniconda2/envs/pyntcloud/lib/python3.6/site-packages/pyntcloud/core_class.py", line 604, in plot
return plot_PyntCloud(new_PyntCloud, output_name=output_name)
File "/Users/lrodrigues/miniconda2/envs/pyntcloud/lib/python3.6/site-packages/pyntcloud/plot/points.py", line 17, in plot_PyntClou
d
with open(src, "r") as inp, open(dst, "w") as out:
FileNotFoundError: [Errno 2] No such file or directory: '/Users/lrodrigues/miniconda2/envs/pyntcloud/lib/python3.6/site-packages/pyn
tcloud/plot/points.html'
Do you have any tip to solve this ?
Thanks!

Thanks for reporting!
Let me look into this.
Regarding conda packages on Mac OS, I'm working on loading all dependencies to conda-forge, a comunnity-driven alternative to anaconda's default channel.

Found the problem. You were not doing something wrong. I forgot to add data filles (with no .py extensions) in setup.py, so the points.html file is missing. I'll fix this soon.
Pd. I'm insteresting in knowing wich packages failed to install using the pyntcloud_env.yml file, could you pass me a list??

@cercao Please could you confirm that this is fixed on Mac Os??


Lints do not correctly handle renamed providers

Describe the bug

As you can see, renamed providers trigger this lint. This is possibly a wider issue that might be affecting other lints, and making it so we dont see lint hints when we should.
To Reproduce
As shown above, simply create a generated provider, and alias it. then attempt to use it in another generated provider
Expected behavior
I should not see the lint, as the provider is, in fact, a generated provider.

This isn't supported and won't be.
The proper solution is to wait for static metaprogramming.
Then we'd be able to do:
class Foo {
  @riverpod
  int fn(FnRef ref) => 0;
}


add long running operation result to the botservice swagger

Automation for azure-sdk-for-ruby

Automation for azure-libraries-for-java

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

@swagatmishra2007 Please address the comments soon, the PR will be closed if not active.

it seems like we need further discussion on how to get the semantics working here. We were looking at the analysis services swagger and like you pointed out , they arent doing the right thing too. we will follow up on email and then send out a new pr. i am closing this for now. thanks for your comments @dsgouda

Automation for azure-sdk-for-java


Read ORCA Handbook and Policies

Read the Following Documents:

How_ORCA_Works.md
ORCA_Handbook.md
IT_and_Data_Security_Policies.md
Intellectual_Property_Policy.md
CODE_OF_CONDUCT.md
Add a comment to this issue with your initials and date completed, then close the issue

JC 5/31/34


(WIP) MINOR: Cache topic resolution in TopicIds set

This is just a prototype at this stage. Resolving topic names to topic ids in the assignors, especially in the heterogeneous case, is quite expensive. This patch adds a cache in front of the resolution. The results show that it reduces significantly the runtime of the assignors in heterogeneous case.
Before
Benchmark                                       (assignmentType)  (assignorType)  (isRackAware)  (memberCount)  (partitionsToMemberRatio)  (subscriptionType)  (topicCount)  Mode  Cnt    Score   Error  Units
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL           RANGE          false          10000                         10         HOMOGENEOUS          1000  avgt    5   32.267 ± 1.020  ms/op
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL           RANGE          false          10000                         10       HETEROGENEOUS          1000  avgt    5  181.725 ± 1.464  ms/op
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL         UNIFORM          false          10000                         10         HOMOGENEOUS          1000  avgt    5    2.457 ± 0.147  ms/op
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL         UNIFORM          false          10000                         10       HETEROGENEOUS          1000  avgt    5  318.835 ± 2.517  ms/op
JMH benchmarks done

After
Benchmark                                       (assignmentType)  (assignorType)  (isRackAware)  (memberCount)  (partitionsToMemberRatio)  (subscriptionType)  (topicCount)  Mode  Cnt    Score    Error  Units
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL           RANGE          false          10000                         10         HOMOGENEOUS          1000  avgt    5   32.734 ±  2.146  ms/op
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL           RANGE          false          10000                         10       HETEROGENEOUS          1000  avgt    5  117.596 ±  4.650  ms/op
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL         UNIFORM          false          10000                         10         HOMOGENEOUS          1000  avgt    5    2.472 ±  0.137  ms/op
ServerSideAssignorBenchmark.doAssignment             INCREMENTAL         UNIFORM          false          10000                         10       HETEROGENEOUS          1000  avgt    5  292.808 ± 21.007  ms/op
JMH benchmarks done

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Replaced by https://github.com/apache/kafka/pull/17285.


Directory Service: DescribeDirectories expects LaunchTime to be a JSON Number, got string instead

Hello,
I'm using moto server with Terraform, creating a AWS Directory Service instance. I think there was a change in the API for ds:DescribeDirectories, or maybe just new validation on the response. But using the latest moto version, 5.0.12, I'm seeing the following error:
Error: reading Directory Service Directory (d-7b4fdb73d6): operation error Directory Service: DescribeDirectories, https response error StatusCode: 200, RequestID: QjGxElo4976zUbXqHjhAzLjSYn2WHHZ0VA46AmJTfyjldHWH6hVP, deserialization failed, failed to decode response body, expected LaunchTime to be a JSON Number, got string instead

  with module.directory_service.aws_directory_service_directory.this,
  on ../../main.tf line 1, in resource "aws_directory_service_directory" "this":
   1: resource "aws_directory_service_directory" "this" {

Checking the code, I see it is writing a datetime string in isoformat:
https://github.com/getmoto/moto/blob/2a8bb4a6fc06ad91ad1b234ccb11c1199b0898f2/moto/ds/models.py#L83
Looking up the API doc for the command, the response syntax for LaunchTime is actually a number.
https://docs.aws.amazon.com/directoryservice/latest/devguide/API_DescribeDirectories.html#API_DescribeDirectories_Examples

Actually, near identical issue on CodeBuild Projects. The codebuild:CreateProject response expects both TimeStamp and BuildTimeOut to be a number, but it's getting a string.
Error: creating CodeBuild Project (tardigrade-test-branch-flow-ci-branch-master-flow-ci): operation error CodeBuild: CreateProject, https response error StatusCode: 200, RequestID: 0btCD9rbQYZDkxcRWJCHux6XSJy7z6pJUzPY7X1sPRCd6Gcpinve, deserialization failed, failed to decode response body, expected BuildTimeOut to be json.Number, got string instead

  with module.test_branch["master_branch"].module.runner.aws_codebuild_project.this,
  on ../../modules/_internal/runner/main.tf line 168, in resource "aws_codebuild_project" "this":
 168: resource "aws_codebuild_project" "this" {

Error: creating CodeBuild Project (tardigrade-test-branch-flow-ci-branch-testempty-flow-ci): operation error CodeBuild: CreateProject, https response error StatusCode: 200, RequestID: bu61y90m14BiKzBPndSMQxGcyinqauHLzy5Tzgs7LX3yIpJhchxn, deserialization failed, failed to decode response body, expected Timestamp to be a JSON Number, got string instead

  with module.test_branch["test_empty_list"].module.runner.aws_codebuild_project.this,
  on ../../modules/_internal/runner/main.tf line 168, in resource "aws_codebuild_project" "this":
 168: resource "aws_codebuild_project" "this" {

I think these are where it's set in moto:
https://github.com/getmoto/moto/blob/2a8bb4a6fc06ad91ad1b234ccb11c1199b0898f2/moto/codebuild/models.py#L120
https://github.com/getmoto/moto/blob/2a8bb4a6fc06ad91ad1b234ccb11c1199b0898f2/moto/codebuild/models.py#L130
And here's the api doc with the response syntax indicating those should be numbers:
https://docs.aws.amazon.com/codebuild/latest/APIReference/API_CreateProject.html#API_CreateProject_ResponseSyntax

Hi @lorengordon! I've opened a PR that fixes both issues (+ a bunch of other things to make TF happy).


Problem with TimeSeek blend.

TimeSeek blend seems not working properly.
Cause I am unable to describe this I made a repo with my test project.
https://github.com/kakoeimon/third
Press right mouse button to get in the aiming pos and then move up the mouse to see that the animation is wrong.

Is this still reproducible in the current master branch? I think there were fixes made to TimeSeek around 2.0 - early 2.1 days.

Bump.

I think that with the new AnimationTree in 3.1 we can assume this is definitely fixed.


How to separate RGB chanels?

Here is the C++ equivalent to separate a R/G/B channel.
Mat src = imread("img.png",CV_LOAD_IMAGE_COLOR); //load  image

Mat bgr[3];   //destination array
split(src,bgr);//split source

//Note: OpenCV uses BGR color order
imwrite("blue.png",bgr[0]); //blue channel
imwrite("green.png",bgr[1]); //green channel
imwrite("red.png",bgr[2]); //red channel

How to achieve this in Go OpenCV?

Hope help
	for x := 0; x < img.Width(); x++ {
		for y := 0; y < img.Height(); y++ {
			channels := img.Get2D(x, y).Val()
			fmt.Printf("B:%d, G:%d, R:%d, A:%d \n", uint8(channels[0]), uint8(channels[1]), uint8(channels[2]), uint8(channels[3]))
		}
	}


core-plugin-api: switch to using a plain string key for attaching component data

Hey, I just made a Pull Request!
Turns out the WeakMap method of storing component data has some issues when react-hot-loader is brought into the mix, as well as the old symbol storage method. This switches over to a plain non-enumerable string key which is a bit ugly but also way more robust. Having debugged some issues related to this I also find it very useful to have the component data of a component more easily accessible at runtime. This change is of course backwards and forwards compatible and we can keep that in place for a long time if needed.
Also cleaned up some useless stuff in core-app-api while at it x)
This fixes the currently broken storybook in local development, and removes the need for an ugly workaround. (Thank you for reporting @Fox32 👍)
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@freben it's only storybook changes so no need for a changeset


Added miniumResultsForSeach

Added custom attribute 'minimumResultsForSelect' to ui-select directive which will remove the 'select2-with-search' class.
Added styles to hide the search if the 'select2-with-search' class is not applied.
Updated examples to include a case where the search is hidden.
Resolution for Issue #54

+1

@LukeBaulch does #166 resolve this issue?
@sambomartin, your can fork the repo, make your changes, commit and then make a pull request. For more information please see the following https://help.github.com/articles/using-pull-requests/

+1

As the initial PR was for issue #54 and that is closed I think this can be closed as wel?? @user378230 @aaronroberson


Store balance of each token is separate keys

This will lead to more efficient querying of custom-token balances.
Attackers will not be able to spam accounts with tokens anymore

Codecov Report
Base: 60.91% // Head: 60.77% // Decreases project coverage by -0.14% :warning:

Coverage data is based on head (5d6eded) compared to base (04d82a1).
Patch coverage: 51.96% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
- Coverage   60.91%   60.77%   -0.15%
==========================================
  Files          69       69
  Lines        3618     3653      +35
==========================================
+ Hits         2204     2220      +16
- Misses       1414     1433      +19

Impacted Files
Coverage Δ

src/core/address.rs
26.08% <ø> (-10.96%)
:arrow_down:

src/core/transaction.rs
71.05% <ø> (+2.00%)
:arrow_up:

src/db/mod.rs
93.22% <ø> (ø)

src/main.rs
0.00% <ø> (ø)

src/blockchain/mod.rs
57.61% <48.93%> (-0.43%)
:arrow_down:

src/node/heartbeat/log_info.rs
78.26% <75.00%> (ø)

src/db/keys.rs
100.00% <100.00%> (ø)

src/zk/mod.rs
59.12% <0.00%> (-1.75%)
:arrow_down:

src/core/money.rs
92.30% <0.00%> (+5.12%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Rename README.markdown to README.md

Maintain consistency in project based on other usages of Markdown files (.md)

@piperchester you'll also need to update .travis.yml and Makefile.


Proposed Recipes for Euro-Cordex

The following is transcribed from @larsbuntemeyer in https://github.com/pangeo-data/pangeo/issues/862
Source Dataset

I wanted to drop some of my thoughts here on bringing WCRP EURO-CORDEX datasets to the cloud. That would be cmorized datasets on the European Cordex domain that are currently available only for access by download from, e.g., ESGF or the Coperniucs Climate Data Store.

Link to the website / online documentation for the data - https://www.euro-cordex.net/

The file format (e.g. netCDF, csv) - ???

How are the source files organized? (e.g. one file per day):

i guess i would be able to get support from DKRZ-ESGF where i usually work with the ensemble and where also an intake collection is maintaned. The ensemble contains about:

up to 150 datasets on the EUR-11 Cordex domain each for a number of frequently requested variables,
about 75 TB of data volume for the complete ensemble and all variables on the EUR-11 domain.

How are the source files accessed (e.g. FTP)

a notebook that shows access to the 2m surface temperature EURO-CORDEX ensemble dataset at DKRZ.

Any special steps required to access the data (e.g. password required) - Raw data from ESGF or CDS. Copy at DKRZ.

Transformation / Alignment / Merging

???
Output Dataset

Zarr?
Licensing Question

I am especially wondering what license would be required for the data to be made available publicly and if you think that the Cordex terms of use would be a problem for distributing the data freely? Right now, on ESGF only CMIP5 and CMIP6 data are freely available while for Cordex you still have to register.
I would be interested in your thoughts on whether that data could be successively made available through PANGEO cloud storage. As i said, right now this is just an idea, but the Euro-Cordex General Assembly is coming up in the end of January 2022 and i wanted to bring that up and discuss it in the community. Thanks a lot!

Regarding the license, I note that there are two different licenses for CORDEX:

Terms of use for CORDEX data for non-commercial research and educational purposes of:
a) I agree to restrict my use of CORDEX model output for non-commercial research
and educational purposes only.
Results from non-commercial research are expected to be made generally available
through open publication and must not be considered proprietary. Materials prepared
for educational purposes cannot be sold. These restrictions may only be relaxed by
permission of the individual modelling groups responsible for the simulations.
OR
Terms of use for CORDEX data for commercial purposes (unrestricted use):
a) I understand that the subset of CORDEX model output that will be made
accessible to this group has been designated for "unrestricted" use.

A big reason for putting data in the cloud is to make it more accessible for commercial use. So could we choose the option of the commercial license?

Thanks @rabernat for moving this issue, the recipe approach sounds great!! I am familiar with it from conda forge feedstocks. Just found some more detailled info on the license of individual mode ids.

The easiest way to get the data will probably be via ESGF, like for CMIP6: https://cordex.org/data-access/

@larsbuntemeyer did you get any further with this?


Update lockfile after Storybook move

Description

Additional context

Issue reference

coverage: 80.646% (+8.9%) from 71.722%
when pulling 1fb2ca69d6932c2f038ac4d4cbbf058a28e99158 on chore/update-yarn-lock
into b36ed743041abbee9d900c94721d916b9956e012 on main.


Hangup when formatting in VSCode

Hi!
First, thanks for making this amazing tool, it really saved me a lot of time :)
When using the VSCode extension, the plugin hangs up when formatting some files. After some digging, I think I found the culprit: https://github.com/belav/csharpier/blob/eb567079b7aac4b3c5c277702888edf7d3890b61/Src/CSharpier.VSCode/src/CSharpierProcessPipeMultipleFiles.ts#L29-L48
When the chunk contains multiple format results, this gets just the first one and won't call other callbacks until the next chunk arrives. An easy fix I applied locally is to wrap the "last chunk" section of the code in a while(true) loop and get all the results from the chunk. That seems to resolve the issue.
I can provide a PR for that if you want.
Cheers!

@hkvoch I'm in here trying to fix some other issues and can include that fix as well, thanks for tracking down the fix for it!
I should have a new version out in the next day or two.


Workaround DeprecationWarning raised from pkg_resources

Workaround for https://github.com/pypa/setuptools/issues/2885

pfnCI, run Jenkins please.

Seems like this fixes it :)

Jenkins CI test (for commit 9a506a9ed46ed4cbb423f579d35458e33400c3f0, target branch master) succeeded!


use absl-py instead of google-apputils and gflags

I signed it!

Thanks for the pull-request -- I actually just merged another change that I believe makes this request obsolete. Thank you in any case.


typeof null === 'object', but we don't need such objects

Otherwise it breaks at least toArray pipe, and probably others.

Coverage remained the same at 100.0% when pulling 5a59d376160cf4184423dce650b20c9c277f0137 on komachi:master into 65681cda084b79cced3aefa968dc2a7634fd7e8f on fknop:master.

Can you merge it? It's possible to use ugly workaround like (obj || {}) | toArray, but it will be better if null will not be considered as object.


Case insensitivite match/regular expressions

Hello all,
Postgres supports case sensitive and insensitive operations.
Regular expressions match (~) currently defaults to case sensitive but match (LIKE) defaults to case insensitive.
The goal of this PR is to

Make case sensitivity explicit for match and regular expression match.
Introduce predicates matches_regexp and does_not_match_regexp.

I'd like it if both regular expressions and like match defaulted to case sensitivity, but that would change the def sql generated by postgres and I assume that is discouraged.
If you would like me to make both operators default to case sensitive (or case insensitive), let me know.
/cc @matthewd @tenderlove thoughts?

@tenderlove I can change this to have a different Arel operator for case insensitive operators instead of booleans. Just let me know.
Happy conference going.

Wonder if this is a little related to #286
And ugh. Postgres uses different regular expression syntax. their SIMILAR TO uses % as a wild character, but the regular expression uses standard posix regexps .* as wild character.
I can split this PR into 2. Just ask that you state a preference around whether a) to default to case insensitive or sensitive and b) is case sensitive a boolean or a separate token?
Thanks

@kbrock tbh I'm totally fine with this. I'll merge it.


Support BIND (and other SPARQL 1.1 constructs) in SparqlQueryRenderer

(Migrated from https://openrdf.atlassian.net/browse/SES-2206 )
SPARQL 1.1 constructs cannot be rendered via the SparqlQueryRenderer class.
Subtasks

[x] support BIND
[ ] support aggregates (#3000)
[ ] support subqueries (#3001)

Examples
For example If I parse this query with QueryParserUtil.parseQuery:
SELECT \* WHERE {
  ?s ?p ?o .
  BIND(uri("http://test-graph.com/") AS ?foo) .
}

And then render the ParsedQuery back out again with SPARQLQueryRenderer, it appears to lose the binding clause, returning the following string:
select ?g ?s ?p ?o ?g2
where {
  GRAPH ?g {
    ?s ?p ?o.
}}

Looking at renderTupleExpr in SparqlTupleExprRenderer I can see that the following lines are commented out:
    // aRenderer.mProjection = new ArrayList<ProjectionElemList>(mProjection);
    // aRenderer.mDistinct = mDistinct;
    // aRenderer.mReduced = mReduced;
    // aRenderer.mExtensions = new HashMap<String, ValueExpr>(mExtensions);
    // aRenderer.mOrdering = new ArrayList<OrderElem>(mOrdering);
    // aRenderer.mLimit = mLimit;
    // aRenderer.mOffset = mOffset;

With the following commented out in SPARQLQueryRenderer:
                    // SPARQL does not support this, its an artifact of copy and
                    // paste from the serql stuff
                    // aQuery.append(mRenderer.getExtensions().containsKey(aElem.getSourceName())
                    // ?
                    // mRenderer.renderValueExpr(mRenderer.getExtensions().get(aElem.getSourceName()))
                    // : "?"+aElem.getSourceName());
                    //
                    // if (!aElem.getSourceName().equals(aElem.getTargetName()) ||
                    // (mRenderer.getExtensions().containsKey(aElem.getTargetName())
                    // &&
                    // !mRenderer.getExtensions().containsKey(aElem.getSourceName())))
                    // {
                    // aQuery.append(" as ").append(mRenderer.getExtensions().containsKey(aElem.getTargetName())
                    // ?
                    // mRenderer.renderValueExpr(mRenderer.getExtensions().get(aElem.getTargetName()))
                    // : aElem.getTargetName());
                    // }

I believe these lines are commented out in error and that they should be commented back in in order to get be able to round trip queries from SPARQL text into the AST and back out again.
Other SPARQL 1.1 queries that fail include:
SELECT (COUNT (*) as ?c) WHERE { ?s ?p ?o }
is rendered as
select ?c where { ?s ?p ?o }
and the query
SELECT (?p as ?x) WHERE { ?s ?p ?o }
is rendered as
select ?p WHERE { ?s ?p ?o }

The basic problem is that the QueryRenderer was implemented against the SPARQL 1.0 standard, and has never been extended to include the new SPARQL 1.1 features (even though RDF4J's query engine fully supports SPARQL 1.1). The renderer should be extended to be able to process these features.

We need to have a discussion about the query render and the query builder tools, and the newly integrated spanqit module.

Hi evrybody,
so as this ticket is closed, is there any way to create an AST based on a SPARQL Query, modify it, and transform it back to SPARQL? I believe this is a very viable feature for this project.
Regards

Creating an AST from a query is what the SPARQL parser package (specifically the class org.eclipse.rdf4j.query.parser.sparq.ast.SyntaxTreeBuilder) does. There's support for modifying it as well through the SyntaxTreeBuilderVisitor interface.
The only thing we don't really have full support for is serializing an AST back into a SPARQL query string. The SparqlQueryRenderer discussed in this issue has partial support, but as the ticket says, it's never been updated to deal with SPARQL 1.1.

This got closed accidentally a while ago by merging a fix that had nothing to do with this, but which (accidentally) used this issue's ticket number.

Thanks @RedCrusaderJr, your fix for BIND has been merged in!
I am planning to pick up further improvements as subtasks of this issue.

Closing this as complete, further improvements will be taken care of as followup tasks.


How can I better handle the form JSON in my own database?[Question]

I have been developing an Angular 8 CMS which includes angular-form builder / renderer and allows CMS users to create forms and external users to submit forms. When creating a form within the CMS, I POST the JSON to my own custom Symfony API server and store the JSON against a Form entity. That all works good....
When an external user completes and submits a form, the JSON is posted to my own web service and is stored in an FormSubmission entity. That also works good....
Now, the problem I am finding is that it is unreliable to match a form submission response to a form question because I only have string matching to help me
I understand that it is really upon me to write code to handle the matching but I am wondering if there is anything within the angular-formio library that can help me with this?

So after some thought today it seems to me that I need a database representation of each question of each form and also a database representation of each form question response with a database relation between question and form
The form and response JSON will still exist in the database but only for angular formio to parse and display the form and also for the response that formio sends back to my web server
I would appreciate any further suggestions if you are reading this
Many thanks

The formio.js library contains some utils that allows you to find a component provided the "key" of the data.
const component = FormioUtils.getComponent(form.components, 'firstName');
console.log(component);

This can be used to traverse the form components array to find the component JSON that has the metadata to describe the component for a specific field in the submission.

The formio.js library contains some utils that allows you to find a component provided the "key" of the data.
const component = FormioUtils.getComponent(form.components, 'firstName');
console.log(component);

This can be used to traverse the form components array to find the component JSON that has the metadata to describe the component for a specific field in the submission.

This worked great and is exactly what I needed to help me
Thank you :)

When an external user completes and submits a form, the JSON is posted to my own web service

Hi @sterichards,
Could you please let me know how did you manage to post the form data to your endpoint through the Form Render component? I'm unable to spot any documentation around this topic that enables us to set our custom endpoint. I cannot allow any 3rd party service to store our data due to its sensitivity and privacy concerns.
Any guidance or help is highly appreciated.
I also apologize for posting help questions here but I found the Form IO Gitter community is not very active.

When an external user completes and submits a form, the JSON is posted to my own web service

Hi @sterichards,
Could you please let me know how did you manage to post the form data to your endpoint through the Form Render component? I'm unable to spot any documentation around this topic that enables us to set our custom endpoint. I cannot allow any 3rd party service to store our data due to its sensitivity and privacy concerns.
Any guidance or help is highly appreciated.
I also apologize for posting help questions here but I found the Form IO Gitter community is not very active.
Thanks,
Manaday

I'm happy to help, it's OK
I am very "rusty" with this project because it got discontinued but I still have the code. Maybe this helps:
Component code - https://pastebin.com/Y3QUuuwL
Template code - https://pastebin.com/1TPbuQrN
If that doesn't help I can give you access to the repo so you can look through the code yourself

So kind of you. That was very quick @sterichards! Thanks much for your time and efforts.
I think I could've better narrated my question in the first place.
I've achieved all items from the following Todo list except the last one. That's where I seek help.

[x] Form Builder component integration to design the form
[x] Saving generated JSON form schema to my (mock) backend API
[x] Fetching and rendering JSON form schema using Form Renderer (formio) component for my web app users to allow them to fill the form
[ ] Posting/Saving filled form data to my backend API (This is where I'm stuck).

The code snippets you've shared seem to save JSON Schema (#2) to the backend API which I've also achieved.
If your repo doesn't contain any sensitive information then I'd request you to kindly grant access to it. That'd be a great help.
Again many thanks! 😊🙏🏼

So kind of you. That was very quick @sterichards! Thanks much for your time and efforts.
I think I could've better narrated my question in the first place.
I've achieved all items from the following Todo list except the last one. That's where I seek help.

[x]  Form Builder component integration to design the form
[x]  Saving generated JSON form schema to my (mock) backend API
[x]  Fetching and rendering JSON form schema using Form Renderer (formio) component for my web app users to allow them to fill the form
[ ]  Posting/Saving filled form data to my backend API (This is where I'm stuck).

The code snippets you've shared seem to save JSON Schema (#2) to the backend API which I've also achieved.
If your repo doesn't contain any sensitive information then I'd request you to kindly grant access to it. That'd be a great help.
Again many thanks! 😊🙏🏼

@ManadayM  - https://github.com/sterichards/fillform-web-app
Hope you find what you need

Thank you so much, @sterichards! I'm going through your implementation now. 🤞🏼


DOC: Add Craig as a maintainer

@eteq , is this the right way to update this file? Offline, you and Craig should meet to lay out scope and expectations. Thank you!

cc @brechmos-stsci

Actually... this is a good question we haven't decided for sure.  CODEOWNERs files are not just documentation - they also auto-set as reviewers, which is not quite the same as "maintainer" as in someone focused on infrastructure or the like.
As someone who's used CODEOWNER more than I, maybe @arfon can advise here?  Put more succinctly, the question is: would you say CODEOWNER is for "person who maintains the infrastructure", "person who reviews content", or both?
(Note mostly to self: we may want to back out #56 depending on the answer to the above.)
Regardless, though, this is a good ping to give @brechmos-stsci and @obviousrebel as maintainers in the team for this repo.  Will do that now.

As someone who's used CODEOWNER more than I, maybe @arfon can advise here? Put more succinctly, the question is: would you say CODEOWNER is for "person who maintains the infrastructure", "person who reviews content", or both?

IMO the CODEOWNERs we most need here are reviewers of content. Maintainers of the overall infrastructure/organization of the repo could be captured elsewhere?

Ops sorry. My bad. 😬
Is README a better place then?

Is README a better place then?

I'm not completely sure TBH. If we all agree that that CODEOWNERS file is most useful for would-be contributors opening pull requests on this repository (and looking for a review) then I think we should restrict CODEOWNERS to reviewers, and list the repo maintainers elsewhere. The README seems like as good a place as any?

After discussing the matter a bit, I think the best course is to have the CODEOWNERS be content as @arfon suggested, and have the infrastructure team be recorded as the GitHub team that has maintainer rights. I don't think there's really a need to keep it in the README itself since that would be duplicating the info that's already in the team membership (which I'll make public).
If that sounds good to you, @pllim and @arfon, we can close this and I'll open another PR with some updates to the codeowners (I've already updated the maintainers team)

If that sounds good to you, @pllim and @arfon, we can close this and I'll open another PR with some updates to the codeowners (I've already updated the maintainers team)

👍

Yes, I agree. Thanks for fixing this mess I created!


dumb-init: 1.2.4 -> 1.2.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/dumb-init/versions.
meta.description for dumb-init is: "A minimal init system for Linux containers"
meta.homepage for dumb-init is: "https://github.com/Yelp/dumb-init"
meta.changelog for dumb-init is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.2.5 with grep in /nix/store/0fqfkv7a3jvdjlzlnkc1r1mnvyyh98nj-dumb-init-1.2.5

directory tree listing: https://gist.github.com/f63cc7491d9da872ede2b4fc3b649b37

du listing: https://gist.github.com/66a7ca9174cb82a5bba63779f4ed13cd

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dumb-init

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0fqfkv7a3jvdjlzlnkc1r1mnvyyh98nj-dumb-init-1.2.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dumb-init https://github.com/r-ryantm/nixpkgs/archive/2ed911999cacb93c8ebc6ca51c013ccb680f1aeb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0fqfkv7a3jvdjlzlnkc1r1mnvyyh98nj-dumb-init-1.2.5
ls -la /nix/store/0fqfkv7a3jvdjlzlnkc1r1mnvyyh98nj-dumb-init-1.2.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dumb-init

Maintainer pings
cc @marsam for testing.

@GrahamcOfBorg eval

@GrahamcOfBorg eval


Add RepoLayoutRef for virtual repositories too

This PR adds support for repo_layout to virtual repositories too.
 $ make testacc
==> Checking that code complies with gofmt requirements...
==> Launching Artifactory in Docker...
42750aa9ca588f0967666b78a5a10cd885505bae48f8177534b20ff115805499
Waiting for Artifactory to start
.
.
.
.
.
.
.
TF_ACC=1 ARTIFACTORY_USERNAME=admin ARTIFACTORY_PASSWORD=password ARTIFACTORY_URL=http://localhost:8080/artifactory \
        go test ./... -v -parallel 20  -timeout 120m
?       github.com/atlassian/terraform-provider-artifactory     [no test files]
=== RUN   TestProvider
--- PASS: TestProvider (0.00s)
=== RUN   TestProvider_impl
--- PASS: TestProvider_impl (0.00s)
=== RUN   TestAccGroup_basic
--- PASS: TestAccGroup_basic (0.26s)
=== RUN   TestAccGroup_full
--- PASS: TestAccGroup_full (0.18s)
=== RUN   TestAccLocalRepository_basic
--- PASS: TestAccLocalRepository_basic (0.81s)
=== RUN   TestAccLocalRepository_full
--- PASS: TestAccLocalRepository_full (0.70s)
=== RUN   TestAccPermission_basic
--- PASS: TestAccPermission_basic (0.74s)
=== RUN   TestAccRemoteRepository_basic
--- PASS: TestAccRemoteRepository_basic (0.61s)
=== RUN   TestAccRemoteRepository_full
--- PASS: TestAccRemoteRepository_full (0.71s)
=== RUN   TestAccReplication_full
--- PASS: TestAccReplication_full (1.03s)
=== RUN   TestAccUser_basic
--- PASS: TestAccUser_basic (0.28s)
=== RUN   TestAccUser_full
--- PASS: TestAccUser_full (0.24s)
=== RUN   TestAccVirtualRepository_basic
--- PASS: TestAccVirtualRepository_basic (0.52s)
=== RUN   TestAccVirtualRepository_full
--- PASS: TestAccVirtualRepository_full (0.43s)
PASS
ok      github.com/atlassian/terraform-provider-artifactory/pkg/artifactory     (cached)
artifactory

CC @dillon-giacoppo

Any updates on this ?

It is expected that the IT would fail as the key cannot be decrypted from a fork (for obvious security reasons). I will update the build so it doesn't run IT on PRs. This field is undocumented in the API so I am hesitant to add it. I see there is also a PR for it in the client library. Let me test that first and then I can update this -- my main concern is that this will break existing configurations who do not already change it as it would get set to the default, if this is the case this PR will have to be a part of the next major release.

@dillon-giacoppo Thanks for getting back. You are right, not documented but I see it in GUI and I've tested it locally and it works. I will raise a support request so that JFrog update the REST API docs.

@dillon-giacoppo FY: JFrog Support submitted  a documentation change request for this (FYI there are other fields missing too in JSON docs).

@dillon-giacoppo JFrog has officially updated the documentation.
https://www.jfrog.com/confluence/display/RTF/Repository+Configuration+JSON