Allow multiple levels of custom root models

This relates to #911 which has a fix, but that doesn't work for models with custom roots which nest models with custom roots.
class Level2(BaseModel):
    __root__: str

class Level1(BaseModel):
    __root__: Dict[str, Level2]

class Level0(BaseModel):
    __root__: Dict[str, Level1]

Note that I am new to pydantic, so let me know if the above is not something anyone should be doing.

This still seems to be an issue, and from what I can tell, this PR is the path of least resistance for fixing the issue.
While, it may seem strange to have to have a seemingly magical if "__root__" in response_content:, it's directly related to a longstanding issue with Pydantic's .dict() behavior that won't be fixed until Pydantic v2:

dict() behaviour will change in v2 to default to returning the root object, but that's backwards incompatible so can't happen now. It's also not a bug.

The fundamental issue seems to be that Pydantic's .dict() -> pydantic.parse_* does not round-trip correctly: .dict() wraps the result inside {"__root__": ...} but pydantic.parse_* does not accept such wrapping.
Oddly enough, .json() -> pydantic.parse_raw_as(...) does round-trip correctly, unlike .dict() -> pydantic.parse_obj_as(...); and unfortunately this .dict() asymmetry impacts FastAPI.
I realize that it's generally sub-optimal to design APIs around reliance of __root__ containers, but it's often the case that it's not an option to change existing API contracts, so there is a valid use case for this fix.
Apparently the .dict() behavior will be "fixed" in Pydantic v2 (as mentioned above) at which point this may become a non-issue, but there's the question of what to do in the meantime. From what I can tell, FastAPI works almost flawlessly with __root__ except for the quirky wrapping that Pydantic does with .dict(), so a small bandaid could go a long ways.
FWIW, here's a minimum-viable example that demonstrates the issue:
class Item(pydantic.BaseModel):
    name: str

class ItemMap(pydantic.BaseModel):
    __root__: dict[str, Item]

class Container(pydantic.BaseModel):
    __root__: dict[str, ItemMap]

sample_obj = Container(
    __root__={
        'group1': ItemMap(
            __root__={
                'id1': {'name': 'Item 1'},
                'id2': {'name': 'Item 2'},
            }
        ),
        'group2': ItemMap(
            __root__={
                'id3': {'name': 'Item 3'},
            }
        ),
    }
)

@app.get('/index', response_model=Container)
async def handle_index() -> Container:
    return sample_obj

Error message:
2 validation errors for Container
response -> __root__ -> __root__ -> __root__ -> group1 -> name
  field required (type=value_error.missing)
response -> __root__ -> __root__ -> __root__ -> group2 -> name
  field required (type=value_error.missing)

This PR seems to fix the issue, so it would be great if this could be finalized/merged/released.
In the meantime, this may be a viable workaround (at least in some cases) - manually apply .dict() and unpack __root__ before returning dict[str, Any]:
@app.get('/index', response_model=Container)
async def _handle_index() -> dict[str, Any]:
    return sample_obj.dict()['__root__']  # type: ignore

Note that the schema still shows up correctly thanks for response_model=Container, despite the -> dict[str, Any] type annotation.
The full example code, along with test cases that demonstrate the underlying Pydantic .dict() behavior issue is attached below.

(Click to expand)
import fastapi
import fastapi.testclient
import http
import json
import pydantic
import pytest
import textwrap
from typing import Any

class Item(pydantic.BaseModel):
    name: str

class ItemMap(pydantic.BaseModel):
    __root__: dict[str, Item]

class Container(pydantic.BaseModel):
    __root__: dict[str, ItemMap]

sample_obj = Container(
    __root__={
        'group1': ItemMap(
            __root__={
                'id1': {'name': 'Item 1'},
                'id2': {'name': 'Item 2'},
            }
        ),
        'group2': ItemMap(
            __root__={
                'id3': {'name': 'Item 3'},
            }
        ),
    }
)

def test_pydantic__serialization_quirks() -> None:
    rootless_dict = {
        'group1': {
            'id1': {'name': 'Item 1'},
            'id2': {'name': 'Item 2'},
        },
        'group2': {
            'id3': {'name': 'Item 3'},
        },
    }
    rootless_json = json.dumps(rootless_dict)
    rooted_dict = {'__root__': rootless_dict}
    rooted_json = json.dumps(rooted_dict)

    # Serialization quirks - `.dict()` emits `__root__` but `.json()` doesn't:
    assert sample_obj.json() == rootless_json  # (without __root__)
    assert sample_obj.dict() == rooted_dict  # (*with* __root__)

    # Parsing quirks - neither `parse_raw_as` nor `parse_obj_as` expect `__root__`.
    assert pydantic.parse_raw_as(Container, rootless_json) == sample_obj
    assert pydantic.parse_obj_as(Container, rootless_dict) == sample_obj
    with pytest.raises(pydantic.ValidationError):
        assert pydantic.parse_raw_as(Container, rooted_json)
    with pytest.raises(pydantic.ValidationError):
        assert pydantic.parse_obj_as(Container, rooted_dict)

    # In other words, dump->parse round-trips correctly for `.json()` but *not* `.dict()`:
    assert pydantic.parse_raw_as(Container, sample_obj.json()) == sample_obj
    with pytest.raises(pydantic.ValidationError):
        assert pydantic.parse_obj_as(Container, sample_obj.dict()) == sample_obj

    # Workaround:
    assert pydantic.parse_obj_as(Container, sample_obj.dict()['__root__']) == sample_obj

def test__fastapi__validation_error() -> None:
    app = fastapi.FastAPI()

    @app.get('/index', response_model=Container)
    async def handle_index() -> Container:
        return sample_obj

    testclient = fastapi.testclient.TestClient(app)
    with pytest.raises(pydantic.ValidationError) as excinfo:
        testclient.get('/index')

    assert (
        str(excinfo.value)
        == textwrap.dedent(
            '''
            2 validation errors for Container
            response -> __root__ -> __root__ -> __root__ -> group1 -> name
              field required (type=value_error.missing)
            response -> __root__ -> __root__ -> __root__ -> group2 -> name
              field required (type=value_error.missing)
            '''
        ).strip()
    )

def test__fastapi__workaround() -> None:
    app = fastapi.FastAPI()

    @app.get('/index', response_model=Container)
    async def _handle_index() -> dict[str, Any]:
        return sample_obj.dict()['__root__']  # type: ignore

    testclient = fastapi.testclient.TestClient(app)
    response = testclient.get('/index')
    assert response.json() == json.loads(sample_obj.json())
    assert response.status_code == http.HTTPStatus.OK

Setup:
virtualenv venv
. venv/bin/activate
pip install fastapi mypy pytest requests types-requests
mypy --strict test_example.py && pytest test_example.py

Thanks! The recommended approach for dealing with types that would go in root models in Pydantic is to use the type annotations directly in FastAPI, as each parameter is not a model but a model field, we can have more flexibility. So, instead of `
class Level1(BaseModel):
    __root__: Dict[str, Level2]

You can use:
Dict[str, Level2]

Also, have in mind that some other PRs related to this were probably merged, so the original problem might be solved. And also with Pydatnic v2 you could use TypeAdapter, that would probably be much better than the root model.
Although if you have another use case, please create a Discussion with a minimal self contained example that I can copy paste to understand your use case better. :nerd_face:
For now, I'll close this one, but thanks for the effort! :cake:


Crash

Hi~
Sadly, no more information than this, but when it happens, Haruna is not working anymore.

This is the updated jar based from the latest commit. Please check and see if the issue still pops up in this commit.
https://amanogawa.moe/cdn/haruna-3.2.0-beta.jar

Seems fixed, thanks again!


Add hftools python package

Add hftools python package used in the BSM search demo example. https://github.com/reanahub/reana-demo-bsm-search/issues/1

Not necessary here anymore, since that example shows how to extend upstream environments and publish one's own images.


Match arms with Self::Foo(something) are not resolved

When an enum variant has some data in it and matched with Self:: prefix, rust-analyzer does not properly infer the corresponding match arm and does not allow such things as "go to definition":

pub(crate) enum TestEnum {
    A,
    Unresolved(i32),
}

impl std::fmt::Display for TestEnum {
    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
        let _resolved = Self::Unresolved(2);
        let _resolved_too = TestEnum::Unresolved(2);

        let _take_one = match self {
            Self::A => write!(f, "A"),
            // unresolved
            Self::Unresolved(_) => write!(f, "unresolved: Try go to definition on this match arm"),
        };

        let take_two = match self {
            TestEnum::A => write!(f, "A"),
            TestEnum::Unresolved(_) => write!(f, "resolved"),
        };

        take_two
    }
}

I think this might be a dupe, but I can't find the issue I'm thinking of.

https://github.com/rust-analyzer/rust-analyzer/issues/6549

Looks very related, although in my case some of the Self:: variants are actually resolved.

Still happens on rust-analyzer version: nightly (36465b3) even after https://github.com/rust-analyzer/rust-analyzer/issues/6549 is fixed.


find the correct value from nssPrivate

In my key4.db, the table nssPrivate has some rows where a11 == NULL, thus the tool crashes. I add a check to find the correct row.

Great contribution, thanks!


Fixed minor typo in zappa/cli.py

Great thanks to all the authors and contributors for this awesome project!
I found a typo in an error message while using zappa with my messy environment,
and here's the fix 😉

Coverage remained the same at 79.988% when pulling 725e7692fe0bcde859ff4b86d9159129a5598a35 on cyhsutw:cyhsutw/fix-minor-typo into 03ab19b588993e1a552e4acb6996c43f8a7d3b8c on Miserlou:dev.

👍


RDKTV-24799: WPEFramework crash with signature RdkShell::systemRam

Reason for change: ensure closing file properly if memory extraction fails
Test Procedure: TBD
Risks: None
Priority: P1
signed-off-by: Ezhilarasi Velumani<EMAIL_ADDRESS>

https://jenkins.code.rdkcentral.com/job/github-triggered/37950/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/5214/ started

https://jenkins.code.rdkcentral.com/job/build-component/75704/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/8341/ started.

Sanity tests for ['RPI3 Hybrid/MC'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/19138/

'['RPI3 Hybrid/MC']' Sanity test FAILURE, investigation pending.
Build Jobs: ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell']
Flash MC [FAILURE]
Flash HYB [FAILURE]
MC - Video Test skipped [FAILURE]
HYB - Video Test skipped [FAILURE]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-rdkv-raspberrypi-flow/4618/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/19143/

https://jenkins.code.rdkcentral.com/job/github-triggered/38218/ started

https://jenkins.code.rdkcentral.com/job/build-component/76007/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/8655/ started.

Sanity tests for ['RPI3 Hybrid/MC'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/19660/

'['RPI3 Hybrid/MC']' Sanity test FAILURE, investigation pending.
Build Jobs: ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell']
Flash MC [FAILURE]
Flash HYB [FAILURE]
MC - Video Test skipped [FAILURE]
HYB - Video Test skipped [FAILURE]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-rdkv-raspberrypi-flow/4748/

'['BCM Reference Refapp2']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-brcm-refboard/5446
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp Movie Session Mgr VoD Test [FAILURE]
RefApp Movie Firebolt MP Encrypted VoD Test [FAILURE]
RefApp Channel Change Video Tests [FAILURE]
RefApp Lightning Bouncing Ball App Launch and Exit Test [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/4007/


Rejected connection in ETCD logs from localhost every 10 seconds

Hi,
I've recently been testing out a Kubernetes Cluster deployment with ETCD v3.3.0, and noticed the following messages in the logs:
2018-02-06 12:41:06.905234 I | embed: rejected connection from "<IP_ADDRESS>:35574" (error "EOF", ServerName "")
2018-02-06 12:41:07.211189 I | embed: rejected connection from "<IP_ADDRESS>:35578" (error "EOF", ServerName "")
2018-02-06 12:41:16.905274 I | embed: rejected connection from "<IP_ADDRESS>:35602" (error "EOF", ServerName "")
2018-02-06 12:41:17.211320 I | embed: rejected connection from "<IP_ADDRESS>:35606" (error "EOF", ServerName "")

There are two of these log lines generated every 10 seconds. The cluster itself is operating without any issues, I can create / delete resources and I haven't noticed/experienced any problems so far. Just curious if anyone has an idea what may be making the requests or if it's even anything of concern?
Additional notes:

I haven't managed to recreate the issue with ETCD v3.2.15.
There are no additional deployments in the cluster, aside from what kops may create on a standard install

Versions:
ETCD Version: v3.3.0
Kubernetes Version: v1.8.7
Kops Version: master + PR
CoreOS Version: v1632.2.1

Hi @KashifSaadat I assume you are using TLS? Can we see your full etcd startup flags?

I haven't managed to recreate the issue with ETCD v3.2.15.

So are you saying you can recreate the issue with v3.3.0? Can you provide full steps?

Hi @hexfusion, apologies forgot to include that info! ETCD is started up with the following env vars (pulled from one of the hosts):
ETCD_ADVERTISE_CLIENT_URLS='https://etcd-a2.internal.<KOPS-CLUSTER-NAME>:4001'
ETCD_CERT_FILE='/srv/kubernetes/etcd.pem'
ETCD_DATA_DIR='/var/etcd/data'
ETCD_INITIAL_ADVERTISE_PEER_URLS='https://etcd-a2.internal.<KOPS-CLUSTER-NAME>:2380'
ETCD_INITIAL_CLUSTER='etcd-a1=https://etcd-a1.internal.<KOPS-CLUSTER-NAME>:2380,etcd-a2=https://etcd-a2.internal.<KOPS-CLUSTER-NAME>:2380,etcd-b1=https://etcd-b1.internal.<KOPS-CLUSTER-NAME>:2380,etcd-b2=https://etcd-b2.internal.<KOPS-CLUSTER-NAME>:2380,etcd-c1=https://etcd-c1.internal.<KOPS-CLUSTER-NAME>:2380'
ETCD_INITIAL_CLUSTER_STATE='new'
ETCD_INITIAL_CLUSTER_TOKEN='etcd-cluster-token-etcd'
ETCD_KEY_FILE='/srv/kubernetes/etcd-key.pem'
ETCD_LISTEN_CLIENT_URLS='https://<IP_ADDRESS>:4001'
ETCD_LISTEN_PEER_URLS='https://<IP_ADDRESS>:2380'
ETCD_NAME='etcd-a2'
ETCD_PEER_CERT_FILE='/srv/kubernetes/etcd.pem'
ETCD_PEER_KEY_FILE='/srv/kubernetes/etcd-key.pem'
ETCD_PEER_TRUSTED_CA_FILE='/srv/kubernetes/ca.crt'
ETCD_TRUSTED_CA_FILE='/srv/kubernetes/ca.crt'

I've attached an example Kops ClusterSpec you can use for testing:
example-clusterSpec.yaml
^ Will need some tweaking such as setting the kops state bucket, cluster name, tightening down Kube API & SSH Access, etc.. General guide on this here: https://github.com/kubernetes/kops/blob/master/docs/aws.md#creating-your-first-cluster
As mentioned in the initial post I've built kops from source, to make use of particular contributions. A guide on building kops from source is here: https://github.com/kubernetes/kops/blob/master/docs/development/building.md
In particular, you would need to build new versions of kops, nodeup & protokube. This can be done by running similar to the following:
go get k8s.io/kops
cd go/src/k8s.io/kops
git remote add appvia git@github.com:appvia/kops.git
git checkout appvia/bootstrapscript-etcdClusterSpec
make upload S3_BUCKET=s3://<KOPS-S3-BUCKET>

Then to build a cluster using kops (make sure you use the kops binary that is built in the above steps, located in go/src/k8s.io/kops/.build/upload/kops/1.8.0/):
export NODEUP_URL=https://s3.<REGION>.amazonaws.com/<KOPS-S3-BUCKET>/<PATH-TO-NODEUP>
export PROTOKUBE_IMAGE=https://s3.<REGION>.amazonaws.com/<KOPS-S3-BUCKET>/<PATH-TO-PROTOKUBE>
kops create -f clusterSpec.yaml # based off the attached file with your amendments
kops create secret --name <KOPS-CLUSTER-NAME> sshpublickey admin -i ~/.ssh/id_rsa.pub
kops update cluster <KOPS-CLUSTER-NAME> --yes

Once the cluster has started, you'll be able to ssh into one of the master instances using the default user (core for the CoreOS AMI I've used in the attached ClusterSpec), and the etcd logs are located at:

/var/log/etcd.log
/var/log/etcd-events.log

@KashifSaadat great details thanks for that.

There are two of these log lines generated every 10 seconds.

I wonder if this is some kind of health check failing to connect? Also can you provide more logging?

Actually, the 10 seconds could be TLSHandshakeTimeout: 10 * time.Second. We will want probably logs for all peers. You also should verify your certs. It seems that it perhaps should also include <IP_ADDRESS> in your SAN?
openssl x509 -in $cert_name.pem -text -noout

Probably there are other client requests coming with wrong certs, thus being closed.
Still the error message is not descriptive, which seems addressed in https://go-review.googlesource.com/c/go/+/86715/7/src/crypto/tls/tls.go.

I ran curl http://<IP_ADDRESS>:8080/healthz on a master node. On both, I get a HTTP 200 OK response and the response content ok is returned. By making this curl request, ETCD v3.3.0 returns the logs:

@xiang90 Does api server probes ping etcd?

Been doing a little more debugging, it appears to be this call here:

https://github.com/kubernetes/kubernetes/blob/v1.8.7/cmd/kube-apiserver/app/server.go#L278
https://github.com/kubernetes/apiserver/blob/kubernetes-1.8.7/pkg/storage/etcd3/preflight/checks.go#L44

My kops master nodes start kube-apiserver up with the flag --etcd-servers=https://<IP_ADDRESS>:4001. Trawling through the code, the request ends up as my below example:
import (
	"fmt"
	"net"
	"time"
)

func main() {
	conn, err := net.DialTimeout("tcp", "<IP_ADDRESS>:4001", 1*time.Second)
	if err != nil {
		fmt.Printf("failed, %v", err)
	} else {
		defer conn.Close()
		fmt.Printf("successful\n") // I return successfully here, no errors.
	}
}

I can execute that to replicate the behaviour and logs in etcd exactly, where the above code gets a successful response however etcd reports the rejected connection.

I run etcd 3.3.1  have the same problem on log : etcd: rejected connection from "localIP:54124" (error "EOF", ServerName "")

I've noticed that this happens when you hit the "/healthz" endpoint on the kubernetes API Server for some reason. It doesn't seem to be an issue but when you're trying to debug something it wastes a few hours of your time ha

Solved.
I replaced the server certificate with the peer certificate. Although it seems unreasonable.
#9785

I can confirm that the errors occur on kubernetes v1.10.3 with etcd v3.3.5. The error appears when kubelet calls apiserver's healthz endpoing like what @KashifSaadat said. Manually calling curl -k https://localhost:6443/healthz triggers this as well.
Does anyone know why this is happening?

We see the same log entries here with Kubernetes 1.10.4 and etcdv3.3.7.

I'm still seeing this with Kubernetes 1.10.5 and etcd v3.3.8.

See kubernetes/kubernetes#63316 and kubernetes/kubernetes#64909.
It looks like the PR kubernetes/kubernetes#65027 "Use actual etcd client for /healthz/etcd checks" will replace apiserver's TCP dial with an actual etcd client trying to list etcd members, so I guess this will be resolved in Kubernetes v1.12.

Thank you for this issue. I've been tolling for two days to understand why kubectl exec fails on my 1.10 deployment (works on 11, 12, 13..). Kept seeing the EOF errors regarding health checks. Really bad when an AWS ALB is fronting your cluster, hitting the health checks every few seconds. If this is a false positive, it's a doozy! Put me on a deep-dive this morning that sounds like I can ignore. Back to the other issue :)

I also see this with Kubernetes 1.11.1 and etcd 3.3.9.
Is there any known workaround ?

No worries @akutz, glad it helped!
@n0made1 the above Kubernetes PR was released and available in v1.12.0 (changelog), I've not yet got around to testing it.

Thanks but I can't manage to upgrade to 1.12, so I was wondering if there
would any workaround for 1.11.
Le jeu. 4 oct. 2018 à 17:15, Kashif Saadat<EMAIL_ADDRESS>a
écrit :

No worries @akutz https://github.com/akutz, glad it helped!
@n0made1 https://github.com/n0made1 the above Kubernetes PR was
released and available in v1.12.0
https://github.com/kubernetes/kubernetes/releases/tag/v1.12.0 (changelog
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md#other-notable-changes-6),
I've not yet got around to testing it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etcd-io/etcd/issues/9285#issuecomment-427056845, or mute
the thread
https://github.com/notifications/unsubscribe-auth/App015R6mBiASOOmqdEdo1bNrCkdlErSks5uhiYOgaJpZM4R7Ele
.

Just talked to the author @liggitt  of the fix mentioned, as we need to balance between the severity of the issue vs. the risk of back porting, we are not planning to back port it k8s 1.10 and 1.11. If you have a strong use case that really need the back port in k8s, please open an issue in kubernetes, so we could have more experts evaluating it. Otherwise I am closing this issue since it's not an etcd issue.


AWS p4de.24xlarge instance type support

Description
What problem are you trying to solve?
The p4d instance type is listed at https://karpenter.sh/docs/reference/instance-types/#p4d-family but p4de is missing
note p4d != p4de.
However the specs of p4de were added 1 year ago https://github.com/aws/karpenter-provider-aws/blob/6934ef58e8e13686d4f57c2d336dd165cbf3e759/pkg/providers/pricing/zz_generated.pricing_aws.go#L246
How important is this feature to you?
Karpenter is currently not scheduling our p4de.24xlarge pods so perhaps is not supported yet?

It looks like the p4de.24xlarge is still in preview, have you requested access? Are you running in one of the supported regions (us-east-1 or us-west-2)? As long as those are true it should be supported. If not could you attach logs and relevant objects (pods, nodeclass, nodepool, etc)?

Yes, p4de.24xlarge is still in preview, we got access and we have are able to spin them up in our region via EC2 and also via EKS (without Karpenter). The problem arises with Karpenter. Let me check if we can bring the logs.

I think this problem is actually more general, we just need to support preview instance types. There's an issue that's tracking this here: #3585. Do you mind +1-ing that issue. We should think about raising that issue in priority to unblock for cases like this.

Closing this as duplicate of #3585 to track it there as the overarching issue


Proposal for new category to track 'Mobile Apps'

It will be good to track if a site has Mobile apps. For example, I would like to see how many eCommerce sites also have mobile apps.
We can track this using META tags and few other signals. Example - https://www.levi.com/GB/en_GB/
<meta data-vue-meta="1" name="apple-itunes-app" content="app-id=1481624020">
<meta data-vue-meta="1" name="google-play-app" content="app-id=com.levistrauss.customer">

We need to check for META tag with name 'apple-itunes-app' for iOS app and with name 'google-play-app' for Android app.
@AliasIO - What do you think?

How would this appear in the extension, something like this?

Mobile apps
iOS
Android

I think it might be confusing to mention that there is an app without linking to it.

Hmm... Didn't think about that..
@AliasIO
For Android apps, links are constructed like this (where 'com.levistrauss.customer' is app id from relevant META tag) -
https://play.google.com/store/apps/details?id=com.levistrauss.customer
For iOS app, URLs have company name and app id both. Example -<PHONE_NUMBER> is app ID from relevant META tag)
https://apps.apple.com/us/app/levis-shop-denim-more/id1481624020
But looks like company name is irrelevant so if you change URL to following, it will still work.
https://apps.apple.com/us/app/XXX/id1481624020
Now, I am not sure how to construct 'website' link in technologies.json using regex pattern from other attributes... Is there any way to do this?

It would have to link to the wappalyzer.com like the other technologies, where there would be a page listing websites using 'iOS' or 'Android'. It's a little weird as they're not actually technologies used by the websites. It's an interesting idea but I don't think it fits.

@AliasIO  - We can also look at this in more generic way for META TAG as technology and see what type of META Tags a site is using. For example, BuiltWith tracks usage of ViewPort META - https://trends.builtwith.com/mobile/Viewport-Meta.
If we go with that approach, we will tracking usage of META tag 'apple-itunes-app' and 'google-play-app'. In terms of linking from chrome extension to a site -

For 'apple-itunes-app, we will link to https://developer.apple.com/documentation/webkit/promoting_apps_with_smart_app_banners
For 'google-play-app', I will have to find the relevant link

and if we are making it generic, for Viewport META, link can be https://www.w3schools.com/css/css_rwd_viewport.asp

Either way it relies on the developer including the relevant meta tags, the majority of websites that may have a mobile app may not include this. Would you still be able to get useful metrics from it?


spinning blue circle during first load experience

When trying to add app to my left rail in Teams I get the spinning blue circle during first load experience.  I have pimmed to Teams Admin, SharePoint, Admin, and Application Administrator.
If I try to add the app to a Teams/channel site, I get a message at top saying 'Welcome to the Microsoft 365 Champion Management Platform' on the left side is text "Quick Start Guide' and on the right side is the spinning blue circle. I am an owner of the Teams site.
I've tried multiple times, e.g. uninstalling the app.  In SharePoint I approved the API access. As a SharePoint admin, I can create SharePoint sites.
I am working with version <IP_ADDRESS>

Hi @dietrichmeyer,
Thanks for your patience.
Please try the below steps for a reinstall using an account with "Tenant admin" access:

Delete the app from Teams

Delete 'ChampionManagementPlatform' Sharepoint site from both 'Active Sites' and 'Deleted Sites' from Share point admin center.

Delete the package from App catalog

Wait for 15-30 mins to clear the cache related issues.

Re upload the package to app catalog and deploy and sync to Teams.

Install the APP in Teams using the same tenant admin account. Perform this step by opening Teams in browser.

If you see an error "An issue occurred. Try again after some time", try refreshing the app after few minutes.

Please follow the steps above and if you see any issues please share screenshots and browser console logs.
Thanks.

I have a customer with this same spinning blue circle issue who followed these instructions for uploading the new version after the previous version also gave the spinning blue circle and the new version still fails to get past the first spinning blue circle. Any other suggestions?

v-saikirang sent me the email below to just reinstall, which I did and it eventually worked.
I didn’t have Tenant admin access but I did PIM to Administrator Admin, SharePoint Admin, and Teams Admin.
It got me past the spinning blue circle.
From: v-saikirang @.>
Sent: Thursday, November 18, 2021 11:05 PM
To: OfficeDev/microsoft-teams-apps-champion-management @.>
Cc: Meyer, Clark D @.>; Mention @.>
Subject: [External Mail] Re: [OfficeDev/microsoft-teams-apps-champion-management] spinning blue circle during first load experience (Issue #69)
CAUTION: This email originated from outside of the Allina Health network. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi @dietrichmeyer,
Thanks for your patience.
Please try the below steps for a reinstall using an account with "Tenant admin" access:

    Delete the app from Teams

    Delete 'ChampionManagementPlatform' Sharepoint site from both 'Active Sites' and 'Deleted Sites' from Share point admin center.

    Delete the package from App catalog

    Wait for 15-30 mins to clear the cache related issues.

    Re upload the package to app catalog and deploy and sync to Teams.

    Install the APP in Teams using the same tenant admin account. Perform this step by opening Teams in browser.

    If you see an error "An issue occurred. Try again after some time", try refreshing the app after few minutes.

Please follow the steps above and if you see any issues please share screenshots and browser console logs.
Thanks.
Clark Meyer
Phone:<PHONE_NUMBER>
From: StaciMild @.>
Sent: Thursday, December 16, 2021 9:24 AM
To: OfficeDev/microsoft-teams-apps-champion-management @.>
Cc: Meyer, Clark D @.>; Mention @.>
Subject: [External Mail] Re: [OfficeDev/microsoft-teams-apps-champion-management] spinning blue circle during first load experience (Issue #69)
CAUTION: This email originated from outside of the Allina Health network. Do not click links or open attachments unless you recognize the sender and know the content is safe.
I have a customer with this same spinning blue circle issue who followed these instructions for uploading the new version after the previous version also gave the spinning blue circle and the new version still fails to get past the first spinning blue circle. Any other suggestions?
[FailChampionsPlatform]https://user-images.githubusercontent.com/61475939/146399198-8a6b198c-9bcf-4f39-9d39-45f66468f7e0.jpg
—
Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-apps-champion-management/issues/69#issuecomment-995918177, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVJEA3NP5SPWFH4JY3IUWKLURIABNANCNFSM5IKWT7XA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This message contains information that is confidential and may be privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message.

Hi @StaciMild,
Please try refreshing the app. If you still see any issues please follow the instructions as mentioned  above. Thanks @dietrichmeyer for your inputs here

Thank you both. Customer performed the full, exact steps and is still getting this generic error as depicted above. Any other suggestions?

Hi @StaciMild,
If you are fine to troubleshoot over a call please share your Email and i can set up a meeting to go over the issue.
Thanks.

@.***
please also invite @.*** (Ryan Perian), my customer who can share with you his tenant and deployment details for the app.
we are open today before 4 PM EST.
Staci

From: v-saikirang @.>
Sent: Tuesday, December 21, 2021 2:02 AM
To: OfficeDev/microsoft-teams-apps-champion-management @.>
Cc: Staci Mildenberger @.>; Mention @.>
Subject: Re: [OfficeDev/microsoft-teams-apps-champion-management] spinning blue circle during first load experience (Issue #69)
Hi @StaciMildhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FStaciMild&data=04|01|staci.mildenberger%40microsoft.com|fdb9e7931d7b485cf99608d9c44fd0e7|72f988bf86f141af91ab2d7cd011db47|1|0|637756669360379326|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=VoGB3ZuDst28J7XucVw8x2odTeuOnvBkbwStZhgLn4M%3D&reserved=0,
If you are fine to troubleshoot over a call please share your Email and i can set up a meeting to go over the issue.
Thanks.
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fmicrosoft-teams-apps-champion-management%2Fissues%2F69%23issuecomment-998523589&data=04|01|staci.mildenberger%40microsoft.com|fdb9e7931d7b485cf99608d9c44fd0e7|72f988bf86f141af91ab2d7cd011db47|1|0|637756669360379326|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=qKfXqyasxg7f%2FGYaWQ2OsYIojJ0ulgQjpDS49dOxCy0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOVAYY42SVZ7RNREFLILCSDUSAQ7LANCNFSM5IKWT7XA&data=04|01|staci.mildenberger%40microsoft.com|fdb9e7931d7b485cf99608d9c44fd0e7|72f988bf86f141af91ab2d7cd011db47|1|0|637756669360429327|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=6FSxTPPpr2azlGhPMlju30nQsCISCJm5UEX3elmt164%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|staci.mildenberger%40microsoft.com|fdb9e7931d7b485cf99608d9c44fd0e7|72f988bf86f141af91ab2d7cd011db47|1|0|637756669360429327|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=yZnD%2BRO%2FM8spN3tBhf93ig556dJN4cPsCu7qZBckHFs%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|staci.mildenberger%40microsoft.com|fdb9e7931d7b485cf99608d9c44fd0e7|72f988bf86f141af91ab2d7cd011db47|1|0|637756669360429327|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=DRHJZRcbrHnTC3H%2BfPIr4yfzIGc7PWl4Uum6pU7v0M8%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @StaciMild,
I cant find the Email IDs in the above message. Can you please share.
Thanks.

<EMAIL_ADDRESS><EMAIL_ADDRESS>


Favorites - Icon size/mouse move

As mentioned in the pull request, moving the mouse along the red line:

will make the dropdown disappear. The icon horizontal width is quite small, can we extend the element with blank space or do something so moving the mouse along the red line will not make the dropdown disappear?

follows #401
Yeap, I'll fix with an invisible CSS element most probably.
http://www.positioniseverything.net/css-dropdowns-red.html

OK, added some extension zone and some "forgiving shadow" zone. Should be fine now.
CSS is in a mess a bit, but I plan a serious refactoring after implementation of "external resources".

Closing then. :)


Support for Ember 1.9.0 + HBS 2.0.0?

Hi, I tried to update my app to Ember 1.9.0 and Handlebars 2.0.0. I'm on ember-cli 0.1.4. With a single {{liquid-outlet}} in my template, I get the following deprecation:
DEPRECATION: Using {{outlet}} with an unquoted name is not supported.
But the outlet doesn't use a name in this case, so? Apologies if this was already fixed in the master branch.

Same here. I'm using 0.16.0 but still get the depreciation message.

In case anyone stumbles on this deprecation that happens to be using emblem for templates, you need to use a standard handlebars tag:
| {{liquid-outlet}}


v0.0.5

Version is actually v0.0.5, not v0.0.4, so updated issue title accordingly and the CHANGELOG.md.


Compare Images Failed - how to ignore the false positive differences?

Basically, I just want to compare the content within the webpage, the browser border/windows date time/taskbar isn't concern.
How do I set robot to ignore them?

Hi, there are different ways how to ignore parts.
One very simple way, is by using an area mask.
You can basically say: Ignore the top 10 % of the image. Or the left 5% of the image.
That's a very simple way to ignore parts.
Check out the example here for Compare two different PDF Files with area mask
https://github.com/manykarim/robotframework-doctestlibrary/blob/main/atest/Compare.robot
Compare Images    testdata/sample_1_page.pdf    testdata/sample_1_page_changed.pdf    placeholder_file=testdata/pdf_area_mask.json
The mask file looks like that:
[     { 		"page": "all", 		"name": "Job ID", 		"type": "area", 		"location": "top", 		"percent":	10 	} ]
You will also find some explanatio here
https://github.com/manykarim/robotframework-doctestlibrary#different-mask-types-to-ignore-parts-when-comparing
It is also mentioned in the video (roughly from this position)
https://youtu.be/qmpwlQoJ-nE?t=377

thanks I got it by simply use
[
    {
    "page": "all",
    "type": "area",
    "location": "top",
    "percent":  15
    },
    {
    "page": "all",
    "type": "area",
    "location": "left",
    "percent":  15
    },
    {
    "page": "all",
    "type": "area",
    "location": "right",
    "percent":  15
    },
    {
    "page": "all",
    "type": "area",
    "location": "bottom",
    "percent":  15
    }
]

Cool, happy that this solved your problem :)


Adding queue name to FailedEnqueueException

FailedEnqueueException isn't hugely useful at the moment, if I'm a client and catching it, I have little idea of what's gone on. I can pull out the failed messages and the adapter that emitted it but not the queue url/name that failed to enqueue.
This PR adds an argument to FailedEnqueueException to represent the name of the queue. In SqsAdapter I have simply used the $this->name var for this purpose. I don't think it's unreasonable to assume that other queue adapters will also have a unique identifier for a queue that can be used.

@h-bragg as it stands this is a BC break, do you agree? I could change it to be a minor rather than major change. Thoughts?

Hmmm, that is true. For something this minor it seems excessive to generate a whole new major(ish) version.
You could do some __toString() checking; a bit ugly. OR some kind of NamedInterface or QueueNameInterface that has getName() which the adapter might implement.
I would do 2 PR's one (this change) and merge into a new 0.4 branch and another that is the equivalent but only a minor change to get the name but a but more hacky.

@h-bragg this is now a BC break PR into the 1.0 branch.

So, with the other change... Should we actually keep this. Using a NamedInterface seems a bit tidier, and with AdapterException being the base it is more generic...

@h-bragg yeh having gone through the other change, I think it's a better all-rounder. Close this off?

Closed because this is a better and less breaking implementation: https://github.com/graze/queue/pull/38


[Ostrava] Just to re-deploy

SSIA, we need to deploy new set of tasks today.

Tested also locally.


Re-exporting EventInfo

Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>Leftover of #83

@slinkydeveloper I don't see any local code depending on this reexport though?

@tcnghia nope, this is to help users of the assert (look at https://github.com/knative/eventing/pull/4859 for more details)


e2e testing using Nightwatch and Cucumber

This is an experiment to add e2e testing alongside with unit tests using Nightwatch.js writen in Cucumber.
The following new ENV variables are required:
QA_USER_EMAIL=
QA_USER_PASSWORD=
QA_SELENIUM_PORT=4444
QA_SELENIUM_HOST=<IP_ADDRESS>
QA_HOST=http://localhost:3000

QA_USER_EMAIL can be set to<EMAIL_ADDRESS>QA_HOST can be pointed to https://rhod.datahub.dev.uktrade.io
The password is usual.

LGTM 👍


wrong definition of action_space in env/env_stocktrading.py ?

In file env/env_stocktrading.py and also in env/env_portfolio.py:
self.action_space = spaces.Box(low = -1, high = 1,shape = (self.action_space,))
how can this recursive definition be correct? Should it not be:
self.action_space = spaces.Box(low = -1, high = 1,shape = (self.stock_dim,))
?
In fact, the comment above this line in env/env_portfolio.py mentions:
 # action_space normalization and shape is self.stock_dim
Anyways, I guess these files for defining the environment are obsolete since there is a newer version StockTradingEnvV2 in multistock_docker.ipynb and this one defines the state space correctly as
        self.state_space = (
            1 + len(self.assets) + len(self.assets) * len(self.daily_information_cols)
        )

, right?

I think the codes in the file env/env_stocktrading.py and env/env_portfolio.py are correct. Before this definition, we have assigned the action space dimension to self.action_space. For example, you can see the corresponding codes in lines 48 and 50 in the file env/env_stocktrading.py. And action_space is one input parameter in the StockTradingEnv.

Of course your suggestion: self.action_space = spaces.Box(low = -1, high = 1,shape = (self.stock_dim,)) is also correct. In  the action settings in the file env/env_stocktrading.py and env/env_portfolio.py, the dimension of the action space is equal to the stock dimension.
The reason for differentiating stock dimension and action space dimension is that they are NOT necessarily the same in the general case.  For example, if you are designing an environment for single stock trading using the DQN algorithm, you may consider setting the stock dimension to 1 and the action space dimension to 3, where action 0 means doing nothing, action 1 means buying 100 shares and action 2 means selling 100 shares.
Hope this helps.


Branch release/v7, vs running problem

Use the following command clone
git clone -b release/v7 --recurse-submodules https://github.com/lvgl/lv_sim_visual_studio.git

No response when running vs.

Hi.
I'm having the same problem.
I need to install v7 on visual studio 2022 (actually downgraded 2019 v142) and I do not find the way.
Please help!
thank you

@gregrgr @sergioaiello
I have reproduced the issue and fixed it.
Because the newer version of win32drv don't support LVGL v7, I have created the win32drv_v7 in release/v7 branch.
Kenji Mouri

Hi,
I did:
git clone https://github.com/lvgl/lv_sim_visual_studio.git
--recurse-submodules
cd lv_sim_visual_studio
git checkout release/v7
git submodule update
when I loaded the sln file I got an error window with the following
message:
One or more projects in the solution were not loaded correctly.
Please see the Output Window for details.
And Visual Studio did not open a workable project.
Could you, pls, help me?
Thank you and best regards, S.


ElephantSQL free tier usage doesn't work

It appears the free tier on ElephantSQL doesn't allow you to create roles.

ERROR:  permission denied to create role


plugin does not exist

Support guidelines

[X] I've read the support guidelines

I've found a bug and checked that ...

[X] ... the documentation does not mention anything about my problem
[X] ... there are no open or closed issues that are related to my problem

Description
I'm seeing the following in the logs. I dont have any plugins disabled per the docker env vars
Setting custom config for create plugin...
  WARNING: create plugin does not exist

Setting GeoIP2 databases for geoip2 plugin...
  WARNING: geoip2 plugin does not exist

Expected behaviour
All plugins should work
Actual behaviour
create and geoip2 dont work per the log files.
I've also noticed the edit plugin isn't available and doesn't show up under the Plugins tab
Steps to reproduce
Start container with no plugins disabled
View the logs
Docker info
Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 10
  Running: 10
  Paused: 0
  Stopped: 0
 Images: 10
 Server Version: 20.10.3
 Storage Driver: btrfs
  Build Version: Btrfs v4.0
  Library Version: 101
 Logging Driver: db
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs db fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3fa00912415f3e9c6f82dd72119179d599efd13b
 runc version: 31cc25f16f5eba4d0f53e35374532873744f4b31
 init version: ed96d00 (expected: de40ad0)
 Security Options:
  apparmor
 Kernel Version: 4.4.180+
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 31.32GiB
 Name: DiskStation
 ID: TKJ6:OOPS:DLHP:LVJL:CDWA:JLVD:6O3A:OMQI:BHGE:VN4V:B7LE:JBLE
 Docker Root Dir: /volume3/@docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio weight support
WARNING: No blkio weight_device support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support

Version
docker-compose version 1.28.5, build 24fb474e
Linux DiskStation 4.4.180+ #42661 SMP Fri Apr 1 15:31:10 CST 2022 x86_64 GNU/Linux synology_v1000_1821+
Docker compose
n/a

Container logs
Setting custom config for create plugin...
WARNING: create plugin does not exist
Setting GeoIP2 databases for geoip2 plugin...
WARNING: geoip2 plugin does not exist
Additional info
No response

Can't tell without seeing your compose file and full logs. Please create a proper bug report.


Changed start_date was ignored in vector tiles

OHM obviously doesn't like v2 edits.
v1 was a route from Aschaffenburg to Würzburg with start_date=1796
v2 is an old ferry route via Lengfurt ferry which started (as turnpike) in 1775.
In 1846, a new bridge was built across Main river in Marktheidenfeld. As a consequence, Lengfurt has lost a lot of its ferry traffic.
1846 is the only year where both routes (new bridge and old ferry) were equallly important.
However, OHM ignores the changed start_date in Marktheidenfeld.
https://www.openhistoricalmap.org/changeset/151014#map=12/49.8154/9.7081&layers=O&date=1846-06-02

Another location, same problem: Kärntner Straße in Graz (southwestern main highway)
https://www.openhistoricalmap.org/#map=14/46.9777/15.3929&layers=O&date=1821-08-20
start_date was brought forward from 1868 to 1814. In 1868, the highway was officially approved by state parliament, however construction started in 1814 as military operation during wartime. In 1822, a book describes it as "new road". While there is some untertainty about 1814/1822 construction, the road from Graz to southwest should certainly appear since 1823.

Thanks for posting this. We have been implementing some server-side caching to improve map rendering performance and my hunch is that these edits are not getting purged and re-rendered in a timely fashion in the map tiles, though the edits are properly saved in the OHM database.
We see here that the start_date is 1846:

That's Way ID 200380759
But then in the vector tiles, in the same area if we inspect the same Way ID, we still show 1796:

So for some reason the change in teh OHM database is not making it into the tiles, though the edit was ~2 days ago.

I just fixed the issue. It was related to imposm, which is responsible for importing and updating the tiler-db. It had fallen behind, but now it is fully up to date.


Checkpoint name attributed may needs updated for OFA_large

I downloaded the pre-trained OFA-large checkpoint here: https://ofa-beijing.oss-cn-beijing.aliyuncs.com/checkpoints/ofa_large.pt
And try to load the model by
task = tasks.setup_task(cfg.task)
models, cfg = checkpoint_utils.load_model_ensemble(
    pre_trained_model_path,
    task=task
)

But it doesn't work and it shows didn't find the corresponding model name.
Then I check the checkpoint , found the name is m6_unify_large
Then I modify this line https://github.com/OFA-Sys/OFA/blob/main/models/ofa/ofa.py#L320 to replace ofa_large to m6_unify_large then everything works fine.
I guess maybe need to update a bit the checkpoint state and upload again

Thank you so much for pointing this out! We have updated and uploaded the OFA-large checkpoint.


dbt-ol Loggin the wrong number of events emitted

Stack trace:
[2023-01-09, 15:54:41 UTC] {subprocess.py:75} INFO - Running command: ['/bin/bash', '-c', 'dbt-ol run --profiles-dir /usr/local/airflow/include/dbt --project-dir /usr/local/airflow/include/dbt/jaffle_shop']
[2023-01-09, 15:54:41 UTC] {subprocess.py:86} INFO - Output:
[2023-01-09, 15:54:41 UTC] {subprocess.py:93} INFO - Running OpenLineage dbt wrapper version 0.17.0
[2023-01-09, 15:54:41 UTC] {subprocess.py:93} INFO - This wrapper will send OpenLineage events at the end of dbt execution.
[2023-01-09, 15:54:44 UTC] {subprocess.py:93} INFO - 15:54:44  Running with dbt=1.3.0
[2023-01-09, 15:54:44 UTC] {subprocess.py:93} INFO - 15:54:44  Found 5 models, 20 tests, 0 snapshots, 0 analyses, 303 macros, 0 operations, 3 seed files, 0 sources, 0 exposures, 0 metrics
[2023-01-09, 15:54:44 UTC] {subprocess.py:93} INFO - 15:54:44
[2023-01-09, 15:54:46 UTC] {subprocess.py:93} INFO - 15:54:46  Concurrency: 1 threads (target='dev')
[2023-01-09, 15:54:46 UTC] {subprocess.py:93} INFO - 15:54:46
[2023-01-09, 15:54:46 UTC] {subprocess.py:93} INFO - 15:54:46  1 of 5 START sql view model demo.stg_customers ................................. [RUN]
[2023-01-09, 15:54:47 UTC] {subprocess.py:93} INFO - 15:54:47  1 of 5 OK created sql view model demo.stg_customers ............................ [SUCCESS 1 in 0.69s]
[2023-01-09, 15:54:47 UTC] {subprocess.py:93} INFO - 15:54:47  2 of 5 START sql view model demo.stg_orders .................................... [RUN]
[2023-01-09, 15:54:47 UTC] {subprocess.py:93} INFO - 15:54:47  2 of 5 OK created sql view model demo.stg_orders ............................... [SUCCESS 1 in 0.68s]
[2023-01-09, 15:54:47 UTC] {subprocess.py:93} INFO - 15:54:47  3 of 5 START sql view model demo.stg_payments .................................. [RUN]
[2023-01-09, 15:54:48 UTC] {subprocess.py:93} INFO - 15:54:48  3 of 5 OK created sql view model demo.stg_payments ............................. [SUCCESS 1 in 0.61s]
[2023-01-09, 15:54:48 UTC] {subprocess.py:93} INFO - 15:54:48  4 of 5 START sql table model demo.customers .................................... [RUN]
[2023-01-09, 15:54:50 UTC] {subprocess.py:93} INFO - 15:54:50  4 of 5 OK created sql table model demo.customers ............................... [SUCCESS 1 in 2.07s]
[2023-01-09, 15:54:50 UTC] {subprocess.py:93} INFO - 15:54:50  5 of 5 START sql table model demo.orders ....................................... [RUN]
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52  5 of 5 OK created sql table model demo.orders .................................. [SUCCESS 1 in 1.58s]
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52  Finished running 3 view models, 2 table models in 0 hours 0 minutes and 8.00 seconds (8.00s).
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52  Completed successfully
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52
[2023-01-09, 15:54:52 UTC] {subprocess.py:93} INFO - 15:54:52  Done. PASS=5 WARN=0 ERROR=0 SKIP=0 TOTAL=5
[2023-01-09, 15:54:54 UTC] {subprocess.py:93} INFO -
Emitting OpenLineage events:   0%|          | 0/10 [00:00<?, ?it/s]
Emitting OpenLineage events:  10%|█         | 1/10 [00:00<00:02,  3.45it/s]
Emitting OpenLineage events:  20%|██        | 2/10 [00:00<00:01,  4.90it/s]
Emitting OpenLineage events:  30%|███       | 3/10 [00:00<00:01,  6.07it/s]
Emitting OpenLineage events:  40%|████      | 4/10 [00:00<00:01,  4.86it/s]
Emitting OpenLineage events:  50%|█████     | 5/10 [00:01<00:01,  4.58it/s]
Emitting OpenLineage events:  60%|██████    | 6/10 [00:01<00:00,  4.94it/s]
Emitting OpenLineage events:  70%|███████   | 7/10 [00:01<00:00,  5.29it/s]
Emitting OpenLineage events:  80%|████████  | 8/10 [00:01<00:00,  5.86it/s]
Emitting OpenLineage events:  90%|█████████ | 9/10 [00:01<00:00,  4.96it/s]
Emitting OpenLineage events: 100%|██████████| 10/10 [00:02<00:00,  4.29it/s]
Emitting OpenLineage events: 100%|██████████| 10/10 [00:02<00:00,  4.76it/s]
[2023-01-09, 15:54:54 UTC] {subprocess.py:93} INFO - Emitted 12 openlineage events
[2023-01-09, 15:54:54 UTC] {subprocess.py:97} INFO - Command exited with return code 0

Logging is saying 12 events emitted, when the progress bar shows 10 events.

Yeah, this is known issue - the 2 additional events are "wrapping" events for overall dbt project, serving as parent for each task. The progress bar does not show them, because it's emitted outside of its context.
How confusing is current setup? We can either add information to the Emitted X events or maybe we can hack progress bar to show those additional events.

I think even just a line before mentioning that 2 additional wrapping events are occurring would be plenty.


Fix issue with static files

Pictures

TODO List
Before merging, a PR will need

[ ] Signoff from product if there are UX changes
[ ] Signoff from one other engineer at Architect.io

Running into an issue during testing where the migration does not seem to be running.
Looking into why and a fix.

Giving engineering sign off


仓库更新

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

更新


Show warnings - implementation

Signed-off-by: kuba--<EMAIL_ADDRESS>This PR implements just:
SHOW WARNINGS [LIMIT [offset,] count]

Note: We need to implement collect session warnings (https://github.com/src-d/go-mysql-server/issues/465)
Closes https://github.com/src-d/go-mysql-server/issues/442

@erizocosmico - I wrapped it by Offset/Limit (what's cool - I didn't notice that we've already got it).
Regarding naming... I renamed AppendWarning to Warn. I don't like both (but I don't have a better idea). AddWarning describes an operation, so I don't see any difference to Append.... Eventually we can rename it to Put... (which is more stack related).
Anyway, I sticked to Warn assuming that it's pretty descriptive and less is sometimes more.

@erizocosmico - done.

@ajnavarro - added clearWarnings rule. PTAL

@kuba-- could you rebase again please?


Form view does not correspond to graph editor view -> (ref: gomodel:5ae3b0f600000604)

From @BarbaraCzub on May 24, 2018 17:7
Hi,
I have 5 annotations displayed in the form view:

But only 3 are displayed in the model:

Why is this? The 2 which are missing, do actually get displayed in the graph view for the first 1 second after switching to it, but then disappear.
And: how do I delete an annotation from the form view? (The fifth annotation is an identical copy of the fourth one. I added it only as a test, because the fourth annotation was not getting displayed in the graph view, and now I don't know how to remove it - it's not shown in 'Take a Tour').
Thanks,
Barbara
Copied from original issue: geneontology/noctua-models#95

From @vanaukenk on May 24, 2018 17:28
Also, @tmushayahama and @lpalbou are working on adding Delete functionality to the form.  We want to make sure that when curators delete information using the form, the full implications are apparent, i.e. the potential effects on other relations and nodes in a given model.
Does deleting from the graph editor work okay for you in the meantime?

Thank you @kltm!
And is there a way to navigate from the graph view directly to the form view?
(In the form view you have the drop down menu, which can be used to navigate to the graph view. But I do not think the opposite is possible?)

@BarbaraCzub
In the graph view, click on the Workbenches menu and then select 'Noctua form' at the very bottom of the list.

Thank you!

There are a number of things in this ticket, but the main issue wrt placement of new nodes seems to be fixed, so I will close the ticket.
For effects of deleting BP nodes, see #94


#169 add pre/post hooks for the canvas renderers

Following an issue on linkurious.js, here's a backward-compatible change to the canvas renderer allowing pre and post hooks to the renderers.
It's mainly useful for improving performance. It's used to be able to do pre-computation in the renderers.
It's already implemented in the svg and webgl renderers in some way (update/create in the svg renderer for example).
You can see how I doubled the performance of the performance via this fix in this edges label renderer for example: https://github.com/Linkurious/linkurious.js/blob/bench/edge-labels/bench/final.js

Fixed the webgl renderer usage of the canvas renderers, needs to be merged again.


akash provider lease-shell and the way it handles EOF

akash v0.16.4-rc2.
There are different use-cases getting broken due to the way akash provider lease-shell handles EOF.

Can upload the data into the container using this command, despite the error:

$ tar -cf - -C /usr/share -- info | akash provider lease-shell --stdin app1 -- tar -xf - -C /root
Error: EOF: failed while reading from stdin

When passing "z" flag (compressed tar), it just hangs until I Ctrl+C it:

$ tar -czf - -C /usr/share -- info | akash provider lease-shell --stdin app1 -- tar -xzf - -C /root
halted by signal: interrupt

even a small file:
$ tar -czf - -C /etc -- hosts | akash provider lease-shell --stdin app1 -- tar -xzf - -C /root
halted by signal: interrupt

It is waiting forever on user input (neither Ctrl+D is helping):

$ echo hi30 | akash provider lease-shell --stdin app1 -- cat -
hi30
<prompt hangs in here>

the issue still persists:

provider-services v0.2.1

[10390294-1-1-ssh]$ tar -cf - -C /usr/share -- info | provider-services lease-shell --stdin -- ssh tar -xf - -C /root
Error: EOF: failed while reading from stdin

[10390294-1-1-ssh]$ tar -czf - -C /usr/share -- info | provider-services lease-shell --stdin -- ssh tar -xf - -C /root
tar: Archive is compressed. Use -z option
tar: Error is not recoverable: exiting now
Error: lease shell failed: remote process exited with code 2
tar: -: Wrote only 8192 of 10240 bytes
tar: Child returned status 141
tar: Error is not recoverable: exiting now

[10390294-1-1-ssh]$ tar -czf - -C /etc -- hosts | provider-services lease-shell --stdin -- ssh tar -xf - -C /root
<hangs here>


Tweak: Make evac pods flyable

About the PR

copied the design of the disaster evec pod unkonwn shuttle event to the emergency pods.
Why / Balance

issue: https://github.com/Goob-Station/Goob-Station/issues/632
Technical details

old evac pod had the component "ProtectedGrid"
i havent re added this so the shuttle buildes can build and expand the pod
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

tweak: escape pod now flyable

Summary by CodeRabbit

New Features

Introduced a new map entity for enhanced functionality and structure.
Added prototypes for "ComputerShuttle" and "Gyroscope," expanding gameplay elements.

Improvements

Updated the "NT Escape Pod" entity to improve its interaction with the map.


media_player doesn't send off IR command if entity is off but TV is on

I'm having a issue with the debug logs and will update this post with relevant logs and yaml shortly
Home Assistant version
2024.11.2
SmartIR version
1.19.0
SmartIR configuration

media_player:
  - platform: smartir
    name: Smartir TV sala
    unique_id: smartir_tvsala
    device_code: 1060
    controller_data:
      controller_type: Broadlink
      remote_entity: remote.rm4new
      delay_secs: 0.5
      num_repeats: 1

Describe the bug
AFTER 1.17.15, if the TV is ON but the TV media player entity is OFF (turned on via real remote). HA wont turn TV off using the media_player.turn_off service. The IR command is not sent
If I turn the entity ON, then OFF, the OFF IR command will be sent.
(either via UI or service)
Expected behavior
To HA always send the IR turn off command independently to the entity state (climate entity works exactly like that!)
(works this way before 1.17.15)
To Reproduce

Turn on TV manually
send media_player.turn_off command to the corresponding TV entity

Debug log
(it's the only log related to smartir i see after reproducing the bug)
2024-11-23 17:52:58.030 DEBUG (MainThread) [custom_components.smartir.media_player] Setting up the SmartIR media player platform

Additional context
I want to reinforce that the climate entity works exactly in the way described in Expected field. I was using the "official" SmartIR integration and never encountered this issue. I'm currently reinstalling it to check and will update this post with the information

I can confirm that in 1.17.9 in the original SmartIR git, this behavior is not present. The media_player works as I described in the Expected field.

The issue is present after 1.17.15
Seems to be related to this commit from @litinoveweedle

Hello, can you please check, if the ON and OFF code are different or same?

Hello, can you please check, if the ON and OFF code are different or same?

In this case yes, the repo has discrete on and off commands

Yep, I can confirm this bug. The proposed correction is to sent always ON or OFF command except the case, when ON and OFF codes are same - then the current functionality will be kept.

Yep, I can confirm this bug. The proposed correction is to sent always ON or OFF command except the case, when ON and OFF codes are same - then the current functionality will be kept.

I would suggest always send the command, independly of the state of the entity because the entity state doesn't have a direct relation to the real tv state.
Imagine this situation:

ON and OFF codes are equal, mediaplayer entity is OFF and TV is OFF
I Turn on TV by the physical remote
I call alexa: "Alexa, turn off the TV"
SmartIR would not turn off the tv, because both codes are equal and entity state is off
Doesn't sound good

The only case in which this makes sense is if both codes are equal AND the feature of power_sensor is enabled (entity attributed to it)

While I understand you explanation, the feature to prevent sending again ON/OFF commands was implemented based on #70 and you can read very good reasoning behind it as well. So if we will not come with some smart idea how to accommodate both cases.....

While I understand you explanation, the feature to prevent sending again ON/OFF commands was implemented based on #70 and you can read very good reasoning behind it as well. So if we will not come with some smart idea how to accommodate both cases.....

Okay, good point, but...  Make it configurable!
We have the same issues with cover_template, in yaml we have a field called optimistic
if it's true, the HA stores the internal state and will refuse to send a command to lower the cover if it's already in lowered state.
if it's false, you can send whatever command whenever you want to.

Good point. Even I am not much of a fan of inflating configuration to include options for every single use case, this one is probably deserved. To keep backward compatibility, by default this option would be set to false. It will be only used in case when the power sensor is not used. I think then similar change needs to be implemented in all classes across SmartIR.


Add option to allow customization of the thickness of the slider bar

Describe the Feature
It would be great to allow the option to customize the thickness of the slider bar itself.  Something like a thickness prop.

This is somewhat related, but being abble to set the size of the thumb would be great too.
<Slider
    // ...
    trackThickness={5}
    thumbSize={12}
    />

Seeing that many people are waiting for this, until it's implemented here, you can use this slider that does that. It uses the same API so your code should not change.

Hello @pistou and @holtc!
I understand the case, but I can't give any estimation on when will it be implemented, but at the same time I'm definitely not saying "no" to this.
Hence why I keep this open and trying to figure out the way to implement features that are not natively supported by all four (Android, iOS, Windows, Web) platforms we support. Thank you for the patience!

@BartoszKlonowski  Any ETA for this issue?

I would really appreciate if this feature was implemented 🙇

so which prop can I use to increase the thickness of the slider

when will it be implemented?

5 year passed, and this feature has not been implemented?!

  slider: {
width: '100%',
height: 100,
marginBottom: 24,

},
still not working.

slider: {
width: '100%',
height: 100,
},
not working thumbSize, height, trackThickness

is this Feature implemented?

any updates on this please ?

No plans for this?

Any plans for this feature to be implemented?

Any progress?

Any progress?
All other tickets about thickness are closed as "duplicates" while no real progess on this 5 year-old ticket...

I'm no android dev but it seems like this is a limitation of SeekBar not having a height property, whereas Slider has a method called setTrackHeight(int) docs
Not sure if this means it needs a whole rewrite for the package, if anyone has any expertise with Java feel free to weigh in

brother we're still waiting for this


[BUG] set_annotations fails for data with a meas_date prior to 1970

Try reading this example_file (800MB) and check out raw.info['meas_date'] --> it will be negative.
That's because the data has been anonymized (cc @agramfort ) to some time prior 1970.
That's an issue, because we represent raw.info['meas_date'] in unix time, which is 0 at 1970, and thus negative for all prior years (strictly speaking, it's even undefined)
A negative meas_date will raise an error when we make an annotation object from scratch and try to set it with raw.set_annotations().
That is because of this code:
in set_annotations: https://github.com/mne-tools/mne-python/blob/368a490f9d7a298050ee04c2aa7882629c9fab21/mne/io/base.py#L792
--> time_of_first_sample will be negative if meas_date is negative
then later we do: https://github.com/mne-tools/mne-python/blob/368a490f9d7a298050ee04c2aa7882629c9fab21/mne/io/base.py#L798-L801
i.e., pass a negative tmin to the crop function, which then raises an error: https://github.com/mne-tools/mne-python/blob/368a490f9d7a298050ee04c2aa7882629c9fab21/mne/annotations.py#L363-L364

If there is no limitations with fif files to have negative time stamps we should handle these files smoothly

Yes this seems like a bug in our Annotations handling somewhere. @massich can you look?
It should not matter what meas_date relative to 1970 is (negative or positive)

yes I was just looking at it

What was the logic behind DATE_NONE and anonymization?
I understand that is a convention to move the date to 1930 or so for anonymization purposes. But do people usually keep the rest of the information i.e: imagine that I have one record every month/year for a particular subject. Do they only offset to 1/1/1930 and keep all the recordings with respect to that date or do we fold all recordings to the same date?

@massich see: https://github.com/mne-tools/mne-bids/issues/193#issue-436776387
I don't know about how anonymization is currently handled in MNE, but I think the way we SHOULD handle this is to allow for an anonymization by a certain offset in days ... this would then be applied to all data recordings of a subject, so that the relative time distances keep their logic.
the anonymization_offset_days would be set to a sensible default but could also be given as an input to raw.annonymize(anonymization_offset_days=36500)
I briefly discussed this with @larsoner at the last MNE sprint, maybe he wants to weigh in

yes we need to have such anonymization routines in mne-python
the reason why you cannot set the date to None is that you want to
keep the order between
datasets eg for longitdinal studies etc. So yes we should use random
day offsets and make
sure the dates can be before 1970. The latest mne-c command does this
with .fif files


Different widget form factor (2w*4h)

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
6.202
Problem you are trying to solve
Well, put simply: The widget size of 4 wide by 3 high is too large.
Suggested solution
Coming from blackberry I tried the blackberry client for Android only to be disappointed and after about a year I've had it now.
What I do enjoy is the widget though. The size of 2 wide by 4 tall is perfect to allow a rough but good overview of the mail inboxes while leaving enough space for further apps.
If k-9 would support a 2*4 widget I'd switch for good tbh.
Screenshots / Drawings / Technical details
Ignoring the wallpaper you can see 24 allows for essential apps to be easy to reach on the first page allowing it to be the perfect hub for everything necessary
Using the current 43 sized widget there'd be a lot space wasted and would make this efficient layout impossible.

edit: reduced image display size

K-9 Mail's message list widget can be resized. On most Android versions this works by long-pressing the widget on your home screen.

ahh, thanks, I'm still fairly new to android and learning the ins and outs. I tried that but must have overlooked that faint blue outline that I noticed, now.
sadly the width is only reducible to 3 wide, is there a chance to have this limit reduced to 2?
I do admit that 2 is very narrow. I don't need the widget to do much work though, I mostly need to know which inbox received messages from whom, so I know whether I need to get active or not.

A width of 2 cells is very narrow and doesn't feel generally useful. But I guess it doesn't hurt to allow the user to make the choice.
I created pull request #6353 for the change.

thank you so much!


ES6 / Babel / Rollup / Mocha / Other

This is a rewrite / re-factor of the main tracker into ES6. This is not even close to final but I wanted to submit the PR now so that it if this is something you guys are considering there is no duplication of work. Here is a rough summary of what I did:
Convert to ES6
Convert build process to use rollup.js
Add Babel
Tried to fixup the JSDoc syntax wherever I could.
Mostly remove Lodash dependencies
Add Mocha and rewrite functional tests
There is still a decent amount to do. The built/compiled tracker works, however there are a lot of optimizations to the code that should happen. I also have a bunch of things I used for testing that should eventually be pulled out. Some additional things I would like to focus on would be:
More unit tests / better code coverage
Use JSDom to simulate more DOM / Browser things for unit tests
Update many methods / functions to use more efficient ES6 code
Update build process / docs
Modularize (pull out the code for optimizely etc. into plugins to reduce the size of the main bundle)
Update library to use fetch (or fetch polyfill) / beacon API
Once this ES6 conversion is in place it makes fixing some of the outstanding bugs and creating new plugins / functionality much easier. Also having 100% solid unit tests would probably be a huge plus. Anyways this is mostly to start the discussion, just trying to help however I can.
Cheers.

Hi @mmathias01, this is fantastic! We're just about to release a new version (pending the release of a schema to iglu central) that kicks off moving the codebase in the direction of an overhaul. This is super helpful and timely though because ES6 support (among the other parts of modern JS dev) is what I had in mind to tackle upon return from the holidays.
Agreed, let's keep work in the overhaul branch. Thanks again for jump-starting this!

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://github.com/snowplow/snowplow/wiki/CLA to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

Signed.

@mhadam :) glad this comes at a good time. I will do some more clean up and continue to add commits to this. Let me know what if any questions you have if any about the things I have done so far!

Confirmed! @mmathias01  has signed the Individual Contributor License Agreement. Thanks so much

@mhadam fixed the merge conflicts. I believe that I rebased in all of the changes you had made since I forked properly. Still need to pull in some of the new tests and look at the overall build process, but at least it is mergeable now so you have something to play with.


chore(main): release veto 0.1.4

:robot: I have created a release beep boop
0.1.4 (2024-04-12)
Bug Fixes

veto: expose VNumber (8138052)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/uniform/releases/tag/veto-v0.1.4 :sunflower:


Builtin support for dbstat table

After https://github.com/simolus3/sqlite3.dart/issues/237 landed, I added the dbstat table as a builtin table to the sqlparser.
Open question is, shall the inclusion of the dbstat table be controlled by an option (like its the case for json or fts)?

Merged in db75bce0d4ec41fbdf5aba74bd1ada14f4e24efc, I'll make this opt-in with a dbstat option you'd have to list in build.yaml.


zei/Update TLS settings to TLSv1.2

Signed-off-by: Vinay Satish<EMAIL_ADDRESS>Description
To improve the security of chef-server the TLS is defaulted to only TLSv1.2 instead of TLSv1 TLSv1.1 TLSv1.2
Issues Resolved
resolved #2302
Check List

[ ] All buildkite tests pass
[ ] Full omnibus build and tests in buildkite pass
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Adhoc build - https://buildkite.com/chef/chef-chef-server-master-omnibus-adhoc/builds/2300#_


Upload problem

When I upload the file, the contentType is multipart / form-data. Something went wrong. The reason is that when the convert method in the BodyConverter class gets the parameter value, the file type is according to String. Is this a bug or am I using it the wrong way.

This is not a bug. The default BodyHandler only works with JSON and Form. If you want to handle file upload, you need to provide your own handler according to the format or encoder you have for the data.

Here is an example of how to upload pdf files.
https://github.com/networknt/light-example-4j/blob/1.6.x/client/pdf/src/main/java/com/networknt/example/pdf/handler/PdfReportGetHandler.java

Another example of upload  https://www.codota.com/code/java/methods/io.undertow.util.Headers/extractQuotedValueFromHeader

I override the methods in BodyHandler and redefined the processing link. The problem was resolved. Thank you very much for your help.

I am so glad it helps. Happy coding :)


feat(system_launch): add group tag around include

Signed-off-by: Tomohito Ando<EMAIL_ADDRESS>PR Type

Improvement

Related Links

https://github.com/tier4/autoware_launch/pull/361

Description
This change was only applied to tier4/universe branch, so sometimes conflicts happened when doing sync-awf-latest.
I applied this change to awf-latest branch too.

https://github.com/tier4/autoware_launch/pull/361

Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@h-ohta Could you check this? :pray:


Raygun Cross platform error reporting updated

Raygun Cross platform error reporting Detailing Information added

Respected Dignatary  @RussKie please approve the Pull Request


AttributeError: 'NoneType' object has no attribute 'fileno'

Hello,
I'm trying to start some of our processes via  rez  using Epic Games' Switchboard Listener and there is not fileno defined in that context so I'm getting an exception:
AttributeError: 'NoneType' object has no attribute 'fileno'

https://github.com/AcademySoftwareFoundation/rez/blob/89686626c37e68391c61a5e7a55c9490984f933b/src/rez/utils/execution.py#L67
If fixed it on my end by adding yet another try...except AttributeError around the second  call to sys.__stdin__:
                try:
                    file_no = sys.__stdin__.fileno()
                except AttributeError:
                    file_no = None

Cheers,
Thomas

Thanks @KelSolaar ! I'm curious, what is sys.__stdin__ set to? It's clearly set to something from what I see right? Else that block woudn't be exeuted because the if statement checks if sys.__stdin__ is not None... Generally speaking, I think __stdin__ is expected to be a file like object, so maybe the issue could also be reported to Unreal devs? I think we have some Unreal devs in ASWF...

Yeah it is set to None, I can ask on UDN too.

https://udn.unrealengine.com/s/question/0D54z00008osjsBCAQ/calling-a-python-script-that-access-sysstdinfileno-from-switchboardlistener-raises-an-exception

Epic has patched Switchboard Listener: https://github.com/EpicGames/UnrealEngine/commit/8705ef5a4a889f4b3c7c02016bb0e5a1af932c4a
Let's close this one!


feat(listbox): add new component

after https://github.com/Vonage/vivid-3/pull/760 will be merged

listbox options, when are selected / checked, are styled by background color only. does it comply with rules? should we add another indicator?

wait for #750

merged

mouse click on an option should set focus on listbox. additional keyboard events like arrow navigation should continue navigating through other options but it doesn't

@yinonov @rachelbt If I return this , it fixes the problem.

@yinonov The refactor in fieldset broke the listbox. Can you take a look?


Add event url to create_application

Without an event url, the API returns a 400

@ChrisGuzman Merged, thanks :+1:


remove type:ignore from DataNode.storageType() method #417

Instead of
return NotImplementedError

I did
raise NotImplementedError

This is for issue #417

Please be patient with me. I'm on it

Yes of course , thanks for your help

We will merge it after PR #810 is merged. It should be done by today

Yay


⚠ Turnos 24x7 has degraded performance

In dd87b45, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 933 ms

Resolved: Turnos 24x7 performance has improved in b1170ab.


Unable to Run DataGeneration.ipynb

Hello, I'm attempting to run your example DataGeneration.ipynb script here: https://github.com/salesforce/PyRCA/blob/main/examples/DataGeneration.ipynb
Unfortunately, it throws an error on this line:
graph_matrix = DAGGen(DAGGenConfig).gen()
Error as follows:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[2], line 1
----> 1 graph_matrix = DAGGen(DAGGenConfig).gen() # create a DAG
      2 G = nx.DiGraph(graph_matrix)
      4 # transform node names from 0 to N-1 to X1 to XN

File [~/anaconda3/envs/pyrca/lib/python3.9/site-packages/pyrca/simulation/data_gen.py:70](https://file+.vscode-resource.vscode-cdn.net/home/suciokhan/rca/~/anaconda3/envs/pyrca/lib/python3.9/site-packages/pyrca/simulation/data_gen.py:70), in DAGGen.gen(self)
     68 # Make the graphs connected
     69 for cause in range(1, self.config.num_node):
---> 70     result = self.config.rng.integers(low=0, high=cause)
     71     matrix[cause, result] = 1
     72 num_edge -= self.config.num_node - 1

AttributeError: 'NoneType' object has no attribute 'integers'

I'm running this in an Anaconda environment with Python 3.9, and using version '1.0.1' for PyRCA.

Hi, there is an error in this notebook. You can try "graph_matrix = DAGGen(DAGGenConfig()).gen()". Thanks for raising this issue, and the problem has been fixed in the main branch.

Thanks for the help- confirming that fixed the problem.


Weird @media behaviour

Hey!
I'm trying to use typographic inside media query, but it seems that in this case the settings are not overridden correctly:
@media (max-width: 320px)
	$header-font 	= $geneva
	$body-font 		= $geneva
	$body-color		= orange
	typographic()

results in
@media (max-width: 320px) {
  html {
    font-family: 'Helvetica Neue', 'Helvetica', 'Arial', 'sans-serif';
    font-weight: 300;
    color: #666;
    font-size: 12px;
    line-height: 1.75em;
  }
//more code here

As you can see, the font and color remain default.

Hm. Not sure what's going on exactly. At first glance it seems like that should work.
Also, sorry I didn't get to this sooner.  :(

Sorry it's taken me so long to respond. I have my ups and downs with being a good maintainer.
I'm planning on migrating this project to PostCSS in the next month or so, and when I do, I'll probably rewrite it from scratch.

TBH, I'm not really sure what's going on, but as I said above, this is getting completely rewritten in PostCSS so I think it's safe to close this.


Add info about default configuration for macOS

Updated README.md to include information for default macOS configuration file: alacritty_macos.yml

Looks good to me, thanks! :)

@mesaugat You typoed 'respectively' in this as 'repsectively', BTW ;)

@apenney Feel free to open a PR. :)

@apenney Dear me. 😞

Here. https://github.com/jwilm/alacritty/pull/1131


fix parsing of PropType types in storybook Prop table tab

all data-ui + vx proptypes show as other in the storybook:

this likely has to do with prop type functions being stripped during babel parsing / some build issue. may need to restructure the repo to fix it. may not be fixable for @vx issues

Going to punt on this until Storybook updates are out!


Documentation request

I am a little bit annoyed that I am failing to find any documentation on the data map that is supported in each template type.
I'm running into this issue due to me trying to add a simple bit of data to my templates (all of them) which I would ideally be something akin to:
source: {resource.source}

OR
source:
    book: {resource.source.book}
    page: {resource.source.page}

(And in some cases things have several sources so a for loop or some other mechanism to have each of these version within the same space, would be nice to have)
but now it prints the full book name + the page number. I would just like to break that information out so I can use other obsidian features to help sort things.
I initially assumed I should look at the JSON data, as in the source I couldn't find anything that builds this combined data. When I looked into the JSON data the page numbers are split away from the books within the sourcing information...
Or am I doing something silly/misunderstanding?

I do track sources (where there are several). I don't currently expose those for you to use in templates. Not because I can't, but because no one has asked for it.
If you're making a request to have book/page references accessible for templates, we can start there. Remember I do this in my spare time. It is a lot, it can be fussy, and I prioritized making functional content that renders well and is readable over making extensive documentation for something that is somewhat fluid. Where there are variations in how things are rendered, I try to provide an example with the alternate usage.

I'm happy to take PRs for contributions to the examples directory. ;)
Getting source/page pairs out is involved, I'm working on it. In general, things happen in stages:

EVERYTHING is "parsed". Directories are scanned, json files are loosely parsed, with known top-level types indexed. If you run the CLI with the --index option, you can see the keys for all discovered and/or constructed nodes, and a second index for the smaller set that has been "allowed". Filtering can happen because the source was excluded, or because one node (say, a beastie), was marked as a reprint of another, that is already included. I think the full index also contains a map of keys to their replacement (the node that should be used instead). The list of sources

A second phase converts the included nodes into notes. This is when the contents of each node are parsed in detail, recursively. There is roughly one Java class per emitted type that does the conversion (Json2*). The result is attached to one of the classes in the qute package (Qute*). I don't do full getters/setters here. Any public field is implicitly available directly to a template (resource.fieldName). Any getter on a Qute* object is also available to the template in the usual Java bean conversion sense: getData() would be available as resource.data. In some cases, I have additional inner classes that provide a toString() method. You can then either reference the field itself (which will implicitly call the toString() method), or you could reference the inner fields.

Note: I did the 5e side first, and improved some things when I started the pf2e work, so the two sides are not exactly the same, I'm reconciling things as I go to bring them closer together.

I have an idea. Give me a bit.

If you would like we could link up over the weekend to see how collaboration is best achieved. Note that I am not too familiar with Java. I'm mainly over in C, C++, and C#. (also some TypeScript when i did web-dev)

I have a doclet.. and now a lot of fixups. ;)


Fixing implicit any typing issues

Small fix for some implicit any type compile errors with typescript. Can work around it by setting "noImplicitAny": false in tsconfig.json but I prefer stricter settings.
Fixes the following errors:
node_modules/node-nats-streaming/index.d.ts(74,5): error TS7010: 'ack', which lacks return-type annotation, implicitly has an 'any' return type.
node_modules/node-nats-streaming/index.d.ts(87,5): error TS7010: 'unsubscribe', which lacks return-type annotation, implicitly has an 'any' return type.
node_modules/node-nats-streaming/index.d.ts(96,5): error TS7010: 'close', which lacks return-type annotation, implicitly has an 'any' return type.
node_modules/node-nats-streaming/index.d.ts(113,2): error TS7010: 'close', which lacks return-type annotation, implicitly has an 'any' return type.

Version: 0.0.25
Typescript version: 2.3.4

Coverage remained the same at 96.0% when pulling 4e4236297733a0a646d76e2fcbf11f5a8773af96 on Qwerios:fix-typings-implicit-any into eef8995a7c5c2c6b0874d06144f169a28ad20cea on nats-io:master.

Coverage remained the same at 96.0% when pulling 4e4236297733a0a646d76e2fcbf11f5a8773af96 on Qwerios:fix-typings-implicit-any into eef8995a7c5c2c6b0874d06144f169a28ad20cea on nats-io:master.

My fix has no running code only typings so I have no idea why that one travis test fails on node 6...

Is there any chance of getting this merged? It's a very basic problem and fix IMHO

Sorry for dropping the ball. I missed that this PR was open.

Thank you very much!


issues/854: add Bruno tests

DelegationCheck is performed by app which is not authorized to delegate any instance access rights response.
Related Issue(s)

#854

Developer/Reviewer Checklist

[ ] Your code builds clean without any errors or warnings
[ ] No changes to config/appsettings or environment variables created in separate linked PR
[ ] Manual testing done (required)
[ ] Relevant integration test added (required for functional changes)
[ ] Relevant automated test added (required for functional changes)
[ ] All integration tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Ser ellers at Remi også har PR på denne:
https://github.com/Altinn/altinn-access-management/pull/861
så her har det ikke blitt kommunisert godt nok


exported Notes lose formatting

Exported notes contain only the plain text content of the notes, losing any
rich text formatting.  The formatting information seems to be stored separately
from the text that it applies to.  It's not obviously in html or rtf or any other
common rich text format.  It would be great if this formatting information could
be extracted and applied to the text, creating an html or markdown or similar
rich text document.  The Exporter app is able to create a markdown version
of the text.

On older versions of the notes app, the database contains html, which if available is provided by the notes plugin. However, newer versions have an unknown format where the data and formatting are stored separately. I have described the basic format here.
Their version of the markup is yet unknown as well as a low priority item for research right now.

I'm guessing it's an NSAttributedString, but I don't know enough about Objective-C and especially its serialization format to know how to interpret the data.

I will. Thank you @bshannon!


[BUG] Longhorn won't fail all replicas if there is no valid backend during the engine starting stage

Describe the bug
This issue is found during the #1253 fixing.
The volume gets stuck in the detach-reattach loop if there is no valid backend during the engine starting stage.
To Reproduce
Steps to reproduce the behavior:

Create and attach a volume.
Create some snapshots for the volume.
Manually modifying/invalidating one snapshot/head metafile for all replicas.
Detach then reattach the volume.

Expected behavior
The volume should fail to attach and become Faulted state.
Environment:

Longhorn version: v0.8.1

Additional context

If all replicas are invalid during the engine starting stage, the engine monitor is not launched since the engine instance is still starting. The engine process has no way to tell the manager that all replicas should be mode ERR and directly errors out. The longhorn manager considers the replicas as valid but the engine dies unexpectedly, then keeps trying auto reattachment. Finally, the volume gets stuck in the detach-reattach loop.
Even if all replica can be marked as failed, e.g., manually marking all replicas as failed in the volume controller if engine.Status.CurrentState == "Error" && !engine.Status.Started, the auto-salvage feature will try to reuse all replicas. Then the volume still loops in detach and reattach. This is another issue tracked in #1342.
The original discussion is in #1253.

Move this to the next release.

We might want to follow the steps to repro the issue also as mentioned https://github.com/longhorn/longhorn/issues/1251.

@roger-ryao could you help check if this issue is still valid? Thanks.
cc @longhorn/qa

Hi @innobead :
This issue is still valid on the master-head.
To Reproduce
Steps to reproduce the behavior:
Scenario 1

Create and attach a volume.
Create three snapshots for the volume.
Manually modify volume-head-003.img.meta on all nodes
replace the Parent with the invalid image file name
Detach then reattach the volume.
Then the volume still loops in detach and reattach

Scenario 2

Create and attach a volume.
Create three snapshots for the volume.
Remove one of volume-snap-XXX.img.meta & volume-snap-XXX.img on all nodes.
Then the volume still loops in detach and reattach

Thanks @roger-ryao .
cc @longhorn/qa this is a good example for resilience.

cc @mantissahz


Translating all API from Zint

Dear My frinend:
Thanks for  you opening you source code. It solve  my  problem that from zero to one.  But its results were not ideal. So I have a problem that do you have translate all API from  zint.
I had a test in Ubuntu.

If you select this checkbox reader init the barcode bcomes different.
So I don't find the API or options in your packpage.
Looking forward to hearing from you soon

I have solved the problem.  I bulid a zint.dll .


Enhance compose box with buttons for emoji/mentions/uploads

We should think about adding buttons to pop up emoji/mention autocomplete (and file upload when we add that).  I would investigate whether there's an open source library that we can borrow that would make it easy to put this into a custom keyboard or something.

I'm going to work on this issue.

so this issue has been worked on separately

we have @-mention autocomplete feature merged
for file uploads #398
emoji picker #248


Space after colon in fielded keyword searches are leading to strange results

Tried with subtitle and it generated empty records; number of digitized works is off (it returns 4,999 records and only 4,948 are shown with dictionaries and word lists excluded).  Tried with author and returned irrelevant records.

@mnaydan the team discussed this one when we estimated last week, and we couldn't think of anything that could be done. What you're seeing is the default behavior of the edismax query parser, and as we've learned it's pretty error tolerant. We're concerned that by trying to work around this problem we're more likely to introduce errors.
I'd like to close this with a "won't fix" tag but wanted to give you a chance to respond.

@rlskoeser trust you guys, sounds fine to me. The correct syntax is included on the how to search section ("Enter the lower-case field type, a colon, and your search term without any spaces after the colon") so if people get weird results they'll hopefully look there.