Update concept.md

代理服务器的描述重复，条目5、15都是描述代理服务器的。
What is the purpose of the change
代理服务器的描述重复，条目5、15都是描述代理服务器的。
Brief changelog
删除重复记录
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.02%) to 50.591% when pulling ce3a556fffb9a63288cf6559a80e815d943bc627 on zhibo6:patch-1 into 15df3297e1dbdaa8de8874bd37fe51c69dac8d28 on apache:master.

@zhibo6 could you change your target branch to develop?


AOT template error only displayed on initial build

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

1.5.0
Repro steps.

Create a component with a template which attempts to call a private method
ng serve --aot
Note that an error is thrown, like "Property 'formSubmit' is private and only accessible within class 'FormComponent'"
Kill the build task
Fix error by making method public and run ng serve --aot again
After successful build, reintroduce the error by making the method private again and save to trigger incremental build
Note that no error is thrown

Desired functionality.

Should throw errors for templates in incremental AOT builds

Sounds like a bug alright. Thanks for the report, will investigate 👍

Yes, I can confirm this. The initial build fails to compile due to errors but then a simple save causes a rebuild with successful compilation and no more errors to be thrown. I seem to be unable to reproduce this in a separate project so far.

@filipesilva in our application it was the result of an explicit include in the tsconfig.
include:["**/*.ts", "libs/mysuperlib/index.ts"]

Change to:
include:["**/*.ts", "libs/mysuperlib/*"]

@filipesilva do we want to look at this or it behaves as expected?

From the description it's not behaving as expected, but I haven't had time to investigate further. I get the impression it's not a frequent problem though.

It seems to be quite heavily dependent on project complexity although I've struggled to reproduce the problem to a single source

Looks like a problem with old version of the CLI. Let us close the issue for now. If it's still relevant, please open a new ticket with steps to reproduce and a minimal demo. Thanks!


Experimental sub command support

Codecov Report

Merging #4 (f9bd214) into master (a0fbf54) will decrease coverage by 8.39%.
The diff coverage is 44.44%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
- Coverage   94.36%   85.97%   -8.40%
==========================================
  Files           3        3
  Lines         142      164      +22
==========================================
+ Hits          134      141       +7
- Misses          8       23      +15

Impacted Files
Coverage Δ

typed_argparse/type_utils.py
88.42% <25.00%> (-2.79%)
:arrow_down:

typed_argparse/typed_argparse.py
81.81% <42.85%> (-18.19%)
:arrow_down:

typed_argparse/__init__.py
100.00% <100.00%> (ø)

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 a0fbf54...f9bd214. Read the comment docs.


compare function returning true still updates cache

Bug report
Description / Observed Behavior
When using a custom compare function and the comparison returns true, the data returned correctly keeps its current value, but the cached value still updates. This causes data to use the last received value when the component remounts and not the intended initial value we wanted to cache.
Expected Behavior
From reading the documentation I was expecting the cache to be persisted if a comparison returns true.
Repro Steps / Code Example
https://codesandbox.io/s/swr-using-compare-zn185?file=/src/App.tsx

click to mount the component
click "force revalidate" to... force some revalidates, and check data is correctly persisted.
click unmount to unmount the component
click mount again and check that data value is not the previously persisted value but the value of the last call

Additional Context
In my use case, the server response contains urls of images with timestamps that I want to exclude from the data diff in order to avoid re-downloading images the browser has in disk cache.
swr v0.4.0

Thanks for your detailed repro 🙏
For your specific use case. I think you could filter the data in the fetcher function, which might be more easier.
const result = [{
  image: 'xxx',
  timestamp: 'xxx'
}]

const fetcher = () => Promise.resolve(result).then(result => result.map(item => ({ image: item.image })))
const { data } = useSWR('/api', fetcher)

Writing a compare function sometimes could be a trick problem. so we use dequal as our default compare function.

Thanks for your detailed repro 🙏
For your specific use case. I think you could filter the data in the fetcher function, which might be more easier.
const result = [{
  image: 'xxx',
  timestamp: 'xxx'
}]

const fetcher = () => Promise.resolve(result).then(result => result.map(item => ({ image: item.image })))
const { data } = useSWR('/api', fetcher)

Writing a compare function sometimes could be a trick problem. so we use dequal as our default compare function.

Thank for the suggestion @promer94!
Unfortunately my use case is a bit more nuanced and I actually need the timestamp and other variable parts of the response to use in my component. The compare feature is exactly what I need to update the cache conditionally.

Thank for the suggestion @promer94!
Unfortunately my use case is a bit more nuanced and I actually need the timestamp and other variable parts of the response to use in my component. The compare feature is exactly what I need to update the cache conditionally.


freeze on first run with 2 monitors

Platform:
Darwin MacBook-Pro-de-Vladimir.local 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
Kap Version:
Versión 1.0.0 (<IP_ADDRESS>)
Steps to reproduce
first open: open up app with 2 monitors connected
Current behaviour
works after unplug the external monitor
Expected behaviour
no freeze
Workaround
unplug external monitor, kill app, open app again and then work ok even when external monitor was connected -again-

I have dual monitor screens and your workaround works. But kind of painful ...


channel names with special chars (app crash)

This file has a comment that isn’t being returned properly. https://odysee.com/@TheQuartering:1/instant-regret-youtube-mocks-creators:e
This channel created a comment https://lbry.tv/@🌀Epic◄►Games✔:d
The comment server is returning the authorURI as “lbry://@?Epic...” instead of “lbry://@:cyclone:EpicGames”  replacing the emoji with a question mark. It’s causing the page to crash because a question mark makes it an invalid URI. Can this be fixed on the comment server? (edited)
Claim id:
d89c5f31b688dc8097714dc0cb1694a5707067e2

@akinwale I am using character set utf8mb4_unicode_ci for the name column which is exactly what I am using in Chainquery. Thats the right one to capture this encoding right?
@tzarebczan Its either the jsonrpc protocol or its what I was passed from the API if @akinwale confirms.

@tiger5226 Yes, that's the correct encoding. Maybe it's been re-encoded or escaped incorrectly somewhere along the way? The only way to confirm for sure would be to check the actual data stored in the database.

This data was fixed in commentron. Some old notifications may still crash stuff.


Await for response from discord auth

We want to have a listener at a certain url (i.e. localhost:8080/redirect), and we send this url with the original redirect request. We then need to wait for that response as a json file, and print that to the console.

More Details:
NOTE: this follows on from the last issue: #2

Receive a POST request on /redirect?code={code}?state={state} (this is also the redirect_uri from #2)
where code is a temporary code used to obtain the access token
where state is the same state parameter that was supplied in #2, this should be validated to be the same

Make POST request to https://discordapp.com/api/oauth2/token with parameters in x-www-form-urlencoded:
grant_type is code
code is the code parameter obtained earlier
redirect_uri is the redirect_uri from #2
client_id is our bot's client_id (set in config)
client_secret is our bot's client_secret (set in config)

For now we can just display the response as json in a console or terminal, however later on we will be storing the tokens in the db


Write a JavaScript program to find the eigenvectors of a matrix

Description
Write a JavaScript program to find the eigenvectors of a matrix
The eigenvalues and eigenvectors of a linear transformation are the values and vectors that determine the transformation. The eigenvectors of a matrix A are the vectors v for which the matrix equation Av = λv has a non-trivial solution.
Input  :
1 2 3
4 5 6
7 8 9

Output :
[[-0.23197068724628608, -0.7858302387246789, 0.4082482904638631],
 [-0.5253220933012334, -0.08675134095039447, -0.8164965809277261],
 [-0.8186734993561807, 0.6123275568238899, 0.4082482904638631]]

How to contribute

Save the solution in program/FindTheEigenvectorsOfAMatrix.js file
Add FindTheEigenvectorsOfAMatrix.js file in find-the-eigenvectors-of-a-matrix folder

!assign

Hey @surajrane42,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign

Hey @pritish1906, this issue is already assigned to @anandfresh !!!
Please choose another issue.
Thanks for your interest in contributing to this project.

!assign


storage: Client is leaking go routine(s).

Repro unit test:
package gcs

import (
	"context"
	"os"
	"testing"
	"time"

	"cloud.google.com/go/storage"
	"github.com/fortytw2/leaktest"
	"github.com/stretchr/testify/require"
)

func TestBug(t *testing.T) {
	defer leaktest.CheckTimeout(t, 10*time.Second)()

	gcsClient, err := storage.NewClient(context.Background())
	require.NoError(t, err)

	testName := "test-gcs-leak"
	bkt := gcsClient.Bucket(testName)

	defer func() {
		if err := bkt.Delete(context.Background()); err != nil {
			t.Logf("deleting bucket failed: %s", err)
		}

		gcsClient.Close()
	}()

	require.NoError(t, bkt.Create(context.Background(), os.Getenv("GCP_PROJECT"), nil))
}

Basically I am unable to detect leaks easily on my own code if the client library leaks go routines on its own ):
I am pretty sure it is not limited to storage, but not tested any other client.
The truth is that it must be only some single go routine that is leaked, because long-term running applications that use this library does not indicate intensive mem usage or leak.
This is just annoying while testing my own code.
Client
My vendoring stats:
[[projects]]
  name = "cloud.google.com/go"
  packages = [
    "compute/metadata",
    "iam",
    "internal",
    "internal/optional",
    "internal/version",
    "storage",
    "trace/apiv1"
  ]
  revision = "2d3a6656c17a60b0815b7e06ab0be04eacb6e613"
  version = "v0.16.0"

Describe Your Environment
64bit Ubuntu
Expected Behavior
Above unit test output that uses gcs storage client:
=== RUN   TestBug
--- FAIL: TestBug (10.03s)
	leaktest.go:90: leaktest: timed out checking goroutines
	leaktest.go:108: leaktest: leaked goroutine: goroutine 30 [IO wait]:
		internal/poll.runtime_pollWait(0x7f7fe08c3f00, 0x72, 0xc420542858)
			/usr/local/go/src/runtime/netpoll.go:173 +0x57
		internal/poll.(*pollDesc).wait(0xc42018a618, 0x72, 0xffffffffffffff00, 0xa19660, 0xc936e8)
			/usr/local/go/src/internal/poll/fd_poll_runtime.go:85 +0x9b
		internal/poll.(*pollDesc).waitRead(0xc42018a618, 0xc420450000, 0x1000, 0x1000)
			/usr/local/go/src/internal/poll/fd_poll_runtime.go:90 +0x3d
		internal/poll.(*FD).Read(0xc42018a600, 0xc420450000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
			/usr/local/go/src/internal/poll/fd_unix.go:157 +0x17d
		net.(*netFD).Read(0xc42018a600, 0xc420450000, 0x1000, 0x1000, 0x435c09, 0xc420086900, 0x200000003)
			/usr/local/go/src/net/fd_unix.go:202 +0x4f
		net.(*conn).Read(0xc4201d02b0, 0xc420450000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
			/usr/local/go/src/net/net.go:176 +0x6a
		crypto/tls.(*block).readFromUntil(0xc4201c5380, 0x7f7fe0883230, 0xc4201d02b0, 0x5, 0xc4201d02b0, 0xc420542a10)
			/usr/local/go/src/crypto/tls/conn.go:493 +0x96
		crypto/tls.(*Conn).readRecord(0xc4201d5180, 0x9daa17, 0xc4201d52a0, 0xc420086900)
			/usr/local/go/src/crypto/tls/conn.go:595 +0xe0
		crypto/tls.(*Conn).Read(0xc4201d5180, 0xc4203b8000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
			/usr/local/go/src/crypto/tls/conn.go:1156 +0x100
		bufio.(*Reader).Read(0xc4201c9860, 0xc42033b458, 0x9, 0x9, 0xc4201d54b0, 0x61d060, 0xc4201d54b0)
			/usr/local/go/src/bufio/bufio.go:216 +0x238
		io.ReadAtLeast(0xa17880, 0xc4201c9860, 0xc42033b458, 0x9, 0x9, 0x9, 0x68a3e1, 0xc4201d5180, 0xc420451000)
			/usr/local/go/src/io/io.go:309 +0x86
		io.ReadFull(0xa17880, 0xc4201c9860, 0xc42033b458, 0x9, 0x9, 0x6d0c24, 0x7f7fe0883c90, 0xc4201d5180)
			/usr/local/go/src/io/io.go:327 +0x58
		net/http.http2readFrameHeader(0xc42033b458, 0x9, 0x9, 0xa17880, 0xc4201c9860, 0x0, 0xc400000000, 0x42c1e4, 0x9daac0)
			/usr/local/go/src/net/http/h2_bundle.go:1517 +0x7b
		net/http.(*http2Framer).ReadFrame(0xc42033b420, 0xc42037be60, 0x0, 0x0, 0x0)
			/usr/local/go/src/net/http/h2_bundle.go:1775 +0xa4
		net/http.(*http2clientConnReadLoop).run(0xc420542fb8, 0x9da3c0, 0xc4203b7fb8)
			/usr/local/go/src/net/http/h2_bundle.go:8028 +0x90
		net/http.(*http2ClientConn).readLoop(0xc4202b7c00)
			/usr/local/go/src/net/http/h2_bundle.go:7956 +0x68
		created by net/http.(*http2Transport).newClientConn
			/usr/local/go/src/net/http/h2_bundle.go:7143 +0x65c
	leaktest.go:108: leaktest: leaked goroutine: goroutine 34 [IO wait]:
		internal/poll.runtime_pollWait(0x7f7fe08c3d60, 0x72, 0xc420543858)
			/usr/local/go/src/runtime/netpoll.go:173 +0x57
		internal/poll.(*pollDesc).wait(0xc4201f4a98, 0x72, 0xffffffffffffff00, 0xa19660, 0xc936e8)
			/usr/local/go/src/internal/poll/fd_poll_runtime.go:85 +0x9b
		internal/poll.(*pollDesc).waitRead(0xc4201f4a98, 0xc4203b9000, 0x1000, 0x1000)
			/usr/local/go/src/internal/poll/fd_poll_runtime.go:90 +0x3d
		internal/poll.(*FD).Read(0xc4201f4a80, 0xc4203b9000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
			/usr/local/go/src/internal/poll/fd_unix.go:157 +0x17d
		net.(*netFD).Read(0xc4201f4a80, 0xc4203b9000, 0x1000, 0x1000, 0x435c09, 0xc420468780, 0x200000003)
			/usr/local/go/src/net/fd_unix.go:202 +0x4f
		net.(*conn).Read(0xc4201d0030, 0xc4203b9000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
			/usr/local/go/src/net/net.go:176 +0x6a
		crypto/tls.(*block).readFromUntil(0xc42032c870, 0x7f7fe0883230, 0xc4201d0030, 0x5, 0xc4201d0030, 0xc420543a10)
			/usr/local/go/src/crypto/tls/conn.go:493 +0x96
		crypto/tls.(*Conn).readRecord(0xc4201d4700, 0x9daa17, 0xc4201d4820, 0xc420468780)
			/usr/local/go/src/crypto/tls/conn.go:595 +0xe0
		crypto/tls.(*Conn).Read(0xc4201d4700, 0xc4202cf000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
			/usr/local/go/src/crypto/tls/conn.go:1156 +0x100
		bufio.(*Reader).Read(0xc4201c8600, 0xc4202cc738, 0x9, 0x9, 0xc4201d4a30, 0x61d060, 0xc4201d4a30)
			/usr/local/go/src/bufio/bufio.go:216 +0x238
		io.ReadAtLeast(0xa17880, 0xc4201c8600, 0xc4202cc738, 0x9, 0x9, 0x9, 0x68a3e1, 0xc4201d4700, 0xc4202ce000)
			/usr/local/go/src/io/io.go:309 +0x86
		io.ReadFull(0xa17880, 0xc4201c8600, 0xc4202cc738, 0x9, 0x9, 0x6d0c24, 0x7f7fe0883c90, 0xc4201d4700)
			/usr/local/go/src/io/io.go:327 +0x58
		net/http.http2readFrameHeader(0xc4202cc738, 0x9, 0x9, 0xa17880, 0xc4201c8600, 0x0, 0xc400000000, 0x42c1e4, 0x9daac0)
			/usr/local/go/src/net/http/h2_bundle.go:1517 +0x7b
		net/http.(*http2Framer).ReadFrame(0xc4202cc700, 0xc420305220, 0x0, 0x0, 0x0)
			/usr/local/go/src/net/http/h2_bundle.go:1775 +0xa4
		net/http.(*http2clientConnReadLoop).run(0xc420543fb8, 0x9da3c0, 0xc4200497b8)
			/usr/local/go/src/net/http/h2_bundle.go:8028 +0x90
		net/http.(*http2ClientConn).readLoop(0xc4201e68c0)
			/usr/local/go/src/net/http/h2_bundle.go:7956 +0x68
		created by net/http.(*http2Transport).newClientConn
			/usr/local/go/src/net/http/h2_bundle.go:7143 +0x65c
FAIL

Actual Behavior
Just pass, no leaktest stack traces.
I would really recommend using https://github.com/fortytw2/leaktest in every go project test. It will help detect these issues early on.

I thought that context is not simply not cancelled, but actually, with explicit context cancel, leak output stays the same:
package gcs

import (
	"context"
	"os"
	"testing"
	"time"

	"cloud.google.com/go/storage"
	"github.com/fortytw2/leaktest"
	"github.com/stretchr/testify/require"
)

func TestBug(t *testing.T) {
	defer leaktest.CheckTimeout(t, 10*time.Second)()

	ctx, cancel := context.WithCancel(context.Background())

	gcsClient, err := storage.NewClient(ctx)
	require.NoError(t, err)

	testName := "test-gcs-leak"
	bkt := gcsClient.Bucket(testName)

	defer func() {
		if err := bkt.Delete(ctx); err != nil {
			t.Logf("deleting bucket failed: %s", err)
		}

		gcsClient.Close()
		cancel()
	}()

	require.NoError(t, bkt.Create(ctx, os.Getenv("GCP_PROJECT"), nil))
}

Thanks for filing this. I looked into it - it appears to be an x/net/http2 bug. I've filed an issue - please track there. https://github.com/golang/go/issues/25759
(will re-open this issue if it turns out the above is incorrect, but it seems fairly straightforward)

Seems as though Go's h2 is working as intended. Re-opening to investigate more.

Try calling http.DefaultTransport.CloseIdleConnections() and see if that helps. If your leak checker allows you to ignore goroutines, you could also try that. (If not, I suggest finding one that does.)
It's hard for us to plumb the connection-closing logic through the clients, and not worth it given the above workarounds. If there are other downsides to those idle goroutines, we would reconsider.

defer http.DefaultTransport.(*http.Transport).CloseIdleConnections() while being bit sketchy (invoking some method on global variable, works fine.
Also storage client accepts custom http.Client so all is fine:
package gcs

import (
	"context"
	"os"
	"testing"
	"time"

	"cloud.google.com/go/storage"
	"github.com/fortytw2/leaktest"
	"github.com/stretchr/testify/require"
	"net/http"
	"google.golang.org/api/option"
	"net"
)

func TestBug(t *testing.T) {
	defer leaktest.CheckTimeout(t, 10*time.Second)()

	c := &http.Client{
		Transport: &http.Transport{
			Proxy: http.ProxyFromEnvironment,
			DialContext: (&net.Dialer{
				Timeout:   30 * time.Second,
				KeepAlive: 30 * time.Second,
				DualStack: true,
			}).DialContext,
			MaxIdleConns:          100,
			IdleConnTimeout:       90 * time.Second,
			TLSHandshakeTimeout:   10 * time.Second,
			ExpectContinueTimeout: 1 * time.Second,
		},
	}

	defer c.Transport.(*http.Transport).CloseIdleConnections()
	gcsClient, err := storage.NewClient(context.Background(), option.WithHTTPClient(c))
	require.NoError(t, err)

	testName := "test-gcs-leak"
	bkt := gcsClient.Bucket(testName)

	defer func() {
		if err := bkt.Delete(context.Background()); err != nil {
			t.Logf("deleting bucket failed: %s", err)
		}

		gcsClient.Close()
	}()

	require.NoError(t, bkt.Create(context.Background(), os.Getenv("GCP_PROJECT"), nil))
}

Thanks for so quick reaction! And sorry for filling issue that was not storage issue in any way ):

No worries - glad we got it figured out! 😃


Rephrasing, and actually describe what files each section is describing

Thanks a lot, that is indeed improvement.


sp-logout should make request with accept json header

The request that sp-logout makes should be sent with an accept: json header. When sent as accept: text/html an unnecessary redirect is made to /.

This was fixed with #48.


⚠ PrivateHD has degraded performance

In 025a66c, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2151 ms

Resolved: PrivateHD performance has improved in 8529e1d.


[regression test](schema change) add some schema change regression cases (#27112)

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Command mentioned in Docs doesn't work anymore

The command mentioned in the documentation doesn't work anymore and needs to be updated
CURRENT_IP=$(dig @resolver1.opendns.com ANY myip.opendns.com +short)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 48d0faa9-cf20-e7b2-be10-4cee86147789
Version Independent ID: 65588401-dec8-1720-5f7a-c01b959d043f
Content: Access Kubernetes resources from the Azure portal - Azure Kubernetes Service
Content Source: articles/aks/kubernetes-portal.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for your contribution to the doc by opening a PR. Once the reviewer approves the PR, the changes will be merged to the doc.


Support "short citation" in search syntax

In accordance with https://github.com/metanorma/metanorma-nist/issues/95#issuecomment-487120038 , NistBib should support the following search syntax:

Type
Short

Undated reference
"SP 800-162" or "NIST SP 800-162"

Final without updated-date
"SP 800-162 (January 2014)" or "NIST SP 800-162 (January 2014)"

Final where updated-date > original-release-date
"SP 800-162 (February 25, 2019)" or "NIST SP 800-162 (February 25, 2019)"

Please also refer to the following issues when parsing the page:

https://github.com/metanorma/metanorma-nist/issues/115
https://github.com/metanorma/metanorma-nist/issues/116

The "short form" is:

NIST publications:

NIST {abbrev(series)} {docnumber} {edition, optional} {(stage)}

(stage) is empty if the state is "final" (published)

edition is the date of publication or update (see original post above https://github.com/metanorma/nistbib/issues/12#issue-437754112)

FIPS:

FIPS {docnumber}
# or
NIST FIPS {docnumber}

(docnumber is the full FIPS number, including revision, e.g., 140-2.)

And if stage is not empty, it is going to be abbreviated, as discussed in https://github.com/metanorma/metanorma-nist/issues/116:
The first iteration of a public draft (<status><stage>draft-public</stage><iteration>1</iteration></status> or just <status><stage>draft-public</stage></status>) is abbreviated IPD.
The final iteration of a public draft (<status><stage>draft-public</stage><iteration>final</iteration></status>) is abbreviated FPD.
The other iterations of a public draft (e.g. <status><stage>draft-public</stage><iteration>3</iteration></status>) are abbreviated 2PD, 3PD, etc.

@ronaldtse @opoudjis where we can scrape the iteration number?

@ronaldtse does the table https://github.com/metanorma/nistbib/issues/12#issue-437754112 mean we should search:

for Undated reference references all type docs (final, draft)
for Final without updated-date only final type of docs where an issued date is as in the reference.
for Final where updated-date > original-release-date only final type docs where an updated date is as in the reference?

@ronaldtse I see drafts with codes include Rev. 1, Rev. 2, Rev. 3. For example SP 800-52 Rev. 2 (DRAFT)
Could we consider this part of the code as status iteration? If yes does it mean drafts without the part of code have status iteration final?

@ronaldtse I think we can use document history to calculate an iteration.

if history is empty or the current document is first in history then an iteration is initial (1)
if the document isn't first in history then a position of the document is an iteration value (2,3)
if the last document in history is final and current document position in history is before the last document then iteration is final

See iterations here https://github.com/metanorma/metanorma-nist/issues/116#issuecomment-488677211

@ronaldtse @opoudjis where we can scrape the iteration number?

Dunno. Ronald?

@ronaldtse does the table #12 (comment) mean we should search:

I'm not convinced I have heard clearly articulated rules yet. I know that the updated date is only meant to be present in errata releases. (Minor changes which are not considered significant enough to result in a version update.) For drafts, I have been putting the circulated-date (date of last issued draft) in the citation, and reserving undated references for final. I'm not sure that is the rule. I also don't know when final drafts get dates, and I suspect that is a legacy convention instead of proper Revision notation.
@ronaldtse, question remains open, and I am concerned that there won't be clear guidance from NIST about this, because they have not been historically consistent in their use of dates.

@ronaldtse could a short ref be with stage and without edition? For example SP 800-162 (2PD).

Don't know. Like I said, I am putting the date in.

@ronaldtse I see drafts with codes included Rev. 1, Rev. 2, Rev. 3. For example SP 800-52 Rev. 2 (DRAFT)
Could we consider this part of the code as status iteration? If yes does it mean drafts without the part of code have status iteration final?

Regrettably, revision and iteration are two completely different things.

Revision are a new version of the published document; they are what is elsewhere called a new edition. The first edition is a zeroth revision, so there is no revision number; the second edition is a first edition, so it's indicated as Rev. 1, right after the {docnumber}.
Iterations are numbers of times the current stage of the draft has been gone through.

So the following are all possible:

NIST SP 800-162 (IPD) (first iteration of public draft of zeroth revision of 800-162)
NIST SP 800-162 (2PD) (second iteration of public draft of zeroth revision of 800-162)
NIST SP 800-162 (published version of zeroth revision of 800-162)
NIST SP 800-162 Rev. 1 (IPD) (first iteration of public draft of first revision of 800-162)
NIST SP 800-162 Rev. 1 (2PD) (second iteration of public draft of first revision of 800-162)
NIST SP 800-162 Rev. 1 (published version of zeroth revision of 800-162)

After the refactoring, the revision is indicated in bibitem as <edition>Revision 1</edition>, <edition>Revision 2</edition>: it is an attribute of the document, whatever stage it is in. The iteration, on the other hand, is specifically an attribute of the draft stage.
If there is no "Rev. 1" in the document title, do not populate <edition>. And do not assume anything about iterations from published documents, as your last comment suggests. The only place you will ever see iterations in the website is in descriptions of drafts, as IPD, 2PD, 3PD, ..., FPD (or: initial public draft, second public draft, third public draft... final public draft). Again: iterations are attributes only of drafts, not of published documents.

@andrew2net sorry for the late reply.

@ronaldtse @opoudjis where we can scrape the iteration number?

This is not available from the NIST Publications site. It will be available from the new CSRC web service for Metanorma (which is not yet available).

@ronaldtse does the table #12 (comment) mean we should search:
for Undated reference references all type docs (final, draft)

An undated reference means that it refers to the latest Final (with the latest updated-date), but in the bib item it should also be undated.

for Final without updated-date only final type of docs where an issued date is as in the reference.

A Final reference only refers to the latest Final (with the latest updated-date), but the bib item should keep it without the updated-date.

for Final where updated-date > original-release-date only final type docs where an updated date is as in the reference?

Yes. In the bib item, it should also specify the full information about the updated-date too.

@ronaldtse could a short ref be with stage and without edition? For example SP 800-162 (2PD).

Yes! NIST edition means Rev. X. Edition = 1 --> Rev. 1, which is not displayed (implied). So SP 800-162 (2PD) means it is the 2nd Public Draft of SP 800-162 (which is Edition = 1).

@ronaldtse I see drafts with codes included Rev. 1, Rev. 2, Rev. 3. For example SP 800-52 Rev. 2 (DRAFT)
Could we consider this part of the code as status iteration? If yes does it mean drafts without the part of code have status iteration final?

No. The Rev. X means "edition". "SP 800-52 Rev. 2 (DRAFT)" means it is the PD (public draft) of "SP 800-52 Rev. 2" (draft of edition = 3).
Edition applies to the document (document as project). Iteration applies to a document stage. They are different.

@ronaldtse I think we can use document history to calculate an iteration.
if history is empty or the current document is first in history then an iteration is initial (1)

Yes -- but iteration only applies to "Drafts".
All stages have an "initial" iteration (iteration = 1). This is abbreviated as "I", such as "IPD" (Initial Public Draft), "IPreD" (Initial Preliminary Draft).

if the document isn't first in history then a position of the document is an iteration value (2,3)

Yes, again only for drafts. Or 4, 5, or whatever.

if the last document in history is final and current document position in history is before the last document then iteration is final

It doesn't work like this, I should have clarified earlier.
The "final" iteration is applied ad-hoc -- only in some documents the authors put "final". Most of the time, an "IPD" (iteration = 1), "2PD" (iteration = 2) or "3PD" (iteration = 2) becomes the last PD. So this cannot be automated. Most documents never have an "FPD".
Now for @opoudjis :

If there is no "Rev. 1" in the document title, do not populate . And do not assume anything about iterations from published documents, as your last comment suggests. The only place you will ever see iterations in the website is in descriptions of drafts, as IPD, 2PD, 3PD, ..., FPD (or: initial public draft, second public draft, third public draft... final public draft). Again: iterations are attributes only of drafts, not of published documents.

Why not use edition = 1 for non-Rev, and edition = 2 for "Rev. 1"?

I'm not convinced I have heard clearly articulated rules yet. I know that the updated date is only meant to be present in errata releases. (Minor changes which are not considered significant enough to result in a version update.) For drafts, I have been putting the circulated-date (date of last issued draft) in the citation, and reserving undated references for final. I'm not sure that is the rule. I also don't know when final drafts get dates, and I suspect that is a legacy convention instead of proper Revision notation.
@ronaldtse, question remains open, and I am concerned that there won't be clear guidance from NIST about this, because they have not been historically consistent in their use of dates.

We have agreed on the rules with NIST:

updated-date is the date we use for errata releases
confirmed-date is the date a document was confirmed (after Editorial Review Board approval every 5 years and when there has not been any update; this is a new process)
circulated-date is used for stage drafts

I feel that we actually need to bind a bibliographic date with a document stage...

Why not use edition = 1 for non-Rev, and edition = 2 for "Rev. 1"?

Because I don't trust them not to make up a text-based revision, or to otherwise break this; and I don't trust them, for that matter, not to end up using editions as well as revisions. This is more future-proof.
The rules you list are for when dates are used; what is still not clear to me is when identifiers (other than errata releases) are undated, and when they are dated by publication date. Presumably the latter are legacy, but Andrej is still going to be seeing them.


modify make and tox for unit tests

make unit wasn't running unit tests. Now it should.
Reviewers: please run make dev then make unit in a new virtual environment and report back if this works for you or not.
Checklist

[ ] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-spark next" section.

Stale PR. We fixed this a little while back now.


OPC-UA connector not working anymore

Hi Klaus,
tried 2.0.5 and 2.0.8 cannot connect to an OPC-UA server anymore. It works before, log shows
[ 'opc.tcp://<IP_ADDRESS>:4840 NONE http://opcfoundation.org/UA/SecurityPolicy#None' ]

Hi Giovanni,
could you give more logs?

strange ... just if a clean install had that problem in my development environment ... should be fixed with v2.0.9

Tested and deployed 2.0.9 same error
[ 'opc.tcp://<IP_ADDRESS>:4840 NONE http://opcfoundation.org/UA/SecurityPolicy#None' ]
The listener node cannot connect to an external OPC/UA server the status message is always waiting...

I am not sure, I guess the problem is coming from node-opcua CreateSession ?

v2.0.9 is on node-opcua 0.2.1 and it works for me

You'll get the endpoint in debug log - try the given endpoint, please

Please test the v2.0.10, what you get for the endpoints
coreConnector.internalDebugLog('Get Endpoints Request Error ' + err.message)

Nothing changed since 2.0.5:

In the log I get always: [ 'opc.tcp://<IP_ADDRESS>:4840 NONE http://opcfoundation.org/UA/SecurityPolicy#None' ]
My OPC-UA server has definitively another IP address and port.
The status of IIOTConnector is waiting...
From the command line I can ping the OPC-UA server.
If I use the ProSys OPC Client I can successfully connect to the OPC-UA server.
I am using node 6.10.10 and npm 3.10.3
I am running Alpine Linux 3.7 on Docker 17.09.1-ce

Should I enable DEBUG on IIOTConnector to track down the problem?

Questions:
What caused this breaking change?
API changed in major style for node-opcua 0.2.x and I am working in iterative steps to fix all until 2.1.x
You could also use v1.x of my package if 2.x is not stable for you

Should I enable DEBUG on IIOTConnector to track down the problem?
Yes, but better to see is a DEBUG=opcuaIIoT* log

opc.tcp://pcname.mshome.net:53530/

I have tested with the opcua-commander and it looks like an issue in node-opcua. Please, open an issue for that at node-opcua!

tested with opcua-commander v0.2.1 and v0.2.2 node-opcua

Hi @biancode
Here is the debug output from the connector, please bear in mind my OPC-UA server has two network adapter LAN and WAN. the <IP_ADDRESS> is my LAN address and <IP_ADDRESS> is my WAN address. I want to connect from the LAN side using <IP_ADDRESS>

2018-02-26T19:46:51.222Z opcuaIIoT:connector Connecting On opc.tcp://<IP_ADDRESS>:4840
2018-02-26T19:46:51.551Z opcuaIIoT:connector Connected On opc.tcp://<IP_ADDRESS>:4840 Options {"securityPolicy":"None","securityMode":"NONE","defaultSecureTokenLifetime":"60000","keepSessionAlive":true,"certificateFile":"/data/red/node_modules/node-opcua-client/certificates/client_selfsigned_cert_1024.pem","privateKeyFile":"/data/red/node_modules/node-opcua-client/certificates/PKI/own/private/private_key.pem"}
2018-02-26T19:46:51.564Z opcuaIIoT:connector endpoint: opc.tcp://<IP_ADDRESS>:4840
2018-02-26T19:46:51.565Z opcuaIIoT:connector urn:<IP_ADDRESS>
2018-02-26T19:46:51.569Z opcuaIIoT:connector Setup Certified Options For opc.tcp://<IP_ADDRESS>:4840
2018-02-26T19:46:51.585Z opcuaIIoT:connector !!!!!!!!!!!!!!!!!!!!!!!!  CONNECTION CLOSED !!!!!!!!!!!!!!!!!!!
2018-02-26T19:46:51.592Z opcuaIIoT:connector Disconnected From opc.tcp://<IP_ADDRESS>:4840
2018-02-26T19:46:51.638Z opcuaIIoT:connector Secured Connected On opc.tcp://<IP_ADDRESS>:4840
2018-02-26T19:46:51.640Z opcuaIIoT:listener starting OPC UA session with delay of 1000
2018-02-26T19:46:52.643Z opcuaIIoT:listener Listener Start OPC UA Session
2018-02-26T19:46:52.644Z opcuaIIoT:connector Request For New Session From Listener Node
2018-02-26T19:46:52.669Z opcuaIIoT:connector Session Start Error Error:  End point must exist opc.tcp://<IP_ADDRESS>:4840
2018-02-26T19:46:52.670Z opcuaIIoT:listener Handle Session Error Error:  End point must exist opc.tcp://<IP_ADDRESS>:4840
[ 'opc.tcp://<IP_ADDRESS>:4840 NONE http://opcfoundation.org/UA/SecurityPolicy#None' ]

@erossignon - please - some idea about that problem? - I tested with ProSys server too and it does not work - same problem with the opcua-commander

BTW, I just retested installing<EMAIL_ADDRESS>this way and it worked as expected
npm install opcua-commander -g
opcua-commander opc.tcp://MYLAPTOP:53530/OPCUA/SimulationServer

OK, I'll add the endpoint_must_exist option to control from node settings.

@erossignon thank you - step forward but Internal Error in ProSys server.

Hi,
I have a similar / the same issue: I can't connect to an opc server using the current version.
node: v8.9.4
node-red: v0.17.5
node-opcua: v0.2.2
node-red-contrib-iiot-opcua: v2.0.12
opc ua server: open62541
I can connect without problems using UAExpert. Using node-red / OPCUA-IIoT, I get the following errors on the server:

[03/05/2018 19:56:23.715] info/network  Connection 5 | New connection over TCP from <IP_ADDRESS>:40705
[03/05/2018 19:56:23.814] info/channel  Connection 5 | SecureChannel 2 | OpenSecureChannel: Opened SecureChannel
[03/05/2018 19:56:23.828] info/session  Try to use Session with token 00000000-0000-0000-0000-000000000000 but is not found
[03/05/2018 19:56:25.919] info/session  Try to use Session with token 00000000-0000-0000-0000-000000000000 but is not found
[03/05/2018 19:56:25.927] info/channel  Connection 5 | SecureChannel 2 | CloseSecureChannel
[03/05/2018 19:57:25.948] info/network  Connection 6 | New connection over TCP from <IP_ADDRESS>:40791
[03/05/2018 19:57:25.967] info/channel  Connection 6 | SecureChannel 3 | OpenSecureChannel: Opened SecureChannel
[03/05/2018 19:57:25.984] info/session  Try to use Session with token 00000000-0000-0000-0000-000000000000 but is not found
[03/05/2018 19:57:27.036] info/session  Connection 0 | SecureChannel 0 | Session dd73bc5f-2f84-a3ea-e0ce-5ca505509509 | ActivateSession: SecureChannel 3 wants to activate, but the UserIdentify token is invalid

In node-red, I receive:

"Error: ServiceResult is BadIdentityTokenInvalid (0x80200000)"

older issues on node-opcua for that


Enabling Operator Feature Flags in Admin Portal 2.0

Which issue this PR addresses:

Fixes
Display ARO Operator feature flags

What this PR does / why we need it:

This PR adds functionality for displaying Operator Feature Flags in the Admin Portal 2.0

Test plan for issue:

Added E2E Tests for Frontend, along with the backend functionality tests.

Is there any documentation that needs to be updated for this PR?

No

/azp run e2e

/azp run e2e

/azp run e2e

@Shivkumar13 E2E are green now, but if you are going to be doing more changes to the branch - I recommend you to rebase on top of the master. I see that some previous runs for this PR failed on a flake which was fixed in #2507

@Shivkumar13 I think you need to execute locally make generate, commit and push changes because you are modifying pkg/util/mocks/api/api.go
We can see that info in the output of the "ci-go / ci-from-docker (pull_request)" check:
2022/11/17 10:44:42 pkg/util/mocks/api/api.go has been modified after make generate
exit status 1

Did make generate and pushed the code again, CI seems to be green now!

/azp run e2e

@darthhexx PTAL

Added the functionality to get the Operator Feature Flags which are changed via a cluster object. Since here we are seeing the cluster object as a source of truth. And not the CosmosDB Document.

This is a nice PR. I wonder could we resurrect it easily enough by dealing cherry-picking, starting a new branch, dealing with outstanding comments there and opening a new PR? (Happy to help with this if that sounds good?)


Incorrect links

Hi Team,
The doc link for the Amazon CloudTrail - Cloud Security Monitoring and Analytics  in the App Catalog is confusing as it navigates us to https://help.sumologic.com/docs/integrations/cloud-security-monitoring-analytics/aws-cloudtrail-pci-compliance/.
Also, The setup doc link for CIS AWS Foundations Benchmark is incorrect.  It takes us to Share a Dashboard Outside Your Org https://help.sumologic.com/docs/dashboards/share-dashboard-outside-org/
cc: <@U8WP8747J>
Slack Message

You beat me to it @JainM6
I have a whole page of notes on this topic related to Cloud Trail in general. There are several docs that need to be updated as a group to help this all make sense. Very confusing ATM.  Happy to help with sharing info and suggesting edits, perhaps a quick internal call to level set is a good starting point.

You beat me to it @JainM6 I have a whole page of notes on this topic related to Cloud Trail in general. There are several docs that need to be updated as a group to help this all make sense. Very confusing ATM. Happy to help with sharing info and suggesting edits, perhaps a quick internal call to level set is a good starting point.

Hi @rplahn , thank you so much for reaching out! We would love the help. @nmohantyctr manages the App Catalog docs and would be your contact for Cloudtrail edits. Maybe you two can connect over Slack?


encoding problems when saving/loading requests

If using characters outside the latin alphabet for naming requests, or to body content to send in a request, saving to json all requests and reloading again causes these characters to be garbage.

Can you provide an example of the text it has problems with?

The above is the original-correct presentation
The following is the image after reloading the json file:

And the saved json is:
testGreekChars.zip
The JSON should be UTF-8 by default. I think that Delphi needs always a conversion when a utf8string is assigned to string

Thanks.. pushed a change to SL.Storage.Profile.pas that should fix this.

Thank you. waiting for it.

Sorry, my git client got "stuck"..


add-netpol-actions-to-plan1

towards https://github.com/giantswarm/giantswarm/issues/13955
 #: ./awscnfm plan pl001 -h
Test plan pl001 launches a basic Tenant Cluster and verifies basic criteria like
the correct number of nodes and pods are running. Plan execution might take up
to 3h3m0s.


submodule, subtree, subrepo

@MatthewJA What do you think of bleeding edge?
https://github.com/ingydotnet/git-subrepo

Bleeding edge is fun!
Questionable Windows compatibility though. I'd have to test it.

I don't really mind which of these we pick, but if we pick something, we can close this issue. So whatever works for you.

Added as submodule in commit 652777d42da96d0db0ef4d4d15a835469b5b3dc1
https://github.com/chengsoonong/crowdastro-projects


Set droppedAttributesCount correctly

Similar to https://github.com/agardnerIT/tracepusher/issues/31
Logpusher is currently (v0.1.0) hardcoded to silently drop invalid span attributes and always return a zero.
https://github.com/agardnerIT/logpusher/blob/77c4de9ddd227275ecff25af5bc39e260feb5005/logpusher.py#L42
https://github.com/agardnerIT/logpusher/blob/77c4de9ddd227275ecff25af5bc39e260feb5005/logpusher.py#L143
This should not be the case. If attributes are ignored, the droppedAttributesCount should be accurate.

Fixed in https://github.com/agardnerIT/logpusher/commit/7308cab63202004c0fbd6825adfd39acb1c79d83


Upgrade ruby to 2.7

Ruby 2.6 is EOL next spring. In order to get a ahead of that change as well as take advantage of some optimization in ruby 2.7 we can upgrade this now.
This did break the csv transformer. Digging into what changed in the new csv library, it no longer supports an encoding option that indicates the csv should be transcoded (ie "binary:utf-8"). However, it turns out csv never supported transcoding from an IO stream on initialization and would only read the input encoding. From 2.6.6. to 2.7 this is made explicit because it no longer parses the encoding option to separate input and output encodings. The upshot is that this option was never transcoding anyway so removing it should not change the behavior we see.
The upgrade also resulted in several deprecation warnings that are resolved here related to the way ruby 2.7 handles keyword arguments (see https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/).
Rollbar is updated here to accomodate another deprecation warning. This required a minor spec change as rollbar no longer sends the accesss_token in the payload (see https://github.com/rollbar/rollbar-gem/pull/966)

Code checks and manual testing are both looking good here, so let's ship


Auto generate main index.js file

Review plan

[ ] Checkout this branch
[ ] Delete the lib folder
[ ] Run npm run build:release
[ ] Confirm that there is a lib/index.js file with all the module exports
[ ] Run the app locally
[ ] Go to http://react.ions:3000/components/
[ ] Click through all the components in the sidebar to make sure everything still works

@samageloff please review when you have some free time. No rush

@jivinivan if you can give this a review - great!

@jivinivan @Chochek you think we can get this out the door? This PR will make the upgrade path to Ions a little bit easier, as the import syntax will match.


mWeb - Expense -Title text moves left to right on tapping back arrow

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: V9. 0.74-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Open a workspace chat with few expenses
Open the expense report
Tap header - title
Paste https://staging.new.expensify.com/r/2348509720956985 and save it
Tap on title and then tap on top left arrow and go back
While performing step 6, note the text in title field.

Expected Result:
In expense report title page, the text must not move left to right on tapping back arrow on top left.
Actual Result:
In expense report title page, the text moves left to right on tapping back arrow on top left.
Workaround:
Unknown
Platforms:

[ ] Android: Standalone
[ ] Android: HybridApp
[x] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/74aa3f9c-4236-494b-a01d-1180fb1381c4
View all open jobs on GitHub

Hey @IuliiaHerets can you point to the timestamp in the video where the bug is happening? I'm not seeing any weird behavior here

@stephanieelliott Around the 18th second in the video, you can try it

This is a minor display display issue it's hardly noticeable. I am gonna close this but will add the 'Not a Priority` label in case we want to address it later.


ENH support all input length

resolves #39

@xir4n many thanks for this. kindly merge at your convenience


s3 input with cloudtrail codec not working with gzipped files

Not sure if this is a problem with s3 input plugin or the cloudtrail codec...  but I can't seem to get the s3 input with cloudtrail codec working if the file is gzipped (which is the default for cloudtrail). It does work if I download the file, unzip it, and upload it back into a different S3 bucket.
logstash 2.2.2
logstash-input-s3 2.0.4
logstash-codec-cloudtrail 2.0.2
I started out with a normal cloudtrail bucket created by AWS, and a simple config like this:
input {
    s3 {
        bucket => "cloudtrail-logs"
        codec => cloudtrail {}
    }
}

output {
    stdout { codec => rubydebug }
}

When I run logstash with --debug, I see this:
S3 input: Adding to objects[] {:key=>"AWSLogs/blahblah/CloudTrail/us-east-1/2016/03/15/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"116", :method=>"list_new_files"}
S3 input processing {:bucket=>"cloud-analytics-platform-cloudtrail-logs", :key=>"AWSLogs/blahblah/CloudTrail/us-east-1/2016/03/15/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"150", :method=>"process_files"}
S3 input: Download remote file {:remote_key=>"AWSLogs/blahblah/CloudTrail/us-east-1/2016/03/15/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :local_filename=>"/var/folders/8f/1bjm5vq53c73tjq0yl4560dj1r5f6h/T/logstash/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"344", :method=>"download_remote_file"}
Processing file {:filename=>"/var/folders/8f/1bjm5vq53c73tjq0yl4560dj1r5f6h/T/logstash/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"182", :method=>"process_local_log"}
Pushing flush onto pipeline {:level=>:debug, :file=>"logstash/pipeline.rb", :line=>"450", :method=>"flush"}
Pushing flush onto pipeline {:level=>:debug, :file=>"logstash/pipeline.rb", :line=>"450", :method=>"flush"}
Pushing flush onto pipeline {:level=>:debug, :file=>"logstash/pipeline.rb", :line=>"450", :method=>"flush"}

And it just keeps printing that last line over and over and never does anything else. If I go look in /var/folders/8f/1bjm5vq53c73tjq0yl4560dj1r5f6h/T/logstash/ I do indeed see a gzipped file, blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz .
Now, if I unzip this file, and create myself a test bucket, and put the unzipped file into the test bucket, and run logstash pointing at my test bucket, it works fine!
According to the docs at https://www.elastic.co/guide/en/logstash/current/plugins-inputs-s3.html , if the filename ends in .gz then the s3 input should handle it automatically.

This looks like a bug in the S3 input plugin
On Wed, Mar 16, 2016, 02:57 kevinpauli<EMAIL_ADDRESS>wrote:

Not sure if this is a problem with s3 input plugin or the cloudtrail
codec... but I can't seem to get the s3 input with cloudtrail codec working
if the file is gzipped (which is the default for cloudtrail). It does work
if I download the file, unzip it, and put upload it back to the S3 bucket.
logstash 2.2.2
logstash-input-s3 2.0.4
logstash-codec-cloudtrail 2.0.2
I started out with a normal cloudtrail bucket created by AWS, and a simple
config like this:
input {
s3 {
bucket => "cloudtrail-logs"
codec => cloudtrail {}
}
}
output {
stdout { codec => rubydebug }
}
When I run logstash with --debug, I see this:
S3 input: Adding to objects[] {:key=>"AWSLogs/blahblah/CloudTrail/us-east-1/2016/03/15/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"116", :method=>"list_new_files"}
S3 input processing {:bucket=>"cloud-analytics-platform-cloudtrail-logs", :key=>"AWSLogs/blahblah/CloudTrail/us-east-1/2016/03/15/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"150", :method=>"process_files"}
S3 input: Download remote file {:remote_key=>"AWSLogs/blahblah/CloudTrail/us-east-1/2016/03/15/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :local_filename=>"/var/folders/8f/1bjm5vq53c73tjq0yl4560dj1r5f6h/T/logstash/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"344", :method=>"download_remote_file"}
Processing file {:filename=>"/var/folders/8f/1bjm5vq53c73tjq0yl4560dj1r5f6h/T/logstash/blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz", :level=>:debug, :file=>"logstash/inputs/s3.rb", :line=>"182", :method=>"process_local_log"}
Pushing flush onto pipeline {:level=>:debug, :file=>"logstash/pipeline.rb", :line=>"450", :method=>"flush"}
Pushing flush onto pipeline {:level=>:debug, :file=>"logstash/pipeline.rb", :line=>"450", :method=>"flush"}
Pushing flush onto pipeline {:level=>:debug, :file=>"logstash/pipeline.rb", :line=>"450", :method=>"flush"}
And it just keeps printing that last line over and over and never does
anything else. If I go look in
/var/folders/8f/1bjm5vq53c73tjq0yl4560dj1r5f6h/T/logstash/ I do indeed see
a gzipped file,
blahblah_CloudTrail_us-east-1_20160315T1520Z_qQm4gunsTnNuJosk.json.gz .
Now, if I unzip this file, and create myself a test bucket, and put the
unzipped file into the test bucket, and run logstash pointing at my test
bucket, it works fine!
According to the docs at
https://www.elastic.co/guide/en/logstash/current/plugins-inputs-s3.html ,
if the filename ends in .gz then the s3 input should handle it
automatically.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/logstash-plugins/logstash-codec-cloudtrail/issues/6

@kevinpauli I am facing the same issue. Were you able to make this work?

No, I eventually gave up on logstash.  I ended up sending logs from CloudTrail to CloudWatch, and then from CloudWatch to ElasticSearch as described here: http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/CWL_ES_Stream.html

I just got this working few minutes ago 👍
Here's my config.. maybe this will help someone.
`input {
s3 {
access_key_id => ""
bucket => "bucketname"
region => "us-east-1"
secret_access_key => ""
prefix => "AWSLogs/AccountID/CloudTrail/us-east-1/"
type => "s3"
add_field => { source => gzfiles }
codec => cloudtrail {}
}
}
output {
elasticsearch {
host => localhost
protocol => http
}
}         `

Any movement on this issue?

This is not a bug in the cloudtrail codec. This codec assumes the files where gunzipped the s3 input plugin.


[FEATURE]: option to increase rate limits

What problem does it solve
Some projects and applications will require higher rate limits than the current configuration allows
What is the solution
A system that allows higher rate limits for certain clients.
The main reason for the rate limits currently is to make sure the system stays within the limits of the current hosting plan, higher funding allows for higher limits thus allowing higher rate limits.
Existing alternatives
Use the existing rate limits
Added value
Allows certain clients to use higher rate limits for more demanding applications
Additional notes
Specifics on how this should be implemented needs to be discussed.

Would self-hosting this API not be a better workaround for people that need higher limits?

Would be fine if the rate limit was configurable by environment variable.
As far as I can see, there's already a TODO for that:
https://github.com/helldivers-2/api/blob/f2992c626725a3bef26831cd07bc624704febc2b/src/Helldivers-2-API/Middlewares/RateLimitMiddleware.cs#L12-L14
This way, self-hosted deployments can customize the rate limit (possibly to infinite) and the public endpoint can keep its rate limits like they currently are.
This was the case before the switch to .NET and I was very happy with it.

self hosting would definitely be the primary way to go for people if they need higher rate limits etc, however we need 2 things in place for that to be viable at this moment:

like @stnokott mentions it needs to be configurable through environment variables
this needs to be properly documented (as requested in #46)

As mentioned in docs/containers.md, deployment-specific options can be supplied as environment variables if they are present in src/Helldivers-2-API/appsettings.json.
So moving the two rate-limit parameters mentioned in https://github.com/helldivers-2/api/issues/70#issuecomment-2051479635 to appsettings.json should solve this issue, right?

100% correct, next step would indeed be moving rate limits to configuration.


Add a model for CoSQL

Hi, amazing work!
Would it be possible to add a pretrained docker model t5.1.1.lm100k.large for CoSQL?

Hi @ReinierKoops!
This has been requested before, https://github.com/ElementAI/picard/issues/23 😄
I haven't trained such a model yet. I'll look into it.

Thank you :)

Hi @ReinierKoops,
I've added a t5.1.1.lm100k.large model for CoSQL, https://github.com/ElementAI/picard/commit/f19c49c0b232bcffe7f4fc79b3ffe0ddd382f4ef.


Buggy

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I don't see anything actionable here so I'm going to close this issue. If you have further information to provide, please leave a comment.


Does the size of the input image have to be [720,1280] ? When testing images of other sizes, an indexError is always reported.

What need to do if want to test images of different sizes? Thanks very much.

similar error, I believe the network has SPP so the input size should not be a factor, should be the visualisation code fixing the size. I see similar errors:
python tools/demo.py ...
 line 57, in show_seg_result
    img[color_mask != 0] = img[color_mask != 0] * 0.5 + color_seg[color_mask != 0] * 0.5
IndexError: boolean index did not match indexed array along dimension 0; dimension is 1208 but corresponding boolean dimension is 1116

me too, how to solve it ?

@shgrace233 @Miaonika @timothylimyl @callmesora
u have to set default image size
(python3 demo.py --img-size = int())
or put resizing in DemoDataset.py
if self.video_flag[self.count]:
           # Read video
           self.mode = 'video'
           ret_val, img0 = self.cap.read()
           img0 = cv2.resize(img0, (640,640))

Just like @saitishmukhametov mentioned before, do resizing in lib/dataset/DemoDataset.py:
        if self.video_flag[self.count]:
            # Read video
            self.mode = 'video'
            ret_val, img0 = self.cap.read()
            # **Resize**
            img0 = cv2.resize(img0, (self.img_size, self.img_size))
            if not ret_val:
                self.count += 1
                self.cap.release()
                if self.count == self.nf:  # last video
                    raise StopIteration
                else:
                    path = self.files[self.count]
                    self.new_video(path)
                    ret_val, img0 = self.cap.read()
            h0, w0 = img0.shape[:2]

            self.frame += 1
            print('\n video %g/%g (%g/%g) %s: ' % (self.count + 1, self.nf, self.frame, self.nframes, path), end='')

        else:
            # Read image
            self.count += 1
            img0 = cv2.imread(path, cv2.IMREAD_COLOR | cv2.IMREAD_IGNORE_ORIENTATION)  # BGR
            #img0 = cv2.cvtColor(img0, cv2.COLOR_BGR2RGB)
            assert img0 is not None, 'Image Not Found ' + path
            print('image %g/%g %s: \n' % (self.count, self.nf, path), end='')
            # **Resize**
            img0 = cv2.resize(img0, (self.img_size, self.img_size))
            h0, w0 = img0.shape[:2]

if not is_demo:
    img = cv2.resize(img, (result.shape[1], result.shape[0]), interpolation=cv2.INTER_LINEAR)
else:
    img = cv2.resize(img, (result[0].shape[1], result[0].shape[0]), interpolation=cv2.INTER_LINEAR)

img[color_mask != 0] = img[color_mask != 0] * 0.5 + color_seg[color_mask != 0] * 0.5

This will solve your problem

Hey buddy, where do I change this code？

of you solve it? I have the same problem

me too


Add option to not reload automatically, let the user call aliv.reload() by himself if he wants to

Right now, every file being watched and modified will trigger the reload call; but sometimes the user wants to control that in a different way, like executing other tasks before actually reloading the browser.

Closed by: f71b4fd.


ValueError: strides is not compatible with available memory

I am trying to subscribe to a msgfy-ied image and that is leading to a value error.
On the publisher side,
 imgpub = rospy.Publisher("/env_level/labelled_image", Image, queue_size=10)
 imgpub.publish(label_image)

def get_label_image():
        im = pilimg.open("label.png")  # Image from PIL
        label = np.asarray(im)
        print (np.shape(label))
        message = msgify(Image, label, encoding="mono8")
        message.height = np.shape(label)[1]
        message.width = np.shape(label)[0]
        return message

On the subscriber callback,
def lblimg_callback(self, lblimg_data):
      self.label_image = lblimg_data
      im = numpify(self.label_image)

Which leads to the error.
For information, np.intp is int64

Can you show the full error?


etl and literature-etl

Hi, What is the difference and connection between the two directories（etl and literature-etl）? Thanks!

This is nothing significant about the directory names. The etl directory contains the outputs generated through the ETL project, and the literature-etl outputs are generated through the ETL Literature project. At some point the ETL Literature code will be migrated into the ETL and we'd expect from that point on only to have a single output directory (see: opentargets#1793).


devilutionx: minor cleanup after review

Motivation for this change
thank you very much @SuperSandro2000 for your suggestions in https://github.com/NixOS/nixpkgs/pull/144569!
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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 wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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.

ping @karolchmist

Will leave the merge part to @SuperSandro2000 just in case he remembers something else.

Am I the only one that can't run it with this PR?
I get :
Couldn't find matching render driver

The error occured at: SourceX/display.cpp line 218

It works if I build the previous PR
Here is the screenshot:

?

Eh? As @thiagokokada mentioned:

No-op, good signal.

This PR didn't actually change anything :eyes: You're sure the previous PR builds? I force pushed after your initial test...

I've just re-built both PRs with nixpkgs-review pr XXX, and https://github.com/NixOS/nixpkgs/pull/144569 works, whereas this one still fails. Maybe if there is a "cache" or something I should remove in order to make it build from scratch?
If it's only me, then nevermind...

If you do nix-collect-garbage the build cache should be removed.
Also you only need a GITHUB_TOKEN if you want to interact with GitHub or are rate limited.

@karolchmist please confirm when you get things working!

I've just re-built both PRs with nixpkgs-review pr XXX, and #144569 works, whereas this one still fails. Maybe there is a "cache" or something I should remove in order to make it build from scratch?
If it's only me, then nevermind...

Can you check the /nix/store hash. Here on my computer, using master branch, I have the following for x86_64-linux (that hits the Hydra cache so it doesn't build locally unless forced): /nix/store/3d6x5xkk9hnlg7zl6dxx8ak53k31597q-devilutionx-1.3.0
I ran the binary and looks fine. It showed one screen asking for the required diabdat.mpq or spawn.mpq files.

I found the reason: I had installed devilutionx with nix-env -i, so that's why I could find its executable in this PR. I uninstalled it and I could no longer run it. Everything is correct, sorry for the confusion!


[PT/XLA] Add many more ResNet50 tests

Description
Porting several existing variants of this test to the new system.
@JackCaoG let me know if there's another nightly variant that you want to add here.
Tests
Checked DAG construction:

Checklist
Before submitting this PR, please make sure (put X in square brackets):

[x] I have performed a self-review of my code.
[x] I have necessary comments in my code, particularly in hard-to-understand areas.
[x] I have run one-shot tests and provided workload links above if applicable.
[x] I have made or will make corresponding changes to the doc if needed.

Thanks Will! The screenshot is nice, but I will probably prefer to have a link of the test that could direct me to original tests (composer env).

Makes sense. I skipped actually running any of these in this case because there are too many and these tests have already been running in the old system for a while. We also know that other variants have been passing in airflow.


Add instructions on how to find the rails server on Windows

Hi,
I am trying to run the Ohana API locally on a Windows 8.1 machine, and I have followed the instructions on the Ohana API virtual machine installation guide for Windows step by step. I am able to get the rails server up and running in the virtual machine:
=> Booting Puma
=> Rails 4.2.1 application starting in development on http://localhost:8080
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
Puma 2.11.2 starting...
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://localhost:8080

However, when I got to http://localhost:8080 in my web browser I only get back "Server not found".
If I try to see the virtual machine in the web browser it seems to be working okay, http://<IP_ADDRESS>:2222  returns:
SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
Please help me (and others with this issue) access the rails server running in the virtual machine, from Windows!
Thanks!

Thanks for using Ohana API, and thanks for the bug report. I will update the instructions, but in the meantime, you can run the app with puma -p 8080 instead of rails s -p 8080.

Thank you, that worked!


Message filtering did not account for message with only attachments

There was a mute issued to an user after posting 5 messages with 5 attachments. The bot issued a mute and treated accordingly against message spamming behaviour, however in this case there are two problems:

They were messages with empty message contents, only attachments.
The attachments were completely deleted, and there is no way to know what they were.

The log of the case looks like this
Deleted by: Python#4329
Date: Oct. 23, 2019, 6:54 a.m.
A̷k̴a̴s̵h̶#4646Oct. 23, 2019, 6:54 a.m. | User ID:<PHONE_NUMBER>98284554
A̷k̴a̴s̵h̶#4646Oct. 23, 2019, 6:54 a.m. | User ID:<PHONE_NUMBER>98284554
A̷k̴a̴s̵h̶#4646Oct. 23, 2019, 6:54 a.m. | User ID:<PHONE_NUMBER>98284554
A̷k̴a̴s̵h̶#4646Oct. 23, 2019, 6:54 a.m. | User ID:<PHONE_NUMBER>98284554
A̷k̴a̴s̵h̶#4646Oct. 23, 2019, 6:54 a.m. | User ID:<PHONE_NUMBER>98284554

The following codes might be of interest:
    """Detects duplicated messages sent by a single user."""
    relevant_messages = tuple(
        msg
        for msg in recent_messages
        if (
            msg.author == last_message.author
            and msg.content == last_message.content
        )
    )

    total_duplicated = len(relevant_messages)

    if total_duplicated > config['max']:
        ...

Which is in duplicates.py

Hi, I would like to work on it please.

Assigning @Akarys42 - If you have any question, don't hesitate to post yours in the dev channel.

As far as I can tell, the mute was issued because of the duplicate of message, but if this rule haven't trigger, the attachment rule would have trigger anyway, and my testing shown that attachment trigger first. What do you want me to do?

Yes, the duplicates rule was the one that triggered here.
I don't think @ikuyarihS intention is to stop antispam from triggering, but rather to make sure we still get the information: What kind of attachments were deleted? I think we could just relay them to the mod-alerts channel to retain them, regardless of the rule that deleted the attachment. I'm not that concerned about a couple of additional messages in that channel, since it's not a "conversation" channel. (Other mods may, though.)

Okay I though @ikuyarihS wanted to stop it from triggering if the images are differents. I can make the link appear on https://admin.pythondiscord.com/ instead if some mods doesn't want it to appear in mod-alert.
I also get an error about the cog trying to delete the same message twice that I will probably try to investigate.

That's an interesting idea. Since we're only allowing image attachments anyway, we could upload the attachment links and display the images directly in the front-end, Just like regular content or embeds.

Done in python-discord/site#303.


Properly retry in TestPiggyback

Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

integ-ipv6_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

integ-ipv6_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

integ-ipv6_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

integ-ipv6_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

integ-ipv6_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-multicluster

integ-cni_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-basic-arm64

lint_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test lint

analyze-tests_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test analyze-tests

integ-ipv6_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot-multicluster

integ-cni_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-cni

integ-pilot_istio
e53471c45cfb08863cbd3c2830d07f06d74da785
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Isssue passing timestamps with ms precision

I am trying to import 200M CSV records into clickhouse to take it for a spin. I have the following schema
CREATE TABLE vod (
  createdAt DateTime,
  sessionId String,
  deviceId String,
  clientTimestamp DateTime,
  event String,
  publisherId String,
  mediaId String,
  mediaDuration Float32,
  remoteAddress String,
  fromPosition Float32,
  toPosition Float32,
  secondsViewed Float32,
  browser String,
  os String,
  platform String,
  version String,
  plugin String,
  timezoneOffset Int16,
  url String,
  altMediaId String,
  clockDifferential Int32,
  seriesName String,
  episodeName String,
  channel String,
  classification String,
  errors UInt16,
  vendorVersion String,
  screenType String,
  protocolVersion String,
  publisherName String,
  genre String,
  programId String,
  programName String,
  demo1 String,
  demo2 String,
  demo3 String,
  connectionType String,
  streamingType String,
  longitude Float32,
  latitude Float32,
  id String,
  mediaType String,
  insertedAt DateTime,
  clientDeviceId String,
  endpoint String
)
ENGINE = Merge(createdAt, (publisherName, createdAt), 8192);

The problem i have is that createdAt is specified as 2016-07-14T14:00:00.002Z, which is causing issues when i try and import the data.  Here is the error below
ubuntu@secondary-realtime:/vol/20160715/vod/data$ cat 00.csv | clickhouse-client --query="INSERT INTO vod FORMAT CSV"
Code: 27.
ERROR: Date must be in YYYY-MM-DD format.

: (at row 1)

ubuntu@secondary-realtime:/vol/20160715/vod/data$ clickhouse-client
ClickHouse client version 1.1.53988.
Connecting to localhost:9000.
Connected to ClickHouse server version 1.1.53988.

Here is a typical row of CSV.
2016-07-14T14:00:00.002Z,35d326b8-d9df-f916-2926-feca78234209,ae533d61912a45a76462f3bde8b44b89,2016-07-14T14:00:00.164Z,PROGRESS,f0619170-c1e9-47cf-b347-f068ee3a3b65,9264697,2580,d4
50eaf3215d99090b6be9ec76d088a1,1173.9,1233.9,60,IE,Windows 8,Microsoft Windows,8.0,shim,600, , ,-162, , , , ,0,Publisher1-PC-1.90-CV-1.8,tablet,1,Publisher1, , , , , , , , , , ,981bc1632b
e4f5d6fdec020b96c129a8,vod, , ,meter

Do you have any advice on how i can proceed?

I had a similar question earlier about recommendations for storing currencies. The answer was multiply by 100 an store it in UInt32/64. So I assume it similar here: Use Epoch TS x 1000 and store it as UInt64.

Probably better solution is to store milliseconds separately as mentioned here:
https://groups.google.com/d/msg/clickhouse/N9tjlgNFnvU/3wPcGpqYAQAJ
Also note, that first parameter of MergeTree engine need to be column of type Date (not DateTime) that is used as partition key. You may have column createdDate DEFAULT toDate(createdAt) for that purpose.

when support datetime with millisecond?


⚠ ClamAV has degraded performance

In 6b6f24e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 192 ms

Resolved: ClamAV performance has improved in 6f03826.


ArrayMesh text resources always saved as binary

Godot version
3.4.4-stable
System information
Windows 10
Issue description
I use the ResourceSaver to save meshes as text for debugging when I suspect that meshes are not being imported correctly from the DCC. Upon investigation, it turns out that text resources (.tres) are now being saved as binary, even when explicitly telling ArrayMesh to NOT use compression on method add_surface_from_arrays (compress_flags = 0) and ResourceSaver's save method (flags = 0).
The thing is, it wasn't like this a few versions ago.
Saving a single vertex, such as Vector3(-1.0, 0.0, 1.0), would result in a .tres file with:
...
"array_vertex_data": PoolVector3Array( Vector3( -1.0, 0.0, 1.0)),
...

Now, it yields:
...
"array_data": PoolByteArray( 0, 0, 128, 191, 0, 0, 0, 0, 0, 0, 128, 63 ),
...

Converting to hex, that is clearly 0xbf800000, 0x00000000 and 0x3f800000, which are the hex-float IEEE 754 representations of -1.0, 0.0 and 1.0 respectively.
Text resources were supposed to be human-readable, and to a certain point they were. I even tried on 3.5-rc1, but the issue is still present.
Steps to reproduce
I've included a mrp below. Just extract it and run. It should create and save a buggy_mesh.tres ArrayMesh text resource file on the project's root folder.
Minimal reproduction project
array_mesh_resource_saver_bug.zip

Upon investigation, it turns out that text resources (.tres) are now being saved as binary

Which Godot version was the first one to exhibit this new behavior?

Closing due to lack of response, if you provide the requested information this can be reopened


SPARKC-433: Correct order of "Limit" and "orderBy" clauses in JWCT

JoinWithCassandraTable places limit and order queries in the wrong
order. Thanks to<EMAIL_ADDRESS>for pointing this out.

Build against Scala 2.10 finished with failure

Build against Scala 2.11 finished with failure

+1

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success


[VS Code] An error occurred while sending the request.

Error:
An error occurred while sending the request.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.198

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.23.1

platformName
Linux

platformVersion
4.4.0-127-generic

@leuthera Thanks for reporting this! We're tracking this issue via #466, so I'm going to close this is a duplicate. On #466, could you let us know which Linux distro you're running, and attach the log file you get after running the Live Share: Export Logs command in the command palette? Thanks!


Not all disks are displayed

Output of fastfetch --logo none --structure Disk
Disk (/): 16.93 GiB / 93.93 GiB (18%)

Output of df
Filesystem            Size  Used Avail Use% Mounted on
udev                   32G     0   32G   0% /dev
/dev/mapper/pve-root   94G   13G   78G  14% /
/dev/nvme0n1p2        511M  328K  511M   1% /boot/efi
/dev/mapper/hdd-hdd   2.7T   56K  2.6T   1% /hdd
/dev/sda1             1.8T  1.5T  212G  88% /nas
/dev/fuse             128M   24K  128M   1% /etc/pve

My config:
--structure Title:Separator:OS:Host:Kernel:Uptime:Shell:Resolution:DE:WM:Terminal:CPU:GPU:Memory:Disk:Battery:LocalIP
--host-format "{/2}{-}{/}{2}{?3} {3}{?}"
--os-format "{3} {12}"
--resolution-format "{}x{}"
--de-format "{2} {3}"
--memory-format "{/1}{-}{/}{/2}{-}{/}{} / {}"
--gpu-key "GPU"
--resolution-key "Resolution"

Is this a bug, or did configure it wrongly?

Please try the dev branch, it got fixes in that area.

I could fix it by mentioning the disks individually in the config.


QOS tag section clarification

clarify restrictions on QOS tags for traffic

@S-AA-RON : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

@GitHubber17 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Faker Image

Could You remove curl() condition in Provider/Image.php - just  $success = copy($url, $filepath); works great.
In curl condition there is a problem with unlink() function before fclose().
  /*
        // save file
        if (function_exists('curl_exec')) {
            // use cURL
            $fp = fopen($filepath, 'w');
            $ch = curl_init($url);
            curl_setopt($ch, CURLOPT_FILE, $fp);
            $success = curl_exec($ch) && curl_getinfo($ch, CURLINFO_HTTP_CODE) === 200;

            if ($success) {
                fclose($fp);
            } else {
                unlink($filepath);
            }

            curl_close($ch);
        } elseif (ini_get('allow_url_fopen')) {
            // use remote fopen() via copy()
            $success = copy($url, $filepath);
        } else {
            return new \RuntimeException('The image formatter downloads an image from a remote HTTP server. Therefore, it requires that PHP can request remote hosts, either via cURL or fopen()');
        }
        */
        $success = copy($url, $filepath);`

there is a problem with unlink() function before fclose()

Can you be more specific?

In my experience, I was getting this error
Message: unlink(D:/path/to/facker/img/**e496355.jpg): Permission denied
I've solved it adding this lines before CURLOPT_FILE:
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); curl_setopt($ch, CURLOPT_FILE, $fp);

Fixed in #1319


fix(tests): update integration test targets to use fulfillment in async context

Issue #

Description

General Checklist

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #3294 (df31bad) into main (86d7adf) will increase coverage by 0.02%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main    #3294      +/-   ##
==========================================
+ Coverage   64.27%   64.30%   +0.02%
==========================================
  Files        1075     1075
  Lines       35880    35880
==========================================
+ Hits        23063    23071       +8
+ Misses      12817    12809       -8

Flag
Coverage Δ

API_plugin_unit_test
67.07% <ø> (ø)

AWSPluginsCore
66.15% <ø> (ø)

Amplify
47.84% <ø> (ø)

Analytics_plugin_unit_test
81.37% <ø> (ø)

Auth_plugin_unit_test
74.01% <ø> (+0.07%)
:arrow_up:

CoreMLPredictions_plugin_unit_test
59.44% <ø> (ø)

DataStore_plugin_unit_test
80.07% <ø> (ø)

Geo_plugin_unit_test
70.75% <ø> (ø)

Logging_plugin_unit_test
63.09% <ø> (ø)

Predictions_plugin_unit_test
37.29% <ø> (ø)

PushNotifications_plugin_unit_test
60.29% <ø> (ø)

Storage_plugin_unit_test
54.24% <ø> (ø)

unit_tests
64.30% <ø> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 6 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Window resize

I'm asking this question since last time I got no response. Why on click on a variable in Variable Explorer window, Spyder main window resizes to a small size? This has ben existing for a while now. Only using Spyder in fullscreen mode, one doesn't see this problem. Why this is not being fixed? I'm running the latest Spyder 5.0 on macOS 11.2

I encountered this problem too, but only for pandas.DataFrame or numpy.ndarray type, when opening a list or dictionary, the window won't be resized.

Hi @Tissot11 thanks for the feedback, could you provide a GIF or screen capture of the behavior you are experiencing? Also, did you submit previously an issue then? Could you link it here then please? Also, could you provide us the information regarding your setup and a small code example which triggers this behavior systematically for you? @williamjin1992 Maybe could you give us more information to replicate this in our side too?
Any information in order to reproduce this is greatly appreciated, thanks!

Thanks @dalthviz and @williamjin1992 . I attach a screen recording of the issue.
https://user-images.githubusercontent.com/31315017/113919037-6a328c00-97e3-11eb-9a04-786a81813efc.mp4

This is a problem with macOS that merges windows related to the same application into a single one.
@steff456, is there a Mac setting that prevents this behavior?

I have turned off the Group windows by applications in Mission Control but I still see this behaviour. So perhaps some settings adjustments in Spyder can help.

Perhaps this is a problem with Qt, the graphical toolkit used by Spyder. Maybe in more recent Qt versions this fixed (the latest one we support is 5.15).

I have installed Spyder 5.0  both standalone and from conda. I see the same problem in both apps. So unfortunately, it is not fixed in new Spyder.