text:
Cleanup: update golangci-lint and fix new linters alerts

This PR should be just a cleanup with no intended functional changes.
It fixes the following 129 alerts. I split the unused-parameter fixes between the one with and without context.ctx removal.
Please review carefully the commit that removes unused parameters since some look very suspicious and could correspond to bugs (the author might have not used the param without realizing it).
pkg/stacktracetree/stacktracetree_test.go:11:17               revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/stacktracetree/stacktracetree.go:37:26                    revive  empty-block: this block is empty, you can remove it
pkg/stacktracetree/stacktracetree.go:39:33                    revive  empty-block: this block is empty, you can remove it
pkg/vmtests/list.go:38:38                                     revive  unused-parameter: parameter 'testDir' seems to be unused, consider removing or renaming it as _
cmd/tetragon/conf_test.go:1075:22                             revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
cmd/tetragon/conf_test.go:1145:20                             revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
cmd/protoc-gen-go-tetragon/helpers/helpers.go:192:2           revive  if-return: redundant if ...; err != nil check, just return error instead.
pkg/testutils/sensors/load.go:25:91                           revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/testutils/sensors/load.go:46:68                           revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/sensors/exec/cgroups_test.go:244:33                       revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
contrib/rthooks/tetragon-oci-hook/main.go:33:19               revive  unused-parameter: parameter 'log' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:16:27                               revive  unused-parameter: parameter 'polID' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:20:27                               revive  unused-parameter: parameter 'polID' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:24:33                               revive  unused-parameter: parameter 'podID' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:28:27                               revive  unused-parameter: parameter 'podID' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:32:33                               revive  unused-parameter: parameter 'podID' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:36:24                               revive  unused-parameter: parameter 'podID' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/dummy.go:40:37                               revive  unused-parameter: parameter 'podInformer' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/map.go:73:2                                  revive  if-return: redundant if ...; err != nil check, just return error instead.
pkg/policyfilter/k8s_test.go:83:19                            revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/state.go:485:11                              revive  superfluous-else: if block ends with a continue statement, so drop this else and outdent its block (move short variable declaration to its own line if necessary)
pkg/bench/trace_bench_rw.go:104:50                            revive  unused-parameter: parameter 'args' seems to be unused, consider removing or renaming it as _
pkg/bench/trace_bench_rw.go:121:40                            revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/bench/trace_bench_custom.go:15:33                         revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/bench/trace_bench_open.go:58:52                           revive  unused-parameter: parameter 'args' seems to be unused, consider removing or renaming it as _
pkg/bench/trace_bench_custom.go:33:44                         revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/bench/trace_bench_open.go:77:42                           revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/sensors/manager_test.go:25:38                             revive  unused-parameter: parameter 'p' seems to be unused, consider removing or renaming it as _
pkg/sensors/load.go:168:31                                    revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/sensors/load.go:183:27                                    revive  unused-parameter: parameter 'stopCtx' seems to be unused, consider removing or renaming it as _
pkg/sensors/load.go:239:27                                    revive  unused-parameter: parameter 'stopCtx' seems to be unused, consider removing or renaming it as _
pkg/sensors/load.go:315:22                                    revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/sensors/load.go:347:16                                    revive  unused-parameter: parameter 'bpfDir' seems to be unused, consider removing or renaming it as _
pkg/reader/network/network.go:14:22                           revive  unused-parameter: parameter 'op' seems to be unused, consider removing or renaming it as _
pkg/api/readyapi/readyapi.go:19:44                            revive  unused-parameter: parameter 'ev' seems to be unused, consider removing or renaming it as _
pkg/api/readyapi/readyapi.go:23:36                            revive  unused-parameter: parameter 'internal' seems to be unused, consider removing or renaming it as _
pkg/api/readyapi/readyapi.go:31:35                            revive  unused-parameter: parameter 'o' seems to be unused, consider removing or renaming it as _
pkg/sensors/tracing/generickprobe.go:666:95                   revive  unused-parameter: parameter 'version' seems to be unused, consider removing or renaming it as _
pkg/sensors/tracing/generickprobe.go:708:97                   revive  unused-parameter: parameter 'version' seems to be unused, consider removing or renaming it as _
pkg/sensors/tracing/generictracepoint.go:521:80               revive  unused-parameter: parameter 'version' seems to be unused, consider removing or renaming it as _
pkg/sensors/tracing/selectors_test.go:245:14                  revive  empty-block: this block is empty, you can remove it
pkg/sensors/tracing/selectors_test.go:374:14                  revive  empty-block: this block is empty, you can remove it
pkg/sensors/tracing/kprobe_test.go:1000:56                    revive  unused-parameter: parameter 'path' seems to be unused, consider removing or renaming it as _
pkg/sensors/tracing/kprobe_test.go:2991:18                    revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/identitty.go:49:40                      revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/labels.go:84:38                         revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/port.go:74:36                           revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/protocol.go:93:40                       revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/reply.go:46:37                          revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/event_type.go:51:41                     revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/http.go:90:36                           revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/k8s.go:78:35                            revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/ip.go:62:34                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/verdict.go:44:39                        revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/fqdn.go:117:36                          revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/filters/k8s.go:104:39                           revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/sensors/program/loader.go:162:15                          revive  unused-parameter: parameter 'load' seems to be unused, consider removing or renaming it as _
pkg/sensors/program/loader.go:172:20                          revive  unused-parameter: parameter 'load' seems to be unused, consider removing or renaming it as _
pkg/sensors/program/loader.go:192:16                          revive  unused-parameter: parameter 'load' seems to be unused, consider removing or renaming it as _
cmd/tetragon-vmtests-run/image.go:159:22                      revive  unused-parameter: parameter 'rcnf' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:40:88                 revive  unused-parameter: parameter 'opts' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:53:36                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:57:43                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:61:46                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:65:39                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:69:38                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:73:39                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:77:40                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:81:42                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:85:42                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:89:44                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:93:37                 revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/tetra/getevents/io_reader_client.go:120:38                revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/cilium/dns.go:49:10                             revive  superfluous-else: if block ends with a continue statement, so drop this else and outdent its block
pkg/observer/observer_test_helper.go:175:28                   revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/observer/observer_test_helper.go:198:25                   revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/observer/observer.go:123:46                               revive  unused-parameter: parameter 'cpu' seems to be unused, consider removing or renaming it as _
tests/e2e/install/cilium/cilium.go:74:35                      revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/btf/validation_test.go:28:15                              revive  unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _
pkg/btf/btf.go:28:22                                          revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/bpf/loader.go:9:20                                        revive  unused-parameter: parameter 'linkName' seems to be unused, consider removing or renaming it as _
pkg/bpf/loader.go:13:22                                       revive  unused-parameter: parameter 'progFd' seems to be unused, consider removing or renaming it as _
pkg/bpf/perf_linux.go:671:27                                  revive  unused-parameter: parameter 'fd' seems to be unused, consider removing or renaming it as _
pkg/bpf/map_linux.go:375:2                                    revive  if-return: redundant if ...; err != nil check, just return error instead.
pkg/bpf/bpffs_linux.go:186:3                                  revive  if-return: redundant if ...; err != nil check, just return error instead.
pkg/bpf/bpffs_linux.go:216:3                                  revive  if-return: redundant if ...; err != nil check, just return error instead.
pkg/bpf/bpffs_linux.go:241:3                                  revive  if-return: redundant if ...; err != nil check, just return error instead.
pkg/bpf/bpffs_linux.go:276:3                                  revive  if-return: redundant if ...; err != nil check, just return error instead.
cmd/tetra/main.go:27:1                                        revive  redefines-builtin-id: redefinition of the built-in function new
operator/cmdref.go:32:18                                      revive  unused-parameter: parameter 's' seems to be unused, consider removing or renaming it as _
tests/e2e/tests/skeleton/skeleton_test.go:130:23              revive  unused-parameter: parameter 'kernelVersion' seems to be unused, consider removing or renaming it as _
pkg/policyfilter/rthooks/rthooks.go:33:26                     revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/exporter/exporter_test.go:73:39                           revive  unused-parameter: parameter 'original' seems to be unused, consider removing or renaming it as _
pkg/process/process.go:59:16                                  revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
tests/e2e/tests/labels/labels_test.go:123:25                  revive  unused-parameter: parameter 'kernelVersion' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:16:36                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/server.go:202:28                                   revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/server.go:207:51                                   revive  unused-parameter: parameter 'request' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:20:37                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/server.go:359:36                                   revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/server.go:366:29                                   revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:24:38                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:28:40                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:32:40                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:36:37                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:40:41                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:44:41                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:48:37                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/server/fake_observer.go:52:44                             revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/watcher/watcher.go:171:14                                 revive  unused-parameter: parameter 'podID' seems to be unused, consider removing or renaming it as _
pkg/filters/labels.go:46:38                                   revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
cmd/protoc-gen-go-tetragon/eventchecker/multichecker.go:29:2  revive  if-return: redundant if ...; err != nil check, just return error instead.
cmd/protoc-gen-go-tetragon/eventchecker/eventchecker.go:62:2  revive  if-return: redundant if ...; err != nil check, just return error instead.
cmd/protoc-gen-go-tetragon/eventchecker/field.go:355:86       revive  unused-parameter: parameter 'eventVar' seems to be unused, consider removing or renaming it as _
cmd/protoc-gen-go-tetragon/eventchecker/enum.go:29:2          revive  if-return: redundant if ...; err != nil check, just return error instead.
cmd/protoc-gen-go-tetragon/eventchecker/field.go:371:60       revive  unused-parameter: parameter 'checkerName' seems to be unused, consider removing or renaming it as _
pkg/rthooks/dummy.go:14:35                                    revive  unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec_test_helper.go:66:48                       revive  unused-parameter: parameter 'listener' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec_test_helper.go:68:51                       revive  unused-parameter: parameter 'listener' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:99:46                                   revive  unused-parameter: parameter 'ev' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:103:38                                  revive  unused-parameter: parameter 'internal' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:161:46                                  revive  unused-parameter: parameter 'ev' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:244:45                                  revive  unused-parameter: parameter 'ev' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:248:37                                  revive  unused-parameter: parameter 'internal' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:401:54                                  revive  unused-parameter: parameter 'ev' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:429:46                                  revive  unused-parameter: parameter 'internal' seems to be unused, consider removing or renaming it as _
pkg/grpc/exec/exec.go:446:45                                  revive  unused-parameter: parameter 'o' seems to be unused, consider removing or renaming it as _
pkg/oldhubble/servicecache/service_cache.go:94:50             revive  unused-parameter: parameter 'typ' seems to be unused, consider removing or renaming it as _
pkg/encoder/encoder.go:334:22                                 revive  unused-parameter: parameter 'p' seems to be unused, consider removing or renaming it as _

@mtardy I think all of the above type signature modifications are probably OK from a first pass. If we need them later we can add them back when the fields are actually used.

authors: mtardy willfindlay

repo: cilium/tetragon


text:
Support CCL search operators

Support https://github.com/cinchapi/ccl/pull/42
When search operators are included, query logic should leverage search() functions

To implement,
https://github.com/cinchapi/concourse/blob/19c4ae4b4c9858473436fdf0a14c1e1fdd207e6d/concourse-driver-java/src/main/java/com/cinchapi/concourse/thrift/TObject.java#L675: Add support for search operators
https://github.com/cinchapi/concourse/blob/19c4ae4b4c9858473436fdf0a14c1e1fdd207e6d/concourse-server/src/main/java/com/cinchapi/concourse/server/storage/db/Database.java#L536: Check if operator is a search operator and defer to the search call?

Need to have a fallback for timestamp queries with search operators. So, in the Database will need to support the search operators in the IndexRecord#findAndGet.

I think find is the only Store routine that calls into explore. If so, get rid of explore and just implement the logic in find directly. This will make it easy to call into the search method in the Database when trying to respond to a search operator

https://github.com/cinchapi/concourse/blob/develop/concourse-server/src/main/java/com/cinchapi/concourse/server/query/Finder.java#L129
An alternative is to add logic in Finder to check if the operator is a search operator and therefore defer to the engine search method. This will mean we can't support historical search

^^^ that won't work for navigation keys though

source: gharchive/issue

repo: cinchapi/concourse

license_type: permissive

license_source: bigquery


text:
🛑 CIOOS Data Explorer API is down

In 95dc1bc, CIOOS Data Explorer API (https://pac-dev2.cioos.org/ceda/api/) was down:

HTTP code: 502
Response time: 308 ms

Resolved: CIOOS Data Explorer API is back up in 94be536.

repo: cioos-siooc/cwatch-upptime

license: MIT

license_source: github-api


text:
Update scalafmt-core to 3.0.6

Updates org.scalameta:scalafmt-core from 3.0.5 to 3.0.6.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #138 (cf80718) into master (ea69638) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #138   +/-   ##
=======================================
  Coverage   54.41%   54.41%
=======================================
  Files           1        1
  Lines          68       68
=======================================
  Hits           37       37
  Misses         31       31

Continue to review full report at Codecov.

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

source: gharchive/pull-request

authors: codecov-commenter scala-steward

repo: circe/circe-spire


text:
Update refined, refined-scalacheck to 0.9.9

Updates

eu.timepit:refined
eu.timepit:refined-scalacheck

from 0.9.8 to 0.9.9.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "eu.timepit" }]

labels: semver-patch

Codecov Report

Merging #1207 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1207   +/-   ##
=======================================
  Coverage   86.51%   86.51%
=======================================
  Files          90       90
  Lines        2803     2803
  Branches      114      114
=======================================
  Hits         2425     2425
  Misses        378      378

Impacted Files
Coverage Δ

...scala/io/circe/shapes/LabelledHListInstances.scala
92.59% <0%> (-3.71%)
:arrow_down:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
89.02% <0%> (-3.66%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
78.52% <0%> (-0.62%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
86.25% <0%> (+0.5%)
:arrow_up:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
88.88% <0%> (+0.58%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io scala-steward

repo: circe/circe


text:
Update sbt to 1.9.0

About this PR
📦 Updates org.scala-sbt:sbt from 1.8.3 to 1.9.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #22.

repo: circe/sbt-circe-org


text:
MOD: out of range circ-median-ci

Hi,
Thanks for the implementation of pycircstat2, continuing on the former pycircstat.
I quickly got started and stumbled upon a small problem when instantiating a Circle (I unfortunately can't really share the bug), I suggested a very tiny patch for that feel free to check it out and see if it makes sense.

Thank you very much! Is it possible to add a test with some artificial data for this special case (to tests/test_descriptive/test_circ_median_ci())?

@miki998 Thank you very much again, and Happy New Year! I'll take a look after the New Year break.


text:
Linters

Agregamos los archivos de eslint y rubocop para evitar perdida de tiempo en reviews =)

Si hay una forma en Rubocop de "extender" como la que uso en eslint, la prefiero. Si es la única, que así sea.

Si hay una forma en Rubocop de "extender" como la que uso en eslint, la prefiero. Si es la única, que así sea.

Creo que no hay un "esta es la super base" igual googleo y te comento =P
Esto es lo que uso en el día a día, y cuando aparece algo que me molesta lo agrego/cambio.

Joya, no te volvás loco, si no existe que quede así y listo.

Mirá lo que acabo de encontrar.... Pero hay que meterlo en el gemfile....
https://github.com/github/rubocop-github
No debería haber nada mas confiable que el propio Gh jaja.

Uhh... se ve tentador... y creo que apuesto a que pongamos la gema. Después vemos si termina en mucha tortura =)

Ahí ya quedo "decente" arreglé algunos archivos con los linterns.

authors: Shelvak francocatena

repo: cirope/monitor

license: mit


text:
gitignore missing ds_store

💡 Summary
What is the work, as a high-level summary?
Add .DS_store to .gitignore
Motivation and context
This would be useful because...
It would prevent MacOS-specific configuration files from getting into the repo.
Implementation notes
Please provide details for implementation, such as:
Add this line to .gitignore
**/.DS_Store
Acceptance criteria
How do we know when this work is done?
When the updated .gitignore is checked into main.

Enhancement completed.  Added new line to .gitignore.  Can be safely merged into main at any time.

repo: cisagov/ScubaGear


text:
Error output from PS1 execution

Hi,
We are attempting to run 'C:\temp\Sparrow.ps1', however we continue to receive the following error:

I get this same series of errors in PowerShell 5.1
My full version: 5.1.19041.610

Have you tried https://raw.githubusercontent.com/cisagov/Sparrow/develop/Sparrow.ps1 ? It looks like you have the HTML file from the page instead of the raw ps1

Have you tried https://raw.githubusercontent.com/cisagov/Sparrow/develop/Sparrow.ps1 ? It looks like you have the HTML file from the page instead of the raw ps1

Thanks @overflowingInt. That was the problem! I've never experienced that issue, but grateful it was a simple fix. Thanks.

authors: cdev45 overflowingInt volleronline

repo: cisagov/Sparrow


text:
UI: Create Vulnerability Details visuals for Xpanse data

💡 Summary
Create Vulnerability Details visuals for Xpanse data
Motivation and context
Different vulnerability details will show different content. This is specific to Xpanse data.
Implementation notes
The vulnerability table has a field called "source". When it has the field "xpanse", it will show a different set of details in the UI.
Acceptance criteria

[ ] When clicking on details in the vulnerability table, it should show this updated page for an xpanse vulnerability.

In coordination with issue https://github.com/cisagov/XFD/issues/324 and branch 324-Xpanse-Data-Pull

repo: cisagov/XFD


text:
Modifications necessary for kerberization of guacamole

🗣 Description
This pull request makes several modifications necessary for the successful kerberization of guacamole.  These include:

Add some necessary-but-missing httpd modules
Ensure all necessary httpd modules are enabled
Save the HTTP service keytab to its own file.  httpd does not require access to the host keytab.
Add a restart for the httpd service so that it can take advantage of the keytab once it becomes available.

See also:

cisagov/guacamole-composition#9
cisagov/cool-assessment-terraform#58
cisagov/ansible-role-guacamole#6

💭 Motivation and Context
Guacamole must be kerberized in the COOL.
🧪 Testing
I have used these changes to successfully deploy a kerberized version of guacamole to env0 in our staging environment.
🚥 Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Oh! Red Hat Linux
Bending into the cold wind
You special flower

repo: cisagov/ansible-role-httpd


text:
api puppeteer and report

🗣 Description

Moved pupeteer and headless chrome to run with api.
Setup auth against client to use same auth credentials.
💭 Motivation and Context

🧪 Testing

📷 Screenshots (if appropriate)
🚥 Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@zenine07 Is this work replacing the need for the project in con-pca reports repository?

@mostafac0des Yes, this changes means the con-pca-reports repository is no longer needed. The changes function the same as the work being done in the reports repo, but removes one more moving piece.

repo: cisagov/con-pca-api


text:
Generate notification docs for new tickets with KEV CVEs

Task
In support of BOD 22-01 requirements 5 & 6: Generate notification docs for new tickets with KEV CVEs
Comments

Changes to be made here: https://github.com/cisagov/cyhy-core/blob/develop/cyhy/db/ticket_manager.py#L247-L249

References

Epic https://github.com/cisagov/cool-system-internal/issues/107
Story #29
Current Estimated LOE: Approximately 2 hours.

Closed by: cisagov/cyhy-core#63

authors: chelsgr felddy

repo: cisagov/cyhy-system


text:
ETL hangs forever querying ArangoDB

This is likely due to another bug in pyArango. https://github.com/ArangoDB-Community/pyArango/issues/160
Bug introduced after latest release on pypi, probably resolved by using release instead of upstream git. The changes desired have been merged, latest release was last September and merges occurred in March.

Related to #59

repo: cisco-ie/tdm


text:
Create transboundary-and-emerging-diseases.csl

To continue: https://github.com/citation-style-language/styles/pull/2194
Reviewed using mostly actual publications for journals, books, chapters and webpages. Plenty of changes needed, documentation of journal lacking anything useful.

(wrong repo)

repo: citation-style-language/journals


text:
Jessbumblebee/firstissue

Description
Add a description field to the CiviForm all programs page and adapt change "All Programs" to "Program Dashboard" as per the mocks. The intention is to make it easier for civi form admins to understand what this page is for.
Additional notes I skipped internationalization based on our conversation about this not being a priority for admins
I also did not add tests based on the instructions in the testing documentation which mentions that it is up to our discretion if smaller changes to views should have unit tests.
Release notes:
Rename the "All programs" page to "Program dashboard" and add a description to make it easier for Civi Form admins to understand the purpose of the page.
Checklist

[ x ] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ x ] Created tests which fail without the change (if possible)
[ x ] Extended the README / documentation, if necessary

Issue(s)
Fixes #3129

Few comments on PR

Change the name of PR from Jessbumblebee/firstissue to more meaningful message. You can do it from github UI.
For checklist don't add spaces between [ and x. It should be [x] to render as checkbox.
I think you change affects more screenshots. Basically all screenshots with program index should be updated. Also looks like there is some conflict with publish-modal. So you should merge main branch to your branch and rerun tests.

Codecov Report

Merging #3693 (c6b149d) into main (b1ec0ec) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #3693   +/-   ##
=========================================
  Coverage     80.53%   80.53%
  Complexity     2431     2431
=========================================
  Files           295      295
  Lines          9619     9619
  Branches        658      657    -1
=========================================
  Hits           7747     7747
  Misses         1619     1619
  Partials        253      253

Impacted Files
Coverage Δ

server/app/auth/oidc/admin/AdfsProfileAdapter.java
0.00% <0.00%> (ø)

.../app/controllers/admin/AdminProgramController.java
87.50% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi Mikita
Thanks for the comments. I fixed some formatting issues and cleaned  up my git branch which I had messed up a little.
I can't find any additional tests that fail. Let me know if there is anything additional that I should other than the standard browser tests to find some.
Quick question: is there a naming convention for PRs we use such as naming issues by the branch name? I initially went for a descriptive name in the sense of "it describes what the change does" and would like to understand your comment around better naming so that I can apply it next time.
Thanks
Jessica

repo: civiform/civiform


text:
🛑 NC is down

In 1d932e1, NC ($NC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NC is back up in 892d4d5.


text:
make categories searchable

Hey Stephane @StRigaud ,
this change is required to make the napari-assistant find the right functions. Under the hood, I read out all functions, that claim to be assistant-compatible like this list(cle.operations("in assistant").keys())
I had to modify this:
@plugin_function(category=[...

to this in many places:
@plugin_function(categories=[...

Does this require a change in a code-generator? If so, where?
Let me know what you think! (Or feel free to merge this).
Best,
Robert

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 80.74866% with 36 lines in your changes missing coverage. Please review.

Project coverage is 84.93%. Comparing base (5382c42) to head (e986221).

Files with missing lines
Patch %
Lines

pyclesperanto/_operations.py
10.34%
26 Missing :warning:

pyclesperanto/_categories.py
9.09%
10 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #232      +/-   ##
==========================================
- Coverage   86.52%   84.93%   -1.60%
==========================================
  Files          18       20       +2
  Lines        1603     1646      +43
==========================================
+ Hits         1387     1398      +11
- Misses        216      248      +32

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

Hey @haesleinhuepf
Yes, it does, but very minimalist has we just change the name when we write the file:
https://github.com/clEsperanto/gencle/blob/221c044ac6bec00726eafee80ef2f6e7852031ce/update_scripts/gencle/_genpy.py#L207

Also I did an operations function in functionalities.py but most likely not good compared to yours:
https://github.com/clEsperanto/pyclesperanto/blob/5382c42d8ba926ab4d18828532053de1f6c9ce12/pyclesperanto/_functionalities.py#L266-L269
dont hesitate to remove it

Just a note: the pre-commit is super annoying

The categories function is missing a doc :wink:

repo: clEsperanto/pyclesperanto


text:
Simultaneous access error

Player 3 version of the error screen in 1920x1080.

repo: clappr/clappr


text:
Some refactoring

better usage of let and const
blank lines between class methods and properties
do not switch indentation between tabs and spaces in same code file
consistent usage of semicolon at end of statement
replace super() with super(props) in constructor
initialize local component state in constructor
replace == with type safe ===
initialize direction with 0
avoid confusion with declaration of index in SortableElement's componentWillReceiveProps
some other minor code improvements

Hi Clauderic,
I hope that it is easier to diff and merge now, and that you can agree with the improvements.
Kind regards,
Ralf

Looks good, thanks!

authors: clauderic ralf-strehle

repo: clauderic/react-sortable-hoc


text:
🛑 livevault is down

In 9a0ccd7, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in d9b7304.

repo: claytonplong/backup-uptime


text:
Fix js component examples for release mode

We merged a broken version of the JS Components Example, this fixes it and cleans it up a bit.

+1

+10
JS Components example serves / functions as expected with no errors in DDC or dart2js

repo: cleandart/react-dart


text:
javax.mail/javax.mail-api 1.6.2

Type: Missing
Summary:
javax.mail/javax.mail-api 1.6.2
Details:
Note: there is mention of other licenses but believe they are discovered not the declared
Nuget is MS-PL
GitHub is MS-PL: https://raw.githubusercontent.com/haf/DotNetZip.Semverd/master/LICENSE
Resolution:
MS-PL
Affected definitions:

javax.mail-api 1.6.2

License file states CDDL-1.1 OR GPL-2.0-only WITH Classpath-exception-2.0.

authors: LandOfBliss capfei

repo: clearlydefined/curated-data


text:
307 temporary redirect issue .. caused by npm/@clerk/clerk-js@5/dist/clerk.browser.js

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs

[X] I have searched for existing issues: https://github.com/clerk/javascript/issues

[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction
https://www.ekksite.com
Publishable key
pk_test_YXdha2UtYWlyZWRhbGUtNzAuY2xlcmsuYWNjb3VudHMuZGV2JA
Description

  |
-- | --
GET |
scheme | https
host | awake-airedale-70.clerk.accounts.dev
filename | /npm/@clerk/clerk-js@5/dist/clerk.browser.js

Address | [2606:4700:8392:f8f1:aa39:50d:3478:6a32]:443
GET
scheme
https
host
awake-airedale-70.clerk.accounts.dev
filename
/npm/@clerk/clerk-js@5/dist/clerk.browser.js
Address
[2606:4700:8392:f8f1:aa39:50d:3478:6a32]:443
Status
307
VersionHTTP/3
Transferred73 kB (264.89 kB size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem
access-control-allow-origin
*
alt-svc
h3=":443"; ma=86400
cache-control
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
cf-ray
8ef829ba19aea788-DEL
content-length
0
date
Mon, 09 Dec 2024 21:42:05 GMT
location
https://awake-airedale-70.clerk.accounts.dev/npm/@clerk/clerk-js@5.40.1/dist/clerk.browser.js
priority
u=3,i=?0
server
cloudflare
server-timing
cfExtPri
set-cookie
__cf_bm=T_wBz9PRripnSPIETUhD76zIdHZ6zEckwLxYTr0LyLg-1733780525-1.0.1.1-OzMJBHkbn2WJJyLkoDNQc9_dNr9lUtlV7MgjlV0HzGmgM5dgQzMb9QTvZ1TJDtJykiI4mfg6IAGQbYJoTVObDQ; path=/; expires=Mon, 09-Dec-24 22:12:05 GMT; domain=.awake-airedale-70.clerk.accounts.dev; HttpOnly; Secure; SameSite=None
set-cookie
_cfuvid=nG1Do3QXv7DQ5fW9nGY5tMXvtTCeyDMsKp05tcmAQyo-1733780525150-0.0.1.1-604800000; path=/; domain=.awake-airedale-70.clerk.accounts.dev; HttpOnly; Secure; SameSite=None
vary
Accept-Encoding
Accept
/
Accept-Encoding
gzip, deflate, br, zstd
Accept-Language
en-US,en;q=0.5
Connection
keep-alive
Host
awake-airedale-70.clerk.accounts.dev
Origin
http://localhost:3000/
Referer
http://localhost:3000/
Sec-Fetch-Dest
script
Sec-Fetch-Mode
cors
Sec-Fetch-Site
cross-site
User-Agent
Mozilla/5.0 (M
Environment
npm
nextjs app router

Hello, thanks for the issue. Since you didn't leave any description of what your issue is or what you expect to happen I assume you mean the redirect. That is totally fine and working as expected.

authors: LekoArts vipulchaube

repo: clerk/javascript


text:
refactor(elements): Machine consolidation

Description

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Closing in favor of a separate branch


text:
Added computation of best perfectWidth with kmeans algo

This PR attempts to bring the computation of perfectWidth (= ideal image width depending on the viewport popularity) with k-means algo.
It seems working for a testing project, but I'm not 100% sure of this.
Ref #14

@welcoMattic now that I managed to upgrade all dependencies to current versions (apart from csv-parse: #391 ), could you try to update your PR?
There are many conflicts in package files, I'm not sure own to deal with this without breaking things. 😞
Thanks

Hi @nhoizey, the branch is rebased. TBH, I don't remember very well how this works, but I fixed the tests.

@welcoMattic thanks! 🙏
I'll try to check and test this week.

@welcoMattic I just checked, I get a result that looks fine! 👍
I will merge the PR, as it will be at least a good start, and we'll be able to fine tune after.
Thanks a lot, and sorry again for the way too long delay to merge this. 🙏

authors: nhoizey welcoMattic

repo: cleverage/daltons


text:
Literature review > PDF document extraction approaches

Create a Notion page summarising and categorising the PDF processing approaches.
e.g.
Image-based

LayoutLMv2 / LayoutXLM
faster-RCNN derived models

Text & markup-based

GROBID

We need to think about:

the inference overhead (cost) of each model, vs the accuracy benefit
how we train or improve them, including creating training data
which layout elements (headings, paragraphs) each method can extract (out-of-the-box vs modified)
adaptability to different document layouts, e.g. slides; case law

on Notion, ready for review (cc @chrisaballard)

repo: climatepolicyradar/navigator


text:
Terraform build errors deploying pre-built AMIs in AWS

Operating System Version: OSX Catalina 10.15.4
Provider (VirtualBox/VMWare): N/A (AWS AMIs)
Vagrant Version:  Vagrant 2.2.7
Packer Version: 1.5.5
Are you using stock boxes (downloaded) or were they built from scratch using Packer? Stock -- AMIs for build in AWS
Is the issue reproducible or intermittent?
reproducible for me from OSX against us-east-1

Initializing the backend...

Initializing provider plugins...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.aws: version = "~> 2.56"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Description of the issue:
AMIs will start to build, and i usually get errors similar to these where i eventually cannot connect over winRM and then get an i/o timeout, fail...
aws_key_pair.auth: Creating...
aws_vpc.default: Creating...
aws_key_pair.auth: Creation complete after 0s [id=id_logger]
aws_vpc.default: Creation complete after 1s [id=vpc-0fe145023c4a4199b]
aws_internet_gateway.default: Creating...
aws_subnet.default: Creating...
aws_security_group.windows: Creating...
aws_security_group.logger: Creating...
aws_internet_gateway.default: Creation complete after 1s [id=igw-0f3109dcaa7e800cd]
aws_route.internet_access: Creating...
aws_subnet.default: Creation complete after 1s [id=subnet-04996c16c775d30dc]
aws_route.internet_access: Creation complete after 1s [id=r-rtb-0b51198b87515a6751080289494]
aws_security_group.windows: Creation complete after 2s [id=sg-0865695008ac485ee]
aws_security_group.logger: Creation complete after 2s [id=sg-06493e2bab4855b4b]
aws_instance.dc: Creating...
aws_instance.wef: Creating...
aws_instance.win10: Creating...
aws_instance.logger: Creating...
aws_instance.wef: Still creating... [10s elapsed]
aws_instance.logger: Still creating... [10s elapsed]
aws_instance.dc: Still creating... [10s elapsed]
aws_instance.win10: Still creating... [10s elapsed]
aws_instance.logger: Still creating... [20s elapsed]
aws_instance.win10: Still creating... [20s elapsed]
aws_instance.dc: Still creating... [20s elapsed]
aws_instance.wef: Still creating... [20s elapsed]
aws_instance.dc: Provisioning with 'remote-exec'...
aws_instance.dc (remote-exec): Connecting to remote host via WinRM...
aws_instance.dc (remote-exec):   Host: 54.204.85.141
aws_instance.dc (remote-exec):   Port: 5985
aws_instance.dc (remote-exec):   User: vagrant
aws_instance.dc (remote-exec):   Password: true
aws_instance.dc (remote-exec):   HTTPS: false
aws_instance.dc (remote-exec):   Insecure: false
aws_instance.dc (remote-exec):   NTLM: false
aws_instance.dc (remote-exec):   CACert: false
aws_instance.win10: Provisioning with 'remote-exec'...
aws_instance.win10 (remote-exec): Connecting to remote host via WinRM...
aws_instance.win10 (remote-exec):   Host: 3.88.183.121
aws_instance.win10 (remote-exec):   Port: 5985
aws_instance.win10 (remote-exec):   User: vagrant
aws_instance.win10 (remote-exec):   Password: true
aws_instance.win10 (remote-exec):   HTTPS: false
aws_instance.win10 (remote-exec):   Insecure: false
aws_instance.win10 (remote-exec):   NTLM: false
aws_instance.win10 (remote-exec):   CACert: false
aws_instance.wef: Provisioning with 'remote-exec'...
aws_instance.wef (remote-exec): Connecting to remote host via WinRM...
aws_instance.wef (remote-exec):   Host: 3.84.154.43
aws_instance.wef (remote-exec):   Port: 5985
aws_instance.wef (remote-exec):   User: vagrant
aws_instance.wef (remote-exec):   Password: true
aws_instance.wef (remote-exec):   HTTPS: false
aws_instance.wef (remote-exec):   Insecure: false
aws_instance.wef (remote-exec):   NTLM: false
aws_instance.wef (remote-exec):   CACert: false
aws_instance.win10: Still creating... [30s elapsed]
aws_instance.wef: Still creating... [30s elapsed]
aws_instance.logger: Still creating... [30s elapsed]
aws_instance.dc: Still creating... [30s elapsed]
aws_instance.logger: Provisioning with 'remote-exec'...
aws_instance.logger (remote-exec): Connecting to remote host via SSH...
aws_instance.logger (remote-exec):   Host: 52.91.231.176
aws_instance.logger (remote-exec):   User: ubuntu
aws_instance.logger (remote-exec):   Password: false
aws_instance.logger (remote-exec):   Private key: true
aws_instance.logger (remote-exec):   Certificate: false
aws_instance.logger (remote-exec):   SSH Agent: true
aws_instance.logger (remote-exec):   Checking Host Key: false
aws_instance.logger: Still creating... [40s elapsed]
aws_instance.dc: Still creating... [40s elapsed]
aws_instance.win10: Still creating... [40s elapsed]
aws_instance.wef: Still creating... [40s elapsed]
aws_instance.logger (remote-exec): Connecting to remote host via SSH...
aws_instance.logger (remote-exec):   Host: 52.91.231.176
aws_instance.logger (remote-exec):   User: ubuntu
aws_instance.logger (remote-exec):   Password: false
aws_instance.logger (remote-exec):   Private key: true
aws_instance.logger (remote-exec):   Certificate: false
aws_instance.logger (remote-exec):   SSH Agent: true
aws_instance.logger (remote-exec):   Checking Host Key: false
aws_instance.logger (remote-exec): Connecting to remote host via SSH...
aws_instance.logger (remote-exec):   Host: 52.91.231.176
aws_instance.logger (remote-exec):   User: ubuntu
aws_instance.logger (remote-exec):   Password: false
aws_instance.logger (remote-exec):   Private key: true
aws_instance.logger (remote-exec):   Certificate: false
aws_instance.logger (remote-exec):   SSH Agent: true
aws_instance.logger (remote-exec):   Checking Host Key: false

aws_instance.win10: Still creating... [8m31s elapsed]
aws_instance.win10: Still creating... [8m41s elapsed]

Error: error executing "/tmp/terraform_1833763437.sh": wait: remote command exited without exit status or exit signal

Error: Failed to upload script: Error removing temporary file $env:TEMP\winrmcp-028f5e3b-86f8-4982-50f6-2f359594076d.tmp: unknown error Post http://3.84.154.43:5985/wsman: dial tcp 3.84.154.43:5985: i/o timeout

Error: error executing "C:/Temp/terraform_1864348089.cmd": unknown error Post http://3.88.183.121:5985/wsman: read tcp 10.0.0.8:57247->3.88.183.121:5985: read: operation timed out

this is especially strange to me since during the bulid connections over winRM work early on, but eventually get this far and then error --
in EC2 all the instances are up, the security groups are applied correctly (so it seems), yet if i try to nmap any of hte allowed ports i always get back "filtered".
Link to Gist Containing Build Logs:
Full build logs here https://gist.github.com/randaal/63f12ca24f9f0b2747346ed90aba1644

Just refreshed the Terraform AMIs! Mind giving this another shot and letting me know how it goes?

Still looks like similar errors... timeouts hitting the WinRM and SSH ports on the AMIs -- i've tried building on us-east and us-west --- tried also building from a digital ocean droplet to rule out any issues that may come from my own network or workspace, and still the same...
is there any other way i can troubleshoot?
--SNIP--
aws_instance.wef: Still creating... [3m50s elapsed]
aws_instance.win10: Still creating... [3m50s elapsed]
aws_instance.dc: Still creating... [4m0s elapsed]
aws_instance.wef: Still creating... [4m0s elapsed]
aws_instance.win10: Still creating... [4m0s elapsed]
aws_instance.win10: Still creating... [4m10s elapsed]
aws_instance.dc: Still creating... [4m10s elapsed]
aws_instance.wef: Still creating... [4m10s elapsed]
aws_instance.win10: Still creating... [4m20s elapsed]
aws_instance.dc: Still creating... [4m20s elapsed]
aws_instance.wef: Still creating... [4m20s elapsed]
aws_instance.dc (remote-exec): Connecting to remote host via WinRM...
aws_instance.dc (remote-exec):   Host: 52.207.241.81
aws_instance.dc (remote-exec):   Port: 5985
aws_instance.dc (remote-exec):   User: vagrant
aws_instance.dc (remote-exec):   Password: true
aws_instance.dc (remote-exec):   HTTPS: false
aws_instance.dc (remote-exec):   Insecure: false
aws_instance.dc (remote-exec):   NTLM: false
aws_instance.dc (remote-exec):   CACert: false
aws_instance.dc: Still creating... [4m30s elapsed]
aws_instance.win10: Still creating... [4m30s elapsed]
aws_instance.wef: Still creating... [4m30s elapsed]
aws_instance.win10 (remote-exec): Connecting to remote host via WinRM...
aws_instance.win10 (remote-exec):   Host: 54.172.126.139
aws_instance.win10 (remote-exec):   Port: 5985
aws_instance.win10 (remote-exec):   User: vagrant
aws_instance.win10 (remote-exec):   Password: true
aws_instance.win10 (remote-exec):   HTTPS: false
aws_instance.win10 (remote-exec):   Insecure: false
aws_instance.win10 (remote-exec):   NTLM: false
aws_instance.win10 (remote-exec):   CACert: false
aws_instance.wef: Still creating... [4m40s elapsed]
aws_instance.dc: Still creating... [4m40s elapsed]
aws_instance.win10: Still creating... [4m40s elapsed]
aws_instance.wef: Still creating... [4m50s elapsed]
aws_instance.dc: Still creating... [4m50s elapsed]
aws_instance.win10: Still creating... [4m50s elapsed]
aws_instance.dc: Still creating... [5m0s elapsed]
aws_instance.wef: Still creating... [5m0s elapsed]
aws_instance.win10: Still creating... [5m0s elapsed]
aws_instance.wef: Still creating... [5m10s elapsed]
aws_instance.dc: Still creating... [5m10s elapsed]
aws_instance.win10: Still creating... [5m10s elapsed]
aws_instance.dc (remote-exec): Connecting to remote host via WinRM...
aws_instance.dc (remote-exec):   Host: 52.207.241.81
aws_instance.dc (remote-exec):   Port: 5985
aws_instance.dc (remote-exec):   User: vagrant
aws_instance.dc (remote-exec):   Password: true
aws_instance.dc (remote-exec):   HTTPS: false
aws_instance.dc (remote-exec):   Insecure: false
aws_instance.dc (remote-exec):   NTLM: false
aws_instance.dc (remote-exec):   CACert: false
aws_instance.win10: Still creating... [5m20s elapsed]
aws_instance.dc: Still creating... [5m20s elapsed]
aws_instance.wef: Still creating... [5m20s elapsed]
aws_instance.win10 (remote-exec): Connecting to remote host via WinRM...
aws_instance.win10 (remote-exec):   Host: 54.172.126.139
aws_instance.win10 (remote-exec):   Port: 5985
aws_instance.win10 (remote-exec):   User: vagrant
aws_instance.win10 (remote-exec):   Password: true
aws_instance.win10 (remote-exec):   HTTPS: false
aws_instance.win10 (remote-exec):   Insecure: false
aws_instance.win10 (remote-exec):   NTLM: false
aws_instance.win10 (remote-exec):   CACert: false
aws_instance.dc: Still creating... [5m30s elapsed]
aws_instance.wef: Still creating... [5m30s elapsed]
aws_instance.win10: Still creating... [5m30s elapsed]

aws_instance.wef: Still creating... [5m40s elapsed]
aws_instance.win10: Still creating... [5m40s elapsed]

aws_instance.wef: Still creating... [5m50s elapsed]
aws_instance.wef: Still creating... [6m0s elapsed]
aws_instance.wef: Still creating... [6m10s elapsed]
aws_instance.wef: Still creating... [6m20s elapsed]
aws_instance.wef: Still creating... [6m30s elapsed]
aws_instance.wef: Still creating... [6m40s elapsed]
aws_instance.wef: Still creating... [6m50s elapsed]
aws_instance.wef: Still creating... [7m0s elapsed]
aws_instance.wef: Still creating... [7m10s elapsed]
aws_instance.wef: Still creating... [7m20s elapsed]
aws_instance.wef: Still creating... [7m30s elapsed]
aws_instance.wef: Still creating... [7m40s elapsed]
aws_instance.wef: Still creating... [7m50s elapsed]

Error: timeout - last error: unknown error Post http://52.207.241.81:5985/wsman: dial tcp 52.207.241.81:5985: i/o timeout

Error: timeout - last error: unknown error Post http://54.172.126.139:5985/wsman: dial tcp 54.172.126.139:5985: i/o timeout

Error: error executing "C:/Temp/terraform_209971115.cmd": unknown error Post http://54.227.49.213:5985/wsman: read tcp 10.0.0.8:52983->54.227.49.213:5985: read: operation timed out

Error: error executing "/tmp/terraform_1940723860.sh": wait: remote command exited without exit status or exit signal

Hi @randaal ! Did you define a terraform.tfvars file and add a line for the ip_whitelist? It should look like this:
region = "us-west-1"
shared_credentials_file = "/Users/user.aws/credentials"
public_key_name = "id_logger"
public_key_path = "/Users/user/.ssh/id_logger.pub"
private_key_path = "/Users/user/.ssh/id_logger"
ip_whitelist = ["<your_ip_here>/32"]

That would explain why the WinRM connections are being blocked.

yep, heres mine -- like i said, its strange to me that it works early on in the build and then cant connect towards the end --
profile = "terraform"
shared_credentials_file = "/Users/<HIDDEN>/.aws/credentials"
public_key_name = "id_logger"
public_key_path = "/Users/<HIDDEN>/.ssh/id_logger.pub"
private_key_path = "/Users/<HIDDEN>/.ssh/id_logger"
ip_whitelist = ["<HIDDEN>"]

@randaal - I'm at a total loss here! What makes you think it's working early on in the build, though? It looks like the connection is never successfully made from what I can tell.

Hey @randaal - just checking back in here

@clong  thanks for following up -- Not sure root cause just yet, but 99% confident this is something with my AWS account and possibly IAM roles... tried with a fresh set of keys and everything works fine.
Do i need any specific roles or privileges for the build tasks? i'm comfortable closing this out since seems like the error is not reproducible for now :(

Nope, should be pretty standard in terms of roles!

Not trying to open a closed issue but I ran into the same thing described above.
The fix for me was to set ip_whitelist = ["<HIDDEN-1>"] to the source IP I was running terraform from and the source IP of the host I intended to connect to detection lab from. They weren't the same, as I was running terraform from an instance on AWS and wanting to connect to the lab from my home public IP.
Changed config to:
ip_whitelist = ["<AWS-VM>","<Home-Public-IP>"]
After that, it worked perfectly.

authors: clong randaal swarleysez

repo: clong/DetectionLab


text:
Add deployKubernetesCluster() function to the test-client

Add deployKubernetesCluster() function to show an usecase easily
Update existing scripts
Improve log messages

Wrong branch

repo: cloud-barista/cb-larva


text:
Add SECURITY.md

Changes proposed in this pull request:

added Security.md

Things to check

Ensure everything looks correct

Security considerations
Improves security by adding Security.md

Superseded by #75

authors: markdboyd wz-gsa


text:
Allow users to select features they can see

In profile dialog top right add switches to select azure, ibm cloud, aws, compliance and sol builder

@mjperrins please approve design:

2 main toggles:

Compliance features disabled by default: if disabled will hide Compliance section and impacted controls in service details in all views when applicable
Solution Builder features enabled by default: if disabled will hide Solution Builder section

3 secondary toggles you can only see if Solution Builder features is enabled

IBM Cloud content enabled by default: if disabled will hide IBM Cloud specific BOMs and solutions in solution builder
Azure content enabled by default: if disabled will hide Azure specific BOMs and solutions in solution builder
AWS content enabled by default: if disabled will hide AWS Cloud specific BOMs and solutions in solution builder
All of those will be configurable by user and stored in mongo user model as config, here’s a view of the UI:

repo: cloud-native-toolkit/ascent-ui


text:
CDTReplicatorFactory initWithDatastoreManager:nil returns a non-nil object

If you call:
CDTReplicatorFactory *repFactory = [[CDTReplicatorFactory alloc] initWithDatastoreManager:nil];

The result is a non-nil object that can then be used to create a CDTReplicator that is non-nil but is essentially useless when you try to use it.

I've opened an ticket in our internal issue tracker, we will update this ticket as progress is made

authors: jimix rhyshort

repo: cloudant/CDTDatastore


text:
Fix AES key creation for Android versions less then KitKat (API 19)

Encrypt/Decrypt methods now have a create the SecretKeySpec for the AES key.  This fixes issues with encryption of the PBK on versions of Android less than KitKat (API 19)
reviewer @mikerhodes
reviewer @tomblench

Can you see any of the changes here https://developer.android.com/sdk/api_diff/19/changes.html that might have caused this? (I think 19 is kitkat).

Seems to follow http://docs.oracle.com/javase/7/docs/technotes/guides/security/crypto/CryptoSpec.html#SimpleEncrEx, so I think we're good here. Seems like any specific references are hard to find, so I guess I will need to retract my previous request.
+1.

+1
I added the StackOverflow solution URL to help remind our future selves why we did this.

Merging.

authors: kholdaway mikerhodes tomblench

repo: cloudant/sync-android


text:
🛑 myrepublic.co.id is down

In 6ae372e, myrepublic.co.id (https://myrepublic.co.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: myrepublic.co.id is back up in 79058aa.

repo: cloudbip/upptime


text:
🛑 hsp.net.id is down

In 55be8e7, hsp.net.id (https://hsp.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hsp.net.id is back up in 0186323 after 8 minutes.


text:
🛑 id.hosting24.com is down

In 080e1ed, id.hosting24.com (https://id.hosting24.com) was down:

HTTP code: 403
Response time: 147 ms

Resolved: id.hosting24.com is back up in 708baa5.


text:
🛑 lintas.net.id is down

In cc7e607, lintas.net.id (https://lintas.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lintas.net.id is back up in 26bf5f9 after 8 minutes.


text:
🛑 daeliweb.com is down

In 8f8cded, daeliweb.com (https://daeliweb.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: daeliweb.com is back up in 2401547.


text:
🛑 hoster.co.id is down

In 616fa53, hoster.co.id (https://hoster.co.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hoster.co.id is back up in 8da826e.


text:
🛑 niagahoster.co.id is down

In 140c351, niagahoster.co.id (https://niagahoster.co.id) was down:

HTTP code: 403
Response time: 105 ms

Resolved: niagahoster.co.id is back up in 2412019.


text:
🛑 cbn.id is down

In 58bbf9d, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 1e9658c.


text:
🛑 cbn.id is down

In d33197f, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 7d20d5f.


text:
🛑 ardhosting.com is down

In 5b53d43, ardhosting.com (https://ardhosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ardhosting.com is back up in 50e76af.


text:
Change lambdas folder

Hi, @hupe1980.
It is my first pull request, so any questions and / or questions you can ask.
Thank you

closes #6

closes #5

repo: cloudcomponents/cdk-components


text:
[importer] header reformatting for local file upload

-Automatically replaces local file upload table headers white spaces with underscores and changes all letters to lowercase
-uses a list comprehension to .replace(" ", "").replace('.', '').lower(), the first row of an uploaded file, this is stored separately from the raw file so if header is unchecked it reverts to the original first line of doc and uses either default, field_1 headers, or user inputed headers.
-Added test case with '.' and ' ' it uses same mechanism as local file upload to read test csv file and compare if headers are correct. I could not figure out how to cast the json response into a dict to assert equal just columns names.
-Checking and unchecking has header checkbox in the importer, works as intended. With the has header checked the first row spaces and '.' are replaced with ''. When unchecked auto generated header names appear and the previous headers become the first row without spaces and '.' replaced with ''

Also if you want to clean-up the list of commit and rebase on latest hue, if upstream hue is origin:
git fetch origin
git rebase origin/master
git push michael-brine HEAD:header_reformating

I think i am just going save the test file as ascii and it should work with just open(), for both versions.

authors: michael-brine romainr

repo: cloudera/hue


text:
Prototype http negation for cloudevents versions accepted.

If a producer wants to send to a consumer, could the producer hit the consumer with OPTIONS request to understand what it can send?

There is nothing in the spec for this. Close for now.

repo: cloudevents/sdk-go


text:
AMQP does't work

Hi! I try to use amqp sample, and when I run, I got an compilation error:
github.com/cloudevents/sdk-go/protocol/amqp/v2
..\github.com\cloudevents\sdk-go\protocol\amqp\v2\message.go:125:23: not enough arguments in call to m.AMQP.Reject
have (*amqp.Error)
want (context.Context, *amqp.Error)
..\github.com\cloudevents\sdk-go\protocol\amqp\v2\message.go:130:22: not enough arguments in call to m.AMQP.Accept
have ()
want (context.Context)
When I open message.go - I see an error in the file. This file read-only and func Finish contain errors. It's normal?

In the file message.go I added context.TODO() in Finish function:
func (m *Message) Finish(err error) error {
if err != nil {
return m.AMQP.Reject(context.TODO(),&amqp.Error{
Condition:   condition,
Description: err.Error(),
})
}
return m.AMQP.Accept(context.TODO())
}
I'm not sure, that it correct solution, but error is gone.

It seems the API on the AMQP lib have changed. https://github.com/Azure/go-amqp/releases/tag/v0.13.6


text:
New filter to allow plugins to hook for purging.

New filter cloudflare_purge_actions added so plugins like page builders can add their publish actions and have the cache purged.

Thanks, but merged #212 instead.

authors: Pross patryk

repo: cloudflare/Cloudflare-WordPress


text:
can not access my account

Example URL(s)
www.warehousecables.com
Actual Behavior
Site keeps becoming unreachable. Error 523
Expected Behavior
The expected behavior is for the site to be available
Additional information
Can not access Cloudflare dashboard because I do not know what email address was used. We have tried entering our domain name to receive a reset  link but we do not receive any notifications. No one answers the phone at CloudFlare support. Very frustrating

Howdy @warehousecables, unfortunately this is a documentation repo.
You might want to check out the troubleshooting docs around that issue, but otherwise your best avenue would be reaching out in the Cloudflare Community.

repo: cloudflare/cloudflare-docs


text:
Highlight the differences between all the ways we can develop Workers

Which Cloudflare product(s) does this pertain to?
Workers
Subject Matter
All the ways to develop Workers
Content Location
https://developers.cloudflare.com/workers/
Additional information

Production Workers, Quick Edit, https://cloudflareworkers.com/, Remote Dev, Local Dev, Miniflare Raw, etc.?

Would be cool as a doc too. I've noticed some differences, but probably not everything.

from @helloimalastair

Hey there - I'm going to close this issue out in lieu of an effort to create specific, internal tutorial tickets that capture what we need for Workers. Feel free to open a PR if you have content! FYI @kristianfreeman and @rickyrobinett.


text:
Update aside styling and remove titles from workers-ai asides

Summary
• Update the styling of the asides to make them smaller
• Start the process of removing titles from asides (starting with /workers-aI)
Screenshots (optional)

Documentation checklist

duplicate


text:
[🐛 Bug]: Should not increase bundle size when build project after upgrade Sentry version to V8

next-on-pages environment related information
@cloudflare/next-on-pages: 1.13.2
Description
We want to apply the feature thirdPartyErrorFilterIntegration for Sentry, but this feature requires version 8.10.0 or above (Sentry documentation).
As a result, we updated @sentry/nextjs from 7.119.0 to 8.20.0. However, when we redeployed the project on Cloudflare with the new version, we encountered the following error:
Generated Pages Functions bundle size (83882560) is over the limit of 25.0 MiB.
This issue is impacting our business significantly: we are being overwhelmed with third-party errors, making it difficult to filter and identify our own errors in Sentry.
Our desired resolution is to have Sentry V8 without increasing the bundle size.
Ideally, we want to maintain a smaller bundle size to ensure optimal performance for the functions.
Reproduction
No response
Pages Deployment Method
None
Pages Deployment ID
No response
Additional Information
No response
Would you like to help?

[X] Would you like to help fixing this bug?

Believe this will also have been fixed by https://github.com/cloudflare/next-on-pages/pull/886. Should be available in the latest beta release for next-on-pages.

Thanks @james-elicx ,
Can you tell me the time to release new version for @cloudflare/next-on-pages ?
We want to use it as soon as possible.

Thanks @james-elicx , Can you tell me the time new version for @cloudflare/next-on-pages released? We want to use it as soon as possible.

The release is out now @danhnguyen-agilityio

Bizarrely, something appears to be wrong with npm and it is not showing the published version

npm is finally showing our releases. Should be good for you to try out now with the latest release.

authors: danhnguyen-agilityio james-elicx

repo: cloudflare/next-on-pages


text:
examples: respond to non-GET requests with 405

The http3-server example doesn't respond at all to non-GET requests. This is not helpful to clients as it could be confused with some other (transport) error.
Since the example is simple, we just default to responding to these kinds of requests with a 405 Method Not Allowed.

Please rebase on latest master, this is pretty old.

d'oh. So when I rebase, this happens
cargo build --examples
error: failed to select a version for `winapi`.
    ... required by package `quiche v0.1.0-alpha4 (/home/lucas/workspace/quiche2)`
versions that meet the requirements `= 0.2.8` are: 0.2.8

the package `quiche` depends on `winapi`, with features: `wincrypt` but `winapi` does not have these features.

failed to select a version for `winapi` which could resolve this conflict

Yeah, it's always the same problem, removing Cargo.lock should "fix" it.

Oh, I just realized that for requests with a body we also need to shutdown the stream, otherwise poll() would still keep reporting Data events. Can be done in a separate PR though.

authors: LPardue ghedo

repo: cloudflare/quiche


text:
Do not redeclare TS lib

After diving into worker-types with #1383, I realized that many of the workers-types are just modified from TS lib. Is there a reason for this? Why not extend pre-existing classes where needed?
For example, instead of re-declaring Body:
worker-types currently:
export declare abstract class Body {
  readonly body: ReadableStream | null;
  readonly bodyUsed: boolean;
  arrayBuffer(): Promise<ArrayBuffer>;
  text(): Promise<string>;
  json<T>(): Promise<T>;
  formData(): Promise<FormData>;
  blob(): Promise<Blob>;
}

lib.dom.d.ts (comments removed):
interface Body {
    readonly body: ReadableStream<Uint8Array> | null;
    readonly bodyUsed: boolean;
    arrayBuffer(): Promise<ArrayBuffer>;
    blob(): Promise<Blob>;
    formData(): Promise<FormData>;
    json(): Promise<any>;
    text(): Promise<string>;
}

Updated:
worker-types/alias.d.ts
export { Body };

worker-types/index.d.ts
import type { Body as FetchBody } from './alias';

export declare abstract class Body extends FetchBody {
  json<T>(): Promise<T>;
}

This would add a ton of reusability and compatibility to the types since the only code is changes from built-in classes. The following classes can use this approach:

DOMException
WorkerGlobalScope
WorkerGlobalScopeEventMap
Console
console
BufferSource
WebAssembly
ServiceWorkerGlobalScope
addEventListener
removeEventListener
dispatchEvent
btoa
atob
setTimeout
clearTimeout
setInterval
queueMicrotask
structuredClone
fetch
...

I won't bother to list the 250+ symbols which only redeclare ones already present in TS lib, with little to no change.

This is intentional. The types for @cloudflare/workers-types are generated directly from the workers runtime implementation, and so accurately match runtime behaviour. In most cases we're pretty close to spec-compliant with web standards, and so are similar to lib.dom.d.ts, but we recommend using @cloudflare/workers-types exclusively, and not typing your codebase against lib.dom.d.ts.

authors: dr-vortex penalosa

repo: cloudflare/workerd


text:
Fix websocket auto-response message races

This PR fixes racing issues between regular websocket messages and auto-responses.
The initial version of this PR held a jsg::Ref<> for a long time, which could cause occasional segfaults. This new version fixes that segfault.

Thank you, @bcaimano and @MellowYarker for the very fast review!

Thanks for the cleanup!

authors: MellowYarker jqmmes


text:
Always npm install

Closes #428 by removing logic to skip npm install step if node_modules is already present. npm install is pretty good about not redundantly downloading packages. tested locally on a mac.

closing in favor of needing more design for how we can let users "customize builds"

authors: ashleygwilliams ashleymichal

repo: cloudflare/wrangler


text:
remote worker: Error: ENOENT: no such file or directory

This error occasionally happens, not sure why.

I wonder if it is related to this fix: https://github.com/cloudflare/wrangler2/pull/258/files#diff-d79823fe1e90cdc27158bbeaab5f58954e81375f84f4403ca124318c7bccd54fR156-R158
Note that here I had to resolve against the "destination" directory. The current working directory and the wrangler.toml directory did not work.

Can reproduce this by using npx wrangler publish from inside example-worker-app in our codebase.

I think this should now be fixed in @alpha, am closing. Please reopen if you see it again!

Still an issue, happens sporadically with dev.
remote worker: [Error: ENOENT: no such file or directory, open '../../../../../var/folders/kv/f6jw8r5d26q9_r6vjvlz87q00000gn/T/tmp-58328-oNNeQQ2mz8WM/chat.js'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '../../../../../var/folders/kv/f6jw8r5d26q9_r6vjvlz87q00000gn/T/tmp-58328-oNNeQQ2mz8WM/chat.js'
}

Haven't seen this in a while, probably got fixed with our bundle refactor. Closing for now.

authors: Electroid petebacondarwin threepointone


text:
fix(button-modal): fix alert theme header style

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[x] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[x] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[ ] Tested with console(if usages are changed)

Description
SSIA

In alert theme, Header layout with lottie is changed.
Previously, header text and lottie was different block. But, now looks like same block in case of header with 2 or more lines.

Before

After

:tada: This PR is included in version 1.1.0-beta.504 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: admin-cloudforet piggggggggy

repo: cloudforet-io/mirinae


text:
fix(lottie): delete PLottie component

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[ ] Feature improvement

[x] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[ ] Tested with console(if usages are changed)

Description

delete lottie component

:tada: This PR is included in version 2.0.0-beta.35 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
Docker swarm is having issue related to TLS

Deployed docker swarm using " docker-boshrelease/manifests/swarm/docker-swarm.yml" file.
All the instances created by BOSH director shows status as "running" state but I am getting following error messages under swarm node
time="2017-07-05T13:28:14Z" level=info msg="Listening for HTTP" addr="0.0.0.0:2375" proto=tcp
time="2017-07-05T13:28:14Z" level=info msg="Listening for HTTP" addr="/var/vcap/sys/run/swarm-manager/swarm-manager.sock" proto=unix
time="2017-07-05T13:28:14Z" level=error msg="Get https://b175f288-5ac8-4d17-86f1-bc25f3c84d02.docker.default.docker-swarm.bosh:4243/v1.15/info: x509: certificate is valid for docker, not b175f288-5ac8-4d17-86f1-bc25f3c84d02.docker.default.docker-swarm.bosh"
time="2017-07-05T13:28:14Z" level=error msg="Get https://f65d0cad-3918-41b0-8794-0525f932c2e2.docker.default.docker-swarm.bosh:4243/v1.15/info: x509: certificate is valid for docker, not f65d0cad-3918-41b0-8794-0525f932c2e2.docker.default.docker-swarm.bosh"
time="2017-07-05T13:28:14Z" level=error msg="Get https://abec7b28-8f4b-43f7-a9d8-d29faa1f91d1.docker.default.docker-swarm.bosh:4243/v1.15/info: x509: certificate is valid for docker, not abec7b28-8f4b-43f7-a9d8-d29faa1f91d1.docker.default.docker-swarm.bosh"
2017/07/05 13:28:19 http: TLS handshake error from @: EOF
2017/07/05 13:28:29 http: TLS handshake error from @: EOF
2017/07/05 13:28:39 http: TLS handshake error from @: EOF
2017/07/05 13:28:49 http: TLS handshake error from @: EOF
2017/07/05 13:28:59 http: TLS handshake error from @: EOF
2017/07/05 13:29:09 http: TLS handshake error from @: EOF
Docker node gives following error messages
time="2017-07-05T13:27:55.011151475Z" level=info msg="libcontainerd: new containerd process, pid: 11884"
time="2017-07-05T13:27:56.126917370Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2017-07-05T13:27:56.127396702Z" level=warning msg="Your kernel does not support cgroup rt period"
time="2017-07-05T13:27:56.127422455Z" level=warning msg="Your kernel does not support cgroup rt runtime"
time="2017-07-05T13:27:56.127918501Z" level=info msg="Loading containers: start."
time="2017-07-05T13:27:56.349686484Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
time="2017-07-05T13:27:56.416849340Z" level=info msg="Loading containers: done."
time="2017-07-05T13:27:56.445588207Z" level=info msg="Daemon has completed initialization"
time="2017-07-05T13:27:56.445635146Z" level=info msg="Docker daemon" commit=092cba3 graphdriver=aufs version=1.13.1
time="2017-07-05T13:27:56.455364220Z" level=info msg="API listen on /var/vcap/sys/run/docker/docker.sock"
time="2017-07-05T13:27:56.455505393Z" level=info msg="API listen on 0.0.0.0:4243"
2017-07-05 13:28:13.995048 I | http: TLS handshake error from 192.168.1.60:36948: remote error: tls: bad certificate
Kindly let me know in case more details are required for the same.
Thanks ~ Prashant

Do you think issue is due to "subject alternative name"?


text:
Contacting for merging with my work

Hello @davidehringer,
I couldn't find your mail address so I'm contacting you with this issue.
I did the same work as your work or close to, you can see it here: https://github.com/Orange-OpenSource/cloudfoundry-s3-service-connector.
What I did:

Could find any s3 storage from service (no matter if it's p-riakcs or aws s3 or other things)
Auto-provisioning a jcloud ContextBuilder to use the s3 directly

Can I put my work here? Like this we could work together on it.

Hi @ArthurHlt ,
That sounds great.  Feel free to submit the necessary pull requests.
I'm going to get issue #2 started as well.

Sorry I didn't see your reply, well in fact it will be more a replacement than a merge because I didn't based my work on yours. I'm able to push my work directly in the rep, if you are interested take a look on what I did

authors: ArthurHlt davidehringer


text:
Update shrinkwrap files

Signed-off-by: Nikolay Maslarski nikolay.maslarski@sap.com

Coverage remained the same at 91.741% when pulling 8ef9c0d3962b43b6a6ae6cf40c17ff6cf3a19844 on SAP:shrinkwrap_update into db46a3563c74971d90ad2d82619e04fac9c5ee10 on cloudfoundry-incubator:master.

authors: PlamenDoychev coveralls

repo: cloudfoundry-incubator/cf-abacus-broker


text:
Users list is empty after cancel

On 2nd step of manage users, click cancel and you are taken back to en empty list.

Closing - cannot reproduce.

authors: KlapTrap nwmac

repo: cloudfoundry-incubator/stratos


text:
"*.the_deployment_name.bosh" should not match all VMs in all deployments

Hello, I'd like to use bosh-dns to resolve a hostname to IPs of all VMs within a deployment, but the following aliases matches to all VMs in all deployments.
cat /var/vcap/jobs/my-aliases/dns/aliases.json
{"a.my.local":["*.service1-2e1a321358b8d3507a45.bosh"]}
nslookup a.my.local
Server:		169.254.0.2
Address:	169.254.0.2#53
Name:	a.my.local
Address: 30.0.0.12
Name:	a.my.local
Address: 30.0.0.14
cat /var/vcap/instance/dns/records.json
{"records":[["30.0.0.12","c6bc7173-3143-424c-9e6f-a404f624fbcc.service1.deployment-network.service1-2e1a321358b8d3507a45.bosh"],["30.0.0.14","5708c0e8-fa04-4290-b798-93d18a080891.harbor-app.deployment-network.service2-e3831e72d40367bb3794.bosh"]],"version":32,"record_keys":["id","num_id","instance_group","group_ids","az","az_id","network","network_id","deployment","ip","domain","agent_id","instance_index"],"record_infos":[["c6bc7173-3143-424c-9e6f-a404f624fbcc","25","service1",["15"],"az-1","1","deployment-network","1","service1-2e1a321358b8d3507a45","30.0.0.12","bosh","2ac18ad8-7d1f-4fdc-8bef-89e320133333",0],["5708c0e8-fa04-4290-b798-93d18a080891","35","myapp",["19"],"az-1","1","deployment-network","1","service2-e3831e72d40367bb3794","30.0.0.14","bosh","d5833ea9-99e9-4c29-83b2-dde2fc86
I can use (( ..service1.deployment_name )) to get the deployment name in Tile yaml, but not sure who to get the deployment network name. Is it (( ..service1.deployment_network )) ? If so, I can specify a more specific domain like "*.job1.(( ..service1.deployment_network )).(( ..service1.deployment_name )).bosh".

I can use '.instance_group_name.network_name.deployment_name.bosh' to match all IPs of VMs in that group. Here I want to report the bug that ".depoyment-1_name.bosh" matches all VMs in all deployments, which is not expected.

that doesnt really describe why you need this feature. any more info?

@cppforlife I don't need this feature. Actually this is a bug : ".depoyment-1_name.bosh" matches all VMs in all deployments, which is not expected".

@jessehu oh im sorry, it appears i misread. will take a look on tue.

@jessehu You're instinct is correct to provide more information to the filter. The problem you're facing is the distinction bosh-dns makes between a long-query and short-query.
Short queries take the rough form: {query}.{group-query}.{domain}, for example: q-s0.q-g7.bosh.. When the group query does not match the correct format, we omit it from the filtering chain effectively making it q-s0.*.bosh. In this case, the deployment name is not a valid "group query". You can test this theory out by substituting the group-query with random letters: dig q-s0.askhfjahfajshfja.bosh
Gonna close this out as it stands.

authors: aashah cppforlife jessehu

repo: cloudfoundry/bosh-dns-release


text:
bosh cck restarts jobs in a (random?) order instead of the order of the deployment spec

Just when you might be most stressed - your entire production system has been deleted by someone with dashboard access; or you're preparing a screencast for PlatformCF - bosh cck brings back VMs one at a time.
Applying problem resolutions
  missing_vm 21: Recreate VM using last known apply spec (00:01:32)
  missing_vm 27: Recreate VM using last known apply spec (00:01:32)
  missing_vm 24: Recreate VM using last known apply spec (00:01:52)
  missing_vm 26: Recreate VM using last known apply spec (00:02:00)
  missing_vm 20: Recreate VM using last known apply spec (00:01:30)
  missing_vm 23: Recreate VM using last known apply spec (00:01:39)
missing_vm 18: Recreate VM using... |oooooooooooooo          | 6/10 00:10:16  ETA: 00:06:31

I think it wants to torture me. It loves me. But the love hurts.

Closing. We are slowly converging to having bosh deploy --fix having ability to recover deployments in a irregular state. Ultimately we may even turn bosh cck into a command that just reports problems instead of allowing to interactively fix them.

authors: cppforlife drnic

repo: cloudfoundry/bosh


text:
runner_z1/0 is not running after update. Review logs for failed jobs: warden, dea_next

Updating instance runner_z1: runner_z1/6262f048-954a-4dff-b04e-f9818cab3dc0 (0) (canary) (00:10:45)
L Error: 'runner_z1/0 (6262f048-954a-4dff-b04e-f9818cab3dc0)' is not running after update. Review logs for failed jobs: warden, dea_next
06:23:50 | Error: 'runner_z1/0 (6262f048-954a-4dff-b04e-f9818cab3dc0)' is not running after update. Review logs for failed jobs: warden, dea_next
runner_z1 logs:
please remove .txt.
peracloud.runner_z1-20170609-062439-977279851.tgz.txt

Hi @bxlkm. I took a look at the logs, and the issue is that you're deploying with an incompatible stemcell. You need to be using the 3312.X line.
More importantly, however, support for the runner jobs ended a few weeks ago. You'll need to start deploying Diego instead.

Hi @bxlkm. I'm going to close this issue due to inactivity, but feel free to close it if you need more help.

authors: bxlkm dsabeti

repo: cloudfoundry/cf-release


text:
CF cups password prompt should hide user input

Please provide details on the following items. Failure to do so may result in deletion of your feature request.
We were creating a user provided service with cf cups redis -p "host, port, password" and we noticed that the password prompt is displayed in plaintext while entering it.
What's the user value of this feature request?
User security
Who is the functionality for?
People using create-user-provided-service and interactively entering password
How often will this functionality be used by the user?
Any time creating a user provided service
Who else is affected by the change?
N/A
Is your feature request related to a problem? Please describe.
No, just concerned
Describe the solution you'd like
Password input should be either asterisked out or blank
Describe alternatives you've considered
N/A
Additional context
example current workflow:
$ cf cups redis -p "host, port, password"

host> example-db.cloud.redislabs.com

port> 15462

password> hunter12

@jpalmerpivotal : Thank you for submitting the issue, we agree that it is not very ideal in terms of security to expose the password field. There is an option for passing the credentials in a file rather than plain text if you wish to hide the,.
We think that coming up with an exhaustive and predictable list of parameter names that should be treated as secure, would be really difficult in this case, just password won't cover all scenarios.
Please re-open the issue if you see any other issue with this command or option mentioned above.
Thanks,
Aarti & @ablease

authors: AartiKriplani jpalmerpivotal

repo: cloudfoundry/cli


text:
Ensure space supporter receives proper error code for specific environment variable endpoints

Context
We are introducing a new role and we want to make sure it has the right access.
Expected result
A space should get a 403 unauthorized error when trying to curl the following endpoints:
GET /v3/apps/:guid/environment_variables
PATCH /v3/apps/:guid/environment_variables
Acceptance
As a space supporter, if I curl the above endpoints for an app that exists, I receive a 403 error telling me I am not authorized to perform this action.
Documentation
No changes required. We are just aligning with our style guide.

I wasn't sure if there was a reason that this wasn't on the project board... so I just added it.

Oh no! I think this story got duplicated because it wasn't on the project board. I think the behavior we are looking for is covered by #2388. Thank you still for your contributions!

@monamohebbi I'll close the PR I opened then.  Should this issue be closed then also?

@moleske hold off for one second, I'd like to test and confirm against a bosh lite that these changes really have made it through.

Closing out this issue. I think this was made on accident as we have updated other issues to allow for both of these endpoints to be used by the space supporter.

authors: ctlong moleske monamohebbi


text:
Add cpu_weight_scalar configuration property

This configuration property gives operators more control over the CPU weight calculation
and the ability to disable CPU reservations entirely.
Resolves #2107
Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

Adds a configuration property cpu_weight_scalar which allows operators control over how aggressive the CPU reservations are.

An explanation of the use cases your change solves

Currently we find the CPU calculation to be too aggressive. This allows operators to adjust the weight on a whole deployment until it is possible to specify on a per app basis.

Links to any other associated PRs

[x] I have reviewed the contributing guide

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

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

Unfortunately I had a lot of trouble getting Ruby running locally and have been unable to run acceptance tests

Hi there! This is my first PR in Ruby so please let me know if I missed anything. Specifically I want to make sure this defaults to 1.0 if it is not specified.
Additionally there is 1 test failure in postgres but it doesn't seem to be related to my changes here.

closing in favor of https://www.pivotaltracker.com/n/projects/2172361/stories/177225389

authors: braunsonm sethboyles


text:
credentials in cmdArgs are not redacted

Below line logs credentials in cmdArgs but does not redact them.
https://github.com/cloudfoundry/voldriver/blob/master/invoker/invoker.go#L30

Hi Abel,
Are you using the RedactingWriterSink that we use in nfsv3driver?
If so, note that RedactingWriterSink is configurable--you can give it regular expressions to redact things from your logs based on pattern match of either the keys or the values of json that is passed in a lager.Data block.  If you give it nil pattern lists, it will default to filtering any value where the key contains pwd or pass, and it will also look for MD5 keys, SHA values AWS keys, or private SSH keys, but it is totally customizable.
You can find the code that sets up the default values for redaction here: https://github.com/cloudfoundry/lager/blob/b4f07fd10491fae0d6d9a0d07145e9f90935ac50/json_redacter.go#L22
My guess is that you just need to override the pattern list for the key patterns to include whatever key value your secrets have.
HTH,
-Julian

@julian-hj I did use the same code. You can see my code here.
The password in opts is redacted but that in args is not.
Below is my logs:
{"data":{"opts":{"dirMode":"0777","fileMode":"0777","gid":"2000","password":"*REDACTED*","source":"//abelstorage.file.core.windows.net/test","uid":"2000","username":"abelstorage","vers":"3.0"},"session":"3.8900.1.1"},"log_level":1,"message":"smb-driver-server.server.handle-create.with-cancel.create.with-opts","source":"smb-driver-server","timestamp":"1496644498.816172600"}
{"data":{"args":["-t","cifs","//abelstorage.file.core.windows.net/test","/var/vcap/data/volumes/smb/d7633591-a3c3-44e4-96f6-8ee9fcd2e2b4-27c18a0aaf2ade2cd5568d67a428c62f","-o","username=abelstorage,password=MY-REAL-PASSWORD-HERE,file_mode=0777,dir_mode=0777,uid=2000,gid=2000,vers=3.0","--verbose"],"executable":"mount","session":"3.8901.1.1.4","volume":"d7633591-a3c3-44e4-96f6-8ee9fcd2e2b4-27c18a0aaf2ade2cd5568d67a428c62f"},"log_level":1,"message":"smb-driver-server.server.handle-mount.with-cancel.mount.invoking-command.start","source":"smb-driver-server","timestamp":"1496644498.817555189"}

Yes I see--it is because in this case the "password" string is in a value in the array so the key filter will not find it. Probably you could add "args" to the list of key filters to fix this, or add "pass" to the list of value filters.

Sent from VMware Boxer
On August 10, 2017 at 6:31:50 PM PDT, Chou Hu notifications@github.com wrote:
@julian-hjhttps://github.com/julian-hj I did use the same code. You can see my code herehttps://github.com/AbelHu/smbdriver/blob/master/cmd/smbdriver/main.go#L252.
The password in opts is redacted but that in args is not.
Below is my logs:
{"data":{"opts":{"dirMode":"0777","fileMode":"0777","gid":"2000","password":"REDACTED","source":"//abelstorage.file.core.windows.net/test","uid":"2000","username":"abelstorage","vers":"3.0"},"session":"3.8900.1.1"},"log_level":1,"message":"smb-driver-server.server.handle-create.with-cancel.create.with-opts","source":"smb-driver-server","timestamp":"1496644498.816172600"}
{"data":{"args":["-t","cifs","//abelstorage.file.core.windows.net/test","/var/vcap/data/volumes/smb/d7633591-a3c3-44e4-96f6-8ee9fcd2e2b4-27c18a0aaf2ade2cd5568d67a428c62f","-o","username=abelstorage,password=MY-REAL-PASSWORD-HERE,file_mode=0777,dir_mode=0777,uid=2000,gid=2000,vers=3.0","--verbose"],"executable":"mount","session":"3.8901.1.1.4","volume":"d7633591-a3c3-44e4-96f6-8ee9fcd2e2b4-27c18a0aaf2ade2cd5568d67a428c62f"},"log_level":1,"message":"smb-driver-server.server.handle-mount.with-cancel.mount.invoking-command.start","source":"smb-driver-server","timestamp":"1496644498.817555189"}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cloudfoundry/voldriver/issues/2#issuecomment-321714472, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIF0_KE_mceE34Aqp4W-UN64z6K6PmsYks5sW68CgaJpZM4OzJqS.

If I set any of the key or value as a filter, the default filters will be overwritten. It is not my expected. Could we add a new value filter in json_redacter for such cases? How do you think?
https://github.com/cloudfoundry/lager/blob/94c528f7360490f75431b618078be3c89dcbbe50/json_redacter.go#L22-L27

It was never really the intent that the default values for the redacter would catch all secrets.  We added that redaction capability because we anticipated that people would write drivers and brokers that have different types of sensitive information we could not know about in advance.  So we made the RedactingWriterSink configurable for exactly this kind of circumstance--so that we don't have to modify our code each time someone uses it within a different library.
We might consider removing the args from that logger session altogether, since it's likely to have sensitive things in it, but in the mean time, I think it's a pretty small change in your newLogger function to add "args" to the list of redacted keys:
	sink, err := lager.NewRedactingWriterSink(os.Stdout, lager.DEBUG, []string{"[Pp]wd","[Pp]ass","args"}, nil)

@julian-hj Agree with you. It is better to remove args in logs.  I will try to create RedactingWriterSink with customized filters. Thank you so much.

authors: AbelHu julian-hj

repo: cloudfoundry/voldriver