Yarn fails to compile when Sage project created with Tailwind selected. PostCSS Loader has been initialized using an options object that does not match the API schema.

[X] I've read the guidelines for Contributing to Roots Projects
[X] This request isn't a duplicate of an existing issue
[X] I've read the docs and followed them (if applicable)
[X] This is not a personal support request that should be posted on the Roots Discourse community

Description
Yarn fails to compile when Sage project created with Tailwind selected. PostCSS error:
Module build failed: ModuleBuildError: Module build failed: ValidationError: Invalid options object. PostCSS Loader has been initialized using an options object that does not match the API schema.
Steps to reproduce

Create sage project composer create-project roots/sage
Select tailwind when installing
yarn && yarn build

Expected behavior: [What you expect to happen]
Yarn compiles succesfully
Actual behavior: [What actually happens]
ERROR  Failed to compile with 2 errors                                                                                12:13:34 pm
error  in ./resources/assets/styles/main.scss
Module build failed: ModuleBuildError: Module build failed: ValidationError: Invalid options object. PostCSS Loader has been initialized using an options object that does not match the API schema.

options has an unknown property 'plugins'. These properties are valid:
object { postcssOptions?, execute?, sourceMap? }
at validate (/home/dave/web/spp/web/app/themes/spp/node_modules/schema-utils/dist/validate.js:104:11)
at Object.loader (/home/dave/web/spp/web/app/themes/spp/node_modules/postcss-loader/dist/index.js:43:29)
at /home/dave/web/spp/web/app/themes/spp/node_modules/webpack/lib/NormalModule.js:195:19
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:233:18

@ multi ./scripts/main.js ./styles/main.scss
error  in ./resources/assets/styles/main.scss
Module build failed: ModuleBuildError: Module build failed: ValidationError: Invalid options object. PostCSS Loader has been initialized using an options object that does not match the API schema.

options has an unknown property 'plugins'. These properties are valid:
object { postcssOptions?, execute?, sourceMap? }
at validate (/home/dave/web/spp/web/app/themes/spp/node_modules/schema-utils/dist/validate.js:104:11)
at Object.loader (/home/dave/web/spp/web/app/themes/spp/node_modules/postcss-loader/dist/index.js:43:29)
at /home/dave/web/spp/web/app/themes/spp/node_modules/webpack/lib/NormalModule.js:195:19
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:233:18
Asset     Size  Chunks             Chunk Names
scripts/main.js  8.74 kB       0  [emitted]  main
scripts/customizer.js  3.24 kB       1  [emitted]  customizer
scripts/main.js.map  8.51 kB       0  [emitted]  main
scripts/customizer.js.map  3.07 kB       1  [emitted]  customizer
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dave@dave-AERO-15XV8:~/web/spp/web/app/themes/spp$ yarn rebuild
yarn run v1.22.5
error Command "rebuild" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dave@dave-AERO-15XV8:~/web/spp/web/app/themes/spp$ yarn install
yarn install v1.22.5
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 0.55s.
dave@dave-AERO-15XV8:~/web/spp/web/app/themes/spp$ yarn
yarn install v1.22.5
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.1".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^7.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^2.7.0 || ^3.11.0 || ^4.4.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[5/5] Building fresh packages...
Done in 21.13s.
dave@dave-AERO-15XV8:~/web/spp/web/app/themes/spp$ yarn build
yarn run v1.22.5
$ webpack --progress --config resources/assets/build/webpack.config.js
95% emitting

ERROR  Failed to compile with 2 errors                                                                                12:15:29 pm
error  in ./resources/assets/styles/main.scss
Module build failed: ModuleBuildError: Module build failed: ValidationError: Invalid options object. PostCSS Loader has been initialized using an options object that does not match the API schema.

options has an unknown property 'plugins'. These properties are valid:
object { postcssOptions?, execute?, sourceMap? }
at validate (/home/dave/web/spp/web/app/themes/spp/node_modules/schema-utils/dist/validate.js:104:11)
at Object.loader (/home/dave/web/spp/web/app/themes/spp/node_modules/postcss-loader/dist/index.js:43:29)
at /home/dave/web/spp/web/app/themes/spp/node_modules/webpack/lib/NormalModule.js:195:19
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:233:18

@ multi ./scripts/main.js ./styles/main.scss
error  in ./resources/assets/styles/main.scss
Module build failed: ModuleBuildError: Module build failed: ValidationError: Invalid options object. PostCSS Loader has been initialized using an options object that does not match the API schema.

options has an unknown property 'plugins'. These properties are valid:
object { postcssOptions?, execute?, sourceMap? }
at validate (/home/dave/web/spp/web/app/themes/spp/node_modules/schema-utils/dist/validate.js:104:11)
at Object.loader (/home/dave/web/spp/web/app/themes/spp/node_modules/postcss-loader/dist/index.js:43:29)
at /home/dave/web/spp/web/app/themes/spp/node_modules/webpack/lib/NormalModule.js:195:19
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at /home/dave/web/spp/web/app/themes/spp/node_modules/loader-runner/lib/LoaderRunner.js:233:18
Asset     Size  Chunks             Chunk Names
scripts/main.js  8.74 kB       0  [emitted]  main
scripts/customizer.js  3.24 kB       1  [emitted]  customizer
scripts/main.js.map  8.51 kB       0  [emitted]  main
scripts/customizer.js.map  3.07 kB       1  [emitted]  customizer
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Reproduces how often: [What percentage of the time does it reproduce?]
100%
Versions
9.0.10: November 9th, 2020
Ubuntu 18.04.5 LTS

+1

It looks like this is caused by<EMAIL_ADDRESS>The quick fix is to downgrade autoprefixer and postcss-loader like so:
yarn add<EMAIL_ADDRESS>-D
yarn add<EMAIL_ADDRESS>-D

it is not working :(

it is not working :(

Downgrading PostCSS to 3.0.0 worked for me.
npm uninstall postcss-loader --save-dev
npm install<EMAIL_ADDRESS>--save-dev

Then running yarn again just for safe keeping.

Downgrading PostCSS to 3.0.0 worked for me.
npm uninstall postcss-loader --save-dev
npm install<EMAIL_ADDRESS>--save-dev

Then running yarn again just for safe keeping.

it is not working :(

Try deleting node_modules then reinstalling

it is not working :(

Try deleting node_modules then reinstalling

Module build failed: Error: PostCSS plugin autoprefixer requires PostCSS 8.
Followed all the above steps.. any ideas?

Module build failed: Error: PostCSS plugin autoprefixer requires PostCSS 8.
Followed all the above steps.. any ideas?

@lcottingham in case you didn't see this article over onStack Overflow.
I downgraded autoprefixer to ^9.0.0 and was able to get past the same error you mentioned above but then I got the error:
Module build failed: Error: PostCSS plugin postcss-nested requires PostCSS 8.

And followed the steps here running:
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat @tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9

After running the above commands and fixing a handful of The 'border-gray-500' class doesn't exist errors, I am now up and running with Tailwind 2.0.2 on Sage 9.0.10.
Hopefully this helps someone 👍

It looks like this is caused by<EMAIL_ADDRESS>The quick fix is to downgrade autoprefixer and postcss-loader like so:
yarn add<EMAIL_ADDRESS>-D
yarn add<EMAIL_ADDRESS>-D

If you got "no matches found<EMAIL_ADDRESS>fix it by escaping special character '^', as below.
yarn add<EMAIL_ADDRESS>-D

I was having the same problem and found this post https://github.com/tailwindlabs/tailwindcss/discussions/2941#discussioncomment-145518 which fixed the initial problem for me!
Then I just had to run yarn upgrade<EMAIL_ADDRESS>and yarn && yarn build and all went green 👍

Nov 12 2020 and this still has not been fixed, is this project dead?

@stephan-v what exactly are you looking for?  there are solutions in this thread along with @strarsis PRs and topics about using sage 9 with newer node versions.
we are not actively supporting sage 9 anymore but the roots community is still helping maintain it. this issue doesn’t exist in sage 10, which is nearing final release.


Memory leak? Ferret v5.70 crashes/hangs for no apparent reason

Reported by Andrew Wittenberg on 30 Mar 2005 06:08 UTC
In Linux and Irix, the following script makes Ferret 5.70 alternately
crash, hang, or run properly, depending on subtle changes to this
script.  Is this due to a memory leak in Ferret?  Possibly related
to unresolved bugs #883 and #1140.
Although this script looks random, it took almost a full day to winnow
this out of a thousand lines from our diagnostic scripts.  This is the
simplest example I could come up with.  I'm attaching the datafile
dw_wavelet_1.nc referenced in the script.  Try commenting out various
lines, or changing the number of variables that get defined with LET,
and the crash goes away!  This subtlety makes me wonder whether a similar
bug may be in 5.80, even though this particular script doesn't crash in
5.80 for Linux.  Many of the lines in this script don't even do anything,
but take them out and the behavior of Ferret changes.
! mytest.jnl
rep/name=s/range=1:130 let cs = 0
can dat/all; use dw_wavelet_1.nc
def ax/z/depth pw_zax = period
let pd = wave_re^2+wave_im^2
let spec = pd[pd_zperiod = zaxreplace(pd,z[gz=pw_zax](t=@ave]
let),z[spec_zperiod = zaxreplace(spec,zgz=pw_zax
let),z[view; shade pd
let pw_ytics = xgx=0:1:1
can)
let da_labels = 2^pw_ytics
let dr_xpts  = xsequence(0*pw_ytics)
let dr_ypts  = xsequence(pw_ytics)
let l2_angle = xsequence(0)
let l2_labtxt = xsequence(da_labels)
rep/i=1:2 (\
let l2_valid = strcmp("l2_labtxt","bad") NE 0 AND missing(0*dr_ypts,1) EQ 0;\
IF l2_valid THEN; label 0 0 1 0 .12 "l2_labtxt"; ENDIF)
Here's what I get when I run this under Linux & Irix:
    NOAA/PMEL TMAP
    FERRET v5.70
    Linux(g77) 2.4.18 - 06/30/04
    30-Mar-05 00:52

yes? can mode verify
yes? go mytest
Segmentation fault
    NOAA/PMEL TMAP
    FERRET v5.70
    IRIX 6.5 - 06/24/04
    30-Mar-05 00:52

yes? can mode verify
yes? go mytest
STOP  FREE_MEMORY
STOP
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1208

Comment by<EMAIL_ADDRESS>on 30 Mar 2005 22:56 UTC
The seg fault occurs under solaris too, and in versions back to v5.41.  It
happens at a call to strcmp from c_strcmp, the second time through the loop at
the end of the script.  The first execution of the repeat loop works; on the
second, the first argument to c_strcmp, a pointer to a string, has been fouled
up.  The debugger lists it as a bad address
rep/i=1:2 (\
let l2_valid = strcmp("l2_labtxt","bad") NE 0
Note that after the release of v5.7 and before v5.8, Yonghua did all that work
on how internal strings are handled -- matching variable names, etc.  Perhaps he
fixed something that's been wrong all along.
Continuing to look, though.

Attachment from<EMAIL_ADDRESS>on 30 Mar 2005 06:09 UTC
dw_wavelet_1.nc
REPLACE THIS TEXT WITH UPLOADED FILE ./attachments/TRAC_1208_GIT_557/dw_wavelet_1.nc


Make build script more portable

To fix the issue with the missing await when using the admin password config, I used the Gitpod Cloud IDE. I noticed that the build script does not run in Gitpod.
This is because sh is given as interpreter in the shebang line und double square brackets [[ ... ]] are used. In a POSIX sh double square brackets are not available. Most modern Linux desktop distribution does not provide a real sh but point to bash instead. Therefore using this script on a desktop works even though. Gitpod uses a docker container that has sh installed. Therefore, the script does not work correctly.
I would suggest to use bash as interpreter to make the build script more portable.
By the way: If you would like to provide other developers with an easier entry you could find a configuration for the Gitpod Cloud IDE with a running SQLPad in my SQLPad Gitpod branch. Gitpod is free for up to 100 hours per month for open source projects. You can add it to your repository, if you like. [Full disclosure: I work for TypeFox who makes Gitpod.]

Hi @corneliusludmann feel free to create a PR for the sh, bash change :)


ps-design-system-util: typescript can't compile

NOTE: We are blocked by this bug and we cannot upgrade design system components until this issue is resolved.
Bug
When compiling a project that uses a design system component that has ps-design-system-util as a dependency , I get a typescript compilation error
../node_modules/@pluralsight/ps-design-system-util/dist/esm/use-resize-observer.d.ts:3:127 - error TS2304: Cannot find name 'ResizeObserverCallback'.

3 export declare function useResizeObserver(ref: RefObject<HTMLElement> | MutableRefObject<HTMLElement | undefined>, onResize?: ResizeObserverCallback): {

If I go to the file in the error above and add import 'resize-observer-polyfill', it can build successfully because ResizeObserverCallback is imported
Since the error is occurring in a generated .d.ts file, I am not sure how to make the generated .d.ts file explicitly import the needed file that contains the ResizeObserverCallback type
Expected behavior
projects using design system components that use ps-design-system-util build
Actual behavior
project does not build
Steps to repro

Install any ps-design-system component that uses ps-design-system-util in your project
Typescript compile the project

hi @izikandrw i'm attempting to reproduce your issue but haven't been able to yet.
i've created a sandbox here that i'm hoping you can look at and help me out
https://codesandbox.io/s/codesandboxer-example-forked-ts5y6?file=/example.tsx

side note. the resize-observer-polyfill is a dependency of the ps-design-system-util package so it should have been installed along with the design system packages. can see if/where the polyfill was installed to with something like npm ls esize-observer-polyfill

hi @izikandrw i'm attempting to reproduce your issue but haven't been able to yet.
i've created a sandbox here that i'm hoping you can look at and help me out
https://codesandbox.io/s/codesandboxer-example-forked-ts5y6?file=/example.tsx

side note. the resize-observer-polyfill is a dependency of the ps-design-system-util package so it should have been installed along with the design system packages. can see if/where the polyfill was installed to with something like npm ls esize-observer-polyfill

hmmm not sure why it's not reproducible unfortunately. I remember that I got around this issue by adding skipLibCheck": true to my tsconfig.json. I think that made it stop trying to check types in my node_modules and let me compile. Not sure if this is the greatest solution haha. Sorry couldn't be of more help.

hmmm not sure why it's not reproducible unfortunately. I remember that I got around this issue by adding skipLibCheck": true to my tsconfig.json. I think that made it stop trying to check types in my node_modules and let me compile. Not sure if this is the greatest solution haha. Sorry couldn't be of more help.

no worries. thanks @izikandrw. I also often use skipLibCheck when typescript gets over zealous in it's type checking.
closing this issue for now. please reach out if you have any other issues in the future.

no worries. thanks @izikandrw. I also often use skipLibCheck when typescript gets over zealous in it's type checking.
closing this issue for now. please reach out if you have any other issues in the future.


Generate values.yaml from schema

In cluster apps, we maintain default values in the schema and generate values.yaml from the schema.
This values.yaml file has been generated using
make generate-values

and should be updated in the same way whenever the schema changes.

Some complaints to take care of:
helm/cluster-cloud-director/combined-values.yaml: fail: connectivity.network.controlPlaneEndpoint.port: Invalid type. Expected: integer, given: string
helm/cluster-cloud-director/combined-values.yaml: fail: connectivity.network.pods.cidrBlocks: Invalid type. Expected: array, given: string
helm/cluster-cloud-director/combined-values.yaml: fail: connectivity.network.services.cidrBlocks: Invalid type. Expected: array, given: string
1 of 1 failed validation
helm/cluster-cloud-director/combined-values.yaml: fail: connectivity.network.controlPlaneEndpoint.port: Invalid type. Expected: integer, given: string
helm/cluster-cloud-director/combined-values.yaml: fail: connectivity.network.pods.cidrBlocks: Invalid type. Expected: array, given: string
helm/cluster-cloud-director/combined-values.yaml: fail: connectivity.network.services.cidrBlocks: Invalid type. Expected: array, given: string

@giantswarm/team-rocket Could you take a look here, please?


Feature: Add text file output for Twitch streamers.

Twitch streamers could use a feature that outputs there player id, the opponents id, the game id, and finally once https://github.com/TimothyMeadows/GUvrs/issues/16 is completed it can also output a text file for daily, and weekend ranked stats (win / loss record).

Issue merged with #16


feat: add seqc2 wgs and ffpe to presets

I think I forgot to set high-coverage to false for the WGS dataset. We might need to change that.


Address SDK conflict with legacy firebase-element

/cc @mbleigh @rictic @e111077
We need to make this change to address a naming conflict with the old SDK when deployed alongside the legacy firebase-element component.

LGTM

LGTM


"as" only works for some functions + inconsistent column naming

influxdb 0.9.1-rc1
"as" works for sum / min - the column in the result is called "foo":

> select sum(rx_bytes) as foo from port_rx_bytes where time > now() - 1h group by time(10m) limit 1
name: port_rx_bytes
-------------------
time			foo
2015-06-29T08:20:00Z	798336

"as" doesn't work for derivative / non_negative_derivative - the column in the result isn't called "foo":

> select derivative(rx_bytes) as foo from port_rx_bytes where time > now() - 1h group by time(10m) limit 1
name: port_rx_bytes
-------------------
time				rx_bytes
2015-06-29T08:16:32.916135011Z	0

Additionally, even when no "as" is used, the column names are determined differently:

> select derivative(rx_bytes) from port_rx_bytes where time > now() - 1h group by time(10m) limit 1
name: port_rx_bytes
-------------------
time				rx_bytes
2015-06-29T08:18:37.928172484Z	0

> select sum(rx_bytes) from port_rx_bytes where time > now() - 1h group by time(10m) limit 1
name: port_rx_bytes
-------------------
time			sum
2015-06-29T08:10:00Z	290304

In 0.9.2 the derivative column is always named value instead of what it should be.

This is fixed in this PR: https://github.com/influxdb/influxdb/pull/3564
Column name should always be the aggregate function name, so in this case, it would be derivative unless you alias it (which now works again).

Thank you @corylanou


Support passing the code as a query param in the URL

To quickly open the playground with some code, a useful feature would be passing the code text in the URL as a query parameter.
Let's say I have some python code:
num = 42
print(f"Hello {num}")

I can base64 encode this code-block programmatically, so that I can generate a link to the playground with all the code.

Yep, that makes sense. Just FYI, the build system for Riju has aged and it is not currently in a state where changes can be deployed, but as soon as I am able, I will be resolving that problem (which is actually a large horde of smaller problems) and making it possible to contribute again.


Fix usage of undocumented _implicitHeader

As discussed in #127 this PR now only includes the changes that should not break node v0.8 and has tests.
Sadly supertest does not support http2 yet, so I had to resort to vanilla server/client creation.
I'm not destroying the client/server here, not sure if that's needed?!

Sorry to pester you, but is there any update on this?

I'm very sorry, I totally forgot to follow up on your request to rerun the Travis CI job.

There were changes in node v9.8.0 that have the potential to maybe fix this... That's about all I got for this right now. :-(

I'm actually occasionally seeing this in the one app where I use this PR occasionally. I have no indication yet what causes it and it always takes the entire process down.
If anyone has any ideas on how to debug this, I'm very interested in it.

I added a fix for node 10.4 onward that caused timeouts there every time. This allowed me to add node v10.11 to the travis.yml targets, providing one more data point for the CI tests. I also added a bunch of error logging to the http2 tests.
However after several local runs and 10 forced CI runs I have not seen a single failure. There were plenty of changes in node v10 and even some in the v8 and v9 lines on http2, especially about closing connections and such.
This might mean it is fixed. I haven't seen the problem in my production app in a while either (using node v10), but I may have disabled http2 for unrelated reasons at some point, I'll check that later tonight.
@dougwilson Since I added node v10 in the travis.yml, could you re-run the dependency checks again? Maybe making this part of the testchain/tooling would be a good idea?

Sadly this is still happening, had to revert to the proxy doing compression again.
Error [ERR_HTTP2_INVALID_STREAM]: The stream has been destroyed,
    at Http2ServerResponse.write (internal/http2/compat.js:599:19),
    at Gzip.onStreamData (/usr/src/app/node_modules/@maritz/compression/index.js:206:20),
    at Gzip.emit (events.js:182:13),
    at addChunk (_stream_readable.js:283:12),
    at readableAddChunk (_stream_readable.js:264:11),
    at Gzip.Readable.push (_stream_readable.js:219:10),
    at Gzip.Transform.push (_stream_transform.js:151:32),
    at Zlib.processCallback (zlib.js:591:10)

Not sure if it's actually the same error as we had before anymore, I can't remember. I'll maybe try to see how to reliably reproduce it and add a failing test. Otherwise this PR is still a no-go.

Just to clarify: The code changes in this PR should be completely fine - they just change _implicitHeader to writeHead.
There is just some problem with how compression works over http2. If you want, I can make yet another PR for just this code change. I don't know if _implicitHeader on http1 is going away anytime soon, so there is probably no hurry.

@maritz, @dougwilson: need any help with this PR? I'd definitely prefer using this over rolling our own compression support for HTTP2.

If you can figure out what is causing the seemingly random failures, that would be great.
I don't have the time and honestly probably lack understanding of how compression and http2 work to fix this properly.

@maritz: do you have any hints on what your app does that might be provoking those failures? So far, I've been unable to reproduce that failure. It may be that the version of node 10 is different than what you were using. I see that some fixes (such as https://github.com/nodejs/node/pull/23146) have been made to HTTP2 since you saw this happening.

do you have any hints on what your app does that might be provoking those failures?

Not really, it was just failing after X amount of time working fine. It's a next.js server that also serves a few static files. So nothing too fancy.
But the Travis CI also had failures sometimes. So I really don't know how to approach this.

I'll be doing a bunch of testing of your published fork within our app soon; maybe that will be sufficient validation. Will report back.

With current commit, I could not reproduce the error @maritz reported.
But I figured out 2 possible reasons that caused the error.

First possible reason (The error found with Travis-CI)
Till this commit, the http2 test closes http2 stream when client get header frame ('response' is emmited when header frame reaches client).
https://github.com/expressjs/compression/blob/521863cb435a9ce258fb6f477f031a7ed7e1cec3/test/compression.js#L325-L328
Since Zlib compression processes asynchronous, the client possibly gets the header frame and close the stream before sending a body.
I surmised that @maritz occasionally saw the above issue and it has been solved.
100% reproduce this issue with the following code.

var server = createHttp2Server({ threshold: 0 }, function (req, res) {
    res.setHeader('Content-Type', 'text/plain')
    res.writeHead(res.statusCode)
    setImmediate(()=>{res.end()})
})

server.on('listening', function () {
    var client = createHttp2Client(server.address().port)
    var request = client.request({
        'Accept-Encoding': 'gzip'
    })
    request.on('response', function (headers) {
        closeHttp2(request, client, server, ()=>{})
    })
    request.end()
})

Second possible reason (The issue found with next.js)
When the server returns 304(not modified) or 204(no content), the error possibly happens with Compression.
When server returns statusCode 304 or 204, node http2 module starts to close stream. After that, seemingly call res.end() is safe. However, with compression, res is wrapped with Zlib stream and Zlib stream emit data even thought empty input (which is not a bug). So that, a server calls res.end() which is wrapped Zlib stream, eventually calls res.write(chunk) and it possibly causes the error.
With http1, If already set statusCode as 304 or 204, http_outgoing_message.write(chunk) checks if it has body and [do nothing] (https://github.com/nodejs/node/blob/master/lib/_http_outgoing.js#L619-L624).
With http2 compat layer, just throw an error.
next.js serves static file with send package. Send package check if file is cached and return 304(not modified) and  call res.end().
100% reproduce this issue with the following code.

var server = createHttp2Server({ threshold: 0 }, function (req, res) {
    res.setHeader('Content-Type', 'text/plain')
    res.writeHead(304)
    setImmediate(()=>{res.end()})
})

server.on('listening', function () {
    var client = createHttp2Client(server.address().port)
    var request = client.request({
        'Accept-Encoding': 'gzip'
    })
    request.end()
})

Fixing the second issue, I think there are two approaches.
A. check the status code in this package.
B. check the status code in nodejs http2 compat layer.
I prefer approch B, because of keeping compatibility with http1.
Any thoughts?

do you have any ETA to get this merged?

Can someone update this or get another one open to achieve the same results? It's been a known issue for quite some time and prevents using http2 with server framework (spdy, http2, nextjs, etc).
Separately is there any reason to keep supporting older engines with serious security risks?
"engines": {
  "node": ">= 0.8.0"
}

Hi @Icehunter I believe that the OP is working to update the PR. The things left have nothing to do with old Node.js versions; they are mainly about the tests included here to get them updated. If you publish a module you're welcome to choose whatever Node.js version support policy you would like. The versions supports are the ones I care about, and changing them at that point would be a fork since I would still need a module that suited my needs. I see no blocker in having it support all of them and also not use the above property when not needed.

If someone else wants to take over, of course they are free to do so. I can't promise any time frame about when I'll get around to this, sorry.

@maritz You can check a box I believe bottom right of the PR to allow maintainers to push to this PR, if youd like to leave the work open to updates.

@jonchurch Thanks, already checked by default, it seems. 👍

@maritz @jonchurch I can't rebase this PR however https://github.com/expressjs/compression/compare/master...Icehunter:bugfix/use_writeHead_instead_of_implicitHeader I did fork @maritz 's fork; and then rebased from express master. How can I help with this?

@Icehunter You can either submit a PR to OP's branch https://github.com/maritz/compression/tree/bugfix/use_writeHead_instead_of_implicitHeader or create a new PR here

Hey, I am running into this issue as well. To merge this what is needed is to address the change requests, correct? If so, I would maybe give it a try.

Superseded by #170.

Close in favor of #170


No module issue on Ubuntu 20.04(Focal)/WSL

If you just run apt update && apt install azure-cli on Ubuntu Focal, you'll install an old 2.0.81 version from focal/universe and it's packaged differently than the official deb packages we release and still in testing stage. It's not tested and maintianed by Azure CLI Team and has several issues that need to be fixed.
ℹPlease first uninstall azure-cli 2.0.81 and its dependencies:
sudo apt remove azure-cli -y && sudo apt autoremove -y
Then install the latest azure-cli:
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
See more install documentation.
Related Issues:
#13519 No module named 'builtin' in Ubuntu 20.04 (Canonical image)
#13958 az cli failing on webapp deployment (No module named 'decorator')
#14001 Missing antlr4, Error with az vm image list on ubuntu 20.04 (WSL)

Do we know the reason why it link to 2.0.81 instead of latest CLI?

Do we know the reason why it link to 2.0.81 instead of latest CLI?

@bluca packaged it initially for testing and is blocked by https://github.com/Azure/azure-cli/pull/13490.

Add one issue might related https://github.com/Azure/azure-cli/issues/14777#event-3752926198 (could deleted if it's unnecessary)

@fengzhou-msft the "blocking" issue closed in July, but I just had this recur TODAY on a brand new installation of 20.04 in WSL2. Is this issue still open, and if so, why? Likely because of resources, but it's five months later now..... :-)

It would be really great if the Azure CLI team could work with Debian and Ubuntu to produce releases that they can use and package in a normal way so that they work.  The AWS client works just fine out of distro packages, and most users use and expect to use distro packages and won't want to install a custom repository.  I'm certainly in that case, and It's a bit of a problem that the Azure CLI is so brittle that it's broken when packaged by a normal Linux distro.

Why isn't this added to the Ubuntu repo so we can always get the latest with apt update?

How is this not fixed by now? it's the year 2022 and this problem still exists in Ubuntu 20.04 LTS
it is madness to install binaries using this method:
$ curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

as this is super vulnerable to supply-chain attacks
When can we expect this to be fixed?

Um, agree on bash install, but my 20.04 apt does the right thing. Does yours not? azure-cli is already the newest version (2.34.1-1~focal).

@squillace
Dockerfile:
FROM docker.devops.moneris.com/groovy:3.0-jdk11
...
 Although I followed: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt#option-2-step-by-step-installation-instructions
and then:
 sudo apt-get remove azure-cli
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  python3-crcmod
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  azure-cli
0 upgraded, 0 newly installed, 1 to remove and 14 not upgraded.
After this operation, 1083 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 160756 files and directories currently installed.)
Removing azure-cli (2.34.1-1~focal) ...                                                                        /9.5s
 squillace@dellsquill  / 
▶ sudo apt-get install azure-cli
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  python3-crcmod
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  azure-cli
0 upgraded, 1 newly installed, 0 to remove and 14 not upgraded.
Need to get 0 B/75.4 MB of archives.
After this operation, 1083 MB of additional disk space will be used.
Selecting previously unselected package azure-cli.
(Reading database ... 102877 files and directories currently installed.)
Preparing to unpack .../azure-cli_2.34.1-1~focal_all.deb ...
Unpacking azure-cli (2.34.1-1~focal) ...
Setting up azure-cli (2.34.1-1~focal) ...                                                                     /20.3s
 squillace@dellsquill  / 
▶ az --version
azure-cli                         2.34.1

@squillace thanks for this tip, I applied it inside the Dockerfile, and the Azure CLI seems to be working fine now
to anybody who finds this page, I have slightly improved Microsoft's Debian/Ubuntu install commands to the following:
Dockerfile:
...

@alan-czajkowski, this is because you didn't add Microsoft Linux repo. Please see https://github.com/Azure/azure-cli/issues/19640.

@jiasli you're late to the party, see my solution above
why can't Microsoft add Azure CLI to the official Debian repos?

@jiasli you're late to the party, see my solution above

I know, since 05/12 is Saturday! 🤣

why can't Microsoft add Azure CLI to the official Debian repos?

All Microsoft Linux packages are delivered from https://packages.microsoft.com/ due to company policy. Appreciate your understanding.


Feat: Create first Vue component: dropdown sidebar

Topic
A tracer issue for the first Vue component to be added to the application.  Need to create a sidebar with a dropdown menu for changing which metrics are being accessed (by repo, org, etc.). Also need to feed in fake JSON data that will eventually come from API.
Service
Frontend
Steps

[ ] Create sidebar Vue component
[ ] Create fake JSON data and link to component
[ ] sidebar loads in app
[ ] tests?

This will be separate from a drop down component, might want to edit the title.

This has been added to VueCobalt.


workflow api's for schedule queries

Add's two new endpoints from heracles to fetch schedule queries cron between a duration and missed schedule queries crons between a duration
Opens up a new function that can fetch details about schedule queries cron using saved query id
Re-triggers a workflow for schedule query, this is different from re-running a workflow. Re-running a workflow gets run using the user who is triggering it, but in case of schedule query, re-run has to happen from the owner of the workflow for queries to work.
Adds an new endpoint for updating the workflow owner, call to heracles

More info:

https://www.notion.so/atlanhq/Python-SDK-Functions-for-Replaybility-ed63d0e992954b62a9d84edabded8612

Hi @nishantmunjal7, thanks for your contribution! 🥳 🎉
I've pushed the refactored changes to this PR Could you please review these newly added methods manually again on the latest changes 🙏 and let us know if something needs to be updated 😄
Currently, this feature is not enabled on our dev tenant (https://devx8.atlan.com), but we'll be adding integration for this feature soon. 💯


Composer update needed to fix error from new GitHub token format

I'm using this image to run tests for a Laravel project using a GitHub action. It appears GitHub has changed the format of their token which is causing an [UnexpectedValueException] error when calling composer config -g github-oauth.github.com *TOKEN*. The issue is described here and is fixed in the latest version of Composer. Can you update the images to use Composer 2.0.12?

@aharp-afg Done, pushed new images for 7.3, 7.4 and 8.0.

@luisdalmolin Thank you!

I'm still getting the same error. Is there a certain way you have to tell GitHub to pull the latest version of the image?

I'm not sure tbh, you may be able to clear the GH cache for actions.


Adding a threshold setting to FGFXLargeScalePerceptualObscuranceIrradiance.fx

FGFXLargeScalePerceptualObscuranceIrradiance.fx originally detects anything brighter than 0.5 as Irradiance and anything darker as Occlusion. Some games look too dark to have the Occlusion Intensity on anything higher than 0.
I added an Occlusion/Irradiance Threshold setting so that you can change the line that separates Occlusion and Irradiance to any value ranging from 0.004 to 0.996.
I did notice you have an Occlusion-Irradiance Neutral Point hidden setting, but it only seems to increase/decrease the brightness. It is different from my solution, which again, tweaks the middle line between Occlusion and Irradiance.
I've been using this tweaked version of your shader in many games, and I figured it would be more convenient if this was accepted in the main file, plus other people could have access to it too.
As an extra suggestion, I would also love to have the default value of Effect Saturation set to 0.1 since it's the minimum I've used ever since I found out how beautiful games can look with it.

Please change change the name of "ScaleOcclusionAndIrradiance2" to something more meaningful (ex. "ThresholdedScaleOcclusionAndIrradiance"). As for the Effect Saturation, set its default to 0.1 if you like it more.

Also please use spaces before and after '/' in "Occlusion/Irradiance Threshold".

Changes made! 😄

The extra changes were just to improve the readability of the thresholded formulas and to standardize the indentation based on the rest of the code 🙂

@AlexTuduran there's nothing else I want to add or change, so unless you want me to do something, this should be ready to go

That's great mate. Thanks for the contribution!


SPN target missing

Targeted SPs do not appear for some Test 1.26 and 2.17 log query displays for 3.0.12
PGN 61450 with Supported SPNs         <—— location for missing SP.
07:39:25.2363 0CF00A00 [8] FF FF 00 00 FF FF FF FF
Found: Engine Gas Flow Rate from Engine #1 (0):
SPN  2659, Engine EGR 1 Mass Flow Rate: Not Available
SPN   132, Engine Intake Air Mass Flow Rate: 0.000000 kg/h
SPN  5257, Engine EGR 2 Mass Flow Rate: Not Available
SPN 12758, Target Fresh Air Mass Flow: Not Available
WARN: <IP_ADDRESS>.a - N.7 Provided SPN 132 is not indicated as supported by Engine #1 (0)
07:41:54.6414 DS Request for PGN 65253 to Engine #1 (0) for SPNs
07:41:54.6437 18EA00F9 [3] E5 FE 00 (TX)
07:41:54.6507 18FEE500 [8] C5 83 03 00 7E D6 09 00
Engine Hours, Revolutions from Engine #1 (0):
SPN   247, Engine Total Hours of Operation: 11517.050000 h
SPN   249, Engine Total Revolutions: 644734000.000000 r
Start Test 1.26 - Data stream support verification
Expecting the following messages:
SPN 1213 is supported by Engine #1 (0) but will be omitted
SPN 1220 is supported by Engine #1 (0) but will be omitted
Req PGN 40448 from Engine #1 (0) with SPNs 4106
Req PGN 40960 from Engine #1 (0) with SPNs 4127, 4130
Req PGN 49408 from Engine #1 (0) with SPNs 3069, 3294, 3295, 3296
BCT PGN 61443 from Engine #1 (0) with SPNs 91, 92
BCT PGN 61444 from Engine #1 (0) with SPNs 190, 512, 513
BCT PGN 61454 from Engine #1 (0) with SPNs 3216, 3217
BCT PGN 61455 from Engine #1 (0) with SPNs 3226
BCT PGN 61466 from Engine #1 (0) with SPNs 3464
Req PGN 64587 from Engine #1 (0) with SPNs 7333
Req PGN 64720 from Engine #1 (0) with SPNs 7393
BCT PGN 64739 from Engine #1 (0) with SPNs 5541
BCT PGN 64765 from Engine #1 (0) with SPNs 5313
Req PGN 64782 from Engine #1 (0) with SPNs 7351
Req PGN 64784 from Engine #1 (0) with SPNs 7353
BCT PGN 64870 from Engine #1 (0) with SPNs 4076
Req PGN 64878 from Engine #1 (0) with SPNs 5463
Req PGN 64891 from Engine #1 (0) with SPNs 5466
BCT PGN 64892 from Engine #1 (0) with SPNs 3700
BCT PGN 64908 from Engine #1 (0) with SPNs 3609
BCT PGN 64916 from Engine #1 (0) with SPNs 27
BCT PGN 64923 from Engine #1 (0) with SPNs 3516
BCT PGN 64946 from Engine #1 (0) with SPNs 3251
BCT PGN 64947 from Engine #1 (0) with SPNs 3246
BCT PGN 64948 from Engine #1 (0) with SPNs 3242
Req PGN 64952 from Engine #1 (0) with SPNs 3301, 3302
Req PGN 64962 from Engine #1 (0) with SPNs 5837
Req PGN 64963 from Engine #1 (0) with SPNs 2623
Req PGN 64981 from Engine #1 (0) with SPNs 2791, 5323
BCT PGN 65110 from Engine #1 (0) with SPNs 1761
Req PGN 65154 from Engine #1 (0) with SPNs 1413, 1414, 1415, 1416
Req PGN 65155 from Engine #1 (0) with SPNs 1417, 1418
BCT PGN 65174 from Engine #1 (0) with SPNs 1188, 1189
BCT PGN 65177 from Engine #1 (0) with SPNs 1177
BCT PGN 65178 from Engine #1 (0) with SPNs 1173
Req PGN 65194 from Engine #1 (0) with SPNs 1692
BCT PGN 65243 from Engine #1 (0) with SPNs 157
BCT PGN 65247 from Engine #1 (0) with SPNs 3236
BCT PGN 65251 from Engine #1 (0) with SPNs 539, 540, 541, 542, 543, 544
BCT PGN 65252 from Engine #1 (0) with SPNs 1081
Req PGN 65253 from Engine #1 (0) with SPNs 247
BCT PGN 65262 from Engine #1 (0) with SPNs 110, 175
BCT PGN 65263 from Engine #1 (0) with SPNs 94
BCT PGN 65265 from Engine #1 (0) with SPNs 84
BCT PGN 65266 from Engine #1 (0) with SPNs 51, 183
BCT PGN 65269 from Engine #1 (0) with SPNs 108, 171
BCT PGN 65270 from Engine #1 (0) with SPNs 102, 105
BCT PGN 65271 from Engine #1 (0) with SPNs 158
Req PGN 64920 from DPF Controller (85) with SPNs 5454
Step <IP_ADDRESS>.a - Reading bus for 20 seconds
DM24 from Engine #1 (0): [
D F T F
a r e F
t F s l
a r t n  SPN — SP Name
D F   2  SPN 27 - Engine EGR 1 Valve Position
D F   1  SPN 51 - Engine Throttle Valve 1 Position 1
D F   2  SPN 84 - Wheel-Based Vehicle Speed
D F   1  SPN 91 - Accelerator Pedal Position 1
D F   1  SPN 92 - Engine Percent Load At Current Speed
D F   1  SPN 94 - Engine Fuel Delivery Pressure
1  SPN 96 - Fuel Level 1
F   1  SPN 100 - Engine Oil Pressure 1
D F T 1  SPN 102 - Engine Intake Manifold #1 Pressure
D F   1  SPN 105 - Engine Intake Manifold 1 Temperature
D F   1  SPN 108 - Barometric Pressure
D F T 1  SPN 110 - Engine Coolant Temperature  <—- SP 132 not in DM24
D F   2  SPN 157 - Engine Fuel 1 Injector Metering Rail 1 Pressure
D F   2  SPN 158 - Key Switch Battery Potential
D F   2  SPN 171 - Ambient Air Temperature
1  SPN 172 - Engine Intake 1 Air Temperature
D F   2  SPN 175 - Engine Oil Temperature 1
D F   2  SPN 183 - Engine Fuel Rate
D F   2  SPN 190 - Engine Speed
D F   4  SPN 247 - Engine Total Hours of Operation

Blank SPNs reflect those (relevant) PGs in Table A-1 not in DM24 response.

Please estimate effort for this change.


egl_rpi - BCMDisplayException: Failed to get display size

Python: 3.6
OS: Raspbian Stretch Lite (without X)
Kivy: 1.11
Kivy installation method: pip install from master branch

Description
I'm trying to run Kivy on Raspberry Pi Zero with OpenGL driver set to Full KMS. It fails with "egl_rpi - BCMDisplayException: Failed to get display size". Everything works when OpenGL driver is disabled.
Code and Logs
(sorry for doubled logs)
[INFO   ] [Logger      ] Record log in /home/pi/.kivy/logs/kivy_18-06-22_4.txt
2018-06-22 00:10:33,265 [INFO] [kivy                    ] [Logger      ] Record log in /home/pi/.kivy/logs/kivy_18-06-22_4.txt
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
2018-06-22 00:10:33,249 [INFO] [kivy                    ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[INFO   ] [Kivy        ] v1.11.0.dev0, git-4d3ea59, 20180621
2018-06-22 00:10:33,931 [INFO] [kivy                    ] [Kivy        ] v1.11.0.dev0, git-4d3ea59, 20180621
[INFO   ] [Python      ] v3.6.0 (default, Jun  4 2018, 04:51:36)
[GCC 6.3.0 20170516]
2018-06-22 00:10:33,943 [INFO] [kivy                    ] [Python      ] v3.6.0 (default, Jun  4 2018, 04:51:36)
[GCC 6.3.0 20170516]
[INFO   ] [Text        ] Provider: sdl2
2018-06-22 00:10:34,023 [INFO] [kivy                    ] [Text        ] Provider: sdl2
[INFO   ] [Factory     ] 194 symbols loaded
2018-06-22 00:10:34,108 [INFO] [kivy                    ] [Factory     ] 194 symbols loaded
[INFO   ] [Window      ] Provider: egl_rpi
2018-06-22 00:10:42,661 [INFO] [kivy                    ] [Window      ] Provider: egl_rpi
[INFO   ] [Window      ] Provider: sdl2(['window_egl_rpi'] ignored)
2018-06-22 00:10:43,062 [INFO] [kivy                    ] [Window      ] Provider: sdl2(['window_egl_rpi'] ignored)
[CRITICAL] [Window      ] Unable to find any valuable Window provider.
egl_rpi - BCMDisplayException: Failed to get display size
  File "/usr/local/lib/python3.6/site-packages/kivy/core/__init__.py", line 67, in core_select_lib
    cls = cls()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/__init__.py", line 968, in __init__
    self.create_window()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/window_egl_rpi.py", line 33, in create_window
    w, h = bcm.graphics_get_display_size(self._rpi_dispmanx_id)
  File "kivy/lib/vidcore_lite/bcm.pyx", line 74, in kivy.lib.vidcore_lite.bcm.graphics_get_display_size (/tmp/pip-a55waee4-build/kivy/lib/vidcore_lite/bcm.c:1877)

sdl2 - RuntimeError: b'No available video device'
  File "/usr/local/lib/python3.6/site-packages/kivy/core/__init__.py", line 67, in core_select_lib
    cls = cls()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/window_sdl2.py", line 140, in __init__
    super(WindowSDL, self).__init__()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/__init__.py", line 968, in __init__
    self.create_window()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/window_sdl2.py", line 272, in create_window
    self.fullscreen, resizable, state)
  File "kivy/core/window/_window_sdl2.pyx", line 93, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window (/tmp/pip-a55waee4-build/kivy/core/window/_window_sdl2.c:2398)
  File "kivy/core/window/_window_sdl2.pyx", line 66, in kivy.core.window._window_sdl2._WindowSDL2Storage.die (/tmp/pip-a55waee4-build/kivy/core/window/_window_sdl2.c:1975)

x11 - ModuleNotFoundError: No module named 'kivy.core.window.window_x11'
  File "/usr/local/lib/python3.6/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    fromlist=[modulename], level=0)

2018-06-22 00:10:43,150 [CRITICAL] [kivy                    ] [Window      ] Unable to find any valuable Window provider.
egl_rpi - BCMDisplayException: Failed to get display size
  File "/usr/local/lib/python3.6/site-packages/kivy/core/__init__.py", line 67, in core_select_lib
    cls = cls()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/__init__.py", line 968, in __init__
    self.create_window()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/window_egl_rpi.py", line 33, in create_window
    w, h = bcm.graphics_get_display_size(self._rpi_dispmanx_id)
  File "kivy/lib/vidcore_lite/bcm.pyx", line 74, in kivy.lib.vidcore_lite.bcm.graphics_get_display_size (/tmp/pip-a55waee4-build/kivy/lib/vidcore_lite/bcm.c:1877)

sdl2 - RuntimeError: b'No available video device'
  File "/usr/local/lib/python3.6/site-packages/kivy/core/__init__.py", line 67, in core_select_lib
    cls = cls()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/window_sdl2.py", line 140, in __init__
    super(WindowSDL, self).__init__()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/__init__.py", line 968, in __init__
    self.create_window()
  File "/usr/local/lib/python3.6/site-packages/kivy/core/window/window_sdl2.py", line 272, in create_window
    self.fullscreen, resizable, state)
  File "kivy/core/window/_window_sdl2.pyx", line 93, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window (/tmp/pip-a55waee4-build/kivy/core/window/_window_sdl2.c:2398)
  File "kivy/core/window/_window_sdl2.pyx", line 66, in kivy.core.window._window_sdl2._WindowSDL2Storage.die (/tmp/pip-a55waee4-build/kivy/core/window/_window_sdl2.c:1975)

x11 - ModuleNotFoundError: No module named 'kivy.core.window.window_x11'
  File "/usr/local/lib/python3.6/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    fromlist=[modulename], level=0)

[CRITICAL] [App         ] Unable to get a Window, abort.
2018-06-22 00:10:43,173 [CRITICAL] [kivy                    ] [App         ] Unable to get a Window, abort.

Also experiencing this, although on an Ubuntu armhf install.
I have tried changing the resolution using raspi-config to no avail.

It's an issue for BCM directly. So any app using it will fail the same, not directly related to Kivy. But would be nice to understand.

Closing this as Won't Fix, because the component in question is deprecated. See #8434.


libreoffice: offline help doesn't get added.

Describe the bug
Offline help is not available on Libreoffice, even though withHelp flag is enabled by default.
Steps To Reproduce
Steps to reproduce the behavior:

Add libreoffice to the system packages
Notice the offline help is missing
Check the source for a potential setting, notice it's enabled by default and nothing ever touches it.
scream for 3 months unsure if this is PEBKAC or not

Expected behavior
Have a toggle to build with help, or have a separate package that has the offline help.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

Notify maintainers

@7c6f434c (note: raskin leads to an unrelated org, rename?)
cc @vcunat @doronbehar
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[hjs@nixfv:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.7, NixOS, 23.11 (Tapir), 23.11.2082.d02ffbbe834b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.11, unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

PS: appears i got a double-zero issue id :D

Add a :+1: reaction to issues you find important.

Thanks for the report, I think this should fix it (haven't tested the full build yet): https://github.com/NixOS/nixpkgs/pull/276434 .

@FavoritoHJS I waited for CI to be green in #276434 to make sure it doesn't break the build. Could you please test it on your machine, and see if it indeed helped?

seems like it didn't use the cache so i'm waiting 2 hours for libreoffice to compile... fun!

Haha yes I know :) That's why I waited for CI to be green - to make sure that at least you won't encounter a build error after hours of building. Ideally, CI would have pushed to an online cache server such as cachix.

Great, glad I could help :). Follow the PR at https://nixpk.gs/pr-tracker.html?pr=276434 .


docs: fix link to svelte file for pipeline icon

Hey,
this MR introduces a minor fix in the Models -> Tasks documentation and updates link to PIpeline Icon Svelte implementation.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


MINECRAFT GAMER

Dilan gamer

Sorry, I'm not sure what you mean? If you want to report a bug, lease describe your issue and re-open this issue.


Colorize sprites

I have a feeling there is a more efficient way to do this, but none of the blending options did quite what I wanted. I need to do a multiply blend on both the color and the opacity.
This solution creates a separate canvas, redraws the sprite there, does a "source-in" operation to paint the sprite with a color, and then "multiply" this back onto the image. The result looks decent:

Closes #14

That's very close to what I expected we would need to do. Nicely done with using source-in to make a colour mask for just the sprite.


JSON Request Postman Collection

I'm using this library to auto generate a postman collection. But I can't seem to figure out how to make it expect JSON data as the input as opposed to form-data (see pic).
Cheers

Tried adding "Content-type" => "application/json" to apply.headers?

No that doesn't do anything. It's actually about defining the output type for Postman and encoding the data as a JSON object. It is the same request as the one defined here - https://github.com/mpociot/laravel-apidoc-generator/issues/390
Is this feature planned at all?

This has been done in #627 (coming in v4)


Physics System

I've decided to use Box2D as my engines main physics/collision system because it look similar to BulletPhysics and simple to use. I've never release used it for anything so it will be fun getting it integrated into my little game engine.

Here is the introduction video and the initial plan for the physics system.

Alright its time to get started on this issue.

Alright just got done with clean the main.cpp file so lets take a look at the documentation of Box2D

I'm debating of either switching to a different physics system. After reading through the documentation of Box2D and in the faqs section of the documentation page it states that box characters aren't well optimized for the tile maps and also it doesn't use pixel cords but meters which could be a problem.
I'm going to checkout Chipmunk which is a different physics engine that was created during the same time as Box2D. If I can't use that engine I'll just have to roll my own which is going to be a task in a half.

Ok, I took a look a chipmunk physics and it does have the ability to interact with tilemaps or should I say solids. I'm going to download chipmunk and test it. Just like Box2D its under the mit license.

Alright I'm going to do 2 branches to test both Box2D and Chipmunk Physics engines.

Instead of wasting time with youtube videos I'm going to focus on getting this project in a much more complete state. Basically getting this physics stuff implemented. That what I'm going to do for now before I make any more videos. I'll do my next video in December or January. I want to get to the point of working on the editors before make anymore videos.

Alright I'm done with the Box2D physics test. Needed to know how it works and I'm quite pleased with it. There are some interesting consequences of using said api because it uses meters not pixels as a measurement and I had to set a standard of what a meter is which in the test branch is every 32 pixels = 1 meter which makes since considering a tile in the engine will be 32x32 so a single tile would be 1x1 meters. The other thing is that the y-axis is inverted so I had to make a conversion method for the positions to account for that for example
p=<32, 32>
m=convert_position(p)
then
m=<1, -1>
As for sizes I don't need to worry about negating the y because sizes are always positive numbers so therefore
s=<32, 32>
ms=convert_size(s)
then
ms=<1, 1>
This should sum up the math portion of the what I'll need to do if I'm going with Box2D as my physics system.
Now its time to test chipmunk to see what the difference is.

After reading through some of chipmunks documentation it apparently is a lot faster then Box2D which is a plus. Also I don't need to convert the measurements to meters which is also a plus. This means I can use pixel coords. I think. This is make Chipmunk into a really good contender compared to Box2D. Also it uses C language instead of C++ which is fine in my book. Lets get into the meat and potatoes of this api.
Here is the chipmunk physics website. https://chipmunk-physics.net
Here is the chipmunk physics documentations https://chipmunk-physics.net/release/ChipmunkLatest-Docs/
I'm adding these in for documentation purposes.

Alright got it working tonight. Figured out that one the boxes are created in counter clock wise fasion so I'll need to account for that. Also the y-axis in chipmunk is inverted so I'll have to account for that when I get started on the actual physics system in the master branch of the code.

Alright I've made my decision of which physics engine I'll be using for this project for now. And its going to be... Chipmunk! The reason why I've made this decision is because I don't need to change my units. The problem I have with Box2D is that its uses meters instead of just simple pixels units. Now Chipmunk has its own issues but those are out weigh by the advantages. So tonight I'm going to remove Box2D and add in Chipmunk. I'll most likely take a look at Box2D in the future but for now Chipmunk will be used instead.

Alright I'm thinking I'm at the point were I can pause this issue for a bit and move on to something else for a bit. I'm going to go back to the app, input, and add a new issue called config which will allow to configure the game engine during runtime which is going to be cool plus I'll be needing a gui system that is used with in the game because ImGui isn't going to the job after all ImGui is used to create editors and example guis but isn't meant for an end user gui.


Vulnerability roundup 94: libvirt-6.3.0: 1 advisory [6.7]

search, files

[ ] CVE-2020-25637 CVSSv3=6.7 (nixos-20.09, nixos-unstable)

Scanned versions: nixos-20.09: 0b8799ecaaf; nixos-unstable: 420f89ceb26.
Cc @fpletz
Cc @globin

See also: #93268

This is fixed on master via #109332.
I've found one bug in the update (#109415) that would mean it shouldn't be backported to 20.09 yet, and given the large packaging difference it might be worth waiting for it to be on the unstable channel for a short while before considering backporting.

This is fixed on master via #109332.
I've found one bug in the update (#109415) that would mean it shouldn't be backported to 20.09 yet, and given the large packaging difference it might be worth waiting for it to be on the unstable channel for a short while before considering backporting.

@euank Do you think it's possible to backport the patches instead updating the version?

Good idea, @dotlambda, they backported pretty cleanly. I put up a PR for that over here: #111708


Adding duplicate torrent when stopped

I took a look at the issue #581 i created about adding a stopped torrent that is already in the list.
I was able to fix the issue by replacing the torrentKey of the first torrent with the key of the duplicate, and mimic a toggleTorrent.
This is not an elegant solution, but maybe it could do for now?
Also, I was wondering why a torrent have a torrentKey instead of being identified by the infoHash?

Any updates for this PR?

Just updated PR to accommodate refactor.
I don't know if there is interest in merging, maybe somebody has a better idea on how to do this?
I tried to keep changes minimal, but it would probably be better to determine the duplicate before starting a new webtorrent session.

Thanks for this PR, @mathiasvr! And for updating it to accommodate the refactor.
The reason for torrentKey is that some torrentIds don't have an info hash that can be determined trivially (i.e. synchronously). For example, an http torrent url or filesystem path where the file has to be fetched asynchronously. So we need a way to identify the torrent before it's info hash has been determined.
We should document this better in the comments. PR welcome for that 👍

Upon further thought, I think we should error when they adda duplicate torrent instead of setting the state to new, so that it's consistent with how the app behaves when adding a duplicate torrent and the current one is actively torrenting.

https://github.com/feross/webtorrent-desktop/pull/612


AmbiguousElementError is raised when locator matches multiple elements

It would be more convenient if the first element that matches specified locator would return instead of raising AmbiguousElementError.

@dnovikau This is actually by design. The guiding principle behind interactors is that they flow from the perspective of how the user would interact with a UI, and not code.
This is, for example, why most of the locators match human readable text, and not test ids or data attributes.
While it might be more convenient for code, a user must, by definition be able to disambiguate between elements in order to use them correctly, and so having interactors which reflect that results, in our experience, a better structured UI.
All that said, what is your specific structure of HTML that is causing problems and would be made better by not raising ambiguous element errors?

I'm going to close this, but leave this here. A common option to disambiguate elements is to use a filter https://frontside.com/interactors/docs/locators-filters#filters


Add new customised tools in @cornerstonejs/tools package

What feature or change would you like to see made?
I would like to contribute some of our own customised tools to the @cornerstonejs/tools package. Do we have particular guidelines for contributing tools to the project or a customised way to add tools?
There are many types of measures based on angles and segments that we would allow users to draw by using tools.
Why should we prioritize this feature?
This feature might help us to beautifully integrate the CornerstoneJS library to one of our legacy project that allows users to draw measures and annotate them directly on dicoms instead of drawing on Images

Thank you, @sedghi. I was able to create the tools by following the inbuilt instructions.


[dart2wasm] Compile-time crash with mixin with a monomorphised WasmArray member

This is not a user-visible crash, but it's causing issues in the standard libraries.
import 'dart:_wasm';

class A {
  final int a;

  A(this.a);
}

class B extends A {
  final int b;

  B(int a, this.b): super(a);
}

class C extends A {
  final int c;

  C(int a, this.c): super(a);
}

mixin ArrayMixin<T extends A> {
  WasmArray<T?> array = WasmArray<T?>(10);

  void reallocate() {
    final newSize = array.length * 2;
    array = WasmArray<T?>(newSize);
  }
}

class Bs with ArrayMixin<B> {}

class Cs with ArrayMixin<C> {}

void main() {
  final bs = Bs();
  bs.reallocate();

  final cs = Cs();
  cs.reallocate();
}

Crash:
Null check operator used on a null value
#0      SelectorInfo._upperBound.<anonymous closure> (package:dart2wasm/dispatch_table.dart:203)
#1      MappedIterator.moveNext (dart:_internal/iterable.dart:413)
#2      SetBase.addAll (dart:collection/set.dart:58)
#3      _Set.addAll (dart:_compact_hash:1068)
#4      new LinkedHashSet.of (dart:collection/linked_hash_set.dart:192)
#5      Iterable.toSet (dart:core/iterable.dart:513)
#6      SelectorInfo._upperBound (package:dart2wasm/dispatch_table.dart:206)
#7      SelectorInfo._computeSignature.<anonymous closure> (package:dart2wasm/dispatch_table.dart:159)
#8      new _GrowableList.generate (dart:core-patch/growable_array.dart:136)
#9      SelectorInfo._computeSignature (package:dart2wasm/dispatch_table.dart:158)
#10     SelectorInfo.signature (package:dart2wasm/dispatch_table.dart:61)
#11     Translator.signatureForDirectCall (package:dart2wasm/translator.dart)
#12     AstCodeGenerator._directSet (package:dart2wasm/code_generator.dart:2285)
#13     AstCodeGenerator.visitInstanceSet (package:dart2wasm/code_generator.dart:2252)
#14     InstanceSet.accept1 (package:kernel/src/ast/expressions.dart:860)
#15     AstCodeGenerator.translateExpression (package:dart2wasm/code_generator.dart:667)
#16     AstCodeGenerator.visitExpressionStatement (package:dart2wasm/code_generator.dart:1158)
#17     ExpressionStatement.accept (package:kernel/src/ast/statements.dart:50)
#18     AstCodeGenerator.translateStatement (package:dart2wasm/code_generator.dart:684)
#19     AstCodeGenerator.visitBlock (package:dart2wasm/code_generator.dart:796)
#20     Block.accept (package:kernel/src/ast/statements.dart:103)
#21     AstCodeGenerator.translateStatement (package:dart2wasm/code_generator.dart:684)
#22     SynchronousProcedureCodeGenerator.generateInternal (package:dart2wasm/code_generator.dart:3195)
#23     AstCodeGenerator.generate (package:dart2wasm/code_generator.dart:212)
#24     AstCompilationTask.run (package:dart2wasm/translator.dart:1313)
#25     Translator.translate (package:dart2wasm/translator.dart:401)
#26     compileToModule (package:dart2wasm/compile.dart:253)
<asynchronous suspension>
#27     generateWasm (package:dart2wasm/generate_wasm.dart:80)
<asynchronous suspension>
#28     main (file:///usr/local/google/home/omersa/dart/sdk/sdk/pkg/dart2wasm/bin/dart2wasm.dart:10)
<asynchronous suspension>

Relevant code: https://github.com/dart-lang/sdk/blob/01238a49ec0858778098ed77d8b2aec7e347072a/pkg/dart2wasm/lib/code_generator.dart#L2278-L2300
It looks like the reference for the field array is not a field but a setter (not sure why), so we generate its signature via the dispatch table, which tries to take the LUB of WasmArray<B?> and WasmArray<C?>, and failing as WasmArray is a top type on its own.

I think there's two part to fixing this.
The problem occurs in polymorphic code like this:
WasmArray<T?> getArray<T extends A>(ArrayMixin<T> array) => array.array;

Even if we copy the array field to every mixin application this code remains polymorphic.
Currently this code tries to compute the least upper bound of different WasmArray types, which always fails. I can fix this in a hacky way with this:
diff --git a/pkg/dart2wasm/lib/dispatch_table.dart b/pkg/dart2wasm/lib/dispatch_table.dart
index b270441f303..6658649afe9 100644
--- a/pkg/dart2wasm/lib/dispatch_table.dart
+++ b/pkg/dart2wasm/lib/dispatch_table.dart
@@ -197,13 +197,18 @@ class SelectorInfo {
       return w.RefType(heapTypes.single, nullable: nullable);
     }
     int targetDepth = minDepth;
+
     while (heapTypes.length > 1) {
-      heapTypes = heapTypes.map((s) {
-        while (s.depth > targetDepth) {
-          s = s.superType!;
-        }
-        return s;
-      }).toSet();
+      if (heapTypes.every((heapType) => heapType is w.ArrayType)) {
+        return w.RefType(w.HeapType.array, nullable: false);
+      } else {
+        heapTypes = heapTypes.map((s) {
+          while (s.depth > targetDepth) {
+            s = s.superType!;
+          }
+          return s;
+        }).toSet();
+      }
       targetDepth -= 1;
     }
     return w.RefType.def(heapTypes.single, nullable: nullable);

That fixes the type of array.array expression, but the function itself still returns WasmArray<A?>:
  (rec
    (type $Array<A> (;557;) (array (field (mut (ref $A)))))
  )
  (rec
    (type $Array<B?> (;176;) (array (field (mut (ref null $B)))))
  )
  (rec
    (type $Array<C?> (;172;) (array (field (mut (ref null $C)))))
  )
  (func $getArray (;587;) (param $var0 (ref $_Type)) (param $var1 (ref $Object)) (result (ref $Array<A>))
    (local $var2 (ref $Object))
    local.get $var1
    local.tee $var2
    local.get $var2
    struct.get $#Top $field0
    i32.const 689
    i32.add
    call_indirect (param (ref $Object)) (result (ref array))
    ref.cast $Array<A>
    return
  )

So the ref.cast here always fails because none of the array getters return Array<A>:
  (func $_Cs&Object&ArrayMixin.array (;591;) (param $var0 (ref $Object)) (result (ref array))
    local.get $var0
    ref.cast $_Cs&Object&ArrayMixin
    struct.get $_Cs&Object&ArrayMixin $field2
  )
  (func $_Bs&Object&ArrayMixin.array (;592;) (param $var0 (ref $Object)) (result (ref array))
    local.get $var0
    ref.cast $_Bs&Object&ArrayMixin
    struct.get $_Bs&Object&ArrayMixin $field2
  )

The return type of getArray should be ref array.

In our dart:convert I want to make the UTF8 parser to operate on Wasm arrays instead of U8Lists. I haven't tried this yet, but I think this issue will block that change as we pass the chunk type to a mixin type parameter: https://github.com/dart-lang/sdk/blob/a9469269d79e2fe182cb2baad088eb59d865810b/sdk/lib/_internal/wasm/lib/convert_patch.dart#L1613-L1614
Here the mixin type will be _ChunkedJsonParser<WasmArray<WasmI8>>.


Thanks! But please still watch your language :/


Add a note somewhere in the README that selinux enablement can lead to pods trying to use volumes with many files never booting

Description
I got bit by this, and it took awhile to figure out because you get very little in the way of logs about this outside of the containerd logs in the k3s folder on the node. These logs don't even make it to journalctl sadly adding further difficulty when investigating.
Long story short disabling selinux for a nodepool to use these volumes is the best workaround in the short term. Best solution will be this: https://kubernetes.io/blog/2023/04/18/kubernetes-1-27-efficient-selinux-relabeling-beta/
But for this we need this to be closed first:
https://github.com/hetznercloud/csi-driver/issues/582

@sharkymcdongles PR welcome if you want to make our docs more complete with this special use case.


Scroll sensitivity too high with Mac trackpad

Older versions had normal scroll sensitivity, but since I updated a few days ago  (I have actually re-installed the newest version because I upgraded my MacBook from a 13" Pro to the new 14" Pro and I installed everything from scratch) the sensitivity when scrolling with the trackpad is higher and it's a bit TOO high.

Looks like this is being addressed in #146403—waiting on some log output but for the moment the recommendation is to set the workbench.list.mouseWheelScrollSensitivity and editor.mouseWheelScrollSensitivity settings to ~0.4.

OK, sorry for reporting. I did try to find open issues on this topic, but somehow missed that one. I will close this issue and try the workaround.
Thank you!


Amazon connect Task flow stopped working

I created inbound flow where i added create Task block with Sample Lambda function integration ... before 2 days it was partially working but now it routes to error message.

What is the behavior / UX that you're seeing on your custom ccp? What in streams is surfacing the error?

@clarists Can you share the error message you are seeing?

Thanks for the update. I will close the ticket.


plugins:Add plugin for saying no to 'sir'

Reviewers Checklist

[x] Appropriate logging is done.
[x] Appropriate error responses.
[x] Handle every possible exception.
[x] Make sure there is a docstring in the command functions. Hint: Lookout for
botcmd and re_botcmd decorators.
[x] See that 100% coverage is there.
[x] See to it that mocking is not done where it is not necessary.

Okay ,sure I will do that in bit
On Tue, 23 Apr 2019, 10:47 pm Keshav Garg<EMAIL_ADDRESS>wrote:

@KVGarg requested changes on this pull request.
Please re-base your branch!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coala/corobo/pull/651#pullrequestreview-229686402,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHCL3B5FX3TOY5CRYOEGRMTPR5ADPANCNFSM4G432YBA
.

@kvgarg sure I will look after ur suggestions , actually I m quite busy for
a day or two soon I will look towards this pr
Thanks
On Tue, 23 Apr 2019, 11:06 pm Keshav Garg<EMAIL_ADDRESS>wrote:

@KVGarg commented on this pull request.
In plugins/no_sir.py
https://github.com/coala/corobo/pull/651#discussion_r277792542:

+import re
+from errbot import BotPlugin

+class no_sir(BotPlugin):

"""
Do not use sir
"""

def callback_message(self, msg):

   emots = [':D']

   match_sir = re.search(r'\bsir\b', '\bSir\b', msg.body)

   if match_sir:

       self.send(

         msg.frm,

         '@{}, Do not use sir in your conversation. {}'.format(

I guess we can frame a message somewhat like this
Hi @ :wave:! We don't use "Sir" in the community during the conversation. It's perfectly fine to call them via there usernames or handle. Also, If you to do such think you can better go with buddy :smiley:
Something like this the message can be framed!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coala/corobo/pull/651#discussion_r277792542, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHCL3B3LYBUB2IGAHLASYCLPR5CKDANCNFSM4G432YBA
.


TFTP Client service stops at Block#24

Hi!
I try to transfer a large size data to server by TFTP client service.
I use Synergy S7G2 processor, SSP 2.0.0 and IAR compiler.
I can transfer a small size data(ex. 2048bytes) to server.
But I can't transfer a large size data(Ex. 9MBytes).
The transmit always stops at 24th block.
Please give me a hint to solve.
Best regards.
#define WLAN_TFTP_SEND_TIMEOUT (500)
#define WLAN_TFTP_PACKET_SIZE  (512)

static NX_PACKET *my_packet;

extern NX_TFTP_CLIENT g_tftp_client0;

#if 1 //FOR TEST
static uint8_t buf[9*1024*1024+3];
#endif

UINT Tftp_Send(uint8_t *data_addr, uint32_t data_size)
{
	uint32_t status=0;
	UINT server_addr=0;
	uint32_t transfer_cnt=0;
	uint32_t remaining_size=0;
	uint32_t i=0;

#if 1 //FOR TEST
	for(int j=0; j < sizeof(buf); j++){
		buf[j] = j;
	}
	data_addr = buf;
	data_size = sizeof(buf);

#endif
	//calculate trans num
	if( (data_size % WLAN_TFTP_PACKET_SIZE) == 0){
		transfer_cnt = data_size / WLAN_TFTP_PACKET_SIZE;
	}else{
		transfer_cnt = (data_size / WLAN_TFTP_PACKET_SIZE) + 1;
		remaining_size = data_size % WLAN_TFTP_PACKET_SIZE;
	}

	//server address
	server_addr = IP_ADDRESS(192,168,1,3);

	// TFT Open
	status = nx_tftp_client_file_open(&g_tftp_client0, "/test.bin", server_addr, NX_TFTP_OPEN_FOR_WRITE, WLAN_TFTP_SEND_TIMEOUT);

	// Transfer data
	for(i=0; i < transfer_cnt; i++){
		// allocate
		status = nx_tftp_client_packet_allocate(&g_packet_pool0, &my_packet, WLAN_TFTP_SEND_TIMEOUT);

		if(remaining_size==0){
			my_packet -> nx_packet_prepend_ptr = data_addr + WLAN_TFTP_PACKET_SIZE*i;
			// Write pointer update
			my_packet -> nx_packet_length = WLAN_TFTP_PACKET_SIZE;
			my_packet -> nx_packet_append_ptr = my_packet -> nx_packet_prepend_ptr + WLAN_TFTP_PACKET_SIZE;
		}else{
			if(i == transfer_cnt-1){
				my_packet -> nx_packet_prepend_ptr = data_addr + WLAN_TFTP_PACKET_SIZE*i;

				// Write pointer update
				my_packet -> nx_packet_length = remaining_size;
				my_packet -> nx_packet_append_ptr = my_packet -> nx_packet_prepend_ptr + remaining_size;
			}else{
				my_packet -> nx_packet_prepend_ptr = data_addr + WLAN_TFTP_PACKET_SIZE*i;

				// Write pointer update
				my_packet -> nx_packet_length = WLAN_TFTP_PACKET_SIZE;
				my_packet -> nx_packet_append_ptr = my_packet -> nx_packet_prepend_ptr + WLAN_TFTP_PACKET_SIZE;
			}

		}

		// Transfer
		status = nx_tftp_client_file_write(&g_tftp_client0, my_packet, WLAN_TFTP_SEND_TIMEOUT);
	}

	/* close */
	status = nx_tftp_client_file_close(&g_tftp_client0);

	return status;
}

Hi @CYG01571 looks the packet points (nx_packet_prepend_ptr, etc) are not set correctly, here is my sample how to send data, could you update your code and test again?
VOID tftp_send(UCHAR *data_ptr, UINT data_size)
{
NX_PACKET   *my_packet;
UINT        status;
UINT        packet_length;
ULONG       i;

    /* Loop to send the data.  */
    send_data_length = 0;
    while(send_data_length < data_size)
    {

        /* Allocate a TFTP packet.  */
        status =  nx_tftp_client_packet_allocate(&client_pool, &my_packet, NX_IP_PERIODIC_RATE);
        /* Check status.  */
        if (status)
        {
            printf("ERROR");
            break;
        }

        /* Write ABCs into the packet payload!  */
        if (send_data_length + 512 < data_size)
            packet_length = 512;
        else
            packet_length = data_size - send_data_length;

        /* Write ABCs into the packet payload!  */
        status = nx_packet_data_append(my_packet, buffer + send_data_length, packet_length, &client_pool, NX_IP_PERIODIC_RATE);

        /* Check status.  */
        if (status)
        {
            printf("ERROR");
            break;
        }

        /* Write this packet to the file via TFTP.  */
        status =  nx_tftp_client_file_write(&client, my_packet, NX_IP_PERIODIC_RATE);

        /* Check status.  */
        if (status)
        {
            printf("ERROR");
            break;
        }

        send_data_length += packet_length;
    }
}

Dear bo-ms,
Thank you for your quickly response!
I resolved this issue for your advice.
I could send a large file to TFTP server!
Your advice was very useful because I didn't notice a thing that I should use nx_packet_data_append() API.
Best Regards.


Break library bundles into pieces

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Libraries usually provide large bundles or exports through index files. Importing bundles breaks webpack's ability to perform optimal code-splitting.
If the current behavior is a bug, please provide the steps to reproduce.

Here's a small repo describing the issue.
There is a library (lib) which exports four functions: a, b, c, and d and an app with two entry files entry1.js (E1) and entry2.js (E2). E1 imports functions a and c. E2 import functions b and c. Webpack is configured to create a commons chunk (C).
The output is:
E1:
E2:
C: a, b, c, d
Everything is moved into the commons chunk C if functions are imported from a bundle.
What is the expected behavior?
E1: a
E2: b
C: c
d should be shaken off.
This behavior can be achieved by importing functions from their source files, however, that is not very practical as source files might be in a different language, e.g. TypeScript.
If this is a feature request, what is motivation or use case for changing the behavior?
By breaking into pieces, each entry chunk may include specific parts of imported libraries, so the commons chunk doesn't get too big and contains only what's really common across entry points.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
<EMAIL_ADDRESS>RC1

reexporting other modules is great, but it also means all modules have to be executed/included. The ESM spec says that a module have to be executed even if none of it's imports is used. The modules could have sideeffects.


Circleci project setup

Setup CircleCI CI.

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


Streamline Contributing Instructions (e.g. use cli commands)

Status
Text instructions like
Fork this repository.
Clone your fork of the repository.

https://github.com/Constellation-Labs/tessellation/blob/develop/CONTRIBUTING.md#how-to-contribute
Expected
Create a fork via  https://github.com/Constellation-Labs/tessellation/fork
git clone https://github.com/<my-github>/tessellation/fork
*

Create a PR (follow instructions within PR template)
[...]

@abebeos I think your suggestion would be a small improvement over the current contribution instructions. We would be open to a PR with the changes if you'd like to contribute.


[staging-next] several gcc11 fixes

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

archiveopteryx fails ton aarch64-linux https://hydra.nixos.org/build/173824928

This should fix the aarch64 flag issue: https://github.com/NixOS/nixpkgs/pull/168942


Can't display SVG layer on IE11

https://lucas0819.github.io/
Here is my demo.
And it can work well on IE10, but can't display on IE11.
version:
IE: 11.1480.14393.0
openlayers: 4.6.5

It's because on IE11, it can't get image's height when create an element by new Image();
To get image's height i rewrite defaultImageLoadFunction function in options:
imageLoadFunction: function (image, src) {
  image.getImage().src = src;
  image.getImage().width = imgWidth;
  image.getImage().height = imgHeight;
}


Disable damage in chunks with shooting disable

See #9 for more information
Tested and working in freeplay lobby. Main menu lobby is not affected

Reverting Test command because it would not be used for testing

@OcZi FYI the project has not an extensive CI that prepares an isolated environment with a build for every pull request. Just select Client build from the CI, download the artifact, and then double-click on the jar


Database transactions

Should this PR work on iOS? I'm getting this error: Uncaught Kotlin exception: kotlin.native.IncorrectDereferenceException: illegal attempt to access non-shared <object>@xxxx from other thread

I think to make this work on iOS we'll need to freeze the callback blocks: https://youtrack.jetbrains.com/issue/KT-43566

I wouldnt freeze it, you should be able to enable the new memory model and disable freezing.
https://github.com/JetBrains/kotlin/blob/master/kotlin-native/NEW_MM.md
kotlin.native.binary.memoryModel=experimental
kotlin.native.binary.freezing=disabled


give every name token of the entire tree to the equip

i think this is safe because equipment is lowest priority already
please comment this really clearly so we can undo it if needed
this should be the very last step of the tree-name-moving-around shit

This issue replaces #575

This issue replaces #575


Only reload data that has changed

Right now, all data is reloaded after an update however it would be better if only data that changes reloads
Probably do something different with fetching new data with promises?

This is quite annoying and distracting behavior.  It would be great to prioritize this fix!


The top-level build.gradle uses antipatterns

This issue is somewhat of a sibling to #123934, but that issue is about the internal implementation of the Flutter Gradle Plugin. This one is about the template file that, upon flutter create, becomes android/build.gradle.
It is nothing very important, but IMHO, it's good to take note of this nonetheless. It can be useful to whoever might be working on Flutter x Gradle in the future.
Description
Using subprojects and allprojects in Gradle build scripts is considered to be a rather bad practice – it can lead to some problems and limitations in certain scenarios.
Excerpt from the build.gradle file template for an app:
allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

The subprojects in this snippet is reasonable and I don't know how we could get rid of it easily, but as for the allprojects, it's unneeded. I tested this by removing it in a few of my Flutter projects and nothing happened.
The subprojects and allprojects closures are used to apply configuration or tasks to all sub-projects or to all projects in a multi-project build. While this can be useful for applying common settings or tasks to multiple projects, it makes the buildscript less flexible.
One of the main drawbacks of using subprojects or allprojects is that it can limit the flexibility and customizability of individual sub-projects. If a sub-project needs to deviate from the common configuration or tasks, it may be difficult to do so without modifying the global build script. This can lead to conflicts and version control issues if multiple developers are working on the same build script.
Possible alternative
So I'd suggest removing it, because plugins also declare these repositories. If the current behavior is to be kept, Gradle has a new feature for this - dependencyResolutionManagement {}:

Instead of declaring repositories in every subproject of your build or via an allprojects block, Gradle offers a way to declare them in a central place for all project.
Repositories used by convention by every subproject can be declared in the settings.gradle(.kts) file:

dependencyResolutionManagement {
    repositories {
        mavenCentral()
        google()
    }
}

Learn more here about this feature.
FWIW, Android Studio updated its templates to use dependencyResolutionManagement – learn more here.

Hi @larssn 👋🏻
I'm just an open-source contributor, not a Googler, so I don't know, but if I were to guess it'd be that there are just many more important things to work on. Also, I feel like developers mostly don't care about build tooling, as long as it doesn't break.
I like to tinker with developer tools, so I've been trying to make the Gradle x Flutter situation better for the last year or so :)

And I greatly appreciate you for it 😊


yii2-authclient - Facebook authclient does not work with enablePrettyUrl = false

It gives this error:
Request failed with code: 400, message: {"error":{"message":"Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request","type":"OAuthException","code":100}}

Steps:

Install yii2-basic-app from scratch, adding yii2-authclient into composer.json
Set up component->authClientCollection with facebook credentials
Add AuthChoice widget to view
Add auth action to SiteController::actions()

(So 2-4 are the exact steps listed in https://github.com/yiisoft/yii2-authclient#quick-start)
If I add a .htaccess file, enable pretty url, and set showScriptName = false, then it works properly.

The problem with this is that Yii itself gives a 404 error for a URL like the following:

The problem with this is that Yii gives a 404 error on the following URL:
http://backend.aceepo.com/index.php?r=module%26set%3Dpayment%26module%3DAuthorizenet%26action%3Dedit
If I switch it to the following, it resolves just fine:
http://backend.aceepo.com/index.php?r=module&set=payment&module=Authorizenet&action=edit

See https://github.com/yiisoft/yii2/issues/3656#issuecomment-341172034


FIX Updated to implement new interfaces & updated to store more than just the generated secret in session

Supersedes #5


Update Program.cs for usability and a tyop

detecte is changed to detected; typo
\t changed to , in above so that the spacing is the same for the headers and the text output
added , to console writeline to delimit the output and changed the "on, de" to not have a comma so the output can be put into a csv seamlessly for examination
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Verified the change is required. The article and code uses , as a separator but the header code was using a tab.
Fixed merge conflict.


Allow access to the PixBuf pixels without an unsafe.

Has an API break.
Closes #75

Is it ok for you @EPashkin and @sdroege?

That might actually not be enough, you could have two clones of the same object. Access one mutable and at the same time modify via some function on the other

Isn't Rc<RefCell<T>> supposed to prevent such things?

In a way, yes. But that doesn't help us here because we have GObjects and their refcounting in the middle of everything.

I don't know what exactly you're talking about :) Can you write down how you want to solve this specific bug? It's an inherent limitation of GObject that there is reference counting and everything has interior mutability, which conflicts with (not only) mutable borrowing of contained data (unless that data is completely immutable).

I clearly didn't understand the issue entirely. Damn... We're just doomed on this one I suppose...

As there are functions changing the underlying memory, the function borrowing the immutable slice is also unsafe btw. So yes, we're doomed here and the code in the PR is wrong, and the current code is also wrong and the only valid thing to do here is returning a raw pointer to the data.
The gdk-pixbuf people should take a look at GStreamer for how to provide a C API that does this things safely and bindings compatible.

It would indeed but who has enough time to do it? :)

Doing it like in cairo::ImageSurface should be fine here, if someone wants to update the patch like that

So I have to mimic ImageSurfaceData? Will take a look when I have a time.

So I have to mimic ImageSurfaceData? Will take a look when I have a time.

That should work, yes


Can't paste embed code

Using 2.0.4, the plugin works fine with pasting youtube urls, but the dialog does not allow me to type or paste into the embed code into the larger text area.
The area is not disabled/greyed out (unless I begin typing into the URL field), it just doesn't accept any input.

Try to update to the last version.


GH-1278 Complete implementation of cilium identity get

Complete the implementation of cilium identity get
Add a unit test for cilium identity get

NOTE: cilium identity get --list still returns only the reserved identities. This is a limitation of this patch. Fixing this requires changes to the API, which will be done in a separate ticket/PR.

Please amend your commit so that it says:
Signed-off by: Ashwin Paranjpe<EMAIL_ADDRESS>at the end. Also, please the beginning of your commit that shows the area of code that was changed, e.g.:
cilium/cmd: finish implementing \cilium-identity-get``

@ianvernon amended the commit. Fixed the problem with the build (make tests-common was failing).


Errow while running with hashtag

[] => Finding Not Now button with xpath: //button[text()="Not now"]
[] => Do not save login info: True
[] => Opening target #koramangala
[] => [open_target]: Attempt - 1
[] => [target: #koramangala] No. of posts found: 162638
[] => [target: #koramangala] Checking if #koramangala is a private account
[] => Failed to find text: This account is private
[] => Failed to find text: This Account is private
[] => Failed to find text: This Account is Private
[] => [target: #koramangala] Account not private
[] => [target: #koramangala] Opening first post
[] => [target: #koramangala] Number of posts to like: 10
[] => [target: #koramangala] Liking post: 1
[] => [like]: Attempt - 1
[*] => [like]: Attempt - 2

We've noted a change in the interface when hashtags are opened. This is going to be implemented soon in the code.

The bot is not working for hashtags


Fix date format for Czech

See #2016.

Hmm I don't understand why the tests passed if I did not fix them. Any ideas?

@petrbela, your thoughts, please?

It seems l is not an option in longDateFormat. From looking at other parts of the code, there isn't any shortDateFormat; maybe the short versions are generated dynamically from the long?
So far, this change doesn't change the behavior (as confirmed by the test), as the l most likely is getting ignored.

Yeah, I was thinking the same thing. I did see an l option in some other language file though (don't remember which).

@mj1856, can we change l separately?

I thought you could, but I can't find it... @ichernev ?

You should be able to change l by itself. It's in the following function:
    function longDateFormat (key) {
        var format = this._longDateFormat[key],
            formatUpper = this._longDateFormat[key.toUpperCase()];

        if (format || !formatUpper) {
            return format;
        }

        this._longDateFormat[key] = formatUpper.replace(/MMMM|MM|DD|dddd/g, function (val) {
            return val.slice(1);
        });

        return this._longDateFormat[key];
    }

None of the locales do it that I can tell, but it doesn't mean you couldn't.
In fact, the following code works just fine:
//change the 'l' format to be month abbreviation, just to make it obvious that we aren't falling back to default
moment.updateLocale('en', {longDateFormat: {l:'MMM'}})
//format something with `l`
moment().format('l')
"Apr"

If you were going to introduce this to this locale, I would definitely explicitly test it.

@maggiepint is right, just using l should work. Just make sure to modify src/locale/cs.js and src/test/locale/cs.js

Any progress on this. The modifications need to be made to different files. The change is fine, but needs a unit test.

@enumag Are you working on this?

@petrbela No.

Close in favor of #3237.


Limit context output for stack trace output of errors in IPCWorker/IPCServer scenario

Currently, the context that is output for stackframes via raise RemoteProcessError("Request failed") from pickle.loads(error) is by far too long. Most likely, this can be configured somewhere.
Goal would be that it is easy to see the stackframes to quickly search for the last stack frame before entering library code.

I am also not sure whether recursive raise xxx from e pass through RemoteProcessError correctly. I am missing the _e here in my stack trace:
>               raise RuntimeError(msg) from _e
E               RuntimeError: Failed putting copied lazy table (__cpy_)t1 (schema: 'pd_mssql_pytsql_stage_1__tmp.dbo') in place of alias.


liqo-fabric crashLoopBackOff when metrics.enabled=true

What happened:
After deploying liqo v1.0.0-rc.1 with the Helm Chart, the liqo-fabric pods are in crashLoopBackoff state ; logs show the following error:
I0903 11:35:55.555675       1 controller.go:240] "Shutdown signal received, waiting for all workers to finish" controller="routeconfiguration" controllerGroup="networking.liqo.io" controllerKind="RouteConfiguration"
I0903 11:35:55.555692       1 controller.go:242] "All workers finished" controller="routeconfiguration" controllerGroup="networking.liqo.io" controllerKind="RouteConfiguration"
E0903 11:35:55.555521       1 kind.go:68] "failed to get informer from cache" err="Timeout: failed waiting for *v1beta1.InternalFabric Informer to sync" logger="controller-runtime.source.EventHandler"
I0903 11:35:55.555754       1 controller.go:242] "All workers finished" controller="pod" controllerGroup="" controllerKind="Pod"
I0903 11:35:55.555818       1 internal.go:526] "Stopping and waiting for caches"
I0903 11:35:55.556014       1 internal.go:530] "Stopping and waiting for webhooks"
I0903 11:35:55.556034       1 internal.go:533] "Stopping and waiting for HTTP servers"
I0903 11:35:55.556059       1 server.go:43] "shutting down server" kind="health probe" addr="[::]:8081"
I0903 11:35:55.556174       1 internal.go:537] "Wait completed, proceeding to shutdown the manager"
Error: failed to start metrics server: failed to create listener: listen tcp :8080: bind: address already in use

Usage:
  liqo-fabric [flags]
[...]

E0903 11:35:55.556744       1 main.go:79] failed to start metrics server: failed to create listener: listen tcp :8080: bind: address already in use

I've not seen any place to configure ports, are they hardcoded ?
What you expected to happen:
The liqo-fabric pods should start with no errors
How to reproduce it (as minimally and precisely as possible):
Deploy liqo helm chart v1.0.0-rc.1 on AKS cluster, with enable-ha and enable-metrics
Environment:

Liqo version: v1.0.0-rc.1
Liqoctl version: not used
Kubernetes version (use kubectl version): 1.30.3
Cloud provider or hardware configuration: AKS
Node image: Ubuntu 22.04.4 LTS
Network plugin and version: Cilium
Install tools: Helm
Others:

Hello, I can't explain why, but all pods were eventually running fine this morning. I have tried to reproduce the issue without success, so I'm closing this.


CLOWNFISH-40 Make LockFreeRegistry private

LockFreeRegistry is needed only to achieve thread-safety for the Clownfish class registry; it should not be publicly exposed.
Furthermore, it should be implemented in plain C and without using Clownfish object system features in order to simplify bootstrapping.

+1 to merge.


Add connection type param to hangUp()

Fixes https://github.com/libp2p/js-libp2p/issues/299
Note: Requires https://github.com/libp2p/js-libp2p-circuit/pull/41 for tests to pass

@dirkmc I reran CI so the latest libp2p-circuit would get pulled in. Looks like there are some failures, can you take a look at those?

Thanks Jacob, I’m in Nicaragua this week but I can take a look when I’m
back next Wednesday
On Wed, Jan 2, 2019 at 2:37 PM Jacob Heun<EMAIL_ADDRESS>wrote:

@dirkmc https://github.com/dirkmc I reran CI so the latest
libp2p-circuit would get pulled in. Looks like there are some failures,
can you take a look at those?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/libp2p/js-libp2p-switch/pull/298#issuecomment-450977818,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKUpMI5GDvrv9jR-xVAGv0OvagKEEaYks5u_Rh5gaJpZM4ZfCzh
.

@jacobheun with the refactor, these need to be remade or closed. I'll let you do the review

Closing this as tagging will be needed for this and it will likely change the structure of this significantly.


soc: riscv: riscv-privilege: telink: Added Telink b92 soc PMP support

Added the generic RISCV PMP support for B92 SoC series.

Can we create Telink config option for enabling memory protection feature?
Disable it for default (for now) and selects all features you provides.
In tht case it's safe entry point for memory protection implementation.

Can we create Telink config option for enabling memory protection feature? Disable it for default (for now) and selects all features you provides. In tht case it's safe entry point for memory protection implementation.

Yes, we can. But the purpose of it is not clear. This is just a description of CPU architecture. So we are not enabling the implementation of user space or memory protection.
Also the ROM size and RAM size is not changing in case if this option is enabled.
The SiFive vendor just adds this option to his own core description.
So I think for development process we may go the way you suggested, but after we finish, we need to prepare our code in common way.