Imports from ESM packages fail

🐛 Bug Report
We've recently upgraded to Node 14 and we're looking to remove esm (-r esm, jdalton package) / babel / webpack and run everything natively.
We are running a monorepo and all packages got updated with type: "module.
Everything works now except for some tests where there's an error with imports (don't even know how to call it... double import?)
To Reproduce
We have some simple tests to ensure our schema doesn't change unintentionally / by mistake.
// Currency.test.js
import { graphql } from "graphql";
import { basename } from "path";

import schema from "../../../schema";

const entity = basename(__filename, ".test.js");

/* eslint-disable no-underscore-dangle */
describe(`"${entity}" regression testing`, () => {
  test(`Fields are as advertised`, async () => {
    const query = `
      query {
        __type(name: "${entity}") {
          name
          fields {
            name
            type {
              kind
              ofType {
                name
                kind
              }
            }
          }
        }
      }
    `;
    const expected = [
      .....
    ];

    const result = await graphql(schema, query);
    expect(result.data.__type.fields).toEqual(expected);
  });
});

// schema.js
import gqlTools from "graphql-tools";
import merge from "lodash/merge.js";

import root from "./root/index.js";
// + other imports in the same manner

// root/index.js
import definitions from "./definitions.js";
import resolvers from "./resolvers.js";

export default { definitions, resolvers };

// resolvers.js
import moment from "moment";
import gql from "graphql";

const { GraphQLScalarType, Kind, GraphQLError } = gql;

running yarn jest packages/internal-api/src/__tests__/currency/schema/Currency.test.js ends up in error
 FAIL  packages/internal-api/src/__tests__/currency/schema/Currency.test.js
  ● Test suite failed to run

    TypeError: Cannot read property 'GraphQLScalarType' of undefined

      2 | import gql from "graphql";
      3 |
    > 4 | const { GraphQLScalarType, Kind, GraphQLError } = gql;
        |         ^
      5 |

Expected behavior
I'm expecting this to work?
envinfo

  System:
    OS: Linux 4.19 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
  Binaries:
    Node: 14.10.1 - ~/.nvm/versions/node/v14.10.1/bin/node
    Yarn: 1.18.0 - /usr/bin/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v14.10.1/bin/npm

While the code was upgraded to remove any babel dependency jest still runs with the following config
// babel.config.js
module.exports = api => {
  api.cache(true);

  const presets = ["@babel/preset-env", "@babel/preset-react"];
  const plugins = [
    "@babel/plugin-syntax-dynamic-import",
    "@babel/plugin-syntax-import-meta",
    "@babel/plugin-transform-modules-commonjs",
    "@babel/plugin-proposal-class-properties",
    "@babel/plugin-proposal-json-strings",
    [
      "@babel/plugin-proposal-decorators",
      {
        legacy: true,
      },
    ],
    "@babel/plugin-proposal-function-sent",
    "@babel/plugin-proposal-export-namespace-from",
    "@babel/plugin-proposal-numeric-separator",
    "@babel/plugin-proposal-throw-expressions",
    "@babel/plugin-proposal-export-default-from",
    "@babel/plugin-proposal-logical-assignment-operators",
    "@babel/plugin-proposal-optional-chaining",
    [
      "@babel/plugin-proposal-pipeline-operator",
      {
        proposal: "minimal",
      },
    ],
    "@babel/plugin-proposal-nullish-coalescing-operator",
    "@babel/plugin-proposal-do-expressions",
    "@babel/plugin-proposal-function-bind",
  ];

  return {
    presets,
    plugins,
  };
};

// jest.config.js

module.exports = {
  setupFilesAfterEnv: ["./utils/jestSetup.js"],
  resetMocks: true,
  verbose: true,
  testEnvironment: "node",
  // Only test actual test files
  testMatch: ["**/__tests__/**/(*.)+(spec|test).[jt]s?(x)"],
  testPathIgnorePatterns: ["/node_modules/", "/.history/"],
  reporters: [
    "default",
    ["jest-junit", { output: "reports/js-test-results.xml" }],
  ],
  collectCoverage: false,
  collectCoverageFrom: ["**/*.{js,jsx}", "!**/node_modules/**"],
  coverageReporters: ["json", "html"],
  coverageDirectory: "reports/coverage",
};

To use ESM in Jest you need run node with --experimental-vm-modules, see https://jestjs.io/docs/en/ecmascript-modules.
If that doesn't work, please provide a minimal reproduction: https://stackoverflow.com/help/minimal-reproducible-example

Forgot to mention I've tried that too and it's worse:
node --experimental-vm-modules node_modules/.bin/jest packages/internal-api/src/__tests__/currency/schema/Currency.test.js
 FAIL  packages/internal-api/src/__tests__/currency/schema/Currency.test.js
  ● Test suite failed to run

    /home/the-noob/workspace/santa-maria/packages/internal-api/src/__tests__/currency/schema/Currency.test.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { graphql } from "graphql";
                                                                                ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:579:25)

(although not sure if the error message hides an issue with __dirname/__filename which are not available under ESM)
// jest.config.js

module.exports = {
  setupFilesAfterEnv: ["./utils/jestSetup.js"],
  resetMocks: true,
  verbose: true,
  testEnvironment: "node",
  transform: {},
  // Only test actual test files
  testMatch: ["**/__tests__/**/(*.)+(spec|test).[jt]s?(x)"],
  testPathIgnorePatterns: ["/node_modules/", "/.history/"],
  reporters: [
    "default",
    ["jest-junit", { output: "reports/js-test-results.xml" }],
  ],
  collectCoverage: false,
  collectCoverageFrom: ["**/*.{js,jsx}", "!**/node_modules/**"],
  coverageReporters: ["json", "html"],
  coverageDirectory: "reports/coverage",
};

When running with the default transform (babel-jest), if I comment out the babel.config.js I get the same import syntax error. Adding it back in gets stuck at that ...fourth? level import.
Will try to create a repo with the same structure and see if I can reproduce although it might be a babel thing.

as long as you have type: "module" in package.json that should work fine... A reproduction would be great 👍

Much to my surprise I've managed to reproduce it.
If anything looks strange please bear in mind it's part of a bigger project and the stripped down version might not make sense. At least that's what I like to tell myself.
https://github.com/the-noob/jest-import-issue
yarn start:internal-api successfully starts a graphql server at localhost:3090
yarn jest has the same failures at the multi level import.

See https://github.com/the-noob/jest-import-issue/pull/1 - you were missing type: module which is needed for ESM in .js files. You also had a CJS babel plugin active

Thanks!
Indeed it fixes my demo repo but now I'm getting ES Modules are only supported if your test environment has the 'getVmContext' function on the production repo.
Still, a step forward and something to look at tomorrow :)

You either have an older or a custom testEnvironment in your config

Jest monorepo runs with a single babel config in root. You can try jest --show-config to see what's resolved as testEnvironment. I'd also verify you don't have any old versions of jest-runtime lying around.
FWIW create-react-app@4 ships with Jest 26

I've upgraded CRA to 4 right after posting, still the same.
jest --show-config has the same output in both repos (except for repo paths, obviously)
Deleted node_modules 100 times,

Will park this for a while before I go mad.

Maybe this saves someone some headache ....
My package.json had something like
  "scripts": {
....
    "test:internal-api": "jest packages/internal-api/",
....
    "jest": "NODE_OPTIONS='--experimental-vm-modules' jest",
    "clear-all": "rimraf ./packages/*/node_modules && rimraf ./node_modules"
  },

Every time running yarn jest path/to/package things were fine... running yarn test:internal-api was failing and I couldn't figure out why. Because my test:internal-api was missing the experimental-vm-module option :|


Preempt nan to fix deprecated calls to Get/SetHiddenValue

In v8 5.2 (modules v49), Get/SetHiddenValue are removed (they've long been deprecated). But, the replacements (Get/SetPrivate) don't exist in node 4's version. NAN is planning on supporting this eventually (see: https://github.com/nodejs/nan/issues/587), but we need something shorter term as electron 1.3 has already bumped v8.
Fixes https://github.com/nodegit/nodegit/issues/1089

Note: locally, this is tested with latest node 4, node 6, and electron 1.3

Also @srajko did this with me, so with 2 people involved, I'm gonna go ahead and merge this.

@maxkorp what's the NODE_MODULE_VERSION for Electron?

I am still getting this using Electron v1.3.3, node v6.3.1 and npm 3.10.3 on OS X 10.11.6 having installed node and npm using Homebrew. Any help would be much appreciated.

@saper for 1.3 It's 49, since they bumped v8 (iirc to 1.5.2, whereas node 6 is on 1.5.0?).
@daryl-williams This hasn't been published yet, unfortunately. Are you just trying npm install nodegit? There will unfortunately be a few more steps than that until this ships.

@saper, Thanks for your reply.  I'm actually trying to setup to debug an
Electron application, following the instructions here:
https://github.com/electron/electron/blob/master/docs/tutorial/debugging-main-process.md
and I got this error when trying to rebuild the v8-profile module
because pre-built binaries were not found for<EMAIL_ADDRESS>and
<EMAIL_ADDRESS>This was the error:
CXX(target) Release/obj.target/profiler/src/heap_snapshot.o
../src/heap_snapshot.cc:46:46: error: no member named 'GetHiddenValue'
in 'v8::Object'
info.GetReturnValue().Set(info.This()->GetHiddenValue(__root));
~~~~~~~~~~~  ^
../src/heap_snapshot.cc:50:20: error: no member named 'SetHiddenValue'
in 'v8::Object'
info.This()->SetHiddenValue(__root, _root);
~~~~~~~~~~~  ^
All this is happening on OS X 10.11.6  and node and npm were installed
using Homebrew.
Thanks again.
On 8/17/16 4:09 PM, Max Korp wrote:

@saper https://github.com/saper for 1.3 It's 49, since they bumped
v8 (iirc to 1.5.2, whereas node 6 is on 1.5.0?).
@daryl-williams https://github.com/daryl-williams This hasn't been
published yet, unfortunately. Are you just trying |npm install
nodegit|? There will unfortunately be a few more steps than that until
this ships.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodegit/nodegit/pull/1106#issuecomment-240576808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_wdScC9acJCoM51EkGwz6u-MNImYhjks5qg5TAgaJpZM4JipdH.

Yeah thats probably this, but it will require us to release our new version first.

Any release date yet? Can I get myself on an announce list possibly?
Thanks
On 8/17/16 4:36 PM, Max Korp wrote:

Yeah thats probably this, but it will require us to release our new
version first.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodegit/nodegit/pull/1106#issuecomment-240581790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_wdcO-7iuEC3NHNvdwfOwey2iqkmdnks5qg5r8gaJpZM4JipdH.

If you start this repo, you should get a notification from github when it comes out. No set release date, but I'd say sooner rather than later, due to this issue
.

@daryl-williams I've compiled NodeGit from source and after running electron-rebuild it runs for me now using electron 1.3.3.
This is my workaround till next release

@daryl-williams I've just submitted a PR to get v8-profiler building for Electron 1.3.0+, thanks to @maxkorp for the inspiration. In the meantime you can try my workaround.
Apologies to the NodeGit devs for the off-topic reply.


Improve test coverage

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

Project coverage is 92.68%. Comparing base (5d8be14) to head (b9f3678).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
+ Coverage   90.87%   92.68%   +1.81%
==========================================
  Files           5        5
  Lines         504      506       +2
==========================================
+ Hits          458      469      +11
+ Misses         46       37       -9

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


The Robot Evolution

[WIP]
This PR starts a new phase in HubotNatural development, please give some attention.
It takes out all coffeescript files and replaces them for Javascript EC2015 files.
That's right, from now on, no more coffeescript. And of course, welcome to ASYNC/AWAIT.
It also upgrades Hubot to v3.0.1, Rocket.Chat adapter to 2.0.0 (with async, thanks @timkinnane), upgrades the docker image to node:8-alpine, and finally gives a better package.json info.
Still missing:

[ ] Better README.md with animated gifs and syntax update
[ ] Update YAML files with new syntax
[ ] CI scripts to generate new rocketchat/hubot-natural:latest docker images and releases

Please feel free to colaborate.

 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.Diego Dorgam seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update documentation for 1.4.x

Need to update the upgrade instructions for upgrading to 1.4.0

Work in progress

This is a work in progress to rework everything for a 1.5.x + world

Working fork/branch:
https://github.com/blinc117/docs.rocketpool.net/tree/1.5-Doc-Upadtes

Completed, PR


Changed copypaste-socks-chromeapp to listen to all local interfaces.

Useful for making it work in docker images.

:+1:


determine system to display Flowey's speech-text / soul event text

examples from Undertale / the old map:
* You called for help (ACTing during a soul event)

Undertale
original map

https://youtu.be/RJ4kumxv_1k?t=147
https://youtu.be/2IprmKr31pU?t=93

for the Jevil map we just put anything text-related directly into chat. (some stuff used /title or /subtitle, but mostly just used /tellraw). this is also an option but we might be able to do better.
maybe with the new text displays? https://minecraft.wiki/w/Display#Text_Displays

Gonna give this a shot over the next week or so


Implement plus and minus on IntervalUnion

Add/remove intervals from interval unions.
To write tests for this, it will become useful to first implement #36.

plus has been implemented (#42).


[Feature] Parallel sync

Is your feature request related to a problem? Please describe.
I've recently had to do my uploads manually (incidentally left wandb in offline mode). In attempting to do wandb sync --sync-all, the client uploads each run sequentially.
I'm curious if supporting parallel uploads (at least to network saturation) would be a useful feature to others.
Describe the solution you'd like
Parallel uploads – probably some set of options like --nprocs and --saturate. Maybe this makes sense even within a run, but I imagine that probably stresses the W&B side quite a bit.
Describe alternatives you've considered
Monkeypatching my install to support spinning up processes to handle uploads.
Additional context
N/A

Hi there John, this isn't in the near term roadmap but thank you for the suggestion. We'll track this as a potential addition for our next major release.

Would it be possible to bump this? @cvphelps
I unfortunately have to run things in airgapped contexts (i.e. a computing environment without Internet access) and then manually run wandb sync to upload the results. It sometimes takes a long time, but I usually am running this on a beefy machine that could do parallel uploads.


clarifying requirements for tracking

Add clarification that href must be the first argument in the <a> tag.
Add examples of failures.
Fix minor typo.
Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @jacobmovingfwd,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


No manpage for /usr/bin/pyproj

The new pyproj commandline tool has no manpage, the triggers a lintian warning for the Debian package.
docs/cli.rst is not very informative either.

Thanks for trying it out. I haven't attempted to make man pages. Will have to look into that. Here are the CLI docs: https://pyproj4.github.io/pyproj/latest/cli.html

That looks much better, and would be good to have sphinx also build a manpage from.


[docs][joy-ui] Add the Box page

[x] I have followed (at least) the PR section of the contributing guide.

Closes https://github.com/mui/material-ui/issues/35699
This PR adds a Box page documentation to the Joy UI docs. It might be a good idea to get any revision from this effort to both the Material UI and MUI System docs later (they could use it!).
https://deploy-preview-39159--material-ui.netlify.app/joy-ui/react-box/
Todos

[ ] Copywriting revision: Understand what we want to emphasize from this component.
[ ] Add demos & introduction playground.

@samuelsycamore Feel free to chime in here whenever possible, even though it's in draft. We can make progress with the copy and add the demos later!


Geneset friendly name, description, date, author?

Eventually users will be generating their own name, description, date, and author fields.
But for the built-in genesets, we currently don't have these fields. Can we possibly add them? Is description and date metadata available for KEGG and the like? As for the author, it could just be e.g. "KEGG", so more like a more generic creator/source field.

{
      "_id",
      "_score",
      "name",
      "description",
      "date",
      "author" / "source",
      "genes": [],
      "is_public",
      "taxid"
}

@dongbohu Here are the values we will use as name and description for each data source:
source: ctd
name: "${ctd.chemical_name} interactions"
description: "Chemical-gene interactions of ${ctd.chemical_name} in ${species_name}.

source: do
_id: ${do.id}
name: (The value after ":" in the current _id field.)
description: ${do.abstract}

source: go
name:
description: ${definition}

source: kegg
name: ${kegg.name}[0]
description:

source: msigdb
name:
description:

source: reactome
name: ${reactome.geneset_name}
description:

source: wikipathways
name: ${wikipathways.pathway_name}
description:

I think we can leave description blank if we cannot obtain or generate one for a datasource. We should also delete the duplicate fields.

@ravila4 Thanks. I will add the news fields for kegg, do and ctd, and you can take care of the others.

Great. I'm still undecided about the date field. I'm not sure if we have a good value to add to it.

date can be either the date when the geneset is generated by the parser, or the date when the data source is updated. I prefer the former, because when we may change the parser code, the geneset may become different (even if the data source is not updated at all).

I brought up the issue with Chunlei, and he still feels that a date field for public genesets is not that relevant.
Another reason, is that for each release we get a release notes doc like this:
Build version: '20210302'
=========================
Previous build version: '20210211'
Generated on: 2021-03-02 at 10:25:00

+--------------------+------------------------------------+------------------------------------+-----------------+---------------+
| Updated datasource |           prev. release            |            new release             | prev. # of docs | new # of docs |
+--------------------+------------------------------------+------------------------------------+-----------------+---------------+
| ctd                |                 -                  |        March-2-2021-16438M         |               - |        22,959 |
| do                 | obo-2021-01-28_genemap2-2021-02-10 | obo-2021-02-24_genemap2-2021-03-01 |           4,254 |         4,258 |
| kegg               |    Release 97.0+/02-06, Feb 21     |    Release 97.0+/02-27, Feb 21     |           5,453 |         5,456 |
| wikipathways       |              20201210              |              20210210              |           1,693 |         1,723 |
+--------------------+------------------------------------+------------------------------------+-----------------+---------------+
New datasource(s): ctd

+----------------+----------+---------+
| Updated stats. | previous |     new |
+----------------+----------+---------+
| total          |  120,332 | 143,328 |
+----------------+----------+---------+

New field(s): ctd

Overall, 143,328 documents in this release
23,002 document(s) added, 6 document(s) deleted, 1,670 document(s) updated

Modifying a field across all documents each time the uploader runs will obfuscate the statistics for meaningful data changes.

I brought up the issue with Chunlei, and he still feels that a date field for public genesets is not that relevant.

The user of the web app will definitely want to know the last update of the built-in genesets.
Also we should stop saying "public" when referring to the built-in genesets because user genesets will be able to be public or private. "built-in" or "curated" would be a better term to avoid confusion.

Modifying a field across all documents each time the uploader runs will obfuscate the statistics for meaningful data changes.

The intention was not to update all the genesets with a hardcoded date field. Our thought was that either the backend or the frontend could dynamically look up the metadata for the built-in geneset (stored only in one place) and return it with the result.

@vincerubinetti I agree on the wording, it does get confusing.
If you need the field for the user interface, I think it would be easier for the frontend to query the field from the metadata endpoint, rather than dynamically adding the field to the returned JSON for each geneset.
Nevertheless, there is another issue that in http://mygeneset.info/v1/metadata we don't have a good date string to use for individual data sources.
The closest we have are build date, which applies to the entire index... or version strings, which have inconsistent formats:
wikipathways:      "20210210",
ctd:                      "March-2-2021-16438M",
reactome:              "75",
msigdb:                 "7.2",
go:                        "20210201",
kegg:                    "Release 97.0+/02-27, Feb 21",
do:                        obo-2021-02-24_genemap2-2021-03-01"

On the other hand, hust because we re-run the uploader for a particular built-in datasource, it doesn't mean that all the genesets within it were modified, so it's misleading to conflate document datestamps with datasource datestamps.

The last missing action item in this issue was adding a way to query the last updated date for curated genesets. This has been implemented as new upload_date and download_date fields  in the https://mygeneset.info/v1/metadata/ endpoint.
    "kegg": {
      "license": "Academic service provider license",
      "code": {
        "folder": "src/plugins/kegg",
        "repo": "https://github.com/biothings/mygeneset.info.git",
        "commit": "02b2a6e",
        "branch": "master",
        "url": "https://github.com/biothings/mygeneset.info/tree/02b2a6e17aaf90b1129fb22afdf403049427aba5/src/plugins/kegg"
      },
      "stats": {
        "kegg": 5618
      },
      **"download_date": "2022-08-29T23:15:28.967000",**
      "version": "Release 103.0+/08-29, Aug 22",
      "license_url": "https://www.kegg.jp/kegg/legal.html",
      "url": "https://www.kegg.jp",
      **"upload_date": "2022-08-30T05:33:06.427000"**
    },


Ansible collection for OpenStack VM role

The following command fails:
(.snowdrop-venv)  cd ansible/ansible_collections/snowdrop/cloud_infra
(.snowdrop-venv)  ansible-galaxy collection build ansible/ansible_collections/snowdrop/cloud_infra --output build/ --force
ERROR! The collection galaxy.yml path '/Users/cmoullia/code/snowdrop/k8s-infra/ansible/ansible_collections/snowdrop/cloud_infra/ansible/ansible_collections/snowdrop/cloud_infra/galaxy.yml' does not exist.

What is the status of this PR ? @jacobdotcosta

This MR should be finished @cmoulliard . Care to take another look?


Issue when used with alpha-nvim

Description
When NNP is triggered via enableOnVimEnter and I open neovim on my dashboard styled greeter made with alpha-nvim, the whole dashboard is slightly off center. Then, if I proceed to a file from the dashboard, everything is centered properly except the autocomplete menu. Strangely, if prior to proceeding to a file, I move the cursor (on the dashboard) it brings everything back to the center (and I don't have any issues when proceeding to a file).
If I open vim on a file or folder, there is no issue.
Thanks for the amazing plugin! :+1:
Steps to reproduce
I am only able to reproduce on a wide screen (i.e., 34"), and I don't have the issue otherwise.

Set enableOnVimEnter to true
Setup a dashboard greeter with alpha-nvim
Open the dashboard

Expected behavior
Everything is centered properly when opening the greeter, or the NNP trigger is disabled until the next buffer. It might be possible to solve this using a similar approach to https://github.com/shortcuts/no-neck-pain.nvim/issues/17?
Environment

Neovim version: 0.9.5
no-neck-pain.nvim version: 1.8.1
Plugin clash: alpha-nvim

Hey @vincentlabelle, thanks for reporting the issue and I'm glad you like the plugin!!
I've tried reproducing it but so far no luck (I'm on no-neck-pain latest version, 1.8.3), I've joined a recording so you can let me know if you have a different config/do different input
https://github.com/shortcuts/no-neck-pain.nvim/assets/20689156/690270db-bea0-49e8-8708-d24311e14542

Hey @shortcuts, thanks for looking into the issue!
I don't see anything from the video in terms of config/input that could be the cause of the discrepancy. I use the dashboard theme of alpha rather than the startify theme, but I doubt that's relevant.
I've tried updating to version 1.8.3, but I still have the issue.
I've taken two videos to show how I get the issue on a 34" screen with an aspect ratio of 21:9, but I don't get the issue on a 32" screen with an aspect ratio of 16:9. I hope this can help troubleshoot.
https://github.com/shortcuts/no-neck-pain.nvim/assets/40727826/0f50eb5f-108e-42bf-aab9-dccbd5a47e73
https://github.com/shortcuts/no-neck-pain.nvim/assets/40727826/e4024388-6745-41cd-88b6-c650d0100937

Thanks a lot @vincentlabelle for the throughout reproduction, I don't have such screen at home so can't really reproduce but looking at the videos my guess is that https://github.com/shortcuts/no-neck-pain.nvim/pull/317 will fix it. Do you have a way to try the fix by installing this specific branch? e.g. if you use lazy.nvim you can do:
return {
    "shortcuts/no-neck-pain.nvim",
    branch = "feat/support-alpha",
    ....
}

Thanks @shortcuts for being so responsive! I tested #317, and it fixes the issue. 😄

Thanks @shortcuts for being so responsive! I tested #317, and it fixes the issue. 😄

Nice to hear!! Thanks for testing and using the plugin :D


SuccessResponseView overrides the chosen shipping method

I have been tracking down why my orders come through with the wrong shipping method code, but correct method name.
It's because in express checkout we have this code:
    def get_shipping_method(self, basket, shipping_address=None, **kwargs):
        """
        Return the shipping method used
        """
        if not basket.is_shipping_required():
            return NoShippingRequired()

        # Instantiate a new FixedPrice shipping method instance
        charge_incl_tax = D(self.txn.value('PAYMENTREQUEST_0_SHIPPINGAMT'))

        # Assume no tax for now
        charge_excl_tax = charge_incl_tax
        method = FixedPrice(charge_excl_tax, charge_incl_tax)
        name = self.txn.value('SHIPPINGOPTIONNAME')

        if not name:
            session_method = super(SuccessResponseView, self).get_shipping_method(
                basket, shipping_address, **kwargs)
            if session_method:
                method.name = session_method.name
        else:
            method.name = name
        return method

Is there a reason we don't attempt to use the real shipping method class and instead instantiate a FixedPrice and set attributes on it?  Is this deliberately to avoid recalculating the price?  We have the basket object here and in build_submission method, can we not trust the real shipping method object to calculate the same price again?
If we're going to do it like above it should also set the code attribute at least

Closed by #107. Thank you for the great analysis and PR.


restore possibility to "open in same window" by default

in v0.0.5 you had the possibility by default to open a project in the actual window and if you wanted it in a new window you had to specify by clicking on the cornered icon or with the command, but since the 0.1.0 it's always a new window. even when not specified. i saw there was a change in how a project is opened.
btw: i'm working on mac

You're totally right @Samba25leo. It has been bugging me a little bit too, but not enough for me to get on it right away.
I'll fix it soon when I get some free time, in the meantime, PRs are welcomed ❤

Actually, @Samba25leo it was an annoyingly easy fix so I just pushed it now. Update the extension in VS Code and it will work now 👍


Closes #1139: Add support for a customizations that use a Composable that returns a boolean

This allows nodes that change visibility to recompose or redraw without requiring the whole screen to recompose also.

While looking at this, I realized that squoosh does not support the @Composable () -> Text, @Composable () -> Meter, and now the @Composable () -> Boolean customizations. Any thoughts on how to implement that? We could recurse down the tree in the SquootRoot() composable function and call all the composable customization functions, then set some data and pass that into resolveVariantsRecursively(). However, wouldn't that recompose everything every time?

Hm, I didn't think about the Squoosh case. I wonder if we can retire all of the @Composable variations and provide State<> versions instead. State<> is nice because you can read it from some Composable, and then when the state is changed, that Composable is marked dirty for the next recomposition. So it allows similar optimizations in scoping of invalidations with a bit more flexibility (e.g.: we can read State<> in a render function).
You can update State<> in LaunchedEffects or in other coroutines.

Hm, I didn't think about the Squoosh case. I wonder if we can retire all of the @Composable variations and provide State<> versions instead. State<> is nice because you can read it from some Composable, and then when the state is changed, that Composable is marked dirty for the next recomposition. So it allows similar optimizations in scoping of invalidations with a bit more flexibility (e.g.: we can read State<> in a render function).
You can update State<> in LaunchedEffects or in other coroutines.

Even if we changed to State<>, let's say I have a State to control visibility. Every time this changed values, wouldn't entire SquooshRoot tree be recomposed every time?

Even if we changed to State<>, let's say I have a State to control visibility. Every time this changed values, wouldn't entire SquooshRoot tree be recomposed every time?

Yes, if we wanted to change the layout tree because we only edit that during recomposition (we could make it so some values are consulted during layout, then we'd just redo layout and not recomposition).
No, if it was just a rendering thing (in which case it would just redo the rendering).
Most Squoosh property changes will result in the recomposition of everything because it centralizes all of the invalidations, so I think for Squoosh State allows a bit more efficiency than Composables would.

Interesting, I thought access the value out of a State<> needed to be done in a composable function. That's quite helpful -- I updated to use State instead. Created https://github.com/google/automotive-design-compose/issues/1301 to take care of the other customizations.


v0.2.0 - Migrating to Websockets for real time updates

Initial changes for moving to websockets
Updated the way that we store light properties by getting all variables as attributes (will be used for future entities)
Changes made to Home-Assistant core to support register device callbacks (https://github.com/Xorso/core/tree/control4_wss)

I am open to design changes. I figured this would just get us started. I working on the sensors proxy now as well so we can get sensors. I don't have any door locks so I am not sure I could implement that but I do have the audio matrix and thermostats that I want to get integrated as well.

Hi @Xorso! Thanks for your PR!
I'm going to look over the code and test it on my system soon, but for now could you try formatting your code with https://pypi.org/project/black/? This helps keep code in the repo formatted consistently and prevents random formatting changes to the existing code. I'm pretty sure Home Assistant also requires Black formatting for when we make PRs to the core as well.

Interesting. I will update the PR.  I will try again.

Hi @Xorso!
I've looked over the code and made a few small comments.
One design change I was considering is to move all the websockets code (including C4DirectorNamespace and all the new callback code under C4Director) into a separate file called websocket.py.
The callback code that is currently under C4Director would become a new class called C4Websocket. Then, in the Home Assistant side, we would use a C4Websocket object to register the callbacks:
(core/__init__.py)
async def async_setup_entry(hass: HomeAssistant, entry: ConfigEntry) -> bool:
...

    director = C4Director(
        config[CONF_HOST], director_token_dict[CONF_TOKEN], director_session
    )
    entry_data[CONF_DIRECTOR] = director

    websocket = C4Websocket(director_token_dict[CONF_TOKEN])
    entry_data[CONF_WEBSOCKET] = websocket
...

class Control4Entity(Entity):
...
    async def async_added_to_hass(self):
        """Sync with HASS."""
        await super().async_added_to_hass()
        await self.hass.async_add_executor_job(
            self.entry_data[CONF_WEBSOCKET].add_device_callback,
            self._idx,
            self._update_callback,
        )
        _LOGGER.debug(f"Registering device {self._device_id} for callback")
        return True

What do you think of this?

@Xorso I ended up implementing the changes I suggested in the previous comment, please take a look and let me know what you think!
If we go ahead with this change, we will have to change the code in the Home Assistant integration to use the C4Websocket object as well.

Looks good to me. I like the idea of putting it in it's own module. You are right it keeps things cleaner. This was just a first attempt hack and Ithink there are still going to be issues to resolve along the way but It has been working out well for me (there does appear to be some frequent disconnects so we may need to adjust the keep-alive on the socket)

@lawtancool Since you fixed and merged your changes is there anything else you would like me to do with this PR?

@lawtancool Since you fixed and merged your changes is there anything else you would like me to do with this PR?

I haven't had time to test the code yet, but I think we should be done soon with this. I'll start looking at the Home Assistant code soon so we can try to merge it into the official repo.

Sounds good. Just wanted to make sure you were not waiting on me.

Thanks for your work guys.  Any chance we’ll get to see Websocket support for HA soon?  Anything I can do to help test this?
I’m experiencing controller freezes and I’m not sure if it’s related to all the HTTP polling requests sent by HA…

Any change here?

@Xorso I'm going to merge this code and release it as v1.0.0b1 to make it easier to test the Home Assistant integration code. Once the Home Assistant integration is done, I'll re-release with any necessary changes as v1.0.0.
Thanks for your work on this!


Use tiny-xlib instead of x11-dl

As of now, x11-dl takes up a significant part of our executable.

In order to avoid this bloat, especially since we only really use one function from Xlib, I've created the tiny-xlib crate to act as a small interface over Xlib and Xlib-Xcb. This PR replaces the x11-dl crate with tiny-xlib.

This patch breaks any executables using this crate on NixOS, since the tiny-xlib library is unable to find libX11 library, even if it's installed by including it in buildInputs.
In my nix-shell environment, I was able to get around this by setting the LD_LIBRARY_PATH variable like so:
with pkgs; LD_LIBRARY_PATH = lib.makeLibraryPath [ xorg.libX11 ]

This allows me to resume development on my own crate, but I don't know how I will be able to distribute it in any usable form now.

Thanks for finding this out! Please file an issue on the tiny-xlib repo

@camtauxe NixOS binary packages are routinely distributed with wrapper scripts and/or patchelf fixups to support this type of dlopen use, but you can probably also just disable the x11-dlopen feature and put xorg.libX11 in buildInputs like usual. Not sure why this patch changed anything for you, since it looks like it was using dlopen beforehand anyway?

Apologies for the sour tone in my last comment, I appreciate the advice! Disabling the x11-dlopen feature did the trick. And "dlopen" was the term I was missing when trying to describe the problem to Google, so I was able to find some help there. This thread on the NixOS discourse in particular has a variety of suggestions.


feat: hello php nginx sample (multi-containers) 🚧

Still WIP, hold off on reviewing.

/gcbrun

/gcbrun

/gcbrun

@JulienBreux When you have time to review, would love your feedback!

Since this is not lang agnostic, moving to php-docs-samples.
https://github.com/GoogleCloudPlatform/php-docs-samples/pull/1901
Closing out here.


Support for custom server domains

Please add custom Zulip server domain configuration for self-hosted setups.

@excieve this is already discussed in #1

@ff- sorry, was searching by "domain" and didn't find anything. Closing this one.


[CT-3103] [BACKPORT] [Bug] dbt show adding decimal places to non-decimal values

Housekeeping

[X] I am a maintainer of dbt-core

Short description
Backport #8153 to 1.6.latest
This will break adapter tests and needs to be coordinated with them
Acceptance criteria
Change is backported and all adapter tests run successfully
Impact to Other Teams
Some tests in adapters break as a result of this change.  Adapter functionality itself does not break.
Will backports be required?
This ticket is specifically for the 1.6 backport.  The change is already on main.
Context
No response

Currently blocked on capacity from adapters team.

Completed by #8619


Do I need to run an installer to get the config.toml file?

I am running the app from source on OSX and not finding this file in any of the prescribed locations.
Can someone share a default config.toml I can install?
In particular, I'm trying to figure out the setting that will let me set the "Home" key  (in re: https://github.com/ayntgl/discordo/issues/173)
Thank you very much

A default configuration file is created on first start-up at $HOME/.config/discordo/config.toml on Unix, $HOME/Library/Application Support/discordo/config.toml on Darwin, and %AppData%/discordo/config.toml on Windows. You can configure the default configuration path using the config command-line flag.

@ayntgl - this file is not getting created for me after running, in any of those locations

Hmmm, Ctrl+H isn't actually working after setting it and restarting.  It seems the app only loads a small batch of messages and you can't scroll up beyond that.  Understandable I guess because this is a heavily used channel with 90 thousand messages in it as of today.
[keys]
toggle_guilds_list = "Rune[g]"
toggle_channels_tree_view = "Rune[c]"
toggle_messages_text_view = "Rune[m]"
toggle_message_input_field = "Rune[i]"
open_message_actions_list = "Rune[a]"
open_external_editor = "Ctrl+E"
select_previous_message = "Up"
select_next_message = "Down"
select_first_message = "Ctrl+H"
select_last_message = "End"
~

It seems the app only loads a small batch of messages and you can't scroll up beyond that. Understandable I guess because the channel in question is heavily used channel with 90 thousand messages in it as of today.

The application loads 50 messages by default which is also default behavior of the official client. The limit can be changed from the configuration file using the messages_limit field; furthermore, the maximum limit of messages that will be fetched is 100.

no idea what "Rune" is, but I appreciate what you are doing and it must be overwhelming.

The Go language defines the word rune as an alias for the type int32, so programs can be clear when an integer value represents a code point. For characters (though there is distinction between a character and rune), you have to wrap them in Rune[x], where x is any character.

thank you for such detailed answers!

So, that suggests the max message limit of 100 means you can't jump to the first message in a channel unless the channel has less than 101 messages in it.


Aggressive completion makes it difficult to type function types.

Note that i'm just trying to write (a: string) => but i get 'a' completing out to some value.  We need a builder here.

Fixed with PR #2979


Allow Transfer/Gifting of Licenses

We want to have a way of creating products that can be gifted to others.  Not only is this great for showing appreciation for common purchasers, but it allows those with Patreon accounts or other social media accounts to do so for those who already pay money through some other mechanism.

We also want to allow redeemable codes that can be used for merchandise/integration with other services/platform.  e.g. 10% off for purchases made at an artist's Redbubble.

Consider adding gifting/transfer of licenses w/acknowledgments.


chore(main): release 2.3.0

:robot: I have created a release beep boop
2.3.0 (2022-12-21)
Features

added observability module with tracer (25839ae)

Bug Fixes

added missing observability export (1f280d4)
fixed missing metrics export (d71124b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/flowcore-io/library-flowcore-microservice-ts/releases/tag/v2.3.0 :sunflower:


Add the jexcel property to the instance in DefinitelyTyped.

To get the jexcel methods etc. in the jspreadsheet event, write as follows
  (instance: any, cell, c, r, source) => {
    const value = instance.jexcel.getValueFromCoords(...) ;

Currently DefinitelyTyped's  instance is typedefed as HTMLElement, is it possible to add a jexcel property as follows?
instance: HTMLElement & { jexcel: JSpreadsheetElement }

I can define the above myself in a TypeScript project, but it would be very helpful if it existed at the time of DefinitelyTyped.

@Ruan-Miguel


Support installation with rnpm

Added support for easy installation with rnpm.
Also updated README installation instructions.

+1 to this. I installed via rnpm and had to go edit MainActivity.java.

👍

👍

Since the "this" parameter is no longer required, this change shouldn't be needed to install with rnpm, as "new ExtraDimensionsPackage()" is added by default. Can someone confirm this? It may be a week or so before I can test it.

that's correct @sirnacnud

If anyone is interested, I've forked this repo and implemented support for rnpm. I've also ensured it works the current version of React Native 0.37
It looks as if @jaysoo isn't here to maintain this project

This is now in the newest version - Thanks for contributing!


Pr/attachments fclose

If some file is added using unreal4u\TelegramAPI\Telegram\Types\Custom\InputFile(), file is locked using fopen() and read via stream_get_contents() but it is never closed. Usually it doesn't matter, because lock is released once PHP script is finished but in specific situations, it is causing troubles. Steps to reproduce:

create directory some-dir
create file some-dir/some.file
upload it using InputFile() and SendDocument()
delete file some-dir/some.file (file is really deleted)
delete directory some-dir (warning will occure, that Directory is not empty and directory is not deleted)

In this PR I also added real example with these steps, see examples/send-document-custom-name.php.
Disclaimer
It seems, that warning is occuring only on Windows not on Linux, can someone run more tests?
Tested on:

Windows 10, PHP 7.3.21, 7.4.9 and 8.0.9
Linux Ubuntu 20.04.3, PHP 7.4.3

While I think this is an okay option for the short term, I don't think it should be the post option builder's responsibility to close file handles.
Instead, I'd rather have methods for clearing file handles on InputFile, like a close() method or similar.
After taking a look, InputFile is inherently broken because it calls setStream() on every invocation of getStream(), which in turn does a fopen call every time without checking if the resource is already open.
Adding this to InputFile and fixing up that mess (by adding file handle availability checks?) puts the user in charge of the file handle lifecycle. While this does add an extra necessary step ($inputFile->close();), the initial opening can be implied by the constructor.
Anyway, that's my two cents for this mess. Regarding the PR, again, I think it's an OK solution until the rewrite, but it might cause unexpected bugs down the line. I'm not sure if this can be put in a minor patch release; OTOH, setStream should reopen the stream if it was ever closed.

Thanks for your input!
I agree it might not be job for post builder, but it should be closed once it is uploaded, that is for sure.
I still don't have necessary knowledge of this library so I don't have strong opinion who's job closing is, so you can update it as you want. First though was it could be in InputFile()->__destruct() but it is too late so as you wrote - user would need to call it manually. Or it could be destroyed somewhere in library automatically.

Object destructuring in PHP unfortunately is unreliable as not enough care is generally taken for object life cycles, this could leave the file handle open for much longer than intended as you mentioned. Forcing object management on users is another can of worms I wouldn't put in this library.
Maybe a more elegant solution would be to expose a method which expects a callback, where only in that callback the resource is available through its parameters. This would provide automatic file handle lifecycle management by the InputFile object and also in the best case prevent accidental leaking of the handle elsewhere (unfortunately we can't battle stubborn developers who steal the handle from said closure).
I think @unreal4u is planning to do a major rewrite of the library soon(Tm) so depending on that we could fix up InputFile as-is, or implement this patch. Might be worth waiting for his input on this.
If the rewrite will be much later, I'd be in favour of a proper fix now which could perhaps be ported to the new version.
Thanks for bringing this up anyway, it's food for thought and it does impact the architecture of the rewrite, so it's worth thinking about now.

Difficult one: InputFile comes from the days where this library wasn't async yet, and I had to pass on a stream to curl.
As for responsibilities, InputFile should do this, however you would need to do this manually: I don't like that. The user doesn't open the file manually, so neither should he/she close it manually.
I was thinking that getStream() will know and can close the file appropiately: however since it is a stream, we can't close yet until we have appended it.
I will merge this PR for now, but I'll need to check out this properly. The idea of opening a file in the constructor was a very bad one, but fo fix it we'll have to rewrite InputFile entirely. This is something we can do for the big rewrite.

made a new card for this: https://github.com/unreal4u/telegram-api/projects/5#card-69531588


Is this possible to do 2 balls range in one slider?

Is this possible to do 2 balls range in one slider?
like this:
https://i.imgur.com/MjblcxN.png

This feature is the range slider, which is already requested #269
Please keep the progress in the linked issue.
I will close this item as a duplicate.

This feature is the range slider, which is already requested #269
Please keep the progress in the linked issue.
I will close this item as a duplicate.


WASM Error: Memory access out of bounds

Complete error:
RuntimeError: memory access out of bounds
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:670612
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2248216
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2240349
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2237935
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2189441
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2491805
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2213847
 ❯ ../../node_modules/.pnpm/@dcspark+cardano-multiplatform-lib-nodejs@5.3.0/node_modules/@dcspark/cardano-multiplatform-lib-nodejs/cardano_multiplatform_lib.js:19117:79

Accompanying error:
Error: recursive use of an object detected which would lead to unsafe aliasing in rust
 ❯ module.exports.__wbindgen_throw ../../node_modules/.pnpm/@dcspark+cardano-multiplatform-lib-nodejs@5.3.0/node_modules/@dcspark/cardano-multiplatform-lib-nodejs/cardano_multiplatform_lib.js:37518:11
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2501206
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2501220
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2211768
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:1633196
 ❯ null.<anonymous> wasm:/wasm/00a747c2:1:2180248
 ❯ ../../node_modules/.pnpm/@dcspark+cardano-multiplatform-lib-nodejs@5.3.0/node_modules/@dcspark/cardano-multiplatform-lib-nodejs/cardano_multiplatform_lib.js:11775:77

So far this error has been observed to occur after successfully submitting a transaction using the Staking Validator design pattern (multiple script inputs being spent along with a withdrawal). The transaction gets successfully confirmed too every time. A reproduction has been added as a test in branch fix/memory-access-out-of-bounds.
Once such failed test run
Attaching code snippets for source of these errors in cardano_multiplatform_lib.js:

Line  11775: const Ed25519KeyHashListFinalization = new FinalizationRegistry(ptr => wasm.__wbg_ed25519keyhashlist_free(ptr));
Line  19117: const PartialPlutusWitnessFinalization = new FinalizationRegistry(ptr => wasm.__wbg_partialplutuswitness_free(ptr));
Line  37491: const WithdrawalBuilderResultFinalization = new FinalizationRegistry(ptr => wasm.__wbg_withdrawalbuilderresult_free(ptr));

I have encountered the same issue. Here's the log
`RuntimeError: memory access out of bounds
RuntimeError: memory access out of bounds
at wasm://wasm/00a7830e:wasm-function[611]:0xea2bb
at wasm://wasm/00a7830e:wasm-function[273]:0xa40bc
at wasm://wasm/00a7830e:wasm-function[2409]:0x18fa81
at wasm://wasm/00a7830e:wasm-function[5312]:0x21532b
at /home/runner/work/mynth-swaps/mynth-swaps/packages/mynth-swaps/node_modules/@dcspark/cardano-multiplatform-lib-nodejs/cardano_multiplatform_lib.js:11775:77
at FinalizationRegistry.cleanupSome ()`
This happens when I run a more than 3 tests cases which are doing transactions using smart contracts and chaining. If I run the tests in batches of 3 all of them pass, however, if I run all together I get this error for 4th or 5th test. Am concerned in the real world we might start facing this issue when we have actual users. Can you please look into this?

@nikhils9 try the new version

The latest version 0.2.45 fixes this issue. Successful test run


update README install commands

Thanks so much for the work you guys have done updating the gatsby-source-bigcommerce code! It's amazing timing for a project I'm working on. Just a small PR here to help others with the install.

@shanejdonnelly Hey there. Thanks for this pull request. This is a welcome change for the README docs. I just recently made an effort to maintain this repo since the original gatsby-source-bigcommerce plugin is already outdated and had a lot of issues and pull requests that were left unresolved. :)


Add tokio asyncread implementation

Well, here you go, my first try! I've currently only implemented for tokio, because I'm lazy enough.
Also, the new load_from_path_async  methods signature changed as I find it more idiomatic.
The example is also updated to use async.
yes I know, we also need a async-std and smol implementation but im too lazy for that 🤓
Open to suggestions, as always!
Fixes #1

Thanks for this! I'm not sure we need to worry about supporting a sync API so I think we can just call things from_reader and load_from_path. Then we can conditionally choose which implementation we use depending on feature flag.
I think the default implementation can use https://github.com/smol-rs/async-fs and I think it'll work for all the other executors (threadpool, smol & async-std) but I can test this. So we may only need the tokio feature.

Thanks! I'll get this wrapped up w/ the non-tokio async implementation.


Compatibility with Windows 11

Install and check the application compatibility on Windows 11 operating system.

After a bunch of tests, the application looks to be fully compliant with Windows 11 :tada:


How to add CQA to LUIS Dispatcher

Hi, I know how to create and add QnA maker to Luis Dispatcher.
But we cannot find Adding CQA to Luis Dispatcher  Can anyone help us with it !

The recommended approach would be to use Cognitive Service for Language's orchestrator workflow to generate the combined language model. We don't yet have a sample for how to do that from the Bot Framework.

@JonathanFingold  Thank you so much

@JonathanFingold
Can we use the downloaded CQA KB (json/tsv) adding to the dispatcher as a file. Since we are aware of that command.
"dispatch add -t file -n TestModule3 -f c:\src\testmodule3.json"

I've pinged the engineering team. Hopefully, they'll be able to comment soon.

@JonathanFingold
As per our requirement, we have added .tsv file from CQA to Luis Dispatcher and it's working fine.
Thank you :)


Added a GLFW/Vulkan backend.

Note: I developed this in a container as not to pollute my wider WSL installation.
This may not work as intended as I am currently having trouble with the project that intends to consume this having trouble building and having it exist in its workspace (another docker container).

Hi @grahamreeds, thanks for the PR! :) I'll try to have a look sometime this week or weekend and hopefully merge it if all good.


Add bootargs.cfg docs

This commit adds some documentation about the purpose and use cases
of the /etc/cos/bootargs.cfg file regarding grub2 configuration and
boot parameters.
Related to #237
Signed-off-by: David Cassany<EMAIL_ADDRESS>

I didn't included this in https://rancher-sandbox.github.io/cos-toolkit-docs/docs yet, care to add it in there instead? we have a GRUB section here .. only because #418 drop entirely the docs folder :smile:

I didn't included this in https://rancher-sandbox.github.io/cos-toolkit-docs/docs yet, care to add it in there instead? we have a GRUB section here .. only because #418 drop entirely the docs folder smile

Sure, let me close this PR and I'll do a new one there.


wish: document which conditions trigger retries.

Another retrying module retries when the error is ECONNRESET or ETIMEDOUT. It appears you retry any time that the request-promise would reject. That's a useful detail to clarify in the docs.

@markstos This is actually the intention of doing the retry. Post adding the delay mechanism, no matter what the outcome of the request is, the request will be retried, in case retry is allowed.


Added a Godot theme

I think this theme captures the Godot spirit well, making it a perfect fit for a GameMaker tool. I hope you'll agree that including this theme is sure to attract the attention and admiration from developers far and wide. Also, it will be funny.

Honestly, why not - besides, I already made a GM theme for Godot as part of an April Fools joke


Getting shader include errors with URP 13.1.8

Hey I'm getting these two errors:
Shader error in 'Shader Graphs/ShadowReceiver': Couldn't open include file 'Packages/com.cyanilux.shadergraph-customlighting/CustomLighting.hlsl'. at line 210
Shader error in 'Shader Graphs/ShadowReceiver': Couldn't open include file 'Packages/com.cyanilux.shadergraph-customlighting/CustomLighting.hlsl'. at line 877
Any ideas?

Try restarting Unity. If that doesn't work, maybe remove the package and reinstall it.


Can't create  mount and move /tmp/Dynatrace-OneAgent-Linux.sh

Hi  Team,
I am on 1.19.9-gke.1900 and hitting this issue when installing dynatrace-operator

wrong repo


Clarification added to WEBAUTHN_CLIENT_DATA

If I understood it correctly, collectedClientData holds data collected by the browser, where origin and cross.origin are taken from the browser's environment, while others come from the WebAuthn API.  The point I'm trying to do is that this JSON data is created by the trusted browser WebAuthn driver and is therefore not parsed or interpreted by the "by design" fairly limited authenticators.  The purpose is being able to return a bunch of vital objects signed by the authenticator to the RP.  For non WebAuthn use cases, the value of this JSON object is limited and as I wrote, actually could be any binary data. There are such applications:
https://fido-web-pay.github.io/specification/crypto.html#4.2

The correctness of the clarification has been extensively tested: https://github.com/cyberphone/ctap2-sign
I have unfortunately not been able to get it to work with Android although it is quite similar: https://developers.google.com/android/reference/com/google/android/gms/fido/fido2/api/common/PublicKeyCredentialRequestOptions.Builder#setChallenge(byte[])


Possibilities of sorting MutableObservableArray

I was wondering if it was possible to sort the MutableObservableArray based on alphabet. This is the code I have so far :
class ViewController: UIViewController {

    var letters = MutableObservableArray(["z", "x","y", "b","a", "c","d", "q"])
    @IBOutlet weak var tableview: UITableView!

    override func viewDidLoad() {
        setupCellConfiguration()
        Timer.scheduledTimer(timeInterval: 3, target: self, selector: #selector(add), userInfo: nil, repeats: true)
    }

    func add() {
        self.letters.append(UUID().uuidString)
    }

    private func setupCellConfiguration() {

        self.letters
        .filter({ (chat) -> Bool in
            return chat != "x"
        })
        .bind(to: tableview) { letters, IndexPath, tableview in
        let cell = tableview.dequeueReusableCell(withIdentifier: "cell")
        cell?.textLabel?.text = letters[IndexPath.row]
        return cell!
        }
    }

    }

If not, is there some kind of workaround?

I know it's late for the answer, but MutableObservableArray does not support sorting. You'll have to make sure to insert items in the right order.


Enhanced README file

Pretty much the same. Just filled in some of the blanks.

Thanks for the PR :+1:


fix aum rounding error

fix small rounding error see #142

closed as dupe, merging to 4.0.2 branch first for testing


bump to external dns 0.13.5

Description
bumps us to external dns 0.13.5.
Need to land on this version before jumping to higher versions because of this. This is documented by ExternalDNS.
We also need to document this breaking change made by ExternalDNS that will come into affect as part of this bump. This change will land in a minor k8s preview version so customers are well informed of this.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.471%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2905

Relevant Lines:
3610

💛  - Coveralls

/ok-to-test sha=362a538

/ok-to-test sha=4ee2005

/ok-to-test sha=4e29c80


Update README.md

Codecov Report

Merging #1265 (afbd4d3) into master (7126c48) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1265   +/-   ##
=======================================
  Coverage   77.37%   77.37%
=======================================
  Files         272      272
  Lines        7731     7731
=======================================
  Hits         5982     5982
  Misses       1390     1390
  Partials      359      359


Cherry-pick: update snapshot and timestamp

This was done in a second branch (fixroll) and then cherry-picked to main to ensure it worked.
See #110 for details.
Signed-off-by: GitHub<EMAIL_ADDRESS>
Summary

Ticket Link

Fixes
Release Note

I'll push a fix for CI

In https://github.com/sigstore/root-signing/pull/113

No longer needed?


feat: add pickBy

Description
Please provide a detailed description of the changes and the intent behind them :)
Checklist

[x] Changes are covered by tests if behavior has been changed or added
[x] Tests have 100% coverage
[x] If code changes were made, the version in package.json has been bumped (matching semver)
[x] If code changes were made, the yarn build command has been run and to update the cdn directory
[x] If code changes were made, the documentation (in the /docs directory) has been updated

Resolves
Resolves #157

Hey @yubaoquan, we've merged this feature over at the Radashi fork, where we're bringing Radash to new heights. We've made a lot of improvements already, and it'd be great to have you there. 😄
You can install radashi@beta to use this feature today. An official release is pending.
P.S. You can read my post to learn more about the differences between Radashi and its predecessor.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test

Docs Build status updates of commit 67b6af7:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 67b6af7:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-27-03-21-49 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-27-03-21-49

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Pop Layout Clean Up

Pop layout could be utilised more widely (by get data and the project detail pages).
To achieve this, the tab component used by the pop layout will require greater flexibility (receive the required tab inputs from the parent component).

[x] A good first pass would be to set up these inputs.
[ ] The second pass should be re-use of the pop layout by get data and project detail pages.

@MillenniumFalconMechanic first pass complete.  Second pass to be completed when #711 is resolved.

@MillenniumFalconMechanic second pass complete.


support silversearcher-ag

support silversearcher
https://github.com/ggreer/the_silver_searcher
The current silversearcher has bug, so this script can't work.
I send patch silver searcher.
This version can work properly.
https://github.com/ggreer/the_silver_searcher/pull/351/files

I like the idea of this source and would like to add it.  When I try to test it, though, zsh crashes on a "double free or corruption" error.  I'm not sure what's causing it, but it happens on both zsh 5.0.7 and zsh 5.0.5.

@willghatch I cannot reproduce the crash in both zsh 5.0.7 and 5.0.8,
and I confirm it works appropriately.

Hmm, it may be OS dependent.  What OS do you have?  (I'm on Arch Linux).  I'm not sure what to do here -- it would be great for those who have a zsh that doesn't crash on it, but I wouldn't want unsuspecting users to get a nice core dump and potentially closed terminal window and then have them think that zaw sucks.

I just tested on a couple servers I run, one with Debian Stable and one with Ubuntu Trusty (I think that's the current LTS) and I get a double free or corruption error on both.

I am testing on ArchLinux too.
When I test on ubuntu:latest docker image (Trusty) with smallest .zshrc
source $HOME/zaw/zaw.zsh

it does not crash though it does not work well because ubuntu use old version of ag (0.19).
(zsh version is 5.0.2)
I suspect that your settings of zsh causes the crash.
Could you test in clean environment?

So some quick printf debugging shows me that it crashes on line 36 of the ag source, where the anonymous function returns.  If I comment out the anonymous function header/ending (IE inlining/lifting the contents of the function) it then crashes at line 67, where the zaw-src-ag function exits.  So... somehow in a very reliable way zsh is crashing on a function return for me.  I don't think I'll take time to compile a debug version of zsh and try to step through it right now.  And besides, I'm terrible with gdb.
But, if I comment out lines 24, 25, 27, and 33 it stops crashing and works fine.  It just adds the ag command that was used to the history.
And since you wrote your last comment while I was writing this, I tested with a clean zshrc and you're quite right.  So I'll have to figure out what in my settings is causing this to crash if it does that history stuff.

Sorry for all the confusion of my setup causing crashes.  I'll have to remember to test things with a minimal environment...


python spec endpoint

Current dependencies on/for this PR:

main

PR #48   👈

PR #49

This comment was auto-generated by Graphite.


Limit on concurrency

What's the limit on concurrency? If we have 10k messages in the queue, will this spin-up 10k PHP processes at the same time?

The rabbitmq-cli-Consumer does not deal with concurrency. It processes one message at a time. If you need concurrency, you can spin up as mutch instances as you need.

@corvus-ch Would you be willing to accept a PR that implements handling of concurrency? We currently have a PHP version of what rabbitmq-cli-consumer does, which basically runs sequentially as well. We upscale our Kubernetes pods based on the queue length, but that seems all a bit wasteful.

Dealing with concurrency is a complexity I tried to keep out of the project. The way it is designed is to delegate it to a suitable process supervisor. With Kubernetes in mind (and similar platforms for that matter), I can see why this might be helpful from an orchestrationanl point of view.
If I would accept such a PR, the following requirements must be met:

The default must be the current behaviour.
It must be possible to keep the log output for different messageages apart. Here I refer to the STDOUT and STDERR captured from the script processing the message.

With those two things in mind, feel free to go ahead and provide PR.

@corvus-ch Working through the code I'm wondering why the func (p *processor) Process is given the message as type delivery.Delivery instead of just the plain message.
Shouldn't the responsibility of ack/nack'ing be lying on the consumer?

@corvus-ch I have something that is working to some extent, but I'm not sure where that exception is coming from.
2019/02/27 14:41:50 Connecting RabbitMQ...
2019/02/27 14:41:50 Connected.
2019/02/27 14:41:50 Opening channel...
2019/02/27 14:41:50 Done.
2019/02/27 14:41:50 Setting QoS...
2019/02/27 14:41:50 Succeeded setting QoS.
2019/02/27 14:41:50 Declaring queue "foobar"...
2019/02/27 14:41:50 Registering consumer...
2019/02/27 14:41:50 Succeeded registering consumer.
2019/02/27 14:41:50 Processing messages with 3 workers.
2019/02/27 14:41:50 Waiting for messages...
2019/02/27 14:41:50 [Worker 2] Processing message...
2019/02/27 14:41:50 [Worker 0] Processing message...
2019/02/27 14:41:50 [Worker 1] Processing message...
hellohello2019/02/27 14:42:00 [Worker 0] Processed!
2019/02/27 14:42:00 [Worker 0] Processing message...
hello2019/02/27 14:42:00 [Worker 2] Processed!
2019/02/27 14:42:00 [Worker 2] Processing message...
2019/02/27 14:42:00 [Worker 1] Processed!
2019/02/27 14:42:00 Exception (406) Reason: "PRECONDITION_FAILED - unknown delivery tag 1"

@estahn Can you do a pull request with your changes so I can have a look?
Searching for that error on the web, indicates that your code might be mixing up messages and acknowledgments and or that sharing channels across threads/(go functions?) is an issue. Without looking at the code, it is not possible for me to tell what the issue is.

@corvus-ch Will do shortly. I think the issue is double acking of the message (https://github.com/streadway/amqp/issues/83).

Just some comments:

I have removed the mutex from the processor as I think it is not necessary if you move variables into local scope. If you want to keep the mutex then the current solution isn't working.
There are sporadic issues manifesting in unknown delivery tag 1. Possibly double ack-ing the message.

In order to find what the issue with the unknown delivery tag is, I have hacked together a minimal example.
package main

import (
	"flag"
	"log"

	"github.com/streadway/amqp"
)

var (
	uri   = flag.String("uri", "amqp://guest:guest@localhost", "AMQP URI")
	queue = flag.String("queue", "myqueue", "Ephemeral AMQP queue name")
	ctag  = flag.String("consumer-tag", "simple-consumer", "AMQP consumer tag (should not be blank)")
)

func init() {
	flag.Parse()
}

func main() {
	conn, err := amqp.Dial(*uri)
	if err != nil {
		log.Fatalf("dial: %v", err)
		return
	}

	channel, err := conn.Channel()
	if err != nil {
		log.Fatalf("channel: %v", err)
		return
	}

	queue, err := channel.QueueDeclare(*queue, true, false, false, false, nil)
	if err != nil {
		log.Fatalf("queue Declare: %v", err)
		return
	}

	if err := channel.Qos(5, 0, true); err != nil {
		log.Fatalf("qos: %v", err)
		return
	}

	deliveries, err := channel.Consume(queue.Name, *ctag, false, false, false, false, nil)
	if err != nil {
		log.Fatalf("queue Consume: %v", err)
		return
	}

	done := make(chan error)

	for i := 0; i < 10; i++ {
		go handle(i, deliveries, done)
	}

	if err := <- done; err != nil {
		log.Fatalf("error during message consumption: %v", err)
	}
}

func handle(i int, deliveries <-chan amqp.Delivery, done chan error) {
	for d := range deliveries {
		log.Printf("[%d] got %dB delivery: [%v] %q", i, len(d.Body), d.DeliveryTag, d.Body)
		if err := d.Ack(false); err != nil {
			done <- err
		}
	}
	done <- nil
}

The issue lies with the message acknowledgement. The boolean passed to Ack() is set to true the current and all prior unacknowledged messages will be acknowledged. With concurrency in place, this can lead to a situation where a worker tries to acknowledge a message which was already acknowledged by another worker. This occurs if worker A is processing message 1 and worker B is processing message 2 and worker B finishes before A. Once worker A tries to acknowledge its message, the error occurs.
To fix this, the boolean in https://github.com/corvus-ch/rabbitmq-cli-consumer/blob/master/delivery/delivery.go#L28 and https://github.com/corvus-ch/rabbitmq-cli-consumer/blob/master/delivery/delivery.go#L33 needs to be changed to false.

@corvus-ch Yay! Nice job tracking this down!
Docu: https://github.com/streadway/amqp/blob/master/delivery.go#L113-L115
I'll add the adjustments.

Hi all - I also needed an option for message processing concurrency, and wanted to implement it using multiple RabbitMQ channels to be as close as possible to how our project handles RabbitMQ in other languages (we have consumers in node and python, as well as PHP). This seems to be the canonical way to handle multiple concurrent consumers in a single client in RabbitMQ.

@corvus-ch What is the intent of the mutex in processor.Process? After further testing, my multi-channel solution is fetching messages in parallel, but only processing one at a time because each call has to wait for the mutex to free up. The simple solution is to remove the mutex, but that could obviously cause issues that I'm not seeing. The more complicated solution would be to have a separate processor per channel, but I don't want to pursue that solution if there's a simpler one.

@corvus-ch I think I answered my own question - Processor had a single os.Cmd that it was re-using for each new call. I just pushed an update to my PR that uses a new os.Cmd for each call to Process instead.


[BUG]

Version of Advanced Rocketry
AdvancedRocketry-1.12.2-1.5.0-139-universal.jar
Have you verified this is an issue in the latest unstable build

[x] Unfortunately No, AdvancedRocketry 1.12.2-1.5.0-139-UNSTABLE-deobf build -139 for 1.12.2 will not load. causes minecraft to crash

Version of LibVulpes
LibVulpes-1.12.2-0.4.0-56-universal.jar
Version of Minecraft
1.12.2
Does this occur without other mods installed

[x] N/A, it is an issue within advanced rocketry, the connection of two blocks

Crash report or log (if applicable)
http://pastebin.com is a good place to put them
crash reports that are put in the issue itself are
hard to read

no crash with stable version of mod, space station assembler just does not get power with normal input plug

Description of the problem

Space station assembler unable to get power from input plug on any side, however it does get power from creative input plug, was able to reproduced the issue in both multiplayer survival and single player creative.

I will attach screen shots, which will hopefully help. Thank you, fully willing to admit I am doing something wrong, just can't figure out what.
to show setup trying to input power from multiple sides

to show assembler interface is not getting power

To show input plug is getting power

to show creative plug has power (obviously it would, just a demonstration)

to show assembler gets power but only with creative input plug

to show device does work, but only with creative power.

This is expected behaviour, the rocket assembling machine takes power directly and doesn't need a plug.  There's no need for a battery block on it.  The reason the creative battery works is because it's outputting power the the rocket assembling machine.
I hope this helps!

ok thank you, my main power comes though flux plugs, which didn't seem to provide it power, I will try other power options. and the videos I have been watching as a tutorial have the creative so I assumed the input was required. amazing mod. just building my rocket now for the first time.


Update to the latest lets-encrypt version: v0.4.0

Is there a reason or incompatibility why the version currently defaults to v0.1.0 here?
lets-encrypt released v0.4.0 a couple of days ago, and I think I would be nice to upgrade the default.
And with this new release there is now support for a renew command, which could be used in the cron job.
https://letsencrypt.readthedocs.org/en/latest/using.html#renewal

No deliberate reason for this. PRs are welcome ;)

Closed via #15


DeltaManager: refactor out connectivity manager

First step on separating Container-DeltaManager layers into smaller, more manageable and replaceable/swappable layers.
Ultimate goal - be able to have various implementations suitable for various needs (like Word scenario not caring about reconnects, and thus ideally preferring API shape that does not have notion of reconnects on it). This also might cause re-evaluation of existing interfaces (like driver interface) and potential shift of responsibilities in the future.
In this change I extracted connectivity logic into its own class and for most part hidden it behind interface. DeltaManager only depends on such interface, while Container can reach out to particular class. This is done with the goal of future refactoring of Container class into base class (that will depend only on interface) and leaf derived classes that will control actual policy / create particular implementations of connection manager (or possibly - push this out to users).
I tried to preserve existing behavior exactly as it was, but in some cases I had to change slightly semantics, logic or ordering of events to make it possible to separate things into layers. I believe each such case is safe, but more testing is required. It might be hard to see these places, as most code changes happened in newly created file.
Please note that the shape of API is not final and mostly reflects how code was structured before my changes. But these changes allow easier future changes in this space.

Ping


Image references mutated even when mode is set to insecureValidateOnly

Describe the bug

Image references in the pod definition is mutated and the digests are included even when with.mode is set to insecureValidateOnly in the policies.
Below is the extract from connaisseur-app-config configmap.
data:
  config.yaml: |
    validators:
    -
      name: default
      trustRoots:
      - key: |
          <KEY>
        name: default
      type: cosign
    policy:
    -
      pattern: '*:*'
      validator: default
      with:
        mode: insecureValidateOnly
        verifyInTransparencyLog: false

Logs in the Connaisseur pod
{
  "level": "info",
  "msg": "successfully validated image customacr.azurecr.io/stakater/reloader:v1.0.95 using rule *:* and validator default. Result is customacr.azurecr.io/stakater/reloader:v1.0.95@sha256:5e15985882a8312abe5281aaae61301089244d5a33470eba16a7aeca715340c9.",
  "time": "2024-11-10T15:28:24Z"
}

This is just an example. Same issue is happening with all the images.
Expected behavior

Only the validation should happen and the image references should not be mutated.
Optional: To reproduce

Deployment with the above config should reproduce the issue
Optional: Versions (please complete the following information as relevant):

OS: Redhat8.6
Kubernetes Cluster: RKE2 (1.30.5)
Container registry: Azure Container Registry
Connaisseur: v3.7.0

Optional: Additional context

This causes applications as OutOfSync in Argocd. Is any additional configuration needed to do only validation?

Hi @phbelitz
Thanks for the fix. When would this change get published?


[WIP] Rails 5 upgrade

Awesome work @matthewd !  Can any of this be extracted and used ahead of time ni the Rails 4 code base?  I'm looking at things like the helper changes in the helper specs as an example.
cc @tenderlove

Can any of this be extracted and used ahead of time in the Rails 4 code base?

Yeah.. I'll plan to extract a couple (like the helpers) which seem conflict-prone to keep separate. For most, even if they're 4.2-compatible, it shouldn't matter once I tame VirtualColumn and get this green.

Yeah.. I'll plan to extract a couple (like the helpers) which seem conflict-prone to keep separate. For most, even if they're 4.2-compatible, it shouldn't matter once I tame VirtualColumn and get this green.

Nice work @matthewd !!!  You can do it!

wow. this is looking very close

tests failing on draper gem ;)
LoadError: cannot load such file -- active_model/serializers/xml
gems/draper-2.1.0/lib/draper.rb:5:in `require'
gems/draper-2.1.0/lib/draper.rb:5:in `<top (required)>'
gems/bundler-1.11.2/lib/bundler/runtime.rb:77:in `require'
gems/bundler-1.11.2/lib/bundler/runtime.rb:77:in `block (2 levels) in require'
gems/bundler-1.11.2/lib/bundler/runtime.rb:72:in `each'
gems/bundler-1.11.2/lib/bundler/runtime.rb:72:in `block in require'
gems/bundler-1.11.2/lib/bundler/runtime.rb:61:in `each'
gems/bundler-1.11.2/lib/bundler/runtime.rb:61:in `require'
gems/bundler-1.11.2/lib/bundler.rb:99:in `require'
config/application.rb:12:in `<top (required)>'
Rakefile:5:in `require'
Rakefile:5:in `<top (required)>'
(See full trace by running task with --trace)

:tada: :tada: :tada:
:clap: @matthewd


New integration tests #19

Hey Aaron, nope nothing specific.  I'll go through the code review with a couple others as well and get this merged in!


sign main assembly

if we are to sign Confluent.SchemaRegistry and Confluent.SchemaRegistry.Serdes, all their dependencies must be signed.
i'm aware there are white-space changes.

see https://github.com/confluentinc/confluent-kafka-dotnet/issues/973#issuecomment-508270026


Clarify for TIs who they are logged in as vs who they are applying on behalf of

When a TI goes to apply on behalf of a client, CiviForm shows at the top of the screen "Apply as: Jenny Lee" and also "Logged in as: Jenny Lee." This copy is confusing for TIs.
@sijiayam I'd suggest implementing the sub banner you created in the header and footer exploration unless you'd like to head another direction? https://www.figma.com/file/RmhVJCLgAKWGENJLWWAtNS/CiviForm%3A-Components%2C-Styles?type=design&node-id=1014%3A3542&mode=design&t=oYxUgVr20cUbNupL-1

Wondering if the "guest" version of this banner could also be used for the TI in the scenario where they decide to apply on behalf of someone without making a client first.
In that case, the CTA would be "add this client" and it would take them to the client creation view AND ideally, use the info already entered in the application.

Should solve issue: https://github.com/orgs/civiform/projects/1/views/59?pane=issue&itemId=30602588

@isabelcshaw Could you help me understand how adding the sub-header will solve the issue of what user is displayed as logged in?  The header mocks only show "Applying for..."  I suggest that we keep the other bug separate from the work of adding the new header.

Wondering if the "guest" version of this banner could also be used for the TI in the scenario where they decide to apply on behalf of someone without making a client first.

@isabelcshaw does the functionality of a TI applying for someone who is not a client already exist?  If not, I propose that this work be separated from that of creating the new header.  It could be fairly complex and require a PRD and TDD.  I also don't see a "guest" version of this banner.  Where can I find that?

@melanie-exygy these are great callouts!
Some preliminary thoughts before our sync later:

You're right - the ability to view/browse programs without selecting a client first is a future looking workflow that we currently don't support, so any type of "guest" workflow is not a part of this issue

To complete:

Remove 1
Add banner at 3
Update 2 to reflect the TI --> this to be pulled out into a separate issue

Perfect.  That completely answers my questions.  Thank you!

@sijiayam In the mock, I see "You are applying for First Name, Last Name".  Do we want a comma between the first and last name or should this be "Last Name, First Name" the way we have now?

@melanie-exygy LEts go with "First Name Last Name" ex. "Jenny Lee" like we currently have. Apologies for the mistake!

@sijiayam For the name format, we actually currently have "Last Name, First Name".  It would be easier to keep the format the way it is.  Would that be okay?

@melanie-exygy I think its fine to keep the current name format.
As for isabels question above, lets keep the big blue button for now. I think without the header update its not clear a quick path back to the client dashboard.


How to bind a nested class property to the attribute of html element with GetEncapsulatedData Method?

https://github.com/zzzprojects/html-agility-pack/blob/c12580b2025144d618d3397dec1fd81132e3f822/src/HtmlAgilityPack.Shared/HtmlNode.Encapsulator.cs#L298
In most situations， I like to use XPath attribute binding to a Property. But in the nested class, it can not access the parent node, the parent node's attribute often records some important information, like id.

   [HasXPath]
    class TestA
    {
        [XPath("a")]
        public List<Item> Items { get; set; }
        [HasXPath]
        public class Item
        {
            [XPath(".", "href")] //not working
            [SkipNodeNotFound]
            public string Href { get; set; }

            [XPath(".")]
            [SkipNodeNotFound]
            public string Name { get; set; }
        }

    }

    var html = @"

Hello
1.html
2.html

World

";

     var document = new HtmlDocument();
     Document. LoadHtml(html);
     var testA = Document. DocumentNode.GetEncapsulatedData<TestA>();

In the HtmlNode.Encapsulator.cs#L298,  Is using OuterHtml better than InnerHtml?

In the HtmlNode.Encapsulator.cs#L298, Is using OuterHtml better than InnerHtml?

The bug seems to be not adhering to the [XPath] attribute's NodeReturnType value here (the NodeReturnType value is supposed to govern whether InnerText, InnerHtml or OuterHtml is used for "encapsulation".
HtmlNode.Encapsulator.cs#L298 isn't the only place exhibiting this issue,
https://github.com/zzzprojects/html-agility-pack/blob/c12580b2025144d618d3397dec1fd81132e3f822/src/HtmlAgilityPack.Shared/HtmlNode.Encapsulator.cs#L298
HtmlNode.Encapsulator.cs#L180 also forgets to take HasXPathAttribute.NodeReturnType  into account:
https://github.com/zzzprojects/html-agility-pack/blob/c12580b2025144d618d3397dec1fd81132e3f822/src/HtmlAgilityPack.Shared/HtmlNode.Encapsulator.cs#L180

Side note: There is a related issue that also warrants fixing when the proper NodeReturnType support is being implemented. Currently, when a property of a simple type like string has a [XPath] attribute with an invalid NodeReturnType value, a bare-bones and non-descript System.Exception is being thrown:
https://github.com/zzzprojects/html-agility-pack/blob/c12580b2025144d618d3397dec1fd81132e3f822/src/HtmlAgilityPack.Shared/HtmlNode.Encapsulator.cs#L629
This should to be changed into a meaningful exception with a message that informs about the concrete cause of the exception.

@elgonzo I created a PT on your advice, please help me review it.

Hello @rwecho ,
We will close this issue has your PR has been merged and now available in the v1.11.50
Best Regards,
Jon


Roll Flutter Engine from db3e5af2ca22 to 33de14d6c31b (1 revision)

https://github.com/flutter/engine/compare/db3e5af2ca22...33de14d6c31b
2024-11-13<EMAIL_ADDRESS>Roll Dart SDK from c7d140d18895 to e5c2c502c890 (1 revision) (flutter/engine#56555)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Docs missing what "warehouse" is or should be in the future

I looked at this page:
https://warehouse.readthedocs.org/en/latest/
I am missing what warehouse is or should be in the future.

What sort of thing are you looking for there? Warehouse is "PyPI 2.0", I'm not sure how best to describe it.

Here's a stab at describing it.
Warehouse is a new code base that implements a Python package index. It is being actively developed and the plan is that it will eventually power http://pypi.python.org (PyPI) and replace an older code base that is currently powering PyPI. You can see Warehouse in production at xxx.
Warehouse is built on top of the Pyramid web application framework and uses PostgreSQL, Elasticsearch, etc.
The goal is to improve PyPI by making it:

be more user-friendly
have a more modern look
more features
remove legacy APIs
have more maintainable code with test coverage, docs, etc.

Thank you very much.


Packages with "@" not upgrading correctly

Please follow the general troubleshooting steps first:

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?

You can erase any parts of this template not applicable to your Issue.
Bug reports:
Packages with "@" in them (or at a very minimum<EMAIL_ADDRESS>does not appear to be upgrading correctly:
~/p/h/letsencrypt-aws (master) $ brew upgrade
Checking out v1.0.1 in /usr/local/Homebrew...
To checkout v1.0.1 in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout v1.0.1
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
<EMAIL_ADDRESS>✔

~/p/h/letsencrypt-aws (master) $ brew upgrade
Checking out v1.0.1 in /usr/local/Homebrew...
To checkout v1.0.1 in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout v1.0.1

This has left me with an out-of-date<EMAIL_ADDRESS>Attempting to explicitly upgrade it does not work:
~/p/h/letsencrypt-aws (master) $ brew upgrade<EMAIL_ADDRESS>Checking out v1.0.1 in /usr/local/Homebrew...
To checkout v1.0.1 in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout v1.0.1
Error<EMAIL_ADDRESS>1.1.0 already installed

I can confirm the issue exists on my machine as well:
Checking out v1.0.1 in /usr/local/Homebrew...
To checkout v1.0.1 in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout v1.0.1
Error<EMAIL_ADDRESS>1.1.0 already installed

And here:
cory@heimdall:requests-oauthlib/ % brew upgrade<EMAIL_ADDRESS>Error<EMAIL_ADDRESS>1.1.0 already installed

This isn't the fault of the @. See https://github.com/Homebrew/homebrew-core/pull/5117.

lol, welp. thanks
On Thu, Sep 22, 2016 at 12:04 PM, Dominyk Tiller<EMAIL_ADDRESS>wrote:

This isn't the fault of the @. See Homebrew/homebrew-core#5117
https://github.com/Homebrew/homebrew-core/pull/5117.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Homebrew/brew/issues/1083#issuecomment-248948391, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAADBGftwf_LkWEDiAF86Ag42DWtJfCHks5qsqcTgaJpZM4KD8oX
.

--
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6

Fixed in 1e9537f. Folks:
brew update
brew upgrade<EMAIL_ADDRESS>


Add support for session-close

The transmission RPC interface offers the session-close method to shut down Transmission remotely.
It would be nice if the library could make this command available.

you can send a PR.


Add to Bezhanov\Faker\Provider\Commerce a ProductDescription

Hello,
First thanks for this library.
Is it possible to add a ProductDescription to Bezhanov\Faker\Provider\Commerce ?
Thank you by advance.

Hello @HamzaDevz,
What kind of content would you like the ProductDescription generator to create? I usually use https://github.com/fzaninotto/Faker#fakerproviderlorem for generating description.

I am closing the issue due to lack of activity.


Showing differences between schedules

Fixes #30

Coverage remained the same at 100.0% when pulling 5b5fb025095b2bca9704cef8f9cc57e957992b5c on issue-30 into 40b7c829330765540c5d8c61a530434e537fb77b on master.

Coverage remained the same at 100.0% when pulling 852c69b4aed62e26bfa362ad9885f37db69d06ba on issue-30 into 40b7c829330765540c5d8c61a530434e537fb77b on master.

Coverage remained the same at 100.0% when pulling 852c69b4aed62e26bfa362ad9885f37db69d06ba on issue-30 into 40b7c829330765540c5d8c61a530434e537fb77b on master.

Leave this for now. I'm mucking about with the docs

Coverage remained the same at 100.0% when pulling 4ea36197bbc32ab8c2bb2e9407451ef702c73da0 on issue-30 into 40b7c829330765540c5d8c61a530434e537fb77b on master.

Coverage remained the same at 100.0% when pulling 2b326ea0ec6dd484e119fb4f8400011ec726f457 on issue-30 into 40b7c829330765540c5d8c61a530434e537fb77b on master.


Have you tried more views?

I mean if you use 3 or 4 views in epipolar sample, like fuse features one more time by the 3rd view,  you may get better results I guess.
I'm appreciated if you reply.

Did you experiment according to the script you said?


calculate speed of a vehicle from given distance and time in the general maths section.

ok @jugeshraghav assigning to you
dead line 17 june

Thank you @arpit456jain

Do provide steps for the same, if you can. We are using LaTex text for showing steps, We have sent a link of documentation of Katex support table in our Slack Channel

Sure I will do that.
On Mon, Jun 14, 2021, 00:18 Rajinderpal Singh @.***>
wrote:

Do provide steps for the same, if you can. We are using LaTex text for
showing steps, We have sent a link of documentation of Katex support table
in our Slack Channel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5254#issuecomment-860254092,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVI6WJGZPKED6SIRJGMWOTTST4QZANCNFSM46T5WXFQ
.

@jugeshraghav any updates ?

I will give updates till tommorow morning actually I have semester exams.
On Mon, Jun 21, 2021, 11:22 111arpit1 @.***> wrote:

@jugeshraghav https://github.com/jugeshraghav any updates ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5254#issuecomment-864747926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVI6WLKRN2UEOJOK5DTNILTT3HTHANCNFSM46T5WXFQ
.

ok @jugeshraghav

Thank you so much
On Mon, Jun 21, 2021, 11:28 111arpit1 @.***> wrote:

ok @jugeshraghav https://github.com/jugeshraghav
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5254#issuecomment-864749959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVI6WIEDS6VFKFCYGIIVNDTT3IHTANCNFSM46T5WXFQ
.

@arpit456jain I need a help , the calculator is to be placed in the calculator section or there is any other section for general maths.

@jugeshraghav You need to place .html file into the Calculators folder

okay how to i write css and js code for it . I looked in several files there is only html code written for them and what do i do to write logics.

we are planning to release it as a library also, so place logic for functions in
library/logicjavascript.js file
and for css just add class to the fields, for test purpose you can call
loadcalculator ('filename') on window load
for calling the function which you defined in logicjavascript.js file use script tag in file you will create in Calculators folder.
for more clarity see magicNumber.html file and logic for it in logicjavascript.js file

okay, thank you so much @sairish2001

what is the final label of this issue . I am confused.

level 2 @jugeshraghav  you can check it on right side on top

Thanks, I'll check it out.
On Wed, Jun 23, 2021, 12:07 111arpit1 @.***> wrote:

level 2 @jugeshraghav https://github.com/jugeshraghav you can check it
on right side on top
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5254#issuecomment-866570472,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVI6WOUKPAGDLP3GXOOUHDTUF6JVANCNFSM46T5WXFQ
.


VSTi host?

Hi there,
Here's more a question than issue report.
I'm interested in having VSTi acting as host (or "chainer" as people tend to call it).
Is DPF having such capabilities implemented already or do I have to add them in on top of a standard boilerplate code?
Cheers
Martin

DPF does not have such a thing, but I have plans to add to my carla plugin host a sorta "plugin-wrapper api" that allows anyone to load any kind of plugin by reusing carla's internals.

Oh, I see.
I remember referencing Carla for a C++ VST wrapper I made ages ago I made for the Cinder framework. Much water passed under the bridge since then, huh.
Anyways, I'll give it a go anyways.
Cheers for a quick response

I was thinking of turning this point into a discussion, but I am just going to close it.
It is not within the scope of DPF to allow hosting of other plugins.
It would be straight forward to do a mini-host based on carla and dpf though, if anyone is willing to work on the UI side for it.
But that would be something that is not this ticket.


Audit templates - what does not work with JavaScript disabled?

Following an email from a user who prefers to browse the web with JS off - can we please audit the codebase to find those places where the user cannot acheive their goals?
The user mentioned checksums in particular.

This is due to the client-side include failing (which requires Javascript).
It should be possible to add some "default" HTML for the logged-out user which would be replaced if the CSI is successful here: https://github.com/pypa/warehouse/blob/master/warehouse/templates/base.html#L184-L185
Probably worth mentioning that this same HTML is currently inside the include as well, so this shouldn't be duplicated twice and instead should become a macro probably: https://github.com/pypa/warehouse/blob/master/warehouse/templates/includes/current-user-indicator.html#L77-L82

Another thing to audit here is the click-to-copy feature for file hashes on the "Files" page, I suspect it doesn't work at all without JS enabled.