Metamask not detected on Brave/Opera

When using Brave/Opera I get the Metamask not installed banner even though I have metamask installed.

It seems that @tomclose and @geoknee have been able to use to brave/opera so it looks like this is something particular to me?

I am also hitting this issue with Brave. So I don't think it's just your local setup @lalexgap.

@kerzhner with Brave I followed these instructions and was able to use metamask after.

I think maybe the Brave settings have changed, but I had different UI in my settings.

But now, Metamask is detected properly on web3torrent.statechannels.org.


Translate contribute/new-content/new-content/ in Korean

This is a Feature Request

What would you like to be added

Translate contribute/new-content/new-content/ in Korean.
Why is this needed
There is no document of contribute/new-content/new-content/ which translated into Korean.
Comments

Page to translate: https://kubernetes.io/docs/contribute/new-content/new-content/
/language ko

/assign


[$125]  Settings - Wrong index when pressing Tab button in the Save the world section

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.85-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Open the app
Go to Account Settings
Tap on Save the World
Press the Tab on the keyboard

Expected Result:
"I am a teacher" should selected when pressing a first Tab
Actual Result:
Wrong index when tapping the Tab button in the Save the world section, "I am a teacher" first selected instead "I know a teacher"
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/295897c6-41b9-4fe9-b93c-b954582dba2b

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e452205241cde504
Upwork Job ID:<PHONE_NUMBER>857100557
Last Price Increase: 2024-06-21
Automatic offers:

s77rt | Reviewer | 102862296

Issue OwnerCurrent Issue Owner: @s77rt

We should probably fix this for accessibility consistency, but it's such a small issue so I'm going to reduce the payout to $125.

@devguest07 Your RCA makes sense and the solution works but can we add all the settings routes at once instead of adding each manually? (This is missing SCREENS.SETTINGS.TROUBLESHOOT as well)

This is not a blocker. We can proceed with your solution.
🎀 👀 🎀 C+ reviewed
Link to proposal

Looks like this was fixed by another PR https://github.com/Expensify/App/pull/43832

Bump @sakluger

Should we close this one? The bug has been fixed by another PR

Sorry for the delay, I missed this one entirely.
I'm going to check with my team to see if we should compensate for the work done here.

We will pay out the full amount for this issue. @devguest07 could you please apply to the Upwork job or share your Upwork profile so that I can send you an offer? Thanks!

Summarizing payment on this issue:
Contributor: @devguest07 $125, payable via Upwork (No offer yet)
Contributor+: @s77rt $125, please request on Newdot

$125 approved for @s77rt

Found @devguest07's Upwork profile and sent an offer: https://www.upwork.com/nx/wm/offer/103264866.
@devguest07 please let me know once you've accepted the offer so I can complete the payment and close the GH issue. Thank you!

Thanks! All paid 👍


AttributeError: 'State' object has no attribute 'ENABLE_API_KEY_ENDPOINT_RESTRICTIONS' when accessing API via curl

Bug Report
Installation Method
I installed OpenWebUI using pip install within a Python 3.11 virtual environment created with Miniconda.
Environment

Open WebUI Version: [v0.3.11]

Ollama (if applicable): [N/A]

Operating System: Ubuntu 24.04

Browser (if applicable): N/A

Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[x] I have included the browser console logs (open-webui logs)
[ ] I have included the Docker container logs.
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
When making an API request to /api/models with a valid API key using curl, the application should validate the API key and return the appropriate response without errors. The ENABLE_API_KEY_ENDPOINT_RESTRICTIONS attribute should be properly recognized by the application.
Actual Behavior:
When making an API request to /api/models with a valid API key in the Authorization header using curl, the application fails and raises the following error:
bash
AttributeError: 'State' object has no attribute 'ENABLE_API_KEY_ENDPOINT_RESTRICTIONS'

This issue occurs because the ENABLE_API_KEY_ENDPOINT_RESTRICTIONS attribute is not initialized in the application state (app.state). However, when accessing the same endpoint via a web browser, the error does not occur, and the endpoint functions as expected.
Description
Bug Summary:
The application attempts to access request.app.state.ENABLE_API_KEY_ENDPOINT_RESTRICTIONS during API requests made using curl, but this attribute is not initialized, resulting in an AttributeError. This issue does not occur when accessing the same endpoint via a web browser, leading to inconsistent behavior.
Reproduction Details
Steps to Reproduce:

Install OpenWebUI using pip in a Python 3.11 virtual environment.
Start the OpenWebUI server.
Enable "API Key Endpoint Restrictions" in the OpenWebUI settings.
Send a request to /api/models with a valid API key in the Authorization header using curl:curl -H "Authorization: Bearer <valid_api_key>" https://your_openwebui_server/api/models

Observe the following error in the logs:AttributeError: 'State' object has no attribute 'ENABLE_API_KEY_ENDPOINT_RESTRICTIONS'

Logs and Screenshots
Relevant Logs:
Traceback (most recent call last):
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 401, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in __call__
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in __call__
    await self.app(scope, receive, _send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/cors.py", line 85, in __call__
    await self.app(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in __call__
    with collapse_excgroups():
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/open_webui/main.py", line 723, in inspect_websocket
    return await call_next(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in __call__
    with collapse_excgroups():
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/open_webui/main.py", line 702, in check_url
    response = await call_next(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in __call__
    with collapse_excgroups():
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/open_webui/main.py", line 692, in commit_session_after_request
    response = await call_next(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in __call__
    with collapse_excgroups():
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/open_webui/utils/security_headers.py", line 11, in dispatch
    response = await call_next(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in __call__
    with collapse_excgroups():
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/open_webui/main.py", line 681, in dispatch
    response = await call_next(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 65, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/routing.py", line 756, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/routing.py", line 776, in app
    await route.handle(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/routing.py", line 297, in handle
    await self.app(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/routing.py", line 77, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/routing.py", line 72, in app
    response = await func(request)
               ^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/fastapi/routing.py", line 269, in app
    solved_result = await solve_dependencies(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 572, in solve_dependencies
    solved_result = await solve_dependencies(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 602, in solve_dependencies
    solved = await run_in_threadpool(call, **sub_values)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/concurrency.py", line 42, in run_in_threadpool
    return await anyio.to_thread.run_sync(func, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2505, in run_sync_in_worker_thread
    return await future
           ^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 1005, in run
    result = context.run(func, *args)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/open_webui/utils/auth.py", line 99, in get_current_user
    if request.app.state.ENABLE_API_KEY_ENDPOINT_RESTRICTIONS:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/suntzuping/miniconda3/envs/open-webui/lib/python3.11/site-packages/starlette/datastructures.py", line 702, in __getattr__
    raise AttributeError(message.format(self.__class__.__name__, key))
AttributeError: 'State' object has no attribute 'ENABLE_API_KEY_ENDPOINT_RESTRICTIONS'

Screenshots/Screen Recordings (if applicable):
N/A
Additional Information
Suggested Fix:
The issue can be resolved by:

Using getattr to handle the missing attribute gracefully in auth.py at line 99:
if getattr(request.app.state, "ENABLE_API_KEY_ENDPOINT_RESTRICTIONS", False):

Environment Details:

Python 3.11
Miniconda virtual environment
Running as a systemd service
Endpoint tested: /api/models

#8135

99386bf Already fixed in dev, so, hope that 0.5.3 is coming soon

Cool beans

Every time I open the page, it stays blank. After checking the network requests, I found that the /api/module endpoint is always pending, and eventually, it throws the error mentioned above. This process takes a long time, around 2-3 minutes. It will be fixed in the next version, right?


Support different types of block devices

Which issue(s) this PR fixes:

Issue Longhorn/longhorn#7672
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context

Resolved the conflict. @shuo-wu can you help check and approve again? Thank you.

cc @shuo-wu


[#171281178] Document metric exporting to prometheus

What
Does three main things:

Separates the monitoring documentation into different pages for apps and services
Adds instructions on how to get backing service metrics into Prometheus
Removes metric descriptions that now exist inline with the metric graphs in paas-admin

See the commit messages for more details.
How to review

Preview the content locally (see README) and check that it renders as expected.
Manually check that any removed or renamed anchor tags are not in use (linkchecker doesn't do this).

Who can review
Not @46bit

Now that I've removed the metrics definitions, the "Monitoring backing services" page is quite short. I suggest we keep it that way, as the "Monitoring apps" section is huge.
I think we need to be able to have separate pages where necessary--for instance, instructions for setting up Logit. These long sets of instructions pollute the pages and make it impossible to find anything by scrolling.

The Monitoring Apps docs could use some love, but I'm not going there right now. I've filed #344 for one of the most obvious issues with them.


[DH-514] Add sort by company sector in Contact search.

As in the subject.

Codecov Report

Merging #421 into develop will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #421      +/-   ##
===========================================
- Coverage    96.04%   96.02%   -0.02%
===========================================
  Files           90       89       -1
  Lines         3007     2994      -13
  Branches       258      258
===========================================
- Hits          2888     2875      -13
  Misses          82       82
  Partials        37       37

Impacted Files
Coverage Δ

datahub/search/contact/views.py
90.9% <ø> (ø)
:arrow_up:

datahub/omis/order/serializers.py
100% <0%> (ø)
:arrow_up:

datahub/omis/order/validators.py

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 964a11a...52d5927. Read the comment docs.


Actually name the controls

goodness I'm lazy

Done with https://github.com/dotcomboom/gopherit/commit/81a7d8e50c3260c6f1b4215cbdc263581a0c6444


Azure SQL MI GA

This article shows the wrong information. https://techcommunity.microsoft.com/t5/Microsoft-Data-Migration/Announcing-General-Availability-of-Azure-SQL-Database-Managed/ba-p/368706

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

ID: 33c1b11a-7bd3-6ed2-d9ad-ec31da29bd55
Version Independent ID: 5bddd6fb-c779-f408-94bf-937934c5ca29
Content: Rehost an on-premises app by migrating to Azure VMs and Azure SQL Database Managed Instance - Microsoft Cloud Adoption Framework for Azure
Content Source: docs/migrate/azure-best-practices/contoso-migration-rehost-vm-sql-managed-instance.md
Service: cloud-adoption-framework
Sub-service: migrate
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

update to be released in next push to live site.


Hyperfoil 0.5.2

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Hi @rvansa, please sign your commit according the output
There is also some issue running operator on the test pipeline, please have a look.

Hi @J0zi , thanks for the heads up. Not sure what failed in the CI but I've added the sign-off and it seems to be green now.

Thanks!


clicking git add in an atom settings dialog has bad unintended consequences

I have atom open and the project view open with a root folder of a git project displayed. I went into atom's settings view and was going to add a file pattern to the 'Ignored Names' input field, and somehow ended up clicking 'Git add' in the context menu by mistake. I canceled the context menu and pasted the string I was trying to paste in there, and about 3 minutes later, a confirmation notice popped saying 'git add succeeded'. I panicked and went out and did a git status, and sure enough, every file and folder from the root down had been added. luckily, my working tree was in a state that git reset undid the add without affecting any other of my working set.
Git-plus should not be active on a non project file related dialog/tab

The next update will have this fixed.


I've swapped Win-Left and Alt-Left and now Win+R doesn't work

Microsoft PowerToys version
0.43.0
Running as admin

[ ] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce
Hello! I've turned on Keyboard manager and added key swaps:
Windows (left) -> Alt (left)
Alt (left) -> Windows (left)
Now when I press the physical Alt key plus E, it opens Explorer (as expected).
But when I press the physical Alt key plus R, nothing happens.
When I press the physical Windows key plus R, nothing happens.
When I press the physical Alt key, the Start menu pops up, so I know the remapping worked.
PowerToysReport_2021-08-29-03-48-34.zip
✔ Expected Behavior
"Run command" should pop up
❌ Actual Behavior
Nothing.
Other Software
No response

Actually I just noticed when I press (logical) Windows+R (i.e., physical Alt plus R), PowerToys starts recording my screen.

Here is the recording window:

When I click the "stop" icon, it says XBox Game Bar has finished recording.
So I guess Win+R invokes the recording from XBox Game Bar.
I can't uninstall "XBox Game Bar" (a Microsoft app).  The uninstall button is greyed out.

Can reproduce

I've turned off the Game Bar following https://www.howtogeek.com/273180/how-to-disable-windows-10s-game-dvr-and-game-bar/ but Win+R still doesn't bring up the Run Command window.

Even stranger: Default hotkey to start recording is Win+Alt+R

I tried rebooting but that didn't help.

I tried uninstalling XBox Game Bar following the directions in
https://www.minitool.com/news/how-to-uninstall-xbox-game-bar.html:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\WINDOWS\system32> dism /Online /Get-ProvisionedAppxPackages | Select-String PackageName | Select-String xbox
PackageName : Microsoft.Xbox.TCUI_1.23.28002.0_neutral_~8wekyb3d8bbwe
PackageName : Microsoft.XboxApp_48.76.8001.0_neutral~8wekyb3d8bbwe
PackageName : Microsoft.XboxGameOverlay_1.54.4001.0_neutral~8wekyb3d8bbwe
PackageName : Microsoft.XboxGamingOverlay_5.721.8052.0_neutral~8wekyb3d8bbwe
PackageName : Microsoft.XboxIdentityProvider_12.67.21001.0_neutral~8wekyb3d8bbwe
PackageName : Microsoft.XboxSpeechToTextOverlay_1.21.13002.0_neutral~_8wekyb3d8bbwe
PS C:\WINDOWS\system32> dism /Online /Get-ProvisionedAppxPackages | Select-String PackageName | Select-String xbox | ForEach-Object {$.Line.Split(':')[1].Trim()} | ForEach-Object { dism /Online /Remove-ProvisionedAppxPackage /PackageName:$}
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19043.1165
The operation completed successfully.
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19043.1165
The operation completed successfully.
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19043.1165
The operation completed successfully.
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19043.1165
The operation completed successfully.
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19043.1165
The operation completed successfully.
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19043.1165
The operation completed successfully.
PS C:\WINDOWS\system32>

XBox Game Bar still shows up in my Start menu, so those directions didn't work.

I just remembered I'd run into this earlier -- https://github.com/microsoft/PowerToys/issues/5956 is still open about it
I'll update that original issue and close this one as a duplicate.


[Bug] State parameter is not returned in case of error

In case of authentication error, the state parameter is not returned to the RP redirect URI.
You could reproduce it, for example, by clicking "Cancel" on the login form, no "state" querystring parameter will be returned to the RP

Done here
https://github.com/italia/spid-cie-oidc-django/pull/205#pullrequestreview-927199386

Verified. The issue can be closed


AMBARI-25391 Ambari logging Grafana Password in ActionQueue.py (santal)

What changes were proposed in this pull request?
This is a critical Security Issue. Grafana uses the admin password for Ambari by default during its setup. This password is getting logged from the ActionQueue.py....  As this is the admin password for the cluster this is a huge security risk to have this logged in plaintext in Syslog.
ActionQueue.py [ 6398 ] - root - INFO - Cmd log for taskId=456 and chunk 3/42 of log for command: #012s_user\', \'hdfs\')}}/hadoop-{{default(\'configurations/hadoop-
.
.
.
  u'metrics_grafana_log_dir': u'/var/log/ambari-metrics-grafana',
  u'metrics_grafana_username': u'admin',
*  u'metrics_grafana_password': u'mypassword123!',*
  u'metrics_grafana_pid_dir': u'/var/run/ambari-metrics-grafana',
  u'metrics_grafana_data_dir': u'/var/lib/ambari-metrics-grafana'
}, u'ranger-hive-policymgr-ssl': {
  u'xasecure.policymgr.clientssl.keystore': u'/usr/hdp/current/hive-server2/conf/ranger-plugin-keystore.jks',
  u'xasecure.policymgr.clientssl.truststore': u'/usr/hdp/current/hive-server2/conf/ranger-plugin-truststore.jks',
  u'xasecure.policymgr.clientssl.truststore.credential.file': u'jceks://file{{credential_file}}',
  u'xasecure.policymgr.clientssl.keystore.password': u'myKeyFilePassword',
  u'xasecure.policymgr.clientssl.truststore.password': u'changeit',
  u'xasecure.policymgr.clientssl.keystore.credential.file': u'jceks://file{{credential_file}}'
}, u'hivemetastore-site': {
  u'hive.service.metrics.hadoop2.component': u'hivemetastore',
  u'hive.metastore.metrics.enabled': u'true',
  u'hive.service.metrics.reporter': u'HADOOP2'
}, u'llap-cli-log4j2': { u'content': u'\n# Licensed to the Apache Software Foundation (ASF) under

The fix looks for matching passwords in the log message and replaces them with *****.
How was this patch tested?
The patch was tested by unit tests.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5473/
Test PASSed.

done with requested changes  @aonishuk please review it

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5475/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5476/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5478/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5479/
Test PASSed.


The use of longdouble numpy types

Dear Samuel,
I have been very interested in your research regarding "force rdf" calculations and implemented my own version to postprocess reaction properties from AIMD simultions in VASP. Your code majorly inspired me and of course it will be cited adequately.
I do have a question though, you rely on dtype=np.longdouble, is there a specific reason that you did not use a np.float64 here? Normally, I would avoid the longdouble as it is very badly defined and depends on the os of the computer. I tried to calculate the forcerdf with both and had very similar results. Could you explain why you selected the longdoubles?
I did notice that there seems to be an accumulation of rounding errors in both the "from zero" and the "from infinity" (or better L/2) cases. It mostly seems to occur in very steep parts of the rdf. Is this reduced when using longdoubles? I added a plot below where I have the rdf of the atoms inside a water molecule (you can derive the shape of the molecule from this). This plot shows this error clearly while the oxygen-oxygen rdf (now show) does not have this problem at all. Using the reduced covariance method really solved this issue, so I am using that one now.
Thanks in advance and kind regards,
Jelle Lagerweij

I have a second question regarding the fundamentals of your method. The rescale factor contains the temperature and some physical constants. In my code, I use rescale1 = 8*np.pi*(co.k/co.eV)*self.T_set and you have something similar: accumulated_storage_array*=prefactor/(4*np.pi*len(to_run)*generate_boltzmann(TS.units)*temp) (you do some of the rescaling in a different order so some terms you have in the prefactor are in my rescale1 ect.).
My question is regarding the temperature, I run MD simulations, so I have fluctuating temperatures. Would you advise using the instantaneous temperature of the specific time step or the average temperature? I loop over many time steps and average and rescale my rdf afterward. Now I am using my average temperature, but I got unsure about this. Maybe you can shed some light on my questions.
Thanks in advance,
Jelle

Hello JelleI’m so sorry for my delay in replying. I find the usage of the maximum amount of precision is useful for the method hence the use of long double. This as I remember was particularly important when calculating the frames in order to get the variance. I might look into setting a float128 over the next couple of days as I work on the code thanks for the suggestion.I was wondering what you mean by rounding errors is this something other than the Delta value we refer to in this publication: https://pubs.aip.org/aip/jcp/article/154/19/191101/565890I’ll reply to your next message as a separate postBest on sorry for the delay again Sam Sent from my iPhoneOn 31 May 2024, at 10:47, Jelle Lagerweij @.***> wrote:
Dear Samuel,
I have been very interested in your research regarding "force rdf" calculations and implemented my own version to postprocess reaction properties from AIMD simultions in VASP. Your code majorly inspired me and of course it will be cited adequately.
I do have a question though, you rely on dtype=np.longdouble, is there a specific reason that you did not use a np.float64 here? Normally, I would avoid the longdouble as it is very badly defined and depends on the os of the computer. I tried to calculate the forcerdf with both and had very similar results. Could you explain why you selected the longdoubles?
I did notice that there seems to be an accumulation of rounding errors in both the "from zero" and the "from infinity" (or better L/2) cases. It mostly seems to occur in very steep parts of the rdf. Is this reduced when using longdoubles? I added a plot below where I have the rdf of the atoms inside a water molecule (you can derive the shape of the molecule from this). This plot shows this error clearly while the oxygen-oxygen rdf (now show) does not have this problem at all. Using the reduced covariance method really solved this issue, so I am using that one now.
Thanks in advance and kind regards,
Jelle Lagerweij
rdf_water.png (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hello JelleSo the temperature was something I looked into when I was looking at the delta offset. I found little computational difference between the two.The method is derived using the average temperature (free of fluctuations) and so Benjamin and I felt it was more proper to do this.I Hope this helpsPlease feel free to ask any further questions, if you’d like to discuss any of the science in more detail you should be able to find my professional email on the Cambridge university website. I’m in the ice group at the department of chemistry Have a nice daySamSent from my iPhoneOn 20 Jun 2024, at 15:26, Jelle Lagerweij @.> wrote:
I have a second question regarding the fundamentals of your method. The rescale factor contains the temperature and some physical constants. In my code, I use rescale1 = 8np.pi(co.k/co.eV)self.T_set and you have something similar: accumulated_storage_array=prefactor/(4np.pi*len(to_run)*generate_boltzmann(TS.units)*temp) (you do some of the rescaling in a different order so some terms you have in the prefactor are in my rescale1 ect.).
My question is regarding the temperature, I run MD simulations, so I have fluctuating temperatures. Would you advise using the instantaneous temperature of the specific time step or the average temperature? I loop over many time steps and average and rescale my rdf afterward. Now I am using my average temperature, but I got unsure about this. Maybe you can shed some light on my questions.
Thanks in advance,
Jelle
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Add Deck Royale to the list

I've made a SPA using Vue and Express using this API to generate random decks and display some other information.
You can check the FrontEnd of the app on Deck Royale - https://github.com/ikenami/Deck-Royale.
And you can check the server that runs the app on Deck Royale Server - https://github.com/ikenami/Deck-Royale-Server.
And you can test it on Heroku here - http://deck-royale-ultimate.herokuapp.com/.

Hey! Seems nice! 😃
Unfortunately, your Heroku App is down

I turned it off on accident, oops. Now it's up and running. :D

The website looks really well! I
'll add it to the list of projects, thanks for using my API 😸

I got these requests failing @ikenami, what's happening?

Hey, @TorzuoliH , I see. The problem is that different browsers treat the Mixed Contend error differently. This happens because Heroku server the website via HTTPS and I'm making an HTTP request to the API. Chrome let it pass as a warning, that's why it worked fine for me. But other browsers (Safari, Edge, Mozilla,..) block the content instead, that's why you get these error messages.
I've made some changes on my application and it should work just fine in any browser if you use HTTP instead. :) Try using this link: http://deck-royale-ultimate.herokuapp.com
And if the error persists (or you would like to see some new features) you can create an issue on my project! (https://github.com/ikenami/Deck-Royale) Since this is an error from my application and not this API, it would be best if we could solve it there. :D

Ok I see, it seems to be solved on Chrome macOS. I tried on Chrome Windows 10, it wasn't working well.
Good job :)


Follow NIO conventions closer

Remove throws and use makeFailedFuture instead.
Always return an EventLoopFuture instead of an Optional (returning a failed future in that condition).

Hi @joshjacob , sorry for the long response time. Looking at it now, and the tests needed updating. Got them all updated bar one

@niklassaers I have a couple updates to this PR: the patch file you sent me, the fix for leaked promise I sent you, and then a final update to the SocketTests. The only outstanding issue I see is with the *Transaction tests failing. It appears that neo4j 4.x.x syntax changed. Do you happen to know if that's the case?

Thanks, Josh. When running "swift build" I get NIO compile issues, trying to figure out what that is about.
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/CircularBuffer.swift:114:1: error: type 'CircularBuffer<Element>' does not conform to protocol 'MutableCollection'
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/CircularBuffer.swift:114:1: error: unavailable subscript 'subscript(_:)' was used to satisfy a requirement of protocol 'MutableCollection'
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/MarkedCircularBuffer.swift:132:1: error: type 'MarkedCircularBuffer<Element>' does not conform to protocol 'MutableCollection'
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/MarkedCircularBuffer.swift:132:1: error: unavailable subscript 'subscript(_:)' was used to satisfy a requirement of protocol 'MutableCollection'
error: emit-module command failed with exit code 1 (use -v to see invocation)[4/22] Emitting module NIO
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/CircularBuffer.swift:114:1: error: type 'CircularBuffer<Element>' does not conform to protocol 'MutableCollection'
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/CircularBuffer.swift:114:1: error: unavailable subscript 'subscript(_:)' was used to satisfy a requirement of protocol 'MutableCollection'
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/MarkedCircularBuffer.swift:132:1: error: type 'MarkedCircularBuffer<Element>' does not conform to protocol 'MutableCollection'
Bolt-swift/.build/checkouts/swift-nio/Sources/NIO/MarkedCircularBuffer.swift:132:1: error: unavailable subscript 'subscript(_:)' was used to satisfy a requirement of protocol 'MutableCollection'

Updated NIO versions:
        .package(name: "swift-nio", url: "https://github.com/apple/swift-nio.git", from: "2.39.0"),
        .package(name: "swift-nio-ssl", url: "https://github.com/apple/swift-nio-ssl.git", from: "2.18.0"),
        .package(name: "swift-nio-transport-services", url: "https://github.com/apple/swift-nio-transport-services.git", from: "1.11.4"),

That fixed the errors (but I'm not clear as to why those versions came now and not before, though). Ran it on a test server v4.4.5 and got a number of deprecations in the tests, leading to 7 test failures with NIO errors. Will have a look

(mostly the encrypted tests, may be a local setup issue, checking it out)

Regarding the 100k test, you're totally right that the problem here is old syntax, will fix that up

@niklassaers It looks like this may be a recent issue with Xcode 13.3:

https://stackoverflow.com/questions/71722562/circularbuffer-error-after-upgrading-to-xcode-13-3-swiftnio-vapor-in-the-mix
https://developer.apple.com/forums/thread/703340

I'll take another look with that version of Xcode and the updated NIO versions.
– josh

I'll merge and then merge in changes tonight. Not quite sure how to put changes into the branch without sending you diffs all the time - I should figure that out


react-native link react-native-snap-carousel not working for 0.62.2 version of React native.

react-native link react-native-snap-carousel not working for 0.62.2 version of React native.
Environment
Environment:
React: 16.11.0
React native: 0.62.2
react-native-snap-carousel: 3.9.1
Target Platform:
Android (9.0)
Expected Behaviour
It should automatically link/ add the dependencies to the corresponding IOS/ android files.
Actual Behaviour
It is not linking/adding dependencies to android.

As I am new to android development, if you could help me to manually link the package to the android it would be great help. For debug build it is working fine. whereas for the release build it is not loading.
Many Thanks.

@selvarajendran The plugin has no external native dependencies — apart from the React native ones that is.
So no react-native link command is required to use it.


[WIP] refactor(organisms):  SfAccordion

Checklist

[x] No commented blocks of code left
[x] Run tests and docs
[x Self code-reviewed

@aniamusial please adjust this component to desing
[storybook]

[design]

on desktop we don't have borders

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Set hstart to timestep

To make it easy to test backward euler in the performance repository, I've added h_start to the backward euler parameters. This means we can use the same testing code for rosenbrock or backward euler

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

Project coverage is 93.19%. Comparing base (9c93671) to head (db522ab).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #679   +/-   ##
=======================================
  Coverage   93.19%   93.19%
=======================================
  Files          53       53
  Lines        3586     3586
=======================================
  Hits         3342     3342
  Misses        244      244

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


SASS-1670 Create Expenses Interrupt Page

Description
Expenses - Create interrupt page following 'do you want to claim employment expenses
Add a link to the relevant story in Jira
SASS-1670
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[x]  Have you moved the task to “in review” on JIRA?
[x]  Have you checked to ensure all dependencies are up to date?
[ ]  Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[x]  Have you run the tests?

[x]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
[x]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of main?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[x]  Have you checked the PR Builder passes?

Can be rebased


New syntax: (x: X) => mutates x to Y, similar to asserts x as Y but not only narrowing

🔍 Search Terms
mutation, tuple push
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

Design Goals #5 might be iffy here; I suspect the questions here will be less “how does this work?” and more “is this a good idea?” I think being able to capture a common JavaScript paradigm is worth risking some surprise, but it’s a fair question.
⭐ Suggestion
A special return type similar to (x: X) => asserts x is Y, but instead is mutates x to Y. Does different (less) checking about x and Y than asserts x is Y does, and does not assume that afterwards x is X & Y, instead changing x’s type to just Y.
📃 Motivating Example
The thing that got me started on this is that we were manually creating a FormData structure (for a library):
const form = new FormData();
form.append('foo', 'something');
form.append('foo', 'else');
form.append('bar', 'Coyote Ugly');

And I wanted to type this better, so that form.getAll('foo') knows it’s getting ['something', 'else'] and form.getAll('bar') knows it’s getting ['Coyote Ugly']. I created a TypedFormData interface with a generic parameter Pairs extends Record<string, [FormDataEntryValue, ...FormDataEntryValue[]]>, and used that to type all of the methods. For mutating methods, I used asserts this is to indicate the new value.
For example, to type append (with a string value, I had overloads for blobs and blobs-with-filenames), I used
export interface TypedFormData<Pairs extends Record<string, [FormDataEntryValue, ...FormDataEntryValue[]]> = {}> extends FormData {
    append<K extends string, V extends string>(name: K, value: V): asserts this is TypedFormData<{
        [P in (keyof Pairs) | K]: [
            ...(P extends keyof Pairs ? Pairs[K] : []),
            ...(P extends K ? [V] : [])
        ] extends infer NewTuple extends [FormDataEntryValue, ...FormDataEntryValue[]] ? NewTuple : never
    }>;

This actually works—once. That is, after form.append('foo', 'something') in my above, t has type TypedFormData<{ foo: ['something'] }> and all my typing works. However, further calls to append fail: I get TypedFormData<{ foo: ['something'] }> & TypedFormData<{ foo: ['something', 'else'] }> and then that does not behave correctly with any my method signatures to indicate the correct type.
This is due to how asserts works, and makes sense because asserts wasn’t meant for this scenario. But I would like something that is.
💻 Use Cases

Mutating objects in-place is a pretty common JavaScript pattern. There’s a trend towards immutable objects and not doing this kind of thing—which is great—but there’s a ton of existing code and libraries, including lots of the standard library, that mutate like this. There is a lot of use-case here.

The obvious concern is that it is arguably extremely surprising for something annotated as one thing to have a different type later. Assertions—narrowing—are one thing, since it still fits the original annotation, but this would be something actually changing and quite possibly no longer fitting that annotation at all.
Another issue is more practical: one of the biggest use-cases for this is (non-readonly) tuples, and this suggestion alone doesn’t solve all of the problems for those. All of the mutating methods on Array also return values (e.g. push returning the new length), which is a problem here—and arguably something that also needs to be considered for asserts x is Y constructions, because a function that asserts a type may also return things. That’s a separate concern but without addressing both, one of the strongest use-cases for this change (tuples) isn’t actually going to be solved by this change.

The “workaround,” such as it is, is to just accept that you can’t generate an interface that will track its own type this way. You either set the type to something extremely broad and generic—losing any type safety you might have had by being more specific—or you literally just accept types that are wrong or use type casting to tell TS what is going on. We have the signatures of native methods being completely wrong in certain cases, such as the issues with mutating (non-readonly) tuples in #52375. Per #6325, TS isn’t going to restrict non-readonly tuples to use ReadonlyArray methods, so this is a fairly-serious instance of unsound-ness that isn’t going away.

Essentially a duplicate of #22865.

I saw that, and it is the same concept, but a different syntax more in line with what Typescript already has (at this point).

A different syntax for the very same problem usually does not warrant a new issue. It's better suited as a comment.
Quoting RyanCavanaugh:

we prefer to organize issues by use case / end-goal, not have competing separate issues for different syntactic representations.


Can you help with finding this code.

let PAPAppDelegateApplicationDidReceiveRemoteNotification           = "com.parse.Anypic.appDelegate.applicationDidReceiveRemoteNotification"
let PAPUtilityUserFollowingChangedNotification                      = "com.parse.Anypic.utility.userFollowingChanged"
let PAPUtilityUserLikedUnlikedPhotoCallbackFinishedNotification     = "com.parse.Anypic.utility.userLikedUnlikedPhotoCallbackFinished"
let PAPUtilityDidFinishProcessingProfilePictureNotification         = "com.parse.Anypic.utility.didFinishProcessingProfilePictureNotification"
let PAPTabBarControllerDidFinishEditingPhotoNotification            = "com.parse.Anypic.tabBarController.didFinishEditingPhoto"
let PAPTabBarControllerDidFinishImageFileUploadNotification         = "com.parse.Anypic.tabBarController.didFinishImageFileUploadNotification"
let PAPPhotoDetailsViewControllerUserDeletedPhotoNotification       = "com.parse.Anypic.photoDetailsViewController.userDeletedPhoto"
let PAPPhotoDetailsViewControllerUserLikedUnlikedPhotoNotification  = "com.parse.Anypic.photoDetailsViewController.userLikedUnlikedPhotoInDetailsViewNotification"
let PAPPhotoDetailsViewControllerUserCommentedOnPhotoNotification   = "com.parse.Anypic.photoDetailsViewController.userCommentedOnPhotoInDetailsViewNotification"
I want to know where this function i.e didFinishImageFileUploadNotification is defined. I am new to NSNotification. Thanks

Hi @nishantdongare , looks like it is dead code.


Change how we specify environment markers

The latest version of setuptools (36.2.0) introduced https://github.com/pypa/setuptools/pull/1085, which disallows the manner in which we were specifying environment markers, which broke a variety of env marker usages https://github.com/pypa/setuptools/issues/1087.
This PR properly specifies env markers.

You don't need to name it differently, this would work:
    extras_require={
        'test': ['flake8'],
        'test:python_version >= "3.4"': ['mypy'],
    },

installing both flake8 and mypy when using Python 3.


create template package.

fixed #12
Signed-off-by: Bo-Yi Wu<EMAIL_ADDRESS>

Current coverage is 95.04% (diff: 100%)

Merging #13 into master will not change coverage

@@             master        #13   diff @@
==========================================
  Files             2          2
  Lines           121        121
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            115        115
  Misses            3          3
  Partials          3          3

Powered by Codecov. Last update cd6f912...accc7fb


Embed the notebook kernel information in page metadata

Right now when we parse notebooks, we throw away any notebook-level metadata that is not string/int/float:
https://github.com/ExecutableBookProject/MyST-NB/blob/master/myst_nb/parser.py#L173
However, this throws away the notebook kernel information, which may be useful for interactive tools like Thebelab. Here's the structure it has:
 "metadata": {
   "kernelspec": {
     "display_name": "Python 3",
     "language": "python",
     "name": "python3"
   }
  }

Can we either:

Special-case the kernel information and put it in the metadata of the page (really we just need name, but perhaps language as well.
Keep non int/float/string values as strings in the page metadata? (that's what we currently do for manually-specified Front Matter in myst-markdown)

Yeh just json serialize

This is fixed in #147


replaced (deprecated) property with exchangeProperty

With this small changes this example works also with Camel 3.
Added toString method for malformed record tracing logic.

Thanks a lot, merged


Add Permissions-Policy header

Add Permissions-Policy to the list of headers

Thanks for submitting the PR! My initial feeling is that this header is likely too niche to include in the general list of constants. There are other header names that we've not added as well. But I realize that there isn't policy spelled out for how to decide what names to add.

I filed #573 to track creation of that policy.


pbmm2 align error

Hi,
quiver-run error issue.
I found uow*** folder under 4-polish/quiver-run/000**/, because aligned bam file was not generated.
I re-ran user_script.sh under uow***, but execution stopped with pbmm2 align error with comments below
Could not determine read input type(s). Please do not mix data types, such as BAM+FASTQ. File of files may only contain BAMs or datasets.
I do not understand why only this sample gives me an error.
(Actually, this sample was sequenced by Sequel II and I do not think this occurs an error.)
Do you have any Solutions??
Thank you

I updated pbmm2 and genomicConsensus. These are the latest.
pbmm2 works well, but variantCaller does not work... 😢
[Error Message]
Arrow: unsupported chemistries found: (S/P4-C2/5.0-8M)
Arrow: unsupported chemistries found: (S/P4-C2/5.0-8M)
Traceback (most recent call last):
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/pbcommand/cli/core.py", line 138, in _pacbio_main_runner
return_code = exe_main_func(*args, **kwargs)
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/main.py", line 340, in args_runner
return tr.main()
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/main.py", line 270, in main
self._configureAlgorithm(options, peekFile)
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/main.py", line 164, in _configureAlgorithm
self._algorithmConfiguration = self._algorithm.configure(options, alnFile)
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/arrow/arrow.py", line 233, in configure
die("Arrow: unsupported chemistries found: ({0})".format(", ".join(sorted(unsupp))))
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/utils.py", line 16, in die
raise DieException(msg)
DieException: Arrow: unsupported chemistries found: (S/P4-C2/5.0-8M)
[ERROR] Arrow: unsupported chemistries found: (S/P4-C2/5.0-8M)
Traceback (most recent call last):
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/pbcommand/cli/core.py", line 138, in _pacbio_main_runner
return_code = exe_main_func(*args, **kwargs)
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/main.py", line 340, in args_runner
return tr.main()
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/main.py", line 270, in main
self._configureAlgorithm(options, peekFile)
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/main.py", line 164, in _configureAlgorithm
self._algorithmConfiguration = self._algorithm.configure(options, alnFile)
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/arrow/arrow.py", line 233, in configure
die("Arrow: unsupported chemistries found: ({0})".format(", ".join(sorted(unsupp))))
File "/home/denovo/miniconda2/envs/pbasm/lib/python2.7/site-packages/GenomicConsensus/utils.py", line 16, in die
raise DieException(msg)
DieException: Arrow: unsupported chemistries found: (S/P4-C2/5.0-8M)
Arrow does not support Seqeul II reads??
Thank you

You need to use gcpp instead of GenomicConsensus. You'll have that automatically if you use a python3.7 environment. We no longer support python2.7 in Bioconda. Sorry!

Hi.
I am having the same issue - "Could not determine read input type(s). Please do not mix data types, such as BAM+FASTQ. File of files may only contain BAMs or datasets."
The version of pbmm2 1.1.0
The command:
pbmm2 align --log-level DEBUG --sort --alignment-threads 32 --preset SUBREAD --sample MNDY0206 --unmapped ../../input/ref/GRCh38.p12.genome.fa bam.fofn output.bam
The bam.fofn only contains bam files

m54106_180305_090504.subreads.bam
m54106_180305_191055.subreads.bam
m54106_180306_095808.subreads.bam
m54106_180306_200343.subreads.bam
m54106_180704_064123.subreads.bam
m54106_180704_165029.subreads.bam
m54106_180710_082246.subreads.bam
m54106_180710_183350.subreads.bam
m54107_180305_090413.subreads.bam
m54107_180305_191001.subreads.bam
m54107_180306_095813.subreads.bam
m54107_180306_200409.subreads.bam
m54107_180430_173338.subreads.bam
m54107_180502_045750.subreads.bam
m54107_180626_073517.subreads.bam
m54107_180626_174914.subreads.bam
m54107_180627_102459.subreads.bam
m54107_180627_203329.subreads.bam
m54107_180702_065016.subreads.bam
m54107_180702_170553.subreads.bam
m54107_180703_080930.subreads.bam
m54107_180703_182453.subreads.bam
m54107_180704_044013.subreads.bam
m54107_180704_145613.subreads.bam
m54107_180705_011214.subreads.bam
m54107_180705_112915.subreads.bam
m54107_180709_070406.subreads.bam
m54107_180709_172201.subreads.bam
m54107_180710_082455.subreads.bam
m54107_180710_184412.subreads.bam
m54107_180711_050825.subreads.bam
m54107_180711_152740.subreads.bam
m54107_180712_014716.subreads.bam
m54107_180712_120227.subreads.bam

Any idea how to solve this?


Types resolving to any across packages in monorepo using project references

Bug Report

🔎 Search Terms

TypeScript issue monorepo references
TypeScript issue monorepo types resolving to any
TypeScript issue types depth limit
TypeScript issue resolution limit
TypeScript issue references type any

🕗 Version & Regression Information

I have tested versions from 4.9.5 to 5.1.3, all presenting the same behaviour regarding this issue.

⏯ Playground Link

N/A.

💻 Code

NOTE
Unfortunately I have not been able to replicate this issue in a reproduction repository because I think it is related to type resolution limits of tsserver (so it depends on the size and complexity of the codebase) and I am not allowed to give access to the original repository. However, I will try to be as precise and linear as possible, providing all relevant information.
If there are any additional debugging steps that I can perform or any other information I can gather, I would be happy to do so.
ISSUE SUMMARY
We have a monorepo (~17 packages and ~1287 files) using Yarn Workspaces and Yarn PnP with TS Project references configured as per documentation.
Everything seems to work just fine, but for some reason, some types get resolved to any when consumed in other packages.

This is only happening when packages are not built (no types directory generated).
This is only happening in some packages, even if all packages are configured in the same way.
This is only happening for a particular type (see details below).
All packages imports get resolved correctly.
I suspect that the issue is only present in tsserver, since the project builds without errors using tsc --build.
@typescript-eslint/eslint-plugin is able to resolve the type correctly (I assume it uses tsc and not tsserver internally) (see test 2 below).
Error is shown both in WebStorm and in VSCode.
All references have been properly set (done automatically with a script and then manually checked multiple times).
There are no circular dependencies or other strange stuff.
Packages have been renamed for confidentiality reasons and non related/relevant data have been removed when possible.

PROJECT CONFIGURATION

 Root's File Structure
.
├── package.json
├── packages
│   ├── package-a
│   ├── package-b
│   ├── package-c
│   ├── package-d
│   ├── package-e
│   ├── package-f
│   ├── package-g
│   ├── package-h
│   ├── package-i
│   ├── package-j
│   ├── package-k
│   ├── package-l
│   ├── package-m
│   ├── package-n
│   ├── package-o
│   ├── package-p
│   ├── package-q
├── tsconfig.base.json
└── tsconfig.json

 Root's tsconfig.base.json
{
    "compilerOptions": {
        "baseUrl": "./",
        "paths": {
            "@scope/*": ["./packages/*"]
        },
        "target": "ESNext",
        "isolatedModules": true,
        "resolveJsonModule": true,
        "esModuleInterop": false,
        "allowJs": false,
        "checkJs": false,
        "strict": true,
        "noImplicitAny": true,
        "strictNullChecks": true,
        "allowUnreachableCode": false,
        "allowSyntheticDefaultImports": true,
        "forceConsistentCasingInFileNames": true,
        "useDefineForClassFields": true,
        "removeComments": false,
        "noEmitOnError": true,
        "declaration": true,
        "declarationMap": true,
        "emitDeclarationOnly": true
    }
}

 Root's tsconfig.json
{
    "files": [],
    "references": [
        {
            "path": "packages/package-a"
        },
        {
            "path": "packages/package-b"
        },
        {
            "path": "packages/package-c"
        },
        {
            "path": "packages/package-d"
        },
        {
            "path": "packages/package-e"
        },
        {
            "path": "packages/package-f"
        },
        {
            "path": "packages/package-g"
        },
        {
            "path": "packages/package-h"
        },
        {
            "path": "packages/package-i"
        },
        {
            "path": "packages/package-j"
        },
        {
            "path": "packages/package-k"
        },
        {
            "path": "packages/package-l"
        },
        {
            "path": "packages/package-m"
        },
        {
            "path": "packages/package-n"
        },
        {
            "path": "packages/package-o"
        },
        {
            "path": "packages/package-p"
        },
        {
            "path": "packages/package-q"
        }
    ]
}

 Package's File Structure
.
├── package.json
├── src
└── tsconfig.json

 Package's tsconfig.json
{
    "extends": "../../tsconfig.base.json",
    "compilerOptions": {
        "rootDir": "./src",
        "outDir": "./types",
        "composite": true,
        "incremental": true,
        "lib": ["ESNext", "DOM"],
        "module": "ESNext",
        "moduleResolution": "NodeNext",
        "jsx": "preserve"
    },
    "include": ["./src/**/*"],
    "references": [
        {
            "path": "../package-a"
        },
        {
            "path": "../package-g"
        },
        {
            "path": "../package-h"
        },
        {
            "path": "../package-c"
        },
        {
            "path": "../package-d"
        }
    ]
}

 Package's package.json
{
    "name": "@scope/package-f",
    "types": "./types/index.d.ts",
    "module": "./esm/index.js",
    "main": "./esm/index.js",
    "exports": {
        ".": {
            "types": "./types/index.d.ts",
            "import": "./esm/index.js",
            "default": "./esm/index.js"
        }
    },
    "dependencies": {
        "@scope/package-a": "workspace:*",
        "@scope/package-g": "workspace:*",
        "@scope/package-h": "workspace:*"
    },
    "devDependencies": {
        "@scope/package-c": "workspace:*",
        "@scope/package-d": "workspace:*"
    }
}

ISSUE DETAILS
The problematic type is declared in a certain package (package-g) and is applied to a wrapper of createUseStyles from react-jss.

 createUseStyles Declaration
import {getFileCallerDetails} from '@scope/package-b';
import type {Classes, Styles} from 'jss';
import {createUseStyles as _createUseStyles} from 'react-jss';
import type {ITheme} from '../../defines/theme.types';

type TStyles<TC extends string, TProps, TTheme> =
    | Styles<TC, TProps, TTheme>
    | ((theme: TTheme) => Styles<TC, TProps>);

type TUseStyles<TC extends string, TProps, TTheme> = (
    data?: TProps & {theme?: TTheme}
) => Classes<TC>;

function createUseStyles<
    TProps = unknown,
    TC extends string = string,
    TTheme = ITheme
>(styles: TStyles<TC, TProps, TTheme>): TUseStyles<TC, TProps, TTheme> {
    if (process.env.NODE_ENV === 'development') {
        const {componentName, packageName} = getFileCallerDetails();

        return _createUseStyles(styles, {
            name: `${packageName}-${componentName}`
        });
    }

    return _createUseStyles(styles);
}

export {createUseStyles};

Now, the type works perfectly fine when importing and using the function in most of the other packages:

But in some packages, this happens:

@scope/package-g is properly declared as a dependency for all packages in the same way.
@scope/package-g is imported and used in the same way in all packages.
There are no other significative differences between working and non-working packages.
I suspect that this is related to the overall complexity of the type (thus some kind of limitation), because the following modification in the declaration also makes the issue go away:

type TStyles<TC extends string, TProps, TTheme> =
    // | Styles<TC, TProps, TTheme>
    | ((theme: TTheme) => Styles<TC, TProps>);

INTERESTING TESTS
1
If I move the file containing the above error from its original position, to the root of the src directory of the package, the error disappears:

It only seems to work when placed just inside src, also for the other non-working packages.
2
I changed the type for breakpoint.s from number to null | boolean to make ESLint complain (@typescript-eslint/restrict-template-expressions), proving that it is correctly resolving the type. TypeScript still resolved it to any.

POTENTIAL WORKAROUND
I have been trying to figure this out by myself for around 10 days, so believe me I have researched and tried a lot.
This is the farthest I got:
If I change the paths configuration in the root's tsconfig.base.json file from this:
{
    "paths": {
        "@scope/*": ["./packages/*"]
    }
}

To this:
{
    "paths": {
        "@scope/*": ["./packages/*", "./packages/*/src"]
    }
}

The issue goes away and everything seems to work perfectly. IntelliSense and overall performance also seemed to be improved.

But, does this configuration make sense? What other issues could it provoke? The only issue I could think of is if packages are build in the wrong order (should not happen using tsc --build).
If a package gets built before one of its dependencies, a direct relative import will be generated in declaration files, which is obviously wrong. When done in the correct order, the first pattern of paths has priority (types directory can be found), and build is correct.
Wouldn't this workaround be ideal? I mean, does not it make the entire monorepo to be seen as a single source? So the IDE does not need need to build packages in the background?
In any case, right now, this workaround is triggering some errors:

TS6059: File '...' is not under 'rootDir' '...' .'rootDir' is expected to contain all source files.
TS6307: File '...' is not listed within the file list of project '...'. Projects must list all files or use an 'include' pattern. File is CommonJS module because '...' does not have field "type".

But I think those can be easily solved by changing rootDir config and having a separate TS config for building (with the correct rootDir).
POTENTIALLY RELATED ISSUES

https://github.com/microsoft/TypeScript/issues/30946
https://github.com/microsoft/TypeScript/issues/48728
https://github.com/microsoft/TypeScript/issues/26913
https://github.com/microsoft/TypeScript/issues/29511
https://github.com/microsoft/TypeScript/issues/32707
https://github.com/microsoft/TypeScript/issues/32573

Thanks @ernestostifano for the very detailed description. A few thoughts/questions:

Would you be able to give me read access to the repo where this is happening? Ultimately, that, or an equivalent repro, might be the only way I can determine if there’s actually a TS bug and figure out a real fix.
Is there a reason you don’t want to or can’t use yarn workspaces (symlinks to local packages in node_modules, or whatever equivalent Yarn PnP sets up) instead of compilerOptions.paths? Especially considering you’re using --moduleResolution nodenext and package.json exports, it’s highly recommended to set things up so that module resolution of your local packages works the way it will actually work in the runtime/bundler; i.e. through node_modules.
FYI, #54567 made --module esnext --moduleResolution nodenext, as your packages have, an error. You probably want to switch to either just --module nodenext or --module esnext --moduleResolution bundler, depending on where your packages are getting loaded. (I doubt this will affect the bug you were observing, just an off-topic observation.)
What does go-to-definition on createUseStyles do when you’re getting the error? Does it change when types are built?
Are you sure disableSourceOfProjectReferenceRedirect isn’t enabled anywhere?

From lots of trial and errors with extensive searches, this config helped my problem.
  "typeAcquisition": {
    "enable": true
  }

In the interest of housekeeping, I’m going to close this since I can’t reproduce the issue and haven’t received any follow-up info I could use to try to narrow down the problem. I really appreciate the significant effort given here to provide a lot of detail in lieu of a repro, but unfortunately this kind of issue is nearly impossible to diagnose even with TS Server logs, and definitely impossible without. If anyone is able to provide a repro, please file a new issue. Thanks!

I'm having the exact same problem. I can provide a repo.


koordlet: fix flaky tests

Ⅰ. Describe what this PR does

koordlet: Fix flaky tests in be_resource_collector_test.go. Fix flag parsing UTs which cannot run with go test -race.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/cc @zwzhang0107 @eahydra @jasonliu747 @hormes

/lgtm
/approve


[BUG] Line-wrapped links do not work

First, thanks for an awesome plugin! 🔥
Please confirm

[X] I am running the latest version of this plugin

Describe the bug
Following [[note links that include newlines]] does not work, whereas it works as expected for [external links](). Similarly, syntax highlighting does not work for such note links, while external links work just fine.
To Reproduce
Enter the following in a markdown file and make sure telekasten.nvim is loaded.
[[example link on one line]]

[[example link with a
newline]]

[example external link with a
newline](https://www.google.com)

Try to follow the links with the follow_link() Telekasten function; the first and third will work, but not the second (the Telescope picker won't even appear). This yields the following error message:
E5108: Error executing lua ...share/nvim/lazy/telescope.nvim/lua/telescope/pickers.lua:899: 'replacement string' item contains newlines
stack traceback:
        [C]: in function 'nvim_buf_set_lines'
        ...share/nvim/lazy/telescope.nvim/lua/telescope/pickers.lua:899: in function 'reset_prompt'
        ...share/nvim/lazy/telescope.nvim/lua/telescope/pickers.lua:741: in function 'set_prompt'
        ...share/nvim/lazy/telescope.nvim/lua/telescope/pickers.lua:433: in function 'find'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:1007: in function 'find_files_sorted'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:2167: in function 'picker'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:2210: in function 'callback'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:490: in function 'callback'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:218: in function 'check_dir_and_ask'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:469: in function 'create_note_from_template'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:2201: in function 'callback'
        ...
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:237: in function 'callback'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:218: in function 'check'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:236: in function 'callback'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:218: in function 'check'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:235: in function 'callback'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:218: in function 'check'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:234: in function 'global_dir_check'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:2085: in function 'selection'
        ...local/share/nvim/lazy/telekasten.nvim/lua/telekasten.lua:3082: in function 'panel'
        [string ":lua"]:1: in main chunk

Expected behavior
The example link should be followed when using the follow_link() Telekasten function, and should also be correctly syntax highlighted.
Screenshots

Operating system (please complete the following information):

OS: MacOS

Additional context
This is important to me because I always format all of my files to have a maximum width of 80 characters, which helps with readability and other stuff. The current functionality forces me into one of two solutions: (1) write my notes such that any internal link happens to land one of continuous line within the maximum line width, or (2) have links exceed the maximum line width. Alternative one adds additional overhead to writing links, since I now have to word the note such that links become formatted on a single line. Both alternatives makes automatic formatting with e.g. gq impossible.
I'm assuming it's something wrong with the [[internal links]], since [external links]() work fine?

Can you try adding
title = title:gsub("%s*\n", " ")

between lines 2122 and 2123 ?
https://github.com/renerocksai/telekasten.nvim/blob/d2b7c2c4d4727f31bb0676ed90e7ecdc8f67ae12/lua/telekasten.lua#L2118-L2124
just to make sure it works as expected before I push the fix ?

Mmmm indeed.

I really do not have time to go deeper on that and solve the syntax highlighting stuff. So this will be for a separate issue.
Making the function work on the second line requires fixing the taglincks.is_tag_or_link_at function which is significantly more complicated than simply replacing any end of line character by a space. We first need to go up any number of lines and detect if we are indeed in a link or not. I am not sure why we need such a complex function to do that tbh, so we must proceed with caution here.

Unfortunately I do not think I have much more time to work on this in the foreseeable future. If you are up to it, you can try fixing this yourself and I will happily review the PR.

Okay, shall I add a separate issue for that?
Alright, but why is the internal link not working while the external ones do? I assume that they share some kind of functionality between them? I'm not a plugin developer myself, so my intuition here can easily be wrong.

Not yet, we will do when the other part is fixed (maybe both will be fixed together, I am not familiar with the highlighting stuff)
External link is the else condition (-> default behavior). As the stuff under the cursor is not recognized as a link or a tag (taglinks.is_tag_or_link_at returns nil), then we end up here and directly go for what is inside parenthesis.
You can see this behavior yourself in the following example:

Lorem ipsum
[word1] word2 (should get yanked) lorem ipsum

Put the cursor anywhere before the ( ... )  and try follow_link. It should yank what is inside the parentheses in the default register (now that I think of it, it should reset the register afterward before trying to open the url)

Okay, turns out that the syntax highlighting issue was a very simple fix: the oneline setting had been used, and removing that from the link-related syntax fixed it; see #308.
I'll see if I can get something going for the link following-problem.

Awesome! Thank you very much for your contribution.


Write new example

I removed lib folder from example when adding generated files to git ignore

Great! Let me add a PR with a simple example boiler app


Viewing of Videos

Ability to watch lecture video (linked to youtube and Vimeo, external link and our own from our channel).
Viewing Portal
Connected to Links and categories in backend.

I've tested out the react-player module. Playing external videos on Youtube and Video works great.
Setting the loop prop to true makes the video start from the beginning once it ends. This works on Vimeo but doesn't seem to work on Youtube.
The controls prop is also a boolean that toggles native controls to the user. This works on Youtube but not on Vimeo however this is by design on Vimeo's end.
I've also tested the player with local video files. The local files are set relative to the path of the public folder where index.html currently is. Here are the formats that works from my findings:

.mp4 works
.ogv works
.webm works
.flv doesn't work

Currently, I don't think a PR is needed as we don't have any actual videos that need to present on Cassandra. I'm posting this here just confirm that react-player is quite good and fit our needs when they do arise.

I didn't test the style prop for adding inline styles to the root video element. We haven't decided on the overall look and design of the app yet so this seemed unnecessary.


Add banner on dbt docs site

Description & motivation
This sets up the Docusaurus announcementBar and adds additional customization to control the bar. The AnnouncementBar component is swizzled to add the following custom updates:

Wrap the entire announcement bar with the link
Add announcementBarLink & announcementBarActive properties to the config to provide additional control.

To-do before merge
Include any notes about things that need to happen before this PR is merged, e.g.:

[x] Confirm content is correct

Preview
https://deploy-preview-1543--docs-getdbt-com.netlify.app/

Thank you for answering my super basic questions!


Add ArrowStream source operator

Add the ArrowStream source operator to read data from an  ArrowArrayStream.
Fixed: https://github.com/facebookincubator/velox/issues/1254.

@mbasmanova This operator is used as the source node to fetch data from the arrow array stream. In this way, the arrow data after shuffle is sent to Velox for computing. It can also be feasible to implement it in the connector, we will take a look on that.

It is my understanding now that this is an operator that reads shuffle data in Arrow format. If that's the case, then it is fine as a separate operator. (An alternative could be to use the Exchange operator with a custom ExchangeSource.)
Let me read the PR. In the meantime, it would be nice to add a test.

It is my understanding now that this is an operator that reads shuffle data in Arrow format. If that's the case, then it is fine as a separate operator. (An alternative could be to use the Exchange operator with a custom ExchangeSource.)
Let me read the PR. In the meantime, it would be nice to add a test.

Thanks for your comment. Working on the unit test.

This PR is still needed. @zhejiangxiaomai

This PR is needed but not ready for view because the doc and unit test are not added.

Hi @mbasmanova @majetideepak, it has been a long time and sorry for the late response because we were on other tasks. This PR mainly supports an operation to read data from arrow array stream, and I fixed above comments including adding unit test and updating the doc.
Is it possible to reopen this PR, or do I need to open a new one for your review? My changes are still in this branch: https://github.com/rui-mo/velox/commits/wip_arrow_stream. Thanks for your help!

@rui-mo It should be possible to re-open the PR, but I see that "Reopen and comment" button is greyed out. Would you try updating the associated branch with the latest code? CC:@kgpai

@rui-mo It should be possible to re-open the PR, but I see that "Reopen and comment" button is greyed out. Would you try updating the associated branch with the latest code? CC:@kgpai

@mbasmanova Thanks for your advice. Updated the associated branch to the latest status, but the PR content did not change. I'm glad to open a new one if it's needed.

@rui-mo Let's open a new PR.

@mbasmanova Hi Masha, a new PR https://github.com/facebookincubator/velox/pull/3917 was opened to replace this one. Would you like to take a review? Thanks.

@rui-mo Thank you, Rui. I have a few things I need to work on today and tomorrow. I'll try to get to this PR early next week.

@rui-mo Thank you, Rui. I have a few things I need to work on today and tomorrow. I'll try to get to this PR early next week.

@mbasmanova Sure, thanks for your time!


Fixed a typo, a bug and allows it to work even if a file has been renamed (auto-update will break if not updated too)

I don't know what I'm doing but there it is

I don't know what other things there are that require this.
I don't even know if I should do the change differently to avoid breaking backwards compatibility
Like I said I don't know what I'm doing this is my first time contributing to something

Have to tested the changes?

yes

The new version requires everyone to change their existing code a little bit and it will crash if it's not done
Because now we have to be able to support an old and a new name

The new version requires everyone to change their existing code a little bit and it will crash if it's not done Because now we have to be able to support an old and a new name

we have to use the filename and filepath along with new and old.
Or we can simply use filename instead of old_filename and new_filename for new filename. This way, no need to change old code, and they can access new filename in the update.
If you have other solutions, discuss here.

Or we can simply use filename instead of old_filename and new_filename for new filename. This way, no need to change old code, and they can access new filename in the update.

If we do that it creates a file duplication bug if there is a renamed file
example for an automatic update code:
if we have
V0: old(1)
V1: new(12)
V2: new(15)
First we we update from V0 to V1 (Because V2 hasn't been released yet)
If the code has not been updated to use the new name so we have
V1: old(12)
and then we update from V1 to V2
the code will try to replace the file "new" which does not exist and will therefore create another so we have
V2: old(12) new(15)
I thought of two solutions
(I prefer this one)
An argument to set if we want to support name change and used new name  old name
If the argument is not specified it works as before and crashes if there is a name change as before
(I don't recommend this one)
We use name and old name
and if a file has been renamed we don't put anything in name to make the program crash (I don't think we can throw an error ourselves because we would have to detect if it uses name or old name)
I don't recommend because we can't tell them wat the error is and we have to hope they looks at the code

ok then, i am merging the changes. is there anything to add?

no that was all


web3 endpoint

Hi! Could you please provide and expample value of L2_WEB3_ENDPOINTS? Not clear what it is. Thx

You can get one on Infura, Alchemy, or QuickNode for free. It's the endpoint where the bot submits your transaction, which will later be broadcasted to blockchain validators/miners.


Update deployment.yaml

Added ClusterIp Port service

I think this is not right, it didn't pass the checks


script rewriting throws UnicodeDecodeError when it encounters binary file

I'm installing binary program directly to bin (with this CmakeLists.txt).
After upgrading from 0.2.1 to 0.3.1 I got this error:
  [100%] Built target trigger
  -- Install configuration: "Release"
  -- Installing: /tmp/tmp284d30cb/wheel/scripts/gemmi
  *** scikit-build-core 0.3.1 using CMake 3.26.3
  *** Configurating CMake...
  *** Building project with Unknown...
  *** Installing project into wheel...
  *** Making wheel...
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
      main()
    File "/usr/lib/python3/dist-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "/usr/lib/python3/dist-packages/pip/_vendor/pep517/in_process/_in_process.py", line 261, in build_wheel
      return _build_backend().build_wheel(wheel_directory, config_settings,
    File "/tmp/pip-build-env-9_hn868s/overlay/local/lib/python3.10/dist-packages/scikit_build_core/build/__init__.py", line 32, in build_wheel
      return _build_wheel_impl(
    File "/tmp/pip-build-env-9_hn868s/overlay/local/lib/python3.10/dist-packages/scikit_build_core/build/wheel.py", line 211, in _build_wheel_impl
      process_script_dir(wheel_dirs["scripts"])
    File "/tmp/pip-build-env-9_hn868s/overlay/local/lib/python3.10/dist-packages/scikit_build_core/build/_scripts.py", line 23, in process_script_dir
      first_line = next(file_iter)
    File "/usr/lib/python3.10/codecs.py", line 322, in decode
      (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcb in position 25: invalid continuation byte
  [end of output]

which I think is related to script rewriting in #254.

Yes, that needs to be protected. The first draft opened it in binary and I forgot that it would fail on binaries when I changed it to opening it with encoding.
This does mean we don’t support shabang rewriting on .pyz files. Not sure if anyone will be doing that, though, so protecting this is a good first step.


Your blockchain seems to be bottlenecked from the end-users VPN

I was happily using this software when suddenly it crashed due to a VPN exploitation! This is very bad. It's bottlenecking the application's blockchain. The software aimbot hacked the 4th dimension to alter reality and crashed my C++! Please help, my life is on the line.

This is a very serious issue and very high priority!

Please stop trolling. If you actually need help, please tell me. Otherwise,
this issue will be closed tomorrow.
On Sat, Apr 8, 2023, 12:55 PM bredcat999 @.***> wrote:

This is a very serious issue and very high priority!
—
Reply to this email directly, view it on GitHub
https://github.com/PPPDUD/M-SHELL/issues/2#issuecomment-1500932736, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZTWPZJHTXA5Y6LY35NE3PDXAGKAHANCNFSM6AAAAAAWXR2WUQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

okay

I do have a tip though: if you are going to include .exes, please bundle them as a zip file in releases.

They clog up the repo


Create documentation

This will include video tutorials, and will cover:

Google Form creation, best practices and downloading
Event separation, for trials where events are combined into one form
TrialManager usage

In progress. Closing as this issue is not a definitive tracker


Line chart Google doc appears to be protected

I created a new line chart, then visited it (after running fab app) on my local machine. This throws an error: KeyError: 'Error! Google returned a 403 error'
The command line when creating the chart also shows an error:
Creating spreadsheet...
Error creating spreadsheet (status code 404) with message Not Found

Pasting the graphic_config key into a google docs URL tells me to ask permission to see the document.

Good catch. Can you try now and let me know if it's fixed?

Looks good now. Thanks for the quick fix!


Send email when a new collaborator has been added to the project.

send the email to the newly added collaborator
send the email to other owners
email not sent to the person who added the collaborator

For https://github.com/pypa/warehouse/issues/1000

@Mariatta looks like tests are failing -- take a look?

Thanks! The tests are passing now. Please re-review when you have the chance.

Hi @Mariatta!  I tested this PR and it looks like the emails are being sent to the new collaborator, but not to the other owners.

Thanks @lgh2! With the latest commit (https://github.com/pypa/warehouse/pull/3155/commits/ca04e7c7f6368b175ed0805c1aff138f0fd61e46) the other owners should receive the email notification now.

Thanks @Mariatta!

Thanks for the patience in reviewing this :)


Add an exercise list to the course details page

Checklist

[ ] I tested all changes and all related features with different users (student, tutor, editor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Client: I followed the coding and design guidelines.
[ ] Client: I added multiple integration tests (Jest) related to the features (with a high test coverage)
[ ] Client: I added authorities to all new routes and check the course groups for displaying navigation elements (links, buttons)
[ ] Client: I documented the TypeScript code using JSDoc style.
[x] Client: I added multiple screenshots/screencasts of my UI changes
[ ] Client: I translated all the newly inserted strings into English and German using neutral, gender-inclusive language

Description
Extends the course detail page to include a list of exercises for quick navigation.
Steps for Testing
Open the course details page of a course and check the exercises list. It should display all exercises, be sortable, and show correct buttons.
Test Coverage
Screenshots

Focusing on the exam mode fixes at the moment.


Fixed material colors for Ackermann SDF files

Signed-off-by: Jenn Nguyen<EMAIL_ADDRESS>
🦟 Bug fix
Summary
There were several Ackermann SDF files that had invalid material color components (e.g., <diffuse>11 11 11</diffuse>). With the new changes from https://github.com/osrf/sdformat/pull/519, this will fail. These invalid color components have been replaced with 1 1 1.
Checklist

[X] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Our Windows CI has a long queue right now. Since this shouldn't affect Windows, I cancelled that build. Merging with the current results!


Resolve issue with legends not expanding by default

Legends expand to open automatically when the map is loaded, if stated in the map configuration.
DanB: Is this still an issue? Is there an existing RAMP3 issue to link?

Hey team! Please add your planning poker estimate with ZenHub @JahidAhmed @RyanCoulsonCA @yileifeng

This is still a problem and is a bug within RAMP3. I can reproduce this using the index-many.html sample page in the RAMP3 repo using the StoryRAMP config files. I've been doing a bunch of investigating surrounding this issue and it appears to be related to the symbology animation service (it doesn't occur anymore if I remove the animation part of the code, but that also prevents symbology from opening at all so that's not a solution for this).
The issue doesn't pop up every time which means we could also be dealing with a race condition somewhere, but it's hard to track down exactly where that could be occurring. I'm still looking into this issue and will post more updates as I find them.


Fix spaces between "AVAILABLE" AND "MAX PRIVACY" tabs

Current implementation

Design: https://zpl.io/VqWLnGl and https://zpl.io/25LYNQ3

Please make changing tab animation smoother
RPReplay_Final1609929284.MP4.zip

don't fixed

don't fixed

№ 2 not fixed.
Please make changing tab animation smoother (between Available and Max privacy)
https://user-images.githubusercontent.com/68247034/120313052-2f7c3a00-c2e2-11eb-9adb-7cdc520f1c64.MP4

irrelevant


Allow for resolver extension

Allow for extension of resolver methods by moving everything into an extendable class.
While my dev environment was hosed and was waiting for Python and all my tooling to compile/install, I wrote up a nicer implementation of lazy classes for overriding with a setting. The main benefit here is that we only need two classes to allow for override, and they can exist in the same source file. We can also automate the logic around where to pull the override setting from. There were several issues that I hit while trying to expose the class methods as module functions, this solved those issues in a much cleaner way. Use of CLASS_OVERRIDES is for the future, so we can have an explicit list of the Classes overridden instead.
The diff on this looks awful, so I'll enumerate what was actually changed, besides moving everything into a class:

_get_canonical_project was broken out into a method
_get_project_subdomain was broken out into a method
Everything was made to reference a class instance with self

No logic changed on the resolver methods, things were just moved and broken out, cleaned up for linting.

WIP here too, have some changes inbound

Okay, tests fixed, ready for review. Note updated ticket description.

Seems like if USE_SUBDOMAIN is set, we'd not want to serve from /docs/ URL.. what is the reasoning behind that change?

Ah, I see in the tests -- we were serving from the subdomain, but with the /docs/ URL -- in general I think we should bias against any use of the /docs/ URL, only using it when necessary in dev -- and we should be able to get away from that with a remote wildcard domain that points at <IP_ADDRESS>.

Looks good overall -- mainly just have nitpicks about resolution, but the current implementation is good for now.

Yeah, reason behind the change was that we don't want to serve subdomain docs from PRODUCTION_DOMAIN under any circumstances. I'm not sure it makes sense to drop USE_SUBDOMAIN for if PUBLIC_DOMAIN is not None: sort of logic, as that's not horribly clear either. It seems the most correct thing is to have USE_SUBDOMAIN be explicitly dependant on PUBLIC_DOMAIN -- possibly to the point we throw an exception?
With changes to how we view subdomain hosting, I think it makes sense to require both. It may push independent installs to use /docs/ but I don't think this does much else to enable serving from /docs/


Fastcode Challenge

Let's use fastcode.org to promote the programming competition. Right now the important pages are these two:

program to win
PPoPP programming competition

Hi @syhlalala looks good! I am merging. I did a quick test and found one broken link. From the main contest page to the github page for the LLM track, that link goes to a 404 error on GitHub. Maybe the repo is private?


models: Account for UPLOADING runs in sync projects

We have a bug where a synchronous project can have CI runs
mis-scheduled. Here's the simplest flow:

Two builds (one run each) builds for project get queued, 1 and 2.
Build 1's run's goes into UPLOADING
A worker check's in for work and gets assigned Build 2's run

The scheduler needs to filter on uploading as well as running.
Signed-off-by: Andy Doan<EMAIL_ADDRESS>

@mike-scott - FYI