• 【2019年12月8日 百天英语-Day135】【华东师范大学-林森撰写】昨日内容复习提要：昨天学习了主要学习了 ①be able to …与can的区别。②如何通过不认识的单词，猜到作者表达的含义。昨天文章如下：表示有能力做某事...
【2019年12月8日 百天英语-Day135】【华东师范大学-林森撰写】昨日内容复习提要：昨天学习了主要学习了 ①be able to …与can的区别。②如何通过不认识的单词，猜到作者表达的含义。昨天文章如下：表示有能力做某事，be able to …与can的区别今日文章解读：The Titanic turned just in time, narrowly missing the immense wall of ice which rose over 100 feet out of the water beside her. Suddenly, there was a slight trembling sound from below, and the captain went down to see what had happened. The noise had been so faint that no one thought that the ship had been damaged.“泰坦尼克”这个弯拐得及时，紧贴着高出海面100英尺的巨大的冰墙擦过去。突然，从船舱下部传来一声微颤音，船长走下船舱去查看究竟。由于这个声音非常轻，没人会想到船身已遭损坏。节选《新概念英语3 Flying cats》(1)in time，on time分别是什么意思The Titanic turned just in time…in time表示及时，用于修饰句中动作发生的时间状态Can we get to the station in time? 我们能够及时赶到车站吗?on time虽然也与时间有关，但表示的是副词“准时”，考研单词有一个叫punctual准时的，puncturally准时地。看用来形容哪部分，选择对应的词性即可。The train pulled in exactly on time.列车准时进站。在表示有能力做某事的时候，虽然can与be albe to都可以，但在使用时也有一些区别需要注意一下。(2)narrowly表示“adv. 狭窄地，勉强地”narrow我们常见的就是“狭窄的”，但还能表示勉强的，是我们不常见的。He narrowly escaped death.他九死一生。(勉强逃过了死亡)narrowly missing the immense wall of ice…miss在打游戏的时候，是玩家最讨厌的，比如在魔兽世界中，miss就是未命中的意思。未命中就是错过，差一点命中。narrowly missing就是差一点撞上，narrowly突出了船与冰之间的距离感，是非常的狭窄的错过去了。(3)so … that… 与too… to …的区别The noise had been so faint that no one thought that the ship had been damaged.so faint that … 太微弱了，以至于没有人想到…太…以至于…这样的用法，肯定会有同学会想到too… to …这个两个都表示太…以至于，但区别是so … that 表示肯定， too … to表示否定He spoke so fast that I could not follow. 他说太快，以至于我跟不上了(听不懂了)。He spoke too fast for me to follow. 他说得太快，以至于我跟不上。这两句只明显的区别在于后句，一个有not否定词，一个没有。所以too…to是形式上肯定，实际上否定的。这里大家需要注意区分一下。【明日预报】摘要：新概念英语3的第11课not guilty无罪。明天主要内容：go through穿过，通过等词的用法。还没有关注的请关注《百天英语》，每天更新，如果对《百天英语》有什么意见或建议，欢迎留言或私信我哦。
展开全文
• 在使用mongosync迁移数据过程中，目标库log提示如下错误： 发现在bulid index的时候遇到”key too larger to index”错误，并且每次报错后会重新开始创建这...


在使用mongosync迁移数据过程中，目标库log提示如下错误：

发现在bulid index的时候遇到”key too larger to index”错误，并且每次报错后会重新开始创建这个索引，再次报错，再次重建。。。。。。一直retry index bulid，于是数据同步卡在这块了

经过查询发现：

Mongo启动时有noIndexBuildRetry选项，指定此参数则不会去尝试重建索引

再次查看官当，发现：

大概意思是：

在mongoDB2.6 ,当insert或者update一个长度大于Index key length Limit的操作，mongo将会返回一个错误给客户端。而在早期的mongo版本将会操作成功

为了避免这个问题，你可以使用hash index或者索引计算值.如果你有一个现有的数据集合，那你可以禁用此行为，然后逐步解决这些索引问题，使用参数：

failIndexKeyTooLong来禁用此行为

failIndexKeyTooLong 默认为 true. 当设置为false时, 2.6 mongod 实例将提供2.4的行为

运行mongo时，如下关闭：

mongod --setParameter failIndexKeyTooLong=false

解决问题：

停止mongosync 进程

重启目标库的mongo实例 指定--setParameter failIndexKeyTooLong=false —noIndexBuildRetry 选项

开启mongosync进行增量同步（-s 去之前的synclog中找）

再次tail –f mongo.log发现刚才卡着一直retry的地方过去了 但是还是有

错误

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/27000195/viewspace-1662275/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/27000195/viewspace-1662275/
展开全文
• SVN：This client is too old to work with working copy…解决方法[OK]  这两天项目提交时候，虚拟机用SVN提交的时候，总是报如下提示： svn: This client is too old to work with working copy ‘/opt/...


SVN：This client is too old to work with working copy…解决方法[OK]

这两天项目提交时候，虚拟机用SVN提交的时候，总是报如下提示：

svn: This client is too old to work with working copy ‘/opt/gforge/www/account’. You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.

其实有时候仔细看下报错提示还是很有用的，开始没有仔细看，试着升级SVN，其实是一个错误的方向。

正确的解决办法就是按照提示中的地址有FAQ的解释，可以解决这个问题。
访问地址：

http://subversion.tigris.org/faq.html#working-copy-format-change

官网已经明确说明地址转移了：

http://subversion.apache.org/faq.html#working-copy-format-change

原文如下：

Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try
out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn’t work — it just gives the above error.

This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn’t
know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.

1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important
information might be lost, possibly causing corruption (see issue #2961, for example).

But this automatic upgrade behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can
downgrade working copies when doing so is safe:

http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc-format.py

Run that script with the “–help” option to see how to use it. As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios
and their implications.

举例，在/home/mysvn文件夹下建立好change-svn-wc-format.py文件，然后在该目录下执行：

./change-svn-wc-format.py –help

可以看到命令格式：

usage: change-svn-wc-format.py WC_PATH SVN_VERSION [--verbose] [--force] [--skip-unknown-format]
change-svn-wc-format.py –help

执行命令：

./change-svn-wc-format.py /mulu 1.x –skip-unknown-format

说明：

上面的/mulu为文件路径，1.x为SVN当前版本号，只写2位版本号即可。
如版本为1.5.4，那么这里就写1.5就可以了。至此svn up可以正常执行了。

myeclipse安装svn插件的多种方式

方法一：在线安装
1.打开HELP-&gt;MyEclipse Configuration
Center。切换到SoftWare标签页。

3.在左边栏中找到Personal Site中找到SVN展开。将Core SVNKit Library和Optional JNA
Library添加(右键Add to Profile)，Subclipse下面的Subclipse Integration for Mylyn
3.0可以不添加（特别注意，此处不要添加）。
4.在右下角窗格(Pending Changes )中点击Apply。安装重启后MyEclipse即可。

Eclipse的在线安装如下：

http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA

查看适合的版本，将url,拷贝（Location中的url），进行以下步骤：

--------打开Eclipse-->Help-->Install new Software

name :svn

Location:http://subclipse.tigris.org/update_1.12.x
安装subclipse, MyEclipse9.0 SVN插件
1、从官网下载site-1.6.10.zip文件,网址是:subclipse.tigris.org,
2、从中解压出features与 plugins文件夹，复制到E:\MyEclipse\myPlugin\svn里面，其它的*.xml文件不要。
4、(唛呆儿:这一步不确定，先不要删除)删除E:\MyEclipse\MyEclipse8.5\configuration \org.eclipse.update文件夹
5、重启myeclipse就一切正常了。[/size]
以上两种方法都尝试成功方法三:直接解压
下载SVN插件：site-1.6.10.zip
解压后将其全部文件拷贝至：D:\Program Files\Genuitec\MyEclipse 8.5\dropins（MyEclipse的安装目录）
重启MyEclipse即可出现SVN！

方法四：肯定可行的方法

1、下载最新的SVN包：
http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA
2、在你的磁盘上任意位置创建文件夹：“myplugins/svn”。名字可以任取，为了方便插件管理，建议名称为“myplugins”。
3、将解压的svn里的两个文件夹拷贝到“myplugins/svn”下。
4、复制下列java代码，修改路径并执行：
package app;
import java.io.File;
import java.util.ArrayList;
import java.util.List;
/**
* MyEclipse9 插件配置代码生成器
*
*
*/
public class PluginConfigCreator
{
public PluginConfigCreator()
{
}
public void print(String path)
{
List<String> list = getFileList(path);
if (list == null)
{
return;
}
int length = list.size();
for (int i = 0; i < length; i++)
{
String result = "";
String thePath = getFormatPath(getString(list.get(i)));
File file = new File(thePath);
if (file.isDirectory())
{
String fileName = file.getName();
if (fileName.indexOf("_") < 0)
{
print(thePath);
continue;
}
String[] filenames = fileName.split("_");
String filename1 = filenames[0];
String filename2 = filenames[1];
result = filename1 + "," + filename2 + ",file:/" + path + "/"
+ fileName + "//,4,false";
System.out.println(result);
} else if (file.isFile())
{
String fileName = file.getName();
if (fileName.indexOf("_") < 0)
{
continue;
}
int last = fileName.lastIndexOf("_");// 最后一个下划线的位置
String filename1 = fileName.substring(0, last);
String filename2 = fileName.substring(last + 1, fileName
.length() - 4);
result = filename1 + "," + filename2 + ",file:/" + path + "/"
+ fileName + ",4,false";
System.out.println(result);
}
}
}
public List<String> getFileList(String path)
{
path = getFormatPath(path);
path = path + "/";
File filePath = new File(path);
if (!filePath.isDirectory())
{
return null;
}
String[] filelist = filePath.list();
List<String> filelistFilter = new ArrayList<String>();
for (int i = 0; i < filelist.length; i++)
{
String tempfilename = getFormatPath(path + filelist[i]);
}
return filelistFilter;
}
public String getString(Object object)
{
if (object == null)
{
return "";
}
return String.valueOf(object);
}
public String getFormatPath(String path)
{
path = path.replaceAll("", "/");
path = path.replaceAll("//", "/");
return path;
}
public static void main(String[] args)
{
/*你的插件的安装目录*/
String plugin = "改成安装目录//Genuitec//svn";
new PluginConfigCreator().print(plugin);
}
}
这里需要注意的是修改成为刚才svn所在路径，建议改为绝对路径。比如d:/myplugins/svn/。。。
5、 找到“\$myeclipse_home/configuration /org.eclipse.equinox.simpleconfigurator/”，打开其中的“bundles.inf”文件，为了防止分不清是不 是我们自己后加的东西，在最后面多回几次车，然后粘贴第4步运行后的代码，保存
6、重启myeclipse


展开全文
• <div><p>…iming out <p>Split TestGetFromClientSide. Means have to also split the superclass TestFromClientSideWithCoprocessor.</p><p>该提问来源于开源项目：apache/hbase</p></div>
• SVN：This client is too old to work with working copy…解决办法 Posted on 2010/04/06 这两天项目提交时候，虚拟机用SVN提交的时候，总是报如下提示： svn: This client is too old to work with ...
SVN：This client is too old to work with working copy…解决办法
Posted on 2010/04/06

这两天项目提交时候，虚拟机用SVN提交的时候，总是报如下提示：

svn: This client is too old to work with working copy ‘/opt/gforge/www/account’. You need
to get a newer Subversion client, or to downgrade this working copy.See
http://subversion.tigris.org/faq.html#working-copy-format-change
for details.

其实有时候仔细看下报错提示还是很有用的。开始没有仔细看，试着升级SVN，其实是一个错误的方向。正确的解决办法就是按照提示中的地址有FAQ的解释，可以解决这个问题。
如下地址：

http://subversion.tigris.org/faq.html#working-copy-format-change

原文如下：

Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to
1.4.4, but it doesn’t work — it just gives the above error.
This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn’t know anything about these new features, it can at least recognize
that the working copy format has been upgraded to something higher than it can handle.
1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue
#2961, for example).
But this automatic upgrade behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:
http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc-format.py
Run that script with the “–help” option to see how to use it. As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.

以我自己的SVN为例，在/home/mysvn文件夹下建立好change-svn-wc-format.py文件，然后在该目录下执行：

./change-svn-wc-format.py –help

可以看到命令格式。

usage: change-svn-wc-format.py WC_PATH SVN_VERSION [--verbose] [--force] [--skip-unknown-format]
change-svn-wc-format.py –help

执行命令

./change-svn-wc-format.py /mulu 1.x –skip-unknown-format

上面的/mulu为文件路径，1.x为SVN当前版本号，只写2位版本号即可。
如版本为1.5.4，那么这里就写1.5就可以了。
完成，svn up可以正常执行了。


展开全文
• 昨天检出的项目，今天本想更新一下 ，结果svn直接报错，svn: This client is too old to work with working copy ‘/opt/gforge/www/account’. You needto get a newer Subversion client, or to downgrade this ...
• 这两天项目提交时候，虚拟机用SVN...svn: This client is too old to work with working copy ‘/opt/gforge/www/account’. You need to get a newer Subversion client, or to downgrade this working copy. See ht
• <div><p>…found that was causing the ...<p>Please let me know if you think storing the reference bases of one contig is too much memory.</p><p>该提问来源于开源项目：broadinstitute/picard</p></div>
• is too old (format 10) to work with client version '1.8.0 (r1490375)' (expects format 31). You need to upgrade the working copy first. 解决办法： svn原文声明： Sometimes the working copy ...
• Too… to… 太……不能……用法透视该句用来表示某情况过于……，以致于不能……，虽然句中没有”no”，却含有一个否定的意思。支持范例 The bottle is too small to hold so much water. 瓶子太小，不能装那么多水...
• ESP_IDLE_TIMEOUT is set to 30 minutes by default in the CQD too. <p>Added test in core/TESTRTS to test ESP_IDLE_TIMEOUT</p><p>该提问来源于开源项目：apache/trafodion</p></div>
• Control Panel Security Account Allow/Block List Block List If yoiur address is here Remove it.
• <div><p>This is but a small band-aid, but at least display a message when ... exif data added by darktable are too big and discarded.</p><p>该提问来源于开源项目：darktable-org/darktable</p></div>
• <div><p>之前提交的lambda方法引用只能处理单个参数,为了支持多参数方法引用，参考了一下scala的Function相关实现，感觉实现方式上不太优雅,从使用的角度感觉也不是特别友好，...
• Description Mr Zhou准备了一块nm的巧克力想分给301的小(da)朋友们，强迫症的他想沿着纹路掰成恰好nm个11的小块。 每次他只能拿起一块巧克力，并沿着纹路掰断，这称为一次操作（比如一块34的，一次操作可以掰成两块...
• <p>too many call _drawZoomedElement leads to memory, fix it by add condition. </li><li> <p>fix disableCallback, because params is element, but not event. </li><li> <p><strong>What is the new behavior ...
• <div><p>…sagePack#packString <p>Fix https://github.com/msgpack/msgpack-java/issues/292</p><p>该提问来源于开源项目：msgpack/msgpack-java</p></div>
• https://community.home-assistant.io/t/listen-to-attribute-state-change-seems-to-trigger-too-often/26110?u=registax</p><p>该提问来源于开源项目：AppDaemon/appdaemon</p></div>
• s visibility with a search engine make them relevant to accessibility? Should we start including more articles on this topic? If so, what topics should we start with? Am I asking too many questions?...
• <div><p>…n branch-2, branch-2.3, and master</p><p>该提问来源于开源项目：apache/hbase</p></div>
• Too few arguments to build the query string' thrown in /…/system/modules/core/library/Contao/Database/Statement.php on line 316</p> <h1>0 /…/system/modules/core/library/Contao/Database/Statement...
• <p>This function caches information about specific filenames, so you only need to call clearstatcache() if you are performing multiple operations on the same filename and require the information about...

...