Excellent, thanks for the input and I'll get on to those changes.

I do have couple of questions:
- What do you mean by use more numbers, do you mean something like "with 9 years of testing experience.." or "I coded in 2 languages whilst at Makers..."?
- I have a work history section but what should the "Experience" section cover exactly? Anything that touches coding and the skills I list above in the CV or is it the what I did in my previous role type of stuff?

Thanks

Meads


The only thing I would suggest would be to change the imported name to make it clear that you are not relying on the side-effect of the reference path inclusion of bluebird.d.ts.  That is, instead of `Promise`, you could call it `BluePromise` or something like that.  Ideally, bluebird.d.ts (and others like it) would be changed so that all of its symbols are declared within a module scope, so that nothing leaks into the global namespace.


![51ad344e48d311e390cd22000a1f90d7_8 1](https://cloud.githubusercontent.com/assets/8668962/7280032/d9268730-e928-11e4-892b-66ff4ec3ff50.jpg)


I actually like this approach better. The Shelf has a property `books` that is an array of Book objects. This lets a book object be more than just a key-value pair.


СУКА


Hi @tchoulihan,

No, I'm just using the most updated branch to try some things of the record. Nothing really to be re-used though.

Sorry ;)


This is really broken:
1. The `str().find()` test is broken; the `find()` method will return -1 if it can not find the string - which will evaluate to `True`.
2. The data equals `["TIME_STEP"]` - no reason to use the `find()` in the first place.


/home/revenant/springlobby/src/gui/hosting/votepanel.cpp:2:23: fatal error: wx\colour.h: No such file or directory
 #include <wx\colour.h>


Similarly, Library should have it's own constructor function, and should be an object that has a `shelves` property, which would be an array of Shelf objects.


Don want this project anymore


step | pass?
--- | ---
canary site online |  :white_check_mark:
authenticated with GitHub | :white_check_mark:
no carry over reviews |  :white_check_mark:
created request |  :white_check_mark:
Uploaded pdf |  :white_check_mark:
Found issues in GitHub |  :white_check_mark:


That will allow you to instantiate a Book object, and then add that object itself to the array of `books` in a Shelf for a particular Library.


Looking good :+1:


@dg I don't like this patch nowadays :(

I suggest revert it.

Please, see https://github.com/nette/database/issues/15#issuecomment-95263285

Sorry.


Yes, I wanted you to test-drive first, as both noop color sets a rather similar to me when looking at the samples you provided.


> @nicost <https://github.com/nicost> ... this does not need to be done.
> On derived classes you can be less specific, what is not allowed is to
> be more specific than the superclass.
>
Funny thing is that Netbeans does not like it, it claims that the method
does not override a supertype with the original function parameters.  I
am not set up to compile outside of Netbeans, and do not know if this is
a Netbeans-specific problem or depends on the Java compiler. Is it OK to
leave it at the more specific signature for now?

> For return values, it is exactly the other way around. You can return
> more specific values.
>
Yes, Netbeans does take that.  I'll revert to JMenuItem.


Avoid the `str.find()` method; the test could instead be:

1. `self.assertTrue( isinstance( data[0] , datetime.datetime ))`
2. `self.assertEqual( data[0] , datetime.datetime( ... ))`


Well, even though the rgba values will be zero when calling to nil, it breaks when trying to insert a nil value to the colorsWithAlpha array.
"""
[colorsWithAlpha addObject:[backgroundColor copy]];
"""


According to the `Linear.V3` documentation, there is evidentially no good way to extract the individual numbers from a vector without lenses. This makes me sad.


Lgtm +1


maybe `air.build.heapsize`


Ok, removed


It is possible that this can be done more elegantly with Dyadic Functile Hyper-Arrows.


Fixed


Maybe this should really be git://git.apache.org/incubator-groovy.git ?


Hi Ying,

Your profile is stellar!  Our client would like to speak with you......we should chat.

The reason for this note is to introduce myself to you, and to make you aware of a senior role we have to fill. Our client is a technology company that successfully applies disciplined, process-driven investment strategies based on statistical models developed using rigorous mathematical analysis. They are recruiting for a senior level software engineer to build proprietary algorithmic research systems capable of executing extremely high levels of computation and will detect anomalies in massive datasets i.e. Big Data. Candidates will likely hold a degree in Computer Science or Electrical Engineering, however all backgrounds will be considered, and experience building highly available systems in an industrial setting.

Would you like to learn more about this opportunity? Kindly let me know your thoughts.

Brian McNeill
Alpha Advisors
(914) 584-9471
bmcneill@alphaadvisorsllc.com
http://www.alphaadvisorsllc.com/
http://www.linkedin.com/pub/brian-mcneill/43/a4b/343/en


Fix: `toolbox_blocks` is transformed to `toolbox`, not `toolboxBlocks`.


Hmm, it also looks like `lock()` should be throwing `FileLockInterruptionException` rather than `ClosedByInterruptException` if interrupted.


По описанию метода:
1. Не хватает расшифровки констрейнтов (что значат, для чего используются)
2. Не описан констрейнт "M (Masks)"

По методу:
Нет описания ограничений и минусов метода


I will try to get hold of GK1 to see what it does. Are you guys able to offline disassemble some of the older DOS games? My DOS copy of KQ6 looks like the executable is compressed.


MarkdownDocs (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1641 of 1641 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


The .pdf file in the outputGraphics folder does look fine though.


I'm trying to edit this code. Where do I edit this so I can fix ImageJ for several people who are trying to use Java3D?


recognize txt as forth source


##Hello World##


package ua.kh.kml.yanzhula.test1;

public class Class1 {

	public static void  main (String[] args ){
		int x ;
		try{
			x=System.in.read();
			char c =(char)x ;
			System.out.println("Код ошибки"+ c+ "=" + x );
		}
		catch (java.io.IOException e )	{
			System.err.println("Ошибка ввода " + e);

		}
		}
	}
package ua.kh.kml.yanzhula.test1;

public class ClassWork {

	public static void main(String[] args) {
		// TODO Auto-generated method stub

		String strInt= "123"; String strDouble= "123.456";
		int x; double y;
		x=Integer.parseInt(strInt);
		y =Double.parseDouble(strDouble);
		System.out.println("x"+ x);
		System.out.println("y"+ y);
		strInt= String.valueOf(x+1);
		strDouble= String.valueOf(y+1);
		System.out.println("strInt="+ strInt);
		System.out.println("strDouble=" + strDouble);
		String str;
		str= "num="+ 345;
		System.out.println(str);

	}

}

package ua.kh.kml.yanzhula.test1;

public class task1_5v2 {

	public static void main(String[] args) {
		// TODO Auto-generated method stub

		for( int i=0; i<args.length; i++)

			System.out.println(args[i]);
		int Summ=0;

		for( int i=0; i<args.length; i++)
		{
			Summ += Integer.parseInt(args[i]);
		}
		System.out.println("Summa= " + Summ);

		int Umn=1;
		for( int j=0; j<args.length; j++)
		{
			 Umn*= Integer.parseInt(args[j]);
		}
		System.out.println("Proizv= " + Umn);

	}

}
package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class Task1_6_3 {
	public static void main(String []args )
	{
		System.out.println("->n");
		Scanner scan= new Scanner(System.in);

		int mass[]= new int [5];
		for (int i = 0; i < mass.length; i++) {
			mass[i]= scan.nextInt();
			}

		for (int i = 0; i < mass.length; i++) {
			if( mass[i]%3==0 || mass[i]%9==0)
			{
				System.out.println("Делиться на 3 или на 9:-- "+mass[i]);
			}

	}
scan.close();
}
}
package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class task1_6_4 {

	public static void main(String[] args) {
		// TODO Auto-generated method stub
		System.out.println("->n");
		Scanner scan= new Scanner(System.in);

		int mass[]= new int [5];
		for (int i = 0; i < mass.length; i++) {
			mass[i]= scan.nextInt();
			}

		for (int i = 0; i < mass.length; i++) {
			if( mass[i]%5 == 0  && mass[i]%7 == 0)
			{
				System.out.println("Делиться на 5 и на 7:-- "+mass[i]);
			}
scan.close();
	}
	}
}

package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class task1_6_5 {
	public static void main(String[] args)
	{
		/*System.out.println("->n");
		Scanner scan= new Scanner(System.in);

		String mass[]= new String [5];

		for (int i = 0; i < mass.length; i++) {
			mass[i]= scan.next();
			}*/

  for(int i=100; i<1000; i++)
  {
	  String s= Integer.toString(i);

	  if(s.charAt(0)!= s.charAt(1)&s.charAt(0) != s.charAt(2)& s.charAt(1)!= s.charAt(2) )
			  System.out.println("_____" +s);

	}

}
	}

package ua.kh.kml.yanzhula.test1;

public class task1_6_6 {

	public static void main(String[] args) {
		// TODO Auto-generated method stub

		for(int i=1000; i<10000; i++){
			String s=Integer.toString(i);
			if((int)(s.charAt(0))+(int)(s.charAt(1))==(int)(s.charAt(2))+(int)(s.charAt(3)))
				System.out.println(s);
		}
	}

}
package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class task1_6 {
public static void main(String[]args)

 	{

	System.out.println("->n");
	Scanner scan= new Scanner(System.in);

	int mass[]= new int [5];
	for (int i = 0; i < mass.length; i++) {
		mass[i]= scan.nextInt();
		}

	for (int i = 0; i < mass.length; i++) {
		if( mass[i]%2==0 )
		{
			System.out.println("Четное "+mass[i]);
		}
		else
			if(mass[i]%2 != 0 )
			{  System.out.println("нечеткое "+mass[i]);}

	}
	scan.close();

	}

}
package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class task1_6 {
public static void main(String[]args)

 	{

	System.out.println("->n");
	Scanner scan= new Scanner(System.in);

	int mass[]= new int [5];
	for (int i = 0; i < mass.length; i++) {
		mass[i]= scan.nextInt();
		}

	for (int i = 0; i < mass.length; i++) {
		if( mass[i]%2==0 )
		{
			System.out.println("Четное "+mass[i]);
		}
		else
			if(mass[i]%2 != 0 )
			{  System.out.println("нечеткое "+mass[i]);}

	}
	scan.close();

	}

}
package ua.kh.kml.yanzhula.test1;

public class task1 {
	public static void main( String[] args){
		//TODO Auto-generated method stub
		float x=0, y=0;
		x=(float)0.3f+0.4f;
		y=0.3f+0.4f;
		System.out.println(x==y);

	}

}

package ua.kh.kml.yanzhula.test1;
import java.util.Scanner;

public class task1Pass {
	public static void main(String[] args){
		System.out.println("-> Pass and click -> ENTER");
		Scanner scan= new Scanner(System.in);
		String pas=scan.next();
		scan.close();
		if(pas.equals("stasik1205"))
		{
			System.out.println("Welcome)!");
		}
		else {System.out.println("Error pass! ");

		}
	}

}package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class task6_1 {
	public static void main(String [] args){

		System.out.println("->n");
		Scanner scan= new Scanner(System.in);

		int mass[]= new int [5];
		for (int i = 0; i < mass.length; i++)
		{mass[i]= scan.nextInt();}

		int MAX=-999999;
		int MIN= 999999;

		for (int i = 0; i < mass.length; i++) {
			if(mass[i]<MIN)
				{ MIN=mass[i];}

		for(int j=0;j<mass.length; j++ )
			if (mass[j]>MAX)
				{MAX=mass[i];}

		}
		System.out.println("Минимум"+ MIN);
		System.out.println("Максимум"+ MAX);
	}

}
package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;
import java.util.Random;

public class TaskOne {
	public static void main (String[]args){

		Scanner scan = new Scanner(System.in);
		String number = scan.next();
		int mass [] ;
			for(int i=args.length-1;i>=0;i--)

		//mass=number.toString();
	//	Random rand  = new Random();

		System.out.println();

		scan.close();
	}

}

package ua.kh.kml.yanzhula.test1;

import java.util.Scanner;

public class TaskOne2 {

	public static void main(String []args ){

		  for (int i = 0; i < args.length; i++)
			     System.out.println("args[" + i +"]=" +args[i]);

		  System.out.println("____________");
		  for( int j=args.length-1; j > -1; j--)
			  System.out.println("args[" + j +"]=" +args[j]);

	}
}


Or just use `\date`.


iya.,
jalanji.,


Thanks for the input! I'll look at the issues thoroughly tomorrow. Some of the code is left over from the previous implementation and I didn't have time to clean it up yet.
One thing I'm still not sure about is what kind of requests should send `clientId` (apart from the token request)?


One inv message for every block? Can't the pushmessage be moved outside of the loop?


`ASP.NEt` --> `ASP.NET`


Instead of saying it's "complicated" just say "follow these steps" or similar.


Move to C++11, list initialization is usually more predictable than () initialization and boost::shared_ptr should be replaced with std::shared_ptr when we can do it.


You can use unp.exe to decompress the earlier interpreters.
http://unp.bencastricum.nl/


AND `SourceEntry`=@TANK must be added


LGTM


Did you have issues getting django_compressor to work with this file?


@thovden  I'm curious how you're planning to implement full-text search.

We (team formerly known as chronicle team) have discussed modifying the Places database to store a (limited) amount of full text, but a remote service (modulo privacy, legal, and security concerns) seems like a better solution: mobile-friendly, allows search to span multiple devices.

Let's keep in touch about this, there might be a good medium-term opportunity to productize full-text search in some form.


I made an update mentioning both the web front-end and the git link.
But don't hesitate to change if you think that's not clear.


I'll make these changes myself :)


That's a good point. You can solve it whichever way you want. I did this because it was the first thing I thought of and I wanted to get to the Travis stuff quickly.


FYI, `ember new project-name` is going to create a new git repo for you


@cgwalters Point taken, but then that is an upstream Vagrant issue which I recommend you file over there. Please cc me if you do!


Sorry this is a big chunk of stuff at once.

This needs pretty heavy testing and might need some changes to Nginx configs related to /public folder.


Часть багов мы все же можем найти, техника не гарантирует покрытия для комбинаций размерностью больше 2.
Технику можно применить на любом этапе, главное понимать, что она не гарантирует 100% покрытия и рассматривает только узкую часть возможных ошибок (связанных с комбинацией пар параметров)


looks good, merged!


@plugz just tested and it works for me.
Tested RGB panel (which was not working before) and traditional lights with dimmers and LTP channels.

Do you have a test project that shows issues ?


Thank you for the fixes @rryan! Shall I sign the contributor agreement?


This chunk of code is duplicate with the one below. Do you think you can make it more DRY?


I would actually love it if clicking on `Download` on `git-scm.com` would download the installer of the matching architecture by default. Anybody using a 32-bit browser on 64-bit Windows (and that is really the only -- rare! -- case against automatic downloads) would download a 32-bit Git. Big deal.


Yo guys, run "migrate" at the root folder to reflect schema change!


develop (lefticus) - i386-Windows-8.1-VisualStudio-12: OK (339 of 340 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.71%25-yellow.svg)


not sure i understand. this is just text, no encoding here.


Bah, thank you for catching this.


https://github.com/aspnet/Home/commit/78a600ae831af2a3d9925cdaf8727febf6bb0d44 :smile:


Nested a <1 and a >0 along with conditional setting backgroundColor = nil sure seem like a magic when we read it in the next month. What about make it more verbose like `BOOL alphaBackgroundColor = a < 1` to show your intention there.


@noobtrader15 What exactly are you trying to accomplish? Please report a new issue (or commenting on existing issue, if there is one), and give [specific details](http://imagej.net/Bug_reporting_best_practices) of what goes wrong for you and these other "several people."

And see also https://github.com/imagej/imagej/issues/120


A lot of not relevant text here. please  use commit -i and select what you commit (2)


В условиях, когда количество значений у параметров практически одинаково, увеличение числа значений для одного из них (или небольшой части) будет приводить к резкому снижению эффективности техники: за счет того, что сочетания будут генерироваться для добавленных значений с любыми значениями других параметров, число кейсов будет приближаться к простому перебору.
Поэтому сопоставимое число значений у всех параметров системы является одним из условий успешного применения техники.


Thanks Brook. I will take a look in a bit. I'm working on my CSS project
now :)

On Wed, Apr 22, 2015 at 9:55 AM, Brook Riggio <notifications@github.com>
wrote:

> That will allow you to instantiate a Book object, and then add that object
> itself to the array of books in a Shelf for a particular Library.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kcomey/CodeFellows2/commit/2bc3937a597e1072b0e263b898a752b7d09ed890#commitcomment-10851517>
> .
>


That is perhaps a better solution to provide a fix both problems. But is is still a behavior that is inconsistent with the addParameter methods, and I believe it is not as intuitive.
I am instead considering implementing two different binding strategies.

SkipExistingParamtersStrategy and OverwriteExistingParametersStrategy. Then you could do something like.
``` java
insQuery.setBindingStrategy(new IgnoreExistingParametersStrategy()).bind(pojo)
```

Default should be to use the overwrite-strategy.


Tudo certinho. Pode fechar!


`final String line`


you don't need to set the version explicitly on release. It is even recommended to avoid it (it does not add any benefit, but it increases the lieklyhood of mistakes when forgetting to update it for next versions)


Just make sure a strings that should get translated are within a qsTr(""), I'll deal with getting them translated then.
So instead of e.g. `currentStatus.text = "Done."     // TODO: use translation` just write `currentStatus.text = qsTr("Done.")`

Branch names, hmm..., how about just "mac"?


et moi qui prenait une erreur du genre
Warning (512): Method MediaHelper::image does not exist [CORE/Cake/View/Helper.php, line 192]
eh bah voilà le probléme , vous avez rayé la méthode entiere du code


this is different. this is text -> normal base64, the one in the emitter is number->base64VLQ which takes care of sign.. etc.


fix #839


@wkennington mh ok I'm trying glib-networking 2.44.


I can confirm. Fixed! Thanks!


I confuse that crash is on my code (those reversed order confused me). I have put the comment on the codes.

Another suggestion is to use git rebase to clean your history before submit a PR
i.e. squash these 2 commits (Added support for transparent background views. and Fixed crash when backgroundColor is nil.) to avoid confusion original code shouldn't break by the PR even you fix it in the next commit, this can still be headache in the future.


Salut,

A mon avis il y a un piège ici : Sporeling Ooze Sac
ooze = suinter (http://www.wordreference.com/enfr/ooze)

Je dirais Sac ou Poche suintante de sporeling, c'est un item qu'on drope en tuant un sporeling.


@rbreitenwischer This information is super helpful. Do you have another link available with relevant content to share on this topic?


По Soap Testing: можешь добавить описание, чем руководствоваться при построении многошагового теста (по какому принципу подбираем параметры, какие ошибки надеемся найти)?


kerja sendiriji itu kak cuma pke laptopna isna z upload fileku

2015-04-22 23:23 GMT+08:00 tuxkids <notifications@github.com>:

> copas kah ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/faisalrefleks/pemrograman-berorientasi-objek/commit/d3ac4914f6e073511b0bc03fd52647fabd58d8e2#commitcomment-10849504>
> .
>


Thanks fixed in the main repo !!


This adds the new settings but don't remove the old one. I kept it for backward compatibility if needed. Though if we need to remove it, let me know.


I'm not sure about this commit, atleast the versioning


盲点‥！

Sent from iPhone

On Wednesday, April 22, 2015, Linda_pp <notifications@github.com> wrote:

> @ujihisa <https://github.com/ujihisa>
>
> 今更こういうこと言うのもアレですけれど，全部書き直すぐらいなら #207
> <https://github.com/vim-jp/vital.vim/issues/207> の時点で書き換えやってくださいよ…
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/vim-jp/vital.vim/commit/2ba6456f8bb0d7d3b68c87bd379e78a151c40657#commitcomment-10851025>
> .
>


@norine-badr


Also looks like you forgot to do `git add appendices/changelog.tex`.


This commit was wrongly attributed to me. The original author is @plribeiro3000


They don't have any contribution guidelines, so I just kind of went with what we use. These are breaking changes that aren't backwards compatible, so I did a major bump.


fixes #13


@bladeSk, in the case of the REST lib, I believe we only use `clientId` for auth. I'll ask @paddybyers to confirm


updated header


Looks pretty good! I'll leave it open so you guys can keep pushing commits to it and I'll close it at the end of class


rax retry tests


Not "calculateTotalLength"?


MarkdownDocs (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1647 of 1647 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


advi*s*ed


Ha. No worries man. The important is that it works now. =)


q: in front of what? :-)


Addressed in ae5d36a6855a0811982e5e4f72086983637b0850


r+


@markus101 Won't the pidpath be lost if restarted via NzbDrone.Update?


Good idea, will do that tomorrow. Thanks!

On 22 april 2015 18:50:34 CEST, Matt Frantz <notifications@github.com> wrote:
>The only thing I would suggest would be to change the imported name to
>make it clear that you are not relying on the side-effect of the
>reference path inclusion of bluebird.d.ts.  That is, instead of
>`Promise`, you could call it `BluePromise` or something like that.
>Ideally, bluebird.d.ts (and others like it) would be changed so that
>all of its symbols are declared within a module scope, so that nothing
>leaks into the global namespace.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/basarat/typescript-node/commit/467b8b0a235de9ac9fa6b31ee4a5a001d3bdc654#commitcomment-10851437


It would be good to  put a comment here that explains what this does, especially around how values can be dropped (?)


Don't you need to change the function signature provided for unzip too?

unzip_.unzip(*arrays)   <- should be ([*arrays])


Two questions: should we always use strict mode, and is this the right way to add it to exported modules?


cool!


Cái đó thì xem lại tuốt ở trên, ở bước refine Camera :v
nó có một câu là cv::detail::waveCorrect(rmats,
cv::detail::WAVE_CORRECT_HORIZ);
Hiển nhiên mode để tính rotation của camera của mình là theo đường chân
trời theo chiều ngang :v
void waveCorrect(vector<Mat> &rmats, WaveCorrectKind kind)
{
    LOGLN("Wave correcting...");
#if ENABLE_LOG
    int64 t = getTickCount();
#endif
    if (rmats.size() <= 1)
    {
        LOGLN("Wave correcting, time: " << ((getTickCount() - t) /
getTickFrequency()) << " sec");
        return;
    }

    Mat moment = Mat::zeros(3, 3, CV_32F);
    for (size_t i = 0; i < rmats.size(); ++i)
    {
        Mat col = rmats[i].col(0);
        moment += col * col.t();
    }
    Mat eigen_vals, eigen_vecs;
    eigen(moment, eigen_vals, eigen_vecs);

    Mat rg1;
    if (kind == WAVE_CORRECT_HORIZ)
        rg1 = eigen_vecs.row(2).t();
    else if (kind == WAVE_CORRECT_VERT)
        rg1 = eigen_vecs.row(0).t();
    else
        CV_Error(CV_StsBadArg, "unsupported kind of wave correction");

    Mat img_k = Mat::zeros(3, 1, CV_32F);
    for (size_t i = 0; i < rmats.size(); ++i)
        img_k += rmats[i].col(2);
    Mat rg0 = rg1.cross(img_k);
    double rg0_norm = norm(rg0);

    if( rg0_norm <= DBL_MIN )
    {
        return;
    }

    rg0 /= rg0_norm;

    Mat rg2 = rg0.cross(rg1);

    double conf = 0;
    if (kind == WAVE_CORRECT_HORIZ)
    {
        for (size_t i = 0; i < rmats.size(); ++i)
            conf += rg0.dot(rmats[i].col(0));
        if (conf < 0)
        {
            rg0 *= -1;
            rg1 *= -1;
        }
    }
    else if (kind == WAVE_CORRECT_VERT)
    {
        for (size_t i = 0; i < rmats.size(); ++i)
            conf -= rg1.dot(rmats[i].col(0));
        if (conf < 0)
        {
            rg0 *= -1;
            rg1 *= -1;
        }
    }

    Mat R = Mat::zeros(3, 3, CV_32F);
    Mat tmp = R.row(0);
    Mat(rg0.t()).copyTo(tmp);
    tmp = R.row(1);
    Mat(rg1.t()).copyTo(tmp);
    tmp = R.row(2);
    Mat(rg2.t()).copyTo(tmp);

    for (size_t i = 0; i < rmats.size(); ++i)
        rmats[i] = R * rmats[i];

    LOGLN("Wave correcting, time: " << ((getTickCount() - t) /
getTickFrequency()) << " sec");
}

Đến bước blend
warper->warp(img[img_idx], K, cameras[img_idx].R, cv::INTER_LINEAR,
                cv::BORDER_REFLECT, img_warped);
Ảnh của mình là theo chiều dọc, lại bắt warp theo camera chiều ngang
Point SphericalWarper::warp(const Mat &src, const Mat &K, const Mat &R, int
interp_mode, int border_mode,
                               Mat &dst)
{
    Rect dst_roi = buildMaps(src.size(), K, R, d_xmap_, d_ymap_);
    dst.create(dst_roi.height + 1, dst_roi.width + 1, src.type());
    remap(src, dst, d_xmap_, d_ymap_, interp_mode, border_mode);
    return dst_roi.tl();
}

Rect CylindricalWarper::buildMaps(Size src_size, const Mat &K, const Mat
&R, Mat &xmap, Mat &ymap)
{
    projector_.setCameraParams(K, R);

    Point dst_tl, dst_br;
    detectResultRoi(src_size, dst_tl, dst_br);

    buildWarpCylindricalMaps(src_size, Rect(dst_tl, Point(dst_br.x + 1,
dst_br.y + 1)),
                                  K, R, projector_.scale, xmap, ymap);

    return Rect(dst_tl, dst_br);
}

Chỗ mà em phóng to nó thuộc thư viện imgproc/imgwarp.cpp và dài loằng
ngoằng. Nhưng đại loại là làm bài toán nội suy (để tính lại tỉ lệ trong tấm
ảnh) và ngoại suy (fill các điểm ảnh để đảm bảo khung ảnh cuối cùng vẫn là
hình chữ nhật.
Điểm đặt camera ban đầu sai -> bài toán nội suy và ngoại suy sai số lớn ->
dễ lỗi.
Chi tiết bài toán nội suy và ngoại suy thì nó là cả mấy chương liền môn MAN
của lớp CS nên em ko thể giải thích chi  tiết được đâu ạ @@

Nguyễn Văn Khôi - Lớp CS0801 - SE61174

Vào 23:09 Ngày 22 tháng 04 năm 2015, Manh Thiep Nguyen <
notifications@github.com> đã viết:

> Anh đồng ý với chỗ chú mô tả việc ghép theo chiều dọc.
> Chỗ nào cho thấy: "=> dễ gây tràn bộ nhớ và tốn thời gian xử lý ko cần
> thiết." ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/iDoraemon/BiBo-Kit---Panorama/commit/672eb450ff9769ea3c95f12c237f5514fa74b06d#commitcomment-10850634>
> .
>


MarkdownDocs (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg)


КурсовойПроект/project.txt

Целых две разных таблицы - это круто!
Но у меня такой вопрос - точно вся таблица и шаги по ней - это один кейс?


:muscle::dog:


This should be mentioned in the docs somewhere, too, including explaining what fields the policy has


> I believe we only use clientId for auth

It is also the `clientId` used when doing a `Presence.enter()` (ie when no `clientId` is passed explicitly in `enter()`)


MarkdownDocs (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1647 of 1647 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


I'd rather note here the fact that it has been automatically generated. Same for the file phpDoc.


Задание 7


КурсовойПроект/project.txt

Можно ли планировать такое тестирование? Когда это может потребоваться?


But this is a REST lib only.


I'm curious why this was needed?  I know it is what Adobe does, but I have use cases for other types of lookups and was going to suggest to Adobe that they accept it in any lookup.


КурсовойПроект/project.txt

Всегда ли исследовательское тестирование не зависит от требований?


ran on iPhone 6, works!


to access jobs for the specific client use:
clientList.get(clientIndex).getJobList().size()


Not a fan. I will leave others have a look and comment!


Can you please ignore the eclipse settings file in the push. This will mess up some of the settings I have.


I would prefer we hide unused sensors (as done in the firmware)


Sorry mix up comments, it should be:
added line: 39 - int loop = content.length();
update line 40 to this : for (int i = 0; i < loop; i++) {


hee..tidak ada kk. tapi sudah mi sa rubah. ada miii.


Hi James,

Here's my assignment.  The output is correct, but the server.js file feels a little messy.  I'm sure as things get more complex we'll export modules to our server instead of performing logic there, but is this what you were expecting for this project?

Thanks for the help!


КурсовойПроект/project.txt

Почему именно в этих случаях метод наиболее эффективен? Какие его особенности играют роль?


Also sensors lines could be splitted (2 lines) in a sort of grid, it would be better than what I did ...


Same here:
clientList.get(clientIndex).getJobList().get(j).getTitle()


This sounds excellent. I like the idea of basing it on frames rather than time. Do we still need the `scrollingVertically` state now that this approach has changed? I've forgotten how else we use it.


RIght it is better than what I did


Aren't IDE files already supposed to be in gitignore? If not, we should add them in for sure...


I worry that this list and what the code uses internally could diverge. It might be worth putting this array into a more global constant, and reference it here, but also check in Hook#run that we only trigger events from this list and raise some sort of internal error if we ever try to run a hook with an event not in this list.

We should probably also advertise the list of hookable events in the API somewhere, though I am not sure how much that is needed.


unneeded space?


[R/zzz.R:1:1:](https://github.com/jimhester/covr/blob/ef1f8e0cdb6edbdd94c5959a79b9cd3bea6db412/R/zzz.R#L1) *style:* **Variable and function names should be all lowercase.**
```r
.onLoad <- function(libname, pkgname) {
^~~~~~~
```


Why do you omit `__clone` but not the other magic methods?
The only special case in Contao should be the `final public function __clone() {}` which is a no op.
IMHO it is still bad habit to use the magic `__get()`and `__set()` methods, so maybe you want to provide proper replacements for these.
For known classes it would be pretty cool to have the `@property` annotations evaluated and setter/getter created from these.


Link please, would like to see the full announcement. Anyway, if needs be, we can use the same hack as for `add_submenu_page()`, with the hack it passes ;-)


Mỗi tấm ảnh chí có một camera đại diện (hiển nhiên, mỗi tấm ảnh chỉ do một
camera chụp thôi :v), nó ko thể vừa ngang vừa dọc được :v
Với bộ test hoàn toàn ghép theo chiều dọc, em chỉ cần đổi mode sang
WAVE_CORRECT_VERT
 là vấn đề tràn sẽ được giải quyết

Nguyễn Văn Khôi - Lớp CS0801 - SE61174

Vào 00:36 Ngày 23 tháng 04 năm 2015, Văn Khôi, Nguyễn <
khoinvse61174@fpt.edu.vn> đã viết:

> Cái đó thì xem lại tuốt ở trên, ở bước refine Camera :v
> nó có một câu là cv::detail::waveCorrect(rmats,
> cv::detail::WAVE_CORRECT_HORIZ);
> Hiển nhiên mode để tính rotation của camera của mình là theo đường chân
> trời theo chiều ngang :v
> void waveCorrect(vector<Mat> &rmats, WaveCorrectKind kind)
> {
>     LOGLN("Wave correcting...");
> #if ENABLE_LOG
>     int64 t = getTickCount();
> #endif
>     if (rmats.size() <= 1)
>     {
>         LOGLN("Wave correcting, time: " << ((getTickCount() - t) /
> getTickFrequency()) << " sec");
>         return;
>     }
>
>     Mat moment = Mat::zeros(3, 3, CV_32F);
>     for (size_t i = 0; i < rmats.size(); ++i)
>     {
>         Mat col = rmats[i].col(0);
>         moment += col * col.t();
>     }
>     Mat eigen_vals, eigen_vecs;
>     eigen(moment, eigen_vals, eigen_vecs);
>
>     Mat rg1;
>     if (kind == WAVE_CORRECT_HORIZ)
>         rg1 = eigen_vecs.row(2).t();
>     else if (kind == WAVE_CORRECT_VERT)
>         rg1 = eigen_vecs.row(0).t();
>     else
>         CV_Error(CV_StsBadArg, "unsupported kind of wave correction");
>
>     Mat img_k = Mat::zeros(3, 1, CV_32F);
>     for (size_t i = 0; i < rmats.size(); ++i)
>         img_k += rmats[i].col(2);
>     Mat rg0 = rg1.cross(img_k);
>     double rg0_norm = norm(rg0);
>
>     if( rg0_norm <= DBL_MIN )
>     {
>         return;
>     }
>
>     rg0 /= rg0_norm;
>
>     Mat rg2 = rg0.cross(rg1);
>
>     double conf = 0;
>     if (kind == WAVE_CORRECT_HORIZ)
>     {
>         for (size_t i = 0; i < rmats.size(); ++i)
>             conf += rg0.dot(rmats[i].col(0));
>         if (conf < 0)
>         {
>             rg0 *= -1;
>             rg1 *= -1;
>         }
>     }
>     else if (kind == WAVE_CORRECT_VERT)
>     {
>         for (size_t i = 0; i < rmats.size(); ++i)
>             conf -= rg1.dot(rmats[i].col(0));
>         if (conf < 0)
>         {
>             rg0 *= -1;
>             rg1 *= -1;
>         }
>     }
>
>     Mat R = Mat::zeros(3, 3, CV_32F);
>     Mat tmp = R.row(0);
>     Mat(rg0.t()).copyTo(tmp);
>     tmp = R.row(1);
>     Mat(rg1.t()).copyTo(tmp);
>     tmp = R.row(2);
>     Mat(rg2.t()).copyTo(tmp);
>
>     for (size_t i = 0; i < rmats.size(); ++i)
>         rmats[i] = R * rmats[i];
>
>     LOGLN("Wave correcting, time: " << ((getTickCount() - t) /
> getTickFrequency()) << " sec");
> }
>
> Đến bước blend
> warper->warp(img[img_idx], K, cameras[img_idx].R, cv::INTER_LINEAR,
>                 cv::BORDER_REFLECT, img_warped);
> Ảnh của mình là theo chiều dọc, lại bắt warp theo camera chiều ngang
> Point SphericalWarper::warp(const Mat &src, const Mat &K, const Mat &R,
> int interp_mode, int border_mode,
>                                Mat &dst)
> {
>     Rect dst_roi = buildMaps(src.size(), K, R, d_xmap_, d_ymap_);
>     dst.create(dst_roi.height + 1, dst_roi.width + 1, src.type());
>     remap(src, dst, d_xmap_, d_ymap_, interp_mode, border_mode);
>     return dst_roi.tl();
> }
>
>
> Rect CylindricalWarper::buildMaps(Size src_size, const Mat &K, const Mat
> &R, Mat &xmap, Mat &ymap)
> {
>     projector_.setCameraParams(K, R);
>
>     Point dst_tl, dst_br;
>     detectResultRoi(src_size, dst_tl, dst_br);
>
>     buildWarpCylindricalMaps(src_size, Rect(dst_tl, Point(dst_br.x + 1,
> dst_br.y + 1)),
>                                   K, R, projector_.scale, xmap, ymap);
>
>     return Rect(dst_tl, dst_br);
> }
>
> Chỗ mà em phóng to nó thuộc thư viện imgproc/imgwarp.cpp và dài loằng
> ngoằng. Nhưng đại loại là làm bài toán nội suy (để tính lại tỉ lệ trong tấm
> ảnh) và ngoại suy (fill các điểm ảnh để đảm bảo khung ảnh cuối cùng vẫn là
> hình chữ nhật.
> Điểm đặt camera ban đầu sai -> bài toán nội suy và ngoại suy sai số lớn ->
> dễ lỗi.
> Chi tiết bài toán nội suy và ngoại suy thì nó là cả mấy chương liền môn
> MAN của lớp CS nên em ko thể giải thích chi  tiết được đâu ạ @@
>
> Nguyễn Văn Khôi - Lớp CS0801 - SE61174
>
> Vào 23:09 Ngày 22 tháng 04 năm 2015, Manh Thiep Nguyen <
> notifications@github.com> đã viết:
>
>> Anh đồng ý với chỗ chú mô tả việc ghép theo chiều dọc.
>> Chỗ nào cho thấy: "=> dễ gây tràn bộ nhớ và tốn thời gian xử lý ko cần
>> thiết." ?
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/iDoraemon/BiBo-Kit---Panorama/commit/672eb450ff9769ea3c95f12c237f5514fa74b06d#commitcomment-10850634>
>> .
>>
>
>


> But this is a REST lib only.

ah :) then yes, you're correct


Please do not use static inside method, just make a new spc1000_state variable m_motor for this and initialize it to 0 in constructor of spc1000_state.


looks good, minor comments, validated on personal device


Bộ test nhiều tầng thì do trộn lẫn giữa ngang và dọc, để ra kết quả ưng ý
thì phải ưu tiên thằng ngang.

Nguyễn Văn Khôi - Lớp CS0801 - SE61174

Vào 00:42 Ngày 23 tháng 04 năm 2015, Văn Khôi, Nguyễn <
khoinvse61174@fpt.edu.vn> đã viết:

> Mỗi tấm ảnh chí có một camera đại diện (hiển nhiên, mỗi tấm ảnh chỉ do một
> camera chụp thôi :v), nó ko thể vừa ngang vừa dọc được :v
> Với bộ test hoàn toàn ghép theo chiều dọc, em chỉ cần đổi mode sang
> WAVE_CORRECT_VERT
>  là vấn đề tràn sẽ được giải quyết
>
> Nguyễn Văn Khôi - Lớp CS0801 - SE61174
>
> Vào 00:36 Ngày 23 tháng 04 năm 2015, Văn Khôi, Nguyễn <
> khoinvse61174@fpt.edu.vn> đã viết:
>
> Cái đó thì xem lại tuốt ở trên, ở bước refine Camera :v
>> nó có một câu là cv::detail::waveCorrect(rmats,
>> cv::detail::WAVE_CORRECT_HORIZ);
>> Hiển nhiên mode để tính rotation của camera của mình là theo đường chân
>> trời theo chiều ngang :v
>> void waveCorrect(vector<Mat> &rmats, WaveCorrectKind kind)
>> {
>>     LOGLN("Wave correcting...");
>> #if ENABLE_LOG
>>     int64 t = getTickCount();
>> #endif
>>     if (rmats.size() <= 1)
>>     {
>>         LOGLN("Wave correcting, time: " << ((getTickCount() - t) /
>> getTickFrequency()) << " sec");
>>         return;
>>     }
>>
>>     Mat moment = Mat::zeros(3, 3, CV_32F);
>>     for (size_t i = 0; i < rmats.size(); ++i)
>>     {
>>         Mat col = rmats[i].col(0);
>>         moment += col * col.t();
>>     }
>>     Mat eigen_vals, eigen_vecs;
>>     eigen(moment, eigen_vals, eigen_vecs);
>>
>>     Mat rg1;
>>     if (kind == WAVE_CORRECT_HORIZ)
>>         rg1 = eigen_vecs.row(2).t();
>>     else if (kind == WAVE_CORRECT_VERT)
>>         rg1 = eigen_vecs.row(0).t();
>>     else
>>         CV_Error(CV_StsBadArg, "unsupported kind of wave correction");
>>
>>     Mat img_k = Mat::zeros(3, 1, CV_32F);
>>     for (size_t i = 0; i < rmats.size(); ++i)
>>         img_k += rmats[i].col(2);
>>     Mat rg0 = rg1.cross(img_k);
>>     double rg0_norm = norm(rg0);
>>
>>     if( rg0_norm <= DBL_MIN )
>>     {
>>         return;
>>     }
>>
>>     rg0 /= rg0_norm;
>>
>>     Mat rg2 = rg0.cross(rg1);
>>
>>     double conf = 0;
>>     if (kind == WAVE_CORRECT_HORIZ)
>>     {
>>         for (size_t i = 0; i < rmats.size(); ++i)
>>             conf += rg0.dot(rmats[i].col(0));
>>         if (conf < 0)
>>         {
>>             rg0 *= -1;
>>             rg1 *= -1;
>>         }
>>     }
>>     else if (kind == WAVE_CORRECT_VERT)
>>     {
>>         for (size_t i = 0; i < rmats.size(); ++i)
>>             conf -= rg1.dot(rmats[i].col(0));
>>         if (conf < 0)
>>         {
>>             rg0 *= -1;
>>             rg1 *= -1;
>>         }
>>     }
>>
>>     Mat R = Mat::zeros(3, 3, CV_32F);
>>     Mat tmp = R.row(0);
>>     Mat(rg0.t()).copyTo(tmp);
>>     tmp = R.row(1);
>>     Mat(rg1.t()).copyTo(tmp);
>>     tmp = R.row(2);
>>     Mat(rg2.t()).copyTo(tmp);
>>
>>     for (size_t i = 0; i < rmats.size(); ++i)
>>         rmats[i] = R * rmats[i];
>>
>>     LOGLN("Wave correcting, time: " << ((getTickCount() - t) /
>> getTickFrequency()) << " sec");
>> }
>>
>> Đến bước blend
>> warper->warp(img[img_idx], K, cameras[img_idx].R, cv::INTER_LINEAR,
>>                 cv::BORDER_REFLECT, img_warped);
>> Ảnh của mình là theo chiều dọc, lại bắt warp theo camera chiều ngang
>> Point SphericalWarper::warp(const Mat &src, const Mat &K, const Mat &R,
>> int interp_mode, int border_mode,
>>                                Mat &dst)
>> {
>>     Rect dst_roi = buildMaps(src.size(), K, R, d_xmap_, d_ymap_);
>>     dst.create(dst_roi.height + 1, dst_roi.width + 1, src.type());
>>     remap(src, dst, d_xmap_, d_ymap_, interp_mode, border_mode);
>>     return dst_roi.tl();
>> }
>>
>>
>> Rect CylindricalWarper::buildMaps(Size src_size, const Mat &K, const Mat
>> &R, Mat &xmap, Mat &ymap)
>> {
>>     projector_.setCameraParams(K, R);
>>
>>     Point dst_tl, dst_br;
>>     detectResultRoi(src_size, dst_tl, dst_br);
>>
>>     buildWarpCylindricalMaps(src_size, Rect(dst_tl, Point(dst_br.x + 1,
>> dst_br.y + 1)),
>>                                   K, R, projector_.scale, xmap, ymap);
>>
>>     return Rect(dst_tl, dst_br);
>> }
>>
>> Chỗ mà em phóng to nó thuộc thư viện imgproc/imgwarp.cpp và dài loằng
>> ngoằng. Nhưng đại loại là làm bài toán nội suy (để tính lại tỉ lệ trong tấm
>> ảnh) và ngoại suy (fill các điểm ảnh để đảm bảo khung ảnh cuối cùng vẫn là
>> hình chữ nhật.
>> Điểm đặt camera ban đầu sai -> bài toán nội suy và ngoại suy sai số lớn
>> -> dễ lỗi.
>> Chi tiết bài toán nội suy và ngoại suy thì nó là cả mấy chương liền môn
>> MAN của lớp CS nên em ko thể giải thích chi  tiết được đâu ạ @@
>>
>> Nguyễn Văn Khôi - Lớp CS0801 - SE61174
>>
>> Vào 23:09 Ngày 22 tháng 04 năm 2015, Manh Thiep Nguyen <
>> notifications@github.com> đã viết:
>>
>>> Anh đồng ý với chỗ chú mô tả việc ghép theo chiều dọc.
>>> Chỗ nào cho thấy: "=> dễ gây tràn bộ nhớ và tốn thời gian xử lý ko cần
>>> thiết." ?
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/iDoraemon/BiBo-Kit---Panorama/commit/672eb450ff9769ea3c95f12c237f5514fa74b06d#commitcomment-10850634>
>>> .
>>>
>>
>>
>


If this command is mostly for debugging/development, would it make sense to include the input to the hook in the result as well as the output ? It might help in spotting simple errors in the hook script, plus given valid input to your hook, you can then just run it locally from the command line to catch egregious errors like looking for a non-existent key in the input


When I looked through commits last week, it looked like it had been merged, sorry to delay you


what are these?


wrong link. use this one https://github.com/PUGX/PUGXAutoCompleterBundle/blob/master/Resources/doc/index.md


Disagree, nobody needs to know whether it was generated or not.


Because I haven't used them yet?


@asmecher i've made a few tests and removed these line, it looks like just changing owner to www-data gives permission to php write in these paths.


`dok.error()`s are difficult to track, since the *lua* error message doesn't report where they are coming from. There is just a message saying that the `image.hflip` domain complains.
Moreover, if the test is `true`, which means the *Tensor* is not *contiguous*, shouldn't we force it rather than crashing, perhaps with a warning?


Can you talk more about why you don't start at 0 here? You said:

> ...the current scheme is an attempt to never issue the same node ID + generation number, so you can NFS mount a file system without clients confusing which inode they are accessing.

I'm not sure how the generation number would be exposed to the NFS mounts...


this way you disabled the previous "feature" of subscribing to all events

I would consider restoring it - it's convenient to be able to listen to all events easily - let's say for displaying all the events on the UI on the fly.


The code samples can be found at https://github.com/awslabs/aws-sdk-android-samples


Sure. I can do that. I am not sure why this went in in first place. I too remember that we ignore the ide files automatically.


Can you make this a table based method ?

public static final String[] validExtensions =  { INDEX_FILE_EXTENSION , COMPRESSED_INDEX_FILE_EXTENSION , DATA_FILE_EXTENSION , COMPRESSED_DATA_FILE_EXTENSION };

for(String extension: validExtensions) {
   if( f1.endsWith(extension) && f2.endsWith(extension)) return f1.comapreToIgnoreCase(f2);


The input and output can be added to the Event that is returned by using the new `store_hook_input` and `store_hook_output` configuration properties. Is this sufficient, or should we avoid returning the Event from the command and instead return debugging information?


2 questions: should we always use strict mode, and is this the right way to do it with exported modules?


Like this


Your eclipse settings removed the space between the catch, for and if. It is generally better to read if you have a space between them.


we can't until scribble is updated


1: M111 unrecognized component name: testsuite


maintenance branch ?


BnP is creating AdminClient like Crazy and never disposing them. Can this method take in an AdminClient instead of creating one every time.

AdminClient creates 9 threads and connections, none of them are disposed until the process terminates.


These static calls should IMO rather be calls to `instantiate()` instead of calling `getInstance()` in each and every method.
Makes it easier to mock the stuff as you will only have to override one method to swap out the entire "delegated" class.


This commit is an attempt at  refactoring the implementation of escaping. Keeping `sRun` didn't make too much sense once I added the boolean because the boolean needs to be applied at the last minute to decide between `runCommand` and `runCommandNoEscape`, but `onCommandHandles` might have already changed that.


@ferranpujolcamins thank _you_ for the nice new functionality :). Please do sign the contributor agreement.


- 2 more phases
- few final (most hard to fix  quests)
+ some events...
+ few spells are not working there
so yes ..still smth to do there ;)


algo


https://openqa.suse.de/tests/31133/file/autoinst-log.txt - still not enough.


For some odd reason, it didn't like the var name "location"...


Done (without NEWS file entry)


If you checked the actual code I used a simply workaround, 2 variables absolute and 2 that reflect the actual with and height.
If you have the display in portrait mode and I follow what you are saing, my display will be 800 wide and 480 height??? Did you think it's realistic?
There's not so many changes to do, just adding a couple of vars in the code and the people using this display together with this library can use width() and height() for their code (otherwise they always get wrong results in portrait mode).


je teste toujours


Yes, I agree your approach is better. I added another draft here including an attempt at refactoring `escaping`:  https://github.com/hsenag/Shelly.hs/commit/590bab8d215d5f6f3cf80d64a289488089b4caf9

I still need to get the test suite working for me and add tests for the new feature.


Well arguable, I asusme you do not want to limit this tool to be run on the core classes but also allow other legacy vendors to map their classes but this is really nitpicking. Just wanted to mention it. :)


It might be better not to have a version number. When snap 3.0 is installed, the user may still want to to use the stuff inside .snap.
The alternative is that the installer migrates from .snap2 to .snap3


Ok. I'll try to accomplish that.


@r-a-y Could I get your feedback on this changeset? I've been messing with your handiwork, but I think it's in the right spirit :) This is the only way I could figure out how to get consistent and predictable actions from EO without refactoring EO's entire save routine.


https://openqa.suse.de/tests/31231
https://openqa.suse.de/tests/31343
...
I don't have the impression your fix helped


Yeah, I thought about that first but no, I don't want others to use this. If they want to use it as a foundation then fine but I don't have the time to make it a universal library.


Wow.


So where does this leave us now?
You did not answer the initial question why you omit the method.
Don't take me wrong here, I just want to understand the reasoning, IMO silently omitting it is bad as it should at least throw an exception that cloning is not supported on the adapter.


2 questions: should we always use strict mode, and is this the right way to do it with exported modules?


I had test drive locally already for my proposed colours.

I wanted to check if it was alright in all the colour blindness types with your current code before answering. I was afraid the orange of allowed.blocked would react next to the new yellowish allow, and how the current noop would be next to the new navy blue block. But everything is fine, I'll close the PR as well.

Although, just one note: I pushed the transparency from 0.3 to 0.4 in colorblind mode. The corresponding noop rule should be pushed too, otherwise the drop in saturation is noticeable.


Author: user.name?


FixTransitionIssues (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1641 of 1641 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


I have no idea about `__clone`, `__set` and `__get` yet but I'll think about it when I need to :)


je teste tout simplement .


@Tux64 @javathunderman We were hoping that list would get us some help! :smiley: Please keep us up-to-date with the development of it, and we will try to help out the best that we can! Let me know if you need anything (like button images, or even just help coding)!


You don't need to credit individual lines using comments in the code, the version control will record that you made this contribution. :smile:

Ideally, your commit message for this change should be what this comment is, along the lines of "Fix writing of incorrect plSpan value."  This comment is just an artifact of history (applying to _this_ changeset) and has no relevance to the actual code that it decorates.


Mind submitting this as a pull request? Thanks!


Why did you add the .h file to gitignore?


Yeah, this is merged. I have a new pull request now...


Bien! Arreglaron el tema de las fechas.
Acá podrían tranquilamente recibir un string y convertirlo a LocalDate, después fíjense si encuentran por ahí como hacerlo que les va a reducir un poco la cantidad de parámetros que quizás más adelante les sirva.


Also check the last beta, I have fixed the 8 bit color and you can forget the Color565 modifications, the RA8875 has internal hardware 16 to 8 bit conversion.


@6a68 good question, and I don't have a good answer yet.

There's a pretty big fork in the road coming up I think - should we focus on *local* search, i.e., index locally, answer as much we can without sending bits over the wire, or do focus on using the local data to enhance cloud services, including search.

In plain english: do we index the history locally, or do we push it to a moz cloud and index it there. Pros/cons for both.

The most flexible route is to index centrally, but it's also what everybody else does. The local option makes us different, for what that's worth.


This will do a lexical sort, ie "10000" will come before "2000", is that ok?


As it was discussed before, at the moment the client-side scrypt can't match the server side "globaleaks" hash, so in that case there's this special condition to make it work for now. At a later stage, when integration begins, we'll need a server-side fix, or a client-side wizard fix to send the default password as it would be hashed by the scyrpt at login


Validate form's data that user inputs by JavaScript and JavaSE's ServerSocket object.


If you can squish this commit into ea91245841 and re-push the corrected combined commit, it would clean this up.


Дык, я ещё вчера переписал


if "tab_size > MAX_TAB_SIZE" then "tab_size>=MIN_TAB_SIZE" is true and you set tableSize to a number larger than MAX_TAB_SIZE


How to install Erica tool --> https://github.com/benoitc/erica


Looks like a solid design now, thanks!

Let me know what problems you run into on the test suite. I only run it on Linux right now.


If you return from the above block you don't need the 'else' block.


Great


IDE files are ignored, but if you change them, your git status will always show them. git commit -a wont commit it, but git status will always show it. You have to add it explicility using git add and commit it.

You can use the command I gave above to remove it from git status


To create NFS server, run: es_snap::server
On all ES nodes, run: es_snap::client and es_snap::es_backup


"proejct"


Why do you comment this out here only to revert it back in 09dca3cfdedb4c ?


Hmm, I would rather not introduce a special after save hook when the `'save_post'` hook should do the job in normal circumstances.

What if I brought back the autosave feature?  And when someone clicked on the "New Event" button, this would pull up the last event draft for the current user if one exists and displays a message like "It looks like you have an existing draft.  Please continue editing or discard this draft and create a new event" above the editor?  If an event draft does not exist, it would create a new auto-draft post and autosave would kick in as normal.

Would this fix the majority of these problems and not require you to jump through hoops to determine if an event is new or not?


oui preque @benTrust :) ce que j'ai compris c'est que la classe solo herite de la classe partie, mais est ce que je dois recuperer une variable coups de partie ? je vais essayer de faire un truc pour voir si j'ai bien compris


> I'll close the PR as well

I hadn't noticed there was a pull request -- I just pulled it. (I turned off github email notifications days ago).


like the new logos


I've just checked, and `image.{h,v}flip()` were working alright with non-contiguous *Tensor*s. I guess that enforcing contiguity is the way to go, for keeping back-compatibility.


much better logically


But you are already skipping `__clone` and therefore already have thought about it? :D


Why?????


No, I haven't - I just ignored it because I don't care about cloning. I don't see where we would need to clone an adapter yet.


We stellen voor om het meer info te noemen


This is now obsolete.


Yes, I transformed it to fix the noop colour instead.
Thanks for your time, it looks fine now.


Looks like a copy-paste error here.  Should be `str(self.fSmartSeek)`


No problem thanks for closing that.  Might be easier to just have both authors present when we merge

On Apr 22, 2015, at 10:49 AM, Alex Campbell <notifications@github.com> wrote:

> All the above work was done by @abgordon. I screwed up the branch merge...
>
> —
> Reply to this email directly or view it on GitHub.
>


Thank you so much! It is so nice to get such excellent contributions.


Same as above, with `str(self.fReverseFBControlsOnRelease)`


31:1: I100 Imports statements are in the wrong order. from invenio.ext.passlib should be before from sqlalchemy_utils.types.choice


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
36:1: I101 Imported names are in the wrong order. Should be CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS, CFG_BASE_URL, CFG_BIBFORMAT_HIDDEN_TAGS, CFG_BIBINDEX_CHARS_PUNCTUATION, CFG_BIBRANK_SHOW_DOWNLOAD_GRAPHS, CFG_BIBRANK_SHOW_DOWNLOAD_GRAPHS, CFG_BIBSORT_BUCKETS, CFG_BIBSORT_ENABLED, CFG_BIBUPLOAD_EXTERNAL_SYSNO_TAG, CFG_BIBUPLOAD_EXTERNAL_SYSNO_TAG, CFG_BIBUPLOAD_SERIALIZE_RECORD_STRUCTURE, CFG_BIBUPLOAD_SERIALIZE_RECORD_STRUCTURE, CFG_CERN_SITE, CFG_INSPIRE_SITE, CFG_LOGDIR, CFG_LOGDIR, CFG_OAI_ID_FIELD, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_RECORD, CFG_SITE_URL, CFG_SOLR_URL, CFG_WEBSEARCH_DEF_RECORDS_IN_GROUPS, CFG_WEBSEARCH_DETAILED_META_FORMAT, CFG_WEBSEARCH_DISPLAY_NEAREST_TERMS, CFG_WEBSEARCH_FIELDS_CONVERT, CFG_WEBSEARCH_FULLTEXT_SNIPPETS, CFG_WEBSEARCH_IDXPAIRS_EXACT_SEARCH, CFG_WEBSEARCH_IDXPAIRS_FIELDS, CFG_WEBSEARCH_PREV_NEXT_HIT_LIMIT, CFG_WEBSEARCH_SYNONYM_KBRS, CFG_WEBSEARCH_VIEWRESTRCOLL_POLICY, CFG_WEBSEARCH_WILDCARD_LIMIT, CFG_WEBSEARCH_WILDCARD_LIMIT, CFG_XAPIAN_ENABLED
36:1: F999 redefinition of unused 'CFG_BIBUPLOAD_SERIALIZE_RECORD_STRUCTURE' from line 36
36:1: F999 redefinition of unused 'CFG_BIBUPLOAD_EXTERNAL_SYSNO_TAG' from line 36
36:1: F999 redefinition of unused 'CFG_BIBRANK_SHOW_DOWNLOAD_GRAPHS' from line 36
36:1: F999 redefinition of unused 'CFG_LOGDIR' from line 36
36:1: F999 redefinition of unused 'CFG_WEBSEARCH_WILDCARD_LIMIT' from line 36
36:1: F401 'CFG_XAPIAN_ENABLED' imported but unused
36:1: F401 'CFG_BIBINDEX_CHARS_PUNCTUATION' imported but unused
36:1: F401 'CFG_OAI_ID_FIELD' imported but unused
36:1: F401 'CFG_WEBSEARCH_VIEWRESTRCOLL_POLICY' imported but unused
36:1: F401 'CFG_WEBSEARCH_SYNONYM_KBRS' imported but unused
36:1: F401 'CFG_BIBUPLOAD_SERIALIZE_RECORD_STRUCTURE' imported but unused
36:1: F401 'CFG_WEBSEARCH_DISPLAY_NEAREST_TERMS' imported but unused
36:1: F401 'CFG_WEBSEARCH_FIELDS_CONVERT' imported but unused
36:1: F401 'CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS' imported but unused
36:1: F401 'CFG_SITE_RECORD' imported but unused
36:1: F401 'CFG_BIBRANK_SHOW_DOWNLOAD_GRAPHS' imported but unused
36:1: F401 'CFG_INSPIRE_SITE' imported but unused
36:1: F401 'CFG_LOGDIR' imported but unused
36:1: F401 'CFG_BIBUPLOAD_EXTERNAL_SYSNO_TAG' imported but unused
36:1: F401 'CFG_WEBSEARCH_PREV_NEXT_HIT_LIMIT' imported but unused
36:1: F401 'CFG_BASE_URL' imported but unused
36:1: F401 'CFG_BIBFORMAT_HIDDEN_TAGS' imported but unused
36:1: F401 'CFG_WEBSEARCH_WILDCARD_LIMIT' imported but unused
36:1: F401 'CFG_WEBSEARCH_DETAILED_META_FORMAT' imported but unused
36:1: F401 'CFG_BIBSORT_BUCKETS' imported but unused
36:1: F401 'CFG_WEBSEARCH_FULLTEXT_SNIPPETS' imported but unused
36:1: F401 'CFG_SOLR_URL' imported but unused
36:1: F401 'CFG_WEBSEARCH_IDXPAIRS_EXACT_SEARCH' imported but unused
36:1: F401 'CFG_WEBSEARCH_IDXPAIRS_FIELDS' imported but unused
36:1: E402 module level import not at top of file
37:6: E126 continuation line over-indented for hanging indent
80:1: E402 module level import not at top of file
81:1: F401 'get_most_popular_field_values' imported but unused
81:1: E402 module level import not at top of file
82:1: I101 Imported names are in the wrong order. Should be InvenioWebSearchCitedbyLimitError, InvenioWebSearchReferstoLimitError, InvenioWebSearchUnknownCollectionError, InvenioWebSearchWildcardLimitError
82:1: I100 Imports statements are in the wrong order. from invenio.modules.search.errors should be before from invenio.modules.search.utils
82:1: F401 'InvenioWebSearchUnknownCollectionError' imported but unused
82:1: F401 'InvenioWebSearchReferstoLimitError' imported but unused
82:1: F401 'InvenioWebSearchWildcardLimitError' imported but unused
82:1: F401 'InvenioWebSearchCitedbyLimitError' imported but unused
82:1: E402 module level import not at top of file
83:6: E126 continuation line over-indented for hanging indent
87:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.search.errors
87:1: F401 'get_fieldvalues_alephseq_like' imported but unused
87:1: E402 module level import not at top of file
89:1: E402 module level import not at top of file
90:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from .utils
90:1: I201 Missing newline before sections or imports.
90:1: F401 'create_record' imported but unused
90:1: F401 'record_xml_output' imported but unused
90:1: E402 module level import not at top of file
91:1: I101 Imported names are in the wrong order. Should be get_bibrank_methods, is_method_valid, rank_by_citations, rank_records
91:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrank.record_sorter should be before from invenio.legacy.bibrecord
91:1: F401 'rank_by_citations' imported but unused
91:1: F401 'get_bibrank_methods' imported but unused
91:1: E402 module level import not at top of file
96:1: I101 Imported names are in the wrong order. Should be calculate_reading_similarity_list, register_page_view_event
96:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrank.downloads_similarity should be before from invenio.legacy.bibrank.record_sorter
96:1: F401 'register_page_view_event' imported but unused
96:1: F401 'calculate_reading_similarity_list' imported but unused
96:1: E402 module level import not at top of file
97:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_stemmer should be before from invenio.legacy.bibrank.downloads_similarity
97:1: F401 'stem' imported but unused
97:1: E402 module level import not at top of file
98:1: F401 'BibIndexDefaultTokenizer' imported but unused
98:1: E402 module level import not at top of file
99:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_utils should be before from invenio.modules.indexer.tokenizers.BibIndexDefaultTokenizer
99:1: F401 'author_name_requires_phrase_search' imported but unused
99:1: F401 'get_field_tags' imported but unused
99:1: E402 module level import not at top of file
101:1: I101 Imported names are in the wrong order. Should be lower_index_term, wash_author_name, wash_index_term
101:1: F401 'wash_index_term' imported but unused
101:1: F401 'wash_author_name' imported but unused
101:1: F401 'lower_index_term' imported but unused
101:1: E402 module level import not at top of file
102:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_config should be before from invenio.legacy.bibindex.engine_washer
102:1: F401 'CFG_BIBINDEX_SYNONYM_MATCH_TYPE' imported but unused
102:1: E402 module level import not at top of file
103:1: F401 'create_download_history_graph_and_box' imported but unused
103:1: E402 module level import not at top of file
104:1: F401 'DataCacher' imported but unused
104:1: E402 module level import not at top of file
105:1: I101 Imported names are in the wrong order. Should be perform_external_collection_search, print_external_results_overview
105:1: F401 'perform_external_collection_search' imported but unused
105:1: F401 'print_external_results_overview' imported but unused
105:1: E402 module level import not at top of file
106:1: E402 module level import not at top of file
107:1: I101 Imported names are in the wrong order. Should be CFG_ACC_GRANT_AUTHOR_RIGHTS_TO_EMAILS_IN_TAGS, CFG_ACC_GRANT_AUTHOR_RIGHTS_TO_USERIDS_IN_TAGS, CFG_ACC_GRANT_VIEWER_RIGHTS_TO_EMAILS_IN_TAGS, CFG_ACC_GRANT_VIEWER_RIGHTS_TO_USERIDS_IN_TAGS, VIEWRESTRCOLL
107:1: F401 'CFG_ACC_GRANT_AUTHOR_RIGHTS_TO_EMAILS_IN_TAGS' imported but unused
107:1: F401 'CFG_ACC_GRANT_AUTHOR_RIGHTS_TO_USERIDS_IN_TAGS' imported but unused
107:1: F401 'CFG_ACC_GRANT_VIEWER_RIGHTS_TO_USERIDS_IN_TAGS' imported but unused
107:1: F401 'CFG_ACC_GRANT_VIEWER_RIGHTS_TO_EMAILS_IN_TAGS' imported but unused
107:1: E402 module level import not at top of file
113:1: I100 Imports statements are in the wrong order. from invenio.legacy.websearch.adminlib should be before from invenio.modules.access.local_config
113:1: F401 'get_detailed_page_tabs' imported but unused
113:1: F401 'get_detailed_page_tabs_counts' imported but unused
113:1: E402 module level import not at top of file
114:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.legacy.websearch.adminlib
114:1: I201 Missing newline before sections or imports.
114:1: E402 module level import not at top of file
115:1: I101 Imported names are in the wrong order. Should be DatabaseError, InvenioDbQueryWildcardLimitError, deserialize_via_marshal
115:1: I201 Missing newline before sections or imports.
115:1: F401 'deserialize_via_marshal' imported but unused
115:1: F401 'DatabaseError' imported but unused
115:1: F401 'InvenioDbQueryWildcardLimitError' imported but unused
115:1: E402 module level import not at top of file
116:1: F401 'acc_authorize_action' imported but unused
116:1: E402 module level import not at top of file
117:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.modules.access.engine
117:1: E402 module level import not at top of file
118:1: I101 Imported names are in the wrong order. Should be encode_for_xml, strip_accents, wash_for_utf8
118:1: F401 'encode_for_xml' imported but unused
118:1: F401 'wash_for_utf8' imported but unused
118:1: F401 'strip_accents' imported but unused
118:1: E402 module level import not at top of file
119:1: I100 Imports statements are in the wrong order. from invenio.legacy should be before from invenio.utils.text
119:1: E402 module level import not at top of file
121:1: E402 module level import not at top of file
124:1: I101 Imported names are in the wrong order. Should be calculate_cited_by_list, calculate_co_cited_with_list, get_cited_by_list, get_citedby_hitset, get_citers_log, get_records_with_num_cites, get_refers_to_list, get_refersto_hitset
124:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrank.citation_searcher should be before import invenio.legacy.template
124:1: F401 'get_citedby_hitset' imported but unused
124:1: F401 'get_records_with_num_cites' imported but unused
124:1: F401 'calculate_cited_by_list' imported but unused
124:1: F401 'get_refersto_hitset' imported but unused
124:1: F401 'get_cited_by_list' imported but unused
124:1: F401 'get_citers_log' imported but unused
124:1: F401 'calculate_co_cited_with_list' imported but unused
124:1: F401 'get_refers_to_list' imported but unused
124:1: E402 module level import not at top of file
129:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrank.citation_grapher should be before from invenio.legacy.bibrank.citation_searcher
129:1: F401 'create_citation_history_graph_and_box' imported but unused
129:1: E402 module level import not at top of file
130:1: I101 Imported names are in the wrong order. Should be get_self_cited_by, get_self_cited_by_list, get_self_refers_to_list
130:1: F401 'get_self_refers_to_list' imported but unused
130:1: F401 'get_self_cited_by' imported but unused
130:1: F401 'get_self_cited_by_list' imported but unused
130:1: E402 module level import not at top of file
131:55: E126 continuation line over-indented for hanging indent
134:1: I101 Imported names are in the wrong order. Should be get_table_update_time, run_sql, run_sql_with_limit, wash_table_column_name
134:1: F401 'wash_table_column_name' imported but unused
134:1: F401 'get_table_update_time' imported but unused
134:1: F401 'run_sql_with_limit' imported but unused
134:1: E402 module level import not at top of file
136:1: I101 Imported names are in the wrong order. Should be collect_user_info, getUid
136:1: F401 'collect_user_info' imported but unused
136:1: E402 module level import not at top of file
137:1: I101 Imported names are in the wrong order. Should be create_error_box, pagefooteronly, pageheaderonly, write_warning
137:1: I100 Imports statements are in the wrong order. from invenio.legacy.webpage should be before from invenio.legacy.webuser
137:1: F401 'pagefooteronly' imported but unused
137:1: F401 'create_error_box' imported but unused
137:1: F401 'write_warning' imported but unused
137:1: F401 'pageheaderonly' imported but unused
137:1: E402 module level import not at top of file
138:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.legacy.webpage
138:1: E402 module level import not at top of file
140:1: F401 'apache' imported but unused
140:1: E402 module level import not at top of file
142:1: I100 Imports statements are in the wrong order. from invenio.legacy.websearch_external_collections should be before from invenio.utils
142:1: F401 'do_calculate_hosted_collections_results' imported but unused
142:1: F401 'calculate_hosted_collections_results' imported but unused
142:1: E402 module level import not at top of file
143:1: F401 'CFG_EXTERNAL_COLLECTION_MAXRESULTS' imported but unused
143:1: E402 module level import not at top of file
148:22: E203 whitespace before ':'
148:14: E225 missing whitespace around operator
149:24: E203 whitespace before ':'
150:24: E203 whitespace before ':'
151:28: E203 whitespace before ':'
152:30: E203 whitespace before ':'
153:24: E203 whitespace before ':'
154:23: E203 whitespace before ':'
155:29: E203 whitespace before ':'
156:26: E203 whitespace before ':'
157:33: E203 whitespace before ':'
158:30: E203 whitespace before ':'
159:30: E203 whitespace before ':'
160:30: E203 whitespace before ':'
161:30: E203 whitespace before ':'
162:30: E203 whitespace before ':'
163:30: E203 whitespace before ':'
164:41: E703 statement ends with a semicolon
166:1: E402 module level import not at top of file
167:1: F401 'collection_restricted_p' imported but unused
167:1: E402 module level import not at top of file
168:1: F401 'restricted_collection_cache' imported but unused
168:1: E402 module level import not at top of file
169:1: F401 'get_permitted_restricted_collections' imported but unused
169:1: E402 module level import not at top of file
170:1: I100 Imports statements are in the wrong order. from invenio.modules.collections.cache should be before from invenio.modules.search.utils
170:1: F401 'get_all_restricted_recids' imported but unused
170:1: E402 module level import not at top of file
173:1: F401 'check_user_can_view_record' imported but unused
173:1: E402 module level import not at top of file
175:1: I100 Imports statements are in the wrong order. from invenio.modules.collections.cache should be before from invenio.modules.records.access
175:1: E402 module level import not at top of file
176:1: I100 Imports statements are in the wrong order. from invenio.modules.collections.cache should be before from invenio.modules.collections.cache
176:1: E402 module level import not at top of file
177:1: F401 'get_field_i18nname' imported but unused
177:1: E402 module level import not at top of file
179:1: I100 Imports statements are in the wrong order. from invenio.modules.indexer.models should be before from invenio.modules.search.cache
179:1: E402 module level import not at top of file
185: D401 First line should be in imperative mood ('Create', not 'Creates')
185: D202 No blank lines allowed after function docstring (found 1)
185: D400 First line should end with a period (not 'n')
185: D205 1 blank line required between summary line and description (found 0)
193:33: E261 at least two spaces before inline comment
202:1: F401 'get_synonym_terms' imported but unused
202:1: E402 module level import not at top of file
204:1: F403 'from invenio.modules.search.washers import *' used; unable to detect undefined names
204:1: E402 module level import not at top of file
207: D401 First line should be in imperative mood ('Return', not 'Returns')
207: D300 Use """triple double quotes""" (found '-quotes)
228:1: I100 Imports statements are in the wrong order. from invenio.modules.collections.cache should be before from invenio.modules.search.washers
228:1: F401 'get_collection_allchildren' imported but unused
228:1: E402 module level import not at top of file
231: D401 First line should be in imperative mood ('Return', not 'Returns')
231: D202 No blank lines allowed after function docstring (found 1)
234:5: E266 too many leading '#' for block comment
238:5: E266 too many leading '#' for block comment
239:5: E266 too many leading '#' for block comment
241:34: E261 at least two spaces before inline comment
258:13: B901 blind except: statement
263:9: E266 too many leading '#' for block comment
275:9: E266 too many leading '#' for block comment
280:17: E266 too many leading '#' for block comment
289: D400 First line should end with a period (not 'o')
289: D205 1 blank line required between summary line and description (found 0)
289: D208 Docstring is over-indented
334:1: F403 'from invenio.modules.search.searchext.engines.native import *' used; unable to detect undefined names
334:1: E402 module level import not at top of file
337: D209 Multi-line docstring closing quotes should be on a separate line
337: D400 First line should end with a period (not 'y')
337: D205 1 blank line required between summary line and description (found 0)
337: D208 Docstring is over-indented
350:38: E203 whitespace before ','
381:1: E302 expected 2 blank lines, found 0
381: D209 Multi-line docstring closing quotes should be on a separate line
381: D400 First line should end with a period (not 'g')
381: D205 1 blank line required between summary line and description (found 0)
381: D208 Docstring is over-indented
410: D209 Multi-line docstring closing quotes should be on a separate line
410: D205 1 blank line required between summary line and description (found 0)
422:1: I100 Imports statements are in the wrong order. from invenio.modules.search.models should be before from invenio.modules.search.searchext.engines.native
422:1: E402 module level import not at top of file
427: D210 No whitespaces allowed surrounding docstring text
427: None: None
427: D400 First line should end with a period (not 'h')
427: D205 1 blank line required between summary line and description (found 0)
445: D401 First line should be in imperative mood ('I', not 'Is')
445: D400 First line should end with a period (not '?')
456:1: E302 expected 2 blank lines, found 1
456: D205 1 blank line required between summary line and description (found 0)
456: D208 Docstring is over-indented
463:1: I101 Imported names are in the wrong order. Should be CACHE_SORTED_DATA, SORTING_METHODS
463:1: F401 'CACHE_SORTED_DATA' imported but unused
463:1: E402 module level import not at top of file
466: D205 1 blank line required between summary line and description (found 0)
466: D208 Docstring is over-indented
480:20: E127 continuation line over-indented for visual indent
482:25: E126 continuation line over-indented for hanging indent
533: D103 Missing docstring in public function
543: D401 First line should be in imperative mood ('calculate', not 'calculates')
543: D209 Multi-line docstring closing quotes should be on a separate line
543: D202 No blank lines allowed after function docstring (found 1)
543: D400 First line should end with a period (not 'e')
543: D205 1 blank line required between summary line and description (found 0)
554:20: E261 at least two spaces before inline comment
558:17: E261 at least two spaces before inline comment
601: D210 No whitespaces allowed surrounding docstring text
601: None: None
601: D400 First line should end with a period (not 'n')
607:25: E261 at least two spaces before inline comment
608:13: E222 multiple spaces after operator
631:10: E261 at least two spaces before inline comment
648:1: E266 too many leading '#' for block comment
650: D103 Missing docstring in public function
651:25: E128 continuation line under-indented for visual indent
652:25: E128 continuation line under-indented for visual indent
653:25: E128 continuation line under-indented for visual indent
654:25: E128 continuation line under-indented for visual indent
671: D401 First line should be in imperative mood ('Set', not 'Sets')
671: D202 No blank lines allowed after function docstring (found 1)
671: D400 First line should end with a period (not 'l')
671: D200 One-line docstring should fit on one line with quotes (found 3)
672:23: E128 continuation line under-indented for visual indent
673:23: E128 continuation line under-indented for visual indent
674:23: E128 continuation line under-indented for visual indent
675:23: E128 continuation line under-indented for visual indent
676:23: E128 continuation line under-indented for visual indent
714:9: B901 blind except: statement


1: D210 No whitespaces allowed surrounding docstring text
1: None: None
27:1: I101 Imported names are in the wrong order. Should be CFG_SITE_ADMIN_EMAIL, CFG_SITE_NAME, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.config
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.base.i18n
29:1: F401 'config' imported but unused
29:1: E402 module level import not at top of file
146:16: E126 continuation line over-indented for hanging indent
152:58: E203 whitespace before ','
212:15: E126 continuation line over-indented for hanging indent
215:1: E402 module level import not at top of file
248:17: E203 whitespace before ':'
249:22: E203 whitespace before ':'
250:20: E203 whitespace before ':'
251:18: E203 whitespace before ':'
252:24: E203 whitespace before ':'
253:22: E203 whitespace before ':'
254:19: E203 whitespace before ':'
255:20: E203 whitespace before ':'
256:23: E203 whitespace before ':'
257:18: E203 whitespace before ':'
258:17: E203 whitespace before ':'
259:19: E203 whitespace before ':'
260:20: E203 whitespace before ':'
261:21: E203 whitespace before ':'
262:19: E203 whitespace before ':'
263:19: E203 whitespace before ':'
264:20: E203 whitespace before ':'
265:17: E203 whitespace before ':'
266:24: E203 whitespace before ':'
267:23: E203 whitespace before ':'
268:21: E203 whitespace before ':'
269:37: E203 whitespace before ':'
283:4: E131 continuation line unaligned for hanging indent
312:1: W391 blank line at end of file


1: D100 Missing docstring in public module
4: L102 copyright year is outdated, expected 2015 but got 2014
55:1: I100 Imports statements are in the wrong order. import datetime should be before import time
57:1: I100 Imports statements are in the wrong order. import logging should be before import traceback
62:1: I201 Missing newline before sections or imports.
63:1: I100 Imports statements are in the wrong order. from socket should be before from intbitset
63:1: I201 Missing newline before sections or imports.
65:1: I101 Imported names are in the wrong order. Should be _db_login, run_sql
67:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio.modules.accounts.models
68:1: I101 Imported names are in the wrong order. Should be CFG_BIBSCHED_FLUSH_LOGS, CFG_BIBSCHED_PROCESS_USER, CFG_BINDIR, CFG_PREFIX, CFG_SITE_NAME, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_TMPDIR, CFG_VERSION
68:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.modules.access.engine
68:1: F401 'CFG_PREFIX' imported but unused
81:1: I101 Imported names are in the wrong order. Should be CFG_EXTERNAL_AUTHENTICATION, CFG_EXTERNAL_AUTH_USING_SSO
82:49: E126 continuation line over-indented for hanging indent
83:1: I101 Imported names are in the wrong order. Should be get_email, get_email_from_username, get_user_preferences
83:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.modules.access.local_config
84:1: I101 Imported names are in the wrong order. Should be CFG_BIBSCHED_LOGDIR, CFG_BIBTASK_DEFAULT_GLOBAL_TASK_SETTINGS, CFG_BIBTASK_DEFAULT_TASK_SETTINGS, CFG_BIBTASK_FIXEDTIMETASKS, CFG_BIBTASK_LOG_FORMAT, CFG_BIBTASK_VALID_TASKS
84:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask_config should be before from invenio.legacy.webuser
94:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.utils.shell
95:1: I101 Imported names are in the wrong order. Should be bibsched_get_host, bibsched_set_host
96:41: E126 continuation line over-indented for hanging indent
110: D101 Missing docstring in public class
113:1: E302 expected 2 blank lines, found 1
113: D101 Missing docstring in public class
114: D102 Missing docstring in public method
118:1: E302 expected 2 blank lines, found 1
118: D400 First line should end with a period (not 't')
118: D205 1 blank line required between summary line and description (found 0)
141:13: E266 too many leading '#' for block comment
157: D205 1 blank line required between summary line and description (found 0)
184:17: E266 too many leading '#' for block comment
207:17: E266 too many leading '#' for block comment
227:17: E266 too many leading '#' for block comment
250:17: E266 too many leading '#' for block comment
273:17: E266 too many leading '#' for block comment
290:12: E713 test for membership should be 'not in'
310:86: F812 list comprehension redefines 'arg' from line 296
312:9: E266 too many leading '#' for block comment
316:13: E128 continuation line under-indented for visual indent
327: D401 First line should be in imperative mood ('Return', not 'Returns')
353: D401 First line should be in imperative mood ('Return', not 'Returns')
353: D400 First line should end with a period (not 'k')
366: D401 First line should be in imperative mood ('Return', not 'Returns')
366: D400 First line should end with a period (not 'k')
385: D400 First line should end with a period (not 's')
410: D400 First line should end with a period (not 'r')
430: D401 First line should be in imperative mood ('Set', not 'Sets')
458: D210 No whitespaces allowed surrounding docstring text
458: None: None
458: D205 1 blank line required between summary line and description (found 0)
488:18: E203 whitespace before ':'
489:31: E203 whitespace before ':'
490:20: E203 whitespace before ':'
491:29: E203 whitespace before ':'
492:15: E203 whitespace before ':'
493:18: E203 whitespace before ':'
494:20: E203 whitespace before ':'
495:18: E203 whitespace before ':'
496:19: E203 whitespace before ':'
497:24: E203 whitespace before ':'
498:18: E203 whitespace before ':'
534:33: E128 continuation line under-indented for visual indent
535:33: E128 continuation line under-indented for visual indent
536:33: E128 continuation line under-indented for visual indent
567:5: E303 too many blank lines (2)
643:1: E302 expected 2 blank lines, found 1
643: D210 No whitespaces allowed surrounding docstring text
643: None: None
643: D205 1 blank line required between summary line and description (found 0)
665:13: E128 continuation line under-indented for visual indent
701:41: E261 at least two spaces before inline comment
744:1: E302 expected 2 blank lines, found 1
744: D400 First line should end with a period (not 'k')
750:24: E203 whitespace before ':'
752:1: E302 expected 2 blank lines, found 1
752: D401 First line should be in imperative mood ('Return', not 'Returns')
752: D400 First line should end with a period (not 'k')
762:1: E302 expected 2 blank lines, found 1
762: D400 First line should end with a period (not 'S')
769:1: E302 expected 2 blank lines, found 1
769: D401 First line should be in imperative mood ('Return', not 'Returns')
769: D400 First line should end with a period (not 'm')
779:1: E302 expected 2 blank lines, found 1
779: D400 First line should end with a period (not 'm')
785:28: E203 whitespace before ':'
787:1: E302 expected 2 blank lines, found 1
787: D401 First line should be in imperative mood ('Update', not 'Updates')
792:13: E128 continuation line under-indented for visual indent
794:1: E302 expected 2 blank lines, found 1
794: D401 First line should be in imperative mood ('Update', not 'Updates')
799:13: E128 continuation line under-indented for visual indent
801:1: E302 expected 2 blank lines, found 1
804:9: E128 continuation line under-indented for visual indent
811:1: E302 expected 2 blank lines, found 1
811: D400 First line should end with a period (not 'e')
818:1: E302 expected 2 blank lines, found 1
818: D205 1 blank line required between summary line and description (found 0)
844:1: E302 expected 2 blank lines, found 0
844: D401 First line should be in imperative mood ('Return', not 'Returns')
844: D209 Multi-line docstring closing quotes should be on a separate line
844: D205 1 blank line required between summary line and description (found 0)
844: D208 Docstring is over-indented
866: D401 First line should be in imperative mood ('Thi', not 'This')
866: D400 First line should end with a period (not ',')
866: D205 1 blank line required between summary line and description (found 0)
904:1: E302 expected 2 blank lines, found 1
904: D400 First line should end with a period (not 'n')
904: D205 1 blank line required between summary line and description (found 0)
915:1: E302 expected 2 blank lines, found 1
915: D202 No blank lines allowed after function docstring (found 1)
915: D205 1 blank line required between summary line and description (found 0)
944:5: E266 too many leading '#' for block comment
975:68: F821 undefined name 'Tru'
986:13: E266 too many leading '#' for block comment
993:1: E302 expected 2 blank lines, found 1
993: D401 First line should be in imperative mood ('Submit', not 'Submits')
993: D209 Multi-line docstring closing quotes should be on a separate line
993: D202 No blank lines allowed after function docstring (found 1)
993: D400 First line should end with a period (not 'l')
993: D205 1 blank line required between summary line and description (found 0)
993: D208 Docstring is over-indented
997:5: E266 too many leading '#' for block comment
1000:5: E266 too many leading '#' for block comment
1002:5: E266 too many leading '#' for block comment
1005:5: E266 too many leading '#' for block comment
1015:9: E128 continuation line under-indented for visual indent
1020:5: E266 too many leading '#' for block comment
1025: D401 First line should be in imperative mood ('Return', not 'Returns')
1025: D209 Multi-line docstring closing quotes should be on a separate line
1025: D400 First line should end with a period (not 'k')
1025: D205 1 blank line required between summary line and description (found 0)
1030:9: E128 continuation line under-indented for visual indent
1035:13: E128 continuation line under-indented for visual indent
1089: D400 First line should end with a period (not 'n')
1095:25: E127 continuation line over-indented for visual indent
1103: D400 First line should end with a period (not 'n')
1109: D401 First line should be in imperative mood ('Run', not 'Runs')
1109: D209 Multi-line docstring closing quotes should be on a separate line
1109: D202 No blank lines allowed after function docstring (found 1)
1109: D205 1 blank line required between summary line and description (found 0)
1119:5: E266 too many leading '#' for block comment
1126:13: E128 continuation line under-indented for visual indent
1135:5: E266 too many leading '#' for block comment
1139:13: E128 continuation line under-indented for visual indent
1162:17: E266 too many leading '#' for block comment
1163:205: E261 at least two spaces before inline comment
1164:193: E261 at least two spaces before inline comment
1174:13: E128 continuation line under-indented for visual indent
1179:5: E266 too many leading '#' for block comment
1186:5: E266 too many leading '#' for block comment
1189:5: E266 too many leading '#' for block comment
1211:13: E266 too many leading '#' for block comment
1213:17: E266 too many leading '#' for block comment
1220:17: E266 too many leading '#' for block comment
1230:13: E266 too many leading '#' for block comment
1232:9: E266 too many leading '#' for block comment
1253: D401 First line should be in imperative mood ('Print', not 'Prints')
1263:9: E128 continuation line under-indented for visual indent
1265:9: E128 continuation line under-indented for visual indent
1267:9: E128 continuation line under-indented for visual indent
1268:9: E128 continuation line under-indented for visual indent
1272:9: E128 continuation line under-indented for visual indent
1273:9: E128 continuation line under-indented for visual indent
1274:9: E128 continuation line under-indented for visual indent
1281:9: E128 continuation line under-indented for visual indent
1294:1: E302 expected 2 blank lines, found 1
1298:13: E128 continuation line under-indented for visual indent
1303:1: E302 expected 2 blank lines, found 1
1306:13: E128 continuation line under-indented for visual indent
1308:25: E261 at least two spaces before inline comment
1311:1: E302 expected 2 blank lines, found 1
1314:13: E128 continuation line under-indented for visual indent
1322:1: E302 expected 2 blank lines, found 1
1322: D209 Multi-line docstring closing quotes should be on a separate line
1328:13: E128 continuation line under-indented for visual indent
1332:1: E302 expected 2 blank lines, found 1
1337:1: E302 expected 2 blank lines, found 0
1354:1: E302 expected 2 blank lines, found 1
1354: D205 1 blank line required between summary line and description (found 0)
1369:1: E302 expected 2 blank lines, found 1
1369: D400 First line should end with a period (not 'r')
1369: D205 1 blank line required between summary line and description (found 0)
1386:63: E502 the backslash is redundant between brackets
1387:13: E128 continuation line under-indented for visual indent
1389:57: E261 at least two spaces before inline comment
1396:63: E502 the backslash is redundant between brackets
1397:9: E128 continuation line under-indented for visual indent


1: D100 Missing docstring in public module
83:1: E402 module level import not at top of file
84:1: I101 Imported names are in the wrong order. Should be IndentedHelpFormatter, Option, OptionError, OptionGroup, OptionParser
84:1: E402 module level import not at top of file
86:1: I100 Imports statements are in the wrong order. import os should be before from optparse
86:1: E402 module level import not at top of file
87:1: I201 Missing newline before sections or imports.
87:1: E402 module level import not at top of file
88:1: I100 Imports statements are in the wrong order. import random should be before import pkg_resources
88:1: I201 Missing newline before sections or imports.
88:1: F401 'random' imported but unused
88:1: E402 module level import not at top of file
89:1: E402 module level import not at top of file
90:1: E402 module level import not at top of file
91:1: E402 module level import not at top of file
92:1: F401 'string' imported but unused
92:1: E402 module level import not at top of file
93:1: E402 module level import not at top of file
94:1: E402 module level import not at top of file
95:1: I201 Missing newline before sections or imports.
95:1: E402 module level import not at top of file
96:1: I100 Imports statements are in the wrong order. from warnings should be before from six
96:1: I201 Missing newline before sections or imports.
96:1: E402 module level import not at top of file
97:1: I201 Missing newline before sections or imports.
97:1: F401 'exc' imported but unused
97:1: E402 module level import not at top of file
105: D210 No whitespaces allowed surrounding docstring text
105: None: None
105: D400 First line should end with a period (not 'o')
116: D202 No blank lines allowed after function docstring (found 1)
116: D400 First line should end with a period (not 'g')
116: D205 1 blank line required between summary line and description (found 0)
122:5: E266 too many leading '#' for block comment
125:5: E266 too many leading '#' for block comment
137:5: E266 too many leading '#' for block comment
153:5: E266 too many leading '#' for block comment
158:5: E266 too many leading '#' for block comment
164:5: E266 too many leading '#' for block comment
168:5: E266 too many leading '#' for block comment
219:5: E266 too many leading '#' for block comment
226:5: E266 too many leading '#' for block comment
267:5: E266 too many leading '#' for block comment
272:5: E266 too many leading '#' for block comment
277:5: E266 too many leading '#' for block comment
285:5: E266 too many leading '#' for block comment
289:5: E266 too many leading '#' for block comment
311:5: E266 too many leading '#' for block comment
315: D103 Missing docstring in public function
321: D400 First line should end with a period (not 's')
321: D205 1 blank line required between summary line and description (found 0)
337: D205 1 blank line required between summary line and description (found 0)
344:5: E266 too many leading '#' for block comment
346:21: E127 continuation line over-indented for visual indent
347:5: E266 too many leading '#' for block comment
351:50: E502 the backslash is redundant between brackets
352:25: E127 continuation line over-indented for visual indent
352:66: E502 the backslash is redundant between brackets
353:25: E127 continuation line over-indented for visual indent
364: D205 1 blank line required between summary line and description (found 0)
371:5: E266 too many leading '#' for block comment
373:21: E127 continuation line over-indented for visual indent
374:5: E266 too many leading '#' for block comment
377:5: E266 too many leading '#' for block comment
393: D400 First line should end with a period (not '6')
393: D205 1 blank line required between summary line and description (found 0)
410: D400 First line should end with a period (not 'r')
410: D205 1 blank line required between summary line and description (found 0)
418:5: E266 too many leading '#' for block comment
420:14: E127 continuation line over-indented for visual indent
421:5: E266 too many leading '#' for block comment
424:16: E126 continuation line over-indented for hanging indent
425:13: E266 too many leading '#' for block comment
439:45: E128 continuation line under-indented for visual indent
440:45: E128 continuation line under-indented for visual indent
449: D400 First line should end with a period (not 'd')
449: D205 1 blank line required between summary line and description (found 0)
477: D209 Multi-line docstring closing quotes should be on a separate line
477: D400 First line should end with a period (not 'n')
477: D205 1 blank line required between summary line and description (found 0)
503:32: F841 local variable 'err' is assigned to but never used
523: D209 Multi-line docstring closing quotes should be on a separate line
523: D400 First line should end with a period (not 'n')
523: D205 1 blank line required between summary line and description (found 0)
537: D200 One-line docstring should fit on one line with quotes (found 3)
542:5: F401 'run_sql' imported but unused
556: D400 First line should end with a period (not 'N')
556: D205 1 blank line required between summary line and description (found 0)
566:5: E266 too many leading '#' for block comment
568:5: E266 too many leading '#' for block comment
570:5: E266 too many leading '#' for block comment
573:9: E266 too many leading '#' for block comment
574:9: E266 too many leading '#' for block comment
590:9: E266 too many leading '#' for block comment
596:49: E128 continuation line under-indented for visual indent
601:9: E266 too many leading '#' for block comment
607:82: E231 missing whitespace after ','
622: D400 First line should end with a period (not 's')
622: D205 1 blank line required between summary line and description (found 0)
641: D209 Multi-line docstring closing quotes should be on a separate line
641: D205 1 blank line required between summary line and description (found 0)
666: D103 Missing docstring in public function
676: D103 Missing docstring in public function
711:72: E502 the backslash is redundant between brackets
712:20: E127 continuation line over-indented for visual indent
712:44: E231 missing whitespace after ','
716:35: E261 at least two spaces before inline comment
735:21: E128 continuation line under-indented for visual indent
735:93: E231 missing whitespace after ','
753:50: E231 missing whitespace after ','
773:48: E231 missing whitespace after ','
826: D400 First line should end with a period (not 'e')
826: D205 1 blank line required between summary line and description (found 0)
848: D400 First line should end with a period (not 's')
848: D205 1 blank line required between summary line and description (found 0)
863: D400 First line should end with a period (not 'r')
863: D205 1 blank line required between summary line and description (found 0)
873:10: E122 continuation line missing indentation or outdented
886: D200 One-line docstring should fit on one line with quotes (found 3)
901: D400 First line should end with a period (not 'y')
901: D205 1 blank line required between summary line and description (found 0)
920: D400 First line should end with a period (not 'L')
920: D205 1 blank line required between summary line and description (found 0)
935: D400 First line should end with a period (not 's')
935: D200 One-line docstring should fit on one line with quotes (found 3)
949: D400 First line should end with a period (not 's')
949: D200 One-line docstring should fit on one line with quotes (found 3)
963: D400 First line should end with a period (not 'd')
963: D200 One-line docstring should fit on one line with quotes (found 3)
977: D200 One-line docstring should fit on one line with quotes (found 3)
991: D202 No blank lines allowed after function docstring (found 1)
994: D203 1 blank line required before class docstring (found 0)
994: D204 1 blank line required after class docstring (found 0)
994: D400 First line should end with a period (not 'l')
1110: D210 No whitespaces allowed surrounding docstring text
1110: None: None
1110: D400 First line should end with a period (not 's')
1149:9: E266 too many leading '#' for block comment
1205:21: B901 blind except: statement