text:
warn if [miniflare] is used in wrangler.toml

We currently ignore the [miniflare] key in wrangler.toml, but that's actually confusing because folks think we support its configuration values. We should probably throw a warning here. Separately we should implement features similar to the ones minifalre provides (with additional edge equivalents) incl. mounts and testing environment, but that's for 2.1

LOL - I specifically removed the warning here - https://github.com/cloudflare/wrangler2/pull/627

lmao oh right

LOL - I specifically removed the warning here - #627 - and you approved it @threepointone 😆

I can put this back (maybe try to improve the format and UI), or are we leaving it as is?

We need a custom message explaining why exactly we don't support miniflare configuration


text:
feat: Add commands for holding and unholding pull requests

This commit adds two new commands, '/hold' and '/unhold', to handle the holding and unholding of pull requests. The '/hold' command adds the 'do-not-merge' label to the pull request, preventing it from being merged. The '/unhold' command removes the 'do-not-merge' label, allowing the pull request to be merged.
Signed-off-by: Victor Palade victor@cloudflavor.io

/triage
/merge
fixes: https://github.com/cloudflavor/oscar/issues/24

source: gharchive/pull-request

repo: cloudflavor/oscar

license_type: permissive

license_source: github-api


text:
Update Swift snapshot to 2015-12-31

Newer tools again!

I've successfully pushed with this, I'm sure it's good to go. I don't have write access to this repo though so it'll have to wait I guess!

Invite sent for @cloudfoundry-community.

Thanks, @drnic!

authors: briancroom drnic

repo: cloudfoundry-community/swift-buildpack

license_source: bigquery


text:
Link to download Concourse Worker produces a 404 error

in /bosh-windows-stemcell-builder/wiki/Windows-Worker-and-Concourse-Setup
the link for concourse_windows_amd64.exe should be:
https://concourse-ci.org/download.html
Thanks,
--
Tony Markel

Thanks @tonymarkel. This is updated.

source: gharchive/issue

authors: aminjam tonymarkel


text:
Add syslog auto update + Add syslog no internet ops

Hi there,
just saw that the used syslog-release version in the syslog ops file is pretty outdated and that there is no 'no-internet-access' ops file for it so I added both with this PR.

Hi @benjaminguttmann-avtq , thanks for this PR!
Can you change the base branch to develop?

Hi @ssapra , thx for mentioning that.
Done

authors: benjaminguttmann-avtq ssapra

repo: cloudfoundry/bosh-deployment


text:
Incompatible change in v1.x (Ruby and Python removed)

Hi everyone,
the cflinuxfs4 releases v1.x have Ruby and Python removed. The release has been automatically pushed to the cf-deployment "develop" branch and now we see a number of buildpack detection tests failing:
https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/cf-deployment/jobs/experimental-cats-cflinuxfs4/builds/136
Summarizing 5 Failures:
  [FAIL] [detect] Buildpacks php when using cflinuxfs4 stack [It] makes the app reachable via its bound route
  /go/src/github.com/cloudfoundry/cf-acceptance-tests/detect/buildpacks.go:149
  [FAIL] [detect] Buildpacks ruby when using cflinuxfs4 stack [It] makes the app reachable via its bound route
  /go/src/github.com/cloudfoundry/cf-acceptance-tests/detect/buildpacks.go:44
  [FAIL] [detect] Buildpacks java when using cflinuxfs4 stack [It] makes the app reachable via its bound route
  /go/src/github.com/cloudfoundry/cf-acceptance-tests/detect/buildpacks.go:84
  [FAIL] [detect] Buildpacks staticfile when using cflinuxfs4 stack [It] makes the app reachable via its bound route
  /go/src/github.com/cloudfoundry/cf-acceptance-tests/detect/buildpacks.go:186
  [FAIL] [detect] Buildpacks binary when using cflinuxfs4 stack [It] makes the app reachable via its bound route
  /go/src/github.com/cloudfoundry/cf-acceptance-tests/detect/buildpacks.go:206

This is the failing CATs suite: https://github.com/cloudfoundry/cf-acceptance-tests/blob/main/detect/buildpacks.go
Tests fail because some buildpacks (and also some test apps) assume that a "ruby" or "erb" executable is available. This could also affect running CF apps.
Why exactly did you decide to remove Ruby and Python? Is there a chance to revert this change to enable a smooth transition from cflinuxfs3 to cflinuxfs4?
Thanks and Best Regards,
Jochen.

We will be fixing these issues in the buildpacks and advise not to upgrade to the v1 line of cflinuxfs4 until all buildpacks are patched. The following issues can be tracked for progress:

[ ] https://github.com/cloudfoundry/ruby-buildpack/issues/764
[ ] https://github.com/cloudfoundry/cf-acceptance-tests/issues/809
[ ] https://github.com/cloudfoundry/staticfile-buildpack/issues/359
[ ] https://github.com/cloudfoundry/php-buildpack/issues/849

not just very late, you combine a security deadline (fs4) with a buildpack upgrade. Most of our users pin the buildpack version via #hashtag instead of relying on the latest buildpack provided with CF-deployment. This is required due to stable delivery of the same artefact with the ability to easily downgrade in case of issues.
This is without grace period and pre-notification and will break many applications due to short time frames!
Just as an example, the most critical aspect is not the mentioned runtime dependency but the build time dependency: https://github.com/cloudfoundry/staticfile-buildpack/blob/master/CHANGELOG#L4
IMHO breaking changes only done via major version change, but this was ignored as well...
With this in place, you force applications with ruby templating to have major actions on short notice and there is even no way to downgrade or roll back their buildpack, once fs3 is gone due to a CVE! Despite that they are busy with cflinuxfs4 checks, this should not happen and would be a disaster, caused by "theoretical future reductions of CVE" and non-available bundles of ruby inside the individual buildpacks.
https://github.com/cloudfoundry/cflinuxfs4/pull/3
Remove Ruby from the stack to reduce the CVE surface area of the image.

Overall i would like to request you to think about theoretical CVE's in future vs. breaking changes. I accept the reason, because reduction of CVE is a good approach! But please with a reasonable timeframe of 3-6 months ETA to production (meaning 2-4 months as of today) or at least without bundle of fs3 deadline. Thank you!
@ryanmoran @TisVictress @sophiewigmore @robdimsdale @krismarc

This is serious. The product is 'sold' as best developer experience. So they don't have to care about things like this except the code. What should I tell to my users now? Please start shipping your own runtime/interpreter? Please also start to maintain it. We are not going to do that anymore after so many years of doing so.
We just talk about buildpacks so far and possibility to continue using them. What about all other reasons of using removed software? Eg. Liberty buildpacks requires only Ruby to be executed. However, we added a custom script which traps java exceptions and if it's a case then using python we generate a dump and send it to S3. This will become broken until we ship python ourselves. Buildpack maintainer would not add python as he do not really need it fo the buildpack itself.
There might be many usecases where people use python in addition to their main purpose of the buildpack.
That's quite a breaking change. As mentioned above. People will start seeing crashed apps and there might be no quick fix for potential developer.

Hello folks,
We apologize for the late-breaking change. The blast-radius of this specific change ended up being much bigger than we anticipated. For our failure to communicate this effectively at an earlier point in time, we are sorry.
On the topic of the change and its need to address our CVE posture, let me first talk about the current state of the world. Today, the cflinuxfs3 stack contains a version of Ruby (v2.5) that has been unmaintained upstream for nearly 2 years. The stack also contains a version of Python (v2.7) that has been unmaintained upstream over 3 years. Both runtimes likely contain any number of critical-level security vulnerabilities for which there is no patch or mitigation. Anybody running these stacks in their production cluster should be extremely wary of the possibility of their exploitation.
For cflinuxfs4, based on Ubuntu Jammy, the Ruby version, 3.0, is expected to go out of support approximately 1 year from now (3/31/2024). Python version 3.10, which is the version shipped in the python3 package as part of Jammy, has a slightly better timeline as it remains in support for the next 3.5 years (Oct. 2026), but still falls out of support before Jammy and hence cflinuxfs4 would in April 2027.
With that security posture playing out right now in cflinuxfs3 and there being no good time to ever introduce a breaking change in the stack (especially, when it is exceedingly easy to unknowingly couple to it through your own application code), we felt an urgent need to make the breaking change with as much lead time as we could before cflinuxfs4 became the only supported stack and a change of this magnitude would become all the more painful. Timelines and workloads being what they are, this change happened very late in our process to move everything we could onto cflinuxfs4.

At this point, we cannot roll back the clock and provide early communication that might ease the transition. We can only provide guidance and support to move forward. For the specific issues outlined, we believe there are reasonable workarounds that should not require immediate re-writes of any application.
Specifically, if you are still in need of Ruby or Python in your application and were relying upon the presence of those provided in the stack, you can trigger either the Ruby or Python buildpacks to install a Ruby or Python for you by just including it ahead of your usual buildpack in a multi-buildpack chain. For example, if I use the Staticfile buildpack, and still want Ruby for some reason, I can ask CF to build my app with both Ruby and the Staticfile buildpack with the following command:
cf push <app> --buildpack ruby_buildpack --buildpack staticfile_buildpack

For the breaking change in the Staticfile buildpack, we apologize for our failure to bump the major version. FWIW, the feature of using ERB templating was never expected to be an external-facing feature and has been marked and logged as deprecated for more than 5 years. Separate from incorrect versioning of this feature removal, we feel that the removal of the feature came with exceedingly early feedback of its pending removal. If you still want to enable this workflow, you can follow the steps provided above to get a Ruby installed at runtime. You can then also include a .profile script with contents similar to the following:
erb $HOME/nginx/conf/nginx.conf.erb $HOME/nginx/conf/nginx.conf

This should enable the same outcome without relying upon the internal implementation details of a buildpack for its side effect. You should also consider migrating to the NGINX buildpack as has been stated in the deprecation notice.

Again, apologies for the communication issues and our failure to provide better guidance before now. We believe everyone should have at least some path forward at this point and we are happy to hear any other issues folks encounter with this change or in the migration to cflinuxfs4 more broadly.
Sincerely,
The CF Buildpacks Team

Can anyone point me to the information about which cf-deployment release will include this stack as a default? I'd probably be able to find it in the PRs and the source code. However, it would be nice to have a statement here as well.

Can anyone point me to the information about which cf-deployment release will include this stack as a default? I'd probably be able to find it in the PRs and the source code. However, it would be nice to have a statement here as well.

https://github.com/cloudfoundry/cf-deployment/issues/989

Hi folks,
@ryanmoran thank you for the understanding and the detailed explanation. I also agree that going that direction is the right one. In the CF community we don't have a well defined deprecation process and maybe that could help regarding the messaging around this change, but this is a topic for the TOC. In this change I'm concerned about the many apps we already have on the cflinuxfs4 stack, where some of them could break with the next CF update containing the Ruby and Python removal. This is an effect from the short timelines between cflinuxfs3 deprecation and the availability of cflinuxfs4 but this is another topic :-). The proposed mitigations need to be executed by end users of CF and our experience is that this takes time. Additionally, we have to announce such breaking changes three months in advance. I think that it will help us and in general make end users of CF happier if we can find a way how the CF operators could mitigate this for end users and offer a deprecation period to them. Do you see any options in that direction?
Regards,
Beyhan

Hi folks,
There is a proposed RFC for this change. This was discussed in the last TOC meeting on 2023-04-04. The meeting notes are available here. We will be happy to get your feedback on this.
Regards,
Beyhan

authors: beyhan h0nIg jochenehret krismarc ryanmoran


text:
TOC Candidate Nomination for Beyhan Veli

Candidate Name: Beyhan Veli (@beyhan)
Affiliation: SAP SE
Nomination Statement: Beyhan has been active in the Cloud Foundry community for the past 7+ years. He started to contribute to the Cloud Foundry community as member of the BOSH team at SAP. His focus areas have been BOSH in general, BOSH DNS, BOSH monitoring, the BOSH command line interface, and bosh-deployment. Additionally, he actively helped people via the community BOSH slack channel and gave sessions about BOSH at CF Summit and CF Operators SIG . E.g. in 2020, he did a CF summit session titled "A Journey Through BOSH and BOSH DNS Monitoring" (https://sched.co/fDVn, https://youtu.be/jpnMKWKFhT0).
Since one year, Beyhan has taken on a broader role at SAP and is now also looking into other areas of Cloud Foundry like the Cloud Controller and general topics from a Cloud Foundry developer experience perspective. In the CF Community, Beyhan is technical lead in the Foundational Infrastructure working group and acted as the co-chair for the CF Summit 2021 "Behind the Curtain" track.

@loewenstein thanks, so glad to see this nomination come in!
@beyhan can you please reply or give a 👍 to indicate you accept the nomination? Thanks!

+1

Closing as the 2022 TOC election has concluded.

authors: beyhan emalm loewenstein

repo: cloudfoundry/community


text:
Add Tim Downey as a CLI reviewer

Hello, I would like to formally be a review for the CF CLI. Here are some of my past contributions:

Commits: https://github.com/cloudfoundry/cli/commits?author=tcdowney
PRs: https://github.com/cloudfoundry/cli/pulls?q=is%3Apr+author%3Atcdowney+is%3Aclosed

We need two thumps up or approvals from the CLI approvers for this pr before it can be merged because the CLI are has more than four approvers.

@cloudfoundry/wg-app-runtime-interfaces-cli-approvers

The Reviewer requirements are met. Welcome @tcdowney in CLI area of ARI WG.

authors: Gerg beyhan stephanme tcdowney


text:
Improve performance of registry.Register

The use of IncrementCounter vs BatchIncrement counter causes
registry.Registry to be 6~7x slower
with sender.IncrementCounter:
go test -run Benchmark -bench=.
BenchmarkRegisterWith100KRoutes-4         100000             23244 ns/op
BenchmarkRegisterWithOneRoute-4           100000             19677 ns/op
PASS
ok      code.cloudfoundry.org/gorouter/registry 17.593s

with batcher.BatchIncrementCounter:
go test -run Benchmark -bench=.
BenchmarkRegisterWith100KRoutes-4         300000              3616 ns/op
BenchmarkRegisterWithOneRoute-4           500000              3032 ns/op
PASS
ok      code.cloudfoundry.org/gorouter/registry 8.872s

This commit changes the behavior of one of Gorouter's metrics:
Instead of the registry_message counter metric being emitted on every
NATS message, it will emit the metric on a set interval.
Thanks for contributing to gorouter. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

An explanation of the use cases your change solves

Instructions to functionally test the behavior change using operator interfaces (BOSH manifest, logs, curl, and metrics)

Expected result after the change

Current result before the change

Links to any other associated PRs

[x] I have viewed signed and have submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[x] I have run all the unit tests using bin/test

[ ] I have run CF Acceptance Tests on bosh lite

@flawedmatrix Thank you for helping the team improve performance.
Will the metric name change?
How often will it be emitted? Based on other gorouter metrics documented here, I would expect every 5 seconds.
On merging this PR, we will also need a PR to update the CF docs: https://github.com/cloudfoundry/docs-running-cf/blob/master/metrics/_routing.html.md.erb

@shalako
The metric name isn't changed as part of this PR. It's emitted on the same interval as all the other batch metrics in gorouter (5 seconds).
Here's a performance report showing the comparison between how gorouter currently handles 100K routes and after making this improvement + the improvement in this PR: https://github.com/cloudfoundry/gorouter/pull/174
registry_perf.pdf

prioritized for eng team review

authors: flawedmatrix shalako

repo: cloudfoundry/gorouter


text:
CF Routes that a displayed as links should default to https when port is 443

cf routes don't contain scheme info, and there doesn't appear to be a solid way to determine it from the port
at the moment we default everything to http. we should default to https when port is 443
See https://cloudfoundry.slack.com/archives/C80EP4Y57/p1606138125060900

The port field is only for TCP routes - there is no way of us knowing that an HTTP route should be accessed via https rather than http.

I think the best solution for this is just to allow this to be configurable in the deployment/installation, instead of a hardcoded false value in the following places:
https://github.com/cloudfoundry/stratos/blob/423c2417d52edddfcd68215b8971c9d3a6e9f752/src/frontend/packages/cloud-foundry/src/shared/components/list/list-types/cf-routes/table-cell-route/table-cell-route.component.ts#L21
https://github.com/cloudfoundry/stratos/blob/423c2417d52edddfcd68215b8971c9d3a6e9f752/src/frontend/packages/cloud-foundry/src/shared/components/list/list-types/cf-routes/cf-routes-data-source-base.ts#L91
https://github.com/cloudfoundry/stratos/blob/423c2417d52edddfcd68215b8971c9d3a6e9f752/src/frontend/packages/cloud-foundry/src/features/applications/application.service.ts#L265
That way, the "default" for that deployment could at least be more correct for that particular environment.
Like, in our case, we use HTTPS everywhere, so a default of HTTP for us doesn't make any sense, and so being able to switch this to HTTPS would solve everything for our use case.
You will of course have cases where some apps run with HTTP and some with HTTPS, but at least the admins will have an option to configure the most sensible default for their environment, that fits with the majority of the apps that are being deployed.

An alternative would be to support opt-in configuration to display routes for both http and https schemes:

authors: gberche-orange maximhan nwmac richard-cox

repo: cloudfoundry/stratos

license: MIT


text:
Allow to set database.testwhileidle

With this PR the property database.testwhileidle can be set for the UAA via this bosh release.
It is already possible to configure this property in the UAA via uaa.yml, however it is not possible to configure it via bosh release. With this PR this is now possible. As the value defaults to false in the UAA, also here the default value will be false (-> no change in the current behavior)

@bruce-ricard Did the answers from @tack-sap clarify the open points? Are there any other things that block the PR merge where we could help?

authors: tack-sap torsten-sap

repo: cloudfoundry/uaa-release


text:
Unable to map attributes from SAML assertion

Hello
I have set up the UAA (version 4.14.0) to act as a SP and integrated ADFS as IDP. The login procedure works fine however I cannot get the UAA to map any of the SAML attributes. The users are created with a user name such as XXXXX@unknown.org.
Here's the config I am using. I would like to map the group, given_name, family_name and email attributes:
login:     saml:         signatureAlgorithm: SHA256         providers:             some-idp:             nameID: urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified             idpMetadata: <redacted>             signMetadata: true             signRequest: true             showSamlLoginLink: true             linkText: Log in with IDP             metadataTrustCheck: false             groupMappingMode: AS_SCOPES             attributeMappings:                 external_groups:                     - group                 given_name: givenname                 family_name: surname                 email: emailaddress

Closing due to inactivity.

authors: mruf shamus

repo: cloudfoundry/uaa


text:
Backups getting stucked on walArchivingFailing phase

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
vatsal.sharma@kavida.ai
Version
1.22.2
What version of Kubernetes are you using?
1.28
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
Helm
What happened?
Have deployed the cnpg operator and cluster successfully on my eks cluster, but the scheduled backups is getting stucked at walArchivingFailing phase.
Below given is my helm values.yaml file for the cluster ->
`# -- Override the name of the chart
nameOverride: ""
# -- Override the full name of the chart
fullnameOverride: ""

###
# -- Type of the CNPG database. Available types:
# * `postgresql`
# * `postgis`
type: postgresql

###
# -- Cluster mode of operation. Available modes:
# * `standalone` - default mode. Creates new or updates an existing CNPG cluster.
# * `replica` - Creates a replica cluster from an existing CNPG cluster. # TODO
# * `recovery` - Same as standalone but creates a cluster from a backup, object store or via pg_basebackup.
mode: standalone

recovery:
  ##
  # -- Available recovery methods:
  # * `backup` - Recovers a CNPG cluster from a CNPG backup (PITR supported) Needs to be on the same cluster in the same namespace.
  # * `object_store` - Recovers a CNPG cluster from a barman object store (PITR supported).
  # * `pg_basebackup` - Recovers a CNPG cluster viaa streaming replication protocol. Useful if you want to
  #        migrate databases to CloudNativePG, even from outside Kubernetes. # TODO
  method: backup

  ## -- Point in time recovery target. Specify one of the following:
  pitrTarget:
    # -- Time in RFC3339 format
    time: ""

  ##
  # -- Backup Recovery Method
  backupName: ""  # Name of the backup to recover from. Required if method is `backup`.

  ##
  # -- The original cluster name when used in backups. Also known as serverName.
  clusterName: ""
  # -- Overrides the provider specific default endpoint. Defaults to:
  # S3: https://s3.<region>.amazonaws.com"
  # Leave empty if using the default S3 endpoint
  endpointURL: ""
  # -- Specifies a CA bundle to validate a privately signed certificate.
  endpointCA:
    # -- Creates a secret with the given value if true, otherwise uses an existing secret.
    create: false
    name: ""
    key: ""
    value: ""
  # -- Overrides the provider specific default path. Defaults to:
  # S3: s3://<bucket><path>
  # Azure: https://<storageAccount>.<serviceName>.core.windows.net/<containerName><path>
  # Google: gs://<bucket><path>
  destinationPath: ""
  # -- One of `s3`, `azure` or `google`
  provider: s3
  s3:
    region: ""
    bucket: ""
    path: "/"
    accessKey: ""
    secretKey: ""
  azure:
    path: "/"
    connectionString: ""
    storageAccount: ""
    storageKey: ""
    storageSasToken: ""
    containerName: ""
    serviceName: blob
    inheritFromAzureAD: false
  google:
    path: "/"
    bucket: ""
    gkeEnvironment: false
    applicationCredentials: ""

cluster:
  # -- Number of instances
  instances: 2

  # -- Name of the container image, supporting both tags (<image>:<tag>) and digests for deterministic and repeatable deployments:
  # <image>:<tag>@sha256:<digestValue>
  imageName: ""  # Default value depends on type (postgresql/postgis/timescaledb)

  # -- Image pull policy. One of Always, Never or IfNotPresent. If not defined, it defaults to IfNotPresent. Cannot be updated.
  # More info: https://kubernetes.io/docs/concepts/containers/images#updating-images
  imagePullPolicy: Always

  # -- The list of pull secrets to be used to pull the images.
  # See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-LocalObjectReference
  imagePullSecrets: []

  storage:
    size: 20Gi
    storageClass: "gp3"

  # -- The UID of the postgres user inside the image, defaults to 26
  postgresUID: 26

  # -- The GID of the postgres user inside the image, defaults to 26
  postgresGID: 26

  # -- Resources requirements of every generated Pod.
  # Please refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more information.
  # We strongly advise you use the same setting for limits and requests so that your cluster pods are given a Guaranteed QoS.
  # See: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/
  resources:
    limits:
      cpu: 2000m
      memory: 8Gi
    requests:
      cpu: 200m
      memory: 1Gi

  priorityClassName: ""

  # -- Method to follow to upgrade the primary server during a rolling update procedure, after all replicas have been
  # successfully updated. It can be switchover (default) or in-place (restart).
  primaryUpdateMethod: switchover

  # -- Strategy to follow to upgrade the primary server during a rolling update procedure, after all replicas have been
  # successfully updated: it can be automated (unsupervised - default) or manual (supervised)
  primaryUpdateStrategy: unsupervised

  # -- The instances' log level, one of the following values: error, warning, info (default), debug, trace
  logLevel: "debug"

  # -- Affinity/Anti-affinity rules for Pods.
  # See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-AffinityConfiguration
  affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
            - matchExpressions:
                - key: Deployment
                  operator: In
                  values:
                    - copilot
#    topologyKey: topology.kubernetes.io/zone

  # -- The configuration for the CA and related certificates.
  # See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-CertificatesConfiguration
  certificates:

  # -- When this option is enabled, the operator will use the SuperuserSecret to update the postgres user password.
  # If the secret is not present, the operator will automatically create one.
  # When this option is disabled, the operator will ignore the SuperuserSecret content, delete it when automatically created,
  # and then blank the password of the postgres user by setting it to NULL.
  enableSuperuserAccess: true
  superuserSecret: ""

  monitoring:
    # -- Whether to enable monitoring
    enabled: true
    podMonitor:
      # -- Whether to enable the PodMonitor
      enabled: true
    prometheusRule:
      # -- Whether to enable the PrometheusRule automated alerts
      enabled: true
      # -- Exclude specified rules
      excludeRules: []
        # - CNPGClusterZoneSpreadWarning
    # -- Custom Prometheus metrics
    customQueries:
       - name: "pg_cache_hit_ratio"
         query: "SELECT current_database() as datname, sum(heap_blks_hit) / (sum(heap_blks_hit) + sum(heap_blks_read)) as ratio FROM pg_statio_user_tables;"
         metrics:
           - datname:
               usage: "LABEL"
               description: "Name of the database"
           - ratio:
               usage: GAUGE
               description: "Cache hit ratio"

  # -- Configuration of the PostgreSQL server.
  # See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-PostgresConfiguration
  postgresql: {}
    # max_connections: 300

  # -- BootstrapInitDB is the configuration of the bootstrap process when initdb is used.
  # See: https://cloudnative-pg.io/documentation/current/bootstrap/
  # See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-bootstrapinitdb
  initdb: {}
    # database: app
    # owner: "" # Defaults to the database name
    # secret: "" # Name of the secret containing the initial credentials for the owner of the user database. If empty a new secret will be created from scratch
    # postInitSQL:
    #   - CREATE EXTENSION IF NOT EXISTS vector;

  additionalLabels: {}
  annotations:
    cnpg.io/skipWalArchiving: "enabled"

backups:
  # -- You need to configure backups manually, so backups are disabled by default.
  enabled: true

  # -- Overrides the provider specific default endpoint. Defaults to:
  # S3: https://s3.<region>.amazonaws.com"
  endpointURL: ""  # Leave empty if using the default S3 endpoint
  # -- Specifies a CA bundle to validate a privately signed certificate.
  endpointCA:
    # -- Creates a secret with the given value if true, otherwise uses an existing secret.
    create: false
    name: ""
    key: ""
    value: ""

  # -- Overrides the provider specific default path. Defaults to:
  # S3: s3://<bucket><path>
  # Azure: https://<storageAccount>.<serviceName>.core.windows.net/<containerName><path>
  # Google: gs://<bucket><path>
  destinationPath: ""
  # -- One of `s3`, `azure` or `google`
  provider: s3
  s3:
    region: "us-east-1"
    bucket: "ds-mongodb-backup"
    path: "/postgresbackup/"
    accessKey: "AKIAZMOEICVTYDS2R5RXHB"
    secretKey: "eWKStVPqqI2nzq5uYCJKDWlOTxQT2RjlsWFsnx2CYR"
  azure:
    path: "/"
    connectionString: ""
    storageAccount: ""
    storageKey: ""
    storageSasToken: ""
    containerName: ""
    serviceName: blob
    inheritFromAzureAD: false
  google:
    path: "/"
    bucket: ""
    gkeEnvironment: false
    applicationCredentials: ""

#  wal:
#    # -- WAL compression method. One of `` (for no compression), `gzip`, `bzip2` or `snappy`.
#    compression: gzip
#    # -- Whether to instruct the storage provider to encrypt WAL files. One of `` (use the storage container default), `AES256` or `aws:kms`.
#    encryption: AES256
#    # -- Number of WAL files to be archived or restored in parallel.
#    maxParallel: 1
  data:
    # -- Data compression method. One of `` (for no compression), `gzip`, `bzip2` or `snappy`.
    compression: gzip
    # -- Whether to instruct the storage provider to encrypt data files. One of `` (use the storage container default), `AES256` or `aws:kms`.
    encryption: AES256
    # -- Number of data files to be archived or restored in parallel.
    jobs: 2

  scheduledBackups:
    - name: daily-backup
      schedule: "0 0 10 * * *"
      backupOwnerReference: self

  # -- Retention policy for backups
  retentionPolicy: "15d"

pooler:
  # -- Whether to enable PgBouncer
  enabled: true
  # -- PgBouncer pooling mode
  poolMode: transaction
  # -- Number of PgBouncer instances
  instances: 1
  # -- PgBouncer configuration parameters
  parameters:
    max_client_conn: "1000"
    default_pool_size: "25"

  monitoring:
    # -- Whether to enable monitoring
    enabled: true
    podMonitor:
        # -- Whether to enable the PodMonitor
      enabled: true

  # -- Custom PgBouncer deployment template.
  # Use to override image, specify resources, etc.
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
              - key: Deployment
                operator: In
                values:
                  - copilot

  template: {}`

Could anyonee please help me with the same why is it getting stuck and not working properly.
Cluster resource
No response
Relevant log output
No response
Code of Conduct

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

I had the same problem. Deleted all the filels in the WAL folder on s3 and everything resumed working.

Cluster pod logs should give you the reason. Most common was bucket folder having wals already in it. You need to specify a different location for backups.

I'm experiencing the same issue on a newly bootstrapped cluster with an empty S3 bucket. I verified that the AWS S3 credentials are working and that containers can write to it. However, the absence of a detailed error makes this difficult to debug. I noticed "backup already running" in the operator logs.
Operator logs:
{"level":"info","ts":"2024-07-15T00:00:00Z","msg":"Next backup schedule","controller":"scheduledbackup","controllerGro
{"level":"info","ts":"2024-07-15T00:00:00Z","msg":"Creating backup","controller":"scheduledbackup","controllerGroup":"postgresql.cnpg.io","controllerKind":"ScheduledBackup","ScheduledBackup":{"name":"scheduled-backup","namespace":"best"},"namespace":"best","name":"scheduled-backup","reconcileID":"b31e7cac-347c-4158-8493-8c8a05e301fe","uuid":"2dc8a92f-423d-11ef-84b6-c6399d9139b1","backupName":"scheduled-backup-20240715000000"}
{"level":"info","ts":"2024-07-15T00:00:00Z","logger":"backup-resource","msg":"default","version":"v1","name":"scheduled-backup-20240715000000","namespace":"best"}
{"level":"info","ts":"2024-07-15T00:00:00Z","logger":"backup-resource","msg":"validate create","version":"v1","name":"scheduled-backup-20240715000000","namespace":"best"}
{"level":"info","ts":"2024-07-15T00:00:00Z","msg":"Next backup schedule","controller":"scheduledbackup","controllerGroup":"postgresql.cnpg.io","controllerKind":"ScheduledBackup","ScheduledBackup":{"name":"scheduled-backup","namespace":"best"},"namespace":"best","name":"scheduled-backup","reconcileID":"b31e7cac-347c-4158-8493-8c8a05e301fe","uuid":"2dc8a92f-423d-11ef-84b6-c6399d9139b1","next":"2024-07-15T00:00:00Z"}
{"level":"info","ts":"2024-07-15T00:00:00Z","msg":"Next backup schedule","controller":"scheduledbackup","controllerGroup":"postgresql.cnpg.io","controllerKind":"ScheduledBackup","ScheduledBackup":{"name":"scheduled-backup","namespace":"best"},"namespace":"best","name":"scheduled-backup","reconcileID":"24ae6d1e-b548-4fca-a72a-17215af9b785","uuid":"2de16b8c-423d-11ef-84b6-c6399d9139b1","next":"2024-07-16T00:00:00Z"}
{"level":"info","ts":"2024-07-15T00:00:01Z","msg":"Starting backup","controller":"backup","controllerGroup":"postgresql.cnpg.io","controllerKind":"Backup","Backup":{"name":"scheduled-backup-20240715000000","namespace":"best"},"namespace":"best","name":"scheduled-backup-20240715000000","reconcileID":"de927665-4853-4e49-ae5f-9e4485e7a6de","uuid":"2ddcce2f-423d-11ef-84b6-c6399d9139b1","cluster":"db","pod":"db-2"}
{"level":"info","ts":"2024-07-15T00:09:02Z","msg":"Backup is already running on","controller":"backup","controllerGroup":"postgresql.cnpg.io","controllerKind":"Backup","Backup":{"name":"scheduled-backup-20240715000000","namespace":"best"},"namespace":"best","name":"scheduled-backup-20240715000000","reconcileID":"9261bcc0-af7b-45d6-a440-587b6045d625","uuid":"71476548-423e-11ef-84b6-c6399d9139b1","cluster":"db","pod":"db-2","started at":"<nil>"}

Backup status:
on  best ☸ admin@best-prod (best) in via 🐍 v3.10.14 (venv) ❯ k describe backup scheduled-backup-20240715000000
Namespace:    best
Labels:       cnpg.io/cluster=db
              cnpg.io/immediateBackup=false
              cnpg.io/scheduled-backup=scheduled-backup
Annotations:  <none>
API Version:  postgresql.cnpg.io/v1
Kind:         Backup
Metadata:
  Creation Timestamp:  2024-07-15T00:00:00Z
  Generation:          1
  Owner References:
    API Version:     postgresql.cnpg.io/v1
    Controller:      true
    Kind:            ScheduledBackup
    Name:            scheduled-backup
    UID:             c4994e69-52d5-42ee-8679-5129e58f5b65
  Resource Version:  4491710
  UID:               fd29e4bd-2f63-4174-ba84-967f69cbc5cb
Spec:
  Cluster:
    Name:  db
  Method:  barmanObjectStore
Status:
  Backup Name:       backup-20240715000002
  Destination Path:  s3://best-prod-cnpg-backup
  Instance ID:
    Container ID:  containerd://65dae0a3eca6f7491bad969b52dc84d719ffd33af9827a9dd5fe94355f338912
    Pod Name:      db-2
  Method:          barmanObjectStore
  Phase:           walArchivingFailing
  s3Credentials:
    Access Key Id:
      Key:   AWS_ACCESS_KEY_CNPG
      Name:  secrets-config
    Secret Access Key:
      Key:      AWS_SECRET_KEY_CNPG
      Name:     secrets-config
  Server Name:  db
Events:         <none>

I recreated my cluster and noticed an S3 access error when trying to write the first WAL archive during the bootstrap phase. It turns out the S3 permissions were not permissive enough for Barman, and S3 access was the real issue. I modified my s3 policy from allowing only:
        Action = [
          "s3:GetObject",
          "s3:PutObject",
          "s3:ListBucket"
        ]

to:
        Action = [
          "s3:*",
          "s3-object-lambda:*",
        ]

Logging Barman errors when backups are performed would be incredibly helpful in diagnosing and fixing S3 access issues.

I had the same problem. Deleted all the filels in the WAL folder on s3 and everything resumed working.

This worked for me so closing the issue

authors: mpsOxygen rochecompaan salotz vatsal-kavida

repo: cloudnative-pg/cloudnative-pg


text:
The plugin command: cnp report operator fails if the operator was deployed with more than one replica

If we deploy the operator with more than one replica and run the command
kubectl cnp report operator
We receive the following error:
Error: could not get operator pod: number of running operator pods greater than 1: 2 pods running
This is caused by the following code block:
https://github.com/cloudnative-pg/cloudnative-pg/blob/27404c93ad728ef1654c2c439b0555df56dee666/internal/cmd/plugin/report/deployments/deployments.go#L60-L62
We should make the function GetOperatorPod more robust by allowing it to handle multiple replica operator deployments

Code looks good. Also, compiled the plugin and tested that it works with 2 operator Pods.
Nice job @armru

authors: armru jsilvela


text:
zh-translation: docs/root/configuration/listeners/network_filters/red…

…is_proxy_filter.rst

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes: docs/root/configuration/listeners/network_filters/redis_proxy_filter.rst
Release Notes:
[Optional Runtime guard:]
[Optional Fixes #Issue] #260
[Optional Deprecated:]

@vgbhfive 非常棒的翻译，就一个小 comment 仅供参考。

@addozhang 晓辉，看一下这个 PR 是否还有问题。

authors: majinghe vgbhfive

repo: cloudnativeto/envoy


text:
Historical command line editing is broken

what
Concerning version 0.12.6. Also reproduced in 0.11.0.
Editing historical command lines using emacs keys is broken in certain circumstances. My guess is that it has to do with a divergence between the actual length of the prompt when output versus the length of the prompt when queried by the command line editor.
Reproducing this bug is a little tricky. This seems to work for me, but you might have to try some variations.

Enter a long command at the command line:echo top level this is a long command

Press the up-arrow ↑ to recall the command to the command line.
Press ctrl-A to move the cursor to the beginning of the command line.

Expected: cursor hovers over "e" in echo.
Observed: cursor hovers over "c" in echo.
why
Not only does this cause difficulty in editing historical command lines, it results in a dangerous situation where the command visible on the command line is not exactly what will be submitted when you hit return.

What version are you using?
You can set PROMPT_STYLE=plain which will probably eliminate your problems

Using 0.12.6. Previously using 0.11.0 which did not have this problem.
PROMPT_STYLE=plain does not solve the problem.
Commenting out PROMPT_HOOKS+=("geodesic_prompt") from /etc/profile.d/prompt.sh eliminates the issue (and the nice prompt) but of course does not survive a restart of the container.

Replacing /etc/profile.d/prompt.sh with version from 0.9.18 does not solve the problem, nor does unsetting PROMPT_HOOKS.

This is what I see in iTerm2:

Maybe related to my terminal (why it works).
Can you try just radically simplifying the prompt characters in /etc/profile.d and removing all the tput statements.
If that works, we can introduce another prompt format.

I'm using the OS X Terminal. I seem to see some improvement in Terminal if I turn on the "Unicode East Asian Ambiguous characters are wide" option in Terminal -> Preferences -> Advanced, but not complete solution. What do you see when you search for "echo" and then start to edit the line (key sequence ctrl-R e c h o ctrl-A)? I see a colon left over from search and the cursor over the space between the colon and the "e" in "echo".

Okay, I think we'll introduce a new prompt style that uses these gyphs: 0x20E0, 0x2234
∴ ⃠

FWIW, I reproduced the issues in iTerm2 version 3.1.7. The problem goes away in iTerm2 if the option "Use Unicode Version 9 widths" it enabled. Documentation for this feature says "Unicode version 9 offers better formatting for Emoji."
Glyphs 0x20E0 and 0x2234 seem to have the same problem of being double-width and messing up Terminal. Using those in the prompt will not solve this issue.

I suggest you use these single-width glyphs instead.
✗
BALLOT X
Unicode: U+2717, UTF-8: E2 9C 97
✓
CHECK MARK
Unicode: U+2713, UTF-8: E2 9C 93
⨠
Z NOTATION SCHEMA PIPING
Unicode: U+2A20, UTF-8: E2 A8 A0

Fixed in https://github.com/cloudposse/geodesic/releases/tag/0.15.0

authors: Nuru osterman

repo: cloudposse/geodesic


text:
typo fix: ue to us

what

Change ue to us in new

why

Typo 😬

references

#41

/test all


text:
Specify instance count

How do I specify if I want more than 1 instance of this module?

@prandelicious, thanks for reaching out!
Unfortunately, this module does not support a custom instance_count parameter via a variable at this time. I would welcome the addition if you want to submit a PR. The effort should be minimal.
https://github.com/cloudposse/terraform-aws-ec2-instance/blob/master/main.tf#L2

@prandelicious soooon you can https://github.com/cloudposse/terraform-aws-ec2-instance/pull/28

@prandelicious although, wouldn't you want to use an asg at that point?

@Jamie-BitFlight I think it depends on the use-case. An ASG would be less suitable for stateful applications.
For example, using the count parameter is kind of like StatefulSets in kubernetes, while using ASG is more like using Deployments in kubenretes. I would use the strategy in this module for deploying Kafka.

@prandelicious A new module has been created, and will be published soon that allows for a set of instances to be created as you require.
https://github.com/cloudposse/terraform-aws-ec2-instance-group/pull/1

The instance group module has been released. Big thanks to @jamie-bitflight for seeing it through.

authors: Jamie-BitFlight osterman prandelicious


text:
Iam authenticator

what
This enabled AWS IAM authenticator in testing.cloudposse.co
Note that this PR does not enforce IAM authentication and we can still talk to the k8s API via regular kubectl export kubecfg
why
So that we can use IAM roles for RBAC
dependant PRs
https://github.com/cloudposse/terraform-root-modules/pull/111
https://github.com/cloudposse/geodesic/pull/376
testing
Build testing.cloudposse.co (also using the above PRs)
 ✓   (cpco-testing-admin) ~ ⨠  build-kube-cfg
download: s3://cpco-testing-kops-state/us-west-2.testing.cloudposse.co/pki/issued/ca/keyset.yaml to ../tmp/tmp.JDBsYKcEQV
Wrote Kube cfg to /dev/shm/kubecfg...

kubecfg is templated as below:
 ✓   (cpco-testing-admin) ~ ⨠  cat /dev/shm/kubecfg
apiVersion: v1
kind: Config
preferences: {}

clusters:
- cluster:
    server: https://api.us-west-2.testing.cloudposse.co
    certificate-authority-data: <REDACTED>
  name: us-west-2.testing.cloudposse.co

contexts:
- context:
    cluster: us-west-2.testing.cloudposse.co
    user: us-west-2.testing.cloudposse.co
  name: us-west-2.testing.cloudposse.co

current-context: us-west-2.testing.cloudposse.co

users:
- name: us-west-2.testing.cloudposse.co
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: aws-iam-authenticator
      args:
      - token
      - -i
      - us-west-2.testing.cloudposse.co

test it works and we can auth against the k8s API:
 ✓   (cpco-testing-admin) ~ ⨠  kubectl get nodes
NAME                                           STATUS   ROLES    AGE   VERSION
ip-172-20-100-72.us-west-2.compute.internal    Ready    master   4h    v1.10.11
ip-172-20-111-167.us-west-2.compute.internal   Ready    node     22d   v1.10.11
ip-172-20-35-199.us-west-2.compute.internal    Ready    node     12d   v1.10.11
ip-172-20-41-111.us-west-2.compute.internal    Ready    master   4h    v1.10.11
ip-172-20-45-164.us-west-2.compute.internal    Ready    node     55d   v1.10.11
ip-172-20-92-206.us-west-2.compute.internal    Ready    node     6h    v1.10.11
ip-172-20-94-81.us-west-2.compute.internal     Ready    master   4h    v1.10.11

Should this be running under atlantis?

Note that this PR does not enforce IAM authentication and we can still talk to the k8s API via regular kubectl export kubecfg

I think that's acceptable. I like that we have an escape hatch for now

@osterman It is currently failing as the release of terraform-root-modules hasn't been cut yet. https://github.com/cloudposse/terraform-root-modules/pull/111 Will need to be merged and a release cut, I've just jumped the gun a little here.

authors: joshmyers osterman


text:
GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.30 to before v4.14.259",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d4e0fe01a38a073568aee541a0247fe734095979",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8d0c927a9fb2b4065230936b77b54f857a3754fc"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d4e0fe01a38a073568aee541a0247fe734095979",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "8d0c927a9fb2b4065230936b77b54f857a3754fc",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "igbvf: fix double free in `igbvf_probe`\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.259 by commit 8d0c927a9fb2b4065230936b77b54f857a3754fc, it was introduced in version v2.6.30 by commit d4e0fe01a38a073568aee541a0247fe734095979. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002634

repo: cloudsecurityalliance/gsd-database


text:
fix: verbosity to the failed read file

Currently the application only closes when reading a schedule configuration that does not exist. This PR presents an error for client if the file does not exist.
Example problem:
scheduled-backups $ go run cmd / scheduler / main.go -config schedule.not-found.config.yaml
scheduled-backups $

@googlebot I signed it!

Hi @hengfengli, can you see if this fix is valid for this repository?

@bernardo-bruning Nice catch. 👍  Sorry that I did't get any notifications until you tagged me now.

authors: bernardo-bruning hengfengli

repo: cloudspannerecosystem/scheduled-backups


text:
The method Cloudstate().start(config) does not work

When I try to start Cloudstate java-support using the start method that receives a Config as a parameter, it does not go up the server (ActorSystem) the problem seems to be related to:
public CloudStateRunner createRunner (Config config) {
    return new CloudStateRunner (services, config);
  }

And
  def this (services: java.util.Map [String, StatefulService], config: Config) {
    this (ActorSystem ("StatefulService", config), services.asScala.toMap)
  }

When I use the start () method without configuration the server goes up normally.
I verified that the Hocon configuration is read correctly by my code according to the logs below:
Status: Downloaded newer image for sleipnir / kotlin-shoppingcart: latest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar: file: /app/libs/logback-classic-1.2.3.jar! /Org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar: file: /app/libs/slf4j-simple-1.7.26.jar! /Org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
03: 14: 14.901 [main] DEBUG io.cloudstate.javasupport.impl.AnySupport - Attempting to load com.google.protobuf.Message class com.example.shoppingcart.Shoppingcart $ AddLineItem
03: 14: 14.906 [main] DEBUG io.cloudstate.javasupport.impl.AnySupport - Attempting to load com.google.protobuf.Message class com.google.protobuf.Empty
03: 14: 14.908 [main] DEBUG io.cloudstate.javasupport.impl.AnySupport - Attempting to load com.google.protobuf.Message class com.example.shoppingcart.Shoppingcart $ RemoveLineItem
03: 14: 14.911 [main] DEBUG io.cloudstate.javasupport.impl.AnySupport - Attempting to load com.google.protobuf.Message class com.example.shoppingcart.Shoppingcart $ GetShoppingCart
03: 14: 14.914 [main] DEBUG io.cloudstate.javasupport.impl.AnySupport - Attempting to load com.google.protobuf.Message class com.example.shoppingcart.Shoppingcart $ Cart
03: 14: 15.002 [main] DEBUG io.cloudstate.kotlinsupport.ReflectionHelper - Process Runtime class ShoppingCartEntity type: class ShoppingCartEntity
03: 14: 15.026 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - EventHandler for method public final void ShoppingCartEntity.itemAdded (com.example.shoppingcart.persistence.Domain $ ItemAdded) found. Parameter: com.example.shoppingcart.persistence.Domain $ ItemAdded arg0. Class: class com.example.shoppingcart.persistence.Domain $ ItemAdded
03: 14: 15.028 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - EventHandler for method public final com.example.shoppingcart.Shoppingcart $ LineItem ShoppingCartEntity.itemRemoved (com.example.shopping.istam. ) found. Parameter: com.example.shoppingcart.persistence.Domain $ ItemRemoved arg0. Class: class com.example.shoppingcart.persistence.Domain $ ItemRemoved
03: 14: 15.035 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - SnapshotHandler for method public final void ShoppingCartEntity.handleSnapshot (com.example.shoppingcart.persistence.Domain $ Cart) found. Parameter: com.example.shoppingcart.persistence.Domain $ Cart arg0. Class: class com.example.shoppingcart.persistence.Domain $ Cart
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> snapshot
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> handleSnapshot
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> itemAdded
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> itemRemoved
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> getCart
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> addItem
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> removeItem
03: 14: 15.036 [main] DEBUG io.cloudstate.kotlinsupport.api.eventsourced.KotlinEventBehaviorReflection - AllMethods :: Method -> access $ convert
03: 14: 15.040 [main] INFO io.cloudstate.kotlinsupport.CloudStateRunner - Loading Config ...
03: 14: 15.222 [main] INFO io.cloudstate.kotlinsupport.CloudStateRunner - Load config library.name: kotlin-support
03: 14: 15.222 [main] INFO io.cloudstate.kotlinsupport.CloudStateRunner - Load config library.version: 0.5.0
03: 14: 15.222 [main] INFO io.cloudstate.kotlinsupport.CloudStateRunner - Load config user-function-port: 8080
03: 14: 15.222 [main] INFO io.cloudstate.kotlinsupport.CloudStateRunner - Load config user-function-interface: 0.0.0.0

The method I am using to start the application is part of kotlin support:
  fun start (): CompletionStage <Done> = engine.start (getConfig ())

And getConfig () has already been defined in several ways in the attempt to succeed, the most recent being this:
private fun getConfig(): Config {
        log.info("Loading Config...")
        setEnv(
                mapOf("SUPPORT_LIBRARY_NAME" to "kotlin-support",
                        "SUPPORT_LIBRARY_VERSION" to getProjectVersion()))

        val properties = Properties()
        properties.setProperty("cloudstate.system.akka.loglevel", initializer.configInit.loglevel)
        properties.setProperty("cloudstate.system.akka.actor.provider", "local")
        properties.setProperty("cloudstate.system.akka.coordinated-shutdown.exit-jvm", "on")
        properties.setProperty("cloudstate.system.akka.http.server.preview.enable-http2", "on")
        properties.setProperty("cloudstate.system.akka.http.server.idle-timeout", "infinite")
        properties.setProperty("cloudstate.eventsourced.snapshot-every", "100")
        properties.setProperty("cloudstate.library.name", "kotlin-support")
        properties.setProperty("cloudstate.library.version", getProjectVersion())
        properties.setProperty("cloudstate.user-function-interface", initializer.configInit.host)
        properties.setProperty("cloudstate.user-function-port", initializer.configInit.port.toString())

        val conf = ConfigFactory.load()
        conf.getConfig("cloudstate.system").withFallback(conf)
        val appConf = ConfigFactory.parseProperties(properties)
                //.withFallback(conf)
                .resolve()
        log.info("Load config library.name: ${appConf.getString("cloudstate.library.name")}")
        log.info("Load config library.version: ${appConf.getString("cloudstate.library.version")}")
        log.info("Load config user-function-port: ${appConf.getString("cloudstate.user-function-port")}")
        log.info("Load config user-function-interface: ${appConf.getString("cloudstate.user-function-interface")}")
        return appConf
    }

Any help?
ping @pvlugter @viktorklang

@sleipnir,
i think the problem with the method Cloudstate().start(config) is that the passing config is just a small part of the actor system settings. This part should be merged in the whole actor system settings loaded with ConfigFactory.load().
I think it can be fixed this way:
def this(services: java.util.Map[String, StatefulService], config: Config) {
  // config is just a part of the actor system settings
  this(ActorSystem(
	   "StatefulService", {
	    val conf = ConfigFactory.load()
	     conf.getConfig("cloudstate.system").withFallback(config)
         }
      ),
      services.asScala.toMap)
}

Perhaps there is a better way.

Thanks @ralphlaude I had already tried this before opening the issue

I would expect the config loading to look something like this:
private fun getConfig(): Config {
  val properties = Properties()
  properties.setProperty("cloudstate.system.akka.loglevel", initializer.configInit.loglevel)
  properties.setProperty("cloudstate.library.name", "kotlin-support")
  properties.setProperty("cloudstate.library.version", getProjectVersion())
  properties.setProperty("cloudstate.user-function-interface", initializer.configInit.host)
  properties.setProperty("cloudstate.user-function-port", initializer.configInit.port.toString())

  val conf = ConfigFactory.load(ConfigFactory.parseProperties(properties))
  return conf.getConfig("cloudstate.system").withFallback(conf)
}

You only need to provide settings that you want to override, and let defaults be loaded from the reference conf. If you pass the custom config (from ConfigFactory.parseProperties) to ConfigFactory.load it will apply the reference defaults (and also system property overrides) automatically. And then you need to add the cloudstate.system overrides like the other constructor. That looks like it should work fine to me. What's the issue on start that you're seeing?

Hello I tested many shapes and none of them seemed to work. The example I showed was just one of them. It is the end of Sunday here in Brazil and tomorrow I will take another look at it. Thanks

@pvlugter your suggestion worked thank you
Thanks @ralphlaude

authors: pvlugter ralphlaude sleipnir

repo: cloudstateio/cloudstate


text:
Adding OriginReadTimeout aka OriginResponseTimeout to cloudfront orig…

Adding support for OriginReadTimeout to cloudfront

👍👍👍

more info on this option can be found here
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-customorigin.html#cfn-cloudfront-distribution-customoriginconfig-originreadtimeout

Thanks!

authors: bantam316 markpeek ntwaddell

repo: cloudtools/troposphere


text:
Add ODBC support for SQL Server Adapter v7.0

This pull request brings back ODBC support to activerecord-sqlserver-adapter gem which was revoked sometimes back,
With every rails upgrade, we also try to upgrade activerecord-sqlserver-adapter and bring ODBC support back to the repo.
This pull request contains total 13 commits out of which initial 9 commits are responsible for bring back ODBC and are being cherry-picked for every other upgrade as well.
The other four commits are specific to version 7 and needs specific review
Note - CI/CD checks are breaking here as there is a trouble installing ruby-odbc gem. The same has been happening in earlier releases as well. We have tested the changes internally and everything looks good. So, CI/CD checks can be ignored.

Have you added this or automatically created in CHANGELOG.md file. I guess it is created with using a gem, not sure, but I see pull request link "https://github.com/cloudvolumes/activerecord-sqlserver-adapter/pull/17" is missing in this file.
v7.0.4.0.odbc
Added

ODBC restoration.

Good work all, you should try to get the tests working and showcase this to the community. Obviously it is still needed, and with a little extra effort, it can be brought back to the gem officially!

Good work all, you should try to get the tests working and showcase this to the community…

Good to hear from you! -toj

authors: lavika raj-sharan smlsml tojified


text:
feature DE3633-empty_backtrace_email_notifier

email_notifier: Provide text for exception_text when exception.backtrace is nil
@fractalis Can you review this for me?

Awesome, and nice fix!
@ajayanty :+1 for merging

@bklang Another fix that we'll send upstream soon!

:+1: Love it! Thanks Stephen!

@ajayanty Can you merge when you get a chance?

authors: bklang fractalis rsuddeth sfgeorge

repo: cloudvox/adhearsion-reporter


text:
Fix markdown syntax error by adding blank line after 'Arguments' in e…

…xtraction schema generation.

When I ran
pandoc extraction_schemas.md -o extraction_schemas.html

and opened the HTML file in the browser, I was seeing this:

Adding the extra line after Arguments fixed it.

repo: clulab/processors


text:
Allow PIL image to be used as a CMUImage url

Tries to address:

#67

In case the argument passed to checkURL is a PIL image, raises an appropriate less confusing error and suggests a fix.

Thanks for this PR.
I'm using this test code:
from cmu_graphics import *
import os
from PIL import Image as PILImage

USE_MVC = os.environ.get('USE_MVC') == '1'

if USE_MVC:
    def redrawAll(app):
        drawRect(0, 0, 500, 500)
        drawImage(PILImage.open("/Users/evan/Desktop/Screenshot 2024-07-03 at 9.59.07 AM.png"), 0, 0)

    runApp()
else:
    Image(PILImage.open("/Users/evan/Desktop/Screenshot 2024-07-03 at 9.59.07 AM.png"), 0, 0)
    cmu_graphics.loop()

When I run in MVC mode, I see this:
An error occurred. Here is the stack trace:
  "/Users/evan/cpython-cmu-graphics/test.py", line 10:
        drawImage(PILImage.open("/Users/evan/Desktop/Screenshot 2024-07-03 at 9.59.07 AM.png"), 0, 0)
Exception: drawImage only accepts string URLs or instances of CMUImage.
            Did you forget to wrap a PIL image in a CMUImage?

When I run in non-MVC mode, I see this:
An error occurred. Here is the stack trace:
  "/Users/evan/cpython-cmu-graphics/test.py", line 14:
        Image(PILImage.open("/Users/evan/Desktop/Screenshot 2024-07-03 at 9.59.07 AM.png"), 0, 0)
Exception: drawImage only accepts string URLs or instances of CMUImage.
            Did you forget to wrap a PIL image in a CMUImage?

The error message looks good in MVC mode, but in non-MVC mode, we now reference drawImage even though the user didn't use drawImage.
I think instead of changing the error message, it would be nice to automatically wrap PIL Images with PILWrapper, whether you are drawing the drawImage() or Image(). Or if you just want to improve the error message, then this PR would need to be modified so that it shows a different message in non-MVC mode.

This took me the entirety of yesterday, but it should now be working as excepted and automatically wraps non CMUImage into CMUImage. There might be some small detail that could incite change but I hope you like this progress, and I am open for feedback.

I would like to know; is there any reason this pull request isn't merged?
The only thing I am doing here is wrapping PIL images in PIL wrapper at initialisation, instead of the student doing that in their program. Simple, quick and effective solution.

Hi there, thanks for checking in about this. I haven't merged this because it doesn't fully address the issue. See the July 15 comment on that issue. I didn't realize originally why we don't let you pass a PILImage to drawImage, but that comment explains it. I think the best thing for this PR would be to automatically wrap PILImage with a CMUImage as you are doing now, but cache the CMUImage so that if in a subsequent call to drawImage the user passes the same PILImage that they have passed before, then cmu_graphics will look up the CMUImage that we created before and use it instead of making a new one.
Alternatively, you could abandon the change that automatically wraps PILImage with a CMUImage, and go back to more or less what you had in 9bdb2d4, except fixing the wording problems that I pointed out here.

Ah yes, I see now.
Well, taking all of this into consideration I made several changes.
I think it is working great now. The only potential for improvement is if we could find a quicker hashing function for images as using the built in tobytes() function is just a tiny bit slow right now.
Additionally, with the current changes drawing images with a string as reference goes much faster, so if anything, these changes are a good improvement.
I hope this helps :)

authors: Mohamed-Waiel-Shikfa schmave

repo: cmu-cs-academy/desktop-cmu-graphics


text:
Selected indicator gets lost in date change

When I'm on explore an indicator mode, with vaccine acceptance, since it's not available for the current day I get a warning at the top telling me it was last available on June 25.

But when I click on June 25, it takes me to covid cases.

Maybe it's that covid cases is the default but we should make sure that the selected indicator doesn't get lost in date changes.

To be clear, I clicked on June 25 in the orange text box and that's what loses the vaccine acceptance indicator selection. When I just change the date in the date dropdown box (if I move back to June this way) then it keeps vaccine acceptance.

closing as a duplicate of #1241

repo: cmu-delphi/www-covidcast


text:
Provide possibility to specify codec (lossless cut)

Hi,
I would like to be able to cut video (using ConvertAsync) but with lossless codec (-codec copy).
I know I can use prepare the full, custom path and call ExecuteAsync but it would be nice ConvertAsync also supports custom parameters (or at least codec specification).  Or maybe it is possible already somehow?
greetings
Bartek

Hello,
A little add to the FFmpegArgumentBuilder.cs could be :
if (conversionOptions.BaselineProfile)
commandBuilder.Append(" -profile:v baseline ");
if (conversionOptions.CopyVideo)
commandBuilder.Append(" -c copy ");
In order to switch between 2 modes  : .BaselineProfile or .CopyVideo
Thanks for your work, I love and use SVC !

I added some parameters in ConversionOptions. For this case use VideoCodec parameter that sets the Encoder to be used
This should be available when #42 pull request is accepted

PR has been merged

authors: LwRed Nightmare204 bartekmotyl cmxl


text:
[ESP] add content/es/api_gateway.md

Based on issue #563
Please do a review of this concepts:
API Gateway : Concentrador API
I did not see any style guide or glossary about this translation.
Regards.

Preview should be available at https://deploy-preview-698--cncfglossary.netlify.app/es/api_gateway/ .
And please refer to https://github.com/cncf/glossary/pull/705#issuecomment-1090893838 . 😊

Gracias por tu contribución, coloque algunas sugerencias.

Ya hice los cambios, gracias por las observaciones!

@gamba47 podrías agregar las siguientes palabras al wordlist?
API
APIs
Gateway
technology
interface

@gamba47 podrías agregar las siguientes palabras al wordlist?
API
APIs
Gateway
technology
interface

done!

authors: electrocucaracha gamba47 jihoon-seo

repo: cncf/glossary


text:
fixes

Olá,
Inclui 2 alias no restarea pois ao finalizar a sua rotina se o usuário digitar o código do país o sistema apresenta erro pois o padrão é o índice 1
inclui também uma validação caso a consulta não retorne valor a rotina utilizar o conteúdo informado pelo usuário nos campos A1_NOME e A2_NOME dinamicamente.
Incluída rotina para truncar o tamanho da razão social conforme o tamanho dos campos A1_NOME e A2_NOME caso contrário o sistema apresenta erro.

Boa tarde
Perdão Renan, só vi agora!

repo: cnpj-ws/protheus


text:
config: CNF installation (3.1?) Limit cnf_setup to only one CNF

Description
Remove the ability of users to run cnf-testsuite cnf_setup {../testsuite.yml} multiple times.
Issues:
Refs: #2095 #2120
How has this been tested:

[x] Covered by existing integration testing
[x] Added integration testing to cover
[ ] Verified all A/C passes

[ ] develop
[ ] master
[ ] tag/other branch

[x] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[x] Kind cluster

[ ] Have not 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 not work as expected)
[ ] Documentation update

Checklist:
Documentation

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] No updates required.

Code Review

[ ] Does the test handle fatal exceptions, ie. rescue block

Issue

[ ] Tasks in issue are checked off

I have some problems with this one, the main issue is that it would be easiest to implement this change after the rest of the #2120 epic is already done. With #2120 finished we could leverage the ability of setting up multiple CNFs as one, as currently some tests (/spec/5g/ran_spec.cr) rely on setting up two CNFs. There is a hack around this, and that is to use the Helm.install function directly, followed up by KubectlClient::Get.resource_wait_for_install, which is not exactly pretty.

repo: cnti-testcatalog/testsuite


text:
builtins: add num_nulls, num_nonnulls builtins

PR: https://github.com/cockroachdb/cockroach/pull/51515
From release notes:

Added the num_nulls and num_nonnulls builtin functions, which count the number of arguments that are passed to them which are NULL or non-NULL, respectively. [#51515][#51515] {% comment %}doc{% endcomment %}

This is already documented.

authors: ericharmeling lnhsingh

repo: cockroachdb/docs


text:
[DOC-6045] Remove stray sentence fragment

[DOC-6045]

This change is

authors: cockroach-teamcity mdlinville


text:
Update C# code samples to use secure connections

Addresses part of #3700.
Summary of changes:

Update C# code samples to show how to connect to secure clusters (this
is using code from @BramGruneir and @rolandcrosby - thanks guys!).

Update the instructions in the docs to show how to create the
PKCS#12-formatted certificates which are required by C# (thanks for
the magic openssl incantation @mberhault).

Various updates and copy edits to make the page work like our other
updated "Build an app" examples, i.e., using the new includes,
providing secure and insecure examples, etc.

Note: all of the changes to both docs and code were replicated across
both v2.1 and v2.2.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3b0133eaed411e5feda47ae66ec773ebd4ed3891/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a45a7b63767fdc3f72ddd5f9221a1dc0f076019d/

authors: cockroach-teamcity rmloveland


text:
Document fresher follower reads

Fixes #6001.
Addresses #6753.
Summary of changes:

Update 'Follower reads' page to:

Note shorter follower read timestamp value

Consolidate all mentions of that timestamp to point to one section,
where the value is listed (including links from other pages).

Note that AOST queries that are not far enough in the past will not
trigger follower reads (addresses #6753)

Consolidate some of the wording around what FRs are and how they
work.

Add links to definitions of "leaseholder", etc., in the architecture
docs.  This required adding anchors to the page listing the terms.

Add instructions for using the Admin UI's Custom Chart page to
verify that FRs are actually happening on your system.

Update 'AS OF SYSTEM TIME' to link to the follower read timestamp
definition directly.

Update 'Follower Reads Topology Pattern' to remove hardcoded mention
of FR timestamp and link to the canonical value on the 'Follower
Reads' page instead.

Update 'Enterprise Features' page to remove hardcoded mention of FR
timestamp and link to the canonical value on the 'Follower Reads' page
instead.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/fe27f7b8b5a5dace217ab882f3ff939c05c3b793/
Edited pages:

v20.1/as-of-system-time.md
v20.1/follower-reads.md
v20.1/topology-follower-reads.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d0c8eb9b4b47757b62f24a18d67fff6307be6566/
Edited pages:

v20.1/as-of-system-time.md
v20.1/follower-reads.md
v20.1/topology-follower-reads.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/551fab020aab6ac7e709ea969b2e85e86544ef32/
Edited pages:

v20.1/as-of-system-time.md
v20.1/follower-reads.md
v20.1/topology-follower-reads.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8dd9ad349a10f29116a2161b4f0672adf16178f0/
Edited pages:

v20.1/as-of-system-time.md
v20.1/follower-reads.md
v20.1/topology-follower-reads.md

@jseldess I think my latest update addressed all of your feedback.  Any objection to merge?


text:
Does it support typescript repos?

Hello. First of all, let me just say your docs seem top notch for such a low-star repo. I am currently working in a typescript monorepo with multiple package.json files which is handled by turborepo + pnpm workspaces. Can cocogitto work with typescript monorepos? Thanks in advance.

Can you try with actions/checkout@v3.4 ? Also if you use a pull request based flow I would suggest using cocogitto-bot instead of the action.

It worked. I love the cog check and cog edit functionality. Also, the detail of error logs are insane, makes wanna start learning rust again.

I can't access the Discord via the link invite...

authors: AlexandrosMelissas Rendez oknozor

repo: cocogitto/cocogitto


text:
IGVM: Embed firmware in IGVM file and parse OVMF metadata into IGVM parameter block

This PR adds support for embedding firmware, particularly OVMF into an IGVM file using the IGVM builder.
The Makefile has been updated to allow the OVMF file to be specified by the FW_FILE environment variable. This needs to be set to the OVMF.fd file (and not the separate OVMF_CODE.fd and OVMF_VARS.fd files). When provided, the firmware binary is parsed by the IGVM builder during the build to extract metadata which is then populated into the IGVM parameter block, passed to SVSM.
By providing the metadata in the IGVM parameter block, SVSM does not need to parse the OVMF metadata when using an IGVM file. The SVSM has been updated to reflect this by removing the fw_metadata IGVM parameter that specified the OVMF metadata page. In the future, if IGVM is solely used to configure the SVSM then the OVMF metadata parsing can be removed entirely from SVSM.

@msft-jlange, on reflection following our email conversation it is probably best to hardcode the firmware base calculation for QEMU and just return an error at the moment if --firmware is specified for Hyper-V as I don't know how the base address will be calculated in this case. This means I can remove --fwtop and --fwbase.
I've pushed a new version with this change.

repo: coconut-svsm/svsm


text:
SpriteBuilder renamed to CocosBuilder

SpriteBuilder has been renamed Cocosbuilder
ccbLang files have been renamed ccblang

2ebdae1a03e5c97037f0c4f9c854aeeebf8cfe49

authors: SimsonEnduro oxeron

license: mit


text:
Boldface not working on competition pages

This is bold
does not result in boldface fonts.

@madclam
Do you have a specific example?
You can see in this competition main page that "classification tasks" is in bold:
https://www.codabench.org/competitions/870/
Your problem may be that the markdown is not interpreted because it is mixed with HTML:

#879

I close this issue to keep track of this in the new issue

authors: Didayolo madclam

repo: codalab/codabench


text:
Problem with debug log level : no message written in console

Hello, I just started using angular2-logger and I think I faced an issue with it. Basically I can't manage to write to the debug level, and I dont understand why the code is different only for this level?
https://github.com/code-chunks/angular2-logger/blob/4fece8bc7b1381b23053d1a8c6b8622afb0e60f6/app/core/logger.ts#L79
Please tell me if you need additionnal config settings. I just followed what's written on the README page.
Regards
Videl

Ops I just saw #172... That was it. Sorry ;-)


text:
fix: force peerDependencies vue and add tailwind

修复 element-plus@1.0.2-beta.53 vue版本问题，模板添加tailwindcss依赖

感谢，element-plus 暂时先升级到 1.2.0 版本，tailwindcss 已经加入到依赖中。
但是这次只能 close 这条 pr，建议不同功能分开提交。再次感谢

authors: codexu singleManFan

repo: code-device/x-build


text:
能否支持spark3呢？

非常好的项目，但是能否支持spark3呢？

最近比较忙，国庆前后发布一下spark3。

authors: code-ferry lohcve

repo: code-ferry/ansible-middleware


text:
Could pointcloud2 be available for rviz?

Hi, first I want to say thank you for your great work!
Now, I have a question that when I use rviz, I could not make Pointcloud2 and Camera show the data of topics they subscribe.
Among the ways of visualization, it seems that only Image could work and show the data of /Kinect2/rgb/image.
I don`t know how to deal with it. Could you give me a hand?
Thank you in advance!

Could you copy and past the terminal output of kinect2_bridge here? Does the registration_viewer work?

It solved with the help of @wiedemeyer. So many thanks to you!
For me, there is a mistake that I forgot to modify the cmakelists.txt. For more details, please check
https://github.com/code-iai/iai_kinect2/issues/92
What`s more, if you want to use rviz, please set Fixed Frame as kinect2_rgb_optical_frame.

authors: KahnShi wiedemeyer


text:
Document possibility to access container registry using docker/podman locally

General information
https://github.com/code-ready/crc/issues/147 says access to container registry is possible but that seems to not be the case - at least it is not documented.
Ask is to be able to get container registry access so can use docker, podman, jib, etc. to build and push containers locally without requiring remote quay etc.

https://github.com/code-ready/crc/issues/147#issuecomment-577151340

Rather make this dependent on the clients beinmg available and the podman functionality going GA.

thanks for link to the comment - I didn't spot it as I was looking the docs ;)
it would be nice with a crc env docker command or similar one could use to do the login/setup docker env etc.

Rather make this dependent on the clients beinmg available and the podman functionality going GA.

Not following what you mean here? I don't need any custom clients or podman to push to registry; lots of things can do push, including maven/gradle builds.

it would be nice with a crc env docker command or similar one could use to do the login/setup docker env etc.

We will likely not be introducing a docker-env command, but podman-env would be possible to set values for this.

container-env Or registry-env works If goal is to avoid product/project specific names.

container-env goes nicely with the Containerfile naming alternative (to Dockerfile)

authors: cfergeau gbraad maxandersen

repo: code-ready/crc


text:
Enhance the troubleshooting guide

We could use examples of how to gather information to be used for troubleshooting purposes.

one would be #160, but also commands like oc get co

Seems we could also use crc delete && crc start --log-level debug. We could at least mention this in docs as part of the suggestion to open a new issue in this repo.

If you mention crc delete, you need to make it very clear it's going to lose all changes which were done to the CodeReady Containers instance.

As far as I'm concerned, this is done.

authors: cfergeau gbraad robin-owen


text:
feature: Add "Mark as Done" Button for Videos and Notes to Manually Track Completion

Is your feature request related to a problem? Please describe.
I'm frustrated with how the current system marks content as "done." For video lectures, completion is tracked based on whether I watch the video until the end of the timeline. However, many lectures include extended Q&A sessions, and the core content might only last for 1–1.5 hours out of a 2-hour video. This means that even if I've completed the main lecture, it isn't marked as "done."
Similarly, there is no mechanism to track whether I’ve read notes completely. Since only the user knows if they’ve reviewed the notes, it would be helpful to have a way to manually mark them as "done."
Describe the solution you'd like
I would like a "Mark as Done" button for both videos and notes. This button would allow users to manually mark content as completed.

For videos: The current automatic tracking based on the timeline should remain in place, but users should also have the option to manually mark content as done.
For notes: This feature would provide the only way to indicate completion, since there is no automated tracking for them.

Describe alternatives you've considered

For videos: Adjust the current tracking mechanism to allow users to mark specific timestamps (e.g., after the main lecture ends) as the completion point.
For notes: Implement scroll-tracking or text-highlight tracking to estimate completion. However, these methods may not be reliable or user-friendly.

Additional context
Adding a "Mark as Done" button empowers users to track progress more accurately and flexibly. Here's a mockup of how the button might look on the content page (if needed, we can alter this as required ). This feature would also be helpful for users revisiting content who want to reset or update their completion status manually.

/assign

/assign @devsargam can i submit a PR for this ?

dont have to wait to be assigned, just create a pr


text:
fix a bug with devices list --include-settings

There's a bug with devices list --include-settings caused by the addition of row.pop() to _process_csv_row. This fixes it by passing in a list of dicts as expected, instead of a list of strings.
I'm not sure if we're passing lists of strings to run_bulk_process() anywhere else, but if we are those should probably be updated as well.

Looks like an integration test is failing? I'm not sure why though, I don't think I touched anything that it'd look at


text:
fix(questionnaire): school autocomplete matchs fourm field width

visual bug to be fixed:

repo: codeRIT/hackathon-manager


text:
About - 姚工的备份 - backup

https://codet.github.io/3-about/?
姚工的技术文章和记忆备份

test


text:
Transparent Background not working

Adding Color.Transparent to
val donutChartConfig = PieChartConfig(
            backgroundColor = Color.Transparent, //transparent color
            strokeWidth = 120f,
            activeSliceAlpha = .9f,
            isAnimationEnable = true,
            labelVisible = true,
            labelColor = Color.Black,
            isEllipsizeEnabled = true,
            labelFontSize = 16.sp,
            chartPadding = 16,
        )

        Column(
            modifier = Modifier
                .fillMaxWidth().padding(horizontal = 12.dp, vertical = 8.dp),
            horizontalAlignment = Alignment.CenterHorizontally,
        ) {
            DonutPieChart(
                modifier = Modifier
                    .fillMaxWidth()
                    .background(Color.Transparent),
                donutChartData,
                donutChartConfig
            )
            Legend(donutChartData.slices, listOfColor)
        }

Results in a black background behind the circle instead of a transparent background.

I'm facing the same issue. I've set the background on a LineChart to transparent, but it renders as the background color instead of the composable that is actually underneath.

Yeah I made a fork to fix it that way.

You don't actually set transparency through the modifier for canvas. You would actually need to change the background for Surface(). Surface() is causing the issue. By default the Surface() is not transparent and we need to make it transparent like so:
Surface(
modifier =modifier,
color = Color.Transparent)
{
}
The inner most composable should determine the background colors not surface.

authors: ErickSorto mathklk

repo: codeandtheory/YCharts


text:
seeInField not work for textarea for webdriverio

What are you trying to achieve?
I want to check what value was setted to textarea
What do you get instead?
I get error
  - I.seeInField({"css":"textarea"}, "Hello world") at Test.Scenario.only (tests/user-scenario/Forms/Platinum/happy-path.test.js:14:11)
  - I.fillField({"css":"textarea"}, "Hello world") at Test.Scenario.only (tests/user-scenario/Forms/Platinum/happy-path.test.js:13:11)
  - I.saveScreenshot("debug.png") at Test.Scenario.only (tests/user-scenario/Forms/Platinum/happy-path.test.js:12:11)
  - I.amOnPage("https://html.com/tags/textarea/") at Test.Scenario.only (tests/user-scenario/Forms/Platinum/happy-path.test.js:11:11)

  TypeError: Cannot read property 'indexOf' of null
      at Object.comparator (node_modules/codeceptjs/lib/assert/include.js:16:23)
      at InclusionAssertion.assert (node_modules/codeceptjs/lib/assert.js:36:36)
      at Object.browser.elementIdAttribute.then.res (node_modules/codeceptjs/lib/helper/WebDriverIO.js:2010:144)
      at Object.exec (node_modules/webdriverio/build/lib/helpers/safeExecute.js:28:24)
      at Object.resolve (node_modules/webdriverio/build/lib/webdriverio.js:191:29)
      at node_modules/webdriverio/build/lib/webdriverio.js:540:32
      at _fulfilled (node_modules/q/q.js:854:54)
      at node_modules/q/q.js:883:30
      at Promise.promise.promiseDispatch (node_modules/q/q.js:816:13)
      at node_modules/q/q.js:624:44

Provide console output if related. Use --verbose mode for more details.

# paste output here

Provide test source code if related

If in proceedSeeField add part of code, test will be work is good
if (tag.value === 'textarea') {
    const proceedTextArea = el => this.browser.getValue(el).then(res => stringIncludes(`fields by ${field}`)[assertType](value, res));
    return proceedTextArea(res.selector)
  }

Details

CodeceptJS version: 1.4.6
NodeJS Version: v10.14.0
Operating System: Ubuntu 18.94
Protractor || WebDriverIO || Nightmare version (if related) WebDriverIO
Configuration file:

# paste suite config here

Any update on this ?

authors: SimonKlausLudwig Vorobeyko

repo: codeceptjs/CodeceptJS


text:
Extend Registration Form to capture more user's details

Is your feature request related to a problem? Please describe.
We need to know more about the user when they sign up. We will use this data to give users offerings/opportunities in future.
Describe the solution you'd like
Add more registration field like

First Name
Last name
City
Country
Gender (Male, Female, Prefer not to say).
Date of Birth
Phone Number

I was thinking we make it later when the user updates their profile. It's overwhelming to have to provide all of these details at registration.

That's fine then. We have to make it mandatory though. We need that data. This is how we can pair them with recruiters in future.

So could you modify your req/feat to state this

Alright

authors: ofuochi tayormi

repo: codeclannigeria/codeclannigeria-backend


text:
[FEAT] Forgot password page

A user should be able to request a password reset.

Assign to me

Connect to API left

authors: rammyblog seunbayo


text:
Support ES6 block scoping

(Related to #15 and #16)
Is it easy to add support for ES6 block scoping for let and const?
It's somewhat meaningless (and even confusing) to have let and const but no block scoping for them, because it's the main difference between them and var.

It's not so hard.
You would need to expand the Scope class to track both the block scope, and the function scope.  This gets a little tricky when things like declaring a let inside a for loop deceleration is considered.
It's on my TODO list for sure.

Thanks for working on this feature!
I've tried the code at #16 again, but it still doesn't work as expected.
To make it work as expected, I still need to change this line:
const char = string[i]

to:
let char = string[i]

Hi, is PR #20 "Closure fixes" for fixing this issue?

It improves the situation but does not fix it entirely.

authors: basicer ngocdaothanh


text:
Some Amendments

I am just making a few changes here to try and get this working.

Still trying to determine the best way of avoiding forcing users to have an acf-folder in their dev-theme if they don't want it.

repo: codeconverters-nl/wp-theme-starter


text:
Space Traveler's Hub

In this PR:-
We have merged dev branch into main branch accidentally Please consider this PR for our final submission.
@codedit334

[x] Fetching Mission data from Spacex API.
[x] Rendering Mission list using Redux and React.
[x] Created join mission button for reservation.
[x] Created cancel mission button for cancel reservation.

@ShiroYaksha90

[x] Fetching Dragon data from Spacex API.
[x] Rendering Dragon list using Redux and React.
[x] Created join Dragon button for reservation.
[x] Created cancel Dragon button for cancel reservation.

@shubhambhoyar077

[x] Fetching Rockets data from Spacex API.
[x] Rendering Rockets list using Redux and React.
[x] Created join Rockets button for reservation.
[x] Created cancel Rockets button for cancel reservation.

Group:-

[x] Created NavBar using NavLinks
[x] Created tests for each components.
[x] Added styling.

Additional requirements:-

[x] Enhance the My Profile section by adding a placeholder message when the "My Missions" or "My Rockets" lists are empty (no missions joined or no rockets reserved).

[x] Enhance the My Profile section by adding the "Cancel reservation" and "Leave Mission" buttons to the lists here. Clicking them should dispatch the actions you have already used in the main Rockets and Missions sections.

Hi @rotimiazeez @Lameck1 ,
Thanks for taking the time to review our code... We'll make sure this issue won't happen again.


text:
Removes install fix, no longer needed. Numbers don't matter.

Also tweaks wording a bit.

Thanks! Nice catch!

Apparently this isn't fixed yet... so... the quest continues!

repo: codeforboston/cliff-effects


text:
[FEATURE] Register basic user

Register a Viewer (basic user)
Register viewer user

Tooltip and visible password

Validation

Requirements

Six input fields

First Name (required)
Last Name (required)
Email Address (required, email)
Phone Number (required, phone)
Create Password (required, minimum password requirements)
Re-enter Password (required, match)

Show Password
Submit Button
Link to Login Page
Validation for all fields

I'd like to take this ticket

Closing after merge

repo: codeforboston/police-data-trust


text:
Spark Electron: Cellular dev kit with a simple data plan

I don't think any part of this makes exact sense for what we're doing, but I'll still drop it here.
https://www.kickstarter.com/projects/sparkdevices/spark-electron-cellular-dev-kit-with-a-simple-data?ref=home_popular

That's pretty awesome.  I'll see if I can figure out if it, or an
additional shield, can provide gps coords.
On Thu, Feb 26, 2015 at 10:44 AM Adam Gautsch notifications@github.com
wrote:

I don't think any part of this makes exact sense for what we're doing, but
I'll still drop it here.
https://www.kickstarter.com/projects/sparkdevices/spark-electron-cellular-dev-kit-with-a-simple-data?ref=home_popular
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/18.

Awesome! Dan did you see that I have a SIM running on T-Mobile that is active and ready? The Android phone that I thought was going to work isn't charging via the cable anymore so I don't think it will work, but I've got an active SIM that will work if anyone has a device.

authors: agautsc jeremywight thedanfields

repo: codeforgreenville/trolley-tracker


text:
UIコンポーネント作成（Chakra UIをラップ）

#70

[WIP]themeをカスタマイズ
FormLabelのラップ OstFormLabel を追加
Textareaのラップ OstTextarea を追加
Inputのラップ OstInput を追加
Selectのラップ OstSelect を追加
Checkboxのラップ OstCheckbox を追加
Buttonのラップ OstButton を追加
Linkのラップ OstLink を追加

メモ

とりあえずすべて forwardRef で囲っています。不要の場合は後ほど調整します。
スタイルは今のところ仮置きで、後ほど要調整です。
input系のスタイルは少々複雑なので、コンポーネントのThemeファイルを上書きするようにしました。デフォルトThemeをほぼそのまま持ってきているので、いくらかシンプルにできるかもです。
Buttonのスタイルもパターンが多いのでThemeの上書きで対応しています。
イベントまわりも仮置きです。

http://localhost:3000/test で試し表示

@yu23ki14 レビューありがとうございます！追加コミットしました！

repo: codeforjapan/OpenDataTools


text:
Add a time machine to allow user to travel through time

This lets user inspect historical counting data.

FYI: Mobile users won't see insight from this feature. Mobile screens are too small to see the buttons and numbers at the same time.

Personally, we can go with the current implementation.
What do you think?

authors: dtinth heytitle

repo: codeforthailand/election-live


text:
Update displayed title in bar to be same as title from Helmet

It seems like this is not attainable through Helmet itself.

repo: codefoundries/UniversalRelayBoilerplate


text:
Notice - Améliore la réutilisation

Bonjour, pour les besoins de France Chaleur Urbaine, nous utilisons extensivement le DSFR react et proposons les choses suivantes pour améliorer la réusabilité du composant Notice

Supprimer isClosable -> s'il y a un onClose, cela parait suffisant pour afficher le bouton close
Supprimer le title et le remplacer par children. Cela permettra de rajouter potentiellement des liens à l'intérieur et d'utiliser une casse différente
Ajouter un onClick -> aujourd'hui il est difficile d'ajouter un lien sur ce composant, or nous l'utilisons en haut de page pour présenter une nouvelle fonctionnalité

transmettre l'evenement de click au onClose

Merci

Bonjour @martinratinaud,
Merci pour tes suggestions.
Je n'ai pas écrit ce composant, donc je le découvre en parcourant cette issue. Bien que le typage des props soit difficile à lire (j'ai d'ailleurs fait un commit pour l'améliorer), je trouve que le design de l'API de ce composant est globalement satisfaisant.

Supprimer isClosable -> s'il y a un onClose, cela paraît suffisant pour afficher le bouton de fermeture

Il peut être pertinent de rendre la notice closable sans pour autant nécessiter un callback pour une action à exécuter lors de sa fermeture.

Supprimer title et le remplacer par children, permettant ainsi d'ajouter des liens ou d'utiliser une autre casse

Le type de title est ReactNode, donc il ne s'agit pas nécessairement d'un string. Effectivement, utiliser children à la place de title serait plus esthétique, mais cela reste une considération mineure.
Écrire :
<Notice title={<Link>MonLien</Link>} />

ou
<Notice>
    <Link>MonLien</Link>
</Notice>

revient au final au même, et je ne pense pas que cela justifie un breaking change.

Ajouter un onClick -> aujourd'hui, il est difficile d'ajouter un lien dans ce composant, bien que nous l'utilisions en haut de page pour présenter une nouvelle fonctionnalité

Un onClick serait souvent trop restrictif. On veut éviter d'inciter les développeurs à écrire quelque chose comme :
<Notice
   onClick={() => {
     location.href = routes.profile({ tabId: "notification" }).link.href;
   }}
   title="Vous avez une nouvelle notification"
/>

Cela rechargerait l'application en entier lors du clic, et l'utilisateur ne pourrait pas utiliser le clic droit, ouvrir dans un nouvel onglet, ou copier l'adresse du lien.
Nous préférons quelque chose comme :
<Notice
    title={(
        <a {...routes.profile({ tabId: "notification" }).link}>
            Vous avez une nouvelle notification
        </a>
    )}
/>

(Ici, j'utilise un exemple avec TypeRoute, mais cela dépend du système de routage en place.)

Transmettre l'événement de clic au onClose

Ok, je l'ajoute, mais je suis un peu hésitant. L'API JS de DSFR (vanilla) ne permet pas de fermer impérativement ce composant, donc, actuellement, la fermeture se fait nécessairement via un événement de clic.
Cependant, il serait envisageable que la fermeture puisse aussi se faire via dsfr(element).notice.conceal(). Dans ce cas, il n'y aurait pas d'événement de clic à transmettre au callback. Je modifierai l'API si celle de DSFR évolue.
Garder en tête que vous êtes tout a fait libre de copier coller le code du composant dans votre codebase et de le modifier pour qu'il s'adapte a vos besoin spéficique.
Il suffit juste de remplacer les import relatifs avec des imports absolut:
-import { fr } from "./fr";
+import { fr } from "@codegoufr/react-dsfr/fr";
-import { cx } from "./tools/cx";
+import { cx } from "@codegouvfr/react-dsfr/tools/cx";
...

Ok, c'est noté, merci pour ces réponses super détaillées

authors: garronej martinratinaud

repo: codegouvfr/react-dsfr


text:
is there any kind of documentation on centos 7?

have anybody can get this working on centos 7? is there a step by step guide like ubuntu?

At which point did you get stuck? Paste as many details as possible so we can help.
(Personally I've never used centos so there aren't any guides)

nope everything working fine, but still need guide for those who dont know

Do we need an installation guide? i.e., was it painful for you to set this library up on your machine?
If so, would you like to provide an installation guide? Otherwise I'll look into it.

well i think not yet, but it sure could save people time, ok then let me see, ill open this when its ready to review

:+1:

authors: adamramadhan codelucas

repo: codelucas/newspaper


text:
Feature / New functionality - Allow transport of less strict data-types non-json serializable data

Description
Requiring strict json serialization capable data types between RPC endpoints can limit users ability to share functionality without creating an additional translation layer.
I.e Custom Data Type -> Json Structured -> Rpc Transport -> Json Load - > Restructure Data Type.
The additional translation often means that data may be serialized / deserialized more than once. JSON serialization is also not the best performing serialization method.
Solution
Core
Using pythons built in pickle serialization, objects & data types can be sent between RPC endpoints as bytes & deserialized as the same data type, removing translation interface requirements.

[x] - Implement default serialization between EasyRpc endpoints: EasyRpcServer -> EasyRpcServer, EasyRpcProxy -> EasyRpcServer

Bonus
Function annotations could be implemented but not fully mirrored by their proxy counterparts. While implementing the above pickle serialization, annotations of methods and their associated datatypes can be serialized & sent to a proxy which could then fully mirror the origin methods annotations. This removes

[x]  - Add support for annotations & transporting associated datatypes to proxies when created by EasyRpcProxies / or with server_proxies.

Completed in #4

repo: codemation/easyrpc


text:
Overlapping text markers - conflicting title property

Hi,
Please review this: https://jsfiddle.net/7sy8smma/1/
We have two overlapping markers. Both have titles which browsers show on tooltip. On the overlapping segment, comdemirror uses the marker which came first. Shouldnt it use the marker which came last? In the attached jsfiddle, the bold section should have title 'span-2' and the underlying section should have title 'span-1'.
I believe this is a bug. Am i missing something?
Thanks and regards
Abhishek Ganguly

Markers aren't really ordered/layered in CodeMirror's model, and since a DOM element can have only one title, any tie-breaking solution seems acceptable. So I'm going to call this the intended behavior.

authors: abhigan marijnh

repo: codemirror/CodeMirror