Error when run on android jelly bean 4.1.2

When i run the the app it show force close dialog :'( please fix it

Can you share more details? An error log would be great.
Thanks.

No error details. Closing.

Please give me the apk.

Send us your Realtime application key for configuration and build. If you don't have one you can get one for free at https://accounts.realtime.co/signup/

Application Key: UGXo2h
Private Key: chJV1jxmAAsOAccount Type:Realtime Messaging Free
Rabu, 08 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

Send us your Realtime application key for configuration and build. If you
don't have one you can get one for free at
https://accounts.realtime.co/signup/
—
Reply to this email directly or view it on GitHub.<
https://ci4.googleusercontent.com/proxy/aOGwNhdNIvfmnBH66HQrJzR7ca4hv-qk697SujA7bqbd9s4CfCpnjffVD_yuIZ5ckQq_IDzPIxtpoVpG7GunmjwmC21U9FVhVV7sa74KufrYFiihdvHPwa8OeoXVvymikhMvUy9vwUnf7Qyv-C5WiWdQeUYS-A=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYWB5d1xwOvBkwf0ZfJru3XuPk2aiks5obAuIgaJpZM4FPW3s.gif

@muafakul You can download the APK from the following URL: http://storage-public.realtime.co/tmp/RTMChat-release.apk

Thanks.
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

@muafakul You can download the APK from the following URL:
http://storage-public.realtime.co/tmp/RTMChat-release.apk
—
Reply to this email directly or view it on GitHub.<
https://ci3.googleusercontent.com/proxy/VkiGcbLP4AnFfzk3CYI6ip7c1MfAgSlLGZXFbOYh1OiEM6TZLrCtHCTg1t0Uf8_TTbxLOyiomEchNy8mTwrCnjHkEtazhUCGSgG0azOgqq8O25vuzOEgLZkC_OcBAfSJPQGDtIKGKkj6Qzg6kWZIrg7PmueAww=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYdUcMN49ir8-IJoj9k6XnRxI7YtUks5obtUJgaJpZM4FPW3s.gif

But when i posting ...it doesnot work
Jumat, 10 Juli 2015, shania junianatha<EMAIL_ADDRESS>menulis:

Thanks.
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

@muafakul You can download the APK from the following URL:
http://storage-public.realtime.co/tmp/RTMChat-release.apk
—
Reply to this email directly or view it on GitHub.<
https://ci3.googleusercontent.com/proxy/VkiGcbLP4AnFfzk3CYI6ip7c1MfAgSlLGZXFbOYh1OiEM6TZLrCtHCTg1t0Uf8_TTbxLOyiomEchNy8mTwrCnjHkEtazhUCGSgG0azOgqq8O25vuzOEgLZkC_OcBAfSJPQGDtIKGKkj6Qzg6kWZIrg7PmueAww=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYdUcMN49ir8-IJoj9k6XnRxI7YtUks5obtUJgaJpZM4FPW3s.gif

What doesn't work? Can you give us more details?
It's hard to help you with so little information.

On 10/07/2015, at 12:22, muafakul<EMAIL_ADDRESS>wrote:
But when i posting ...it doesnot work
Jumat, 10 Juli 2015, shania junianatha<EMAIL_ADDRESS>menulis:

Thanks.
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

@muafakul You can download the APK from the following URL:
http://storage-public.realtime.co/tmp/RTMChat-release.apk
—
Reply to this email directly or view it on GitHub.<
https://ci3.googleusercontent.com/proxy/VkiGcbLP4AnFfzk3CYI6ip7c1MfAgSlLGZXFbOYh1OiEM6TZLrCtHCTg1t0Uf8_TTbxLOyiomEchNy8mTwrCnjHkEtazhUCGSgG0azOgqq8O25vuzOEgLZkC_OcBAfSJPQGDtIKGKkj6Qzg6kWZIrg7PmueAww=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYdUcMN49ir8-IJoj9k6XnRxI7YtUks5obtUJgaJpZM4FPW3s.gif

—
Reply to this email directly or view it on GitHub.

I cant reply to others users
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

What doesn't work? Can you give us more details?
It's hard to help you with so little information.

On 10/07/2015, at 12:22, muafakul<EMAIL_ADDRESS>wrote:
But when i posting ...it doesnot work
Jumat, 10 Juli 2015, shania junianatha<EMAIL_ADDRESS>menulis:

Thanks.
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

@muafakul You can download the APK from the following URL:
http://storage-public.realtime.co/tmp/RTMChat-release.apk
—
Reply to this email directly or view it on GitHub.<

https://ci3.googleusercontent.com/proxy/VkiGcbLP4AnFfzk3CYI6ip7c1MfAgSlLGZXFbOYh1OiEM6TZLrCtHCTg1t0Uf8_TTbxLOyiomEchNy8mTwrCnjHkEtazhUCGSgG0azOgqq8O25vuzOEgLZkC_OcBAfSJPQGDtIKGKkj6Qzg6kWZIrg7PmueAww=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYdUcMN49ir8-IJoj9k6XnRxI7YtUks5obtUJgaJpZM4FPW3s.gif

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.<
https://ci3.googleusercontent.com/proxy/luTCOiRJs9erpuvWbyBBFpmnTzfjSWIsHPo_RG2pFmD2DMCjIR-MjgDN7AevLaETNVus_3YzqHhjHLLnfAJ1BhmSWjXZSMptaXYzwWx1dY44dioYCrVvK-upDR7zGhlatcKfPkoTHeukJdwvUFaNu_yZ05WPsQ=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYW28cSY0GJMt7UwYcybZTLNpTnMmks5ob6WhgaJpZM4FPW3s.gif

What do you mean? You have an error when replying to other users, is that it?
Please give us a fully detailed description of what is the issue otherwise it will be impossible to help you.

On 12/07/2015, at 00:28, muafakul<EMAIL_ADDRESS>wrote:
I cant reply to others users
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

What doesn't work? Can you give us more details?
It's hard to help you with so little information.

On 10/07/2015, at 12:22, muafakul<EMAIL_ADDRESS>wrote:
But when i posting ...it doesnot work
Jumat, 10 Juli 2015, shania junianatha<EMAIL_ADDRESS>menulis:

Thanks.
Jumat, 10 Juli 2015, Realtime Framework<EMAIL_ADDRESS>menulis:

@muafakul You can download the APK from the following URL:
http://storage-public.realtime.co/tmp/RTMChat-release.apk
—
Reply to this email directly or view it on GitHub.<

https://ci3.googleusercontent.com/proxy/VkiGcbLP4AnFfzk3CYI6ip7c1MfAgSlLGZXFbOYh1OiEM6TZLrCtHCTg1t0Uf8_TTbxLOyiomEchNy8mTwrCnjHkEtazhUCGSgG0azOgqq8O25vuzOEgLZkC_OcBAfSJPQGDtIKGKkj6Qzg6kWZIrg7PmueAww=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYdUcMN49ir8-IJoj9k6XnRxI7YtUks5obtUJgaJpZM4FPW3s.gif

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.<
https://ci3.googleusercontent.com/proxy/luTCOiRJs9erpuvWbyBBFpmnTzfjSWIsHPo_RG2pFmD2DMCjIR-MjgDN7AevLaETNVus_3YzqHhjHLLnfAJ1BhmSWjXZSMptaXYzwWx1dY44dioYCrVvK-upDR7zGhlatcKfPkoTHeukJdwvUFaNu_yZ05WPsQ=s0-d-e1-ft#https://github.com/notifications/beacon/AMePYW28cSY0GJMt7UwYcybZTLNpTnMmks5ob6WhgaJpZM4FPW3s.gif

—
Reply to this email directly or view it on GitHub.

Have you test the app ?? i iknow ..notyet.

Yes we did test it and it's working just fine. So it must be something particular to your device/emulator or network.
If you don't tell us what you are experiencing we can't troubleshoot it.

On 12/07/2015, at 02:08, muafakul<EMAIL_ADDRESS>wrote:
Have you test the app ?? i iknow ..notyet.
—
Reply to this email directly or view it on GitHub.


Add tutorial on hamiltonian symmetry

Title: Testing for symmetry with quantum computers
Summary: Test if a system possesses discrete symmetries
Relevant references: LaBorde and Wilde (2022, arxiv: 2203.10017)
Possible Drawbacks: Potentially could have meatier code, e.g. the variational alternative from the paper, but don't want to overwhelm the reader.
Related GitHub Issues: N/A

Thanks for the work! When you are ready let me know, I'll take care of the first review 😊

Will do! Just fixing the rst
On Wed, Nov 9, 2022 at 3:41 PM Guillermo Alonso-Linaje <
@.***> wrote:

Thanks for the work! When you are ready let me know, I'll take care of the
first review 😊
—
Reply to this email directly, view it on GitHub
https://github.com/PennyLaneAI/qml/pull/626#issuecomment-1309350401, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3FEV55ZNOQ5JB22H7Y6TN3WHQD6DANCNFSM6AAAAAAR3SQ3BY
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
xanadu.ai http://xanadu.ai/
"To build quantum computers that are
useful and available to people everywhere"
This e-mail message is
privileged, confidential and subject to
copyright. Any unauthorized use or
disclosure is prohibited.
Le contenu du présent courriel est privilégié,
confidentiel et
soumis à des droits d'auteur. Il est interdit de l'utiliser
ou
de le divulguer sans autorisation.


DateRangePicker - Type 'null[]' is not assignable to type 'RangeInput

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I just copied / paste this basic example: DateRangePicker
import * as React from 'react'
import TextField from '@mui/material/TextField'
import DateRangePicker from '@mui/lab/DateRangePicker'
import AdapterDateFns from '@mui/lab/AdapterDateFns'
import LocalizationProvider from '@mui/lab/LocalizationProvider'
import Box from '@mui/material/Box'

const DateRangeGraph = () => {
  const [value, setValue] = React.useState([null, null])

  return (
    <LocalizationProvider dateAdapter={AdapterDateFns}>
      <DateRangePicker
        startText="Check-in"
        endText="Check-out"
        value={value}
        onChange={(newValue) => {
          setValue(newValue)
        }}
        renderInput={(startProps, endProps) => (
          <React.Fragment>
            <TextField {...startProps} />
            <Box sx={{ mx: 2 }}> to </Box>
            <TextField {...endProps} />
          </React.Fragment>
        )}
      />
    </LocalizationProvider>
  )
}
export default DateRangeGraph

and I got this typescript error:

Type 'null[]' is not assignable to type 'RangeInput<null>'.
  Target requires 2 element(s) but source may have fewer.ts(2322)
DateRangePicker.d.ts(47, 5): The expected type comes from property 'value' which is declared here on type 'IntrinsicAttributes & Pick<DateRangePickerProps<null> & RefAttributes<HTMLDivElement>, keyof RefAttributes<...> | keyof DateRangePickerProps<...>> & Pick<...>'

We are using:
    "@mui/lab": "^5.0.0-alpha.54",
    "@mui/material": "5.1.0",

Expected behavior 🤔
No response
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

npx: installed 2 in 1.739s

  System:
    OS: macOS 11.5.2
  Binaries:
    Node: 12.18.3 - /usr/local/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.14.6 - /usr/local/bin/npm
  Browsers:
    Chrome: 95.0.4638.69
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.0
  npmPackages:
    @emotion/react: ^11.4.1 => 11.5.0
    @emotion/styled: ^11.3.0 => 11.3.0
    @mui/core:  5.0.0-alpha.54
    @mui/lab: ^5.0.0-alpha.54 => 5.0.0-alpha.54
    @mui/material: 5.1.0 => 5.1.0
    @mui/private-theming:  5.1.0
    @mui/styled-engine:  5.1.0
    @mui/system:  5.1.0
    @mui/types:  7.1.0
    @mui/utils:  5.1.0
    @types/react: 17.0.11 => 17.0.11
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2
    typescript: 4.3.4 => 4.3.4

I just copy the above code and run, it shows me an error at DateRangePicker:

But if I use StaticDateRangePicker according to docs it worked fine.
https://codesandbox.io/s/wxo51?file=/demo.js:125-146
I think DateRangePicker is not working properly in v5.

Hi, thanks for reporting this. The problem is caused by TS inferring the wrong type in useState. I'm going to update the demo.


Exec task fails in Windows Nano Server docker containers using MSBuild 15.3

Something in the Exec task is failing to launch basic command line processes in MSBuild 15.3, but only when running in Nano Server docker containers. This worked fine in MSBuild 15.1.
Repro
Install Docker for Windows and ensure "Windows containers" are used (not Linux containers).
Create a dockerfile like this and a file named test.proj.
FROM microsoft/dotnet-nightly:2.0.0-preview3-sdk-nanoserver
WORKDIR /app
COPY test.proj .
RUN dotnet msbuild test.proj

<!-- test.proj -->
<Project>
    <Target Name="Build">
        <Exec Command="dir" />
    </Target>
</Project>

Execute
docker build .

Expected
Build target runs and executed the "dir" command.
Actual
The dotnet msbuild test.proj command fails with:
C:\app\test.proj(3,9): error MSB6004: The specified task executable location "C:\Users\ContainerAdministrator\cmd.exe" is invalid.

Details
MSBuild version: <IP_ADDRESS>955 for .NET Core
Docker base image: microsoft/nanoserver:10.0.14393.1358
OS: Windows 10
Docker: 17.06
Environment variables inside the container:
PATH = C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Users\ContainerAdministrator\AppData\Local\Microsoft\WindowsApps;C:\Program Files\dotnet;
USERPROFILE = C:\Users\ContainerAdministrator

You can gather logs by launching a container with a volume mount to the folder containing the test.proj file.
docker run --rm -v "$(get-location):C:/app" -it -w C:/app microsoft/dotnet-nightly:2-sdk
C:\app> dotnet msbuild test.proj /bl

cmd.exe itself runs run, and is located in C:\Windows\system32\cmd.exe.
There is no file named C:\Users\ContainerAdministrator\cmd.exe
Full diagnostic log:
msbuild-2-sdk.txt
For comparision
This works just fine using MSBuild 15.1. Example
FROM microsoft/dotnet:1-sdk

WORKDIR /app
COPY test.proj .
RUN dotnet msbuild test.proj

msbuild-1-sdk.txt

A clue:
Environment.GetFolderPath(Environment.SpecialFolder.System) returns an empty string in Nano on .NET Core 2.0.0-preview3-25502-01

Yeah, that sure looks like the problem.

I'm less sure now. We have our own implementation of the locate-the-special-folder code.
I made this local change:
diff --git a/src/Shared/FileUtilities.GetFolderPath.cs b/src/Shared/FileUtilities.GetFolderPath.cs
index 315354fc..613cafbd 100644
--- a/src/Shared/FileUtilities.GetFolderPath.cs
+++ b/src/Shared/FileUtilities.GetFolderPath.cs
@@ -35,6 +35,8 @@ namespace Microsoft.Build.Shared
                                                       Win32Native.SHGFP_TYPE_CURRENT, /* dwFlags:   [in] retrieve current path */
                                                       sb);                            /* pszPath:   [out]resultant path */

+            Console.WriteLine($"ShGetFolderPath for {folder} returned {hresult} and gave up {sb.ToString()}");
+
             String s;
             if (hresult < 0)
             {
diff --git a/src/Utilities/ToolTask.cs b/src/Utilities/ToolTask.cs
index 38dcad86..985ccc6b 100644
--- a/src/Utilities/ToolTask.cs
+++ b/src/Utilities/ToolTask.cs
@@ -619,6 +619,8 @@ namespace Microsoft.Build.Utilities
                 // Otherwise, try to find the tool ourselves.
                 pathToTool = GenerateFullPathToTool();

+                Console.WriteLine($"** {pathToTool}");
+
                 // We have no toolpath, but we have been given an override
                 // for the tool exe, fix up the path, assuming that the tool is in the same location
                 if (pathToTool != null && !String.IsNullOrEmpty(_toolExe))

And get this output when plunking current 15.3 bits on top of CLI 1.0.4:
ShGetFolderPath for LocalApplicationData returned 0 and gave up C:\Users\ContainerAdministrator
ShGetFolderPath for LocalApplicationData returned -2147024693 and gave up C:\Users\ContainerAdministrator
ShGetFolderPath for ApplicationData returned 0 and gave up C:\Users\ContainerAdministrator
ShGetFolderPath for ProgramFiles returned -2147024693 and gave up C:\Users\ContainerAdministrator
ShGetFolderPath for ProgramFilesX86 returned 0 and gave up C:\Users\ContainerAdministrator
ShGetFolderPath for System returned 0 and gave up C:\Users\ContainerAdministrator
** C:\Users\ContainerAdministrator\cmd.exe
C:\app\test.proj(3,9): error MSB6004: The specified task executable location "C:\Users\ContainerAdministrator\cmd.exe" is invalid.

That should isolate against the runtime, but it's still failing.

Worked on MSBuild v<IP_ADDRESS>484

Apparently a regression from c113d5be19016ceef76b55107e6b16e0b920aabd (thanks, git bisect!). Investigating why.

Related: https://github.com/dotnet/corefx/issues/19110. CoreFX has similar calls and is getting bad results too--though that doesn't explain why this apparently started failing with a specific commit in MSBuild.

We can work around the problem by changing Exec.GenerateFullPathToTool to return %ComSpec% instead of ToolLocationHelper.GetPathToSystemFile("cmd.exe"). I'm not sure of the impact of changing the other calls, and would like to avoid doing this on any other environment given how late it is in the release, so I'm trying to find a good way to do that only on Nano Server.

Thanks @rainersigwald. I've verified this has been fixed in the aspnetcore Nano Server docker images.


create change-case extension

Description
create a change case extension
It is a wrapper for change-case.
Inspired by vscode-change-case
Type of change

New extension

Screencast
https://user-images.githubusercontent.com/72744903/137641165-d53a32c2-60bc-42f4-8f9f-d5fadb766fde.mp4
Checklist

[x] I read the documentation about publishing

Just realized I added the files to the wrong directory. Remaking the PR.


How to fail the webhook action

What is error handling supposed to look like for a webhook action? If my async process encounters an error, is there a magic string I can post to the callback to have the logic app webhook action fail?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 43127bca-9e45-47bc-8164-f7c0bd670fe3
Version Independent ID: 559964eb-d2eb-93fc-fd6a-8a8f63a3232e
Content: Wait and respond to events - Azure Logic Apps
Content Source: articles/connectors/connectors-native-webhook.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@sirdank Thank you for your feedback! We will review and update as appropriate.

Hello @sirdank
Per this Azure UserVoice item, you can set a timeout limit in your Webhook action's settings:

When this timeout limit is hit, Webhook action will gracefully fail the action and unsubscribe automatically.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Fix initcontainer script

Signed-off-by: zhu733756<EMAIL_ADDRESS>If the target path is unmouted, this script would be panic. Like the platform Kind.

Have some problems.  Fix like: " echo CONTAINER_ROOT_DIR=$(docker info -f '{{.DockerRootDir}}' 2> /dev/null) > /fluent-operator/fluent-bit.env"
I will revert it.


MINOR: fix RocksDBStore range search

The range is inclusive according to KeyValueStore's java doc.

Filed https://issues.apache.org/jira/browse/KAFKA-3220 for the Jenkins transient failure.
LGTM and merged to trunk.


time with milliseconds is not handled properly

Steps to reproduce:

        var duckDbCommand = connection.CreateCommand();
        duckDbCommand.CommandText = "select  now() as tme";
        var reader = duckDbCommand.ExecuteReader();
        reader.GetDateTime(0)

This will crash with below error
"Valid values are between 0 and 999, inclusive. (Parameter 'millisecond')"
now function returns time with milliseconds. If specifying time without milliseconds  (e.g. TIMESTAMP '1992-09-20 20:38:40' ) GetDateTime works correctly

Fixed in #93


lwsmd/lwio Service Crashes in Cross-domain Trust scenario

Version: pbis-open-8.5.4-334.x86_64
OS/Distro: RHEL 6.9
Issue/Impact:
**We have a setup that involves two AD domains: a user domain, U, and a resource domain R. There is a one-way trust between the U domain and the R domain, with the R domain being the trusting domain. Our Linux machines are added to the R domain. We create resource groups in the R domain which contain users from the U domain. The resource groups are added to the RequireMembershipOf attribute. We do have a few user accounts in the 'R' domain as a backdoor in case the trust relationship to 'U' is broken. The 'U' domain is hosted in a co-lo data center. The 'R' domain is hosted in an AWS environment and the two communicate via a VPN connection. The domain logins are only used for administrative tasks on the server. They are not used by the applications running on them.
We wanted to eliminate the need for administrators from the U domain to log in using the domainName\Username format and just use user name. Thus, we set the 'UserdomainPrefix' setting to 'U' in PBIS.
We noticed that after a few days, we ended up being unable to log into our boxes, regardless of whether we were using a domain or local account. We had to reboot them. When we checked the messages log, we found the following.
Once we undid the change and switched the Userdomainprefix back from 'R' from 'U', the errors went away and things started behaving normally.
So our hunch is that setting the UserdomainPrefix to 'U' may have resulted the guest trying to resolve all logon attempts against domain first. We thought that PBIS is only involved when a user logs into the system. But it seemed to be doing something once that value changed that ended up crashing the service, even if users weren't trying to log in. All we had to do is let a server sit there for a while and after a few days, we would be unable to log in. SSH never even got to the password prompt.
Unfortunately, abrt wasn't configured to actually do a core dump for libraries that aren't managed by Redhat. PBIS being a third party, it refused to do the dump. So we'd have to reconfigure abrt to perform core dump even if a libary doesn't have Redhat signature.
Any idea why a userdomainprefix change could result in service crashes?
Output/Error:
*Dec  4 13:14:15 vertica3 /opt/pbis/sbin/lwsmd: Restarting dead service: lwio (attempt 2/2)
Dec  4 13:14:15 vertica3 abrtd: Package 'pbis-open' isn't signed with proper key
Dec  4 14:36:59 vertica3 abrt[9025]: Saved core dump of pid 109062 (/opt/pbis/sbin/lwsmd) to /var/spool/abrt/ccpp-2017-12-04-14:36:55-109062 (559874048 bytes)
Dec  4 14:36:59 vertica3 /opt/pbis/sbin/lwsmd: Restarting dead service: lwio (attempt 2/2)
Dec  4 14:36:59 vertica3 abrtd: Package 'pbis-open' isn't signed with proper key
Dec  4 15:56:14 vertica3 abrt[36605]: Saved core dump of pid 9043 (/opt/pbis/sbin/lwsmd) to /var/spool/abrt/ccpp-2017-12-04-15:56:10-9043 (549326848 bytes)
Dec  4 15:56:14 vertica3 /opt/pbis/sbin/lwsmd: Restarting dead service: lwio (attempt 2/2)
Dec  4 15:56:14 vertica3 abrtd: Package 'pbis-open' isn't signed with proper key
Dec  5 04:28:10 vertica3 /opt/pbis/sbin/lwsmd: lwsmd timer expired, executing timer expired action.
Dec  5 04:28:10 vertica3 /opt/pbis/sbin/lwsmd: Service failed to start: lsass
Dec  5 04:28:10 vertica3 /opt/pbis/sbin/lwsmd: Could not shut down service; ignoring error: LW_ERROR_SERVICE_UNRESPONSIVE (41203)#012
Dec  5 04:28:51 vertica3 /opt/pbis/sbin/lwsmd: Logging started
Dec  5 04:32:46 vertica3 /opt/pbis/sbin/lwsmd: Logging started

We are unaware and need time to investigate. For now I'm going to mark this as a bug

Please upgrade to Active Directory Bridge Enterprise. If the issue still exists then please submit a ticket to our service team and we’ll have a look for you.
pbis-open will longer receive updates and will be archived. Closing all outstanding issues. Please consider BeyondTrust Active Directory Bridge for continued support.
https://www.beyondtrust.com/privilege-management/active-directory-bridge


docs: Update workflow name of release.yml

The author should do the following, if applicable

[ ] Add tests
[ ] Run tests
[ ] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

@siguici Thanks!


[AMD] Introduce a CanonicalizePointer pass

In order to support buffer operations (see Chapter 9 of the MI300 ISA reference) the pointers we feed to the buffer_load/buffer_store instructions need to be constant across the threads.
This means that they have to point at some base address. The only thing that can vary per-thread is the offset.
If the base address is divergent (i.e., it is different per each thread) the LLVM backend will emit a waterfall loop (i.e., for i=0:64: mask all the threads except the i-th; buffer_load for thread i)
This pass is canonicalizing the pointers across the IR, in this <basePtr,offset> style.

Propagate an offset across the IR associated with the given pointer. For each operation that makes use of a pointer we replace the pointer with the basePtr  and we add an offset operand that tracks where the pointer is.
We replace tt.addptr %ptr, %offset with %newOffset = arith.add %base_offset, %offset and propagate newOffset
We materialize tt.addptr only before a tt.load or a tt.store operation.

This PR only adds this canonicalization. A subsequent PR will run this pass just before translating TritonIR into LLVMIR (and if the pass succeeds, we will enable buffer operations).
Note: enabling buffer operations will give us a way to support masking without having to emit branches.

cc @sjw36

Looks good overall.
For call support you can handle like load/store for now.

I can, but the reason I didn't is because I thought that if every function is root, nothing can be can called.

The test needs to moved to test/Triton since it's operating on the triton IR level.

I refactored the pass. Now the CanonicalizePointer pass is calling into PointerCanonicalization::run(). The reason why I did that is to decouple the pass failure from analysis results. Now the pass will always work (unless the IR is in a bad state). Additionally, two flags will be used (while lowering Load/Store ops) to decide if we can effectively use buffer operations (namely, hasUnknownOp and has64BitOffset)
I also corrected some bugs I found while I was trying to use that on all different kinds of IRs
Finally, Re: test location:
@zhanglx13 , I don't have a strong opinion, but the reasoning is the following:

This pass will run before conversion to LLVM, so it will always run on TritonGPU IR
It's true that it "can" run on TritonIR (because it's not specific to blocking, etc...), but I think that test/Triton is used for backend-agnostic passes, while this will be run only for AMD. I mean, if people don't build Triton with AMD support, the pass won't be available
I could move the test in a test/Triton/amd folder, but I fear people may want the test/Triton folder to contain only backend-agnostic passes

This pass will run before conversion to LLVM, so it will always run on TritonGPU IR

This confuses me because the test you added is triton IR.
If you plan to apply this pass at tritongpu IR, you need to add tests with tritongpu IR.

This confuses me because the test you added is triton IR. If you plan to apply this pass at tritongpu IR, you need to add tests with tritongpu IR.

Can you elaborate on the differences? Do I need to add the blocked encoding?

Yes, ok, I see the point.

The pass does not care about block encodings. So it could be a Triton IR pass
The pass is always run on tritonGPU IR (before llvm conversion)
The pass is executed only by the AMD backend, and this is why I put it third_party/amd.

So I think there are two options:

We add the pass as a generic Triton pass (not in third_party/amd) and we move the test to be a generic Triton test
We add the pass as an AMD backend specific pass, hence we have to cast the test to be a TritonGPU test (which will run only on AMD backend)

What do you guys think?

We add the pass as a generic Triton pass (not in third_party/amd) and we move the test to be a generic Triton test

For this option, you need to make sure the result of the pass is not "reverted" by later passes.
And we can make it a generic pass but only add it to make_ttir() in the amd's compiler. So this way, it's generic, but acts like an AMD specific pass.
For me, it seems simpler to add it at Triton IR level if the effect can be preserved.

I don't think the effect can be preserved but I also I need the pass to be executed during llvm conversion, because I need to know information about the IR (e.g., if the offsets are 64 bits or 32 bits). However, I think I  can still add it as a generic pass, add the test in test/triton and then instead of calling it in make_ttir I will call it before the llvm conversion (like I do here)

I don't think the effect can be preserved but I also I need the pass to be executed during llvm conversion, because I need to know information about the IR (e.g., if the offsets are 64 bits or 32 bits). However, I think I can still add it as a generic pass, add the test in test/triton and then instead of calling it in make_ttir I will call it before the llvm conversion (like I do here)

If you call it before the llvm conversion it means this pass applies at tritonGPU level, and then it should go to test/TritonGPU/

If you call it before the llvm conversion it means this pass applies at tritonGPU level, and then it should go to test/TritonGPU/

The idea behind the pass is that it is acting like a canonicalization. So it can work on both triton and tritonGPU dialects.
It can be run everywhere, but to be sure that we have the pointers ready to be used with buffer ops, it needs to be executed before llvm conversion.

Anyway, my opinions about tests are never strong. So I added a blocked layout to the tests. As I said, the pass does not care about that, it will work on any triton/tritonGPU IR, but it needs to run before the llvm translation.

Hi @antiagainst , thanks for the review! Let me address the main topics here:

This is a delicate change due to the i64/i32. Need to guarantee correctness. You listed three cases there. Those make sense to me. I suppose the third one will be quite useful in reality. I'm fine to just implement the first two to have the overall structure though. There is also a forth one as we chatted where we can use tl.assume to let the developer provide range information regarding those indices so it can work for i64 indexing types in the source code too.

The problem with the tl.assume is that since Triton is a Tensor IR, the assumptions would need to me bade very specific. Let me clarify. In TritonIR the program_id is the id of the thread within the block, which is a 2D concept. Hence the program_id will be multiplied by the block_size and then strided. So for instance here:
    offs_cm = pid_m * BLOCK_SIZE_M + tl.arange(0, BLOCK_SIZE_M)
    offs_cn = pid_n * BLOCK_SIZE_N + tl.arange(0, BLOCK_SIZE_N)
    c_ptrs = c_ptr + stride_cm * offs_cm[:, None] + stride_cn * offs_cn[None, :]

It seems hard to understand what generic assumptions on stride_cm should be made to not overflow. And these will be very specific to the kernel we are building, which goes a bit against the dynamic size kernels we are trying to generate. And this the reason why I didn't list the assumption solution as a possibility.

We are upcasting to i64 and then downcasting to i32 back.. I kinda understand your purpose there but is it really necessary? If we fails to accumulate as i32, we need to abort anyway. And upcasting to perform indexing calculation in i64 comes with as costs.

So, in theory this pass should never "abort". It will still simplify pointer arithmetic, moving "constant" pointer updates to scalar adds and pushing all the pointer arithmetic on the offset. The pointer arithmetic is already happening in 64 bits (because the pointer is 64 bits), so it should do no harm. Now there are two possibilities:

The 64 bits offset is always casted down before being used. At this point canonicalization should do the right thing and cast everything to 32 bits.
The 64 bits is only sometimes casted down before being used. In this case, we need to stick with the conversions. But we do need the cast anyway, because this will allow us to inject buffer operations.

One thing is signedness. If I'm reading the ISA spec correctly, those SGPR_offset and VGPR_offset are unsigned values (in "Table 44. Address Components from GPRs" of MI300X ISA doc), but the offsets in triton is not guranteed to be that? We can have negative values from the source program that'd be interpreted wrongly? Do we need tl.assume( >= 0) to have the pass work?

I am not sure we need this assumption. Because in the buffer operation pass, I take this pair of instruction (in LLVMIR):
%ptr0 = gep %ptr[%offset]
%data = global_load(%ptr0)

And translate them into:
%data = buffer_load(%ptr0, %offset)

So the offset should not be negative in this case, because this is the offset we use to load data from memory, and we made sure that all the pointer updates were done on the offset.
So yes, at a particular point a gep might have a negative offset. But the sum of all those offsets (which is presented to the load) should be positive overall.

The problem with the tl.assume is that since Triton is a Tensor IR, the assumptions would need to be made very specific. Let me clarify. In TritonIR the program_id is the id of the thread within the block, which is a 2D concept. Hence the program_id will be multiplied by the block_size and then strided. So for instance here:

offs_cm = pid_m * BLOCK_SIZE_M + tl.arange(0, BLOCK_SIZE_M)
offs_cn = pid_n * BLOCK_SIZE_N + tl.arange(0, BLOCK_SIZE_N)
c_ptrs = c_ptr + stride_cm * offs_cm[:, None] + stride_cn * offs_cn[None, :]

It seems hard to understand what generic assumptions on stride_cm should be made to not overflow. My fear is that these will be very specific to the kernel we are building, which goes a bit against the dynamic size kernels we are trying to generate. And this the reason why I didn't list the assumption solution as a possibility.

First of all, program_id is the block id in the grid. Triton does not expose thread id.
It should also be safe to assume stride_cm = N and stride_cn = 1 given the C tensor is always row major. And for other values like pid_m and pid_n, they all can be pre-computed before the kernel given the inputs.
If such information is so important and hard to figure out at compile time, maybe we can pre-compute something based on these values and use tl.assume() on it? E.g. tl.assume(N < 1048576) so that the compiler should know stride_cm only needs 20 bits.

I did not check the implementation of this PR, but spend some time playing with the tests.
According to the intention of this PR, the current pointer arithmetic is not friendly to buffer_load instructions and this PR is trying to massage the IR into the buffer_load-friendly format.
Please correct me if I'm wrong. I can see from the tests this PR is trying to guarantee two things about the load instruction
%ptr = tt.addptr %base, %off
%result = tt.load %ptr

%base must come from a tt.splat op, so that threads in the same wave are using the same base address.
%off must be i32

If my understanding is correct, then it should be easy to achieve this at python level.
The current way of address calculation:
offs_k = tl.arange(0, BLOCK_SIZE_K)
offs_am = pid_m * BLOCK_SIZE_M + tl.arange(0, BLOCK_SIZE_M)
a_ptrs = a_ptr + offs_am[:, None] * stride_am + offs_k[None, :] * stride_ak

which is problematic since offs_am[:, None] will first be added to the a_ptr, which leads to an early splat of the pointer.
Therefore, we can compute the offset first
offs_k = tl.arange(0, BLOCK_SIZE_K)
offs_am = pid_m * BLOCK_SIZE_M + tl.arange(0, BLOCK_SIZE_M)
a_ptrs = a_ptr + (offs_am[:, None] * stride_am + offs_k[None, :] * stride_ak)

Then the pointer will be only splatted once right before the final tt.addptr.
And the final offset of the tt.addptr is naturally i32.
I'm NOT trying to say we should do this at python level and abandon this PR. I'm suggesting that we can take some information/hint from the python code and simplify the logic.
For example, regarding offset range. The max offset we can have here is MxK. And we only want MxK < 2^32, which should cover most of the gemm sizes we care about.
And we can further reduce the offset by doing
offs_k = tl.arange(0, BLOCK_SIZE_K)
offs_am = tl.arange(0, BLOCK_SIZE_M)
a_ptr_new = a_ptr + pid_m * BLOCK_SIZE_M * stride_am
a_ptrs = a_ptr_new + (offs_am[:, None] * stride_am + offs_k[None, :] * stride_ak)

In this case, a_ptr_new will be the base pointer of the tile. And we only need BLOCK_M x K < 2^32.

The problem with the tl.assume is that since Triton is a Tensor IR, the assumptions would need to be made very specific. Let me clarify. In TritonIR the program_id is the id of the thread within the block, which is a 2D concept. Hence the program_id will be multiplied by the block_size and then strided. So for instance here:

I have the same opinion as what @zhanglx13 had in the following--we can rely on tl.assume over the scalar kernel arguments, because they are the source of all downstream tensor computations. Though a few comments in @zhanglx13's points too:

It should also be safe to assume stride_cm = N and stride_cn = 1 given the C tensor is always row major.

This might not the the case--these values are passed in as kernel parameters. Normally what you said is true but not always guaranteed.

And for other values like pid_m and pid_n, they all can be pre-computed before the kernel given the inputs.
If such information is so important and hard to figure out at compile time, maybe we can pre-compute something based on these values and use tl.assume() on it? E.g. tl.assume(N < 1048576) so that the compiler should know stride_cm only needs 20 bits.

+1. I think we should tl.assume on the source scalar values.

So, in theory this pass should never "abort". It will still simplify pointer arithmetic, moving "constant" pointer updates to scalar adds and pushing all the pointer arithmetic on the offset. The pointer arithmetic is already happening in 64 bits (because the pointer is 64 bits), so it should do no harm. Now there are two possibilities:

The 64 bits offset is always casted down before being used. At this point canonicalization should do the right thing and cast everything to 32 bits.
The 64 bits is only sometimes casted down before being used. In this case, we need to stick with the conversions. But we do need the cast anyway, because this will allow us to inject buffer operations.

Okay I think the above makes sense--it's simpler to write a pass in this way. And I guess even if we cannot downcast it still helps over performance because we separated out the warp-uniform indexing calculation so less chances to confuse LLVM backend I guess so likely better CodeGen.

So the offset should not be negative in this case, because this is the offset we use to load data from memory, and we made sure that all the pointer updates were done on the offset.
So yes, at a particular point a gep might have a negative offset. But the sum of all those offsets (which is presented to the load) should be positive overall.

I'm not so sure about this assumption. I don't think triton forbids negative strides? If strides are negative we just read data in the reverse way?

So the main topics of discussion (I think) are:

E.g. tl.assume(N < 1048576) so that the compiler should know stride_cm only needs 20 bits.

We can try to play with this. But the problem I was underlying is that, in this expression:
offs_cm = pid_m * BLOCK_SIZE_M + tl.arange(0, BLOCK_SIZE_M)
offs_cn = pid_n * BLOCK_SIZE_N + tl.arange(0, BLOCK_SIZE_N)
c_ptrs = c_ptr + stride_cm * offs_cm[:, None] + stride_cn * offs_cn[None, :]

If stride_cm,stride_cn <= 20 bits and pid_m<=9bits(8 warps) we have that offs_cm = (9+7) + 1 = 19 bits (I assume BLOCK_SIZE_M=128) which means that  stride_cm * offs_cm<=20+19 bits=39bits which would not fit. We can assume stride_cm<10 bits, and that would work, but it would not satisfy (say) 8k matrices. So basically different matrix sizes would need different assumptions to make sure everything fits. This is what I meant when I was saying we could loose generality. This is because we have the stride that needs to be applied to the pid, being Triton a Tensor IR.

I'm suggesting that we can take some information/hint from the python code and simplify the logic.

Yes, I agree on that. For now, the user needs to structure the code in a specific way in Python, like adding parenthesis around the (non-uniform) pointer update. Remember that there are also some uniform updates to the pointers and these need to be moved to the scalar pointer (by the pass), otherwise we would end up with a waterfall loop (killing performance).
Let me repeat that, if we had the pass also in LLVM we could do that more generally (without assumptions, and without having the user to write specific python code).

I'm not so sure about this assumption. I don't think triton forbids negative strides? If strides are negative we just read data in the reverse way?

It might be (not sure if this is implemented), but it doesn't read "before" the pointer. I mean, Triton will still load data after the start of the buffer. What I am saying is that if you write (in python):
a = tensor[-10:0]

It will generate a LLVM load like llvm.load(tensor_ptr + tensor_size-10). The load always reads "after" the raw pointer. We could have a chat about this specific point?
Finally, let me underline that while this pass will be beneficial to inject buffer loads, moving the workgroup-uniform pointer arithmetic to the scalar pointer and the workgroup-non-uniform pointer arithmetic to an integer offset should be beneficial in general.

If stride_cm,stride_cn <= 20 bits and pid_m<=9bits(8 warps) we have that offs_cm = (9+7) + 1 = 19 bits (I assume BLOCK_SIZE_M=128) which means that  stride_cm * offs_cm<=20+19 bits=39bits which would not fit. We can assume stride_cm<10 bits, and that would work, but it would not satisfy (say) 8k matrices. So basically different matrix sizes would need different assumptions to make sure everything fits. This is what I meant when I was saying we could loose generality. This is because we have the stride that needs to be applied to the pid, being Triton a Tensor IR.

The max offset you need (when you address the very last element in the tensor) is max_off=max(M x N, M x K, N x K). So if max_off < 2^32, we should have 32-bit offset. 8K x 8K is definitely within the range.

@antiagainst , I applied your comments. PTAL


Is NVD api host in throubles?

Our ci jobs are  not finishing because they exceed the timeout of one hour. The task of updating the NVD database (for the first time) does not finish. In one hour, only 20%. Do you know if there is a problem?
INFO] NVD API has 264,240 records in this update
[INFO] Downloaded 10,000/264,240 (4%)
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=10000 : 2 time
[INFO] Downloaded 20,000/264,240 (8%)
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=18000 : 2 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=32000 : 2 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=36000 : 2 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=18000 : 3 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=32000 : 3 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=38000 : 2 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=36000 : 3 time
[INFO] Downloaded 30,000/264,240 (11%)
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=32000 : 4 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=38000 : 3 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=36000 : 4 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] NVD API request failures are occurring; retrying request for the 6 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=38000 : 4 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] NVD API request failures are occurring; retrying request for the 6 time
[WARNING] NVD API request failures are occurring; retrying request for the 6 time
[WARNING] NVD API request failures are occurring; retrying request for the 7 time
[WARNING] NVD API request failures are occurring; retrying request for the 6 time
[WARNING] NVD API request failures are occurring; retrying request for the 7 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] NVD API request failures are occurring; retrying request for the 6 time
[WARNING] NVD API request failures are occurring; retrying request for the 7 time
[WARNING] NVD API request failures are occurring; retrying request for the 8 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=34000 : 2 time
[WARNING] NVD API request failures are occurring; retrying request for the 6 time
[WARNING] NVD API request failures are occurring; retrying request for the 7 time
[WARNING] NVD API request failures are occurring; retrying request for the 7 time
[WARNING] NVD API request failures are occurring; retrying request for the 8 time
[WARNING] NVD API request failures are occurring; retrying request for the 8 time
[WARNING] NVD API request failures are occurring; retrying request for the 9 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=34000 : 3 time
[WARNING] NVD API request failures are occurring; retrying request for the 7 time
[WARNING] NVD API request failures are occurring; retrying request for the 8 time
[WARNING] NVD API request failures are occurring; retrying request for the 8 time
[WARNING] NVD API request failures are occurring; retrying request for the 9 time
[WARNING] NVD API request failures are occurring; retrying request for the 9 time
[WARNING] NVD API request failures are occurring; retrying request for the 10 time
[WARNING] NVD API request failures are occurring; retrying request for the 9 time
[WARNING] NVD API request failures are occurring; retrying request for the 10 time
[WARNING] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=34000 : 4 time
[WARNING] NVD API request failures are occurring; retrying request for the 5 time
[WARNING] NVD API request failures are occurring; retrying request for the 8 time
[WARNING] NVD API request failures are occurring; retrying request for the 9 time
[WARNING] NVD API request failures are occurring; retrying request for the 10 time
[WARNING] NVD API request failures are occurring; retrying request for the 11 time

No issues seen on my side. We have a job that runs (with API key) every 4 hours to take in NVD API updates that are stored in the cveDB on the data folder on a persistent share on our CI environment.
Your logs indicate that you don't have such a persistent share, as it has the full 260k+ entries to download. You should cache the data folder of dependency-check across runs in order to play nicely with NVD rather than abusing their service to reload full dataset on each scan.
See also what NVD themselves have to say about using their API responsibly at https://nvd.nist.gov/general/news/API-Key-Announcement


update kube and openapi

Hi @imp any chance this could be merged? It's just dependency bump :)

Sure, thanks for nudging me


[FEATURE] Windows support

Any chance for native windows support?
Currently it runs fine in WSL but natively it fails to import
AssertionError: This file should end with 'meerkat/meerkat/constants.py'.

I don't know much about Windows -- do you have a sense of what that would require to support?

We are currently working on Windows support. We'll leave updates here.


Fix: infinite loop possible in sample builder

Active becomes "empty" after consuming the packets, but instead of the
"filled" getting purged by "purgeConsumedBuffers", it doesn't because
active is now empty and empty buffers cannot cause any purging. So the
solution is to purge the "consumed" area first, then "active".
Description
Reference issue
Fixes #1810

:fire:
Your reasoning sounds perfect to me! Would it be possible to add a test that would have failed/OOM before? Even if it touches private APIs better then nothing :)

Yes, I think I can/will. It's a bit more complicated because it only happens in a perfect storm of things but obviously it's frequent enough if two people hit it.

@Sean-Der I added a test which would fail without this fix as you requested.

@robin-raymond fantastic! Thank you so much :)

Closed by f7f760f8c6e2f1aba1bf7c544fdd84d70f6e05b6 (squashed into one)


use relative link

switch to relative link for /bin/ponyc, /lib/libponyrt.a /lib/libponyc.a
and /include/pony.h (instead of absolute link). Ensure that installation using fakeroot (like
makepkg) don't create link to fakeroot directory

Test failure is unrelated - I'm merging.
Thanks!


feat: premium membership

The premium membership system shall be implemented with the Stripe payments system.

[ ] Free tier will give 50 song recognition credits to a server per month.
[ ] Server-Paid* tiers will give every WHITELISTED user in a server the ability to recognise songs for:

[ ]  Pro $2.49 a month for 4500 credits a month

[ ] Absolute $5.99 a month for 15000** credits

In all cases, one credit equals one song recognition.
*Include discount codes for the first six months of the offering. Annual payments will have a 20% discount.
**15000 is essentially unlimited, as radios will only play as many as 10,800 songs per month.

It's been a couple of weeks since we released this feature, and here are the stats:

Users have called the recognize command 181 times, with a 0% error rate and 1100ms average latency.
Our links implementation is broken.


Update dkim.md

Description of the change: I just added a couple of sentences to better explain the Private Key and Public Key role in DKIM.
I added that the sending email server uses a Private Key to generate the signature and the receiver system uses the Public Key to verify that the signature was generated by the matching Private Key.
Reason for the change: Concept of Private and Public Key was not very clear
Link to original source: Reference: https://dl.icewarp.com/online_help/341.htm

Closes #

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


store final output (clusters) in sql instead of returning to memory

requires storing fapi predictions on full_distances in memory; this would mean no longer need fit_model() in oagdedupe.api


refetchOnWindowFocus rerenders

I noticed refetchOnWindowFocus fires many rerenders.
There is a sample here: https://codesandbox.io/s/refetchonwindowfocus-test-xxsf5
Notice it will console.log many times on each windowFocus. Is this the expected behavior?

Initially, I thought it has something to do with the iframe focus (As Codesandbox uses it). But I could reproduce the above issue in the app I'm working on too (No Iframes).
The network call is being made only once, but It re-renders 3 times.

A rerender is triggered for every state change in react query. So mount, fetch start, loading, success, etc. no different than if you were to use useState with useEffect to fetch data.


Stability of Kinetic Branch

@tonybaltovski there have been a lot of questions online regarding the stability of the kinetc branch of software in regards to both the simulation and hardware environments. When pulling from the repository and building from source there aren't any issues, however, there are tons of issues during execution.  Is the kinetic branch stable or is there another preferred branch? Is there a gazebo version that these branches have been developed against?

Which errors are you referring to?

Closing due to inactivity.  Please feel free to re-open if issue persists.


Jest causes ESLint's getConfigForFile to error under Node 6

I have a project that depends on eslint and runs tests using Jest. We've noticed an issue when running our tests under Node 6, and I think it might be a bug in Jest. We have an issue tracking this here: https://github.com/Galooshi/import-js/issues/272
I've created a minimal repro case that reproduces this issue: https://github.com/lencioni/jest-eslint-node6-bug
The following code works when run outside of jest:
var eslint = require('eslint');

var cli = new eslint.CLIEngine();
cli.getConfigForFile('foo.js');

However, in a jest test, under Node 6+, it causes a runtime error:
Using Jest CLI v12.1.0, jasmine2
 FAIL  __tests__/index-test.js
● Runtime Error
  - TypeError: Cannot read config file: /Users/joe/jest-eslint-node6-bug/.eslintrc.js
    Error: Path must be a string. Received undefined
        at assertPath (path.js:7:11)
        at Object.dirname (path.js:1324:5)
        at module.exports (node_modules/require-uncached/index.js:11:34)
        at loadJSConfigFile (node_modules/eslint/lib/config/config-file.js:161:16)
        at loadConfigFile (node_modules/eslint/lib/config/config-file.js:200:22)
        at Object.load (node_modules/eslint/lib/config/config-file.js:494:18)
        at loadConfig (node_modules/eslint/lib/config.js:64:33)
        at getLocalConfig (node_modules/eslint/lib/config.js:126:23)
        at Config.getConfig (node_modules/eslint/lib/config.js:227:22)
        at CLIEngine.getConfigForFile (node_modules/eslint/lib/cli-engine.js:777:29)
1 test suite failed, 0 tests passed (0 total in 1 test suite, run time 0.823s)

This does not happen in Node versions before 6.

eslint depends on require-uncached, which depends on caller-path, which depends on callsites, which under this version of Node is not working as expected in the Jest test. I've updated my local copy of callsites to their latest version on master and that did not resolve the issue.

As a workaround, I tried to change my project's .eslintrc.js file to .eslintrc, but this also seems to affect plugins:
● Importer › #fixImports › when an unused variable that shares its name with an import exists › it does not display any message
  - TypeError: Cannot read config file: /Users/joe/import-js/node_modules/eslint-plugin-react/index.js
    Error: Path must be a string. Received undefined
    Referenced from: /Users/joe/import-js/.eslintrc
        at assertPath (path.js:7:11)
        at Object.dirname (path.js:1324:5)
        at module.exports (node_modules/require-uncached/index.js:11:34)
        at loadJSConfigFile (node_modules/eslint/lib/config/config-file.js:161:16)
        at loadConfigFile (node_modules/eslint/lib/config/config-file.js:200:22)
        at load (node_modules/eslint/lib/config/config-file.js:494:18)
        at eval (node_modules/eslint/lib/config/config-file.js:386:36)
        at Array.reduceRight (native)
        at applyExtends (node_modules/eslint/lib/config/config-file.js:363:28)
        at Object.load (node_modules/eslint/lib/config/config-file.js:525:22)

argh, I'm confident the problem here is that eslint depends on some other undocument module APIs that I haven't added to Jest (because they are undocumented). I'll try to figure out where exactly this is coming from.

It might be worth looking at callsites, which does some funky things with error stacktraces.

Same issue for me using Jest 12.1.1. Not only getConfigForFile, but also any option on CLIEngine that takes a configuration, like configFile or baseConfig.

This looks like a JSDOM bug. I noticed that the filenames from modules run in the vm are missing and this is likely because of jsdom's eval which doesn't allow to set the filename properly. I filed a bug in the jsdom issue tracker: https://github.com/tmpvar/jsdom/issues/1509
Workaround: if you are not using doing any DOM tests, you can switch to the node environment:
In your config:
  "jest": {
    "testEnvironment": "node"
  },

The nice thing about this is that it will also speed up the startup time of Jest by 500ms, making your test suites way faster ;) If you have DOM tests and code tests for things like eslint, I recommend making two separate Jest configs for both. We are also working on a multi-runner so tying them together in CI will be easy. I'm also happy to accept a PR that will allow to set the environment on a per-test basis like:
/**
 * @jest-environment node
 */

I'll close this task and will track the bug in jsdom and make and changes to Jest if necessary. Sorry that I can't resolve this right away.

Thanks @cpojer! Adding that config option does the trick for us.


html + dart2js: annotate Element.getBoundingClientRect() with implementation type

Annotating it with @Returns("_ClientRect") will avoid interceptor calls on the use of the rectangle.

Fixed by 9c3d439b1e63012af6158db320e6a2874e48d44b


Add workflow tests

Codecov Report

Merging #210 (76bc057) into main (0df628c) will increase coverage by 1.57%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #210      +/-   ##
==========================================
+ Coverage   73.92%   75.49%   +1.57%
==========================================
  Files         188      190       +2
  Lines        7443     7555     +112
==========================================
+ Hits         5502     5704     +202
+ Misses       1941     1851      -90

Impacted Files
Coverage Δ

config/settings/test.py
90.00% <100.00%> (+2.19%)
:arrow_up:

leavers/workflow/tests/test_leaving_workflow.py
100.00% <100.00%> (ø)

leavers/workflow/leaving.py
100.00% <0.00%> (ø)

leavers/workflow/tasks.py
61.05% <0.00%> (+3.22%)
:arrow_up:

activity_stream/models.py
92.00% <0.00%> (+24.00%)
:arrow_up:

leavers/utils/emails.py
62.06% <0.00%> (+44.13%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[Design] POStringLocalizer

This is a design PR for the POStringLocalizer work. Missing from the is the pluralization work (other than just to parse the file) because we haven't decided on what the shape of IPluralizedStringLocalizer is.

Finally we have it 😄 , great job @ryanbrandenburg I appreciate it.
One thing why we didn't finalize the pluralization stuff after that build this on top of that, as we know PO files support pluralization by its nature

@ryanbrandenburg can you fix the checks failure?

@ryanbrandenburg It will be nice if POLocalizer implement IPluralizeStringLocalizer that I suggest in PR #305 instead of IStringLocalizer because it doesn't support pluralization, so that's why you need to do it yourself in each implementation that may support pluralization. My aim to eliminate the tedious and repetitive code that we wrote in such cases.
Second thing the amount of code to parse PO is too much, can we simplify this like what we did in INI configuration as example?

@sebastienros is that mean that POStringLocalizer will not be supported?!!

Fortunately no. It's just that this branch required more changes so it will be started fresh.

I see, furthermore I saw that implementation is complicated little bit, It would be nice if we can simplify parsing like what I have seen in INI Configuration
thanks


Default Branch Name is always master when creating new project

VS Code Version: 1.93
OS Version: Windoes_NT x64 10.0.22631
Steps to Reproduce:
Command Palatte
Azure Functions: Create New function
(walk through)
After the project is created the default branch is master even though the VS Code setting for Git: Default Branch Name is "main"

Hi @robinhalabicki
I don't think that the Functions extension is the one initializing the git repository. How are you initializing it?

I am not, I literally create the function using the Palette.   Then the git extension shows its default branch is master, even though the setting is main in the settings

Could you tell me your git version?
git -v

git version 2.45.1.windows.1

Weird. Maybe the folder that you're in has a parent folder that has a git repository with the master branch? I really have no idea why it's doing that, but it should be unrelated to the Functions extension since we don't initialize the repository for the user.

I wondered that too.
But,
if I open Git Desktop and create a new folder for new local repo, it defaults to main
if I open VS Code, open folder, create new folder, click on the source control, click initialize, it defaults to main
if I open VS Code, open folder, create new folder, CTRL+SHIFT+P, Create new function, walk through, it defaults to 'master'

My teammate fact-checked me thankfully. I forgot, we do initialize a repo if you don't have one on create: https://github.com/microsoft/vscode-azurefunctions/blob/010c071035bb6a8e441741b3a9912497abbcc4c3/src/commands/createNewProject/ProjectCreateStep/ProjectCreateStepBase.ts#L28
Our current theory is that because we're running it through a child process, that it's using your git config settings and not the VS Code settings when initializing the repo.
You can try changing that like so
git config --global init.defaultBranch main
We should switch to using the VS Code Git API to do this though, but this should hopefully suffice as a workaround in the meantime.

HAZZAH!   Bingo, worked, thank you.

Close this, possibly add a fix/feature to use the VS Code setting for the Function Extension


[📚] Document how to disable IDFA collection (iOS)

In native, it is possible to disable IDFA, see https://firebase.google.com/docs/analytics/configure-data-collection?platform=ios#disable-IDFA-collection.
At some point, this issue has been created https://github.com/firebase/flutterfire/discussions/6030, and fixed https://github.com/firebase/flutterfire/pull/6046. The new switch in Podfile was first documented for 8.2.0 and last for 8.3.4 (the last version in the 8.x line). Starting with 9.0.0 up to now it is no longer documented. However, the solution still works.
Could you please add this documentation back, so that it is easier to find it? Or answer here if it is no longer recommended to use this 'without idfa' dependency?

Hello @wujek-srujek, since we migrated from the old FlutterFire documentation to the official Firebase documentation website, some part have been dropped since they would duplicate the instructions for either Android or iOS. If nothing is specified for Flutter, it means that you should use the native instructions.
Thanks for bringing this to our attention, we'll see if we can improve this.

Hi. Problem is, there is no official documentation about how to do it in Flutter. The native docs tell us to change the pod we depend on, but we typically don't do it in Flutter this way, Pod spec is created and filled out for us.
A simple mention, like it used to be on Dart Pub, would be sufficient, no idea why it disappeared.

@wujek-srujek I'd like to work on this issue, can you assign it to me

@wujek-srujek I'd like to work on this issue, can you assign it to me

I don't think I can, it's not my project, we have to wait for the owners. But I think you can just implement it and create a PR, looks like nobody is working on it yet.


Add a standalone BNN

Codecov Report
Attention: Patch coverage is 97.84173% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 95.29%. Comparing base (9284cb5) to head (d82b1b9).
Report is 1 commits behind head on main.

Files
Patch %
Lines

gpax/models/spm.py
84.21%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #91      +/-   ##
==========================================
+ Coverage   95.20%   95.29%   +0.08%
==========================================
  Files          53       55       +2
  Lines        4127     4247     +120
==========================================
+ Hits         3929     4047     +118
- Misses        198      200       +2

Flag
Coverage Δ

unittests
95.29% <97.84%> (+0.08%)
:arrow_up:

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

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


feat:updated style.css

feat:updated style.css
Title and Issue number
Title :Enhanced responsivness
Issue No. : https://github.com/apu52/Travel_Website/issues/137
Screencast from 22-01-24 11:40:25 PM IST.webm

@apu52 Please Review

@apu52 Please Review

@Niharika-Upveja Thanks for your valuable contribution.

@Niharika-Upveja Can you please share your full name so that I can update the leaderboard


Update xtb and crest versions to 6.7.1 and 3.0.2 respectively

Closes #12
Closes #14
See #12 and #14 for individual task lists

After simply swapping out the binary versions:

xtb works fine for basic energy, opt, orbitals (without changing any settings, still need to check that solvation, model etc. work fine)

crest conformer searches with no solvation currently fail because --alpb none is passed on the command line

Still haven't tested extensively but crest conformer searches work again.


CreateImageWizard: Add support for vsphere-ova imagetype

The OVA type is also the default when checking VMWare now.

I chose different tooltip text for the vmdk, I found the text supplied in the mocks not super informative, so I decided to stress the usage of it as well.
I also changed the tooltip text on the ova sligthly, mostly to indicate that it also includes the vmdk.

/retest

The .OVA image will need to be added to targetOptions in Target.js

/retest


In small window crops node address

Is your feature request related to a problem? Please describe.
Then XT is in small window  "CONFIRM CONNECTION",at Networks section, node address is cropped.
Describe the solution you'd like
Show on next line
Describe alternatives you've considered
Length of node address can be checked and if bigger then x show on next line
Additional context

available in 1.1.0


bump.cjs updates example deps

Helps prevent issues like https://github.com/solidjs/solid-start/issues/690
Could also do others like @solidjs/meta or @solidjs/router - just say the word!

To be fair I released that version after you reported the bug. But to be fair having the examples on the latest for new installs probably isn't the worst thing. Like it will do that automatically anyway within the range but like you only install a template once so why not.

Yeah I only realized that after making the PR xD


doc strings

plz bike shed

ah the failure on an unused import betrays that I was planning to do a much better job of this initially. Very well CI, you win this round


Bind variables are double escaped

Bind variables are being escaped here before sending to the low-level Vitess API:
https://github.com/pixelfederation/vitess-php-pdo/blob/master/src/VitessPdo/PDO/ParamProcessor.php#L111
This results in double-escaped strings, because Vitess already escapes bind variables when it builds the final query just before sending to MySQL. You should be able to just remove the escaping at this level.

fixed in #v0.1.3


Add support for datetime/smalldatetime using TVP

Populating table having datetime/smalldatetime using TVP throws the unsupported datatype exception right now.
Repro attached.
tryTVPwithDateTime.txt

fixed by #435


Don't allow slashses in repo names

This should fix issue #137

Many thanks for the pull1 Everything looks correct here except I think we should enforce this in a different place. Reason being driver is an interface that may have more than one implementation in the future and we don't want to have to enforce this separately for each.
Instead could you put the check in pfs.APIServer.CreateRepo?
Also would you mind filling out our CLA? https://pachyderm.wufoo.com/forms/pachyderm-contributor-license-agreement/

Whoops, just noticed you've already signed the CLA, feel free to ignore that :)

I believe I have it in the correct place now.

Indeed, merging!

This looks like it hasn't been merged.

Err, sorry I clicked the wrong button there.

There we go :)


Scope variable in definition files problem with types

Right now, let variable; in definition files have no type declaration.
When I add types to it:
let variable: String;

it screws up variable resolution in the LSP -- e.g. the goto-definition no longer works.
let variable: ?;

Marking the variable as ? does continue to work.

I can't reproduce this, so I assume it was #84.


Update methods that return IEnumerable to instead return IReadOnlyList

Receive/ReceiveDeferred/Peek/Complete methods
Send is different as that should use a MessageBatch and is being tracked in a separate issue.

Can I suggest to cross-reference issues when mentioning another work item?
In this case, MessageBatch is https://github.com/Azure/azure-sdk-for-net/issues/10155

One potential issue with using IReadOnlyList is that we couldn't take the return as input to a different method that is expecting an IList. For instance, if you want to complete all the messages that you received, and the Complete method took an IList, this wouldn't work. For this reason, it may be better to just use IList or ICollection.

Would ImmutableList<T> help?

@SeanFeldman thanks for that idea. Since customers might end up wanting to remove messages from the received message list, we figured it was better to just stick with IList.

Would ImmutableList<T> help?

Fixed in https://github.com/Azure/azure-sdk-for-net/pull/10235


Voice over is announcing as incorrect information that "you are in a tree grid" for "Call Stack section" which has no data inside it: A11y_Visual Studio Code Client_Sidebar Bar Options_Accessing Debug sidebar options_Screen Reader.

GIT Hub Tags:
#AILimited; #A11yTCS; #A11ySev2; #Visual Studio Code Client; #BM_Visual Studio Code Client_MAC_JULY2024; #DesktopApp; #WCAG1.3.1; #FTP; #A11yMAS; #Screen Reader; #Voiceover;
Environment and OS details:
MAC Book Pro
MAC OS Sonoma Version 14.5
Visual Studio code Insider version 1.92.0
Reproduction Steps:

Open Visual Studio Code Insiders editor
Using "Shift+Command+D -1" key navigate to the debug side view bar option.
Using "Tab" key navigate to Debug side bar options.

Actual behavior:
Voice over is announcing as incorrect information that "you are in a tree grid" for "Call Stack section" which has no data inside it.
Expected behavior:
Voice over should not be announcing as incorrect information that "you are in a tree grid" for "Call Stack section" which has no data inside it.
User Impact:
Screen reader users will face difficulty if Voice over is announcing as incorrect information that "you are in a tree grid" for "Call Stack section" which has no data inside it.
Attachments:
https://github.com/user-attachments/assets/fbfa3c27-e425-4b68-969d-a3024b6a32b0

I am not sure that we should change the role depending on the state. Users can explore the tree grid and find there are no rows in there. @jooyoungseo and @rperez030 what do you think?

@keerthiduvvuri can you cite documentation that says the role should change depending on whether or not there's data in the element?

@meganrogge I totally agree with you. Unless I'm missing something, it is empty simply because there is no code running at that point. Also, @keerthiduvvuri can you please explain the rational for considering this a sev2? How is the user blocked in this case?
until we have more information, I would consider this an invalid bug.

#Closed;
Closing this bug as not blocking issue.

Thanks, can this be closed now?


Update zfileutils.py

Change number of digits in exponential (can be less than 3).
This fixes #71 #79.

I found a few more issues when reading detectors, so I'm gonna close this, fix all together and resubmit.


Revisiting a url for editing a page throws a 500

If I have a page, say id 3, and I click the edit icon from the pages tab, I will then be redirected to the edit form. If I then go into the URL bar and click enter I get the following error:
Routing Error
No route matches {:action=>"update", :controller=>"refinery/admin/pages"}
Try running rake routes for more information on available routes.
Notice, this only happens if you revisit the link directly. If you click edit again from the pages tab, it works fine AND if your on the edit page (refinery/pages/3/edit) and click refresh it works fine.

This is how Rails routing works.
I'm guessing that the problem actually occurs when you have tried to save the page and gotten validation errors?

No, there are no errors. I understand if there was an error the URL in the url bar is invalid and would produce this behavior.
To reproduce try the following steps:

Visit the admin panel and click on Pages tab
Click edit on a page
Go the URL bar and just click enter (as if revisiting the URL from history)
(At step 3 the URL should look something like: http://localhost:3000/refinery/pages/3/edit)

You will get:
Routing Error
No route matches {:action=>"update", :controller=>"refinery/admin/pages"}
Try running rake routes for more information on available routes.

Whoa, you're right. I'm sorry I closed this!

@miskander thanks for reporting this! Sorry that I mistook it for something else without really checking first :-)

Thanks for the quick fix, and no problem. It was a very subtle bug. :)


API Gateway - Allow integrationURI to ref a targetGroupBinding

I'm trying to avoid using a hardcoded integrationURI but that doesn't seem possible.    I can parameterize it in helm but thats a bit clunky, I'd love to be able to refer to targetGroupBinding but it's unclear how to do that.

Hi @bberzinskas-tw , thank you for raising this issue. I'm trying to understand more what are you trying to achieve here.

Are you using apigatewayv2-controller and a aws-load-balancer-controller ?
Can you please try to provide some examples of manifests you're trying to deploy?


Is it 'uid' or 'uuid'?

In some places it's one, in some places another. I remember Nils having concerns that if the user can assign it, it's not really universally unique, so maybe that's why it's only one "u" in some places? I don't care, and would be happy with any of uuid/uid/id, but the inconsistency seems like something we'll trip over in the future.

It can be either. Should stand for universal identifier. If you need to use
it somewhere new use 'uid'.
On Feb 15, 2017 5:39 PM, "mccalluc"<EMAIL_ADDRESS>wrote:

Assigned #16 https://github.com/hms-dbmi/higlass-server/issues/16 to
@pkerpedjiev https://github.com/pkerpedjiev.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hms-dbmi/higlass-server/issues/16#event-963396513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACC1jfZKBoTMDrIYtt4PXfVUQoExvlC2ks5rcyougaJpZM4MB8mG
.

So, uuid that means Universally Unique Identifier. This is cryptographically strong pseudo random number generator. About uid or Unique Id over time with respect to the host that it was generated on.
Example:

Generated UUID : 4e4deff9-b027-4359-8ad5-320e429b5739
Generated UID: 3e336481:14ed674b5d1:-8000

The ancient Romans used uuid I believe, but eventually what we know today as "roman numerals" took over as it was regarded as "disruptive tech" at the time.


[Task]: Identify intermediate high level model for Ballerina constructs

Description
$subject
Describe your task(s)
We need an IR to use at a higher level with abstraction to map Ballerina constructs as an alternative to Syntax APIs.
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

As per the offline discussion, we could design an intermediate object model to map the Ballerina code.
Please refer to https://github.com/HindujaB/BallerinaObjectModel/blob/main/src/main/java/io/ballerina/object/model/BallerinaPackage.java for the rough implementation.


Simple Label Renderer

This MR should implement a simple label renderer.

Text layouted with cosmic-text
Glyph Classification by projecting the center pixel to the surface's pixel array.
Render glyphs in different sizes, depending on the projection.
Dynamically switch to signed distance filed depending on the projection.
A quaternion based camera animation to show off 3D text quality.

I've reduced the scope of this PR to only contain glyph classification and basic camera movement, which should be sufficient for testing dynamic changes of rendered glyphs.


Feature/relay

Codecov Report

Merging #45 (7b4c58d) into master (b5621b2) will decrease coverage by 7.64%.
The diff coverage is 35.31%.

:exclamation: Current head 7b4c58d differs from pull request most recent head 4ae22d7. Consider uploading reports for the commit 4ae22d7 to get more accurate results

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
- Coverage   52.96%   45.32%   -7.65%
==========================================
  Files           8       12       +4
  Lines        1316     2436    +1120
==========================================
+ Hits          697     1104     +407
- Misses        502     1126     +624
- Partials      117      206      +89

Flag
Coverage Δ

unittests
45.32% <35.31%> (-7.65%)
:arrow_down:

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

Impacted Files
Coverage Δ

internal/ipfs/adder.go
0.00% <0.00%> (ø)

mobile/discovery.go
30.14% <16.07%> (-0.89%)
:arrow_down:

internal/repo/repo.go
54.85% <33.33%> (-1.80%)
:arrow_down:

internal/replication/replication.go
36.58% <33.97%> (-13.83%)
:arrow_down:

mobile/datahop.go
42.63% <39.13%> (-20.19%)
:arrow_down:

internal/replication/group_replication.go
41.11% <41.11%> (ø)

internal/repo/state.go
44.44% <44.44%> (ø)

internal/ipfs/ipfs.go
60.38% <55.72%> (ø)

internal/security/security.go
64.28% <64.28%> (ø)

internal/config/config.go
75.00% <100.00%> (ø)

... and 7 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 511bc01...4ae22d7. Read the comment docs.


posix: Implement mq_notify()

The function was the last missing piece of the _POSIX_MESSAGE_PASSING
option group. Due to lack of signal subsystem in the Zephyr RTOS
the sigev_notify member of the sigevent structure that describes
the notification cannot be set to SIGEV_SIGNAL - this notification
type is not implemented, the function will return -1 and set errno
to ENOSYS.
mq_notify documentation:
https://pubs.opengroup.org/onlinepubs/9699919799/functions/mq_notify.html
Fixes https://github.com/zephyrproject-rtos/zephyr/issues/66958

try not to modify unrelated lines, with the right config I think you can format just the modified lines in vscode

@ycsin just tried to fix some formatting issues but don't need to do that

Looks like you need a rebase

@awojasinski - if you're feeling generous, we could also use mq_timedreceive() and  mq_timedsend() for the _POSIX_TIMEOUTS subprofiling option 😃

@awojasinski - if you're feeling generous, we could also use mq_timedreceive() and mq_timedsend() for the _POSIX_TIMEOUTS subprofiling option 😃

@cfriedt sure I'll take a look in my spare time


Error in test contact

In GitLab by @nmansard on Mar 6, 2019, 17:47
In test contact, the numerical errors are below the threshold, but for some initialization. Looking at it, it seems that they are above the noise. I start digging into it. To reproduce the error, use the following initialization of x and u at line 274 of test_contacts.py
x[:3] = 0
x[3:7] = [1,0,0,0]
x[7:] = 0
u[:] = 0

I believe this is coming from the state cost, when there is a free flyer.

In GitLab by @proyan on Mar 6, 2019, 17:49
assigned to @proyan

In GitLab by @nmansard on Mar 6, 2019, 17:58
mentioned in merge request !126

In GitLab by @nmansard on Mar 6, 2019, 17:58
See !126 for a patch, please merge it.

In GitLab by @proyan on Mar 7, 2019, 13:05
I located the error in StatePinocchio.Jdiff.
I'm quite sure that it is just the problem of a rotation matrix.
I'm fixing it and adding a unit-test to check the SE3 case.

In GitLab by @proyan on Mar 7, 2019, 15:22
Weird. I try to test the jdiff with finite differencing, and it works. Then I try to test the CostModelState.Rx with finite differencing, and it also works.
However, ActionModelNumdiff is doing the same thing, but it isn't working.
test_jdiff.py

In GitLab by @proyan on Mar 7, 2019, 15:31
Ok, I can reproduce the error if I take x_ref=state.zero() in the above script.

In GitLab by @proyan on Mar 8, 2019, 13:48
The problem comes from doing finite differences when the difference between the quaternions is pi.
By definition of pinocchio, diff(q1,q2) returns values between pi and -pi.
As a result, fd becomes unstable when diff(q1,q2) is exactly, or close to pi, since the increments could be positive or negative.
Attached script plots the errors around this value.
plot_jdiff.py

In GitLab by @proyan on Mar 8, 2019, 13:51
Your patch is already taking care of this instability by making sure that the freeflyer quaternions are always [0 0 0 1].
A more robust approach might be to use state.rand(), and check that the difference is not pi for free-flyers. However, that seems to be too much of work for the unit-test. Perhaps that might be a low-priority task for the cpp case.
I would suggest not taking any action, and closing this issue.

In GitLab by @nmansard on Mar 8, 2019, 15:16
This is bad, as num-diff is typically used in practice when we are to lazy to compute the derivatives. I think it is necessary, at least, assert that this case is not happening. Could you implement an assert, and then open an issue to advertise this assert?

In GitLab by @proyan on Mar 8, 2019, 15:31
Where would you put the assert? The error is specific for finite differencing of the state.
I don't see this happening anywhere other than the costmodelstate, for which we already have a jdiff implemented.

In GitLab by @nmansard on Mar 12, 2019, 10:31
In the numdiff class, maybe? That might be quite ugly code.

In GitLab by @cmastalli on Mar 21, 2019, 14:44
mentioned in merge request !146

In GitLab by @nmansard on Mar 22, 2019, 15:49
Please @proyan could you finalize this one?

In GitLab by @proyan on Mar 26, 2019, 15:00
mentioned in merge request !148

In GitLab by @nmansard on Mar 28, 2019, 10:29
Fixed by !148

In GitLab by @nmansard on Mar 28, 2019, 10:29
closed

In GitLab by @nmansard on Mar 28, 2019, 14:37
mentioned in commit 975e94d5553ed9903c1566369dac9dc18722f747


Preroll and main video play simultaneously on Android device, when main video is of type m3u8

When the video is started as soon as possible on an Android device and the main video is of type m3u8, the preroll and main video will start playing both at the same time, instead of playing the preroll first and then the main video. The preroll only is visible but we can hear the audio of the main video in the background.
I have made a copy of the simple example changing only the main video from a mp4 to a m3u8
original (mp4 no bug)
https://googleads.github.io/videojs-ima/examples/simple/
modified version (m3u8 bug)
https://tbourigault.github.io/IMA-SDK-Plugin-VideoJS-Simple-M3U8.html
Steps to reproduce:

Open https://tbourigault.github.io/IMA-SDK-Plugin-VideoJS-Simple-M3U8.html on an Android device.
Click on the play button of the video as soon as possible

Expected behavior:
The preroll ad should play first, followed by the main video.
Actual behavior:
Both the preroll ad and main video start playing at the same time. The preroll only is visible but we can hear the audio of the main video in the background.
Environment details:
Bug was reproduced on multiple android devices, different m3u8 files and versions of videoJS 7 & 8
one example:
Operating system: Android 6.0.1
Browser: Google Chrome (Version 106.0.5249)
Video player: video.js (Version 7.18.1) with the videojs-ima plugin (Version 2.0)

Hello @tbourigault
Android 6.0.1 is marked as no longer maintained. If you are able to develop a fix using using your device, I can take a look at the pull-request. Otherwise, the plugin may not be able to support that version of Android.
Thank you,
Jackson
IMA SDK team

Hello @Kiro705
I was able to reproduce it on more recent device also
2 person on my team were also able to reproduce the bug on:
Phone Samsung s22, android 13
Tablet Samsung Tab A7, Android 12
Thank you

I have the same issue, really weird to hear the audio of the 2 videos at the same time.
@Kiro705 Any idea about this bug? must be a timing problem?
The important point is to click on the player as soon as the video icon appears, knowing that I can reproduce almost every time. Does not seem to happen when we wait a few seconds or more.
My phone is a Samsung Galaxy A51, Android 13.

Hi 👋🏻☺
I was able to reproduce on me device.
Chrome 114.0.5735.60
Android 11; ONEPLUS A6013 Build/RKQ1.201217.002
Both audios can be heard simultaneously with this URL:
https://tbourigault.github.io/IMA-SDK-Plugin-VideoJS-Simple-M3U8.html

Hello all,
I was looking into this issue more, and have been able to reproduce it reliably, when making sure to play the video as soon as possible. Unfortunately, I have not been able to identify a fix for the issue, but will plan to take another look soon. Please let me know if any changes on your end seem to resolve this issue.
Thank you,
Jackson
IMA SDK team

@floverdevel  how are you being able to play mid roll and post roll ads. as i am only being able to play pre-roll ads. can you please share the code.
@Kiro705

I never tried to play mid-roll or post-roll ads.

Are there any plans of fixing it or workarounds? Maybe downgrade to some particular version?

Here is my workaround, it doesn't solve the root issue but masks it for users:
`
let tempVolume;
player.ima.addEventListener(google.ima.AdEvent.Type.STARTED, () => {
const adVideoEl = player.el().querySelector(".ima-ad-container video[src]");
tempVolume = player.volume();
player.volume(0);
adVideoEl.volume = tempVolume;
});
player.ima.addEventListener(google.ima.AdEvent.Type.CONTENT_RESUME_REQUESTED, () => {
player.currentTime(0);
player.volume(tempVolume);
player.src(player.src());
player.play();
}
);
`
So basically I mute video on ad start, then unmute and reload on ad end.

Hi Everyone, Can you please advise this issue is fixed? Still I am facing this issue in VideoJS latest version


fix: configure Spin state dir

fixes https://github.com/spinkube/containerd-shim-spin/issues/216

This is also capturing logs, so we need to configure the dir for kv/sqlite but not for logs.
Logging component stdio to "/.spin/logs/"
Storing default SQLite data to "/.spin/sqlite_db.db".

Serving http://<IP_ADDRESS>:80
Available Routes:
  todo-api: http://<IP_ADDRESS>:80/api (wildcard)
  fileserver: http://<IP_ADDRESS>:80 (wildcard)

Resolved logs not being displayed by explicitly unsetting the log dir.
Storing default SQLite data to "/.spin/sqlite_db.db".

Serving http://<IP_ADDRESS>:80
Available Routes:
  todo-api: http://<IP_ADDRESS>:80/api (wildcard)
  fileserver: http://<IP_ADDRESS>:80 (wildcard)
Getting todos
Handler returned an error: Error::Io("no such table: todos")
Initializing migration
Getting todos

@Mossaka i am not sure what i would add to the CHANGLOG for this as this is a fix to ensure that we do not have a change in this release with regards to the state dir


[URI] Introduce URI/URL structs + relevant APIs

Description:
Need to introduce URI/URL structs along with APIs for handling URIs/URLs.
Suggested Labels (optional):
Type/Feature

Won't implement this


Update Windows development usage.

So that the example invocation works in PowerShell and cmd.
Fixes Issue
Invocation doesn't work OOB on cmd.
Description of Change
Fix CLI invocation.
Have test cases been added to cover the new functionality?
No

thanks!


✔ 2.2.1 Hotfix

🏷 Emoji Picker Hotfix 🏷
✔ Bugfixes ✔

Modal of the emoji picker will now close after selection an emoji

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Delete ujson and uvloop from requirements.txt

ujson and uvloop are not nessesary for sanic, so maybe we can delete them from requirements.txt, and give a message to user to manually install them for faster running?
https://github.com/channelcat/sanic/blob/7b66a56cad9820b3172850fde9a61f0cb865dcf5/sanic/response.py#L4-L7
https://github.com/channelcat/sanic/blob/eb06e6ba51b493f871d71dbddd9c7b4271e799b4/sanic/server.py#L22-L25

#855

httptools may still not work on Windows. But I don't have a windows machine, so can't test it out.

True, currently it sill not work on Windows, but why not try to make it work on Windows step by step.

I'm a fan of the batteries included but swap-able design. People who come to sanic for the purported speed may be dissuaded when it doesn't work as advertised out of the box.

I understand your point, but for example, ujson is not a drop-in replacement for json and it might lead to issues, so, at least, when it's not 100% compatible, it shouldn't be forced.
 That way you could pip install sanic or pip install sanic[uvloop] or pip install sanic[all] which has the opt in your looking for. But the project has a stated "main goal" of speed so I think its probably more in line with the project to be an opt-out feature a la SANIC_NO_UJSON=true pip install sanic.

The sad thing is that SANIC_NO_UJSON=true is not taken into account because in requirements.txt
And there are no solution in pip right now to be able to avoid that.

yea that's annoying :disappointed:, in some senses this is a pip ergonomics problem, it's possible this could be alleviated with conda features. I think someone started the process of making a conda package here #848

We might be able to take advantage of PEP 508 -- Dependency specification for Python Software Packages.
requirements.txt:
ujson; sys_platform != 'win32'
uvloop; sys_platform != 'win32'

But upgrading to newer pip version might be required.

Making uvloop and ujson optional would be appreciated. Even though I plan to run my app on a linux machine, being able to work on windows would be a great boon.

👍
My app has just started segfaulting due to ujson, so the ability to easily not use it would be appreciated.

He folks, wanted to give a gentle prod to some of the folks on this thread to see if anyone else could try pip install-ing or providing feedback on #1117 .

I thought ujson was compatible with python 3 — at least that’s what http://py3readiness.org http://py3readiness.org/ says.  Maybe this is a bad resource for determining python 3 compatibility.  Now that’s not to say that ujson should remain in the requirements.txt file.

On Jan 29, 2018, at 1:40 PM, Artem Krylysov<EMAIL_ADDRESS>wrote:
I would love to get uvloop and ujson removed from requirements.txt, these libraries are not compatible with PyPy3.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/channelcat/sanic/issues/916#issuecomment-361362095, or mute the thread https://github.com/notifications/unsubscribe-auth/AFpHSnh-F2YZvx_FwvERv7BXYanTbqk6ks5tPh7JgaJpZM4PBVFI.

@marcstreeter I think py3readiness is specific to cpython, when @akrylysov mentions pypy3 I think he's talking about https://pypy.org/ which is going to have completely different compatibility from cpython

lol- I can't read it seems.  I had in fact just deleted my comment because I noticed he put "PyPy3" and not Python 3.

Glad to see that, thanks.


Compilation error missing DotNet

@maki0315 I have the same issue, may I ask how did you fix it?

Now I figured it out, after running dotnet publish Reinterop~ -o ., I totally missed the line "open cesium-unity-samples project in the Unity Editor" from the docs


Upgrading and standardizing versions of Node

Upgrading the default version we're using to build this project from 8.16 to 12.7.
Also adding 8.10 as the lowest version we'll currently support (works with ESLint) so that we know when it breaks (and then fix it or reevaluate which versions we'll support).
package-lock.json is simply the new generated file after upgrading to 12.7.

It should work with any versions newer than 8.10, so I think he's good, but yeah, I'll check with him ^_^

@megoth Yeah it should work, but with the newer version you'd also get a newer version of npm, and in between the lockfile format changed. So if Tim would continue to use the old version of npm, we'd get a new lockfile with many changes every time someone runs npm install with a different version than the last time the file was generated :)

Tim needs to upgrade 😄
@megoth Is DEFAULT_NODE_VERSION still used anywhere? Looks like a leftover from older build scripts.

@megoth Is DEFAULT_NODE_VERSION still used anywhere? Looks like a leftover from older build scripts.

I'll double-check, gotta admit it was shamelessly copied from https://github.com/rdfjs/N3.js/blob/master/.travis.yml#L3-L7 without much though -_-

I can't find any information for why it should be there, so I'll remove it.

@RubenVerborgh I was thinking of switching out npm install with npm ci (npm-ci), which means that we must test with Node v8.10.0 (npm v5.6.0) and Node v10.3.0 (nvm v6.1.0).
I think it would be good to have a clean install and be 100% sure that package-lock.json describes what dependencies to use.
Do you have thoughts on this?

Do you have thoughts on this?

npm ci.


Handle --debug CLI option

Right now it is not hooked up.  Follow standard practices for debugging:

Implement a DEBUG(string, ...interface{}) function
Print to os.Stderr
Prefix each line with DEBUG>

At the very least, we should DEBUG() that we have enabled debugging output.

Apparently, I'm a huge fan of --debug.  This is a dupe of #18


Fix missing import in coresight_target.py

Import six in coresight_target.py to fix error introduced in e808d93 (which was itself supposed to fix a regression! 😞).

/morph test


feat(big-number): format datetime according to granularity

🏆 Enhancements
This adds support for "Time Grain" in Superset for Big Number with Trendline chart.

It will now render date format in tooltip according to the time granularity.
Before
When "Time Grain" is set to "Quarter":

After
When "Time Grain" is set to "Quarter":

Will create a follow up PR to introduce alignTimeRange after this is merged.

Note: Can ignore the test coverage for now.

Merge it for now. No need to publish. Will address the comments in a future PR.


"in" sometimes recognised as function call by syntax highlighting

https://pluto-lang.org/docs/New Features/In Expressions

Fixed in 76ee6037642bd45c5e1b7b0d8e82eecf0311ec4a


[SMALLFIX] Do not start master when one is running

Signed-off-by: liuhongtong<EMAIL_ADDRESS>

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/Alluxio-Pull-Request-Builder/4628/
Test PASSed.

@liuhongtong The old behavior of ./bin/alluxio-start.sh master is
(1) if there is any existing AlluxioMaster, kill the current AlluxioMaster.
(2) and then start the new AlluxioMaster.
The changes in your PR is when ./bin/alluxio-start.sh -N master,
(1) Do not kill existing AlluxioMaster
(2) if there is already one existing AlluxioMaster, do not start a new one. <-- I think it make sense to maintain the current old AlluxioMaster.
What will happen before? We will have two AlluxioMaster or the later AlluxioMaster cannot be started correctly?

@LuQQiu when ./bin/alluxio-start.sh -N master, a new AlluxioMaster will start, but fail immediately, because the port has been used.

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/Alluxio-Pull-Request-Builder/4661/
Test PASSed.

@apc999 PTAL, thanks

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/Alluxio-Pull-Request-Builder/4685/
Test FAILed.

@apc999 PTAL, thanks.
Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 48.77 sec <<< FAILURE! - in alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest
pin(alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest)  Time elapsed: 1.506 sec  <<< ERROR!
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: EOF while parsing checkpoint type. Was your checkpoint written by alluxio-1.x? See https://docs.alluxio.io/os/user/edge/en/operation/2.x-Upgrade.html for instructions on how to upgrade from alluxio-1.x to alluxio-2.x
at alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.createFsMasterFromJournal(UfsJournalIntegrationTest.java:634)
at alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.pinTestUtil(UfsJournalIntegrationTest.java:394)
at alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.pin(UfsJournalIntegrationTest.java:390)
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: EOF while parsing checkpoint type. Was your checkpoint written by alluxio-1.x? See https://docs.alluxio.io/os/user/edge/en/operation/2.x-Upgrade.html for instructions on how to upgrade from alluxio-1.x to alluxio-2.x
at alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.createFsMasterFromJournal(UfsJournalIntegrationTest.java:634)
at alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.pinTestUtil(UfsJournalIntegrationTest.java:394)
at alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.pin(UfsJournalIntegrationTest.java:390)
Caused by: java.lang.IllegalStateException: EOF while parsing checkpoint type. Was your checkpoint written by alluxio-1.x? See https://docs.alluxio.io/os/user/edge/en/operation/2.x-Upgrade.html for instructions on how to upgrade from alluxio-1.x to alluxio-2.x
Caused by: java.io.EOFException

@apc999 PTAL. Thanks.

Hi @liuhongtong !
We appreciate your contribution, however after some offline discussion with @LuQQiu we would like to see a few things before merging this PR

Can we extend this functionality across all alluxio processes, and ensure that the check only runs when the -N flag is supplied?
Instead of copying and pasting the same functionality, can we abstract out the s -Aww -o pid,command | grep -i "[j]ava" | grep ${keyword} | awk '{print $1}' into another function which can be called for each process?

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/Alluxio-Pull-Request-Builder/5026/
Test PASSed.

@ZacBlanco I accept. But could I commit a new PR to implement your proposal？

Yes, whatever you would like to do. Either open a new PR or continue working on this one.

@ZacBlanco Please help to merge this PR. And I will open a new PR.

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/Alluxio-Pull-Request-Builder/5208/
Test PASSed.

I don't think that merging this PR first is necessary. You can either open a new PR with this branch as the base or just continue working on top of what you have here. For anything to be merged we would like the previous comments I mentioned addressed.

Since there's been no progress here I'm going to close the PR.
Please re-open if you would like to continue the work.