I don't understand. the assets are only bound during grab?


Using this hashmap is a bit of a problem because it's pretty inefficient in the size/number of keys, and it essentially stringifies the entire object with extra annotation.
Ideally using a proper hashing function on arbitrary objects is what we want. It looks like that's possible with the [object-hash](https://www.npmjs.com/package/object-hash) package, but it needs the `set` and `get` methods implemented as it's not really intended as a key-value store.
Looks like a marriage between hashmap and object-hash will be ideal.


Actually all that code was just moved into a function, so it's all being covered by this call (shown as the added code above).
````````
$fields = $this->wire('modules')->getModuleConfigInputfields($moduleName);
````````
I think I need a test case to see what you are talking about. I've tried installing a couple ConfigurableModule modules that I have locally, but everything is working normally. I will try installing the Blog module next. But if there's anything specific I should look for during installation, please let me know.


Grosso modo c'est des fichiers compilés ce qui veut dire qu'il changent tout le temps et devraient faire partie des fichiers ignorés (ça alourdi le dépot). Il y a généralement 2 raisons pour pas versionner les fichiers compilés :
1. Ils sont compilés donc inutile de les versionnés (redondant mais bon j'insiste)
2. Ils changent à chaque compilation donc si 2 personnes compilent pour tester avant de commit grosso modo le 2e il se prend un méchant merge conflict dans la gueule.

D'ailleurs vous pouvez voir en regardant les recap des commits que ces fichiers changent quasi à chaque commit.

Sinon quelqu'un sait pourquoi on voit des fichiers source dans les commit mais sur github quand on cherche le code source y rien ?


nevermind j'ai vu la réponse sur facebook


A downside of BunnyMock is that it can not mock `Bunny::Channel` so you have to test double it.


:godmode:


Okay just installed ProcessBlog, but can't detect any errors. Maybe I just don't know what to look for, but it appears like it installed normally to me?


this is mistake.
Symbolic Link remove.
https://github.com/movabletype/movabletype/commit/f92ea66e3fb626437015c28a6aa5e85fbd2ed2d9


Congratulation, great work with this patch and the "update_stats" patch.


I will CC this to the issue report, as I'm not sure if you'll find your way back into these commit comments which are little hidden. :)


Is that right to left?
For what purpose?


fireball-x/dev#549:加入 mouseenter 和 mouseleave 事件


The user should be asked, with a dialog, if he wants to download the file again.

There is no GUI code in `arduino-core` so an exception should be thrown and catched in the GUI, that is exactly what the function already did before your PR.


Without having it tested, I think this is missing the TrackableActivity where we apply the same saving mode...


اتشرف الى ادارة هده المؤسسة المحترمة ان تلبي طلبي وفي اسرع وقت ممكن  واود ان ادكركم انها المرة الاولى لطلبكم ان ترسلوا 120 ملين دولار عبر بنك المغرب مرفوقا بقن لاسحب المبلغ وفي انتظاركم لردكم تقبلوا فائق احترماتي الغالية  العقيد حسن شفيقي// رقم البطاقةالبريدية 3328 وشكرا


Ah true. I overlooked the protocol. The thing is firefox is proposing Mibbit per default and freenode has blocked its use on their network, so I wondered whether you would rather propose their webchat url instead.
WDYT?


Looks like you misspelled "canola".


Yes!


Wow. Thanks! Love it.


WTF


Seems very pleasing, but which is better? Often times I hear advice to atomise, avoid instance variables, apply Law of Demeter, hence I try various ways of coding and sometimes miss :P


`JQL_TEMPLATE` field shouldn't be `static` as it is a configuration of given instance. There will not be a conflict in unit tests then.
As this field is not `final` then it should be named in camel case, so `jqlTemplate`.


You could have rewritten the history (rebase) to avoid this commit. Next time!


Hi Charles,
I found you update ns3 to 3.22 version.   How can I rebuild OpenNet to update to ns3.22?
Do I need to reuse ./install.sh -a ?
I also found ns3.21 doesn't  build click and openflow module, how is your SDN WLAN work without these two modules? Is there another documentation?
Best Regards!


Would you mind to provide the pointer to the kernel's thread object instead of the thread_id? That way the additional lookup can be omitted, the return value becomes always true, and therefore can be omitted too. Moreover, it is then already in sync with my work in commit 60b3826ec1c40e92543b45ec70fc43647214179a


test


What is the purpose of using (window).load ?


note that this happened on client so we know when journey happens


Let's explain *why*. i.e. https://github.com/md-systems/globalredirect/pull/6#issuecomment-91508844 + https://github.com/md-systems/globalredirect/pull/6#issuecomment-91510065


s/Globalredirect/Global Redirect/


Good point, i'll refactor it to not be so confusing.
I thought about making it final, but i'm not sure how often one could run configuration, that possibly changes this field, so it's better to change variable name to "jqlTemplate".


A few comments at this stage:
- Would it be possible to have more comments on
- CalculateAccidX returns bool, but this seems not to be used. Can you verify/change this?


s/rendered/'rendered'/

and an @see to `GlobalredirectSettingsCacheTag`, which will have the explanation for why we do this. Or perhaps the explanation should live here, and `GlobalredirectSettingsCacheTag` should refer to this place. Either way.


I feel the term 'core_quota' pretty misleading, because something with 'core' in the name within the core component is mostly associated with the component e.g.: core_pd ...
What about 'minimum_quota' or something similar?


can this be in lib.js


Yup. I think this falls under the category of 'Silly bug' or perhaps "I-shouldn't-be-coding-but-sleeping" bug


What happens if there are multiple `_remove` roles and the run fails in the middle of one of them?  Shouldn't each one be removed from the runlist and `to_remove` queue immediately after it is completed?  This would reduce failure windows in the orchestration workflow.


> But that would break if you want the child's fd 4 and 5 to be the partent's fd 42, right? because after you dup 42 into 4 you'd close it and on the next iteration you'd fail.

You're right, good point.  Does the same logic apply to the `uv__close(close_fd)` call?


Не бачу сэнса рабіць паліморфныя класы, а потым апрацоўваць іх праз світч.

Што наконт будачага дызайну, маю такія думкі адзін працэсар апрацоўваецца ў адным патоку, агульная памяць разшареная, магчыма працуе праз менеджэр памяці які таксама ў асобным патоку. Апрацоўку каманд ажыцяўляць праз масіў функцый (альбо замыканій).


Yes, I've changed this here and below (similar) to:

    if (systemForServer == null) {
      throw new Error("releaseServer called with systemForServer == null");
    }


Should be ``zh_CN`` here, thanks.


See above for a more direct approach to throwing.


@redox do you know that this flag just change the timeout ? :)


Um.. this is a 442 error page


в смысле динамические? Если где размер хранится - там же и хранится, где
был. Просто проверяется не на 100, а на размер моника.
А если показывать сами единицы измерения, типа пиксели или проценты - то
сие не надо, ибо динамическая панель является скрытой настройкой, ее не
будет в конфигураторе до 0.4 точно. А для 0.3 даже еще много - я еще не все
апплеты с LXPanel разделил и портировал (нет netstatus, monitors, indicator)

2015-04-10 16:23 GMT+06:00 repsac <notifications@github.com>:

> Так ведь всёравно динамические юниты, надо вводить переменную.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/repsac-by/vala-panel/commit/74cf216e334ced9713b048296d14bfacdd414077#commitcomment-10663321>
> .
>


This is the 500 error page


@7thcubic  Can u please use here something like `realpath('..')`  and `DIRECTORY_SEPARATOR` ?


Безумоўна вы правы, але гэта assert, а не логіка праграмы, ён працуе толькі ў не рэлізнай зборцы.

Саша, вы знаёмы з кантрактным праграмаваннем?


Build is still broken. Please see http://ci.cgeo.org/job/c-geo/3641/console
Build was first broken at http://ci.cgeo.org/job/c-geo/3640/


Done


please remove the commented code


making sbt-users less unhappy ;)


I suppose it's mostly hypothetical for small reads.  Okay, never mind then.


commented code


I'm not 100% sure, but it's in my GCLI tree and not showing up in 'git status', so I've committed it, and it should get into github someway if it's not there already.


Is there a reason to continue instead of calling uv__write_int() and exiting?


I don't think so, because close_fd will point to a fd we just opened to /dev/null, in order to redirect stdin, stdout and stderr to it, so in that case use_fd was -1.


This change is not working well on windows. Get the following error:

/bin/sh: -c: line 2: syntax error: unexpected end of file
make: *** [obj/NAZE/drv_adc.o] Error 2


Fixed!


not really, lets fail. I'll also do that in the F_DUPFD call then.


these three should sufficient :)


I didn't see your comment @davisagli you put in https://docs.google.com/document/d/1duXEAsoCXp4u0Tp-KYmBjEtLWb_zi3xgKQVTobdCoyU/edit
"This is a hard one to solve. We're relying on Chameleon's support for putting a full dictionary in tal:attributes to specify a number of different data attributes at once. But that isn't supported by the TAL parser used by i18ndude."

Thanks for fixing some of the issues btw.
Well, is lingua supporting it? we can maybe use lingua instead of i18ndude, it may be a lot of work, I don't really know right know.


Readme file


test


commentaire


Note that `emsdk` also has a single `git://` link which should probably be changed too.


@mattheworiordan There are a bit more things going under the hood that it makes it work.

The purpose of the locking here is to lock access to the map:

```go
c.listenerMtx.RLock()
callbacks := c.listeners[connState]
c.listenerMtx.RUnlock()
```

There's no need to lock the []ConnListener, as its always a copy (meaning we always append to the slice, and append returns new slice). So even if the value of c.listeners[connState] is set to other slice, the one we're ranging over is not affected, that's why it's safe to range over it without a lock.

Right now I'm working on the realtime client so I'd simplify the implementation either way, the purpose of the this fix series was to have test not fail randomly if I change something / add more tests.

Ps I'm not so familiar with Ruby internals, from what I read in Ruby doc `clone` performs shallow copy of the hashmap, so if no locking is involved I could imagine the values of the callback list might by altered. I'm not sure if Ruby is, but in Go copy / map assignments are not thread-safe.


I just test the blame


We may need to manually delete the file in `postinstall`


Nice!


Yeah, a mouthful. I think the proof that we don't do it regularly is that I needed to look up how to do it.


From [Apple Documentation - Creating Custom Container View Controllers](https://developer.apple.com/library/ios/featuredarticles/ViewControllerPGforiPhoneOS/CreatingCustomContainerViewControllers/CreatingCustomContainerViewControllers.html) Apple mentions that a call to `removeFromParentViewController` automatically calls `didMoveToParentViewController:`:

> Calling the removeFromParentViewController method automatically calls the child’s didMoveToParentViewController: method.


This is ok, but I was wondering whether we want to include the exception name also, and not only the message, by using toString() instead?


Yes you're right. server and client is still messed up in my head.


You can simply run the install.sh. It should help you do all the works.

OpenNet does not use the OpenFlow provided by ns-3. OpenNet is a combination of Mininet and ns-3. The Mininet takes care about the OpenFlow part, while the ns-3 takes care about the wireless simulation. The OpenvSwitch (OVS) used by Mininet provides better compatibility to the latest OpenFlow protocol.
You can find more detail in the paper entitled "OpenNet: A simulator for software-defined wireless local area network" pushlished in IEEE WCNC 2014.


Ar planuoji šitam pataisymui kurti pull request?


done


I don't really know how how, but this worked :+1: (#1787)


I just realized this change is good for a second reason: the `continue` introduces a bug where the loop starts counting from zero again. :-)


@mpdude fixed in https://github.com/symfony/symfony/pull/14301


please create an issue


Right now, `GcliActor._getRequisition()` calls `commands-index.js:gcliInit.loadServer()` which in turn does `require("definitions").defaultTools`.

An alternate solution would be to have `GcliFront.initialize` do `require("definitions").defaultTools` and then call `gcliActor.addItemsMyModule`.

I.E.: Rather than have the server work out what commands it has, have the client inject them in.


Build is still broken. Please see http://ci.cgeo.org/job/c-geo/3642/console
Build was first broken at http://ci.cgeo.org/job/c-geo/3640/


I think we're agreed that we shouldn't do that in this patch though.


This commit also fixes `--no-terminal` not including `--really-quiet` (it made no sense to print to console that's supposed to be disabled).

(Warnings and errors are still printed, though.)


Can someone kindly explain why is the percentage not simply (count*100/max)? Is this some other metric? I am asking because I have 2 models, one having a single record and the other having two. So, I was expecting the former progress bar to be at 50% and the latter at 100%, whereas I am getting 63% and 100% respectively.


``m_config_preparse_command_line()`` sets the terminal option, and update_logging acts on it. So update_logging had to be called afterwards it. And if the terminal is not initialized, --input-terminal is ignored.


Beware this changed to `accounts_user`


Oops, missed that. Fixed with 076d9311fa513c499fb4a0b4371ac8cfd546811e.


If you look under the compile compile task you will see it is clearly documented under source and target.  I can add animal sniffer no problem.  Just be aware it doesn't support jdk8 in case this library is headed there.  If you have time poke around my github at base parent.  Its maven on steroids and fully works.

--- Original Message ---

From: "Ceki Gulcu" <notifications@github.com>
Sent: April 10, 2015 6:06 AM
To: "qos-ch/slf4j" <slf4j@noreply.github.com>
Cc: "Jeremy Landis" <jeremylandis@hotmail.com>
Subject: Re: [slf4j] Set Java 5 in parent and remove elsewhere (2cae64b)

Removing the repetitive declaration of maven-compiler-plugin is good. On the other hand,  I am reluctant about relying on seemingly implicit behavior for the "maven.compiler.source" and "maven.compiler.target" properties. The documentation on these properties is sparse. It could be quite problematic if these properties were no longer supported and the build defaulted to some other target. Frankly, it would be a nightmare of epic proportions as published artifacts cannot be recalled. I going to play it safe and declare the compiler plugin and set the source/target explicitly.

As a more concrete safety measure, we should use the animal-sniffer-plugin to provide an additional safety net.

---
Reply to this email directly or view it on GitHub:
https://github.com/qos-ch/slf4j/commit/2cae64b236c439dae423d140ee26195a6ba23f4f#commitcomment-10663135


:beers:


I did not understand the change of meaning for isSemi. It would be good to give an example.

Previously, for `class Meter(val length: Double) extends AnyVal`.

If isSemi:  Meter erases to ErasedValueType(Meter)
Otherwise: Meter erases to Double

Now, what is the meaning? If it is different, we probably also need a different name.


>And if the terminal is not initialized, --input-terminal is ignored.
This is the part that was missing. Thanks. I thought something managed config option cross-dependencies within the `m_config_preparse_command_line` (in which case this would make no difference).


Thanks for the detailed explaination,it helps a lot!


Hi all,

This is a nice new feature from Chang-Hua (PMLs ported to GPUs) but it
did not go through BuildBot and thus maybe did not compile right on all
machines.

Chang-Hua, could you please submit it again but let it go through
BuildBot? (i.e., do not accept the pull request on GitHub.com, just let
BuildBot handle it)

Please do a "git pull" before because David has reverted some recent
changes.

Thanks,
Dimitri.

On 04/09/2015 11:08 PM, David Luet wrote:
> I reverted it
>
> git reset --hard 3512fff3
>
> On Thu, Apr 9, 2015 at 4:53 PM, Elliott Sales de Andrade <
> notifications@github.com> wrote:
>
>  > I'm not totally sure, but it doesn't seem right to me either.
>  >
>  > CC @specfem3d-zhang-ksu <https://github.com/specfem3d-zhang-ksu> because
>  > he probably won't get these notifications since his email is not
> right and
>  > this commit is not attributed to him.
>  >
>  > —
>  > Reply to this email directly or view it on GitHub
>  >
> <https://github.com/geodynamics/specfem3d/commit/cf6e22e8c4c93f732ba7a5895eb2d9ed37c34473#commitcomment-10654944>
>  > .
>  >
>
>
>
> --
> David Luet
> Linux Administrator/Software & Programming Analyst
> Department of Geosciences & PICSciE
> Princeton University
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/geodynamics/specfem3d/commit/cf6e22e8c4c93f732ba7a5895eb2d9ed37c34473#commitcomment-10655204>.
>

--
Dimitri Komatitsch
CNRS Research Director (DR CNRS), Laboratory of Mechanics and Acoustics,
UPR 7051, Marseille, France    http://komatitsch.free.fr


Hi Martin,
alles in Ordnung, danke der Nachfrage ;-)

Gruß Rolf


Ah cool I almost thought so, but just copied straight from https://github.com/artificialio/sane/blob/master/tests/lint/eslintTest.js


OK


The variable names inside list comprehensions are not in their own scope, they are part of the surrounding function's scope. Using order as a name here causes a shadowing of the function argument of the same name, and we depend on the function argument being there in the line below.


The HTTPClient is widely used everywhere. It would be much better to centralize the calls within a single service


Using 3 here is still correct, otherwise you don't count the item used to do the search. The number would be off by one.


Ta. Ye, let's continue the conversation over there.


@cpennington ok, I'll see what I can do, but after I'm done with what I was doing when discovered this. Thank you for confirmation.


![Uploading screenshot.png . . .]()


I think that's vestigial. I was experimenting with different formatters at one time. Could be removed there too.


thanks Mark!

why pilot.prof?  we have agent.out/err/log ?


ah thats a lot of bugs >.> thankyou


包主

进口（
	“编码/ JSON”
	“旗帜”
	“FMT”
	“github.com/github/git-lfs/lfs”
	“OS”
	“OS / EXEC”
	“路径/文件路径”
	“弦”
）

VAR（
	在BuildOS = flag.String（“OS”，“”，“OS目标：达尔文，FreeBSD的，LINUX，窗户”）
	BuildArch = flag.String（“弓”，“”，“拱目标：386，AMD64”）
	BuildAll = flag.Bool（“全部”，假的，“构建所有架构”）
	使用showHelp = flag.Bool（“帮助”，假“显示帮助”）
	matrixKeys =地图[字符串]字符串{
		“达尔文”：“苹果”
		“FreeBSD的”：“FreeBSD的”，
		“LINUX”：“Linux的”，
		“窗口”：“窗口”，
		“AMD64”：“AMD64”
	}
）

FUNC mainBuild（）{
	CMD，ERR：= exec.Command（“脚本/ FMT”）输出（）
	如果犯错！= {为零
		恐慌（ERR）
	}

	如果len（CMD）> 0 {
		fmt.Println（字符串（CMD））
	}

	如果*使用showHelp {
		fmt.Println（“用法：脚本/引导[-os] [-arch] [-all]”）
		flag.PrintDefaults（）
		回报
	}

	buildMatrix：=做（图[字符串]发布）

	差错：= FALSE

	如果* BuildAll {
		为_，在BuildOS：=范围。[] {字符串“达尔文”，“freebsd的”，“LINUX”，“窗口”} {
			为_，buildarch：=范围。[] {字符串“386”，“AMD64”} {
				如果错误：=构建（在BuildOS，buildarch，buildMatrix）; 犯错！= {为零
					误码=真
				}
			}
		}
	}其他{
		建设（*在BuildOS，* BuildArch，buildMatrix）
		误码=真//跳过构建矩阵的东西
	}

	如果！出错{
		由，ERR：= json.Marshal（buildMatrix）
		如果犯错！= {为零
			fmt.Println（“错误编码生成矩阵JSON：”ERR）
			os.Exit（1）
		}

		文件错误：= os.Create（“斌/发行/ build_matrix.json”）
		如果犯错！= {为零
			fmt.Println（“错误创建build_matrix.json：”ERR）
			os.Exit（1）
		}

		写的，错误：= file.Write（所）
		file.Close（）

		如果犯错！= {为零
			fmt.Println（“错误的写作build_matrix.json”，ERR）
			os.Exit（1）
		}

		如果jsonSize：= LEN（所）; 写！= {jsonSize
			fmt.Printf（“有望写入％d字节，居然写了％D \ N”，jsonSize，写）
			os.Exit（1）
		}
	}
}

FUNC版本（在BuildOS，buildarch字符串，buildMatrix地图[字符串]发布）错误{
	addenv：= LEN（在BuildOS）> 0 && LEN（buildarch）> 0
	名称：=“混帐lfs-”+ lfs.Version
	DIR：=“斌”

	如果addenv {
		fmt.Printf（“共建％S /％S \ N”，在BuildOS，buildarch）
		DIR = filepath.Join（DIR，“发布”，在BuildOS +“ - ”+ buildarch，名）
	}

	filepath.Walk（“CMD /混帐-LFS”，FUNC（路径字符串，信息os.FileInfo，宁可错误）错误{
		如果！strings.HasSuffix（路径“。去”）{
			返回nil
		}

		CMD：= filepath.Base（路径）
		CMD = CMD [0：LEN（CMD）-3]
		返回buildCommand（路径，目录，在BuildOS，buildarch）
	}）

	如果addenv {
		错误：= os.MkdirAll（DIR，0755）
		如果犯错！= {为零
			fmt.Println（“错误设置的安装程序：\ N”，err.Error（））
			返回ERR
		}

		ERR = setupInstaller（在BuildOS，buildarch，DIR，buildMatrix）
		如果犯错！= {为零
			fmt.Println（“错误设置的安装程序：\ N”，err.Error（））
			返回ERR
		}
	}

	返回nil
}

FUNC buildCommand（路径，目录，在BuildOS，buildarch字符串）错误{
	addenv：= LEN（在BuildOS）> 0 && LEN（buildarch）> 0
	名称：= filepath.Base（路径）
	名称=名称[0：LEN（名称）-3]

	斌：= filepath.Join（目录，名称）

	如果在BuildOS ==“窗口”{
		斌=斌+“.EXE”
	}

	CMD：= exec.Command（“走出去”，“建”，“O”，垃圾桶，路径）
	如果addenv {
		cmd.Env = [] {字符串
			“全球海洋观测系统=”+在BuildOS，
			“GOARCH =”+ buildarch，
			“GOPATH =”+ os.Getenv（“GOPATH”），
			“GOROOT =”+ os.Getenv（“GOROOT”），
		}
	}

	输出错误：= cmd.CombinedOutput（）
	如果len（输出）> 0 {
		fmt.Println（字符串（输出））
	}
	返回ERR
}

FUNC setupInstaller（在BuildOS，buildarch，DIR字符串，buildMatrix地图[字符串]发布）错误{
	如果在BuildOS ==“窗口”{
		返回winInstaller（在BuildOS，buildarch，DIR，buildMatrix）
	}其他{
		返回unixInstaller（在BuildOS，buildarch，DIR，buildMatrix）
	}
}

FUNC unixInstaller（在BuildOS，buildarch，DIR字符串，buildMatrix地图[字符串]发布）错误{
	fullInstallPath：= filepath.Join（DIR，“install.sh”）
	CMD：= exec.Command（“CP”，“脚本/ install.sh.example”，fullInstallPath）
	如果错误：= logAndRun（CMD）; 犯错！= {为零
		返回ERR
	}

	如果错误：= os.Chmod（fullInstallPath，0755）; 犯错！= {为零
		返回ERR
	}

	名称：= zipName（在BuildOS，buildarch）+的“.tar.gz”

	addToMatrix（buildMatrix，在BuildOS，buildarch，名）

	CMD = exec.Command（“焦油”，“CZF”，“../"+name，filepath.Base（DIR））
	cmd.Dir = filepath.Dir（DIR）
	返回logAndRun（CMD）
}

FUNC addToMatrix（buildMatrix地图[字符串]发布，在BuildOS，buildarch，名字符串）{
	buildMatrix [fmt.Sprintf（“％S-％的”，在BuildOS，buildarch）] = {版
		标签：releaseLabel（在BuildOS，buildarch）
		文件名：姓名，
	}
}

FUNC winInstaller（在BuildOS，buildarch，DIR字符串，buildMatrix地图[字符串]发布）错误{
	CMD：= exec.Command（“CP”，“脚本/ install.bat.example”，filepath.Join（DIR，“INSTALL.BAT”））
	如果错误：= logAndRun（CMD）; 犯错！= {为零
		返回ERR
	}

	installerPath：= filepath.Dir（filepath.Dir（DIR））

	名称：= zipName（在BuildOS，buildarch）+“.ZIP”
	全：= filepath.Join（installerPath，名）
	比赛中，犯错：= filepath.Glob（DIR +“/ *”）
	如果犯错！= {为零
		返回ERR
	}

	addToMatrix（buildMatrix，在BuildOS，buildarch，名）

	的args：=使得（[]字符串，LEN（匹配）+2）
	的args [0] =“-j”//垃圾压缩路径
	的args [1] =全
	副本（参数[2：]，匹配）

	CMD = exec.Command（“ZIP”的args ...）
	返回logAndRun（CMD）
}

FUNC logAndRun（CMD * exec.Cmd）错误{
	fmt.Printf（“ - ％S \ N”，strings.Join（cmd.Args，“”））
	如果len（cmd.Dir）> 0 {
		fmt.Printf（“ - 在％s \ N”，cmd.Dir）
	}

	输出错误：= cmd.CombinedOutput（）
	fmt.Println（字符串（输出））
	返回ERR
}

FUNC zipName（OS，拱字符串）{
	返回fmt.Sprintf（“混帐lfs-％S-％S-％的”，操作系统，拱，lfs.Version）
}

FUNC releaseLabel（在BuildOS，buildarch字符串）{
	返回fmt.Sprintf（“％s％S”键（在BuildOS），钥匙（buildarch））
}

FUNC键（K线）{字符串
	如果s，确定：= matrixKeys [K] 好不好{
		返回小号
	}
	复位K
}


Hey guys... please rename the folder from EAT-1 to "upload-form", and the HTML file can be index.html or upload.html.... folders and filenames should be descriptive and represent their content and purpose.  It's good enough to just put EAT-1 in your commit message... that's enough linkage back to the Jira story.


Why go though the trouble of adding these methods to companion objects? Could you not simply have two synthetic methods in Definitions that do the job for all value classes?


Having another convenience copy constructor is a nice idea. I'll review it soon, i.e. once this proposal craziness is over.


This commit indicates it is not a good idea to duplicate packstream in two places to me.


Nothing else in the class uses or needs to know about access_token or token_expiry.
How about something like
```
try:
    self.access_token
    self.token_expiry
except AttributeError:
    self.access_token = ''
    self.token_expiry = 0
````


I was thinking maybe the X variance picked up some shot noise for calibrating even numbers of 90's or 180's but adding them in quadrature should cover us.

You're exactly right that we're not estimating the angle at each step (just which half) so your criteria is reasonable for determining that.


<!-- PMABOT:SOB -->
This commit is missing Signed-Off-By line to indicate that you agree with phpMyAdmin Developer's Certificate of Origin. Please check [contributing documentation](https://github.com/phpmyadmin/phpmyadmin/blob/master/CONTRIBUTING.md) for more information.


@orta I love the Artsy Coins :+1:


Not sure whether we can use isSemi for this. Don't we need a third case, where a value class like Meter erases to Double? For instance when computing erased signatures for bridge construction? So, it seems we actually have a three way decision (again taking Meter as an example)

    Meter -> Double                                                   - full erasure
    Meter -> ErasedValueClass(Meter, Double)        - semi erasure
    Meter -> Meter                                                      - no erasure

Model with a type like ValueClassErasure = None | Semi |Full, maybe?


According to the docs, the `save()` should also validate the state. However this didn't happen.

Is there a reason why `no_state_validation` defaults to `True`? [django_states/fields.py#L102](https://github.com/gvangool/django-states2/blob/f4704779ae46466d00d7d58a28939e8014610884/django_states/fields.py#L102)

cc @jgeskens @jonathanslenders


You could simplify this considerably by adding an HTML color -> stat name mapping to Stats and replacing the switch with a method call.

```javascript
Stats.colorNames = { '#820080': 'purples', '#0083C7': 'blues' }; // except fully populated

Stats.countColor = function (htmlColor) {
  if (!this.colorNames[htmlColor]) {
    return;
  }

  this[this.colorNames[htmlColor]]++;
}
```


Just as a general style remark; why not writing that:

return p.map(function (x) return Options.isNone(x));

like this?

return p.map(Options.isNone);


Oxford comma or :frogout:


历史图被我搞乱了。。。


好厉害的感觉


ну так не инетересно


Thanks, that was the intent, but I totally botched the lowercase check!


Fair enough!


а на ret зачем умножать?


Please refer to [Logarithmic scale](http://en.wikipedia.org/wiki/Logarithmic_scale) :)


Hi, just put that to lib
but the code still runs on client
and we don't need journey there
what's will be the next step to be taken?


No other command is case insensitive in it's second argument. The command name would be case sensitive too if I had my way but that's a limitation of the framework.


extra spaces


Hello,

I wish I had seen your work prior to starting this :)

Merging would be fine, I'll need to get your branch and see how it works for me,
and then send you any changes I need. How does this work?

BTW we should get in contact with openembedded to have meta-odroid listed somewhere,
so people can find some authoritative source.

Which devices do you have? I have a XU3-lite and a C1.

Thanks for the heads up


No, I don't think so we need try catch,
because as of now we should know what error might occur in the code,
and so that we can rectify our errors,

and make the code more accurate,
if we make try and catch
this will lead of uninformed errors,
which we may not catch in the future.

Let me kknow you idea.


Because the bootstrapper also writes entries.
Same is true for .out/.err ...


The reason why the variable is unnecessary would make up for a nice commit message.


Good catch


So I probably would suggest to undo this change, and in that spirit, also don't use PILOT_ID anywhere.
The pilot is implicit by the fact of where this logfile belongs to. The cu_id is the only variant, and if the uid field is empty, the event is not in the context of a/one CU.

What do you think?


rys ostrovid wrote:
> Warum hast du die Formatierung der floats nach Foundation verschoben?

Damit wir in den Messages darauf zugreifen können.


cool... cmake 98% -.- :D fuck:D need start againxd


Yep, good point


But Im open to the suggestion that agent/pilot are synonyms and that they each cover both shell and python script.


will this always be 47802?


inserted Jippi


Well, it's hard coded due to lack of configuration system... You could make it more flexible, but we saw that this port was available...


Nice


Sure


Requesting grunt-karma package update to 0.12.0 as npm install returns error:

npm ERR! peerinvalid The package karma does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer grunt-karma@0.7.3 wants karma@~0.12.0
npm ERR! peerinvalid Peer karma-firefox-launcher@0.1.4 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-html2js-preprocessor@0.1.0 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-chrome-launcher@0.1.7 wants karma@>=0.9.3
npm ERR! peerinvalid Peer karma-coffee-preprocessor@0.1.3 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-mocha@0.1.10 wants karma@>=0.12.8
npm ERR! peerinvalid Peer karma-script-launcher@0.1.0 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-phantomjs-launcher@0.1.4 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-jasmine@0.1.5 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-requirejs@0.2.2 wants karma@>=0.9


Why is this commented out? We have had problems with people adding expire dates but not setting the time which have lead to expire being set to never.


@patrick033
Hi, in ~/pawno/include/PPC_Speedometer.inc, **right under** the defination of the vehicle textdraw (line 9), place this:

```pawn
TextDrawColor(APlayerData[playerid][VehicleName], 0xFF0000FF);
```
This will make the text red. Feel free to change it to your liking.


merge... @aronstrandberg


How about we preserve the ability just pass the string by doing "opts or {}" here.


The install rule could be improved. Perhaps set:
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)

Then POCHOIR_LIB_PATH could be set to $(CMAKE_LIBRARY_OUTPUT_DIRECTORY)/porchoir (so that it is not mixed up with the .a's and .so's), porchoir in CMAKE_RUNTIME_OUTPUT_DIRECTORY etc?


Line is too long. [156/100]


Since this doesn't fit on a line, would you mind formatting it like this:

```lua
local compile_defaults = {
    optimize=true, pcap_offline_filter=false, ...
}

i.e. normal 3-space indent.


nice catch :)  i wonder, should the option be pcap_offline_filter or just libpcap?  I am thinking maybe just "libpcap" is a better name.  WDYT?


let's not do the "opts or {}" thing here; instead let caller(s) handle lack of opts.


tested and working


just a few small nits.  thank you for humoring me and nice bug catch!


Message should have said 'Upgrade reactor to version 1.1.6.RELEASE (resolves #637).'


So, basically, anyone can run the agent?
Only root or a specified user should.


This method doesn't belong in this class. See below. There is a Rails mechanism for this.


Going to check that. Big Thanks :)


+ distro-branch: rpm-master


```erb
Next your research <%= pluralize(@entity.reviewing_directors_count, 'director') %>...
```


So, there is no variable KARAF_LOG?


@gponsu Esto lo he cambiado porque doy por hecho que es un error, si no tira para atrás el pull ;)


This change makes no sense. Just check out ansible's module utils facts.py implementation.
This fact is being retrieved using a code as simple as:

    try:
        import selinux
        HAVE_SELINUX=True
    except ImportError:
        HAVE_SELINUX=False
    ...
    def get_selinux_facts(self):
        if not HAVE_SELINUX:
            self.facts['selinux'] = False
            return
    ...

So, you never get `ansible_selinux == True`. You either get `False` or a complete `dict` with all the parameters. So, if you want to check for for status without worrying if you have seliux python bindings or not, you would have to use something like `command: getenforce` and register the result while ignoring errors. If you get either Enforcing or Permissive, it's enabled, if you get Disabled or error, well, then it's disabled. While this approach would would skip the statement every single time.


The logic of this method delves to deep into the workings of the data structure; Our goal is to present the information via the presenter. Consider the following.

```ruby
def collaborators_responsible_for_review
  @collaborators_responsible_for_review ||= repository.work_collaborators_responsible_for_review(work: work)
end
```


You can use the controller as syntax with state controllers too:
controller: "#{name}Controller"
controllerAs: name


1: M111 unrecognized component name: BibIndex


Good idea to display id


Le 10/04/2015 13:59, Vincent Zurczak a écrit :
>
> So, there is no variable KARAF_LOG?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/roboconf/roboconf-system-installers/commit/5151864bfcb1fab7034d0595d9e68fec8086ca56#commitcomment-10664573>.
>
No, there is no such variable. The place for karaf logs is specified in
etc/org.ops4j.pax.logging.cfg .


looks good to me ^^


See [this commit](https://github.com/johngrogg/ics-parser/commit/2fd2db6e59229bde7bed2b2745677bc995b6611b#diff-943ec5e7e6b8ee5e1a4a129123fa94d4R257)


This if() isn't really necessary since buffer is a required arg.


Closed Visual Studio Online Task [vso#4345](https://azurecom.visualstudio.com/DefaultCollection/ACOM/_workitems#_a=edit&id=4345): 'This is a test usersnap task submission'

VSO State: Done


Same here


I am confused, why we need the variable dst?


Why CurlBUFFERFile, not CurlBuffer, btw?


JAL, would you mind including some rationale in the commit message in the future? I didn't see any mention of your thinking about this change on #s44 or here.


en eclipse


deleted


Esta maneira de instanciar as imagens está consumindo bastante memória, dá pra fazer com o NSPath e chamar a imagem através do caminho: foto = [UIImage imageNamed:@"nomeDaImagen"];


Can you explain why you chose `nil` the return value? Consider that we have a copyright code that was persisted and was valid.


@saladthieves @mativodminic @JohnAdamsy
i moved android, ios and windows folders into 'mobile' folders.

2015-04-10 9:16 GMT+00:00 John Adams <notifications@github.com>:

> @saladthieves <https://github.com/saladthieves> @mativodominic
> <https://github.com/mativodominic> I hope things don't break. I just
> moved the android code into a folder named android. Mativo I'm sure you're
> familiar with that trick by now, incase Egide requires help.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/C4AProjects/pug/commit/344d6b50fd0ef7d4d1346878d891a2eed72fe0dd#commitcomment-10662296>
> .
>


bin_img=list(Image.open(imname).getdata())


Thanks, yay! Yeah, Moniker is super convenient, saved an api call or twelve lol


I'm thinking this method goes on an Attribute decotorator object; Note that the method has nothing to do with the `WorkDecorator` (it uses none of the work's state, and manipulates the input parameters). That is one indicator that another class is asking to be defined.


Avoid variables with short names like $id. Configured minimum length is 3.


PHPCS: Whitespace found at end of line


PHPCS: Expected 1 newline at end of file; 0 found


Mea culpa


what da fk is dis  ?


Hi,

> Hello,
>
> I wish I had seen your work prior to starting this :)

Yes, it's pitty that we did it twice...

> Merging would be fine, I'll need to get your branch and see how it works for me,
> and then send you any changes I need. How does this work?

I'm not sure if I understand correctly, are you asking for current status? From the first quick tests it seems that everything for ODROID-C1 works as expected - both u-boot and linux are build from sourcecodes (Hardkernel's github repos) and bootable SD card image is created. It can be flashed using dd and it boots.

There is just one issue - with core-image-minimal there is no u-boot.ini and DTB in the /boot directory of the image. I added

```
IMAGE_INSTALL += " \
        u-boot-ini \
        kernel-devicetree \
        "
```

to my image's definition and it works as expected.

What about you layer? Is it "production ready" or it still needs some more work?

> BTW we should get in contact with openembedded to have meta-odroid listed somewhere,
> so people can find some authoritative source.

That's true, probably layers.openembedded.org is the best place. I was just asking in the Yocto thread on ODROID's forum and found that there is no C1 support yet. I found one guy (Christian) also interested in the support for C1 so we made the current layer. Next time I will do better marketing ;)

But the problem is that I have only C1. Other devices in the repository are here only because of the fork, I didn't test them... So it is somehow "production ready" only for C1.

> Which devices do you have? I have a XU3-lite and a C1.

I have C1 only and I won't have any other in the near future.

> Thanks for the heads up

Thanks for you answer,

Tomas


Yes, this allows you to specify a "template" variable when calling the twig ```render_menu()``` function.
If not given, the default will be used, if given, it replaces it.


always use journey, let it fun on client but take extra care when it does


Hmm, instead of this "if cls.ITEM_CLASS == GItem" clause, would it be possible to write a specific GItem.create class method ?
I think it is not needed to have this if here, just write the specific code in a GItem.create class method must be OK.


Very nice.  Thanks!


Не работет для a = 9223372036854775783


Done: https://github.com/akka/akka/issues/17173.


style changed


sir i am trying to compile this kernel for v5 max but during compilation there is dt.img error as shown below

 HOSTCC  scripts/mod/file2alias.o
  HOSTLD  scripts/mod/modpost
  DTC     arch/arm/boot/dts/qcom/../msm8916-sim.dtb
  DTC     arch/arm/boot/dts/qcom/../msm8916-rumi.dtb
  DTC     arch/arm/boot/dts/qcom/../msm8916-cdp.dtb
ERROR (phandle_references): Reference to non-existent node or label "mpu6050_default"

ERROR (phandle_references): Reference to non-existent node or label "mpu6050_sleep"

ERROR (phandle_references): Reference to non-existent node or label "apds99xx_default"

ERROR (phandle_references): Reference to non-existent node or label "apds99xx_sleep"

ERROR (phandle_references): Reference to non-existent node or label "ak8963_default"

ERROR (phandle_references): Reference to non-existent node or label "ak8963_sleep"

ERROR (phandle_references): Reference to non-existent node or label "nfc_disable_active"

ERROR (phandle_references): Reference to non-existent node or label "nfc_disable_suspend"

ERROR: Input tree has errors, aborting (use -f to force output)
make[3]: *** [arch/arm/boot/dts/qcom/../msm8916-cdp.dtb] Error 2
make[2]: *** [dtbs] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/media/k2wlxda/_windows/cm/kernel/zte/t1'

can you help me with this error.
my source for kernel is
https://github.com/k2wlxda/android_kernel_N958St/tree/new

please help me sir.

thank you


Le 10/04/2015 13:58, Vincent Zurczak a écrit :
>
> So, basically, anyone can run the agent?
> Only root or a specified user should.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/roboconf/roboconf-system-installers/commit/5151864bfcb1fab7034d0595d9e68fec8086ca56#commitcomment-10664543>.
>
Probably not, because access to some files or directories would probably
get denied (eg. if a non-root user runs /etc/init.d/roboconf-agent start).
And even if it runs, there is nothing in the startup script to launch
the agent as root - so the process would have the rights of the user who
launched it.

Of course, anyone can run the agent by executing directly the proper
java command (issue a "ps -ef | grep java" to obtain it - then copy the
config and logs somewhere else, and adapt the command).

Anyway, running the agent as non-root does not really make sense... as
it would not be able to install anything !


Ha.  Too modest.  We developers all to often let emotion take control of
our project...  In time it becomes compromised.
I think we can learn a little from you Jake.  Keep up your fantastic work.
On Apr 9, 2015 10:31 PM, "Jacob Kelley" <notifications@github.com> wrote:

> You're good Robert, I'm the author but you're the owner, I'll have a pull
> request soon:)
>
> On Thursday, April 9, 2015, Robert Plummer <notifications@github.com>
> wrote:
>
> > Jake, you are too cool. This is YOUR repository, and you are treating it
> > like a polite foreign resident. What can I do to help?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/jakiestfu/Medium.js/commit/2a40a652285e9e297acabb546e46177f89ef2947#commitcomment-10658506
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jakiestfu/Medium.js/commit/2a40a652285e9e297acabb546e46177f89ef2947#commitcomment-10658573>
> .
>


yes, the code needs to be accurate.

the caught errors need to be logged to address this, the thing to do is both accurate and catch.

when hooks run client and server it will lead to some race conditions where client and server competes to make the same change. cought errors need examined...stored..


Не работает для числа 9223372036854775783


Hey!
Now worksforme:
diff --git a/app-editors/texworks/texworks-0.4.6.ebuild b/app-editors/texworks/texworks-0.4.6.ebuild
index e69b3af..c3cce29 100644
--- a/app-editors/texworks/texworks-0.4.6.ebuild
+++ b/app-editors/texworks/texworks-0.4.6.ebuild
@@ -23,16 +23,16 @@ QT4_DEPS="
        dev-qt/qtdbus:4
        dev-qt/qtgui:4
        dev-qt/qtscript:4
-       dev-qt/qtscript:4
 "
+
 QT5_DEPS="
        app-text/poppler[qt5]
        dev-qt/qtcore:5
        dev-qt/qtdbus:5
        dev-qt/qtgui:5
-       dev-qt/qtscript:5
-       dev-qt/qtscript:5
+       dev-qt/qtscript:5[scripttools]
 "


This is a first try at the moment parameters test. I tried to make this dynamic, and the idea is the following:
1. I try to pick the models that have a moments method
2. Call said method and grab the returned parameters
3. Try to call .n_modelfunc with the parameters
If the number of parameters is correct it should succeed.


- dev-qt/qtscript:5
+dev-qt/qtscript:5[scripttools]

Now woksforme.


Ubuntu 12.04 (and possibly others) doesn't have the dialog command installed by default, we'll need a wrapper here.


TEST


Wouldn't ``==`` be more efficient?


Why false? What does ErasedValueType have to do with type variables? I'd have written

    case _: TypeErasure.ErasedValueType => true

here


Why is `SEVEN` a constant?


@kylemac It works!


Very optimistic assumption :)


New work version


This is not HTML safe.


Hmm, then you'd have to handle the case prescaler=1 separately...


this is ok:)


What about counting down? (like the timer)


carbon oil? That is silly.


OK, I can see now that signature handling does not need isSemi in its old form. So maybe we can do without. Still need to rename to reflect the difference between no and half erasure. `EraseVC`?


Это ничего не изменило, код будет работать точно так же как и раньше


I'll miss those spaces. 8-)


the documentation has been updated


And why is a prescaler better than a wider timestamp counter?


github.com/CyanogenMod/android_hardware_ril

some how this is not working on my rom.


I commented at https://github.com/TrinityCore/TrinityCore/commit/e743f4a479ce7ddd3f13d51ca1c19a591c803fc0#commitcomment-10654271 too that it looks impossible to me for group to be NULL at that point, the crash is most likely caused by group->Disband() deleting group and then the calling function tries to access the free'd group.

Still no callstack or crashlog around tho.


To highlight similarity with class CURLFile and clarify what will be sent a file. But it is not critical, CURLBuffer looks great too. Will update it.
What do you think about serialize/unserialize for this class? If it small file we can accept it, but file also may be very big.


@tisto Should this be now moved into p.a.mosaic?


Nice syntax, I didn't know that but it's pretty useful :)


Well I've partly to revert stuff. **lib32-mesa** is not always installed.


verdade, foi mal, não tinha visto que subi assim.
faltou fechar ] e também o ;
cell.detailTextLabel.text = [dicionario randomStringWithLength:[dicionario.alfabeto ler]];
conseguiu arrumar pra rodar?


Почему я не могу ввести размер матрицы?


http://cdn.polyfill.io/v1/docs/features/#Element_prototype_closest

`var actionEl = ev.target.closest('li');`

Did we talk about deprecating `oDom`?


OK, I didn't know about that syntax.


okay!


@talbs this commit contains latest changes regarding the course cards design (SOL-531). I've returned some of the files to their previous state (current state on the master branch).

@cptvitamin I addressed the issues you pointed out in your comments regarding accessibility.


Should probably be `var`s on each line to conform to the style Origami agreed.


Good that we use a config lock nowadays — masters do change in incompatible ways....


Like the documentation says:
> If true, value classes are mapped in an intermediate step to ErasedValueClass types

So Meter erases to ErasedValueType(Meter, underlying) when isSemi = true

> otherwise they're erased like normal classes

so Meter is erased to Meter, and a hypothetical value class with a type parameter like VC[Int] is erased to VC, just like if it was a normal class and not a value class.


__repr__ and __str__ are just moved here from below


Instead of chaining onto the results of a repository method, craft a new repository method to do the single query. It will make your test easier to stub/build out.


Ну так. Перебралось немножко, да.


Not essential but nice to think about:

[`event.initEvent` has a horrible API](http://ariya.ofilabs.com/2011/08/hall-of-api-shame-boolean-trap.html), maybe we could introduce intermediate variables in cases like this to make intent clearer?

```JS
var bubbles = true;
var cancelable = true;
event.initEvent(name, bubbles, cancelable);
```


@marjev, thanks for the update - this focused change looks good to me.


вы же сами вроде разрешили во время кр built-inами пользоваться... Ну ладно


Why can't you just do `desc.length + 11` (11 is the length of

) here?


This mostly looks good, and provides a good test of whether the number of model parameters is correct, which is the most basic test and is important.  I think it's fine.  It would probably be good to encapsulate the whole try/except block into a function and use pytest to parametrize over that... but I'm not sure that's possible right now...


Can we remove commented code?  It's not going to run and the reason it's commented out isn't clear.  If we need to recover it in the future it should be in the commit history.


I don't mind much either way, as long as it is consistent... :)  Have gotten used to 'agent.*' by now, but that does not mean much...


haha when willox made his csluaviewerthingy, he also had a "dumb" button but he never implemented its functionality, so I did:D


I forgot about it, thought I removed it! Thanks!


Yup, missed these ones


да, но тут надо по сути реализовать библиотечную функцию, а вы реализовали, просто вызвав ее


I agree


I don't think so, we removed the matches polyfill


From the documentation of ExtensionMethods(with some typos I just noticed fixed):
```scala
/**
 * ...
 *
 * Additionally, for a value class V, let U be the underlying type after erasure. We add
 * to the companion module of V two cast methods:
 *   def underlying2evt$(x0: U): ErasedValueType(V, U)
 *   def evt2underlying$(x0: ErasedValueType(V, U)): U
 * The casts are used in [[Erasure]] to make it typecheck, they are then removed
 * in [[ElimErasedValueType]].
 * This is different from the implementation of value classes in Scala 2
 * (see SIP-15) which uses `asInstanceOf` which does not typecheck.
 */
```

So these methods have signatures `U => ErasedValueType(V, U)` and `ErasedValueType(V, U) => U`, they need to have these signatures to typecheck. I don't see how we could do this with just two general methods.


Also `var`.


Note that ideally I would like to split them, i.e. having bootstrapper.log and agent/pilot.log.

My hunch is that for practical purposes there is no reason to have .err and .out split over two files.


In principle I agree, PID should not be needed.  But it is little overhead, as not many events are logged with a pid.  Also, it makes evaluating the profiles a little simpler (as one does not need to infer the implicit knowledge).  So, either way is fine.

Independent of that, it might be worthwhile to split the parsing and execution of pre-exec -- that always bothered me a little, that we run arbitrary commands while still trying to  sort through the parameter list...  But that is a very low priority...

All the above probably doesn't help you much :P


On 04/10/2015 02:16 PM, Tomas Novotny wrote:
> Hi,
>
>> Hello,
>>
>> I wish I had seen your work prior to starting this :)
>
> Yes, it's pitty that we did it twice...
>
>> Merging would be fine, I'll need to get your branch and see how it works for me,
>> and then send you any changes I need. How does this work?
>
> I'm not sure if I understand correctly, are you asking for current status? From the first quick tests it seems that everything for ODROID-C1 works as expected - both u-boot and linux are build from sourcecodes (Hardkernel's github repos) and bootable SD card image is created. It can be flashed using dd and it boots.

Ok, same status here, although I am not 100% sure of the u-boot fix:
https://github.com/funman/meta-odroid/commit/93d1b80ed98ef44bbb6ba2e3277aec2fdd7a44ea

> There is just one issue - with core-image-minimal there is no u-boot.ini and DTB in the /boot directory of the image. I added
>
> ```
> IMAGE_INSTALL += " \
>         u-boot-ini \
>         kernel-devicetree \
>         "
> ```
>
> to my image's definition and it works as expected.
>
> What about you layer? Is it "production ready" or it still needs some more work?

Definitely would need some testing.

I started with core-image-minimal target, but I made some changes since
and I'd need to reverify that
core-image-minimal still works.

>> BTW we should get in contact with openembedded to have meta-odroid listed somewhere,
>> so people can find some authoritative source.
>
> That's true, probably layers.openembedded.org is the best place. I was just asking in the Yocto thread on ODROID's forum and found that there is no C1 support yet. I found one guy (Christian) also interested in the support for C1 so we made the current layer. Next time I will do better marketing ;)

Ok, I wanted to announce it on ODROID forums too but my activation link
had failed.

> But the problem is that I have only C1. Other devices in the repository are here only because of the fork, I didn't test them... So it is somehow "production ready" only for C1.
>
>> Which devices do you have? I have a XU3-lite and a C1.
>
> I have C1 only and I won't have any other in the near future.

OK well I can test on XU3 and hopefully we can find some people on the
ODROID forums.

>> Thanks for the heads up
>
> Thanks for you answer,
>
> Tomas

I will be gone for a couple of weeks so not sure if I'll give you
updates on this, but I'm definitely interested into
working on your branch rather than duplicating the work!


Hey Eric, cool to see you taking on the exercises and lab. I did want to recommend not checking in node_modules--there's a brief aside about this in one of the lessons, but I haven't talked about it much in class yet. Basically, there's just no real point to check in all those files, especially since you can always get a fresh copy from NPM. So you'll want to do three things:

* Add `**/node_modules` to your .gitignore file, delete the node_modules folders, and check in that change (don't worry, we'll put them back).
* Create a `package.json` file in each of your folders by using `npm init` and filling out the details (you can usually just hit enter until it goes away).
* Re-install your packages, but save their metadata to the `package.json` manifest using the `--save` flag, like so: `npm install request --save`.

Let me know if you have any questions!


Please, back-port this commit to maint-2.4.2.


А, ок.


Can you please explain why you had to change "mat" files? What are these changes exactly? Thanks.


the redundancy in err and out is annoying in fact...

Why would you split them?  I see the tandem as the same thing really, a single entity, which for practical reasons happens to be written in two languages...  I cannot imaging that we would ever run multiple agents from one bootstrapper?  OTOH, I *can* imagine that we split the agent components over nodes, and at that point, profiles are probably splitting, too (as are out/err).  Should we wait with sorting that out once we go that route?


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.186](http://teamcity.monogame.net/viewLog.html?buildId=6111&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


At some point we might compute `baseTypeRefOf(foo)` where the underlying type of `foo` is `ErasedValueType`, in this case it is very important to __not__ cache this in `baseTypeRefCache`, because after `ElimErasedValueType`, `foo` will no longer have an `ErasedValueType` as its underlying type and so a new call to `baseTypeRefOf(foo)` might yield a different result. If you remove this line or change it in the way you propose, some tests will fail.


@abe33 Aha, ok. I tested this [on xfce] and it seems to actually work at first sight. However, after releasing the cursor outside atom a couple of times, some strange things indeed start happening. This is especially obvious with multiple panes (e.g. scrolling one minimap scrolls both) and weirdly enough, selecting text also starts calling `endDrag()`.

So I was thinking if this is a common problem for js apps and after a quick search, I found [this post](http://stackoverflow.com/questions/14407869/capture-mouseup-event-outside-of-browser-window). So I tested the current behavior of minimap when:

1. dragging the minimap
2. while having the mouse button still held, alt tab away from atom

Doing this a couple times hits the "strange behavior" I mentioned above on the current version of minimap. Easiest way to check it is to have multiple panes with files open, and trigger the alt-tab behavior mentioned above twice, then drag the second minimap - it will actually scroll both panes.

Maybe there's a clever solution that both solves the current bug with alttabbing and also allows for not triggering the `mouseupHandler` when the cursor leaves the window?


I created this test:
tttt
    Run Keyword If    ${1}==${10}    Log    tata    Else    log    mama

It looks to me that if else is spelled another way than all-caps than this code is not being evaluated at all. Robot treats else as another parameter for first Log keyword and as ${1}==${10} is not true than it is just not being called. Also there is nothing in logs that says that else is a reserved keyword.
It looks to me that this change is not needed at all. But i may be mistaken...


Does it make sense to have a threshold on max and decide the scale accordingly? Isn't it better to have a linear scale for a lower max value?


```
isSemi = false ==> no erasure
isSemi = true  ==> semi-erasure
```
I don't know if another name would make this more clear, but I'm not opposed to changing it.


自动合并而已，完全不是事儿。这事情我的几个库里面几乎每周都要出现几次，本来就是另一种风格。

收到邮件吓了我一跳，我还以为你 git push --force 把哪个东西给清空了呢。


The reason why I used `\(\)` and `\[\]` is because they are matched and hence are safer. Should the string `~` exist outside math, all the math after it will be broken. But since they are in a `<span>`, it's less likely for it to cause problems.


So an empty package path means it's a remote package, that hasn't been downloaded yet, right?


@ilkayilknur Okay, but how can i know what is the type of parameter? I I do not get the parameter type. If i get parameter type, is it right implementation? Maybe
i can change type of minValue to any from number and check type in function. Which do you prefer?


I will not be committing this file as I have fixed the problem that caused my opengl to create a 4.0 context. It now creates a 3.3 context and works fine. :)


closes #214


Robot checks for reserved keywords only if we use it as a keyword, for example if we have such line of code:
else	log 	tttttttt


Why is this sent to System.out.println and the logger?


chal o


Identificados con //* metodos de prueba


Falta corregir detalle en posicion de insercion


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


Thanks @cesine :D


36: D204 1 blank line required after class docstring (found 0)
45: D102 Missing docstring in public method
51: D102 Missing docstring in public method
78: D102 Missing docstring in public method
83: D102 Missing docstring in public method
109: D102 Missing docstring in public method
121: D101 Missing docstring in public class
122: D102 Missing docstring in public method
126: D103 Missing docstring in public function
186: D203 1 blank line required before class docstring (found 0)
186: D204 1 blank line required after class docstring (found 0)
186: D400 First line should end with a period (not 'I')
186: D200 One-line docstring should fit on one line with quotes (found 3)
190: D400 First line should end with a period (not '2')
190: D200 One-line docstring should fit on one line with quotes (found 3)
215: D102 Missing docstring in public method
228: D203 1 blank line required before class docstring (found 0)
228: D204 1 blank line required after class docstring (found 0)
228: D400 First line should end with a period (not 'I')
228: D200 One-line docstring should fit on one line with quotes (found 3)
232: D400 First line should end with a period (not '2')
232: D200 One-line docstring should fit on one line with quotes (found 3)
250: D102 Missing docstring in public method
262: D203 1 blank line required before class docstring (found 0)
262: D204 1 blank line required after class docstring (found 0)
262: D200 One-line docstring should fit on one line with quotes (found 3)
266: D102 Missing docstring in public method
273: D102 Missing docstring in public method
285: D203 1 blank line required before class docstring (found 0)
285: D204 1 blank line required after class docstring (found 0)
285: D200 One-line docstring should fit on one line with quotes (found 3)
289: D102 Missing docstring in public method
292: D102 Missing docstring in public method


28:1: I100 Imports statements are in the wrong order. from invenio.utils.shell should be before from invenio.version
520:28: E127 continuation line over-indented for visual indent


80: D102 Missing docstring in public method
109: D209 Multi-line docstring closing quotes should be on a separate line
109: D203 1 blank line required before class docstring (found 0)
109: D400 First line should end with a period (not 'f')
109: D205 1 blank line required between summary line and description (found 0)
115: D102 Missing docstring in public method
150:10: E126 continuation line over-indented for hanging indent
157:10: E126 continuation line over-indented for hanging indent
175: D102 Missing docstring in public method
183:27: F821 undefined name 'WebInterfaceSearchInterfacePages'
183: D210 No whitespaces allowed surrounding docstring text
183: None: None
183: D209 Multi-line docstring closing quotes should be on a separate line
183: D203 1 blank line required before class docstring (found 0)
183: D400 First line should end with a period (not 'l')
183: D205 1 blank line required between summary line and description (found 0)
187:16: F821 undefined name 'WebInterfaceSearchInterfacePages'
218: D102 Missing docstring in public method
254: D102 Missing docstring in public method


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)
552: D400 First line should end with a period (not 'N')
552: D205 1 blank line required between summary line and description (found 0)
562:5: E266 too many leading '#' for block comment
564:5: E266 too many leading '#' for block comment
566:5: E266 too many leading '#' for block comment
569:9: E266 too many leading '#' for block comment
570:9: E266 too many leading '#' for block comment
586:9: E266 too many leading '#' for block comment
592:49: E128 continuation line under-indented for visual indent
597:9: E266 too many leading '#' for block comment
603:82: E231 missing whitespace after ','
618: D400 First line should end with a period (not 's')
618: D205 1 blank line required between summary line and description (found 0)
637: D209 Multi-line docstring closing quotes should be on a separate line
637: D205 1 blank line required between summary line and description (found 0)
662: D103 Missing docstring in public function
672: D103 Missing docstring in public function
707:72: E502 the backslash is redundant between brackets
708:20: E127 continuation line over-indented for visual indent
708:44: E231 missing whitespace after ','
712:35: E261 at least two spaces before inline comment
731:21: E128 continuation line under-indented for visual indent
731:93: E231 missing whitespace after ','
749:50: E231 missing whitespace after ','
769:48: E231 missing whitespace after ','
822: D400 First line should end with a period (not 'e')
822: D205 1 blank line required between summary line and description (found 0)
844: D400 First line should end with a period (not 's')
844: D205 1 blank line required between summary line and description (found 0)
859: D400 First line should end with a period (not 'r')
859: D205 1 blank line required between summary line and description (found 0)
869:10: E122 continuation line missing indentation or outdented
882: D200 One-line docstring should fit on one line with quotes (found 3)
897: D400 First line should end with a period (not 'y')
897: D205 1 blank line required between summary line and description (found 0)
916: D400 First line should end with a period (not 'L')
916: D205 1 blank line required between summary line and description (found 0)
931: D400 First line should end with a period (not 's')
931: D200 One-line docstring should fit on one line with quotes (found 3)
945: D400 First line should end with a period (not 's')
945: D200 One-line docstring should fit on one line with quotes (found 3)
959: D400 First line should end with a period (not 'd')
959: D200 One-line docstring should fit on one line with quotes (found 3)
973: D200 One-line docstring should fit on one line with quotes (found 3)
987: D202 No blank lines allowed after function docstring (found 1)
990: D203 1 blank line required before class docstring (found 0)
990: D204 1 blank line required after class docstring (found 0)
990: D400 First line should end with a period (not 'l')
1106: D210 No whitespaces allowed surrounding docstring text
1106: None: None
1106: D400 First line should end with a period (not 's')
1145:9: E266 too many leading '#' for block comment
1201:21: B901 blind except: statement


22:1: E402 module level import not at top of file
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
30:1: E302 expected 2 blank lines, found 1
30: D202 No blank lines allowed after function docstring (found 1)
36: D202 No blank lines allowed after function docstring (found 1)
41:1: E302 expected 2 blank lines, found 1
41: D210 No whitespaces allowed surrounding docstring text
41: None: None
41: D202 No blank lines allowed after function docstring (found 1)
47:1: E302 expected 2 blank lines, found 1
47: D103 Missing docstring in public function
50:1: E302 expected 2 blank lines, found 1
50: D202 No blank lines allowed after function docstring (found 1)
56: D210 No whitespaces allowed surrounding docstring text
56: None: None
56: D202 No blank lines allowed after function docstring (found 1)
64: D210 No whitespaces allowed surrounding docstring text
64: None: None
64: D202 No blank lines allowed after function docstring (found 1)
72: D202 No blank lines allowed after function docstring (found 1)
72: D400 First line should end with a period (not 's')
77:1: E302 expected 2 blank lines, found 1
77: D202 No blank lines allowed after function docstring (found 1)
77: D400 First line should end with a period (not 't')
82:1: E302 expected 2 blank lines, found 1
82: D202 No blank lines allowed after function docstring (found 1)
82: D400 First line should end with a period (not 't')
87:1: E302 expected 2 blank lines, found 1
87: D202 No blank lines allowed after function docstring (found 1)
87: D400 First line should end with a period (not 'y')
92:1: E302 expected 2 blank lines, found 1
92: D202 No blank lines allowed after function docstring (found 1)
92: D400 First line should end with a period (not 't')
97:1: E302 expected 2 blank lines, found 1
97: D202 No blank lines allowed after function docstring (found 1)
102:1: E302 expected 2 blank lines, found 1
102: D202 No blank lines allowed after function docstring (found 1)
102: D400 First line should end with a period (not 't')
107:1: E302 expected 2 blank lines, found 1
107: D202 No blank lines allowed after function docstring (found 1)
107: D400 First line should end with a period (not 't')
112:1: E302 expected 2 blank lines, found 1
112: D210 No whitespaces allowed surrounding docstring text
112: None: None
112: D202 No blank lines allowed after function docstring (found 1)
117:1: E302 expected 2 blank lines, found 1
117: D210 No whitespaces allowed surrounding docstring text
117: None: None
121:1: E302 expected 2 blank lines, found 1
121: D210 No whitespaces allowed surrounding docstring text
121: None: None
121: D202 No blank lines allowed after function docstring (found 1)
124:151: E231 missing whitespace after ','
126:1: E302 expected 2 blank lines, found 1
126: D202 No blank lines allowed after function docstring (found 1)
126: D400 First line should end with a period (not 'e')
132: D202 No blank lines allowed after function docstring (found 1)
132: D400 First line should end with a period (not 'e')
141: D202 No blank lines allowed after function docstring (found 1)
141: D400 First line should end with a period (not 'e')
151: D202 No blank lines allowed after function docstring (found 1)
151: D400 First line should end with a period (not 'e')
160: D202 No blank lines allowed after function docstring (found 1)
160: D400 First line should end with a period (not ':')
177: D202 No blank lines allowed after function docstring (found 1)
177: D400 First line should end with a period (not ':')
188:32: E128 continuation line under-indented for visual indent
189:32: E128 continuation line under-indented for visual indent
190:32: E128 continuation line under-indented for visual indent
191:32: E128 continuation line under-indented for visual indent
192:32: E128 continuation line under-indented for visual indent
193:32: E128 continuation line under-indented for visual indent
196: D209 Multi-line docstring closing quotes should be on a separate line
196: D202 No blank lines allowed after function docstring (found 1)
196: D400 First line should end with a period (not ',')
196: D208 Docstring is over-indented
208: D202 No blank lines allowed after function docstring (found 1)
215: D210 No whitespaces allowed surrounding docstring text
215: None: None
215: D202 No blank lines allowed after function docstring (found 1)
222: D210 No whitespaces allowed surrounding docstring text
222: None: None
222: D202 No blank lines allowed after function docstring (found 1)
229: D209 Multi-line docstring closing quotes should be on a separate line
229: D202 No blank lines allowed after function docstring (found 1)
229: D208 Docstring is over-indented
245: D209 Multi-line docstring closing quotes should be on a separate line
245: D202 No blank lines allowed after function docstring (found 1)
245: D208 Docstring is over-indented
261: D209 Multi-line docstring closing quotes should be on a separate line
261: D202 No blank lines allowed after function docstring (found 1)
275: D210 No whitespaces allowed surrounding docstring text
275: None: None
275: D209 Multi-line docstring closing quotes should be on a separate line
275: D202 No blank lines allowed after function docstring (found 1)
275: D400 First line should end with a period (not ':')
275: D208 Docstring is over-indented
292: D209 Multi-line docstring closing quotes should be on a separate line
292: D202 No blank lines allowed after function docstring (found 1)
292: D208 Docstring is over-indented
303:37: E128 continuation line under-indented for visual indent
304:37: E128 continuation line under-indented for visual indent
305:37: E128 continuation line under-indented for visual indent
306:37: E128 continuation line under-indented for visual indent
309: D209 Multi-line docstring closing quotes should be on a separate line
309: D202 No blank lines allowed after function docstring (found 1)
309: D400 First line should end with a period (not 's')
309: D205 1 blank line required between summary line and description (found 0)
309: D208 Docstring is over-indented
335: D209 Multi-line docstring closing quotes should be on a separate line
335: D202 No blank lines allowed after function docstring (found 1)
335: D400 First line should end with a period (not 'a')
335: D205 1 blank line required between summary line and description (found 0)
344: D210 No whitespaces allowed surrounding docstring text
344: None: None
344: D202 No blank lines allowed after function docstring (found 1)
349:1: W391 blank line at end of file


1: D100 Missing docstring in public module
20:1: E402 module level import not at top of file
21:1: I100 Imports statements are in the wrong order. import cgi should be before import urllib
21:1: E402 module level import not at top of file
23:1: E402 module level import not at top of file
24:1: I101 Imported names are in the wrong order. Should be CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBSEARCH_MAX_RECORDS_IN_GROUPS, CFG_WEBSESSION_ADDRESS_ACTIVATION_EXPIRE_IN_DAYS, CFG_WEBSESSION_RESET_PASSWORD_EXPIRE_IN_DAYS
24:1: F401 'CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS' imported but unused
24:1: E402 module level import not at top of file
25:6: E126 continuation line over-indented for hanging indent
40:1: I101 Imported names are in the wrong order. Should be create_html_link, create_url, make_canonical_urlargd
40:1: E402 module level import not at top of file
41:1: I100 Imports statements are in the wrong order. from invenio.utils.html should be before from invenio.utils.url
41:1: F401 'nmtoken_from_string' imported but unused
41:1: E402 module level import not at top of file
42:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
42:1: E402 module level import not at top of file
43:1: E402 module level import not at top of file
44:1: I100 Imports statements are in the wrong order. from invenio.legacy.websession.websession_config should be before from invenio.modules.apikeys.models
44:1: E402 module level import not at top of file
47: D101 Missing docstring in public class
69:17: E225 missing whitespace around operator
70:16: E126 continuation line over-indented for hanging indent
70:25: E203 whitespace before ':'
71:25: E203 whitespace before ':'
72:25: E203 whitespace before ':'
73:25: E203 whitespace before ':'
74:14: E126 continuation line over-indented for hanging indent
78: D102 Missing docstring in public method
79:9: F841 local variable '_' is assigned to but never used
87: D102 Missing docstring in public method
97:37: E203 whitespace before ':'
98:28: E203 whitespace before ':'
99:38: E203 whitespace before ':'
100:29: E203 whitespace before ':'
101:30: E203 whitespace before ':'
103:35: E203 whitespace before ':'
108:5: E303 too many blank lines (2)
108: D401 First line should be in imperative mood ('Display', not 'Displays')
108: D202 No blank lines allowed after function docstring (found 1)
108: D400 First line should end with a period (not 'r')
134:22: E126 continuation line over-indented for hanging indent
134:36: E203 whitespace before ':'
163:31: E126 continuation line over-indented for hanging indent
168:43: E203 whitespace before ':'
196:32: E203 whitespace before ':'
197:43: E203 whitespace before ':'
198:27: E203 whitespace before ':'
199:22: E203 whitespace before ':'
201:39: E203 whitespace before ':'
204:16: E126 continuation line over-indented for hanging indent
208: D401 First line should be in imperative mood ('Display', not 'Displays')
208: D202 No blank lines allowed after function docstring (found 1)
263:17: E126 continuation line over-indented for hanging indent
263:30: E203 whitespace before ':'
264:30: E203 whitespace before ':'
265:33: E203 whitespace before ':'
266:27: E203 whitespace before ':'
268:34: E203 whitespace before ':'
268:45: E225 missing whitespace around operator
269:34: E203 whitespace before ':'
269:45: E225 missing whitespace around operator
270:28: E203 whitespace before ':'
271:28: E203 whitespace before ':'
272:26: E203 whitespace before ':'
273:23: E203 whitespace before ':'
274:29: E203 whitespace before ':'
275:24: E203 whitespace before ':'
276:33: E203 whitespace before ':'
278:38: E203 whitespace before ':'
279:13: E121 continuation line under-indented for hanging indent
318:21: E126 continuation line over-indented for hanging indent
318:34: E203 whitespace before ':'
319:32: E203 whitespace before ':'
320:35: E203 whitespace before ':'
321:35: E203 whitespace before ':'
323:31: E203 whitespace before ':'
324:27: E203 whitespace before ':'
325:36: E203 whitespace before ':'
326:40: E203 whitespace before ':'
327:38: E203 whitespace before ':'
328:33: E203 whitespace before ':'
329:40: E203 whitespace before ':'
331:17: E121 continuation line under-indented for hanging indent
334:21: E128 continuation line under-indented for visual indent
334:34: E203 whitespace before ':'
336:139: E203 whitespace before ':'
337:35: E203 whitespace before ':'
340:30: E203 whitespace before ':'
340:96: E203 whitespace before ':'
344:5: E303 too many blank lines (2)
344: D400 First line should end with a period (not 'd')
362:11: E121 continuation line under-indented for hanging indent
362:26: E203 whitespace before ':'
363:32: E203 whitespace before ':'
364:32: E203 whitespace before ':'
365:37: E203 whitespace before ':'
366:21: E203 whitespace before ':'
367:21: E203 whitespace before ':'
368:28: E203 whitespace before ':'
374:5: E303 too many blank lines (2)
374: D102 Missing docstring in public method
382:11: E121 continuation line under-indented for hanging indent
382:26: E203 whitespace before ':'
383:31: E203 whitespace before ':'
387:27: E203 whitespace before ':'
388:27: E203 whitespace before ':'
389:26: E203 whitespace before ':'
394:26: E203 whitespace before ':'
395:30: E203 whitespace before ':'
401:5: E303 too many blank lines (2)
401: D102 Missing docstring in public method
409:11: E121 continuation line under-indented for hanging indent
409:26: E203 whitespace before ':'
410:26: E203 whitespace before ':'
413:23: E203 whitespace before ':'
414:19: E203 whitespace before ':'
417:23: E203 whitespace before ':'
418:19: E203 whitespace before ':'
423:30: E203 whitespace before ':'
429:5: E303 too many blank lines (2)
429:51: E251 unexpected spaces around keyword / parameter equals
429:53: E251 unexpected spaces around keyword / parameter equals
429:72: E251 unexpected spaces around keyword / parameter equals
429:74: E251 unexpected spaces around keyword / parameter equals
429:93: E251 unexpected spaces around keyword / parameter equals
429:95: E251 unexpected spaces around keyword / parameter equals
429: D102 Missing docstring in public method
441:11: E121 continuation line under-indented for hanging indent
441:26: E203 whitespace before ':'
442:36: E203 whitespace before ':'
443:27: E203 whitespace before ':'
444:30: E203 whitespace before ':'
445:25: E203 whitespace before ':'
446:28: E203 whitespace before ':'
452:25: E126 continuation line over-indented for hanging indent
452:35: E203 whitespace before ':'
453:28: E203 whitespace before ':'
454:21: E121 continuation line under-indented for hanging indent
460:17: E126 continuation line over-indented for hanging indent
460:34: E203 whitespace before ':'
461:39: E203 whitespace before ':'
463:13: E121 continuation line under-indented for hanging indent
466: D401 First line should be in imperative mood ('Display', not 'Displays')
466: D202 No blank lines allowed after function docstring (found 1)
479:256: E203 whitespace before ':'
479:280: E203 whitespace before ':'
479:302: E203 whitespace before ':'
501:20: E203 whitespace before ':'
502:19: E203 whitespace before ':'
503:11: E121 continuation line under-indented for hanging indent
507:45: E203 whitespace before ':'
508:46: E203 whitespace before ':'
509:45: E203 whitespace before ':'
511:46: E203 whitespace before ':'
515:15: E128 continuation line under-indented for visual indent
515:73: E201 whitespace after '{'
515:81: E203 whitespace before ':'
515:106: E202 whitespace before '}'
518:9: E303 too many blank lines (2)
520: D401 First line should be in imperative mood ('Display', not 'Displays')
520: D202 No blank lines allowed after function docstring (found 1)
520: D400 First line should end with a period (not 'n')
542:17: E126 continuation line over-indented for hanging indent
542:32: E203 whitespace before ':'
543:25: E128 continuation line under-indented for visual indent
544:15: E126 continuation line over-indented for hanging indent
552:22: E126 continuation line over-indented for hanging indent
552:26: E203 whitespace before ':'
553:37: E203 whitespace before ':'
554:38: E203 whitespace before ':'
555:20: E126 continuation line over-indented for hanging indent
560:11: E121 continuation line under-indented for hanging indent
560:15: E203 whitespace before ':'
561:26: E203 whitespace before ':'
562:27: E203 whitespace before ':'
568:9: E122 continuation line missing indentation or outdented
568:13: E203 whitespace before ':'
569:9: E122 continuation line missing indentation or outdented
569:23: E203 whitespace before ':'
570:9: E122 continuation line missing indentation or outdented
570:25: E203 whitespace before ':'
576:13: E122 continuation line missing indentation or outdented
576:17: E203 whitespace before ':'
577:13: E122 continuation line missing indentation or outdented
577:28: E203 whitespace before ':'
578:13: E122 continuation line missing indentation or outdented
578:31: E203 whitespace before ':'
583:11: E121 continuation line under-indented for hanging indent
583:15: E203 whitespace before ':'
584:24: E203 whitespace before ':'
585:27: E203 whitespace before ':'
592:15: E121 continuation line under-indented for hanging indent
592:27: E203 whitespace before ':'
593:30: E203 whitespace before ':'
594:13: E122 continuation line missing indentation or outdented
595:13: E122 continuation line missing indentation or outdented
604: D401 First line should be in imperative mood ('Display', not 'Displays')
604: D202 No blank lines allowed after function docstring (found 1)
604: D400 First line should end with a period (not 'e')
617:17: E225 missing whitespace around operator
619:19: E225 missing whitespace around operator
629: D401 First line should be in imperative mood ('Display', not 'Displays')
629: D202 No blank lines allowed after function docstring (found 1)
629: D400 First line should end with a period (not 'r')
652: D401 First line should be in imperative mood ('Display', not 'Displays')
652: D202 No blank lines allowed after function docstring (found 1)
652: D400 First line should end with a period (not 'e')
667:14: E225 missing whitespace around operator
678: D401 First line should be in imperative mood ('Display', not 'Displays')
678: D202 No blank lines allowed after function docstring (found 1)
678: D400 First line should end with a period (not 'e')
740:32: E128 continuation line under-indented for visual indent
746:36: E128 continuation line under-indented for visual indent
750:35: E222 multiple spaces after operator
751:36: E222 multiple spaces after operator
752:35: E128 continuation line under-indented for visual indent
757:33: E222 multiple spaces after operator
758:34: E222 multiple spaces after operator
765: D401 First line should be in imperative mood ('Display', not 'Displays')
765: D202 No blank lines allowed after function docstring (found 1)
765: D400 First line should end with a period (not 'd')
779:14: E225 missing whitespace around operator
780:15: E225 missing whitespace around operator
787:17: E203 whitespace before ':'
788:18: E203 whitespace before ':'
789:24: E203 whitespace before ':'
790:11: E121 continuation line under-indented for hanging indent
793: D202 No blank lines allowed after function docstring (found 1)
793: D400 First line should end with a period (not 't')
793: D205 1 blank line required between summary line and description (found 0)
812:17: E128 continuation line under-indented for visual indent
813:17: E128 continuation line under-indented for visual indent
814:33: E203 whitespace before ':'
814:34: E231 missing whitespace after ':'
815:30: E203 whitespace before ':'
816:35: E203 whitespace before ':'
819:21: E203 whitespace before ':'
820:19: E203 whitespace before ':'
821:17: E131 continuation line unaligned for hanging indent
822:25: E203 whitespace before ':'
823:24: E203 whitespace before ':'
825:20: E203 whitespace before ':'
826:21: E203 whitespace before ':'
830: D202 No blank lines allowed after function docstring (found 1)
830: D400 First line should end with a period (not 'e')
830: D205 1 blank line required between summary line and description (found 0)
849:17: E128 continuation line under-indented for visual indent
850:17: E128 continuation line under-indented for visual indent
851:33: E203 whitespace before ':'
851:34: E231 missing whitespace after ':'
852:30: E203 whitespace before ':'
853:35: E203 whitespace before ':'
856:21: E203 whitespace before ':'
857:19: E203 whitespace before ':'
858:17: E131 continuation line unaligned for hanging indent
859:25: E203 whitespace before ':'
860:33: E203 whitespace before ':'
862:20: E203 whitespace before ':'
863:21: E203 whitespace before ':'
867: D401 First line should be in imperative mood ('Display', not 'Displays')
867: D202 No blank lines allowed after function docstring (found 1)
867: D400 First line should end with a period (not 't')
881:14: E225 missing whitespace around operator
885: D401 First line should be in imperative mood ('Display', not 'Displays')
885: D202 No blank lines allowed after function docstring (found 1)
885: D400 First line should end with a period (not 't')
900: D401 First line should be in imperative mood ('Display', not 'Displays')
900: D202 No blank lines allowed after function docstring (found 1)
900: D400 First line should end with a period (not 't')
900: D205 1 blank line required between summary line and description (found 0)
905:9: F841 local variable '_' is assigned to but never used
909:22: E126 continuation line over-indented for hanging indent
909:26: E203 whitespace before ':'
914: D401 First line should be in imperative mood ('Display', not 'Displays')
914: D202 No blank lines allowed after function docstring (found 1)
914: D400 First line should end with a period (not 'r')
1006: D401 First line should be in imperative mood ('Display', not 'Displays')
1006: D202 No blank lines allowed after function docstring (found 1)
1006: D400 First line should end with a period (not 'k')
1052:22: E126 continuation line over-indented for hanging indent
1053:26: E203 whitespace before ':'
1054:33: E203 whitespace before ':'
1055:31: E203 whitespace before ':'
1056:29: E203 whitespace before ':'
1057:20: E126 continuation line over-indented for hanging indent
1061:21: E126 continuation line over-indented for hanging indent
1061:36: E203 whitespace before ':'
1062:25: E203 whitespace before ':'
1063:31: E203 whitespace before ':'
1064:16: E121 continuation line under-indented for hanging indent
1066:21: E126 continuation line over-indented for hanging indent
1066:36: E203 whitespace before ':'
1067:25: E203 whitespace before ':'
1068:29: E203 whitespace before ':'
1069:17: E121 continuation line under-indented for hanging indent
1072: D400 First line should end with a period (not 's')
1072: D205 1 blank line required between summary line and description (found 0)
1093: D400 First line should end with a period (not 'r')
1093: D205 1 blank line required between summary line and description (found 0)
1100:9: F841 local variable '_' is assigned to but never used
1109: D401 First line should be in imperative mood ('Display', not 'Displays')
1109: D202 No blank lines allowed after function docstring (found 1)
1109: D400 First line should end with a period (not 'l')
1113:52: E251 unexpected spaces around keyword / parameter equals
1113:54: E251 unexpected spaces around keyword / parameter equals
1134:9: F841 local variable '_' is assigned to but never used
1149:14: E225 missing whitespace around operator
1159:14: E225 missing whitespace around operator
1163:5: E303 too many blank lines (2)
1163: D202 No blank lines allowed after function docstring (found 1)
1182:9: E303 too many blank lines (2)
1183:102: E202 whitespace before ')'
1203:35: E225 missing whitespace around operator
1210:15: E225 missing whitespace around operator
1213:46: E203 whitespace before ':'
1214:44: E203 whitespace before ':'
1216:42: E231 missing whitespace after ':'
1217:43: E231 missing whitespace after ':'
1218:45: E231 missing whitespace after ':'
1220:49: E203 whitespace before ':'
1221:47: E203 whitespace before ':'
1223:45: E231 missing whitespace after ':'
1224:46: E231 missing whitespace after ':'
1225:48: E231 missing whitespace after ':'
1284:15: E225 missing whitespace around operator
1308:16: E127 continuation line over-indented for visual indent
1309:29: E231 missing whitespace after ':'
1310:16: E124 closing bracket does not match visual indentation
1314:5: E303 too many blank lines (2)
1347:15: E225 missing whitespace around operator
1361: D400 First line should end with a period (not ':')
1361: D205 1 blank line required between summary line and description (found 0)
1384:20: E225 missing whitespace around operator
1399:46: E231 missing whitespace after ','
1468:25: E203 whitespace before ':'
1471:28: E203 whitespace before ':'
1479:30: E231 missing whitespace after ':'
1480:31: E231 missing whitespace after ':'
1481:28: E231 missing whitespace after ':'
1483:30: E203 whitespace before ':'
1483:31: E231 missing whitespace after ':'
1486:16: E124 closing bracket does not match visual indentation
1489: D201 No blank lines allowed before function docstring (found 1)
1489: D205 1 blank line required between summary line and description (found 0)
1580:25: E203 whitespace before ':'
1584:25: E231 missing whitespace after ':'
1585:29: E231 missing whitespace after ':'
1588:31: E231 missing whitespace after ':'
1589:29: E203 whitespace before ':'
1589:30: E231 missing whitespace after ':'
1589:64: E231 missing whitespace after ','
1590:33: E203 whitespace before ':'
1591:16: E124 closing bracket does not match visual indentation
1594: D202 No blank lines allowed after function docstring (found 1)
1729:19: E203 whitespace before ':'
1730:26: E222 multiple spaces after operator
1735:37: E231 missing whitespace after ','
1735:23: E222 multiple spaces after operator
1736:13: E203 whitespace before ':'
1738:27: E203 whitespace before ':'
1739:27: E222 multiple spaces after operator
1747:38: E231 missing whitespace after ','
1747:23: E222 multiple spaces after operator
1748:13: E203 whitespace before ':'
1757:21: E203 whitespace before ':'
1758:30: E203 whitespace before ':'
1759:27: E203 whitespace before ':'
1767:9: E122 continuation line missing indentation or outdented
1767:73: E201 whitespace after '{'
1767:81: E203 whitespace before ':'
1768:65: E128 continuation line under-indented for visual indent
1768:78: E203 whitespace before ':'
1769:65: E124 closing bracket does not match visual indentation
1770:26: E128 continuation line under-indented for visual indent
1774:13: E128 continuation line under-indented for visual indent
1776:24: E231 missing whitespace after ':'
1777:30: E203 whitespace before ':'
1778:31: E203 whitespace before ':'
1778:32: E231 missing whitespace after ':'
1779:25: E231 missing whitespace after ':'
1780:24: E231 missing whitespace after ':'
1789:31: E231 missing whitespace after ':'
1790:21: E231 missing whitespace after ':'
1858:21: E222 multiple spaces after operator
1861:13: E203 whitespace before ':'
1867:25: E203 whitespace before ':'
1868:29: E203 whitespace before ':'
1869:25: E231 missing whitespace after ':'
1871:24: E203 whitespace before ':'
1872:31: E231 missing whitespace after ':'
1873:21: E203 whitespace before ':'
1873:22: E231 missing whitespace after ':'
1874:25: E203 whitespace before ':'
1879:5: E303 too many blank lines (2)
1879: D400 First line should end with a period (not 'p')
1879: D205 1 blank line required between summary line and description (found 0)
1910:11: E225 missing whitespace around operator
1911:19: E231 missing whitespace after ':'
1914:22: E231 missing whitespace after ':'
1916:15: E124 closing bracket does not match visual indentation
1919: D400 First line should end with a period (not 'e')
1919: D205 1 blank line required between summary line and description (found 0)
1950:11: E225 missing whitespace around operator
1951:19: E231 missing whitespace after ':'
1954:22: E231 missing whitespace after ':'
1956:15: E124 closing bracket does not match visual indentation
1959: D400 First line should end with a period (not 'y')
1959: D205 1 blank line required between summary line and description (found 0)
1973: D210 No whitespaces allowed surrounding docstring text
1973: None: None
1973: D400 First line should end with a period (not 'u')
1973: D205 1 blank line required between summary line and description (found 0)
1978:20: E203 whitespace before ':'
1980:62: E225 missing whitespace around operator
1981:13: E203 whitespace before ':'
1988:54: E225 missing whitespace around operator
1993:5: E303 too many blank lines (2)
1993: D400 First line should end with a period (not 's')
1993: D205 1 blank line required between summary line and description (found 0)
1999:9: F841 local variable '_' is assigned to but never used
2011: D400 First line should end with a period (not ':')
2011: D205 1 blank line required between summary line and description (found 0)
2026:15: E271 multiple spaces after keyword
2028: D400 First line should end with a period (not ':')
2028: D205 1 blank line required between summary line and description (found 0)
2045: D400 First line should end with a period (not 'p')
2045: D205 1 blank line required between summary line and description (found 0)
2064: D400 First line should end with a period (not 'd')
2064: D205 1 blank line required between summary line and description (found 0)
2089: D400 First line should end with a period (not 'd')
2089: D205 1 blank line required between summary line and description (found 0)
2107: D400 First line should end with a period (not ')')
2107: D205 1 blank line required between summary line and description (found 0)
2125: D400 First line should end with a period (not 'e')
2125: D205 1 blank line required between summary line and description (found 0)
2173:19: E128 continuation line under-indented for visual indent