How to only download subtitles vtt (WebVTT) files with youtube-dl

I mistakenly downloaded over 200GB of playlists before realizing I didn't have the --write-auto-sub switch on.  I would like to rerun youtube-dl against my playlists but have it only download the vtt files.  I would like to do it with youtube-dl becuase it will automatically give them all the correct file name (has to match in my application).
I would like to know how to use youtube-dl to only download subtitles for all videos in a given playlist.
Thank you

--skip-download --sub-format vtt --write-sub.

youtube-dl https://www.youtube.com/watch?v=1-xiSOvgNvw&t=6s --skip-download --sub-format vtt --write-sub

@dstftw  Thanks
still work in 2019.
here is a example for copy & paste


Search does not work in Version 2.0

Operating system: ✍ TODO
Last upstream commit (run git log --author="Robert Lord" | head -n 1): ✍ TODO
Browser version(s): ✍ TODO
Ruby version (run ruby -v):  ✍ TODO

✍ TODO write your issue here

Seems to be working for me. Can you elaborate as to why it's not working for you?

My bad sorry, I had my files messed up. Works like a charm. Closing issue.


DataClass error

Hi Ben
Thank you very much for making this great code available to other researchers. I'm just trying to run the demo as you describe it in your youtube video and I'm running into a problem that I can't seem to fix. It may well be down to my lack of matlab experience, but I thought I'd post a question about it here to see if you could offer any suggestions. Perhaps it is a basic oversight on my part so I've pasted the code that I ran below. The error relates to data object that you say shoud be created.  In your basic script it is called 'methodspaper-kirby27.txt'. When I run this script, I get this error:
??? Error using ==> DataClass
Too many input arguments.
Error in ==> test at 6
myData = DataClass('methodspaper-kirby27.txt','data');
Script:
% cd to project folder
cd('C:\Users\Desktop\delay_discounting_code\delay-discounting-analysis-master\demo');
% define toolbox location
toolboxPath = setToolboxPath('C:\Users\Desktop\delay_discounting_code\delay-discounting-analysis-master\ddToolbox');
% load data
myData = DataClass('methodspaper-kirby27.txt','data');
myData.loadDataFiles({'AC-kirby27-DAYS.txt','CS-kirby27-DAYS.txt','NA-kirby27-DAYS.txt','SB-kirby27-DAYS.txt'});
% construct a model and change some option
hModel = ModelHierarchical(toolboxPath, 'JAGS', myData);
hModel.sampler.setMCMCtotalSamples(10^5);
hModel.sampler.setMCMCnumberOfChains(2);
% conduct inference
hModel.conductInference();
%examine results
hModel.exportParameterEstimates();
hModel.plot();

Hi
I hope it's of use to you. So this should be a simple issue to resolve, although I've not tested with a PC, so there could be some more saving issues later, let me know if so.
We can resolve this pretty simply... basically there are two lines in your code which create objects in the 'old' way before I updated the code at a certain point. So I'll assume you've got, or will download the latest version. Let me know if this doesn't work...
% cd to project folder
cd('C:\Users\Desktop\delay_discounting_code\delay-discounting-analysis-master\demo');
% define toolbox location
toolboxPath = setToolboxPath('C:\Users\Desktop\delay_discounting_code\delay-discounting-analysis-master\ddToolbox');
% load data
myData = DataClass('data');
myData.loadDataFiles({'AC-kirby27-DAYS.txt','CS-kirby27-DAYS.txt','NA-kirby27-DAYS.txt','SB-kirby27-DAYS.txt'});
% construct a model and change some option
hModel = ModelHierarchical(toolboxPath, 'JAGS', myData, 'saveFolder');
hModel.sampler.setMCMCtotalSamples(10^3);
hModel.sampler.setMCMCnumberOfChains(2);
% conduct inference
hModel.conductInference();
%examine results
hModel.exportParameterEstimates();
hModel.plot();

The lines changed were
myData = DataClass('data');

and
hModel = ModelHierarchical(toolboxPath, 'JAGS', myData, 'saveFolder');

I'm trying to not change how this setup script works because of exactly this kind of problem. But in situations where you run multiple analyses on the same dataset it makes more sense to do it the new way, that is, to define the save folder in the model. Anyway, reasons aren'y so important, but hopefully this all works now
Let me know how you get on.
Ben

Hi Ben
Thanks very much for getting back to me so quickly and with such a thorough reply. So I just tried your amended script and I got a different error (which is progress I guess!). Also, the version of your code that I have is the latest you have available to download as a zip file from this site. Any more advice would be great!. The output is below.
Cheers
David
??? Undefined function or variable 'table'.
Error in ==> DataClass>DataClass.DataClass at 26
obj.groupTable = table();
Error in ==> test at 6
myData = DataClass('data');

No problem. Sorry about the roadblock to using the code.
The issue seems to be initialising an empty Matlab table, so this could be a Matlab version issue. What version are you running? If you type table() into the matlab command window, do you get an error?
I'll run through it all on a PC to check there aren't issues on that front, but it will take me a few days to get hold of one.

Thanks again for your prompt reply. So when I type table() into matlab I get the output, which is below. My desktop has quite an old version of matlab (2010) though. I just managed to get on to the 2013a version that we have on the server and the same problem occurred. That is, the same error when I run the script and the same ouput when I type table() into the command window.
Sorry to keep bothering you about this problem. Any further ideas would be greatly appreciated.

table()
Undefined function or variable 'table'.

PS Having googled this problem. It seems that the earliest version to have table available is 2013a
http://www.mathworks.com/matlabcentral/answers/167018-which-numeric-type-works-for-function-table

It's not a problem, this is my first 'big' bit of code I am releasing into the wild, so I'm happy to make sure it works for people. And it's not going to hurt the citation count of the paper :)
So sure it seems a pretty straight forward Matlab version issue. The options are either:

upgrade to a newer version of Matlab :)
I could subclass DataClass to make a version which doesn't use Matlab tables. I might be able to fit this in next week.

I realise this is one of the downsides of Matlab. I'm doing an extremely slow transition over to using Python where everything is free, but a Python implementation of this toolbox is not a small job. I've been considering this for a while, partly as a way to commit to learning Python properly, but this is something for the future.
See how you get on with updating Matlab version if possible, but otherwise I hope to resolve this next week at some point.

Yeah unfortunately, I doubt that my lab will update Matlab soon. They are quite strict about those things here in France.
It would be great if you could amend your code, but I would also fully understand if you don't have the time to tailor your code for every single user's needs ;)
Hopefully more researchers will start switching to Python. FYI you probably know of him already but Thomas Wiecki (https://github.com/twiecki) has a lot of Python code available that uses Bayes to analyse choice data. I've never used his code but I saw him give a talk recently and he was very passionate about using Python in science!

I've seen a talk of his on YouTube about PyMC which is a great looking package for doing inference direct in Python rather than having a separate package like JAGS. I'll get to Python eventually! But first on the list is to port the JAGS models to STAN. I've been having a bit of trouble fitting one of my other datasets with JAGS and suspect the sampling in STAN will solve these problems.
Anyway, I'll post back here when I get time to make the code backward compatible.

Ok. That last commit (in the dev branch) should get around the fact that old Matlab versions don't have tables. You need to replace DataClass for DataClassLegacy in your setup script. That should fix the immediate problem you were having. So you change from this
myData = DataClass(pathToData);

to this
myData = DataClassLegacy(pathToData);

Although we may well find more problems with older Matlab version. In particular, the code does require the Statistics Toolbox (recently renamed to Statistics and Machine Learning Toolbox). Try it and see.
If you are not that familiar with GitHub or don't use the GitHub Desktop app, you can go to the main repository page > look for a button called "Branch: master" and change it to "Branch: dev". You can then download as a zip. That should give you the latest version. I'm waiting until I've done a few more things until I do another proper release.

Great! Thanks very much for updating this. I will let you know how it goes once I try it.

Closing this issue, as it wasn't a bug as such. Just we require Matlab 2015 or later


If ResourceId has a duplicate slash it will fail to pull a Token from IMDS

Noticed that resource ID is essentially a path - if a double slash is passed in there is no dedupe and it will fail to grab the token from IMDS

@samkreter @yangl900 @serbrech
had an issue where templating makes it too easy to pass in duplicate slashes into resourceID, should just use the path package to auto dedupe


Integrate SPI delay patch for TS4900

https://github.com/embeddedarm/u-boot/commit/72549bef582001b6dbec2ecb83e094ccb57d72c8

Moved to resin-os/resinos repository.


Update terraform to 0.9.4

This updates the Terraform version used by project from 0.7.2 to 0.9.4. It fixes multiple issues related to Terraform (see : https://github.com/hashicorp/terraform/blob/master/CHANGELOG.md).

As the cert request flow changed after the 0.7.5 version, the jsonnet had to be updated to reflect this change.
The env variable TERRAFORM_SHA256SUM was also deleted from the docker-build script as it wasn't used.

I signed it!

This is probably going to break e2e when it merges. We will need to update:
https://github.com/kubernetes/test-infra/blob/master/images/ci-kubernetes-e2e-kubeadm/Dockerfile#L27

Thanks for taking this on, @MohGeek! I don't fully grok the jsonnet diff, but I can at least do some independent testing to confirm that things still work.

Did you test this with ignition? Things look good with phase2.provider=kubeadm, but I'm not seeing the control plane ever come up when using ignition. Do you have a .config file that works (in particular, the .phase2.installer_container)?

Hi @pipejakob, yes, I was able to test this with ignition on vSphere with the following configuration :
#
# Phase 2: Node Bootstrapping
#
.phase2.installer_container="docker.io/cnastorage/k8s-ignition:v1"
.phase2.docker_registry="gcr.io/google-containers"
.phase2.kubernetes_version="v1.5.3"
.phase2.provider="ignition"

Ah, thank you. It seems my issue was testing your patch with a 1.6.x release, since it looks like our ignition phase2 configuration tries to use flags that are no longer valid for kubelet 1.6, so it's broken anyway. Also, our ignition phase2 currently uses hyperkube, which seems to be unmaintained, so it might be time to consider it deprecated in favor of kubeadm anyway (unless someone wants to give it a lot of love).
/lgtm
I'll handle updating the kubeadm e2e image. Our e2e jobs are currently pinned to a fork of k8s-anywhere, so your commit shouldn't break them. Thanks again for taking this on!


Upgrade concourse-up to 3.13

concourse-up is falling behind the concourse releases.
Recently 3.13.0 was released, concourse-up is still on 3.9.2
We are seriously affected by performance issues due to the Docker overlay driver, which has been fixed/reverted back to btrfs in 3.10 and upwards.
Can you provide som insight into your roadmap for upgrading concourse-up?

In the meantime, is it possible to override the driver settings in a bosh descriptor so that we can use btrfs in 3.9.2 ?

@danyoung sorry to stress this matter.  Do you have some sort of estimate for this issue?
It would be useful to know wether its days, a week or several weeks

@engrun this is more likely to be weeks than days, due to our availability.

@engrun We've resolved the issues we were seeing and have released a new version. I'm going to mark this issue as resolved.

thanks!


Integration Test - Release - 2019/03/14 20:26:34

Auto create for integration test. IssueCommandFlow

@PRMergerTest2 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


nginx config doesn't follow my VIRTUAL_PORT

I've used nginx-proxy with containers running on several ports without any issues using VIRTUAL_PORT to map it to the correct port.
Now I've started using docker-letsencrypt-nginx-proxy-companion but since I've added this container it seems nginx-proxy is ignoreing my VIRTUAL_PORT.
Here is my docker-compose.yml for the nginx-proxy:
version: "3"
services:

  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - "/var/run/docker.sock:/tmp/docker.sock:ro"
      - "nginx-certs:/etc/nginx/certs:ro"
      - "nginx-vhost:/etc/nginx/vhost.d"
      - "nginx-html:/usr/share/nginx/html"
      - "./etc/nginx/conf.d/client_max_body_size.conf:/etc/nginx/conf.d/client_max_body_size.conf"
    labels:
      - "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy"

  letsencrypt-nginx-proxy-companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt-nginx-proxy-companion
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro"
      - "nginx-certs:/etc/nginx/certs:rw"
      - "nginx-vhost:/etc/nginx/vhost.d"
      - "nginx-html:/usr/share/nginx/html"
    environment:
      - NGINX_PROXY_CONTAINER=nginx-proxy

volumes:
  nginx-certs:
  nginx-vhost:
  nginx-html:

And here is the docker-compose.yml snippet for my container that I'm trying to run:
  something:
    environment:
      - VIRTUAL_HOST=something.somedomain.nl
      - VIRTUAL_PORT=3081
      - LETSENCRYPT_HOST=something.somedomain.nl
      -<EMAIL_ADDRESS>      - PORT=3081
    image: 'somebody/something:latest'

Yet the upstream in /etc/nginx/conf.d/default.conf points to port 80:
# something.somedomain.nl
upstream something.somedomain.nl {
				# Cannot connect to network of this container
				server <IP_ADDRESS> down;
				# Cannot connect to network of this container
				server <IP_ADDRESS> down;
				# Cannot connect to network of this container
				server <IP_ADDRESS> down;
				## Can be connected with "someproject_default" network
			# someproject_something_1
			server <IP_ADDRESS>:80;
				# Cannot connect to network of this container
				server <IP_ADDRESS> down;
				# Cannot connect to network of this container
				server <IP_ADDRESS> down;
}

I'm not sure why it complains about the other containers not being connectible. I've made sure all containers are in the same network.

Hi. I don't see any network configuration statements in your compose files. If you have multiple compose files and zero additional network configuration, there is no way they'll be in the same docker network.

Closing due to inactivity.

@buchdag Sorry, I had missed your earlier comment.

Hi. I don't see any network configuration statements in your compose files. If you have multiple compose files and zero additional network configuration, there is no way they'll be in the same docker network.

The networks are attached manually (actually, scripted outside of the docker-compose files). Any services that run on port :80 would work normally, however when I try to proxy something to a different port it will simply not work.
You can also see in the nginx config snippet I posted that someproject_default network is accessible from the nginx-proxy container.

Also, I have since switched to Traefik exclusively so unless someone else shows up with the same issue there is no need to reopen the issue. Just thought I'd reply to explain it better.

Aaaaand I ripped and reopened the issue 😄

@Yogarine  Could this project to converted to use Traefik instead of Nginx? It seems a lot easier to configure and has a nice UI frontend.
How did you use Traekif instead of nginx with letsencypt?

@IAMtheIAM I'm considering the same. This project seems a bit neglected by it's author.


Error when interpolating to='outer'

This is pigging back on the issue #507 but using the version xgcm=0.8.0 now I'm getting an error when trying to interpolate along a dimension that has outer coordinates. I've pasted a reproducible example below.
ds = xr.DataArray(np.ones(10)*.5,dims='Z',coords={'Z':np.arange(.5,10,1)}).chunk({'Z':-1}).to_dataset(name='drF')
ds.coords['Zp1'] = xr.DataArray(np.arange(11),dims='Zp1',coords={'Zp1':np.arange(11)})
grid = Grid(ds, coords={'Z': {'center': 'Z', 'outer': 'Zp1'}})

grid.interp(ds.drF, 'Z', boundary='extend', to='outer')

--------------------------------------------------------------------
NotImplementedError                       Traceback (most recent call last)
Input In [19], in <cell line: 5>()
      2 ds.coords['Zp1'] = xr.DataArray(np.arange(11),dims='Zp1',coords={'Zp1':np.arange(11)})
      3 grid = Grid(ds, coords={'Z': {'center': 'Z', 'outer': 'Zp1'}})
----> 5 grid.interp(ds.drF, 'Z', boundary='extend', to='outer')

File ~/miniconda3/envs/xgcm/lib/python3.9/site-packages/xgcm/grid.py:2041, in Grid.interp(self, da, axis, **kwargs)
   1989 def interp(self, da, axis, **kwargs):
   1990     """
   1991     Interpolate neighboring points to the intermediate grid point along
   1992     this axis.
   (...)
   2039     >>> grid.interp(da, ["X", "Y"], periodic={"X": True, "Y": False})
   2040     """
-> 2041     return self._1d_grid_ufunc_dispatch("interp", da, axis, **kwargs)

File ~/miniconda3/envs/xgcm/lib/python3.9/site-packages/xgcm/grid.py:1836, in Grid._1d_grid_ufunc_dispatch(self, funcname, data, axis, to, keep_coords, metric_weighted, other_component, **kwargs)
   1833 else:
   1834     map_overlap = False
-> 1836 array = grid_ufunc(
   1837     self,
   1838     array,
   1839     axis=[(ax_name,)],
   1840     keep_coords=keep_coords,
   1841     dask=dask,
   1842     map_overlap=map_overlap,
   1843     other_component=other_component,
   1844     **remaining_kwargs,
   1845 )
   1847 if ax_metric_weighted:
   1848     metric = self.get_metric(array, ax_metric_weighted)

File ~/miniconda3/envs/xgcm/lib/python3.9/site-packages/xgcm/grid_ufunc.py:460, in GridUFunc.__call__(self, grid, axis, *args, **kwargs)
    458 map_overlap = kwargs.pop("map_overlap", self.map_overlap)
    459 pad_before_func = kwargs.pop("pad_before_func", self.pad_before_func)
--> 460 return apply_as_grid_ufunc(
    461     self.ufunc,
    462     *args,
    463     axis=axis,
    464     grid=grid,
    465     signature=self.signature,
    466     boundary_width=self.boundary_width,
    467     boundary=boundary,
    468     dask=dask,
    469     map_overlap=map_overlap,
    470     pad_before_func=pad_before_func,
    471     **kwargs,
    472 )

File ~/miniconda3/envs/xgcm/lib/python3.9/site-packages/xgcm/grid_ufunc.py:745, in apply_as_grid_ufunc(func, axis, grid, signature, boundary_width, boundary, fill_value, keep_coords, dask, map_overlap, pad_before_func, other_component, *args, **kwargs)
    742 # Maybe map function over chunked core dims using dask.array.map_overlap
    743 if map_overlap:
    744     # Disallow situations where shifting axis position would cause chunk size to change
--> 745     _check_if_length_would_change(sig)
    747     mapped_func = _map_func_over_core_dims(
    748         func,
    749         args,
   (...)
    753         out_dtypes,
    754     )
    755 else:

File ~/miniconda3/envs/xgcm/lib/python3.9/site-packages/xgcm/grid_ufunc.py:1002, in _check_if_length_would_change(signature)
    996 all_ax_positions = set(
    997     p
    998     for arg_ps in signature.in_ax_positions + signature.out_ax_positions
    999     for p in arg_ps
   1000 )
   1001 if any(pos in DISALLOWED_OVERLAP_POSITIONS for pos in all_ax_positions):
-> 1002     raise NotImplementedError(
   1003         "Cannot chunk along a core dimension for a grid ufunc which has a signature which "
   1004         f"includes one of the axis positions {DISALLOWED_OVERLAP_POSITIONS}"
   1005     )

NotImplementedError: Cannot chunk along a core dimension for a grid ufunc which has a signature which includes one of the axis positions ['inner', 'outer']

The error goes away again if I load the array into memory:
grid.interp(ds.drF.load(), 'Z', boundary='extend', to='outer')

Sorry for the slow response everyone.

I have (or had) the same problem and can confirm that changing the > 0 back to > 1 fixes the issue and produces the expected results. Hopefully the change doesn't break anything else!

This works, and makes sense, but for reasons I don't fully understand it re-breaks #507... I need to investigate further.
I'm tempted to make this small change to fix interp first and then fix cumsum afterwards - cumsum is a special function which is fundmentally different to all other operations offered by xGCM (as it is an integral operator rather than a differential one).


spanner-jdbc: Add jdbc statement integration tests

Adds integration tests for JDBC statements and prepared statements.

Test failure is caused by flake that is addressed by #6095.

LGTM after rebase

Rebased.


Add Livewire debug attribute

[ ] Bug fix
[x] New feature
[ ] Breaking change

Description
Usage
#[Ds]
class ActionRulesTable extends PowerGridComponent
{
    public string $tableName = 'actionRulesTable';

    // ...
}

Profile

Properties

Queries

Validation

Events

Documentation
This PR requires Documentation update?

[ ] Yes
[ ] No
[ ] I have already submitted a Documentation pull request.

@luanfreitasdev do we need to check for this attribute in vendor/bin/laradumps check so it doesn't go to production?

@dansysanalyst. We can leave a #[Ds] or default full namespace. Even though this doesn't work in production because of the "isProduction()" validation

Yes, fair enough. Very cool feature.
I am also wondering if the annotation is too generic and could be used in the future for other functionalities, while today is dedicated to debug Livewire.
Would be better to rename it to  something like #[DsLivewire], #[DsWire] , #[LivewireDs] ?

Good catch. However, I find "Ds" simple to write about others. We can keep Ds because of the namespace. If one day there is another attribute, the namespace will be different


Fix battery.plugin when acpi writes to stderr

I have a machine which outputs the following when acpi is run:
❯ acpi
No support for device type: power_supply

This ends up showing everywhere I include battery_pct() - including my prompt!  It's an easy fix - just make it consistent which arguments we're passing to acpi in the battery plugin.

No worries - and I'm happy to tweak it.
BUT - if I do, I'm fixing all of the references to acpi 2&>/dev/null in the file to be consistent.

Oh that's awesome, I didn't knew there were other instances of that. Thanks for the change!
PS. looks like Github's new review process is absolutely perfect :)


Can't install bitsdojo

When I run the command: flutter pub add bitsdojo_window
I get the following output:
The current Dart SDK version is 3.1.4.

Because bitsdojo_window <0.1.0 doesn't support null safety and bitsdojo_window >=0.1.2 <0.1.3 depends on bitsdojo_window_windows ^0.1.2,
  bitsdojo_window <0.1.0-∞ or >=0.1.2 <0.1.3-∞ requires bitsdojo_window_windows ^0.1.2.
And because bitsdojo_window >=0.1.0 <0.1.2 depends on bitsdojo_window_windows ^0.1.0 and bitsdojo_window_windows >=0.1.0 <0.1.2 depends on
  win32 ^2.0.0, bitsdojo_window <0.1.3 requires win32 ^2.0.0 or bitsdojo_window_windows ^0.1.2.
And because bitsdojo_window >=0.1.4 <0.1.5 depends on bitsdojo_window_windows ^0.1.4 and bitsdojo_window >=0.1.3 <0.1.4 depends on
  bitsdojo_window_windows ^0.1.3, bitsdojo_window <0.1.5 requires win32 ^2.0.0 or bitsdojo_window_windows ^0.1.2.
And because bitsdojo_window_windows >=0.1.2 <0.1.4 depends on win32 ^2.5.2 and bitsdojo_window >=0.1.5 depends on bitsdojo_window_windows
  ^0.1.5, every version of bitsdojo_window requires win32 ^2.0.0 or bitsdojo_window_windows ^0.1.4.
And because bitsdojo_window_windows >=0.1.4 depends on win32 ^3.0.0 and win_ble >=1.0.0 depends on win32 ^5.0.6, win_ble >=1.0.0 is
  incompatible with bitsdojo_window.
So, because <APP_NAME> depends on both win_ble ^1.0.1 and bitsdojo_window any, version solving failed.

The lower bound of "sdk: '>=2.7.0 <3.0.0'" must be 2.12.0 or higher to enable null safety.
For details, see https://dart.dev/null-safety

Any suggestions on how to resolve this problem?

Please try updating to the latest bitsdojo_window version.

So far so good. I can install bitsdojo successfully. Will need more time to integrate it into my app though...


Update gridcoinresearch.pro

Tested builds in qt5 and qt4 ubuntu linux. All good. Needs a Win build test.
Added win32: prefix to three modules at top of the .pro file that are win only.

Tested successfully on Arch linux as well

Thanks.


Encounter a segmentation fault when trying to search something

General troubleshooting steps

[ ] I have retried my command with --force and the issue is still present.
[x] I have checked the instructions for reporting bugs (or making requests) before opening the issue.

[x] None of the templates was appropriate for my issue, or I’m not sure.

[ ] I ran brew update-reset && brew update and retried my command.
[x] I ran brew doctor, fixed as many issues as possible and retried my command.
[x] I understand that if I ignore these instructions, my issue may be closed without review.

Description of issue
brew cask suddenly cause ruby segmentation fault and then goes fine. It should be a bug of ruby (from Apple), however I cannot reproduce it anymore. I decided to open this issue, if it does not any makes sense, feel free to close it.
Terminal output:
[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 134]
% brew cask search tenpaycert
/usr/local/Homebrew/Library/Homebrew/brew.rb:16: [BUG] Segmentation fault at 0x00000000000000
ruby 2.3.3p222 (2016-11-21 revision 56859) [universal.x86_64-darwin17]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/CrashReporter
     * /Library/Logs/CrashReporter
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

-- Control frame information -----------------------------------------------
c:0004 p:---- s:0023 e:000022 CFUNC  :initialize
c:0003 p:---- s:0021 e:000020 CFUNC  :new
c:0002 p:0181 s:0017 E:000018 EVAL   /usr/local/Homebrew/Library/Homebrew/brew.rb:16 [FINISH]
c:0001 p:0000 s:0002 E:001d30 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `<main>'
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `new'
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `initialize'

-- Machine register context ------------------------------------------------
 rax: 0x0000000000000005 rbx: 0x00007fdf2b895cf8 rcx: 0x000000000000001f
 rdx: 0x000000000000002c rdi: 0x2c87d9b800007fc0 rsi: 0x0000000000000000
 rbp: 0x00007ffee9fb5b70 rsp: 0x00007ffee9fb5b70  r8: 0x00007ffee9fb5bb0
  r9: 0x00007ffee9fb5c98 r10: 0x00007fdf2c421a20 r11: 0x00007fff64bc7ac0
 r12: 0x0000000105da4f40 r13: 0x00007fdf2ae00af0 r14: 0x00007fdf2b895488
 r15: 0x00007fdf2c422b00 rip: 0x00007fff64bc7add rfl: 0x0000000000010202

-- C level backtrace information -------------------------------------------
0   Ruby                                0x00007fff48878247 rb_print_backtrace + 29
1   Ruby                                0x00007fff4887841e rb_vm_bugreport + 364
2   Ruby                                0x00007fff487756dd rb_bug_context + 206
3   Ruby                                0x00007fff48810a96 Init_signal + 3242
4   libsystem_platform.dylib            0x00007fff64bc8f5a _sigtramp + 26
5   libsystem_platform.dylib            0x00007fff64bc7add _platform_memchr$VARIANT$Haswell + 29

-- Other runtime information -----------------------------------------------

* Loaded script: /usr/local/Homebrew/Library/Homebrew/brew.rb

* Loaded features:

    0 enumerator.so
    1 thread.rb
    2 rational.so
    3 complex.so
    4 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/enc/encdb.bundle
    5 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/enc/trans/transdb.bundle
    6 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/unicode_normalize.rb
    7 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/rbconfig.rb
    8 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/compatibility.rb
    9 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/defaults.rb
   10 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/deprecate.rb
   11 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/errors.rb
   12 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/version.rb
   13 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/requirement.rb
   14 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/platform.rb
   15 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/basic_specification.rb
   16 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/stub_specification.rb
   17 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/util/list.rb
   18 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/stringio.bundle
   19 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/specification.rb
   20 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/exceptions.rb
   21 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/dependency.rb
   22 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb
   23 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/monitor.rb
   24 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb
   25 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems.rb
   26 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/path_support.rb
   27 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/version.rb
   28 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/core_ext/name_error.rb
   29 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/levenshtein.rb
   30 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/jaro_winkler.rb
   31 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkable.rb
   32 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/delegate.rb
   33 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb
   34 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb
   35 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers.rb
   36 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/method_name_checker.rb
   37 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/null_checker.rb
   38 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/formatter.rb
   39 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean.rb
   40 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/pathname.bundle
   41 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/pathname.rb

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

[1]    61268 abort      brew cask search tenpaycert

[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 134]
% brew cask search
/usr/local/Homebrew/Library/Homebrew/brew.rb:16: [BUG] Segmentation fault at 0x00000000000000
ruby 2.3.3p222 (2016-11-21 revision 56859) [universal.x86_64-darwin17]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/CrashReporter
     * /Library/Logs/CrashReporter
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

-- Control frame information -----------------------------------------------
c:0004 p:---- s:0023 e:000022 CFUNC  :initialize
c:0003 p:---- s:0021 e:000020 CFUNC  :new
c:0002 p:0181 s:0017 E:000a58 EVAL   /usr/local/Homebrew/Library/Homebrew/brew.rb:16 [FINISH]
c:0001 p:0000 s:0002 E:001ab0 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `<main>'
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `new'
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `initialize'

-- Machine register context ------------------------------------------------
 rax: 0x0000000000000005 rbx: 0x00007fe0db094cf0 rcx: 0x0000000000000020
 rdx: 0x000000000000002c rdi: 0xdb89986000007fc0 rsi: 0x0000000000000000
 rbp: 0x00007ffee9c5ab80 rsp: 0x00007ffee9c5ab80  r8: 0x00007ffee9c5abc0
  r9: 0x00007ffee9c5aca8 r10: 0x00007fe0dae58500 r11: 0x00007fff64bc7ac0
 r12: 0x00000001060fff40 r13: 0x00007fe0dac02b40 r14: 0x00007fe0db094ca0
 r15: 0x00007fe0dae595e0 rip: 0x00007fff64bc7add rfl: 0x0000000000010202

-- C level backtrace information -------------------------------------------
0   Ruby                                0x00007fff48878247 rb_print_backtrace + 29
1   Ruby                                0x00007fff4887841e rb_vm_bugreport + 364
2   Ruby                                0x00007fff487756dd rb_bug_context + 206
3   Ruby                                0x00007fff48810a96 Init_signal + 3242
4   libsystem_platform.dylib            0x00007fff64bc8f5a _sigtramp + 26
5   libsystem_platform.dylib            0x00007fff64bc7add _platform_memchr$VARIANT$Haswell + 29

-- Other runtime information -----------------------------------------------

* Loaded script: /usr/local/Homebrew/Library/Homebrew/brew.rb

* Loaded features:

    0 enumerator.so
    1 thread.rb
    2 rational.so
    3 complex.so
    4 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/enc/encdb.bundle
    5 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/enc/trans/transdb.bundle
    6 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/unicode_normalize.rb
    7 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/rbconfig.rb
    8 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/compatibility.rb
    9 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/defaults.rb
   10 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/deprecate.rb
   11 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/errors.rb
   12 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/version.rb
   13 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/requirement.rb
   14 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/platform.rb
   15 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/basic_specification.rb
   16 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/stub_specification.rb
   17 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/util/list.rb
   18 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/stringio.bundle
   19 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/specification.rb
   20 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/exceptions.rb
   21 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/dependency.rb
   22 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb
   23 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/monitor.rb
   24 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb
   25 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems.rb
   26 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/path_support.rb
   27 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/version.rb
   28 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/core_ext/name_error.rb
   29 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/levenshtein.rb
   30 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/jaro_winkler.rb
   31 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkable.rb
   32 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/delegate.rb
   33 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb
   34 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb
   35 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers.rb
   36 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/method_name_checker.rb
   37 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/null_checker.rb
   38 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/formatter.rb
   39 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean.rb
   40 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/pathname.bundle
   41 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/pathname.rb

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

[1]    61399 abort      brew cask search

[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 134]
% brew update

[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 130]
% which ruby
/usr/bin/ruby

[0|lanxingcan@macbook-of-lanxingcan:~]
% brew update
^C%
[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 130]
% brew cask
/usr/local/Homebrew/Library/Homebrew/brew.rb:16: [BUG] Segmentation fault at 0x00000000000000
ruby 2.3.3p222 (2016-11-21 revision 56859) [universal.x86_64-darwin17]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/CrashReporter
     * /Library/Logs/CrashReporter
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

-- Control frame information -----------------------------------------------
c:0004 p:---- s:0023 e:000022 CFUNC  :initialize
c:0003 p:---- s:0021 e:000020 CFUNC  :new
c:0002 p:0181 s:0017 E:0005f8 EVAL   /usr/local/Homebrew/Library/Homebrew/brew.rb:16 [FINISH]
c:0001 p:0000 s:0002 E:001490 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `<main>'
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `new'
/usr/local/Homebrew/Library/Homebrew/brew.rb:16:in `initialize'

-- Machine register context ------------------------------------------------
 rax: 0x0000000000000005 rbx: 0x00007fe1aa895f38 rcx: 0x0000000000000021
 rdx: 0x000000000000002c rdi: 0xac81559800007fc0 rsi: 0x0000000000000000
 rbp: 0x00007ffee0a7fb90 rsp: 0x00007ffee0a7fb90  r8: 0x00007ffee0a7fbd0
  r9: 0x00007ffee0a7fcb8 r10: 0x00007fe1aa44f2a0 r11: 0x00007fff64bc7ac0
 r12: 0x000000010f2daf40 r13: 0x00007fe1aa403550 r14: 0x00007fe1aa895dd0
 r15: 0x00007fe1aa46cc60 rip: 0x00007fff64bc7add rfl: 0x0000000000010206

-- C level backtrace information -------------------------------------------
0   Ruby                                0x00007fff48878247 rb_print_backtrace + 29
1   Ruby                                0x00007fff4887841e rb_vm_bugreport + 364
2   Ruby                                0x00007fff487756dd rb_bug_context + 206
3   Ruby                                0x00007fff48810a96 Init_signal + 3242
4   libsystem_platform.dylib            0x00007fff64bc8f5a _sigtramp + 26
5   libsystem_platform.dylib            0x00007fff64bc7add _platform_memchr$VARIANT$Haswell + 29

-- Other runtime information -----------------------------------------------

* Loaded script: /usr/local/Homebrew/Library/Homebrew/brew.rb

* Loaded features:

    0 enumerator.so
    1 thread.rb
    2 rational.so
    3 complex.so
    4 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/enc/encdb.bundle
    5 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/enc/trans/transdb.bundle
    6 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/unicode_normalize.rb
    7 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/rbconfig.rb
    8 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/compatibility.rb
    9 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/defaults.rb
   10 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/deprecate.rb
   11 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/errors.rb
   12 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/version.rb
   13 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/requirement.rb
   14 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/platform.rb
   15 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/basic_specification.rb
   16 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/stub_specification.rb
   17 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/util/list.rb
   18 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/stringio.bundle
   19 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/specification.rb
   20 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/exceptions.rb
   21 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/dependency.rb
   22 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb
   23 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/monitor.rb
   24 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb
   25 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems.rb
   26 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/path_support.rb
   27 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/version.rb
   28 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/core_ext/name_error.rb
   29 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/levenshtein.rb
   30 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/jaro_winkler.rb
   31 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkable.rb
   32 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/delegate.rb
   33 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb
   34 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb
   35 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/name_error_checkers.rb
   36 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/method_name_checker.rb
   37 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/spell_checkers/null_checker.rb
   38 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean/formatter.rb
   39 /Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib/did_you_mean.rb
   40 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17/pathname.bundle
   41 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/pathname.rb

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

[1]    61845 abort      brew cask

[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 134]
% brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: The filesystem on / appears to be case-sensitive.
The default macOS filesystem is case-insensitive. Please report any apparent problems.

[0|lanxingcan@macbook-of-lanxingcan:~] [exit: 1]
% brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.3.6
caskroom/homebrew-cask (git revision 4bb15; last commit 2017-11-06)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (36 files, 3.9GB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3797 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-fonts (1121 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-versions (175 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib
/Library/Ruby/Site/2.3.0
/Library/Ruby/Site/2.3.0/x86_64-darwin17
/Library/Ruby/Site/2.3.0/universal-darwin17
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0/x86_64-darwin17
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0/universal-darwin17
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/x86_64-darwin17
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17
==> Environment Variables
LANG="zh_CN.UTF-8"
LC_CTYPE="zh_CN.UTF-8"
PATH="~/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/MacGPG2/bin:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/zsh"

[0|lanxingcan@macbook-of-lanxingcan:~]
% brew cask
brew-cask provides a friendly homebrew-style CLI workflow for the
administration of macOS applications distributed as binaries.

Commands:

    --version              displays the Homebrew-Cask version
    audit                  verifies installability of Casks
    cat                    dump raw source of the given Cask to the standard output
    cleanup                cleans up cached downloads and tracker symlinks
    create                 creates the given Cask and opens it in an editor
    doctor                 checks for configuration issues
    edit                   edits the given Cask
    fetch                  downloads remote application files to local cache
    home                   opens the homepage of the given Cask
    info                   displays information about the given Cask
    install                installs the given Cask
    list                   with no args, lists installed Casks; given installed Casks, lists staged files
    outdated               list the outdated installed Casks
    reinstall              reinstalls the given Cask
    search                 searches all known Casks
    style                  checks Cask style using RuboCop
    uninstall              uninstalls the given Cask
    zap                    zaps all files associated with the given Cask

See also "man brew-cask"
Error: Unknown command:

The script having the issue is /usr/local/Homebrew/Library/Homebrew/brew.rb so this is a problem for https://github.com/homebrew/brew.
But if you can’t reproduce anymore, there’s not much to do.


ValidationUtils.isNonnegativeInteger returns true for -0

Just something I came across while working on #46 - i'm not sure if this is desired behaviour or not

I didn't know about signed 0 until today.  Where can we meet it?

@tonyofbyteball https://stackoverflow.com/questions/7223359/are-0-and-0-the-same
It's part of IEEE 754. Most of the time you can ignore it because -0 === 0 and 1+ -0 === 1 + 0 etc.
The main difference in practical terms is when dividing by zero as:
1/-0 === -Infinity and 1/0 === Infinity
JS also returns false for Object.is(-0,0).
The reason it is coming up at all is because JS doesn't actually have an explicit integer number type, as it uses doubles for everything. Even after ES6 introduced Number.isInteger it still uses doubles for all "integers" - this breaks down a bit at 0 and outside Number.MIN_SAFE_INTEGER and Number.MAX_SAFE_INTEGER.
As a comparison, here is the output from my REPL in clojure (using the JVM which has both floats and integer number types):
boot.user=> (/ 1 0)
java.lang.ArithmeticException: Divide by zero
boot.user=> (/ 1 -0)
java.lang.ArithmeticException: Divide by zero
boot.user=> (/ 1 0.0)
Infinity
boot.user=> (/ 1 -0.0)
-Infinity

You can see there is a difference between signed 0 in doubles but dividing by integer 0 is always an exception as there isn't an integer negative zero AFAIK.
IMO the behaviour of integers is usually what you want, dividing by the integer 0 is undefined in normal arithmetic and throwing an error is more helpful than returning Infinity to be propagated through the rest of your code :/

So yeah... tbh it could go either way...
Argument for:
There is no difference between the integer represented by both -0 and 0 as there is only one integer 0 so therefore -0 is not a negative integer, so therefore isNonnegativeInteger should return true.
Argument against:
JavaScript does not have any integers in reality, so following IEEE 754 there is a difference between -0 and 0 that will be apparent as soon as you multiply or divide anything by either of them. Even though we are willing to take ES6's lead on designating a subset of doubles as "integers" as per Number.isInteger, and -0 is definitely one of these integers, it is also a negative value, so we cannot say that it is "non negative". Therefore isNonnegativeInteger should return false.


Add new module: dictionary

https://github.com/the-vision/jarvis-telegram/wiki
Maybe use urban dictionary api

@swapagarwal @TeAmP0is0N Please assign me this.

@adityabisoi Go Ahead.


Error Lens shows me an issues that is not shown in my "Problems" window

I just installed Error Lens for the first time and my  "Problems" window is empty:

Despite this, in one of my files, Error lens shows me an error:

It would expect both views to be in sync.

Those are hint level diagnostics. VSCode doesn't show them in problems view and doesn't have an option to include it.
You can either add this particular message to excluded in settings.json:
"errorLens.exclude": [
    "'require' call may be converted to an import."
]

Or disable all hint level diagnostics:
"errorLens.enabledDiagnosticLevels": [
	"error",
	"warning",
	"info",
	// "hint",// delete this
],

Yes, this was the problem. Thank you!!


Can multiple secondary databases  share an elastic pool?

Are “Each elastic pool is contained within a single region, therefore multiple secondary databases in the same topology can never share an elastic pool.” and
“You can use geo-replication to create a secondary database in the same region as the primary.” statements contradict each other?

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

ID: 16170e73-99ca-1a2f-b5ba-b4f0396e3e39
Version Independent ID: d83478e0-f123-5fe6-6f17-3d118eb280da
Content: Active geo-replication - Azure SQL Database
Content Source: articles/sql-database/sql-database-active-geo-replication.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @anosov1960
Microsoft Alias: sashan

@MNF
Thanks for your feedback! We will investigate and update as appropriate.

There is no contradiction. Each secondary must have the same database name as the primary. The database names are unique within each SQL server. Therefore, within the same server you can only have a single secondary for the same primary. You can host the secondary in a pool but because pools cannot span servers, you can only have one per pool.

#reassign: @MashaMSFT
See my comment above

@MNF , thanks for your patience and our apologies for the delay. Has your question been addressed?
Thanks!
Masha from the SQL Docs team

I'm going to go ahead and close this issue. Feel free to continue the conversation if needed.
Thanks!
#please-close


[ci] Test approval jobs

Testing how approval jobs interact with github checks.

It'll display as pending. Though we can mark it as not required in the github checks settings. Looks like a good candidate for more expensive manual tests.


Fix import error in torchtune due to bc breaking changes in torchao

Summary: att
Differential Revision: D64261315

real fix in https://github.com/pytorch/torchtune/pull/1812


Great performance, but multi-line comments broken

I enabled ES6 preview as a random attempt to reduce CPU usage of IntelliSense with my Node.js code. (I'm using a different node executable to run my code from the one used by MSVS, so I thought maybe...) Turns out it really helped perf a lot! Yay!
But soon afterwards I found that my multiline comment auto-completion was broken. No more support for typing "/**" and getting the comment block to complete, and no adding of the leading '*' for newlines in the block comment.
To verify, I switched back to "Quick IntelliSense" for Node.js, and restarted VS. Sure enough, the block commenting was working again... and perf started sucking horribly again. :)
Hope this helps.

Thanks for the feedback! Unfortunately, switching to a new language service means we need to re-implement features, and we haven't gotten to all of them just yet.

Understood. Just making sure it's known. Thanks for the reply.
Oh, and whatever you're doing with the performance, keep it up! :)

I just tested this in the latest VS2017 builds ("VS15") and confirmed that the TypeScript team has partially added this behavior.
The editor will now automatically complete multiline documentation comments if they precede an documentable element (variable declaration, function, class, ...).
Starting with this code:

When I press * again, the following is completed:

However, this completion is not triggered if the element is not documentable:

Also, there are no completions for regular (non-documentation) multiline-comments.

Closing as this is a TypeScript issue.


Custom Reporter (documentation update request)

Hi there. I just wrote a custom Mocha reporter that I believe might be useful to Mocha users. Is it possible to have the official documentations list or mention it in the third-party reporters?
This is the package: https://www.npmjs.com/package/mocha-progress-reporter
There's a screen recording GIF in the documentation that shows some of the extra capabilities of this reporter.
P.S. I posted this a few days ago in the Gitter chatroom and no one replied. No idea where to ask this. So I apologize if this is not the right place.

We don't manage third-party reporters tightly yet. So, I added your reporter to our Wiki page. Thank you.

@outsideris Thank you so much!


Streaming rate

The current way we calculate rate and friends (increase and delta) is to buffer
samples for the whole windowing range and apply the rate function over
that buffer. Samples which are used in the next step are retained, and
reused for the next step. This approach works well for short rate intervals (up to a few minutes),
but it ends up using significant memory when the rate interval is over an hour long.
This commit implements a specialized rate buffer which can calculate the rate
in a streaming manner, by keeping track of the first and last sample for each
evaluation step. In order to account for counter resets, we also store samples
that trigger the reset in a separate slice and pass them to the rate function.
The advantage of this approach is twofold:

we can use far less memory for instant queries over long rate intervals since we
only track the first and last sample for the evaluation step
when using Grafana, the rate interval and step variables are set such that there
is a very small overlap between sequential steps (e.g. rate_interval = 1m, step = 45s).
This means that the rate buffer should only calculate the value for 2 steps at a time,
and can reuse state from past steps for upcoming ones.

This PR also sets up a framework for adding other specialized aligner implementations in the future, such as count_over_time, sum_over_time or last_over_time.
cc @beorn7 Maybe something we can also use for Prometheus?

Maybe… I don't know the Prometheus engine well enough to tell how much re-plumbing this needs.
Mid-term, I'd like to see an approach where we know the counter resets in advance (native histograms are already providing that information in parts, and with the created-at timestamp, we can know even better). With that, we only have to look at very few samples in the first place.


Not working in IE11?

Hi,
Hypernova-vue is not working on IE11, maybe because it's using the async function for rendering? Should there be a polyfill to make it compatible?
I have checked on few of your examples, they all give a JS error "expected ';'" on IE11

Hi @Vuete, I'll take a look at the issue this weekend.


DroneKit has no method for detecting command failure - do we need one?

Currently our instructions suggest that you change the mode like this:
v.mode = VehicleMode("AUTO")
v.flush() # After this, write to vehicle has been made

The problem is that after this code the write has succeeded, but the mode may not actually have been changed (and if you read back v.mode.name it may well be the old name). A better coding paradigm is to not proceed to the next step until all your conditions are met:
print " Get ready to take off"
v.mode = VehicleMode("AUTO")
v.armed= True
v.flush() # After this, write to vehicle has been made, but no guarantee change succeeded.
while not v.mode.name=='AUTO' and not v.armed==False and not api.exit:
    print " Waiting for AUTO and ARMED..."
    time.sleep(1)
print "Ready to take off"

Note: I will change our docs and examples to show the above.
There are two problems with this. Firstly it involves polling, which I object to on principle. Secondly, this will sit in a loop forever if the arming/mode change fails. This can happen because it is not possible to set modes/armed from certain states. We don't process the message that tells us if the other commands failed, so there is no way of determining what is going on.
So the question is, can/should we process command failure, and if so how?
The easiest way would probably be to make the flush() api synchronous and wait on responses to all preceding set messages (leaving exception if they fail). I wouldn't like to do it using callbacks because that is very messy code. We could just live with the code above.
@mrpollo - any ideas?
P.S. Don't know if it is possible in Python, but .NET does this quite nicely - you can make asynchronous requests and (at some point) wait on the result synchronously. This would allow us to write the code above without polling, and still return a value on failure. This is the problem with spending time in other languages, you learn about things you wish you had :-)

Hi, I agree there should be some method to identify whether a command has failed.
Another common example is arming failing. As mentioned above an easy workaround is issuing the command then polling the state until it is set, an timeout would allow you to detect this has failed but is messy also.
Are there currently any functions to handle command acknowledges?

Adding Fredia,  the Droidplanner/Tower lead,  who has been thinking about
the same thing.
On May 17, 2015 7:33 PM, "ggregory8"<EMAIL_ADDRESS>wrote:

Hi, I agree there should be some method to identify whether a command has
failed.
Another common example is arming failing. As mentioned above an easy
workaround is issuing the command then polling the state until it is set,
an timeout would allow you to detect this has failed but is messy also.
Are there currently any functions to handle command acknowledges?
—
Reply to this email directly or view it on GitHub
https://github.com/diydrones/dronekit-python/issues/114#issuecomment-102899117
.

If the command (i.e: arm) is sent to the autopilot via the COMMAND_LONG mavlink message, as done in DroneKit-Android, then the autopilot will reply with a COMMAND_ACK message to give feedback whether the command was executed.
This mechanism can be used to detect if the command successfully reached the autopilot, and the COMMAND_ACK result field can also indicate the execution result, as described by the MAV_STATUS mavlink enum.

Yes. I've been thinking it might be good to change our generic send_mavlink to being a message that has a callback, passing that response on return.
The problem would be to decide how you might make that work well with our current model of having settable python attributes - it might be that we need to have another model in this case.

I'm not familiar with the python threading model, but using the described mechanism, it's possible to implement a synchronous api in java by having the executing thread block on a lock, and have it awaken by a watchdog thread when the result is confirmed, to continue execution.
However with DroneKit-Android, I decided to go with an asynchronous api as blocking on the executing thread is a no-go on mobile, and it nicely fits the exhibited client-server interaction.

Thanks! AFAIK both models are possible on Python. Its really more a question of how we want people to be able to use the API - and move away from our dead simple but not quite effective approach. A question for @mrpollo

Has there been any progress with regards to the direction DroneKit might be taking with this?
Command failure detection is absolutely crucial be it through a having a callback for send_mavlink or having other asynchronous calls for critical applications.

@AkshayBudhiraja DroneKit-Android is in the process of adding the implementation discussed above, which will allow support for explicit callbacks.

@AkshayBudhiraja Not implemented yet on DroneKit-Python. We do consider it important an will be prioritising it in the coming weeks.

@tcr3dr I quite like the "futures" approach described here https://github.com/dronekit/dronekit-python/issues/209#issuecomment-129629149

This futures library might be worth looking into.

For those who are looking at this and want a solution for the moment, I've found that using
on_message('COMMAND_ACK')

and
on_message('STATUSTEXT')

work relatively well for detecting failure. However, as mentioned in the best practices guide, I think checking state often and explicitly, as well as polling on command success is the most reliable. That said, being able to see when there is a problem early is nice. It's also nice to be able to log the cause of failure (I send all output from both listeners to logs).
COMMAND_ACK is the MAVLink message for acknowledging the success or failure of a command, while STATUSTEXT is the MAVLink message for delivering plain text (as in, the output you see in MAVProxy). For me, on COMMAND_ACK, if the command is an arm or takeoff command and has a non-zero result (i.e. failure), I send the LAND command to immediately abort. STATUSTEXT also reports a severity which you can possibly act on. You can read about it under the section "MAV_SEVERITY" in the specification here.

Thanks @atomictom . It may well be worth updating http://python.dronekit.io/develop/best_practice.html#monitor-and-react-to-state-changes with some of those ideas ... or adding them into logging/debugging etc. I'll think on it.

@hamishwillee No problem!
On the system_status. That's a good point, and something I also monitor. But it's nice to get the STATUSTEXT for logging which includes things like PreArm failure messages since the system_status is more of a summary indicating if there are issues and how bad they are, but doesn't tell any of the extra information found in STATUSTEXT.

This might be an X-Y problem here, but I am also considering if this is necessary to avoid overrunning the ability of the autopilot to process commands.  I've added a topic to the forum as well.  If there were a mechanism for acknowledgement of a command, then would that be sufficient to allow queuing of another command and expect that it would also be processed?  Or alternatively, is there a way to examine the command queue depth and only issue a new command if the depth is <= 2  or some other heuristic?  If such were the case then my need for this issue to be solved is reduced greatly.

@waTeim Essentially there is no way to do this right in every case. The autopilot acknowledges only some commands (those sent with a commandlong) and that acknowledgement is pretty useless in that

it only tells you that something was invalid or was received - it doesn't tell you that the command succeeded or failed.
The command format is lossy, so you can't guarantee the message will arrive at the vehicle or that you will receive the acknowledgement.
There is no way to associate a message to its acknowledgement - though it is most likely that as long as you aren't sending messages too quickly (and that the script and the autopilot are the only things communicating on the network) that the current ack will match last sent.

And yes, it is also quite possible that messages will be swamped. In general commands are replaced by later commands "silently".

@hamishwillee Hey, thanks for the quick response.  Luckily I have a restricted set of commands I'm concerned about.  Velocity, Yaw, and gimbal -- well at least for now.  I can avoid worrying about item 2  for the most part since this is using localhost.  But items 1,3  and the follow-up is a problem because that's exactly what I'm worried about.  Sending commands that don't actually get executed.  In practice, it looks like if I wait long enough, then it's almost guaranteed, but waiting too long is also a problem because then the dynamics are incorrect.
Kinda OT but, earlier in this (or perhaps related threads) it was suggested you could observe vehicle state and wait for matching the command.  Is that reliable w.r.t. velocity and yaw like in the docs?  Is the autopilot capable of processing many things in parallel?

Hi @waTeim
It just so happens I'm between contracts :-) Hence the speed of reply.
So I've looked into this topic quite extensively when thinking about creating safe "synchronous" functions for setting attributes - #566 (ie that either return when command has succeeded or raise and exception on failure). The conclusion I've come to is that at the moment it is not possible to create robust functions in all cases. It is easy enough in cases like mode changes where the value changes quickly and you can read a value to detect success within a second or so, but not so good for cases like velocity control.
In the case of position, velocity and yaw this is problematic if your changes are rapid so measuring the response takes too long, or if the delta itself is small or within normal deviation for the measured value. You might be able to do it in your specific case, but I haven't been able to do "generically".

Is the autopilot capable of processing many things in parallel?

I don't know. My understanding though is that it does only 2 or three "known things" in parallel - a movement commands and a yaw or gimbal command can be done in parallel. Essentially the autopilot loop runs over incoming messages and sets the target yaw. The system then decides if it is in a state where it can yaw (ie it can only do so after the first movement command has been issued) and then does so.
Hope that helps.


add new interpret-vision package to npm publish workflows in build and release gates

Description
Add the new interpret-vision package to npm publish workflows in build and release gates.  Also adds codeowners for the new UI package.
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1615 (cd90118) into main (ad73992) will decrease coverage by 3.69%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1615      +/-   ##
==========================================
- Coverage   88.95%   85.25%   -3.70%
==========================================
  Files         111       58      -53
  Lines        5440     2937    -2503
==========================================
- Hits         4839     2504    -2335
+ Misses        601      433     -168

Flag
Coverage Δ

unittests
85.25% <ø> (-3.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ai/responsibleai/_tools/causal/causal_constants.py

.../responsibleai/_managers/counterfactual_manager.py

responsibleai/responsibleai/exceptions.py

responsibleai/responsibleai/_config/base_config.py

...ponsibleai/responsibleai/_tools/shared/__init__.py

...eai/responsibleai/databalanceanalysis/constants.py

...tools/counterfactual/dashboard_schemas/__init__.py

...ponsibleai/responsibleai/modelanalysis/__init__.py

responsibleai/responsibleai/__init__.py

responsibleai/responsibleai/_tools/__init__.py

... and 43 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Improve run to return an optional, n number of vars

This is mostly addressed through the work completed in #33. While run still exists, the approach is pointed towards using the Query DSL.


[Dropdown] autocomplete="off" does not work for dropdowns anymore

How this affects me
I'm trying to create a country selection dropdown. I just copied it from the docs, and it almost works. The only issue is that chrome autofill overlaps with the options and users cannot select the country unless they click away from the field and click on it again (this causes autofill to not appear). This is because autocomplete="off" option doesn't work anymore in chrome.
Google's position
Google has confirmed that they now ignore the autocomplete="off" option here.
The reason for that is:

The tricky part here is that somewhere along the journey of the web autocomplete=off become a default for many form fields, without any real thought being given as to whether or not that was good for users. This doesn't mean there aren't very valid cases where you don't want the browser autofilling data (e.g. on CRM systems), but by and large, we see those as the minority cases. And as a result, we started ignoring autocomplete=off for Chrome Autofill data [1].

They provided another way to disable autocomplete:

In cases where you really want to disable autofill, our suggestion at this point is to utilize the autocomplete attribute to give valid, semantic meaning to your fields. If we encounter an autocomplete attribute that we don't recognize, we won't try and fill it.
As an example, if you have an address input field in your CRM tool that you don't want Chrome to Autofill, you can give it semantic meaning that makes sense relative to what you're asking for: e.g. autocomplete="new-user-street-address".  If Chrome encounters that, it won't try and autofill the field.

What I propose
I suggest adding autocomplete="some-random-string" instead of autocomplete="off" here:
https://github.com/Semantic-Org/Semantic-UI/blob/577ae996568e355cb0141a7cce9ba07bec2ceceb/dist/components/dropdown.js#L328
Other browsers
There is an article at Mozilla developer portal that suggests using autocomplete="something-random" to disable autocomplete.
PS: Sorry if this doesn't make sense, I'm not a frontend developer : (

We are facing the same issue and don't to show chrome autofill in our drop-down search boxes.

This is still an issue for me too, by default it appears the  component adds a autocomplete="off" property.
If you simply change that "off" (in dev tools) to "anythingelse" (personally i like "nope" lol)  - the Chrome Autofill stops showing and allows the user to actually make a selection.
I like Autofill for somethings but it's ruining a handful of our dropdowns, we definitely need a way to disable it.

For a workaround we added onFocus={handleFocus} property on the dropdown component with the below code.
handleFocus = e => { e.target.setAttribute("autocomplete", "nope"); };

I've found it easier to just add it to the dropdown style like this:
<Dropdown
   name="x"
   style={{autocomplete: "off"}}
   onChange={onChange}
/>

The focus solution is not working for me.
I managed to have a fix not so bad in Vue.js:
in my vue component:
<sui-dropdown
  ref="search"
  fluid
  search
  selection
  :placeholder="placeholder"
  :options="options"
  :value="value"
  @input="emitInput" // I am using custom v-model here
  @change="removeAutocomplete"
/>

the remoteAutocomplete method:
removeAutocomplete ($event) {
  // check the default autocomplete on first change
  if ($event.target.getAttribute('autocomplete') === 'off') {
    // remove the autocomplete behaviour once it is possible
    $event.target.setAttribute('autocomplete', 'nope');
    // unset the Semantic UI search filter to display the default option
    this.$refs.search.filter = '';
  }
},

Hope this can help somebody one day...

thanks @gabrielruss it worked for me
For select box
In HTML
onFocus={handleFocus}
In Script File
handleFocus = e => { e.target.setAttribute("autocomplete", "nope"); };

+1, why not fix this in the project?

The community fork Fomantic-UI fixed this by https://github.com/fomantic/Fomantic-UI/pull/1887


Feature: JWT Authentication

Specify how JWT authentication with surrealdb functions, and subsequently implement it for the Rest and RPC drivers.
Write tests for JWT authentication

Hi,
like I said in the mail, I am happy do give support. I will start here, because JWT is something I do almost daily at the moment. At least I want to try. The documentation is not there yet, but I think I can steal something from the other implementations...

Hey,
awesome! Thanks, that means a lot to me. I assigned the issue to you. Which you fun coding. Have a great day! ^^


WIP: Add contract examples

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: chenfengjin:x: icexin:x: Tri-stonechenfengjin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Upgrade to ducktape 0.7.0

Preliminary PR.  Still looking into a failure in ./tests/kafkatest/tests/client/consumer_test.py

consumer_test.py is fixed -- the issue was a typo in a service shutdown

@cmccabe Have you run the branch builder against this? Can you link to the results?

Have you run the branch builder against this? Can you link to the results?

I ran the branch builder.  However, I identified some dependency issues in ducktape 0.7.0.  So we are going to do a ducktape 0.7.1 release which fixes the dependency issues and rebase on that.

Running branch builder on https://jenkins.confluent.io/view/All/job/system-test-kafka-branch-builder/1060/console (will replace with s3 URL as soon as it is done)

There was a test failure caused by the fact that JmxMixin#java_class_name was conflicting with the java_class_name of services that inherited from it (such as KafkaService#java_class_name).  I renamed JmxMixin#java_class_name to JmxMixin#jmx_class_name to avoid this issue.  I will re-run the tests again...

Re-running branch builder: https://jenkins.confluent.io/view/All/job/system-test-kafka-branch-builder/1061/

Tests are passing, should be ready to go.

Thanks for the patch. Merging to trunk.