"using" property should be formatted as a bulleted list, like "required" et. al

For consistency, and to prevent whitespace changes by text editors.

Hi @waldyrious, I'm not sure I understand. Are you talking about this list?

Hi. Yes, I'm talking about that list, but just to clarify, I meant in the yaml/txt files. The change I propose would make the "using" property consistent with the other list-like properties like "required", etc.
For instance, in epl-1.0.txt, instead of:
using:
  The Eclipse Foundation: "http://www.eclipse.org"
  OpenDaylight: "http://www.opendaylight.org/"
  Clojure: "http://clojure.org/"
  JUnit: "http://junit.org/"
  Ruby: "https://github.com/jruby/jruby"
  Mondrian: "http://en.wikipedia.org/wiki/Mondrian_OLAP_server"

required:
  - disclose-source
  - include-copyright

permitted:
  - commercial-use
  - distribution
  - modifications
  - sublicense
  - patent-grant
  - private-use

forbidden:
  - no-liability

we'd have:
using:
  - The Eclipse Foundation: "http://www.eclipse.org"
  - OpenDaylight: "http://www.opendaylight.org/"
  - Clojure: "http://clojure.org/"
  - JUnit: "http://junit.org/"
  - Ruby: "https://github.com/jruby/jruby"
  - Mondrian: "http://en.wikipedia.org/wiki/Mondrian_OLAP_server"

required:
  - disclose-source
  - include-copyright

permitted:
  - commercial-use
  - distribution
  - modifications
  - sublicense
  - patent-grant
  - private-use

forbidden:
  - no-liability

...which, as a bonus, makes it more evident that it's a list and not hard-wrapped prose.

Huh. Looks like that creates an array of hashes, rather than a single hash. Didn't realize that would be valid YAML. @waldyrious if you'd like to put together a pull request (I suspect the layout and tests will need to be updated), I'd be glad to review/merge.

Didn't realize that would be valid YAML.

Me either. TIL

@waldyrious I'm :cool: with switching the formatting of this list. I'm going to close this in the mean time since it's not currently causing any issues, but feel free to submit a pull request!

IIRC, I didn't put a PR together when I submitted this issue, because I wanted to wait until my latest PR (#293) got merged, since I'd been "burned" before due to nonresponsiveness to a previous PR (#258) making it go stale and giving me quite some work redoing it almost entirely from scratch. Sorry for not making it clear in this thread. I'm ready to submit a PR if you guys are ready to review and hopefully merge it.

Weird, I'm pretty sure github used to generate a backlink to the actual PR, not just the commits. Anyway, here's the PR, for future reference: #306.


can not directly update iris when iris has new version

[DBUG] 2017/10/01 11:59 Host: register startup notifier
[DBUG] 2017/10/01 11:59 Host: register server shutdown on interrupt(CTRL+C/CMD+C)
[DBUG] 2017/10/01 11:59 Host: server will ignore the following errors: []
Now listening on: http://localhost:8089
Application started. Press CMD+C to shut down.
[WARN] 2017/10/01 11:59 A new version is available online[8.4.4 > 8.4.3].
Release notes: https://github.com/kataras/iris/blob/master/HISTORY.md#su-01-october-2017--v844
Update now?[y/n]:
[INFO] 2017/10/01 11:59 Ignore updates? Disable version checker via:
app.Run(..., iris.WithoutVersionChecker)

Hello @motecshine , can you give more information please?
You mean by running rizla main.go or when go run main.go, if rizla main.go then the problem is that you're unable to use the os.Stdin inside it, we can fix it but I don't think that this is a priority right now.


python: Revert buggy gitpython version

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: python: Revert buggy gitpython version
Additional Description:
version 3.1.15 has been yanked from pypi for being "too buggy"
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

/lgtm deps


Cirtical Error using mythril Docker

Description
After pulling latest mythril Docker from docker hub, i tried to analyze a smart contract.
myth analyze throws Critical Error and aborts.
How to Reproduce
sudo docker run -v /home/zotac/BA:/tmp mythril/myth analyze /tmp/Contract.sol
mythril.mythril.mythril_analyzer [CRITICAL]: Exception occurred, aborting analysis. Please report this issue to the Mythril GitHub page.
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/mythril/mythril_analyzer.py", line 149, in fire_lasers
    sym = SymExecWrapper(
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/symbolic.py", line 163, in __init__
    self.laser.sym_exec(
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 175, in sym_exec
    self._execute_transactions(created_account.address)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 216, in _execute_transactions
    execute_message_call(self, address)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/transaction/symbolic.py", line 108, in execute_message_call
    laser_evm.exec()
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 253, in exec
    new_states, op_code = self.execute_state(global_state)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 335, in execute_state
    self._execute_pre_hook(op_code, global_state)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 654, in _execute_pre_hook
    hook(global_state)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/module/base.py", line 69, in execute
    result = self._execute(target)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/module/modules/state_change_external_calls.py", line 116, in _execute
    issues = self._analyze_state(state)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/module/modules/state_change_external_calls.py", line 180, in _analyze_state
    issue = annotation.get_issue(global_state, self)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/module/modules/state_change_external_calls.py", line 61, in get_issue
    solver.get_transaction_sequence(
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/solver.py", line 65, in get_transaction_sequence
    model = get_model(tx_constraints, minimize=minimize)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/support/model.py", line 57, in get_model
    result = s.check()
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/smt/solver/solver_statistics.py", line 19, in function_wrapper
    result = func(*args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/smt/solver/solver.py", line 55, in check
    evaluate = self.raw.check(args)
  File "/usr/local/lib/python3.8/dist-packages/z3/z3.py", line 7534, in check
    return CheckSatResult(Z3_optimize_check(self.ctx.ref(), self.optimize, num, _assumptions))
  File "/usr/local/lib/python3.8/dist-packages/z3/z3core.py", line 4468, in Z3_optimize_check
    _elems.Check(a0)
  File "/usr/local/lib/python3.8/dist-packages/z3/z3core.py", line 1420, in Check
    raise self.Exception(self.get_error_message(ctx, err))
z3.z3types.Z3Exception: b'push canceled'

Expected behavior
analysis of the given smart contract
Environment
Docker Image: mythril/myth:latest
created (local)  2020-11-14 09:48:07

It's an issue with unit propogation timeout in current version of z3 library which mythril uses. It may be fixed in a new version or z3py .

I encountered the same issue, which are not always reproducible. When this issue occurs, final results (with -o json option) are not properly generated, i.e., threre are not records such as "success": false.

This problem appeared only once.
Another run worked without problems.
But this error appears permanently with the -t option.
mythril.mythril.mythril_analyzer [CRITICAL]: Exception occurred, aborting analysis. Please report this issue to the Mythril GitHub page.
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/mythril/mythril_analyzer.py", line 149, in fire_lasers
    sym = SymExecWrapper(
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/analysis/symbolic.py", line 163, in __init__
    self.laser.sym_exec(
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 175, in sym_exec
    self._execute_transactions(created_account.address)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 216, in _execute_transactions
    execute_message_call(self, address)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/transaction/symbolic.py", line 108, in execute_message_call
    laser_evm.exec()
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 258, in exec
    new_states = [
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/svm.py", line 261, in <listcomp>
    if state.world_state.constraints.is_possible
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/ethereum/state/constraints.py", line 32, in is_possible
    get_model(tuple(self[:]))
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/support/model.py", line 57, in get_model
    result = s.check()
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/smt/solver/solver_statistics.py", line 19, in function_wrapper
    result = func(*args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/mythril-0.22.14-py3.8.egg/mythril/laser/smt/solver/solver.py", line 55, in check
    evaluate = self.raw.check(args)
  File "/usr/local/lib/python3.8/dist-packages/z3/z3.py", line 7534, in check
    return CheckSatResult(Z3_optimize_check(self.ctx.ref(), self.optimize, num, _assumptions))
  File "/usr/local/lib/python3.8/dist-packages/z3/z3core.py", line 4468, in Z3_optimize_check
    _elems.Check(a0)
  File "/usr/local/lib/python3.8/dist-packages/z3/z3core.py", line 1420, in Check
    raise self.Exception(self.get_error_message(ctx, err))
z3.z3types.Z3Exception: b'push canceled'```

@KurtMerbeth , can you provide the BadBet contact in that case, as that might be helpful.

@KurtMerbeth , can you provide the BadBet contact in that case, as that might be helpful.

BadBet.sol

This should be fixed in the develop branch.


Add Teach Yourself Programming in Ten Years

A useful post for someone learning to program

Good suggestion: "Teach Yourself Programming in Ten Years"

Good stuff 👍


Add the create_policy variable to allow users attach their own policy

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?
I want to have the ability to attach my own policy on the addons without having to create the default one, this is an existing faction of the addon module.

Describe the solution you would like
adding the variable create_policy to the modules addons

Describe alternatives you have considered

Additional context

one of the main intents of this module is to make it easy to deploy commonly used addons. what is the benefit here if the policy is not created - then its simply an IAM role and a helm release resource

hi Bryan, the idea would be that use user can create their own more fine grained policy that they want to attach to the sa role. You can already disable the create of the default role its just an enchantment in case the use wants to keep the role but just go in more detail about the policy that they will use for this role :)

I think at that point, you are better off creating your own role and helm release

I will message you internally as well to explain more in detail the reason of the pull request :)

if they want to continue on this route, they can roll their own version of this module (i.e. - fork it), or they can leverage the underlying module we use https://github.com/aws-ia/terraform-aws-eks-blueprints-addon and pass in their own values
Closing this out for now


Password Org Reset Feature (web)

Functional Requirements
The web app must offer a password reset feature.
The app must send a password reset link to the organizer's email.
Non-Functional Requirements
The password reset process must adhere to security best practices.
The password reset email should be received by the user within 5 minutes.
Dependencies
Existing log-in functionality.
Supabase configuration for email services to handle password reset.
Resources
https://supabase.com/docs/guides/auth/auth-password-reset
https://supabase.com/docs/guides/auth/auth-email-templates
Implement password reset request feature - 4 hours

Completed


Translations of views don't load (revert to English)

The translation of views (Trending, New, etc.) don't load. It shows the original (English) text there, while shows the translated (Hungarian) text everywhere in the app.
I've experienced this once in the past, but the problem disappeared while I used the app.
I've updated the app, and the problem came back.
I'll update this when I've found out how it started working before.

Thank you for reporting, translation of filters are not instant. But once you choose any other filter it should update with next language text. noted this to fix in upcoming release!

I've tried changing between filters. They didn't update for me. Strange, because the solution was something like that.

It's reloaded finally, when I changed not these filters (New, Trending, etc.) but navigating in the app menu. I visited the Market Place, though I don't think that specific detail matters but the fact that I moved away from Home and came back to it.

As we have discussed in steemit.chat #esteem in next release we will have app reload when language is changed.

Please also confirm if this is resolved on your devices.

This was the first thing what I've done after refreshed the app (reading you announcement meanwhile).
I have to say that the problem still exist.
To make sure, I've changed the language to Dolan (it's fun) and changed back to Hungarian. The app has been reloading each time, and the filters changing to the expected words.
However, after I close the app and start it again, the filters reverts to English, no matter which language I'm using.

Thank you, great find...   v1.3.8 uses get_state api that fetches post and comments and author details with one request but there is downside of processing all that data. I think it might be causing long delay when we have 40+ comments, need optimization

thank you @tibonova, found the issue right after your detailed report.

Closing this, if you encounter this again, please let me know. Thank you!


replace request.context with request.locals

Implements the first part of https://github.com/sveltejs/kit/issues/984#issuecomment-830656946
Before submitting the PR, please make sure you do the following

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

This is another PR that will cause checks to fail until we release a new version — in this case because https://netlify.demo.svelte.dev/ won't build and deploy itself until @sveltejs/kit@next uses request.locals instead of request.context


How could I install this?

This may trivial but I don't know how to install and use it .. would you mind give me how I could compile this?

This repo is not active nor supported.  It was a quick experiment that was never really used...


static Contact.find() / static Contact.findAll() throws exception

Actual behavior
Contact.find() related functions always throw exceptions:

static Contact.find(query: Query) Promise
static Contact.findAll(query: Query) Promise

Steps to reproduce the behavior (and fixes, if any)
try {
    const contactFindByName = await Contact.findAll( );
} catch (ex) {
   console.log(`${ex}`);
}

Log output:
========
Error: id must be string. found: undefined
    at new Contact (/wechaty/dist/src/contact.js:45:19)
    at Wechaty.onMessage (/bot/controller/message.js:83:19)
    at emitOne (events.js:96:13)
    at Wechaty.emit (events.js:191:7)
    at PuppetWeb.<anonymous> (/wechaty/dist/src/wechaty.js:235:31)
    at emitOne (events.js:96:13)
    at PuppetWeb.emit (events.js:191:7)
    at PuppetWeb._callee5$ (/wechaty/dist/src/puppet-web/event.js:289:18)
    at tryCatch (/wechaty/node_modules/regenerator-runtime/runtime.js:65:40)
    at Generator.invoke [as _invoke] (/wechaty/node_modules/regenerator-runtime/runtime.js:303:22)
    at Generator.prototype.(anonymous function) [as next] (/wechaty/node_modules/regenerator-runtime/runtime.js:117:21)
    at fulfilled (/wechaty/dist/src/puppet-web/event.js:4:58)
    at tryCatcher (/bot/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/bot/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/bot/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/bot/node_modules/bluebird/js/release/promise.js:614:10)

try {
    const contactFindByName = await Contact.find({ name:"ContactName"} );
} catch (ex) {
   console.log(`${ex}`);
}

Log output:
========
Error: id must be string. found: undefined
    at new Contact (/wechaty/dist/src/contact.js:45:19)
    at Wechaty.onMessage (/bot/controller/message.js:83:19)
    at emitOne (events.js:96:13)
    at Wechaty.emit (events.js:191:7)
    at PuppetWeb.<anonymous> (/wechaty/dist/src/wechaty.js:235:31)
    at emitOne (events.js:96:13)
    at PuppetWeb.emit (events.js:191:7)
    at PuppetWeb._callee5$ (/wechaty/dist/src/puppet-web/event.js:289:18)
    at tryCatch (/wechaty/node_modules/regenerator-runtime/runtime.js:65:40)
    at Generator.invoke [as _invoke] (/wechaty/node_modules/regenerator-runtime/runtime.js:303:22)
    at Generator.prototype.(anonymous function) [as next] (/wechaty/node_modules/regenerator-runtime/runtime.js:117:21)
    at fulfilled (/wechaty/dist/src/puppet-web/event.js:4:58)
    at tryCatcher (/bot/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/bot/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/bot/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/bot/node_modules/bluebird/js/release/promise.js:614:10)

Have you import Contact as you import wechaty do?

Yes, already imported.
const { Message, MediaMessage, MsgType, Contact } = require('wechaty');

Well, could you try the following code:
import { Wechaty, Contact } from 'wechaty'

@lijiarui No, this problem will not appear if the import/require fail.
@galendai Could you please provide the full shortest code that can reproduce this error?
I'm afraid that there's some bug in your code because inside the Wechaty Framework itself, we will always provide the right id .

@zixia ouch, u are definitely correct. I incidentally create an new instance without giving id in constructor and it's not related to the static methods at all.
Really appreciated for both of you & @lijiarui 's attentions.
this issue is safe to close now.

Great to hear that, cheers!


[WIP] Execute SG changes e2e tests

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/test all

/retest

Closing in favor of  #194


RedisClusterMgt Nodes function throwing an exception when there is more than 2 flags

When a node has more than 2 flags, RedisClusterMgt.Nodes will throw an exception during the split of flags.
In my case, the flags are "slave,fail,noaddr"

Hi.
Nice find. It should be easy to fix. Instead of allways assuming the role is the second value, it should be better to just check if master or slave is in the flags block.

@piront Closing this because of the merged PR you submited before


Anyone has UPDATE?

Hi,
Does anybody has update i know R3nzSkin'll not comeback since it loads in memory and vanguard block that, but maybe do you have any informations or discord/ about a future skin changer, thanks.
Btw don't use : GadzoSense, this guy is a pure scammer all his versions of skin changer are not working take care.

If you find one let me know too


[AutoPR network/resource-manager] Swagger support for DDoS protection policy customization feature

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4441

(message created by the CI based on PR content)

PR was closed


[Question] LazySentry.ts -  how does errorQueue work?

errorQueue.forEach(x => window.onerror?.(...x));
rejectionQueue.forEach(e => window.onunhandledrejection?.(e));

Hey Daniel, can you please comment this piece of code?
How does this work? I guess "Sentry Init" replaces window.onerror with its "global handlers"?
Couldn't find in source code of sentry-js
@Daniel15

Yes, Sentry attaches its own onerror handler. I think it's here, but I'm not entirely sure what the code is doing: https://github.com/getsentry/sentry-javascript/blob/ac3cf2023d577de920febd346b827020f6ca2e0c/packages/browser/src/integrations/globalhandlers.ts
I just noticed it as a user of the library - after loading it, there's an onerror handler, so I rely on that :smiley:  I didn't actually investigate how the Sentry JS code works.


Using arrows for navigation

Is there a built-in option for the navigation to be controlled by the up and down keyboard arrows?
Thanks!

works for me like this

And then on the next arrow you specify the other data-menu-top for the next slide


Is headless raspberry possible?

Hello, I was testing the code and I setup a headless raspberry with only ssh access, and whenever i tried the sample for still images it is givingme a GTK warning, no display was found, I was wondering if you can point me in the right direction to create a new screenshot with the details of the recognized object.
Greetings!

nevermind, I just saw the parameters in the file

Hey, thanks for closing the issue! If you're in headless mode, you can't display any images with cv2.imshow, or you will get an error. Instead, you can add something like print(object_name) after line 207 to make it print each object that's detected.


What's the recommended approach for user roles?

The docs mention using the extended plug to check for an admin role, but how should that data be set on the user?  If I simply add a role field to the user table it still won't be present on the AccessPass.Users record.
Thanks!

Sure, so extended plug does comparison inside the user meta objects. So if you had
plug AuthExtended, role: "admin"
it would check the uses meta object(that was stored on registration) for the key of role that equals value of "admin".
So all things you want to compare against in the keyword list passed to the plug are compared in the users meta object.

Great!  Last question: how can I make sure users can't make themselves admins?  Normally I'd filter out that field in my controller if the user isn't an admin.

Sure so you can do that a couple different ways.
You can run your own custom validation on the changeset to include/exclude roles in the meta object using the custom_user_changes behavior.
Or
You could do the same custom validation logic and use insert_override to handle the changeset insert yourself.
https://hexdocs.pm/access_pass/AccessPassBehavior.html

If for example you don't want users to add role to the meta on registration you would do something like follows inside the custom_user_changes behavior
put_change(changeset, :meta, %{})
This would update the meta object to empty regardless of what the users passed in.

Awesome, that's a very elegant solution.  Thanks!

No problem! Thanks for all the feedback through github issues! I have a project I have been working on for quite a while that is going through a closed private beta shortly I would love feedback on if thats something that might interest you. It is actually the reason I made accesspass in the first place.
Information on the project:
https://medium.com/appdoctor/what-is-appdoctor-5cceaedf7a05
email<EMAIL_ADDRESS>if interested so I can send you a key when we add our next group to the closed beta!


More rounded tabs

Description
I installed latest theme version (v24.4.10), but more rounded tabs not more rounded. Is it normal? Should I do something to switch them on?

Configuration

Firefox Version: 125.0
OS: KDE Neon 6.0

The more rounded tabs are enabled with the rounded browser corners tweak (uc.tweak.rounded-corners).

Yes, now it works as it should.
P.S. Many thanks for beautiful theme!


[ICONS] remove deprecated shapes for 1.0

This removes the eye and eye-hide alias since they were moved to the core.

We should also remove them from essential-shapes.ts.


cpp-netlib: remove insecure openssl dependency and unnecessary asio

Upstream openssl has dropped support for 1.0.2; see #77503 for details. This
also cleans up the old asio dependency, which now comes from boost, and
documents why the test driver fails.
CC @vcunat

Motivation for this change
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build cpp-netlib


MissionGroup musicTrack?

We send a musicTrack in this line:
https://github.com/Areloch/Torque3D/blob/BaseGameTemplate/Templates/BaseGame/game/data/clientServer/scripts/server/levelDownload.cs#L54
But we do not receive it in the other end, nor use it for anything. It's unused. I think we can safely delete it.

Cleaned up


chore(deps): bump

Applied mkpr on undefined
/tmp/mkpr.sh

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Disable both public facing Froware sites (Wordpress site and Discourse forum)

Requires definitions, we could use
As a user ...
I want to ...
Because ...

Acceptance Criteria ... (how do we know this is done?

WP shut down, Discourse staying online for dev/testing


chore: fix some comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Store set volume for each sound

Many sounds one could use have varying volume, or one does want to play the sound at another volume in combination with others. It would be nice if either:

the volume set in the player (in the right side bar) would be stored for that sound or
each sound had an additional option (like name and image) for setting an individual volume offset

Hi, thanks for the suggestion!
I'm currently working on an update which will include the ability to set the default volume for individual sounds, so that the sound will always start with that volume.

Version 2.0 is now out, which includes both the ability to set a default volume for sounds and a simple fade out effect when closing a playing sound! Manually search for updates in the Microsoft Store to get it now.
Also see my blog post, where I described all other changes:
blog.dav-apps.tech/universalsoundboard-version-2-0


SIDE-988 - Update Go examples, add to test step

https://crosschx.atlassian.net/browse/SIDE-988

I mistakenly opened this PR using the wrong GitHub account. 😔 Will close and reopen.


Integration Test - Release - 2019/06/13 18:35:29

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#reassign PRMergerTest2

GitHub user PRMergerTest1 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.


Adds azureProperty property to handle backward compatibility when using the isBinary property

Closes #494

I'm not sure I understand the intent #494 references #311 which talks about property, this is true for all cases of returning binary data from a secret backend (some require isBinary to be set, some can detect automatically).
apiVersion: kubernetes-client.io/v1
kind: ExternalSecret
metadata:
  name: hello-service
spec:
  ...
  data:
    - key: hello-service/credentials
      name: password
      property: password # <--- this is unsupported with `isBinary`
      isBinary: true

I'm not sure what issue or use case you are trying to cover, would be great on you could elaborate.
It's correct that the Azure backend currently doesn't have feature parity with other backends outside of isBinary usage, there's some info in #460 which tries to resolve this allowing property to be used as expected (when not using isBinary)

Closing this until further discussion takes place.


[Bug]: Accordion heading not responding correctly on smaller screens

Describe the bug
When stacking on smaller screens, the smaller text and badge is too close to the edge of the accordion container.
Current:

Design intent:

Provide Code
No response
To Reproduce
Can see on Storybook
https://ui-components.alberta.ca/iframe.html?viewMode=docs&id=components-accordion--basic#secondary-text-and-badges
Relevant console log output
No response
What browsers are you seeing the problem on?
No response
Additional context
No response

:tada: This issue has been resolved in version 1.15.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.15.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.15.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.6.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


typeof abstract class do not allow typeof inherited classes

TypeScript Version:  3.3.3

Search Terms: typeof abstract class
Code
// Definition
export declare type PrimitiveType =
    "string" |
    "number" |
    "int8" |
    "uint8" |
    "int16" |
    "uint16" |
    "int32" |
    "uint32" |
    "int64" |
    "uint64" |
    typeof Schema;

export declare type DefinitionType = (PrimitiveType | PrimitiveType[] | {
    map: typeof Schema;
});

export declare type Definition = {
    [field: string]: DefinitionType;
};

export declare abstract class Schema {
    static _schema: Definition;
}

export declare function type(type: DefinitionType): (target: any, field: string) => void;

// Usage
class Player extends Schema {
    @type("string")
    name: string;

    constructor(param:string) { // this contructor creates the bug
        super();
    }
}

class State {
    @type({ map: Player }) // this doesn't work
    mapOfPlayers: { [id: string]: Player } = {};
}

Expected behavior:
Allow using { map: Player } with different constructor signature, as it calls super() properly
Actual behavior:
TSError: ⨯ Unable to compile TypeScript:
src/server/rooms/State.ts(13,9): error TS2345: Argument of type '{ map: typeof Entity; }' is not assignable to parameter of type '"string" | "number" | typeof Schema | "int8" | "uint8" | "int16" | "uint16" | "int32" | "uint32" | "int64" | "uint64" | PrimitiveType[] | { map: PrimitiveType; }'.
  Type '{ map: typeof Player; }' is not assignable to type '"string"'.

Playground Link:
https://typescript-play.js.org/?experimentalDecorators=true#code/PTAEBEFMDMEsDtYBdYHt4ChIA8AOqAnJUAE0gGMAbAQwMlCQE9d6AFA2AW2VgDdIAKs3oBeDKAmgARAGckHeAHMpoAD7jJU+AFdOAI0gEV6ydIRIAHMY0Sp281bU2z8JAEYAbNdN3zn75rmAMwATAG29q6h4S5IHgAsMb6uCTFMLKjQoADK5AAWkJzUANwYWHiExGRUtPTp9FBwiCjoQiygIqAAFOxcPPxt9KqgvdwoA8IA2gC6aqAA3s5FuABcDMKZOfmFJRgAvgCUpeX4RKQUNHTr7Y0IPOgdC86TcJCUJGtyCorTa7fNaHgg1Ke2OOFOVQutVA1D0X2o5GINRkMi2BSKT1McmoKHIoAA+jJtkU-jA7i14CCyuDKucaldoNp4IjAddIF16qSmvcgcIDmsObRFJAkGtqPBGAAaUCvd6feQIRQHDoAPlAvFQsBIxxAoAAqjJqMKMMjUawaIxDKAcEhIPASKjcujqJjJAABepdWQKpRSA7OeDUTiQeXfY6mcjoL7aRGELq4WhBlZfRXKxamLHaFgELpHMqmPb7MqmnJIHH0dPuz3zUDLNbm6iWgigQ5Lai4ADy0AbTZkaxrky1ocVvxGFqte0e81B+yAA
Related Issues:

https://github.com/Microsoft/TypeScript/issues/5843
https://github.com/Microsoft/TypeScript/issues/5236

I've edited my original post with an updated playground link!

This has been fixed defining a permissive constructor on Schema:
export declare abstract class Schema {
    static _schema: Definition;
    constructor (...args:any[]);
}

Not sure it's a bug though, hope you guys know :)

This is the expected behavior. Typescript issues an error because the constructor Schema takes no arguments, while the constructor of Player requires one. If your code were allowed this would be valid:
let cls: typeof Schema = Player;
class newCls extends cls {
    constructor() {
        super() // super call with no args, wops Player requires name
    }
}

The better approach to hold constructors that return Schema would be to use a constructor signature:
type Constructor<T> = new (...a:any[]) => Schema
export declare type PrimitiveType =
    "string" |
    "number" |
    "int8" |
    "uint8" |
    "int16" |
    "uint16" |
    "int32" |
    "uint32" |
    "int64" |
    "uint64" |
    Constructor<Schema>;

export declare type DefinitionType = (PrimitiveType | PrimitiveType[] | {
    map: Constructor<Schema>;
});

Although that will not allow abstract classes to be passed in. Or you can constrain prototype to allow abstract classes as well  (note: Schema as defined right now is equivalent to {} so any class will be accepted unless you define some members):
type AbstrctConstructor<T> ={ prototype: Schema }

thanks for clarifying @dragomirtitian <3


License

Congrats on this project.
Can you add a License please?
Thanks

https://github.com/VojislavD/TailwindCSS-Alpine.js-Template/commit/1b2673b3a828fb4efd2d2fdeae40af469bee4bb4


Set "extensionKind": "ui" to support remote development

Fixes #10. See that issue for details

Thanks for your support!


An uncaught Exception was encountered  Type: RuntimeException  Message: Unable to locate the model you have specified: CI_auth

An uncaught Exception was encountered
Type: RuntimeException
Message: Unable to locate the model you have specified: CI_auth
Filename: C:\wamp\www\CodeIgniter\ci_reg\system\core\Loader.php
Line Number: 344
Backtrace:
File: C:\wamp\www\CodeIgniter\ci_reg\application\controllers\Welcome.php
Line: 8
Function: model
File: C:\wamp\www\CodeIgniter\ci_reg\index.php
Line: 315
Function: require_once
I am a beginner in codeigniter. My website shows me this error. I want help for my problem and see which file work. it is also a help to solve this problem in codeigniter, please show me this link.

This is a bug tracker, not a helpdesk system.
Please ask your questions on our forums instead.


Fix missing parent attribute for icinga2_envzone

Previously parent variable was missing from template  in icinga2_envzone and thus does not show up in template file.

@rusia-rak 👍


Fix python bindings types cases

Python type names can be FooBar in some places and FOOBAR in others. Further, the serializer and deserializer functions will be serialize_FOOBAR and deserialize_FOOBAR. This naming misalignment causes errors, and this PR attempts to fix it.
I adjusted the example to generate both Javascript and Python bindings.
Also, the fix I implemented is quick and possibly not ideal in the context of the overall codebase. I have made the PR a draft PR as a result. Please let me know if there is a better way to achieve what I am trying to do.

Could you elaborate more, in which cases this can happen, with a small example?

Sure thing. Also, thanks for publishing this work in the first place. I have been using this crate in some form for about a year now. I started with the JS bindings but switched to Python, which wasn't as well supported as JS initially. Thus, I created an ugly, hacky fork for what I needed. I am working on a new project and noticed that Python support here has improved, so I am giving the upstream crate a second go.  If I can help improve Python support, I will try.
I created an example branch to showcase the issue I'm attempting to resolve.  See below.
https://github.com/nerwalt/postcard-bindgen/tree/python-issues-example/examples/no_std/no_std_bindings_py/src/no_std_bindings_py
In des.py, there is the following
T = TypeVar("T", Protocol, Packet, A1Meta)
def deserialize(obj_type: Type[T], bytes: bytes) -> T:
    d = Deserializer(bytes)

    if obj_type is PROTOCOL:
        return cast(T, deserialize_PROTOCOL(d))
    elif obj_type is PACKET:
        return cast(T, deserialize_PACKET(d))
    elif obj_type is A_1_META:
        return cast(T, deserialize_A_1_META(d))
    else:
        raise TypeError("{} not deserializable".format(obj_type))

However, the types in types.py are the following.  Note the name difference (e.g. PACKET in deserialize() and Packet in the types module).

class Packet:
    pass

@dataclass
class Protocol:
    packet: Packet

@dataclass
class A1Meta:
    name: str
    version: u16
    payload: list[u8]

class Packet_A1(Packet, tuple[A1Meta]):

    def __new__(cls, _0: A1Meta):
        return super(Packet_A1, cls).__new__(cls, (_0,))

    def __init__(self, _0: A1Meta):
        pass

    def __str__(self) -> str:
        return "{}{}".format("Packet_A1", super().__str__())

    def __format__(self, format_spec: str) -> str:
        return super().__format__(format_spec)

    def __repr__(self) -> str:
        return super().__repr__()

The name issue seems to arise from the following
// let obj_name = binding_type.inner_name().to_obj_identifier();
    let obj_name = String::from(binding_type.inner_name());

to_obj_identifier() converts the names to uppercase and snake case, which seems wrong.
Also, there is another issue that I fixed manually in the above example.  If you look at the previous commit of my issue example branch, you will see types.py as listed below.  The second issue is definition order (e.g. Packet is used in Protocol, but defined after Protocol). I think a topological sort of the structs/types before generation will address this, but I am not sure how to implement it yet.  There are probably other ways to address this too.
@dataclass
class Protocol:
    packet: Packet
class Packet:
    pass

class Packet_A1(Packet, tuple[A1Meta]):

    def __new__(cls, _0: A1Meta):
        return super(Packet_A1, cls).__new__(cls, (_0,))

    def __init__(self, _0: A1Meta):
        pass

    def __str__(self) -> str:
        return "{}{}".format("Packet_A1", super().__str__())

    def __format__(self, format_spec: str) -> str:
        return super().__format__(format_spec)

    def __repr__(self) -> str:
        return super().__repr__()
@dataclass
class A1Meta:
    name: str
    version: u16
    payload: list[u8]

While digging into the problem, I came up with the problem, when having two structs with the same name in different mods in rust, that two exact same named bindings will be generated #52. Maybe you have a suggestion how to fix.

I removed the String usage and implemented some of your suggestions.  I also did a few other cleanups.  This PR seems good for addressing the type naming errors.   I will look into definition order and #52  on a different branch.

Closing in favor of #55. Added all your @nerwalt suggestions there.


[BUG] Using the STATUS utils instead of direct numbers

Description
Currently, we have Status codes and Status messages that are configured for each of those codes that are being used. The goal is to replace any codes we find, with these , like 200 might be replaced with STATUSCODE.OK and then the message for some cases saying "Internal server error" might be replaced with STATUSMESSAGE.INTERNAL_SERVER_ERROR and so on.
Please ensure that this is done for all the codes in the project.
Screenshots

Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (blank for no).

Assignees me this issue

Hi @cu8code Thanks for showing interest, but never make a PR before you are assigned. Either ways, I'll check the PR shortly.


Some users reporting blank screen

The user in question said he was using iOS/Safari version 16.x (don't remember the minor version. I've used Testing back to iOS version 15 on BrowserStack, I get:
[Error] SyntaxError: Invalid regular expression: invalid group specifier name
	RegExp (index-Bmiwqowh.js:823:1872362)
	npe (index-Bmiwqowh.js:823:1872362)
	map
	Module Code (index-Bmiwqowh.js:823:1872308)
	evaluate
	moduleEvaluation
	(anonymous function)
	promiseReactionJob

Googling, it looks like Safari didn't support regex lookbehinds until very recently:
https://stackoverflow.com/a/51568859/2180570
https://caniuse.com/js-regexp-lookbehind
Working on a fix now.

Fixed with: https://github.com/colorado-cancer-center/ecco/commit/07292a324d02bbb773a3b788e4ce1a9b6d37b6f1 (verified on BrowserStack with iPhone 13, iOS/Safari version 15.4)


CSS missing

In the given example the css is forgotten and the rendered graphiql is styleless.

@aleksandrenko do you mean this live demo? For me it renders as expected - could you elaborate the problem you're having?

@aleksandrenko I had the same problem! I ended up having to require the grpahql css file into my index.js file like this require('../node_modules/graphiql/graphiql.css') and adding a css loader to my webpack config.

Thanks for the report. I added more to the README to explain the requirement of adding the CSS file to the page.

cool thanks @leebyron!


[eas-cli] Improve wording for version bumps

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Few wording/formatting changes suggested by Dominik.

/changelog-entry chore Improve wording on version auto-increment.


Repeat to connect to the server

Bug Report
For more information, see the CONTRIBUTING guide.
Prerequisites

[x] Can you reproduce the problem in a MWE?
[x] Are you running the latest version?
[x] Did you perform a search in the issues?

Environment Details and Version
macos
<EMAIL_ADDRESS>Description
Repeat to connect to the server
Steps to Reproduce
MWE

yarn && cd src/samples/sample-piral-core && yarn start
Modify any content of the file src/samples/sample-piral-core/package.json and commit to the staging area

Expected behavior
Do not restart the server repeatedly
Actual behavior
Repeatedly restart the server
Possible Origin/Solution
The content of the files package.json/.krasrc monitored by fs.watch has not changed, and the server has been restarted.

The content of the files package.json/.krasrc monitored by fs.watch has not changed, and the server has been restarted.

I don't understand this - the repro steps listen explicitly that the package.json should be modified - so yes, with such a modification the server should restart.
I'll have a look with the repro steps, but a server restart is expected if certain files changed (otherwise you'd need to manually shut down the server and restart it again).

Alright, so as this is an edge case (package.json changed, leading to a change for the dev server) we'll exclude it. This implies that changes to the package.json that affect the build (e.g., change of the "app" path) would require a fixed restart. I guess this is a good trade-off, as such scenarios rarely occur and often are expected to come with a manual server restart anyway.
The server would still restart on changes to the krasrc; as it might re-configure the server in crucial areas.

The server would restart multiple times on changes to the krasrc.
version: 1.5.4-beta.6998

The server would restart multiple times on changes to the krasrc. version: 1.5.4-beta.6998

This is also an edge case. This happens when app-shell's webpack.config.js configures a longer build.
But it no longer affects normal development. Thanks for the quick fix.


'true' result always return, when setting invalid data to 'access' properties

When setting properties of some repo, I found it reject invalid data. However, the response is always 'true', which seems to be some incorrect. right?
for example:
PUT -H "Content-Type: application/json" -k http://myregistry.io/v1/repositories/foo/bar/properties -d '{"access": "(invalid data)"}'
true
if it is a bug? Maybe we should add a judgement in registry properties function, which impact little to performance.
Thanks

GET and PUT properties methods lie in registry code. but it seems to do nothing.
maybe develops can do it in their own index. However, if it had better to be available and to be useful user?
Thanks.


TTL=0 too soon

via irc,
Version: 3.0.15
Code: https://github.com/immesys/wdd/blob/dev/actionRunner.go#L237-L253
Client-side logs:
began actionRunner at 2016-12-09 20:44:20.410794237 +0000 UTC
lease ID:<PHONE_NUMBER>250880988 &clientv3.LeaseGrantResponse{ResponseHeader:(*etcdserverpb.ResponseHeader)(0xc4206934e0), ID:1713998858250880988, TTL:60, Error:""}
lease problem (resp= &clientv3.LeaseKeepAliveResponse{ResponseHeader:(*etcdserverpb.ResponseHeader)(0xc4205cc440), ID:1713998858250880988, TTL:0}) at 2016-12-09 20:44:20.449213404 +0000 UTC<PHONE_NUMBER>250880988)
panic: etcdserver: requested lease not found

So it's triggering the TTL == 0 path in the client to report the lease is gone. However, given that there's a minute-length TTL, the TTL shouldn't be 0 so soon.
About 1/1000 chance of happening.

It's a cluster of 3 etcd machines, here are the logs for the three machines at the time this happened:
Server 3/3 application logs:
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: began actionRunner at 2016-12-09 23:20:38.280300978 +0000 UTC
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: lease ID:<PHONE_NUMBER>250893126 &clientv3.LeaseGrantResponse{ResponseHeader:(*etcdserverpb.ResponseHeader)(0xc420247aa0), ID:1713998858250893126, TTL:60, Error:""}
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: lease problem (resp= &clientv3.LeaseKeepAliveResponse{ResponseHeader:(*etcdserverpb.ResponseHeader)(0xc420247da0), ID:1713998858250893126, TTL:0}) at 2016-12-09 23:20:38.291247976 +0000 UTC<PHONE_NUMBER>250893126)
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: panic: etcdserver: requested lease not found
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: goroutine 30 [running]:
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: panic(0x90d6a0, 0xc420151a60)
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]:         /usr/local/go/src/runtime/panic.go:500 +0x1a1
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: main.actionRunner()
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]:         /home/immesys/w/go/src/github.com/immesys/wdd/actionRunner.go:256 +0x17f3
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: main.actionRunnerLoop()
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]:         /home/immesys/w/go/src/github.com/immesys/wdd/actionRunner.go:309 +0x22
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]: created by main.main
Dec 09 23:20:38 ip-172-30-2-86 wdd[9129]:         /home/immesys/w/go/src/github.com/immesys/wdd/main.go:142 +0x4c
Dec 09 23:20:38 ip-172-30-2-86 systemd[1]: wdd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 09 23:20:38 ip-172-30-2-86 systemd[1]: wdd.service: Unit entered failed state.
Dec 09 23:20:38 ip-172-30-2-86 systemd[1]: wdd.service: Failed with result 'exit-code'.
Dec 09 23:20:38 ip-172-30-2-86 systemd[1]: wdd.service: Service hold-off time over, scheduling restart.
Dec 09 23:20:38 ip-172-30-2-86 systemd[1]: Stopped wdd.
Dec 09 23:20:38 ip-172-30-2-86 systemd[1]: Started wdd.

Server 3/3 etcd logs:
Dec 09 23:15:25 ip-172-30-2-86 etcd[32563]: compacted raft log at 10636184
Dec 09 23:15:53 ip-172-30-2-86 etcd[32563]: purged file /srv/etcd/member/snap/000000000000001d-0000000000a19bcb.snap successfully
Dec 09 23:16:02 ip-172-30-2-86 etcd[32563]: apply entries took too long [10.319602ms for 1 entries]
Dec 09 23:16:02 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:16:15 ip-172-30-2-86 etcd[32563]: apply entries took too long [13.980275ms for 1 entries]
Dec 09 23:16:15 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:16:50 ip-172-30-2-86 etcd[32563]: store.index: compact 13997656
Dec 09 23:16:52 ip-172-30-2-86 etcd[32563]: finished scheduled compaction at 13997656 (took 1.111694177s)
Dec 09 23:17:48 ip-172-30-2-86 etcd[32563]: apply entries took too long [21.53577ms for 1 entries]
Dec 09 23:17:48 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:17:52 ip-172-30-2-86 etcd[32563]: apply entries took too long [10.891494ms for 1 entries]
Dec 09 23:17:52 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:17:57 ip-172-30-2-86 etcd[32563]: apply entries took too long [10.97979ms for 1 entries]
Dec 09 23:17:57 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:18:52 ip-172-30-2-86 etcd[32563]: apply entries took too long [16.315694ms for 1 entries]
Dec 09 23:18:52 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:19:54 ip-172-30-2-86 etcd[32563]: apply entries took too long [15.228846ms for 1 entries]
Dec 09 23:19:54 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:20:07 ip-172-30-2-86 etcd[32563]: apply entries took too long [14.42986ms for 1 entries]
Dec 09 23:20:07 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:20:18 ip-172-30-2-86 etcd[32563]: apply entries took too long [11.783642ms for 1 entries]
Dec 09 23:20:18 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:20:33 ip-172-30-2-86 etcd[32563]: apply entries took too long [10.887894ms for 1 entries]
Dec 09 23:20:33 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:20:49 ip-172-30-2-86 etcd[32563]: apply entries took too long [13.208403ms for 1 entries]
Dec 09 23:20:49 ip-172-30-2-86 etcd[32563]: avoid queries with large range/delete range!
Dec 09 23:21:09 ip-172-30-2-86 etcd[32563]: start to snapshot (applied: 10651185, lastsnap: 10641184)
Dec 09 23:21:09 ip-172-30-2-86 etcd[32563]: saved snapshot at index 10651185
Dec 09 23:21:09 ip-172-30-2-86 etcd[32563]: compacted raft log at 10646185
Dec 09 23:21:23 ip-172-30-2-86 etcd[32563]: purged file /srv/etcd/member/snap/000000000000001d-0000000000a1c2dc.snap successfully
Dec 09 23:21:29 ip-172-30-2-86 etcd[32563]: apply entries took too long [13.671298ms for 1 entries]

Server 2/3 etcd logs:
Dec 09 23:19:54 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:19:56 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.438076ms for 1 entries]
Dec 09 23:19:56 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:11 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.860611ms for 1 entries]
Dec 09 23:20:11 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:16 ip-172-30-0-123 etcd[16048]: apply entries took too long [19.643459ms for 1 entries]
Dec 09 23:20:16 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:22 ip-172-30-0-123 etcd[16048]: apply entries took too long [17.38268ms for 1 entries]
Dec 09 23:20:22 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:29 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.581141ms for 1 entries]
Dec 09 23:20:29 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:31 ip-172-30-0-123 etcd[16048]: apply entries took too long [10.472098ms for 1 entries]
Dec 09 23:20:31 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:37 ip-172-30-0-123 etcd[16048]: apply entries took too long [29.638966ms for 1 entries]
Dec 09 23:20:37 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:37 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.9494ms for 1 entries]
Dec 09 23:20:37 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:41 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.776336ms for 1 entries]
Dec 09 23:20:41 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:43 ip-172-30-0-123 etcd[16048]: apply entries took too long [13.208463ms for 1 entries]
Dec 09 23:20:43 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:50 ip-172-30-0-123 etcd[16048]: apply entries took too long [16.989491ms for 1 entries]
Dec 09 23:20:50 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:50 ip-172-30-0-123 etcd[16048]: apply entries took too long [12.737201ms for 1 entries]
Dec 09 23:20:50 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:20:51 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.580143ms for 1 entries]
Dec 09 23:20:51 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:21:02 ip-172-30-0-123 etcd[16048]: apply entries took too long [15.476916ms for 1 entries]
Dec 09 23:21:02 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:21:07 ip-172-30-0-123 etcd[16048]: start to snapshot (applied: 10651128, lastsnap: 10641127)
Dec 09 23:21:07 ip-172-30-0-123 etcd[16048]: saved snapshot at index 10651128
Dec 09 23:21:07 ip-172-30-0-123 etcd[16048]: compacted raft log at 10646128
Dec 09 23:21:08 ip-172-30-0-123 etcd[16048]: apply entries took too long [13.548155ms for 1 entries]
Dec 09 23:21:08 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!
Dec 09 23:21:09 ip-172-30-0-123 etcd[16048]: apply entries took too long [11.168493ms for 1 entries]
Dec 09 23:21:09 ip-172-30-0-123 etcd[16048]: avoid queries with large range/delete range!

Server 1/3 etcd logs:
Dec 09 23:19:13 ip-10-42-12-114 etcd[10497]: avoid queries with large range/delete range!
Dec 09 23:20:32 ip-10-42-12-114 etcd[10497]: apply entries took too long [12.001082ms for 1 entries]
Dec 09 23:20:32 ip-10-42-12-114 etcd[10497]: avoid queries with large range/delete range!
Dec 09 23:21:06 ip-10-42-12-114 etcd[10497]: start to snapshot (applied: 10651085, lastsnap: 10641084)
Dec 09 23:21:06 ip-10-42-12-114 etcd[10497]: saved snapshot at index 10651085
Dec 09 23:21:06 ip-10-42-12-114 etcd[10497]: compacted raft log at 10646085
Dec 09 23:21:27 ip-10-42-12-114 etcd[10497]: purged file /srv/etcd/member/snap/000000000000001d-0000000000a1c278.snap successfully
Dec 09 23:21:32 ip-10-42-12-114 etcd[10497]: apply entries took too long [12.646203ms for 1 entries]
Dec 09 23:21:32 ip-10-42-12-114 etcd[10497]: avoid queries with large range/delete range!
Dec 09 23:22:29 ip-10-42-12-114 etcd[10497]: apply entries took too long [13.096274ms for 1 entries]

For reference, the three servers are located in different EC2 regions. They have GP SSD drives. I haven't had time yet to work out why I am getting warnings about apply entries taking too long, I'm not an etcd expert. Not sure if this information was relevant.

@immesys https://github.com/coreos/etcd/blob/master/Documentation/faq.md#what-does-the-etcd-warning-apply-entries-took-too-long-mean explains why you see apply entries took too long warning. I think the limit is set to 10 ms for the version that you are using right now. it will be increase to 100ms in the coming up release.

@immesys what timezone are your other etcd servers live in? are they in same timezone? by default, etcd server side logging uses local timezone.
You client side logging indicate time in UTC and your server side logging might be using local zone. Could you double check that your previous logging pastes are time aligned correctly.

@immesys could you possibly provide a simpler script that I can reproduce the issue locally?

Sure I can try make one. I haven't had a chance to triple check my timezones but I usually keep all my servers in UTC so I would be surprised if the logs did not line up.

I was able to reproduce this with the stock 3-member goreman cluster on both 3.0.15 and master using tmpfs:
package main

import (
        "fmt"
        "github.com/coreos/etcd/clientv3"

        "golang.org/x/net/context"
)

func stress(s string) {
        cfg := clientv3.Config{Endpoints: []string{s}}
        cli, err := clientv3.New(cfg)
        if err != nil {
                fmt.Println(err)
                return
        }
        i := 0
        for {
                resp, gerr := cli.Grant(context.TODO(), 60)
                if gerr != nil {
                        panic(gerr)
                }
                _, kerr := cli.KeepAliveOnce(context.TODO(), resp.ID)
                if kerr != nil {
                        panic(kerr)
                }
                cli.Revoke(context.TODO(), resp.ID)
                fmt.Println(s, i)
                i++
        }
}

func main() {
        for i := 0; i < 10; i++ {
                go stress("http://localhost:2379")
        }
        stress("http://localhost:2379")
}

@heyitsanthony Do you know if I could switch to a different version in the meantime? Is this present in the 3.1 rc?

@immesys nope, this case looks all around broken, sorry :(
Now, this isn't a true fix, but since the cause may take some time to figure out: is there a reason why that code must immediately call KeepAliveOnce? I think this is a race isolated to creating renew streams. Another way to structure the loop without the KeepAliveOnce:
kactx, kcancel := context.WithCancel()
defer kcancel()
if _, err := cli.KeepAlive(kactx, leaseId); err != nil { panic(err) }
for _, ev := range resp.Kvs { ....}
cli.Revoke(context.Background(), leaseId)

This is a lot cheaper because it'll use a single renew stream per client and it keeps a timer so it doesn't have to send a keep alive message for every loop iteration. Even if it doesn't patch over the problem (it seems to mask it in the stress test), it'll still save some bandwidth.

@heyitsanthony Thanks! I'll change my code to do that.

I added some server side debugging for this issue by running @heyitsanthony's script.
The problem only occurs if the client talks to a follower not a leader. In that way, the follower must redirect Renew request to the leader. From the following log, you can see that the client Grant req returns before the leader stores the newly granted lease. Then immediately, client looks up the lease in the leader via redirect from the follower where leader hasn't store the lease yet, and then the leader couldn't find it. Thus, the leader returns requested lease not found error to client.
client (url: http://localhost:22379):
2016-12-13 13:25:41.9853106 grant lease id<PHONE_NUMBER>928416115
2016-12-13 13:25:42.0485981 renew lease id<PHONE_NUMBER>928416115

Server:
etcd1 is the leader
2016-12-13 13:25:41.985682 etcd2 | DEBUG EtcdServer.LeaseGrant() req {60<PHONE_NUMBER>928416115} leaseID<PHONE_NUMBER>928416115
2016-12-13 13:25:42.048048 etcd2 | DEBUG lessor.Grant() lease id<PHONE_NUMBER>928416115
2016-12-13 13:25:42.048053 etcd2 | DEBUG lessor.Grant() id<PHONE_NUMBER>928416115 updating le.leaseMap
2016-12-13 13:25:42.048059 etcd2 | DEBUG lessor.Grant() id<PHONE_NUMBER>928416115 updating le.leaseMap finished

// EtcdServer.LeaseGrant() returns when etcd2 finishes its lessor.Grant() but does not wait for other nodes to finish their lessor.Grant().

2016-12-13 13:25:42.048119 etcd2 | DEBUG EtcdServer.LeaseGrant() done resp (header:<revision:1 > ID:4703544691928416115 TTL:60 )

// client starts to call LeaseRenew() at this point.

2016-12-13 13:25:42.048932 etcd2 | DEBUG EtcdServer.LeaseRenew() leaseID<PHONE_NUMBER>928416115 I am not a leader
2016-12-13 13:25:42.048896 etcd2 | DEBUG lessor.Renew() I am not a primary lessor. Looking up lease id<PHONE_NUMBER>928416115

// etcd follower redirects LeaseRenew() req to the leader

2016-12-13 13:25:42.061091 etcd1 | DEBUG lessor.Grant() lease id<PHONE_NUMBER>928416115
2016-12-13 13:25:42.061171 etcd1 | DEBUG lessor.Renew() I am a primary lessor. Looking up lease id<PHONE_NUMBER>928416115
2016-12-13 13:25:42.061179 etcd1 | DEBUG lessor.Renew() I am a primary lessor. Looking up lease id<PHONE_NUMBER>928416115 not found

// lessor.Renew() could not find the lease because the original grant request has not being applied at etcd 1(leader) yet

2016-12-13 13:25:42.061295 etcd1 | DEBUG lessor.Grant() id<PHONE_NUMBER>928416115 updating le.leaseMap
2016-12-13 13:25:42.061304 etcd1 | DEBUG lessor.Grant() id<PHONE_NUMBER>928416115 updating le.leaseMap finished

The issue does not just affect the KeepAliveOnce() but also TimeToLive(). I replace  cli.KeepAliveOnce(context.TODO(), resp.ID) => cli.TimeToLive(context.TODO(), resp.ID) from @heyitsanthony's script. Same issue happens.

@immesys I pushed out a fix for this issue. If you checkout the latest version from etcd master branch, it should solve this problem. Please reach out if this fix doesn't solve this problem on your side.


Remove Debug from log

Can you remove the full debug from the log unless a debug flag is set.

Would someone help me with setting up my dev system. And so that I can create a pull request?

Can anyone help with this.


Bump Dependencies #2215950513

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/2215950513

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix VA search bug

During the protobuf conversion extend was incorrectly used. This bug caused repeated transcript effect records to appear in results. Fixing this bug revealed that the simulated stack tests for VA were incorrect and generated transcript effect records for the same alternate base repeatedly. This PR removes the uncecessary outer loop.
A test has been added to guard for this. Close #1294

+1.
We really should have tests for this sort of thing from real data also, but I think we need to tackle this as part of another update. Namely, I think we should change the current data driven tests framework to be an end-to-end test. That is, the client has the data (VCF file, BAM file, etc) that corresponds to a given ReadGroupSet, VariantAnnotationSet, etc, and then makes queries it knows should succeed or fail. This would plug a big gap in our current test coverage I think.
Anyway, that's off-topic on this thread.


meta: add nix tooling

Adds nix tooling to allow people to develop using nix dependencies.
Uses niv to pin nixpkgs, rust-overlay, and niv itself.
This will give Rust tooling that is up to date with rustc-1.64.0.

@cloudhead you happy to merge this?

@cloudhead you happy to merge this?

Happy is a big word :joy: I'm just getting used to the idea of having all these obscure nix files in my repo. Is there a way to like, tuck them away somehow?

You know like, .nix/, and have the shell/default files in there as well? That way it doesn't distract non-nix users?

You know like, .nix/, and have the shell/default files in there as well? That way it doesn't distract non-nix users?

Poor nix users trying to not distract non-nix users :(
I've pushed a change to do that and I can always start the shell with nix-shell .nix/shell.nix -- annoying but fair.


Fixed WSL2 support in Fork.RI

First problem found after upgrading to WSL2.

Great, thanks for testing and fixing.


Test failure in develop on all platforms

The CI for this trivial fix is failing on all interpreters for Appveyor and Travis. Fails locally as well with this error:
_____ [doctest] setuptools.command.develop.VersionlessRequirement __
200
201     Adapt a pkg_resources.Distribution to simply return the project
202     name as the 'requirement' so that scripts will work across
203     multiple versions.
204
205     >>> dist = Distribution(project_name='foo', version='1.0')
UNEXPECTED EXCEPTION: NameError("name 'Distribution' is not defined")
Traceback (most recent call last):

  File "~/.pyenv/versions/3.7.1/lib/python3.7/doctest.py", line 1329, in __run
    compileflags, 1), test.globs)

  File "<doctest setuptools.command.develop.VersionlessRequirement[0]>", line 1,
     in <module>

NameError: name 'Distribution' is not defined

Seems like it's a doctest failing.

Looks like this commit is the problem: 0902f02d9d68f18e906e727cbafa4a05fe5c9c91, because Distribution is no longer in the namespace of the doctest.

Gah. Sorry about that. Thanks for chasing this down. I probably missed that usage because I was relying on the linter for finding the names.

@jaraco No harm no foul, though I think it would be best to go through the motions of a PR next time, even if you just do a self-merge. It's helpful for catching stuff like this.

Closed by #1613

I think it would be best to go through the motions of a PR next time.

The problem I have with this is it does increase the burden of making a contribution often to the point of making it infeasible in the time allotted. I usually have an implicit, manual check, where I'll notice if tests start failing after pushing a falsely-presumed error-free commit.
I agree with the concept though.
If I could create a command that could automate this operation, I'd be all in favor of it.
I've started looking into using hub. It looks like it can create a pull request but not set it for merge automatically. It's also not yet clear to me if it can correctly automatically detect the correct fork/branch for the source and target. But if it can, that almost streamlines the process.

I successfully created #1615 from the command-line with a simple hub pull-request invocation after pushing the branch. Hmm. Looks like GitHub doesn't support automatic merges, but there is a service called mergify, which I've enabled on this repo.
It's going to take some work to understand what the implications are of this - can mergify be readily installed on repos? Can it discern which pull requests should be automatically merged (and how)?

I've created a new rule that will automatically merge any PR with the auto-merge tag present. I still see two issues with this workflow. First, it would allow any user to use this feature (I think I can restrict it to a team). Second, it leaves the branch in the remote and local repos, and I don't see a way to mechanize the removal of either... so you'll start to get lots of stale, merged branches.

Huh. For some reason, it seems the setuptools-developers team isn't a team login. Only a team login is suitable for designating the allowed authors. So I've just set it to jaraco instead. ...until that issue can be sorted out. I've spent way too much time on this already.

The problem I have with this is it does increase the burden of making a contribution often to the point of making it infeasible in the time allotted. I usually have an implicit, manual check, where I'll notice if tests start failing after pushing a falsely-presumed error-free commit.

Generally I find that my contributions are not time-sensitive, so "make a PR" and "push to master" are roughly equivalent - both put the code on github and since it's very rare for me to not hit the "merge" button before a new release is cut, the effect is about the same. I personally prefer to let my PRs act as "drafts" that I can look at with fresh eyes before the merge if I have time and also that anyone can review.
That said, occasionally my changes are blocking stuff on master (like PR #1613, which was blocking the CI for everyone), so in that situation I can see how the PR workflow would just get in the way (though usually I still need a PR because the stuff blocking on master is almost always something about the CI itself that I need to fix).
In any case, everyone has their own way of working, and I don't think there's a single "right way". I think your solution of adding an auto-merge bot that just merges PRs that pass the CI is a great solution. It gives us the quality assurance of CI, the notification mechanism of a PR (I don't think people watching the repo get notifications of pushes to master - I certainly don't), and facilitates your contributions to the project, so it's a win all around! 🎉


Importing TypeScript files from node_modules causes errors

When importing TypeScript files and trying to build a project, the build fails saying the (typescript) files are "unsupported" and may need an "appropriate loader" to handle them. I'm using awesome-typescript-loader though.
If you would like to see the repository, you can find it here.
yarn run v1.17.3
$ yarn clean && webpack --config config/webpack.config.ts
$ rimraf lib
Using . in C:\Users\adria\Desktop\XplorationByAdrian\touch
Using lib in C:\Users\adria\Desktop\XplorationByAdrian\touch\lib
Using tsconfig.json in C:\Users\adria\Desktop\XplorationByAdrian\touch\tsconfig.json
Using package.json in C:\Users\adria\Desktop\XplorationByAdrian\touch\package.json
Using src in C:\Users\adria\Desktop\XplorationByAdrian\touch\src
Using node_modules in C:\Users\adria\Desktop\XplorationByAdrian\touch\node_modules
i ｢atl｣: Using<EMAIL_ADDRESS>from typescript
i ｢atl｣: Using tsconfig.json from C:/Users/adria/Desktop/XplorationByAdrian/touch/tsconfig.json
i ｢atl｣: Checking started in a separate process...
i ｢atl｣: Time: 648ms
Hash: da2bbabc48518ffba1e2
Version: webpack 4.40.2
Time: 2656ms
Built at: 10/11/2019 1:33:08 AM
 1 asset
Entrypoint main = touch.js
 [7] ./src/touch.ts 350 bytes {0} [built]
[11] (webpack)/buildin/module.js 497 bytes {0} [built]
[16] external "os" 42 bytes {0} [built]
[20] ./src/CommandEcho.ts 365 bytes {0} [built]
    + 17 hidden modules

ERROR in ./node_modules/xba-houston/src/ICommand.ts 1:7
Module parse failed: Unexpected token (1:7)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> export interface ICommand {
|   /**
|    * Gets the name of the command.
 @ ./node_modules/xba-houston/src/index.ts 5:0-38 5:0-38
 @ ./src/touch.ts

ERROR in ./node_modules/xba-houston/src/CommandBase.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { ICommand } from './ICommand';
|
> export abstract class CommandBase implements ICommand {
|   public version?: string;
|
 @ ./node_modules/xba-houston/src/index.ts 1:0-44 1:0-44
 @ ./src/touch.ts

ERROR in ./node_modules/xba-houston/src/ICommandManager.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { ICommand } from './ICommand';
|
> export interface ICommandManager {
|   /**
|    * Attempts to execute a command
 @ ./node_modules/xba-houston/src/index.ts 6:0-52 6:0-52
 @ ./src/touch.ts

ERROR in ./node_modules/xba-houston/src/CommandHandler.ts 4:10
Module parse failed: Unexpected token (4:10)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export class CommandHandler {
>   private readonly commandMap: Map<string, ICommand> = new Map<
|     string,
|     ICommand
 @ ./node_modules/xba-houston/src/index.ts 2:0-50 2:0-50
 @ ./src/touch.ts

ERROR in ./node_modules/xba-houston/src/HoustonCommandManager.ts 6:10
Module parse failed: Unexpected token (6:10)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export class HoustonCommandManager extends CommandHandler {
>   private readonly houston: Houston;
|   public constructor(houston: Houston) {
|     super();
 @ ./node_modules/xba-houston/src/index.ts 4:0-64 4:0-64
 @ ./src/touch.ts

ERROR in ./node_modules/xba-houston/src/Houston.ts 6:9
Module parse failed: Unexpected token (6:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export class Houston {
>   public readonly commandManager: ICommandManager;
|   /**
|    *
 @ ./node_modules/xba-houston/src/index.ts 3:0-36 3:0-36
 @ ./src/touch.ts
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It looks like you just deleted/ignored our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.

You excluded node_modules from the typescript loader.


L515 - Can't get range over 3.5m

Required Info

Serial Number
f1062522

Camera Model
L515

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win10/Ubuntu 18.04

Kernel Version (Linux Only)

Platform
x86PC

Issue Description
<Describe your issue / question / feature request / etc..>
My L515 was still working yesterday but suddenly I can't detect objects four meters away. I didn't change any settings, and the sensors didn't suffer any damage.  I rebooted the firmware but nothing improved.Would you please tell me how did you solve this problem?Any help would be greatly appreciated.

Thanks.

Hi @xyxegle  First, please try setting the Preset to Low Ambient Light.  This setting uses maximum laser power like the Max Range setting does but takes account of low ambient lighting if the lighting level has reduced.

Under the Depth Visualization category of the options side-panel of the Viewer, also check that the Max Distance setting is at its default of '16'.

Thank you for your reply. I just tried it again. I found that the depth data returned to normal without adjusting the parameters.
I remember that I had been using it from last night until today. Finally, it overheated and the data became abnormal. Anyway, thank you very much for your careful reply to my question, and I hope RealSense can provide better sensors soon.

Thanks very much @xyxegle for the update - it's excellent to hear that your camera is operating normally.

Case closed due to solution achieved and no further comments received.


The duration of audio is different with Wavesurfer and Audio Element

Hi everyone,
I was trying to sync WaveSurfer element with a audio player(I'm using videojs). Then I figured out that there is a strange difference on durations between wavesurfer and videojs. Then I have tried with a native audio element then the problem is the same.
I have created a codesandbox to reproduce the issue. When you open the project, you will see the durations computed by audio element and wavesurfer are not the same. I have used two different sources. You can change and see the problem with different audio file types.
What is wrong with the durations? Am I missing something?
Thanks
Wavesurfer version: 4.4.0

It's primarily how web audio analyzes the audio length, when using web audio it is more accurate in the actual precision of the duration in web audio processing.
You can always set the backend: "MediaElement" option which will use media element and have the same duration as an audio element already on your page.


[Publisher][API Lifecycle] When API deployed as prototype, lifecycle image show a transition to published state

Description:
When an API deployed as prototype, lifecycle image show a transition to published state but the corresponding action button is not there.

Steps to reproduce:

Create an API
Deploy it as a prototype

Affected Product Version:

Environment details (with versions):

OS:
Client:
Env (Docker/K8s):

Optional Fields
Related Issues:

Suggested Labels:

Suggested Assignees:

I think we should support the transition from prototype to published , it's a valid case

This is now fixed with Pre-release state.


Automate nix flake update PRs

fixes  #4817

I think this would have been more efficient if DPC just did it himself. Too much review time wasted here already.


Use zero width join character for better rendering in Chrome

@ichord @chrisfay
This PR switches Editable Controller from using the word joiner character to using the zero width joiner character.  The normal word joiner, \u2060, is broken in my version of Chrome (46.0.2490.86, 64 bit) on mac:

Using the zero width joiner seems to accomplish the same things while rendering properly.

@wbw20 Cool. Thanks.


How to catch dropdown change event in directive?

I'm using this dropdown modules. I want to ask, how can i catch when i select item dropdown change event in directive?
I can catch event in controller, but i can not catch event in directive.. How should i use in directive?

Use onItemSelect attribute, like in #39 in PawelDecowski's example. There are no examples on the GitHub Pages, and the author will most likely not provide documentation for this on his GitHub Pages site as he is writing a new dropdown-multiselect module to supersede this one.

I'm using onItemSelect event already. There is no problem for this.. My ask, How to catch dropdown change event in directive? I catching in the Controller, its working.. but this is not good code. I want to use in Directives. Do you understand me?

That should work fine. Do you have an example of your code? Maybe a plunker?

onItemSelect works fine, but my question is can you attach a function on onItemSelect. I was successful in doing it like $scope.example9event = {onItemSelect: function(){ alert(); }}; But i want to know if can do it like $scope.example9event = {onItemSelect: $scope.myFunction()}; and i have declared the myFunction in the same controllerm, any help would be much appreciated. Thanks Mukthi

Solved it
$scope.example9event = {onItemSelect: function() { myFunction() } };
Thanks :)

How can i send parameters to the events.
<span ng-dropdown-multiselect="" options="allUsers2" selected-model="Others"  events="multiuserevents" extra-settings="multiuserSetting" translation-texts="multiuserTexts" >                                                             </span>
` $scope.multiuserevents = {
onSelectionChanged: function (item) {
$scope.myFunction(item);
},
};`

Need to pass parameters to the onSelectionChanged Event


response failed error

I get a lot of those errors when I want to start a node:
WARN request{route=/sui.StateSync/GetCheckpointSummary remote_peer_id=13783584 direction=outbound}: anemo_tower::trace::on_failure: response failed error=Error: closed latency=0 ms
What does this mean? What can I do to resolve this?

It means your node was trying to download checkpoint information from a remote node and the connection was closed before the request completed. This is not in itself particularly a cause for concern. Do you have any functional issues aside from log messages?


'My Dashboard' and 'Create plan' not visible for non-admin users

When I log in as a regular user (non-admin) I don't see the nav options for 'My Dashboard' or 'Create plan' (screenshots below). They appear for Org and Super Admins as expected. Just need to replace them for non-admin users.

yep. this is working as expected now.


Configuration example

Can the AutoTunnel be used like Proxifier?  Basically I want use AutoTunnel to intercept the TCP and UDP traffic to a private IP address and send them to a public server which has the forwarded port .
If you can give a picture like the following
Client computer (gray ip, NAT) <-> Router <-> (Internet) <-> Router     <-> Proxy       <-> Server (NAT)
<IP_ADDRESS> <-> <IP_ADDRESS>|<IP_ADDRESS>  <-> (Internet) <-> <IP_ADDRESS> <-> <IP_ADDRESS> <-> <IP_ADDRESS>
and specify their roles (tunnelhost, connecthost, proxyhost) and the config.json file for each, specify the network border, it would be better to use.

Sorry for delay.
I'll try to clarify these situation in documentation.
In your case (public server with forwarded port) you should not use proxy. You need to specify tunnelHost to your public server and connectHost to private IP address


Fix grass

This isn't quite ready yet, as I think the grass offsets in the game aren't appropriate here, I'm just not totally sure why.

That's much better, thank you.


"Hamburger" menu is being blocked on few websites (generic Elementor dialogs blocked)

Hey,
Thanks a lot for a great app! I'll try to contribute myself with code, once have time learning how the extension works, but meanwhile hope this report will be useful. I've installed the extension yesterday, and noticed on 2 websites, that a commonly used pattern with hidden menu (opened with a hamburger icon button) is not working on mobile devices (narrow screen).
I could reproduce it both on desktop and iOS Safari. I found that the extension is injecting a big CSS selector with somehow forced highest specificity, and in this case, it's .elementor-popup-modal.dialog-widget selector that's blocking the mobile menu. It looks like the selector is too generic, and blocks some standard classnames from a library component (actually a wordpress site builder), that could be used for virtually any dialogs, not only cookies.
One of the websites I've noticed this on is https://protosmanagement.com (the other website is behind auth).
Hope you will consider removing this generic popup selector, as I imagine it will block a variety of functional popups across many wordpress websites.

This should be fixed by #82


Fix more threading issues

This fixes a number of threading issues:

Ensure the EVP_PKEY operation_cache is appropriately locked

The EVP_PKEY operation_cache caches references to provider side key
objects that have previously been exported for this EVP_PKEY, and their
associated key managers. The cache may be updated from time to time as the
EVP_PKEY is exported to more providers. Since an EVP_PKEY may be shared by
multiple threads simultaneously we must be careful to ensure the cache
updates are locked.
Fixes #13818

Don't update rate_limit every time we call ossl_prov_is_running()

Thread santizer was complaining about the unlocked update to the static
variable rate_limit in the FIPS module. In practice this is only important
in the event of the module having gone into the error state. Technically
this access should be locked, but it is only used to limit the rate of
errors that are raised on the error stack. It's not particularly important
if it gets this rate limiting wrong and a lock for this seems over the top.
So we just fix the concurrent access in the normal running state in order
to appease thread sanitizer, and ignore the concurrent access in the error
state.

Always ensure we hold ctx->lock when calling CRYPTO_get_ex_data()

Otherwise we can get data races.

Avoid races by caching exported ciphers in the init function

TSAN was reporting a race of the exported ciphers cache that we create in
the default and fips providers. This was because we cached it in the query
function rather than the init function, so this would cause a race if multiple
threads queried at the same time. In practice it probably wouldn't make much
difference since different threads should come up with the same answer.

Refactor RAND_get0_primary() locking

Make sure we never read or write to dgbl->primary outside of a lock.
I've also extended the multi-threads test. This was primarily with the objective of making tsan spot the unlocked operation_cache issue which was identified in #13818, but it also identified a number of the other issues above.
Finally I've added a CI build to run the threads_test with tsan on.

CI failures are relevant.

CI failures are relevant.

Fixups pushed addressing the feedback and  also hopefully addressing the CI failures. The operation_cache locking turned out to be insufficient, and I also reworked the locking in the self_test.c file.
Please take a look.

Fixups pushed addressing the feedback and  also hopefully addressing the CI failures. The operation_cache locking turned out to be insufficient, and I also reworked the locking in the self_test.c file.
Please take a look.

I have a nasty feeling that the key downgrade code is going to have big threading problems...but I haven't tested it yet and I probably won't bring that in to scope for this PR.

I have a nasty feeling that the key downgrade code is going to have big threading problems...but I haven't tested it yet and I probably won't bring that in to scope for this PR.

I have a nasty feeling that the key downgrade code is going to have big threading problems...but I haven't tested it yet and I probably won't bring that in to scope for this PR.

My suspicions are confirmed: #14020

I have a nasty feeling that the key downgrade code is going to have big threading problems...but I haven't tested it yet and I probably won't bring that in to scope for this PR.

My suspicions are confirmed: #14020

This pull request is ready to merge

Pushed. Thanks.

FYI I bisected to this commit that the tests are hanging on my FreeBSD system (in test_encoder_decoder_legacy).
I will try to debug more but there may be lingering issues.

FYI I bisected to this commit that the tests are hanging on my FreeBSD system (in test_encoder_decoder_legacy).
I will try to debug more but there may be lingering issues.

This is a clear attempt to recursively CRYPTO_thread_write_lock() an EVP_PKEY's lock, which on my system is using pthread_rwlock and (self-)deadlocks.
In test_key(idx==2), the call to test_protected_PEM() from line 535 in turn calls PEM_read_bio_DSAPrivateKey() at line 339, which eventually ends up in evp_pkey_downgrade():
1940        if (!CRYPTO_THREAD_write_lock(pk->lock))
(gdb) p pk
$3 = (EVP_PKEY *) 0x800ec6780

we then end up in evp_pkey_free_it() and get to evp_keymgmt_util_clear_operation_cache() that tries to lock the already-locked lock:
1883                evp_pkey_free_it(*dest);
(gdb) p *dest
$5 = (EVP_PKEY *) 0x800ec6780
(gdb) s
evp_pkey_free_it (x=0x800ec6780) at crypto/evp/p_lib.c:1631
1631        evp_keymgmt_util_clear_operation_cache(x, 1);
(gdb) s
evp_keymgmt_util_clear_operation_cache (pk=0x800ec6780, locking=1)
    at crypto/evp/keymgmt_lib.c:206
207             if (locking && pk->lock != NULL && !CRYPTO_THREAD_write_lock(pk->loc
k))
(gdb) p pk
$6 = (EVP_PKEY *) 0x800ec6780

@kaduk - can you raise this as a separate issue?

Yes, this is #14171 (which I filed and then stepped away before realizing I didn't actually cross-link)


feat(table): Use lighter color for hover background

Use $dc-blue80, it matches the current live version better (from CMS).

Looks Good.


Installing an MSIX including Microsoft.Playwright (nugget package that automate browser tasks)

Hello,
Im currently trying to publish a desktop application that uses Microsoft Playwright to automate few task, however it seems that im missing something...
So after creating a windows package project in visual studio to package my application (Publish > Create Package > ...) I ended up with an installer:

The application installs correctly and all other dependencies such as API and Database are working correctly but Playwright is not working for some reason.
For testing purpose I've created a Mock project that has a simple button that calls playwright:
try
{
    var exitCode = Microsoft.Playwright.Program.Main(new[] { "install" });
    if (exitCode != 0)
    {
        Console.WriteLine("Failed to install browsers");
    }

    using var playwright = await Playwright.CreateAsync();
    await using var browser = await playwright.Chromium.LaunchAsync(new BrowserTypeLaunchOptions() { Headless = false });
    await using var browserContext = await browser.NewContextAsync();
    var page = await browserContext.NewPageAsync();
    await page.GotoAsync("https://www.google.com");
    await page.WaitForTimeoutAsync(10000f);
}
catch (Exception exception)
{
    output.Text = exception.Message + Environment.NewLine + exception.StackTrace + Environment.NewLine;
}

The package installation details:
.NET CORE 6
Playwright package version: 1.27.2
Windows 10 x64
After the package is installed I run the application that looks like this:

When the Test button is pressed, the above code runs and this is the final output:

Playwright fails to install and therefore the launching/creation not working which I believe the exception is pointing to.
.playwright folder exist after installing my package

It seems I cant run/execute any kind of action in this folder C:\Program Files\WindowsApps ... which means that I cant install playwright, even if playwright is installed manually the app cant launch it...
All MSIX (package installers generated by Visual studio) are installed in this particular folder with high security.
Any clue how to solve this problem without getting access to this folder? Clients shouldnt unsecure this folder
Thanks.
Note: I really want to install using MSIX because I want to upload my application into microsoft store

@kaidoatgit would Install location vitualization work?

@kaidoatgit would Install location vitualization work?

Hello mate, I will give a try and research about it, thanks for your answer, i will give feedback as soon as possible

@kaidoatgit would Install location vitualization work?

Hello mate, I will give a try and research about it, thanks for your answer, i will give feedback as soon as possible

It does not work :(

Coolio.  Thank you for trying my suggestion.  Before I continue with suggestions I want to make sure I understand your problem.
What is the main issue?  playwright can't be installed?

Coolio. Thank you for trying my suggestion. Before I continue with suggestions I want to make sure I understand your problem.
What is the main issue? playwright can't be installed?

Im currently deploying my MSIX Package, everything works perfect in localhost however when I install using the package itself some funcionalities of my WPF dont work. After some researches I found that all MSIX package are deployed into this super protected folder with read-only permissions: C:\Program Files\WindowsApps.
My problem is that im using a nugget package from Microsoft to install Microsoft.Playwright which is a tool to automate browser tasks. The following code installs the binaries for chromium browser:
var exitCode = Microsoft.Playwright.Program.Main(new[] { "install", "chromium" });
            if (exitCode != 0)
            {
                   output.Text += "Failed to install browsers" + Environment.NewLine;
            }

However because of the super protected folder C:\Program Files\WindowsApps the code above does not work.
I've tried another approach that was to install the binaries manually and then use the following code to create the object to automate browser task:
using var playwright = await Playwright.CreateAsync();
                await using var browser = await playwright.Chromium.LaunchAsync(new BrowserTypeLaunchOptions() { Headless = false });
                await using var browserContext = await browser.NewContextAsync();
                var page = await browserContext.NewPageAsync();
                await page.GotoAsync(website_url);
                await page.WaitForTimeoutAsync(10000f);

Even this way it still doesnt work. I did give permission myself to write aswell on this super protected folder: C:\Program Files\WindowsApps and this way works, but this is a big NO, because this folder shouldnt be unsecured.


GitHub workflow rebuilds docker image each time, look at using self hosted agent

Build times are slow. A big part of this is as Docker images are rebuilt each time. Either look at transferring cached layers between workflow runs or self hosted runners.

@ross-p-smith  think this is still needed?

Closing as builds are now much improved.


Make md-button & others usage look like mdButton along the lines of mdInput

Bug, feature request, or proposal:
Currently there is a confusion as to why mdInput is an attribute directive [which is the reason why it is written as mdInput instead of md-input] & md-button is a component
Since md-button(and other button variants) are used only as html attributes, it would be easy for the user's mental model if he can write
<button mdButton> instead of <button md-button> similar to <input mdInput>
What is the expected behavior?
Ability to use button variations using camelCase such as <button mdButton>
What is the current behavior?
All button variations needs to be used using kabab cased attribute <button md-button>
What is the use-case or motivation for changing an existing behavior?
Now the user needs to know how button is implemented (which is why it is kabab case instead of camel), instead end user should not care how it is implemented, instead just knows elements follow kabab case & directives follow camelCase.
This way, the implementation detail does not leak to end user
The mental model of "html element => component", "html attribute => directive" is easy to remember & intuitive for most angular developers.
Which versions of Angular, Material, OS, browsers are affected?
2.0.0-beta.2

As a new user of material (but familiar with Angular 1 and Material 1) this difference is hard to understand at first glance. And it looks like material naming is incoherent since both mdInput and md-button are used in the same way, as attributes, but are cased differently. So at first I'd like them to be renamed too.
However renaming them would go directly against the official style guide about custom prefix for components and attribute directives. Not sure what the best of course of action would be...

+1 to migrate to mdButton for consistency.

Does the latest release (2.0.0-beta.10) fix this issue?
The first item under Deprecations says:

All dash-case @ Directive selectors are deprecated in favor of the camelCase equivalent. The
dash-case selectors will be removed in a subsequent release. Some examples include:

md-line ---------------> mdLine
md-tab-link ----------> mdTabLink
md-tab-label --------> mdTabLabel
md-card-avatar ----> mdCardAvatar

The current behavior is that @Components are dash-case and @Directives are camelCase. The reasoning is that an element can only have one @Component, but multiple @Directive instances. So you can tell by looking at <button mat-button matTooltip="Hello"> that MatButton is the @Component, and all of the unprefixed attributes (disabled, color, disableRipple, etc.) apply to that, while MatTooltip is a directive and its properties would all be prefixed with matTooltip

Just came from #18606.  I think confusion arose there because the docs agree with @jelbourn, telling you to use camelCase directives, but the example for the same components shows the directives in dash-case (<mat-icon mat-list-icon>folder</mat-icon>).
Would it make sense to resolve this issue by reviewing the docs to ensure that both the Overview and Example tabs of each component consistently use these case conventions?

Yes, a docs review would be useful to make sure we're not using any deprecated selectors (we didn't have this rule totally internalized when we first started, and some of the old inconsistent APIs stuck around).


Legality analysis: hack checking

For future reference and discussion: http://i.imgur.com/ZcGD4de.jpg

Closing this in favour of having this in a wiki: https://github.com/porygonco/porybox/wiki/Hack-Checking
Individual hack checks can be in individual issues on github.


Change the hyperlink to text of air quality

Changed the hyperlink to text
issue number #256

@avinash201199 can you accept the pull request