'hg status' failed with code 1:'*** failed to import extension hgext.hgsubversion from /Applications/SourceTree.app/Contents/Resources/mercurial_local/hgext/hgsubversion: 'module' object has no attribute 'canonpath'
** Unknown exception encountered with possibly-broken third-party extension sourcetree_auth
** which supports versions unknown of Mercurial.
** Please disable sourcetree_auth and try your action again.
** If that fixes the bug please report it to the extension author.
** Python 2.7.6 (default, Sep 9 2014, 15:04:36) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)]
** Mercurial Distributed SCM (version 3.2.3)
** Extensions …我有一个运行ZFS的Solaris 11.2服务器,具有以下配置;
6x 4TB HDDs in raidz2 (approx 14TB usable)
16GB RAM (ECC)
E5-2670 (16 cores)
No ARC or L2ARC
No zfs settings tweaks
读取和写入性能在两者iozone和现实世界中都非常快速,超过了700MB/sec顺序.
但是,元数据读取速度非常慢.例如,我有一个包含大约130k文件的mount,find在这个目录上运行大约需要5分钟.作为一种解决方法,我必须使用find > files.txt然后grep over(它输出一个15MB的文件).
我的印象是元数据应该存储在LRU中(在RAM中)并且它永远不会从LRU中逐出,因此find应该快速完成.或者至少,这是我期望的行为.
是否有任何ZFS调整或我可以考虑的其他更改可以提高严重依赖元数据的工具的性能(例如find)？例如,我是否可以强制元数据永远不会从RAM中逐出？
以下是ARC统计数据;
zfs:0:arcstats:buf_size 79301640
zfs:0:arcstats:c 773376320
zfs:0:arcstats:c_max 16054530048
zfs:0:arcstats:c_min 67108864
zfs:0:arcstats:class misc
zfs:0:arcstats:crtime 120.399677
zfs:0:arcstats:data_size 431609856
zfs:0:arcstats:deleted 412089
zfs:0:arcstats:demand_data_hits 523939
zfs:0:arcstats:demand_data_misses 10351
zfs:0:arcstats:demand_metadata_hits 2334880
zfs:0:arcstats:demand_metadata_misses 423667
zfs:0:arcstats:evict_l2_cached 0
zfs:0:arcstats:evict_l2_eligible 0
zfs:0:arcstats:evict_l2_ineligible 37581707264
zfs:0:arcstats:evict_prefetch 10717167616
zfs:0:arcstats:evicted_mfu …很多人都在SO上遇到过这个问题,但几乎所有答案都没用.
Traceback (most recent call last):
File "/venv/local/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 91, in inner_run
self.validate(display_num_errors=True)
File "/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 266, in validate
num_errors = get_validation_errors(s, app)
File "/venv/local/lib/python2.7/site-packages/django/core/management/validation.py", line 103, in get_validation_errors
connection.validation.validate_field(e, opts, f)
File "/venv/local/lib/python2.7/site-packages/django/db/
backends/mysql/validation.py", line 14, in validate_field
db_version = self.connection.get_server_version()
File "/venv/local/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 415, in get_server_version
self.cursor().close()
File "/venv/local/lib/python2.7/site-packages/django/db/backends/__init__.py", line 306, in cursor
cursor = self.make_debug_cursor(self._cursor())
File "/venv/local/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 387, in _cursor
self.connection = Database.connect(**kwargs)
File "/venv/local/lib/python2.7/site-packages/MySQLdb/__init__.py", line 81, in Connect
return Connection(*args, **kwargs)
File "/venv/local/lib/python2.7/site-packages/MySQLdb/connections.py", line 193, …我正在尝试将OTP/2FA支持添加到OAuth2中,但经过对RFC6749的大量阅读后,仍然不清楚如何在不违反规范的情况下干净地添加OTP/2FA.
虽然可以在authorize对话框流中添加OTP/2FA条目,但是没有将其添加到其中的规定token.例如,public具有Resource owner password-based特权的客户端应用程序可能希望在请求新的时直接提供令牌access_token,而不必嵌入HTML对话框.
因此,我的问题是;
RFC是否允许自定义grant_type？它应该用于提供2FA/OTP功能吗？
RFC是否允许现有的其他属性grant_type？例如,grant_type=token&otp_code=1234(RFC不清楚是否允许在grant_type规范中使用其他属性)
OTP功能应该放在标题中吗？这是Github 使用的方法,但它感觉非常丑陋/ hacky.
还有其他方法我忽略了吗？
先感谢您
出于某种原因,我无法从Ubuntu 14.04计算机SSH到Cisco CSR1000v路由器.
我们的思科固件是;
Cisco IOS XE Software, Version 03.12.00.S - Standard Support Release
Cisco IOS Software, CSR1000V Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(2)S, RELEASE SOFTWARE (fc2)
显示的服务器错误是;
%SSH-3-DH_RANGE_FAIL: Client DH key range mismatch with maximum configured DH key on server
显示的客户端错误是;
$ ssh -v admin@172.16.3.253
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 172.16.3.253 [172.16.3.253] port 22.
debug1: Connection established.
debug1: identity file /home/admin/.ssh/id_rsa type 1
debug1: …Vagrant在对网络进行一些更改后拒绝启动,我得到了以下内容;
$ vagrant up
default: Warning: Connection timeout. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
我尝试通过重新启动服务(失败)来解决这个问题,然后导致了这个问题.
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and …