Receiving:   werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.

When I am trying to add permissions to an existing role it is returning me
File "/opt/app-root/lib64/python3.11/site-packages/werkzeug/sansio/multipart.py", line 203, in next_event
raise RequestEntityTooLarge()
werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.
How to reproduce the bug

Go to 'Roles'
Click on 'any role that is created'
Add a policy
Click on Save

Expected results
The role should get save properly with the new permission.
Actual results
File "/opt/app-root/lib64/python3.11/site-packages/werkzeug/sansio/multipart.py", line 203, in next_event
raise RequestEntityTooLarge()
werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.
Additional context
By default the max decoded part what wrekzeug support is 1000. Since the size of the decoded part is more that 1000, it is throwing up the error.
https://forum.checkmk.com/t/request-entity-too-large-the-data-value-transmitted-exceeds-the-capacity-limit-web-log/40116
Superset Team: need a quick fix for this.

Do we need to increase max_form_parts for werkzeug? -- https://github.com/pallets/werkzeug/blob/817aac4d2c71b83752e451d23f96ac26cfd7bbcd/src/werkzeug/wrappers/request.py#L94
And how to achieve it?

I edit role directly in database
insert into ab_permission_view_role (id, permission_view_id, role_id)
values ('<id>', '<permission_view_id>', '<role_id>')

Where:

 is a primary key
<permission_view_id> is a id from public.ab_permission_view. You need to lookup for necessary pair of permission_id and view_menu_id, for example permission_id = 121, where 121 == can_execute_sql_query and view_menu_id = 4448, where 4448 == SQLLab
<role_id> is a Role id in superset, you can view them from roles pages in url or in ab_role table

For me, this was happening because we had too many users, but the number of permissions the role had was small. We patched our Superset changing this line
RoleModelView.edit_columns = ["name", "permissions", "user"]

to
RoleModelView.edit_columns = ["name", "permissions"]

Disables editing users in the List Roles page but let us edit the permissions again


Add crio mirror command to testrunner

Adds a command to copy a modified registries.conf to k8s
workers in order to point to our local docker image mirror.
Triggered by DOCKERHUB_MIRROR env var, if empty it will skip
doing anything.
This is done to avoid hitting the newly enacted DockerHub rate limits
of pulling images which we are hitting daily on CI jobs
Prerequisite to https://github.com/SUSE/caasp-automation/pull/807
Reminder: Add the "fixes bsc#XXXX" to the title of the commit so that it will
appear in the changelog.
What does this PR do?
please include a brief "management" technical overview (details are in the code)
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:

link to other PRs that should be merged together
link to packages that should be released together
upstream issues

Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

Not needed! Thanks @davidcassany !!


Added RPC method to query exchange rate

Added RPC method to query exchange rate for a given CurrencyID.
The new method for the oracle pallet, oracle_getExchangeRate, will return an UnsignedFixedPoint which is the type of the exchange rate and is needed to represent the exact value.
Issue #383.

I will leave this open until we can connect to stellar testnet for integration test just to be sure. Is that okay @ebma ?

CI passed so let's get this merged 👍


[BUG] external ui-source breaks v1.1.1 Harvester

Describe the bug

When you select external ui-source for Harvester v1.1.1 it breaks the UI
To Reproduce
Steps to reproduce the behavior:

Deploy v1.1.1 harvester
set ui-source to external
refresh page
Expected behavior

UI should come back up on refresh
Support bundle

There's not really asupport bundle since it's a UI issue and if you trigger it then you can't load the UI.
Environment

Harvester ISO version: v1.1.1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): single node virtualized libvirt

Additional context
Add any other context about the problem here.
v1.1.1 harvester is pointing at v1.1-head assets instead of a pinned v1.1.1 version. This means that if you select the external ui-source it breaks the ui.

Hi, @noahgildersleeve. Sorry for I can not reproducing this issue. Could you provide a video to let me investigate further?

we should probably be pointing to a separate v1.1.1 set of assets on v1.1.1

For the external UI, we want the user to have access to the latest UI, so the default value of ui-index points to the latest UI.
If the user wants to use the version-specific UI, can select the bundle option.

I think this might have been resolved with some of the RC3 fixes. I'll test and verify.

Tested in v1.1.1 and it seems to be working now. Closing as fixed.


IB Designables errors via storyboard

Hi, thank you for sharing this nice animation button, i really like it!
I manually installed the library and followed the instructions for storyboard setup and it works but it also gives me two red errors that I'm going to report:

IB Designables: Failed to update auto layout status: Interface Builder Cocoa Touch Tool crashed;
IB Designables: Failed to render instance of DOFavoriteButton: Rendering the view took longer than 200 ms. Your drawing code may suffer from slow performance.

Am I making any mistakes?
Kind regards
Alessandro

Thank you for informing me.
I fixed this issue.
Please check.

Thank you for your kind help, I'm really enthusiast about your animation.
After the update, i tried with the manual installation and I wasn't lucky, so I went with pod and at the beginning the same error appeared.
What worked for me was deleting old outlets and make a new ones: from the identity inspector I saw the "module" field auto filled like the image.
I apologize in case i was the reason of error ;-)

I'm sorry. I made a mistake.
Please confirm that again.

Hi,
I made a new project to give you a feedback as the last version you've posted worked as I mentioned.
Starting from an empty view controller, I dragged a button, changed the class, created the outlet and added the action following your instructions.
This time the Module filed remains empty but after the launch, the app crash with these errors:
dyld: Library not loaded: @rpath/libswiftCore.dylib
Reason: image not found
PS: I used your icons, so I'm quite sure that they are in ;-)
PPS: From my experience, the previous version was perfect and I'm continuing using it so I can just thank you and stay with it


Add a --dry-run option to tx sign

Once we add the tx sign command I think we should add a --dry-run option to it that doesn't actually sign or output a tx, but just lists what will and won't be signed.
For example for a simple tx it'll just show the tx being signed.
For a transaction with one or more auths it'd show which auths will be signed and which won't.
This could be really helpful for users of hardware signers or other devices in understanding what they'll be signing without needing to actually go and sign. It could become a good way to understand if the tx is doing something it shouldn't be.
I think we'll have other ways to introspect a tx as well, but this would be focused on auths and the entities to be signed.
Another way of approaching this instead of a --dry-run option would be to make an auths command, such as tx auths that provides capabilities specific to auths.
cc @janewang @willemneal

Created task for adding tx auths command #1493


[Gekidou] Show alert message when server is unsupported

Summary
Set the ESR version to 7.1.0 and displays an alert for Admins and End users about the need to upgrade the server without blocking usage of the app, kept the same forced version as the mobile app v1 to be servers below 5.25.0
Important: During development there was an assumption that it needed to support servers starting from 6.3.0, so it is imperative that we test on severs from 5.25 to 6.3 to identify if there is something broken and decide if we bump 5.25 to be 6.3 or if we try at least to support 5.37 which was an ESR at the time.
The ESR check happens in the following conditions:

When only one server is connected the check happens on every cold start from the app icon
When multiple servers, the check happens on server switch with a cooldown of 24 hours.

Ticket Link
https://mattermost.atlassian.net/browse/MM-42567
NONE

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/26117
https://circleci.com/gh/mattermost/mattermost-mobile/26116

Artifact links:
https://output.circle-artifacts.com/output/job/9aa33a76-ef60-491c-adbd-310b81ac5362/artifacts/0/tmp/artifacts/Mattermost_Beta.apk
https://output.circle-artifacts.com/output/job/7337feec-80b7-4a56-875e-47f3dcd01342/artifacts/0/tmp/artifacts/Mattermost_Beta.ipa

@jgilliam17 wont merge until we have the version that forces the update..


push 11/23:5

Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:bug: Bug fix or new feature
:memo: Documentation Fix
:book: New/Updated Documentation Content

update package.json, please

rm /.eslintrc.js


fix: bridge_ip method does not exist

container_bridge_ip should be used.
NameError:
  undefined local variable or method `bridge_ip' for an instance of Testcontainers::RedisContainer
# /usr/local/bundle/gems/testcontainers-core-0.2.0/lib/testcontainers/docker_container.rb:703:in `host'

@guilleiguaran could you please take a look 🙏


Concurrency: what measures does Rust take for ensuring secure concurrency? (big question - break this down!)

https://cwe.mitre.org/data/definitions/609	Double-Checked Locking
https://cwe.mitre.org/data/definitions/663	Use of a Non-reentrant Function in a Concurrent Context
https://cwe.mitre.org/data/definitions/820	Missing Synchronization
https://cwe.mitre.org/data/definitions/833	Deadlock
https://cwe.mitre.org/data/definitions/1058	Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
https://cwe.mitre.org/data/definitions/1223	Race Condition for Write-Once Attributes

Regarding deadlock, neither the language nor the standard library prevents deadlock.  The strong type system and ownership does allow abstractions of locks that could prevent deadlock (at the expense of some expressiveness) or could enforce a particular deadlock detection (at the expense of some performance), though both would require opt-in to use those abstractions and forgo using the deadlock possible std library locks.

Safe Rust does prevent Missing Synchronization; that's Rust's "Fearless Concurrency" guarantee (https://doc.rust-lang.org/book/ch16-03-shared-state.html).  However, that only guarantees that are no (low-level, memory) race conditions; one does still need to be aware of higher-level, logical race conditions (e.g., fine-grained locks on a hash table will prevent dangling pointers, but don't automatically guarantee the atomicity of application-level logic, like a "move" operation that removes a key/value pair and re-inserts under a different key).
On the other hand, the CWE example of "Missing Synchronization" has to do with insufficient locking on stdout when a parent process forks a child process, for which Rust would not necessarily help.  (It may be that the std library does better in that regard, e.g., with buffering, but it's a property of the implementation of the standard library, not the language.)


⚠ Bofrost.de has degraded performance

In f716b30, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1206 ms

Resolved: Bofrost.de performance has improved in db36dd1 after 6 minutes.


Include all @ApiObjects under configured packages in documentation (AbstractSpringJSONDocScanner)

SpringJSONDocScanners should include all objects annotated with @ApiObject under the configured packages opposed to only including return types, request bodies and their fields (one level deep).
Currently AbstractSpringJSONDocScanner.jsondocObject(List packages) considers methods annotated with @RequestMapping, it includes their return types and @RequestBody types as candidates. The fields of these candidates are then considered candidates as well. Of these candidates, only the candidates that are under the configured package are included in the docs.
In this case, you can have an @ApiObject in the configured packages that is not included in the resulting jsondocs.

A solution is to create a custom JSONDocScanner that extends Spring3JSONDocScanner (or Spring4*) and overrides the jsondocObjects methods:
`@Override
public Set<Class<?>> jsondocObjects(List packages) {
    Set<Class<?>> objects = Sets.newHashSet();
    Set<Class<?>> apiObjects = reflections.getTypesAnnotatedWith(ApiObject.class);

    for (Class apiObject : apiObjects) {
        if(apiObject.getPackage() != null) {
            for (String pkg : packages) {
                if(apiObject.getPackage().getName().contains(pkg)) {
                    objects.add(apiObject);
                }
            }
        }
    }

    return objects;
}`

I hope this helps someone.


Rosetta Dev Test for checkForValidSession-rewrite

@KatieWoe, please only have QA do this if there isn't anything else to do or if someone is bored with sim testing.
Instructions
Don't use the production website!

Head over to https://ox-dev.colorado.edu/translate.
Try logging in with all different kinds of accounts. Please try your personal PhET website account and the QA accounts in the credentials sheet. (You should only be able to log in if you're a PhET team member or a trusted translator.)
Make sure you don't see a 503 status code or any buggy behavior with logging in like the page reloading suddenly.
Dev test the translation utility. Just mess around with it and see what bugs you can find. (Your translations won't appear on Ox-Dev. I have that feature disabled.)
If anyone does any testing, please write what time you did your testing in a comment.

Thanks!

At 4:40 pm on 1/20/2021. Tested a bit on Win 10 Chrome. Upon logging in, two buttons are cut off and unreadable.

I'm fairly confident we're not seeing any issues from the rewrite. Closing.

I'm fairly confident we're not seeing any issues from the rewrite. Closing.


feat(updater): Add packages GC support for tracer packages

What does this PR do?
Adds a garbage collector to the updater to support tracer updates. As tracers are long running, we can't just delete the package version at the end of an experiment and we must track which applications still use that package version. Once no process uses it, it can be removed from the host.
The GC runs periodically (every hour) & at each operation from the updater.
Motivation
RC-1517
Additional Notes
To keep the existing behaviour for agents, there is a new flag -w to watch processes using that package. Additionally, this PR makes the paths configurable from the CLI.
Possible Drawbacks / Trade-offs
N/A
Describe how to test/QA your changes

Create the /var/run/datadog-packages and give it 777 permissions (easier to test)
Bootstrap the updater with go run cmd/updater/main.go bootstrap -p go if not already done
Run the updater with go run cmd/updater/main.go run -p go
Start an experiment: curl -X POST -v --unix-socket /opt/datadog-packages/go-updater.sock -H 'Content-Type: application/json' http://agent/experiment/start -d '{"version":"1.21.5"}'
Find a running process that you can kill (watch ls & for instance will give you the PID)
Create a file with the PID in the run directory (this'll be done by the injector in the future): mkdir -p /var/run/datadog-packages/go/1.21.5 && touch $_/<PID>
Try to delete the experiment: curl -X POST -v --unix-socket /opt/datadog-packages/go-updater.sock -H 'Content-Type: application/json' http://agent/experiment/stop -d '{"version":"1.21.5"}'
Check the contents of both /var/run/datadog-packages/go & /opt/datadog-packages/go, note that while the experiment symlink is gone the package still exists
Kill your process and run step 7: the package is now gone.

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


Fix udp issue

step-security/harden-runner#112

@h0x0er I already made the change few minutes back. Was in hurry to release it. Sorry did not communicate about it.

@varunsh-coder alright.


Linux version of the patch?

Hi, will there ever be a linux version of the patcher? I used it on windows and it worked flawlessly, but have since switched to arch linux and don't know if it's a good idea to use the patcher as-is, considering linux and windows use different filesystems and libraries.
Any chance it'll be worked on in the future?

Hey,
Since the original release of Settlers 6 and the history editions are Windows only, i don't think it would make much sense to release a Linux build. I have no plans regarding this right now, i'm sorry.
However, since the functionality of the Patcher is very simple, and it's based on .Net Framework 2.0, you should be able to run it using e.g. Mono and it should work fine.
Basically, the latest release of the Patcher modifies a few bytes the game executable and it creates two files in the Documents folder of Settlers 6 (where usermaps are also located). If those changes are made, it worked. I never tried it under Linux, so you would have to try.
If Mono doesn't work, you could also patch your game installation in an windows environment (e.g. by using a virtual machine or another computer) and copy the modified files to your Linux machine.
Regards,
Eisenmonoxid


[Question] Dealing With Multiple Sequential Functions - asyncio.gather

Given some sequential functions:
    task_1 = search(x)
    task_2 = extraction(task_1)

Given n users (A,B,...,n)
How can I keep  async so that if n users will make the API call at the same time, the app will process the requests at the same time parallely?
    User A      User B
     task_1      task_1
     task_2      task_2

Here's the code I'm using and it is returning me an error:
    app = FastAPI()
    @app.post("test")
    async def extract_text(image: UploadFile = File(...)):

    function = [search(x), extraction(task_1)]
    a,b = await asyncio.gather(*functions)
    return {a,b}

concurrency x parallelism x asyncio


orical Fairy Tales Animal Stories Short Stories Poetry & Drama Classic Inspirational Poetry Regional Love & Romance Modern Drama Mystery & Thrillers Legal Spy Historical Horror War & Battle Detective Crime & Suspense Humor Anectodes Political Social & Relationships History Military World Ancient Revolutionary Genocide Religion Recent Centuries Romance Regional Historical Religion & Spirituality Christianity History Kids & Teens Elementary Toddler Pre-school Teens Professional Psychology Philosophy Science Lifestyle Social Values House Development Self Development Nature" label="Biography & Memoir Professional Political Figures Women Personal Memoirs Historical Religious Artists Fiction Action & Adventure Fantasy & Myths Regional Religious Classics Lifestyles & Social Historical Fairy Tales Animal Stories Short Stories Poetry & Drama Classic Inspirational Poetry Regional Love & Romance Modern Drama Mystery & Thrillers Legal Spy Historical Horror War & Battle Detective Crime & Suspense Humor Anectodes Political Social & Relationships History Military World Ancient Revolutionary Genocide Religion Recent Centuries Romance Regional Historical Religion & Spirituality Christianity History Kids & Teens Elementary Toddler Pre-school Teens Professional Psychology Philosophy Science Lifestyle Social Values House Development Self Development Nature">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="112" width="319" height="38" name="Biography & Memoir Professional Political Figures Women Personal Memoirs Historical Religious Artists" label="Biography & Memoir Professional Political Figures Women Personal Memoirs Historical Religious Artists">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="112" width="319" height="38" name="Biography & Memoir" label="Biography & Memoir">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="150" width="319" height="38" name="Fiction Action & Adventure Fantasy & Myths Regional Religious Classics Lifestyles & Social Historical Fairy Tales Animal Stories Short Stories" label="Fiction Action & Adventure Fantasy & Myths Regional Religious Classics Lifestyles & Social Historical Fairy Tales Animal Stories Short Stories">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="150" width="319" height="38" name="Fiction" label="Fiction">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="188" width="319" height="38" name="Poetry & Drama Classic Inspirational Poetry Regional Love & Romance Modern Drama" label="Poetry & Drama Classic Inspirational Poetry Regional Love & Romance Modern Drama">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="188" width="319" height="38" name="Poetry & Drama" label="Poetry & Drama">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="226" width="319" height="38" name="Mystery & Thrillers Legal Spy Historical Horror War & Battle Detective Crime & Suspense" label="Mystery & Thrillers Legal Spy Historical Horror War & Battle Detective Crime & Suspense">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="226" width="319" height="38" name="Mystery & Thrillers" label="Mystery & Thrillers">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="264" width="319" height="38" name="Humor Anectodes Political Social & Relationships" label="Humor Anectodes Political Social & Relationships">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="264" width="319" height="38" name="Humor" label="Humor">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="302" width="319" height="38" name="History Military World Ancient Revolutionary Genocide Religion Recent Centuries" label="History Military World Ancient Revolutionary Genocide Religion Recent Centuries">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="302" width="319" height="38" name="History" label="History">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="340" width="319" height="38" name="Romance Regional Historical" label="Romance Regional Historical">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="340" width="319" height="38" name="Romance" label="Romance">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="378" width="319" height="38" name="Religion & Spirituality Christianity History" label="Religion & Spirituality Christianity History">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="378" width="319" height="38" name="Religion & Spirituality" label="Religion & Spirituality">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="416" width="319" height="38" name="Kids & Teens Elementary Toddler Pre-school Teens" label="Kids & Teens Elementary Toddler Pre-school Teens">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="416" width="319" height="38" name="Kids & Teens" label="Kids & Teens">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="454" width="319" height="38" name="Professional Psychology Philosophy Science" label="Professional Psychology Philosophy Science">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="454" width="319" height="38" name="Professional" label="Professional">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="492" width="319" height="38" name="Lifestyle Social Values House Development Self Development Nature" label="Lifestyle Social Values House Development Self Development Nature">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="492" width="319" height="38" name="Lifestyle" label="Lifestyle">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="false" x="342" y="112" width="30" height="501" name="Vertical scroll bar, 1 page" label="Vertical scroll bar, 1 page" value="0%">                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="false" x="0" y="580" width="375" height="30" name="Horizontal scroll bar, 1 page" label="Horizontal scroll bar, 1 page" value="0%">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeScrollView>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="302" y="540" width="60" height="60">                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="0" y="613" width="375" height="54" name="Home Search My list Settings" label="Home Search My list Settings">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="0" y="613" width="375" height="54" name="Home Search My list Settings" label="Home Search My list Settings">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="28" y="623" width="80" height="34" name="Home" label="Home">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="56" y="623" width="24" height="24">                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeStaticText type="XCUIElementTypeStaticText" enabled="true" visible="true" x="56" y="646" width="24" height="12" name="Home" label="Home" value="Home">                                                                                </XCUIElementTypeStaticText>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="108" y="623" width="80" height="34" name="Search" label="Search">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="136" y="623" width="24" height="24">                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeStaticText type="XCUIElementTypeStaticText" enabled="true" visible="true" x="134" y="646" width="28" height="12" name="Search" label="Search" value="Search">                                                                                </XCUIElementTypeStaticText>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="187" y="623" width="81" height="34" name="My list" label="My list">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="216" y="623" width="23" height="24" name="navBarMyList">                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeStaticText type="XCUIElementTypeStaticText" enabled="true" visible="true" x="214" y="646" width="27" height="12" name="My list" label="My list" value="My list">                                                                                </XCUIElementTypeStaticText>                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="267" y="623" width="80" height="34" name="Settings" label="Settings">                                                                                <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="true" x="296" y="623" width="23" height="24" name="navBarSettings">                                                                                </XCUIElementTypeOther>                                                                                <XCUIElementTypeStaticText type="XCUIElementTypeStaticText" enabled="true" visible="true" x="290" y="646" width="34" height="12" name="Settings" label="Settings" value="Settings">                                                                                </XCUIElementTypeStaticText>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                                </XCUIElementTypeOther>                                                                             </XCUIElementTypeOther>                                                                         </XCUIElementTypeOther>                                                                     </XCUIElementTypeOther>                                                                 </XCUIElementTypeOther>                                                             </XCUIElementTypeOther>                                                         </XCUIElementTypeOther>                                                     </XCUIElementTypeOther>                                                 </XCUIElementTypeOther>                                             </XCUIElementTypeOther>                                         </XCUIElementTypeOther>                                     </XCUIElementTypeOther>                                 </XCUIElementTypeOther>                             </XCUIElementTypeOther>                         </XCUIElementTypeOther>                     </XCUIElementTypeOther>                 </XCUIElementTypeOther>             </XCUIElementTypeOther>         </XCUIElementTypeWindow>         <XCUIElementTypeWindow type="XCUIElementTypeWindow" enabled="true" visible="false" x="0" y="0" width="375" height="667">             <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="false" x="0" y="0" width="375" height="667">                 <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="false" x="0" y="0" width="375" height="667">                 </XCUIElementTypeOther>                 <XCUIElementTypeOther type="XCUIElementTypeOther" enabled="true" visible="false" x="0" y="667" width="375" height="216">                 </XCUIElementTypeOther>             </XCUIElementTypeOther>         </XCUIElementTypeWindow>     </XCUIElementTypeApplication> </AppiumAUT>


Update Logo and add Financial Token Sector

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

It looks like it is not possible to update logo of a token once we publish it.  I have to find how to do it. For now, I will close my PR


Issues with installation android

Looking forward to using this library, however I keep getting errors whenever I'm trying to install it for Android - any solutions? I see it's quite common in the issues threads.

Hey @jamesvovos  If you're encountering issues with the original version, I'd like to invite you to try my fork of React Native Mapbox Navigation. I've made some enhancements and fixes that might address your concerns. You can easily install it using npm with the following command:
npm install https://github.com/sarafhbk/react-native-mapbox-navigation
I'm eager to hear your feedback and improve it further, so please don't hesitate to share your thoughts and experiences!

Hey @sarafhbk  I am using your forked version but on android its not starting navigation guide only opening map can you suggest me anything or help me resolve this issue ? I have been on this for weeks now.


Add failure/success helpers to either.ts

Changes
Added several helpers to Either functionality for ease and clarity of use:

isFailure(value) unwraps the Either value and tells if it has an error
isSuccess(value) unwraps the Either value and tells if it has a result
failure(error) wraps error into an Either
success(result) wraps result into an Either

Checklist

[x] Apply one of following labels; major, minor, patch or skip-release
[x] I've updated the documentation, or no changes were necessary
[x] I've updated the tests, or no changes were necessary

@drdaemos There is an issue with vite, I am fixing it on -> https://github.com/lokalise/node-core/pull/80


feat(trusted claim issuers): support DID strings as well as Identity

Methods that modify Default Trusted Claim Issuers now also accept DIDs to represent the Claim
Issuer. Also fixed a bug in TrustedClaimIssuers.get

:tada: This PR is included in version 3.0.0-alpha.5 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add some fuzz tests

Codecov Report
Attention: Patch coverage is 61.29032% with 24 lines in your changes missing coverage. Please review.

Project coverage is 80.48%. Comparing base (c46c203) to head (f523a96).

Files
Patch %
Lines

io.go
7.69%
10 Missing and 2 partials :warning:

imagemeta.go
71.42%
3 Missing and 3 partials :warning:

imagedecoder_webp.go
69.23%
3 Missing and 1 partial :warning:

helpers.go
66.66%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   80.84%   80.48%   -0.36%
==========================================
  Files          14       14
  Lines        1164     1199      +35
==========================================
+ Hits          941      965      +24
- Misses        150      161      +11
  Partials       73       73

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


Project leak in attributes provider

Storing project component inside of the extension point is causing project leak:
https://github.com/henjue/vue-for-idea/blob/master/src/main/java/io/j99/idea/vue/component/VueAttributeDescriptorProvider.java#L12.

I think this field is not needed, it can be replaced with local variable declaration.

The future will be rewritten. This plugin is currently used for learning

I find it weird to close the issue that is still present. It's just a matter of deleting 4 lines of code, do you need PR for that?

I don't care about it at the present, for me it is more about learning how to develop plug-ins, and the second is to do it well.


Reintroduce the download file fallback.

If I remember correctly, if it couldn't play the file, it would have created a download link.
I'm assuming it was removed for a reason, if so, it was probably a good one.
I have a workaround, if people need one.
Just create a download renderer, load it last, and return true for canPlayType.
Then the create function will be called, and you can basically just take over the entire renderer at that point.
It's not version stable, as the moment some key structures change, it'll just error.
I'll post the code, if people want as well.

Yes, please. If you wanna submit a PR for this, I'll be happy to review it. Thanks for pointing this

Chrome's default player now has a download button when you are playing a video
Just saying...

playing a video

Not if the fallback for flash, or something kicks in.
And assuming they're using chrome.
And the download button doesn't always show up.

This one was in the old version but given the new approach we took this weapon carry it over so I need to check if we really need a renderer or just a piece of code

It would be a lot easier with just some code inlined, instead of a renderer.
If the download was a renderer, there's some workarounds within that you have to do as well, as the renderer is expected to have a number of functions implemented on the returned value from create.

I'll work on this tonight in the mejs-standalone branch, and I'll let you know when it's ready so you can test it. This branch will become the 4.0 version of this player soon

@Jezza Can you give me a URL that can cannot be played so I can test this, please?

@Jezza I tried a test case using a dummy MIME type to check this. If you download the mejs-standalone branch and test it, please let me know if it works for you. Thanks

Sorry, was asleep.
Basically, to get it to fail, you just add any type that mejs doesn't support.
In our case, it was just a mov.
I'll give it a shot, and report back.

Perfect. Keep me posted please

Don't forget that this fix is on the mejs-standalone branch. Any updates on this?

Yeah, sorry.
We had a slight emergency at work, and ended up sending most of the day working with that.
Sorry about that.
Had a glance at the code, and it seems fine.
The only functional difference between my download renderer and the replacement code, is my code offers a link for each of the sources.
So, if you had an mp4, and an avi, it'll link both of them with their names as the text, and the mimetype as the title.
Download:
source.mp4
source.avi

If you want to go down that road, that would be great, if not, I'd still be willing to test the code on Monday, and give any more feedback, but I'd probably still have to use the renderer, so by no means do I expect you do implement the renderer's functionality.

Yeah if you can test this on Monday I'd appreciate it. I don't think it will be difficult to provide links for each element so let me explore that and I'll keep you posted

Maybe the Mime type won't be that important given that it is spelled in the URL for each source. Is there a reason why that could be useful?

I mean, practically, no.
The only reason it's even there, was for testing purposes, and I just forgot to remove it.
So, yeah, if you ditch that part of it, that's perfectly reasonable.
I only mentioned it because I had some of the html on hand, and felt an obligation to explain why it was there. :)
But yeah, it's not necessary at all.

OK I think I have it ready. Download the latest version of mejs-standalone branch and test it on Monday, please and let me know

Should I close this ticket? This will be part of the 4.x version and it will be released soon

Oh, I didn't submit it.
I'm at home now but the original comment was:
Yeah, works as expected, not having any issues with it, so I can remove my workaround.
Many thanks, I very much appreciate the work.

You are welcome. Glad it worked


Add-on to introduction of README

I have made an addition in clear, easy-to-understand language to the introduction. I believe my add-on makes the introduction even more comprehensive, while being free of complex technical terms. Seasoned developers, new programmers, and even nontechnical visitors will benefit from the clear language, exposing Peek to a broader range of users.

@rulep thank you for taking the time to open this PR and revise the README, I'm going to leave what is in the current README as I believe it succinctly explains the purpose of peek and how to use/extend it. I have a preference for shorter a README over a verbose README when possible.


Adding typespec base package reference for liftr

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

@mikeharder PFB the response

Source code is part of Liftr ADO repo https://dev.azure.com/msazure/Liftr/_git/LiftrBaseApiSpec?path=/packages/typespec-liftr-base/lib/main.tsp
Versioning is not followed as per other typespec packages. as This will only be used by LIftr team
Version will be updated by Liftr team.
Liftr will take care of breaking changes.

This package contains some standard typespec models used in Liftr related RPs. Instead of our teams adding those models in different RP's typespec, we are using this package. for e.g. you can see currently these models are copied as part of each rp https://github.com/Azure/azure-rest-api-specs/tree/main/specification/liftrastronomer

Source code is part of Liftr ADO repo https://dev.azure.com/msazure/Liftr/_git/LiftrBaseApiSpec?path=/packages/typespec-liftr-base/lib/main.tsp

Can some members of the Azure SDK team be given read access to this repo?  When I try to browse to https://dev.azure.com/msazure/Liftr I get a 404 (which I assume means I don't have permissions).

Version will be updated by Liftr team.  Liftr will take care of breaking changes.

I encourage you to proactively work with the TypeSpec team, to coordinate with their montly releases.  For example, TypeSpec might make a breaking change, which you will need to react to in typespec-liftr-base, and publish a new version very shortly after TypeSpec publishes.  You will also likely want to run all your tests against both the current version and the "next" version of TypeSpec, to detect breaking changes that impact you as soon as possible.
To summarize, the Liftr team is responsible for reacting to two types of breaking changes:

TypeSpec makes a breaking change, typespec-liftr-base needs to react
typespec-liftr-base makes a breaking change, all specs using typespec-liftr-base need to react

For updating specs, the current process is everything in public/main must be updated by the team who made the breaking change to the tool (Azure SDK or Liftr).  The process for RPSaaSMaster is different, where spec authors are expected to update their spec in their next PR.

@mikeharder Yes, we are working with Typespec team and @allenjzhang is aware about the changes. Our typespec files are versioned.
For access, let me check with my team, how can i provide the access to sdk team.

@mikeharder, I have went over the maintenance plan with Liftr team. Signing off from my side.
The Liftr team will be pulled in by the EngSys/TypeSpec team if any breaking changes are needed due to TypeSpec releases. The Liftr team needs to make expedited fixes and publish updates promptly.
If the Liftr team is making or introducing breaking changes in the Liftr library, these changes will be tested beforehand before upgrading the Liftr package versions in the rest-api-spec repository.


Direct resolve and claim_search requests to a separate SDK instance

Worth to keep #174 in mind

This may not be possible if/once we start using claim search/resolve along with wallet_id. This would be used to show purchase receipts or having awareness of your own claims in those calls. There are workaround like passing the claim ids to txolist / claim list instead.

We should temporarily put this on hold.

Not needed anymore as resolves and claim search can accept wallet_id now.


Cannot create new token with Refresh Token button.

The page: https://codetime.datreks.com/account
Picture
There is no token. When I click Refresh Token, nothing happen.
Open developer tool and check Network, I see:
GET https://codetime-api.datreks.com/updateToken
Response:
{"code":-1,"message":"invalid token/token expired"}

How did you even registered?

@awesomelewis2007 @ttpro1995 @MrMasrozYTLIVE fixed! Sorry, I have been too busy recently. The problem is caused by too much data. We will expand the storage space in the future.


Some small Publishing API fixes

This fixes a few small issues I found with Publishing API when I was writing the code https://github.com/alphagov/gds-api-adapters/pull/974. More details in the commits.

@leenagupte I've amended


[release-4.15] USHIFT-2208: add periodic test scenario for the standard tests on rpm-based system

Manual backport of #2850

/lgtm

Updated to include part of https://github.com/openshift/microshift/pull/2746 from @eggfoobar

We will need to backport #2918 before we can merge this change.

The ARM job failed with an unrelated issue in the storage snapshot test<EMAIL_ADDRESS>

/override ci/prow/microshift-metal-tests-arm
/label backport-risk-assessed

/label  jira/valid-bug
/lgtm

/label jira/valid-bug

/label cherry-pick-approved

hi @pacevedom I'd like to get this PR merged. Also created another PR to merge this changes into release-4-14 branch: https://github.com/openshift/microshift/pull/3039

/label staff-eng-approved
@agullon I've added the missing label. I'll leave it up to you and @pacevedom to remove it when you're comfortable landing a CI change.

/hold cancel


Setup husky for frontend and backend

This is to save some time reviewing the code and then changing the linting errors. Which will be done by locally automating this process before committing the code.
Husky Package

Can I work on this under LGMSOC'21. Also, I just have to set up the husky package, or do I have to automate the changing of linting errors process too?

Sure, one of the steps in the husky pre commit could be npm run lint --fix to auto fix the lint errors. But now that I think about it, it might be a good exprience to auto correct without the developer knowing it. So just linting should be fine. Let me know if you have any questions. Assigning this to you :)

Yes, I am on it...one question though, I will have to install and set up eslint too in both the directories?

The backend is not configured with eslint, if you could do that as well, that would be awesome!

Hey @avinashupadhya99, I just wanted to ask why the readme doesn't show my pic in the contributors' section?
Also, it was my first PR, thank you for guiding me through🙌

Hey @Diksha02 , well done! 🎉 Thank you for setting it up. Your picture should show up in a while as it usually takes around 24h for it to update.


Improving Voice Model Dominance Over TTS Voice in Applio

First of all, thank you for the amazing work on Applio—it's a fantastic tool! I'm currently working on generating audio files using a TTS voice and then applying a voice model to mimic a specific person. However, the final audio still sounds more like the original TTS voice rather than the intended voice model. Do you have any recommendations for making the voice model more prominent in the output? Any tips on fine-tuning or balancing the two would be greatly appreciated!

this has been discussed in many issues, this tool is not intended for TTS, the results with TTS are certainly limited so if your intention is to use only TTS you may want to look at other alternatives.
You can use the elevenlabs plugin for applio or try with different voices in the TTS.


Bulbs not found for Homebridge

I installed v2.0.5.
Running Homebridge 1.1.1 (Node.js version 12.15.0) and I can't add my two Wiz bulbs to Homekit via this plugin. My config has this:
        {             "platform": "WizSmarthome",             "name": "WizSmarthome"         },

I don’t think I was able to find them until I had first set them up in the Wiz app. Not sure if you have tried that?

Agreed with @mitch7391, unfortunately I'm not quite sure how to troubleshoot this without more details. Are the bulbs all in the same subnet (and discoverable through UDP broadcast?)

@kpsuperplane I'm having a similar issue. Details:

Initial config of homebridge-wiz-lan worked well and bulbs could be controlled fine ( posted a demo even! https://twitter.com/ethanschoonover/status/1295200829394231297?s=20 )

Today I restarted Homebridge for system maintenance and the lights stopped working via this plugin

Testing via CLI works fine. E.g.:

echo '{"method":"setPilot","env":"pro","params":{"mac":"FF:BB:29:D3:89:EE","src":"udp","state":true,"temp":2869,"dimming":100}}' | nc -u <IP_ADDRESS> 38899

Testing via Wiz app works fine

I uninstalled the homebridge-wiz-lan plugin and removed the plugin section from the config in Homebridge. Additionally I cleared cached accessories.

After a Homebridge restart I re-added the plugin and it does not scan or detect any accessories.

Other plugins (e.g. Nest) in Homebridge continue to function properly.

If there is anything else I can test or try, I'd be happy to. Thanks! Loved the plugin when it was working!

Hey @kpsuperplane I just installed this plugin with a bulb on the same network as my Pi, and it doesn't seem to pickup my RGB bulb. Is there a command I can use to ping it for the plugin to pickup?
I am able to control it locally and see it on my Wi-Fi network.

@kpsuperplane All my bulbs are in a separate vlan (<IP_ADDRESS>) and my HB server is multi-honed (<IP_ADDRESS> and <IP_ADDRESS>) and it's also not picking up any bulbs. I can see the discovery going out through debug, but nothing ever comes back to the HB server.
Any ideas?

Hey everyone,
Unfortunately I don't know what might be causing your issues. I also don't have any bulbs anymore to debug with as I've transitioned my home to the Hue ecosystem.
My best suggestion is to look into setting up homeassistant instead; they have an actively supported wiz implementation https://github.com/sbidy/wiz_light

Unfortunately I don't know what might be causing your issues. I also don't have any bulbs anymore to debug with as I've transitioned my home to the Hue ecosystem.

LOL, I went the opposite direction: Hue > Wiz.

My best suggestion is to look into setting up homeassistant instead; they have an actively supported wiz implementation https://github.com/sbidy/wiz_light

I'm currently using that and it's actually really well done. I wanted to have my bulbs (40+ of them) in both HB and HA. The main reason is that with iOS14, Homekit seems to have some issues with HA's HomeKit bridge.
Thanks for chiming in @kpsuperplane. Much appreciated.

@code-in-progress slightly off topic here, but given you have so many wiz bulbs. Do you have any issues with them emitting high frequency noises (quiet little beeps and chirps)? Iv taken two back due to the issue and now one that didn’t do it is starting to. It’s actually making want to move away from wiz; however, I really love the design of their large filament style bulbs.

 I've since fixed it and 2 of my RBG bulbs work great in HomeKit. Thanks for the plugin!

@code-in-progress slightly off topic here, but given you have so many wiz bulbs. Do you have any issues with them emitting high frequency noises (quiet little beeps and chirps)? Iv taken two back due to the issue and now one that didn’t do it is starting to. It’s actually making want to move away from wiz; however, I really love the design of their large filament style bulbs.

Yeah, the filament bulbs tend to do that. The color bulbs (which I have the most of), don't, but if you have a LOT of broadcast UDP traffic, commands sometimes seem to just vanish into thin air. The other thing I've noticed is that the new A21 bulbs (https://www.homedepot.com/p/Philips-Color-and-Tunable-White-A21-LED-100-Watt-Equivalent-Dimmable-Smart-Wi-Fi-Wiz-Connected-Wireless-LED-Light-Bulb-562405/313643239) seem to die a lot. Might just have been a bad batch, but I got 5 of them and 2 of them have died in the past week. :(

Thanks for the update :) I will have to keep an eye on the filament bulbs then. Wiring hopefully wouldn’t be an issue as they were newly wired bedside pendant lights that I put these straight into (also the house is only 4 years old). The high pitch noise is so noticeable for me as it’s right next to me at night when everything else is quiet haha...

The high pitch noise is so noticeable for me as it’s right next to me at night when everything else is quiet haha...

Are these in some sort of a dimmer or on a circuit with a dimmer type switch? That's the only other thing I can think of that would cause that (especially since you already replaced the bulbs). Does it happen in the same fixture or on the same circuit?
I would be ripping my hair out if it was that noticeable, so I can only imagine what it's doing to you. lol

No dimmer switch, just a regular switch; the idea was that I knew I was going to have a smart bulb of some kind and that would handle the dimming. I might try another brand of bulb (I have some regular Hue laying around) to see if that happens, but I do know the one of my missus's side is not doing it and mine has done it twice (replacement didn't at first and does now when on, but the original was doing it while on and off).
It took me a week to realise it wasn't crickets in the house that I could faintly hear somewhere lol and eventually realised it only started once I got the lights installed, then I put my ear up against the bulb and could hear it very loudly... So yes, I was going crazy haha...

Hi everyone, I had similar issue as above... Basically I installed Wiz plugin and the Light appeared in Homekit immediately and was working fine... But there was a "crack" in the light and seller sent me a replacement. After replacing the light, new one popped in my Homekit automatically and worked perfectly. But I wasn't sure how to remove the old one, as there was no option to remove it in Homekit app. Now I know that I have to remove it in Accessories section in Homebridge web page, but I didn't know that before... And I'm not sure exactly what I did, but both lights are gone now. I tried everything to bring it back, but no luck. I even deleted the Wiz app on my phone and completely re-installed whole Homebridge on my Synology NAS. But still no luck. Ring doorbell is working fine... The light works fine in Wiz app. It works in both Google and Alexa apps... The only place it doesn't work is Homebridge. It's making me crazy now :) If anyone can help, I'd really appreciate it. Thank you, Martin

Closing because v3.0.0+ should fix most issues, feel free to open another issue if you continue having problems :)


Limit size of the script by validation on server side

Express limits the size of the request to ~1MB by default: http://stackoverflow.com/questions/19917401/node-js-express-request-entity-too-large


support jsonb_build_array / jsonb_build_object

binder & expr support of VARIADIC any is poor

Requested by a community user

@KeXiangWang Since @xiangjinwu is busy with Kafka sink recently, can you please take this?

Ok, I'll take it.


Expand upon SignalR access token logging section

From #9424 discussions
Expanded a bit on how access token logging affects your app and what it means. Also, how to disable URL logging entirely in ASP.NET Core (this is a bit of a severe option, since it disables logging of ALL request URLs).
cc @Tratcher
Internal Review Link

:up: :date: Feedback addressed.

@Tratcher Please take another look.


Fix issues number 5 and 6 mainly

Build Component (Footer)
Build Header Component (Navigation)
Add Header Component (hero section)
Add development dependencies and configurations
Add Sass module

Kindly make the navigation bar responsive.

Responsive navigation added for smaller devices.

Kindly make the navigation bar responsive.

Completed a week ago.


php.suggest.basic list appears after closing any HTML tag in a PHP file

VSCode Version: 1.18
OS Version: Windows 10

When typing HTML into a PHP file, the php.suggest.basic list appears after closing each tag (presumably on the press of the > key).

The problem goes away if I set php.suggest.basic: false but it didn't do this with the previous version.
Steps to Reproduce:

Type HTML into a PHP file

Reproduces without extensions: Yes

Similar to https://github.com/atom/ide-php/issues/47 which is the start of a trail to https://github.com/Microsoft/language-server-protocol/issues/138

This was the cost of #26598, and needs Microsoft/language-server-protocol#138 to be fixed

Would checking for the - that precedes > in the completion provider solve this? If it does not exist then return an empty completion list.

Yeah, that would probably be a good workaround.

Implemented in https://github.com/felixfbecker/php-language-server/pull/527


Don't accumulate waveforms if no one is looking at them

Currently we collect a lot of waveform data in mod_pagespeed that has a non-trivial cost in memory & cpu.  However we don't even have a live admin-page tab to show them.  (at one point in the past we did, but it did not survive a refactor).
So we might as well not collect them until they are shown.

@jmarantz  Did https://github.com/pagespeed/mod_pagespeed/commit/53be049cf0f170ff4342d9dfb11974e65745d3ea fix this?

yes


Updating to latest netns to fix amd64 / RPI issues

Signed-off-by: Madhu Venugopal<EMAIL_ADDRESS>

LGTM

LGTM


feat(source): add ruleid to metadata

The code gets a bit ugly when trying to support meta(*) in this feature , maybe just support meta(ruleid) ? or any suggestion ? thanks

The code gets a bit ugly when trying to support meta(*) in this feature , maybe just support meta(ruleid) ? or any suggestion ? thanks

Good point. How about just create another function like rule_meta()

Sounds good. I already updated the code, and I think there is no other rule info we can get inside the built-in function , maybe  just call it rule_id() ?

Sounds good. I already updated the code, and I think there is no other rule info we can get inside the built-in function , maybe just call it rule_id() ?

Great. No problem. Let's wait for the checks. I may merge this after 1.9.0 release.


Add search multidimensional collection method

This method allows for searching in a multidimensional collection. Its arguments are the collection, the columnName on the collection that should be searched and whether or not the search should be in strict mode.
I used array_combine to assure that the original collection keys are preserved. While this may make the method somewhat fragile, as the number of items in the original collection must match the number of items found with the given key (columnName), I believe it's the only sane way to handle this. Otherwise the method would return the keys of the newly created array, i.e. array_column($this->items, $columnName), which, if the equality requirement mentioned above was not met, could have no meaning in the original collection.
I also realize that this could be one lined like below,
return array_search($value, array_combine(array_keys($this->items), array_column($this->items, $columnName)), $strict);

But, it's a lot easier to review and understand when it is broken into two parts, IMO.
In a recent project with a lot of collection work, I found myself reaching for this type of utility quite a few times.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Help: Include Saturday in Business Day?

Hi good day,
How can i include saturday in business day please? thanks

nvm.. i solved it now.. thanks


Add Kaggle competition result

We're currently processing your upload.  This comment will be updated when the results are available.


CORS error on web client

Preflight Checklist

[ ] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[ ] I am not looking for support or already pursued the available support channels without success.

OpenMeter Version
1.0.0-beta.29
Expected Behavior
I have simple next js with web integration in place. Im getting cors error for each query ?

Actual Behavior
Should be able hit server without cors error.
Steps To Reproduce
Deploy simple next js app with integration as suggested here
https://openmeter.io/blog/launchweek-1-day-4-consumer-portal#heading-how-can-openmeter-help
Additional Information
No response

Thank you for reporting @dhrn !
We will investigate and get back to you. It's likely a web server misconfiguration.

A fix has been rolled out; thanks for reporting, @dhrn!


Add support for Calico for Windows upgrades

Description
This PR adds a new controller to control the upgrade of Calico for Windows to the operator's supported enterprise version when the Linux nodes are upgraded to enterprise.
This PR works in conjunction with a new Windows node service that will help complete the upgrade.
Tests are coming shortly but the I think the PR is ready for some review as-is.

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

Also @lmm looks like tests are failing.


HotFix Initial State for sandbox contract

Fix initial state for sandbox bootstrap: https://github.com/tqtezos/minter/issues/279

Tested and this worked for me to allow sandbox to bootstrap

If the storage changed then the contract won’t work with minter ui at all. Not without other changes that we shouldn’t be randomly making right now. The real fix is to go back to the previous marketplace contract and put migrating to the newer version on the roadmap. Why was it suddenly changed in the first place?

If the storage changed then the contract won’t work with minter ui at all. Not without other changes that we shouldn’t be randomly making right now. The real fix is to go back to the previous marketplace contract and put migrating to the newer version on the roadmap. Why was it suddenly changed in the first place?

Not sure why the change was made, but here is where contract changes were made:

https://github.com/tqtezos/minter/pull/278
https://github.com/tqtezos/minter/pull/278/commits/654fb2ca80552587375c8a80f7fdf384be471406
https://github.com/tqtezos/minter/pull/278/commits/2f1a8acbd8d3d1ffd7aa2a89dc9006b05032ecbe

If the storage changed then the contract won’t work with minter ui at all. Not without other changes that we shouldn’t be randomly making right now. The real fix is to go back to the previous marketplace contract and put migrating to the newer version on the roadmap. Why was it suddenly changed in the first place?

Not sure why the change was made, but here is where contract changes were made:

#278
654fb2c
2f1a8ac

The newer version adds admin functionality. We’re not quite ready to implement those changes into the front end. We should change the marketplace to the previous one for now.

The newer version adds admin functionality. We’re not quite ready to implement those changes into the front end. We should change the marketplace to the previous one for now.

@obstropolos
Feel free to close this PR once you get the info you need.

Closing for now, fix handled in #280


[Documentation] Provide apitrace instructions for steam/proton

I was about to report a bug in Elite Dangerous with messed up colours on smoke effects as of the latest in-game update but this bug report page requires an apitrace file, unfortunately it's not clear how to do this through steam (proton). I tried adding
apitrace.exe trace -a dxgi  %command%

However it doesn't launch which implies apitrce.exe isn't included in the prefix. Is there an easy way to include apitrace.exe reports from within steam?

The guide over here is still pretty good:
https://github.com/Joshua-Ashton/d9vk/wiki/Making-a-Trace

You added an apitrace to your original issue, so I think it's safe to say that you did figure it out.
Closing this.


Add AutoHotkey lexer

Adds a lexer for AutoHotkey (https://en.wikipedia.org/wiki/AutoHotkey) based on the AutoIt lexer.
Is there a way to enforce both a minimum and maximum amount of characters via patt^n and patt^-n? This would be for an F-key rule (match F1-F12 but don't match F123 or F by itself).
Is it possible for word_match to be case insensitive? Currently it does not seem to work.

I can't think of a way to do that. The CSS lexer recognizes #rgb and #rrggbb using xdigit * xdigit * xdigit * (xdigit * xdigit * xdigit)^-1, so perhaps you can do something similar.
Are there any file extensions for AutoHotkey scripts? You can add them to lexer.lua's extensions table in the detect() function. (Or I can do so if you let me know.)
word_match() accepts a second argument for case-insensitivity. It works at least for the vb lexer.

Many thanks for your input!
I noticed you even used the case-insensitivity in your latest commit. Sorry for not paying attention to that.


Change mean_axis to use FromPrimitive

The documentation for the Zero and One traits says only that they are the additive and multiplicative identities; it doesn't say anything about converting an integer to a float by adding One::one() to Zero::zero() repeatedly. Additionally, it's nice to convert the length to A directly instead of having to use a loop.

I'd love to be constructive, but :( Isn't there a better way to convert the integer?
We could limit this method to only float and complex numbers (do we have nice traits for that? https://github.com/bluss/complexfloat is a draft). Ideally we support a wider range of scalar types than complex numbers, though.

The other trait from the num-traits crate that would work for this is NumCast, which to some extent reveals less about the internals of mean_axis. It is similar in complexity to implement on custom types, though, because it requires ToPrimitive.
The standard library implements some conversions from integers with From, but not enough to be useful (e.g. From<i32> is implemented for f64 but not f32 because it's only lossless when converting to f64). There's the unstable TryFrom trait, which may work in the future, but it's unclear how it will handle converting to floating-point numbers with a mantissa with fewer bits than the integer (will it just not be implemented, return an error, or round).
Would an A: NumCast bound be better?

FromPrimitive does the right thing for floats at least. Num's traits feel imperfect (that we specify exactly Zero + Add + Div, we should do this at a bit higher level). Here we'd like an approxmating conversion that does not fail.
On one hand I'd like to restrict this to complex numbers, since we know that we don't handle bignums graciously (we probably clone them too much inside sum_axis). But the other case is custom Copy-able scalars, and I guess it could make sense to panic in the usize to scalar conversion there.

On one hand I'd like to restrict this to complex numbers, since we know that we don't handle bignums graciously (we probably clone them too much inside sum_axis).

Why aren't we using Add<&'a A, Output=A> instead of Add<A, Output=A>?

Here we'd like an approxmating conversion that does not fail.

That's what we've been thinking about, but I think the best thing would be if we didn't have to convert the length to A at all, but rather if we could use A: PromotingDiv<usize, Output = A> and directly perform the division. Unfortunately, we can't use Div for this because the Div trait implementations in the standard library are fairly limited.

For floating-point values, this PromotingDiv trait would be implemented by converting the usize to the floating-point type (possibly rounding) and performing the division. In some cases, it may make sense to use a higher-precision floating point type for the division. (For example, ::std::u128::MAX as f32 is inf, while ::std::u128::MAX as f64 is a finite value.)
For integer values, this trait would be implemented either by performing the division with however many bits are necessary for full precision and then converting the result back to the Output type, or by observing that the result is always zero if the divisor is greater than the maximum possible value of the dividend type. (For why this behavior would be nice, consider the current implementation or this PR if A is i8: we can't calculate the mean of more than 127 i8 values, even if the sum fits within i8.)
For complex numbers, just operate elementwise on the real and imaginary parts.
For bignums, convert the usize to a bignum and perform the division.

This also got me thinking about the sum, too. It would be nice if the sum could exceed the maximum of the element type as long as the mean doesn't. For example, consider array![::std::i8::MAX, ::std::i8::MAX]; it would be nice if mean_axis could return ::std::i8::MAX even though the sum of the elements is greater than ::std::i8::MAX. How to do this isn't obvious, though. One option would be to determine the sum type based on the number of elements being added:
// for A = i8
if n <= 1 {
    // use i8
} else if n <= 2 {
    // use i16
}  else if n <= 4 {
    // use i32
} else if n <= 8 {
    // use i64
} else {
    // use i128
}

In practice, this would mean that A would need to provide a mean function because its behavior depends on both the precise type of A and the number of elements. I don't like this, and I'm not sure it's worth doing.
With the options we have available today, I think FromPrimitive or NumCast make the most sense.

Why aren't we using Add<&'a A, Output=A> instead of Add<A, Output=A>?

I think we need even more to do it in a way that saves copies for bignums, for exampe preferring to use AddAssign with &A on the right hand side, so we don't have to create a new number for every operation. Best to implement and look at this whole picture, if we'd want to do it. We used the current way to keep it simple and build a good enough library first :)
Promoting sounds interesting but not important enough. Aren't for example accurate summation algorithms more interesting for sums and means?
And I don't need bignums, I don't want us to spend significant time and complexity on things that ndarray probably isn't going to be used for. (This is why we lean heavily towards floats, isn't it?)

With the options we have available today, I think FromPrimitive or NumCast make the most sense.

Yes. There are options of rewriting the numeric traits. I'd still like to do that, but of course I can't commit to doing that, don't have the time.

I think we need even more to do it in a way that saves copies for bignums, for exampe preferring to use AddAssign with &A on the right hand side, so we don't have to create a new number for every operation.

I don't understand. With A: Add<&'a A, Output = A>, the signature of the add method is fn add(A, other: &A) -> A. The implementation takes ownership of the first argument, so it can modify it in-place and return it. That's how it's actually implemented for BigUint, for example. No copies are necessary (unless you count moves, which are hopefully optimized out by the compiler, and the data in BigUint is a Vec anyway, so unoptimized moves are still cheap).

Promoting sounds interesting but not important enough. Aren't for example accurate summation algorithms more interesting for sums and means?

Yes, for floating-point numbers. I was thinking about adding a sum_kbn method for A: Float.

And I don't need bignums, I don't want us to spend significant time and complexity on things that ndarray probably isn't going to be used for. (This is why we lean heavily towards floats, isn't it?)

I agree. All I really care about for my use-cases is f64.
For the purpose of this PR, should we merge the current version in the next breaking release?

Good point, that makes sense. Sure, let's merge this when we can.

I think my vision for our numerical methods is a bit more focused on primitive numeric types and floats, and possibly using custom numerical traits instead of just the ones from num
Add to that a 'static bound for the scalar so that we can use ad-hoc type based dispatch, just like we do for dot. At this point I don't see much alternatives if we want to dispatch to for example specific SIMD implementations for f32, f64 and complex specifically.

Thanks! I meant to merge this after resolving the conflict. Apparently forgot.


Test against Kafka 1.0.1 rather than 1.0.0

1.0.1 is the bugfix release of 1.0.0

Codecov Report

Merging #783 into master will decrease coverage by 0.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #783      +/-   ##
==========================================
- Coverage   84.83%   84.55%   -0.28%
==========================================
  Files          27       27
  Lines        3580     3580
  Branches      534      534
==========================================
- Hits         3037     3027      -10
- Misses        403      410       +7
- Partials      140      143       +3

Impacted Files
Coverage Δ

pykafka/managedbalancedconsumer.py
84.1% <0%> (-3.98%)
:arrow_down:

pykafka/topic.py
82.97% <0%> (-2.13%)
:arrow_down:

pykafka/simpleconsumer.py
85.61% <0%> (-0.47%)
:arrow_down:

pykafka/cluster.py
74.9% <0%> (-0.39%)
:arrow_down:

pykafka/balancedconsumer.py
91.81% <0%> (-0.3%)
:arrow_down:

pykafka/protocol.py
94.22% <0%> (+0.1%)
:arrow_up:

pykafka/broker.py
90.05% <0%> (+0.58%)
: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 340f8e1...9e19696. Read the comment docs.

Happy to help, thanks for merging


Fixing run example

The parameters needs double dash otherwise I get:
Error parsing commandline arguments: unknown short flag '-c'

in linux at least.

This example is for Prometheus 1.x, for which it is correct.

I am sorry, I thought I was editing the v2 docs.


Made organization's description box responsive #8504

Fixed issue #8504 with the organization description textarea not being responsive.

@Shobitha-M your commit message is not appropriate. Please read the commit guideline and update the commit message.

Hey @Shobitha-M, I had claimed this issue and was working on it. Please keep this in mind next time. Thanks.

I am sorry, I didn't know how the Zulip bot works, new to Zulip. I tried to claim this issue before you but the bot didn't let me do that.
Apologies.

@Shobitha-M also mention the issue in the commit message. For example in this case add Fixes #8504 in the description.

@sinwar Mentioned the issue in the commit message :)

Hello @abhigyank, are you working on this issue?

Not anymore since you created a PR.

@zulipbot claim

@zulipbot claim

@Shobitha-M can you reply to my question above?

Apologies for the late reply. I was having my exams.
I set the width to 98% in the class- organization-settings-parent, so that the content inside the div becomes responsive. I think I should have set it to 100%. Is there some other way to do it? Should I make a new class? And I couldn't find out which part of the page is getting affected due to this.

I merged #8678 as a fix for this, which was a cleaner solution.  Thanks @Shobitha-M!


[0] Add interval selection to Grafana dashboards

Describe the bug
Thanos does automatic downsampling which requires that Grafana changes the interval it queries at to be able to present the metrics. (Else it will just be as if there are no metrics.)
To Reproduce
Steps to reproduce the behavior:

Go back +30 days in Grafana
Perform a query at default 15s interval
See no metrics
Perform a query at 30m interval
See metrics

Expected behaviour
Best would be if it could figure this out automatically, but it seems like we need to add some configuration to add interval selection. (There is an auto mode which seems able to fix this, but it will generally be quite rough so it would be good to have the option to increase the resolution.)
Version (add all relevant versions):

Compliant kubernetes apps version v0.30

Additional context
Adding this would also make Grafana in general more resilient as it's interval is quite conservative so it will reduce the size of long time range queries by a lot.

this should not happen in apps v0.30. closing it for now until we notice it again


New Plastic SCM 4.0 plugin

I've upgraded the Plastic SCM plugin to be compatible with Plastic SCM 4.0 version.
I would like to get it integrated in the next ReviewBoard release.
If you have any doubts, please don't hesitate to ask me.
Best,
Luis

Please post this on http://reviews.reviewboard.org/

Done!
http://reviews.reviewboard.org/r/2798/

Ok, I need to add a group or reviewer to publish it.......

So, who I should add as reviewer to publish the review request?

There are 'rbtools' and 'reviewboard' groups. They should be automatically assigned if you use post-review.

Well, I created the review request several weeks ago and I've noticed that there are new versions of the ReviewBoard that don't include the plugin (that seems to be, according to the release notes). I then visited the review link and it is private so...
I'll try to assign the review to those groups that you've pointed out, because I need the plugin to be integrated asap, as there are clients waiting for it.
Thanks for your help,
Luis


Enter in IPython console inserts new line when big Dataframes are in namespace

@Khris777 said in https://github.com/spyder-ide/spyder/issues/2696#issuecomment-330441511
@ccordoba12
Try this example, it reproduces the problem for me:
import pandas as pd
import numpy as np
nrow = 1000000
ncol = 50
test = np.ones((nrow,ncol),dtype=object)
df = pd.DataFrame(test)

Then enter commands like these into the console:
df.head()
df[df[1] == 1]
df[(df[1] == 1)&(df[4] == 1)]

You should pretty soon encounter a case when pressing enter will bring up another line and seemingly not executing the command.
The behaviour is erratic though, sometimes a command works, then it won't.
Adding the commands into a file and pressing F9 for that line always works, and sometimes after doing so entering a command manually will work again as well.
EDIT: It seems like dtype=object is a significant factor here. Using the same array with dtype=int makes it work well and to encounter some problematic behaviour (still way less than with dtype object) I need to set nrow = 10000000. But since I'm working with arrays/dataframes that have mostly strings in them (internally dtype object), the example case is fitting.

@Khris777, besides my fix in PR #5298, you also need to go to
Preferences > IPython console > Display > Interface

and deactivate the option called
Display ballon tips

Those two things completely fix the error in my side.

Disabling balloon tips already helped a lot, I'm not getting the issue with my example anymore.
Thanks a lot for both fixes.

Problem was the kernel was busy trying to display the ballon tip while you hit Enter to evaluate df.head(), for example. And that was the cause for a new line, instead of a direct evaluation of your expression.

Here the problem persists after disabling balloon tip...
Only getting rid of Numpy options configurations (such as below) helps...
np.set_printoptions(edgeitems=200, linewidth = 200)
The code uses tensorflow, keras, matplotlib and other usual suspects...
So, if anyone has a idea I would be grateful...

@andreidi, thanks for letting us know about it. What those options do?

@ccordoba12 , Hi, well formatting of numpy displayed arrays  (such as how many items left/right for row vectors, how many chars until breaks line)


Comseg cli

implementation of ComSeg cli

An example to run comseg in CLI is in  sopa/docs/tutorials/cli_other_segmentation.md
documentation at "sopa/docs/cli.md" was update fro comseg

A function transcript_segmentation() was created to handle both Baysor and ComSeg

Here is a todo list for the next steps:

[ ] Update the Snakefile and utils.py
[ ] Have a complete ComSeg tutorial for API + CLI + snakemake
[ ] Have a ComSeg config for the toy dataset (used in the above snakemake tutorial)
[ ] Have a ComSeg config for a few major technologies (e.g., MERSCOPE and Xenium)

Thanks for the changes! Regarding the CI, you can install pre-commit locally to fix the issues:
pre-commit install

pre-commit run --all-files

Thanks for the changes! Regarding the CI, you can install pre-commit locally to fix the issues:
pre-commit install

pre-commit run --all-files

Ok thanks I just saw it

I added comseg to the snakemake pipeline + few config file examples.
Now I will complete ComSeg tutorial for API + CLI + snakemake all in the file  : "other_segmentations.ipynb"
do you agree ?

Thanks for your updates, it looks very good!
I fixed and cleaned a few things
Also, I had some issues running comseg, now I get an error 'PCA' object has no attribute 'explained_variance_' when running the patch step of comseg, do you know why?
Two other things:

Installing comseg is not enough to have all the dependencies, I also needed to install alphashape / igraph / leidenalg. Do you think these could be added as a dependency of ComSeg for convenience?
I moved the tutorial in docs/tutorial/comseg.ipynb, can you check and fill the "Snakemake" and "CLI" sections? It can be pretty short, since it is very similar to the existing tutorial. For instance, for the Snakemake pipeline, you can provide the command line to run the toy dataset, and for the CLI you can do something similar to the CLI tutorial with Baysor.
Why do you need to do importlib.reload(method)?

After this, I will merge the PR!

Ok thanks  reviewing!

PCA' object has no attribute 'explained_variance_' I will look at it and also complete dependency of ComSeg

for importlib.reload(method) I will remove it I think it is a mistake

I will do additional tests on other data this week, before the next push.

Hello,
Sorry it took so long, I think that it is now ready for your review.
I added min_transcripts_per_patch and min_cells_per_patch options to the CLI for ComSeg. Additionally, I included support for  other segmentation than Cellpose for prior initialization, which is useful for protocols that already segment nuclei, such as Xenium. I also updated the Snakefile with checkpoint patchify_comseg. An example config for Snakemake + Xenium + ComSeg has been added.
I modified the valid index patches of ComSeg so it run only on crops with nuclei.
I updated the ComSeg dependency in the new pip version. However, I did not encounter the `PCA object has no attribute 'explained_variance_' issue, so I do not know why it occurred for you.


Adding category entry to the frontmatter

The category is used to indicate what section of the documents the page relates to and expands the appropriate menu item

@mmoayyed Please go ahead and merge when you get a chance.


Load a genome reference on project creation, and after

When a user creates a new project, they should be able to select one or more "reference genomes" to include with their project. The options should be:
-hg38 (default)
-b37
-none
Selecting one of the predefined reference genome builds should pre-populate a fixed set of attributes constituting the files relevant to the reference build (fasta, index, reference VCFs, etc).
Each set of reference genome files should appear as its own bundle akin to global variables. "hg38 Reference" etc.  The section currently holding generic global attributes should be given the header "Reference Data"
After a project has been created, the user should have the option of adding additional "reference data" sets (ie, I have the hg38 genome reference bundle and I want to add a b37 genome reference bundle)
The specific set of reference files to load for each of these can be found from FireCloud featured workspaces and should be selected under advice from Brad/Geraldine.

@zarsky-broad said something about a namespacing colon in the attribute names?


Override merge existing lib generators

@adamwathan @reinink @davidhemphill
I am using tailwind via an npm. Its a great tool. Is there a way to override or combine/merge the existing generators in the lib of this module with custom defined styles.
Consider the following
static: { position: 'static' },
fixed: { position: 'fixed' },
absolute: { position: 'absolute' },
relative: { position: 'relative' },
sticky: { position: 'sticky' },
'pin-none': {
  top: 'auto',
  right: 'auto',
  bottom: 'auto',
  left: 'auto'
},
pin: {
  top: 0,
  right: 0,
  bottom: 0,
  left: 0
},
'pin-y': { top: 0, bottom: 0 },
'pin-x': { right: 0, left: 0 },
'pin-t': { top: 0 },
'pin-r': { right: 0 },
'pin-b': { bottom: 0 },
'pin-l': { left: 0 }

This is taken from the position.js. What if I want to add couple of extra classes for position as
'pin-t-m': { top: '50%' },
'pin-l-m': { left: '50%' }

and the final output should be
static: { position: 'static' },
fixed: { position: 'fixed' },
absolute: { position: 'absolute' },
relative: { position: 'relative' },
sticky: { position: 'sticky' },
'pin-none': {
  top: 'auto',
  right: 'auto',
  bottom: 'auto',
  left: 'auto'
},
pin: {
  top: 0,
  right: 0,
  bottom: 0,
  left: 0
},
'pin-y': { top: 0, bottom: 0 },
'pin-x': { right: 0, left: 0 },
'pin-t': { top: 0 },
'pin-r': { right: 0 },
'pin-b': { bottom: 0 },
'pin-l': { left: 0 },
'pin-t-m': { bottom: '50%' },
'pin-l-m': { left: '50%' }

How can I achieve that.
I know that I can simply define these classes in a separate file but want to keep it as a part of build process, so that I don't have to worry about adding these separately all the times.

Yep I would suggest creating your own plugin. All of those classes live in our position module, so you could disable that module in your config and instead use your own advanced positioning plugin.
Writing plugins is really easy, can read more about it here:
https://tailwindcss.com/docs/plugins

Thank you for the reply. From above I can conclude that there is no way to merge existing modules with your own classes for that module. Either you create a new plugin for extra classes or disable that module and create new plugin will the classes + your new classes for that module.


tls-docs-examples

Writer's Quality Checklist
Before merging your PR, did you:

[ ] Run spell checker
[ ] Run link checker to check for broken xrefs
[ ] Check for orphan files
[ ] Perform a local build and do a final visual check of your content, including checking for:

Broken images
Dead links
Correct rendering of partials if they are used in your content
Formatting issues, such as:

Misnumbered ordered lists (steps) or incorrectly nested unordered lists
Messed up tables
Proper indentation
Correct header levels

[ ] Receive final review and signoff from:

Technical SME
Product Manager
Editor or peer reviewer
Reporter, if this content is in response to a reported issue (internal or external feedback)

[ ] If applicable, verify that the software actually got released

Hi @aneisen-mulesoft, I just committed a change to this branch that moves one of the pages you're modifying. This is why there's a merge conflict. The new location of the page is:
https://github.com/mulesoft/docs-gateway/blob/get-well-staging-branch/gateway/1.4/modules/ROOT/pages/policies-included-tls-outbound.adoc

Hi @aneisen-mulesoft, is this PR still an open issue? If so, the files have moved. Also, can you prepend a GUS ID to the subject of this PR? We're being asked to include GUS ID's so we can trace contributions.

@aneisen-mulesoft  Would you please create a GUS work item for this so we can trace it and keep track of the rationale for the changes requested in the PR?

Closed as outdated.