text:
New vis

Many, many changes related to supporting SimPixel. And some cleanup as well.

All right!
So let me say overall that my plan is to get this out as soon as possible and then push further reviews to fix any non-critical problems I discover.
I've been looking at this branch already of course... :-D
It does actually pass tests and the coverage testing isn't much worse - though we're mis-measuring that.
And I assume you are testing it on hardware at your end too.  So I'm inclined to want few changes to this now, and then cleanups later.
Specific comments to follow.

Yeah... I realize coverage is a little worse. I was mostly just trying to
get it in front of you before we diverged too much with MP stuff or
something. Will certainly add in new tests for all the new layout stuff and
others shortly.
On Sun, Feb 12, 2017 at 5:21 AM, Tom Swirly notifications@github.com
wrote:

All right!
So let me say overall that my plan is to get this out as soon as possible
and then push further reviews to fix any non-critical problems I discover.
I've been looking at this branch already of course... :-D
It does actually pass tests and the coverage testing isn't much worse -
though we're mis-measuring that.
And I assume you are testing it on hardware at your end too. So I'm
inclined to want few changes to this now, and then cleanups later.
Specific comments to follow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/101#issuecomment-279208895,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6riFG1RYPbOPjWoiJZlxAHPJV1b9ks5rbt0egaJpZM4L-Scj
.

SHIT!  Did that go out already piecemeal?  I was intending to have one long
blop of comments!
Well, wait till the end to reply.  :-D
On 12 February 2017 at 12:50, Adam Haile notifications@github.com wrote:

Yeah... I realize coverage is a little worse. I was mostly just trying to
get it in front of you before we diverged too much with MP stuff or
something. Will certainly add in new tests for all the new layout stuff and
others shortly.
On Sun, Feb 12, 2017 at 5:21 AM, Tom Swirly notifications@github.com
wrote:

All right!
So let me say overall that my plan is to get this out as soon as possible
and then push further reviews to fix any non-critical problems I
discover.
I've been looking at this branch already of course... :-D
It does actually pass tests and the coverage testing isn't much worse -
though we're mis-measuring that.
And I assume you are testing it on hardware at your end too. So I'm
inclined to want few changes to this now, and then cleanups later.
Specific comments to follow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
101#issuecomment-279208895>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6riFG1RYPbOPjWoiJZlxAHPJV1b9ks5rbt0egaJpZM4L-Scj>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/101#issuecomment-279213230,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdslxldVlVrsuoDu055wdHFrtq5G_3ks5rbvIMgaJpZM4L-Scj
.

--
/t
http://radio.swirly.com - art music radio 24/7 366/1000

lol...yeah, they go out as you make the comments.
On Sun, Feb 12, 2017 at 6:55 AM, Tom Swirly notifications@github.com
wrote:

SHIT! Did that go out already piecemeal? I was intending to have one long
blop of comments!
Well, wait till the end to reply. :-D
On 12 February 2017 at 12:50, Adam Haile notifications@github.com wrote:

Yeah... I realize coverage is a little worse. I was mostly just trying to
get it in front of you before we diverged too much with MP stuff or
something. Will certainly add in new tests for all the new layout stuff
and
others shortly.
On Sun, Feb 12, 2017 at 5:21 AM, Tom Swirly notifications@github.com
wrote:

All right!
So let me say overall that my plan is to get this out as soon as
possible
and then push further reviews to fix any non-critical problems I
discover.
I've been looking at this branch already of course... :-D
It does actually pass tests and the coverage testing isn't much worse -
though we're mis-measuring that.
And I assume you are testing it on hardware at your end too. So I'm
inclined to want few changes to this now, and then cleanups later.
Specific comments to follow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
101#issuecomment-279208895>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6riFG1RYPbOPjWoiJZlxAHPJV1b9ks5rbt0egaJpZM4L-Scj>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
101#issuecomment-279213230>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAPdslxldVlVrsuoDu055wdHFrtq5G_3ks5rbvIMgaJpZM4L-Scj>
.

--
/t
http://radio.swirly.com - art music radio 24/7 366/1000
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/101#issuecomment-279213488,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6pWFyqZ7i5-x04jlna_GlB6dmhYJks5rbvNDgaJpZM4L-Scj
.

Urg, I thought I set "start a review"?
Well, w/e.
On 12 February 2017 at 13:06, Adam Haile notifications@github.com wrote:

lol...yeah, they go out as you make the comments.
On Sun, Feb 12, 2017 at 6:55 AM, Tom Swirly notifications@github.com
wrote:

SHIT! Did that go out already piecemeal? I was intending to have one long
blop of comments!
Well, wait till the end to reply. :-D
On 12 February 2017 at 12:50, Adam Haile notifications@github.com
wrote:

Yeah... I realize coverage is a little worse. I was mostly just trying
to
get it in front of you before we diverged too much with MP stuff or
something. Will certainly add in new tests for all the new layout stuff
and
others shortly.
On Sun, Feb 12, 2017 at 5:21 AM, Tom Swirly notifications@github.com
wrote:

All right!
So let me say overall that my plan is to get this out as soon as
possible
and then push further reviews to fix any non-critical problems I
discover.
I've been looking at this branch already of course... :-D
It does actually pass tests and the coverage testing isn't much
worse -
though we're mis-measuring that.
And I assume you are testing it on hardware at your end too. So I'm
inclined to want few changes to this now, and then cleanups later.
Specific comments to follow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
101#issuecomment-279208895>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6riFG1RYPbOPjWoiJZlxAHPJV1b9ks5rbt0egaJpZM4L-Scj>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
101#issuecomment-279213230>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAPdslxldVlVrsuoDu055wdHFrtq5G_3ks5rbvIMgaJpZM4L-Scj>
.

--
/t
http://radio.swirly.com - art music radio 24/7 366/1000
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
101#issuecomment-279213488>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AA6a6pWFyqZ7i5-x04jlna_GlB6dmhYJks5rbvNDgaJpZM4L-Scj>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/101#issuecomment-279214035,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsmkVj9QFEOpzkfJl-Kaj1_09GhCGks5rbvW3gaJpZM4L-Scj
.

--
/t
http://radio.swirly.com - art music radio 24/7 366/1000

I'm going to send out the comments so far as a blob, because they got rebased away from the main - they're still basically good now but in a few rebases... :-)

blah blah blah 👍

authors: adammhaile rec

repo: ManiacalLabs/BiblioPixel


text:
Flat lib

Follow flat_lib in alphabase: https://github.com/MannLabs/alphabase/pull/53
Add FlatPredictSpecLib.predict_and_parse_in_batch() for large libraries

Test failed as this PR requires https://github.com/MannLabs/alphabase/pull/53 released on pip

source: gharchive/pull-request

repo: MannLabs/alphapeptdeep

license_type: permissive

license_source: github-api


text:
Review requirements.txt

The requierements.txt file is possibly not up to date.

we've addressed this issue by making the documentation more explicit and providing clear and precise install instructions for scportrait if the stitching capabilities want to be used. I don't think there is any workaround for having a working java installation for the stitching as we require the use of the Bioformats library to be able to work with a multitude of different imaging formats. If we create a conda release we could address this issue by providing java within the conda specs.

source: gharchive/issue

authors: namsaraeva sophiamaedler

repo: MannLabs/scPortrait


text:
Installing in the correct folder ?

I have followed you advice given that is composer require slim/slim "^3.0"
Now when I go it create a folder called vendor and in it is slim with many slims folder like this /var/www/html/vendor/slim/slim/Slim so where to copy your codes ? Please advice ?

Hi @newbie14 ,
This is my configuration. I hope you find it useful.

Hi manuel,
Thank you so added on your public and src folder rite ?

@newbie14 , you can add the folders in the root and run the web service without problems

@ManuelGil I dont get what you do you mean by adding the folders in root? I need to run different application besides this api ?

repo: ManuelGil/REST-Api-with-Slim-PHP

license: MIT


text:
Added Geometry Simplify Provider

This can be used to Simplify the Geometries and increase the Drawing speed (less complexity).

This is a provider that I wrote for the V2 TiliningLayer Pull request and can be used without a tiling Layer

The Sample number 5 is intentional because I have The Sample number 4 used in the TilingProvider pull request.

repo: Mapsui/Mapsui


text:
[4.1] MapControl: Reset widget cache

This is my attempt to fix #2599. I'm adding a method that triggers the re-caching of widgets in MapControl. The method is protected, so that it can be called in all classes derived from MapControl (including MapView etc). This should be enough to fix the problem (for me).

This should be enough to fix the problem (for me).

I just verified via the GHA-generated nupkgs that this does indeed fix the problem for me. And yes, it does!
All I do is call the new method ResetWidgetCache after switching layers.
@giobiondani Does this work for you as well, or do you need the method to be public?
@pauldendulk Is this PR ok for the develop/4.1 branch? Or can we find a way to make this work automatically (without the additional call to ResetWidgetCache)?

This should be enough to fix the problem (for me).

I just verified via the GHA-generated nupkgs that this does indeed fix the problem for me. And yes, it does!
All I do is call the new method ResetWidgetCache after switching layers.
@giobiondani Does this work for you as well, or do you need the method to be public?
@pauldendulk Is this PR ok for the develop/4.1 branch? Or can we find a way to make this work automatically (without the additional call to ResetWidgetCache)?

In my case I had to create my own code to manage the attributions anyway because I realized that Stadia and Thunderforest require multiple separate URL links in the same attribution and as far as I can tell I can't do that with the standard Attribution object. So I guess this isn't relevant anymore to my case.

So I guess this isn't relevant anymore to my case.

Thanks for the comment :)

I think this is currently the Best solution Because change notification was removed or will be removed.

I'm not fully sure what you mean by "change notification was removed", @inforithmics, but in #2694 @pauldendulk mentioned that the caching of widgets is removed entirely in v5. So in any case, it seems like this problem only still exists on the stable v4.1.x, and we should try to apply a simple fix there without too much restructuring. My fix is really the least intrusive way of fixing it, I think.
Since @inforithmics has approved this PR (and I need the fix rather urgently) I will merge it tonight, unless anyone objects until then.

In Mapsui 5.0 the Widget can indicate that it needs a Redraw NeedsRedraw So that it is again rendered. So this cache isn't needed there.

In Mapsui 5.0 the Widget can indicate that it needs a Redraw NeedsRedraw So that it is again rendered. So this cache isn't needed there.

Thanks for the comment! I merged this now.
@pauldendulk @inforithmics Do you think we can tag a version 4.1.8 or 4.1.8-beta.2 soon?

authors: giobiondani inforithmics janusw


text:
Headers not sent

Describe the bug
Headers parameters are specified in method arguments, but not set in headers
Headers parameters in OpenAPI schema:
"parameters": [
    {
        "required": true,
        "schema": { "title": "Api-Key", "type": "string" },
        "name": "api-key",
        "in": "header"
    }
],

Generated code:
def update_groups_v1_actions_accounts_update_groups_post(
    api_key: str, # header parameter
    data: AccountRequest,
) -> UpdateAccountGroupsResponse:
    base_path = APIConfig.base_path
    path = f"/v1/actions/accounts/update_groups"
    # not in headers
    headers = {
        "Content-Type": "application/json",
        "Accept": "application/json",
        "Authorization": f"Bearer { APIConfig.get_access_token() }",
    }

To Reproduce
Tested schema https://pastebin.com/6HvTY3ZF
Expected behavior
All headers parameters must be specified

Is this strictly related to api-key params in the header or also other header params?

Same result for https://pastebin.com/NLBEcVW2 with two headers parameters - api_key and some_param. It is cutted example from Swagger Editor, so I think schema is valid and error somewhere in generator (some_param was added later, it also don't work only with api_key)
def deletePet(
    api_key: str, # unused
    some_param: str, #unused
    petId: int,
) -> None:
    base_path = APIConfig.base_path
    path = f"/pet/{petId}"
    headers = {
        "Content-Type": "application/json",
        "Accept": "application/json",
        "Authorization": f"Bearer { APIConfig.get_access_token() }",
    }
    query_params: Dict[str, Any] = {}

    query_params = {key: value for (key, value) in query_params.items() if value is not None}

    with httpx.Client(base_url=base_path, verify=APIConfig.verify) as client:
        response = client.request(
            "delete",
            httpx.URL(path),
            headers=headers,
            params=query_params,
        )

    if response.status_code != 200:
        raise HTTPException(response.status_code, f" failed with status code: {response.status_code}")
    return response.json()

authors: MarcoMuellner mamsdeveloper

repo: MarcoMuellner/openapi-python-generator


text:
Add support for condition evaluation

This PR adds evaluation of condition elements of the CMakePresets.json, with the goal of making Linux and Windows builds easier to co-exist. The PR adds support for not, equals and notEquals expressions, and improves the macro expansion to include hostSystemName. When selecting a 'build' or 'configure' preset, any preset that has a condition that evaluates to false will be ignored, and any build preset that has a corresponding configure preset with a condition that evaluates to false will be ignored. This means if presets are marked with a condition that specifies a hostSystemName, only the matching presets will be used for tab-completion, and the default build configuration. As a result, running Build-CMakeBuild will use the first non-hidden, condition-matching preset.

Ah, I should've said, this fixes #20.

repo: MarkSchofield/PSCMake


text:
Only check for timeout if not logged in remotely

Motivation and Context

If logged in with remote authentication, the remote authenticator handles its own timeouts so we don't need to artificially handle timeouts in MarkUs. Otherwise it is just annoying for the user:

if MarkUs times out before the remote authenticator, the user has to re-log in to MarkUs even though their login credentials haven't expired
if the remote authenticator times out before MarkUs, there is no warning and pages will just stop loading all of a sudden

Your Changes

Description:
Type of change (select all that apply):

[x] Bug fix (non-breaking change which fixes an issue)

Testing

Questions and Comments (if applicable)

Checklist

[x] I have performed a self-review of my own code.
[x] I have fixed any Hound bot comments.
[ ] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported on Coveralls.
[x] I have updated the Changelog.md file.

Required documentation changes (if applicable)

TODO: don't check for imminent timeout if logged in remotely

failing tests are unrelated to this PR

repo: MarkUsProject/Markus


text:
Disconnecting when there is a lot of volume

Thank you so much for putting this together. Its been very helpful. I am running into an issue where it is disconnecting during heavy trading hours (open,close). I wonder if it would be more efficient to do the time conversion and columns in stream_listener.py script and just have the stock_stream.py scripts bring the data in. I am pretty new to Python, so I could just be messing something up. Thanks again for putting this together its excellent.

MarketMakerLite, do you ever do any programming on the side for other people? I would, of course, pay you for your time. I would like to get this working with no disconnects and add a few other options. If you are interested, please send me an email at rogray2@gmail.com. Thanks for all your time putting this together.

Hey rogray85, thanks for raising this issue. I'm wondering if this might be a hardware limitation or possibly related to the redis config. I will look into it, and I'm also interested in hearing your thoughts on extra options to add. If you have Discord, please join the server here: https://discord.gg/jjDcZcqXWy and we can try a few different things.

Thank you for the quick response. I don't think it hardware related. I have a good amount of memory (288GB) and a decently powerful computer, but I could be wrong. I did modify your code; I should have mentioned that previously, and maybe that is where I am having the issue. The options_stream.py is working perfectly. I have attached the modified script below to get all the trades instead of the second quotes. Any help you could provide, I would greatly appreciate it.
I will join the Discord. Thank you for the invite, and share some ideas. I moved over from LiveVol to Polygon to get more data-driven, and your script has been beneficial.
Thank you again for any help you can provide.
Thank you,
O'Neal Gray II
Cell: 214-724-2020

On Jan 26, 2022, at 1:24 PM, MML @.***> wrote:
Hey rogray85, thanks for raising this issue. I'm wondering if this might be a hardware limitation or possibly related to the redis config. I will look into it, and I'm also interested in hearing your thoughts on extra options to add. If you have Discord, please join the server here: https://discord.gg/jjDcZcqXWy and we can try a few different things.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

@MarketMakerLite feel free to close this issue since the reason behind disconnection is the sheer high number of messages (as high as 15000 a second on just trades sub)
The callback streamer isn't the best option to choose for anyone needing to deal with very high number of msgs. They should use the async streamer with uvloop to ensure good performance. Using orjson instead of the builtin json or third party ujson/simplejson should be preferred.

repo: MarketMakerLite/polygon


text:
The argument 'saveAs' of 'Wait For Download' is not working

Describe the bug
The argument 'saveAs' of keyword 'Wait For Download' is not working.
To Reproduce
Steps to reproduce the behavior:

*** Settings ***
Library    OperatingSystem
Library    Browser    timeout=20s    enable_playwright_debug=true    auto_closing_level=MANUAL
*** Variables ***
${dwl}    c:${/}temp${/}npp
${url}    https://notepad-plus-plus.org/downloads/v7.9.1/
*** Test Cases ***
TC01 Download NPP
New Browser    chromium    headless=false    downloadsPath=${dwl}
New Context    acceptDownloads=${TRUE}
New Page
Go To    ${url}
${dwl_promise}    Promise To    Wait For Download    saveAs=npp7.exe
Click    //*[@id="main"]/p[5]/a
${file_path}=    Wait For    ${dwl_promise}
File Should Exist    ${file_path}
Log    ${file_path}

Expected behavior
File should be downloaded successfully and saved with name 'npp7.exe'
Screenshots
File downloaded succefully, but the name is incorrect.

Though download location of chrome browser is not changed to 'C:/temp/npp' I specified in the script, but the file was actually downloaded in the folder

Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 88.0.4287.0
Browser library: 2.1.0

There is bug, but the bug is in the documentation. saveAs argument does not define the filename, as the documentation incorrectly claims, but it defines a path where the file is saved. The enhancement in https://github.com/MarketSquare/robotframework-browser/issues/597 in next release will change the functionality and return also the suggested filename from the browser/web app.

There is bug, but the bug is in the documentation. saveAs argument does not define the filename, as the documentation incorrectly claims, but it defines a path where the file is saved. The enhancement in https://github.com/MarketSquare/robotframework-browser/issues/597 in next release will change the functionality and return also the suggested filename from the browser/web app.

@all-contributors please add @estimation for userTesting

@all-contributors please add @estimation for userTesting

authors: aaltat estimation

repo: MarketSquare/robotframework-browser


text:
403 Forbidden

When i click on Generate button nothing happen. Looking at the console, i found out that the request returned 403 status code.

Seem like the website reached the GitHub API rate limit

For unauthenticated requests, the rate limit allows you to make up to 60 requests per hour

You could fork this repo and host it on your IP to eliminate the limit.

authors: DiSiqueira MarkoCen

repo: MarkoCen/github-flair

license: mit

license_source: bigquery


text:
NPM ERR! building frontend

Raspberry Pi 3 running Raspbian Jessie. Successfully cloned and ran npm install. Then failed with a ton of errors on npm run build.
Here's a gist with the debug log
Quick Googling of npm ERR! code ELIFECYCLE errno 2 did not return any help for me.
Thanks in advance for any help.

I sent the output to a file instead of stdout so I could actually read it and found this.
ERROR in ./node_modules/css-loader?{"importLoaders":1}!./node_modules/vue-loader/lib/style-compiler?{"vue":true,"id":"data-v-2ccece95","scoped":false,"hasInlineConfig":false}!./node_modules/postcss-loader/lib!./node_modules/sass-loader/...
Module build failed: Error: Node Sass does not yet support your current environment: Linux Unsupported architecture (arm) with Node.js 8.x
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.8.3

Node-Sass does not have an ARM binary available so Node was complaining. It looks like I'll have to compile it from source:
https://github.com/sass/node-sass/issues/1609

Okay that fixed that issue. I'm getting a new one now:
ERROR in ./frontend/img/models/model-google-home-carbon.png
Module build failed: Error: spawn /home/pi/google-home-notification-gateway/node_modules/optipng-bin/vendor/optipng ENOENT

Which looks like optipng is having a problem and may be solved by npm install gulp-imagemin

Which looks like optipng is having a problem and may be solved by npm install gulp-imagemin

That didn't work. Same errors as a few minutes ago.

Ok you try to install GHNG on Pi, didn't know for Node-sass and ARM sorry.
I think I'll commit sources already built to solve this issue (should fix the imagemin issue too)

Ok done,
I added the prebuilt public folder to git.
So now, just re-clone the repository, and do:
$ npm install
And don't build the frontend, just start the app directly:
$ npm run start

I deleted the entire GHNG directory and re-cloned it. Ran npm install and got a new error
https://gist.github.com/starbuck93/a1c04f6d544e6512fa7c22ff7cd7a79f
After a little bit of trial and error... Googled "dns_sd.h: No such file or directory" and found this fix: sudo apt-get install libavahi-compat-libdnssd-dev then ran npm install mdns again.
It looks like it finished successfully but got the same error about eslint needs "peer dependencies". Okay, let's npm install eslint.
Weird. It still came up with the same warning:
npm WARN eslint-config-import@0.13.0 requires a peer of eslint-plugin-import@0.13.x but none is installed. You must install peer dependencies yourself.
Tried to install fsevents and got
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: arm

But tried npm install again and it didn't exactly fail (it had a warning)
so npm start:
...
throw new Error('Please install sqlite3 package manually');
...

Okay, so npm install sqlite3
10 years later after compiling from source
npm start
sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators node_modules/sequelize/lib/sequelize.js:242:13
module.js:538
    throw err;
    ^
Error: Cannot find module '/home/pi/google-home-notification-gateway/node_modules/bcrypt/lib/binding/bcrypt_lib.node'

I'm determined
npm install bcrypt
That seemed to work.
npm start didn't fail!
I had to type in !adminpassword! several times but it eventually let me in.

Thank a lot for your determination ^^ and for sharing all these issues.
I'll try to reproduce and fix all these dependencies issues, can you tell me more about your environment ? It seems you are using a debian based OS (Raspbian probably ?)

Sure thing:
Raspberry Pi 3 B
Linux hassbian 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
10:49:15 up 74 days, 36 min,  2 users,  load average: 0.07, 0.08, 0.08
npm 5.5.1
node v8.9.3
I think I installed this image from the Home Assistant "Hassbian" a while ago, sorry I don't have more details on that bit.
Maybe there's a few more details in the first debug log I shared in the beginning.


text:
Uncaught Exception: listen EADDRINUSE 0.0.0.0:5672

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.2.4
Time: Sun May 15 2016 14:11:39 GMT-0700 (Pacific Daylight Time)
Error:
listen EADDRINUSE 0.0.0.0:5672
Error: listen EADDRINUSE 0.0.0.0:5672
    at Object.exports._errnoException (util.js:890:11)
    at exports._exceptionWithHostPort (util.js:913:20)
    at Server._listen2 (net.js:1234:14)
    at listen (net.js:1270:10)
    at net.js:1379:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #325

authors: GPMDP-Magical-Unicorn zacharygoold


text:
Currently playing song displaying incorrectly with dark theme

OS: Windows 10 Pro Build 14393.105
Issue Descriptions:
Looks like Google may have changed some web player CSS, as the dark theme breaks on the highlighted song.

Steps to Reproduce:

Be running v3.5.0
Change to dark theme in settings
Play a song in a playlist, or open now playing queue - the current song has strange artefacts where theme is badly applied

Please raise over at https://github.com/gmusic-utils/gmusic-theme.js

authors: MarshallOfSound ZephireNZ


text:
Have an official dlang REPL

Currently there is drepl and dabble, both weren't compilable when I looked at them. It seems to me that having a working REPL is nowadays an essential feature of a language and we should try to get some manpower and maintainer on this. Even C++ has this!
How about this agenda?

Bring  in a good shape (not perfect)
Move to github.com/dlang/repl
Get it stable
Include into release with dmd, rdmd and dub (as idmd)
Continue with more features

:+1: for this. If this repo is unmaintained now and should be forked, I'm on board.

:+1: for this. If this repo is unmaintained now and should be forked, I'm on board.

I have pushed my working fork to drepl/drepl. That's probably the easiest and at some point we hopefully can move over to the dlang namespace.
So let's make further plans over there?

Let me at least transfer the repo so we maintain the issue tracker.

Let me at least transfer the repo so we maintain the issue tracker.

Great to hear that you are alive - you should have full admin acces. Feel free to move ;-)

We first need to delete the other repo, I'll try to migrate the issues over to here.

We first need to delete the other repo, I'll try to migrate the issues over to here.

No worries - I renamed it to drepl-old, so we can do this after you moved it over.
It's just two issues, so just removing them shouldn't hurt.

Already done

Already done

Great - then I close this issue and once we feel confident enough, we can propose that's moved to dlang?

Already done

I forgot: Thanks a lot, Martin!

authors: MartinNowak carljv wilzbach

repo: MartinNowak/drepl


text:
fix: add equal 0 condition to least square method section

線形最小二乗法の説明の式10番で、Sを最小にする条件の式の辺解から"= 0"の記述が抜けていたため追記しました。
些細なこととは思いますが…

Thank you for pointing out the mistake.
I will merge your PR.

repo: MasatakaYm/Molecular-Simulation


text:
Comparing with lists

In implementing a client, I have a hard to time to query and retrieve all 2-dimensional structures - as an example.
In trying to figure this out, I found that there is no way to query for property(that is a list) = value, which is maybe okay?
But can be a problem in some instances.
Specifically for dimension_types this can be solved with a query possibility of counting a value in a list, i.e., "how many of X is there in property_list Y". With this, one could check for the number of zeros (and/or ones) in dimension_types and deduce the dimensionality of the structure.
If there are some clever tricks in the current filter language to be combined and get unique results for these issues I would be very interested to know of them.

I already mentioned before so I just conclude another concept very briefly and hope that this time it will get more support :)

All the comparison operations happen element-wise (=, <, >, AND, OR)
"Functions" can be defined to reduce all the dimensions to scalar values
Disclaimer: all these changes only related to arrays and most of them are optional

list HAS value                      -> ANY(list = value)
list HAS ALL [value1, value2, ...]  -> ANY(list = value1) AND ANY(list = value2) AND ...
list HAS ANY [value1, value2, ...]  -> ANY(list = value1) OR ANY(list = value2) OR ...
list LENGTH value                   -> LENGTH(list) = value

HAS ONLY [value1, value2, ...]      -> ALL(list = value1 OR list = value2 OR ...)
NOT list HAS inverse                -> NOT ANY(list = inverse)

I'm not sure that I managed to interpert properly but I try do my best:
list1:list2:... HAS val1:val2:...      -> ANY(list1 = val1 AND list2 = val2 AND ...)
list1:list2:... HAS ALL val1:val2:...  -> ALL(list1 = val1 AND list2 = val2 AND ...) ???
list1:list2:... HAS ANY val1:val2:...  -> ANY(list1 = val1 OR list2 = val2 OR ...)
list1:list2:... HAS ONLY val1:val2:... -> ANY(list1 = val1 AND list2 = val2 AND ...) ???

For example:
matches all entries for which list contains at least one element that is less than three:
list HAS < 3
ANY(list < 3)

matches only those entries for which list simultaneously contains at least one element less than three and one elements greater than three:
list HAS ALL < 3, > 3
ANY(list < 3) AND ANY(list > 3)

matches all entries for which list contains at least one element that is between the values 2 and 5:
list:list HAS >=2:<=5
ANY(list >= 2 AND list <= 5)

And now back to the original issue:
2D only
COUNT(dimension_types = 1) = 2

1D and 2D
COUNT(dimension_types = 1) <= 2

where the COUNT OR SUM is the same type of "dimension reducer" function like ANY or ALL or LENGHT.
I'm a little bit biased by python but I think most of our intended users as well.
The current definition is very compact (which is very nice) but I would sacrifice a little bit on the compactness if it is easier to understand the new definition.
It is a lot of work especially to implement the details but I would be happy to prepare the changes for the grammar specifications.
I completely agree that defining a property in another representation is a "good" solution right now but this concept implements in a future release ...

I think the idea is interesting and in general I find you suggestion probably a bit more intuitive than the current (but both require anyway some time to grasp them). However I a bit scared that this change of grammar is not something that can be done in a few days, many clients are implementing the existing grammar, and it would require some testing to make sure the new grammar doesn't have different difficulties...
With the aim to release 1.0 very soon, I don't know what to suggest.
Probably we should check if this new grammar is "better" in some sense (easier to use or to implement or more powerful...), and work on it for v2? Ideally it should be a superset, and we should come with an automatic query converter from the old to the new syntax.
But other opinions are welcome, I am not an expert of grammars!

authors: CasperWA fekad giovannipizzi

repo: Materials-Consortia/OPTIMADE


text:
Algorytm ByteRun - P7

Zaimplementować algorytm ByteRun.

Kompresja wyświetlanego obrazka algorytmem ByteRun.
Dane wejściowe muszą być 8 bitowe ( Uint8_t ).
Dane wyjściowe muszą być zapisane do osobnego pliku ( .byterun ).

Analogicznie zaimplementować algorytm dekompresji ByteRun.

Dekompresja pliku wejściowego ( .byterun )
Dane wejściowe muszą być 8 bitowe ( Uint8_t )
Dane wyjściowe zostają wyświetlone w formie zdekompresowanego obrazka w prawym górnym rogu okna.

masakra


text:
Update Build Notes. Add Steps for compilation via VS2015

Hi,
I have updated Build Notes to add compilation steps using VS2015 and have successfully tested it.

Continuous Integration build is failing because of the following error
"Error uploading artifact the storage: Remote server returned 500: Operation could not be completed within the specified time". It has nothing to do with my PR.

Thank you for your contribution.
This would make Captura buildable by a larger number of users. 👍

authors: MathewSachin armujahid

repo: MathewSachin/Captura


text:
"_fke.csv"

kit dataset originally had "_fke.csv" file, or was it generated by data preprocessing? If it was generated by preprocessing, could you please send me the code

I got the same question, did you fix it? I can only find files end with "_quat.csv" and "_quat.fke"

Hello both @1390806607 @maplect,
As explained in the readme, you should run the code from Ghosh et al or JL2P to process the data. It will create the files which ends with "fke.csv". The code links are in the readme.
Tell me if you have any issues

Hello both @1390806607 @maplect,
As explained in the readme, you should run the code from Ghosh et al or JL2P to process the data. It will create the files which ends with "fke.csv". The code links are in the readme.
Tell me if you have any issues

Many thanks for your rapid reply. I got the problem, I firstly run the code from JL2P, and the output of find datasets/kit/* -name . -o -prune | head -20 is
datasets/kit/00001_annotations.json datasets/kit/00001_meta.json datasets/kit/00001_mmm.xml datasets/kit/00001_quat.csv datasets/kit/00001_quat.fke datasets/kit/00001_quat.rifke datasets/kit/00001_raw.c3d datasets/kit/00002_annotations.json datasets/kit/00002_meta.json datasets/kit/00002_mmm.xml datasets/kit/00002_quat.csv datasets/kit/00002_quat.fke datasets/kit/00002_quat.rifke datasets/kit/00002_raw.c3d datasets/kit/00003_annotations.json datasets/kit/00003_meta.json datasets/kit/00003_mmm.xml datasets/kit/00003_quat.csv datasets/kit/00003_quat.fke datasets/kit/00003_quat.rifke
While I run the code from Ghosh, the output of find datasets/kit/* -name . -o -prune | head -20 is
datasets/kit/00001_annotations.json datasets/kit/00001_ax.csv datasets/kit/00001_fke.csv datasets/kit/00001_meta.json datasets/kit/00001_mmm.xml datasets/kit/00001_quat.csv datasets/kit/00001_raw.c3d datasets/kit/00001_rifke.csv datasets/kit/00002_annotations.json datasets/kit/00002_ax.csv datasets/kit/00002_fke.csv datasets/kit/00002_meta.json datasets/kit/00002_mmm.xml datasets/kit/00002_quat.csv datasets/kit/00002_raw.c3d datasets/kit/00002_rifke.csv datasets/kit/00003_annotations.json datasets/kit/00003_ax.csv datasets/kit/00003_fke.csv datasets/kit/00003_meta.json
and I can find the files which end with "fke.csv". So I think there are some differences between these two data generation script.

Hi @maplect,
I will remove JL2P from the README then, thanks for pointing it out!

authors: 1390806607 Mathux maplect

repo: Mathux/TEMOS


text:
DevTools refreshes when another tab refreshes

When listening to music from youtube, and the song chhanges, I might have a devtools open on my other window. The devtools refreshes like I would've updated the devtools page.
There's something wrong with the side channel handling these

This was fixed in 0.1.4

repo: Matsuuu/web-component-devtools


text:
Inquries: i18n interpolation, first-page problem

I have been using virtual-dom for my projects in the past 6 months, while it's an absolute joy 99% of the time, these 2 topics bother me quite a bit:
(They bother me mostly because I don't know if I am doing them as elegantly as possible. And both are not direct problems with virtual-dom, but using virtual-dom with other modules.)

Q1 - We use node-polyglot for i18n, and like most i18n libraries they support string interpolation, but in order to mix polyglot output with virtual-dom, we need to do following:
h('p.message', {
	innerHTML: i18n.t('msg.general', {
		message: '' + i18n.t('msg.error') + ''
	})
})

// msg.general = 'Hi, %{message}'

Obviously we would like to avoid hardcoding any html, so  should preferably be generated with h
And to keep our vnode p.message flexible, we should avoid innerHTML approach as well

So ideally we need to go vnode -> string -> vnode in order to use i18n interpolation involving html. That involves:

Generate message vnode with h and use vdom-to-html to convert into string
Pass it as an object attribute into polyglot, which produce the message content, as html string
Use html-to-vdom to convert content into vnodes, pass them as children into vnode p.message

I am not sure how expensive this would be, should I just use innerHTML for performance?

Q2 - Existing frameworks like mercury focus on single page app (most examples are client-side rendering); we use virtual-dom extensively server-side for first-page view rendering, and want to add client-side rendering as a progressive enhancement.
I have seen a few discussions (#49, #203) on this, and know that virtual-dom isn't looking to do complex client-side binding (that allows client-side rendering to kicks in when real dom already exists).
Does it mean currently the best approach for mixing server-side and client-side rendering, is to re-render the whole document again when client-side data is ready? I can't think of a better way, and would like to believe virtual-dom is fast enough when re-rendering full document.
How do you approach this problem? mercury encourages no manual dom manipulation, which I assume applies to virtual dom libraries in general.

In short, sorry for posting 2 long questions, but hopefully these 2 questions are common enough to worth answering :)

For Q2 see https://github.com/Matt-Esch/virtual-dom/issues/203
For Q1, I don't understand, why wouldn't the following suffice?
(in other words, why are you translating an html string and not the contents)
h('p.message', {
  h('a.link', {href: '/help'}, i18n.t('msg.error'))
})

@Zolmeister Thx for the reply, but I did read #203, see my OP, I am wondering the conclusion it reached: if we avoid patching real dom, then the only solution to me, is to replace it wholesale.
As for Q1, you are missing out the interpolation part, imagine a i18n mapping like
// in english i18n file
msg.welcome = 'Hi, %{user}, today is %{date}.'
...
// in chinese i18n file
msg.welcome = '你好，%{user}，今天是%{date}。'

To avoid interpolation you need to split welcome message into 5 strings, which doesn't make it easier to manage.

My understanding is that you generate the first diff via html-to-vdom and simply apply it to the DOM as normal.
As for the i18n interpolation, I guess I think interpolating over the html is a mistake (in general), and the answer really is to break it up into components

Yeah ideally we wouldn't need interpolation with html, but human languages are not designed with programmers in mind, eg. word order changes, divide english sentences into word phrases (or divide them based on dom nodes), you will soon find yourself unable to translate them into other languages properly.
I don't think there is a way to avoid html string being used in i18n interpolation, unless we explicitly structure sentences with templating language constraints in mind.
For other templating system, these are often done through specifying the input is html safe. For virtual-dom, innerHTML looks like the obvious approach, but sacrifices diff-ing flexibility in the process. To do it correctly, vnode -> string -> i18n -> vnode seems unavoidable.
Is it possible to extend virtual-dom hyperscript with node-polyglot translation feature, through a plugin of sorts? How do one get started on such a plugin?

For the client-side rendering problem, is html-to-vdom designed to be used to convert full document into vnode, and then diff-ing it through patches? cc @TimBeyer
I am not sure if it would be faster than just rendering the full document and replace it in one go? Can traversing real dom and patching them be slower? I see more researching are to come at #222

If you want different vnode structures for different phrases, you're going to have to build something on top of virtual-dom where you can define a vtree in some form that suits you, and create a lookup system for the structures, using i18n under the hood to do translations. If you are putting html in your translation strings you can probably parse the html and convert the structures to template functions using one of the html to vdom libraries out there.

I have been dealing with this problem lately, and while approach like using html-to-vdom to obtain a vdom from html do work, it does add quite a bit of dependencies to frontend.
200kb+ minified js to be exact, since it depends on htmlparser2, which is a very good parser but mostly designed for node.js environment.
So for simplicity sake I still prefer wiping out existing server-rendered dom, and using virtual-dom to re-render the whole page again (when js are loaded and data are available, otherwise it behaves like a traditional page-based website).
I believe React is the only implementation of virtual dom that actually attempts to bind client-side virtual dom into existing real dom? All other vdom solutions avoided this to keep implementation simple, and they indeed run much faster.

Why can't you use https://github.com/marcelklehr/vdom-virtualize ? It does not require a parser since it uses innerHTML to parse into DOM node first then translates that into VDOM.

Thx! I was pointed to https://github.com/tbranyen/diffhtml in another thread as well, use the same technique you mentioned.
But we do need to wipe existing server-rendered dom and replace it with a virtual-dom, right? I don't know how React did it without destroy existing dom, from many examples it appear to:

able to see the real dom from server is the same dom you will get by rendering client-side, thus doesn't re-render.
able to attach events automagically on real dom.
able to extract data from real dom to minimize ajax needed.

That's huge amount of automation (and probably a lot of code and tests).

If you create an initial vtree from your existing HTML, then the resulting diff of the new tree should not produce any DOM operations if it hasn't change since you rendered from the server. It will not replace everything.

Just trying to understand your problem...

Does it mean currently the best approach for mixing server-side and client-side rendering, is to re-render the whole document again when client-side data is ready? I can't think of a better way, and would like to believe virtual-dom is fast enough when re-rendering full document.

What is the problem in re-rendering client-side?

@alexmingoia I will dig into it further, what you describe sounds like what I expect from React.
@staltz I think the main problem I had was: now we have a complete document from server, we should try to reuse those dom/data for as much as possible, to avoid replacing it again client-side, which can be bad for battery, network, or experience (say user has scrolled, re-render the whole document might cause jump).

which can be bad for battery, network, or experience (say user has scrolled, re-render the whole document might cause jump).

Unless you have a truly huge page, like some monolithic news paper site, client-side rendering should be normally in the milliseconds (10ms -- 150ms). It is not nearly enough processing to affect battery. User's experience should be unaffected too, since 150ms is too fast to read+interact. Of those, maybe only redundant network calls could be the problem. In fact, if rendering depends on network calls, then that could truly make client-side rendering pass the milliseconds mark. But in that case you should do something smarter, having some kind of flag given to the app, where flag=true on the server-side would make initial network requests, but flag=false on the client-side would not make initial requests.

Zorium-seed does server-side network requests and pre-loads the data client-side: https://github.com/Zorium/zorium-seed

@bitinn yes, you can apply patches to any dom tree.  if that dom tree matches the rendering of oldTree then the patches will make sense. virtual-dom maintains no state related to the dom nodes used in the previous render.
i'm not familiar with vdom-virtualize but in your 4 steps i'm not seeing where you would apply event handlers.  does the first diff more or less just produce patches that only add event handlers?

@neonstalwart It's a good question, so without createElement step, we are still not getting the same result we should expect from a full client-side render. @alexmingoia have you had any experience about that?

To sum up our discussion so far, virtual-dom + vdom-virtualize (or other html to vdom solution) can do item 1 well, if anyone had any experience about item 2 or 3, I am all ears.
[x] - able to see the real dom from server is the same dom you will get by rendering client-side, thus doesn't re-render.
[ ] - able to attach events automagically on real dom.
[ ] - able to extract data from real dom to minimize ajax needed.

@bitinn for number 3 you have to manage it yourself by injecting it into the DOM (via script tag).
This is how Zorium does it:
https://github.com/Zorium/zorium-seed/blob/master/src/components/head/index.coffee#L119
https://github.com/Zorium/zorium-seed/blob/master/src/services/preload.coffee

@Zolmeister got it, so server render include inline data to be loaded by client, that's certainly a solution.

I tested vdom-virtualize a bit today with these 2 approaches:
this.vdomCache = virtualize(base);
this.nodeCache = base;

this.vdomCache = virtualize(base);
this.nodeCache = createElement(this.vdomCache);
var root = base.parentNode;
root.replaceChild(this.nodeCache, base);

Using a simple page with around 100 nodes:
On my macbook air, solution 1 takes ~15ms, solution 2 takes ~30ms.
On my iphone 6, solution 1 takes ~30ms, solution 2 takes ~45ms.
If replaceChild only add a linear penalty to render time, then replacing node might just be enough in most case.

As for events, does it mean dom-delegator is able to attach events based on diff / patch change? If we want solution 1 to work, we need to replicate create-element functionality to fire hooks?
To be honest I don't have enough knowledge about virtual-dom to reason it properly myself.

Also whichever solution I use, I am running into this bug while updating my simple page: #176

If it's a virtual-dom bug, it's a blocking bug that will prevent users from doing PE.

That is not a bug in virtual-dom. You're creating a vdom node somewhere with contentEditable="" or there's a bug in vdom-virtualize. You need to find where in your vtree you're creating a node with contentEditable and why it has an empty value.

@alexmingoia please see this reply in that thread:
https://github.com/Matt-Esch/virtual-dom/issues/176#issuecomment-74390185
I think that's how innerHTML work, unless it's not supported by virtual-dom?

@Zolmeister saw your comment edits in response to item 2 able to attach events automagically on real dom, you said this works on first vdom diff, right?
Looking at create-element source I can see it uses on apply-properties to fire hook/unhook. So who's in charge of attaching hooks (events) to real dom? If it's create-element, then I can't just create a vtree from existing dom, and expect subsequent diff/patch will auto-attach hooks right? If it's diff/patch, well, I am not sure why we need create-element to do additional work.
In short, this is key factor on whether we can just diff existing dom by getting a vtree representation of it and get event attached for free; or we should replace existing dom with result from create-element, in order to attached event properly.

@bitinn I don't think you understand how virtual-dom works

Build new v-tree (including hooks and events)
Diff v-tree from before (when constructed from DOM does not have hooks/events)
Apply patch, attaching hooks and events

@Zolmeister Great to hear, so it's the better case. But what's create-element doing here?
https://github.com/Matt-Esch/virtual-dom/blob/master/vdom/create-element.js#L34
https://github.com/Matt-Esch/virtual-dom/blob/master/vdom/apply-properties.js#L12

@bitinn The first time you're not diffing an existing tree, and must create the nodes

@Zolmeister
My understanding before starting this discussion is as you described:

if no dom tree exists, create a new vtree then use create-element render it in dom.
if dom tree exists, get a vtree from it, and diff/patch as required, no create-element needed.

But the discussion lead me to doubt myself :)
for example, I don't fully understand @neonstalwart's question earlier https://github.com/Matt-Esch/virtual-dom/issues/227#issuecomment-99187341, if diff/patch does the magic already, what else about events do I need to worry about?

I used dom-delegator with my fix branch for vdom-virtualize now it works and correctly patch a server-rendered dom with new vtree and events, all without using create-element.
I am closing this ticket as all 3 features from React can be implemented in some way. Thx all for replying.

A small update: after spending much time working on progressive enhancement with virtual-dom, I finally made this module: https://github.com/bitinn/vdom-parser, it serves a similar role like vdom-virtualize and html-to-vdom, but is much better tested.
We use it in production, you are welcomed to try it out.

authors: Matt-Esch Zolmeister alexmingoia bitinn neonstalwart staltz

repo: Matt-Esch/virtual-dom


text:
Fix getChatLength() calculation

In 'unsigned short getChatLength()', create char pointer before incrementing

Fixed in https://github.com/Matt-and-Gib/gleemail/commit/a26c9e36d5d548072448b12823f35de2ab3af1d0

repo: Matt-and-Gib/gleemail

license: Unlicense


text:
Expose expandAndSimplify

I see no good reason for Expression objects to not have an expandAndSimplify method (though you can totally just chain .expand and .simplify).

Decided against exposing it, and just made it so simplify expands first, which makes a lot more sense really.

repo: MatthewJA/Coffeequate


text:
Refactor building Stubby from source

Stubby can now be built standalone with libgetdns as a dependancy (as opposed to a submodule of getdns).

https://dnsprivacy.org/wiki/pages/viewpage.action?pageId=3145786#Installation:Linux(Buildfromsource)-Buildoptions
https://github.com/getdnsapi/stubby#build-stubby-from-source

It needs more testing and refinement, but a proof-of-concept version has been published to the stubby branch.

Re-worked how Stubby is built in https://github.com/MatthewVance/stubby-docker/commit/4a06090ac5500d755387722e470f40ad6a59d289. It's still a sub-module, but works with the latest stable getdns version (1.6.0) and also uses the CMake build system. At this time, the Stubby version is 0.3.0.

repo: MatthewVance/stubby-docker


text:
Use Double.greatestFiniteMagnitude by default

DBL_MAX is now deprecated

Can I get a status update on this?

repo: MatthewYork/DateTools


text:
Support for Slovenian eID

Description of the changes
Slovenian eID was added to OpenSC 0.24.0 which allows to extend the PKCS11Signer to enable simple path to sign PDF with signature key/certificate on the card.
Caveats
Official driver based on IDProtect is not supported (yet)

Hi @msetina,
Thank you for your contribution, but as-is I don't think I can merge this... The two main reasons are (a) I can't maintain nor test this since I don't have the relevant hardware, and (b) as pyHanko established itself in the Python space a bit, I've made a conscious effort not to add vendor-specific code.
To point (b): you could argue that the code specific to the Belgian eID violates that rule (and you'd be right). That's also why I moved it out of the tree with the 0.23.0 release (it now lives here: https://github.com/MatthiasValvekens/pyhanko-beid-plugin). The reason why it stuck around for so long is purely because of history/inertia: if you go back far enough in the commit history, you'll find that it got added some time in the first week or so (because pyHanko was a simple CLI tool at the time, and that was what I used it for). That code was later generalised to work with generic PKCS#11 implementations, but I didn't remove the BeID code at the time because it would've broken the CLI.
A few releases ago, I added plugin support to the CLI specifically to serve this use case: seamless integration of vendor-specific signing implementations in pyHanko's CLI. Part of the end goal was always to leverage that to "spin off" the BeID code into a plugin, but I didn't get around to it until today.
So, my proposal is that you either release your own plugin / companion lib with this code (feel free to use the pyhanko-beid-plugin repo as an example), or rework it as a contribution to the "advanced examples" section of the documentation. How's that sound?

Hi @MatthiasValvekens,
in the meantime I have found the solution you are describing. I had also done some work to be able to use the CLI as addition to this, so separate plugin is the way I will go. It is equivalent to the pyhanko-beid-plugin, so it has to live like that.
I find you project as an excelent example to show how singing is done. The code was a delight to folow and simple to extend as most of the work was already done.
I hope we can cross link our work to show the extent of your solution.
At this point I would like to ask you if you know the state of python-pksc11 project this depends on. Is it still alive? OpenSC has moved on, but it is lagging.

Hi @msetina, thank you for your understanding :)
python-pkcs11 has not seen much maintenance recently, that's for sure... I currently can't really afford to take on the burden of forking it since I don't have the resources (esp. time-wise) to test a Cython project the "proper" way (i.e. on multiple platforms, with multiple PKCS#11 implementations). But if there's an actively-maintained alternative that supports the same features with the same (or better) performance characteristics, I could be convinced to switch as well :).

authors: MatthiasValvekens msetina

repo: MatthiasValvekens/pyHanko


text:
PUSH_RECEIVER:::Error while starting the service TypeError: Object has been destroyed

Here is my setup.
"dependencies": {
"@capacitor/electron": "2.2.1",
"electron-push-receiver": "^2.1.3",
"electron-updater": "^4.3.1",
},
"devDependencies": {
"electron": "9.1.0",
"electron-builder": "22.7.0"
},
in the renderer process:
import {
    START_NOTIFICATION_SERVICE,
    NOTIFICATION_SERVICE_STARTED,
    NOTIFICATION_SERVICE_ERROR,
    NOTIFICATION_RECEIVED as ON_NOTIFICATION_RECEIVED,
    TOKEN_UPDATED,
} from 'electron-push-receiver/src/constants';

// Listen for service successfully started
ipcRenderer.on(NOTIFICATION_SERVICE_STARTED, (_, token) => // do something);
// Handle notification errors
ipcRenderer.on(NOTIFICATION_SERVICE_ERROR, (_, error) => // do something);
// Send FCM token to backend
ipcRenderer.on(TOKEN_UPDATED, (_, token) => // Send token);
// Display notification
ipcRenderer.on(ON_NOTIFICATION_RECEIVED, (_, notification) => // display notification);
// Start service
ipcRenderer.send(START_NOTIFICATION_SERVICE, senderId);

in the main process:
setupPushReceiver(mainWindow.webContents);

I received the following error when running the electron app, when it is setting up the push receiver :
PUSH_RECEIVER:::Error while starting the service TypeError: Object has been destroyed
at WebContents..send (electron/js2c/browser_init.js:173:2098)
at IpcMainImpl. (/Users/pianokai/Sites/restvo/front/electron/node_modules/electron-push-receiver/src/index.js:55:19)
(node:81584) UnhandledPromiseRejectionWarning: TypeError: Object has been destroyed
at WebContents..send (electron/js2c/browser_init.js:173:2098)
at IpcMainImpl. (/Users/pianokai/Sites/restvo/front/electron/node_modules/electron-push-receiver/src/index.js:59:19)
upon further investigation, it seems like it crashed in src/index.js line 52 - 55
      // Listen for GCM/FCM notifications
      await listen(Object.assign({}, credentials, { persistentIds }), onNotification(webContents));
      // Notify the renderer process that we are listening for notifications
      webContents.send(NOTIFICATION_SERVICE_STARTED, credentials.fcm.token);

#11

repo: MatthieuLemoine/electron-push-receiver


text:
adding version support and top banner

@jdorfman per our discussion

:+1:

authors: jdorfman jmervine

repo: MaxCDN/shml


text:
Adding first e2e test

And a bonus health endpoint to make the simplest test possible.
Working towards #43

Thanks @jazcarate! This is great

authors: MaxLeiter jazcarate

repo: MaxLeiter/Drift


text:
initial version of Realtime DataSource

Hi,
this is an initial draft to integrate realtime datasource and some test code. It is based on the CSVDataSource and tries to stick to IATK's design prenciple. Please have a look. I am currently cleaning and refactoring some higher layer glue code. Which will follow soon.
let me know,
best philipp

Hi Philipp -
This is looking good. A few thoughts for the cleanup:

IATKRuntime would be better named ReatimeDataDemo or similar.
RealTimeDataSource can go in the Scripts/Model folder and namespace set to IATK.

I don't think you need to do this for this feature, but in the future I think it would be good for the DataSource to have a simple event emitter so that every time the datasource is updated, associated visualisations can automatically update.

Hi,
thanks for the input. I am still new to the internal mechanics of IATK. I will try follow the suggested naming schemes. Since i am still working out some parts of the glue code to a higher layer, the IATKRuntime is still subject to change (eg when using it from a javascrict-layer, which i am currently, not all bindings like overloading and reflexion can resolve at runtime).
A reason not having the automatic update in place, is due to realtime data, where one might want to update the view on a different pace as the data comes in.
Since this is not the end, there is more to come (hopefully this week).
Anyway, thanks for the reply and i will post updates here.
best,
Philipp

Hi,
I just added a reference to PowerUI (only within a README) since i dont know how you want that to be referenced. Additionally,i added sample code and an interface to IATK from js. The js part is executed at runtime without prior knowledge. Maybe it is of interest to keep a brunch with external refs?
However, i have it within a bigger project running with more details and some more code around, which might also be interesting.
Let me know.
best philipp

@philfleck I've made some recommended changes and submitted a PR to the philfleck:icg_fleck_realtime_datasource branch. Maybe consider making some of the changes so that they can be applied to this PR, let me know if you have any questions 🙂

Hi @philfleck, thank you for accepting my changes 🙂. I've noticed this PR now includes some code for the Replicator feature you are working on.
I'd recommend removing the Replicator code from this PR and keeping it just for "Replicator for iatk visualizations" PR. We can then keep the features separate and they can then be reviewed separately as well 🙂.
Only a recommendation so up to you, depends on how you want to approach it. Maybe another option would be to combine the two PRs into one maybe?
Thank you again for accepting my changes, really appreciate it!

Hi @danieljharris,
I know, that was my bad, but nothing too big. I am still testing, hopefully i am doe today. I might add some points back which do not work out. There some issue with function overloading, because i am interfacing IATK directly from bindings to JS and not all function overloads are distinguishable and therefore might not be found at runtime. Anyway, this was good progress and i am going to sort out the replicator stuff from this PR, to have it by its own.
best,
Philipp

Hi @philfleck, yeah that sounds good. I wasn't considering how the function overloading would work with JS so apologies if that didn't work out.
Feel free to add anything back that I changed, my alterations were only suggestions 🙂.

Closed in favor  https://github.com/MaximeCordeil/IATK/pull/22.
See #22.

authors: atzanteotl danieljharris philfleck

repo: MaximeCordeil/IATK


text:
Refactor codebase to be consistent with guideline #5

Guideline #5 states: Rule/subroutine names should follow the format: rule "[file_name.opy]: My custom rule": and @Name "[file_name.opy]: mySubroutineFunc()".
Constants in ow1/2_constants.opy should also be ALL_CAPS
Some of the code written in the early phase of the project do not strictly follow this guideline, so this refactor attempts to make the condebase consistent with all current styling guidelines.

I'm currently in the process of adding names to all the initHero() subroutines


text:
How to make this amazing project a semantic segmentation model?

If I want to segment yellow lane, white lane, zebra. How could I modify this model? Does anyone have any ideas? Thank you.

@meanmee 不明白你的意思

这个模型是做实例分割的，一条线当做一个类别。现在我想要改成做予语义分割的，类别是确定的，比如黄实线，白实线，斑马线分别为不同类。

@meanmee 那你只要binary segmentation就好了 然后自己改类别从二分类到多分类:)

是这样的，之前我在自己数据集上是直接训练的多分类分割模型，但是由于黄实线和白实线数据量差距太大，黄实线很容易被当成白实线，尝试过加权，但效果不理想。
然后用你的模型测了一下，发现可以很好地区分黄实线，白实线。所以在想能不能在你模型的基础上改动（我觉得聚类部分是关键）

@meanmee 那你可以尝试下:)

请问你有做出来吗？我现在也做了自己的数据集，在检测的基础上需要区分虚线和实现，请问要怎么修改呢？ @meanmee

authors: MaybeShewill-CV gabaebae123 meanmee

repo: MaybeShewill-CV/lanenet-lane-detection


text:
add Solarized color scheme

http://ethanschoonover.com/solarized

Solarized Light
$ wget -O xt  http://git.io/vvjFb && chmod +x xt && ./xt && rm xt

Solarized Dark
$ wget -O xt  http://git.io/vvjFH && chmod +x xt && ./xt && rm xt

repo: Mayccoll/Elementary-OS-Terminal-Colors


text:
Copy xfce4 terminalrc if it's available

In Linux Mint Xfce doesn't have terminalrc at HOME.
Try to copy default terminalrc before exit an error.

Thank you

authors: Mayccoll grooveshaker

repo: Mayccoll/Gogh


text:
logging something  with '{string}' and add  args or kwargs BUGs (hashtag678)

from loguru import logger
logger.error("{ssss}", 'sss')

hashtaghashtaghashtag KeyError
Traceback (most recent call last):
  File "/Users/sato/Desktop/rct/scrcpy_ai/buff_detection_srv/logger.py", line 6, in <module>
    logger.error("{ssss}", 'sss')
  File "/Users/sato/.virtualenvs/scrcpy_ai/lib/python3.7/site-packages/loguru/_logger.py", line 1989, in error
    __self._log("ERROR", None, False, __self._options, __message, args, kwargs)
  File "/Users/sato/.virtualenvs/scrcpy_ai/lib/python3.7/site-packages/loguru/_logger.py", line 1954, in _log
    log_record["message"] = message.format(*args, **kwargs)
KeyError: 'ssss'

hashtaghashtag reason
hashtag file _logger.py

line1952    elif args or kwargs:
line1953        colored_message = None
line1954        log_record["message"] = message.format(*args, **kwargs) hashtag this line will cause KeyError!!!!!!!!!!!

Hi
I don't think this qualifies as a bug... :open_mouth:
The logging methods (like logger.error()in your example) are designed and documented to act as much as possible like the built-in [str.format()]( method. It automatically formats a message based on optional *args and **kwargs arguments, which is more convenient that calling message.format() manually when logging a message.
logging.warning("%s before you %s", "Look", "leap!")         hashtag Built-in logging use old % formatting.
logging.warning("{} before you {}".format("Look", "leap!"))  hashtag Modern formatting using {} is verbose.
logger.warning("{} before you {}", "Look", "leap!"))         hashtag Loguru tries to make it more convenient.

In your example, beacause you provide "sss" as an argument to the logging method, Loguru thinks you want to format the message and thus call "{ssss}".format("sss"). This raises an error because Python expects a ssss keyword argument to format the string, but find none (hence the KeyError). For example, logger.error("{ssss}", ssss="sss") would be valid and generate "sss" message. If you don't need formatting, don't pass the "sss" as an argument when logging your message, and Loguru won't try to format it. Otherwise, you can also disable formatting with logger.error("{{ssss}}", "sss") and the argument will just be ignored.
Using str.format() internally makes less sense now that f-string became popular, so I plan to modify the current behavior in the future, but I would say it's working as expected for now.

Thank you for your reply！！ 😊
I add a callback function like ：

from loguru import logger as ruloger

hashtag add callback
def fn_callback(record):
    if record['extra'].get('flag'):
        do_something()

logger = ruloger.patch(fn_callback)

hashtag in use
 = {"code": 0, "msg": "", "data": None}
logger.error( flag=True) hashtag I just want to log a dict and add a `flag` 😁

In this case I better understand the issue you're facing.
This is a problem that has been reported multiple times, and that's indeed why I plan to (optionally) remove the automatic formatting in a future version. In the meantime, you should use [bind()]( when passing data which isn't intended to be formatted:
logger.bind(flag=True).error(

many thx, it`s working!


text:
Error adding to Webjars using bower

http://www.webjars.org/bower -> add a new bower webjar
Failed!
No valid licenses found. Detected licenses: Apache
The acceptable licenses on BinTray are at: https://bintray.com/docs/api/#_footnote_1
License detection first uses the package metadata (e.g. package.json or bower.json) and falls back to looking for a LICENSE, LICENSE.txt, or LICENSE.md file in the master branch of the GitHub repo.
Since these methods failed to detect a valid license you will need to work with the upstream project to add discoverable license metadata to a release or to the GitHub repo.
If you feel you have reached this failure in error, please file an issue: https://github.com/webjars/webjars/issues
Created Bower WebJar
Fetched Bower zip
Generated POM
Converted dependencies to Maven
Got Bower info
Determined Artifact Name: Leaflet.VisualClick
Starting Deploy

Closed by #7.
@gavioto In the future, please explain yourself better in bug reports - a copy-paste of an error message is not a bug report. I suggest you read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

authors: IvanSanchez gavioto


text:
Shields working with Chiseled items?

Is there a possibility of having shields working with chiseled blocks? I tried chiseled stone and it would not work, but it works fine with standard stone.
Thanks for your hard work McJty!

I should be able to fix this in RFTools just like I did in XNet.

Will be fixed in the next release of RFTools.

repo: McJty/McJtyLib


text:
[1.10][4.30b44]Dimlets.json appears to revert itself on server restart

The Dimlets.json appears to regenerate default every time the server instance is restarted, any changes introduced are wiped.

You have to put your own configs before the line:
Everything below this line will be regenerated from defaults every time. Remove this line if you do not want that

Hello and apologies for necrothreading. I am encountering this same issue, both on the server, and on my local instance. I have tried both adding my changes before the line, and removing that line and adding my changes in its place. In both cases, the file reverts back to its default settings.
RFTools: 1.1x-5.84
RFTools Dimensions: 1.1x-4.54

authors: McJty Rosethorns rishenko

repo: McJty/RFToolsDimensions


text:
Change block-ui default location

I tried to set in na specific div but it keeps showing in full screen. How can I use block-ui for all request (as default) but show only in

?

Hi,
You can relocate the main blockUI instance by setting autoInjectBodyBlock to false in the configuration and marking your custom element with block-ui="main".
See this plunker for more info.

authors: McNull erickne

repo: McNull/angular-block-ui


text:
MAT-5828_timeField

MADiE PR
Jira Ticket: MAT-5828
(Optional) Related Tickets:
Summary
All Submissions

[x] This PR has the JIRA linked.
[x] Required tests are included.
[x] No extemporaneous files are included (i.e Complied files or testing results).
[x] This PR is merging into the correct branch.
[ ] All Documentation needed for this PR is Complete (or noted in a TODO or other Ticket).
[ ] Any breaking changes or failing automations are noted by placing a comment on this PR.

DevSecOps
If there is a question if this PR has a security or infrastructure impact, please contact the Security or DevOps engineer assigned to this project to discuss it further.

[x] This PR has NO significant security impact (i.e Changing auth methods, Adding a new user type, Adding a required but vulnerable package).
[ ] All CDN/Web dependencies are hosted internally (i.e MADiE-Root Repo).

Reviewers
By Approving this PR you are attesting to the following:

Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose.
The tests appropriately test the new code, including edge cases.
If you have any concerns they are brought up either to the developer assigned, security engineer, or leads.

replaced by this new PR: https://github.com/MeasureAuthoringTool/madie-design-system/pull/182


text:
Qt GUI: About dialog fixes

simplified layout without visual changes
better resize behavior - keep "about text" aligned to top
use SVG icon for "info" icon (HighDPI support)
"OK" button is default button
get app version "in place" instead of passing it
use format string for "about text" instead of "keyword + replace"

Thanks.

authors: JeromeMartinez Kolcha

repo: MediaArea/MediaInfo


text:
Fixed Websocket problem with latest Firefox versions

The latest Firefox versions (>=37) are using permessage compression.
The current implementation of permessage compression in websocket-sharp
is incorrect because it creates a new DeflateStream object for every
message, but this is only allowed, if client_no_context_takeover or
server_no_context_takeover has been agreed during the handshake.
Otherwise the DeflateStream object would need to be persisted and reused
for each connection, in order to implement the LZ77 sliding window.
I tried to copy over some stuff from websocket-sharp, to include
client_no_context_takeover and server_no_context_takeover, but that does
not have any effect on the Firefox behaviour. According to the spec, the
server may just acknowledge the extensions requested by the client, but
may not add options (like client_no_context_takeover). As a consequence,
this didn't solve the problem.
The final solution would of course be to change the code to reuse the
DeflateStream objects, but it hasn't even been done in webbsocket-sharp.
Instead websocket-sharp has introduced an IgnoreExtensions property
which effectively disables lines 163-165 in WebSocket.cs. I have
commented these out in our code as a quick fix. As a result permessage
compression is simply disabled.
This change finally made Emby-Websockets on Firefox clients work again!

Excellent, thanks! Really glad to see this one fixed.

Some further reading:
https://bugzilla.mozilla.org/show_bug.cgi?id=1176176
https://www.igvita.com/2013/11/27/configuring-and-optimizing-websocket-compression/
https://github.com/sta/websocket-sharp/issues/132
https://github.com/sta/websocket-sharp/issues/140

Wow, that was a quick merge :-)
PS: Closes #1194

Actually this also closed MediaBrowser/Emby/#1193

authors: LukePulverenti softworkz

repo: MediaBrowser/SocketHttpListener


text:
Mega read this

umg fix the pslit ahhhhhhh umg ahhhhhhhhhhhhhhh

@AlexandriteErikParacelsus https://streamable.com/gfjus

@AlexandriteErikParacelsus and please stop making pointless issues