TODO: Although questions s2.q4 and s4.q1 now accept and download multiple responses, one of the possible responses for those two questions is "Other", which is accompanied by a text input. The user interaction for these questions appears to be ok, but the text for "Other" is neither saved or downloaded.


good idea.


Is there a reason why this project is a separate solution? If it's a new project in the same solution as the source, you won't need to reference an external location, you can reference the project so others can build it easier:
    <HintPath>..\..\..\OneDrive\BitBucket\CSharpTradeOffers\CSharpTradeOffers\bin\Debug\CSharpTradeOffers.dll</HintPath>


The previous two members were given explicit sizes apparently so that the object can fit into a certain space. @arvidn, how big does `m_allocated_observers` actually have to be? If 30 bytes is still enough, `m_read_only` would fit into the same space without increasing the size of the object.


Yeah, I'd just pick one.


No to przełączam na ten branch
path = http://efik.syntax-shell.me/czatrepajr/
+ zmiany w kodzie skryptu


fast-forwarding develop to borshop-integration-84-feature/subscribe-improvements = a62b0cc3


This comment is a syntax error.


Sry :(


No newline at the end of file.


I think this is equivalent to `React.render(<Library collection={layerItems} />, el);`.


@aldenml, do you have any copyright of your own to add here?


It's good practice to specify your propTypes in react so it can check them for you as well.


I was trying to explain that it's not a problem because if I have to build
it with the other "normal" makefiles it doesn't expect that convention
anymore, just the regular names, simple as that, but you don't like to
listen (or read) you just keep stating over and over what you want.

On Wed, Sep 2, 2015 at 3:34 PM, Twinaphex <notifications@github.com> wrote:

> Do whatever you want with the mgba core, at this point I don't care.
>
> Just don't let it be said that I tried to warn you about this beforehand.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/libretro/libretro-super/commit/bccf87f82cf0e2003587085a62b53173bda9fec7#commitcomment-13033075>
> .
>


to make this so we don't have to change it once global admins can edit nodes, you should be able to save the $key in the foreach to check the field name

```
foreach ($fields as $field_name => $field) {
      //test for translation
}
```


Of course, what if there is more than one track with a clip under the playhead? As you said yourself, you lost confidence in using implicit selection. You click to select the clip to trim, position the playhead, and then press i or o. Or, does i/o trim clips on all unlocked tracks? If so, that's not a simple in/out trim, which to me is a clip-oriented action.


Looks good, it's simple and direct


cual metodo? between? yo tampoco, pero todos los días se aprende algo :angel: jajaja


@philipobenito

Inlined this one, not sure - what do you think?


I could be wrong, but I think you only need to wrap values in curly braces if there is interpolation involved.


Don't change the topic. Is this change needed or not?


Then you should start explaining it because you didn't explain anything so far and I simply (in a very cool manner) stated my reasons for not liking this change.

Come back on IRC so you can actually talk to me in PM about whatever it is you wanted to communicate, I have no desire to be going back and forth with you over public communications.


@jayelkaake I included this in my fork in order to be able to use it in a Magento setup. You already merged @gregrobbins original file and included it in a tagged release. So no need to issue a PR for this.


:+1: on turning this into a function, but once we go to `n+1` admins, this or statement will get a little out of control.
at the top of this file we can `define(GLOBAL_ADMIN_ROLES, ['mexio admin, brazil admin])` and test against that constant


Okay awesome, thanks!


Why is the top 20% dropped?


At a brief glance, it seems like `const` could be restored here. lookup_peers() in dht_default_storage is const and the changes to this method seem like they don't require additional mutability compared to before.


Put this in `state.boards`


This is but a drop in the bucket of the violations- see #12214 (which now has a conflict w/ this removal)


since this is a noop would it be better to just define this function in the closure surrounding the element def. That way we do not have to put it on the prototype of the polymer element?


You can control OpenCL from the terminal before you launch Natron
export MAGICK_OCL_DEVICE=OFF
export MAGICK_OCL_DEVICE=GPU
export MAGICK_OCL_DEVICE=CPU

So you only need the -OpenCL build, and export MAGICK_OCL_DEVICE=OFF if you don't want OpenCL

Will in the future add the ability to control this with a param.


The `LICENSE.md` file should probably be updated or removed.


I didnt really contribute!


Oh man, that commit message is blinging!


86139842-AddAutoSizing (Nigusse) - x86_64-MacOS-10.9-clang: OK (1779 of 1809 tests passed)

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


An updated version is available in the marketplace for BA-server 5.3+

On Wed, 2 Sep 2015 20:01 JohnEricson <notifications@github.com> wrote:

> I think I need this fix. The Transfer button no longer works for me on the
> "Transfer from JCR to file system" choice. Nothing happens, nothing in
> browser console or the Tomcat log.
>
> Any possibility we could get a new release of PRS with this fix? The
> latest in the Marketplace seems to be 14.12.10.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/webdetails/repositorySynchronizer/commit/2bf31e9740b93c75fd514cd8f63c52ee7bd1c30f#commitcomment-13031172>
> .
>


ah, had not seen that PR yet


There's some similarity, but for such simple classes I'm not sure it is worth trying to capture. Only two of three properties have even the same general purpose, and both of those have crucially different types (that is, they are actions taking a particular kind of object as arguments, not methods to override/implement. And the new class is not (nor intended to be) widely used.


I don't think so, this is essentially how signatures are "typechecked", the internal syntax produced by the typed `define-signature` form needs to be parsed in order to register an entry into the Signature environment.


I spotted something else that needs fixing too, related to this change. I will do a different change that fixes this for all the resources, plus adds the "something else", reply with that commit here, and then we can close out this PR (without merging it) after making sure this is what you're looking for (globally on all these topics).


looks good


Spelling: `candidate`
That said, I find this comment a bit hard to understand. Maybe don't know enough about the role it's playing.


> Organization Bug


Hmm, probably not perfect. I've had two crashes since then, but the rate seems significantly diminished. From now on, I'll try running with OTMC disabled as well.


How does the generation of the overclock signal work? Why is there an & with 1023?


Clutch :8ball:


Something like this?
```
@@ -1289,7 +1289,11 @@ void MainWindow::keyPressEvent(QKeyEvent* event)
         }
         break;
     case Qt::Key_Up:
-        if (multitrack()) {
+        if (event->modifiers() & Qt::AltModifier) {
+            m_playlistDock->raise();
+            m_playlistDock->decrementIndex();
+            m_playlistDock->on_actionOpen_triggered();
+        } else if (multitrack()) {
             int newClipIndex = -1;
             if ((event->modifiers() & Qt::ControlModifier) &&
                     !m_timelineDock->selection().isEmpty() &&

```


I think they should be able to refer to aliases which is why I thought I should register them after the aliases have been registered, though I am not certain if that was the correct thing to do.


Judging from how it looks in the GitHub web interface, it seems like this line is using spaces instead of the tab that was likely meant to go here.


ok maestro :+1:


It should work fine.
I'm just making sure the difference can be stored in the irange packet.


What does this do?


yes, if you only set dht_settings, it won't work.  you have to restart dht (dht_tracker). That's the caller's responsibility to do this since dht_tracker only accept dht_settings in constructor.


If anything was dropped from the google docs text at http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf that was an oversight.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (761 of 761 tests passed)

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


Testing Testing


Add a short comment about what is the purpose of this class. Mention that multi bindings are not resolved yet.


:tropical_fish: :fish: :blowfish: :fishing_pole_and_fish:

I quite like the way this library handles things - sorry you can't maintain it anymore.


Just learning new things.


develop (evanweaver) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2288 of 2332 tests passed)

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


Yeah, this shouldn't be necessary. Any skeleton that has been completely removed should have already been removed from the master list.


Consider lifting this out because we shouldn't need to create a new `ActionElements` class everytime `render` is called. You can pass callbacks to the element props instead like `<ActionElements onDelete={this.onDelete} ... />`


Maybe put your share buttons in a <ul> ?


Wygląda na to, że działa.


Ok, ich hab mal die History durchgesehen und im Wiki einige ähnliche Fälle betrachtet. Es gibt Gegenstände die Statusefekte bei Krit verursachen, die haben aber eigentlich einen eigenen Text, hier scheint Obsidian das verdaddelt zu haben weswegen wir nicht schreiben können „Verursacht Verwirrung bei kritischem Treffer“.

Das „Talent“ hat niko dort hingeschrieben und damit sind wir gut gefahren. Es macht jetzt halt bei dem Bogen weniger Sinn, da der Zustand kein Zauber ist.


They're not, but their representation in Unit types is the same as for imports and exports, a list of Signatures.


Whoops, okay. I was only looking at session_handle and just assumed that it would propagate downward without a DHT restart. Sorry.


Thanks @IainNZ :+1:


This as in this exact commit, then no, I have no basis for saying it is. The only thing I can say for sure for this  crash is that for the specific reproduction steps I had when I first encountered it, adding this line stopped it for happening.


I just tested it, but there was a missing *then* (see latest commit). After re-testing, the installation went fine, but I noticed that /system/lib/libwebviewchromium.so is removed, while I think it is here in factory images. I installed an HTML5 WebView tester and it worked, so I think there's no problem. I just have 27 more MBs in /system to install other apps.


Consider flattening this.


Thanks!


its not recording
it is record_on_answer
this is called on bridge

i believe this code was misplaced here


Possibly, but the only time `Signature`s should be printed is when they are subpieces of a Unit type, in which case I think it would not be ideal to have printed types that look like

(Unit (import (Signature a^) ...) (export ...) ...)


I find it a bit odd to fork on whether we have array or not, vs a more clear bool value. But this is internal enough that probably not worth refactoring.


Consider binding events in `componentDidMount` (called when the component is rendered for the first time).


@andrerom it is my understanding that in cli there is no site access matching that occurs.  The site access specified by --siteaccess does not go through a siteaccess matcher to fall back to the default as it would if it was an http request.  It’s not even tested to see if it is valid.  @lolautruche perhaps this should change?

Defaulting to `%ezpublish.siteaccess.default.name%` may be wrong perhaps as this is not updated  to coincide with the user setting of ezpublish.siteaccess.default_siteacces.


Subindo


Could you move `url` into a sculpin_site_prod.yml so that it doesn't get added when working locally?


I updated the yellow model to have an extra 100 years, intended to allow for a longer burn in. I used the `ss3sim::change_year` function, and then did some minor tweaks to make sure nothing else was changed.


You don't use your convenience getter here.


Most of these should go in `devDependencies`. `dependencies` are packages required for your app to run whereas `devDependencies` are packages required to develop your app.

Also add `node-sass` and `babel-core` to stop npm peerDependencies warnings


develop (kbenne) - i386-Windows-7-VisualStudio-12: Build Failed

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


added travis


That's a lot of wrapping for something called NoWrap :smirk_cat:


What's this supposed to fix?  Both variables you changed are local and non-static, so will be on the stack per-thread already.  This just wastes stack.


Is that checking enough? You may want to check for the particular mismatch. Same for other tests.


test


https://github.com/zackargyle/insta-pinterest/ :)


Here too


NoWrapTLS would probably be the right name.


here too, I am tempted to tell you to remove that getter :)


Are you still coding this?


I think just `unit?`, all the other bindings appear to be syntax.


I wonder how would alias interact with multi binding, can you add a simple test.


Don't need this line


That would also help maintainers know what the test is actually testing (i.e. what is expected to fail). It's not clear to me what some of those tests are testing.


which means we can get rid of this line


write a view and/or controller spec to ensure this renders and doens't crash said page


Why should the error mention tags?


Hm, komisch.


develop (evanweaver) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


You don't need an `assert()` here, because `ubuf_init()` does its own malloc failure detection.


Doch, hatte ich... :)


I agree, but I don't know how to write the interesting test cases of units importing and exporting signatures since the signatures need to be in the environment.


I started explaining and you were "it has to work like the rest" when in
fact it's working like the rest, it's not even a change, I thought that I
had to use leiradel's makefiles, then you said I shouldn't, so I understood
that and, I said it wasn't a problem if it uses the regular makefiles,
then you stated what you wanted.

Then I said you don't understand (because in fact you didn't) and you kept
going over and over about it becoming a mess without even considering my
words as valid

It's simple actually, the bot takes whatever the different build jobs
produce, there are three of these, GENERIC, LEIRADEL and GENERIC_JNI every
single of these names the products differently, JNI uses a subdirectory for
the ABI for instance, then the same build process converts the filename to
what RETROARCH needs (or dist-scripts) and copies in the dist folder, much
like libretro-super.

So yes, if I don't use leiradel's makefile YOUR naming convention is still
in place... which I could have explained if you stopped thinking about what
you WANT and read what I had to say.

<Twinaphex> if we start making exceptions for certain cores it will turn
into a total mess
*<radius> no it's not a problem if it's not supposed to build with that
makefile*
<Twinaphex> I want convention over configuration
<Twinaphex> for Wii it has to work the exact same way as everywhere else
<radius> you don't get it
<Twinaphex> and with the exact same naming convention
<Twinaphex> no you don’t get it
<Twinaphex> I don’t want this turning into a total mess
<radius> can you let me speak?
<Twinaphex> I never prevented you from speaking
<radius> yo don't get it because you don't know how the buildbot works
<radius> again
<radius> it doesn't matter
<Twinaphex> then it’s a messy buildbot
<Twinaphex> which in the long run should be sanitized

On Wed, Sep 2, 2015 at 3:40 PM, Twinaphex <notifications@github.com> wrote:

> Then you should start explaining it because you didn't explain anything so
> far and I simply (in a very cool manner) stated my reasons for not liking
> this change.
>
> Come back on IRC so you can actually talk to me in PM about whatever it is
> you wanted to communicate, I have no desire to be going back and forth with
> you over public communications.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/libretro/libretro-super/commit/bccf87f82cf0e2003587085a62b53173bda9fec7#commitcomment-13033396>
> .
>


I think he means "why are the top 20% of votes dropped, if you're just taking a minimum after dropping the bottom 20%?" I just submitted a pull request to fix the wording of that rule.


I can confirm that this fixes it for me. Thanks!


I'm writing about the statistical reasoning for removing the top 20%. Since the minimum is chosen removing the top is redundant. The same could be accomplished by sorting the votes in ascending order and choosing the 2400th value (index=2399 if the list starts from 0).


Looks really good, I agree with removing `:config` from the readme.  Do you think we should leave it and put `[deprecated]`?


Achei ofensivo. Posta mais :smile_cat:
A questão é, apesar de ter melhorado 196x, o meu algoritmo continua lento pois o seu fazia em menos de 10 segundos XD
O antigo fazia em 2 horas e alguns minutos hahahaah


> by state, I mean something to distinguish if it's a task to check for a config file, or to actually do the task. Like preparation, so it's not required, but if it is specified, then scored should be Not Scored

I though this kind of extra task was represented by an extra version number in the task ID (seems to be the case for some tasks).
Should we open an issue about this and document it in CONTRIBUTING.md?


TeamCity Chorus :: chorus-precise64-master Continuous [Build 1.5.461.de275939eed03371b4e82440214b2abb96f02201](http://build.palaso.org/viewLog.html?buildId=62581&buildTypeId=bt323) outcome was **SUCCESS**
Summary: Tests passed: 862, ignored: 54 Build time: 00:25:40


Let's talk about this in PM, you' are seriously overreacting over nothing and you honestly catched me wrong.

Honestly man, just come back and talk and don't make this any bigger than it is because it is really nothing. Seriously...............


Sure, adding documentation


まぁインデントと字句トークン的に削除できる空白を消せばもっと文字数減らせるけれども！


Why is that a problem? No-one should be able to link to that unit (since they can't refer to `bad^`), so it's a useless program, but I don't understand why that should be a type error.


:+1: \o/ This is great!


I'll test once more, I might not have a 100% clean setup after several attempts at installations on same ezp install.


Why is the error about contracts? Isn't the problem that the *type* doesn't list it?


removed


Why "anything" ?


This seems to lead to a segfault when `_textures` is deleted. I'm still trying to find the error, but the contained data is valid. The segfault happens in the first line of the `AbstractTexture` destructor. Which is *really* weird, because it tries to delete completely different data than the one pointed to in the data array.

Address of `this` in the AbstractTexture destructor is `28bbeb80`, but Array data is `8ad6878`. I tried cleanly rebuilding everything, but that did not change anything.


I'm not making anything bigger, I closed my bouncer and I left home, I'll
just log in again later.

On Wed, Sep 2, 2015 at 3:58 PM, Twinaphex <notifications@github.com> wrote:

> Let's talk about this in PM, you' are seriously overreacting over nothing
> and you honestly catched me wrong.
>
> Honestly man, just come back and talk and don't make this any bigger than
> it is because it is really nothing. Seriously...............
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/libretro/libretro-super/commit/bccf87f82cf0e2003587085a62b53173bda9fec7#commitcomment-13033879>
> .
>


Still not got the name of the conference right. It needs to be exactly PyCon UK. Also when used a proper noun rather than as a shell command, the language is called Python not python.


That looks safe to me. No objections to a merge.


This is very tiny, but very useful for those wanting to move to Lua 5.2 or LuaJIT.


Da lass uns doch lieber auf die Skripte von @nkemnitz zurückgreifen.


OK, let's just resolve this issue in any case. I was just expressing my concerns that if we start going down this path, it will become harder and harder to compile all these cores in batch fashion with dist-cores.sh. And that was my only point of contention, that we have to keep things relatively sane and the same across the board.

That's it. That was all there was to it and why I even raised the objection. Anyway, let's talk about this later. This is not worth any conflict over.


>I have reasoned as follows: Switch/case statements that have handlers for every item in the enum, but no default case get a default handler with an assert( false ).

hmm... I'd rather kept that as is, because of next reasoning:
If JointType will be altered in the future, it would be nice to have a warning here... but I won't insist on that your way may be useful to track more errors in runtime...


Hey Ken, I like your approach here. I think an issue is that you're searching for relationships that are master-detail to contact using npe4__Contact__c, which will get deleted automatically thanks to cascading deletes. It's the relationships where the contact is the secondary member, i.e. npe4__RelatedContact__c which is a lookup relationship, that we have to delete manually.

I've never tried querying an object related to a deleted record with ALL ROWS, does that work? I thought the relationship would just be blank at that point.

Maybe an approach could be to switch to a before delete trigger so we can query on the relationships before the contacts are gone, so we can query on npe4__RelatedContact__c IN :conctacts.keyset() and delete them before the contacts are deleted. I think this approach could impact our ability to recover that data from the recycle bin, though.


This looks good, too.


The type of the variable bad refers to the signature bad^ which is only available inside of the let body, the intent is to disallow references to signatures outside of their scope.


I think this might be slightly better as a std::deque<std::vector<>>


91958608DOASEffectOnZoneSizing (wfbuhl) - x86_64-MacOS-10.9-clang: Tests Failed

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


da hat jemand git und template misst gebaut - bitte noch https://github.com/FreifunkBremen/ansible/tree/master/roles/fastd/files/fastd löschen,
ein symlink ins repo bauen, damit https://github.com/FreifunkBremen/ansible/blob/master/roles/fastd/templates/fastd.conf ```on verify```
und hier der pfad anpassen.

----

der copy befehl wurde schon richtig entfernt :P  (ähm durch ein template ersetzt)
https://github.com/FreifunkBremen/ansible/commit/7911ef9eeb00cc8964b78167a3c054f60f0c738b#diff-8c2560430cc1c38986df1b21c9a1c178


Should check more.


:tada:


I think it is better to have a dedicated task_id for each subtask. Otherwise, the unique key will be (task_id, state) and it is harder to parse (both visually and with tools).

However there is an underlying issue to open with non-unique task_id in the `tasks/` folder.


Die habe ich nur leider nicht und er scheint im Moment nicht da zu sein, daher hatte ich erstmal einen Teil von Hand gemacht. Soviel war es gar nicht. Der Rest ist allerdings mehr. Naja, mal schauen.


What's the difference in this case? It only pushes/pops from the end.


We should add an assertion that the stack we are popping is empty.


I think this can be a non-release ASSERT


why more


Point to failing test in `fail` directory.


Thanks!! :)


@andrerom we may need to change `ezpublish.siteaccess.default.name` to `ezpublish.siteaccess.default`  A quick test show this did correct the var_dar for me.

https://gist.github.com/wizhippo/eca58cd9ebc6fff7b1a6


On 5.1 indeed /system/lib/libwebviewchromium.so is initially removed if webviewgoogle is installed from the package, but it should be then replaced by the libwebviewchromium.so from the package.
Because in inc.compatability.sh line 139 is specified that the libs of webview should go into /system/lib/ which should be applied in inc.buildhelper.sh line 79.
Then on inc.updatebinary.sh line 1148 and further it should make the symlinks from the app's folder to the systemlibs.


## TITLE

this commit rocks


here's what I love about this commit
 - it's small


I see, I didn't realize it was undefined.


It doesn't look like this variable is being used


require/typed will wrap u in a contract corresponding to that type, but the first order check will fail since the contract has fewer init-depends than the unit value.

The situation is similar to a module providing a variable bound to the number 5, which is then require/typed as a String, which will signal a contract error.


On 5.0 it should not remove it (if everything is well).


Thanks, I keep forgetting releases exist.


I should have changed this class to extend to the full width now that there's no button in the upper right corner. Long names wrap too soon.


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.5.38.de275939eed03371b4e82440214b2abb96f02201](http://build.palaso.org/viewLog.html?buildId=62574&buildTypeId=bt2) outcome was **SUCCESS**
Summary: Tests passed: 874, ignored: 50 Build time: 00:37:57


We are going to go over in class some style guide items. In Java we use Uppercase CamelCase for class names and lowercase camelCase for packages. Just something to start keeping track of.


@snorrees you are partially parent of the profiler!


Looks good :+1:


Why not use `get_astute_yaml` here as well?


Should this be `ezpublish.siteaccess.default` instead?


wait, I guess this setting is different than others. Like if caller changed dht_settings.enforce_node_id, then he needn't restart dht, because we are using a reference of dht_settings(a member variable of session_impl) everywhere.

But for this value, since it's a bool value, not a reference to settings, maybe your concern is right.


This is not enough.


Won't this replace $log_folder then with the value of this variable during the execution of the build process?
Probably best to remove all ' and " that are inlined in those messages IMHO.


Dlaczego mapa? Nie można na obiektach?


Is it better to write properties on top of pom.xml?


:clap:


Would you be open to releasing this change soon?
The version on NPM is currently broken with Webpack because it uses `main`.


Please at least test some non-trivial cases.


Fixes #14


@Nadahar try using [SwingUtilities.invokeLater](http://docs.oracle.com/javase/7/docs/api/javax/swing/SwingUtilities.html#invokeLater(java.lang.Runnable)) here so it happens in the swing event dispatch thread.


OK, keep this change, and add "onVisibleChanged: requestPaint()" I confirmed that fixes the regression.


The mnemonic for this code point is actually `NSAP-PTR`, not `NSAP_PTR`. Do we need to do a "_" -> "-" fixup in the Python code that generates `rrtype_to_str.c`?


Idem.


Miało lecieć do `.gitgnore` ale global.


The issue here is that the error occurs at runtime by checking performed by define-values/invoke-unit. This is an instance of a program which typechecks, but fails at runtime because no import is provided.


To bym wrzucił do master poma w dependency managment, a reszta tylko w konkretnym module bez wersji.


Ok, yes that seems to be what was used before as well above here. Do you open a PR? :)


I really like your resuse of the 's' and 'é'

How could you have renamed the variables to make that more evident?


Looks good :+1:

was the world


dehumidifier-fixup (kbenne) - x86_64-MacOS-10.9-clang: Tests Failed

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


> - add error for Tuple{x} where x isn't a Type

I guess you mean `Type{x}` ? (doesn't matter much either way...)


Sure there are many cases where exact floating point comparison is needed, but not enough to make it a default and have it chosen without people's realisation. It's trivial to opt-in by adding a one-line declaration to components that need it so I think that's best.
Yes, a PR for tolerance would be welcome. :+1:


I was looking at an example on asp.net for implementing a repository with a constructor that uses a context. They had an example which involved disposables, which I don't need because like you said, "using" already closes the connection/destroys object


> does i/o trim clips on all unlocked tracks?

With shift+i it will do a ripple trim affecting all later clips, and if multitrackripple is enabled, it will remove that same region for the other unlocked tracks in order to keep the tracks aligned.

> As you said yourself, you lost confidence in using implicit selection.

A bit unsure what you are referring to here? I have been unsure about implicit selection before for operations that do not depend on the playhead being over the clip (ie. remove/lift) that can accidentally affect something else that you did not notice was selected. But when the playhead position is required, as is for example also the case with the split command, there's no ambiguity about what will happen when pressing the key, so here I think it works well.

If you haven't already I suggest you try out the keyboard shortcut to get a feel of how it works... I'm a bit unsure about how to proceed.


Also maybe a default instance of `Reusability[js.Date]` would be better?


What character is 0


Should this be `{:ok, {0, queue}}`?


Haha Firefox 40 -> http://pl.tinypic.com/view.php?pic=24kxiio&s=8#.Vedm83Xtmko
Coś parsowanie wiadomości w message.js nie działa. :heavy_multiplication_x:
Czyli co, piszemy, że wspieramy tylko Chrome? :D @magic96  @marcinlacina @da-an


91958608DOASEffectOnZoneSizing (Myoldmopar) - i386-Windows-7-VisualStudio-12: Tests Failed

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


Generally, because of "Code Sign on Copy" there isn't a valid need to specify code signing details in a framework/library. You'd be second guessing how the developer would want to sign it anyway (if at all on OS X).


4952-FixBranchAgain (rraustad) - Win64-Windows-7-VisualStudio-12: OK (1815 of 1815 tests passed)

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


ah sorry i will link a moment for now i did have screen record compare AE glow.. (there are particulars.) you could to see video (my link from mega.nz ok?)


I haven't.  You are welcome to.  If not I can do it tomorrow.

On 2 September 2015 at 17:14, André R. <notifications@github.com> wrote:

> Ok, yes that seems to be what was used before as well above here. Do you
> open a PR? :)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ezsystems/ezpublish-kernel/commit/6f29cfa28adb27a5f526498cb8f35181be23b0cf#commitcomment-13034172>
> .
>

--
Douglas Hammond
VA3DJX


You didn't remove QString::Number()


Wouldn't this match multiple groups?
/:(.*?);/
might fix this


Then add it to the `xfail` directory.


ukljuci biblioteku stdint.h


That's fine - my primary concern is readability and freedom from side effects (accidental closure capture, etc).


Neither you changed the `limit/1024.` to `limit` since you changed the used function.


Yes, but we need to make the rules around playlist vs. multitrack consistent, not have a special behavior for alt. And only if playlist dock is opened.


As I said, remove the assigned. Otherwise there will be bogus text.


Як тобі, Віктор, мій коміт?
Особливо коментарій до коміту.

Ти готовий до плавання в морі Коду?


Why these empty errors? IIUC, this would cause the test to pass (because an error is thrown) even if the unit stuff doesn't error, which is wrong.


Of course now that I think about this it might be better to have a specific error handler passed to this (so clients could process errors).  We can deal with that later in the channels.

Does io.Copy return nil when EOF is reached?


develop (evanweaver) - x86_64-MacOS-10.9-clang: Tests Failed

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


Would this work just as well?
    run_with_timer(timeout) { return yield(self) }


raptorch?


Acredito que se não for alterado a linha 113 de Webservice-1.5-php/src/Cielo/Serializer/TransactionResponseUnserializer.php a correção não irá funcionar.


Looks like you have tab characters in here. We don't use tabs anywhere (they render differently on different machines, and that's not a good thing). Make sure your editor is set to not use tabs.


You should return value returned from function _pwm_read, since it may return differnt values. It may fail to open the file (EINVAL, malloc errors (ENOMEM)), fail to scan (EAGAIN, EBADF, EILSEQ, EINTR, EINVAL, ENOMEM, ERANGE), and you're return EIO if the function fails.

Just do something like:

r = _pwm_read(...);
if (r < 0) {
  SOL_WRN(...);
  return r;
}


Shouldn't most of these 2 lines be in init? The only thing decode needs to do is readValue() I would presume.


yes, io.Copy returns nil on EOF, and propagates other errors


samo ovu liniju prebaci u .c fajl


If a the arguments default to none it hints that they are optional, but it throws an exception if they are None. Is that the desired behaviour?


The introduction most likely shouldn't be a bulleted list. It should be an easy to read introductory paragraph using complete sentences and proper grammar.


Sorry, something must have happened during the rebase. All the changes were reverted!


Because of that annoying thing where the scrollbar changes the number - just validate it later on


If you have "Bedrock Dependencies" above, there is no need to repeat "Bedrock" in the list below it. You could just use "Bower:"


Is T really being used well here? I don't see any tests showing the use of the generic. Probably this can just change to Object.


@andrewcox I'm actually surprised there's a way to do this in maven, but will be very happy to drop this commit (and purge all knowledge from memory) :)


This is a good description - it tells the reader what it provides and what that thing provided does. You'll want to use this approach for the rest of the bulleted items.


I have not yet tried it, but one more question. There can be ambiguity when pressing i with no shift and  ripple-all-tracks off, and multiple clips under the playhead. So, if I have one of them selected, will it trim the selected one instead of the topmost? Does it give selection priority. I want to assert which clip to act on. Does it respect that?


Sorry, you're right, it's just that I now have 27MB more of free space in /system compared to the lasted flashed package in July, so I thought that was the problem. Maybe the old packages installed the library in /system/app/WebViewGoogle/lib/arm/libwebviewchromium.so instead of creating a symlink.


Should this link to docs.nuget.org instead of GitHub? Also, 3.1.1 was a minor patch. Should we link to NuGet 3.1 release notes instead?


My understanding was that the tc-err form expects an Error or Bottom type as the result which is why they all end in empty error calls, but that the tests will only pass if there is a typechecker error, so in particular

[tc-err (let () (error ""))]

Is actually a failing test since the typechecker accepts this program.


Might want to reword as "Provides directives for displaying a credential given an IdentityCredential object"


That was what I was referring to when I said “I am not sure how it works” since T is never specified.  I didn’t try just Object to see if it still worked
> On Sep 2, 2015, at 4:26 PM, Charles Swanberg <notifications@github.com> wrote:
>
> Is T really being used well here? I don't see any tests showing the use of the generic. Probably this can just change to Object.
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/wired-mind/usher/commit/eac041bf604541888f063776e7bd2aeeab4fd83a#commitcomment-13034399>.
>


You're right @loup99 I did, whoops. I'll get to work in it by Friday.


You dirty fuck having sex with my wife GlobalScum. You are far too old for her.


Change to "NPM:"


which two lines?


Shouldn't this be called out as RC release?


Yes, you're right. I'll fix it right away.


*fostering* (friendly note)


No; general types allow non-type parameters like `T{1}`, but tuples shouldn't.


ok i try this now..
link of pyplug of glow:

"You can control OpenCL from the terminal before you launch Natron
export MAGICK_OCL_DEVICE=OFF
export MAGICK_OCL_DEVICE=GPU
export MAGICK_OCL_DEVICE=CPU

So you only need the -OpenCL build, and export MAGICK_OCL_DEVICE=OFF if you don't want OpenCL"

Will in the future add the ability to control this with a param.

link video screen record AE for GLOW:
https://mega.nz/#!LhkliaIa!xJwvvcmczzs9jMUfFskcZU81oRl4rcFYQopY4iOa8Ao

link pyplug:
http://www.coyhot.com/no_CoyHot/Natron/PyPlugs/


*primitives*


Should this 'New Features' section go under Command line Updates? Command line should have 'New Features' and 'Updates and Fixes' section just like VSIX section


Yes. I was trying to keep everything a keyword instead of a argument.


I'm not sure why ``addToExpression_reorder`` is even being called with tuple arguments


Great thanks :)


You can just pass `sizeof(buffer)` here: that's the size of the buffer, not the length; the `ret >= sizeof(buffer)` check will check if overflow happened.


@Buckmarble thanks for the info


Is `method` guaranteed to be non-null by MHD?


You will want to elaborate more on this - REST API for credential storage and retrieval, which is used to X, Y, Z... I think we should clearly state what this module uses the dependency for, otherwise, there is nothing different between reading this one liner and just clicking through to the package and reading the first paragraph of description.


Notably, this commit has now caused `gulp-util` and `gulp` to have different versions of `vinyl` when installed, thus breaking assertions that a given `File` instance from a `gulp.src()` (actually `vinyl-fs.src()`) stream is an `instanceOf` gulp-util's `File` export. I understand work is underway to remove gulp-util's `File` export, but it'd be nice if the current version of gulp didn't have this disparity.

```bash
$ npm i gulp
$ npm ls vinyl
(cwd)
└─┬ gulp@3.9.0
  ├─┬ gulp-util@3.0.6
  │ └── vinyl@0.5.1
  └─┬ vinyl-fs@0.3.13
    └── vinyl@0.4.6
```

I would go so far as saying this broke the semver contract for a patch version, and since presumably the next major version of gulp-util won't have the vinyl `File` export, you should probably publish a `v3.0.7` that downgrades the vinyl dependency version back to `^0.4.0`.


should be be utf-16? Do emoji's work?


What should link to docs.nuget.org?


Also Instant Messaging.
See https://github.com/nylira/prism-break/pull/1392


Why do you need "authentication to bedrock"? You'll want to explain where and why this module needs authentication.


Yes...  I'll rename release notes and re-label as 3.2-RC


The three of us might want to talk about exception handling here. Our only real use-case is the KafkaInput plugin. We definitely want to ensure tight integration there. I don't think we can just log and do nothing. You'll notice in the RuleBasedPacketParser which is used by the PacketSplitter that if the splitter encounters a byte sequence it doesn't recognize it throws a PacketParsingException. This is handled right here: https://github.com/wired-mind/usher/blob/d8b181b1a3a96cadb27a01f34459caabc85c518c/src/main/java/io/cozmic/usher/streams/ChannelFactoryImpl.java#L71. The two things are similar and probably what I did in the RuleBasedPacketParser will need to change with whatever we come up with here.

The big thing here is we need to decide if/how we communicate back with the KafkaInput plugin. The scenario is that an entry in kafka can't be decoded. We'll be building in something so that we can commit or not commit to kafka based on if we succeed or error.


Click View in Github


access control to what resources?


BTW I think that quoting all is better, even if *$log_folder/open_gapps_log.txt* is not a "dangerous" string, also because it looks better when analyzed with an editor that uses a different color for quoted text.


@maximevince, @phalox,

In the latest commit (1f88ff6f7e7c941f58491f83342f89b90b5a9373) I've updated the pico_device-structure with a "media layer type"-enum type, like Maxime's proposal. Before the pico_device_init()-call this mode can be set to something not 0 (0 means Ethernet or LL_MODE_ETHERNET) to express another type of L2, in this case 1 or LL_MODE_SIXLOWPAN, which means that the device is a 6LoWPAN-capable device.

If existing drivers check for ethernet-devices with;
```C
if (dev->eth) {
   /* ... */
}
```
then this implementation is not backwards compatible with existing drivers though. Since the eth-pointer can also be set for, for example, 6LoWPAN-devices. The proper check for ethernet devices should be:
```C
if (!dev->mode && dev->eth) {
   /* ... */
}
```
But as long as existing applications don't work with 6LoWPAN-devices this shouldn't be an issue.


T is likely Object at runtime if you're creating the class without specifying using reflection (which is what the plugin loader does).


I'll check


I agree


actually the above was simple my curiosity how this gc thing worked and simple trial-and-error, so no idea what's wrong with it...

On the other hand, this thing (as above) is not working if a user assigns the result of a slice to a dict or a list :-/

My updated code got quickly out of hand:

```
import gc
import inspect
import collections
import re
import types

def get_names_for_obj(__really_unused_name__342424__, exclude=None):
    """Returns all named references for self"""
    import gc
    import inspect
    removals = {"__really_unused_name__342424__", "__really_unused_name__xxxxx__", "self"}
    if exclude:
        removals = removals | set(exclude)
    gc.collect(2)
    refs = gc.get_referrers(__really_unused_name__342424__)

    names = []
    for ref in refs:
        if inspect.isframe(ref):
            for name, __really_unused_name__xxxxx__ in ref.f_locals.iteritems():
                if __really_unused_name__xxxxx__ is __really_unused_name__342424__:
                    names.append(name)
    for name, __really_unused_name__xxxxx__ in globals().iteritems():
        if __really_unused_name__xxxxx__ is __really_unused_name__342424__:
            names.append(name)
    return set(names) - removals

def get_all_names_for_obj(__really_unused_name__342424__, exclude=None, __cache_123__=None, depth=2):
    """Returns True if the argument is referenced from a container"""
    removals = ["__really_unused_name__342424__", "__really_unused_name__xxxxx__", "__v__", "self",
                "__globals__", "func_globals", "__self__", "im_self", "cell_contents", '__dict__'
                "user_ns", 'namespace', 'user_global']
    if exclude:
        removals.extend(exclude)
    if __cache_123__ is None:
        __cache_123__ = []
        __cache_123__.append(__cache_123__)

    gc.collect(2)
    refs = gc.get_referrers(__really_unused_name__342424__)
    __cache_123__.append(refs)

    def _get_names(refs):
        names = []
        container_names = []
        for ref in refs:
            if ref in __cache_123__:
                continue
            __cache_123__.append(ref)
            if id(ref) == globals().get("__ID_D__", None):
                print(inspect.isframe(ref), isinstance(ref, collections.Mapping),
                      isinstance(ref, collections.Sequence), isinstance(ref, object),
                      ref)
                pass
            try:
                if inspect.isframe(ref):
                    for name, __really_unused_name__xxxxx__ in ref.f_locals.iteritems():
                        if __really_unused_name__xxxxx__ is __really_unused_name__342424__:
                            names.append(name)
                elif depth < 1:
                    # don't try to get too deep into container ref cycles...
                    continue
                elif isinstance(ref, collections.Mapping):
                    _names = list(get_all_names_for_obj(ref, exclude={"ref", "refs"}, __cache_123__=__cache_123__, depth=depth-1))
                    if len(_names) == 0:
                        continue
                    for _name in _names:
                        name_in_map = "<unknown>"
                        for k, __v__ in ref.items():
                            if __v__ is __really_unused_name__342424__:
                                # we don't want to catch whatever['namespace'] and similar things
                                if name_in_map not in removals:
                                    name_in_map = k
                                    # only catch the first instance
                                    break
                        if name_in_map != "<unknown>":
                            # check that we don't have class backing dict (xxx.__dict__)
                            # -> this should end up as xxx.<name_in_map>
                            if _name[-9:] == ".__dict__":
                                container_names.append("%s.%s" % (_name[:-9], name_in_map))
                            else:
                                container_names.append("%s['%s']" % (_name, name_in_map))
                elif isinstance(ref, collections.Sequence):
                    _names = list(get_all_names_for_obj(ref, exclude={"ref", "refs"} ,__cache_123__=__cache_123__, depth=depth-1))
                    if len(_names) == 0:
                        continue
                    for _name in _names:
                        item_pos = ref.index(__really_unused_name__342424__)
                        container_names.append("%s[%s]" % (_name, item_pos))
                elif isinstance(ref, object) or isinstance(old(), types.InstanceType):
                    _names = list(get_all_names_for_obj(ref, exclude={"ref", "refs"}, __cache_123__=__cache_123__, depth=depth-1))
                    if len(_names) == 0:
                        continue
                    for _name in _names:
                        for n in dir(ref):
                            if getattr(ref, n, None) is __really_unused_name__342424__:
                                if n in removals:
                                    continue
                                container_names.append("%s.%s" % (_name, n))
                else:
                    _names = list(get_all_names_for_obj(ref, exclude={"ref"}, __cache_123__=__cache_123__, depth=depth-1))
                    container_names.append("<included in item of type %s with name(s) %s>" % (type(ref), _names))
            finally:
                __cache_123__.remove(ref)
                del ref
        return names, container_names
    names, container_names = _get_names(refs)
    __cache_123__.remove(refs)
    for name, __really_unused_name__xxxxx__ in globals().iteritems():
        if __really_unused_name__xxxxx__ is __really_unused_name__342424__:
            names.append(name)

    return list((set(names) | set(container_names)) - set(removals))

class whatever(object):
    def is_item_in_refs(self, item):
        import gc
        refs = gc.get_referrers(self)
        for ref in refs:
            if item is ref:
                print(ref)

    def print_names(self):
        print(",".join(get_all_names_for_obj(self)))

    def __getitem__(self, val):
        import gc
        ref = gc.get_referrers(self)[0]
        double_slice = getattr(ref,'im_func',None) is not None
        print("__getitem__: %s, %s" % (double_slice, get_all_names_for_obj(self)))
        ww = whatever()
        #return w2
        return ww

    def __setitem__(self, key, val):
        import gc
        ref = gc.get_referrers(self)[0]
        double_slice = getattr(ref,'im_func',None) is not None
        print("__setitem__: %s, %s" % (double_slice, get_all_names_for_obj(self)))

#print(dir(o))
global __ID_D__
__ID_D__ = None

w = whatever()
l=[w]
d={"w":w}
class c(object):
    pass
o = c()
setattr(o, "w", w)
o.w
w.print_names()

wxw3x = whatever()
wxw3x[1] = 3
wxw3x[1][1] = 3
w2 = wxw3x[1]
w3 = w2
w2[1] = 3

d = {"w" : whatever()}
#d["w"].is_item_in_refs(d)
d["w"][0] = 1
d["w"][0][0] = 1
d["x"] = d["w"][0]
l = [d["x"]]
d["x"][1] = 1
```


We can show all shortcuts in the UI, but I see no point in allowing the user to define more than one.


Not that it really matters, but I put an empty line before the final return in all the functions, I guess as a habit... So this was intentional.


Maybe it's better to save path as a sol_str_slice, and use its comparison function here? Not only it'll be slightly faster (as it compares the length first), but slightly more secure, as this is a value passed down from the network and it's not a good idea to compare it without a boundary.


I did that, but it's just a comment name, doesnt matter much. I'll make it cleaner next time I update it, thanks.


Hmm, I think my comment says that I _do_ expect those.  All command callbacks will receive commands which they cannot interpret, that is the point of the comment.  Sorry if that was not clear.


I'm not sure this is a great name for this -- it's a description of the problem and not really the object itself.  I'd advocate for something like "GCVisitable".  We could also make GCAllocatedRuntime inherit from this.

I'm still against using virtual inheritance for all of this :/  But I guess let's go with it for now, but I'd say let's make the destructors `=delete` rather than `=default`.


I think this could be named something like `ScanningHandle`.


Is the conversion ok?


This module should be removed ASAP from phobos.

* not d style
* not even conform to detect what's an URI, and barely able to validate an URL.

[URI specs](https://tools.ietf.org/html/rfc3986#section-1.1.1)


this allowed me to compile in VS2015 but now getting another error! Good fun!


Is there a reason it needs to be a doubly-nested list?  This commit at least seems to treat it as a one-dimensional structure.


See https://sympa.inria.fr/sympa/arc/caml-list/2015-09/msg00011.html -- x87 messing things up, of course.

And since I happen to be at ICFP right now I just grabbed Xavier in person, and he pointed me to an Ocaml binding for the MPFR library (I think http://pop-art.inrialpes.fr/~bjeannet/mlxxxidl-forge/mlgmpidl/). We could also try to use that (it would cover float32), but it's probably too big a hammer for what we currently need.


This just truncates the value. Should be OK.


That seems like an acceptable solution if you are being mandated to use Chrome 28.


I was trying to have a single stack in the beginning, which makes sense because I only push/pop stack bound variables on it. But I ran into two problems.
1) Push/pop happening out of order (when switching back and forth between generator stacks).
2) Pops not happening because the generator would stop running and eventually get GCed, and the local variable's destructors never get called.


@jfleong Nice, gotta watch Top Gun!


Yes!


@brycemcd here you go!


91958608DOASEffectOnZoneSizing (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1292 of 1292 tests passed)

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


Посмотри внимательно недели и номера лекций.


Why static? What happens if there are two boolean nodes in a single program?


Где-то упустили 4 лекцию.


2 лекции на 1 неделе?


Foi sim; removi o cast para inteiro que era feito.


oh, no sorry I meant that the inner vector that we are popping off doesn't still have any elements in it.  If we run into that case, we would need to save those elements onto the generator object, scan them as part of the generator, and then push them back on the the outer stack when we resume the generator.

Actually probably a simpler strategy would be to have the generator vectors live on the generator objects themselves (and one on the thread info), and then have the thread info just store a pointer to the current vector.


"Doctor! It hurts when I punch myself in the face!"

I don't see a bug here to fix.


Being default == null, are we using mt19937 for the node always? We can do better if possible, no?


Other than that, LGTM.


>ok, ValDegre. and anElement are not removed; I did not dare to do that. I just mention them with a useless statement at the end to keep the compiler happy. It is probably an error in the original code to not interpret the result in e.g ok, but that is not a task for now (or for me!).

IMHO clean build log doesn't worth masking a potential error...

>Variables that have been removed by commenting them out will actually generate a compile error if they are used somewhere else, so I'm pretty sure they are covered ok.

Important thing about src/3rdParty/salomesmesh/src/SMESH/SMESH_MeshEditor.cpp:
seams surface->{UV}Period() have some indirect result... check out upstream changes here:
https://git.salome-platform.org/gitweb/?p=modules/smesh.git;a=blobdiff;f=src/SMESH/SMESH_MeshEditor.cxx;h=324b6b81dabf7a55c2d5b9085717e9d949de8ae6;hp=063f68819b32d16555af4e0042897aa02c1fdbac;hb=bd4e115a;hpb=0635c9fc80f67d1e5dc0e94ec85f487286a92070

PS: I haven't checked all of them, but it seems upstream already fixed those warnings, IMHO it would be better to backport patches from there (where possible)...


@joseph-jalbert - I think here you should create one function and enqueue all scripts unless there is some specific reason you did it on a per script bases?


It looks like it crashes for me on the top level

```
$ cat test03.ml
(* Open up a simple database *)
let db = Sqlite3.db_open "foo.db"

(* Create a table *)
let _ = Sqlite3.exec db "create table foo (name text,value real);"

(* Put some random data in a list *)
let mydata = List.map (fun name->(name,Random.float 1.0))
    ["frank";"bob";"larry"]

(* Put this data into the database *)
let myinsert (name,value) =
    let s = Sqlite3.prepare db "insert into foo values (?,?);" in
    let _ = Sqlite3.bind s 1 (Sqlite3.Data.TEXT name) in
    let _ = Sqlite3.bind s 2 (Sqlite3.Data.FLOAT value) in
    let _ = Sqlite3.step s in
    let _ = Sqlite3.finalize s in
    ()
let _ = List.iter myinsert mydata

(* Register a function to throw an error *)
let myerror x = failwith "This is a user defined error"
let _ = Sqlite3.create_fun1 db "myerror" myerror

(* Run the error *)
let res = Sqlite3.exec db "update foo set value = myerror(value);"
let _ = Printf.printf "%s\n" (Sqlite3.Rc.to_string res)
```

and

````
$ ocaml -I /home/josyoun/installed/sqlite3-ocaml/_build/lib sqlite3.cma test03.ml
Segmentation fault
```

However, it does work if this file is compiled

```
$ ocamlc -I /home/josyoun/installed/sqlite3-ocaml/_build/lib sqlite3.cma test03.ml -o test03
$ ./test03
ERROR
```

It also works on the top level if we change the query to

```
let res = Sqlite3.exec db "select myerror();"
```

However, looking at the code, does your fix just enable `exec` to return `Rc.ERROR`?  Basically, the use case that I'm concerned about is using a user defined function to either insert or update from a large query.  If the function fails, I generally have enough information to produce a sensible error message as to where with something like `sqlite_result_error`.  For example, if I wanted to run `log` on a bunch of data, I'd write the user defined function to accept both the value name as well as the value.  If the value is positive, we return the log.  However, if the value is nonpositive, we can throw `sqlite3_result_error` with the value name.  Returning `Rc.ERROR` for the entire query loses this information.


I understand that.
What I'm saying is: signature expressions (or their internal syntax) are just forms inside the `let` body. The typechecker already goes over the contents of the `let` body and recurs on them, which calls the appropriate function, depending on what each form is. (The dispatch being in `tc-expr`, or similar.) Could you just move the work that's being done here for signatures to one such function instead of here?


@joseph-jalbert - This should be stored by using bower.  `bower install .... --save` should do the trick. Take a look at the docs though. You shouldnt store vendor dependencies in the repo. Take a look at the docs for bower to see. All is stored in the bower.json file.


Yes they did. So that explains the difference you see.


@nyalldawson these changes for symbol renderer seem to break the API. Shouldn't be reimplemented the ```virtual QgsSymbolV2* symbolForFeature( QgsFeature& feature );``` method as well?

The following code does not work anymore:
```python
vl = iface.activeLayer()
f = QgsFeature()
symbol = vl.rendererV2().symbolForFeature(f)
```
I also see the ```symboloForFeature( QgsFeature& feature )``` method is deprecated in ```QgsFeatureRendererV2```, but it is supposed to work in qgis 2.12, isn't it?

thanks.


Closes #7


Зачем такая точность? Когда это может быть нужно?


Tried this, getting an extraneous 'endif' error at line 150 of firmware-common.mk.


At the moment, yes -- but MT19937 is actually a quite good PRNG, and suitable for most applications.

It might be possible to have an option to pick the engine; for instance, reading too much from /dev/urandom is often not a good idea due to entropy pool exhaustion. See getrandom(2), where it states that it's not a good idea, for instance, for Monte Carlo simulations and other programs that are performing probabilistic sampling.


Well, it sounds like you're not sure whether it's necessary, but it doesn't hurt. Let's leave it that way.


Ok.


yes. i agree with that. that quoting is indeed more neat. my comment about quotes is meant at situations where they are used in a textual way within the result-scripts like update-binary.


Could they appear standalone if you just type `a^` at the REPL? Or ask for `a^`'s type?


:+1: for the name clarification


xx


Because I've made a mistake when I've released that version and I wanted to tag it even though.


sneaky pep8 fixes


91958608DOASEffectOnZoneSizing (Myoldmopar) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


Ohh, excuse me that was an another. This is part of the master.


I don't think so, and trying an example in the repl seems to confirm this. References to signatures outside of unit should be syntax errors.


Fack! Typo, should be just "raptor" dude. Man am i glad you double check my
work :)

-L
On Sep 2, 2015 6:22 PM, "Fevix" <notifications@github.com> wrote:

> raptorch?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Luthor614/Avali/commit/fce298d576484dec1fcdd64fbdbf568019134a3a#commitcomment-13034337>
> .
>


I went full-retard, let me check :)


I think that setting the `cmake_minimum_required(VERSION 3.0)` before the `project(Boost.Hana CXX)` line will silence the warning. Can you confirm?


Fixed it, thanks for reporting.


`if (m_playlistDock->isVisible() && (event->modifiers() & Qt::AltModifier))` should take care of it.


As the comment mentions, to get the correct number of clocks for the Neo Geo so it produces a frame once every 60th of a second, we need to produce a clock transition every 11 and 111 1024ths cycles of the 270MHz clock. The fractional part is stored in fraction (as current number of 1024ths). Every cycle we check the top bit (>=1024) to see if it's set and if it is do an extra full cycle (we set neoGeoClks to 15 which is equivalent to -1 for this counter). We then mask off the top bit (&1023) because that extra full cycle has now been accounted for and we add 111 to keep accumulating. Does that help?


4695_hpwh_equip_seq_num (nmerket) - x86_64-MacOS-10.9-clang: OK (1813 of 1813 tests passed)

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


Jared Jones
  512-968-4435
  jared.jones2@g.austincc.edu


We should integrate this into the type system; ie createRewriter should return something like a `gc::ScanningHandle<std::unique_ptr<Rewriter>>` which is not implicitly convertible to a `std::unique_ptr<Rewriter>`.  Well, that might take some template-fu, or maybe we could fold the unique_ptr auto-deletion into the ScanningHandle class.


thanks, fixed with a force push :smile:


Oh I see what you meant now. I think the problem with that becomes that the result-type of a let-body may reference a locally defined signature which should be prevented from escaping, but if signatures are typechecked as expressions then there would be no way of knowing which signatures were defined within that scope and should be prevented from escaping.


:+1: :koala:


fix_vscoils_coilsystem (mbadams5) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2261 of 2332 tests passed)

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


I had to put this handleSuccess noop in a few times because it isn't possible to provide a default implementation of a method that can be overridden like you can with inheritance (which isn't compatible with React).


Ok, era porque '(to) partition' es el término común en inglés. Para jerga técnica me fío antes del diccionario de la RAI, pero 'particionar' no está tampoco. Así que tu solución me parece perfecta, [partición](http://diccionario.raing.es/es/lema/partici%C3%B3n-de-disco) sí viene bien definida. Lo corrijo en 14f855b.


You can try to use the top-level to get the types to print, or something. Or add some hooks so you can add mock signature objects. There's a number of ways this can be worked around.


Turns out the crate has to be public, but not the arena - I need access to the crate after lowering in driver/pretty.rs


Ok.


Note that I had to upgrade the test project to .NET 4.0, so I can create `Delegate` instances that have `void` return type, e.g., `Action`, via `LambdaExpression.Compile()`. This is not a problem, is it?


These need to move someday


Are these issues actually addressed by the nested-stack approach?


This commit wasnt needed if you guys know what your doing instead of copy/paste everything.
You guys copy/paste so many commits that you even don't know what you even pull and also don't even know your own source. The original buttons made by hyde would have worked without any issues on bliss source as the "sync status bar signal cluster code with AOSP" commit was already present in the bliss source . So instead of stealing this commit and the main qsbar commit out of our (Cyanide and Fusion) private repo's thru Jacob McSwain. And just pulled it from hyde then you only had to modify a few little things to get it to work on cm based roms. (Only 5 minutes work) But you need to know what your doing!! You guys proved multiple times that you all don't know what your doing. So to get a nice feature that you guys want and cant port/make yourselves then steal or copy/paste it from all REAL devs that do the actual work and spend many hours of work on such features, ports or fixes.

Also the comment in the main qsbar commit is total bullshit. like i said just had to pull it from hyde, then
you could have written own comment to it, if you got it to work by yourselves on cm based roms.

Happy copy/pasting in the future and be happy with this.


Hm, strange that the toplevel would crash but not the compiled version.  I'll look into that, thanks for the report.

`exec` will only return `Rc.ERROR` if the error was not caused by a user function exception.  If the user function raises an exception, `exec` itself will raise this exception.  The database will still know the error of the last statement (i.e. that an exception was raised), though it won't remember the exception itself.  But the user is free to raise any exception with any helpful information they want and catch it at the call site of `exec`.  This should give you much more flexible error handling than merely receiving an error string.


To by som dal rovno do css ako hidden,


Yes in that I don't trigger my assertions (that things are pushed/popped in the right order). However, I do not have a great understanding of how the generator stack switching is implemented.


Awesome thanks!

After merging this, I may implement it slightly different with a method on validator itself to avoid duplicate code.

I'll also make sure to implement in v8, which is coming soon.


Sorry, I am a beginner. I have built a game and would like upload it to both android and iOS. I would like to integrate ChartBoost in my game. Will this help?


Also, I didn't test this new technique for dealing with stack objects against the moving gc.


Toto sa podla mna da poslat aj v data `data: criteria` a vyescapuje to za teba.


Seems this does break the redirects, as it now redirects to the hostname. Guess we need to change the apache templates too, as they use the "alias" and "name" attributes in a bunch of places, right?


처음시도


`form_for`, `select_tag`, `options_for_select` a tak.


Oh, and about vector-vs-deque -- deque has some nice properties over vector which can make it nice when it's usable (stack/queue usages).  vector will need to move its elements when it resizes but deque doesn't; I'm not sure how much that matters here since hopefully it can use the inner vector's move constructor.


@Brit200313 Yeah, so, hows about I get the coverage to 80% (which I doubt it is) and then do a pull request and THEN work on fleshing out the actual user/email situation?


Thanks for catching this issue! The name changed earlier this year, prior to GA of the Python SDK, and the sample had not been updated.


> Organization


1579840-GroundTemps (mmatts) - Win64-Windows-7-VisualStudio-12: OK (1801 of 1824 tests passed)

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


fix_vscoils_coilsystem (mbadams5) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Looks reasonable. Can you git --amend to fix the commit message?


Ponieważ użyliśmy `id__in=id_list` mamy z powrotem zwykły queryset - `count()` będzie działał poprawnie.
Można zmienić przy okazji.


dangling string, fixed in subsequent commit


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/20034/testReport/) for this commit**


Doesn't lexical scope give you that already?


Why the changes? exit 0 implies success, which this doesn't seem to be.


looks suspicious... I suppose here should be:
```
if (ret < 0) {
    return ret;
}
```
or some other negative value...


This change is useless, reference: https://github.com/CyanogenMod/android_device_yu_tomato/commit/05ba56c52d27dcb5878c3b67775d4a57d0186dc0


Tu asi chces `live`, toto vyrabas dobry event storm po par klikoch.


Done! Thanks.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1289 of 1289 tests passed)

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


Tie dva riadky sa daju spojt do jedneho.


Is that the expected behavior?


You can do this with system.prop, take a look at cyanogen/msm8939-common


Ok, thanks


let's add this to `try_delete` in `tools/tempfiles.py` (maybe it should be in `shared.py`?), and use try_delete instead of `rmtree`


Hi @jkutner,

I think there's an unexpected interaction that is caused by this commit and Clojure buildpack.
Prior to this `JVM_OPTS` (which [gets set by Clojure bp][1] like so `export JVM_OPTS="${JVM_OPTS:--Xmx400m -Dfile.encoding=UTF-8}"`) had no effect on setting `JAVA_OPTS` with dyno-appropriate memory settings. But as of this commit, if `JVM_OPTS` is present and has `Xmx` in it, which it always does on Clojure dynos, JAVA_OPTS is no longer set. Also JAVA_TOOL_OPTIONS ends up lacking Xmx settings too.

I noticed that one of our apps started having R14 errors because the JAVA_OPTS setting has disappeared. We launch this web app like so (quoted from its Procfile):
```
web: java $JAVA_OPTS -cp target/uberjar/elided.jar clojure.main -m some.server
```

Also order of evaluation of shell scripts in `.profile.d/` is undefined (if I remember right), so this error ends up happening sporadically, I bet.

[1]: https://github.com/heroku/heroku-buildpack-clojure/blob/92020d2fbd0d11d7050c9ff1dd31d05f0e386cb3/bin/compile#L160


Toto je tu na co?


-  export MAGICK_OCL_DEVICE=GPU:
   maybe there is little little strange 2things:
- 1 first frame and 2 frame is begin to dark, 3- 30 is ok procress.. :-1:
- 2 number of value from amount and from softening are strange number feedback.. :-1:

see screen record:
https://mega.nz/#!blFBVApZ!6pMA72ajpYZyZ0UL3EKHHJudBTJmCCGF25nhj3_ySpE

****

-  export MAGICK_OCL_DEVICE=CPU:
   maybe there is little little strange 2things:
- 1 first frame to 30 frames is perfect result.. :+1:
- 2 number of value from amount and from softening are strange number feedback.. :-1:

see screen record:
https://mega.nz/#!LgtGSagC!8LxGYsVE617-rtaU2oxJ9yuKX9V6d9UjnY0CZw_7jbI


All these are either in /vendor/cm or in /build


Ok, no worries then.


I confirmed with @stephentoub that the usage of `ThreadPool.QueueUserWorkItem` is a fine idea: there are no plans to remove this API from .Net Core.


Ok, no problem then.


Ked nemas obrazok tak sem dojde `<div>No Rep Image</div>`.


@mikehearn Yes, see https://github.com/bitcoinj/bitcoinj/pull/1074


I still don't understand why the typechecker needs to check that. Lexical scope should be enough.


1579840-GroundTemps (mmatts) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


These two will most likely cause trouble (with the first being a proper prefix of the second).
Perhaps, it might be better to replace the first rule with:
```xml
<RegEx find="\b([dD])esi(?!ć)" replaceWith="$1ogodi" />
```


Shouldn't need a default value -- when would you want a set with an empty value?


Cool idea.  Here's some more code to help with the testing and clarify what the change in v3 allowed and what I'm trying to accomplish with your new changes.  In v3, I could write this:

```
$ cat test04.ml
(* Open up a simple database *)
let db = Sqlite3.db_open "foo.db"

(* Create a table *)
let _ = Sqlite3.exec db "create table foo (name text,value real);"

(* Put some data in a list *)
let mydata = [("frank",1.0);("bob",-1.0);("larry",2.0)]

(* Put this data into the database *)
let myinsert (name,value) =
    let s = Sqlite3.prepare db "insert into foo values (?,?);" in
    let _ = Sqlite3.bind s 1 (Sqlite3.Data.TEXT name) in
    let _ = Sqlite3.bind s 2 (Sqlite3.Data.FLOAT value) in
    let _ = Sqlite3.step s in
    let _ = Sqlite3.finalize s in
    ()
let _ = List.iter myinsert mydata

(* Register a function to throw an error *)
let mylog name x =
    match x with
    | Sqlite3.Data.FLOAT x ->
        begin if x > 0. then
            Sqlite3.Data.FLOAT (log x)
        else
            Sqlite3.Data.ERROR (
                "Attempted to take the log of a nonpositive element: " ^
                (Sqlite3.Data.to_string name) ^ " = " ^ (string_of_float x))
        end
    | _ -> Sqlite3.Data.ERROR ("Attempted to take the log of a non-float: " ^
        (Sqlite3.Data.to_string name) ^ " = " ^ (Sqlite3.Data.to_string x))
let _ = Sqlite3.create_fun2 db "mylog" mylog

(* Run program error *)
let res = Sqlite3.exec db "update foo set value = mylog(name,value);"
let _ = match res with
| Sqlite3.Rc.ERROR -> Printf.printf "%s\n" (Sqlite3.errmsg db)
| _ -> ()
```

This returns

```
$  ocaml -I +sqlite3 sqlite3.cma test04.ml
Attempted to take the log of a nonpositive element: bob = -1.
```

With the new code, the example would be

```
$ cat test05.ml
(* Open up a simple database *)
let db = Sqlite3.db_open "foo.db"

(* Create a table *)
let _ = Sqlite3.exec db "create table foo (name text,value real);"

(* Put some data in a list *)
let mydata = [("frank",1.0);("bob",-1.0);("larry",2.0)]

(* Put this data into the database *)
let myinsert (name,value) =
    let s = Sqlite3.prepare db "insert into foo values (?,?);" in
    let _ = Sqlite3.bind s 1 (Sqlite3.Data.TEXT name) in
    let _ = Sqlite3.bind s 2 (Sqlite3.Data.FLOAT value) in
    let _ = Sqlite3.step s in
    let _ = Sqlite3.finalize s in
    ()
let _ = List.iter myinsert mydata

(* Register a function to throw an error *)
let mylog name x =
    match x with
    | Sqlite3.Data.FLOAT x ->
        if x > 0. then
            Sqlite3.Data.FLOAT (log x)
        else
            failwith ("Attempted to take the log of a nonpositive element: " ^
                (Sqlite3.Data.to_string name) ^ " = " ^ (string_of_float x))
    | _ -> failwith ("Attempted to take the log of a non-float: " ^
        (Sqlite3.Data.to_string name) ^ " = " ^ (Sqlite3.Data.to_string x))
let _ = Sqlite3.create_fun2 db "mylog" mylog

(* Run program error *)
let res = Sqlite3.exec db "update foo set value = mylog(name,value);"
let _ = match res with
| Sqlite3.Rc.ERROR -> Printf.printf "%s\n" (Sqlite3.errmsg db)
| _ -> ()
```

At the moment, this crashes the top level (it's not all that different from the example above),

```
$ ocaml -I /home/josyoun/installed/sqlite3-ocaml/_build/lib sqlite3.cma test05.ml -o test05
Segmentation fault
```

When compiled, it doesn't crash, but it doesn't look like exec is reraising the exception:

```
$ ocamlc -I /home/josyoun/installed/sqlite3-ocaml/_build/lib sqlite3.cma test05.ml -o test05
$ ./test05
OCaml callback raised an exception
```


It shouldn't be 20th percentile.  It should say "The 20th percentile vote is the new block size limit for an increase, and 80th percentile vote for a decrease".


5110_stdbaropress_sealevel (nmerket) - x86_64-MacOS-10.9-clang: OK (1794 of 1813 tests passed)

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


This test is to ensure that signatures can't escape let bodies, because the general problem would be something like the following:
```
(define-signature bad^ ())
(define bad@
  (let ()
    (define-signature bad^ ())
    (unit (import bad^) (export) 5)))
(invoke-unit bad@ (import bad^))
```
Without the check that prevents signatures escaping, I think this would still be a type checking error, but the message would be approximately:

expected: (Unit (import bad^) ....)
received: (Unit (import bad^) ...)


Currently all the ab_compare_*.sh scripts do a test on the y4m to try to count the frames. They then convert to PNG if frames > 1. Instead of working around this, how about:
- remove the png conversion from ab_compare_*.sh
- add the test and conversion to ab_compare.sh (or maybe just make a command line option if the conversion should be done)


93651760-RowPerObjectReport (JasonGlazer) - i386-Windows-7-VisualStudio-12: OK (1815 of 1815 tests passed)

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


Could we just iterate over ics_by_return_addr instead of keeping the separate list?  It seems error-prone too to maintain two separate lists in two similar but slightly-different ways -- especially since I'd imagine we are relying on them containing the exact same elements.


Leftover: removed in 3ad1b82


Vehicle.build(row)


This is what actually fixed it...


I believe this is standard practice to signal that you are expecting hash params or such? Someone correct me if I'm wrong.


bez { na końcu, prosta jednolinikowa pętla znajdzie ppierwszy niezerowy, dodatkowo niech bedzie A[i]<=0


:octopus:


The correct way to do that would be via rdoc


I know, I always use system_prop.mk tho. Feel free to switch it, I don't care either way, it's just a habit to fall back to system_prop.mk


@druzus: Przemek, this patch may not be correct here, as `nRead` will have `uiRest` added to it, so it won't match `FS_ERROR` in case of an error.

See my patch for it: https://github.com/vszakats/harbour-core/commit/31fb998b7e64271a049e37acaeff2593faf869c9#diff-9af7df3fac6eaae66b9c58fa1065d386


I think so, we discussed this example a while ago with Robby, essentially it needs to check the type of the fact binding, but it also produces that binding and without the use of `link` it can't connect them so results in a runtime error.


w tym miejscu dodaj sprawdzenie czy pierwsza liczba jest wieksza od 1, jesli jest to mamy wynik :)


Trebuchet is crashing due to a missing class, but yeah I see that now.


Bug: si querias aplicarle un aspect a una lista vacia el flatten va a causar que se ignore


Since this is an early return I suppose the property's user-defined setter won't get called, right? I'd say that the type coercion be skipped, but the setter still be called later on (https://github.com/skatejs/skatejs/blob/3b6dcaf4566d6a33da76de88193273255a18d088/src/lifecycle/properties.js#L103, but `s/newValue/value/` I expect), at least to serve as acknowledgement of the property being changed in some way.


Update


take into account also that it doesn't makes a lot sense to wrap MESSAGE macro into an additional _DEBUG_ ifdef


1579840-GroundTemps (mmatts) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1802 of 1824 tests passed)

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


develop (kbenne) - Win64-Windows-7-VisualStudio-12: Build Failed

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


oh man i'm embarrassed by this one for sure... :)


Could we publish a release ?


test


testa


Aquele algoritmo de busca de números primos é uma loucura.


I think I'll come back to this (after addressing the other comments) and see what happens if I remove the escape analysis because if it can be removed I think your suggestion would significantly improve signature handling.


lol


It should work - the deprecated method calls the new symbolForFeature( feature, context ) method, which is the one which is reimplemented by all the renderers.

What happens when you run your code? What's the actual error?


93651760-RowPerObjectReport (JasonGlazer) - Win64-Windows-7-VisualStudio-12: OK (1815 of 1815 tests passed)

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


You guys have awesome skills


I'd suggest renaming the parameter to something like `baseUrl`. Relative URI implies that it is path only and without a scheme. But in this case, we're expecting an absolute URI.


@stale2000 that is what I initially thought Jeff meant, but if you read the post to the dev list in the pull request description, it looks like he really meant 20th percentile. If the interpretation in this pull request is wrong, the meaning should be clarified via another change because no one seems to understand what the existing text means.


Thanks for looking into this. And it's good to know there's a multi-precision library available in case we need it. Fortunately for now, I believe the current technique of using 64-bit math with explicit rounding to 32-bit should suffice for everything in WebAssembly right now.


I have been testing this out but was unable to make it work with our directive that uses a mix of chips and autocomplete. It might be in our end though, as I also noticed that this also happens in the a normal input field with autocomplete but also in the demos right now so this should probably have some attention before 0.11 is out.

Any news in your end @topherfangio ?


By testing I mean I used your branch to see how that changed things.


Ok, thank you very much for your patch. I am going to go ahead and accept it. I'll do another build shortly


Just fyi I think the seqdoop version of htsjdk is old, the up to date is http://mvnrepository.com/artifact/com.github.samtools/htsjdk/1.129


Ох уж эти стандарты табуляции.


Missed marking this synchronized. Added. But you are connect. Need to make copy of the objects. I am planning to address this in another pull request.


Ahh . . thanks.  Just wondering about that.

Nathan

> On Sep 2, 2015, at 3:30 PM, Colin Diesh <notifications@github.com> wrote:
>
> Just fyi I think the seqdoop version of htsjdk is old, the up to date is http://mvnrepository.com/artifact/com.github.samtools/htsjdk/1.129 <http://mvnrepository.com/artifact/com.github.samtools/htsjdk/1.129>
> —
> Reply to this email directly or view it on GitHub <https://github.com/GMOD/Apollo/commit/65073700b0068e13024ced0cd2917a2ff8cc7036#commitcomment-13035481>.
>


add here link for image source:
https://mega.nz/#!ng13SYSa!sRXtYGdsPkW2D3I6HLvmi6-Z68NWyjXyL9AFpP8jGiI

for compare AE and natron+glowofx


Missed quotes. And in two following cd commands.


It does succeed. See [this](https://github.com/xiph/daala/blob/master/tools/ab_compare.sh#L37-L44) where those are supposed to be optional. It should only continue if those variables are set but it shouldn't throw a failure.


could you use `ncol` instead of `dim` here?


issue in dev with this: TypeError: Cannot read property 'https' of undefined


93651760-RowPerObjectReport (JasonGlazer) - x86_64-MacOS-10.9-clang: OK (1809 of 1809 tests passed)

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


矮油，几天没看，唐神已经改用 hexo 啦？blogGenerater 是不是要告别历史舞台了？2333333


hmm container.content(xxx) as an include condition? does that work?


Won't shell processing of the "secret.toString()" have problems if the password contains a double quote character?  I would assume that will break the echo command, since the wrapping double quote will be seen as closed by the double quote embedded inside the string.


How would change this function to take in any number of years? e.g. Your boss now wants bikes under 7 years old... instead of writing a whole new method, how could this be done?


Бомбит у меня...
Откуда взялся Main2Activity. Точнее где он?


This seems a bit roundabout :/  I guess I see now why you want to tie the gc-tracking to the icinfo object rather than the ics_by_return_addr structure, but I think it'd be better if we made the tracking a bit more explicit.  So in this case, maybe we could in `finishCompilation()` call something like `trackGCReferences(std::move(ic_info))`.  Ideally that would not use the ICInfo object's lifetime to determine which ICs are live or not, but it could and the baseline jit wouldn't need to know.


There is a weirdo no-op case which work on BoltDB+PostgresSQL, and would not be accepted with this Memstore Precheck:

```    t := cayley.NewTransaction()
    t.AddQuad(cayley.Quad("E", "follow", "G", ""))
    t.RemoveQuad(cayley.Quad("E", "follow", "G", ""))
    err = database.GetStore().ApplyTransaction(t)```


Ok.


I think these aren't potential roots, since they got filtered when they were put into the list?


reack


oh, make sure you're on the `nuke-lru` branch of `snoode`, and `refactor-populateData` for `horse-react`, to test the latest.


suggest changing to:

When your module depends on other modules, set the upper version boundary in your version range; for example, `1.x` (any version of `1`, but less than `2.0.0`) or `>=1.0.0 <3.0.0` (greater than or equal to `1.0.0`, but less than `3.0.0`).


suggested changes:

Without this upper bound, users might run into compatibility issues across major version boundaries, where incompatible changes occur. It is better to be conservative and set an upper bound, and then release a newer version of your module after a major version release of the dependency. Otherwise, you could suddenly have to fix broken dependencies.


suggest:

If your module is compatible with only one major or minor version, you can use the semantic major/minor version shorthand (e.g., `1.x`). If your module is compatible with versions crossing major version boundaries, such as with stdlib, you can set your supported version range to the next unreleased major version, e.g.:


suggest:

In this example, the current version of stdlib is `4.8.0`, and version `5.0.0` is not yet released. Under the rules of semantic versioning, `5.0.0` is likely to have incompatibilities, but every version of 4.x should be compatible. We don't know yet if the module will be compatible with 5.x. So we set the upper bound of the version dependency to less than the next known incompatible release (or major version).


Editing comments above, @ferventcoder . Also, this is PR'd against an old version of the docs. I didn't know if you had a particular reason for that, but if not, I'd like you to PR this against the current version of the docs (shallowgravy branch). Thank you!


LGTM


I reverted that as discussed, but can't really figure out why the agent signals would not arrive for you.  Is that happening on every run?  If that persists, I'm guess we'll have to turn on logging on the communication channels to  narrow this down.  Let me know when  you would  find time (and are motivated) to look into this...

For your data cleanup, the change you did above may or may not help, really -- depends on the time it needs to create components, which should be significantly shorter than aprun times though...


This commit caused soft reboot problem..
http://review.cyanogenmod.org/#/c/100437/


PS.: I confirmed again that empty agents are not a problem in general...


Aww. I was noting lacewing for something I had planned. Still an amazing library. I'll make sure to add it to a section named "honorable mentions" once i get to it :)


I like the Parsing module :tada:

How could we change write a method to let our boss know about any given number of years provided, versus having to specify 2010? For instance, what if your boss says: I want bikes less than 7 years?


Does git promise the prompt will be English language "Username" even on local language environments?

For example, if I'm running Spanish language git, I think there is a chance that the git messages will be in Spanish.  Refer to [stackoverflow git locale question](https://stackoverflow.com/questions/10633564/how-does-one-change-the-language-of-the-command-line-interface-of-git) for hints about that.


As we talked about I don't think this is tracking the actual set of pointers embedded into the instructions :/  I think the easy approach for now is to just keep a separate set, and put pointers into it during calls to embedRelocatablePtr / embedConstantPtr.


I assumed it was safe as this is what we already do for the ssh passphrase thing?

Maybe we need a way to quote this here? I think the only real solution would be some sort of call to a java library that safely quotes the string?

We'll need the same thing in windows..

However, I think we already have this issue inside of createUnixSshAskpass as well, so as no one has seriously complained.... what are your thoughts?

I'm not sure the best way to solve this...


Done.


Rad! :smiley:

How could we change the `#find_bikes_less_than_5_years_old` to `num_bikes_less_than_years(years)`?


Yes, i don't know an automatic way to fix that.


Oh whoops didn't see that you changed it in the next commit.


Good idea.


1579840-GroundTemps (mmatts) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (766 of 766 tests passed)

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


rax retry tests


If snap should fail immediately in such a case then that's fine, but right now it doesn't do that, instead printing `msg: ./snap[xxx]: [: false: unexpected operator/operand` a few times throughout the execution of the program.


(not potential)


Revert


Very nice, I like it.
I'll check for existing applications; Also, don't forget to update the documentation ;)


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1291 of 1291 tests passed)

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


Sweet! Thank you. Will change it as soon as possible.


I think we can leave this as static.


I think we can kill the visiting of relocatable_syms?


Odd, are you sure it's not applied over some other modifications? Although git should sort it I think...


Do we need a new variable "vertexLoc"? It seems it is only used in the next two lines. We can directly use GLProgram::POSITION_ATTRIBUTE_LOCATION there.

Same for "normalLoc" and "texCoordLoc" below.


I'm a bit iffy about actually implementing this destructor, since there is more work that it's supposed to do.  Maybe we can leave it unimplemented, and just add this as a note to the comment (above the destructor declaration) in core/types.h?


I incorrectly coded this, it isn't based on standard input but in the first argument, so it provides "argv[1]" as what the prompt is for. According to git source, this is not a translated string. The displayed output if we do a prompt to the user will be translated, but the actual value passed to the script does not appear to be marked for translation.

I need to fix these scripts, though, because they are based on the standard input, which is not guaranteed.

I will respin this change.


Maybe these should be getAllocationFromInteriorPointer? (so that we can embed references to interior pointers)


Forgot to check my work. Accidentally wiped out the daily summary icons! :see_no_evil:


ack


FourPipeBeamAirTerminal (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1816 of 1816 tests passed)

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


Just delete the whole function.


TeamCity LabkeyTrunk :: Git postgres 9.4 [Build 489](https://teamcity.labkey.org/viewLog.html?buildId=269785&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 5, passed: 0 Build time: 00:08:41
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSMeasureStoreTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSVisualizationTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSLoginTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSSecurityTest: <no details avaliable>

```


oh and I implemented close fully, didn't realize the api stated that port and be nil and close all ports. I support that now.


Isn't `[io], ` also an optional parameter?


Hi @fpelliccioni

Can you explain your commit and how use this version please ?


i think we are using `opts` instead of `args`


Maybe we should just omit the subscripts on functor applications entirely; it seems that maybe they generate more confusion (for both author and reader) than they are worth.


`let`


This is missing a few possible values.


You can include `net/if.h` and use IF_NAMESIZE, which is covered by the POSIX standard.


Maybe remove `console.log` in production?


lol i like the secret


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1291 of 1291 tests passed)

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


Completed Order display and total cost calculations, order confirmation alert with unique id number


I fixed this but since I clobbered my local rd_tool working on integrating python3, I can't test the changes. I'll update it once I get it working again.


I did a manual edit, helps me learn things.  Reverted those changes out so.  To use git:

1)git fetch https://github.com/tracernz/TauLabs
2)git merge tracernz/TauLabs/tlfw-padding-fixup

Correct?


TeamCity LabkeyTrunk :: Git postgres 9.4 [Build 490](https://teamcity.labkey.org/viewLog.html?buildId=269787&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 5, passed: 0 Build time: 00:08:48
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSMeasureStoreTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSVisualizationTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSLoginTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSTest: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSSecurityTest: <no details avaliable>

```


Comment also needs adjusting.


Fixes #1


nit: it's SignalFx


/home/ec2-user/daala is the checkout used to do the test run. There is a separate checkout at /home/ec2-user/daalatool intended to be used for all the tools and metrics, as then you can test older versions of daala with the new tools.


Undo this formatting change - it looks like it changed spaces to tabs. CoreCLR convention is to use spaces.