Fix e2e tests related to nginx image

Failure:
=== RUN   TestImageSanity/nginx:1.25.0-alpine/libx11/1.8.4-r0
    sanity_test.go:126:
        	Error Trace:	/Users/dcaravel/dev/stackrox/scanner/e2etests/sanity_test.go:126
        	Error:      	Not equal:
        	            	expected: v1.Feature{Name:"libx11", NamespaceName:"alpine:v3.17", VersionFormat:"apk", Version:"1.8.4-r0", Vulnerabilities:[]v1.Vulnerability(nil), AddedBy:"sha256:4aacde79cec42c8d0c5886185e70a16b107ae8c6b1a67d63d6efdb6d6978ed97", Location:"", FixedBy:"1.8.4-r1", Executables:[]*scannerV1.Executable(nil)}
        	            	actual  : v1.Feature{Name:"libx11", NamespaceName:"alpine:v3.17", VersionFormat:"apk", Version:"1.8.4-r0", Vulnerabilities:[]v1.Vulnerability(nil), AddedBy:"sha256:df332c62b62203bc571db5a701bfb416982e1c998a2c6893c488d55c29f27fb0", Location:"", FixedBy:"1.8.4-r1", Executables:[]*scannerV1.Executable(nil)}

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -6,3 +6,3 @@
        	            	  Vulnerabilities: ([]v1.Vulnerability) <nil>,
        	            	- AddedBy: (string) (len=71) "sha256:4aacde79cec42c8d0c5886185e70a16b107ae8c6b1a67d63d6efdb6d6978ed97",
        	            	+ AddedBy: (string) (len=71) "sha256:df332c62b62203bc571db5a701bfb416982e1c998a2c6893c488d55c29f27fb0",
        	            	  Location: (string) "",
        	Test:       	TestImageSanity/nginx:1.25.0-alpine/libx11/1.8.4-r0
=== RUN   TestImageSanity/nginx:1.25.0-alpine/nghttp2/1.51.0-r0
    sanity_test.go:126:
        	Error Trace:	/Users/dcaravel/dev/stackrox/scanner/e2etests/sanity_test.go:126
        	Error:      	Not equal:
        	            	expected: v1.Feature{Name:"nghttp2", NamespaceName:"alpine:v3.17", VersionFormat:"apk", Version:"1.51.0-r0", Vulnerabilities:[]v1.Vulnerability(nil), AddedBy:"sha256:4aacde79cec42c8d0c5886185e70a16b107ae8c6b1a67d63d6efdb6d6978ed97", Location:"", FixedBy:"1.51.0-r1", Executables:[]*scannerV1.Executable(nil)}
        	            	actual  : v1.Feature{Name:"nghttp2", NamespaceName:"alpine:v3.17", VersionFormat:"apk", Version:"1.51.0-r0", Vulnerabilities:[]v1.Vulnerability(nil), AddedBy:"sha256:df332c62b62203bc571db5a701bfb416982e1c998a2c6893c488d55c29f27fb0", Location:"", FixedBy:"1.51.0-r2", Executables:[]*scannerV1.Executable(nil)}

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -6,5 +6,5 @@
        	            	  Vulnerabilities: ([]v1.Vulnerability) <nil>,
        	            	- AddedBy: (string) (len=71) "sha256:4aacde79cec42c8d0c5886185e70a16b107ae8c6b1a67d63d6efdb6d6978ed97",
        	            	+ AddedBy: (string) (len=71) "sha256:df332c62b62203bc571db5a701bfb416982e1c998a2c6893c488d55c29f27fb0",
        	            	  Location: (string) "",
        	            	- FixedBy: (string) (len=9) "1.51.0-r1",
        	            	+ FixedBy: (string) (len=9) "1.51.0-r2",
        	            	  Executables: ([]*scannerV1.Executable) <nil>

Ugh, reverting layer change, with scanner update to read host architecture - my local testing was showing the arm64 layers.

/test db-integration-tests


"export 'Url' was not found in './Url.vue' || Uncaught TypeError: route is undefined

This is  a bug.

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/laravel-enso)
[x] Did you check the documentation?
[x] Did you perform a cursory search?

Description
Hi,
Just update today 2022.03.03 - 19:16.
Yarn serve has this warning
"export 'Url' was not found in './Url.vue'

and
Application is not working anymore (build or serve):

Uncaught TypeError: route is undefined
    match routeBuilder.js:23
    process routeBuilder.js:23
    add routeBuilder.js:10
    add routeBuilder.js:10
    handle routeBuilder.js:16
    node_modules chunk-vendors.js:5612

Any hints for us?
Thanks!

Investigation:
https://github.com/laravel-enso/enso/blob/master/client/package.json
is using
"@enso-ui/ui": "^5.0",

And
"@enso-ui/ui": "^5.0",
is using
"<EMAIL_ADDRESS>
But it seems that there are references in yarn.lock to multiple versions after this update :
@enso-ui/ui": "^5.0 and @enso-ui/ui": "^6.0
<EMAIL_ADDRESS>and<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>I managed to fix the error by setting my package.json to
"@enso-ui/ui": "^6.0",

& yarn install && yarn build.
Can you confirm this is the fix?

hi @robbykrlos
We will release this week v5.0 that has breaking changes on both BE & FE.
You should not use UI 6.0 until the release and upgrade steps are public.
Meanwhile, use yarn why and determine what is requiring<EMAIL_ADDRESS>/<EMAIL_ADDRESS>

hi @robbykrlos
We will release this week v5.0 that has breaking changes on both BE & FE.
You should not use UI 6.0 until the release and upgrade steps are public.
Meanwhile, use yarn why and determine what is requiring<EMAIL_ADDRESS>/<EMAIL_ADDRESS>
Hi, thanks for the reply, meanwhile we reverted yarn.lock to previous version.
Thanks for the explanation.


perf: reduce allocation for JavascriptParser::new

Summary

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

!bench

!bench


Modify add command

Modify add command so that we can add person without having complete data

PR #25.


Add Seasonally Adjusted to Geography App

Ensure that the CSV can be downloaded as seasonally adjusted or not, and that this also makes its way to the choropleths.

Also make sure that the CSV is downloadable as seasonally adjusted or not.


fs delays don't seem to have homing capabilities

self.driver.address.hardware.q.push('home')
AttributeError: 'Driver' object has no attribute 'address'

fixed as of commit ccd186784dd7f3bd3fbbf8ce0b565e5fb3edf6ab


XP Progress Bar ignores Configure XP Drops settings

An issue that somehow every single 3rd party client has managed to copy over.

The progress bar is one of the moveable widgets. Press Alt and click-and-drag it to whatever location you'd like, including the top-middle anchor point.


Problem with updating cards?

First of all, thanks for building this. Having a two-way interface between my roam database and anki makes both MUCH more useful. This has become one of the few systems that I use on a literally daily basis.
I'm currently running into a bug: for at least some cards, when I make changes to corresponding block in roam, that card is not updated when I run the script.
I double checked, and the uid field on the anki card matches the id of the roam block (and when I click on the asterisk, it does link me back to the block in my browser).
I'm still getting all the terminal messages that indicate success...
2021-03-19 19:46:10,070 - INFO - Setting up Ankifier 2021-03-19 19:46:10,241 - INFO - Loading Roam Graph 2021-03-19 19:47:02,041 - INFO - Fetching blocks to ankify 2021-03-19 19:47:02,188 - INFO - Ankifying 157 blocks 2021-03-19 19:47:10,116 - INFO - Added 0 new notes and updated 157 existing notes
...so I'm pretty confident that the script is working.
Is this a known bug?

I'm glad you're finding the tool so useful! I get a ton of value out of it and/but it's great to hear that other's are as well.
This sounds like a bug I'd run into previously but it sounds like it's not fully fixed. If I remember correctly, there was a character encoding issue which was causing ankify_roam to fail to match up some blocks with the corresponding anki cards. I'm sure this is something we can get fixed, but I'm going to need some help from you to replicate the issue on my end.
I'll need the raw json of the blocks which are having the problem. Here's what I'll need you to do to create a json with the problematic blocks:

Get the uids for a few of the blocks which aren't updating
Follow the steps below to create a json of those blocks (I don't need or want your whole roam graph)
Paste the contents of the json here, or send the json to<EMAIL_ADDRESS>
Once I have the json and can replicate the issue, I should be able to turn around a fix pretty quickly.

Steps to create a json of select blocks

Get the uids for a few of the blocks which aren't updating
Export your roam graph as a json and unzip it
Copy the python script below and paste it into a file called extract_buggy_blocks.py
Place extract_buggy_blocks.py in the same folder as your roam graph (e.g. your Downloads folder)
Run the extract_buggy_blocks.py script. The first parameter is the path to your roam graph export and the remaining parameters are the block uids. The script will load your roam graph, select the blocks with the uids you gave, and save those blocks as a separate json called buggy_blocks.json. Running it will look something like:

cd ~/Downloads
python extract_buggy_blocks.py my_roam_graph.json WAjKH-S05 4z-Ud6kRx

You should now have a buggy_blocks.json file in the same folder where you ran the script from.

extract_buggy_blocks.py
import os
import json
import sys

def get_block(uid, blocks):
    for block in blocks:
        if block.get("uid") == uid:
            return block
        block = get_block(uid, block.get('children',[]))
        if block:
            return block
    return None

def main():
    # User inputs
    path = sys.argv[1]
    uids = sys.argv[2:]
    # Load roam graph
    with open(os.path.expanduser(path)) as f:
        rm = json.load(f)
    # Get blocks with given uids
    select_blocks = []
    for uid in uids:
        for page in rm:
            block = get_block(uid, page.get('children',[]))
            if block:
                select_blocks.append(block)
    # Save blocks as json
    dir, _ = os.path.split(os.path.expanduser(path))
    with open(os.path.join(dir, "buggy_blocks.json"), "w") as f:
        json.dump(select_blocks, f)

if __name__=="__main__":
    main()

Ok. I'll get to this sometime this weekend, and then let you know.

Sent.

UTF 8 Same error.


Year period page, require all month list by default

Need this list by default
Jan to Dec
Q1 to Q4
H1, H2

It depends on last year added

It depends on last year added

an to Dec
Q1 to Q4
H1, H2
its same for all CA firms, to please add it by default with current year, sothat when we setup its appeared automatic in year period section.

it comes by default, if user change year / Period than that continues


[c++/ci] Update make format and CI format-checker to find more C++ files

The make format and the CI checker were coded back when all the C++ source was located in libtiledbsoma. Since then, there are C++ source files located elsewhere, but make format and the CI checker were never updated to find them. So we've been running clang-format on some files and not others.

So we've been running clang-format on some files and not others.

Intentional for the R package embedded here (just like the external R package). clang-format was never used.


Fix bug where the database name wasn't being emitted in some circumstances

Ah, fun. I was bit by a similar thing in another case -- checking to see if  something's been specified vs is at the default value is so annoying.


Execute defaults

This brings the execute command defaults into alignment with the message spec documentation at http://jupyter-client.readthedocs.org/en/latest/messaging.html#execute.
@ellisonbg - you changed the defaults in the kernel.js code away from these in https://github.com/jupyter/notebook/commit/f306423c7ea3bc60735a8bfb4f5f2cc60dc36b97.  Do you recall why you did this, and do you have comments about changing it back in jupyter-js-services?

I'll just add that the current kernel.js execute function has contradicting documentation about the default of silent (it says it is false in one place and true in another): https://github.com/jupyter/notebook/blob/7e4f72ed6c4a8c0857d16cee648f9e692debf33c/notebook/static/services/kernels/kernel.js#L700

I'm in favor of merging this, and reverting if Brian has evidence why we should.


Test code for multiget; date_search to optionally do a multiget

Pull request #111 needs some more test code and the date_search should have an optional parameter causing it to fetch the object data if needed, and by multiget if supported.

https://tools.ietf.org/html/rfc4791#section-7.9

https://tools.ietf.org/html/rfc4791#section-7.9

Oups.  This functionality seems broken in master now.  It is important with test code!

This also needs to be integrated with the sync work.  By now we have the following code there:
        if load_objects:
            for obj in objects:
                try:
                    obj.load()
                except error.NotFoundError:
                    ## The object was deleted
                    pass

This won't go into v0.10 either, I'm afraid.


How to import css from other lib or node_modules

I try to make, with post css
@import 'slick-carousel/slick/slick';

There are other ways to do the import css directly in the component or post-css, other loaders
Like this
import 'slick-carousel/slick/slick-theme.css';

I dont understand what you're trying to ask here.
You can import css in components, just the way you wrote.


Regression: All stores selection UX

was fixed with #92
Tested on latest Chrome on W10

I think I will write unit tests with all those regressions happening.


chore: update react and happo packages

FX-2778
Description
As per Dependabot's open PRs, I've updated all selected packages for this week.
How to test

all tests pass
Click around Storybook

Screenshots

Before.
After.

Insert screenshots or screen recordings
Insert screenshots or screen recordings

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure that tests pass by running yarn test
[x] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

Good point. Didn't think about devDependencies. I'll remove the changeset.


cannot resolve reference #/components/schemas/SchemaName, it's missing: $.components.schemas['SchemaName']

When using the language server in neovim, I am getting an error being reported that is not reported when running the lint command using vacuum in the terminal.
I am using neovim v0.10.1, and vacuum v0.12.1 installed using Mason. I also have vacuum v0.12.1 installed using brew in my environment.
It occurs when a component schema references another component schema. As far as I can tell this is fine if the reference is in the paths section and only happens when you try to references schemas from schemas.
You can use the below spec to reproduce the issue.
openapi: 3.0.0
info:
  title: Example
  version: 1.0.0
  description: Bug example
  contact:
    name: Bug name
    url: bug.example.com
    email<EMAIL_ADDRESS>servers:
  - url: http://localhost
    description: Local development environment
components:
  schemas:
    ID:
      description: A unique ID
      type: string
      pattern: ^[0-9a-f]{32}$
      example: d0bf5a6a909111f0aabf02d14af18cff
    ReferenceToID:
      description: An object that references the ID
      type: object
      properties:
        id:
          $ref: '#/components/schemas/ID'
        otherProp:
          type: string
          example: Some string
      example:
        id:<PHONE_NUMBER>abcdef0123456789abcdef
        otherProp: Some string

In neovim, for the spec, it reports the following errors and warnings:

openapi-example.yml|2 col 2 error| schema invalid: missing properties: 'paths'
openapi-example.yml|21 col 7 warning| #/components/schemas/ReferenceToID is potentially unused or has been orphaned
openapi-example.yml|25 col 11-15 error| cannot resolve reference #/components/schemas/ID, it's missing: $.components.schemas['ID'] [25:11]

While using vaccum in the command line using the command:

vacuum lint -dq openapi-example.yml

It produces the following list of errors:

██╗   ██╗ █████╗  ██████╗██╗   ██╗██╗   ██╗███╗   ███╗
██║   ██║██╔══██╗██╔════╝██║   ██║██║   ██║████╗ ████║
██║   ██║███████║██║     ██║   ██║██║   ██║██╔████╔██║
╚██╗ ██╔╝██╔══██║██║     ██║   ██║██║   ██║██║╚██╔╝██║
 ╚████╔╝ ██║  ██║╚██████╗╚██████╔╝╚██████╔╝██║ ╚═╝ ██║
  ╚═══╝  ╚═╝  ╚═╝ ╚═════╝ ╚═════╝  ╚═════╝ ╚═╝     ╚═╝

version: 0.12.1 | compiled: Fri, 16 Aug 2024 14:08:38 UTC
🔗 https://quobix.com/vacuum | https://github.com/daveshanley/vacuum

INFO: Linting file 'openapi-example.yml' against 44 rules: https://quobix.com/vacuum/rulesets/recommended

/Users/kuba/Google Drive/My Drive/src/payouts/openapi-example.yml
-----------------------------------------------------------------
Location                 | Severity | Message                                                                         | Rule                  | Category | Path
openapi-example.yml:0:0  | error    | schema invalid: missing properties: 'paths'                                     | oas3-schema           | Schemas  |
openapi-example.yml:21:7 | warning  | `#/components/schemas/ReferenceToID` is potentially unused or has been orphaned | oas3-unused-component | Schemas  | $.components.schemas['ReferenceToID']

Category | Errors | Warnings | Info
Schemas  | 1      | 1        | 0

Linting file 'openapi-example.yml' failed with 1 errors, 1 warnings and 0 informsError: failed with 1 errors

As you can see the error is missing, and this gives an impression in the editor that the spec has a problem when it does not.

do you still get the pb ?
🤔not sure what is wrong there , at least the command line in vacuum looks right ? isnt'it
it is true that the ReferenceToID has been orphaned , and that looks the unique error
btw updgrading to 3.1.0 will drop the error
make sure your neovim is using the right version of vacuum and adjust as well may be the base when running in neovim

What do you mean by pb?
I think I wasn't too clear on the actual issue.
Yes, the command line has no issue.
And yes, ReferenceToID is orphaned so this is expected in both the command line and neovim.
The only issue is that with the command line there is no error/warning for using a $ref to a schema from another schema while in the LSP provided for neovim, it is flagged as an error. And I believe this to be false negative as I believe it is perfectly valid to reference a schema object from another schema object.

Hi,
I looked at this today using v0.14.3
I saw this in the CLI

Which is correct.
The I loaded up VSCode and enabled the vacuum plugin
I saw this :

Same thing.
I can't help beyond this, I can't reproduce it using the language server (which is what you were seeing) or the CLI. They are in sync and doing the same thing.
Sorry I can't help more, but I don't use neovim, even so - when using the LSP, I still can't re-create it.


How to customize handleItemClick?

Hello!
So I managed to replace the fileRenderer with my React Component. But I'm still struggling to custom the onClick Event on the file.
I want to pass my function as props to the FileBrowser to get the key of the clicked file to use it in my app.
Any suggestions how I can pass the function?
Thanks!!

Yea wondering the same here

bump


Verbose tikz

It is not clear what error is raised by tikz sometimes. this attempts to be more informative when it does not render correctly.

Thank you, both for the contributions and your patience :)


Charts not be displaying

Why might charts not be displaying properly?In settings js/css connected

How I can reproduce the issue? Demo site looks okay:
https://demo.unfoldadmin.com/admin/


x/build: update NetBSD builders to NetBSD 8-beta

In https://go-review.googlesource.com/c/47036/, Christos Zoulas mentions that there are known bugs in the NetBSD 7.1 kqueue code and we should switch our builders to NetBSD 8-beta.
Also mentioned in https://github.com/golang/go/issues/20836#issuecomment-312066066
This is a tracking bug to update our NetBSD builders past 7.1
I've updated https://golang.org/wiki/MinimumRequirements too.
/cc @krytarowski @bsiegert @zoulasc @adams-sarah @andybons

This should also be fixed in  the 7.1 branch now, builds available from:
https://releng.netbsd.org/builds/netbsd-7-1/201707090640Z/

I would be more comfortable with a netbsd-8 system than with 7.1. http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=52034 is still pending, and it means that significant disk activity is likely to crash the VM, or make it hang.

@bsiegert, this doesn't boot on GCE as far as I can tell:
$ gomote create netbsd-amd64-8branch
Error running create: failed to create buildlet: 500 Internal Server Error: buildlet didn't come up at http://<IP_ADDRESS> in 5m0s

Please let me know once you've actually run it on GCE.
Until that time, Go will continue to not run NetBSD builders.

I didn't mean to close this. Reopened.

Are there any log messages on how -8 fails to boot on GCE, or are there any GCE hosts available for us to try?

I didn't have time to capture the serial console. I had assumed @bsiegert tested this.
You can create small GCE VM instances yourself for free: https://cloud.google.com/free/

The relevant bit from the serial console:
+ curl -H 'Metadata-Flavor: Google' 'http://metadata.google.internal/computeMetadata/v1/instance/attributes/buildle
t-binary-url'
Shared object "libssl.so.10" not found
+ curl -o /buildlet
Shared object "libssl.so.10" not found
+ echo 'giving up'
+ command echo 'giving up'
giving up
+ sleep 10
+ halt -p
Jul 15 19:11:28 netbsd8-builder-20170715 halt: halted by root

The binary packages are for NetBSD-7, and I suppose they are linked against base OpenSSL from NetBSD-7 :( Sorry for not catching this before sending out the CL.

Yes, it is unfortunate that there are no pre-built packages for -8 yet. I will work on that. Do you need anything else from me?

I'll try unpacking a /lib and /usr/lib from NetBSD-7 to fix this.

the better way is to make the symlinks to the missing shared libraries to point to the new ones...

@zoulasc That sounds unsafe if there was a major bump in between.

it is not an issue, people were just being conservative with libcrypto. OTOH if you replace libraries with older versions every binary on the system will break. But no worries, I'll have packages built soon.

@bsiegert, it still doesn't work.
Logs from the new x/build/cmd/debugnewvm tool running debugnewvm --host=host-netbsd-8branch --run-build=netbsd-amd64-8branch:
https://gist.github.com/bradfitz/3a6ba42ed3f9d7a47338e2172cfab9bb

Thanks for testing, and thanks for making me aware of debugnewvm.
It appears that this time, there has been a regression around setting routes. There is a default route via .0.1 but the host route to .0.1 is missing for some reason.

It took me a long time to find out, but it is a small bug in dhcpcd, the DHCP client. I will get this fix into NetBSD-8, then try again.

http://releng.netbsd.org/cgi-bin/req-8.cgi?show=266

Thanks, I'm looking forward to it. I started to require golang for llvm tsan.

Forgot to attach this to golang/build@664baafecb10b70a3011f9016f975188c6f82732, which was just merged.
@andybons, can you run a new netbsd-amd64 builder based on the image created from that script? Or should I send another CL to enable it? I have some access to things (from my google.com account) but probably not all of it.

I updated the image based on the latest change, and I get the following output from debugnewvm ...
https://gist.github.com/andybons/eed808dcd5201e4f74d165a47e54a710
It seems that the instance is coming up and serving on 80, but debugnewvm isn't able to connect.

Hopefully setting the correct MTU will fix this, see the CL I just sent.

You haven't booted this on GCE yourself yet?

Are we using the most recent -8? If so, then packages might be broken (unless they were regenerated) due to libstdc++ major bump.

On Tue, Nov 14, 2017 at 5:32 PM, Brad Fitzpatrick<EMAIL_ADDRESS>wrote:

You haven't booted this on GCE yourself yet?

No, but this has definitely helped with network issues in my other NetBSD
instances on GCE.

@krytarowski AFAICT, none of the packages we use (bash, curl, git-base, mozilla-rootcerts, go14) are in C++.

@andybons debugnewvm with the latest iteration of the image fails in exactly the same fashion as yours. However, from another VM in the same network, I can get the buildlet status just fine:
$ ftp -o- http://<IP_ADDRESS>
Requesting http://<IP_ADDRESS>
  0% |                                                            |     0        0.00 KiB/s    --:-- ETAbuildlet running on netbsd-amd64
100% |************************************************************|    33       79.76 KiB/s    00:00 ETA
33 bytes retrieved in 00:00 (60.57 KiB/s)

On the external address, port 80 appears to be firewalled, thus the connection times out. According to nmap, the only non-firewalled external ports are 22, 443 and 3389.

@bsiegert, thanks for confirming. And yes, I always run debugnewvm from withing the same GCE project that the buildlets will be running, to avoid the firewall (like the coordinator will be doing).

Running debugnewvm in another VM in the same project did the trick!
I got it to run a test suite, and I found a test failure I had not seen before (https://gist.github.com/bsiegert/80e5cf6cca5d656eef38dee398b7f843).

Ignore that error. That's known flaky #22665.

Have you got this commit:
Module Name:	src
Committed By:	christos
Date:		Sat Nov 11 03:58:01 UTC 2017

Modified Files:
	src/sys/kern: kern_event.c

Log Message:
Don't add kevents to closing file descriptors (from riastradh)

To generate a diff of this commit:
cvs rdiff -u -r1.97 -r1.98 src/sys/kern/kern_event.c

It's needed to fix another panic on NetBSD from golang.

Jamil, is that even in -8 yet?
Kamil Rytarowski<EMAIL_ADDRESS>schrieb am Mi. 15. Nov. 2017 um
21:49:

Have you got this commit:
Module Name:	src
Committed By:	christos
Date:		Sat Nov 11 03:58:01 UTC 2017
Modified Files:
src/sys/kern: kern_event.c
Log Message:
Don't add kevents to closing file descriptors (from riastradh)
To generate a diff of this commit:
cvs rdiff -u -r1.97 -r1.98 src/sys/kern/kern_event.c
It's needed to fix another panic on NetBSD from golang.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/20852#issuecomment-344723722, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA04Gqd8Bw3Ez-nf_PzmqMxXQgVHA8DAks5s205zgaJpZM4OJv1v
.

I meant @kamilrytarowski, thanks Autocorrect.
Benny Siegert<EMAIL_ADDRESS>schrieb am Mi. 15. Nov. 2017 um 22:15:

Jamil, is that even in -8 yet?
Kamil Rytarowski<EMAIL_ADDRESS>schrieb am Mi. 15. Nov. 2017
um 21:49:

Have you got this commit:
Module Name:	src
Committed By:	christos
Date:		Sat Nov 11 03:58:01 UTC 2017
Modified Files:
src/sys/kern: kern_event.c
Log Message:
Don't add kevents to closing file descriptors (from riastradh)
To generate a diff of this commit:
cvs rdiff -u -r1.97 -r1.98 src/sys/kern/kern_event.c
It's needed to fix another panic on NetBSD from golang.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/20852#issuecomment-344723722, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA04Gqd8Bw3Ez-nf_PzmqMxXQgVHA8DAks5s205zgaJpZM4OJv1v
.

No, I don't see even a pull-request.

The amd64 NetBSD 8+ builder is up and working.
The i386 kernel boots on GCE but never gets networking:
bradfitz@gdev:~/src/golang.org/x/build/cmd/buildlet$ debugnewvm  -host host-netbsd-386-8branch
2017/11/28 23:13:06 Creating debug-temp-1511910786 (with VM image "netbsd-386-8branch-a")
2017/11/28 23:13:07 instance requested
2017/11/28 23:13:24 instance created
2017/11/28 23:13:24 got instance info
2017/11/28 23:13:24 About to hit http://<IP_ADDRESS> to see if buildlet is up yet...
2017/11/28 23:13:29 client buildlet probe error: Get http://<IP_ADDRESS>: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2017/11/28 23:13:29 SERIAL: SeaBIOS (version 1.8.2-20171012_061934-google)
                            Total RAM Size = 0x0000000073300000 = 1843 MiB
                            Failed to get pci whitelist data
                            CPUs found: 2     Max CPUs supported: 2
                            found virtio-scsi at 0:3
                            virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
                            virtio-scsi blksize=512 sectors=8388608 = 4096 MiB
                            drive 0x000f3050: PCHS=0/0/0 translation=lba LCHS=522/255/63 s=8388608
                            Booting from Hard Disk 0...

                            >> NetBSD/x86 BIOS Boot, Revision 5.10 (from NetBSD 8.0_BETA)
                            >> Memory: 639/1886196 k

                                 1. Boot normally
                                 2. Boot single user
                                 3. Disable ACPI
                                 4. Disable ACPI and SMP
                                 5. Drop to boot prompt

                            Choose an option; RETURN for default; SPACE to stop countdown.
                            Option 1 will be chosen in 0 seconds.
                            17692960\
2017/11/28 23:13:30 About to hit http://<IP_ADDRESS> to see if buildlet is up yet...
2017/11/28 23:13:34 SERIAL:+681836+839668 [816032+834459+13083]=0x13ea18c
                            Loading /var/db/entropy-file
                            Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
                                2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017
                                The NetBSD Foundation, Inc.  All rights reserved.
                            Copyright (c) 1982, 1986, 1989, 1991, 1993
                                The Regents of the University of California.  All rights reserved.

                            NetBSD 8.0_BETA (GENERIC.201711280120Z)
                            total memory = 1842 MB
                            avail memory = 1792 MB
                            cpu_rng: RDRAND
                            rnd: seeded with 128 bits
                            running cgd selftest aes-xts-256 aes-xts-512 done
                            mainbus0 (root)
                            ACPI: RSDP 0x00000000000F3090 000014 (v00 Google)
                            ACPI: RSDT 0x00000000732FDC70 000034 (v01 Google GOOGRSDT 00000001 GOOG 00000001)
                            ACPI: FACP 0x00000000732FFF00 0000F4 (v02 Google GOOGFACP 00000001 GOOG 00000001)
                            ACPI: DSDT 0x00000000732FDCB0 0017B2 (v01 Google GOOGDSDT 00000001 GOOG 00000001)
                            ACPI: FACS 0x00000000732FFEC0 000040
                            ACPI: FACS 0x00000000732FFEC0 000040
                            ACPI: SSDT 0x00000000732FF590 000930 (v01 Google GOOGSSDT 00000001 GOOG 00000001)
                            ACPI: APIC 0x00000000732FF4A0 000076 (v01 Google GOOGAPIC 00000001 GOOG 00000001)
                            ACPI: WAET 0x00000000732FF470 000028 (v01 Google GOOGWAET 00000001 GOOG 00000001)
                            ACPI: Executed 1 blocks of module-level executable AML code
                            ACPI: Executed 1 blocks of module-level executable AML code
                            ACPI: 2 ACPI AML tables successfully acquired and loaded
                            ioapic0 at mainbus0 apid 0
                            cpu0 at mainbus0 apid 0
                            cpu0: Intel(R) Xeon(R) CPU @ 2.50GHz, id 0x306e4
                            cpu0: package 0, core 0, smt 0
                            cpu1 at mainbus0 apid 1
                            cpu1: Intel(R) Xeon(R) CPU @ 2.50GHz, id 0x306e4
                            cpu1: package 0, core 0, smt 1
                            acpi0 at mainbus0: Intel ACPICA 20170303
                            pckbc1 at acpi0 (KBD, PNP0303) (kbd port): io 0x60,0x64 irq 1
                            pckbc2 at acpi0 (MOU, PNP0F13) (aux port): irq 12
                            COM1 (PNP0501) at acpi0 not configured
                            COM2 (PNP0501) at acpi0 not configured
                            COM3 (PNP0501) at acpi0 not configured
                            COM4 (PNP0501) at acpi0 not configured
                            PEVT (QEMU0001) at acpi0 not configured
                            apm0 at acpi0: Power Management spec V1.2
                            ACPI: Enabled 16 GPEs in block 00 to 0F
                            pckbd0 at pckbc1 (kbd slot)
                            pckbc1: using irq 1 for kbd slot
                            wskbd0 at pckbd0 mux 1
                            pms0 at pckbc1 (aux slot)
                            pckbc1: using irq 12 for aux slot
                            wsmouse0 at pms0 mux 0
                            pci0 at mainbus0 bus 0: configuration mode 1
                            pchb0 at pci0 dev 0 function 0: vendor 8086 product 1237 (rev. 0x02)
                            pcib0 at pci0 dev 1 function 0: vendor 8086 product 7110 (rev. 0x03)
                            piixpm0 at pci0 dev 1 function 3: vendor 8086 product 7113 (rev. 0x03)
                            piixpm0: SMBus disabled
                            virtio0 at pci0 dev 3 function 0
                            virtio0: Virtio SCSI Device (rev. 0x00)
                            virtio0: no matching child driver; not configured
                            virtio1 at pci0 dev 4 function 0
                            virtio1: Virtio Network Device (rev. 0x00)
                            vioif0 at virtio1: Features: 0x30020<CTRL_VQ,STATUS,MAC>
                            vioif0: Ethernet address 42:01:0a:f0:00:16
                            virtio1: config interrupting at msix0 vec 0
                            virtio1: queues interrupting at msix0 vec 1
                            isa0 at pcib0
                            com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
                            com0: console
                            com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
                            com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, working fifo
                            attimer0 at isa0 port 0x40-0x43
                            pcppi0 at isa0 port 0x61
                            midi0 at pcppi0: PC speaker
                            sysbeep0 at pcppi0
                            isapnp0 at isa0 port 0x279
                            attimer0: attached to pcppi0
2017/11/28 23:13:35 client buildlet probe error: Get http://<IP_ADDRESS>: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2017/11/28 23:13:36 About to hit http://<IP_ADDRESS> to see if buildlet is up yet...
2017/11/28 23:13:39 SERIAL: acpicpu0 at cpu0: ACPI CPU
                            acpicpu1 at cpu1: ACPI CPU
                            WARNING: 1 error while detecting hardware; check system log.
                            boot device: <unknown>
                            root device:
2017/11/28 23:13:41 client buildlet probe error: Get http://<IP_ADDRESS>: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2017/11/28 23:13:42 About to hit http://<IP_ADDRESS> to see if buildlet is up yet...
2017/11/28 23:13:47 client buildlet probe error: Get http://<IP_ADDRESS>: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2017/11/28 23:13:48 About to hit http://<IP_ADDRESS> to see if buildlet is up yet...
2017/11/28 23:13:53 client buildlet probe error: Get http://<IP_ADDRESS>: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

@bsiegert, @krytarowski, any ideas?

Hmm, I'm not familiar with GCE myself.

GCE is KVM/virtio.
I'll let @bsiegert debug.

Your VM has no storage. Note this bit:
virtio0: Virtio SCSI Device (rev. 0x00)
virtio0: no matching child driver; not configured

I filed https://gnats.netbsd.org/52774 upstream.

Module Name:    src
Committed By:   martin
Date:           Wed Nov 29 16:10:01 UTC 2017

Modified Files:
        src/sys/arch/i386/conf: GENERIC

Log Message:
PR port-i386/52774: vioscsi missing in i386 kernel

http://mail-index.netbsd.org/source-changes/2017/11/29/msg090062.html

Diff for those curious:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/i386/conf/GENERIC.diff?r1=1.1170&r2=1.1171&only_with_tag=MAIN

https://releng.netbsd.org/cgi-bin/req-8.cgi?show=413 pullup to -8.

@bsiegert, I don't know how to tweak the netbsd-386 make.bash to pick up -CURRENT changes, so you'll have to send me that.

@bradfitz, tomorrow's build should have the change, so it is sufficient to rerun the generator script.

Update on Go on NetBSD:

With GOARCH=amd64, Go runs on NetBSD 8.0-BETA (amd64, 64-bit kernel), and all.bash now passes, both on GCE and in VMWare.

With GOARCH=386, GO runs on NetBSD 8.0-BETA (i386, 32-bit kernel), and all.bash now passes on VMWare, but not yet on GCE, due to the virtioscsi config issue.

With GOARCH=386 (and GOHOSTARCH=386), Go spins 100% CPU in go_bootstrap during the Building Go toolchain2 using go_bootstrap and Go toolchain1 step when running on NetBSD 8.0-BETA (amd64, 64-bit kernel), on both GCE and VMWare.

... but with just GOARCH=386 (and not setting GOHOSTARCH), make.bash doesn't spin.

So while we could perhaps put up our Mission Accomplished banner once the 32-bit NetBSD runs on GCE, or by not setting GOHOSTARCH=386, I'm afraid there's still some issue here, perhaps in how NetBSD's amd64 kernel handles the 32-bit compat syscalls.
@bsiegert, can you reproduce?
The $GOROOT_BOOTSTRAP I used was https://storage.googleapis.com/go-builder-data/gobootstrap-netbsd-amd64-bbd15ff.tar.gz (prepared today from Go tip), untarring that inside my $HOME/go1.4 (even though it's not 1.4, but that's the default path). Or set GOROOT_BOOTSTRAP to your bootstrap dir.

To clarify: with GOARCH=386 (and no GOHOSTARCH) on 64-bit NetBSD, only make.bash. Tests still fail (random timeouts, hangs) on both GCE and VMware. I've reenabled the netbsd-386 Go builder with a 64-bit kernel for now, but it's all red.

@bsiegert, I just rebuilt the 386 image. It boots saying NetBSD 8.0_BETA (GENERIC.201711301510Z) which is newer than the<PHONE_NUMBER>20Z I see above. But still no luck:
virtio0: Virtio SCSI Device (rev. 0x00)
virtio0: no matching child driver; not configured

I'll try again tomorrow.

https://releng.netbsd.org/cgi-bin/req-8.cgi just monitor 413. Martin who committed the fix cannot pullup it and we need another person from releng to test and merge the patch.

@krytarowski, thanks for the info & link!

@bsiegert, the NetBSD/386 VM now boots on GCE, but I can't find any NetBSD mirror with binary packages for i386, which means we have no curl and we can't download the buildlet.
The builder script fails on these lines,
https://github.com/golang/build/blob/master/env/netbsd-amd64/mkvm.py#L63
But doesn't stop building the VM image on error.
localhost# PS1='anita-root-shell-pr''ompt-1512499919.93# '
PS1='anita-root-shell-pr''ompt-1512499919.93# '
anita-root-shell-prompt-1512499919.93# env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All/ pkg_add bash curl
env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All/ pkg_add bash curl
pkg_add: Can't process http://ftp.netbsd.org:80/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All//bash*: Not Found
pkg_add: no pkg found for 'bash', sorry.
pkg_add: Can't process http://ftp.netbsd.org:80/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All//curl*: Not Found
pkg_add: no pkg found for 'curl', sorry.
pkg_add: 2 package additions failed
anita-root-shell-prompt-1512499919.93# echo exit_status=$?=
echo exit_status=$?=
exit_status=1=
anita-root-shell-prompt-1512499919.93# exec /bin/sh
exec /bin/sh
localhost# PS1='anita-root-shell-pr''ompt-1512499922.04# '
PS1='anita-root-shell-pr''ompt-1512499922.04# '
anita-root-shell-prompt-1512499922.04# env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All/ pkg_add git-base
env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All/ pkg_add git-base
pkg_add: Can't process http://ftp.netbsd.org:80/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q2/All//git-base*: Not Found
pkg_add: no pkg found for 'git-base', sorry.
pkg_add: 1 package addition failed

Does somebody build i386 packages?
Or do we need to build from source? (That's what I did on my test NetBSD/i386 VM, but it was super tedious and involved checking out all of the pkgsrc cvs repo.... I'd rather not do that all in qemu)

We need to rebuild the packages for NetBSD-8/i386.
I've noted execution of "race" tests for FreeBSD, Linux, Windows - is this ThreadSanitizer (TSan) related? If so, we could add a NetBSD/amd64 target.

@krytarowski, who rebuilds packages? When can that be done by?
As for race detector support, that's unrelated to this issue. There is at least #19273 open for more platform support. Or you could file a new bug. But it would likely require upstream TSAN support. It won't happen for Go 1.10.

We, have already passed the requests internally to responsible developers.If I recall correctly, Manuel Bouyer was generating them.. however -current branches (like -8) are special cases so they will be generated on demand.

Oh, you already ported TSAN (https://blog.netbsd.org/tnf/entry/one_year_checkpoint_and_thread). Feel free to file a new bug for tracking Go support.

I am trying to build i386 packages for NetBSD-8.0...

There should be packages now for 8.0 + i386. Please let me know if I missed any dependencies.

@zoulasc, I don't seen mozilla-rootcerts here:
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/8.0_2017Q3/All/
The complete set we try to install is:
    "env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/%s/%s/All/ pkg_add bash curl" % (arch, release),
    "env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/%s/%s/All/ pkg_add git-base" % (arch, release),
    "env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/%s/%s/All/ pkg_add mozilla-rootcerts go14" % (arch, release),
    # Interactive debugging tools for users using gomote ssh:
    "env PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/%s/%s/All/ pkg_add emacs25-nox11 vim screen" % (arch, release),

But emacs, vim, screen, go14, and even git-base should be optional. They're more nice-to-have for debugging. But without mozilla-rootcerts, curl & Go might have issues fetching resources.

stay tuned :-)

you should have everything but emacs... which should come later.

@zoulasc, thanks. I'm kicking off a build of the image.

thank you for all your patience :-) I am building git now.

Okay, deployed. I have it configured to only use 1 VM at a time so it won't use our self-imposed 500 VM quota all at once to catch up, but it'll catch up slowly on its own. I ran one test build manually and watched it get through the start, so I see networking on GCE now works, and bash & curl work, the buildlet starts (I needed to rebuild it for the sysctl fix), and make.bash starts running. I assume it'll be fine. Famous last words. Off to sleep...
Thanks again, @zoulasc and @bsiegert and @krytarowski!

Thanks for your effort! The next release should ship with TSan, NSan and ARM CI machines on NetBSD!

Really impressed with all the collaboration on this effort. Nice work, everyone! 🎉

And looks good this morning. Still some flakes here & there, but much better.
I'm going to close this bug. We can open new ones for specific issues that come up.


no optimizations made

Sorry if I'm making an obvious mistake, but can you point out what I'm doing wrong? I tried to use cssnano for autoprefixer and rule compacting, but all it seems to be doing is removing whitespace
$ cat dist/css/test.css
div {
	margin: 0;
	margin: 1rem;
	appearance: none;
}
$ cssnano dist/css/test.css dist/css/test.min.css
$ cat dist/css/test.min.css
div{margin:0;margin:1rem;appearance:none}

I expected it to look like this:
div{margin:1rem;-webkit-appearance:none;-moz-appearance:none;appearance:none;}

You're not doing anything wrong; no prefixes are added as autoprefixer is used in a removal only capacity; this is a compression tool. See http://cssnano.co/optimisations/#autoprefixer. 😄
Secondly, we don't support declaration merging yet; there is an open issue for it. https://github.com/ben-eb/cssnano/issues/86


Update README to reflect v3 migration

Resolving issue #21

Coverage remained the same at 94.723% when pulling 632bd3394d1de53933e76666cb44d824773bdcd9 on iss-21 into 47f9466a2a7dffc6be5a603ff7d468d9a28fb036 on master.


Add Will's page

I added my html pages to the archive.
Thanks for hosting such a cool event :)

I can't seem to merge, could you do it for me?

Oh, sorry, I thought you had the option. Going in now!


Fix a grammer in a code comment

Hi
This is a small pull request to fix a grammer in a code comment.
Please check it out. Thanks!

Coverage decreased (-1.8%) to 96.626% when pulling 04b68d8fcd3320dd56125cd33967a01c13e01718 on garigari-kun:fix-a-grammer into 914435da7ba2f0919c06f8309f629b3a639a1b80 on devise-security:master.


Keys with '-' are ignored. using ['key'] might solve the problem.

I have the same issue, making this package pretty useless for mow. Very unfortunate.


Added option --composer-dir to the sql:build command

Hi There
I ran into a situation where I have a behaviour thats part of of my main project, and when I ran the sql:build command, it complained about not being able to find my behaviour because it was using a different composer directory, and therefore wanted me to provide the composer-dir option (I have a fairly complex project structure, with modules and plugins). Upon adding the composer-dir option, Propel told me that it wasn't an option for the command sql:build. So upon inspecting the command, lone behold it doesn't exist. After adding it and running the sql:build command again with --composer-dir, everything worked as expected.
Im aware you are in the process of making a massive change with the internals of propel, but I'm offering this small fix anyway (in case someone ran into a similar issue :) ).
Cheers

Sounds good, thanks!


Adding metrics-server support for K8s version 1.9

Adding support for Kubernetes Metrics Server.
From the 1.8 changelog
Consuming metrics directly from Heapster is deprecated in favor of consuming metrics via an aggregated version of the resource metrics API.

In version 1.8, enable this behavior by setting the --horizontal-pod-autoscaler-use-rest-clients flag to true.

In version 1.9, this behavior will be enabled by default, and must be explicitly disabled by setting the --horizontal-pod-autoscaler-use-rest-clients flag to false.```

https://github.com/kubernetes-incubator/metrics-server/ is now needed to support Autoscaling.

ci check this

I haven't 100% tested this, but at first run, the aggregator cert was not landing on the other masters i have. this was remedied by implimeting the following patch
diff --git a/roles/kubernetes/secrets/tasks/check-certs.yml b/roles/kubernetes/secrets/tasks/check-certs.yml
index 782da686..bc5e3524 100644
--- a/roles/kubernetes/secrets/tasks/check-certs.yml
+++ b/roles/kubernetes/secrets/tasks/check-certs.yml
@@ -105,6 +105,7 @@
       {% if gen_node_certs[inventory_hostname] or
         (not kubecert_node.results[0].stat.exists|default(False)) or
           (not kubecert_node.results[10].stat.exists|default(False)) or
+          (not kubecert_node.results[7].stat.exists|default(False)) or
             (kubecert_node.results[10].stat.checksum|default('') != kubecert_master.files|selectattr("path", "equalto", kubecert_node.results[10].stat.path)|map(attribute="checksum")|first|default('')) -%}
               {%- set _ = certs.update({'sync': True}) -%}
       {% endif %}
diff --git a/roles/kubernetes/secrets/tasks/gen_certs_script.yml b/roles/kubernetes/secrets/tasks/gen_certs_script.yml
index 9be59fb7..4038d211 100644
--- a/roles/kubernetes/secrets/tasks/gen_certs_script.yml
+++ b/roles/kubernetes/secrets/tasks/gen_certs_script.yml
@@ -84,6 +84,8 @@
                       'admin-{{ inventory_hostname }}-key.pem',
                       'apiserver.pem',
                       'apiserver-key.pem',
+                      'kube-controller-manager.pem',
+                      'kube-controller-manager-key.pem',
                       'kube-scheduler.pem',
                       'kube-scheduler-key.pem',
                       'kube-controller-manager.pem',

I would also imagine someone would want to test with vault ( i haven't used the vault method)
and lastly, I think we should add the apiserver flags in if kube_version > =1.9.

Hi, why we need create additional certs for metrics-server?
I think we can run metrics-server like other addons, after k8s is running.
Metrics-server deployments.

@chapsuk Tried that. Not working. You need to provice the options to the kube-apiserver.
This also requires a certificate and it seems recommended to create it's own.

what k8s version you using?
I'm running metrics-server by source deployment on 1.9.2 and it's working great. HPA with prometheus-adapter works too.

yep, RBAC enabled

What arguments did you add to the apiserver to get it to work? I have tried to deploy the metrics-server from source on a new cluster build with Kubespray from the master branch. Did not work for me.

How it described in pr description
In version 1.9, this behavior will be enabled by default

i didn't set any additional flags.
Can you describe what exactly does not work?

when turning up metrics-server, the pod displays the following, which led us down this path:
cluster doesn't provide requestheader-client-ca-file

To get the certs to sync to the other masters, I had to add the following:
index 782da686..bc5e3524 100644
--- a/roles/kubernetes/secrets/tasks/check-certs.yml
+++ b/roles/kubernetes/secrets/tasks/check-certs.yml
@@ -105,6 +105,7 @@
       {% if gen_node_certs[inventory_hostname] or
         (not kubecert_node.results[0].stat.exists|default(False)) or
           (not kubecert_node.results[10].stat.exists|default(False)) or
+          (not kubecert_node.results[7].stat.exists|default(False)) or
             (kubecert_node.results[10].stat.checksum|default('') != kubecert_master.files|selectattr("path", "equalto", kubecert_node.results[10].stat.path)|map(attribute="checksum")|first|default('')) -%}
               {%- set _ = certs.update({'sync': True}) -%}
       {% endif %}
diff --git a/roles/kubernetes/secrets/tasks/gen_certs_script.yml b/roles/kubernetes/secrets/tasks/gen_certs_script.yml
index 9be59fb7..33b81a49 100644
--- a/roles/kubernetes/secrets/tasks/gen_certs_script.yml
+++ b/roles/kubernetes/secrets/tasks/gen_certs_script.yml
@@ -85,6 +85,8 @@
                       'apiserver.pem',
                       'apiserver-key.pem',
                       'kube-scheduler.pem',
+                      'aggregator-proxy-client.pem',
+                      'aggregator-proxy-client-key.pem',
                       'kube-scheduler-key.pem',
                       'kube-controller-manager.pem',
                       'kube-controller-manager-key.pem']

@whereismyjetpack Can you confirm that HPA now works for you now on a 1.9.2 cluster with this PR and metrics-server deployed.

This PR allows metrics-server based hpa, verses using heapster.

is it ready to merge? @woopstar

The params for apiserver need to be added for kubeadm as well.
Vault requires a new param for the aggregator. Look at the proxy role here: https://github.com/kubernetes-incubator/kubespray/blob/master/roles/vault/defaults/main.yml#L143
@chapsuk should be able to help here.

looks good!
i'm runned vault CI and try to check this changes locally, need some time

Awesome


fix:soul-admin中AppAuthMapper 中 insertSelective方法

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #560 (f6cdd18) into master (49ad241) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #560   +/-   ##
=========================================
  Coverage     22.48%   22.48%
  Complexity      374      374
=========================================
  Files           197      197
  Lines          4656     4656
  Branches        496      496
=========================================
  Hits           1047     1047
  Misses         3508     3508
  Partials        101      101

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 49ad241...f6cdd18. Read the comment docs.


add setup.py

Hello Abdur,
I made a new setup.py for honeybot.
Could you please tell me how can I show you my code? I can't create a new branch in your project.
Thank you!

just click create new file on honeybot project (my project), then click propose new file. complete for pull request. that's easier for a begining than forking, branching and PR

Done, just created file and made a PR.


[EVENT REQUEST] Skip planning in report 699 after deleting the requisition lines.

Hello,
could we get this event? Thank you.
report 699 "Calculate Plan - Req. Wksh."
{
    Caption = 'Calculate Plan - Req. Wksh.';
    ProcessingOnly = true;

    dataset
    {
        dataitem(Item; Item)
        {
            DataItemTableView = SORTING("Low-Level Code") WHERE(Type = CONST(Inventory), Blocked = CONST(false));
            RequestFilterFields = "No.", "Search Description", "Location Filter";

            trigger OnAfterGetRecord()
            var
                IsHandled, Skip: Boolean;
            begin
                if Counter mod 5 = 0 then
                    Window.Update(1, "No.");
                Counter := Counter + 1;

                if SkipPlanningForItemOnReqWksh(Item) then
                    CurrReport.Skip();

                PlanningAssignment.SetRange("Item No.", "No.");

                ReqLine.LockTable();
                ActionMessageEntry.LockTable();

                IsHandled := false;
                OnBeforeDeleteReqLines(Item, PurchReqLine, ReqLineExtern, IsHandled);
                if not IsHandled then begin
                    PurchReqLine.SetRange("No.", "No.");
                    PurchReqLine.ModifyAll("Accept Action Message", false);
                    PurchReqLine.DeleteAll(true);

                    ReqLineExtern.SetRange(Type, ReqLine.Type::Item);
                    ReqLineExtern.SetRange("No.", "No.");
                    if ReqLineExtern.Find('-') then
                        repeat
                            ReqLineExtern.Delete(true);
                        until ReqLineExtern.Next() = 0;
                end;

                // >>>
                Skip := false;
                OnItemOnAfterDeleteReqLines(Item, Skip);
                if Skip then
                    CurrReport.Skip();
                // <<<
                InvtProfileOffsetting.SetParm(UseForecast, ExcludeForecastBefore, CurrWorksheetType);
                InvtProfileOffsetting.CalculatePlanFromWorksheet(
                  Item,
                  MfgSetup,
                  CurrTemplateName,
                  CurrWorksheetName,
                  FromDate,
                  ToDate,
                  true,
                  RespectPlanningParm);

                if PlanningAssignment.Find('-') then
                    repeat
                        if PlanningAssignment."Latest Date" <= ToDate then begin
                            PlanningAssignment.Inactive := true;
                            PlanningAssignment.Modify();
                        end;
                    until PlanningAssignment.Next() = 0;

                OnItemOnAfterGetRecordOnBeforeCommit(ReqLine, Item, CurrTemplateName, CurrWorksheetName, FromDate);
                Commit();
            end;
...
[IntegrationEvent(false,false)]
local procedure OnItemOnAfterDeleteReqLines(Item: Record Item; var Skip: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


posit cloud

provide guidance on how to request posit cloud access and use

who knows about this? Could this person either make a PR or add notes here so I'd edit https://guide.rladies.org/organization/tech/accounts/ (unless it seems better to store the info somewhere else)?

A couple of this issues are made by the leadership as reminders to our selves to make the content. This one is Shannon and myself :)

Ok! Let me add assignments to do tidy GitHub project management à la @drmowinckels :stuck_out_tongue_winking_eye:

What do you think about separating it and moving event tooling (meetup & posit cloud) to events section?

Sounds good!
So sorry for the huge delay :grimacing:


Get questionnaire score displaying after completion

Use Case
When a user completes a questionnaire, wants to see their outcome without having to go to the Trends tab
Problem
Not easy to do this via ResearchKit pre-designed pages
Solution
Create a custom page?
Alternatives considered
Not sure
Additional context
No response
Code of Conduct

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

Done using custom view at end! PR #109


Plugin does not encode non ASCII chars

Trying to add a file to the project with @ in the path name, I didn't get the non ASCII character encoded.
The issue caused Visual Studio to see two files in the solution, actually pointing to the same file on disk.
// E.G.

// expected
<TypeScriptCompile Include="path\to\my\file\%40folder\file-name.service.ts" />
// got
<TypeScriptCompile<EMAIL_ADDRESS>/>

Visual Studio v. 15.4.1 (Community Edition)
Visual Studio Code v. 1.18.0

Fixed in #18


License is missing

Hey! I'd actually love to use this as an basis for my blog. Unfortunately, if a license was never set, all rights are reserved to you and I am not allowed to use the code formally.
Would it be okay if you license it?
If you just want people to use it without being legally required to disclose this tutorial, CC0 or UNLICENSE would make sense.
Otherwise probably Apache2 oder MIT, GPL is most likely too restrictive for the community!
### Tasks
- [ ] Decide on a License
- [ ] Add the License to the Repo

Hi @lquenti! Thank you for this message, and yes, let's get this figured out!
We typically use the MIT license for Astro public repos. You can see all our templates, which are also available for use, here: https://github.com/withastro/astro/tree/main/examples
I assume since all of these templates exist under the main withastro/astro repository, they are all covered by the license in the root of the project and therefore do not show up in each individual starter template.
I will loop @FredKSchott into this conversation, but my assumption is that we can add the same MIT license here to this repository.

Thanks @lquenti — just added an MIT license to the repo. Thanks for letting us know it was missing 🙌


There is no asteroid photometry being done.

Description
Currently, aperture photometry on an asteroid is not performed. Because of this, the MPC record derivation cannot have the magnitude associated with it as well.
The photometric engine does not have any knowledge of the location of the object so it cannot do aperture photometry of the target. It can be given the target location optionally to compute the aperture photometry (this is likely the best solution and the one which should be implemented).
Alternatively, aperture photometry of the target can be left up to the OpihiSolution class; but it seems weird for something that is primarily a photometric job to be not in the photometric solution.

Currently the asteroid photometry value being provided is 0.0 when a photometric solution is done.
It is not providing any value if a photometric solution is not done as expected.


Generation of the End and the Nether default is not working.

Minecraft version
1.19.2
LibX version
1.18.2-3.2.18
Skyblock Builder version
1.18.2-3.3.25
Forge version
40.2.1
The latest.log file
https://pastebin.com/KYwE2L8L
Issue description
Is it possible to put so that I try the Nether and the End to generate the normal world? Because even if I put Default true, they still continue to generate nothing.
`"Dimensions": {
"End": {
// Should end generate as in default world type? [default: false]
"Default": true,
// Should the main island be generated as normal? [default: true]
"mainIsland": true
},
"Nether": {
// Should nether generate as in default world type? [default: false]
"Default": true
},
"Overworld": {
// Should overworld generate as in default world type? [default: false]
"Default": false
}
},`
Steps to reproduce
No response
Other information
No response

Sadly, I can’t see the log. Did you configure it as private paste, or do I just need for moderation? If you set it to private, please create a public one, else I’m just waiting until it’s approved :)

https://gist.github.com/rlcoldx/59f2793c46fc42b1a2cecfa9be4d5812

That was it. I generated a new level.dat and now it worked normally. Thanks.


Fix issue where an engine could be nested in another engine

Solve this by ensuring when we enumerate the engines we look at deeper engines first.
@jrafanie Please review.
This PR also changes the stubbing of the Rails Engines paths a little higher so we can exercise more of the code in rails_engines_paths.

@jrafanie I rekicked manageiq-api - run is here: https://github.com/ManageIQ/manageiq-api/actions/runs/10949539587

🎉


Feature Request: Allow root for users of Kali Linux

Because of what this app does, there is a higher than normal probability the user will be running Kali Linux, and as we all know, Kali's default user account is root. Since they might not want to create a separate user account just for this script, a good resolution would be the creation of a system account solely to run this script as.
It would be nice if this resolution were included in the installation script, or if Kali users could disable the non-root user requirement.

Hi,
The default user of kali linux is not root. When you setup kali linux it generates a normal user for you and that user is in the Group of root. What you're telling is not secure. It happens to be in old versions of kali linux but currently, kali doesn't provide what you are telling.
I will update this tool after 1 month. I might add root feature as well


RTC: STM32: Add alarm support for all STM32 MCU series

This PR implements rtc_driver_api Alarm functions for the 2 alarms, A & B, of STM32 RTC device.
Tested on all the boards that have been added in the tests/drivers/rtc/rtc_api/boards.

why are there two PRs ?  #71965

why are there two PRs ? #71965

A pure coincidence :)

After #71784 was merged, the y2k test is now skipped automatically if the RTC correctly returns -EINVAL if the time is outside if its range, like before 2000 :) Could you try try to rebase and run the test suite without the commit excluding the y2k test?

After #71784 was merged, the y2k test is now skipped automatically if the RTC correctly returns -EINVAL if the time is outside if its range, like before 2000 :) Could you try try to rebase and run the test suite without the commit excluding the y2k test?

Done.

Does it allows to cover all boards used on the bench ?

No, a .overlay & a .conf should be added for each board for it to be tested. Also the RTC source clock must be configured in .dtsof each board. Alternatively, a specific test case can be added for STM32 boards in testcase.yaml with a common overlay & .conf.

Great! Is RTC_ALARM_TIME_MASK_NSEC support when HW_SUBSECOND_SUPPORT==1 planned in another step?

Great! Is RTC_ALARM_TIME_MASK_NSEC support when HW_SUBSECOND_SUPPORT==1 planned in another step?

Yes.


Update getting-started.md

Some edits to docker-compose commands that would fox a newbie.

@harrisonpim for your review.

Ooh, thanks for the PR! 😁
The latest version(s) of docker actually allow you to run compose as a command within docker, without needing to install a separate docker-compose command https://docs.docker.com/engine/reference/commandline/compose/

I'm going to leave these lines as they are, but the general point about docker newbies is well taken. I might add some info on getting started with docker to the /docs folder, or add a link to a blog post with the info people might need.


Lovelace Baidu Map

Describe why you are flagging this

is this supposed to convey an actual message? this tells us nothing...


refactor cmd/build to be more testable

Description of the change:
Refactor cmd/build to be more testable. This includes making a struct to contain the info needed to execute the command, a validate method that parses the args, and a run method containing the execution.
I actually have a question about the project root check that is currently here.. That helper method appears to exit directly instead of bubbling an error up, which makes it extremely difficult to test, as the test process just blows up. What is the reasoning for exiting directly instead of returning an error and letting the calling environment handle it, which seems to be the more normal golang style?
Motivation for the change:
See #3246

Hi @jberkhahn,
Are you ok with we close this one since we will replace very soon the operator-sdk build for make docker-build and all here will be removed? PS. Note that it was made for GO already and we are working on to do the same for Ansible and Helm.


chore(release): 1.19.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7614c96eff540efbf3e0b680cbe13944833fef19
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


azcopy list - show only top level directories

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.3.4
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy list
What problem was encountered?
It shows list of all files recursively, but we want to show only list of directories at the top level.
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?

I'd also like to have this feature. Our directories have hundreds of thousands of files in subdirectories, so it makes azcopy ls uninformative.

yes, I would like to have this feature. I have a set of subdirectories with a large number of files ( thousands maybe millions ) so the plane azcopy list command becomes very time consuming and difficult to deal with.

+1 here

bash workaround...
# find top level contents
azcopy ls "https://{store}.blob.core.windows.net/{dir}?SAS" | cut -d/ -f 1 | awk '!a[$0]++'

# find directories with depth N
N=3
azcopy ls "https://{store}.blob.core.windows.net/{dir}?SAS" | cut -d/ -f 1-${N} | awk '!a[$0]++'

+1 here

Same here, I sync many thousands of files with azcopy. The workaround to cut the top-level directories works, but is very slow.
I recommend an optional parameter like "--depth" to determine the required level. But a parameter "--top-level-only" would also work for me.

Yes, this is sorely needed...

sftp:// is the best workaround if you can afford it.
I recommend the lftp client, it has been working great for us. lftp has a mirror command that has been working much, much better than azcopy sync.
You can of course use any other sftp:// client at the same time, they're not mutually exclusive.
Here's a list of other azcopy bugs that lftp + sftp:// does NOT have:

#1973, #1974, #1975, #221, #718, #1294, #1215,...

+1

+1

Please delete "+1" comments and use the "thumbs up" button at the top. Unlike "+1" comments, the latter is usable by both machines and humans.

This is a work around using python's azure-blob-storage sdk
from azure.storage.blob import BlobServiceClient
from azure.storage.blob import BlobPrefix

# Replace these with your actual connection string and container name
connection_string = "your_connection_string"
container_name = "your_container_name"

# Create a BlobServiceClient
blob_service_client = BlobServiceClient.from_connection_string(connection_string)

# Get a reference to the container
container_client = blob_service_client.get_container_client(container_name)

# List only the top-level directories (virtual directories)
directories = set()

# Use walk_blobs with delimiter="/" to list virtual directories only
for blob in container_client.walk_blobs(name_starts_with='folder/where/you/want/to/ls/', delimiter='/'):
    if isinstance(blob, BlobPrefix):
        directories.add(blob.name[:-1])  # Remove trailing '/' from the name

# Print the top-level directories
for directory in directories:
    print(directory)

Unfortunately, we are not going to add this functionality.  We are focused on documentation, testing, and quality, and this feature would represent a large increase in scope for the product.

Not doing something is hardly ‘completing’ it…

Closed reasons are a relatively new feature:
https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/
That's probably why they have been barely used:
https://github.com/Azure/azure-storage-azcopy/issues?q=is%3Aclosed+-reason%3Acompleted+
https://github.com/Azure/azure-storage-azcopy/pull/1  was in 2018


Deploy urban farm land locator so that Aaron can begin using it

Get Aaron to add 5 parcels to app.


Doesn't build with recent atdgen due to generated [@@@ocaml.warning ...]

The opam package wcs-lib doesn't build due to atdgen producing [@@@ocaml.warning ...] at the beginning of ml and mli files.
$ make
jbuilder build @install
        rmlc wcs-lib/wcs_t.rzi (exit 2)
(cd _build/default/wcs-lib && /home/martin/.opam/ocaml-base-compiler/bin/rmlc.opt -c wcs_t.mli)
File "wcs_t.mli", line 2, characters 14-15:
Syntax error
Makefile:23: recipe for target 'build' failed
make: *** [build] Error 1

(* Auto-generated from "wcs.atd" *)
              [@@@ocaml.warning "-27-32-35-39"]

(**
  Watson Conversation Service data structures.

  Data structures used in Watson Conversation Service.

  Based on the documentation available at:
  https://www.ibm.com/watson/developercloud/conversation/api/v1/

  Version 2017-05-26.
*)

Thank you for the notice. It should be closed by #73.


Should quartiles in vx/boxplot be switched?

vx/boxplot requires firstQuartile and thirdQuartile to render the boxplot.
From my understanding of summary statistics, the standard order of the values should be:
min < firstQuartile < median < thirdQuartile < max
Currently, vx/boxplot renders the box when:
min < thirdQuartile < median < firstQuartile < max
Should vx/boxplot follow the first or the second ordering?
See this sandbox for an implementation

Hi @trainorpj thanks for checking out vx and for the helpful example code!
Here's an updated take on your example: https://codesandbox.io/s/v25Vm3Q15

@vx/boxplot expects the y axis to increase in value pointing up, which means it always expects max to be the top line. Looks like you're trying to draw an inverted box plot, which the current @vx/boxplot doesn't allow at the moment. This is because when boxplot goes to draw the box it draws a rect region starting at y={thirdQuartile} with height={firstQuartile - thirdQuartile}.  Your first screenshot doesn't show a box because height={-170} in that example. The solution here is to pass in scaled values starting with max at the top and min on the bottom.
So the current @vx/boxplot api expects scaled values where the y axis increases going towards the top of your screen. We should make it so it can support the inverted case where y axis increases going towards the bottom of your screen to.
Hope that helps and thanks for opening up the issue for clarification. We will look into adding this in an upcoming release.

Thanks @hshoff for taking the time to respond! This makes a lot of sense, especially if you're making reusable charts with svg-coordinates in mind :grin:


AuthorizationError issues - No public accessors and lacking of toString

Before opening, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

Bug Category
Other
Describe the bug
Hello team, would appreciate the help in the following issues
Version: 4.2.2

Add public getters to AuthorizationError
AuthorizationSuccessResponse.getErrors() exposes AuthorizationError, but it lacks public accessors.
Could you please provide some getters so we can access AuthorizationError fields? We use them for logging/debugging and mapping the errors to internal representations.
Note: getErrors() returned strings in the 3.x versions and we used them for logging, so we are losing debugability without the accessors in the newest version.

Override toString in AuthorizationError
AuthorizationSuccessResponse.toString() references diagnostics.errors, but given that AuthorizationError doesn't override toString, it returns the memory reference instead of the string representation.

Expected behavior

Being able to access policyId and error within AuthorizationError
Return String representation of diagnostics.errors

Reproduction steps

Tried to access fields within any AuthorizationError instance
Example code and string resulted:

final Diagnostics diagnostics = new Diagnostics(new HashSet<>(reasons), List.of(new AuthorizationError("policy", new DetailedError("message", Optional.empty(), Optional.empty(), Optional.empty(), Optional.empty(), Optional.empty(), Optional.empty()))));
final AuthorizationSuccessResponse authorizationSuccessResponse = new AuthorizationSuccessResponse(decision, diagnostics);
final String authString = authorizationSuccessResponse.toString();

Code Snippet
// Put your code below this line.

Log output
// Put your output below this line

Additional configuration
No response
Operating  System
MacOS
Additional information and screenshots
No response

Hi thanks for opening this, we agree that these functions should be added. This looks like an oversight when moving from strings to more structured error types


Alternative to identify the digest of a docker image

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
Docker
Description
While testing a private registry, I identified https://github.com/deitch/docker_registry2/issues/83
With various usages in our codebase such as
https://github.com/dependabot/dependabot-core/blob/570898ac6071113c268403d0ca5f946108fb55cc/docker/lib/dependabot/docker/update_checker.rb#L248
We might need to either :

Find an alternative method (as described in the issue) and update our code base
Wait (or contribute) to the upstream library to fix the problem and update our version

In either case, I think that it is worth tracking here for visibility. Please share your thoughts

Update:
We're currently making progress at the original repository https://github.com/deitch/docker_registry2/pull/85 and hopefully we'll close this soon


api-ms-win-core-path-l1-1-0.dll missing

Describe the bug
install with MSI installer, invoke the wsgidav from commandline, it prompts
api-ms-win-core-path-l1-1-0.dll missing
To Reproduce
Steps to reproduce the behavior:

download WsgiDAV-<IP_ADDRESS>-win64.msi
Click and install
run wsgidav from the command line
See error

Environment:
windows 7 x64,

Additional context
searching api-ms-win-core-path-l1-1-0.dll on my pc with everything.exe results in no file.

I assume this is specific to the legacy windows version.
Windows 7 support ended on January 14, 2020 and I don't have plans to support this any more.
Please let us know if it happens an recent platforms as well, thanks.

it works on my win10 x64 laptop. thanks.


As a user, I would like the option to start the app at login

Basically implement this package: https://github.com/sindresorhus/LaunchAtLogin

New API in macOS 13:
https://github.com/sindresorhus/LaunchAtLogin/issues/76


React Native support

Can we have support for react native.

Sadly, no. React Native doesn't have use DOM elements, so the entire thing would be need to be re-written specifically for that. Although....maybe someday

+1 @justin-schroeder you can ?

How difficult would it be to write a rn reanimated integration?


Enable geolocation for notice logs

A community user asked in a public Slack message:

How can I get the remote location information to show up?

These are fields on Zeek's notice logs. The geoip-conn package that's enabled in the Zeek that's included with Brimcap does provide some geolocation data. However, a closer look at the Zeek docs explains that these fields are only populated in the notice logs if that https://docs.zeek.org/en/master/scripts/base/frameworks/notice/actions/add-geodata.zeek.html is loaded, and it looks like that's not loaded by default in our Zeek. This should be pretty easy to enable once we create our next round of Zeek artifacts. While we're at it, it's probably worthwhile to look around for any other non-conn logs that might have geolocation fields that are disabled by default that we can toggle.
In the meantime, as shown in the following video taken with Brim v0.31.0, it's pretty easy for users to pivot from a notice record to the corresponding conn record and see if the geo fields are populated, such as they are in this example with a wrccdc pcap.
https://user-images.githubusercontent.com/5934157/221300342-a612171e-b041-4f74-beb5-a576b94dd88f.mp4

I just looked into adding this. Based on my testing described in https://github.com/zeek/zeek/issues/3674, it seems the Zeek build we use is already prepared to populate this info, except there's a set-type config variable Notice::lookup_location_types that starts out empty and would need to be populated with all the types of notice events for which this geolocation detail should be added. I found this strange since, for instance, the remote_location field of ssh events appears to be populated as long as the geolocation data is available, i.e., there's no similar whitelist there.
I've opened that issue https://github.com/zeek/zeek/issues/3674 with the Zeek team to see if I'm missing something obvious and, if not, to check if there's interest in adding some kind of wildcard functionality here, since it seems like it would be quite tedious to create/update a long list of notice types.

Verified with an artifact based on build-zeek commit dc10ee9 created from this Actions run.
Because the free MaxMind geolocation database has limited coverage, I'm using the attached repro2.pcap.gz test data because it's known to be a "hit" in that DB. After processing the pcap with that Zeek artifact, we can see a notice event now includes this detail under the nested remote_location record.
$ cat repro2.pcap | ./zeekrunner -

$ zq -Z '*SSL*' notice.log
{
    _path: "notice",
    ts: 2015-03-11T09:38:43.633846Z,
    uid: "CI8moi3p7fcgT0cd6h",
    id: {
        orig_h: <IP_ADDRESS>,
        orig_p: 48543 (port=uint16),
        resp_h: <IP_ADDRESS>,
        resp_p: 443 (port)
    },
    fuid: "Fw3yYj47FjADHwdzhj",
    file_mime_type: null (string),
    file_desc: null (string),
    proto: "tcp" (=zenum),
    note: "SSL::Invalid_Server_Cert" (zenum),
    msg: "SSL certificate validation failed with (unable to get local issuer certificate)",
    sub: "CN=www.paypalobjects.com,OU=CDN Support,O=PayPal\\, Inc.,L=San Jose,ST=California,C=US",
    src: <IP_ADDRESS>,
    dst: <IP_ADDRESS>,
    p: 443 (port),
    n: null (uint64),
    peer_descr: null (string),
    actions: |[
        "Notice::ACTION_LOG" (zenum),
        "Notice::ACTION_ADD_GEODATA" (zenum)
    ]|,
    email_dest: |[]| (|[string]|),
    suppress_for: 1h,
    remote_location: {
        country_code: "SE",
        region: "AB",
        city: "Liljeholmen",
        latitude: 59.3199,
        longitude: 18.0123
    }
}

As noted above, I did use this opportunity to audit the other Zeek logs and see if others could also include geolocation information. The only other I found was ssh, and that was already intact and didn't need any change to enable it. Using this same test data we once again see a nested remote_location record.
$ zq -Z 'remote_location.country_code != null | head 1' ssh.log
{
    _path: "ssh",
    ts: 2015-04-11T19:04:38.713425Z,
    uid: "CFWNuY3hanzDVfLUz5",
    id: {
        orig_h: <IP_ADDRESS>,
        orig_p: 2780 (port=uint16),
        resp_h: <IP_ADDRESS>,
        resp_p: 22 (port)
    },
    version: 2 (uint64),
    auth_success: false,
    auth_attempts: 4 (uint64),
    direction: "INBOUND" (=zenum),
    client: "SSH-2.0-libssh2_1.4.3",
    server: "SSH-2.0-OpenSSH_6.4",
    cipher_alg: "aes128-ctr",
    mac_alg: "hmac-sha1",
    compression_alg: "none",
    kex_alg: "diffie-hellman-group14-sha1",
    host_key_alg: "ssh-rsa",
    host_key: "24:ca:ee:e1:84:b3:0f:1a:17:86:c0:72:0a:8c:61:f6",
    remote_location: {
        country_code: "CN",
        region: null (string),
        city: null (string),
        latitude: 34.7732,
        longitude: 113.722
    },
    hasshVersion: "1.1",
    hassh: "92674389fa1e47a27ddd8d9b63ecd42b",
    hasshServer: "cca34b641961a75a15b91d1f1a13a3fb",
    cshka: "ssh-rsa,ssh-dss",
    hasshAlgorithms: "diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1;aes128-ctr,aes192-ctr,aes256-ctr,aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-cbc,aes128-cbc,blowfish-cbc,arcfour128,arcfour,cast128-cbc,3des-cbc;hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-ripemd160@openssh.com;none",
    sshka: "ssh-rsa,ecdsa-sha2-nistp256",
    hasshServerAlgorithms: "ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1;aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se;hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160<EMAIL_ADDRESS>}


Fix PyTorchObjectDetector Missing Gradients Bug

Description
When a non-leaf tensor is moved to another device, the gradient retention property is lost and needs to be manually set again. This PR adds this minor change
Fixes #2248
Type of change
Please check all relevant options.

[ ] Improvement (non-breaking)
[x] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.

[x] Tests for PyTorchObjectDetector are unchanged
[x] Tests for PyTorchFasterRCNN are unchanged

Test Configuration:

OS
Python version
ART version or commit number
TensorFlow / Keras / PyTorch / MXNet version

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Codecov Report

Merging #2249 (bb50392) into dev_1.15.1 (52c240a) will decrease coverage by 65.27%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@               Coverage Diff               @@
##           dev_1.15.1    #2249       +/-   ##
===============================================
- Coverage       85.62%   20.36%   -65.27%
===============================================
  Files             308      308
  Lines           27470    27472        +2
  Branches         5046     4631      -415
===============================================
- Hits            23522     5594    -17928
- Misses           2668    21827    +19159
+ Partials         1280       51     -1229

Files Changed
Coverage Δ

...mators/object_detection/pytorch_object_detector.py
17.61% <0.00%> (-67.94%)
:arrow_down:

... and 250 files with indirect coverage changes

Hi @f4str Thank you for your pull request. In #2238 we made the same change also in method PyTorchObjectDetector._preprocess_and_convert_inputs. Is the same change also needed in PyTorchYolo._preprocess_and_convert_inputs?

Hi @beat-buesser this is a separate bug-fix independent from #2238 that affects both the PyTorchObjectDetector and PyTorchYolo. The previous change addressed a different bug that only occured for the PyTorchObjectDetector.


[stable/filebeat] The chart deployment fails for output.elasticsearch

Describe the bug
A clear and concise description of what the bug is.
The daemonset pods for stable/filebeat chart cannot start and fail with Error -
Exiting: more than one namespace configured accessing 'output' (source:'filebeat.yml')
I have configured 2 types of inputs

Kubernetes Container logs
kubernetes Audit logs
Version of Helm and Kubernetes:

helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}
kubectl version
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:16Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
stable/filebeat
What happened:
The daemonset pods for stable/filebeat chart cannot start and fail with Error -
Exiting: more than one namespace configured accessing 'output' (source:'filebeat.yml')
What you expected to happen:
The filbeat daemonset pods to start normally.
How to reproduce it (as minimally and precisely as possible):
Use the below values file -
image:
repository: "docker.elastic.co/beats/filebeat"
tag: "7.3.2"
pullPolicy: IfNotPresent
config:
filebeat.config:
modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
filebeat.inputs:

type: container
paths:

/var/log/containers/*.log
processors:
add_kubernetes_metadata:
in_cluster: true
host: ${NODE_NAME}
matchers:

logs_path:
logs_path: "/var/log/containers/"

add_fields:
fields:
cluster-log: playground-kube

type: container
paths:

/var/log/apiserver/*.log
processors:
add_kubernetes_metadata:
in_cluster: true
host: ${NODE_NAME}
matchers:

logs_path:
logs_path: "/var/log/apiserver/"

add_fields:
fields:
cluster-log: playground-audit

processors:
- add_cloud_metadata:
cloud.id: CaaS:********0xLmF3cy5jbG91ZC5lcy5pbyRlMGYwZTVkMjc1NWE0YTExODcyYmQ5YjFlYzk1ZmEzNSQ1ZGNhNjgxZDcxNjI0ZDA4OGE4M2I1ODg3NzM0MDE4Yw==
cloud.auth: elastic:******pc9Nd2Ow66EHHsvJk9
output.elasticsearch:
hosts: ['https://e0f0e5d2755a4a11872bd9b1ec95fa35.eu-central-1.aws.cloud.es.io:9243']
username: elastic
password: *****pc9Nd2Ow66EHHsvJk9
index: "%{[fields.cluster-log]}-%{[agent.version]}-%{+yyyy.MM.dd}"
setup.template.enabled: false
setup.template.overwrite: true
setup.template.name: "playground"
setup.template.pattern: "playground-*"
setup.template.fields: "fields.yml"
setup.template.settings:
index.number_of_shards: 1
index.number_of_replicas: 1
setup.ilm.enabled: false
setup.ilm.rollover_alias: "playground"
setup.ilm.policy_name: "playground"
setup.ilm.check_exists: false
setup.ilm.overwrite: true
data:
hostPath: /var/lib/filebeat
extraVars:

name: ELASTICSEARCH_HOST
value: https://e0f0e5d2755a4a11872bd9b1ec95fa35.eu-central-1.aws.cloud.es.io
name: ELASTICSEARCH_PORT
value: "9243"
name: ELASTICSEARCH_USERNAME
value: elastic
name: ELASTICSEARCH_PASSWORD
value: *****c9Nd2Ow66EHHsvJk9
name: ELASTIC_CLOUD_ID
value: CaaS:******0xLmF3cy5jbG91ZC5lcy5pbyRlMGYwZTVkMjc1NWE0YTExODcyYmQ5YjFlYzk1ZmEzNSQ1ZGNhNjgxZDcxNjI0ZDA4OGE4M2I1ODg3NzM0MDE4Yw==
name: ELASTIC_CLOUD_AUTH
value: "elastic:******9Nd2Ow66EHHsvJk9"
name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName

resources:
requests:
cpu: "100m"
memory: "200Mi"
limits:
cpu: "1000m"
memory: "400Mi"
rbac:
create: true
serviceAccount:
create: true
podSecurityPolicy:
enabled: true
annotations:
seccomp.security.alpha.kubernetes.io/allowedProfileNames: '*'
seccomp.security.alpha.kubernetes.io/defaultProfileName: 'docker/default'
privileged: false
monitoring:
enabled: true
serviceMonitor:
enabled: true
namespace: monitoring
interval: 60s
telemetryPath: /metrics
image:
repository: trustpilot/beat-exporter
tag: 0.1.1
pullPolicy: IfNotPresent
resources:
limits:
cpu: 100m
memory: 200Mi
requests:
cpu: 100m
memory: 100Mi
exporterPort: 9479
targetPort: 9479
Anything else we need to know:
The link for configuring the outputs for this chart leads to documentation link for configuring Outputs, however the similar configuration does not work.

I am able to circumvent the problem by including below lines in the config part of the values file.
output.file:
enabled: false
This needs to be documented in the README.md of the stable/filebeat helm chart.
However now I am stuck into another problem which is that of using default https port 443 t connect to Elastic Cloud.
However the cloud URL which it should try to connect is -
https://e0f0e5d2755a4a11872bd9b1ec95fa35.eu-central-1.aws.cloud.es.io:9243
The non-standard port listening on ES endpoint is 9243.
The error stack which I get is as below -
2019-10-04T07:16:15.426Z        ERROR   pipeline/output.go:100  Failed to connect to backoff(elasticsearch(https://e0f0e5d2755a4a11872bd9b1ec95fa35.eu-central-1.aws.cloud.es.io:443)): 401 Unauthorized: {"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Bearer realm="security"","ApiKey","Basic realm="security" charset="UTF-8""]}}],"type":"security_exception","reason":"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Bearer realm="security"","ApiKey","Basic realm="security" charset="UTF-8""]}},"status":401}
2019-10-04T07:16:15.426Z        INFO    pipeline/output.go:93   Attempting to reconnect to backoff(elasticsearch(https://e0f0e5d2755a4a11872bd9b1ec95fa35.eu-central-1.aws.cloud.es.io:443)) with 1 reconnect attempt(s)
2019-10-04T07:16:18.589Z        ERROR   pipeline/output.go:100  Failed to connect to backoff(elasticsearch(https://e0f0e5d2755a4a11872bd9b1ec95fa35.eu-central-1.aws.cloud.es.io:443)): 401 Unauthorized: {"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Bearer realm="security"","ApiKey","Basic realm="security" charset="UTF-8""]}}],"type":"security_exception","reason":"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Bearer realm="security"","ApiKey","Basic realm="security" charset="UTF-8""]}},"status":401}
I have used the cloud.id and cloud.auth output parameters.
Can you please help to override the default port using the values file ?


delayed scaling: delete Float8LinearMixin

Stack from ghstack (oldest at bottom):

#273
#272
-> #271

Summary:
The mixin was originally used to share code with Float8 versions of
RowParallelLinear and ColParallelLinear.  Since we moved those to
DTensor, the mixin is not needed anymore.  Removing it to
simplify the code in preparation of upcoming delayed scaling
improvements.
In addition, making the from_float conversion use meta device
to speed it up.
Test Plan:
pytest test/test_base.py -s -x
pytest test/test_compile.py -s -x

Reviewers:
Subscribers:
Tasks:
Tags:
Differential Revision: D58396872

@vkuzo has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.

@vkuzo has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.

recreated in https://github.com/pytorch-labs/float8_experimental/pull/276 to get around ghstack weirdness


Add more C++ file extensions for syntax highlighting

%.c++$ needs to be escaped as %.c%+%+$, otherwise looks good!

%.c++$ needs to be escaped as %.c%+%+$, otherwise looks good!

Fixed!

whoops -- I wasn't paying attention unfortunately and thought this was a pull request for a different file. The language_c file intentionally only operates on non-c++ files. I'd be happy to merge the pull request if made for the language_cpp file on the plugins repository! Sorry about that

On Sun, May 31, 2020 at 9:26 AM Mihael Dimoski<EMAIL_ADDRESS>wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/rxi/lite/pull/126
Commit Summary
Add more C++ file extensions for syntax highlighting
What File Changes
M data/plugins/language_c.lua (2)
Patch Links:
https://github.com/rxi/lite/pull/126.patch
https://github.com/rxi/lite/pull/126.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


lxd/instance/lxc: Fix swappiness calculation

Closes #9017
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

I've posted the details in the other PR but basically the logic was meant to add some weight when the priority is lowered (increase swapiness) but keeping the max value at the system default of 60 to avoid getting the container above all other processes.
At some point (possibly the cgroup rework?) the logic got tweaked and we ended up with the current behavior. This both fixes the calculation to work the expected way AND also properly handles unsetting the key.

@tomponline updated

@stgraber thanks.
Why do we only allow setting the swap priority between 0 and 10 (mapping to swappiness 70 and 60) rather than a higher range (0 .. 100)?

@tomponline no real reason, we could expose more of the swapiness range, though in practice the real use cases we've seen are:

Don't have the instance swap (limits.memory.swap=false)
I don't care about those containers (lower limits.memory.swap.priority)
Normal containers (standard system swapiness)

The lack of that knob in cgroup2 also means that whatever we add at this point may be lost until an alternative is implemented over there. I'm also not the biggest fan of that particular option these days as unfortunately reducing the swappiness can backfire, basically putting more memory pressure on the container which then causes the kernel to evacuate the VFS cache.
In the worst example of that, we've had a few containers doing NorthSec that ended up trading around 5MB of additional memory (or swap) usage for 1.5GB/s of constant I/O re-fetching the same 5MB chunk over and over again...

Testsuite passed

Testsuite passed


Document AnnData portal downloads

I'm filing this as a placeholder right now for updating the docs to include the AnnData that will available for download. We are planning on discussing this in our next meeting, but for now some places that will need to get changed:

Downloads section
SCE contents (new sample metadata)
AnnData contents (?)
FAQ working with python

After we discuss what we would like to update, we should break this out into multiple issues.

I broke out everything we will need to do to update the docs into separate issues. Going to go ahead and close this in favor of those new issues.