TypeError: unsupported operand type(s) for +: 'int' and 'str'

After migrating to HA Core 2022.9.7 (on docker-debian) the Tuya integration cannot setup and i see this error in the log:
Logger: homeassistant.config_entries
Source: components/tuya/init.py:79
First occurred: 9:35:56 AM (1 occurrences)
Last logged: 9:35:56 AM
Error setting up entry<EMAIL_ADDRESS>for tuya
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 357, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/tuya/init.py", line 79, in async_setup_entry
response = await hass.async_add_executor_job(
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py", line 222, in connect
self.token_info = TuyaTokenInfo(response)
File "/usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py", line 41, in init
token_response.get("t", 0)
TypeError: unsupported operand type(s) for +: 'int' and 'str'
Any help?

I've got the exact same issue since this morning after a restart of the HA server.

Hello. I have exactly the same issue.
I tried creating a new tuya project. Changing my password. Disabled the integration. Etc...

Seeing the same thing, no changes to config.
Just stopped working after a scheduled restart.
Could be a server side issue?

I am just get something less janky than this. Seems like devs updated their APIs

nothing changed my end, and the app works, looks like a server end change?
Logger: homeassistant.config_entries
Source: config_entries.py:1073
First occurred: 10:07:31 am (1 occurrences)
Last logged: 10:07:31 am
Config entry 'Tuya' for tuya integration not ready yet: {'code': 2406, 'msg': 'skill id invalid', 'success': False, 't': ***********, 'tid': '*************'}; Retrying in background

I managed to solve the problem:

edit the openapi.py file in /usr/local/lib/python3.10/site-packages/tuya_iot
modify instruction in line 41-42
from:
token_response.get("t", 0)
+ result.get("expire", result.get("expire_time", 0)) * 1000
to:
token_response.get("t", 0)
+ int(result.get("expire", result.get("expire_time", 0)) * 1000)

Looks working now (need to restart the docker to read the modified file).
Comments?

inside the container image /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

My solution similar to @galtamur I changed this:
        self.expire_time = (
            token_response.get("t", 0)
            + result.get("expire", result.get("expire_time", 0)) * 1000
        )

to this:
        self.expire_time = (
            int(token_response.get("t", 0))
            + int(result.get("expire", result.get("expire_time", 0))) * 1000
        )

Dockerfile:
FROM ghcr.io/home-assistant/home-assistant:stable
COPY patch/openapi.py /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

patch/openapi.py:
"""Tuya Open API."""
from future import annotations
import hashlib
import hmac
import json
import time
from typing import Any
import requests
from .openlogging import filter_logger, logger
from .tuya_enums import AuthType
from .version import VERSION
TUYA_ERROR_CODE_TOKEN_INVALID = 1010
TO_C_CUSTOM_REFRESH_TOKEN_API = "/v1.0/iot-03/users/token/"
TO_C_SMART_HOME_REFRESH_TOKEN_API = "/v1.0/token/"
TO_C_CUSTOM_TOKEN_API = "/v1.0/iot-03/users/login"
TO_C_SMART_HOME_TOKEN_API = "/v1.0/iot-01/associated-users/actions/authorized-login"
class TuyaTokenInfo:
"""Tuya token info.
Attributes:
    access_token: Access token.
    expire_time: Valid period in seconds.
    refresh_token: Refresh token.
    uid: Tuya user ID.
    platform_url: user region platform url
"""

def __init__(self, token_response: dict[str, Any] = None):
    """Init TuyaTokenInfo."""
    result = token_response.get("result", {})

    self.expire_time = (
        int(token_response.get("t", 0))
        + int(result.get("expire", result.get("expire_time", 0))) * 1000
    )
    self.access_token = result.get("access_token", "")
    self.refresh_token = result.get("refresh_token", "")
    self.uid = result.get("uid", "")
    self.platform_url = result.get("platform_url", "")

class TuyaOpenAPI:
"""Open Api.
Typical usage example:

openapi = TuyaOpenAPI(ENDPOINT, ACCESS_ID, ACCESS_KEY)
"""

def __init__(
    self,
    endpoint: str,
    access_id: str,
    access_secret: str,
    auth_type: AuthType = AuthType.SMART_HOME,
    lang: str = "en",
) -> None:
    """Init TuyaOpenAPI."""
    self.session = requests.session()

    self.endpoint = endpoint
    self.access_id = access_id
    self.access_secret = access_secret
    self.lang = lang

    self.auth_type = auth_type
    if self.auth_type == AuthType.CUSTOM:
        self.__login_path = TO_C_CUSTOM_TOKEN_API
    else:
        self.__login_path = TO_C_SMART_HOME_TOKEN_API

    self.token_info: TuyaTokenInfo = None

    self.dev_channel: str = ""

    self.__username = ""
    self.__password = ""
    self.__country_code = ""
    self.__schema = ""

# https://developer.tuya.com/docs/iot/open-api/api-reference/singnature?id=Ka43a5mtx1gsc
def _calculate_sign(
    self,
    method: str,
    path: str,
    params: dict[str, Any] | None = None,
    body: dict[str, Any] | None = None,
) -> tuple[str, int]:

    # HTTPMethod
    str_to_sign = method
    str_to_sign += "\n"

    # Content-SHA256
    content_to_sha256 = (
        "" if body is None or len(body.keys()) == 0 else json.dumps(body)
    )

    str_to_sign += (
        hashlib.sha256(content_to_sha256.encode("utf8")).hexdigest().lower()
    )
    str_to_sign += "\n"

    # Header
    str_to_sign += "\n"

    # URL
    str_to_sign += path

    if params is not None and len(params.keys()) > 0:
        str_to_sign += "?"

        params_keys = sorted(params.keys())
        query_builder = "".join(f"{key}={params[key]}&" for key in params_keys)
        str_to_sign += query_builder[:-1]

    # Sign
    t = int(time.time() * 1000)

    message = self.access_id
    if self.token_info is not None:
        message += self.token_info.access_token
    message += str(t) + str_to_sign
    sign = (
        hmac.new(
            self.access_secret.encode("utf8"),
            msg=message.encode("utf8"),
            digestmod=hashlib.sha256,
        )
        .hexdigest()
        .upper()
    )
    return sign, t

def __refresh_access_token_if_need(self, path: str):
    if self.is_connect() is False:
        return

    if path.startswith(self.__login_path):
        return

    # should use refresh token?
    now = int(time.time() * 1000)
    expired_time = self.token_info.expire_time

    if expired_time - 60 * 1000 > now:  # 1min
        return

    self.token_info.access_token = ""

    if self.auth_type == AuthType.CUSTOM:
        response = self.post(
            TO_C_CUSTOM_REFRESH_TOKEN_API + self.token_info.refresh_token
        )
    else:
        response = self.get(
            TO_C_SMART_HOME_REFRESH_TOKEN_API + self.token_info.refresh_token
        )

    self.token_info = TuyaTokenInfo(response)

def set_dev_channel(self, dev_channel: str):
    """Set dev channel."""
    self.dev_channel = dev_channel

def connect(
    self,
    username: str = "",
    password: str = "",
    country_code: str = "",
    schema: str = "",
) -> dict[str, Any]:
    """Connect to Tuya Cloud.

    Args:
        username (str): user name in to C
        password (str): user password in to C
        country_code (str): country code in SMART_HOME
        schema (str): app schema in SMART_HOME

    Returns:
        response: connect response
    """
    self.__username = username
    self.__password = password
    self.__country_code = country_code
    self.__schema = schema

    if self.auth_type == AuthType.CUSTOM:
        response = self.post(
            TO_C_CUSTOM_TOKEN_API,
            {
                "username": username,
                "password": hashlib.sha256(password.encode("utf8"))
                .hexdigest()
                .lower(),
            },
        )
    else:
        response = self.post(
            TO_C_SMART_HOME_TOKEN_API,
            {
                "username": username,
                "password": hashlib.md5(password.encode("utf8")).hexdigest(),
                "country_code": country_code,
                "schema": schema,
            },
        )

    if not response["success"]:
        return response

    # Cache token info.
    self.token_info = TuyaTokenInfo(response)

    return response

def is_connect(self) -> bool:
    """Is connect to tuya cloud."""
    return self.token_info is not None and len(self.token_info.access_token) > 0

def __request(
    self,
    method: str,
    path: str,
    params: dict[str, Any] | None = None,
    body: dict[str, Any] | None = None,
) -> dict[str, Any]:

    self.__refresh_access_token_if_need(path)

    access_token = self.token_info.access_token if self.token_info else ""
    sign, t = self._calculate_sign(method, path, params, body)
    headers = {
        "client_id": self.access_id,
        "sign": sign,
        "sign_method": "HMAC-SHA256",
        "access_token": access_token,
        "t": str(t),
        "lang": self.lang,
    }

    if path == self.__login_path or \
        path.startswith(TO_C_CUSTOM_REFRESH_TOKEN_API) or\
        path.startswith(TO_C_SMART_HOME_REFRESH_TOKEN_API):
        headers["dev_lang"] = "python"
        headers["dev_version"] = VERSION
        headers["dev_channel"] = self.dev_channel

    logger.debug(
        f"Request: method = {method}, \
            url = {self.endpoint + path},\
            params = {params},\
            body = {filter_logger(body)},\
            t = {int(time.time()*1000)}"
    )

    response = self.session.request(
        method, self.endpoint + path, params=params, json=body, headers=headers
    )

    if response.ok is False:
        logger.error(
            f"Response error: code={response.status_code}, body={response.body}"
        )
        return None

    result = response.json()

    logger.debug(
        f"Response: {json.dumps(filter_logger(result), ensure_ascii=False, indent=2)}"
    )

    if result.get("code", -1) == TUYA_ERROR_CODE_TOKEN_INVALID:
        self.token_info = None
        self.connect(
            self.__username, self.__password, self.__country_code, self.__schema
        )

    return result

def get(self, path: str, params: dict[str, Any] | None = None) -> dict[str, Any]:
    """Http Get.

    Requests the server to return specified resources.

    Args:
        path (str): api path
        params (map): request parameter

    Returns:
        response: response body
    """
    return self.__request("GET", path, params, None)

def post(self, path: str, body: dict[str, Any] | None = None) -> dict[str, Any]:
    """Http Post.

    Requests the server to update specified resources.

    Args:
        path (str): api path
        body (map): request body

    Returns:
        response: response body
    """
    return self.__request("POST", path, None, body)

def put(self, path: str, body: dict[str, Any] | None = None) -> dict[str, Any]:
    """Http Put.

    Requires the server to perform specified operations.

    Args:
        path (str): api path
        body (map): request body

    Returns:
        response: response body
    """
    return self.__request("PUT", path, None, body)

def delete(self, path: str, params: dict[str, Any] | None = None) -> dict[str, Any]:
    """Http Delete.

    Requires the server to delete specified resources.

    Args:
        path (str): api path
        params (map): request param

    Returns:
        response: response body
    """
    return self.__request("DELETE", path, params, None)

how would i make this change in HASS OS?

inside the container image /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

I don't have such a file, what should I do?
[core-ssh ~]$ cd /usr/local/lib
[core-ssh lib]$ ls -l
total 49516
-rwxr-xr-x    1 root     root      22397664 Aug  2 16:46 libjemalloc.a
lrwxrwxrwx    1 root     root            16 Aug  2 16:46 libjemalloc.so -> libjemalloc.so.2
-rwxr-xr-x    1 root     root       5887272 Aug  2 16:46 libjemalloc.so.2
-rwxr-xr-x    1 root     root      22407794 Aug  2 16:46 libjemalloc_pic.a
drwxr-xr-x    2 root     root          4096 Aug  2 16:46 pkgconfig
[core-ssh lib]$

inside the container image /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

I don't have such a file, what should I do?
[core-ssh ~]$ cd /usr/local/lib
[core-ssh lib]$ ls -l
total 49516
-rwxr-xr-x    1 root     root      22397664 Aug  2 16:46 libjemalloc.a
lrwxrwxrwx    1 root     root            16 Aug  2 16:46 libjemalloc.so -> libjemalloc.so.2
-rwxr-xr-x    1 root     root       5887272 Aug  2 16:46 libjemalloc.so.2
-rwxr-xr-x    1 root     root      22407794 Aug  2 16:46 libjemalloc_pic.a
drwxr-xr-x    2 root     root          4096 Aug  2 16:46 pkgconfig
[core-ssh lib]$

May happen that the problem is that you should search INSIDE the docker; could be?

May happen that the problem is that you should search INSIDE the docker; could be?

tell a beginner how to do it?

May happen that the problem is that you should search INSIDE the docker; could be?

tell a beginner how to do it?

Seems like its an issue for everyone - i.e. server side
I'm going to wait a few hours and hope they fix with an update

inside the container image /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

I don't have such a file, what should I do?
[core-ssh ~]$ cd /usr/local/lib
[core-ssh lib]$ ls -l
total 49516
-rwxr-xr-x    1 root     root      22397664 Aug  2 16:46 libjemalloc.a
lrwxrwxrwx    1 root     root            16 Aug  2 16:46 libjemalloc.so -> libjemalloc.so.2
-rwxr-xr-x    1 root     root       5887272 Aug  2 16:46 libjemalloc.so.2
-rwxr-xr-x    1 root     root      22407794 Aug  2 16:46 libjemalloc_pic.a
drwxr-xr-x    2 root     root          4096 Aug  2 16:46 pkgconfig
[core-ssh lib]$

same problem

Will this be fixed in the next hass update ?
as i'm having the same issue, running it from VM

My solution similar to @galtamur I changed lines 39-42 in openapi.py from this:
        self.expire_time = (
            token_response.get("t", 0)
            + result.get("expire", result.get("expire_time", 0)) * 1000
        )

to this:
        self.expire_time = (
            int(token_response.get("t", 0))
            + int(result.get("expire", result.get("expire_time", 0))) * 1000
        )

and put a copy of the patched file in a subdirectory where my Dockerfile lives patch/openapi.py
Here is my Dockerfile:
FROM ghcr.io/home-assistant/home-assistant:stable
COPY patch/openapi.py /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

any advise how to access the python libs path in VM installation?

how would i make this change in HASS OS?

any hint?

This looks like we just might just get a HA 2022.9.8 release

May happen that the problem is that you should search INSIDE the docker; could be?

tell a beginner how to do it?

To enter the docker execute:
docker exec -it home-assistant sh

And it's allready working, without doing nothing.

Same issue using HAS OS. Not sure if this is causing any update issues later on or whether it will survive a restart but this fixed it immediately for me. Use on your own risk!

Login via SSH
Run docker exec -it homeassistant sh
Inside the docker container run:
sed -i 's/ result.get("expire", result.get("expire_time", 0))/ int(result.get("expire", result.get("expire_time", 0)))/g' /usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py

Just rebuilt my container with the latest image pull and all is now working.

Try now. It seems to have been resolved.

May happen that the problem is that you should search INSIDE the docker; could be?

tell a beginner how to do it?

Seems like its an issue for everyone - i.e. server side I'm going to wait a few hours and hope they fix with an update

Well I'm glad I waited - its fixed now :)

After migrating to HA Core 2022.9.7 (on docker-debian) the Tuya integration cannot setup and i see this error in the log:
Logger: homeassistant.config_entries
Source: components/tuya/init.py:79
First occurred: 9:35:56 AM (1 occurrences)
Last logged: 9:35:56 AM
Error setting up entry<EMAIL_ADDRESS>for tuya
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 357, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/tuya/init.py", line 79, in async_setup_entry
response = await hass.async_add_executor_job(
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py", line 222, in connect
self.token_info = TuyaTokenInfo(response)
File "/usr/local/lib/python3.10/site-packages/tuya_iot/openapi.py", line 41, in init
token_response.get("t", 0)
TypeError: unsupported operand type(s) for +: 'int' and 'str'
Any help?

Will you close the issue?

Thank you


[Bug]: Browser hang on My Account Page

Expected Behavior
it should shown user profile
Actual Behavior
Browser stuck while clicking on https://example.com/my-account and not showing any pm2 log error
Possible Solution
No response
Steps to reproduce

Create An Account
Sign In
click on my-account button (user icon)

What version of vendure integration are you using?
1.6.4
What version of Node.js are you using?
v14.19.3
What browser (and version) are you using?
Chrome
What operating system (and version) are you using?
Linux
Relevant log output
not showing any log

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I deployed vendure-1.6.4 ecommerce and storefront again on local host and configured as written in a guide https://docs.vuestorefront.io/vendure/guide/configuration.html#requirements and getting an error
[dev:*theme]  ERROR  [VSF][error]:  [GraphQL error]: Message: You are not currently authorized to perform this action, Location: [column: 3, line: 2], Path: me

Hey @ashishkpaul
Sorry for no contact, I completely missed your issue.
Can you check if you have a cookie stored in your browser after logging in?

yes sit its storing

when i refresh the page after login my-account page not showing user data

@ashishkpaul
Please check in the dev tools if thevendure-auth-token cookie is correctly set after login?

Hello sir, I am not a developer,  Vendure authOptions is
   authOptions: {         superadminCredentials: {             identifier: 'superadmin',             password: 'superadmin',         },         cookieOptions: {           secret: process.env.COOKIE_SECRET || 'cookie-secret',         },     tokenMethod: 'bearer', // authorization header method     requireVerification: false, // disable register by email verification     },

In the browser, not in the configuration

Sorry for delay sir, deployment was was stuck on localhost. I am sending the snapshop of public server

I cant really help with that. It seems that for some reason in your case, the redirect to my-account is not working even when a user is signed in.
Could you do some more debugging and share with me more details?

 Can you remove the
        <SfContentPage title="Loyalty card">
          <LoyaltyCard />
        </SfContentPage>

from MyAccount page in your project. It solved the issue in my case.

Sir, I grep and didn't find this code anywhere. Can you specify the path
and file name
On Mon, 8 Aug 2022, 14:16 Jakub Andrzejewski, @.***>
wrote:

Hey,
I managed to reproduce the error localy. Can you remove the
    <SfContentPage title="Loyalty card">
      <LoyaltyCard />
    </SfContentPage>

from MyAccount page in your project. It solved the issue in my case.
—
Reply to this email directly, view it on GitHub
https://github.com/vuestorefront-community/vendure/issues/234#issuecomment-1207840960,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4NU7YZCNQGBJGCH72TJ73VYDCM7ANCNFSM55LCXN3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

By cloning the repo
On Tue, 9 Aug 2022, 14:57 Jakub Andrzejewski, @.***>
wrote:

MyAccount.vue page file.
Have you generated the project by using vue storefront cli or have you
cloned this repository?
—
Reply to this email directly, view it on GitHub
https://github.com/vuestorefront-community/vendure/issues/234#issuecomment-1209138167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4NU76UMVGXR6BJ2DXR2ZDVYIQA5ANCNFSM55LCXN3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

You should be using the vue storefront cli or the template-vendure instead as explained in the documentation here -> https://docs.vuestorefront.io/vendure/guide/getting-started.html#how-to-start-if-you-want-to-try-out-the-integration

Sir I tried a lot through cli command but every time it's giving error "vsf
command not found " I will try again and inform you soon
On Tue, 9 Aug 2022, 15:06 Jakub Andrzejewski, @.***>
wrote:

You should be using the vue storefront cli or the template-vendure instead
as explained in the documentation here ->
https://docs.vuestorefront.io/vendure/guide/getting-started.html#how-to-start-if-you-want-to-try-out-the-integration
—
Reply to this email directly, view it on GitHub
https://github.com/vuestorefront-community/vendure/issues/234#issuecomment-1209147236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4NU72RP42B4MHZ57PLHWTVYIRARANCNFSM55LCXN3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes sir, I tried on localhost as guided the link given by you. account page not stucking through cli command (node 14, os: PRETTY_NAME="MX 19.4 patito feo") installation, thanks

Hello sir, through template-vendure myaccount page is stucking or visible by refreshing the page. product variant images are also visible after refreshing the page
https://youtu.be/ZLIOVTO1_UQ
I download the repo from given link https://docs.vuestorefront.io/vendure/guide/configuration.html#setting-up-vendure-server

through cli installation: crash on mobile, home, menu are not clickable
https://youtu.be/MHO1Gy5nw2g

Closing as cannot reproduce any of these issues.

Let me check sir
On Fri, 5 Aug 2022, 13:29 Jakub Andrzejewski, @.***>
wrote:

Hey @ashishkpaul https://github.com/ashishkpaul
Sorry for no contact, I completely missed your issue.
Can you check if you have a cookie stored in your browser after logging in?
—
Reply to this email directly, view it on GitHub
https://github.com/vuestorefront-community/vendure/issues/234#issuecomment-1206160321,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4NU72GDOJPDJUDM5M5AYDVXTCWPANCNFSM55LCXN3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

This error still persist Please read: https://github.com/vuestorefront-community/vendure/pull/185#issuecomment-1301762309


error NU1101: Unable to find package Microsoft.NET.Sdk.Functions.

I have been trying to use the C# to create the .net function . I tried many times but keep getting this issue.
I further noticed unresolved dependenciies for these class. This is weird that creating azure function via C# is such a pain.
using Microsoft.AspNetCore.Mvc;
using Microsoft.Azure.WebJobs;
using Microsoft.Azure.WebJobs.Extensions.Http;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Logging;
using Newtonsoft.Json;

I have used visual studio 2016 and visual code locally as well but no luck

I see the same thing on a brand new project:

But as soon as I do a dotnet restore, the issue goes away. In VS Code a dotnet restore will happen automatically when you debug, or the C# extension will sometimes pop up this notification to do it:

I tried that already. I think it is something to do having multiple version of .net installed on system.

What version of .net are you attempting to target - 3.1? And what is the result if your run dotnet --list-sdks?
I've got a few versions installed and it's still working
% dotnet --list-sdks
2.1.807 [/usr/local/share/dotnet/sdk]
3.1.408 [/usr/local/share/dotnet/sdk]
5.0.200 [/usr/local/share/dotnet/sdk]

C:\Users\pushp>dotnet --list-sdks
2.1.505 [C:\Program Files\dotnet\sdk]
3.1.409 [C:\Program Files\dotnet\sdk]
5.0.203 [C:\Program Files\dotnet\sdk]
On Mon, May 24, 2021 at 3:55 PM Eric Jizba @.***> wrote:

What version of .net are you attempting to target - 3.1? And what is the
result if your run dotnet --list-sdks?
I've got a few versions installed and it's still working
% dotnet --list-sdks
2.1.807 [/usr/local/share/dotnet/sdk]
3.1.408 [/usr/local/share/dotnet/sdk]
5.0.200 [/usr/local/share/dotnet/sdk]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azurefunctions/issues/2816#issuecomment-847294997,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABR5R6A22MMCCNBA5S7L2TTTPKVJ3ANCNFSM45KURSHQ
.

--
Regards,
Pushpendra

Do you see any errors when you run dotnet restore from the command line? If so, can you copy those here
Was this a clean project in an empty folder? Sometimes I've noticed issues if I ever switched the target framework in the csproj - the fix in that case is either to create a fresh new project or to delete the "bin" and "obj" folders in the existing project.

This was an empty project and tried twice but got the same error. No
issues, i have moved to Java and was able to make it work with single
attempt.
On Tue, May 25, 2021 at 2:01 PM Eric Jizba @.***> wrote:

Do you see any errors when you run dotnet restore from the command line?
If so, can you copy those here
Was this a clean project in an empty folder? Sometimes I've noticed issues
if I ever switched the target framework in the csproj - the fix in that
case is either to create a fresh new project or to delete the "bin" and
"obj" folders in the existing project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azurefunctions/issues/2816#issuecomment-848260913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABR5R6F7NKT5CYKJNYNZX7TTPQFZHANCNFSM45KURSHQ
.

--
Regards,
Pushpendra

dotnet restore didnt help though. I can walk you through the steps though if you are free to check this issue today. My understanding was that it should have worked at the first attemp like java.


TS Build error

I have added this package to my nextjs project and I have this build error

if I update line 4 to this

everything builds no problem .
So my questions:
Is this a true bug?
can I get my project to build another way?
Would this change be accepted as a pr, even thought I seem to be the only person running into this?
here is my tsconfig
{
"compilerOptions": {
"target": "es5",
"lib": [
"dom",
"dom.iterable",
"esnext",
"es2022"
],
"allowJs": true,
"skipLibCheck": true,
"strict": true,
"forceConsistentCasingInFileNames": true,
"noEmit": true,
"esModuleInterop": true,
"module": "esnext",
"moduleResolution": "node",
"resolveJsonModule": true,
"isolatedModules": true,
"jsx": "preserve",
"incremental": true,
"types": [
"cypress"
],
"baseUrl": "./src",
"paths": {
"@lib/": [
"lib/"
],
"@modules/": [
"modules/"
],
"@pages/": [
"pages/"
]
}
},
"include": [
"next-env.d.ts",
"/*.ts",
"/*.tsx",
"cypress/support/index.js",
"cypress/support/commands.js",
"cypress/integration/product.spec.js",
"cypress/plugins/index.js",
],
"exclude": [
"./node_modules/@qdrant",
"node_modules",
".next",
".nyc_output",
"cypress-coverage",
"coverage",
"jest-coverage"
]
}
and my package json
{
"name": "medusa-next",
"version": "1.0.3",
"private": true,
"author": "Kasper Fabricius Kristensen<EMAIL_ADDRESS>(https://www.medusajs.com)",
"description": "Next.js starter to be used with Medusa server",
"keywords": [
"medusa-storefront"
],
"scripts": {
"dev": "next dev -p 8000",
"build": "next build",
"start": "next start -p 8000",
"lint": "next lint",
"cypress": "cypress open",
"analyze": "ANALYZE=true next build",
"embedDocs": "tsx ./src/lib/util/ai/embeddDocs.ts"
},
"resolutions": {
"webpack": "^5",
"@types/react": "18.0.28"
},
"dependencies": {
"@headlessui/react": "^1.7.8",
"@hookform/error-message": "^2.0.0",
"@juggle/resize-observer": "^3.4.0",
"@medusajs/medusa": "^1.10.0",
"@medusajs/medusa-js": "^1.3.10",
"@meilisearch/instant-meilisearch": "^0.7.1",
"@paypal/paypal-js": "^5.0.6",
"@paypal/react-paypal-js": "^7.8.1",
"@pinecone-database/pinecone": "^1.0.0",
"@popperjs/core": "^2.11.7",
"@qdrant/js-client-rest": "^1.5.0",
"@stripe/react-stripe-js": "^1.16.5",
"@stripe/stripe-js": "^1.29.0",
"@tanstack/react-query": "^4.29.5",
"@vercel/analytics": "^1.0.2",
"@xenova/transformers": "^2.6.0",
"axios": "^1.1.3",
"clsx": "^1.2.1",
"daisyui": "^2.51.6",
"langchain": "^0.0.146",
"lodash": "^4.17.21",
"medusa-react": "^7.0.0",
"next": "^13.2.4",
"next-mdx-remote": "^4.1.0",
"nookies": "^2.5.2",
"react": "^18.2.0",
"react-confetti": "^6.1.0",
"react-cool-dimensions": "^3.0.1",
"react-country-flag": "^3.0.2",
"react-country-region-selector": "^3.6.1",
"react-dom": "^18.2.0",
"react-hook-form": "^7.30.0",
"react-hot-toast": "^2.4.0",
"react-instantsearch-hooks-web": "^6.29.0",
"react-intersection-observer": "^9.3.4",
"react-popper": "^2.3.0",
"remark-gfm": "^3.0.1",
"sharp": "^0.30.7"
},
"devDependencies": {
"@babel/core": "^7.17.5",
"@tailwindcss/typography": "^0.5.9",
"@types/node": "17.0.21",
"@types/react": "17.0.40",
"@types/react-instantsearch-dom": "^6.12.3",
"autoprefixer": "^10.4.2",
"babel-loader": "^8.2.3",
"cypress": "^9.5.2",
"eslint": "8.10.0",
"eslint-config-next": "^13.2.4",
"eslint-plugin-react-hooks": "^4.6.0",
"postcss": "^8.4.8",
"tailwindcss": "^3.0.23",
"tsx": "^3.12.8",
"typescript": "4.6.2"
}
}

Ran into the same problem today trying to build after installing @qdrant/js-client-rest.
Looks like other folks are experiencing the same issue

I need top upgrade to a later version of typescript. I was on 4.5.4 and upgraded to 5.3.3.
There were other dependencies that needed to bumped but that will be dependent on your package.json


Set is not explicitly required

When trying the examples from the README in a fresh IRB shell, it results in a NameError: uninitialized constant Dry::Initializer::Builder::Set error, because Set has not been explicitly required.
This PR adds the explicit requirement.

Thank you!


Regression test failure if dependent package is not available on PyPI

azure-storage-blob requires latest version of azure-core which is not released yet. whl installation of azure-storage-blob hence fails since azure-core is not released yet. Regression test should  handle this scenario to exit the test gracefully.

This should also be done for latest and minimum dependency test


Add publishInstance config to ApplicationConfig

What is the purpose of the change
Add publishInstance config to ApplicationConfig
Brief changelog
Add publishInstance configuration to ApplicationConfig which already exist in RegistryConfig.
Verifying this change
XXXXX

LGTM


Bug: Files app background flickers when using a GIF

Description
Whenever I use any animated(gif) background as my background in my files app, it starts flickering randomly.
Steps To Reproduce
1 - Add a gif background
2

Randomly wait for the error

Requirements
A gif background
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.4598
Log File
debug.log

Thanks for the report, I've added this to the project board.

@AffirmativeGuy thanks for the report. Support for GIFs is available as an afterthought, but it’s not the primary intended use of the feature. The feature is mainly designed for static images, but all that being said, we can try to take a further look if you can upload a screen recording of the actual issue.

oh ok thanks for your time!

@AffirmativeGuy although it's not the way we designed the feature, it wouldn't hurt to take a closer look. Do you think you can upload a screen recording?

Yeah sure

Well, that's a weird bug, whenever i record it, it just woudn't come

It looks like this limitation is here to stay. GIFs aren’t really designed to be used as app backgrounds in an endless loop, as this puts extra strain on the system. I understand this isn’t the response you were hoping for, but we believe in being transparent.


chore(deps): update common-dev-assets digest to a3a882c

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
6565341 -> a3a882c

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


Common build error

After a fresh clone always blow up this error:
[2015-10-28 13:23] D:\projects\oss\corefxlab [master ≡]
λ .\build.cmd
  Restoring build tools...
  Restoring all packages...
D:\projects\oss\corefxlab\build.proj(24,5): error MSB3073: The command ""D:\projects\oss\corefxlab\packages//dnx-coreclr-win-x86. 1.0.0-beta5-12101/\bin\dnu.cmd" restore --packages "D:\projects\oss\corefxlab\packages" --source https://www.myget.org/F/dotnet-c ore/ --source https://www.myget.org/F/dotnet-coreclr/ --source https://www.myget.org/F/dotnet-corefx/ --source https://www.myget. org/F/dotnet-corefxtestdata/ --source https://www.myget.org/F/dotnet-buildtools/ --source https://www.nuget.org/api/v2/ "D:\proje cts\oss\corefxlab\src" "D:\projects\oss\corefxlab\packages/Microsoft.DotNet.BuildTools.1.0.25-prerelease-00070/lib/"" exited with  code 1.

    0 Warning(s)
    1 Error(s)
Time Elapsed 00:00:10.48
Build Exit Code = 1

@DoCode does this still repro for you? It doesn't seem to repro for me

Closing. I have plenty of issues around build right now, but not this particular one.


Question: How to add my own css resources?

Hi!
I need to add my own css resources and the only way I found is adding directly here this piece of code:
<MyLibrary.stylesheet_links
      stylesheets={my_stylesheets()}
    />

Internally my library return something like that:
 ~H"""
    <%= for path <- @stylesheets do %>
      <link rel="stylesheet" href="..." />
    <% end %>
    """

Is there another way?
Really appreciate your help. Thanks!!

I think you should dynamically add the stylesheet from javascript.
For instance, you can do from your assets/js/storybook.js
var link = document.createElement('link');
link.setAttribute('rel', 'stylesheet');
link.setAttribute('href', 'css/my.css');
document.head.appendChild(link);

I'm already doing something like that to load googlemaps js file for my stories

The problem, this resources are provided by another elixir library. Is it possible?

I think you should dynamically add the stylesheet from javascript.
For instance, you can do from your assets/js/storybook.js
var link = document.createElement('link');
link.setAttribute('rel', 'stylesheet');
link.setAttribute('href', 'css/my.css');
window.onload = () => {
  document.head.appendChild(link);
}

I'm already doing something like that to load googlemaps js file for my stories

Thanks @cblavier, if others come across this issue looking for more specific examples I ended with adding this to assets/js/storybook.js:
window.onload = () => {
  const stylesheets =<EMAIL_ADDRESS>
  stylesheets.forEach(href => {
    const link = document.createElement('link');
    link.setAttribute('rel', 'stylesheet');
    link.setAttribute('phx-track-static', '');
    link.setAttribute('href', href);
    document.head.appendChild(link);
  });
};

It works. It's… a little odd? Certainly quite difficult to discover without coming across this specific issue 😅 Maybe an update to a guide to suggest this, or extend the lib so we can pass stylesheets into e.g. use PhoenixStorybook? But just thoughts, happy the above works.


Add set and function literals

Let sets (of type A1 -> ... -> An -> Prop) and functions be definable as constants using lookup tables, for example:
def foo : N -> N := [1N => 2N, 3N => 5N].

def bar : N -> Prop := {1N, 3N, 5N}.

Add relation variables to Sigma^1_1 formulas. They can't be quantified over, and they can't be instance variables, but they can be defined by constant tables, which are provided to the Sigma^1_1 compiler as aux data.

Done.


Incorrect aspect ratio in output of img2img.py (and similars: img2img_color.py, video2video.py and video2video_color.py)

From the demo image (dimension: 976×538, aspect ratio = 976/538 = 1.81):

python3 img2img.py --num_cols 100 --language general --mode complex --background white --output data/output.png gives:

which is a picture of dimension 1200×515 (aspect ratio = 1200/515 = 2.33, which is very different from 1.81).
The reason is this line of code: cell_height = scale * cell_width (in line 36 of img2img.py).
The factor cell_height / cell_width needs to be the same as the factor char_height / char_width, so the previous code becomes:
cell_height = (char_height / char_width) * cell_width.
Moreover, the line char_width, char_height = font.getsize(sample_character) generate a warning:
DeprecationWarning: getsize is deprecated and will be removed in Pillow 10 (2023-07-01). Use getbbox or getlength instead.
So on utils.py, all lines similar to char_width, char_height = font.getsize("◊") (with various values for ◊) needs to be replaced by:
char_bbox = font.getbbox("◊")
char_width = char_bbox[2] - char_bbox[0]
char_height = char_bbox[3]

(caution: there is no missing char_bbox[1] in the previous code. And strangely "bottom" really gives the height. See this: https://github.com/python-pillow/Pillow/issues/7802).
This correction must also be made in line 44 of img2img.py: remplace char_width, char_height = font.getsize(sample_character) with
char_bbox = font.getbbox(sample_character)
char_width = char_bbox[2] - char_bbox[0]
char_height = char_bbox[3]

So, by rearranging order of some calculus (because the calculus of cell_height needs to known the value of char_height / char_width), I suggest this correction in the code of img2img.py (extract of the code for the main function):
def main(opt):
    if opt.background == "white":
        bg_code = 255
    else:
        bg_code = 0
    char_list, font, sample_character, scale = get_data(opt.language, opt.mode)
    num_chars = len(char_list)
    num_cols = opt.num_cols
    image = cv2.imread(opt.input)
    image = cv2.cvtColor(image, cv2.COLOR_BGR2GRAY)
    height, width = image.shape
    char_bbox = font.getbbox(sample_character)
    char_width = char_bbox[2] - char_bbox[0]
    char_height = char_bbox[3]
    cell_width = width / opt.num_cols
    #cell_height = scale * cell_width
    cell_height = (char_height/char_width) * cell_width
    num_rows = int(height / cell_height)
    if num_cols > width or num_rows > height:
        print("Too many columns or rows. Use default setting")
        cell_width = 6
        #cell_height = 12
        cell_height = (char_height/char_width) * cell_width
        num_cols = int(width / cell_width)
        num_rows = int(height / cell_height)
    #char_width, char_height = font.getsize(sample_character)
    out_width = char_width * num_cols
    out_height = scale * char_height * num_rows
    out_image = Image.new("L", (out_width, out_height), bg_code)
    draw = ImageDraw.Draw(out_image)

For comparison, the old code for the same portion was:

def main(opt):
    if opt.background == "white":
        bg_code = 255
    else:
        bg_code = 0
    char_list, font, sample_character, scale = get_data(opt.language, opt.mode)
    num_chars = len(char_list)
    num_cols = opt.num_cols
    image = cv2.imread(opt.input)
    image = cv2.cvtColor(image, cv2.COLOR_BGR2GRAY)
    height, width = image.shape
    cell_width = width / opt.num_cols
    cell_height = scale * cell_width
    num_rows = int(height / cell_height)
    if num_cols > width or num_rows > height:
        print("Too many columns or rows. Use default setting")
        cell_width = 6
        cell_height = 12
        num_cols = int(width / cell_width)
        num_rows = int(height / cell_height)
    char_width, char_height = font.getsize(sample_character)
    out_width = char_width * num_cols
    out_height = scale * char_height * num_rows
    out_image = Image.new("L", (out_width, out_height), bg_code)
    draw = ImageDraw.Draw(out_image)

So, with the modified code, python3 img2img.py --num_cols 100 --language general --mode complex --background white --output data/NewOutput.png gives:

The dimension of this corrected image is 1200×648, and it's aspect ratio is 1200/648=1.85, which is near the 1.81 aspect ratio of the original image.
I will show a more visible difference, by scaling the outputted image, so it's width is the same as the inputed image, and displaying it in a graphic manipulation software, with a transparent backgroung over the inputed image:
Before the correction:

After the correction:

fix works on my end, this should be a pull request !


chore: Update node Docker tag to v23

This PR contains the following updates:

Package
Type
Update
Change

node
final
major
22-alpine -> 23-alpine

Release Notes

nodejs/node (node)
v23
Moved to doc/changelogs/CHANGELOG_V6.md#6.1.0.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 23.x releases. But if you manually upgrade to 23.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Enforcement action page

@cfarm
Alternative implementation of https://github.com/cfpb/cfgov-refresh/pull/5475.
This creates a new page type EnforcementActionPage, which stores an enforcement action's metadata at the page level.

Categories & topics are always shown, so I didn't keep the "show categories" check since I figured it was crufty (however, maybe it's useful as a reminder to set in in the configuration section?)
Also, I removed the date_filed section because that should also be set in the configuration section. (we could also have a "show date filed" reminder here if we do for categories and topics).
Other pieces of the sidebar, like "related links" are still set in the sidebar tab

Seems like plenty of other fields in our models are nullable, so I'm assuming it's fine to make these nullable as well, change reflected in latest commit.
Something that I think would be the best possible UX would be if categories, tags(listed as "topics" in the template), and date_filed were settable from the metadata pane but whose values were bound to the same underlying variables in the configuration pane. Not really sure what this would look like in code, and I wouldn't want to change the underlying AbstractFilterPage without good reason, so maybe the current regime (unique metadata fields set in the metadata tab and categories, tags, date_filed set in Configuration) is acceptable.

putting the fields that are in the new Metadata tab in Configuration is 1) technically acceptable and 2) more usable for editors

Placement of fields into tabs is arbitrary from a technical POV; any field can go anywhere (except maybe the title field, which comes from the base Page class). In terms of editor usability, I think it'd be better UX to have a separate tab instead of putting these into the Configuration tab. See also the "Wagtail fundamentals" page in Hubcap, which says:

To make it easier for users to edit specific parts of a page, the Wagtail page editing interface provides a tabbed layout that groups similar page content and settings together. For consumerfinance.gov, most pages are configured with three tabs following this general setup:

General content: the main content area of the page
-Sidebar / Footer / "Sidefoot": the secondary content area of the page, appearing as a sidebar or page footer depending on the page layout and browser width
-Configuration: settings controlling page behavior and other information that does not visually appear on the page

Some page types use an alternate set of tabs to organize content; for example, EventPages have separate tabs about an event's venue and agenda. In general, though, the last tab is always used for page configuration.

In terms of nullability,

Seems like plenty of other fields in our models are nullable, so I'm assuming it's fine to make these nullable as well

If a field is required, it should be null=False, and, if a text field, also blank=False. Were you running into a specific issue with doing this to make fields required?

If a field is required, it should be null=False, and, if a text field, also blank=False. Were you running into a specific issue with doing this to make fields required?

I believe I was getting errors around providing a default value with blank=False and null=False. AFAICT, the blank=False bit is the only part necessary to make a CharField required, but I had to set null=True in order to do not set default values for these required fields.
It's possible that this is related to some intermediate database state where I've added data without required fields and so the migration is choking on that once I try to switch it to required. Does this sound likely?

It's possible that this is related to some intermediate database state where I've added data without required fields and so the migration is choking on that once I try to switch it to required. Does this sound likely?

Yes, this happens when you first have a model state with an optional field and then make it non-optional. Since these models haven't been merged/deployed yet, a good strategy is to delete migrations from previous commits and recreate a new one.

Superseded by #5523


Javascript Error

When running inside Visual Studio, I keep getting this error
JavaScript critical error at line 13, column 33 in http://localhost:41573/App_Plugins/uSplit/backoffice/uSplitManageResource.js?cdv=943451263\n\nSCRIPT1003: Expected ':'
I have not configured a split test as of yet.

Hi @JohnBergman, that is a weird error! Do you use Browser Link by any chance? Could you disable it, and try again, just in case that is what is breaking the JS file?
I have used a shorthand object declaration, perhaps whatever tool is parsing the file does not like that.. Can you replace the file by the following code, to check if that helps?
angular.module("umbraco.resources").factory("uSplitManageResource",
    function ($http) {
        var controllerPath = "backoffice/uSplit/Manage/";
        return {
            getExperiment: function (id) {
                return $http.get(controllerPath + "GetExperimentAsync/" + id);
            },
            createExperiment: function(id) {
                return $http.get(controllerPath + "CreateExperimentAsync/" + id);
            },
            addVariation: function(experimentId, nodeId) {
                return $http.post(controllerPath + "AddVariationAsync/",
                {
                    experimentId: experimentId,
                    nodeId: nodeId
                });
            },
            deleteExperiment: function(id) {
                return $http.delete(controllerPath + "DeleteExperimentAsync/" + id);
            },
            deleteVariation: function (experimentId, variationName) {
                return $http.post(controllerPath + "DeleteVariationAsync/",
                {
                    experimentId: experimentId,
                    variationName: variationName
                });
            },
            setSegment: function (experimentId, providerKey, value) {
                return $http.post(controllerPath + "SetSegmentAsync/", {
                    experimentId: experimentId,
                    providerKey: providerKey,
                    value: value
                });
            },
            start: function (experimentId) {
                return $http.post(controllerPath + "StartExperimentAsync/" + experimentId);
            },
            stop: function (experimentId) {
                return $http.post(controllerPath + "StopExperimentAsync/" + experimentId);
            }
        }
    }
);

No change with browserlink disabled :-(

@JohnBergman I realise this was a while ago, but did you get this error in your browser or in Visual Studio?
It's possible that Visual Studio was trying to build the JS when you first run?

Browser.

@HarveyWilliams Are you getting the same error?

@ondrejpialek Nope! I'm just interested.

Ok, having spent some time thinking about this... :)
This one is caused by having a return statement on line 13 that does follows with a { on the next line. This might be ambiguous in some cases as JS does not require semicolons at the end of statements. I don't think it's ambiguous in this case, but VS is probably being overprotective.
See https://stackoverflow.com/questions/2846283/what-are-the-rules-for-javascripts-automatic-semicolon-insertion-asi
Not gonna fix myself (just moving the { at the end of the prev line should solve this), but if someone want's do submit a PR feel free :)


chainHead_storage: Backport queries for value types

This PR backports the following RPC V2 spec changes for chainHead_storage:

Add a new Storage event since the ChainHeadEvent::Done has diverged
Test serialization/deserialization for both the added events and input parameters to the method
Allow users to fetch initially the value similarly as before
Adjust testing to reflect the new API

Part of: https://github.com/paritytech/substrate/issues/14547
// @paritytech/subxt-team

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3166771


fixed python 2 specific code

This pull request addresses #989

This travis failure only happens in the ASTROPY_VERSION=development testing configuration, and it looks like it's due to a section of code that Erik wrote as some kind of workaround related to building the documentation with sphinx. Tagging @eteq in case he has an opinion about this.

Ahh, nevermind and my fault for bothering @eteq - there was an automated PR that I forgot to merge.


millis() off by factor of 8

I'm building my own (proprietary) firmware based on this repo and I'm running into an issue where the return value of millis() is a factor of 8 too high.
I must admit that I've changed so many things even minimal code to reproduce this issue wouldn't work with the current state of this repo, but I wanted to report the issue nonetheless because fixing it may help future users.
To test this, I added a line to the main loop which cycles a GPIO output on and off every 100 ms. This would be something like:
digitalWrite(MCU_GPIO9, millis() % 100 < 50);

I then connected my scope to GPIO9. I'd expect this to produce a signal that cycles between being off for 50 ms and then on for 50 ms, which would be a 10Hz signal. However, what I found was a 80Hz signal. Dividing the output from millis() by 8 seems to solve the problem but I guess there would be some underlying reason why the calculation is off.

I just noticed this problem doesn't occur anymore. I'm currently working on setting up PWM and ADC, so I'm guessing that a timer somewhere impacts the timer used by millis(). Closing because it will be difficult to reproduce.


Add 'log: true' property to methods and properties.

From<EMAIL_ADDRESS>on February 14, 2014 09:46:04
If set to true then calls to methods are logged to the console as are updates to methods.  This is better than adding console.log() messages when debugging.
Original issue: http://code.google.com/p/foam-framework/issues/detail?id=187

Do we still think this would be useful? It's easier than it used to be thanks to hierarchical postSet these days.

I think the reward:cost ratio justifies this feature.


Round trip from CSV to CSV should leave data types unaltered

I love where pandas is going. A use-case for which R's csv capabilities still win, though, is in editing a large csv file that's used as a poor-mans database.
R will keep a column of integers as integers, pandas changes some of them to floats, some to strings! I'm not sure why there's inconsistency there, but I figure I'll kick the general issue your way and I'm happy to clarify as needed.

Could you post some sample text that pandas mishandles? The best way to address this is by writing some tests.
The primary present limitation with type-handling in pandas compared with R is with NAs in integer columns. I just haven't got a great solution to that right now except to cast the column to float and use NaN.

This illustrates two situations, for example:
col1,col2
"1",3
"2",NA
First column converted to integer (turns out, R does this also), second column gets converted to floating point, NA is also not specifically listed, but would be nice to keep it.
Could you optionally keep metadata (i.e., with a read_csv(..., preserve_types=True) call) that you would use to write the file back out? I might be able to contribute to that... especially now that I realize R is breaking things too!
Cheers,
Dav

Hm, so I think to really do things correctly you're going to need to make a modified version of Python CSV parser -- right now I use Python's csv module which handles quoted strings and stuff like that-- you just get strings as the result and it's up to you to infer the types.
Secondly, I like I said I don't currently have a solution for integer columns with NAs-- things get casted to float. I'm hopeful with the addition of an NA type to NumPy that this can be improved in the future.


feat: add env vars

This PR allows setting custom environment variables inside the systemd service file.
It could be needed for specific things, like the elastic APM tracing.
i.e :
env_vars          => ["ELASTIC_APM_SERVER_URL=http://apm-server.domain:8200",
                               "ELASTIC_APM_GLOBAL_LABELS=label1=labelvalue1,label2=labelvalue2]

Generates :
 [Service]
-
+Environment=ELASTIC_APM_SERVER_URL=http://apm-server.domain:8200
+Environment=ELASTIC_APM_GLOBAL_LABELS=label1=labelvalue1,label2=labelvalue2

@syberalexis Do you have a bit of time for this ? The pipeline is failing because a stdlib dependency that is below the one required for prometheus module if I'm not wrong.
puppetlabs-stdlib, installed: 6.6.0, expected: >= 9.0.0 < 10.0.0

Hello,
It's good for me.
I will try to finish to fix the CI next week ;)
Sorry for the late answer, my life is very busy.

Awesome, thanks a lot for your time 🙏

Sorry, i forgot to release…
I try to do it this evening.


reuse python code from datadog_checks_base

This removes all code that is also in https://github.com/DataDog/integrations-core/tree/master/datadog_checks_base by simply importing what is necessary.
Motivation
Deduplication of logic: We often have to update code in both places at the same time.
depends on:
https://github.com/DataDog/integrations-core/pull/1561 :heavy_check_mark:
https://github.com/DataDog/integrations-core/pull/1562 :heavy_check_mark:
https://github.com/DataDog/integrations-core/pull/1565 :heavy_check_mark:
https://github.com/DataDog/integrations-core/pull/1566 :heavy_check_mark:

@ofek: could you explain a little more what this PR does and why ?
Thanks

@ofek about the legacy imports that I mentioned in my review: the rationale is to continue supporting the old import paths for custom checks that may still be using them, so I think we should do that for every class/function that could reasonably be imported from a custom check.
Ideally, once all the integrations-core checks use the new import paths, we'd log a deprecation warning when an old import path is used so that it's clear to users that they need to update their custom checks' code.


Cannot test react routing with enzyme tests.

This is probably not a bug, but i have already posted this on SO, and even offered a 400 point bounty, however I have gotten no luck so far :
https://stackoverflow.com/questions/62266127/cannot-navigate-to-path-using-memoryrouter-while-testing
This is why I am posting it here as well. Hopefully someone knows about this, or maybe people need to be aware of this issue.
Version
"react-router": "^5.2.0",
"react-router-dom": "^5.2.0",

Test Case

import React from 'react';
import Enzyme, {mount} from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';
import {BrowserRouter as Router, MemoryRouter, Route, Switch} from 'react-router-dom';

Enzyme.configure({adapter: new Adapter()});

describe('Routing test', () => {
    let wrapper;

    beforeEach(() => {
        wrapper = mount(
            <MemoryRouter initialEntries={["/A"]}>

This is my Test Component and should not have any test specific code in it
                        <Router>
                            <Switch>
                                <Route path={"/A"}>

A

                                </Route>
                                <Route path={"/B"}>

B

                                </Route>
                            </Switch>
                        </Router>

                </MemoryRouter>
        );
    });
    afterEach(() => {
        wrapper.unmount();
    });

    it('matches snapshot', () => {
        expect(wrapper.find(".Test")).toHaveLength(1); //this ok
        expect(wrapper.find(".A")).toHaveLength(1); //but this is not ok :( It should find  A
    });
});

Steps to reproduce

run the jest test

Expected Behavior

expect enzyme wrapper to find the element ".A".

Actual Behavior

seems to ignore all the routes

You have two routers in your tree. The inner BrowserRouter is overriding the outer MemoryRouter.

yeah but how do i get my test to pass?


Add pprof HTTP server for snapshotter

As titled. This PR is address #359

Codecov Report
Base: 29.26% // Head: 29.22% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (96a4006) compared to base (302c0c3).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head 96a4006 differs from pull request most recent head 335b169. Consider uploading reports for the commit 335b169 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #372      +/-   ##
==========================================
- Coverage   29.26%   29.22%   -0.04%
==========================================
  Files          38       38
  Lines        3810     3815       +5
==========================================
  Hits         1115     1115
- Misses       2563     2568       +5
  Partials      132      132

Impacted Files
Coverage Δ

config/config.go
19.29% <ø> (ø)

config/default.go
0.00% <ø> (ø)

config/global.go
32.14% <0.00%> (-1.20%)
:arrow_down:

pkg/daemon/daemon.go
0.00% <0.00%> (ø)

pkg/manager/daemon_adaptor.go
0.00% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Visual/color updates, and a homepage refresh

These columns probably want to be equal height? Maybe some margin on the bottom?

The hover states on the buttons in dark mode might need some love still


chore: Adjusts format CI to use docker

This was done because the swiftformat action was unable to run in lint mode, so contributors didn't know what formatting must be fixed.

It looks like the swiftformat CI stage was broken for a while, but still reported as passing (see https://github.com/GraphQLSwift/Graphiti/pull/105/checks#step:4:437). I think these are formatting violations that crept in during that time period.


Update cypress

Updating Cypress because of reasons.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@0e310a5). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #264   +/-   ##
==========================================
  Coverage           ?   59.06%
==========================================
  Files              ?      118
  Lines              ?     3591
  Branches           ?      466
==========================================
  Hits               ?     2121
  Misses             ?     1239
  Partials           ?      231

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 0e310a5...5fabfc4. Read the comment docs.

@denis-yuen coverage for each PR will be compared against the base branch (develop).  Latest develop build on Travis seems to have error'd at the starring test.


Live tests for Continuous Dtmf Detection & Send Dtmf

Add live test for Continuous Dtmf Detection & Send Dtmf

API change check
API changes are not detected in this pull request.


Question?

Is it faster?
What's the new update?

Faster in what exactly ?
New update adds 1.0.0 compatibility.


Add gitter badge and information about dev branch

@XhmikosR i've removed the so-called "stupid scheme" from my commit :)

Thanks. :)


Move ClusterConfig watch to shared informer

Description
This PR changes the way ClusterConfig is kept updated in watchConfig pkg moving to a shared informer.
Testing
This PR was tested with Unit and E2E tests.

Pull Request Test Coverage Report for Build 265305931

22 of 42 (52.38%)  changed or added relevant lines in 3 files are covered.
118 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.01%) to 51.403%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/clusterConfig/watchConfig.go
19
28
67.86%

api/config/v1alpha1/clusterConfigClient.go
2
13
15.38%

Files with Coverage Reduction
New Missed Lines
%

api/config/v1alpha1/clusterConfigClient.go
1
48.57%

pkg/clusterConfig/watchConfig.go
1
46.81%

internal/peering-request-operator/peering-request-controller.go
3
73.68%

internal/peering-request-operator/foreign-cluster.go
5
78.43%

internal/kubernetes/endpoints.go
6
72.78%

internal/liqonet/tunnel-operator.go
15
0%

pkg/liqonet/ipam.go
35
40.32%

internal/liqonet/tunnelEndpointCreator-operator.go
52
65.5%

Totals

Change from base Build 265066683:
-0.01%

Covered Lines:
6905

Relevant Lines:
13433

💛  - Coveralls

/rebase


chatRooms does not properly store IDs of multi-user chats

As expected, information on group chat rooms is stored under bot.chatRooms[Chat ID]. However, information on multi-user chats not associated with Steam groups is stored under bot.chatRooms["0"]. Presumably, this would cause problems if multiple multi-user chats were joined at once, but I haven't had a chance to check.
These multi-user chat rooms do have IDs, as confirmed by information contained within message events. The bot can send messages to these IDs and the messages work as expected. The only problem is with the ID they are stored as in bot.chatRooms.

Yet another bug caused by the switch to ProtoBuf.js. Should be trivial to fix.


Which time buckets are we tracking?

@livlab In last week's review, we decided to get finer-grained time buckets for early on (if I remember right) -- was that reporting one second ("1s" buckets) up to 10 or 20 seconds? Or longer?

Here's what I'm thinking:

5 second increments up to 60 seconds
10 second increments from 60 seconds to 120 seconds
30 second increments from 120 seconds up

This is what I expect most graphics data to look like:

So, most activity between 0 and 2 minutes (this is an estimate based on timing myself reading about 10 stories to try to come up with a number so, n = 1, beware!), and then a bump at the long tail for people who leave their tab open, go away, come back and finish reading the story.
@brianboyer please chime in.

I am certain we'll have to adjust these buckets after we see what real data looks like, but I thought starting granular will show us more detail so we can calibrate better, rather than broader buckets where we'll miss variability (that I expect) between stories.

I'm good w/ whatever y'all think is best, as long as we keep in mind that
it might be useful to hit the same marks as the normal NPR analytics.
On Mon, Feb 8, 2016 at 2:17 PM, Livia Labate<EMAIL_ADDRESS>wrote:

I am certain we'll have to adjust these buckets after we see what real
data looks like, but I thought starting granular will show us more detail
so we can calibrate better, rather than broader buckets where we'll miss
variability (that I expect) between stories.
—
Reply to this email directly or view it on GitHub
https://github.com/thecarebot/carebot-tracker/issues/31#issuecomment-181451937
.

We can record an increased granularity while still hitting NPR metrics. The current metrics I got from Tyler's code are:

10 second increments up to a minute
1 minute increments from 1-5 min
5 minute increments from 5 min on

If we code the proposal:

5 second increments up to 60 seconds
10 second increments from 60 seconds to 120 seconds
30 second increments from 120 seconds

We'll still hit NPR marks (eg 10s, 1m, 30m etc) and also have additional data with more details (1m10s).
One complication could be the number of events we log. NPR has a limit on the # that can be logged monthly, so a popular viz seen by a million people for 30 seconds would generate 6,000,000 additional events.

 How about we test for a week or
two w/ the granular numbers, see what we get, and make a ticket to
fine-tune/reduce them later, when we know better what we need?
On Mon, Feb 8, 2016 at 4:21 PM, Matt Hampel<EMAIL_ADDRESS>wrote:

We can record an increased granularity while still hitting NPR metrics.
The current metrics I got from Tyler's code are:

10 second increments up to a minute
1 minute increments from 1-5 min
5 minute increments from 5 min on

If we code the proposal:

5 second increments up to 60 seconds
10 second increments from 60 seconds to 120 seconds
30 second increments from 120 seconds

We'll still hit NPR marks (eg 10s, 1m, 30m etc) and also have additional
data with more details (1m10s).
One complication could be the number of events we log. NPR has a limit on
the # that can be logged monthly, so a popular viz seen by a million people
for 30 seconds would generate 6,000,000 additional events.
—
Reply to this email directly or view it on GitHub
https://github.com/thecarebot/carebot-tracker/issues/31#issuecomment-181552452
.


Fix missing publication_type in DrugCentral transforms

Also fixing an issue with Ensmallen installs here - it's only used during the build on Jenkins, so it is removed from the Poetry dependencies.


linbasex intensity scaling

linbasex intensity scaling is incorrect, it does not agree with the other methods, and as @DanHickstein has found appears to be dependent on the number of Legendre polynomials orders.

The required scaling factor is 1/2r

Okay, problem solved! Nice work!

I have pushed the 1/2r factor, linbasex.py line 267, and set the default smoothing to zero, in the current PyAbel PR #232.

Great, some motivation for us to merge #232 :)

linbasex transform alignment, relative to the other methods

That's annoying that there is this small shift. Can you subtract the 2D transform (say linbasex versus three-point) so that we can see if the shift is symmetric, or just in horizontal?

I am looking into the linbasex code, which, I must admit I never fully understood during the transfer process of Thomas Geber's jupyter notebook code :-(. However, now it is starting to make sense. It looks possible to switch to 1/2-image transforms, and associated basis calculations. In the process I hope to track down any subpixel offset issues. Although, my track record for this, with other methods (hansenlaw) is not good ;-)

Sounds exciting! Changing to half-image transforms sounds like a good step, and a better understanding (and comments!) of the code should help.

So, it looks like the intensity scaling was fixed in #232. @stggh, should we close this ancient issue?

So, it looks like the intensity scaling was fixed in #232. @stggh, should we close this ancient issue?

Hi @DanHickstein and @MikhailRyazanov, happy New Year. I am travelling at the moment, domestic, in South Australia until Jan 11.
Yes, it is fine to close this issue.

Hi @DanHickstein and @MikhailRyazanov, happy New Year. I am travelling at the moment, domestic, in South Australia until Jan 11.
Yes, it is fine to close this issue.

Great! Thanks for letting me know.
I hope that you are having great fun on your travels!

Great! Thanks for letting me know.
I hope that you are having great fun on your travels!


[explore]server pagination is not working

server pagination is not working, the regular pagination is working properly.
https://user-images.githubusercontent.com/67837651/118917382-9f072800-b8e5-11eb-850f-c94a2491a4a6.mov
@jinghua-qa thanks for spotting!

only happen before saving the chart. known issue, we are looking into a fix.
https://user-images.githubusercontent.com/67837651/118930961-46428a00-b8fb-11eb-99b0-8cd8e5fb2308.mov

This was fixed by #14779

Hi @junlincc. I see that this issue has been fixed with #14779, but I am still experiencing the same issue as you did, as shown in your first screen recording. I can’t seem to find any changes made to the pagination between the fix and now, so wondering if this issue is still prevalent. I tried this on the out-the-box superset and I still have the same results. Any insights are appreciated.

@villebro it's still not working in 1.3.0. Page buttons remain disfunctional until the chart is saved.

That's weird, I distinctly remember this working when reviewing #14779. @simcha90, if you have any spare bandwidth, would you be able to check if this works for you?


VirtualShield::block() needs clarification/correction

VirtualShield::block() makes a peculiar call to VirtualShield::waitFor(). If it is used correctly, then the usage should be described in a comment; otherwise it is a bug and should be fixed.
The code in question is pasted below:
int block(int id, bool blocking, size_t timeout = WAITFOR_TIMEOUT, int waitForResultId = -1);
int VirtualShield::block(int id, bool blocking, size_t timeout, int watchForResultId)
{
    return allowAutoBlocking && blocking ? waitFor(id, timeout, watchForResultId) : id;
}

int waitFor(int id, size_t timeout = WAITFOR_TIMEOUT, bool asSuccess = true, int resultId = -1);

Can you explain fruther what you find peculiar? This reads fine for me.
I think there should be paren around the blocking ternary to be explicit about order of operations.

block calls waitFor() with three parameters, which leaves the forth, resultId to be defaulted. block()'s waitForResultId is passed to the asSuccess parameter of waitFor(), while resultId is defaulted to -1

Closing issue due to inactivity


az aks pod-identity command failure

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks pod-identity list
Errors:
The command failed with an unexpected error. Here is the traceback:
cannot import name 'map_azure_error_to_cli_error' from 'azure.cli.command_modules.acs._helpers' (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\command_modules\acs\_helpers.pyc)
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 556, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/__init__.py", line 517, in load_arguments
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 313, in load_arguments
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/commands.py", line 104, in load_arguments
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
  File "importlib\__init__.py", line 127, in import_module
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "C:\Users\stalla\.azure\cliextensions\aks-preview\azext_aks_preview\custom.py", line 105, in <module>
    from ._helpers import (
  File "C:\Users\stalla\.azure\cliextensions\aks-preview\azext_aks_preview\_helpers.py", line 7, in <module>
    from azure.cli.command_modules.acs._helpers import map_azure_error_to_cli_error
ImportError: cannot import name 'map_azure_error_to_cli_error' from 'azure.cli.command_modules.acs._helpers' (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\command_modules\acs\_helpers.pyc)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks pod-identity list --help

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.32.0 *

Extensions:
aks-preview 0.5.70

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

route to CXP team

@Sri-Talla Can you please upgrade to the latest version of az cli 2.39.0


fix: Prevent id duplication in page header

Prevent duplicate ids in the hidden sizing items used in the page header.
What did you change?
Moved ID from hidden sizing items to data-original-id and added tests to ensure duplication of IDs does not happen.
How did you test and verify your work?
Test and storybook.

if i'm understanding the intent correctly, this PR removes the optional id prop from ActionBarItem, BreadcrumbItem, and Tag and puts it in the data-original-id attribute. just out of curiosity what's the problem here? i'm not an expert on these components, so i'm curious as to why we're trying to safeguard these specific components from the user error of providing duplicate id's.

if i'm understanding the intent correctly, this PR removes the optional id prop from ActionBarItem, BreadcrumbItem, and Tag and puts it in the data-original-id attribute. just out of curiosity what's the problem here? i'm not an expert on these components, so i'm curious as to why we're trying to safeguard these specific components from the user error of providing duplicate id's.

Not quite. These components monitor both the size they would like to be and the space available. To do so they clone the active elements, hide them and measure the space they would use if it were available. It is these clones that we move the 'id' to 'data-originial-id'.


Redirection based on parameters [v3.0]

I have a default view containing certain reports that are filtered by parameters.
I need to send the users to a unauthorized view based on a parameter.

ok thanks !!


chore: remove structure test

The rule should just live in the repo that provides the binaries. It has no coupling at all with the code in this repo, rather it should be coupled with the container-structure-test Go program.
I'm working with @loosebazooka to see if that might be accepted upstream, then we don't need to carry this in the rules_oci public api.

this is awesome.

We have a preliminary okay to upstream this, so I'm going to remove it before 1.0

We have a preliminary okay to upstream this, so I'm going to remove it before 1.0

sounds good. lmk when it's ready for review

@thesayyn ready for a review. We have to decide if we want to land this before we get into the upstream, or are okay with aspect-forks.

upstream PR has landed, cleaning this up now.


Notably:

Removes buttons from the ingredients list
Makes donation buttons red
Emphasizes call to action in navbar
Changes buttons to use »

Again, since I'm the only FTE on this project, I'm going to go ahead and merge myself once I fix Hound's comments and once the tests pass.


Images in Libbre office are cropped to single string

More in my pull request https://github.com/privateOmega/html-to-docx/pull/26

@NazarBashinskiy I checked out your PR and I don't think that is the solution to the problem that you are facing. I will try to test out the problem you are facing. Also I am open to other solutions, You could use ECMA-376 as reference for solutions. Thanks for the attempt and I apologize for the late reply.

@NazarBashinskiy I tried out the problem you mentioned and it seems only with LibreOffice, the particular problem is cropping up, so I don't really think its a problem that is within scope of this project or OOXML per se, hence please open an issue with LibreOffice, high chance its a problem with their implementation. So I am closing this issue.


Is my understanding correct?

Hello, my understanding of the division of the paper is that the third part is the practical application stage of adding an audio-driven portrait speech to the trained character image model, and the fourth part is to give a wild video and then train the corresponding model. May I ask if my understanding is correct? Thank you very much!

More clearly, the sec. 3 describes what is the architecture, what it consists of, and how it works, i.e., forward pass. In sec. 4, we describe how to build such a system (in sec. 3 we just illustrate what it is but not how to build this), and that is why the name of sec. 4 is Implementation Details and sec. 3 is named as Method.

Is this written for the training process of wild video or input voice program running process?

The proposed model is a person-specific method, and you should train each model for each wild target person and sec. 4. describes this process.


2nd time animation don't work well

I'm using react-native 0.57.2 and react-native-reanimated 1.0.0-alpha.9. I'm new with reanimated, so maybe I don't understand well, but I think I find a weird case. When mounting 2nd time a component with an animation, sometimes the animation don't work or start at a random place.
I reproduce using the rotation example :
import React, { Component } from 'react';
import { StyleSheet, Text, View, Alert, TouchableOpacity } from 'react-native';

import Animated, { Easing } from 'react-native-reanimated';

const {
  set,
  cond,
  startClock,
  stopClock,
  clockRunning,
  block,
  timing,
  debug,
  Value,
  Clock,
  divide,
  concat,
} = Animated;

function runTiming(clock, value, dest) {
  const state = {
    finished: new Value(0),
    position: new Value(0),
    time: new Value(0),
    frameTime: new Value(0),
  };

  const config = {
    duration: 5000,
    toValue: new Value(0),
    easing: Easing.inOut(Easing.ease),
  };

  return block([
    cond(clockRunning(clock), debug('clockRunning', clock), debug('clockNOTRunning', clock)),
    cond(clockRunning(clock), 0, [
      set(state.finished, 0),
      set(state.time, 0),
      set(state.position, value),
      set(state.frameTime, 0),
      set(config.toValue, dest),
      startClock(clock),
    ]),
    timing(clock, state, config),
    cond(state.finished, debug('stop clock', stopClock(clock))),
    state.position,
  ]);
}

class Screen1 extends Component {
  render() {
    return (
      <View
        style={[
          styles.box,
          { backgroundColor: 'blue' },
        ]}
      />
    );
  }
}

class Screen2 extends Component {
  trans = runTiming(new Clock(), 0, 360);

  render() {
    return (
      <Animated.View
        style={[
          styles.box,
          { transform: [{ rotate: concat(this.trans, 'deg') }] },
        ]}
      />
    );
  }
}

export default class Example extends Component {

  state = {
    screen: 'screen1',
  };

  handleClickScreen1 = () => {
    this.setState({screen: 'screen1'})
  };

  handleClickScreen2 = () => {
    this.setState({screen: 'screen2'})
  };

  render() {
    return (
      <View style={styles.container}>
        {this.state.screen === "screen1" ? (
          <Screen1 />
        ) : (
          <Screen2 />
        )}
        <TouchableOpacity onPress={this.handleClickScreen1} style={styles.button}><Text>SCREEN 1</Text></TouchableOpacity>
        <TouchableOpacity onPress={this.handleClickScreen2} style={styles.button}><Text>SCREEN 2</Text></TouchableOpacity>
      </View>
    );
  }
}

const BOX_SIZE = 100;

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  box: {
    width: BOX_SIZE,
    height: BOX_SIZE,
    borderColor: 'white',
    alignSelf: 'center',
    backgroundColor: 'pink',
    margin: BOX_SIZE / 2,
  },
  button: {
    paddingVertical: 6,
    paddingHorizontal: 12,
    marginVertical: 6,
  },
});

The only difference I found, is that the first debug display of the first animation clockNOTRunning 0 and for the others animations it display a clock number clockNOTRunning 988059745.5713011.
And sometimes, when there is no animation, all debug only display :
clockNOTRunning 988350127.1424431
clockRunning 988356431.1301451
stop clock 0

Ok, maybe it's iOS (12?) related, because I can reproduce the issue with react-native-reanimated 1.0.0-alpha.8 on iOS but can't reproduce on Android with 1.0.0-alpha.8 and 1.0.0-alpha.9.
But I can't reproduce with Expo 30 (using 1.0.0-alpha.6) with the expo app on iOS.

Still get the issue with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>on iOS

Hi, @Freddy03h
Thank you a ton this issue. Sorry for answering so late, but I suppose that I fixed it with https://github.com/kmagiera/react-native-reanimated/pull/121/files

Hello @osdnk, no problems !
It fix the issue indeed, thank's for your work ! I can continue to explore the library now 😄
👍


Sketch 3.7

I think you need to update the instructions. With Sketch 3.7, you need to click the circular arrow icon next to the symbol name in the inspector to apply yours screenshots/backgrounds to the rest of the template.

fixed


Readme file

#Readme file
##User Story
When I view the README for the repository,
Then I can see a professional README that provides information on the project and how to use it.
##Acceptance Criteria
The repository contains a quality README file with a description, screenshot, and link to a deployed application.

done


为什么量化后指定不了哪一块儿显卡，运行还是占用第0块儿

Is your feature request related to a problem? Please describe.

Solutions
1
Additional context
No response

try this, add them to the top of your code
import os os.environ['CUDA_VISIBLE_DEVICES'] = '1'

Is there any way to run the model on 2 gpus?

import os os.environ['CUDA_VISIBLE_DEVICES'] = '1,2'

import os os.environ['CUDA_VISIBLE_DEVICES'] = '1,2'
@zxcvbn114514

try this, add them to the top of your code
import os os.environ['CUDA_VISIBLE_DEVICES'] = '1'

Is there any way to run the model on 2 gpus?

import os os.environ['CUDA_VISIBLE_DEVICES'] = '1,2'
@zxcvbn114514

try this, add them to the top of your code
import os os.environ['CUDA_VISIBLE_DEVICES'] = '1'

Is there any way to run the model on 2 gpus?

It's not working.The model simply runs at the second gpu after I add the code.


PEXes should be useable as sys.python entries.

Currently. only the top-level 1st party code in a PEX is zip importable. None of the 3rd party dependencies embedded in the PEX can be seen by a traditional zip importer. If the PEX bootstrap code could short-circuit after activating a PEX but before execution it, this would make all PEX code available on the sys.path. Further, if the VendorImporter made the PEXed up code available via a root __pex__ psuedo-package, this would mean you could do things like use a PEX directly as an AWS Lambda function by specifying an entry point like __pex__.my.module:my_funtion in the AWS Lambda configuration. The __pex__ psuedo-package, which would be zip importable 1st party code, would unpack the PEX and install the import hook transparently.

This should remove the last known reason for folks to need to use the PEX code APIs: #747 for example.

The known bootstrap API users beyond #747:

Lambdex:

https://pypi.org/project/lambdex/
https://github.com/pantsbuild/lambdex

pyuwsgi_pex: https://github.com/kwlzn/pyuwsgi_pex


typescript-generic-sdk unused generic paramter

Describe the bug
When generating a generic SDK (without raw requests) an unused generic param is introduced. This causes typescript errors when noUnusedParameters is set to true.
The bug was introduced in https://github.com/dotansimha/graphql-code-generator/pull/7689, ideally in https://github.com/dotansimha/graphql-code-generator/pull/7689/files#diff-c0735fcd78dffef10d637a4d56bc3d1e70efa65258aa96533d0fcced83254e75R98 a check should be added that if we are not generating a raw request the additional E generic should be dropped
Your Example Website or App
https://codesandbox.io/s/nameless-sky-t833oi?file=/types.ts
Steps to Reproduce the Bug or Issue

Use latest version of typescript-generic-sdk
When generating the sdk the Requester type had an unused generic param

Expected behavior
I expect that the generated sdk does not contain unused params
Screenshots or Videos

Platform

OS: macOs
NodeJS: 16
graphql version: 16.5.0
@graphql-codegen/* version(s):

"@graphql-codegen/add": "3.2.0",
"@graphql-codegen/cli": "^2.4.0",
"@graphql-codegen/typescript": "2.7.2",
"@graphql-codegen/typescript-operations": "2.5.2",
"@graphql-codegen/typescript-generic-sdk": "2.5.0",
"graphql": "16.5.0",
"typescript": "4.7.4"

Codegen Config File
schema: schema.graphql
documents: document.graphql
generates:
  types.ts:
    config:
      avoidOptionals:
        field: true
      documentMode: string
      pureMagicComment: true
      dedupeFragments: true
    plugins:
      - typescript
      - typescript-operations
      - typescript-generic-sdk

Additional context
No response

@dotansimha @ardatan Sorry to tag you, but I'm having this problem as well, any ideas what's happening?!

Hey !
I just wrote a PR addressing this issue. Hope it can speed up the resolution 💪
Thanks for pointing out this issue 🙇
https://github.com/dotansimha/graphql-code-generator/pull/8313


fixed spelling

For some unknown reason, TRAVIS isn't finding the AWS S3 credentials (used to upload coverage analysis reports for each test in stage 1) in the environment, even though they are set up and haven't been changed since I first created them:

Initially I suspected that we hit the free tier usage limit for S3, but it appears we are well below thaqt:

Let's wait a day, and if the Travis tests still fail tomorrow, @agahkarakuzu will create a new AWS account and setup his new keys and try with that. If that fails, we'll open an issue on the Travis Github page about it.

I have heard via Twitter that the travis.com / travis.org changes are causing a lot of issues - would not be surprised if this is related given the timing

Ahhh thanks for the heads up @spinicist ! I browsed their Issues page, but could not see anything recent that would relate to us. We'll wait to see if they sort this out soon.

I think I've figured out the issue. All our other Travis test PRs and branches are passing – this is the first PR that's from an external fork. I'm wondering if Travis is looking for the AWS credentials on @nnadeau's account and isn't finding them there, so it's failing. Which is odd behaviour, because I'd expect Travis to use the environment variables of the project being merged into (since we're the ones requiring these tests).
One alternative would be to force merge this PR into a temporary branch (not master) on our repo (even though the Travis tests fails). Then, do another pull request from that branch into master, which would run the Travis tests with our credentials.

So Travis-CI got back to me on twitter: https://twitter.com/travisci/status/1027285889263779840
It appears that the environment variables I set for the AWS S3 credentials are not included when running tests on external forks into this project on purpose.
As a short-term fix, I'll change the base branch of this PR to a new one (pr254), force merge into it (even though it fails – I can do that now that I have admin privileges), and then create a new PR from that branch to master so that the tests run.
In the longer term, we'll need to look into encrypting the S3 credentials and including them in the .travis.yml file (I tried to do that when I initially was setting up AWS S3 + Travis, but was unsuccessful then).


Flamegraph

Idea
Add a flamegraph for the repository so and show on readme.

You can flamegraph the arbiter part of the bench code. I did that before.

@0xJepsen let's do this soon or just drop it. But this is getting quite stale!

i feel like it's not a priority right now


Give each redshift client their own boto session

resolves #2756
Description
Since the boto session is not thread-safe, using the default session in a multi-threaded scenario will result in concurrency errors.
This change ensures that a fresh session is instantiated before creating the client. This is similar to what is happening in the else branch. Thus, this change should not cause any unexpected issues (e.g. exceeding service quotas)
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

@jweibel22 Nice! I'd love to get this in for v0.18.1. Does this change work for you locally when you run with multiple threads?
Also, could you:

pull changes from dev/0.18.1 (which should include fixes to the failing Redshift integration tests)
add a changelog entry under v0.18.1

@jweibel22 Nice! I'd love to get this in for v0.18.1. Does this change work for you locally when you run with multiple threads?

Yes, I have verified that is does resolve the issue when I run dbt compile locally.


Question: meter off by 100, what to do?

I believe my meter is broadcasting the decimals added on to the number.  For example, 6673907 should be 66739.07.  Is there anything I could do to convert the number?
Also, huge thank you for this project, integrating my meter with home assistant was very simple thanks to to this project and rtlamr.

Ah, thank you!  ...duh


[FLINK-16433][table-api] TableEnvironmentImpl doesn't clear…

… buffered operations when it fails to translate the operation

What is the purpose of the change
TableEnvironmentImpl won't clear buffered operations if the translation throws an exception. This can cause problem for following DMLs.
Brief change log

Always clear the buffered operations.
Add test case.

Verifying this change
Added test case
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? NA

@godfreyhe Please let me know if you think the change makes sense. Thanks.

Personally, +1
If we take a look to JDBC statement, the batch interfaces have this behavior that clear batch when failed.

I think there are two kinds of failures, one is the inevitable failure (e.g. type mismatch), the other is the accidental failure (e.g. catalog may be not accessible). For the first case, if the buffer does not cleared, the TableEnvironment can not execute more queries. and this kind of failure need users to solve.  For the second case, re-executing translate  may be success, but I think the probability of this kind of failure is very small.
In general, I agree with @lirui-apache and @JingsongLi

Thanks @godfreyhe and @JingsongLi for your review. PR updated accordingly.

Since FLINK-16363 has the changes I intended to make, I just rebased and keep the test in this PR.
@JingsongLi @godfreyhe Please have another look. Thanks.

@godfreyhe I updated the java doc of TableEnvironment#execute. Please let me know if change makes sense to you. Thanks.


Add support for Ping and Pong frames for the native implementation

The web_sys interface directly mimics the web browser interface.
On the web, the User Agent is responsible for sending ping frames as needed. When building an application outside this context, we would need to manage the send of pings ourselves.
It's quite common to design protocols where the client is responsible for sending frames within a given time interval to not be considered disconnected (for example MQTT requires the client to send PINGREQ messages if it doesn't have any other data to send).
Also, when tungstenite receives ping/pong frames, those will become FromTungsteniteMessageError values, which I think is sub-optimal.

Yes, the ping/pong frames become errors, but are then ignored by the stream.
The problem with adding Ping/Pong variants to the Message enum would be that the user of this crate would need to have platform-dependent code when handling Messages (e.g. when using match). We could add Ping/Pong variants regardless of platform and document that on wasm they will never be received and sending them has no effect.

We could add Ping/Pong variants regardless of platform and document that on wasm they will never be received and sending them has no effect.

Yes that's definitely an option, but I think it's a rather fragile one. Instead of getting a compilation error because the feature is not supported, you suddenly start having silent protocol breakage in term of random disconnects because no data is being sent.

I believe using *Ext for an extension trait is perfectly fine. I've seen this convention multiple times e.g. in tracing-subscriber (SubscriberExt) and tower-http (ServiceBuilderExt). In the worst case (i.e. name collisions), you can use use *Ext as _.
The method could be renamed to into_websocket() (as it's self into another type), but in that case, I'd also suggest renaming UpgradedRequestBuilder to the more specific WebsocketRequestBuilder.
Either solution works well, especially considering that Request already has special handling for Wasm. Instead of silently ignoring Ping/Pong in Message, you could add a platform-gated #[deprecated] attribute to provide a warning.

Ping, Pong and Close frames were added.


1.2.3 publishing to pub.dev

Hello.
First of all wanted to say thank you for your work and contribution into Flutter open source projects - you rock.
Could you please publish 1.2.3 verison to pub.dev as 1.2.2 blocks us from upgrating project packages.
Many thanks

@Ahmadre gentle reminder regarding this. Thanks in advance.

Before publishing to pub.dev, please update the wakelock (and any other dependencies) to the latest

When is this being published? My app build broke today.

@brianegan I think we definitely need a new release. Even pointing the library to master doesn't look like it's gonna cut it.
@Ahmadre any plans for a new release for this issue, since lots of folks are waiting patiently for one? Thanks in advance.

Amy update on this?

I need an update as well

@Ahmadre just gently reminding you regarding this. Thanks in advance.

Is this project maintained anymore ? A lot of dependency conflicts are here

@WatchDogsDev I hear your frustration. As of today, I am now responsible for publishing new versions on pub.dev. Also, the project has been transferred to Flutter Community, which ensures it's long term commitment to this project.
One more thing, I'll publish a new build tonight.

Version 1.3.0 has been published to pub.dev. Looks like updates are back on the menu, folks, courtesy of yours truly. Thank you for your patience.


additional url for douban fm

direct connect to douban fm audio source

这是一封自动回复邮件。已经收到您的来信，我会尽快回复。如有急事，请致电本人，谢谢！Thank you for your email! Please do not reply to this message, as this is an automated response. We will respond as soon as we can!


added RegExp comparison so you can provide RegExp in post request spec

I really need this feature that allows you to give a request spec as a RegExp (actually, only by string)
So you can write cool stuff like:
var scope = nock('http://www.google.com')
    .post('/echo', 'key=v.?l')
    .reply(200, function(uri, body) {
        return 'OK !';
    });

And be able to match requests like POST http://www.google.com/path key=valor key=vul, or even key=vlif you want.
If the provided pattern is actually not a valid RegExp, then nock considers it as a basic string.

Yes, you're right.
This would break such string.
You shall decline my PR.
I'll make another one with real regexp.
On Wed, Dec 31, 2014 at 4:08 PM, Pedro Teixeira<EMAIL_ADDRESS>wrote:

@rehia https://github.com/rehia regular expressions have a lot of
special characters like "[", "]", "{", "}", that users may want to use for
literal matching. Wouldn't this break using your changes?
I'm all for allowing regular expressions, as long as they are intended
regular expressions like:
var scope = nock('http://www.google.com')
.post('/echo', /key=v.?l/)
.reply(200, function(uri, body) {
return 'OK !';
});
Wouldn't you agree?
—
Reply to this email directly or view it on GitHub
https://github.com/pgte/nock/pull/259#issuecomment-68446904.

I finally just updated the PR
Take a look at it and tell me.
Here's the example
var scope = nock('http://www.google.com')
.post('/echo', /key=v.?l/g)
.reply(200, function(uri, body) {
return 'OK !';
});

landed on v0.53.0.
@rehia thanks for the contribution!

You're welcome ;)
Thanks for releasing it so quickly !