Update kafka, kafka-clients to 2.7.0

Updates

org.apache.kafka:kafka
org.apache.kafka:kafka-clients

from 2.4.1 to 2.7.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

labels: library-update, semver-minor

Superseded by #650.


how should I send response multiple time.

as res.send() or res.json() close the connection
but I have to send the data in small parts in multiple times.
I am using two functions connected by next() middleware function and I have to send the response in both the functions.
How should I do that?

I am using two functions connected by next() middleware function and I have to send the response in both the functions.
Can you please add the code here? I am finding it difficult to understand.


make-initrd: store all files with root as owner

This was initially done as a fix to a certain kernel which wouldn't boot the other way. Later it was discovered that the kernel had fs.protected_hardlinks and fs.protected_symlinks enabled by default (which was reverted), but this fix looks like generally the Right Thing to do (and shouldn't harm).

Any comments on this? In theory this should be absolutely harmless, but I don't feel confident enough and don't want to break people's initrds ~_^.

Sounds good from the bitwise-reproducibility-point-of-view too, because I've noticed you get different results based on the UID of the build user that executed it.

Yeah, this is a nice feature, too. I'm going to merge this in several days if noone objects -- I had this patch applied for a long time without any problems.


--counter does not seem to be working

Description
I built my app with the --counter option, and the titles for my site have (#) Site Name - Page Title.  They are updated when new notifications come in from a websocket via AJAX with code like this:
document.title = document.title.replace(/^\(\d+\)/, "(" + unread_count + ")");

If I am missing something, or need to do something in a different fashion, please let me know, as I don't seem to be able to find any documentation specifying.
Steps to Reproduce Issue
Build app using
nativefier --name "App Title" --platform osx --icon /path/to/my/logo.png --counter --fast-quit --maximize --disable-context-menu --disable-dev-tools "http://my.site.com"

Specifications

Version of Nativefier (run $ nativefier --version): v7.0.1
Version of Node.js (run $ node --version): v7.2.0
OS: MacOS Sierra
Architecture <ARCH>
Stack trace from the error message (if any) - N/A

Actually, it does create the badges if the app does not have focus, but when it gets focus it clears them.  This is directly opposed to the documentation: "Use a counter that persists even with window focus for the application badge...".
Also, although it is catching JS title updates, it seems to be using the old title, rather than the new one (i.e. if the title changes from (2) to (3), the badge shows 2).

@jasonivers https://github.com/jiahaog/nativefier/pull/256 was recently release as part of Nativefier 7.1.0, could you try it and see if --counter works better now? Thanks :)

Will try first thing on Monday.
On Fri, Apr 7, 2017, 5:53 PM Ronan Jouchet<EMAIL_ADDRESS>wrote:

@jasonivers https://github.com/jasonivers #256
https://github.com/jiahaog/nativefier/pull/256 was recently release as
part of Nativefier 7.1.0, could you try it and see if --counter works
better now? Thanks :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jiahaog/nativefier/issues/299#issuecomment-292683274,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARnuXznuVFu5MA3XhLH8caqzkpg15w_ks5rttp2gaJpZM4LHXM-
.

That does seem to have fixed it.  Thank you.  It was keeping me from releasing a desktop app with nativefier, but now I can move ahead.


Remove Traffic signs summary AB test

The AB test for the summary on Traffic signs has ended. This undoes https://github.com/alphagov/fastly-configure/pull/44

 Remove Transport A/B test


Handle empty capture rules

create an extension from https://raw.githubusercontent.com/textmate/markdown.tmbundle/master/Syntaxes/Markdown.tmLanguage
Run the extension
create a README.md file with below contents
open it

Contents:
# README
## This is the README for your extension "test-ts"
You can author your README using Visual Studio Code.  Here are some useful editor keyboard shortcuts:

* Split the editor (`Cmd+\` on OSX or `Ctrl+\` on Windows and Linux)
* Toggle preview (`Shift+CMD+V` on OSX or `Shift+Ctrl+V` on Windows and Linux)
* Press `Ctrl+Space` (Windows, Linux) or `Cmd+Space` (OSX) to see a list of Markdown snippets

### For more information
* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)

**Enjoy!**

//Users/bpasero/Development/Microsoft/monaco/out/vs/workbench/electron-browser/shell.js:240 Cannot read property 'split' of null: TypeError: Cannot read property 'split' of null
at DecodeMap.getTokenIds (file:////Users/bpasero/Development/Microsoft/monaco/out/vs/editor/node/textMate/TMSyntax.js:127:34)
at decodeTextMateToken

The tmgrammar has the following empty capture on line 1078:
				<key>raw</key>
				<dict>
					<key>captures</key>
					<dict>

						<key>2</key>
						<dict/>

the textmate engine could ignore such rules.


Link issue in presence of Intel MKL

I'm getting the following error when linking with DLib:
/usr/local/include/dlib/matrix/lapack/gesvd.h:38: undefined reference to `dgesvd_'

Here's cmake configuration output:
user@user-VirtualBox:~/Downloads/dlib-19.4/_build$ cmake ..
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- C++11 activated.
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so
-- Looking for png_create_read_struct
-- Looking for png_create_read_struct - found
-- Searching for BLAS and LAPACK
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'cblas'
--   No package 'cblas' found
-- Checking for module 'lapack'
--   No package 'lapack' found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of void*
-- Check size of void* - done
-- Found Intel MKL BLAS/LAPACK library
CUDA_TOOLKIT_ROOT_DIR not found or specified
-- Could NOT find CUDA (missing:  CUDA_TOOLKIT_ROOT_DIR CUDA_NVCC_EXECUTABLE CUDA_INCLUDE_DIRS CUDA_CUDART_LIBRARY) (Required is at least version "7.5")
-- *** cuDNN V5.0 OR GREATER NOT FOUND.  DLIB WILL NOT USE CUDA. ***
-- *** If you have cuDNN then set CMAKE_PREFIX_PATH to include cuDNN's folder.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/user/Downloads/dlib-19.4/_build

Note: I haven't explicitly set DLIB_USE_LAPACK

What exactly does one have to type to reproduce your error?

Sorry, as it turned out it's not an issue with DLib. I just don't use CMake to build my projects and the need to link some MKL libraries was totally unexpected for me (especially since the function's name does not indicate its origin).


refactor: keep source location information in compiler state

There are few things I am not sure of, like why tokenize() was sometimes called with a line number zero or how to handle the difference between two variants of add_code()

Wonderful refactor! Thank you very, very much! Sorry for taking so long, I've been super busy.


[GOBBLIN-546] Use appropriate Lists package

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-546

Description

[x] Here are some details about my PR, including screenshots (if applicable):
Use correct package name.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@htran1  Please review


Factor out shared 'Operation' class and helpers.

Intended to replace the versions currently in .bigtable.instance and bigtable.cluster.  Differences in approach from those:

No parsing / reconstruction of operation's name:  the new class just holds the name as retrieved.

Add a from_pb classmethod factory, which attempts to parse out the metadata Any, IFF the type_url on the Any is set, and there is a class registered for it.

Drops the complicated __eq__/__ne__ as YAGNI:  if needed, reimplement using just the name attr.

Use new gcloud.operations.Operation for long-running ops.

LGTM when Travis goes green

Consider squashing some commits

I'd rather not squash and have to run through Travis again today.

Totally

:+1: LGTM after latest commit as well.


docker-machine ls shows client version 1.15 is too old talking to a Windows Docker engine

I have a manually configured docker-machine config.json that connects to a Windows Docker engine 1.13.0-rc4. But docker-machine ls complains about a too old client API version:
$ docker-machine ls
NAME      ACTIVE   DRIVER         STATE     URL                          SWARM   DOCKER        ERRORS
dev       -        virtualbox     Running   tcp://<IP_ADDRESS>:2376            v1.12.5
linux     -        vmwarefusion   Running   tcp://<IP_ADDRESS>:2376           v1.13.0-rc3
windows   *        generic        Running   tcp://<IP_ADDRESS>:2376           Unknown       Unable to query docker version: 400 Bad Request: client version 1.15 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

Setting the environments and using it with docker cli works:
$ eval $(docker-machine env windows)

$ docker version
Client:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 06:14:34 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.13.0-rc4
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   88862e7
 Built:        Sat Dec 17 01:34:17 2016
 OS/Arch:      windows/amd64

So question is, should https://github.com/docker/machine/blob/2d0127535ed904d09b8984266d35affdd7ad3f2e/vendor/github.com/samalba/dockerclient/dockerclient.go#L20 be updated / vendored with a newer version?

You may ask where I got a Windows Docker machine. I just finished my workaround to spin up a Windows VM that creates the docker-machine config.json. docker-machine itself is used only to switch environments.

You may ask where I got a Windows Docker machine. I just finished my workaround to spin up a Windows VM that creates the docker-machine config.json. docker-machine itself is used only to switch environments.

Ha, cool.
Yes, the Docker client should absolutely be updated.

Hm, again and again I stumble over this problem. But changing the Docker client is a tip of the iceberg as these are no longer maintained.
So my current workaround is using vim: sudo vi /usr/local/bin/docker-machine and replace v1.15 with v1.24.

It works for me.
Sending a PR with only that change probably wouldn't be accepted. But changing the whole Docker cli is too much work for me.

Hope this issue fixed soon!

I am guessing it would suffice to edit this line and rebuild?


Windows support

This refactors to allow building a Windows binary as well as adds nerdctl run  support. This a draft to figure out/show the amount of work.   This should be broken down into smaller PRs that can be reviewed easier.  See #28 for discussion

closing in favor of a more iterative approach.  I did take much of the feedback here into consideration. Thanks for the early reviews!


Add command line functionality Description

I would like to use Ultimate Vocal Remover from the command line instead of the GUI. This would make it easier to process multiple files and automate workflows. Please consider adding command line functionality to this tool. Thank you for your great work!

Duplicate of #359


api/permissions: Allow user to GET their own permissions

Required for #1480
Code Changes

This change updates the GET USER_PERMISSIONS endpoint to only require the USER_PERMISSION_READ scope when requesting the permissions for another user. If the User Id of the client credentials matches the User Id of the request, the scope check is skipped.
Cleaned up tests for the endpoint and added case for current-user case

The test functions were inconsistent about creating the user and permissions object that needed to be queried.
Some were using a url fixture that was an invalid string - it contained {user_id} instead of actually passing the id.

Steps to Confirm

[ ] GET /api/v1/user/{user_id}/permission when authenticated as the root user should return the users's permissions.
[ ] When authenticated as a user with limited permissions, this should only succeed with the current user Id and raise a 403 for any other.

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
Issue #1480 highlights that we never re-validate the auth token saved in localStorage. Requests that require auth return 403 if the token gets invalidated on the backend, but this isn't enough information for the frontend to tell whether the token was invalid or if it just doesn't have permission for that one scope.
The User Permission endpoint seems like a robust solution: if a user can't get their own permissions, then they must not have a valid token. We could also use this in the future to toggle features that only make sense if the user has, for example, PRIVACY_REQUEST_DELETE permissions.

Alternative solutions/implementations

Log out on any endpoint 403 (or 401)

I thought through this option, but it just creates more problems. It's perfectly reasonable for a user to have access to some endpoints block without kicking them out of the app.
Also, some endpoints authenticate accounts other than Fides itself. For example, AWS scanning returns 403 if the credentials failed. So a global handler wouldn't work, resulting in a piecemeal solution.

Use the Login endpoint - Nope, that's a POST with credentials.
Use the GET USER_DETAIL endpoint

This was a strong contender, and we might want to allow the user to query themselves anyway.
However, for auth checking, the user's permissions seem like the most important information.
Also, the USER_DETAIL endpoint is implemented in fideslib, so it's a bit more annoying to change.

For some reason I'm getting a 500 as a response with no traceback in the server logs. Were you able to call the route from postman?

Yeah, I did before I wrote the tests. Are you including a valid auth header? I noticed that it 500's instead of nicely handling a jank token, even before this change.

@ssangervasi I think that's it. I tried copying the token from the browser. Manually creating a token in postman worked.

I notice the pylint lint failing after I approved it. It should be good to merge once that is fixed.

@ssangervasi It looks like a fix was just merged to handle malformed tokens properly #1523