0.16.3 版本docker镜像无法选择 sglang 作为推理引擎

System Info / 系統信息
Driver Version: 535.171.04   CUDA Version: 12.2
Running Xinference with Docker? / 是否使用 Docker 运行 Xinfernece？

[X] docker / docker
[ ] pip install / 通过 pip install 安装
[ ] installation from source / 从源码安装

Version info / 版本信息
xinference 0.16.3 (docker image)
The command used to start Xinference / 用以启动 xinference 的命令
docker-compose.yml:
services:
  xinference:
    container_name: xinference
    image: xprobe/xinference:latest
    ports:
      - "9997:9997"
#      - target: 9997
#        published: 9997
    volumes:
       - /data/xinference:/data
    environment:
#      # add envs here. Here's an example, if you want to download model from modelscope
      - XINFERENCE_MODEL_SRC=modelscope
      - XINFERENCE_HOME=/data
      - ATTENTION_BACKEND=flashinfer
#    command: xinference-local --host <IP_ADDRESS> --port 9997
    command: sh /data/config/init.sh
    shm_size: 128gb
    deploy:
      resources:
        reservations:
          devices:
            - capabilities: [gpu]
              driver: nvidia
              count: all

init.sh :
xinference launch --model-name qwen2.5-instruct --model-uid Qwen2.5-72B-INT4-Instruct-awq-SGLANG --model-engine sglang --size-in-billions 72 --model-format awq --n-gpu 1 --model_path /data/modelscope/hub/qwen/Qwen2___5-72B-Instruct-AWQ --enable_torch_compile True --disable_cuda_graph True --mem_fraction_static 0.88 --kv_cache_dtype fp8_e5m2 &

Reproduction / 复现过程
xinference  | 2024-11-10 10:43:13,558 transformers.models.auto.image_processing_auto 592 INFO     Could not locate the image processor configuration file, will try to use the model config instead.
xinference  | Could not locate the image processor configuration file, will try to use the model config instead.
xinference  | INFO 11-10 10:43:13 awq_marlin.py:89] The model is convertible to awq_marlin during runtime. Using awq_marlin kernel.
xinference  | INFO 11-10 10:43:13 config.py:648] Using fp8 data type to store kv cache. It reduces the GPU memory footprint and boosts the performance. Meanwhile, it may cause accuracy drop without a proper scaling factor
xinference  | 2024-11-10 10:43:13,566 xinference.api.restful_api 7 ERROR    [address=<IP_ADDRESS>:10179, pid=165] Model qwen2.5-instruct cannot be run on engine sglang.
xinference  | Traceback (most recent call last):
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/api/restful_api.py", line 987, in launch_model
xinference  |     model_uid = await (await self._get_supervisor_ref()).launch_builtin_model(
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/context.py", line 231, in send
xinference  |     return self._process_result_message(result)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/context.py", line 102, in _process_result_message
xinference  |     raise message.as_instanceof_cause()
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/pool.py", line 659, in send
xinference  |     result = await self._run_coro(message.message_id, coro)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/pool.py", line 370, in _run_coro
xinference  |     return await coro
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/api.py", line 384, in __on_receive__
xinference  |     return await super().__on_receive__(message)  # type: ignore
xinference  |   File "xoscar/core.pyx", line 558, in __on_receive__
xinference  |     raise ex
xinference  |   File "xoscar/core.pyx", line 520, in xoscar.core._BaseActor.__on_receive__
xinference  |     async with self._lock:
xinference  |   File "xoscar/core.pyx", line 521, in xoscar.core._BaseActor.__on_receive__
xinference  |     with debug_async_timeout('actor_lock_timeout',
xinference  |   File "xoscar/core.pyx", line 526, in xoscar.core._BaseActor.__on_receive__
xinference  |     result = await result
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/core/supervisor.py", line 1040, in launch_builtin_model
xinference  |     await _launch_model()
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/core/supervisor.py", line 1004, in _launch_model
xinference  |     await _launch_one_model(rep_model_uid)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/core/supervisor.py", line 983, in _launch_one_model
xinference  |     await worker_ref.launch_builtin_model(
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/context.py", line 231, in send
xinference  |     return self._process_result_message(result)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/context.py", line 102, in _process_result_message
xinference  |     raise message.as_instanceof_cause()
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/pool.py", line 659, in send
xinference  |     result = await self._run_coro(message.message_id, coro)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/backends/pool.py", line 370, in _run_coro
xinference  |     return await coro
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xoscar/api.py", line 384, in __on_receive__
xinference  |     return await super().__on_receive__(message)  # type: ignore
xinference  |   File "xoscar/core.pyx", line 558, in __on_receive__
xinference  |     raise ex
xinference  |   File "xoscar/core.pyx", line 520, in xoscar.core._BaseActor.__on_receive__
xinference  |     async with self._lock:
xinference  |   File "xoscar/core.pyx", line 521, in xoscar.core._BaseActor.__on_receive__
xinference  |     with debug_async_timeout('actor_lock_timeout',
xinference  |   File "xoscar/core.pyx", line 526, in xoscar.core._BaseActor.__on_receive__
xinference  |     result = await result
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/core/utils.py", line 78, in wrapped
xinference  |     ret = await func(*args, **kwargs)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/core/worker.py", line 869, in launch_builtin_model
xinference  |     model, model_description = await asyncio.to_thread(
xinference  |   File "/usr/lib/python3.10/asyncio/threads.py", line 25, in to_thread
xinference  |     return await loop.run_in_executor(None, func_call)
xinference  |   File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
xinference  |     result = self.fn(*self.args, **self.kwargs)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/model/core.py", line 73, in create_model_instance
xinference  |     return create_llm_model_instance(
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/model/llm/core.py", line 216, in create_llm_model_instance
xinference  |     llm_cls = check_engine_by_spec_parameters(
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/model/llm/llm_family.py", line 1136, in check_engine_by_spec_parameters
xinference  |     raise ValueError(f"Model {model_name} cannot be run on engine {model_engine}.")
xinference  | ValueError: [address=<IP_ADDRESS>:10179, pid=165] Model qwen2.5-instruct cannot be run on engine sglang.
xinference  | Traceback (most recent call last):
xinference  |   File "/usr/local/bin/xinference", line 8, in <module>
xinference  |     sys.exit(cli())
xinference  |   File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1157, in __call__
xinference  |     return self.main(*args, **kwargs)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1078, in main
xinference  |     rv = self.invoke(ctx)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1688, in invoke
xinference  |     return _process_result(sub_ctx.command.invoke(sub_ctx))
xinference  |   File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1434, in invoke
xinference  |     return ctx.invoke(self.callback, **ctx.params)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 783, in invoke
xinference  |     return __callback(*args, **kwargs)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/click/decorators.py", line 33, in new_func
xinference  |     return f(get_current_context(), *args, **kwargs)
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/deploy/cmdline.py", line 906, in model_launch
xinference  |     model_uid = client.launch_model(
xinference  |   File "/usr/local/lib/python3.10/dist-packages/xinference/client/restful/restful_client.py", line 959, in launch_model
xinference  |     raise RuntimeError(
xinference  | RuntimeError: Failed to launch model, detail: [address=<IP_ADDRESS>:10179, pid=165] Model qwen2.5-instruct cannot be run on engine sglang.

Expected behavior / 期待表现
0.16.3 版本docker镜像  中丢失 model engine sglang 引擎参数选项（cli & webui）

同样的问题，之前的版本有这个问题吗

我们看下

V1.0.0 也没有

We will try to address this issue.

V1.0.0 也没有

me too


:bug: Failed building debian images

          debian failed to build with provider-kairos: https://github.com/kairos-io/provider-kairos/actions/runs/4276026019/jobs/7444575360

We might need to tag a 1.6.1 on the provider repository
Originally posted by @mudler in https://github.com/kairos-io/kairos/issues/782#issuecomment-1445928162

https://github.com/kairos-io/provider-kairos/actions/runs/4276026019/jobs/7444575360


Add contributors and maintainers files

All journey repos needs files to explain to users how to contribute.
See guidelines here: https://github.ibm.com/developer-journeys/journey-docs/blob/master/other_markdown_files.md
See example here: https://github.com/IBM/pixiedust-facebook-analysis

Added.


TypeError: history.isActive is not a function

This code tries to call history.isActive
https://github.com/rackt/react-router/blob/master/modules/Link.js#L103
In history module there is no method isActive
https://github.com/rackt/history/

Can you give more details?
Also have a look at the isActive docs
If you are using ES6 classes you should check this part

I'm instantiating history with history/lib/createBrowserHistory and then passing it into react-router.
The history object created has only these methods and there is no "isActive" method (because history module has no)
 Object {}createHref: createHref(path)createKey: createKey()createPath: createPath(path)go: go(n)goBack: goBack()goForward: goForward()listen: listen(listener)pushState: pushState(state, path)registerTransitionHook: registerTransitionHook(hook)replaceState: replaceState(state, path)setState: setState(state)transitionTo: transitionTo(nextLocation)unregisterTransitionHook: unregisterTransitionHook(hook)

Am I doing it right?

can you post the part where you calling isActive? I'm not sure if I understand what you mean

I'm not calling isActive, the Link class does:
https://github.com/rackt/react-router/blob/master/modules/Link.js#L103

this is how you would the browser history in the router:
import React from 'react';
import createBrowserHistory from 'history/lib/createBrowserHistory';
import {Router, Route, IndexRoute} from 'react-router';
import App from '../components/App';
import Home from '../components/Home';
import About from '../components/About';
import Features from '../components/Features';

React.render(
  <Router history={createBrowserHistory()}>
    <Route path='/' component={App}>
      <IndexRoute component={Home} />
      <Route path='about' component={About} />
      <Route path='features' component={Features} />
    </Route>
  </Router>,
  document.getElementById('app')
);

I don't get any errors with that. Let me know how I can reproduce your error and I'll try to help

@knowbody okay, thanks for the help.
This currently surpasses my understanding of react-router and I'll figure that out in the following weeks.
For now, I'm closing the issue - seems that my code is doing something that's not intended.

@knowbody oh, by the way, your advice fixed my issue: seems that I didn't pass history as a prop to Router.
don't know why this.context.history wasn't null then, but that's another story, unrelated.

I'm here to help, feel free to post some code and we will try to solve it

@knowbody Thanks


FastAdapter with 2 different itemadapter

About this issue

Briefly describe the issue
How can the issue be reproduced / sample code

Details

[ ] Used library version
[ ] Used support library version
[ ] Used gradle build tools version
[ ] Used tooling / Android Studio version
[ ] Other used libraries, potential conflicting libraries

Checklist

[ ] Searched for similar issues
[ ] Checked out the sample application
[ ] Read the README
[ ] Checked out the CHANGELOG
[ ] Checked out the MIGRATION GUIDE

The FastAdapter has to define the parent type, then you can have child item adapters.
the sample showcases this :)

The FastAdapter has to define the parent type, then you can have child item adapters.
the sample showcases this :)

Yeah, I saw that, in fact I set FastAdapter type to IItem but same error happened.
Btw, thank for your reply, very very fast. :)

@Raffaa what is the error you see?

When the adapter try to render Item2 ViewHolder couse the Exception:  Item2 cannot be cast to Item1. The exception is fired at onBindViewHolder method implementation inside StickyHeader implementation.
Maybe, later, I can create and share you a test repository to help undestand the error.

Here the repo -> https://github.com/Raffaa/TestFastAdapter2
Just build, and then scroll down in the app

The issue is that you are not using unique type ids. The type is used by the RecyclerView to tell which items is supposed to be used and thus has to be unique to ensure the correct things are used :).
The best pattern is to specify a integer int resource per item which you use per item.
https://github.com/mikepenz/FastAdapter/blob/develop/app/src/main/java/com/mikepenz/fastadapter/app/items/SimpleImageItem.kt#L33

Ah, missed that.
Thank you, problem solved :)


Bootstrap to start registry loading early

Description:
Kick off loading the device / area / entity registries early in the bootstrap process to allow disk IO to occur while waiting for other stuff to load.
Also cleans up registry lookup code to avoid overhead in creating tasks.
@balloob we were talking about this in discord a little while ago.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

How's this version:

Registry loading task gets kicked off early, but not awaited.
No async_block_till_done at the end of stage 0, since it's not required and would block waiting for registries to load (which is what we're trying to avoid).
Registry loading awaited after stage 1. advantage here is any exceptions get thrown, downside is that it's less lazy load, since the loading would otherwise be awaited at the point that some component calls it.
Use gather instead of creating tasks, that way any exceptions get picked up. this is the main change, easy enough to revert if you want. Alternative would be asyncio.wait for stage 3 and just discard any exceptions.

So the only changes to the initial code are points 2 and 4. If we drop 2 then we might as well roll it all back.
Profiling it is going to depend very sensitively on the speed of disk access, it will very much depend on if the file in in memory cache / flash ram / hard drive, so it's going to be difficult to prove for all cases.

why you want to load registry before logger?
Logger should be the first loaded even before registry in my opinion.

Rolled back to minimal change.

What we were talking about on Discord was to actually set the registries as properties on hass. That way we avoid an await and can access it via hass.entity_registry.X.

OK cool. It's difficult to store the properties directly on hass. You have three choices:

Load all the registries, store on hass, and then continue with phase one (slow)
Kick off loading the registries, kick off stage 1, if the registries are accessed in stage one you get an null object exception, after stage 1 is complete, set the properties. You'd still have to await at the end of stage 1 for the registries to be ready before you can start stage two (faster but still potentially slow, plus prone to causing exceptions in stage 1)
Kick off registry loading, set properties to uninitialised registries, and start stage one and accept that if stage one accesses the registries there's a race condition there. (yeh bad).

What's here has the advantage that there's no race conditions possible, registry loading is asynchronous, and everything is safe with no race conditions. The only downside is needing the await when getting the registries. There's no problem however with a component storing the registry somewhere privately once it's got a reference to it however, and you can't get an unloaded registry with the current code or cause a race condition.

How slow we are talking here? We just deserialize 3 JSON file, don't we? How slow it could be comparing load one Python module and all its dependency?

@awarecan  Depends on how slow disk access is, if it's a spinning disk or a network disk it could take some time. We might as well do it asynchronously since that means all the network waits and disk accesses in stage 1 and 2 happen at once, and there's no real overhead in doing this. The serialisation isn't the slow part, it's getting it off the disk.

Yeah this is hard to do right. I think the current solution is a great step forward.


websocket should stream rather than copy whole message

Issue
Gorouter is slow when handling large payloads in websocket messages
Context
[provide more detailed introduction]
Steps to Reproduce
Send a large (20-30MB) payload in a websocket message.
Expected result
Message should be streamed to the app with minimal work on the router.
Current result
Long delay between sending the message and it arriving at the application. Timeouts occurring.
Possible Fix
[not obligatory, but suggest fixes or reasons for the bug]
name of issue Output Results
[if relevant, include a screenshot]

@TimMurnaghan
Until you posted this, I thought GoRouter did stream messages on websockets. The relevant bit is a single line of code for us https://github.com/cloudfoundry/gorouter/blob/8128246bd730c55034bbb0fb855f20b7d0275a51/proxy/handler/request_handler.go#L234
I can look into this a bit more, but I'm not sure if we have any feasible options to improve the streaming. Do you have any suggestions yourself? @flawedmatrix do you think we can use io.CopyBuffer to force things to chunk without taking a big performance hit?

@charleshansen Sorry for slow response - not monitoring here. And no - I suspect that the answer is some bigger refactoring/new apis  down in the go runtime. It probably should be a single line from the router's point of view.
On the question of CopyBuffer - the router's performance is actually awful on large messages generally (same copying behaviour on http as well). You're relying on go to do the right thing but in the shared environment of the router memory behaviour is critical - so I would actually expect a huge performance boost from streaming properly.
Sadly, it's a dealbreaker for me so I'm actually giving up on CloudFoundry completely as I think that this (and other issues like no control over timeouts) make the gorouter too much of a non-controllable risk and that it's not yet a viable option for production.

If too much off topic, please ignore..
@TimMurnaghan at the CF Summit in Basel a few guys hacked together a replacement for the router. The usecase was actually using https://letsencrypt.org/ on the fly for apps.. but what they did was replace the router with https://traefik.io/ and use nats route announcements to config traefic on the fly.. I do not see a reason why you would not be able to replace the routers if you wanted to..

@nouseforaname you may be interested in this design doc about replacing Gorouter with Envoy.  The effort is in-flight.  You can track our progress towards the first milestone via this "epic" label in Pivotal Tracker.

We'll don't plan on any major refactors in Gorouter, as our long term strategy is to replace it with Envoy.   We'll make a note to explore Envoy support for streaming large payloads.


https://datatracker.ietf.org/doc/rfc1101/email/

Description
https://datatracker.ietf.org/doc/rfc1101/email/
Code of Conduct

[x] I agree to follow the IETF's Code of Conduct

Closing as unactionable. If you see something that needs to change, add a new comment.


Add something to enable remote pair programming

https://atom.io/packages/atom-pair
or
https://atom.io/packages/motepair
maybe
but probably not: https://atom.io/packages/pair-programming

Seems to be a duplicate of #29


[v2.3.0-Beta2] Popup background has an odd black shadow appearing on the top left and top right corners without any reason for it to be there

Describe the bug
When opened, on any device, popups draw a weird semi-shadow on the top left and top right corners/shoulders of the popup.
This happens on any device, any browser, any theme, with or without custom backgrounds. I am aware that each popup draws a bit of a shadow behind it to make it stand out a bit more from the surroundings, but it looks like the shadow is somehow encroaching on the corners.
It looks like the popup is trying to blurr the background, but there is no reason for the two corners to have these shadows.
To Reproduce
Steps to reproduce the behavior:

Go to any popup on any device on any browser
Observe the top left and top right corners

Expected behavior
No shadow on the corners.
Screenshots:

YAML
Available if requested.
Informations (please complete the following information):

OS: ANY
Browser/App: ANY
Bubble Card version: v2.3.0-Beta2
Home Assistant version: inclined to say ANY, but here's my set:
Core 2024.10.4
Supervisor 2024.10.3
Operating System 13.2
Frontend 20241002.4

Additional context
Keep up the great work, bubble card rocks :D

Hi and thank you for your feedback, indeed I've noticed it as well. This is because I had to move the blurred background to another container to fix a dropdown issue. But this shouldn't be too difficult to fix.

This issue was fixed in v2.3.0-beta.4, I'm closing this 🙂
Thanks again for the feedback!


Reduce number of steps required to set everything up

Reduce the number of pre-requisite steps required to getting started by doing the following:

[x] Auto detect node-red installation folder #7
[x] Enable node-red project feature automatically #8

Included in releas: 0.2.0


Menu implementation

Implementing a menu based system for users to navigate the program.

wrong repo :woozy_face:


unrecognized argument --max-lr

I tried to run the training command from the readme, but I get the following error:
train.py: error: unrecognized arguments: --max-lr 1.0

I'm very sorry about that, thanks for pointing this out! I've updated the README and training should now work. Please respond here if it doesn't.

Thanks for the fix!
Just one thing: the text says 512 tokens but the new command says --tokens-per-sample 1024. If I want to use 512, can I keep the other settings as they are?

Yup that was a mistake, fixed that now too. Thanks!


Github link for babel-plugin-react-display-name in README leads to 404

It appears the project no longer lives at https://github.com/babel-plugins/babel-plugin-react-display-name even thought the npm page is still there https://www.npmjs.com/package/babel-plugin-react-display-name.
I believe this would be the "official" version of the package now but wanted to ask before submitting a PR: https://github.com/gajus/babel-plugin-react-display-name

AFAIK the official page should be inside babel/babel monorepo.


Topic/Partition related admin functions return Future[None]

Initial Checks

[X] I confirm that I'm using Types-Confluent-Kafka

Description
Thank you for the awesome work!
https://github.com/benbenbang/types-confluent-kafka/blob/c9f9e1843fc66fc09f18d77de1eb51c9fa0b15b4/confluent_kafka-stubs/admin/__init__.pyi#L63
https://github.com/confluentinc/confluent-kafka-python/blob/dc3114afd15d56a828bcfb48f1601c4c3f076d78/src/confluent_kafka/admin/__init__.py#L568-L569
https://github.com/benbenbang/types-confluent-kafka/blob/c9f9e1843fc66fc09f18d77de1eb51c9fa0b15b4/confluent_kafka-stubs/admin/__init__.pyi#L66
https://github.com/confluentinc/confluent-kafka-python/blob/dc3114afd15d56a828bcfb48f1601c4c3f076d78/src/confluent_kafka/admin/__init__.py#L600-L601
https://github.com/benbenbang/types-confluent-kafka/blob/c9f9e1843fc66fc09f18d77de1eb51c9fa0b15b4/confluent_kafka-stubs/admin/__init__.pyi#L75
https://github.com/confluentinc/confluent-kafka-python/blob/dc3114afd15d56a828bcfb48f1601c4c3f076d78/src/confluent_kafka/admin/__init__.py#L641-L642
Should return Future[None]
Also
https://github.com/benbenbang/types-confluent-kafka/blob/c9f9e1843fc66fc09f18d77de1eb51c9fa0b15b4/confluent_kafka-stubs/admin/__init__.pyi#L81
will just return None. Not sure how to annotate, that the future might throw a KafkaException
https://github.com/confluentinc/confluent-kafka-python/blob/dc3114afd15d56a828bcfb48f1601c4c3f076d78/src/confluent_kafka/admin/__init__.py#L719-L720
Example Code
.

Python, verion of Types-confluent-kafka. verion of Confluent-kafka-python, your applications settings & OS Version
.

Affected Components

[ ] confluent-kafka-python and librdkafka version (confluent_kafka.version() and confluent_kafka.libversion())
[ ] Apache Kafka broker version
[ ] Client configuration: {...} is provided
[ ] Operating system is provided
[ ] Provide IDE screenshot if it's possible

Hello @ronchler
Thanks for the report. According to PEP 484., which is the guiding document for typing hints in Python, while it does not provide specific details on handling exceptions in the Future, it outlines how to use type hints and the typing module to annotate function signatures. You can read more about PEP 484.
here's the summary of handling Exceptions:

No syntax for listing explicitly raised exceptions is proposed. Currently, the only known use case for this feature is documentational, in which case the recommendation is to put this information in a docstring.

:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[5.7][SourceKit] Guard DependencyStamps with a lock

Explanation: We might run into situations where matchesSourceState reads DependencyStamps while they are being written in buildASTUnit, causing a crash. Guard DependencyStamps by a mutex to avoid this problem. We don’t need to provide any ordering guarantees about whether DependencyStamps have been computed in are accessed because we already assume that the dependencies shouldn't change (much) in the time between an ASTBuildOperation is created and until it produced an AST. I made sure that the mutex can’t introduce deadlocks.
Scope: Non code-completion SourceKit requests
Risk: Low
Issue: rdar://92748564
Reviewer: @bnbarham on https://github.com/apple/swift/pull/58681

@swift-ci Please test


GLFWError: (65537) b'The GLFW library is not initialized'

python demo_visual_servo.py
INFO:root:Activated agents: ['arm0']
Traceback (most recent call last):
File "/home/hjx/hjx_file/mujoco_file/robopal/robopal/demos/demo_visual_servo.py", line 125, in
env.step()
File "/home/hjx/hjx_file/mujoco_file/robopal/robopal/demos/demo_visual_servo.py", line 70, in step
cam2aruco_r, cam2aruco_p, detected_already = self.aruco_detection(marker_size)
File "/home/hjx/hjx_file/mujoco_file/robopal/robopal/demos/demo_visual_servo.py", line 42, in aruco_detection
rvec, tvec, _ = cv2.aruco.estimatePoseSingleMarkers(
AttributeError: module 'cv2.aruco' has no attribute 'estimatePoseSingleMarkers'
/home/hjx/anaconda3/envs/hjx/lib/python3.9/site-packages/glfw/init.py:914: GLFWError: (65537) b'The GLFW library is not initialized'

Upgrade to the latest opencv and opencv-contrib version

Thanks!
The problem was resolved using the pip installation:
pip install opencv-python
pip install opencv-contrib-python


Feedback for .NET API browser / Microsoft.Xrm.Sdk?

Where can I leave feedback for the documentation for Microsoft.Xrm.Sdk?
The remarks for this method is not entirely correct. Instead of returning null, it returns default. For the example with EntityReference, null is correct. For DateTime it is not null, but DateTime.MinValue.
https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.entity.getattributevalue?view=dataverse-sdk-latest#remarks

@darshSWL Thanks for pointing that out. I will update the page.


Hudi Clustering not working

Describe the problem you faced
Hudi Clustering not working.
I'm using Hudi Delta streamer in continuous mode with Kafka source.
we have 120 partitions in the Kafka topic and the ingestion rate is (200k) RPM
we are using the BULK INSERT mode to ingest data into target location .
But we could see that lot of small files were being generated. In Order to overcome this small file problem we are using the Hudi Clustering ,still we could see files were not being merged.
Configuration for the JOB is
#base properties
hoodie.insert.shuffle.parallelism=50
hoodie.bulkinsert.shuffle.parallelism=200
hoodie.embed.timeline.server=true
hoodie.filesystem.view.type=EMBEDDED_KV_STORE
hoodie.compact.inline=false
hoodie.bulkinsert.sort.mode=none
#cleaner properties
hoodie.cleaner.policy=KEEP_LATEST_FILE_VERSIONS
hoodie.cleaner.fileversions.retained=60
hoodie.clean.async=true
#archival
hoodie.keep.min.commits=12
hoodie.keep.max.commits=15
#datasource properties
hoodie.deltastreamer.schemaprovider.registry.url=
hoodie.datasource.write.recordkey.field=
hoodie.deltastreamer.source.kafka.topic=
hoodie.datasource.write.keygenerator.class=org.apache.hudi.keygen.CustomKeyGenerator
hoodie.datasource.write.partitionpath.field=timestamp:TIMESTAMP
hoodie.deltastreamer.kafka.source.maxEvents=600000000
hoodie.deltastreamer.keygen.timebased.timestamp.type=EPOCHMILLISECONDS
hoodie.deltastreamer.keygen.timebased.input.timezone=UTC
hoodie.deltastreamer.keygen.timebased.output.timezone=UTC
hoodie.deltastreamer.keygen.timebased.output.dateformat='dt='yyyy-MM-dd
hoodie.clustering.async.enabled=true
hoodie.clustering.plan.strategy.target.file.max.bytes=3000000000
hoodie.clustering.plan.strategy.small.file.limit=200000001
hoodie.clustering.async.max.commits=1
hoodie.clustering.plan.strategy.max.num.groups=10
#kafka props
bootstrap.servers=
schema.registry.url=
Deltastreamer Class Arguments:
- "--table-type"
- "COPY_ON_WRITE"
- "--props"
- "/opt/spark/hudi/config/source.properties"
- "--schemaprovider-class"
- "org.apache.hudi.utilities.schema.SchemaRegistryProvider"
- "--source-class"
- "org.apache.hudi.utilities.sources.JsonKafkaSource"
- "--target-base-path"
- ""
- "--target-table"
- ""
- "--op"
- "BULK_INSERT"
- "--source-ordering-field"
- "timestamp"
- "--continuous"
- "--min-sync-interval-seconds"
- "60"

Hudi version :0.9

Spark version :2.4.4

Storage (HDFS/S3/GCS..) :BLOB

Running on Docker? (yes/no) :Kubernetes

Stacktrace
22/06/09 22:11:07 INFO ClusteringUtils: Found 0 files in pending clustering operations
22/06/09 22:11:07 INFO RocksDbBasedFileSystemView: Resetting file groups in pending clustering to ROCKSDB based file-system view at /tmp/hoodie_timeline_rocksdb, Total file-groups=0```

can you try setting hoodie.clustering.plan.strategy.max.bytes.per.group" as a multiple of hoodie.clustering.plan.strategy.target.file.max.bytes`.

Can you leave the small file and target file config to default value and also for hoodie.clustering.async.max.commits to default value and see whats happening. This time, can you enable debug logs when you restart your pipeline. We might get more insights.

may be this could be the issue. can you try adding this to spark-submit command
--hoodie-conf hoodie.clustering.async.enabled=true

may be this could be the issue. can you try adding this to spark-submit command
--hoodie-conf hoodie.clustering.async.enabled=true

Have tried this option still no luck

I think there are no eligible filegroups for clustering. More than the number of records, clustering is a function of file size. What's the avg file size for the data files w/o clustering. We need to set the clustering configs accordingly? Did you try out the suggestion by Siva i.e. to try with default configs?

Hi @codope ,
I have first setup the clustering with default configuration only. since it's not working have used these options.
hoodie.clustering.async.enabled=true
hoodie.clustering.plan.strategy.target.file.max.bytes=3000000000
hoodie.clustering.plan.strategy.small.file.limit=200000001
hoodie.clustering.async.max.commits=1
hoodie.clustering.plan.strategy.max.num.groups=10
oodie.clustering.plan.strategy.max.bytes.per.group=9000000000

@ksrihari93 : are you still stuck at this issue.

if you can provide us w/ debug logs, would be of great help. we are kind of running out of ideas as to why clustering is not getting triggered.

@ksrihari93 : gentle ping.

Hi Team,
Sorry for the late reply.
Now it's working fine. we can close this issue.

thanks!. curious to know what was missing or how did you resolve.

Also interested by the way you solve ! I'm stuck with this problem on 0.10.1 version integrated with AWS Glue


Question : Basic way to get message via Uid

Please be aware that these issues will be closed if inactive for more then 14 days :)
Please be aware that these issues will be closed if inactive for more then 14 days :)
Good Evening,
I have trouble getting message via Uid using getMessage
$oClient = Client::account('default'); // defined in config/imap.php
        $oClient->connect();

        // get all unseen messages from folder INBOX
        $aMessage = $oClient->getFolders();

        foreach ($aMessage as $oMessage) {
            // do something with the message
            $message = $oMessage->query()->getMessage(7);
        }

instead getting message Uid 7 its display Uid 13 instead
PS: a bit example will help me alot
Thanks you

Im sorry for opening 2 same issue


E-mails are not sorted by date

RainLoop version, browser, OS:
Latest version, on all Browsers
Expected behavior and actual behavior:
The e-mails should be sorted by received date, but are actually sorted by "changed" date.
Logs or screenshots:

I know. There are many threads to this issue, but all of them inconclusive. This is a major issue. I have more than 200 users with totally messed up e-mails with no actual sorting. This leads to a terrible user experience.
The e-mail server is Yandex, which doesn't support IMAP Sort (like most, I think).
Can we do anything to fix that?

RainLoop does not store any email messages at all, it meant that it show messages in IMAP response order.
So, if Yandex cannot sort messages, RainLoop will not fix this problem.
But, you may change next setting:
[labs]
date_from_headers = Off
It takes (and show) date from mime DATE header.

But is it needed to store anything? Can't we just "intercept" the response and handle the sorting ourselves? I understand other webmail clients can sort this in real time?
I'm not even asking you to do that. Only, perhaps, guide us in doing it.


feat: enhance client otel tracing and linking to scheduler &  manager

Description

Introduce a grpc_tracing interceptor to inject tracing span context into the global propagator.
Related Issue

Motivation and Context

The client now cannot pass tracing context to other system conponents.
Let's enhance it by injecting otel tracing context into the global propagator, then collecting total spans in the same trace.
Screenshots (if appropriate)

That is the enhanced result:

Please fix lint, thanks!

@gaius-qi Done. PTAL : )


storagecache release

https://github.com/Azure/sdk-release-request/issues/4228
Recording: https://github.com/Azure/azure-sdk-assets/tree/js/storagecache/arm-storagecache_4a87b481e5

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-storagecache


Async API

Having an async API would be nice.

The updated API would be a good moment for introducing support for connection reuse (shared client).


Reorder priority of users to receive OA reminder emails

Currently, OA reminder emails go out to the first X users in the list of users that need emails, where X is the "email cap" number in the OA notification settings. A user "needs" an email if they have publication that is subject to the Standard OA Workflow and doesn't have an OA URL, and if they haven't received an email within the last 6 months.
The list of users needing emails seems to be prioritized alphabetically by Access ID. For example, on Feb. 12, 2024, 300 users received reminder emails:

5 users had Access IDs beginning ar, cd, ee, g5, and hm.
The other 295 users had Access IDs beginning with ji through lx.

The result of this is that users with Access IDs at the beginning of the alphabet will receive an email in the first week that they are eligible, whereas a user at the end of the alphabet will only receive an email if X is greater than the number of eligible users in a given week.
Ideally, we would order the list of users needing OA reminder emails based on the "OA notification last sent at" time stamp (so that those who received an email furthest in the past get a new email first) rather than alphabetically by Access ID.
This is low priority. I'm hopeful that we'll get through the backlog of users needing OA reminder emails and be able to keep up with this such that the number of users needing an email in a given week is never much greater than X and naturally smooths out. Documenting this issue just in case that doesn't happen.

Not sure why, but looking at March 25, 2024 emails, this seems no longer to be the case.

@ajkiessl Related to this issue, I have found a user (bsw13) who has never received a reminder email, and I can't figure out why they haven't (especially since we've gotten the total number of emails needed down to 0 many times). Is there a way to check if they are due for an email? I know how to see the count of users who are due for an email in a given organization, but I'm wondering if there's a list somewhere of the users who are currently queued up for one. Thanks!

@anaelizabethenriquez There isn't a view for admins to see who is queued up for an email, but I can check from the backend.  This user is not listed to receive an email.  It appears there's an issue with our database query to determine who needs an email.  If the user is not part of an organization, they get filtered out.  This is the case for this user — no organization.  Adding this user to an organization should fix the problem in the short term.  We may want to open an issue to fix the database query, assuming we want oa notification emails going out to users not associated with an organization.

Thanks, @ajkiessl! I created a new issue for this, #1015.

Adding this user to an organization should fix the problem in the short term, but we may want to open an issue to fix the database query. That's assuming we want oa notification emails going out to users not associated with an organization.
Also, we'll probably want to figure out why this user is not associated with an organization.

I can't remember for sure why this was a condition in the query, but I'm certain that it was intentional. It may have been an attempt to make sure that RMD doesn't send OA emails to people who are still in the database but no longer affiliated with Penn State (thus, no organizations). Whether or not the data about organization affiliation stays sufficiently up-to-date and whether or not it's correct enough for that to work is another question.
As @ajkiessl said, I suppose we'd want to determine:

Whether or not my guess above is correct
If bsw13 actually belongs in one or more organizations
If so, why they're not in them currently
Whether or not the organization membership data is generally reliable enough to use for this purpose


Multi window example should include example of how to bubble the close event on the main window to all children windows.

Specific Demand
This is required because in certain circumstances you may launch a headless window (as seen in the overlay example) as a popup window. Closing the main window will actually do nothing on MacOS specifically if a headless window still exists from the same process.
Implement Suggestion
Not quite sure on the exact fix but I assume simply calling close on all open windows prior to emitting the actual close event would be adequate.

The way I've solved that is by moving a flume receiver into the the window. Then, when the parent window closes, it has a Vec<Sender<Action>> and sends a close method to each child window. The way to get a channel into a Window was a bit tricky because the documentation is sparse:
fn open_window(cx: Scope) -> Sender<Action> {
    let (sender, receiver) = flume::unbounded::<Action>();
    let dom = VirtualDom::new(new_window);

    let s = LogicalSize::new(800., 600.);
    let builder = WindowBuilder::new()
        .with_inner_size(s);

    let dom_scope = dom.base_scope();
    dom_scope.provide_context(receiver);

    let config = Config::new()
        .with_window(builder);
    self.context.new_window(dom, config);
}

fn new_window(cx: Scope) -> Element {
    let Some(receiver) = cx.consume_context::<Receiver<Action>>() else {
        return cx.render(rsx!(div {"Unknown Error "}));
    };
    cx.render(rsx!(window_state.window(cx, receiver)))
}

Great solution! This is an API surface we need to overhaul, but since it's breaking, we can't do it until the next major release.
The trickiness is that the window that tao gives has a drop handler, so if you open a window and then close the scope, it disappears immediately, hence the idea that the window that spawned the window is the owner.
However, I think we can address this specific issue in a minor release.


Query composition api

We should be able to compose queries together. My concerns are on the API at the moment and not implementation. There are 2 specific problems that I want to solve: 1) easily augmenting an existing query and 2) nesting queries.
Problem 1: Augmenting existing queries
Our current query implementation requires that you specify all of the parameters when the query is created like so:
field = text_field("My Text Field", visible: false)
users = css(".user", count: 3)
grace = css(".user", count: 1, text: "Grace Hopper")

If you want to write a test that ensures that an element has been hidden you have to do something like this:
session
|> assert_has(css(".user", text: "Grace", visible: true))
|> click(button("Hide User"))
|> assert_has(css(".user", text: "Grace", visible: false))

Ideally we could extract the base "grace" query and change the visibility property of the query as needed. I think a nice api for doing this might be something like this:
grace = css(".user", text: "Grace")

session
|> assert_has(grace)
|> click(button("Hide User"))
|> assert_has(hidden(grace))

I'm not sure how I feel about extending the query api with semantically meaningful names like hidden over using something like visible(Query.t, boolean()) :: Query.t. I think the later might be less surprising and easier to maintain. But the point stands that I think we should provide a set of functions in Query that allow us to change specific attributes of the provided query. This would also allow us to define queries using pipes like so:
grace =
  css(".user")
  |> text("Grace")
  |> visible(true)

I don't think that we need to deprecate our existing api to support this. We can discuss that if people feel strongly about it.
Problem 2: Nesting Queries
Our queries don't allow you to nest them. For instance if you want to find a text field inside a specific form you have to do that with calls to find like so:
form = css(".form")
field = text_field("User Name")

session
|> find(form, fn f -> fill_in(f, field, with: "Grace") end)

This can lead to race conditions if the form element changes. It breaks the declarative nature of the api. I propose that we should support nesting at the query level. My initial thought is to do something like this:
form = css(".form")
field = text_field("User Name")

session
|> fill_in(within(form, field), with: "Value")

I'm not sure about the within syntax. Perhaps something like child or child_of is better. I'm also not sure if flipping the arguments to something like field |> within(form) reads better. Very open to suggestions here.
Conclusion
I'd love feedback on either of these issues. Both of these are going to be important for making #378 ergonomic.

Sorry I didn't come back here to respond sooner!
I think nested_under is pretty good, though I do like the notion of child or descendant, since that's how the W3 spec talks about the content model.
Since child has the issues of being the immediate descendant, maybe one of the following?
# 1
descendant_of(selector, parent)

selector
|> descendant_of(parent)

# or 2
descendant(selector, of: parent)

selector
|> descendant(of: parent)

They're more verbose, but maybe that's fine?


Invitation from Official Tuya smart.

Dear Sir,
This is from Tuya Smart.We have seen your great work here which helped the Tuya devices to be connected into IoT. We would like invite you to join our Homebridge Tuya Plug-in Beta Test with Tuya support. Your feedback would be helpful to the whole community! Check we have cooperated with Home Assistant Official for improving the integration and users experience. And we hope we could help the homebridge community for their needs as well.

If you are interested in,pls let us know.
Our<EMAIL_ADDRESS>Skype:Devops-Tuya.
Good day!
Best Regards!

@iRayanKhan Have you seen this request?

Hi! Yes, we’re also currently in talks with their team to bring the community the best outcome. Unfortunately we can’t say much more at the moment but the official Tuya team looks to want nothing but the best for all of you


What is the reason for the mismatch in results?

This emulator compiled with JTAG Remote Bitbang client. To enable, use +jtag_rbb_enable=1.
Listening on port 42453
[UART] UART0 is here (stdin/stdout).
Initialization finished!
It takes 8295 cycles for CPU to finish the task.
It takes 1717 cycles for CGRA to finish the task(1).
(2, 15, 0): 0, 3433
(2, 15, 3): 0, 4117
(2, 15, 6): 0, 4801
(2, 15, 9): 0, 5485
(2, 15, 12): 0, 6169
(2, 15, 15): 0, 6853
(2, 14, 0): 0, 2799
(2, 14, 3): 0, 3396
(2, 14, 6): 0, 3993
(2, 14, 9): 0, 4590
(2, 14, 12): 0, 5187
(2, 14, 15): 0, 5784
(2, 13, 0): 0, 2249
...
What is the reason for the mismatch in results?

I'm wondering whether the cgra_execute() in the software/tests/bareMetalC/xxx.c is consistent with the CGRA configuration. Could you try the conv2d_3x3.c example to check the result?

Thank you very much for your reply. Based on your prompt, I have now resolved the issue.


Connect Redis with Cachet

Hey guys, hoping you can guide me in the right direction here...
Was asked to implement Cachet at my company but I'm not a developer and am having a hard time setting up the cache-side of it.
Didn't have any issues with setting up Cachet with Docker in my localhost but would like as well to see it running with Redis cache.
From what I've been reading, the best way to make Redis work along with Cachet in Docker is by running a different container and link them both together...
My question is: what exactly do I need to change in .env and .yml files so that I make it happen? Or...is there an easier solution to this?
Really just trying to get some guidance here! Any input is greatly appreciated guys!
BTW, Cachet is awesome, was really easy to make a business case to show my superiors 😄

It should just be a matter of linking a redis container, and setting the relevant redis ENV variables, however I believe this won't work until we have a 2.4 release, so that Cachet includes the predis dependency.
I started a branch here which is pretty close, but does require an image to be built from the upstream 2.4 branch : https://github.com/CachetHQ/Docker/tree/redis-test
Once 2.4 is generally available, I think we can look at supporting an optional external redis image, if there is interest and benefits to doing so.
We currently default to the PHP apc cache driver, which seems to work pretty well in most cases, although I haven't really done extensive testing in that area. Performance with the defaults always has seemed good enough.

@djdefi Thanks for the insight! I might have to rethink it then and go with APC instead of Redis. Thanks man!

It should just be a matter of choosing APC during the setup / setting in in the environment. #336 makes it the default as well.


Disable flaky test for now

Motivation:
JdkOpenSslEngineInteroptTest.testMutualAuthSameCerts() is flaky on the CI and so fails the PR build quite often.
Let's disable it for now until we were able to reproduce it locally and fix it.
Modifications:
Disable flaky test
Result:
More stable CI builds

Once pulled in I will open an issue for this


locale getLayers and addLayers to mapview

Getting all Layers [json] for a locale adds unnecessary requests.
The /api/workspace/locale endpoint should have an options to return all layers as JSON objects instead of keys.
Layers provided as object with the locale to the mapview creation should automatically be added by calling the addLayer method.
The addLayer method should check whether an array is provided and also allow for a single layer to be added.

A second PR for adding the layers in the Mapview creation should be made once #1095 has been reviewed and merged.


standardize docker python versions

standardizing on<EMAIL_ADDRESS>across docker images

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#234  👈
#230
#225
#220 : 1 other dependent PR (#224 )
#219
#218
#217
#216
#215
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @chrisaddy and the rest of your teammates on  Graphite


Registering with fsspec, and speed relative to SFTP

Hi - I'm interested in using sshfs as a faster alternative to the builtin sftp filesystem in fsspec (and also need server side copy) in Runhouse, a compute and data sharing layer for ML. It appears to me that sshfs still is not built-into fsspec and I need to register it as suggested here to use it with apis like fsspec.open(). A few questions I couldn't figure out:

Why has sshfs not yet been made a builtin implementation of fsspec, nor register itself upon installation like other non-builtins? Is it due to some stability or hardness bar it hasn't yet reached?
Will it indeed be faster than the builtin SFTPFileSystem? I see that SSHFileSystem is faster than Paramiko, but can't tell if there's any reason it'd be faster than SFTP.

Hey @dongreenberg . Thank you for your interest!
sshfs was developed as a part of https://github.com/iterative/dvc and we were not sure that we are ready to submit it as a defeault one to fsspec.
As pointed out in that discussion, we could try doing that now. If you are interested in contributing, feel free to submit a PR for that. Especially if you plan on using sshfs.
Regarding the performance, sftpfilesystem is also paramiko-based and sshfs is based on an amazing project https://github.com/ronf/asyncssh . I don't remember any particular benchmarks from the top of my head, but we've had our fair share of struggle with paramiko in dvc and when implementing sshfs we did see much better performance when downloading/uploading as well as much better overall stability (asyncssh is miles ahead of paramiko in terms of overall quality). Another benefit of sshfs is that it is async-capable (again thanks to asyncssh).

I would be interested! What would be needed for such a PR?
I can also do a smaller step of just adding the standard fsspec registeration call in the sshfs package to make SSHFileSystem the filesystem for "ssh" if the user has sshfs installed. That would be intuitive behavior to me, and would mean that we don't need to deal with some kind of migration from the behavior of the SFTPFileSystem which is registered for 'ssh' in fsspec today (For example, SSHFileSystem expects credentials in a slightly different format that SFTPFileSystem). WDYT?

@dongreenberg It would be something like https://github.com/fsspec/filesystem_spec/pull/952 The time consuming part is using sshfs and trying to pinpoint what it lacks.

@dongreenberg With the above PR merged and latest release, sshfs now automatically registers with fsspec.
If it's still relevant to you, you could give it a try!


how to adapt aspect ratio

After reading the code, I realized that the aspect ratio is fixed throughout the tracking, because the make_scale_pyramid function creates the pyramid evenly along with the width and height.
So the question is: how to adapt to changing aspect ratio?
Thanks!

Hi,
The code doesn't allow change in aspect-ratio unfortunately.
A simple way to do that is to use a single scale and train a second network which only does bounding box regression.


Entities fall through jumppads

If an entitiy (player or enemy) triggers a jumppad while it can't move vertically (-> while the velocity that is being applied to it by the jumppad can't be "executed") (for example because another solid entitity is located directly above it), the entitiy simply falls through the jumppad.
(reproducable, consistent)
(low priority)

Jumppad tiles aren't solid, which means other solid entities (like that one enemy) can push the player (or other jummpad-affected entities) through the jumppad.
Possible solutions:

Make Jumppads solid.
Jumppad collision checking would have to be adjusted, and would probably have to assume that the tile is solid.
Don't use Jumppad component.
Instead, configure event/actions to recreate the same behaviour, for each tile that needs it. This allows for way more flexibility, as collision checking can be adjusted per entity, instead of the Jumppad code needing to assume stuff, like that the entity is solid.
This obviously depends on me adding the events/actions system to tile configs first.
After more thought, this makes no sense as the jumppad.

I'll work on making solid jumppads work.

Works for now, could probably be made solid via config, but probably also unnecessary.


issues for non-maintainers to take a look at?

any issues for casual OSS enthusiasts to take a look at, perhaps something in the backlog?
taking a look at some of these, it's not immediately clear what's a good first issue, etc? maybe a top-level issue to track these? idk, just spitballing as i would love to help out with anything i can.

Hello @flbn,
thanks for your feedback. I did make a few "good first issue"s now.

I'm going to close this as @jtklein added this label to a few issues. In my experience, it's hard to judge what is a good first issue since we don't know what capabilities people have when they decide to contribute. IMO if you'd like to contribute, have a look at a few issues and try one that seems reasonable to you.


Fix bug in dropdown

Fixing a bug in the dropdown component. This only happens on mobiles with IOS. You try to close the dropdown when clicking outside it and nothing happens. To correct it simply add a cursor: pointer in the style of .dropdown.brackground

Thank you!


Middleware of ForwardAuth returns incorrect location header

Welcome!

[x] Yes, I've searched similar issues on GitHub and didn't find any.
[x] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I made an auth server that returns a relative url as the Location header in the response. I'm expecting the relative url will be passed to the downstream and then be resolved by the browser or other clients.
What did you see instead?
ForwardAuth middleware resolves the location header and return the resolved url as the location header in the response. While the correct behavior should just return the original location header.
https://github.com/traefik/traefik/blob/33c1d700c02ad09ab793673a14674b39d78fe352/pkg/middlewares/auth/forward.go#L193
For example,

Auth server endpoint address: http://forward-auth.server.local:8080/auth
Auth server response Location header: /index.html
Downstream received response Location header: http://forward-auth.server.local:8080/index.html
Expected Location header: /index.html

Note, that the location should be resolved at the customer side, like the browser, which should be relative to the original forwarded domain, not the auth server.
What version of Traefik are you using?
v3.1.6
I checked the latest code. It seems it's still the same behavior.
What is your environment & configuration?
Not related. But can provide if being asked.
If applicable, please paste the log output in DEBUG level
No response

@emilevauge I made a PR to fix this, Please review


Remove casting

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
#19238

BC

Line already removed, closing.


Output generated conversion functions/names

This outputs the generated functions/names to files so that people who hit test failures related to needing to regenerate conversion functions already have them generated

@wojtek-t PTAL

@pmorie FYI

@pweil- @sdminonne

One of the things I struggled with recently was that the generator output didn't tell me all of the things it failed to generate based on an api change I made (removing an field from internal but leaving it in the v1beta* apis).  It was on Container so pretty much everything that had a container didn't generate.  Maybe we can use a technique like this to give some output in the conversion utility for reference.

Cleaned up files if there were no problems

LGTM


Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)

My Angular version is 10, and i'm getting this error after this package's been installed.
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:171-191
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 59:83-103
Can't import the named export 'ChangeDetectorRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 55:18-27
Can't import the named export 'Directive' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:145-158
Can't import the named export 'ElementRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 59:58-71
Can't import the named export 'ElementRef' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 21:25-37
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 22:26-38
Can't import the named export 'EventEmitter' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 60:22-27
Can't import the named export 'Input' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 73:18-26
Can't import the named export 'NgModule' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 62:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 64:22-28
Can't import the named export 'Output' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 23:22-34
Can't import the named export 'Subscription' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 42:32-44
Can't import the named export 'debounceTime' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 41:22-31
Can't import the named export 'fromEvent' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 42:18-27
Can't import the named export 'startWith' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:204-222
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 69:141-159
Can't import the named export 'ɵɵFactoryTarget' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 54:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 72:0-27
Can't import the named export 'ɵɵngDeclareClassMetadata' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 53:25-48
Can't import the named export 'ɵɵngDeclareDirective' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 52:25-46
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 69:22-43
Can't import the named export 'ɵɵngDeclareFactory' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 71:22-44
Can't import the named export 'ɵɵngDeclareInjector' from non EcmaScript module (only default export is available)
ERROR in ./node_modules/ngx-metafizzy-flickity/fesm2015/ngx-metafizzy-flickity.mjs 70:22-44
Can't import the named export 'ɵɵngDeclareNgModule' from non EcmaScript module (only default export is available)
ERROR in node_modules/ngx-metafizzy-flickity/src/app/ngx-flickity/ngx-flickity.directive.d.ts:16:21

Which version of this package do you use? The current version needed angular13.

"ngx-metafizzy-flickity": "^3.0.0",

which version should I use for angular 10?

and how can I use this for angular 10?

Please try version 2.2.0.
The best way is to update angular in your project :-)


Emit type arguments for call expressions

Description:
The ECMA code generation implementation was not emitting type arguments for call expressions. This PR fixes that.

 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.


ctx.nuxt does not exist when build: false in setup

🔗 Linked issue

Resolves #918
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[X] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Thank You so much for this @Al-Rozhkov. I've been wondering why I've unable to run my tests for a while without any luck.

Thank you 🙏
Can you explain a bit about why you would do this rather than passing that config to setup?

Thank you 🙏
Can you explain a bit about why you would do this rather than passing that config to setup?

I wasn't sure how to build Nuxt manually and make setup use exact that build. I would appreciate your advice.
Also not sure why windows tests failed.


GestureDrag does not signal events

Sorry if I'm again inadvertently using the issues as support, but I triple-checked the testcases to be identical this time :-)
So, creating a GestureDrag on ApplicationWindow in Rust, clicking (or dragging) in the window does not trigger the drag-begin-event, but in C it does.
Testcases: https://github.com/Voker57/gtk-rs-button-testcase/tree/drag

gesture_drag is unreffed at the end of the activate signal handler closure. As nothing else is keeping a reference to it, it is then destroyed and there's no chance for the signal to trigger anymore. You need to keep it alive somehow for as long as you need it.
In the C code you're leaking gesture_drag.


Height calculation is broken on recent Unity

I tried this out on Unity 2018.3 and my Help always pushes my actual properties below the bottom edge of their containing component which makes them render over top of the next component.
Not sure how to fix it. However, it looks like this alternative solution using DecoratorDrawers works with Range, arrays, and my simpler use cases.
Might be worth integrating that code?

I tried this out on Unity 2018.3 and my Help always pushes my actual properties below the bottom edge of their containing component which makes them render over top of the next component.
Not sure how to fix it. However, it looks like this alternative solution using DecoratorDrawers works with Range, arrays, and my simpler use cases.
Might be worth integrating that code?

Hey, I tried both versions and they both have same issue with height calculation. In my case the result of height calculation for the helpbox is over 3000 pixels in both solutions. Any idea how to fix the height calculation?

@CSE-JS: I switched to NaughtyAttributes.InfoBox worked for me on Unity 2020.3. They also have ValidateInput which is a nice alternative -- only show error icon when something's wrong.


Ballerina format wrongly formats @untainted function parameter

Description:
Ballerina format wrongly formats @untainted function parameter
Steps to reproduce:
Try "ballerina format" below code snippet.
import ballerina/http;

public client class MockHttpClient {
    public remote function get(@untainted string path, http:RequestMessage message = (), http:TargetType targetType =
                               http:Response) returns @tainted http:Response|http:Payload|http:ClientError {

        http:Response res = new;
        res.statusCode = 500;
        return res;
    }
}

It will remove the space between @untainted and string as @untaintedstring.
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed via #26529


chore: share vscode lint settings

@R894 I fixed a problem I had with your test, could you please have a look? thanks!


Added support for custom animation

Added support for custom animation.
Just need to set the animation in builder pattern and that will be repeated on the image drawable.
Added support for infinite animation for now.

This was rebased and merged into master.

Thank you @muditpant13


Add yaml config support

Pull Request Test Coverage Report for Build 196

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.734%

Totals

Change from base Build 194:
0.0%

Covered Lines:
494

Relevant Lines:
583

💛  - Coveralls


Simplify docker functions

Instead of piping the standard output of docker ps and docker images
through a series of heads, tails, and awks, use the flags available to
the docker command to achieve the same goal.

Thanks!


README.md References Section Enhacements

We kindly need to improve the quality of references section properly. Kindly requesting your pull requests in the form of feature/ branch

feature/references branch contains initial commits to our reference paper list.


APT whitelist request for texlive-backports

There already seems to be an issue open travis-ci/apt-source-whitelist#55 requesting the texlive-backports source.


Diff without visible changes

I've created a file using PHPStorm via New -> PHP Class. (It uses some predefined templates).
$ php-cs-fixer fix --diff --dry-run
Loaded config from "/home/kilte/projects/crazyarts/backend/.php_cs"
   1) A.php
      ---------- begin diff ----------
      --- Original
      +++ New
      @@ @@

      -class A
      +class A
       {
       }

      ---------- end diff ----------

   2) IA.php
      ---------- begin diff ----------
      --- Original
      +++ New
      @@ @@

      -interface IA
      +interface IA
       {
       }

      ---------- end diff ----------

Fixed all files in 0.267 seconds, 5.750 MB memory used

If I create a class manually, all is ok.
.php_cs:
<?php

$finder = \Symfony\CS\Finder\DefaultFinder::create()
    ->files()
    ->name('*.php')
    ->in(['source']);

return \Symfony\CS\Config\Config::create()
    ->finder($finder)
    ->fixers(['-psr0', '-phpdoc_to_comment']);

Diff you provide is in fact:
-      class A
+      class A
       {
       }

take a look at a whitespace after class' name that was removed by fixer.

Really. Sorry.

Glad to help ;)


[IndexDatastore] Provide an option to disable the file-out-of-date notification mechanism

This mechanism is disabled by default for the CIndexStoreDB API because the out-of-date notifications are not exposed at all, so the mechanism is taking CPU & memory unnecessarily.

@swift-ci Please test

@swift-ci test linux platform

@swift-ci Please test


Migrate from Drone to GitHub Action

This PR

migrates the existing Drone workflows to GitHub Action workflows
bump the golangci-lint to the latest version, replace golint ( which is deprecated) with revive, and fix some syntax errors reported by revive

Validation of the new GHA workflows:

CI on Pull Request is trigged on this PR
CI on Release is validated here, tags are pushed as jq20/system-agent/v0.3.7-suc and jq20/system-agent/v0.3.7

CI fails because it hits Docker's rate limit ( https://www.docker.com/increase-rate-limits/).


[DOCS] [ ENHANCEMENT][Navigation.md] - Package manager conflict on install instruction

The instruction will produce error and delete some package if the user first installation of react native using YARN, and the instruction to install react-navigation library use NPM.
Motivation
I start to learn react with zero knowledge of es6, package manager. I follow all the basic documentation. Until i come to Navigating Between Screens section. I got error after install the react-navigation package using NPM
Test Plan
This is what happen after i use npm install --save react-navigation

After that i cant run my react native on android

After some googling i realize the problem come from the package manager. I shouldnt use npm because my react native projects installed using yarn.

I hope my change can save the millisecond of time for the developers who are still learning like me
Release Notes
CATEGORY
[DOCS] [ ENHANCEMENT] [Navigation.md] - Add package installation instruction option

We've been purposefully avoiding listing Yarn in the docs, to avoid issues like these. The docs assume you're using npm everywhere to install the packages. We make the assumption that if you're using Yarn, you'll know which commands to use when our examples list npm.
I wouldn't merge this PR with this single change, but I'd take a look at a PR that updates all of the onboarding docs to include Yarn as an option. This is no small change, as npm is mentioned in several places and we want to avoid confusing newcomers who don't know the difference between npm and yarn.


Added documentation for two core modules

Hi Julian & the PyMOO community,
I have added module, class, and function type hints and documentation for two of the core modules in PyMOO. Hopefully this is helpful for the package, its developers, and its users.
Additionally, I have added some minor features to the two modules. They include:

Inclusion of an __all__ variable to specify what objects are to be imported from a wildcard statement: from pymoo.core.<module> import *
Addition of a deprecation warning when calling Individual.feasible.

Thanks for the effort improving the code documentation!


[🖥] Add example configurations for LSP servers

It would be a good idea to add some example configurations for various editors, so we could just copy+paste when using asai.lsp in other projects.
Unfortunately, the situation with lsp-mode is pretty grim; see https://github.com/emacs-lsp/lsp-mode/issues/3625

Perhaps we (or I?) should spend a bit more time resolving this issue. 😅 @TOTBWF What's the current progress of fixing bugs in the cited issue?
@mikeshulman Is there a particular editor you want to try out first?

I discussed the issue with the maintainers and it's a WONTFIX 😔  However, it looks like the emacs community has decided that https://github.com/joaotavora/eglot is the implementation of choice, and has upstreamed it into emacs proper.
It appears that they have an opt-in mode that does the right thing with UTF-16; not sure if UTF-8 is supported, or if they've implemented the position encoding handshake from LSP 3.17. I'll try and ask on IRC

@TOTBWF I see, but no, I don't think that's the main issue or difficulty here. There's no need to try to work around UTF-8/16 now---at least that's not the priority. The main issue here is the documentation. In @mikeshulman's case, I strongly suspect that the prototype only uses ASCII, so none of the encoding issues should matter.

I don't use emojis, but I'm a big fan of unicode math symbols.  In fact one of the reasons I picked fmlib_parse was that it seemed like the best lexer/parser combination for dealing with utf8.  So no, I'm not using only ASCII.
I am also a dedicated Emacs user, but not particularly a fan of things that try to compile/typecheck my code while I'm writing it.

not particularly a fan of things that try to compile/typecheck my code while I'm writing it.

Maybe that's an exaggeration.  I don't hugely mind the way tuareg highlights errors in my OCaml code in real-time, although I like that it doesn't do it until I save the file.  In fact I would prefer to have a separate command to make it do that, so that if I'm making a big breaking change I can save while I'm partway through it even though what's currently in the file is not syntactically correct without causing huge amounts of the code to be highlighted.  (Maybe there's a configuration option for that, I haven't found it but I haven't looked really hard.)
But I've had pretty unpleasant experiences with Lean.  A lot of that is probably due to the typechecking not always being instantaneous (unlike with OCaml), so it's hard to tell whether the automatic highlighting is in sync with the text or not.
I'm not sure this is relevant at all to what we're talking about here though.

@mikeshulman The speed is indeed important, especially for auto-completion. So we were thinking about promoting the design of having a separate scope-checker to give quick feedback on whether there's a typo, etc. None of these ideas have been realized so I can't really make any useful comment. 😅

@TOTBWF Is examples/stlc/asai-stlc-lsp.el still working?


Add support for amazon-bedrock-guardrailConfig

Add support for amazon-bedrock-guardrailConfig

Adds guardrailConfig to hold values for this field within the guardrails property for Bedrock classes and this is passed to the bedrock invoke model calls via the amazon-bedrock-guardrailConfig field in the body. amazon-bedrock-guardrailConfig allows adding a tagSuffix [documentation] and different streaming response behaviors [documentation]
Also cleaned up some documentation, error messages and tests
Added a conftest file for common fixtures that can be used across tests

Closes: #52

@3coins: can we trigger the workflow checks on this PR? Thanks.

is there any idea when this might be released?

is there any idea when this might be released?

I haven't heard back from @3coins yet, but hopefully soon!

@3coins any updates on this PR? I need this feature ASAP. Please let me know if I can help :)

@supreetkt
Can you fix conflicts and rebase from main.

hey guys! Is there any chance this is going to be released soon?

Does this actually work with streaming? I'm finding that even with these changes, whether I use asynchronous or synchronous streaming with the Anthropic bedrock models in langchain, as soon as I include guardrails I get the results in a single chunk rather than streaming out the response in smaller chunks gradually.

I really hope this gets implemented soon.

@supreetkt Can you fix conflicts and rebase from main.

yes, I can resolve the conflicts. Missed notifications on this.

Is there any idea when this might be released?


Using in a framework with backward compatibility?

Hi,
I'm currently building a framework which is shared between two applications, one with a minimum deployment target of iOS 13 and another with iOS 11.
I am able to use Combine in this scenario by utilising @available attributes to limit optional portions of the framework to iOS 13+, but GRDBCombine refuses to work when the target is lower.
Is it possible (or even desirable?) for a library such as GRDBCombine to allow the framework to be imported, but wrapped up with @available attributes everywhere such as what I would need to use it here?
Thanks

After reflecting on this a bit further, I believe the better approach would likely be to create a new iOS 13+ framework that has my current framework as a dependency. This would then avoid the issue and make it clearer what is supported, though at the cost of another framework to manage.
I am still curious about your thoughts on this (the combination of GRDB and Combine having a higher requirement than either separately?), but feel free to close this as it isn't really an issue with GRDBCombine

Hello @gverdouw,
I'm not sure I follow. What would be the point of hiding the whole GRDBCombine APIs behind @available, since this library requires Combine anyway? I don't have enough information about your setup - maybe you just need something like #if canImport(GRDBCombine)?

🤦♂ How did I miss that, canImport is the solution here.
Thanks @groue!


[Feature request] Support SSH invoke_shell

Hi Cédric,
First of all, your citizenshell is awesome! The package is so well written and a begginer like me learned a lot from your code.
However, my current project requires to interact with a customized SSH server in a WiFi router, and I'm having current barriers:

The citizenshell.SecureShell's initialization failed because of BannerTimeout Exception, after I directly adding bannter_timout=100000 into SecureShell's do_connect, the 2nd barrier arises
The SSH server seems to be incompatible with paramiko's exec_command(), chan.recv_exit_status() seems to run internally until the banner_timeout exceeded.

I tried using paramiko's invoke_shell and finally could manually interact with the router's SSH shell. I forked citizenshell and tried to modify by myself but maybe my limited knowledge is not enough yet. It would be wonderful if user could pick a method between exec channel and invoke_shell to interact with SSH server.
Thank you for the wonderful citizenshell!

Hey,
Thanks for the report (and the compliments 😊). Sorry for not getting back to you sooner, but I just realised that I somehow disabled the notifications from github. I'll look into what you propose and see what I can do. Can you maybe share what you tried?
Kind regards
-Cédric

Hi,
With paramiko exec_command(), I have to write my own SSH class using invoke_shell() instead of exec_command() in order to communicate with the customized shell of the WiFi router.
Best regards,
Duy


Changing color mode panics

Hello,
changing a color mode using use_color_mode causes a panic for me.
I have prepared a simple reproduction app.
Cargo.toml:
[package]
name = "app"
version = "0.0.0"
edition = "2021"

[dependencies]
console_error_panic_hook = "0.1.7"
leptos = { version = "0.5.0-alpha2", features = ["csr", "nightly"] }
leptos-use = { git = "https://github.com/Synphonyte/leptos-use.git", rev = "075b073", features = [
  "storage",
] }

main.rs:
use leptos::*;
use leptos_use::{use_color_mode, ColorMode, UseColorModeReturn};

#[component]
fn App() -> impl IntoView {
    let UseColorModeReturn { mode, set_mode, .. } = use_color_mode();

    let toggle_dark = move |_| {
        set_mode(if mode() == ColorMode::Dark {
            ColorMode::Light
        } else {
            ColorMode::Dark
        });
    };

    view! {
        <div>
            <button on:click=toggle_dark>"Toggle dark"</button>
        </div>
    }
}

fn main() {
    std::panic::set_hook(Box::new(console_error_panic_hook::hook));
    leptos::mount_to_body(|| view! { <App/> })
}

Additional context:

feature "storage" must be present for the problem to occur
only changing color mode (dark -> light / light -> dark) triggers the panic
appears in both dev and release profile
Trunk was used to run the code above in case that matters :)

Thanks for the excellent error report! It was indeed a problem in use_storage. I'm surprised that this ever worked to be honest. 😄
It's fixed now anyway.


I am using md2-tabs in my Angular 2 Application. Tabs are responsive in Chrome but not in Firefox.

Bug, feature request, or proposal: BUG
What is the expected behavior?
Responsive behaviour in as in Chrome
What is the current behavior?
Not responsive in Firefox
Firefox not responsive
  Chrome One responsive
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/rQmUz8WYRh5Vz4gwY8E4?p=info
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, MD2, OS, browsers are affected?
Is there anything else we should know?

@sunpasup it is working fine in FF


Incorrect MutatingWebhookConfiguration

When using a.GenericKind Pepr assumes the plural for resources. We need logic to check if the kind.kind ends in y, and if so, add ies instead of s
Example of error:
in Capability
When(a.GenericKind, {
  group: "source.toolkit.fluxcd.io",
  version: "v1beta2",
  kind: "GitRepository",
})

Resulting MutatingWebhookConfiguration
  - apiGroups:
    - source.toolkit.fluxcd.io
    apiVersions:
    - v1beta2
    operations:
    - CREATE
    - UPDATE
    resources:
    - gitrepositorys

expectation
gitrepositories                   gitrepo            source.toolkit.fluxcd.io/v1beta2       true         GitRepository

No biggy, i can work around this and I will pick up this PR.

A bit confused about this, why wouldn't you pass in the plural in that case?
When(a.GenericKind, {
  group: "source.toolkit.fluxcd.io",
  version: "v1beta2",
  kind: "GitRepository",
  plural: "gitrepositories",
});

I should have, didn't realize. Thanks -- this will solve that problem.


The panoramic sky field of view is not set correctly in orthogonal mode

Godot version:

0dbe01483a902c49ecedf4fd36b74353424145a5
OS/device including version:

Linux
Issue description:

Auto/default FOV

The same with a similar custom FOV

Steps to reproduce:
Attach a panorama texture to the environment node and press numpad-5.

If I increase sky_custom_fov and then set back to zero the skybox or panorama looks correct. Weird.

In Blender the background is at least not disturbing (and looks physically more correct ?):

The background flickers when you turn the view, but that doesn't seem to be a problem.

I tried that out as I was looking into fixing this, but I think the rapid color flashes when rotating can be problematic for people who are prone to light-induced seizures.

Here's a patch that sets the sky FOV to 0.1 in orthogonal mode when no custom sky FOV is set:
diff --git a/servers/visual/rasterizer_rd/rasterizer_scene_high_end_rd.cpp b/servers/visual/rasterizer_rd/rasterizer_scene_high_end_rd.cpp
index a33c94fbcd..34a8ad2b57 100644
--- a/servers/visual/rasterizer_rd/rasterizer_scene_high_end_rd.cpp
+++ b/servers/visual/rasterizer_rd/rasterizer_scene_high_end_rd.cpp
@@ -1306,13 +1306,15 @@ void RasterizerSceneHighEndRD::_draw_sky(RD::DrawListID p_draw_list, RD::Framebu
 	// Camera
 	CameraMatrix camera;

-	if (custom_fov) {
+	if (custom_fov || p_projection.is_orthogonal()) {
+		// Use a very low FOV when using orthogonal projection.
+		// This is more technically correct compared to drawing a stretched out sky.

 		float near_plane = p_projection.get_z_near();
 		float far_plane = p_projection.get_z_far();
 		float aspect = p_projection.get_aspect();

-		camera.set_perspective(custom_fov, aspect, near_plane, far_plane);
+		camera.set_perspective(MAX(0.1, custom_fov), aspect, near_plane, far_plane);

 	} else {
 		camera = p_projection;

But as I said, it kind of hurts to look at when panning the camera around, especially in panoramas with strong light variations.

Now when I think about it again, in orthogonal mode it would be better to turn the panorama off for the background and/or make a viewport option for a replacement color. You can do that in the blender
viewport.

The sky in the very default "just opened Godot and created new project" 3D scene seems to have the same problem. When set to orthogonal view, the sun seems to be broken in the same way.

@DDL-Blue Indeed, this issue isn't limited to PanoramaSky. It'll occur with any sky that's not a plain color.


Properly account for DAPR sidecar options

Fixes https://github.com/dotnet/aspire/issues/1333
The real fix is in the DAPR lifecycle hook. The rest is just to ensure that the dashboard shows the startup parameters properly for Executables and Containers.
Microsoft Reviewers: Open in CodeFlow

This is fixing a regression. Is it possible to add testing here to prevent future regressions?

This needs to be backported as well.

This is fixing a regression. Is it possible to add testing here to prevent future regressions? (can be in a future PR if difficult. The action now can be to create an issue)

Good suggestion, added https://github.com/dotnet/aspire/issues/1360 @philliphoff  FYI

/backport to release/8.0-preview2

/backport to release/8.0-preview2


[chore](delta writer) remove unused write method

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 37.94 seconds
load time: 576 seconds
storage size:<PHONE_NUMBER>9 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221031092316_clickbench_pr_36254.html


Wrong parameter order inside documentation example

Description
The parameter order in the example is wrong, source_image_digest and cosign_image are switched.
https://github.com/sigstore/sigstore-rs/blob/bb68d371e8c9c4d513b7f74e2073bec80e6ffd2f/src/cosign/client.rs#L75-L80
https://github.com/sigstore/sigstore-rs/blob/bb68d371e8c9c4d513b7f74e2073bec80e6ffd2f/src/lib.rs#L103-L107

Effect: A RegistryPullManifestError as the OCI client reaches out to  docker.io/library/<source_image_digest>, which is hard to understand the source of if you do not closely inspect the URL in the error message.
Version
This affects the most recently on crates.io published version 0.6.0 and the current main branch version. Also affects earlier versions.

Possible API improvment: using &oci_distribution::Reference or a wrapper type instead of &str for OCI images, though I'm unsure about the consequences of this as I'm not too experienced with API design.

Possible API improvment: using &oci_distribution::Reference or a wrapper type instead of &str for OCI images, though I'm unsure about the consequences of this as I'm not too experienced with API design.

I think this would be a nice fix. The API would break, but this is fine.
Would you like to work on this fix with another PR?


Changing a published Kata name?

I tried changing the name of one of my (already published) Katas to something better.
But doing this completely broke the "favourites" (star list) - gave some sort hideous looking DB error saying that the record no longer existed.
So then I was worried that it would similarly break in everybody else's star list or in any collections which it may have been added to.
So there seemed nothing I could do but change the name back to the original again...
Is there a risk-free way to change the name of a published Kata?

it probably has something to do with slugs again.

I've changed to always use ids when generating kata URLs so changing the name shouldn't break stars/collections anymore.


Interpolation functions are called twice

Interpolation functions are called twice for every render in current version 4.3.1
While trying to reproduce, I cloned some existing example that, by chance, used an older version 2.1.0 that did not exhibit this behaviour.
v2.1.0 is not called twice

v.4.3.1 is called twice

Steps to reproduce
https://codesandbox.io/s/v014z5jnll
Put a console.log inside css template.
const Title = styled.article`
  ${() => console.debug("called")}
  ...

Actual Behavior
The "called" will be called twice for every render.
Expected Behavior
Expected is that it is only called once as in version 2.1.0.

While in codesandbox it is indeed called twice every time you click the button, the same code run in my dev environment behaves even stranger. On first render I get
= rendered =
inner
called
nested

on first button click I get
= rendered =
inner
called
nested
called
nested

and all consecutive clicks give only single "called" and "nested".

This is going away with https://github.com/styled-components/styled-components/pull/2428, keep an eye out for 4.2.0 coming soon!


Convert standard single and double quotes to open / close quotes

Is your feature request related to a problem?
In much of the content, quotes are straight quotes which can be hard to parse.
Describe the solution you'd like
Convert all single and double quotes to open and close (aka curling left and right) quotes.
Additional context or notes
See this page for the HTML codes for curling open and close quotes:
https://www.w3schools.com/CSSref/pr_gen_quotes.asp

This can be mostly done by adding the following to the .eleventy.js file.
    // Configure markdown to use smartquotes
    let markdownIt = require("markdown-it");
    let options = {
        html: true,
        typographer: true
    };
    config.setLibrary("md", markdownIt(options));

This makes uses of the typegrapher setting from markdown-it.
However, things that aren't processed by markdown won't be updated. Most notably this is in the excerpts used for the news articles.
When 11ty 1.0 is released it will come with a Render plugin, that will allow us to add a shortcode for wrapping the excerpt in, so that it is processed by Markdown in the nunchucks template.
eleventy-plugin-fluid does come with a markdown shortcode, but unfortunately there isn't a way to configure it. see https://github.com/fluid-project/eleventy-plugin-fluid/issues/85


WIP: QBE generator

Description
This PR implements a backend for qbe. It should replace LLVM backend at some point
Status
No outgoing work, assembly is hard
Development environment
First of, you need to disable stdlib as it's not fully ported yet:
$ find lib -type f | xargs -i sed -i 's!^!// !g' {}
$ find lib -type f | xargs -i sh -c 'printf "\n\n" >> {}' # Work around a lexer bug with comments

Then, you need to get QBE installed:
$ git clone git://c9x.me/qbe.git
$ cd qbe
$ make

ToDo

[x] Generate functions
[ ] Generate variables

[ ] Integer variables
[ ] Special types like booleans
[ ] String variables (will be hard)

[ ] Call standard library functions like printf
[ ] Control statements

[ ] If statements
[ ] Loops
[ ] Match statement No, too hard

[ ] Module support
[ ] Port stdlib
[ ] Add documentation
[ ] Add to "Unreleased" section in the changelog

I'm not able to work on this as I'm not very comfortable with QBE yet, will do this again later


Social handles not placed properly

Description
Social media handles are not placed properly and are overlapping the banner on hover.
Screenshots

pls assign me this

Hey! I would like to work on this. Please assign this issue to me

Hey! I'd like to take up this issue, please assign this to me.

Please assign to me

@SauravMukherjee44 can I work on this??


[gardening] Fixed broken subtype relationship anchor

Removed a stray - in the subtype relationship anchor link

@swift-ci please smoke test

⛵


How to use this model to do other tasks without re-train the tracker?

I am now learning this method to do other tasks and I find it not ideal, so that I modify the parameters in 'helper/bouding_box.cpp' including 'kContextFactor ' and 'kScaleFactor ' to let the tracker search in a smaller region.
But I found the output not ideal, all the bouding boxes turn out to be a small red dot finally.
My question is: is it exist a way to modify the parameters of 'sizeof search region' in order to let the tracker do other task(here I use it to track the dead object in background in order to calculate background optical flow so that I want to modify parameters to let it search in a smaller region)without re-train the tracker?
Thank you

I don't believe so - if you change the parameters you will likely have to
retrain the tracker.
On Sat, Oct 8, 2016 at 10:32 PM, raoqi<EMAIL_ADDRESS>wrote:

I am now learning this method to do other tasks and I find it not ideal,
so that I modify the parameters in 'helper/bouding_box.cpp' including '
kContextFactor ' and 'kScaleFactor ' to let the tracker search in a
smaller region.
But I found the output not ideal, all the bouding boxes turn out to be a
small red dot finally.
My question is: is it exist a way to modify the parameters of 'sizeof
search region' in order to let the tracker do other task(here I use it to
track the dead object in background in order to calculate background
optical flow so that I want to modify parameters to let it search in a
smaller region)without re-train the tracker?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davheld/GOTURN/issues/12, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEHoHOZgaEvO3Y5X1RGzLR8TTUNDg97fks5qyHxjgaJpZM4KR6Xd
.

Ok, I know.
And do you remember how long have you spent to train your tracker?

A few days, I believe?
On Mon, Oct 10, 2016 at 1:29 PM, raoqi<EMAIL_ADDRESS>wrote:

Ok, I know.
And do you remember how long have you spent to train your tracker?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/davheld/GOTURN/issues/12#issuecomment-252592794, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEHoHK2c0r5BBLA5qjpLgEjpjlXwoE4nks5qyiGHgaJpZM4KR6Xd
.

@davheld Hi, @rao1219 I want to increase the searching area during the test using VOT2014, do I need to  retrain the model or just change the parameters in 'helper/bouding_box.cpp' including 'kContextFactor ' and 'kScaleFactor ' ?

In theory, I don't think you should need to retrain the model, but in practice I found that it helps a lot if you do.  You can try it without retraining, but I'm guessing that you'll need to retrain.  If anyone else has tried this, feel free to pipe in here.


Fixes incorrect glyph positioning for text2d

Objective
Fixes #6272
Solution
Revert to old way of positioning text for Text2D rendered text.

I've verified that this fixes the issue.

bors r+


Error when running configure on Kali

OS: Kali 2017.1
I have encountered the following error when trying to run configure:
root@kali:~/kalibrate-bladeRF# ./configure  checking for a BSD-compatible install... /usr/bin/install -c ... checking for strtoul... yes checking for strtol... yes ./configure: line 5095: syntax error near unexpected token FFTW3,'
./configure: line 5095: PKG_CHECK_MODULES(FFTW3, fftw3 >= 3.0)'
Have installed relevant BladeRF resources via apt:
`root@kali:~# apt list --installed | grep bladerf
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
bladerf/kali-rolling,now 0.2016.06-1+b2 amd64 [installed]
libbladerf-dev/kali-rolling,now 0.2016.06-1+b2 amd64 [installed]
libbladerf1/kali-rolling,now 0.2016.06-1+b2 amd64 [installed,automatic]
soapysdr0.5-2-module-bladerf/kali-rolling,now 0.3.2-2 amd64 [installed,automatic]`
I am wondering if there is something that I do to resolve the error. Is there something that I am missing?

Solved this issue by installing libfftw3-dev and pkg-config:
$ apt install libfftw3-dev pkg-config


VScode cursor will switch styles when using pinyin input method

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:
<IP_ADDRESS>
2.macOS 12.1
VScode cursor will switch styles when using Pinyin Input Method, how to adjust? Refer to iA Writer. The cursor style is unchanged.There is no style switching in English in VScode.
https://user-images.githubusercontent.com/72077265/148716148-5f051622-2089-4277-8202-eb6608172902.mp4

When doing composition, we reveal the native <textarea> that we use for input. The native <textarea> only allows to customize the caret color (not its shape or its blinking style). So we can align the color, but that's about it.

✅👍💯

@alexdima This does not solve the problem of frequently switching cursor styles in the input method state. I now request vscode to provide the system default cursor style options to avoid this problem.


[api-docs] rename pin/unpin methods

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/73e592074dabe62f452c291d2f6fde94ec8b9b7a

ncn