# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


AFN_FanModel (jasondegraw) - Win64-Windows-10-VisualStudio-16: Tests Failed (0 of 0 tests passed, 0 test warnings)

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


Please open an issue instead of commenting on a year old commit @u01jmg3 - this will get ignored here.


Dear @SuperStulle007,
> I regret to inform you that your plugin "**UltraCapes**" (v1.1.0 submitted on 2019-07-11T15:50:50.000Z) has been rejected.

Plugins should include FormAPI as a library and should not depend on it as a plugin.

Please resolve these issues and submit the plugin again.

> This comment is posted here because this is the last commit when the released build was created.


socket should be changed to l3cat_id


Successfully aliased the URL <https://yld-storybook-9u12m7zmf.now.sh> to the following aliases:

* https://yld-storybook.now.sh
* https://yld-storybook.carvil.now.sh
* https://yld-storybook-git-master.carvil.now.sh


ooo


I'm not sure I understand why you have to change  `fsGroup` and `runAsGroup` to 1000 now that you have made [this change in the Dockerfile](https://github.com/eclipse/che/commit/924e6c897cbde2aaa8fee6e61842ec0735e11fbc#diff-47383421eb7faa4eb651978d3a598677R19)

[K8s Documentation](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod) states that if the `runAsGroup` field is omitted, the primary group ID of the containers will be root(0). That means that the primary group of processes run in the container will be precisely the group we gave permissions to for the `/scripts` folder in the Dockerfile.
So having the 1000 userId and 0 groupId (which is the default groupId) for container processes seems to be consistent with what is expected by the Dockerfile.

Am I missing some point here ?


Successfully aliased the URL <https://nextjs-gr0h39fxg.now.sh> to the following aliases:

* https://nextjs.jarforjs.now.sh
* https://nextjs-git-master.jarforjs.now.sh


@locutus2
Cool patch! Nice work!
Maybe also try updating capture stats as well.


mba_id for os_mba_set()


@jow- many thanks! And the new client side "view" looks really cool, much more flexible than the old approach.


好工具多谢


#3 問題消失了
再跑一段時間驗證


I've created a pull request:
https://github.com/brummer10/GxMatchEQ.lv2/pull/1


Successfully aliased the URL <https://whatcolourhoodieiskevinwearingtodaycom-fpcrgziwa.now.sh> to the following aliases:

* https://whatcolourhoodieiskevinwearingtoday.com
* https://whatcolourhoodieiskevinwearingtodaycom.kevincarrogan.now.sh
* https://whatcolourhoodieiskevinwearingtodaycom-git-master.kevincarrogan.now.sh


One note on the documentation: You treat the upper and lower case letters differently, not the same.


Golang recommends reusing the client.
https://golang.org/pkg/net/http/#Client


Successfully aliased the URL <https://jjswebsite-h310qfwjq.now.sh> to the following aliases:

* https://jjswebsite.jj4.now.sh
* https://jjswebsite-git-master.jj4.now.sh


yeah,lots of thanx for updating this unit i haved like problems and i think its fixed :)


This method does not works with the `IntegrationTests`


HAMT2_Release (antretterf) - x86_64-MacOS-10.13-clang: Tests Failed (2391 of 2992 tests passed, 29 test warnings)

Messages:\n
 * 279 tests had: AUD diffs.
 * 279 tests had: EIO diffs.
 * 145 tests had: ESO big diffs.
 * 271 tests had: RDD diffs.
 * 232 tests had: Table big diffs.
 * 67 tests had: ESO small diffs.
 * 133 tests had: BND diffs.
 * 136 tests had: MDD diffs.
 * 146 tests had: MTD diffs.
 * 39 tests had: ERR diffs.
 * 64 tests had: MTR big diffs.
 * 14 tests had: MTR small diffs.
 * 5 tests had: SSZ small diffs.
 * 12 tests had: ZSZ small diffs.
 * 4 tests had: SSZ big diffs.
 * 17 tests had: ZSZ big diffs.
 * 1 test had: DXF diffs.
 * 1 test had: SHD diffs.

Failures:\n

regression Test Summary
 * Passed: 34
 * Failed: 601

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


@hectoralos Aquestes dobles entrades són necessàries perquè després de "mitjan" fem caure l'article en postedició. Per exemple: Hasta mediados del siglo XX > Fins a mitjan segle XX. No sé si pot molestar per a alguna altra cosa.


Successfully aliased the URL <https://web-lbkbs8whx.now.sh> to the following aliases:

* https://cesko.digital
* https://web.ceskodigital.now.sh
* https://web-git-master.ceskodigital.now.sh


Successfully aliased the URL <https://class101-dev-dswxn3iac.class101.dev> to the following aliases:

* https://class101-dev.class101.dev
* https://class101-dev-git-master.class101.dev


Why do you see that as a secret?


you should change

`let id = req.param["id"]`

at line 42 and 57 to

`let id = req.params["id"]`


@esmos So fresh build, fresh usb flash ...... and Yes it works - my apologies.
@betacentauri - so are you able now to add the GPT changes to ofgwrite?


Because with the slug you can open the profile page and see all the other
collectives that that particular anonymous profile has backed.

On Fri, 12 Jul 2019 at 11:04, François Hodierne <notifications@github.com>
wrote:

> Why do you see that as a secret?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/opencollective/opencollective-api/commit/1e3a5ce32e5b970c022ef63ec2cc91f1be980399?email_source=notifications&email_token=AAASE5SK4CUMZ2RIUOFAEO3P7BCIRA5CNFSM4ICFJGD2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAWEDG#commitcomment-34279526>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAASE5XTYGKA7W4K5BFCRLLP7BCIRANCNFSM4ICFJGDQ>
> .
>


Per a evitar aquests merge, que no aporten res i maregen una mica, em sembla que cal fer "git pull --rebase" en comptes de "git pull". És així? @xavivars


Successfully aliased the URL <https://jjswebsite-9chh66kmi.now.sh> to the following aliases:

* https://jjswebsite.jj4.now.sh
* https://jjswebsite-git-master.jj4.now.sh


这里检测环境最好还是用 configs.inBrowser 这个变量吧


Sounds good, but there is one more problem. This button is/was not appearing.

![image](https://user-images.githubusercontent.com/52812950/61116669-868c8200-a4b2-11e9-8257-ba3e05eff7cf.png)


Ok, with this there is a tiny advantage for "CH" and "CH without instructions" over master. It is no error but within 5%, so not worth the effort


there was #runWriteInEDT and the comment above looks very strange together with the new code


Java


പറ്റും. അപ്ലിക്കേഷനിൽ (4 ാമത്) എന്നുള്ള റ്റെക്സ്റ്റ് മുഴുവനായും സ്വമക ഫോണ്ടു തന്നെ ഉപയോഗിക്കുക.
ചില അപ്ലിക്കേഷനുകൾ (ഉദാഃ ലിബ്രെഓഫിസ്) ഇതു ശരിയായി പിന്തുണയ്ക്കുന്നില്ല. മറ്റു ചിലത് (ഉദാഃ ഫയർഫോക്സ്) ലാറ്റിൻ അക്ഷരങ്ങൾ — 4 — ലാറ്റിൻ ഫോണ്ടുപയോഗിച്ചാവും സാധാരണ കാണിക്കുക (ഫോണ്ട് സ്റ്റൈൽ പറഞ്ഞിട്ടില്ലാത്തതിനാല്), ആ അവസരത്തിൽ dotted-circle കാണപ്പെടും.

പിന്‍കുറിപ്പ്: ഇത്തരം ചൎച്ചകള്‍ക്കും പ്രശ്നങ്ങൾ രേഖപ്പെടുത്താനും Gitlab issues ഉപയോഗിക്കുക: https://gitlab.com/smc/fonts


test html


Sure: #105


oo_plant_load_profile (drewyh) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (658 of 660 tests passed, 0 test warnings)

Failures:\n

integration Test Summary
 * Passed: 658
 * Timeout: 2

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


Successfully aliased the URL <https://gelfand-gatsby-project-d97bdd6my.now.sh> to the following aliases:

* https://gelfand-gatsby-project.leoraw.now.sh
* https://gelfand-gatsby-project-git-master.leoraw.now.sh


Successfully aliased the URL <https://prisma-specs-jzu0eevwi.now.sh> to the following aliases:

* https://prisma-specs.prisma.now.sh
* https://prisma-specs-git-master.prisma.now.sh


Successfully aliased the URL <https://web-9zshlnf02.now.sh> to the following aliases:

* https://cesko.digital
* https://web.ceskodigital.now.sh
* https://web-git-master.ceskodigital.now.sh


Run project with this tutorial, But can not login with user, pass on D00T0030 table


Successfully aliased the URL <https://portfolio-bsfx6kbpv.now.sh> to the following aliases:

* https://portfolio.sklinkusch.now.sh
* https://portfolio-git-master.sklinkusch.now.sh


one way of doing it is to sample every second or so, and ACK the latest sample. Let's chat privately about the ways it can be achieved 👍


Aggg, ara ho he vist en els logs! Perdoneu...


I did not get from the commit where NPE happened, it will be good to clarify that in the commit message.
The other workflow we have is to create an issue in YouTrack (named smth like "ShowImplementations does not work" or "NPE in Show Implementations") and to refer to the issue in the commit message (smth like
git commit -m"MPS-12345 NPE in Show Implementations"
)

Of course any clarifications on the actual changes in the commit could be appended to the commit message body.


As far as I can see this is not tested in our CI. Please add a line in our Travis and/or Appveyor scripts.


really really really really raelly slowwwwwwwwwww


Successfully aliased the URL <https://web-ezqn1rdxl.now.sh> to the following aliases:

* https://cesko.digital
* https://web.ceskodigital.now.sh
* https://web-git-master.ceskodigital.now.sh


ok


Successfully aliased the URL <https://fortech-835wozos0.now.sh> to the following aliases:

* https://fortech.now.sh
* https://arjunsn.now.sh
* https://fortech.arjunsn.now.sh
* https://fortech-git-master.arjunsn.now.sh


Nên dùng padding thay vì khoảng trống cho placeholder


should not be called dummy


## Jenkins Build Summary

Built from [this commit](https://github.com/ximinez/rippled/commit/87eb6405e3c07343c29adbeacc716616b364a65e)

Built at __20190712 - 09:21:49__

### Test Results

Build Type | Log | Result | Status
---------- | --- | ------ | ------
msvc.Debug | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/msvc.Debug.txt) | 1178 cases, 0 failed, t: 574s | PASS :white_check_mark:
msvc.Debug,
NINJA_BUILD=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/msvc.Debug_NINJA_BUILD_true.txt) | 1178 cases, 0 failed, t: 604s | PASS :white_check_mark:
msvc.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/msvc.Debug_Dunity_OFF.txt) | 1177 cases, 0 failed, t: 1096s | PASS :white_check_mark:
msvc.Release | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/msvc.Release.txt) | 1178 cases, 0 failed, t: 406s | PASS :white_check_mark:
gcc.Release
-Dassert=ON,
MANUAL_TESTS=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Release_Dassert_ON_MANUAL_TESTS_true.txt) | 915 cases, 0 failed, t: 4m59s | PASS :white_check_mark:
docs,
TARGET=docs | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/docs_TARGET_docs.txt) | 1 cases, 0 failed, t: 0m1s | PASS :white_check_mark:
clang.Debug | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/clang.Debug.txt) | 1178 cases, 0 failed, t: 2m56s | PASS :white_check_mark:
gcc.Debug
-Dcoverage=ON,
TARGET=coverage_report,
SKIP_TESTS=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Debug_Dcoverage_ON_TARGET_coverage_report_SKIP_TESTS_true.txt) | 1178 cases, 0 failed, t: 16m49s | PASS :white_check_mark:
gcc.Debug | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Debug.txt) | 1178 cases, 0 failed, t: 2m58s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/clang.Debug_Dunity_OFF.txt) | 1177 cases, 0 failed, t: 10m30s | PASS :white_check_mark:
gcc.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Debug_Dunity_OFF.txt) | 1177 cases, 0 failed, t: 11m24s | PASS :white_check_mark:
clang.Release
-Dassert=ON | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/clang.Release_Dassert_ON.txt) | 1178 cases, 0 failed, t: 5m4s | PASS :white_check_mark:
gcc.Debug
-Dstatic=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Debug_Dstatic_OFF.txt) | 1178 cases, 0 failed, t: 2m54s | PASS :white_check_mark:
gcc.Release
-Dassert=ON | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Release_Dassert_ON.txt) | 1178 cases, 0 failed, t: 4m59s | PASS :white_check_mark:
gcc.Debug
-Dstatic=OFF -DBUILD_SHARED_LIBS=ON | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Debug_Dstatic_OFF_DBUILD_SHARED_LIBS_ON.txt) | 1178 cases, 0 failed, t: 2m53s | PASS :white_check_mark:
gcc.Debug,
NINJA_BUILD=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/gcc.Debug_NINJA_BUILD_true.txt) | 1178 cases, 0 failed, t: 2m51s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF -Dsan=address,
PARALLEL_TESTS=false,
DEBUGGER=false | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/clang.Debug_Dunity_OFF_Dsan_address_PARALLEL_TESTS_false_DEBUGGER_false.txt) | 1177 cases, 0 failed, t: 7m39s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF -Dsan=undefined,
PARALLEL_TESTS=false | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/fund-flags/18//artifact/clang.Debug_Dunity_OFF_Dsan_undefined_PARALLEL_TESTS_false.txt) | 1177 cases, 0 failed, t: 12m45s | PASS :white_check_mark:


empty line


I think we should not try to protect that because it's not possible to do it properly. There is too many places this would need to be enforced in the API.

I would be ok with a frontend land feature preventing to display the information.


number of local subscribers and number of affected brokers should be optional fields, so we need a secondary constructor. The default value for these two should be -1 if not set.


Typo - should be `while`


why is it 1, 2?


also dummy


I meant, I don't make a PR for it ^^ Just commit on master...


is read access absolutely necessary here?


what is c?


TBH, I still need to take a look at `Kind_Media_View`, to figure out the uses. I only stumbled onto it last night when comparing my view templates to the latest versions while debugging something. From a quick scan, it would be nice to be able to override the gallery attributes in `Kind_Media_View::photo`, if you're planning to continue down this path.

What I'd be most interested in, is a simplified way to access Kind data, both inside the view templates and outside of them. Whether that's best done through helper functions, or an object interface like `$kind = new Kind($post)` and then using `$kind->verb`, `$kind->the_url`, `$kind->photos`, or similar, I'm not sure. At the moment, there's a bunch of setup needed at the start of every template to get author/url/response details, which feels like it could made simpler. Similarly, looking up Kind info outside of a view requires getting the MF2_Post, then using that to extract different bits of information with Kind_Taxonomy or Kind_View.  It's not a big deal to do, but removing these steps would be a nice "quality of life" improvement for hooking into Post Kinds from themes.


no dummy


How about `test_verifyRuleTexts`?


Can you also add a number of test cases to validate that the results are as expected. Maybe it is also sufficient to update some of the existing tests (like the scenario runs) to also check the PUBACK fields for correct values.


The cool kids use `yay` now


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


M’ho apunte però això no hauria evitat el conflicte, no? I en quin moments ho he de fer: abans de començar a treballar i abans de fer commit?

Perdona i gràcies per apanyar-ho.

Gema

Gema Ramírez | CEO
Prompsit Language Engineering  | www.prompsit.com
gramirez@prompsit.com | (+34) 96 545 75 49

MT-powered translation: http://aplica.prompsit.com
AtlLang, all your content in the right language variant of your audience: https://www.altlang.net/home/

Este mensaje y sus archivos adjuntos pueden contener información confidencial, cuyo uso sin autorización está prohibido por las leyes europeas y las de otros países. Si ha recibido este mensaje por equivocación debe notificarlo inmediatamente a través de esta misma vía y proceder al borrado del mensaje original junto con sus ficheros adjuntos sin leerlo o grabarlo total o parcialmente.

Conforme a lo establecido en el  reglamento europeo 2016/679 de protección de datos o RGPD, le informamos que los datos personales que consten en esta comunicación son responsabilidad de PROMPSIT LANGUAGE ENGINEERING, S.L. con la finalidad de gestionar la relación con nuestros clientes y contactos en relación al ejercicio de nuestra actividad. Todo ello bajo la legitimación otorgada por consentimiento expreso del propio interesado, y/o en base a la ejecución de un contrato de servicios. No se cederán datos a terceros salvo obligaciones legales. En cuanto a sus derechos podrá acceder, rectificar y suprimir los datos, limitarlos o incluso oponerse a su tratamiento, entre otros derechos, contactando con nosotros por email o por correo postal dirigido a Avenida UNIVERSIDAD, S/N, PCUMH-EDIF.QUORUM III, CP 03202 Elx/Elche, Alicante.

> El 12 jul 2019, a les 11:06, Jaume Ortolà <notifications@github.com> va escriure:
>
> Per a evitar aquests merge, que no aporten res i maregen una mica, em sembla que cal fer "git pull --rebase" en comptes de "git pull". És així? @xavivars <https://github.com/xavivars>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <https://github.com/apertium/apertium-spa-cat/commit/b9e9e6a49267042137746cddaff0ceb16acac3f6?email_source=notifications&email_token=AHXCWNLDF5T6ZJXHOET5BDDP7BCRPA5CNFSM4ICFKLSKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAWEDZ#commitcomment-34279545>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHXCWNNEB4FMRLIRHWUL7J3P7BCRPANCNFSM4ICFKLSA>.
>


I prefer the coffee version


@DiegoPino sorry, not clear to me here: does filename include "node:" ? or e need "node_" ?


Wonder if a PR introduces a CRD we should require a plan on how it gets cleaned up / garbage collected


@bran0 By removing support for mouse and touch events you break compatibility with Safari, iOS Safari, Opera Mini and Firefox for Android. Please see this: https://caniuse.com/#search=pointer%20events


ah just seen that below -  ignore ;)


One can only dream
On 12 Jul 2019, 10:30 +0100, Jamie Parkinson <notifications@github.com>, wrote:
> I prefer the coffee version
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.


_datetime is not needed -> can be removed


Attached nodes must be modified only in command action. It's [issue in itself](https://github.com/JetBrains/MPS/blob/77b4f33bc26f4523569ee02194a87181a204d45c/core/kernel/source/jetbrains/mps/smodel/AttachedNodeOwner.java#L84). That's why `executeCommand`. As for comment, I should've deleted it


That is because you don't declare `this.dom`.

If at the end of the consturctor method you do

```
this.dom = this.imgMenu
```

Then it ONLY shows the menu buttons (and not the figure).  So you'll basically have to create the HTML of the figure node as well there. See http://prosemirror.net/docs/ref/#view.NodeView


cheers @zzen


nice,  was thinking on this one.  It will fill up bigbuff fast but its nice to have a trace log regardless.
PR?


The warning only happen in release/optimized builds. It's possibly only so noisy with clang.


What does the datasheet say about it?  Should it NACK or not?


@Tylerwbrown

- It isn't necessary to overload `checkIfTimeInRange` with a signature that takes a Predicate or a long stream. There should only be two: one that takes a single `long` (timestamp) and another that takes two `long`s (start, end)
- Use the primitive `long` over `Long` where possible
- The block's id shouldn't be used to determine anything about the contents of the block

The purpose of the method proposed in CON-616 is to test whether a timestamp or range of timestamps is covered by the revisions in a Block. Every Revision is associated with a timestamp. So, the return value of the method's you're adding should be based on the smallest and largest revision timestamps.

These methods will be used to speed of historical querying. For instance, if a query is looking to select data for record n at timestamp x, these methods can be used by the Database to test whether the block even has data that covers timestamp x

Also, I'd prefer to call this method something like `covers` instead of `checkTimeInRange` because its more fluent an semantic


I think I'm getting a bit confused here... it looks like we're renaming $element to $jqElement (which I'm assumig stands for 'jQuery Element'), but we've changed the logic to pass HTML rather than a jQuery object?


revise comment


Successfully aliased the URL <https://web-4tw3f9mqv.now.sh> to the following aliases:

* https://stardev.co
* https://web.stardev.now.sh
* https://web-git-master.stardev.now.sh


Successfully aliased the URL <https://nextjs-green-5wj8gdilb.now.sh> to the following aliases:

* https://nextjs-green.now.sh
* https://nextjs-green.ftandcompany.now.sh
* https://nextjs-green-git-master.ftandcompany.now.sh


Successfully aliased the URL <https://backend-qdc8vgd01.now.sh> to the following aliases:

* https://api.stardev.co
* https://backend.stardev.now.sh
* https://backend-git-master.stardev.now.sh


@bran0 This is not datetime - but differential time (as stated in the XML comments).
We need to set X, Y by default.
In case there is force touch, we additionally need to set F.
In case there is a pen in a browser with PointerEvent support we need to additionally set TX and TY  and if available rotation (twist).
In case there is a iPad pen (iOS, Safari) we need to set azimuth, elevation and if available rotation (twist).


@DiegoPino Great!


Can we just exclude them by namespace in .rsp file?


ほほう


is not 0.6.2 for release ?


Successfully aliased the URL <https://class101-dev-mz8weity4.class101.dev> to the following aliases:

* https://class101-dev.class101.dev
* https://class101-dev-git-master.class101.dev


[](url)


靠，搞个混淆之后的代码来开源


@bran0 DT is not datetime but differential time (e.g. if every 1/50 second, there is a point measured, it would be 50 Hz). DT can be ignored because we use absolute time (T). Only one time measurement method is needed.


Hi,
I search on this folder:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions
But i don't find  this dll: Microsoft.Dynamics.AX.Metadata.Core.dll.


how #dispose is invoked multiple times?


Actually, Dao should be responsible for generating product ids. So, as long as we have only one modification method here, I propose to implement it this way:
- if product.id is null then we're saving a new item, so we need to generate a new unique id (implement counter/smth like that), set it to a product and add the product to the list
- otherwise, we're trying to update a product, so instead of adding it to the list we need to replace the existing product having the same id


could 'extends' be replaced with composition?


2時間かかった


Somehow the changes in sources/nix/misc/__cpucheck.c got lost in your merge. The #ifdef __HAVE_68881__ part is missing. So FPU-checking does not work at all.
The file should look as follows:

`#include "bases.h"
#include "stabs.h"

#if defined(mc68020) || defined(__HAVE_68881__)

asm(
"       .text;"
"       .even;"

"       .globl  ___cpucheck;"
"___cpucheck:;"
"       movel   "A4(_SysBase)",a1;"
"       movew   a1@(0x128:W),d0;"

#ifdef mc68020

"       move.l  #0x68020,d1;"
"       btst    #1,d0;"
"       jeq     error;"

#endif
#ifdef __HAVE_68881__

"       move.l  #0x68881,d1;"
"       btst    #4,d0;"
"       jeq     error;"

#endif

"       rts;"
"error:"

"   move.l  a1,a6;"
"   move.l  d1,d7;"
"   jsr -0x6c(a6);"
"       pea     20:W;"
"       jsr     _exit;"         /* dito */
);

ADD2INIT(__cpucheck,-80); /* Highest priority */

#else

void __cpucheck(){}

#endif
~   `


these suites crash on tests discovery step - I didn't look why yet, but `-nonamespace` won't help.


@bran0 Please revert those changes and support all kind of event types and import code from here to support measuring the right data from all devices and browsers: https://patrickhlauke.github.io/touch/tracker/scripts/multi-touch-tracker-pointer-hud.js