fix: 通用指定项目到云上创建资源

这个 PR 实现什么功能/修复什么问题:
通用指定项目到云上创建资源
是否需要 backport 到之前的 release 分支:
None
/area region
/cc @swordqiu @zexi

Codecov Report

Merging #6592 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #6592      +/-   ##
==========================================
- Coverage    7.17%    7.16%   -0.01%
==========================================
  Files         647      647
  Lines      109213   109270      +57
==========================================
  Hits         7831     7831
- Misses     100782   100839      +57
  Partials      600      600

Flag
Coverage Δ

#aFlag
7.16% <0.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudprovider/cloudprovider.go
1.49% <0.00%> (-0.05%)
:arrow_down:

pkg/cloudprovider/instance.go
0.00% <ø> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/models/cloudproviders.go
0.86% <0.00%> (-0.02%)
:arrow_down:

pkg/compute/models/dbinstances.go
0.82% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/disks.go
0.53% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/elasticips.go
1.15% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/hostdrivers.go
18.18% <ø> (ø)

pkg/compute/models/loadbalancers.go
1.36% <0.00%> (-0.02%)
:arrow_down:

pkg/compute/models/storages.go
0.93% <0.00%> (-0.01%)
:arrow_down:

... and 2 more

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 b859eea...9916c99. Read the comment docs.

/lgtm


cosmic-tasks: 0-unstable-2024-04-30 -> 0.1.0 + rename to tasks

Description of changes
The package was renamed tasks upstream, so I did the same here.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.


whether the confidence setting is too low, and re-run issue

Hi @gunthercox
Thank you for great work. ChatterBot is in very good quality and easy to use. After used for a while, I found three issues which would like to discuss with you.

After added "TheIDontKnowAdapter", about codes below:if confidence < 10:
        return 1, default_response
return 0, closest_match

whether the value of confidence is setting too low? normally,  it is easy to pass default_repsonse and return as closest_match

within "base_match.py", the codes are
    if response_list:          response = self.break_tie(response_list, self.tie_breaking_method)      else:          response = self.context.storage.get_random()
so if response_list is empty, you pick up answer randomly. I changed to
     else:          response = self.context.storage.update(closest_match)
what do you think? is there any better way when response_list is empty?

After re-run for several times, I found the output part can have wrong answer even the answer come from previous question part when there is no related input from corpus data . For every first run, the answer was correct, then after "database.db" was built,  program will search even all the records within database, so provided the previous question part to output answer when the  fuzz confidence is higher.

Hi @PengTedShen, for your question:

It is possible that 10 is not the most optimal value for that code example. Feel free to adjust it as needed.
The method call to self.context.storage.update(closest_match) will return the updated statement that is passed in to the method. Although, it's meta data may change, the statement text will be the same. I would advocate keeping the random response fallback for now rather than just returning the input as a closest match, but I'm open to other suggestion.
Note that the chat bot also continues to learn as you talk to it, so it may be learning additional response options from your input. If this functionality is not desired then it is possible to but the database into read-only mode by specifying read_only=True when initializing the chat bot.

Thank you for your reply. About point 2, I will discuss with you if I could have some suggestions after study codes further.


feat(amplify-category-auth): enable alternative signup/signin options

Description of changes

The AWS Cognito console provides these options to users when creating a user pool. Alternative sign in options allow developers to create a coginito user that can sign in using their preferred username, phone number, or email address, or any combination of the three.

Without this change, the only options available are username, email, phone number, or email and phone number. For example, username and email is not allowed.

With this change, developers are able to multi-select any combination of these options:

Issue #, if available

#1546
Description of how you validated changes

updated unit tests
created app, walked through amplify-dev add auth steps. generated cognate resources in AWS had the desired fields.

Here is a demo app created with this change that allows sign-in via both email and username (previously not available): http://testing12345-20210716122645-hostingbucket-dev.s3-website-us-east-1.amazonaws.com/
Here is a demo app created without the change. Email and username could not both be selected:

email only selected: http://testing1234567-20210716125640-hostingbucket-dev.s3-website-us-east-1.amazonaws.com
username only selected: http://testing1234568-20210716130713-hostingbucket-dev.s3-website-us-east-1.amazonaws.com

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #7461 (31438e8) into master (08704f0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #7461   +/-   ##
=======================================
  Coverage   52.75%   52.76%
=======================================
  Files         514      514
  Lines       25921    25924    +3
  Branches     5058     5059    +1
=======================================
+ Hits        13675    13678    +3
  Misses      11278    11278
  Partials      968      968

Impacted Files
Coverage Δ

...utils/awscloudformation/assets/cognito-defaults.js
69.56% <ø> (ø)

...gory-auth/src/provider-utils/supported-services.ts
100.00% <ø> (ø)

...ider-utils/awscloudformation/assets/string-maps.js
86.20% <100.00%> (+0.49%)
:arrow_up:

...s/awscloudformation/utils/auth-request-adaptors.ts
44.11% <100.00%> (+1.11%)
:arrow_up:

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 08704f0...31438e8. Read the comment docs.

Hello @johnpc and @sachscode!
One of the issue that I come across since the change where AliasAttributes is used instead of UsernameAttributes when
following this Amplify documentation: https://docs.amplify.aws/guides/authentication/email-only-authentication/q/platform/js
The following error would be raised: "Username cannot be of email format, since user pool is configured for email alias"
Where a hash (uuid?) would be generated for the username with UsernameAttributes it is not the case when using AliasAttributes
I'm wondering if the cloud formation generated should have something like, if only one sign-in type selected, use UserNameAttributes otherwise use AliasAttributes which would have that kind of implementation:
packages/amplify-category-auth/resources/cloudformation-templates/auth-template.yml.ejs
<% if (props.aliasAttributes.length === 1 && props.aliasAttributes !== 'username') { %>
  UsernameAttributes: !Ref usernameAttributes
<% } else if (props.aliasAttributes && props.aliasAttributes.length > 1) { %>
  AliasAttributes: !Ref aliasAttributes
<% } %>

Note that in the current implementation the following could be deleted as props.usernameAttributes would always be set as undefined
<% if (props.usernameAttributes && props.usernameAttributes !== 'username') { %>
  UsernameAttributes: !Ref usernameAttributes
<% } %>

Another solution could be to hash the email is hashed when using AliasAttributes but as I'm unfamiliar with Amplify and AWS Cognito, I'm not sure where this should happen
Have a great one 👋

@fabientownsend, I'm running into the same bug you are. Do you think the maintainers might look at your comment if you opened it as a bug report in the issues area?

Would be good to have the ability to edit this in the existing project.


charan-web

Due we close new issues on PR merge and voting is still possible on closed issues I will close this one.


add examples and tests

Adds some basic examples, and uses the examples for testing CLI.

Nice, should we add this testing to CircleCI?

@SuperQ yes, I think running the tests in CircleCI would be good, I added a commit for the CircleCI config.

Fixed signoff and squashed commits


2022 Day 14 Part 2 implementation is too slow to test

The actual changes were in 4b27a76100ee6275f5057448df745c28cf47981c

It's still not very fast, but it's good enough to not worry about, I think. Anything else will over-complicate the solution, IMO.


WIP: Allow walltime as None to be given during initialization

Distinguish between None (set by user) and the default value
so walltime=None can be set during initilization
Fixes #500

Wouldn't it be easier to understand if the default was set to the actual default value and None meant no wall time? Another advantage to that approach is that it makes documentation of what's going on more straightforward and automatic. I'm also not sure that we'd want to change defaults for just one implementation.

I'm also not sure that we'd want to change defaults for just one implementation.

This is just a draft. I am trying to see how the maintainers would like this to be implemented.

I think we've got to make it clear if kwargs are None, then they are loaded from the config, and if different of None then, they are used in the job_script.

I agree with @guillaumeeb! I think is reasonable to keep the existing defaults and point users to the ~/.config/dask/jobqueue.yaml as a recommended way to set their preferred, permanent defaults.

Anyway, I'm fine with setting more parameters in the default config files to None. With a quick glance, I see that almost only the walltime is set by default. We can set it to null and add some advice in the documentation.

I also think this is the best approach. With a bit of documentation and not setting walltime by default, you let users decide what's best for them.

I'm going to close this one.
I think there is already enough information about how config file works here: https://jobqueue.dask.org/en/latest/configuration.html.
We just need to clarify the default values.


Additional Views

This PR introduces additional views to quickly check table bloat, table vacuum times and Postgres internal cache usage when. Furthermore it adds client statistics.

Thanks for this as well, but see #7


Support for sass-rails 5.0 dependency?

Rails : 4.2.1
Ruby : 2.2
Mongoid : 4.0.2
getting this error when trying to bundle
Bundler could not find compatible versions for gem "sass-rails":
In snapshot (Gemfile.lock):
sass-rails (5.0.1)
In Gemfile:
activeadmin-mongoid (>= 0) ruby depends on
sass-rails (< 5.0, >= 3.1.4) ruby

which ref are you using for activeadmin-mongoid?


69+17 Warnings in Unity 2019.1.3f1 and 159 Warnings in Unity 2019.1.2f1

Hello,
I wanted to inform you that the newest version of Unity (2019.1.2.f1) throws 159 warnings corresponding to LeapMotion.
On my system: https://pastebin.com/265chmXg
Hope this helps.
Update
In the even newer version 2019.1.3f1 the warning count has reduced to 69 warnings: https://pastebin.com/7zhrTQz6
And 16 additional ones complaining about several lighting data assets and 1 about a mesh:
ImportFBX Warnings:
Can't generate normals for blendshape 'Key 1' on mesh 'Cube', mesh has no smoothing groups.
Lighting data asset ‘LightingData’ is inconsistent because 2 files out of 10 are missing.  Please use Generate Lighting to rebuild the lighting data.
[...]

It's true, at present, 2019 has lots of import warnings. Incremental UnityModules changes to address this are slowed down right now as we will possibly be making larger changes to the Unity SDK.
If the warnings become frustrating enough that you wind up fixing them yourself, I'd be happy to review a PR, unfortunately some of the warnings get into the weeds on the specifics of, e.g., Unity's changes to prefabs and are a little sticky for that reason.

The LeapMotion scripts will actually also cause a substantial freeze in the editor (likely due to the countless warnings). I my case after each script compilation the editor freezed for 20 seconds. Is there any work done on the LeapMotion Unity integration? Or is this dead?

Release 4.5.0 moves the LeapMotion to the Plugins folder to reduce compilation times, and also implements a bunch of changes to get rid of warnings in Unity 2019. If any new obnoxious warnings pop up for Unity 2019, please open up a new ticket and we can take a look. :)


No endpoint set on first load

Ah, this is only a problem in private mode, safari. Localstorage throws an exception because 'it is full' (a private mode restiction)

Cause: the lib we use does not guarantee behaviour in private mode. Added checks to all storage functions (in yasgui-utils), to avoid getting Js errors.


why can't I enter the error code and get the info on that.

As the title explains, I want a facility to enter the error code and get the info and any fixes or workaround related to that error code number.  The error code I have is not listed in this article despite it beginning with 0x800???   Where do I go from here???   Poor show from such an almighty company.   Maybe including a read me file on the installation USB with some general information on what to do before installation to avoid all of these common pitfalls??
So what do I do to rectify a 0x8007001F - 0x20006  The installation failed in the SAFE_OS phase with an error during REPLICATE-OC operation   ?????????
This is meaningless technobabble that one of your engineers might understand, but even for someone computer savvy like me it is still meaningless.   So why wasn't the remedy included on the infographic when the error flagged up on my screen???

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

ID: 528014e0-02e5-2d77-a229-4895731bb872
Version Independent ID: 4f46b620-e345-c9e4-70fa-ae4f5a8e48b9
Content: Resolution procedures - Windows IT Pro
Content Source: windows/deployment/upgrade/resolution-procedures.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@Romney57 - Thank you for submitting feedback.
I think the best way forward is if you can contact support and open a service ticket for Windows 10 products  so this can get resolved ASAP. Based on outcome, let me know if it is something that can be called out in the docs.
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


A customer support agent should be able to set an away message when they are away

Is your feature request related to a problem? Please describe.
When a user sends a message to agents that are away or out of hours than they should receive a custom message setting expectations that they might not receive an immediate message
Describe the solution you'd like
A user should receive a custom message if there are no customer support agent has been active for more than 10 minutes. On the getting started page the customer support agent should be able to set the custom message for default away messages.

For a bit more context: the problem we're trying to solve is when a customer is sending messages through the chat, but no one is around to respond.
This could be solved in a few ways:

Make it more obvious when people are around to chat
Automatically send an away message if a customer sends a message and no one is around (e.g. outside of working hours)
Automatically send an away message if nobody replies within X minutes


feat: support proxy for outgoing traffic

I have the requirement that our selfhosted gitlab-runners need to use a proxy for outgoing traffic. This solved the problem.
Is that something that you would consider in a PR? Or do you maybe even have a better solutions?

Hi @juldanherglo
We are standardizing on actions/http-client because that's what GitHub recommends for proxy settings on self-hosted runners (https://docs.github.com/en/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners). I added support in https://github.com/google-github-actions/auth/pull/218.

Hi @juldanherglo
We are standardizing on actions/http-client because that's what GitHub recommends for proxy settings on self-hosted runners (https://docs.github.com/en/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners). I added support in #218.

Thank you, @sethvargo . I tested #218 and it works as well. There was one warning though:
(node:18684) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.


Allow the user to display available upgrades and installed packages in a window with a textbox instead of CMD so stuff doesn't disappear.

Would have to make sure to update the sources beforehand so it doesn't look horrible. Maybe if PowerShell doesn't trim off the output past a certain point, the commands could be switched to use it instead. Would prefer to stick with CMD since it's a lot faster to start, though. Hopefully that ConsoleControl would work and display all the packages that are installed.

Nah, we can just switch over to PowerShell for now since it doesn't seem to remove items like CMD does.

As stated in https://github.com/DrewNaylor/guinget/issues/78#issuecomment-737906327, neither CMD nor PowerShell have infinite scrollback buffers, so I'm going to just read the output into a textbox, or if I can manage it, a ListBox or even DataGridView.

This textbox should be in a form with a Close button in the bottom-right corner next to a Save to text file button. The textbox may need both horizontal and vertical scrolling and the window will definitely need to be resizable. Probably would be a good idea to reuse this form for stuff like the upgrades by doing what I do with the download progress form. Could look nice to have an indeterminate progress bar below a "Loading packages, please wait..." label that shows up while loading the lists of installed packages and upgrades. Probably should run winget source update beforehand so the progress bar doesn't mess with the textbox. It's possible that updating the sources will have issues, so redirecting standard error will be important.

Just to make things simple, there should be a way to display just a textbox and a way to show a tabcontrol that has both a textbox and a consolecontrol (as mentioned in the first post). The one with the consolecontrol can be used to show the output from winget source update instead of just putting it in a textbox.

Actually, maybe the ConEmu control could be used instead of ConsoleControl:
https://www.nuget.org/packages/ConEmu.Control.WinForms/

Doing the fancy two-tab thing was too much work that I don't really know how to do right now, so maybe I can just have a reusable window with ConEmu embedded that runs specific commands based on which one is clicked in the menubar. The Save to file button can just run the command a second time and pipe the output to a file of the user's choosing.

If I use a textbox or another similar control without support for ANSI sequences, I'll have to replace the spinner thing.

Did a quick test with listing in a textbox, and it just looks bad. Probably would have to use monospace fonts to make it look ok sometimes, but there's a lot that just ends suddenly. None of this is mentioning the progress bar text when the command is run that would have to be removed with a replace thing. Might have to do something like watch the output and put it into a nice list right after the progress bar is full, but that doesn't help with the part where the column just ends.

Did a quick test with listing in a textbox, and it just looks bad. Probably would have to use monospace fonts to make it look ok sometimes, but there's a lot that just ends suddenly. None of this is mentioning the progress bar text when the command is run that would have to be removed with a replace thing. Might have to do something like watch the output and put it into a nice list right after the progress bar is full, but that doesn't help with the part where the column just ends.


handle the stem issue

img2dataset doesn't produce unique stem , remove from dataset loader or change in img2dataset

see stem

A simple solution seems to be to use as key shard id * shard size + current id
Let's make this change at least for non webdataset, but maybe for webdataset too


Allow projection actor to retrieve latest Cfd state itself from DB

Instead of retrieving Cfds inside Cfd actors, send a msg that they changed and
retrieve them by the projection actor itself.

bors r+

Nice, thank you!
I think the two functions cfd_actors are pretty useless now so wouldn't mind inlining them :)

they're pretty small, but IMHO not useless! we had a problem previously that we forgot to update the feed in some cases... when we will move to looking at events in projection actor, then it will be useless - I agree :)

Build failed:
* [test_daemons (macos-latest)](https://github.com/itchysats/itchysats/runs/4405024373?check_suite_focus=true)

Well that is concerning:

process didn't exit successfully: /Users/runner/work/itchysats/itchysats/target/debug/deps/happy_path-795f3ae0e3f41528 (signal: 11, SIGSEGV: invalid memory reference)

How can our tests SEGFAULT??

bors retry

I have never seen a segfault on my macos, I suspect it might be some linked to the gh actions container.... is there any way to obtain a code dump from gh actions? 😅

I have never seen a segfault on my macos, I suspect it might be some linked to the gh actions container.... is there any way to obtain a code dump from gh actions? sweat_smile

I don't think so but it might be the same issue we saw on the Windows tests at times!


GENv1 HL7 Validations: Blanket Processing QA-Reqid-00005: Updates needed for DEX

Reference document: NND Requirements - Blanket Processing
Rule: Reqid-00005
QA TEST RESULTS HERE on tab QA-Reqid-00005 - Coded Value
Postman Collection -

@nadiackhan - Link to spreadsheet is missing


Update ubuntu.sh

The downloaded file is no longer gziped file.

I don't think this is correct.
% curl -o vmlinuz "https://cloud-images.ubuntu.com/releases/focal/release/unpacked/ubuntu-20.04-server-cloudimg-arm64-vmlinuz-generic"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10.1M  100 10.1M    0     0  7484k      0  0:00:01  0:00:01 --:--:-- 7484k
% file vmlinuz
vmlinuz: gzip compressed data, was "vmlinuz-5.4.0-65-generic.efi.signed", last modified: Wed Jan 20 15:20:49 2021, max compression, from Unix, original size modulo 2^32 30382464


Created testimonial v2

Created testimonial v2 component using HTML and Tailwind CSS

You do not need to add any HTML boiler template and tailwind config. You only need to add the main part see other samples in the repo. @MadhurKharche

Good job @MadhurKharche
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

https://www.clueless.tech/profile/admin/78757405 @Rajdip019


Registration status for bidders

We will now need to support two new instances in the bid registration status of users.
Partners can now:

Close registration at a certain point, likely 24-48hrs before a live sale begins
Choose to pre-approve every single bidder that wants to register.

Both these instances can happen at once.
Below is a spec for what we should show in each instance

If the bidder is approved, then that state "wins" regardless if registration closes prior to the sale going live or not.

[ ] Native auction sale page
[ ] Sale information modal
[ ] Live Bidding UI bid button
[ ] Native artwork bid button

As a part of this, we should add another command that re recognize whose job it is to force a refresh. Thinking that maybe "ConnectionRefresh" could be the trigger?
/cc @acjay

Works for me, or perhaps HardRefresh, just to emphasize that the intention is to reload the whole experience.

👍

@craigspaeth / @acjay any idea how I can determine this data? Would it come inside the JWT?

Data should be in gravity already

@orta I'm afraid we do need to change the status of the bid button on the artwork pages as follows
Logged out Experience:

Logged In:

If the user is approved, the we give them the standard bid button

If this is the type of auction where registration actually closes at some point then we show the following

@orta In case your question was still open, "yet to register" would be the absence of a Bidder model from Gravity, and also the observer role being assigned, "sent registration in a pre-approval auction" would be the presences of a Bidder model, with qualified_for_bidding: false , which would be true if approved.

#1654 gets half of this done, waiting on https://github.com/artsy/prediction/pull/263 to be deploy'd to work on the live section

Going to take on the next half.

@ashfurrow you wanna do this TODO too - https://github.com/artsy/eigen/pull/1661/files#diff-6d73ebd58fdd2d00c32813f60608fbd1R111

done for now. Individual updates will be tackled with new issues/epics


Series sort order not followed consistently.

when viewing a series, with the default sort by series number, the order is not followed. This is one example but happens frequently.

(Thanks for the application).

I'll try to have a look, thanks for the report

should be fixed in 0.56.3

should be fixed in 0.56.3

Pulled new image and confirmed sort order is now as expected.


[AutoPR web/resource-manager] Update managedserviceidentity type enum

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5536

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/1960


[Blog] Open source ecosystem health goals/metrics

https://docs.google.com/document/d/1X9MoOrZXXAQqBx2fTAxE23an2DTExgDxC20BH3J_EH4/edit?usp=sharing


need a maj for 10.0.0 version c:

Yeah no problem I actually knew you would do that I was just asking :)

Fixed by #40, see latest release


SET CLUSTER SETTING inside a transaction

PR: https://github.com/cockroachdb/cockroach/pull/29082
From release notes:

The SET CLUSTER SETTING statement can no longer be used inside a transaction. It also now attempts to wait until the change has been gossiped before allowing subsequent statements. [#29082][#29082] {% comment %}doc{% endcomment %}

No docs update needed


Please add a version option

Please add a version flag to the list of cli options for getting easier information about the current release version:
catt --version

Done, thanks!

@skorokithakis

Winter Waterfall

:rofl: :rofl: :rofl:

https://www.youtube.com/watch?v=L0MK7qz13bU

I get to choose the next version codename, and trust me, it's going to be silly. Like, Ubuntu silly.
PS: I was unable to extract any subliminal messages from the video you linked to, but then again, I'm pretty dumb.

Who said we're changing it every version, or, indeed, ever?!

The video was just winter-waterfall-themed :P

Who said we're changing it every version, or, indeed, ever?!

Party pooper :cry:

Actually, we can start picking release names if you want to, it just felt like too much work :stuck_out_tongue: Let's alternate, I'll take odd (starting with this 0.9.3, Winter Waterfall), you take even.
The rules are:

They have to alliterate.
They can't be serious.
Starting with the next letter from the previous release would be nice.


Chunking seems to not be working properly

Hello and thank you for creating this tool!
I have been trying to use the noun_chunks with your pipelines but it does not seem to be working correctly. I have tried with en_core_sci_sm, en_core_sci_md and en_core_sci_lg. For example when I input the sentence "CCR5(+) and CXCR3(+) T cells are increased in multiple sclerosis and their ligands MIP-1alpha and IP-10 are expressed in demyelinating brain lesions." I only get "CCR5(+", "CXCR3(+" and "T cells" as chunks and I would expect more chunks. For example, using spaCys en_core_web_trf I get "CCR5(+) and CXCR3(+) T cells", "multiple sclerosis", "their ligands", "MIP-1alpha", "IP-10" and "brain lesions".
Is the chunking supposed to work in a similar way as spaCys pipelines or have I misinterpreted something?
Thank you in advance!
Best regards

so, I think this is due to differences in the dependency parse. our dependency parser is more accurate on biomedical data (but different from spacy's), and spacy's noun chunker is defined here (https://github.com/explosion/spaCy/blob/a59f3fcf5dab3acf5570483cc314b47cc5833f39/spacy/lang/en/syntax_iterators.py#L8), with respect to specific dependency relations. See an example of the difference for your sentence below. Perhaps we should write our own noun chunker based on our dependency parser, but I am really not an expert in linguistics. You might get some mileage from adapting spacy's noun chunker based on patterns you observe from our dependency parser. Also, @DeNeutoy do you have any thoughts about this?
In [14]: [(t.text, t.pos_, t.dep_) for t in sci_doc]
Out[14]:
[('CCR5(+', 'NOUN', 'nsubjpass'),
 (')', 'PUNCT', 'punct'),
 ('and', 'CCONJ', 'cc'),
 ('CXCR3(+', 'NOUN', 'compound'),
 (')', 'PUNCT', 'punct'),
 ('T', 'NOUN', 'compound'),
 ('cells', 'NOUN', 'conj'),
 ('are', 'VERB', 'auxpass'),
 ('increased', 'VERB', 'ROOT'),
 ('in', 'ADP', 'case'),
 ('multiple', 'ADJ', 'amod'),
 ('sclerosis', 'NOUN', 'nmod'),
 ('and', 'CCONJ', 'cc'),
 ('their', 'PRON', 'nmod:poss'),
 ('ligands', 'NOUN', 'conj'),
 ('MIP-1alpha', 'NOUN', 'dep'),
 ('and', 'CCONJ', 'cc'),
 ('IP-10', 'NOUN', 'conj'),
 ('are', 'VERB', 'auxpass'),
 ('expressed', 'VERB', 'conj'),
 ('in', 'ADP', 'case'),
 ('demyelinating', 'VERB', 'amod'),
 ('brain', 'NOUN', 'compound'),
 ('lesions', 'NOUN', 'nmod'),
 ('.', 'PUNCT', 'punct')]

In [15]: [(t.text, t.pos_, t.dep_) for t in web_doc]
Out[15]:
[('CCR5(+', 'NOUN', 'ROOT'),
 (')', 'PUNCT', 'punct'),
 ('and', 'CCONJ', 'cc'),
 ('CXCR3(+', 'PROPN', 'npadvmod'),
 (')', 'PUNCT', 'punct'),
 ('T', 'NOUN', 'compound'),
 ('cells', 'NOUN', 'nsubjpass'),
 ('are', 'AUX', 'auxpass'),
 ('increased', 'VERB', 'conj'),
 ('in', 'ADP', 'prep'),
 ('multiple', 'ADJ', 'amod'),
 ('sclerosis', 'NOUN', 'pobj'),
 ('and', 'CCONJ', 'cc'),
 ('their', 'PRON', 'poss'),
 ('ligands', 'NOUN', 'conj'),
 ('MIP-1alpha', 'PROPN', 'appos'),
 ('and', 'CCONJ', 'cc'),
 ('IP-10', 'NUM', 'conj'),
 ('are', 'AUX', 'auxpass'),
 ('expressed', 'VERB', 'conj'),
 ('in', 'ADP', 'prep'),
 ('demyelinating', 'VERB', 'amod'),
 ('brain', 'NOUN', 'compound'),
 ('lesions', 'NOUN', 'pobj'),
 ('.', 'PUNCT', 'punct')]

Did you have any luck adapting the noun chunker?

Sorry for my late response. Your answer was very helpful! I decided to try a different approach since I did not have enough time in my project to look for these patterns. Thank you very much!

has anyone worked on a scispacy noun chunker? thanks !


Fix volume screen images.

WHAT
CI tests are failing because of a different result for volume tests.  Try recreating the images.
WHY
Went from 1000px to 999 for some reason?
HOW
Checklist :clipboard:

[x] Add explicit visibility modifier and explicit return types for public declarations
[x] Run spotless check
[x] Run tests
[x] Update metalava's signature text files

@luizgrp Going to raise a paparazzi bug, this is weird

Actually it could be my code WearSnapHandler, so need to check that first.

loads of weirds things going on with these paparazzi tests, main branch is green after merging this but my PRs that are up to date with main are failing with:
com.google.android.horologist.audio.ui.VolumeScreenIndividualTest > volumeScreenAtMaximum FAILED
    java.lang.NullPointerException at VolumeScreenIndividualTest.kt:66
com.google.android.horologist.audio.ui.VolumeScreenIndividualTest > volumeScreenAtMinimum FAILED
    java.lang.NullPointerException at VolumeScreenIndividualTest.kt:49
com.google.android.horologist.audio.ui.VolumeScreenIndividualTest > volumeScreenWithLongTest FAILED
    java.lang.NullPointerException at VolumeScreenIndividualTest.kt:83


⚠ Fetchers has degraded performance

In cb1bee4, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 839 ms

Resolved: Fetchers performance has improved in 9977327.


Be able to restart/reinstall application during UI test execution

Use case
I'd like to restart application between each UI test run.
Actually and as workaround we have something that via dataHandler we're doing on each test setUp() that's restarting the activity but it's not ideal as we're not properly cleaning memory. As a QA I think that's mandatory that each test has to be executed in isolation and without depending on previous run outcome.
Proposal
Have an additional argument on flutter drive that will let application restart like a fresh install for each test.
Proposal:
flutter drive --reinstall-between-tests or something similar

Future<void> main() {
  final config = FlutterTestConfiguration()
    ..hooks = [AttachScreenshotOnFailedStepHook()]
    ..features = [Glob(r"test_driver/features/**.feature")]
    ..reporters = [JsonReporter(path: './cucumber.json'),
      ProgressReporter(),
      TestRunSummaryReporter(),
    ]
    ..stepDefinitions = [
    ]
    ..restartAppBetweenScenarios = false
    ..targetAppPath = "test_driver/app.dart"
    ..exitAfterTestRun = false;
  return GherkinRunner().execute(config);
}

Replace  ..restartAppBetweenScenarios = false with  ..restartAppBetweenScenarios  = true

Future<void> main() {
  final config = FlutterTestConfiguration()
    ..hooks = [AttachScreenshotOnFailedStepHook()]
    ..features = [Glob(r"test_driver/features/**.feature")]
    ..reporters = [JsonReporter(path: './cucumber.json'),
      ProgressReporter(),
      TestRunSummaryReporter(),
    ]
    ..stepDefinitions = [
    ]
    ..restartAppBetweenScenarios = false
    ..targetAppPath = "test_driver/app.dart"
    ..exitAfterTestRun = false;
  return GherkinRunner().execute(config);
}

Replace ..restartAppBetweenScenarios = false with ..restartAppBetweenScenarios = true

Hey, @endritgojani thanks for your solution! Sadly, I don't want to use cucumber to execute the tests, so that's not a solution to me.

Take a look here, don't know yet if it is what I also need...
https://beltran.work/blog/restart-flutter-app-with-driver/

@vvargas90 hi, you mentioned there is a workaround that via dataHandler on each test setUp() that can restart the activity, can you share with us the code on how to do it? i want to try it  to see if it could work on my side, thanks a lot!

Or, the driver could provide a function like driver.restartApp(). that is what we need now.

You can use the example mentioned by @virgule-xyz  :)

Basically what I did was use similar approach what @virgule-xyz said, but without an extra package. I just added key option to main function so I can reload app from fresh.
  enableFlutterDriverExtension(handler: (message) async {
    switch (message) {
      case 'restart':
        app.main(key: UniqueKey());
        return 'ok';
    }
    throw Exception('Unknown command');
  });

void main({Key key}) {
  runApp(App(key: key));
}

Restarting app with UniqueKey sometimes freeze the whole app just after restart. It can be fixed manually by pausing and resuming app with opening tasks list and entering app again. In this case tests will continue to executing. Has anyone else encountered such a problem and have you managed to solve it?

I can't get the app to perform a restart by supplying a UniqueKey(). The only thing, that makes my app restart is mounting an empty container before running the app again.
runApp(Container());
runApp(App());

But I got the same problem like alexandr2levin. Sometimes the app just freezes and I cant perform any more tests after the restart.

Definitely need a built-in method to do this

Just tried the methods mentioned and no luck. Anyone successfully implemented this method recently?

This could also be neat if you are testing data persistency.

I think I have a solution:
I'm using Integration test
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';

import '../main.dart' as app;

void main() {
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  group('end-to-end test', () {
    bool beforeRestartValue = false;

    testWidgets('before restart', (tester) async {
      app.main(); // <- see this function was called explicitly
      await tester.pumpAndSettle();

      final _widget = find.byToolTip('Increment');

      // you can set the variable here
      beforeRestartValue =
          Theme.of(tester.element(_widget)).brightness == Brightness.dark;
    });

    testWidgets('after restart test', (tester) async {
      // app.main() was called again, so the app was restarted
      // and you can tell by the emulator screen.
      app.main();

      await tester.pumpAndSettle();

      final _widget = find.byToolTip('Increment');

      // get the new value
      final restartedVariable =
          Theme.of(tester.element(_widget)).brightness == Brightness.dark;

      // and compare
      expect(beforeRestartValue, equals(restartedVariable));
    });
  });
}

My app restarts between tests if I

Edit: this does not work!
I think I have a solution: I'm using Integration test
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';

import '../main.dart' as app;

void main() {
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  group('end-to-end test', () {
    bool beforeRestartValue = false;

    testWidgets('before restart', (tester) async {
      app.main(); // <- see this function was called explicitly
      await tester.pumpAndSettle();

      final _widget = find.byToolTip('Increment');

      // you can set the variable here
      beforeRestartValue =
          Theme.of(tester.element(_widget)).brightness == Brightness.dark;
    });

    testWidgets('after restart test', (tester) async {
      // app.main() was called again, so the app was restarted
      // and you can tell by the emulator screen.
      app.main();

      await tester.pumpAndSettle();

      final _widget = find.byToolTip('Increment');

      // get the new value
      final restartedVariable =
          Theme.of(tester.element(_widget)).brightness == Brightness.dark;

      // and compare
      expect(beforeRestartValue, equals(restartedVariable));
    });
  });
}

My app can restart if I declare the router inside the MyApp class itself (the _routes member).
class MyApp extends StatelessWidget {
  MyApp({
    Key? key,
    required this.settingsController,
  }) : super(key: key);

  final SettingsController settingsController;

  final _routes = GoRouter(routes: <GoRoute>[
    GoRoute(
      routes: <GoRoute>[
        GoRoute(
          path: 'test',
          builder: (BuildContext context, GoRouterState state) => BlocProvider(
            create: (context) => LogicCubit(),
            child: const TestPage(),
          ),
        )
      ],
      path: '/',
      builder: (BuildContext context, GoRouterState state) => const Base(),
    )
  ]);

  @override
  Widget build(BuildContext context) {
    // Glue the SettingsController to the MaterialApp.
    //
    // The AnimatedBuilder Widget listens to the SettingsController for changes.
    // Whenever the user updates their settings, the MaterialApp is rebuilt.
    return AnimatedBuilder(
      animation: settingsController,
      builder: (BuildContext context, Widget? child) {
        return MaterialApp.router(
          theme: lightTheme,
          darkTheme: ThemeData.dark(),
          themeMode: settingsController.themeMode,
          routerDelegate: _routes.routerDelegate,
          routeInformationParser: _routes.routeInformationParser,
          routeInformationProvider: _routes.routeInformationProvider,
        );
      },
    );
  }
}

My app goes back to homepage if I declare the router inside the MyApp class itself (the _routes member).

Yes, the app seems to have restarted.
I didn't explain why I think it doesn't work, my bad :P.
If you have a singleton in your app, and you did something in UI that changes the properties in that singleton in the first test, that singleton will not get re-initialized after the second app.main() call.
So if your app depends on properties in that singleton for conditional rendering, that way can't really test it.

@A7GoD

My app goes back to homepage if I declare the router inside the MyApp class itself (the _routes member).

Yes, the app seems to have restarted.
I didn't explain why I think it doesn't work, my bad :P.
If you have a singleton in your app, and you did something in UI that changes the properties in that singleton in the first test, that singleton will not get re-initialized after the second app.main() call.
So if your app depends on properties in that singleton for conditional rendering, that way can't really test it.

Then.. it seems for now, multiple files is the only option. Which revompiles the app for each file.

I think this issue is badly worded, because in Flutter's universe, the app is your integration test.

And progress on this?

I think this issue is badly worded, because in Flutter's universe, the app is your integration test. The test code you write in your test is compiled directly into your .apk (Android) / .app (iOS), so if you wanted to "restart your app during UI test", you'd have to essentially kill the test and run it again.

Yes, but anyway, restart test or app. It doesn't really matter imo. We need to be able actually to test how app works if I run app from scratch but with some data in shared_pref or database. Is it possible to accomplish this without restarting test or not? This is quite common thing to do and if it's impossible for now then big amount of tests should be tested manually.

Does flutter test integration_test uninstalls app after every executing each *_test.dart file?

Does flutter test integration_test uninstall the app after executing each *_test.dart file?

I'm not able to configure execution order for test files. When I run tests inside one file I get this error
'package:flutter_downloader/src/downloader.dart': Failed assertion: line 48 pos 7: '!_initialized': plugin flutter_downloader has already been initialized which as I understand happens because I call main from the second test and app wasn't killed on previous one.

happens because I call main from the second test and app wasn't killed on previous one

Yeah, that sounds like the root cause.

happens because I call main from the second test and app wasn't killed on previous one

Yeah, that sounds like the root cause.

managed to do the job like this
/// For integration testing purposes
bool _nativePluginsInitialized = false;
Future<void> run(AppEnvironment environment) async {
  final widgetsBinding = WidgetsFlutterBinding.ensureInitialized();
  if (!_nativePluginsInitialized) {
    FlutterNativeSplash.preserve(widgetsBinding: widgetsBinding);
    await Firebase.initializeApp(
      options: getFirebaseOptionsForEnvironment(environment),
    );
    await FlutterDownloader.initialize(debug: !environment.isProd);
    _nativePluginsInitialized = true;
  }
  await configureDependencies(environment);
....
everything else which depends on getIt + runApp with UniqueKey

final getIt = GetIt.instance;

@InjectableInit(preferRelativeImports: false)
Future<void> configureDependencies(AppEnvironment environment) async {
  await getIt.reset();
  await $initGetIt(getIt, environment: environment.name);
  getIt<DiConfigurator>().configure(environment);
}


Padding left on repohead breaks for gists

Example URL:
https://gist.github.com/MiniDigger/872365b35245bec55660e64d2ca46c47
Example Screenshots:
https://i.imgur.com/ME0pTsX.png https://i.imgur.com/DDFYwJa.png

16:9 (1080p) and 21:9 (1440p)
Browser:
Chrome 83 on Win10

This has been fixed and will be released tomorrow.


Fix: New disclaimer: Do not send to exchanges on certain networks (AH) #8149

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #8149
[x] ## Did your issue had any of the "$" label on it?
[x] My DOT address: Payout

@JustLuuuu @prury please review

@AshutoshSingh00001
I wanted to drop my bit here.

It's not very clear why people should not send the funds to exchange.
We are not offering any solution to them (what should they do if they want to send funds to exchange?)
The hovering info point has the same text as the main text.
I would put a different text under the info circle: Something like if you are sending your funds from Assethub to exchange, your funds may be permanently lost; teleport them before sending. Or something in this style

@AshutoshSingh00001
I wanted to drop my bit here.

It's not very clear why people should not send the funds to exchange.
We are not offering any solution to them (what should they do if they want to send funds to exchange?)
The hovering info point has the same text as the main text.
I would put a different text under the info circle: Something like if you are sending your funds from Assethub to exchange, your funds may be permanently lost; teleport them before sending. Or something in this style

thanks for the reply @JustLuuuu
i'lll be updating my pr according to your needs

AAA text ran away from the info box 😂

mobile needs work as well:

Uf, I'm not sure about this.
Sorry, but I did not drop any instructions, now it's just a random toggle button that does not make sense.
https://github.com/kodadot/nft-gallery/issues/8149#issuecomment-1817904418


How to document array elements?

Hi,
I have a function that takes an array of strings.
Something like:
function myFunc(args) {
    var a = args[0];
    var b = args[1];
}

But I want to specify what each element within the array represents.
How can I achieve that? I tried with something like:
/**
 * @param {String[]} args
 * @param {String}  args.0 - attribute name.
 * @param {String}  args.1 - value to set.
 */

But obviously this is wrong since they are interpreted as properties.
Of course, I also tried with args[0] but I get an error at jsdoc generation phase.
Finally, Google did not help this time. :/
Any suggestion?

Same question for me.

I'm also wondering this.  In my case, I have a typedef of an array, for which the first element has a particular significance and should always be a number.  Any suggestions how to document this?

i'm using it

/**
 * The `@returns` below was autogenerated by WebStorm:
 * @returns {Promise.<{f: [number,number], b: [string,string]}>}
 */
foo() {
  return Promise.resolve({
    f: [1, 2],
    b: ['bar', 'baz']
  })
}

There's currently no way to document the expected type of individual array elements. The best you can do is the workarounds proposed by @brunano21 and @ElfenLiedGH. Or, of course, you can just use text:
/**
 * Foo function.
 *
 * @param {Array} bar - The bar array. The first element must be a number, and the
 * second element must be a string.
 */
function foo(bar) {}

I'm open to a pull request that supports something like the following example (inspired by WebStorm), but keep in mind that most of the work will involve modifying the Catharsis type-expression parser:
/**
 * Foo function.
 *
 * @param {[number, string]} bar - The bar array.
 */
function foo(bar) {}

While it is not great DRY, one advantage of the @property {type} index - Description approach would be that a named label might be made allowable after the index to represent the item, e.g.:
/**
* @property {string} 0 type The type that...
* @property {string} 1 value The value which ...
*/

And if the list is long, the numeric indexes also do help one see at a glance what the number is without having to count commas....

Any updates on this from the maintainers?

What if the array is defined like
const myList = [1,' hellow', true, { a: 1 }]

or
const [hello, world] = 'hello world'.split(' ');

Now it's possible to document arrays like this (at least on VS Code):

It's also possible to name elements:

@brunoenribeiro what exact values are expected to be passed in both of your examples? It's not immediately clear what a named element in an array is.

@brunoenribeiro what exact values are expected to be passed in both of your examples? It's not immediately clear what a named element in an array is.

Hey there! Sorry for the delay.
In both cases, you should pass an array with 2 elements. For instance: [0, 'zerkms'].
There'll be no difference to the code itself. The only difference is how much information will be provided in the documentation.
Other example: suppose you have a function vector3Adapter() that receive an array with 3 numbers. You can name each element and make the docs be clearer:

But you still can destructure the array using any names you want:

@brunoenribeiro , @zerkms : VisualStudio is using TypeScript's own extension of JSDoc. JSDoc itself does not appear to support the "tuples" you are describing; see https://github.com/jsdoc/jsdoc/issues/1703 nor do its docs embrace such a type (and Closure, whose types JSdoc mentions supporting, doesn't either: https://github.com/google/closure-compiler/issues/379 ).
(Side: note: these "tuples" are not the same as those in the stage 2 JS proposal: https://github.com/tc39/proposal-record-tuple ).
Of course, it's good to know about this for those who are using the TypeScript extension, and it'd be nice for it to be supported.

This way

/**
 * Foo function.
 *
 * @param {[number, string]} bar - The bar array.
 */
function foo(bar) {}

is throwing an error in the last versions of the library.

If you want to define valid string values that an array can accept, you can do it like this
/**
 * @param {Array<('cjs' | 'es' | 'iife')>} formats
 * @returns {void}
 */
function config(formats) {
}


Reach feature parity with python-wopeditor

The new wopeditor already has better UI in most places than python-wopeditor, but some features are still missing:

[x] model preview
[x] setting number of model components/gaussians
[x] alphabet export
[x] mod download

⊂(✰‿✰)つ


Sync up with katib component rename

Sync up with change of https://github.com/kubeflow/katib/issues/1004

This change is

/assign @sarahmaddox

/lgtm
/approve
Thanks!


Fix Update coordinator.py

Fix to https://github.com/kvj/hass_openwrt/issues/36#issue-2674941522

Thanks!


TST: new errors on linux-{aarch64,ppc64le} related to cdf with fft in TestLevyStable

I'm getting some new errors in https://github.com/conda-forge/scipy-feedstock/pull/255, which are most likely triggered somehow by a third-party dependency, as I didn't see these failures on any recent runs, and there's no new scipy version to blame. It started today, as of a couple hours ago, going from all green (modulo some spurious timeouts), to all aarch/ppc64le runs finishing with the exact same set of test failures.
Coincidentally, all the failing tests raise the same RuntimeWarning:
stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf-1.0-points0-0.0-0.25]
stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf-1.0-points0-0.0-0.5]
stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf-1.0-points0-0.0-0.75]
stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf--1.0-points2-1.0-0.25]
stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf--1.0-points2-1.0-0.5]
stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf--1.0-points2-1.0-0.75]
  $PREFIX/lib/python3.10/site-packages/scipy/stats/_levy_stable/__init__.py:1068: RuntimeWarning: Cumulative density calculations experimental for FFT method. Use piecewise method instead.
    warnings.warn(

While the logs talk about missed toleranced, I think the failures must be considered total, given that one side of the comparision is unexpectedly constant zero or one.

test failures incl. main error message
=========================== short test summary info ============================
FAILED stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf-1.0-points0-0.0-0.25] - AssertionError:
Arrays are not almost equal to 7 decimals

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 0.02345738
Max relative difference: inf
 x: array([0.0116484, 0.0116608, 0.0116732, 0.0116857, 0.0116982, 0.0117106,
       0.0117228, 0.0117349, 0.0117468, 0.0234574])
 y: array([0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])
FAILED stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf-1.0-points0-0.0-0.5] - AssertionError:
Arrays are not almost equal to 7 decimals

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 0.0005926
Max relative difference: inf
 x: array([0.0005859, 0.0005867, 0.0005875, 0.0005883, 0.0005891, 0.0005899,
       0.0005907, 0.0005915, 0.0005923, 0.0005926])
 y: array([0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])
FAILED stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf-1.0-points0-0.0-0.75] - AssertionError:
Arrays are not almost equal to 7 decimals

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 2.33537973e-05
Max relative difference: inf
 x: array([-2.3353797e-05, -2.3312442e-05, -2.3271041e-05, -2.3229594e-05,
       -2.3188102e-05, -2.3146564e-05, -2.3104981e-05, -2.3063353e-05,
       -2.3021680e-05, -2.2979962e-05])
 y: array([0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])
FAILED stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf--1.0-points2-1.0-0.25] - AssertionError:
Arrays are not almost equal to 7 decimals

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 0.11131309
Max relative difference: 0.11131309
 x: array([0.8886869, 0.9003975, 0.9004094, 0.9004215, 0.9004337, 0.9004461,
       0.9004586, 0.9004711, 0.9004835, 0.9004958])
 y: array([1., 1., 1., 1., 1., 1., 1., 1., 1., 1.])
FAILED stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf--1.0-points2-1.0-0.5] - AssertionError:
Arrays are not almost equal to 7 decimals

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 0.01326475
Max relative difference: 0.01326475
 x: array([0.9867353, 0.9867356, 0.9867364, 0.9867372, 0.986738 , 0.9867388,
       0.9867396, 0.9867404, 0.9867412, 0.986742 ])
 y: array([1., 1., 1., 1., 1., 1., 1., 1., 1., 1.])
FAILED stats/tests/test_distributions.py::TestLevyStable::test_distribution_outside_support[cdf--1.0-points2-1.0-0.75] - AssertionError:
Arrays are not almost equal to 7 decimals

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 0.00165994
Max relative difference: 0.00165994
 x: array([0.9983401, 0.9983401, 0.9983401, 0.9983402, 0.9983402, 0.9983403,
       0.9983403, 0.9983404, 0.9983404, 0.9983404])
 y: array([1., 1., 1., 1., 1., 1., 1., 1., 1., 1.])
= 6 failed, 42445 passed, 2805 skipped, 134 xfailed, 12 xpassed, 6 warnings in 5683.39s (1:34:43) =

python dev.py test -t scipy/stats/tests/test_distributions.py::TestLevyStable (and the full suite) passes for me with Python 3.9 on the Linux aarch64 architecture below the fold, along with Red Hat GNU toolchain 8.5.0 (and same thing for 11.2.0, and also tests still pass if I go back to NumPy 1.22.4 per your log).

Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              256
On-line CPU(s) list: 0-255
Thread(s) per core:  4
Core(s) per socket:  32
Socket(s):           2
NUMA node(s):        2
Vendor ID:           Cavium
Model:               0
Model name:          ThunderX2 99xx
Stepping:            0x1
BogoMIPS:            400.00
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            32768K
NUMA node0 CPU(s):   0-127
NUMA node1 CPU(s):   128-255
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm

(and using python tools/openblas_support.py  for OpenBLAS).
My pip list is below:

Package            Version
------------------ ----------
appdirs            1.4.4
attrs              22.1.0
bashlex            0.18
beniget            0.4.1
bracex             2.3.post1
certifi            2022.12.7
charset-normalizer 2.1.1
cibuildwheel       2.12.0
click              8.1.3
cloudpickle        2.2.0
commonmark         0.9.1
Cython             3.0.2
devpy              0.1a3.dev0
doit               0.36.0
exceptiongroup     1.0.4
execnet            1.9.0
filelock           3.9.0
gast               0.5.3
hypothesis         6.87.1
idna               3.4
importlib-metadata 5.2.0
iniconfig          1.1.1
meson              1.2.2
meson-python       0.14.0
ninja              <IP_ADDRESS>
numpy              1.26.0
packaging          22.0
pip                23.2.1
platformdirs       2.6.2
pluggy             1.0.0
ply                3.11
pooch              1.6.0
pybind11           2.11.1
pydevtool          0.3.0
Pygments           2.13.0
pyproject-metadata 0.7.1
pytest             7.4.2
pytest-xdist       3.3.1
pythran            0.14.0
requests           2.28.1
rich               12.6.0
rich-click         1.6.0
setuptools         56.0.0
sortedcontainers   2.4.0
threadpoolctl      3.2.0
toml               0.10.2
tomli              2.0.1
typing_extensions  4.4.0
urllib3            1.26.13
zipp               3.11.0

I did notice some weaknesses for pytest running at high concurrency on the slower ARM cores though, having to reduce the level of concurrency because Different tests were collected between gw7 and gw31 type errors.
So I guess I'm saying I can't reproduce locally just yet, but do have convenient access to the hardware if there's a more specific route to reproduction.

Thanks for checking! Good to know you're not hitting it. It might also somehow be related to QEMU, see discussion in https://github.com/scipy/scipy/issues/19210.
Though since we didn't observe it for several runs, and then all at once, I'm guessing either infrastructure or third party libs are at fault. Though it's possible of course - like Ralf was saying - that there are lurking bugs already, and perhaps we're just now starting to trigger them.

This is fixed as of 1.12 from the POV of conda-forge, closing.


[release-v0.42.x] picking up latest changes in knative 1.8

Changes
This PR is a result of:
go get<EMAIL_ADDRESS>./hack/update-codegen.sh

knative.dev/pkg was recently updated to include a performance fix which helped reduced the CPU usage by 61% and memory usage by 44% for huge pipelines. This PR is updating the tekton controllers to include that fix such that Pipelines 0.42.x can take advantage of this performance improvement.
The same fix was cherry picked in knative.dev/pkg 1.9. Tekton pipeline was updated to use knative 1.9 post 0.45 in PR #6062.
We have another PR #6194 open to update pipeline controllers in the main branch.
/kind misc

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Bring the latest performance fix in knative/pkg which helps reduce CPU/Memory usage for huge pipelines.

/test check-pr-has-kind-label

/retest
/approve

/retest
/lgtm

/retest

/test pull-tekton-pipeline-beta-integration-tests

/retest

/retest


Cannot resolve symbol frame

In step 3 the line "locationScene.processFrame(frame);" has a frame parameter. Should this be defined as variable. There is no other reference to it.
Note: Since setOnUpdateListener is deprecated I am using addOnUpdateListener.

you can get instance of frame like this
Frame frame = arSceneView.getArFrame();
please close the issue if it resolve your problem


Time to hide

Instead of time to hide, is there a way to make it wait until page is fully loaded to hide?

You might have to use it in a different way. You have to hide the div when window is fully loaded.
$(window).load function will help.


fix .swap() by reverting improperly merged @classmethod change

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[X] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

brings back .swap() (will not work with inpainting, sequential guidance, or xformers. untested with SDXL)

SD 1.x results
Prompt: ("a cat in the forest", "a fantasy forest").and()
Result: ❌ operation completes without error, but only "a cat in the forest" is logged and the result looks equivalent to that part alone; the second term "a fantasy forest" seemingly having no impact at all.
Prompt: silhouette of a dancing (Elvis).swap(frog)
Result: ✅ behaving appropriately. Both terms logged, output is as expected.
Prompt: (pineapple, cogwheel).blend()
Result: ✅ behaving appropriately. Both terms logged, output is as expected (probably? I should have picked a blend I had a prior result for.)
SD 2.x results
Same as SD 1.x.

SDXL results
Exceptions all the way. Is that in scope here or should we consider it separately?

thanks @keturn.
.and() support is being looked at by @StAlKeR7779 (there's not PR), so it's a known issue that that doesn't work.
i don't know what SDXL support should look like. i cannot run SDXL on my machine which makes me a poor candidate for looking into it.

Merging as the missing pieces (.and() and SDXL) are both known WIP items.


Fix skipvalue for maps and arrays

Replaces #5. Renamed branch.
I discovered these bugs trying to read pre-written object files.

I actually ran into this yesterday (with files created without byte lengths).


[SPARK-15232][SQL] Add subquery SQL building tests to LogicalPlanToSQLSuite

What changes were proposed in this pull request?
We currently test subquery SQL building using the HiveCompatibilitySuite. The is not desired since SQL building is actually a part of sql/core and because we are slowly reducing our dependency on Hive. This PR adds the same tests from the whitelist of HiveCompatibilitySuite into LogicalPlanToSQLSuite.
How was this patch tested?
This adds more testcases. Pass the Jenkins tests.

Test build #62936 has started for PR 14383 at commit 5b313fc.

cc @hvanhovell and @rxin

Test build #62938 has started for PR 14383 at commit 7292435.

Test build #62936 has finished for PR 14383 at commit 5b313fc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62936/
Test FAILed.

Test build #62941 has started for PR 14383 at commit 9a49580.

Test build #62942 has started for PR 14383 at commit d7d70e6.

Test build #62938 has finished for PR 14383 at commit 7292435.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62938/
Test PASSed.

Merged build finished. Test PASSed.

Test build #62941 has finished for PR 14383 at commit 9a49580.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62941/
Test PASSed.

Test build #62942 has finished for PR 14383 at commit d7d70e6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62942/
Test PASSed.

Hi, @rxin and @hvanhovell .
It's ready for review again.

Looks reasonable to me. Merging in master/2.0.

Thank you for review and merging, @rxin .


Update badges

Additional Notes
The badge for test results gets regenerated on every commit to master here https://github.com/DataDog/integrations-core/blob/badges/test-results.svg


[release-1.13] fix istioctl x metrics

This is an automated cherry-pick of #36948

fix https://github.com/istio/istio/issues/37184


HT 466

Pick the correct file to diff against.

@amit-altiscale this is a huge diff, can you please let us know (pref. via JIRA) what is it you're trying to achieve?

Hi Roman,
I'm sorry that request was sent out on error. My apologies.
regards
--amit
On Thu, Jul 14, 2016 at 5:51 PM, Roman V Shaposhnik <
<EMAIL_ADDRESS>wrote:

@amit-altiscale https://github.com/amit-altiscale this is a huge diff,
can you please let us know (pref. via JIRA) what is it you're trying to
achieve?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/bigtop/pull/133#issuecomment-232815260, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQATPCCKC-mE89p7-WO1qB2_MYVBRC7Iks5qVr1lgaJpZM4JMi8Y
.


[104] Issue #104 - March 8, 2018

To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.
The current draft for this issue in _drafts/. If you want to contribute directly, open a pull request.

Created a draft for you @RomanVolkov :)

https://github.com/apple/swift-clang/commit/334f080ab3c1bfbb13601a4f404b9c97e2294eb9

https://github.com/apple/swift/pull/14442

Jordan Rose blog post
http://belkadan.com/blog/2018/02/Many-to-Many-Protocols/

https://twitter.com/ericasadun/status/968705706777042944
https://forums.swift.org/t/accepted-se-198-playground-quicklook-api-revamp/10401

@BasThomas  thanks!

https://github.com/apple/swift-evolution/issues/794
Sent with GitHawk

https://forums.developer.apple.com/thread/97662

https://github.com/apple/swift/pull/14854

Thanks for sharing these @mackoj!
Sent with GitHawk

https://twitter.com/Catfish_Man/status/968567431835795457
This (from @ilseman) is probably the Swift change I’m most excited about this year. Still a ways to go, but look at those delicious 2.5x ObjC bridging speedups even on this relatively early version! https://github.com/apple/swift/pull/14755

198 accepted: https://github.com/apple/swift-evolution/commit/6591496881319b749d4503a748317aedcd5be46a

Community reports of improved build times with Xcode 9.3 beat 3
https://twitter.com/benasher44/status/968905975724892160
https://twitter.com/adellibovi/status/969012500682477568

https://github.com/apple/swift-nio

Swift 4.2: https://github.com/apple/swift-evolution/pull/795

https://download.developer.apple.com/Developer_Tools/Xcode_9.3_beta_3/Release_Notes_for_Xcode_9.3_beta_3.pdf
Testing
xccov is a new command-line utility for inspecting the contents of Xcode coverage reports. It can be used to view coverage data in both human-readable and machine parseable format. See the man page for more information about the tool (man xccov). (37172926)

Also, regarding swift-nio (which @BasThomas linked above), they're using GH issues, not JIRA:
https://github.com/apple/swift-nio/issues (just interesting to note)

hey @RomanVolkov 👋 Do you want to try to get a draft going soon? 😄

@mackoj I covered xccov in issue 103 already. :)

@BasThomas sorry I forgot about it :/

https://github.com/apple/swift/pull/14913

Community: First Class Swift API for Objective-C Frameworks

@jessesquires  yeah. I'll make first draft soon. Just had a crazy week after week of snowboarding and broken arm:) will start soon

Oh noes! If you do need any help, feel free to let me know.

Oh man. Sorry @RomanVolkov ! Get well soon 😊

Update on SE 192
https://forums.swift.org/t/se-0192-non-exhaustive-enums/7291/337

@BasThomas @jessesquires thank you guys:)

@RomanVolkov: Were you snowboarding swiftly ? Get well soon :)
Sent from my iPhone

On 03-Mar-2018, at 10:52 AM, Jesse Squires<EMAIL_ADDRESS>wrote:
@RomanVolkov

@tapthaker yes:) just had bad braking from the top

@SwiftWeekly/writers Sorry about that, but seems I won't be able to make a good issue this time. Broken arm after traveling kicked me off of regular rhythm and past days were very chaotic. If anyone can handle this one - that will be great. I pushed new branch, but it has very few changes, just the list of started tasks (which is bigger that usual).
Sorry again for late news

No worries - I can take over if no one else wants to :)

@BasThomas thanks a lot! Hope will make another issue soon)

Xcode 9 beta 4: https://download.developer.apple.com/Developer_Tools/Xcode_9.3_beta_4/Release_Notes_for_Xcode_9.3_beta_4.pdf

Take care @RomanVolkov . @BasThomas : let me know if I can help. We can split work amongst ourselves if need be.

fun trivia from Doug Gregor:
https://twitter.com/dgregor79/status/970857272724172800

Thanks @RomanVolkov ! Get well! 🤒

Thanks @tapthaker! Feel free to commit directly to the branch. 😊

https://twitter.com/ericasadun/status/970754573609484288

@BasThomas I will take up Commits & Pull Requests & Proposals.

@tapthaker if you don't mind, just make your edits directly on the existing PR #371 😄

194 accepted with revisions (https://github.com/apple/swift-evolution/pull/798)


serverless-init - better handling of non executable command

Currently it is really hard to debug issues if Datadog serverless-init is used and there is some typo or command that should be run does not exist or is not executable. Here is example dockerfile:
# syntax=docker/dockerfile:1
FROM php:8.2.12-fpm-bookworm

COPY --from=datadog/serverless-init:1 /datadog-init /app/datadog-init

ADD https://github.com/DataDog/dd-trace-php/releases/latest/download/datadog-setup.php /datadog-setup.php

RUN php /datadog-setup.php --php-bin=all --enable-profiling

ENV DD_VERSION=test
ENV DD_LOGS_ENABLED=true
ENV DD_TRACE_ENABLED=true
ENV DD_TRACE_PROPAGATION_STYLE=datadog
ENV DD_APM_ENABLED=true
ENV DD_SERVICE=my-service
ENV DD_SITE=datadoghq.eu
ENV DD_DOGSTATSD_PORT=8125

ENTRYPOINT ["/app/datadog-init"]

CMD ["/usr/local/sbin/php-fm"]

CMD contains a typo and when running this container there is no error message, container just exit with error code.
$ docker build -f Dockerfile . -t dd-exit:test
....

$ docker run -it --rm -e DD_API_KEY="key"  -e DD_ENV=test --name=dd-exit dd-exit:test

$

This is far from optimal DX and pretty hard to debug if pushed to the cloud. Would it be possible for serverless-init to check first if command from CMD exist and is executable? If not then exit with some meaningful error message?
Thank you.

Hello, can u assing that issue to me??


A couple of my projects are showing up in my gallery as completed tutorials when they are not

Describe the bug

Wondering if this is connected to getting the "Project open elsewhere" message I get when I'm working on multiple projects (and no duplicates).
Info: I copy the JSON from some projects into the tutorial tool to create new tutorials.

No repro.


Colons (and possibly other characters) in Test Cases Cause File Path Errors

Summary
Most filesystems recognize the colon character as a path delimiter. For example, here are several reserved characters in Windows file systems, inclusive of the colon character. If a test case has a colon (or, likely any other illegal file/path character), the robotframework-FlaUI library does not escape the character, and thus tries to save screenshots using this as part of the filename.
Example
Assuming we've installed and imported robotframework-flaui, a test case with this name:
Test Case 1234: Something to Test
    [Documentation]    Pretend we're testing something here...
    Log to Console    What's the state of the desktop?
    Take Screenshot

...will cause the library to attempt to create a screenshot with a name like: test_case_1234:_something_to_test.jpg
Issue
The screenshot cannot be successfully created because the colon is an illegal/reserved character.

Invalid characters will be removed in future by testcase name and hostname.

Fix merged to master next Version will fix this issue.


conv2d_9_input_3:0 is both fed and fetched.

Whenever I run mnist attention example I get the below error
#InvalidArgumentError: conv2d_9_input_3:0 is both fed and fetched.
I tried re installing keras vis as I am on google colaboratory, but that fix did not work.

Hi @MatthiasRathbun .
Probably, You used keras-vis 0.4.1 which was installed via PiPY, didn't you.
The version has some problems, so please try to re-install keras-vis again such as below:
pip install git+https://github.com/raghakot/keras-vis.git -U

Thanks!


pull request for e2e test at 11/12/2016 18:56:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


css syntax is not working in css component definitions or

when declaring a css component in templ, the css is not properly highlighted outside of the go part.
same goes for inside the css class of a tag, like a button:

i cant assign myself but ill push a PR later @vrischmann

is partially adressed in https://github.com/vrischmann/tree-sitter-templ/pull/10

Hi.
I'm getting back to this issue to see if it can be closed.
As far as I can tell there were two issues:

CSS properties not properly highlighted in a CSS component
Bad highlighting in the class attribute of a tag

The first point was addressed by your PR (#10)
The second point I'm not sure the issue actually still exists; this is what I'm getting right now:

@BKR-dev can you confirm the highlighting looks OK for you too ?

i think this looks good so i havent yet added more as i think it helps enough.
happy new year btw!

Thanks, I'll close this issue then.
Happy new year !


Provide mechanism for opting applications out of uprobe attachment

Despite our best intentions and thorough testing, there are times where uprobes are undesirable or cause Pixie's PEM to crash. An example of the former is when applications perform stack unwinding. This leads to applications thinking that the stack is corrupt and results in them crashing (https://github.com/cloudamqp/amqproxy/issues/117). As for an example of the latter, our Go binary parsing has had edge cases addressed (https://github.com/pixie-io/pixie/issues/1300), but there is still at least one case that causes PEMs to crash (https://github.com/pixie-io/pixie/issues/1646).
Providing the ability to define a uprobe opt out list would allow end users to work around any PEM bugs and prevent probing applications that could otherwise crash under our instrumentation (see amqproxy issue above).

This was completed in #1971 and will be available in the v0.14.11 vizier release (once it's made).


[main] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.23
./hack/update-codegen.sh

Details:
bumping knative.dev/networking 945b81a...89774aa:
  > 89774aa Append headers to TestRule to verify we hit expected backend (# 385)
  > e294898 upgrade to latest dependencies (# 390)

/lgtm
/approve


Feature request: Expand colormap options

Super neat project!
I was wondering if we could expand what kinds of colormaps we can pass into STYLES (stylename/palettename).
On a quick prototype, passing in a cmocean colormap from palettable works with in get_map.py.
import palettable
colormap = palettable.cmocean.sequential.Ice_20.get_mpl_colormap()

shaded = tf.shade(
    mesh,
    cmap=colormap #self.palettename
    how="linear",
    span=span,
)

You can pass any default matplotlib colormap name into raster/{colormap}! We are thinking of how to do custom but for now this is a bit of options if it wasn't clear

You can also deploy this custom with the render function overridden to further customize


[Bug Report] dropdown not opening inside a table row

Element UI version
2.11.1
OS/Browsers version
ubuntu
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/cjs1fgbq/
Steps to reproduce
just add an el-dropdown in  a table row fiddle:https://jsfiddle.net/cjs1fgbq/
What is Expected?
the dropdown should get opened even inside the table row
What is actually happening?
the dropdown is not getting opened inside a table row

HI... Any update on this?

same problem

@wacky6 could you look into this please if you get some free time, I am stuck with this, I can't use any dropdown in table

<el-table-column prop="select" label="下拉">
  <template slot-scope="scope">
    ...
  </template>
</el-table-column>

Adding slot-scope="scope" did the trick, Thanks

why must added   slot-scope="scope",  even not use scope attr.


Feature request: Support for hex and binary literals

In computer science and embedded device engineering, it often makes sense to work wit integers in a different base than decimal.
For example: Most ADCs have resolutions in powers of 2, so ADC full range would be something like (1<<14)-1 for a 14-bit ADC.
This is easily expressed in hexadecimal as 0x3FFF (binary 0b0011_1111_1111_1111), while in decimal it is the highly unintuitive 16383.
So when I debug an ADC, and it returns 0x3b26, it would make sense to, in Calcpad, do
Vref=0.6V
adc=0x3b26
res=0x3fff
gain=1/6
input = adc/res*(Vref/gain)

Instead, I have to first perform the base conversion somewhere else to arrive at
Vref=0.6V
adc=15142
res=16383
gain=1/6
input = adc/res*(Vref/gain)

Occasionally it also makes sense to represent data in binary, when for example, bit 13 of a register means "reboot" and bit 14 means "smoke while doing so". Showing the contents of a 32-bit register as 0b00000000_00000000_01100000_00000000 makes it easy to see what bits are set.
So I would like if there were native support for the 0x and 0b integer prefixes, along with a way to force a result into the corresponding format (with truncation to integer optional, "not an integer" error as an alternative).
As Calcpad is (as far as I can tell) based on Python, which has native support for these representations (along with support for literals with _ as group separators), this seems like it should mostly be a parsing engine change, not a math engine change.
Fixed or floating point conversions (except perhaps IEEE 754, if the implementer feels particularly masochistic) are usually too custom to merit incusion in a general purpose software package, so are explicitly excluded from this feature request.

(I'm aware that for many common ADC implementations, I should use 0x4000, not 0x3FFF, in the calculation. That's just an additional complexity in the process to keep in mind, so removing decimal conversion as an additional stumbling block would really benefit the mind).

Hi!
Thank you for your suggestion. I have tought about implementing different numerical systems, other than decimal. Calcpad is not based on Python (it has even nothing to do with it), but it is still just a matter of parsing and rendering the number back to text. I will consider adding this option to future versions. Also, we can implemplement any base-n system quite easily. This is simple math.


Update delete-calendar.md

Updating the correct recipient type details.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/4450

@kwekuako Please merge this PR. Thanks.


python name 'null' is not defined

Hi, great work!
When I ran this script it threw an error 'python name 'null' is not defined'
In remote.py I changed to
def connect(kind_id, delay=None):
Running Python 3.9.1 on Windows 10 Version 10.0.19042 Build 19042

Changing it to None should of fixed that, I have updated the code with the proper remote.py file. Try downloading and installing it again. If that does not work, we can go from there.

Changing it to None should of fixed that, I have updated the code with the proper remote.py file. Try downloading and installing it again. If that does not work, we can go from there.

Hey, thanks for the quick reply. Yes that did fix the issue. Thanks bud.

Hey, thanks for the quick reply. Yes that did fix the issue. Thanks bud.


Correction for raw affiliation CNRS, UMR 5574

Correction needed for raw affiliation CNRS, UMR 5574
raw_affiliation_name: CNRS, UMR 5574
new_rors: 04zzdbj59;0084x3h80
previous_rors: 04zzdbj59
works_examples: W2121734372;W1888374515;W1752024775;W2109896455
contact: 888735b5a2bb827be82cd57cf4c8111c:5467786a8a9ebacefbac402ca908 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


User login is disabled after i run it on our local server.

We hope to run it on our local server so that we can manage our team, at first we hope to login and share the collections and documents to anyone in  our team, so can you help us to make the ability to login by local user in the database, and manage our team in the system?

For local development checkout How to set up local development

Checkout out Wiki on Hosting

For local development checkout How to set up local development
Checkout out Wiki on Hosting

yeah, we have build it local on our local server, but we cannot login and manage the team, so can you help us to approve the login ability by update the project?

Step 1:
Set up local development environment. You've completed this step.
Step 2:
Create a Firebase project and obtain app's access keys.
Step 3:
Rename .env.example to .env and fill it with your own Firebase API keys.

Step 1:
Set up local development environment. You've completed this step.
Step 2:
Create a Firebase project and obtain app's access keys.
Step 3:
Rename .env.example to .env and fill it with your own Firebase API keys.
Make sure you added Sign in with Google / GitHub from Firebase Dashboard.

OK thanks. I will have a try.


Random iAPS stoppage overnight

IAPS has been shutting down randomly overnight and is stalled when opening in the morning. This has happened at least 4 times. I have screenshots and logs for two of the events which are attached. Upon waking I check iAPS first thing. It will be stalled with a Red Loop for greater than 300min and will not automatically reconnect. Function only regained after forcing communication with Dash through Test Beeps. I have been using iAPS since Nov 23. Previously Looped for 5 years and never had this happen. Dexcom G6 used in both Loop and iAPS. Same iphone 13 running iOS 17.2.1. iAPS ver 3.3.1? (sorry already deleted app. Build was 1-9-24).
iAPS log.txt
iAPS log02062024.txt
log_prev.txt
log.txt

I am not a developer but a simple user. @dnzyx (Dan Moody) suggested I post shots and logs here after reviewing. I am not good at this and I apologize for breaking any protocols or if some info is irrelevant (seems like some of the screenshots may not be related). The dates of the incidents were 2-6-24 and 1-14-24 which have both shots and logs. Your help is greatly appreciated. I have moved back to Loop temporarily until the source of these shutdowns can be determined.

Upon first look it looks like a CGM problem, as CGM readings are missing. Without a new fresh CGM reading iAPS will not loop . Is your transmitter getting old?

The transmitter had a month left on it at the time. I had been using Loop for 4 years without any connectivity issues like this. Been using iAPS for about a month when problems started creeping in. It is NOT a Dexcom problem. Been using that for about 10 years. Please read the logs if possible. I moved back to Loop because this is so disturbing. I saw another apparent case on FB and recommended submitting logs. I think this problem is out there and no one is reporting it because they get the same answer. It's Dexcom. No, it is iAPS when used with Dexcom.

Your screenshot for Dexcom app shows missed readings for 3-4 hours. IAPS can’t get its readings from listening at the Dexcom traffic. If no traffic(as your screenshot illustrates), no readings in iAPS.


Refer to "core concepts" earlier and more

https://fluxcd.io/docs/concepts/ explains core concepts like "Kustomization". This is great.
We should re-work the flow of our docs a little, so new users are directed to this more early on, e.g. on /docs/ or /docs/get-started where e.g. Kustomization is mentioned and it's sort of assumed that you know what it and its impact is - it will make the life unsuspecting and beginner type of readers easier.

Tracking in #1723 from now. 📇


ECNIM-710

Type

[ ] Bugfix 🐛
[ ] New feature 🌈
[x] Change request 🤓
[ ] Documentation 📚
[x] Tech debt 👩💻

Changes proposed ✔
<EMAIL_ADDRESS>💡 Others

Some patterns extend the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

<EMAIL_ADDRESS>💡 Others

This component extends the properties of the Box component which has undergone some significant changes, so you should consult the Box component documentation when performing this update. (#56 by @juniorconquista)

📚 3rd party library updates

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(#56 by @juniorconquista)

Codecov Report
Patch coverage: 75.00% and no project coverage change.

Comparison is base (20a11b0) 92.37% compared to head (85f9734) 92.37%.

: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      #56   +/-   ##
=======================================
  Coverage   92.37%   92.37%
=======================================
  Files          94       94
  Lines         603      603
  Branches       88       88
=======================================
  Hits          557      557
  Misses         46       46

Impacted Files
Coverage Δ

...ges/react/src/components/AppShell/src/AppShell.tsx
90.90% <ø> (ø)

...act/src/components/CalloutCard/src/CalloutCard.tsx
100.00% <ø> (ø)

...s/react/src/components/DataTable/src/DataTable.tsx
100.00% <ø> (ø)

...ents/DataTableBulkActions/DataTableBulkActions.tsx
100.00% <ø> (ø)

...ges/react/src/components/HelpLink/src/HelpLink.tsx
100.00% <ø> (ø)

...react/src/components/MenuButton/src/MenuButton.tsx
100.00% <ø> (ø)

...onents/MenuButtonAccordion/MenuButtonAccordion.tsx
28.57% <0.00%> (ø)

...kages/react/src/components/NavTabs/src/NavTabs.tsx
100.00% <ø> (ø)

...NavTabs/src/components/NavTabsItem/NavTabsItem.tsx
90.90% <ø> (ø)

...ts/ThumbnailWithAction/src/ThumbnailWithAction.tsx
100.00% <ø> (ø)

... and 3 more

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


WIP: Add lutram tests

This PR adds a first basic test for LUTRAMs.
To have a full coverage we'd need to add at least one test for each possible macro:

[x] RAM32X1S
[ ] RAM32X1D
[x] RAM32M
[x] RAM64X1S
[ ] RAM64X1D
[x] RAM64M
[ ] RAM128X1S
[ ] RAM128X1D
[ ] RAM256X1S

TODO:

[ ] add simulation tests
[ ] fix macro cells placement issue. despite completing place and route, and working on HW, the cells belonging to a macro, and specifically to a LUTRAM macro, end up being in different sites, which should not be allowed.

Closing, superseeded by https://github.com/SymbiFlow/fpga-interchange-tests/pull/78


Switch.Toggle service isn't working on Ewelink switches even from HA

If I test my Ewelink switches from the HA Developer tools/Services, they are not working with switch.toggle.
Services switch.turn_on and switch.turn_off are working however. Other (non-ewelink) switches are working with switch.toggle as well as from the app and from the watch, too.
I was about to use apps on my WearOS watch. Ewelink switches did nothing from the official wearos app (beta) so I had opened issue1954 there and slowly it became clear that it is caused by the addon. It wasn't working from the Home Slide app either (it's an unofficial HA client).
Tested versions:
Ewelink Addon 1.2.3
Home Assistant OS 7.0.rc1
Home Assistant Android client beta-1744-9fd3164-full

Hi, @perriert. The ha-addon doesn't support switch.toggle yet.

Hi, @perriert. The ha-addon doesn't support switch.toggle yet.

Thanks! Are there any plans to support it in the near future?

Hi, @perriert. My current task is to refactor some features that might cause bugs. This may take some time.

Hi @perriert , I don't know if you need a workaround for this problem, in any case you can find my simple solution on HA community

suggest you refer to this to deal with


@formkit/pro uses @formkit/utils but does not declare it as dependency

Reproduction
None
Describe the bug
Hey there!
I've noticed that the @formkit/pro package has an internal reference to @formkit/utils:
import {isRecord as e,isObject as t,isPojo as o,eq as n,undefine as r,whenAvailable as s,clone as a} from "@formkit/utils"

However, @formkit/utils isn't listed as a dependency in the package.json file, which causes issues in strict dependency managers like pnpm or Yarn. When using these package managers in strict mode, the missing dependency leads to build errors.
{
  "name": "@formkit/pro",
  "version": "0.127.6",
  "dependencies": {
    "@formkit/drag-and-drop": "^0.0.38",
    "@formkit/tempo": "^0.1.1"
  },
  "peerDependencies": {
    "@formkit/core": "^1.6.5",
    "@formkit/inputs": "^1.6.5"
  }
}

To fix this, adding @formkit/utils as a dependency in package.json should resolve the issue.
Environment
Not needed

@RomainLanz This should be resolved at @formkit/pro v0.127.7.


Theme7 does not work

I embedded the custom button theme in my nextjs project and it did not work. Nothing happens after you click the button.

Is theme7 the only one that does not work or do they all not work?

The script that the themes reference are rather heavy and are probably going to conflict with some of the elements of nextjs.  Thus, the button will probably need to be buffered into it's own content-area or placed in a more simple HTML page and then referenced into the project.

Theme 7 is the only theme not working
On Thu, Nov 4, 2021, 21:39 bph9 @.***> wrote:

Is theme7 the only one that does not work or do they all not work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CDCgov/covid19healthbot/issues/69#issuecomment-961358703,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DUQP2H47T4QLR7RZB3N3UKLVORANCNFSM5HMCTXCA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Okay i will try that
On Fri, Nov 5, 2021, 19:19 pwhitebe @.***> wrote:

The script that the themes reference are rather heavy and are probably
going to conflict with some of the elements of nextjs. Thus, the button
will probably need to be buffered into it's own content-area or placed in a
more simple HTML page and then referenced into the project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CDCgov/covid19healthbot/issues/69#issuecomment-962075407,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DUQISSED4XGB5JBC5GA3UKQN4XANCNFSM5HMCTXCA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Add network request data support.

Adds network request support for form data only.  I tried for a while to poke around to get streams also but it's a bit convoluted and I think I might have to wrap an existing mojo::Remote<ChunkedData> with my own mojo::Remote that  implements the same interface and traps info.
Tested this briefly but I don't see request data showing up in the UI yet, so something is still wrong even with the non-stream request data.  Still needs fixing before landing.

Ok this works now, and I can see form request data coming back in the UI for a simple test case I wrote.
This does NOT yet handle streaming request data.