Wrong certificate exposed

What happened?
An Ingress (with Pomerium Ingress Controller) exposes the authenticate Service with a cert-manager-generated certificate but this certificate is not provided to the http client. Instead a self signed certificate (used for communication between Pomerium component) is provided. As if it was a TLS passthrough, the Ingress doesn't terminate the TLS communication.
If I change the ingressClass of the Ingress (for traefik for example), the correct certificate is exposed.
What did you expect to happen?
The certificate defined in the Ingress resource should be exposed.
How'd it happen?

deploy an Ingress with Pomerium Ingress Controller and authenticate Service as upstream application.
curl the ingress
get a TLS error (self signed certificate)

What's your environment like?

Pomerium version (retrieve with pomerium --version): 0.16.2
Pomerium Helm chart : 29.0.1
Server Operating System/Architecture/Cloud: AWS EKS

What's your values.yaml
pomerium:
  config:
    rootDomain: domain.com
    policy: []
  authenticate:
    replicaCount: 3
    ingress:
      tls:
        secretName: pomerium-authenticate-cert
      annotations:
        cert-manager.io/cluster-issuer: letsencrypt-dns
    idp: {}
  proxy:
    replicaCount: 3
    service:
      annotations:
        service.beta.kubernetes.io/aws-load-balancer-type: "external"
        service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip"
        service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing"
        service.beta.kubernetes.io/aws-load-balancer-target-group-attributes: "deregistration_delay.timeout_seconds=60,stickiness.enabled=false"
        service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-healthy-threshold: "2"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-unhealthy-threshold: "2"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-timeout: "10"
        service.beta.kubernetes.io/aws-load-balancer-healthcheck-interval: "10"
        service.beta.kubernetes.io/aws-load-balancer-access-log-enabled: "false"
  ingressController:
    replicaCount: 3
    enabled: true
    config:
      ingressClass: pomerium.io/ingress-controller-external
    ingressClassResource:
      enabled: true
      name: pomerium-external
      controllerName: pomerium.io/ingress-controller-external
  metrics:
    enabled: true

What did you see in the logs?
It generates this Ingress :
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-dns
    ingress.pomerium.io/allow_public_unauthenticated_access: "true"
    ingress.pomerium.io/preserve_host_header: "true"
    ingress.pomerium.io/secure_upstream: "true"
    ingress.pomerium.io/tls_server_name: authenticate.domain.com
    ingress.pomerium.io/secure_upstream: "true"
  labels:
    app.kubernetes.io/instance: pomerium
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: pomerium
    helm.sh/chart: pomerium-29.0.1
    oi/appname: pomerium-external-kube-shared-nonprod
  name: pomerium-authenticate
  namespace: pomerium-external
spec:
  ingressClassName: pomerium-external
  rules:
  - host: authenticate.domain.com
    http:
      paths:
      - backend:
          service:
            name: pomerium-authenticate
            port:
              name: https
        path: /
        pathType: Prefix
  tls:
  - hosts:
    - authenticate.domain.com
    secretName: pomerium-authenticate-cert

@rguichard can you provide the logs from the ingress controller when it processes that Ingress resource?

Ingress controller
{"level":"info","ts":1644879449.631355,"logger":"controller.ingress","msg":"new pomerium config applied","reconciler group":"networking.k8s.io","reconciler kind":"Ingress","name":"pomerium-authenticate","namespace":"pomerium-external"

Pomerium proxy when I curl, sometimes I get 503, sometimes 302 to my IdP.
{"level":"info","service":"envoy","upstream-cluster":"pomerium-external-pomerium-authenticate-authenticate-shared-dev4apps-com-6ceaeb9bf3be8e62","method":"GET","authority":"authenticate.shared.dev4apps.com","path":"/.pomerium","user-agent":"curl/7.74.0","referer":"","forwarded-for":"<IP_ADDRESS>","request-id":"17e3fc3d-aecb-4137-8c66-65a2f8fc4b33","duration":1.540371,"size":91,"response-code":503,"response-code-details":"upstream_reset_before_response_started{connection_failure}","time":"2022-02-14T23:17:25Z","message":"http-request"}
{"level":"info","service":"envoy","upstream-cluster":"pomerium-external-pomerium-authenticate-authenticate-shared-dev4apps-com-6ceaeb9bf3be8e62","method":"GET","authority":"authenticate.shared.dev4apps.com","path":"/.pomerium","user-agent":"curl/7.74.0","referer":"","forwarded-for":"<IP_ADDRESS>","request-id":"abefec8f-4cc1-4014-9a89-373ae33af752","duration":106.438187,"size":612,"response-code":302,"response-code-details":"via_upstream","time":"2022-02-14T23:17:27Z","message":"http-request"}

I'm not able to reproduce this.  There are some minor tweaks to your original config but they should not be material in which certificate is served.  There's no reference to pomerium-tls in any resources that I can find.

Set up a self signed CA issuer per https://cert-manager.io/docs/tutorials/acme/pomerium-ingress/#configure-a-private-certificate-issuer
config:

config:
  rootDomain: localhost.pomerium.io
  policy: []
authenticate:
  replicaCount: 1 # changed
  ingress:
    tls:
      secretName: pomerium-authenticate-cert
    annotations:
      cert-manager.io/issuer: pomerium-issuer # use a self signed issuer to avoid needing a reachable LoadBalancer service
      ingress.pomerium.io/tls_skip_verify: "true" # due to using a self signed issuer rather than let's encrypt
  idp: {}
proxy:
  replicaCount: 1 # changed
ingressController:
  enabled: true
  config:
    ingressClass: pomerium.io/ingress-controller-external
  ingressClassResource:
    enabled: true
    name: pomerium-external
    controllerName: pomerium.io/ingress-controller-external
metrics:
  enabled: true

I have no pomerium-tls secret.  The values you have there would not use it since they do not specify an existingSecret or disable certificate generation.

% k get certificate
NAME                         READY   SECRET                       AGE
pomerium-authenticate-cert   True    pomerium-authenticate-cert   7m35s
pomerium-ca                  True    pomerium-ca                  30m

% kubectl get secret pomerium-authenticate-cert -o json | jq '.data."tls.crt"' -r | base64 -d | openssl x509 -text | md5sum
758366ffeb27d0c130982370e7fcbd05  -

% openssl s_client -connect authenticate.localhost.pomerium.io:443 | openssl x509 -text | md5sum
758366ffeb27d0c130982370e7fcbd05  -

I add a self signed cert to the cluster (without referencing it) copied from here:

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: pomerium-cert
  namespace: pomerium
spec:
  secretName: pomerium-tls
  issuerRef:
    name: pomerium-issuer
    kind: Issuer
  usages:
    - server auth
    - client auth
  dnsNames:
    - pomerium-proxy.pomerium.svc.cluster.local
    - pomerium-authorize.pomerium.svc.cluster.local
    - pomerium-databroker.pomerium.svc.cluster.local
    - pomerium-authenticate.pomerium.svc.cluster.local

% k get cert
NAME                         READY   SECRET                       AGE
pomerium-authenticate-cert   True    pomerium-authenticate-cert   10m
pomerium-ca                  True    pomerium-ca                  32m
pomerium-cert                True    pomerium-tls                 3s

I still get the correct cert:

openssl s_client -connect authenticate.localhost.pomerium.io:443 | openssl x509 -text | md5sum
758366ffeb27d0c130982370e7fcbd05  -

I'm not sure how to explain the behavior you're seeing but it appears to be specific to your environment, somehow.

Closing for now, pending more info on reproduction.

Hi, @travisgroth i am experiencing a similar issue.
In my case i use auto-generated certs for comms between services. In my case i use manually-generated letsencrypt certs.
just installed pomerium helm-chart version 31.0.1 hoping my problems with 421 are fixed, but no luck.
values for helm-chart:
config:
  sharedSecret: <redacted> # You can use "head -c32 /dev/urandom | base64" to generate.
  cookieSecret: <redacted> # You can use "head -c32 /dev/urandom | base64" to generate.
  rootDomain: example.com
  generateTLS: true # On by default, disabled when cert-manager or another solution is in place.
authenticate:
  existingExternalTLSSecret: authenticate-ingress-tls
  idp:
    provider: oidc
    clientID: pomerium
    clientSecret: pomerium
    serviceAccount: <redacted>
    url: <redacted>
    scopes:  openid,profile,email,phone,roles
  ingress:
    tls:
      secretName: authenticate-ingress-tls
resources:
  limits:
    cpu: 1
    memory: 600Mi
  requests:
    cpu: 100m
    memory: 300Mi
ingressController:
  enabled: true
proxy:
  existingTLSSecret: examplecom-wildcard-cert
  service:
    type: LoadBalancer
ingress:
  enabled: false

ingress resource generated by helm installation (get ingress -o yaml), getting it here as an example, all other apps on pomerium ingress behave the same.
apiVersion: v1
items:
- apiVersion: networking.k8s.io/v1
  kind: Ingress
  metadata:
    annotations:
      field.cattle.io/publicEndpoints: '[{"addresses":["<redacted>"],"port":443,"protocol":"HTTPS","serviceName":"pomerium:pomerium-authenticate","ingressName":"pomerium:pomerium-authenticate","hostname":"authenticate.example.com","path":"/","allNodes":false}]'
      ingress.pomerium.io/allow_public_unauthenticated_access: "true"
      ingress.pomerium.io/secure_upstream: "true"
      meta.helm.sh/release-name: pomerium
      meta.helm.sh/release-namespace: pomerium
    creationTimestamp: "2021-11-12T14:40:05Z"
    generation: 3
    labels:
      app.kubernetes.io/instance: pomerium
      app.kubernetes.io/managed-by: Helm
      app.kubernetes.io/name: pomerium
      helm.sh/chart: pomerium-31.0.1
    name: pomerium-authenticate
    namespace: pomerium
    resourceVersion: "103810960"
    uid: <redacted>
  spec:
    ingressClassName: pomerium
    rules:
    - host: authenticate.example.com
      http:
        paths:
        - backend:
            service:
              name: pomerium-authenticate
              port:
                name: https
          path: /
          pathType: Prefix
    tls:
    - hosts:
      - authenticate.example.com
      secretName: authenticate-ingress-tls
  status:
    loadBalancer:
      ingress:
      - ip: <redacted>
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Where both authenticate-ingress-tls and examplecom-wildcard-cert are located in pomerium namespace.

authenticate-ingress-tls with cert for authenticate.example.com
examplecom-wildcard-cert with cert for *.example.com and example.com

Whenever i access authenticate.example.com (or any other domain specified in ingress resources) i am served with the wildcard certificate.
If i unset proxy.existingTLSSecret in values i get served with auto-generated certificate which is rejected by my browser. - this makes me think i (almost) always am served with proxy certificate.
I encountered this problem when our testers wanted to access secured endpoints on safari. (i am trying to solve this problem https://github.com/pomerium/pomerium/issues/2150)

@travisgroth can we reopen the issue?

@travisgroth pinging again. Is the info I provided enough to start some investigation?

Possibly Related (and closed by) https://github.com/pomerium/pomerium/pull/3596
History:

https://github.com/pomerium/pomerium/issues/2150
https://github.com/pomerium/pomerium/pull/3596
https://github.com/pomerium/internal/issues/972

You need create a certificate for the authenticate endpoint.
Assuming the following:

you are using cert-manager to manage certificates in your cluster,
you have a letsencrypt-prod ClusterIssuer
your authenticate endpoint is authenticate.corp.com
you deployed pomerium using new recommended manifests + CRD method

Certificate spec:
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: pomerium-authenticate-tls
  namespace: pomerium
spec:
  dnsNames:
  - authenticate.corp.com
  issuerRef:
    group: cert-manager.io
    kind: ClusterIssuer
    name: letsencrypt-prod
  secretName: pomerium-authenticate-tls
  usages:
  - digital signature
  - key encipherment

the following should be added into your pomerium/global CRD:
apiVersion: ingress.pomerium.io/v1
kind: Pomerium
metadata:
  name: global
spec:
  authenticate:
    url: https://authenticate.corp.com
  certificates:
  - pomerium/pomerium-authenticate-tls


make the instance more clear

Tiny change: messy code clean up.
For University College London Software System Engineering Group research purpose.

 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.


Remove .

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@cazawideh PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


[Bug]: network_info_plus 3.0.2 WINDOWS NOT WORKING

https://ibb.co/qgHdcfW
please check this screenshot also
Platform
windows 11
Plugin
network_info_plus
Version
latest
Flutter SDK
latest
Steps to reproduce
not working on latest version of windows 10 , 11 ,,
please check
Thanks,
Code Sample
No response
Logs
ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: MissingPluginException(No implementation found for method wifiGatewayAddress on channel dev.fluttercommunity.plus/network_info)
#0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:313:7)
<asynchronous suspension>
#1      _MyhomeState.getValues (package:starr_pro_flutter/screens/dashboard_home.dart:138:25)
<asynchronous suspension>

Flutter Doctor
all good

Checklist before submitting a bug

[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

I got this problem when I using getWifiIP() at android.
Flutter version:
flutter --version
Flutter 3.7.8 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 90c64ed42b (6 weeks ago) • 2023-03-21 11:27:08 -0500
Engine • revision 9aa7816315
Tools • Dart 2.19.5 • DevTools 2.20.1

My code:
final info = NetworkInfo();
final String? ip = await info.getWifiIP();

Error message:
E/flutter (13448): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: MissingPluginException(No implementation found for method wifiIPAddress on channel dev.fluttercommunity.plus/network_info)
E/flutter (13448): #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:313:7)
E/flutter (13448): <asynchronous suspension>

bro its working fine on android. i am facing issues on windows 11

@vbuberen thank you, I will test it and get back to you tomorrow :)

@vbuberen
hello bro, I have tested your latest version 4.0.0
final wifiIP = await info.getWifiIP(); // <IP_ADDRESS>
it's working fine on Windows 10 and 11, but getwifiname method is not working it's returning null.
and it will work only if we connect to wifi, if the computer is connected with a LAN cable, it's returning null.
Thanks, for the help
great work.
Thank you


Add bdelete functionality

Implements #527
Added a new key mapping gd to delete the current NERDTree file node's buffer, even if it's not currently active in a window. If that file is not open, there is no error. In all cases, an appropriate message is displayed, indicating success or failure.
Tested on console version only:

Windows, vim 7.4
Mac OSX, neovim 0.1.1

I'm closing this request. I implemented this functionality as a NERDTree plugin: https://github.com/PhilRunninger/nerdtree-bwipeout-plugin


it's a good idea to create a new package for sc-deployer, we should de the same for sc-compiler, maybe later in another issue/pr

    it's a good idea to create a new package for sc-deployer, we should de the same for sc-compiler, maybe later in another issue/pr

Originally posted by @Thykof in https://github.com/massalabs/massa-sc-toolkit/pull/69#discussion_r1056392035

blocked by https://github.com/massalabs/massa-sc-toolkit/pull/69


Handle multiple output .d.ts files changedness correctly

Fixes #25337 and gets rid of a bad type assertion

We probably need a unit test to cover the scenario in #25337

The new file in the PR tests that scenario


Show ENS Avatar or Generated/Random Image

Right now, it says I am a cat. I am not a cat

https://wagmi.sh/docs/hooks/useEnsAvatar

I disagree. Drake is a cat.

did you actually just link me to docs sir

https://wagmi.sh/docs/hooks/useEnsAvatar

did you actually just link me to docs sir

I think this has been taken care of in #6. Please confirm.


docs(SEO): Consistent taglines, titles, description and instant-search usage

fixes #1817
cc @neilrichler

@vvo Maybe you can surge.sh a version of the website :)

We do not yet have the needed script eheh :)


Nextflow expects pos_sp_nt_freq.tsv when do_pos_sp_nt_freq is false

As described in example-datasets/#4 : https://github.com/riboviz/example-datasets/issues/4#issuecomment-696723426
Cryptococcus dataset JEC21 not running via nextflow on Eddie, as it's giving an error relating to expected pos_sp_nt_freq.tsv file being missing.
If do_pos_sp_nt_freq is FALSE, I don't think that should be expected.

For our purposes, this is mostly a problem because it prevents nextflow continuing to the next step of the pipeline and executing collateTpms

@FlicAnderson  wrote...
I finally got one of my jobs to complete on Eddie, but it's failed and I'm having trouble locating which part exactly is responsible for the failure.
It's the Cryptococcus JEC21 dataset, and so running fullsize data, and using system links to scratch and the input files etc. I don't think that those are anything to do with the failure, and seem to be working ok so far!
I think the problem lies possibly in the nextflow code? Potentially something around how it might be expecting an output file "pos_sp_nt_freq.tsv" despite the fact "do_pos_sp_nt_freq" is set to false in the .yaml?  The error does ping up in the generateStatsFigs process though, so I checked that first in case of any issues.
For reference, the riboviz branch was a days-old-if-that develop.
In the output for the job I got this:
N E X T F L O W  ~  version 20.04.1
Launching `prep_riboviz.nf` [furious_mestorf] - revision: 62d3b58c5d
Validating configuration only
Validated configuration
N E X T F L O W  ~  version 20.04.1
Launching `prep_riboviz.nf` [clever_minsky] - revision: 62d3b58c5d
[21/dbc8a3] Submitted process > buildIndicesrRNA (JEC21_rRNA)
# ... lots of processes happening as usual...
[d9/ada46b] Submitted process > generateStatsFigs (JdAGO1)
[f0/646ed1] Submitted process > samViewSort (JEC21)
[d9/ada46b] NOTE: Missing output file(s) `pos_sp_nt_freq.tsv` expected by process `generateStatsFigs (JdAGO1)` -- Error is ignored
[d2/69c0a5] Submitted process > outputBams (JEC21)
[d9/2e5534] Submitted process > makeBedgraphs (JEC21)
[3b/0746af] Submitted process > bamToH5 (JEC21)
[35/6e194f] Submitted process > generateStatsFigs (JEC21)
[35/6e194f] NOTE: Missing output file(s) `pos_sp_nt_freq.tsv` expected by process `generateStatsFigs (JEC21)` -- Error is ignored
No sample was processed successfully

I figured that this means that generate_stats_figs.R might have failed, but checking out the .command.log file for the generateStatsFigs (JEC21) 35/6e194f process as an example, it seems to have run as normal and completed:
[1] "Created by: RiboViz"
[1] "Date: 2020-09-20 11:29:48"
[1] "File: /exports/eddie3_homes_local/fanders6/riboviz/riboviz/rscripts/generate_stats_figs.R"
[1] "Version: commit 9e41fb6854d93799edc037c7190429aa574dd0a1 date 2020-09-16 09:40:36 GMT"
[1] "generate_stats_figs.R running with parameters:"
$output_dir
[1] "."

$orf_fasta_file
[1] "JEC21_10p_up12dwn9_CDS_with_120bputrs.fa"

$orf_gff_file
[1] "JEC21_10p_up12dwn9_CDS_120bpL_120bpR.gff3"

$num_processes
[1] 32

$min_read_length
[1] 10

$max_read_length
[1] 50

$buffer
[1] 30

$primary_id
[1] "Name"

$dataset
[1] "Wallace_2020_JEC21"

$rpf
[1] TRUE

$features_file
[1] NA

$do_pos_sp_nt_freq
[1] FALSE

$t_rna_file
[1] NA

$codon_positions_file
[1] NA

$count_threshold
[1] 1

$length_threshold
[1] 500

$output_prefix
[1] ""

$hd_file
[1] "JEC21.h5"

$nnt_buffer
[1] 25

$nnt_gene
[1] 50

$asite_disp_length_file
[1] NA

$help
[1] FALSE

[1] "Starting: Check for 3nt periodicity globally"
`summarise()` ungrouping output (override with `.groups` argument)
`summarise()` ungrouping output (override with `.groups` argument)
Saving 7 x 7 in image
[1] "Starting: Check for 3nt periodicity globally"
`summarise()` ungrouping output (override with `.groups` argument)
`summarise()` ungrouping output (override with `.groups` argument)
Saving 7 x 7 in image
[1] "Completed: Check for 3nt periodicity globally"
Warning message:
In write.table(three_nucleotide_periodicity_data, file = tsv_file_path,  :
  appending column names to file
[1] "Starting: Distribution of lengths of all mapped reads"
Saving 7 x 7 in image
[1]Warning message:
In write.table(read_length_data, file = tsv_file_path, append = T,  : "Completed: Distribution of lengths of all mapped reads"
[1] "NOT calculating position-specific nucleotide frequency - reason: do_pos_sp_nt_freq parameter set to FALSE"
[1] "NOT checking for 3nt periodicity (frame) by gene - reason: asite_disp_length_file parameter not provided"
[1] "Starting: Position specific distribution of reads"
  appending column names to file
Saving 7 x 7 in image
Warning message:
In write.table(pos_sp_rpf_norm_reads_data, file = tsv_file_path,  :
  appending column names to file
[1] "Completed: Position specific distribution of reads - RPF method"
[1] "Completed: Position specific distribution of reads"
[1] "Starting: Calculate TPMs of genes"
[1]Warning message:
In write.table(tpms, file = tsv_file_path, append = T, sep = "\t",  :
  appending column names to file
 "Completed: Calculate TPMs of genes"
[1] "Skipped: Correlations between TPMs of genes with their sequence-based features - features_file.tsv not provided"
[1] "Skipped: Codon-specific ribosome densities for correlations with tRNAs - t-rna-file and/or codon-positions-file not provided"
[1] "Completed generate_stats_figs.R"

The .exitcode file contains a 0, which means that there wasn't an issue, I think?
.command.err for that process contained just the usual warning message lines about write.table and so on, nothing unusual.
Is there something in the nextflow code that perhaps expects pos_sp_nt_freq.tsv file to be created, even though this shouldn't be an expected output if do_pos_sp_nt_freq is set to FALSE?  I was trying to unpick what's going on in process generateStatsFigs in prep_riboviz.nf but I'm still not quite sure.
Should the line in prep_riboviz.nf  process generateStatsFigs output:
tuple val(sample_id), file("pos_sp_nt_freq.tsv") \ into pos_sp_nt_freq_tsv

instead be something like:
tuple val(sample_id), file("pos_sp_nt_freq.tsv") \ optional (! do_pos_sp_nt_freq) \ into pos_sp_nt_freq_tsv

?  And if that's something along the right lines, are there any other edits that would need to be made?

@mikej888  thanks for adding my problem notes!  Hope they make sense so far?

@FlicAnderson, Almost spot on with your fix :-) The fix is:
         tuple val(sample_id), file("pos_sp_nt_freq.tsv") \
           optional (! params.do_pos_sp_nt_freq) \
           into pos_sp_nt_freq_tsv

The params. prefix is required because the flag comes straight from the YAML file. The other optional outputs are based on variables created within prep_riboviz.nf itself.

I've commited the fix to develop.

The same pattern applies for any other optional outputs from any processes. If an output is not marked as optional then Nextflow checks that the file exists after its command (in this case generate_stats_figs.R) completes and will fail (even if the command itself succeeded).

shakes fist at sky SO CLOSE!!! :grin:
Thanks, I'll give the fix a bash.
Your params. explanation makes total sense, cheers :+1:

Currently testing this fix in latest run with Cryptococcus datasets, will update if/when it works & can close since it's merged to develop already.

Closing this since it's working with the Cryptococcus datasets and already merged.


Change to use C#7 async Main

@pcmichaels Thank you for the contribution, and I'm sorry it has taken so long to get back to you. I have tested this tutorial extensively, and it seems to work exactly as written. I tried your changes, but got compiler errors. Can you clarify exactly what you're trying to do here?

@sethmanheim Have you compiled it under C# 7.1+?  It's basically trying to leverage the new async Main functionality available for console apps.

@pcmichaels I am simply building the tutorial as it's written, using VS 2017 and the Visual C# Compiler version <IP_ADDRESS>329.

@sethmanheim It would need to target 7.1+, as that was when async main was introduced.


KAFKA-15355: Message schema changes

Schema changes in API messages and metadata records for KIP-858.
https://issues.apache.org/jira/browse/KAFKA-15355
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I am putting myself as a reviewer because I would like to keep up to date with these changes. I will aim to provide my review tomorrow!

Thanks for the review @clolov

Thanks for the PR, @soarez ! Do you have revisions ready for this one or do you want one of us to jump in and fix these comments like we talked about earlier? I feel like it's really close now 👍

Thanks for the review @cmccabe. Sorry it took me a bit longer to update this.

do you want one of us to jump in and fix these comments like we talked about earlier

I'm not sure I understand what you're proposing, but in general: any help to get this over the line is welcome and much appreciated. 👍
I've switched the partition record schema changes to include a new LogDirs field instead of replacing the Replicas field. I've also brought in the changes from #14516 as Ron suggested, and the reserved UUID renames you suggested in the voting thread from #14517. So both of those other PRs can be closed.
@rondagostino , @pprovenzano  PTAL

LGTM too!

Failing tests are unrelated.

Should have included the below information as additional description in the commit to trunk -- I forgot to.  Damn.
Schema changes in API messages and metadata records for KIP-858.
https://issues.apache.org/jira/browse/KAFKA-15355


Increment version to 1.3.12

Description
Version Bump from 1.3.11 to 1.3.12
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Not sure if the version number at line needs to be incremented as well.
@prudhvigodithi

Not sure if the version number at line needs to be incremented as well. @prudhvigodithi @gaiksaya

Checked 2.x and main, it needs to be incremented

Hey @ohltyler and @amitgalitz can you please check with node incompatible error? This error is causing issues to automation in raising the version increment PR's for anomaly-detection-dashboards-plugin repo.
@bbarani @peterzhuamazon
Thank you

The complaining dependency was added in a CVE fix: https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/pull/567/files

The complaining dependency<EMAIL_ADDRESS>was added in a CVE fix: https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/pull/567/files, same error seen there.

Looks like that PR was merged with failing CI. Is it expected to fail or will this be an issue when we build distribution too?

The complaining dependency<EMAIL_ADDRESS>was added in a CVE fix: https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/pull/567/files, same error seen there.

Looks like that PR was merged with failing CI. Is it expected to fail or will this be an issue when we build distribution too?

Yeah it should be passing, I see some weird conflicts that I had to resolve in the dependency, I will open a working PR while I continue looking at the exact root cause

Closing in favor of #582


[bug] html template outputs static attributes onto wrong element, deletes elements

In this example, the attributes from the <lume-camera-rig> element are placed onto the root <lume-scene> element in the output DOM:
https://playground.solidjs.com/?hash=-1630892593&version=1.3.16
I was trying to simplify it further, but then in this simpler example the root <lume-scene> element is entirely removed and leaves the <lume-node> element as the root:
https://playground.solidjs.com/?hash=488900709&version=1.3.16

Not sure what exactly triggers it yet, but if I remove all hyphens, then no DOM is output at all:
https://playground.solidjs.com/?hash=881513018&version=1.3.16

I think I know the cause. It doesn't like partial attribute interpolation. It basically follows JSX rules. This works I think: https://playground.solidjs.com/?hash=1449697475&version=1.3.16.
I never got around to adding this capability probably didn't even realize because I used it like JSX.

Indeed that was it! Seems there are two separate issues. Here is one with no partial attribute interpolation, in this one no DOM outputs:
https://playground.solidjs.com/?hash=589409240&version=1.3.16

I imagine that foo="blah${blah}blah" could be detected then treated the same as foo=${'blah' + blah + 'blah'}

On a similar note, I had syntax like <div foo="${blah}>, which has a missing quote. Perhaps it can also throw errors on unexpected syntax?


Check data error in cal_mean_variance

Hi, I got exactly the same problem as #16 in motion_representation:
Here is the output of motion_representation, just the same as #16 and #12

However, for cal_mean_variance.ipynb, the error seems large:

Is this normal or something goes wrong?

Exactly same error in motion_representation, but with

in cal_mean_variance.ipynb
btw: a warning occurred while running motion_representation, not encountered in .ipynb file. Does this matters?


Proposal: Integration of Dynamic Language Translation Management

Proposal: Integration of Dynamic Language Translation Management
Objective
The objective of this proposal is to integrate a dynamic language translation management system into our project, enhancing user experience by allowing seamless updates and localization of application text content without requiring app updates.
Background
Currently, our application uses static language files bundled within the app. This approach poses challenges in updating translations and adapting to user preferences dynamically. By implementing a dynamic language translation management system, we can provide users with up-to-date translations and support multiple languages more efficiently.
Proposal Details
1. Translation Service Integration

Implement a TranslationManager class that handles fetching translations from a remote server.
Utilize JSON files hosted on a server to store translations for each supported language.
Include versioning in the JSON files to manage updates and ensure consistency across devices.

2. Dynamic Language Switching

Allow users to switch languages dynamically within the app.
Store the user's preferred language locally using UserDefaults to maintain language preferences across sessions.
Load translations based on the selected language, falling back to a default language (e.g., English) when translations are not available.

3. Translation Update Mechanism

Implement a mechanism to periodically check for updates to translation files based on versioning.
Provide options for manual and automatic updates to ensure users have access to the latest translations.

4. User Interface Integration

Modify the UI components to support dynamic language switching.
Implement localized string handling using extensions or utility classes to simplify integration across the project.

5. Testing and Validation

Conduct thorough testing to ensure seamless integration and functionality across different language settings.
Test scenarios include language switching, update checks, fallback to default language, and UI responsiveness to language changes.

6. Performance Considerations

Optimize the translation fetching and updating processes to minimize network usage and ensure smooth performance.
Implement caching strategies to store translations locally and reduce load times for frequently accessed content.

Benefits

Improved User Experience: Users can interact with the app in their preferred language without waiting for app updates.
Scalability: Easily add new languages and update translations without modifying the core app code.
Efficiency: Reduce app size by removing bundled language files and dependencies on static content.

Conclusion
Integrating dynamic language translation management into our project will significantly enhance user satisfaction and operational efficiency. This proposal outlines the steps, benefits, and timeline for implementing this feature. Your approval and support are crucial to successfully delivering this enhancement to our users.

Thanks for submitting a issue!
to assign this issue to yourself please comment @aurora-care-bear please assign me


support for "prompt attention"

To fully customize prompts, there is a "hack" that popular versions of stable diffusion use to allow you to increase/decrease the strength of each token using parens/square brakets
lpw_stable_diffusion.py is an implementation for this within diffusers.
def parse_prompt_attention(text):
    """
    Parses a string with attention tokens and returns a list of pairs: text and its associated weight.
    Accepted tokens are:
      (abc) - increases attention to abc by a multiplier of 1.1
      (abc:3.12) - increases attention to abc by a multiplier of 3.12
      [abc] - decreases attention to abc by a multiplier of 1.1
      \( - literal character '('
      \[ - literal character '['
      \) - literal character ')'
      \] - literal character ']'
      \\ - literal character '\'
      anything else - just text

This might be fairly straightforward to add to the default template

looks like the code mentioned in #26 also supports this ... it might be a good combo


Taskbar Icons disappear

Mostly, when I (re-) start the computer, after 1-2 min all taskbar icons disappear on one monitor, on the other one they are still there. If I restart TaskbarX, they come back.
Thanks for your help

Can you try this? https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


wasi: allow users to configure a filesystem that can accept new files

WASI defines portable system calls to manipulate files. We currently use fs.FS to map to many of these. read-only operations are implicit, but the status quo goes beyond this in the standard library.
For example, fs.FS can write existing files as implementations are free to go beyond the functionality defined on fs.File. Some of this is encouraged. Concretely, os.File goes beyond with mutations such as chmod and write. os.FS
Also, there are standard extensions to fs.FS including fs.ReadDirFS. The point is that in many cases, there is an existing mapping of a go interface to WASI functions, even if it isn't required by fs.FS. By safe casts, you can get most functionality needed.
However, there are gaps, notably creating new files. This issue is solved when the core WASI APIs requested by end users have a corresponding implementation. This is ideally done without introducing any wazero-specific interfaces. As such research is needed and validation is needed prior to introducing an interface not in Go's standard library.
Moreover, as the README suggests, completion of all WASI functions is a non-goal. In other words, if there is a tricky API, and hasn't been asked directly by end-users yet.. wait until that's the case, then solve it. WASI is completely changing its filesystem API so we can conserve energy by only focusing on what users need today.
Solving this issue is a high priority and 1.0 will be held back until it is solved. However, it is likely this will be solved way before 1.0, like in a week or two.
References:

Go has an issue tracking approaches to weave in write support to fs.FS https://github.com/golang/go/issues/45757
Last year,  @Gaboose added a toe-hold implementation of many WASI features including a MemFS https://github.com/tetratelabs/wazero/pull/22 This was maintained over time, but we completely redid our API. Reads are now via fs.FS despite limitations of that.
Recently, @nullpo-head attempted to make an extension of fs.FS in https://github.com/tetratelabs/wazero/pull/362 with some custom APIs to add write support to it. This was closed out because it coupled read-side with writes and the former is easier to implement. This issue was raised to carry that forward.
https://github.com/golang/go/issues/45757 is a gold mine of insight both in what people are thinking about and their use cases. One example of a linked issue is https://github.com/mvdan/sh/pull/799 which summarized to thinking that sharing the same interface of fs.FS for writes may be faulty. This is the main reason why this is a separate issue, to do thorough research and consider a completely different path for exposing writes as needed, even if internally we share a base fs.FS impl.

I completely rewrote the description as the gap here is much smaller than I originally thought. While fs.FS doesn't specify extended APIs it is routine in practice to already support writes (ex os.File).

Does that mean that it is possible to write new files from Wasm?
I have tried using the open syscall in WASI for non-existing files with writing mode, but it fails.

@mmathys exactly. in fact this it is about time we got back to this one. if you don't mind, as it is usually interesting.. what's the use case you are working with that needs to open for writing? is it a log or config file? or are you sharing data?

@ncruces noted in #740 that there's a corner case in the io.Reader docs hard to reason with when mapping to io.Reader based implementation of fdread

Callers should always process the n > 0 bytes returned before considering the error err. Doing so correctly handles I/O errors that happen after reading some bytes and also both of the allowed EOF behaviors.

https://pkg.go.dev/io#Reader
The "process the n > 0 bytes returned before considering the error err" ends up a bit dodgy as you have a choice to ignore that part or create expense by holding per-fd state to return the error when >n bytes are read.

Looking at the issue and current implementation, I don't think there's anything missing from wazero in this regard.
For instance, if you use os.DirFS you'll get a read-only view into a directory and, from what I could tell, you won't be able to create or modify any files.
But you don't have to use os.DirFS, you can create a copy of it that does OpenFile with O_RDWR here, then with the current implementation you'll have writeable files in your WASI.
Or you can create an implementation that, instead or returning fs.ErrNotExist for a missing file, os.Creates one. With this, you should already able to write new files, no?
Or you don't create an actual os.File, but your own “file” object, that's a thin wrapper around a bytes.Buffer. Then you get memory backed writeable files.
Now, all this has subtleties, but it seems doable, and not something wazero needs to provide out-of-the-box.
As an example, for my usage I wanted to lock my WASM even harder, so I created a file system that can only ever open a single file (not an entire directory).

To fix this, I just replaced instances of
f, err := c.fs.Open(fsOpenPath)

by
f, err := os.OpenFile(fsOpenPath, os.O_APPEND|os.O_CREATE|os.O_RDWR, 0644)

and I get a writable FS.

The first way we'll implement this is via a new ModuleConfig which allows you to pass a path instead of an fs.FS. When that's the case, we'll use os.OpenFile after coercing WASI flags to go ones. This will happen by our next pre-release, and likely in the next day or two.

Awesome!

https://github.com/tetratelabs/wazero/releases/tag/v1.0.0-pre.6 adds writefs.NewDirFS, which lets you add new files. We'll track pluggability of this in another issue.

https://github.com/tetratelabs/wazero/releases/tag/v1.0.0-pre.6 adds writefs.NewDirFS, which lets you add new files. We'll track pluggability of this in another issue.

This is awesome!

This is awesome!

Great work!

Great work!

If someone is looking for it now and hits this issue and wonders, where it is; it's in
github.com/tetratelabs/wazero/experimental/sys
<EMAIL_ADDRESS>https://github.com/tetratelabs/wazero/blob/08998eda2dd0efbb22cdff78df650ad1f7c8cc10/experimental/sys/fs.go#L29

See #2076


chore: bump unstructured to 0.7.8

Does this make this PR irrelevant? Bump version of unstructured-inference and unstructured

Looks like a 0.7.8 got in there before yours so you'll want to start a 0.7.9 on that branch

Makes sense to me! Once that's merged in I can bump this again.


Returning a null smart pointer from C++ does not return a nil object

When called from Lua, the following function returns an object rather than nil:
static std::shared_ptr<int> TestPtr()
{
    return nullptr;
}

It appears to go through value_converter::to_lua, which calls make_value_instance with a null pointer check anywhere.
Can you recommend a way to fix this behavior?
Thanks!

I suspect
if (!p) {
    lua_pushnil(L);
    return;
} else {
   /...
}

in shared_ptr_converter.hpp will do the trick. Since I need to be careful with changes, I would ask you to try that out manually until I'm confident I'm not breaking anything ;)

This doesn't work unfortunately, because value_converter is being used instead of shared_ptr_converter. Here's the call stack:
 	luabind::detail::make_value_instance<std::shared_ptr<int> >(lua_State * L, std::shared_ptr<int> && val, std::integral_constant<bool,1> __formal) Line 107	C++
 	luabind::detail::make_value_instance<std::shared_ptr<int> >(lua_State * L, std::shared_ptr<int> && val) Line 164	C++
 	luabind::detail::value_converter::to_lua<std::shared_ptr<int> >(lua_State * L, std::shared_ptr<int> && x) Line 49	C++
 	luabind::detail::invoke_struct<luabind::meta::type_list<>,luabind::meta::type_list<std::shared_ptr<int> >,std::shared_ptr<int> (__cdecl*)(void)>::call_struct<0,0,luabind::meta::index_list<> >::call(lua_State * L, std::shared_ptr<int> (void) * & f, std::tuple<> & argument_tuple) Line 389	C++
 	luabind::detail::invoke_struct<luabind::meta::type_list<>,luabind::meta::type_list<std::shared_ptr<int> >,std::shared_ptr<int> (__cdecl*)(void)>::invoke(lua_State * L, const luabind::detail::function_object & self, luabind::detail::invoke_context & ctx, std::shared_ptr<int> (void) * & f) Line 516	C++
 	luabind::detail::invoke<luabind::meta::type_list<>,luabind::meta::type_list<std::shared_ptr<int> >,std::shared_ptr<int> (__cdecl*)(void)>(lua_State * L, const luabind::detail::function_object & self, luabind::detail::invoke_context & ctx, std::shared_ptr<int> (void) * & f) Line 533	C++
	luabind::detail::function_object_impl<std::shared_ptr<int> (__cdecl*)(void),luabind::meta::type_list<std::shared_ptr<int> >,luabind::meta::type_list<> >::entry_point(lua_State * L) Line 82	C++

In invoke_struct<>::call_struct<> it references traits::result_converter, which is a value_converter instead of a shared_ptr_converter. It looks like the issue stems from how invoke_traits<Signature, PolicyList> chooses its result_converter type, but this is where it gets a little too in-the-weeds for me to follow.

Okay, it was only one step to solve this issue. shared_ptr_converter.hpp is not included in default_policies.hpp, so the shared_ptr-default_converter specialization is not available for the compile. You can include it manually in the meanwhile, I will add the include to default_policies.hpp.

The test also includes the converter policy manually. It might be a deliberate design decision, though I can't find a reason not to enable it by default.

So, this issue extends to custom smart pointer types that are implemented by specializing get_pointer<> (as was done in the original Luabind as as still exists in the docs).
I've already observed that in this version implementing a custom smart pointer currently requires also implementing detail::has_get_pointer_::get_pointer and detail::pointer_traits<> in addition to get_pointer<>. Is adding a default_converter<> implementation then also an additional required step in order to handle this return value case?

Oh I'm sorry for misleading you. That shared_ptr converter shows special behaviour that we don't really need here. It's been a while...
Okay, now to the true thing: The value_converter is actually really responsible for this, it is okay being hit, because it detects if the value supports get_ptr(). It does not check wether the pointer being held is null though (see make_instance.hpp lines 98 following).
I dont know if this is an "understandable" design setup really. Need to think about decoupling value_converter and automatic smart pointer handling... But for the time being this would be the spot.
Now I'm not really sure if it is okay to push nil there, I will check if  cpp -> lua -> cpp still works as intended. But I'm off for a walk now before it gets dark... so that will take a few hours maybe.

I'll give it a try as well. Looks like it should work so long as it comes at the very top of the function (before the call to get_dynamic_class which will attempt to dereference a null pointer).

Okay, we're touching object_rep and instance_holder here, two of which I really want to reimplement as they're wasting space and destroy memory locality...
If only looking on the C++ side it's simple to solve, but doing class inheritance from the lua side complicates things, as object_rep really needs two phase object and payload construction. Getting this sorted out will also make it possible to implement move semantics... I hope the temporary fix you're trying holds for the moment?

It appears to. I am closing the issue. Look forward to your updates. :)


Concatenating make-commands fails

The current setup int he MAKEFILE defines the following type of command:
pano-wordlist:
	edictor wordlist --data=cldf-data/oliveiraprotopanoan/cldf/cldf-metadata.json --preprocessing=data/panoan_prep.py --addon="cognacy:cogid","alignment:alignment" --name=data/panoan
pano-reconstruction:
	python example-1.py Panoan
pano-pdf:
	pandoc -i panoan.md -o panoan.pdf --pdf-engine=xelatex
pano: pano-wordlist, pano-reconstruction, pano-pdf

Individually, the commands pano-wordlist, pano-reconstruction, and pano-pdf run fine. But the final command, pano, throws the following error:
(fuzzy) blum@lingn45 examples % make pano
make: *** No rule to make target `pano-wordlist,', needed by `pano'.  Stop.
(fuzzy) blum@lingn45 examples % make pano-wordlist
edictor wordlist --data=cldf-data/oliveiraprotopanoan/cldf/cldf-metadata.json --preprocessing=data/panoan_prep.py --addon="cognacy:cogid","alignment:alignment" --name=data/panoan
2023-10-12 09:31:13,058 [INFO] Data has been written to file <data/panoan.tsv>.

Am I missing something? Should we rather create a single command for each language, that runs all the code?

It looks like the commas separating targets in the pano:  line are not needed.


Feature request: pipe

It would be great if the masking functionality could be used without forms, perhaps as a pipe or service.
Use case: Form in read-only mode are displayed as plain text values

Sorry, my available time to this project is very limited and I can't do this.


Feature/bmauer/fixes #2149

This PR updates the arithemetic expression parser to use the new field utilities to work ons fields, rather than arrays. This means it can now work in a rank/type agnostic fashion which crucial for future development since ExtDataDriver.x makes use of this extensively and was limited to 2D/3D gridded fields without this.
In addition I found several bugs in the new field utilities. These were:

The binary operator template had a bug, and the test was not working to catch it which I quickly found when trying to use these in the expression parser.
The field clone function had been improperly implemented in the initial fieldBlas implementation and moreover the test that had been added for it that wasn't actually added with an @test nor even if it had been was it doing anything. This function was implemented and a proper test was added.
The initial testing framework in the geom directory never even added a way to create and test fields with ungridded dimensions for some bizarre reason. I added that.

This also requires 2 new features to the field geom class:

I added a "**" operator to the binary operators as this was necessary for the expression parser.

A "broadcast" copy, the idea is if you want to copy field x of rank x_r to field y of rank y_r, if y_r = x_r + 1 and the shape of the first x_r dimensions in field y matches field x, then copy the pointer from x to y and replicate x along the last dimension of y. This is 110% crucial for ExtDatDriver.x and without this I would be hosed and this is non-negotiable for inclusion.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[X] I have tested this change with a run of GEOSgcm (if non-trivial)
[X] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[X] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Yes I see the gfortran test is failing. I will see what is going on and fix.

ok, fixed gnu on Discover, lets see what the CI does.


PostgreSQL error failed to retrieve PostgreSQL server_version_num: tlsv1 alert protocol version

Hello
Summary
I am trying to connect to a postgres v11 Managed Database from my plataform Provider (Digital Ocean) and apparently it requires a ssl connection or something with the version of TLS, but even when I set the config I can not get to run kong. I have tested with docker too and I get the same error...
Steps To Reproduce

Installed Kong via apt repositories on a recently created Ubuntu v20 server following this
https://docs.konghq.com/install/ubuntu/
I have changed default config and created the .conf file

cp kong.conf.default kong.conf
database = postgres
pg_user = kong
pg_database = kong

pg_host = MY_URL
pg_port = MY_PORT
pg_password = MY_PASSWORD # generated by D.O.
pg_ssl = on
pg_ssl_version=TLSv1.2

# I am not sure how to set this, but even commeted out don't do what I expect
pg_sslmode=require
PGSSLMODE=require
sslmode=require

# this too, not sure which one should do the trick
ssl_protocols=TLSv1 TLSv1.1 TLSv1.2 TLSv1.3
ssl_min_protocol_version=TLSv1 TLSv1.2 TLSv1.2 TLSv1.3
nginx_http_lua_ssl_protocols=TLSv1 TLSv1.1 TLSv1.2 TLSv1.3

lua_ssl_trusted_certificate = /PATH-TO-CERT/ca-certificate.crt  # this is from DO too, I have commented out too

I have created the user, database, I added kong as owner of the database kong
the I run
kong migrations bootstrap  -c kong.conf --v
I installed postgres-client on the server and can connect fine to the database with this user, the problem arise when kong tries to connect

Additional Details & Logs

Kong version 2.3.2, openssl version is OpenSSL 1.1.1f  31 Mar 2020
Operating system: Ubuntu 20.04
Kong debug-level startup logs:  Can not get to run migrations, so I have not run this command yet
Kong error logs:

2021/03/09 14:09:00 [warn] 68949#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:09:30 [warn] 68967#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:09:53 [warn] 68985#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:10:20 [warn] 69003#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:11:27 [warn] 69021#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:12:01 [warn] 69039#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:29:51 [warn] 69069#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6
2021/03/09 14:37:43 [warn] 69089#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:6

I have seen this with no luck
https://support.konghq.com/support/s/article/Unable-to-connect-to-a-Postgres-DB-using-TLS-1-2
I have contacted DO support but since I can connect from the droplet correctly they say it's not at their end..
Much appreciated any help please...

Hello,
Sounds like https://github.com/Kong/kong/issues/6645 to me. The upcoming 2.4.0 release should fix this issue.
In the meantime, if you are in a hurry you can give https://github.com/Kong/kong/releases/tag/2.4.0-rc.1 a try which already contains the fix for this.


Notification not received on Android when application is dead

I made a custom notification when a specific kind of data arrives from server, but it only works when the application is alive (be it foreground or background). For this, I tested setting OneSignal.inFocusDisplaying(0); and OneSignal.inFocusDisplaying(2);.
When in foreground, everything runs smooth: the notification is received, the data is processed and a modal is shown to the user.
When in background, I still have a little problem: the notification is received, the data is processed and the modal is created and shown on the screen; the problem is that no notification appears on the tray in a way that the user has no idea of what happened. This occured with both inFocusDisplaying 0 and 2.
The real problem is when the application is dead, because no notification is shown. I checked #341, but I still need this custom notification to be built and shown on screen. Is there a way to do so?
Versions:

"react": "16.0.0",
"react-native": "0.51.0",
"react-native-onesignal": "3.1.1",

@lucasharada this is quite unusual.
Silly question, but are you sure you don't have Do-Not-Disturb enabled on the device?
Here are the different types of notification display modes:
0: ** None** It is up to your application to show the notification when the application is open. Whenever your application is closed or in the background, however, the system should still show the notification.
1: In-App Alert The SDK will show an in-app alert whenever a notification is received if the app is running in the foreground. However if the app is closed or in the background, the system will show the notification.
2: ** System** Lets the system handle whether or not the notification is shown.

@Nightsd01 Do-Not-Disturb is disabled. I already tested this on 2 devices, but the output is the same. The notification is only received when the application is alive.
Based on your explanation, the display mode I need is the None (0), so I can threat it when the application is open, but let the system handle it when application is dead.
Here is the piece of code related to the OneSignal feature:
import React, { Component } from 'react';
import { View } from 'react-native';
import OneSignal from 'react-native-onesignal';

import RootNavigator from './RootNavigator';
import GiftModal from './modals/GiftModal';

// Mocked data to be received with Notification additionalData
const test = require('./TestGift.json');

OneSignal.configure({});

class RootComponent extends Component<{}> {

  state = {
    modalVisible: false,
    activeModalImage: null,
    activeModalEstablishmentName: null,
    activeModalTitle: null,
    activeModalDescription: null
  };

  componentWillMount() {
    OneSignal.inFocusDisplaying(0);
  }

  componentDidMount() {
    this.onReceived = this.onReceived.bind(this);
    this.onOpened = this.onOpened.bind(this);

    OneSignal.addEventListener('received', this.onReceived);
    OneSignal.addEventListener('opened', this.onOpened);
  }

  componentWillUnmount() {
    OneSignal.removeEventListener('received', this.onReceived);
    OneSignal.removeEventListener('opened', this.onOpened);
  }

  onReceived(notification) {
    console.log('Notification received: ', notification);
    // console.log('Test file: ', test);

    // const data = notification.payload.additionalData;
    const data = test;
    if (data.type === 'gift') {
      this.setState({
        activeModalImage: data.Gift.Image,
        activeModalEstablishmentName: data.Gift.Name,
        activeModalTitle: data.Gift.Title,
        activeModalDescription: data.Gift.Description
      });
    }
  }

  onOpened(openResult) {
    console.log('Message: ', openResult.notification.payload.body);
    console.log('Data: ', openResult.notification.payload.additionalData);
    console.log('isActive: ', openResult.notification.isAppInFocus);
    console.log('openResult: ', openResult);
    this.setState({
      modalVisible: true
    });
  }

  hideModal() {
    this.setState({ modalVisible: false });
  }

  formatDate(date) {
		const day = date.getDate()
			.toLocaleString('en-US', { minimumIntegerDigits: 2, useGrouping: false });
		const month = (date.getMonth() + 1)
			.toLocaleString('en-US', { minimumIntegerDigits: 2, useGrouping: false });
		const year = date.getFullYear().toString().substr(-2);

		return `${day}/${month}/${year}`;
	}

  render() {
    return (
      <View style={{ flex: 1 }}>
        <RootNavigator />
        <GiftModal
          isVisible={this.state.modalVisible}
          hideModal={this.hideModal.bind(this)}
          giftImage={this.state.activeModalImage}
          giftEstablishmentName={this.state.activeModalEstablishmentName}
          giftTitle={this.state.activeModalTitle}
          giftDescription={this.state.activeModalDescription}
          date={this.formatDate(new Date())}
        />
      </View>
    );
  }
}

export default RootComponent;

@Nightsd01 Got to work! Seems like I had some trouble with cache. The steps I took to fix were:

npm cache clean --force
cd android && ./gradlew clean
cd .. && react-native run-android

@lucasharada I'm facing same issue. I'm looking a way to get notification when app is closed. I just did exactly as tutorial and it works just when app is open.did you succeed to get notification in android when app is closed?

I'm getting same issue in One Plus 5 which has Oreo 8.0.0. Other android version except 8, get notification even app is killed. I'm using react-native-one-signal 3.0.5 version.


US1114858 - Add all-courses test

More tests to come, but I messed up releasing on my last merge so going to use this test as a redo 🤦

Merging so I can redo the release, but feel free to still review and I will incorporate feedback into the next PR 😄


Spell for Spell Sniper not available

Spell Sniper Issue.zip

Since the update for Palace of Ice, the spell I selected for spell sniper feat is not working.

Already fixed in dev. Thanks.


Added 'Reverse Proxy' and 'Basic Usage' to GUIDE.md

Now included in the guide:

Reverse Proxy instructions (Cloudflare and Nginx)
(Incomplete) Basic Usage section

Thank you for putting all this together! I will go through and make some small expansions/changes later today, and then I'll merge it.
This is excellent, thank you!


Initialize ScrollBehavior's content size to infinite rather than 0.

This way, we don't clamp the scroll offset until after the first layout,
when we update the ScrollBehavior's contentSize to its actual value.
This only matters when restoring a Scrollable to a previous
scrollOffset. Since it was valid before the Scrollable was disposed, we
assume its still valid when restored.
BUG=https://github.com/flutter/flutter/issues/4883
BUG=https://github.com/flutter/flutter/issues/4797

Test?

This is a deft little fix. Definitely needs a regression test.
LGTM

OK, all ScrollBehaviors now initialize to INFINITE contentExtent. And found a good place to add the regression test.


Update

Does anyone tried to update all the packages that is compatible with the latest node lts 12+ ?

It looks like this repo is not managed anymore!

I bumped into this as well. Downgrading to 10.20.1 worked.


DOC: Want to change the logo

What's wrong with the existing documentation
The logo of agriLearnNetwork can be improved as it does not look that attractive , it should be simple but a statement
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

What kind of  logo you are planning to design?


Unexpected failure updating Kong configuration

Summary
Kong isn't working since a restart. I can see strange errors in the logs.
Kong Ingress controller version
0.7.1
Kong or Kong Enterprise version
1.5
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.11-eks-af3caf", GitCommit:"af3caf6136cd355f467083651cc1010a499f59b1", GitTreeState:"clean", BuildDate:"2020-03-27T21:51:36Z", GoVersion:"go1.12.17", Compiler:"gc", Platform:"linux/amd64"}

Environment

Cloud provider or hardware configuration: AWS EKS

What happened
Kong got Evicted for Memory Usage. Now, when starting, it doesn't pick its own configuration and I can see this error spamming the logs :
E0624 13:00:08.401512       1 controller.go:119] unexpected failure updating Kong configuration:
posting new config to /config: 500 Internal Server Error
<title>500 Internal Server Error</title>

500 Internal Server Error

W0624 13:00:08.401543       1 queue.go:112] requeuing assets-paris-dev/sh.helm.release.v1.api-certificate-generator.v3, err posting new config to /config: 500 Internal Server Error
<title>500 Internal Server Error</title>

500 Internal Server Error

Things to note  : I don't know why Kong is trying to requeue this secrets (the sh.helm one).
Expected behavior
Kong restarts and things go on normally.
Steps To Reproduce
No idea, sorry. It just happened and now Kong is unusable.

I can see another error from time to time :
│ proxy 2020/06/24 13:13:45 [error] 30#0: *15168 [kong] api_helpers.lua:260 Cannot serialise table: excessively sparse array, client: <IP_ADDRESS>, server: kong_admin, request: "POST /config?check_hash=1 HTTP/1.1", host: "localhost:8444"   │

You are running into https://github.com/Kong/kong/issues/5768, the fix is merged in but not yet released.
Can you use kong 2.1.0-beta1 image for this?

I think I can, yes. I'll try to find a moment to test it out and will keep you posted here.

I'm seeing something similar (well in a way) with 2.1.0-beta1 and KIC 0.9.1. Running in AKS 1.15.11, 3 pods, db-less. No error from Kong/kong#5768 in Kong logs.
E0710 05:46:01.012093       1 controller.go:128] unexpected failure updating Kong configuration:
posting new config to /config: 500 Internal Server Error {"message":"An unexpected error occurred"}
W0710 05:46:01.012139       1 queue.go:112] requeuing default/increased-timeout, err posting new config to /config: 500 Internal Server Error {"message":"An unexpected error occurred"}

The error is rare, occurring randomly in time and not simultaneous in all kong pods. If I restart pod, it syncs configuration without errors. Our monitoring system reported invalid SSL certificate issue once, around the time this happened:
W0710 05:46:30.963562       1 queue.go:112] requeuing default/increased-timeout, err posting new config to /config: 500 Internal Server Error {"message":"An unexpected error occurred"}
I0710 05:46:34.030230       1 kong.go:68] no configuration change, skipping sync to Kong
I0710 05:55:54.498295       1 kong.go:81] successfully synced configuration to Kong

(We upgraded to 2.1.0-beta1 to resolve the TLS breakage actually, because 2.0.5 was not released at the time we hit the bug heavily)
Also in ingress controller logs I see this sometimes (looks unrelated but who knows):
E0709 23:35:51.764732       1 reflector.go:307] pkg/mod/k8s.io/client-go@v0.17.4/tools/cache/reflector.go:105: Failed to watch *v1.Service: Get "https://<IP_ADDRESS>:443/api/v1/services?allowWatchBookmarks=true&resourceVersion=69347513&timeout=8m58s&timeoutSeconds=538&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
...
W0709 23:35:52.869074       1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.4/tools/cache/reflector.go:105: watch of *v1.Service ended with: too old resource version: 69347513 (69369016)

I'm seeing something similar (well in a way) with 2.1.0-beta1 and KIC 0.9.1. Running in AKS 1.15.11, 3 pods, db-less. No error from Kong/kong#5768 in Kong logs.

Can you share the logs of the kong container from around the same time when the controller container logs the unexpected failure updating Kong configuration error? That would help us figure out the root cause of why this is happening.
cc @Kong/team-core

Closing this due to lack of activity. Please re-open if needed.


Improve HTML Semantics of Rendered Diff

This is definitely a useful library, but I would hope for improved HTML semantics.

Table caption
When rendering the table to display the diff, it would be beneficial to support or auto-generate a caption value. In practice this would probably be something like "Changes for [filename]". This way, those navigating with assistive technologies, accessibility trees or landmarks navigation can have greater context as to what the information is.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/caption

Deletions use <del> tag
When showing document changes like this diff viewer, and showing deletions, it's more appropriate to use the <del> element. This creates a more accurate semantic experience and doesn't rely entirely on the visual UI to understand what content is being deleted.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/del

Insertions use <ins> tag
Much like the previous <del> tag, when displaying insertions, the <ins> tag should be used. Again, this provides greater context to those who may browse with assistive technologies and /or accessibility trees. Using these semantic tags will ensure that the markup communicates as clearly as the UI design.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ins

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: restrict node version to >= 14

Description
Because we at the moment don't restrict which node version, it is up to interpretation and can be wrongfully used. We use version 14 for all our GitHub actions, so let's cap it to that.
Related issue(s)
fixes https://github.com/asyncapi/modelina/issues/160

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.419%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1842

Relevant Lines:
1880

💛  - Coveralls


feature request: toPixels

Right now deeplearn.js has a method fromPixels which takes an ImageData and converts it into a Tensor3D.
It would be nice to have something that does the inverse, like toPixels - which would take a 2d or 3d tensor and convert it to an ImageData

This issue was moved to tensorflow/tfjs#103


CNI: add host-side interface info to cni.Result

Fixes: https://github.com/cilium/cilium/issues/24899

Add host-side interface info to cni.Result, which allows bandwidth CNI to work with Cilium

Add host-side interface info to cni.Result, which allows bandwidth CNI to work with Cilium

Off topic and unrelated to the fix, have you considered using Cilium's bandwidth manager? https://docs.cilium.io/en/stable/network/kubernetes/bandwidth-manager/

mirroring +1 from last pr which was closed: https://github.com/cilium/cilium/pull/24901

/test

/test

Marking for backport since this is a bug fix.


all_robots.xml file is not updated

Please remember to add every new robot to the list included in the all_robots.xml file

I added CER04, iCubGenova08 and iCubWaterloo01 to this list on my branch CER04 (for now)


Support for the title element with phantomjs driver

Here is a test I am running with phpunit-spiderling, nice and simple:
/**
 * Check page title
 *
 * @todo Works with simple driver but not phantomjs, report bug
 *
 * @driver simple
 */
public function testTitle()
{
	$page = $this->visit(self::DOMAIN . '/browse');
	$this->assertEquals('Browse reports — Awooga', $page->find('title')->text());
}

It works fine, but if I switch the driver to phantomjs it cannot find the element. I wonder, does the PhantomJS driver only look in the body of the HTML document?
This isn't urgent, as the simple driver is fine, and arguably is better where JavaScript does not need to be run. However, it would be good to know it works as it should in all drivers.
Happy to supply an example script, if you have trouble re-creating this.

You seem to be able to do
$page->find("title", ["visible" => false])->text();

and it works.

Thanks @wakeless. It's good to hear it can be made to work with the Phantom driver, but shouldn't the call be the same across all drivers?

I actually don't think this does work unfortunately. I'll probably hack something together for it later today.

@wakeless Thank you! :clap:

Great stuff :smile_cat:

@wakeless: did you have any luck with this? I'd like to see the two Spiderling libraries get more attention generally, so little fixes are nice if they can be done. I have some coming too!


Segmentation Fault on changing function params

Running on Ubuntu 20.04
When testing out the bevy example, if I add commands to the parameters for player_movement_system then the application seg faults.  This happens for any change to the system params I have tested.  This may be a fundamental limitation with these techniques though.

Yeah exactly, with the current implementation this is unavoidable. The executable expects the library function signatures to be fixed, if they change you'll hit undefined behavior.
The most practical workaround for now is to either pass a larger state parameter that likely includes what you'll want to work with on the library side.
I'll be looking into ideas of making this more flexible and do welcome suggestions to solve this problem. I'll leave this issue open for a discussion around that.

I'll be reading through your write-up and the code tonight.  I love this idea and I think it can grow into a very powerful dev tool for bevy


Optimize put result phase in the vm.

Many opcodes has no results, or their results are always pushed onto the stack,
and checking their result type is wasting CPU cycles. Furthermore the
last_completion_value is removed which simplify this third phase.

Separated into multiple patches.


Path trailing parameter not validated as required

First of all thank you for this very useful middleware.
In the OAS I have the following path with int parameter required, but if I make a request without it (/health/validator/) I get 200 instead of the expected validation error.
Is there a way to get it validated as required?
OAS:
  '/health/validator/{int}':
    parameters:
      - schema:
          type: integer
        name: int
        in: path
        required: true
    get:
      summary: Validator test
      tags:
        - System
      responses:
        '200':
          description: OK
      operationId: getHealthValidatorInt
      description: For openapi validator test

I am using fastify with fastify-multer and your openapi-validator-middleware.
This is a package.json extract:
  "dependencies": {
    "@fastify/autoload": "^4.0.1",
    "@fastify/cors": "^7.0.0",
    "@fastify/helmet": "^8.0.0",
    "@fastify/sensible": "^4.1.0",
    "cross-env": "^7.0.3",
    "dotenv": "^16.0.1",
    "fastify": "^3.29.0",
    "fastify-cli": "^3.0.0",
    "fastify-multer": "^2.0.2",
    "fastify-plugin": "^3.0.1",
    "openapi-validator-middleware": "^3.2.6",
    "uri-js": "^4.4.1"
  },
  "devDependencies": {
    "@types/jest": "^27.5.1",
    "@types/node": "^17.0.32",
    "@typescript-eslint/eslint-plugin": "^5.22.0",
    "@typescript-eslint/parser": "^5.22.0",
    "eslint": "^8.15.0",
    "eslint-config-prettier": "^8.5.0",
    "jest": "^28.1.0",
    "nodemon": "^2.0.16",
    "pino-pretty": "^7.6.1",
    "prettier": "^2.6.2",
    "rimraf": "^3.0.2",
    "ts-jest": "^28.0.2",
    "ts-node": "^10.7.0",
    "typescript": "^4.6.4"
  }

And this is the related app code:
  openapiValidator.init('src/openapi/my_service.oas.yml', {
    framework: 'fastify',
  });
  fastify.register(
    openapiValidator.validate({
      skiplist: [],
    })
  );
  fastify.setErrorHandler(async (err, req, reply) => {
    if (err instanceof openapiValidator.InputValidationError) {
      return reply.status(400).send({ more_info: JSON.stringify(err.errors) });
    }
    fastify.log.error(err);

    reply.status(500);
    reply.send();
  });

  // API routes
  fastify.register(apiRootRoutes);

Hi @itacode , glad to see this package helps you.
The reason that you't not getting any validation error for requests coming to /health/validator is that it's actually not the same path as /health/validator/{int}, so it's not being validated.
But still fastify should return 404. Isn't that the case for you?


Fixed steamcmd call for beta

this quote marks around $STEAMAPPID$STEAMBETAFLAG were causing it to not download the experimental branch correctly; this rectifies that

created test image and works now. Thanks.

No problem!


Update communicate-with-users-from-other-organizations.md

Updating to clarify that external access is available in all clouds, however it is not available across any clouds. Also added clarity on federation/interop support by area. Would appreciate review by team to ensure proper terminology.

Docs Build status updates of commit 6bb57d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/communicate-with-users-from-other-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 99435d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/communicate-with-users-from-other-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@MikePlumleyMSFT PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Docs Build status updates of commit e5dddd9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/communicate-with-users-from-other-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


gantt is not deleting row after removing data array

Hi,
I am trying to remove row from gantt. even after updating data. its not refreshing gantt immediately.
if user clicks then row is removed from ui.
data.splice(i,1);

Have you tried api.columns.refresh() ?

after scope.$apply it started working


Security Benchmarks commands

Summary of new feature
We were able to get the CIS benchmarks results mostly through individual dbatools commands. Please check if it would be worth adding a separate section for Security benchmarks. Few auditors have tools to generate report(eg. CIS CAT Pro) though they dont have the flexibility like PowerShell.
Proposed technical details (if applicable)
https://www.cisecurity.org/benchmark/microsoft_sql_server/
http://www.itsecure.hu/library/image/CIS_Microsoft_SQL_Server_2016_Benchmark_v1.0.0.pdf
Attached our script prepared using few other modules for taking these benchmarks.
CIS_SQLServer.txt
Latest version of dbatools as of writing
1.0.21

@g-kannan you can check sqlcollaborative/dbachecks as CIS is being implemented in that module for building reports and performing the scans.
This project is being used to directly track that progress. https://github.com/sqlcollaborative/dbachecks/projects/1


Bug - "No chapter" error on certian series.

I experienced this error from time to time, but usually once I've restarted the process it all goes well (maybe something related to connection timeout?). Yet for certian series  the error is persistent and forced me to obscure their links so that the process could continue smoothly. Now that we have the --keep-alive option I tried a separate process with only the problematic links in the list and I noticed that some chapters, but never all of them (looks quite random) are actually downloaded each time I start the .bat, yet in 4-5 runs the process still gives mixed results, like errors or isolate chapters correctly downloaded.
The links appear to be correct and the chapters not downloaded by mangarack looks fine on batoto (I tried some at random).
Right now the problematic series I encountered should be the following:
B
http://bato.to/comic/_/comics/btooom-r899
G
http://bato.to/comic/_/comics/gokukoku-no-brynhildr-r3594
http://bato.to/comic/_/comics/gurenki-creo-the-crimson-crises-r6840
M
http://bato.to/comic/_/comics/mahouka-koukou-no-rettousei-r3290
N
http://bato.to/comic/_/comics/nyan-koi-r509
and a screenshot of the error:

Right now:
Btooom: only v3 c17 downloaded
Gokukoku no brynhildr: each run it downloads from 3 to 5 chapters (in order), then "No Chapter".
Gurenki: in more tries it was downloaded all, except omake and ch10, no luck with them.
Mahouka: only a single chapter downloaded (ch3)
Nyan Koi: no chapter ever downloaded.
Sorry if I missed something.

Great find! I didn't encounter it yet. I'm confident I fixed it. Please check and comment :+1:

It went well with the "bugged.bat" that I prepared for testing purposes with all problematic mangas, so I stopped the downloads and started the proper library global update. Now is going fine past ch15 of Gokukoku, so I think we can consider this solved :)

Maybe this deserve a different issue, but since it happened now for the first time after the update and only affects (it seems) one of the manga that presented the bug of #14 I reopen this.
For Nyan Koi chapters up to 11 were downloaded and now a different error appears, the following:

This happens when the .mrpersistent has become corrupted, for some reason. An error happens when the file is written and goes wrong. I thought I fixed this from ever happening again in 3.0.13. Could it be possible you still have old persistent files around from the 3.0.13 time? If so, simply delete the persistent file with a problem and a new one should be made that cannot go wrong anymore.

Yes, you are right! no problem now :) Thanks


Linkedin Connection scraper

Script Title - script should able to scrap all connections of one who is running that script
(can be done by requests/selenium/bs4 )
what will change - Adding script for that
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Code
[x] Improving Documentation
[x] Bug Fix

Programming Language

[x] Python

Happy Coding,

Hey, Id like to take this issue.

Okay, sure :)

Hey! Turns out Scraping on LinkedIn isn't permitted according to the Terms and Conditions!
I'm afraid Ill have to discontinue! Sorry about that

Yeah, I recently got to know that. Thanks for your step and aware all of us about the same :). Looking forward to you for coming up a different scraper maybe like getting facebook data using APIs


Limit the Number of Users a Gitea Deployment Can Have

Feature Description
I propose adding a new configuration variable to the app.ini file in Gitea, allowing administrators to define a maximum limit on the number of users within a deployment. Similar to the MAX_CREATION_LIMIT feature for repository creation, this enhancement would provide greater control over the scalability and management of Gitea instances.
Additionally an option for Admins to update and change this configuration from the Admin UI could be a good idea. But this option should be enabled in api.ini file to do so.
Screenshots
No response

no can we do a privet message on discord

Isn't DISABLE_REGISTRATION enough? This sounds like a controlled environment, so disabling the registration should be doable.


Unable to delete target

Summary
404 Not Found message comes when i try to delete target from upstream
request
GET http://<IP_ADDRESS>:8001/upstreams/MailerService/targets
response
{
"data": [
{
"target": "<IP_ADDRESS>:9898",
"id": "21444ca0-5964-4dd5-b51c-d0919e314649",
"weight": 100,
"created_at":<PHONE_NUMBER>691,
"upstream_id": "0afe1b67-9079-4959-9d2a-92992679993b"
},
{
"target": "<IP_ADDRESS>:9898",
"id": "fcae9ff9-146b-435e-bdbb-42cb12f335f4",
"weight": 100,
"created_at":<PHONE_NUMBER>685,
"upstream_id": "0afe1b67-9079-4959-9d2a-92992679993b"
}
],
"total": 2
}
request
DELETE http://<IP_ADDRESS>:8001/upstreams/MailerService/targets/fcae9ff9-146b-435e-bdbb-42cb12f335f4
response
{
"message": "Not found"
}
Additional Details & Logs

Kong version 0.10.0
Operating System ubuntu 14

You cannot delete it, just set the weight to 0. See https://getkong.org/docs/0.10.x/admin-api/#target-object

I can't able to update the existing target weight.
Request
PATCH http://<IP_ADDRESS>:8001/upstreams/MailerService/targets/fcae9ff9-146b-435e-bdbb-42cb12f335f4
weight=50
Response
{
"message": "Not found"
}

This seems a clear case of rtfm to me. It keeps a history of changes, so you're adding an entry to the history, hence you should make a POST request.

@Tieske   When i delete one target , it  will add new record with weight=0..Can you help me?


Remove missleading javadoc

Motivation:
Its completely fine to start writing before the handshake completes when using SslHandler. The writes will be just queued.
Modifications:
Remove the missleading and incorrect javadoc.
Result:
Correct javadoc.

@Scottmitch @nmittler PTAL

Cherry-picked into 4.1 (00deb2e) and 4.0 (b618848a729de01258d7c533ccbe83fd92c3f3be)

lgtm


Are we ready to update?

I think we are, @WorldLanguages thoughts?

Nevermind, we have some issues.

I'll localize the remaining spanish localization today

Closing this issue; we know we're ready when all issues with v1.5 milestone are closed


Drawing view fixes

Description of Change

Bugs Fixed

Fixes

#1452,
#1453
#1451

Behavioral Changes
LineColor is set to Black, Enable SmoothLine by default
PR Checklist

[x] Has a linked Issue, and the Issue has been approved
[ ] Has tests (if omitted, state reason in description)
[x] Has samples (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Changes adhere to coding standard

[ ] Updated documentation

Awesome @VladislavAntonyuk! Thanks for the quick action!


Cannot use personal account

Hi!
i get the following when trying to link:
"You can't sign in here with a personal account. Use your work or school account instead."

Sorry, you need to provide more detail than that. Have you configured your azure application as specified - please double check? Are you using the same email address you set up the azure application? I'd anticipate that the error is correct, in that you are logged in with a personal account and not the azure hosted account, it is possible (I have both a personal and an O365 account both with the same email address - it can be confusing).

ive tested in my directory called "default directory" and one in called "Default directory" no luck
" in that you are logged in with a personal account and not the azure hosted account,"
how can i check this, its realy confusing  im logging in with my outlook.com account and the domain turns to outlook.onmicrosoft.com

i found this statement now....
Due to temporary differences in supported functionality, we don't recommend enabling personal Microsoft accounts for an existing registration. If you need to enable personal accounts, you can do so using the manifest editor.  Learn more about these restrictions.

Not sure what you mean about directories. With regards the account, log out on your browser, make sure you are logged out, then log in again. If you have two accounts with the same email address it will prompt you to login with the right account.
When you created the app, did you make sure to use this permission - Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)?

I've manged it to work!
but i still got an error where i cant remove my notifications from previous attempts
"failed to call service persistent_notification/dismiss. required key not provided @ data['notification_id']
any tips here?

gone!
no issues

That's a new one on me, I'll take a look because I've noticed the window has stopped closing. After a reboot I'd just refresh my browser, since HA doesn't retain notifications between reboots.


parallel should support limit = Infinity

parallel should an arbitrary number of parallel executions. Semantically this could be expressed with limit equal either to undefined or Infinity.
In the current implementation, limit: undefined is precluded by type requirements, and limit: Infinity blows up at this line.

Hey @karmaniverous! This is fixed in the Radashi fork in v12.3.0.


Flatpickr Changes

This PR fixes some of our really jarring issues with Flatpickr styling.
In order to not maintain flatpickr styles ourselves, we fork upstream to add a theme with our nightmode colors in it: https://github.com/aero31aero/flatpickr .
Also, we add sass-loader to our webpack pipeline, which should enable us to use a lot of sass features we currently do not use.
Testing Plan:
Manual testing
GIFs or Screenshots:
We go from:

to:

Visuall, this is definitely better.  But the flatpickr base picked is kinda ugly (e.g. the year dropdown); I wonder if there's a better project we could use instead?

Flatpickr upstream already has a dark theme that looks essentially equivalent. Why do we need to roll our own?

I see you filed flatpickr/flatpickr#2168 for namespacing the CSS themes to a class. Here’s a way we could use PostCSS plugins to introduce such a class without forking:
--- a/postcss.config.js
+++ b/postcss.config.js
@@ -2,6 +2,9 @@ module.exports = ({ file }) => ({
     parser: file.extname === ".scss" ? "postcss-scss" : false,
     plugins: {
         // Warning: despite appearances, order is significant
+        "postcss-use": {
+            modules: "*",
+        },
         "postcss-nested": {},
         "postcss-extend-rule": {},
         "postcss-simple-vars": {},
--- /dev/null
+++ b/static/styles/flatpickr-dark.scss
@@ -0,0 +1,3 @@
+@use postcss-import;
+@use postcss-wrap(selector: "body.night-mode");
+@import "flatpickr/dist/themes/dark.css";

Or we could dynamically add and remove the stylesheet as in emojisets.js (#13981).

Oh, I was thinking we were mimicking sass syntax with postcss so I added sass. After your comment I did some more reading on it, and it looks like if we want some feature for css we just have to add postcss plugin for it, right? Neat!

Also, even if they scope the themes or we scope it ourselves, their dark theme is subtly different and stands out like a sore thumb.
I think we actually either want to get a theme like "zulip-dark" merged upstream or roll our own.
My option currently is a middle ground: we create a new theme file in flatpickr and their theme building pipeline gives us a theme built with the colors we specified. Then we just update that theme whenever we update flatpickr and we stay current with the upstream changes to their html selectors.

Also, even if they scope the themes or we scope it ourselves, their dark theme is subtly different and stands out like a sore thumb.

Can you post a screenshot of what it looks like?

This is the default theme. If we're fine with this, we can load this theme easily, I think.

Hey guys, flatpickr author here.
I'm delighted to know it's being used at Zulip.
Please feel free to open up issues over at the flatpickr repo with any other problems or suggestions you may have.

Honestly I’d say the upstream dark theme looks totally fine if not better. We don’t need edit the theme to match our exact page background color; that makes the popup look less like a popup and start disappearing into the background.

Great, given that opinion let's proceed with just doing the default dark theme flatpickr; that seems much more maintainable and less complex to manage.
@aero31aero can you update this PR to do that?

@timabbott I just opened #15476 for this. I still stand behind this PR, however, or at least its parts about SCSS changes.
@andersk in particular, I couldn't replicate SCSS's nested imports in PostCSS. The current @import implementation we use, postcss-import, intends to be compatible with CSS spec so it enforces that imports are at the top of the file.
I'd prefer to keep this PR open for the time being. Once we have scoped themes from upstream, this issue would be moot anyway, and we'd have to use night_mode.js to add the necessary theme class to body.

Replaced by #19550.


src: Fix genl command payload size calculations.

Correct generic netlink command payload buffer size calculations by aligning against the size of the attribute (e.g. sizeof(uint16_t)) as  expected instead of size of the attribute size (e.g. sizeof(sizeof(uint16_t))).
Payload buffer sizes should now be smaller in some cases since netlink attributes are aligned on a 4 byte boundary.  For example, the underlying NLA_ALIGN() macro returns 4 when the type is uint16_t, i.e. NLA_ALIGN(sizeof(uint16_t)).  Previously, 8 was returned on 64 bit platforms since the NLA_ALIGN() call was incorrectly called as NLA_ALIGN(sizeof(sizeof(uint16_t))), which boils downs to NLA_ALIGN(size_t).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 65.005%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
1395

Relevant Lines:
2146

💛  - Coveralls


feat(Azure OpenAI) log content filter results in proper attributes #855

[ ] I have added tests that cover my changes.
[ ] If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.
[x] PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....
[ ] (If applicable) I have updated the documentation accordingly.

 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.

The lint failure was reproduced locally. I fixed it and was able to run lint locally with no issue with the latest commit

Thanks @jinsongo! can you add a test for that?

Thanks @jonhsma! can you add a test for that?  ^_^

🙈😅

Thanks @jinsongo! can you add a test for that?

Thanks @jonhsma! can you add a test for that? ^_^

Sure. Is there any guide on writing test? If not I will try to figure it out..

I tried to test it locally. It seems that this type of response could only come from Azure OpenAI and it's impossible for me to get an API key for that. I think I saw in the docs that simulated responses are used for these tests but I can't find that page anymore. Is there any suggestions? Thanks!

This is still a work in progress. It passed the tests locally.
The latest commit should be able to (🤞) handle both streaming and non-streaming filtered results like these

https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/content-filter?tabs=warning%2Cuser-prompt%2Cpython-new#sample-response-stream-blocked-by-filters
https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/content-filter?tabs=warning%2Cuser-prompt%2Cpython-new#scenario-your-api-call-asks-for-multiple-responses-n1-and-at-least-one-of-the-responses-is-filtered

but it won't handle situations like this where the input is filtered

https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/content-filter?tabs=warning%2Cuser-prompt%2Cpython-new#example-scenario-an-input-prompt-containing-content-that-is-classified-at-a-filtered-category-and-severity-level-is-sent-to-the-completions-api

It seems that both streaming and non-streaming calls would eventually run _set_completions()? So in that case as long as I collect content_filter_results in _accumulate_stream_items(), it will be passed in to _set_completions() in _build_from_streaming_response()?
Here is what I have in _accumulate_stream_items()
https://github.com/traceloop/openllmetry/blob/de2c882e5111dc5bb64326345775c0ef3db89800/packages/opentelemetry-instrumentation-openai/opentelemetry/instrumentation/openai/shared/chat_wrappers.py#L797-L798


TODO list

Description
TODO list
It would be nice that Brackets has a "to do" list.  As a developer would be helpful since when I'm tired in the middle of the night, I would like to make some notes where I'm leaving the code... to continue later or so...  to keep track of the things one it's doing...  this is a good implementation of a TODO list, please take a look: http://docwiki.embarcadero.com/RADStudio/Seattle/en/To-Do_List
Thanks.

@arevalosoft 'task-list' brackets extension does similar thing and can be used to keep track of tasks project wise. Please have a look at this git repo https://github.com/ckip/brackets-task-list

There's also https://github.com/mikaeljorhult/brackets-todo, which works great but could use some contributions on fixing deprecation warnings.

Thanks!
On Wed, Oct 19, 2016 at 1:31 AM, Swagatam Mitra<EMAIL_ADDRESS>wrote:

@arevalosoft https://github.com/arevalosoft 'task-list' brackets
extension does similar thing and can be used to keep track of tasks project
wise. Please have a look at this git repo https://github.com/ckip/
brackets-task-list
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adobe/brackets/issues/12841#issuecomment-254734674,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKhZEg-50qwdt6_F_thlpxgl4FOHNe0mks5q1cdigaJpZM4Kakvv
.

--
César Arévalo
+(506) 8704-6390

Thanks!
On Wed, Oct 19, 2016 at 1:38 AM, Pete Nykänen<EMAIL_ADDRESS>wrote:

There's also https://github.com/mikaeljorhult/brackets-todo, which works
great but could use some contributions on fixing deprecation warnings.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adobe/brackets/issues/12841#issuecomment-254735922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKhZEhfh6Qx6r9UuK9ztJF_A_xb2rk6Yks5q1cj_gaJpZM4Kakvv
.

--
César Arévalo
+(506) 8704-6390

@arevalosoft Closing this issue as the requested feature is available in multiple extensions.


Configurable weights

It would be useful to be able to tweak the likelyhood of options being selected.
For example, I might be willing to play with a scenario or the thematic map, but I don't want to be getting a these options very often.

I've now modified the additional board and secondary adversary settings to use percentages rather than being based on the number of different options that match the difficulty settings. (e.g. there are almost always way more combinations of multiple adversary levels that match a given difficulty level than single adversary levels. This had caused a secondary adversary to be far more likely if that option was enabled.)

#13 Provides this functionality


hub sync crashes if branch disappears during iteration

Running hub sync, I see
warning: `gssdp-0.14.15' seems to contain unpushed commits

Once hub sync completes, I kick it off again. Before it gets to gssdp-0.14.15, while it's listing other branches with unpushed commits, in another shell I delete gssdp-0.14.15:
$ git branch -D gssdp-0.14.15
Deleted branch gssdp-0.14.15 (was 265d3fc8da).

At that point, when hub sync reaches gssdp-0.14.5 in its iteration, it crashes:
...
warning: `googler-2.5.1' seems to contain unpushed commits
warning: `gosu-1.13.5' seems to contain unpushed commits
warning: `gpac-0.6.1' seems to contain unpushed commits
warning: `gputils-1.4.2-1' seems to contain unpushed commits
exit status 128

So it may benefit from sort of locking or at least shouldn't assume the branch will still exist when it gets to it.

+1 on this