Speaker Card sizes

The speaker cards have varying content and differing images. Currently, the card wraps the text, and so they all end up as different sizes. Ideally, they would all be the same size.

Fixed by carousel implementation.

Fixed by carousel implementation.


Support RandomizedSearchCV

RandomizedSearchCV takes argument param_distributions which can accept a scipy.stats.distributions instance. When calling sklearn_model.get_params() this comes back as an rv_frozen instance. This is recapitulated as the name of the distribution and the args that were passed to it, eg
uniform(loc=0, scale=4)

becomes
{
    "dist_name": "uniform",
    "args": [],
    "kwds": {
        "loc": 0,
        "scale": 4
    }
}

could we do this via PR, from now on as i have some comments that needs to be address that i'll put it directly to the commits now... but that'd make easier the dev cycle... hence i've created a kanban that is review based

yes sorry, forgot about the kanban. just let me know the procedure and i will follow from now on


Add ControllerFactory

Description
Add ControllerFactory to override the instantiation of the controller.
This PR enables users to use dependency injection (container) when instantiation of a controller.
See https://forum.codeigniter.com/thread-78699.html.
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

I'll be honest - I'm struggling with the need for this one. You've replaced what is accomplished in 2 lines with a new service and a new class. Only a single controller is ever loaded at a time, so this doesn't do anything for caching. It doesn't help performance and likely hinders it a touch. I cannot come up with a compelling reason to make this change. it just seems to add complexity for complexity's sake.
Closing for now but feel free to make you case.

Reading back over the referenced thread I get it. This is an attempt to make it more like what people are used to. We purposefully chose to not use a DI container. See the comment here and give Maxwell's blog a read to understand why.

@lonnieezell

We purposefully chose to not use a DI container.

This PR never introduces a DI container to CI4.
This provides a way to override a controller creation.
What should a user do if he/she wants to inject dependencies into a controller?

@lonnieezell I came up with another way. #4376

This PR never introduces a DI container to CI4.
This provides a way to override a controller creation.

I understand that. But it's adding an additional layer of complexity to make it possible to support one person's desire for something we already made a decision not to support.
Your new solution has more promise. I'll look it over in more detail later.

I guess this will accomplish the desired result, but I was thinking more along the lines of Config\Services::controller() as a way for this particular user (and anyone) to supply their own controller class.


Using v1.0.5 Authenticated Connection Fails

Hey Tux & Joel,
First the update IS more stable. Thnx. Analyzing all the async/awaits and Task.Run and Thread.Starts is horrendous. I had to smoke 2 bowls to make sense of it all, along with deprecated or renamed requirements/variables/etc between the packages. All packages need some refactoring to get on the same level. For example, some packages want XSXT Jwt token and named that, while the parent package is looking for XToken Jwt, and they the same thing but you get exceptions unless manual edit. Along with calculating size of payload. Passes Authentication and parsing of tokens.json, but fail authenticated.Connect(ip, hash, xtoken), always ends in a substring exception about limits and position while calling fragment sendasync(), connects anonymously fine but no authenticated connection due to length/position exception. Note: Under python core and REST it works as should. only under NetStandard2.0/Net v4.7.2, it's in SessionMessageTransport  wait for response.
I can get a annon connection but never authenticated. All the variables are dynamic, xtoken refreshes at startup, authenticate succeeds, connection(ip) succeeds, connection(ip,hash, auth) fails with substring limit/length exception in generate CreateRequestMessage().
Ideas? This kinda related to another issue with connections, but I do get a connection a everything seems to work other than an authenticated session. BTW, what are the gain/losses over authenticated/anonymous connections? with/o using Live functions? What would be the limitations?
P.S. Tux I using the "ey...." token (XToken, XSTSToken), don't get a failed auth or anything just the exception for parsing the token.

80acd7e Fix authenticated ConnectRequest assembly
Give that a try

Thnx Tux! That seemed to have solved that. No more exception.
Thank you for the informative answer with the differences.


When delete a service, should be truly deleted service from DB and repos.

In GitLab by @cuiaq123 on Mar 21, 2018, 09:17
Menu location：Image create
Preconditions：input image name and tag ,confirm success
operating：upload file ,and input other information，once again confirm the image name and tag
expected results：confirm success
actual results：show :image name or tag exist

In GitLab by @sokril on Nov 8, 2019, 07:48
fix with pr1108

In GitLab by @sokril on Nov 8, 2019, 08:19
closed

In GitLab by @sokril on Nov 8, 2019, 08:19
assigned to @sokril


Some modules are missing when using webpack 2

Problem
We tried to use Webpack 2 and the current master branch of the webpack plugin.
The bundle generation is creating a correct bundle, but the packaged node modules,
that are installed as sibling to the bundle by the plugin are missing some external modules.
I.e. although they are present in the local services' package.json, they do not appear in
the package.json that is temporarily created by the webpack plugin to install the needed
external modules.
This leads to "required module not found" errors, when executing the compiled code on AWS
after Serverless deployed it.
Root cause
The plugin parses the webpack stats to find external modules by matching the returned stats
with "external ".
See comment below: Webpack 2's dependency optimization sometimes removes first level dependencies but keeps the removed dep's second level dependencies.

I'll have to investigate this further. The package.json created by the plugin in .webpack is different regarding the dependencies than the original package.json. I'll reopen this as soon as I have more qualified information at hand.
Seems to be more than just the npm install.

Reopened the issue after deeper investigation. Changed the description and subject to match my findings and the problem.

Further analysis:
The stats object returned by webpack 2 contains all external references marked with "external ", but not in compilation.chunks but in compilation.Compilation._modules. These marked modules are the complete and correct list. The chunks array that the plugin analyzes does not contain the modules needed for the output to be functional.
The underscore hints to this being private, but maybe there is an other way to detect and get the modules.

It is even more complex.
The only way to handle this correctly is, in my opinion, copying all of the emitted externals right from the project's node_modules folder as webpack operated on exactly this.

Fixing #71 would also fix this it seems.

I am also experiencing a similar issue where I use yarn to install a local npm module (a library I have created) and webpack reports a "Webpack Missing Module 'Module Not Found'". Not sure if this is an error with webpack or this plugin as I didn't have time to dig too deeply

any updates on this?

@daviskoh I stabilized the packaging in V3 and we run that already in our production environment. You can try it by using version ^3.0.0-rc.1. We did not experience "module losses" anymore.
However, the key to make it work well, is to use the new slsw.lib.entries automatic entry/handler detection and making sure that the function definitions in your serverless.yml point correctly to the handler files if they are located in subdirectories.


hide grid-specific controls when no grid in workspace

When there is no grid in the workspace, we shouldn't display any controls that are grid-specific.

https://www.figurl.org/f?v=http://localhost:3000&d=e9d66edac2246a9db4aca6c515d4b79aaa450796&channel=flatiron1&label=Test volumeview workspace is a good figure to develop against.

https://www.figurl.org/f?v=http://localhost:3000&d=e9d66edac2246a9db4aca6c515d4b79aaa450796&channel=flatiron1&label=Test volumeview workspace is a good figure to develop against.

But that's an example that does have a grid. So I'm not sure why that link is part of this issue...

Oh, sorry, I misread--I was assuming we would suppress everything but the grid selection when no grid is selected (even if one could be selected).

Oh, sorry, I misread--I was assuming we would suppress everything but the grid selection when no grid is selected (even if one could be selected).

Oh you are right, we'll want to do that too.


opencompetition in md

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue

How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[x] All tests passed, and additional code has been covered with new tests.

Jeremy, is it possible that I directly edit this file? I have now created a separate pull request, I believe -- sorry, I am somewhat lost (new to GitHub...)

The simplest way for now is indeed to create a separate pull request on this branch, I just merged it now, your edits should be included


feat: 1.0.0-EAP-2

New features:

AsyncAPI 2.6.0
New bindings
New Security Schemes
Specification components now can be extended - x-*

Changes:

Bindings now are common for 2.6.0, 2.0.0
Schema now is common for 2.6.0, 2.0.0
Security Scheme now is common for 2.6.0, 2.0.0
Specification components doesn't overrides given ObjectMapper - https://github.com/asyncapi/jasyncapi/issues/128
Schema.additionalProperties now can be boolean or Schema
Schema.minimum, Schema.exclusiveMinimum, Schema.maximum, Schema.exclusiveMaximum now are BigDecimal  - https://github.com/asyncapi/jasyncapi/issues/97, https://github.com/asyncapi/jasyncapi/issues/96

Fixed:

[2.0.0] Typo in Components serverBindings: ServerBinding instead of ServerBindingsDeserializer
Error while parsing of specifications when Reference was recognized as Schema
[2.0.0] Fixed typo in ServerVariable field name - example was renamed to examples

https://github.com/asyncapi/jasyncapi/issues/126


Tooltip for Adding New Devices

WHY?
Some users have emailed the support inbox with confusion about not seeing the devices they would like. Oftentimes the underlying issue is A- the device doesn't exist or B- the org/facility admin has not added that device to the facility or org
AS A user of SR
I WANT some notification of why i don't see the device i want to use on my test card
SO THAT i don't have to email the support inbox

GIVEN I am on a test card
WHEN I hover over the device tooltip
THEN I am presented with the tooltip explaining how to get my device added
https://www.figma.com/file/NPSPM5SBzQ7Ra3mmr9M9cB/SimpleReport-Public-Site?node-id=6342%3A22315
Design notes:

The icon is from font awesome
The tool tip is an available component from USWDS (https://designsystem.digital.gov/components/tooltip/)

Translations

[ ] Translations are required
[ ] Translation request has been submitted
[ ] Translations have been received

@Rebecca-LM , currently the text for this tool tip is: "Don’t see the test you’re using? Ask your organization admin to add the correct test and it'll show up here."
What do you think of the idea of also mentioning where the org admin can add the correct test ("Manage facilities"), i.e. "Ask your organization admin to add the correct test under 'Manage facilitities' and it'll show up here."
Also noticing some content inconsistencies. Right now, the dropdown for this is labeled "Device" and the place to add another test for the admin is called "Manage devices". However, in this tool tip, we refer to it as "test". Wondering what you think about using "test" or "device" across the experience if possible. I've included a screenshot for context.

@kenieh I'd shorten the tooltip text just a bit. Something like "Don't see the test you're using? Ask your organization admin to add it and it'll show up here." Honestly I'd love to see a "request a device" functionality where it sends their admin an email add one, with instructions on how! A tooltip to try to cover all that seems alright, but not the best solution.
You bring up some good points (test vs. device) we've touched on before that are probably a longer conversation. Can we add this to the bug hunt items?

closing as a dupe. already done


API Design for "Resource-based subscription"

Problem description
Within Commonalities API design guidelines, it has been indicated a common way to define the support for notifications model.
https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#12-subscription-notification--event
In "Resource-based subscription" when applying this model to the API design, several approaches are seen:
Model 1:

Device Location Verification (separate API): https://github.com/camaraproject/DeviceLocation/pull/74/files

Model 2:

Device Status (functionlity embebbed within API): https://github.com/camaraproject/DeviceStatus/blob/main/code/API_definitions/device-status.yaml#L134

We think it is reasonable to have a common way to design this features.
Our proposal is to align the approach and use a common model when including this features in WG APIs families.
This will require some indication in Commonalities Guidelines. Once some conclusion is reached.
Possible evolution
Our proposal is to follow Model 1 when designing "Resource-based subscription" in API families. Main reasons to support this model are:

Design 'simpler' APIs, avoiding APIs with many endpoints, that make its implementation and availability complex.

Have more 'flexibility' to evolve "Resource-based subscription" separately, so also roadmaps can be decoupled in order to expose this functionality. In this way, timeline for API functionality and subscriptions feature can be decoupled so Telco Operators can provide them in a more agile way depending on its market needs.

Notification subscriptions systems can be from technical perspective decoupled from API BE Logic, so having different "server url" exposition. That is, the logic of subscription management is managed separately from the API BE logic, as the main "core" of this logic is to identify when an event occurs if there is a matching susbcription for that event and if so, send a notification to the notificationURL indicated

Would like to see the view about this point  within CAMARA

@shilpa-padgaonkar, @hdamker, @eric-murray, @patrice-conil, @bigludo7
RubenBG7
cc @RubenBG7, @jpengar, @jlurien

HI @PedroDiez,
We (@bigludo7 and I) also believe that model 1 is the way to go to clearly define that the /notifications endpoint will be called from the consumer side of the API.
As this model is not well supported by code generators (openapi-generator or swagger-generator for example), we proposed to define a separate OAS specification for the /notifications endpoint that consumers could use to generate their server part.
We have made two joint proposals in commonalities that you can review and comment on.

Thanks @patrice-conil, I will review them

@PedroDiez : I would also like to extend my full support for model 1. The decoupling point you have mentioned is a very important one IMHO.

So far, seems Model 1 is preferred, that is, define a separate API functionality for resource-based susbcription.
If no further comments, I will be preparing a PR to Commonalities API design guidelines next in order to reflect this.

Hi @PedroDiez
Maybe the reason that there are not many comments on this issue is that it is the holiday season, and companies are taking longer to confer internally on this.
Any I do think it important that we get the consolidated views of companies rather than individual developers on this, for otherwise we risk decisions being made based on the opinions of individual developers when other developers from that same company are expressing contradictory views within individual API sub-projects.
For example, the issue of whether APIs should adopt multiple endpoints within an API or multiple APIs was originally discussed within Commonalities here. As the issue did not get any traction, it was agreed to discuss it within individual sub-projects.
The discussion and decision within Device Status can be found here. The agreement was that additional use cases for Device Status should be combined within a common API. This decision was supported by Orange and Deutsche Telekom.
But now we risk a requirement that subscriptions be included in a separate API for exactly the same reasons that were discussed and rejected during the discussion within Device Status.
So this issue should be kept open until after the holiday season, when each company will have had the opportunity to reach and express an internal consensus. This will help to avoid a decision being made here which contradicts decisions made by the same company in the individual sub-projects.

Hi @eric-murray
Get your point, Let's keep open until other companies reflect here also their view

Hi all,
Just recovering this issue, and let me extend with some relationship with Issue#8
We have two models for subscription:

Resource-based (this issue is related to it)
Instance-based (e.g. QoD model)

And we are trying to define a common model for the notification to the API consumer (Issue#8 scope).

One of the topics of Issue #8, reflected in related PRs 41 and 43, is how to indicate the "real" payload carried within the generic framework it is been defined and that it specific depending on the context of the event (i.e. the API the event is related to).

In Implicit-Based models, think is well addressed with the indication of callback model within the API endpoint that implicitly has events related (e.g. QoD: https://github.com/camaraproject/QualityOnDemand/blob/main/code/API_definitions/qod-api.yaml#L99).
In Resource-based Models, think it could be some indication within API Proposal. Like an (informative) endpoint that determines the specific payload in the context of the involved API. It would not be the real endpoint because that one is the one defined via Notifications API (PR#41, PR#43 scope)
This is also aligned with the proposal in Model1. Have checked comments and historic background and (if not wrong), it seems that DT, ORA, VF, TEF would be aligned to go for Model 1.
@shilpa-padgaonkar, @patrice-conil, @bigludo7 have commented in that way, and @eric-murray i understand your comment/concern raised and checking VF view was also to have a separate functionality.
Therefore, my feeling is that we have initial consensus to move towards Model 1 and the pending point here would be how to indicate in this model the specific format of the event to be signalled via common/traversal notifications API

Hi @PedroDiez
Yes, I discussed this internally, and Vodafone's preference is for Model 1. Hopefully this topic can be discussed at this week's Commonalities meeting so that we can get the explicit agreement of other companies.

Hi @PedroDiez, @eric-murray
Idea we have with @bigludo7 with issue #8 is to provide a "base spec" each API could use to extend with its proper event models.

Hi,
understood @patrice-conil.
And we need to decide in the use of a common model: PR#41 or PR#43. (that is at least my understanding)

Not adding comment but trying to separate the topics as we have a commonalities meeting tomorrow and let's see what we can solve

Have a distinct swagger file to define the generic CAMARA notification (tracked in issue #8) - We have so far a lot of positive comment to have this separate notification file (format of this file is point 2)

If decision on separate notification file we need to decide the format: "CAMARA Specific" #41  or based on Cloud Event #43 . I got the feeling that we have more positive feedback about using Cloud Event.

use of callbacks: OAS definition (like in QoD API) or add a specific /notification endpoint (like in Device Status). Got the feeling that we have a consensus to follow the 'callback pattern. In this callback event specific to the API are described but of course use the generic template (point 1) and follow format defined in point 2.

Last but not least the last point mentioned by @PedroDiez about having a specific swagger for Resource-based subscription. As mentioned by @eric-murray I'm not sure this is an easy point to solve as we have already a lot of debates inside commonalities and inside device status WG.

As a lot of API working Group (device location, Device status for example) are waiting for Notification design decision we should perhaps try to get consensus to points 1 to 3 (Decisions there could be reflected on the design guideline document) and park 4 for later.
@PedroDiez @patrice-conil @eric-murray @shilpa-padgaonkar  WDYT?

Feedback for every Point:

Fully aligned, have a common / unique interface for notifications to an API client is indeed ky point to make a common traversal implementation for any Operator. J

Just to set difference in scope of Issue #8 and Issue#44

In this bullet, the key point is to decide which model to apply. We have to decide on one, and apply in the same way for every API. Same the have feeling, and even our current model is closer to PR#41, we are fine to go for Cloudevent Model if we have consensus here.

Now i understood your comment about (@bigludo7) Model 1 and Model 2 (I will comment on bullet 4, because I opened this Issue with other perspective, nonetheless this is also another point to be aligned and have also doubts about @shilpa-padgaonkar understood in the same view as you). Probably the use of callbacks is cleaner and can be used in both models:

Implicit-based: making callback reference in the endpoint that have events associated
Resource-based: making callback reference in the POST /subscriptions endpoint

One thing that we have to bear in mind is that if we go for CloudEvents Model, we will have to adapt the callback definitions in the APIs as they are mainly based in PR#41 proposal.

When opened this Issue was in the context of opening discussion about defining "Resource-Based" suscription model as a separate API in any scenario. @eric-murray got the point and referenced to the thread and background context within Device Status WG, and now I understand @bigludo7 your comment about Model 1 and Model 2 that was related to bullet 3. Have doubt @shilpa-padgaonkar if your comment was in the context raised the issue.

Anyway, I am fine to prioritize Points 1,2,3.
And make follow-up for point 4. Let's talk tomorrow about this point 4

Please provide additional comments till 31st of August. Then @bigludo7 will prepare PR related  to points 1,2,3 to be decided by Technical Steering Committee.

Please provide any additional reviews or comments by 15th September

@bigludo7 (@PedroDiez is on vacation): just to confirm that the scope of #56 is

Not adding comment but trying to separate the topics as we have a commonalities meeting tomorrow and let's see what we can solve

Have a distinct swagger file to define the generic CAMARA notification (tracked in issue Provides specific CAMARA OAS for notification event #8) - We have so far a lot of positive comment to have this separate notification file (format of this file is point 2)
If decision on separate notification file we need to decide the format: "CAMARA Specific" Add generic notification OAS file #41  or based on Cloud Event Define CAMARA Event using cloudevents in OAS notifification #43 . I got the feeling that we have more positive feedback about using Cloud Event.
use of callbacks: OAS definition (like in QoD API) or add a specific /notification endpoint (like in Device Status). Got the feeling that we have a consensus to follow the 'callback pattern. In this callback event specific to the API are described but of course use the generic template (point 1) and follow format defined in point 2.
Last but not least the last point mentioned by @PedroDiez about having a specific swagger for Resource-based subscription. As mentioned by @eric-murray I'm not sure this is an easy point to solve as we have already a lot of debates inside commonalities and inside device status WG.

As a lot of API working Group (device location, Device status for example) are waiting for Notification design decision we should perhaps try to get consensus to points 1 to 3 (Decisions there could be reflected on the design guideline document) and park 4 for later.
@PedroDiez @patrice-conil @eric-murray @shilpa-padgaonkar WDYT?

@bigludo7 (@PedroDiez is on vacation): just to confirm that the scope of #56 is circumscribed to points 1-3. Is it correct?

@jordonezlucena

just to confirm that the scope of https://github.com/camaraproject/Commonalities/pull/56 is circumscribed to points 1-3. Is it correct?

Yes !

Hi,
I propose to close this Issue. Main points have been aligned and addressed within https://github.com/camaraproject/Commonalities/pull/56
@bigludo7, @shilpa-padgaonkar, @rartych, @eric-murray (just thumbs up emoji is enough)
cc @jordonezlucena

Closing this issue


ChemDraw 18-21  不能预测熔、沸点等性质。

您好！首先特别感谢您的成果，给我们使用者提供了方便。
按您的方法试了版本17、18、19、20、21，都比直接替换的好，但有一个问题不知道您是否发现，除了17版，18、19、20、21都不能正常预测分子化学性质（chemical properties）：

这几个版本试了几次，运行COS_Win_Patch时，都是绿色提示通过，应该是正常激活的了。
不知是哪里出了问题？

FYI，我测试了一下mac版本
以methanol为例
没任何问题
[image: image.png]
On Sun, 15 May 2022 at 14:24, Git123HubLee @.***> wrote:

您好！首先特别感谢您的成果，给我们使用者提供了方便。
按您的方法试了版本17、18、19、20、21，都比直接替换的好，但有一个问题不知道您是否发现，除了17版，18、19、20、21都不能正常预测分子化学性质（chemical
properties）：
[image: Snipaste_2022-05-15_14-17-23]
https://user-images.githubusercontent.com/105578334/168459878-2082e643-4be3-4afd-ac19-e7884264581f.jpg
这几个版本试了几次，运行COS_Win_Patch时，都是绿色提示通过，应该是正常激活的了。
不知是哪里出了问题？
—
Reply to this email directly, view it on GitHub
https://github.com/Z-H-Sun/CS_CCME_Posts/issues/9, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJXGGSTI7XQJOGMXB76VR3VKCKARANCNFSM5V6UCZ6Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

[image: image.png]
Just in case，看了下Benzene，也没遇到问题
On Sun, 15 May 2022 at 23:35, Kaijian Law @.***> wrote:

FYI，我测试了一下mac版本
以methanol为例
没任何问题
[image: image.png]
On Sun, 15 May 2022 at 14:24, Git123HubLee @.***>
wrote:

您好！首先特别感谢您的成果，给我们使用者提供了方便。
按您的方法试了版本17、18、19、20、21，都比直接替换的好，但有一个问题不知道您是否发现，除了17版，18、19、20、21都不能正常预测分子化学性质（chemical
properties）：
[image: Snipaste_2022-05-15_14-17-23]
https://user-images.githubusercontent.com/105578334/168459878-2082e643-4be3-4afd-ac19-e7884264581f.jpg
这几个版本试了几次，运行COS_Win_Patch时，都是绿色提示通过，应该是正常激活的了。
不知是哪里出了问题？
—
Reply to this email directly, view it on GitHub
https://github.com/Z-H-Sun/CS_CCME_Posts/issues/9, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJXGGSTI7XQJOGMXB76VR3VKCKARANCNFSM5V6UCZ6Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

换台电脑试了一下，都正常的。
应该我那台PC哪里出了问题。
谢谢你的回复！
Thanks

I have never met such problems, so I have no idea. Maybe just some issue with Windows 11, which I have never tested on.
I am closing this issue. Let me know if there is any update, or anyone else is experiencing the same issue.

确实应该是win11的问题。两台win11都不行，另两台分别win10和win7是正常的。

My goodness，那我早上用win11试试看能复现这问题么。我已经好多年没用Windows版本的chemdraw了
Regards,
Kaijian Lawrence Law
loc
On Fri, 20 May 2022, 21:35 Yoko, @.***> wrote:

确实应该是win11的问题。两台win11都不行，另两台分别win10和win7是正常的。
—
Reply to this email directly, view it on GitHub
https://github.com/Z-H-Sun/CS_CCME_Posts/issues/9#issuecomment-1132910000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJXGGRLRDGZRUD4TVHHWGDVK6ILXANCNFSM5V6UCZ6Q
.
You are receiving this because you commented.Message ID:
@.***>

My impression is that Windows 11 is not a good OS for productivity. I have a laptop shipped with Windows 11. From my observation, I have received Windows Update notifications very frequently, which is not a good sign and indicates the OS is not stable enough. Moreover, I have experienced incompatibility issues with some hardware drives when I connected it with some instruments. Since then, I have decided not to rely heavily on that computer, which I have mainly used to browse the web and reply emails.

On May 20, 2022, at 12:46, Kaijian Laurent Law @.***> wrote:

My goodness，那我早上用win11试试看能复现这问题么。我已经好多年没用Windows版本的chemdraw了
Regards,
Kaijian Lawrence Law
loc
On Fri, 20 May 2022, 21:35 Yoko, @.***> wrote:

确实应该是win11的问题。两台win11都不行，另两台分别win10和win7是正常的。
—
Reply to this email directly, view it on GitHub
https://github.com/Z-H-Sun/CS_CCME_Posts/issues/9#issuecomment-1132910000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJXGGRLRDGZRUD4TVHHWGDVK6ILXANCNFSM5V6UCZ6Q
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.

@Git123HubLee The latest CD 22.0 can display those predictions properly (tested on the latest Win 11). Either Microsoft or PerkinElmer has fixed this bug. I have already uploaded the cracked installer for this latest version in the Baidu/GDrive shared folder, so you can download it from there (and I will also update the article soon).

font{
    line-height: 1.6;
}
ul,ol{
    padding-left: 20px;
    list-style-position: inside;
}

Thank you very much！

<EMAIL_ADDRESS>

---- 回复的原邮件 ----

     发件人

<EMAIL_ADDRESS>

     发送日期

    2022年11月18日 15:29

     收件人

<EMAIL_ADDRESS>

     抄送人

<EMAIL_ADDRESS>        ,

<EMAIL_ADDRESS>

     主题

          Re: [Z-H-Sun/CS_CCME_Posts] ChemDraw 18-21  不能预测熔、沸点等性质。 (Issue #9)

@Git123HubLee The latest CD 22.0 can display those predictions properly (tested on the latest Win 11). Either Microsoft or PerkinElmer has fixed this bug. I have already uploaded the cracked installer for this latest version in the Baidu/GDrive shared folder, so you can download it from there (and I will also update the article soon).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Maybe try updating your Win 11? It is fine on my side (Version 21H2, 22000.1219). See screenshot below.

So I tried CD 20 on Win11, which can also give correct values. Then it should not be PerkinElmer's issue. To further troubleshoot, maybe try the following:

Upgrade Win11
Restore all the cracked programs and use this latest patch to crack chem office again. The older patches might be flawed.
Uninstall and reinstall the .NET framework required by the chem office (for 22.0, the version is .NET 4.8)

非常感谢您的回复。
但我的两台Win11，依然不行，其中一台还重新初始化过。win11内置了 .NET 4.8，试图重新安装4.8、4.81版，但提示已经安装更高版，无法继续。

非常感谢您的回复。
但我的两Win11依然不行，其中一台重新恢复过。chem office也是完全卸载后重新安装的。win11内置了.NET 4.8，试图重装安装4.8、4.81版均提示已经安装更高版，无法继续。

感觉可能有还是其它原因。不知道是否也有其他用户碰到这个样的问题？

What would happen if you click "report"? What does the report say?
I just realize the OS I have been using is still 21H2, so I will upgrade to 22H2 and retest

click "report"：

会出现：
记事本，系统找不到系统路径：

难不成是我把这个改动过？

恢复一下试试

I think it might be better to remove the CJK characters in your temp folder? Basically, CD will open a .tmp file in the %TEMP% folder.

您说的CJK characters，我在temp文件夹下并没有找到。我重新试下17，18，20版，表现各不相同：
17能正常正常预测，点击“report”能正常打开文件，文件名为CP2.tmp，在D:\用户\Temp下。
18不能正常预测，但“report”能正常打开文件，只能里面没有预测的数值。也是在D:\用户\Temp下。

20不能正常预测，点击“report”无响应。
22，就是之前向反映的“report”记事本找不到指定路径，D:\用户\Temp下也生成的文件。chem office安装在C和D盘，结果一样。
实在不行，只能再回到17版用了，因为这个功能我用的比较频繁。
再次感谢您的回复。

您说的CJK characters，我在temp文件夹下并没有找到。

That is not what I meant. I meant to say the Chinese characters "用户" in your path (folder name). But that does not seem to be the major reason, since you said the following:

18不能正常预测，但“report”能正常打开文件，只能里面没有预测的数值。也是在D:\用户\Temp下。

So even if the presence of CJK characters is the reason why Notepad says "cannot find path," there are other things that prevents the prediction of CD.
On a different note, I previously said:

I just realize the OS I have been using is still 21H2, so I will upgrade to 22H2 and retest

I updated my Win11 to 22H2, but on my side, I can still see correctly displayed predictions in the chemical properties window. Therefore, this fact led me to doubt if there is conflict between CD and other software you installed, e.g. anti-virus software: If the anti-virus software blocks the function of, say, CambridgeSoft.ChemOffice.ChemPropPro.dll, then of course you cannot find it working.
Since I cannot reproduce your issue, there is nothing I can further help.
One last thing you can possibly try is installing and running the software in Windows Sandbox, which basically provides the same OS as your physical computer but on an isolated environment so as to exclude influence from other factors like other software you installed.

实在不行，只能再回到17版用了，因为这个功能我用的比较频繁。

Reasonable.

font{
    line-height: 1.6;
}
ul,ol{
    padding-left: 20px;
    list-style-position: inside;
}

很高兴，找到原因了。就是要恢复“临时文件”至C盘默认位置就行了。

<EMAIL_ADDRESS>

---- 回复的原邮件 ----

     发件人

<EMAIL_ADDRESS>

     发送日期

    2022年11月23日 12:32

     收件人

<EMAIL_ADDRESS>

     抄送人

<EMAIL_ADDRESS>        ,

<EMAIL_ADDRESS>

     主题

          Re: [Z-H-Sun/CS_CCME_Posts] ChemDraw 18-21  不能预测熔、沸点等性质。 (Issue #9)

您说的CJK characters，我在temp文件夹下并没有找到。
That is not what I meant. I meant to say the Chinese characters "用户" in your path (folder name). But that does not seem to be the major reason, since you said the following:
18不能正常预测，但“report”能正常打开文件，只能里面没有预测的数值。也是在D:\用户\Temp下。
So even if the presence of CJK characters is the reason why Notepad says "cannot find path," there are other things that prevents the prediction of CD.
On a different note, I previously said:
I just realize the OS I have been using is still 21H2, so I will upgrade to 22H2 and retest
I updated my Win11 to 22H2, but on my side, I can still see correctly displayed predictions in the chemical properties window. Therefore, this fact led me to doubt if there is conflict between CD and other software you installed, e.g. anti-virus software: If the anti-virus software blocks the function of, say, CambridgeSoft.ChemOffice.ChemPropPro.dll, then of course you cannot find it working.
Since I cannot reproduce your issue, there is nothing I can further help.
One last thing you can possibly try is installing and running the software in Windows Sandbox, which basically provides the same OS as your physical computer but on an isolated environment so as to exclude influence from other factors like other software you installed.
实在不行，只能再回到17版用了，因为这个功能我用的比较频繁。
Reasonable.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Cloning of Submodule fails

Looks like submodule https://github.com/elk-zone/elk.git is not public, but needed.
:elephant: :elephant: :elephant: and thanks: Elk is quite pretty and fast! :elephant: :elephant: :elephant:

Hey @jo, Elk is in private alpha. But if you would like to get involved, you're welcome to help us get things ready for opening up. I sent you an invite to the Elk repo and you can join our discord at https://chat.elk.zone

Thank you @patak-dev!

@pro-sumer invited 👍🏼
We're going to open-source Elk in a few days, we should have added this note before. This repo was initially going to be closed too but it was opened because we needed the GitHub actions minutes.


Command flags of inkscape 1.1 have changed

Inkscape 1.1 (currently dev edition) has changed it's option --export-file to --export-filename. This means that current release of inkscape-figures doesn't work with Inkscape 1.1 and latter. I don't know which versions do and don't work and when the change occured.
This is fixed in pull request #19.
Tested with Inkscape 1.1-dev (3a9df5bcce, 2020-03-18).

Thanks a lot! I'll merge your pull request!


⚠ Samsung has degraded performance

In 2191cc8, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2438 ms

Resolved: Samsung performance has improved in 6727dd6.


Document settings in the manual page

Settings settable from ~/.config/dwt/* should be documented in the dwt.1 manual page.

Note that the text for most of them is already present in the README.rst file. It would need to be copied over to the manual page, and completed.


Thanks for open sourcing it!

Just a shout out. Was helpful to find it on Github 👏

One suggestion after I read the code: Add a license so someone can use your software without getting into legal trouble.

Hi! Thanks for the heads up, totally forgot to add the license. I guess MIT will do it.

Done! Thanks for using the library!


Error: No such file or directory "deno"

I've installed Deno and LSP but whenever I try to enable the Deno language server, it throws an error stated in the title of this issue.
OS: Linux Mint 21.2 Cinnamon
(My user configuration is the default one)

Deno binary needs to be available on the PATH in context of Sublime Text. Check https://lsp.sublimetext.io/troubleshooting/#updating-the-path-used-by-lsp-servers on how to solve it.


Update Threefold Chain button navigation after logging in

Description
After logging in, Pressing on Threefold Chain from homepage or sidebar menu will direct you back to the Please connect to your tfchain wallet page while the twin is still logged in.
Logs/Alerts
Untitled_ Jul 27 2023 2_42 PM.webm

still debugging

Verified on devnet.
Now it redirects the user to the homepage of the dashboard and the user stays logged in.
TF DASHBOARD (15).webm


Add other_parties_ledger to the txn snark global state

This PR adds an other_parties_ledger field to the transaction snark's global state, and updates the merge proof to merge this second pair of hashes.
Currently, the values are all empty_hash, pending the ability to generate the required hashes.
Checklist:

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Stale, closing in favour of #12548.


Superscript with Unicode delimiters don't get scaled

Description
When using unicode-delimiters like ⌈ ⌉ to delimit superscript-content, those delimiters aren't scaled to match the content. This is not the case when wrapping the whole thing in another pair of ( ) parentheses, or when using the math.ceil function.
$2^⌈∫_0^1x⌉ + 2^(⌈∫_0^1x⌉) + 2^ceil(∫_0^1x)$

Reproduction URL
No response
Operating system
Web app
Typst version

[X] I am using the latest version of Typst

Duplicate of https://github.com/typst/typst/issues/2979


File export and import

Add to general settings the option to export the file or import the file as .json.

Added on https://github.com/MetlHedd/todolist/commit/644abd0a68e2d3e4c3072261a79407d99aac60bb


77 fix time zone bug in two other places

Ticket
https://github.com/usdigitalresponse/usdr-gost/issues/77
Description
Found the bug in two more places
Screenshots / Demo Video
n/a
Testing
Manual
Checklist

[x] Provided ticket and description
[x] Your PR title contains the ISSUE ticket number e.g "86: ..."
[x] Provided screenshots/demo
[x] Provided testing information
[x] Provided adequate test coverage for all new code
[x] Run automated tests (docker compose exec app yarn test)
[x] Added PR reviewers
[ ] Ensure at least 1 review before merging

@chrisxkeith thanks for doing this! My only small suggestion is to replace timeZone: 'Europe/London' to timeZone: 'UTC'


Add bftpd test server

Lets add another test server.
This one was interesting: Due to a bug it has (it is not an impressive server, to be honest), it uses up its passive port range and then fails. This is why in this docker container the passive port range is a little bit larger, otherwise the tests fail.

Absolutely amazing work! I love adding new servers. Thanks a ton!!


Fix: YamlCreate using invalid filename for downloading

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I'm not familiar with what this code is actually doing? Would you be able to help me understand how it works?

I'm not familiar with what this code is actually doing? Would you be able to help me understand how it works?

I updated the code so that it will not invoke web requests twice.
The script obtains the file name by slicing InstallerUrl variable and appends it to the destinaiton path, but sometimes the url doesn't contain a valid filename, which may cause errors.
For example, if InstallerUrl is set to "https://pinyin.thunisoft.com/webapi/v1/setup/downloadSetup?setupid=21f0e88683894ebcb440759c5aa25c47&filename=HuayuPY-V<IP_ADDRESS>.exe", the script will slice it into "downloadSetup?setupid=21f0e88683894ebcb440759c5aa25c47&filename=HuayuPY-V<IP_ADDRESS>.exe", which contains an invalid file name character "?".
Many servers tell the client the real file name by adding a "ContentDisposition" field to the response header. If existed, the modified code will use it instead.

Why not just name the file {PackageIdentifier}.{PackageVersion}.{extension} like winget does? You'll have to write in what the extension is for each installer type, but that way you don't have to rely on a header.  (Or just name it "temp" or something, the extension doesn't really matter for this case I guess).
I'm fine with this, but I'm just afraid if someone didn't configure their web server correctly you could still get a yucky name.


Add strong typing for events emitted by login targets

Also moves the event emitter methods to .events as opposed to inheritance.

:rocket: PR was released in v0.2.0 :rocket:


Add acsch to library

Resolves # .
Description

RFC for inverse hyperbolic cosecant

This pull request includes:

the main function
benchmark
examples
tests
readme
doc

Please ensure the following tasks are completed before submitting this pull request.

[ ] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@ArashST79 You mind checking the box above to indicate that you've read the contributing guidelines? In particular, checking this box means agreeing to the licensing terms.

The functionality proposed in this PR was added in https://github.com/stdlib-js/stdlib/pull/486. Closing...


Expose /internal functions

Is it possible to expose some of the functionality in /internal so that other go projects can make use of it by importing?

Thanks for your comment. If someone needs the functions of the internal package, sure I would expose them or create a library.

@srlehn Is the commit 3836b73e2a201ac8ab906ab9c1ad09c8e0f89541 solving this issue?


Ontario epicurves

add graph of cases by reported date by situation
add graph of projection infection date

@anomal you now have authority to merge your own PRs, which might be helpful for minor changes or bug fixes.
Thank you so much for contributing to this project.  🙇  Cheers


Support HPA

Proposed changes
Support HPA

Types of changes

New feature (non-breaking change which adds functionality)

Linked Issues
https://github.com/rancher/rancher/issues/16214

Further comments

Updated. Thanks!

backend is in


Upgrade to v1.11.1 of the Linode Terraform Provider

Fixes: #64

Closing this as we need to take into account the new api_version work


#22 avoid repetitive call $this->_calculatePageCount() in count() method if count equals zero

#22

Duplicates #25

@froschdesign you are right my PR is duplicating #25 but my PR contains tests which tests the repetitive call of Zend\Paginator\Paginator::_calculatePageCount() unlike the PR #25. Please consider merging of my ZendTest\Paginator\PaginatorTest::testRepetitiveCallCountResultingZeroDoesNotCauseRepetitiveCallOfCalculatePageCountMethod()

I've seen it and I prefer your test in this special case.

thanks :)

@fedys
Can you simplify the test method name? Maybe replace "RepetitiveCallCountResultingZero" with "CountResultOfZero" or something shorter.

Can you simplify the test method name?

Just a note: as a general rule, the more descriptive the name, the better. Test names should indicate the behavior being tested.

Thanks, @fedys!


Fix typos and prettify md/yaml

Resolved via commands:

codespell .
prettier -w .

Hi @kianmeng thank you for the contribution! Would you be willing to add these into the pre-commit hooks? It looks both codespell and prettier are supported. The config file is here. Let me know if you need any pointers!


Refine configurations, Fix tsc / eslint errors

Refine configurations

typescript configuration(tsconfig.json)

Remove unnecessary options
Include "dist" folder to "exclude" property

Fix errors

Fix tsc errors
Fix eslint errors
Refactor indent

Question

I looked at the the src/simstance/SimstanceManager.ts, the keyword storege means actually storage?
What is the word renderd() mean in src/SimpleApplication.ts?

q1 : storege -> storage
q2 : renderd() -> After hashchange event, all modules finish rander
Method called for last post processing.


Potential memory leaks in a file.

https://github.com/facebook/infer/blob/89040bee1c53f2fe67edb70717561fb370202502/infer/tests/codetoanalyze/cpp/shared/constructors/constructor_new.cpp#L27-L30
https://github.com/facebook/infer/blob/89040bee1c53f2fe67edb70717561fb370202502/infer/tests/codetoanalyze/cpp/shared/constructors/constructor_new.cpp#L32-L35
https://github.com/facebook/infer/blob/89040bee1c53f2fe67edb70717561fb370202502/infer/tests/codetoanalyze/cpp/shared/constructors/constructor_new.cpp#L37-L40
Not sure how often is this file used, but are these not  cases of potential Memory Leaks. Why are we creating pointer to the objects. Can we replace them with.
type variable_name(initial_value);

@jberdine

These are tests meant to specifically test that infer understands the behaviour of new(). It doesn't matter that they are creating potential memory leaks.


Fix MPO to term list (one off error in max_range)

Adding a test to #477.

Adding a test to #477.

Thanks for adding the test! Looks great to me—let's merge it!


Remove gp3 from supported EBS volume types for in-tree provisioner "kubernetes.io/aws-ebs"

gp3 is not supported for the in-tree plugin "kubernetes.io/aws-ebs", only for external EBS CSI driver. So we have to remove it here
See following issue which shows that it does not work:
https://github.com/kubernetes/website/issues/33036#issuecomment-1110766774

Thanks!
We'll need you to sign a license agreement @youwalther65 - see https://github.com/kubernetes/website/pull/33256#issuecomment-1110825243

/approve

/sig storage
/lgtm
based on https://github.com/kubernetes/website/issues/33036


Update x86 runner to macOS13

The macOS 12 runner image will be removed by December 3rd, 2024.
This PR will update the existing runner to macOS13.

@andreivladmatei could we rebase this to main 🙏

I don't follow, it's up to date with main

This pull request appears based on an unmerged branch. It shows as 4 commits ahead of main:


[docs][App Bar]: AppBarWithResponsiveMenu logo href link

[ ] I have followed (at least) the PR section of the contributing guide.

Error when clicked  LOGO in below example Appbar
https://mui.com/material-ui/react-app-bar/#app-bar-with-responsive-menu

Replicated the error in local

I saw there is an issue on this and some one already assigned to it
https://github.com/mui/material-ui/issues/38412

It seems a reasonable solution. Is it working locally?
You should provide a label to pass the remaining test.

It seems a reasonable solution. Is it working locally?
You should provide a label to pass the remaining test.

diff --git a/docs/src/modules/utils/helpers.ts b/docs/src/modules/utils/helpers.ts
index d8c774cfa6..0057c707e9 100644
--- a/docs/src/modules/utils/helpers.ts
+++ b/docs/src/modules/utils/helpers.ts
@@ -100,7 +100,13 @@ export function pathnameToLanguage(pathname: string): {
   // Remove hash as it's never sent to the server
   // https://github.com/vercel/next.js/issues/25202
   const canonicalAsServer = canonicalAs.replace(/#(.*)$/, '');
-  const canonicalPathname = canonicalAsServer.replace(/^\/api/, '/api-docs').replace(/\/$/, '');
+  let canonicalPathname = canonicalAsServer.replace(/^\/api/, '/api-docs');
+
+  // Remove trailing slash as Next.js doesn't expect it here
+  // https://nextjs.org/docs/pages/api-reference/functions/use-router#router-object
+  if (canonicalPathname !== '/') {
+    canonicalPathname = canonicalPathname.replace(/\/$/, '');
+  }

   return {
     userLanguage,


wsgidav.response_headers only added to GET/HEAD requests

The custom headers should be included in every response, not only when using GET/HEAD.
https://github.com/mar10/wsgidav/blob/08768f6c4364021a3b1f4da8866960469e7e78a9/wsgidav/request_server.py#L1593-L1598
Also, res.finalize_headers() should be called.

Can you give a use case? #90 seems to be ok with setting headers on every request. I am not sure if this is always the case and we might need to extend the configuration?

#90 talked about the "Access-Control-Allow-Origin" header. Adding this header to the response_headers configuration currently does not help at all, as for CORS to work (https://developer.mozilla.org/de/docs/Web/HTTP/CORS), the headers must be added to every request. Currently, they are only added to GET and HEAD requests. CORS is actually a little bit more complex, so maybe there should be a middleware for that, but still I think response_headers should be applied to every request.
Trying to do a CORS request from the browser:

response_headers added to GET:

response_headers not added to OPTIONS:

response_headers not added to PUT:

For my use-case I actually tried to achieve setting a cookie from a Directory Controller (verifying basic auth credentials on every request is very expensive using modern password hash algorithms) and some clients support sending cookies instead. I "fixed" this by caching a hash of the username+password combination in memory using a faster hash algorithm (blake2) and storing that hash (and the auth result) for 60 seconds. Therefore, clients that send many requests at once (like macOS Finder when unpacking a ZIP file on a WebDAV drive) does not require hashing the password all the time.

Started a branch: append_custom_headers


Would it help if I had more "ground truth" masks?

Hi,
I have the "grounds truth" masks for all the frames (without tracking).
Would it be possible/helpful to add more "ground truth" masks for the DeAOT tracking? At the moment the tracking is done from the first ground truth mask frame
Thanks,
Renaud

DeAOT/AOT supports using multiple reference frames during inference. The method is simple. You can place all the inference frames in the mask folder. During the inference, the algorithm will paste the reference frame to the predicted mask and cover your prediction.
I designed this function since, in some videos, some objects may not appear in the first frame but in one of the middle frames.

I designed this function since, in some videos, some objects may not appear in the first frame but in one of the middle frames.

@z-x-yang What about if the optimal reference frame is not frame 0? I see that the evaluator it is strictly forward only and it assume frame 0 reference frame.


[Enum Request] Table 10752 "SII Doc. Upload State" Field "Document Source"

Dear AL Team,
To improve SII Spanish functionality we need this option field as an enum.
Best Regards

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Fix XdsClient for multiple watchers on the same resource

Fix #28468

Why does the use of XdsCredentials matter for the RBAC NACK tests?

Why does the use of XdsCredentials matter for the RBAC NACK tests?

The NACKing infrastructure uses the WaitForNack() which uses the default RPC sending infrastructure instead of the one specialized for server testing, which causes inconsistencies in what the clients and the servers expect from each other in terms of credentials. Disabling XdsCredentials means that both clients and servers would use fake credentials.

@markdroth Please take another look. This should fix the bug for RDS updates where the response does not need to include all the resources. Instead of using separate balancers for clients and servers, I simply keep track of whether an individual resource has been ACKed or NACKed. This approach seems to be more flexible.

I simply keep track of whether an individual resource has been ACKed or NACKed.

I don't think this approach makes sense.  At the protocol level, it is not currently possible for the client to specify which individual resource it is ACKing or NACKing, so the server cannot possibly know how to record which resource has been ACKed or NACKed.  The protocol allows only ACKing or NACKing a complete response, but that does not mean that the client has rejected every single resource in that response; it means only that the client has rejected at least one of the resources in the response, but the server has no way of knowing which of the resources in the response were accepted and which were rejected.  So it's very misleading for the server to provide an API that implies that it does know that.
(As it happens, in the long term, we do actually want to change the protocol such that the client can explicitly indicate which individual resource(s) are being rejected.  And once we do that, this sort of interface might make sense.  But until then, I don't think it makes sense.)
I can think of two possible alternatives here.
Option 1: Server maintains a queue of client responses
The server maintains a queue of ACK/NACK responses from the client for each resource type.  It can provide a method like this to access the client responses:
// Waits for a client response for the specified resource type.
// If no response is seen by the time the timeout elapses, returns absl::nullopt.
// Otherwise, returns the response.
absl::optional<ResponseState> WaitForClientResponse(absl::string_view resource_type, absl::Duration timeout);

The implementation of that method will probably be somewhat similar to LrsServiceImpl::WaitForLoadReport().
Then you can change the WaitForNack() methods to be a simple loop that repeatedly calls WaitForClientResponse() until it sees either a NACK or a timeout.  That way, if the server sees an ACK from another client, we'll just ignore that response and keep waiting for the NACK that we're expecting.
The down-side of this approach is that it will ignore spurious ACKs, so the test would still pass if the client incorrectly sent an ACK and then a NACK.  But the odds of that happening aren't that high, and ultimately the current ACK/NACK semantics are fuzzy enough that that would probably be okay behavior anyway.
Option 2: Use a different xDS server for the client and server
Now that #27938 has been merged, you can change the tests to just use a different xDS server for the client and server.
This isn't as general of a solution as option 1; instead of fixing the WaitForNack() infrastructure to handle this problem for all callers, it would require that we explicitly change all affected callers to use a separate xDS server for the client and server.  However, there aren't a huge number of tests that both call WaitForNack() and have both xDS-enabled client and server, so the cost of being less general isn't that high.  And this option would avoid the problem of incorrectly accepting spurious ACKs that we'd have with option 1.
I think I could live with either option, so feel free to pick between them (or suggest another alternative).

Updated to save a vector of updates for each resource type.

Thanks for reviewing!


[python] Temporarily pin to AnnData 0.9.*

As of Friday all Python CI is failing like this:
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/6434852473/job/17474905281
E   ImportError: cannot import name 'SparseDataset' from 'anndata._core.sparse_dataset' (/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/anndata/_core/sparse_dataset.py)

This is a nuanced issue with a nuanced solution in discussion between @nguyenv , @thetorpedodog , and myself.
It will be dealt with soon, however, to unblock CI and high-pri PRs over the next day or two I will temporarily pin to AnnData 0.9. This issue will be kept open for tracking until the issue is dealt with properly.

Closing in favor of #1785 for longer-term tracking


Hi, have you solved this issue?

Hi, have you solved this issue? I encountered this problem when training on Sceneflow.

yes，I solved it by https://github.com/ibaiGorordo/CREStereo-Pytorch
and,there is not much difference in their effectiveness after 500 epoch

Hi, have you solved this issue? I encountered this problem when training on Sceneflow.

besides,I think it's the lack of memory that causes it NAN.You can try to solve this problem

Hi, have you solved this issue? I encountered this problem when training on Sceneflow.

besides,I think it's the lack of memory that causes it NAN.You can try to solve this problem

Thanks! I haved tried in this way. Train on RTX3090, and the batch size is 1. NaN still appeared after few iterations.

Hi, have you solved this issue? I encountered this problem when training on Sceneflow.

yes，I solved it by https://github.com/ibaiGorordo/CREStereo-Pytorch and,there is not much difference in their effectiveness after 500 epoch

Thank you for your reply! I will try in this way.

Hi, have you solved this issue? I encountered this problem when training on Sceneflow.

besides,I think it's the lack of memory that causes it NAN.You can try to solve this problem

Were you able to reproduce their performance with the pytorch implementation? I tried that repo you mentioned, but I'm still suffering from Nan loss after some epochs. If you were able to reproduce, what datasets did you use? Please specify the sub-datasets such as "monkaa", and "clean" or "final" versions you used. Thanks!

@deephog
I used https://github.com/ibaiGorordo/CREStereo-Pytorch and solved NAN. I use the datasets of Baidu Web disk provided by the author (Download from BaiduCloud here(Extraction code: aa3g) and extract the tar files manually).This is the result after 200 epochs

@deephog I used https://github.com/ibaiGorordo/CREStereo-Pytorch and solved NAN. I use the datasets of Baidu Web disk provided by the author (Download from BaiduCloud here(Extraction code: aa3g) and extract the tar files manually).This is the result after 200 epochs

Did you compare the final results to the pre-trained model they provide? I can get similar results, but I can never get as good as theirs

@deephog I used https://github.com/ibaiGorordo/CREStereo-Pytorch and solved NAN. I use the datasets of Baidu Web disk provided by the author (Download from BaiduCloud here(Extraction code: aa3g) and extract the tar files manually).This is the result after 200 epochs

Did you compare the final results to the pre-trained model they provide? I can get similar results, but I can never get as good as theirs

I'm sorry，This is what I did a few months ago，I only remember that after 500 epochs the results were more or less adequate for my needs.However, in general, the author's pre-trained model is the best, and it is normal that you cannot achieve the author's results.


Implement a Garbage Collection Strategy for Processors

This is potentially linked to #4 depending on which solution we end up going with there.


Test for Coverage

Please prefix your pull request with one of the following: [FEATURE] [FIX] [IMPROVEMENT].
In raising this pull request, I confirm the following (please check boxes):

[ ] I have read and understood the contributors guide.
[ ] I have checked that another pull request for this purpose does not exist.
[ ] I have considered, and confirmed that this submission will be valuable to others.
[ ] I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
[ ] I give this submission freely, and claim no ownership to its content.

My familiarity with the project is as follows (check one):

[ ] I have never used the project.
[ ] I have used the project briefly.
[ ] I have used the project extensively, but have not contributed previously.
[ ] I am an active contributor to the project.

{pull request content here}

Codecov Report
Patch coverage: 78.26% and project coverage change: -0.10 :warning:

Comparison is base (85b03e3) 83.25% compared to head (3844c13) 83.15%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   83.25%   83.15%   -0.10%
==========================================
  Files          36       36
  Lines        3678     3675       -3
  Branches      741      434     -307
==========================================
- Hits         3062     3056       -6
- Misses        475      477       +2
- Partials      141      142       +1

Flag
Coverage Δ

unittests
83.15% <78.26%> (-0.10%)
:arrow_down:

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

Impacted Files
Coverage Δ

mod_ci/controllers.py
71.25% <70.58%> (-0.31%)
:arrow_down:

mod_auth/controllers.py
84.39% <100.00%> (ø)

mod_ci/cron.py
100.00% <100.00%> (ø)

mod_customized/controllers.py
97.36% <100.00%> (ø)

mod_test/controllers.py
71.57% <100.00%> (-0.15%)
:arrow_down:

mod_upload/controllers.py
74.34% <100.00%> (ø)

... and 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Additional CSC Updates

This patch cleans up some of the CSC flags as well as no longer prints out the full help text when a command is in error.

Hi @lpabon,
Per your suggestion I did end up changing the behavior of a command with an error to print only the error followed by a short blurb about using the -h,--help flag for more information.


Is there a way to limit RAM?

As in the title. My server always restarts because the RAM is full load. Is there no way to limit the server RAM?

limit what? ask your game.
for example, for minecraft, use -Xmx 1G to limit minecraft(exactly jvm) ram usage.

limit what? ask your game.
for example, for minecraft, use -Xmx 1G to limit minecraft(exactly jvm) ram usage.

i know i limit my ram to 7G but yeah that not working. and i checking docker thats exactly like i want but thats always generated error

do not ask here. it's not our problem.

emm this?

ahh. my fault. Sorry, it turns out I just need to install Docker as usual


Should auth options be using IOptionsMonitor?

Currently we are using IOptionsSnapshots which have scoped lifetimes, so the instances will get recreated every request via IOptionsFactory.  If we want longer lifetimes, we could switch to IOptionsMonitor, which would would leave lifetime up to the IOptionsMonitorCache.
Downside is, scoped IConfigureOptions won't be run every request for auth which was also something we wanted to support.

Please keep in mind that this functionality is desirable for those of us doing multitenancy.  See this comment from the auth redesign issue for the specific strategy that I am referring to.

What functionality is desirable?  That you want to reconfigure options for every request?

Currently we are using IOptionsSnapshots which have scoped lifetimes, so the instances will get recreated every request via IOptionsFactory.

WTF? This is a HUGE regression! In practice, this means that options configuration classes will be run for every handler+requests even when options are supposed to be static (I just confirmed this new behavior when moving my ASOS port to the latest bits including the events changes...)
Related posts:

https://github.com/aspnet/Security/pull/1065#issuecomment-271478610
https://github.com/aspnet/Security/pull/1065#issuecomment-271480850

What functionality is desirable? That you want to reconfigure options for every request?

I have not been able to follow the changes super close, but I thought IOptionsSnapshot was the go forward strategy (at least in 2.0) to switch the security settings per tenant on each request.  That's what the link I pointed to showed.  Has that changed?  If so what's the new plan?

@RickBlouch even if we switch to IOptionsMonitor, you could still get similar behavior to the IOptionsSnapshot by replacing IOptionsMontiorCache with a scoped instance, that would result in in the options being recomputed every request.

@Eilon Copying you per discussion today.

After discussing with @Tratcher we'll switch Auth back to the old behavior (meaning switching to IOptionsMonitor).  OpenIdConnect metadata + RemoteAuthentication.Backchannel both will fall over if new instances are created every request.  There will still be a way for developers to opt into per request options if they really want, they could do this by changing IOptionsMonitorCache<TOptions> to be a scoped lifetime for the specific scheme they wanted to recreate per request.

After discussing with @Tratcher we'll switch Auth back to the old behavior (meaning switching to IOptionsMonitor).

This should have never changed in the first place, specially since this issue had been clearly identified during the initial 2.0 design. I'm really surprised this change passed the review stage... :trollface:

Yeah there's a test hole as there's no formal requirement in the form of tests that enforce this requirement for the auth handlers, so the options breaking change to snapshot didn't cause any issues.  But I did file this issue for followup :)

Yeah there's a test hole

"hole" is an euphemism, as many aspects of the OIDC handler are not tested at all (https://github.com/aspnet/Security/issues/772) :trollface:

Yup, I've pointed that out in the past :)


Silo Writer Spews Uninformative Error Messages

I am trying to export a mesh I created with blueprint.
This occurs on the most recent version of develop.
If I am doing something wrong here, better error messages should tell me what that is.
If I am not doing anything wrong, then whatever is causing this to fail should be fixed.

Any chance you can attach exported results here?
Were you using default export options for Silo? If not, what options were you using?
I might be able to explain 5 (ndomains=5) instances of that error message but not 6.
That said, I wonder if the problem is we are passing a string like mesh_topo/dist to a Silo DBPutXxx() call without having made the intervening directory(s).
What if you create the expression mydist as alias for mesh_topo/dist and export just mydist?

These are the export options used:

Here are the files VisIt generated:
silo_files.zip

When I create an expression mydist as an alias for mesh_topo/dist and choose it as the variable to export, it works as expected.


feat: option implementation

Codecov Report

Merging #1 (d991c99) into main (173a9f6) will decrease coverage by 3.36%.
The diff coverage is 80.00%.

@@             Coverage Diff             @@
##              main       #1      +/-   ##
===========================================
- Coverage   100.00%   96.63%   -3.37%
===========================================
  Files           10       11       +1
  Lines           99      119      +20
===========================================
+ Hits            99      115      +16
- Misses           0        4       +4

Impacted Files
Coverage Δ

option/option.go
80.00% <80.00%> (ø)

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 173a9f6...d991c99. Read the comment docs.


metatab.org down?

I'm getting "Error establishing a database connection" when I visit: http://metatab.org/

Thanks! Fixed.


[COR-866] Spike: Determine how users can claim extensions

Users should be able to claim ownership of extensions that we've published. We need a way to verify they are the rightful owner.
From SyncLinear.com | COR-866

If users log in with Github, can we check if they are Owner of the repo, if yes then grant?


Play better with BugSee

We use BugSee in some projects for test builds to more-invasive-but-more-useful error reporting, but Steamclog/Sentry doesn't always play well with it (can have problems if both Sentry and BugSee are on at the same time, if the project isn't using BugSee we probably DO want to be capturing Sentry info in test builds by default, etc.)
There's a broad range of potential solution here, ranging from just coming up with some guidelines here, all the way to potentially just integrating BugSee into Steamclog as well and making the default behaviour correct out-of-the-box.

Looks like we've already filed this ticket.
Here's a recent discussion on a crash discovery and later another suggestion to include to Bugsee:
https://steamclock.slack.com/archives/C0WL7G3JL/p1649969406222429

Hi @brendanlensink @jenncoop when you have time, I would like to get your feedback on this. Thanks! I could try to implement this for us.

I'm a little hesitant to get behind integrating Bugsee straight into SteamcLog, given that we just spent some time decoupling Sentry from SteamcLog. Maybe it's different enough as an internal tool that it's worth doing?
Maybe it would be worth looking at how we're setting up SteamcLog and making it more modular, then allowing users to set up integrations with things like Sentry/Bugsee using custom Destinations?

Yeah, I think we are actually a fair bit more likely to want an alternate production logging library (i.e. Sentry vs. Rollbar) than a more internal debugging tool like this, so I don't think that it's as important to make Bugsee replaceable, HOWEVER it's likely that any logging library that does crash handling is going to have that same issue that Sentry does of needing some co-ordination with BugSee at init time, so at least the way we handle the initialization needs to be modular enough that any replacement destination that might support crash reporting has some way to know that BugSee is active and turn off it's own crash reporting.

I no longer think it’s a good idea to integrate Bugsee as well. I don’t know how yet, but I am also in favour of figuring out a way to make the ordering of init more resilient to crashing when Bugsee is involved.


more information needed under: Couldn't retrieve the data for this visual. Please try again later.

"Couldn't retrieve the data for this visual. Please try again later."
This error is displayed consistently when a report consumer accesses a report which uses Direct Query over Power BI datasets connection and lacks build permission to the underlying dataset.
https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-datasets-azure-analysis-services#considerations-and-limitations
"Build permissions are required to view reports built using this feature when one or more datasets in the chain are in Pro workspaces."

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

ID: d6fe0913-78f9-47f1-ead1-dbecb17127d6
Version Independent ID: 5828f2fc-25ae-18d8-a9ac-786511478fbe
Content: Troubleshooting tile errors - Power BI
Content Source: powerbi-docs/connect-data/refresh-troubleshooting-tile-errors.md
Service: powerbi
Sub-service: pbi-data-sources
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @fpk3. This issue has been assigned to the doc author for review.

Thanks for your comment. This looks like a support request rather than documentation feedback. You might find a solution in the Power BI Community, found at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.

Hi David,
This is NOT a support request, but I understand that you closed the issue.
I've seen this error many times, and it's never transient.
It always has to do with DirectQuery.
The most common cause of this error showing up was the requirement for
build permission for composite data models.
Now that composite models has gone GA, that requirement has been removed,
and therefore the error will not recur in that context.
These are the remaining two cases:
#2. one dataset in composite model has been deleted.
#3. Gateway data source offline for DirectQuery model.
For more information on the situations when this error occurs, please see:
https://www.fpk3.com/blog/power-bi-tile-error-couldnt-retrieve-data-visual-please-try-again-later
On Mon, Apr 17, 2023 at 10:43 AM David Iseminger @.***>
wrote:

Thanks for your comment. This looks like a support request rather than
documentation feedback. You might find a solution in the Power BI
Community, found at https://community.powerbi.com. If not, you can get
support by going to https://support.powerbi.com.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/powerbi-docs/issues/4401#issuecomment-1511622904,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ66PP3LLZXTU3DJSNHHGBLXBVQI7ANCNFSM6AAAAAAVVPJS7M
.
You are receiving this because you were mentioned.Message ID:
@.***>

@fpk3 - the requirement for build permissions have not been removed fully, so it looks like your Pro workspaces still require Build permissions.
Quote from the blog:
"
When we started the preview, any consumer of a report that leveraged a composite model based on a Power BI dataset was required to have Build permissions or the Contributor role. Since then, we have changed this for Premium and PPU workspaces: readers of reports based on datasets in Premium or PPU workspaces just require Read permissions (or the Viewer role).
However, for most Pro workspaces Build permissions are still required in the scenario above. We are making backend changes to align the Pro workspaces with the Premium and PPU workspaces so everyone consuming these reports will just require Read permission or the Viewer role, regardless of the workspace type the data is stored in."

Thanks for the clarifications - closing this issue, and @fpk3 now you should have the info you need. Thanks all!


prefer runtime_dir instead of home_dir for cached credentials

runtime_dir is in RAM on most (linux) systems, so is better suited for
temporary credentials.

In this change I've implemented a more functional style of handling optional values (instead of the more imperative matches/conditionals), if you feel this way is more readable, I can change some other occurrences of the same pattern.
I didn't look to much into the places where cache_dir is used, but it might be a better idea to keep it as PathBuf instead of a String (would make this code simpler too). What do you think?

@gdamjan thanks once more for the PRs 😄

runtime_dir is in RAM on most (linux) systems, so is better suited for temporary credentials.

I found it nice, I'd have to read a bit more about it, but AFAIU if you use something on RAM would it be persisted across usages of the binary?
Like, the whole purpose of the cache is to avoid creating new tokens (and requesting the MFA on my scenario) every time you want to run the command again.

In this change I've implemented a more functional style of handling optional values (instead of the more imperative matches/conditionals), if you feel this way is more readable, I can change some other occurrences of the same pattern.

I wanted to do that too eventually, yet I'm still not quite familiar with rust since I've been only in the middle of The Rust book, feel free to open PRs, I find functional style much easier to read/write for sure. I was just evolving the code as I was learning something new from the Rust Book.

I didn't look to much into the places where cache_dir is used, but it might be a better idea to keep it as PathBuf instead of a String (would make this code simpler too).

Yeap, eventually I was considering either using Path or PathBuf, we can totally change that, makes more sense type-wise.

I found it nice, I'd have to read a bit more about it, but AFAIU if you use something on RAM would it be persisted across usages of the binary?

it's persistent until you logout or reboot.

I've added a commit to change Cache::dir to a PathBuf. I like how it simplified the parse function.
Although it's perhaps more logical to be a Path, I'd have to investigate how to store it in a structure.


docs: update transfer docs with support for path forwarding

Description

The docs as they were pre-ICS20v2 have been moved to the ICS20 v1 folder.
closes: #6608

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

I will merge this one now, and open a PR to update when https://github.com/cosmos/ibc-go/pull/6841 is merged (or I can update the docs there as well).


Support non-uniform tile pixel ratios

This is an alternative to #13593 for supporting non-uniform pixel resolutions.
In #13593, the tile grid is updated to know about non-uniform resolutions.  In this branch, the source and tile textures are updated to support non-uniform pixel ratios, modifying the tile sizes returned by the tile grid.

I don't think is it necessary to allow tilePixelRatio arrays in anything other than DataTile/GeoTIFF sources.  The only use in image tiles is to request larger images for WMS and ArcGISRest and to render to larger image canvas.  Single numbers could be converted internally to arrays using toSize() where arrays are expected.

This also introduces conflicts with #13609 which fixes incorrect dependence of pixel ratios in favour of using the real image size.

I opened this to demonstrate (to myself at least) that the tilePixelRatio approach was not a good one.  And I'm convinced.


H6008 Unsupported Cmd Value,

The integration finds H6008 bulbs and are available in home assistant. The bulbs turn on and off and display the correct color in home assistant. However, I cannot change the color from home assistant. It causes all bulbs to lose connection temporarily. Waiting a few moments and the bulbs work again. The log is posted below.
Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/govee_lan/light.py:330
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 9:24:10 PM (13 occurrences)
Last logged: 9:42:43 PM
[139816948107856] failed to control device: Rate limit exceeded, retry in 25 seconds.
[139816948107856] failed to control device: Rate limit exceeded, retry in 30 seconds.
[139816541358544] failed to control device: Unsupported Cmd Value, please check the value of properties.colorTem.range returned by DeviceList
[139816494839056] failed to control device: Rate limit exceeded, retry in 43 seconds.
[139816494839056] failed to control device: Unsupported Cmd Value, please check the value of properties.colorTem.range returned by DeviceList
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 205, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1965, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2005, in _execute_service
return await cast(
^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 848, in entity_service_call
response_data = task.result()  # pop exception if have
^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1192, in async_request_call
return await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 892, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 582, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/config/custom_components/govee_lan/light.py", line 330, in async_turn_on
await self._govee_controller.set_color_temperature(
File "/usr/local/lib/python3.11/site-packages/govee_led_wez/govee.py", line 619, in set_color_temperature
await asyncio.wait_for(
File "/usr/local/lib/python3.11/asyncio/tasks.py", line 479, in wait_for
return fut.result()
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/govee_led_wez/http.py", line 105, in http_device_control
raise RuntimeError(f"failed to control device: {message}")
RuntimeError: failed to control device: Rate limit exceeded, retry in 43 seconds.

The error message makes it sound like you're trying to set a color that is out of the supported range of the device.
Can you manually probe your device capabilities and share the info here?
See: https://github.com/wez/govee-lan-hass/issues/7#issuecomment-1378904151
and also share information about what color/color temperature you were trying to set when you hit that error.

The list devices result is below. I uninstalled and reinstalled after a day and everything worked again. I think the integration stops working because of the rate limit. I may have a device with weak wifi. Could that is trigger a rate limit issue?
As for the colors, I'm using the integrated color picker.
{
"data": {
"devices": [
{
"device": "16:BC:D2:39:32:35:1A:38",
"model": "H7050",
"deviceName": "Path",
"controllable": true,
"retrievable": true,
"supportCmds": [
"turn",
"brightness",
"color",
"colorTem"
],
"properties": {
"colorTem": {
"range": {
"min": 2000,
"max": 9000
}
}
}
},
{
"device": "F7:E1:D4:AD:FC:D0:FE:6E",
"model": "H6008",
"deviceName": "Bar 1",
"controllable": true,
"retrievable": true,
"supportCmds": [
"turn",
"brightness",
"color",
"colorTem"
],
"properties": {
"colorTem": {
"range": {
"min": 2700,
"max": 6500
}
}
}
},
{
"device": "4E:6F:D4:AD:FC:DB:DC:E2",
"model": "H6008",
"deviceName": "Bar 2",
"controllable": true,
"retrievable": true,
"supportCmds": [
"turn",
"brightness",
"color",
"colorTem"
],
"properties": {
"colorTem": {
"range": {
"min": 2700,
"max": 6500
}
}
}
},
{
"device": "E5:9F:D4:AD:FC:E8:16:94",
"model": "H6008",
"deviceName": "Master 2",
"controllable": true,
"retrievable": true,
"supportCmds": [
"turn",
"brightness",
"color",
"colorTem"
],
"properties": {
"colorTem": {
"range": {
"min": 2700,
"max": 6500
}
}
}
},
{
"device": "3F:9D:D4:AD:FC:E8:15:2E",
"model": "H6008",
"deviceName": "Master 1",
"controllable": true,
"retrievable": true,
"supportCmds": [
"turn",
"brightness",
"color",
"colorTem"
],
"properties": {
"colorTem": {
"range": {
"min": 2700,
"max": 6500
}
}
}
}
]
},
"message": "Success",
"code": 200
}

I have the roughly the same problem but I am using the mushroom light card.
Error excerpt:
async_turn_on failed with 'API-Error 400 on command ('name': 'colorTem', 'value': 9000}: {'message": "Unsupported Cmd Value, please check the value of properties.colorTem.range returned by DeviceList" "status":400} for device GoveeDevice (device='44:26:60:74:F4:44:8 model='H6008, device_name=lounge light',.........truncated.

The reported color temperature range is:
                "properties": {
                    "colorTem": {
                        "range": {
                            "min": 2700,
                            "max": 6500
                        }
                    }
                }

but it looks like you are trying to set it to 9000 'name': 'colorTem', 'value': 9000, so the device is failing that request.
The easiest thing you can do for now is not try to set it larger than the max.  I do think it would be reasonable to clamp the value to the supported range.

I think it is something someone could do as a PR to either or both of govee-lan-hass (perhaps there is a way to tell hass about the acceptable range of values) and/or https://github.com/wez/govee-py (where the value could be clamped into range).
I don't currently have time to do either of those things.

I have no plans to fix that here in this integration, but I do want to note that my new Govee2MQTT AddOn does handle clamping the color temperature to the range reported by the device so you may wish to consider moving to that.


Translation support + english

Rewrote mod code to support translations
Rewrote datapack code to support translations
Added English translations for both mod and datapack
Minor tweaks for Russian translation (Например бутылочка мёда -> мёд, т. к. бутылочки не едят :) )
Russian translation is moved into mod assets to exclude the need of an extra resourcepack

Big thanks!


Terminal indicator for pwsh doesn't get clear if use shortcut Ctrl+L.

Steps to Reproduce:
1.Use pwsh
2. Clear it using Ctrl+L instead of clear command

it works for me for pwsh on macOS

The fix for this is probably the same as suggested in https://github.com/microsoft/vscode/issues/153476#issuecomment-1203813334

/duplicate https://github.com/microsoft/vscode/issues/198776


fixed typo

Coverage remained the same at 0.0% when pulling 339ea28e3fb4f59c7718f50cd9e3895bea930c2a on paulhfischer:typo into 6a5be8b72d84037b83a5ea838e17bcf372ab1d5f on saitoha:master.


fp8 leads to black images (numerical instabilities) for transformer diffusion models

I am on the main of quanto.
from diffusers import DiffusionPipeline
import torch
from optimum.quanto import quantize, freeze, qfloat8_e4m3fn

pipeline_id = "PixArt-alpha/PixArt-Sigma-XL-2-1024-MS": "pixart"
pipeline = DiffusionPipeline.from_pretrained(
    pipeline_id,
    torch_dtype=torch.float16
).to("cuda")

quantize(pipeline.transformer, weights=qfloat8_e4m3fn)
freeze(pipeline.transformer)

image = pipe(
    prompt="ghibli style, a fantasy landscape with castles",
    num_images_per_prompt=1,
    generator=torch.manual_seed(0),
).images[0]

leads to a black image

I reproduce the issue. Somewhere in the third encoder block nan outputs are generated. I suspect this comes from one the quantized weights after dequantization (and not from a torch.float16 operation). I am checking them one by one to find out which.

It works well with int8 though ...

Somewhere in the third transformer block nan outputs are generated. I suspect this comes from one the quantized weights after dequantization (and not from a torch.float16 operation)
So I was wrong: this was indeed an overflow in a torch.float16 matmul, but only because I applied the float8 quantization scale after the matmul. By applying the scale to the float8 weights before the matmul they are back in the numerical range they had before quantization and the overflow disappears.

Here are the images generated with a float16 transformer and a float8 transformer (very subtle differences in the towers).

I am pushing the fix with a working example. I also quantized the text_encoder to make a real difference in size.

我处于main双币种状态。
from diffusers import DiffusionPipeline
import torch
from optimum.quanto import quantize, freeze, qfloat8_e4m3fn

pipeline_id = "PixArt-alpha/PixArt-Sigma-XL-2-1024-MS": "pixart"
pipeline = DiffusionPipeline.from_pretrained(
    pipeline_id,
    torch_dtype=torch.float16
).to("cuda")

quantize(pipeline.transformer, weights=qfloat8_e4m3fn)
freeze(pipeline.transformer)

image = pipe(
    prompt="ghibli style, a fantasy landscape with castles",
    num_images_per_prompt=1,
    generator=torch.manual_seed(0),
).images[0]

导致图像变黑

Hello, I wonder if the time spent has gone down?

I am pushing the fix with a working example. I also quantized the text_encoder to make a real difference in size.

I also got a black images with fp8, and used more time. Do you know how to speed it up
On 4090

qtype
time

fp16
6.06s

fp8
7.22s

int8
16.16s


Naming of files and classes in xaitk-saliency

I went through the xaitk-saliency package at a high-level and noticed some inconsistencies in our current naming scheme. I don't think any of these are huge issues, but it might help a new user or contributor to have a consistent naming pattern. Here are some examples:
xaitk-saliency/xaitk-saliency/interfaces:

Should the filename represent a shortened version of the class name?
e.g. gen_classifier_conf_sal.py (GenerateClassifierConfidenceSaliency) vs. gen_detection_sal.py (GenerateDetectorProposalSaliency) and gen_similarity_sal.py (GenerateDescriptorSimilaritySaliency)
Should these be something like gen_detector_prop_sal.py and gen_descriptor_sim_sal.py, respectively?

xaitk-saliency/xaitk-saliency/impls:

Note: implementation folder names might need to be changed if we decide to make edits to the interface names above.
Should we use underscores for filenames and Camel case for class names? Again, how closely should the filename match the class name?
gen_classifier_conf_sal: occlusion.py vs. rise_scoring.py, should this be occlusion_scoring.py?
gen_similarity_sal: currently similarityscoring.py, should this be similarity_scoring.py?

Good question, I didn't think about module naming. Consistency is important.

Should the filename represent a shortened version of the class name?

In general module, names are supposed to represent what they contain, and in the interface cases all that is usually contained is the interface class it self, so I was thinking/assuming that module names are shorted versions of the interface class names. Specifically how to generate that name I don't think I have any specific rule in mind.

Should these be something like gen_detector_prop_sal.py and gen_descriptor_sim_sal.py, respectively?

I think these are good suggestions that seem to follow a similar level of detail to the classifier variant.
I can put up a PR soon-ish with this application.
I thing to be wary of is to avoid too much bikeshedding, which can easily crop up with naming things.

Note: implementation folder names might need to be changed if we decide to make edits to the interface names above.

Yep.
I thing that is also assumed and not mentioned is the observed pattern in how the implementation submodule matches the interface class module.
I previously thought this would be an obvious observation, but if that's not the case then we can document this.
Of course, this doesn't have to be the case for functionality: all that is truly important is the plugin exposure in the pyproject.toml's [tool.poetry.plugins."smqtk_plugins"] section.
This assumed "rule" was more for intuitive organization.

Should we use underscores for filenames and Camel case for class names?

This was assumed as it is part of Python's PEP8 style-guide base.

Again, how closely should the filename match the class name?

For me it's the same as above: whatever gets across what's contained in the module.
You again have some salient points about consistency, though, that is more important to me than specifically the names.


Basement Optimization

We are currently operating our computer systems and networks in the basement, which requires immediate attention for maintenance and optimization. The current environment poses challenges that could impact the performance and longevity of our equipment.
Key Tasks:

Dusting and Cleaning:

Conduct a thorough cleaning of the basement area to remove dust and debris.
Establish a regular cleaning schedule to maintain cleanliness.

System Monitoring:

Ensure all computer systems and network equipment are operational.
Implement monitoring solutions to quickly identify and address any downtime.

Dust-Proofing:

Research and propose solutions for creating a dust-proof area around the computer systems.
Consider options such as air filtration systems, sealed enclosures, or relocating equipment to a less dusty environment.

Goals:

Improve the overall environment for our computer systems to enhance their performance and reliability.
Establish a sustainable maintenance routine to prevent future issues.
Create a long-term plan for a dust-proof area to safeguard our technology.

By the end of my 4-hour shift, I will thoroughly vacuum the computers and network area, ensuring that all dust is removed from all the KVMS and laptops. I will also check each setup to confirm they are running smoothly, and well-ventilated, and the dehumidifier is switched on aiming for at least 90% operational efficiency by the end of my shift.

I cleaned up the basement, specifically the computer lab area, and ensured each computer and all KVMs were running.


[Coinbase Pro] Size is too accurate (buy and sell: quote_increment vs base_increment)

Describe the bug
For Coinbase Pro, currently in code we are checking the base_increment in marketBuy method where it should check the quote_increment and min_market_funds according to the API documentation: https://docs.pro.coinbase.com/#get-products.
https://github.com/whittlem/pycryptobot/blob/ee8a58309999e8939c17c97640be56fb242fbbb6/models/exchange/coinbase_pro/api.py#L285
And no check is done in the marketSell method whereas Coinbase Pro check the base_increment and base_min_size.
https://github.com/whittlem/pycryptobot/blob/ee8a58309999e8939c17c97640be56fb242fbbb6/models/exchange/coinbase_pro/api.py#L308
We should create a marketQuoteIncrement method and use it in marketBuy and use the marketBaseIncrement method in marketSell.
Also it would be good to check the min quantity:

min_market_funds in marketBuy (maybe no need to check max_market_funds as I guess that not man people will trade 1M$)
base_min_size in marketSell (maybe no need to check base_max_size as it would be more than 8M$ for BTC nowdays)

The following screenshot was sent by @Revonox on Telegram Dev Channel.

Duplicate of #201
I already have done a pull request with a commit to fix this issue: https://github.com/whittlem/pycryptobot/pull/206/commits/8a52e6622bdf02a83951795c48e70c7707adcb23

It's not solving the problem since the commit you mentionned only use base_increment for both buy and sell where base_increment should only be used for sell and quote_increment for buy.

You'are right, I'll fix that.

https://github.com/whittlem/pycryptobot/pull/206/commits/8631c93ca68d9f89e46a342daadc66895b7b2176


New package: LinusDierheimer.fastfetch version 1.9.1

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

Manifest 1.4

Note: fastfetch is missing out some information, such as terminal font, due to https://github.com/microsoft/winget-cli/issues/2889

@wingetbot run

@sitom I think this can be converted to a "real PR".

There are issues such as https://github.com/microsoft/winget-pkgs/pull/94697#issuecomment-1407229646, though. I wouldn't like to merge a half-working program.

/AzurePipelines run

Hello, I have received some requests to make fastfetch available in winget. I hope this PR can be made further. A few comments:

This issue is no longer an issue because we embedded the the necessary library in fastfetch. Terminal font should work out of box.
The fastfetch version should be updated. The latest version is v2.13.1.
The PackageIdentifier and URLs should be updated. Fastfetch has been moved to Group fastfetch-cli and the Windows port of fastfetch was fully written by me @CarterLi.

Hello, I have received some requests to make fastfetch available in winget. I hope this PR can be made further. A few comments:

This issue is no longer an issue because we embedded the the necessary library in fastfetch. Terminal font should work out of box.
The fastfetch version should be updated. The latest version is v2.13.1.
The PackageIdentifier and URLs should be updated. Fastfetch has been moved to Group fastfetch-cli and the Windows port of fastfetch was fully written by me @CarterLi.

Have released in wInget-pkgs with updated info, see https://github.com/microsoft/winget-pkgs/pull/94697 @CarterLi

Have released in wInget-pkgs with updated info, see #154718 @CarterLi

Hi, thanks for the update. I'm currently off-town at the moment, but once I get back, I can set up Winget Releaser in the fastfetch repo for automated updates (or maybe you can set it up yourself @CarterLi; it's quite easy 🙂).


Pattern for serial_number for intel real sense D415

Hi,
I am using serial_number of camera as a unique camera id. I wanted to check if camera id passed is invalid id or not. Do Intel real sense have any regular expression for serial_number so that we can quickly check if the id format is correct or its an invalid id.

I suppose there is no publicly available information on this.