Update google-cloud-trace to 2.54.0

About this PR
📦 Updates com.google.cloud:google-cloud-trace from 2.3.7 to 2.54.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-trace" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-trace" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #408.


Is there support for ARM64 JIT compiler ?

Wondering if there is any plan to support ARM64 JIT for ubpf ?

Not yet, there is only an x86_64 JIT right now. But an ARM64 (AArch64?) JIT would certainly be welcome.

Oh boy, I would LOVE one of these.

PR #99 is a draft PR which implements an ARM64 JIT.

@matt-gretton-dann Thanks for the work, PR #99 looks to be a good start for AArch64 JIT support, I tested it locally, passed uBPF builtin tests. Hope this could be merged.
Meanwhile, I kind of feel the string relocation and jump relocation could be unified and could share common data structure, this perhaps applies to both x86 and aarch64 backend and might be worth some follow up patches

Closing this as the aarch64 JIT is now implemented and tested in CI/CD.


Slow first range loading (http 206)

Hi,
I have made a custom viewer for PDF.JS that users can include on their own website with CORS request.
I give a webservice url to the getDocument function, that set the correct headers and serve the PDF file progressively with HttpResponse::setFile($location) and HttpResponse::send() [from apache]
The first time the pdf loads, it is very fast, but when I refresh the page many times, it takes always one minute before the first range request give an answer. (screenshot below)
The problem doesn't appear when I give the direct link to the PDF.
Do you have an idea where to look for ?
Thank you, best regards

Configuration:

Web browser and its version: Chrome 58
Operating system and its version: MAC OS X El Captain
PDF.js version: 1.7.225

Looks like it's a PHP side is holding response. Not sure it's a problem on PDF.js side, but would be much clear with complete and worker example (including PHP code was provided). Please provide short PHP project that reproduces the issue.

Hi,
thank you for the answer.
I have tried to empty my webservice and just let the HttpResponse method for serving the files and I noted that the slow loading was caused by the session_start() in my webservice.
I cannot explain why but now the problem of slowness has disappeared.
Thank you very much !
Best regards


Streambed #12867 - Update Python buildpack

Fixes https://github.com/plotly/streambed/issues/12867.

I don't think this change is necessary, as we no longer update the herokuish release from this repository. That's done from our herokuish repository now.
Instead, lets close this and file a PR to remove the circleci config from this repository.


Read-only barometer in Position_estimation

Position_estimation has a non const reference to Barometer, and it calls barometer.calibratre_bias(...) which modifies the barometer object.
This is an issue when the barometer is used in another filter (say a Kalman) in parallel to Position_estimation. When Position_estimation decides to updates the barometer bias, the Kalman sees a jump of several meters on the barometer value.
This PR updates position_estimation in order to use its own bias on the barometer.
WARNING: To be tested outdoor

Now the question is whether we should keep the methods Barometer:calibrate_bias() and Barometer::has_been_calibrated().
As you worked on this @basil-huber and @mdouglas90,  what do you think ?

We probably shouldn't have two separate calibrations accessible from the same place because someone wouldn't easily know which one to use, So if we are moving it to the Position_estimation class, it should be removed from the Barometer class. But it would still be better to have it somehow only in the Barometer class.
Should the Kalman filter be updating itself from the barometer when it has not been calibrated?

The kalman also estimates the barometer bias, it does not really matter if the barometer is not calibrated.
It would be fine if it was calibrated once (though every filter would have to check if the barometer is calibrated, and do it if it is not).
The big problem is that Position_estimation recalibrates the baro every time we arm, so just before flight!

Tested today outside, Position_estimation was behaving well with this change.

@GregoireH @mdouglas90 what do you think ?
I removed the calibration methods in Barometer interface. But I added a member
static float Barometer::pressure_at_sea_level_;

and associated static methods
static float Barometer::altitude_from_pressure(float pressure, float pressure_at_sea_level = pressure_at_sea_level());
static float Barometer::compute_pressure_at_sea_level(float pressure, float altitude);

The behaviour is unchanged compared to after the first commit (when I last tested), because Barometer::calibrate_bias(float current_altitude_gf) was never called.
Just now we have the additional capability to calibrate the pressure at sea level. The pressure at sea level is used to convert pressure to altitude.


Hacked and synced

Type: Bug
Hacked and sync using localhost virtual machine
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.19041
Modes:

System Info

Item
Value

CPUs
Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz (4 x 2167)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
3.90GB (0.68GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

remote-ssh
ms-
0.107.2023092715

remote-ssh-edit
ms-
0.86.0

remote-explorer
ms-
0.4.1

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30792226
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
89544117:30613380
showlangstatbar:30737416
0bi6i642:30841073
a2ce3375:30757347
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
copilotsettingc:30839828
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30845448

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

Sorry, second bot message it my bad :(

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Bulk obsoletion for #28482

Fixes #28482.
@pgaudet should I just remove all these?
<http://purl.obolibrary.org/obo/GO_0018275> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0017191
<http://purl.obolibrary.org/obo/GO_0042037> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0042260
<http://purl.obolibrary.org/obo/GO_0019124> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018088
<http://purl.obolibrary.org/obo/GO_0019124> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018370
<http://purl.obolibrary.org/obo/GO_0019129> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018093
<http://purl.obolibrary.org/obo/GO_0019129> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018375
<http://purl.obolibrary.org/obo/GO_0018238> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018239
<http://purl.obolibrary.org/obo/GO_0044392> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0036045
<http://purl.obolibrary.org/obo/GO_0019123> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018369
<http://purl.obolibrary.org/obo/GO_0019123> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018087
<http://purl.obolibrary.org/obo/GO_0019125> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018371
<http://purl.obolibrary.org/obo/GO_0019125> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018089
<http://purl.obolibrary.org/obo/GO_0019126> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018372
<http://purl.obolibrary.org/obo/GO_0019126> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018090
<http://purl.obolibrary.org/obo/GO_0019128> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018374
<http://purl.obolibrary.org/obo/GO_0019128> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018092
<http://purl.obolibrary.org/obo/GO_0018362> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0019924
<http://purl.obolibrary.org/obo/GO_0018363> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0019925
<http://purl.obolibrary.org/obo/GO_0018360> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018384
<http://purl.obolibrary.org/obo/GO_0018359> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018385
<http://purl.obolibrary.org/obo/GO_0018356> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018382
<http://purl.obolibrary.org/obo/GO_0018353> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018380
<http://purl.obolibrary.org/obo/GO_0018357> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018383
<http://purl.obolibrary.org/obo/GO_0018358> is used as replaced_by for http://purl.obolibrary.org/obo/GO_0018381
<http://purl.obolibrary.org/obo/GO_0042082> is used as consider for http://purl.obolibrary.org/obo/GO_0042080

Also:
FAIL Rule ../sparql/missing_superclass-violation.sparql: 3 violation(s)
http://purl.obolibrary.org/obo/GO_0043538
http://purl.obolibrary.org/obo/GO_1902390
http://purl.obolibrary.org/obo/GO_1902391

yes


dev build of openmm

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

What's the goal of this PR?  Is this just for debugging?

@peastman Few goals:

debugging why our last release had the segfaults/testing future releases
Making it easier for people to install the dev/HEAD version of openmm

Right now a lot of the work in the openmm-ml spacing is happening faster than openmm releases are and by allowing users to install openmm with the dev label, they can install a version of openmm that has the latest PRs merged in + in binary compatible with conda-forge, see this comment/thread on slack https://openmm.slack.com/archives/GMNUN3ZV2/p1650568039713289

Got it.  Let's update the documentation at https://github.com/openmm/openmm/blob/master/devtools/CONDA_FORGE_RELEASES.md to add a section on dev builds.  Based on what you've done here, it looks like the plan is

They will be built from the dev branch of this repository.
They will be posted with the openmm_dev label.
They won't be built on any automated schedule.  We'll trigger a new dev build by hand whenever we decide it would be a good idea.

Does that all match what you had in mind?

@peastman yes, exactly! I will make a PR to update that document adding steps/checklist for the dev build. Right now I'm just working on getting things to pass the CI, but then I will get everything documented.

Ok, sounds good to me.  Your changes look right as far as I can tell.  I'm not sure what's causing all the build failures.

New dependency needed?
/home/conda/feedstock_root/build_artifacts/openmm_1650923055449/work/libraries/asmjit/asmjit/core/cpuinfo.cpp:18:12: fatal error: sys/auxv.h: No such file or directory

This is part of glibc so no clue. Is this only available in a more recent version than 2.17?

Love when I stumble into issues with familiar faces :) https://github.com/conda-forge/conda-forge.github.io/issues/1625
Going to see if that fixes it.

That might fix the linux builds, but this is why the osx builds are failing:
2022-04-25T21:50:51.1346250Z /Users/runner/miniforge3/conda-bld/openmm_1650923045777/work/libraries/asmjit/asmjit/core/../core/environment.h:104:29: error: 'TARGET_OS_OSX' is not defined, evaluates to 0 [-Werror,-Wundef-prefix=TARGET_OS_OSX]
2022-04-25T21:50:51.1415270Z #elif defined(__APPLE__) && TARGET_OS_OSX
2022-04-25T21:50:51.1515830Z                             ^
2022-04-25T21:50:51.1621630Z OpenMMSwigHeaders.i:1619: Warning 453: Can't apply (OpenMM::Context &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.1722150Z OpenMMSwigHeaders.i:1753: Warning 453: Can't apply (std::vector< Vec3,std::allocator< Vec3 > > &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.1819590Z OpenMMSwigHeaders.i:1756: Warning 453: Can't apply (std::vector< Vec3,std::allocator< Vec3 > > &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.1922770Z OpenMMSwigHeaders.i:1759: Warning 453: Can't apply (OpenMM::Context &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.2024610Z OpenMMSwigHeaders.i:1864: Warning 453: Can't apply (OpenMM::Context &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.3358690Z OpenMMSwigHeaders.i:1945: Warning 453: Can't apply (std::vector< Vec3,std::allocator< Vec3 > > &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.3517170Z OpenMMSwigHeaders.i:1948: Warning 453: Can't apply (std::vector< Vec3,std::allocator< Vec3 > > &OUTPUT). No typemaps are defined.
2022-04-25T21:50:51.4590050Z 1 error generated.
2022-04-25T21:50:51.4604510Z make[2]: *** [CMakeFiles/OpenMM.dir/build.make:188: CMakeFiles/OpenMM.dir/openmmapi/src/CompiledExpressionSet.cpp.o] Error 1
2022-04-25T21:50:51.4606620Z make[1]: *** [CMakeFiles/Makefile2:589: CMakeFiles/OpenMM.dir/all] Error 2
2022-04-25T21:50:51.4608040Z make[1]: *** Waiting for unfinished jobs....
2022-04-25T21:50:51.5611970Z ./swig_lib/python/extend.i:414: Warning 509: Ov

@jaimergp any ideas why its trying to pull in mesa-libgl-devel-cos6-x86_64 instead of cos7? I thought the cdt macro would adjust to cos7

@conda-forge-admin, please rerender

Sorry for the ping Jaime, it did just need a re-rendering

@peastman I see that this PR introduced this
2022-04-28T07:01:21.5523450Z /Users/runner/miniforge3/conda-bld/openmm_1651129070600/work/libraries/asmjit/asmjit/core/../core/environment.h:104:29: error: 'TARGET_OS_OSX' is not defined, evaluates to 0 [-Werror,-Wundef-prefix=TARGET_OS_OSX]
2022-04-28T07:01:21.5524930Z #elif defined(__APPLE__) && TARGET_OS_OSX

I'm not sure why the preprocessor isn't working on it

I'm really not sure what is going on here, it looks like TargetConditionals.h should be included on __APPLE__
#if defined(__APPLE__)
  #include <TargetConditionals.h>
#endif

Is it possible that on M1 __APPLE__ is not defined, so then elif defined(__APPLE__) && TARGET_OS_OSX short circuts and we don't get the TARGET_OS_OSX undefined error? But on intel apple, we pull in TargetConditionals.h but it doesn't actually define TARGET_OS_OSX?

When compiling locally on a Mac, I tried adding this code:
#include <TargetConditionals.h>
...
cout << "__APPLE__=" << __APPLE__ << endl;
cout << "TARGET_OS_OSX=" << TARGET_OS_OSX << endl;

I tried both an Intel Mac and an M1 Pro.  It compiles and prints the same output on both:
__APPLE__=1
TARGET_OS_OSX=1

I also verified that if I omit the #include, __APPLE__ is still defined but TARGET_OS_OSX is not.

Is it possible conda-forge is shipping their own version of TargetConditionals.h rather than using the one built into the OS?  That's just the sort of thing they would do.

If CondaForge were installing its own copy of that file, where would I find it?  I notice the recipe includes the lines
https://github.com/conda-forge/openmm-feedstock/blob/d68725f149ed2b6cfdf89f3e197ba5d7f99f954f/.ci_support/osx_64_numpy1.21opencl_implkhronospython3.10.____cpython.yaml#L19-L20
which looks as if it were naming a machine image or something similar.  But if so, I can't figure out where it comes from.  The macos_machine option is never mentioned anywhere in the CondaForge documentation.

@peastman I'm not sure, this could also be in the hands of however Microsoft handles their OSX VMs... I'm going to try seeing if any other packages using these same macros have some work around for conda-forge

Could also be an xcode version thing, still investigating

TARGET_OS_OSX is not defined by the macOS SDK that we are using by default. You can increase the macOS SDK version (look at the conda-forge docs) or just define -DTARGET_OS_OSX=1 in CXXFLAGS.
Note that increasing the macOS SDK might make the package not compatible with an older version of macOS if the build system is doing function existence checks. If that's the case, then you need to increase the deployment target too. (see docs)

Thanks!
@mikemhenry the relevant documentation is at https://conda-forge.org/docs/maintainer/knowledge_base.html in the section labeled, "Requiring newer macOS SDKs."  I don't know what version it was added in, so let's start by trying something fairly old and work up.

@peastman sounds good, do you think that's better than just passing -DTARGET_OS_OSX=1 if we are doing an OSX build?

I think it's safer.

For what it's worth, the copyright date at the top of TargetConditionals.h is 2014.  Assuming that's correct, that implies it was last updated in either 10.10 or 10.11.

I'll keep trying until it works, but it is odd (at least to me) and the osx arm builds are fine, just the intel ones that seem to be missing this macro

It was introduced in 10.12. (osx-arm64 builds use 11.0 since support for osx-arm64 was added in 11.0)

osx-arm64 builds use 11.0 since support for osx-arm64 was added in 11.0
This is great to know, thanks!

@mikemhenry, after each change you need a rerendering.

@isuruf ha, that it explains it!!

osx osx_64_numpy1.19opencl_implapplepython3.8.____cpython failed failed with an http error https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=507537&view=logs&j=a8dee1cf-d17f-5cb0-b53f-4a93dfdbfb0c&t=929f6101-935e-5679-3be5-15b073490bac&l=396 which I can reproduce locally, I'll bump CI to give it another chance but I think things are fixed now!

@peastman as long as we don't need windows support, I think this is good to go! I'm going to build with the latest commit, then manually test the Linux package, then merge? Does that sound okay?

Sounds good!

All of the tests passed locally for me with cuda 11 build of linux-64/openmm-7.7.0dev0-py310h11b7549_0.tar.bz2. So I will merge this and announce it on slack, after I get feedback I'll update the release doc you mentioned at the top of the PR.


Registration

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/65027
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 73e0d7e34af46dc62fb2736c8c52a8dc171572f7
git push origin v0.1.0


Read dsn from system

Allow read dsn system values for deployment
Closes https://github.com/getsentry/sentry-elixir/issues/107
I kindly ask you to merge it asap as I have a application running in production waiting this feature,
Thanks

I can start reviewing this at some point today, but if you need it ASAP, you can reference your fork in mix with: {:sentry, git: "git://github.com/rafaeljesus/sentry-elixir.git", branch: "read-dsn-from-system"}

@mitchellhenke Thanks!

@mitchellhenke I also just realized that I need to do the same on Mix.Tasks.Sentry.SendTestEvent

@rafaeljesus It might be easier to have something like Sentry.Client.get_dsn! that fetches from sys/env and parses.  Then it can just be called in Sentry.Tasks.Sentry.SendTestEvent and Sentry.Client.send_event/1

@mitchellhenke mate I did the changes you requested may you take a 👀  again?

Also execute the send_test_event manually with my sentry account and works like a charm

Thanks for the contribution!


Include notification banner from design system

Those who need the new components from the design system might have to update their npm using 'npm update' on terminal.
Try to merge this PR first and see if it is working on your version. If the banner doesn't show or behave as expected, try the npm update.


feat: Global performance improves, add no-cache for HTML

Type of Change

Build Scripts: add Cache-Control: no-cache for HTML source to improve the performance

What should this PR do?
Global performance improves, add no-cache for HTML
What are the acceptance criteria?

These changes will add Cache-Control: no-cache for website HTML
Environmental preparation

Nginx website nginx location config

listen      80;
# ...
 set                     $base /var/www/example.com;
 root                    $base/public;
 location / {
     try_files $uri $uri/ /index.html;
 }

Create index.html in /var/www/example.com/public/cache-test and input anything like:

Caching Test

In order to prevent the influence of successive operations, please use incognito mode

previous behavior

When you visit localhost/cache-test with Chrome first time
You will get 200 status code
F5 this page
You will get 304 status code
When you open a new tab and  visit localhost/cache-test
You will get 200 status code with a cache

Current behavior
Nginx config change to
listen      80;
# ...
 set                     $base /var/www/example.com;
 root                    $base/public;

# This commit chages
location ~* \.(?:html)$ {
    add_header Cache-Control "no-cache";
    access_log off;
}

 location / {
     try_files $uri $uri/ /index.html;
 }

When you visit localhost/cache-test with Chrome first time
You will get 200 status code
F5 this page
You will get 304 status code
When you open a new tab and  visit localhost/cache-test
You will get 304 status code

UI Changes:
Before:

After:

Add some information

How no-cache work
Chrome behaviors

If you refresh the page via the F5 key or the Refresh button, the page and all resources revalidate (i.e. a request is made to the server for each resource and a 304 returned).
If you return to the page via a link or entering the URL into the URL bar in a new tab, then no revalidation is done (i.e. no requests are made).
In Chrome, if you refresh the page by selecting the URL bar and pressing Enter, the page itself revalidates but no other resources do. In Firefox, neither the page nor resources revalidate.

👋 I'm not sure what you're trying to achieve here, but setting a no-cache header is not going to improve cache performance -- it will in fact do the opposite, it will tell the browser to never cache the file locally and always make a fresh request to the origin (NGINX) to get the file.

If you want to be able to customise the cache lifetime of HTML files, instead of just adding a checkbox that forces them to never be cached, I'd suggest mirroring how we set cache lifetimes for other asset types already.

I'm not sure what you're trying to achieve here

A: When we deploy a new frontend version the client will receive the latest changes in time

but setting a no-cache header is not going to improve cache performance -- it will in fact do the opposite,

A: My understanding is skewed, I thought it was related to "performance" rather than "improving performance".

it will tell the browser to never cache the file locally and always make a fresh request to the origin (NGINX) to get the file.

If you want to be able to customise the cache lifetime of HTML files, instead of just adding a checkbox that forces them to never be cached, I'd suggest mirroring how we set cache lifetimes for other asset types already.

Let me provide some example:
1.DigitalOcean NGINXConfig
cache-control: max-age=0

2.Google
cache-control: private, max-age=0

3.Amazon
cache-control: no-cache

HTML is special, If HTML is changed that means related CSS and JS need to be refreshed, If HTML isn't changed that means get CSS and JS from the local cache and follow the expiration setting
max-age=0 and no-cache have the same effect

Ah okay, I see what you are trying to do now -- could we name this feature "Disable HTML caching" instead then?

I have changed it to "Disable HTML caching"

Done.

Hey, @chenyhd - Thanks a ton for this sweet PR! 😄
Would you please shoot me an email when you get a chance?
mcowley at digitalocean dot com 🎉


Fix evaluation for the belebele dataset

Fixes two issues with the current implementation of the belebele task:

In the HF repository for the belebele dataset (facebook/belebele), the different languages are implemented as splits rather than dataset subsets. This PR deals with this by labelling each language-specific subset as a test_split in each .yaml file rather than a dataset_name (which looks for a data subset/config). In order to align with the original _default_template_yaml file, the language-specific subsets are also used as the fewshot_split for each language.
lm_eval.logger.eval_logger no longer appears to exist in the main branch. This is replaced by lm_eval.utils.logging in

 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.


When python main.py -g leakgan, there have a BUG and the data/shi.txt have a encoding BUG

Traceback (most recent call last):
File "main.py", line 85, in
parse_cmd(sys.argv[1:])
File "main.py", line 67, in parse_cmd
gan = set_gan(opt_arg['-g'])
File "main.py", line 26, in set_gan
gan = Gan()
File "E:\all_code\aspectLevel\Texygen\models\leakgan\Leakgan.py", line 64, in init
self.sequence_length = FLAGS.length
File "D:\Anacond\lib\site-packages\tensorflow\python\platform\flags.py", line 84, in getattr
wrapped(_sys.argv)
File "D:\Anacond\lib\site-packages\absl\flags_flagvalues.py", line 630, in call
name, value, suggestions=suggestions)
absl.flags._exceptions.UnrecognizedFlagError: Unknown command line flag 'g'

Traceback (most recent call last):
File "main.py", line 85, in
parse_cmd(sys.argv[1:])
File "main.py", line 73, in parse_cmd
gan_func(opt_arg['-d'])
File "E:\all_code\aspectLevel\Texygen\models\textGan_MMD\Textgan.py", line 328, in train_real
wi_dict, iw_dict = self.init_real_trainng(data_loc)
File "E:\all_code\aspectLevel\Texygen\models\textGan_MMD\Textgan.py", line 290, in init_real_trainng
self.sequence_length, self.vocab_size = text_precess(data_loc)
File "E:\all_code\aspectLevel\Texygen\utils\text_process.py", line 75, in text_precess
train_tokens = get_tokenlized(train_text_loc)
File "E:\all_code\aspectLevel\Texygen\utils\text_process.py", line 50, in get_tokenlized
for text in raw:
UnicodeDecodeError: 'gbk' codec can't decode byte 0xa6 in position 2: illegal multibyte sequence

https://github.com/geek-ai/Texygen/issues/14

Hello @cyzLoveDream ,Did you solved the first question? I met the same problem. If you did, please tell me.

I also ran into this problem, which seems to be due to tensorflow parsing the command line flags within the leakgan code.
I solved it by modifying main.py to run leakgan by default, so that I wouldn't have to specify the -g leakgan on the command line:
        if not '-g' in opt_arg.keys():
            #print('unspecified GAN type, use MLE training only...')
            #gan = set_gan('mle')
            print('unspecified GAN type, use leak GAN training only...')
            gan = set_gan('leakgan')

This is really helpful thank you!


⚠ Cioos National CKAN has degraded performance

In 12f107e, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 8030 ms

Resolved: Cioos National CKAN performance has improved in fd70c81 after 5 minutes.


non_compliance penalty change

"not available" should be set to blank
example id: ACAPS_158448

Just checked dataset and it looks like this has been removed. Closing here.


Fixed CSRF issue

State object was being saved in encoded form and was retrieved as decoded one. So it was returning CSRF error when there are special characters in the state.

Good catch! thanks!


Luxor

Hi. Woulde you add Luxor API in your lib ?

LuxOS is already part of pyasic, it should (mostly) work out of the box, but it's possible there are issues with recent updates as I haven't had access to one in ~6 months.


Unused tokens in ballerina lexer definition

Description:
Current ballerina ANTLR lexer definition includes following unused lexer tokens, which were not removed along with the recent parser definition changes.
i.e. some, timeout and but keywords
Steps to reproduce:
Affected Versions:
0.983.1-SNAPSHOT (in branch df_endpoint_changes)
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

These lexer tokens are not available in the new parser. Hence could be closed.


[test] prepend 0x to address

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)

pickup https://github.com/starcoinorg/move/pull/21

this pickup will conflict with https://github.com/move-language/move/pull/441. Maybe wait for the PR merge to the Move repo?

conflict with https://github.com/move-language/move/pull/441, I will close it.


New-PartnerCustomerOrder throws "2004" error with Trial orders

$lineItems = New-Object -TypeName Microsoft.Store.PartnerCenter.PowerShell.Models.Orders.PSOrderLineItem
$lineItems.OfferId = "EB5BC29F-C744-4D36-8042-68BC11114EDA" (Tested several trials here with the same error)
$lineItems.Quantity = 25
New-PartnerCustomerOrder -CustomerId [insert customer id] -LineItems @($lineItems)
Generates
New-PartnerCustomerOrder : 2004 The following offer(s): EB5BC29F-C744-4D36-8042-68BC11114EDA does not support billing cycle type: Unknown
I see trials now need billingcycletype = "none" for trials
https://docs.microsoft.com/en-us/partner-center/develop/product-resources#billingcycletype
I do not see any options in the cmdlet or the class that supports a billingcycletype parameter
Partner Center Module Version 1.5.1903.6
PS Version 5.1.14393.2879

@jmeilleur1 you will be able to configure the billing cycle for orders with the next release. The required code changes have been made, and I hope to have everything ready to release early this week. Until that is available you can utilize the cart functionality instead.

Hi @jmeilleur1 version 1.5.1905.1 was just released. Please update and you will find the billing cycle property now.


Hosting on an ESP32

I'm in the process of coding an ESP 32 with a T-Panel display https://www.lilygo.cc/en-ca/products/t5-4-7-inch-e-paper-v2-3?srsltid=AfmBOoqGyGQo8zs4eGypdadbyr5RbfBxRUK-hock2-Yf6sNINq-4DQ0Y, to work as a in house display of the SPA status.  And was going include a web site for local access and control.
Do you think I could host your website code on the ESP32 ?  And have the data retrieved locally from the ESP32 rather than the cloud API?
https://github.com/NorthernMan54/esp32_balboa_panel

of course, but you need rewrite code to work with local ESP data

I was just going to change the URL to point to my ESP32, and have a web server mimic the balboa endpoint.  I looked at the interface, and it is the spa’s binary format wrapped in xml.  Pretty simple, as I already have the binary data.
am thinking the only change should be the url within your code base. And if it’s that simple, I may submit a PR to support it.

If your ESP has same data structure as Balboa cloud API you can change just the endpoint, otherwise you need to make more changes on ESP or here.


Feature ActiveMQ Artemis scaler

Added artemis_scaler.go and modified scale_handler.go
This PR adds a new ActiveMQ Artemis Scaler, this feature will finally support Java based applications using Java Messaging Service Broker like ActiveMQ Artemis
Checklist

[X] A PR is opened to update the documentation on https://github.com/kedacore/keda-docs
[X] Commits are signed with Developer Certificate of Origin (DCO)
[X] Tests have been added

Sorry guys accidentally closes the previous PR.  This is the good one now. :)

qq about naming. Is artemis mainly for queues or are there other potential event sources there that qualifying the scaler as artemis-queue would make sense.

Aaaa true artemis supports queue and topics.  artemis-queue sounds less ambiguous. Which is good.

Aaaa true artemis supports queue and topics. artemis-queue sounds less ambiguous. Which is good.

@balchua do you plan to include this change?

Yes i will. Tomorrow. Don't have too much time on weekdays. 😊 Releasing 1.5 soon?

@balchua thanks! Take your time, no need to rush :)  Yeah, we would like to release 1.5 at the end of the next week, but that's not a strict date.

I have updated the PR as well as the docs https://github.com/kedacore/keda-docs/pull/203
Thanks for reviewing.

Docs are great, thanks!


Can you share the CAD design files?

Hi
Firstly can I say thanks for open sourcing the PCD design. Would it be possible for you to share the CAD project files for the PCB. I ask as I would like to fork your repro and add the serial interface to the PCB, and using your starting point would make that a lot easier.
Thanks in advance
Regards
David

I have an updated PCB with serial support in the works.
New boards were received from china a few days ago and I will build and test a board in the next few days.
If successfull I will upload the new design to github along with the easyeda design file so people can make changes in the future.


How to implement a python variation of alpha-beta and test using the framework in WSL

I would like to know if the correct way to implement a new variation of alpha-beta using: open_spiel/python/algorithms/minimax.py and minimax_test.py for testing. I would like to know if this is the correct way to do this using WSL

Hi @tonirm2077,
By WSL do you mean "Windows Subsystem for Linux"? The way to do it is independent of environment.
Yes, that is correct. You can either build on top of or fork and modify minimax.py and minimax_test.py. Is this for personal research, or is the question more because you are considering submitting your code as a PR?
(Because if it's for your own research you can do whatever you want. :) If it's about submitting your variant, then that depends on the variant and how much modifying of the alpha-beta code is required.)

We have moved this discussion to https://github.com/google-deepmind/open_spiel/discussions/1173 so I'm closing this for now.


Can't connect to livereload from android device

My laptop and phone are both on the same wifi network. When I run cordova run android -- --lr the phone tries to connect to <IP_ADDRESS>:8081 (laptop's IP), but fails to connect. I can connect to this URL in the phone's browser and correctly get a bunch of JS alerts.
I'm wondering if somehow the app isn't getting its <allow-navigation href="*"/> entitlement correctly...? I've tried adding that into config.xml manually in a few different ways, but no luck.
Any help greatly appreciated!

My laptop and phone are both on the same wifi network. When I run cordova run android -- --lr the phone tries to connect to <IP_ADDRESS>:8081 (laptop's IP), but fails to connect. I can connect to this URL in the phone's browser and correctly get a bunch of JS alerts.
I'm wondering if somehow the app isn't getting its <allow-navigation href="*"/> entitlement correctly...? I've tried adding that into config.xml manually in a few different ways, but no luck.
Any help greatly appreciated!

Did you found a solution?

Same problem here


[Request feature] Add support for smart-enter

Please add support for smart-enter.
https://yazi-rs.github.io/docs/tips#smart-enter
local smart_enter = ya.sync(function()
	local exist, smart_enter = pcall(require, "smart-enter")
	if exist then
		smart_enter.entry()
	else
		ya.manager_emit("enter", {})
	end
end)

and replace all ya.manager_emit("enter", {}) with smart_enter()

Yep. Your code looks much better.


[autotest] Switch to using exceptions in check_bloq_example implementations

So qualtran.testing has these new check_bloq_example_xxx functions. They return BloqCheckResult enums that have pass and fail; but also na, missing, unverified, and error. This is used for the "bloq report card" where we want more info than a straight pass/fail.
For unit tests, we need a straight pass fail. Previously: the check results were wrapped in conftest.py and any bad status would raise an AssertionError or pytest.skip. Unfortunately, this means the tracebacks in pytest failures would be very unhelpful: they would only trace back to the wrapper function in conftest.py.
This PR refactors the check functions. The implementations now raise an exception for anything other than PASS. Unknown errors are passed through. The check functions catch these special exceptions to turn them into BloqCheckResult. BloqCheckException is a special exception type to make this translation easy peasy.
I was motivated to make this change when adding a new check and needing to debug individual instances via the unit tests. And the traceback thing was hindering me.

Awesome, I was going to raise this issue.

changed cr -> check_result


vite-plugin-esmodule with file-type

Hello, thank you for this plugin.
It's works smoothly with execa but I have one issue with another esm package;
I'm trying to use it with file-type but I'm getting an error "getDefaultExportFromCjs is not a function"
What can be a problem?

In Vite, the module exports are loaded by default Browser module
I tried to change the default behavior by configuration, such as
esmodule([
  { 'file-type': 'file-type/index.js' },
])

However, there is a problem with the operation of the code packaged with Vite or esbuild, and I am trying to solve this problem with Webpack

I tried webpack and it works normally.
I am rewriting the core logic part, and the next version will support webpack construction.
like this, e.g.
esmodule([
  { 'file-type': 'file-type/index.js' },
], {
  webpack: (config) => config, // support custom webpack config, if you choose it.
  // or
  vite: (config) => config, // support custom vite config, if you choose it
})

I'll fix it soon. Just a moment, please. 😄

Thank you!

Hey!
<EMAIL_ADDRESS>has been released
You can configuration blow options in your vite.config.js file for resolve the BUG
esmodule([
  { 'file-type': 'file-type/index.js' },
], {
  webpack: true,
})

Hi! Thank you for this update.
But I just checked it and I still have the same issue. I tried to use both 'file-type' and { 'file-type': 'file-type/index.js' } :(

Case 1: plugins: [esmodule(["execa", "file-type"], { webpack: true })],
Error: getDefaultExportFromCjs is not a function
Case 2: plugins: [esmodule(["execa", { "file-type": "file-type/index.js" }], { webpack: true })],
Error: [vite:load-fallback] Could not load /Users/***/node_modules/.vite-plugin-esmodule/execa (imported by electron/electron.ts): EISDIR: illegal operation on a directory, read

<EMAIL_ADDRESS>fix the BUG 😅
You can see the demo file-type.ts

With v1.1.2 I still had some issues, but with v1.2+ everything looks fine. Thanks!

As time goes on, everything will be all right 😄


Move RoundRect from Rect -> RoundRect

Move RoundRect to a new file like it's done with DiffRect.

New file RoundRect

This PR is about this comment : https://github.com/Shopify/react-native-skia/pull/99#issuecomment-1010999161

good idea, can you rename it to RoundedRect?

@rvasseur31 I think in the PR we merged yesterday (#85) it was renamed to RoundedRect after some discussion.
Thanks for the PR btw!

PS. Remember to sign the CLA, @rvasseur31 :)

I had already sign it ! The CLA check is now green !


HDMI output is black screen, miniDP to DP is ok

Configuration

HaC Mini version [e.g: 2.0]: 2.8
OSX version [e.g: 10.14.6]: 10.15.4
NUC model [e.g: NUC8i7HNK]: NUC8i7HVK6
Boot SSD model and protocol [e.g: Samsung EVO 860 1TB, SATA]: toshiba RD500 500GB NVEM
Second SSD model and protocol (if installed) [e.g: HP EX920 1TB, NVMe]:
First DIMM model [e.g: Patriot DDR4-2666 16GB]: DRR4-2666-16GB
Second DIMM model (if installed): DRR4-2666-16GB
Display port(s) used [e.g: USB-C, mini DP]: mini DP
Display resolution(s) [e.g: 4K, 5K]: 4K
Any TB3 devices:
Any USB devices:

Got the same problem when first install the Hac-mini. Using HDMI cable can't light up the screen during the MAC OS installation. Used to think my NUC was broken for this problem. But after OS installed, HDMI output should be fine.

I believe this is an Intel BIOS issue. Do you see the Intel BIOS logo when powering on?
If you do an unplug+replug then power on THEN ctrl+alt+delete right after powering on, you can reset the graphics config and see the Intel logo.


Create timeout depracted

The create timeout option is deprecated with this warning message when submitting apply.
Warning: google_compute_image.ops-manager-image: "create_timeout": [DEPRECATED] Use timeouts block instead. See https://www.terraform.io/docs/configuration/resources.html#timeouts.

What version of terraform are you using?

This will be in the next release!


.trim() usage

I was looking into code and found strange usage of .trim() function.
When cache is parsed from web is stored with all spaces and every single usage of almost every field then uses .trim()
I believe it would be better user trim once at parsing and not when using fields. What do you think?

With the rework of cgbase.parse* and the use of BaseUtils we are now using trim() nearly everywhere.

We store the trimmed version now, but we still call trim() later.


DOCS: Setup infrastructure for documentation

This PR

creates mkdocs docs
includes material and glightbox addons/extensions to mkdocs in the mkdocs config
adds the scaffolding for the documentation
ignores the built docs from the git repo
adds a github workflow to build and push docs to gh-pages branch

This PR can be merged as-is and the filling out the individual docs pages can happen in a separate PR

not sure why the ci job failed - restarted it to see if it was an intermittent failure

CI failing is my fault, fixing the tests

@rahulporuri just making sure, this branch is supposed to be merged in develop right? are we supposed to create a branch gh-pages ?

@rahulporuri just making sure, this branch is supposed to be merged in develop right?

yes

are we supposed to create a branch gh-pages ?

nope. that should get autocreated.


Help on understanding this piece of code

I am debugging on vgg_16 model.
Why not use the else branch, I think it's the real ground truth?
"Y=newX.reshape(newX.shape[0],-1).dot(W2.reshape((W2.shape[0],-1)).T)"
Thank you so much!
the piece of code is in lib/net.py:1689
if dcfgs.ls != cfgs.solvers.gd or not self._mem: # add paramb
            gtY = self._feats_dict[Y_name] - self.param_b_data(Y_name)
            if 0:
                print("warning, not accumulative")
                feats_dict, _ = self.extract_features([Y_name],points_dict=self._points_dict, save=1)
                Y = feats_dict[Y_name] - self.param_b_data(Y_name)
            else:
                Y = gtY
            resY = self.appresb(Y_name)
            if dcfgs.model in [cfgs.Models.xception, cfgs.Models.resnet]:
                resY = self.invBN(resY, Y_name)
            else:
                newX = relu(newX)
            #if resY != 0: embed()
            Y+= resY
else:
            Y=newX.reshape(newX.shape[0],-1).dot(W2.reshape((W2.shape[0],-1)).T)
print("rMSE", rel_error(newX.reshape((newX.shape[0],-1)).dot(W2.reshape((W2.shape[0],-1)).T), gtY))

Can you leave a mail, we can discuss
About this code

you can look at PocketFlow. Their code is well documented.
They implemented both channel pruning and AMC. They have results on MobileNets.


Update code for breaking changes in epiprocess through v0.10

WIP.  I think some changes are necessitated by earlier epiprocess versions than the intended 0.9 -> 0.10 bump, so it seems like these should be fixed regardless of whether -> 0.10 bump to main happens.  I'll try to work through these, and then mark this PR ready & merge epiprocess 0.10 to epiprocess main.

I've gone ahead and released epiprocess 0.10.0 on epiprocess@main so we can point at that with these changes in place.

Sorry, I think there are some more changes needed.  Cache refresh render is not working to generate errors reliably.


[BUG] The result of inserting into the column that is primary key and auto_increment using 0 is not correct

Describe the bug

What did you do

create table t in tidb

create table t(a int auto_increment primary key);

write data to t using tispark

insert into t values(0)

select table t in tidb

select * from t;

What do you expect

1
What happens instead

0

Spark and TiSpark version info

tispark: 2.3.1
spark: spark-2.4.6-bin-hadoop2.7
tidb: v4.0.2

@lilinghai  Thanks for your report!

tispark now disables user provided auto increment value


AMBARI-25141. Encrypting LDAP manager password in case password security is ON

What changes were proposed in this pull request?
In 2.7.x we store LDAP password within its own file; however the content of that file is not encrypted even if password encryption is on. To approach this issue the following should be done:

in case password encryption is enabled we will encrypt the LDAP password in the credential store and write the corresponding CS alias in the LDAP password file (just like we do with other passwords in ambari.properties)
in case the password encryption is disabled we will write the raw password in the LDAP password file

In both cases an additional level of security can be achieved by setting the appropriate user/group access on the file system to the LDAP password file.
How was this patch tested?
Manually tested both cases (password encryption was ON/OFF):

configured LDAP
checked if the LDAP password file content was OK
synched LDAP successfully

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4907/
Test PASSed.


Changing hostname not possible

Hi, i'm not sure if this is a firmware or webinterface issue, but i'm not able to update the camera's hostname via the webinterface.
Changing it via SSH in /etc/hostname and /etc/hosts works, but that makes the option in Settings -> Network pointless. :-)

@jangrewe, i pushed some changes to dev branch. please test and report if it works for you. it's better to have a uart connected while trying this, just in case :)

No reply for a month. Closing as stale.


Strip coupler interface to basics

This removes extraneous functionality (units, date checking) from the coupler interface beyond putting and getting data from a coupler storage object. This is the starting point for coming development.

@LenkaNovak will merge after formatting - next step will probably introduce the "ClimaSimulations-like" abstractions

@jb-mackay @LenkaNovak it might be good to leave some of this optional. What can happen when you don't have this sort of stuff available is something gets confused and then you end up mapping the wrong fields to each other.  It can be easier tom unravel that if you have the option to tag things in various ways.


scripts: testedtlib.py: Generate SystemExit on test failures

The devicetree check in check_compliance.py in ci-tools expects the
dtlib/edtlib test suites to exit with sys.exit() (which raises
SystemExit) on test failures, and interprets Exception as an internal
error in the test suite.
testdtlib.py accidentally raised Exception on test failures, making
check_compliance.py error out and skipping the rest of the tests when
there were failures. Fix it.

I just tested this and it does fix the issue reported in https://github.com/zephyrproject-rtos/ci-tools/pull/97


App has connected to desk but isn't communicating

Keen to get this app working as it looks great and I love that it can be controlled with scripts.
After connecting to my desk the app isn't able to read the current height of the desk and cannot move it up/down or to the predefined positions.
I have tried to reset my desk and have deleted the app, however I can't see where to wipe the app preferences so I can try to initialise the connection again. If I delete the app and download it again then it is already connected to the desk on open, but still cannot communicate.

Hi Codylg, did u fix this problem?

@yurazazik I think this might have resolved itself? It has been connected and working fine. The issue possibly might have been that I had one or two other apps connected to the desk at the same time as I was testing a few out, but I'm not sure.


BUG Virtual server inventory item cannot be changed to some states

Description
It does not seem to be possible to update inventory item state as CANCELLED or REMOVED
Subtasks

[x] Fix the issue

Duplicate of #46


Rename AddCachingServices -> AddCaching

Fixes : https://github.com/aspnet/Caching/issues/43
@HaoK

@muratg

This PR will break a few samples in other repos. I'll fix them.

:shipit:


Add test for get_address_from_username() function

The function is located in the game_actions.cairo file
The test should be located in the test_game.cairo file

Hi @princeibs can I please be assigned to this issue

I'm level 8 on node guardian and I've just finished the ecole 42 common core. I'm looking to progress and solving this issue would help me get even more involved in the ecosystem :)

May I handle this issue?
i'm a blockchain dev and would love to work on this issue
kindly assign :)

Gm, I'm a blockchain developer
I would like to handle this issue,
my steps
I will locate the test in the "game_actions.cairo" file and write the function test in test_game.cairo file,  will implement the test to make sure all the assert passed and the test also passes without an error
I am confident that I can handle this
ETA < 24h

Let me handle this issue! This is quite straightforward, I have written tests in cairo and rust. ETA 1 day.

I am Super Franky, a software developer with 3+ years of experience, and I have worked with frontend technologies like React, NextJS, JavaScript/TypeScript. I am also proficient in Cairo and Solidity for smart contract development. I'm a recent graduate of Web3bridge Africa, the foremost and premier blockchain developer community. I have made contributions to many open-source projects, and I look forward to contributing to this one. My approach to this will be to:
Review the game_actions.cairo file to understand the function that needs to be tested.
Write comprehensive unit tests in the test_game.cairo file to ensure the function works as expected.
Ensure the test cases cover all edge cases, including valid and invalid inputs, and verify that the function behaves as intended.
Test that the function returns the correct outputs, and edge cases like boundary values are handled correctly.
ET: 1 day

Hello @princeibs,
I’d be happy to work on this issue as well! With strong experience in developing secure and efficient smart contracts using Cairo and testing them on StarkNet, I can implement a thorough and high-quality test for the get_address_from_username() function in the test_game.cairo file.
If approved, I’ll ensure to deliver a well-structured and robust PR within 12-24 hours. Let me know if I can proceed!
Thank you, and I’m eager to contribute.

Is it okay if I take this?

Let me handle this issue!

I'd love to work on this!
My name is Gideon Bature, a Software Engineer with experience writing TypeScript and Cairo. I will love to work on this issue, writing the function in the smart contract and integration test for the function in the smart contract. If I am assigned, I will send my first PR within 24 hours.
Thank you!

Mind if I take this issue?

Hi, may I take up on this?


tidal-hifi: 5.10.0 -> 5.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/tidal-hifi/versions.
meta.description for tidal-hifi is: The web version of Tidal running in electron with hifi support thanks to widevine
meta.homepage for tidal-hifi is: https://github.com/Mastermindzh/tidal-hifi
meta.changelog for tidal-hifi is: https://github.com/Mastermindzh/tidal-hifi/releases/tag/5.11.0
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.11.0 with grep in /nix/store/144l07c478f3rz3q107hx2ipgslhkgfi-tidal-hifi-5.11.0
found 5.11.0 in filename of file in /nix/store/144l07c478f3rz3q107hx2ipgslhkgfi-tidal-hifi-5.11.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

tidal-hifi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/144l07c478f3rz3q107hx2ipgslhkgfi-tidal-hifi-5.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/55cf427ddf635dfadc48b30bdf23d3dd6247cfc5#tidal-hifi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/144l07c478f3rz3q107hx2ipgslhkgfi-tidal-hifi-5.11.0
ls -la /nix/store/144l07c478f3rz3q107hx2ipgslhkgfi-tidal-hifi-5.11.0/bin

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

1 package built:

tidal-hifi

Maintainer pings
cc @qbit @spikespaz for testing.

Tested, works, approved.


Error in pcluster 2.8.1 Master node using pdsh

Hi PC Team!
I have deployed pdsh on the master node of a cluster launched using ParallelCluster 2.8.1 on Centos 7.
I've got the following error message when executing pdsh:
$ pdsh -w ip-10-0-208-156,ip-10-0-248-39,ip-10-0-254-161 hostname
ip-10-0-248-39: /bin/ssh_target_checker.sh: line 27: syntax error near unexpected token `<'
ip-10-0-248-39: /bin/ssh_target_checker.sh: line 27: `    if ! mapfile -t vpc_cidr_list < <(curl --retry 3 --retry-delay 0 --silent --fail "${vpc_cidr_uri}"); then'
ip-10-0-254-161: /bin/ssh_target_checker.sh: line 27: syntax error near unexpected token `<'
ip-10-0-254-161: /bin/ssh_target_checker.sh: line 27: `    if ! mapfile -t vpc_cidr_list < <(curl --retry 3 --retry-delay 0 --silent --fail "${vpc_cidr_uri}"); then'
ip-10-0-208-156: /bin/ssh_target_checker.sh: line 27: syntax error near unexpected token `<'
ip-10-0-208-156: /bin/ssh_target_checker.sh: line 27: `    if ! mapfile -t vpc_cidr_list < <(curl --retry 3 --retry-delay 0 --silent --fail "${vpc_cidr_uri}"); then'
ip-10-0-248-39: ip-10-0-248-39
ip-10-0-254-161: ip-10-0-254-161
ip-10-0-208-156: ip-10-0-208-156

I could see in a PC cookbook that ssh configuration in PC clusters references "ssh_target_checker.sh", as you can see here:
https://github.com/aws/aws-parallelcluster-cookbook/blob/develop/attributes/default.rb
Please can you help me understand what's going on?
Best regards,
Vincent.

Hi @vbosquier,
ssh_target_checker.sh was written to be used by ssh. There is no issue when the script is used by ssh, but looks like the syntax of file is not compatible with some commands that depends on ssh, such as pdsh.
We can fix the syntax error for pdsh easily, PR here: https://github.com/aws/aws-parallelcluster-cookbook/pull/864
Please let us know if you have any question. Thanks!

Hi, I assume the issue is resolved, closing the issue now.
Please let us know if you have any question. Thanks!


Modify CI tests in .travis.yml

Ⅰ. Describe what this PR does
Add static go code check and markdown linter.
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
1.添加了go静态检查工具golangci-lint，可以参考https://golangci-lint.run/usage/linters/    ，目前有些检查项存在误报(比如errcheck，可以通过设置来关闭。
2.添加了markdown检测工具mdl，错误信息可以参考https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md。

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7a61341). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #124   +/-   ##
=========================================
  Coverage          ?   19.71%
=========================================
  Files             ?       16
  Lines             ?      345
  Branches          ?        0
=========================================
  Hits              ?       68
  Misses            ?      257
  Partials          ?       20

Continue to review full report at Codecov.

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


Whitelist: idealista.com

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[x] Whitelist
[ ] Blacklist
[ ] App Broken
[ ] Website Broken
[x] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name:

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name: Regional

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

idealista.com

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client: NextDNS

Version: <IP_ADDRESS>

Details:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail: Your Regional extension is blocking "Idealista" which is one of the biggest real estate portal in Spain.

Thank you for making Energized Protection great, with your kind help!
A project by Ador with ❤

[x] website is broken
Pack name: basic
Extension name: extreme


(Attempt to) Reduce startup time

I'm currently using Atom Beta (64-bit) on a Windows 10 machine, but this happenes systematically also with the Stable (32-bit) version.
Git (64-bit) is updated to the last available version here.
With git-plus enabled (default options):

With git-plus disabled:

Yes, please reduce the loading time.
Even though I love it, I have to disable it now 😢

This is interesting. I've been interested in reducing the startup time though it's only about 115ms for me.
I'm not sure how to replicate this without a windows machine. I'll keep this open though because it's something I want to improve

By trying to reproduce the bug I came up with a solution:

This setting lowered the startup time to only 200ms.

Ok cool! I'll change the title of this then

MBP 2016. It is 117ms, still high. I wish it can only takes 1/3 of this.

Now, it double the loading time with version 7.3.3


Identify stats for Remote Translog and integrate with remote store stats API

Identify stats around remote translog and integrate with remote store stats API being tracked here.

This task is completed as part of 2.10 release


added time range splitting and process status management

Added process status management for AMDA requests
Split time range by days.

My main concern is about using a fixed threshold that might really impact DL performances of slow products.

A simple rule could be defined to automatically adapt the threshold in relation with the min sampling of the parameter.

IIRC generating requests has side effects on AMDA about TMP folder, is this still true @brenard-irap?

I don't see any problem in my side. The same session will be used for all "splitted request", and the result will have almost the same size in our TMP folder even it's split into several files.

My main concern is about using a fixed threshold that might really impact DL performances of slow products.

A simple rule could be defined to automatically adapt the threshold in relation with the min sampling of the parameter.
I prefer something like this, then I don't think we need anymore to let the user change it. We now have to define a good threshold.

IIRC generating requests has side effects on AMDA about TMP folder, is this still true @brenard-irap?

I don't see any problem in my side. The same session will be used for all "splitted request", and the result will have almost the same size in our TMP folder even it's split into several files.
Ok, I didn't remember if there was something bound to requests count.

Looks better to me, can you add a test that validates the case when the request is too long?

How do you propose to implement the test. speasy does not check if the request is too long, it will just split the requests if the time range exceeds 1 day. I don't like the idea of having a test that tries to download more than a day's worth of data from AMDA.

I think we don't have the choice, if this is implemented, this has to be tested. If this is something users might do then the CI has also to reproduce this behavior, I don't see any other way to ensure this code path works and will work in the future (we might brake it changing something else for example).

Alright, in that case I would propose to modify the test test_amda_parameter by changing the dates to cover more than one day :

start : 2000-01-01
stop : 2000-01-02T00:01:00

On another note : the instructions in the documentation for running a single test suite doesn't seem to work : running py.test tests.test_amda returns
=================================== no tests ran in 0.00 seconds ====================================
ERROR: file not found: tests.test_amda

Alright, in that case I would propose to modify the test test_amda_parameter by changing the dates to cover more than one day :

start : 2000-01-01
stop : 2000-01-02T00:01:00

This test focuses on AMDA parameter properties, so the best is to add a test here https://github.com/SciQLop/speasy/blob/main/tests/test_amda.py#L53-L71 as we already test few requests, you can name it test_long_request. The benefit also to make a dedicated test is to be able to tag it and skip it in some configs on CI if we have some issues.

On another note : the instructions in the documentation for running a single test suite doesn't seem to work : running py.test tests.test_amda returns
=================================== no tests ran in 0.00 seconds ====================================
ERROR: file not found: tests.test_amda

Exact it's inherited from https://github.com/audreyfeldroy/cookiecutter-pypackage/blob/master/{{cookiecutter.project_slug}}/CONTRIBUTING.rst#tips :/ I'll update this, the syntax is py.test tests/file.py


Allow to set preferred node id to execute query

Server has ability to return node id during table describe
https://github.com/ydb-platform/ydb/pull/10935
It allows to reduce number of network transfers.
This is initial implementation of client support for this feature.

Codecov Report
Attention: Patch coverage is 64.10256% with 14 lines in your changes missing coverage. Please review.

Project coverage is 47.66%. Comparing base (4d80170) to head (d43de94).

Files with missing lines
Patch %
Lines

internal/pool/pool.go
70.58%
4 Missing and 1 partial :warning:

internal/conn/middleware.go
50.00%
3 Missing and 1 partial :warning:

internal/operation/context.go
62.50%
3 Missing :warning:

context.go
0.00%
2 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (4d80170) and HEAD (d43de94). Click for more details.
HEAD has 520 uploads less than BASE

Flag
BASE (4d80170)
HEAD (d43de94)

macOS
24
0

unit
72
0

go-1.21.x
48
1

ubuntu
103
3

go-1.22.x
48
1

go-1.23.x
55
1

windows
24
0

integration
72
3

ydb-23.3
24
3

ydb-nightly
7
0

experiment
7
0

ydb-24.1
24
0

ydb-24.2
24
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #1547       +/-   ##
===========================================
- Coverage   70.87%   47.66%   -23.22%
===========================================
  Files         362      355        -7
  Lines       37509    36034     -1475
===========================================
- Hits        26583    17174     -9409
- Misses       9841    17714     +7873
- Partials     1085     1146       +61

Flag
Coverage Δ

experiment
?

go-1.21.x
47.48% <64.10%> (-22.86%)
:arrow_down:

go-1.22.x
47.62% <64.10%> (-20.74%)
:arrow_down:

go-1.23.x
47.61% <64.10%> (-23.25%)
:arrow_down:

integration
47.66% <64.10%> (-4.58%)
:arrow_down:

macOS
?

ubuntu
47.66% <64.10%> (-23.21%)
:arrow_down:

unit
?

windows
?

ydb-23.3
47.66% <64.10%> (-0.20%)
:arrow_down:

ydb-24.1
?

ydb-24.2
?

ydb-nightly
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Use the current branch instead of defaulting to master

https://github.com/zeke/npm-hub/pull/17#issuecomment-270287417
Perhaps:
const branchSelector = document.querySelector('[data-hotkey="w"][title]');
const branch = branchSelector ? branchSelector.title : 'master';

💡


refactor: move plugin client into own package

Just the first step but I think mergable on its own...

Actually hold on, need to move a bit more...

Closing this for now, doing this before the other refactoring in the other PR is a bit more then just moving things...


Data script updated

Modified data script to check for the existence of the files, skip if present. Effectively resuming where it left off if interrupted

What is the purpose of this change? Why would you run download.sh again if you've already downloaded the files?

Oh it just takes hours to download. If it fails during the download and I run it again it didn’t work.
If you don’t see a purpose for the PR you are welcome to delete it!
Thanks,Boyd Hitt
On Monday, April 22, 2024, 5:12 AM, Anian Ruoss @.***> wrote:
What is the purpose of this change? Why would you run download.sh again if you've already downloaded the files?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


chore(deps): update vite 5.1.4

Description
Related https://github.com/vitest-dev/vitest/pull/5123#issuecomment-1949788480, https://github.com/vitest-dev/vitest/pull/5193
I tweaked vite-node watch test cases with a quick workaround. I'll see how others go on CI.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[ ] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Maybe flakiness increased or maybe it's just same as before. I retried three times and Windows CI hasn't go through yet.
https://github.com/vitest-dev/vitest/actions/runs/8106298865?pr=5311

Maybe flakiness increased or maybe it's just same as before. I retried three times and Windows CI hasn't go through yet.
https://github.com/vitest-dev/vitest/actions/runs/8106298865?pr=5311

Yea, it increased. I have another PR open with this change and it's not merged because of the flakiness. We need to rewrite the waitForWatcher to wait for a specific file. The watcher is ready too soon.

The watcher emits ready event too soon.

@sheremet-va Do you know where this change is coming from? I couldn't find any specific change on Vite, so maybe something from chokidar (bumped to 3.6.0 in https://github.com/vitejs/vite/pull/15803)?

The watcher emits ready event too soon.

@sheremet-va Do you know where this change is coming from? I couldn't find any specific change on Vite, so maybe something from chokidar (bumped to 3.6.0 in vitejs/vite#15803)?

Could be anything, I don't know why this started happening, but watcher was always unstable.

Maybe we can pass down a ENV variable and wait for it to appear in watcher.getWatched()? Like here: https://github.com/vitejs/vite/blob/63a39c244b08cf1f2299bc2c3cfddcb82070d05b/playground/hmr-ssr/tests/hmr.spec.ts#L971

Thanks for the pointer. I didn't know you were referring watcher.getWatched() when you were talking about vite runtime tests https://github.com/vitest-dev/vitest/pull/5123#issuecomment-1949921957.
For vite-node tests, we can wait for entry files to be included watcher.getWatched(), but I'm not sure what we should target for Vitest watch tests.

For vite-node tests, we can wait for entry files to be included watcher.getWatched(), but I'm not sure what we should target for Vitest watch tests.

We can use something lime this VITEST_TEST_WATCHER_FILE=filename vitest run

We can use something like this VITEST_TEST_WATCHER_FILE=filename vitest run

Failing CI is indicating that runVitestCli is stuck before outputting Waiting for file changes:
https://github.com/vitest-dev/vitest/actions/runs/8135325279/job/22229683329#step:10:977
https://github.com/vitest-dev/vitest/blob/c3eb8deb768f6ef1adff8e6644ce99de58fd8b01/test/test-utils/index.ts#L191-L196
So, I'm not sure if this flakiness can be fixed by waiting any specific file by VITEST_TEST_WATCHER_FILE=filename.

Failing CI is indicating that runVitestCli is stuck before outputting Waiting for file changes:

This error happens more on Mac OS, to be honest. For some reason, this line is not reported at all.

Failing CI is indicating that runVitestCli is stuck before outputting Waiting for file changes:

This error happens more on Mac OS, to be honest. For some reason, this line is not reported at all.

While searching I noticed this one VITE_TEST_WATCHER_DEBUG, I noticed this darwin specific one:
https://github.com/vitest-dev/vitest/blob/dcc8dda2e2813a40671f864049e089f459766834/packages/vite-node/src/hmr/emitter.ts#L33-L44
Maybe tweak this to see if it helps anything?

@hi-ogawa do you think this is stable enough?

do you think this is stable enough?

Ubuntu and macos CI seems okay. I cannot really judge Windows behavior, so I can only hope it's stable enough.


Users have to reinstall after every app update, or get infinite loading/splash screen.

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)  : 4.1.1 (/Users/admin/.nvm/versions/node/v10.6.0/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.0

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : android 7.1.1, browser 5.0.3, ios 4.5.4
   Cordova Plugins       : cordova-plugin-ionic 5.0.0, cordova-plugin-ionic-keyboard 2.1.2, cordova-plugin-ionic-webview 2.0.0, (and 12 other plugins)

System:

   ios-deploy : 2.0.0
   NodeJS     : v10.6.0 (/Users/admin/.nvm/versions/node/v10.6.0/bin/node)
   npm        : 6.2.0
   OS         : macOS High Sierra
   Xcode      : Xcode 9.4.1 Build version 9F2000

Describe the Bug
After updating any part (html, js, css, etc) of the ionic project and uploading the build to test flight and/or the app store, users get an infinite loading/splash screen if they update the app. The only way it works is if you delete the app and re-download. If done, everything works perfectly (until an update comes out).
Edit:
To add to this, restarting the phone seems to allows access without having to reinstall app. I assume most users are going to update and try to open the app shortly after if not immediately. Debugging via xcode doesn't really help me with anything. It shows the device as ready but the root page never loads.
Also, ionic serve does NOT have this issue. It's only when uploading a complete build to TestFlight or the App Store.

I'm getting a similar behaviour with a PWA using @stencil/core v0.11.4.
In some unidentified cases, when opening the webapp from the homescreen, the splash screen appears as frozen and never switches to the main page.
Trying to debug using Chrome remote device debugger, the webapp is detected by the debugger, but the app content (elements, networks, etc) appears as blank, there's no way to know what's happening while the splash screen is freezing.
I'd suspect that it'd be related to SW caching with the splash screen freezing while Workbox is fetching and saving resources in IndexedDB, but there's no hint.

To add to this, restarting the phone seems to allows access without having to reinstall app. I assume most users are going to update and try to open the app shortly after if not immediately. Debugging via xcode doesn't really help me with anything. It shows the device as ready but the root page never loads.

Could use some assistance with this. Is there any other place I could post the issues? Any paid support options?

Can you grab an Android device and watch what's happening using ADB with a faulty build ?
There's perhaps a frozen process that blocks the update, or maybe a problem with WebViews (assuming that's what's used). Try to grep for chrom*or for the name of the web engine used by the app.

@Levy4u are you using Ionic Pro? I had this same issue using cordova-plugin-ionic. Once I removed it everything started working again. There seems to be an issue with one of the dependencies (cordova-plugin-ionic-webview). I'm using beta.5, but I also tried to upgrade to beta.7 and was having the same issues.

@kael I made it for iOS but i guess I could package it for android and see.
@schmitzt3 I am using Ionic Pro (deploy). Don't I need the ionic plugin?
Will try these solutions and report back. Thanks so much, first client job and it's 99% done... just need the users to be able to use the dang thing after updating.

@Levy4u yes - you would need it, but we may to report this bug elsewhere.

@Levy4u To debug WebViews with ADB, you'll need to modify some code and add explicit debug according to that HowTo (never used).

For me it's more support question than a bug because I have different apps build with Ionic and don't see such a behaviour. So I think you coded something not correct what causes this issue


aws_db_instance listener endpoint

I can't see an option in the aws_db_instance code to extract the listener endpoint address.  This is an item created as part of a multi-az RDS for SQL Server.  Am I missing something?

if its not exposed by the AWS provider, then we cannot expose it here

The details can be obtained from the aws cli using describe-db-instance and the property ListenerEndpoint

you will need to file a feature request here https://github.com/hashicorp/terraform-provider-aws to get this added to the provider first before we can support it here


Is the connection encrypted ?

Just a quick question.
Is the connection between the client and server encrypted when using this driver ?

It's indeed a good question... Currently not. There is the option to specify ODBC encryption via dbConnect, but that only works for the SQL. Data is currently transferred unencrypted via HTTP. I will review that before a final release (that could be sent to CRAN). However considered that you currently need your client to be reachable from the EXASOL cluster (the cluster opens connections for parallel file transfer), use via plain Internet is for now somehow dodgy anyway.
To be improved together with issue #3.

Hi ... any update on r-exasol encryption.
Is the connection between the client and server encrypted when using this driver now ?

Created feature ticket for TLS support (#56). Will be tracked from there now. Closing this ticket.


use :: operator to declare constants

constants can be pre-compiled onto the stack
how to pre-compile recursive functions?

::varname is now being used to declare symbols


[bug]: Cannot read property '_normalized' of undefined

发布错误

ref: https://wiki.eryajf.net/pages/32108f/


feat: Add TargetAllocator MTLS configuration to operator chart

The OTEL operator recently added support for using MTLS to secure the HTTP requests made from the collectors and the Target Allocator.
This PR adds support for enabling that feature gate using the directions found in the added documentation here.

it looks like something went very wrong with generating examples 😅

it looks like something went very wrong with generating examples 😅

I promise it wasn't me. :sweat_smile:
If it makes any difference, I'm running on a linux laptop so I wonder if there's some sort of tool with a different API. I know I always get bit by sed when dealing with Mac vs Linux environments. Same goes for Docker bind mounts.

Found the issue. Turns out that if values schema validation fails template rendering explodes.

also be sure to re-run make generate-examples CHARTS=opentelemetry-operator

hmmm it seems that there's a diff in the CRDs... not 100% sure why though. I wonder if it has to do with us checking the wrong version of them?

hmmm it seems that there's a diff in the CRDs... not 100% sure why though. I wonder if it has to do with us checking the wrong version of them?

I had to rerun the update CRD target and that seems to have cleared things up.

@thefirstofthe300 can you add a new example that uses the new map.

Added.

@TylerHelmuth Can I get another review?


Display filename in supported version warning

This fixes #305.

@nden currently this is just a quick-and-dirty fix and should probably be cleaned up a little bit.

Need to add change log entry.

Coverage increased (+0.001%) to 94.493% when pulling 385c69d8ba8012b2ba1d17ee80f1ae48a4cc191a on drdavella:filename-in-warning into c37e02fc61bead888950128aaa60708b73b8c52e on spacetelescope:master.

Coverage increased (+0.002%) to 94.494% when pulling 486840c12415147d0c43ecdb486e35a3ed09f7b8 on drdavella:filename-in-warning into c37e02fc61bead888950128aaa60708b73b8c52e on spacetelescope:master.

Coverage increased (+0.002%) to 94.494% when pulling 67168fe688784a1d4d07f67369f867be89b32ca8 on drdavella:filename-in-warning into c37e02fc61bead888950128aaa60708b73b8c52e on spacetelescope:master.

@nden this is ready for merge if it looks good to you.

LGTM. Thanks.

It looks like the warnings in the JWST pipeline are coming from FITS files with embedded ASDF, and unfortunately this fix doesn't handle that case. I'll open a new issue.

Yes, having the warnings display a filename is useful when creating reference files. I think we will have to suppress the warnings in the pipeline unless you have a better idea.

These warnings maybe should not be enabled by default. Maybe we can introduce some kind of "strict validation" mode which would cause these warnings to appear, but otherwise they are handled silently. I'll have to think about the best way to allow users to configure that.
On the other hand, I think the warnings introduced in #295 are more likely to indicate real sources of problems, and I think they should not be silenced by default. I actually ran the JWST pipeline against that PR and I don't believe that there were any new warnings as a result.


[BUG] 同时使用async-queue组件和socketio-server组件时，收到sigterm信号不能正常退出

Execute the command and paste the result below.
Command: uname -a && php -v && composer info | grep hyperf && php --ri swoole
# Darwin yue 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64
PHP 7.3.9 (cli) (built: Sep 14 2019 18:07:55) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.9, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.9, Copyright (c) 1999-2018, by Zend Technologies
hyperf/async-queue                   v1.1.26  A async queue component for hyperf.
hyperf/cache                         v1.1.30  A cache component for hyperf.
hyperf/command                       v1.1.26  Command for hyperf
hyperf/config                        v1.1.26  An independent component that provides configuration container.
hyperf/contract                      v1.1.26  The contracts of Hyperf.
hyperf/database                      v1.1.30  A flexible database library.
hyperf/db-connection                 v1.1.26  A hyperf db connection handler for hyperf/database.
hyperf/devtool                       v1.1.30  A Devtool for Hyperf.
hyperf/di                            v1.1.28  A DI for Hyperf.
hyperf/dispatcher                    v1.1.26  A HTTP Server for Hyperf.
hyperf/event                         v1.1.26  an event manager that implements PSR-14.
hyperf/exception-handler             v1.1.26  Exception handler for hyperf
hyperf/framework                     v1.1.27  A coroutine framework that focuses on hyperspeed and flexible, specifi...
hyperf/guzzle                        v1.1.26  Swoole coroutine handler for guzzle
hyperf/http-message                  v1.1.26  microservice framework base on swoole
hyperf/http-server                   v1.1.29  A HTTP Server for Hyperf.
hyperf/logger                        v1.1.26  A logger component for hyperf.
hyperf/memory                        v1.1.26  An independent component that use to operate and manage memory.
hyperf/model-listener                v1.1.26  A model listener for Hyperf.
hyperf/paginator                     v1.1.26  A paginator component for hyperf.
hyperf/pool                          v1.1.26  An independent universal connection pool component.
hyperf/process                       v1.1.26  A process component for hyperf.
hyperf/redis                         v1.1.26  A redis component for hyperf.
hyperf/server                        v1.1.26  A base server library for Hyperf.
hyperf/socketio-server               v1.1.0   Socket.io implementation for hyperf
hyperf/testing                       v1.1.28  Testing for hyperf
hyperf/utils                         v1.1.27  A tools package that could help developer solved the problem quickly.
hyperf/websocket-server              v1.1.27  A websocket server library for Hyperf.

swoole

Swoole => enabled
Author => Swoole Team<EMAIL_ADDRESS>Version => 4.5.1
Built => May 11 2020 16:21:50
coroutine => enabled
kqueue => enabled
rwlock => enabled
sockets => enabled
openssl => OpenSSL 1.0.2q  20 Nov 2018
pcre => enabled
zlib => 1.2.11
brotli => E16777223/D16777223
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => Off => Off
swoole.unixsock_buffer_size => 262144 => 262144
 ~/Backend/outsource/ws3 

Description:
项目中使用async-queue组件和socketio-server组件时，Server 在收到sigterm信号不能正常退出。
socketio-server组件 文件 /vendor/hyperf/socketio-server/src/Room/RedisAdapter.php
mixSubscribe 函数
        Coroutine::create(function () use ($sub) {
            CoordinatorManager::get(Constants::ON_WORKER_EXIT)->yield();
            $sub->close();
        });

Steps To Reproduce:
新建一个hyperf项目
composer create-project hyperf/hyperf-skeleton
安装async-queue组件
composer require hyperf/async-queue
安装socketio-server组件
composer require hyperf/socketio-server
运行hyperf
php bin/hyperf.php start
发送sigterm信号

我抽空试试

下次更新时，这个能修复么？-_-


active_set not yet in use

We just had a failed circleci build triggered by a number of clusters vs number of active states mismatch and need to address how to work with the active_set attribute.

I'll have a look where this applies and put the fix into my current PR #15.

The failed build was not actually an active set problem but rather a misplaced use of msm.pi.
Disconnectivity does not seem to be a problem for our three systems, but I'll add some hints to the active_set anyway.


centos:latest not downloading

Expected behavior
Starting New Container centos:latest
Download and start
Actual behavior
Fails to download
Information about the Issue
(HTTP code 404) unexpected - {"message":"manifest for centos:latest not found"}
Steps to reproduce the behavior

Search for centos container
Click Create on official container

Thought it was our network, doesn't seem to be, can not download any docker image ATM.

Docker Hub is hosted on AWS s3, which is currently down:
https://status.aws.amazon.com/
Sorry for the inconvenience.


Upgrade dependencies to support Ubuntu 22.04

@s-ludwig : Could we get a new release with this ? DDOX on Ubuntu 22.04 (which is becoming latest on Github Actions) is broken.

Ping @s-ludwig @l-kramer
Any chance we could widen access to this repository given dub depends on it ?

Ping @s-ludwig @l-kramer


set BEMCheckBox on property to NO

When i set BEMCheckBox on property to NO, And it's value is No ,But the view is not refreshed .

This is the intended behavior. To refresh the checkbox, please use the reload method.

@Boris-Em ok, Thanks.


wiki.openwrt.org has SSL certificate for SubSignal.org

I do realize that subsignal may be hosting openwrt wiki, but it seems an SSL certificate may have been applied to the wrong virtual host in the web configuration. I don't know where else to post this.

Not a Luci issue