Undefined class constant 'CATEGORY_NOTIFICATIONS'

I just saw this plugin in my backend as "recommendation" so i clicked on it and voila: my backend does not work anymore and throws this error:
Undefined class constant 'CATEGORY_NOTIFICATIONS'
public function registerSettings()
{
    return [
        'notifications' => [
            'label'       => 'rainlab.notify::lang.notifications.menu_label',
            'description' => 'rainlab.notify::lang.notifications.menu_description',
            'category'    => SettingsManager::CATEGORY_NOTIFICATIONS,
            'icon'        => 'icon-bullhorn',
            'url'         => Backend::url('rainlab/notify/notifications'),
            'permissions' => ['rainlab.notify.manage_notifications'],
            'order'       => 600
        ],
    ];

This plugin is only compatible with Build 420+

I experienced exactly the same. Understand that it is only compatible with Build 420+ but how do I recover from this? Don't want to reinstall OctoberCMS again preferably.

@stelgenhof do you mean make your October instance work again without this plugin or do you mean make it work with this plugin?

@LukeTowers Well, this error appears all the time in the backend so the backend is unusable. In the end I removed the notify plugin files from the plugin folder. That way the backend worked again.
It may be better if plugins that are in beta or for a specific build be marked as such in the UI for example. Just to avoid people experiencing similar issues in the future :)


Name of the project and Contributing.md

Good name for the project.
Contributing.md is just a placeholder. We can modify according to our needs.

Name discussed as Donatify.


unable to use pandas or numpy as it says...

I can run generate data folder and go &&python files.
(1) using extract from mylib\data\ failed
fils,e:=embed_util.NewEmbeddedFiles(data.Data,"example2")
ep.AddPythonPath(fils.GetExtractedPath())
It throws e not xx file found
(2)
directly use the lib like this
ep.AddPythonPath("C:\Users\Adminis\xx\mylib\data\windows-amd64")
it says like this
ImportError: Unable to import required dependencies:
numpy:
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.
We have compiled some common reasons and troubleshooting tips at:
https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

The Python version is: Python3.10 from "C:\Users\Administrator\AppData\Local\Temp\go-embedded-python-example-5f873ba0fa0239f0\python.exe"
The NumPy version is: "1.24.0"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.
Original error was: No module named 'numpy.core._multiarray_umath'

This issue should be fixed now, as discussed in https://github.com/kluctl/go-embed-python/issues/20


Missing getInstallations method in latest version of octokit

I'm trying to add probot-stale as a composed app, but it's failng to load because getInstallations is not a function. It seems it was renamed to listInstallations according to this PR: https://github.com/angular/github-robot/commit/19f42906cb944f6b71730853e1efd9e77c25457d#diff-dc25f195229dc07dc2800f765f2fb98fL27

Here is the exact error on startup:
15:37:31.994Z ERROR probot: github.apps.getInstallations is not a function
  TypeError: github.apps.getInstallations is not a function
      at eachInstallation (/bot/node_modules/probot-scheduler/index.js:74:29)

Is this still relevant?
Yes
If so, what is blocking it?
The Author of you.
Is there anything you can do to help move it forward?
No, the latest version of github needs to be pushed to NPM! It's not a hard fix

@JasonEtco ^

yes

yes

I am facing the same issue , do you have any update ?

I only have this problem when working with stale and pr-triage
❯ 06:36:04.951Z ERROR probot: github.apps.getInstallations is not a function                                                                     ─╯
  TypeError: github.apps.getInstallations is not a function
      at eachInstallation (/app/node_modules/stale/node_modules/probot-scheduler/index.js:74:29)

please fix this

Works when downgrading probot to match: https://github.com/probot/stale/blob/master/package.json#L21


MQTT Broker Host suggests http:// but only accepts tcp://

By creating or editing the Broker Host, you have to type tcp://.....
Shoudn't it be http:// ?

@rollercontainer  As far as i know, MQTT protocol supports only tcp:// and ws://. So we cannot use http://. Please correct me if I am wrong.

How about an IP input field without protocol info if it is fix?

@rollercontainer  You should give IP or hostname with protocol and port information information, as MQTT supports for tcp and ws. Most of us using tcp://

Ok, close it. :-)


propagate additional tags from awsCluster to ebs-csi-driver

What this PR does / why we need it
At the moment tagging is not followed for resources created by ebs-csi-driver. This PR add propagation of necessary tags to respective resources.
Towards https://github.com/giantswarm/giantswarm/issues/29583
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites


Push Datasets not working in PowerShell 7 without useragent declared

Hi,
We have discovered push datasets are not working in PowerShell 7.3 (local install), 7.2 via azure automate, 7.1 via azure automation and 5.1 via azure automation without useragent declared. it does work with 5.1 locally.
This is the case when using the below commands
$a = Invoke-RestMethod -Method Post -Uri "$endpoint" -Body (ConvertTo-Json @($output))
$a = Invoke-WebRequest -Method post -Uri "$endpoint" -Body (ConvertTo-Json @($output))
The return value is a 200 however the datasets do not update.
To workaround this we discovered that declaring the useragent (any useragent works) via the example below resolves this issue and teh dataset updates correctly in all the above versions
$userAgent = [Microsoft.PowerShell.Commands.PSUserAgent]::Chrome
$a = Invoke-WebRequest -Method post -Uri "$endpoint" -Body (ConvertTo-Json @($output)) -useragent $useragent.
It appears the default useragent is causing some kind of issues in the mentioned versions

Thanks for your comment, @gtowsey. This issue has been assigned to the doc author for review.

Thank you for this information @gtowsey. I'll pass it on to the relevant engineers.


[WIP]Add a training & support page

Closes #1599.
Todo:

[ ] Finalize criteria (if any) around PR-ing to this page and let @celestehorgan know.

@juliusv, @cra

I like this overall!
Probably we should then remove the list in the Commercial Support section on the Community page, and instead link to this new page from there.

I see the marketing blurbs were now removed in the last commit. @brian-brazil is this good to merge now?

It still contains a blurb for RP, a course name for LF, and is still adding new hard requirement for listing that even several existing listings do not meet/

Ok, I would personally prefer to not be that pedantic about it, but in the interest of getting this merged without veto, @celestehorgan let's maybe minimalize it even further and just have company names + links for the courses, and remove the all requirements for now? I would still like to have something like that again later, but maybe then we can discuss that separately.

@juliusv That sounds like a good plan. I'll submit a new commit in an hour or so.

@celestehorgan Any updates on the last commit to remove the blurbs + requirements? Otherwise I'm also happy to make those last changes myself if you're ok with it.

@juliusv :( apologies for the delay, see the latest commit.

@celestehorgan Thanks! Ah, now the latest commit also removed the whole "Add a resource" section that is linked to at the top. I think that section is definitely good to keep starting from "To submit, open a pull request against...", only the new requirements were disputed.

Updated!

Thanks! I think this looks good now. @brian-brazil all ok?

Just in the interest of getting things done[tm], I'll merge this for now and send an immediate follow-up to remove the still-controversial items.


Implementation of Giscus for the blog

Hello, everyone!
I would like to know how to implement giscus on the blog to make it more interactive!
I saw it on @mcruzdev 's blog and I think it would be nice to keep the comments for greater interaction with the public!
Link giscus: https://giscus.app/
Link Matheus's blog: https://matheuscruz.dev/2024/02/14/how-quarkus-prepare-reflective-code-to-graalvm/

Yes, I think it would be very interesting to add the giscus!

I submitted this: https://github.com/quarkiverse/quarkiverse-devops/pull/303

Discussions now available:https://github.com/quarkiverse/quarkus-roq/discussions

This is done


fix(bridge): Exclude webhook-service results from sequence result (#5954)

Fixes #5954
By excluding the source webhook-service from isFaulty, isSuccess, is Warning, traces should now show the proper state.
Signed-off-by: Elisabeth Lang<EMAIL_ADDRESS>

Does this also remove webhook-service .started and .finished events in case of listening to .triggered events?

@christian-kreuzberger-dtx as it filters for the source, the event type should not matter.

@christian-kreuzberger-dtx When subscribing to started / finished events the webhook shouldn't send an event at all. For triggered the behavior is as expected and it is allowed to fail the sequence.
As why the events are still sent, someone from core team is taking a look at it.


Drop the dependency of fbjs

From https://github.com/tomchentw/react-google-maps/commit/91d57909bf1de15f8f41e89d71a21da823cca0ab#commitcomment-13781930

@tomchentw fbjs is discouraged from being used outside of Facebook.

Seems can't do it right now. animationMixin depends on it.


iOS: footnote markers in main text have wrong z-index once tapped

See attached screenshot of this post displayed in NNW 6.1.4 (Build 6120) on iOS 16.6.1

Steps to reproduce:

View the article
Tap footnote marker "2" to show the footnote in a pop-up.
Tap elsewhere to dismiss the pop-up.
Tap footnote marker "1".

Expected result:
The pop-up for footnote 1 is displayed above the footnote marker "2".
Actual result:
See screenshot.
(Note that step 2. is essential. If you skip it, you get the expected result.)
Let me know if you have any questions; I'm happy to help!

Replicable on macOS as well.


ci/cd - add temporary test environments

see https://github.com/ntno/mkdocs-demo for example
new s3 bucket for each PR, deploy doc site to temporary website, teardown bucket when PR is closed

related feature:
long-lived example environments implemented for the following examples using GitHub Actions and GitHub Pages:

example name
source
site URL
pages repo

hilightjs
./tests/examples/highlightjs
https://ntno.github.io/mkdocs-terminal-example-highlightjs
ntno/mkdocs-terminal-example-highlightjs

hilightjs-dark
./tests/examples/highlightjs-dark
https://ntno.github.io/mkdocs-terminal-example-highlightjs-dark
ntno/mkdocs-terminal-example-highlightjs-dark

see PRs:

#172
#173

wip PRs:

#167
#166
#165
#164


[DF] Add support for filtered groupby aggregations

Adds back support for filtered aggregations with FILTER (WHERE ...), which allows us to unxfail test_group_by_filtered and unblocks several related tests in #746 and #759.

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@528108c). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #760   +/-   ##
=========================================================
  Coverage                          ?   75.55%
=========================================================
  Files                             ?       73
  Lines                             ?     3682
  Branches                          ?      767
=========================================================
  Hits                              ?     2782
  Misses                            ?      766
  Partials                          ?      134

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[v4-beta.12] Chrome & Firefox have different styles

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)          : 4.1.2 (/usr/local/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.12
   @angular-devkit/core       : 0.7.5
   @angular-devkit/schematics : 0.7.5
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : 1.0.8
   @ionic/schematics-angular  : 1.0.6

System:

   NodeJS : v10.11.0 (/Users/chicho/.nvm/versions/node/v10.11.0/bin/node)
   npm    : 6.4.1
   OS     : macOS High Sierra

Describe the Bug
Android and Firefox have different styles. Both browsers seem to be loaded in md mode based on styles and node html[mode="md"]. The problem is that Firefox adds classes like if it was on Android.
For example, check the 2 images for the ion-tabbar which have different classes on each browser.
This happens with almost all ion-components, like ion-avatar, ion-content, etc.
Chrome

Firefox

Steps to Reproduce

Create a new project like ionic start myApp tabs --type=angular
Open dev tools and inspect the elements

Related Code
No code changes needed.
Expected Behavior
I assume the default platform is android, so android classes should be loaded in chrome too.
Both browsers should show the same.
Additional Context
In Safari, it behaves exact as Chrome, loading md styles.

Firefox does not support shadow-dom, meaning the shadow-dom polyfill kick in adding that classes.

Thanks for the quick response.


Add a test page with a peer connection from realistic video.

Description
Add a test page with a stream from a realistic video to a peer connection.
Purpose
Currently, telemetry tests for WebRTC use an auto generated video that is not realistic and is very simple to encode and decode. This might be a way for using realistic video for telemetry tests.

PTAL

Thanks :)
Do you have to publish it, or something?

Yes it's currently served on AppEngine (want to move these to a separate repo soonish.)


[SMALLFIX]Java 8 Improvement: replace anonymous type with lambda in a…

…lluxio.security.group.CachedGroupMapping

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/966/
Test FAILed.

请再试一次吧，谢谢

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/969/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/975/
Test FAILed.


"Mixin apply for mod citresewn-defaults failed"

Greetings.
I know that CIT-Resewn is not yet released for 1.20.4.  I'm eagerly awaiting the day that it is.
In the meantime, I was updating everything today and figured I'd give it a try, and at the very least give you a crash log to maybe help you guys figure out what to point your mixing spoons at, and also provide something the other tickets failed to do.  Logs!
Environment:

Operating System: Windows 10 (Latest updates as of February 15)
Minecraft 1.20.4
Fabric Loader 0.15.7
Allocated RAM: 16 Gb

Mods List:

ClothConfigAPI 13.0.121
FabricAPI 0.96.4
BetterEndSky 0.2.1
CameraUils 1.0.9-Beta
CITResewn 1.1.3
CITResewn-JSON Lag Patch <IP_ADDRESS>
GammaUtils 1.7.19
IKnowWhatImDoing 4.1.1
LambDynamicLights 2.3.4
MaLiLib 0.18.1
Litematica 0.17.2-BETA
MiniHUD 0.30.2
ModMenu 9.0.0
RainGlow 1.2.0
Spark 1.10.60
StatusEffectBars 1.0.4
Stenhal 1.4.1
WorldEdit 7.3.0
WorldEdit-CUI 01

Logs:
latest.log

Thank you for the details, closing to not have duplicate issues.


vscode-extensions.gruntfuggly.todo-tree: 0.0.198 -> 0.0.201

Motivation for this change
Things done

[ ] 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"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 115438 at c666f8df run on x86_64-linux 1

1 package built:

vscode-extensions.gruntfuggly.todo-tree

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/misc/vscode-extensions/default.nix:371:9:
    |
371 |         meta = with lib; {
    |         ^


Dateparser parses years as a date when STRICT_PARSING = True

Dateparser with STRICT_PARSING parses a year wrongly:
>>> dateparser.parse('2017', settings={'STRICT_PARSING': True})
datetime.datetime(2020, 1, 7, 0, 0)

I would have expected it to return None instead. Did I understand the docs wrongly?
For reference, the parsing seems ok without STRICT_PARSING:
>>> dateparser.parse('2017')
datetime.datetime(2017, 10, 30, 0, 0)

Setup:

Python 3.5.2
dateparser==0.6.0

I investigated a bit this issue and I'm sharing what I've found so far.
Following there are two approaches to this problem:

Parsing a date with or without STRICT_PARSING parameter should use the same parser, and return the same result in order to keep consistency. After parsing the date/time string, we check for STRICT_PARSING parameter and return None if it's incomplete.

Currently, if the date is incomplete and STRICT_PARSING is set, it keeps trying to parse the data using other formats, so we end up with different results depending on if you are using STRICT_PARSING or not.

Other approach would be to not parse complete dates from 4 digits data. Parsing 4 digits as complete dates is generating quite weird results, for example:

dateparser.parse('2001', settings={'STRICT_PARSING': True})
datetime.datetime(2000, 2, 1, 0, 0)
MYD
dateparser.parse('2019', settings={'STRICT_PARSING': True})
datetime.datetime(2020, 1, 9, 0, 0)
YMD
dateparser.parse('1983', settings={'STRICT_PARSING': True})
datetime.datetime(1983, 1, 9, 0, 0)
MDY

Hey @asadurski , Could you give your opinion, if it's the right way to go?

I'm having the exact same issue. Ideally, I would expect None to be returned when executing something like this:
dateparser.parse('2011', settings={'STRICT_PARSING': True})
Are there any updates on this?

From my perspective, the dateparser.parse() method should do the best to return dates.
I know that 2017 doesn't seem a full date, but it theoretically fits for 2020-01-07.
I added a new PR separating the no-spaces-time parser from the absolute-time parser: https://github.com/scrapinghub/dateparser/pull/786
It would allow doing:
from dateparser_data.settings import default_parsers

parsers = [parser for parser in default_parsers if parser != 'no-spaces-time']

dateparser.parse('2017', settings={'STRICT_PARSING': True, 'PARSERS': parsers})

(and it wouldn't return anything).
I know this doesn't fix the issue 100%, as you have to add specific settings, but in my opinion, we shouldn't change the default behavior, so we could consider this fixed when releasing that PR. Any strong opinion on this?

Hi guys, we finally decided to exclude the no-spaces-time parser from the default parsers (PR: https://github.com/scrapinghub/dateparser/pull/786), so it will work as expected in the next version!


Not working with angular 11

Hi,
What are the plans to make agm work with angular 11 ?
It block me to upgrade un entire application
Thanks

It is working with Angular 11, use the --force parameter when updating with ng update. Check to make sure that your other dependencies work too.

Hello,
i think that this package is no longer maintained (no updates, no answer to our questions or requests,...)
If i was you, i would use the native Angular Google Map component...

Thanks a lot Pierre, I didn’t know about it.
It’s just what I need.
De : Pierre Steinier<EMAIL_ADDRESS>Envoyé : mardi 17 novembre 2020 21:58
À : SebastianM/angular-google-maps<EMAIL_ADDRESS>Cc : Marcos Tabaj<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [SebastianM/angular-google-maps] Not working with angular 11 (#1913)
Hello,
i think that this package is no longer maintained (no updates, no answer to our questions or requests,...)
If i was you, i would use the native Angular Google Map component...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SebastianM/angular-google-maps/issues/1913#issuecomment-729209426 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHTOEMIOIJYIQA2HNJGA6TSQLPUZANCNFSM4TU7Q4FQ .  https://github.com/notifications/beacon/AAHTOELQCEWYD5WYDUSPROLSQLPUZA5CNFSM4TU7Q4F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFN3NUUQ.gif

Working fine for me. Except compiler warnings:
<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^10.0.0 but none is installed. You must install peer dependencies yourself.

Hello
Do you have more info how to get it running? when I run npm install with Angular 11 I get the following error
Could not resolve dependency: npm ERR! peer<EMAIL_ADDRESS>|| ^10.0.0" from<EMAIL_ADDRESS>

Hello
Do you have more info how to get it running? when I run npm install with Angular 11 I get the following error
Could not resolve dependency: npm ERR! peer<EMAIL_ADDRESS>|| ^10.0.0" from<EMAIL_ADDRESS>

For those who run into this issue, I solved it by using a hack from here:
https://stackoverflow.com/a/62988875/10400584

For those who run into this issue, I solved it by using a hack from here:
https://stackoverflow.com/a/62988875/10400584


Website scaling for small screens

The title bar is a bit long, so for small-to-medium screens it takes up to 3 lines. Note that the layout is correctly changed for very small screens (e.g. phones).

Also, the side panel cannot be scrolled, so if the screen is too small we cannot see part of the side panel.

on safari when I scroll down on the front page I get this now

it works on chrome though


docs(Correct docsUrl)

Description
In the Documentation, the DocsUrl is not correctly set. This makes the Edit on github  not show the Correct Location. This Pr will fix this.
Issues

Change the URL to the main repo not a fork

Thanks for this PR :)


Inconsistency with set of days given by name

0 */2 * * Mon,Tue,Wed,Thu,Fri,Sun echo "hello"
The command echo "hello" will execute the 0th minute of every 2nd hour Sundays and Sundays and Sundays and Sundays and Sundays and Sundays in every month.

Yikes. Definitely not right. Thanks for reporting!

You're welcome.  Good luck with the fixes.
Best,
Mathieu
On Monday, April 20, 2015, Patrick Byrne<EMAIL_ADDRESS>wrote:

Yikes. Definitely not right. Thanks for reporting!
--
Reply to this email directly or view it on GitHub
https://github.com/pbyrne/cron-checker/issues/27#issuecomment-94538071.


Allow using this.state within cb in this.setState(updater, cb)

Fixes #1604.
It should be allowed to use this.state within cb in this.setState(updater, cb).

Wops, seems like I was late to the party. Consider #1610 instead of this one.

Thanks! Indeed tho, closing as a duplicate of #1610 :-)


How to bind more buffers to tabpage?

With :TablineBuffersBind, I could bind the current tab's buffers to some files.
After a while, I want to bind more  buffer so I try the same command and found the previous buffers were unbound.
How can I bind more file to only this tab without losing previous buffers?

I think having a :TablineBuffersAddToBind might make a lot of sense as well!


Add tests for validation rules

Need to add some tests which cover the validation rules class.

Relates to #73


SAMZA-2632: Processors should only write their own task locality to zookeeper

Problem:
Processors update the task locality for all the tasks in the job model with their own locality regardless of whether the tasks belong to their container model or not.
Description:
As part of SEP 11, host affinity for standalone was introduced. For this feature, we persist the task locality in zookeeper so that subsequent rebalances take this locality into account when generating job model. During job model consensus, we update the task locality for all the tasks and this results in incorrect locality depending on the order of writes.
Changes:
Only update the locality for the tasks that belong to the processor.
Tests: Added unit tests
API Changes: None
Upgrade Instructions: None
Usage Instructions: None

@santhoshvenkat1988 Can you take a look at this PR?


Specify module for Webpack 4

Hi, thanks for this project!
Webpack 4 currently loads ./dist/chart.cjs since it doesn't support exports: https://github.com/webpack/webpack/issues/9509

Looks like it was broken by #11033 (which switched main)

This seems ok, but I am a bit wary of all these changes in the package.json file. It seems like the bundler ecosystem is so fragmented that finding a solution that works for everyone is impossible.

This seems ok, but I am a bit wary of all these changes in the package.json file. It seems like the bundler ecosystem is so fragmented that finding a solution that works for everyone is impossible.

I think one mistake was to change anything else than adding the exports. Old stuff does not read the exports at all, and we had things working quite well.

Thanks everyone!

@etimberg @kurkle @LeeLenaleee Hi. How about to make bugfix release with it?

I think @LeeLenaleee suggested in slack, that it should be 4.2 because package.json changed. But I'd be fine releasing this kind of change as a bug fix.

@kurkle @LeeLenaleee @dangreen @etimberg this PR should also solve another issue opened in annotation plugin (https://github.com/chartjs/chartjs-plugin-annotation/issues/831). Maybe this PR could be marked as "chore" in order to have an evidence in the release note. I'm just thinking loud.

Thank you @kurkle

can anyone one solve this problem I spend almost 4hours to fix this and still no clue thanks.

@Sokhongg you should transpile dependencies with babel
https://dev.to/cubejs/why-and-how-to-transpile-dependencies-of-your-javascript-application-3phf


chore: cancel previous CI runs in PRs

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
If PR branch is pushed/force-pushed, there's no reason to keep running previous CI checks
Use cases and why
To use less CI minutes. This change applies only to CI that is triggered by opened PR
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Ahh cool, wasn't aware this was possible, thanks for the PR!


Fix createClient issue

Minimal changes required to fix createClient issue

Maybe an explanatory comment? And perhaps this can be temporary as well.


[LoongArch64] Add support for loongarch64 architecture

Add support for the new architecture LoongArch64.

The (Architecture)6 is Architecture.LoongArch64, which was introduced since .NET 7 and later.

@shushanhf

@microsoft-github-policy-service agree

Hi, @am11
Could you help to review this PR?
Thanks!

The code changes look good. Perhaps @mikem8361 can take a look together with dotnet/diagnostics PR for loongarch64.

cc @leculver, this is similar to riscv64 https://github.com/microsoft/clrmd/pull/1255.


Home-landing-page

This pull request implements the following changes and addresses the related issue. The motivation and context behind these modifications are outlined below. Additionally, any dependencies necessary for this update are specified.
Summary of Changes
This pull request introduces a new webpage layout based on the provided HTML template. The layout includes a section with a heading, subheading, and a button, along with an optional image displayed on larger screens.
Motivation and Context
The motivation behind this change is to create an engaging and visually appealing webpage layout for the project. By incorporating Bootstrap styles and custom CSS, the design aims to enhance user experience and make the content more accessible and attractive.
Dependencies
Bootstrap CSS and JavaScript libraries
Google Fonts
Custom stylesheets

closing as this is done, please pick another issue


[SVCS-565]Allow same origin in sandboxing

Ticket
https://openscience.atlassian.net/browse/SVCS-565

Purpose
Add allow-same-origin to our sandboxing

Changes
added allow-same-origin to sandboxing. this should fix the PDF issue on staging (hopefully)

Side effects
Could possibly make it less secure (specifically jasp and jamovi renderers)

QA Notes

Deployment Notes

Coverage remained the same at 68.016% when pulling c6ce99a74839bd527d136e1c708dcf108375ebf1 on AddisonSchiller:sandbox-fix-allow-same-origin into b2ba1103591a84c18764d542416f9d07f484b9ce on CenterForOpenScience:develop.

Merged!


specgen: re-enable acceptance tests

Feature description
The acceptance testing has been commented out in #198. We need to re-enable those tests.

Fixed in #212.


Find a way to get the normalized unerased type of a local

Validation needs to be able to access the fully normalize, non-erased type of a local. Currently (well, with https://github.com/solson/miri/pull/297 merged), we use our own copy of some functions from rustc/infer/mod.rs, but they end up replacing ReVar with ReErased for lack of an alternative. That's enough to make the test suite pass, but probably that's just because our test suite is fairly small and doesn't hit the really interesting case here.
Going one step further, validation should actually be able to assert that it never sees a ReErased. Currently, it does see them, and the above is not the only source of ReErased. I have yet to figure out where the other ReErased come from.
Unfortunately, the compiler currently doesn't have the infrastructure to do region inference in a non-erased way, so this will have to wait until @eddyb did some magic in regionck.

The other ReErased come from types like this &ReEarlyBound(0, 'a) [T]] that end up being &ReErased [u8] after normalization.

I did give you a potential that doesn't involve regionck rewriting:
infcx.resolve_regions_and_report_errors(def_id,
                                        &RegionMaps::new(),
                                        &FreeRegionMap::new());

You'd have to do this just after select_all_or_error and before trying to resolve inference variables in the result (and lift it). I just don't know what dummy value you could use for def_id.

Oh wow the context is unused! brb making PR to remove it!!!

I tried resolve_regions_and_report_errors, and calling it works, but I was unable to come up with an example that gets fixed by this. In fact, I hard a hard time even finding an example where we actually get incorrect lifetimes currently (the fact that ReEarlyBound turns into ReErased makes it really hard to test for this). Here is one:
trait Id {
    type Out;

    fn id(self) -> Self::Out;

   // fn step2(Self::Out) ->
}

impl<'a> Id for &'a mut i32 {
    type Out = &'a mut i32;

    fn id(self) -> Self { self }
}

impl<'a> Id for &'a mut u32 {
    type Out = &'a mut u32;

    fn id(self) -> Self { self }
}

fn foo<T>(mut x: T) where for<'a> &'a mut T: Id
{
    let x = &mut x;
    let _y = x.id();
    // Inspecting the trace should show that _y has a type involving a local lifetime, when it gets validated.
    // Unfortunately, there doesn't seem to be a way to actually have a test fail if it does not have the right
    // type.  Currently, this is NOT working correctly; see <https://github.com/solson/miri/issues/298>.
}

fn main() {
    foo(3)
}

Unfortunately, this involves HRTB, which do not work correctly even with resolve_regions_and_report_errors. The trace shows:
TRACE:rustc_miri::interpret::step:   // bb1
TRACE:rustc_miri::interpret::step:   Validate(Acquire, [_4: <&ReScope(Remainder(BlockRemainder { block: NodeId(62), first_statement_index: 0 })) mut T as Id>::Out])
TRACE:rustc_miri::interpret::eval_context:   _4: by ref:
TRACE:rustc_miri::interpret::memory:   Alloc Runtime(2): 00 00 00 00 00 00 00 00 (8 bytes, alignment 8) (stack)
TRACE:rustc_miri::interpret::memory:                     └────(Runtime(1))─────┘
TRACE:rustc_miri::interpret::memory:   Alloc Runtime(1): 03 00 00 00 (4 bytes, alignment 4) (stack)
TRACE:rustc_miri::interpret::validation:   Acquire on Local { frame: 1, local: _4 }: &ReErased mut i32
TRACE:rustc_miri::interpret::memory:   Frame 1 acquiring Write lock at MemoryPointer { alloc_id: Runtime(2), offset: 0 }, size 8 for region None
TRACE:rustc_miri::interpret::validation:   Acquire on Ptr { ptr: PtrAndAlign { ptr: Pointer { primval: Ptr(MemoryPointer { alloc_id: Runtime(1), offset: 0 }) }, aligned: true }, extra: None }: i32
TRACE:rustc_miri::interpret::memory:   Frame 1 acquiring Write lock at MemoryPointer { alloc_id: Runtime(1), offset: 0 }, size 4 for region None

Notice how the type starts out as <&ReScope(Remainder(BlockRemainder { block: NodeId(62), first_statement_index: 0 })) mut T as Id>::Out, but then in the validation method we see &ReErased mut i32. The region got lost, and it should be a ReScope, so this is just wrong.
However, the test case still passes no matter what I do, because when _y goes out of scope it actually calls drop which means the locks do get released at the right time.

Actually this does not work. Some testcases fail:
error: internal compiler error: src/librustc/infer/region_inference/mod.rs:910: cannot relate region: LUB(ReErased, ReEmpty)

the fact that ReEarlyBound turns into ReErased makes it really hard to test for this

So. Inside a body, it's not ReEarlyBound. It's ReFree. ReEarlyBound would be invalid, or would require some de Bruijn gymnastics to make work in that position.
If something erases ReFree lifetimes, I don't see why it wouldn't erase ReScope at the same time. MIR building should definitely not erase anything.

Note to future self: Here is the code that does more resolution:
        use rustc::hir::def_id::{DefId, CRATE_DEF_INDEX};
        use rustc::middle::region::RegionMaps;
        use rustc::middle::free_region::FreeRegionMap;
[...]
            self_.resolve_regions_and_report_errors(
                DefId::local(CRATE_DEF_INDEX),
                &RegionMaps::new(),
                &FreeRegionMap::new()
            );

            let result = self_.resolve_type_and_region_vars_if_possible(result);

However, it doesn't work because region resolution is not happy with some of the regions that occur here.

However, it doesn't work because region resolution is not happy with some of the regions that occur here.

Note that back when I wrote some of the function pointer calling code I started erasing all kinds of regions everywhere. Maybe that's where your weird regions are coming from?

I am trying to avoid calling miri's function for this, precisely because it erases regions everywhere, but maybe I accidentally still call one of them somewhere. Next thing I want to do here is figure out where the ReErased are still coming from.

I think this might be happening inside interpreted function calls. The erasing might have already happened for the Instance. Even if you are not calling any of miri's functions, you might be reading a type from something that was created via an erasing function.

I think you are right -- the frame's substitution already contains erased lifetimes:
TRACE:rustc_miri::interpret::step:     Validate(Acquire, [_1: &ReFree(DefId { krate: CrateNum(0), node: DefIndex(5) => issue_26709/8cd878b::{{impl}}[0]::drop[0] }, BrAnon(0)) mut Wrapper<ReEarlyBound(0, 'a), T>])
TRACE:rustc_miri::interpret::validation:     Type after substitution: &ReFree(DefId { krate: CrateNum(0), node: DefIndex(5) => issue_26709/8cd878b::{{impl}}[0]::drop[0] }, BrAnon(0)) mut Wrapper<std::marker::Send + ReErased>
TRACE:rustc_miri::interpret::validation:     Substitution: Slice([ReErased, std::marker::Send + ReErased])

Notice how ReEarlyBound(0, 'a) becomes ReErased. TBH I'd rather keep the ReEarlyBound for the purpose of validation; that will at some point even let me determine whether this lifetime is may_dangle or not...
I tried to find out where the instance gets erased, but couldn't find the spot.

Right here: https://github.com/solson/miri/blob/master/src/librustc_mir/interpret/terminator/mod.rs#L100

That erases the sig, but not the instance (called fn_def here).

right. in the non fn ptr case https://github.com/solson/miri/blob/63c48435030c3f3057aa9da8ffb4be8389896050/src/librustc_mir/interpret/eval_context.rs#L1249 erases the regions before we extract the def_id and subst
and in the fn ptr case it's also operand_ty called in the ReifyFnPointer arm

I have pretty much given up on ever achieving this, and instead will implement an aliasing model that does not rely on lifetimes.


Array "items" gets "type" even if "items" contains a manual $ref

I have
###
#   summary: Retrieves the public data from multiple user id's at once.
#   parameters:
#     - name: id
#       type: array
#       in: query
#       items:
#         $ref: '#/definitions/bsonObjectId'
#       collectionFormat: multi
#   responses:
#     200:
#       description: A list of all the locatable users that were requested, up to once per unique id.
###
GET     /multi            controllers.UserController.getMultiple(id: Seq[BSONObjectID])

The output:
{
  "/user/multi": {
    "get": {
      "tags": [
        "user"
      ],
      "summary": "Retrieves the public data from multiple user id's at once.",
      "parameters": [
        {
          "name": "id",
          "type": "array",
          "required": true,
          "items": {
            "type": "bsonobjectid",
            "$ref": "#/definitions/bsonObjectId"
          },
          "in": "query",
          "description": "The User ID's to look up.",
          "collectionFormat": "multi"
        }
      ],
      "responses": {
        "200": {
          "description": "A list of all the locatable users that were requested, up to once per unique id."
        }
      }
    }
  }
}

"/user/multi"/get/parameters/0/items should not contain "type"

There are 2 enhancement I can think of that both fix this.

for items add a special treatment so that if a '$ref' is given, remove all other elements
enable "removal" override, so that if people add something like a type: "__removal" in the comment then the type element will be removed at the final result. As of now people don't have a way to remove an element generated by play-swagger unless they override the whole parent element.

@joprice would like to get some of your thoughts on this one as well.

@SattaiLanfear can #116 help mitigate this issue?


Fix the scheduling and permissions issue of CA

by fixing the conditional in stack-template.json for worker and controller stacks, while making configuration easier.
Resolves #897
Context
The intended way of enabling cluster-autoscaler on your cluster has been to:

Set addons.clusterAutoscaler.enabled to true
Set experimental.clusterAutoscalerSupport.enabled to true to allow CA to be run on controller nodes, while providing appropriate IAM permissions to the controller nodes
Set worker.nodePools[].clusterAutoscalerSupport.enabled to true to allow CA to be run on worker nodes, while providing appropriate IAM permissions to the worker nodes
Finally, set worker.nodePools[].autoscaling.clusterAutoscaler.enabled to true for registering the node pool(s) as the scaling targets

Note that:

is required in order to deploy CA on your cluster.

and/or 3. is required to actually allow scheduling CA to any node

is required to instruct CA to start auto-scaling. Btw, missing this step had been resulted in #800 before.

The fix
worker.nodePools[].clusterAutoscalerSupport.enabled has been configured CA to run on worker nodes, certainly. However, it was not providing required IAM permissions to the worker nodes.
More concretely, you had to set worker.nodePools[].addons.clusterAutoscaler.enabled instead and that's not an expected way of configuring things. This is now fixed.
#897 is considered to be affected by this.
The easier configuration
To make this process easier, experimental.clusterAutoscalerSupport.enabled is now set to true by default.
This way, 2. and 3. can be completely omitted when you don't mind on which node CA runs.
A validation to prevent a misconfiguration is also added.

Codecov Report

Merging #905 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #905   +/-   ##
=======================================
  Coverage   35.41%   35.41%
=======================================
  Files          57       57
  Lines        3978     3978
=======================================
  Hits         1409     1409
  Misses       2406     2406
  Partials      163      163

Impacted Files
Coverage Δ

core/controlplane/config/config.go
57.92% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Delete model directory if it wasn't loaded correctly, when fetching from server

Proposed changes:

Fixes https://github.com/RasaHQ/rasa-x/issues/3597.

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Should we also delete the old model_directory in update_model if model_directory is a temp directory?

@wochinge yes that would be good. Let me check if there's a reliable way of knowing if a directory is temporary or not.


Coerce to Csparsematrix for C++ conversion efficiency

@LuckyMD bumping this

Addresses https://github.com/MarioniLab/scran/issues/70

Sorry, haven't gotten around to this. The point about the 2e9 non-zero value limitation... is that sth we need to worry about?

2e9 non-zero values would mean 25k genes and 80k cells max. That doesn't really work for single-cell data, no? If you assum 90% dropout that would be 800k cells. Still not really enough for our 1 million cell case. What do you think about a size limitation for when you cast to dgCmatrix?

You're right. Maybe a better solution would be to do this in python.
X = adata.X.T
if scipy.sparse.issparse(X):
    if X.nnz > 2**31-1:
        X = X.tocoo()
    else:
        X = X.tocsc()
ro.global_ev['data_mat'] = X

That way we avoid dgRMatrix which is terrible, and use dgCMatrix when possible.

Could you merge master into this PR? Then I can merge. Looks good now and gives me the same results. We can always troubleshoot if there are storage limitations at some point.

no merge conflicts... so all good.

Thanks!
On Fri, 25 Sep 2020, 1:00 pm MalteDLuecken<EMAIL_ADDRESS>wrote:

no merge conflicts... so all good.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/theislab/scib/pull/164#issuecomment-699041960, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA3DX7NTBMLWH3S4J7FNMTSHTEDXANCNFSM4RIJWDYQ
.


Fix Issue with Parenthesis in URL

SUmmary
This commit fix an issue when one user try to add an URL
containing an URL. The pattern matching stop at the open
parenthesis. The URL generated is wrong and it archives
a truncated one.
You can easily reproduce this behavior by adding any URL
to archive and see this will not correctly archived.
Related issues
Did not find any related issue.
Changes these areas

[x] Bugfixes
[ ] Feature behavior
[ ] Command line interface
[ ] Configuration options
[ ] Internal architecture
[ ] Snapshot data layout on disk

I'm looking forward to using this app. Please fix. If I knew more I would help.

The reason we stop parsing at parens is to support loading URLs from markdown. A solution would have to detect if the content looks like markdown and parse it accordingly, which is difficult and why I haven't done it already.

I'm going to close this for now because the markdown-parsing behavior is one of the most common uses of ArchiveBox. But don't worry, I still plan to implement markdown-detection in the future to resolve the underlying UX issue and allow parens in non-markdown URLs.


haskell: ghcjs packages: fix ghcjs-dom-jsffi with newer Cabal

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I don’t think that fixes it; normally you can’t simply replace cabal, since it’s a distribution package.

For me it works, I'm not sure why it wouldn't but I can explain what happens.
This is just a setup dependency, which means there won't be any diamond style dependency conflicts, the package doesn't care with which Cabal version it was build, after the fact.
We do this in other places but the override way doesn't work here because Cabal is not an explicit dependency.
Generally user package-db entries take precedence over distribution package-db entries and newer packages versions take precedence over older. So even if there is a Cabal in the distribution (which won't be the case after #23614) the one we pass here will be selected and if there is an older one in the user package-db (there will be after #23614), it will be selected, since it is newer. So it all works out.
What isn't quite correct here, is that Cabal is added to libraryHaskellDepends it should be setupHaskellDepends. At the moment it makes no difference, but I will change it, quickly.
By user package-db I mean the one we construct and pass explicitly, not some literal user package-db.

Ah, I see! Then I suggest @peti should merge it.


On collectd >5.5 the default metrics include swap even if swap not enabled

When installing on CentOS 7 (behaves the same on RHEL 7.2) which has collectd 5.6 in the repos the setup.py defaults to option 3 on the last step which adds the 4 metrics to the whitelist.
If the machine does not have swap enabled the swap--percent-used causes 400 errors to the API because the plugin tries to send NaN values to CloudWatch.
setup.py should check if swap is even enabled before adding swap to whitelist.

One thing to add for anyone looking to fix.  If you're seeing 400 errors in /var/log/collectd.log try removing swap--percent-used from:
/opt/collectd-plugins/cloudwatch/config/whitelist.conf
Then restart collectd.  If you have SELinux in enforcing mode you may have some trouble restarting collectd.
I don't know SELinux too well so someone may have a better fix here, but to check if this is the problem set SELinux to permissive in /etc/selinux/config and reboot.  I had no luck with setenforce 0.
If anyone has an SELinux policy that will play nice with collectd I'm all ears. :)

Updated the title of the issue to include mentioning 400 errors so it might catch more people heading here for help. :)

fixed by https://github.com/awslabs/collectd-cloudwatch/commit/853c99e4b370a2518107c29c69364f81985b38b0


[Snyk] Upgrade husky from 7.0.4 to 8.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade husky from 7.0.4 to 8.0.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Warning: This is a major version upgrade, and may be a breaking change.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2022-05-08.

Release notes

Package name: husky

8.0.0 - 2022-05-08What's Changed
Feats

feat: add husky - prefix to logged global error messages by @ joshbalfour in #1092
feat: show PATH when command not found to improve debuggability
feat: drop Node 12 support
feat: skip install if $HUSKY=0

Fixes

fix: hook script use /usr/bin/env sh instead of direct path of sh by @ skhaz in #1051
fix: actually set 'husky_skip_init' as readonly in ./husky.sh by @ hyperupcall in #1104
fix: force basename/dirname to treat $0 as an argument by @ mataha in #1132
fix: remove git.io links by @ renbaoshuo in #1136

Docs

docs: fix uninstall via npm by @ pddpd in #1033
docs: add dog emoji as favicon by @ jamiehaywood in #1095
docs: replace deprecated npx --no-install option with npx --no by @ sibiraj-s in #1070
docs: add pnpm installation by @ MohamadKh75 in #1139

Chore

chore: update workflows by @ tiziodcaio in #1125

7.0.4 - 2021-10-21No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

    from husky GitHub release notes

Commit messages

Package name: husky

f5b5c33 chore: update version
3e0e15c feat: show PATH if command not found
356714b test: command not found message
21bc342 feat: skip install if $HUSKY=0
e9351c0 docs: add pnpm installation (#1139)
19710f7 docs: replace deprecated npx option (#1070)
4b33931 docs: fix windows workaround
54b3fab chore: skip windows npm 6 tests
74a88ef test: skip sub-dir
d400b3b test: skip sub-dir
3a24ae5 chore: update package.json node version to 14
afd07f0 chore: update workflow
2a12f3e chore: update devDependencies
beaf645 feat: add `husky -` prefix to logged global error messages (#1092)
ff246cf chore: update workflow
cfa2b15 chore: update workflow
a9083bc chore: update workflow
6f85d63 chore: update workflow
2374e7b chore: update Workflows (#1125)
3845804 chore: remove git.io (#1136)
0bcdac6 fix: force `basename`/`dirname` to treat `$0` as an argument (#1132)
68e26c6 docs: update yarn 2+ install
82b0c59 fix: actually set 'husky_skip_init' as readonly (#1104)
222b1de docs: add another way to disable husky in prod

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report

Merging #231 (6305f13) into master (1a04fb5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #231   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines          218       218
  Branches        29        29
=========================================
  Hits           218       218

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


proxy-setting: Feature to use system proxy settings.

This commit uses resolveProxy to to read system proxy settings by requesting to a url namely chat.zuip.org using the 4 protocols http, https, ftp, socks, this causes the main process to return the system used proxy for this particular protocol. We store this proxies in proper proxy format string using ConfigUtil into settings.json as systemProxySettings.
On turning on the use system proxy settings this value of systemProxySettingsis written into the proxy rules and the webview session and is reloaded as done previously with only manual settings.
It removes the previous use proxy option and replaces it with use system proxy and manual proxy
options.
Fixes: #296
You have tested this PR on:

[x] Windows
[x] Linux/Ubuntu
[ ] macOS

@akashnimare Could you also test this on your macOS? If you're not on a proxy server, you can just try putting some random proxy server in system settings and just test if the correct ones are being written on to the settings.json.

Merged. Thanks, @abhigyank. The only thing remaining here is to update the system proxy settings without restarting the app. The more advance set up would be update the settings etc when user changes/updates these settings from the system configs. Let's also look into http-proxy if it gives better results :)


Adding and Subtracting

Hi,
So I'm looking for a way to be able to add, subtract, multiply and divide timecode - for archive and licensing calculations.
Mind if I take a look at implementing some functions?

Hey, I'm open to adding some more functions here, but what in particular did you have in mind? Could you share a list of function signatures and a quick description of what each would do before you start implementing anything?
The main approach I've used with formulas so far has been to convert all timecodes into frame indexes with TC_TO_FRAMEIDX(), do any math in terms of frames, and then convert back to timecode with FRAMEIDX_TO_TC() as needed.
WALL_SECS_BETWEEN_TCS() does timecode subtraction to get a duration in wall seconds, mainly as a convenience since that's a common use case.
So I'm open to adding other functions here, but I do want to make sure the semantics stay clear and aren't error-prone (just as an example: I think measuring durations in timecode is ambiguous or at least potentially confusing because of drop frames, so I wouldn't want any API functions to accept or return timecode durations).


[Automation]  BIOS versioning string changed

Please refer : https://github.com/openbmc/openbmc/issues/821
for details of the information.

@SrideviRamesh  I think the string are now as per original one i think.. Confirm the same and close this..

This is the BIOS string which we are seeing at the preset. This string the not matching with our test and failing our test.
1:30:13     "Name": "OpenPOWER Firmware",
21:30:13     "Serial Number": "",
21:30:13     "Version": "IBM-barreleye-ibm-OP8_v1.12_2.77",
21:30:13     "fault": "False",
21:30:13     "fru_type": "SYSTEM",
21:30:13     "is_fru": 1,
21:30:13     "present": "True", ```

Again the Versioning changed... ?

Closing as the new interface xyz is coming up..


Flair authentication failed. Are your credentials correct? - Creds are correct, debug logging does not help troubleshoot

I've been using this container to push flair data to home assistant via mqtt. Its been working well for me for a year, but I stumbled on your project which is a much better solution than the container I hacked together.
Unfortunately, I encounter an issue when adding the integration "Flair authentication failed. Are your credentials correct?". The credentials are correct, so I enabled debug logging for the component but didn't find anything that indicated what the issue might be.
Installed via HACS - v0.0.4

I just deleted the integration, restarted HA, and added it again without a problem. I'll need to add logging to the config flow in an upcoming release.  The config flow essentially takes your credentials and logs in. Try rebooting the host machine (of Home Assistant) and then  add the integration.

@mlebaugh any updates on this?

Sorry for the delay, got caught up on some work tasks. I deleted the integration, restarted the server its running on, reinstalled etc. I tried all the normal things. I also did not use apostrophes when attempting through the automation. I'll probably have to wait for additional debugging logs, unless you have some other troubleshooting ideas.

Can you send this curl command via your terminal and let me know if it returns an authentication token:
curl -X POST 'https://api.flair.co/oauth2/token?client_id=CLIENT_ID&client_secret=CLIENT_SECRET&scope=thermostats.view+structures.view+structures.edit&grant_type=client_credentials' -H 'Content-Type: application/x-www-form-urlencoded' -F 'client_id="CLIENT_ID"' -F'client_secret="CLIENT_SECRET"' -F 'scope="thermostats.view+structures.view+structures.edit"' -F 'grant_type="client_credentials"'
Be sure to put your client ID and Client secret where CLIENT_ID and CLIENT_SECRET are defined after "-F".
For example where it says -F 'client_id="CLIENT_ID"' it should be -F 'client_id="YourClientID"'
Do the same for the secret and be sure to keep all quotation marks and apostrophes where they are.

here is what I ran, I replaced redacted_* with what I replaced.
matt@Matts-MBP ~ % curl -X POST 'https://api.flair.co/oauth2/token?client_id=CLIENT_ID&client_secret=CLIENT_SECRET&scope=thermostats.view+structures.view+structures.edit&grant_type=client_credentials' -H 'Content-Type: application/x-www-form-urlencoded' -F 'client_id="redacted_id"' -F 'client_secret="redacted_secret"' -F 'scope="thermostats.view+structures.view+structures.edit"' -F 'grant_type="client_credentials"'
{"error": "invalid_client"}%                                                                                matt@Matts-MBP ~ %

Sorry, it looks like the updated Flair API documentation isn't correct/doesn't work yet (they will be moving to oauth2 in the future). Could you please use this curl command and be sure to replace CLIENT_ID and CLIENT_SECRET in the URL with your client ID and client secret.
curl -X POST 'https://api.flair.co/oauth/token?client_id=CLIENT_ID&client_secret=CLIENT_SECRET&scope=thermostats.view+structures.view+structures.edit&grant_type=client_credentials' -H 'Content-Type: application/x-www-form-urlencoded'

That returns a token. See below
matt@Matts-MBP ~ % curl -X POST 'https://api.flair.co/oauth/token?client_id=redacted_id&client_secret=redacted_secret&scope=thermostats.view+structures.view+structures.edit&grant_type=client_credentials' -H 'Content-Type: application/x-www-form-urlencoded'
{"access_token": "redacted_token", "expires_in": 3600, "token_type": "Bearer", "scope": "thermostats.view structures.view structures.edit"}%
matt@Matts-MBP ~ %

@mlebaugh update the Flair integration to <IP_ADDRESS> (most recent release). It should now log any exceptions raised by Flair's API during initial set up as errors in Home Assistant. Let me know what your log shows whenever you get a chance to test it out so we can narrow down the problem.

Well this is interesting.
2021-08-11 21:40:39 ERROR (MainThread) [custom_components.flair.config_flow] Unable to connect to Flair: Failed to Log In
2021-08-11 21:40:39 ERROR (MainThread) [custom_components.flair.config_flow] ApiError<HTTP Response: 404>
Previously I ran that curl command on my laptop, to ensure I'm not having any issues with my container I attached to it and issued the same command, it returned a token there too. Not really sure why I'd be getting a 404 from the integration, but not directly from the container.

Yes 7 rooms, 1 puck, and probably ~14 vents.

Edit the config_flow.py file and replace discover_rooms located on line 51 with discover_pucks. Save the changes, restart home assistant, and try again.

No luck, same error.

How are you running Home Assistant? I'm starting to think that this issue is related to your personal setup as others have not had this problem.

I'm running home-assistant in an unsupervised docker container, which I think is pretty common.  I've spun up another test home-assistant container with nothing but the custom-config directory and tried to set this up there and had the same issue (on multiple hosts).
That said, I'm thinking there is something is unexpected with my flair setup. I don't mind sharing my flair creds for you to take a look, just don't know the best way to do that.
Thanks again for your help.

Sure just send them my way. Best way to do it would be via e-mail to dr.robert1316 at gmail.com


Error: connect ECONNREFUSED <IP_ADDRESS>:8883

Hi,
I get this issue every time, when I deploy a change in nodered.
Only one config node available. Username 'Senbei'.
Can you support?
Br,
Senbei

Ignore it, it will reconnect on the other port about 30 seconds later.
You can also set Node-RED to only deploy changed nodes (since the config node will never change after the first deploy) and it won't tear down and restart the connection on every deploy


Fix index.fetch() bug

index.fetch() was accidentally hardcoded to always pull data from hash, even if the schema declared JSON for data storage. Updated the method to use the Storage class for handling the get operation and updated the tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (bcb27dd) 80.65% compared to head (3762664) 82.59%.

:exclamation: Current head 3762664 differs from pull request most recent head 58f2b67. Consider uploading reports for the commit 58f2b67 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
+ Coverage   80.65%   82.59%   +1.94%
==========================================
  Files          25       25
  Lines        1473     1477       +4
==========================================
+ Hits         1188     1220      +32
+ Misses        285      257      -28

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Avoid try: .. except ImportError: blocks

The following occurs when running on https://github.com/stephenmcd/django-forms-builder with various deprecation/removed args.
Several problems can be seen here, but IMO the main one is that both branches should just be ignored unless the parser properly understands what ImportError exceptions will occur in each branch, and avoid changes when they are supposed to trip an exception and are handled correctly in the exception block.
git diff forms_builder/example_project/urls.py
diff --git a/forms_builder/example_project/urls.py b/forms_builder/example_project/urls.py
index 78627dd..a944703 100644
--- a/forms_builder/example_project/urls.py
+++ b/forms_builder/example_project/urls.py
@@ -1,10 +1,10 @@
 from __future__ import unicode_literals

 try:
-    from django.urls import re_path, include
+    from django.urls import re_path as re_path, re_path, include
 except ImportError:
     # For Django 1.8 compatibility
-    from django.conf.urls import url as re_path, include
+    from django.conf.urls import include
 from django.contrib import admin
 from django.shortcuts import render

When I started this tool, I had in mind Django projects, not re-usable Django app. Django app usually need to target more than one version of Django, and will have these sort of imports.
This is indeed not supported yet, it's more that it's out of the initial scope and objetive of the project.
We should at least put up a warning or disclamer somewhere until we handle it better.
I think it should be feasible by disabling the visitors temporarily using the context when inside of try/except blocks

I've added a paragraph in the readme to make this limitation clearer.

I've added a paragraph in the readme to make this limitation clearer.


Support for MySensors switch component

Currently the home-assistant mysensors component can only relay data, If the mysensors could be added as a switch that would greatly improve the compatibility of a mysensors setup.

+1 for this
I've started doing some work on this but I don't know how fast it'll progress. I'd be happy if the maintainers of pymysensors and home-assistant or someone else beats me to it. =)
So far I've added a fifo queue to pymysensors to handle the communication with the thread and function to send a set command from gateway to node. This is working, but there seems to be some general reliabilty issues around the serial interface when restarting the program, which I've been troubleshooting.
I've also started a bit on adding a general mysensors component and a switch platform to home-assistant. But it's not tested yet.

Update:
I've successfully implemented support for mysensors switches by adding a general mysensors component and a mysensors switch platform and rewriting the mysensors sensor platform in a similar way. I'm waiting for my pull request to pymysenors to be evaluated, before I submit a pull request here.

Any news on that @MartinHjelmare? Sounds great.

I'm still waiting for any feedback on my PR to pymysensors: https://github.com/theolind/pymysensors/pull/13.
I'm considering dropping that one, and making another less code invasive, using a threading.Lock, which should enable the same thread conflict handling. I've already a branch for that in my fork. I've also made a corresponding alternative branch for home-assistant using my new lock_thread branch, https://github.com/MartinHjelmare/pymysensors/tree/lock_thread.
Meanwhile I've also adding functionality to both home-assistant alternatives, https://github.com/MartinHjelmare/home-assistant/tree/mysensors-component-switch and https://github.com/MartinHjelmare/home-assistant/tree/mysensors-component-switch-ver2, support for multiple serial gateways is the major one. I'm finishing testing of this during this week.
Bottom line is, since home-assistant relies on pymysensors for the MySensors serial gateway implementation, my PR to home-assistant must wait for my PR to pymysensors.

Update:
https://github.com/balloob/home-assistant/pull/771 is merged and included in release 0.11. Please try it and let us know of any problems.


Soroban settings upgrade failure is silent

https://github.com/stellar/quickstart/blob/974fb36f9df9bf0f0600367cdcc6ec7e5d4fb453/start#L509 can fail due to bad values being set, but supervisor just catches the error and continues. We should fail on startup here.

We should prioritize this. The upgrade started failing silently after the v21 update.


crypto_box_seal

Would it be possible to add the functionality for sealed boxes?
https://doc.libsodium.org/public-key_cryptography/sealed_boxes

Had some free time pop up today - I've got version 2.4.0 released which adds the crypto_box_seal and crypto_box_seal_open functions https://luarocks.org/modules/jprjr/luasodium


Minor README fix

Great looking project! Just a quick grammar tweak I noticed when first looking through.

https://youtu.be/C6MGKHkNtxU

Thanks for you interest, and for the correction!


Supports feature for iso_datastore

This came up as part of the work to split the oVirt provider and getting necessary spec tests passing

Depends on:

https://github.com/ManageIQ/manageiq-ui-classic/pull/8129
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/596

@miq-bot add_label enhancement
@miq-bot assign @agrare


There may be a problem with the callback logic

Which version and edition of Flyway are you using?
7.5.2
8.3.0
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
8.3.0 is latest
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line,
Which database are you using? (Type & version)
postgresql13
Which operating system are you using?
Mac
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
migrate with afterMigrate
What did you expect to see?
It is called only when the migrate is successful (the version number has changed).
What did you see instead?
It will be called every time you migrate, even if the version number has not changed

This is expected behavior, so closing this issue for now.
Depending on what you're doing, you might want to look into using both afterMigrate and afterMigrateError, or use repeatable migrations.


about train code

Thank you for your work, it looks very interesting. I hope I can replicate this work, would it be possible to open source the related training code?

Unfortunately we have not trained the model. But if someone wanted to add their training code we could definately incorporate it.


Change the functions/ directory?

Curious if there's a way to change the functions/ directory. I tend to keep everything under src/, so having it top-level is a little inconvenient.

Looks like functions is hardcoded:
https://github.com/apex/apex/blob/master/boot/boot.go#L170-L171

I kinda like it hard-coded TBH haha, at least for Go projects where you have tons of root-ish pkgs

ahh that does look really nice, what about your project's dotfiles? with node there's a gazillion of them.

closing, this standardization has grown on me


Get ScreenCapture working for OpenXR-Build on Quest 3

Hey trev3d,
my project is set up with the OpenXR-Background and I can't change so easy back to Oculus (like your example)... so I've tried to include your work in the OpenXR space, but get always the follown error...
"java.lang.NoSuchMethodError: no non-static method with name='startScreenCaptureWithPermission' signature='(Ljava/lang/String;II)V' in class Lcom.unity3d.player.UnityPlayerActivity;"
I've also seen that you included the "RecordNotificationService.java" library in the AndroidManifest for the Oculus-Build in the XR-Management.
I am an absolute newbie in Java plugins so have you any help for me, how I could get ScreenCapture work in the OpenXR space?
Have you got the capture functionality already running for OpenXR backend OR are you planning to get it work for this backend?
Thanks for your help :)
All best!

The project relies on a custom UnityPlayerActivity which includes the code for screen capture. That is in UnityPlayerActivityWithMediaProjector.java. You must specify this class as the launch activity in your manifest. See the <activity> bit of the project's manifest :)

Thank you trev3d!
I had completely overlooked the other part after it was hidden so far back in the line!
Works great now.
P.S. for all those who want to integrate the ScreenCapture into their application... you should add the following colored lines to your setup.

All the best :)


Crash in modpack

Description
I added this mod in my modpack, and the game crashed when I switched to survival mode. Below is the crash report and the log file.
I could't make sure whether it's a bug or it's the incompatibility with other mods(Maybe the Victus mod?), so I didn't open the issue as a bug.
Screenshots
No response
Other Files
crash-2022-05-03_01.07.57-client.txt
latest.log

There was some update in obfuscated names from 1.18.1 to 1.18.2 which fabric didn't handle well (forge handled it without any problems)

the v3.0.0 does only support 1.18.2, though there was a beta version targeting 1.18.1 (doesn't have the full range of features, though)... i've uploaded that one to my webserver for you to use: https://files.cheos.dev/armorpointspp-fabric-1.18.1-3.0.0-beta3.jar


Remove transports field from js/ts as it is not mapped on server side

AuthenticatorAttestationRawResponse.ResponseData on server side doesn't contain any Transports property.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (11c78ce) 77.52% compared to head (79493f6) 77.52%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #453   +/-   ##
=======================================
  Coverage   77.52%   77.52%
=======================================
  Files          98       98
  Lines        2714     2714
  Branches      445      445
=======================================
  Hits         2104     2104
  Misses        491      491
  Partials      119      119

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@abergs, @aseigler this PR is ready to be reviewed

@abergs I added the transports on server side and tested manually (in addition to updating the unit tests).

@iamcarbon, @aseigler any thoughs please?

Code looks reasonable to me, not sure what is going on with those failed tests.  Is that new or an environment issue?

Code looks reasonable to me, not sure what is going on with those failed tests. Is that new or an environment issue?

The dotnet format step has failed with Unable to locate dotnet CLI. Ensure that it is on the PATH.. Are you able to re-run the failed job?

I'm trying to re-run those checks to see if can get this in!


[WIP] Implemented Browser tests

closes #185

Why are we including lib/Win64-526987/chrome-win32/locales/ar.pak?

Check this out @Meir017  https://github.com/kblok/puppeteer-sharp/commit/f7ed88ea1d0cad13f60f651995ffa882f16dfa72

@Meir017 https://github.com/kblok/puppeteer-sharp/pull/224/commits/90e9b23f8fe498635a05b92525c30f1171c67e91
If you want to read a little bit about the WebSocket mess go to https://github.com/dotnet/corefx/pull/26429 and https://github.com/dotnet/corefx/issues/26556
I found out that we don't need to filter exceptions if the read fails we need to close and move on.

It's not WIP anymore right @Meir017 ?


sensu2 - Support Amazon Linux 2.0, 2017.03 and 2018.03

Pull Request Checklist

Description

Add support for several Amazon Linux versions
Related Issue

Relates to #901
Motivation and Context

Should support Amazon's latest versions.
How Has This Been Tested?

In both Vagrant and Docker.
General

[ ] Tests pass - bundle exec rake validate lint spec

There is something wrong with Facter on Amazon 2.0 that causes the OS version to be kernel version and not 2.0.  This makes it difficult to use EL7 repo for just that version and EL6 repo for all others.  I found this https://tickets.puppetlabs.com/browse/FACT-1485, but says already fixed.  I think I can work around this issue with some reversed logic on fact checking for versions that do work and else falling back for version that doesn't work.

This PR will need to be squashed before merge.  I discovered this in Vagrantbox:
[root@amazon2-agent ~]# cat /etc/system-release
Amazon Linux release 2.0 (2017.12) LTS Release Candidate

This reports as Amazon 2 via Facter and appears to be accessible via amazonlinux:2017.12 docker image.  This version supports systemd and only mention I have found of Amazon Linux with systemd is Amazon Linux 2.

Opened https://tickets.puppetlabs.com/browse/FACT-1867 for fact amazonlinux:2 docker image is unable to report OS version using Facter.

That facter ticket has been fixed.

@ghoneycutt Updated to fix vagrant provisioning.  Sometimes vagrant up of amazon-201703 box will fail but a vagrant reload will fix the VM.  I think some race condition or timing issue with vbguest additions getting installed.
I updated acceptance tests to test amazonlinux 2 against amazonlinux:2 docker image now that puppet-agent-5.5.4 has patched Facter to properly identify Amazon Linux 2.

@ghoneycutt rebased and squashed.


Could you help me with adding multiple models to keras-serving

Could you help me with adding multiple models for keras-serving ? Just reply we can discuss it via email or skype.

Hi jerminal, I would like to help you on this. Are you talking about changing the model's feature vectors (input) and breaking the dimension apis in GRPC nodejs requests?
I will need a description of the input vector of your network to help you.

Or do you just want to add multiple versions of a model to the same serving-server?

I have both problems. I need to classify images (so to change the input vector). And I have multiple keras models that I want to apply to each image. So maybe you can add me to skype: jermuk_skype and I'll describe it with more details?

Or maybe you can tell me your skype or email?

For example to server models for face recognition.
Some examples from here: https://github.com/oarriaga/face_classification

Hi @jerminal I will try to setup an example using the face_classification soon.
I am sorry that I cannot give you support through Skype or Email.
Serving multiple versions of a model at once should be no problem, you should only have to name the exports differently and send the version as paramter to the grpc service during requests.

Oh. Great. But is it possible to check 1 image for several models at 1 request to docker server?
And about support - ok, no problem. You can add me to twitter or anything else. And I can pay for such improvements of your model if you'd like.

I would probably suggest to load multiple versions of the model into the serving-server and then use the nodejs service to make parallel requests to both/multiple models at the same time, its very easy to do this in node. Il try to setup the face-recog. example with such a parallel request endpoint.
Haha cheers! Il pm you on twitter, when I am working on it ;)

Actually the question here is, are you actually using the node.js service simplified API? If yes (thats cool) how many requests are u going to run against it? (You could scale the services to unlimited instances,, but its still a valid question if you are trying to predict in realtime using web-services)

I have about 10-15 requests per minute. It's not very much :)

And yes - I use the node.js service simplified API.

Cool, just hang on ;)

👍

So I have already pushed my current state into the remote master, but I am not done yet.
I still have to finalise the grpc node communications so that both models are used to predict on behalf of an image that is uploaded to the node server via client. I think I can finish this until mid next week :)

I have created a sub project as directory: https://github.com/krystianity/keras-serving/tree/master/face-recog

Thanks. Will be waiting for this very much!!!

@jerminal alright. It is up an running :)
Enjoy the awesomeness :cocktail: and drop me beer if you like https://www.paypal.me/5cf :beer:
Let me know if you need or want to try something else.

Hi. Thanks a lot!!! I'll check it in the evening.  And of course  I've sent drop for a beer for you.
And promise when I come to Germany again, I'll to treat you beer personally :)

Oh.. I have a strange problem. When follow the instructions:
https://github.com/krystianity/keras-serving/tree/master/face-recog#4-test-api-via-client
at p. 4  when I run: "npm start ./../images/cutouts/4.png" I got strange error :(
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/siarheiparashchanka/sites/keras-serving/face-recog/client
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node request.js "./../images/cutouts/4.png"' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: `node request.js "./../images/cutouts/4.png"`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:283:16)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at EventEmitter.emit (events.js:172:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at ChildProcess.emit (events.js:172:7)
14 verbose stack     at maybeClose (internal/child_process.js:818:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /Users/siarheiparashchanka/sites/keras-serving/face-recog/client
17 verbose Darwin 16.6.0
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "./../images/cutouts/4.png"
19 verbose node v5.1.0
20 verbose npm  v5.0.3
21 error code ELIFECYCLE
22 error errno 1
23 error<EMAIL_ADDRESS>start: `node request.js "./../images/cutouts/4.png"`
23 error Exit status 1
24 error Failed at the<EMAIL_ADDRESS>start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

No worries, your running node 5.10; (with npm 5.0.3 o.O) Can you upgrade you node version to at least 7.10 ?

If its not possible for you to update node on the root system, I can wrap the client in a Docker container as well :)

Updated node. Now strange thing with running npm start ./../images/cutouts/4.png
I got response:

><EMAIL_ADDRESS>start /Users/siarheiparashchanka/sites/keras-serving/face-recog/client
> node request.js "./../images/cutouts/4.png"

Reading from path: /Users/siarheiparashchanka/sites/keras-serving/face-recog/images/cutouts/4.png
Loaded image with size: 2304
Making request to CNN GRPC wrapper.
{
  "error": {
    "code": 3,
    "metadata": {
      "_internal_repr": {}
    }
  }
}

After upgrading nodejs, did you delete the node_modules folder in the face-recog/client dir and ran "npm install again" ? (just to make sure)
Additionally, I have a feeling that the models you servers are serving arent correct e.g. cached.
How are you starting the servers? When you are using my script (start-dual-servers.sh) it should make sure that nothing is cached.
To understand whats going wrong I need you to send me the error that is logged by the server, when your client retrieves the error.

Additionally.
Are you executing via python 2.7?
Which docker and docker-compose versions are you running?
Could you dump the whole output of docker-compose when you start the dual servers and make a request with the client?

Oh. I'll check it now on different computer. A few hours and will write back.

I've checked. The same problem.
Looks like problem with input tensor size:
node-server_1     | npm info it worked if it ends with ok
node-server_1     | npm info using<EMAIL_ADDRESS>node-server_1     | npm info using<EMAIL_ADDRESS>node-server_1     | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>node-server_1     | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>node-server_1     |
node-server_1     | ><EMAIL_ADDRESS>start /usr/src/app
node-server_1     | > node server.js
node-server_1     |
emotion-server_1  | 2017-06-16 13:55:14.421089: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:145] Restoring SavedModel bundle.
gender-server_1   | 2017-06-16 13:55:14.691086: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:145] Restoring SavedModel bundle.
node-server_1     | listening @ http://localhost:8080
emotion-server_1  | 2017-06-16 13:55:15.425129: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:180] Running LegacyInitOp on SavedModel bundle.
emotion-server_1  | 2017-06-16 13:55:15.459184: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:274] Loading SavedModel: success. Took 2047432 microseconds.
emotion-server_1  | 2017-06-16 13:55:15.460264: I tensorflow_serving/core/loader_harness.cc:86] Successfully loaded servable version {name: emotion_model version: 1}
emotion-server_1  | 2017-06-16 13:55:15.471674: I tensorflow_serving/model_servers/main.cc:298] Running ModelServer at <IP_ADDRESS>:9000 ...
gender-server_1   | 2017-06-16 13:55:15.608845: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:180] Running LegacyInitOp on SavedModel bundle.
gender-server_1   | 2017-06-16 13:55:15.648949: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:274] Loading SavedModel: success. Took 2080879 microseconds.
gender-server_1   | 2017-06-16 13:55:15.650862: I tensorflow_serving/core/loader_harness.cc:86] Successfully loaded servable version {name: gender_model version: 1}
gender-server_1   | 2017-06-16 13:55:15.663076: I tensorflow_serving/model_servers/main.cc:298] Running ModelServer at <IP_ADDRESS>:9000 ...
node-server_1     | { Error: input must be 4-dimensional[]
node-server_1     | 	 [[Node: image_array_2/convolution = Conv2D[T=DT_FLOAT, _output_shapes=[[-1,48,48,16]], data_format="NHWC", padding="SAME", strides=[1, 1, 1, 1], use_cudnn_on_gpu=true, _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_image_array_input_2_0_0, image_array_2/kernel/read)]]
node-server_1     |     at /usr/src/app/node_modules/grpc/src/node/src/client.js:442:17 code: 3, metadata: Metadata { _internal_repr: {} } }

And yes, I execute via python 2.7.

Which docker and docker-compose versions are you running?
Docker version 17.04.0-ce, build 4845c56
docker-compose version 1.12.0, build b31ff33

Could you dump the whole output of docker-compose when you start the dual servers and make a request with the client?
Yes, I've done it above. Hope it will help you.

Alright,
the versions look fine, the output is strange as it relates to the dimensions defined for the interface.
Of which both are 4 dimensional for predictEmotion(1,48,48,1) and predictGender(1,48,48,3).
I have added additional logging to the node-server and the client, could please run the following and
send me the output of the docker-compose, as well as the client here again:
cd /keras-prod
git pull
rm -r ./export
python face-recog/export.py
./start-dual-servers.sh
#..
cd face-recog/client
npm start ./../images/cutouts/4.png

This is how should actually look like :/

Here log:
node-server_1     | npm info it worked if it ends with ok
node-server_1     | npm info using<EMAIL_ADDRESS>node-server_1     | npm info using<EMAIL_ADDRESS>node-server_1     | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>node-server_1     | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>node-server_1     |
node-server_1     | ><EMAIL_ADDRESS>start /usr/src/app
node-server_1     | > node server.js
node-server_1     |
node-server_1     | listening @ http://localhost:8080
node-server_1     | Input array size: 2304, example value: 0.9882352941176471.
node-server_1     | Tensor Dim: [{"size":1},{"size":48},{"size":48},{"size":3}].
node-server_1     | Input array size: 2304, example value: 0.9882352941176471.
node-server_1     | Tensor Dim: [{"size":1},{"size":48},{"size":48},{"size":1}].
node-server_1     | emotion prediction failed.
node-server_1     | { Error: input must be 4-dimensional[]
node-server_1     | 	 [[Node: image_array_2/convolution = Conv2D[T=DT_FLOAT, _output_shapes=[[-1,48,48,16]], data_format="NHWC", padding="SAME", strides=[1, 1, 1, 1], use_cudnn_on_gpu=true, _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_image_array_input_2_0_0, image_array_2/kernel/read)]]
node-server_1     |     at /usr/src/app/node_modules/grpc/src/node/src/client.js:442:17 code: 3, metadata: Metadata { _internal_repr: {} } }
node-server_1     | gender prediction failed.

And request:
MBPJ-2:client siarheiparashchanka$ npm start ./../images/cutouts/4.png

><EMAIL_ADDRESS>start /Users/siarheiparashchanka/sites/keras-serving/face-recog/client
> node request.js "./../images/cutouts/4.png"

Reading from path: /Users/siarheiparashchanka/sites/keras-serving/face-recog/images/cutouts/4.png
image flat size: 48.
Loaded image with size: 2304
Making request to CNN GRPC wrapper.
POST to http://localhost:8080/predict-emotion-and-gender with 43601 body length.
{
  "error": {
    "code": 3,
    "metadata": {
      "_internal_repr": {}
    }
  }
}

Strange :/
On which OS are you running this? MacOSX?
I will try to set this up on a clean VM tomorrow, I cannot reproduce this error using Ubuntu 16.04

Okay so I have spun up a clean Ubuntu 16.04 LTS VM and ran through the setup as defined in the READMEs. I have found 2 potential errors regarding the naming of the input vectors of the gender model as well as the output vectors, its possibly related to some strange docker-compose caching behavior that I wasnt able to see these locally.
The bugs are fixed in the current master, so please go ahead and run:
cd /keras-prod
git checkout .
git pull
python ./face-recog/export.py
./start-dual-servers.sh
#..
cd face-recog/client
npm start ./../images/cutouts/4.png

again :)

Cool. Now works!

Awesome :)
Let me know if you want to take this in another direction.
I am currently trying to:

setup a Google Cloud BigQuery large dataset batch-training example
reduce the size of the tf-model-server image, 3,4 GB is way too large
*?

Maybe some preprocessing images. For example, I send big ".jpg" image and it reshapes it and responses with the output of models.
And also maybe more details how to add your own models and make it work.


User agent not set correctly when specifying a base url

Test script:
function main(splash)
  local url = 'http://httpbin.org/headers?nocache=' .. math.random()
  splash:set_user_agent('FooBar/1.0')
  assert(splash:go(url, 'http://httpbin.org'))
  assert(splash:wait(0.5))
  return {
    html = splash:html(),
    png = splash:png(),
    har = splash:har(),
  }
end

Uses Mozilla/5.0 instead of FooBar/1.0.
Specifying the user agent as a header works.

you're right, and it also seems like "accept" header is missing too, looks like no headers are set on request, simple test reproducing this:
https://github.com/pawelmhm/splash/commit/a84c3d7ffbb901f8cb7c3b7d74670c6f36e3a137

Aha! This is because user_agent is set on web_page object and when we pass "base_url" we never load url into webpage but we bypass webpage completely

hey @kmike @Youwotma seems like we dont set UA at all for all manual forms of requests, e.g. if you do splash:http_get() or splash:http_post() request from Splash will not have UA. If you do go() request will have default Splash UA. Should we consider this a bug? By default if you use HTTP API or go() without base url you get UA: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML, like Gecko) splash Safari/538.1" so not having UA in http_get() or http_post() is inconsistency.

I think it makes sense to use default headers in http_get and http_post.

and same for go with base url right? so we should have default UA for all those requests. I'm not sure how websites would handle reqeusts without any UA, perhaps no big deal but could be trouble in some cases?

yeah, right

and did you mean UA or all headers? Because QWebPage also adds "Accept: text/html" header, which is also missing

I think Accept: text/html is not a good default for http_get/http_post. E.g. requests library uses Accept: */* which makes more sense.
Re other header: I think it is fine to use headers set by splash:set_custom_headers in http_get/http_post, but there should be a way to override it just for a single request. Currently we only adding or replacing headers using headers argument; it works because default set of headers is empty.

there should be a way to override it just for a single reques

I see in docs that there is request:set_header(name, value) so that would probably be the way to do it?

would be nice to have some settings where users could set default headers, but I see that https://github.com/scrapinghub/splash/pull/279/files is stalled now, perhaps worth prioritizing it sounds like a really useful PR and lots of work already done


Delete of evalset does not always work

The following request
DELETE
https://foresight.foreai.co/api/eval/set?evalset_id=evalset_20240524_120349
returns a 200, but the evalset does not get deleted

This evalset doesn't exist anymore. Maybe the UI didn't update? Can you check again if it still apears?

It still does not work using the frontend, but it works when using the REST API, e.g.
DELETE https://foresight-gateway.foreai.co/api/eval/set?evalset_id=kings-and-queens

Btw, I experience strange behaviour re browser file upload on Mac OS X, whereas I do not seem to be alone
https://cleanmymac.com/faq/why-wont-mac-upload-files
After updating and restarting Chrome, the browser file upload worked again, at least for the moment.
Let me check again whether this glitch might be connected somehow


Consider passing the configuration to the log_context from config file

with log_context('localhost', 'admin', 'password', 'gpudb', 'gpuseries'):
This exposes username and password in plain text in the code.

Good idea

@msalvaris what is the correct usage after this PR if we want to use the .env ?

@ThomasDelteil  .env file in the same directory as you are executing the cli logger or the logging context and the necessary information will be pulled from it. It uses python-dotenv find_dotenv which will search higher folders in the hierarchy as well (https://github.com/theskumar/python-dotenv/blob/master/dotenv/main.py) Let me know if you run into any issues.


Anyone have this base with imgui?

bro? imgui is open source. just paste it in. lol

https://github.com/VortexShrimp/imgui-csgo-sdk


Openstack simple stress doc

Release of the inital Simple Stress Test Documentation

Markdown link check failures seem to be unrelated to this PR