Maintenance status

Hello, I am working on https://pkarr.org which is mostly a thin wrapper around BEP_0044 to enable DNS queries for Ed25519 keys.
I think this DHT implementation is the closest to something I can extend and add BEP_0044 support to. However, I am curious if you are still maintaining this library, so I can open a PR with minimal changes. Or should I just maintain a separate fork and be more liberal with the changes I would like to introduce, but also maintain it long-term?
Thanks and I appreciate your work on this.

Hi, thanks for reaching out.

I am working on https://pkarr.org/ which is mostly a thin wrapper around BEP_0044 to enable DNS queries for Ed25519 keys.

Sounds like a cool project!

I think this DHT implementation is the closest to something I can extend and add BEP_0044 support to. However, I am curious if you are still maintaining this library, so I can open a PR with minimal changes. Or should I just maintain a separate fork and be more liberal with the changes I would like to introduce, but also maintain it long-term?

As you can probably see from the commit history, I haven't been working on this recently. It's a hobby project that I did mainly for fun and to learn Rust. Where I'm at currently with life and this project, I'm happy to look at PRs/issues on a best-effort basis. Small, simple, and/or reasonable things have a pretty good chance of getting reviewed and merged. Large, complex, PRs, or ones requiring a lot of collaboration, on the other hand, may never get enough attention from me to reach the finish line.
So if your BEP0044 changes are small, I would tentatively say to do them here and I will try to help get them merged. But if you think it's going to be a lot of code, or pretty complex, or if there are other big features you're planning to implement, then you may be better served by forking the project.

Thanks and I appreciate your work on this.

 Looking through the code, there are definitely a few rough patches and things I would like to clean up, but I hope it can be useful to you.

Thanks for the quick reply, I just wanted to confirm I am not fragmenting development. I will maintain a fork then. Thanks again.

Sounds good. Good luck!


OSM Biome & Vegetation bug

Greece is mostly Mesa and looks like canyon. This specific location should be actually green and with trees, also stone cliffs.

Yeah the biomes espically are an approxomation, the biome classifier needs to be refined for the next version. It looks like the trees are spawning properly from your image, however.

I also am having a weird issue except the trees are not working right. For my area, the trees should be more spruce like than the swamp. is this something with the algorithm?
https://gyazo.com/99c0e55e4f8350d83a570a170f09fdec

The tree type is based on biome so it goes back to the poor biome classification. It would be nice to find a dataset for soil and climate of biomes.

There are other issues with biomes that I have noticed. Basically, the entire Peruvian coastline is covered in Swampland in this mod ; it's supposed to be the opposite. Peru on its coast (especially Lima) has a very dry climate, but very often covered in a humid fog, and it never rains. So I would change the soil to sandstone and stone and the climate would be the same as a desert.
Also, sand deserts that are suposedly sand in Namibia and Egypt were Mesa biomes. Same thing with the largest sand desert  in the American continent (the famous Cerro Blanco) which is in Ica, Peru.
Finally, forests which are at high altitudes (1500+ meters) in the Alps are supposed to be Taiga-like, with spruce trees, but instead, it's covered with "normal" oak and birch trees.
Also I forgot : snow-covered mountains like the Huascaran (culminating point of Peru) and Mont-Blanc are not at all covered in snow : I think it would be a good idea to try and coordinate satellite images with snow-covered regions so at least we have snowy biomes at these altitudes if you considerer we are constantly in the summer.
This will be a lot of work I imagine, and these are only a few specific examples so I don't know how to make it more world-wide, but I wish you good luck !


Clear all timers on Waku.stop

Resolves https://github.com/status-im/js-waku/issues/766

LGTM!
bors merge

@felicio have you tried removing "exit": true from the mocha config see if it's still needed after this change?


Release v2.11.0

This is an auto-generated release PR for version 2.11.0.

This was mistakenly not merged as a part of our 2.11 release and should have been. However, the Gateway code did not change between 2.10 and 2.11, and the docker image release process happens separately from this PR. Therefore the only consequence of this is that the Aerie gateway UI will display "2.10.0" on deployments using the 2.11.0 release. This was determined to be a small enough impact to not be worth trying to retroactively fix it or make a 2.11.1 release, but will be fixed in 2.12. Closing this.


Replace references to azdata extension interfaces in Core code with internal equivalents

@corivera is this something that we need to be tracking for April?

No, it's just some cleanup we need to get around to eventually


error ludwig after install tensorflow-gpu

I installed ludwig in a virtualenv with last github master code and start successfuly train with CPU.
I have decided to install the GPU with the following command
pip uninstall tensorflow
pip install tensorflow-gpu
install completed But after run ludwig show the following error
(venv) D:\Project*****\virtualenv\ludwig-master-gpu>ludwig
Traceback (most recent call last):
File "D:\Project*\virtualenv\ludwig-master\venv\Scripts\ludwig-script.py", line 6, in
from pkg_resources import load_entry_point
File "D:\Project*\virtualenv\ludwig-master\venv\lib\site-packages\pkg_resources_init_.py", line 3250, in
@call_aside
File "D:\Project*****\virtualenv\ludwig-master\venv\lib\site-packages\pkg_resources_init.py", line 3234, in call_aside
f(args, **kwargs)
File "D:\Project****\virtualenv\ludwig-master\venv\lib\site-packages\pkg_resources_init.py", line 3263, in initialize_master_working_set
working_set = WorkingSet.build_master()
File "D:\Project*****\virtualenv\ludwig-master\venv\lib\site-packages\pkg_resources_init.py", line 583, in build_master
ws.require(requires)
File "D:\Project*****\virtualenv\ludwig-master\venv\lib\site-packages\pkg_resources_init.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "D:\Project*****\virtualenv\ludwig-master\venv\lib\site-packages\pkg_resources_init.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'tensorflow==1.14.0' distribution was not found and is required by ludwig

1.14.0

thanks
i removed env and installed it again of github last source and change requirements.txt replace tensorflow with tensorflow-gpu


Error while doing yarn install

I get this error in my local, then I tried with codespaces i get same error there too
error /workspaces/stamp/node_modules/canvas: Command failed.
Exit code: 1
Command: node-pre-gyp install --fallback-to-build
Arguments:
Directory: /workspaces/stamp/node_modules/canvas
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| linux | x64
node-pre-gyp info check checked for "/workspaces/stamp/node_modules/canvas/build/Release/canvas.node" (not found)
node-pre-gyp http GET https://github.com/Automattic/node-canvas/releases/download/v2.9.0/canvas-v2.9.0-node-v111-linux-glibc-x64.tar.gz
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.9.0/canvas-v2.9.0-node-v111-linux-glibc-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not installable for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v111 ABI, glibc) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.9.0/canvas-v2.9.0-node-v111-linux-glibc-x64.tar.gz
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info ok
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info find Python using Python version 3.10.4 found at "/home/codespace/.python/current/bin/python3"
gyp info spawn /home/codespace/.python/current/bin/python3
gyp info spawn args [

Solved after running PKG_CONFIG_PATH=/opt/X11/lib/pkgconfig/

I get an error on yarn too, but with different error messages.
This library depends on canvas, with requires some additional libraries. See https://www.npmjs.com/package/canvas
On OS X, running the following command solve all my install errors:
brew install pkg-config cairo pango libpng jpeg giflib librsvg pixman


Tasks that run Django queries mostly fail with "connection already closed"

I have a working Django 4.0 project. My Django 4.2 project will error out on almost any basic query that uwsgi-tasks runs.
With this code it simply is failing to run obj, created = Task.objects.get_or_create(id=task_id).
Any tips as to what could cause this? Is it simply me running a newer version of Django or is something else going on?
Here is the error output.
mark_running start
[2023-09-27 21:06:11] Background task 'process_async_events' is starting...
Traceback (most recent call last):
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/backends/base/base.py", line 308, in _cursor
    return self._prepare_cursor(self.create_cursor(name))
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
    return func(*args, **kwargs)
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/backends/postgresql/base.py", line 330, in create_cursor
    cursor = self.connection.cursor()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/psycopg/connection.py", line 853, in cursor
    self._check_connection_ok()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/psycopg/connection.py", line 489, in _check_connection_ok
    raise e.OperationalError("the connection is closed")
psycopg.OperationalError: the connection is closed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/uwsgi_tasks/tasks.py", line 539, in signal_handler
    return self.execute_now()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/uwsgi_tasks/tasks.py", line 228, in execute_now
    return self.function(*self.args, **self.kwargs)
  File "/home/ryan/apps/orderdirect/content/./tasks/tasks.py", line 131, in process_async_events_thread2
    process_async_events(timing, 2)
  File "/home/ryan/apps/orderdirect/content/./tasks/utils.py", line 141, in process_async_events
    rid = mark_running("process_async_events", timing)
  File "/home/ryan/apps/orderdirect/content/./tasks/utils.py", line 327, in mark_running
    obj, created = Task.objects.get_or_create(id=task_id)
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/manager.py", line 87, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/query.py", line 916, in get_or_create
    return self.get(**kwargs), False
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/query.py", line 633, in get
    num = len(clone)
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/query.py", line 380, in __len__
    self._fetch_all()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/query.py", line 1881, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/query.py", line 91, in __iter__
    results = compiler.execute_sql(
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/models/sql/compiler.py", line 1558, in execute_sql
    cursor = self.connection.cursor()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
    return func(*args, **kwargs)
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/backends/base/base.py", line 330, in cursor
    return self._cursor()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/backends/base/base.py", line 308, in _cursor
    return self._prepare_cursor(self.create_cursor(name))
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/backends/base/base.py", line 308, in _cursor
    return self._prepare_cursor(self.create_cursor(name))
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
    return func(*args, **kwargs)
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/django/db/backends/postgresql/base.py", line 330, in create_cursor
    cursor = self.connection.cursor()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/psycopg/connection.py", line 853, in cursor
    self._check_connection_ok()
  File "/home/ryan/apps/orderdirect/venv/lib64/python3.9/site-packages/psycopg/connection.py", line 489, in _check_connection_ok
    raise e.OperationalError("the connection is closed")
django.db.utils.OperationalError: the connection is closed
Wed Sep 27 14:06:11 2023 - error managing signal 1 on worker 2

Oops I think this was just caused by another uwsgi running the same project in the background.

Alright I'm officially stumped. I found that other copy of uwsgi running, stopped it and my problems disappeared. I then updated all my packages (Django 4.2.1 to 4.2.5) and the problem has reappeared. I've confirmed I don't have multiple UWSGI's running. I have no idea where to look here...

Hi, it looks like the issue related to db connection management, a single connection to a db is shared between your main application process and spooler process(es) and when your main application closes the connection - spooler fails since the connection is closed.
Here are couple workarounds which could be considered:

Set MAX_CONNECTION_AGE to None explicitly (https://docs.djangoproject.com/en/4.2/ref/databases/#persistent-connections), so the shared connection will never be closed - I would not recommend this for a serious project because of possible performance degradation.
Add lazy-apps: true to your uwsgi configuration file (https://uwsgi-docs.readthedocs.io/en/latest/Options.html?#lazy-apps). This should force a spooler to start in a separate process with a separate db connection.


Populate PBegin input when decoding from Runner API

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @robertwb

As a side note, I find it very surprising that () | Flatten(...) is allowed in the model.  It makes the reasonable expectation that the pipeline DAG traces back to PBegin through all paths non-intuitive.  Should we consider changing this behavior?

As a side note, I find it very surprising that () | Flatten(...) produces an AppliedPTransform with no inputs, and that it is allowed in the model.  It makes the reasonable expectation that the pipeline DAG traces back to PBegin through all paths false just for this special case, which is non-intuitive.  Should we consider changing this behavior?

Coverage increased (+0.01%) to 70.681% when pulling 843f3f5a7ad7cf5297b3078aa9e929efcdc7092d on charlesccychen:fix-runner-api-input into 346a77fa8e10e218109cbd100ffc12c35323d66e on apache:master.

LGTM
PBegin is not part of the model; technically these are simply zero-input PTransforms. PBegin is simply an artifact of the SDK. Not being able to handle the degenerate flatten would be a regression.

Thanks! Can you please merge?


"Something went wrong" randomly pops up

Microsoft PowerToys version
0.60..0
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
There were no actions by me that resulted in this error. These popups suddenly started two days.
And when I tried to interact with them by trying to copy the content from the error dialog, they all closed.
Attaching error log
2022-07-16.txt
2022-07-17.txt
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/dup #16975
System.DllNotFoundException: Unable to load DLL 'PenIMC_cor3.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)
   Source: PresentationCore
   TargetAssembly: PresentationCore, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
   TargetModule: PresentationCore.dll
   TargetSite: Boolean CreateResetEvent(IntPtr ByRef)
   at MS.Win32.Penimc.UnsafeNativeMethods.CreateResetEvent(IntPtr& handle)
   at System.Windows.Input.PenThreadWorker..ctor()
   at System.Windows.Input.PenThreadPool.GetPenThreadForPenContextHelper(PenContext penContext)
   at System.Windows.Input.PenThreadPool.GetPenThreadForPenContext(PenContext penContext)
   at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTabletsImpl()
   at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTablets()
   at System.Windows.Input.StylusWisp.WispLogic.OnDeviceChange()
   at System.Windows.Input.StylusWisp.WispLogic.HandleMessage(WindowMessage msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.SystemResources.SystemThemeFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)


Pods contains proper labels

Motivation

I've deployed BTP operator and the service with only one label selectors pointed to other applications so webhook was not requested when I was applying BTP operator resources

Approach
Pods contains labels which identifies only btp operator Pods
This PR fixes the issue: https://github.com/SAP/sap-btp-service-operator/issues/152

please merge your branch with main in order your build to run properly


Reform operator spread

Per conversation in #831, these commits make breaking changes to operator spreading.

Operator spreading now requires a splat: typeof ...[0] => [typeof 0]
Operator spreading now supports objects: typeof ...{a: 0} => {a: typeof 0}
The LHS of assignment operators can also be spread: ++...a{b, c} can be written as ...a{b, c} += 1

foo ...+...a<[b c]> => foo.apply(null, [+a['b'], +a['c']]) works.
(...a=b) -> never really worked (an array, even empty, will never be nullish) but is now an explicit error.
Close #831

That looks good! It might take me a few days before I can actually review it though.
I'd gladly hear anyone's opinions on this PR. Especially if someone happens to find a case where syntaxes conflict :).
I might also want to add a few more tests. It's a pretty big change.
When merged, I'll also create an issue to track the docs state about this.

I like the DRY aspect of this. And I can't think of any way this could currently conflict with standard argument spreading. And +1 for making odd edge cases explicit errors.

Seems like no one objected, so I'm just gonna merge it :). Thanks.


Include types with HaveReceived failure messages

Addresses part of the pain discussed in #326 by including type information with HaveReceived matcher failure messages.
This makes it more obvious when your test fails because your object expects a certain type but your test expectation unintentionally used the wrong type.

Thanks @idoru for getting this out there to keep the conversation going. I would prefer not to merge this as-is, because it seems that it decreases the signal-to-noise ratio in the majority of failure cases where type mismatches aren't the cause of the failure. I'm wondering if we can instead have a more specialized failure message that gets triggered when the expectation arguments don't match the types of the actual method.
I actually thought we had a behaviour like that in place already, but it doesn't seem to be working as I would have expected. I'll see if I can take a little time to investigate.

Yeah, I agree. This was easy enough to do, and I think you're right about the signal-to-noise ratio.


:bug: Anonymous Volume breaks webhook update

Fix #111

Need to add a functional test that validate the fix.

Need to add a functional test that validate the fix.

Done


[Gulp 4]gulp.watch,a conflic between the file name & folder name.

I'm using Gulp 4 to do some pre-compile in my project&use gulp.watch for auto compiling my *.jade files to *.html.Recently,I want to do some diffferent job between 'jade/*.jade' and 'jade/**/*.jade' when they're edited.Then i add a new watch to do this.
gulp.watch(['jade/*.jade'],function(){
      console.log('a')
})

When i edit jade/course.jade,log 'a',right.
But when i edit jade/course/sth.jade,still log 'a',wrong.
I've tried different globs but still can't solve the problem.
Finally i find out the problem.
When i edit jade/only/one.jade nothing logged,right.
then i add a new file jade/only.jade,
re-edit jade/only/one.jade,logged 'a',wrong
I'm quite sure it's a conflic between the  file name & folder name.
What version of gulp are you using?
Gulp 4
What versions of npm and node are you using?
node 6.9.0
npm 2.15.10

You aren't signaling async completion in your watch task.

@phated Sorry,my bad.But the async completion just to help Gulp detect if the task done,so that it can move on to the next task,right?And now I did the signaling ,this issue is still.
gulp.task('wt',function(){
    gulp.watch(['jade/*.jade'],function(done){
      console.log('hi12');
      done();
    })
});

I noticed that gulp.watch was base on chokidar.And tried to find some solutions on chokidar's repo.
And there were many similar Issues in chokidar.Now I'm sure this should be a bug deeper than gulp and chokidar.
I found a solution in this page isssue#296.
By setting the option usePolling: true can just fix.More details about usePolling, check chokidar's repo#performance.
gulp.task('wt', {
    usePolling:true
  },function(){
    gulp.watch(['jade/*.jade'],function(done){
      console.log('hi12');
      done();
    })
});

@phated Thx 4 help.


Outlined buttons have the same appearance on :active and :focus states

Slightly modified example from the docs:
<div class="btn-group" data-toggle="buttons">
  <label class="btn btn-primary-outline">
    <input type="checkbox" checked="" autocomplete="off"> Checkbox 1
  </label>
  <label class="btn btn-primary">
    <input type="checkbox" autocomplete="off"> Checkbox 2
  </label>
</div>

Once you clicked the button you can't say what is its state actually until you move your mouse pointer away (or on mobile devices - tap outside of the buttons area). So, if user have tapped some checkbox he can't really say what state is it in.
Compare this behavior with not outilined buttons.

I'm assuming you mean in v4 ?

Yep, there are no outlined buttons in v3

btw note that in your example code btn-primary-outline should be btn-outline-primary

My code was based on docs, it seems that outline buttons docs need to be updated.

actually, ignore me...i seem to have gotten myself mighty confused while hacking away with devtools. you and the documentation are right...

need to stop looking at the out-of-sync v4-alpha site, as it seems the naming was swapped at some point. i'll make a note to check/update the docs if needed.

just to confirm that the docs in the latest version here are up-to-date. it's just http://v4-alpha.getbootstrap.com that is quite a few commits behind.

@patrickhlauke I've checked the actual docs. See pull request.


[CWS] only report ebpfless selftest once

What does this PR do?
This PR makes it so the ebpfless selftests are only run once.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Uplink set

Description
Implementation of uplink set actions

added  comments to unmanaged device sample file and increased uplink tests coverage

Issues Resolved
#76
Check List

[x] New functionality includes testing.

[x] All tests pass ($ rake test).
[x] New resources and/or actions have are included in the matchers.rb and matchers_spec.

[x] New functionality has been documented in the README if applicable.

[x] New functionality has been thoroughly documented in examples (please include helpful comments).

[x] Changes documented in the CHANGELOG.

Thanks for the insights, all the issues have been addressed/commented in the code. Could you please take another look, @jsmartt? Ty!

Shoot. Well, trying to push a change added some recent commits from master. But I'm good with this now :smile:


(HTTP code 404) unexpected - manifest for mesosphere/mesos-master:latest not found

Expected behavior
Success while installing Mesos master.
Actual behavior
(HTTP code 404) unexpected - manifest for mesosphere/mesos-master:latest not found
Information about the Issue

Steps to reproduce the behavior

Open Kitematic
Search Mesos
Create new Mesos master.

it looks like there is no latest tag available, I did follow below steps to select most recent tag :

it looks like latest tag was not created at all


api versions out of date

The apiVersion for deployments and the ingress are not working for kubernetes 1.18. Even when manually upgrading them gives me issues:
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"

Even though I have apiVersion: apps/v1 in my deployments.
I am using:

helm: v3.2.4
kubernetes client: 1.18.5
kubernetes server: 1.18.3

I have the same problem using helm v3.3
when linting the chart shows a copuple of errors :
[tiber@linux fn-helm]$ helm lint fn ==> Linting fn [ERROR] Chart.yaml: apiVersion is required. The value must be either "v1" or "v2" [ERROR] templates/flow-deployment.yaml: the kind "apps/v1beta1 Deployment" is deprecated in favor of "apps/v1 Deployment" [ERROR] templates/flow-deployment.yaml: a Deployment must contain matchLabels or matchExpressions, and "test-release-fn-flow-depl" does not [ERROR] templates/fn-deployment.yaml: the kind "apps/v1beta1 Deployment" is deprecated in favor of "apps/v1 Deployment" [ERROR] templates/fn-deployment.yaml: a Deployment must contain matchLabels or matchExpressions, and "test-release-fn" does not [ERROR] templates/fn-ingress.yaml: the kind "extensions/v1beta1 Ingress" is deprecated in favor of "networking.k8s.io/v1beta1 Ingress" [ERROR] templates/fn-runner-node-deployment.yaml: the kind "apps/v1beta1 Deployment" is deprecated in favor of "apps/v1 Deployment" [ERROR] templates/fn-runner-node-deployment.yaml: a Deployment must contain matchLabels or matchExpressions, and "test-release-fn-runner" does not [ERROR] templates/ui-deployment.yaml: the kind "apps/v1beta1 Deployment" is deprecated in favor of "apps/v1 Deployment" [ERROR] templates/ui-deployment.yaml: a Deployment must contain matchLabels or matchExpressions, and "test-release-fn-ui" does not
On the other thought helm added some breaking changes to version 3. for example:  init, install --name doesn't exist anymore  🙄

Are there any plans to update this chart for recent versions of k8s APIs and Helm 3?

Are there any plans to update this chart for recent versions of k8s APIs and Helm 3?

I don't think this project has active development..

Are there any plans to update this chart for recent versions of k8s APIs and Helm 3?

I don't think this project has active development..

Yup, I swapped to OpenFaaS


Add support for Python 3.8.20, 3.9.20, 3.10.15, 3.11.10 and 3.12.6

Release notes:
https://blog.python.org/2024/09/python-3130rc2-3126-31110-31015-3920.html
Changelogs:
https://docs.python.org/release/3.8.20/whatsnew/changelog.html#python-3-8-20-final
https://docs.python.org/release/3.9.20/whatsnew/changelog.html#python-3-9-20-final
https://docs.python.org/release/3.10.15/whatsnew/changelog.html#python-3-10-15-final
https://docs.python.org/release/3.11.10/whatsnew/changelog.html#python-3-11-10-final
https://docs.python.org/release/3.12.6/whatsnew/changelog.html#python-3-12-6-final
Binary builds:
https://github.com/heroku/heroku-buildpack-python/actions/runs/10750205053/job/29818038722
https://github.com/heroku/heroku-buildpack-python/actions/runs/10751132694/job/29818059983
https://github.com/heroku/heroku-buildpack-python/actions/runs/10750206118
https://github.com/heroku/heroku-buildpack-python/actions/runs/10750206743
https://github.com/heroku/heroku-buildpack-python/actions/runs/10750207733
GUS-W-16690151.

Updated versions on:
https://devcenter.heroku.com/articles/python-support#specifying-a-python-version
https://devcenter.heroku.com/articles/python-runtimes#selecting-a-runtime
Published changelog entry:
https://devcenter.heroku.com/changelog-items/2986


can we treat --query as placeholder?

[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
my usecase in steps

$ fzf --query='hello' --query-as-placeholder
user input w
fzf removes "hello" from the input, and set it to "w"

this is really convenient when fzf is used in nvim repeatly: first time user input something and got their result, second time the fzf nvim plugin will start fzf with --query='previous-input', and if user dont want previous input, user can simple type what they want without c-u first.
 --query-as-placeholder (or whatever name) indicates once user input a rune firstly, fzf will reset terminal.inputbefore processing tui.GetChar().
this usecase is just like html input tag's placeholder attribute
(yeah, i scratched a just-work commit to do this, hope it can make myself more clear)

I'm not sure if I want this feature in fzf (I think it can be confusing), but you can emulate the behavior like so.
fzf --query foo --bind 'change:clear-query+unbind(change)'

Oh, that will consume the first key press.

wow, nice to know that approach. though it have a little downside, it will not keep the rune/key i just pressed after clear.

it can be confusing
to me, it's just a standard behavior of html <input placeholder="foo">

well, this does bring in additional complex: user may want to custom its fg, bg, style ... (i dont need that so far)

to me, it's just a standard behavior of html <input placeholder="foo">

Well, fzf is not an HTML <input>, so.

custom its fg, bg, style

That is required if we are really going to do this. There must be a visual cue to let the user know if the text on the prompt is going to be cleared or not.

i just found it while writing a reply using text area, haha

But in that case, you can't press Comment button and "Leave a comment" message is not posted as a message.

yeah, you are right on this case. but if you put it in a search box, then this placeholder do have a meaning when you dont type anything just click the submit button.

This partly works,
fzf --query foo --bind 'change:unbind(change)+backward-char+unix-line-discard+forward-char'

except it breaks when the user presses a non-character key such as backspace. So a more general approach would be to add char event in addition to change that is triggered when the user types in a "character".
fzf --query foo --bind 'char:unbind(char)+clear-query+put'

i'm fine with both of them, i can do some logic on (n)vim side.

and yes, i really like this event+action approach, it avoid adding various cli flags and is more flexible.

(i'm not familiar to ruby, so i can't easily add a test and run it locally, but this Char event is rather easy to implement :) )
thanks for your time! do you think this issue can be closed? it's done on my side.

I haven't decided if I want to add the event to fzf. It feels like a niche feature that few users will find useful, I'd like to hear what others think.

another week passed. i think you are right, not much users need it.
thanks for your help about the event+action solution, and thanks for your time.


moveToNewFile: Update namespace imports (#24612)

Port of #24612

looks like you need another change for this to be ported to release-2.9


KeyError: 'text_backbone.encoder.all_layers.0.attn_qkv.weight'

It is fine when I fit the text classification model with default settings, but accuracy is only about 35%,
so I tried to use the bert base model with following code
predictor = TextPredictor(label='label', problem_type='multiclass', path='./ag_sst')
predictor.fit(train_data, presets='multi_cased_bert_base_fuse_late', time_limit=60)
with this error raised:
~/.conda/envs/spacy3/lib/python3.7/site-packages/mxnet/util.py in _with_np_array(*args, **kwargs)
479         def _with_np_array(*args, **kwargs):
480             with np_array(active=True):
--> 481                 return func(*args, **kwargs)
482         return _with_np_array
483     else:
~/.conda/envs/spacy3/lib/python3.7/site-packages/autogluon/text/text_prediction/mx/utils.py in average_checkpoints(checkpoint_paths, out_path)
18                 arr = data_dict_l[i][key]
19             else:
---> 20                 arr += data_dict_l[i][key]
21         arr /= len(data_dict_l)
22         avg_param_dict[key] = arr
KeyError: 'text_backbone.encoder.all_layers.0.attn_qkv.weight'

We have upgraded the TextPredictor to support huggingface backbones.
Compared with the TextPredictor in AutoGluon 0.3, the TextPredictor in AutoGluon 0.4 has 72.22% win-rate in the multimodal text-tabular benchmark. If we use the “high_quality” preset, the win-rate increased to 77.8% thanks to the microsoft/deberta-v3-base backbone.
In addition, the new version has ~2.88x speedup in training and ~1.40x speedup in inference. With g4dn.12x instance, the model can further achieve 2.26x speedup with 4 GPUs.
You may try the new version and feel free to reopen if the issue persist.


Simplify programmatically sending invitations

I'm working on an application that has USER_ENABLE_INVITATION and USER_REQUIRE_INVITATION set. In the initial database, there are no users and an elegant way to bootstrap that would seem to run a flask cli command to send an initial invitation.
With the code shown below, I can send an invitation as follows:
SERVER_NAME=localhost:8000 FLASK_APP=app flask invite<EMAIL_ADDRESS>
However, the below code is quite long and mostly copy-pasted from the views.invite function. It would probably be more elegant if UserManager exposed an invite() method (or something like that), that could be used from the application as well as from views.invite.
Here's what I'm using now:
@app.cli.command('invite')
@click.argument('email')
def initdb_command(email):
    """Invite a user to this project."""
    user_invite = db_adapter.add_object(
                db_adapter.UserInvitationClass,
                    email = email,
                    invited_by_user_id = -1,
                )
    db_adapter.commit()
    user_invite.token = user_manager.generate_token(user_invite.id)
    db_adapter.commit()

    accept_invite_link = flask.url_for('user.register', token=user_invite.token, _external=True)

    try:
        # Send 'invite' email
        flask_user.emails.send_invite_email(user_invite, accept_invite_link)
    except Exception as e:
        # delete new User object if send fails
        db_adapter.delete_object(user_invite)
        db_adapter.commit()
        raise

    print('Sent invite to ' + email)

Nice to find out that someone is actually using the USER_ENABLE_INVITATION and USER_REQUIRE_INVITATION features!
Great minds think alike: Flask-User v0.9 (alpha) and v1.0 (stable) will provide customizable view methods inside a customizable CustomUserManager class. My plan is to offer low level 'building block' methods that views can use. This building blocks will also be available for custom use such as your command line invitation. Stay tuned.
Here is a v0.9 docs preview: http://flask-user.readthedocs.io/en/latest/

I know this is an old thread, but here goes.
I commented out a raise exception that was preventing the /user/invite page to show... I guess that's for @northtree -- I'll post later the file and line numbers
Now when I invite a user (via email address) I get a 500 code...It's odd since it does do the right flash() response when an email address is already present in the system....looking at the error log on the server, it's point to this:
user_invitation = self.UserInvitationClass(**kwargs)
TypeError: 'NoneType' object is not callable

from here: /site-packages/flask_user/db_manager.py", line 125, in add_user_invitation
any help or ideas would be greatly appreciated...I'm thinking of trying to build my own invite system that sends a URL with an AUTH token into the the Registration page (I'm guessing that's exactly how this setup in flask-user should work but it seems to be a bit buggy here).
Thanks for reading this!
-Doug Jr.

Hi everyone,
@douglasmccormickjr I had a similar issue while I was resetting my project's dependencies. Erasing the database led to a similar behaviour due to cookies being present and database empty.
@lingthio I really enjoy your work here! I read your comment about the upcoming custom classes you'll be introducing.
Are you still considering an invite method as a possible feature or do you prefer to leave this mechanism to each programmer's custom class?
Cheers!


Update copyright statement

This PR also needs to be duplicated across all repos

We will do that...

Awesome, thanks!


min size is not scaled correctly?

Hi,
Is the default min_size calculated based on (640x640)?
I found the scale of width and height of each anchor is weird.
https://github.com/biubug6/Pytorch_Retinaface/blob/master/layers/functions/prior_box.py#L23
s_kx = min_size / self.image_size[1]

I think it should be
s_kx = min_size * (self.image_size[1] / 640)

when testing with new image scales.
Not sure if I am right.
thank you.

I was wrong.


Add org.freedesktop.fwupd appstream check

See #23

If we merge https://github.com/flathub/org.flatpak.Builder/pull/111 then we don't need this exception.


Renames new_from to from_reader in order to align better with common rust naming.
Adds iterators for Rules.
Adds derive(Debug) to rules related types.

Thanks for this PR! I'm still not that familiar with some Rust conventions so this is great. At this stage breaking changes are not a problem if it means better alignment with conventions.

Thanks!


Create a lightweight agent for Docker Hosts to retrieve more detailed Host information

[ ] OS information
[ ] Hostname
[ ] CPU usage/cores/speed
[ ] Memory usage
[ ] Storage usage
[ ] Docker version
[ ] Streams for performance charts (CPU, memory, network util., ...)

Will not be implementing at this stage. Moved to the-concierge#7


0.15.0: cannot import name '_check_google_client_version' from 'pandas_gbq.gbq'

Versions of related packages inside the webserver container:
airflow@cfaac0843862:~$ pip freeze | grep pandas-gbq
 pandas-gbq==0.15.0
airflow@cfaac0843862:~$ pip freeze | grep google-cloud-bigquery
 google-cloud-bigquery==2.13.1
 google-cloud-bigquery-storage==2.3.0

I'm running into this issue as well with pandas_gbq using BigQueryHook in Airflow.

Do you have a fuller stack trace? That attribute is not in v0.15.0's gbq.py. What is attempting to import that? It may be another library.

Hi @max-sixty ,
Sorry I didn't put that stack trace in the first place (because it was basically just an import).
As @Yinabled aforementioned, that call happens at
https://github.com/apache/airflow/blob/1.10.15/airflow/contrib/hooks/bigquery_hook.py#L39 as
from pandas_gbq.gbq import \
    _check_google_client_version as gbq_check_google_client_version

OK — this is an issue for airflow, then. That's a private function; they need to either vendor it or use a public function.


[feature]support for custom component plugin

https://github.com/VisActor/VRender/pull/158 completed in this PR


Notebook2

It should fix the issues you encountered. If not, can you tell if it works when you remove the with_gtk_3_16 please?

So, have you tested?

This does allow the menubutton to work now, but it does undo a number of recent commits made to the glade and the source code, such as menu button changes.

Okay, with your build, I get this:
src/systemd/dbus.rs:146:1: 164:2 warning: function is never used: `enable_unit_files`, #[warn(dead_code)] on by default
src/systemd/dbus.rs:146 pub fn enable_unit_files(unit: &str) -> Option<String> {
                        ^
src/systemd/dbus.rs:168:1: 186:2 warning: function is never used: `disable_unit_files`, #[warn(dead_code)] on by default
src/systemd/dbus.rs:168 pub fn disable_unit_files(unit: &str) -> Option<String> {

And the MenuButton does not allow clicking.

If I remove with_gtk_3_16 I get
systemd_gui.rs:167:19: 167:31 error: no method named `set_position` found for type `gtk::HeaderBar` in the current scope
systemd_gui.rs:167         right_bar.set_position(1);
                                     ^~~~~~~~~~~~
systemd_gui.rs:167:19: 167:31 note: the method `set_position` exists but the following trait bounds were not satisfied: `gtk::HeaderBar : gtk::IsA<gtk::Editable>`, `gtk::HeaderBar : gtk::IsA<gtk::Window>`, `gtk::HeaderBar : gtk::IsA<gtk::Popover>`
error: aborting due to previous error

You can specifiy the position with Glade though.

And if I remove that one line, I just get a panic on a None value:
thread '<main>' panicked at 'called `Option::unwrap()` on a `None` value', ../src/libcore/option.rs:325
stack backtrace:
   1:     0x56465cab0e20 - std::sys::backtrace::tracing::imp::write::h9fb600083204ae7f
   2:     0x56465cab4d6b - std::panicking::default_hook::_$u7b$$u7b$closure$u7d$$u7d$::hca543c34f11229ac
   3:     0x56465cab49f3 - std::panicking::default_hook::hc2c969e7453d080c
   4:     0x56465caa77df - std::sys_common::unwind::begin_unwind_inner::h30e12d15ce2b2e25
   5:     0x56465caa82e8 - std::sys_common::unwind::begin_unwind_fmt::hb2de8a9968d38523
   6:     0x56465cab01e1 - rust_begin_unwind
   7:     0x56465caeafaf - core::panicking::panic_fmt::h257ceb0aa351d801
   8:     0x56465caeb288 - core::panicking::panic::h4bb1497076d04ab9
   9:     0x56465ca579ad - _<std..option..Option<T>>::unwrap::h6ba146c0d1022871
                        at ../src/libcore/macros.rs:21
  10:     0x56465ca44901 - systemd_manager::systemd_gui::launch::hec754e8cc76f2b1b
                        at /home/mmstick/Programming/testing/systemd-manager/src/systemd_gui.rs:170
  11:     0x56465ca43fe8 - systemd_manager::main::h22a01905651f008f
                        at /home/mmstick/Programming/testing/systemd-manager/src/main.rs:10
  12:     0x56465cab4634 - std::sys_common::unwind::try::try_fn::h04c0c89e4add6cc4
  13:     0x56465cab016b - __rust_try
  14:     0x56465cab407b - std::rt::lang_start::h61f4934e780b4dfc
  15:     0x56465ca474f9 - main
  16:     0x7f3e41a17740 - __libc_start_main
  17:     0x56465ca43ed8 - _start
  18:                0x0 - <unknown>

With the first version I patched it was possible to use an older version (I fixed the issue). But with the current version, it wouldn't have any sense.


Investigate e2e test execution time

Background
E2E execution time takes very long. Often takes 8+ minutes, adding notable delay to CI (and thus developer flow). Roman's made a series of very helpful issues for mitigating build times. This issue is for investigating whats happening in our test execution time. CI run copy/paste for reference
--- PASS: TestIntegrationTestSuite (431.08s)
    --- PASS: TestIntegrationTestSuite/TestCreatePoolPostUpgrade (5.42s)
    --- PASS: TestIntegrationTestSuite/TestIBCTokenTransfer (94.79s)
    --- PASS: TestIntegrationTestSuite/TestSuperfluidVoting (77.14s)

Ideas
Ideas I have for why this could be taking so long (in sequence of what I'd try / check):

What are block times in e2e? For e2e test, we should be setting precommit_timeout_wait to be negligible. I'd even suggest 5ms, we gain nothing by having delay in these tests. We don't need every validator signing every block either.

Lets just adjust this config parameter and see what happens?

Whats the blocking behavior for subsequent txs and subsequent queries?

Are we getting blocked in this? Can we add a "time trace'" to our ExecCLI & ExecQuery commands to learn more?

Are relayers getting stuck in getting things onto both chains?

Acceptance Criteria
We have some understanding of where time is getting stuck, via "guess and check", metrics / hacky log file, or otherwise

Some things that strike out to me with adding some basic time logging in https://github.com/osmosis-labs/osmosis/pull/2103 is that:

We are running all tests / actions in sequence. When we have more tests post-upgrade, they should be able to run in parallel if they use different accounts
IBC test is really slow (looks like 1.5 minutes, and is ran twice)
Superfluid voting - we should be doing votes across nodes in parallel. Maybe we can make a helper method for doing the same action, on all node configs, in parallel?

update from #2103, most of the time was in require.Eventually tick timers. Changing those brought execution time to 3min 30 sec! Once we can get the test config propogated to lower block times, we'll probs be fine for now in terms of execution time

Most of the items in this issue are tracked separately so I'm going to close this. Open an issue for parallelizing tests


updated my bio and picture

updated bio and picture in subspace page

Hi Rogers, apologies, my first edit was to erase the URL in the local config file as was suggested to try to bypass my port issue but that didn’t work. Then I updated the subspace yml with my bio and added my picture, and used “bundle exec jekyll serve —config _config_local.yml —port 4001”. That worked to create a local website that I looked correct, and that’s what was committed. It must have rewritten aspects of the HTML file as a result, including changing all values of 4000 to 4001 and swap Hussain and Mite’s bios (as far as I can see it’s a swap and no info is lost). Let me know if any of that was wrong to do, again my apologies

@j-hanania  no worries at all! Just make a new pull request where only data/subspace_volunteers.yml has been modified. Can you do that?

Yes, the _site folder is in gitignore and should not have been merged. But no big deal.. it can be fixed later.
@j-hanania should submit a PR that contains modifications to the yml file only. The html file is going to stay in his local when he compiles the site.. but as long as it is not being committed that is fine.

@esalman The HTML file is already being tracked since before @j-hanania first pulled. The only way he can send a PR without the HTML file is if he removes it from the git index, which I think is the right thing to do bc it should have never been there.
The problem is that it will cause the HTML file to be deleted locally the first time anyone pulls the repo after this git index update. This would be OK IF jekyll creates the file again automatically. Is that the case @esalman ?

Yes correct, doesn't matter if the html file is delete from the index, it will be regenerated every time the site is compiled.

@j-hanania Could you try the following in your develop branch? (check if the path&filename are correct)

If you made any changes recently: stage and commit the changed files in your develop branch.

Continue from step 5 e) in the guide from Carlos.

You may not need to repeat step 6... check if you can just 'update' this PR.
Otherwise, use step 6 in the guide to create a new PR.

Looking into it now!
I tried to commit just the yml and jpg files yesterday but it got blocked saying that my branch wasn't up to date, despite following Carlos' workflow instructions. I'll try now again and see if it works.

@j-hanania
It looks like some conflicts popped up in your develop branch after we accepted Anjali's PR.
This is normal. It only means they are gonna have to be resolved before updating your PR.
FYI, that can be a bit frustrating, but we will help you along the way. :-)
Just keep us posted of any problems you come across.
Heads up: at this point you should go from step 5 d) in Carlos's guide to update your local master and rebase you local develop branch. If the commit is being blocked, you may have to git add first. Otherwise, send us the commands you issued and the full output you see on the terminal.
Thanks for your patience!


bug, "NewObject, todo, infer type"

CLASS lcl_bar DEFINITION.
ENDCLASS.
CLASS lcl_bar IMPLEMENTATION.
ENDCLASS.

FORM moo.
  TYPES: BEGIN OF ty_dict,
           rollname TYPE string,
           obj      TYPE REF TO lcl_bar,
         END OF ty_dict.

  DATA(ls_blah) = VALUE ty_dict(
      rollname = 'bar'
      obj      = NEW #( ) ).
ENDFORM.

https://syntax.abaplint.org/?filter=read#/statement/ReadTable


Do not skip the status test

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>Fixes #

Proposed Changes

Remove a skip, committed here

Release Note

Docs

/assign @lionelvillard  not sure if there was a reason to skip it.
Please review the removal of the skip


Provide argument to worker command to run only one specific build

Adds the --build-id option to the worker-command.
If set, the worker only tries to run the build with the given id.
If no build with given id available, it exits.
As discussed in https://talk.vespene.io/t/slurm-isolation/49/18.

 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.

Hi @ynop - I made some style suggestions above - I think they are pretty straightforward, but if you would rather me take a shot at them, let me know.
Let me know if there are questions!

Hey, I can't see any reviews. Do I miss something?

Hi, sorry about that, I'm very new to the github review widget!  I submitted some stuff.
I apologize for being a little more picky than usual (one of these might be a push as to whether it's actually better), though they should all be pretty easy.

Thanks for sending this along and apologizes on not staying on top of my GitHub notifications.
This looks good, the only minor catch is I noticed if there is no build it returns 0, when it should probably return non-zero?
I'll test this out soon, but I can go ahead and change that constant.  Looks good!

All merged in, apologies on the delay - thank you!
(I didn't change anything except for the return code for when the build was not found)


fix(index.ts and index.test.ts): refactored the plugin to support latest version of semantic release

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[5.8] Fix container contract violations

The Container contract concrete implementation also implements ArrayAccess (it uses the methods which are on the contract to implement ArrayAccess). As the Container contract itself doesn't extend ArrayAccess we cannot use ArrayAccess when resolving services from the container as a Illuminate\Contracts\Container\Container contract implementation isn't forced to implement it and would break when we'd attempt to resolve the services from it that way. Some parts of the framework are using ArrayAccess which is a clear violation of the contract while on some other places the proper contract methods are used so not only is the contract violated in a lot of places, the entire code is pretty inconsistent. This PR aims to fix that. I also added some type-hints for better IDE auto-completion in Closures.

Wouldn't the easier change just be to add ArrayAccess to the contract?

@taylorotwell It sure would've been easier for me to do just that than to go through and change all this code, but I didn't wanna force all implementations to implement ArrayAccess since the current contract has everything we need and I consider ArrayAccess just another "fancy" way of getting the same thing. But if adding that to the contract is fine with you I'll just send another PR with just that.

I was glad to see that some magic stuff will be changed with unified solution. Just don't like when same things could be solved in many ways without any reason for it.


python311Packages.websocket-client: 1.6.3 -> 1.6.4

Changelog: https://github.com/websocket-client/websocket-client/blob/v1.6.4/ChangeLog
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

@ofborg build python311Packages.websocket-client python311Packages.kubernetes

Part of #271586


Update README.md

I have written short description of what osmlab.github.io can be used for. I would like to contribute more for the home page but  could not find Html file in the repository.

Thanks for adding something here.
OSM Lab is more than just the changeset analyzer, though. Can you add references to the other projects in the OSM Lab organization?


Configure Hound to use in-repo SCSS lint config

The enabled flag is now turned on.
The file name is scss/.scss-lint.yml.

https://twitter.com/mdo/status/581544087146254338

Damn, that's a huge oversight on my part :laughing:.

Thanks!


prisma-engines: 3.14.0 -> 3.15.1

Description of changes
Changes since 3.14.0:

https://github.com/prisma/prisma/releases/tag/3.15.0
https://github.com/prisma/prisma/releases/tag/3.15.1

Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@pimeys As there are tests now it is possible to automate the upgrade process (so you don't have to manually do it yourself). An update script is necessary to update the two packages at once and keep version in sync. But should be simple. It's just a suggestion.

I'm doing the engines with nix-update and it works superb. With the node package it just crashes, even if we set the version statically in the overrides.
That would be great so we could automate everything, no matter how much I enjoy doing these PRs :)

With the node package it just crashes, even if we set the version statically in the overrides.

On reading the manual on JS packages:
A JS package (manually packaged in nixpkgs) should only provide end user software packages, such as CLIs. Libraries should only be added to the package set if there is a `non-NPM package` that requires it.

When it is desired to use NPM libraries in a development project, use the `node2nix` generator directly on the `package.json` configuration file of the *project*.

Is the package nodePackages.prisma used by the prisma-engines package or the other way around?
If not, maybe nodePackages.prisma package could be removed from nixpkgs so it is downloaded directly by the JS/npm project fetcher instead from nixpkgs. And prisma JS package would be kept at sync at package.json at JS side instead of from Nix side?

The engines must be there though and the flake/shell definition must have the env vars for the CLI to work, but yes that sounds feasible.
The only thing what I'm thinking is there might be people who want the CLI to their system.

This PR is ready to be merged.

@bobby285271 Beyond me, @tomhoule has also approved it. He left a message saying lgtm. Isn't that good enough?

The labels are semi-automatic updated by https://github.com/nix-community/label-approved

I didn't click approve but just signaled that I read the PR because I'm just someone who works at Prisma and uses nix, I don't consider myself a qualified nixpkgs reviewer :)


Need a xml document attribute to specify request model, similar to the response /// <response ...

I have an ASP.NET Web API (lets say A) controller, actually it is a "proxy": it forwards all the requests to an internal Web API (lets say B). So the API A accepts any request and just forward it to API B and let API B do validation check and respond.
My solution is to use a parameter-less controller action and inside the action to use HttpClient to forward the request to API B. code like below:
        /// <response code="200" cref="ReturnModel"></response>
        [SwaggerResponse(HttpStatusCode.OK, Type = typeof(ReturnModel))]
        public async Task<HttpResponseMessage> Post()
        {
            var client = new HttpClient();
            Request.RequestUri = Uri_Of_B;
            return await client.SendAsync(Request);
        }

The code works well. But unfortunately, the generated Swagger page does not show the input box to let user input request body and try.
So, I request to support an xml document attribute like ///  to specify request input model.
I do not want put the InputModel as parameter in the Post action/method for two reasons:

I want the action accept any input message even invalid model, but if I put the InputModel in Post parameter, I will loose the input from forwarding to API B.
Request.content will be empty if I put any parameter in Post method.

Going forward, I want to limit the use of XML comments to just populate free-text fields, like "description" and "summary", in the generated Swagger. For the structured metadata like parameter and response schema's, which are more tightly-bound to the implementation code, the provided Swagger attributes or the built-in .Net attributes (e.g. ResponseType) should be used.
Yours seems like a pretty special case and so I'm reluctant to make exceptions within the library to support it. However, you can achieve what you're trying to do very easily with an Operation filter (see readme). Here's an example to get you started:
public class AddDefaultPostParameter : IOperationFilter
{
    public void Apply(Operation operation, SchemaRegistry schemaRegistry, ApiDescription apiDescription)
    {
        if (apiDescription.HttpMethod == HttpMethod.Post
            && apiDescription.ParameterDescriptions.Count == 0)
        {
            operation.parameters = new List<Parameter>
            {
                new Parameter
                {
                    name = "body",
                    schema = schemaRegistry.GetOrRegister(typeof(InputModel))
                }
            };
        }
    }
}


Document PublishReadyToRunShowWarnings MSBuild property

The dotnet-publish page mentions the property PublishReadyToRun but it doesn't mention the property PublishReadyToRunShowWarnings
Some ReadyToRun compilations emitted warnings, indicating potential missing dependencies. Missing dependencies could potentially cause runtime failures. To show the warnings, set the PublishReadyToRunShowWarnings property to true.

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

ID: 211afdc7-c796-202d-239d-823f2a499dff
Version Independent ID: 9439897e-dcb3-bc2e-5cae-35c1ca2e0681
Content: dotnet publish command - .NET Core CLI
Content Source: docs/core/tools/dotnet-publish.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Thanks for the suggestion, we'll add this the next time we update the article.


Cognitive Service data plane swaggers (face, computervision, etc. does not have descriptions).

@fearthecowboy - Please take a look. Filing an issue as discussed.
Some examples

https://github.com/Azure/azure-rest-api-specs/blob/current/specification/cognitiveservices/data-plane/Face/v1.0/Face.json#L1846

https://github.com/Azure/azure-rest-api-specs/blob/current/specification/cognitiveservices/data-plane/Face/v1.0/Face.json#L1874

@lebronJ can you please add necessary descriptions?

Hi, anuchandy, I think the latest Face API spec already has necessary descriptions by last commit.

Closing this ticket as the Face API addressed the descriptions.
@amarzavery please re-open if there are any remaining issues that need to be addressed.
Thanks,
Chris


Transition to VTK7

Now Slicer has switched to VTK7, it makes to transition.
Reading the Migration Guide written for Slicer should help: https://www.slicer.org/slicerWiki/index.php/Documentation/Labs/VTK7
Cc: @cdeepakroy @aylward

ITKTubeTK works with VTK 8.


'NoneType' object is not subscriptable

After startup i got error in telegram messages:
Something went wrong during completion. Reason: 'NoneType' object is not subscriptable

Went into the same issue.
How did u get over it ? @snegodick

Went into the same issue. How did u get over it ? @snegodick

I already forgot, sorry :) But the problem was on my side - check DNS or something like that.

Went into the same issue. How did u get over it ? @snegodick

I already forgot, sorry :) But the problem was on my side - check DNS or something like that.

Thanks for the tip. I'll check it. :)

Went into the same issue.  So not the disk.
I just waited for several minutes after docker compose up, and retry the telegram bot, it worked.
Still confused what standed in the way. Maybe i'll dig into it when i have time.

I had the same issue, started chatting without sending /new was the issue


add: error message for case when metadata file doesn't exist

Provide users with a more informative error message in case where metadata file passed to qza_to_phyloseq doesn't exist, as mentioned in the issue #62.

Great!


Allow assign private ip in config Fixes #52

This fixes #52 by adding private_ip_address option to config

Coverage increased (+0.23%) to 84.58% when pulling e2c8da5fbd9a873c73c5981c4407168c6ac69a1f on j00p34:master into a0a926767185ff309e946b31ccf120cbba06b3e9 on schubergphilis:master.

@miguelaferreira please review my pull request

@j00p34 doesn't this change also require a change in the underlying fog model?

nope. That was not needed. I've been looking in the wrong direction all the time.
This is tested and works with standard fog. (but you're always welcome to test it yourself)

LGTM


set up github & drone workflows

after the split from the original repo we no longer have automatic testing, we should fix that.
pending configurations:

[ ] .drone.yml
[ ] .github/workflows/

[ ] macos_test.yml
[ ] ubuntu_test.yml
[ ] windows_test.yml

I've just added the -renamed as WIP- workflow files, extracted from the notcurses repository, with other bindings parts removed, as a base to work on.

linux github actions are working, trying to make macos & windows pass


what would cause "dockerinit unable to execute /usr/sbin/sshd - accessing a corrupted shared library"

This happened on a previously running docker container and ssh access was working like a charm. sshd is used to keep it running so that I can ssh into it and configure it using Ansible Playbooks.
Here's my Dockerfile for the image:
FROM centos:latest

MAINTAINER ...

# install openssh server
RUN yum -y install openssh-server

# install openssh clients
RUN yum -y install openssh-clients

# make ssh directories
RUN mkdir /root/.ssh
RUN mkdir /var/run/sshd

# create host keys
RUN ssh-keygen -b 1024 -t rsa -f /etc/ssh/ssh_host_key
RUN ssh-keygen -b 1024 -t rsa -f /etc/ssh/ssh_host_rsa_key
RUN ssh-keygen -b 1024 -t dsa -f /etc/ssh/ssh_host_dsa_key

# move public key to enable ssh keys login
ADD docker_ssh.pub /root/.ssh/authorized_keys
RUN chmod 400 /root/.ssh/authorized_keys
RUN chown root:root /root/.ssh/authorized_keys
# tell ssh to not use PAM
RUN sed -i 's/UsePAM\syes/UsePAM no/' /etc/ssh/sshd_config

# make the terminal prettier
RUN echo 'export PS1="[\u@docker] \W # "' >> /root/.bash_profile

# enable networking
RUN echo 'NETWORKING=yes' >> /etc/sysconfig/network

EXPOSE 80
EXPOSE 22

ENTRYPOINT ["/usr/sbin/sshd"]
CMD ["-D"]

Update
Running on Vagrant - CentOS release 6.4 (Final) box using docker-io. Vagrant box hosted on a Mac.

Based on the official response from @jimperrin (now @jperrin), I'm going to close this and recommend and update to the latest CentOS using yum update and a reboot.


Install.sh fails if unzip is not installed

If unzip is not installed, the install.sh should install it for you

No, but it should be documented in the README.

Yep, this belongs in the "Known Issues" section of the README: https://github.com/denoland/deno_install#known-issues

Hello,
I ran into this issue installing deno inside docker, I believe we could use tar to make the install more portable. As I was just working on this I don't mind making a PR.

I think part of this is because deno moved from a gzipped binary to a zip file. I remember having to update my aur package, and had to add unzip because I didn't realise that it wasn't part of base-devel (in arch) like gzip was. Can i ask why we removed that gzipped file? It was nice and easy to use imo

We have updated the readme in the known issues section and moved program checks to the start of the file.
@MarkTiedemann I believe it is reasonable to close this issue.


Pract.03: Add 13,14,16 | Bogomil Pankov

SI 4 6MI0600428

Task 13 - I've made changes to the code that will make it more readable. I advise you to look at exactly what I changed. I added an additional condition that checks if the input to the num variable is valid.
Task 14 - The logic in the solution you sent is not correct. As a counterexample, enter the input 3 4 4 4.
Таск 16 - The solution is alright.


[importer_direct_upload_blog] blog post for direct upload in importer is added

What changes were proposed in this pull request?

blog post for importer direct upload

Looks great! Thanks.


Rails 3.2 is almost out

Rails 3.2 is almost out

+1

+1

+1

+1

+1

+1

+1

+1

+1

i close this as it was fixed :)

thank you!


[477] Add Initial State rules for delegation to the Byron spec

Edits the Byron Ledger spec - adds initial rules for delegation (initial rules already exist for other parts of the spec) - where possible, refer to existing init rules
Issue: https://github.com/input-output-hk/cardano-ledger-specs/issues/477

I haven't followed why delegEnv and delegSt instead of whatever was there before. Would you mind explaining?
Also, should in e.g. Figure 18 both equation (15) and equation (16) be present? Perhaps @dnadales can confirm. The same question goes for (18) and (19) in Figure 19.

@mdimjasevic we use delegEnv/delegSt to avoid repeating the initial env/state once they are defined.
Eq (15) states that when processing a sequence of delegations (SDELEGS), we can inherit the init state from SDELEG, whereas Eq (16) states that in the case of an empty sequence of delegations, the state will be unchanged by the rule. The same goes for (19).


Update the docker-compose configuration to fix building issues

Fix CircleCi containers building

Change how Docker is installed in Dockerfile.compute_worker

Change the port of selemium in docker-compose.selenium.yml from 5900 to 5904 to avoid bind: address already in use error

I think this commit broke the v15 submission automated test:
https://app.circleci.com/pipelines/github/codalab/codabench/767/workflows/d379f8f5-146b-4b2a-95fc-ee9d6055e28d/jobs/2428
FAILED src/tests/functional/test_submissions.py::TestSubmissions::test_v15_submission_end_to_end
in e2e Tests.

Now the three following tests are not passing:
=========================== short test summary info ============================
FAILED src/tests/functional/test_submissions.py::TestSubmissions::test_v15_submission_end_to_end
FAILED src/tests/functional/test_submissions.py::TestSubmissions::test_v18_submission_end_to_end
FAILED src/tests/functional/test_submissions.py::TestSubmissions::test_v2_submission_end_to_end
============= 3 failed, 5 passed, 8 warnings in 400.20s (0:06:40) ==============

It can be due to this commit, but most likely due to the many commits that were pushed with failing automated tests.
Should we go back to the last working version? Or try to fix the bugs now that we have potentially the automated testing workflow working?
@NehzUx @dtuantran
It is really problematic that some people did all these commits without bothering about testing... the platform is broken currently.

Strangely, the problem seems to be independent from the version of the repository.
The following branch: https://github.com/codalab/codabench/tree/test-old-develop
is an old version of develop that worked before. Now the tests are not passing.
>       prediction_score = Submission.objects.get(pk=submission_id).scores.first().score
E       AttributeError: 'NoneType' object has no attribute 'score'

I don't know what could have changed in between.


请问下 再次打开nvim ,按u 还能 撤销 (保存已经关闭的文件的操作历史记录) 的 插件 叫什么名字

Describe the bug
如题
To Reproduce
Steps to reproduce the behavior:

neovim 编辑 aaa.txt
wq退出
neovim 再次编辑  aaa.txt
按u 撤销
原生的 vim/nvim 这样是不行的， 应该是装了插件吧？ 不知道这个插件的名字……

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: [e.g. Archlinux/Ubuntu/macOS]
Nvim version(output of nvim --version)

Additional context
Add any other context about the problem here.

It's vim/neovim's feature call Persistent Undo history.
Refer to this: https://jovicailic.org/2017/04/vim-persistent-undo/

It's vim/neovim's feature called Persistent Undo history. Refer to this: https://jovicailic.org/2017/04/vim-persistent-undo/

谢谢！


GH-2897: Add tests for MyGetProvider

Fixes #2897 Add unit tests for MyGetProvider.
Additionally replacement of special characters was rewritten. Although original implementation (surprisingly) worked, it relied on implementation of Dictionary. Problem was that | should be replaced first, otherwise it would be replaced multiple times. However, Dictionary does not guarantee to enumerate items in the same order as they were added to the dictionary. So it was not guaranteed that | would be first token to replace.
I changed the replacement to iterate through characters of source string.
Also original code replaced [ by |['. I assume it was type and correct replacement is |[

@duracellko your changes have been merged, thanks for your contribution 👍


gkeV2- Labels field at cluster level, is missing

What kind of request is this (question/bug/enhancement/feature request): feature request
Steps to reproduce (least amount of steps as possible):
We are missing cluster level Labels parameter

Result:
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5-1963c2e01996894c36480583903f5d5642702269-head
Installation option (single install/HA):

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

(paste the output here)

I can create a label.

However, I cannot delete or add a new one, once the cluster is created.
GCP:

Added a UI fix to make the fields editable. Did not know they were.

I am still seeing issues with delete

I cannot delete a label from Rancher, if there is only one label present
If there are two labels and I try to delete one from Rancher, both labels get deleted (and I can no longer add a new label with the old key=value which got deleted, from Rancher)

There seem to be two issues here.
Back end: After a cluster is created which includes cluster labels (gkeConfig.labels) and the cluster has had enough time to provision and complete its first round trip sync, the labels exist in the upstream spec config and the metadata object in the Google GKE Console UI, but the gkeConfig.labels parameter is now null.
Front end: When we have labels in our upstream config and the user removes the labels during edit, the UI doesn't send an empty map to indicate the removal of the labels (see rancher/ui#4609)


Kafka <IP_ADDRESS> log format?

Hi guys, do you plan to implement <IP_ADDRESS> support?

Do you know if we change kafka(server) <IP_ADDRESS> log format to 0.11.0 ruby-kafka works?

Thanks!

I can't speak to 1, but as to 2.:
ruby-kafka does work fine with <IP_ADDRESS> and <IP_ADDRESS>, barring the considerations in kafka's 0.11 upgrade guide: http://kafka.apache.org/documentation.html#upgrade_1100_notable

@marcosArruda @tcrayford work with 0.11 here as well - at least in mine scope.

@marcosArruda I plan to add 0.10 support in the near term – this will provide message timestamp support. It will take a while before 0.11 features will be supported, but ruby-kafka should continue to work with 0.11 brokers.


refactor!: deprecate proxyWithHistory

Related Issues or Discussions

https://github.com/pmndrs/valtio/discussions/838
https://github.com/valtiojs/valtio-history

Summary
Move proxyWithHistory to the valtio-history package
This includes an api change for the utility function.
The proxyWithHistory utility within valtio/utils is now marked as deprecated.
BREAKING CHANGE:
see valtio-history for change notes and migration guide

How about adding console warning to force migrating?
https://github.com/pmndrs/valtio/blob/58f17ba0113a0dd080f69e6ac1f323cd0ba5886a/src/vanilla/utils/proxyWithComputed.ts#L23-L27

updated


Use file module to remove /root/.auth_ref.json

Otherwise the upgrade.sh script looks as if it fails and causes
confusion.
Addresses #369
(cherry picked from commit 5ea9f3a2fa214dba954badc3d4bb854ccdd483d6)

:+1:

:+1: LGTM


Make (containers with) networks reusable

I am loving the reusable containers. They can speed up development so much when repeating individual tests locally or when tests are run in several JVMs successively in the CI.
Currently, I am working with containers that are additionally connected through a network. These cannot be reused since the name of the network will be a random UUID each time. The hash of the containers to be reused is based on the create container command. This includes the network. Hence the hash chances each time and a reusable container cannot be found if a network is used.
I guess an easy solution would be to make the name of the network customizable. I can imagine weird effects when a user doesn't know the exact consequences, however. A more robust solution would be copy the reuse mechanism from containers using a name prefix for the network to make sure that one can have multiple networks which are created with identical settings.
What do you think? I would like to work on this, if it matches the direction of the project.

Thanks stale bot. There is already a PR which at least prevents erroneously reusing containers with Networks.
I was hoping for some discussion on the matter itself :)

Allowing reuse of connected containers would be really great. As a workaround I now use the Docker client to check if the network already exists and then use Java reflection to modify the NetworkImpl object. https://github.com/testcontainers/testcontainers-java/pull/3084#issuecomment-776607920 mentions that "there are options to preserve the network IDs, which makes the reuse work". Can someone elaborate on those options? I assume they are better than my hack.

@knutwannheden there is no need to use Reflection btw, just implement Network yourself.
We plan to work on improving the reusable mode eventually, but it requires some major changes, as compared to the current "alpha" version.

Thanks for the tip. I guess I have grown too used to always declaring everything final 😄
I was a bit surprised that the containers declared for reuse always get stopped through the JUnit 5 lifecycle hooks of the @Container annotation. Is there also some workaround for that?

I was a bit surprised that the containers declared for reuse always get stopped through the JUnit 5 lifecycle hooks of the @Container annotation. Is there also some workaround for that?

Would it possibly make sense with something like @Container(reuse = true) to indicate that a container should not be stopped at the end of the test scope and thus be available for reuse by another matching @Container annotation in another test?

@knutwannheden the problem with this approach is that the behaviour will differ between reuse and regular mode (as it is per-environment)
It is recommended to use the manual lifecycle control:
https://www.testcontainers.org/test_framework_integration/manual_lifecycle_control/
You should really think about the reusable containers as a next step in the "Container per test (@Rule) -> per class (@ClassRule) -> per JVM (singleton)" chain

Makes sense. Thanks for the explanation.

Hi @knutwannheden, if you could share your hack or at least what you are planning to do, it would be great !!
I am also really interested by the ability to reuse containers that share the same network.

@loic-seguin What I did was to use Java reflection to create a Network object and then set its name, id, and initialized fields. I set the name field, since I also use the name to find any corresponding network to reuse, if it already exists. But that could of course also be done using the id or some label:
    private Network createNetwork(String networkName) {
        Network network = Network.newNetwork();
        try {
            Field nameField = Network.NetworkImpl.class.getDeclaredField("name");
            nameField.setAccessible(true);
            nameField.set(network, networkName);
            List<com.github.dockerjava.api.model.Network> networks =
                    DockerClientFactory.instance().client().listNetworksCmd().withNameFilter(networkName).exec();
            if (!networks.isEmpty()) {
                Field idField = Network.NetworkImpl.class.getDeclaredField("id");
                idField.setAccessible(true);
                idField.set(network, networks.get(0).getId());
                Field initializedField = Network.NetworkImpl.class.getDeclaredField("initialized");
                initializedField.setAccessible(true);
                ((AtomicBoolean) initializedField.get(network)).set(true);
            }
            return network;
        } catch (NoSuchFieldException | IllegalAccessException e) {
            throw new RuntimeException(e);
        }
    }

Also, as discussed, creating a custom Network subclass would probably be more appropriate.

@knutwannheden  : I have subclass Network instead and did the job you did but it is not enough apparently. I had a look in the code and when there is a network inside of the command, the code is setting Random Networks aliases in the method applyConfiguration that is called in the method 'tryStart'.... Then the hash that is calculated is always different either you are reusing the same network or not.
Then a new container is recreated on the same network of course but this is not why I wanted.
I wanted that no new container is recreated even if we are using withNetwork(myNetwork).withReuse(true).
Maybe I misunderstood the point.

+1 For allowing a reuse of connected containers

Please refrain from spamming issues with "+1" comments. this won't expedite the implementation and it just adds noise for the maintainers.

I had a look in the code and when there is a network inside of the command, the code is setting Random Networks aliases in the method applyConfiguration that is called in the method 'tryStart'.... Then the hash that is calculated is always different either you are reusing the same network or not.
@loic-seguin I believe this is the code you are referring to?

public class GenericContainer<SELF extends GenericContainer<SELF>>
...
    private List<String> networkAliases = new ArrayList<>(Arrays.asList("tc-" + Base58.randomString(8)));

Could this have been used to avoid what you're seeing?
    // For the container to be reused
    container.withCreateContainerCmdModifier(cmd -> cmd.withAliases(alias));

since:
    public CreateContainerCmd withAliases(List<String> aliases) {
        Preconditions.checkNotNull(aliases, "aliases was not specified");
        this.aliases = aliases; // Note that this is not an append, unlike `container.withAliases`
        return this;
    }

@Tillerino Thanks for sharing your solution.
I'll add my 2 cents: I had to upgrade testcontainers dependency to 1.18.2 as in the version I used previously (1.16.3) the DockerClientFactory.DEFAULT_LABELS included a randomly generated UUID which made the filter "network.getLabels().equals(DockerClientFactory.DEFAULT_LABELS)" fail

Duplicate #7335


refactor: move unixfs out of the iroh-resolver package

We need to separate out the unixfs definition, unixfs_builder,  and hamt work from the rest of the iroh-resolver code.
This is a bit hairy as there is some cross-contamination of dependencies (iroh-resolver::resolver depends on some iroh-resolver::unixfs bits, and vice versa)

That would be great, especially if that is reusable for native ipfs:// and ipns:// protocol handlers in browsers.


[Merge] DICER1 syndrome

MONDO:0017288
DICER1 syndrome
A rare, autosomal dominant inherited syndrome caused by mutations in the DICER1 gene. People with this syndrome are at an increased risk of developing pleuropulmonary blastoma, cystic nephroma, Sertoli-Leydig cell tumor of the ovary, and multinodular goiter.
MONDO:0100216
DICER1-related tumor predisposition
Pathogenic germline variation in DICER1 confers an autosomal dominant predisposition to tumor formation at multiple primary sites, including pleuropulmonary blastoma, pulmonary cysts, thyroid gland neoplasia, ovarian tumors, and cystic nephroma. Other syndromic features such as macrocephaly have been described.
ClinGen request, emailed with Sheng-An
related to #5779

note- this term should not be in the inherited disease susceptibility branch


Cancellation token support for async methods

Hi,
we would like to add cancellation tokens support for async methods.
I prepared PR (see patch in attachment). It also includes update from obsolete WebRequest to HttpClient
(please rename from txt -> patch)
cancellation_token_support_for_async_methods.txt
.

Hi @alex-bortnik - we just closed an issue yesterday about this, and we provided an option for users to configure timeouts on these requests, which sounds like would be helpful to you. Can you take a look at https://github.com/statsig-io/dotnet-sdk/issues/12 and see if that works first?

Hi @jkw-statsig - yes, I saw that, my PR is based on #12 implementation. This PR allows to provide either timeout or cancellation token.
Override with cancellation token is added only to the public methods which are calling RequestDispatcher.Fetch (where actual http request is being sent).
I also switched from WebRequest to HttpClient which has better async support. Plus WebRequest is already declared obsolete: https://docs.microsoft.com/en-us/dotnet/core/compatibility/networking/6.0/webrequest-deprecated

Also, the common practice in .NET/C# is to pass cancellation token downstream from upper layer.
It is not possible to get remaining timeout value from cancellation token downstream.
Plus there could be other reasons for cancellation apart from timeout.

Got it, thanks for the context. We'll take a look into your patch

@jkw-statsig any update on this?


Linkerd Prometheus: Unable to update list of all metrics: unable to fetch metrics for query unknown response code 403

What happened?:
Prometheus adapter not able to get metrics from Linkerd Prometheus
What did you expect to happen?:
I expected the prometheus-adapter to fetch the metrics from custom Linkerd Prometheus in the Kubernetes cluster.
Please provide the prometheus-adapter config:
prometheus:
url: http://prometheus.linkerd-viz.svc
port: 9090
path: ""
rules:
default: false
custom:
- seriesQuery: 'request_total{namespace!="",pod!=""}'
resources:
template: '<<.Resource>>'
name:
matches: 'request_total'
as: "request_total"
metricsQuery: 'sum(rate(<<.Series>>{<<.LabelMatchers>>, direction="inbound", deployment!="", namespace!=""}[5m])) by ( <<.GroupBy>>)'
Prometheus-adapter logs
I0725 11:44:17.036335       1 api.go:90] GET http://prometheus.linkerd-viz.svc:9090/api/v1/series?match%5B%5D=request_total%7Bnamespace%21%3D%22%22%2Cpod%21%3D%22%22%7D&start=1690285397.035 403 Forbidden E0725 11:44:17.036384       1 provider.go:229] unable to update list of all metrics: unable to fetch metrics for query "request_total{namespace!=\"\",pod!=\"\"}": bad_response: unknown response code 403
Anything else we need to know?:
Verified the correctness of the prometheus-adapter configuration.
Inspected the prometheus-adapter logs with -v=6 around the time the issue occurred.
Validated all the manifests and resources related to prometheus-adapter deployment.
Verified the version of prometheus-adapter and prometheus.
Prometheus adapter deployed without any changes to Service account, Cluster role or Cluster role binding
Environment:
https://artifacthub.io/packages/helm/prometheus-community/prometheus-adapter
prometheus-adapter version: 0.10.0
Cloud provider or hardware configuration: AWS EKS 1.25

/assign @dgrisonnet
/triage accepted

I0725 11:44:17.036335       1 api.go:90] GET http://prometheus.linkerd-viz.svc:9090/api/v1/series?match[]=request_total{namespace!%3D""%2Cpod!%3D""}&start=1690285397.035 403 Forbidden E0725

This means that prometheus-adapter can't reach your Prometheus instance because it is unauthorized. You most likely need to configure authentication on prometheus-adapter. There are a couple of options that you can use to do that: https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/cmd/adapter/adapter.go#L136-L147

+1, I'm also getting the same error when trying to connect to Amazon Managed Service for Prometheus for querying metrics.  I am currently using a sigv4-proxy sidecar container for signing the request and a serviceAccount for assuming a role for querying metrics from the AMP Workspace.
@dgrisonnet could you explain what type of auth do we need to configure? Do we need to provide auth details to connect to AWS AMP Workspace or something else. In my limited knowledge, I thought that having an IAM Role that allows querying operations on AWS AMP through a policy is enough for this setup (using serviceAccount annotations).
unable to update list of all metrics: unable to fetch metrics for query "{__name__=\"container:memory_usage_bytes:sum\",container!=\"POD\",kubernetes_namespace!=\"\",pod!=\"\",cluster_name=\"compute\"}": bad_response: unknown response code 403

This could be issue with some network policies. At least for me setting up Linkerd auth policies resolved the 403 issue.


[UWP] Update window interface implementation

See 202.
Implemented visible as well, not sure why it wasn't before.

Merged, thanks!


Command doesn't work when run via cargo aoc but does when run via cargo-aoc

$ cargo aoc --help
error: unrecognized subcommand 'aoc'

Usage: cargo-aoc [OPTIONS] [COMMAND]

For more information, try '--help'.

Fixed in #149


Adding Racks with the same name to different groups within same site

Hi,
I am trying to add multiple racks and I was starting to name them via row#-rack# however, it seems that you cant have multiple Racks in the same site but different site groups with the same name. You can however if you are adding it to a different site altogether. Not sure if this is the intended workflow or not, or if I have to find a new naming scheme for racks in the same building just in different comms rooms or locations within the same site. E.G we have 2 different cages in 1 DC, I added each cage as a group, both in the same overall site. Do I have to configure each cage as an entire site? or should we be able to add racks with the same name to different groups within the same site.

I'm not sure of your physical layout but if your cages are simply encompassing racks that are part of the row system then those racks should follow the same numbering scheme not reset within
If the cages are off to the side you might go:
cage#-row#-rack# where cage 0 is the common floor and increment cage for your actual cages

I think the impediment to allowing non-unique rack names within a site is that the rack group effectively becomes part of the rack name. So when importing devices, for instance, we'd need to specify the rack group along with the rack. I suppose it's a trade-off between flexibility in the data model and overhead.

Yeah I see where you're coming from now. Basically in our of our facilities we have 2 cages that are at separate ends of the data hall because we purchased them at different times due to growth etc.  Each cage's set of racks are numbered the same, i.e row then rack number in the row so I figured I could use the rack groups to signify the cages. I can see how this is going to get messy in once we add all of our facilities in, the devices and racks views are almost going to be redundant without filtering 100% of the time.
I guess in this case, for sanity's sake I'll have to duplicate the cage number/name as part of the rack name for all sites going forward, at least then I can still filter by name and get an order by location thats accurate without necessarily filtering for each query.

@LordBoBCUP Out of curiosity, do you have unique facility IDs for your racks (e.g. identifiers assigned by the data center provider)?

Hi Jeremy, yeah we do but the only place I've really seen them is on the invoices etc. Not really used in the real world. We could use them in netbox and have everyone reference them, but then again, each datacentre around the world would do them different as well, so uniformity would be lost. I guess if its not a feature thats super popular, people will find a workaround (probably the duplication/overhead)

How many levels of groups can you have in netbox?
eg. Site - DC - Server room - (Cage - )Row - Rack

Site, rack group, rack, device. Each layer of organization adds a performance penalty.
#257 would add a region field to sites, but I think that's as far as we'll go.

Just to add my .02 here as I'm running into similar issues where I'm working now.
We break the datacenters into zones and within those zones the racks all the same name.
So where I would have:
R1 in Zone 1 (Zone 1 is the rack group)
R1 in Zone 2 (Zone 2 is the rack group)
I cannot have two racks named R1, so I'm relegated to using:
R101 and R201, which isn't any help and has no "meaning"
My facility ID was well becomes complicated having to use:
R1.Z1 and R1.Z2
We maintain DNS for things as such:
R#.Z#.SITE.DOMAIN.TLD
...and for future usage of Netbox features having to kitbash the names kinda suck being that we'd want to use:
Rack-Slug.RackGroup-Slug.Site-Slug.
The same issue applies to devices, namely PDU's - we do:
R#-PDU-[A-Z].Z#.SITE.DOMAIN.TLD
However I can't have mutliple R1.PDU-A (they'd exist in multiple zones) so I need to do:
R1.PDU-A.Z1 and R1.PDU-A.Z2
It's just make things a lot harder to with down the line when you'd want to just chain slugs or names together.
My .02 being uniqueness for names should be scoped to the rack group level, please =)

This has gotten worse.
I cannot have devices that are named the same between two different sites.
E.g I cannot have a "R6-PDU-A.Z1" in Site A and Site B
Just to clarify, both my sites are basically identical in naming convention, the only thing that is different is the site.
I have the same zone names, rack names and devices names, they simply have a different site ID in their hostname.
We REALLY need to relax this please.

@bellwood Device naming constraints are unrelated to this issue. Please open a new issue if you'd like to discuss that.