[Package Issue]: Microsoft.ServiceFabricSDK - winget configure yields "The group or resource is not in the correct state"

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
When winget configure, process fails to install Microsoft.ServiceFabricSDK:
Apply :: WinGetPackage [installServiceFabricSDK]
  The configuration unit failed while attempting to apply the desired state.
WinGetPackage Failed installing Microsoft.ServiceFabricSDK. InstallStatus 'DownloadError' InstallerErrorCode '0' ExtendedError '-1978334960'
<See the log file for additional details>
Some of the configuration was not applied successfully.

with log
[FAIL] C:\__w\1\s\external\pkg\src\AppInstallerCLICore\ExecutionContext.cpp(377)\WindowsPackageManager.dll!00007FFAF618E3D2: (caller: 00007FFAF6211BCE) Exception(64) tid(17dc) 8007139F The group or resource is not in the correct state to perform the requested operation.

Steps to reproduce
configuration.dsc.yaml:
# yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.2
properties:
  assertions:
    - resource: Microsoft.Windows.Developer/OsVersion
      directives:
        description: Verify min OS version requirement
        allowPrerelease: true
      settings:
        MinVersion: "10.0.22631"
  resources:
    - resource: Microsoft.Windows.Developer/DeveloperMode
      directives:
        description: Enable Developer Mode
        allowPrerelease: true
      settings:
        Ensure: Present
    - resource: Microsoft.WinGet.DSC/WinGetPackage
      directives:
        description: Install Service Fabric SDK
        allowPrerelease: true
      id: installServiceFabricSDK
      settings:
        id: Microsoft.ServiceFabricSDK
        source: winget
        version: "7.0.1949.9590"
        installMode: Default
  configurationVersion: "0.2.0"

Run as administrator:
winget configure -f .\configuration.dsc.yaml

Actual behavior
winget configure output:
Assert :: OsVersion
  Verify min OS version requirement
  Module: Microsoft.Windows.Developer by Microsoft Corporation [Local]
    DSC Resource for Windows
  Settings:
    MinVersion: 10.0.22631
Apply :: DeveloperMode
  Enable Developer Mode
  Module: Microsoft.Windows.Developer by Microsoft Corporation [Local]
    DSC Resource for Windows
  Settings:
    Ensure: Present
Apply :: WinGetPackage [installServiceFabricSDK]
  Install Service Fabric SDK
  Module: Microsoft.WinGet.DSC by Microsoft Corporation [Local]
    https://github.com/microsoft/winget-cli
    PowerShell Module with DSC resources related to WinGet configurations
  Settings:
    version: 7.0.1949.9590
    id: Microsoft.ServiceFabricSDK
    installMode: Default
    source: winget
You are responsible for understanding the configuration settings you are choosing to execute. Microsoft is not responsible for the configuration file you have authored or imported. This configuration may change settings in Windows, install software, change software settings (including security settings), and accept user agreements to third-party packages and services on your behalf.  By running this configuration file, you acknowledge that you understand and agree to these resources and settings. Any applications installed are licensed to you by their owners. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages or services.
Have you reviewed the configuration and would you like to proceed applying it to the system?
[Y] Yes  [N] No: yes
Assert :: OsVersion
  Configuration successfully applied.
Apply :: DeveloperMode
  Configuration successfully applied.
Apply :: WinGetPackage [installServiceFabricSDK]
  The configuration unit failed while attempting to apply the desired state.
WinGetPackage Failed installing Microsoft.ServiceFabricSDK. InstallStatus 'DownloadError' InstallerErrorCode '0' ExtendedError '-1978334960'
<See the log file for additional details>
Some of the configuration was not applied successfully.

WinGetCOM log:
[FAIL] C:\__w\1\s\external\pkg\src\AppInstallerCLICore\ExecutionContext.cpp(377)\WindowsPackageManager.dll!00007FFAF618E3D2: (caller: 00007FFAF6211BCE) Exception(86) tid(17dc) 8007139F The group or resource is not in the correct state to perform the requested operation.

Expected behavior
Installs successfully.
Environment
Windows Package Manager v1.6.3482
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3155
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.3482.0

Screenshots and Logs
Full WinGetCOM log:
2024-03-08 13:25:11.009 [CORE] Passed in Correlation Vector Json is invalid: ; Error: * Line 1, Column 1
  Syntax error: value, object or array expected.

2024-03-08 13:25:11.009 [CORE] WinGet, version [1.6.3482], activity [{DEB14D76-C925-4127-9309-B5500972D386}]
2024-03-08 13:25:11.009 [CORE] OS: Windows.Desktop v10.0.22631.3155
2024-03-08 13:25:11.009 [CORE] Command line Args: C:\Users\user\AppData\Local\Microsoft\WindowsApps\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\WindowsPackageManagerServer.exe --manualActivation
2024-03-08 13:25:11.009 [CORE] Package: Microsoft.DesktopAppInstaller v1.21.3482.0
2024-03-08 13:25:11.009 [CORE] IsCOMCall:1; Caller: Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
2024-03-08 13:25:11.013 [CLI ] Executing command: download
2024-03-08 13:25:11.013 [SQL ] Opening SQLite connection #277: ':memory:' [6, 0]
2024-03-08 13:25:11.019 [REPO] Opening SQLite Index for ReadWrite at 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Microsoft.Winget.Source_8wekyb3d8bbwe\installed.db'
2024-03-08 13:25:11.019 [SQL ] Opening SQLite connection #278: 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Microsoft.Winget.Source_8wekyb3d8bbwe\installed.db' [2, 0]
2024-03-08 13:25:11.020 [REPO] Opened SQLite Index with version [1.6], last write [2024-03-08 13:04:21.000]
2024-03-08 13:25:11.040 [REPO] Finding installed package from available package using system reference search: Query:[none] Include:ProductCode='{0f770e99-3916-4b0c-8f9b-83822826bcbf}'[Exact] Include:ProductCode='{282975d8-55fe-4991-bbbb-06a72581ce58}'[Exact] Include:ProductCode='{295d1583-fdb9-414b-a4c8-da539362a26b}'[Exact] Include:ProductCode='{2aaf1df0-eb13-4099-9992-962bb4e596d1}'[Exact] Include:ProductCode='{2c673fb6-3e65-4751-965d-33d30b68a8a6}'[Exact] Include:ProductCode='{2d507699-404c-4c8b-a54a-38e352f32cdd}'[Exact] Include:ProductCode='{33628a12-6787-4b9f-95a1-92449f69fae0}'[Exact] Include:ProductCode='{3746f21b-c990-4045-bb33-1cf98cff7a68}'[Exact] Include:ProductCode='{40d3fee2-b257-46c2-bdc0-cb1088d97327}'[Exact] Include:ProductCode='{43d1ce82-6f55-4860-a938-20e5deb28b98}'[Exact] Include:ProductCode='{4b2f3795-f407-415e-88d5-8c8ab322909d}'[Exact] Include:ProductCode='{53f1dc9d-ed94-4650-a079-129785ce7905}'[Exact] Include:ProductCode='{57a73df6-4ba9-4c1d-bbbb-517289ff6c13}'[Exact] Include:ProductCode='{5c6cccca-61ec-4667-a8d9-e133a59a5a73}'[Exact] Include:ProductCode='{69becc62-c3d6-4307-9fc5-738d92cdf886}'[Exact] Include:ProductCode='{71af7464-a4a9-4c71-b645-bef3577171be}'[Exact] Include:ProductCode='{7c829c52-b42c-4e7d-8078-6d2bf6235dab}'[Exact] Include:ProductCode='{7d607fb4-7e28-4c7a-a92f-3fcdaf555faf}'[Exact] Include:ProductCode='{855e31d2-9031-46e1-b06d-c9d7777deefb}'[Exact] Include:ProductCode='{9f7f52eb-dcd8-47d7-a48e-c1dc5f31fbca}'[Exact] Include:ProductCode='{ac8ae441-cfc2-41f2-bbca-7b6668740f8d}'[Exact] Include:ProductCode='{b8e12890-118d-4721-8e54-05d978086712}'[Exact] Include:ProductCode='{c2dfe55a-4c5a-4641-8158-8f0d7aec1c2d}'[Exact] Include:ProductCode='{c649ede4-f16a-4486-a117-dcc2f2a35165}'[Exact] Include:ProductCode='{d4cecf3b-b68f-4995-8840-52ea0fab646e}'[Exact] Include:ProductCode='{d992c12e-cab2-426f-bde3-fb8c53950b0d}'[Exact] Include:ProductCode='{fa7f6d52-f85e-48ef-8f56-a37268aa5772}'[Exact] Include:ProductCode='{fd9b6070-d13e-45dc-819b-41806bf45b6b}'[Exact] Include:NormalizedNameAndPublisher='microsoftvisualc2015redistributable'+'microsoft'[Exact] Include:NormalizedNameAndPublisher='microsoftvisualc2015redistributable(x64)'+'microsoft'[Exact] Include:NormalizedNameAndPublisher='microsoftvisualc2017redistributable'+'microsoft'[Exact] Include:NormalizedNameAndPublisher='microsoftvisualc2017redistributable(x64)'+'microsoft'[Exact] Include:NormalizedNameAndPublisher='microsoftvisualcredistributable'+'microsoft'[Exact] Include:NormalizedNameAndPublisher='microsoftvisualcredistributable(x64)'+'microsoft'[Exact]
2024-03-08 13:25:11.050 [REPO] Opening pinning index
2024-03-08 13:25:11.051 [REPO] Opening existing pinning index
2024-03-08 13:25:11.051 [REPO] Opening SQLite Index for ReadWrite at 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\pinning.db'
2024-03-08 13:25:11.051 [SQL ] Opening SQLite connection #279: 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\pinning.db' [2, 0]
2024-03-08 13:25:11.052 [REPO] Opened Pinning Index with version [1.0], last write [2024-03-08 12:20:05.000]
2024-03-08 13:25:11.054 [REPO] Finding installed package from tracking package using system reference search: Query:[none] Include:NormalizedNameAndPublisher='microsoftazureservicefabric'+'microsoft'[Exact]
2024-03-08 13:25:11.062 [REPO] Finding installed package from available package using system reference search: Query:[none] Include:NormalizedNameAndPublisher='microsoftazureservicefabric'+'microsoft'[Exact]
2024-03-08 13:25:11.067 [REPO] Opening pinning index
2024-03-08 13:25:11.067 [REPO] Opening existing pinning index
2024-03-08 13:25:11.067 [REPO] Opening SQLite Index for ReadWrite at 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\pinning.db'
2024-03-08 13:25:11.067 [SQL ] Opening SQLite connection #280: 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\pinning.db' [2, 0]
2024-03-08 13:25:11.068 [REPO] Opened Pinning Index with version [1.0], last write [2024-03-08 12:20:05.000]
2024-03-08 13:25:11.069 [REPO] Downloading manifest
2024-03-08 13:25:11.069 [CORE] WinINet downloading from url: https://cdn.winget.microsoft.com/cache/manifests/m/Microsoft/ServiceFabricRuntime/10.0.1949.9590/77be
2024-03-08 13:25:11.070 [CORE] Download hash: ec8ec36bda9340de68170d908c32c525636c7163bc847535b68d7822cc11bef4
2024-03-08 13:25:11.070 [CORE] Download completed.
2024-03-08 13:25:11.071 [CLI ] Manifest fields: Name [Microsoft Azure Service Fabric], Version [10.0.1949.9590]
2024-03-08 13:25:11.071 [CLI ] Package agreements accepted by CLI flag
2024-03-08 13:25:11.081 [CLI ] Generated temp download path: C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\48e63b247272e996d6bda31e61af1cf9aec13bd155a586f01bc0507b72e8149f
2024-03-08 13:25:11.082 [CORE] Downloading to path: C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\48e63b247272e996d6bda31e61af1cf9aec13bd155a586f01bc0507b72e8149f
2024-03-08 13:25:11.082 [CORE] DeliveryOptimization downloading from url: https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabric.10.0.1949.9590.exe
2024-03-08 13:25:13.015 [CORE] Download completed.
2024-03-08 13:25:13.452 [CORE] Started applying motw to C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\48e63b247272e996d6bda31e61af1cf9aec13bd155a586f01bc0507b72e8149f with zone: 3
2024-03-08 13:25:13.454 [CORE] Finished applying motw
2024-03-08 13:25:13.454 [CLI ] Installer hash verified
2024-03-08 13:25:13.454 [CORE] Started applying motw to C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\48e63b247272e996d6bda31e61af1cf9aec13bd155a586f01bc0507b72e8149f with zone: 2
2024-03-08 13:25:13.460 [CORE] Finished applying motw
2024-03-08 13:25:13.461 [CLI ] Successfully renamed downloaded installer. Path: C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\MicrosoftServiceFabric.10.0.1949.9590.exe
2024-03-08 13:25:13.461 [REPO] Creating new SQLite Index with version [Latest] at ':memory:'
2024-03-08 13:25:13.461 [SQL ] Opening SQLite connection #281: ':memory:' [6, 0]
2024-03-08 13:25:13.466 [REPO] Reading MSI UpgradeCodes
2024-03-08 13:25:13.534 [REPO] Reading MSI UpgradeCodes
2024-03-08 13:25:13.673 [CLI ] Installer args: /quiet /AcceptEULA
2024-03-08 13:25:13.673 [CLI ] Starting: 'C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\MicrosoftServiceFabric.10.0.1949.9590.exe' with arguments '/quiet /AcceptEULA'
2024-03-08 13:25:44.808 [REPO] Creating new SQLite Index with version [Latest] at ':memory:'
2024-03-08 13:25:44.808 [SQL ] Opening SQLite connection #282: ':memory:' [6, 0]
2024-03-08 13:25:44.814 [REPO] Reading MSI UpgradeCodes
2024-03-08 13:25:44.886 [REPO] Reading MSI UpgradeCodes
2024-03-08 13:25:44.917 [CLI ] During package install, 0 changes to ARP were observed, 0 matches were found for the package, and 0 packages were in both
2024-03-08 13:25:44.917 [CLI ] No single entry was determined to be associated with the package
2024-03-08 13:25:44.925 [REPO] Opening SQLite Index for ReadWrite at 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Microsoft.Winget.Source_8wekyb3d8bbwe\installed.db'
2024-03-08 13:25:44.925 [SQL ] Opening SQLite connection #283: 'C:\Users\user\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Microsoft.Winget.Source_8wekyb3d8bbwe\installed.db' [2, 0]
2024-03-08 13:25:44.926 [REPO] Opened SQLite Index with version [1.6], last write [2024-03-08 13:04:21.000]
2024-03-08 13:25:44.968 [CLI ] Removing installer: C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricRuntime.10.0.1949.9590\MicrosoftServiceFabric.10.0.1949.9590.exe
2024-03-08 13:25:44.985 [CLI ] Found existing installer file at 'C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricSDK.7.0.1949.9590\MicrosoftServiceFabricSDK.7.0.1949.msi'. Verifying file hash.
2024-03-08 13:25:45.064 [CLI ] Existing installer file hash matches. Will use existing installer.
2024-03-08 13:25:45.064 [CLI ] Installer hash verified
2024-03-08 13:25:45.064 [CORE] Started applying motw to C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.ServiceFabricSDK.7.0.1949.9590\MicrosoftServiceFabricSDK.7.0.1949.msi with zone: 2
2024-03-08 13:25:45.066 [CORE] Finished applying motw
2024-03-08 13:25:45.066 [CLI ] Executing command: install
2024-03-08 13:25:45.066 [FAIL] C:\__w\1\s\external\pkg\src\AppInstallerCLICore\ExecutionContext.cpp(377)\WindowsPackageManager.dll!00007FFAF618E3D2: (caller: 00007FFAF6211BCE) Exception(64) tid(17dc) 8007139F The group or resource is not in the correct state to perform the requested operation.

    Msg:[Reporting ExecutionStage to an earlier Stage without allowBackward as true]

2024-03-08 13:25:45.066 [CLI ] Caught wil::ResultException: C:\__w\1\s\external\pkg\src\AppInstallerCLICore\ExecutionContext.cpp(377)\WindowsPackageManager.dll!00007FFAF618E3D2: (caller: 00007FFAF6211BCE) Exception(64) tid(17dc) 8007139F The group or resource is not in the correct state to perform the requested operation.

    Msg:[Reporting ExecutionStage to an earlier Stage without allowBackward as true]

2024-03-08 13:25:45.068 [CLI ] Successfully refreshed process PATH environment variable.
2024-03-08 13:25:45.068 [CLI ] Terminating context: 0x8a150110 at C:\__w\1\s\external\pkg\src\AppInstallerCLICore\Workflows\InstallFlow.cpp:2e1

@cthlo - Does this same error occur when using the latest version of the client (1.7.10582)?

@cthlo - Does this same error occur when using the latest version of the client (1.7.10582)?

@Trenly Yes, unfortunately:
2024-03-10 13:40:24.890 [FAIL] C:\__w\1\s\external\pkg\src\AppInstallerCLICore\ExecutionContext.cpp(432)\WindowsPackageManager.dll!00007FFE434632C2: (caller: 00007FFE434F4311) Exception(12) tid(29a8) 8007139F The group or resource is not in the correct state to perform the requested operation.

(Updated description)


Specify Fact in argv

This commit enables the ability to specify a fact on the command-line without
the need to format it.

Actually, I'm going to close this one for now. I don't think this works with arrays/indexed facts.


Undefined not accepted

Hello, I am still seeing this regression with the current version of change-case: https://github.com/blakeembrey/change-case/issues/69.
Repro: https://repl.it/@cloverb/PlaintiveVacantCryptocurrency.
Is this going to be fixed or do you intend it to be a breaking change?

It was a breaking change, hence the major version bump.

The issue you linked to also said it was intentional, that was just about it missing from release notes.


SPT with massive neutrinos

This PR implements massive neutrinos in the SPT computations necessary to compute the reaction.
The method used to implement massive neutrinos in SPT follows Section 2.3 of arXiv:1902.10692 -- first the 1-loop terms are rewritten to take P_L(k, z) as input instead of P_L(k, 0); secondly the effect of massive neutrinos is only included in P_L, such that the PT kernels are unchanged.
Unless we want to change the input from P_L(k, 0) to P_L(k, z) throughout, it would be good to add some sort of flag for massive neutrinos that switches the code to use these new SPT functions and reminds the user to supply P_L(k, z) instead of (or as well as) P_L(k, 0).
Currently, the implementation here is for density-density terms only, but it is easy to apply the same method to density-velocity and velocity-velocity terms.

@nebblu I'm not sure where to place flags to switch on massive neutrino modifications. With massive neutrinos turned on, do we want users to supply a) only P_L^{MG+M_nu}(k,z); or b) both P_L^{MG+M_nu}(k,z) and P_L^{LCDM}(k,0)?

@billwright93 since @nebblu added your commits to SPT and SpecialFunctions in #10 (and he has also requested some changes here) I will concentrate on reviewing #10 only so there is no confusion.


Merge GraphQL support efforts

Currently we have your amaring client as generator and github.com/FSProjecrs/FSharp.Data.GraphQL as server and type provider.
Maybe it worse to merge efforts and integrate both projects together?

Hi there @xperiandri,
How do you imagine merging the efforts? To me, Snowflaqe is pretty much a standalone project for consuming GraphQL endpoints regardless of a specific backend type (FSharp.Data.GraphQL or otherwise).
Would be happy to accept PRs / contributions to Snowflaqe directly :wink:

I suppose that your code can be reused in GraphQL client type provider

That won't work. The code used here generates records and union types which type providers ironically don't support. Not to mention making the type provider compatible with Fable is a huge pain in the back, compared to the situation now where things just work out of the box


The usernames and accounts are not updated - what should I do?

I have written something else in the username and accounts files and saved it but it is not updated in the bot. The bot uses the example usernames and accounts.
What should I do?
Except this the tool is great

you ever figure it out @MaxOder


Report of missing monthly updates

@chrisjwood16 has asked for someone to investigate a report from an OpenPrescribing subscriber that she hasn't been getting monthly updates recently. Please could you follow this up?
Originally reported in Slack.

Replied here:
https://bennettoxford.slack.com/archives/C051A4P27GE/p1707154930707459


Update Japanese translation

Coverage remained the same at 40.123% when pulling 6b5ce99910431eb9a6fc630115605b05b45da476 on MMP0:patch-37 into 7264ab0d0a016d9d791c3baec9d9e9f9f0eaf844 on NyaaPantsu:dev.


Support STI or Namespaced models.

Can you add a description or screenshots or where its going wrong or any info related  to this so I can take a look?

@rishirajkumar97 It's awaiting implementation. I have a branch which has a small POC for the implementation but never got around to test it.
Currently due to the fact that methods can't have symbols like colons or slashes, I was not clear of w
The basic idea would be something similar to the resources method that is used in routes. It has an option called module which is used to namespace a controller. Here we can add a similar option which can be prepended to the class and then constantised.
You can check it out if you feel like it!


Make the project suitable for VSCode PDE.

can you share some background about the purpose of this PR?

Use javaConfig.json instead for PDE development. This name is temporarily.

test this please


:memo: Added documentation for the option module.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tiles do not fill canvas after rotation

Clone this repo and serve it via HTTP server (e.g. ecstatic, python -m SimpleHTTPServer).
Visit the page and enter the following snippets in console.
These are exposed to window:

viewer
viewport
tiledImage

Fail case
viewport.zoomTo(tiledImage.imageToViewportZoom(2.0))
// wait for 'view-updated'
viewport.setRotation(0)
// wait for 'view-updated'
viewport.setRotation(44)

The tiles do not fill canvas these operations (the white canvas background  can be seen).

Resizing the window will fix the issue, and subsequent calls to rotation will not trigger the issue.
OSD 2.1.0 does not have this issue (change the <script> in index.html).
Success case
Single paste and execute, without waiting for view-updated
viewport.zoomTo(tiledImage.imageToViewportZoom(2.0))
viewport.setRotation(0)
viewport.setRotation(44)

Success case
Without setRotation(0)
viewport.zoomTo(tiledImage.imageToViewportZoom(2.0))
// wait for 'view-updated'
viewport.setRotation(44)

Good catch and thanks for the detailed bug report. I suspect a timing error when creating (or extending) the sketch canvas here: https://github.com/openseadragon/openseadragon/blob/master/src/drawer.js#L319-L339
Would you be up to trace that down?

Verified the fix.
Actually I'm also skipping setRotation(0) in my app as a hotfix.

@leesei Thank you for verifying!


diff_transformer.py is not available inside the directry it referenced

from fairseq.models.text_to_speech.diff_transformer import (
ModuleNotFoundError: No module named 'fairseq.models.text_to_speech.diff_transformer'
While trying to run the code getting above module not found error (diff_transformer) form where oi imports two classes     DiffusionTransformerModel and base_s2st_transformer_encoder_architecture .
After inspection i found that this   diff_transformer.y is not present in the dir, i also  checked in fairseq liberary also not present there.
Please update this file in the repository or provide any source form where i can ge that python file.
Thank you.

@mahendraphd  Thanks for spotting the issue. I previously removed that file because it is not actually used, but apparantly the argument processing requires this outdated file. The file is now pushed to the repo and you can find in this commit: https://github.com/steventan0110/DiffNorm/commit/f7e9426147a78132549f5c640cf247cf7e45dcca


bug: on Login Page, Phone number login displays email suggestions and blocks login without an email

Describe the bug
Login form should allow users to sign in using either their phone number or email. However, when a phone number is entered, the form still displays email suggestions like "9090900904@gmail.com," and prevents login without entering an email. I have to disable these email suggestions when a valid phone number is detected.
To Reproduce
Users should be able to log in using either an email or a phone number.
When a phone number (e.g., "9090900904") is entered, no email suggestions should appear, and the form should process the login correctly.
Expected behavior
Login using phone number also
Actual Behavior
When entering a phone number, the form incorrectly displays email suggestions, such as<EMAIL_ADDRESS>The login attempt is blocked, as it expects an email instead of a phone number.
Steps to Reproduce
Implement the login form with fields for email and password.
Enter a valid 10-digit phone number into the email field.
Observe that email suggestions are generated (e.g., "9090900904@gmail.com").
Try to log in with the phone number — it fails without entering a valid email address.
Screenshots or GIFs

Info (please complete the following information):

Browser [e.g. chrome, safari, brave]

Additional context
Add any other context about the problem here.

Just added the Solution for this , if that's correct please accept my pull request

As of now login with phone is not  implemented bcs i dont think its needed and changing the suggestion is not a solution u cannot enter phone no. in a email field

I can’t login with my phone number , i have created my account using phone
number🙂
On Sat, 14 Sep 2024 at 10:45 AM, Anshu Kumar Singh @.***>
wrote:

As of now login with phone is not implemented bcs i dont think its needed
and changing the suggestion is not a solution u cannot enter phone no. in a
email field
—
Reply to this email directly, view it on GitHub
https://github.com/code100x/cms/issues/1211#issuecomment-2350843122, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHHHE3ILQLNJN7Z5GPVZGDZWPA6BAVCNFSM6AAAAABOGASHZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQHA2DGMJSGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Changing suggestions will help because whenever you are writing phone
number you don’t need suggestions
On Sat, 14 Sep 2024 at 1:09 PM, Pranav Ahuja @.***>
wrote:

I can’t login with my phone number , i have created my account using phone
number🙂
On Sat, 14 Sep 2024 at 10:45 AM, Anshu Kumar Singh <
@.***> wrote:

As of now login with phone is not implemented bcs i dont think its needed
and changing the suggestion is not a solution u cannot enter phone no. in a
email field
—
Reply to this email directly, view it on GitHub
https://github.com/code100x/cms/issues/1211#issuecomment-2350843122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHHHE3ILQLNJN7Z5GPVZGDZWPA6BAVCNFSM6AAAAABOGASHZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQHA2DGMJSGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

So can we add a feature to login using phone number?

Just remove the suggestions area it is simple, then it does not matter whether we are using a phone number or an email and it is very much hectic to see the suggestions, if a user comes to a particular website and sees this he/ she will not be happy with this


Show console output for custom test tasks

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan


cbi.js: dynlist and password input initialized more than once

The issue was observed on luci-app-shadowsocks-libev, but it's likely a regression during code refactor and can also affect other components.
The 1st issue being that every dynlist was initialised 3 times on "Redir Rules" tab.  This was caused by the fact that there are there cbi_init() call in the generated html.  The other two are triggered by filebrowser.

The 2nd issue being that it seems for every "o.password = true" field, there are two dom input elements present.  One generated directly in the html response.  The other initialised by js code.  The effect can be observed on the "Remote Servers" tab.  Both are visible with one of them run far away from the main view.

I understand.  Previously browser autocomplete can indeed cause trouble.  But it seems when embedded in a table, the added input element will be visible, despite the css code left: -1000px

Another minor undesirable change is that previously the Reveal/hide password button stick to the input element on the same row, not wrapping to the next line.

Will look into this asap.


feat: Add adaptors for ollama and openai

Adding adaptors here, as per https://github.com/huggingface/llm-ls/pull/40

Unfortunately I have been unable to get this to word, as the commands in downloadAndUnzip do not seem to work on my windows machine

@noahbald I am new to this work. Can you please provide documentation on how to test this and I can give it a try on my machine.

Hey @YasirFarhan I reckon @McPatate will be able to help you out. For me to get this set up, I did the following

Follow the instructions for developing a plugin, using Gradle to run an instance of Intellij with the plugin
Pull my fork of llm-ls, from here (https://github.com/noahbald/llm-ls)

Use Cargo to build the project

Configure your instance of the llm-intellij plugin, setting the binary path to your build of llm-ls


[Avatar] Custom variant

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

LGTM - but you're the expert! :D


put in a quick check on axes marked as EVEN

Reported by Ansley B Manke on 10 Nov 2003 23:27 UTC
If an axis in a NetCDF file is marked as evenly spaced,
do a quick check of the 1st, 2nd, and last coordinate
values to verify that (z2-z1) = (zn-z1)/(n-1) to within
some tolerance.  If not, issue a warning like "axis DEPTH
has uneven coordinates, ignoring erroneous EVEN attribute..."
Make sure to do it with care for precision; using TM_FPEQ
and TM_DFPEQ.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/689

Comment by<EMAIL_ADDRESS>on 2 Dec 2003 22:12 UTC
*** Bug 743 has been marked as a duplicate of this bug. ***

Modified by ansley.b.manke on 5 Jan 2011 19:38 UTC

Adding @AndrewWittenberg

This is fixed.  I ran into it with the Discrete Sampling Geometries development but want to get it into the trunk as well.
Note that point_spacing is not an attribute listed in the CF conventions.  Its use is for convenience in not having to read in all the coordinate data every time and check for regularity.
If the user has said "USE/REGULART my_data.nc" then we'll take them at their word and treat the data as regularly spaced in time.

Discussion with Ryo Furue on the Users' list, 7/3/2020.
The test as implemented for regular spacing, comparing the first delta-coordinate with  (z2-z1) = (zn-z1)/(n-1), turns up too many "uneven" axes that are in fact ok, but are merely looking a little irregular due to promoting single-point floating point coordinates to double-precision.  Rework this test.
Also, when the warning is given "...has uneven coordinates, ignoring erroneous EVEN attribute...", we've decided to treat the axis as uneven.  In this case the point-spacing attribute needs to be written as point_spacing = "uneven".  It's being written as even!


[Discussion] Simplify custom bindings generation for custom builds

Hello, I just wanted to make a small proposal to this wonderful crate. Namely, to improve the ergonomics for when using a custom build of godot.
Problem
The problem is as such, a user wants to use godot-rust with a custom build of godot so they need a custom build of gdnative-bindings to use godot-rust. The current process is nicely documented here but it is quite convoluted. To summarize, when using a custom godot build we need to rebuild the gdnative-bindings with the correct api.json exported from our custom godot build. The recommended steps are to download the gdnative-bindings crate, modify the stored api.json file, and then do some magic in our project's Cargo.toml.
Criticism
My main argument against this implementation is that it's neither here, nor there. On the one hand, there's the kind of user that is comfortable customizing godot, making a custom build, using these bindings, etc. For those people I think we can safely assume that they would be comfortable maintaining a fork of this repo and can simply change the api.json directly. For these power users, I would argue the guidance can be simplified to "regenerate the api.json here and rebuild".
On the other hand I think there is a second type of user who uses a custom build of godot but maybe makes very minor modifications (disable specific modules, compiler tweaks, etc.) or none at all (e.g. is on a minor version beta). For this user I think the steps outlined in the docs are too cumbersome. If I am on 3.2.3-stable but I want to test my project on 3.2.4-beta then there's quite a bit of ceremony to update my gdnative lib.
Proposal
I believe we can simplify the process by leveraging the build file in gdnative-bindings. I propose that using a feature flag and an environment variable, the api.json can be automatically generated at build time. This would allow users to use the latest sources without having to modify any source code but still be able to target a custom build. Here is an example of how I would foresee this working.
A new feature flag would be introduced in the top level crate that gets forwarded to the gdnative-bindings crate. Users who want to use a custom build would specify this feature flag.
[dependencies.gdnative]
version = "0.9.1"
features = ["godot_custom_build"]

The user would then also have to specify an environment variable to their custom godot build, e.g. GODOT_BIN. The feature could then be detected in gdnative-bindings/build.rs and if it is enabled and the var set then the api.json can be re-built on the fly.
if cfg!(feature = "godot_custom_build") {
    let godot_bin = env::var("GODOT_BIN").expect("GODOT_BIN not set");

    // Call std::process and generate the api.json
}

I believe this would be a big enhancement to support the workflow of custom builds and would not be too disruptive. It would require adding a feature flag to the crates, adding the feature check to the build.rs and adding some minor logic to pick the correct api.json after it has been generated.

Seems like a good idea to me. Thanks for the suggestion! Could you create a PR for this?

Is the feature flag necessary, it may work that if some env var (let's say GODOT_BIN) is present and not empty this behavior will occur, otherwise default api.json will be used. User will have even less to do to use custom Godot.
If nobody works on it, I may try to do this in +/- 2 weeks.

The user would then also have to specify an environment variable to their custom godot build, e.g. GODOT_BIN.

Could we also use which::which("godot") and fallback to $GODOT_BIN if it isn't set? I'd assume that Linux users typically symlink the binary into their path anyway.

@rminderhoud and @bluenote10: Thanks a lot for your input! I realized your ideas as a proof-of-concept in #833.
Let me know if you have time to test it or other feedback (you could leave it directly in the PR)! 🙂
@carmel4a: I think it's important that godot-rust in its default configuration behaves consistently. If the presence of an executable on the system alters runtime behavior (to the point of incompatibility) without the user opting in, that will lead to unpleasant surprises. That's why custom-godot is now a default-off feature flag.

@Bromeon, happy new year. I didn't get a chance to test this before it merged but the changes look awesome!

@rminderhoud Thanks, happy new year to you too! 🍾
Glad to hear! No worries about the testing, we can continuously enhance the experience. Now that's in master, many more people have the chance to try it out and give feedback. There's already a follow-up PR that improves robustness: #838


Introduce a changelog

Hi phraseapp-in-context-editor-ruby-maintainers (what a title for a business card),
What do you think about introducing a changelog users could quickly check against when updating to a newer version?
Even easier when following Semantic Versioning (http://semver.org/).
Thanks in advance!

This gem generates them from github: https://github.com/skywinder/github-changelog-generator

done. thanks @kieranklaassen for the hint.


[5.3] Simplify conditional

This little PR simplifies the conditional in ModelMakeCommand.php. 🌵

@fernandobandeira ah, yes! you are right. I've change it

i don't want to labor on this since both before and after do the same thing. but i'm curious why this simplifies it? you just moving the code from inside to the outside of the conditional?  is it purely a readability thing?

Yeah, it's only meant to improve readability


Can i use right-click menu ? And webkit in windows is even better.

Can i use right-click menu ? And webkit in ms-windows is even better.

Right-click has "Reload" menu item in it. So I disable context menu since
it's not needed in most of my use cases. Of course, it might as well be a
flag.
Not sure I understand about windows part. WebKit is only used on Linux and
Mac because it's available there natively. On Windows MSHTML is available
natively.
Integrating other engines such as Edge or CEF or WebKit would be harder,
but if you have any ideas how it can be done - feel free to help.
Regards,
Serge
On Sun, Dec 17, 2017 at 10:09 AM, 朱博文<EMAIL_ADDRESS>wrote:

Can i use right-click menu ? And webkit in ms-windows is even better.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zserge/webview/issues/52, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0r0EUZj59SQelZOy6oy4H-No-kdbqnks5tBMwlgaJpZM4RElK-
.

--
"One must have a chaos inside oneself to give birth to a dancing star." -
Thus Spoke Zarathustra

can you make it a flag please ?

Some people get used to copy and paste (I am one of them) via right-click menu, and feel panic when right-click menu lost.
A flag is great, thanks.
I do not think I can make webkit work in ms-windows right now, mainly web and sometimes server side work.


[AST] SRATE RNG randomize & USB Calibration Test Support

The following is addressed:

SRATE RNG randomize support
USB Calibration Test Support

Signed-off-by: Jacob Levy<EMAIL_ADDRESS>

@tjaychen @msfschaffner  kokoro failed on AST (20 Errors) and on chip_earlgrey_asic (7 errors)...
What needs to be done to fix it? Can it be bypass for now?

I will recommend splitting AST RNG changes and USB change into separate PRs so that they can be independently reviewed and merged.
The AST RNG part looks good to me and can be merged.

@sriyerg I have been working with @tjaychen on the USB calibration test and this is the resulting AST changes that was tested.

@sriyerg I have been working with @tjaychen on the USB calibration test and this is the resulting AST changes that was tested.

i tend to agree with @sriyerg that splitting this up would be better, so we don't couple the dependencies.

@tjaychen  The rng.sv is a single file with new plusargs for the random min-max. The rest of the files are for the USB cal test.

@sriyerg Can you copy the ring.sv to your PR?
After you merge it, I will rebase and remove it from this PR.

@sriyerg Can you copy the 'rng.sv' to your PR? After you merge it, I will rebase and remove it from this PR.

@tjaychen
I am not sure if this logic works. If you tie off seed_en_i to 1, then the LFSR will never advance to the next state. The LFSR will get tied off the random value set with dv_rng_lfsr_seed in the initial block. See associated logic in prim_lfsr.sv:
  assign lfsr_d = (seed_en_i)           ? seed_i          :
                  (lfsr_en_i && lockup) ? DefaultSeed     :
                  (lfsr_en_i)           ? next_lfsr_state :
                                          lfsr_q;

@sriyerg Good point! I was not aware that this is how it was implemented...
It should be:
assign lfsr_d =   (lfsr_en_i && lockup) ?  ((seed_en_i)  ? seed_i   :  DefaultSeed)    :
                 (lfsr_en_i)           ? next_lfsr_state :
                                         lfsr_q;

@sriyerg Good point! I was not aware that this is how it was implemented... The ;eeed_i' will re-seed the LFSR in mid life when the seed_en_i get pulsed.
I have expected it to be:
 assign lfsr_d = (lfsr_en_i && lockup) ? ((seed_en_i) ? seed_i : DefaultSeed) :
                 (lfsr_en_i)           ? next_lfsr_state :
                                         lfsr_q;

If the prim_lfsr will stay as is, I will remove the seed_i option...

I will instead update prim_lfsr,sv to internally handle initial seed randomization. I think that is a better solution because it will apply to ALL instances of prim_lfsr in the chip, and revert the seed related changes in rng.sv.

sounds good.
i might not be able to do today, but i will try to pull down the usb stuff
to give it a spin.
On Thu, Aug 25, 2022 at 3:10 PM Srikrishna Iyer @.***>
wrote:

@sriyerg https://github.com/sriyerg Good point! I was not aware that
this is how it was implemented... The ;eeed_i' will re-seed the LFSR in mid
life when the seed_en_i get pulsed.
I have expected it to be:
assign lfsr_d = (lfsr_en_i && lockup) ? ((seed_en_i) ? seed_i : DefaultSeed) :
(lfsr_en_i)           ? next_lfsr_state :
lfsr_q;
If the prim_lfsr will stay as is, I will remove the seed_i option...
I will instead update prim_lfsr,sv to internally handle initial seed
randomization. I think that is a better solution because it will apply to
ALL instances of prim_lfsr in the chip, and revert the seed related
changes in rng.sv.
—
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/14576#issuecomment-1227810254,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSRPS23LOUCR63DMVETV27VPBANCNFSM57TSNB6A
.
You are receiving this because you were mentioned.Message ID:
@.***>

@sriyerg There is some logic that generate the 'seed_en' in the blocks that use it. Not sure what was the use intent...
@tjaychen Can you clearify what was the intended use of the external Seed in the prim_LFSR?
If the 'seed_en_i' is set to '1' the LFSR is "dead"...

@sriyerg There is some logic that generate the 'seed_en' in the blocks that use it. Not sure what was the use intent... @tjaychen Can you clearify what was the intended use of the external Seed in the prim_LFSR? If the 'seed_en_i' is set to '1' the LFSR is "dead"...

ah yes. A fair number (not all) of the prim_lfsr in our system interface with the entropy complex. So periodically (based on block unique conditions) they request for new entropy seed from the entropy complex.  This just helps break up the predictability of the lfsr's somewhat for the use cases where this matters.

@sriyerg Can you add a parameter to  the prim_lfsr the by default will choose the DefaultSeed and is set will use a randomize internal seed. This option is limited to simulation and not for synthesis.

@sriyerg Can you add a parameter to the prim_lfsr the by default will choose the DefaultSeed and is set will use a randomize internal seed. This option is limited to simulation and not for synthesis.

i think that's exactly what @sriyerg has planned :)

@sriyerg Can you add a parameter to the prim_lfsr the by default will choose the DefaultSeed and is set will use a randomize internal seed. This option is limited to simulation and not for synthesis.

i think that's exactly what @sriyerg has planned :)

PTAL: https://github.com/lowRISC/opentitan/pull/14601

@tjaychen  Why I am getting this for CI (Quality (quick lint))?
##[error]Commit has one or more Signed-off-by lines, but not the one we expect. We expected to find "Signed-off-by: Jaedon
Kim<EMAIL_ADDRESS>The commit message must contain a Signed-off-by line that matches the commit author name and email, indicating agreement to the Contributor License Agreement. See CONTRIBUTING.md for more details. You can use "git commit --signoff" to ask git to add this line for you.
##[error]Commit lint failed.
Should I rebase?

@tjaychen Why I am getting this for CI (Quality (quick lint))?
##[error]Commit has one or more Signed-off-by lines, but not the one we expect. We expected to find "Signed-off-by: Jaedon Kim<EMAIL_ADDRESS>The commit message must contain a Signed-off-by line that matches the commit author name and email, indicating agreement to the Contributor License Agreement. See CONTRIBUTING.md for more details. You can use "git commit --signoff" to ask git to add this line for you. ##[error]Commit lint failed.
Should I rebase & force push again?

i'm not quite sure, did you pull another PR prior to starting this? For whatever reason github thinks @jdonjdon originally authored a part of this, and is looking for his signature. @eunchan do you happen to know?

@tjaychen Just rebased  and forced push to get @sriyerg merged PR of the rng.sv
I can close this PR and open a new one after I pull opentitan.

Closing an open a new PR...


Camera returning black screen

Hi,
I installed the tiscamera library on my Linux PC with Ubuntu 20.04 and using the basic command
gst-launch-1.0 tcambin ! videoconvert ! ximagesink to run the camera. However, my camera is returning a black screen with the following message in the background
gst-launch-1.0 tcambin ! videoconvert ! ximagesink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... INFO: Working with src caps: video/x-raw, framerate=(fraction)539/1, width=(int)720, height=(int)540, format=(string)GRAY8 Setting pipeline to PLAYING ... New clock: GstSystemClock ERROR: from element /GstPipeline:pipeline0/GstXImageSink:ximagesink0: Output window was closed Additional debug info: ximagesink.c(696): gst_x_image_sink_handle_xevents (): /GstPipeline:pipeline0/GstXImageSink:ximagesink0 Execution ended after 0:00:05.060191483 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...
The camera mode is DMK 37AUX287. I also installed IC Measure from https://www.theimagingsource.com/support/downloads-for-linux/ and my camera is displaying frames in this application.
I also tried to use the camera on Windows PC with its windows software and it works fine there with any frame rate.
It would be great if someone can let me know some workarounds for the problem since I would like to use the camera from Python for my project. Thank you!
--
Deepak

I would start with lower frame rates in the GStreamer pipeline.
gst-launch-1.0 tcambin ! video/x-raw, format=BGRx, width=720, height=540, framerate=30/1 ! videoconvert ! ximagesink
If that works, you may use "300/1" instead of "30/1". You can try up to "539/1" until your computer can not handle the high frame rate anymore.
Stefan

Hi Stefan,
Thank you for your reply. I tried the following command on my PC. So the following happens: As soon as I plugged in the camera, and ran the command, it displayed me some frames when I moved the camera, however within 10 seconds the frame update stopped and it kept on displaying the last frame captured. After canceling this and running the command again, it started displaying the black screen again.
To be fair, it seems IC-Measure is a bit buggy too on my PC and it keeps on crashing sometimes when I try to open my device there. Any help would be greatly appreciated. Thanks!
Deepak

Hello
Is the USB connector plugged well into the camera?
Which computer model and brand do you use? In particular, which USB controller chip do you use? If it is AMD/ASMEDIA, then you must expected issues.
Stefan

Hi Stefan,
Yes, the USB connector is well plugged in. Here are some of the details of the processors in PC:
vendor_id	: AuthenticAMD
cpu family	: 25
model		: 33
model name	: AMD Ryzen 9 5900X 12-Core Processor x24
It also has a graphics card by NVIDIA.
I bought the PC from iBuyPower.
To check the USB controller chip, I used sudo lspci|grep -i usb and it returned me this:
02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43ee
2d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
It seems from here, it is AMD.
By the way, it seems I was connecting the camera on the front 3.0 ports earlier and it showed black screen but on the port at the back, it is showing live stream well. However, I am not able to understand why it didn't work on the front port since other devices work well on the front ports.
Thanks for your help.
Deepak

Closed due to inactivity.


Insert HTML attribute value quotes does not work in Razor Editor Visual Studio 2022

"Insert attribute value quotes" is turned on in Visual Studio settings but does not work.
On attribute selection from the IntelliSense it does as follows:
<div class|>

</div>

Actually it should have been as follows:
<div class="|">

</div>

Visual Studio Version: Visual Studio 2022 preview 7

Closing as duplicate of: https://github.com/dotnet/razor-tooling/issues/4436


Add test coverage for Download & Postman Upload service

In the 1.10.0 release @nicklloyd did a great rework of the Postman upload API implementation.
Closing this issue, since the changes & tests were part of the 1.10.0 release


Ace theme+mode+worker file locations?

Hi,
thank you for updating the aceeditor for vaadin7.
Maybe I found a bug:
When I have text in the AceEditor and set the cursor on a line, the whole line is not highlighted (as it has been in old vaadin6 version).
Bug? Or did i forget to set a needed option?

Hi,
I am new In vaadin ace editor. i added ace editor in my application. but enter in is not working. the cursor only in first line can u help me.


User management list roles very slow

When using the User management tool, clicking on a user's 'roles' button opens a dialog with spinning wheel that takes several minutes to fetch the list of roles.

This has also been my experience.
On Oct 16, 2015, at 11:29 AM, Amos Hayes<EMAIL_ADDRESS>wrote:

When using the User management tool, clicking on a user's 'roles' button opens a dialog with spinning wheel that takes several minutes to fetch the list of roles.
—
Reply to this email directly or view it on GitHub.

Can you please provide me with a an atlas where this behaviour is observed?

The normal delay that I perceive is about 3 seconds.

This has been addressed in Issue #243. Are you reporting this on an atlas older than this fix?
I am basically unable to reproduce this problem on my platform.

This was happening last week on Gwich'in. After several attempts with several users, eventually I gave up (never did come back with the list, even after 30 minutes.)
Later that afternoon, it worked after a few seconds.

Looking at the thule atlas, I experience the same delay. When logging in as 'admin' on the CouchDb futon app and selecting 'status', the app reports indexing of a back up copy of thule (thule_20151016_02).
Obtaining the list of roles is a database wide operation. The algorithm is to iterate over all databases, find the name for each database and find the layers for each database. Then, from this information, it is possible to create a complete list of all roles.
However, getting a list of layers in a database is a view query. If a database has not been indexed yet, then the query does not return until the indexing is done. Obviously, this induces a timeout in the client request, which takes about a minute. Furthermore, this timeout does not seem to be respected by the client application.

Ha! I wondered about that. I was making a couple replicated backups each day. Of course, the first (and maybe only?) time those backup db instances would be asked to create their indices would be when that role dialog was hit.

One solution is to have a robot thread hitting all databases, keeping them indexed.
A simpler solution is to change the role dialog to report all roles already set on the user plus all the possible roles for the current database.

Your second solution sounds best for this issue.
That said, something that pokes the active db to create indices so users don't hit the delays after a reboot would be good for the current database, regardless. But that is a different problem (that isn't as big a deal because I'm already using a web site monitoring service that hits our active atlases regularly.)


add lightning argument parser

What does this PR do?

Adds a way to more easily parse up datamodule + model args and share duplicate ones if names are repeated. i.e. if you mention 'train_batch_size' in your init args of both your dm and your model, you probably want to share those values, not pass separate ones. In addition, this handles collisions of names by default.
Its just an argparse argument parser w/ 2 added hooks: add_object_args and parse_lit_args.
I'll provide more concrete example later, but this snippet gives quick overview...
from pytorch_lightning.utilities import LightningArgumentParser

parser = LightningArgumentParser()
parser.add_object_args('dm', MyDataModule)
parser.add_object_args('model', MyModel)
args = parser.parse_lit_args()

# args.dm --> init args to your dm
# args.model --> init args to your model

Fixes #3076 #2385
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@carmocca tagging you as we discussed on slack.

closing for now. will implement in bolts before moving here.


[#1094]: Add trigger for previous version warning

Preview environment images deployed!
The preview environment has been updated:
client image tag: preview-1928-c5d38788411aec2f56660136bda0d88ada3ae701-20240524.0714
storybook image tag: preview-1928-c5d38788411aec2f56660136bda0d88ada3ae701-20240524.0714
Client URL: https://pr-1928--epp.elifesciences.org
Storybook URL: https://pr-1928--epp-storybook.elifesciences.org
Note: Updated images can take a few minutes to roll out.

Preview environment created!
The preview environment has been deployed to the cluster.
Client URL: https://pr-1928--epp.elifesciences.org
Storybook URL: https://pr-1928--epp-storybook.elifesciences.org
Note: If this is a new environment, it can take a few minutes for DNS to update.


Support multiple column-level badges when loading CSV

Expected Behavior or Use Case
Table columns currently support one badge only. I'd like them to support multiple badges.
Service or Ingestion ETL
Databuilder
Possible Implementation
In ./databuilder/extractor/csv_extractor.py  line 195, change:
badges=[column_dict['badges']]

to load multiple again, like split on commas.
Example Screenshots (if appropriate):
Context
I would like to multiple badges on columns to display different column attributes, since my project is doing data lineage and access control at a column level.
I have implemented this in my project by making my own class based on this CsvTableColumnExtractor.

This issue can be closed per https://github.com/amundsen-io/amundsendatabuilder/pull/469


Missing pixels and extractors (GlobalPeak / NeighborPeak)

LST has now the first observed data with a switched off module.
Initially, we filled the missing pixels with nan, however that broke the GlobalPeak and NeighborPeak extractors since they do a waveform.mean(axis=-2) which is then all nan which results in peak_index = 0 for alle pixels, since np.argmax([np.nan, np.nan]) == 0.
I am not proposing to change those algorithms to be able to treat nans, since using nanmean is a major increase in runtime.
However, we should probably define in the data model, what value waveforms of event.mon.tel[tel_id].pixel_status.hardware_failing_pixels are expected to have and how these are treated by the extractors combining multiple pixels for the extraction.
We probably need to give the extractors this mask and fill zeros for all failing pixels and only look at the non-failing pixels.

Yes, we should  treat excluded pixels in a consistent way at all data levels.  Also, I guess using hardware_failing_pixels is not enough: that helps with missing drawers, but for extractors that use neighbors/means those would also be affected by noisy pixels as well (stars etc).   Is the current sequence of steps used right now to analyze/calibrate LST data written somewhere? I would like to see where excluded pixels are computed, since that may have some impact on the data model.  E.g. is a pedestal file generated first,  and the pedestal variances used to detect turned-off or noisy pixels?

There are three "failing pixel" arrays, hardware, pedestal and flatfield. The latter two are filled by lstchain by the class that calculates the pedestal and flatfield calibration data on the interleaved pedestal / flat field events.
I don't think this information is yet used for anything. With the exemption of the Muon analysis, lstchain currently uses LocalPeakWindowSum, probably exactly for those reasons.
For the cleaning, the levels are adjusted now by the pedestal_std from the interleaved events in a second step.
So first extract images and interleaved calibration info, then calculate image parameters in a second pass.

https://github.com/cta-observatory/ctapipe/pull/2023


Crash on rigidbody enter_shape with a set_contact_monitor(false) call

I'm trying to disable collision for the player on enemy hit with this code on enter body
func _on_body_enter_shape( body_id, body, body_shape, local_shape ):
	self.set_contact_monitor(false)

This causes a crash for some reason, looking for debug dump on godot source code, the method who crash called by the player is:
void RigidBody2D::_body_inout(int p_status, ObjectID p_instance, int p_body_shape,int p_local_shape)

It seems to be a problem with enter collision, disable on enter contact monitor and for some reason godot call exit collision and crash, maybe add a check for contact monitor bool here?.
video from the issue:
https://gfycat.com/LegitimateThunderousBorderterrier
Here is the simple demo from video which reproduce the problem and you could trace with debug:
https://dl.dropboxusercontent.com/s/ktv2ltlufr9v19c/bug_collision.zip?dl=0
Tested with the last compiled godot from git today Dec 10, 2015 (https://github.com/godotengine/godot/commit/3b68f0d051ac33a95e78025622c5f93219591da9)
So, I don't know if this is a bug or is the intended behaviour and if I should use another simple alternative for disable/enable ALL rigidbody collisions on player respawn/death animation?

if it's from a singal it should at least throw an error before crashing
(though i think it was not supposed to crash)
you can always do
call_deferred("set_contact_monitor",false)
and it will work
On Sat, Dec 12, 2015 at 6:25 AM, Hearto<EMAIL_ADDRESS>wrote:

I'm trying to disable collision for the player on enemy hit with this code
on enter body
func _on_body_enter_shape( body_id, body, body_shape, local_shape ):
self.set_contact_monitor(false)
This causes a crash for some reason, looking for debug dump on godot
source code, the method who crash called by the player is:
void RigidBody2D::_body_inout(int p_status, ObjectID p_instance, int p_body_shape,int p_local_shape)
It seems to be a problem with enter collision, disable on enter contact
monitor and for some reason godot call exit collision and crash, maybe add
a check for contact monitor bool here?.
video from the issue:
https://gfycat.com/LegitimateThunderousBorderterrier
Here is the simple demo from video which reproduce the problem and you
could trace with debug:
https://dl.dropboxusercontent.com/s/ktv2ltlufr9v19c/bug_collision.zip?dl=0
Tested with the last compiled godot from git today Dec 10, 2015 (3b68f0d
https://github.com/godotengine/godot/commit/3b68f0d051ac33a95e78025622c5f93219591da9
)
So, I don't know if this is a bug or is the intended behaviour and if I
should use another simple alternative for disable/enable ALL rigidbody
collisions on player respawn/death animation?
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3041.

Thanks for your reply, with deferred works, but always crash if I close the window after the collision with deferred call, so leaves the game unstable, tested with the demo. Also for what I understand from deferred methods, those are asynchronous, so the object could collide with another objects on the window of true > false?
On the console doesn't print anything weird or errors, also I tried disconnect signals on enter before the set_contact_monitor and the bug persist.
Screenshot from the console: http://vgy.me/zYU8GP.png
The complete code on the demo uploaded to reproduce the bug is so simple:
extends RigidBody2D

func _ready():
	pass

func _on_bug_body_enter_shape( body_id, body, body_shape, local_shape ):
	self.set_contact_monitor(false)

And with the godot source code is easy to track where the error is.


runtime: terminate locked OS thread if its goroutine exits

I propose a new runtime.TaintOSThread function. This would mark the current thread that the calling goroutine is running on as being "tainted": not safe for use by other goroutines. When the goroutine exits or the goroutine is unpinned from the (previously pinned) OS thread, the thread is killed.
This is needed when goroutines are pinned to OS threads and the state of the thread is modified in way that is unsafe for other goroutines, such as unsharing and then modifying one of the Linux namespaces. Without this change, it is impossible to clean up OS threads: the pinning goroutines and OS threads need to stay until the programme exits, leading to unfixable goroutine and OS thread leaks.
The expected calling pattern is:
runtime.LockOSThread()
runtime.TaintOSThread()
syscall.Unshare(syscall.CLONE_NEWNS) // Example mutation of OS thread state.

How can I kill the thread safely? I don't see a function in the runtime package to do this. If I can safely kill the thread on which a goroutine is running, then that would work too, I just didn't think that would be as palatable as marking a thread as tainted.
There's actually no need to unshare (and that wouldn't help anyway, since the new namespace inherits from its ancestor).

syscall.Syscall(syscall.SYS_EXIT, 0, 0, 0)? Haven't tried it, though.

Works for me:
bradfitz@gdev:~$ cat exit.go

package main

import (
        "runtime"
        "syscall"
        "time"
)

func main() {
        runtime.LockOSThread()
        println("Hi from ", syscall.Gettid())
        go func() {
                runtime.LockOSThread()
                println("Hi from ", syscall.Gettid())
                syscall.Syscall(syscall.SYS_EXIT, 0, 0, 0)
        }()
        time.Sleep(500 * time.Millisecond)
        println("Bye from ", syscall.Gettid())
}

bradfitz@gdev:~$ go run exit.go
Hi from  6876
Hi from  6878
Bye from  6876

Or, better
package main

import (
        "fmt"
        "os"
        "runtime"
        "strconv"
        "syscall"
        "time"
)

func main() {
        runtime.LockOSThread()
        fmt.Println("Hi from ", syscall.Gettid())
        other := make(chan int, 1)
        go func() {
                runtime.LockOSThread()
                tid := syscall.Gettid()
                other <- tid
                fmt.Println("Hi from ", tid)
                fi, err := os.Stat("/proc/" + strconv.Itoa(tid))
                fmt.Printf("proc %d: %v, %v\n", tid, fi, err)
                syscall.Syscall(syscall.SYS_EXIT, 0, 0, 0)
        }()
        time.Sleep(500 * time.Millisecond)
        tid := <-other
        fi, err := os.Stat("/proc/" + strconv.Itoa(tid))
        fmt.Printf("proc %d: %v, %v\n", tid, fi, err)
        fmt.Println("Bye from ", syscall.Gettid())
}

Hi from  7277
Hi from  7279
proc 7279: &{7279 0<PHONE_NUMBER> {63630648429 114580211 0x550860} 0xc20804e000}, <nil>
proc 7279: <nil>, stat /proc/7279: no such file or directory
Bye from  7277

I worry that the runtime would be upset at an OS thread permanently vanishing. The runtime may want notification to ensure that anything the m is holding is freed first.
Maybe the existing enterSysCall already does everything that might matter?
At the very least, the allm list will grow without bound.

Yes, that was one of my worries too. Can we get some kind of guidance on whether it's considered safe to kill a thread? What happens to the goroutine that's running on it?

@aclements

I do think we need to let the runtime know that the thread can not be used.  The simple approach is
runtime.LockOSThread()
select{}

That will ensure that nothing else uses the thread, but it won't actually kill the thread.  It would be an acceptable approach if you only need to do this a few times, but of course would be unsatisfactory if you need to do it continually.
Another approach would be to go through C.  Have C code create a new thread, which could then call into Go.  That gives you a thread that the Go runtime won't use itself, so you can simply call pthread_exit when done.  Of course this is not ideal if you otherwise have a pure Go program.

All my Go code so far is pure Go. I was hoping to keep it that way.
It seems to me that we need some way to cleanly kill a thread. The hack shown above is, well, a hack :-)

Is runtime.ThreadExit sufficient for your purposes?  I'm thinking of a function that would simply cause the thread to exit and not return.  The goroutine could continue running on a different thread.
I'll note that I appreciate that you need this, but it seems awfully special purpose.

Yes, runtime.ThreadExit would work fine. I'm not special, I'm just ahead of the curve :-)

@ianlancetaylor, or instead of introducing new API: just consider all threads "tainted" if they ever used LockOSThread and when the goroutine exits (implicitly or via the existing runtime.Goexit()), then kill the thread.

That works for me too.

Or maybe consider tainted all locked threads whose goroutine exits. If a goroutine calls Unlock before exiting, the thread is probably safe for reuse.

Yes, that works too. Which of these proposals is the most palatable?

I rather like @rasky's suggestion. If a goroutine exits without unlocking its thread, then you could think of that thread as still being locked, but with nothing it can ever do again, so you might as well kill it.
My only concern would be existing code that exits without unlocking implicitly unlocks the thread right now, so this change could cause such code to cycle through new OS threads, which could be a performance problem. But this all seems sufficiently obscure (and the fix for this performance problem is trivial) that I'm not too concerned.

Indeed. Can we can get an approval from the core team for the proposal that @rasky made?

@rgooch, we do proposal reviews roughly weekly, on Mondays. Sometimes we don't get through all open proposals and things wait another week.

Did this get into the review this week?

Nope. We spent this week on NeedsDecision bugs (#20192).
When this gets reviewed, updates will be posted here.

@rsc, @dr2chase, @ianlancetaylor and myself are all good with @rasky's suggestion. I haven't figured out how difficult it is to implement yet (it's certainly too late for Go 1.9).

Well, this is nice to see. Thank you. So, it looks like this will be available in go1.10 but not go1.9?
How can one add a compile assert so that a minimum go version is required to compile? Once this is available, I can relax certain restrictions in my code, but I need to be sure I have this fix otherwise it will be unsafe.

Use build tags, as in
// +build go1.10

to only compile a file for Go 1.10.
See "Build Constraints" in https://golang.org/pkg/go/build/ .

Maybe an aside to this behavior change, but is there a definition of what a "clean" thread would be, w.r.t. to the current state. The premise here is that the developer will be responsible for returning a locked thread to some reusable state, but it's clear what this means in a practical sense.
Perhaps this is left to the end user, but it'd be good to have guidelines in documentation re: the basic assumptions in this implicit behavior.

It's not possible to guarantee that a thread is returned to a previous state. For example, when unsharing a namespace, you may not be able to rejoin the original namespace. Thus, I think the safe approach is "once tainted, forever tainted. Kill it. Kill it with fire. Nuke it from orbit"

Maybe an aside to this behavior change, but is there a definition of what a "clean" thread would be, w.r.t. to the current state.

Really any change to thread state makes it unclean. That could mean namespace, priority, affinity, values in TLS, and probably at least a dozen other things that vary from OS to OS. If it's in any way distinguishable from any other thread in your process, it's probably not safe to return it to the thread pool. I'm not sure how to give useful guidelines on this, though I'm open to suggestions.

Why even worry about this? The simple and safe thing to do is kill the thread. Creating a new thread is cheap enough. I doubt that threads are being tainted at a high rate, so the cost of creating a new thread is insignificant in this context.

Why even worry about this? The simple and safe thing to do is kill the thread. Creating a new thread is cheap enough. I doubt that threads are being tainted at a high rate, so the cost of creating a new thread is insignificant in this context.

Sure. To be clear, I'm not suggesting that user's are encouraged to try to reset thread state. I agree that tracking / observing all potential those changes is highly complex and dependent on operating environment. The alternative of just leading thread be reaped / recreate is almost certainly more efficient from runtime and development perspective.

I'm not sure how to give useful guidelines on this, though I'm open to suggestions.

I suppose the documentation could be a note on LockOSThread:
A goroutine's thread context can be isolated with LockOSThread to allow modifications to that thread's system-level context, such as namespace, uid, gid, etc. Leaving the OS Thread locked at the completion of the goroutine indicates that the thread is polluted and should not be reused by other goroutines.
(Perhaps you had already come to something along these lines, but I do think providing some context in docs of the use case for this is valuable.) Cheers!

@benschumacher, I took a stab at your suggestion here: https://go-review.googlesource.com/c/52871

May also be worth auditing references to UnlockOSThread to make sure they're being used appropriately. This one from ensureSigM seems debatable. (The goroutine never exits, as far as I can tell. But if it did, you wouldn't want the thread to be reused.)


Allow Shoot deletion even when OS version or K8s version are expired

How to categorize this PR?

/area control-plane
/kind bug
What this PR does / why we need it:
If you don't touch your Shoots for a long time, it might be that their currently used OS image version or k8s version are deprecated and beyond the expiration date. In this case, you should still be able to delete the Shoot, which currently doesn't work.
Seems like we introduced this with the refactorings done in https://github.com/gardener/gardener/pull/4521? A similar thing was fixed in https://github.com/gardener/gardener/pull/4911 some time ago.
Special notes for your reviewer:
Release note:

A bug that prevented Shoot deletion when the OS image version or kubernetes version was beyond its expiration date is now fixed.

Thanks!
/lgtm

/cherry-pick release-v1.51

/cherry-pick release-v1.50

/cherry-pick release-v1.49

Ok, with 1.52.0 just released, I think the release-v1.49 branch should be no longer maintained.


Client refresh / credential caching issues in dev and prod

Saw an az aro create fail with the following storage deployment error messages:
{
    "error": {
        "code": "AuthorizationFailed",
        "message": "The client 'b9bc1545-a684-4e50-9a4d-2e2ee90bed6a' with object id 'b9bc1545-a684-4e50-9a4d-2e2ee90bed6a' does not have authorization to perform action 'Microsoft.Storage/storageAccounts/write' over scope '/subscriptions/225e02bc-43d0-43d1-a01a-17e584a4ef69/resourcegroups/aro-6hwuovvq/providers/Microsoft.Storage/storageAccounts/clusterixgbq' or the scope is invalid. If access was recently granted, please refresh your credentials."
    }
}

Need to understand how to fix this.

I also get this too
ERRO[2020-02-21T12:01:30+10:00] pkg/frontend/frontend.go:268 frontend.reply() authorization.PermissionsClient#ListForResource: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client '99d7cb4b-e087-4c94-8ced-3e15b07a870a' with object id '99d7cb4b-e087-4c94-8ced-3e15b07a870a' does not have authorization to perform action 'Microsoft.Authorization/permissions/read' over scope '/subscriptions/225e02bc-43d0-43d1-a01a-17e584a4ef69/resourcegroups/v4-australiasoutheast/providers/Microsoft.Network/virtualNetworks/dev-vnet/providers/Microsoft.Authorization' or the scope is invalid. If access was recently granted, please refresh your credentials."  component=frontend correlation-id= request-id=9bac8f35-12df-4aaa-8f9f-74f70c075979

https://gist.github.com/mjudeikis/81dc0f875d794992fb724df1f0c0ada8

dynamic validation has moved to backend, closing this.


loginActivity.js:11: Добавить кнопки login и sign up

The puzzle 6-c9a2a6c3 from #6 has to be resolved:
https://github.com/team-dev-spring-2022/teamMPSF/blob/0820c1d6b19a78da673eb35cd78e8184e717839c/components/screens/loginActivity.js#L11-L11
The puzzle was created by Deslifer on 05-Feb-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 6-c9a2a6c3 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #13 is still not solved.

@0pdd the only puzzle #13 is solved here.


fix: replace CL/sycl.hpp includes

Description
Please include a summary of the change. For large or complex changes please include enough information to introduce your change and explain motivation for it.
Changes proposed in this pull request:

does not resolve the problem, need fix on MKL side


Publish updated dataset to GBIF

Hi @LienReyserhove: I added basisOfRecord to the mappgin, see https://github.com/riparias/anb-crayfishes-occurrences/pull/17
Could you please republish the dataset? Thanks a lot.

Sorry, @LienReyserhove: basisOfRecord  is in occurrence extension, as you already tought me in the mapping of another dataset (see https://github.com/riparias/vmm-macrophytes-occurrences/issues/24).
I revert the PR #17.


Filter content stage accordingly to the API token settings

Using the "gatsby-source-plugin" I can retrieve records only by the "default stage" configured in the API settings. I would ask to maintainers to let us to filter the content accordingly the "Content that can be queried" setting.  Reference: https://graphcms.slack.com/archives/C2VP3HAJH/p1603438442078400

@lanzoninicola Love for you to try this out!


FIXBUG: convolution use error GFile API

This place should use Size() method.

Can one of the admins verify this patch?

I had signed a CLA and add email address in my github. How to pass the authorization. Thanks

https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/lib/io/file_io.py#L83
defines a size() and not Size() method.


Generalize the n-locating code

Add a way to ask where we should have put the locations of a conference
if all the people that came to a certain set of conferences participated
to that edition.

That will be handy. In particular, it's probably interesting to run it over the set of all editions of each conference.


Add missing emits for empty statement body in compile_program_single

Compared to previous version of compile_program_single, below two
codes are skipped when an empty body is given.
self.emit_constant(ConstantData::None);
self.emit(Instruction::ReturnValue);

Fix #3704

Oh, Ok I agree. I'll apply that change later and ping you.

@youknowone  I applied it 😊 Please take a look


[NEW]: afk with Lens

Please use this template to suggest a new event or update an existing event for the BBW website! You can also directly submit your event as a pull request to this repository. This will speed up things significantly!
# the name of your event
name = "afk Berlin"

# shortest possible name (without year)
shortname = "afk Berlin"

# type of the event
#  available types (you can choose more):
#   * meetup
#   * conference
#   * party
types = ["meetup, conference, party"]

# status of the event
#  available types:
#   * idea
#   * planning
#   * published
status = "published"

# the name of the group organizing the event
org = "Lens Protocol"

# the github handle of the directly responsible individual for this event
# (this person will coordinate with #bbw24 organizers)
dri = "parisrouzati"

# A point of contact (responsible person)
poc = "Paris Rouzati"

# the start date of the event
date = "2024-05-24"

# how many days the event lasts (1 - N)
days = 1

# the event times (shows up in the event card)
times = "15:00-19:00"

# Link to venues from the Places table - use this OR enter venueName, venueUrl and venueAddress
# venues = ["Monbijoustr. 11
 10117 Berlin"]

# the event venue name
venueName = "Telegraphenamt"

# link to the venue on open-street maps
venueUrl = "https://www.openstreetmap.org/node/10264516383"

# the event venue address
venueAddress = "Monbijoustr. 11
 10117 Berlin"

# the languages in which the event will take place (you can choose more)
languages = ["english"]

# the max number of attendees of the event
attendees = 400

# blockchains that the event deals with
# if it is an interchain event, then leave blank
chains = ["ethereum"]

# tags for the event, will show up as labels.
# pick 1-4
tags = ["web3 social", "new internet", "privacy", "scalability"]

# A logo attachment
logo = "[logo.png](https://ik.imagekit.io/lens/media-snapshot/tr:w-1000,q-80/576f955c3a8cbf5c6fd1d9d398c05ee1dce45e8a45ea6ac6deac33d7d6187c51.png)"

# a description of the event.
description = """
AFK is a new event series debuting in Berlin.
Alongside a line-up of cultural leaders, thinkers and technologists, we invite you to take a break from your laptop, dive into ideas, enjoy great conversations, and enjoy pop-ups from Orb, t2 and Bonsai. We'll wrap the evening up with a set by Sound of Fractures and delicious bites.
"""

[cfp]

[registration]
# type of registration
#  Possible values:
#   * tickets
#   * invites
#   * signup
type = "signup"

# price of the ticket
price = "Free"

# link to the registration or ticket purchase page
link = "https://lu.ma/afkberlin"

# custom action button label
#button = "RSVP on Luma"

# status of registrations
#  Possible values:
#   * available
#   * sold-out
#   * closed
status = "available"

[links]
# the website of the event
# make sure to have all the relevant information: dates, venue, program, ticketing (if any), etc.
web = "https://lu.ma/afkberlin"

# twitter account
twitter = "https://twitter.com/lensprotocol"

# docs
#docs = "https://lens.xyz/docs"

Your event is live please double check if everything is correct :) https://blockchainweek.berlin/24


toMtree for Pat.Alternative

add a converter for Pat.Alternative like case 0 | 1

Thanks you! I'll publish 3.0.0-SNAPSHOT with this fix soon.


SelectPanel: Accessibility remediation (breaking changes)

Co-authored-by: @hectahertz

Context
This PR addresses the changes derived from:

The Accessibility design review of the Figma files
The Accessibility engineering review

The Accessibility engineering review has more details on the reasoning behind all changes.
Screenshots

Before
After

Merge checklist

[x] Added/updated tests
[x] Added/updated documentation
[x] Tested in Chrome
[ ] Tested in Firefox
[x] Tested in Safari
[ ] Tested in Edge

@bolonio @hectahertz a few design comments:

Can we keep the placeholder attribute with the same aria-label contents? For users who don't need accessibility tools, that information should still be useful, and it's quite jarring to see an empty search field.
Let's use a large height going forward
the x close icon button should be dark gray, not blue ;)

Thank you!

Can we keep the placeholder attribute with the same aria-label contents? For users who don't need accessibility tools, that information should still be useful, and it's quite jarring to see an empty search field.

No, we shouldn't. The placeholder attribute should include an example of what the user need to insert in the input, while the aria-label attribute add more context about the purpose of the input. Technically, the placeholder attribute is optional, so it can always be included with their own content, but the content should not be the same as the aria-label attribute.
The sentence For users who don't need accessibility tools doesn't make any sense.

@bolonio @hectahertz a few quick design comments:

Can we keep the placeholder attribute with the same aria-label contents? For users who don't need accessibility tools, that information should still be useful, and it's quite jarring to see an empty search field.
Let's use a large height going forward
the x close icon button should be dark gray, not blue ;)
Let's use small buttons in the footer 🙌

Thank you!

Thank you for your comments!
I added an explicit inputPlaceholder attribute so that we don't have empty search fields. I do agree with @bolonio on the fact that having the aria-label as a placeholder will encourage incorrect aria-label values, so I think this is a good compromise!
I addressed all the other visual changes but I wanted to ask about the close icon button.
Our current IconButton variants don't support this, and there is a ButtonClose component but it's deprecated.
We probably shouldn't custom-style all our close buttons. Should we bring back the ButtonClose component?

Also! I just noticed the hover state no longer appears when you mouseover while an item is focused:
Screen.Recording.2022-07-18.at.13.45.13.mov

Good catch! This one is an old ActionList bug. It will get fixed once we upgrade to the new one.


JSONLD.js Parse Issue Failed to frame need-data

The given link https://ownerblue.master.matchat.org/owner/#!/post/?postUri=https:%2F%2Fnodeblue.master.matchat.org%2Fwon%2Fresource%2Fneed%2Fesl5xjgbpze2s96w28mb should display a correct taxi bot offer, but app. our jsonld.js fails to frame it (it used to work at some point)  -> you have to look into the console output otherwise you only see the mainpage as you are redirected to it due to the failed need retrieval
The Error is as follows:
Failed to frame need-data. https://nodeblue.master.matchat.org/won/resource/need/esl5xjgbpze2s96w28mb Error: Invalid JSON-LD syntax; if an element has the property "@set" or "@list", then it can have at most one other property that is "@index".     at new JsonLdError (jsonld.js:932)     at Object.api.expand (jsonld.js:14830)     at Object.api.expand (jsonld.js:14654)     at _expandObject (jsonld.js:15151)     at api.expand (jsonld.js:14763)     at _callee2$ (jsonld.js:11464)     at tryCatch (runtime.js:65)     at Generator.invoke [as _invoke] (runtime.js:303)     at Generator.prototype.(:8443/owner/anonymous function) [as next] (https://localhost:8443/owner/generated/app_jspm.bundle.js:94199:21)     at step (jsonld.js:11035)
issue is in linkeddata-service-won.js ca. line 1077

The Problem
This seems to be an issue with the included jsonld implementation in our rdfstore.
It gets triggered when a need contains rdf data for a list.
A list, in jsonld, is represented like this to distinguish it from the default interpretation of a json array as a set:
{
    "example:somePredicate": {
        "@list": ["a value"]
    }
}

The inline implementation of jsonld does not seem to support this format (yet?) and therefore parses it as a blank node when it is loaded into the rdf store:
_:b1 example:somePredicate _:b2
_:b2 "@list" "a value"

When retrieving the need from the rdf store the data gets converted to jsonld again (this time with the updated version from npm), which "correctly" results in:
[
    {
         "@id": "_:b2",
         "@list": "a value"
    },
    {
        "@id": "_:b1",
        "example:somePredicate": {
            "@id": "_:b2"
        }
    }
]

This, however, is not valid jsonld as the spec notes:

A list object MUST be a JSON object that contains no keys that expand to an absolute IRI or keyword other than @list, @context, and @index.

https://json-ld.org/spec/latest/json-ld/#lists-and-sets
Possible Fixes
Fixing this problem with our current setup would probably mean updating rdfstore. This might fix the problem, but it definitely will cause a lot of fallout in our current code base, since there are many breaking changes between our (modified) version of rdfstore and the current release.
It seems more feasible to work around the problem until October, when we will hopefully have the time to replace the current solution wholesale.
Workarounds

Before framing the data coming from our rdfstore, run it through a custom converter which fixes the blank nodes containing @list attributes.
This would mean writing said converter, and might introduce more bugs if the implementation is not correct

Do not use any rdf that contains lists.
Currently we only use lists in our taxi bot need, because sh:ignoredProperties is specced to refer to a list. Since we only use the property to refer to rdf:type we could work around this by not ignoring the type but requiring "at least one" type, regardless of its value.

i will try and change the shacl constraints with the suggested workaround from @peacememories


Use a default style if no feature schema

This is an addition to #247 not to crash on GeoJSON layers with empty feature collections.

Looks good


[SPARK-10737] [SQL] When using UnsafeRows, SortMergeJoin may return wrong results

https://issues.apache.org/jira/browse/SPARK-10737

Merged build triggered.

Merged build started.

Test build #42783 has started for   PR 8854 at commit 5bff8dc.

Test build #42783 has finished for   PR 8854 at commit 5bff8dc.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #42789 has started for   PR 8854 at commit 3c8f8cb.

Merged build triggered.

Merged build started.

Test build #42790 has started for   PR 8854 at commit 3a948d2.

Test build #42789 has finished for   PR 8854 at commit 3c8f8cb.

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

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

Merged build finished. Test FAILed.

jenkins test this please

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #42798 has started for   PR 8854 at commit 5406680.

Merged build finished. Test FAILed.

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

Test build #42790 has finished for   PR 8854 at commit 3a948d2.

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

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

Merged build finished. Test FAILed.

Test build #42798 has finished for   PR 8854 at commit 5406680.

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

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #42809 has started for   PR 8854 at commit 55d4f9a.

Test build #42809 has finished for   PR 8854 at commit 55d4f9a.

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

Merged build finished. Test FAILed.

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

test this please

Merged build triggered.

Merged build started.

Test build #42816 has started for   PR 8854 at commit 55d4f9a.

Test build #42816 has finished for   PR 8854 at commit 55d4f9a.

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

Merged build finished. Test PASSed.

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

LGTM

@JoshRosen Can you also take a look?

LGTM.

Thank you for reviewing this PR! I am merging it to master and branch 1.5.


Docs 1.0

I probably forgot something somewhere, but I think these are done enough to publish.
/cc @benvinegar @MaxBittker @mattrobenolt

@benvinegar pushed a commit that should address all these.


Add conv layer, as in article

In the article, it is mentioned that there is a 3x3 conv layer before the resnet blocks, in the refiner.
I thought it might help to add this layer as well.

Thanks for the PR. Nice catch 👍


OSX support

This is probably just a matter of adding one  or more osx tasks to the Travis build matrix.
PRs also accepted!

The build fails:

In file included from /Users/travis/.conan/data/Assimp/3.3.1/jacmoe/testing/build/5719b45ce3c28f685807df810559357d1decda02/assimp-3.3.1/code/glTFImporter.cpp:55:
In file included from /Users/travis/.conan/data/Assimp/3.3.1/jacmoe/testing/build/5719b45ce3c28f685807df810559357d1decda02/assimp-3.3.1/code/glTFAsset.h:59:
/Users/travis/.conan/data/Assimp/3.3.1/jacmoe/testing/build/5719b45ce3c28f685807df810559357d1decda02/assimp-3.3.1/code/../contrib/rapidjson/include/rapidjson/document.h:562:14: error: constructor cannot be redeclared
explicit GenericValue( size_t u ) RAPIDJSON_NOEXCEPT : data_(), flags_( kNumberUintFlag ) {
^
/Users/travis/.conan/data/Assimp/3.3.1/jacmoe/testing/build/5719b45ce3c28f685807df810559357d1decda02/assimp-3.3.1/code/../contrib/rapidjson/include/rapidjson/document.h:550:14: note: previous declaration is here
explicit GenericValue(unsigned long u64) RAPIDJSON_NOEXCEPT : data_(), flags_(kNumberUint64Flag) {

https://travis-ci.org/jacmoe/conan-assimp/jobs/242586047

I don't have a Mac, so if any of you have a Mac, it will be much faster to fix this, because debugging via Travis takes a loooooooooooooooooooooooooooooooooong time 😄


🚫 Implement "Lock New Issues" Workflow to Reduce Notifications and Support Maintainers

Description
As a repository maintainer, I propose the implementation of a workflow that aims to minimize notifications and enhance the support provided to maintainers. This workflow will automatically lock newly opened issues and provide guidance to contributors.
Screenshots
name: 'Lock new issues'

on:
  issues:
    types: opened

permissions:
  issues: write

jobs:
  action:
    runs-on: ubuntu-latest
    steps:
      - name: Lock issues
        uses: dessant/repo-lockdown@v3
        with:
          close-issue: false
          exclude-issue-labels: 'gssoc23.'
          process-only: 'issues'
          skip-closed-issue-comment: true
          issue-comment: >
            To reduce notifications, issues are locked. Your issue will be unlocked when we add the label `gssoc23`. If you're participating in GSSoC'23, please add the `gssoc23` label to your issue.

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hey @Vaishnavi-Patil2211  I think there are 200+ Issue as of now managing so many issue is so hard if this workflow will applied its reduce notification which help to maintain project easy to for maintainer


Simplify webmock:  exclude User-Agent and Connection from stubbing recommendation

I recently ran into an annoying issue with WebMock when implementing stubs the way the gem recommended.  I.e. the gem recommends copying over the User-Agent header of each request when pasting in what to stub.
Since most ruby http gems append their gem name and version number as the User-Agent in requests, this means that WebMock will automatically break whenever you update your http client, even if nothing else about the request has changed.  These breaks from updates are difficult to debug.
Rather than need to hack my HTTP gem to find way to keep my User-Agent stable in WebMock across gem updates, it dawned on me that it might be a lot simpler for most developers if WebMock by default just excluded the user-agent altogether from what it recommends stubbing... so that developer's using this tool don't see their tests break in confusing ways when they inevitably update their http client gems.
This will make WebMock tests less brittle, developer's more productive, and if people need the User-Agent recommended in their stubbing output they should just switch a flag on declaring they want it.

It may also be worth thinking about ways to reduce HTTP boilerplate in what webmock's mock.  If so I would recommend removing the Connection header also.

Hey @KelseyDH . That makes sense, good idea. I don't think anyone takes advantage of the user agent header.


Check if Grafana Agent can reach Prometheus

Enhancement Proposal
Hi Team,
I ran into an issue where grafana-agent was unable to reach Prometheus and I didn't get any clear feedback on the issue, thegrafana-agent charm was in active state.
I was integrating the observability stack to a machine charm using grafana-agent, here is my setup:

Add the integration in charm code
Deployed the charm on a machine juju model
Deployed grafana-agent on the same model
Deployed cos-lite on a k8s model
Integrated the applications as required

However the metrics of my charm were not being visible in prometheus. Upon some debugging I noticed the following message in the logs of grafana-agent:
ts=2024-04-23T08:09:36.894207378Z caller=dedupe.go:112 agent=prometheus instance=772477519ad7c8b1cfe32e99d44a4389 component=remote level=warn remote_name=772477-1d1fdd url=http://prometheus-0.prometheus-endpoints.cos.svc.cluster.local:9090/api/v1/write msg="Failed to send batch, retrying" err="Post \"http://prometheus-0.prometheus-endpoints.cos.svc.cluster.local:9090/api/v1/write\": dial tcp: lookup prometheus-0.prometheus-endpoints.cos.svc.cluster.local on <IP_ADDRESS>:53: server misbehaving"
And of course juju show-unit grafana-agent/0 agreed with the value of the url:
- relation-id: 4
    endpoint: send-remote-write
    cross-model: true
    related-endpoint: receive-remote-write
    application-data: {}
    related-units:
      prometheus/0:
        in-scope: true
        data:
          egress-subnets: <IP_ADDRESS>/32
          ingress-address: <IP_ADDRESS>
          private-address: <IP_ADDRESS>
          remote_write: '{"url": "http://prometheus-0.prometheus-endpoints.cos.svc.cluster.local:9090/api/v1/write"}'

It is failing because it is trying to reach Prometheus from outside of the k8s cluster using its fqdn.
Later I realised that Traefik was misconfigured during the deployment of cos-lite, once I fixed that everything seemed to be working fine.
My enhancement Proposal:
Is there any chance grafana-agent could report to the user that is unable to reach prometheus?

This was solved via the addition of the absent alert rule, as you can see here. If Grafana agent can't reach Prometheus, the alert rule will fire and you'd be notified that way.
Closing, but feel free to reopen if this is still an issue!


Is it possible to allow notification when app is in foreground on iOS?

I know apple suggests the behavior of notifications in foreground should be handled by the app silently, but I would like to achieve so because my notifications are reminder type and I want to prompt the user like such in background.
I was planning to use another local notification plugin to fire a notification when the app receives a push notification from firebase while it is in foreground. However, after testing out and reading some discussions over there, I realized that local notification plugin is implemented in the same way, which means no notifications can be seen in foreground.
I saw a similar plugin for react native includes a flag to allow notifications shown in foreground.
Wonder if that can be considered in this plugin as well.
FYI: https://github.com/evollu/react-native-fcm
Meanwhile, I was trying to modify the source code and make a hacky workaround but without success.
I am not so familiar with objective C so I'm looking for some help here.

When in the foreground, onNotificationOpen() silently returns the notification data. Just capture the data and present it with your own alert, toast, etc. Obviously, the notification title/message would have to be part of the data payload. On iOS, it can be found in the "apn" object. On Android, it doesn't seem to be there. As a solution, I decided to replicate the title and body of the notification (server-side) and included them in the data payload.


Expose zero, one, and multiplicative_generator as constants

This MR exposes the zero, one, and multiplicative_generator values as constants rather than functions. It might be preferred to only have the constants version---and I'm happy to make that change if so---but for now I've left the original function versions as well.

Related: #87

This PR is now almost entirely the codegen changes, which cannot be reviewed in the same PR as the trait changes. So I'm going to make my own PR on top of #93 that adds the associated constants, and we can use that to investigate the ecosystem and confirm whether it will cause any issues for downstream trait implementors (https://github.com/zkcrypto/ff/issues/87#issuecomment-1294891608).

#87 has now been closed by #94. This PR now needs rebasing, after which it will only contain the proposed codegen changes.