cmd/go: incompatible module version not detected by 'go run' or 'go build'

What version of Go are you using (go version)?

[user@localhost ~]$ go version
go version go1.13 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
[user@localhost ~]$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY="*.sc-corp.net"
GONOSUMDB="*.sc-corp.net"
GOOS="linux"
GOPATH="/home/user/go"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/user/.local/share/umake/go/go-lang"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/user/.local/share/umake/go/go-lang/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/tmp/test/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build698062687=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Create the following go.mod file:
module test

go 1.13

require k8s.io/client-go v12.0.0+incompatible

Create the following main.go file:
package main

import (
        "fmt"

        "k8s.io/client-go/pkg/version"
)

func main() { fmt.Println(version.Get()) }

What did you expect to see?
The toolchain should fail all interactions with k8s.io/client-go because of the combination of the go.mod file at the v12.0.0 tag:
[user@localhost test]$ go get<EMAIL_ADDRESS>go: finding k8s.io v12.0.0
go: finding k8s.io/client-go v12.0.0
go: finding k8s.io/client-go v12.0.0
go get<EMAIL_ADDRESS><EMAIL_ADDRESS>invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v12
[user@localhost test]$ go run .
go: finding k8s.io/client-go v12.0.0+incompatible
go: finding k8s.io/client-go v12.0.0+incompatible
go list -m<EMAIL_ADDRESS>invalid version: +incompatible suffix not allowed: module contains a go.mod file, so semantic import versioning is required
[user@localhost test]$ go build
go: finding k8s.io/client-go v12.0.0+incompatible
go: finding k8s.io/client-go v12.0.0+incompatible
go list -m<EMAIL_ADDRESS>invalid version: +incompatible suffix not allowed: module contains a go.mod file, so semantic import versioning is required
[user@localhost test]$ go doc k8s.io/client-go/pkg/version
go: finding k8s.io/client-go v12.0.0+incompatible
go: finding k8s.io/client-go v12.0.0+incompatible
go list -m<EMAIL_ADDRESS>invalid version: +incompatible suffix not allowed: module contains a go.mod file, so semantic import versioning is required

What did you see instead?
All parts of the toolchain I tested appear to re-find the problematic module on every invocation, however go get fails (as above), go doc warns, and both go run and go build succeed:
[user@localhost test]$ go run .
go: finding k8s.io/client-go v12.0.0+incompatible
go: finding k8s.io/client-go v12.0.0+incompatible
v0.0.0-master+$Format:%h$
[user@localhost test]$ go build
go: finding k8s.io/client-go v12.0.0+incompatible
go: finding k8s.io/client-go v12.0.0+incompatible
[user@localhost test]$ ./test
v0.0.0-master+$Format:%h$
[user@localhost test]$ go doc k8s.io/client-go/pkg/version
go: finding k8s.io/client-go v12.0.0+incompatible
go: finding k8s.io/client-go v12.0.0+incompatible
go list -m<EMAIL_ADDRESS>invalid version: +incompatible suffix not allowed: module contains a go.mod file, so semantic import versioning is required
package version // import "k8s.io/client-go/pkg/version"

Package version supplies version information collected at build time to
kubernetes components.

func Get() apimachineryversion.Info

I am not sure if this is a bug in build or doc. /cc @bcmills @jayconrod who know more about the nuances here.

Thanks for the report. I can reproduce the described behavior starting from a clean module cache, and this is indeed a bug in go run / go build.

Hi all,
I see the same problem on Golang 1.15, also when I run go mod download it produces this output:
<EMAIL_ADDRESS>invalid version: +incompatible suffix not allowed: module contains a go.mod file, so semantic import versioning is required

It seems that the problem is with the v12.0.0+incompatible version, finally I opted by using v0.18.2 according to my k8s version and works fine

@seguidor777, that's https://github.com/kubernetes/client-go/issues/631.

With the recent changes in 1.16 the failure is not reproducable through the suggestions and default flow:
[user@localhost trash]$ go run .
go<EMAIL_ADDRESS>missing go.sum entry; to add it:
        go mod download k8s.io/client-go
[user@localhost trash]$ go mod download k8s.io/client-go
go mod download<EMAIL_ADDRESS>invalid version: +incompatible suffix not allowed: module contains a go.mod file, so semantic import versioning is required

But the go get is only a warning, so it still reproduces:
[user@localhost trash]$ go get<EMAIL_ADDRESS>go get<EMAIL_ADDRESS>invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v12
[user@localhost trash]$ go run .
main.go:6:2: missing go.sum entry for module providing package k8s.io/client-go/pkg/version (imported by test); to add:
        go get test
[user@localhost trash]$ go get test
go: downloading k8s.io/client-go v12.0.0+incompatible
go: downloading k8s.io/apimachinery v0.0.0-20190612205821-1799e75a0719
go: warning<EMAIL_ADDRESS>retracted by module author: pre-module versions are obsolete
go: to switch to the latest unretracted version, run:
        go get k8s.io/client-go@latest
[user@localhost trash]$ go run .
v0.0.0-master+$Format:%h$

Though the go get test line really smells of a bug.

Thanks for the updated steps to reproduce. I'll see if I can get to this for 1.17 once the lazy-loading changes are done.

@bcmills Is this likely to happen for 1.18?  Thanks.

Sadly no.
(Changes to version validation tend to catch existing broken modules, so they shouldn't happen during the freeze.)


Fabric, Minecraft Version 1.16.3

When I go through the portal I seem to phase through the floor see here

I cannot reproduce. Uploading the world would help.

Are you using Forge? If so try the latest Fabric version

Close because outdated.


Prepare for separating ClassElement, EnumElement, and MixinElement.

All three implement InterfaceElement, but in the breaking change for analyzer we will stop implementing ClassElement in EnumElement and MixinElement. This is a minimal change necessary to make google3 green, the might be need for more changes that are not exercised there.

This sounds reasonable to me, I was told that only the stable version is rolled.


Refactor gravity_stas and gravity_aps to **

this is in the wrong project and should be in esp32-gravity. Oops. Oh well, it's still required


write OpenSSL integration test for Windows

Write the equivalent of integration/oqs_openssl/run.sh for Windows.

See #8


[8.x] Use parents to resolve middleware priority

This PR allows using parents of the middleware as fallback to resolve the middleware priority. This allows overriding system middlewares while it keeps the correct ordering.
Also this fixes a bug where Jetstream overrides the AuthenticateSession middleware but since the priority was lost, a password update will log out the user if it was authenticated on a non-default guard.

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!


Remove dead code

Already checked on line 56

Already fixed in https://github.com/neo-project/neo-node/pull/613


HQ UK Support

Hi ,
I would love if you could adapt this to support HQ UK

It supports it.
On Fri, May 11, 2018 at 3:42 AM Anush Patel<EMAIL_ADDRESS>wrote:

Hi ,
I would love if you could adapt this to support HQ UK
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gjacobs314/HQTrivia/issues/47, or mute the thread
https://github.com/notifications/unsubscribe-auth/AhAkIips2vYO6_dcJk6eT8U8mkLOmYvWks5txUDygaJpZM4T7CoB
.

--
Gordon

Does it? The Stream links shows US Data?

If you are from the US and using US credentials then it will be for US.
It’s automatic. HQ doesn’t have a different app for ppl in UK does it?
On Fri, May 11, 2018 at 7:16 AM Anush Patel<EMAIL_ADDRESS>wrote:

Does it? The Stream links shows US Data?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gjacobs314/HQTrivia/issues/47#issuecomment-388335477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhAkIjWH0IAM1-qqZx1YB6RiVfinr5nHks5txXMkgaJpZM4T7CoB
.

--
Gordon


Add mountAsync, groupAsync

These will do the same as their sync equivalents, but allow for a callback that returns FutureOr<void>.

https://pub.dev/packages/angel_route/versions/3.1.0+1


test_type: method uses old test types

Describe the bug
As documented here test_type: accepts data and schema instead of bespoke and generic.
Steps To Reproduce
dbt test -m test_type:bespoke
dbt test -m test_type:generic

Expected behavior
The selectors to work ;)
$ dbt test --m test_type:generic
Running with dbt=0.20.1-rc1
Partial parsing enabled: 0 files deleted, 0 files added, 0 files changed.
Partial parsing enabled, no changes found, skipping parsing
Found 145 models, 749 tests, 0 snapshots, 0 analyses, 341 macros, 0 operations, 4 seed files, 67 sources, 0 exposures
Encountered an error:
Runtime Error
  Invalid test type selector generic: expected "data" or "schema"

System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[X] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.20.1-rc1
   latest version: 0.20.0

Your version of dbt is ahead of the latest release!

Plugins:
  - bigquery: 0.20.1rc1
  - snowflake: 0.20.1rc1
  - redshift: 0.20.1rc1
  - postgres: 0.20.1rc1

The operating system you're using: Mac
The output of python --version: 3.8.10
Additional context
While I'm running the 0.20.1rc, I don't believe this to be an issue specific to the RC

@jaypeedevlin You're 100% right! Thanks for opening the issue, it's one of a few things that prompted me to rekindle the conversation over in https://github.com/dbt-labs/dbt/issues/3234. I'd love to get your thoughts there about where we're landing: definitely sticking with generic, but leaning singular over bespoke
I'm going to close this issue in favor of that one, to keep the conversation centralized there. Once we have a final verdict, it's time for find+replace in the codebase.


feat: Ensure claimer is owner of the note

I'm going to update the e2e test too

Benchmark results
Metrics with a significant change:

tx_sequencer_processing_time_ms (0): 10.5 (+37%)
note_successful_decrypting_time_in_ms (8): 145 (-35%)
note_trial_decrypting_time_in_ms (8): 54.2 (+101%)
note_trial_decrypting_time_in_ms (64): 133 (+279%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 7f216eb0 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
5,668
18,820
36,356

l1_rollup_calldata_gas
65,848
238,564
469,460

l1_rollup_execution_gas
666,328
953,273
1,336,616

l2_block_processing_time_in_ms
1,302 (-2%)
4,660 (-2%)
8,900 (-6%)

note_successful_decrypting_time_in_ms
:warning: 145 (-35%)
553 (+15%)
1,002

note_trial_decrypting_time_in_ms
:warning: 54.2 (+101%)
73.3 (-25%)
:warning: 133 (+279%)

l2_block_building_time_in_ms
12,479 (+2%)
48,951 (+1%)
98,513 (+1%)

l2_block_rollup_simulation_time_in_ms
7,388 (+1%)
29,019
59,077 (+2%)

l2_block_public_tx_process_time_in_ms
5,052 (+2%)
19,867 (+2%)
39,323 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,655 (+3%)
26,757 (-4%)

note_history_successful_decrypting_time_in_ms
1,244 (-3%)
2,552 (+3%)

note_history_trial_decrypting_time_in_ms
93.6 (-18%)
189 (-1%)

node_database_size_in_bytes
18,640,976
35,315,792

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
274 (+1%)
44,338
27,700

private-kernel-ordering
210 (+1%)
52,324
14,326

base-rollup
670 (+2%)
177,083
925

root-rollup
68.8 (+1%)
4,176
789

private-kernel-inner
363 (+1%)
73,197
27,700

public-kernel-app-logic
179
34,582
27,671

public-kernel-tail
92.0 (+1%)
34,206
27,671

merge-rollup
8.36 (+1%)
2,696
925

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.1 (+1%)
16.2 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.586 (+1%)
0.501 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
46.2 (+1%)
72.9 (-1%)
230
458 (+2%)
865
1,716 (-1%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.474 (+1%)
0.450 (-1%)
0.420
0.428 (+2%)
0.412
0.410 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
54.2 (+1%)
108 (+2%)
335 (+1%)
680 (+3%)
1,311
2,585 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
104
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.481 (+1%)
0.487 (+1%)
0.455
0.467 (+3%)
0.454
0.450
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
62.1 (+2%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.543 (+1%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes

tx_size_in_bytes
19,191

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
2,822
1,454 (+1%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
:warning: 10.5 (+37%)
616 (+1%)


Porting to 1.18.2

Hello, i'm created modpack on my home server, and i rid of programs for lan tunnelling. I found this mod, and want see on 1.18.2 version. Can you please port this mod?

Forgot to add, mod for Forge 1.18.2

I'll work on it in the next few days.

If cloudflared installed already with config, mod will be use it, or it uses other method?

The mod will always download its own binary file. The only thing the user has to do is create the json file.

If cloudflared installed already configured, mod will be use it, or it uses other method?

I don't know if you can run 2 cloudflared tunnels from one machine but since you are only accessing a tunnel it should work. Test it and report the results

It should now work on Minecraft version 1.18.2. Unfortunately, I don't have a Cloudflared test server, so I couldn't test it. If you find any problems, please feel free to reopen the issue.

Thanks for porting mod, but it seems not work. I have setted up access.json in modflared folder, configured default config.yml, mod downloaded binary, but it dont start (im checked manually, it work).
In server logs

[modloading-worker-0/ERROR] [modflared/]: No accessData to load found!

what i do wrong?
in access.json

I ported the 1.20.2 1.0.0 version to 1.18.2.  This version no longer uses access.json.  You can find a description of the new version on the Modrinth page.  If something doesn't work or you have questions, just write them in the issue.

It doesnt start tunnel, on zerotrust dashboard tunnel is down, but i can manually set it up by command

cloudflared tunnel run

But it does nothing, client cant connect to server anyway

You have to set up the tunnel so that it appears as UP in your Zero Trust dashboard. Then you have to add the DNS record for the Tunnel CNAME -> ".cfargotunnel.com". Then you have to create a TXT-DNS entry with the value “cloudflared-use-tunnel” and the same sub-domain. When everything is done you can start your Minecraft and enter the DNS name for your tunnel CNAME entry “example.mydomain.com”. NOTE: The server's MOTD is not visible!

Thanks for porting mod, but it seems not work. I have setted up access.json in modflared folder, configured default config.yml, mod downloaded binary, but it dont start (im checked manually, it work). In server logs

[modloading-worker-0/ERROR] [modflared/]: No accessData to load found!

what i do wrong?
in access.json

Please note that Modflared is not a server mod but a mod that allows the client to easily connect to the server. Cloudflared must be set up manually by the server admin.

Can you run the command windows-amd64.exe access tcp --hostname minec.mydomain --url localhost:27095 in the Modflared bin folder and then try to join the server with localhost:27095?

I'm trying to do everything on my local machine, maybe later I'll try to connect through a friend, maybe that will work....

I tested it again on my setup and it worked without any problems. I have uploaded screenshots of the DNS and tunnel settings.

I tested again with tunnel on localhost, <IP_ADDRESS> and received ip from router
Ill try bit later on a vps

Any updates?

Many days and nothing, idk what im doing wrong, tried many variations, reinstalled cloudflared, rewrite config on cli, created many tunnels on dashboard...


Cuda issue : RuntimeError: CUDA error: invalid device ordinal

In your code, the GPU you are using is named "cuda:1", but this fails on some computers.
For instance, on my computer, this dummy piece of code fails :
import torch
device = torch.device("cuda:1")
a = torch.tensor([1, 2, 3])
a.to(device)  # Fails

The error is
RuntimeError: CUDA error: invalid device ordinal
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1

I had the same error with this repository, and I fixed this error by replacing all occurences of "cuda:1" to "cuda:0"
The files involved are:

https://github.com/yandex-research/tab-ddpm/blob/b476257dd460b778ba09eb97f7a51d6490fa17f8/scripts/train.py#L12
https://github.com/yandex-research/tab-ddpm/blob/b476257dd460b778ba09eb97f7a51d6490fa17f8/scripts/train.py#L91
https://github.com/yandex-research/tab-ddpm/blob/b476257dd460b778ba09eb97f7a51d6490fa17f8/scripts/pipeline.py#L41
https://github.com/yandex-research/tab-ddpm/blob/b476257dd460b778ba09eb97f7a51d6490fa17f8/scripts/sample.py#L34
all the files in exp/*/*/config.toml

Hi, I'm having the same problem as you and would like to ask about your version of cuda and pytorch to run the code？


[MINOR] chore: unify the style of spark profile id

What changes were proposed in this pull request?
Change spark3 profile to spark3.1.
Change spark2 profile to spark2.4.
Why are the changes needed?
To make profile names more intuitive.
Does this PR introduce any user-facing change?
-Pspark3 should be replaced by -Pspark3.1.
-Pspark2 should be replaced by -Pspark2.4.
How was this patch tested?
CI.

I'm not quite satisfied with this style.
Normally spark2/spark3 for spark2 and spark 3 branches, it would be better if we could specify minor version with -Dspark.minor.version={2.3.1,2.4.6} to build with different releases.

We don't support every minor version.

I'm not quite satisfied with this style.
Normally spark2/spark3 for spark2 and spark 3 branches, it would be better if we could specify minor version with -Dspark.minor.version={2.3.1,2.4.6} to build with different releases.

Let's make incremental improvements first?

Please help check if there is any missing changes required in this PR.


rename emit to invalidate; remove invalidate method from GraphQL live query store

The invalidate method is an implementation detail of the InMemoryLiveQueryStore

resolved by https://github.com/n1ru4l/graphql-live-queries/pull/168


adding helm-repo as github pages

Changes done:

Make our github pages as an helm repo as well 🤣  (History images are also maintained😆 )
Partially resolve #693

Test done:
An helm repo build via make docs-deploy, which contains different versions of alb-ingress-controller-helm: https://m00nf1sh.github.io/aws-alb-ingress-controller
How to install:
helm repo add aws-alb https://m00nf1sh.github.io/aws-alb-ingress-controller
helm repo update
helm repo install aws-alb/alb-ingress-controller-helm --name=test --set extraArgs.v=1 or
helm repo install aws-alb/alb-ingress-controller-helm --version=0.1.3 --name=test --set extraArgs.v=1
Source code of helm-repo plugin:
https://github.com/M00nF1sh/mkdocs-helm
Future work:

Tune our helm charts.
Update  alb-ingress-controller-helm into alb-ingress-controller or aws-alb-ingress-controller, since the -helm suffix is not need after migrate off quay.io
Update the docs for install instructions
Move the chart to centralized helm repo :(

@M00nF1sh I get an error while trying to install alb-ingress-controller via CLI using this command:
helm repo install aws-alb/alb-ingress-controller-helm --name=test --set extraArgs.v=1
Error: unknown flag: --name

the correct command is:
helm install aws-alb/alb-ingress-controller-helm --name=test --set extraArgs.v=1

and to check if the alb-ingress-controller is installed:
$ kubectl --namespace=default get pods -l "app=alb-ingress-controller,component=controller,release=test"

NAME                                                      READY     STATUS    RESTARTS   AGE
test-alb-ingress-controller-controller-8654c45bf5-28786   1/1       Running   0          1m

I realized when I installed the chart like this:
helm install --name alb-ingress --namespace kube-system --set extraArgs.v=1 aws-alb/alb-ingress-controller-helm

The installation works, but the deployment name will be:
alb-ingress-alb-ingress-controller-controller

The name contains a lot of redundant terms.

Hi, do you have suggestions for this 😄 , currently the deployment name is generated as 'releaseName-alb-ingress-controller'. I noticed other projects like helm using similar name pattern..

The "helm create" command in 2.11.0 has updated the default _helpers.tpl functions which will address that redundancy. It also has different default labels. We may want to consider recreating the chart with helm 2.11.0.

The "helm create" command in 2.11.0 has updated the default _helpers.tpl functions which will address that redundancy. It also has different default labels. We may want to consider recreating the chart with helm 2.11.0.

Nice! I'll recreate the helm chart.
BTW, the current helm is creating the resources in default namespace, should we change it to kube-system to align with our example yaml?

Most charts that i've seen dont specify a namespace in their resource templates, allowing users to specify a namespace in their helm upgrade command. Maybe we include an example helm upgrade --namespace kube-system in the docs?

I agree with @rifelpet, I would not specify the kube-system namespace in the template, but what is important for me is to be able to set the name and the namespace to what I want.

Most charts that i've seen dont specify a namespace in their resource templates, allowing users to specify a namespace in their helm upgrade command. Maybe we include an example helm upgrade --namespace kube-system in the docs?

Cool!  Then an example usage in READ.md should be enough, thanks for the explanation! 👍

/lgtm


FEAT: South Carolina PDF Vaccine Data

There is a tableau dashboard, however I can't seem to find all the data. The PDF's are much more in depth with the available data.
The problem with the PDF's is that they aren't formatted consistently. I've made some headway with requesting all the data from the PDF's with a given date, but formatting it is proving to be a bit tricky.
Currently, the fetch method works, and will download the associated vaccine data for all three vaccines (Moderna, Pfizer, and Jenssen).

The data for today probably hasn't been uploaded yet. By default, if the data isn't uploaded, I return an empty dataframe.

I see -- My preference would be to grab the most recent data.
Could we do that?

@tlyon3 this doesn't seem to be catching everything :(
Here's what I get from the scraper:
In [2]: d = SCVaccineCounty()

In [3]: data = d.fetch()

In [4]: df = d.normalize(data)
Normalizing pfizer data
Normalizing moderna data
Normalizing janssen data

In [5]: df.groupby("category")["value"].sum()
Out[5]:
category
janssen_vaccine_completed     35554.0
moderna_vaccine_completed    118015.0
moderna_vaccine_initiated    173274.0
pfizer_vaccine_completed       5845.0
pfizer_vaccine_initiated      23454.0
Name: value, dtype: float64

And here are the summary stats in the Pfizer pdf:

Looks like we aren't even close :(

This is the problem that I talked about in the discussion. The missing data is probably coming from the pages that I couldn't figure out how to parse.

Ahh ok. Well for now I think we are stuck unless you can figure out how to parse those.

PDF's are still not matching up. Luckily they are now displaying their data on a Tableau dashboard. This is great, because it ensures their are no parsing errors. However it doesn't seem to have all the data we want. It currently has:

total doses by county
at least one dose by county
fully vaccinated by state

It is missing fully vaccinated by county. And I can't find a way to extrapolate the fully vaccinated by county with the current available data.
I've also found their ArcGIS server, but the data is the same data in the dashboard.

What's your recommendation ?

I'm not sure. the PDF's have the most amount of data, but they are inconsistently formatted and difficult to parse via camelot.
The dashboard doesn't have the data we want, and neither does the ArcGIS server.

What data is missing from Tableu and ArcGIS?
Do either  (or both together) of them provide people with at least one dose and people fully vaccinated by county?

ArcGIS and  Tableau have the same data. They are both missing total_vaccine_completed by county. They have it by state, but not county


Handshake failed. Your blog does not support https, Try to changing it to http

FILL THESE DETAILS FIRST:

Ghost version: 1.5.2
App version: 1.5.6

When I try to sing in with the app I got this message:
Handshake failed. Your blog does not support https, Try to changing it to http!
but if you open my blog:
blog.tareef.me
your can see that it run with SSL without any problem. How I can figure out the problem and solve it?
thanks

Hi @tareefdev 👋
The Ghost 1.x support in Quill is in beta right now. To get it, you'll need to opt in to the beta here: https://play.google.com/apps/testing/me.vickychijwani.spectre.
Just follow the instructions there and you should be able to sign in. To confirm you have the beta installed, check your system settings > Apps > Quill. The version should be 2.0.0-beta2.
I guess the error message could be clearer though (something like "Your blog uses Ghost 1.x. To use Quill with it, please opt in to the beta here: ). Let me see if I can do that - leaving this issue open to track.

Hi @vickychijwani
Thanks for your working in this wonderful app. I upgraded successfully to 2.0.0-beta2 (which use a new UI?), clean the app cache, but still face the same error!
What else can we do?
thanks :)

Let me guess: you're using Android 7.0 right? In that case I think I know what the problem is and can replicate it. The bad news is that it's a bug in Android 7.0 (here's the bug report), which was fixed in Android 7.1.1.
So here are the solutions I can think of:

Update your device to Android 7.1.1
If that's not possible, try setting this in your Nginx configuration, because prime256v1 (also known as "secp256r1" or "NIST P-256") is the only elliptic curve Android 7.0 supports (that is the bug): ssl_ecdh_curve prime256v1;
If that doesn't work either, you may want to remove the elliptic-curve cipher suites (ones starting with "ECDHE") entirely from your Nginx configuration (depending on whether you think the security trade-off is worth it).

Let me know what works for you.

 My phone (Samsung S8) run with Android 7.0, But I think Samsung will send the version 7.1.1 this month or something like that.. so I prefer to wait this period of time although I'm very excited to try your app since it has a very nice reputation in the store
Big thanks for your help :)

Quill v2.0.0 is now rolled out to all users, so this issue can be closed 🎉


docs: remove "Built with deno_std" badge

No one uses it.

There are some usages and they will be broken with this change https://github.com/search?q=https%3A%2F%2Fraw.githubusercontent.com%2Fdenoland%2Fdeno_std%2Fmain%2Fbadge.svg&type=code

Possible replacement: https://img.shields.io/badge/built_with_deno__std-blue?logo=deno


(#50791): after extensions/v1beta1 is removed, move selector immutability check inside ValidateReplicaSetUpdate().

Issue opened with imdone.io from code comment on 92952cf
TODO (#50791): after extensions/v1beta1 is removed, move selector immutability check inside ValidateReplicaSetUpdate(). id:1482

https://github.com/imdone/kubernetes/blob/92952cfe77835cffd1a861221507df2592c2e857/pkg/registry/extensions/replicaset/strategy.go#L124-L129

Can anyone clarify me about these issue


Add Logic to Process Use as Application Owner New Property Introduced for WSO2 IS Connector Configuration

Purpose

Add Logic to Process New Property Introduced for WSO2 IS Connector Configuration
Related Issue: https://github.com/wso2/api-manager/issues/1821

Related PRs
https://github.com/wso2-extensions/apim-km-wso2is/pull/108
https://github.com/wso2/carbon-apimgt/pull/12027

Replaced with https://github.com/wso2/apim-apps/pull/472


logged in with someone else account

When going on the server website, sometimes you are automatically logged in as someone else.

I have so far never seen this

Happened to me too. On my phone in Chrome I went to the site and I was logged in as Albert, without asking for pwd. It seems it only happens among site admins. It's also not easy to reproduce this. It may be related to this: https://stackoverflow.com/questions/32885710/flask-login-sometimes-mixes-logins-im-logged-in-as-somebody-else


Address agent unit test suite instability

Type of change

Bugfix

Description
I was seeing the Agent unit test suite mostly fail both locally and on CI.  With these test only changes, the suite seems much more stable.

The semantics of addAddressSettings/removeAddressSettings mock methods didn't match the real implementation.  The handling of those errors seemed to be cause some of the suite's instability.
Corrected a missing Rhea client.close().
Added close/done chaining in the ragent afterEach to ensure that resources are definitely released before the next test starts.

Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest crc

@enmasse-ci run tests profile=systemtests testcase=SmokeTest crc

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: systemtests
TEST_CASE: SmokeTest
TOTAL: 14
PASS: 14
FAIL: 0
SKIP: 0
BUILD_NUMBER: 1344
BUILD_ENV: crc

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest crc

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: systemtests
TEST_CASE: SmokeTest
TOTAL: 14
PASS: 14
FAIL: 0
SKIP: 0
BUILD_NUMBER: 1346
BUILD_ENV: crc

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=systemtests testcase=SmokeTest

:x: Test Summary :x:
TEST_PROFILE: systemtests
TEST_CASE: SmokeTest
TOTAL: 14
PASS: 13
FAIL: 1
SKIP: 0
BUILD_NUMBER: 1354
BUILD_ENV: oc cluster up
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testAddressTypes in io.enmasse.systemtest.isolated.brokered.SmokeTest

@enmasse-ci run tests profile=systemtests testcase=SmokeTest crc

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: systemtests
TEST_CASE: SmokeTest
TOTAL: 14
PASS: 14
FAIL: 0
SKIP: 0
BUILD_NUMBER: 1355
BUILD_ENV: crc


Feature request: output to jpg file format

Hi there! This is a great add on, thanks for build and maintenance. I’m trying to use an inkplate in lieu of a kindle, which only accepts jpg file format. Any chance you could build option to change image output to jpg? Also, is there a way to specify a full URL for the image rather than a port? (Inkplate programming via Ardunio IDE seems to only want an address ending in .jpg rather than an open port). Thanks heaps!

Hi, allowing an output type jpeg sounds like a good idea, I'll keep that on the list!
I'm not sure about including the file extension in the path, however. It sounds like an easy way the library took to detect the file type.
If I'm not mistaken, it should be possible for you to work with Image::drawPngFromWeb after including the ImagePNG.h, see their code: https://github.com/SolderedElectronics/Inkplate-Arduino-library/blob/aba019c9d2e67bc7e4afb9862be97cf22bd4b430/src/include/ImagePNG.cpp#L208
Maybe this also already solves your specific case?

Hi Sibbl.
Just discovered your screensaver. Its exactly what i was looking for as I did collect an old Kodak digital photo frame from the 2nd hand store. Unfortunately it would only accept JPG's so I would be highly interested in this feature request as well. Many thanks in advance!

I adapted the so its exporting to JPG. Does what it needs to do, although this is not the most pretty solution. See my fork

@LaTrappe thanks for that reference! Do you think you'd find the time to make the file extension configurable? I think a lot of people would be interested in such a pull request 👍 I currently unfortunately don't find the time myself, but would be happy to review it and support you.

@LaTrappe thanks for that reference! Do you think you'd find the time to make the file extension configurable? I think a lot of people would be interested in such a pull request 👍 I currently unfortunately don't find the time myself, but would be happy to review it and support you.

Im afraid not, Im not a software developer. Just a script kiddy. See this as a proof of concept.

MR available for discussion.


Readme

@aneesh2usman could you add the compatible python and django versions in the readme?
That'd be quite helpful.

support Python >=3.6


Crysis flickering foliage

While playing Crysis foliage has flickering shaders(?) or something like that, here's an image example of an extreme scenario.
Software information
Crysis, any settings. The object detail setting is the only setting that has a noticable impact on the amount of flickering foliage, setting it to very high is ideal for maximizing reproduction of the effect, if set to high there will be noticably less of foliage flickering (even if the amount of foliage itself is not reduced)
System information

GPU: Nvidia GTX 980-Ti
Driver: 410.57
Wine version: Proton 3.16-1 Beta
DXVK version: 0.81-47

Apitrace file(s)

Failed to run apitrace on crysis.exe

The latest Vulkan beta drivers have a fix for that which hasn't made it into the stable branch yet.

@K0bin I see, since I'm using proprietary drivers I don't think I can test that, but if this is true then I'm sure glad to hear it'll get fixed soon.

@Rabcor We are talking about proprietary here. Just a different branch. 410.57 doesn't have the fix. 396.54.06 and 396.54.09 (released today) both have it.

Ah, so it's an nvidia specific issue then?

Indeed. And since 410 series is behind on the vulkan side, it's only been fixed in the vulkan beta drivers as of yet.

It seems that I'm going to have to just wait on the driver update; getting the beta drivers installed on manjaro is a lot harder than it should be.  I hope it won't be too long before the 410 series catches up...

@Rabcor You can give my PKGBUILD a try : https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-dev-all
I just confirmed it to work on Manjaro.

I have confirmed, the nvidia beta driver solved the issue.


Install packages via custom URI handler

I believe we casually discussed this in person or in Chat, but I couldn't find a follow-up issue. I think it would be really excellent. In the meantime we can work around on the site with instructions for install through the editor or CLI, but that's a bit clunky.

Closing in favor of #5262 which is more detailed.


Add quotations to arguments with blank spaces when executing kernel processes

For #4647

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #5201 (a027142) into main (d99989e) will increase coverage by 0%.
The diff coverage is 60%.

@@          Coverage Diff          @@
##            main   #5201   +/-   ##
=====================================
  Coverage     73%     73%
=====================================
  Files        402     402
  Lines      26403   26407    +4
  Branches    3799    3800    +1
=====================================
+ Hits       19432   19451   +19
- Misses      5403    5479   +76
+ Partials    1568    1477   -91

Impacted Files
Coverage Δ

...lient/datascience/kernel-launcher/kernelProcess.ts
79% <60%> (-1%)
:arrow_down:

...lient/datascience/jupyter/kernels/cellExecution.ts
77% <0%> (-1%)
:arrow_down:

...datascience/notebookStorage/nativeEditorStorage.ts
80% <0%> (-1%)
:arrow_down:

src/client/datascience/notebook/helpers/helpers.ts
76% <0%> (-1%)
:arrow_down:

src/client/datascience/webviewExtensibility.ts
72% <0%> (ø)

src/client/datascience/jupyter/jupyterExporter.ts
73% <0%> (ø)

src/client/datascience/commands/commandRegistry.ts
40% <0%> (ø)

...client/datascience/raw-kernel/rawJupyterSession.ts
68% <0%> (ø)

...lient/datascience/notebookStorage/notebookModel.ts
82% <0%> (ø)

...ient/datascience/interactive-ipynb/nativeEditor.ts
70% <0%> (ø)

... and 22 more


Fixed context not up to date in createFormValues

This fixes the problem described in #3202

Codecov Report

Merging #3203 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3203   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          68      68
  Lines        1507    1507
======================================
  Hits         1507    1507

Impacted Files
Coverage Δ

src/createFormValues.js
100% <100%> (ø)
: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 8c6f4a2...f0e954f. Read the comment docs.

Published in v7.0.1.


Feature Request: Job Timeout

Hi,
Sometimes a job is depend on other external and third-party libraries/devices and can be freeze forever because of a link/hardware failure or network error.
But i can compute a rational and reasonable runtime for it, as an example, 20 mins. if the job don't return any result/exception it might be considered as Not Responding so it need a hard restart.
it would be nice to have a timeout property for each job, something like:
scheduler.add_job(
            _job,
            trigger=CronTrigger(minute="*/1"),
            timeout=Timeout(timedelta(seconds=360), TimeoutAction.[HardReset, ForceStop, Delete, ...]),
            ...
        )

Thanks

django-apscheduler is just an APScheduler job store and does not control the actual running of APScheduler jobs.
You probably want to submit this feature request upstream, or look at combining APScheduler with a more full featured background task processing library like Dramatiq (which does cater for runtime timeouts).


trufflehog: 3.63.0 -> 3.63.1

Diff: https://github.com/trufflesecurity/trufflehog/compare/refs/tags/v3.63.0...v3.63.1
Changelog: https://github.com/trufflesecurity/trufflehog/releases/tag/v3.63.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 269050 run on x86_64-linux 1

1 package built:

trufflehog


Using FeedParser causes incompatibility with Python 2.3

From<EMAIL_ADDRESS>on November 04, 2013 04:57:59
Because of importing email.FeedParser, the library is incompatible with Python 2.3 which is still declared as supported.
Tested with Python 2.3.5 on Windows 7. According to Python documentation, FeedParser is a new feature in Python 2.4, so it probably wouldn't work on any platform.
I would recommend either to use email.Parser instead, or drop the compatibility with Python 2.3.
Original issue: http://code.google.com/p/httplib2/issues/detail?id=298

Just support 2.6+ it makes a lot more sense now and simplifies supporting 2 and 3.


War of Numbers #235

Description
Created a function war_of_numbers
Issue No.- #235

Type issue number after hash(#)

Checklist

[x] Yes, this task assigned to me.
[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My Filename is in camelCase format
[x] I have added Problem statement, Problem link in file.

Missing and wrong issue number, Marking it as spam


Release v6.0.3

v6.0.3 (10/07/2020)
Enhancements:

Enable importing from FA backend local snapshots.
Add hostname/FQDN support on platform9
Add REST API 2.x support
Fix NFS mount 4.1 to 3.0 rollback on client-side for FB NFS volume.
Optimization by reducing the number of RESTful API calls
Fix the bug cockroach operator creates more pods than needed

Are we going to include the cockroach resource limits exposure as discussed??

@sdodsley Are you talking about the memory leak issue? I remember a fix was reversed, so I didn't included. Is there a new fix included in the code? (I remember David wanted to modify something in values.yaml to set a limit for this.)

It's not a leak, but a bad implementation that needs fixing. As it's relatively simple we should wait and include in this release

As I mentioned in the team channel. Users today can rein them memory using database.resources.memory.limits in values.yaml. We can do another enhancement to expose the default values (--cache .25 --max-sql-memory .25), which is hard-coded in the cockroach-operator today, but I don't think it urgent to do so. We can do in the next release. IMHO, the release is good to go, we just need to have a full/successful CI test.

Aslo, what is this one, @DIMPLY ?

Optimization by reducing the number of RESTful API calls

These database resource limits need to be documented then.

@dsupure I originally put it as "En’s fix for the TestAttachAndDetachStorm" according to our Slack discussion, but it's actually reducing all rest api calls, not only for TestAttachAndDetachStorm. TestAttachAndDetachStorm just happens to put more loads on the REST server.


Document the cert pooling bug

Hi there.  I just ran into https://github.com/kennethreitz/requests/issues/2863 and spent a lot of time trying to figure out what was wrong.  It would be really nice for future people who might encounter this bug to be informed up front, so here is a note to add to the User Guide and the API documentation.
I understand that people are working on fixing this bug, but it's not fixed yet and it's been open for about 6 months.  I think it's valuable to make this quick change to the docs in the meantime, and then when the bug is fixed we can remove these warnings.
Thanks!

Thanks for this suggestion! However, I don't think the proposed documentation change is good: in fact, I think it is dangerously misleading. The bug occurs regardless of how cert is set: so long as it has been set and a session is being used it is possible for it to be effectively incorrectly set.
However, I also think there is no urgency to document this. A fix has been merged into urllib3 (shazow/urllib3#830), and a new urllib3 release will be out in the next few weeks. I doubt this will remain unfixed for more than another few weeks.

Thanks, I didn't know a fix was imminent.  I'm looking forward to it!
I don't understand what's wrong with the advice to set cert immediately on creation and never changing it—only asking for clarification in case it means I don't understand what the bug is.  If you set cert before making any requests and never change it, then how can you encounter the bug?

Nothing's wrong with that advice: it's just not what your documentation says. =) Your documentation change says don't use it at all, which is not necessarily right.
You're right though: if you set cert before using the Session and never want to change or override it, you won't hit the bug.


Make the API easy to use without macros.

I received the feedback that abusing custom syntax can be intimidating, and make it hard to understand what is happening under the hood. As a general rule of thumb I think that It's best for an API to be easily usable without macros and then on top of that optionally provide some macros to provide extra ergonomics for those who want it.
Let's follow this rule for defining and registering scripts and classes.

The manual class class registration code is new on par with the godot_class macro.


[PE-D][Tester A] 'Clear' commands clear everything immediately after user input 'clear'

Would it be better if the user got a clear confirmation message asking them if they really wanted to clear all data? That might help guard against users who accidentally input the 'clear' command.

Labels: severity.Medium type.FeatureFlaw
original: Choonyan02/ped#1

My suggestion to this is we remove this feature, as it is not a planned feature by us, rather inherited from AB3.
Reasoning:
Considering the case where users will actually clear the whole address book is relatively rare, I think this feature is less important. On top of that, we can include in our UG on how to clear the address(by manually polluting the data file) so that when they plan to do so, they got workarounds.

I agree to remove, but do we allow to remove feature in v1.4?

Will be including this in planned enhancements


Question: Showing a full source code of component

Question
Have a look at current docs site. There is an interactive MobX example made as a component and wrapped into Playground. Right below it is some copy of that source file. It's somewhat hard to maintain both versions if I need to change something there.
The current Playground's function to show source code feels fairly useless as it shows only what's in the MDX, not the source of the component.
One way would be adding a link directly to GitHub source, but that's fairly awkward, I would like people to stay on the site.
So I am thinking if I can somehow prepare a plugin similar to the Playground, but it would have a tight connection to a source file and show it inline when the user toggles the button (or show it open initially).

it might be easier than you guys think:

Install raw-loader
Use it

import source from '!raw-loader!test.mdx'
<editor>{ source }</editor>

The only way I could make it work is like this
create a symbolic link to the source code file as ".txt"
import source from '!!raw-loader!whatever.txt' //the double !! at the beginning matter or else you will see the compiled code
<editor>{ source }</editor>

@xaviergonz yeah I don't know why I worked for me with just !, either webpack's behavior changed or I just forgot it. Anyway, if you already override the configured loader then there is no need to symlink.


BVAL-554 Add the ability to generate a single asciidoc file containing all the specification

https://hibernate.atlassian.net/browse/BVAL-554

I added a pom file so that it's possible to quickly import the asciidoctor extensions in Eclipse.

Nice, thanks! I'll play around a bit with it tomorrow.

Looks like this one can be closed.


Folders uploaded to HyperThought are hanging and not finishing.

The upload is probably getting hung up on these particular folder names with dots and right parentheses.

Fixed in release 1.0.1.


Exclusion Report | Gov Analyst Recommend Acceptance |1|

Story:
As a Government Analyst, I want to be able to recommend acceptance of an exclusion report.
Scenario:
GIVEN that I am an IDIR user
AND I have the Government Analyst role
AND I am viewing a submitted Exclusion Report (i.e. status = Submitted)
AND I am on the Exclusion Agreements page
WHEN I click on the Recommend Acceptance button
AND I accept the confirmation alert
THEN I am returned to the main compliance reporting page
AND the status of the report in the UI changes to Reviewed - Analyst (back-end status should be "Recommended Acceptance - Analyst")
AND a report history record is created (see below)
AND a system alert appears on the screen
Status update visibility:

The status change should only be visible to IDIR users. For BCeID users, the status should remain at Submitted.

Report History Record:
A report history record should be created when the Gov't Analyst recommends acceptance of the report. The format should be as follows:

Reviewed and <Status> on Month DD, YYYY by <First, Last Name> of <Organization Name>
Example: Reviewed and Recommended Acceptance on March 31, 2019 by Justin Lepitzki of Government of British Columbia

Note: This report history record should only be visible to IDIR users.
Confirmation Alert Messaging:

Are you sure you want to recommend acceptance of the exclusion report?

System Alert Messaging:

Acceptance Recommended

https://trello.com/c/sJLrjyOc/1686-exclusion-report-gov-analyst-recommend-acceptance-1

 Exclusion Report | Gov Analyst Recommend Acceptance |1|

resolved in sprint vulcan


advertised.listeners is not set EXTERNAL_INGRESS when Kafka instance with external NodePort service exposed

Hi guys,
reference the doc: https://github.com/kudobuilder/operators/blob/master/repository/kafka/docs/latest/external-access.md
I installed a Kafka instance with external NodePort type service exposed in my k8s cluster.
-p EXTERNAL_ADVERTISED_LISTENER=true \
-p EXTERNAL_ADVERTISED_LISTENER_TYPE=NodePort \

I exec to the kafka pod inside and check the server.properties as below:
kafka@kfk-x102-kafka-0:/opt/kafka$ cat server.properties | grep listen
listeners=INTERNAL://<IP_ADDRESS>:9093,CLIENT://<IP_ADDRESS>:9092
advertised.listeners=INTERNAL://kfk-x102-kafka-0.kfk-x102-svc.x102.svc.cluster.local:9093,CLIENT://kfk-x102-kafka-0.kfk-x102-svc.x102.svc.cluster.local:9092
listener.security.protocol.map=INTERNAL:PLAINTEXT,CLIENT:PLAINTEXT
inter.broker.listener.name=INTERNAL

Expected:
EXTERNAL_INGRESS is configured as below(example from above reference):
advertised.listeners=INTERNAL://kafka-kafka-2.kafka-svc.default.svc.cluster.local:9093,EXTERNAL_INGRESS://<IP_ADDRESS>:30904

Any mistake or misconfiguration I make here? could you please help.
Thanks a lot!

@walk1ng thanks for the issue, can you please provide the KUDO and KUDO Kafka versions?

@walk1ng thanks for the issue, can you please provide the KUDO and KUDO Kafka versions?

Version information:
KUDO Version
version.Info{GitVersion:"0.13.0", GitCommit:"900ca042", BuildDate:"2020-05-14T18:23:50Z", GoVersion:"go1.14.2", Compiler:"gc", Platform:"darwin/amd64"}
Operator version
kafka-1.3.0
zookeeper-0.3.0
App version
kafka 2.5.0
zookeeper 3.4.14

versions seems correct, and it's working as for me but that depends on the kubernetes distro also
can you verify if the node has an external-ip?
kubectl get nodes -o wide should be enough to verify that and <IP_ADDRESS> should be listed there
other things that might help is to check if plans are complete
 kubectl kudo plan status --instance=kafka-instance

the external access via nodeports works in KUDO Kafka by using a clusterrole that let the KUDO Kafka get the nodes information and fetch their external-ip.
if external IP is there you can verify the clusterrole is created correctly
kubectl get clusterrole kafka-instance-clusterrole -o yaml

@walk1ng can you test by updating the instance with -p EXTERNAL_ADVERTISED_LISTENER=false and enable it again?
kubectl kudo update --instance=kafka-instance  -p EXTERNAL_ADVERTISED_LISTENER=false

kubectl kudo update --instance=kafka-instance  -p EXTERNAL_ADVERTISED_LISTENER=true

it could be an issue with deploy plan

-p EXTERNAL_ADVERTISED_LISTENER=false

versions seems correct, and it's working as for me but that depends on the kubernetes distro also
can you verify if the node has an external-ip?
kubectl get nodes -o wide should be enough to verify that and <IP_ADDRESS> should be listed there
other things that might help is to check if plans are complete
 kubectl kudo plan status --instance=kafka-instance

the external access via nodeports works in KUDO Kafka by using a clusterrole that let the KUDO Kafka get the nodes information and fetch their external-ip.
if external IP is there you can verify the clusterrole is created correctly
kubectl get clusterrole kafka-instance-clusterrole -o yaml

my node has not an external-ip, does it the reason I met the problem?
and I checked the deploy plan is COMPLETE.
the clusterrole related my Kafka instance is created.

my node has not an external-ip, does it the reason I met the problem?
yes @walk1ng, to have any external-access through nodeport it goes through the kubernetes node external-ip

my node has not an external-ip, does it the reason I met the problem?

yes @walk1ng, to have any external-access through nodeport it goes through the kubernetes node external-ip

question:
I haven't find the related script or code to add/generate EXTERNAL_INGRESS://IP:NODEPORT for advertised.listeners property in file server.properties if my node have external-ip and I install Kafka with params as below:
-p EXTERNAL_ADVERTISED_LISTENER=true \
-p EXTERNAL_ADVERTISED_LISTENER_TYPE=NodePort \

could you please figure out?
my purpose is create a Kafka cluster with NodePort type services exposed in my k8s, and my apps or users inside of my k8s cluster can access the Kafka and use it.
how can I achieve it with KUDO Kafka operator?
thanks a lot!

@walk1ng have you tested what I posted above?
https://github.com/kudobuilder/operators/issues/267#issuecomment-634632457
There might be an issue that we need to fix around first time deploys the PR is open https://github.com/kudobuilder/operators/pull/268

@walk1ng have you tested what I posted above?
#267 (comment)
There might be an issue that we need to fix around first time deploys the PR is open #268

hi zmalik,
I saw your fix had been merged into master.
I tested it follow your comment, firstly update EXTERNAL_ADVERTISED_LISTENER=false then update EXTERNAL_ADVERTISED_LISTENER=true, I saw the plan external-access is COMPLETE.
below is snippet about advertised.listeners in kafka pod.
kafka@kfk-xyz-kafka-0:/opt/kafka$ cat server.properties | grep listen
listeners=INTERNAL://<IP_ADDRESS>:9093,CLIENT://<IP_ADDRESS>:9092
advertised.listeners=INTERNAL://kfk-xyz-kafka-0.kfk-xyz-svc.xyz.svc.cluster.local:9093,CLIENT://kfk-xyz-kafka-0.kfk-xyz-svc.xyz.svc.cluster.local:9092
listener.security.protocol.map=INTERNAL:PLAINTEXT,CLIENT:PLAINTEXT
inter.broker.listener.name=INTERNAL

my question is that, if my k8s node has not external-ip configured(I am not the administrator of k8s cluster), any work around to let NodePort service exposed and work?(cannot use loadbalancer also)
thanks for your help and patiences.

I saw your fix had been merged into master.

it's not yet released, and we will release in upcoming days, as for now the workaround is https://github.com/kudobuilder/operators/issues/267#issuecomment-634632457 for the first time deploys to force the detection of external-ip again

my question is that, if my k8s node has not external-ip configured(I am not the administrator of k8s cluster), any workaround to let NodePort service exposed and work? (cannot use loadbalancer also)

How are any services in the cluster exposed outside the kubernetes cluster? I'm afraid that you would need to fix that part before focussing on Kafka itself.

Cloud i fix it by get the ip value use "internal ip" ?  in private network in company, internal ip is safe  too.

could you figure out where
Line#95 to #110 from https://github.com/kudobuilder/operators/blob/master/repository/kafka/operator/templates/bootstrap.yaml

I saw your fix had been merged into master.

it's not yet released, and we will release in upcoming days, as for now the workaround is #267 (comment) for the first time deploys to force the detection of external-ip again

my question is that, if my k8s node has not external-ip configured(I am not the administrator of k8s cluster), any workaround to let NodePort service exposed and work? (cannot use loadbalancer also)

How are any services in the cluster exposed outside the kubernetes cluster? I'm afraid that you would need to fix that part before focussing on Kafka itself.

hi,
could you please figure out where is the code to create/generate the two files: /opt/kafka/external.listeners and /opt/kafka/external.advertised.listeners in kafka pod?
the two files is not existed in kafka pod when my kafka installed done.
from line#95 to line#110 in https://github.com/kudobuilder/operators/blob/master/repository/kafka/operator/templates/bootstrap.yaml
it read configurations ADVERTISED_LISTENERS and LISTENERS from the two files I mentioned above, but get nothing because the two are not exists in pod.
I think it's the reason why the config file server.properties is missing my required settings advertised.listeners and listeners about expose kafka cluster externally with NodePort.

@walk1ng the logic is in the docker image https://github.com/mesosphere/kudo-kafka-operator/tree/master/images/kafka
and it works when there are external-ip attached to the service. can you please post the logs any Kafka pod? specially the first few lines when its trying to detect the service's external-ip

Cloud i fix it by get the ip value use "internal ip" ? in private network in company, internal ip is safe and accessible too.

It would work with any IP that the kubelet gets assigned. Please read https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-services/#ways-to-connect
Kafka or any other operator cannot do much here if the cluster isn't accessible.

@walk1ng closing this issue as advertised.listeners is working with EXTERNAL_INGRESS when kubelets have external IP addresses.


You get disconnected from emp run when a lot of output is generated

The remote connection will die with an error message like this:
attaching to container (e413a2f40b7de61f84839a7b8fd0d52f3b25997f80afcf3c7c2eee6eea2af305): InvalidParameterException: Upload too large: 1049218 bytes exceeds limit of 1048576
                               status code: 400, request id: ed318bff-1116-11e8-beegoku :: ~/remind/r101-api ‹16b3fe1› »

Reproducible if running commands with a lot of output, or smth likewhile true ; do ; find / ; done.  It's a bit jarring to have the session suddenly die. You've gotta log back in and get back into the interactive context you were in, and be really careful about the output you're generating. And if you mess up and generate too much output, you have to do it again.
Is there any way empire can be more resilient to running commands with a lot of output remotely?

To clarify the issue above, this can happen when Empire is configured to forward logs from attached containers to CloudWatch. There's a lot of ways that CloudWatch logs forwarding can fail (throttling, messages too big, stream too big, etc).
When we originally discussed implementing this, we agreed that failing closed would be best for security, so containers would die if logs couldn't be forwarded. I can see how that would get annoying pretty quickly in the case above.
We could potentially provide a flag to ensure that CloudWatch logs failures don't effect the session, which would be pretty easy to do.

just had this happen to me again :(


Update 0118, subscribers clarified and 2 ways to verify mappers

Waiting on @zer0tweets for 👍

This is a Zerotweets 👍🏻
He just did it discord not here

I confirm here as well =).


Enhanced_tilemap Plugin for Kibana 5.4.2

Hey Guys,
We want to use this plugin in one of the cluster which is running on Kibana 5.4.2 (upgrade not possible at present). Unfortunately, I din found any release for Kibana 5.4.2. It will be really nice if we can get the plugin for version 5.4.2 :smiley: .
Cheers, Ankit

5.4 is supported in with release https://github.com/nreese/enhanced_tilemap/releases/tag/v2017-09-23. Just change the version in package.json to 5.4.2

Hey Nathan,
Thanks for the reply :smiley: . I tried today what you asked but unfortunately it doesn't seem to help. I don't see the version incompatible error anymore, as I was seeing before, and kibana also says that the installation completed but seems like there is a problem.
Following are the execution logs:
`
root@testdwm-046 /usr/share/kibana/bin # ./kibana-plugin install http://<SERVER_ADDR>/pumosw/enhanced-tilemap-v2018-03-16-5.4.2.zip
Attempting to transfer from http://yum.dilax.com/pumosw/enhanced-tilemap-v2018-03-16-5.4.2.zip
Transferring 6432602 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Optimizing and caching browser bundles...
Plugin installation complete
root@testdwm-046 /usr/share/kibana/bin # ./kibana-plugin list
/usr/share/kibana/src/cli_plugin/list/list.js:26
throw new Error('Unable to read package.json file for plugin ' + filename);
^
Error: Unable to read package.json file for plugin enhanced_tilemap
at forEach.e (/usr/share/kibana/src/cli_plugin/list/list.js:26:15)
at Array.forEach (native)
at list (/usr/share/kibana/src/cli_plugin/list/list.js:13:44)
at Command.processCommand (/usr/share/kibana/src/cli_plugin/list/index.js:38:22)
at Command. (/usr/share/kibana/src/cli/command.js:93:20)
at Command.listener (/usr/share/kibana/node_modules/commander/index.js:301:8)
at emitTwo (events.js:106:13)
at Command.emit (events.js:191:7)
at Command.parseArgs (/usr/share/kibana/node_modules/commander/index.js:610:12)
at Command.parse (/usr/share/kibana/node_modules/commander/index.js:458:21)
at Object. (/usr/share/kibana/src/cli_plugin/cli.js:54:9)
at Module._compile (module.js:570:32)
at Module._extensions..js (module.js:579:10)
at Object.require.extensions.(anonymous function) [as .js] (/usr/share/kibana/node_modules/babel-register/lib/node.js:152:7)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
´
When I tried looking inside the plugins directory, I see an empty folder with the name of the plugin /usr/share/kibana/plugins/enhanced_tilemap.
Following is the content of the Json file post modification :
{   "name": "enhanced_tilemap",   "version": "5.4.2",   "scripts": {     "test": "gulp test"   },   "devDependencies": {     "babel-core": "6.22.1",     "babel-preset-es2015": "6.22.0",     "babel-register": "6.22.0",     "chai": "3.5.0",     "gulp": "3.9.1",     "gulp-mocha": "3.0.1",     "jsdom": "9.9.1",     "jsdom-global": "2.1.1"   } }
Can you maybe think of a possible explanation of this behavior?


DevDrive: Windows cannot deploy to path AppX of file system type ReFS

Describe the bug
Testing a .NET MAUI app out with the new Windows DevDrive, there is an error while trying to deploy and debug the app from Visual Studio:
DEP0700: Registration of the app failed. [0x80073CFD] Windows cannot deploy to path AppX of file system type ReFS.

This seems intentionally blocking, however given MAUI's use of multitargeted projects, this effectively means we cannot use DevDrive without some workaround.
Steps to reproduce the bug

File New MAUI App project
Save the project to a DevDrive (or otherwise ReFS partition)
Debug the Windows app

Expected behavior
Expected to be able to deploy and debug
Screenshots
No response
NuGet package version
None
Packaging type
Packaged (MSIX)
Windows version
Insider Build (xxxxx)
IDE
Visual Studio 2022-preview
Additional context
NuGet version is 1.3.230331000
If it's not possible to make this supported, we need to come up with some workaround to deploy to a non-ReFS partition if the MAUI project exists there.

This is also blocking WinUI, UWP, packaged Win32 and Win32 app isolation development, making dev drives useless for those cases.

Update with a bit more info...
Apparently this only happens if you access the DevDrive from a mapped folder.
For instance i have created a DevDrive partition as X:\.  If I load my project from X:\MyProject\MyProject.csproj, using packaged apps works fine for deploy and debug.
But there's also an option to map the DevDrive to a folder elsewhere, so I have D:\code\ mapped to it... I can access files from either X:\ or D:\code\ just fine but it seems the D:\code\ folder appears as 'removable' to windows and is not allowed for appx deployment.

As a workaround, you can set the LayoutDir MSBuild property in your project to a path on a drive that is not formatted with ReFS to tell VS to deploy the folder layout to different location.

All of my non-OS drives have been ReFS, i can debug my WinUI3/C#/MSIX packaged app from ReFS drives without any problems.
I use the latest Windows 11.
Installing MSIX from ReFS also works just fine.

@manodasanW  - I believe this bug was fixed back in fall 2023, either Windows 11 Sept 2023 release or at least Windows 11 23H2.


Over/Out Events

Added Over/Out events

I changed the names you suggest from enter/leave to over/out since I felt they made more sense. For instance the moment I start dragging an element it has really entered its container but it is over a droppable target and when I drop on a target to me out more represents there is no currently dragging item that is in a position to be dropped, which is why I also had the cleanup function emit out as well.

Sounds good to me. Please add the relevant documentation. Thanks

Do you need me to make those changes in the PR code or are you?

Yeah please do

OK, let me know if that covers everything. Not sure if documentation is just updating that read.markdown and I hit all the areas necessary.

Perfect, one last detail, squash your commits. You can do:
git reset HEAD~3
git commit -am "Added over/out events"
git push --force

Sorry man, I did this all through github site. How do I execute those commands using the website? I never pulled my fork down to my local, made my changes there and used command line to push them back.

Hey I think I got those commands to run. Let me know if everything is good.

I refactored what you did a little and added a demo. It's in release 2.1.0

Sweet. Thanks!


S3 code storage: keys authentication

Implement accessKeyID and accessKeySecret in the s3 code storage.
It would be nice to also being able to load the accessKeySecret from a existing secret

Done


Where's The BetterDiscord Setting In Setings

It Cant Be!!!

I install Better Discord And Where is It

look at faq question 2 in the betterdiscord server


Always use automatic jsx transform

Heya! First of all, thank you for maintaining resium! We've used it in a couple of prototypes and it has worked out well for us, and we are looking forward to using it more.
We have run into a small problem with our latest project. While the proposed change fixes our problem, I can't say I fully understand what is happening. Here is the situation:

We are building a js library that among other things offers cesium visualizations.
Just like resium, our library is compiled using vite in library mode. cesium, react and react-dom are also treated as externals and are provided by host applications. Our configurations are exactly the same in that regard.
We use the react vite plugin without custom options, and by default is uses the automatic jsx transform
When we package our library, the resium.mjs file is transformed again by vite (which seems normal to me)

This is where things get interesting.
classic transform
We get the following error when using our library: ReferenceError: React is not defined. It traces back to this line in resium but I believe it's unrelated to the line itself, it's just that this is the first call to a React function when we are using resium.
In resium.mjs, the output is as follows
import k, { createContext as ge, etc… } from "react";

return h ? /* @__PURE__ */ k.createElement(x.Provider, {
      value: h
    }, s) : s;

and inside our library compiled code
import React__default from "react";
…
return h2 ? /* @__PURE__ */ React.createElement(x$2.Provider, {
      value: h2
    }, s2) : s2;

Note that k.createElement gets transformed into React.createElement — but React is not present in the global scope.
automatic transform
If resium uses automatic transform mode (eg. what this PR proposes), the output is
In resium.mjs
import ai, { createContext as Gi, etc } from "react";
…
return E ? /* @__PURE__ */ le(Le.Provider, {
      value: E,
      children: f
    }) : f;

Note that it uses le and not ai. le in the compiled source points to the react jsx transformed that is now shipped along.
In our library
import React__default from "react";
…
React__default.createElement(me$1.Provider…

The code is transformed again, but this time the resium dependency to react is treated like all the others we have in our code, it gets mapped to an import from "react", and the host application will have to deal with that since it's a dev dependency.

In summary, I think this is an edge case where if resium is compiled again in a context where react is not present (because it's an external), the classic transform mode has as consequence that resium expect React to be present as a global variable, as a fallback. With the new automatic transformer this is not the case.
While I'm confident that the PR fixes our issue, I don't know what other consequences it could have, especially on the umd version of the package.
Was there any specific reason to use the classic transformer for production?

Hello, has anyone from your side had time to look at this? Anything I could do to help with the process?

Thank you for PR. I will check it soon!

Hello, not to guilt-trip you but any chance you could take a look at this soon?

Oh sorry, I just saw that the change has been integrated into the main branch! Great, thank you!

One more update from me: would it be possible to publish a new version of resium with this fix please?


Bump @astrojs/react from 3.0.5 to 3.0.6

Bumps @astrojs/react from 3.0.5 to 3.0.6.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: "@astrojs/react" dependency-type: direct:production update-type: version-update:semver-patch ...

#184

Wtf


Error with OneSignal initialization

I want initialize OneSignal on all pages of my web application as some js function in other file instead code on cshtml page.
When I try to use it as code on page, it's working. Here is code from _Layout.chtml in  tags (as in OneSignal Documentation):
<link rel="manifest" href="/manifest.json">
<script src="https://cdn.onesignal.com/sdks/OneSignalSDK.js" async></script>
    <script>
        var OneSignal = OneSignal || [];
        OneSignal.push(["init", {
            appId: " *** " ,
            autoRegister: true,
            notifyButton: {
                enable: false
            }
        }]);
    </script>

And now I editing code like this:
<link rel="manifest" href="/manifest.json">
<script src="https://cdn.onesignal.com/sdks/OneSignalSDK.js" async></script>
<script src="~/js/Push.js"></script>
  <script>
        OneSignalInit();
  </script>

Here is my Push.js:
function OneSignalInit() {
    $.getScript("https://cdn.onesignal.com/sdks/OneSignalSDK.js", function (data, textStatus, jqxhr) {
    });
    var OneSignal = OneSignal || [];
    OneSignal.push(["init", {
        appId: " *** ",
        autoRegister: true,
        notifyButton: {
            enable: false
        }
    }]);
};

But it doesn' work. Thank you for any help!

Are you sure if you filed this in the right place? :smile:

Yup, of course, because its working when i place code in Layout.

@deeplydippy Your example is javascript code above, and you mention OneSignal. I don't understand how this is related to ASP.NET. Are you saying that this exact JS snippet works on a non ASP.NET app, and fails with ASP.NET?

Probably, I incorrectly formulated my question. When I placing this JS snippet on  a ASP.NET app in cshtml page (_Layout.cshtml), it works. And now on the same ASP.NET app I create function OneSignalInit() in Push.js, which calling at the same place. And its not working. Thank for help!

@deeplydippy Sorry, I'm still confused (about how this is related to ASP.NET). What's not working exactly?  Looks like a JS issue to me. Could you use the browser developer tools to see if your JS file is loaded?

@deeplydippy
Your problem is likely here:
$.getScript("https://cdn.onesignal.com/sdks/OneSignalSDK.js", function (data, textStatus, jqxhr) {     });
Your callback function contains no code.  Keep in mind that $.getScript is an asynchronous method, so it will return immediately before OneSignal has been loaded from the server.  You should move the contents of
var OneSignal = OneSignal || [];
    OneSignal.push(["init", {
        appId: " *** ",
        autoRegister: true,
        notifyButton: {
            enable: false
        }
    }]);

inside your callback method in getScript.  Also keep in mind that anything else on your page may have to wait for OneSignal to be loaded before they will be able to use it.

Thank you!


docs: Timeouts in ClientTrafficPolicy

Description:

Describe the issue.

relates to https://github.com/envoyproxy/gateway/issues/2598
[optional Relevant Links:]

Any extra documentation required to understand the issue.

cc @yaelSchechter


Reset rotation field when changing schema in UI

Ref: #334

ref #336

Hi @LeandroBanaszeski, thanks for the contribution!
Would you mind please opening separate PRs for the separate issues that you have contributed to?
One is a bug fix and the other is a new feature so it's easier to get them merged if they're not dependent.
Thanks!

Hi, I don't have much experience in PRs, this is the first time I've done
it. I realized that it hadn't turned out the way I wanted. How can I fix
this, could you help me?
Em dom., 26 de nov. de 2023 às 07:02, Peter Ward @.***>
escreveu:

Hi @LeandroBanaszeski https://github.com/LeandroBanaszeski, thanks for
the contribution!
Would you mind please opening separate PRs for the separate issues that
you have contributed to?
One is a bug fix and the other is a new feature so it's easier to get them
merged if they're not dependent.
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/pdfme/pdfme/pull/335#issuecomment-1826740495, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5SDVFMDPIGMHK6Y4RDXKDYGMHU5AVCNFSM6AAAAAA72RTB5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWG42DANBZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

--


Dev

longhorn/longhorn#6191

@shuo-wu the commit subject looks weird. Please help correct it. Thanks.


'scenario_test_runner' doesn't work with Autoware

Describe the bug
I installed scenario simulator v2 and autoware.universe on Ubuntu 22.04 with ROS2 humble.
All the installation and build procedures are successful.
When I started the scenario_test_runner. It seems failed: 'AutowareError: Simulator waited for the Autoware state to transition to WaitingForRoute, but time is up. The current Autoware state is INITIALIZING.'
Full log
run_3.txt
run_2.txt
run_1.txt
Expected behavior
I'm waiting for the scenario simulation to run with Autoware.
Screenshots
scenario:='/home/arge01/Downloads/scenerios/lanelet2_map/success/crosswalk_v2.yaml

Desktop (please complete the following information):

Ubuntu Version 22.04
ROS 2 Version Humble
Cyclone DDS

@halilsenaydin Could you provide the version of Autoware you used?

Branch: release/2024.04

@halilsenaydin Could you provide the version of Autoware you used?

@hakuturu583  I am using,
Branch: release/2024.04

Could you try with
ros2 launch scenario_test_runner scenario_test_runner.launch.py architecture_type:=awf/universe/20230906 record:=false scenario:='$(find-pkg-share scenario_test_runner)/scenario/sample.yaml' sensor_model:=sample_sensor_kit vehicle_model:=sample_vehicle

Unfortunately this doesn't work. I am started it the Autoware workspace and the script _v2 workspace. Both return errors.
bug-1.txt
bug-2.txt

[openscenario_interpreter_node-3] [WARN] [1716667180.184187593] [simulation.openscenario_interpreter]: Your machine is not powerful enough to run the scenario at the specified frame rate (30 Hz). We recommend that you reduce the frame rate to 4.52489 or less.

In this log, warnings like this are remians.
This warning means your computer is not powerful enough.
Could you try with more powerful computer?


Install jekyll-paginate along with jekyll.

A lof of Jekyll users will need jekyll-paginate, so add it to the dependencies.

The plugin seems to be discontinued. I have no strong opinion on whether to include it or not, but ideally we would have an easy way to add plugins..

The "discontinued" plugin is misleading, it's still the official way to do pagination:
https://jekyllrb.com/docs/pagination/
Also, it's installed on github pages.

Pushed to master. Thank you. Please observe the contribution guidelines in the future.


ImageView border not appearing in design view.

Hello. I wanted to report that the view's border is not visible if previewed in the design tab of Android Studio 2.2. The view works fine in devices.

It actually works for me in AS 2.2. Can you provide more details and try with the sample project?

Don't really know what to add. The preview works (it shows the image) but the circle around it is not visible. If I launch the app without chaning any code it is visible.
screen
source code
Right now I set it white since I like it more.

i can not set border for my image in this component when i used it in navigation drawer

I haven't had any issue like that with any version of Android Studio. Upgrading AS to the latest version and cleaning the project should solve problems like this. Closing this as there's no issue with the library itself.


use setuptools.Extension

Codecov Report

Merging #235 (7bf59f9) into master (60c48e9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #235   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines         2097      2097
=========================================
  Hits          2097      2097

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 60c48e9...7bf59f9. Read the comment docs.


Optional URI::Generic#to_s redefinition

Think the URI::Generic#to_s could be problematic for some users if they are already relying on the original implementation.
People using the gem directly should be fine but this is an excellent gem to be used as a dependency for other gems, so having this redefinition happening indirectly could trigger some confusing behaviors.
That being said, I love the output of the new #to_s so I would suggest either making the redefinition module optional, and adding instructions on how to load it, or creating a custom method #cooler_to_s like 😆
I know that the overall redefinition could add some value to indirect/inner usages of #to_s, so the optional module might be a better approach to it.
Happy to help if you find any of these options interesting.
Cheers,
Roberto

The purpose of overriding #to_s is to allow setting the query_params then dumping out the formatted URL.
uri = URI("https://example.com/path")
uri.query_params['foo'] = 'bar'
puts uri
# https://example.com/path?foo=bar

Since query_params is a plain Hash, there's no way of automatically updating query when a param is added, changed, or removed. Maybe in the future we could create our own smart-Hash that updates the parent URIs query each time it's modified?

Oh, gotcha, I love that idea.
Feel free to close this one. Just wanted to share my thoughts on that
monkey patch.
On Wed, 22 Dec 2021 at 02:49, Postmodern @.***> wrote:

The purpose of overriding #to_s is to allow setting the query_params then
dumping out the formatted URL.
uri = URI("https://example.com/path")uri.query_params['foo'] = 'bar'puts uri# https://example.com/path?foo=bar
Since query_params is a plain Hash, there's no way of automatically
updating query when a param is added, changed, or removed. Maybe in the
future we could create our own smart-Hash that updates the parent URIs
query each time it's modified?
—
Reply to this email directly, view it on GitHub
https://github.com/postmodern/uri-query_params/issues/6#issuecomment-999219154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAASUW624RF5DCHG274D5QDUSEVBRANCNFSM5KQE2IEA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards,
Roberto Decurnex

Oh I also realized that a fake Params Hash-like class wouldn't be able to catch when query param values are modified in-place:
uri.query_params['foo'] = 'bar'
uri.query_params['foo'] << " oops"

Unfortunately there isn't a way around overriding #to_s, since URI::Generic#to_s loads the query value directly from @query instead of query.


Wrong named envvars

Just identified when looking into global envvars that should start with OCIS_
STORAGE_USERS_PERMISSION_ENDPOINT --> OCIS_STORAGE_USERS_PERMISSION_ENDPOINT
STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY --> OCIS_STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY
In the graph service, same as in userlog, there is the key-pair:
OCIS_MACHINE_AUTH_API_KEY
USERLOG_MACHINE_AUTH_API_KEY --> GRAPH_MACHINE_AUTH_API_KEY
WEB_UI_CONFIG_FILE is double present, can be seen in the web service too, we need to check why.
Following envvars are used in both the userlog and clientlog service. Those should be then either a global one starting with OCIS_ or the clientlog version adapted to CLIENTLOG_:
USERLOG_DEBUG_ADDR
USERLOG_DEBUG_PPROF
USERLOG_DEBUG_TOKEN
USERLOG_DEBUG_ZPAGES
USERLOG_LOG_COLOR
USERLOG_LOG_FILE
USERLOG_LOG_LEVEL
USERLOG_LOG_PRETTY
@kobergj @dragonchaser

STORAGE_USERS_PERMISSION_ENDPOINT and STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY are only present in storage-users service and therefore need no global OCIS prefix
All MACHINE_AUTH_API_KEY envvars can be deleted as they are no longer used because of service accounts
USERLOG envvars in clientlog service need of course be changed to CLIENTLOG.... That was a copy/paste mistake on implementation and a lazy no-look during review

All MACHINE_AUTH_API_KEY envvars can be deleted as they are no longer used because of service accounts

The proxy service is still using machine auth to be able to mint reva tokens for oidc user (and signedurl IIRC). Service accounts won't help to get rid of those cases I think. So we still need MACHINE_AUTH_API_KEY

:+1:  let me rephrase
For all services except proxy the MACHINE_AUTH_API_KEY envvar can be deleted as it is no longer used because of service accounts.

Services idp and frontend also still need the MACHINE_AUTH_API_KEY otherwise tests fail. We need to find out why and replace usage of machine authentication with service authentication. I'll create seperate tickets for that.


Update vendoring

Integration tests aren't liking this, may require some tweaking in client_golang.

Needed a few more vendoring commands due to the previous changes to involving expfmt. Should be good now.


Fix difference between original 'IO#each' and extended implementation

I found a different behavior of IO#each between origin and extended by packable gem.
If original IO#each be called with no option, a line is passed to the block for each line.
However, extended IO#each by packable gem doesn't behave same.
reproduction
str = <<EOS
line 1
line 2
line 3
EOS

puts '### before require packable gem'
StringIO.new(str).each { |line| puts (line + '---') }

# ### before require packable gem
# line 1
# ---
# line 2
# ---
# line 3
# ---

require 'packable'

puts '### after require packable gem'
StringIO.new(str).each { |line| puts (line + '---') }

# ### after require packable gem
# line 1
# line 2
# line 3
# ---

solution
If gave no option or first option is nil, then call original IO#each.
effects of problem
e.g. DNS resolution fails by Resolv
see: https://gist.github.com/passer-b/747677203b29a3b1103d97ca6e2dcb7a
reference

https://docs.ruby-lang.org/en/2.3.0/IO.html#method-i-each

@marcandre can you check this PR?


:memo: feat(ethers): Add jsdoc comments

Description
Update ethers package with minor cleanups and better jsdoc comments and generics
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #396   👈

This comment was auto-generated by Graphite.


[docs] Clarification on "category": "DeveloperTool"

In short I changed the value on my tauri.conf.json from
"category": "DeveloperTool", to "category": "Creative Tool", thinking this was a general string but received an error
Error running CLI: failed to build bundler settings: invalid category
I assume this is more likely a cargo error, but in case someone makes a similar error, may be worth having some clarification as to the allowed values, which despite some research i have not found a clear answer to.
Cargo suggests using a value from a predefined list
https://doc.rust-lang.org/cargo/reference/manifest.html?highlight=category#the-categories-field
However the value DeveloperTool isn't present? so I'm hesitant to list this as a solution and was hoping someone a bit more seasoned with rust/cargo/app dev might have some further insight, apologies i can't offer more.

The allowed categories are listed here: https://tauri.studio/v1/api/config#bundleconfig.category. (And another related thing is here: https://tauri.studio/v1/guides/building/macos#application-bundle-customization)
Furthermore it's not a cargo error, we handle this completely ourselves and the binary itself doesn't even know about this. It's only relevant for .deb (linux) and .app (macos) bundles (mainly for the appstore(s) i think?)


Cleanup of prune jobs not working as expected

Describe the bug
It seems that keep_jobs: 1 isn't respected correctly for prune type jobs. I'm observing that newer instances of finished prunes are deleted but older instances still stick around.
Additional context
This makes monitoring and manually checking the jobs really confusing.
Logs
Given keep_jobs: 1:
2021-07-22T04:47:17.206Z	INFO	observer	new event on observed job	{"event": "succeeded", "jobName": "test/backup-pods-prune-mckmq"}
2021-07-22T04:47:17.206Z	INFO	observer	job succeeded	{"jobName": "test/backup-pods-prune-mckmq"}
2021-07-22T04:47:17.206Z	INFO	controllers.Prune	cleaning old job	{"prune": "test/backup-pods-prune-mckmq", "namespace": "test", "name": "backup-pods-prune-mckmq"}
2021-07-22T04:47:17.333Z	INFO	observer	new event on observed job	{"event": "delete", "jobName": "test/backup-pods-prune-mckmq"}
2021-07-22T04:47:17.333Z	INFO	observer	deleting job from observer	{"jobName": "test/backup-pods-prune-mckmq"}
2021-07-22T04:47:17.333Z	INFO	controllers.Prune	cleaning old job	{"prune": "test/backup-pods-prune-mckmq", "namespace": "test", "name": "backup-pods-prune-mckmq"}

Expected behavior
The prune job should not get cleaned up, but rather older instances.
To Reproduce
Steps to reproduce the behaviour:

Specs

  prune:
    schedule: '45 */4 * * *'
    keepJobs: 1

Environment (please complete the following information):

Image Version: v1.1.0
K8s Version: OpenShift 3.11
K8s Distribution: OpenShift

Seems to be closed by #462.  Please reopen if this issues still exists


[BUG] code comment error

Describe the bug
in this class: org.apache.dolphinscheduler.server.master.runner.MasterSchedulerThread. the line number 104, zkMasterClient.getMasterLockPath() The lock path obtained may should be /dolphinscheduler/lock/masters,  but in the comment, is's /dolphinscheduler/lock/failover/master, I think it's easy to mislead people who read the source code,  please check this,  if it does, I can open a pr to fix it
To Reproduce
None
Expected behavior
Node
Screenshots
None
Which version of Dolphin Scheduler:
latest version
Additional context
None
**Requirement or improvement
None

welcome pr to  fix it

+1, please fix it

@lenboo
hi, I have fix the issue in the pr, may be you can review it, so I can close the issue


Update coconutbattery to 3.5

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for your contribution.

Hi there,
could you please check sha256sum again?
I always get ee1a404ecde685c6368adb6418e14523f212317d2a849af21ea093aeab8d616e but not 3aee9f08c1e63e9bc78ebe03156cf69e71c788ce6cfb9701f83bec6f5cc59575
Thx.

@RJHsiao Confirmed. https://github.com/caskroom/homebrew-cask/pull/29697.

Thanks. 😃

Huh, that's weird.
Checked the current zip in the Cask cache:
% shasum -a 256 ~/Library/Caches/Homebrew/Cask/coconutbattery--3.5.zip
3aee9f08c1e63e9bc78ebe03156cf69e71c788ce6cfb9701f83bec6f5cc59575 /Users/hobbinhood/Library/Caches/Homebrew/Cask/coconutbattery--3.5.zip`
Tried to verify with a freshly download zip and boom:
% shasum -a 256 ~/Downloads/coconutBattery_3.5.zip
ee1a404ecde685c6368adb6418e14523f212317d2a849af21ea093aeab8d616e  /Users/hobbinhood/Downloads/coconutBattery_3.5.zip
But both zip files extract the exact same App bundle with equal size down to the bit.
Any ideas on this behaviour?
Thank you for checking and updating, though :)

But both zip files extract the exact same App bundle with equal size down to the bit.
Any ideas on this behaviour?

It’s likely due to the metadata of the compressed archive itself.


Unable to use ng-model-options on the same tag as ng-app when ng-app is on html tag

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] other

Current behavior:

When using ngModelOptions on the same tag as the ngApp, the value of defaultModelOptions gets set to undefined. This causes errors for every ngModel directive in the template.
The error seems to come from NgModelOptionsController $onInit where the parentOptions is undefined and the createChild method can't be executed.
Expected / new behavior:

There should not be an error when a ngModelOption is defined on the same tag as an ngApp.
Or, it should be present in the migration documentation.
Minimal reproduction of the problem with instructions:

https://plnkr.co/edit/jOmVWDvIFuOyOWB2
AngularJS version: 1.6.10

Browser: Chrome 65, probably in all browsers

Anything else:

Hi, thanks for the report. From which version did you upgrade to 1.6.10?

15.11
Le sam. 21 avr. 2018 08:38, Martin Staffa<EMAIL_ADDRESS>a
écrit :

Hi, thanks for the report. From which version did you upgrade to 1.6.10?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/16535#issuecomment-383291841,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AByQUE_bB57N4k6S3MTMGekVjz7Y8x4dks5tqyhWgaJpZM4TdhNM
.

Marke it as a regression. I'm not sure we'll do another 1.6. release, though - maybe you'll have to upgrade to 1.7 straight.

Ok, nous problème. I have found a workaround by moving the ngModelOptions
elsewhere
Le mar. 24 avr. 2018 09:50, Martin Staffa<EMAIL_ADDRESS>a
écrit :

Marke it as a regression. I'm not sure we'll do another 1.6. release,
though - maybe you'll have to upgrade to 1.7 straight.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/16535#issuecomment-383937283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AByQUM-H_hQ7ZiT-Ry9IaEjMVs6sUk6wks5try2kgaJpZM4TdhNM
.

Just noticed that this only happens when ngApp is on the html tag - maybe that's because this is the top most tag in an html document.


fix compile error

这个 PR 实现什么功能/修复什么问题:
fix compile error
是否需要 backport 到之前的 release 分支:
None
/cc @swordqiu @yousong

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f4dbe64). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master   #1175   +/-   ##
========================================
  Coverage          ?   7.85%
========================================
  Files             ?     367
  Lines             ?   57813
  Branches          ?       0
========================================
  Hits              ?    4539
  Misses            ?   52875
  Partials          ?     399

Flag
Coverage Δ

#aFlag
7.85% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/cloudsync.go
0% <0%> (ø)

pkg/compute/models/natdtables.go
5.92% <0%> (ø)

pkg/compute/models/natstables.go
5.36% <0%> (ø)

pkg/compute/models/natgateways.go
3.73% <0%> (ø)

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 f4dbe64...32b7fb1. Read the comment docs.

/approve
/lgtm


Consider adding Svarog CLI to the list

Link to project (GitHub):
dantothefuture/svarog
Describe the project in 2-3 sentences:
Svarog is a CLI that generates schema validators for Firestore from JSON Schema files. The output is a single universal function isValid($id: string): boolean that you can use anywhere in your security rules to prevent unwanted mutations.
Why would Firebase developers be interested in this project?:
Schemaless design can be both an advantage and a disadvantage - and when it's the latter, devs have to write a ton of hardly readable CEL code to make sure their database schema is protected. That's where Svarog comes in, allowing Firebase developers to generate structure validators from a familiar, platform-agnostic JSON Schema format.
I know this is a shameless plug but maybe it's worth a try who knows 🙂

@dantothefuture that's a really cool project!  If you add a .opensource/project.json file to your repo I am happy to add it to this site.

Oh wait it's already there.  In that case will add now.

Will be live within 24h, let me know if that's not the case.

@dantothefuture lookin' good:
https://firebaseopensource.com/projects/dantothefuture/svarog/

Wow that was quick! Thanks @samtstern 🙂

@dantothefuture no problem thanks for the awesome tool!  I also shared it on our team chat.  We're always looking for new ways to make Security Rules better.