⚠ Bofrost.de has degraded performance

In abd628d, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1191 ms

Resolved: Bofrost.de performance has improved in 9b1a229.


Importing AWS EC2 resources via Terraformer throws error stating EC2 not supported.

I am new to use this tool to import AWS EC2 resources into terraform state.
I am using the below versions.
Terraform: 1.1.4
Terraformer: v0.8.19
Terraform AWS provider: 4.9.0
OS: Mac ARM64 bit.
When I execute the below command to import AWS EC2 instance, I am receiving this error.
terraformer import aws --resources=ec2 --connect=true --profile=personal
command output:-
2022/04/12 20:31:23 aws importing default region
2022/04/12 20:31:25 aws importing... ec2
2022/04/12 20:31:25 aws error importing ec2, err: aws: ec2 not supported service
2022/04/12 20:31:25 aws Connecting....
I am just wondering if this is a known bug or issue.
Is there a solution for this issue, please do let me know.

I think I have to close this issue, since I was not using the correct syntax for the same.
I again checked the aws docs.
the correct syntax is :- terraformer import aws --resources=ec2_instance --connect=true --profile=personal


Port to  OAuth 2

I'd be interested in other people trying out this branch and see if it makes sense and works as expected.  I was able to do the requests I was doing before with it.
I used it like this:
# Request method
client = LinkedIn::Client.new(ENV["LINKEDIN_API"], ENV["LINKEDIN_SECRET"])
session[:linkedin_state] = SecureRandom.uuid
redirect_to client.authorize_url(redirect_uri: linkedin_auth_callback_url, state: session[:linkedin_state])

# Callback method, should check the state set above on response
client = LinkedIn::Client.new(ENV["LINKEDIN_API"], ENV["LINKEDIN_SECRET"])
token = client.authorize_from_request(params[:code], redirect_uri: linkedin_auth_callback_url)

@hexgnu I can confirm that this PR is working, LinkedIn recently required oauth2 for accessing their company endpoints and this patch got things working. What's the likely hood of this PR being merged and a new gem cut and published?
Thanks,
-- Arron

I can merge this branch and cut a new gem version.  Just need to resolve the conflicts.

Thanks for this PR, I have merged and cut a new version of the gem.

Awesome thanks so much! I had to vender the pr branch to get it all
working, relying on a new gem is going to be much better. Thx a ton! :-)
-- Arron
On August 8, 2018 at 11:43:57 AM, Ryan Resella<EMAIL_ADDRESS>wrote:

Thanks for this PR, I have merged and cut a new version of the gem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hexgnu/linkedin/pull/247#issuecomment-411492085, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAH1Kp3dv6tND0ysYWRyJIOqSIsSvK0vks5uOyNdgaJpZM4CycGI
.

Thanks @ryanatwork


feat: introduce new CRD ComputeNode

Type of change:

[ ] Bugfix
[x] New feature provided
[ ] Improve performance
[ ] Backport patches

What this PR does / why we need it:

refers to #166
Pre-submission checklist:

[x] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?

Codecov Report

Merging #181 (129e159) into main (46be6a7) will decrease coverage by 11.23%.
The diff coverage is 50.69%.

@@             Coverage Diff             @@
##             main     #181       +/-   ##
===========================================
- Coverage   62.36%   51.12%   -11.24%
===========================================
  Files           2        7        +5
  Lines         279      755      +476
===========================================
+ Hits          174      386      +212
- Misses        103      353      +250
- Partials        2       16       +14

Impacted Files
Coverage Δ

...hardingsphere-operator/pkg/reconcile/deployment.go
0.00% <0.00%> (ø)

shardingsphere-operator/pkg/reconcile/resource.go
25.00% <0.00%> (-35.08%)
:arrow_down:

shardingsphere-operator/pkg/reconcile/configmap.go
4.00% <4.00%> (ø)

shardingsphere-operator/pkg/reconcile/hpa.go
38.23% <38.23%> (ø)

shardingsphere-operator/pkg/reconcile/service.go
43.95% <43.95%> (ø)

...gsphere-operator/pkg/reconcile/deployment_proxy.go
84.61% <84.61%> (ø)

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


Bug: Share Link in http not https

Hi there,
The server is configured on the app as https:// but the share links  are always in http://

@x011 on the server, in the config, did you by any chance write http:// as the URL ?

As @licaon-kter said, this would be caused by public_url starting with http instead of https in the server-side config. Please double check your config and re-open this issue if the problem persists.


INT B-19474 approvals requested or approved move status check issue

Agility ticket
Summary
When the TOO has actions they need to take (approve a shipment, review destination address request, etc), the move status should be APPROVALS_REQUESTED instead of APPROVED. Now once the TOO has completed those actions, we want to move the status back to APPROVED as well to reflect that those actions have been taken.
There was an issue created that addressed this and this BL item and PR was a lot of analysis and essentially expanding and adding in the function ApproveOrRequestApproval into service objects that are used when the TOO performs an action.
The following actions that a TOO can perform were assessed/updated to ensure that the move status was being checked on completion of the action:
MOVE

update billed weight amount (excess weight alert)
approve/reject sit extension
SIT extension approve/reject

ORDERS

updating orders
updating allowances

SHIPMENT

approve shipment
delete shipment
approving diversions
address update request/review

SERVICE ITEM

SI creation
SI approve/reject

NOTE
Right now there is a BL item in process to fix an issue with a flag persisting on the MTO page (this seems to be related to excess weight & SIT data): https://www13.v1host.com/USTRANSCOM38/assetdetail.v1?number=B-19178
So there might be a situation where you aren't able to successfully test if it falls within that specific issue.
How to test

Access MM as a TOO
Find a move that has a status of Approvals Requested
Complete any items that need review
Ensure that the move status changes back to Approved in the queue following completion of the actions

There seems to be a test failing for playwright, not sure why and this PR didn't touch any of that code. Locally I can reproduce and here's the error I get:
2024-04-11T14:42:17.071Z        ERROR   ppmshipment/ppm_estimator.go:293        could not calculate param value lookup  {"git_branch": "INT-B-19474-approvals-requested-or-approved-move-status-check-issue", "git_commit": "e3052448cd3e3caf15c26fe79e5977f3c72bceea", "host": "officelocal:3000", "milmove_trace_id": "eb78ee43-248a-4ad7-ad93-a4a86722dbfa", "session_id": "GzsnsLiM7Y-NrXAjbxrfvmlNtAJLVmoELwMuE2f2SRY", "error": " failed ServiceParamValue DistanceZipLookup with error invalid distance using pickup 84022 and destination 38649"}
github.com/transcom/mymove/pkg/services/ppmshipment.estimatePPM.calculatePrice

2024-04-11T14:42:17.071Z        ERROR   ghcapi/mto_shipment.go:141      ghcapi.CreateMTOShipmentHandler error   {"git_branch": "INT-B-19474-approvals-requested-or-approved-move-status-check-issue", "git_commit": "e3052448cd3e3caf15c26fe79e5977f3c72bceea", "host": "officelocal:3000", "milmove_trace_id": "eb78ee43-248a-4ad7-ad93-a4a86722dbfa", "session_id": "GzsnsLiM7Y-NrXAjbxrfvmlNtAJLVmoELwMuE2f2SRY", "error": " failed ServiceParamValue DistanceZipLookup with error invalid distance using pickup 84022 and destination 38649"}

Passing now suckas

Looking good so far as far as actions the TOO takes moving it back the Approved state!
Reading through the story description, it says "Expected Behavior: A move with a status of "Approvals Requested" should have an item to review in the MTO page and should not erroneously display a status of "Approvals Requested" if there is nothing to review."
I do still see that behavior - for REWAYD for example, appears as Approvals requested but there is no action to take as the TOO. Maybe since that's a pre-existing move after a db refresh, it's not an issue and your changes will apply to all new moves. Thoughts?

Changes will apply to all new moves. There's no way to go back and retroactively change all of those statuses without doing a loop when listing all of the moves, but that just seems like unnecessary and might impact performance.
For now you can just update the orders without changing anything and that should do it.

For now you can just update the orders without changing anything and that should do it.

Yep updating orders works. Not sure if it's mentioning to users that it will only be for new moves, as they might get confused on why they still see moves without action to take after your fix goes in.

For now you can just update the orders without changing anything and that should do it.

Yep updating orders works. Not sure if it's mentioning to users that it will only be for new moves, as they might get confused on why they still see moves without action to take after your fix goes in.

I mentioned to Danny about calling the function when the TOO fetches the move, but he didn't want it. So... It's a check that is reactionary and not a proactive call at this time.

For now you can just update the orders without changing anything and that should do it.

Yep updating orders works. Not sure if it's mentioning to users that it will only be for new moves, as they might get confused on why they still see moves without action to take after your fix goes in.

I mentioned to Danny about calling the function when the TOO fetches the move, but he didn't want it. So... It's a check that is reactionary and not a proactive call at this time.

Alright, bases covered then! Good by me

Possible issue here:
WTSTAT has two shipments to approve so it's in Approvals Requested status.

I approve and send both shipments.

I now see an action to take on the MTO page, reviewing billable weight:

However, the move is already in the Move approved state while still having an action to take on the MTO page so the TOO doesn't really know they have something to approve if looking at their move queue:

This WTSTAT test can be duplicated with db_dev_fresh.
You could make the argument that the TOO should see the things to review on the MTO page and take care of them, but the issue is that the status of the move does not reflect that there are still items needing review. The TOO could close the browser or somehow not see that MTO page and those things requiring review might get lost

Just checked and also see this in main so... going to ignore this!


Feature: Consistent the order same line-length entities

What rule do you want to change?
sort-named-imports,sort-jsx-props
Describe the problem
Be enabling line-length for sort-name-imports/sort-jsx-props (and others), the same length entities can be re-order after some code manipulations.
Code example
E.g: I have
import { all, put, call, select } from "typed-redux-saga";
After remove the statement containg all and put functions, then revert the deletion, then re-import in order put then all. So the import statement becomes:
import { put, all, call, select } from "typed-redux-saga";
which is a unnecessary change.
Additional comments
Plugin version v2.1.0
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

I am currently unable to reproduce your problem. Can you tell me how I can do this?


UNR-1375: Delete existing generated schema files when doing a full scan.

Description
Running schema generator in full scan should first delete all existing schema files. This prevents schema files for deleted actors from colliding with regenerated ones.
Release note
Bugfix: Running Schema (Full Scan) now clears generated schema files first.

Closing as obsolete. Need finer control of what to delete when.


Add template header rendering

new markup language feature that handles rendering of template title openlawteam/openlaw#1237

Added "Title" section that covers this.


Can't use --force compilerOptions when build is set to true

First of all, this is a great plugin, appreciate the work!
Current behavior
We are setting build: true in order to leverage project references(which is working as expected). Furthermore, we want to skip the cache and force the build when building for production. I tried to add --force option to compilerOptions, but then it complains about TS5093: Compiler option '--verbose' may only be used with '--build'. Adding the build option to compilerOptions again doesn't seem to do anything either.
Expected behavior
That I can use compiler options like --force --verbose when build: true is set.
Or some workarounds that can avoid reusing the tsconfig.tsbuildinfo cache, thanks!
Steps to reproduce the issue
Set up the plugin with config as following:
var forkTsCheckerPlugin = new ForkTsCheckerWebpackPlugin({
  typescript: {
    build: true,
    configOverwrite: {
      compilerOptions: {
        force: true,
      },
    }
  }
});

Issue reproduction repository

Environment

fork-ts-checker-webpack-plugin: 7.2.13
typescript: 4.8.4
eslint: 8.24.0
webpack: 5.74.0
os: macOS 12.6

Hi! According to tsconfig.json documentation these is no such option as force. You can use it with CLI, but not with config file. Therefore, having support for force flag is a feature request - not a bug :)


html output

I get the following output in Python console when running qs.reports.html(stock, "SPY"):
<IPython.core.display.HTML object>
How can I generate your statistics in an html file?

Need to put in an output location:
qs.reports.html(stock, "SPY",output='test.html')

Thanks a lot for your response. This was very helpful.
In general, this library has been a lifesaver.
On Fri, Jun 18, 2021 at 11:21 PM damienklassen @.***>
wrote:

Need to put in an output location:
qs.reports.html(stock, "SPY",output='test.html')
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ranaroussi/quantstats/issues/102#issuecomment-864347875,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDGVET4THNE3C5ITFU2VW3TTQEM7ANCNFSM447X3DEQ
.

Once the html file has been created how can I open it in a Jupyter Notebook? thank you.

When I use:
qs.reports.html(stock, "SPY", title='Strategy Tearsheet', download_filename='test.html',figfmt='svg', output=True)
I see the html in terminal window, but it doesnt appear to get written as a file anywhere. There are no errors. Please can you advisor how I get html file written?


Issue-459: remove old FAQ and fix any links

Pull Request Template
Description
Removed FAQ page, FAQ posts, and updated URL in _config.yml to point to the new FAQ.
Fixes #459
Type of change
Please delete options that are not relevant.

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

...
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] I have tagged the reviewers in a comment below incase my pull request is ready for a review
[x] I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

@Rene-Ch1 or @johnwalicki
I searched for "faq" in all the pages and ensured that the old URL is no longer found.  No links should break when this is merged.


Alphabetize Contibuter List in README

Right now the list is not in any particular order. Would be better if it was sorted, alphabetically, or otherwise.

Just pulled a request on that. Hope it's ok. Thank you.


Nesting components

This is really a wonderful package. I just love it. Makes my life so much easier.
I was wondering if you could agree with the following : it would be nice to have the ability to nest components and use their inner_block slots "normally". At the present moment, that generates a recursion error.
Here is an example
`component1 :

  {% render_slot slots.inner_block %}

`
`component2 :
{% component1 %}
Some dummy content I would like to show
  {% render_slot slots.inner_block %}
{% endcomponent1 %}`

Hello,
A simple solution to this is to capture the slot into a variable before entering the component1 block, e.g.:
{% with inner_block=slots.inner_block %}
    {% component1 %}
        Some dummy content I would like to show

        {% render_slot inner_block %}
    {% endcomponent1 %}
{% endwith %}


Create list of links on FreeBMD2 where we sould advise opening in a new tab.

Discuss multimodal instances on a new story on Systemwide.
Note FreeBMD specific links to open on a new page here:
-[ ] Report a data problem

Maybe not quite on-topic, but the 'Printable format' link in the Tools drop-down should open in a new tab, since the resulting page lacks any navigation controls.

@richardofsussex Good point — we would have to notify all users that this will happen (accessibility requirement).
Opening in a new tab does not happen on other sites for the equivalent page AFAIK.


Standardise italics

Added a new custom jinja2 tag for parsing and formatting specimen taxonomy - can be added to other templates as necessary
closes #266

The italics look correct to me. If possible removed the italic formatting on the filed as name. May be worthwhile getting some additional testing by one of the botanists.


Option to reverse playlist order

Playing let's plays is a great way for me to wind down but unless they provide a correctly ordered playlist for me to watch the uploaded videos playlist goes in reverse!
It would be great if there was a simple checkbox in the playlist combo selector to reverse the order in which videos will be queued!

What is the progress/prospect of this happening at the moment? And which of these is the 'official' request?:
#104
#396
#955

*subtly pointing at labels*


Fix Typo in readme.md

Nothing big, just a Typo

Hi @timschoch, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thx Tim, even small things do matter, but this was targeted to master branch, not to dev branch. If you do not mind, could you target this it dev, since we do take all changes only to dev side and then do master merge during monthly releases.
It's not a big change and happy to do this quickly personally as well, but since this PR does already exist, did not want to steal this edit - small one, but even small things do matter.


Test istio pipeline

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test all

/test all


Permission denied

Using MacOs
Command used to install:
docker run -h spfx -it --rm --name ${PWD##*/} -v $PWD:/usr/app/spfx -p 5432:5432 -p 4321:4321 -p 35729:35729 waldekm/spfx
Let's create a new SharePoint solution.
? What is your solution name? spfx
? Where do you want to place the files? Use the current folder
? What is your webpart name? HelloWorld
? What is your webpart description? HelloWorld description
? What framework would you like to start with? React
create package.json
fs.js:640
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: EACCES: permission denied, open '/usr/app/spfx/package.json'
at Error (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.writeFileSync (fs.js:1333:33)
at write (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/mem-fs-editor/lib/actions/commit.js:14:6)
at DestroyableTransform._transform (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/mem-fs-editor/lib/actions/commit.js:43:7)
at DestroyableTransform.Transform._read (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/readable-stream/lib/_stream_transform.js:159:10)
at DestroyableTransform.Transform._write (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/readable-stream/lib/_stream_transform.js:147:83)
at doWrite (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/readable-stream/lib/_stream_writable.js:347:64)
at writeOrBuffer (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/readable-stream/lib/_stream_writable.js:336:5)
at DestroyableTransform.Writable.write (/usr/local/lib/node_modules/@microsoft/generator-sharepoint/node_modules/readable-stream/lib/_stream_writable.js:274:11)
spfx@spfx:/usr/app/spfx$

Have you shared the directory mapped in the volume in Docker's settings?

I'm having the same issue on Windows.
Docker for Windows version <IP_ADDRESS> using the latest docker image.

same issue here

OS: Windows 10
Docker Desktop v3.5.2 setting > General > Use the WLS 2 based engine  is ticked
Using Windows Terminal  which has been running as administrator, I ran this command in a Ubuntu terminal:
docker run -it --rm --name ${PWD##*/} -v $PWD:/usr/app/spfx -p 5432:5432 -p 4321:4321 -p 35729:35729 waldekm/spfx:1.4.1
And then after running the container, using this command: npm -g ls -depth=0 checked it, but got this error:
npm ERR! invalid<EMAIL_ADDRESS>/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib

After running gulp serve I got this error:
[10:06:01] Error - 'copy-static-assets' sub task errored after 14 s
EPERM: operation not permitted, chmod '/usr/app/spfx/lib/webparts/scriptEditor/ScriptEditorWebPart.manifest.json'
{ Error: EPERM: operation not permitted, chmod '/usr/app/spfx/lib/webparts/scriptEditor/components/ScriptEditor.module.css'
errno: -1,
code: 'EPERM',
syscall: 'chmod',
path: '/usr/app/spfx/lib/webparts/scriptEditor/components/ScriptEditor.module.css' }
[10:06:01] Error - Unknown
EPERM: operation not permitted, chmod '/usr/app/spfx/lib/webparts/scriptEditor/components/ScriptEditor.module.css'
{ Error: EPERM: operation not permitted, chmod '/usr/app/spfx/src/webparts/scriptEditor/components/ScriptEditor.module.scss.ts'
errno: -1,
code: 'EPERM',
syscall: 'chmod',
path: '/usr/app/spfx/src/webparts/scriptEditor/components/ScriptEditor.module.scss.ts' }
[10:06:01] Error - Unknown
EPERM: operation not permitted, chmod '/usr/app/spfx/src/webparts/scriptEditor/components/ScriptEditor.module.scss.ts'
[10:06:01] ==================[ Finished ]==================
Warning - [spfx-serve] When serving in HTTPS mode, a PFX cert path or a cert path and a key path must be provided, or a dev certificate must be generated and trusted. If a SSL certificate isn't provided, a default, self-signed certificate will be used. Expect browser security warnings.
Error - 'copy-static-assets' sub task errored after 14 s
EPERM: operation not permitted, chmod '/usr/app/spfx/lib/webparts/scriptEditor/ScriptEditorWebPart.manifest.json'
Error - Unknown
EPERM: operation not permitted, chmod '/usr/app/spfx/lib/webparts/scriptEditor/components/ScriptEditor.module.css'
Error - Unknown
EPERM: operation not permitted, chmod '/usr/app/spfx/src/webparts/scriptEditor/components/ScriptEditor.module.scss.ts'
[10:06:02] Project pnp-script-editor version: 1.0.0
[10:06:02] Build tools version: 3.2.7
[10:06:02] Node version: v8.9.4
[10:06:02] Total duration: 1.33 min
[10:06:02] Task warnings: 1
[10:06:02] Task errors: 5
[10:06:02] Error - 'undefined' errored after
"orchestration aborted"
[10:06:02] Error - 'undefined' errored after
"orchestration aborted"

And finaly in browser I get this error:
manifests.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
sp-loader-assembly_en-us.js:16841 Beacon: To disable logging to the console set "window.disableBeaconLogToConsole = true" in the debug window
sp-loader-assembly_en-us.js:20952 Beacon: To disable logging to the console set "window.disableBeaconLogToConsole = true" in the debug window
workbenchInit.js:8 Uncaught TypeError: Cannot read property 'getManifests' of undefined
at workbenchInit.js:8
sp-loader-assembly_en-us.js:5428 Uncaught (in promise) Error: ***Invalid preloaded data.
at sp-loader-assembly_en-us.js:5428
DevTools failed to load source map: Could not load content for https://localhost:4321/node_modules/<EMAIL_ADDRESS>HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Dependencies are not a part of the container. Could it be that there was a network issue or an issue with npm that would lead to the issue with minizlib you mentioned? Have you tried restoring the dependencies again?

First, Thank you for the quick response.
Then, I tried to install npm again through npm -g i<EMAIL_ADDRESS>I got this error:
npm WARN notice [SECURITY] npm has the following vulnerabilities: 4 low. Go here for more details: https://www.npmjs.com/advisories?search=npm&version=5.6.0 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules/npm
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules/npm/node_modules/tar/node_modules
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! path /usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib'
npm ERR!  { Error: EACCES: permission denied, access '/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib'
npm ERR!   stack: 'Error: EACCES: permission denied, access '/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/minizlib' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/spfx/.npm/_logs/2021-07-12T14_05_30_402Z-debug.log

Today: >
From in the docker container:
git clone https://github.com/pnp/sp-dev-fx-webparts.git
I got this error:
fatal: could not create work tree dir 'sp-dev-fx-webparts'.: Permission denied

Have you granted Docker write access to the local folder you mounted as volume for the container?

As far as I know, to make a read-only volume, we shall use ":ro" at the end of the path string (after "-v" switch), which obviously we didn't! I assume otherwise, Docker should have write access by default. But I am not sure how can I check it.
Besides, I am not sure if grant write access to the folder -in which volume is nested- is different from write access to the volume itself or not.
I even tried to make using id=1000 for the inner user - in this case "spfx" - (same as the user who ran docker), but no different.
Still, the problem persists. I appreciate your help in forward.

In Docker desktop settings, have you included the path that you're mounting the volume to in the file sharing options under Preferences > Resources > File sharing?

Since I had started Docker with wls 2, there was no "File sharing" option under the Resources. (
But even though, to see the result, I unchecked General > Use the WSL 2 based engine and restarted docker. Then I added this address: "c:\users\administrator" to File sharing. but again I got exactly same Error.

I had a similar issue:
spfx@25d1b387f069:/usr/app/spfx$ gulp serve --nobrowser
Build target: DEBUG
[10:39:46] Using gulpfile /usr/app/spfx/gulpfile.js
[10:39:46] Starting 'serve'...
[10:39:46] Starting gulp
[10:39:46] Starting subtask 'spfx-serve'...
[10:39:46] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js
[10:39:46] Starting server...
[10:39:46] Finished subtask 'spfx-serve' after 61 ms
[10:39:46] Starting subtask 'pre-copy'...
[10:39:46] Finished subtask 'pre-copy' after 15 ms
[10:39:46] Starting subtask 'copy-static-assets'...
[10:39:46] Starting subtask 'sass'...
[10:39:46] Server started https://localhost:4321
[10:39:46] LiveReload started on port 35729
[10:39:46] Running server
[10:39:46] Error - 'sass' sub task errored after 464 ms
 EACCES: permission denied, open '/usr/app/spfx/src/webparts/secretGenerator/components/SecretGenerator.module.scss.ts'
[10:39:48] Finished subtask 'copy-static-assets' after 2.05 s
^C[10:40:38] Server stopped
[10:40:38] The following tasks did not complete: serve
[10:40:38] Did you forget to signal async completion?
About to exit with code: 0
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1

I solved it via running sudo chown -R 1001:1001 in the solution directory.
I actually was very confused and spent quite a lot of hours on troubleshooting because this file src/webparts/secretGenerator/components/SecretGenerator.module.scss.ts in fact does not exist, So the problem I had was not in the specific file but in the permissions to the whole src directory

@shurick81 in which solution directory did you run sudo chown -R 1001:1001 . ?

cd <project directory>
sudo chown -R 1001:1001 .


Rename Get{Block/Append/Page}BlobClient -> As{Block/Append/Page}BlobC…

…lient

/azp run

@vhvb1989 code coverage tool causes CI to fail, can you take a look?

@vhvb1989 code coverage tool causes CI to fail, can you take a look?

Well, when you did /azp run you asked for all pipelines to be run (not only storage).
There is actually a bug for the live test code cov generation for core and template project, I will fix that, but it should not block you for this PR (not Storage Live test passed)


Client stops delivering any output

I am starting with Kaldi-Gstreamer-Server and trying out some MP3 Ted talks with different models and I am getting to the point (if the recording is longer then ~1 min), that the client stops delivering any output.
Here is the output from the worker, which I am getting on the beginning
2019-03-06 15:10:23 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Postprocessing done.
2019-03-06 15:10:23 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:10:23 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:10:23 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:10:23 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Got partial result: IT'S SO TO SPEAK OF DINNER PARTIES I WANTED TAKE YOU BACK TO TWO THOUSAND FIFTEEN AND A DINNER PARTY THAT I WENT TO IT PLACES IN TIME THIS WAS WHEN KATE WHEN JENNER WAS FIRST COMING OUT SHEDDING HER IDENTITY ZACHAR DASH IN AND MOVING INTO HER LIFE AS A TRENCH UNDER

but then it gets into:
2019-03-06 15:11:04 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Postprocessing (final=False) result..
2019-03-06 15:11:04 -   DEBUG:       root: 99e23dd3-973f-4333-b116-49547707b3a8: Skipping postprocessing since post-processor already in use
2019-03-06 15:11:04 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:04 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:04 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:04 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Got partial result: UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND
2019-03-06 15:11:04 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:04 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:04 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:04 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:04 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:04 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:04 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:04 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Got final result: UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND
2019-03-06 15:11:04 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Got full final result: {"status": 0, "result": {"final": true, "hypotheses": [{"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 456.134}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR HAD IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 456.105}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 456.027}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR HAND IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 456.023}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER HAD IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 455.997}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER HAND IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 455.915}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR HAND IT IS SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 455.689}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAVEMEN JENNER ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 455.689}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAVEMEN JENNER HAD IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 455.659}, {"transcript": "UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER HAND IT IS SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND", "likelihood": 455.582}]}, "segment-start": 82.63, "segment-length": 20.0, "total-length": 102.63}
2019-03-06 15:11:04 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Before postprocessing: {u'status': 0, u'segment-start': 82.63, u'segment-length': 20.0, u'total-length': 102.63, u'result': {u'hypotheses': [{u'likelihood': 456.134, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 456.105, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR HAD IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 456.027, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 456.023, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR HAND IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 455.997, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER HAD IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 455.915, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER HAND IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 455.689, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME AGENOR HAND IT IS SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 455.689, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAVEMEN JENNER ADDED SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 455.659, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAVEMEN JENNER HAD IT SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}, {u'likelihood': 455.582, u'transcript': u'UNDER FULL FIND WHEN MY HOST GOES ON A RANT ABOUT CAME ENGENDER HAND IT IS SHE IS SAYING THAT IT IS DISRESPECTFUL FOR CONGENER TO FORCE HER TO USE A NEW NAME AND TO USE THESE NEW PRONOUNS HUT SNATCHED UP ONE OF THEM AND LISTENING AND'}], u'final': True}, 'segment': 6, 'id': u'99e23dd3-973f-4333-b116-49547707b3a8'}
2019-03-06 15:11:05 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:05 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:05 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:05 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:05 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:05 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:06 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:06 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:06 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:06 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:06 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:06 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:07 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:07 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:07 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:07 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:07 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:07 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:08 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:08 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:08 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:08 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:08 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:08 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:09 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:09 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:09 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:09 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:09 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:09 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:10 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:10 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:10 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:10 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:10 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:10 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:11 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:11 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:11 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:11 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:11 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:11 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:12 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:12 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:12 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:12 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:12 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:12 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:13 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:13 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:13 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:13 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:13 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:13 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:14 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:14 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:14 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Checking that decoder hasn't been silent for more than 10 seconds
2019-03-06 15:11:14 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:14 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:14 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:15 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:15 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:15 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:15 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:15 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer of size 6144 to pipeline
2019-03-06 15:11:15 -   DEBUG:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Pushing buffer done
2019-03-06 15:11:15 - WARNING:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: More than 10 seconds from last decoder hypothesis update, cancelling
2019-03-06 15:11:15 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Master disconnected before decoder reached EOS?
2019-03-06 15:11:15 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Sending EOS to pipeline in order to cancel processing
2019-03-06 15:11:15 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Cancelled pipeline
2019-03-06 15:11:15 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Waiting for EOS from decoder
2019-03-06 15:11:15 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:15 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:15 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:15 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:16 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:16 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:16 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:16 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:16 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Waiting for EOS from decoder
2019-03-06 15:11:16 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:16 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:16 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:16 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:17 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:17 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:17 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:17 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:17 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Waiting for EOS from decoder
2019-03-06 15:11:17 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:17 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:17 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:17 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:18 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:18 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:18 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:18 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8

and finaly the only output is
2019-03-06 15:11:44 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:44 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Waiting for EOS from decoder
2019-03-06 15:11:44 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:44 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:45 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:45 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8

or later
2019-03-06 15:11:46 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:46 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 100
2019-03-06 15:11:46 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:46 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 100
2019-03-06 15:11:46 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:46 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 100
2019-03-06 15:11:46 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:46 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 100

With the transition between both:
2019-03-06 15:11:45 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:45 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:45 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:45 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:45 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 8
2019-03-06 15:11:45 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Giving up waiting after 31 tries
2019-03-06 15:11:45 -    INFO:   decoder2: 99e23dd3-973f-4333-b116-49547707b3a8: Resetting decoder state
2019-03-06 15:11:45 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:45 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 100
2019-03-06 15:11:46 -   DEBUG:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Got message from server of type <class 'ws4py.messaging.BinaryMessage'>
2019-03-06 15:11:46 -    INFO:   __main__: 99e23dd3-973f-4333-b116-49547707b3a8: Ignoring data, worker already in state 100

and the master output at the end in this endless loop is:
    INFO 2019-03-06 15:10:50,170 99e23dd3-973f-4333-b116-49547707b3a8: Forwarding client message (<type 'str'>) of length 6144 to worker
    INFO 2019-03-06 15:10:50,422 99e23dd3-973f-4333-b116-49547707b3a8: Forwarding client message (<type 'str'>) of length 6144 to worker
    INFO 2019-03-06 15:10:50,675 99e23dd3-973f-4333-b116-49547707b3a8: Forwarding client message (<type 'str'>) of length 6144 to worker
    INFO 2019-03-06 15:10:50,928 99e23dd3-973f-4333-b116-49547707b3a8: Forwarding client message (<type 'str'>) of length 6144 to worker
    INFO 2019-03-06 15:10:51,181 99e23dd3-973f-4333-b116-49547707b3a8: Forwarding client message (<type 'str'>) of length 6144 to worker
    INFO 2019-03-06 15:10:51,434 99e23dd3-973f-4333-b116-49547707b3a8: Forwarding client message (<type 'str'>) of length 6144 to worker

And it goes like this forever and it happens for every configuration file which I tested.
The model configuration file, which I am using in this case is the default librispeech_english_nnet2.yaml.
For the debugging purpose I am starting the elements in the following way:
python kaldigstserver/worker.py -u ws://localhost:8888/worker/ws/speech -c librispeech_english_nnet2.yaml
python kaldigstserver/master_server.py --port=8888
python kaldigstserver/client.py -r <bitrate> <data_file>

Every command executed in separate terminal of course.
I tried also the Docker image to avoid this problem, but there I wasn't able to start the worker for some reason, so I am trying to concentrate on this installation.
I will be thankful for any help! If I should provide anything more to investigate this, I will be happy to do so.

I suggest to start with disabling the post processing (comment out the lines at the yaml file), and report if you see any change.

That's how easy it was, thank you! This line is every yaml configuration file.
Would be nice if someone could mention this issue in the README file :)

I struggled with this myself. It seems that the postprocessor mechanism doesn't work with Tornado 5. It works with Tornado 4.5.3.

Is it then worth downgrading to Tornado 4.5.3 and leave postprocessor running?

It depends whether you need the post-processor. Post-processor is required only when you need to rewrite recognition results somehow (it's application specific).

Thank you for your input!


Default ignore can be accidentally overridden in packagerConfig

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.0.5
Electron version
v22.2.0
Operating system
macOS 13.4.1
Last known working Electron Forge version
No response
Expected behavior
Specifying an ignore option in packagerConfig should not replace any default options (unless the ignore option is a function, as per electron-packager's standard behaviour).
Actual behavior
If ignore is not specified in packagerConfig, then it defaults to [/^\/out\//g]. Setting ignore to any other value silently overrides this default.
As a consequence of this, the packager fails to remove the out directory.
For me, this results in the following crash:
An unhandled rejection has occurred inside Forge:
Error: Detected file "Contents/Resources/app/out/<MY APP>-darwin-arm64/<MY APP>.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework" that's the same in both x64 and arm64 builds and not covered by the x64ArchFiles rule: "undefined"
at exports.makeUniversalApp (<APP ROOT>/node_modules/@electron/universal/dist/cjs/index.js:101:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async packageUniversalMac (<APP ROOT>/node_modules/electron-packager/src/universal.js:56:3)
    at async Promise.all (index 0)
    at async packager (<APP ROOT>/node_modules/electron-packager/src/index.js:204:20)

Steps to reproduce
I'm testing this by placing a console.log(opts.ignore) statement at the top of the userPathFilter function in node_modules/electron-packager/src/copy-filter.js.
Additional information
No response

Indeed ran into this today as well, thanks for the report!


Update gcloud cluster setup to use GKE

https://docs.pachyderm.com/latest/contributing/gcloud-setup/
This doc needs to be updated to use GKE rather than a single VM

Can this issue be closed @chainlink ?

Yep. These instructions are old and shouldn't be used anymore

I believe this issue should not be closed as the contribution guide still show gcloud and not gke.

I believe this issue should not be closed as the contribution guide still show gcloud and not gke.

https://pachyderm.atlassian.net/browse/DOC-135


Update Nix derivations for new test suite

@jwiegley this should work!

etlas still fails to build:
builder for '/nix/store/cdm8ccbp6fspwjmws4my4hlsrvrb4hzb-etlas-<IP_ADDRESS>.drv' failed with exit code 1; last 10 log lines:
  ignoring (possibly broken) abi-depends field for packages
  ignoring (possibly broken) abi-depends field for packages
  unpacking sources
  unpacking source archive /nix/store/zgfpviyzqcx8r8yzg3qz25zxisp5h0m3-etlas
  source root is etlas
  patching sources
  compileBuildDriverPhase
  setupCompileFlags: -package-db=/private/tmp/nix-build-etlas-<IP_ADDRESS>.drv-0/setup-package.conf.d -j1 -threaded -hide-package=etlas-cabal
  <command line>: cannot satisfy -hide-package etlas-cabal
      (use -v for more information)

@jwiegley I have a feeling you have an outdated submodule, maybe.

@puffnfresh That may be it. I'll merge this for now. @jwiegley If you still get problems after doing git submodule update --init --recursive, feel free to file a new issue.

Note that I have git config --global submodule.recurse true set, so I always update submodules on a pull.  This is what I see:
git pull
remote: Counting objects: 700, done.
remote: Compressing objects: 100% (396/396), done.
remote: Total 700 (delta 308), reused 688 (delta 297), pack-reused 0
Receiving objects: 100% (700/700), 89.94 KiB | 1.45 MiB/s, done.
Resolving deltas: 100% (308/308), completed with 44 local objects.
From github.com:puffnfresh/ghcvm
 * branch              nix/fixes  -> FETCH_HEAD
Fetching submodule codec-jvm
Fetching submodule etlas
From https://github.com/typelead/etlas
   b69d186..0ae4612  master                            -> origin/master
 * [new branch]      revert-52-long-path-fix           -> origin/revert-52-long-path-fix
 * [new branch]      revert-53-revert-52-long-path-fix -> origin/revert-53-revert-52-long-path-fix
Fetching submodule etlas/hackage-security
fatal: bad object<PHONE_NUMBER>000000000000000000000000000000

Other than that oddness, the build works now!


Mono compiler missing permissions or env variables

Mono compiler may not have execution permissions by the operating system. I believe this is caused by the msc.bat file using path variables, which requires mono be installed on the system. Since the engine packages and distributes mono for windows with the engine itself, it is not a requirement for mono to be installed on the system.
https://github.com/ttalexander2/chroma/blob/33a2f814ea248578ebd089508d400ea70b0f53b7/Polychrome/src/Build.cpp#L27
This results in the c# scripts not being built into the dll, which will crash the engine on play.

Additionally, the play button should be disabled if the c# scripts were unable to build for any reason.


[Feature] Add Number System Calculator

Description
This calculator is used to convert the Decimal, octal, hexadecimal and octal numbers and vice versa.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 I have made the pull requests to my recent 2 issues. Please verify those and merge if it's all correct. 😊

We already have Number System Calculator, pls create new issues, or you can check up-for-grab issues to work @Yuvraj960

@Rakesh9100 I have commented to 4 up-for-grab issues. Please assign those all to me, as I can complete 2-3 issues in one day only. I want to contribute more and more in open source with a fast pace so please help me by assigning those issues. I am sure you will like all the PRs I make in those PRs


Add E variable in v3 as it was in v2

Hello,
I had a template using V2, that sort of had this
const etaConfig = {
  async: true,
  autoEscape: false,
  views: __dirname + '/../reports',
  functions: {
    require: require
  },
};

....
const eta = new Eta(etaConfig);
....
eta.render(template, {})

And then I could use the following in the template
<%
mod = E.functions.require("....");
...

That no longer seems to work. I get an exception
ReferenceError: E is not defined
Is there some other way to access the configuration in the templates?
Tx!
Peter

@petercoppensdatylon I love the creativity of this usage! I'd recommend something like the following.
First, extend the Eta class:
const functions = {
	require: require
}

export class NewEta extends Eta {
  functions = functions;
}

Then create a new instance using functionHeader:
const eta = new NewEta({ functionHeader: "const functions = this.functions" })

Inside your template, you'll then be able to write functions.require("...").
Let me know how this works for you!

Hello,
Thanks for this tip. Really appreciate it. I first worked around it by passing in the functions through the render parameters, but I changed it using your suggestion. I like it better.
Best,
Peter