Bluebird Always Defaults to Debug Config w/ Webpack

What version of bluebird is the issue happening on?
Bluebird 3.5.1

What platform and version?
Windows 10 64-bit
Node v6.11.1
NPM 3.10.10

Did this issue happen with earlier version of bluebird?
At least as early as 3.4.x

When using Bluebird with Webpack 2.x/3.x, the JavaScript pulled in always comes from node_modules/bluebird/js/browser/bluebird.js. This originates from:
https://github.com/petkaantonov/bluebird/blob/0da7d15c7241857fc2b853393fb8dd1ab3bbd5d7/src/debuggability.js#L21
But in bluebird's unminified JS  __DEBUG__ was replaced with a true when it was built. As a result, debugging will always default to true consequently enabling longStackTraces and other options which may be undesired by the developer.
A workaround for the problem is to explicitly pass debug options via Promise.config(), however if the developer does not specify all relevant options then they will all be enabled by default. A second workaround is to set the BLUEBIRD_DEBUG environment variable to 0. Both of these solutions contradict the defaults specified in the Bluebird API docs: http://bluebirdjs.com/docs/api/promise.config.html#promise.config
Created a repo to demonstrate:
https://github.com/Cleod9/minimal-bluebird-webpack-debug-issue

Honestly I've run bluebird on dozens of frontend applications and I've always kept the stack traces turned on because at the client (not server) debugging issues in production was always a much bigger problem for me than performance.

Luckily there was a workaround for this, but do know that longStackTraces can be a real showstopper for games have specific memory requirements and a demanding frame-rate. We had been dealing with memory issues for years and sadly this was the biggest contributor. I personally feel this should be off by default, and it was apparently meant to be off, however unfortunately the binary for this package had __DEBUG__ baked in as true :/

Luckily there was a workaround for this

What do you mean? We explicitly allow you to build without long stack traces - what behavior would you prefer?

I created a minimal use-case repo to demonstrate the problem late last year. Again to put it simply, the docs claim that all of these debug values default to false:
http://bluebirdjs.com/docs/api/promise.config.html#promise.config
However this is not the case due to the problem I demonstrate in the repo. You have to explicitly set them to false or the entire library executes in debug mode. I'm not going to push to change the defaults but I do think the docs should address this so that devs don't rule out Bluebird too quickly when investigating memory leaks

Again to put it simply, the docs claim that all of these debug values default to false:

The first sentence after the function signature is:

Configure long stack traces, warnings, monitoring and cancellation. Note that even though false is the default here, a development environment might be detected which automatically enables long stack traces and warnings.

I can make that bigger or bolder but I'm not sure there is anything else actionable on our behalf. I agree this behaviour is potentially confusing but the alternative is more confusing and bluebird has always opted for what we think helps users.
I apologize for your bad UX and I'm open to ways to fix it.

And I just noticed the issue is from 2017 😮 sorry for the late reply!

@benjamingr No worries! Thanks for taking the time to respond.
So I'm just curious, is a "debug environment" the default in my minimal use case? I disregarded text since I assumed that wasn't the case, so I might be missing something here with webpack or something

Even with NODE_ENV=production, output is still:
Debugging value: true
Done.

Remember that a true is baked into node_modules/bluebird/js/browser/bluebird.js which messes with the defaults. And that's the file that appears to be loaded when require()'d regardless of environment vars

If you use bluebird in browser then no matter what value set in environment variable because it is not available inside browser. Also util.env("BLUEBIRD_DEBUG") always return undefined which is not equal to 0 so this:
var debugging = !!(util.env("BLUEBIRD_DEBUG") != 0 &&
                        (true ||
                         util.env("BLUEBIRD_DEBUG") ||
                         util.env("NODE_ENV") === "development"));

will always set debugging to true.
So we have debugging mode forever.

@Matrosskin Yup, that is absolutely correct. Have you tried my workaround by explicitly setting those environment variables via Promise.config()?
As with most open source repos I assume perhaps the contributors are waiting for us to submit a PR (which may or may not ever get merged judging by the current queue). Unfortunately I don't have the time to craft the proper solution myself, but as long as this ticket is open I hope others are able to at least find this thread

@Cleod9 yes, I also set required options via Promise.config(). Today I just returned to the issue with hope to see the fix :)

node_modules/bluebird/js/browser/bluebird.js is the build for development
node_modules/bluebird/js/browser/bluebird.min.js is the build for production

@petkaantonov what does your message should mean?

browser/bluebird.js has always debug values, this is intended as you wouldn't use non minified file in production
browser/bluebird.min.js has debug values disabled because you use minified file in production
I don't know how to make webpack use different file, the browser field in package.json only allows 1 file to be chosen, and it is currently the debug file (browser/bluebird.js).

I see. But such configuration confuse me. Possibly it is just my own opinion - I expect that the browser/bluebird.js and browser/bluebird.min.js have same behavior. I expect that the min version is just smaller and less readable. So I expect that I can work with any file in same way. But, with bluebird it was wrong assumption which cause a additional time for investigation of different behavior.
Also, if we use webpack then it often mean that we use own config to minify script, so (again my personal opinion) I would rather use not minified version - it allow to debug every script during developing the own app, and in production it still will be minified.
Also, as you mentioned, in package.json can be configured only one script - as I understand it means I need some additional logic in webpack to use min verssion instead of version from package.json, is not it? So the environment and/or configuration of of my project to develop and to build for production will be a little different - it does not look fine for me.
Sorry if wrong somewhere, I have not much practice. Can you help me if I miss something?

The differences between the browser files is documented here:http://bluebirdjs.com/docs/install.html#browser-installation
For webpack: http://bluebirdjs.com/docs/install.html#browserify-and-webpack The instructions imply usage of Promise.config is needed

I updated the http://bluebirdjs.com/docs/install.html#browserify-and-webpack docs to make it more clear.

Also updated http://bluebirdjs.com/docs/api/promise.config.html#promise.config

Awesome, thank you!

The documentation update is much appreciated, thanks for the follow up!


Azure Func deploy in ACA - Virtual IP

Hi,
I did attempt to deploy an azure function app in ACA via CLI and receive the following error message:
ERROR: Invalid input. Unable to create a function app in Azure Container Apps Environment configured with Virtual IP as Internal. Currently only External Virtual IP is supported.
I am able to deploy a web api as a container, however, no function app.
What would be the reason?
Thanks

Hi @mehmetaltuntas , this feature work is in progress. Should be out soon!! Will update this thread once the support is out!

Hey @raorugan, any update regarding this?

This will be released on May 22. Please stay tuned.

we are ahead of our promised date . This feature is out now!! do check out and let us know your experience - https://learn.microsoft.com/en-us/azure/container-apps/networking?tabs=workload-profiles-env%2Cazure-cli


Potential anti-troll help mechanic:

So the primary way trolls are trolling right now isn't via nuking the x00 levels, it's wormholing the x98/x99 levels so we never hit a x00 level.
Solution?   If every script running saved their tactical nuke for the 2-4 levels before the x00 boss, I think we could reduce the amount of wormholes that are screwing us over.  And every x00 level has LNs used, so the nuke is going to be immediately reset then anyway.
Thoughts?

If i'm not wrong, overkill damage is recorded and applied to following levels. If everyone nukes the 98-99 wave it can very well skip the 100th level every time.

I thought that was just for click damage.  The tactical nuke at least says 'damage to current target'.  Could also use a shitton of cripple monsters on x98-99, since those just reduce a monster to 1hp, so there is no carry-over.  Obviously can't use Napalm.  Not sure about cluster bombs, since it's not single target.

even then lag would have nukes going off on the x00 level

Or disable the nukes (and other spells a few levels before x00. I'm not sure, but i think almost everybody has a script, so maybe the trolls have them too.


Fix typos and simplify some phrasing on the ft component doc

Thank you for this excellent thorough editing Carol! :D


Linkify breaking at web urls with @ in them

Some links nowadays have @ in them. For example: https://medium.com/@ainiesta/how-instagram-closed-my-account-and-gave-it-to-a-football-celebrity-625a6a770eb3 or http://naya.com.np/@mandala/post/5b62ff340a9451b3bdda9d89be5c61be
Linkify ignores everything after @

This is a duplicate of #33 and has already been fixed in 2.0.


feat add Grafana explorer integration with pyrra UI

Hi guys recently we start to use pyrra, with grafana mimir .
It possible configure prometheusExternalUrl to use grafana explorer instead of the prometheus dashboard for see queries directly in grafana?

May be the Grafana SDK has some methods to build the URL properly. We could make a bit of research on this regard

you can do this
https://grafana.foobar.com/explore?orgId=1&left={"datasource":"AbfTenkVk","queries":[{"expr":"vector(1)"}]}

You'd need a way to pass in orgId and datasource
Without datasource it'll use the default or whatever you selected last to explore from.
I'm happy to attempt a PR if people are ok with passing those in. Not sure of another way to make grafana be an external link to the data though

I think for that you need to capture those variables by using flags. IMHO they could be something like:
--is-grafana-gui (or something similar)

--grafana-organization-id
--grafana-datasource

Sounds like something we can explore, yes. 👍
I wonder, do you think the Prometheus external links should still show too, or would this replace those with opening in Grafana entirely?

Ok, sounds good to me! 👌

Ok, sounds good to me! 👌

to me too. It makes sense 🙂

Any updates here? We expose a central grafana that aggregates hundreds of prometheus instances, and do not expose Prometheus. This would be a great way to connect the two systems.


Possible to make event.preventDefault() into an option?

Right now a lot of shortcuts like Ctrl+S, Ctrl+R, etc trigger the default browser behavior. When mapped to custom hotkeys the programmer generally would want to skip this for which we can call event.preventDefault();
But I was thinking that we can add a modifier like this to make this the default behavior and save some extra code like this:
<template>
  <span v-hotkey.prevent="keymap" v-show="show">Not the .prevent</span>
</template>

What do you guys think?

@san-kumar, were you able to fix this in your app? Can you share the solution?

LGTM, would you work for that feature?


update godep-save.sh to enable restore some pkg before save

Add pre-restore mechanism in godep-save.sh, make sure we correctly update pkg like k8s.io/client-go.
as @resouer mentioned in #93 .
This is enabled by adding --pre-restore flag, since we only need this when update these particular pkg.
Signed-off-by: Crazykev<EMAIL_ADDRESS>

This change is

/lgtm


tsconfig.paths not followed when validating path-aliases

Hello thanks for adding this plugin! For react-native this plugin is very valuable for direct asset imports.
Issue
tsconfig paths are not being considered valid path imports.
Expected
tsconfig Paths aliases do not error when used to import svgs.
Example
Folder structure:
src
src/assets.d.ts
src/assets
src/assets/Spinner.svg
src/component/Component.tsx

tsconfig.json
{
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
      "assets/*": ["src/assets/*"]
    }
  },
}

declarations
declare module '*.svg' {
  const content: React.FC<React.SVGAttributes<SVGElement>>
  export default content
}

eslint config (with react-native references)
module.exports = {
  root: true,
  extends: [
    '@react-native-community', // adds typescript support in this config
    'prettier',
  ],
  plugins: ['validate-declared-imports'],
  rules: {
      "validate-declared-imports/no-unresolved-declared-imports":
          ["error", {
              "fileExtensions": [
                  ".svg", // svg
                  ]
                }
          ]
        }
}

Component.tsx
// opens a definitions window and shows both the relative path import and declaration file
import ../assets/Spinner.svg

// Only resolve the assets.d.ts file
import assets/Spinner.svg

// bad imports that do not error (until runtime)
import ../assets/Spinner1.svg
import ../assets/123/Spinner.svg

There is a PR opened to address this issue.

Resolved in #4 :)


Update indexedDBHelper and DBWrapper

R: @jeffposnick @addyosmani @gauntface
This PR updates our DBWrapper implementation to use a WIP general-purpose IDB wrapper library I'm developing. Note that in this PR I've just updated the code to the new API; I haven't taken advantage of any of the new features. We can do that in another PR.
Notable changes:

I've removed the indexedDBHelper export and now just export a DBWrapper class, which packages can consume directly.

The DBWrapper class handles opening the connection behind the scenes (prior to making any transactions), so our code doesn't have to worry about it. This allows us to create instances in constructor functions since it happens sync.

// No connection is made by doing this.
const db = new DBWrapper('my-db', 1);

// This calls `await db.open()` in the background
const entries = await db.getAll('my-store');

DBWrapper has a general purpose query function called getAllMatching(), which is similar to getAll() but it supports specifying an index, direction, key range, and count (like "limit" in SQL) as well as optionally returning the keys (useful for autoIncrement:true).

There are places in our code where we call getAll() and then filter the results. This is inefficient since in many cases we can do the filter via the getAllMatching(). For example, workbox-cache-expiration can request only entries with timestamps greater than X by doing something like this:
const expiredEntries = await db.getAllMatching('store-name', {
  index: 'timestamp',
  query: IDBKeyRange.lowerBound(X),
});

Or if you wanted to get just the entry with the newest timestamp, you can do something like this:
const [oldestEntry] = await db.getAllMatching('store-name', {
  index: 'timestamp',
  direction: 'prev',
  count: 1,
});

Both of these are much more efficient than doing getAll() since they only search/return a subset of the object store.

BTW, this PR has a total prod size increase of 0.75K. If I remove some of the class methods that we're not using, I can shave 0.58K off of that (making the delta only +0.17K). However, my concern is that if I release this as a standalone library, I'd almost certainly want to keep those methods included.
What do folks think about the trade-offs here?

I've removed some of those unused helpers, and now the total size has actually gone down 150B \o/.

LGTM from me - can't approve cos mobile site is Le pants.


feat(server): Using quantize_config.json instead of GPTQ_BITS env variables.

Current PR is not great because we're side stepping the
Weights.__init__ but Weights shouldn't requires anything related
to the config or the model_id as it aims to be a simple Wrapper
over multi file loading.

Ideal solution would be to use something like Rust enum
enum Quantize{
  Bitandbytes(Bitsandbytes),
  GPTQ(bits: usize, groupsize: usize)

And passing that around during load. Unfortunately we don't
have access to this, so for now, side-stepping seems easier.

Re-enabling groupsize<0 with exllama (confirmed it works.)

Helps #601
In next steps we should make sure our quantization script uses that format and make it standard.
What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

Merging. It's only the flaky tests from exllama kernels. We're fixing their flakyness in a different PR.


Add support for PHP 7.2

just a sec, I'll submit my fixes as a PR

sorry, didn't notice this is a PR... whoops

php 7.1 and 7.2 need to be registered to .travis.yml

@samsonasik Where can I take a look how it's done, so that I can complete this?

there is .travis.yml file which the php versions can be registered, for example https://github.com/zendframework/ZendDeveloperTools/blob/master/.travis.yml#L26-L35 , you can add php 7.1 and php 7.2 there after php 7

@webimpress Is there anything else I can do to help?

@thexpand It would be nice if you can update the .travis.yml configuration. So basicaly we need define LEGACY_DEPS (see for example: https://github.com/zendframework/zend-servicemanager/blob/master/.travis.yml#L22) - I can't say what it should be in LEGACY_DEPS list in case of this repo - you need to figure it out based on current build logs.
Then we need update these legacy deps, as it is here:
https://github.com/zendframework/zend-servicemanager/blob/master/.travis.yml#L62-L63
Then we should be able to update composer.lock to the latest version (by running composer update) and all build should be fine.

Thanks, @thexpand. I have updated the Travis configuration, and also upped the minimum supported
version of PHPUnit so that it will work correctly with PHP 7.2; last tests passed all versions!

@weierophinney Thanks for helping out. I was extremely busy lately and moreover I was not quite sure how to update the Travis file. Could you explain to me your changes?

Detailed explanation as always :wink: Thank you once again, @weierophinney


Introduce token from variable

Change behaviour of the easy_jwt parameter:
easy_jwt - module operation mode
Syntax: easy_jwt  mode [variable]
Default: mode=off
Context: location
Turns on module functionality.

mode is one of
    off - module inactive (default)
    parse - only parses JWT
    hs256 - check JWT only HS256 signature if found in JWT
    rs256 - check JWT only RS256 signature if found in JWT
    hmac  - check JWT HMAC only signature if found in JWT (based on 'alg' from JWT header)
    pub   - check JWT priv/pub key signature if found in JWT (based on 'alg' from JWT header)
    all   - check JWT with any supported algorithms (based on 'alg' from JWT header)

variable is a name of nginx variable to extract token from.

variable also obsoletes easy_jwt_cookie directive. Since variable could be set to $cookie_[name]

another bug, found by cppcheck -j"$(nproc)" --verbose --force --enable=all --suppress=variableScope
ngx_http_ejwt_module.c:921:9: style: Redundant initialization for 'var'. The initialized value is overwritten before it is read. [redundantInitialization]
    var = cf->args->elts;
        ^
ngx_http_ejwt_module.c:919:44: note: var is initialized
    ngx_str_t                         *var = cf->args->elts;
                                           ^
ngx_http_ejwt_module.c:921:9: note: var is overwritten
    var = cf->args->elts;
        ^

Thank you @RekGRpth !!!

Thank you for token from variable


Add id to RPC request body

This might be a Viem thing so let me know if I should file this there.
Request to Ankr's RPC ( https://rpc.ankr.com/filecoin_testnet ) while backfilling errors out as it needs the id param.
Example,
Request:
{

    "method": "eth_getLogs",
    "params": [
        {
            "address": [
                "0x0b9737ab4b3e5303cb67db031b509697e31c02d3"
            ],
            "topics": [],
            "fromBlock": "0x30f53",
            "toBlock": "0x3133B"
        }
    ]
}

Response:
{
    "jsonrpc": "2.0",
    "error": {
        "code": -32600,
        "message": "invalid request"
    },
    "id": null
}

Corrected Request:
{
    "id": "42",
    "method": "eth_getLogs",
    "params": [
        {
            "address": [
                "0x0b9737ab4b3e5303cb67db031b509697e31c02d3"
            ],
            "topics": [],
            "fromBlock": "0x30f53",
            "toBlock": "0x3133B"
        }
    ]
}

Response:
{
    "jsonrpc": "2.0",
    "result": [
        {
            "address": "0x0b9737ab4b3e5303cb67db031b509697e31c02d3",
            "data": "0x",
            "topics": [
                "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
                "0x0000000000000000000000000000000000000000000000000000000000000000",
                "0x000000000000000000000000661c77a0598d0d61f01cb6575423fad50881241b",
                "0x0000000000000000000000000000000000000000000000000000000000000001"
            ],
            "removed": false,
            "logIndex": "0x0",
            "transactionIndex": "0x0",
            "transactionHash": "0xbd5656cd2e7a675a33981818d5d86f06995916b3304efd6a6da6433f294cff70",
            "blockHash": "0xa3ec2bb6ccdcf673bdb6339f2ec2f35e8ae05f1ac23710c9df6b0cb5d5c0b78c",
            "blockNumber": "0x30f53"
        },
        {
            "address": "0x0b9737ab4b3e5303cb67db031b509697e31c02d3",
            "data": "0x000000000000000000000000661c77a0598d0d61f01cb6575423fad50881241b00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000002e637265617465207461626c65206865616c7468626f745f333134312028636f756e74657220696e7465676572293b000000000000000000000000000000000000",
            "topics": [
                "0xfe0c067afc4fe17adcf4cfa139aabad6dc30dd86dfe39fb2b858961637156cdd"
            ],
            "removed": false,
            "logIndex": "0x1",
            "transactionIndex": "0x0",
            "transactionHash": "0xbd5656cd2e7a675a33981818d5d86f06995916b3304efd6a6da6433f294cff70",
            "blockHash": "0xa3ec2bb6ccdcf673bdb6339f2ec2f35e8ae05f1ac23710c9df6b0cb5d5c0b78c",
            "blockNumber": "0x30f53"
        },
        {
            "address": "0x0b9737ab4b3e5303cb67db031b509697e31c02d3",
            "data": "0x000000000000000000000000661c77a0598d0d61f01cb6575423fad50881241b0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000028696e7365727420696e746f206865616c7468626f745f333134315f312076616c756573202831293b00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000c000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "topics": [
                "0x6de956d2cb2e161f8c91c6ae7b286358c7458d5ad5e26ea2d55330fbe282839c"
            ],
            "removed": false,
            "logIndex": "0x0",
            "transactionIndex": "0x1",
            "transactionHash": "0x797681c20f498a6c8648154461d9eaf9ea3fb06621fd3ae2dbc64e1942c77dbc",
            "blockHash": "0xb8f4c2dd84a15830774bc88ae25f5ba604044f04f74570bff819f28b745da770",
            "blockNumber": "0x30f55"
        }
    ],
    "id": "42"
}

Weird. viem definitely appends an id to every RPC request.

@jxom the error that gets logged containing the request while backfilling doesn't have the Id.

@anudit Could you share a screenshot of the logged error?

@0xOlias @jxom

Source Code: https://github.com/anudit/tableland-subgraph/tree/main/ponder

Hey @anudit - were you able to get to the bottom of this?

@0xOlias Dug a bit deeper into this, the id param requirement comes from the louts node of Filecoin EVM.
Running into the following error currently, As you can see the logged request body in the error does not have the id param.
error    - Block backfill queue error
Task:
  blockNumberToCacheFrom:  2728630
  blockNumber:             2729629
  requiredTxHashes:        [object Set]
Stack: RpcError: RPC Request failed.

URL: http://<IP_ADDRESS>:8545/api/fvm-rpc
Request body: {"method":"eth_getBlockByNumber","params":["0x29a69d",true]}

Details: failed to retrieve messages and receipts: error loading messages for tipset: [bafy2bzaceavk5owagavmx4sjpnwowwxjgede3ax6e6xmvzbqasqrwmcvnb4qi]: failed to load state tree at tipset [bafy2bzaceavk5owagavmx4sjpnwowwxjgede3ax6e6xmvzbqasqrwmcvnb4qi]: failed to load state tree bafy2bzacedrufu6ega5dk23mfeqcgvkdcv3xs4cjnut2q6tfbyp74evo4fnqi: failed to load hamt node: ipld: could not find bafy2bzacedrufu6ega5dk23mfeqcgvkdcv3xs4cjnut2q6tfbyp74evo4fnqi
Version<EMAIL_ADDRESS>    at Object.http (/Users/anudit/Documents/GitHub/tableland-subgraph/ponder/node_modules/.pnpm/viem@0.1.8_typescript@5.0.4/node_modules/viem/dist/chunk-SWM5USHJ.js:3306:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async request (/Users/anudit/Documents/GitHub/tableland-subgraph/ponder/node_modules/.pnpm/viem@0.1.8_typescript@5.0.4/node_modules/viem/dist/index.js:326:30)
    at async withRetry.delay.count.count (/Users/anudit/Documents/GitHub/tableland-subgraph/ponder/node_modules/.pnpm/viem@0.1.8_typescript@5.0.4/node_modules/viem/dist/chunk-SWM5USHJ.js:2912:16)
    at async attemptRetry (/Users/anudit/Documents/GitHub/tableland-subgraph/ponder/node_modules/.pnpm/viem@0.1.8_typescript@5.0.4/node_modules/viem/dist/chunk-SWM5USHJ.js:2852:22)

@0xOlias Debugging this more with the FEVM team, Looks like a node issue. Will update as I get more information, feel free to close this in the meanwhile.


storage: NewReader fails with retryable error

Fails at: f, err := bkt.Object(file).NewReader(ctx)
err is「Get https://storage.googleapis.com/...: http2: no cached connection was available 」

This was fixed in go 1.8.


Why there is no positional embeds in the flow decoder transformer layers inputs?

the flow model in cosyvoice, its encoder Conformers contains position embeds while in its decoder transformers, I see no such addition. is that means no benifit  here in flow-matching? sorry for it if I did not find the code.

well decoder is from matha-tts, we haven't tested whether position embedding can help in decoder, maybe it can

Yes there is no position in macha, may be it assume the intput hidden had contain such info?


Update testcontainers-scala-postgresql, ... to 0.40.3

Updates

com.dimafeng:testcontainers-scala-postgresql
com.dimafeng:testcontainers-scala-scalatest

from 0.40.2 to 0.40.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.dimafeng" } ]

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

Superseded by #206.


Utilising tags set on markdown cells

Is your feature request related to a problem? Please describe.
When using jupyter-notebook generated document, toggle-button only works on code cell, but not markdown cell, if metadata of cell changed to
{"tags": ["hide_cell"]}

Toggle-button still works if using something like
    ```{toggle}
    Something not to be divulged
    ```

However, this is somehow not convenience.
In my first edition of issue, I does not know there could be four ```` before {toggle} (T.T)
So just ignore the following text in the un-edited issue:

Furthermore, I want to write code inside toggled text:
    ```{toggle}
    ```python
    np.allclose(np.exp(complex(0, 1) * np.pi) + 1, 0)
    ```
    That's one of many Euler's fomulars.
    ```

That kind of code is probably not working well.

Describe the solution you'd like
Adding hide-cell support to markdown cell metadata.

Chris
:smile: Looking forward!

Thanks @ajz34, so to "wrap" an entire markdown cell is not possible with the current implementation I'm afraid. (at least I cannot see a way)
The reason for this is due to the hierarchy of the underlying document structure.
For example, if you have [markdown,code,markdown] cells:
# H1 a
## H2 a
text1

print("hi")

## H2 b
text2
# H1 b

this turns into:
<h1 a>
  <h2 a>
    text1
    <codecell tags="hide_cell">
      print("hi")
  <h2 b>
    text2
<h1 b>

which is fundamentally incompatible (at least to my knowledge) with a structure like:
<mdcell 1 tags="">
  elements...
<mdcell 2 tags="hide_cell">
  elements...

does that explanation make sense?

and of course if you have any suggestions for a workaround 😬

Got that!
(actually I'm not considering wraping title :sweat_smile:)
(is that some technical concerns you may encounter? :open_mouth:)

actually I'm not considering wraping title

For a general implementation though, we have to account for this possibility.
There may be some workaround, like a sphinx setting to "force" this wrapping, that comes with the caveat that it could break the build.
I'm going to have a re-look at the way we handle cell metadata soonish in #84, and so will bear this in mind


[Monitor] add src and dst data to json output

Signed-off-by: Maciej Kwiek<EMAIL_ADDRESS>

test-me-please

test-me-please

@nebril the previous flake was already informed here https://github.com/cilium/cilium/issues/3850#issuecomment-391437815

test-me-please


Enable CircleCI

@JustinBeckwith not sure why Circle is not running anything from this repo. Can you please take a look?

:waves magic wand:
https://circleci.com/gh/googleapis/nodejs-security-center


google profiler hangs in rhel5 and rhel6, but works in rhel4

Originally reported on Google Code with ID 642
What steps will reproduce the problem?
1.Write a code which has system calls
2.Run in any rhel5 or rhel6 platform
3.Hangs abruptly in any system call. The hanging happens more predominantly for little
large testcases.

What is the expected output? What do you see instead?
Completion of the run, but it hangs in middle ..
stack 39372
Thread 4 (Thread 0x2b5992f95700 (LWP 39373)):
#0  0x00000038e260b5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00000000023a122e in k34ba3 ()
#2  0x00000038e26079d1 in start_thread () from /lib64/libpthread.so.0
#3  0x00000038e1ee8b6d in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x2b5993196700 (LWP 39374)):
#0  0x00000038e260b98e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00000000023a1142 in a3467n3 ()
#2  0x00000038e26079d1 in start_thread () from /lib64/libpthread.so.0
#3  0x00000038e1ee8b6d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x2b5994972700 (LWP 39379)):
#0  0x00000038e260b98e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00000000024f07c1 in ?? ()
#2  0x00000038e26079d1 in start_thread () from /lib64/libpthread.so.0
#3  0x00000038e1ee8b6d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x2b5991b6fee0 (LWP 39372)):
#0  0x00000038e1e3e8ca in do_system () from /lib64/libc.so.6
#1  0x00000038e1e3ec40 in system () from /lib64/libc.so.6
#2  0x000000000213a666 in VeMacroUsageDump::setDumpDirPath(char const*) ()
#3  0x0000000000d16e92 in hdlSetCheetahArgs() ()
#4  0x0000000000d227e2 in hdlParserMain ()
#5  0x0000000000d9a92a in CHECKRULES(registeredNameList*, SgWorkspace*, int) ()
#6  0x0000000000d924dc in sgCompareNDesigns(registeredNameList*) ()
#7  0x0000000000d8455c in sgGoCheckRules ()
#8  0x0000000000a95543 in runGoal() ()

What version of the product are you using? On what operating system?

google profiler version 2.2.1 compiled on gcc 4.8.1 on 2.6.18-92.el5 platform.
Please provide any additional information below.
The hang is more consistent in 2.6.18-92.el5 platform and works smoothly without hang
in 2.6.9-5.EL platform.

Reported by rajdeep.babu on 2014-08-18 12:34:17

Still seeing this on RHEL 7.4, with gperftools 2.8. This time it is stuck on system("mkdir ..."), when CPU profiler is enabled. Any updates?

Thanks for update. Please file fresh ticket and ideally with some means to reproduce. Also if you're able to attach backtraces from all threads involved that would help a lot.


How to reset page numbers in a new section

I want to use a new page number in a new section, but can't find where to set it

I don't think we have this feature yet. I guess I wasn't aware you can do that per section.


python311Packages.coinmetrics-api-client: 2<IP_ADDRESS> -> 2<IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.coinmetrics-api-client is: Coin Metrics API v4 client library
meta.homepage for python311Packages.coinmetrics-api-client is: https://coinmetrics.github.io/api-client-python/site/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2<IP_ADDRESS> with grep in /nix/store/abbd71c76dgdpaqryzd18177vcm21pxf-python3.11-coinmetrics-api-client-2<IP_ADDRESS>
found 2<IP_ADDRESS> in filename of file in /nix/store/abbd71c76dgdpaqryzd18177vcm21pxf-python3.11-coinmetrics-api-client-2<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.coinmetrics-api-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/abbd71c76dgdpaqryzd18177vcm21pxf-python3.11-coinmetrics-api-client-2<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.coinmetrics-api-client https://github.com/r-ryantm/nixpkgs/archive/e4ff02e4c4d420741e2f1757bde6e1ade7559c8b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e4ff02e4c4d420741e2f1757bde6e1ade7559c8b#python311Packages.coinmetrics-api-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/abbd71c76dgdpaqryzd18177vcm21pxf-python3.11-coinmetrics-api-client-2<IP_ADDRESS>
ls -la /nix/store/abbd71c76dgdpaqryzd18177vcm21pxf-python3.11-coinmetrics-api-client-2<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

python311Packages.coinmetrics-api-client

Maintainer pings
cc @centromere for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.coinmetrics-api-client is: Coin Metrics API v4 client library
meta.homepage for python311Packages.coinmetrics-api-client is: https://coinmetrics.github.io/api-client-python/site/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2<IP_ADDRESS> with grep in /nix/store/hyjlz0rkdxfqh3134idmqrij9npygi2f-python3.11-coinmetrics-api-client-2<IP_ADDRESS>
found 2<IP_ADDRESS> in filename of file in /nix/store/hyjlz0rkdxfqh3134idmqrij9npygi2f-python3.11-coinmetrics-api-client-2<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.coinmetrics-api-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hyjlz0rkdxfqh3134idmqrij9npygi2f-python3.11-coinmetrics-api-client-2<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.coinmetrics-api-client https://github.com/r-ryantm/nixpkgs/archive/cd92b80cebef50c2e4f4e3619609c2371b11e242.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cd92b80cebef50c2e4f4e3619609c2371b11e242#python311Packages.coinmetrics-api-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hyjlz0rkdxfqh3134idmqrij9npygi2f-python3.11-coinmetrics-api-client-2<IP_ADDRESS>
ls -la /nix/store/hyjlz0rkdxfqh3134idmqrij9npygi2f-python3.11-coinmetrics-api-client-2<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

python311Packages.coinmetrics-api-client

Maintainer pings
cc @centromere for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.coinmetrics-api-client is: Coin Metrics API v4 client library
meta.homepage for python311Packages.coinmetrics-api-client is: https://coinmetrics.github.io/api-client-python/site/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2<IP_ADDRESS> with grep in /nix/store/83bmynk4d4k17nwzd3sn71w0z42wbb0x-python3.11-coinmetrics-api-client-2<IP_ADDRESS>
found 2<IP_ADDRESS> in filename of file in /nix/store/83bmynk4d4k17nwzd3sn71w0z42wbb0x-python3.11-coinmetrics-api-client-2<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.coinmetrics-api-client
python312Packages.coinmetrics-api-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/83bmynk4d4k17nwzd3sn71w0z42wbb0x-python3.11-coinmetrics-api-client-2<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.coinmetrics-api-client https://github.com/r-ryantm/nixpkgs/archive/948cc5d3df8f6a7721429b1ca30b3fda34d25888.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/948cc5d3df8f6a7721429b1ca30b3fda34d25888#python311Packages.coinmetrics-api-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/83bmynk4d4k17nwzd3sn71w0z42wbb0x-python3.11-coinmetrics-api-client-2<IP_ADDRESS>
ls -la /nix/store/83bmynk4d4k17nwzd3sn71w0z42wbb0x-python3.11-coinmetrics-api-client-2<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

python312Packages.coinmetrics-api-client

1 package built:

python311Packages.coinmetrics-api-client

Maintainer pings
cc @centromere for testing.


[parsers] alternate csv quote character support

to: @austinbyers
cc: @airbnb/streamalert-maintainers
size: small
Background
CSV logs can have fields quoted, and the typical quote character is a double quote ("). However, some logs can use an alternate quote character to quote fields.
Changes

Adding support for specifying alternate quotechar in csv log parsing.
Updating cloudwatch:rds_aurora to use single quote character.
Fixing bug with envelope extraction in embedded csv logs.
Changing logger statement from warning to debug that was very noisy.

Testing

Adding unit test for new quotechar support.
Adding new schema validation test for single quoted csv field data.
All current rule tests passing.

Coverage increased (+0.001%) to 97.595% when pulling 48c3240a2208310b5f461af882e7d9dacdb8cbc3 on ryandeivert-csv-quote-char into a00f7ae8566d3f375c4860377eed22d4c0eb6f0f on master.


Make SMC more efficient by allocating memory at the model-layer

One area for improvement is to not allocate memory when new particles are sampled. We currently don't do this to keep compatibility with autodiff.
The way to do this is actually at the model layer (e.g. LinearGaussian) rather than at the SMCModel layer
function rp_base(m::LinearGaussian, rng, Zs, t)
    μ, Σ = calc_prop(m, Zs, t)
    @assert isposdef(Σ)
    Zs_new = μ + rand(rng, MvNormal(Σ), size(Zs, 2))
    return Zs_new
end

turns into
function rp_base(m::LinearGaussian, rng, Zs, t)
    μ, Σ = calc_prop(m, Zs, t)
    @assert isposdef(Σ)
    eps = rand!(rng, MvNormal(Σ), m._eps_old)
    eps .+= μ
    m._eps_old = m._eps_new # swich the underlying storage
    m._eps_new = eps
    return Zs_new
end

Maybe implement a proof-of-concept in a new model (LinearGaussianCached ?) to compare performance

Closed by #20


add support for node-selector

introduce cmdline arg and docker label for setting a node selector
format is a comma-separated list of key-value pairs

I tried to conform to kubedock conventions as best as I could. I wasn't sure where to put the parsing code, so I went with containers.go as a first try.
Please let me know if you find this useful and if I should adapt anything.

Thanks appreciated, sorry for the late response.
I aggree with the suggested format, and that it should be configureable via a label as well as cli arguments. Note that the applying a node selector should also be possible with the use of a pod-template. However, in this case it can be dynamically applied (by using the labels) as well, which is a nice feature to have.
Generally, if such a label is introduced, the processing of the label is handled in internal/model/types/container.go and the routes implementations (docker/containers.go and libpod/containers.go) make sure the label is present (as you already did for the docker variant). For example, see how the pull policy is implemented, where the label is populated, and the value is processed and retrieved in the model implementation with GetImagePullPolicy. The node-selector should be implemented in a similar fashion.
Can you move the code to the model, and add some unit tests as well?
Can you also update the documentation in the README.md and config.md files?

Thanks for your feedback.
I moved the code to the model as you suggested and added the label handling to the libpod routes. I am now honoring the node selector from the pod template by passing it into GetNodeSelector() as an argument.
I also added unit tests and documentation.
Please let me know if you would like to have adapted anything else.

Sure, removed it.

Awesome, thanks @dschiemann80 !


JKernel: static class variables and more matches

abs, memset
changed JKRCompression to typedef (this will make signatures make)
changed some static variables in JKernel from lbl_XXXXXXXX to their real name
JKRArchive setExpandSize and getExpandSize matched
JKRDvdFile 100% complete
JKRDvdArchive matched a few, still problems with instruction ordering

These changed are already merged. As pull request #80 was based on this pull request, and #80 is already merged.

These changed are already merged. As pull request #80 was based on this pull request, and #80 is already merged.


Calling 3rd party DLL that makes calls out to the internet from .Net core fails proxy authentication despite configuring or coding the required settings

I have created a .Net Core 2.0 Web.API that will relay a request to a 3rd party provider via their .Net 4.0 DLL which in turn handles the communication with their Web API and returns the results.
In a simple .Net 4 application this all works perfectly and when I run my Web.API and make calls to it using a direct internet connection again it all works perfectly.
However, if it is run connecting to our work network which uses a proxy I get 407 Proxy Authentication Required. Fair enough all I need do is specify that I want to use the default credentials and it should all work. So A bit of digging around had given me several possible solutions. Unfortunately under .Net Core 2.0 they don't work.
I have tried deploying to my local machine and specifying in the web.Config:
<system.net>   <defaultProxy useDefaultCredentials="true" /> </system.net>
I have also tried adding this configuration to the machine.config (which seemed a bit overkill) again no joy.
I have also tried adding to my code in my Web API:
System.Net.WebRequest.DefaultWebProxy.Credentials = System.Net.CredentialCache.DefaultNetworkCredentials;
both before and after instantiating a reference to the 3rd party DLL and still when the vendors DLL makes its call to their Web API, via HTTP or HTTPS I get back 407 Proxy Authentication Required.
In an attempt to prove that I was not going mad I stripped the core of the work out to a standard .Net application to create basic a test harness and applying either of the solutions to that program it all works as expected. I have also created a separate .Net 4 DLL to act as a wrapper to the 3rd party DLL and in its constructor put in the above code to set the credentials in an attempt to isolate the effect to that environment. Again, this works perfectly under a simple test application but fails under the .Net Core Web.API.
Putting fiddler into the equation to watch the communication with the working application you can see the initial request get denied and proxy authentication get requested, the authentication then gets passed back and the actual request then gets through and the result passed back.
But in the .Net core Web.API I have developed the request simply goes out, hits the proxy authentication request, but then no credentials get pushed back to get things going and the conversation terminates.
This is the first time that I have ever worked with .Net Core so I may be missing something that I need to do, but from my perspective it looks like when I set-up the environment in my application for proxy authentication that same environment/settings are not being passed through to the DLL's environment and so I can't handle the request properly.
So I need some way of setting up or injecting the environment for the 3rd party DLL to ensure that it knows what to do with the authentication request via System.Net.WebRequest.DefaultWebProxy or similar.
So far I have tried running the code in a completely different thread and tried creating a completely separate .Net standard DLL to act as a wrapper, inside that DLL I then use code to force the System.Net.WebRequest.DefaultWebProxy.Credentials to use the default network credentials. Plugging either of these into my test harness they work but as soon as they are put into the .Net Core Web API they fail in exactly the same way.

Issue moved to dotnet/corefx #31036 via ZenHub


BE - Setup initial Route directory (for testing team members)

FE should be able to pull BE team member data

 BE - Setup initial Route directory


Update README.md

Added HelloFresh to companies using Airflow

Current coverage is 65.96% (diff: 100%)

Merging #1883 into master will not change coverage

@@             master      #1883   diff @@
==========================================
  Files           129        129
  Lines          9898       9898
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           6529       6529
  Misses         3369       3369
  Partials          0          0

Powered by Codecov. Last update f34b292...f4818c8

Welcome to the community! For your reference, please follow https://cwiki.apache.org/confluence/display/AIRFLOW/Contributors'+Guide, which specifies that the commit message look something like :
[AIRFLOW-631] Add HelloFresh to Airflow Users
I created a JIRA for your and updated the commit message on merge this time. We use the commit message subject when building release notes.


Crash: "FailureMessage Object: 0x7ffd0376c1c0"

Bibliogram crashed without any reason, according to the developer ( @cloudrac3r ) it's a sharp issue.
#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 0x7ffd0376c1c0
 1: 0x55717d9bd7e3  [node]
 2: 0x55717e3eb8b8 V8_Fatal(char const*, ...) [node]
 3: 0x55717dd856bf v8::internal::GlobalBackingStoreRegistry::Register(std::shared_ptr<v8::internal::BackingStore>) [node]
 4: 0x55717db02245 v8::ArrayBuffer::GetBackingStore() [node]
 5: 0x55717d92529c node::Buffer::New(node::Environment*, char*, unsigned long, void (*)(char*, void*), void*) [node]
 6: 0x55717d925590 node::Buffer::New(v8::Isolate*, char*, unsigned long, void (*)(char*, void*), void*) [node]
 7: 0x55717d917e71 napi_create_external_buffer [node]
 8: 0x7f84d027101d PipelineWorker::OnOK() [/home/bibliogram/bibliogram/node_modules/sharp/build/Release/sharp.node]
 9: 0x7f84d02604ce Napi::AsyncWorker::OnWorkComplete(napi_env__*, napi_status, void*) [/home/bibliogram/bibliogram/node_modules/sharp/build/Release/sharp.node]
10: 0x55717d9197ff node::ThreadPoolWork::ScheduleWork()::{lambda(uv_work_s*, int)#2}::_FUN(uv_work_s*, int) [node]
11: 0x55717e3ca45e  [node]
12: 0x55717e3cdbd0  [node]
13: 0x55717e3dfc88  [node]
14: 0x55717e3ce3d7 uv_run [node]
15: 0x55717d99216e node::NodeMainInstance::Run() [node]
16: 0x55717d913ad8 node::Start(int, char**) [node]
17: 0x7f84d397d023 __libc_start_main [/usr/lib/libc.so.6]
18: 0x55717d8a4d6e _start [node]
Illegal instruction (core dumped)

Please see #2196 - there is a race condition in Node.js 14.

Hi every one i have a similar trouble.
david@david-ThinkCentre-M72e:~/Escritorio/fe-ct-prepcourse-fs$ npm test 05

<EMAIL_ADDRESS>test
jest --collectCoverage=false 05

RUNS  M05 JavaScript Arrays/test/JSIII.test.js

Fatal error in , line 0
Fatal JavaScript invalid size error 188720663 (see crbug.com/1201626)

#FailureMessage Object: 0x7ffddf644b20
1: 0xd05ae1  [node]
2: 0x20dbe21 V8_Fatal(char const*, ...) [node]
3: 0x107b468  [node]
4: 0x125a3df  [node]
5: 0x125a567  [node]
6: 0x14d3e26 v8::internal::Runtime_GrowArrayElements(int, unsigned long*, v8::internal::Isolate*) [node]
7: 0x191eef6  [node]
Trace/breakpoint trap (core dumped)

i has similar error in ec2 instance, one case is run out of memory, i closed programs and try again it worked


TestKit

Mocking requests in test can become quite verbose. Each call to sttp needs to be mocked separately.
It'd be great to have testkit - something similar to https://github.com/leanovate/play-mockws#example.

Isn't that what http://sttp.readthedocs.io/en/latest/backends/testing.html exactly does? :)


[Snyk] Security upgrade openjdk from 8-jdk-alpine to 19-jdk-alpine

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to openjdk:19-jdk-alpine, as this image has only 11 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

714
Out-of-bounds Write SNYK-ALPINE39-BZIP2-452847
No Known Exploit

729
Out-of-bounds Write SNYK-ALPINE39-FREETYPE-1019627
Mature

714
Out-of-bounds Write SNYK-ALPINE39-MUSL-458529
No Known Exploit

714
Out-of-bounds Write SNYK-ALPINE39-MUSL-458529
No Known Exploit

714
Out-of-bounds Read SNYK-ALPINE39-SQLITE-449671
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

OK


replace underlying indexedDB library with open source idb-keyval package

Description of changes
Replacing the idb.ts with idb-keyval package. Its identical in its usage and now we dont have to worry about testing idb.ts file (which did not have any unit tests).
Pull request checklist

[n/a] Addresses an existing issue: Fixes #0000
[n/a] Added relevant unit test for your changes. (npm run test)
[x] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[x] Ran precheckin (npm run precheckin)
[x] Added screenshots/GIFs for UI changes.

Closing PR as the underlying bug is not fixed from UglifyJS side.

https://github.com/jakearchibald/idb-keyval/issues/51


Add get_size(file) for darwin

The default file size command, stat -c, does not work on macOS:
$ stat -c /Users/Shared
stat: illegal option -- c
usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...]

This PR adds a get_size() method for darwin that uses stat -f %z (same command as free/openbsd).
Test:
describe file("/Users/Shared") do
  its(:size) { should > 10 }
end

Before:
$ rspec

File "/Users/Shared"
  size
    is expected to > 10 (FAILED - 1)

Failures:

  1) File "/Users/Shared" size is expected to > 10
     Failure/Error: its(:size) { should > 10 }
       expected: > 10
            got:   0
       /bin/sh -c stat\ -c\ \%s\ /Users/Shared

     # ./spec/localhost/sample_spec.rb:4:in `block (2 levels) in <top (required)>'

Finished in 0.19662 seconds (files took 0.90007 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/localhost/sample_spec.rb:4 # File "/Users/Shared" size is expected to > 10

After:
$ rspec

File "/Users/Shared"
  size
    is expected to > 10

Finished in 0.17988 seconds (files took 0.87242 seconds to load)
1 example, 0 failures

OS version:
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.15.6
BuildVersion:   19G46c

Thanks!

Released as v2.82.17.


Categories written on top of each other for multiindex bar plot with Matplotlib backend

I would expect to be able to use the a MultiIndex bar plot with the Matplotlib backend just as with the Bokeh backend. But unfortunately the categories are written on top of each other when using the Matplotlib backend.

import pandas as pd
import hvplot.pandas  # noqa

from bokeh.sampledata.autompg import autompg_clean as autompg

autompg.head()

autompg_long_form = autompg.groupby("yr").mean(numeric_only=True).reset_index()
autompg_long_form.head()

autompg_multi_index = autompg.query("yr<=80").groupby(['yr', 'origin']).mean(numeric_only=True)
autompg_multi_index.head()

hvplot.extension("bokeh")
autompg_multi_index.hvplot.bar(width=1000, rot=90)

hvplot.extension("matplotlib")
autompg_multi_index.hvplot.bar(width=1000, rot=90)

I can see there is also an upstream issue in HoloViews. See https://github.com/holoviz/holoviews/issues/5659.


Update mempool v2.1.2 & fixes

This issue is based on the following sub issues:

[x] merge update & fix #2014
[x] drop database fix #1960
[x] default mempool back to 300MB #2007 #2008

All merged in preparation of v1.7 .. set for final testing

Testing looks good. Closing for v.17 release.


Reenable Provider Resource Synchronization

https://github.com/envoyproxy/gateway/pull/447 removed provider resource sync due. When https://github.com/envoyproxy/gateway/issues/413 is resolved, the sync should be reenabled on the single provider resource map that contains all provider resources, i.e. Gateway, Service, etc..

dup of https://github.com/envoyproxy/gateway/issues/448

Closing since this is a dupe.


Writing to tag in iOS throw an exception PlatformException(NFCTagUnavailable, the tag is unavailable for writing, null)

void _ndefWrite(NDEFMessage message) {
if(!message.tag.writable){
result.value = NfcResponse.error(Strings.NFC_TAG_NOT_WRITABLE);
return;
}
List<NDEFRecord> newRecords = new List();
newRecords.add(NDEFRecord.plain(jsonEncode(widget._ticket)));

if (message.records.isNotEmpty) newRecords.addAll(message.records);

NDEFMessage newMessage = NDEFMessage.withRecords(newRecords);

message.tag.write(newMessage).then((value) {
  result.value = NfcResponse.success(null);
  widget.ticketsProvider.startTicket(widget._ticket.id);
}, onError: (error) {
  String errorMessage = Strings.SOMETHING_WRONG_HAPPENED_MESSAGE;

  if(error is Exception)
    errorMessage = error.toString();

  result.value = NfcResponse.error(errorMessage);
});

}
the Android version worked, the issue only appeared in iOS

A few insights from my testing:

it seems like timing might be one of the issues, but I cannot absolutely confirm this. I was able to get some successful writes using the following code:

      await Future<void>.delayed(const Duration(milliseconds: 5000));
      final Stream<NDEFMessage> stream = NFC.readNDEF(throwOnUserCancel: true);
      await Future<void>.delayed(const Duration(milliseconds: 5000));
      writeSub = stream.listen((NDEFMessage message) {
        final NDEFMessage newMessage = NDEFMessage.withRecords([NDEFRecord.text('hello world')]);
        try {
          message.tag.write(newMessage).then((dynamic dummy) {
            writeSub.cancel();
            verifyTag(newPoint, room.roomId);
          });
        } catch (e) {
          writeSub.cancel();
          String errStr2 = e.toString();
          String exStr2 = e.runtimeType.toString();
          int xxx2 = 0;
          print(errStr2);
          print(exStr2);
        }
      }, onError: (Object error) {
        writeSub.cancel();
        print('On error called');
      }, onDone: () {
        writeSub.cancel();
        print('On done called');
      }, cancelOnError: true);

When writes fail, they leave the tag empty. When I erase a tag with NFCTools, it places an empty Record 0 on the tag, after a failed write, this record is gone.

There may be some indication in my testing that the more complex the message, the higher the failure rate.  I was able to successfully write "hello world" more often than I was able to successfully write two records with the following text:

Record 0 contains: R2W:eRfKwMPjeX
Record 1 contains: roomId:FF288C53-FF8E-427E-97C5-83238B7646AE
NOTE: It works fine in Android, so I don't suspect that the content of record itself is a problem, although the length might be an issue (14 + 43 = 57 bytes)?
Any help would be greatly appreciated!

Ahhh… an interesting insight from my testing.  When I write using Android, the payload is encoded with UTF-8 (and everything works fine).  When I write with iOS, the payload is encoded with UTF-16.
Android can read either the UTF-8 or UTF-16 in the data field, although the payload field does not decode correctly. iOS can read only the UTF-8 encoded tags but not the UTF-16 tags.
Using NFC Tools, I can read both tags (that’s how I know that iOS is encoding using UTF-16) and the payload is correct for both encoding schemes.  When reading the UTF-16 tag on Android, here’s what I get; notice that the data field is correct, but the payload field has what appears to be Japanese characters.

When I read the same UTF-16 tag on iOS, the tag reads as empty.
So, it looks like there may be two issues here. One is the ability to read tags with UTF-16 on both iOS and Android platforms. The other is the ability to have a deterministic write function across both the iOS and Android platforms so that the behavior is the same.
I have worked around the problem by adding NDEF records to the message using the "plain" factory constructor as opposed to using the "text" factory constructor.
NDEFRecord.plain(myMessage);
versus
NDEFRecord.text(myMessage);
By doing this, no text encoding is applied and all works as expected.

I'm having the same problems in IOS, In android all works fine, but not in iOS.
Any good advice?
I need to read a tag, and update its value (write a code)
thanks so much

I'm having the same problems in IOS, In android all works fine, but not in iOS. Any good advice? I need to read a tag, and update its value (write a code) thanks so much

do you get how to solve? same problem to me


Integration with Github-Time-Tracking?

Hey
So I am thinking the Time Tracking features of Issue Stats would be a great complementary feature with the current issue stats.
https://github.com/StephenOTT/GitHub-Time-Tracking
Any interest on collaborating on this?
@hstove

Sorry, but I don't have time to integrate any new features into issuestats. However, I did somewhat recently put together a JSON API, if you're interested!


Disable the notification on save

Hi. As described in the title, can I disable notifications for saved actions? e.g. :w

nvim-notify doesn't send any notifications, other plugins do. The saved message is from noice.nvim, you might be able to configure it prevent certain messages or you can do something like this https://github.com/rcarriga/nvim-notify/issues/114#issuecomment-1179754969


feat: update rn-signer readme to contain additional setup information

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
This PR introduces significant updates to the @account-kit/react-native-signer library, enhancing its functionality and structure, particularly for React Native applications. It includes new configurations, example implementations, and improvements to the Android and iOS projects.
Detailed summary

Added .watchmanconfig files for project configuration.
Introduced jest.config.js for testing setup.
Updated tsconfig.build.json to exclude certain directories.
Created new icons and resources for the example app.
Implemented basic authentication flow in HomeScreen.
Enhanced AppDelegate and MainApplication for iOS.
Added NativeTEKStamper functionality for key management.
Updated Gradle settings and properties for Android.
Improved documentation and README files for clarity.
Configured GitHub Actions for CI/CD workflows.

The following files were skipped due to too many changes: account-kit/rn-signer/package.json, account-kit/rn-signer/example/ios/ReactNativeSignerExample.xcodeproj/xcshareddata/xcschemes/ReactNativeSignerExample.xcscheme, account-kit/rn-signer/.github/workflows/ci.yml, account-kit/rn-signer/android/build.gradle, account-kit/rn-signer/example/ios/ReactNativeSignerExample/LaunchScreen.storyboard, account-kit/rn-signer/src/client.ts, account-kit/rn-signer/example/android/app/build.gradle, account-kit/rn-signer/android/src/main/java/com/accountkit/reactnativesigner/NativeTEKStamperModule.kt, account-kit/rn-signer/example/android/gradlew, account-kit/rn-signer/example/ios/ReactNativeSignerExample.xcodeproj/project.pbxproj, yarn.lock

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#1172  👈 (View in Graphite)
moldy/rn-base

This stack of pull requests is managed by Graphite. Learn more about stacking.


[Request] prboom-plus-rt support

I think you can make compatibility with prboom-plus-rt when you switch from off to quality, the game gives an error!

The DLL produced by GitHub Action is broken for Vulkan, you need to compile it yourself.
I compiled it for you to try if you need it:
DLSS-VK.zip
Running very well under Radeon GPU here:

I fixed the Vulkan compatibility in ba346fa6788a2183ecdb5c1eeccf8b03b97b6561. So any future build will support DX12 and Vulkan at the same time.


The urlPathTemplate cannot match the query parameter.

Proposal
I created a stub using the urlPathTemplate: “/contract/app/{pid}/api/{id}/overview”. When I made a request using the path: “/contract/app/1699603961400320001/api/1709863759148662785/overview”, the response was successful. However, when I added a query parameter and used the path: “/contract/app/1699603961400320001/api/1709863759148662785/overview?arg=2” to request, an error occurred with the message: “Path parameter does not match”.
Reproduction steps
first: the response was successful.
url path:/contract/app/1699603961400320001/api/1709863759148662785/overview
The stub:
{
"id" : "b290dbf6-bed1-435a-b6d9-e4aac8f6035d",
"request" : {
"urlPathTemplate" : "/contract/app/{pid}/api/{id}/overview",
"method" : "GET",
"headers" : {
"accept" : {
"equalTo" : "application/json",
"caseInsensitive" : true
}
},
"pathParameters" : {
"pid" : {
"equalTo" : "1699603961400320001",
"caseInsensitive" : true
},
"id" : {
"equalTo" : "1709863759148662785",
"caseInsensitive" : true
}
},
"queryParameters" : {
"arg" : {
"equalTo" : "2",
"caseInsensitive" : true
}
}
},
"response" : {
"status" : 200,
"body" : "{\r\n    "code": 300,\r\n    "data": true,\r\n    "msg": "success"\r\n}",
"headers" : {
"content-type" : "application/json"
}
},
"uuid" : "b290dbf6-bed1-435a-b6d9-e4aac8f6035d",
"persistent" : true,
"insertionIndex" : 1
}
second: an error occurred with the message: “Path parameter does not match”:
url path:/contract/app/1699603961400320001/api/1709863759148662785/overview?arg=2
the stub:
{
"id" : "b290dbf6-bed1-435a-b6d9-e4aac8f6035d",
"request" : {
"urlPathTemplate" : "/contract/app/{pid}/api/{id}/overview",
"method" : "GET",
"headers" : {
"accept" : {
"equalTo" : "application/json",
"caseInsensitive" : true
}
},
"pathParameters" : {
"pid" : {
"equalTo" : "1699603961400320001",
"caseInsensitive" : true
},
"id" : {
"equalTo" : "1709863759148662785",
"caseInsensitive" : true
}
},
},
"response" : {
"status" : 200,
"body" : "{\r\n    "code": 300,\r\n    "data": true,\r\n    "msg": "success"\r\n}",
"headers" : {
"content-type" : "application/json"
}
},
"uuid" : "b290dbf6-bed1-435a-b6d9-e4aac8f6035d",
"persistent" : true,
"insertionIndex" : 1
}
The error:

References
No response

I think it is quite as-designed, but not 100% sure what should be the default behavior (now it is same as absent but should be any matcher which seems to be missing for form parameters at all). I also created https://github.com/wiremock/wiremock.org/issues/206 to have such a case explicitly documented


S2E16 AMC Meeting Announcement

AMC Meeting Announcement

S2E12
Season 2 Episodes 16

Date
7-10 pm, Sunday

Location
821, 8th floor, BUPT Research Building

Chairman
@ArronHZG

Vice Chairman
@Jarvisgivemeasuit

Previous Meeting

Minutes
Link

Blog
Ss2E15 (Season 2 Episodes 15)

Issue
#151

Agenda
1. Oral

Oral should be prepared for 15 - 30 minutes, and no more than 45 minutes, including Q/A.

Presenter
Paper

2. Poster

Posters should be prepared for 5 - 10 minutes, and no more than 15 minutes, including Q/A.
No more than 4 posters per seminar. If there's more than 4 posters purposals(PRs), the chairman should pick at most 4, and leave the others in the PR queue.

Presenter
Paper

@huan
苏现林的2019语言与智能技术竞赛“三元组”信息抽取任务模型

@newip
Idea: Is it possible to put human being's characters model into NLP?

@824zzy
Colab&TPU&Pytorch&Hub

3. After Party
Everyone will be welcome. You can join or not join as you want (not required by the AMC), and change your mind at anytime.

After Party will be started right after all the meeting agenda had been fulfilled.
We will find a bar and drink beers and talk whatever we want. (we can expect that it will be related to meeting topics of the day)
The bill will be paid AA

Party Animals

🍻 @huan
🍻 @newip *
🍻 @824zzy

Newcomers
Newcomers number: 2

Referrer
Newcomer
Bio

@824zzy
@TJH54
大家好我是北邮软件学院的滕静涵，研究生一年级，对AI/ML感兴趣但还是小白，希望能够跟随大佬们的步伐学习进步。

@824zzy
@yyllyy0813
软件学院研一学生杨钰琳，想了解机器学习和深度学习方面的知识。

@ArronHZG Thank you very much for the announcement! You did a good job!
I have three questions for us:
1. A typo needs to be fixed
- Ss2E15
+ S2E15

2. The Chairperson
I remember that our rules are all members should give a talk at the seminar. Chairperson is a member, so the Chairperson should give a talk at the seminar.
Should we make it more specific in our manual?
3. The Vice Chairperson
Should we make the vice chairperson attend the seminar as a must?
Because the vice chairperson need to be the supervise for the chairperson, and vice chairperson needs to be the backup for the chairperson.

OMG , I fixed the first question.
And second , I am preparing a post, but I am afraid that it is too late too talk about it.
And I think the vice chairperson should attend our seminar.

It's amazing that you reply so fast! :smile:
I believe it's never too late to get to be prepared, and as a chairperson, you are always privileged to make any decisions for the seminar. So we would love to looking forward to your poster!
If we agree that the vice chairperson should attend the seminar, could you please to invite your vice chairperson to join your seminar? And also please make him be prepared too! :+1:

ok, I can make sure the vice chairperson attend the seminar.thank you to review the Announcement😁

Awesome, you are very welcome and my pleasure!


attacher.call is not a function when used in a solid-start/vinxi project

remark-embedder-core version: 3.0.2
node version: 22.0.0
pnpm version: 9.1.1

Relevant code or config
// file: app.config.ts

import { defineConfig } from "@solidjs/start/config";

import mdx from "@vinxi/plugin-mdx";

import remarkEmbedder from "@remark-embedder/core";
import oembedTransformer from "@remark-embedder/transformer-oembed";

export default defineConfig({
  extensions: ["tsx", "mdx", "md"],
  server: {
    preset: "aws-amplify",
  },
  vite: {
    plugins: [
      mdx.default.withImports({})({
        jsx: true,
        jsxImportSource: "solid-js",
        providerImportSource: "solid-mdx",
        remarkPlugins: [
          [
            remarkEmbedder.default,
            { transformers: [oembedTransformer.default] },
          ],
        ],
        enforce: "pre",
      }),
    ],
  },
});

Trying to use this plugin in a SolidStart 1.0 RC project. SolidStart uses vinxi as a build system which provides a wrapper for the vite mdx processor.
When trying to use the plugin, this error occurs when processing an md/mdx file:
  file: src/routes/.../index.md
  at Function.freeze (node_modules/.pnpm/unified@11.0.4/node_modules/unified/lib/index.js:636:36)
  at Function.process (node_modules/.pnpm/unified@11.0.4/node_modules/unified/lib/index.js:716:10)
  at Module.compile (node_modules/.pnpm/@mdx-js+mdx@3.0.1/node_modules/@mdx-js/mdx/lib/compile.js:40:35)
  at transform2 (node_modules/.pnpm/@vinxi+plugin-mdx@3.7.1_@mdx-js+mdx@3.0.1/node_modules/@vinxi/plugin-mdx/dist/index.cjs:1535:30)
  at async Object.transform (node_modules/.pnpm/@vinxi+plugin-mdx@3.7.1_@mdx-js+mdx@3.0.1/node_modules/@vinxi/plugin-mdx/dist/index.cjs:2171:16)
  at async transform (node_modules/.pnpm/rollup@4.17.2/node_modules/rollup/dist/es/shared/node-entry.js:18680:16)
  at async ModuleLoader.addModuleSource (node_modules/.pnpm/rollup@4.17.2/node_modules/rollup/dist/es/shared/node-entry.js:18896:36)

This issue is the same as the one encountered here and it has an easy workaround.
Just use remarkEmbedder.default instead of remarkEmbedder directly, like I do in the config above. The same goes for the Oembed transformer.
I solved this issue with the debugger but wanted to save someone else the trouble by writing about it here. I'm not sure which piece of the stack is responsible for the problem but the workaround is easy so it's no biggie.

As I already provided a decent solution and I'm not sure the problem is due to any issue with the code in this repo, I'm just going to close the issue.
If you think that it is an issue with this repo's code, you can of course open it again.


Cleanup: Use sqlx

Use sqlx to interact with the database.

Why? We use tokio_postgres everywhere else for DB integration. When I read around it seems like sqlx is slower (although I don't know by which metrics, and it might be outdated).


Initial implementation

Initial implementations of logger and queue on local storage.
@raybooysen please will you take a look through if you get a chance. It's been a while since I've used TypeScript!

@raybooysen you'll want to ignore everything under build/

Looks good.