Hi @brunomassa
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23098968/1193ecc8-f621-11e6-9924-f137262087a4.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @exch-bms2
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23098977/4e069322-f621-11e6-9194-5ac5cc67e8ba.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


develop (Myoldmopar) - i386-Windows-7-VisualStudio-14: OK (1831 of 1831 tests passed, 0 test warnings)

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


@diablodiab Quick comment, use C comments in the future instead of C++ comments.


Partially fixes #1


about UISettings yes we don't need it. The only what wee need is to get the component CanvasRenderer or when a UI object contains a lot of UI elements we should get the CanvasGroup


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-14: OK (1831 of 1831 tests passed, 0 test warnings)

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


trabalho de facudade


wassup


BT tuần 1&2


@chengrenz  嗯， 有时间就做一下～


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


@tim-field also have a look at this please - intention is to redirect to home on successful token validation (and login) from login page but not when validating from other locations....

Pretty sure there is a better way than passing a pathname check to validateToken...

To be clear intended behaviour is
- when successfully validating token from login page redirect to home (or maybe also some other page in the future
- when successfully validating token from any other page do not redirect to home
- when successfully logged in from login page redirect to home unless a redirect happened from a protected route ( eg "/actions/new"). then "nextPathName" is set and it should redirect back to protected route


Update: Now Quas can say back Hi to user with his/her **first name**.


i guess ideally "redirectToLoginIfNeeded" https://github.com/dumparkltd/hr-nmrf-client/blob/redirect-after-auth/app/utils/redirects.js#L3) would wait for the validation process to finish and only when it fails redirect to login. currently it redirects to login right away from where it redirects back to protected route once successful validated


This commit needs to be reverted. It is causing build to fail with an error.

Reference this comment
https://github.com/chemerisuk/cordova-plugin-firebase-hooks/issues/1#issuecomment-263863894


Yes, you broke Trace in all gens and should emergency hotpatch SmogTours as soon as possible. https://github.com/Zarel/Pokemon-Showdown/commit/8a3e4e5ac1267d067b898d05c72b97a5181e4e43


here ("redirectToLoginIfNeeded" https://github.com/dumparkltd/hr-nmrf-client/blob/redirect-after-auth/app/utils/redirects.js#L5) we could also include checks for user roles


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1833 of 1833 tests passed, 0 test warnings)

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


No problem, I pushed a fix.


> thanks to help from kesong xie!

👍


Accidentally misspelled "to". Good job, me.


@imsantosh confirm password ka koi field nai hota hai.


please review


Yeah, what I was referring to here was using your code for dealing with patch_d2.mpq as a model for what to do with the merged DLLs when migrating to/from 1.14. I knew your code had to include a special case for this situation so I approached the problem of adding 1.14 support from the perspective of doing the same thing that you did for that.


Oops, that commit message shouldn't have "didn't" in it...


Nullcheck


Good point, I'll look at doing this if Thyiad approves my fork, but I figured my way was the simplest for proof-of-concept purposes and that in practical terms, 20 string comparisons wouldn't be a big deal.


@mibby
https://github.com/Borlea/ArmorEquipEvent/issues/8
https://github.com/Borlea/ArmorEquipEvent/issues/9
https://github.com/Borlea/ArmorEquipEvent/issues/10


I think this should still be length. Length will tell us the size of the songs array. Duration is a thing on an individual song. Let me know if that makes sense. :)


does this commit for sure fix the itemframes ? ...  I don't want to say you haven't fixed something when you have.

of all the utensils of PocketMine, this repo has the most progress towards vanilla functions.

Impressed.


I thought about this, but wanted to keep the changes to the existing code minimal, and figured the duplication kept the rest of the code simpler and avoided breaking anything. Might look at this in the future though.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1247 of 1247 tests passed, 0 test warnings)

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


Wassuh


test


Considered this, but there didn't seem to be any advantage to doing it that way and I thought my way was more intuitive. Personal preference I guess, I certainly don't see anything wrong with your suggestion


@java-mentor потому что они впринцыпе не передаются на страницу, туда передается объект видео тайпа, на сколько я понимаю чтобы добавить все списки видео тасков для каждого тайпа придется их в цикле добавлять в modelAndView , что-то вроде этого:
for (int i = 0; i < typeVideos.size(); i++) {
			TypeVideo typeVideo = typeVideos.get(i);
			modelAndView.addObject("videoTasks" + i, typeVideo.getVideoTasks());
		}
мне кажется загружать на страницу дополнительные объекты тасков это хуже чем делать запрос при обновлении типа
то же самое происходит и при изменении роли, если изменить ее названия то у юзера она пропадает


Can I pick this? Or Did you faced any conflicts?


Good point, this issue wasn't triggered by my tests and I never thought about it. I think the best way is just to install the patch using the bundle method, so that you never trigger the migration logic.


Solves #50


Sox isn't soxr, btw.


Return movie instance, not just title.


Well, here's a patch:
```
diff --git a/haskell/Language/Hakaru/Runtime/Prelude.hs b/haskell/Language/Hakaru/Runtime/Prelude.hs
index 55cb1d3d..69fc4cfb 100644
--- a/haskell/Language/Hakaru/Runtime/Prelude.hs
+++ b/haskell/Language/Hakaru/Runtime/Prelude.hs
@@ -106,45 +106,43 @@ plate n f = G.generateM (fromIntegral n) $ \x ->
              f (fromIntegral x)
 {-# INLINE plate #-}

-bucket :: Int -> Int -> (forall s. Reducer () s a) -> a
+bucket :: Int -> Int -> (forall s. Reducer () s cell a) -> a
 bucket b e r = runST $ do
     s' <- init r ()
     F.mapM_ (\i -> accum r () i s') [b .. e - 1]
     done r s'

-data VReducer s a where
-    VRed_Num   :: STRef s a -> VReducer s a
-    VRed_Unit  :: VReducer s ()
-    VRed_Array :: MayBoxVec (VReducer s a) (VReducer s a)
-               -> VReducer s (MayBoxVec a a)
-
-data Reducer xs s a =
-    Reducer { init  :: xs -> ST s (VReducer s a)
-            , accum :: xs
-                    -> Int
-                    -> VReducer s a
-                    -> ST s ()
-            , done  :: VReducer s a
-                    -> ST s a
+data Reducer xs s cell a =
+    Reducer { init  :: xs -> ST s cell
+            , accum :: xs -> Int -> cell -> ST s ()
+            , done  :: cell -> ST s a
             }

-r_add :: Num a => ((Int, xs) -> a) -> Reducer xs s a
+r_add :: Num a => ((Int, xs) -> a) -> Reducer xs s (STRef s a) a
 r_add e = Reducer
-   { init  = \_ -> VRed_Num <$> newSTRef 0
-   , accum = \bs i (VRed_Num s) ->
+   { init  = \_ -> newSTRef 0
+   , accum = \bs i s ->
              modifySTRef' s (+ (e (i,bs)))
-   , done  = \(VRed_Num s) -> readSTRef s
+   , done  = readSTRef
    }

--- r_index :: Int
---         -> (Int -> Int)
---         -> Reducer s a
---         -> Reducer s (MayBoxVec a a)
--- r_index n f body = Reducer
---    { init  = newSTRef $ G.replicate n (init body)
---    , accum = undefined
---    , done  = readSTRef
---    }
+r_nop :: Reducer xs s () ()
+r_nop = Reducer
+   { init  = \_ -> return ()
+   , accum = \_ _ _ -> return ()
+   , done  = \_ -> return ()
+   }
+
+r_index :: (G.Vector (MayBoxVec a) a)
+        => (xs -> Int)
+        -> ((Int, xs) -> Int)
+        -> Reducer (Int, xs) s cell a
+        -> Reducer xs s (V.Vector cell) (MayBoxVec a a)
+r_index n a r = Reducer
+   { init  = \bs -> G.generateM (n bs) (\b -> init r (b,bs))
+   , accum = \bs i s -> let b = a (i,bs) in accum r (b,bs) i (s G.! b)
+   , done  = fmap G.convert . G.mapM (done r)
+   }

 pair :: a -> b -> (a, b)
 pair = (,)
```


Can you try forEach loop here.


Could this be a memory leak in the context of unit testing? This memory is never explicitly deleted because this Vnode will be in use throughout the entire validation process, which normally would occur once per simulation. But in unit tests this memory I think is floating around infinitely :worried:


Beautiful package. So elegant. Thanks. Love this!


Follow same instructions here too


Why method name started with Capital letter ?

Also, this is not the method definition I have given in mail


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1853 of 1853 tests passed, 0 test warnings)

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


Why access modifier is missing here ?


For bar plots, it is still necessary to draw the line in the same way as for histograms.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


To many countries and they are already sorted.


use for each here.


I am using celery 3.1.18 (Cipater) and when I set new values of time_limit/soft_time_limit while constructing a task object or while calling .s or .si(**kwargs) kwargs = {'time_limit': 20, 'soft_time_limit': 25}
I have posted details to
http://stackoverflow.com/questions/42322288/setting-celery-task-attributes-i-e-time-limit-and-soft-time-limit-does-not-wor/42323579#42323579

I was able to make it work by changing execute_using_pool. Can you check if the values can be overridden.
pre-requisite:
The task has default values (time_limit/soft_time_limit)assigned and I want to change during task creation/runtime.


Nice work, baby! ❤


Isn’t your website’s `<title>` ‘/ S.HA’? http://shanieceaurielle.com/


This sentence isn't finished… what a cliffhanger :-P


merging


Cos it's not ready, he'll merge it when it'll ready


Fun time watching you develop this code.


Executing the daily benchmark build, I will reply here when finished:

@nanosoldier `runbenchmarks(ALL, isdaily = true)`


Done with the command `pod trunk push --swift-version=3.0`


enumerage -> enumerate


> `--swift-version=3.0`

That is related to https://github.com/ReactiveCocoa/ReactiveSwift/pull/266 and https://github.com/CocoaPods/cocoadocs.org/issues/506.


I already removed this duplicated `message: null`


please help for windows how to run novnc on window


Is this replacing the previous device on https://home-assistant.io/developers/component_generic_discovery/ that says "To pass any non-serializable information to the platforms in the sub-component, you can use a global variable."?


i don't understand what this is for, is this for EVERY card that Special Summon? (I'm working on implementing the changes to DevPro's card manager)


context vs ctx? (query vs command)


Oh my…that’s a lot of cards to update….thanks

Sent from Mail for Windows 10
Success is your birthright but you got to work for it!

From: Mercury233<mailto:notifications@github.com>
Sent: Saturday, February 18, 2017 10:56 PM
To: Fluorohydride/ygopro-core<mailto:ygopro-core@noreply.github.com>
Cc: SuperAndroid17<mailto:sean7-6@hotmail.com>; Comment<mailto:comment@noreply.github.com>
Subject: Re: [Fluorohydride/ygopro-core] add TYPE_SPSUMMON (df28a5b)

http://yugioh.wikia.com/wiki/Special_Summon_Monster

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/Fluorohydride/ygopro-core/commit/df28a5b8eeb6980c146e1cc4e214caddf1cdfa01#commitcomment-20947990>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD9pAA-2RHldxI7IFq_iG2uUjJO_w0VRks5rd8uQgaJpZM4MFW90>.


What does flower brace notation do. Why is that we { } for {Component} but not for React.


Hi @rzwitserloot
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099479/e05293d2-f62d-11e6-8914-2660d26986e8.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


What does .bind really does. Does it return a function or sets context ?


Will any function which is using this.state will be called or only render() on a state change.


oh i get it, i run that SQL script and it's going to update all the cards to the right type..


Great, thanks too :-)


This is not a `CallableBool`, and put the simpler check first.


From when ReactDom got separated out of React core ?


What is export "default" can i  say export { landing: Landing }  ?


What is webpack-dev-server


Hi @gianm
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099498/48b3f380-f62e-11e6-8dd2-de22c592d841.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


What are babel presets ?


// is v1


Is this generated using an example starter pack project for React ?


Why node_modules are excluded ?


Put the non-query checks first to save some queries.


Hi @tramonex-nate
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099512/a2d285e8-f62e-11e6-8697-164492e08bdd.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


You're [late](https://github.com/DMOJ/site/commit/a8258b3f8a5f30ab7a1e2f1b5063f5968239d5b9).


Hi @spmallette
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099532/1e6c6ff2-f62f-11e6-95e3-10572f31edf7.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @gnut3ll4
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099543/6d95e05e-f62f-11e6-9a95-d163ec45251f.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @remohammadi
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099552/aa516324-f62f-11e6-9275-85a8f4a4fc59.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


@shanmdphd great, thanks for your support!


//comment v4


wtf man


I added this to avoid another crypto library being pulled in just for px5g, when already using OpenSSL for everything else. I have no idea why luci-ssl seems to prefer px5g-standalone by default. I prefer we fix that, if possible, instead of reverting this commit.

Another option would be: revert this commit, and drop the px5g dependency from luci-ssl-openssl, as OpenSSL can generate certificates too.


Hi @hasancelik
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099569/34057a92-f630-11e6-8194-f8e8343e5743.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @pctony
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099594/a14fd7b4-f630-11e6-92bc-4c9c8ebbe14d.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @leventov
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099608/f1da8ab2-f630-11e6-82b9-4f4a4dec6def.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @gokulavasan
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099628/55bd59ba-f631-11e6-8ecb-b24065c5543d.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @tteofili
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099641/87c314d6-f631-11e6-8e84-27263394d533.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Fixes #25


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1836 of 1836 tests passed, 0 test warnings)

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


@kjhoupy Why are these commented? Should I make some tests?


Part of #19


Did you even check this line of code?


Hi @renevanderark
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099665/046b3b1c-f632-11e6-88cf-37d82e5203ae.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


I think catch all exception is dangeous, you should change it to the `except  BadSignature:`, see the https://github.com/pallets/itsdangerous/blob/master/itsdangerous.py#L819-L829.


If only there was a site, a HUB of some sort, where you would be able to GIT the [release](https://github.com/ClusterM/hakchi2/releases) once it hits. ;)


Hi @shalastra
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099671/474ca97a-f632-11e6-9147-b677d5d67285.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Well... I played around a little, learned a lot. a37d6dc

Thanks for sharing this project. It has been great learning from it.


Hi @theck13
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099683/8a54be10-f632-11e6-8e65-a447bb1154d6.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Thanks a million buddy! I knew I had seen ur page on git hub somewhere I
just could not find the url to get back to it.

On Feb 18, 2017 11:30 PM, "burnjx" <notifications@github.com> wrote:

> If only there was a site, a HUB of some sort, where you would be able to
> GIT the release <https://github.com/ClusterM/hakchi2/releases> once it
> hits. ;)
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/ClusterM/retroarch-clover/commit/0e3676102091aa6fc7693497be65ffedd4d8b6e9#commitcomment-20948118>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AYrObxQBtka2OXxtf9XYJBdrixeIqQsbks5rd9NegaJpZM4MFVZk>
> .
>


Hi @yaegor
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099694/b6bd9fc6-f632-11e6-9b72-583b02426db0.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


kiva (nealkruis) - i386-Windows-7-VisualStudio-14: OK (2433 of 2433 tests passed, 587 test warnings)

 * 587 tests had: AUD diffs.

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


Hi @yiming187
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099699/fa1123c4-f632-11e6-87d9-8213495912bf.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


@ko-zu: Thanks for the report!  Fixed in c340d83689fa40d82fa4573ba3d112a9b2e032bf.


Hi @live4thee
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099709/3721118e-f633-11e6-8f4f-65ec3698a3cc.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


update the fifth test file


Hola mundo


Hi @dbernstein
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099721/6aeddbdc-f633-11e6-8e6c-2892cfb42281.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @lukasstadler
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099728/975e055c-f633-11e6-8923-f6f8c9617778.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @jamezp
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099735/cf9b1770-f633-11e6-9552-8c955db810b8.png)
Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @stefannegrea
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099749/11787da4-f634-11e6-9214-e43b0181808b.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @aa112901
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099753/3a24d70c-f634-11e6-9571-bd72e28bfb22.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Aprendiendo github


Lllega el nuevo verano


All the changeling names on their `pony.ini` are exactly the same, I don't think that's intended...?

Seems to be ok on Desktop Ponies, but maybe other implementations will mess up.


Hi @OmniCypher-
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099764/9742947e-f634-11e6-85c1-b7a0535fdfa0.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


@anniepank , the only suggestion is to change src values for your images in html file. This is the way of how you use it:
  - that means that image should be in the same folder with your html file. But when you move all images to folder images, you have to change src to the relative path:


The grammar is incomplete so they will throw an error during compilation


Hi @kasper-piskorski
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099778/24852eaa-f635-11e6-90bf-a1b0c992a435.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


This branch is created for the very first customer Gravity


![09ylmf6qaaaaaelftksuqmcc](https://cloud.githubusercontent.com/assets/24655215/23099781/9232c0b4-f6aa-11e6-8e16-40a26571de54.png)
![09ylmf6qaaaaaelftksuqmcc](https://cloud.githubusercontent.com/assets/24655215/23099785/ad2249c6-f6aa-11e6-9157-334e3a973e83.png)
![111](https://cloud.githubusercontent.com/assets/24655215/23099784/ad1efdc0-f6aa-11e6-897c-b08771436493.png)
![2017-02-01_153623](https://cloud.githubusercontent.com/assets/24655215/23099782/ad1d8080-f6aa-11e6-854b-0fb0be538b84.png)
![20150514093559727](https://cloud.githubusercontent.com/assets/24655215/23099783/ad1f0ea0-f6aa-11e6-8829-dbeae209b3c6.jpg)
![Uploading 20150521044525780.jpg…]()
![Uploading 20150521045018267.jpg…]()
![Uploading 20150521045600833.jpg…]()
![Uploading 20150521050101521.jpg…]()
![Uploading 20150522095507282.jpg…]()
![Uploading 20150522100555605.jpg…]()
![Uploading 20150522103056134.jpg…]()
![Uploading 20150522103454101.jpg…]()
![Uploading 20150522103617978.jpg…]()
![Uploading 20150609022645939.jpg…]()
![Uploading 20150612105420703.jpg…]()
![Uploading 20150612111058866.jpg…]()
![Uploading 20150612111621229.jpg…]()
![Uploading 20150612112557228.jpg…]()
![Uploading 20150612112703897.jpg…]()
![Uploading 20150613111008479.jpg…]()
![Uploading 20150613111217799.jpg…]()
![Uploading 20150613111957995.jpg…]()
![Uploading 20150613112405571.jpg…]()
![Uploading 20150613112634689.jpg…]()
![Uploading 20150613113306969.jpg…]()
![Uploading 20150613113634458.jpg…]()
![Uploading 20150615052344130.jpg…]()
![Uploading 20150615052500512.jpg…]()
![Uploading 20150615052524850.jpg…]()
![Uploading 20150615052559150.jpg…]()
![Uploading 20150615052702647.jpg…]()
![Uploading 20150615052717376.jpg…]()
![Uploading 20150615052804921.jpg…]()
![Uploading 20150615052825723.jpg…]()
![Uploading 20150615052856106.jpg…]()
![Uploading 20150615052915476.jpg…]()
![Uploading 20150823092546338.jpg…]()
![Uploading 20150823092741546.jpg…]()
![Uploading 20160122061122404.jpg…]()
![Uploading 20160219055109324.jpg…]()
![Uploading 20160219055136455.jpg…]()
![Uploading 20160219060234692.jpg…]()
![Uploading 20160414030743981.jpg…]()
![Uploading 20160603111045858.jpg…]()
![Uploading 20160616104715671.jpg…]()
![Uploading 20160616104728421.jpg…]()
![Uploading 20160616104746424.jpg…]()
![Uploading 20160616104816775.jpg…]()
![Uploading 20160616104845513.jpg…]()
![Uploading 20160616104900492.jpg…]()
![Uploading 20160616105125397.jpg…]()
![Uploading 20160616111106210.jpg…]()
![Uploading 20160622092836873.jpg…]()
![Uploading 20161205120144752.jpg…]()
![Uploading 20161207025334898.jpg…]()
![Uploading 20161207032330714.jpg…]()
![Uploading 20161214093423202.jpg…]()
![Uploading erwei.jpg…]()
![Uploading icon02.1.png…]()
![Uploading icon03.1.png…]()
![Uploading icon05.1.png…]()
![Uploading icon06.1.png…]()
![Uploading icon07.1.png…]()
![Uploading icon08.png…]()
![Uploading icon16.png…]()
![Uploading icon30.gif…]()
![Uploading icon091.png…]()
![Uploading img03.png…]()
![Uploading img04.png…]()
![Uploading img05.png…]()
![Uploading img06.jpg…]()
![Uploading img07.jpg…]()
![Uploading img12.gif…]()
![Uploading logo_name.png…]()
![Uploading logo_z.gif…]()


wassuh


Hi @Uhtiybr
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099857/6952e720-f635-11e6-9bef-8266ddb90a11.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Lol


Hi @andrewlague
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099865/c2efae3a-f635-11e6-9b1c-4bd30af4ab8d.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


@vinaykumar2491
The symbol 'service' is NOT getting resolved. What could be the problem?


Here the first version of erp will be built. The option considered is Oodo


Hi @tkountis
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099869/15e45258-f636-11e6-8d40-c5fe3b96f7da.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Yeah I am. I will send it through when I have it working well. At the moment you have to compile Skylight twice, and more confusing you have to do a forced re-compile using something like mix deps.compile to get the second compile to take


Hi @zhangkun83
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099874/5e757bb4-f636-11e6-8d33-1c4b2b918c11.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


Hi @thinline72
We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
We have four short questions regarding the change in the image below which is part of this commit.
![image](https://cloud.githubusercontent.com/assets/2257582/23099884/a362b264-f636-11e6-92cc-cd088a2bee58.png)

Questions:

Q1- Is the change at these lines similar to any other changes (from other locations of the same commit or from other commits)? (yes, no, not sure)

Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)

Q3- Can you give it a name? (for example, Null Check)

Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)

The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/

Thank you,
Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
Danny Dig http://eecs.oregonstate.edu/people/dig-danny


This commit has been deployed to deploy0219T010143


I changed one, thanks John anyway :-)


good work


@syscl 怎么提供信息？


Is there a reason why a `for of` loop isn't being used for that `locales` loop (or possibly even `[.find](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find)`)?


Why is it dangerous? I agree that it is a bad idea to catch all exceptions when there is a chance you may miss some errors in your own code, but in cases where you are calling third party code and want to make sure there are no crashes in my opinion it is justified.


Why do you link forking people stuff and adding your name in?


Fixes #12


'.bind' returns current context. Otherwise it pass result of setState to setTimeout


You've forgot to put `=` after Expense
it should be `var Expense = mongoose.model('Expense', expense);


Apps/NesUGAme.cs
Shouldnt that be NesUGame?
Also, in that file, should DefaultCover be static as you access it without a reference?


@mr-kings 看我分享的那个node后台源码啊，部署到自己的服务器即可。然后这里写上你的服务器地址


Also, there are problems where override and static manipulators are used together when that is not allowed and this stops compiling.


Do you mean the names for the arguments?  You can even write the following:
```lean
meta constant module.write_to (path : string) (mod : module) : io unit
```


Added


[Your benchmark job](https://github.com/JuliaLang/julia/commit/34b39f87188ac4f89c6eac59c80a9db26ae7a1c9#commitcomment-20947967) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/400a9f263c95328201eb29616964bb351e574667/daily_2017_2_19/report.md). cc @jrevels


hey


yo


No if check for pickle on save admin?


@andygrove  I have deleted that key.


I'll make sure to do that


lol, supposed to be `millis()`. Where's C's helpful strong typing now?


hello


hhhh


mm


mmm


Damn nice....


You forgot to replace `bmiTell` here


Thank you.


@pbiecek I think that this is a good idea. The function theme_survminer() could be a simple wrapper of the function ggpubr::ggpar() [http://www.sthda.com/english/rpkgs/ggpubr/reference/ggpar.html], which can already handle many of these arguments: font.x, font.main, ....


@fr500 The crash occurs in backends/fs/posix/posix-fs.cpp in the getChildren method. I've done a very quick and dirty hack in my fork that fixes it, but I haven't submitted a pull request yet, because I haven't located the exact issue:
https://github.com/diablodiab/scummvm/commit/5037bf630171fdf4491bb66721875d0635fc8be4

I have some other improvements/fixes to the ScummVM core in my fork that I'll also prepare for submission soon. Until then you can temporarily point the Retroarch updater url to this url, if you want to download a version that works on the SHIELD:
http://lindqvist.synology.me/shield/


> Another option would be: revert this commit, and drop the px5g dependency from luci-ssl-openssl, as OpenSSL can generate certificates too. In this case, maybe we can drop the px5g-standalone package entirely?

The px5g dependency has already been dropped from from luci-ssl-openssl three weeks ago with commit https://github.com/openwrt/luci/commit/b6341bd197aed9640c4d0dcff73019e045978df0 in master and that was backported into lede-17.01 with commit https://github.com/openwrt/luci/commit/e306ee6c93c1ef600012f47e40dd75020d4ab555

That was done as soon as also Openwrt accepted the PR to implement the cert generation with openssl-utils that I have originally done for LEDE.

There is no reason for px5g dependency for luci-ssl-openssl. Please revert the commit.

@stintel @jow- @nbd168


Karl,
Ken told you about the things you need to consider in order to respond correctly to a signal's aspect speed.  For speed restrictions, the desired response is to have the final incremental change occur just a few scale feet before reaching the protected block.  For releasing a speed restriction (the easy case), the response begins upon entering the block (no longer needing protection).

If it is to be done with any precision, block lengths and the speed characteristics of the train must be known - i.e. his reference to throttle settings for 'distance/sec' values.  I use roster speed profiles if they are available for warrants.  However, most users don't want to bother making them - particularly those with a large number of locos in their rosters.  Also, many users don't bother to enter block or path lengths.  Nevertheless I attempt to make speed changes by guessing lengths with default values and a one-size-fits-all user adjustable 'throttle factor'.  It's quite crude, but it's a 'best effort' given little information.

Also, Ken spoke of the need to look far enough ahead in order to have enough distance to slow down. Blocks can be quite short, some as you have, might be the length of one turnout.  Frequently it takes several blocks to make a smooth speed change. American layouts have the same issues as European ones.

I want warrants to be useful to casual users and I'm willing to compromise by having a 'no ramp' option to simulate SCWarrants since they have already been introduced.  However, I do not think such warrants should jump start to max speed or sudden stop to end and I believe users should determine the speed to run their trains.  Also it would be nice if some form of ramping might be preserved.  Overrunning into a protected block is a hard consequence to swallow.

I perceive your principal need is to have two or more trains share the same route simultaneously.  If we can do that with warrants while doing everything we can to approximate the goals I have for warrants, then fine, lets do it.  Going 'noRamp' is OK since it is rather unobtrusive and the concept has already been introduced. Frankly, I don't want to encourage their use, but if it's the only way to accomplish a necessity, then OK.  I mentioned 3 goals for warrants. It's true they are compromised already with the notion that aspect speeds listed in the speed table can be interpreted 4 ways.  Only the last two are actually consistent with the goal #2.  Having a warrant type that overruns into the protected block takes the compromise further.

You also mentioned trains going berserk and I admit to having bugs and perhaps not the best logic for the algorithms, let alone sparse information to make precise calculations.  So for simplicity and robustness, on the other hand, you can follow Ken's work with RobotThrottle and/or use OBlocks, Portals, OPaths etc in a system of your own.  Warrants are built on top of them, but they can be used for other purposes.  The BlockOrder class holds these objects and signals (heads or masts), for what a train should deal with when looking at an OBlock ahead.

For your own system using OBlocks etc, subclass WarrantRoute to define the route.  Then add pieces of NXFrame and WarrantTableFrame to create and monitor your autotrain objects.  Also make an autotrain  manager to hold them.

I continue to work on getting speed changes to work prototypically.  In fact I'm in that process right now. I confess to breaking parts of the look ahead last November.

PeteC

BTW, SCWarrants suggests an idea that an NXWarrant should ask for the distance into the destination block where the head of the train should stop.  Currently the only stopping point is the middle.

To work together on warrants or to work on a system of your own, let's take further discussion offline.

    On Saturday, February 18, 2017 4:48 PM, Ken Cameron <notifications@github.com> wrote:

 Karl,

My comments were more just passing the angle I took at the task. Automating
trains is far from simple.

I say a lot has to do with falling back the group rules "code wins". That
says your content deserves to be in there somewhere. I think the real issue
is naming. Warrants have a particular definition in the railroad lexicon.
Anything that varies from that too far is asking for trouble. And
fundamentally Warrants are a human interaction at the core with the system
providing the safeguards and record of what is going on.

Given the history of other things, and that your solution is geared toward
automated running, some name focusing on that instead of 'warrants' is my
suggestion. I know when I started with RobotThrottle I did it as script
mostly to work out ideas. Long term I expected to roll it into Java code at
some point, likely some feature near the throttles. But I'm still not sure
if it is the right way to go. I got side tracked when signal masts came
along. They offer a lot of new ideas and I've never had the time to work on
the code to support masts plus I'm not sure of the right way to deal with
them for some issues. Time will tell if I ever get to that.

At least that's my advice. So see what others might offer on this thread.

-ken c

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


checkpoint


Thanks will test


@nguyenhoan do you think the code in the image you sent could be a recurring change?


@chrmarti if this is to be reused between `node` and `electron-main`, I suggest to move it into `src/vs/code/common/windows.ts` and use it from there in all places. This should also then get rid of the weird:

```typescript
export const OpenContext = OriginalOpenContext;
export type OpenContext = OriginalOpenContext;
```

in `src/vs/code/electron-main/windows.ts`


@chrmarti what I find weird is that this does not work out of the box on Linux and macOS, why do users have to change settings to get the same experience as on Windows out of the box?


There is one more repo https://github.com/Imroy/pubsubclient, this is a forked codebase from https://github.com/knolleary/pubsubclient.

As per his documentation http://imroy.github.io/pubsubclient/classPubSubClient.html#ae298afa250bf3393780f8e7a13774fcc he does support QOS level 0,1,2 for subscribe. Also i was digging into his code to find his support for publishing, seems he has implemented QOS 0,1,2 for publishing aswell https://github.com/Imroy/pubsubclient/blob/master/src/PubSubClient.cpp#L282

I was seeing how this guy has managed to give support for all QOS levels when his original forked repo can't give, seems that he has re-written the complete MQTT https://github.com/Imroy/pubsubclient/blob/master/src/MQTT.cpp

Could you integrate this library and make your repo more robust?

Since i don't have my ESP8266 environment setup i couldn't test and create a pull request


Just to make sure that all the regressions from https://github.com/JuliaLang/julia/commit/32227498867ab4a6e3ebd74e76ad99b9f164fe50 where mitigated

@nanosoldier `runbenchmarks(ALL, vs = "@d8ac581f474d5d0f0c032594b46fd1ed84b042f3")`


jaai
djfdo


jlsjasl;aj;w


adafffafaaaaaaaaaaaaaaaaaaaaaa


README.md


I think you goofed here


ssssssssssssssssssssss


@hgouraud : j'ai push force pour fixer cette partie car il n'y a pas de trait -d'union ici « -nopicture » et non « -no-picture »)


Hi @nguyenhoan, here's my answers:

q1: yes
q2: removing unnecessary explicit object array creation
q3: no
q4: already automated


break


I used pkg-config for json-c and openssl.
There is still a call `(brew --prefix)` in configure.ac which it would be nice to get rid of.


hi


sexy


SVN:
https://vip2.svnspot.com/yanyh9747.dzyh/


santhosh page 1


do we need this for loop??


please I need help with this. I'm using windows 10 and cannot get reader to work. need it for credit and debit cards. please email memikerats1985@YAHOO.COM


Any suggestions on names for this? I'm rather unsatisfied with this name.


This 1% you probably got because of mistake in the code. You did self assignment w=w which was probably put out during optimization.
I don't think if there is possible to optimize GetXYZ() when it's inline and CVector3(x, y, z) which is inside is also inline.
I have already corrected the code, because all 4D formulas were broken.


YES I KNOW  nothing. I really wanna learn. I'm broke. I learn quick, and if possible I will return a favor tif you can get me goin


:o useful


> The issue is: "How would it be acceptable to the JMRI community to have both to co-exist.”

Yes.

JMRI grows by addition.  If you add working (for at least your use) code in a way that doesn’t interfere with existing functionality, then “code wins”.


Could you throw an exception instead? This is really a problem to me.


extracted


No; label


 all 4D formulas were broken

good catch. !!!

On Sun, Feb 19, 2017 at 8:37 PM, Krzysztof Marczak <notifications@github.com
> wrote:

> This 1% you probably got because of mistake in the code. You did self
> assignment w=w which was probably put out during optimization.
> I don't think if there is possible to optimize GetXYZ() when it's inline
> and CVector3(x, y, z) which is inside is also inline.
> I have already corrected the code, because all 4D formulas were broken.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/buddhi1980/mandelbulber2/commit/28b8bb64af10103046eda113f69c0da1014e4aa9#commitcomment-20948430>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AMLZHKrPgap0hmql9ecm9xhRnUtVUwwlks5rd_FJgaJpZM4MFY4M>
> .
>


не надо никаких <font /> использовать. Просто обворачиваешь в дополнительный span или div, даешь ему класс и задаешь там нужные стили. Все что касается ВИДА, должно быть в стилях.
<br /> тоже лучше не использовать, если тебе надо на новой строке, обверни каждую строку в отдельный тэг


Чет не понятно, мы же меняем у обьека typeVideo поля name, а у VideoTaska есть просто ссылка на обьект typeVideo. Ссылка же шь не меняется и в таблице  video_task_type  связь по айдишникам та же ?


@Bochkarev-Yuriy попробуй продебажить обновляющий метод


Зачем тут таблица? Таблицы нужны для вывода данных табличного вида и то их сложно сделать отзывчивыми для телефона. Делаешь 3 колонки дивами, даешь каждой колонке display: inline-block. и они будут в 1 строку


нет типа mailto, есть email. mailto есть у ссылок в href, чтоб открылся сразу клиент для почты


`button type="submit"`


ты сделал что в каждом элементе страницы, текст будет по центру. ЛУчше такого не делать, заебешься обнулять его на left


лучше использоваться normalize.css reset.css . Чтобы дефолтные стили были во всех браузерах одинаковые


слишком спецефичные и глобальные стили. Ты щас каждому диву задала. Не надо так+ форматирование


# 简介
PHP基础学习旨在为BJY的学生们搭建一个共同学习PHP基础的平台.
为了方便大家学习，我把每一阶段做了版本标记，你可以根据自己的学习情况，选择合适的版本下载。


Well I tested before I committed the code....and without the conversion the timestamps where completely wrong in my influxdb (latest version)
I would have expect I could indeed just use the output from time_t
That's why I needed to convert them

But from his report, the temperature timestamps looked fine
Maybe because we send (could send) multiple values in one go, that the timestamps for the second and up lines are not correctly being received or handled?

Bdw, at the moment when.your influx machine can not be received, the package is also dropped


Зачем фиксированная ширина, темболее такая большая. У меня это просто вылезло за край экрана. Чтобы тянулось на всю ширину делаешь `100%`. Но у header, div, footer, p и большинства тегов, у которых стоит изначально `display: block`, width и так будет 100%


тоже самое


w00t ! This is going to cut down traffic a lot between scans. Can't wait to try it with the new firmware !
Bravo 👍


ты его нигде не подключила


и тут


还要注意算术溢出的问题


Yes, I was :/


Все картинки надо сжимать через tinypng.com . А то слишком много весят


So while that code compiles, when run using the below program

````
{-# LANGUAGE GADTs #-}
import Language.Hakaru.Runtime.Prelude

import qualified Data.Vector.Generic as G

a = G.replicate 1000000 1

prog =
  lam $ \a' ->
   bucket (nat_ 0) (size a')
     (r_index (\_       -> nat_ 2)
              (\(i, ()) -> a' ! i)
        (r_add (\(i, (_b, ())) -> nat_ 1)))

main =
  print (prog a)
````

I get the following error:

````

BuckWordcount2.hs:12:7: error:
    • Couldn't match type ‘cell0’
                     with ‘Data.Vector.Vector (GHC.STRef.STRef s Int)’
        because type variable ‘s’ would escape its scope
      This (rigid, skolem) type variable is bound by
        a type expected by the context:
          Reducer () s cell0 (Data.Vector.Unboxed.Base.Vector Int)
        at BuckWordcount2.hs:(11,4)-(14,43)
      Expected type: Reducer
                       () s cell0 (Data.Vector.Unboxed.Base.Vector Int)
        Actual type: Reducer
                       ()
                       s
                       (Data.Vector.Vector (GHC.STRef.STRef s Int))
                       (MayBoxVec Int Int)
    • In the third argument of ‘bucket’, namely
        ‘(r_index
            (\ _ -> nat_ 2)
            (\ (i, ()) -> a' ! i)
            (r_add (\ (i, (_b, ())) -> nat_ 1)))’
      In the expression:
        bucket
          (nat_ 0)
          (size a')
          (r_index
             (\ _ -> nat_ 2)
             (\ (i, ()) -> a' ! i)
             (r_add (\ (i, (_b, ())) -> nat_ 1)))
      In the second argument of ‘($)’, namely
        ‘\ a'
           -> bucket
                (nat_ 0)
                (size a')
                (r_index
                   (\ _ -> nat_ 2)
                   (\ (i, ()) -> a' ! i)
                   (r_add (\ (i, (_b, ())) -> nat_ 1)))’

````


nnn


@jimbergman done in e2e360f3ae2e8cda2d14744babdec821b9e0e31e


应该是**Make** The Interface Beautiful Again.


Saltstack


You mentioned you looked through the clang-scan output to find this bug. However, isn't the warning given ( https://neovim.io/doc/reports/clang/report-fda41d.html#EndPath ) unrelated to your change? The warning is "Value stored to 'len' is never read". In the branch on line 4885 and 4888, the warning is correct, since len is simply overwritten. However, the branch on line 4906 does use the len variable. Perhaps clang-scan deduced that one of the first two branches are always true, and thus the last branch never executes? I think it's good to look into this before sending this change upstream.


1.5.0硬编码后期优化一下


TI


buis TI


@SaracenOne Thanks!


return MyResponse.ok(null, false);   是否加解密参数若是方便调式的话 提交代码前还是改回走默认


I'm eventually going to give the trainer code a much-needed overhaul anyway, so this may not even still be relevant then, but for now it's a good call.


This variable was actually named wrongly. It should be called $releases :D


Hi Klaas,

I am pretty certain that this function was called with NULL in the past.
The original did not reference m_currentInfo at all. I decided to hold the
the cached SD table sections in m_currentInfo whereas the code previously
relied on them bring held in Dvbstreamdata.

Roger

On 18 February 2017 6:03:12 pm kmdewaal <notifications@github.com> wrote:

> The test on m_currentInfo not being NULL does fix the crash, but I think
> that it masks an underlying problem. I think that this function should not
> be called with m_currentInfo being NULL. It has never in the past, so that
> it is now called with NULL is likely to have been introduced by other
> recent changes.
>
> --
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/rogerjames99/mythtv/commit/3d5c4dbf7991b3baddcf1c19416904a59b1dba4f#commitcomment-20945455


timesTamp <= 0L   容错强一点  有些客户端喜欢传-1， 当然==0也没啥


aaaa


hoang nan la thien ma doc hanh


best


totest


Oh yeah, that error message makes sense now. I want to try to fix it, but have you committed your latest working code yet?


After further investigation, it appears that has_mbyte is defined to be true in https://github.com/neovim/neovim/blob/2ddadaa28cd62cb601779a1d53ea41aee13482de/src/nvim/globals.h . However, in this same file, there's this comment:

```
// mbyte flags that used to depend on 'encoding'. These are now deprecated, as
// 'encoding' is always "utf-8". Code that use them can be refactored to
// remove dead code.
```

So I think we can remove the branch of line 4906. Furthermore, we could remove lines 4867, 4871, 4875 and 4879 (this includes the change you made, @Hjdskes).


これだと両方ステージに入っちゃいますね


upload some basic javascript code


I committed the Runtime Prelude using GADTs.

On Sun, Feb 19, 2017 at 3:20 AM, Chung-chieh Shan <notifications@github.com>
wrote:

> Oh yeah, that error message makes sense now. I want to try to fix it, but
> have you committed your latest working code yet?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/hakaru-dev/hakaru/commit/7530baec0f4544d6aa225a5b8e9af3a763981224#commitcomment-20948540>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAAhUUnlDcZojSsuHy2oEhMdzA_BbYaNks5rd_s0gaJpZM4MFWt7>
> .
>


it does not work on android 4.4 .why?


Can this be reverted now that 8dc17b31df0967eabb9d0361335cfa038efee9ee makes the unavailable page the default vhost?


gitで管理しているファイルをステージに登録できませぬ。
あとcachedでcね
git addに何かしてみよう


Solved more correctly (I hope) in the set_addr branch. Please test.

--
-- Matthias Urlichs


WTF?!!!


Thanks, comment resolved.


And we could replace the `STRCPY(p + len, ...);` lines with `STRCAT(p, ...);` (see [strcat documentation](http://en.cppreference.com/w/c/string/byte/strcat)). By making this change, we can also remove the `len = (int)STRLEN(p);` line. Then it'll be more clear the len is defined in one of the two if-branches. We should also change `else if (has_mbyte)` into `else`. I can make a PR (within our fork) for all of these changes tonight.


Почему такая длинная строчка?!


Почему нет сообщения коммита?!


hi! i`m a big fan of necrobot2.
i have a question about transfer below.

my general setting for every pokemon(in pokemonconfig) is like this
    "KeepMinCp": 2000,
    "KeepMinIvPercentage": 95.0,
    "KeepMinLvl": 6,
    "KeepMinOperator": "or",
    "UseKeepMinLvl": false,
    "PrioritizeIvOverCp": true,
    "KeepMinDuplicatePokemon": 1

but, i wanna set a little bit different to pupitar, so i set it at transferfilter like below
 "Pupitar": {
      "KeepMinCp": 9999,
      "KeepMinIvPercentage": 90.0,
      "KeepMinLvl": 6,
      "UseKeepMinLvl": false,
      "KeepMinOperator": "or",
      "KeepMinDuplicatePokemon": 10,
      "Moves": [],
      "DeprecatedMoves": null,
      "MovesOperator": "or",
      "CatchOnlyPokemonMeetTransferCriteria": false
    },

here is my question
Q) if the number of my pwupitars in my bag is over 10, which one will be threw away?
 11st pokemon or the smallest iv?

thanks,


read can't be const, because it modifies the `index_` class member.


I dont understand why all of this documentation was removed.  Now navigating to the github page displays no documentation for all the stuff you deleted, and as far as I can tell the only way to access this documentation is to go back to a previous tag


dddd


それも最適化の一つと思いますが、そもそも候補の計算処理も軽いものではないので、素早く入力されたときにもスキップしたいのです。


npm install hexo-material


@cafeiklan , fitur SID 3.10 harus ditambahkan ke OpenSID satu-per-satu, sesuai kebutuhan. Belum tentu perubahan yang dilakukan di 3.10 cocok dengan OpenSID. Banyak fitur 3.10 yang sudah ditambahkan ke OpenSID (contoh: https://github.com/eddieridwan/OpenSID/issues/302, https://github.com/eddieridwan/OpenSID/issues/303, dsbnya).

Sepertinya, semua fitur yang bermanfaat dari SID 3.10 sudah terdaftar di https://github.com/eddieridwan/OpenSID/issues -- dan kebanyakan sudah ditambahkan.

Tetapi kalau anda menemukan fitur SID 3.10 lain yang mungkin bermanfaat, silakan buat issue untuk setiap fitur tambahan.


I don't think so. In Apache, the default vhost is the first to be loaded. The "priority" exposed by the puppet module is just the prefix to the vhost filename so that you can control the order they get loaded *within the one directory*.

But `conf.d/*` always gets loaded before `sites-enabled/*`, so no matter what we make the priority on the "unavailable" vhost, the first vhost listed in the file would always end up being the default vhost.


Algoritma dan Pemrograman I


吼啊，然而已经改不了了啊


Ah, I see, that is a bit of a problem, I didn't realize it worked like that. It's probably fine to keep it like this then, it's not a big deal.


update


Надо сделать вывод сообщений и управление функциями. Иначе main уже 200 строк занимает


> 👯♂

@ecwu Cough, a bug is just fixed in 37ae594. See line 56.


Allright, I can confirm that everything now okay with saving/loading (I repeated template that you have sent me by e-mail). However, while testing I have noticed a wierd thing - there is a small chance that montster will spawn (or ressurect?) at (0,0) as a ghost, i.e. without blockmap:
https://youtu.be/h8tqoXOkG_g

I honestly don't know, was this bug earlier, and even can't imagine, is it a spawn- or REspawn- bug.
Testing was done with `-fast` and `-respawn` parameters.


Pls no swear words here😿  This is serious business!


checkpoint


这里是什么意思？


kiva (nealkruis) - Win64-Windows-7-VisualStudio-14: OK (2433 of 2433 tests passed, 587 test warnings)

 * 587 tests had: AUD diffs.

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


Thx


output_variable_regex (mbadams5) - i386-Windows-7-VisualStudio-14: OK (0 of 0 tests passed, 0 test warnings)

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


output_variable_regex (mbadams5) - Win64-Windows-7-VisualStudio-14: OK (0 of 0 tests passed, 0 test warnings)

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


.....我就吐槽一下啦，也没别的意思


隐约看到我服务器的影子，很高兴对你有帮助 :)


This commit conflicts with my system/sepolicy/seapp_contexts"

Error: Rule in File "vendor/cm/sepolicy/seapp_contexts" on line 3: "user=_app seinfo=OpenDelta name=eu.chainfire.opendelta domain=system_app type=system_app_data_file" violates neverallow in File "system/sepolicy/seapp_contexts" on line 65: "user=((?!system).)* type=system_app_data_file"

Did you make any changes to that file to overcome this or I will have to leave this commit out and let the users run this app in permissive mode.

Btw did you finished building for RR bacon, is OpenDelta running fine?


Tu aurai pu regrouper les champs _publishedAt_ et _validated_ sous la même option de formulaire '_admin_'. L'option '_validated_field_' est un peu redontante.


Created multidev environment [ci-example-d8-composer#ci-383](https://dashboard.pantheon.io/sites/c401fd14-f745-4e51-9af2-f30b45146a0c#ci-383).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-383-ci-example-d8-composer.pantheonsite.io/)