Missing link for Soul Empower

Hi,
Since the change to warlock soulblade, I haven't had a button in-game for Soul Empower though it says I do in my character sheet.  If I'm just not understanding a rule right (likely) can you plea

se educate me?  If I could get some help with this issue, I'd appreciate it.

It became a passive power. If not working on your hero please Respec.

thank you


Frontend error monitoring

To analyze exceptions and errors in the browser from public webpage.

Not relevant to this package.


Application won't open on phone

Hey guys,
I just succesfully built and installed the helloworld example. It also shows the app on my phone (Huawei P Smart). However when I try to open the app it launches and is directly terminated in less then a second. Are you aware what could cause this issue?
Thanks for your help!

Other examples work must be a typo or sth. I think its not worth to go deeper in this issue


⚠ Bofrost.be has degraded performance

In 37b7068, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1300 ms

Resolved: Bofrost.be performance has improved in 1fc2d85.


Limit Password Attempts on User Login

OrientDB Version: 2.1.3
Java Version: 8
OS: Ubuntu 16.04
Expected behavior
I want to see if there is way for the database to limit login attempts per ip to prevent brute force attacks.
Actual behavior
I can see no way to implement this without having a separate host or process to handle the blocking of repetitive login queries.
Steps to reproduce
Just use any api and you can brute force through connection attempts.

Hi @RyanTopps
In ehe Community Edition there is no such feature. In the EE you can rely on Kerberos authentication, so Kerberos can manage it for you, but it's not a built-in feature of OrientDB security system.
I'm flagging it as an enhancement, maybe we will develop it in the future
Thanks
Luigi


feat: weighted avg support in aggregator plugin

Should update cmd/tools/generate/counter.yaml with node_volume_read_latency, node_volume_write_latency, node_volume_other_latency


possible error in example

First, great job. I love the idea of using a schema. Very clever.
In the Defining schema with nested objects example, the schema has e as a number but the data passed is not a number.
A few questions/points:

Is this a typo?
What happens if a data type in the object does not match the schema?
Can you modify the schema after the sjs has been initialized/created?

Thank you! 🎉
Yes, it was definitely an error, thank you for pointing it out!

What happens if a data type in the object does not match the schema?
The template that SJS build is made specifically for the data type that has to be inserted.

E.g.
const schema = { a: 'string', b: 'number' };

// output template =>  [{ "a":" ]  x1  [", "b": ]  x2  [ } ]

Where you insert the values at x positions.
So, it's very important that the data type matches the schema.
Initially, I designed like that for maximum performance. However, I have to check how much a data type check could have an impact on performance.

Can you modify the schema after the sjs has been initialized/created?
There is no built-in feature for that. The template creation is not meant to be a repeated operation. So, it is not optimized for performance.
You can however simply compile another schema.

Thank you!


It seems watchers returned by useFsWatcher is always empty

https://github.com/KermanX/reactive-vscode/blob/main/packages/core/src/composables/useFsWatcher.ts#L53
watchers was never set by any value, which seems should be set here:
const w = workspace.createFileSystemWatcher(
  pattern,
  toValue(ignoreCreateEvents) || false,
  toValue(ignoreChangeEvents) || false,
  toValue(ignoreDeleteEvents) || false,
)
watchers.set(pattern, w) // HERE!
w.onDidCreate(createEmitter.fire)

Thank you for reporting. Got fixed in the latest version~


Deploytime exporters template metadata for app.kub.io/name should fall back to deploymentConfig meta if empty

e.g.
template:
        metadata:
          creationTimestamp:
          labels:
            e2e-app: "true"
            app: todolist
            application: todolist
            deploymentconfig: todolist-mongo-go
            app.kubernetes.io/name: todolist

template.metadata.labels: app.kubernetes.io/name:  IF EMPTY...
use: deploymentConfig.metadata.labels
kind: DeploymentConfig
    metadata:
      name: todolist
      namespace: mongo-persistent
      labels:
        app: todolist
        app.kubernetes.io/name: todolist

It seems we need a more robust solution. I've opened https://github.com/konveyor/pelorus/discussions/511 for discussion.

Once we have better troubleshooting documentation(549) (to go with the existing script), then we'll have a good alternative to this.
We could (later) investigate how to do this performantly-- pagination, multithreading (would help if bound on IO), but that's a lot of work when we don't have metrics on how big most clusters are.


Request: add Casambi switch support

I have added a non casambi occhio luminaire to my casambi network by using an AImotion plug & play switch. It works perfectly in the Casambi app and the Casambi plugin for homebridge detects it perfectly fine. The switch als gets added to my HomeKit setup however pressing the switch in HomeKit does not turn the switch on or off. Checking the Homebridge logs results in the following error:
“Luminaire switch plug & play has no on characteristics”
After reading your list of tested devices I noticed that you explicitly state that on/off functionality is not supported. So it all seems to add up. Are you planning on adding this functionality or are there certain software limitation that would make this impossible to implement? It would be great to be able to successfully use this switch in my HomeKit network.
Thanks in advance,
Martijn

The missing On characteristic would indeed result in this problem.
Could you send me the log when Homebridge starts up? In particular I’m looking for a line saying:
“Unit switch plug & play is a … with fixtureId …”
With that I should be able to debug the missing characteristic.

Here is a screenshot of the log:

“Unit switch plug & play is a … with fixtureId …”

So I guess that would be 7757 :)

So I guess that would be 7757 :)

Thanks :)
I’ll get back to you when I know more.

Awesome! Many thanks in advance Awahlig!

Hello awahlig, I was wondering wether you have found a solution for the switch? Today is the last day I can return the unit and get a refund.

Yes, sorry. I know why it doesn’t work and how to make it work. I haven’t had time yet to start implementing it but I will so you can keep it.

I just published a new beta version to npm with support for simple on/off switches.
To try it out, you'll have to update your homebridge-casambi package:

sudo npm install -g homebridge-casambi@beta

Then, restart Homebridge and check the Plugins page of the Homebridge Config UI to see if it's using the correct version of the plugin (v0.3.4-beta.0).

Hello there,
I returned the unit because it was unsupported and I didn’t want to risk purchasing a switch that was unusable. I will try to get my hands on one soon so i can give your beta a try.
Met vriendelijke groet,
Martijn de Groot

On vrijdag, nov. 05, 2021 at 8:06 PM, Arkadiusz Wahlig @.*** @.***)> wrote:
I just published a new beta version to npm with support for simple on/off switches.
To try it out, you'll have to update your homebridge-casambi package:

sudo npm install -g @.***

Then, restart Homebridge and check the Plugins page of the Homebridge Config UI to see if it's using the correct version of the plugin (v0.3.4-beta.0).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/awahlig/homebridge-casambi/issues/17#issuecomment-962145577), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AEZCFDJL2XZZEYT72ACRH23UKQTLTANCNFSM5D3Y6Q5A).
Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).

Hey Martijn, no problem, I understand. Sorry it took this long, I was quite busy lately. Let me know if you're able to test it.
Best,
Arkadiusz

Will do! Thanks for investing time in making this possible.
Met vriendelijke groet,
Martijn de Groot

On vrijdag, nov. 05, 2021 at 9:00 PM, Arkadiusz Wahlig @.*** @.***)> wrote:
Hey Martijn, no problem, I understand. Sorry it took this long, I was quite busy lately. Let me know if you're able to test it.
Best,
Arkadiusz
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/awahlig/homebridge-casambi/issues/17#issuecomment-962180892), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AEZCFDPTYFVMFDKAKGWRN5DUKQZVPANCNFSM5D3Y6Q5A).
Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).


Fix pagination for bulk delete modal (PROJQUAY-4497)

Fix pagination for bulk delete modal
Signed-off-by: harishsurf<EMAIL_ADDRESS>

When searching the pagination doesn't seem to be updated. For example this search has 3 results but it renders with 1 - 10 of 11.

Although this may get confusing since that may give the impression if you search it will only delete the results you search for. Maybe UX could provide input on what this should look like?

/cherry-pick redhat-3.8


Notification / Event before/after node layout changed?

There is some work for YG_ENABLE_EVENTS. And the event types are:
 enum Type {
    NodeAllocation,
    NodeDeallocation,
    NodeLayout,
    LayoutPassStart,
    LayoutPassEnd,
    MeasureCallbackStart,
    MeasureCallbackEnd,
  };

When does NodeLayout happen? Before, after the node layout was calculated? I think it makes a lot of sense to have two events (start/end) so that the old layout can still be accessed on start, and get a before/after view of a node.
Is this currently possible?

Event happens at end of laying out given node. Having two markers could make sense here, but could also be derived as time from last NodeLayout or pass start.
Right now events are not exposed to Yoga public API. Intent for them is to be used for tracing.


Unable to open colab tutorial

On opening the colab tutorial I get an error: "There was an error loading this notebook. Ensure that the file is accessible and try again."
Other notebooks work fine (for example the nequip-tutorial), so I think it's not on my end.
I did find a workaround: opening in an incognito tab (chrome). So maybe it's something on my end after all, but I thought I'd post anyway just in case.

Thanks for letting us know. It worked for me in different browsers. Which browser is this with?

No problem, it's with chrome in non-incognito mode, the difference being probably that I'm not signed in to my google account in incognito mode.

I’ll take a look, thank you for letting us know.

Did you try this: https://stackoverflow.com/questions/48854737/google-colaboratory-and-google-drive-integration-fails

Yes I don't have adblock and third party cookies are allowed. I removed all cookies and it worked once, but just because I wasn't signed in to my google account. I never had any issues with colab before.

Hm I cannot reproduce this, I tried chrome + a different google account, still can view it in Chrome.

Strange, I asked a colleague and she did have the same issue. Anyway thanks for looking into it, maybe wait to see if someone else independently runs into this before spending more time.

I'm encountering the same issue using Firefox.

Would you mind trying this link: https://colab.research.google.com/drive/1a0s34KERvJnvkdKSHkyG8HZYijC6xhwv#scrollTo=ZPqnt-SAXyvL
Sorry about this, all!

Would you mind trying this link: https://colab.research.google.com/drive/1a0s34KERvJnvkdKSHkyG8HZYijC6xhwv#scrollTo=ZPqnt-SAXyvL
Sorry about this, all!

Worked for me. Thanks!

Updated the link in the REAMDE, thanks all.


Cleanup pacman rule

I wonder how I could write a test for that one since it depends on the external program pkgfile.

You can check pull request #200 (more precisely: https://github.com/scorphus/thefuck/blob/improve-shells/tests/rules/test_pacman.py)

I just merged conflicts with #200.
@scorphus:
Did you test that on Arch Linux?
On mine tests did not pass as pkgfile returns the complete name of the package (eg. extra/gvim for vim). I fixed that in 031669f.

@mcarton: That's awesome!
These last days I've struggled trying to vagrant up an Archlinux to run those tests. I haven't had any near-to-good Internet connection so far since Tuesday. So, thank you!
What do you think about fixing the *mocked tests as well?

@scorphus: I do not know mock but for what I understand I should replace
Command('vim'), '{} -S vim && vim'.format(pacman_cmd), 'vim foo bar'),

with something like:
Command('vim'), '{} -S vim && vim'.format(pacman_cmd), 'extra/gvim\nextra/gvim-python3'),

since pkgfile output is as follow:
% pkgfile vim
extra/gvim
extra/gvim-python3
extra/vim
extra/vim-minimal
extra/vim-python3

Can you confirm that?

Not quite that... almost! rules/pacman.py has:
        # [snip]
        return subprocess.check_output(
            ['pkgfile', '-b', '-v', command.script.split(" ")[0]],
            universal_newlines=True, stderr=DEVNULL
        ).split()
        # [snip]

And I get the following form pkgfile:
vagrant@archlinux:~$ sudo pkgfile -b -v vim
extra/gvim 7.4.723-1        	/usr/bin/vim
extra/gvim-python3 7.4.723-1	/usr/bin/vim
extra/vim 7.4.723-1         	/usr/bin/vim
extra/vim-minimal 7.4.723-1 	/usr/bin/vim
extra/vim-python3 7.4.723-1 	/usr/bin/vim
vagrant@archlinux:~$
vagrant@archlinux:~$ sudo pkgfile -b -v convert
extra/imagemagick <IP_ADDRESS>-2	/usr/bin/convert

Yes I know, I just wanted to be sure return_value was supposed to be the output of pkgfile and forgot the flags in my example. Anyway, it should be right now, this can be merged.

Thanks!


[Docs] Add missing prerequisite for publishing Hugo site (branch naming)

Update Docs
Reporting issue: https://github.com/microsoft/studentambassadors/issues/19
Docs page to be updated: https://learn.microsoft.com/en-us/azure/static-web-apps/publish-hugo
Docs page markdown file: https://github.com/MicrosoftDocs/azure-docs-pr/blob/live/articles/static-web-apps/publish-hugo.md
Prerequisites
VS Code installed locally
Learn Authoring Pack for VS Code extensions added to local VS Code instance
Task
In the list of prerequisites, after the GitHub account item add the following: Git installed.
With "Git" linking to https://learn.microsoft.com/en-us/devops/develop/git/install-and-set-up-git

Fixed: https://github.com/MicrosoftDocs/azure-docs-pr/pull/239835


Replace File.identical with FileUtils.compare_file

File.identical? only tells you if it's the same actual file (eg, a symlink or hardlink), but returns false if two different files have the same contents.
I've confirmed this change works - I'd confirmed the original version with .cmp (alias for compare_file), but not with .identical?.

I missed that while reviewing!
Fixed in a88b206644a14b0de7bbb58e0ba1baab93737a8e
I actually mean FileUtils.identical? which is just an alias to FileUtils.compare_file

@mipearson
Let me know when master tested
I will release after that

I .. forgot about this. You've already released, so I'll close this PR. Thankyou :)


Fix: punctuation, readability and improve wording

Removed extra spaces, punctuation marks, redundant words/expressions and fixed spelling.

@microsoft-github-policy-service agree
I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.


Add open-austin/hackpad to projects page?

New repo. To get this on http://bit.ly/2oCnn7Y, we'll need the following info for fields marked '????' --- title: open-austin/hackpad description: Old Hackpads for archival purposes access_at: ???? project_at: http://bit.ly/2qd0SUv type: ???? status: in development categories: [ ????, ???? ] contact: ???????@????.com?> cfa_stage: alpha layout: post date: April 27, 2017 at 11:26PM thumb: ???? screenshot: ???? featured: ???? ---

Assuming this gibberish is automated.
The hackpad repo isn't for a project, just documentation. Closing

Whoops looks like I messed up my template, will fix

nice, glad we got a little test in. I really like this bot tho. It will up us stay better on top off highlighting projects.


Usability in REPL

Hi, great work!!!, congratulations.
I am new with Julia and reactx, i was tried to use Rocket in REPL console, but I don know how to syncronize "a" variable, subscribe it and then show the change whe I want change the new value of "a", I am trying with schedule, task an nothing.  PleasePlease can you show how to useit?, thanks a lot

Please do not use the issue tracker for questions, you can ask questions on Discourse.
Also I suggest you to check our documentation first.


Update to Logical / Physical Flow workflow #1910

As-Is
The physical flow editing workflow needs to be revisited., current issues include:

Users have no way to move physical flows when incorrectly documented (options are to delete the physical flow and rekey a new physical flow or clone and delete previous flow)

When creating a new physical flow the user is allowed to save without selecting a known datatype, this causes a knock-on effect of the datatype of an existing flow for the source > target being used (might not always be correct)

When creating a new physical flow manually , the target has to exist - this can be frustrating, especially as when the user uses the bulk loader, they are able to create new source > target flows

OLAs are widely used in conjunction with physical flows (Bookmarks), is there a way the process could become easier to manage / less cumbersome?

The overall workflow needs to straighten out these kinks, should we consider making the logical flows read-only and only asking users to update physical flows (whilst this would be a learning curve, it should lead to better data quality and completeness.

Some observations:

Users have no way to move physical flows : have to be careful that the meaning of a flow doesn't change. It may be referenced in a diagram etc. and moving it will cause issues.  Allowing a clone with different source/target should be fine.
Do we want to have datatype selection part of the new physical flow registration process ?  Currently it's a post-creation step. There is no explicit linking of logical data types to physical flow datatypes when the physical has no declared types.

We should make the data type selection process easier by limiting to only those on the logical flow (adding a new type is still possible but would be a additional user action - i.e. show un-used datatypes and then allowing selection)
The same approach can be used for logical flows (i.e. new flow from A -> D shows all currently used datatypes for A ->( B | C) - this assumes new flows are skewed towards datatypes that existing flows use - as above, allow override)

When creating a new flow manually the target hast to exist - is this asking for us to be able to register new logical flows as part of a physical flow creation ?   If so then I agree this makes sense.  If not could you elaborate ?
OLAs - I think this is a wider topic.  Think we need the idea of a physical flow group.  This could then have some documentation associated with it, tagging, surveys etc.

Agree that we are now at the maturity level to only allow for physical flows to be registered (assuming we can create logicals implicitly as per point 3)  However this should be configurable at a Waltz level (i.e. not all orgs may want to opt in to this, some may be happy at a logical only level)


Rails 5/RSpec 3.5 tests failing due to JSON being sent instead of PORO

Summary
I am building a demo app using Rails 5 and RSpec 3.5. When I run the generated contract tests, I'm getting an error indicating the required :data key is missing from the params hash. Further investigation determined this was because the endpoint was expecting a PORO and got a JSON object. I need to investigate whether this is caused by the particular version of RSpec, the particular version of Rails, or some other reason (that didn't get in the way of Repaymnt Estimatr tests working).
Expected Behavior
After running Rambo, assuming the API is functioning as documented, the tests should pass.
Current Behavior
When running the generated RSpec tests for my Rails 5 app, the tests raised this error:
Failures:

  1) Personal Calculator /age POST calculate age given a birthdate
     Failure/Error: params.require(:data).permit(:first_name, :last_name, :birthdate)

     ActionController::ParameterMissing:
       param is missing or the value is empty: data
     # ./app/controllers/calculations_controller.rb:26:in `profile_params'
     # ./app/controllers/calculations_controller.rb:17:in `resp_body'
     # ./app/controllers/calculations_controller.rb:5:in `age'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-2.0.1/lib/rack/etag.rb:25:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-2.0.1/lib/rack/conditional_get.rb:38:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-2.0.1/lib/rack/head.rb:12:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/railties-5.0.0/lib/rails/rack/logger.rb:36:in `call_app'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/railties-5.0.0/lib/rails/rack/logger.rb:24:in `block in call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/railties-5.0.0/lib/rails/rack/logger.rb:24:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-2.0.1/lib/rack/runtime.rb:22:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-2.0.1/lib/rack/sendfile.rb:111:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/railties-5.0.0/lib/rails/engine.rb:522:in `call'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-test-0.6.3/lib/rack/mock_session.rb:30:in `request'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-test-0.6.3/lib/rack/test.rb:244:in `process_request'
     # /Users/dana/.rvm/gems/ruby-2.3.1@personal_calculator/gems/rack-test-0.6.3/lib/rack/test.rb:67:in `post'
     # ./spec/contract/personal_calculator_spec.rb:36:in `block (4 levels) in <top (required)>'

The cause proved to be that Rack middleware is not running when the server processes the Rack::Test request, and as a result, the JSON object is passed through to the controller as-is, instead of being parsed.
Possible Solution
Since the solution will depend heavily on what the cause turns out to be, I will update this issue as I learn more.
The first thing I learned is that the behavior is the same with Rails 4. Since Rambo doesn't support RSpec 2, the problem also can't be with RSpec 3.
Steps to Reproduce (for bugs)

Create a working Rails 4 or 5 API with RAML
Install RSpec v. 3.5 and Rambo
Run rake rambo
Run bundle exec rspec spec/contract
See errors

Your Environment

Version used: 0.4
RSpec-Rails: 3.5.1
Rails: 5.0.0
Rack::Test: 0.6.3

I'm going to create a new release that fixes this. @zeisler and @mleglise-renew, please let me know if version 0.5 breaks Repaymnt Estimatr.


Param: add rate-limited auto-save on LP work queue

This automatically saves parameters after a timeout of 300ms and at most every 2 seconds.
The previous behavior was more complicated: param set on the console (or in scripts) would immediately save params; after bootup, commander would save params on param change notification (but only if COM_AUTOS_PAR was set).
It greatly improves bootup time after an airframe reset (SYS_AUTOCONFIG=1).

Needs on-airframe tests.

Flight tested with in-air param changes worked fine.


evergreen-colors outline

The first package that needs to be added is evergreen-colors. I have generated a new color extended color palette, loosely based on Material colors.
How the color system works
The color system is a set of different colors groups that have each a set of tints and shades.

The primary color of each color group is called 500.
The darkest shade is called 1000.
The lightest color is 5. (0 would be white)

Transparent variations for all colors below 500
There is another identical color system that uses transparent colors instead of fully opaque colors.
This is helpful for text colors, borders, box shadows. Only colors below 500 are transparent.

Example API
import colors from 'evergreen-colors'

// colors is a object with each color group as a key
colors.neutral
colors.green
colors.red
colors.blue
colors.purple
colors.pink
colors.yellow
colors.turquoise
colors.white

// Each color group has a list of colors as a key
colors.neutral['300A']
colors.neutral['400']
colors.neutral['500'] // primary

colors.purple['500'] // primary

White is an exception
Since there is no darker variation of white (everything over 500).
White only has a 500, and everything below 500 is transparent: 300A, 400A etc.
 There is still some documentation improvements required.


mido.get_input_names() and mido.get_output_names() list IAC twice on macOS Ventura 13.3.1, Python 3.11.0

mido.get_input_names() and mido.get_output_names() list IAC twice, even though underlying python-rtmidi correctly lists IAC-Port only once.
>>> import mido
>>> mido.get_input_names()
['IAC-Driver Bus 1', 'IAC-Driver Bus 1']
>>> mido.get_output_names()
['IAC-Driver Bus 1', 'IAC-Driver Bus 1']
>>>
>>> import rtmidi
>>> rtmidi.MidiIn().get_ports()
['IAC-Driver Bus 1']
>>> rtmidi.MidiOut().get_ports()
['IAC-Driver Bus 1']

macOS Ventura 13.3.1
Python 3.11.0
python-rtmidi 1.4.9
mido 1.2.10
EDIT: This has apparently been fixed: Running the same code with the current github version (bff6bf2a8711e33782de5661ed5ccdffb0bb1688) returns the correct number of IAC ports (one each for input/output names).

Thank you for the report.
I think I've seen something similar on Windows a while ago. I'll try and investigate as soon as I get time to work on mido again.

Oh, I didn't see your edit!
Thanks for having checked against the development version.
I'll close the issue then.
Feel free to reopen if need be.

Hello. Thank you for this great project!
When do you plan to release this fixed version on pypi?

Hello. Thank you for this great project! When do you plan to release this fixed version on pypi?

Next release is planned in a few days: https://github.com/mido/mido/milestone/1


why Unexpected '?'.

why is s =... line giving Unexpected "?" ? if i change either ternary its works. i get it, if both terms are same then it will give unexpected, but should it?
function rootx() {
"use strict";
var line,i,s;
for (line=1; line<30; line+=1) {
for(i=1;i<29;i+=1) {
s = (Math.floor((Math.random()*2)%2)) ? "?" : "?";
document.write(s);
}
document.writeln("<br>");
}
}

Both consequences of the ternary operator are "?". JSLint thinks you are misusing the ternary operator.


Failed to load PDF file

I am using tesseract 3.3 for extract text from IMG/PDF.
It will work fine when i am extract text from image, but when i am use pdf file for extract text it will throw error.
Pix img = Pix.LoadFromFile(pdfFilePath);
Please help.

Loading from PDF isn't supported. You'll need to use a different library to
load it and then extract the images.
On Fri., 14 Jun. 2019, 21:54 sumitm815<EMAIL_ADDRESS>wrote:

I am using tesseract 3.3 for extract text from IMG/PDF.
It will work fine when i am extract text from image, but when i am use pdf
file for extract text it will throw error.
Pix img = Pix.LoadFromFile(pdfFilePath);
Please help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/charlesw/tesseract/issues/475?email_source=notifications&email_token=AAB7HSBFOWG5J2MBIX2ASZLP2OBHDA5CNFSM4HYHEW4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZRGKCQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB7HSDJQLIVLTEX55PSAWDP2OBHDANCNFSM4HYHEW4A
.

Thanks..! Could you please suggest any library for extract PDF to image, then i can use to them.

Itextsharp or abcPDF.
Sent from my iPad
On Jun 17, 2019, at 5:09 AM, sumitm815 <notifications<EMAIL_ADDRESS>wrote:
[External email: Use caution! Do not open attachments or click on links from unknown senders or unexpected emails.]
Thanks..! Could you please suggest any library for extract PDF to image, then i can use to them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://protect-us.mimecast.com/s/1Sn_CG6gVxs1kx9lS7z0D5?domain=github.com, or mute the threadhttps://protect-us.mimecast.com/s/ussGCJ6l9AsqZGozfzADfs?domain=github.com.

I use Docnet.Core https://www.nuget.org/packages/Docnet.Core/

you can use Ghostscript C# wrapper and convert to tiff. debug this code
https://sourceforge.net/p/vietocr/code/HEAD/tree/VietOCR.NET/branches/VietOCR3.NET/


CI: fix container tagging

PS: this is specific to the "force container build". Since there's is no new release version, python-semantic-release is not emitting version numbers for the container build step.

Fixed in #26


Code of Conduct

We need a Code of Conduct (or Codes of Conduct) to support:

Contributing to this repo
Participants at events (Speakers, sponsors, organizers, etc)

Encompassing both in-person & virtual events

GitHub contributing Code of Conduct
This seems pretty straightforward in using the same Code of Conduct as other sqlcollaborative projects.
Event Code of Conduct
In #27 @andrekamman mentions the CodeOfConduct.com code as a base, which helps tackle internationalization/translation.
Events should have a "base" code of conduct (like above), plus a "supplement" which has event-specific details.
Requirements:

The event-specific supplement should include who to report violations to, and how/where to contact them.

Reporting/assistance should be a direct, unambiguous path from the Code of Conduct. (ie, a monitored email address, a front desk person at an in-person event, etc)
Provide guidance to event organizers on eliminating single points of failure for individuals seeking help in reporting problems. Event organizers are often busy & not able to provide a fast initial response

The event Code of which is featured prominently & is easy to find. When an attendee is "in crisis" as the victim of harassment, it should not be difficult to find the Code of Conduct (and hence the path to reporting/assistance)

We should additionally provide resources for event organizers so that they feel equipped to provide assistance & response.

I agree with the above, and I think a CoC/AHP ought to be one of the few rules we implement.

Microsoft is requiring a CoC to be part of the Data Community they are setting up for user groups. It was just a requirement to be available on the MeetUp group. I resued the one we created for our last #SQLSatNash and posted it on our site. As long as you make the requirement verifiable this should be easy.  https://nashbi.sqlugs.com/code-of-conduct/
One requirement that I would like to see and maybe it's just a recommendation. 1) HOW to report something and 2) that organizers plan for having a male & female available to talk to an attendee should there be an issue.  I am not 100% certain I would feel like expressing my concerns to a guy.

Thanks, I appreciate seeing this link. Getting a few CoCs is important.

Thanks, I appreciate seeing this link. Getting a few CoCs is important.

I reviewed several before working on this. I also added based on the feedback of doing my session "The community speaks". Getting real feedback from people who were actually attending events was very helpful!


TModLoader Servers Under Heavy Load, but only when downloading bigger mods.

Description
When I try to download big mods (Calamity, Thorium, etc.) it says the servers are under heavy load. When download something like Cheat Sheet, it downloads fine.
Steps to Reproduce

Download a mod like Calamity or Thorium.

Expected behavior
It will say the TModLoader servers are under heavy load.
Actual behavior
It should be working, smaller mods like Cheat Sheet are.
Reproduction frequency
100% of the time.
Versions
tModLoader v9.2.3
Mods
None yet.

Thanks for the report. I think we've been aware of the issue for a while, we don't really have an answer to this yet. The problem is bandwidth. The bigger mods eat away most of our bandwidth, and we are very limited on it. The solution is to move to a server with unlimited bandwidth, but this costs money. (and time to transfer the entire system)

I guess we could throttle it?

Bandwidth issues have been solved by github integration and incentives.


Htmlviewupdate

Addition of Provider for Analysis
Summary of the changes (Less than 80 chars)
This pr supports the addition of the option to receive a report in a different format such as html. Creates a writerprovider interface and cleans up some of the pre-existing code
Modifies:
    modified:   src/cli/Microsoft.DotNet.UpgradeAssistant.Cli/Commands/Analyze/ConsoleAnalyze.cs
    modified:   src/cli/Microsoft.DotNet.UpgradeAssistant.Cli/Commands/Analyze/ConsoleAnalyzeCommand.cs
    modified:   src/cli/Microsoft.DotNet.UpgradeAssistant.Cli/UpgradeAssistantHostExtensions.cs
    modified:   src/common/Microsoft.DotNet.UpgradeAssistant.Abstractions/IAnalyzeResultWriter.cs
    new file:   src/common/Microsoft.DotNet.UpgradeAssistant.Abstractions/IAnalyzeResultWriterProvider.cs
    modified:   src/components/Microsoft.DotNet.UpgradeAssistant.Analysis/AnalysisExtensions.cs
    modified:   src/components/Microsoft.DotNet.UpgradeAssistant.Analysis/AnalysisOptions.cs
    deleted:    src/components/Microsoft.DotNet.UpgradeAssistant.Analysis/AnalyzeResultWriter.cs

Adds:
    src/components/Microsoft.DotNet.UpgradeAssistant.Analysis/HTMLAnalyzeResultWriter.cs
    src/components/Microsoft.DotNet.UpgradeAssistant.Analysis/SarifAnalyzeResultWriter.cs

Addresses #976 (in this specific format)

Looking good so far @bleaphar.
btw You don't need to include the list of files changed in the description since the PR/commit already contains that information and it's possible to change


About NER F1

Hi Zexuan,
In the evaluation in run_entity.py, you select the entites with max_span_length<=8 to compute tot_gold. Does it make the recall overestimate?
https://github.com/princeton-nlp/PURE/blob/8517005d947afedcbb2b04df9d8de18fa1ca9b04/run_entity.py#L76-L108
Best,
Deming

Hi Deming,
Sorry for any confusion. tot_gold is actually computed when we read the dataset (here), and it should be the number of gold NER labels in the dataset.
Best,
Zexuan


Niche versions

Niche Python Package question
If I type "niche --version" in the Anaconda prompt I get version 1.0a8, if I first type "activate niche" and then "niche --version", I get 1.0b1. This is quite confusing.
I installed 1.0a11 from the yml file today and then 1.0b1 manually (with pip). I got no error message.
When i try to run a model in Jupyter, it seems it is still version 1.0a8
Niche Vlaanderen version: 1.0a8
Run at: 2018-02-28 11:20:37.267201

@cecileherr
My error - I forgot to update the yml

OK, thanks! If I start jupyter from the prompt after having activated niche, I indeed use the new version (and I get errors, more issues to come :-) )
Can I remove the old version that was installed outside the environment anyhow?

To remove:
pip uninstall niche_vlaanderen (outside the environment).

OK, perfect! Life can be easy :-)

Closing here: documenting better seems a good idea, but there is an issue for that.


Redesign Footer

Screenshot of my previous work:-

@codervivek5, I would like to work on this issue. Please assign me this task for GSSoC'24.


Send 400 / 500 error status on Internal Server Error

We've gotta bubble up the error from the server when there is an "internal server error" - probably need a try/catch on the main API Request handler and throw an error on the chat_completion helper function
It's a gorgeous gradient, but the user is left poetically waiting with no indication on a server error

Perhaps in the create_chat_completion function:
https://docs.gptr.dev/docs/gpt-researcher/llms/testing-your-llm

@ElishaKay good point, let's do a PR for this?


Allow DI for validator/rules methods

This is mainly copied from the AbstractGenerator however it allows the FormRequest to use dependency injection for the rules/validator methods
related to #133

Thank you! Could you add a test for this?

@mpociot The method is protected and gets used in the GenerateDocumentationTest and the ApiDocGeneratorTest, those tests pass now.
Thanks!

Current coverage is 89.48% (diff: 90.00%)

Merging #134 into master will decrease coverage by 0.13%

@@             master       #134   diff @@
==========================================
  Files             7          7
  Lines           597        618    +21
  Methods          47         48     +1
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            535        553    +18
- Misses           62         65     +3
  Partials          0          0

Powered by Codecov. Last update 2a001a4...fb38216

👍


can not install module with error "Failed building wheel for tslearn"

My problem is I can not install "tslearn" package on mac with python3.
It show error :  " Failed building wheel for tslearn"
May you provide some solution for install this package?
@rth @rtavenar

Do you have more stack trace than that single line please?

Do you have more stack trace than that single line please?
I attach sreencshot in below, i hope you can help me please

Seems to be a problem with xcrun or something like that (second to last line). You'll need to install xcode:
https://apple.stackexchange.com/questions/254380/macos-mojave-invalid-active-developer-path

Seems to be a problem with xcrun or something like that (second to last line). You'll need to install xcode:
https://apple.stackexchange.com/questions/254380/macos-mojave-invalid-active-developer-path

It's workkkkk, thank you so much  :)


tektoncd-cli: 0.17.1 -> 0.17.2

Motivation for this change
Bump tektoncd-cli to 0.17.2
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.

Result of nixpkgs-review pr 119311 run on x86_64-linux 1

1 package built:

tektoncd-cli


Call revert port with port_connect_nic

Issue #761

This puts the switchport in a state HIL expects* it to be. So admins don't have
to worry about clearing the switchport before registration

Update the deployment tests and the sample config files to work with it.

If this seems reasonable I'll add some unit tests for this.
Again, should probably rebase this one once/if my other 2 PRs are merged (just to be safe).

Why do we need this flag ?
I think this should be the default behaviour for all new ports that we register with HIL.
Is there a user-case where this flag is set to False ?

This comment by @zenhack
In short, if we wanted to deploy HIL in an environment without disturbing the pre-existing configuration; this patch would always remove the old config and start afresh.
But now that I think of it, if there's some pre-existing configuration then we would want HIL to have it in it's database; so are we expecting HIL admins to manually edit the database? because I can't think of any other way of syncing a switchport status with HIL database. cc @zenhack

Okay, yeah, I want to think more carefully about the details of retrofitting HIL onto an existing setup before we put some option to try to support it. Will mull it over.

because I can't think of any other way of syncing a switchport status with HIL database

get_port_networks() gets half the info. We would still need to create networks in HIL (network label with a net id). And what if the networks on the switch fall outside the range of HIL allocation pool? do they become admin networks then?

@SahilTikale @zenhack
any thoughts?

I'm tempted to suggest that we ignore that use case entirely for now, and deal with it separately. We're not really breaking anything, since you'd have to do some careful mucking with things (bordering on black magic) to get this to work as-is.

@SahilTikale @zenhack got rid of the config file changes, and rebased this PR.

I just gotta fix the plethora of failed tests, sigh.

Fixing the unit tests require some work. So everywhere we do port_connect_nic() we need to follow it with deferred.apply_networking(). Is there a smart of doing this, or do I go about changing all files?

Some of the tests fail locally for postgres but they don't stall like travis ci. :/c

@SahilTikale @zenhack ping

closing this, we'll implement something like this in the CLI then.


@conda-forge-admin,please add bot automerge

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/cliche-feedstock#12.


obs forum page not updated with the latest build~

hi, it seems the audio writer filter is not updated with the latest build~ its still in 1.1
https://obsproject.com/forum/resources/audio-writer-filter.872/

All the links on the forum are valid. The download link leads to github releases page with all available builds.


CLI Statement is incorrect

The CLI statement for hibernating your DevBox machine says that the parameter --hibernate should be "false" this should be "true".
https://learn.microsoft.com/en-us/azure/dev-box/how-to-hibernate-your-dev-box#hibernate-your-dev-box-using-the-cli
Statement in the documentation
az devcenter dev dev-box stop --name  --dev-center-name  --project-name  --user-id "me" --hibernate false
Statement should be
az devcenter dev dev-box stop --name  --dev-center-name  --project-name  --user-id "me" --hibernate true

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 462dcb23-2176-5f9d-9099-ffd3fe9f7ff7
Version Independent ID: da53bb98-4f9c-9778-f3ef-46e59198128c
Content: Hibernate your Microsoft Dev Box - Microsoft Dev Box
Content Source: articles/dev-box/how-to-hibernate-your-dev-box.md
Service: dev-box
GitHub Login: @RoseHJM
Microsoft Alias: rosemalcolm

@JerJon
Thanks for your feedback! We will investigate and update as appropriate.

Hi @JerJon, thank you for spotting this error & letting us know. It's now fixed, and you should see the changes published in a few hours.

#please-close


update citation

We could use the new CITATION.cff format described here:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files


Fixed broken integration with scheduler plugin (#5745)

Backport from master branch, commit 5a2f41f98b62376c6cebeb2986b6e1d82bbdc588
https://github.com/mesosphere/marathon/pull/5745
Signed-off-by: Siarhei Rasiukevich<EMAIL_ADDRESS>

Great fix! Thank you, @CharlieR-o-o-t !


Proxy settings not working with extension gallery: net::ERR_TUNNEL_CONNECTION_FAILED

VSCode Version: Code - Insiders 1.10.0-insider (496b804f8ae5a95e899406fcc67f6c1896894c91, 2017-02-16T07:10:22.864Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

vscode-opennewinstance
chrisdias
0.0.4

npm-intellisense
christian-kohler
0.1.4

vscode-npm-source
dkundel
0.0.3

githistory
donjayamanne
0.1.2

KillTasksButton
dtrajano
0.0.4

CreateModule
HookyQR
0.0.5

task-master
ianhoney
0.1.37

output-colorizer
IBM
0.0.8

debugger-for-phantomjs
iradul
0.1.1

csharpextensions
jchannon
1.1.0

csharp
ms-vscode
1.5.3

debugger-for-chrome
msjsdiag
2.3.2

color-highlight
naumovs
1.2.1

material-icon-theme
PKief
1.1.4

qub-msbuild
qub
0.5.0

Material-theme
zhuangtongfa
1.0.3

html-css-class-completion
Zignd
1.0.3

Steps to Reproduce:

Open Extension Gallery
Search for 'test'

The extension gallery is no longer working.
For a longer amount of days the version gallery seems to be broken at my office pc, which is behind a corporate proxy.
I always get a net::ERR_TUNNEL_CONNECTION_FAILED when the gallery tries to fetch
https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery
My vscode was set up with proxy credentials in config before. This did work for a long time very well. i was actually able to download extensions, after @joaomoreno fixed an early version in beginning of 2016 and uploaded it here for testing (sorry i dont fint the thread right now). This bugfix got merged in the official version later and worked fine. But as of 3 Months or so its no longer working.
When using google i found this page: http://code.visualstudio.com/docs/setup/setup-overview
I tried switching to env variables. But this does not work either, so i guess its a problem with vscode itself
I switched to HTTP_PROXY and HTTPS_PROXY env variables now, which seems to be the recommended option. But this doesn't work either.

I try to analyze / debug the errors on my own now, too. maybe i can help.

Can you provide some input in #18103 ?

You can find the results here: https://github.com/Microsoft/vscode/issues/18103#issuecomment-280728376
Thx so much for your efforts, great idea with this http proxy unit test ;)

any chance to get a solution soon?

This happens due to the use of XHR in the renderer. cc @jrieken
Soon, but not this month yet, very busy with other stuff. I'll make it a priority for March.

Thx joao.

How is this issue going on?

https://github.com/Microsoft/vscode/pull/21879

Please check out #22214


fix the issue that it can not work with the newer chartist-js 0.10.1

I modified this library with referring a working plugin so It changed a lot. but it works now.
I did not generate the min js and modify the version number. Could you help on them?

#3

Thanks!


Update testcontainers-scala-scalatest to 0.41.4

About this PR
📦 Updates com.dimafeng:testcontainers-scala-scalatest from 0.41.0 to 0.41.4
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.dimafeng", artifactId = "testcontainers-scala-scalatest" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.dimafeng", artifactId = "testcontainers-scala-scalatest" }
}]

labels: test-library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #258.


MRG fix .elp reading

#3613 breaks .elp reading by doing a transpose at the wrong time. This fixes it.
@Eric89GXL
Closes #3684

Can somebody restart? Travis failures due to my bad commit.


preact build error

Hello,
Getting SyntaxError on preact build while npm start works properly
Build [==================  ] 91% (1.9s) additional asset processing
  Total precache size is about 180 kB for 15 resources.

Template execution failed: SyntaxError: Unexpected token {
  SyntaxError: Unexpected token {

  - node.js:152 Object.require.extensions.(anonymous function) [as .js]
    [lib]/[preact-cli]/[babel-register]/lib/node.js:152:7

  - module.js:12 require
    internal/module.js:12:17

  - index.js:3 Object.<anonymous>
    [lib]/[preact-cli]/[postcss-modules-resolve-imports]/index.js:3:18

  - node.js:152 Object.require.extensions.(anonymous function) [as .js]
    [lib]/[preact-cli]/[babel-register]/lib/node.js:152:7

  - module.js:12 require
    internal/module.js:12:17

  - index.js:24 Object.<anonymous>
    [lib]/[preact-cli]/[css-modules-require-hook]/lib/index.js:24:22

  - node.js:152 Object.require.extensions.(anonymous function) [as .js]
    [lib]/[preact-cli]/[babel-register]/lib/node.js:152:7

@nikhilbelchada You can circumvent this using preact build --no-prerender, but I'd like to figure out why that's happening. Are you using less or sass?

I'm having the same issue. No less or sass but my error is
bundle.js from UglifyJs
Unexpected token: punc ()) [bundle.js:5084,22]

preact build --no-prerender does not work either
$ node -v
v4.1.0
$ npm -v
4.4.1

@developit I am not using less or sass, just trying to run the default app.
Steps I followed:
preact create my-great-app
cd my-great-app/
npm start
npm run build [error..]

seems like using the same node version of your preact-cli installed will solve the problem

@nikhilbelchada are you also running Node v4?  I think most of our testing has been done on 6+.

@developit yes i was on v4, now i updated to v6 and its working, so issue is specific to v4.

We can run a pre/post-install hook & notify on version mismatch. Recent push in node CLI community to bite the bullet and enforce 6+ anyway since 4.x is no longer active LTS.

ahh brilliant - at least knowing it's a 4.x issue we can debug.
I'm actually thinking this is happening because Babel was never being run on those files - in Node 6 that didn't matter because it supports a decent amount of ES2015.  In node 4 it bails though.  It's like this gotcha:
https://github.com/babel/babel/tree/master/packages/babel-register#ignores-node_modules-by-default

@lukeed As long as a node LTS version is in maintenance it should be supported by libs & tools. That's the spirit of LTS anyway ..

This will be fixed by switching SSR to use a webpack bundle.

@rkostrzewski This can be closed too right ?

Ah! Here it is. Thought no one reported this issue.
@lukeed do you remember the discussion between us regarding an error in preact build?
This is the one!


Add derived subkey support

Abstract
While fully relying on ETH-JSON-RPC node-side private keys has the advantage of offloading private key (PK) security to the ethereum node, on the most common usecases (e.g. Metamask, Parity) it has the downside of making for a poor UX, as every signature requires an interactive prompt and user action. On current implementation, at least 2 signatures are required at first startup time for Matrix login and up to 6 are required for a single payment sending. This even worse when using a hardware wallet (e.g. Metamask's Trezor support), as each signature will need multiple approval clicks on UI and on the physical device.
As most of the time these are signatures of opaque byte strings or even hashes, there's no point in requiring users to see it anyway.

What is a subkey?
Here we define a subkey (child key) as a new private key deterministically and secretly derived from the main/parent user key/account. An ETH private key is 256bits/32 bytes number/string. A possible approach is to use the last 32 bytes the keccak or sha256 hash (32 bytes) of the signature (65 bytes) of a constant (possibly per-network) string as private key.
Pseudo-code Example:
message = `raiden_${network.name || network.chainId}`;
subkey = web3.sha3(web3.personal.sign(message, web3.eth.accounts[0]));
// or eth_sign equivalent, depending on provider's implementation of EIP191
subwallet = new Wallet(subkey, provider);

Optionally, the to-be-signed constant string could contain BIG WARNINGS (which will be invariably shown to the user in Metamask sign prompt), alerting users to NOT sign this message anywhere outside a trusted Raiden client, to prevent key steal by phishing:

EDIT: updated to the current proposal of using the hash of the signature
Proposal
At startup/load time, the user may be given the choice to use some eth-provider key (e.g. Metamask always expose a single key, the selected one) directly (as is today) or a generated subkey.
On the subkey case:

a single signature is required at startup time to generate a local private key, which will then be used as Raiden key through the session, without needing any user interaction for signing.
this key should not be persisted (only the address on localStorage object, but also no evidence of relationship between main and subkey), and the user will be given the initial prompt again on every startup.
the UI may offer the user information about how this key is generated, steps to reproduce outside of Raiden, and possibly allow the user to download it in password-protected JSON format, for backup or usage in an external wallet (although they'll always be able to re-generate it from the main key)
the UI may offer actions to easily transfer small amounts of ETH from the main account to this subkey, to pay for gas when needed.
investigate: the user may not need to transfer tokens to the subkey, as possibly the main account could perform the on-chain actions related to depositing on a channel on behalf of the subkey, allowing the main account to actually hold the user token's stash and the normal provider transaction prompt to be used to send the deposit tx.
the UI should offer actions to withdraw back to the main account any tokens the subkey may hold, like the ones coming from any channel close or (in the future) withdraw and receiving.

This approach is already used in other dapps which need a big number of signatures.
Compatibility
This proposal is fully compatible with Raiden protocol, as from the other node's perspective, it's just a normal account interacting with the network, with additional perk of being able to keep the bulk of token stash/ether on a separate, not often used main account.
Additionally, it makes possible to use Raiden Light Client with hardware wallets like Trezor, as a single startup signing prompt, plus eventual on-chain deposit tx prompts are the only intervention needed from the main account.
Security
As the key is not persisted anywhere, but derived from the main key on each session's startup and kept only on memory, there's very little risk of steal. If the application isn't trusted or its runtime was compromised somehow, user OS/browser/environment or the account itself was already compromised and there's little value on the interactive prompts anyway, while positively making the main user account use so rare it'd raise red flags if any unrequested prompt is shown.
Implementation complexity
Surprisingly very little, as the SDK already has support for different key/signers (like ether's JSONRPCSigner and local Wallet). It would be just a matter of having the subkey generation code on Raiden.create (to be used as Raiden signer) and keeping the provider's main_signer around and implement giving the alternative of using it on behalf of subkey as deposit source account.
Acceptance criteria

The user can choose to use either the provider's account on Raiden light client directly or a derived subkey of it on every startup, and both accounts/options are usable and seen as different Ethereum accounts for Raiden.
The user should be able to easily transfer ETH back and forth the main account and this subkey, to pay for gas when needed
The user should be able to withdraw any available tokens from the subkey to the main account
The user should be able to deposit on subkey's channels (or possibly even create them) from the main account, to avoid the need to transfer tokens to it.
The user should be able to know how the subkey derives from the main account, have instructions on how to do it outside Raiden dApp, and be able to download the encrypted JSON subkey for backup.

Tasks

[ ]

Story Points

I have two comments about the key generation:

not all 32 byte sequences are valid private keys https://en.bitcoin.it/wiki/Private_key#Range_of_valid_ECDSA_private_keys (but probably you can rely on the luck).
the last byte os a signature is not random enough, so maybe it's not a good source of private keys

I like the warning as a signed message.

@pirapira For the 2nd point, I agree, but that was just a suggestion. How about using the keccak or sha256 hash of the signature of that message as PK? That would be determinist and have the same secrecy as the signature itself.
For the first point, it would be extremely improbable to get a signature or hash outside the range of valid keys, but if desired to be 100% safe, we could e.g. add a loop appending some constant byte to the end of the signature before hashing, until we get a valid PK as hash. But getting a hash starting with 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFF is so improbable I wouldn't care for this edge case, as the worse can happen is a client using a key which triggers it to fail startup on this case, and being asked to use the main key directly or a different account.
Thank you very much for your thoughts, good insights on this.

Deriving a local key sounds like a very nice usability improvement!
But I'd strongly suggest that someone with a solid background in cryptography should give an opinion on the security of this scheme.
From my very limited knowledge in that area these are questions that come to mind:

Is an EC-signature suitable input for a key derivation? Is there enough entropy?
Is a single round of sha3 sufficient? The well known key derivation schemes (e.g. pbkdf2, scrypt, argon2) all have a tuneable rounds parameters. The recommended values for those depend very much on the algorithm (but e.g. for pbkdf2 100k - 200k(!) rounds aren't uncommon).

@ulope great questions! I also would like a specialist view on this approach
My initial thoughts would be that it'd be enough: ec-signatures are 65bytes/520bits long, and although we lose some bytes on beginning and end, I'm quite sure we can get at least 256bits of entropy out of it.
About the the single sha3-pass, it'd be great if we can get that to be verified as well, but if we consider and ETH-address is the last 20bytes of a keccak hash as well, and a colision there would allow any funds to be stollen, I have some hope the hash of something secret adn entropic enough (like the proposed signature) would also give enough security for this kind of usage.
@christianbrb can we get someone to verify this proposal?

@andrevmatos I can have somebody take a look at it.
What about this proposal: https://programtheblockchain.com/posts/2018/07/18/state-channels-with-signing-keys/

@christianbrb that would require changes to the smart contract, and would tie the user to the temporary key by contract. My proposal is fully compatible with current or past contracts, as it actually effectivelly uses the new keys as defacto Ethereum account for signing, with the difference that most on-chain transactions, specially those requiring ETH or token funds to be available, may be performed by the parent account on behalf of the subkey (but it's optional, the user can use either or actually any available account whenever needed), as it's just standard keys, the user can eject at any point and use their subkey wherever he pleases, on Raiden and out of it, without requiring informing the blockchain or the partners of that, as it's transparent.

Outcome of the external review
Problem
When the Raiden Light Client uses the secret key managed by Metamask or Parity a user has to confirm each signing request via a pop-up shown by these applications. For carrying out a single transaction of the Raiden network this results into up to 6 signatures (i.e., confirmations), and hence leads into poor user experience.
Suggested solution
The Raiden team suggested to generate a session key to improve user experience while still being compatible with secret key management offered by external wallets. The session key is generated as follows:
Sig = ECDSA_SIGN(sk,”Raiden subkey generation message”)
Session-key = H(Sig)
In the above ECDSA_SIGN denotes the ECDSA signing algorithm according to RFC 6979 (deterministic usage of ECDSA) as is used by Metamask. H is a cryptographic hash function (e.g., SHA-3) and sk is the ECDSA secret key stored in the wallet.
Evaluation
The suggested solution is secure as long as the message “Raiden subkey generation message” is never signed for other purposes and revealed. In this case the security follows from the security of ECDSA signatures and the security of the hash function. More precisely, from the existential unforgeability property of the signature scheme it follows that signatures on fresh messages are unpredictable, and assuming that H is modeled as a random oracle (which is a standard assumption in cryptography), we can argue that the Session-key is uniform.
Cautionary remarks and countermeasures
We emphasize that the security of the proposed solution highly depends on ensuring that the “Raiden subkey generation message” is never signed in any other context then as for the Raiden Light Client, otherwise it can lead to the loss of all funds that are managed by the Session-key derived in the above protocol. We recommend that the Session-Key is not stored but instead derived for each transaction. Otherwise if the “Session-key” is permanently stored the above approach does not benefit much from the “secure storage” offered by Metamask. There are some extensions, that can offer better security but they result into drawbacks from a user experience point of view.
These are:

Iterative Signing: Instead of using the Session-Key directly as the key for the protocol, we can repeat the Sign-and-Hash approach for several iterations. For instance, a 2-round iteration would use the “Session-key” as generated above, sign it again using Metamask and hash the result to get final Session-key. This would require that the adversary can carry out an adaptive attack against the master key sk, i.e., he needs to be able to iteratively sign-and-hash for multiple rounds to generate the final Session-key. The disadvantage of this proposal is that for each iteration it results into a pop-up generated by Metamask.

Password-based scheme: We can add to the “Raiden subkey generation message” a short password that is entered by the user. This makes it har    der for the adversary to guess the message that has been signed. Moreover, this approach makes the “Raiden subkey generation message” unique for each user (of course, assuming that users do not choose the same password). The disadvantage of this approach is that the users have to remember a password.

Overall, we recommend the above proposed solution as a method to improve user experience. The Raiden team shall investigate if one of the two proposed ideas can be used to improve security without significantly degrading user experience.

Smart-contract work tracked in: https://github.com/raiden-network/raiden-contracts/issues/1123

Ok, SDK-wise, an approach for the implementation of this feature could look something in this direction:

Raiden.create async factory still receives the main account as the current account parameter, but also a subkey: boolean which defaults to false (current behavior)
if subkey is false, everything happens as is now, with Raiden's instance effective account being the account passed to create, and it's also used for signing messages and transactions and as signer on contracts factories
if subkey=true:

after creating/validating the Signer instance in create, it becomes main: { address: Address; signer: Signer } of the instance, and before proceeding, a sub private key/account is created as signer = new Wallet(sha256(await main.signer.signMessage(verif_message)) as PrivateKey, provider), and this signer becomes the effective signer & address: Address of the instance
verif_message above is a string containing network's name and a warning this message should never be signed outside of trusted Raiden dApp

possibly, also include on this message the netloc/current serverName, and warn the user to NEVER sign this message outside of this domain

this private key is never stored, but re-generated on the beginning of each session, if requested by user
main is stored in deps as the optional main?: { address: Address; signer: Signer } property, which iff !== undefined indicates that the subkey case is in use
all signMessages still uses deps.signer, as this is the subkey/effective key for signing messages; filters also use current deps.address (subkey's) where needed, since this is the effective instance address
contracts are constructed passing main.signer instead of signer, as this is the default case for on-chain transactions
all on-chain methods receive an optional subkey: boolean optional param, which tells them to try to use the subkey for this specific on-chain operation. e.g. if Raiden.openChannel method receives subkey: true, forward it to channelOpen action, which will cause channelOpenEpic to use a tokenNetwork contract connected to the subkey's signer for the on-chain call instead of the default contract connected to main.signer;

notice this is optional and not the default case of using main.signer for on-chain tx on behalf of the subkey, but both cases always target subkey's address as self, never main.address
also, if subkey=false (default), this effectively uses main account's funds (tokens, ETH) to pay for anything for the subkey, allowing funds to be kept on safer main account (behind MM/eth node, etc)
always passing subkey=true to all on-chain methods is effectively the same to extracting the subkey and using it as main key for instance, as subkey's signer and address will be user for everything then

when relevant (possibly not yet implemented in contracts), close/withdraw/settle messages signed by subkey have main.address  as beneficiary, so tokens can go back directly to main account
even in above case, some tokens may still end up in the subkey's account (e.g. on locks not unlocked by partner); so it's important to provide methods to transfer (small amounts of) ETH (to pay for gas) and tokens back and forth main and sub accounts; still the bulk of user's stash should preferably not be kept on subkey, but on main account instead

Main usecase for dApp would be:

2 Connect buttons are shown in homescreen: Connect to Main account & Sign & Connect to Derived account
On 2nd case, normal account is passed to create, but subkey is also passed as true, but only to create; all other methods should use defaults
This subkey isn't persisted and doesn't affect main account usage; so the user can always refresh and use either of them for the session
Interface show address as Raiden.address which is subkey's. Some indicator/tooltip that this is a derived session, and possibly allowing to see main account address may be useful but not essential

@andrevmatos Thanks a lot for the writing down the design :) It helps me to understand the whole process.
Let's prepare this for the next refinement to decide how it looks like from a UX perspective and if it might get splitted.
CC @taleldayekh

2 Connect buttons are shown in homescreen: Connect to Main account & Sign & Connect to Derived account

Could be done differently as well

As an additional solution to background signing we might want to take a look how trustlines is doing it: https://github.com/trustlines-protocol/clientlib

This is how it looks like after experimenting in the PoC:

Main account (Metamask, interactive) hols big ETH & tokens stash, pays for gas for txs and tokens for deposit

default, but option allows requesting the on-chain action to be performed by subkey, if possible

Subkey sign messages (automatic), is the beneficiary of on-chain actions and transparently seen as the defacto account by Raiden Network
Main account can send some ETH to subkey to pay for e.g. transfering settled/withdrawn tokens back to main account

raiden-contracts#1123 tracks proposal to allow tokens to be sent directly to main account on settle/unlock

@andrevmatos Thanks for the update
Whiteboard shot from our refinement session

We would also need to decide how this is going to be presented to the end user as the address would be the subkey, but the ETH would be from the main key

Yes, this UX is the "hardest" part of this issue. Ideally, the user would understand and be able to see, select and operate over ETH & tokens from both main & subkey. All of this is already possible on the SDK PoC, but designing it in a comprehensible manner to the user reamains to be done.

Done in #650 for the SDK, dApp's side will be tracked in #745


✨ Add reference (code API) docs with PEP 727, add subclass with custom docstrings for BackgroundTasks, refactor docs structure

✨ Add reference (code API) docs with PEP 727, add subclass with custom docstrings for BackgroundTasks, refactor docs structure.

📝 Docs preview for commit df4c501136c76a2ef83e3c7e8330c15b5f84491b at: https://5419df85.fastapitiangolo.pages.dev

If you install Black alongside mkdocstrings-python, it will use it to format long signatures (such as fastapi.FastAPI).
Also, tables are a bit too large and have an horizontal scrollbar, maybe the list or spacy formats for docstring sections would be more readable? Happy to work with you on improving rendering :slightly_smiling_face:

There's no such option, but I'll see how we can make it happen.

Thanks @pawamoy!

Also I suppose you cannot use from __future__ import annotations (and then use PEP 604's | syntax) for Pydantic/runtime reasons?

I'm not fully sure, I might be able to do that, at least in some places. It's funny and ironic that I would recommend people not to use from __future__ import annotations to not break/complicate their FastAPI and Pydantic apps... but I might actually be able to use it at least in some places (Pydantic already does that as well). 😅  I will try that as well.

As long as you know what you're doing :wink: And it's only for 1 year and 11 months, until 3.9 is EOL :shushing_face:

📝 Docs preview for commit f55ce131307dc1605a945604d55b8467aadd2536 at: https://bfaa233b.fastapitiangolo.pages.dev

@pawamoy am I using the filters correctly? I have tried several settings, but I still see that when I add things from Starlette, it always shows everything, including private attributes, e.g.: https://bfaa233b.fastapitiangolo.pages.dev/reference/testclient/#fastapi.testclient.TestClient._portal_factory
Is there some additional config I have to add? Or something I should add to those specific references?

📝 Docs preview for commit c9a2fb35ca46d53fc82d0f2c91ae437a18c05cbd at: https://7adbf1fe.fastapitiangolo.pages.dev

@pawamoy am I using the filters correctly?

Hmm that's curious indeed. I'm able to reproduce locally, will continue to investigate.

Ah, it's because of the global members: true which takes precedence over filters. But then without it, nothing shows up under TestClient :thinking: Continuing investigation!

OK, everything works as expected:

members: true was taking precedence over filters: ["!^_"], showing every member of the test client
without members: true, filters are applied, as well as the docstring filter: any object without a docstring is filtered out (see https://mkdocstrings.github.io/python/usage/configuration/docstrings/#show_if_no_docstring)

The result is: no members shown.
But if we look at the test client class, it inherits from httpx.Client which does have public objects with docstrings: to select those, you must enable inherited members, and also preload the httpx and starlette modules. Example:
::: fastapi.testclient.TestClient
    options:
        preload_modules: [httpx, starlette]
        inherited_members: true

These two options can also be defined globally, in mkdocs.yml. Inherited members will then affect everything, it might not be what you want. Preloading modules, while being both a global and local option, really only affects the global context, so it's just a matter of preference: whether you find it more explicit to define it in mkdocs.yml or under the objects that need it.
Don't forget to remove members: true from mkdocs.yml :slightly_smiling_face:

Regarding deprecated objects: I see that you sometimes duplicate the message of deprecated in the docstring. It's not strictly necessary since griffe-typingdoc understands deprecated too in Annotated and will insert the message in the docstring, leading to it being duplicated in the rendered docs:

Instead you could write the message in deprecated only, with proper markup (Markdown), and let it be inserted at the top of the docstring. I do think we have to improve the rendering though (in the screenshot: no newline after deprecation message, no styling for the message).
For objects deprecated with the @deprecated decorator, you could either use the griffe-typing-deprecated extension (which is an Insiders project), or create a custom Griffe extension, for example:
# griffe_extensions.py
"""Griffe extensions."""

from __future__ import annotations

import ast
from typing import TYPE_CHECKING
import textwrap

from griffe import Docstring, Extension
from griffe.docstrings.dataclasses import DocstringSectionAdmonition, DocstringSectionText

if TYPE_CHECKING:
    from griffe import Class, Function, ObjectNode

def _deprecated(obj: Class | Function) -> str | None:
    for decorator in obj.decorators:
        if decorator.callable_path in {"typing.deprecated", "typing_extensions.deprecated"}:
            return ast.literal_eval(str(decorator.value.arguments[0]))
    return None

class DeprecatedExtension(Extension):
    """Griffe extension for<EMAIL_ADDRESS>decorator support."""

    def _insert_message(self, obj: Function | Class, message: str) -> None:
        if not obj.docstring:
            obj.docstring = Docstring("", parent=obj)
        sections = obj.docstring.parsed
        sections.insert(0, DocstringSectionAdmonition(kind="warning", text=message, title="Deprecated"))

    def on_class_instance(self, node: ast.AST | ObjectNode, cls: Class) -> None:
        """Add section to docstrings of deprecated classes."""
        if message := _deprecated(cls):
            self._insert_message(cls, message)
            cls.labels.add("deprecated")

    def on_function_instance(self, node: ast.AST | ObjectNode, func: Function) -> None:
        """Add section to docstrings of deprecated functions."""
        if message := _deprecated(func):
            self._insert_message(func, message)
            func.labels.add("deprecated")

plugins:
- mkdocstrings:
    handlers:
      python:
        options:
          extensions:
          - path/to/griffe_extensions.py

Amazing, thank you @pawamoy! 🙇
I updated the configs with your suggestions! 🚀  Also thanks for the typos.

I see that you sometimes duplicate the message of deprecated in the docstring. It's not strictly necessary since griffe-typingdoc understands deprecated too in Annotated and will insert the message in the docstring

Awesome! I was thinking that I could duplicate it there too for editors, but editors still don't support Doc() so it's the same... 😅  I'll remove those duplications!

For objects deprecated with the @deprecated decorator, you could either use the griffe-typing-deprecated extension (which is an Insiders project)

Nice! I was trying to find how to install insiders the other day but I didn't find it... did I miss the docs somewhere?

📝 Docs preview for commit d7b1e1b49d58bc0f7387c5bbff6a475f9ac76b37 at: https://dca072ea.fastapitiangolo.pages.dev

Another amazing job!👍

📝 Docs preview for commit a6b92eac714011535790617a454199ca2f6ed37b at: https://5797c3d1.fastapitiangolo.pages.dev

Found another bug: Source code in not displaying the actual file path. A property was missing in Griffe, pushing a bugfix release right now.

Thanks @pawamoy! Let me know, I think this is pretty much ready. 😎

📝 Docs preview for commit ba112c39c33742a24306987d5877dc08dfd31583 at: https://3dd93525.fastapitiangolo.pages.dev

I was trying to find how to install insiders the other day but I didn't find it... did I miss the docs somewhere?

It's documented here: https://mkdocstrings.github.io/griffe-typing-deprecated/insiders/installation/. I wonder if this extension still makes sense and if we shouldn't just merge it in the typing-doc one.

Griffe 0.36.7 is out :slightly_smiling_face:

Awesome, thanks @pawamoy! 🚀
For some reason, I hadn't found the insiders installation, and now I see that it's quite open there... I was probably too tired and didn't see it 😅 🙈

📝 Docs preview for commit e2c36729e1a7712a5d1678c5e2faa4acf1670307 at: https://690c34e1.fastapitiangolo.pages.dev

📝 Docs preview for commit c34b8c9b8277f105eba63ff21aee75e84b5453f8 at: https://eca9a21b.fastapitiangolo.pages.dev

📝 Docs preview for commit 77cb0c7d6ec09ad2899e148231af5bd531662af3 at: https://ecb1abc9.fastapitiangolo.pages.dev

📝 Docs preview for commit ac82b9ed29894a2955ce723b91c8da8dc76b1125 at: https://2124dde5.fastapitiangolo.pages.dev

I'll tell you when griffe-typing-deprecated is up-to-date with latest Griffe so you can list it in mkdocs.yml :slightly_smiling_face:

Thanks @pawamoy! For now, I'll merge and release this. 😎 🚀

Congrats! I'm amazed by your efficiency here: in just a few days you managed to document the (almost?) entire API :exploding_head:

Oh and for signature_crossrefs to take effect, you need to enable show_signature_annotations too!


Issue with Exporting PLY Data from Intel RealSense D455 Camera

librealsense
2.54.2 RELEASE

OS
Windows

Name
Intel RealSense D455

Serial Number
234222301584

Firmware Version
5.15.1

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
3.2

Product Line
D400

Asic Serial Number
226523134184

Firmware Update Id
226523134184

I am an architecture student using the D455 as part of my thesis. I have no programming experience, but I am facing difficulties using the rs.convert(ply) tool. In my attempt to address this issue, I referred to GitHub issue #7678 and tried to export PLY data instead of bag data using the sample Python script called export_ply_example.py available on this GitHub page:
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/export_ply_example.py
I ran the script in Visual Studio Code, and I encountered the following error message:
PS C:\Users\xx> & C:/Users/xx/AppData/Local/Programs/Python/Python38/python.exe c:/Users/xx/Downloads/export_ply_example.py Traceback (most recent call last):   File "c:/Users/xx/Downloads/export_ply_example.py", line 32, in <module>     frames = pipe.wait_for_frames(1000) RuntimeError: Frame didn't arrive within 1000
Could you please check if there are any issues with the following steps:

Open Intel RealSenseViewer v2.54.2.
Turn on the Intel RealSense D455.
Run the export_ply_example.py script.

I would appreciate any assistance you can provide in resolving this issue. Thank you.

Hi, thank you for your reply!

Objective: My ultimate goal is to export a series of PLY files from a recording, capturing a sequence of frames.

Using Python Script: I have installed the pyrealsense2 library on my computer, which is necessary for interfacing with the RealSense camera. I attempted to run the provided Python script export_ply_example.py via the command prompt, as follows:

C:\Users\xx>pip install pyrealsense2
Requirement already satisfied: pyrealsense2 in c:\users\xx\appdata\local\programs\python\python38\lib\site-packages (<IP_ADDRESS>84)

C:\Users\xx>cd C:\Users\xx\Downloads

C:\Users\xx\Downloads>python export_ply_example.py
Saving to 1.ply...
Done

Issue with Export: The script executed successfully without any errors. However, I expected to see multiple PLY files saved as a result of running the script. My goal was to have each frame from the recording exported as a separate PLY file.

Current Outcome: Unfortunately, I did not find any PLY files saved at the specified file save location. This is the main issue I'm facing.

Using the Export Button: I also explored the RealSense Viewer tool, which has an "Export" button in 3D mode. However, it seems to allow exporting only one frame of a PLY file at a time, which is not practical for my requirement of exporting multiple frames.

I would greatly appreciate your guidance and support in resolving this issue. My thesis project heavily relies on accurately exporting and analyzing the point cloud data from the RealSense camera recording.
If you could provide step-by-step instructions or advice on how to configure the RealSense camera or the Python script to export multiple PLY files from a recording, it would be immensely helpful.
Thank you for your time and assistance.

You may be able to achieve your goal with export_ply_example.py if you edit its code so that it loops the script by commenting out the pipe.stop() instruction at the end of the script.
You would also have to rewrite the filename code so that instead of using the fixed ply name "1.ply", it increases the filename by 1 for each time that the script loops (1.ply, 2.ply, 3.ply, etc).  This can be done by generating a filename from separate strings that are then assembled together into a single name (e.g "1" and ".ply" makes "1.ply").  The principles of doing so are discussed at the link below.
https://bobbyhadz.com/blog/python-create-file-name-using-variables

Hi, thank you for your response.
I'm pleased to let you know that I've successfully exported all my .ply files using the rs-convert tool. I managed this by moving the .bag file in the same folder as the tool (C:\Program Files (x86)\Intel RealSense SDK 2.0\tools), and then running it in the command prompt. I hope this might be helpful for your reference in the future.

You are very welcome.  It's great to hear that you were successful with ply export via rs-convert.  Thanks so much for the the update and for sharing the details of your solution!   As your problem is solved, I will close this case.  Thanks again!


should we use "raspbian" instead of "rasbian" ?

https://github.com/camel-labs/camel-labs/tree/master/iot/initd/rasbian

Good catch! Fixed.


Yarn dev fails on Linux Subsystem for Windows 10

I've been using this boilerplate without issue for most of the year on my project so just wanted to first say thanks for all the hard work!
However revisiting the project after a few months, now that I'm running the Linux Subsystem for Windows 10, I cannot seem to compile anything when running yarn dev.
My setup:
Windows: Version 1803 OS Build 17134.228
Linux Subsystem: 16.04.4 LTS (Xenial Xerus)
Node: v9.10.0
Npm: 5.6.0
Yarn: 1.7.0
yarn dev
yarn run v1.7.0
$ cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 yarn start-renderer-dev
$ cross-env NODE_ENV=development node --trace-warnings -r babel-register ./node_modules/webpack-dev-server/bin/webpack-dev-server --config webpack.config.renderer.dev.js
Starting Main Process...
<EMAIL_ADDRESS>start-main-dev /mnt/c/users/[user]/src/electron-react-boilerplate
cross-env HOT=1 NODE_ENV=development electron -r babel-register ./app/main.dev.js
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start-main-dev: 'cross-env HOT=1 NODE_ENV=development electron -r babel-register ./app/main.dev.js'
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start-main-dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/[user]/.npm/_logs/2018-09-03T11_53_01_899Z-debug.log
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I've also tried to obtain the debug logs but the log files themselves are simply empty.
Side note, I've been able to compile my project and a fresh clone of the boilerplate on my macOS machine running 10.13.6 with no problems.
Let me know if I can provide anything else, cheers!

Upload the logs please

Thanks for the help. Logs attached from an attempt earlier today.
0 info it worked if it ends with ok
1 verbose cli [ '/home/[user]/.nvm/versions/node/v9.10.0/bin/node',
1 verbose cli   '/home/[user]/.nvm/versions/node/v9.10.0/bin/npm',
1 verbose cli   'run',
1 verbose cli   'dev' ]2 info using<EMAIL_ADDRESS>info using<EMAIL_ADDRESS>verbose run-script [ 'predev', 'dev', 'postdev' ]5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true8 verbose lifecycle<EMAIL_ADDRESS>PATH: /home/[user]/.nvm/versions/node/v9.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/c/users/[user]/src/electron-react-boilerplate/node_modules/.bin:/home/[user]/gems/bin:/home/[user]/.nvm/versions/node/v9.10.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files (x86)/Intel/iCLS Client:/mnt/c/Program Files/Intel/iCLS Client:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Windows/System32/OpenSSH:/mnt/c/Ruby23-x64/bin:/mnt/c/Users/[user]/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/Microsoft VS Code/bin:/mnt/c/Users/[user]/AppData/Local/hyper/app-2.0.0/resources/bin:/mnt/c/Users/[user]/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/[user]/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/Users/[user]/AppData/Local/GitHubDesktop/bin9 verbose lifecycle<EMAIL_ADDRESS>CWD: /mnt/c/users/[user]/src/electron-react-boilerplate10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',10 silly lifecycle   'cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 yarn start-renderer-dev' ]11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null12 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
13 verbose stack Error<EMAIL_ADDRESS>dev: `cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 yarn start-renderer-dev`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/[user]/.nvm/versions/node/v9.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack     at EventEmitter.emit (events.js:180:13)
13 verbose stack     at ChildProcess.<anonymous> (/home/[user]/.nvm/versions/node/v9.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:180:13)
13 verbose stack     at maybeClose (internal/child_process.js:936:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /mnt/c/users/[user]/src/electron-react-boilerplate
16 verbose Linux 4.4.0-17134-Microsoft17 verbose argv "/home/[user]/.nvm/versions/node/v9.10.0/bin/node" "/home/[user]/.nvm/versions/node/v9.10.0/bin/npm" "run" "dev"
18 verbose node v9.10.0
19 verbose npm  v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>dev: `cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 yarn start-renderer-dev`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
"2018-09-03T11_25_26_156Z-debug.log" 38L, 4117C


Offset marked as obsolete?

Title.
Why is it marked as obsolete? The data still exists in the JSON response and is very usable.

Please see: https://darksky.net/dev/docs/response Use timezone instead. I'm just reflecting the official document in the annotation.

Ah, sorry, did not see that. Although, I feel like the Obsolete comment should have been more clear like the documentation. Instead of Use Timezone instead, maybe something like Use of this property will almost certainly result in Daylight Saving Time bugs. Please use timezone, instead. like the docs?

Fair enough.

Fixed in v3.0.0 (was also in v2.0.0 but I made a mistake and that version will cause issues).


[SDK Unfork] fix x/superfluid/keeper package tests

Background
The x/superfluid/keeper  package needs to be updated to work on our fork of the cosmos-sdk
PRs should be made from and to the https://github.com/osmosis-labs/osmosis/pull/6413 branch
Suggested Design

Find and fix all tests in the superfluid package
Various off by one breaks here
Initial thoughts are around registering of validator in the setup

        --- FAIL: TestKeeperTestSuite/TestDistributeSuperfluidGauges/happy_path_with_single_validator_and_delegator#01 (0.03s)
            epoch_test.go:327:
                	Error Trace:	/home/ghost/git/osmosis-labs/broken/osmosis/x/superfluid/keeper/epoch_test.go:327
                	            				/home/ghost/go/pkg/mod/github.com/stretchr/testify@v1.8.4/suite/suite.go:112
                	Error:      	Not equal:
                	            	expected: "19999stake"
                	            	actual  : "18181stake"

                	            	Diff:
                	            	--- Expected
                	            	+++ Actual
                	            	@@ -1 +1 @@
                	            	-19999stake
                	            	+18181stake
                	Test:       	TestKeeperTestSuite/TestDistributeSuperfluidGauges/happy_path_with_single_validator_and_delegator#01

Acceptance Criteria

All tests pass

Fixed!