ok!  so, the sprite flickering may actually make sense, now that i think about it.  and it shows on the bitbox as well (even with the v0.9 graph_frame).  it was confusing to me, because on the emulator.c (v0.9), graph_frame executes before the drawing algorithm (VGA_V_PIXELS graph_line's).  but this should maybe be reversed, to be more accurate to what the bitbox actually does, like the v0.10 graph_vsync, which is more accurate to the true bitbox behavior.

ok, so why sprite flickering happens:  when a sprite goes through another sprite vertically, i had some code which would swap their draw orders to be correct for first-on-screen-to-draw.  i expected graph_frame to execute before graph_line (which it does in emulator.c v0.9), so i thought that graph_frame would produce the correct sprite draw locations for the sprite draw algorithm in graph_line, but in fact i have to correct the sprite positions after i change them (in game_frame), so to speak.  so on the bitbox, we see sprite flickers because graph_frame (v0.9) or graph_vsync (v0.10) is using the one-frame-old sprite positions to sort the sprites, which gives some strange artifacts on screen for a split second.

at any rate, i think the solution is to sort the sprites after modifying them (in game_frame).  the alternative is to update everything (essentially doing game_frame) in the vsync callbacks, and finally sort sprites at the end, but i'm not sure how many vsync callbacks I get, or if things make sense to do it that way.

(i still have extra black pixel rows in v0.10 on the bitbox, but i'll raise that issue on the bitbox SDK.)


ok


Yes I think you are right. In early testing I am seeing that the number of writes is huge as clients write small packets. Writing a single 2GB file generated 66,000 write calls and 33,000 flushes!

So instrumenting even 1% of writes may be too much, and we should definitely treat flush as a data operation. I will make the change.


LGTM...@vhart @charleshkang , what's the reason for `index = index + 1` being better than `index +=1` again? I know y'all sent some article, I'm just looking for a brief explanation hehe.


Just a little something I did because a friend who thought 5 second expiring messages were fun, was annoying me.
I like the idea of the feature being under the user's control but before I submit a PR for general consumption, I'd like to add a "clean expired messages in this conversation" button to encourage good housekeeping.


test


Hello,

I've updated the original repository to Selenium Server 3.0.1 as well (a bit late). Would you mind to provide, next time,  a pull request with your changes in the upstream project so everyone can benefit from your updates than rather forking and have a another clone on packagist. Anyway feel free to fork and maintain your own code. :)

Thank you and have a nice day
Sven


This is the most professional way to fix a bug, you cant deal with :laughing:


There is potential out of range lookup if you have trailing space.
E.g. "aaa " will result in i equals to 3 and then you will increment it and address to 4th element, which is out string's length.


Az én házi feladatom címe:
Szólánc.
A szólánc több fórumon nagy siker, hiszen a szókincsünket gyarapíthatjuk általa.
Lényege, hogy leírunk egy szót, aztán a gép a szavunk utolsó betűjével ír egy újabb szót..... és így tovább..
Egy szó többféle ragja is megengedett, bár ennek nem sok értelme van, inkább a változatosságra érdemes törekedni.


@JackyChiu @VikramBombhi


ArrayList.contains() - the same for-loop, so no performance improvement here. HashSet is much better - little memory overhead, but better .contains() function speed unless you prove that array list is quicker with benchmark (you could use [JMH](http://openjdk.java.net/projects/code-tools/jmh/)).


Can somebody explain this change to me? This stops select multiple=checkbox from being allowed to use the required attribute to require at least one selection. If I remove this if block entirely, it behaves fine. What is the purpose for this being here?


Thanks, it makes sense. I have fixed this.


I just pushed a fix for the iPhone build. Should be ok now. I'll check the next nightly build to be sure.


wrong prefix


The following doc(s) have been deployed to the [debugd8](https://debugd8-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/debug-d8](https://debugd8-static-docs.pantheonsite.io/docs/debug-d8)


Sure, I have fixed this. Thanks~


I think u forgot that file


Corrected a typo.


@ppekrol Yes, `Newtonsoft.Json` dependency will mostly go away internally. However, we'll probably still require the client to use some sort of json to object parser, which will most often be json.net


If even at 10 sec/game it is useless according to fishtest, then it is useless everywhere....

...even don't try at 60 sec / game, it will be even worst!


preifx


prefix


great! could you release a new version and deploy it, please? @aserratorta


preifx is wrong


dbService is not a mock here, but object under test, so wrong postfix


prefix is incorrect


Not sure why you're adding a commented line


prefix is not complain with codestyle


prefix has a mistake


prefix had to be another


This program is free software: you can redistribute it and/or modify


incorrect prefix


there is a mistake in prefix


Not sure why you're not sure


prefix is wrong here


test method should start with test* or should*


brilliant, @dpawluk!

Apart from the small backdrop issue, agents liked this new version more than the old one. Focusing on clearly showing your respond and an easier way to cancel the ticket submission.

Thanks for the quick fix yesterday and looking forward to seeing the new version of it! ;)


# **_

> Játékszabály:

_**

[- [ ] - 1. A játékosok megállapodnak abban, hogy a játék egyszerű változatát játsszák-e, azaz bármilyen szót lehet alkotni, vagy valamilyen témakörbe tartozó szavakat kell mondani.
- [ ] - 2. Ha valamelyik játékos már nem tud újabb szót mondani, zálogot ad vagy kiesik a játékból.


test method must start with test* or should*


test method had to start with test* or should*


prfx


I don't see any commented line


please fix prefix


looks like prefix is wrong


First off, why ask here? This is just a repo hosting bleeding edge builds, and not the actual citra repo... Second off yes, its heavily in use. Look in src/core/arm/dynarmic for the connector.


I had a feeling that prefix could be improved here


It is showing the committed file here. but this isn't complete. I have copy pasted the complete work since R was giving us issues last time.


Guys please can we bury this commit


Please don't post comments on commits (especially years old). Open a new issue / PR.


Should the readme.md be
```getMessages($withbody = true, $standard = "UNSEEN")`` get emails in current folder`
?


that's too complex assertion. please split into two independent assertions. it will improve code readability


I had a feeling that prefix must be improved here


maybe here coworker.fullName is better, did you check if it works properly? @aserratorta


It's not a mock ,but object undert test, so no *Mock postfix please


I had a feeling that prefix had to be improved here


In general, element deletion is expensive operation as it internally leads to memory reallocation. Can you figure out solution without deletion?


pls chng prfx


I ❤ you @mikekavouras


Well, I have, since I wrote the code. :-) I wrote it to keep a MacBook at work alive – it was running OS X 10.9 and the app was working when I left work half a year ago. One caveat was that sometimes some other app launched before it, locking the GPU to discrete mode before gfxCardStatus had a chance to do its thing.

I haven't tested it on anything newer than 10.9 and if there've been OS updates to OS X 10.9 in the last 6 months I haven't tested it with them either. If my colleagues haven't reformatted it or thrown the machine in the garbage when I get back to work in a month, I can check how things are.


This software uses the Terminal Green icon <http://www.iconspedia.com/icon/terminal-green-18559.html>
 + by Madeliniz, used under the Creative Commons Attribution 3.0 Unported (CC BY 3.0) license.


Use `RE.ws` from `rivescript.regexp`, it's an already compiled `\s+` regexp. Python's regexp engine is very slow compared to other languages, so I precompile as many regexps as possible to improve performance. The `RE` class contains all the hard-coded regexps.


e


NPE because there is no sessionMock... mocking. Field sessionMock is never initialized


pls prfx


It seems your text editor included a tab character (`\t`) on these two lines. For this level of indentation you should use 8 spaces.


Thanks @UberMouse . Yup @nwoodward and a bunch of others, esp. from North America, are busy evaluating and implementing Sj at the moment. And don't forget Nga Taonga and TPK. Dan and I are thinking about how best to support/grow the community. Will discuss more at stand-up this morning. Meantime, I really appreciate you helping out. :-)


soldOut does not exist in the database.


echo example doesn't run after this.


looks like movieDaoMock isn't initialized, so NPE will be here.


Sure no worries


The following doc(s) have been deployed to the [debugd8](https://debugd8-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/debug-d8](https://debugd8-static-docs.pantheonsite.io/docs/debug-d8)


It's not a mock, but object under test, so no Mock postfix please


Prefixes are incorrect


I think that the movement speed should be 10, but the turn speed should be 15. Our serf should be agile, but not necessarily fast


Prefixes had to be changed to test* or should*


you can value-initialize dynamic char array with 0 using syntax:
```
s = new char[size]();
```


I've updated my database username too now.


I would suggest to verify that .createQuery() hasn't been called without any query
```java
verify(sessionMock, never()).createQuery(anyString())
```


Thanks, don't worry about the delay! Will start to integrate shortly.


@daniel-beck Hey, I  noticed that master is continuously failing to build and I still don't seem to have permissions when I try to publish.

```ps1
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project fortify-on-demand-uploader: Failed to deploy artifacts: Could not transfer artifact org.jenkinsci.plugins:fortify-on-demand-uploader:hpi:2.0.3 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Access denied to: https://repo.jenkins-ci.org/releases/org/jenkinsci/plugins/fortify-on-demand-uploader/2.0.3/fortify-on-demand-uploader-2.0.3.hpi, ReasonPhrase: Forbidden. -> [Help 1]
```

Is there a step I missed here?  Is there anything you guys need help with to get the master build working again?


What is this file used for?


fyi, it is also possible:
```
s3 += len(s3);
```


corected some issues with parametric values, now working and maybe looking better


ok


I just noticed that this branch commits a tarball


Just a test to see if Working Copy is working well.


@mikejolley Sometimes getting a "fresh" instance is the only way to flush internal runtime caches of a product object. Might be a good idea to allow a way to bypass the cache, perhaps add an argument/filter to control this.

Another possibility would be to return a deep copy of the cached object.

Alternatively, it might be a good idea to introduce a product method for "resetting" the state of the object, which internally re-reads all props (and could be used to clear any runtime caches, such as the `prices_array` cache of variable products).


Yeah, it's MASSIVE! 😂


no es tan claro


sigo sin entender bien


bueno, puede ser que sea un metodo


I'm really sorry for this. But after testing Webkit2 handles scrolling internally witch brakes any styling or attempts at reverting screen position.


I had to revert back as Webkit2 handles scrolling internally. This prevents any position saving and breaks GTK styling.


This commit broke the program.


Also, what about modifying object properties?

```
$a = wc_get_product( $id );
$a->prop = 5;
$b = wc_get_product( $id );
```

Wouldn't `$b->prop` equal 5 after this?


Not a perfect function name. Variable, function, class, etc should tell what it does.


Nice!


If I recall correctly, the fetch script can launch before the dispatcher is running, thus the sleep.


On ne peut malheureusement pas utiliser le logger avant que l'entité soit construite.  On pourrait changer cela mais il faudrait changer la signature du constructeur de chacune des entités.
J'ai fait un fix dans ma branche qui est présentement en PR (https://github.com/mldbai/mldb/pull/771).


```
[20:31:46]	[Step 1/1]  ---> Running in f30e4fac937f
[20:31:48]	[Step 1/1] [20:31:48] Failed to load external module babel-register
[20:31:48]	[Step 1/1] [20:31:48] Requiring external module babel-core/register
[20:31:54]	[Step 1/1] module.js:327
[20:31:54]	[Step 1/1]     throw err;
[20:31:54]	[Step 1/1]     ^
[20:31:54]	[Step 1/1]
[20:31:54]	[Step 1/1] Error: Cannot find module 'event-stream'
[20:31:54]	[Step 1/1]     at Function.Module._resolveFilename (module.js:325:15)
[20:31:54]	[Step 1/1]     at Function.Module._load (module.js:276:25)
[20:31:54]	[Step 1/1]     at Module.require (module.js:353:17)
[20:31:54]	[Step 1/1]     at require (internal/module.js:12:17)
[20:31:54]	[Step 1/1]     at Object.<anonymous> (/app/gulpfile.babel.js:5:1)
[20:31:54]	[Step 1/1]     at Module._compile (module.js:409:26)
[20:31:54]	[Step 1/1]     at loader (/app/node_modules/babel-core/node_modules/babel-register/lib/node.js:144:5)
[20:31:54]	[Step 1/1]     at Object.require.extensions.(anonymous function) [as .js] (/app/node_modules/babel-core/node_modules/babel-register/lib/node.js:154:7)
[20:31:54]	[Step 1/1]     at Module.load (module.js:343:32)
[20:31:54]	[Step 1/1]     at Function.Module._load (module.js:300:12)
[20:31:54]	[Step 1/1] The command '/bin/sh -c gulp es6' returned a non-zero code: 1
[20:31:54]	[Step 1/1]
[20:31:54]	[Step 1/1] Process exited with code 1
```


ttreyreytreytre


Umm...Nice readme I guess...


В блоке sorter элементы вложены в элементы, но в именовании классов все равно все по бэму, вложенностей нет.  Это норм?


В блоке sorter элементы вложены в элементы, но в именовании классов все равно все по бэму, вложенностей нет. Это норм?


I completely agree about the RqProduct as a base case. It would make the instances much simpler, and is very convenient when serializing hints (otherwise we'd have to use an "either" message for hints with one modulus vs more than one. However, there's a big drawback to making this change: the new version of Lol will not be able to read the RLWE challenges that we've released. One possible resolution to this is to add a special "challenge" tensor that can still read the instances we released, and which can convert to some other tensor.


Note: also contains a potential fix for #59.


Frankly, one of my goals was to try and be independant of overpass-api.de. If someday the domain crashes/is stolen/closes/…, then it will still be running perfectly.

As for the tags, I like this automated approach. I guess it's up to @drolbr to change the tags ;-)

New version is pushed


To be clear, I'm proposing that we serialize a single Zq modulus to an Rq product, rather than an Rq, which is what we do currently.


                            Streaming UDP Client
  What is it?
  -----------
 This is a Streaming UDP Client program, include Client program only. It is possible to run the test with this stand-alone client program.

  Test Environment
  ------------------
 1.  SUSE Linux Enterprise Server 11 (x86_64)  3.0.101-0.35-xen  + gcc 4.3.4
 2.  Ubuntu 14.04.5 LTS   4.4.0-31   +  gcc 4.8.4

  How to Compile
  ------------------
 1. Enter the folder "./udp_project/client/src"
 2. Run command "make".

  How to Execute
  -------------
 1. Enter the folder "./udp_project/client/bin"
 2. Run command "./udpClient -a 120.0.0.1 -p 2088 -n 1000 -s 200 "

  Udp packets should be printed out on the screen.

  Packet Sample:
  ------------
================================================
00 00 03 e7 23 09 07 f8 be d6 84 fe 63 b2 79 25
06 90 38 ff 43 76 dd a4 5f 86 67 f8 9f e1 89 38
a2 78 72 ee 43 25 c2 02 fb 46 00 5e f8 79 84 ff
09 bc fe 4c 33 db f0 92 62 57 8a 01 39 13 39 db
8b ab c9 cf d0 8b d1 cb d1 d1 2a ca 4a ae c9 53
6a c7 9f 9d a2 8f 30 04 e6 ba 05 1f ce 3e fb 59
e9 c4 28 b9 50 f9 85 21 ca af eb 14 5d b4 67 c7
7b 06 65 1e 95 95 22 7c 4f 28 9b 1d 66 96 77 50
5b 9f 09 ab 99 8e cc 63 3d b8 78 9a 6c df 62 e8
e6 c7 06 7b 5c 28 f7 ab 50 93 c9 b7 29 40 07 84
df 10 2f 78 9f fc dc dc b4 54 77 20 33 d9 08 19
a0 0e 95 fc 37 8c a7 87 1f 70 3e 49 b0 45 cd 90
56 fd 08 f5 f9 e4 d1 ad 38 48 cd 6c 21 d6 85 c1
e4 1a bd 1b a7 65 a3 c6 d5 e1 0f 86 27 dd 16 7d
da 1e 72 d3 03 43 80 3b 8c 4d a7 ad 23 2d 6f 08
47 2c 23 ee 91 c6 b5 67 a8 c4 ed cf a1 03 4c 7b
21 be 4e 24 01 ce 60 8d 1c 07 3b 3f 34 aa 47 7c
d6 6b 6a 68 31 1f cf d9 e4 bc a8 85 bf f4 01 e0
b2 4f 05 b4 1e 65 41 3a 6c 7c 79 a1 26 c1 1d fd
2c 87 65 5d a7 34 37 8b f0 df 10 af d4 11 8f 86
61 94 3a 7f f9 7c b9 66 f8 32 07 1f f3 24 1c 1f
ab 81 7d 52 b5 b4 dd a5 93 ee 54 67 ff e3 ee 60
78 28 df 71 a4 98 d7 9d cb de bc be 02 d8 de ae
59 5b 00 0e 0f de b3 a2 cc 07 0a cb ea f8 2c 62
20 0b d4 c5 a4 ab 62 6f 8a 1e 2d 8c f6 0b 3a 4f
66 3b 5d 75 19 10 18 e5 17 22 b0 01 1a dc 64 3a
e8 38 ff 8c e3 61 fb 6d 7f 28 fa 75 34 34 c4 9a
6f 21 10 88 31 28 6d 48 4a 1e 4a 64 fa ae 9e e2
e6 9e 6e c9 ff 69 37 7f 92 31 f4 c6 65 b9 60 d5
da 70 5d 0c 98 cb 54 e2 e9 9e 46 e3 4c e5 c6 32
83 34 fc 82 9e 33 01 30 64 f6 f6 c9 af 56 9e 89
c7 fc 95 5f c7 ea 42 b0 88 88 93 d5 6d 59 07 f0
8e 03 73 2c 36 74 5c 9a 6a 52 64 19 a8 02 a3 6f
fe 38 cf c5 22 11 75 ab 99 09 80 07 62 87 f7 f0
8b 6a 1c c1 df 78 5c 49 ca c0 63 73 c2 06 e2 c1
3e b1 86 61 c2 fc 0c 5c 05 8c 63 67 13 5a 58 9e
c5 74 60 a4 ed bc ed b7 7c 50 2a 3e 56 0d ff 95
be 86 f6 81 82 02 dd 87 8e 40 ee a1 9a 46 40 5f
bb a0 03 a8 5c f1 5f d8 41 8a 16 98 97 16 2d 55
9c 23 d6 1e 25 b3 a5 b3 f3 93 54 8e da 94 ed 95
34 f1 3d 90 e2 9c 68 23 26 7f bb bd 95 e8 13 31
0b e9 4f 30 9d f4 e3 90 87 38 1e 61 cc 0c f6 01
fd 33 91 df d0 fa 02 f6 79 be b4 0e a6 c7 3f b2
b0 8e e2 4d 82 c6 de 09 fe fc 6b ca 08 61 cb 05
95 5d e4 65 57 e7 5b d0 a5 0f de 4b d6 1d fd 87
ab e0 d4 2d a6 b2 36 a4 af a1 6e b7 03 3a bd 98
97 a1 fd ee 88 58 be 2d 68 9c 79 3e b9 76 c5 64
56 9a 91 fc 4c c7 a0 fb 69 0f b3 6c 49 70 04 e0
11 01 ce 9a 59 8c c7 c1 28 40 00 e1 b7 c5 45 0d
5f d6 0a ac 9d aa a7 06 b9 5a 72 02 ca 76 e2 dc
77 b0 76 d1 3c 3d 92 64 7e 92 45 35 58 8a 42 b7
60 4c 63 fe f7 0b 04 b0 65 77 b3 30 ed 95 0c 65
46 82 36 82 bf c8 e7 3d 5b 2c 72 b3 b7 b5 6a 17
01 ce 15 f8 d9 1a a9 3e 91 5c 6e 7e f1 7a e3 37
fc 19 ba bc e2 a1 f9 3d cd 6c f0 84 21 5a 9c 22
28 b1 1b 01 cb c4 40 5c 20 ae db 11 29 be 49 25
d8 03 e1 ba a4 db f7 71 47 e7 f6 68 41 92 8a 6a
43 a5 6b 0f 69 ab 6b 89 5a 46 9b 83 05 e4 a8 dd
e7 8a 97 8b 65 8e fc ac 75 f2 14 b6 84 9e 20 c8
44 8c d7 ad 37 42 37 91 89 d2 14 8e b6 bd 6b 9d
47 02 28 ac 90 24 58 05 17 6c bb 9b 0a dc 63 4e
68 3a fc 9f 7d 33 31 06 05 45 94 bb 02 ff 58 49
01 80 f5 91 a4 4d 96 bb b9 51 57 c4 2d ba 12 95
f5 0e 35 72 41 66 78 46 ab 0c 01 ae 0b 59 f7 0c
d9 ed 9d 7e 3a 33 39 f4 84 90 b8 b2 4b ca 47 40
d9 7c b2 1a e2 2a 61 8e 36 62 3c 41 bc 33 4d 95
20 ea 13 5b 1d 4d 4f a1 dd 07 53 28 d1 9b 68 aa
17 1a c5 fa 44 26 88 7a 88 c4 bb 44 f7 08 da 18
f2 ed 73 0f 3a c2 b1 18 c9 04 40 9a 9f a9 45 b7
c3 0a b1 08 30 39 82 b8 fd 3e fd f4 46 d7 0c 39
c4 7f 48 ff 41 f9 17 0a fe 57 a5 9d 00 ea 54 c4
f4 05 cc 24 3e 4e dc 3b 8c d9 30 d3 b0 3c 0c 75
bc 54 74 fd 4e 8b 08 4c e2 ad e9 e3 97 3e a7 8b
43 73 af 82 c1 8b bd 4e 65 ed 21 15 2a 2d 8a e6
81 fe e3 cf 89 eb 1b 6c 98 05 4f 2f 43 f6 ba 86
69 69 08 2a f5 c6 78 5a b3 99 6f dd c6 fa c3 48
f8 a7 17 82 92 33 ee 2b 38 3d 5a 7b 33 15 01 9c
7e 0a c6 73 d0 3f cd 83 d8 3d 61 9f 37 24 e7 2f
cb fe b1 5e 31 9f 89 69 dc e3 e4 0f f8 e6 ab 77
f0 72 ea c0 b1 b8 43 89 f5 a4 28 2c c9 0f 5b 94
0e 0d f2 3f ac 7b a9 89 5f 8d 98 57 73 44 ce 63
b6 b9 23 67 71 67 f0 66 0b 19 92 d4 28 ed 69 36
fa 5b 76 a7
================================================


Oh wow, happy to see that a three-year-old gist is still useful! Thanks for the mention, it made my day. 😃


This fix is not in production yet? I have version 1.1.1 and the problem persist.


Thanks. Indeed, we noticed this yesterday afternoon, and I fixed it on the right side


Lookin' good! The `wp_kses()` stuff shouldn't be necessary here since these are static strings and not user input.


Если представить ситуацию, когда продуктам понадобится обертка, то какой ей дать класс, чтобы не сломать бэм? Может есть какие-то "правила" для именования блоков/элементов, которые отвечают за сетку?


What's your Minecraft account? XDDDDDD
-- RK


And I would add that your change comes down to an increase of the midgame and endgame values of each pawn by (+8,+16): you can achieve that in master by changing exactly two constants in types.h

````
PawnValueMg   = 196,   PawnValueEg   = 264,
````


Nice


um you okkkkkkaaaaayyyyY?yY?Y?yyy/Y/Y??Y


Not sure about this one because release script selectively copies doc to the docker-notebook directory.


It might be better to have this configurable and maybe even ask it in the setup flow. `How much would you like to fund your connector account with? (100)` @vhpoet @sharafian


:hand: :smile: :blue_heart:


I work on a special version base on the .sh of this commit, it generates a auto chagelog.md file to use in github, you can make it every time the ROM project version is change
https://github.com/bhb27/android_vendor_crdroid/commit/86c64d0d97772b8f772bcabfec17015d629dd143
result
https://github.com/bhb27/android_vendor_crdroid/blob/change_temp/Changelog.md

there is one special for a specific device, does the same but you add device tree and it separate it commit device or source and gives a nice look
https://github.com/bhb27/scripts/blob/master/etc/changelog.sh
result
https://github.com/bhb27/scripts/blob/master/etc/changelogs/Changelog_RR_N.md


[https://www.youtube.com/watch?v=TAryFIuRxmQ](slow clap)


The Chrome extension I'm using to prettify JSON didn't recognize the response as JSON without the header.


```

# copy doc over
run: workdir='..'
    rm -rf development/docker-notebook/documentation \
        development/docker-notebook/tutorials \
        development/docker-notebook/examples
    # copy only ipynb and .sos files to docker
    rsync -av --prune-empty-dirs --include "*/" --exclude ".ipynb_checkpoints" \
        --include "*.ipynb" --include "*.sos" --exclude "*" \
        doc/documentation doc/tutorials doc/examples development/docker-notebook
```

although we should also copy media over.


//fix


Thanks a lot, that's awesome how reactive your are!


Consider approach using relation between char and int.
You can create array to store symbol repetitions using chars as indexes and number of repetitions as values.
E.g.
```
int symbols[sizeof(char)] = ...;
...
char* s = ...;
for (int i=0; i<size; ++i)
{
    symbols[s[i]] += 1;
    ...
}
...

for (int i=0; i<ARRAY_SIZE(symbols); ++i)
{
    char c = i;
    cout << c << ": " << symbols[i] << endl;
    ...
}
```


Also need to add ExplodingTeeth.o to the end of lines 39 and 42


@danielcardeenas  To support both python 2 and 3, it's always recommended to use logging instead of print, but for your own purpose, you use print to test variables etc


It builds, but it doesn't exactly work


I'll buy you a new pair of glasses for Christmas


Something like that?

![image](https://cloud.githubusercontent.com/assets/1616141/21027553/44a4f3aa-bd5f-11e6-9fd4-1e2e8c058c4d.png)


Thanks for spoofing the gift I'm giving to zayme...


Hmm... I'm not sure I understand how this works. It seems there are some implicit things happening in some of the steps. You might have to walk me through some of this.


Still working to this function


https://github.com/inverse-inc/packetfence/blob/devel/lib/pf/Switch/AeroHIVE.pm#L256

Like said, nothing wrong...


git history is like bôbbee, it never lies

https://github.com/inverse-inc/packetfence/commit/86f2ab2f57ab1f4efa4e31239ae3732cea55c1d5


I did NOT! That's what you're getting for Zayme:

![image](https://cloud.githubusercontent.com/assets/1616141/21027626/aa2ac27c-bd5f-11e6-89b7-ce8de3a5ddf9.png)


Thanks for spoofing the gift I AM giving to Zayme...


I'd probably want to put the <name> <compute allowed> and <renewal strategy> as parameters (maybe as a table?) for the  'command is fired' step.


I think you will still need to build it yourself, and it looks like other people have seen issues though so no guarantees it'll work properly. I kind of gave up trying to work on this given the lack of activity on this project and the fact that there is no automated testing which makes it hard to make safe changes.


Can you add documentation on how to make this plugin usable via the index.php?  Or shoot it over to me and I'll get working on it.

Thanks.


If you know array size by compile time, it is preferred to create arrays on stack => memory will be freed automatically as soon as the variable goes out of scope.


Это вполне можно заменить методом сеттером: `attr_writer :manufacturer`. Да, название переменной экземпляра изменится, но это окей.


I did NOT! That's what you're giving to Zayme:

![image](https://cloud.githubusercontent.com/assets/1616141/21027690/0291917a-bd60-11e6-9261-39bbbb40c58e.png)


If this works, its def nicer to maintain.


I'd want to add <old name> as the name of the allocation source you're creating somehow, instead of relying on implicitly.


This is probably unused import, isn't it?


LGTM


consider calculating index using modulus operation:
```
s2[i] = call_number[(j+5)%size_shifr];
```


bigxie committed with luk1337 on Feb 6, 2013


Good idea to use const specifiers!


That should not be in public template. Otherwise after each 'bnf to flex' user have to remove that line to fix lexer compilation


You're right, this introduces bug the loop actually.


The changes in stm32f4xx.c fix region conflicts


Thanks a lot for the details. I'll check it out and report an issue if I
found one.

On Thu, Dec 8, 2016, 22:04 Connor Dunn <notifications@github.com> wrote:

> I think you will still need to build it yourself, and it looks like other
> people have seen issues though so no guarantees it'll work properly. I kind
> of gave up trying to work on this given the lack of activity on this
> project and the fact that there is no automated testing which makes it hard
> to make safe changes.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/ariya/phantomjs/commit/7d7e5f345b646ef18d23138781ae94197335b342#commitcomment-20125506>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ANG9ux5TCJAUqJtAjIVchXC6pJ9zZ_pVks5rGHDSgaJpZM4Jb7Ex>
> .
>
--
Eddy Ntambwe


no. sry


Yeah, I do know now how did that exactly happen. I did git commit --amend in wrong repository lmao.


Sorry, I didn't know that I changed this locally. Never pushed from here to online_monitor development.


@rimsha1 , make sure to check out the code I posted in the Issues (https://github.com/waldronlab/HMP16SData/issues/1)


Don't really need an Outline & Examples if you only have one example.


Also modified Genom1Test.cpp but it doesn't look like modified here.


Corrigé !


Стоит использовать итератор `select`.


Какой объект поезда будет найден если существует 2 поезда разных типов с одинаковым номером?


use macroses only as a last resort (if you can't achieve the same with functions)
However, if you use make them reusable. Here, macros heavily depends on context (name `s` and `i`). If used in another context (even in the same function) it can fail. You could have used param `#define znak(c) (s[c] ==....)`
But anyway, here it would be better to replace it with function.


why does Qt code needs to know anything about struct _opl3_channel ?
it should be a opaque struct to Qt code.
only nukedop3.c needs to knows the details of struct _opl3_channel


This step should probably have some text in addition to parameters - otherwise it'll be confused with any other step with just three parameters. And it should probably be parameters to the 'command is fired' step. Something like:

```cucumber
When create_allocation_source command is fired
| name                    | compute_allowed | renewal_strategy |
| DefaultAllocationSource | 250             | default          |
```


I believe we dont need this, it is not used in class


Except for some style comments this is very good, perfect implementation. 👏


Related:
http://support.largoproject.org/helpdesk/tickets/373

https://github.com/INN/umbrella-voiceofoc/commit/db80861efb90da404538b4d04c496c657e77a4ef#diff-05c420ac223887d61c7025ad1bf66aca


```cucumber
Given an allocation source with name 'default'
```


It's good that you did these modifications in-place: avoided creating new result string.


I don't necessarily know the different speeds, but it should be relatively slow
For the king, when he upgrades he should have a speed upgrade


Обычно если название модуля или класса состоит из двух частей, файл именуют через `_`: `instance_counter.rb`.


```cucumber
When change_renewal_strategy command is fired
| name     |
| workshop |
```


Можно сразу вызывать `include`.


Этот метод нужно сделать приватным.


this fixed #56


I have created ActivityTrackerController which can be used a parent class of all controllers. It contains method getLoggedUser() which does the same job - returns DTO of logged User. I think it is good idea to user super class, so we dont have to duplicate the same code :)


Whatever I did was temporary anyways, good job :)


Please see related comment below https://github.com/MartinStyk/pa165-activity-tracker/commit/174d67e34144a20420ec4a87ca4c13d253400a08#commitcomment-20125736.
Method getLoggedUser also sets model attribute "loggedUser" to DTO of currently logged user, so this is not neccessary 👍


jajajaja testing


I was thinking of editing that part, I noticed on genisys that it was changed lol


You can find this in super class ActivityTrackerController. If you agree, we can user superclass method and avoid code duplication


Does FGES also stand for Fast Greedy Search?


Especially from what happened when I tested, eh


My code was giving null pointer error at  rootView.addView(wordView); because of a mistake i made in NumbersActivity.xml file. Read logcat and you will know where things went wrong.


Just a note, this broke a lot of stuff for the thousands of tablets we have logging into our copy of Gogs/Gitea. Something like this should really be for a new API version, otherwise thousands of people who use this software daily can't log in. When API specs change, we need to make a new version. :-)


Should the type be `boolean` with default `false`?


Este cambio tambien deberia hacerse en la linea [194](https://github.com/dansanti/l10n_cl_libro_compra_venta/blob/c582aa6925c7b831d7f9cb317da06b2f3f5a80ee/models/consumo_folios.py#L194)


Updated the checkboxes for the cartridges to make the first select/deselect all button press work properly.


yes i did


There is probably copy paste error - date instead of weight


yes


hello bro


CSC 171 - Homework Assignment 15/README.txt.txt

Testing adding a comment to a file.


Look at ActivityTrackerExceptionHandler class. It handles NonExistingEntityException, so we don't have to check it here :)


thank you


@JC5 the date is wrong ;-)


email has unique constrain which can not be defined in DTO class. I have created custom validator, see package cz.muni.fi.pa165.tracker.spring.mvc.validator. It would be great to add something similar here too


Because this, my bank editor failed to build after I applied it.
Here is a header where that happend (compiler gave me error that invalid character at "[", I.e. declared type and array brackets, but missing member name).
https://github.com/Wohlstand/OPL3BankEditor/blob/master/src/opl/generator.h

Preprocessor just applied "slots" macro and resulted code was:
```cpp
 struct _opl3_channel
 {
    opl3_slot *[2]; //         <<------------------seems very weird, isn't it?
     opl3_channel *pair;
//...
```

More about purpose of "slots" macro (I hope you already know this, but let someone who don't know this read text below):

Qt has empty macro
```cpp
#define slots
```
which usually used as mark of section to declare "slot" functions, I.e. those functions are known by meta-object processor which is able to call those functions, and also those functions are can be called from JavaScript code (for example, if you will bind your class into QJsEngine):
```cpp
class XXX{
    Q_OBJECT
    public:
        XXX(Object parent=0) : QObject(parent) {}

    //....
    public slots:
         void eat(Food *food) { /* ... */ }
         void drop(Garbage *gutgarbage) { /* ... */ }
         void fart() {}
    signals:
         void feelingPain(PainReason *reason);
}
```
By compiler those macros are nothing. But there are important for QMake and MOC utilities in Qt set. MOC parses those files and generates extra CPPs which are contains implementations of meta-object processors (bodies for "signals" functions, entry in hash table with text function name, text name of class (parent or child), ability to do thread-safe function calls (only slot functions are can be called by this thing), provide proxy for JavaScript engine to call slot functions and access members, etc. ).


import this to game and call savedata.save or savedata.load to save and load candidate names


A comment.


You have nested loop started each time you find space. Not very efficient as leads to quadratic complexity.
Can you figure out solution without nested loop?


Somebody has a recent fork on Spigot that added entity-locking, such as armor stands, but Hidendra specifically asked them to mark it as an unofficial build.

I know for sure that iron double doors were right-clickable in 1.8 (tested it last night with an old server backup), plus I seem to remember a couple other plugins having double-interact issues when 1.9 came out, so I'm pretty sure this results from the Bukkit/Craftbukkit changes that resulted from the off hand being added to Vanilla.


Hi,

The main problem is, as @dgtlmoon says, that you're outputting ASCII rather than binary.

Each descriptor is 512 bits. These bits stand alone; they _do not represent integers_. Therefore you don't want to print them with `fprintf %u`, because that interprets the bits as unsigned integer values.

If you want to view the bits for debugging purposes, @dgtlmoon has the right idea:

```
#include <bitset>
...
for (int i = 0; i < 8; ++i) std::cout << std::bitset<64>(descriptor[i]) << std::endl;
```

If you want to output some descriptors to a file, make sure to **open the file for binary output:**

```
std::ofstream os("descs.bin", std::ios::binary);
os.write(reinterpret_cast<char*>(desc), num_descs * 512/8);
os.close();
```

A few notes for @dgtlmoon. `ofstream` implies `std::ios::out` and `ifstream` implies `std::ios::in` so those flags are only required if it's just an `fstream`. `reinterpret_cast<char*>()` is preferred over C-style `(char*)()`. Using `fwrite `is actually a lot faster than the C++ `iostream`s, because of their inefficient implementations, mainly, but also the extra work they do with encoding and localization support. If you tweak the buffers enough, and in particular if you do this...

`std::ios::sync_with_stdio(false);`

... before you start, you can get some reasonable fraction of the C performance, but streams still lose pretty badly. **By like an order of magnitude**. My favorite question on stackoverflow is, "Does the C++ standard mandate poor performance for iostreams, or am I just dealing with a poor implementation?"

The answer is basically... uhhh yeah. Yep. Both.

If you absolutely need IO performance, use `fwrite`. Try different buffer sizes and call it in a loop. Sometimes is faster to write 512kb or 2MB sections than letting it do its own buffering. Depends on SSD or HDD, of course. If you need even more performance, use OS-specific file open and close, i.e. `CreateFile `on Windows.


Test comment on the code


Must use double quotes to echo variables inside of strings, or else concatenate variables


lol


It doesn't render? Or it renders nothing? Haha.


Does this fix dyncom flamer too?


ff


Yikes; craziness!


Writing code again :o


Is there anywhere better to discuss this kind of stuffs? Yeah noticed the #include <dynarmic/dynarmic.h> line after asking, was kinda puzzled before but after reading over the sourcecode for about 1 hour I now have a WAY better idea on how everything integrates and works. Thanks for the answer.


@EvanHerman Actually you can use `/* global ajaxurl, gem_notice */`


I think it should stand for fast greedy equivalence search.

Kong

On Thu, Dec 8, 2016 at 16:23 Zhou (Joe) Yuan <notifications@github.com>
wrote:

> Does FGES also stand for Fast Greedy Search?
>
>
>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/bd2kccd/bd2kccd.github.io/commit/cdb007c3c99a78d2e98d3e02491d945b9410587a#commitcomment-20125785>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AEb82uUAm3pQa2khhvRPHvHhkYZ8dfHJks5rGHVMgaJpZM4LITOo>
> .
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


Thanks for catching this. I won't be able to do this myself as I am on the road, but a pull request from you would be useful.


I hope we are close to ALPHA GSE 2.0! I've been watching nonstop the last 48 hours.


consider making it more generic:
```
char* res=new char[strlen(str1) + strlen(str2) + 1];
```


I just checked and the change were applied ! the mentioned changes were all successfully saved 😄
There's just one small oversight I'll fix right now and progress in translation.


looks you dont use bash


add at https://github.com/MetaModels/attribute_translatedurl/pull/8
thx!


Rule of thumb: if there is `new` in you program, there should be `delete` somewhere!
Here, you pass ownership of the pointer to a caller (`main` function), so owner is responsible for deleting.


Sure thing, glad to contribute back in someway!

From: Matthew Joss <notifications@github.com<mailto:notifications@github.com>>
Reply-To: SCILHS/i2p-transform <reply@reply.github.com<mailto:reply@reply.github.com>>
Date: Thursday, December 8, 2016 at 2:39 PM
To: SCILHS/i2p-transform <i2p-transform@noreply.github.com<mailto:i2p-transform@noreply.github.com>>
Cc: Michael Prittie <mprittie@kumc.edu<mailto:mprittie@kumc.edu>>, Comment <comment@noreply.github.com<mailto:comment@noreply.github.com>>
Subject: Re: [SCILHS/i2p-transform] fixed prescribing githun issue: now the left joins use instance_num instead of modifier_cd. (58f138d)

Thanks. Indeed, we noticed this yesterday afternoon, and I fixed it on the right side

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/SCILHS/i2p-transform/commit/58f138dabe46a485b26dacf51d9980a65d0a9cb5#commitcomment-20125193>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALikoHcHSBpYKLFQDOtFULxB5D2Sf6xRks5rGGsegaJpZM4LHHGJ>.


YES .. it was my fault .. sorry


The following doc(s) have been deployed to the [debugd8](https://debugd8-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/debug-d8](https://debugd8-static-docs.pantheonsite.io/docs/debug-d8)


Там я случайно много лишних дублируиющихся файлов залил. Поэтому второй
перезаливкой их удалил.

2016-12-06 15:46 GMT+03:00 Anna Pirova <notifications@github.com>:

> Дмитрий, Вы, пока заливали, удалили файлы. Так и надо?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Kosorukov-Di/list/commit/2bec8d6dbeecef05de79dd53fa1b1186034638e0#commitcomment-20086957>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AVfxkFHNYjBAR8YcM4mmZMb0s7Lc6xidks5rFVk6gaJpZM4LFXrc>
> .
>


Nice and lol i actually worked on this a few week(s) ago.

https://github.com/PocketEssential/UltraFaction


The wire map should now be correct with my latest commit.


Change this selector to: `$('.color-button')` and test it. The class in the `index.html` is color-button not just button.


Pas de soucis.


This is the type of PR I like to see 👍


Once you get the button click working above, you will find a few bugs in this line too. Change it to: `var color = $( this ).attr( "data-color" );`. The difference here are the 'var' keyword, a dash as opposed to a dot, and the attribute is a string.


@sgress454 This looks to be a copy/paste error


See #131 the first alpha is attached there


This is correct and is actually very close to real world code. But for the purpose of academic interest, can you propose similar solution (in terms of memory and space complexity) without stl contatiners? Pseudo code is sufficient.


I am looking at it right now.

Thank you.

On Thu, Dec 8, 2016 at 4:12 PM, Levi Waldron <notifications@github.com>
wrote:

> @rimsha1 <https://github.com/rimsha1> , make sure to check out the code I
> posted in the Issues (#1
> <https://github.com/waldronlab/HMP16SData/issues/1>)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/waldronlab/HMP16SData/commit/4f36b132fbc7cd68e9b61cbfb1945e826688df75#commitcomment-20125622>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AVDwH3P7VdnVmV2lHUNDcH3Qk2ty3fPDks5rGHLagaJpZM4K95Iq>
> .
>


`delete` is missing.
Alternative solution: once you strictly limited size of the string to encode, you automatically limited the size of encrypted string. As such you can create this string in `main` and pass by ref.


delete/rename files with *.ihex


this checks if the value is even, not the index.
the task said to get "every second element" from the list.


I guess me and @dwlfrth are all mixed up in our gifts... well all Zayme's gifts are on github now

Thanks @extrafu...


NICE!

We should update the default ride chart to plot this !


This is the only unbraced variable AFAICT (re: https://github.com/kvz/bash3boilerplate/issues/44#issuecomment-229866052)


I have fixed all mentioned points in 42d88a7ee3f343e5e28751c022bc66426f9a3c39


@sgress454 re: cliArgs - this test util was intended to be for `sails lift` -- so i'd rather not have it test `node app` or other stuff.  Looks like it's only being used this place at one point in the code though, so easy to change.

Also, if we're adding `envVars` (which I think is a good idea), then we've just got to add them to the comments above as well.


Consider passing by ref to avoid unneeded copying.


this test fails, the function to test is case sensitive


The "which prefix do I use?" check only has to be done once per statsd backend process. So we can actually memoize the join character and then just join on that every time. In fact we could just return a method to use for computing the metric name, and in the case metric prefix is blank we do a passthrough, and otherwise we do joining.


In general, element deletion is expensive operation as it internally reallocates memory. Can you figure out solution without deletion?


looks good - readme could use an image. why not?
![img_0210](https://cloud.githubusercontent.com/assets/289994/21029717/0e99be76-bd69-11e6-93e1-ba37f8fde0dd.PNG)
commit to master.


why 0? it seems like now we can launch a rocket that needs 9 fuel even if we only have 1?


One thought on the time signature export:  Do you consider pickup beats?  The only way to properly do them would be to add a rest at the start of the MIDI file for the missing part of the measure.  Or maybe to insert a second time signature meta message at the start of the first full measure to reset the placement of the barlines.  Otherwise the inferred barlines in the MIDI file will be off by the duration of the pickup measure.

Another possibility which is more of a hack would be to give a temporary time signature for the pickup measure.  This would place the barlines correctly, but it would insert a fake time signature for the pickup measure.

Most of the Bach chorales have this problem:

http://verovio.humdrum.org/?file=chorales

A random sample (type alt-M to see the MEI data in the editor):

http://verovio.humdrum.org/?file=chorales/chor160.krn

MEI data

```xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://music-encoding.org/schema/3.0.0/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://music-encoding.org/schema/3.0.0/mei-all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei" meiversion="3.0.0">
    <meiHead>
        <fileDesc>
            <titleStmt>
                <title xml:lang="de" type="main">Gelobet seist du, Jesu Christ</title>
                <respStmt>
                    <persName role="Composer">Bach, Johann Sebastian</persName>
                    <persName role="digital editor">Craig Stuart Sapp</persName>
                </respStmt>
            </titleStmt>
            <pubStmt>
                <date>2016-12-08 14:07:06</date>
            </pubStmt>
        </fileDesc>
        <encodingDesc>
            <projectDesc>

Transcoded from Humdrum with Verovio version 0.9.13-dev-bf3f7d9

            </projectDesc>
        </encodingDesc>
        <extMeta>
            <frames xmlns:humxml="http://www.humdrum.org/ns/humxml">
                <metaFrame n="0" token="!!!COM: Bach, Johann Sebastian" xml:id="loc0">
                    <frameInfo>
                        <startTime float="0" />
                        <frameType>reference</frameType>
                        <referenceKey>COM</referenceKey>
                        <referenceValue>Bach, Johann Sebastian</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="1" token="!!!CDT: 1685/02/21/-1750/07/28/" xml:id="loc1">
                    <frameInfo>
                        <startTime float="0" />
                        <frameType>reference</frameType>
                        <referenceKey>CDT</referenceKey>
                        <referenceValue>1685/02/21/-1750/07/28/</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="2" token="!!!OTL@@DE: Gelobet seist du, Jesu Christ" xml:id="loc2">
                    <frameInfo>
                        <startTime float="0" />
                        <frameType>reference</frameType>
                        <referenceKey language="DE" primary="true">OTL</referenceKey>
                        <referenceValue>Gelobet seist du, Jesu Christ</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="3" token="!!!SCT: BWV 64/2" xml:id="loc3">
                    <frameInfo>
                        <startTime float="0" />
                        <frameType>reference</frameType>
                        <referenceKey>SCT</referenceKey>
                        <referenceValue>BWV 64/2</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="4" token="!!!PC#: 160" xml:id="loc4">
                    <frameInfo>
                        <startTime float="0" />
                        <frameType>reference</frameType>
                        <referenceKey>PC#</referenceKey>
                        <referenceValue>160</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="5" token="!!!AGN: chorale" xml:id="loc5">
                    <frameInfo>
                        <startTime float="0" />
                        <frameType>reference</frameType>
                        <referenceKey>AGN</referenceKey>
                        <referenceValue>chorale</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="87" token="!!!YOR1: 371 vierstimmige Choralges&auml;nge von Johann Sebastian Bach, " xml:id="loc87">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>YOR1</referenceKey>
                        <referenceValue>371 vierstimmige Choralges&auml;nge von Johann Sebastian Bach,</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="88" token="!!!YOR2: 4th ed. by Alfred D&ouml;rffel (Leipzig: Breitkopf und H&auml;rtel, " xml:id="loc88">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>YOR2</referenceKey>
                        <referenceValue>4th ed. by Alfred D&ouml;rffel (Leipzig: Breitkopf und H&auml;rtel,</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="89" token="!!!YOR2: c.1875). 178 pp. Plate "V.A.10".  reprint: J.S. Bach, 371 Four-Part " xml:id="loc89">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>YOR2</referenceKey>
                        <referenceValue>c.1875). 178 pp. Plate "V.A.10".  reprint: J.S. Bach, 371 Four-Part</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="90" token="!!!YOR4: Chorales (New York: Associated Music Publishers, Inc., c.1940)." xml:id="loc90">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>YOR4</referenceKey>
                        <referenceValue>Chorales (New York: Associated Music Publishers, Inc., c.1940).</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="91" token="!!!SMS: B&H, 4th ed, Alfred D&ouml;rffel, c.1875, plate V.A.10" xml:id="loc91">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>SMS</referenceKey>
                        <referenceValue>B&H, 4th ed, Alfred D&ouml;rffel, c.1875, plate V.A.10</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="92" token="!!!EED:  Craig Stuart Sapp" xml:id="loc92">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>EED</referenceKey>
                        <referenceValue>Craig Stuart Sapp</referenceValue>
                    </frameInfo>
                </metaFrame>
                <metaFrame n="93" token="!!!EEV:  2009/05/22" xml:id="loc93">
                    <frameInfo>
                        <startTime float="41" />
                        <frameType>reference</frameType>
                        <referenceKey>EEV</referenceKey>
                        <referenceValue>2009/05/22</referenceValue>
                    </frameInfo>
                </metaFrame>
            </frames>
        </extMeta>
    </meiHead>
    <music>

            <mdiv>
                <score>
                    <scoreDef xml:id="scoredef-0000000406932377" midi.bpm="100">
                        <staffGrp xml:id="m-0000001233909103" symbol="bracket">
                            <staffDef xml:id="staffdef-0000001610950734" clef.shape="G" clef.line="2" key.sig="0" meter.count="4" meter.unit="4" meter.sym="common" n="1" label="Soprano" lines="5" />
                            <staffDef xml:id="staffdef-0000000521538838" clef.shape="G" clef.line="2" key.sig="0" meter.count="4" meter.unit="4" meter.sym="common" n="2" label="Alto" lines="5" />
                            <staffDef xml:id="staffdef-0000000919086697" clef.shape="G" clef.line="2" clef.dis="8" clef.dis.place="below" key.sig="0" meter.count="4" meter.unit="4" meter.sym="common" n="3" label="Tenor" lines="5" />
                            <staffDef xml:id="staffdef-0000000655610890" clef.shape="F" clef.line="4" key.sig="0" meter.count="4" meter.unit="4" meter.sym="common" n="4" label="Bass" lines="5" />
                        </staffGrp>
                    </scoreDef>

                        <app xml:id="app-0000000712067455">
                            <lem xml:id="lem-0000001757404358" />
                            <rdg xml:id="rdg-0000000419148796" label="original-clef">
                                <scoreDef xml:id="scoredef-0000001588214170">
                                    <staffGrp xml:id="m-0000001047691381">
                                        <staffDef xml:id="staffdef-0000000832724458" clef.shape="C" clef.line="1" n="1" />
                                        <staffDef xml:id="staffdef-0000000973768479" clef.shape="C" clef.line="3" n="2" />
                                        <staffDef xml:id="staffdef-0000001008030925" clef.shape="C" clef.line="4" n="3" />
                                    </staffGrp>
                                </scoreDef>
                            </rdg>
                        </app>
                        <measure xml:id="measure-L7" n="0">
                            <staff xml:id="staff-0000000691250535" n="1">
                                <layer xml:id="layer-L7F4" n="1">
                                    <note xml:id="note-L18F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-0000001320493338" n="2">
                                <layer xml:id="layer-L7F3" n="1">
                                    <note xml:id="note-L18F3" dur="4" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-0000000561263914" n="3">
                                <layer xml:id="layer-L7F2" n="1">
                                    <note xml:id="note-L18F2" dur="4" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-0000000048910895" n="4">
                                <layer xml:id="layer-L7F1" n="1">
                                    <note xml:id="note-L18F1" dur="4" oct="3" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L19" n="1">
                            <staff xml:id="staff-L19F4" n="1">
                                <layer xml:id="layer-L19F4" n="1">
                                    <note xml:id="note-L20F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L21F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L22F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L23F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L19F3" n="2">
                                <layer xml:id="layer-L19F3" n="1">
                                    <note xml:id="note-L20F3" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <note xml:id="note-L21F3" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <note xml:id="note-L22F3" dur="4" oct="4" pname="f" accid.ges="n" />
                                    <note xml:id="note-L23F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L19F2" n="3">
                                <layer xml:id="layer-L19F2" n="1">
                                    <note xml:id="note-L20F2" dur="4" oct="3" pname="b" accid.ges="n" />
                                    <note xml:id="note-L21F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <note xml:id="note-L22F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <beam xml:id="beam-0000001077354656">
                                        <note xml:id="note-L23F2" dur="8" oct="4" pname="c" accid.ges="n" />
                                        <note xml:id="note-L24F2" dur="8" oct="4" pname="d" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L19F1" n="4">
                                <layer xml:id="layer-L19F1" n="1">
                                    <note xml:id="note-L20F1" dur="4" oct="3" pname="e" accid.ges="n" />
                                    <note xml:id="note-L21F1" dur="4" oct="3" pname="c" accid.ges="n" />
                                    <note xml:id="note-L22F1" dur="4" oct="3" pname="f" accid.ges="n" />
                                    <note xml:id="note-L23F1" dur="4" oct="3" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L25" n="2">
                            <staff xml:id="staff-L25F4" n="1">
                                <layer xml:id="layer-L25F4" n="1">
                                    <note xml:id="note-L26F4" dur="4" oct="5" pname="c" accid.ges="n" />
                                    <note xml:id="note-L27F4" dur="4" oct="5" pname="d" accid.ges="n" />
                                    <note xml:id="note-L28F4" dur="2" fermata="above" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L25F3" n="2">
                                <layer xml:id="layer-L25F3" n="1">
                                    <note xml:id="note-L26F3" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L27F3" dur="4" oct="4" pname="b" accid.ges="n" />
                                    <note xml:id="note-L28F3" dur="2" fermata="above" oct="4" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L25F2" n="3">
                                <layer xml:id="layer-L25F2" n="1">
                                    <note xml:id="note-L26F2" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <note xml:id="note-L27F2" dur="4" oct="4" pname="f" accid.ges="n" />
                                    <note xml:id="note-L28F2" dur="2" fermata="above" oct="4" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L25F1" n="4">
                                <layer xml:id="layer-L25F1" n="1">
                                    <note xml:id="note-L26F1" dur="4" oct="3" pname="a" accid.ges="n" />
                                    <note xml:id="note-L27F1" dur="4" accid="s" oct="3" pname="g" />
                                    <note xml:id="note-L28F1" dur="2" fermata="above" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L29" n="3">
                            <staff xml:id="staff-L29F4" n="1">
                                <layer xml:id="layer-L29F4" n="1">
                                    <note xml:id="note-L30F4" dur="4" oct="4" pname="b" accid.ges="n" />
                                    <note xml:id="note-L31F4" dur="4" oct="5" pname="d" accid.ges="n" />
                                    <note xml:id="note-L32F4" dur="4" oct="5" pname="e" accid.ges="n" />
                                    <note xml:id="note-L34F4" dur="4" oct="5" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L29F3" n="2">
                                <layer xml:id="layer-L29F3" n="1">
                                    <note xml:id="note-L30F3" dur="4" oct="4" pname="g" accid.ges="n">
                                        <accid xml:id="accid-0000001427501844" accid="n" func="caution" />
                                    </note>
                                    <note xml:id="note-L31F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L32F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L34F3" dur="4" accid="s" oct="4" pname="f" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L29F2" n="3">
                                <layer xml:id="layer-L29F2" n="1">
                                    <note xml:id="note-L30F2" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <note xml:id="note-L31F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                    <beam xml:id="beam-0000001350163308">
                                        <note xml:id="note-L32F2" dur="8" oct="4" pname="c" accid.ges="n" />
                                        <note xml:id="note-L33F2" dur="8" oct="3" pname="b" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L34F2" dur="4" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L29F1" n="4">
                                <layer xml:id="layer-L29F1" n="1">
                                    <note xml:id="note-L30F1" dur="4" oct="3" pname="e" accid.ges="n" />
                                    <note xml:id="note-L31F1" dur="4" oct="2" pname="b" accid.ges="n" />
                                    <note xml:id="note-L32F1" dur="4" oct="3" pname="c" accid.ges="n" />
                                    <note xml:id="note-L34F1" dur="4" oct="3" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L35" n="4">
                            <staff xml:id="staff-L35F4" n="1">
                                <layer xml:id="layer-L35F4" n="1">
                                    <note xml:id="note-L36F4" dur="4" oct="4" pname="b" accid.ges="n" />
                                    <note xml:id="note-L38F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L39F4" dur="4" fermata="above" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L40F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L35F3" n="2">
                                <layer xml:id="layer-L35F3" n="1">
                                    <note xml:id="note-L36F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L38F3" dur="4" accid="s" oct="4" pname="f" />
                                    <note xml:id="note-L39F3" dur="4" fermata="above" oct="4" pname="d" accid.ges="n" />
                                    <note xml:id="note-L40F3" dur="4" oct="4" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L35F2" n="3">
                                <layer xml:id="layer-L35F2" n="1">
                                    <beam xml:id="beam-0000001460148849">
                                        <note xml:id="note-L36F2" dur="8" oct="3" pname="b" accid.ges="n" />
                                        <note xml:id="note-L37F2" dur="8" oct="4" pname="c" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L38F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                    <note xml:id="note-L39F2" dur="4" fermata="above" oct="3" pname="b" accid.ges="n" />
                                    <note xml:id="note-L40F2" dur="4" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L35F1" n="4">
                                <layer xml:id="layer-L35F1" n="1">
                                    <note xml:id="note-L36F1" dur="4" oct="3" pname="g" accid.ges="n" />
                                    <note xml:id="note-L38F1" dur="4" oct="3" pname="d" accid.ges="n" />
                                    <note xml:id="note-L39F1" dur="4" fermata="above" oct="3" pname="g" accid.ges="n" />
                                    <note xml:id="note-L40F1" dur="4" oct="3" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L41" n="5">
                            <staff xml:id="staff-L41F4" n="1">
                                <layer xml:id="layer-L41F4" n="1">
                                    <note xml:id="note-L42F4" dur="4" oct="5" pname="c" accid.ges="n" />
                                    <note xml:id="note-L44F4" dur="4" oct="4" pname="b" accid.ges="n" />
                                    <note xml:id="note-L45F4" dur="4" oct="5" pname="d" accid.ges="n" />
                                    <note xml:id="note-L47F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L41F3" n="2">
                                <layer xml:id="layer-L41F3" n="1">
                                    <beam xml:id="beam-0000001881799911">
                                        <note xml:id="note-L42F3" dur="8" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L43F3" dur="8" accid="s" oct="4" pname="f" />
                                    </beam>
                                    <note xml:id="note-L44F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L45F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L47F3" dur="4" oct="4" pname="f" accid.ges="s" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L41F2" n="3">
                                <layer xml:id="layer-L41F2" n="1">
                                    <note xml:id="note-L42F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <note xml:id="note-L44F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                    <note xml:id="note-L45F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                    <beam xml:id="beam-0000001489660328">
                                        <note xml:id="note-L47F2" dur="8" oct="4" pname="d" accid.ges="n" />
                                        <note xml:id="note-L48F2" dur="8" oct="4" pname="c" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L41F1" n="4">
                                <layer xml:id="layer-L41F1" n="1">
                                    <note xml:id="note-L42F1" dur="4" oct="3" pname="a" accid.ges="n" />
                                    <note xml:id="note-L44F1" dur="4" oct="3" pname="g" accid.ges="n" />
                                    <beam xml:id="beam-0000000367623743">
                                        <note xml:id="note-L45F1" dur="8" oct="2" pname="b" accid.ges="n" />
                                        <note xml:id="note-L46F1" dur="8" oct="3" pname="c" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L47F1" dur="4" oct="3" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L49" n="6">
                            <staff xml:id="staff-L49F4" n="1">
                                <layer xml:id="layer-L49F4" n="1">
                                    <note xml:id="note-L50F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L52F4" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <note xml:id="note-L54F4" dur="4" fermata="above" oct="4" pname="d" accid.ges="n" />
                                    <note xml:id="note-L55F4" dur="4" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L49F3" n="2">
                                <layer xml:id="layer-L49F3" n="1">
                                    <beam xml:id="beam-0000000519552637">
                                        <note xml:id="note-L50F3" dur="8" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L51F3" dur="8" oct="4" pname="d" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L52F3" dur="4" accid="s" oct="4" pname="c" />
                                    <note xml:id="note-L54F3" dur="4" fermata="above" oct="3" pname="a" accid.ges="n" />
                                    <note xml:id="note-L55F3" dur="4" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L49F2" n="3">
                                <layer xml:id="layer-L49F2" n="1">
                                    <note xml:id="note-L50F2" dur="4" oct="3" pname="b" accid.ges="n" />
                                    <beam xml:id="beam-0000000190122362">
                                        <note xml:id="note-L52F2" dur="8" oct="3" pname="a" accid.ges="n" />
                                        <note xml:id="note-L53F2" dur="8" oct="3" pname="g" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L54F2" dur="4" fermata="above" accid="s" oct="3" pname="f" />
                                    <beam xml:id="beam-0000001349981973">
                                        <note xml:id="note-L55F2" dur="8" oct="3" pname="f" accid.ges="s" />
                                        <note xml:id="note-L56F2" dur="8" oct="3" pname="g" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L49F1" n="4">
                                <layer xml:id="layer-L49F1" n="1">
                                    <note xml:id="note-L50F1" dur="4" oct="2" pname="g" accid.ges="n" />
                                    <note xml:id="note-L52F1" dur="4" oct="2" pname="a" accid.ges="n" />
                                    <note xml:id="note-L54F1" dur="4" fermata="above" oct="3" pname="d" accid.ges="n" />
                                    <beam xml:id="beam-0000000652000065">
                                        <note xml:id="note-L55F1" dur="8" oct="3" pname="d" accid.ges="n" />
                                        <note xml:id="note-L56F1" dur="8" oct="3" pname="e" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L57" n="7">
                            <staff xml:id="staff-L57F4" n="1">
                                <layer xml:id="layer-L57F4" n="1">
                                    <note xml:id="note-L58F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L60F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L62F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L63F4" dur="4" oct="4" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L57F3" n="2">
                                <layer xml:id="layer-L57F3" n="1">
                                    <note xml:id="note-L58F3" dur="4" oct="4" pname="d" accid.ges="n" />
                                    <beam xml:id="beam-0000000143028349">
                                        <note xml:id="note-L60F3" dur="8" oct="4" pname="a" accid.ges="n" />
                                        <note xml:id="note-L61F3" dur="8" oct="4" pname="g" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L62F3" dur="4" accid="s" oct="4" pname="f" />
                                    <note xml:id="note-L63F3" dur="4" accid="s" oct="4" pname="g" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L57F2" n="3">
                                <layer xml:id="layer-L57F2" n="1">
                                    <beam xml:id="beam-0000000598459329">
                                        <note xml:id="note-L58F2" dur="8" oct="3" pname="a" accid.ges="n" />
                                        <note xml:id="note-L59F2" dur="8" oct="3" pname="b" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L60F2" dur="4" accid="s" oct="4" pname="c" />
                                    <note xml:id="note-L62F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                    <note xml:id="note-L63F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L57F1" n="4">
                                <layer xml:id="layer-L57F1" n="1">
                                    <beam xml:id="beam-0000001521148834">
                                        <note xml:id="note-L58F1" dur="8" accid="s" oct="3" pname="f" />
                                        <note xml:id="note-L59F1" dur="8" oct="3" pname="g" accid.ges="n" />
                                        <note xml:id="note-L60F1" dur="8" oct="3" pname="a" accid.ges="n" />
                                        <note xml:id="note-L61F1" dur="8" oct="3" pname="b" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L62F1" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <note xml:id="note-L63F1" dur="4" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L64" n="8">
                            <staff xml:id="staff-L64F4" n="1">
                                <layer xml:id="layer-L64F4" n="1">
                                    <note xml:id="note-L65F4" dur="4" oct="5" pname="c" accid.ges="n" />
                                    <note xml:id="note-L66F4" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <beam xml:id="beam-0000001824702414">
                                        <note xml:id="note-L68F4" dur="8" oct="4" pname="g" accid.ges="n">
                                            <accid xml:id="accid-0000000579777346" accid="n" func="caution" />
                                        </note>
                                        <note xml:id="note-L69F4" dur="8" oct="4" pname="a" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L70F4" dur="4" oct="4" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L64F3" n="2">
                                <layer xml:id="layer-L64F3" n="1">
                                    <note xml:id="note-L65F3" dur="4" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L66F3" dur="4" oct="4" pname="f" accid.ges="n">
                                        <accid xml:id="accid-0000001210611201" accid="n" func="caution" />
                                    </note>
                                    <beam xml:id="beam-0000000878184336">
                                        <note xml:id="note-L68F3" dur="8" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L69F3" dur="8" accid="s" oct="4" pname="f" />
                                    </beam>
                                    <note xml:id="note-L70F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L64F2" n="3">
                                <layer xml:id="layer-L64F2" n="1">
                                    <note xml:id="note-L65F2" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <note xml:id="note-L66F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <note xml:id="note-L68F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <note xml:id="note-L70F2" dur="4" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L64F1" n="4">
                                <layer xml:id="layer-L64F1" n="1">
                                    <note xml:id="note-L65F1" dur="4" oct="3" pname="a" accid.ges="n" />
                                    <beam xml:id="beam-0000001371547833">
                                        <note xml:id="note-L66F1" dur="8" oct="2" pname="a" accid.ges="n" />
                                        <note xml:id="note-L67F1" dur="8" oct="2" pname="b" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L68F1" dur="4" oct="3" pname="c" accid.ges="n" />
                                    <beam xml:id="beam-0000001686117298">
                                        <note xml:id="note-L70F1" dur="8" oct="2" pname="b" accid.ges="n" />
                                        <note xml:id="note-L71F1" dur="8" oct="3" pname="c" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                            <tie xml:id="tie-0000002046679017" startid="#note-L70F3" endid="#note-L73F3" />
                            <tie xml:id="tie-0000000288518164" startid="#note-L70F2" endid="#note-L73F2" />
                        </measure>
                        <measure xml:id="measure-L72" n="9">
                            <staff xml:id="staff-L72F4" n="1">
                                <layer xml:id="layer-L72F4" n="1">
                                    <note xml:id="note-L73F4" dur="2" oct="4" pname="a" accid.ges="n" />
                                    <note xml:id="note-L77F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L79F4" dur="4" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L72F3" n="2">
                                <layer xml:id="layer-L72F3" n="1">
                                    <note xml:id="note-L73F3" dur="4" oct="4" pname="g" accid.ges="n" />
                                    <note xml:id="note-L75F3" dur="4" oct="4" pname="f" accid.ges="n" />
                                    <beam xml:id="beam-0000002100091238">
                                        <note xml:id="note-L77F3" dur="8" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L78F3" dur="8" oct="4" pname="d" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L79F3" dur="4" oct="4" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L72F2" n="3">
                                <layer xml:id="layer-L72F2" n="1">
                                    <beam xml:id="beam-0000000948778575">
                                        <note xml:id="note-L73F2" dur="8" oct="4" pname="d" accid.ges="n" />
                                        <note xml:id="note-L74F2" dur="8" oct="3" pname="a" accid.ges="n" />
                                        <note xml:id="note-L75F2" dur="8" oct="4" pname="d" accid.ges="n" />
                                        <note xml:id="note-L76F2" dur="8" oct="4" pname="c" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L77F2" dur="4" oct="3" pname="b" accid.ges="n" />
                                    <note xml:id="note-L79F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L72F1" n="4">
                                <layer xml:id="layer-L72F1" n="1">
                                    <note xml:id="note-L73F1" dur="4" oct="3" pname="d" accid.ges="n" />
                                    <beam xml:id="beam-0000000339453189">
                                        <note xml:id="note-L75F1" dur="8" oct="3" pname="c" accid.ges="n" />
                                        <note xml:id="note-L76F1" dur="8" oct="3" pname="d" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L77F1" dur="4" oct="3" pname="e" accid.ges="n" />
                                    <beam xml:id="beam-0000002018112551">
                                        <note xml:id="note-L79F1" dur="8" oct="3" pname="d" accid.ges="n" />
                                        <note xml:id="note-L80F1" dur="8" oct="3" pname="c" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                            <tie xml:id="tie-0000001100329265" startid="#note-L75F3" endid="#note-L77F3" />
                            <tie xml:id="tie-0000001171649387" startid="#note-L79F3" endid="#note-L82F3" />
                            <tie xml:id="tie-0000001272956280" startid="#note-L79F2" endid="#note-L82F2" />
                        </measure>
                        <measure xml:id="measure-L81" n="10" right="end">
                            <staff xml:id="staff-L81F4" n="1">
                                <layer xml:id="layer-L81F4" n="1">
                                    <note xml:id="note-L82F4" dur="1" fermata="above" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L81F3" n="2">
                                <layer xml:id="layer-L81F3" n="1">
                                    <note xml:id="note-L82F3" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <beam xml:id="beam-0000000802154033">
                                        <note xml:id="note-L83F3" dur="8" oct="4" pname="d" accid.ges="n" />
                                        <note xml:id="note-L84F3" dur="8" oct="4" pname="c" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L85F3" dur="2" fermata="above" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L81F2" n="3">
                                <layer xml:id="layer-L81F2" n="1">
                                    <note xml:id="note-L82F2" dur="4" oct="4" pname="c" accid.ges="n" />
                                    <beam xml:id="beam-0000001703057845">
                                        <note xml:id="note-L83F2" dur="8" oct="3" pname="b" accid.ges="n" />
                                        <note xml:id="note-L84F2" dur="8" oct="3" pname="a" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-L85F2" dur="2" fermata="above" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L81F1" n="4">
                                <layer xml:id="layer-L81F1" n="1">
                                    <note xml:id="note-L82F1" dur="2" oct="3" pname="g" accid.ges="n" />
                                    <note xml:id="note-L85F1" dur="2" fermata="above" oct="2" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>

                </score>
            </mdiv>

    </music>
</mei>
```


needs status code assertion first, then try/catch  around parse and assert


same as above


@jpvguerreiro  are you using voice over? I think gesture recognizer requires blind user to double tap and hold on the view in default. You need to make direct interaction flag true for the view to be operated. Currently NavCoverView is overlay on the map during navigation. If you can disable function of checking former announcements on the NavCoverView, you can use the view to enable your functions.


The gluon-mesh-babel and gluon-mesh-batman-adv-core packages also write there. I can take care of the babel package but this pr should probably include the Batman package


use maths over loops
```python
used_fuel = 5 - self.starting_fuel
self.starting_fuel = 5
```


nice


Developing


For future reference, the [test is failing](https://travis-ci.org/balderdashy/sails/jobs/182409204) because:

```
stdout: info: No local Sails install detected; using globally-installed Sails.
...
...
stderr: debug: -------------------------------------------------------

          ✓ should still be lifted
          ✓ should respond with a 200 status code when a `GET` request is sent to `http://localhost:1337`
          ✓ should humanize the config passed in via env vars
      running `node app.js`
        and then waiting for a bit
stderr: Encountered an error when attempting to require('sails'):

stderr: Error: Cannot find module 'sails'
    at Function.Module._resolveFilename (module.js:326:15)
    at Function.Module._load (module.js:277:25)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/private/var/folders/_s/347n05_x2rgb_0w6s6y0ytr00000gn/T/tmp-291179ZUWIae91wSm/testApp/app.js:35:11)
    at Module._compile (module.js:410:26)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:442:10)

stderr: --

stderr: To run an app using `node app.js`, you usually need to have a version of `sails` installed in the same directory as your app.
To do that, run `npm install sails`

stderr:
Alternatively, if you have sails installed globally (i.e. you did `npm install -g sails`), you can use `sails lift`.
When you run `sails lift`, your app will still use a local `./node_modules/sails` dependency if it exists,

stderr: but if it doesn't, the app will run with the global sails instead!

          ✓ should still be lifted
          1) should humanize the config passed in via env vars
          2) "after all" hook

```


The exclamation mark is not actually included in `NASTY_METACHARS`:
```
#define NASTY_METACHARS	"|`&><'\\[]{};\r\n"
```
https://github.com/NagiosEnterprises/nrpe/blob/master/src/nrpe.c#L64


yes. thanks.


@weinand I'm not sure if you've seen these features - I called them out in the release notes hoping to get more attention to node2, but if you want to implement them in node-debug I could hold off til next month.


Also please proofread my notes for skipFiles, I wasn't sure what all to say.


pass just the `clickColor` variable to the function.


pass `clickColor` to this function too.


Fixed, thanks.


remove forEach and just use the conditional on the clickColor passed into this function.


you could have cleaned this up by eg. saying `we have a next letter` in the diamond and the usual `yes` and `no` on the arrows


try `.append`. `.html` will overwrite previous, which might be why you need to track them all in the array.


remove forEach here too and use the conditional on the clickColor passed into this function.


Why?


Log the globals and see if they are updating correctly.  Then try the DOM append.


cc @javiercn despite what `crossgen /help` says, Linux requires `:` instead of `;` as a path separator. (facepalm)


@dylanwenzlau added this to MySQLQuery only since they are not supported in Postgres


Align - BWA-mem


try with this testcase, that was in the task description:
```python
    def test_list_input_even(self):
        self.assertEqual(first.list_second_elements_selector([1, 2, 3, 4, 5]), [2, 4])
```


Why not `^//+$`?


Hey @musawirali, `resolve-url-loader` owner here. Just looking at the forks. I hope you don't mind me prying.

Can I ask what your use-case is? Looks like you need to process a custom function `image_url(...)` rather than `url(...)`.

Should I add some configuration to `resolve-url-loader` so that we can cater for this?


what you are checking is if the current **value** is odd.
what you should check if the index is even. "a new list with every **second element**"


Maybe this color would look nice as the background #FFF7CE


![](https://github.trello.services/images/mini-trello-icon.png) [test](https://trello.com/c/CFgObpeS/1-test)


nice,


Oops, my bad, I'm not yet used to the apostrophes...
Regarding future builds, I don't really have a preference, but maybe some french translation is better than nothing ^^
However if you prefer finished work it's fine, too. I will give you a heads up once all strings are translated 😉

Apart from that, I have to ask you : the email I use here is my main email, linked to all the services I use. Is it okay to display it publicly ?


nice


This change is unrelated to the rest of the commit.  Why was it added?


Why is it needed? This part of code cause error message in !3
```
Exception ignored in: <bound method Client.__del__ of <hpc05.client.Client object at 0x7f3347af5d68>>
Traceback (most recent call last):
  File "/home/rskolasinski/miniconda3/envs/kwantmaster/lib/python3.5/site-packages/hpc05/client.py", line 126, in __del__
    if self.tunnel:
AttributeError: 'Client' object has no attribute 'tunnel'
```


It did it.


Oh dear!  I can fix it if you like.  Or if you want to.


It was a duplicate.


Hey @Tol1, `resolve-url-loader` owner here. Just looking at the forks, hoping to give some help. I hope you don't mind me prying.

Can I ask what your use-case is? It looks like you need to support some legacy systems where you have assets already written to the output path.

Once Webpack finds these assets in your output path, is it not reprocessing them and overwriting?


Thanks!

This works for me authenticating to Oracle Service Cloud REST service from JSAPI.  I don't use the proxy for anything else.  So, I can't tell you whether or not it breaks any of the other proxy workflows.  What would it take to get this merged up into the master? https://github.com/Esri/resource-proxy

Dan


Could you please remove this


Weird, I manaly tested it before pushing it...

Never mind, no time to add real test to this tiny project.

Thanks for your work ;)


Shouldn't `inst` be `instdir`?

And don't `exeinto` and `insinto` already respect EPREFIX?


OMG, does this actually work?

Looks like it does! https://travis-ci.org/mvdan/interfacer/builds/182339084

I've been wishing I could achieve this for years! How did you discover this? I looked through Travis docs and googled it and couldn't find a way. Thank you!


@iaz3 @fireundubh have a look at the commits in this merge

If you could finalize f313241c65c2a958df39fa4393beb86fa8fbbba7, 0c7e8ac5e295224f60587ba08e178c56e02044cd or b14016d9526f367cedd0e614bf42dfea6f737d2a it would be grand - renames of local text and tip variables plus namespacing settings (see the commit messages)


yes, you could have returned this only once, and stored tank size, but otherwise it's 👍


This changed the functionality of using `timeByUrl` with response code counting. In the old code it would always increment `response_code.<status_code>` regardless of if you were using `timeByUrl`. With the new code if you are using `timeByUrl` you will no longer get `response_code.<status_code>` as it will now always include the `urlPrefix`. Because of this change we are no longer getting counts for status codes in total and now only get counts for status codes scoped to a specific endpoint which broke some of our dashboards. It seems that there should still be a `client.increment('response_code.' + res.statusCode)` in addition to the counting per endpoint.


@roblourens yes please, that's exactly what I'd like to see for node2 (and if you have ideas for surfacing this diagnostic information in a more prominent/direct way, please let us know).


In master it works fine except for the house model.
In renderHeritage branch some things renders correctly others don't


OMG Thank you! Backing up my gs-core now and getting it setup. Thank you so much for this and know many appreciate this!


FFS this should have been on its issue branch.


It must be a new feature, because it's really obviously documented now. https://docs.travis-ci.com/user/languages/go#Specifying-a-Go-version-to-use I swear it was not there before.


it looks like nothing was done xD, control z oddly makes commits become applied without any tests or anything


Why strings are compared with == only? IMO it's plainly wrong!


I think you can also do
```
ar
  << x << y << z;
```
It can sometimes make code simpler to read


for once the pylint warnings could have saved you:
`W0622 Redefining built-in 'type'`
you can't use `type` as a variable name, it is reserved. so this function won't pass a proper falcon1 or falcon9 to the Rocket constructor.
and a rocket without a proper type doesn't return anything in its refill method - all the returns there are inside ifs


Estos cambios eran inecesarios.


estos cambios fueron inecesarios , sugiero omitirlos.


```
M = P.block<3,3>(0,0);
```


Changed wrong bit


Estos comentarios no son relevantes por lo que hay que omitirlos


Estos cambios era inecesarios. Sugiero omitirlos


You shouldn't send `WithHash` over network, it's at least insecure to trust hash provided from other person. Also, `WithHash` is to be used when you want to reuse once calculated hash.


no launches


Estos cambios eran innecesarios


where is the lazy add?


Estos cambios nu fueron reelevantes


Estos cambios no fueron reelevantes


@JackShelley
Can you flip this logic so we have `if user_signed_in?` in the positive without having to use the `!` (just move the `else` logic up here, and this logic down there)


como se ven mis cambios, parece que estan bien


```
pt = {x,y,1.0} * P.diag();
```
or Vec3(x,y,1.0))


:shipit:


TeamCity Glyssen :: Glyssen pull requests [Build *.*.371.bcff640e78f47612f698f1ce69e392ca46ca5f6b](http://build.palaso.org/viewLog.html?buildId=81261&buildTypeId=Glyssen_GlyssenPullRequests) outcome was **SUCCESS**
Summary: Tests passed: 1555, ignored: 18 Build time: 00:07:56


Yup. Added recently, but the docs were confusing until a few hours ago. See https://github.com/mvdan/sh/pull/60#discussion_r91554806

CC @meatballhat I told you people didn't know this :)


DON'T OBEY!


switch?


(you can also edit the commit message to something more descriptive when editing the readme on github)


Cambios inecesarios


@JackShelley
Using the shoulda-matchers gem, you can make this test look like:
```ruby
it { is_expected.to validate_presence_of(:username) }
```

Without using the should-matchers, then I would expect a negative case. What happens when they do not pass it in? Your test suite is not covering that case.


Does this object is used? (I do not see any reference on him in the commit)


k


0 % 2 is also 0, so it would be enough to just `i % 2 != 0`


Можно, например, `catalog__product-wrapper`.
Вот тут, кстати, есть список часто используемых слов в названиях классов: https://github.com/yoksel/common-words.

Ещё можно залезть в код https://ru.bem.info/ и посмотреть как они решают разные задачи.


otherwise it's 👍


It's been dark shipped for a bit now, but just recently documented.  Sorry for delay!


I've posted about it on /r/golang to spread the word a bit: https://www.reddit.com/r/golang/comments/5ha3n5/tip_use_go_17x_to_use_the_latest_patch_version_on/


#1 Update Sitecore NuGet dependencies to 8.2 update 1 versions


This is a brute-force method to find median of 2 sorted arrays.


@gergo85 - Hey, just made an update to include tinypng integration (in relation to issue mentioned here - http://octobercms.com/plugin/support/toughdeveloper-imageresizer/image-size-problem).

I had also had an issue recently that Google Pagespeed insights was flagging up image compression , which this also solves.

If you have time, would appreciate if you could have a once over and correct the Hungarian.

Thanks in advance,
Matt


Ссылка на текущую страницу должна быть некликабельной, для этого можно просто убрать href


Thank you for validate Pull Request.
You are welcome :), it is a pleasure to help.


reading the file back doesn't do the trick here, what we would have needed is just to catch any exception that indicates 'any problem raised'