Use JDK as base image to provide openjdk-8-jdk rather than JRE.

We consistently have issues (see below) with a JDK not being installed or repository packages being updated so they are no longer available.
I have updated the base image to use a JDK rather than a JRE.
`root@0acedf8721c3:/usr/local/tomcat# apt-get install openjdk-8-jdk
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package openjdk-8-jdk
root@0acedf8721c3:/usr/local/tomcat# apt-get update
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Ign http://deb.debian.org jessie InRelease
Get:2 http://deb.debian.org jessie-updates InRelease [145 kB]
Get:3 http://httpredir.debian.org unstable InRelease [230 kB]
Get:4 http://deb.debian.org jessie-backports InRelease [166 kB]
Get:5 http://deb.debian.org jessie Release.gpg [2373 B]
Get:6 http://deb.debian.org jessie Release [148 kB]
Get:7 http://security.debian.org jessie/updates/main amd64 Packages [436 kB]
Get:8 http://deb.debian.org jessie-updates/main amd64 Packages [17.6 kB]
Get:9 http://deb.debian.org jessie-backports/main amd64 Packages [1028 kB]
Get:10 http://deb.debian.org jessie/main amd64 Packages [9049 kB]
Get:11 http://httpredir.debian.org unstable/main amd64 Packages [9929 kB]
Fetched 21.2 MB in 14s (1472 kB/s)
Reading package lists... Done
root@0acedf8721c3:/usr/local/tomcat# apt-get install openjdk-8-jdk=8u111-b14-2~bpo8+1
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '8u111-b14-2~bpo8+1' for 'openjdk-8-jdk' was not found
root@0acedf8721c3:/usr/local/tomcat# apt-get install openjdk-8-jdk
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
openjdk-8-jdk : Depends: openjdk-8-jre (= 8u121-b13-1~bpo8+1) but it is not going to be installed
Depends: openjdk-8-jdk-headless (= 8u121-b13-1~bpo8+1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.`

LGTY


Update cert-manager-app to use upstream 1.6.1

https://github.com/jetstack/cert-manager/releases/tag/v1.6.0

1.6.1 has been released today https://github.com/jetstack/cert-manager/releases/tag/v1.6.1

Updating issue to 1.6.1 🚀

@ubergesundheit wrote a script in the playground for checking ingress versions, we need to check all clusters for CRDs, as they've deprecated old versions of CRDs which they don't reconcile anymore, continue checking those changes upstream
@ubergesundheit to send @webwurst an updated script that does stuff better with the whole gsctl/kubectl-gs changes
@webwurst to drop the data about whether customers have old CRDs <3

@webwurst what's the status here?

Todo:

[ ] Compile list of WCs that reconcile the old cert-manager CRs
[ ] Test new cert-manager PR

Scripted output of apiVersion for ClusterIssuer, Issuer, Certificate shows v1 for clusters where access was possible.

Scripted output of apiVersion for ClusterIssuer, Issuer, Certificate shows v1 for clusters where access was possible.

Do you have the list of management and workload clusters where you could not check?

Tobias is gonna get us a list of the failing workload clusters (i.e: cluster we can't access), or clusters with old certificate CRD versions

Certificate CRD versions are fine across all clusters, we're gonna do some testing bam

released 2.12.0


Subscriptions?

Thank you for the nice Land. I played a bit with rockets 👍
I was able to add users with mutations, but I was not able to play with subscriptions.
subscription {
  users {
    name
  }
}

Here is the result:
{
  "errors": [
    {
      "message": "Cannot return null for non-nullable field Subscription.users.",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "users"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ],
  "data": null
}

Do you know if it should work? Or if I have to adapt my query?
Thank you

I run into the same problem. Did someone has any solution? Is there a subscription active?


JavaScript highlighting issue

VSCode Version: Code - Insiders 1.7.0-insider (0706b425537d8cfe2766eac00662ecf988c7ed7f, 2016-10-28T13:10:55.168Z)
OS Version: Windows_NT ia32 10.0.10240
Extensions:

Extension
Author
Version

ejs-language-support
QassimFarid
0.0.1

vscode-icons
robertohuertasm
3.0.7

code-spell-checker
streetsidesoftware
0.11.4

See screenshot below. Text highlighting seems broken for 'person\'s email'

@SMH110 thank you for opening this issue. The grammar is dependent on this repo. Can you move it there and they can resolve the issue?


jwt rotation not working properly after browser close and open

Environment
Windows 10
Nuxi 3.6.5
Nuxt 3.6.5 with Nitro 2.4.1
@sidebase/nuxt-auth 0.4.4
next-auth 4.22.3
Reproduction
No response
Describe the bug
This is own my jwt refresh code.
This code works well until browser close.
import { NuxtAuthHandler } from "#auth";
import GoogleProvider from "next-auth/providers/google";
import NaverProvider from "next-auth/providers/naver";
import { JwtUtils } from "@/constants/utils";
const config = useRuntimeConfig();
export default NuxtAuthHandler({
  secret: process.env.NUXT_SECRET,
  pages: {
    // Change the default behavior to use `/login` as the path for the sign-in page
    signIn: "/login",
  },
  providers: [
    GoogleProvider.default({
      clientId: process.env.GOOGLE_CLIENT_ID,
      clientSecret: process.env.GOOGLE_CLIENT_SECRET,
    }),
    NaverProvider.default({
      clientId: process.env.NAVER_CLIENT_ID,
      clientSecret: process.env.NAVER_CLIENT_SECRET,
    }),
  ],
  callbacks: {
    async jwt({ token, user, account, profile }) {
      console.log(
        `[current] access: ${token.accessToken}, refresh: ${token.refreshToken}`
      );
      try {
        if (user && account) {
          if (account.provider === "google" || account.provider === "naver") {
            const response = await $fetch(
              `${config.public.apiBase}/dj-rest-auth/${account.provider}/`,
              {
                method: "POST",
                body: {
                  access_token: `${
                    account.provider === "google"
                      ? account.id_token
                      : account.access_token
                  }`,
                },
              }
            );
            const { access, refresh } = response;
            token = {
              ...token,
              accessToken: access,
              refreshToken: refresh,
            };
          }
        } else if (!token.accessToken || !token.refreshToken) {
          return {};
        } else if (JwtUtils.isJwtExpired(token.accessToken)) {
          const response = await $fetch(
            `${config.public.apiBase}/dj-rest-auth/token/refresh/`,
            {
              method: "POST",
              body: {
                refresh: token.refreshToken,
              },
            }
          );
          const { access, refresh } = response;
          console.log(`[new] access: ${access}, refresh: ${refresh}`);
          token = {
            ...token,
            accessToken: access,
            refreshToken: refresh,
          };
          return token;
        }
      } catch (error) {
        if (error.data) {
          console.debug(token.email, error.data);
        } else {
          console.debug(token.email, error);
        }
        return {};
      }
      return token;
    },
    async session({ session, token }) {
      if (token.accessToken) {
        session.accessToken = token.accessToken;
      } else {
        session = {};
      }
      return session;
    },
  },
  events: {
    async signOut({ token }) {
      await $fetch(`${config.public.apiBase}/dj-rest-auth/logout/`, {
        method: "POST",
        body: {
          refresh: token.refreshToken,
        },
      });
    },
  },
});

But in some scenario, user can close browser and after 12 hours like enough expiration access token,
user can open browser again. Then the code refresh access_token and refresh_token automatically.
And then in jwt callback function, returns new access token and refresh token.
But somehow, the token is not updated correctly.
I don't know how I can fix it correctly but I can only figure the cookie is not updated.
<EMAIL_ADDRESS>This code is always runned when jwt callback run like refresh tab , open browser.
So it works well with refreshed tab while browser running.
But it's not working with two conditions.

browser closed
token expired

Then as soon as browser open, the token is updated. And session-token cookie should be updated too matched new token. But somehow even if setCookie code was run, but cookie is still same as previous session-token cookie.
Maybe.. there might be bug with nuxt initialize code with cookie and update cookie after jwt callback logic.
Additional context

This cookie should be updated to browser cookie

But after code run, cookie is still same as before.
Logs
No response

I am not sure what the problem is.. but I modified directus code.
now it works properly what I am expecting.

It's not solved..
It sometimes occurs , it makes me crazy..
I guess I need to give up using nuxt-auth based on next-auth.
It's not frome nuxt-auth, it's more related to next-auth.
And it's an old issue discussed many times in next-auth repo.
https://github.com/nextauthjs/next-auth/discussions/1455
https://github.com/nextauthjs/next-auth/issues/2071
https://github.com/nextauthjs/next-auth/issues/2129
https://github.com/nextauthjs/next-auth/discussions/3941
All of them are related issue. but there isn't realy solution.
Maybe some comments can be workaround but not real solution.
I hope someday it will be solved. Then auth package can be more valuable

I also face this issue....

same problem

Hmm, interesting issue. As you pointed out it seems to be more related to authjs, then our module.
I have used refresh tokens inside the JWT countless times before. I would follow these steps to continue with this issue:

Add a refresh provider example for authjs
See if applying our refresh logic fixes your issue
continue investing

However, as you already pointed our numerous issues in the nextauth repo, it may not be the fix. However, we are also now beginning the migration to authjs, which may fix this issue. Keep an eye on #673 for updates on this!

Closed due to inactivity.


OLS-81: Team ownership of RAG pipeline - RAG content image

Description
This is a part of https://github.com/openshift/lightspeed-service/pull/518 that introduces quay.io/openshift/lightspeed-rag-content:${OLS_VERSION} image.
A Containerfile and supporting scripts for multi-stage build of RAG content, to be run from OLS CI. Inputs into the process are OCP 4.15 docs from https://github.com/openshift/openshift-docs and an embedding model from HuggingFace. Produced image contains

OCP docs plaintext, not intended for inclusion into OLS RAG but can be useful to look at
embedding model
Faiss vector database with embeddings generated from the OCP docs plaintext

The resulting image is intended for consumption during the OLS build process.
The other half of this work is in https://github.com/openshift/release/pull/49510.
Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue # https://issues.redhat.com/browse/OLS-81, https://issues.redhat.com/browse/OLS-355
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

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

Project coverage is 96.83%. Comparing base (c0d2146) to head (b484e97).
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #556   +/-   ##
=======================================
  Coverage   96.83%   96.83%
=======================================
  Files          48       48
  Lines        1485     1485
=======================================
  Hits         1438     1438
  Misses         47       47

see 1 file with indirect coverage changes

/lgtm

/approve


Add separated DataFrame to seals

This splits bearings from seals in two different dataframes:

df_bearings for bearings
df_seals for seals

It aims to better organize the elements and to avoid code interpretation problems such as in static analysis:
This is the free-body diagram of an example while seals and bearings are merged in same dataframe. The code interprets seals like bearings and calculate reaction forces where both seals are placed:

And now, spliting bearings and seals:

Also, fix a bug when modeling too flexible bearings, displacement were getting larger than acceptable.
It uses axuliar bearings with high stiffness, considering almost zero displacement in bearing nodes.

Codecov Report

Merging #278 into master will increase coverage by 0.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #278      +/-   ##
==========================================
+ Coverage   70.68%   70.95%   +0.26%
==========================================
  Files          10       10
  Lines        2934     2961      +27
==========================================
+ Hits         2074     2101      +27
  Misses        860      860

Impacted Files
Coverage Δ

ross/rotor_assembly.py
79.31% <100%> (+0.76%)
:arrow_up:

Continue to review full report at Codecov.

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


Moving to native promises

[x] rewrite parser code without vow

[x] use async/await

[x] lodash full lib should be replaced with single partly libs of lodash

[x] reduce vendors

[x] move envs to separate repos

[x] move paginator to separate repo (https://github.com/redco/goose-paginator)

[x] check with phantom env (https://github.com/redco/goose-phantom-environment)

[x] check with chrome env (https://github.com/redco/goose-chrome-environment)

[x] check with jsdom env (https://github.com/redco/goose-jsdom-environment)

[x] check on live parsers

:goose:

🤝 let's live it

🎢


We already build for armv7, let's also build for armv6 (for the original Raspberry Pi)

Interestingly, the pr build worked, but the push didn't. I'll just merge


SYS A000 caused unexpected results.

SYS $A000 does NOT act like SYS A000.  I don't know if this is an issue with the emulator or the system ROM.
SYS $A000 acts as expected, but SYS A000 does NOT give an error and will run.  BUT... the program can NOT WRITE to memory!!

SYS $A000 does NOT act like SYS A000. I don't know if this is an issue with the emulator or the system ROM. SYS $A000 acts as expected, but SYS A000 does NOT give an error and will run. BUT... the program can NOT WRITE to memory!!

I'm not sure if I understand correctly, but using SYS A000 (without the $) will probably do SYS 0 (and thus it probably crashes or something, since there is no valid code to execute at memory address zero). This is because A000 alone (without the $) means a variable named A000, which is probably zero in value (unless if you set it to other value before). So of course SYS A000 does not give error, since it's legitimate BASIC, meaning you want to SYS to address given by the value of the variable named as A000. To see the difference, try these BASIC commands:
PRINT $A000
PRINT A000
A000 = 2023
PRINT A000
PRINT $A000

SYS $A000 does NOT act like SYS A000. I don't know if this is an issue with the emulator or the system ROM. SYS $A000 acts as expected, but SYS A000 does NOT give an error and will run. BUT... the program can NOT WRITE to memory!!

I'm not sure if I understand the reported problem correctly, but using SYS A000 (without the $) will probably do SYS 0 (and thus it probably crashes or something, since there is no valid code to execute at memory address zero). This is because A000 alone (without the $) means a variable named A000, which is probably zero in value (unless if you set it to other value before). So of course SYS A000 does not give error, since it's legitimate BASIC, meaning you want to SYS to address given by the value of the variable named as A000. To see the difference, try these BASIC commands:
PRINT $A000
PRINT A000
A000 = 2023
PRINT A000
PRINT $A000

It DOES run.  It doesn't do a SYS 0.  It does a SYS $A000 but won't allow memory save.  Acts as if all memory save are to ROM.


Immutable Sample

As the Sample is being treated as an immutable struct, you could use a Builder to make it immutable and then have instance data publicly accessible. It seems this class is just being treated as a container for data.
Note: This will change instantiation and data accessing.

Hi @BlurryZombie I appreciate your effort in this PR but I prefer not to merge it.
I understand this change would make the code base of Sample object better but the main target of this project is illustrate how to do animations. So in order to keep things simple and easy to understand I don't mind scarifying code correctness.
That said, if you like to contribute with more Android animation examples I'm very happy to add those.

Yeah, I understand. thanks for the reply :)


Don't emit throw types at -gline-tables-only.

Caught by the debug-stdlib bots.
rdar://105651154

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves #NNNNN, fix apple/llvm-project#MMMMM.

@swift-ci test and merge

@swift-ci test and merge

@swift-ci please test macOS platform


Add cli commands for “volumeatt achment”

Coverage decreased (-0.2%) to 60.524% when pulling 468092f4d8793f46b4855d74c2b06615576a21b7 on PengYiOfOpenSDS:PengYi into e7f64bb7869c9c336528cf6154703a777e7a9c6e on opensds:development.

Good job!


Update setup.py

@wooparadog are there any blockers to merging this PR and releasing a new version of pystack?


rearange the readme and improve the wording.

Signed-off-by: Krasi Georgiev<EMAIL_ADDRESS>

lgtm


Stop command aliases and flag aliases from being suggested in shell completion

What type of PR is this?

bug fix

Which issue(s) this PR fixes:
This PR fixes #1875. It is the second try, now targeting v3. The first try, targeting v2, was in #1876.
Release Notes

- Command aliases and flag aliases are no longer included in shell completions (#1882)

@Juneezee didnt we say we want a runtime config flag to enable this behavior ?

Hi @dearchap. From my perspective as an avid user of the terminal and fan of CLI tools, I think shortcuts of commands being hidden during shell completion is more common (and personally, I prefer it this way also). Especially that this is targeting v3 so some small minor changes are OK. I am all for adding a flag to control this behavior.
Of course, you are the maintainer and the one to make the call.
We could also add an environmental variable that all CLI tools built with urfave/cli would respect. Perhaps SHELL_COMPLETION_SHOW_ALIASES? Think of it as something similar to the NO_COLOR env var, which is very widely respected.
So, if SHELL_COMPLETION_SHOW_ALIASES was to 1 or true, aliases of commands/flags would be shown. Maybe we could also get other popular CLI packages (such as e.g. Cobra) to adopt it? I'd be happy to know what you (maintainers) think about it :)

Yeah that makes sense

@dearchap Did you want to see the introduction of the SHELL_COMPLETION_SHOW_ALIASES environment variable switch that @bartekpacia described within this PR, or is merging now and adding in a follow-up acceptable?

Merging now is acceptable


TicTacToe

Yes.Actually I was unable to add folder.I will add 2 more files.

@vaishh29 ask her to create proper pr by mentioning issue no. in description

Yes.Actually I was unable to add folder.I will add 2 more files.

Please make a new pull request where all files you have created are present in one request itself . And when you are making the request mention the issue number and name properly

Okk.


Selective retries (on Idempotent methods)  not working right

Bug description
I would like to be able to configure RETRIES only for IDEMPOTENT methods . I have applied this in the virtual service but it appears that ALL methods (eg IDEMPOTENT GETS and NON-IDEMPOTENT POSTS) are retried
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Retries should be executed for Idempotent method calls (GET) and timeout in about 5-6 seconds for the test call.
As per the configured virtual service, calls to non-idempotent methods should not be retried
Could this be related to https://github.com/istio/istio/issues/13851 ?
Steps to reproduce the bug

Deploy httpbin (https://hub.docker.com/r/kennethreitz/httpbin/) in K8s/istio cluster
Install a virtual Service (see below) pointing to the httpbin deploy
Execute a GET curl or siege command that waits for a time . It will retry 5 times (waiting 1 seconds), timeout and return in about 5-6 seconds
Execute a POST curl or siege command that waits for a time . It should just wait and timeout eventually (in 10 -20) seconds, depending on the max delay in httpbin
I observe a timeout in 5-6 seconds, that indicates that the retry is in fact working when it should not.

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: "httpbin-virtual-service"
spec:
  hosts:
  - "*"
  gateways:
  - my-istio-gateway
  http:
  - match:
    - uri:
        prefix: /status
      method:
        exact: GET
    - uri:
        prefix: /delay

    retries:
      attempts: 5
      perTryTimeout: 1s
      retryOn: 5xx,gateway-error,connect-failure,refused-stream
    route:
    - destination:
        host: "httpbin"
        port:
          number: 80
  - match:
    - uri:
        prefix: /status
      method:
        exact: POST
    - uri:
        prefix: /delay
    retries:
      attempts: 0
    route:
    - destination:
        host: "httpbin"
        port:
          number: 80

Version (include the output of istioctl version --remote and kubectl version)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-21T15:34:43Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:16Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
[ocadmin@cmsplavm211 config]$

$ ./istioctl version
client version: 1.3.0
control plane version: 1.3.0

How was Istio installed?
Helm
Environment where bug was observed (cloud vendor, OS, etc)
Bare metal K8s cluster
Cluster Dump
istio-dump.tar.gz

I thought we could disable retries now since #14925.. Can you output the routes config? istioctl pc routes POD -ojson

Ok, I got this working, had to tweak the config a bit
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: "httpbin-virtual-service"
spec:
  hosts:
  - "*"
  gateways:
  - my-istio-gateway
  http:
  - match:
    - uri:
        prefix: /status
      method:
        exact: GET
    - uri:
        prefix: /delay
      method:
        exact: GET
    timeout: 20s
    retries:
      attempts: 5
      perTryTimeout: 3s
      retryOn: gateway-error
#      retryOn: 5xx,gateway-error,connect-failure,refused-stream
    route:
    - destination:
        host: "httpbin"
        port:
          number: 80
  - match:
    - uri:
        prefix: /status
      method:
        exact: POST
    - uri:
        prefix: /delay
      method:
        exact: POST
    route:
    - destination:
        host: "httpbin"
        port:
          number: 80

Results

$ siege -c1 -d1 http://<IP_ADDRESS>:31380/delay/10
** SIEGE 4.0.4
** Preparing 1 concurrent users for battle.
The server is now under siege...
HTTP/1.1 504    18.59 secs:      24 bytes ==> GET  /delay/10

PASS - Istio retries (1+5) x 3 = 18 s and times out on GET (as per expectation)

$ siege -c1 -d1 --content-type "application/json" '<IP_ADDRESS>:31380/delay/10 POST {"ids": ["1","2","3"]}'
** SIEGE 4.0.4
** Preparing 1 concurrent users for battle.
The server is now under siege...
HTTP/1.1 200    10.01 secs:    1078 bytes ==> POST http://<IP_ADDRESS>:31380/delay/10

PASS - Istio does not retry and returns after waiting 10 s on POST (above the threshold of a single retry)

$ siege -c1 -d1 --content-type "application/json" '<IP_ADDRESS>:31380/delay/2 POST {"ids": ["1","2","3"]}'
** SIEGE 4.0.4
** Preparing 1 concurrent users for battle.
The server is now under siege...
HTTP/1.1 200     2.01 secs:    1077 bytes ==> POST http://<IP_ADDRESS>:31380/delay/2

PASS - Istio does not retry and returns after waiting 2 s on POST (below the threshold of a single retry)

Here's the output from the target pod (attached). Does it match up with the config ?


fixed HAPU download link and typo

Changed the download link to the new version.
Fixed my nickname typo.
Extra line-ending spaces (2) were automatically removed.

:shipit:
On Feb 10, 2015 6:50 AM, "inket"<EMAIL_ADDRESS>wrote:

Changed the download link to the new version.
Fixed my nickname typo.
Extra line-ending spaces (2) were automatically removed.

You can view, comment on, or merge this pull request online at:
https://github.com/hummingbird-me/hummingbird/pull/412
Commit Summary

fixed HAPU download link and typo

File Changes

M app/frontend/app/routes/apps/index.js
https://github.com/hummingbird-me/hummingbird/pull/412/files#diff-0
(8)

Patch Links:

https://github.com/hummingbird-me/hummingbird/pull/412.patch
https://github.com/hummingbird-me/hummingbird/pull/412.diff

—
Reply to this email directly or view it on GitHub
https://github.com/hummingbird-me/hummingbird/pull/412.


Pressable component is missing variant property

Description
When I tried to style Pressable component for my footer, typescript gave me warning that: Property 'variant' does not exist on type 'IntrinsicAttributes & InterfacePressableProps ...
CodeSandbox/Snack link
https://codesandbox.io/s/exciting-colden-x5prjf
Steps to reproduce

Use Pressable component
Try to add:  variant="footer" to it
See error

NativeBase Version
3.4.0
Platform

[ ] Android
[ ] CRA
[X] Expo
[ ] iOS
[ ] Next

Other Platform
No response
Additional Information
The only way for me to style it is to change base styles, but that is not what we would prefer. It would be sweet to be able to use this generic component to the fullest wit the theme provider.

Hi @Jirijancik, This issue is fixed in version 3.4.16. Thanks for reporting this.


Fatal error: grunt.sprite requires a src, dest (img), and destCss property

i am getting this error after run grunt sprite
Fatal error: grunt.sprite requires a src, dest (img), and destCss property
//Sprite ===============================
var sprite;
config.sprite = sprite = {};
	  // Configure grunt
	  sprite.dist ={
	    sprite:{
	      all: {
	         src: 'public/images/*.png',
			dest: 'public/images/sprite/spritesheet.png',
			destCss: 'sass/sprites.css'
	      }
	    }
	  };

I have a feeling this is directly tied to #150. Closing this as a duplicate for now.

hi, thanks for your answer, that is my full gruntfile.js
https://gist.github.com/douglasdeodato/2137804a38ca1bc42f72
thank you.


Deprecated: Creation of dynamic property Curl\Curl::$rfc6265 is deprecated

What is the expected behavior?
Do not show the message.
What is the actual behavior?
It said "Deprecated: Creation of dynamic property Curl\Curl::$rfc6265 is deprecated in /home/yucho/CYAutoCheckIn/vendor/php-curl-class/php-curl-class/src/Curl/Curl.php on line 1908".
What steps will reproduce the problem?
Use setCookie method in PHP 8.2.
Code:
$testCURL=new Curl();
$testCURL->setUserAgent($user_agent);
foreach (getCookies($cookie) as $cookie) {
  $testCURL->setCookie($cookie['name'],$cookie['value']);
}
//......

This was just merged into master: https://github.com/php-curl-class/php-curl-class/pull/754

Yes, should be fixed in https://github.com/php-curl-class/php-curl-class/pull/754


Add contract mint link

Changes
Adds the mintURL field to the Contract type. mintURL initially supports Ethereum, Optimism, Base, Zora and Tezos.

Chain
Referral

Ethereum
mint.fun

Optimism
mint.fun

Base
mint.fun

Zora
zora.co

Tezos
objkt.com

When resolving a mint URL, the resolver checks if a mint URL is already present in the DB, and if so, it uses that as the mint link. If it doesn't exist, it either constructs it from a template or retrieves it from a provider. The resolver has an additional step of saving the mint URL in the DB so that future requests can get the mint link faster. Providers that sync contracts are now able to include a mint URL in their response so that mint URLs can also be saved when contracts are upserted.

Looks great!
I don't think it would make that much of a difference but it might be worth it to have the mint link get generated on each multichain provider just like you added for tezos. It only saves us an update to the database on the first call to retrieve a contract after this goes out which isn't really saving much, maybe it just makes more sense to me for a query field resolver not to be responsible with updating the database.

Good call! This is me being too lazy to write a backfill script to populate the links for existing contracts, I'll address this tmrw!


Improve FingerprintJS detection

FingerprintJS had moved away from their Valve GitHub account to their own website and repo.
Added new JS detection FingerprintJS for their new version 3 release

Thanks!


Edgo still incorrectly marks 1st line as a test

Hi, thank you for looking at this, but there is still one instance where it wrongly IDs a test where there is none, line 1. It seems that for some reason edgo always marks the first line as a test. It can be also seen on your screen shot in #2.

Hi, this is fine, cause it is necessary for python file execution

You mean by default edgo will always mark the first line on any python file as a test, even if there is no shebang in the file?

For some languages, it is possible to execute a file using a single command. Edgo adds a green button and spawns some process depending on the language when clicked. For example go, python, js, ts, java, bash.
Shebang is not supported yet, but in the future, of course, it will be.

For some languages, it is possible to execute a file using a single command. Edgo adds a green button and spawns some process depending on the language when clicked. For example go, python, js, ts, java, bash.
Shebang is not supported yet, but in the future, of course, it will be.

Would you consider then making this play icon having a different colour to differentiate from execution of  tests? Either way this issue can be closed


GENERIC_DOWNLOAD_PAGE #874

GENERIC_DOWNLOAD_PAGE #874
Pushing first commit to check if everything works fine with the rebase :D

I think we need to put this one on hold for the time being until I can decide what exactly to do and how to design this one. I haven't really thought of how I want this to look

@YashGovekar These are all the critical bugs right now, maybe comment on one you want to look at?
https://github.com/nabeelio/phpvms/issues?q=is%3Aopen+is%3Aissue+milestone%3A7.0.0+label%3Abug
And I will make clearer for this issue what to do do you can have that when you're ready

I think we need to put this one on hold for the time being until I can decide what exactly to do and how to design this one. I haven't really thought of how I want this to look

Oh okay, sure.

And I will make clearer for this issue what to do do you can have that when you're ready

Sure, I'll check them out and comment on the one I would like yo solve.


Schema: add consistency checks for width/height

Reported for PDF object and image stream; if these are different it might indicate a problem

Done.


[86c04hbeu][data-table] data table sort column properties

Motivation and Context
I've disabled changing sorting columns width by default.
I've added changeSortSize to enable this logic on columns and sortSizeRecalculation to set by which columns we should recalculate width of table. By default we using column width maximum width.

How has this been tested?
Manually

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[X] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Nice improve.

Checklist:

[X] My code follows the code style of this project.
[X] I have updated the documentation accordingly or it's not required.
[X] Unit tests are not broken.
[X] I have added changelog note to corresponding CHANGELOG.md file with planned publish date.
[ ] I have added new unit tests on added of fixed functionality.

A line break in the "KD, %" column appeared in Firefox:

2. Also discussed to slightly change the examples: make the "Vol" column noticeably smaller than "Keyword", and in the last example assign the sortSizeRecalculation prop to the "Vol", so it's obvious that we can take space from a column that's not the largest.

Fixed the first one and changed examples


export src/cli/* in src/index

Clear and concise description of the problem
Which could make secondary development more convenient.
Suggested solution
export * from './cli/exit-code.ts'
export * from './cli/index.ts'
export * from './cli/parse-args.ts'

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I think it may be unnecessary.


Minimum requirements to build source code

What are the "minimum requirements" in order to build the source code from scratch?

Visual Studio version
.Net version
OS version
Git version
...

I think we need to discuss the development environment.
Build requires .net sdk only.

sure.
maybe we need to change this issue to a complete README.md with multiple required parts. (eg. introduction, requirements, build, test, contribution guide, ...)

I'm closing this issue in favor of the new and more polished issue (#339)


Set required proto field for user and provider token

Summary
Ref #4952
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 55.149% (+0.007%) from 55.142%
when pulling 4c10f55206f2c8620c77157229f70deddea9ab11 on eleftherias:openapi-provider-user
into 93c054ada70b19ca8bbc68521ca81a6b0abd0f6b on mindersec:main.


Issue with New-HTMLTableCondition

Hi Klys,
I'm using you rmodule to generate an Certificate report and there is an issue with New-HTMLTableCondition with Date
eg :
# Gathering Date
$MachineCerts = foreach ($Container in $AllMachineCertContainers)
{
    Get-ChildItem -Path Cert:\LocalMachine\$Container
....
# Begining report
# ...
 New-HTMLTable -DataTable $MachineCerts {
                New-HTMLTableCondition -Name 'NotAfter' -Type date -Operator lt -Value $(Get-Date) -BackgroundColor Orange
            }#end-newhtmltable

As you could see in the attach screenshoot, I'm thinking there is a issue with the TableCondition.
My current culture is FR-Fr. I've also checked that the Type of the NotAfter property. It's a [DateTime] type. Then, I'm thinking that it's the way the cmdlet compares Dates that is problemtic.
Could you investigate ?
Sorry for the inconvenience.  :-)
Regards
Olivier

You should read on: https://evotec.xyz/advanced-html-reporting-using-powershell/
There's topic of date comparison covered there.


Skip Link v1

### Deliverables
- [ ] Characteristics spec
- [ ] Interaction spec
- [ ] Accessiblity spec
- [ ] Figma component

### Checklist
- [ ] UITK audit
- [ ] Landscape - Additional opportunities Salt should consider
- [ ] Scope + Kick off - Describe, and update/create issues for, logical version releases; Hold kick off meeting to align team
- [ ] Characteristics - Define tokens for v1
- [ ] Interaction - Define behaviours for v1
- [ ] ADA - Define the accessible experience of v1
- [ ] Documentation - Populate template with stories and best practices
- [ ] Build & QA - (Capacity dependent) Assist as required with build and QA to spec

### Dev Checklist
- [ ] Density (HD, MD, LD, TD)
- [ ] Mode (Light, Dark)
- [ ] Fill (Primary, Secondary, Tertiary)
- [ ] State (Default, Hover, Selected/Active, Disabled, Read-only, Other)
- [ ] Controlled API
- [ ] UITK accessibility parity (screen reader + keyboard interactions)

### Features
- [ ] Single Skip Link
- [ ] Investigate focus ring vs yellow fade technique
- [ ] Clear and usable design of a working example

Hi Stella, can you please post any updates to this issue and where the work stands? Thanks! @maj-stella

Replaced by #2385


Using CSS layers breaks rules which utilize variables

UnoCSS version
0.53.5
Describe the bug
When applying rules like shadow-* inside a layer-xxx: CSS layer, the variables utilized to control shorthand properties are all overridden by the default variable declarations applied to *.

While I understand this is technically working as designed (the rule was generated in the layer as specified, and any non-layer CSS like those variable declarations will override layer rules) it's unexpected from the perspective of usage, and leads to a lot of implicit behavior causing silent CSS failures like the one pictured only for particular rules.
My goal in using CSS layers here was to set up some default built-in styles for reusable components which can be easily overridden at the point of usage without worrying about specificity-- so styles for "Button" will all be in a components layer, button variants will be in variants, and then all user-applied classes will beat both of those. It seemed effective and even elegant, but now I can't apply box-shadows or transforms or a number of other rules as part of this paradigm.
Reproduction
https://unocss.dev/play/?html=DwIwrgLhD2B2AEBjANgQwM7oLwCI0E8BTAJwFoAPALnQAtUATaAd3gJIursadNQFsQJHAD4AKoXQRgAenBQ4wgFChIMBCgzYctBs3g7uvAULESps1QqA&config=JYWwDg9gTgLgBAbwFBzgEwKYDNgDsMDCEuOA5gDQpxhQYDOGMAgjDFMAEYCuMwWAnpVQ16jAJIBjYnSHVaDGAFVcESgF84WKBBBwA5FxUS6dPUiQYAHpFjpsAQy4AbeJhz4iJYKQAUyVFDO9ABccADaVKhhehJcdDA6ALSBThh65IhwUk7QoXq0aHpwagC6VCWydAAW0DCxMHSh-qj6sfFJ1bX1enkwVjCJTqRwfZYD0Pa4pBhwNQBuGFDBowN99k5mqGqyIgqN4ZFyokoqPgCUssLyjCxsnDx8-OeXRwqS0n6HqHQS6xihAEYAHQAJheqAkaFweSqrDAjQA9Aj6CAgdUEZsWmoLuUkNikEA&css=Q&options=N4XyA
System Info
Windows 11, Chrome 114, React
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

After thinking about this, I guess what I really need to do is move the base variable declarations from preset-mini to a layer which is ordered with less precedence than my other layers. Makes sense that this is not something Uno can really do without understanding my layer structure.
Is it too picky to have this be configurable in the built-in presets? Seems like I should just fork and maintain my own if I need this, but building from an existing preset is really convenient.
Feel free to close if this seems like a wontfix. Once nice thing about building all functionality in presets/plugins is I do have a userland way to fix the behavior, even if it is tedious.

I thought a bit harder and I've found a solution that works for me. Perhaps someone else will need to solve this too.
I turned off preflights in my Uno preset, then recreated them in a new CSS layer, following the preset-mini source code...
{
	layer: 'preflights',
	getCSS: (ctx: PreflightContext<any>) => {
		if (ctx.theme.preflightBase) {
			const css = entriesToCss(Object.entries(ctx.theme.preflightBase));
			const roots = toArray(
				ctx.theme.preflightRoot ?? ['*,::before,::after', '::backdrop'],
			);
			return roots
				.map((root) => `@layer preflightBase{${root}{${css}}}`)
				.join('');
		}
	},
} as any,

the any cast is just because the theme situation is more complicated for my custom preset and I didn't want to figure out typings.
The relevant part is adding @layer preflightBase{} around the original ${root}{${css}} bit.
Then I added this new layer to my existing layer ordering in my own preflight
@layer preflightBase, components, variants, utilities;

And that seems to have worked great, without having to ditch my Uno preset. The base CSS vars are all defined within their own low-ranking layer, so other layered rules take precedence and can override them correctly.


Measurement Extraction Enabled

Please review the changes

you rock. Merged, and PR coming your way @manalishah


Improve ResolveAfterDone flakiness

Tested, after changing to Promise.resolve().then(() => context.done()) I get logs on ~90% of individual scenario runs.  Bumping the scenario run count to 5 as well.  Still not promising five 9s haha.

Hi @mamaso, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.


Adds Hound-CI configuration file

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #59   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           6      6
  Lines         273    273
=====================================
  Hits          273    273

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 50f9b7c...5c9632d. Read the comment docs.

@bmeneguele well, we can run flake8 on Travis, but I going to tell why I like Hound.
 On the other hand, using only Travis we would have a build failed and have to go read the verbose log on Travis console.
Second, we would have one of these behaviors: fail and stop the build before run the tests showing only the coding style issues but perhaps some tests would fail; stoping the build when the first test fails and don't even run the coding style check; or configuring to keep running the build no matter what and at the end having a verbose log full of errors. Looking for erros to fix might be a little bit tricky for newbies on programming.
I believe that running the unittests and the coding style check separatedly we would not only have a better overview on the issues but also reduce the amount of commits and pushes till the pull request get accepted.
But as I've said this is my opinion. What do you think guys? Do you have any suggestion?

Well, I understand your point, and that's fine by me. My concern was based on some projects I already found containing more external tooling/infrastructure bootstrap code than their own project's code.. and I honestly think that this kind of situation falsely decreases the "complexity" for newbies, since they'll be required to understand not only project's code, but the external infrastructure/process too.
But I know, that's not our case, we're fine in the number of tools being used :) just would like to make sure we aren't making our "currently simple project" bloated.
Thanks for the reasoning :+1:


[SPARK-22324][SQL][PYTHON][FOLLOW-UP] Update setup.py file.

What changes were proposed in this pull request?
This is a follow-up pr of #19884 updating setup.py file to add pyarrow dependency.
How was this patch tested?
Existing tests.

Btw, should we add 'Programming Language :: Python :: 3.6' to classifiers?

Test build #85424 has started for PR 20089 at commit 36614af.

Test build #85424 has finished for PR 20089 at commit 36614af.

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

Merged build finished. Test PASSed.

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

Yea, I think we could. I added the support and tested it before - SPARK-19019. I think it's okay to add it they are just metadata AFAIK.

@HyukjinKwon Thanks! I'll add it soon.

Test build #85425 has started for PR 20089 at commit bee3c69.

@HyukjinKwon I'll update it as well.

Test build #85426 has started for PR 20089 at commit 896f752.

Test build #85425 has finished for PR 20089 at commit bee3c69.

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

Merged build finished. Test PASSed.

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

Test build #85426 has finished for PR 20089 at commit 896f752.

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

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

Merged build finished. Test PASSed.

Test build #85432 has started for PR 20089 at commit e142e69.

Test build #85432 has finished for PR 20089 at commit e142e69.

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

Merged build finished. Test PASSed.

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

Still LGTM

Test build #85434 has started for PR 20089 at commit d8d9564.

Test build #85434 has finished for PR 20089 at commit d8d9564.

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

Merged build finished. Test PASSed.

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

Merged to master.


Option to display loaders output to shell only, not devtools

Do you want to request a feature or report a bug?
Feature request
What is the current behavior?
webpack 2.7.0
webpack-dev-middleware 1.12.0
webpack-hot-middleware 2.18.0
The output of loaders (eg. eslint) is currently rendered in both the shell console and the devtools console. The quiet option disable it entirely.
What is the expected behavior?
When I'm importing code or while debugging, the output of eslint is redundant between my shell and the devtools console.
Or I'd like to see only logs from the currently running app on my devtools, not being polluted by eslint output. I know that this annoyance shall be resolved by solving the eslint errors, but when I'm coding I do not want to see the console or debugger warnings, yet I'd like to see those in my shell. Plus, some warnings are just warnings and definitely shouldn't make it harder to see the actual console messages from the app.
I'd like to be able to configure the desired output (devtools console, shell console, or both).

One of the main goals of this module is to put all the relevant build infomation into your browser, so you don't need to look at the console when using it.
If you have warnings that you never intend to resolve, I'd suggest you should disable those warnings entirely otherwise you might miss genuine warnings.
It makes sense to me why you'd want to ignore console/debugger warnings during development, but not want to lose track of them at the end.
Personally, I never use eslint loader. I only use eslint in my editor directly, or as part of CI.

That said, I'd accept a PR which provided the options to allow logging to be configured as console | browser | both | none.

Hiding devtools output can be achieved by adding quiet=true to the hot client params:
'webpack-hot-middleware/client?quiet=true'


The duration and position are inconsistent with larger tracks(+1 hour).

Describe the bug
First of all, thanks for this amazing library. 🙌
This only happens on android. iOS works well.
If I use tracks longer than one hour the position exceeds the duration and the duration and position returned are inconsistent.  I realized that if I started the track from beginning and let it run until the end this not happen. Only when I seek to a new position.
It's very strange, if I seek to (seekTo) closer to the end, the difference is less than if I seek to a position less close to the end of the track.
I'm testing with 7 different tracks loaded from network and in some cases the duration and position are inconsistent. I'm adding the duration in the track object add([]). Also my audios have 44.1 kHz of sample rate and they are MP3 files.
I changed the build preferences for the app using many values in track-player.json
Results of my test:
const durations = [
  1177.3648979591837, // 19:36 - Works
  2420.1404081632654, // 40:19 - Works
  3549.126530612245, // 59:08 - Works
  3934.1975510204084, // 01:05:40 - Doesn't work
  4977.502040816326, // 1:24:56 - Doesn't work
  5415.758367346939, // 1:30:14 - Doesn't work
  8872.724, // 2:27:55 - Doesn't work
];

To Reproduce
I create a repository to reproduce the issue 👉  https://gitlab.com/edgargrs/rntrackaudioplayerexample
Environment:
System:
    OS: macOS 11.2.2
    CPU: (8) arm64 Apple M1
    Memory: 130.89 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.0.0 - ~/.nvm/versions/node/v16.0.0/bin/node
    Yarn: 1.22.10 - /opt/homebrew/bin/yarn
    npm: 7.10.0 - ~/.nvm/versions/node/v16.0.0/bin/npm
    Watchman: 4.9.0 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK:
      API Levels: 22, 23, 25, 27, 28, 29, 30
      Build Tools: 23.0.3, 24.0.3, 25.0.3, 26.0.3, 27.0.3, 28.0.3, 29.0.2, 29.0.3, 30.0.2, 30.0.3
      System Images: android-24 | Google APIs Intel x86 Atom, android-25 | Google APIs ARM 64 v8a, android-25 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>99119
    Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_242-release - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.2 => 0.64.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

What react-native-track-player version are you using?
This happens on the plugin version: v2.0.0-rc18 and v1.2.7
In master branch I'm using v2.0.0-rc18
I created another branch with the version v1.2.7 and the same happens.
v2.0.0-rc18  👉  https://gitlab.com/edgargrs/rntrackaudioplayerexample
v1.2.7 👉  https://gitlab.com/edgargrs/rntrackaudioplayerexample/-/tree/v1.2.7

Probably related issues
983
963
860
629
228

After test another playback libraries, and a little research I realized that the problem was with the MP3s.
it seems that the MP3 files are not inherently seekable.
https://stackoverflow.com/questions/53742145/precise-seek-in-mp3-files-on-android
I solved this problem by changing the MP3 for M4A format.


feat: Simplify QueryPlanner AST for CEL comprehensions

Signed-off-by: Dennis Buduev<EMAIL_ADDRESS>Description

Adds support for CEL comprehensions in the Query Planner API.
Introduces a custom AST for them.

Checklist

[x] The PR title has the correct prefix
[ ] PR is linked to the corresponding issue
[x] All commits are signed-off (git commit -s ...) to provide the DCO

Codecov Report

Merging #870 (04fd9d3) into main (112b614) will increase coverage by 0.38%.
The diff coverage is 68.42%.

@@            Coverage Diff             @@
##             main     #870      +/-   ##
==========================================
+ Coverage   54.41%   54.80%   +0.38%
==========================================
  Files         102      102
  Lines       11036    11124      +88
==========================================
+ Hits         6005     6096      +91
+ Misses       4523     4519       -4
- Partials      508      509       +1

Impacted Files
Coverage Δ

internal/engine/planner.go
78.37% <64.86%> (-0.53%)
:arrow_down:

internal/engine/ast.go
78.21% <71.42%> (-1.11%)
:arrow_down:

internal/engine/engine.go
72.72% <100.00%> (+1.52%)
:arrow_up:

internal/server/tests.go
95.13% <0.00%> (+0.91%)
:arrow_up:

internal/storage/index/builder.go
84.35% <0.00%> (+5.02%)
:arrow_up:

internal/compile/errors.go
55.55% <0.00%> (+15.87%)
:arrow_up:

I've updated the docs with the new example. I've removed the note.

I know you're adding more tests but I am merging this right now so that I can do some refactoring of the protobufs without creating a huge merge conflict.


Cannot read property 'pointSize' of null

Which platform(s) does your issue occur on?

iOS
iOS: 14.3
emulator

Please, provide the following version numbers that your issue occurs with:

CLI: 8.0.1
@nativescript-community/ui-label": "^1.1.10
@nativescript/ios": "8.0.0

Please, tell us how to recreate the issue in as much detail as possible.
When I try to use HTMLLabel it gives me the following exception:
***** Fatal JavaScript exception - application has been terminated. *****
NativeScript encountered a fatal error: Uncaught TypeError: Cannot read property 'pointSize' of null
at
updateHTMLString(file: src/webpack:/checkpointcurly/node_modules/@nativescript-community/ui-label/label.ios.js:349:0)
at _setNativeText(file: src/webpack:/checkpointcurly/node_modules/@nativescript-community/ui-label/label.ios.js:443:0)
at onResumeNativeUpdates(file: src/webpack:/checkpointcurly/node_modules/@nativescript-community/ui-label/label-common.js:44:0)
at _resumeNativeUpdates(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:280:0)
at onLoaded(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:235:0)
at onLoaded(file: src/webpack:/checkpointcurly/node_modules/@nativescript-community/ui-label/label.ios.js:159:0)
at (file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:318:0)
at callFunctionWithSuper(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:312:0)
at callLoaded(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:318:0)
at loadView(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:458:0)
at (file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:237:0)
at eachChildView(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/layouts/layout-base-common.js:101:0)
at eachChild(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view/view-common.js:759:0)
at onLoaded(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:236:0)
at (file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:318:0)
at callFunctionWithSuper(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:312:0)
at callLoaded(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:318:0)
at loadView(file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:458:0)
at (file: src/webpack:/checkpointcurly/node_modules/@nativescript/core/ui/core/view-base/index.js:237:0)
at eachChildView(fi<…>

It's only happening to me on iOS, on android it works fine. I am also in NS 8 (I had not tried this plugin before so I could not tell if it only happens in 8). My code:
  <HTMLLabel
          width="100%"
          height="50"
          :autoFontSize="true"
          :textWrap="true"
          :html="username"
          maxFontSize="30"
        />

@vallemar should be fixed in 1.1.11

@farfromrefug Now the error has been solved but the line skipping does not do well. When the text overflows it jumps to the next line.

it worked here. can you show?

Hi @farfromrefug, I have tried the following two settings: textWrap = true and textWrap = false. The result is the same. I show an image of how it looks in both cases: (the text is Lorem Ipsum is....)

The code:
  <HTMLLabel
                width="100%"
                :autoFontSize="true"
                :textWrap="false"
                :html="username"
                maxFontSize="30"
              />

@vallemar i honestly dont see what s wrong here. What are you expecting?

Ah OK, the problem is that it does not respect the TextWrap property, the text should resize in 1 line and as seen in the previous image there are 3 lines

what if you use "text" instead of "html" ? don't use "html" if you don't have html code

ah ok, sorry I hadn't seen the text property. Anyway, the behavior is the same as with html, the textWrap property does not respect it, even with text I don't see that the text is resized

@vallemar should be fixed in 1.1.12


Dev/asolovev add comm profiling

Description
Add a comprehensive description of proposed changes
List associated issue number(s) if exist(s): #6 (for example)
Documentation PR (if needed): #1340 (for example)
Benchmarks PR (if needed): https://github.com/IntelPython/scikit-learn_bench/pull/155 (for example)

Checklist to comply with before moving PR from draft:
PR completeness and readability

[ ] I have reviewed my changes thoroughly before submitting this pull request.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
[ ] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[ ] I have added a respective label(s) to PR if I have a permission for that.
[ ] I have resolved any merge conflicts that might occur with the base branch.

Testing

[ ] I have run it locally and tested the changes extensively.
[ ] All CI jobs are green or I have provided justification why they aren't.
[ ] I have extended testing suite if new functionality was introduced in this PR.

Performance

[ ] I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
[ ] I have provided justification why performance has changed or why changes are not expected.
[ ] I have provided justification why quality metrics have changed or why changes are not expected.
[ ] I have extended benchmarking suite and provided corresponding scikit-learn_bench PR if new measurable functionality was introduced in this PR.

/intelci: run

/intelci: run


Integrated Terminal split terminal sizing issue

VSCode Version:

Version: 1.39.0-insider (user setup)
Commit: 7edc8f786e065edbc9540f1e19ebd9220b9e0cf9
Date: 2019-09-05T05:42:21.072Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134

OS Version: Windows 10 pro

Steps to Reproduce:

Open two or more terminals in split mode and the text sizing is about 1/2 the width of the terminal window

Does this issue occur when all extensions are disabled?: Yes

/duplicate https://github.com/microsoft/vscode/issues/80404


Cannot implement an xsmall breakpoint v6.4.1

I am unable to add an xsmall breakpoint to the list of breakpoints. Anything other than small: 0 seems to fail.
Seems related to issue 10015
How to reproduce this bug:
make your breakpoint settings like this
$breakpoint-classes: (xsmall, small, medium, large, xlarge, xxlarge);
$breakpoints: (
  xsmall: 0,
  small: 360px,
  medium: 480px,
  large: 600px,
  xlarge: 840px,
  xxlarge: 1280px
);

What should happen:
I should have an xsmall breakpoint as the lowest breakpoint
What happened instead:
WARNING: null was passed to rem-calc(), which is not a number.
Backtrace:
    node_modules/foundation-sites/scss/util/_unit.scss:78, in function `-zf-to-rem`
    node_modules/foundation-sites/scss/util/_unit.scss:47, in function `rem-calc`
    node_modules/foundation-sites/scss/grid/_row.scss:83, in mixin `@content`
    node_modules/foundation-sites/scss/util/_mixins.scss:277, in mixin `@content`
    node_modules/foundation-sites/scss/util/_breakpoint.scss:153, in mixin `breakpoint`
    node_modules/foundation-sites/scss/util/_mixins.scss:276, in mixin `-zf-each-breakpoint`
    node_modules/foundation-sites/scss/grid/_row.scss:82, in mixin `grid-row-nest`
    node_modules/foundation-sites/scss/grid/_flex-grid.scss:29, in mixin `flex-grid-row`
    node_modules/foundation-sites/scss/grid/_flex-grid.scss:136, in mixin `foundation-flex-grid`
    scss/_core.scss:17, in mixin `bonsai-core`
    scss/global.scss:35, in mixin `bonsai`
    stdin:3

webpack: Failed to compile.

compiled with:
webpack
sass-loader
Foundation Version(s) you are using:
6.4.1

I'm using a xsmall breakpoint for all of my project too and ran into the same issue. Thanks for reporting!

The smallest breakpoint must be small: 0. It is fixed.
I use something like small, smedium and medium

@jashwant I can see that it is fixed at small: 0 but that seems like poor behavior, especially as it's not documented, and the documentation implies that xsmall: 0 should be possible.
Do you know exactly where in the codebase the smallest breakpoint is fixed as small: 0?
instead of small it should just be first($breakpoint-classes)

@shonin , there has been a lot of discussion about it on github.
This should answer your question.
https://github.com/zurb/foundation-sites/issues/7644
https://github.com/zurb/foundation-sites/issues/8257
Bottomline is small: 0 is fixed. I don't like it either.

@kball according to our brief conversation on slack you indicated that having small: 0 fixed is poor behavior that should be fixed. Looking at these two linked issues in the above comment from @jashwant seems to contradict that.
Is it worth pursuing this work? If not should the documentation be updated to state this behavior?

@shonin my sense from reading back through these issues is that the current behavior was a compromise solution, and looking at the timing at least some of that was in the crunch to get to the first version 6 release. I think we should definitely consider improving this

So when did this issue arise. I know I've used x-small breakpoint in other versions of Foundation 6.

Closing. According to #10383 this was fixed in #10491


Unit Tests

We have room for a lot more unit tests to be added

Tests for what?

Each and every function

Each and every function

I don't think that is feasible, considering we are live-testing the API.

Why not? It was always planned for every function to be tested live from the start.

Why not? It was always planned for every function to be tested live from the start.

https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment
I would like to somehow use this to trigger the workflow to test this way when one of the contributors of the repo leave a comment on a PR once its finalized we can leave a comment like deno test and it would run the tests

https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment
I would like to somehow use this to trigger the workflow to test this way when one of the contributors of the repo leave a comment on a PR once its finalized we can leave a comment like deno test and it would run the tests


Dimension error when evaluate on inloc dataset.

Hello!
I'm going to try your method on InLoc dataset.
When I ran the eval/eval_inloc_extract.py. I got this error.
Traceback (most recent call last): File "/media/pc/E68247168246EB1F/sparse-ncnet/eval/eval_inloc_extract.py", line 167, in <module> args File "/media/pc/E68247168246EB1F/sparse-ncnet/lib/relocalize.py", line 187, in eval_model_reloc corr4d = corr_and_add(feature_A, feature_B, k = model.k, Npts=None) File "/media/pc/E68247168246EB1F/sparse-ncnet/lib/sparse.py", line 147, in corr_and_add scorr = ME.MinkowskiUnion()(scorr,scorr2) File "/home/pc/.pyenv/versions/anaconda3-5.3.1/envs/sncnet/lib/python3.6/sitepackages/MinkowskiEngine/MinkowskiUnion.py", line 100, in __init__ assert dimension > 0, f"dimension must be a positive integer, {dimension}" AssertionError: dimension must be a positive integer, -1
Could you provide some ideas about how to solve it?
Thank you very much!

It seems some tensor is empty. Maybe you can set a breakpoint and debug
with import pdb; pdb.set_trace()?
El dt., 9 de juny 2020, 10:48, PANCHEN<EMAIL_ADDRESS>va
escriure:

Hello!
I'm going to try your method on InLoc dataset.
When I ran the eval/eval_inloc_extract.py. I got this error.
Traceback (most recent call last): File
"/media/pc/E68247168246EB1F/sparse-ncnet/eval/eval_inloc_extract.py", line
167, in  args File
"/media/pc/E68247168246EB1F/sparse-ncnet/lib/relocalize.py", line 187, in
eval_model_reloc corr4d = corr_and_add(feature_A, feature_B, k = model.k,
Npts=None) File "/media/pc/E68247168246EB1F/sparse-ncnet/lib/sparse.py",
line 147, in corr_and_add scorr = ME.MinkowskiUnion()(scorr,scorr2) File
"/home/pc/.pyenv/versions/anaconda3-5.3.1/envs/sncnet/lib/python3.6/site-packages/MinkowskiEngine/MinkowskiUnion.py",
line 100, in init assert dimension > 0, f"dimension must be a positive
integer, {dimension}" AssertionError: dimension must be a positive integer,
-1
Could you provide some ideas about how to solve it?
Thank you very much!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ignacio-rocco/sparse-ncnet/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3LX3CUZOCYHMIJCDRGH4DRVXZOJANCNFSM4NZF7KBQ
.

It seems some tensor is empty. Maybe you can set a breakpoint and debug
with import pdb; pdb.set_trace()?

Thank you for your quick reply.
I checked the shape of scorr and scorr2 after transfering to sparseTensor. They are both 300000*1 Tensor.
They are not empty. But MinkowskiUnion()(scorr, scorr2) is failed due to the above reason.
Maybe they didn't satisfy the dimension they are supposed to be?


Open RPGLint.json fails

F1 and "RPGLE: Open RPGLE ling configuration" fails with this message:

There is nothing in the Code for IBM i OUTPUT tab.
I can open the file:

I just have to remember where it is.
I do not have read only set:

⚠ REMOVE THIS LINE AND ANY SENSITIVE INFORMATION BELOW! ⚠

Context
Version

Code for IBM i version
2.6.5

Visual Studio Code version
1.85.1

Operating System
win32_x64

Active extensions
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.4.0
Db2 for IBM i (vscode-db2i): 0.6.1
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.16.0
Extension Authoring (extension-editing): 1.0.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.6
JSON Language Features (json-language-features): 1.0.0
Merge Conflict (merge-conflict): 1.0.0
NPM support for VS Code (npm): 1.0.1
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Overtype (overtype): 0.5.0
RPGLE (vscode-rpgle): 0.24.0
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0

Remote system

Setting
Value

IBM i OS
V7R5M0

Tech Refresh
n/a

CCSID
37

SQL
Enabled

Source dates
Disabled

Enabled features

/QOpenSys/pkgs/bin
/usr/bin
/QSYS.lib/LENNONS2.lib
/QSYS.LIB
/QIBM/ProdData/IBMiDebugService/bin

bash
attr
GENCMDXML.PGM
QZDFMDB2.PGM
startDebugService.sh

chsh
iconv
GETNEWLIBL.PGM

git
setccsid

grep

ls

md5sum

sort

stat

tar

tn5250

Shell env
BUILDLIB=LENNONS1
CURLIB=LENNONS1
HOME=/home/LENNONS
HOST=pub400.com
IFS_LIB=LENNONSB
IFS_SRCPF=VSCODE
LIB1=LENNONSB
LIBLS=LENNONSB LENNONS1 QGPL QTEMP QIWS
LOGIN=lennons
LOGNAME=lennons
MAIL=/var/spool/mail/lennons
OLDPWD=/home/LENNONS
PASE_USRGRP_LIMITED=N
PATH=/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/LENNONS
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=<IP_ADDRESS> 51648 2222
SSH_CONNECTION=<IP_ADDRESS> 51648 <IP_ADDRESS> 2222
TZ=<UTC>0
USER=lennons
USERNAME=lennons
_=/QOpenSys/pkgs/bin/env

Variants
{
  "american": "#@$",
  "local": "#§$"
}

Errors
[
  {
    "command": "/QOpenSys/usr/bin/qsh",
    "code": 1,
    "stderr": "CPD0032:  Not authorized to command CRTLIB in library *LIBL.\nCPF0001:  Error found on CRTLIB command.",
    "cwd": "/home/LENNONS"
  },
  {
    "command": "/QOpenSys/usr/bin/qsh",
    "code": 1,
    "stderr": "CPF2125:  No objects deleted.",
    "cwd": "/home/LENNONS"
  }
]

Found the cause of the issue. Some changes to our internal API was not reflected here. Working on a fix.


Integration stops working after a period of time.

Hello,
The integration randomly stops working and data not up to date anymore.
Doing a rboot of the integration, fixes the issue for a short period.
The log is giving me 2 errors in cloud.py, line 333 and 59.
2023-02-27 14:17:36.128 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001693779_energy is taking over 10 seconds
2023-02-27 14:17:37.762 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1001690466', 'apikey': '******', 'sequence': '1677503852006'}
2023-02-27 14:17:38.745 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-27 14:17:38.754 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-27 14:40:58.934 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '10016903ca', 'apikey': '', 'sequence': '1677505253008'}
2023-02-27 14:41:00.087 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001690466_energy is taking over 10 seconds
2023-02-27 14:41:01.856 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1001690466', 'apikey': '*************', 'sequence': '1677505256007'}
2023-02-27 15:55:18.568 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_10016936f0_energy is taking over 10 seconds
2023-02-27 15:55:18.583 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001690850_energy is taking over 10 seconds
2023-02-27 15:55:18.587 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_10016949d8_energy is taking over 10 seconds
2023-02-27 15:55:18.592 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001694a23_energy is taking over 10 seconds
2023-02-27 15:55:18.597 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001692aba_energy is taking over 10 seconds
2023-02-27 15:55:18.601 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_100169365e_energy is taking over 10 seconds
2023-02-27 15:55:18.605 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001691785_energy is taking over 10 seconds
2023-02-27 15:55:18.609 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_10016924d3_energy is taking over 10 seconds
2023-02-27 15:55:18.614 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_100169206b_energy is taking over 10 seconds
2023-02-27 15:55:18.618 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_10016937b2_energy is taking over 10 seconds
2023-02-27 15:55:18.622 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonoff_1001691929_energy is taking over 10 seconds

And again:
2023-02-28 11:42:23.167 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1001321643', 'apikey': '*********', 'sequence': '1677580938001'}
2023-02-28 11:42:26.381 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.386 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.401 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.409 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.418 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.425 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.438 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 333, in _process_ws_msg
self._set_response(data["sequence"], data["error"])
File "/config/custom_components/sonoff/core/ewelink/cloud.py", line 59, in _set_response
self._waiters[sequence].set_result(result)
asyncio.exceptions.InvalidStateError: invalid state
2023-02-28 11:42:26.449 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

Same here I can reload it but it fails within a few hours max. I setup an automation to reload it after it becomes unknown or unavailable. But this should only be a temp fix.

I've been experiencing issues also for a week or so. Devices are not syncing with the actual sonoff device state. Random and only a reboot of HA sync them correctly again. I wake up in the morning and some of the exterior lights are showing as on but they are off and show as off on the ewlink app.
Been working flawlessly last 2 years.
Hope there is a fix soon thanks

Same  issue after the last update.
System:
Home Assistant 2023.3.1
Supervisor 2023.01.1
Operating System 7.5
Frontend 20230302.0 - latest
Sonoff lan 3.4.0

Same issue here! I hope to have a response from developers.

I am seeing this as well.  It might not take down all the integrations at once, I only have a few but they eventually become unavailable.

same here. Just reloaded ha to resync status. ewelink was working

same here, I have to reload sonoff plugin to get it working again
any solution will be appreciate
thank you

as of today after updating last night, i'm experiencing the "unavailable" multiple times a day (rather than it seemingly happening overnight sporadically before).
this is driving me bonkers.  Happy to help in any troubleshooting to whoever is dev for this integration.  @AlexxIT ?

Same problem.

hey all, a great workaround since this issue doesn't appear to be being worked on,  is to create an automation to monitor a sonoff device and restart the service automatically.  its not a perfect solution but hopefully it should make the devices work for "most" of the time.
https://github.com/AlexxIT/SonoffLAN/issues/1138#issuecomment-1478580171

Same problem here - all Sonoff devices become unavailable one by one. It doesn't take very long after reloading the integration for them to all go offline again.

Looks like cloud servers can't response on energy request. Exception fixed in latest master version. Will be in the next release

HI Alex
Is it valid also for local devices? I have to be rollback to have a stable release. All my son off are local. Thanks

On 30 Mar 2023, at 11:51, Alex X @.***> wrote:
Looks like cloud servers can't response on energy request. Exception fixed in latest master version. Will be in the next release
—
Reply to this email directly, view it on GitHub https://github.com/AlexxIT/SonoffLAN/issues/1125#issuecomment-1490016620, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXK6MPUM2BKAYZZZ4ULPLN3W6VJSHANCNFSM6AAAAAAVKOPRVI.
You are receiving this because you commented.

@Claudio1L have you show logs with your problem?

No, i rebooted couple of times after two events, before understanding was
an integration issue. Then I quickly rolled back.
I can try again to get logs. The problem is that I don’t know when the
issue start. If I’m not at home could be an issue
Claudio
Il giorno gio 30 mar 2023 alle 12:38 Alex X @.***> ha
scritto:

@Claudio1L https://github.com/Claudio1L have you show logs with your
problem?
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/SonoffLAN/issues/1125#issuecomment-1490076641,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXK6MPTC6PQ3PCD6YNNIDVTW6VPDBANCNFSM6AAAAAAVKOPRVI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Allow Calc to return functions from other functions

Would like to be able to do this:
def f1($a, $b) = { $a + $b }; def f2($a, $b) = { $a * $b }; def f($c) = { $c ? f1 : f2 }; f(true)(1,2)
which at the moment gives the following exception:
Exception in thread "main" java.lang.ClassCastException: class info.rlwhitcomb.calc.FunctionScope cannot be cast to class info.rlwhitcomb.calc.FunctionDeclaration (info.rlwhitcomb.calc.FunctionScope and info.rlwhitcomb.calc.FunctionDeclaration are in unnamed module of loader 'app')
at info.rlwhitcomb.calc.LValueContext.getLValue(LValueContext.java:417)
at info.rlwhitcomb.calc.CalcObjectVisitor.getLValue(CalcObjectVisitor.java:3872)
at info.rlwhitcomb.calc.CalcObjectVisitor.visitVarExpr(CalcObjectVisitor.java:1906)
...

The parse tree for the example code with the current grammar is:
(prog (stmt (defineStmt def (id f1) (formalParamList ( (formalParam $a) , (formalParam $b) )) = (stmtBlock { (stmtOrExpr (formattedExprs (exprStmt (expr (expr (var $a)) + (expr (var $b)))))) } \n))) (stmt (defineStmt def (id f2) (formalParamList ( (formalParam $a) , (formalParam $b) )) = (stmtBlock { (stmtOrExpr (formattedExprs (exprStmt (expr (expr (var $a)) * (expr (var $b)))))) } \n))) (stmt (defineStmt def (id f) (formalParamList ( (formalParam $c) )) = (stmtBlock { (stmtOrExpr (formattedExprs (exprStmt (expr (expr (var $c)) ? (expr (var (id f1))) : (expr (var (id f2))))))) } \n))) (stmt (stmtOrExpr (formattedExprs (exprStmt (expr (var (var (var (id f)) (actualParams ( (expr (value true)) ))) (actualParams ( (expr (value 1)) , (expr (value 2)) )))))))) (stmt (stmtOrExpr (emptyStmt \n))) (stmt (stmtOrExpr (emptyStmt \n))) (stmt (stmtOrExpr (emptyStmt \n))) <EOF>)

Actually, there are several problems:

LValueContext needs to call "evaluateFunction" if it sees a FunctionScope (in the example, this would be the call, already setup) to "f(true)". This is easy to fix.
Inside "evaluateFunction" we need to recognize that the reference to "f1" or "f2" is NOT a function call without parameters, but simply a function reference value that should be passed along.... THIS IS MUCH HARDER TO FIX because before we had real function parameters, this kind of "function call" without "()" was the only way to call functions, so we just did it.... Almost needs to be a mode in this one particular case NOT to do that....

So, IF we make the assumption / convention that a "function call" to a function declared with parameters at the place where we have no parameters is just a reference to the function object and not an actual call to the function, then all is well!


Sampling Fails when moving to CIFAR10

Thanks for your pytorch version of Glow.
When I am running on CIFAR10 with your code, I find that the reconstruction is generally well, but the model fails to produce reasonable sampling results.
Reconstruction:

Sampling:

Do you have any idea how to fix this issue? Thanks.

@XingangPan  Have you ever tried lower temperature (sigma) for sampling?

@chaiyujin Thanks for your suggestion, that might be a reason.
Anyway, I am moving to https://github.com/pclucas14/pytorch-glow, which works for CIFAR10.

@XingangPan  That's great. If you dig some reasons deeper, please tell me. Thanks.


update prereqs

Added OpenShift version info and how to check the WLS version/patches.

What's the current state of this PR?  Looks like both Tom and Monica approved, but then have withdrawn approval?

@mriccell Yes, there was a bit of hashing back and forth. Last I read, Monica gave a final ok, but she can confirm to be sure. Thanks.

OK, let's change "(check with docker run store/oracle/weblogic:<IP_ADDRESS> /u01/oracle/OPatch/opatch lsinventory)" to (check wl version with docker run store/oracle/weblogic:<IP_ADDRESS> sh -c 'source $ORACLE_HOME/wlserver/server/bin/setWLSEnv.sh > /dev/null 2>&1 && java weblogic.version', check wl patches with docker run store/oracle/weblogic:<IP_ADDRESS> sh -c '$ORACLE_HOME/OPatch/opatch lspatches')

@mriccell Suggested a change to use 'lspatches' instead of 'lsinventory'.   And I suggest we add a call to 'java weblogic.version' (opatch doesn't seem to have a clear way to reveal the WL version).    I've incorporatged both suggestions in the comment chain above.

Monica approved Tom's suggestions. I incorporated them.
Tom, please double-check the syntax.


Some array handling micro optimizations

any? without block will still try to iterate through array looking for non-falsey values. But we just need to check do we have nested_exposures or not.
nested_exposures_for? is introduced. It does a good think because current implementation pessimistically assumes that nested exposures exist.
!map { ... }.include?(false) is self-explaining. There's a convenient all? method.
reject { ... }.select { ... } can be done with one select or with one reject. I choosed select.
nested_value_for is extracted because of Rubocop detected offenses. Maybe it's worth to extract other condition branches to separate methods or even to separate classes (replace conditional with polymorphism refactoring)

These things improved bench/serializing.rb result only by 4 percents. I think it's possible to write a more illustrative benchmark but it's not necessary.
Anyway this patch doesn't change code too much and doesn't reduce readability too much so I think it's acceptable.

I like it, merging. Thanks.


[ie/instagram] Fix stories extraction

Closes #8290
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

can't download this type of reels/images from insta using yt-dlp...plz help
URL: https://www.instagram.com/p/DDUj6rzTIoT/

@spidy2356 that's not a video. yt-dlp doesn't download image-only posts


chore: update awsim-stable branch

Description

cherry pick

https://github.com/autowarefoundation/autoware.universe/commit/8ce9156e63ad156c71285c5d1b0fb36b9e0a42d2
https://github.com/autowarefoundation/autoware.universe/commit/61e6e08b8c55c599bcf4d60bc56a9a566a531386

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Thank you for your approval! @yukke42


Machine mac-31 went dead from monitoring website.

Machine mac-31 went dead from monitoring website.

Machine mac-31 is back online and read for service. Keys token was expired and required to run command "salt-call state.apply" to fix issue.
[E2023-05-15T14:13:24.083706-07:00 4933 0 main.go:251] Failed to generate a new token - token server error UNTRUSTED_CERTIFICATE - certificate has expired


Stats and Effort labels do not show on Character sheets

Using foundry 0.6.6 and latest ICRPG. The labels STR/DEX/etc and Basic/Weapon/Magic/etc do not render, however, they are still clickable and will roll correctly. Attached is a comparison of two character sheets (created a new one in case I did it) and a partially working NPC sheet (just has the Stats labels, but not Effort labels)

After digging a bit, it seems that when the sheet is rendered, the data-label and actual label text are simply missing:

I think should be:
STR
When I edit this HTML on the fly, the STR label pops up and the roll does not report an error about "Required field name not present in actor". I am assuming this is trying to look up the attribute via the data-label, but cannot find an attribute named "".

It is unfortunate to hear you're experiencing issues with ICRPG 1.0.1 in combination with FoundryVTT 0.6.6. I tried several clients (FoundryVTT, Microsoft Edge, Mozilla Firefox and Google Chrome) but could not reproduce the issue you're facing.
The labels get generated server-side using Handlebars.  For character sheets, this looks like this:
{{#each data.stats as |stat id|}}
...

        {{localize (concat "ICRPG." (toUpperCase id))}}

...
{{/each}}

For NPC sheets, this looks slightly different and no each was used to iterate over the stats, because of layout reasons as I wanted the stats in two columns next to each other. All six stats are simply written out in full there:
{{localize "ICRPG.STR"}}

So, it looks as if for some reason, your server-side execution is able to handle {{localize "ICRPG.STR"}} but not Handlebars subexpressions like {{localize (concat "ICRPG." (toUpperCase id))}}.
To test this a bit further, can you comment out the  element around line 43 of templates/actor/npc-sheet.html, and put some test code in, as shown below? Important to not do this "on-the-fly" in HTML as you'd be modifying client-side code, but this needs to be executed server-side, so you'll have to temporarily modify that file on disk.
    {{id}}
    {{toUpperCase id}}
    {{concat "ICRPG." (toUpperCase id)}}
    {{localize (concat "ICRPG." (toUpperCase id))}}
    {{localize "ICRPG.STR"}}
{{!--

        {{localize (concat "ICRPG." (toUpperCase id))}}

--}}

When you Ctrl+F5 in FoundryVTT, this should result in:

Note that the last one will always just be STR, because we're just looking up the localization of "ICRPG.STR" every time.
So for STR:
str  <-- the id of the stat
STR <-- the uppercase id
ICRPG.STR <-- the uppercase id prefixed (i.e. the localization key)
STR <-- this key localized in the language you're running, for English this becomes STR
STR <-- trying to look up localization for ICRPG.STR without subexpressions

Hopefully, we'll learn some more from these test results.

Thanks for the reply. I made the modifications to the character-sheet.html (not the npc-sheet), as your code snippets and screen shoots seem to be indicated the character.
Modifications are as follows:

                       {{id}}                       {{toUpperCase id}}                       {{concat "ICRPG." (toUpperCase id)}}                       {{localize (concat "ICRPG." (toUpperCase id))}}                       {{localize "ICRPG.STR"}}                       {{!--                                                 {{localize (concat "ICRPG." (toUpperCase id))}}                                              --}}
and the result definitely misses the localization keys.

Hold up. I was running this test on the standalone client 0.6.6.
I just created a new world on my hosted server with ICRPG and everything is fine...

I actually tested this locally using the Windows version of FoundryVTT 0.6.6 which worked fine. I then used a bunch of different browsers to connect to it, and these tests all passed successfully.
What OS are you running? Maybe the FoundryVTT for your OS doesn't contain the same Handlebars version and doesn't support subexpressions, although I would find that unlikely actually.
Or maybe you have an add-on enabled that comes bundled with its own (lower) version of Handlebars, that doesn't support subexpressions yet, thereby replacing the one that comes with FoundryVTT or something? Maybe try disabling all add-ons (or creating a new world without any enabled) on your local "stand-alone" FoundryVTT and see if that solves the issue.
I am glad to hear that using a hosted server seems to solve the issue for you, at least partially. I will however close this issue, since nobody else seems to have this problem currently. I'm afraid that until more information or reproducible steps are available, there's very little I can do for now.

The offending module is Combat Utility Belt (CUB) 1.2.1.  It is fully updated and while enabled, I get the issue as reported. When disabled, everything renders correctly.
https://github.com/death-save/combat-utility-belt

.< sorry for wasting your time, but thank you.

@TomCosaert My concat implementation is better... ;)
This is caused by us both adding a new concat method to the Handlebars helpers. I'll think about the best way to resolve this, but I suspect we should both namespace our concat methods to avoid this issue and future issues. I don't think it's fair to wash your hands of this issue, so I hope you'll be willing to consider what you can do to resolve it as well.

Thanks for spotting the exact issue @eclarke12!
Indeed, adding handlebars-helpers to FoundryVTT itself would be a great addition 👍 .
For the time being, I just released a new version in which I prefixed all my Handlebars helpers with icrpg- to avoid any collisions.
Glad we got to the bottom of this one!

I will do the same in CUB. Invariably other well meaning devs will implement these helpers like we did!


Switch to playwright for e2e tests

Currently e2e tests are run using Cypress. In order to keep consistent with efforts from the team like py-shinylive we should switch these e2e tests to Playwright.

#84 is a PR to do this.


[Event Change Request] table 36 "Sales Header" OnAfterCopyShipToCustomerAddressFieldsFromCustomer

Could you please add the parameter xRec (xSalesHeader: Record "Sales Header") to the event OnAfterCopyShipToCustomerAddressFieldsFromCustomer?
procedure CopyShipToCustomerAddressFieldsFromCust(var SellToCustomer: Record Customer)
var
    CustomerTempl: Record "Customer Templ.";
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCopyShipToCustomerAddressFieldsFromCustomer(Rec, SellToCustomer, IsHandled);
    if IsHandled then
        exit;

    "Ship-to Name" := SellToCustomer.Name;
    "Ship-to Name 2" := SellToCustomer."Name 2";
    if SellToCustomerIsReplaced() or
        ShipToAddressEqualsOldSellToAddress or
        (HasDifferentShipToAddress(SellToCustomer) and SellToCustomer.HasAddress())
    then begin
        "Ship-to Address" := SellToCustomer.Address;
        "Ship-to Address 2" := SellToCustomer."Address 2";
        "Ship-to City" := SellToCustomer.City;
        "Ship-to Post Code" := SellToCustomer."Post Code";
        "Ship-to County" := SellToCustomer.County;
        Validate("Ship-to Country/Region Code", SellToCustomer."Country/Region Code");
    end;
    "Ship-to Contact" := SellToCustomer.Contact;
    if not CustomerTempl.Get("Sell-to Customer Templ. Code") then begin
        "Tax Area Code" := SellToCustomer."Tax Area Code";
        "Tax Liable" := SellToCustomer."Tax Liable";
    end;
    SetCustomerLocationCode(SellToCustomer);
    "Shipping Agent Code" := SellToCustomer."Shipping Agent Code";
    "Shipping Agent Service Code" := SellToCustomer."Shipping Agent Service Code";

    //-OnAfterCopyShipToCustomerAddressFieldsFromCustomer(Rec, SellToCustomer);
    OnAfterCopyShipToCustomerAddressFieldsFromCustomer(Rec, SellToCustomer, xRec);
end;

[IntegrationEvent(false, false)]
//-local procedure OnAfterCopyShipToCustomerAddressFieldsFromCustomer(var SalesHeader: Record "Sales Header"; SellToCustomer: Record Customer) //OLD
local procedure OnAfterCopyShipToCustomerAddressFieldsFromCustomer(var SalesHeader: Record "Sales Header"; SellToCustomer: Record Customer; xSalesHeader: Record "Sales Header") //NEW
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Confusing TC error message upon too many function args

and in Pact takes two arguments. If we try supplying an arg past position two that performs any computation:
(defun test:bool (x:bool y:bool z:bool)
  (and x y (not z)))

Then we get the following TC.Failure:
Failure not4 "Unable to resolve type"
I was confused when I ran into this here: https://github.com/kadena-io/pact/issues/167
Instead of producing this typechecker error, we should instead report to the user that and was supplied an incorrect number of arguments.

Upon some quick checks, I see that we also get this error message for or, but not for +. These are the only other functions I have checked so far.
In the + case, we actually don't get any error. We should likewise report that + was supplied too many args.