Agent disconnect after idle exits non-zero

Agent version: v3.33.3
Sadly I don't have a whole lot of diagnostic information but I'm happy to generate more and provide it. The last few months we have been using the self-termination option as documented in several of the posts about more effective scaling policies. We solely scale down our buildkite agent pool by configuring the agent to self-terminate after 25 minutes of idle, and having the systemd hook to remove the agent from the ASG.
Not often, but enough to be annoying, an agent will terminate in the middle of a job. Currently the only records we have of this are in the Buildkite job log which simply reads Exited with status -1 (agent lost).
If there are some basic debug logs we can enable that would capture what's going on here, I'd be all for it.
EDIT: As you can see from my later comments, this is really about the agent exiting non-zero from a disconnection, which triggers systemd to restart the unit - thus causing our early termination when the agent receives another job.

@ohookins are you using the Elastic CI Stack for AWS? If so, could you share the parameters for your stack ensuring not to include any agent token value?
Do you use on-demand or spot EC2 instances?
Are your agent logs being streamed to CloudWatch? If so, could you grab a copy of the agent logs on an instance where this has happened so we can reconstruct a timeline?

We're not using the elastic CI stack, although the config files we are using for systemd agent termination, and the agent settings themselves to set that up are directly taken from the elastic CI stack. It would be a large effort to migrate over unfortunately so we're continuing with our custom setup.
Currently we are using on-demand instances so we don't have any instances being taken away early - it should only be the agents themselves self-terminating.
I'll try to grab some logs from when this is happening and forward it on.

2021-11-12 02:11:29 INFO   ip-10-10-128-133-1 All agents have been idle for 1543 seconds. Disconnecting...
2021-11-12 02:11:29 INFO   ip-10-10-128-133-1 Disconnecting...
sleeping for 10 seconds before terminating instance to allow agent logs to drain to cloudwatch...
_) \|                              \| \|  \| \|__  _   _ _\| \| __\| \| \| ___\| \|_ ___    __ _  __ _  ___ _ __ \| \|_  \| '_ \\| \| \| \| \| \|/ _` \| \|/ / \| __/ _ \  / _` \|/ _` \|/ _ \ '_ \\| __\|  \| \|_) \| \|_\| \| \| \| (_\| \|   <\| \| \|\|  __/ \| (_\| \| (_\| \|  __/ \| \| \| \|_  \|_.__/ \__,_\|_\|_\|\__,_\|_\|\_\_\|\__\___\|  \__,_\|\__, \|\___\|_\| \|_\|\__\|                                                 __/ \| https://buildkite.com/agent                    \|___/
2021-11-12 01:45:37 NOTICE Starting buildkite-agent v3.33.3 with PID: 1681

Actually the logs suggest that the sleep of 10 seconds is too long, and the systemd unit for buildkite-agent is restarting the service after the configured value of 5 seconds, which means the instance is scheduled for shutdown but technically buildkite-agent restarts and starts accepting new jobs.
I'm going to tune this in our environment (the values are based on the Elastic CI Stack scripts, as we just copied them to our deployment) and see if that fixes it. Looking at this, it seems unlikely to be a bug in the agent itself but more likely in the Elastic CI Stack scripts ,so I'll close this issue.

OK, have tracked down the issue a bit closer. I'm wondering whether this may actually be an agent fault. Here is the last bit of the log from the agent itself:
2021-11-15 00:46:16 INFO   ip-10-10-128-137-1 Process with PID: 4816 finished with Exit Status: 0, Signal: nil
2021-11-15 00:46:16 INFO   ip-10-10-128-137-1 Finished job 4ecac449-dddd-450d-90c5-0eacff494e19
2021-11-15 01:12:30 INFO   ip-10-10-128-137-1 All agents have been idle for 1567 seconds. Disconnecting...
2021-11-15 01:12:30 INFO   ip-10-10-128-137-1 Disconnecting...

Here's the log from systemd:
Nov 15 01:12:31 ip-10-10-128-137 systemd[1]: buildkite-agent.service: Control process exited, code=exited status=1
Nov 15 01:12:31 ip-10-10-128-137 systemd[1]: buildkite-agent.service: Failed with result 'exit-code'.

So it actually does seem like the agent inconsistently exits with the correct exit code. Since the systemd unit is configured to restart on error, it restarts the agent but then the instance terminates which causes the problem of dropping jobs that have been started.
I'll enable debug in the agent and see if I get any further context on this.

Sadly enabling debug doesn't shed any more light on the issue.
2021-11-15 03:33:28 INFO   ip-10-10-130-161-1 All agents have been idle for 1593 seconds. Disconnecting...
2021-11-15 03:33:28 INFO   ip-10-10-130-161-1 Disconnecting...
2021-11-15 03:33:28 DEBUG  POST https://agent.buildkite.com/v3/disconnect
2021-11-15 03:33:28 DEBUG  ip-10-10-130-161-1 Stopping heartbeats
2021-11-15 03:33:28 DEBUG  ↳ POST https://agent.buildkite.com/v3/disconnect proto=HTTP/1.1 status=200 Δ=49.118495ms

Still get an exit code of 1 after this.

It's weird, there really only appears to be one place where this would exit with 1 afaict: https://github.com/buildkite/agent/blob/848a053b3131ebced93d829c3215b31bddd19f72/main.go#L123-L126
Like there's other places it would due to malformed command or config, but that the agent runs means this is the code path where the exit code comes from. And then only if there was some error and it immediately logs that.
I half remember seeing it before where logging doesn't appear right before an os.exit as that kills the process before it can be written to stdout. Might be as easy as adding a pause or flush here.

We're also experiencing this issue and have been seeing it alot more often in the past couple of months. Is there some debugging information we can give Buildkite to help address this issue?

We have used cloudformation stacks to deploy agents on aws.

this issue is over a year and nobody from Buildkite is looking into it?

hey friends! sorry we've taken so long to get back on this - it's one of those ones that got lost in the churn a little bit.
this issue is really difficult to debug because of its nature as something intermittent, and because it's an issue with shutdown - there's not much state left to investigate after it's happened, after all! unfortunately, as it is, there's probably not enough information here for us to investigate deeply, or to issue a fix
we've done a little bit of looking into things from our end though, and we've come up with a little bit more information. To @liath's comment:

It's weird, there really only appears to be one place where this would exit with 1 afaict: https://github.com/buildkite/agent/blob/848a053b3131ebced93d829c3215b31bddd19f72/main.go#L123-L126

i don't think this is 100% true - my suspicion is that this 1 exit code is coming from a call to log.Fatal, which calls exitFunc (which in this case is just os.Exit) with exit status 1.
given that the agent logs seem to say that they're disconnecting, it seems likely to me that something in this process is going sideways, and causing the agent to shut down before it's properly disconnected - perhaps there's a timeout being hit or something.
one other thing to note is that we fairly recently added retries to the disconnect process, and made the disconnect process print Disconnected. when it's done disconnecting. If this line isn't present in your logs and you're running a relatively recent version of the agent, it likely means that something is going wrong with the disconnection, potentially a serverside issue on our part. if that turns out to be the case, let me know and i can raise it with the relevant people internally, but note that disconnection is a best-effort process, and we might not be able to get a 100% success rate on this API call.
i'm sorry that we can't give a more definitive resolution (or a resolution at all) to this issue, but we'd be more than happy to accept PRs making this issue easier to debug.
<3 benno


only allow lowering maxResults and maxIntermediateRows from groupBy query context

see https://github.com/druid-io/druid/pull/2584#issuecomment-193894113
that PR got merged, so incorporating it here.

:+1:


SSH service connection private keys

SSH service connection section provides no guidance on what types of keys are supported: RSA, DSA, ECDSA, ED25519, PEM format, etc.

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

ID: 72b90dd0-49f9-4ed4-3010-9a64dde6ae5a
Version Independent ID: 6e679d50-4e94-eee3-8793-af884cc909ca
Content: Service connections in Azure Pipelines and Team Foundation Server - Azure Pipelines
Content Source: docs/pipelines/library/service-endpoints.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

The task uses the SSH llibraries, and so supports the key types it uses. The SSH docs at https://www.ssh.com/ssh/public-key-authentication discuss key types. See also the library at https://github.com/mscdex/ssh2.
This information was taken from a similar question at the end of the topic at https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/copy-files-over-ssh: It did not add support for the newer OpenSSH key format until version v0.7.0. (See this issue for more info: mscdex/ssh2#746). The task version 0.148 update will have v0.8 of the ssh2 library and support for the new OpenSSH key format. Prior to that task version, the -m PEM flag must be passed to ssh-keygen so that the key works with the task. The newer version of the task should be rolling out in the next few weeks.


Improve menu information

Right Click to Center would be helpful to add to Help menu
Esc to close menu
add POI" to Help Menu (Ctrl+ Left Click)
Control+Scroll to zoom is also not in menu

Too general, going to close this one.

Thank you Nico.
On Tue, Oct 22, 2019, 6:38 PM Nico Kemnitz<EMAIL_ADDRESS>wrote:

Closed #163 https://github.com/seung-lab/neuroglancer/issues/163.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/seung-lab/neuroglancer/issues/163?email_source=notifications&email_token=ABDOZZRKHCOV6RDIHK6LBQ3QP56FDA5CNFSM4DUW3NEKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUMC2URY#event-2735057479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDOZZQRMQCBQ6KTQWJYWUTQP56FDANCNFSM4DUW3NEA
.


Upgrading to latest causes Lambdas to fail

We've been using 0.0.1-beta.2 for a while successfully.  There was a message in the Sentry console today that we should update to 0.1.0 so we did.  Local testing seemed fine but when running in an actual environment (Lambda based) for some reason it short circuited all processing of the function.  Rolling back to the older version resolved it.  Any idea what may be causing this?  Are there code changes we should be making to get on to the current version?

@mattcollum all breaking changes are marked here in the changelog - https://github.com/getsentry/sentry-go/blob/master/CHANGELOG.md
Do you have any more insights for this issue? I'll take a look at it first thing on Monday.

I just tested everything on AWS and it seems to work just fine. When working with serverless solutions, you may want to take a look at https://docs.sentry.io/platforms/go/transports and use HTTPSyncTransport now, as it doesn't require Flush calls.

@kamilogorek sorry for the delayed response.  holiday long weekend here :)
so the Lambdas just seem to exit after we init sentry and call defer sentry.Recover().
The init is pretty straightforward.  Calls to sentry include the following the first time:
sentry.Init with Dsn, AttachStacktrace and BeforeSend
And on subsequent calls if the Lambda was already inititalized we're calling:
sentry.ConfigureScope(func(scope *sentry.Scope) { 			scope.Clear() 		})
Haven't had a chance to review the change log or look into HTTPSyncTransport as we're pretty busy right now but can look down the road for sure.  For now I've locked the version back to beta.2 and it's working again.  If you happen to see anything in this init or Recover calls that could be the cause let me know

@mattcollum if you don't await event delivery, your lambda will instantly exit the process. You have to either flush the queue manually or use SyncTransport. Although I wonder how it's possible that it worked in beta.2 without it?
Just deployed code below to Lambda and can confirm that it correctly reports to Sentry:
package main

import (
	"encoding/json"
	"errors"
	"fmt"
	"github.com/aws/aws-lambda-go/lambda"
	"github.com/getsentry/sentry-go"
)

func foo() error {
	return bar()
}

func bar() error {
	return baz()
}

func baz() error {
	panic(errors.New("boom"))
}

func HandleRequest() (string, error) {
	defer sentry.Recover()
	foo()
	return "Mkey", nil
}

func main() {
	sentry.Init(sentry.ClientOptions{
		Dsn<EMAIL_ADDRESS>		Transport: sentry.NewHTTPSyncTransport(),
	})

	lambda.Start(HandleRequest)
}

Added the SyncTransport and took out flushes and that seems to be working fine.  Issue seems to be caused by something I'm doing to clear the scope between requests.

Currrently calling this on the second request and onwards before processing starts"

sentry.ConfigureScope(func(scope *sentry.Scope) {
			scope.Clear()
		})

Then we add some tags:

sentry.ConfigureScope(func(scope *sentry.Scope) {
scope.SetTags(tags)
})
First time the lambda runs the scope.SetTags is fine.  Second time I'm getting:
runtime.plainError
assignment to entry in nil map
Let me know if there is a better way to reset scopes between requests


Issue using "attributeExists" in list resolver

Describe the bug
I have a list query resolver that is the standard generated by Amplify. However, when I execute a query using the operator "attributeExists" as shown below it generates an error.
query search{
  listAssets(
  	filter:{assetStatus:{attributeExists: false}}
    limit:10
  )
  {items{id}}
}

The error that is generated from what should be a straight forward query looks like this
{
  "data": {
    "listAssets": null
  },
  "errors": [
    {
      "path": [
        "listAssets"
      ],
      "data": null,
      "errorType": "DynamoDB:DynamoDbException",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "ExpressionAttributeValues must not be empty (Service: DynamoDb, Status Code: 400, Request ID: CGT0NK9ADHR8LVODDPV68N3B37VV4KQNSO5AEMVJF66Q9ASUAAJG, Extended Request ID: null)"
    }
  ]
}

Amplify CLI Version
4.29.8
To Reproduce
Execute a simple query like that shown above
Expected behavior
Data matching the query is returned without error

Hello @sacrampton
I was able to reproduce this and it seems that it's coming from the toDynamoDBFilterExpression utility in AppSync. I've noticed the team of this change, though I would also recommend their support forum for further visibility. https://forums.aws.amazon.com/forum.jspa?forumID=280
A potential workaround I can think of would be to remove it if there are no expression values.
#if( $context.args.filter )
  #set( $filter = $util.parseJson($util.transform.toDynamoDBFilterExpression($ctx.args.filter)))
  #if($filter.expressionValues.keySet().size() < 1)
  	$util.qr($filter.remove("expressionValues"))
  #end
  #set( $ListRequest.filter = $filter )
#end

Closing as this is a dependency is an issue. The AppSync team has been made aware of this issue.

7 months later and still an issue...


Cannot install: "node" not found

On Ubuntu 14.04, NodeJS is available under the command "nodejs" instead of "node".
Hence some packages cannot be installed through npm (namely "fibers"), and datastringer sets the wrong command to give to crontab.
z$ ./install.sh                                                                    [14-08-26 13:13]
Installing datastringer, hang on tight...
Installing postfix
[sudo] password for vpaleologue:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-generic
Use 'apt-get autoremove' to remove it.
Suggested packages:
  procmail postfix-mysql postfix-pgsql postfix-ldap postfix-pcre sasl2-bin
  dovecot-common postfix-cdb postfix-doc
The following NEW packages will be installed:
  postfix
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 1 085 kB of archives.
After this operation, 3 609 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty/main postfix amd64 2.11.0-1 [1 085 kB]
Fetched 1 085 kB in 0s (4 589 kB/s)
Preconfiguring packages ...
Selecting previously unselected package postfix.
(Reading database ... 382023 files and directories currently installed.)
Preparing to unpack .../postfix_2.11.0-1_amd64.deb ...
Unpacking postfix (2.11.0-1) ...
Processing triggers for ufw (0.34~rc-0ubuntu2) ...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db (<IP_ADDRESS>-1) ...
Setting up postfix (2.11.0-1) ...
Adding group `postfix' (GID 126) ...
Done.
Adding system user `postfix' (UID 116) ...
Adding new user `postfix' (UID 116) with group `postfix' ...
Not creating home directory `/var/spool/postfix'.
Creating /etc/postfix/dynamicmaps.cf
Adding tcp map entry to /etc/postfix/dynamicmaps.cf
Adding sqlite map entry to /etc/postfix/dynamicmaps.cf
Adding group `postdrop' (GID 127) ...
Done.
/etc/aliases does not exist, creating it.

Postfix was not set up.  Start with
  cp /usr/share/postfix/main.cf.debian /etc/postfix/main.cf
.  If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed.  To view Postfix configuration
values, see postconf(1).

After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

Processing triggers for ufw (0.34~rc-0ubuntu2) ...
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for libc-bin (2.19-0ubuntu6.1) ...
postfix installed!
Installing node
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-generic
Use 'apt-get autoremove' to remove it.
The following extra packages will be installed:
  libc-ares2 libv8-3.14.5
The following NEW packages will be installed:
  libc-ares2 libv8-3.14.5 nodejs
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 1 912 kB of archives.
After this operation, 7 538 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty/main libc-ares2 amd64 1.10.0-2 [38,5 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ trusty/universe libv8-3.14.5 amd64 <IP_ADDRESS>-5ubuntu2 [1 189 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ trusty/universe nodejs amd64 0.10.25~dfsg2-2ubuntu1 [684 kB]
Fetched 1 912 kB in 0s (3 821 kB/s)
Selecting previously unselected package libc-ares2:amd64.
(Reading database ... 382213 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.10.0-2_amd64.deb ...
Unpacking libc-ares2:amd64 (1.10.0-2) ...
Selecting previously unselected package libv8-3.14.5.
Preparing to unpack .../libv8-3.14.5_<IP_ADDRESS>-5ubuntu2_amd64.deb ...
Unpacking libv8-3.14.5 (<IP_ADDRESS>-5ubuntu2) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_0.10.25~dfsg2-2ubuntu1_amd64.deb ...
Unpacking nodejs (0.10.25~dfsg2-2ubuntu1) ...
Processing triggers for doc-base (0.10.5) ...
Processing 1 added doc-base file...
Processing triggers for man-db (<IP_ADDRESS>-1) ...
Setting up libc-ares2:amd64 (1.10.0-2) ...
Setting up libv8-3.14.5 (<IP_ADDRESS>-5ubuntu2) ...
Setting up nodejs (0.10.25~dfsg2-2ubuntu1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.19-0ubuntu6.1) ...
node installed!
Installing npm
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-generic
Use 'apt-get autoremove' to remove it.
The following extra packages will be installed:
  gyp javascript-common libc-ares-dev libjs-node-uuid libssl-dev libssl-doc
  libv8-3.14-dev node-abbrev node-ansi node-archy node-async node-block-stream
  node-combined-stream node-cookie-jar node-delayed-stream node-forever-agent
  node-form-data node-fstream node-fstream-ignore node-github-url-from-git
  node-glob node-graceful-fs node-gyp node-inherits node-ini
  node-json-stringify-safe node-lockfile node-lru-cache node-mime
  node-minimatch node-mkdirp node-mute-stream node-node-uuid node-nopt
  node-normalize-package-data node-npmlog node-once node-osenv node-qs
  node-read node-read-package-json node-request node-retry node-rimraf
  node-semver node-sha node-sigmund node-slide node-tar node-tunnel-agent
  node-which nodejs-dev
Suggested packages:
  apache2 lighttpd httpd node-hawk node-aws-sign node-oauth-sign
  node-http-signature
The following NEW packages will be installed:
  gyp javascript-common libc-ares-dev libjs-node-uuid libssl-dev libssl-doc
  libv8-3.14-dev node-abbrev node-ansi node-archy node-async node-block-stream
  node-combined-stream node-cookie-jar node-delayed-stream node-forever-agent
  node-form-data node-fstream node-fstream-ignore node-github-url-from-git
  node-glob node-graceful-fs node-gyp node-inherits node-ini
  node-json-stringify-safe node-lockfile node-lru-cache node-mime
  node-minimatch node-mkdirp node-mute-stream node-node-uuid node-nopt
  node-normalize-package-data node-npmlog node-once node-osenv node-qs
  node-read node-read-package-json node-request node-retry node-rimraf
  node-semver node-sha node-sigmund node-slide node-tar node-tunnel-agent
  node-which nodejs-dev npm
0 upgraded, 53 newly installed, 0 to remove and 1 not upgraded.
Need to get 3 361 kB of archives.
After this operation, 14,4 MB of additional disk space will be used.
Do you want to continue?
(Reading database ... 382315 files and directories currently installed.)
Preparing to unpack .../gyp_0.1~svn1729-3ubuntu1_all.deb ...
Unpacking gyp (0.1~svn1729-3ubuntu1) ...
Selecting previously unselected package javascript-common.
Preparing to unpack .../javascript-common_11_all.deb ...
Unpacking javascript-common (11) ...
Selecting previously unselected package libjs-node-uuid.
Preparing to unpack .../libjs-node-uuid_1.4.0-1_all.deb ...
Unpacking libjs-node-uuid (1.4.0-1) ...
Selecting previously unselected package libssl-dev:amd64.
Preparing to unpack .../libssl-dev_1.0.1f-1ubuntu2.5_amd64.deb ...
Unpacking libssl-dev:amd64 (1.0.1f-1ubuntu2.5) ...
Selecting previously unselected package libssl-doc.
Preparing to unpack .../libssl-doc_1.0.1f-1ubuntu2.5_all.deb ...
Unpacking libssl-doc (1.0.1f-1ubuntu2.5) ...
Selecting previously unselected package libv8-3.14-dev.
Preparing to unpack .../libv8-3.14-dev_<IP_ADDRESS>-5ubuntu2_amd64.deb ...
Unpacking libv8-3.14-dev (<IP_ADDRESS>-5ubuntu2) ...
Selecting previously unselected package node-async.
Preparing to unpack .../node-async_0.2.5-1_all.deb ...
Unpacking node-async (0.2.5-1) ...
Selecting previously unselected package node-node-uuid.
Preparing to unpack .../node-node-uuid_1.4.0-1_all.deb ...
Unpacking node-node-uuid (1.4.0-1) ...
Selecting previously unselected package libc-ares-dev:amd64.
Preparing to unpack .../libc-ares-dev_1.10.0-2_amd64.deb ...
Unpacking libc-ares-dev:amd64 (1.10.0-2) ...
Selecting previously unselected package node-abbrev.
Preparing to unpack .../node-abbrev_1.0.4-2_all.deb ...
Unpacking node-abbrev (1.0.4-2) ...
Selecting previously unselected package node-ansi.
Preparing to unpack .../node-ansi_0.2.1-1_all.deb ...
Unpacking node-ansi (0.2.1-1) ...
Selecting previously unselected package node-archy.
Preparing to unpack .../node-archy_0.0.2-1_all.deb ...
Unpacking node-archy (0.0.2-1) ...
Selecting previously unselected package node-inherits.
Preparing to unpack .../node-inherits_2.0.0-1_all.deb ...
Unpacking node-inherits (2.0.0-1) ...
Selecting previously unselected package node-block-stream.
Preparing to unpack .../node-block-stream_0.0.7-1_all.deb ...
Unpacking node-block-stream (0.0.7-1) ...
Selecting previously unselected package node-delayed-stream.
Preparing to unpack .../node-delayed-stream_0.0.5-1_all.deb ...
Unpacking node-delayed-stream (0.0.5-1) ...
Selecting previously unselected package node-combined-stream.
Preparing to unpack .../node-combined-stream_0.0.4-1_all.deb ...
Unpacking node-combined-stream (0.0.4-1) ...
Selecting previously unselected package node-cookie-jar.
Preparing to unpack .../node-cookie-jar_0.3.1-1_all.deb ...
Unpacking node-cookie-jar (0.3.1-1) ...
Selecting previously unselected package node-forever-agent.
Preparing to unpack .../node-forever-agent_0.5.1-1_all.deb ...
Unpacking node-forever-agent (0.5.1-1) ...
Selecting previously unselected package node-mime.
Preparing to unpack .../node-mime_1.2.11-1_all.deb ...
Unpacking node-mime (1.2.11-1) ...
Selecting previously unselected package node-form-data.
Preparing to unpack .../node-form-data_0.1.0-1_all.deb ...
Unpacking node-form-data (0.1.0-1) ...
Selecting previously unselected package node-rimraf.
Preparing to unpack .../node-rimraf_2.2.2-2_all.deb ...
Unpacking node-rimraf (2.2.2-2) ...
Selecting previously unselected package node-mkdirp.
Preparing to unpack .../node-mkdirp_0.3.5-1_all.deb ...
Unpacking node-mkdirp (0.3.5-1) ...
Selecting previously unselected package node-graceful-fs.
Preparing to unpack .../node-graceful-fs_2.0.0-2_all.deb ...
Unpacking node-graceful-fs (2.0.0-2) ...
Selecting previously unselected package node-fstream.
Preparing to unpack .../node-fstream_0.1.24-1_all.deb ...
Unpacking node-fstream (0.1.24-1) ...
Selecting previously unselected package node-lru-cache.
Preparing to unpack .../node-lru-cache_2.3.1-1_all.deb ...
Unpacking node-lru-cache (2.3.1-1) ...
Selecting previously unselected package node-sigmund.
Preparing to unpack .../node-sigmund_1.0.0-1_all.deb ...
Unpacking node-sigmund (1.0.0-1) ...
Selecting previously unselected package node-minimatch.
Preparing to unpack .../node-minimatch_0.2.12-1_all.deb ...
Unpacking node-minimatch (0.2.12-1) ...
Selecting previously unselected package node-fstream-ignore.
Preparing to unpack .../node-fstream-ignore_0.0.6-2_all.deb ...
Unpacking node-fstream-ignore (0.0.6-2) ...
Selecting previously unselected package node-github-url-from-git.
Preparing to unpack .../node-github-url-from-git_1.1.1-1_all.deb ...
Unpacking node-github-url-from-git (1.1.1-1) ...
Selecting previously unselected package node-glob.
Preparing to unpack .../node-glob_3.2.6-1_all.deb ...
Unpacking node-glob (3.2.6-1) ...
Selecting previously unselected package nodejs-dev.
Preparing to unpack .../nodejs-dev_0.10.25~dfsg2-2ubuntu1_amd64.deb ...
Unpacking nodejs-dev (0.10.25~dfsg2-2ubuntu1) ...
Selecting previously unselected package node-nopt.
Preparing to unpack .../node-nopt_2.1.2-1_all.deb ...
Unpacking node-nopt (2.1.2-1) ...
Selecting previously unselected package node-npmlog.
Preparing to unpack .../node-npmlog_0.0.4-1_all.deb ...
Unpacking node-npmlog (0.0.4-1) ...
Selecting previously unselected package node-osenv.
Preparing to unpack .../node-osenv_0.0.3-1_all.deb ...
Unpacking node-osenv (0.0.3-1) ...
Selecting previously unselected package node-tunnel-agent.
Preparing to unpack .../node-tunnel-agent_0.3.1-1_all.deb ...
Unpacking node-tunnel-agent (0.3.1-1) ...
Selecting previously unselected package node-json-stringify-safe.
Preparing to unpack .../node-json-stringify-safe_5.0.0-1_all.deb ...
Unpacking node-json-stringify-safe (5.0.0-1) ...
Selecting previously unselected package node-qs.
Preparing to unpack .../node-qs_0.6.5-1_all.deb ...
Unpacking node-qs (0.6.5-1) ...
Selecting previously unselected package node-request.
Preparing to unpack .../node-request_2.26.1-1_all.deb ...
Unpacking node-request (2.26.1-1) ...
Selecting previously unselected package node-semver.
Preparing to unpack .../node-semver_2.1.0-2_all.deb ...
Unpacking node-semver (2.1.0-2) ...
Selecting previously unselected package node-tar.
Preparing to unpack .../node-tar_0.1.18-1_all.deb ...
Unpacking node-tar (0.1.18-1) ...
Selecting previously unselected package node-which.
Preparing to unpack .../node-which_1.0.5-2_all.deb ...
Unpacking node-which (1.0.5-2) ...
Selecting previously unselected package node-gyp.
Preparing to unpack .../node-gyp_0.10.10-2_all.deb ...
Unpacking node-gyp (0.10.10-2) ...
Selecting previously unselected package node-ini.
Preparing to unpack .../node-ini_1.1.0-1_all.deb ...
Unpacking node-ini (1.1.0-1) ...
Selecting previously unselected package node-lockfile.
Preparing to unpack .../node-lockfile_0.4.1-1_all.deb ...
Unpacking node-lockfile (0.4.1-1) ...
Selecting previously unselected package node-mute-stream.
Preparing to unpack .../node-mute-stream_0.0.3-1_all.deb ...
Unpacking node-mute-stream (0.0.3-1) ...
Selecting previously unselected package node-normalize-package-data.
Preparing to unpack .../node-normalize-package-data_0.2.2-1_all.deb ...
Unpacking node-normalize-package-data (0.2.2-1) ...
Selecting previously unselected package node-once.
Preparing to unpack .../node-once_1.1.1-1_all.deb ...
Unpacking node-once (1.1.1-1) ...
Selecting previously unselected package node-read.
Preparing to unpack .../node-read_1.0.4-1_all.deb ...
Unpacking node-read (1.0.4-1) ...
Selecting previously unselected package node-read-package-json.
Preparing to unpack .../node-read-package-json_1.1.3-1_all.deb ...
Unpacking node-read-package-json (1.1.3-1) ...
Selecting previously unselected package node-retry.
Preparing to unpack .../node-retry_0.6.0-1_all.deb ...
Unpacking node-retry (0.6.0-1) ...
Selecting previously unselected package node-sha.
Preparing to unpack .../node-sha_1.2.3-1_all.deb ...
Unpacking node-sha (1.2.3-1) ...
Selecting previously unselected package node-slide.
Preparing to unpack .../node-slide_1.1.4-1_all.deb ...
Unpacking node-slide (1.1.4-1) ...
Selecting previously unselected package npm.
Preparing to unpack .../npm_1.3.10~dfsg-1_all.deb ...
Unpacking npm (1.3.10~dfsg-1) ...
Processing triggers for man-db (<IP_ADDRESS>-1) ...
Processing triggers for doc-base (0.10.5) ...
Processing 4 added doc-base files...
Setting up gyp (0.1~svn1729-3ubuntu1) ...
Setting up javascript-common (11) ...
Setting up libjs-node-uuid (1.4.0-1) ...
Setting up libssl-dev:amd64 (1.0.1f-1ubuntu2.5) ...
Setting up libssl-doc (1.0.1f-1ubuntu2.5) ...
Setting up libv8-3.14-dev (<IP_ADDRESS>-5ubuntu2) ...
Setting up node-async (0.2.5-1) ...
Setting up node-node-uuid (1.4.0-1) ...
Setting up libc-ares-dev:amd64 (1.10.0-2) ...
Setting up node-abbrev (1.0.4-2) ...
Setting up node-ansi (0.2.1-1) ...
Setting up node-archy (0.0.2-1) ...
Setting up node-inherits (2.0.0-1) ...
Setting up node-block-stream (0.0.7-1) ...
Setting up node-delayed-stream (0.0.5-1) ...
Setting up node-combined-stream (0.0.4-1) ...
Setting up node-cookie-jar (0.3.1-1) ...
Setting up node-forever-agent (0.5.1-1) ...
Setting up node-mime (1.2.11-1) ...
Setting up node-form-data (0.1.0-1) ...
Setting up node-rimraf (2.2.2-2) ...
Setting up node-mkdirp (0.3.5-1) ...
Setting up node-graceful-fs (2.0.0-2) ...
Setting up node-fstream (0.1.24-1) ...
Setting up node-lru-cache (2.3.1-1) ...
Setting up node-sigmund (1.0.0-1) ...
Setting up node-minimatch (0.2.12-1) ...
Setting up node-fstream-ignore (0.0.6-2) ...
Setting up node-github-url-from-git (1.1.1-1) ...
Setting up node-glob (3.2.6-1) ...
Setting up nodejs-dev (0.10.25~dfsg2-2ubuntu1) ...
Setting up node-nopt (2.1.2-1) ...
Setting up node-npmlog (0.0.4-1) ...
Setting up node-osenv (0.0.3-1) ...
Setting up node-tunnel-agent (0.3.1-1) ...
Setting up node-json-stringify-safe (5.0.0-1) ...
Setting up node-qs (0.6.5-1) ...
Setting up node-request (2.26.1-1) ...
Setting up node-semver (2.1.0-2) ...
Setting up node-tar (0.1.18-1) ...
Setting up node-which (1.0.5-2) ...
Setting up node-gyp (0.10.10-2) ...
Setting up node-ini (1.1.0-1) ...
Setting up node-lockfile (0.4.1-1) ...
Setting up node-mute-stream (0.0.3-1) ...
Setting up node-normalize-package-data (0.2.2-1) ...
Setting up node-once (1.1.1-1) ...
Setting up node-read (1.0.4-1) ...
Setting up node-read-package-json (1.1.3-1) ...
Setting up node-retry (0.6.0-1) ...
Setting up node-sha (1.2.3-1) ...
Setting up node-slide (1.1.4-1) ...
Setting up npm (1.3.10~dfsg-1) ...
npm installed!
 Sit back and relax!

Note: I'm not that relaxed, currently.

basilesimon, can u give me a hand here? During the install process, I have several 'command not found' alerts, as below.
[code]
Installing datastringer, hang on tight...
./install.sh: line 9: dpkg-query: command not found
Installing postfix
Password:
sudo: apt-get: command not found
postfix installed!
Installing node
sudo: apt-get: command not found
node installed!
usage: which [-as] program ...
Installing npm
sudo: apt-get: command not found
npm installed!
Installing needed node modules
./install.sh: line 42: npm: command not found
Setting up CRON job
"-":1: bad minute
crontab: errors in crontab file, can't install
Done! Sit back and relax!
[/code]
The [code]node wizard.js[/code] does not work either.
I'm not that relaxed either...
thanks in advance

hey @moxphere, what OS are you trying to run Datastringer on?

Hi, @basilesimon : I am running it on OSX El Capitan. Only now I am seeing that there are restrictions regarding the OS. Is it possible to use on a Mac? Thanks


Invalid Configuration User::identityClass must be set.

is need create /src/models/User.php ?
or
remove views/*  \Yii::$app->user ?

You only need set the User identity in your config components:
components => [
    ...,
    'user' => [
         'identityClass' => 'app\models\User', // User must implement the IdentityInterface
    ]
]

all right.
The project did not create app\models\User.
need add  app\models\User file

I intend to fix the bug of this project recently.
make it work.


enable self-service for aws group and policy

https://issues.redhat.com/browse/APPSRE-7806

/retest


Chore: updated chown command in docker.md

Updated command in docker.md! Let me know if any other changes are needed
References this issue: https://github.com/verdaccio/website/issues/132

Are the people who open PRs responsible for merging or is that left up to maintainers?

I'm not sure about this after read this. https://stackoverflow.com/questions/34831861/can-i-assume-that-nobody-is-65534  I need more approvals before merge it.

I think this was a misunderstanding. Only members with write rights can merge and only if there are at least two successful reviews.

I think this was a misunderstanding. Only members with write rights can merge and only if there are at least two successful reviews.

At least 1 approving review is required by reviewers with write access.

I think this was a misunderstanding. Only members with write access can merge and only if there are at least two successful reviews.

At least 1 approving review is required by reviewers with write access.

10001 is the normal / arbitary user in a Docker context. Which we already use at https://verdaccio.org/docs/en/docker.html
cat /etc/passwd in our Docker image should show the correct values for the user nobody.

~ $ cat /etc/passwd
root:x:0:0:root:/root:/bin/ash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/var/spool/mail:/sbin/nologin
news:x:9:13:news:/usr/lib/news:/sbin/nologin
uucp:x:10:14:uucp:/var/spool/uucppublic:/sbin/nologin
operator:x:11:0:operator:/root:/bin/sh
man:x:13:15:man:/usr/man:/sbin/nologin
postmaster:x:14:12:postmaster:/var/spool/mail:/sbin/nologin
cron:x:16:16:cron:/var/spool/cron:/sbin/nologin
ftp:x:21:21::/var/lib/ftp:/sbin/nologin
sshd:x:22:22:sshd:/dev/null:/sbin/nologin
at:x:25:25:at:/var/spool/cron/atjobs:/sbin/nologin
squid:x:31:31:Squid:/var/cache/squid:/sbin/nologin
xfs:x:33:33:X Font Server:/etc/X11/fs:/sbin/nologin
games:x:35:35:games:/usr/games:/sbin/nologin
postgres:x:70:70::/var/lib/postgresql:/bin/sh
cyrus:x:85:12::/usr/cyrus:/sbin/nologin
vpopmail:x:89:89::/var/vpopmail:/sbin/nologin
ntp:x:123:123:NTP:/var/empty:/sbin/nologin
smmsp:x:209:209:smmsp:/var/spool/mqueue:/sbin/nologin
guest:x:405:100:guest:/dev/null:/sbin/nologin
nobody:x:65534:65534:nobody:/:/sbin/nologin
node:x:1000:1000:Linux User,,,:/home/node:/bin/sh
verdaccio:x:10001:65533:verdaccio user:/opt/verdaccio:/sbin/nologin

So if we need the nobody user it should be 65534, not 65533 which is the verdaccio user.

Thanks for the insight @DanielRuf. What user do we want in this regard? The nobody user or the verdaccio user?

chown is user:group.
The groups are the following:
~ $ cat /etc/group
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin,adm
adm:x:4:root,adm,daemon
tty:x:5:
disk:x:6:root,adm
lp:x:7:lp
mem:x:8:
kmem:x:9:
wheel:x:10:root
floppy:x:11:root
mail:x:12:mail
news:x:13:news
uucp:x:14:uucp
man:x:15:man
cron:x:16:cron
console:x:17:
audio:x:18:
cdrom:x:19:
dialout:x:20:root
ftp:x:21:
sshd:x:22:
input:x:23:
at:x:25:at
tape:x:26:root
video:x:27:root
netdev:x:28:
readproc:x:30:
squid:x:31:squid
xfs:x:33:xfs
kvm:x:34:kvm
games:x:35:
shadow:x:42:
postgres:x:70:
cdrw:x:80:
usb:x:85:
vpopmail:x:89:
users:x:100:games
ntp:x:123:
nofiles:x:200:
smmsp:x:209:smmsp
locate:x:245:
abuild:x:300:
utmp:x:406:
ping:x:999:
nogroup:x:65533:verdaccio
nobody:x:65534:
node:x:1000:node

So for verdaccio:verdaccio or verdaccio:nogroup it is 10001:65533
verdaccio:x:10001:65533:verdaccio user:/opt/verdaccio:/sbin/nologin
nogroup:x:65533:verdaccio

Which is what this PR lists as the updated user:group
Unless is that not correct? Sorry if I'm failing to follow 😅

Not sure why we had 100:101 in the docs so far. The owner should be the verdaccio user probably.
https://security.stackexchange.com/a/175594
In my opinion 10001:65533should be correct but I did not test this.

Which is what this PR lists as the updated user:group
Unless is that not correct? Sorry if I'm failing to follow 😅

Right. Just explaining the details behind this. These should be the correct values for our Docker image.

Gotcha. Thank you for the explanation!

Thanks @DanielRuf , these docs has evolved perhaps with the enough background about the real meaning for our Docker image. Glad we are getting in shape in this area. kudos @sumanbh and @ShawnToubeau 🥇


fix authentication cookie issue

This is the proof of concept of how to handle 401 status so that users can be informed and provide a chance to reauthenticate if the session is expired.
Followings are the changes done:

added a state called isSessionExpired to track session expiration status.
moved sendRequestCommon to be part of AuthProvider hook so that if 401 status is returned from the backend via sendRequestCommon then it can set the states in AuthProvider which sits on top of any other components in ConsoleMe to control things globally.
Searched places where sendRequestCommon is being used and replaced with this logic including components that are not yet React Hooks.
Components in blocks directory and some of helper util.js are not updated yet which requires more work. I will do this once this proof of concept is valid.

How to test this:

First visit Self Service Page then it will pop up a modal for reauthentication.
I have updated the backend endpoint /api/v2/self_service_config to return 401 via AJAX and sendRequestCommon will set isSessionExpired to true so that a Modal will be returned to allow people to reauthenticate
Once you click the button in the modal, we want to redirect the user to the IDP for login once more. The redirect URL should be configurable and returned from the backend so that it can bet set to the state and the modal can use it.

Updated the rest of the codes to use the sendRequestCommon, SendRequestV2, sendRequestPolicy from AuthProvider to interact with the state for showing re-authenticate modal when it's getting 401 status.
I decided not to migrate the completion code Ace editor which is still used in SelfService Step 3 instead we will migrate it to Monaco.
Another area, I found challenging to handle backend calls is Monaco autocomplete typeahead backend call. The completion logic needs to be assigned to the global variable of Monaco and hard to pass the states from AuthProvider.
Instead, I just added a sendRequestCommon just for this complete logic which handles the 401 status by returning null.
We will test this on the staging temporarily for some time since this is a big change and I realized that we didn't a good job at handling exceptions upon fetching data from the backend. I suggest we should spend time standardise our message exchange format between the frontend and the backend.

Updated the rest of the codes to use the sendRequestCommon, SendRequestV2, sendRequestPolicy from AuthProvider to interact with the state for showing re-authenticate modal when it's getting 401 status.
I decided not to migrate the completion code Ace editor which is still used in SelfService Step 3 instead we will migrate it to Monaco.
Another area, I found challenging to handle backend calls is Monaco autocomplete typeahead backend call. The completion logic needs to be assigned to the global variable of Monaco and hard to pass the states from AuthProvider.
Instead, I just added a sendRequestCommon just for this complete logic which handles the 401 status by returning null.
We will test this on the staging temporarily for some time since this is a big change and I realized that we didn't a good job at handling exceptions upon fetching data from the backend. I suggest we should spend time standardise our message exchange format between the frontend and the backend.


SHOW MEASUREMENTS with multiple WHERE conditions

Seeing some unexpected behavior when trying to query for a list of all measurements that contain a particular combination of tag keys (specific key/value pairs aren't relevant, just measurements that are part of a series with any number of tag keys.
I'm trying to reduce a list of possible measurements based on the presence of an arbitrary number of tags.  Below, I would have expected the third query SHOW MEASUREMENTS WHERE host <> '' AND cpu <> '' to return all four cpu-based measurements.  Not sure if I'm using the query language incorrectly or potentially a bug with SHOW MEASUREMENTS.
Querying using Telegraf data:
> SHOW MEASUREMENTS WHERE cpu <> ''
name: measurements
------------------
name
cpu_idle
cpu_nice
cpu_system
cpu_user

> SHOW MEASUREMENTS WHERE host <> ''
name: measurements
------------------
name
cpu_idle
cpu_nice
cpu_system
cpu_user
disk_free
disk_inodes_free
// ...

> SHOW MEASUREMENTS WHERE host <> '' AND cpu <> ''
>

We've confirmed that we can at least work around this issue with regular expressions:
SHOW MEASUREMENTS WHERE host =~ // AND cpu =~ //

The above empty regular expression workaround applies when looking for measurements containing a key, but it does not work when using a value.
> SHOW SERIES WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
name: cpu_idle
--------------
_key						cpu	host
cpu_idle,cpu=cpu0,host=Wills-MacBook-Pro	cpu0	Wills-MacBook-Pro

name: cpu_nice
--------------
_key						cpu	host
cpu_nice,cpu=cpu0,host=Wills-MacBook-Pro	cpu0	Wills-MacBook-Pro

name: cpu_system
----------------
_key						cpu	host
cpu_system,cpu=cpu0,host=Wills-MacBook-Pro	cpu0	Wills-MacBook-Pro

name: cpu_user
--------------
_key						cpu	host
cpu_user,cpu=cpu0,host=Wills-MacBook-Pro	cpu0	Wills-MacBook-Pro

> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" =~ /cpu0/ AND "host" =~ /Wills-MacBook-Pro/

Upon further review, SHOW MEASUREMENTS sometimes works.
influx console:
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
name: measurements
------------------
name
cpu_user

> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
name: measurements
------------------
name
cpu_idle

> SHOW MEASUREMENTS WHERE "cpu" = 'cpu0' AND "host" = 'Wills-MacBook-Pro'
name: measurements
------------------
name
cpu_idle

influxd output:
[wal] 2015/09/16 09:36:17 Flush due to idle. Flushing 9 series with 9 points and 603 bytes from partition 1
[wal] 2015/09/16 09:36:17 write to index of partition 1 took 747.628µs
[query] 2015/09/16 09:36:19 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:19 <IP_ADDRESS> - - [16/Sep/2015:09:36:19 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 99 - InfluxDBShell/0.9 0f25ddf3-5c91-11e5-8024-000000000000 1.626963ms
[query] 2015/09/16 09:36:20 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:20 <IP_ADDRESS> - - [16/Sep/2015:09:36:20 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 0f766d70-5c91-11e5-8025-000000000000 490.778µs
[query] 2015/09/16 09:36:21 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:21 <IP_ADDRESS> - - [16/Sep/2015:09:36:21 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 0fe6b70a-5c91-11e5-8026-000000000000 1.795654ms
[http] 2015/09/16 09:36:22 <IP_ADDRESS> - - [16/Sep/2015:09:36:22 -0700] POST /write?consistency=&db=telegraf&precision=&rp= HTTP/1.1 204 0 - InfluxDBClient 109a0f89-5c91-11e5-8027-000000000000 1.26227ms
[wal] 2015/09/16 09:36:27 Flush due to idle. Flushing 132 series with 132 points and 2244 bytes from partition 1
[wal] 2015/09/16 09:36:27 write to index of partition 1 took 2.689172ms
[wal] 2015/09/16 09:36:27 Flush due to idle. Flushing 9 series with 9 points and 603 bytes from partition 1
[wal] 2015/09/16 09:36:27 write to index of partition 1 took 1.653036ms
[http] 2015/09/16 09:36:32 <IP_ADDRESS> - - [16/Sep/2015:09:36:32 -0700] POST /write?consistency=&db=telegraf&precision=&rp= HTTP/1.1 204 0 - InfluxDBClient 168fce3e-5c91-11e5-8028-000000000000 1.371578ms
[wal] 2015/09/16 09:36:37 Flush due to idle. Flushing 132 series with 132 points and 2244 bytes from partition 1
[wal] 2015/09/16 09:36:37 write to index of partition 1 took 5.792992ms
[wal] 2015/09/16 09:36:37 Flush due to idle. Flushing 9 series with 9 points and 603 bytes from partition 1
[wal] 2015/09/16 09:36:37 write to index of partition 1 took 1.327826ms
[http] 2015/09/16 09:36:42 <IP_ADDRESS> - - [16/Sep/2015:09:36:42 -0700] POST /write?consistency=&db=telegraf&precision=&rp= HTTP/1.1 204 0 - InfluxDBClient 1c8596cf-5c91-11e5-8029-000000000000 1.260942ms
[wal] 2015/09/16 09:36:47 Flush due to idle. Flushing 132 series with 132 points and 2244 bytes from partition 1
[wal] 2015/09/16 09:36:47 write to index of partition 1 took 4.519299ms
[wal] 2015/09/16 09:36:47 Flush due to idle. Flushing 9 series with 9 points and 603 bytes from partition 1
[wal] 2015/09/16 09:36:47 write to index of partition 1 took 1.448022ms
[http] 2015/09/16 09:36:52 <IP_ADDRESS> - - [16/Sep/2015:09:36:52 -0700] POST /write?consistency=&db=telegraf&precision=&rp= HTTP/1.1 204 0 - InfluxDBClient 227b9f43-5c91-11e5-802a-000000000000 1.53705ms
[query] 2015/09/16 09:36:57 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:57 <IP_ADDRESS> - - [16/Sep/2015:09:36:57 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2557c20c-5c91-11e5-802b-000000000000 1.809096ms
[query] 2015/09/16 09:36:57 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:57 <IP_ADDRESS> - - [16/Sep/2015:09:36:57 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 25a0cc8c-5c91-11e5-802c-000000000000 572.044µs
[wal] 2015/09/16 09:36:57 Flush due to idle. Flushing 132 series with 132 points and 2244 bytes from partition 1
[wal] 2015/09/16 09:36:57 write to index of partition 1 took 7.161735ms
[wal] 2015/09/16 09:36:57 Flush due to idle. Flushing 9 series with 9 points and 603 bytes from partition 1
[wal] 2015/09/16 09:36:57 write to index of partition 1 took 1.322408ms
[query] 2015/09/16 09:36:58 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:58 <IP_ADDRESS> - - [16/Sep/2015:09:36:58 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 25f1652c-5c91-11e5-802d-000000000000 578.912µs
[query] 2015/09/16 09:36:58 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:58 <IP_ADDRESS> - - [16/Sep/2015:09:36:58 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2641ed27-5c91-11e5-802e-000000000000 1.484373ms
[query] 2015/09/16 09:36:59 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:59 <IP_ADDRESS> - - [16/Sep/2015:09:36:59 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 268b9ee6-5c91-11e5-802f-000000000000 446.372µs
[query] 2015/09/16 09:36:59 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:36:59 <IP_ADDRESS> - - [16/Sep/2015:09:36:59 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 26cf914d-5c91-11e5-8030-000000000000 1.258828ms
[query] 2015/09/16 09:37:00 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:00 <IP_ADDRESS> - - [16/Sep/2015:09:37:00 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 27202c8c-5c91-11e5-8031-000000000000 644.86µs
[query] 2015/09/16 09:37:00 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:00 <IP_ADDRESS> - - [16/Sep/2015:09:37:00 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 277a8184-5c91-11e5-8032-000000000000 1.59737ms
[query] 2015/09/16 09:37:01 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:01 <IP_ADDRESS> - - [16/Sep/2015:09:37:01 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 27b7e2f7-5c91-11e5-8033-000000000000 437.081µs
[query] 2015/09/16 09:37:01 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:01 <IP_ADDRESS> - - [16/Sep/2015:09:37:01 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 27f4917e-5c91-11e5-8034-000000000000 1.479052ms
[query] 2015/09/16 09:37:01 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:01 <IP_ADDRESS> - - [16/Sep/2015:09:37:01 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 28367f60-5c91-11e5-8035-000000000000 636.492µs
[http] 2015/09/16 09:37:02 <IP_ADDRESS> - - [16/Sep/2015:09:37:02 -0700] POST /write?consistency=&db=telegraf&precision=&rp= HTTP/1.1 204 0 - InfluxDBClient 28715bc4-5c91-11e5-8036-000000000000 1.492536ms
[query] 2015/09/16 09:37:02 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:02 <IP_ADDRESS> - - [16/Sep/2015:09:37:02 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2875fe93-5c91-11e5-8037-000000000000 2.077033ms
[query] 2015/09/16 09:37:02 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:02 <IP_ADDRESS> - - [16/Sep/2015:09:37:02 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 28b3094e-5c91-11e5-8038-000000000000 578.986µs
[query] 2015/09/16 09:37:03 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:03 <IP_ADDRESS> - - [16/Sep/2015:09:37:03 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 28f9dacd-5c91-11e5-8039-000000000000 1.838976ms
[query] 2015/09/16 09:37:03 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:03 <IP_ADDRESS> - - [16/Sep/2015:09:37:03 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 293963a8-5c91-11e5-803a-000000000000 638.167µs
[query] 2015/09/16 09:37:04 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:04 <IP_ADDRESS> - - [16/Sep/2015:09:37:04 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2973ebac-5c91-11e5-803b-000000000000 1.293964ms
[query] 2015/09/16 09:37:04 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:04 <IP_ADDRESS> - - [16/Sep/2015:09:37:04 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 29b36474-5c91-11e5-803c-000000000000 561.434µs
[query] 2015/09/16 09:37:04 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:04 <IP_ADDRESS> - - [16/Sep/2015:09:37:04 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 29f07808-5c91-11e5-803d-000000000000 723.439µs
[query] 2015/09/16 09:37:05 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:05 <IP_ADDRESS> - - [16/Sep/2015:09:37:05 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2a2d854a-5c91-11e5-803e-000000000000 652.398µs
[query] 2015/09/16 09:37:05 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:05 <IP_ADDRESS> - - [16/Sep/2015:09:37:05 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2a6d0607-5c91-11e5-803f-000000000000 1.269706ms
[query] 2015/09/16 09:37:06 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:06 <IP_ADDRESS> - - [16/Sep/2015:09:37:06 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2ab150ec-5c91-11e5-8040-000000000000 570.334µs
[query] 2015/09/16 09:37:06 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:06 <IP_ADDRESS> - - [16/Sep/2015:09:37:06 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 99 - InfluxDBShell/0.9 2af86e7d-5c91-11e5-8041-000000000000 1.137035ms
[query] 2015/09/16 09:37:07 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:07 <IP_ADDRESS> - - [16/Sep/2015:09:37:07 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 99 - InfluxDBShell/0.9 2b79a34d-5c91-11e5-8042-000000000000 479.647µs
[wal] 2015/09/16 09:37:07 Flush due to idle. Flushing 132 series with 132 points and 2244 bytes from partition 1
[wal] 2015/09/16 09:37:07 write to index of partition 1 took 5.80329ms
[wal] 2015/09/16 09:37:07 Flush due to idle. Flushing 9 series with 9 points and 603 bytes from partition 1
[wal] 2015/09/16 09:37:07 write to index of partition 1 took 1.520036ms
[query] 2015/09/16 09:37:07 SHOW MEASUREMENTS WHERE cpu = 'cpu0' AND host = 'Wills-MacBook-Pro'
[http] 2015/09/16 09:37:07 <IP_ADDRESS> - - [16/Sep/2015:09:37:07 -0700] GET /query?db=telegraf&q=SHOW+MEASUREMENTS+WHERE+%22cpu%22+%3D+%27cpu0%27+AND+%22host%22+%3D+%27Wills-MacBook-Pro%27 HTTP/1.1 200 40 - InfluxDBShell/0.9 2bd3c380-5c91-11e5-8043-000000000000 415.549µs
[http] 2015/09/16 09:37:12 <IP_ADDRESS> - - [16/Sep/2015:09:37:12 -0700] POST /write?consistency=&db=telegraf&precision=&rp= HTTP/1.1 204 0 - InfluxDBClient 2e67596c-5c91-11e5-8044-000000000000 1.317701ms

InfluxQL doesn't support <> and should return a parser error for that.  Try != instead.  I'll open a separate issue so that <> will return a descriptive error and suggest !=.
Re the other issue of SHOW MEASUREMENTS sometimes working, once it starts working will it fail again if you keep running it?

This is from commit 6ef51f87839a871558d7c42c5eddfc52939e8fca, starting with an empty ~/.influxdb folder, running a recent build of telegraf to collect data:
Show measurements with two conditions returns inconsistent data:
> SHOW MEASUREMENTS WHERE fstype = 'devfs' AND path != ''
name: measurements
------------------
name
disk_free
disk_inodes_free
disk_inodes_total
disk_inodes_used
disk_total
disk_used

> SHOW MEASUREMENTS WHERE fstype = 'devfs' AND path != ''
name: measurements
------------------
name
disk_free
disk_used

> SHOW MEASUREMENTS WHERE fstype = 'devfs' AND path != ''
name: measurements
------------------
name
disk_free
disk_inodes_free
disk_inodes_total
disk_inodes_used
disk_used

> SHOW MEASUREMENTS WHERE fstype = 'devfs' AND path != ''
name: measurements
------------------
name
disk_free
disk_total
disk_used

> SHOW MEASUREMENTS WHERE fstype = 'devfs' AND path != ''
name: measurements
------------------
name
disk_free
disk_inodes_free
disk_inodes_used
disk_used

Show measurements with one condition seems to consistently and correctly return the full set of matching measurements.


SMP Support

I'm not sure when we should start trying to do this, but I expect the longer we wait the more difficult it will be. That said, it probably makes sense to wait until we at least have something running in the guest address space that can actually use multiple cores.
Essentially, the VirtualMachine abstraction we have right now should probably have VirtualCpus, which would all share locks (to some degree) on the virtual devices (and would contain all of the actual vmcs setup stuff we have now). We will need to at least emulate the local apic as well to get this going. I haven't checked, but I hope that OVMF supports the SMP features of EFI so we can use that in the hypervisor to get the other cores going. That should let us keep a lot of complexity out of the hypervisor itself.

This is essentially done


FilterSelect readonly focus

Hi, please add focus exceptin for filter select readonly
.v-filterselect-focus:not(.borderless):not(.floating):not(.custom):not(.v-readonly) [class*="input"]
file: v-filterselect.scss
line: 9
Thanks in advance

Thank you for the finding 👍


SAMLRaider invalidating seemingly valid SAML responses

Hi
I was really keen to explore SAMLRaider but I got a bit nervy about using it because it appeared to be making changes beyond what I would have expected. I would intercept the HTTP request carrying the SAML response, delete a character, replace it and then send it on its way – thus I've made no overall change - but it would be rejected. When looking at the edited response the plugin had:

stripped all the newlines out completely. As far as I understand it, canonicalization retains CRLFs (but ensures they are always 0x0a) so I assume therefore that any 0a byte is part of the input that’s digested.
taken out the attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" from all elements that contained it (saml:Issuer, saml:Subject, saml:Condition, saml:AuthnStatement and saml:AttributeStatement). This presumably would change the digest of the assertion, assuming canonicalization retains the namespace attribute.

So in both cases the digest was being changed, thus invalidating the signature, hence the response . was rejected. Grateful for any comments.
Jerome

Hi Jerome
Thank you for the bug report.
I tested what you wrote and could reproduce the removing of the namespaces and new lines with self made SAML messages. I will try to fix it in the next days.
My test IdP does not create SAML messages with new lines and also does not attach a namespace to the elements like Issuer or Subject. What product do you use for the IdP and the SP?
Perhaps I can integrate the same product into my test environment.
Cheers
Roland

Hi Roland
Thanks for taking the time to investigate. The IDP was Salesforce but I don't know the details behind the SP because it was part of a blackbox penetration test and I don't know what they were using.
Cheers
Jerome

Hi Jerome
Sorry for the big delay in fixing your issue. The namespaces are now no longer deleted and the line breaks are retained.
Unfortunately I do not have a Salesforce IdP for real life testing :)
I could only test it with an example assertion from the Salesforce website and validate it manually.
I would be glad if you could test the extension the next time you have to deal with such an IdP and send me your feedback.
Thanks again for the bug report.
Cheers
Roland

Hi Roland
No worries. Maintaining an open source project is a thankless task - until now: thanks. When I next come across SAML I'll get the latest version of SAMLRaider and give it another go.
Jerome


JSDOM defaults to ASCII instead of UTF-8

Basic info:

Node.js version: 8.x
jsdom version: 11.3.0

Minimal reproduction case
const { JSDOM } = require("jsdom")

const source = `<!DOCTYPE html>
<html>
<head>
</head>
<body>
카나코
</body>
</html>
`;

new JSDOM(Buffer.from(source, "utf-8")).window.document.documentElement.outerHTML

RunKit: https://runkit.com/embed/kd0d4ic5t13y
How does similar code behave in browsers?
Chrome decodes the example HTML as UTF-8. JSDOM should be able to safely have UTF-8 as the default charset, as it is ASCII-compatible.
Why no <meta charset="utf-8" />?
Some services including YouTube provides UTF-8 HTML without charset declaration to crawlers.

Chrome decodes the example HTML as UTF-8

Interesting. Chrome is not following the spec here, which requires using windows-1252 when the encoding cannot be determined via Content-Type header or meta charset.
I will file a Chrome bug here, but continue having jsdom follow the spec and other browsers.

Actually, Chrome gets this correct for HTTP resources; it only has a bug for file: resources. Example at  https://encoding-test-kludttkpxu.now.sh . So jsdom is behaving per spec and also matches Chrome.

Worth noting that another way you can trigger UTF-8 besides meta charset and the Content-Type header is using a BOM.

Using BOM will force ALL strings to be decoded to UTF-8 even when it has meta charset, so no.

Resolved using html-encoding-sniffer.


⚠ Bofrost.es has degraded performance

In c4d3d62, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1621 ms

Resolved: Bofrost.es performance has improved in bf2cfe7 after 9 minutes.


A few instituitions from Indore, India

I have added few colleges and schools from my city. The only thing is that I was using Windows and the name "nul.txt" is removed automatically. I tried creating it back using the command "touch nul.txt" but even it didn't work.

@74274265j #745 fixed the Travis build. If you close and re-open this thread, it should trigger a new Travis build.

Thanks @pchaigno
All is well -- The Travis CI build passed.

@74274265j Can you revert commit 1275d2a1f057e0b3840915779cfcf117e00a31a1 and push to your branch again? That will update this PR and re-add nul.txt.
Also, are all of these schools post-secondary institutions?


onTouchEnd isn't firing on iOS

Bug report
onTouchEnd isn't firing on iOS
Summary
onTouchStart works on both iOS and Android. However, onTouchEnd only works on Android. This event is crucial for handling interaction with the map.
Is there a fix or a workaround?
Environment info
Expo SDK 40
Same on both React Native Maps v. 0.28.0 and Expo's supported 0.27.1

I have the same problem

Related https://github.com/react-native-maps/react-native-maps/issues/3283 https://github.com/react-native-maps/react-native-maps/issues/3065

@christopherdro forgot to add that. Indeed, it's the same issue.

I just want to mention that I tried to wrap the <MapView> in another <View> and use onResponderRelease, but it didn't help, probably because <MapView> captures the touch event and it bubbles up.

Any news on this?

@christopherdro any news of this issue. Or do you have any temporary fix suggestion until it get fixed? Our App release is stuck because of this issue.

@nkulic I want toggle local-state. if map is touch or scrolling then it will local state will true, if it un-touch or stop-scrolling then local state will false. onPanDrag I can't do this.

We need this feature also

@vitalyiegorov I can get to work on that this weekend.

@jasonmichaels any luck with this?

still issue with  onTouchEnd() on iOS

still looking for solutions

Can anyone experiencing this provide a minimal reproducible example?
Running the following code on iOS, with and without provider="google" and on both simulators and physical devices consistently triggers the event on the latest 1.0.0-beta.5 for me.
import React from 'react';
import {StyleSheet} from 'react-native';
import MapView from 'react-native-maps';

export default function App() {
  return (
    <MapView
      style={styles.mapView}
      onTouchStart={() => console.log('touch started')}
      onTouchEnd={() => console.log('touch ended')}
    />
  );
}

const styles = StyleSheet.create({
  mapView: {
    flex: 1,
  },
});

Interesting. Would you be able to provide a snack reproducing it? :)

OK, I did some more testing. The issue seems to be when placing the map inside a Stack Navigator from React Navigation.
Here it is without it and works: https://snack.expo.dev/@kickbk/react-navigation---map---works
Here it is inside a stack navigator and doesn't fire: https://snack.expo.dev/@kickbk/react-navigation---maps---no-go

Still reproduced on the latest version 1.3.0


Implement StateReader

Codecov Report

Merging #76 (1e2b486) into main (24437f6) will increase coverage by 0.43%.
The diff coverage is 64.34%.

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
+ Coverage   65.27%   65.70%   +0.43%
==========================================
  Files          21       24       +3
  Lines        1028     1076      +48
==========================================
+ Hits          671      707      +36
- Misses        357      369      +12

Impacted Files
Coverage Δ

src/business_logic/execution/gas_usage.rs
97.43% <ø> (ø)

src/business_logic/fact_state/state.rs
21.87% <ø> (ø)

src/business_logic/state/cached_state.rs
0.00% <0.00%> (ø)

src/business_logic/state/update_tracker_state.rs
0.00% <0.00%> (ø)

src/starknet_storage/errors/storage_errors.rs
0.00% <0.00%> (ø)

src/business_logic/fact_state/contract_state.rs
12.50% <12.50%> (ø)

...rc/core/syscalls/business_logic_syscall_handler.rs
52.08% <23.52%> (ø)

src/utils.rs
58.06% <71.42%> (ø)

src/business_logic/state/state_cache.rs
76.74% <75.00%> (ø)

src/business_logic/fact_state/state_reader.rs
83.33% <83.33%> (ø)

... and 12 more

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


Fix Checkpoint struct column terminology

Description
Fix Checkpoint struct column terminology.
The Delta Spec has only 1 version of checkpoint but the delta connector uses the term CheckpointV2 in order to write partition values in struct form (partitionValues_parsed col). This is kind of confusing.
This PR fixes this terminology.
How was this patch tested?
Existing UTs
Does this PR introduce any user-facing changes?
No

I agree.. the naming was bad. and inconsistent with protocol doc. thanks for cleaning up


Processing of secondsSinceEpoch and its reverse processing routine.

Added reverse processing of secondsSinceEpoch

Fixed secondsSinceEpoch so that the result of secondsSinceEpoch is similar to the output of the C mktime function when the timezone　is non-zero.
Added procedures to converd the result of secondsSinceEpoch back to  tm structure and datetime type.

This PR is related to the Issue #79.

It seems failed on windows OS because undefined reference to "gmtime_r" and "localtime_r".
I use gmtime_r and localtime_r routine because of thread safety.
Is anyone know thread safe routine which can be used any OS?
Or should I write some pure fortran code to get same results?
And I will now investigate why Cmake's ctest failed.

I think gmtime_r and localtime_r are POSIX only. We could use them on Linux and macOS and fall back to gmtime and localtime on Windows only.

Thank you, I didn't know it was a POSIX function.
I feel that "datetime-fortran" defines a lot of "pure elemental" functions and it is not good to fall back to thread-unsafe functions here.
I would like the library to be usable for large scale parallel computing, so I have rewritten codes to make it independent of C functions.

Thank you, I like your approach. One quick question for now: where in multiple places you have epoc in variable and procedure names, should that not be epoch?

That is my misspelling. Thank you for pointing that out.
And of the parts I added as C-dependent parts, c_mktime was left unremoved, so I'll comment it out.
I will revise and push it later.


Create leaflet demo

We want to try to see if Leaflet is a good candidate for our mapping purposes. The objective is to create a dummy Leaflet map with a couple of pins on the main page.

@kaashmonee Any progress here?


Make AuthenticateInStandaloneApplication available as a Nuget Tool

Right now, one as to download and compile the AuthenticateInStandaloneApplication example locally to generate the OAuth token. This is not a good experience. It would be better if this were available as a tool to run locally.

Notes so I don't forget this later.

Visual Studio 2019 and netcoreapp3.0 are needed.
Look at the contents of https://www.nuget.org/packages/Grpc.Tools/ package.
dotnet publish -r win10-x64 -p:PublishSingleFile=true and so on for other platforms.


Jenkins: Parallel option should be ignored when num machines is 1

Describe the bug
If the number of machines, and therefore the number of child jobs, equals 1, I don't think we need to bother launching a child job.
To Reproduce
Launch a test with a parallel option and a build node label that only matches 1 machine
Expected behavior
Don't do parallel as it will create unnecessary overhead
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

If we make this change, we could also change the parallel default in a grinder from "None" to (my preferred) "NodesByIterations".


Please add zemismart TB26-3 light switch driver

Hi dear,
How are you?
This is Sky from zemismart.com
Would u like to help us to write edge driver?
We will provide free samples.
Best regards,
Sky

Hi Sky
Hello,
In order to add a device to a edge driver, it is necessary to know the fingerprints, that is, the manufacturer, model and the clusters (capabilities) that it supports.
The brand model does not work.
I don't know exactly what you need, create a driver or add to an existing driver?
currently the number of drives that can be installed in a hub is limited to 50 and therefore it is best to group several devices in each driver.
Regards

Hi Mariano,
Thanks for your reply~
I want to create driver to our devices.
I will provide you the fingerprints information.
Do u need items in your hand too?
Best regards,
Sky

My email is<EMAIL_ADDRESS>

Hi Alberto,
Added to this driver version
`───────────────────────────────────────────────────
Driver Id    bb1b3fd4-dcba-4d55-8d85-58ed7f1979fb
Name         Zigbee Light Multifunction Mc
Version      2023-01-06T15:55:17.423771514
───────────────────────────────────────────────────

id: "_TZ3210_e020aaa/TS0505B"
deviceLabel: RGBW TS0505B
manufacturer: _TZ3210_e020aaa
model: TS0505B
deviceProfileName: rgbw-level-colortemp-2700-6500
`

Thanks... let me try it.

Thanks... let me try it.

Working fine.

Mariano... the device is not yet recognized. I have no idea what could be happening.


merge from template-arlac77-github

package.json

chore(deps): add ^8.0.1 remove ^8.0.0 (devDependencies.c8)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
131

Relevant Lines:
134

💛  - Coveralls


Suggestion: Change Icons for 'mined' factory buildings.

Change the colors of the Icons used for factory buildings that were mined to differentiate between unused factory buildings that have never been placed.
Attached is a sample Icon picture.
factory.lua is changed as shown below at line 61.
icon = F .. "/graphics/icon/factory-1b.png",
The new Icon.
factorissimo_factory.lua_change.zip

The factorio mod discussions have no potential to be automated with CICD bug tracking. Thus they will remain closed.

I have implemented your suggestion. Thank you.


photosphere changes the background even when the cursor is invisible

Although the cursor is invisible and when pointed it to the one of the pictures in the menu, the photosphere background is changed. A very minor bug, thought of letting you know.

Thanks! I look into that.

One possible solution is, inside onclick bound function
if(this.el.parentEl.getAttribute('visible')){
   //change the photosphere material
}

Let me give a PR to this.

Thanks!


TST: Cover resample bar first_trading_day method.

Add a test to directly cover the first_trading_day method via the
test_resample suite. (The lack of coverage was exposed when testing
against real data.)
Also, refactor resample bar tests so that session bar reader is set up
in instance fixture.

Coverage increased (+0.007%) to 86.133% when pulling 3c7dae8c4106bf37b4e3bc85abbd70ba296b4742 on cover-resample-first-trading-day into 22ad891d5191dace3851e2f8815304aba8a37e14 on master.

Coverage increased (+0.007%) to 86.133% when pulling 3c7dae8c4106bf37b4e3bc85abbd70ba296b4742 on cover-resample-first-trading-day into 22ad891d5191dace3851e2f8815304aba8a37e14 on master.

Coverage increased (+0.007%) to 86.133% when pulling 3c7dae8c4106bf37b4e3bc85abbd70ba296b4742 on cover-resample-first-trading-day into 22ad891d5191dace3851e2f8815304aba8a37e14 on master.


add parse function

Codecov Report

Merging #2 into development will increase coverage by 9.25%.
The diff coverage is 100.00%.

@@               Coverage Diff                @@
##           development        #2      +/-   ##
================================================
+ Coverage        90.74%   100.00%   +9.25%
================================================
  Files                6        12       +6
  Lines               54       249     +195
  Branches             2        23      +21
================================================
+ Hits                49       249     +200
+ Misses               4         0       -4
+ Partials             1         0       -1

Impacted Files
Coverage Δ

src/bigquery_sql_parser/column.py
100.00% <100.00%> (ø)

src/bigquery_sql_parser/line.py
100.00% <100.00%> (+9.09%)
:arrow_up:

src/bigquery_sql_parser/multiline.py
100.00% <100.00%> (ø)

src/bigquery_sql_parser/query.py
100.00% <100.00%> (ø)

src/bigquery_sql_parser/tokenizer.py
100.00% <100.00%> (ø)

src/bigquery_sql_parser/utils.py
100.00% <100.00%> (ø)

tests/test_column.py
100.00% <100.00%> (ø)

tests/test_line.py
100.00% <100.00%> (ø)

tests/test_multiline.py
100.00% <100.00%> (ø)

tests/test_query.py
100.00% <100.00%> (ø)

... and 10 more

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 ebcc925...fcb616a. Read the comment docs.


gear_menu: Link to /devlogin/ in development environment

It’d be nicer to use hash_util.build_login_link which also remembers the current hash, but that doesn’t help when the gear menu is only rendered once at page load time.

Merged, thanks @andersk! I've been meaning to fix this but kept forgetting.


Update to RxSwift 3.2 and some cleanup

Updated RxSwift to 3.2
Fixed the swiftlint "vertical alignment" warnings (not sure if this is the preferred formatting?)
Replaced some flatMap's with map where it made sense (mostly thrown errors)

I also looked through the code and changed some formatting like:

spacing before/after : (e.g [SomeClass: SomeOtherClass])
remove else where it is not needed (because the if-part returns)
replace if let with guard where it made sense
replace map{ SomeClass(something: $0) } with map(SomeClass.init)

Great work, as always :)
Looks good to me, @Cierpliwy could you also check this?

Looks great to me as well. I think, we can merge it.


Missing features in sftp support of maven-publish

We use sftp to upload artifacts into an internal Maven repository. Gradle's JSch-based sftp provider has many deficiencies, especially regarding public/private keys. In Gradle 6.x, when the old uploadArchives task was available, this wasn't a big problem, because I created a Wagon implementation which handled the file transfer correctly, based on the Apache MINA SSHD library. The uploadArtifacts task handled this correctly, we set uploadArtifacts.repositories.mavenDeployer.configuration to a configuration which contains that Wagon, and the files was uploaded correctly.
Now, that uploadArchives has been removed, there is no way to use that Wagon. I tried implementing ResourceConnectorFactory, but it's an internal API and I couldn't find any sane way to tell Gradle to use the subclass.
The fix would be either to make a public API for Gradle plugins to implement uploading files to a remote repository, or add Wagon support to maven-publish plugin.
Issue #14750 is related, it wants WebDAV support. If Gradle had a public API for custom repository transports, that issue could be easily solved by using custom webdav provider plugin.

Thanks for the report. This customization of the transport is something that needs to be looked at.
Note that while all the default uploadTask wiring is removed in Gradle 7.0, the task type is still available, although it will disappear in 8.0.

@hoat4 it is not yet clear if there will be a way to add "custom transports" to maven-publish in the foreseeable future.
It looks like your use case is really using sftp as transport. Which Gradle already supports out-of-the-box (as you stated). Could you describe what exactly is not working for you? Can you provide a reproducer for the issue you are facing?

Here is an example for using a custom upload mechanism in combination with maven-publish: https://github.com/gradle/gradle/issues/14750#issuecomment-784358228.

Waking this up because the original problem as described seems to have gotten a bit lost, and it's exactly my problem:
I want to maven-publish to sftp but I'd rather not a: enable password logins and b: put my password in plaintext on the system anywhere. I want it to use private keys, through ssh-agent.
It seems like this, specifically, sftp transport to use ssh pubkey auth through ssh-agent, is the main ask here.
I note that the gradle ssh plugin can actually do this, and it too depends on jsch. I'm not sure if the ssh-agent specific stuff is in jsch, but I think so. If so, it might just (just!) be sufficient to depend on the newer version and expose the parameters to an Authentication section somehow?
In my experience using that plugin for other purposes, it works great in unixy environments such as Linux and Mac OS, but has more of a problem in Windows, because it seems jsch doesn't know about Windows now including OpenSSH, including the agent, and doesn't know how to talk to the named pipe that it uses in lieu of the ssh-agent unix socket. So on Windows you have to use Pageant to handle the agent instead, which is a bit of a pain but at least there is a solution.
It looks like it may be possible to use that to implement a custom upload mech as per the comment above, but it's less than ideal when obviously preferably the sftp transport should just be able to use it directly. In modern security-aware development environments I'd actually say that some kind of pubkey/agent support should be a higher priority to implement than password access.

Relates to

#19028

Hey @hoat4 ,
The PR updating SSHD and jsch is merged.
Would you be able to test with a Gradle nightly to see if it improves the situation for your use case?


Remote ref does not update with push

The following screenshot illustrates the bug:

The gray box representing the origin/dev ref should be updated after pushing, but instead it requires typing git fetch again.

I'll second that.


gan_potential folder missing

Tiny typo in the tutorial
cd .../tdep-tutorials/00_preparation/gan_potential/test
The gan_potential folder does not exist.
In https://tdep-developers.github.io/tdep/program/extract_forceconstants/
there is a typo systemfrom
also  This leads is to one
 forceconstants
~\cite{Leibfried1961,Maradudin1968,Born1998}
method.[CITE]
The format for this file is similar to the second order:
But then the format is missing.

Hello,
In this tutorial, for step 6, you way want to add "--polar":
extract_forceconstants -rc2 10 --polar | tee extract_forceconstants.log


L515 Depth intrinsic model

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
l515

Firmware Version
01.04

Operating System & Version
Win (8.1/10)

Kernel Version (Linux Only)

Platform
PC

SDK Version
{ legacy / 2.36 }

Language
C#

Segment

Issue Description
I currently have 2 L515 cameras, 1 of which has problem with intrinsic params, parameters in intrinsic ( These are exactly these parameters: Principal Point, Focal Length) have changed, it's different from when I saw last week.
I'm sure it has been changed, but I can't prove it right now and I don't know how to reproduce the problem.
This camera is used by me and my colleagues, so I'm not sure anyone makes intrinsic changes somehow.

I used this tool "rs-sensor-control.exe" to see intrinsic parameter.

Question
Hi @RealSenseSupport, @dorodnic , @MartyG-RealSense.

Is there any way to change intrinsic on L515?
Can intrinsic be altered by any of the following:
2.1. Due to version Firmware problem?
2.2. Due to Version SDK problem?
2.3. Other
Note: It only happened on one of my cameras, the other was fine.
Please help me to solve this problem.

Hi @anhTuan0712
Unfortunately without seeing the exact information of the camera in the previous setup and after the new changes, we cannot fully outline what changed the values.  Yes our FW has the ability to make changes to the camera specifics like this.
What FW do you have on the cameras previously and what FW do you have on the camera now?

Hi @RealSenseCustomerSupport .
Thank you for the feedback.
step 1: When I buy the camera on FW is: <IP_ADDRESS>, the intrinsic parameter is INTRINSIC1
step 2: My colleagues used the camera (L515)
step 3:  + when I get the camera again, FW: 01.05.00, intrinsic parameter is INTRINSIC2 (INTRINSIC1 #! INTRINSIC2)
+ I tried to re-install FW which is <IP_ADDRESS>, <IP_ADDRESS> but the intrinsic is still INTRINSIC2  (INTRINSIC1 #! INTRINSIC2)
I'm not sure someone did something in step2

Hi @RealSenseSupport, @dorodnic , @MartyG-RealSense.
Please reply to me with this information, I really need it now!

I also have the same problem,
@RealSenseSupport , @dorodnic , @MartyG-RealSense ,
Please answer the above problem, Thank!

Hi @anhTuan0712 and @nh-97
Do you have a log of the old intrinsic and the new intrinsic information?  I'm hoping I can get the differences to allow for us to do further investigation.  Can you outline if your colleagues did anything specific to the camera?  Just used the camera normally with the SDK?  They must have updated the FW to <IP_ADDRESS>.  There is no command you can do to force changes at the FW level, so unfortunately I cannot provide anything on that front.  But I do want to investigate further.  Can you also provide the serial number of your cameras that show this behavior?

Hi @RealSenseSupport.
1.1) Current intrinsic parameters on my camera:
Resolution 640x480

Resolution 1024x768

1.2) Sorry, I don't have info about the old intrinsic.
2) Yes, Just used the camera normally with the SDK.
3) My colleague used "Intel RealSense Viewer" to update the FW.
4) serial number of cameras

@anhTuan0712
Thanks for the information.  We will start investigating.

Hi @RealSenseSupport.
Please provide me with information as the results of the investigation become available.

Hi @anhTuan0712
We took a look at the serial number you provided F0264364 along with the intrinsic parameter information you were able to provide and found that the values are the same as what was shipped with this unit.  We do not see a change in the values.

Hi @RealSenseSupport.
Sorry for asking for a bit old information, but I want you to confirm this. Which of the following confirmations of yours are correct:

Yes our FW has the ability to make changes to the camera specifics like this.
There is no command you can do to force changes at the FW level, so unfortunately I cannot provide anything on that front.

Hi @anhTuan0712
We took a look at the serial number you provided F0264364 along with the intrinsic parameter information you were able to provide and found that the values are the same as what was shipped with this unit. We do not see a change in the values.

Thanks for your help, but like I said the "intrinsics" have changed since I first got the Camera. I hope you will continue to investigate this matter.

Hi @anhTuan0712
If we run across the problem again then we will be able to investigate further.
Is there anything else on this matter?

Hi @RealSenseSupport.
Sorry for asking for a bit old information, but I want you to confirm this. Which of the following confirmations of yours are correct:

Yes our FW has the ability to make changes to the camera specifics like this.
There is no command you can do to force changes at the FW level, so unfortunately I cannot provide anything on that front.

Hi @RealSenseSupport.
Please confirm this question.

Hi @anhTuan0712
To confirm, internally we have the ability to modify camera specifications as we are able to build FWs to do this.  We also have internal engineering tools that have register level capabilities so commands with our public level tools are not available.
I hope this answers your final questions.
I want to let you know that we have not made such modifications to intrinsic information.


Add Babylon Health to the Adopters list

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1288   +/-   ##
=======================================
  Coverage   85.95%   85.95%
=======================================
  Files          74       74
  Lines        2535     2535
  Branches      108      108
=======================================
  Hits         2179     2179
  Misses        356      356

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
85.38% <0%> (-1.17%)
:arrow_down:

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

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

...re/shared/src/main/scala/io/circe/JsonNumber.scala
96.38% <0%> (+1.2%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
100% <0%> (+2.7%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @ryanb93!


hello, I want to use this for researching XACML. Can you help me to do?

There is some description how to start this engine but it's too simple to me.
Can you provide more more detailed description to start?
I'm a novice but I will try to do my best.
Thanks.

i.e.) how to write the configuration file.

i.e.) how to write that

Hello,
I updated the README to give a basic example of working PDP configuration. If you need extra PDP features, you can look at the XML schema to understand how to enable/use them, as explained in the README.
However, if you have further questions, please send an email to Authzforce contact mailing list for this purpose, as mentioned in the Support section of the README. This page is only for reporting issues or requesting missing features. Thanks :)


print issue

I'm trying to print a long div inside a modal but for some reason I don't have a second page in IE11.
I created a question in Stackoverflow.
https://stackoverflow.com/questions/54825421/css-print-long-div-inside-modal-no-second-page-in-ie
I think is Bootstrap related as I created a minimum project where I can have the second page in all browsers but when I attach bootstrap css to the html it stop to work
I can create a repo in github and share it so you can see that it happens just when I have bootstrap

little update, I've applied display table to the main div that contain the 2 page and now I can print in IE now but not in FF.

There are a lot of print issues, but sadly enough browsers just behave too inconsistent to provide a solution for all scenarios with. We're probably going to remove a lot of the default print styles (if not all) we now provide in Bootstrap for the next major version.


Separate delay for inactivity timeout

In my case, the responsiveness of the final call in a throttle is very important.
So I think I need a separate inactivity timeout.
For example, if some event happens during scrolls (say maybe every 5ms), it's nice to space out the actual callback calls to maybe 250ms, but once the scrolling is done, I would like the final callback call to come very quickly, maybe after 50ms of no calls to the throttled function.  This is important to make things look right for the user.
I don't want to lower the current delay to 50ms because it slows down my page a lot.
Notice in my example that: 5 ms average interval < 50 ms < 250 ms
If you have no time for this, I could code it with a few tips from you to speed things up.

Is this already implemented?
Here or in Lodash at least?
4 years passed :+1:


Aaa

IMPORTANT: If you have a question or an idea for a new feature use Github Discussions instead
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Provide a code snippet and 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.
Reproduction
If applicable, add a link to a simple reproduction on a site like https://codesandbox.io or https://playground.solidjs.com.
Additional context
Add any other context about the problem here.

Hi there just wondering how are doing tomorrow morning @Salemsa89


Issue #1480: Prevent c8y-config-plugin crashing on bad input

Proposed changes

[x] Log failures while processing messges and file watcher events instead of propagating the error eventually crashing the plugin
[ ] Convert errors into SmartREST 502 failure messages

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

This error handling prevents the plugin from crashing but does not stop dangling operations (always executing operations), right?

Yup. That's the sophisticated error handling that I was talking about (the unchecked tick-box in the PR description), which will be handled in a follow-up PR. This PR is just for damage limitation avoiding crashes on every bad input.

I am not able to reproduce the crashing


GPU Support

Hi - Really great implementation, works a treat and stable. I was wondering if you had looked at using the encoder h/w on the pi ? Taking a look at the stats it appears is all CPU and so not really possible to get a smooth stream  on a Model 3 above CIF (352 × 288) ?? The thought would be to use the mmal library and offload to the GPU/VPU?

I haven't looked at this, although it looks interesting. I might have a look at the MMAL library and see if it can do any of the processing (which is pretty much just adding an alpha channel).
If you want to look yourself by all means fork and create a pull request, I'd be interested in seeing how well it performs if we can offload some of that processing.

Having looked further into this, there is a newer version of the NDI library that appears to support Raspberry Pi specifically.
I will have a look at this this week, and see if it works better.

Ok, I've been looking at this, and got a little bit stuck down a rabbit hole. Keep your eyes open for v2.0.0, which completely rewrites how it retrieves the images from the camera, and from my limited testing so far works much, much better (smooth video even at 1920x1080).

Let me know how you get on with version 2.0.0; You should see an improvement on the framerate thing.

Great news thanks - I’ll test it out and report back.

@rf152 - works a treat at 1280x720 @ 30fps in a Model 3B+ - I have monitored the output at it holds up at 30fps, video is smooth. Searching around on monitoring GPU, seems impossible on the rPi. But a `pi@raspberrypi:~ $ sudo vcdbg reloc stats
'Relocatable heap version 4 found at 0x3c000000
total space allocated is 44M, with 44M relocatable, 0 legacy and 0 offline
0 legacy blocks of size 2359296
small_allocs                  : 33
allocs                        : 173
alloc_fails                   : 0
legacy_block_fails            : 0
compactions                   : 0
discard_compactions           : 0
aggressive_compactions        : 0
aggressive_compaction_waits   : 0
aggressive_compaction_timeouts: 0
locks                         : 0
small_locks                   : 0'
Shows it's in use (before largest block is 235M bytes) which matched the rPi mem split
Slightly jerky at 1080p also noticed a warning Aspect ratio forced to: 1920 x 1088 when the Conference file is set
neopixel_path = "/tmp/neopixel.state"; camera_number = "-1"; height="1080"; width="1920"; fps="30";
free list at 0x3cfc1f00
15M free memory in 2 free block(s)
largest free block is 15M bytes`
I'll say again - awesome simple implementation of a raspberryPi studio camera. Thanks

Yeah, the locked ratio is to do with the way that the camera captures; it has all sort of weird artifacts when you force it to 1920x1080. It's supposed to crop, but I couldn't get it to work properly. I might revisit it further down the line.