Getting an undefined: method 'space error

Has anything changed for looker_deployer for api 4.0? I am getting this error when I try to export my dashboards from the dev environment:
options: {"debug"=>true, "host"=>"revegydev.looker.com", "port"=>"19999", "ssl"=>true, "verify_ssl"=>false, "timeout"=>60, Removed Client ID and Secret
"dir"=>"content41122/Shared"}
API 3.1 available? true
connecting to ["api_endpoint=>https://revegydev.looker.com:19999/api/4.0", "connection_options=>{:ssl=>{:verify=>false}, :request=>{:timeout=>60}}", "user_agent=>Gazer 0.2.43", "client_id=>Remove", "client_secret=>*********"]
check for connectivity: true
verify authentication: true
logout
Traceback (most recent call last):
18: from /usr/local/bin/gzr:23:in <main>'         17: from /usr/local/bin/gzr:23:in load'
16: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/exe/gzr:36:in <top (required)>'         15: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start'
14: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch'         13: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command'
12: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run'         11: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:238:in block in subcommand'
10: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:115:in invoke'          9: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch'
8: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command'          7: from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run'
6: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/lib/gzr/commands/space.rb:80:in export'          5: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/lib/gzr/commands/space/export.rb:49:in execute'
4: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/lib/gzr/modules/session.rb:207:in with_session'          3: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/lib/gzr/commands/space/export.rb:81:in block in execute'
2: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/lib/gzr/commands/space/export.rb:87:in process_space'          1: from /var/lib/gems/2.5.0/gems/gazer-0.2.43/lib/gzr/modules/space.rb:65:in query_space'
/var/lib/gems/2.5.0/gems/looker-sdk-0.0.7/lib/looker-sdk/client/dynamic.rb:105:in method_missing': undefined method space' for #LookerSDK::Client:0x000055fccc55f338 (NoMethodError)
Here is the line that I am running: ldeploy content export --env dev --folders 212 --local-target ./content41122/ --debug

I need to push client's dashboards to production. Do you know of work around for the above issue that I am having?

@bobenauf I think this is due to your gazer gem being out of date.
Please try updating the gazer gem: gem install gazer
And uninstall the old version: gem uninstall gazer --version 0.2.43
After updating, you can verify the latest version with gem list and you should see gazer (0.2.54)

Thanks Michael, I will try that

@michaelcramer We ran into this same issue using the pre-built Dockerhub image jcpistell/looker_deployer. Unfortunately we don't have access to that to update the gem, and that image hasn't been updated in over two years. How can we get an updated image built at Dockerhub?

@michaelcramer We ran into this same issue using the pre-built Dockerhub image jcpistell/looker_deployer (as described in the README). Unfortunately we don't have access to that to update the gem, and that image hasn't been updated in over two years. How can we get an updated image built at Dockerhub?
/var/lib/gems/2.5.0/gems/looker-sdk-0.0.7/lib/looker-sdk/client/dynamic.rb:105:in `method_missing': undefined method `space' for #<LookerSDK::Client:0x000055815147d1a0> (NoMethodError)
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/lib/gzr/modules/space.rb:65:in `query_space'
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/lib/gzr/commands/space/export.rb:87:in `process_space'
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/lib/gzr/commands/space/export.rb:81:in `block in execute'
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/lib/gzr/modules/session.rb:207:in `with_session'
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/lib/gzr/commands/space/export.rb:49:in `execute'
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/lib/gzr/commands/space.rb:80:in `export'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:115:in `invoke'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:238:in `block in subcommand'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
	from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
	from /var/lib/gems/2.5.0/gems/gazer-0.2.41/exe/gzr:36:in `<top (required)>'
	from /usr/local/bin/gzr:23:in `load'
	from /usr/local/bin/gzr:23:in `<main>'

You just need to add to the Dockerfile the line gem install gazer
FROM jcpistell/looker_deployer:latest
RUN gem install gazer
COPY looker.ini /

Hello @jsnod,
Did you have a chance to try adding the RUN gem install gazer line to a DOCKERFILE based on jcpistell/looker_deployer:latest as suggested by maurk851 above?
If you are still having an issue, please reply to this comment, otherwise it will be marked closed in 3 days.
Thanks.

Did you have a chance to try adding the RUN gem install gazer line to a DOCKERFILE based on jcpistell/looker_deployer:latest as suggested by maurk851 above?

@ddaugherty Yep, it worked, thanks! How can we get it baked into jcpistell/looker_deployer to save on build time? Any plans for an official looker-open-source/looker_deployer?

@jsnod we would suggest that you build the image locally and run it.  Not on the roadmap atm for an official Deployer, but appreciate the upvote!


GPL-781 BUG - Error ROWS_PER_QUERY on crawler UAT

Reduce batch size
Assume this is necessary because the fields recently added to the lighthouse_sample table means the MLWH insert statement is larger for each row.

Test run has now completed in UAT - no critical errors

Easiest change ever! :P


the progressbar can't display in pycharm

When I use terminal to run the code, the progress bar is ok
while using pycharm, the progressbar can't show in result.

Hm, maybe PyCharm doesn't show the standard error output? By default, pyprind's objects are using stream=2 to output results to stderr (users suggested this so they can pip the "real" output by their program to other files and such.
If you set stream=1 (which is stdout), does it work?
bar = pyprind.ProgBar(n, stream=1)
for i in range(n):
    time.sleep(timesleep) # your computation here
    bar.update()

Hi
after setting stream to 1,It still can't work
Sincerely
Liang
On 09/06/2016 06:58 PM, Sebastian Raschka wrote:

Hm, maybe PyCharm doesn't show the standard error output? By default,
pyprind's objects are using |stream=2| to output results to stderr
(users suggested this so they can pip the "real" output by their
program to other files and such.
If you set |stream=1| (which is stdout), does it work?
bar=  pyprind.ProgBar(n,stream=1)
for  iin  range(n):
time.sleep(timesleep)# your computation here
bar.update()
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rasbt/pyprind/issues/35#issuecomment-245122216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGDTa_Skhv8IEhR3yHVWQN0TtIoxtqdks5qnfAugaJpZM4J2Xcl.

Ah, you are right, for some reason, it doesn't work with stream=1 here. However, I just gave it a try setting the stream manually and it works like a charm(m) ;)
import pyprind
import sys
import time

n = 100
bar = pyprind.ProgBar(n), stream=sys.stdout)
for i in range(n):
    time.sleep(0.1)
    bar.update()

Let me know if this works for you as well, and I'd be happy to add a note to the README/docs if this solves the problem.

it works for me， thanks a lot.
You should add an example using while loop.
tqdm doesn't support while loop

glad to heart that this solution works and adding a while-loop example is a good idea, thanks for the suggestion (just added one). Btw. do you know if tqdm work with PyCharm out of the box? Never tried this package, looks like an interesting alternative though

tqdm can display in pycharm.
but it didn't support tqdm.
On 09/07/2016 01:25 PM, Sebastian Raschka wrote:

glad to heart that this solution works and adding a while-loop example
is a good idea, thanks for the suggestion (just added one). Btw. do
you know if tqdm work with PyCharm out of the box? Never tried this
package, looks like an interesting alternative though
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rasbt/pyprind/issues/35#issuecomment-245355322,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGDTfIRri5Zx14RHf3Y0iIeA66ESnQNks5qnvOPgaJpZM4J2Xcl.

Ah, I just remembered that I added an sys.stdout.isatty() check for setting the stream, which evaluates to False in PyCharm. Just made a little modification and it should work with PyCharm out of the box. If you like, you can upgrade to 2.9.9 via
pip install pyprind --upgrade

it's not working for pyprind 2.11.0 and pycharm 2016.3.3.
i'm doing this https://github.com/rasbt/pyprind/issues/35#issuecomment-245158319

Hi,
hm that's weird, just tested in on PyCharm with and without sys.stdout as stream and it seems to work fine in both cases. Can you maybe check via print(pyprind.__version__) that this is indeed pyprind 2.11? Another explanation would be that there might have been some weirdness in PyCharm 2016 regarding standard outputs? ( was running this on the latest version, 2017.1.2)

The behavior depends on PyCharm's option "Show command line afterwards". If it is on, PyCharm invokes IPython console, you will see each update on the separate line. If it is off, the behavior as expected.

Thanks for the note. So it seems that it's not a bug after all !? :)

It's PyCharm's issue


Subsections in nested elements are not recognized

For some reason, only subsections in the same parent element are recognised by scrollnav. This is obviously not ideal behavior, as there are various reasons one might be nesting their subsections in a different element (e.g. lists).
Config:
scrollnav.init( content, {
	sections: 'h2',
	subSections: 'h3',
	insertLocation: 'prepend',
} );

Html

Section Title

Step 1

Content goes here

Suggestions on how to fix?

I use a nextUntil function to search for the subsections that only looks at elems on the same level. I did this to try and speed up the dom query but I'll have to rethink it. Thanks for opening the bug.

I did come across the same issue.

I did come across the same issue.


Remove previous Authorization header

I have the following use-case:
User gives authenticated url. Something like this: http://user:pass@host:port/path
If request is submitted with such an Url with reqwest, it will automatically form the "Authorization" header, assuming it's basic authentication.
The idea is to be able to "automatically detect" if it is basic auth or digest auth.
In order to implement this, send_with_digest_auth() could remove any previous "Authorization" headers set. But I'm not sure if this is possible. Maybe reqwest adds the header after send_with_digest_auth() acts.
Is this even something that diqwest should handle?
Maybe this issue can be brought to reqwest itself?

Hey @rcastill,
I really have to look into my notification setup 🤦🏾
If you are interested to handle it I encourage you to open a PR and then let's discuss.
✌🏾

Closing this as to my feeling it does not fall into the responsibility of this crate.


Exercise Descriptions and Tags

Add descriptions to Exercise table
Add exercise descriptions to Index and Show views
Add tags table and exercise_tags join table
Add tags to exercise Index and Show views
Model and Feature test all of the above
@NZenitram @annadolan @bermannoah

@epintozzi looks awesome! Great job! 💯


some issues about pc2cad

Hi,@ChrisWu1997 ：
Your work is excellent and I am very interested in your paper on point cloud reconstruction engineering with Pointnet++. So there are some training details I would like to ask for:

I got the same loss curve as you uploaded in the previous comment, although I found that the loss drops below 0.07, but it didn't work out so well. In particular, the difference between the decoded CAD model and the Ground Truth is so great that it can be observed with eyes.
So I'd like to ask for more details about the training:
I'm directly using the Z obtained from the provided encoder in the pre-trained model;
The point cloud file comes from a series of conversions, which are: json->step->stl->ply, because otherwise, using the cad2pc program directly would consist of close to half of the data that cannot be converted.
I didn't normalize any of this data, does it matter?

Could I ask what the purpose of pc2cad is and how to use it?


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 209 ms

Resolved: ClamAV performance has improved in a216646.


Magma A #8 Incorrect placement for tile

Current image for Magma A #8 indicates that the player should stand on the left pillar's safespot for this phase - however, this results in them getting venomed during this phase. This image should instead indicate to move to the right pillar's safespot for this phase, with the same placement as Magma A #9.

Similarly, I noticed SERP #3 isn't correct.

Original issue is really a duplicate of https://github.com/while-loop/runelite-plugins/issues/25


Callback as child processes

Swoole's process abstraction uses a callback rather than calling exec, and then provides an exec method that can be used within the callback for executing commands if that's desired within the child process. See https://openswoole.com/docs/modules/swoole-process-construct . This gives the option of executing PHP code within the child process.
Every time a child process is created within PHP you fork the entire PHP instance, extensions and all. Yet to run any type of PHP within the reactphp child you need to call the the php/php-cli command which will than create yet another php instance, this one without access to any of the original parents resources. This is both inefficient and restrictive. Keep in mind that if the intent is to purposefully restrict the spawned php environment that php/php-cli can still be called via the exec method, as can other procedures to further reduce privileges of that process (if the parent process has privileges to do so).

This would be greatly beneficial. ReactPHP's event loop can then be used as a core reactor much like how Swoole functions, but in PHP userspace (see here https://github.com/swoole/swoole-src/tree/master/src/reactor)

Their process object (https://github.com/swoole/swoole-src/blob/master/src/server/process.cc) is passed "server", which is really just needed for integrating access to the eventloop within the parent.

If you see here (https://github.com/ClosetMonkey/ReactPHPZMQ/blob/main/parallel_ratchet.php) I've done similar for creating a php parallel based thread pool for handling Ratchet websocket messages, but this is not ideal given the experimental nature of the parallel extension. This can be done fairly easily using child processes though to create a stable solution.

Hey @ClosetMonkey, thanks for bringing this up :+1:
Sounds like your suggesting that we implement some kind of fork support. This sounds like a good idea and we're always happy about suggestions or PRs! This will also mean that we'd have to add extensions to this package to make this work. In ReactPHP we try to avoid dependencies if possible. This is why our current implementation works as is. For most use cases this should work just fine but I am interested in your ideas.
If you already have some implementation for this I am happy to take a look.
You can also take a peek at some answers written by @clue in event-loop#184 for more information on this topic and what others have to say about it.
There's also the  clue/reactphp-pq project, maybe this fits into your use case.
Let me know what you think about this.

Thank you for your reply @SimonFrings . My input can be scattered at times. I didn't look deep enough to see that child_process doesn't fork. I've been away from userspace PHP for a while to be honest.
Are you familiar with PHP's start up process and lifecycle? Here's a quick read if not.
PHP starts up in two phases, module init and then request init. The majority of PHP's startup time and startup CPU overhead is within the module init phase. The request init phase can then be called multiple times which is the basic architecture of most servers - call module initialization once, then request init in a loop for each request in either threads or forked processes (minit called prefork). This allows for requests to be processed quicker, and more importantly when it comes to workers, it allows for persistent resources that survive across multiple requests such as database connection pools. This is also how php-cgi is designed to work, but typically by handling fcgi requests when in production. However, when passes a file php-cgi will usually execute the file and then fully shut down, going through the the whole php lifecycle in one go similar php-cli. However the -T arg for php-cgi causes it to execute a file T times, each time within a new request, meaning without having to fully reinitialize PHP, and without loosing persistent resources. T doesn't have a hardset max, so hypothetically it is the system's INT_MAX, which if INT_MAX executions took 1 microseconds each php-cgi would able to handle these 1us requests for slightly under 30,000 decades on a 64 bit system. 1us isn't a baseline for anything, it can just as easily run indefinitely. The -q flag is used to prevent php-cgi from spiting out HTTP headers (since it's not running in the context of a HTTP request handler).
I think the php-cgi should be of interest for ReactPHP because as a high performance IO framework ReactPHP can communicate with php-cgi as meant in production over FCGI. I don't mean in a traditional HTTP/CGI context, but as a means to create and control long running worker/child processes with less overhead and persistent, shareable resources. It's also cross-plat.
Alternatively, php-cli has an undocumented argument --repeat that is similar to php-cgi's -T arg. After a few days of searching I found that it is used heavily in php's test suite (such as make test after compiling PHP). However it didn't surface until PHP7. With the lack of documentation there's no telling if/how it may change.
This all leads me to a few questions, but one is regarding your statement about dependencies. Doe this include PHP userland dependencies that can be resolved with composer?

One that I'm looking at is opis/closure. If both the calling instance and php-cgi (or php-cli) have the same includes, and if the parent is knows the state of the child (fork, cli instance, etc), it's conceivable to be able to pass callable's into the child.

The -T argument was added to php-cgi in PHP-5.3 in 2007 and doesn't seem to be going anywhere https://github.com/php/php-src/commit/6f7b738b712f234ec34a1e905572530bc277c8ca
The --repeat argument for php-cli was added in php-8.1.0RC1 for testing JIT and noted in the source that it might be changed https://github.com/php/php-src/commit/1b3b430f478c785c88655533518a66b88ece060a
I wrote up a quick PHP extension here to demonstrate the effect of -T and --repeat arguments. It will print a notice when major initialization and teardown procedures are completed. It also maintains a counter as a persistent resource across requests.
note that php_request_shutdown(void *dummy) here is where the entire PHP userspace is deconstructed and free'ed, not just garbage collected. This is the point where server sapis release everything created by PHP userspace when PHP is done processing a HTTP request, although the function itself is not bound to any form of HTTP context as can be seen in the php-cli.
This can still be tested without installing an extension. The fact that resources are persistent across iterations can be tested standard php streams.
Create a basic tcp server using ReactPHP
react_server_example.php
<?php

require __DIR__ . '/vendor/autoload.php';

$socket = new React\Socket\SocketServer('<IP_ADDRESS>:8080');

$socket->on('connection', function (React\Socket\ConnectionInterface $connection) {
    echo "New connection \n";

    $connection->on('data', function ($data) use ($connection) {
        echo "Got data: {$data} \n";
    });

    $connection->on('close', function () {
        echo "Connection Closed \n";
    });

    $connection->on('error', function (Exception $e) {
        echo 'error: ' . $e->getMessage();
    });

});

Then run the following example using php-cgi -T 10 pfsockopen_example.php
pfsockopen_example.php
<?php

$psock = pfsockopen("<IP_ADDRESS>", 8080, $errno, $errstr, 30);

if (!$psock) {
    echo "{$errstr} ({$errno}) \n";
} else {
    fwrite($psock, "YO!");
}

Which will result the following, demonstrating one connection across 10 individual script executions:
New connection
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Got data: YO!
Connection Closed

As far as performance goes, which can also be seen without an extension by calling a basic script, such as just echo “Hi”; 50,000 times using php-cgi -T 50000 echo.php takes 1403 milliseconds (1.40 seconds) on my machine. Calling the same 50,000 times without using -T or --repeat arguments, by calling php-cli in a loop took, much, much longer.

Nice read, I can tell you put quite some time into this topic :+1:

This all leads me to a few questions, but one is regarding your statement about dependencies. Doe this include PHP userland dependencies that can be resolved with composer?

I meant that we only want to include extensions if they're really necessary, thus avoiding to overload the whole project (not the only reason tho).


my changes

Added a link to the Python documentation for 3.7 under the "Tools" tab

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: We do not accept PRs which only add links when there are already valid reference links for the article.
Thank you and happy coding.


Proposal: Include a debounced search to the Marvel example

Given that async operations are quite common, I think it would be helpful to add a simple search functionality to the Marvel example that would debounce the input query.
How do you approach such functionality, if possible, in a reusable way?
Sorry if this would fit better in the state_notifier or hooks package. I felt like asking because of the Marvel project 😄
Congratulations on all the packages @rrousselGit !

Good idea!

The existing pagination example is very nice + the combination with freezed for the API responses.
I can't think of other common use cases at the moment.

How about a Retry on errors? As far as I can see the error would only be shown, without a way to get rid of it? Not sure how this fits into the pagination

Actually the pagination is outdated and can be simplified. Families weren't implemented at the time of writing.
I'll also include a "auto cancel HTTP requests if the request is no-longer needed by the UI" and some navigation.

Saving state to disk and recreate the state when come back later :)
I wish there was a sync way to do it :(

You could technically use File.writeSync
Do you want to though... Haha

Uhhhhhh :D
class Foo extends StateNotifier<FooState> {
   Foo(): super(Foo.fromJson(file.readAsStringSync()) ?? Foo())
}

I'm honestly considering making a wrapper around a DB, such that we'd have:
final provider = StreamProvider((ref) async* {
  final json = await ref.deserialize();
  yield Value.fromJson(json);
}, name: "ID", serialize: (value) => value.toJson());

off topic, but this sounds a bit like why I made https://github.com/hpoul/simple_json_persistence#usage-in-flutter-streambuilder which basically produces a json backed ValueStream.. only that you'd have call save to update the state, instead of calling the setter..

I updated the marvel example a bit.
I'm not done yet, but it's a pretty big simplification of how the pagination was done before

Looking good. Can't wait to see how you solve reloading the character page on error :)

Ah good idea too
So:

debounce on search (currently we have a search, just not denounced)
retry
pull to refresh
offline
cancel HTTP requests when no-longer-used
data normalization

That should keep me occupied for this weekend

I opted for a separate list for the search bar
What do you think of it?
I like it as it demonstrate having two separate states in parallel - which is done by default with Riverpod's families
The main list is obtained with:
useProvider(characters(''));

And the filtered list with:
useProvider(characters(search));

Closing for now. The current example does include a denounced search.
I will implement the remaining points in different examples.


Use single TextEncoder/-Decoder instance

Public-Facing Changes
None
Description
Instead of creating a new TextDecoder instance for every CdrReader instance, a single TextDecoder instance is used to reduce unnecessary GC cycles. The same is done for TextEncoder / CdrWriter.

A new CdrReader instance is created for every message: https://github.com/foxglove/rosmsg2-serialization/blob/main/src/MessageReader.ts#L43-L46
However, I don't think that this will make a very noticeable performance difference


brew cask install google-cloud-sdk fails

Description of issue
On a freshly installed brew installation of Google Cloud SDK fails.
If installation is interrupted at a right moment one can see that several directories end up owned as root:
⟫ ls -ld /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk
drwxr-xr-x  17 root  staff  578 Mar 21 16:02 /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk
⟫ ls -ll ~/.config/gcloud/logs/2017.03.21
total 1560
-rw-r--r--  1 tbasanov  staff   2161 Mar 21 10:52 <IP_ADDRESS>1377.log
-rw-r--r--  1 tbasanov  staff   2007 Mar 21 10:53 <IP_ADDRESS>4865.log
-rw-r--r--  1 tbasanov  staff   2011 Mar 21 10:53 <IP_ADDRESS>4962.log
-rw-r--r--  1 tbasanov  staff   2007 Mar 21 10:54 <IP_ADDRESS>5394.log
-rw-r--r--  1 root      staff  23138 Mar 21 15:41 <IP_ADDRESS>1887.log
-rw-r--r--  1 root      staff  87378 Mar 21 15:41 <IP_ADDRESS>674.log
-rw-r--r--  1 root      staff  23138 Mar 21 15:44 <IP_ADDRESS>1461.log
-rw-r--r--  1 root      staff  87378 Mar 21 15:44 <IP_ADDRESS>6464.log
-rw-r--r--  1 tbasanov  staff   2864 Mar 21 15:46 <IP_ADDRESS>0397.log
-rw-r--r--  1 tbasanov  staff   2279 Mar 21 15:46 <IP_ADDRESS>9428.log
-rw-r--r--  1 tbasanov  staff   3743 Mar 21 15:47 <IP_ADDRESS>606.log
-rw-r--r--  1 tbasanov  staff  12433 Mar 21 15:50 <IP_ADDRESS>3566.log
-rw-r--r--  1 tbasanov  staff  87378 Mar 21 15:50 <IP_ADDRESS>2586.log
-rw-r--r--  1 tbasanov  staff   3154 Mar 21 15:51 <IP_ADDRESS>5620.log
-rw-r--r--  1 tbasanov  staff  87378 Mar 21 15:51 <IP_ADDRESS>5733.log
-rw-r--r--  1 tbasanov  staff   1540 Mar 21 15:51 <IP_ADDRESS>2518.log
-rw-r--r--  1 tbasanov  staff  12433 Mar 21 15:52 <IP_ADDRESS>5801.log
-rw-r--r--  1 tbasanov  staff  87378 Mar 21 15:52 <IP_ADDRESS>721.log
-rw-r--r--  1 root      staff  23138 Mar 21 15:59 <IP_ADDRESS>341.log
-rw-r--r--  1 root      staff  87378 Mar 21 15:59 <IP_ADDRESS>0908.log
-rw-r--r--  1 root      staff  23138 Mar 21 16:03 <IP_ADDRESS>9566.log
-rw-r--r--  1 root      staff  87378 Mar 21 16:03 <IP_ADDRESS>3276.log

Output of `brew cask install google-cloud sdk --verbose`
==> Caveats
google-cloud-sdk is installed at /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk. Add your profile:

      for bash users
        source '/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.bash.inc'
        source '/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.bash.inc'

      for zsh users
        source '/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc'
        source '/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.zsh.inc'

      for fish users
        set fish_user_paths /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin
        set -x MANPATH /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/help/man /usr/local/share/man /usr/share/man /opt/x11/share/man

        Run fish_update_completions to generate completions for fish based on the man pages

==> Downloading https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz
/usr/bin/curl --remote-time --location --user-agent Homebrew/1.1.11 (Macintosh; Intel macOS 10.12.3) curl/7.51.0 --fail --silent https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz -C 0 -o /Users/tbasanov/Library/Caches/Homebrew/Cask/google-cloud-sdk--latest.tar.gz.incomplete
==> No checksum defined for Cask google-cloud-sdk, skipping verification
==> Running installer script google-cloud-sdk/install.sh
==> Welcome to the Google Cloud SDK!
==>
==>
==> Your current Cloud SDK version is: 147.0.0
==> Installing components from version: 147.0.0
==>
==> +----------------------------------------------------------------------------+
==> |                    These components will be installed.                     |
==>
==> +-----------------------------------------------------+------------+---------+
==> |                         Name                        |  Version   |   Size  |
==> +-----------------------------------------------------+------------+---------+
==> |
==> BigQuery Command Line Tool
==> |
==>     2.0.24
==>
==> |
==> < 1 MiB
==>
==> |
==>
==> |
==> BigQuery Command Line Tool (Platform Specific)
==> |
==>     2.0.24
==>
==> |
==> < 1 MiB
==>
==> |
==>
==> |
==> Cloud SDK Core Libraries (Platform Specific)
==> |
==> 2016.11.07
==>
==> |
==> < 1 MiB
==>
==> |
==>
==> |
==> Cloud Storage Command Line Tool
==> |
==>       4.22
==>  |
==> 2.8 MiB
==> |
==>
==> |
==> Cloud Storage Command Line Tool (Platform Specific)
==> |
==>       4.18
==>
==> |
==> < 1 MiB
==>
==> |
==>
==> |
==> Default set of gcloud commands
==> |
==>
==>
==> |
==>
==>
==> |
==>
==> |
==> gcloud-deps (Mac OS X, x86_64)
==> |
==> 2017.02.21
==>  |
==> 2.1 MiB
==>  |
==>
==> +-----------------------------------------------------+------------+---------+
==>
==> For the latest full release notes, please visit:
==>   https://cloud.google.com/sdk/release_notes
==>
==> #============================================================#
==> #= Creating update staging area                             =#
==> #
==> ======
==> ======
==> ======
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =#
==> #= Installing: BigQuery Command Line Tool                   =#
==> #
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> ==
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> #
==> #= Installing: BigQuery Command Line Tool (Platform Spec... =#
==> #
==> ==============================
==> ===============
==> ===============
==> #
==> #= Installing: Cloud SDK Core Libraries (Platform Specific) =#
==> #
==> ==============================
==> ==========
==> =========
==> ===========
==> #
==> #= Installing: Cloud Storage Command Line Tool              =#
==> #
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> #
==> #= Installing: Cloud Storage Command Line Tool (Platform... =#
==> #
==> ==============================
==> ===============
==> ===============
==> #
==> #= Installing: Default set of gcloud commands               =#
==> #
==> ============================================================#
==> #= Installing: gcloud-deps (Mac OS X, x86_64)               =#
==> #
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> =
==> #
==> #= Creating backup and activating new installation          =#
==> #
==> ==============================
==> ==============================
==> #
==>
==> Performing post processing steps...
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> .
==> done.
==>
==> Update done!
==>
==>
==> This will install all the core command line tools necessary for working with
==> the Google Cloud Platform.
==>
==> ==> Source [/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.zsh.inc]in your profile to enable shell command completion for gcloud.
==> ==> Source [/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc] in your profile to add the Google Cloud SDK command line tools to your $PATH.
==>
==> For more information on how to get started, please visit:
==>   https://cloud.google.com/sdk/docs/quickstarts
==>
==>
==> Symlinking Binary 'bq' to '/usr/local/bin/bq'
==> Symlinking Binary 'gcloud' to '/usr/local/bin/gcloud'
==> Symlinking Binary 'git-credential-gcloud.sh' to '/usr/local/bin/git-credential-gcloud'
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/bq-nix.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/bq-nix.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/bq.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/bq.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/core-nix.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/core-nix.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/core.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/core.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gcloud-deps-darwin-x86_64.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gcloud-deps-darwin-x86_64.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gcloud-deps.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gcloud-deps.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gcloud.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gcloud.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gsutil-nix.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gsutil-nix.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gsutil.manifest: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/gsutil.snapshot.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/help_text/table.json: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/static_completion/table.py: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/.install/static_completion/table.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/.default_components: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/bootstrapping.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/bq.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/gsutil.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/install.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/prerun.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/bootstrapping/setup.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.bash.inc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.zsh.inc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/gcloud.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/api/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/api/requests.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/appengine_api_client.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/appengine_client.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/cloud_build.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/cloud_endpoints.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/deploy_app_command_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/deploy_command_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/docker_image.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/exceptions.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/ext_runtime_adapter.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/ext_runtimes/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/ext_runtimes/fingerprinting.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/ext_runtimes/loader.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/images/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/images/config.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/instances_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/logs_requestor.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/logs_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/metric_names.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/operations_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/region_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtime_builders.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/fingerprinter.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/go.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/java.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/nodejs.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/python.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/python_compat.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/runtimes/ruby.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/service_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/version_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/wrapper_util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/app/yaml_parsing.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/auth/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/auth/refresh_token.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/auth/service_account.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/auth/util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/bigtable/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/bigtable/util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/billing/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/billing/utils.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/bio/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/bio/bio.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/bio/errors.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/lib/googlecloudsdk/api_lib/cloudbuild/__init__.pyc: Operation not permitted

<...skip...>

==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/retry-decorator/retry_decorator/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/retry-decorator/retry_decorator/retry_decorator.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/retry-decorator/setup.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/.gitignore: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/.hgignore: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/.hgsigs: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/.project: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/.pydevproject: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/CHANGELOG.txt: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/create_timing_table.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/_build/.keep: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/_static/.keep: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/_templates/.keep: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/cli.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/compatibility.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/conf.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/index.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/installation.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/intro.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/licence.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/make.bat: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/Makefile: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/reference.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/upgrading.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/doc/usage.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/LICENSE: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/MANIFEST.in: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/README.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/requirements-dev-py2x.txt: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/requirements-dev-py3x.txt: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/_compat.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/_version133.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/_version200.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/asn1.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/bigfile.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/cli.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/common.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/core.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/key.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/parallel.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/pem.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/pkcs1.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/prime.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/randnum.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/transform.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/util.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/rsa/varblock.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/run_tests.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/setup.cfg: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/setup.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/__init__.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/constants.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/py2kconstants.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/py3kconstants.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_bigfile.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_common.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_compat.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_integers.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_load_save_keys.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_pem.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_pkcs1.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_strings.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_transform.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tests/test_varblock.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/rsa/tox.ini: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/.hgignore: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/.hgtags: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/CHANGES: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/CONTRIBUTORS: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/documentation/conf.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/documentation/index.rst: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/documentation/Makefile: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/LICENSE: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/MANIFEST.in: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/README: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/setup.cfg: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/setup.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/six.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/test_six.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/six/tox.ini: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/socksipy-branch/BUGS: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/socksipy-branch/LICENSE: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/socksipy-branch/MANIFEST: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/socksipy-branch/README: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/socksipy-branch/setup.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/third_party/socksipy-branch/socks.pyc: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/VERSION: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/properties: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/README: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/RELEASE_NOTES: Operation not permitted
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/VERSION: Operation not permitted
==> Using sudo to gain ownership of path '/usr/local/Caskroom/google-cloud-sdk/latest'

Stderr output:
Password:
Error: Command failed to execute!

==> Failed command:
/usr/bin/xattr -w com.apple.metadata:kMDItemAlternateNames (\"git-credential-gcloud\") /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/git-credential-gcloud.sh

==> Standard Output of failed command:

==> Standard Error of failed command:
xattr: [Errno 13] Permission denied: '/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/git-credential-gcloud.sh'

==> Exit status of failed command:
#<Process::Status: pid 17754 exit 1>
Error: nothing to install
Error: Kernel.exit

Output of `brew doctor`
Your system is ready to brew.

Output of `brew cask doctor`
==> Homebrew-Cask Version
Homebrew-Cask 1.1.11
caskroom/homebrew-cask (git revision 731c0; last commit 2017-03-21)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (6 files, 819MB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3614 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-versions (173 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin16
/Library/Ruby/Site/2.0.0/universal-darwin16
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin16
==> Environment Variables
LANG="en_US.UTF-8"
PATH="~/Documents/google-cloud-sdk/bin:~/.gem/ruby/2.0.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/sbin:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/zsh"

Tracked it down to sudo: true by default. It may affect more scripts than just this one.

https://github.com/caskroom/homebrew-cask/pull/30890


RDBES: Deprecate code '<8' and add '<6' and '6-<8'

The following is requested for code type 'RS_VesselLengthCategory':
Deprecate code '<8'
Add code: '<6', description 'Vessel length less than 6 meter'
Add code:  '6-<8', description 'Vessel length between 6 meter and less than 8 meter'.

For RMG:
RS_VesselLenghtCategory: https://vocab.ices.dk/?ref=1633
It should be suggested that all code descriptions needs to be descriptive (written not code copy)
Question is if this code type and this BYC_VesselLRange ( https://vocab.ices.dk/?ref=1502) can be made into one code type (eg VesselLRange or VesselLengthCategory)?

RMG: yes to comments

After discussing this with Henrik, I will contact the BYC chairs and Carlos to see if it would be possible for them shift to (RS_)VesselLengthCategory, instead of the other way around. Since future bycatch data submissions are supposed to go through RDBES.

@cekv  this is linked to issue #263 right? maybe we can close this one?


tls-crypt unwrap error: packet too short

I have tls-auth enabled on my ovpn server. I supply the required file (the TLS key from the server, which the script accepts and sends) but the command fails saying CRIT: Not responding.
Checking the ovpn logs I see that it was having trouble reading the tls key.
Tue Dec 18 21:23:01 2018 TCP connection established with [AF_INET]myip
Tue Dec 18 21:23:01 2018 myip TLS: Initial packet from [AF_INET]myip, sid=removed
Tue Dec 18 21:23:01 2018 myip tls-crypt unwrap error: packet too short
Tue Dec 18 21:23:01 2018 myip TLS Error: tls-crypt unwrapping failed from [AF_INET]myip
Tue Dec 18 21:23:01 2018 myip Fatal TLS error (check_tls_errors_co), restarting
Tue Dec 18 21:23:01 2018 myip SIGUSR1[soft,tls-error] received, client-instance restarting

Here us the command being run:
'/usr/lib/nagios/plugins/check_openvpn' '--tls-auth' '/usr/lib/nagios/plugins/ta.key' '-p' '1194' 'myip'

Guys??

Can I get some help???

@Engineer-of-Stuff can you post your openvpn server config?

@andiwand @Engineer-of-Stuff ,
hello guys, I am confirming that tls-crypt does not work at all.
I am getting  the following error:
Sat Feb  9 14:07:47 2019 tls-crypt unwrap error: packet authentication failed
Here is my server.conf:
mode server
tls-server
tls-crypt /etc/openvpn/certs/tlscrypt.key 0
proto udp
dev tun0
port 1194
topology subnet
group openvpn
user openvpn
auth SHA512
cipher AES-256-GCM
tls-version-min 1.2
tls-cipher TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
duplicate-cn
reneg-sec 0
persist-key
compress lz4-v2
fast-io
tun-mtu 1200
verb 3
max-clients 250
auth-retry interact
ping-restart 15
ping 5
inactive 1800
management <IP_ADDRESS> 5555
status /var/log/openvpn/status.log
log-append /var/log/openvpn/access.log
tmp-dir /etc/openvpn/tmp
plugin /etc/openvpn/plugins/openvpn-plugin-auth-script.so /etc/openvpn/scripts/authenticate.sh
Can you help me please ?
Thank you very much.

@Engineer-of-Stuff i see "Tue Dec 18 21:23:01 2018 TCP connection established with [AF_INET]myip" but for the check script you use udp.
@drajcan i just tested it for my setup and it work. maybe "tls-cipher TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384" is the problem here.

How do I specify TCP in the monitor?

you find it in the usage "  -t, --tcp             use tcp instead of udp"

Note: --tls-auth and tls-crypt are different. This tool doesn't yet have a command-line option for --tls-crypt (see the separate issue https://github.com/liquidat/nagios-icinga-openvpn/issues/22).

@connorpower i see, thank you for pointing this out!

As discussed, we currently do not support tls-crypt. Closing the issue for now.


SQLServiceAccount_SQLAgent running under sysaccount still fails with devversion.

As asked in my previous question, I have tested the scenario of SQLAgent service running under sysadminaccount still fails with dev version. Can this issue be open active  until this is resolved at my end and also to avoid duplicate issues on the same root cause issue. Thank you for your patience .
I took the dev version today and uploaded to azure automation (did not delete the previous version but overwrite the existing module) but still fails. Please find the configuration below and LCM verbose for both setserviceaccount_sqlservice and SetServiceAccount_sqlagent
This is configuration
SqlServiceAccount SetServiceAcccount_SQLAgent
        {
             ServerName     = $Node.NodeName #'$($node.nodename)'#'DSC-SP3'
             InstanceName   = 'MSSQLSERVER'
             ServiceType    = 'SQLServerAgent'
             ServiceAccount = $SqlSysAdmincreds #$ServiceAccountCredential 'OfficeDog\SP997DB' #
             RestartService = $true
         }

Error:
VERBOSE: [DSC-SP11]: LCM:  [ Start  Resource ]  [[SqlServiceAccount]SetServiceAcccount_SQLService]
VERBOSE: [DSC-SP11]: LCM:  [ Start  Test     ]  [[SqlServiceAccount]SetServiceAcccount_SQLService]
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLService] Information: PowerShell module SqlS
erver not found, trying to use older SQLPS module.
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLService] Importing PowerShell module SQLPS.
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLService] 2017-12-29_17-51-14: Connecting to
WMI on 'DSC-SP11'.
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLService] 2017-12-29_17-51-15: Current servic
e account is 'OfficeDog\SP997DB' for DSC-SP11MSSQLSERVER.
VERBOSE: [DSC-SP11]: LCM:  [ End    Test     ]  [[SqlServiceAccount]SetServiceAcccount_SQLService]  in 1.5460 seconds.
VERBOSE: [DSC-SP11]: LCM:  [ Skip   Set      ]  [[SqlServiceAccount]SetServiceAcccount_SQLService]
VERBOSE: [DSC-SP11]: LCM:  [ End    Resource ]  [[SqlServiceAccount]SetServiceAcccount_SQLService]
VERBOSE: [DSC-SP11]: LCM:  [ Start  Resource ]  [[SqlServiceAccount]SetServiceAcccount_SQLAgent]
VERBOSE: [DSC-SP11]: LCM:  [ Start  Test     ]  [[SqlServiceAccount]SetServiceAcccount_SQLAgent]
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLAgent] Information: PowerShell module SqlSer
ver not found, trying to use older SQLPS module.
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLAgent] Importing PowerShell module SQLPS.
VERBOSE: [DSC-SP11]:                            [[SqlServiceAccount]SetServiceAcccount_SQLAgent] 2017-12-29_17-51-15: Connecting to WM
I on 'DSC-SP11'.
VERBOSE: [DSC-SP11]: LCM:  [ End    Test     ]  [[SqlServiceAccount]SetServiceAcccount_SQLAgent]  in 0.7500 seconds.
PowerShell DSC resource MSFT_SqlServiceAccount  failed to execute Test-TargetResource functionality with error message:
System.Exception: The SQLServerAgent service on DSC-SP11\MSSQLSERVER could not be found.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

@rsganta thank you for testing this and providing the verbose logs!

Thank you.  Any possible solutions ?

I created an integration tests for this resource over at PR #987. The configuration do work there, see AppVeyor test run.
I did fix one bug in the resource for the integration tests to pass (see PR description), but that issue should not have cause the above problem.
 Was the resource module replaced on the target node when the configuration ran again?
If you want to use the same code which is tested in the integration tests that was created, you can download the resource code from my working branch, eventually the code will be merged into dev.
Here is the code in PR that is run in the integration tests: https://github.com/johlju/SqlServerDsc/tree/SqlServiceAccount-integration-tests/DSCResources/MSFT_SqlServiceAccount

I am getting the same error, any idea? how to resolve it:
Importing module MSFT_SqlSetup failed with error - File C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\SqlServerDsc\<IP_ADDRESS>\DscResources\MSFT_SqlSetup\MSFT_SqlSetup.psm1 cannot be
loaded. The file C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\SqlServerDsc\<IP_ADDRESS>\DscResources\MSFT_SqlSetup\MSFT_SqlSetup.psm1 is not digitally signed. You cannot run this script on
the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
+ CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : ImportModuleFailed

@cnilak Could you please open a new issue for this error?


Mirror HF summarization example with PiPPy

Create a branch hf_example_summarization
Copy summarization dir to hf
Add files, commit, create a PR(hf_example_summarization->main)
Create another branch hf_example_summarization_pippy on top of hf_example_summarization and all PiPPy changes there
Look at https://github.com/pytorch/PiPPy/pull/359 especially examples/hf/translation/run_translation.py and do the changes in  run_summarization.py accordingly
Add run_summarization.py test to .github/workflows/ci_tests.yaml (see https://github.com/pytorch/PiPPy/pull/359)
Add files, commit, create another PR(hf_example_summarization_pippy->hf_example_summarization)

This is a subtask of https://github.com/pytorch/PiPPy/issues/301

please use T5 and BART for summarization


Materials with dispersion formulas from refractiveindex.info won't load

Materials with n/k tables from refractiveindex.info work just fine, but lots of them (SiO2, BaTiO3) instead have dispersion formulas, and these need to be loaded in separately. Right now the software crashes when trying to load these in, and this needs to be fixed.

This is fixed in commit  c6e3ae0. Unclear if all possible dispersion formulas are included for all materials - likely not.


Update index.yml per Jak's input

Follow-on to https://github.com/MicrosoftDocs/azure-docs/pull/110355

#assign: @jjaygbay, @v-hborys
@jjaygbay or @v-hborys

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

It's jjaygbay1, please.

From: Jak Koke @.>
Sent: Friday, June 2, 2023 5:53:03 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Jacob Jaygbay @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update index.yml per Jak's input (PR #110420)
#assign: @jjaygbayhttps://github.com/jjaygbay, @v-hborys
@jjaygbayhttps://github.com/jjaygbay or @v-hborys

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/110420#issuecomment-1574356432, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AX6KCJHX5XAAASIKRUO6Y23XJJOD7ANCNFSM6AAAAAAYYXYOZY.
You are receiving this because you were mentioned.Message ID: @.***>

#sign-off

#sign-off @jjaygbay1

@Jak-MS AFAIK the assigned author no longer works for Microsoft.

these changes are already live.


⚠ Bofrost.at has degraded performance

In 7b27a0b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1012 ms

Resolved: Bofrost.at performance has improved in aa5c523.


Review Changes from Design Backlog

Review of design changes
The listing page looks for me like this:

-> search bar is too big, please check prototype on figma
-> each listing item is shown in a separate line
-> move the text above the accordion:
"Die hier vorgestellten digitalen Werkzeuge entsprechen den Werkzeugen, die im Rahmen der Auswertung des Fragebogens der wissenschaftlichen Begleitforschung der Forschungsinitiative Energiewendebauen von 2021 und 2023 erfasst wurden. Alle digitalen Werkzeuge werden dementsprechend von Projekten eingesetzt, entwickelt oder weiterentwickelt, die im Rahmen der Forschungsinitiative Energiewendebauen gefördert werden."

-> When accordion is expanded replace the "+" by a "-"
-> can you add the 2 buttons:

Can you fix the spacing here? There should be the same distance to the green border for the image like for the the description text

-> can you add the 2 buttons:

Can you fix the spacing here? There should be the same distance to the green border for the image like for the the description text

Can you please explain more these parts and where they are located? I don't understand.
Everything else is fixed on the branch filip-figma-backlogs.

Sorry i forgot to add a screenshot. Here is the screenshot from the page "Negative Umweltwirkungen"

I just checked and I already added it before, the image looks fine to me:

Could you change it so it looks like in the figma:

So the white padding inside the green box should have the same size everywhere. Here is the figma link: https://www.figma.com/design/9isFFZdptnsTNPVPhOcC5d/Wissensplattform-Entwurf?node-id=631-3301&node-type=canvas&t=HaSzC5vwJEn0whYv-0

Ah I get it now, thanks. I'll get to it

@expeditionengineer it should be okay now


CAA extensions for account URI and method binding

IETF RFC
This allows a CAA record to not only control who is allowed to issue certificates, but also which ACME accounts may receive certificates and which domain validation methods are acceptable. Applicable if DNSSEC works.
Sample CAA record for seirdy.one:
letsencrypt.org; validationmethods=http-01; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/101166947

ready should check for this.

Implementing warnings for both missing accounturi and validationmethod for CAA records that contain "issue"


added google fonts into html and updated title font in css

Best google fonts I have ever laid eyes on

Amazing google fonts


spark#rename spark packages prefixed with 'io'. Removing MANIFEST.MF …

Rename packages for spark.
Adding prefix 'io' as it should be.
Added new Listener io.openlineage.spark.agent.OpenLineageSparkListener
Mark old as deprecated openlineage.spark.agent.OpenLineageSparkListener
They both works fine.
tested with
.config('spark.extraListeners', 'io.openlineage.spark.agent.OpenLineageSparkListener')
and
.config('spark.extraListeners', 'openlineage.spark.agent.OpenLineageSparkListener')
javaagent also works fine

Codecov Report

Merging #216 (0636178) into main (400ff07) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #216   +/-   ##
=======================================
  Coverage   90.00%   90.00%
=======================================
  Files          27       27
  Lines        1580     1580
=======================================
  Hits         1422     1422
  Misses        158      158

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 400ff07...0636178. Read the comment docs.


Allow for expected_elements declaration to enhance all_there check

This should be considered as an alternative approach to https://github.com/natritmeyer/site_prism/pull/98
Let's say the page I'm modeling with a SitePrism::Page class has at least one element that isn't always guaranteed to be present.
class SomePage < SitePrism::Page
  element :name_field, '#name'
  element :err_msg, '.error'
end

If I ever wished to leverage that page's all_there? check, it would fail because the err_msg would not be present on initial load (hopefully). And yet, I would very much like to use the page's all_there? check.
This pull request adds the ability for any page class to declare expected_elements that specifies exactly which page elements should be considered for the all_there? check.
After some thought, I might personally prefer this approach over excluded_elements because, in my experience, it's less verbose to specify the elements that always should be present than to specify those that might not always be present. Furthermore, expected_elements does not need to include literally all elements that should be present - it can include only those element sufficient to signify that the page is ready to receive further automation actions. This is the approach I've taken when doing web automation in non-ruby contexts, and would like to propose a similar approach here.

@tgaff Does this look good to you?

@luke-hill I won't have time to look at the code at least until tomorrow.  At first glance though I'm concerned that it might be a breaking change that will require current users using all_there? to refactor.  Does it by default, default to the current all_there? behavior of checking every element?
If not, and if I'm understanding this, now you have to specify a bunch of elements in order to use it, which will break existing code-bases.  In addition to that, having all_there? by default not really be "all there" strikes me as semantically confusing.  It's not what you would expect when reading just the test code.  (sometimes that's OK, but we should think hard about it)  It's one thing if it excludes one element of many, but a whole other thing if all_there? suddenly means 2 elements out of 20....
I had an idea for an alternate implementation that would allow defining groups of elements to check.  However, I also suspect this feature is getting far more attention than maybe it should.  Nat had stated that he was opposed to it even being in the code-base and I've never needed it.

@tgaff No, it isn't a breaking change. expected_elements is optional, just as excluded_elements was on #98. We know this for two reasons:
First, look at how we gather the elements for the all_there? check:
module SitePrism
  module ElementChecker
    def all_there?
      elements_to_check.all? { |element| send "has_#{element}?" }
    end

    private

    def elements_to_check
      elements = self.class.mapped_items # all defined elements on the page by default
      elements = elements.select { |el| self.class.expected_items.include?(el) } if self.class.expected_items # scope it to expected_elements only if that method is defined
      elements
    end
  end
end

Second, if it were a breaking change I would have had to change existing tests that cover all_there?, and I didn't. Build is green.
This is pretty much exactly the same logic as #98, we're just naming the elements we want to check instead of the ones we don't.

I'm going to go ahead and merge this in as is. I understand specifically how it works. coupled with the elements third definition. As the second definition is explicitly ignored when there is no values in the DSL, so the third value basically "Does nothing"

@TheMetalCode Sorry, maybe I wasn't clear.  I had not had time to look at the code yet.  I was just asking because it's something I would want to be on the lookout for when I do read the code.
Can we talk about tidying up PRs and commit messages a little more in the future?  I think ideally they could be more succinct.  This PR has 27 commits, a number of which don't pass tests and have somewhat unclear commit messages.  It looks like some of them are from 2014.  I realize that that's hardly your fault, but it does make trying to look at this as a whole, once it's merged a little painful.
Also, I know you put a lot of work into this, and it went back and forth until you settled on what you wanted.  I think after you did settle on it, it would have been cleaner to squash most of the original commits (squelching the back-and-forth) and gotten this down to ~1-3 commits.
The rails docs have a relatively short explanation of what I'm trying to say:  http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#commit-your-changes


Add scroll to top button to editor.

closes #3763
Note that this was added to the sticky header instead of the bottom of the page.
Why was this change made?
Editor joy.
How was this change tested?

Which documentation and/or configurations were updated?

Approved, not sure why the codeclimate/diff-coverage declined so much but feel free to merge if ignorable.


Multiple improvements

Composer autoload
register hooks in one method
create tables while installing to show db errors if any exists
remove some unused methods and codes
upgrade postman collection with some random dynamic variables

Nice PR, I will review it, thanks for it ;)

Hey @stifler97,
I reviewed your PR, here are the details:
0- try to push your PR on develop branch, just rebase your current branch with develop
1- adding composer is a nice addition, it looks okay to me, and "prepend-autoloader": false is set. We just need consider namespaces,
why? to avoid future conflicts, (for example, there is a probability of having a class name somewhere in the whole project with the same name RESTTrait.php in the future)
how:

base namespaces' scheme:
PrestaShop\Module\Binshops\
The rest of the namespace follows the directory structure, for example namespace for the class RESTTrait is this:
PrestaShop\Module\Binshops\Classes

same standard for other classes and controllers.
Note:
As the composer and the namespaces need to be checked carefully, we can better track it through another dedicated PR for this feature.
2- register hooks in one method, looks okay to me.
3- It's not necessary, we can keep the old version.
4- We can keep these kind of codes, because this module is for developers and we usually use it as a base module, sometimes we use these lines to build up forms with a quick copy and paste, so they can be used as a boilerplate code.
5- Not necessary to change website_url to SHOP_URL, keep it website_url and I'm not sure about Random variables, because people usually want to see the result of the fixed sent request, especially random password does not make sense. But changing<EMAIL_ADDRESS>to something else like<EMAIL_ADDRESS>and names to John, Doe would be good.

Just to know, this PR's changes are not merged, I just force pushed the older version of develop. If you want to work on it you must create a new PR.


"Segmentation fault" during data preprocessing

Thanks a lot for your implementation!
During the data pre-processing, I encountered "segmentation fault" issues and still now, don't have a clear idea how to solve it. Could you give me some hints how to solve this issue?

Try the two ways:

put blow code into tokenizer.py to get error trace

import faulthandler
faulthandler.enable()

try to use CPU when run tokenizer.py to get more detail error info

If you find the error, make a pull request to fix it.

It is an incompatible error that indicates espeak was not installed properly. Solved by installing espeak-ng from the source.

@KunZhou9646 I ran into the same problem. I also installed espeak-ng from the source. But the problem cannot be solved.
So, how to install espeak-ng from the source properly?

@KunZhou9646 I ran into the same problem. I also installed espeak-ng from the source. But the problem cannot be solved. So, how to install espeak-ng from the source properly?

Can you check if you config espeak-ng properly?

@Dinxin Can you check if you config espeak-ng properly?


WebGL sdk throws compilation errors during linking process for iOS

New static extern methods added to IAgoraGamingRtcEngineNative.cs cause iOS builds to throw compilation errors during the linking process. This was a simple fix by wrapping those methods in platform #define directives, so they only compile for webgl and editor builds. I'd like to make a PR but don't have a write access to the repo. Thanks.

Hi , the proper way to make a PR is via the Fork and Pull model, as described in the official GitHub doc:
https://docs.github.com/en/github/collaborating-with-pull-requests/getting-started/about-collaborative-development-models
Thanks in advance for making contribution to this repo!

Hi, thanks for the PR! It got merged today.


Feature/roi storage maintenance

Feature allows to:

read roi from png file to an object
create png roi file from an object
list all roi from folder

Contains Roi representation.

 ROI storage & maintenance

This is to be continued at https://github.com/spectre-team/platform-components


Improvement/key initialize

Adding functionality to the command line to import certificate and load keys into key table.

Add cert_load function
Add certificate option to command line options
Add key initialization option to command line options

This review will be paused until the completion of #26.

These conflicts will be resolved when this functionality is added during a future merge request.


Correct number of stripes on Malaysia flag

Is your feature request related to a problem? Please describe.
Malaysia flag 🇲🇾 in real life has 14 stripes. Different platform either have correct 14 stripes (Apple, Google, etc), or have an over-simplified version (OpenMoji, JoyPixels). Twemoji has a somewhat realistic flag, but ends up only have 13 stripes, which is a little big confusing.
Describe the solution you'd like
Redesign the 🇲🇾 emoji to either have 14 stripes as in real life, or to a simplified version where there was no confusion that this is supposed to be realistic.

/dup #543
Also no one is working on this repo anymore; It seems https://github.com/jdecked/twemoji is the successor.

Fixed by https://github.com/jdecked/twemoji/pull/5, now in https://github.com/jdecked/twemoji/releases/tag/v14.1.1.


Scrolling is extremely fast on Elan touchpad

VSCode Version: 1.50.0-insider (user setup)
OS Version: Windows 10 Pro version 2004 build 19041.508

When scrolling the code window with touchpad little bit, the thousands of line code scrolling to the end bottom or top one time

My laptop - Lenovo Idepad S145-15IWL i3-8145U version
Touchpad - Elan pointing device Driver version - <IP_ADDRESS> driver date: 5/23/2019

https://im3.ezgif.com/tmp/ezgif-3-0ed3cbf26264.gif

Does this issue occur when all extensions are disabled?: Yes

@0x21106  you can use the editor.mouseWheelScrollSensitivity setting to slow scrolling down. For example, try 0.1.

@0x21106 you can use the editor.mouseWheelScrollSensitivity setting to slow scrolling down. For example, try 0.1.

Thanks brother :) my problem soved 👍  <3


About age and gender

Does it possible to load other DLIB models, like age and gender?
https://github.com/davisking/dlib-models

@jhaoheng, see https://github.com/Kagami/go-face/pull/43

thanks @Danile71