Preparing the release of v2.5.0

@ESMValGroup/esmvaltool-developmentteam
The next release of ESMValTool and ESMValCore are approaching (see schedule). As part of the release process, a candidate release has been made for the Core (v2.5.0rc2) following the feature freeze announcement.
We have now tested all the ESMValTool recipes against the candidate release rc2 for the Core (see next post).
Please note that the feature freeze for the Tool is schedule for Monday, Feb 21. Please let us know as soon as possible if you are still working on something for this release by adding your issue or pull request to our v2.5.0 milestone: https://github.com/ESMValGroup/ESMValTool/milestone/8

Recipe testing against v2.5.0rc2 of the Core
The result of the recipe testing is accessible at: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc2/
Among the 119 available recipes, 80 were ran successfully and 39 failed. A summary of the main failure reasons will be posted soon in this issue.
@ESMValGroup/esmvaltool-recipe-maintainers
Please check that your recipes ran successfully using the link above and let us know something needs to be corrected before the release. This includes that all plots are created and look fine, output files look fine, provenance is stored (checklist here and here).
Everyone can also help us by running a few recipes with the latest development installation in order to confirm these results.
Settings for the recipe testing
Most recipes were run using the Cylc suite using max_parallel_tasks: 8, a time limit of 4h, and 16 GB of RAM. The more memory-intensive recipes were run on a full prepost node. All recipes were run on Mistral using offline=False to automatically download missing data. A total of 110 GB was downloaded (59 GB of CMIP6 data and 52 GB of CMIP5 data). We would need to understand why these data are not available on Mistral. This goes beyond the recent deletion of some CMIP5 data.
And special thanks to @bouweandela for making the recipe testing much more convenient 🥳

Below we summarize all the issues found by the automatic run. Feel free to expand this table as you see fit.
Wontfix Issues
These issues will not be fixed in this release. They are generally due to data that has become unavailable or is not yet fully integrated into ESMValTool.

Missing data

Recipe
Reason of failure
Known problem?
Current Status

xxx
xxx
xxx
won't fix

Other problems

Recipe
Reason of failure
Known problem?
Current Status

xxx
xxx
xxx
won't fix

Outstanding Issues
Missing data

Recipe
Reason of failure
Known problem?
Current Status

xxx
xxx
xxx
xxx

Other problems

Recipe
Reason of failure
Known problem?
Current Status

xxx
xxx
xxx
xxx

Resolved Issues

Missing data

Recipe
Reason of failure
Known problem?
Current Status

xxx
xxx
xxx
xxx

Other problems

Recipe
Reason of failure
Known problem?
Current Status

xxx
xxx
xxx
xxx

The overview of issues found by running all recipes automatically is now complete (see post above). Please add already opened issues to the tables, we may have missed some.
It seems that the missing CMIP5 issue has slightly worsened since the last release (see #2408). But we were told that some deleted data will be retrieved from the archive soon.
We also have a few failures with the automatic download features (too long request on ESGF nodes, download failures, existing data but not found). Could someone else try to rerun some of the impacted recipes? I tried myself but got the same failures. I may not be using optimal settings for the automatic download. Any suggestion welcomed!

stellar work, guys! What's the actual problem with the two Julia recipes? For recipe_autoassess_landsurface_soilmoisture we have https://github.com/ESMValGroup/ESMValTool/issues/2309 - but should work on JASMIN where those files currently live, I'll have a test now :+1:

also, I'm gonna run a bunch of those CMIP5 missing recipes since we have CMIP5 on JASMIN (unlike some German HPC that did a terribly ungerman thing and deleted all that data :rofl: )

OK here's me stuffs on JASMIN:

recipe_anav13jclim.yml: missing a LOT of of OBS and two CMIP5 (even if I turn on auto dll): CMIP5_inmcm4: cSoil and CMIP5_inmcm4: cVeg
recipe_flato13ipcc.yml - missing OBS, CMIP3 and areacello fx files for abrupt mip - a total data mess
recipe_autoassess_landsurface_soilmoisture.yml - ran OK (phew)
examples/recipe_julia.yml - ran OK
recipe_rainfarm.yml - ran OK

let me know if you guys want me to run any others but bugger me flat, am missing lots of OBS's at JASMIN :mag:

What's the actual problem with the two Julia recipes?

Here is the type of error I am getting. Did I do something wrong when installing Julia? I simply followed the instructions and did esmvaltool install Julia which was successful.

you need to purge the (most probably existing) ~/.julia dir, re-create the env so Julia can be installed cleanly from conda-forge, install esmvaltool, then esmvaltool install Julia

We had two cases where using offline=true instead of offline=false was enough to run the recipe successfully: recipe_deangelis15nat.yml and recipe_mpqb_xch4.yml. In both cases, all the files needed are available in the official pool of CMIP5-6 data on Mistral and no data download is needed. Nevertheless, if the automatic download option is used, the tool will search for the many missing fx files on ESGF nodes in order to download these files which are later not used in the recipe. In particular the search for fx files took more than 12 hours (wall time on Mistral) for recipe_deangelis15nat.yml while the run with offline=true took 1 hour. Would this deserves a separate issue for further discussion?

yes - very good find, Remi! That's a pretty serious performance bug :bug:

also, I ran recipe_seaice.yml on JASMIN:
2022-02-16 16:48:03,524 UTC [20412] ERROR   Missing data for preprocessor seaice_tsline/areacello:
- Missing data for CMIP5_bcc-csm1-1-m_r0i0p0: areacello
- Missing data for CMIP5_inmcm4_r0i0p0: areacello
2022-02-16 16:48:03,524 UTC [20412] ERROR   Missing data for preprocessor seaice_trends/areacello:
- Missing data for CMIP5_bcc-csm1-1-m_r0i0p0: areacello
- Missing data for CMIP5_inmcm4_r0i0p0: areacello
2022-02-16 16:48:03,524 UTC [20412] ERROR   Missing data for preprocessor seaice_ecs/areacello:
- Missing data for CMIP5_bcc-csm1-1-m_historical_r0i0p0: areacello
- Missing data for CMIP5_bcc-csm1-1-m_rcp85_r0i0p0: areacello
- Missing data for CMIP5_inmcm4_historical_r0i0p0: areacello
2022-02-16 16:48:03,524 UTC [20412] ERROR   Missing data for preprocessor seaice_yod/areacello:
- Missing data for bcc-csm1-1-m_historical: areacello
- Missing data for inmcm4_historical: areacello

this is like shooting ducks with ballistic missiles: MRI has areacello in historical only but BCC has the same fx variable in piControl only - if we don't get the wildcard search in we'll always hit these sort of roadblocks; esgf-pyclient has no chance to retrieve it either if the same crappe is at other ESGF nodes too, it will just end up spending time looking around

@ESMValGroup/esmvaltool-recipe-maintainers
Please check that your recipes ran successfully using the link above and let us know something needs to be corrected before the release. This includes that all plots are created and look fine, output files look fine, provenance is stored (checklist here and here).

Should we do a comment with the list of full recipes and a checkbox for having them checked for the scientific ok - provenance and figures looking fine? Otherwise we never know if anyone actually looked at the output for the recipes that ran fine.

@bettina-gier yes that is a good idea always - maybe this can be done during the freeze, like we did during other releases :beer:

I just tried to identify the issue with recipe_smpi_4cds.yml. I think this might be related to memory issues: when using only the years 2001-2005 the diagnostic ua (all other diagnostics deactivated) the recipe runs fine, when using 2000-2005 (or the original range 1986-2005) the following error appears:
Traceback (most recent call last):
...
  File "/mnt/lustre01/pf/b/b309192/ESMValCore/esmvalcore/preprocessor/_multimodel.py", line 468, in multi_model_statistics
    group_statistics = _multiproduct_statistics(
  File "/mnt/lustre01/pf/b/b309192/ESMValCore/esmvalcore/preprocessor/_multimodel.py", line 370, in _multiproduct_statistics
    statistics_cubes = _multicube_statistics(cubes=cubes,
  File "/mnt/lustre01/pf/b/b309192/ESMValCore/esmvalcore/preprocessor/_multimodel.py", line 351, in _multicube_statistics
    result_cube = _compute_eager(aligned_cubes,
  File "/mnt/lustre01/pf/b/b309192/ESMValCore/esmvalcore/preprocessor/_multimodel.py", line 286, in _compute_eager
    single_model_slices = [cube[chunk] for cube in cubes]
  File "/mnt/lustre01/pf/b/b309192/ESMValCore/esmvalcore/preprocessor/_multimodel.py", line 286, in <listcomp>
    single_model_slices = [cube[chunk] for cube in cubes]
  File "/work/bd0854/b309192/soft/miniconda3/envs/core_rc2/lib/python3.10/site-packages/iris/cube.py", line 2323, in __getitem__
    dimension_mapping, data = iris.util._slice_data_with_keys(
  File "/work/bd0854/b309192/soft/miniconda3/envs/core_rc2/lib/python3.10/site-packages/iris/util.py", line 779, in _slice_data_with_keys
    raise IndexError("Cannot index with zero length slice.")

see https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc2/recipe_smpi_4cds_20220213_125027/run/main_log_debug.txt.
The weird thing is that I'm running this on a 256 GB node, and the output says Maximum memory used (estimate): 48.4 GB. Note that this is 4D (time, plev, lat, lon) data, so memory issues would not be surprising.

Yes, you're right!! It is related to this. Here is the output of some prints:
time: 71
slices_len 8
n_slices 10
start, end 0 8
start, end 8 16
start, end 16 24
start, end 24 32
start, end 32 40
start, end 40 48
start, end 48 56
start, end 56 64
start, end 64 71
start, end 72 71

The last indices are definitely not correct. I will try to fix this.
(the 48.4 GB referred to my run with only 6 year; the 187.4 GB correspond to using all 20 years)

Status of the release process and recipe testing:
Using the release candidate v2.5rc2 for the Core, we initially got 80 of 119 public recipes to run successfully during the automated testing. Over the past week, the number of successful recipes was increased to 96 by:

writing fixes for the Core
writing fixes for some recipes and diagnostics
manually downloading missing data
turning the automatic download feature off in a couple of cases

The latest fixes to the Core warrants another (an probably last) release candidate for the Core. @schlunma will soon release v2.5rc3. This will be done at the same time as the feature freeze for the Tool. We will perform another round of recipe testing and ask maintainers to check the output later this week.

Recipe testing against v2.5.0rc3 of the Core
The result of the recipe testing is accessible at: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc3/
Among the 120 available recipes, 96 were ran successfully and 24 failed.
Given the current uncertainties in the release process and the choice of iris version used for v2.5 (see https://github.com/ESMValGroup/ESMValCore/issues/1509), we may not need to ask recipe maintainers to check the results of their recipes at this stage. We will do so for the next round of recipe testing (most likely needed if iris=3.1 is chosen) or contact maintainers to check this round of recipe testing later on. Nevertheless, feel all free to take a look at your favourite recipes.
Summary of the main issues
6 recipes ran successfully with v2.5.0rc2 but not this time:

recipe_anav13jclim, recipe_climwip_brunner2019_med, recipe_schlund20esd
=> trouble to find all data needed (we have had some issues with CMIP5 data availability at DKRZ recently)

schlund20jgr/recipe_schlund20jgr_gpp_* (all three recipes)
=> diagnostic issue related to https://github.com/ESMValGroup/ESMValCore/issues/1509

Among the 18 other failing recipes, 1 "new" issue discovered:

recipe_impact (data issue at preprocessing stage)
=> https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc3/recipe_impact_20220223_103317/
In the previous round, the recipe didn't finish looking for data through ESGF nodes.

The 17 other failures remain unchanged:

recipe_autoassess_landsurface_soilmoisture_20220222_161348 and recipe_autoassess_radiation_rms_cfMon_all_20220223_082002
=> still not running on Mistral, better to test them on Jasmin
recipe_julia and recipe_rainfarm
=> still an issue for me to run Julia recipes...
recipe_check_obs => known in https://github.com/ESMValGroup/ESMValCore/issues/1388
recipe_climwip_brunner20esd, recipe_collins13ipcc, recipe_flato13ipcc, recipe_perfmetrics_CMIP5* (all 3), recipe_seaice,  recipe_wenzel14jgr, recipe_williams09climdyn_CREM
=> missing data issue
recipe_bock20jgr_fig_8-10
=> ESGF search takes longer than job wall time (see https://github.com/ESMValGroup/ESMValCore/issues/1495).
recipe_extreme_events
=> diagnostic (cdo) issue, see tables above.
recipe_carvalhais14nat
=> Matplotlib (norm, vmin, vmax) error (@schlunma, not sure how you got this running last time).

I wonder if we could speed-up the search on ESGF nodes for some recipes (recipe_anav13jclim, recipe_climwip_brunner2019_med, recipe_schlund20esd, recipe_bock20jgr_fig_8-10, but not only) by following this suggestion from @bouweandela regarding areacella. Of course, this wouldn't not apply to all cases, but it could help to save computing resources.

[ ] recipe_carvalhais14nat: I just found out that I was using matplotlib=3.4.3, but the error only appears in matplotib=3.5.1. I will have a look at that.

[ ] recipe_impact: That looks like a fix is needed for the dataset. I will also have a look at that.

[ ] recipe_schlund20esd: This one already has fx_variables: areacella, but needs LOTS of data. Not sure about the other recipes that ran into a timeout.

cheers @remi-kazeroni and @schlunma - for the Julia ones, have you nuked the presumably existent ~/.julia dir and still they don't run properly (after a reinstall with esmvaltool install Julia)? Yes, the Autoassess recipes run fine on JASMIN :+1:

Recipe testing against v2.5.0rc4 of the Core
The result of the recipe testing is accessible at: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc4/debug.html
You can also have a look at the recipe portal to browse these results: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc4/
Among the 121 available recipes, 111 were ran successfully and only 10 failed. This is the result of fixes to the Core, recipes/diagnostics and chasing missing data. A summary of the remaining failures in the next post.
This last round of recipe testing also shows nice improvement in the automatic download of data thanks to the updated esgf-pyclient package. The data search through ESGF nodes takes only minutes in cases where it used to take hours to find all the fx files (see https://github.com/ESMValGroup/ESMValCore/issues/1495). Thanks for your great work @bouweandela!
@ESMValGroup/esmvaltool-recipe-maintainers, it would be great if you could check the output of the recipes you are responsible for and tick the corresponding box if happy with the output (checklist here and here). If something does not look right, please let us know if this issue.
List of recipes:

[ ] recipe_bock20jgr_fig_1-4.yml
[ ] recipe_bock20jgr_fig_6-7.yml
[ ] recipe_bock20jgr_fig_8-10.yml
[ ] recipe_daily_era5.yml
[ ] recipe_era5-land.yml
[ ] recipe_check_obs.yml
[ ] recipe_concatenate_exps.yml
[ ] recipe_correlation.yml
[ ] recipe_decadal.yml
[ ] recipe_extract_shape.yml
[ ] recipe_julia.yml
[ ] recipe_my_personal_diagnostic.yml
[ ] recipe_ncl.yml
[ ] recipe_preprocessor_derive_test.yml
[ ] recipe_preprocessor_test.yml
[ ] recipe_python.yml
[ ] recipe_r.yml
[ ] recipe_variable_groups.yml
[ ] recipe_globwat.yml
[ ] recipe_hydro_forcing.yml
[ ] recipe_hype.yml
[ ] recipe_lisflood.yml
[ ] recipe_marrmot.yml
[ ] recipe_pcrglobwb.yml
[ ] recipe_wflow.yml
[ ] recipe_mpqb_xch4.yml
[ ] recipe_albedolandcover.yml
[ ] recipe_anav13jclim.yml
[ ] recipe_arctic_ocean.yml
[ ] recipe_autoassess_landsurface_permafrost.yml
[ ] recipe_autoassess_landsurface_soilmoisture.yml
[ ] recipe_autoassess_landsurface_surfrad.yml
[ ] recipe_autoassess_radiation_rms_Amon_all.yml
[ ] recipe_autoassess_radiation_rms_Amon_obs.yml
[ ] recipe_autoassess_radiation_rms_cfMon_all.yml
[ ] recipe_autoassess_stratosphere.yml
[ ] recipe_capacity_factor.yml
[ ] recipe_carvalhais14nat.yml
[ ] recipe_climwip_brunner2019_med.yml
[ ] recipe_climwip_brunner20esd.yml
[ ] recipe_climwip_test_basic.yml
[ ] recipe_climwip_test_performance_sigma.yml
[ ] recipe_clouds_bias.yml
[ ] recipe_clouds_ipcc.yml
[ ] recipe_cmug_h2o.yml
[ ] recipe_collins13ipcc.yml
[ ] recipe_combined_indices.yml
[ ] recipe_consecdrydays.yml
[ ] recipe_cox18nature.yml
[ ] recipe_cvdp.yml
[ ] recipe_deangelis15nat.yml
[ ] recipe_diurnal_temperature_index.yml
[ ] recipe_eady_growth_rate.yml
[ ] recipe_ecs_constraints.yml
[ ] recipe_ecs_scatter.yml
[ ] recipe_ecs.yml
[ ] recipe_ensclus.yml
[ ] recipe_esacci_lst.yml
[ ] recipe_esacci_oc.yml
[ ] recipe_extreme_events.yml
[ ] recipe_extreme_index.yml
[ ] recipe_eyring06jgr.yml
[ ] recipe_eyring13jgr_12.yml
[ ] recipe_flato13ipcc.yml
[ ] recipe_gier2020bg.yml
[ ] recipe_heatwaves_coldwaves.yml
[ ] recipe_hyint_extreme_events.yml
[ ] recipe_hyint.yml
[ ] recipe_impact.yml
[ ] recipe_kcs.yml
[ ] recipe_landcover.yml
[ ] recipe_lauer13jclim.yml
[ ] recipe_li17natcc.yml
[ ] recipe_martin18grl.yml
[ ] recipe_meehl20sciadv.yml
[ ] recipe_miles_block.yml
[ ] recipe_miles_eof.yml
[ ] recipe_miles_regimes.yml
[ ] recipe_modes_of_variability.yml
[ ] recipe_monitor.yml
[ ] recipe_multimodel_products.yml
[ ] recipe_ocean_amoc.yml
[ ] recipe_ocean_bgc.yml
[ ] recipe_ocean_example.yml
[ ] recipe_ocean_ice_extent.yml
[ ] recipe_ocean_Landschuetzer2016.yml
[ ] recipe_ocean_multimap.yml
[ ] recipe_ocean_quadmap.yml
[ ] recipe_ocean_scalar_fields.yml
[ ] recipe_perfmetrics_CMIP5_4cds.yml
[ ] recipe_perfmetrics_CMIP5.yml
[ ] recipe_perfmetrics_land_CMIP5.yml
[ ] recipe_pv_capacity_factor.yml
[ ] recipe_quantilebias.yml
[ ] recipe_radiation_budget.yml
[ ] recipe_rainfarm.yml
[ ] recipe_runoff_et.yml
[ ] recipe_russell18jgr.yml
[ ] recipe_schlund20esd.yml
[ ] recipe_seaice_drift.yml
[ ] recipe_seaice_feedback.yml
[ ] recipe_seaice.yml
[ ] recipe_sea_surface_salinity.yml
[ ] recipe_shapeselect.yml
[ ] recipe_smpi_4cds.yml
[ ] recipe_smpi.yml
[ ] recipe_snowalbedo.yml
[ ] recipe_spei.yml
[ ] recipe_tcr.yml
[ ] recipe_thermodyn_diagtool.yml
[ ] recipe_toymodel.yml
[ ] recipe_validation_CMIP6.yml
[ ] recipe_validation.yml
[ ] recipe_wenzel14jgr.yml
[ ] recipe_wenzel16jclim.yml
[ ] recipe_wenzel16nat.yml
[ ] recipe_williams09climdyn_CREM.yml
[ ] recipe_zmnam.yml
[ ] recipe_schlund20jgr_gpp_abs_rcp85.yml
[ ] recipe_schlund20jgr_gpp_change_1pct.yml
[ ] recipe_schlund20jgr_gpp_change_rcp85.yml

Summary of the main issues

[ ] recipe_autoassess_landsurface_soilmoisture: to be tested on Jasmin (@valeriupredoi)
[ ] recipe_autoassess_radiation_rms_cfMon_all: to be tested on Jasmin (@valeriupredoi)
[ ] recipe_check_obs: won't fix for this release (https://github.com/ESMValGroup/ESMValCore/issues/1388)
[ ] recipe_climwip_brunner20esd: known missing CMIP6 data (CMIP6_CESM2_r1i1p1f1: tas and CMIP6_CESM2_r2i1p1f1: tas)
[ ] recipe_collins13ipcc: known missing CMIP5 areacello data (see #2408)
[ ] recipe_extreme_events: known cdo issue in diagnostics
[ ] recipe_flato13ipcc: known missing CMIP5 areacello data
[ ] recipe_perfmetrics_land_CMIP5: new data issue (wont fix). This bug has appeared after we managed to download all the data needed
[ ] recipe_seaice: known missing CMIP5 areacello data (#2408 to be updated)
[ ] recipe_wenzel14jgr: new diagnostic issue discovered after getting all the data needed to run the recipe

excellent work guys! I'll test the AA recipes on JASMIN, so we have only 8 crappe'd :grin:

the cfMon_all AA recipe dies with the usual
esmvalcore.cmor.check.CMORCheckError: There were errors in variable clisccp:
 Coordinate plevs has var name plev7 instead of plev
 tau: standard_name should be atmosphere_optical_thickness_due_to_cloud, not None
 clisccp: does not match coordinate rank
in cube:

issue coz of the ISCCP data on JASMIN - I can turn that dataset off, but I know for a fact that that should work if we fix the ISCCP data, what do you recommend @remi-kazeroni ? The other AA went through no problemo

awesome, yeah - I believe I opened that issue judging by the title containing semi-expletives :sweat_smile:

Status of the recipe testing using the version v2.5.0rc4 for the Core: there are up to 115 recipes that can be run successfully. Among the remaining 6 recipes, there should not be any missing data problem any more (CMIP5, CMIP6, OBS,...). For each failing recipe, there is a dedicated issue or PR to fix it. In the (hopefully 😆) last round of testing, we need to pay closer attention to the recipe_perfmetrics_land_CMIP5 (model fix needed?) and the recipe_collins13ipcc. For the later one, there is probably not enough memory on the Mistral nodes to run it. But maybe it could work with Levante, worth trying.

@remi-kazeroni stellar work! Do we have a mention in the documentation of that recipe that needs gargantuan amounts of memory?

Recipe testing against v2.5.0rc6 of the Core
The result of the recipe testing is accessible at: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc6/debug.html
You can also have a look at the recipe portal to browse these results: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.5.0-test-rc6/
Among the 121 available recipes, 114 were run successfully and only 7 failed. Since the outcome of this round of testing is identical to the previous one, there is no need for another thorough recipe output checking. Nevertheless, feel free to check the output of your favourite recipe if you wish. I think this round of testing is good enough to do the release next week 🍻  No new bug was discovered during this testing. Among the 7 known issues, we have:

[ ] recipe_autoassess_landsurface_soilmoisture: to be tested on Jasmin (@valeriupredoi; see also #2309)
[ ] recipe_autoassess_radiation_rms_cfMon_all: see https://github.com/ESMValGroup/ESMValCore/issues/1238
[ ] recipe_check_obs: see https://github.com/ESMValGroup/ESMValCore/issues/1388
[ ] recipe_collins13ipcc: not enough memory on Mistral. We could try soon on Levante
[ ] recipe_extreme_events: see #2576
[ ] recipe_flato13ipcc: see #2156
[ ] recipe_perfmetrics_land_CMIP5: data issue seen now that the data finding step is passed. @schlunma: could you open an issue for that recipe if you understand the reason for the failure? It'd good to keep track of all failures.

make that 6 now :grin: so that's a 5% loss ratio - am very happy and it's a good start for my day off today - excellent work the Release Boys :beer:

I forgot to write that I needed to remove some output files (mostly netcdf files) for the recipe runs that required lots of disk space. The reason is that the recipe outputs are copied to the disk of the bot VM. Disk space there is limited to 1TB while some recipes produce 10GB - 100GB of data (even with the /preproc direcrotry removed). In some cases, there was not much left to check as some recipes do not produce plots but large nc files.
To help checking recipes, I have rerun 2 recipes successfully: recipe_wflow (all netcdf files kept) and recipe_daily_era5 (some netcdf files kept). @axel-lauer: do you want to have another look at these 2 recipes?

@axel-lauer: do you want to have another look at these 2 recipes?

Thanks @remi-kazeroni. As far as I can tell, the output of the two recipes looks OK. I updated the list above.

Closing this now since v2.5.0 is out :tada: Thanks to everyone who contributed to this!
An issue is open for every failing recipe; let's move the discussion to these. Cheers!!


[Settings | Desktop] Components Implementation

Components Implementation
Settings | Desktop
New components available for anyone that wants to contribute to the new design (kibbeh). Make sure to read the guidelines at the bottom of the issue.

New components

[x] SettingsWrapper - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9018%3A9349

Requires none ✅
Container for each page in settings (padding: 20px or .p-4)

[x] BaseSettingsItem - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A69

Requires none ✅
Container/Wrapper for some settings items, size can (and must) vary

[ ] ChangeAvatarCard - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9018%3A9352

Requires BaseSettingsItem, UserAvatar, Button ❌

[x] ChangeBannerCard - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9018%3A9354

Requires Button ✅

[ ] NativeCheckbox - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A0

Requires none ✅
The on/off functionality is important

[ ] NativeRadio - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9018%3A9356

Requires none ✅
Handle children (text) as you think is best

[ ] ErrorButtonItem - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A5

Requires  BaseSettingsItem, Button ❌

[x] VolumeIndicator - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A58

Requires none ✅
It should react to some value (convert it to percentage maybe)

[ ] UserWideButton - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A3

Requires UserAvatar, Button ✅

[ ] SettingsItemButton - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A87

Requires  BaseSettingsItem, Button ❌

[ ] KeybindCard - https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9055%3A18

Requires BaseSettingsItem ❌
Should match current behavior with regard to listening for user input after the keyboard icon is pressed
The red border appears when the listening mode is on

Guidelines:

Don't add margin around the components.
The bordered rectangle around each component in Figma is just for delimitation purposes.
Put your component in kibbeh/src/ui and create a story in kibbeh/src/stories.
Use tailwind for styling (see the tailwind config for theme info).
You have to use TypeScript.
Work on the staging branch.
Please comment below if you start to work on a component, but only claim a component if you plan to work on it right away, so it doesn't block other people.
Don't start working on a component if its dependencies aren't done.

Mockup & grid (get some context about each component): https://www.figma.com/file/CS01VVLR7ArQl0afYFkNj3/Web-App?node-id=9018%3A1060

Most icons should be available under kibbeh/src/icons, but if the one you need isn't, ask on Discord or place a temp one with a comment pointing it out

If you have any questions ask Ben or @ ajb on Discord.

I'll do ErrorButtonItem and KeybindCard once their dependencies are done.

I'll do SettingsItemButton once its deps are finished. And ChangeAvatarCard

I would like to do NativeRadio

I would like to do NativeRadio

I called it my guy 😅

Well you took two components

But sure it's yours

I'll take VolumeIndicator

I'll do ChangeBannerCard

I would like to work on UserWideButton

Most of these components should've been done already, they shouldn't take that long.
has anyone abandoned a component?

Prerequisite components are delaying work on other components. I've been waiting for BaseSettingsItem

No takers for SettingsWrapper? Looks quite straightforward, I can do it.

I'm also going to take "BaseSettingsItem". It's just a container component and was claimed 3 days ago. It should not take that long imo

I'm still working on NativeRadio and NativeCheckbox. They'll be done soon 😎

@ajmnz for NativeRadio you want the cards to be var(--text-primary-900) or var(--text-primary-800)? It's just inconsistent with the figma preview. Every component is 800 but in figma its 900

#2261

Prerequisite components are delaying work on other components. I've been waiting for BaseSettingsItem

You can start now

#2267 - ErrorButtonItem added

@Ongshu777, have you done ChangeAvatarCard?
And sorry for not doing BaseSettingsItem, I was busy.

#2282 - KeybindCard component added

@Mvrs @Ongshu777 What's your progress? Free them up if you aren't able to work on them right away

@Mvrs @Ongshu777 What's your progress? Free them up if you aren't able to work on them right away

Will be done by 7pm PST. I should be done well before that.

@Mvrs @Ongshu777 What's your progress? Free them up if you aren't able to work on them right away

Yea, I'm don't have time, I'll let someone else do it.

@Mvrs @Ongshu777 What's your progress? Free them up if you aren't able to work on them right away

Yea, I'm don't have time, I'll let someone else do it.

I'll do ChangeAvatarCard if no one has picked it up

#2298 - added ChangeAvatarCard

@ajmnz give me tmr 6am PST. I had a huge 5 hr bug and I'm rolling now. My bad. Last extension 🙏🏿🥲

@Mayowa-Ojo you wanna take NativeCheckbox? I'm too tired now 😅.

Almost done with Checkbox just a quick UI then it's a wrap 🥲🚀


Increment version for redis releases

Increment package version after release of Azure.ResourceManager.Redis

API change check
API changes are not detected in this pull request.

/check-enforcer override

Failure is unrelated to these changes; merging.


DNS monitoring for SingleServerConnection

With AWS ElastiCache replication groups there is no autodiscovery of nodes or in-client notification of failovers. Instead Elasticache changes the primary endpoint DNS to point to the newly promoted master. This leads to issues like https://github.com/mrniko/redisson/issues/241
This change allows monitoring of the endpoint to see if the underlying host address has changed. If it has changed, changeMaster() is invoked to shutdown the old client and start a new one.
Example code for testing:
    public static void main(String[] args) {
        // must ensure the JVM isn't caching DNS lookups
        java.security.Security.setProperty("networkaddress.cache.ttl", "1");
        Config config = new Config();
        config.useSingleServer().setAddress(args[0]).setDnsMonitoring(true);
        Redisson r = Redisson.create(config);
        RAtomicLong al = r.getAtomicLong("testLong");
        while (true) {
            try {
                System.out.println(System.currentTimeMillis() +":"+ al.addAndGet(1));
            } catch (Throwable t) {
                System.out.println("Exception: " + t);
                t.printStackTrace(System.out);
            }
            try {
                Thread.sleep(1000);
            } catch (InterruptedException ignored) {}
        }

    }

example output, slave node is promoted while program runs:
1441910645627:372
1441910646632:373
1441910647635:374
1441910648638:375
Exception: org.redisson.client.RedisException: READONLY You can't write against a read only slave.. channel: [id: 0x3fddcec0, /10.0.x.x:52894 => foo.xxxxx.ng.0001.use1.cache.amazonaws.com/10.0.y.y:6379] command: CommandData [promise=DefaultPromise@6c65b2aa(incomplete), command=RedisCommand [name=INCRBY, subName=null], params=[testLong, 1], codec=org.redisson.client.codec.StringCodec@22341d23]
org.redisson.client.RedisException: READONLY You can't write against a read only slave.. channel: [id: 0x3fddcec0, /10.0.x.x:52894 => foo.xxxxx.ng.0001.use1.cache.amazonaws.com/10.0.y.y:6379] command: CommandData [promise=DefaultPromise@6c65b2aa(incomplete), command=RedisCommand [name=INCRBY, subName=null], params=[testLong, 1], codec=org.redisson.client.codec.StringCodec@22341d23]
	at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:168)
	at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:104)
...
[globalEventExecutor-1-1] INFO org.redisson.connection.SingleConnectionManager - Detected DNS change. foo.xxxxx.ng.0001.use1.cache.amazonaws.com has changed from 10.0.y.y to 10.0.z.z
[globalEventExecutor-1-1] INFO org.redisson.connection.SingleConnectionManager - Master has been changed
1441910725723:376
1441910726726:377

FYI I'm working on a ElasticacheReplicationGroupServersConfig that is similar to the ClusterConfig, except it uses INFO replication to determine node role instead of CLUSTER commands.  So there's no auto-discovery of nodes, but it will handle role changes in a more efficient manner than monitoring DNS (as this PR does).
work in progress: https://github.com/scubasau/redisson/commit/3c5346f97eee259b0b59d591641625c297c0e04d

thank you


"No preset version installed for command" message although one was set in .tool-versions

Describe the bug
When I open my terminal, I get the following messaes:
No preset version installed for command oc
Please install a version by running one of the following:

asdf install oc latest

or add one of the following versions in your config file at /home/eisraeli/.tool-versions
oc 4.13.13
oc 4.14.10

No preset version installed for command kubectl
Please install a version by running one of the following:

asdf install kubectl latest

or add one of the following versions in your config file at /home/eisraeli/.tool-versions
kubectl 1.25.4
kubectl 1.26.1
kubectl 1.26.2
kubectl 1.28.2
kubectl 1.29.3
kubectl 1.30.0

BUT
My `~/.tool-versions"  contains:
oc latest
kubectl latest

On top of that, oc version --client output:
Client Version: 4.17.5

and kubectl --client output:
Client Version: v1.31.3

To Reproduce
Running mise 2024.11.27 linux-x64 (5562f2f 2024-11-23)
Steps described above.
Expected behavior
Mise should recognize that I have configured the latest version in .tool-versions

this error is coming from asdf


Fixed scylladb backend init-store failed

The exception is "Indexes are not supported yet"
Change-Id: I5012e2684b7d95ded236207b441fc71d77851fe7

done

hbase ci failed due to not rebase

rebased


[WIP] Disable KeepAlives for HA tests

Trying to see if it affects errors in the HA tests.

/test pull-knative-net-kourier-integration-tests

/test pull-knative-net-kourier-integration-tests

/test pull-knative-net-kourier-integration-tests

OK. The latest failure shows that disabled KeepAlives don't make a difference.


[AKS] Add "--skip-role-assignment" flag and support creation on same role assignment

This PR mainly has following changes:

add '--skip-role-assignment' which allows customer to skip role assignment for customVnet when creating AKS cluster.
2)If role assignment for customVnet  already exists, new AKS creation will not fail, and continue provisioning.
remove non-used fields in AgentPoolProfile

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

do we still create subscription scope role assignment when SP is not provided? if so, can you open a bug?

We don't create role assignment when SP not provided when use az aks create

@zqingqing1 one last thing, can you rebase from dev to get updates?


[docs] Mention llf in existing tools

Hi!
Since I see you have a list of existing tools, I figured you might want to add llf to that list, which is also (compared to latexindent) very fast.

Thanks for the suggestion; I did not know about llf. However I'm having some trouble getting it to work:
lua: llf/llf.lua:144: attempt to call field 'codes' (a nil value)

Thanks for this! I am using NixOS so prefer to avoid global installs if possible. I'll see if I can get it working with a user installation.

As a quick follow-up in case you are interested, I got this working in an isolated env:
git clone https://github.com/engeir/teaching-setup.git
cd teaching-setup
sudo ./run.sh

Inside the new terminal window that pops up:
curl https://mise.run | sh
/home/username/.local/bin/mise use lua
/home/username/.local/share/mise/shims/luarocks install lpeg
/home/username/.local/share/mise/shims/luarocks install wcwidth
/home/username/.local/share/mise/shims/luarocks install utf8
git clone git://repo.or.cz/llf.git
cd llf
/home/username/.local/bin/mise use neovim
/home/username/.local/share/mise/shims/nvim Makefile  # edit prefix to ~/.local
make install
/home/username/.local/bin/llf <test-in.tex>test-out.tex

I have added a note to the README


Lacking support for CommonJS

Operative plays nice with AMD but resorts to a global in CommonJS loaders. Here's an example of a Universal Module Definition that covers all bases.

Hmm yeh should probably get this in. Thanks for opening an issue! Up for putting together a PR?

@padolsey done! Sorry for the delay :)

Thanks!!

No worries :)
Sent from my iPhone

On Apr 20, 2015, at 3:46, James Padolsey<EMAIL_ADDRESS>wrote:
Thanks!!
—
Reply to this email directly or view it on GitHub.

Hey @padolsey - bad news :(
Because some of the submodules (eg. OperativeContext.js) are relying on the global operative, this still doesn't work well in a bundle. I see two routes from here:

Remove checks for both AMD and CommonJS, create a global operative by default, and leave the Grunt concatenation untouched.
Rewrite the modules to use AMD or CommonJS, and bundle them with something like grunt-browserify.

Option 1 has the advantage of minimizing change to the library, and removes the need for more complex bundlers (it's just concatenated .js files). Option 2 has the advantage of allowing the library to be consumed transparently by any client, and removing an unnecessary global in bundled settings.
Sorry to bring this back up - I thought https://github.com/padolsey/operative/pull/34 was sufficient, but I hadn't considered the other files that are concatenated with operative.js...

I can make a PR for either option, just wanted to get your thoughts before moving ahead.

Ah, yep, I should have noticed that. Definitely up for option #2 if you have the time. The concatenation is a bit of a mess now.

Though option 2 has obvious benefits, lines like this might make it pretty hard to remodel. For the time being I think that unbreaking things quickly with a global is the right course of action.
Let me know what you think! Sorry this wasn't as easy as I'd initially thought.

(see https://github.com/padolsey/operative/pull/38)

That __run__ would only be exposed in the generated iframe, but I still agree that this all might be more trouble than it's worth (at least at the moment). Shall look into your PR.

(Closing for now; I would very much like to revisit this at some point though)


Azure Front Door Standard/Premium tier is now GA

Removing preview note

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

ID: 52009ea9-bd18-16cf-30cc-5ab2b85d0d44
Version Independent ID: 56a1a5c6-c760-e0e9-e6c7-2e9687bcc775
Content: Azure Front Door - URL Redirect
Content Source: articles/frontdoor/front-door-url-redirect.md
Service: frontdoor
GitHub Login: @duongau
Microsoft Alias: duau

Working on a PR to remove this note


stdin?

How would you feed a string to stdin of spawned child process?

The following should work:
var spawn = require('child-process-promise').spawn;

spawn('echo', ['hello'])
    .progress(function (childProcess) {
        console.log('[spawn] childProcess.pid: ', childProcess.pid);
        child.stdin.setEncoding('utf-8');
        child.stdin.write('Foo');
    })
    .then(function () {
        console.log('[spawn] done!');
    })
    .fail(function (err) {
        console.error('[spawn] ERROR: ', err);
    });

Thanks! :+1:
Had to change to child.stdin.end() to give it a kick.


Question: is it possible to combine multiple gvadetect and gvaclassify into one pipeline?

Hello,
I'm trying to create a pipeline where I do people detection -> Face detection -> Age/gender recognition as follows:
gst-launch-1.0 filesrc location=./videos/face-demographics-walking-and-pause.mp4 \
! decodebin ! gvadetect model=./person-detection-0200/person-detection-0200.xml \
! gvadetect model=./face-detection/face-detection-retail-0004.xml \
! gvaclassify model=./age/age-gender-recognition-retail-0013.xml model-proc=/opt/intel/openvino_2021/data_processing/dl_streamer/samples/gst_launch/face_detection_and_classification/model_proc/age-gender-recognition-retail-0013.json \
! gvametaconvert json-indent=4 \
! gvametapublish method=file file-path=./tmp/face.json \
! gvawatermark ! xvimagesink

However, the age-gender recognition takes both (people detection and age/gender recognition) as input.
Is it possible to tell gvaclassify to only use the input from face detection? or should I be creating two different pipelines for that purpose?

Closing this issue.


format: md front matter doesn't work

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
The docs say that adding format: md front matter makes the doc to be CommonMark format, but it doesn't work.
After looking into the code, it should be
---
mdx:
  format: md
---

It reads the mdx in front matter first
https://github.com/facebook/docusaurus/blob/a4fa4c27f1321617054d69ff930c765edcb5da7b/packages/docusaurus-mdx-loader/src/utils.ts#L99-L105
https://github.com/facebook/docusaurus/blob/a4fa4c27f1321617054d69ff930c765edcb5da7b/packages/docusaurus-mdx-loader/src/processor.ts#L266-L285
But the docs say it's format in front matter.
https://github.com/facebook/docusaurus/blob/a4fa4c27f1321617054d69ff930c765edcb5da7b/website/docs/guides/markdown-features/markdown-features-react.mdx?plain=1#L251
https://github.com/facebook/docusaurus/blob/a4fa4c27f1321617054d69ff930c765edcb5da7b/website/docs/guides/markdown-features/markdown-features-intro.mdx?plain=1#L44
Should it be fixed in the code or in the docs?
Reproducible demo
No response
Steps to reproduce

add format: md front matter in .mdx file
nothing happened

Expected behavior
Doc changes to CommonMark syntax.
Actual behavior
Doc stay with JSX syntax
Your environment

Public source code:
Public site URL:
Docusaurus version used: v3
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[ ] I'd be willing to fix this bug myself.

Damn, yes you are right 😅

Should it be fixed in the code or in the docs?

Hmmm, I don't know. I'd like to have format: instead of mdx.format but at the same time it's possible that we add extra options under the mdx namespace. I think we should just fix the docs.


Add Raleigh Main Events to the CityCampNC Partners page

Add Raleigh Main Events to the CityCampNC Partners page as a Community Partner.

twitter handle @raleighMAIN

Good call

I don't have a logo and I need a website not a twitter handle

http://www.raleighmainevents.com/
[image: Inline image 1]
?
On Wed, Sep 20, 2017 at 5:14 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

I don't have a logo and I need a website not a twitter handle
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/737#issuecomment-330983120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH9zc5oJ2bE61XyLpGn6-vS0vNI5HJ8Rks5skYBLgaJpZM4PdOfj
.

http://www.raleighmainevents.com/
On Wed, Sep 20, 2017 at 5:37 PM, snewt-n<EMAIL_ADDRESS>wrote:

http://www.raleighmainevents.com/
[image: Inline image 1]
?
On Wed, Sep 20, 2017 at 5:14 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

I don't have a logo and I need a website not a twitter handle
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/737#issuecomment-
330983120>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH9zc5oJ2bE61XyLpGn6-
vS0vNI5HJ8Rks5skYBLgaJpZM4PdOfj>

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/737#issuecomment-330988397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoVzBAF3h0gTNE7agrutw3GIcK3vvgks5skYWWgaJpZM4PdOfj
.


Fix wrong font in Event Configuration

Fixes #73445
get_theme_font() can't be used inside constructor.

Thanks!


Fix Cargo.toml typo in package.links

Fixes #4

See also #3. My reasoning might have been that Qook would have a separate shared library interface, but there's no need, relative the one for Python. WASM uses a different shared library, but the interface requirements are substantially different, there.


Stateful Log Alerts are in Preview

Looking for docs on how to use azure monitor stateful log alerts but it's not here

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

ID: deacb2ef-8b79-04c3-eee9-643714145db5
Version Independent ID: 59625313-cf00-2d17-51a1-d4c683b8d151
Content: Log alerts in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/alerts/alerts-unified-log.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @yanivlavi
Microsoft Alias: yalavi

@cconrado Thanks for the feedback.
This document will be updated soon with the required information.
FYI, this issue is probably a duplicate of https://github.com/MicrosoftDocs/azure-docs/issues/74556.

The document now contains information about Stateful log alerts as well. Thanks.


[Sui Framework] Expose getter for current epoch number

Also expose a test-only function for advancing the epoch number. This is useful for contracts that need time, at least until we have a more fine-grained timestamping scheme.

Although I don't mind adding the getter, I think this might be the wrong way to expose epoch: anyone who wants to access epoch number has to pass in a shared object. Should we add epoch to TxContext?

Yep, great call on TxContext--fully agree. I filed https://github.com/MystenLabs/sui/issues/1980 for this


[Core] az extension add/update and az upgrade: Pre-announcement default value change from true to false for --allow-preview

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.


Dig conformance testing

TODO

[x] failing spec: handle out-of-bounds indexes into Structs
[x] broken spec: probe for range support before testing ranges on String#[] and Integer#[] (unsupported in 2.6.x)

There's more work to be done here, but merging for now as 1) we're green, and 2) I'd like to work on other features for a bit


If the argument of mask image is empty in createImageEdit(), the API will result in error

Describe the bug
according to the api.ts
the function createImageEdit is defined as
createImageEdit: async (image: File, prompt: string, mask?: File, n?: number, size?: string, responseFormat?: string, user?: string, options: AxiosRequestConfig = {}):

It is documented as
* @param {File} [mask] An additional image whose fully transparent areas (e.g. where alpha is zero) indicate where `image` should be edited. Must be a valid PNG file, less than 4MB, and have the same dimensions as `image`.

Found problem,

In the current document, it is referred to the version 3.1.0.
In the document, it is described to be optional.

In 3.2.1, if it is being left out, error will be prompted.
To Reproduce

call createImageEdit
leave the mask argument blank with empty string ''
submit to run and will see the error.

Code snippets
const completion = await openai.createImageEdit(
                    readStream, // File stream for the original image
                    "A cute baby sea otter wearing a beret",
                    '', // leave back for testing, if using a mask, will be fine
                    2,
                    "256x256"
                  );

The test is conducted with original and mask image.

OS
macOS 12.6.3
Node version
v16.17.1
Library version
openai 3.2.1

Why can't my code work properly even with a mask

Why can't my code work properly even with a mask, the order of my parameters is the same as yours, but the request failed with status code 400

Why can't my code work properly even with a mask, the order of my parameters is the same as yours, but the request failed with status code 400

https://github.com/openai/openai-node/issues/84#issuecomment-1482220469

Why can't my code work properly even with a mask, the order of my parameters is the same as yours, but the request failed with status code 400

Are you using 3.1.0 or 3.2.1? There is another problem in 3.2.1, the argument position is swapped and not same as 3.1.0 as documented.

Sorry for the breaking swap in parameter order!
Our new v4 of this library uses an object to specify these parameters, which you can use like so:
await openai.images.edit({
  image: fs.createReadStream("otter.png"),
  mask: fs.createReadStream("mask.png"),
  prompt: "A cute baby sea otter wearing a beret",
  n: 2,
  size: "1024x1024",
})

I hope this reduces any similar confusion, here and in the future.
Related: https://github.com/openai/openai-node/issues/95


Add the SA58 FAL mod to the modpack

Summary
The SA58 FAL mod allows up to 9 different variations of the FAL from coldwar to modern-Anomaly Tarkov era FALs.
Basic example
https://www.nexusmods.com/fallout4/mods/40907
Motivation
I've been playing with mods in Bethesda games for more than a decade and this mod itself is one of the highest quality gun mods I've ever seen in a game. Although the mod does come with some weird immersion breaking locations, it can easily be fixed with this mod
https://www.nexusmods.com/fallout4/mods/49717?tab=files

Thank you, I will look into it! Awesome motivation.


Embedded Map: Powered by graphic flashes big while map is loading and then never shows up below map

Overview
In the design of the Embedded Map, a small graphic that says "Powered by the OAR" is meant to appear in the bottom corner of each Embedded Map. It is currently not displaying on live Embedded Maps. Instead, when the map is loading, it flashes in a large size and then disappears when the map loads.
Expected Behavior
The powered by OAR graphic should appear in the bottom corner of the Embedded Map and not show up in a huge size when loading.
Actual Behavior
We are not seeing the powered by OAR graphic on Embedded Maps and the loading behavior with the large graphic is occurring.
Steps to Reproduce
Load live Embedded Maps on any of these sites to observe (you'll want to scroll to the part of the page with the map to observe loading:
https://www.levistrauss.com/sustainability-report/community/supplier-map/
https://www.textilbuendnis.com/en/lieferkettentransparenz/
Demo
Captured a video of the behavior here: https://us02web.zoom.us/rec/share/DY7yHahVQjPA4xRbw9YOo-4aaTfg0CyGecRmx3BMrnDESV5NL1a4howqyV0kCtwA.0VoVzHsjVyxUb1bd Passcode: +^Tr0Db1
cc @katieashaw

@mariel-oar I am no longer seeing this behavior. Feel free to close.


Control over what version of glibc is used

I currently use this to cross compile to a few platforms, and it works great! One issue I'm having is the resulting binary is always built with a recent (ish) version of glibc and some of our servers are running an older version of glibc, meaning they can't be run in the native environment.
I understand this package is already doing a lot and this might be out of scope, I'm not entirely sure what needs to change but I'd imagine it has something to do with the Dockerfile using bullseye and not an older environment like stretch? It would be awesome if you were able to choose which environment to use!

Hi @jhwz
I think the sysroot is what you are looking for 😉
the example is using custom sysroot with all custom libs including glibc.
Let me know if you need any more help with this topic.

I was coming to that conclusion!
I tried it out and had a few issues with the compiler not being able to find libgcc_so.1:
# runtime/cgo
/usr/bin/ld: cannot find libgcc_s.so.1
collect2: error: ld returned 1 exit status

To extract the sysroot I used the script given, but looking at the custom sysroot repo you linked the sysroot has symlinks that I don't have so there's a chance I'm getting something wrong.. Will keep having a play when I have time!

Yeah, symlinks are the hard part when they are absolute.
You may need to tinker with PKG_CONFIG_PATH  check here and CGO_C(XX)FLAGS.
Should be pretty much it. We've done it on different sorts of projects

Ahh I had briefly looked at that but didn't know what the PKG_CONFIG_PATH was (this is all out of my comfort zone). Cheers, I'll give that a crack

See if the first answer from this thread improves visibility.
I'll close the ticket for now. Feel free to reopen if the issue needs a response from us.

So interestingly, even after setting the sysroots and setting the PKG_CONFIG_PATH to all of the pkgroots in my clone, the build won't run on the other machine:
./mybinary: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./mybinary)

is that something to do with the version of gcc I'm compiling with?

it still seems to link with host glibc. did you mount sysroot to the docker container? this is how it is done in the example I referenced above.
try to use linker flag -Wl,-dynamic-linker,<libc path>. with example above it will be something like this -Wl,-dynamic-linker,/lib)/ld-linux.so.2. but honestly, it is unnecessary with modern gcc
also, it is good to enable linker verbose mode to see where it is trying to find libc. -Wl,--verbose is for it.

Sorry I should give you more context with the commands I'm running, the docker command looks like:
docker run --rm \
    --privileged \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v `pwd`:/build \
    -w /build \
    -v /home/joel/Desktop/hurricane-sysroot:/sysroots/linux_amd64 \
    goreleaser/goreleaser-cross --rm-dist --snapshot

and then in the .goreleaser.yml I have:
  - main: ./cmd/mybinary
    id: linux_amd_build
    binary: mybinary
    env:
      - CGO_ENABLED=1
      - CC=gcc
      - CGO_FLAGS=--sysroot=/sysroots/linux_amd64
      - CGO_LDFLAGS=--sysroot=/sysroots/linux_amd64
      - PKG_CONFIG_SYSROOT_DIR="/sysroots/linux_amd64"
      - PKG_CONFIG_PATH="/sysroots/linux_amd64/usr/lib/x86_64-linux-gnu/pkgconfig:/sysroots/linux_amd64/usr/lib/pkgconfig"
    targets: [linux_amd64]
    tags: [release]

I think it is finding the /sysroots, when I put in the incorrect path for the CGO_FLAGS it complains that it cannot find the correct files, I'll try with the linker flags

Well you're right, it isn't linking against the correct libraries but I have no idea why! If I try build myself in the container doing:
export PKG_CONFIG_SYSROOT_DIR=/sysroots/linux_amd64
export PKG_CONFIG_PATH="/sysroots/linux_amd64/usr/lib/x86_64-linux- gnu/pkgconfig:/sysroots/linux_amd64/usr/lib/pkgconfig"
export CGO_ENABLED=1
export CGO_FLAGS=--sysroot=/sysroots/linux_amd64export CGO_LDFLAGS="-Wl,--verbosesysroot=/sysroots/linux_amd64"
go build -o mybin ./

then I get a bunch of logs like:
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/libgcc.so failed
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/libgcc.a succeeded
/usr/lib/gcc/x86_64-linux-gnu/10/libgcc.a
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/libgcc_s.so succeeded
opened script file /usr/lib/gcc/x86_64-linux-gnu/10/libgcc_s.so
/usr/lib/gcc/x86_64-linux-gnu/10/libgcc_s.so
opened script file /usr/lib/gcc/x86_64-linux-gnu/10/libgcc_s.so
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/libgcc_s.so.1 failed
attempt to open libgcc_s.so.1 failed
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/libgcc_s.so.1 failed
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/libgcc_s.so.1 failed
attempt to open /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/libgcc_s.so.1 failed
attempt to open /lib/x86_64-linux-gnu/libgcc_s.so.1 succeeded

so it's clearly looking in the wrong place. I don't understand what the PKG_CONFIG_SYSROOT_DIR variable is actually doing which doesn't help either.
I also tried building without the CGO_FLAGS and CGO_LDFLAGS to no avail

it should be CGO_CFLAGS i think.

Ahh that worked! Thanks for your time, really appreciate it

Apparently, example I gave you had this typo, sorry for the confusion. Glad tho issue has been resolved.

Hey @troian I have been hit with the same issue. I have a simple cgo project that I want to run on my Amazon Linux 2 server which has a lower glibc version(2.26).
I tried using goreleaser cross without the sysroot approach as given in the example. I got this error:
./cgo: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./cgo)
./cgo: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./cgo)

Then I rsynced the sysroot directory using the script like this:
./sysroot-rsync.sh -i ~/keys/key.pem ec2-user@xxx.xxx.xxx.xxx:/usr/ ~/src/cgo-cross-compilation/sysroot
I rsynced the whole /usr directory from the Amazon Linux EC2 instance. Is this correct? (you can find the rsynced sysroot contents here).
Then I modified my Makefile and Goreleaser.yml file as per the example and built the binary.
But running it again on the Amazon Linux EC2 server gave the same error(which was unexpected):
./cgo: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./cgo)
./cgo: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./cgo)

The sysroot libm.so.6 file has a version of 2.26 (I verified), so I expected the built binary to work this time.
$ strings sysroot/lib64/libm.so.6 | grep GLIBC_2.26
GLIBC_2.26

Is there anything wrong I am doing? Do I need to do anything differently(the rysncing of sysroot)?
Any help will be greatly appreciated.
Thanks
cc @jhwz

Not sure sorry but from the error it looks like the Go runtime (cgo) itself requires at least version GLIBC_2.29. You'll either need to upgrade your server or downgrade your version of Go.

@pskrbasu add this flag to CGO_LDFLAGS -Wl,--verbose
output will be rather huge, what you'll need to look for is what libs linker is picking up


Adds lightbulb support for VS 2015.

Also improves/simplifies the old smart tags slightly.

:+1:

This breaks the Dev14 build because SmartTagTests.cs isn't updated, and it doesn't include test cases for the new lightbulb functionality.


Appropriate formatter

Does an appropriate formatter for the rules defined in xo already exist ?
Something like standard-format for standard.

Yes, $ xo --fix.

Sorry, I've readed about the --fix option just right now (too late), but it doesn't seem to fix all problems found.
For example running xo --esnext --fix on the following file
let a = {
 	b: 1
};

exports.a = a;

Where this problem is:
2:2  error  Mixed spaces and tabs                       no-mixed-spaces-and-tabs

Will increment the indentation of the line 2 like this:
let a = {
 			b: 1
};

exports.a = a;

Not all ESLint (what XO uses underneath) rules have fix ability yet, but it's improving for every release.


VTT Parsing adding \N as newline separator

I create an SRT from a VTT string.
let sub: vtt::SRTFile = Subtitle::from_str(vtt_subs).unwrap().into();

Then all the newlines \n have been replaced with \N. I think that is happening here?
https://github.com/adracea/rsubs-lib/blob/2b34070baea0542f322dceacd9d5432f867c77dd/src/vtt.rs#L447C1-L448C1
Is this intended?

Looks like the \N is replaced in the fmt function but if you just try to iterate over the subtitles and get the line_text it is present.

Hey, @rteabeault ,
The \N workaround is there because unlike .srt and .ssa, webvtt actually uses double line breaks to determine a new line which enables multiple lines with single line breaks. I'll try to see if I can provide a more elegant workaround.


Bump versions of some Perl packages related to DateTime

Built locally against recent Nixpkgs release (16.03pre70724.d4bebcb) using nox-review wip, it produced 61 result directories and made my laptop glowing hot due to Gnucash build.

Thanks!


Reduce thickness of zone where TouchEvent's are intercepted

First of all, this is a great library and thank you for making it.
I have a use case where the items in my RecyclerView feature a button on the right side to show a popupMenu. I already adjusted the thickness of the TouchScrollBar using setBarThickness so that it fits into the margin between the button's right edge and the screen's edge, but it still seems to intercept touches on my buttons. This lead me to the conclusion, that reducing the thickness only reduces the visible size of the TouchScrollBar but not the thickness of the zone where it actually intercepts TouchEvents.
Correct me if I'm wrong and if not: is there a way to reduce that thickness likewise?
Thanks in advance, cheers!

I just checked and it looks like you're right! That's my fault. I'll try and get that fixed for you today.

Thank you, I appreciate it and look forward to trying the fix.

Let me know how it works. If there's a problem I'll reopen.

Thanks for taking care of this this so fast!
The problem I described before is gone now, but another one has arisen:
I use a TouchScrollBar with autoHide = true and respondToTouchIfHidden = false. Before your fix, the ScrollBar would intercept the TouchEvents on the buttons while it was hidden, which is now not a problem anymore. I'm using barThickness = 25 and when the ScrollBar is not hidden, it is almost impossible to use it for scrolling since the area it reacts to touches in is so small. Maybe you can see for yourself with that value.
What first comes to mind as a solution would be to differentiate between hidden and not hidden state: when the ScrollBar is hidden it uses your fix but when visible it falls back to the original thickness to intercept TouchEvents.
I don't know if that is something you would implement, maybe that is too specific for my exact case, but I would love to hear your thought on that matter.

Hi @krimin-killr21,
have you given this issue some thought?
I noticed in the code that the OnTouchListener in the TouchScrollBar only returns false when the ScrollBar has been explicitly hidden by the user. IMHO it should also return false when hidden == true and respondToTouch == false.
It think it makes no sense to consume the TouchEvent when the ScrollBar isn't going to react to it. This way my issue would also be fixed. The buttons get all their TouchEvents when the ScrollBar is hidden and when it is not I can simply use a greater thickness to ensure it is easy to scroll.


[Misc] Enhance prefix-caching benchmark tool

I update the prefix-caching benchmark tool with following new features

Added support for using real ShareGPT data for testing.
Introduced new parameters to duplicate prompts for more extensive testing.
Implemented benchmark support against prompts with varying input token lengths.
Added functionality to sort or shuffle data, simulating real-world traffic patterns.

This update allows for more accurate and flexible performance testing on the prefix cache
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

amazing!

can you please see if this can reproduce the issue reported here: https://github.com/vllm-project/vllm/issues/5543 ?
does this also simulate concurrent requests? we have noticed some correctness/consistency issues that happen only in such cases (didn't manage to open a dedicated issues about it yet)

Thanks!

amazing!

can you please see if this can reproduce the issue reported here: [Bug]: prefix-caching: inconsistent completions #5543 ?
does this also simulate concurrent requests? we have noticed some correctness/consistency issues that happen only in such cases (didn't manage to open a dedicated issues about it yet)

Let me try to reproduce these two issues

amazing!

can you please see if this can reproduce the issue reported here: [Bug]: prefix-caching: inconsistent completions #5543 ?
does this also simulate concurrent requests? we have noticed some correctness/consistency issues that happen only in such cases (didn't manage to open a dedicated issues about it yet)

Let me try to reproduce these two issues

Please check back if you do 🙏. In the meantime, I will also try to reproduce the issue with your PR.

@KrishnaM251 @hibukipanim I have not verified the correctness or consistency in my test yet.  It's great to know you found such issue. This PR right now focusing on more real world data, especially the efficiency between different prompt size. It may not fix the correctness issue but I will definitely try to help check the problem you mentioned as I can

Seems https://github.com/vllm-project/vllm/pull/7018 address the correctness issue. I have not tested it yet. I think maybe we can merge this tool change first? If there's additional correctness issue, let's track it in  https://github.com/vllm-project/vllm/issues/5543 @robertgshaw2-neuralmagic

@robertgshaw2-neuralmagic @simon-mo kindly ping


Clusterable interface for redis commands

The goal of this PR is to get rid off current implementation of filtering for commands that could be executed against OSS cluster. For now, each command should be specified within a dictionary in ClusterStrategy. So whenever we implement a new command the code should be changed in two different places, so it violates some of SOLID principles and make it hard to maintain.
The enhancement based on another case that similar to this one:
https://github.com/predis/predis/pull/1262
Here's a proposal of new implementation:

Introduce Clusterable interface that represents command that can be executed against cluster.
ClusterStrategy filtering now based on Clusterable interface.
ClusterableContract trait contains API that allows to complete Clusterable interface contract.
Commands that currently supported execution against cluster will be marked with Clusterable interface so from user perspective all functionality will be kept.
Introduce getKeys() method within CommandInterface, so now each command itself should provide information about the keys, instead of detecting them within ClusterStrategy.

Enhancements:

ClusterStrategy object wont be changed in case if new command will be introduced, or old one will allowed to be executed against cluster (no more bugs like this: #1368, #1352, #1305). Removed violation of SOLID OCP principle.
ClusterStrategy object now isn't responsible for detecting command keys, moved on a command object level. It's more natural when the information about command keys stores in the command itself, since it's a part of command domain. Removed violation of SOLID SRP principle.
We keep only one responsibility for ClusterStrategy - calculate a hash slot depends on given cluster context. In future, we should get rid off strategies at all and move hash slot calculation into command object as well (according to Information Expert pattern), but this require massive changes that I won't add to this PR.

@tillkruss @chayim I want you to have a look on the draft of PR and lmk what you think about this changes. Don't want to spend so much time for it if it makes no sense 👌


Panic send on closed channel crash

Getting a crash when running against podman. Works on the rare occasion. Seems to be correctly pointing to the right socket. Installed this with go and also getting same result with sh install method. I'm on go 1.17.6 and a linux amd64 on a fedora 5.16 kernel.

Still an issue (for me at least)
  Dry Version: 0.11.2
  Docker Host: unix:///var/run/docker.sock                                                                made with 💙 (and go) by moncho  panic: send on closed channel

                             goroutine 45 [running]:
                                                    github.com/moncho/dry/docker.(*DockerDaemon).Events.func1.streamEvents.1({0x103637300?, 0x14000092190?}, {{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, ...})
                                                                                /opt/code/go/dry/docker/events.go:17 +0x98
                                                                                created by github.com/moncho/dry/docker.handleEvent in goroutine 40
                                                        /opt/code/go/dry/docker/events.go:41 +0x48

docker.sock is a symbolic link:
ls -l /var/run/docker.sock
lrwxr-xr-x@ - root 23 Aug 14:48 /var/run/docker.sock -> /Users/linickx/.local/share/containers/podman/machine/podman.sock

Podman v5.2.1
MacOS: 13.6.9


Remove notify from dist and add description for npm package

Solves #81
Add better description for npm package

just curious: any reason behind 9f1c57c47f4af6a270683e79815b3202b5398ea1 ?

@AsLogd on the previous commit I unordered it for no reason. So on the PR changes it was showing this change. I took it back and that's it :smile:


Support numeric type

I just started to use this module, but unfortunately, only a few types seem to be mapped :
TypeError: do not know how to convert type [numeric]

Would it be possible to add numeric type mapping ?
Thx by advance.

This can be supported by adding a line case 'numeric': on the type mapping function https://github.com/SweetIQ/schemats/blob/master/src/schema.ts#L54
Other types can also be supported by adding respective mappings.
Pull requests are welcomed 👍

Yes, thx ! I eventually found the relevant code too.
Ok, I will send a PR in order to add some frequent datatypes in the upcoming days, I'm glad to help on this.


Create test targets & automation plan for integration / "smoke" tests

Describe the feature
Perform the following for integration tests:

Create test targets as needed to host integration tests
Determine what external resources are needed to run these tests, document them, and determine how to ensure their availability & reliability for testing
Determine what schedule and on what platform(s) these tests should run

Use Case
To help detect regressions as early as possible in the development cycle
Proposed Solution
Create a plan and reach a consensus with the rest of the team.
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

Similar to #814

create a manual trigger for these tests

aws-sdk-swift integration tests are now run on PRs by commenting /test on the PR, and are required to pass prior to merge.
Closing.


Initialize project

In this PR I word on the following:

Add: components ( Books, Add boo form and Categories
Add: page routing linking from books to categories
Add: book form

Nice recommendation, I will try to implement it. Thanks, @Dipeshtwis.


GSLUX-650: Time layers on map

JIRA issue
https://jira.camptocamp.com/browse/GSLUX-650
Description

[x] Enable time layers on map
[x] Improve ui slider: enable click on track
[x] Use factory and helpers for layer creation according to layer type (WMS, WMTS, ...)
[x] Refactor bg layer creation with layer creation that were exactly the same

Thanks for this nice functionality and the refactoring @AlitaBernachot !
One minor things I noticed when testing was that the slider-thumb does not always land exactly on the click position when clicking on the slider on the first click, while it does on the second click. But I think this can be improved later.

Thank you for reporting this! some unneeded extra watchers were causing this. Now, it is fixed.


Why options not use ConcurrentHashMap but synchronized

It's a not an issue. But some doubts
private final Map<ChannelOption<?>, Object> options = new LinkedHashMap<ChannelOption<?>, Object>();

Why options not use ConcurrentHashMap but synchronized？
Hope you could give a hand. Really appreciate.

@zhaojigang If we're talking about Http2StreamChannelBootstrap, options are packed into LinkedHashMap. ConcurrentHashMap does not provide you the same semantic (e.g. predictable iteration order). Potentially, it's possible to use Collections.synchronizedMap to wrap the map mentioned, but that still would not give the same performance as you can get with ConcurrentHashMap. And I don't think the complexity pays itself out in this particular case.


App shows SecTaskLoadEntitlements failed error=22 when opening and then terminates

I tried to bundle a pygame project using the pygame example in the repo. But when I opened the .app it shows this  (my executable script is main.py):

and when I checked the console this is what it shows :

I don't know if this a py2app problem or an error on my mac.
I'm on OSX El Capitan with v0.21 of py2app
Thanks in advance

It is fixed now, I had to put plist info in the setup.py


⚠ Bofrost.at has degraded performance

In e7b211d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1558 ms

Resolved: Bofrost.at performance has improved in 0c9f32a.


Work with Github to fix their Advisory Database importer?

Github used to import FriendsOfPHP vulnerabilities until at some point last year - see an archived version of their docs). I've been contact with Github support twice to flag that their importer seems to be broken - it's only importing a fraction of the advisories we (silverstripe) publish to FriendsOfPHP.
I might have been the cause for Github removing claims about importing FriendsOfPHP, in my view security related features and information should provide high quality data - and showing the occasional vulnerability alert for our ecosystem meant that devs will get a false sense of security through the feature. The lack of alerts on their Github repo does not mean they run a secure installation of our dependencies.
Have you contacted Github about this in any way? It's such a useful feature to the PHP community, I'm keen to get some momentum for them to reinstate their importer.

Looks like they stopped importing this database at all.
For the silverstripe case, I would say that the ones appearing on github are the ones that have a CVE assigned, because they are imported by Github from the CVE database.

Thanks for looking into this! We've got CVEs (through Mitre) for 57 vulns, yet Github lists only 7. See NVD for "silverstripe" vendor. So even for the CVE import (which they appear to be doing through NVD) I'm not quite sure how that importer functions.
Symfony appears to have the same issue: 16 advisories in Github, and well over 30 advisories in symfony.com.
Maybe you could try contacting them? Github Advisories are such a useful feature for the PHP community if they can make them accurate. I've tried my luck already, might carry more weight if it comes from another PHP project and the maintainer of the source they've claimed to import before?

Unfortunately, we don't have the resources nor the time to talk to consumers of this database. Let's close here as I won't be able to do anything here. Of course, I would be more than happy if more projects would try to fix the issue with Github.


[Spatial][Minor] Make SE3 constructor from rotation explicit

(should we keep it?)

Coverage remained the same at 61.788% when pulling 6d5752f302e231dcc20a9ed92e251fa58be6f638 on nmansard:topic/se3explicit into ec2a5f5a45568ec31d471dbb4cebb8977691571b on stack-of-tasks:devel.


feat(notifications): added telegram thread id's

Description
This PR adds support for Telegram Topics / Threads for both system and user notifications. I've tried my hardest to keep new code in line with existing syntax and apparent naming conventions. Should anything have slipped through, let me know.
Following scenarios were tested for both user and system notifications:

[x] Send to supergroup topic when both IDs are specified
[x] Send to "general" topic when supergroup but no topic specified
[x] Send to regular chat / channel when no thread specified (current behaviour)

As a bonus, I've already included german translations for the new strings.
Note: as per server/lib/notifications/agents/telegram.ts#L218, when a user specifies the same group as is set for the system, the user will not receive notifications. In the supergroup construct, this may no longer be ideal.
https://github.com/Fallenbagel/jellyseerr/blob/89831f70909df0a76dfa8a027702e4e5f9b57be8/server/lib/notifications/agents/telegram.ts#L218

Screenshot (if UI-related)
System Settings

Empty
Input Validation

User Settings

Empty
Input Validation

To-Dos

[x] Successful build pnpm build
[x] Translation keys pnpm i18n:extract
[x] Database migration

Issues Fixed or Closed

Fixes #674

All lights should be green now. I've left open one conversation while waiting for a final decision. If there's anything else to do, let me know.

If there's anything else that needs doing, let me know. Otherwise I'd love to see this merged as Jellyseer is the last app on my servers that doesn't support topics yet, so I'd be very happy to get this done sometime soon.

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

v2.2.0
GitHub release

Your semantic-release bot :package::rocket:


Add rules.enum.specified

Closes #797
This PR adds new rules.enum.specified = true that will accept only defined enum values except 0 (unspecified).
message Message {
    Operation operation = 1 [(validate.rules).enum.specified = true];
    // Equivalent to:       [(validate.rules).enum = {defined_only: true, not_in: 0}];
}

enum Operation {
    OPERATION_UNSPECIFIED = 0;
    OPERATION_CREATE = 1;
    OPERATION_UPDATE = 2;
    OPERATION_DELETE = 3;
}

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the contribution @maratori, i like the improvement in readability but id like to see if you can come up with a better name for the new role. specified is far too closely related to defined in my opinion.

Naming zero value enum to *_UNSPECIFIED is official protobuf convention. I think specified is proper wording.

Hey what happended


DEB (non-CLI) not starting due to missing dependency libadwaita

Current behavior
Installing from x86 DEB package misses the libadwaita dependency. Post installation of the package resolves the issue.
Distro: Linux Mint 21.3
How to reproduce it (as minimally and precisely as possible)

Download from here
Install
Run devtoys

Expected behavior
Application should start
Screenshots
No response
Workaround
sudo apt install libadwaita-1-0
Application will start.
Affected platforms
Linux
Affected DevToys kind
DevToys (app with GUI)
DevToys Version
v2.0-preview.1
Relevant Assets/Logs
Unhandled exception. System.TypeInitializationException: The type initializer for 'Adw.Application' threw an exception.
---> System.DllNotFoundException: Unable to load shared library 'libadwaita-1.so.0' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:
/opt/devtoys/devtoys/libadwaita-1.so.0: cannot open shared object file: No such file or directory
/opt/devtoys/devtoys/liblibadwaita-1.so.0: cannot open shared object file: No such file or directory
/opt/devtoys/devtoys/libadwaita-1.so.0.so: cannot open shared object file: No such file or directory
/opt/devtoys/devtoys/liblibadwaita-1.so.0.so: cannot open shared object file: No such file or directory
at System.Runtime.InteropServices.NativeLibrary.LoadLibraryByName(String libraryName, Assembly assembly, Nullable1 searchPath, Boolean throwOnError)    at Adw.Internal.ImportResolver.Resolve(String libraryName, Assembly assembly, Nullable1 searchPath)
at System.Runtime.InteropServices.NativeLibrary.LoadLibraryCallbackStub(String libraryName, Assembly assembly, Boolean hasDllImportSearchPathFlags, UInt32 dllImportSearchPathFlags)
at Adw.Internal.Functions.Init()
at Adw.Module.Initialize()
at Adw.Application..cctor()
--- End of inner exception stack trace ---
at Adw.Application.New(String applicationId, ApplicationFlags flags)
at DevToys.Linux.LinuxProgram..ctor() in /home/etienne/RiderProjects/Publish/submodules/DevToys/src/app/dev/platforms/desktop/DevToys.Linux/LinuxProgram.cs:line 34
at DevToys.Linux.Program.Main(String[] args) in /home/etienne/RiderProjects/Publish/submodules/DevToys/src/app/dev/platforms/desktop/DevToys.Linux/Program.cs:line 9
[1]    11204 IOT instruction (core dumped)  devtoys

Reproduced with the Portable zip download for x64 as well.
|@ ./DevToys.Linux
Unhandled exception. System.TypeInitializationException: The type initializer for 'Adw.Application' threw an exception.
 ---> System.DllNotFoundException: Unable to load shared library 'libadwaita-1.so.0' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:
/home/kyle/Downloads/devtoys/devtoys_linux_x64_portable/libadwaita-1.so.0: cannot open shared object file: No such file or directory
/home/kyle/Downloads/devtoys/devtoys_linux_x64_portable/liblibadwaita-1.so.0: cannot open shared object file: No such file or directory
/home/kyle/Downloads/devtoys/devtoys_linux_x64_portable/libadwaita-1.so.0.so: cannot open shared object file: No such file or directory
/home/kyle/Downloads/devtoys/devtoys_linux_x64_portable/liblibadwaita-1.so.0.so: cannot open shared object file: No such file or directory

   at System.Runtime.InteropServices.NativeLibrary.LoadLibraryByName(String libraryName, Assembly assembly, Nullable`1 searchPath, Boolean throwOnError)
   at Adw.Internal.ImportResolver.Resolve(String libraryName, Assembly assembly, Nullable`1 searchPath)
   at System.Runtime.InteropServices.NativeLibrary.LoadLibraryCallbackStub(String libraryName, Assembly assembly, Boolean hasDllImportSearchPathFlags, UInt32 dllImportSearchPathFlags)
   at Adw.Internal.Functions.Init()
   at Adw.Module.Initialize()
   at Adw.Application..cctor()
   --- End of inner exception stack trace ---
   at Adw.Application.New(String applicationId, ApplicationFlags flags)
   at DevToys.Linux.LinuxProgram..ctor() in /home/etienne/RiderProjects/Publish/submodules/DevToys/src/app/dev/platforms/desktop/DevToys.Linux/LinuxProgram.cs:line 34
   at DevToys.Linux.Program.Main(String[] args) in /home/etienne/RiderProjects/Publish/submodules/DevToys/src/app/dev/platforms/desktop/DevToys.Linux/Program.cs:line 9

Aborted (core dumped)

Hi,
Thanks for reporting this issue. We're adding libadwaita-1-0 to the list of dependencies in CI (private).

@veler - is there a good way to tell when the fix for this issue has been published in a new release artifact?

@veler - is there a good way to tell when the fix for this issue has been published in a new release artifact?

It is available in v<IP_ADDRESS> since yesterday: https://github.com/DevToys-app/DevToys/releases/tag/v<IP_ADDRESS>
It doesn't appear in the "details" of the release because the fix has been done on a private repository (our releasing pipeline), but I mentioned it briefly at the top.


Can't download releases

https://storage.googleapis.com/jblabs/dist/hey_linux_v0.1.2
<Error>
UserProjectAccountProblem
<Message>User project billing account not in good standing.</Message>

The billing account for project<PHONE_NUMBER>13 is disabled in state absent

</Error>

Hey there, @slayer. This is a known issue (see #168), as of right now you can use the links in the README.md file.
Here's a working linux link: https://storage.googleapis.com/hey-release/hey_linux_amd64

Is this going to get fixed?

@rakyll looks like this: Windows 64-bit: https://storage.googleapis.com/hey-release/hey_windows_amd64 is now considered a virus by Windows Defender on win10. so it removes Hey from my machine.. even when using the go get command to install.

Created a PR (#214) to add a GitHub Actions to distribute releases via GitHub Releases and Docker Hub


Bug: Basic auth is not working for domain subdirectories?

Basic auth is not working properly for subdirectories, i.e. if the files are stored in: host.de/subdirectory
Maven App URL configuration;
<EMAIL_ADDRESS>=> With this configuration, an exception occurs: FileNotFoundException<EMAIL_ADDRESS>It seems that the subdirectory is ignored.
I´ve found out that there is a workaround by extending the maven <app.url> configuration
<EMAIL_ADDRESS>=> Now the path host.de/subdirectory seems to be resolved correctly

Can you try to simply add a trailing / to the URL?
<EMAIL_ADDRESS>

ok, i´ve found the solution:
the configuration must be<EMAIL_ADDRESS>instead of<EMAIL_ADDRESS>sorry for any circumstances.
(now i got server 401 although the creditials works in the browser, but thats another issue)

What version of FXLauncher are you using?

And can you possibly send me the URL with a working username and password so I can try it?

I´m using version 1.0.13

Great. I have found the error and I'm working on it now :)

ok, i guess you don´t need the user/pass anymore?!

Probably not :) Hang on!

I have committed a fix for this is 1.0.14-SNAPSHOT. Do you know how to build from source and try this?

Attached is version 1.0.14-SNAPSHOT with the fix. You can install it into your local Maven repo like this:
mvn install:install-file -Dfile=fxlauncher-1.0.14-SNAPSHOT -Dversoin=1.0.14-SNAPSHOT -Dpackaging=jar -DgroupId=no.tornado -DartifactId=fxlauncher
After that you should be able to update to version 10.0.14-SNAPSHOT in your project, do a clean build and try it. Let me know how it goes, OK? :)
fxlauncher-1.0.14-SNAPSHOT.zip

yes i can check it out and build a snapshot, thanks

Perfect, thank you! I need to get to bed now. If it works I'll release 1.0.14 tomorrow after doing some more quality tests, it's getting late here in Norway :)

the snapshot version 1.0.14 is working great! thanks and good night

Version 1.0.14 is now in Maven Central. Thank you for the bug report and your patience.


[cgal] Update cgal to 5.0.3

Upgrade CGAL to 5.0.3

I see that the CI checks failed. But is that really an issue with CGAL? It seems to be in pbc, that does not depend on CGAL.

I see that the CI checks failed. But is that really an issue with CGAL? It seems to be in pbc, that does not depend on CGAL.

This is CI error, it is not related with this PR.


Run fzf with regular expressions

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x ] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[ x] zsh
[ ] fish

Problem / Steps to reproduce
I'd like to use some regular expression as in vim in order to filter my files. For example if I type \<text\> fzf should look after some files, which have the word text in their filename.
Reproducing steps:

Create a directory and run this command to create some test files:

for ((i=0; i<10; i++)) ; do touch "test$i.txt"; done

Use this as your fzf command:

export FZF_DEFAULT_COMMAND="rg --files --hidden --glob \"!.git/*\" | rg --engine=pcre2 --"

Run fzf (and if you can, type test\d)

I'm getting the following error message:
[Command failed: rg --files --hidden --glob \"!.git/*\" | rg --engine=pcre2 --]

I wanted to filter the output of the first rg (which lists all files) by adding the second ripgrep. What am I doing wrong?

I'm sorry for the late reply! Thank you for your answers!
So if I understood it right, I have to do the following:
~/.zshrc
ecport FZF_DEFAULT_OPTS=
export RIPGREP_CONFIG_PATH=~/.config/ripgrep/ripgrep.conf

~/.config/ripgrep/ripgrep.conf
declare gvar=''
declare Fvar=''
rg__com_="rg '{q}' ./ --color=always --colors=match:fg:12 --no-filename"
origcom () {
Fvar="${1:-'.'}"
gvar="${2:-'.'}"
fd -uu -t f "$Fvar" --header | rg "$gvar" --no-filename
}
"$origcom" | fzf --phony --preview="cat {} | $rg__com_"; \
rg --files-with-matches {q}" \
        --bind="ctrl-alt-r:reload:$rg__com_ {1q} {2q}"

right?

Couple things you dont wanr ti save in repgrep config path because rg appends line by line as flag options to ripgrep so anything that isnt a rg flag should error out just want as a script on your path the last preview command. Before the ; you want to get rid of the quote because were passing grouped commands output to the preview and looks like i missed giving you the rgcom function

Before the ; you want to get rid of the quote

So you mean it like that?
declare gvar=''
declare Fvar=''
rg__com_="rg '{q}' ./ --color=always --colors=match:fg:12 --no-filename"
origcom () {
Fvar="${1:-'.'}"
gvar="${2:-'.'}"
fd -uu -t f "$Fvar" --header | rg "$gvar" --no-filename
}
"$origcom" | fzf --phony --preview=cat {} | $rg__com_; \
rg --files-with-matches {q}" \
        --bind="ctrl-alt-r:reload:$rg__com_ {1q} {2q}"

so the adding the glob exclusion to the ripgrep_configpath is correct this is my config file and im re writting the blocks with less error lol.
/home/username/.bin/rgrex.sh
#!/usr/bin/env bash -
DEFAULT='[-a-zA-Z0-9].*'
REGEX="${1:-'$DEFAULT'}"
shift 1
_rgquery () {
local REGEX="${1=-"DEFAULT"}"
rg --files --hidden | rg -e "${REGEX}"
}
_rgquery | fzf --flags --options --stuff

/home/username/.bin/rgrex2.sh
set_var () {
DEFAULTS='[-a-zA-Z0-9].*'
REGEX="${1:-"DEFAULTS"}"
export REGEX
}
origser () {
set_var "$@"
"rg --files --hidden | rg -e ${REGEX}"
}
origser | fzf --bind="ctrl-alt-o:reload:origser {q}" \
--bind='ctrl-o:toggle-search+clear-query'

*/ripgrep.conf
-uu
--no-line-number
--color=ansi
--colors=line:fg:15
--colors=column:style:intense
--colors=column:fg:13
--colors=match:style:intense
--colors=match:fg:12
--colors=path:fg:4
--type-add=shell:'*.sh *.bash'
--colors=path:style:intense
--type-add=picture:'*.jpg, *.png, *.jpeg, *.gif'
--type-add=conf:'*rc, *.conf, *.conig, init*'
--ignore='.git/*'

sorry still rewriting parts of it almost done :) X)  but would be --preview="cat {} | $rg__com_;  rg --files-with-matches {q}" would load two data sets to the preview on the top would be the cat {} | rg__com and underneath would be the files with matches set but this as it is wont work because rg__com isnt a function and inst properly called.

declare gvar=''
declare Fvar=''
if [[ -z "$1" ]]; then
  Fvar='.'; else
  Fvar="$1"
fi
if [[ -z "$2" ]]; then
  gvar='.'; else
  gvar="$2"
fi
grep_flag_available="rg -e '{q}' ./ --color=always --with-filename --colors=match:fg:12 "
fd -uu -t f "$Fvar" | rg "$gvar" --no-filename | fzf --phony \
  --preview="cat {} | $grep_flag_available" \
--bind="ctrl-alt-o:reload:rg --files-with-matches -e {q}"
unset gvar
unset Fvar

so you just start typing out regular expression and once the format is complted with closed brackets it registers but you can also passs additional flags to rg using space --flag  though that prevents you from using the ctrl alt o which then populates fzf with a list of files that contain the regexp (not all regexp are captured 100% but its pretty close

you can then script with it using rgft | command just make sure that you populate the left side select the files you want to work on and then accept :)

Ok, so I think I've got it running now. Thank you!

hey so couple things, still not working perfectly just so you know if you want to use special characters such as word boundaries you need to double escape them \w \W however this doesnt translate currently to the function that exports a new lest currently to get both to work you need to find the regex that matches what your looking for, remove the extra escape and then fire off the command, i will update once i have it working with out the double escapes or auto correcting if there are double escapes

Ok, thanks for the information! :)


IE11 on Windows 10 change playback url using javascript not working

Browser:  IE 11.162.10586.0
OS*: Windows 10
Clappr Version: 0.2.47
Steps to reproduce:
Step 1: Create javascript function as follows:
function changeurl(url){
player.stop();
player.load(url);
player.play();
}

Step 2: call javascript function to change url:
When a user clicks a button on the page, the javascript is executed with the url present, e.g:
onclick="changeurl(http://example.com/index.m3u8)"

This works in all browsers (including on iOS and Android (well done guys! :+1: ) but sadly not IE11.
The console in IE11 logs the following message after a user clicks:

Confirmed. Great username by the way you've lived up to it :P

Thanks - i do try :) Any ideas how long it might take to resolve?

Can i just check i've understood correctly, we can only use the stop() and pause() events when using html5 playback, load() isn't supported?

@ibreakstuff93 load() is still supported and should work.

@tjenkinson thank you for clarifying! I've just tried it again, but i'm still getting an error message in IE11. It's moved a few lines however this time...

@ibreakstuff93 have you built master containing the fix?
 It's not updated on the cdn yet but that should happen at some point soon.


Update actions to be performed in iot.tuya.com

Updating since the front end of the website has changed

@thevickypedia thanks for the PR!  Merging.


Bugfix/home page typo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ChatzikonstantinidisP sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


bug fix for iphone -webkit-overflow-scrolling:touch

not very good with git... just manage to learn up some basic & hope i dont screw up.. haha
basically added 2 things, pls refer comment "by henry" & hopefully u understand.
best regards,
henry

Looks like something wen't wrong with your PR since Github thinks all the lines are additions. Is I understand correctly you have changed lines 34 and 56-62?

yah,
line 32 is due to windows phone return wrong value.
as for line 56-62, reason -webkit-overflow-scrolling:touch will conflict with the CSS transform, therefore the code custom remove all field consisted 'animated bounceInUp' CSS, this you might want to make it dynamic

The changes in line 32 have been implemented some time ago, but I've forgotten to mention that here. The changes on line 56-62 seem a bit to specific for me. An other PR also mentions adding/removing classes for animated, but for as far as I understand we can already use repeat: false to prevent the script from removing the classes during animation.


WTF?

What is the point in this?
Also @richie-south tag this as spam so hacktoberfest doesn't count it as a PR