Add request queue to callbacks

Before submitting

[x ] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[x ] Did you read the contributor guideline, Pull Request section?
[ x] Did you make sure to update the docs?
[x ] Did you write any new necessary tests?

As a user, it would be beneficial to have the ability to track the progress of requests that re coming in through the LitServe workload. To that end, a good metric to decide on when the LitServe instance is being throttled is to measure the number of requests that are still waiting to be processed in the queue. In order to enable the easy calculation of this particular metric, this PR allows the request_queue parameter to also be enabled as part of the callback trigger.
If the changes are too extreme, it might also be worth pointing out that most queue metrics only need to be calculated as and when we start to decode a request and probably only needs to be added as part of the on_before_decode_request callback trigger.
What does this PR do?
Fixes https://github.com/Lightning-AI/LitServe/pull/262#issuecomment-2384724504
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.
Did you have fun?
Yes(?)
Make sure you had fun coding 🙃

Pasting the comments from here
@vrdn-23 although you can use queue.qsize() method, it is approximate and not reliable.
A cleaner way to this would be to have a middleware with a counter that increment the counter when it enters the request and decrement it after processing the request.
Another reason why it shouldn't be exposed is that - it is the core part to make the request flow from LitServer to LitAPI and if users update or access it then it can slow down or bring some weird behaviour.

A cleaner way to this would be to have a middleware with a counter that increment the counter when it enters the request and decrement it after processing the request.

This does look promising. But I'm a little confused how the logger will have access to the value specified in the middleware? Is there a convenient way to access the middleware attributes from the lit_api variable that is made available to the callbacks?

Middleware won't be able to connect to loggers. You can track the number of requests in queue separately using a multiprocessing shared Value and use the same in Logger to log it.

Closing this PR since we won't be adding request_queue to the callback hooks. If someone reading this thread also want to have this feature, please feel free to comment and we can evaluate this in future. Thank you ⚡

Middleware won't be able to connect to loggers. You can track the number of requests in queue separately using a multiprocessing shared Value and use the same in Logger to log it.

I think the wrong link may have been linked here @aniketmaurya. Either way I think I would like to make sure I document the problem properly so that it is understood why I think the current callback mechanism as it is will not be able to effectively solve it.
Why do I think this will currently not work with LitServe?
The idea here is to be able to expose something that allows us to calculate the number of requests that are piled up in a queue waiting to be processed. In the current callback system, the very first callback happens only after the requests from the queue have processed. This means that there is no plausible way for us to record how many messages are still remaining in the queue. Adding any sort of logging metrics within the callback system will give us an accurate count of how many requests have been processed or how many are concurrently going through each phase, but it will not expose the number of requests that are currently waiting in the queue.
Why do I want this feature implemented in LitServe?
The reason why I am keen to see this behavior implemented in LitServe is because I think the amount of requests queueing up is a very crisp and concise indicator of when we need to scale the number of model replicas up according to the current load. We currently host our models on Kubernetes deployments and we would like to use a more relaible metric that directly reflects the pressure the model server is under. (A good proxy for this would be downstream response latency which can tell us that a particular model request spent too much time in the queue but in this case it is unclear to us whether the extra time is due to the prediction time or due to the time the request waits in the queue.)
Do I have a solution for this?
I agree with @aniketmaurya about the concerns he has raised with regarding exposing the request_queue. There are a couple of scenarios that I've considered that may help alleviate this problem (in order of preference):

Expose Prometheus metrics as a LitServe standard: Prometheus is kind of the go-to standard when it comes to exposing metrics in most production environments which rely on Kuberntes. Having in-built metrics that are served during the server running, would be a minimum requirement for any user that hopes to gets this intergated in a cloud k8s environment (which is where most ML workloads run nowadays).
I would like to volunteer my time and effort in helping LitServe expose a small set of standard metrics that I think will be useful from an operational standpoint so that it aligns with what is present in most mature model-serving frameworks. I understand @williamFalcon's concern with performance metrics hindering performance but I do not expect that this is something that will be impactful enough to hinder any performance gains. (One way to actually verify this would be if we had some metrics available from running the server :) )
Providing these metrics as part of the LitServe standard will be a much more safer/cleaner approach as one could argue that I'm sure a user could inadvertently find ways to mess up the the exposed LitAPI object as well by updating or accessing it.

Add a separate callback that runs before the batches are collated: The other alternate option that I would like the maintainer team to consider which would be a much smaller and less involved fix would be to add a callback that is triggered before the requests are collated (something along the lines of before_request_batching or after_request_batching) and this can expose something innocuous like queue.qsize() as the callback args (which although I recognize as approximate and unreliable is still a better approximation than nothing at all). This should alleviate concerns of users having access to the request_queue object but still provide a way for users to keep track of messages in the queue if needed. This also maintains the argument structure for existing callbacks that only expose the lit_api argument and would act as a special callback just for queues if needed.

I'm sorry if it appears that I'm being stubborn on this. I think this project is a phenomenal piece of work and I truly believe that LitServe has the potential to fill the gap that exists in today's state of model deployment infrastructure where we need to host models that are slightly non-conventioal in either set-up or not fully adopted by the mainstream ML field.
I respect the importance that the maintainers have on not over-complicating the code base but I do think that there are certain features from an operational standpoint that make working with open-source libraries much easier to adopt in a production environment and the cost of maintaining a lean library should not stand in the way of providing a flexible and robust framework.
If the decision stands the same, I will respect that but I do think it is worth re-considering at-least. Looking forward to hearing your thoughts on this!

I think being able to know the approximate size of the queue and track it over time is important. We just need to decide where to do it best.
I agree with @aniketmaurya that exposing the queue is too extreme.
Since this metric is useful under heavy load we need to provide the value proactively in a way that has fewer chances to introduce additional latency.
The middleware route is a good one, we could add a hook similar to on_server_start (that is, triggered on the webserver and not in the workers) that passes the number of active requests (incoming vs served). Wdyt?

we could add a hook similar to on_server_start (that is, triggered on the webserver and not in the workers) that passes the number of active requests (incoming vs served). Wdyt?
Would be amazing!

@vrdn-23 This middleware can track the active requests. @lantiga yeah we can have hooks on_request and on_response that is triggered in the endpoint functions. The will have access to this number of active requests through the headers as well. Is that what you meant?
class RequestCountMiddleware(BaseHTTPMiddleware):
    """Adds a header to the response with the number of active requests."""

    def __init__(self, app: ASGIApp, active_counter: multiprocessing.Value) -> None:
        self.app = app
        self._active_requests = active_counter

    async def __call__(self, scope: Scope, receive: Receive, send: Send) -> None:
        if scope["type"] != "http":
            await self.app(scope, receive, send)
            return
        with self._active_requests.get_lock():
            self._active_requests.value += 1
        await self.app(scope, receive, send)
        with self._active_requests.get_lock():
            self._active_requests.value -= 1

@vrdn-23 @fcakyon you can track the active requests now! More details here.

Fantastic news @aniketmaurya 🔥


cv::dnn::net::forward fails because of the latest Winograd optimization in OpenCV

Your code was running properly before the following merged PR: https://github.com/opencv/opencv/pull/22593
Could you confirm that there is indeed a regression in OpenCV due to this PR?
I tested your code with yolov5s-seg.onnx under Visual Studio 17.1.2

I got the same error in forward.
I'm not sure whether it is caused by this pr, because I run it in Python(opencv-python <IP_ADDRESS>) without error.
import cv2
import numpy as np
print(cv2.__version__)
net =cv2.dnn.readNetFromONNX("./yolov5s-seg.onnx")
size=(640,640,3)
img=np.zeros(size,dtype=np.uint8)
blob=cv2.dnn.blobFromImage(img,1/255.0,size=size[0:2],mean=(0,0,0),swapRB=True)
net.setInput(blob)
out=net.getUnconnectedOutLayersNames()
print(out)
pred1,pred2=net.forward(out)
print(pred1.shape,pred2.shape)

At present, it can be determined that there will be problems under the cpp, so I plan to cmake the source code and debug it.


Named Modules

Is it possible to have named modules?
I.e instead of
    define(['require', 'jquery'], function(require, $) { //...

We would have
    define('durandal/system', ['require', 'jquery'], function(require, $) {

This way Durandal can easily be packaged with existing bundling methods (ASP.NET bundling) without having to add a JavaScript build method, which is overkill for most existing ASP.NET projects.

isn't it a requirejs related question? here is an example taken from requirejs doc page http://requirejs.org/docs/api.html#deffunc
//Explicitly defines the "foo/title" module:
define("foo/title",
    ["my/cart", "my/inventory"],
    function(cart, inventory) {
        //Define foo/title object in here.
   }
);

@ibrahimbensalah it is about the RequireJs modules yes, however it is the implementation of the modules within Durandal  that this issue talks about.
If you want to bundle anonymous RequireJs modules you need a custom build method to give the modules names based on their location within the project. I don't know of a reason why the modules inside of Durandal cannot have explicit names. There may be a reason.
If there is no reason why Durandal cannot have explicitly named modules, then I think it would be better to have names, that way we can bundle the Durandal files without having to apply a custom build method which adds the explicit names.

@marvc1 I totally agree, but just to be clear, can you confirm that named modules are not working, inside durandaljs? as far as I know, durandaljs relies on requirejs without any additions.

Named modules work perfectly inside Durandal.
If there is no reason why the main repo cannot have explicitly named modules, it would be nice if we could name them, as currently I am manually changing them each time there is an update. I expect quite a lot of  people are using Durandal in this way.
The bundles are just a script tag.

Just use Gulp.

There doesn't look to be any reason why not to do this. I too use Asp.Net MVC bundling and named modules would save a whole lot of effort.

The reason I can see not to do this is that it's explicitly recommended against in the requirejs documentation.
http://requirejs.org/docs/api.html#modulename

These are normally generated by the optimization tool. You can explicitly name modules yourself,
but it makes the modules less portable -- if you move the file to another directory you will need to
change the name. It is normally best to avoid coding in a name for the module and just let the
optimization tool burn in the module names. The optimization tool needs to add the names so that
more than one module can be bundled in a file, to allow for faster loading in the browser.

That issue of portability means that if someone moves a file and forgets to change the name to match, or makes a typo in the name, then the module will not be loadable.  Essentially you are taking the single source of truth for module names, being the file structure, away and replacing it with a less reliable and less obvious source of truth.
As for using ASP.NET MVC bundling, I'm struggling to see why you would do this.  ASP.NET is a server-side language and Durandal is a client-side framework.  There is an argument for keeping the tooling consistent across projects, but I think a better argument is "use the best tool for the job".  In the case of packaging a Durandal application, that best tool is the r.js optimizer, not a server-side bundling pipeline.  That's just my opinion though, possibly what I'm saying doesn't make sense in some circumstance I haven't considered.

The use case for moving the files will be a very rare one, if at all. If you move the file manually, then you will be taking it outside of whatever package loader you have anyway. Which would break a Single Source of Truth principle. Another Faux Pas on the SSoTruth is that we have to configure Require Js to know where the Durandal folder is.
Adding your own funky folder structure for Durandal would also break the existing references in the Durandal files, which would then have to manually change the Durandal modules to know what the new names of the files were.
For Durandal, I would of thought a lot of the take up of it has come from .NET developers, and making it easy for them to use Durandal with existing projects would be beneficial to all of us.
On using the 'best tool for the job', the argument is based on circumstance and opinon. Adding additional tools to build mix, is perhaps what many don't want or need. It feels like swallowing a Cat to catch a Bird, when the real solution was to not swallow the fly in the first place. ;-P
I guess you have to weigh up the pro's and cons, but I haven't yet seen a con, apart from the recommendation in the RequireJs docs.
The pro's of it working with existing bundling methods, without having to add a client side build method (which is no small effort for someone who has not done it before, or working with anything legacy), and making it easier for a potentially large audience, out weigh the con IMO.

It feels like swallowing a Cat to catch a Bird, when the real solution was to not swallow the fly in the first place. ;-P

You've made my morning

@marvc1 To be clear, I meant that the explicit module id would be one more thing for the maintainers of Durandal to remember to update, if they ever move or add a file in some future version.  They currently do not need to update this because the module id is derived automatically from the file path by r.js.  I wasn't suggesting someone using Durandal would move any files themselves.
Personally it won't affect me if this recommendation is adopted, as long as the explicit module ids match the current, generated ones.  I just saw this extra overhead and possible error as a potential negative worth mentioning; at the least, this is probably the reason why the modules are not explicitly named already.

Closing since Durandal has been superseded by Aurelia just shy of four years ago.


Individual fields whitelisting option added.

Replaces #300

Additionally, the tests are failing with PHP 5.6.

PHPCS violation fixed

Ok fixed.


BUG: The bLuna price is missing the price up/down indicator

go to Kallisto.finance and look that the bLuna price
Expected:
Underneath the price, I should see how much the price went up or down.
Actual:
I only see the price

@wdev733 fYI this is still an issue. Though I have seen it sometimes (mostly not). I'm not sure when/why it shows up.


Whisper's Reflection does not seem to like long strings or something?

Whisper machine broke

Expected behavior
the chat parser should:

take my message
strip the first occurrence of my Sifter's prefix
and make a string Iota with it

Actual behavior
With long strings (or some other trigger, not sure yet), it seemingly duplicates + concatenates the result of step 1.
Reproduction steps
I'm not sure what the MINIMUM reproduction steps are, but so far this has been consistent:

Set a sifter's prefix to ">>>"
send ">>>Room 0x7203cea5 Twisted_Codes would-be quencher" in chat. Maybe play around with it's length or something
Draw "whisper's reflection"
bug occurs.

Additional information
of note, when I tested my reproduction steps, I noticed that it seems to add "#" before "Twisted_Codes", even though, for testing purposes, my string no longer has a "#". "Reveal" posted the following messages to chat (note that I also tried removing my nickname on the server since the nickname display begins with a hash mark)
[09:37:39] [Render thread/INFO]: [CHAT] "Room 0x7203cea5 Twisted_Codes would-be quencher>>>Room 0x7203cea5 #Twisted_Codes would-be quencher"
[09:38:11] [Render thread/INFO]: [CHAT] Your nickname has been removed!
[09:38:21] [Render thread/INFO]: [CHAT] "Room 0x7203cea5 Twisted_Codes would-be quencher>>>Room 0x7203cea5 #Twisted_Codes would-be quencher"

speaking of which, here's the full log file. I'm sure you'll find it forgive the Hex Casting pun enlightening:
latest.log

Minimum string to cause it seems to be my Minecraft screen name?

Trying to figure out how this bug happens for myself (it seems like it's probably simple enough I could PR it, or so I was hoping) I looked at OpChatString and... I don't see anything wrong there, but I also don't see the part where it's supposed to strip the prefix. Where is that part of the logic defined?


Corrected time zone for CAD last updated

Assuming europe is always Europe/Berlin we will need to add logic to handle this.

fixed with latest commit, please test and share results

Confirmed it works.   However set temp reports 16.5 - no way my wife has it set to that. I will dig in.


Update changelog for version 0.7.0

Waiting on https://github.com/trustlines-protocol/relay/pull/301 before releasing version 0.7.0
(feel free to modify).

Codecov Report

Merging #302 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #302   +/-   ##
=======================================
  Coverage   64.34%   64.34%
=======================================
  Files          48       48
  Lines        3200     3200
=======================================
  Hits         2059     2059
  Misses       1141     1141

Continue to review full report at Codecov.

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


Bring back the UwU logo

Documentation is

[X] Missing
[ ] Outdated
[ ] Confusing
[ ] Not sure?

Explain in Detail
The old landing page checked for an uwu route query, and then replaced the Vite logo with an UwU logo.
It seems like the redesigned landing page don't check for the uwu query anymore, which is quite disappointing.
Your Suggestion for Changes
Check for the uwu query and replace the Vite logo in the hero diagram with the UwU logo
Reproduction
No response
Steps to reproduce
No response

@DubNubz I like the idea, would you send us a PR?

Closed by #18924


Can we display the FlexibleHeightBar when user just scroll up, not until to the top?

Can we start to display the FlexibleHeightBar when user just scroll down, not until to the top? Ideally, when user scrolls down, the height bar will continue to shrink and disappear, and whenever an user start to scroll up, it will trigger the height bar to start expand based on offset(progress), not until user scroll up to top.

I think the behavior you're describing can be found in FacebookStyleBehaviorDefiner. Let me know if that works for you.

Nice! I was looking at cash and forgot the facebook style. Another request is, if I choose this facebook style, can I have a view toggle to top? e.g. in your demo, there is a three column blank view under search bar, I want this blank view stick to top no matter where user scrolls. Can we do that?

Sure! That will be configured when you apply layout attributes to your bar's subviews. My Facebook demo configures that subview to slide up and disappear before the rest of the bar, but you can make it look however you'd like.
I'm going to close this since it sounds like your original issue is resolved.

Could you give the attribute names so I can take a look at it?

I think that https://github.com/bryankeller/BLKFlexibleHeightBar#configuring-subviews will help you. Notice how the UILabel moves up and down with the bar.
If you can figure out where you want your "pinned" view to be at progress == 0.0 and where you want it to be at progress == 1.0, then you can make it look like it's pinned. If you only have a full size and a min size state for your bar, then this can be accomplished with only 2 layout attribute definitions added to your pinned view.

I am trying to write a prototype, could you specify what are the two layout attributes?

I kind of figured out what you mean by 2 layout attribute.
It should be the initial layout and final layout attributes you are talking about.


Only render when a key is down or during zooming

Currently rendering happens on every mouse move.

Done!


version 13.0.0 rn 0.69.4 component property change not working

react-native-svg 13.0.0, react-native 0.69.4 component property change not working
Bug
<Star
	fill={isFavorited}
	color={isFavorited ? 'red' : theme.colorText}
/>

Temporary Fix
use different key
{ isFavorited ? <Star
	key="unfavorite"
	fill={isFavorited}
	color={'red'}
/> : <Star
	key="favorite"
	fill={isFavorited}
	color={theme.colorText}
/> }

Environment info
 System:
    OS: macOS 12.0.1
    CPU: (4) x64 Intel(R) Core(TM) i7-7Y75 CPU @ 1.30GHz
    Memory: 1.44 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.8.0 - /usr/local/bin/node
    Yarn: 1.22.5 - ~/.yarn/bin/yarn
    npm: 8.13.0 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK: Not Found
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: /undefined - /usr/bin/xcodebuild
  Languages:
    Java: <IP_ADDRESS> - /usr/local/opt/openjdk@11/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.0.0 => 18.0.0
    react-native: 0.69.4 => 0.69.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

I have the same problem, tnx for the temp fix @linjdev

Could one of you share how you manually linked the project for android use on 0.69 please?
https://github.com/react-native-svg/react-native-svg/issues/1839

@nextriot nothing todo. just use latest version react-native and react-native-svg and enable newarch.

@linjdev on what platforms does the bug appear? @nextriot I will try and make a guide how to do it.

@WoLewicki Android 12 LineageOS 19 Nexus 5X, not enabled newarch. clean project.

setNativeProps don't work in react-native-svg 13.0.0
Is it related issue or need to create new one?
<Circle
  r={4}
  fill="#000000"
  opacity={0}
  ref={ref}
/>

ref.current?.setNativeProps({ opacity: 1 });

@Bardiamist  setNativeProps is not available on Fabric, or do you mean that it stopped working on old architecture?

@linjdev @kneza23 could you check if applying #1843 resolves the problem?

@Bardiamist setNativeProps is not available on Fabric, or do you mean that it stopped working on old architecture?

stopped working on old architecture

@Bardiamist I checked it and it is caused by the same issue as the one fixed in #1843, it should work fine for you after applying the change. Could you check it?

@Bardiamist I checked it and it is caused by the same issue as the one fixed in #1843, it should work fine for you after applying the change. Could you check it?

I tried
"react-native-svg": "git+https://github.com/react-native-svg/react-native-svg#@wolewicki/fix-android-components-not-updating"

Looks good

Unfortunatelly I still see problems should be related with layout invalidation on Android on old architecture. 13.1.0 works better than 13.0.0 but broke after some layout changes. No problems on iOS. I'll wait some time or will try to create repo with example.

@Bardiamist please create a repro so we can work on it 🚀

@WoLewicki ok, I created https://github.com/react-native-svg/react-native-svg/issues/1859


Smart retry mechanism

Currently there is a default retry mechanism to retry up to 5 times if upstash returns an error.
That kind of works but is also quite wasteful. For example if an authentication error is returned there is no point in trying again.
I would categorize errors in two categories, retryable and non retryable ones.
For example:
Retryable:

partition rebalancing

Non retryable

Authentication
wrong consumerGroupId or instanceId when trying to delete a consumer group.

bump


Remove d.ts from your import paths!

Check that this is really a bug

[X] I confirm

Reproduction link
not necessary or not possible
Bug description
TypeScript is used incorrectly. The build fails.
TS2691: An import path cannot end with a '.d.ts' extension.

You can simply fix this by removing all d.ts suffix from path string.
Before 👎
import type Swiper from './swiper-class.d.ts';

After 👍
import type Swiper from './swiper-class';

(tested)
Othwesie it's not possible to use it in TypeScript anymore. It's a blocker. Workaround: Use previous versions like 9.
Affected files:

node_modules/swiper/types/swiper-options.d.ts
node_modules/swiper/types/swiper-events.d.ts
node_modules/swiper/types/swiper-class.d.ts
node_modules/swiper/types/modules/zoom.d.ts
node_modules/swiper/types/modules/thumbs.d.ts
node_modules/swiper/types/modules/scrollbar.d.ts
node_modules/swiper/types/modules/pagination.d.ts
node_modules/swiper/types/modules/navigation.d.ts
node_modules/swiper/types/modules/mousewheel.d.ts
node_modules/swiper/types/modules/keyboard.d.ts
node_modules/swiper/types/modules/hash-navigation.d.ts
node_modules/swiper/types/modules/controller.d.ts
node_modules/swiper/types/modules/autoplay.d.ts
All of your type files.

Expected Behavior
No errors during compiling.
Actual Behavior
The build fails due to incorrect use of typescript.
Swiper version
10.2.0
Platform/Target and Browser Versions
Win 10
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Or update to latest TS v5

@nolimits4web Can you please explain why you insist on the file extensions when importing? I see no problems or disadvantages. Removing the d.ts suffix is better in any way.

Same issue. Cannot be used in latest Angular v 17 with TypeScript v 5.3.3.
swiper@11.1.2/node_modules/swiper/types/shared.d.ts:1:24 - error TS2846: A declaration file cannot be imported without 'import type'. Did you mean to import an implementation file './index.js' instead?
@nolimits4web will you provide any solution?


It can't build to wasm

When I use this dependency in my wasm project, it will report error when compiling:
error: the wasm32-unknown-unknown target is not supported by default, you may need to enable the "js" feature. For more information see: https://docs.rs/getrandom/#webassembly-support
   --> /Users/xxx/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.7/src/lib.rs:235:9
    |
235 | /         compile_error!("the wasm32-unknown-unknown target is not supported by \
236 | |                         default, you may need to enable the \"js\" feature. \
237 | |                         For more information see: \
238 | |                         https://docs.rs/getrandom/#webassembly-support");
    | |________________________________________________________________________^

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
   --> /Users/xxx/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.7/src/lib.rs:262:5
    |
262 |     imp::getrandom_inner(dest)
    |     ^^^ use of undeclared crate or module `imp`

error: failed to run custom build command for `gmp-mpfr-sys v1.4.10`

Caused by:
  process didn't exit successfully: `/Users/xxx/workspace/github-aewc/infinity-swap/evm-canister/target/release/build/gmp-mpfr-sys-d8a467da99dcac09/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'Cross compilation from aarch64-apple-darwin to wasm32-unknown-unknown not supported! Use the `force-cross` feature to cross compile anyway.', /Users/xxx/.cargo/registry/src/github.com-1ecc6299db9ec823/gmp-mpfr-sys-1.4.10/build.rs:111:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
For more information about this error, try `rustc --explain E0433`.
error: could not compile `getrandom` due to 2 previous errors

is there any features that without using the getrandom?

Same.

You need to add getrandom with the feature flag of JS. This is not libsecp256k1, but its dependency rand which depends on getrandom.
https://docs.rs/getrandom/latest/getrandom/#webassembly-support
getrandom = { version = "0.2", features = ["js"]}

docs.rs/getrandom/latest/getrandom/#webassembly-support

But I don't depend on getrandom directly. This reports from the libsecp256k1.


julia.ipynb doesn't run in Binder

PyPlot package isn't installed
https://hub.mybinder.org/user/binder-examples-i-language-demo-ah2jl97h/notebooks/julia.ipynb#

Fixed by #4

@jamesmyatt thanks for catching this!


added a snapcraft for QOwnNotes

added a snapcraft for QOwnNotes, the plain-text file notepad with markdown support and ownCloud integration (http://www.qownnotes.org/)

This change is

Nice work, can you add QOwnNotes to the top-level README.md of the Snappy Playpen repo too?

Comments from Reviewable

qownnotes/README.md, line 19 [r1] (raw file):

You can also visit [QOwnNotes on GitHub](https://github.com/pbek/QOwnNotes).

Are all the features working in the snapped version?

Comments from Reviewable

@dholbach: I now added qownnotes to the readme. And yes, all features are working, but of course the snapped application has no access to a note directory the user's home directory. Is there a way to access the home directory too?

Yes, use the homeplug.

Comments from Reviewable

qownnotes/snapcraft.yaml, line 18 [r2] (raw file):

      - network
      - network-bind

Add the home plug here.

Comments from Reviewable

home works perfectly, thanks a lot @dholbach

Comments from Reviewable

Reviewed 4 of 4 files at r1, 1 of 1 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Do you think it'd make sense to also add the snapcraft.yaml file to the QOwnNotes repository?

To which repository? I already have it here to create snaps: https://github.com/pbek/QOwnNotes/tree/develop/build-systems/snap/snapcraft

Nice work, you're always one step ahead! :-)

And I'm waiting until https://code.launchpad.net/~pbek/+snap/qownnotes finally works (Launchpad needs to update snapd). And I have a snap published at https://myapps.developer.ubuntu.com

Fantastic! :-)

Although I don't know if/when I'm supposed to find it at https://apps.ubuntu.com/cat/search/?q=qownnotes&op=...

On apps.ubuntu.com you can't find snaps, it's only for the .deb packages contained in Ubuntu itself.


removed the pointless 'purchased'

(at least I tried lmao)

This issue has already been fixed. Closing PR.


change title

not an actual issue but a suggestion which ur free to leave or take: maybe something like BetterChatGPT-Plus would be better (tho kinda wordy) b.c. VIsion is only one of the epic new features youve add1ed. i love this thing so much tho. i did notice some slowdown with gpt-4o-mini but that might be gpts servers

Done! Thanks for the suggestion.


Create game rules for all enchantments

Customization is king. Would be pretty neat if you could disable any enchantment from appearing in the table. If added, a category in the game rules page in world gen would also be needed to avoid overwhelming players.

Perhaps a config that lets user select which game rules actually appear as well? May be overwhelming having so many game rules otherwise...


ublox6: Add most popular baud rates to GPS param constants

Adds the most common baud rates (2400, 4800, 19200, & 38400) to the GPS param constants, since this is needed to use any GPS with a baud rate other than B9600, which previously was the only allowed value.

Merged, thank you for expanding these!


Inline formatting not working

Bold and Italic Formatting are not working, but the rest are working fine and also the html output is correct
Please help. Thanks!

Please post a detailed, context-sensitive code

Sorry, I just noticed it now, I think my setup is the one that has an issue it doesn't display any html inline formatting. I'm gonna close this issue now. Anyway, Thanks for the reply :)


"ImportError: No module named tf_transformations" in turtle_tf2_py for ros2 galactic

tf.transformations I think is in the process of being migrated for ros2, but currently the documentation is unclear about what is going on. On top of installing pip3 install transforms3d you also have to manually install https://github.com/DLu/tf_transformations (couldn't find it on pip). I don't know if the documentation should be updated, or what the plan is with this.

Should rosdep install have worked? I thought I did that, but might be mistaken. Thanks.

@kobbled yes, the rosdep should resolve that dependence, but it is mentioned in further tutorials. I think we could add a command to install tf_transformation in https://docs.ros.org/en/rolling/Tutorials/Tf2/Introduction-To-Tf2.html#installing-the-demo. Is that the place you were stuck?

yes that is where I got stuck. pip3 install transforms3d. This line confused me, as when the second turtle didnt follow the first I thought it had to do with this package, but this package is not tf-transforms, and sent me down the rabbit hole of the differences in quaternion ordering. Adding sudo apt-get install ros-<ros_distro>-tf-transformations below the pip command might have avoided the detour for me.

Thanks for the feedback, I will make corresponding updates to the tutorial page.


Feedback for new documentation

Guys,
Thanks for creating new documentations, but I really miss one thing from the previous documentation. There was complete line of code for every command like php artisan module:migrate blog. It was very helpful in copy & paste, change one parameter and done. Very quick and easy.
Consider it if it makes sense.
Thanks

Hello,
Thanks for the feedback. I will add back a module name as an example argument asap.

I added those back. https://nwidart.com/laravel-modules/v1/advanced-tools/artisan-commands

Made few changes https://github.com/nWidart/nwidart-docs/compare/master...webreinvent:patch-1

Wasn't this what you requested ?

look at https://vgy.me/nPAEGg.png you'll get it

Those are now here: https://nwidart.com/laravel-modules/v1/basic-usage/creating-a-module

Feel free to send a pull request to the docs if I missed some 👍

I added the php artisan suffix to all commands.


refactor: Refactored codebase for supporting both ES6 and ES7

What does this do / why do we need it?
Handles multiple versions of ES
What should your reviewer look out for in this PR?
New client and function definition
Do you need help or clarification on anything?
No
Which issue(s) does this PR fix?

closed in favor of #51 which is already merged.


Update basic actions workflow example so it does not fail

In the basic GitHub actions workflow example, install and run bats locally instead of globally.

Why:
When I was following the example provided by the docs, my workflow run would fail:
Run npm install -g bats
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/local/share/man/man7
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/usr/local/share/man/man[7](https://github.com/Plsr/actions-test/actions/runs/8700605027/job/23861082814#step:4:8)'
npm ERR!  [Error: EACCES: permission denied, mkdir '/usr/local/share/man/man7'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: '/usr/local/share/man/man7'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user

For reference, this is my failed run and the matching workflow file.
This isn't a great experience for first-time learners.
What's being changed (if available, include any code snippets, screenshots, or gifs):
The proposed solution to this is not installing bats globally:
jobs:
  check-bats-version:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node_version: '20'
      - run: npm install bats
      - run: ./node_modules/bats/bin/bats -v

(Successful workflow, for reference)

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

- [ ] For content changes, I have completed the self-review checklist.

@Plsr Thanks so much for opening a PR! I'll get this triaged for review ✨

Hi @Plsr! Thank you for contribution ⭐ After reviewing the workflow and testing the example, we have decided that this may be an individual permissions error. We will close the issue with no further actions. Our goal is to ensure the examples are simple and straightforward for everyone to use. Thank you for understanding and being a valued part of our community.


FLASH Chip Interface

Create an interface for the FLASH that uses QSPI and can perform the following:

Read and Write certain bits of the Status Registers   (Write Enable, Write Disable, BUSY Flag, Quad Enable)
Status Poll the BUSY Flag in Status Register 2
Write up to a Page's worth of data at a specific Page address (use DMA if data length > 32)
Read from any random address, up to 4KB of data (use DMA if data length > 32)
Send the Instruction to erase a specific Sector (chunk of 2 pages)

For Page writing, write a function that translates from Page Numbers to Physical Addresses. The User will ask to write to some page number, and the function will write to the appropriate address.
Use a similar logic for defining Sectors as well.

Closed as a better scoped issue is to be created


Added RIN Ether asset to asset-table

Overview
This adds the Rinkeby Ether asset to the asset-table. This allows for glow users to select the RIN Ether asset when using the Rinkeby shared test network
This is to address https://github.com/Glow-Lang/glow/issues/438

Actually, we probably want to add an asset for every known network, so we also work on the other ones.

These new commits should add the nativeCurrency of every network in ethereum-networks to asset-table


Fix timezone handling in timesince_last_update

Ref: https://github.com/wagtail/wagtail/pull/11815/files#r1556095493
test_group_edit was failing when run after 3pm UTC, due to the output being rendered as "Just now" instead of an explicit time. This was due to a previously unsurfaced logic error in the timesince_last_update tag: if the timestamp was passed as a timezone-aware datetime in UTC, it was failing to translate this to local time and thus it compared as a different date, even if it was only from a moment ago. Consequently, it was following the "X days ago" path that was only supposed to be used for timestamps before today.
With this fixed, the special-case for "Just now" can be removed since it won't come into play for timestamps of yesterday and earlier. (Well, technically it could in the first minute after midnight, but that really doesn't warrant a special case...)

Now updated to work with USE_TZ = False. This makes things a bit messy - especially the need to provide alternative tests - but given that we can't really guarantee full correctness when timezone support is disabled, the only real standard of success we have in that case is "it doesn't blow up completely" :-)


cmd/scollector: Add additional Linux interfaces

ppp+
tun+
tap+

IIRC these are all virtual interfaces for vpn? If that is the case I think
we should put this all under a different metric namespace like we do with
bonds
On Jul 1, 2015 7:50 AM, "Peter Fern"<EMAIL_ADDRESS>wrote:

ppp+
tun+
tap+

You can view, comment on, or merge this pull request online at:
https://github.com/bosun-monitor/bosun/pull/1124
Commit Summary

Add additional Linux interface names

File Changes

M cmd/scollector/collectors/ifstat_linux.go
https://github.com/bosun-monitor/bosun/pull/1124/files#diff-0 (3)

Patch Links:

https://github.com/bosun-monitor/bosun/pull/1124.patch
https://github.com/bosun-monitor/bosun/pull/1124.diff

—
Reply to this email directly or view it on GitHub
https://github.com/bosun-monitor/bosun/pull/1124.

tun and tap devices are commonly used for VPN or other tunnels/virtual interfaces, ppp is point-to-point, commonly used for dialup and *DSL connections, frequently used as WAN for satellite offices.  Recommendations?

@pdf Two main things I'm thinking:

We don't want to double count bytes under the metric, or else aggregation will get messed up (i.e. give me the total network traffic for this host)
I think we should keep any non-physical traffic out of os.net.bytes and have a different name space for it. So interfaces should correspond to actual hardware (or at least what the OS believes is actual hardware, i.e. VMWare may provide a virtual NIC, but the OS mostly considers it "real").

Wonder if people agree with me...?

@kylebrandt: I was initially leaning toward using the same namespace for all interfaces, but your arguments made me think it's better to keep them in different namespaces. I'm not sure about ppp interfaces though, because traffic may run over a serial line (i.e., actually a different interface)

@vitorboschi Maybe sys or proc provides a way to distinguish between hardware vs non-hardware ppp devices?

Maybe checking /sys/class/net//type, but I don't have any ppp device here to test

@vitorboschi unfortunately there's no distinction (types are in the kernel include/uapi/linux/if_arp.h).
@kylebrandt shall we just put all these other interfaces under a virtual or other namespace? I also really wonder if the regex whitelist is the right approach.  You can name interfaces anything, and people may want accounting on other virtual interfaces like bridges, VM backing interfaces, etc.  We're also missing wlan, maybe other items that may appear on routers, etc.
Perhaps we should include all devices by default and look at sysfs to determine type based on the contents of type, followed by the presence of bonding/bridge/tun_flags/etc nodes.  This should let us make pretty decent decisions, though we might miss some more esoteric devices that may get mis-classified as 'physical'.

I'm okay with putting them under *.net.virtual. - makes sense to me. I'm not that concerned about the method we use, but I think I like the "don't include" default for interfaces prevents a lot of crap from showing up and is important (in particular with opentsdb where deletion isn't so much of a thing). That and nobody has ever said they needed support for custom interface names yet.

@kylebrandt if not all interfaces are included by default, I think included interfaces need to be configurable.

AFAIK physical interfaces link to real devices in, e.g.
ls -lh /sys/class/net
total 0
lrwxrwxrwx 1 root root 0 Jul  1 23:32 docker0 -> ../../devices/virtual/net/docker0
lrwxrwxrwx 1 root root 0 Jul  1 23:32 eth0 -> ../../devices/pci0000:00/0000:00:19.0/net/eth0
lrwxrwxrwx 1 root root 0 Jul  1 23:32 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx 1 root root 0 Jul  2 00:40 tun0 -> ../../devices/virtual/net/tun0
lrwxrwxrwx 1 root root 0 Jul  1 23:32 wlan0 -> ../../devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0

Here's a first pass, collecting all interfaces by default, categorizing based on type and then /virtual/ device path, and finally bonding for backwards compatibility.
I don't have any teamed interfaces configured, I'll set one up later and make sure that gets tagged as bond. like bonding interfaces do.
If we're sure we don't want to collect all interfaces, I'll add logic to omit virtual devices by default, and allow configuration of which interfaces to include.

Looks like team devices don't expose anything to identify them via sysfs, so I've fallen back to a regex match for them.  Considering team interface names are completely arbitrary that's not reliable, but no worse off than the previous code.
Also, FYI, interface names will likely change for many distros shipping full systemd: https://wiki.freedesktop.org/www/Software/systemd/PredictableNetworkInterfaceNames/
This has already occurred in some distros, making them incompatible with current scollector.

What's needed to move forward on this one?

@pdf sorry I'll test this on a few machines today, thanks for the ping

@captncraig Can you advise why the build is failing here? I would like to get a clean build so I can do some testing and get this merged - @pdf has been pretty patient on this one

This might be from when esc was borked. If you git commit --amend and then force push, you can re-run the build and my guess is it will pass

Passing now.


Mark request bodies as required, closes #1280

Thank you! Could you please add a test to validate that the property is not set when we use emptyRequest?

@julienrf this is already tested
emptyRequest does not create a requestBody

Thank you again @OlegYch, I’ve just released version 1.12.0 of endpoints4s with your changes.


HHH-13840 & HHH-12772 - Issues in @LazyToOne + @OneToOne properties

This fixing repair bugs : HHH-13840 & HHH-12772
I know I should supply a fixing also in javassist & bytebuddy.
but I started with javassist, and waiting to see that the fixing is acceptable.
Once it will be approved - I will supply a fixing also for bytebuddy.
@vladmihalcea ,I will appreciate your attention.

Summary of the fixing:
in the setter itself - we check if this property is lazy and not fetched yet,  and the new value = null

if so call the getter method - to fetch the property from DB.

I no longer work for Red Hat, so one of the Hibernate devs should better review it.

Could you add the test case provided with the original issue? Being able to step through the two variants of the code definitely helps with reviewing :)
https://github.com/chouze/hibernate-test-case-templates/commit/12e43bcba3f9d4e22a3e068e7b99581a9fb0a45b

@jwgmeligmeyling
Attach test case for both HHH-13840 & HHH-12772.
tests-HHH-13840 & HHH-12772.zip

Pay attention that in past there was code in AttributeTypeDescriptor#buildInLineDirtyCheckingBodyFragment that check if the new value = null , in this case - the property tracked . but the null checking was removed in this commit: https://github.com/Agoldstein1/hibernate-orm/commit/1c70e0df0cbf671bc885d0c3ca369fbc2e5a004c

@NathanQingyangXu , my change may cause LazyLoadingException to be thrown from the setter method - in case the object is detach.
is it acceptable?

I am community contributor who is mainly focused on code quality. Other
guys especially team members know much better than me on the business
logic. You can request review from them.
On Mon., Feb. 17, 2020, 03:13 Ayala Goldstein<EMAIL_ADDRESS>wrote:

@NathanQingyangXu https://github.com/NathanQingyangXu , my change may
cause LazyLoadingException to be thrown from the setter method - in case
the object is detach.
is it acceptable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-orm/pull/3240?email_source=notifications&email_token=AB6UYAUPD35Q2KFDPY7KL5TRDJBJRA5CNFSM4KWA3XCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL5OCTY#issuecomment-586867023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6UYAQETB57R7MYH3MWECLRDJBJRANCNFSM4KWA3XCA
.

also, you need to ensure the building succeeds before other guys' review.

@NathanQingyangXu
thanks,
Can you help me please to find the root cause of the failed building ?
in intellij I run build task by gradle to hibernate-core project and it finished successfully.
Your assistance will be appreciated!

@NathanQingyangXu
thanks,
Can you help me please to find the root cause of the failed building ?
in intellij I run build task by gradle to hibernate-core project and it finished successfully.
Your assistance will be appreciated!

It seems some building infrastructure issue (I encountered also last weekend). Maybe you can ask some quesiton on https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev? Everybody is there. I am sure @Sanne would have great interest on your PR.

I left a message there for you. You can also require @Sanne to review your PR after building issue is resolved. He recently fixed many similar issues, to my knowledge.

@jwgmeligmeyling
Attach test case for both HHH-13840 & HHH-12772.
tests-HHH-13840 & HHH-12772.zip

If I were not mistaken, I thought his intention is to require you add testing case to the commit. Without testing case endorsement, there is little odds for the PR to be reviewed.

Test case should be committed in the same PR. Without testing case, team
member won't be able to verify the correctness easily. You can refer to the
testing cases in the ongoing PRs or merged ones.
On Thu., Feb. 20, 2020, 06:04 Ayala Goldstein<EMAIL_ADDRESS>wrote:

@jwgmeligmeyling https://github.com/jwgmeligmeyling
Attach test case for both HHH-13840 & HHH-12772.
tests-HHH-13840 & HHH-12772.zip
https://github.com/hibernate/hibernate-orm/files/4209646/tests-HHH-13840.HHH-12772.zip
If I were not mistaken, I thought his intention is to require you add
testing case to the commit. Without testing case endorsement, there is
little odds for the PR to be reviewed.
Is The test case should be committed in hibernate project, or attaching a
separated project to the PR with the test case is good enough?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-orm/pull/3240?email_source=notifications&email_token=AB6UYARK7BKLGUFKEDWP2OTRDZPU3A5CNFSM4KWA3XCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMNOFEA#issuecomment-588964496,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6UYAQ3ZENCOSPGNMNIYNDRDZPU3ANCNFSM4KWA3XCA
.

I am sure he will require testing case, :)
On Thu., Feb. 20, 2020, 06:11 Ayala Goldstein<EMAIL_ADDRESS>wrote:

@Sanne https://github.com/Sanne
I will be glad if you can review this PR.
thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-orm/pull/3240?email_source=notifications&email_token=AB6UYAXO5NOMASIPBFPWGO3RDZQPDA5CNFSM4KWA3XCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMNOZ6I#issuecomment-588967161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6UYAWOSDXIHAP7D7YL4J3RDZQPDANCNFSM4KWA3XCA
.

I am sure he will require testing case, :)
…
On Thu., Feb. 20, 2020, 06:11 Ayala Goldstein, @.***> wrote: @Sanne https://github.com/Sanne I will be glad if you can review this PR. thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3240?email_source=notifications&email_token=AB6UYAXO5NOMASIPBFPWGO3RDZQPDA5CNFSM4KWA3XCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMNOZ6I#issuecomment-588967161>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6UYAWOSDXIHAP7D7YL4J3RDZQPDANCNFSM4KWA3XCA .

OK, I am going to add test case. thanks.

hi @Agoldstein1 , yes please, if you could integrate the test within the ORM code base as part of this pull request that would be very helpful. Let me know when you've done that, we'll have a look then. Sorry for the delay!

@NathanQingyangXu , my change may cause LazyLoadingException to be thrown from the setter method - in case the object is detach.
is it acceptable?

I am pretty sure @Sanne will guide you on this

Hi @Sanne ,
I committed unit tests both for HHH-13840 & HHH-12772 issues.
pay attention that if you run the tests by the default byte code enhancement - Bytebuddy* - the tests will fail, since I supply a fixing currently only for Javaassist.
so please change the bytecode provider to run with javaassist.
thanks.

@Sanne
It will be great if you could review my commit.
thanks.

great work @Agoldstein1
I'll be happy to get this merge request merged as this issue is a showstopper to move from the old runtime reflection to class enhancement..
Is there anyone in the hibernate team that can review the MR?
@Sanne can you please take a look at this?
Thank you in advance

@Sanne Hi, Thank you for your great work on Hibernate.
Can you please take a look at this PR?
Ayala added the required tests and all is green.
Is there a way this PR is merged to 5.4.x?
This issue is for my company a blocker to move to from copy based heavy dirty checking mechanism to byte code enhancement...
Thanks you in advance. :-)

The @LazyToOne annotation was removed, and I have closed the referenced issues.


Quest mods

Would be great if the mods worked on quest, there are ways to do it (BMBF), and I think melonloader works on it

BMBF does it a separate way using C++, I was looking into this however I never managed to successfully generate any headers or codegens to interact with the game. Melonloader's android support has slowed down and it was made a separate project called Lemon (I believe). I tried using that however it was very difficult and I never got it to work.

Yep ATXL is right, melon loader did develop android support but I also never got it to work.
What you could do however is use sidequest and run bricksVR on steam onto your quest. That way you only have to mod the steam version.

Late update:
The melonloader dev team did fix support for lemonloader and I think it should be better and easier to use, although I have not tried using it.


读取模型pkl文件出现错误

_pickle.UnpicklingError: A load persistent id instruction was encountered,
but no persistent_load function was specified.

读取的是imagenet上的预训练模型


LCFS - Transfer is categorized upon director recording

Description:
The system categorizes the transfer upon director recording (i.e., approval).
From the date on which the written agreement to transfer credits was reached between the two organizations (a user input) and the date the director records the transfer, the transfer will fall under one of 3 categories:

Category A: The agreement to transfer was reached within the last 6 months.
Category B: The agreement to transfer was reached between 6 months to 1 year ago.
Category C: The agreement to transfer was reached more than 1 year ago.

Category D: There is also a Category D checkbox override. This is based on the analyst or director selecting a checkbox which will override the Category A-C date calculation. This functionality is handled in another card: https://app.zenhub.com/workspaces/low-carbon-fuel-standard-644c2db3be098a001977ad0b/issues/gh/bcgov/lcfs/257
Upon director recording a transfer, the predictive language for the categorization in the transaction history section should be replaced with the final category. The predictive language is developed in a different card (#258). See wireframe for mockup of final category.
Wireframe: https://preview.uxpin.com/59145260c7d8cc48969ac79401cc03d84843c3d9#/pages/165112777/simulate/no-panels
Purpose and benefit to user:
Categorizing transfers is used to provide more accurate market pricing information to stakeholders. As transfer agreements can be negotiated at different times (recently vs. months ago vs. years ago), the reported price may not reflect current market prices. Transfers that are negotiated months or years ago are separated out from more recent transfers to better represent market prices over time. Market data is posted in a spreadsheet at the bottom of our Credit Market page: https://www2.gov.bc.ca/gov/content/industry/electricity-alternative-energy/transportation-energies/renewable-low-carbon-fuels/credits-market
Acceptance Criteria:

Given I am a director or analyst, When I record a transfer, Then the transfer should be automatically categorized into Category A, B, or C based on the date the agreement was reached, or Category D if the override checkbox is selected.

Given I am a user viewing the transaction history, When a transfer has been recorded by the director, Then the predictive language indicating the expected category should be replaced with the final category (A, B, C, or D).

Given I am a user accessing the Credit Market page, When I view the market data spreadsheet, Then I should see the transfers categorized appropriately, reflecting accurate market pricing information over time.

Development Checklist:

[ ] Implement logic to categorize transfers into Categories A, B, or C based on the date difference between the current date and the date the transfer agreement was reached.
[ ] Review the TFRS codebase related to this categorization. The logic will be pretty much a copy over.
[ ] Add functionality for a Category D override, which can be selected by an analyst or director, bypassing the date-based categorization.
[ ] Ensure that once a transfer is recorded, the predictive language in the transaction history is updated to show the final category (A, B, C, or D).
[ ] Update the Credit Market page's spreadsheet to display transfers with their respective categories, ensuring accurate representation of market data over time.
[ ] Conduct thorough testing to ensure that the categorization works correctly in all scenarios, including edge cases.
[ ] Implement necessary UI updates as per the wireframe to reflect these changes in categorization and display.
[ ] Ensure proper documentation and comments are added to the code for future maintainability.

Notes:

The override functionality (Category D) should be clearly documented and restricted to authorized personnel only to prevent misuse.

Hey team! Please add your planning poker estimate with Zenhub @hamed-valiollahi @kevin-hashimoto @prv-proton


build: update bazel common test target

other errors seem different than bazel. I'll have to take a look a little later. the CI is passing for   bazel windows though! 😅

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (231ff77) to head (895d463).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##               wip     #1124   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          153       153
  Lines        25464     25464
=========================================
  Hits         25464     25464

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

Oh, I see. I'll change something here but it's ok. Thanks! 👍


Is Wiki "Source Code Organization" outdated?

Noticed that optional decorator has been removed in main branch.

However, there are still an introduction about optional decorator in this Wiki.

I'm confused about this. Is the wiki outdated?

Fixed that today


YOLOv5 version 6 support for ByteTrack

Added support for YOLOv5 tiny and nano models to Bytetrack.
Many thanks to @ifzhang and @gmt710 for their work on ByteTrack and YOLOv5 implementation.

Fantastic!


solr-operator image not found 0.1.1

Describe the bug
In config/operators/solr_operator.yaml
image: bloomberg/solr-operator:0.1.1

However I don't see this image on Docker Hub. Results in subsequent state...
    state:
      waiting:
        message: 'rpc error: code = Unknown desc = Error response from daemon: manifest
          for bloomberg/solr-operator:0.1.1 not found'

To Reproduce
Run the examples
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Operating System and Version: Docker for Mac Version <IP_ADDRESS> (31259) with K8s single node

Hey Zane, I think that the most recent uploaded version is 0.1.0. And the latest tag (0.1.1) only gets pushed to docker whenever a release is cut.
We could change the examples if this is confusing. Maybe it should just use latest in the examples.

Tried to flip back to 0.1.0, but looks like command line flags have changed from 0.1.0 to 0.1.1 Ill make some changes to test out.

Ok, looks good now, made the flag name adjustments containers starts now. Thanks!

No worries. Sorry about the name adjustments. As we add features at this early point, I imagine there are going to be a few breaking changes. I'll add a log of those somewhere though, to make upgrading/downgrading easier.


[NO-MERGE] Testing IL Compiler

As per commit 2224c32, I know want to see what's the latest version of ILCompiler (versions) with which it works.
6.0.0-preview.5.21227.7 - passes
6.0.0-preview.5.21266.2 - fails
6.0.0-preview.5.21253.3 - passes
6.0.0-preview.5.21256.2 - passes
6.0.0-preview.5.21257.1 - passes
6.0.0-preview.5.21258.1 - passes
=> 6.0.0-preview.5.21266.2 is the problematic version

Codecov Report

Merging #423 (91cb559) into master (2224c32) will not change coverage.
 Consider uploading reports for the commit d1b4476 to get more accurate results

@@           Coverage Diff           @@
##           master     #423   +/-   ##
=======================================
  Coverage   80.64%   80.64%
=======================================
  Files         145      145
  Lines       12449    12449
  Branches     1681     1681
=======================================
  Hits        10040    10040
  Misses       1895     1895
  Partials      514      514

Continue to review full report at Codecov.

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


AGOLTokenSecurityHandler and/or ArcGIS Desktop login?

I don't know if it's possible to access the credentials obtained by logging in AGOL in ArcCatalog/ArcMap in my own tool built upon ArcREST.
by doing this, I only need to login from ArcGIS Desktop once and then I will be able to run multiple tools without the need to create new AGOLTokenSecurityHandlers every time for each of them.
thanks

Use the https://github.com/Esri/ArcREST/blob/master/src/arcrest/security/security.py#L877

Thanks @MikeMillerGIS , Could you give a little bit more details? or even better, a snippet of code if possible?

Does that mean I can use ArcGISTokenSecurityHandler for the securityHandler in the following code?
fs = FeatureService(
    url=url,
    securityHandler=agsSH,
    proxy_port=proxy_port,
    proxy_url=proxy_url,
    initialize=True)

Yes, but the script must be run from within ArcMap or ArcCatalog.  There are examples in the tools folder.

Thanks @MikeMillerGIS
@BrunoCaimar
ArcGISTokenSecurityHandler works


Can I use command without verb when verbs are declared?

Is it possible to use verbs with options like this:
app.exe install --name someName --version 1.0.0
and have command which doesn't use verb and use only value attribute such as:
app.exe someName stream
I need to do this for backwards compatibility of my application.

Can you show option class for both cases to figure how that command can work.

you can use default verb wiki page.


UI/UX: Introduce Zoomable Time series Chart in Dashboard Portfolio

Problem
Current Portfolio widget is showing insights in particular timeframe, and if user wants to read/inspect the data for particular time range its getting hard to read/analyse the values
https://anthem.chorus.one/cosmos/total?address=cosmos15urq2dtp9qce4fyc85m6upwm9xul3049um7trd
Proposed Solution
Introduce Zoomable Time series chart to support Click & Drag in the chart to zoom in and inspect the data in particular time frame
Reference: https://www.highcharts.com/demo/line-time-series

simply adding zoomType: 'x'  to options.chart in getHighchartsChartOptions  function would solve this.
https://github.com/ChorusOne/anthem/blob/342a42dab5ee91d2e230b149b333f37a55e42702/packages/client/src/tools/chart-utils.ts#L84

Hey @NageswaraRaoSanika and @sertsedat,
We finally got around to implementing this! You can try it out on any chart in Anthem by marking the area you'd like to zoom in on with your cursor.
Thanks for your contribution to Anthem! I will be closing this issue now.

Hey @NageswaraRaoSanika and @sertsedat,
We finally got around to implementing this! You can try it out on any chart in Anthem by marking the area you'd like to zoom in on with your cursor.
Thanks for your contribution to Anthem! I will be closing this issue now.


SyntaxError: Unexpected number in JSON at position

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
When I was using the UnofficialProxyAPI and used the await method to wait for the results to return, I received a JSON parsing error.
Describe the Bug
After debugging, I found that there is a time interval when querying a specific question, which causes the JSON parsing to fail. The question is 我需要写一个wechaty的功能介绍， I have tried this issue many times and encounter the same problem every time.
...
const chatGPT = new ChatGPTUnofficialProxyAPI({...})
const { conversationId, text, id } = await chatGPT.sendMessage(content);
...

yes, I just encountered this issue a few minutes ago with UnofficialProxyAPI...

same here

I also encountered a problem, we would appreciate it if you could fix it as soon as possible

Been encountering this error a lot lately as well

is there any updates ?

也遇到了一样的问题

Thanks for the report, @leochen-g.
Closing as a duplicate of #557. See my previous response there https://github.com/transitive-bullshit/chatgpt-api/issues/557#issuecomment-1530795074


Expose expiration property on temporary STS credentials

Describe the feature
Currently the expiry time for a token is not exposed when getting a temporary STS token. This property is stored as part of the CredentialsRefreshState is the class below. Could you look at adding this property into ImmutableCredentials or exposing it in some other way.
https://github.com/aws/aws-sdk-net/blob/main/sdk/src/Core/Amazon.Runtime/Credentials/RefreshingAWSCredentials.cs
Use Case
I need to know when I need to refresh temporary STS credentials and don't want to call GetCredentials() before every AWS API call in my application.
Proposed Solution
Add Expiration property into ImmutableCredentials and populate it in the Copy method where it exists.
https://github.com/aws/aws-sdk-net/blob/main/sdk/src/Core/Amazon.Runtime/Credentials/ImmutableCredentials.cs
Other Information
No response
Acknowledgements

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

AWS .NET SDK and/or Package version used
AWSSDK.SSO <IP_ADDRESS>
Targeted .NET Platform
.NET 7
Operating System and version
Windows 10

Appears to be useful feature request. Needs review with the team.

@OnKey Please elaborate your use case. Refreshing credentials happen automatically when RefreshingAWSCredentials are nearing expiration.

I've hit the same limitation now. My use case is that we generate credentials for use with credentials_process, but to make that work well, we need to return the expiry date. It's frustrating that we can't get at it when it's clearly stored within the class.


chore: Delete Kafka Instance, Topic and Consumer Group

What this PR does / why we need it:

make updates to Delete modals based on usability findings

Verification steps

Delete Kafka Instance:

Kafka>  < DeleteKafkaInstance > < Story >

Delete Kafka Topic (Without Active users):

Kafka>  < DeleteKafkaTopic > < Story >

Delete Kafka Topic (With Active users):

Kafka>  < DeleteKafkaTopicActiveUser > < DeleteKafkaTopicActive > < Story >

Delete Consumer Group

Kafka>  < ConsumerGroups >  < components > < DeleteConsumerGroup > < Allow Consumer Group Deletion >

Don't have service account done yet because it doesn't have a place to go yet

Thanks for making these updates. I posted a comment inline regarding some text string changes.
While reviewing these, I realized that the shared Delete modal you’re basing the new components on could use some refactoring. I’m not sure if that’s something that should be addressed as part of this PR, or not.
In the original implementation of the shared Delete modal, there are two instances of the pf-c-modal-box__body section that are nested. This results is more padding around the contents than we should have. I also don't see any examples in PF showing that you could have multiple body elements as siblings in the modal. I think all contents in the modal are expected to reside in the same body.
Making this change will also require some additional layout within the body of Kafka delete modals to add the space we need between contents. I had created a codesandbox a while back to explore how these contents could be implemented. There are probably some things in there that we don't want to reuse, but it might be helpful to see what some options are. I think the right thing to do is to use a stack layout with a gutter to create space between the message text and form input with label.
@riccardo-forina - What would you recommend here?

I'd say that I originally disabled the default body wrapper in the shared delete, and then enabled it back but I can't recall exactly why. Probably it was by mistake. I'd suggest flipping this boolean and see what happens, it should make it work properly.

@jgiardino you should now see the link for storybook

Thanks, @riccardo-forina. I checked again, but I still see the issue with the spacing. But I'm also not sure if @Kells512 tried your suggestion or not with her latest commits.

Ah, no, that's still on the pen I think.

Thanks, @riccardo-forina. I checked again, but I still see the issue with the spacing. But I'm also not sure if @Kells512 tried your suggestion or not with her latest commits.

Yes I will do that today

Thanks, @riccardo-forina. I checked again, but I still see the issue with the spacing. But I'm also not sure if @Kells512 tried your suggestion or not with her latest commits.

It is done now :)

Thank you @Kells512! Your examples look good to me.

@Kells512 it looks like by flipping that boolean we need to manually set an aria attribute
Modal: When using hasNoBodyWrapper or setting a custom header, ensure you assign an accessible name to the the modal container with aria-label or aria-labelledby.

Ping me in chat if you need help figuring this out

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


Fix to 6 Layer Export

Fixed 6 Layer Push because of typo.

Hi @Niklas-Sommer!
Thanks for this MR, we just released an updated release and also published to the KiCad repo. Please remember to update your local plugin, too.


Remove links inside the code block in the loaders.md.

Remove links inside the code block.
I‘m confused about that does JS have a new syntax, when I frist see that. Finally I realized that's Markdown syntax.

Those links are documentation, they are not render correctly at this moment but that's another issue.

@montogeek
Oops, I made some mistake, you already implemented this feature. remark-refractor/js-links-details.js at ed597eed49f792354e8b9889f001a3f2f5aa24d3 · montogeek/remark-refractor
Should we change \src\content\concepts\loaders.md, src\content\configuration\module.md to mdx?

I use global search to search js-with find those two file has md suffix, others are mdx suffix.

@1010543618 I think that would work, Can you try please?

@montogeek
According to my test, Links in js-with-links can be transformed  to HTML a tag only when it in the comment. (I think this it right way, not a bug.)
So links in src\content\configuration\module.md can be fixed by using mdx loader, but for \src\content\concepts\loaders.md we can fix it like this Remove links inside the code block in the loaders.md. by<PHONE_NUMBER> · Pull Request #2857 · webpack/webpack.js.org, because links in it did not in the comment.

Please apply your suggested changes


Mema2

HMEC122L and HMEC240L were imported and figure 1 now plots the R2X for these two, too. Could you please just confirm that these are the data that we are looking for? Here is the website I downloaded them from: https://www.synapse.org/#!Synapse:syn9838985

The size of the tensor for these two is equal and is 57 x 48 x 64, which is ligand x ECM x measurements.

Do the variable names match? It looks like SSC and SS1 are the staining sets shared with MCF10A...

Yeah, you want the SSC files. From the documentation: "There are level 3 and 4 files for each cell line with the staining sets combined (StainingSet = SSC)."

oh.. thank you, I will replace them.

I replaced the data we had (including mcf10a) with all _scc_level3 files. Although I compressed them with xz but they are still above 50 MB and github doesn't let me push them to here. There is this option, "Git Large File Storage": https://git-lfs.github.com/
Do we want to use that?
I can run everything on my local, though. we can make the data files hidden..

Can you put the files in our shared box folder? From there, I can put them in a folder on the lab server that we all can access.

Actually, I'll see if I can just pull the files from your user account...

Ok, these files are available at /opt/MEMA-data/. This path will also work for GitHub builds.

Worked nicely, can I merge this?
I understand we may want to organize figure 1 in a different way, but I guess we would need to think about the cartoon first. Would it be alright to leave it like this for now?


Detected blocking call to open inside the event loop by custom integration 'xiaomi_gateway3'

Debian GNU/Linux 12 (bookworm), Home Assistant Supervise,  core-2024.6.2, XiaomiGateway3 - master
Уровень: ПРЕДУПРЕЖДЕНИЕ
Регистратор: homeassistant.util.loop
Источник: util/loop.py:84
Первое сообщение: 07:16:12 (74238 сообщений)
Последнее сообщение: 14:44:50

Detected blocking call to open inside the event loop by custom integration 'xiaomi_gateway3' at custom_components/xiaomi_gateway3/core/gate/base.py, line 72: self.base_log.debug(msg | kwargs, exc_info=exc_info) (offender: /usr/local/lib/python3.12/logging/__init__.py, line 1263: return open_func(self.baseFilename, self.mode,), please create a bug report at https://github.com/AlexxIT/XiaomiGateway3/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/config/custom_components/xiaomi_gateway3/core/gateway.py", line 58, in run_forever await self.handle_mqtt_messages() File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 147, in handle_mqtt_messages self.on_mqtt_message(msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 177, in on_mqtt_message self.dispatch_event(EVENT_MQTT_PUBLISH, msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 91, in dispatch_event handler(*args, **kwargs) File "/config/custom_components/xiaomi_gateway3/core/gate/ble.py", line 26, in ble_on_mqtt_publish self.ble_process_event(msg.json["params"]) File "/config/custom_components/xiaomi_gateway3/core/gate/ble.py", line 59, in ble_process_event device.on_report(data["evt"], self, ts) File "/config/custom_components/xiaomi_gateway3/core/device.py", line 462, in on_report gw.debug("on_report", device=self, data=payload) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 72, in debug self.base_log.debug(msg | kwargs, exc_info=exc_info)
Detected blocking call to open inside the event loop by custom integration 'xiaomi_gateway3' at custom_components/xiaomi_gateway3/core/gate/silabs.py, line 82: self.zigb_log.debug({"uid": uid, "nwk": nwk, "data": data["decode"]}) (offender: /usr/local/lib/python3.12/logging/__init__.py, line 1263: return open_func(self.baseFilename, self.mode,), please create a bug report at https://github.com/AlexxIT/XiaomiGateway3/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/config/custom_components/xiaomi_gateway3/core/gateway.py", line 58, in run_forever await self.handle_mqtt_messages() File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 147, in handle_mqtt_messages self.on_mqtt_message(msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 177, in on_mqtt_message self.dispatch_event(EVENT_MQTT_PUBLISH, msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 91, in dispatch_event handler(*args, **kwargs) File "/config/custom_components/xiaomi_gateway3/core/gate/silabs.py", line 59, in silabs_on_mqtt_publish self.silabs_process_recv(msg.json) File "/config/custom_components/xiaomi_gateway3/core/gate/silabs.py", line 82, in silabs_process_recv self.zigb_log.debug({"uid": uid, "nwk": nwk, "data": data["decode"]})
Detected blocking call to open inside the event loop by custom integration 'xiaomi_gateway3' at custom_components/xiaomi_gateway3/core/gate/base.py, line 72: self.base_log.debug(msg | kwargs, exc_info=exc_info) (offender: /usr/local/lib/python3.12/logging/__init__.py, line 1263: return open_func(self.baseFilename, self.mode,), please create a bug report at https://github.com/AlexxIT/XiaomiGateway3/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/config/custom_components/xiaomi_gateway3/core/gateway.py", line 58, in run_forever await self.handle_mqtt_messages() File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 147, in handle_mqtt_messages self.on_mqtt_message(msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 177, in on_mqtt_message self.dispatch_event(EVENT_MQTT_PUBLISH, msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 91, in dispatch_event handler(*args, **kwargs) File "/config/custom_components/xiaomi_gateway3/core/gate/silabs.py", line 59, in silabs_on_mqtt_publish self.silabs_process_recv(msg.json) File "/config/custom_components/xiaomi_gateway3/core/gate/silabs.py", line 128, in silabs_process_recv device.on_report(data, self, ts) File "/config/custom_components/xiaomi_gateway3/core/device.py", line 462, in on_report gw.debug("on_report", device=self, data=payload) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 72, in debug self.base_log.debug(msg | kwargs, exc_info=exc_info)
Detected blocking call to open inside the event loop by custom integration 'xiaomi_gateway3' at custom_components/xiaomi_gateway3/core/gate/base.py, line 175: self.mqtt_log.debug({"topic": msg.topic, "data": msg.payload}) (offender: /usr/local/lib/python3.12/logging/__init__.py, line 1263: return open_func(self.baseFilename, self.mode,), please create a bug report at https://github.com/AlexxIT/XiaomiGateway3/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/config/custom_components/xiaomi_gateway3/core/gateway.py", line 58, in run_forever await self.handle_mqtt_messages() File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 147, in handle_mqtt_messages self.on_mqtt_message(msg) File "/config/custom_components/xiaomi_gateway3/core/gate/base.py", line 175, in on_mqtt_message self.mqtt_log.debug({"topic": msg.topic, "data": msg.payload})

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.8


Accessibility Violation: Multiple "search" landmarks with the same parent region are not distinguished from one another because they have the same "" label and Multiple elements with "search" role do not have unique labels

1. Multiple "search" landmarks with the same parent region are not distinguished from one another because they have the same "" label
2. Multiple elements with "search" role do not have unique labels
Detailed description
This issue is specific to the
 element which is used inside <ibm-search> and <ibm-table-toolbar-search> component
In my case I am using <ibm-search> at two places along with <ibm-table-toolbar-search> in a single page. Which is resulting in this accessibility violation.
Using ARIA landmarks to identify regions of a page
The purpose of this technique is to provide programmatic access to sections of a web page. Landmark roles (or "landmarks") programmatically identify sections of a page. Landmarks help assistive technology (AT) users orient themselves to a page and help them navigate easily to various sections of a page.
There are cases when a particular landmark role could be used more than once on a page, such as on primary and secondary navigation menus. In these cases, identical roles should be disambiguated from each other using a valid technique for labelling regions.
Landmarks should supplement native semantic markup such as HTML headings, lists and other structural markup. Landmarks are interpretable by WAI-ARIA-aware assistive technologies and are not exposed by browsers directly to users (see examples below).
It is a best practice to include ALL content on the page in landmarks, so that screen reader users who rely on them to navigate from section to section do not lose track of content.
Example 1
The following example shows a best practice of how landmarks might be added to an HTML4 or XHTML 1.0 document in situations where there are more than two of the same type of landmark on the same page. For instance, if a navigation role is used multiple times on a Web page, each instance may have a unique label specified using aria-labelledby:

Example 2
The following example shows a best practice of how landmarks might be added to an HTML4 or XHTML 1.0 document in situations where there are more than two of the same type of landmark on the same page, and there is no existing text on the page that can be referenced as the label.

Is this a feature request (new component, new icon), a bug, or a general issue?
bug

Is this issue related to a specific component?
yes, <ibm-search>

What did you expect to happen? What happened instead? What would you like to see changed?
Multiple elements with "search" should have unique labels. There should be an option to provide label to <ibm-search>

What browser are you working in?
chrome Version 112.0.5615.49 (Official Build) (arm64)

What version of the Carbon Design System are you using?
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Additional information

Screenshots or code

@Akshat55 Any update on this issue ?

Will look into this! @AmirHussain93

Multiple "search" landmarks with the same parent region are not distinguished from one another because they have the same "" label
Multiple elements with "search" role do not have unique labels

@AmirHussain93 - Unique labels are missing. If you have multiple searches on the page, you need to let the screen reader know what those searches are for.
The labels are hidden, but available to the screen reader. Please add unique labels to each search and your issue will be resolved.

		<ibm-search label="Label!"></ibm-search>

Closing this issue as the fix is required on your end, feel free to respond or reopen.


⚠ 한경주요지수-코스피200 has degraded performance

In 5a4adb2, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 5130 ms

Resolved: 신규상장 performance has improved in 5b40062.


Add versioning section to API overview

Signed-off-by: Maciej Mrowiec<EMAIL_ADDRESS>

Looks good; will tweak the wording slightly and backport to 1.0.x.


Support cash positions

Knowing how much "spare" cash is lying about would be handy for rebalancing, for example.

Donating priority to #64, as that will make this a lot easier.


multiple queued songs possible?

can I load a playlist, or multiple songs to be played consecutively, using this library?

@vesper8 Sorry, I don’t support it, but I can consider it in the future.

@vesper8 Sorry, not yet, but I can consider it later.


fixed #5622 - mysql 5.7 ONLY_FULL_GROUP_BY

#5622
I fixed it with reference to #5973
please check.

I just tested this in our project and it seems to solve the issues. Really awesome! :+1:
Would be great if this could get merged.

Confirmed here too, +1 for a merge :)

Confirmed here too, +1 for a merge :)

Looks good. Let's merge this!

@Ocramius
this pr Is there something wrong?
anything else needed?
thank you.

Simply didn't get to it, sorry.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
On Wed, Mar 15, 2017 at 1:18 PM, chihiro-adachi<EMAIL_ADDRESS>wrote:

@Ocramius https://github.com/Ocramius
this pr Is there something wrong?
anything else needed?
thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/pull/6143#issuecomment-286724927,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakJiQrYhcTpaQqIV6L6P8Xxi9ZjFcks5rl9cBgaJpZM4K5JxB
.

lgtm :+1:

is this on deck to be pulled in anytime soon?

+1

+1

+1

@Ocramius I've synced this PR with master and added MySQL 5.7 to Travis. I'm  just not fully convinced that this is the way to go (regex stuff and also the impact of wrapping the subquery on the other platforms).

the impact of wrapping the subquery on the other platforms

Any SQL-compliant platform should require this fix.

why still not merge?

@Arkemlar because I'd rather not have support for MySQL 5.7 than having security issues due to regex-based SQL manipulation.
The patch may be good, but it will need further checking for edge-cases in the newly added conditionals.
Also, tests were only modified so far, but none was added.

Looking good according to @lcobucci's changes: will likely merge today.

Will this be merged into stable versions as a bugfix?

@chihiro-adachi this is already in 2.6.0

Is 2.6.0 released yet? I can't find it anywhere. But I mean this should be treated as a bug, right? If so, might it be fixed in the currently supported versions?

No, mysql 5.7 is just officially supported in 2.6 (unstable version).
On Mon, 24 Jul 2017, 12:18 Teoh Han Hui<EMAIL_ADDRESS>wrote:

Is 2.6.0 released yet? I can't find it anywhere. But I mean this should
be treated as a bug, right? If so, might it be fixed in the currently
supported versions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/pull/6143#issuecomment-317380394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMU6w196JWvvHIDEAOkedRI0LTy9zlZks5sRG-NgaJpZM4K5JxB
.

@teohhanhui no, newer mysql versions broke BC and we simply support them in a newer version only.

I thought this bug is also present when using other SQL-compliant platforms such as PostgreSQL... Because this bug only manifested itself when MySQL started becoming more SQL-compliant.

@teohhanhui yes, but only MySQL crashes hard. So far, the only issue with such queries was non-deterministic result due to ordering.

@teohhanhui If you can't wait for Doctrine 2.6 to be released you still have the hackish way of overriding the Autoloader in your composer.json:
"autoload": {
        [...]
        "files": ["src/LimitSubqueryOutputWalkerPatch.php"]
    },

Just put the fixed source from this PR into the LimitSubqueryOutputWalkerPatch.php. When composer dumps your autoloader the class will take precedence over the Doctrine 2.5 one. Until Doctrine 2.6 is available you use this to temporarily fix the MySQL 5.7 incompatibility of the Paginator.
But keep in mind that this is pretty hackish. On the other hand if a project is blocked because of this you sometimes just don't have a choice.

It seems like there should be a version of Doctrine that supports both PHP 7.0 and MySQL given that those are the available versions in Ubuntu 16.04

Won't happen, as that is just pushing back the ecosystem with the excuse that the ecosystem is already being pushed back.
You can simply rely on the PPAs by ondrej, which reflect PHP core development, on which you can rely for security maintenance as well.


Layer tooltips not working (since v0.4.11)

🐛 Bug
Just noticed that #3204 broke #2658 ... (Window no longer even has a tooltip_menu attribute anymore)
so this feature has been broken since v0.4.11.  but it was never detected by tests, and it looks like no one has noticed.  @Czaki, is this still a feature that you want to have and fix?  Or does the fact that no one has noticed mean we can trim this one?

Could you explain what you mean when writing that it is not working? This screenshot I do a moment ago on the main branch.

ah, ok sorry my bad.  At the very least, there's some hanging/stale code in qt main window:
https://github.com/napari/napari/blob/458a7e0f0a15c17fab12cb5ae45cbfc591fa303e/napari/_qt/qt_main_window.py#L634-L637
that's the only reference I can find to Window.tooltip_menu

Not only this one.
I remove few of them in #4817

(fixed in https://github.com/napari/napari/pull/4817)


Text-stroke and Paint-order support

This ads support for -webkit-text-stroke, -webkit-text-stroke-width, -webkit-text-stroke-color, and paint-order.
Note that even through these are webkit prefixes, Firefox still uses them.
paint-order is required in order to get strokes to render as an outline of the text and not in the middle.
paint-order does not currently work fully in chrome, as chrome reads the value of the property, but does not apply it in the dom. Firefox and Safari work just fine.
See tests/text/stroke.html for an example

Fixes #759 and #1108

Thanks a lot @arzynik , I've published your branch to npm: https://www.npmjs.com/package/html2canvas-stroke , it unblocked https://github.com/devforth/painterro text-stroke feature (though html2canvas-stroke is very updated, probably someone has time capacity to merge a new changes or needs this, poke me)


Automatic labeling licensing

According to https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance automatic labeling is not allowed in Office 365 E3 nor M365 Business Premium.
However, I have tried with an O365 E3 tenant as well as a M365 BP tenant and automatic labeling options are working.
@pamelaar

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

ID: 6564bdaa-d66b-42ba-85bd-7c8f9989093d
Version Independent ID: 33be52f1-d233-9c5d-abb3-140a9c6a0d74
Content: Automatically apply a sensitivity label in Microsoft 365 - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/apply-sensitivity-label-automatically.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@JMCA2  I don't believe there's anything on this page that covers whether the required licenses for auto-labelling are enforced or not. Instead, you'll see that information generically covered at the top of the licensing page that you referenced, saying it's not always possible to enforce licensing but you should still acquire licenses for any user that you intend to benefit from the service.
If you have feedback about the licensing statements, please open a GitHub Issue for the licensing page rather than here.

Done. I've opened https://github.com/MicrosoftDocs/OfficeDocs-O365ServiceDescriptions/issues/812
Thanks