Transcription failed: The recordings URI contains invalid data.

Hello,
I am using Batch Transcription api with python and getting error 'Transcription failed: The recordings URI contains invalid data.'. My files are on wav format and it is strange that I am getting this error because I used these same files with this api before and it worked properly several times. Can you please help?
I have already read the releated closed issues but not helped. ( https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/399 )
Thanks,
(You can ping me on teams, t-hkalayci )

Could you please share the transcription id of failed transcriptions and the approximate time and regions? Thanks!

Thank you for your fast response. Here they are:
05/28/2021 03:00:26 PM Turkey Standard Time Starting transcription client...
05/28/2021 03:00:27 PM Turkey Standard Time Created new transcription with id 'e3fac6d4-5436-45ed-9e4e-5a6ceba00ac7' in region westeurope
05/28/2021 03:00:27 PM Turkey Standard Time Checking status.
05/28/2021 03:00:32 PM Turkey Standard Time Transcriptions status: Failed
05/28/2021 03:00:32 PM Turkey Standard Time Transcription failed: The recordings URI contains invalid data.

It seems that your audio is stereo and you asked for diarization in the request. Diarization only works for mono audio, as described here. It might have worked in the past due to a bug in our system which just ignores diarization for stereo audio. Now an explicit error is returned users, since diarization cannot be performed on stereo audio. You either need to transform stereo audio into 2 mono audio files or disable diarization if it is not needed.
Btw. You can find detailed error message in the report.json which is provided as a part of returned result files. You can find the link to report.json via GET files API.
Thanks.

Worked! Thank you so much for the explanation!


Updated KeyVaultConfiguration

Updated : key-vault-configuration.md, key-vault-configuration\samples\3.x\SampleApp\SampleApp

Microsoft.Extensions.Configuration.AzureKeyVault to Azure.Extensions.AspNetCore.Configuration.Secrets.
KeyVaultClient  to SecretClient.

There is no new API reference Documentation about AddAzureKeyVault(), so its link is not added in this PR.
@pakrym, @jongio please help review

@FrankieTF - Can you please comment on why the large section of the article was removed?  Is it no longer needed with the new libs?

@pakrym - Can you please review?

Can we separate the package update related stuff and the cleanup please?

AddAzureKeyVault does not accept implementation of IKeyVaultSecretManager any more, this is no longer needed

There is one https://github.com/Azure/azure-sdk-for-net/blob/e51946a4a7fcff55515ecec58c30e30a9ac423ff/sdk/extensions/Azure.Extensions.AspNetCore.Configuration.Secrets/api/Azure.Extensions.AspNetCore.Configuration.Secrets.netstandard2.0.cs#L21

Can we separate the package update related stuff and the cleanup please?

AddAzureKeyVault does not accept implementation of IKeyVaultSecretManager any more, this is no longer needed

There is one https://github.com/Azure/azure-sdk-for-net/blob/e51946a4a7fcff55515ecec58c30e30a9ac423ff/sdk/extensions/Azure.Extensions.AspNetCore.Configuration.Secrets/api/Azure.Extensions.AspNetCore.Configuration.Secrets.netstandard2.0.cs#L21

Yes, we will separate the package update related stuff and the cleanup next time.
In mentioned link, AddAzureKeyVault accept Azure.Extensions.AspNetCore.Configuration.Secrets.KeyVaultSecretManager not Microsoft.Extensions.Configuration.AzureKeyVault.IKeyVaultSecretManager

@FrankieTF  can you separate the package update related stuff and the cleanup  in a new PR next week?
@pakrym  if so, are you OK with merging this now?

Is there a reason we can't get this PR fixed and merge it without extra removals?


Update helm chart to make it stable and safer

WHAT
This pull request updates helm chart to make it stable and safer.

Use jobs for hooks instead of pods
Use helm.sh/hook-delete-policy annotation properly

WHY
To solve the following issues:

It works sometimes, doesn't other times. There is some timing issues when installing and deleting probably due to using pods for hooks.
It creates service account kritis-preinstall-serviceaccount which has cluster-admin role, it should be removed as soon as installation done.

https://github.com/grafeas/kritis/blob/15fa1a046e22870f0d8059bac48dfceb8cd49828/kritis-charts/templates/preinstall/clusterrolebinding.yaml#L16

@dragon3
This PR does not delete cluster-admin Service Account during PostInstall. Will you be doing this in another PR?

@vbanthia

This PR does not delete cluster-admin Service Account during PostInstall. Will you be doing this in another PR?

This annotation will delete those resources:
"helm.sh/hook-delete-policy": "before-hook-creation,hook-succeeded"

The documentation is here:
https://github.com/helm/helm/blob/master/docs/charts_hooks.md#hook-resources-are-not-managed-with-corresponding-releases

This annotation will delete those resources:

Got it. This PR LGTM.

Thank you for the review.
I'm going to merge it. (use squash & merge as well)


chore(csp): add Adobe Target Script and Salesloft Script

Issue
Fixes - https://github.com/hlxsites/merative2/issues/289
Description
Changed

This PR updates both CSPs on Franklin to allow for *.tt.omtrdc.net and *.salesloft.com
See screenshots for the current issues.

Design Specs

Figma Link - N/A

Test URLs

Before (Changes from main): https://main--merative2--hlxsites.hlx.page/
After (Changes from this PR): https://289-chore-update-csp--merative2--proeung.hlx.page

Testing Instruction

No testing instruction is needed.

@keith-kaplan Done. Please check the latest commit.

@proeung  this looked like it fixed the issue. I'm going to submit an Adobe Support ticket to just ensure we have all things setup in Target properly. There are a few other errors I'm seeing in the console when editing and want to make sure I'm not missing anything.

@keith-kaplan Sounds good! Also, feel free to capture those errors that you see in the console in a ticket so that we can help debug where the issue is coming from. In the meantime, I'll go ahead and merge this PR down.


Parse Error

hello, when I go to run an android build it builds to the device but "problem parsing the package"

fixed thanks!


M5Stack CoreS3 IDF 5.1.1 not compiling

When using the M5Stack CoreS3 With IDF 5.1.1 a compile error pops up.
Line 809 of src/lgfx/v1/platforms/esp32/common.cpp is as follows:
 #if (ESP_IDF_VERSION >= ESP_IDF_VERSION_VAL(5, 0, 2) && ESP_IDF_VERSION < ESP_IDF_VERSION_VAL(5, 1, 0))
      (&dev->comd[0])[index].val = cmd_val;
 #else
      (&dev->comd0)[index].val = cmd_val;
 #endif

Which is checking for idf version 5, 0, 2 and higher and lower than 5.1.0. This does not work on
Changing it to
 #if (ESP_IDF_VERSION >= ESP_IDF_VERSION_VAL(5, 0, 2) && ESP_IDF_VERSION <= ESP_IDF_VERSION_VAL(5, 1, 1))
      (&dev->comd[0])[index].val = cmd_val;
 #else
      (&dev->comd0)[index].val = cmd_val;
 #endif

fixes the issue
The &dev->comd[0] is correct here

@oedze
Thanks for the report !
I have fixed the develop branch, please try it and see.

@oedze Thanks for the report ! I have fixed the develop branch, please try it and see.

It works, thanks!


SNI certificates not functioning as expected

Describe the bug
Currently working with @kflynn on this issue via Slack. Defining TLS certificates using TLSContext does not seem to be working correctly.
To Reproduce
Steps to reproduce the behavior:
I removed any trace of the default 'ambassador-certs' secret
I set up a TLSContext as follows,
          ---
          apiVersion: ambassador/v1
          kind: TLSContext
          name: mytls
          ambassador_id: external-gateway
          hosts:
            - "stage01.mydomain.com"
          secret: my-certs

I set up a mapping as follows,
          ---
          apiVersion: ambassador/v1
          kind:  Mapping
          name:  campus-tenant-mapping
          host:  "stage01.mydomain.com"
          ambassador_id: external-gateway
          prefix: /
          service: web-application.frontend:80
          timeout_ms: 5000

I have the tls module also set up in it's most basic form to provide HTTP>HTTPS redirection as follows,
         ---
          apiVersion: ambassador/v1
          kind: Module
          name: tls
          ambassador_id: external-gateway
          config:
            server:
              redirect_cleartext_from: 8080

We are also running an AuthService and Tracing module, however I have disabled these to aid the fault finding.
Expected behavior
I would expect the certificate to be served by Ambassador however this does not happen. In Chrome I see a ERR_CONNECTION_RESET and from the OpenSSL command line I see the following,
connected(00000005)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 327 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)

If I change the TLSContext to use a wildcard. Everything is fine, but obviously I can only serve a single certificate.
          ---
          apiVersion: ambassador/v1
          kind: TLSContext
          name: mytls
          ambassador_id: external-gateway
          hosts:
            - "*"
          secret: my-certs

Versions (please complete the following information):

Ambassador: [e.g. 0.32.1] 0.75 (Also tried on 0.76)
Kubernetes environment [e.g. Minikube, bare metal, Google Kubernetes Engine]
Version [e.g. 1.8.1] Amazon EKS v1.12

Additional context
Add any other context about the problem here.

I am seeing the same, however I just noticed if I disable the tls module so that I do not get redirect_cleartext_from it appears to work properly using a non-wildcard TLSContext.

This issue is happening for me as well.
I am trying to serve three distinct domains using ambassador v0.76.0.
---
apiVersion: getambassador.io/v1
kind: TLSContext
name: aoc-tls
hosts:
- "api.realdomain.com"
secret: aoc-cert
ambassador_id: {{ $ambassadorId }}
min_tls_version: v1.2
max_tls_version: v1.3
alpn_protocols: h2[, http/1.1]
---
apiVersion: getambassador.io/v1
kind: TLSContext
name: short-tls
hosts:
- "domain.pub"
secret: short-cert
ambassador_id: {{ $ambassadorId }}
min_tls_version: v1.2
max_tls_version: v1.3
alpn_protocols: h2[, http/1.1]
---
apiVersion: getambassador.io/v1
kind: TLSContext
name: aoc-tls-old
hosts:
- "api.olddomain.com"
secret: aoc-tls-old
ambassador_id: {{ $ambassadorId }}
min_tls_version: v1.2
max_tls_version: v1.3
alpn_protocols: h2[, http/1.1]
---
apiVersion: getambassador.io/v1
kind: Module
name: tls
ambassador_id: {{ $ambassadorId }}
config:
  server:
    redirect_cleartext_from: 8080

the "ambassador-secret" cert in the namespace is for api.realdomain.com
Any calls for api.realdomain.com work correctly
But I try to call something in domain.pub, the request is not routed correctly, and also the certificate is for  api.realdomain.com

After playing with a bunch of different things today I decided to move to an NLB over the classic ELB and everything appears to be working now, including a default selfsigned cert for all hosts, and then per domain real certificates and even cleartext redirection.

So this is a bug around SNI and host_regex, and I think the simple way forward is this:

make the host field in a Mapping support globs with a leading *
make the SNI host match be a glob match

or in more lay terms, make things like *.example.com in the host field of a Mapping do what you would expect them to. Only leading * will be supported. You won't be able to do e.g. foo.*.example.com (not that I've ever personally run across anything that does support that).
SNI + host regex will still be problematic, but then host-regex should be largely unnecessary if we support glob patterns.
(Note also that I'm not too concerned about breaking people currently using glob patterns in the host field, because * is not legal in a DNS name, so there's no real way it could have worked.)

I'm not using host_regex.
Some more info:
I have three domains: ["api.olddomain.com", "api.realdomain.com", "domain.pub"]
I have certificates for each of these domains: ["files-cert", "a1-cert", "short-cert"], I also have a secret called "ambassador-certs", which is just a copy of "a1-cert"
Here is my annotation on my ambassador service:
metadata:
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: getambassador.io/v1
      kind:  Module
      name:  ambassador
      ambassador_id: analytics-qa
      config:
        service_port: 8443
        diagnostics:
          enabled: true
        cors:
          origins: '*'
          methods: 'GET, POST, DELETE, PUT, OPTIONS'
          headers:
          - authorization
          - content-type
          exposed_headers: ''
          max_age: '1728000'
        load_balancer:
          policy: ring_hash
          source_ip: true
      ---
      apiVersion: getambassador.io/v1
      kind: TLSContext
      name: aoc-tls
      hosts:
      - "api.qa.realdomain.com"
      secret: a1-cert
      ambassador_id: analytics-qa
      min_tls_version: v1.2
      max_tls_version: v1.3
      alpn_protocols: h2[, http/1.1]
      ---
      apiVersion: getambassador.io/v1
      kind: TLSContext
      name: short-tls
      hosts:
      - "domain.pub"
      secret: short-cert
      ambassador_id: analytics-qa
      min_tls_version: v1.2
      max_tls_version: v1.3
      alpn_protocols: h2[, http/1.1]
      ---
      apiVersion: getambassador.io/v1
      kind: TLSContext
      name: files-tls
      hosts:
      - "api.qa.olddomain.com"
      secret: files-cert
      ambassador_id: analytics-qa
      min_tls_version: v1.2
      max_tls_version: v1.3
      alpn_protocols: h2[, http/1.1]
      ---
      apiVersion: getambassador.io/v1
      kind: Module
      name: tls
      ambassador_id: analytics-qa
      config:
        server:
          redirect_cleartext_from: 8080

Here are the mappings I have for "api.realdomain.com" and "api.olddomain.com"
metadata:
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: Mapping
      name: analytics-qa-f4-back-end-puma-mapping-0
      prefix: /
      host: api.qa.realdomain.com
      service: analytics-qa-f4-back-end-puma.analytics-qa
      rewrite: ""
      ambassador_id: analytics-qa
      tls: aoc-tls
      bypass_auth: true
      timeout_ms: 90000
      ---
      apiVersion: ambassador/v1
      kind: Mapping
      name: analytics-qa-f4-back-end-puma-mapping-1
      prefix: /
      host: api.qa.olddomain.com
      service: analytics-qa-f4-back-end-puma.analytics-qa
      rewrite: ""
      ambassador_id: analytics-qa
      tls: files-tls
      bypass_auth: true
      timeout_ms: 90000

here is my mapping for "domain.pub"
metadata:
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: Mapping
      name: analytics-qa-f4-back-end-short-f4-back-end-short-mapping-0
      prefix: /
      service: http://analytics-qa-f4-back-end-short.analytics-qa
      rewrite: ""
      host: domain.pub
      ambassador_id: analytics-qa
      bypass_auth: true

If I look in the admin view it looks like like everything is good to go:
{
    "match": {
        "case_sensitive": true,
        "headers": [
            {
                "exact_match": "api.qa.olddomain.com",
                "name": ":authority"
            }
        ],
        "prefix": "/",
        "runtime_fraction": {
            "default_value": {
                "denominator": "HUNDRED",
                "numerator": 100
            },
            "runtime_key": "routing.traffic_shift.cluster_analytics_qa_f4_back_end_puma_an-1"
        }
    },
    "per_filter_config": {
        "envoy.ext_authz": {
            "disabled": true
        }
    },
    "route": {
        "cluster": "cluster_analytics_qa_f4_back_end_puma_an-1",
        "cors": {
            "allow_headers": "authorization, content-type",
            "allow_methods": "GET, POST, DELETE, PUT, OPTIONS",
            "allow_origin": [
                "*"
            ],
            "enabled": true,
            "max_age": "1728000"
        },
        "hash_policy": [
            {
                "connection_properties": {
                    "source_ip": true
                }
            }
        ],
        "priority": null,
        "timeout": "90.000s"
    }
}

{
    "match": {
        "case_sensitive": true,
        "headers": [
            {
                "exact_match": "api.qa.realdomain.com",
                "name": ":authority"
            }
        ],
        "prefix": "/",
        "runtime_fraction": {
            "default_value": {
                "denominator": "HUNDRED",
                "numerator": 100
            },
            "runtime_key": "routing.traffic_shift.cluster_analytics_qa_f4_back_end_puma_an-0"
        }
    },
    "per_filter_config": {
        "envoy.ext_authz": {
            "disabled": true
        }
    },
    "route": {
        "cluster": "cluster_analytics_qa_f4_back_end_puma_an-0",
        "cors": {
            "allow_headers": "authorization, content-type",
            "allow_methods": "GET, POST, DELETE, PUT, OPTIONS",
            "allow_origin": [
                "*"
            ],
            "enabled": true,
            "max_age": "1728000"
        },
        "hash_policy": [
            {
                "connection_properties": {
                    "source_ip": true
                }
            }
        ],
        "priority": null,
        "timeout": "90.000s"
    }
}

{
    "match": {
        "case_sensitive": true,
        "headers": [
            {
                "exact_match": "domain.pub",
                "name": ":authority"
            }
        ],
        "prefix": "/",
        "runtime_fraction": {
            "default_value": {
                "denominator": "HUNDRED",
                "numerator": 100
            },
            "runtime_key": "routing.traffic_shift.cluster_http___analytics_qa_f4_back_end_-0"
        }
    },
    "per_filter_config": {
        "envoy.ext_authz": {
            "disabled": true
        }
    },
    "route": {
        "cluster": "cluster_http___analytics_qa_f4_back_end_-0",
        "cors": {
            "allow_headers": "authorization, content-type",
            "allow_methods": "GET, POST, DELETE, PUT, OPTIONS",
            "allow_origin": [
                "*"
            ],
            "enabled": true,
            "max_age": "1728000"
        },
        "hash_policy": [
            {
                "connection_properties": {
                    "source_ip": true
                }
            }
        ],
        "priority": null,
        "timeout": "3.000s"
    }
}

but routing just doesn't seem to work at all
curl https://x.x.x.x/api/v1/keys -H "Host: api.qa.olddomain.com" -k -v
*   Trying x.x.x.x...
* TCP_NODELAY set
* Connected to x.x.x.x (x.x.x.x) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=CA; L=Emeryville; O=Aspera Inc.; OU=Aspera_IT; CN=*.qa.realdomain.com
*  start date: Mar 13 00:00:00 2018 GMT
*  expire date: Mar 20 12:00:00 2020 GMT
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
*  SSL certificate verify ok.
> GET /api/v1/keys HTTP/1.1
> Host: api.qa.olddomain.com
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< date: Fri, 13 Sep 2019 21:47:44 GMT
< server: envoy
< content-length: 0
<
* Connection #0 to host x.x.x.x left intact

curl https://<IP_ADDRESS>/api/v1/keys -H "Host: api.qa.realdomain.com" -k -v
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=CA; L=Emeryville; O=Aspera Inc.; OU=Aspera_IT; CN=*.qa.realdomain.com
*  start date: Mar 13 00:00:00 2018 GMT
*  expire date: Mar 20 12:00:00 2020 GMT
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
*  SSL certificate verify ok.
> GET /api/v1/keys HTTP/1.1
> Host: api.qa.realdomain.com
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< date: Fri, 13 Sep 2019 21:52:13 GMT
< server: envoy
< content-length: 0
<
* Connection #0 to host <IP_ADDRESS> left intact

$ curl https://x.x.x.x/api/v1/keys -H "Host: domain.pub" -k -v
*   Trying x.x.x.x...
* TCP_NODELAY set
* Connected to x.x.x.x (x.x.x.x) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=CA; L=Emeryville; O=Aspera Inc.; OU=Aspera_IT; CN=*.qa.realdomain.com
*  start date: Mar 13 00:00:00 2018 GMT
*  expire date: Mar 20 12:00:00 2020 GMT
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
*  SSL certificate verify ok.
> GET /api/v1/keys HTTP/1.1
> Host: domain.pub
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< date: Fri, 13 Sep 2019 21:54:20 GMT
< server: envoy
< content-length: 0
<
* Connection #0 to host x.x.x.x left intact

logs aren't helpful
2019-09-13 21:50:38 diagd 0.76.0 [P248TAmbassadorEventWatcher] INFO: Scout reports {"latest_version": "0.78.0", "application": "ambassador", "cached": true, "timestamp":<PHONE_NUMBER>.584329}
2019-09-13 21:50:38 diagd 0.76.0 [P248TAmbassadorEventWatcher] INFO: Scout notices: [{"level": "DEBUG", "message": "Returning cached result"}, {"level": "INFO", "message": "Upgrade available! to Ambassador version 0.78.0"}]
time="2019-09-13T21:50:38Z" level=info msg="Loaded file /ambassador/envoy/envoy.json"
time="2019-09-13T21:50:38Z" level=info msg="Pushing snapshot v4"
ACCESS [2019-09-13T21:50:50.747Z] "GET /api/v1/keys HTTP/1.1" 404 NR 0 0 0 - "<IP_ADDRESS>" "curl/7.54.0" "472dd1ed-5729-4992-8683-f6f6e9049c19" "api.qa.realdomain.com" "-"
ACCESS [2019-09-13T21:50:59.511Z] "GET /api/v1/keys HTTP/1.1" 404 NR 0 0 0 - "<IP_ADDRESS>" "curl/7.54.0" "215787d0-5048-4a1d-8377-af806f18fd1c" "api.qa.olddomain.com" "-"
ACCESS [2019-09-13T21:56:16.457Z] "GET /api/v1/keys HTTP/1.1" 404 NR 0 0 0 - "<IP_ADDRESS>" "curl/7.54.0" "5d08d7be-c25c-448b-bd90-6404015f9778" "domain.pub" "-"

Really, it seem that routing doesn't work at all if you define a service to use a specific host.

We think we're running into this issue https://github.com/envoyproxy/envoy/issues/3411, because ambassador renders an envoy.json with an empty filter_chain_match
                "filter_chains": [
                    {
                        "filter_chain_match": {},
...snip
                    {
                        "filter_chain_match": {
                            "server_names": [
                                "api.qa.realdomain.com"
                            ]
                        },
...snip
                    {
                        "filter_chain_match": {
                            "server_names": [
                                "domain.pub"
                            ]
                        },
...etc```

Any updates on this? It's still happening.


Rancher Monitoring Grafana variable query fails if two pods with the same name exist in different namespaces

Rancher Server Setup

Rancher version: v2.6.3
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): v1.21.8 on RKE1

Information about the Cluster

Kubernetes version: v1.21.8
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Custom

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin or Cluster Owner

Describe the bug

After installing the rancher-monitoring app via "Apps & Marketplace" the following Grafana template error shows in the Rancher UI if a user tries to view Pod related metrics:

The error in text form (redacted):
Templating
Template variable service failed "found duplicate series for the match group {pod=\"elasticsearch-master-0\"} on the left hand-side of the operation: [{__name__=\"kube_pod_info\", container=\"kube-state-metrics\", created_by_kind=\"StatefulSet\", created_by_name=\"elasticsearch-master\", endpoint=\"http\", host_ip=\"XXX\", host_network=\"false\", instance=\"XXX\", job=\"kube-state-metrics\", namespace=\"namespace1\", node=\"XXX\", pod=\"elasticsearch-master-0\", pod_ip=\"XXX\", service=\"rancher-monitoring-kube-state-metrics\", uid=\"79636ed3-43bc-4d5a-b095-577b340259c3\"}, {__name__=\"kube_pod_info\", container=\"kube-state-metrics\", created_by_kind=\"StatefulSet\", created_by_name=\"elasticsearch-master\", endpoint=\"http\", host_ip=\"XXX\", host_network=\"false\", instance=\"XXX\", job=\"kube-state-metrics\", namespace=\"namespace2\", node=\"XXX\", pod=\"elasticsearch-master-0\", pod_ip=\"XXX\", service=\"rancher-monitoring-kube-state-metrics\", uid=\"57a48079-51ed-46cd-8732-8575784c8343\"}];many-to-many matching not allowed: matching labels must be unique on one side"

The same thing happens (of cause) if a users tries to access the corresponding Grafana dashboard directly.
Using the namespace Variable query from the Rancher / Workload (Pods) Grafana dashboard this error can be reproduced on Prometheus directly:
kube_pod_info{namespace!=""} * on(pod) group_right(namespace, created_by_kind, created_by_name) count({__name__=~"container_.*|windows_container_.*", pod!=""}) by (pod)

The problem in our case is cause by two Pods in different namespaces having the same name.
To Reproduce

install the rancher-monitoring app (v100.1.0+up19.0.3)
create two namespaces
create two pods with the same name in the previously created namespaces
access Metrics view on Pod level in the Rancher UI or the Rancher / Workload (Pods) Grafana dashboard

Result
User is presented with error message and no metrics are displayed.
Expected Result

User should be presented with proper pod metrics.
Screenshots
see above
Additional context
One suggestion that should work from my perspective is the replacement of the following Grafana Variable query:
kube_pod_info{namespace!=""} * on(pod) group_right(namespace, created_by_kind, created_by_name) count({__name__=~"container_.*|windows_container_.*", pod!=""}) by (pod)

with the much simpler:
group (kube_pod_info{namespace!=""}) by (namespace)

As additional results from the original query are not used for the variable generation.
The query under suspect seems to have caused performance issues in the past as well: !36107

Just stumbled across https://github.com/rancher/charts/issues/1848
Would like to let the Rancher maintainers decide where this bug report should go.

Reference to query in rancher-monitoring Chart:
https://github.com/rancher/charts/blob/dev-v2.6/charts/rancher-monitoring/100.1.0%2Bup19.0.3/files/rancher/workloads/rancher-workload-pods.json#L571

Opened PR on the rancher/charts repo to address this issue.


Preview doesn't reflect changes made to the order of Orderable items.

I'm chugging along through the "Displaying Fields with the Editing API" page in the docs, and absolutely loving the power that Wagtail offers. But I've run into a bit of an annoying issue, which appears to be a bug in either wagtail or django-modelcluster.
When I click the Preview button while editing a Page-derived model attached to an Orderable, the order the items are displayed in is always the order in which the Page was saved (or, in the case of a page that hasn't been saved yet, the order in which the items were added to the editor), rather than the order that's currently displayed in the editor form (after clicking the Up and Down arrows to change their order).
How to replicate this bug (see bold note below for easier testing):
In wagtaildemo, add this to models.py:
# The abstract model for related links, complete with panels
class RelatedString(models.Model):
    string = models.CharField(max_length=255)

    panels = [
        FieldPanel('string'),
    ]

    class Meta:
        abstract = True

class TestPageRelatedStrings(Orderable, RelatedString):
    page = ParentalKey('demo.TestPage', related_name='related_strings')

class TestPage(Page):
    body = RichTextField(blank=True)

TestPage.content_panels = [
    FieldPanel('title', classname="full title"),
    InlinePanel(TestPage, 'related_strings', label='Related Strings'),
]

Then add test_page.html to your templates, with these contents:
{% extends "demo/base.html" %}

{% block content %}
    {% include "demo/includes/body.html" with body=self.body only %}

    {% if self.related_strings %}

Related Strings

      {% for related_string in self.related_strings.all %}

        {{ related_string.string }}

      {% endfor %}
    {% endif %}
{% endblock %}

Migrate your site, then add a new Test Page from the admin interface. Set the page's title, then add "String 1" and "String 2" to the Related Strings panel.
Now click "Preview", and you'll see String 1 and String 2 in numerical order. Then, close the Preview tab and move String 2 above String 1 in the editor, and click Preview again.
The bug is that String 1 will still appear above String 2, even though it's been moved below it in the editor.
Note: I realized while writing this up that you can trigger the bug using just wagtaildemo's Standard Index Page content type. Simply edit the page titled "Standard index" under wagtaildemo's "Home page", as its Related Links field has all the setup needed to trigger this bug.
Considering that django-modelcluster's README specifically promotes its ability to "render a preview of the data the user has just submitted, prior to saving", this is pretty significant problem.
I'm not sure if this is a bug in wagtail or a bug in django-modelcluster, though. I'll post a link to this issue on that module's queue.

We're experiencing this too. Related to #222?

Have confirmed that this is a modelcluster bug, now fixed in https://github.com/torchbox/django-modelcluster/pull/16 - will get that merged and a new version of modelcluster released ASAP.

That's great to hear!


Unable to create com.apple.tccd sandbox extension - iOS

I have some simple code where I am trying to get the camera going
import { Plugins } from '@capacitor/core'
import '@capacitor-community/camera-preview'
const { CameraPreview } = Plugins
...
CameraPreview.start({ position: 'rear', parent: 'cameraPreview' })
On starting of the camera it gives me the error
Could not create a 'com.apple.tccd' sandbox extension
2021-09-28 22:32:17.522890+0930 App[15545:4379269] [WebRTC] Unable to create com.apple.tccd sandbox extension
iPhone 13 mini
iOS 15
Xcode 13
Has anyone seen this?

Fixed it. I had an error and I think it was trying to load the web version on iOS


Create dependabot.yml

I am proposing to include dependabot to improve docker image and github action to keep up to date.

Good idea. Haven't really used dependabot so far.
package-ecosystem: "github-actions" checks the deploy workflow file for updates I guess?
When would package-ecosystem: "docker" trigger?
Also it'd be nice to have npm and go dependencies checked as well.

When would package-ecosystem: "docker" trigger?

It would be trigger when alpine:3 from the Dockerfile gets update on DockerHub.  In this case, 24 days ago.
This allows to re-run pipeline when the upstream image gets updated.

Also it'd be nice to have npm and go dependencies checked as well.

I will be working on this later, I really like this project since I've been looking for something like that for a while.  I am leveraging my DevSecOps skill first (expect other PR from me :) )but I am planning at looking more into the codebase and others.

It looked quite good until you reverted everything 😄
Are you still working on it and should I wait?

It looked quite good until you reverted everything 😄 Are you still working on it and should I wait?

So I was pulled on a few personnel and work related emergencies.  I am going to take a look at it next week and reorganize the entirety of my PR to include dependancies management, new docker workflow and a few extra things.
I really am sorry, life got in the way I would prefer to close this PR then continue without achieving fully my idea.  I'll be back.


ICallHandler did not intercept class with HandlerAttribute after upgrading from Unity 4 to Unity 5

Hi,
I am trying to update the Unity from 4.0 to 5.10, and my logging interceptor did not work, can somebody give me some idea? Thanks.
My Container setup/
container.Register<ICallHandler, LogCallHandler>(nameof(LogCallHandler));
container.AddNewExtension<Interception>();

and all my interface-implementaion registrations are going through the following helper function.
 if (typeof(Service).IsInterface)
{
        injectionMembers.Add(new InterceptionBehavior<PolicyInjectionBehavior>());
        injectionMembers.Add(new Interceptor<InterfaceInterceptor>());
 }
        var lifetimeManager = registerAsSingleton ? new ContainerControlledLifetimeManager() : null;

         container.RegisterType<Service, Implementation>(name, lifetimeManager, injectionMembers.ToArray());

and my targetted class are annotated with a HandlerAttribute

Could you provide a unit test that works in 4 and fails in 5?

Hi @ENikS, I have create a repo here.
You may build it and run either Unity4 or Unity5 version.
You can see that in Unity5 Version, the CallHandler did not get invoked.

@raytangRT
I need a Unity Test that I could add to other regression tests. Something like this

@ENikS I will make one once I get home tonite.

@ENikS Please find the attached the test case, thanks
Issue27CallHandlerNotBeingInvoke.zip

I am surprised this was not fixed after so much time. The problem is that people migration to 5.x may inadvertently run into this issue. There is no much point into supporting quite an old syntax if it does not behaves as expected.
FWIW, I got a similar case working and I described the changes here

Would you like to contribute the fix? I am sure people will appreciate it.


Add logging developer guideline

How to categorize this PR?

/area documentation dev-productivity logging
/kind enhancement
What this PR does / why we need it:
In the context of https://github.com/gardener/gardener/issues/4251, we are migrating our components from logrus to logr (see https://github.com/gardener/gardener/pull/5057 for part 1).
As migrating to a new logging library and also a new logging style (structured logging) brings up a lot of questions and confusion, I proactively try to clarify them in a developer guideline around logging in our components.
Also, this guideline will hopefully bring more consistency into logging in our codebase.
This should be consulted by developers adding new logs or refactoring existing code (like me), as well as reviewers.
I hope that it will be useful for them, so that they don't have to read up on so many things and dig through logging code to figure out how to best write a simple log statement in some controller.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/4251
Special notes for your reviewer:
After "formalizing" the guideline, I went over the code touched by https://github.com/gardener/gardener/pull/5057 again and applied it to it. That's also why I'm adding this guideline now, so that I have something to follow along the way as well :)
Also, I cleaned up some "obvious" inconsistencies in the codebase with the guideline already (mainly regarding the capitalization part).
I only touched logr statements for now, as the rest will be touched later on anyways.
Further inconsistencies like e.g. fmt.Sprintf usage in log messages can be cleaned up later on in dedicated PRs.
/squash
Release note:

A developer guideline on logging in Gardener components has been added. Please consult this document as a developer or reviewer to ensure consistency in our logs across the codebase. You can find the document [here](https://github.com/gardener/gardener/blob/master/docs/development/logging.md).

/assign

Fixed the unit tests by adapting them to the changes in the last commit.

/assign

/assign

Thanks for having a look folks, looking forward to your feedback! :)

@ialidzhikov thanks for your feedback! I addressed / answered all of your comments. PTAL :)

Generally lgtm. Only have 2 comments with mainly questions and suggestions (if applicable, of course).
I find the newly added guide very useful! 👍

Thanks for all your feedback!
All assigned reviewers have already approved / reviewed. Hence, I propose to merge this tomorrow if nobody else wants to review / is assigned to this PR.

@stoyanr thanks for your feedback as well. I addressed your comments in new commits. PTAL :)

/retest


Design Data Set Abstraction

Following the design of decoupling the Data Set component from the Charts, one of the first steps to take is designing the Data Set Abstraction itself.
Design should involve:

[x] Integration details with Charts
[x] Conceptual details of functionality
[x] Data Set properties

Integration with Charts based on design: Charts and Data Set should be separate components. Data Set attaches to Chart.
Concrete details of how a Data Set will be abstracted as a component are to be decided on.

Concept of Data Set Abstraction might change, for instance, there are considerations to add an additional layer in between.
For now, this is not of high priority, and is to be considered later on.

Data Set Abstraction decided on. Charts have the ability to have multiple Data Sets. There is no layer in between.


Well known endpoint to discover the features the platform has enabled

To power the CLI premium features we need to have insight into the features the platform has enabled.
The goal will be to use this to provide richer errors during CLI work and obscure features which don't exist from the TUI.

Related to https://github.com/opentdf/platform/issues/563


Cannot get combodate to be editable at all

Using latest x-editable with latest jquery (3.1.1) and latest bootstrap (3.3.7).  I have 2 selects that work perfectly on the page.
Any idea what might be up?

Unfortunately due to this project being supported by volunteers we cannot provide user support at this time. Please try a site like Stack Overflow:  http://stackoverflow.com/questions/tagged/x-editable
Thank you.


add(register.http.js): added functions to register a user

@karolkozlo let me know what kind of naming convention I should follow in frontend/

Tips for testing:

set up the docker-compose with the database locally on your pc
change the baseURL to localhost:3001 or whatever port you are running the backend on
run the backend (npm run dev)
you can paste the example into register.http.js and try running it via node register.http.js

I encourage to test different scenarios - backend working, backend not working, clashing htmls etc
The error messages from the backend need improvements but I am not going to tackle them in this PR. I am going to post an issue and mark it as a good first issue.
I am also considering adding to the docker-compose file to set up nginx, so it reroutes to the backend without changing the baseURL. I think it's a good idea tbh.


Don't enlarge focused nodes.

Calculate size based on number of nodes that come up into the
selection area.

Fixes #1244

@davkal rfr

Otherwise, LGTM


Unify 'CMAKE_*_DIR'

Depends on https://github.com/patrikhuber/eos/pull/84

Thanks, and interesting link!
I'm not completely sold yet on replacing CMAKE_CURRENT_SOURCE_DIR  with CMAKE_CURRENT_LIST_DIR. In the link, there's no explanation on why the latter should be used over the former:

CMAKE_CURRENT_SOURCE_DIR this is a directory with CMakeLists.txt. If you’re using this variable internally you can substitute is with CMAKE_CURRENT_LIST_DIR.

Edit: Ah, this link gives some explanation... looks like it is indeed better to use CMAKE_CURRENT_LIST_DIR :-)

Ah, this link gives some explanation

Actually when I hit this problem first time I've read the SO answer like 5 times and didn't get an understanding. I think here are better explanation:

http://cgold.readthedocs.io/en/latest/tutorials/cmake-sources/includes.html#cmake-current-list-dir-vs-cmake-current-source-dir
http://cgold.readthedocs.io/en/latest/tutorials/cmake-sources/includes.html#example

there's no explanation on why the latter should be used over the former

There is no difference in current case because all the files with CMake code is CMakeLists.txt. However CMAKE_CURRENT_LIST_DIR is more universal and works fine in other cases too.

Yes, I had to read the SO answer for a few times as well. I think we got the same understanding of it now.

Conflicts resolved, ready to be merged.

Conflicts resolved, ready to be merged

One more time.

Sorry for taking so long! I currently think changing it to CMAKE_CURRENT_SOURCE_DIR is fine, as it's more common than CMAKE_CURRENT_LIST_DIR. I will take care of resolving the conflicts of this PR if more emerge, thank you for your persistence! :-D
Would using CMAKE_CURRENT_SOURCE_DIR create any issues for Hunter, so does it depend on CMAKE_CURRENT_LIST_DIR? In that case I would be convinced!
Thanks again!

Would using CMAKE_CURRENT_SOURCE_DIR create any issues for Hunter, so does it depend on CMAKE_CURRENT_LIST_DIR? In that case I would be convinced!

No, it's not related to Hunter at all.

I currently think changing it to CMAKE_CURRENT_SOURCE_DIR is fine, as it's more common than CMAKE_CURRENT_LIST_DIR.

Changing CMAKE_CURRENT_SOURCE_DIR -> CMAKE_CURRENT_LIST_DIR or keeping CMAKE_CURRENT_SOURCE_DIR?

No, it's not related to Hunter at all.

Ok, cool!

Changing CMAKE_CURRENT_SOURCE_DIR -> CMAKE_CURRENT_LIST_DIR or keeping CMAKE_CURRENT_SOURCE_DIR?

I think currently some variables are still CMAKE_SOURCE_DIR, and this is definitely a mistake. I fixed this in another branch, I'll merge this soon. So all of these variables should be CMAKE_CURRENT_SOURCE_DIR (or alternatively as you mentioned CMAKE_CURRENT_LIST_DIR but I think I prefer the first one since it is sufficient in our case).

some variables are still CMAKE_SOURCE_DIR, and this is definitely a mistake

Yes, this may cause troubles when eos used as a subproject that added by add_subdirectory.

I think I prefer the first one since it is sufficient in our case

Okay, closing this one then.

I've taken all your changes and put them in PR #98! I just used CMAKE_CURRENT_SOURCE_DIR everywhere instead of CMAKE_CURRENT_LIST_DIR. I hope I didn't forget any of them :-)
Thanks again for your contributions.


Incompatible versions installed by composer due to tag/config (v1.* ... yeah, I know)

Larastan Version: 1.0.4
Laravel Version: 8.83.27

Description

So yeah, this is a 'bug' report against an old version of Larastan, but it effected me today, might affect others, and should be an 'easy' fix.   The problem is that the composer.json configuration of the v.1.x.x line of versions/tags, allows for incompatible versions of larastan & phpstan to be installed.
So I'm working on a legacy Laravel 8 codebase (and working to get it updated), but trying to get some cleanups/refactoring done first to make sure that transition happens smoothly.   And so have been using larastan to check things.   And I've now found where you made v1.0.4 purely as a 'fix' because of phpstan issues.  Looks like phpstan 1.9+ stopped working with the v1 line ... that was detected, and v1.0.4 was push purely as a tag (not release) to fix that.
The problem is that v1.0.3...v1.0.0 were not changed.   Which means the following happens:
If you install larastan first, in a Laravel 8 codebase.
You get Larastan v1.0.4
... and phpstan 1.8.11
... and it works
However, if you install phpstan first, or already had phpstan installed, you get the latest version:
phpstan 1.11.x
And if you THEN require larastan....  Composer looks at the various tags,  sees that the v2 line can't work on Laravel 8 ... Sees that v1.0.4 doesn't work with phpstan 1.11
...
And then happily installs larastan v1.0.3 instead.
Which of course doesn't work / is broken.
So optimally, the tags v1.0.0 ... v1.0.3 should all be updated, to include the phpstan <1.9 directive, so the composer doesn't think it should work.

Hello @EliW! 👋🏻
There is no support for v1.
But I leave you with this: composer update --with=phpstan/phpstan:1.8.11

Hello @EliW! 👋🏻
There is no support for v1. But I leave you with this: composer update --with=phpstan/phpstan:1.8.11

Thanks @szepeviktor — Definitely understand that v1 is long dead.   And you don't need the --with command, if you just remove phpstan then require larastan, it 'fixes' itself.   (Unless another dependency had already installed a higher version).
I just wanted to bring this up, because it's an extremely minor 'fix', since it's not actually a code change at all.  The 1.0.0, 1.0.1, 1.0.2, and 1.0.3 composer.json files just need the phpstan require section changed to be what is in the 1.0.4 tag as well.
While the 1.x line isn't supported, that 1 line JSON change in the 4 tags would stop composer from installing incompatible versions of larastan/phpstan together, which currently can happen.   For people who are still stuck on Laravel 8, and who are trying to use larastan/phpstan to clean up the codebase to enable moving to 9/10/11 :)
Obviously y'alls call.     It appears that the v1.0.4 tag was basically the fix for this, instead of updating the original tags.  But unfortunately that doesn't fix it fully, since it only solves the issues in '1 direction'.

Hi,
I see how it can cause issues. But given there is kind of a "work around" for it and it'd affect only few people, I think we will not do this. Also I don't want to deal with re-tagging etc. Hope you understand. Thank you!


Réparer le travis.yml pour symfony 4

Closed in favor of https://github.com/theodo/theodo-stack-generator/issues/86


Refactor utils

Current coverage is 92.16% (diff: 81.19%)

Merging #388 into master will decrease coverage by 1.60%

@@             master       #388   diff @@
==========================================
  Files            73         84    +11
  Lines           946       1148   +202
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            887       1058   +171
- Misses           59         90    +31
  Partials          0          0

Powered by Codecov. Last update 63aa837...680e059


fix spelling mistake in example

fixing spelling mistake in line 39 from "feeatures" to "features"

Hey @Caroline-Thies thanks a lot for your PR to fix the example in the README.
I approved and merged it.
Sorry that it took so long.


Multi-line curl is not imported properly if new lines don't have a padding

Expected Behavior
When importing a cURL like this:
curl 'https://example.com/index.html' \
-H 'X-Host: example.com'

It adds a header to the list of headers.
Actual Behavior
All the parameters passed (e.g. -H) are not recognized if they don't have a padding like in:
curl -X POST https://insomnia.rest/ \
  --data "foo=bar&baz=qux" \
  -H Content-Type:application/x-www-form-urlencoded

(link)
Reproduction Steps

Click "New Request/Import" -> "From Curl"

Import a curl without paddings.

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
The issue, I believe, is in https://github.com/Kong/insomnia/blob/54050fe69e3e641c4fadb076e18ca4a1819e31cf/packages/insomnia/src/utils/importers/importers/curl.ts. Although I don't know TS, so 🤷♂
Insomnia Version
8.3.0
What operating system are you using?
macOS
Operating System Version
macOS Sonoma 14.2 Beta
Installation method
download from insomnia.rest
Last Known Working Insomnia version
No response

@mykolasolodukha thanks for reporting this, I was able to reproduce and submit a fix for it https://github.com/Kong/insomnia/pull/6774
it should go out in one of our upcoming releases


Tensorflow backend Function class init() and call() error handling

The TF backend Function now checks the None values present, puts them in the appropriate input, and raises a ValueError if there is a problem.
small part of #6928 and #7046

Error messages are clearer
This is necessary to sort placeholders from ops.

@ahundt, could you squash/remove commits into a clean history on top of master? It is a bit difficult to review these commits when some of them reverse others.
E.g. I would separate typo fixes from cleanup from semantic modifications.
If rebasing is not ok for you on a public branch, I would create a new branch with the rebased commits, and create a new PR it.

@jorgecarleitao Thanks for taking a look! https://github.com/fchollet/keras/pull/7064/files shows everything as a single diff. I merged with master at least, don't have the free cycles for squash/rebase process at the moment. Sorry about that!

Improvements made based on https://github.com/fchollet/keras/pull/8286

@fchollet updated for consideration due to #8286

I think this one can be closed now #8286 is merged.

Closing because equivalent functionality was merged in #8286


Word count or "estimated time to read"?

Hi,
I'd love to add a word count or estimated time to read next to each page on the sidebar on the left. I know I can customize the titleComponent, but without the markdown for each page I don't think I can accomplish this.
Has anyone else had the same desire? Have you found any good hacks to add it in?
(If I wanted to extend the framework, I think I would need to add it to the pageMap and thread that through to the component...)
Thanks,
Tomas

Hey Tomas,
I think readingTime has been included in the PageOpts
as the word count, you can access MdxContent here, you may check if you can figure it out


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

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

This is accepted


[Bugfix] [REST-API] Fixed the problem that the return list is empty due to no status parameters

Purpose of this pull request

close #6037
Does this PR introduce any user-facing change?

No
How was this patch tested?

Already covered
Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

I passed the state parameter in the url actually: http://localhost:5801/hazelcast/rest/maps/finished-jobs/FINISHED.

I passed the state parameter in the url actually: http://localhost:5801/hazelcast/rest/maps/finished-jobs/FINISHED.
So this fix may not solve the bug #6037 .

Can you send the specific error message?

I passed the state parameter in the url actually: http://localhost:5801/hazelcast/rest/maps/finished-jobs/FINISHED.
So this fix may not solve the bug #6037 .

Can you send the specific error message?

Sorry for my mistake, it's ok now.Thanks
.

I found another issue: The metrics were not serialized in CamelCase format.
[
    {
        "jobId": "790041833823535105",
        "jobName": "fake-to-console",
        "jobStatus": "FINISHED",
        "errorMsg": null,
        "createTime": "2023-12-21 02:24:11",
        "finishTime": "2023-12-21 02:24:13",
        "jobDag": {
            "jobId":<PHONE_NUMBER>23535105,
            "pipelineEdges": {
                "1": [
                    {
                        "inputVertexId": 1,
                        "targetVertexId": 2
                    }
                ]
            },
            "vertexInfoMap": {
                "1": {
                    "vertexId": 1,
                    "type": "SOURCE",
                    "connectorType": "pipeline-1 [Source[0]-FakeSource]"
                },
                "2": {
                    "vertexId": 2,
                    "type": "SINK",
                    "connectorType": "pipeline-1 [Sink[0]-Console-MultiTableSink]"
                }
            }
        },
        "metrics": {
            "SourceReceivedCount": "10000",
            "SinkWriteCount": "10000"
        }
    }
]

I found another issue: The metrics were not serialized in CamelCase format.
curl --location --request GET 'http://seatunnel-svc:5801/hazelcast/rest/maps/finished-jobs/FINISHED' \
--header 'User-Agent: Apifox/1.0.0 (https://www.apifox.cn)' \
--header 'Accept: */*' \
--header 'Host: seatunnel-svc:5801' \
--header 'Connection: keep-alive'

[
    {
        "jobId": "790041833823535105",
        "jobName": "fake-to-console",
        "jobStatus": "FINISHED",
        "errorMsg": null,
        "createTime": "2023-12-21 02:24:11",
        "finishTime": "2023-12-21 02:24:13",
        "jobDag": {
            "jobId":<PHONE_NUMBER>23535105,
            "pipelineEdges": {
                "1": [
                    {
                        "inputVertexId": 1,
                        "targetVertexId": 2
                    }
                ]
            },
            "vertexInfoMap": {
                "1": {
                    "vertexId": 1,
                    "type": "SOURCE",
                    "connectorType": "pipeline-1 [Source[0]-FakeSource]"
                },
                "2": {
                    "vertexId": 2,
                    "type": "SINK",
                    "connectorType": "pipeline-1 [Sink[0]-Console-MultiTableSink]"
                }
            }
        },
        "metrics": {
            "SourceReceivedCount": "10000",
            "SinkWriteCount": "10000"
        }
    }
]

Thanks for reminding me, I will enrich the metrics in another PR.

I found another issue: The metrics were not serialized in CamelCase format.
curl --location --request GET 'http://seatunnel-svc:5801/hazelcast/rest/maps/finished-jobs/FINISHED' \
--header 'User-Agent: Apifox/1.0.0 (https://www.apifox.cn)' \
--header 'Accept: */*' \
--header 'Host: seatunnel-svc:5801' \
--header 'Connection: keep-alive'

[
    {
        "jobId": "790041833823535105",
        "jobName": "fake-to-console",
        "jobStatus": "FINISHED",
        "errorMsg": null,
        "createTime": "2023-12-21 02:24:11",
        "finishTime": "2023-12-21 02:24:13",
        "jobDag": {
            "jobId":<PHONE_NUMBER>23535105,
            "pipelineEdges": {
                "1": [
                    {
                        "inputVertexId": 1,
                        "targetVertexId": 2
                    }
                ]
            },
            "vertexInfoMap": {
                "1": {
                    "vertexId": 1,
                    "type": "SOURCE",
                    "connectorType": "pipeline-1 [Source[0]-FakeSource]"
                },
                "2": {
                    "vertexId": 2,
                    "type": "SINK",
                    "connectorType": "pipeline-1 [Sink[0]-Console-MultiTableSink]"
                }
            }
        },
        "metrics": {
            "SourceReceivedCount": "10000",
            "SinkWriteCount": "10000"
        }
    }
]

Thanks for reminding me, I will enrich the metrics in another PR.

Please create an issue for it, let us not lost it.


Function to list devices

Write a function that uses the NM DBus API to retrieve a list of devices.

https://github.com/resin-io/hq/pull/453

Pull-request: #28


Improve docs search

Current behavior
Search mechanism only look for title and description

Expected behavior
Search mechanism look for title, description and content

@dai-shi do you know who can take care of this?

@CodyJasonBennett


Cadl should support decorators for the OpenAPI info.contact and info.license fields

The OpenAPI info object has two fields, contact and license, that API designers may want in the generated openapi. In particular, some linters require the info.contact field to be present.

Is this metadata that we just want for any spec as core decoration?

also terms Of Service for the info object

Add info decorator which takes in these properties. OpenAPI3

pri: 1
est: 3


Upgrade to opentracing-java 0.21.0 and handle PEER_PORT change from s…

…hort to int

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

Codecov Report

Merging #137 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #137      +/-   ##
============================================
+ Coverage     35.96%   35.99%   +0.03%
- Complexity      587      589       +2
============================================
  Files            87       93       +6
  Lines          6298     6301       +3
  Branches       1046     1046
============================================
+ Hits           2265     2268       +3
- Misses         3852     3854       +2
+ Partials        181      179       -2

Impacted Files
Coverage Δ
Complexity Δ

...r/jaeger/httpclient/TracingRequestInterceptor.java
84.61% <100%> (ø)
5 <0> (ø)
:arrow_down:

...ain/java/com/uber/jaeger/context/TracingUtils.java
50% <0%> (-5.56%)
2% <0%> (-3%)

...m/uber/jaeger/httpclient/ClientRequestCarrier.java
83.33% <0%> (ø)
2% <0%> (-2%)
:arrow_down:

...ain/java/com/uber/jaeger/metrics/StatsFactory.java

...er/jaeger/filters/jaxrs2/ClientRequestCarrier.java
83.33% <0%> (ø)
2% <0%> (?)

...a/com/uber/jaeger/filters/jaxrs2/TracingUtils.java
60% <0%> (ø)
3% <0%> (?)

.../java/com/uber/jaeger/dropwizard/StatsFactory.java
100% <0%> (ø)
4% <0%> (?)

...java/com/uber/jaeger/filters/jaxrs2/Constants.java
0% <0%> (ø)
0% <0%> (?)

...-core/src/main/java/com/uber/jaeger/Constants.java
0% <0%> (ø)
0% <0%> (?)

...java/com/uber/jaeger/dropwizard/Configuration.java
50% <0%> (ø)
3% <0%> (?)

... and 3 more

Continue to review full report at Codecov.

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

This update was required to enable Jaeger's java Tracer to be used with the Apache Camel camel-example-opentracing example.

Could you please do release of 0.18.0 once this is merged?


"sourceBranch" not working in local config?

I've created a local config file as follows:
{
    "repoOwner": "DragonMinded",
    "repoName": "libdragon",
    "targetBranchChoices": [{ "name": "trunk", "checked": true }],
    "sourceBranch": "preview",
    "multipleCommits": true
}

My global config only contains the access token. When I run backport with no arguments, the tool fetches the remote commits from the default branch (trunk) and shows me the list of trunk commits to select for backport. If I instead run the tool with backport --sourceBranch=preview, everything works as expected.
I'm running backport 9.6.1.

Thanks for raising this. I'll take a look. Until then can you try with backport --skipRemoteConfig and see if that makes a difference?


⚠ Bofrost.com has degraded performance

In e1b63e3, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 833 ms

Resolved: Bofrost.com performance has improved in bb70c8c after 13 minutes.


Fix line number table corruption, fix #12

This is a rollup PR for a few miscellaneous fixes that I've made to ghidra2dwarf, including a fix for #12. With the fix, DWARF export for ARM works fine.

Hi @nneonneo ,
Thank you for the PR.
Can you try to push an empty commit or to rebase to the latest commit of the master branch? I should have fixed the failing workflow, but I can't find a way to run it against your branch without merging your master branch into a separate branch into this repository :thinking: .
Do you have a binary that I can test the PR with? I also have to validate the new offsets (+ - 1)

Pushed. Here's a test binary with source: testbin.zip
This is compiled with x86_64-linux-android-gcc -m32 --sysroot=android-ndk-r10c/platforms/android-21/arch-x86 test.c -g -o test_gcc_dbg. test is the stripped version of test_gcc_dbg.
testbin_g2d.zip contains the binaries generated by the current version (test_dbg_old) and the PR version (test_dbg_new).
As a test, try the following:
$ gdb ./test_dbg_old
GNU gdb (GDB) 12.1
...
(gdb) disas hswap
Dump of assembler code for function hswap:
   0x080483b8 <+0>:	push   ebp
   0x080483b9 <+1>:	mov    ebp,esp
   0x080483bb <+3>:	mov    eax,DWORD PTR [ebp+0x8]
   0x080483be <+6>:	shl    eax,0x10
   0x080483c1 <+9>:	mov    edx,eax
   0x080483c3 <+11>:	mov    eax,DWORD PTR [ebp+0x8]
   0x080483c6 <+14>:	shr    eax,0x10
   0x080483c9 <+17>:	or     eax,edx
End of assembler dump.

And with the PR:
$ gdb ./test_dbg_new
GNU gdb (GDB) 12.1
...
(gdb) disas hswap
Dump of assembler code for function hswap:
   0x080483b8 <+0>:	push   ebp
   0x080483b9 <+1>:	mov    ebp,esp
   0x080483bb <+3>:	mov    eax,DWORD PTR [ebp+0x8]
   0x080483be <+6>:	shl    eax,0x10
   0x080483c1 <+9>:	mov    edx,eax
   0x080483c3 <+11>:	mov    eax,DWORD PTR [ebp+0x8]
   0x080483c6 <+14>:	shr    eax,0x10
   0x080483c9 <+17>:	or     eax,edx
   0x080483cb <+19>:	pop    ebp
   0x080483cc <+20>:	ret
End of assembler dump.

As for ARM support, try the following binary (same .c file as before):
test_arm.zip
It will crash with the error Exception: enum SHT has no entry with code<PHONE_NUMBER>. on the current master, and will succeed with the PR.

Thank you so much for the PR (and for still using this)!
@meowmeowxw the docs confirm that the +1 offset is correct, it says DW_AT_high_pc should be the "address of the first location past the last instruction associated with the entity". Actually this was already fixed in my (wip) rewrite and I never noticed, so I guess I also tested it.
Great catch with figuring out that the addresses need to be sorted! Is it documented somewhere?
I stopped working on this out of frustration because it never seemed to work properly with big binaries and I couldn't figure out why. I always assumed it was a bug in libdwarf and they made building the new version a nightmare so I gave up. Your commit probably fixes everything so thank you for the dedication and for making it public!
I'll hopefully have some time to test it in the next few days, but the code looks very reasonable and I'm also ok with merging this blindly @meowmeowxw .

I found this out essentially by realizing that libdwarf was generating garbage when the addresses decreased.
However, I found this in the DWARF v2 standard, in section 6.2.5: “Within a sequence, addresses may only increase.”. Similar text is found in the DWARF v4 standard.

Hello @nneonneo ,
Thank you for the references in the commit messages, I remember that we spent lots of hours trying to understand why there was a corruption on big binaries of the dwarf table.
I tested the new changes and they work fine :smile: , I merge the PR and release the new version


Prevent known autokalimba keys triggering browser actions

Motivating example: / triggers quick-find in Firefox.
Done by adding e.preventDefault() in every path where a key is recognised, but not in other paths, so that it won't disable bindings that don't conflict.

wait don't merge this yet i found another problem with the same thing

Changed it to just disable everything because ' also triggers quick-find, which is very annoying while learning to move your fingers around the keyboard correctly, even if it isn't actually used by autokalimba. It's better for me and it's also simpler overall, and consistent with how stuff like ⌘R is already broken.


phaser-sync

Missing bits from phaser creature runtime put into kestrel runtime

Hi,
I stupidly committed my changes when i was tired, i will go back and review this commit.
generally i think the main part which i added was
Creature.prototype.SetAnchorPoint =
which allows to set the anchorpoint dynamically (without needing to have it set in the json file)


Added: URL to the code where the list of available functions in the sandbox is defined

Makes sense, thanks @starrify!


Does not affect Date.prototype.toLocaleString

// I'm in America/Los_Angeles (+08:00) during non-saving time:
(new Date()).getTimezoneOffset()
// 480

// 4pm in America/Chicago (+06:00) is 2pm in my local time:
(new Date('2001-02-03T04:05+06:00')).toLocaleString([], {hour: "2-digit",minute: "2-digit"})
// '2:05 PM'

// If I change to America/Denver (+07:00):
const MD = require('mockdate')
MD.set('2002-03-04T05:06+07:00', -420)

// then getTimezoneOffset is mocked:
(new Date()).getTimezoneOffset()
// 420

// but toLocaleString isn't:
(new Date('2001-02-03T04:05+06:00')).toLocaleString([], {hour: "2-digit",minute: "2-digit"})
// '2:05 PM'

Taking in an offset as a 2nd parameter to MockDate.set was a mistake that I regret because it leads to confusing expectations on how it should work. The only thing it does is mock the result of getTimezoneOffset, but it has no effect on other methods that read that value.
Trying to modify every method whose return value is dependent upon the timezone offset would be too difficult, and is really not the purpose of this library.
I might release a new major version without the timezone offset parameter, because it's confusing and not very helpful.
Sorry, I know that's not the answer you wanted to hear.

@boblauer Am I right that another part to this is that new Date() does not actually use the timezone used in MockDate.set? In other words new Date(2019, 3, 2) will create a date in the running system timezone?

Yup, that is correct.


Update Disks Config

APP_URL by default include http/https scheme

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


Make the name of the knowledge panel visible (per mocks)

What

[ ] Make the name of the knowledge panel visible (per mocks) using the available field in the API

Part of

#499

Will do that,
Plz assign me this issue

Done @AshAman999
It's probably already mapped in openfoodfacts-dart, otherwise you may have to do a PR there.

Done @AshAman999 It's probably already mapped in openfoodfacts-dart, otherwise you may have to do a PR there.

I think that's not needed, got it working will raise a pr soon :)

One question, how do I make this first alphabet capitalized? I guess there is no direct method so should I
create a utility method for the same or one is already there? :confused:

I don't know one, at least not in our codebase. Feel free to create one 👍🏼


add config.services.xserver.windowManager.sway

Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

needs wayland-compatible display manager such as SDDM or GDM (tested with SDDM)

Is this x+wayland? Either way its good progress!

yes, the display manager still runs on X, this just adds the option to select sway, that would run in a wayland session

Thanks for the work. Obviously this should not be part of services.xserver, but fixing this is a whole other issue. So it's probably ok for now.
Another thing:
At least GDM decides which session (x or wayland) is needed by looking at the path of the .desktop file. If I remember correctly, support for GDM-Session-Type (or similar) was dropped again.
I would really appreciate it, if you tested this with gdm 3.22 from #19081 which itself uses wayland instead of X and see if it works. I might give it a shot myself when I find time.

I tested this out. I was using slim. Sway started and it even loaded my i3 config and ran i3status without me creating a separate sway config. However, whenever I tried to create a terminal, the process started but it was not visible on the screen. Looking at the process tree in htop I could see all of my terminals and they were all under pid 1. Everything looked normal, I just couldn't see them.

This is awesome progress!
Note that in https://github.com/NixOS/nixpkgs/pull/21808 sway will be updated, which might result in unexpected things after the merge.
I would vote for an options.services.graphics.xserver option, keeping options.services.xserver to be backwards compatible.
But sure, this is another issue and should be discussed elsewhere.

Can you add a setcap wrapper as described in the README.md using our new setcap wrapper?

This can be closed. It's not longer relevant or up-to-date.

@colemickens So Sway will not be supported in NixOS?

@matthew-piziak oh no, I'm sorry I didn't explain more. There is already a Sway package and module in nixpkgs now!

Reference: https://github.com/NixOS/nixpkgs/blob/release-18.09/nixos/modules/programs/sway.nix

Weird, if I add programs.sway.enable = true; to my configuration.nix and also put "sway" in my extraGroups, then running sway gives me Couldn't exec sway-setcap: Permission denied.
Getting a permission error is weird, given that I'm part of the group.
If I run sway as root, I get 03/19/19 13:42:51 - [main.c:48] [wlc] Failed to add socket to wayland display.

You're not up to date if you're getting errors about setcap and wlc.
See this commit: https://github.com/NixOS/nixpkgs-channels/commit/45004c6f6330b1ff6f3d6c3a0ea8019f6c18a930 It's in nixos-unstable and I know the change was ported into the 19.03 channel as well.

Ah, thanks. Unfortunately NVIDIA drivers do not build on 19.03, and sway does not build on 18.09. NVIDIA is more important to me. I haven't figured out how to import program configuration from specific channels (like sway from unstable, for example). I only know how to do it for packages, not programs. I don't suppose you know how to do that?

Sway 1.0 explicitly will refuse to start with nvidia drivers, anyway. You'd need to use nouvaeu.
The NUR supposedly has examples of importing modules but I've never gotten it to work. I actually wanted to do this as part of nixpkgs-wayland.

Oh, and there's no way to use one set of drivers for sway and one for everything else right? Probably a silly question but I really don't know. Prooobably not going to give up the graphics card performance in exchange for this window manager.
Thanks for answering my questions!

Which features are in this PR that aren't on master? If there aren't any, please close this PR.

Which features are in this PR that aren't on master? If there aren't any, please close this PR. (making an attempt to clean up older PRs)

I don't see any of these features in master.

Aren't they on master under programs.sway ? https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/programs/sway.nix

Aren't they on master under programs.sway ? https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/programs/sway.nix

Yes they are! It makes sense to close then.


doc: Use the right classes in customconfig's Hybrid Example

Propose a new HypridExample.
As mentioned in Issue#1211, the Hyprid Example in the customconfig documentation is broken.

Uses a bunch of deprecated APIs, FileAppender.createAppender and LoggerConfig.createLogger
Using the wrong XMLConfigration class with all caps XML, instead of using the XmlConfiguration class.
Fix the constructor call for both MyXmlConfigurationFactory and MyXmlConfiguration calsses.
Missing the AppenderRef[] from the createLogger invokation.

@aawad6, thanks! :pray:
Keep these PRs coming! :rocket:


IE8 Support

Yes I know.. I know.
It is listed as one of the supported browsers however. Currently we're hitting errors as it does not support array.indexOf().  This was apparently added in IE9. This is being hit here:
https://github.com/rxaviers/cldrjs/blob/d862808e10477092fa4b41176471b957cd6224d5/src/core/set_available_bundles.js#L22

Thanks for filing this issue.
We could polyfill this method in a similar fashion to https://github.com/rxaviers/cldrjs/blob/master/src/util/array/for_each.js perhaps by using https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/indexOf#Polyfill as reference, but reducing it to our use specific case (e.g., input is always a non-empty String).
Would you like to work on that?
Having said that, it's time to consider dropping IE8 support in here as well (and drop several of those helper functions).

We've polyfilled it in for our own case. I'm in two minds on this one, on the one hand, it's entirely fair to just drop IE8 support. On the other hand, there's only this single method call preventing support. So I'm leaning towards the latter.
I'd be weary of polyfilling primitives in a library, so I think revising implementation is probably best.
Am off with a new bub at the moment, will keep this on the radar.

Just to be clear, this libraries doesn't polyfill any primitives, sorry for the confusion. We have helper functions like https://github.com/rxaviers/cldrjs/blob/master/src/util/array/for_each.js.

I believe we can safely ignore this support.


_tsf_reader.convert_base doesn't handle "10 minutes" frequency correctly

Description
For Monash datasets with the "10 minutes" frequency, the frequency converter will convert it to a frequency 10 MonthEnd (10M), instead of the expect 10 Minutes (10T) frequency.
There is already code to properly handle the "minutely" frequency, but it checks for that string explicitly, so it doesn't catch the "10 minutes" case.
To Reproduce
One dataset which has this frequency is the 10 minutes observation Solar dataset: https://zenodo.org/record/4656144
filename: "solar_10_minutes_dataset.zip"
record: "4656132"

If I get this right, changing this for something like
if text.lower() in ["minutely", "minutes"]:

should do the trick, but then maybe we want to review the datasets specs here to make sure this mechanism is robust enough.


Issue using jackson serializer when query hanlder returning list of objects

Basic information

Axon Framework version: 4.6.1
JDK version:  17
Complete executable reproducer if available (e.g. GitHub Repo):

java.lang.IllegalArgumentException: Retrieved response [class java.util.ArrayList] is not convertible to a List of the expected response type

Did you enable default typing on the Jackson serializer?

You can spot the subject here in the Reference Guide, @github4sanjay.

Seems similar to https://github.com/AxonFramework/AxonFramework/issues/1331


[Excel 2003 XML] Add support for font name, size, and color

This is blocked by fixes to other issues such as #42 and #43, but support for fonts and their colors is what I was originally in search of! :)
I would like to be able to do this via the #font method, for example:
roo = Roo::Excel2003XML.new('test/files/font_colors.xml')
roo.default_sheet = roo.sheets.first

roo.font(1, 'A').name
#=> "Courier New"

roo.font(1, 'A').size
#=> "24"

roo.font(1, 'A').color
#=> "#000000"

Fixed in #45


Using Trumbowyg inside bootstap modal is not showing

I have done Trumbowyg editor .. I want to add it also in modal to edit the posted values ,
but it is not showing in bootsrap modal ..
Any way that i can show it ??

Solution U need to use another id because i alredy have one for posting


Pre-configured queries for common devices?

Would it be useful for us to provide pre-configured queries for common devices? If so, what would be the best way to expose it?
The folks over at @CSS-Tricks have compiled a nice list of media queries for standard devices that I thought we could start with. Maybe we could provide a bunch of pre-configured <Media> components that target these devices.
<iPhone6Media>
{matches => matches ? (

You're on an iPhone 6

) : (

You're using something else

)
</iPhone6Media>

@ryanflorence Thoughts?

Hmm, I'm not immediately excited about it, I prefer just doing a general "phone-ish" size in portrait, "phone-ish" size landscape, and then "desktop-ish". Designed to exact sizes makes me nervous. What does it do on the phone that comes out next month?

How about exporting strings under react-media/presets?

Someone suggested on Twitter that we could have components for e.g.
and , which I think is interesting.
https://twitter.com/teh_builder/status/764735449604714496
On Sun, Aug 14, 2016 at 4:57 AM Steven Langbroek<EMAIL_ADDRESS>wrote:

How about exporting strings under react-media/presets?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactTraining/react-media/issues/5#issuecomment-239669828,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFqp8nL-SvmbhMgMnhMlo94Ls9QEZOLks5qfwKNgaJpZM4Jjxq9
.

--
Michael Jackson
@mjackson

yeah, I like Phone, Tablet, but strings might be good enough? Motion
doesn't export "Wobbly" but rather presets.wobbly.
On Sun, Aug 14, 2016 at 7:36 AM Michael Jackson<EMAIL_ADDRESS>wrote:

Someone suggested on Twitter that we could have components for e.g.
and , which I think is interesting.
https://twitter.com/teh_builder/status/764735449604714496
On Sun, Aug 14, 2016 at 4:57 AM Steven Langbroek<EMAIL_ADDRESS>
wrote:

How about exporting strings under react-media/presets?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/ReactTraining/react-media/issues/5#issuecomment-239669828
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAFqp8nL-SvmbhMgMnhMlo94Ls9QEZOLks5qfwKNgaJpZM4Jjxq9
.

--
Michael Jackson
@mjackson
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ReactTraining/react-media/issues/5#issuecomment-239676889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGHaL9a6eEf8z3top9_teJLdh4AIoo-ks5qfyfvgaJpZM4Jjxq9
.

Agree, could be a very nice API. How would it compose though? with exporting strings, you could just:
import Media from 'react-media';
import { PHONE, TABLET } from 'react-media/presets';

export default () => ({
  <Media query={`${PHONE} or ${TABLET}`}>
    {matches => `Phone or tablet!`}
  </Media>
});

You could even use these as primitives to base the "prefab" components on then.

Thought: could an actively maintained set of device-specific and device-class (phone, tablet, desktop) queries serve as the backbone of this project, in the same vein that history is for react-router?

we send strings to matchMedia, that's the "history" part here I think.
On Sun, Aug 14, 2016 at 8:41 AM Steven Langbroek<EMAIL_ADDRESS>wrote:

Thought: could an actively maintained set of device-specific and
device-class (phone, tablet, desktop) queries serve as the backbone of this
project, in the same vein that history is for react-router?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ReactTraining/react-media/issues/5#issuecomment-239680280,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGHaGB228nVMG1EuiMh6yjeH4Nl5c6Kks5qfzcygaJpZM4Jjxq9
.

You're right, but what I meant was "something that could be abstracted away and could serve other projects / the greater community".

Ah, yes. Strings seems to be the obvious choice for composition here. The hardest part left is deciding what the actual queries should look like. Are there any broadly recommended "phone" or "tablet" media queries out there?

Few notes:

Love the idea, of a presets file. Would love to see it as landscape and portrait since they are so different.
Chrome has pre-defined in their dev tools and appear to be close adaptions of the bootstrap media queries.

@kwelch I poked around in Chrome's DevTools but couldn't get the queries they're using. Do you see them?

If you switch the dropdown to Responsive then, the predefined widths show up.

Mobile S - 320px
Mobile M - 375px
Mobile L - 425px
etc..

There is more granular than I think is appropriate for this library (at this point), but could give a decent MVP.

Looks like this conversation stalled. Closing.


SimplePermissionManager.java:92: Implement...

The puzzle 1-98c280ea from #1 has to be resolved:
https://github.com/shiruka/shiruka/blob/24d02de4e698c2d724c0a733186145a34d4b3621/src/main/java/net/shiruka/shiruka/permission/SimplePermissionManager.java#L92-L92
The puzzle was created by Hasan Demirtaş on 01-Feb-21.
Estimate: 10 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1-98c280ea has disappeared from the source code, that's why I closed this issue.


simplify save_webpages

Features
simplify save_webpages

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

Project coverage is 81.18%. Comparing base (803359a) to head (478ba13).
Report is 7 commits behind head on code_interpreter.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                 Coverage Diff                  @@
##           code_interpreter     #981      +/-   ##
====================================================
- Coverage             81.20%   81.18%   -0.03%
====================================================
  Files                   226      226
  Lines                 12483    12466      -17
====================================================
- Hits                  10137    10120      -17
  Misses                 2346     2346

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


Not running Node.js 4, but getting "Node.js 4 is supported but the specific version you're running has a bug known to break npm"

Operating system and version:
OSX 10.13.5
nvm debug output:

nvm --version: v0.33.11
$TERM_PROGRAM: Apple_Terminal
$SHELL: /bin/bash
$SHLVL: 1
$HOME: /Users/Dillon
$NVM_DIR: '$HOME/.nvm'
$PATH: /usr/local/opt/openssl/bin:/usr/local/opt/openssl/bin:/Library/Frameworks/Python.framework/Versions/3.6/bin:/Library/Frameworks/Python.framework/Versions/3.5/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin17)'
uname -a: 'Darwin 17.6.0 Darwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64 x86_64'
OS version: Mac 10.13.5 17F77
curl: /usr/bin/curl, curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
wget: not found
git: /usr/bin/git, git version 2.15.1 (Apple Git-101)
grep: /usr/bin/grep, grep (BSD grep) 2.5.1-FreeBSD
awk: /usr/bin/awk, awk version 20070501
sed: illegal option -- -
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: /usr/bin/sed,
cut: illegal option -- -
usage: cut -b list [-n] [file ...]
       cut -c list [file ...]
       cut -f list [-s] [-d delim] [file ...]
cut: /usr/bin/cut,
basename: illegal option -- -
usage: basename string [suffix]
       basename [-a] [-s suffix] string [...]
basename: /usr/bin/basename,
rm: illegal option -- -
usage: rm [-f | -i] [-dPRrvW] file ...
       unlink file
rm: /bin/rm,
mkdir: illegal option -- -
usage: mkdir [-pv] [-m mode] directory ...
mkdir: /bin/mkdir,
xargs: illegal option -- -
usage: xargs [-0opt] [-E eofstr] [-I replstr [-R replacements]] [-J replstr]
             [-L number] [-n number [-x]] [-P maxprocs] [-s size]
             [utility [argument ...]]
xargs: /usr/bin/xargs,
nvm current: system
which node: /usr/local/bin/node
which iojs:
which npm: /usr/local/bin/npm
npm config get prefix: /usr/local
npm root -g: /usr/local/lib/node_modules
Dillons-MacBook-Pro:~ Dillon$

nvm ls output:

         v4.1.2
        v10.1.0
        v10.4.0
->       system
default -> v4.1 (-> v4.1.2)
node -> stable (-> v10.4.0) (default)
stable -> 10.4 (-> v10.4.0) (default)
iojs -> N/A (default)
lts/* -> lts/carbon (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.14.2 (-> N/A)
lts/carbon -> v8.11.2 (-> N/A)

How did you install nvm? (e.g. install script in readme, Homebrew):
i believe install script in readme. (almost definitely not homebrew)

What steps did you perform?
If I install npm following this https://docs.npmjs.com/getting-started/installing-node, and then open a terminal window.

What happened?
I get the following response before even running any commands:
ERROR: npm is known not to run on Node.js v4.1.2
Node.js 4 is supported but the specific version you're running has
a bug known to break npm. Please update to at least 4.7.0 to use this
version of npm. You can find the latest release of Node.js at https://nodejs.org/
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run npm config delete prefix or nvm use --delete-prefix v4.1.2 --silent to unset it.

What did you expect to happen?
since nvm version gives v10.4.0, and npm version gives { npm: '6.1.0',
ares: '1.14.0',
cldr: '33.0',
http_parser: '2.8.0',
icu: '61.1',
modules: '64',
napi: '3',
nghttp2: '1.29.0',
node: '10.4.0',
openssl: '1.1.0h',
tz: '2018c',
unicode: '10.0',
uv: '1.20.3',
v8: '6.7.288.43-node.7',
zlib: '1.2.11' }
I expect this error to not occur. I have tried reinstalling nvm and npm multiple times.

Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?
echo $PATH gives /Users/Dillon/.nvm/versions/node/v10.4.0/bin:/usr/local/opt/openssl/bin:/usr/local/opt/openssl/bin:/Library/Frameworks/Python.framework/Versions/3.6/bin:/Library/Frameworks/Python.framework/Versions/3.5/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

* Connection #0 to host nodejs.org left intact

This isn't an nvm error, it's an issue with npm itself - probably your system npm.

What happens if you run nvm use system and then run npm version?

{ npm: '5.6.0',
ares: '1.10.1-DEV',
cldr: '32.0',
http_parser: '2.8.0',
icu: '60.1',
modules: '57',
napi: '3',
nghttp2: '1.29.0',
node: '8.11.2',
openssl: '1.0.2o',
tz: '2017c',
unicode: '10.0',
uv: '1.19.1',
v8: '6.2.414.54',
zlib: '1.2.11' }

@dpett122 and what about nvm use 4.1.2 && npm version?

nvm use 4.1.2 && npm version

ERROR: npm is known not to run on Node.js v4.1.2
Node.js 4 is supported but the specific version you're running has
a bug known to break npm. Please update to at least 4.7.0 to use this
version of npm. You can find the latest release of Node.js at https://nodejs.org/
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `npm config delete prefix` or `nvm use --delete-prefix v4.1.2` to unset it.

I found that user/.nvm/versions/node/ has v4.1.2, v10.1.0, and v10.4.0 folders, if that's helpful.

and which npm gives /usr/local/bin/npm

and npm root -g gives /usr/local/lib/node_modules, and in that folder, the CHANGELOG.md shows v5.6.0

What it sounds like the issue is, is that your v4.1.2 installation had npm install -g npm run on it, which is unsafe - you could do nvm uninstall 4.1.2 && nvm install --latest-npm 4.1.2, and that should fix it.

That did the trick! Thanks so much for helping me through this 😄


Custom command doesn't work as expected

The custom command option only sends the first param of a command.
For example:
command PSCINEMA EQ. ? won't send the whole command to the AVR,
instead PSCINEMA will be sent without the rest of the parameters.

I've raised a PR with a fix: #11


style: format files with stylua

Pull requests are currently failing because these files don't pass the StyLua lint check.

I suspect this is because of the new StyLua v0.11.0 release...?

I suspect this is because of the new StyLua v0.11.0 release...?

Hey, someone pointed this issue out to me in passing, and mentioned that their CI suddenly fails whenever stylua updates, pointing out yours as well.
I naively created the action with the version field being optional in the workflow.yml, so by default the action runs using the latest build - this can be annoying when CI suddenly fails like this 🤦!
I'd recommend pinning the version in your lint.yml file, to have something like
  style-lint:
    runs-on: [ubuntu-latest]
    steps:
    - name: Checkout sources
      uses: actions/checkout@v2
    - name: Lint with stylua
      uses<EMAIL_ADDRESS>      with:
        token: ${{ secrets.GITHUB_TOKEN }}
        version: 0.11.0
        # CLI arguments
        args: --check .

The disadvantage being that you'll have to manually change it as you bump your stylua version for new updates, but I think thats better than letting it auto update as current.
I tried to make the README more obvious in the action repo but since the workflow is already out in the wild most workflows have the version field omitted.
Apologies for the hassle (to you and anyone else reading!)


Fields cannot be custom converted when use PostgreSql

Fields cannot be custom converted
Hi, when I use the gen tool to generate code from postgresql, I found that the custom conversion type cannot take effect. Below is my table structure and generated model:
CREATE TABLE call_data
(
    A     INTEGER primary key,
    B     INTEGER,
    C     INTEGER
)

type CallDatum struct {
	A          int32
	B         *int32
	C         *int32
}

Here's the conversion I expect:
	var dataMap = map[string]func(detailType string) (dataType string){
		"tinyint":   func(detailType string) (dataType string) { return "int64" },
		"smallint":  func(detailType string) (dataType string) { return "int64" },
		"mediumint": func(detailType string) (dataType string) { return "int64" },
		"bigint":    func(detailType string) (dataType string) { return "int64" },
		"int":       func(detailType string) (dataType string) { return "int64" },
		"INTEGER":   func(detailType string) (dataType string) { return "int64" },
		"integer":   func(detailType string) (dataType string) { return "int64" },
	}
	g.WithDataTypeMap(dataMap)

I expected the Integer types to all be converted to int64, but that's not happening
The document you expected this should be explained
I have consulted the documentation and materials, but int32 fields are still generated in the end.

Expected answer
Any method capable of converting INTERGER type to int64

@hhmy27 You can take a look at the type tag on the generated model.
e.g. column:age;type:int8

@hhmy27 You can take a look at the type tag on the generated model. e.g. column:age;type:int8

Thanks to your reply.
Here is a filed generated by gen:
id          int32   `gorm:"column:id;type:integer;primaryKey" json:"id"

the type tag is type:integer;.
I wrote the conversion rule as written above: "integer": func(detailType string) (dataType string) { return "int64" },, but it doesn't work,  and finally generates int32 field.

@hhmy27 try numeric .
datatype-numeric

@hhmy27 try numeric . datatype-numeric

it doesn't work..

@hhmy27 playground

@hhmy27
dataMap := map[string]func(columnType gorm.ColumnType) (dataType string){
		"int2": func(columnType gorm.ColumnType) (dataType string) { //smallint
			return "int64"
		},
		"int4": func(columnType gorm.ColumnType) (dataType string) { //integer
			return "int64"
		},
		"int8": func(columnType gorm.ColumnType) (dataType string) { //bigint
			return "int64"
		},
	}

Configuration like this will work.
For More details, please refer to the postgreSQL datatype document I posted above.


Improve germline CNV HMM arguments

XHMM was written in one-off style for a specific bait set and contains parameters that are defined in a bait-specific way.  For example meanTargetsPerSegment and meanTargetsPerSegment depend on the density of targets used.  This is unnecessary because any such prior expectations about the quantity and size of CNVs are biological properties independent of the technology.

Basically, rewrite all parameters in terms of genomic distances.


CIV-4138 All GA Judge Make an Order document should be stored in coll…

…ection
Before creating a pull request make sure that:

[x] commit messages are meaningful and follow good commit message guidelines
[x] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-4138
Change description
All General application, Judge Make an Order document should be visible in main case under claim document tab as a collection.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Grawdle build


adds on parts for Markku design Robocar for 1/10 HG-P402.

Also could you move everything else but rail adapter to the modules directory, since there we have all the accessories for the rail.

Ok will do in the next hour.
Envoyé de mon iPhone

Le 10 mai 2019 à 08:15, Antti Kivimäki<EMAIL_ADDRESS>a écrit :
Also could you move everything else but rail adapter to the modules directory, since there we have all the accessories for the rail.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


feature request check if security.txt exists

https://en.wikipedia.org/wiki/Security.txt

That's a good shout, I've added that in PR #12
And I'll take a look through your other requests too, either later this evening or tomorrow night :)

great implementation @Lissy93