text:
Dates are hard-coded in project report generation

https://github.com/tbpmig/mig-website/blob/9a453ebcb8394d1189d138ef8de639aaa81b5b7f/history/models.py#L99
Please consider making this dynamic (and for now changing the dates on the deployed copy since Elvhin is generating the report)

Deadline?
On Fri, Jun 8, 2018 at 2:57 PM pritpaul notifications@github.com wrote:

https://github.com/tbpmig/mig-website/blob/9a453ebcb8394d1189d138ef8de639aaa81b5b7f/history/models.py#L99
Please consider making this dynamic (and for now changing the dates on the
deployed copy since Elvhin is generating the report)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tbpmig/mig-website/issues/236, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKVBKLbJ9HuRTGxa6Jx7TX3TAJ-S_syks5t6skvgaJpZM4UgzIA
.

--
Mike Hand

"well if it could be fixed by the end of the weekend, that would be great! It's due in a week, but I could use the leeway."
Changing the hard-coded text would cover that IMO, automatic is just nice to have for the future.

Fixed

Thanks!  I like the elegant solution :)  Is it deployed on the live site? @kylelady

authors: mikehand pritpaul

repo: tbpmig/mig-website


text:
node.js resolver may arbitrarily remap modules to different sources

node has loaders which can arbitrarily redirect module resolution, which could then fail these checks. Since this isn't part of node's security model anyway, should this proposal just be optional for hosts to enforce?

Hosts are always free to not, but it would mean the developer will not be able to rely on these checks (which is what this proposal is about). On the other hand it might be wanted during tests.

Are file types resolved before or after remapping?

@littledan after. asking for ./config.json might be turned into /tmp/config_wrapper.mjs

which could then fail these checks.

That's the whole point of the checks. If I have an Node application that loads JSON over the network, I want to assert that it's actually JSON and not script that could do anything to the user's machine.

@justinfagnani your local code is doing the remapping. if a loader is loaded it can just exfiltrate your harddrive using fs and http. no need to hack your json imports.

Coming back to @devsnek 's original point:

should this proposal just be optional for hosts to enforce?

I'd like to conclude: yes. While all hosts are required to support JSON modules using with type: "json", this proposal doesn't prohibit hosts from also exposing other kinds of JSON modules.
Is this sufficient to close the issue, or are there further aspects to discuss?

I'm closing this issue, per https://github.com/tc39/proposal-import-attributes/issues/4#issuecomment-631434268. Hosts are free to provide JSON imports without the attributes that indicates that it must be actually JSON.
Please reopen in https://github.com/tc39/proposal-json-modules if you'd prefer to continue the discussion.

source: gharchive/issue

authors: devsnek justinfagnani littledan nicolo-ribaudo xtuc

license_type: permissive

license_source: github-api


text:
Short-circuiting concerns

(raised by @bakkot in the meeting today)
Currently, every assignment combo operator in JS can be described as a = a <op> b being equivalent to a <op>= b.
Including the short-circuiting semantics would make a = a <op> b equivalent to if (a) { a = a <op> b; }, which is a very large inconsistency.
The argument that "Ruby and CoffeeScript have these semantics" imo does not hold its weight compared to "it would be inconsistent with the rest of JS".

The pedant in me is compelled to note that in cases where evaluating the LHS is observable the sugar is a little more complicated because you need to avoid triggering the side effects multiple times (though most implementations get it wrong, and do in fact trigger a subset of the side effects several times). No one should care about this, though.

Ruby and CoffeeScript have these semantics

On this, both Ruby and CoffeeScript have mathematical operators that always assign, and logical operators that short-circuit assign.

it would be inconsistent with the rest of JS

Meaning the mathematical assignment operators? but none of them could ever have short circuiting semantics.
I think the better argument for always-set semantics path is that it's closer to (my personal intuition) the common de-sugared form (a = a || b). But, I'm pretty sure this is the common because the short-circuit-set semantics is usually a lint error (useless expression).
But, I'm open to either semantics.

where evaluating the LHS is observable the sugar is a little more complicated because you need to avoid triggering the side effects multiple times

This is separate from short-circuiting semantics, but I intend for this to follow whatever the rest of the spec uses, which I hope accounts for deep properties and computed keys.
obj.a.b ||= 'test';
(_a = obj.a).b || (_a.b = 'test');

obj.a[key++] ||= 'test';
(_a = obj.a)[_key = key++] || (_a[_key] = 'test');

Sorry to comment here late and long.  But I am not so familiar with the background of the JS spec and who is allowed to express thoughts here.  And please forgive if this is a FAQ, I do not know where and how to look for such.
However I'd always vote for the most performant way to implement things if this does not break mathematical correctness.  This also means, to allow engines to skip calls to setters if those calls look invariant (which might not necessarily be procedurally correct then) to the value.
So my idea is to turn it around and allow shortcuts like in the ||= case to be allowed in the += case, too!
a += b is internally done by somethings like var _=a; _=_+b;  a=_ so I'd vote that engines are allowed to optimize that to
var _ = a
_ = _ + b
if (_ !== a) a = _    // optionally spare the if() and do a = _ here

which skips calls to the setter if nothing changes.  (Note that this should not be imperative, because there will be many cases where calling the setter is more performant than implementing the identity check.  And I am talking about performance here.).  Now a ||= b flies just the same route:
var _ = a
_ = _ || b;
if (_ !== a) a = _

which effectively is
if (!a) a = b;

To keep the idea that a = a <op> b should be the expanded form of a <op>= b, this means, that it should be allowed to skip the assignment (=setter) if the (known) value is unchanged.
The motivation behind this is that setters should do the obvious thing.  Storing the same value multiple times or only store it a single time should not catastrophically change things from a stability point of view.  (Also getters should never return a value different from what setter expect to set the value returned by the getter again.)  On JS this might break some constructs of Observables, which use such a bad approach to enforce some UI updates/refreshes.  However for this a clear call to something like a.refresh() or a.refresh++ or a.refresh_trigger = !a.refresh_trigger should be a far superior approach, as this creates clear and concise code which everybody can understand out of the box.
Note:

I am not into JS spec, so perhaps this is a fundamental change in some principles there.  But a good language should be allowed to optimize for performance (as long as this does not break some very imperative other things which cannot be expressed otherwise).  And adding some internal assumptions on how getters/setters should be implemented, is not a bad thing.

Statically compiled languages like C are not a good choice to compare here.  The C++ compiler has a good way to examine (inline) the getters/setters at compile time and optimize that.  However JS is an interpreted language where everything can change on runtime, so it shall have other ways of optimization, possibly sacrificing some constraints on how side-effects must be handled in-detail, especially if those side-effects are not obvious to the common programmer anyway and hinder performance and generalization a lot.

Also the C++-optimization is, strictly speaking, not free from side-effects, as at assembly level the "add"-instruction is optimized away which can change behavior of a program.  This could make differences on things like Spectre and the like.  Hence there always is some tradeoff between speed and compliance, where I always go for speed, as long as the pure mathematical result stays correct.

Compare:

Spectre is not a bug from my perspective, it's just a side-effect of a speed feature which only has some possibly bad side-effects in certain few and from my perspective very negligible situations.  So yes, Spectre has an impact on Cloud setups, but you always needed to be aware of side-channels on things like this, so you had to harden your code.  This already was true in the last millennium with non-speculating processors (you were able to measure the power consumption to detect things you are not supposed to access, and there were even exploits known using sound cards to record things like password keystrokes).  This is comparable to the shortcut taken here.  Yes, it might break some existing code.  But only bad code which relies on side-effects, which are not obvious to everybody, and this creates very hard do maintain code and should be changed anyway.

In contrast, Meltdown and SWAPGS are bugs, because both have a vast impact on kernel security guarantees.  But I cannot see any similar bad thing happen here if you allow shortcuts for += as expressed above.  The vast majority of sane code should continue to work completely unharmed, regardless of minified or not.

But what if I want to have:
let hasErrors = testForSomeErrors(foo, logger);
hasErrors = testForOtherErrors(foo, logger) || hasErrors;

So that testForOtherErrors() is also executed, even if testForSomeErrors() already detected some errors, so that the other errors are also logged.

But I am not so familiar with the background of the JS spec

@hilbix For information, the current state of the spec is: Implementation are allowed to do any optimisation provided that it does not change the observable behaviour, which is probably much more restrictive of what you want. Number of wasted CPU cycles does not count of observable; but observable side-effects not related to time and memory do count.
If you want to allow implementations to do more optimisations, that might change the observable behaviour in edge cases, this is not the place to propose it, because it is a major change in the language semantics. See https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md#new-feature-proposals for places where you can express your ideas (the es-discuss mailing list is one place to discuss them). (Although I am personally sceptical that this particular idea will fly , because the tendency is to reduce observable variations between implementation.)

I disagree with this argument:

Currently, every assignment combo operator in JS can be described as a = a <op> b being equivalent to a <op>= b.
Including the short-circuiting semantics would make a = a <op> b equivalent to if (a) { a = a <op> b; }, which is a very large inconsistency.

for the simple reason that descriptions like “a = a <op> b is equivalent to a <op>= b” are willingly incorrect for the sake of simplicity. You already know that you must add: “(except that, of course, a is not evaluated twice)”; now you just need to add: “(and except that, of course, in case of short-circuiting, the value just read in a is not re-written in a)”; there is no need to resort to some alternative (incorrect) expansion such as if (a) { a = a <op> b; }.
In fact, if we look at real semantics instead of simplistic expansions, there is absolute consistency. Here is a synoptic view of the differences of semantics between a + b, a += b, a || b and a =|| b:

<OP>
a <OP> b
a <OP>= b

non short-circuiting operator (e.g., +)

assign the final result to a

short-circuiting operator (e.g., ||)
possibly skip the rest of the algorithm (short-circuit)
possibly skip the rest of the algorithm (short-circuit)assign  the final result to a

The question is whether the “assign the final result to a” step is part of the algorithm that is possibly short-circuited. I say: yes, of course, because the goal of short-circuiting is precisely to avoid operations that are useless in “regular” cases (i.e., assuming that evaluating subexpressions does not trigger observable side-effects, assuming that re-writing the same value just read in some binding is a no-op, and other whatnots)
Concretely, the only case where the difference is observable, is when assignment does something weird or perform some non-trivial work. E.g.
previewElement.innerHTML ||= '<i>Nothing to show</i>'

In that specific case—and I expect in most cases—you most probably don’t want to trigger the .innerHTML setter, as it could have unwanted side-effects (such as the user loosing the focus in case it was on some child element of previewElement). If, for some obscure reason, you do want to always trigger the .innerHTML setter, you’d better be more explicit.

@claudepache The el.innerHTML ||= 'default' is a great example. Want to add it to the readme?

"a = a <op> b being equivalent to a <op>= b" may be too simple, but I feel it reflect the mental model of most programmers.
The problem is, when programmers see a ||= b, will they consider short-circuiting semantic first?

If, for some obscure reason, you do want to always trigger the .innerHTML setter, you’d better be more explicit.

We could also say, if you do not want to trigger the setter, you'd better be more explicit --- write if (el.innerHTML) el.innerHTML = ....
In which direction more explicit is better choice? I don't know.
Some programmers think <op>= as a shorthand, and the doc of ESLint operator-assignment rule said:

Use of operator assignment shorthand is a stylistic choice. Leaving this rule turned off would allow developers to choose which style is more readable on a case-by-case basis.

Whichever we choose, it's not a stylistic choice anymore.
So the most conservative teams might even choose enforcing explicit for both directions, aka. disallow logical assignment operators (via eslint).
Note, actually I will choose current short-circuiting semantic if I'm forced to choose one. Just feel it's really an issue if the feature is added while a lint rule is also added to forbid it 🤓

Whichever we choose, it's not a stylistic choice anymore.

So the most conservative teams might even choose enforcing explicit for both directions, aka. disallow logical assignment operators (via eslint).

This.

Some programmers think <op>= as a shorthand, and the doc of ESLint operator-assignment rule said:

Use of operator assignment shorthand is a stylistic choice. Leaving this rule turned off would allow developers to choose which style is more readable on a case-by-case basis.

Whichever we choose, it's not a stylistic choice anymore.

The doc of ESLint can continue to lie, and say that a ||= b is equivalent to a = a || b. In most cases, skipping a = a makes zero differences. In few cases, it makes a small difference, but it is sufficiently subtle for most coders not to care.
In rare cases it makes a noticeable difference, and:

even in those cases, skipping the self-assignment is probably the most secure choice;
programmers that do care of the difference will also care to understand correctly the code.

programmers that do care of the difference will also care to understand correctly the code.

I’ve seen far too much horrible, buggy code in my life that this sadly feels very unlikely to me.

If a language is created for programmers who do not care, then the language will not take care of the programmers who do care.

Having spoken to some friends on the C# team, I found out that they've also picked the behavior of short-circuiting the assignment (a ??= b -> a ?? (a = b)) rather than performing unconditional assignment (a ??= b -> a = a ?? b). I think that in this case, regardless of whatever I would find preferable, the advantages either way are probably marginal and it makes more sense to drive towards consistency with other languages.

Excellent, thank you for reaching out to them!

As a library developer, how can I inform users that ||= is absolutely prohibited for some objects?
As a library user, how can I find out whether it is safe to call ||=?

There will be much user overhead to know that
transaction.currency = transaction.currency || CURRENCY_EURO; works as expected, but
transaction.currency ||= CURRENCY_EURO; will cause numerous hard to track bugs, and bypass functionality.
The primary difference:
One must pre-verify whether the assigned property is going through a setter or not.
This implies that users need to dig into third-party library code to know internal details.
Any use of the ||= operator, on an object property must now be researched.
// Heavily simplifed example from a library

const transaction = {
  _currency: 0,
  get currency() {
    return this._currency;
  },
  set currency(val) {
    if (val !== this._currency) {
       // Trigger a cancellable event, that may override the change
       console.log(`.dispatch(CURRENCY_CHANGE_EVENT, {old: this._currency, new: val);`);
    }
    this._currency = val;
    // Trigger a non-cancellable event, used for mandatory code auditing, invoking third-party libraries and other service integrations.
    console.log(`.dispatch(CURRENCY_SET_EVENT, {val: val);`);
  }
};

const CURRENCY_EURO = 978;
transaction.currency = transaction.currency || CURRENCY_EURO;
// .dispatch(CURRENCY_CHANGE_EVENT, {old: 0, new: 978);
// .dispatch(CURRENCY_SET_EVENT, {val: 978);

transaction.currency = transaction.currency || CURRENCY_EURO;
// .dispatch(CURRENCY_SET_EVENT, {val: 978);

transaction.currency ||= CURRENCY_EURO;
// .dispatch(CURRENCY_CHANGE_EVENT, {old: 0, new: 978);
// .dispatch(CURRENCY_SET_EVENT, {val: 978);
transaction.currency ||= CURRENCY_EURO;
/*
 * Auditor is not executed.
 * Region based runtime added third-party module, data is not yet synced, currency is not set.
 * Mandatory attempted change of information process is not executed.
 *
 */

```

That’s already something you have to know - i can already always check a property’s value before conditionally setting it.

@icywolfy I think part of the confusion stems from the fact that all existing assignment combo operates are effectively written backwards, += instead of =+. Expandinga += b requires one to place the equals before the plus a = a + b.
On the other hand the new logical assignment operators are written in order. a ||= b expands to a || (a = b).
If you need to log/report when transaction.currency ||= CURRENCY_EURO; is run even if the currency never changed you should be logging in the getter.
Also I wouldn't be comparing this to assignment combo operators. Thearetically the language could support prepending && to other operators besides for the equals operater. (The same would apply a non nullish operator if it is added in the future.)
For example:
a &&*= b expands to a && (a *= b)
a &&-= b expands to a && (a -= b)
a&&++ expands to a && a++
&&++a expands to a && ++a
etc.
There is obviously less demand for these shorthand operators, but they bring out the point that this has different semantics than assignment combo operators.

(raised by @bakkot in the meeting today)
Currently, every assignment combo operator in JS can be described as a = a <op> b being equivalent to a <op>= b.
Including the short-circuiting semantics would make a = a <op> b equivalent to if (a) { a = a <op> b; }, which is a very large inconsistency.
The argument that "Ruby and CoffeeScript have these semantics" imo does not hold its weight compared to "it would be inconsistent with the rest of JS".

As a person who was on that side of the fence, I'd just like to raise:

Combing through our own codebase, practically all of the code that we've written prior to this feature actually uses the conditional set (even though it is likely never observable). We actually have many instances of this for lazy assignment. Ideally, a naive refactoring should preserve that behavior.
C#, Ruby, and CoffeeScript all have the same difference in behaviors, and as far as I can tell it's been just fine in over a decade of support (Ruby has had it well before 2008, and C# just shipped with the same behavior). Making it inconsistent with the rest of the programming ecosystem is ignoring the cowpath and actually adds potential to surprise a user coming from another language.

authors: DanielRosenwasser ExE-Boss Mouvedia arye-dov-eidelman asktheworld bakkot claudepache hax hilbix icywolfy jridgewell ljharb

license: MIT


text:
how did you convert the "Arcticons Thin Line Icons pack" to "d="

i want to add some custom vector for the website but i seem to get these files as
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48"><defs><style>.a{fill:none;stroke:#000;stroke-linecap:round;stroke-linejoin:round;}</style></defs><circle class="a" cx="24" cy="24" r="9.44"/><circle class="a" cx="9.53" cy="24" r="5.03"/><circle class="a" cx="38.47" cy="24" r="5.03"/></svg>
not a data "d=" string, how did you do it?

Hi and sorry for the (very) late answer, i don't now what you're using to create svg icons, i like to use Heroicon / Heroicon (dev / Bootstrap i can just recomend using these to help you ..

authors: makuru-dd tchartron

repo: tchartron/blow


text:
🛑 SciOly-ID is down

In f1aadad, SciOly-ID (https://sciolyid.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SciOly-ID is back up in 418fe27.


text:
🛑 Personal Site is down

In afb93fe, Personal Site (https://tomichen.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Personal Site is back up in f7cdcb3.


text:
[question] About line break, I found a case that seems to be a bug

Hi tdewolff, recently when I was using canvas, I found a line break case that might not be as expected, demo like this:
package main

import (
	"github.com/tdewolff/canvas"
	"github.com/tdewolff/canvas/renderers"
)

func main() {
	fontLatin := canvas.NewFontFamily("latin")
	if err := fontLatin.LoadFontFile("Arial.ttf", canvas.FontRegular); err != nil {
		panic(err)
	}
	face := fontLatin.Face(30, canvas.Black, canvas.FontRegular, canvas.FontNormal)

	W := 500.0
	H := 500.0

	c := canvas.New(W, H)
	ctx := canvas.NewContext(c)
	ctx.SetFillColor(canvas.White)
	ctx.DrawPath(0, 0, canvas.Rectangle(W, H))

	ctx.SetCoordSystem(canvas.CartesianIV)

	// Note: text "", " " or any text that match "^/s*$" will cause panic
	txt := canvas.NewTextBox(face, "+++++++++++ HelloWorld", 100, 0, canvas.Left, canvas.Top, 0, 0)
	ctx.DrawText(0, 0, txt)
	renderers.Write("test.png", c, canvas.DPMM(2.0))
}

we can see that when textbox's width can't include "+++++++++++ HelloWorld", so it cause line break like below, this is what we expected:

but when we replace "+" to space, text become "            HelloWorld", now the result is:

so why in second case, HelloWorld doesn't break into a new line?  is it a bug?

LOL, you are right, thanks for reply!

repo: tdewolff/canvas


text:
Clear unread messages on init

Is possible to clear all the unread messages on init?
In my application I have to avoid to read old messages.

No. There is no way to read all unread messages.

I dont want to read. I want to clear and ignore them. And from this point, read new messages.

If you mistakingly name "old" messages as "unread", then this is possible only if all databases are disabled and "ignore_background_updates" option is enabled by a call to setOption before setTdlibParameters.

Sometimes I close the application and when I start there are a lot of messages unread. So I have to ignore.

It is possible to mark unread messages as read only by viewing them.

If you mistakingly name "old" messages as "unread", then this is possible only if all databases are disabled and "ignore_background_updates" option is enabled by a call to setOption before setTdlibParameters.

How do I disable all the databases?
Will I lose the authorization if I close and open the application when the database are disabled?

Databases settings are passed in setTdlibParameters.

authors: levlam vinifr

repo: tdlib/td


text:
🛑 drop.chapril.org is down

In ba913b0, drop.chapril.org (https://drop.chapril.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: drop.chapril.org is back up in 6834f4a after 33 minutes.

repo: tdulcet/send-instances-status


text:
Adjust frequency of fetching schedulers

Fetch new blogs two times a day (e.g. 9 am and 9 pm, generally any hour not clashing with 12 o'clock when mailing is sent is good)
Fetch new blog posts every 6 hours.

I will try to add this feature.

authors: jborkowski tdziurko

repo: tdziurko/jvm-bloggers

license: mit

license_source: bigquery


text:
Fallback to using the node address when service address not defined

This mirrors consul's dns behaviour. See here for more information.

Hey @mattmatters,
That's cool! Thanks.

Hey @balena!
No problem, thanks for writing such a useful library!

source: gharchive/pull-request

authors: balena mattmatters


text:
Expand selenium.Display to accept screen numbers.

Previously, if you ran a single Xvfb display with multiple screens, you
couldn't pass them to selenium.Display because it would fail on the
input "x.y", which is a perfectly valid $DISPLAY value. See [1] for more
information.
[1] https://docstore.mik.ua/orelly/unix3/upt/ch35_08.htm

Codecov Report

Merging #110 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #110      +/-   ##
=========================================
- Coverage    0.31%   0.31%   -0.01%
=========================================
  Files           4       4
  Lines         946     954       +8
=========================================
  Hits            3       3
- Misses        943     951       +8

Impacted Files
Coverage Δ

service.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3ab953b...4e88b6a. Read the comment docs.

Thanks!

authors: bcspragu codecov-io minusnine

repo: tebeka/selenium


text:
Move Windows instructions to README

I think it best to unify the setup instructions location and format. What do you think, @gailweiss?

tomorrow someone else will tell me the separate windows file was nicer, and i dont want to start thinking seriously about such things, so: arbitrary first decision = best decision :)

authors: emileferreira gailweiss

repo: tech-srl/RASP


text:
Standardized inconsistencies in forms of address

Hi @mvbrooks! #33
I've edited the Spanish translation to fix inconsistencies with forms of address and made the necessary changes to the sentences around those, and have also made some text edits: some necessary (wrong URL for tenantprotections.org) and some to improve the style in Spanish.
I hope this is useful!
Small request: I'm taking part in this year's Hacktoberfest, so it would be great if you could add the hacktoberfest-accepted label to the repo so it counts towards it 😊
Edit: to link to issue #

Hi @Carababusha thanks so much for the contribution! Label added. If you're willing to do one more pass through it before we publish, we'll likely be adding a few more paragraphs in the next few weeks.

Absolutely, @mvbrooks! It'll be a pleasure to give the new paragraphs a once over whenever they are ready for review ☺
And thanks very much for adding the label!

authors: Carababusha mvbrooks


text:
bugs in invoice

[x] we have to click mark as sent button two times for functioning
[x] while doing record payment , it showing error message

[x] validation message is wrong under bank charges field
[x] remove sales return under - approval ,rejected status
[x] sales person & item is not populating in edit page

issue closed

repo: techgebra/polosys-books-mobile

license: Unlicense


text:
Design tokens / Theme support (with dark mode)

Setup svelte-ux as a locally linked dependency
Setup daisy theme variables and theme selection via Svelte UX's ThemeButton

Current dependencies on/for this PR:

main

PR #78   👈

This stack of pull requests is managed by Graphite.

repo: techniq/layerchart


text:
Improvements/Suggestions

Hello!
Thanks for the wonderful docker app!
Can we seperate the Environment variables to a seperate file? Currently it clutters up the docker-compose file with settings not really related to server configuration. It also does not make any sense if you plan to add more supported services.
Also can we have the option to rearrange the links? And to add custom links as well for advanced users as well?
i could propose a yml configuration file something like this (ps: github doesnt support uploading of yml files.):
sample.yml.txt

Hey, thanks for the suggestions.  These are related to the server configuration since it is server side rendered and needs to modify the output.  Unfortunately I do not plan on changing the API in a breaking way and time soon unless there is a good reason too.  There's also a lot of mapping that would also have to change.  Sorting links is already planned https://github.com/techno-tim/littlelink-server/issues/2

Okay, although you might say it relates to server configuration, i would think of it as content management of the website. I was referring to more docker related settings like port, timezone, password, etc, in the docker-compose file than website links content management. Using a seperate file for links can allow the expandability to add custom links. :) It could also be a json file where it is possible for the website to read from :)

You can put the environment variables in a separate file with
env_file:
      - variables.env

repo: techno-tim/littlelink-server


text:
Fixed potencial issue with commnds when one of the device is locked

Fixed potencial issue in sending a commands if a device is locked.
ps: Is there any reason to loop on all devices in the network when you have an IP adress as input? You could just do broadlink.hello(ip_adress)

Thank you!

repo: techno-tim/techno-broadlink


text:
HIGH registration not possible

Background: Why this issue?
-I wanted to register to fill in how much water I gave to which trees.
Klicking on the registration button always brings you to the project description on Browser. On mobile device it brings you back to the map. No registration possible.
One time I came through to the registration side (safari), filled out the form and nothing happened when I sent the form.
Deliverables: How to fix the issue?
-relink the registration or fix the registration itself.
Output: Gain of fixing the issue?
-registration for new waterers :)
Issue creation checklist

[x] I have attached one of the priority labels HIGH, MIDDLE, LOW
[x] I have attached other labels with regard to the issues purpose (i.e.enhancement, bug, community feedback)

Hi @offtaste ! Thank you for reporting this bug. We are looking into it. Could you please provide us more information about which OS and browser (and version) you are using, so we can try to reproduce the Bug? Cheers ☮

@offtaste we have fixed some bugs related to authentication and it might have also solved your issues. Please let me know if you keep experiencing issues. I'll close this ticket for now.

authors: offtaste vogelino

repo: technologiestiftung/giessdenkiez-de


text:
🛑 Sklep Y2M is down

In 3e5fb8d, Sklep Y2M (https://sklep.yes2move.com) was down:

HTTP code: 503
Response time: 452 ms

Resolved: Sklep Y2M is back up in e574d06.

repo: techsupp/uptime


text:
Command key always pressed

First, thanks for a great product and apologies for a rather vague possible bug report.
Sometimes when my computer wakes up from sleep, it behaves as if the left command key is always pressed, with corresponding behavior. For instance, every link clicked on a web page opens in a new window. The only way to fix this is to restart the computer. I think this has not happened when I haven't used Karabiner Elements.
Is there any way of providing a manual "keyboard reset" command or similar? Alternatively call that automatically after waking up from sleep or starting the app?

Have to confirm that this is Karabiner issue. Just updated from 0.91.5 to 0.91.6 and had the same problem immediately and it took me a while to understand why every app behaves so weird. Rebooted once and the cmd key isn't pressed anymore.
Also: Thanks for this great app! 👍

I have the same problem, but in my case it is not a command key but OS behaves as if a shift key is being pressed down.
I use macOS 10.12.5 (MacBook Pro (Retina, 15-inch, Mid 2014)) and Karabiner-Elements 0.91.6. I hope some information below is helpful for debugging.

My Settings

Quitting Karabiner-Elements immediately resolves the issue, that's why I believe this is a Karabiner-Elements issue.

I have never seen this problem with 0.91.5.

It looks to appear only after waking up from sleep.

I have checked key events by Karabiner-EventViewer. Pressing the left shift key properly shows event types "FlagsChanged 0x38 left_shift Shift" and "FlagsChanged 0x38 left_shift" sequentially.

In all applications, they behave as if a shift key is being pressed down, but in Japanese IME, I can type hiragana (pressing the left shift key usually changes the typed hiragana to katakana). So it is puzzling.

Same problem for me in 0.91.6. The letter A is being pressed down after MacBook wakes up from sleep.
In EventViewer, it just shows a constant stream of letter A KeyDown.
I quitted Karabiner-Elements once, the problem still remains. Then I reopened and quitted Karabiner-Elements again, the problem suddenly goes away.

I'm getting the same thing in 0.91.7.
It's happened 3 times since it started a couple days ago. If I open EventViewer and mash all the keyboard keys randomly (because desparation), it stops.
I don't see any errors in the logs; just warnings:
[2017-07-13 21:15:47.511] [info] [console_user_server] core_configuration is updated.
[2017-07-13 21:15:47.511] [info] [console_user_server] Check for updates...
[2017-07-13 21:15:47.513] [info] [grabber] event_tap_manager initialized
[2017-07-13 21:15:47.513] [info] [grabber] Load karabiner.json...
[2017-07-13 21:15:47.513] [info] [grabber] core_configuration is updated.
[2017-07-13 21:15:47.514] [info] [grabber] initialize_virtual_hid_keyboard
[2017-07-13 21:15:47.514] [info] [grabber]   keyboard_type:40
[2017-07-13 21:15:47.514] [info] [grabber]   caps_lock_delay_milliseconds:0
[2017-07-13 21:15:47.514] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is ignored.
[2017-07-13 21:15:47.514] [warning] [grabber] virtual_hid_keyboard is not ready. Please wait for a while.
[2017-07-13 21:15:47.515] [info] [grabber] matching device:
[2017-07-13 21:15:47.516] [info] [grabber]   manufacturer: pqrs.org
[2017-07-13 21:15:47.516] [info] [grabber]   product: Karabiner VirtualHIDKeyboard
[2017-07-13 21:15:47.516] [info] [grabber]   vendor_id: 0x0
[2017-07-13 21:15:47.516] [info] [grabber]   product_id: 0x0
[2017-07-13 21:15:47.516] [info] [grabber]   location_id: 0x0
[2017-07-13 21:15:47.516] [info] [grabber]   serial_number: org.pqrs.driver.Karabiner.VirtualHIDDevice.VirtualHIDKeyboard
[2017-07-13 21:15:47.516] [info] [grabber]   registry_entry_id: 4294982545
[2017-07-13 21:15:47.519] [info] [grabber] Karabiner VirtualHIDKeyboard (device_id:3) is detected.
[2017-07-13 21:15:47.519] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is ignored.
[2017-07-13 21:15:47.669] [info] [console_user_server] frontmost_application_observer initialize
[2017-07-13 21:15:48.579] [info] [console_user_server] system_preferences::values is updated.
[2017-07-13 21:15:48.580] [info] [grabber] system_preferences_values_updated
[2017-07-13 21:15:48.580] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is grabbed
[2017-07-13 21:16:35.847] [info] [console_user_server] the configuration directory is updated.
[2017-07-13 21:16:35.875] [info] [console_user_server] the configuration directory is updated.
[2017-07-13 21:16:35.875] [info] [console_user_server] Check version...
[2017-07-13 21:16:35.876] [info] [console_user_server] Version is changed: '0.91.6' -> '0.91.7'
[2017-07-13 21:16:35.993] [info] [console_user_server] version 0.91.7
[2017-07-13 21:16:35.994] [info] [console_user_server] Check version...
[2017-07-13 21:16:36.257] [info] [grabber] version 0.91.7
[2017-07-13 21:16:36.259] [info] [grabber] Check version...
[2017-07-13 21:16:36.439] [info] [grabber] IOServiceOpen is succeeded @ void krbn::virtual_hid_device_client::matched_callback(io_iterator_t)
[2017-07-13 21:16:36.472] [info] [grabber] matching device:
[2017-07-13 21:16:36.472] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-13 21:16:36.472] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-13 21:16:36.472] [info] [grabber]   vendor_id: 0x5ac
[2017-07-13 21:16:36.472] [info] [grabber]   product_id: 0x274
[2017-07-13 21:16:36.472] [info] [grabber]   location_id: 0x14400000
[2017-07-13 21:16:36.472] [info] [grabber]   serial_number: D3H52374NA1FTV4AA3FS
[2017-07-13 21:16:36.472] [info] [grabber]   registry_entry_id: 4294968105
[2017-07-13 21:16:36.473] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is detected.
[2017-07-13 21:16:36.474] [info] [grabber] matching device:
[2017-07-13 21:16:36.474] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-13 21:16:36.474] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-13 21:16:36.474] [info] [grabber]   vendor_id: 0x5ac
[2017-07-13 21:16:36.474] [info] [grabber]   product_id: 0x274
[2017-07-13 21:16:36.474] [info] [grabber]   location_id: 0x14400000
[2017-07-13 21:16:36.474] [info] [grabber]   serial_number: D3H52374NA1FTV4AA3FS
[2017-07-13 21:16:36.474] [info] [grabber]   registry_entry_id: 4294968109
[2017-07-13 21:16:36.475] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is detected.
[2017-07-13 21:16:37.540] [info] [grabber] current_console_user_id: 502
[2017-07-13 21:16:37.540] [info] [grabber] Check version...
[2017-07-13 21:16:46.220] [info] [console_user_server] version 0.91.7
[2017-07-13 21:16:46.220] [info] [console_user_server] Check version...
[2017-07-13 21:16:47.297] [info] [console_user_server] receiver is initialized
[2017-07-13 21:16:47.297] [info] [console_user_server] Check version...
[2017-07-13 21:16:47.298] [info] [grabber] karabiner_console_user_server is connected (pid:25066)
[2017-07-13 21:16:47.298] [info] [console_user_server] grabber_client_ is connected
[2017-07-13 21:16:47.298] [info] [console_user_server] Load karabiner.json...
[2017-07-13 21:16:47.298] [info] [console_user_server] core_configuration is updated.
[2017-07-13 21:16:47.298] [info] [console_user_server] Check for updates...
[2017-07-13 21:16:47.300] [info] [grabber] event_tap_manager initialized
[2017-07-13 21:16:47.300] [info] [grabber] Load karabiner.json...
[2017-07-13 21:16:47.301] [info] [grabber] core_configuration is updated.
[2017-07-13 21:16:47.301] [info] [grabber] initialize_virtual_hid_keyboard
[2017-07-13 21:16:47.301] [info] [grabber]   keyboard_type:40
[2017-07-13 21:16:47.301] [info] [grabber]   caps_lock_delay_milliseconds:0
[2017-07-13 21:16:47.302] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is ignored.
[2017-07-13 21:16:47.302] [warning] [grabber] virtual_hid_keyboard is not ready. Please wait for a while.
[2017-07-13 21:16:47.303] [info] [grabber] matching device:
[2017-07-13 21:16:47.303] [info] [grabber]   manufacturer: pqrs.org
[2017-07-13 21:16:47.303] [info] [grabber]   product: Karabiner VirtualHIDKeyboard
[2017-07-13 21:16:47.303] [info] [grabber]   vendor_id: 0x0
[2017-07-13 21:16:47.303] [info] [grabber]   product_id: 0x0
[2017-07-13 21:16:47.303] [info] [grabber]   location_id: 0x0
[2017-07-13 21:16:47.303] [info] [grabber]   serial_number: org.pqrs.driver.Karabiner.VirtualHIDDevice.VirtualHIDKeyboard
[2017-07-13 21:16:47.303] [info] [grabber]   registry_entry_id: 4294982605
[2017-07-13 21:16:47.305] [info] [grabber] Karabiner VirtualHIDKeyboard (device_id:3) is detected.
[2017-07-13 21:16:47.311] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is ignored.
[2017-07-13 21:16:47.425] [info] [console_user_server] frontmost_application_observer initialize
[2017-07-13 21:16:48.371] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is grabbed
[2017-07-13 21:16:48.373] [info] [grabber] system_preferences_values_updated
[2017-07-13 21:16:48.373] [info] [console_user_server] system_preferences::values is updated.
[2017-07-13 22:26:59.943] [info] [grabber] version 0.91.7
[2017-07-13 22:26:59.950] [info] [grabber] Check version...
[2017-07-13 22:27:00.170] [info] [grabber] IOServiceOpen is succeeded @ void krbn::virtual_hid_device_client::matched_callback(io_iterator_t)
[2017-07-13 22:27:00.175] [info] [grabber] matching device:
[2017-07-13 22:27:00.175] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-13 22:27:00.175] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-13 22:27:00.175] [info] [grabber]   vendor_id: 0x5ac
[2017-07-13 22:27:00.175] [info] [grabber]   product_id: 0x274
[2017-07-13 22:27:00.175] [info] [grabber]   location_id: 0x14400000
[2017-07-13 22:27:00.175] [info] [grabber]   serial_number: D3H52374NA1FTV4AA3FS
[2017-07-13 22:27:00.175] [info] [grabber]   registry_entry_id: 4294968109
[2017-07-13 22:27:00.175] [info] [console_user_server] connection_manager::grabber_is_launched_callback
[2017-07-13 22:27:00.175] [info] [console_user_server] frontmost_application_observer terminate
[2017-07-13 22:27:00.176] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is detected.
[2017-07-13 22:27:00.177] [info] [grabber] matching device:
[2017-07-13 22:27:00.177] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-13 22:27:00.177] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-13 22:27:00.177] [info] [grabber]   vendor_id: 0x5ac
[2017-07-13 22:27:00.177] [info] [grabber]   product_id: 0x274
[2017-07-13 22:27:00.177] [info] [grabber]   location_id: 0x14400000
[2017-07-13 22:27:00.177] [info] [grabber]   serial_number: D3H52374NA1FTV4AA3FS
[2017-07-13 22:27:00.177] [info] [grabber]   registry_entry_id: 4294968105
[2017-07-13 22:27:00.178] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is detected.
[2017-07-13 22:27:01.055] [info] [console_user_server] receiver is terminated
[2017-07-13 22:27:01.059] [warning] [console_user_server] bind: No such file or directory
[2017-07-13 22:27:01.178] [info] [grabber] current_console_user_id: 502
[2017-07-13 22:27:01.178] [info] [grabber] Check version...
[2017-07-13 22:27:01.812] [info] [grabber] karabiner_console_user_server is connected (pid:25066)
[2017-07-13 22:27:01.812] [info] [console_user_server] receiver is initialized
[2017-07-13 22:27:01.812] [info] [console_user_server] Check version...
[2017-07-13 22:27:01.812] [info] [console_user_server] grabber_client_ is connected
[2017-07-13 22:27:01.812] [info] [console_user_server] Load karabiner.json...
[2017-07-13 22:27:01.812] [info] [console_user_server] core_configuration is updated.
[2017-07-13 22:27:01.812] [info] [console_user_server] Check for updates...
[2017-07-13 22:27:01.815] [info] [grabber] event_tap_manager initialized
[2017-07-13 22:27:01.815] [info] [grabber] Load karabiner.json...
[2017-07-13 22:27:01.815] [info] [grabber] core_configuration is updated.
[2017-07-13 22:27:01.815] [info] [grabber] initialize_virtual_hid_keyboard
[2017-07-13 22:27:01.815] [info] [grabber]   keyboard_type:40
[2017-07-13 22:27:01.815] [info] [grabber]   caps_lock_delay_milliseconds:0
[2017-07-13 22:27:01.816] [warning] [grabber] virtual_hid_keyboard is not ready. Please wait for a while.
[2017-07-13 22:27:01.816] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 22:27:01.817] [info] [grabber] matching device:
[2017-07-13 22:27:01.817] [info] [grabber]   manufacturer: pqrs.org
[2017-07-13 22:27:01.817] [info] [grabber]   product: Karabiner VirtualHIDKeyboard
[2017-07-13 22:27:01.817] [info] [grabber]   vendor_id: 0x0
[2017-07-13 22:27:01.817] [info] [grabber]   product_id: 0x0
[2017-07-13 22:27:01.817] [info] [grabber]   location_id: 0x0
[2017-07-13 22:27:01.817] [info] [grabber]   serial_number: org.pqrs.driver.Karabiner.VirtualHIDDevice.VirtualHIDKeyboard
[2017-07-13 22:27:01.817] [info] [grabber]   registry_entry_id: 4294982966
[2017-07-13 22:27:01.819] [info] [grabber] Karabiner VirtualHIDKeyboard (device_id:3) is detected.
[2017-07-13 22:27:01.820] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 22:27:01.957] [info] [console_user_server] frontmost_application_observer initialize
[2017-07-13 22:27:02.886] [info] [console_user_server] system_preferences::values is updated.
[2017-07-13 22:27:02.887] [info] [grabber] system_preferences_values_updated
[2017-07-13 22:27:02.887] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is grabbed
[2017-07-13 23:09:40.677] [info] [grabber] version 0.91.7
[2017-07-13 23:09:40.695] [info] [grabber] Check version...
[2017-07-13 23:09:41.230] [info] [grabber] IOServiceOpen is succeeded @ void krbn::virtual_hid_device_client::matched_callback(io_iterator_t)
[2017-07-13 23:09:41.241] [info] [grabber] matching device:
[2017-07-13 23:09:41.241] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-13 23:09:41.241] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-13 23:09:41.241] [info] [grabber]   vendor_id: 0x5ac
[2017-07-13 23:09:41.241] [info] [grabber]   product_id: 0x274
[2017-07-13 23:09:41.241] [info] [grabber]   location_id: 0x14400000
[2017-07-13 23:09:41.241] [info] [grabber]   serial_number: D3H52374NA1FTV4AA3FS
[2017-07-13 23:09:41.242] [info] [grabber]   registry_entry_id: 4294968109
[2017-07-13 23:09:41.242] [info] [console_user_server] connection_manager::grabber_is_launched_callback
[2017-07-13 23:09:41.242] [info] [console_user_server] frontmost_application_observer terminate
[2017-07-13 23:09:41.243] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is detected.
[2017-07-13 23:09:41.243] [info] [grabber] matching device:
[2017-07-13 23:09:41.243] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-13 23:09:41.243] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-13 23:09:41.243] [info] [grabber]   vendor_id: 0x5ac
[2017-07-13 23:09:41.243] [info] [grabber]   product_id: 0x274
[2017-07-13 23:09:41.243] [info] [grabber]   location_id: 0x14400000
[2017-07-13 23:09:41.243] [info] [grabber]   serial_number: D3H52374NA1FTV4AA3FS
[2017-07-13 23:09:41.243] [info] [grabber]   registry_entry_id: 4294968105
[2017-07-13 23:09:41.244] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is detected.
[2017-07-13 23:09:42.287] [info] [console_user_server] receiver is terminated
[2017-07-13 23:09:42.287] [warning] [console_user_server] bind: No such file or directory
[2017-07-13 23:09:42.304] [info] [grabber] current_console_user_id: 502
[2017-07-13 23:09:42.304] [info] [grabber] Check version...
[2017-07-13 23:09:42.707] [info] [grabber] karabiner_console_user_server is connected (pid:25066)
[2017-07-13 23:09:42.707] [info] [console_user_server] receiver is initialized
[2017-07-13 23:09:42.707] [info] [console_user_server] Check version...
[2017-07-13 23:09:42.707] [info] [console_user_server] grabber_client_ is connected
[2017-07-13 23:09:42.707] [info] [console_user_server] Load karabiner.json...
[2017-07-13 23:09:42.708] [info] [console_user_server] core_configuration is updated.
[2017-07-13 23:09:42.708] [info] [console_user_server] Check for updates...
[2017-07-13 23:09:42.709] [info] [grabber] event_tap_manager initialized
[2017-07-13 23:09:42.709] [info] [grabber] Load karabiner.json...
[2017-07-13 23:09:42.709] [info] [grabber] core_configuration is updated.
[2017-07-13 23:09:42.709] [info] [grabber] initialize_virtual_hid_keyboard
[2017-07-13 23:09:42.709] [info] [grabber]   keyboard_type:40
[2017-07-13 23:09:42.709] [info] [grabber]   caps_lock_delay_milliseconds:0
[2017-07-13 23:09:42.710] [warning] [grabber] virtual_hid_keyboard is not ready. Please wait for a while.
[2017-07-13 23:09:42.710] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 23:09:42.710] [info] [grabber] matching device:
[2017-07-13 23:09:42.711] [info] [grabber]   manufacturer: pqrs.org
[2017-07-13 23:09:42.711] [info] [grabber]   product: Karabiner VirtualHIDKeyboard
[2017-07-13 23:09:42.711] [info] [grabber]   vendor_id: 0x0
[2017-07-13 23:09:42.711] [info] [grabber]   product_id: 0x0
[2017-07-13 23:09:42.711] [info] [grabber]   location_id: 0x0
[2017-07-13 23:09:42.711] [info] [grabber]   serial_number: org.pqrs.driver.Karabiner.VirtualHIDDevice.VirtualHIDKeyboard
[2017-07-13 23:09:42.711] [info] [grabber]   registry_entry_id: 4294983146
[2017-07-13 23:09:42.713] [info] [grabber] Karabiner VirtualHIDKeyboard (device_id:3) is detected.
[2017-07-13 23:09:42.713] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 23:09:42.875] [info] [console_user_server] frontmost_application_observer initialize
[2017-07-13 23:09:43.782] [info] [grabber] system_preferences_values_updated
[2017-07-13 23:09:43.782] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is grabbed
[2017-07-13 23:09:43.782] [info] [console_user_server] system_preferences::values is updated.
[2017-07-13 23:10:59.621] [info] [grabber] Load karabiner.json...
[2017-07-13 23:10:59.621] [info] [console_user_server] Load karabiner.json...
[2017-07-13 23:10:59.623] [info] [grabber] core_configuration is updated.
[2017-07-13 23:10:59.623] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 23:10:59.623] [info] [console_user_server] core_configuration is updated.
[2017-07-13 23:11:55.034] [info] [grabber] Load karabiner.json...
[2017-07-13 23:11:55.034] [info] [console_user_server] Load karabiner.json...
[2017-07-13 23:11:55.036] [info] [grabber] core_configuration is updated.
[2017-07-13 23:11:55.036] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is ignored.
[2017-07-13 23:11:55.036] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 23:11:55.036] [info] [console_user_server] core_configuration is updated.
[2017-07-13 23:12:09.128] [info] [grabber] Load karabiner.json...
[2017-07-13 23:12:09.129] [info] [console_user_server] Load karabiner.json...
[2017-07-13 23:12:09.130] [info] [grabber] core_configuration is updated.
[2017-07-13 23:12:09.130] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:1) is ignored.
[2017-07-13 23:12:09.130] [info] [console_user_server] core_configuration is updated.
[2017-07-13 23:12:09.297] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is grabbed

Thank you for feedback!
I believe this issue has been fixed at the latest version. (v0.91.8)
Please confirm v0.91.8.
I guess this issue is caused by karabiner_grabber process crash that is fixed at v0.91.8.
(I think there are some crash logs in Console.app.)

Hi @tekezo
Thank you for the update, but I encountered this problem again this morning. In my case it is always the (left?) option key. I rebooted Karabiner-Elements several times but it didn't help at this time, while I reported before that rebooting Karabiner-Elements temporality resolved the issue.
I typed the right option key, which is changed to be a function key in my environment, finding that it fixed my problem. As I have shown in a previous post with screen shots, I use "right_option to fn." Perhaps this setting is related to my option key problem.
I do not see any output in the Log tab or Console.app when the problem appeared.
いつも更新ありがとうございます。以前に Karabiner-Elements を再起動すると治ると書いたのですが、勘違いだったかたまたまだったのかもしれません。0.91.8 を再起動しても、sleep 後に option が押されっぱなしの状態になる問題は解決されず、右側の option (fn に置き換え済み) を押すと症状が治りました。
どこか debug 情報など取得すべきものがあれば、次回問題が再発した時に情報を集めますので、ご指示ください。

Got it again now. Using 0.91.8 Here's an excerpt from the log. I basically had it shutdown between 18:39 yesterday and 08:59 today.
[2017-07-17 18:39:10.636] [info] [grabber] removal device:
[2017-07-17 18:39:10.636] [info] [grabber]   vendor_id: 0x45e
[2017-07-17 18:39:10.636] [info] [grabber]   product_id: 0x745
[2017-07-17 18:39:10.636] [info] [grabber]   location_id: 0x14130000
[2017-07-17 18:39:10.659] [info] [grabber] Microsoft® Nano Transceiver v2.0 (device_id:10) is removed.
[2017-07-17 18:39:10.753] [info] [grabber] Microsoft® Nano Transceiver v2.0 (device_id:11) is ignored.
[2017-07-17 18:39:10.753] [info] [grabber] Staffan Eketorp’s Trackpad (device_id:9) is ignored.
[2017-07-17 18:39:10.753] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is ignored.
[2017-07-17 18:39:10.760] [info] [grabber] removal device:
[2017-07-17 18:39:10.760] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 18:39:10.760] [info] [grabber]   product_id: 0x250
[2017-07-17 18:39:10.760] [info] [grabber]   location_id: 0x14120000
[2017-07-17 18:39:10.760] [info] [grabber] Apple Keyboard (device_id:13) is removed.
[2017-07-17 18:39:10.771] [info] [grabber] Microsoft® Nano Transceiver v2.0 (device_id:11) is ignored.
[2017-07-17 18:39:10.771] [info] [grabber] Staffan Eketorp’s Trackpad (device_id:9) is ignored.
[2017-07-17 18:39:10.771] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is ignored.
[2017-07-17 18:39:10.771] [info] [grabber] removal device:
[2017-07-17 18:39:10.771] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 18:39:10.771] [info] [grabber]   product_id: 0xffff
[2017-07-17 18:39:10.771] [info] [grabber]   location_id: 0x14130000
[2017-07-17 18:39:10.771] [info] [grabber] Microsoft® Nano Transceiver v2.0 (device_id:12) is removed.
[2017-07-17 18:39:10.777] [info] [grabber] Microsoft® Nano Transceiver v2.0 (device_id:11) is ignored.
[2017-07-17 18:39:10.777] [info] [grabber] Staffan Eketorp’s Trackpad (device_id:9) is ignored.
[2017-07-17 18:39:10.777] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is ignored.
[2017-07-17 18:39:10.778] [info] [grabber] removal device:
[2017-07-17 18:39:10.778] [info] [grabber]   vendor_id: 0x45e
[2017-07-17 18:39:10.778] [info] [grabber]   product_id: 0x745
[2017-07-17 18:39:10.778] [info] [grabber]   location_id: 0x14130000
[2017-07-17 18:39:10.778] [info] [grabber] Microsoft® Nano Transceiver v2.0 (device_id:11) is removed.
[2017-07-17 18:39:10.800] [info] [grabber] Staffan Eketorp’s Trackpad (device_id:9) is ignored.
[2017-07-17 18:39:10.800] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is ignored.
[2017-07-17 18:52:01.244] [info] [grabber] removal device:
[2017-07-17 18:52:01.244] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 18:52:01.244] [info] [grabber]   product_id: 0x30e
[2017-07-17 18:52:01.244] [info] [grabber]   location_id: 0x3539f6d9
[2017-07-17 18:52:01.245] [info] [grabber] Staffan Eketorp’s Trackpad (device_id:9) is removed.
[2017-07-17 18:52:02.329] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is ignored.
[2017-07-17 23:40:27.220] [info] [grabber] removal device:
[2017-07-17 23:40:27.760] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 23:40:27.760] [info] [grabber]   product_id: 0x274
[2017-07-17 23:40:27.760] [info] [grabber]   location_id: 0x14400000
[2017-07-17 23:40:27.760] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:2) is removed.
[2017-07-17 23:40:28.301] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is ignored.
[2017-07-17 23:40:28.304] [info] [grabber] removal device:
[2017-07-17 23:40:28.304] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 23:40:28.304] [info] [grabber]   product_id: 0x274
[2017-07-17 23:40:28.304] [info] [grabber]   location_id: 0x14400000
[2017-07-17 23:40:28.304] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:7) is removed.
[2017-07-17 23:40:28.307] [info] [grabber] matching device:
[2017-07-17 23:40:28.307] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-17 23:40:28.307] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-17 23:40:28.307] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 23:40:28.307] [info] [grabber]   product_id: 0x274
[2017-07-17 23:40:28.308] [info] [grabber]   location_id: 0x14400000
[2017-07-17 23:40:28.308] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-17 23:40:28.308] [info] [grabber]   registry_entry_id: 4294999566
[2017-07-17 23:40:28.311] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:14) is detected.
[2017-07-17 23:40:28.311] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:14) is ignored.
[2017-07-17 23:40:28.312] [info] [grabber] matching device:
[2017-07-17 23:40:28.312] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-17 23:40:28.312] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-17 23:40:28.312] [info] [grabber]   vendor_id: 0x5ac
[2017-07-17 23:40:28.312] [info] [grabber]   product_id: 0x274
[2017-07-17 23:40:28.312] [info] [grabber]   location_id: 0x14400000
[2017-07-17 23:40:28.312] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-17 23:40:28.312] [info] [grabber]   registry_entry_id: 4294999562
[2017-07-17 23:40:28.315] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:15) is detected.
[2017-07-17 23:40:28.315] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:14) is ignored.
[2017-07-17 23:40:28.549] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:15) is grabbed
[2017-07-18 01:40:38.617] [info] [grabber] removal device:
[2017-07-18 01:40:40.145] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 01:40:40.145] [info] [grabber]   product_id: 0x274
[2017-07-18 01:40:40.145] [info] [grabber]   location_id: 0x14400000
[2017-07-18 01:40:40.145] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:15) is removed.
[2017-07-18 01:40:40.244] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:14) is ignored.
[2017-07-18 01:40:40.247] [info] [grabber] removal device:
[2017-07-18 01:40:40.247] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 01:40:40.247] [info] [grabber]   product_id: 0x274
[2017-07-18 01:40:40.247] [info] [grabber]   location_id: 0x14400000
[2017-07-18 01:40:40.247] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:14) is removed.
[2017-07-18 01:40:40.250] [info] [grabber] matching device:
[2017-07-18 01:40:40.250] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 01:40:40.250] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 01:40:40.250] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 01:40:40.250] [info] [grabber]   product_id: 0x274
[2017-07-18 01:40:40.250] [info] [grabber]   location_id: 0x14400000
[2017-07-18 01:40:40.250] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 01:40:40.250] [info] [grabber]   registry_entry_id: 4294999747
[2017-07-18 01:40:40.354] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:16) is detected.
[2017-07-18 01:40:40.356] [info] [grabber] matching device:
[2017-07-18 01:40:40.356] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 01:40:40.356] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 01:40:40.356] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 01:40:40.356] [info] [grabber]   product_id: 0x274
[2017-07-18 01:40:40.356] [info] [grabber]   location_id: 0x14400000
[2017-07-18 01:40:40.356] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 01:40:40.356] [info] [grabber]   registry_entry_id: 4294999757
[2017-07-18 01:40:40.359] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:17) is detected.
[2017-07-18 01:40:40.360] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:17) is ignored.
[2017-07-18 01:40:40.461] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:16) is grabbed
[2017-07-18 03:40:52.350] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:16) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 03:40:52.765] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:16) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 03:40:52.765] [info] [grabber] removal device:
[2017-07-18 03:40:52.765] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 03:40:52.765] [info] [grabber]   product_id: 0x274
[2017-07-18 03:40:52.765] [info] [grabber]   location_id: 0x14400000
[2017-07-18 03:40:52.765] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:16) is removed.
[2017-07-18 03:40:53.244] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:17) is ignored.
[2017-07-18 03:40:53.245] [info] [grabber] removal device:
[2017-07-18 03:40:53.245] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 03:40:53.245] [info] [grabber]   product_id: 0x274
[2017-07-18 03:40:53.245] [info] [grabber]   location_id: 0x14400000
[2017-07-18 03:40:53.245] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:17) is removed.
[2017-07-18 03:40:53.433] [info] [grabber] matching device:
[2017-07-18 03:40:53.433] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 03:40:53.433] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 03:40:53.433] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 03:40:53.433] [info] [grabber]   product_id: 0x274
[2017-07-18 03:40:53.433] [info] [grabber]   location_id: 0x14400000
[2017-07-18 03:40:53.433] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 03:40:53.433] [info] [grabber]   registry_entry_id: 4294999980
[2017-07-18 03:40:53.717] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:18) is detected.
[2017-07-18 03:40:53.719] [info] [grabber] matching device:
[2017-07-18 03:40:53.719] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 03:40:53.719] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 03:40:53.719] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 03:40:53.719] [info] [grabber]   product_id: 0x274
[2017-07-18 03:40:53.719] [info] [grabber]   location_id: 0x14400000
[2017-07-18 03:40:53.719] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 03:40:53.719] [info] [grabber]   registry_entry_id: 4294999991
[2017-07-18 03:40:53.722] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:19) is detected.
[2017-07-18 03:40:53.724] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:19) is ignored.
[2017-07-18 03:40:53.896] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:18) is grabbed
[2017-07-18 05:41:05.453] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:18) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 05:41:05.683] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:18) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 05:41:05.683] [info] [grabber] removal device:
[2017-07-18 05:41:05.683] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 05:41:05.683] [info] [grabber]   product_id: 0x274
[2017-07-18 05:41:05.683] [info] [grabber]   location_id: 0x14400000
[2017-07-18 05:41:05.683] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:18) is removed.
[2017-07-18 05:41:05.749] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:19) is ignored.
[2017-07-18 05:41:05.750] [info] [grabber] removal device:
[2017-07-18 05:41:05.750] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 05:41:05.750] [info] [grabber]   product_id: 0x274
[2017-07-18 05:41:05.750] [info] [grabber]   location_id: 0x14400000
[2017-07-18 05:41:05.750] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:19) is removed.
[2017-07-18 05:41:05.755] [info] [grabber] matching device:
[2017-07-18 05:41:05.755] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 05:41:05.755] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 05:41:05.755] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 05:41:05.755] [info] [grabber]   product_id: 0x274
[2017-07-18 05:41:05.755] [info] [grabber]   location_id: 0x14400000
[2017-07-18 05:41:05.756] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 05:41:05.756] [info] [grabber]   registry_entry_id: 4295000191
[2017-07-18 05:41:05.761] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:20) is detected.
[2017-07-18 05:41:05.794] [info] [grabber] matching device:
[2017-07-18 05:41:05.794] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 05:41:05.794] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 05:41:05.794] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 05:41:05.794] [info] [grabber]   product_id: 0x274
[2017-07-18 05:41:05.794] [info] [grabber]   location_id: 0x14400000
[2017-07-18 05:41:05.794] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 05:41:05.794] [info] [grabber]   registry_entry_id: 4295000195
[2017-07-18 05:41:05.820] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:21) is detected.
[2017-07-18 05:41:05.821] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:21) is ignored.
[2017-07-18 05:41:06.071] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:20) is grabbed
[2017-07-18 06:40:36.595] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:20) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 06:40:37.289] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:20) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 06:40:37.289] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:20) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 06:40:37.289] [info] [grabber] removal device:
[2017-07-18 06:40:37.289] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 06:40:37.289] [info] [grabber]   product_id: 0x274
[2017-07-18 06:40:37.289] [info] [grabber]   location_id: 0x14400000
[2017-07-18 06:40:37.289] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:20) is removed.
[2017-07-18 06:40:37.736] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:21) is ignored.
[2017-07-18 06:40:37.736] [info] [grabber] removal device:
[2017-07-18 06:40:37.736] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 06:40:37.736] [info] [grabber]   product_id: 0x274
[2017-07-18 06:40:37.736] [info] [grabber]   location_id: 0x14400000
[2017-07-18 06:40:37.736] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:21) is removed.
[2017-07-18 06:40:37.895] [info] [grabber] matching device:
[2017-07-18 06:40:37.895] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 06:40:37.895] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 06:40:37.895] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 06:40:37.895] [info] [grabber]   product_id: 0x274
[2017-07-18 06:40:37.895] [info] [grabber]   location_id: 0x14400000
[2017-07-18 06:40:37.895] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 06:40:37.895] [info] [grabber]   registry_entry_id: 4295000450
[2017-07-18 06:40:38.067] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:22) is detected.
[2017-07-18 06:40:38.120] [info] [grabber] matching device:
[2017-07-18 06:40:38.120] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 06:40:38.120] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 06:40:38.120] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 06:40:38.120] [info] [grabber]   product_id: 0x274
[2017-07-18 06:40:38.120] [info] [grabber]   location_id: 0x14400000
[2017-07-18 06:40:38.120] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 06:40:38.120] [info] [grabber]   registry_entry_id: 4295000460
[2017-07-18 06:40:38.121] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:23) is detected.
[2017-07-18 06:40:38.178] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:23) is ignored.
[2017-07-18 06:40:38.386] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:22) is grabbed
[2017-07-18 08:57:53.369] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:22) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 08:57:54.043] [error] [grabber] IOHIDDeviceSetValue error -536870206 for Apple Internal Keyboard / Trackpad (device_id:22) @ ___ZN4krbn22human_interface_device23set_caps_lock_led_stateENS_9led_stateE_block_invoke
[2017-07-18 08:57:54.043] [info] [grabber] removal device:
[2017-07-18 08:57:54.043] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 08:57:54.043] [info] [grabber]   product_id: 0x274
[2017-07-18 08:57:54.043] [info] [grabber]   location_id: 0x14400000
[2017-07-18 08:57:54.043] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:22) is removed.
[2017-07-18 08:57:54.168] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:23) is ignored.
[2017-07-18 08:57:54.169] [info] [grabber] removal device:
[2017-07-18 08:57:54.169] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 08:57:54.169] [info] [grabber]   product_id: 0x274
[2017-07-18 08:57:54.169] [info] [grabber]   location_id: 0x14400000
[2017-07-18 08:57:54.169] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:23) is removed.
[2017-07-18 08:57:54.171] [info] [grabber] matching device:
[2017-07-18 08:57:54.171] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 08:57:54.171] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 08:57:54.171] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 08:57:54.171] [info] [grabber]   product_id: 0x274
[2017-07-18 08:57:54.171] [info] [grabber]   location_id: 0x14400000
[2017-07-18 08:57:54.171] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 08:57:54.171] [info] [grabber]   registry_entry_id: 4295000690
[2017-07-18 08:57:54.174] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:24) is detected.
[2017-07-18 08:57:54.267] [info] [grabber] matching device:
[2017-07-18 08:57:54.267] [info] [grabber]   manufacturer: Apple Inc.
[2017-07-18 08:57:54.267] [info] [grabber]   product: Apple Internal Keyboard / Trackpad
[2017-07-18 08:57:54.267] [info] [grabber]   vendor_id: 0x5ac
[2017-07-18 08:57:54.267] [info] [grabber]   product_id: 0x274
[2017-07-18 08:57:54.267] [info] [grabber]   location_id: 0x14400000
[2017-07-18 08:57:54.267] [info] [grabber]   serial_number: D3H53957UE1FTV4A06FS
[2017-07-18 08:57:54.267] [info] [grabber]   registry_entry_id: 4295000698
[2017-07-18 08:57:54.268] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:25) is detected.
[2017-07-18 08:57:54.284] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:25) is ignored.
[2017-07-18 08:57:54.454] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:24) is grabbed
[2017-07-18 08:59:17.003] [info] [grabber] Load karabiner.json...
[2017-07-18 08:59:17.027] [info] [grabber] core_configuration is updated.
[2017-07-18 08:59:17.029] [info] [grabber] initialize_virtual_hid_keyboard
[2017-07-18 08:59:17.029] [info] [grabber]   keyboard_type:40
[2017-07-18 08:59:17.029] [info] [grabber]   caps_lock_delay_milliseconds:0
[2017-07-18 08:59:17.029] [info] [console_user_server] Load karabiner.json...
[2017-07-18 08:59:17.031] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:25) is ignored.
[2017-07-18 08:59:17.031] [warning] [grabber] virtual_hid_keyboard is not ready. Please wait for a while.
[2017-07-18 08:59:17.031] [info] [grabber] removal device:
[2017-07-18 08:59:17.031] [info] [grabber]   vendor_id: 0x0
[2017-07-18 08:59:17.031] [info] [grabber]   product_id: 0x0
[2017-07-18 08:59:17.031] [info] [grabber]   location_id: 0x0
[2017-07-18 08:59:17.031] [info] [grabber] Karabiner VirtualHIDKeyboard (device_id:8) is removed.
[2017-07-18 08:59:17.031] [info] [console_user_server] core_configuration is updated.
[2017-07-18 08:59:17.032] [info] [grabber] Connected devices are ungrabbed
[2017-07-18 08:59:17.033] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:25) is ignored.
[2017-07-18 08:59:17.033] [info] [grabber] matching device:
[2017-07-18 08:59:17.033] [info] [grabber]   manufacturer: pqrs.org
[2017-07-18 08:59:17.033] [info] [grabber]   product: Karabiner VirtualHIDKeyboard
[2017-07-18 08:59:17.033] [info] [grabber]   vendor_id: 0x0
[2017-07-18 08:59:17.033] [info] [grabber]   product_id: 0x0
[2017-07-18 08:59:17.033] [info] [grabber]   location_id: 0x0
[2017-07-18 08:59:17.033] [info] [grabber]   serial_number: org.pqrs.driver.Karabiner.VirtualHIDDevice.VirtualHIDKeyboard
[2017-07-18 08:59:17.034] [info] [grabber]   registry_entry_id: 4295000936
[2017-07-18 08:59:17.037] [info] [grabber] Karabiner VirtualHIDKeyboard (device_id:26) is detected.
[2017-07-18 08:59:17.037] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:25) is ignored.
[2017-07-18 08:59:18.109] [info] [grabber] Apple Internal Keyboard / Trackpad (device_id:24) is grabbed

I think I get the reason now.
@akira-okumura uses the Emacs key bindings, which map option + b/f to option + arrow keys like this:
{
  "type": "basic",
  "from": <%= from("b", ["option"], ["caps_lock", "shift"]) %>,
  "to": <%= to([["left_arrow", ["left_option"]]]) %>,
  "conditions": [ <%= frontmost_application_unless("emacs_key_bindings_exception") %> ]
},

However, the Emacs key bindings do not append a vk_none key after the left_arrow + left_option event, so the left_option modifier will keep pressed after this event. Append a vk_none in this rule should fix the problem:
"to": <%= to([["left_arrow", ["left_option"]], ["vk_none"]]) %>,

Other complex modification rules may have this same problem. Every time a modifier key has been mapped to, we must manually append a vk_none after that event to release the modifier key.

No, actually we should use to_after_key_up to release the modifier key, so if the user keeps pressing option + b, he will get the multiple left_arrow strokes as expected.
{
  "type": "basic",
  "from": <%= from("b", ["option"], ["caps_lock", "shift"]) %>,
  "to": <%= to([["left_arrow", ["left_option"]]]) %>,
  "to_after_key_up": <%= to([["vk_none"]]) %>,
  "conditions": [ <%= frontmost_application_unless("emacs_key_bindings_exception") %> ]
},

First, please confirm the latest Karabiner-Elements. I fixed an issue about modifier flag handling in v0.91.11.
There are several layers related with input events. (Hardware, macOS system, Karabiner-Elements)
If restarting KE does not solve your issue, the issue is caused by hardware or macOS.
@apm1467 The lazy modifier flag release is necessary to suppress unnecessary flag changes.
For example, press control+p, control+n with emacs key bindings,
We want to send these events:

control key down
control key up
up arrow key down
up arrow key up
down arrow key down
down arrow key up

Without the lazy modifier flag release:

control key down
control key up
up arrow key down
up arrow key up
control key down
control key up
down arrow key down
down arrow key up
up arrow key down

I have used 0.91.11 and 0.91.12 for a while, but I still have this issue. Repeating restart of KE several times usually fixes this issue.

Duplicate to #466

@akira-okumura Would you mind test this modified version of Emacs key bindings?
You can just disable the official Emacs key bindings, copy this JSON file to ~/.config/karabiner/assets/complex_modifications and enable it in KE. All key bindings are the same.
I just append some vk_none after the option key bindings. As @tekezo has mentioned, this will create unnecessary flag changes. But as I've tested, it actually does not influence the normal usage. And it might fix the option key issue.
Hope it works.

I'm also seeing this on 0.91.12. Restarting Karabiner Elements resolves it for me

KE Version: 0.91.12
MacOS: 10.12.6
Same thing here,  with the Shift key. It doesn't happen after every "sleep", but does happen enough that it is annoying. Quiting and Relaunching karabiner-elements usually, fixes it, but sometimes it takes a few quit/restarts to fix it.
The log file will be filled with these types of errors:
2017-08-09 09:54:21.695] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:21.696] [error] [grabber] IOHIDDeviceSetValue error -536870195 for Apple Keyboard (device_id:12) @ IOReturn krbn::human_interface_device::set_caps_lock_led_state(krbn::led_state)_block_invoke
[2017-08-09 09:54:21.793] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:21.894] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:21.994] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.094] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.192] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.294] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.393] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.493] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.590] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)
[2017-08-09 09:54:22.696] [error] [grabber] IOHIDDeviceOpen error: kIOReturnBadArgument (-536870206) Apple Keyboard (device_id:12)

It adds about 10 lines of errors every second, until I quit KE, and relaunch.

I ran into this as well, my shift key was being held down so using a web browser in a normal way was quite challenging. I am guessing that this will be solved by me changing my (custom) readline-ish bindings in some way. I tried restarting KE but this didn't seem to solve the problem.
One thing that did seem to remove the key from being held down was invoking a few of my custom bindings. I am guessing that it ended up running them and then sending VK_NONE as specified to clear the shift key. Now I am able to use apps normally! I realize this is just a workaround but it might be helpful for someone.

authors: akira-okumura alexeden apm1467 h-nn-ng k0nserv panozzaj staeke tekezo tphalp

repo: tekezo/Karabiner-Elements

license: unlicense


text:
MELEBERUOU e ng ngera a belkul?

MELEBERUOU e ng ngera a belkul? created by palau371@gmail.com on 2016-12-26 16:22:20

palau371@gmail.com replied, we have that word in a pdef, but not in DB

johnbent@gmail.com replied, Can you share the pdef please and its root word?

palau371@gmail.com replied, deleberuou, v.r.s.deleberuou a meterekakl, terrekakl a kelel me a ududel; meleberuou a bol secher e ng diak a udoud el mechar a kerul.

mngiruchelbad@gmail.com replied, Inept: un prepared: Synonym: melebaob or delebaob

palau371@gmail.com replied, is there words like DOBOBII or DOBAOB?

mngiruchelbad@gmail.com replied, Just delbaob;melebaob.deleberuou:meleberuou

mngiruchelbad@gmail.com replied, Ngkal Ulang a kmal deleberuou a teletelel meng di blechoel el olengesonges sel nga er ngii a mechesang. Ulang never manages her finances well that she is always short when there is a need for her.Ulang! Ke kemeral meleberuou mekedi belchoel lolengeseonges. Ulang, you are  always inept that you are short.

masa@palaunet.com replied, dobaob is the plural of delebaob.  Ng mla dobaob a udoud.  Masaharu

johnbent@gmail.com replied, Aleks, would you mind please arranging this one into the format so I can easily import it into the database?  I'll edit the English definitions if necessary before doing the import?

palau371@gmail.com replied, No problem, John!The only things I need for that is the ENG's for them.

johnbent@gmail.com replied, Thanks.  Very much appreciated.  If you can just try your best on the
english, I'll fix it up.

mngiruchelbad@gmail.com replied, meleberuou: meterkakl: careless

johnbent@gmail.com replied, Hello Aleks,  will you be able to provide the import block for this one please?

palau371@gmail.com replied, it's v.t., careless isn't exact translation for it

johnbent@gmail.com replied, I can fix the English once everything is in our standard format.

johnbent@gmail.com replied, Beautiful.

repo: tekinged/missing


text:
Node.js Client SDK

Must be written in Typescript and live in /sdk/node/
Handles:

/api/ping
/api/list-runtimes
/api/execute

See: https://github.com/teknologi-umum/pesto/blob/master/rce/src/index.ts

Hi @aldy505
So, I need to write a sample code for consuming/handling pesto API?

SDK is not a sample code. SDK is a client library to consume the API.

Hey @aldy505 I can be of help here. I use Fern (www.buildwithfern.com) to auto-generate SDKs, including Node.js.
Here's an SDK I recently built for another organization: https://github.com/fern-primer/primer-node
Let me know if this is of interest for https://github.com/teknologi-umum .

Hi @dannysheridan unless you can show a sample of code gen'd SDK that you're impling, I'm sorry, I'm not really interested on code gen'd SDK. I want to focus to the DX, not just a functional code that calls the API correctly.

@aldy505 here's a TypeScript example app consuming a Node SDK generated by Fern: https://github.com/fern-primer/primer-node/blob/main/.sample-app/app.ts

authors: aldy505 dannysheridan ddouble-d

repo: teknologi-umum/pesto


text:
Including YACL.h into Arduino Sketch throws error - call of overloaded 'add(unsigned int&)' is ambiguous

Hello,
when adding your library to an Arduino sketch the Arduino IDE (1.8.13) throws an error when I try to compile a sketch for the board MKRWAN 1310:
In file included from /home/user/Arduino/libraries/YACL/src/YACL.h:4:0,
              from /home/user/Arduino/cbor_test/cbor_test.ino:1:
/home/user/Arduino/libraries/YACL/src/CBOR.h: In instantiation of 'CBOR::CBOR(T) [with T = unsigned int]':
/home/user/Arduino/libraries/YACL/src/CBOR.h:773:20:   required from 'CBOR CBOR::find_by_key(T) [with T = unsigned int]'
/home/user/Arduino/libraries/YACL/src/CBOR.h:287:27:   required from 'CBOR CBOR::access_op_numeric(T) [with T = unsigned int]'
/home/user/Arduino/libraries/YACL/src/CBOR.h:825:72:   required from here
/home/user/Arduino/libraries/YACL/src/CBOR.h:303:41: error: call of overloaded 'add(unsigned int&)' is ambiguous
   template <typename T> CBOR(T value) { add(value); }
                                         ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:196:8: note: candidate: bool CBOR::add(bool)
   bool add(bool value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:206:8: note: candidate: bool CBOR::add(uint8_t)
   bool add(uint8_t value) { return encode_type_num(CBOR_UINT, value); }
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:207:8: note: candidate: bool CBOR::add(uint16_t)
   bool add(uint16_t value) { return encode_type_num(CBOR_UINT, value); }
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:208:8: note: candidate: bool CBOR::add(uint32_t)
   bool add(uint32_t value) { return encode_type_num(CBOR_UINT, value); }
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:209:8: note: candidate: bool CBOR::add(uint64_t)
   bool add(uint64_t value) { return encode_type_num(CBOR_UINT, value); }
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:219:8: note: candidate: bool CBOR::add(int8_t)
   bool add(int8_t value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:220:8: note: candidate: bool CBOR::add(int16_t)
   bool add(int16_t value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:221:8: note: candidate: bool CBOR::add(int32_t)
   bool add(int32_t value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:222:8: note: candidate: bool CBOR::add(int64_t)
   bool add(int64_t value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:229:8: note: candidate: bool CBOR::add(float)
   bool add(float value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:235:8: note: candidate: bool CBOR::add(double)
   bool add(double value);
        ^~~
/home/user/Arduino/libraries/YACL/src/CBOR.h:256:8: note: candidate: bool CBOR::add(const CBOR&)
   bool add(const CBOR &value);
        ^~~
exit status 1

The error already is shown when I include your library without using it in the code.

Hello,
Thank you for raising this issue.
I will investigate the problem and keep you informed.

OK I can reproduce the bug, and found the source of the problem.
I will issue a fix in a few days.

Thanks a lot!
Am 16. Juli 2020 20:30:20 MESZ schrieb Alexandre Marquet notifications@github.com:

OK I can reproduce the bug, and found the source of the problem.
I will issue a fix in a few days.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/telecombretagne/YACL/issues/4#issuecomment-659592087

I just released v1.0.3 of the library. It should resolve the compilation issue, and be available in the Arduino libraries manager soon.
Unfortunately, I do not own an Arduino MKR *.
If the compilation is successful on your platform, would you mind executing examples sketched test_encode.ino and test_decode.ino, to see if everything works fine?

Hi,
thanks for all your work!
Compilation now is successful - this is the output of test_encode.ino:
Begining test sequence!
Null: OK
True: OK
False: OK
-1: OK
-1000: OK
-1000000000: OK
-1000000000000000: OK
23: OK
1000: OK
1000000000: OK
2376030000: OK
1000000000000000: OK
-1.5 : OK
1.5 : OK
-1.5 (double) : OK
1.5 (double) : OK
"aoeu1234" : OK
"åöéûのかめ亀" : OK
"" : OK
[] : OK
[1, 2, 3] : OK
{2: 2, "1,2,3": [1,2,3], "Null": NULL} : OK
[1, 3.16, "test"] : OK
Custom tag encoding : OK
h'' : OK
h'01020304' : OK

and of test_decode.ino:
Begining test sequence!
True: OK
False: OK
-1: NOK
-1000: OK
-1000000000: OK
-1000000000000000: OK
23: OK
1000: OK
1000000000: OK
2376030000: OK
1000000000000000: OK
-0.0 (half) : OK
-4.0 (half) : OK
1.0 (half) : OK
0.0 (half) : OK
65504.0 (half) : OK
1.5 (half) : OK
5.960464477539063e-8 (half) : OK
0.00006103515625 (half) : OK
Infinity (half) : OK
-Infinity (half) : OK
NaN (half) : OK
-1.5 : OK
100000.0 : OK
1.5 : OK
3.4028234663852886e+38 : OK
Infinity : OK
-Infinity : OK
NaN : OK
-1.5 (double) : OK
-4.1 (double) : OK
1.5 (double) : OK
1.1 (double) : OK
Infinity (double) : OK
-Infinity (double) : OK
NaN (double) : OK
aoeu1234 (char[]) : OK
åöéûのかめ亀 (char []) : OK
Lorem ipsum... (char []) : OK
aoeu1234 (String) : OK
åöéûのかめ亀 (String) : OK
[1, 2, 3] : OK
[1, 3.16, "test"] : OK
[1, [2, 3], [4, 5]] : OK
[1, ..., 25] : OK
{1: 2, 3: 4} : OK
{"a": 1, "b": [2, 3]} : OK
{"a": "A", "b": "B", "c": "C", "d": "D", "e": "E"} : OK
Custom tag : OK
h'' : OK
h'01020304' : OK

I had to add a while (!Serial); to see the output, first I saw nothing also when the serial monitor was already open.
Because I saw that decoding "-1" was NOK I added a Serial.println((char)cbor); to the test test_negint1() and the output in the serial monitor was: ⸮. Hope that helps.
Thank you

Interesting: I always thought that char was defined as a signed type, but this is actually application-defined!
Well, v1.0.4 should fix this last NOK in test_decode.ino :)
P.S.: I always do a manual reset of my boards to see the messages in the serial monitor, seems like I should think about adding a while(!Serial);, as you suggested.

Hi,
you're right, now this is the result of test_decode.ino:
Begining test sequence!
True: OK
False: OK
-1: OK
-1000: OK
-1000000000: OK
-1000000000000000: OK
23: OK
1000: OK
1000000000: OK
2376030000: OK
1000000000000000: OK
-0.0 (half) : OK
-4.0 (half) : OK
1.0 (half) : OK
0.0 (half) : OK
65504.0 (half) : OK
1.5 (half) : OK
5.960464477539063e-8 (half) : OK
0.00006103515625 (half) : OK
Infinity (half) : OK
-Infinity (half) : OK
NaN (half) : OK
-1.5 : OK
100000.0 : OK
1.5 : OK
3.4028234663852886e+38 : OK
Infinity : OK
-Infinity : OK
NaN : OK
-1.5 (double) : OK
-4.1 (double) : OK
1.5 (double) : OK
1.1 (double) : OK
Infinity (double) : OK
-Infinity (double) : OK
NaN (double) : OK
aoeu1234 (char[]) : OK
åöéûのかめ亀 (char []) : OK
Lorem ipsum... (char []) : OK
aoeu1234 (String) : OK
åöéûのかめ亀 (String) : OK
[1, 2, 3] : OK
[1, 3.16, "test"] : OK
[1, [2, 3], [4, 5]] : OK
[1, ..., 25] : OK
{1: 2, 3: 4} : OK
{"a": 1, "b": [2, 3]} : OK
{"a": "A", "b": "B", "c": "C", "d": "D", "e": "E"} : OK
Custom tag : OK
h'' : OK
h'01020304' : OK

test_encode.ino is also ok - I have tested it again.
P.S.: the Arduino Library Manager shows 1.0.3 as last version, not 1.0.4.
Resetting the board didn't worked for me, i always had to insert while(!Serial); to see the results of the tests - don't know if this is a MKRWAN specific problem.
Thanks again - Issue can be closed if you haven't other things for me to test ;).

Ah! I forgot to increment the version number in library.properties, thanks!
Thank you for the hints. I'm closing this issue.

repo: telecombretagne/YACL


text:
add grouping option to holdings tree maker

currently makeValuationReportHoldingsTree groups holdings by
classification. It is default and fixed. We should make it configurable to
group by classification or sector or industry or country or currency.
https://github.com/teloscube/decaf-client-javascript-extras/blob/f0247da9dde73c028e325df6fa427f79fb9580b2/src/reports/valuation/-valuation-report-holdings-tree/-machinery.ts#L172

I am going to steal below section from headless folder and integrate it here:

@vst Do you have any objection for this ?

No objection your Honor.

Niye close ettiysem :)

authors: alioguzhan vst


text:
WALLET - Single Account template updates - main information section

To support the new connected account functionality, we'll be updating all the Single Account templates.
For all accounts, except for ones that the user has attached, users will now see:

In the main informational section, this will show the user:

accountname
creator account
status of the resources, with a nice circle graph around each
a table of the account's balances for:
-- total
-- refunding tokens
-- staked by other accounts
-- staked to REX (for later, I think)

In the secondary detail section, we will have tabs with sub-content:

Transactions
Tokens
Keys
Children (child accounts created by this account)

Transactions
Transactions will use the typical quasar table functionality already developed to show transactions.

Tokens
Tokens will use the following layout:

Keys
Keys and permissions will be shown using this layout:

Children
Children will be shown using a simple quasar table.

@ramijames @DestinyDevTeam I split this into two cards,  the main info section that this PR addresses, and another card with this linked for the secondary detail section.  See the Netlify Deploy Preview link in the associated PR to review. Thanks.

authors: DonaldPeat ramijames

repo: telosnetwork/open-block-explorer


text:
🛑 Secret Site2 is down

In ed03050, Secret Site2 ($SECRET_SITE_2) was down:

HTTP code: 404
Response time: 103 ms

Resolved: Secret Site2 is back up in 2462127.

repo: templain/mywatcher


text:
merge from template-kronos-app

.github/workflows/ci.yml

chore(deps): remove 18.7.0 (jobs.test.strategy.matrix.node-version)

:tada: This PR is included in version 1.10.163 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.10.163
GitHub release

Your semantic-release bot :package::rocket:

repo: template-tools/template-sync-hook


text:
Add headers to signals and queries

What was changed
Passes headers to signals and queries appropriately
Why?
Headers good
Checklist

Closes https://github.com/temporalio/sdk-core/issues/236

How was this tested:
Added tests

Any docs updates needed?

@bergundy Can't do IT at the moment without adding entire query functionality to prototype SDK, but added to UT stuff that covers necessary path

repo: temporalio/sdk-core


text:
Enable sequential execution with specific seed

Please note that every time you call the ip_adapter instance twice, the generator resets the seed. This prevents the reproduction of experiments with multiple calls.
Using num_samples to generate multiple images with the same seed is limited by the available device memory.

thanks a lot

repo: tencent-ailab/IP-Adapter


text:
Bcrypt usability

I extracted the cost as a parameter. The current value (14) is nice and secure, but kills the UX. Signing a tx (or returning a bad password error) takes around 1 second just due to the bcrypt decoding of the key on my desktop (i7), slower on other computers. Tests are super slow.
Reducing this to 12 (a factor of 4) makes it much more usable, and I think the security is still quite high. Remember that we decrypt the key every time we use it to avoid keeping it in memory and passing it outside the key manager.
If you think I am destroying the security of our key system, please reject this.

Just out of curiosity, what's the threat model with not storing the key in memory inside the key manager while the program is running?
Are we protecting against malware that has memory read access but not at the point that a transaction is happening? or cold boot attacks?

Are we protecting against malware that has memory read access but not at the point that a transaction is happening? or cold boot attacks?

Good question. Seems standard for the key to be kept in memory for a short time, for convenience sake. The tradeoff is there's a longer period during which someone could hit you with a cold boot attack, vs. having to time it for right after you sign.
Malware that doesn't have read access at the point of the tx happening seems unlikely.
Maybe we should consider storing the key in memory unlocked for a few minutes at a time?

From a user's perspective, I think it's okay to wait a second to unlock the wallet and then have the key in memory for a configurable amount of time (i.e 1 minute, 10 minutes, 1 hour, until program is quit)
Also, we're relying on Go's garbage collection to clear the keys out of memory. It's worth researching if there's a deterministic way to make sure an address is zeroed out.

authors: ebuchman ethanfrey mveytsman

repo: tendermint/go-crypto


text:
🛑 GgzPraktijk is down

In 4911e3f, GgzPraktijk (https://ggzpraktijk.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GgzPraktijk is back up in a5b9b28 after 4 minutes.

repo: tendsgn/upptime


text:
🛑 Beeldoverleg Website is down

In 9aac62a, Beeldoverleg Website (https://beeldoverleg.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beeldoverleg Website is back up in 2e20b40 after 6 minutes.


text:
Automatizar a checagem de barel export

Talvez eslint
Talvez prettier
@erick-medeiros como eu criei a issue tu que faz  😂😂

blz hehe

Pelo que testei aqui se o index.ts existir o vscode já prioriza o barrel export
Então se fosse existir alguma obrigatoriedade seria de impedir a importação que não seja feita pelo barrel export
E para isso não encontrei alternativas muito viáveis
https://stackoverflow.com/questions/76167422/how-to-force-the-use-of-barrel-files-in-typescript
Encontrei essa ideia mas teria que mudar a estrutura que estamos usando atualmente

authors: LucasKuhn erick-medeiros


text:
🛑 Cloud Services (tcloud.dev) is down

In 9f48c78, Cloud Services (tcloud.dev) (https://tcloud.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cloud Services (tcloud.dev) is back up in 0524642 after 2 hours, 2 minutes.

repo: tensegrity-labs-admin/uptime


text:
feat(CLI): Add envd images remove command

Description
We lack the command envd images remove to remove the envd images. The environment can be removed via envd destroy, but the built images cannot be removed using envd. This issue is to support it.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Is it related to https://github.com/tensorchord/envd/pull/925?

Yep, but there may be some images in the host. For example, the images you pulled from docker registry.

remove the unused images by project names?

Remove by the image name, I think.

I can try on this issue

/assign @Triple-Z
Thanks!

authors: Triple-Z gaocegege kemingy

repo: tensorchord/envd


text:
Removing the call to the deprecated Interpreter constructor on the Speech Command example for Android

Replacing the Interpreter constructor with the deprecated signature public Interpreter(MappedByteBuffer byteBuffer) by the one with the supported signature public Interpreter(ByteBuffer byteBuffer), by just updating the returned type of the method loadModelFile(AssetManager assets, String modelFilename) to ByteBuffer.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

@googlebot I signed it!

Hi Michel,
MappedByteBuffer is a subclass of ByteBuffer. There is no problem when deprecated function Interpreter(MappedByteBuffer) is deleted, and it will call the equivalent Interpreter(ByteBuffer) directly. So it is not needed to make a change essentially.

Hi Tian,
I see. If that is the case I am going to close this PR.
Thank you!

repo: tensorflow/examples