text:
Add Segment Analytics to Showcase

Acceptance criteria
We want to see the activity on the showcase website, how many users, recurring users, more traffic after a demo, etc.

Let's determine what metrics we want to capture, then determine what tool to use.

following @christophe-f ideas, I am starting to list some ideas on metrics
MoSCoW List
Must

Number of Users/Visitors (identify times of more or less traffic, e.g., after demo, summit)
1.1. Number of Recurring Users/Visitors
Number of Sessions
2.1. duration of a session (interest and usability of the showcase)
2.2. pages during a session (finding funnels, often used pages, may not be possible within the Backstage framework?)

Should

Bounce rate (user only visiting one page could indicate technical, UI, or usability problems)
Conversions/Funnels (if we have paths that a user should follow/ we expect a user to follow? here this can be measured)

Could

Average time on page (depending on the page and its content; could identify too long or uneasy to read pages)

Won't
The above mentioned Must and Should could be archived with google analytics out of the box.

do we need more or others, please add and correct
is google analytics an option at all

authors: christophe-f schwesig serenamarie125

repo: janus-idp/backstage-showcase


text:
chore(backstage): update backstage to 1.18.x

Description
Please explain the changes you made here.
Which issue(s) does this PR fix

Fixes https://github.com/janus-idp/backstage-showcase/issues/551

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

Added to new story to complete the upgrade. #593

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
chore(changesets): remove changesets

Description
We should remove the changesets from the showcase because we have not updated the changelogs since dev preview.
Which issue(s) does this PR fix

Fixes https://issues.redhat.com/browse/RHIDP-1129

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

Not to be too pedantic, but you're not removing the changesets...
they're still in https://github.com/janus-idp/backstage-showcase/tree/main/.changeset
you're just no longer checking PRs for new ones, and removing the yarn commands to add new ones.
FWIW this may be a different path to what's suggested for migrated plugins from backstage-plugins -> community-plugins as that team likes changesets (but we might convince them to do releases on every commit using semantic release instead or in addition to changeset-grouped releases).

Wouldn't it be better if we start using this properly instead of removing it? Last release we had a hard time coming up with the changelog, if we start using changesets properly it will make releases easier.

Wouldn't it be better if we start using this properly instead of removing it? Last release we had a hard time coming up with the changelog, if we start using changesets properly it will make releases easier.

we discussed that and come to the conclusion that we will remove changes fro now

authors: kadel nickboldt schultzp2020


text:
remove white space between images in the printPic method ??

@LeanPerez21  can you please share you code i am stuck I got blank when I print image

same issue please help

android/src/main/java/cn/jystudio/bluetooth/escpos/RNBluetoothEscposPrinterModule.java

android/src/main/java/cn/jystudio/bluetooth/escpos/RNBluetoothEscposPrinterModule.java
@ReactMethod
public void printPic(String base64encodeStr, @Nullable  ReadableMap options) {
int width = 0;
int leftPadding = 0;
if(options!=null){
width = options.hasKey("width") ? options.getInt("width") : 0;
leftPadding = options.hasKey("left")?options.getInt("left") : 0;
}
    //cannot larger then devicesWith;
    if(width > deviceWidth || width == 0){
        width = deviceWidth;
    }

    byte[] bytes = Base64.decode(base64encodeStr, Base64.DEFAULT);
    Bitmap mBitmap = BitmapFactory.decodeByteArray(bytes, 0, bytes.length);
    int nMode = 0;
    if (mBitmap != null) {
        /**
         * Parameters:
         * mBitmap  要打印的图片
         * nWidth   打印宽度（58和80）
         * nMode    打印模式
         * Returns: byte[]
         */
        byte[] data = PrintPicture.POS_PrintBMP(mBitmap, width, nMode, leftPadding);
        //  SendDataByte(buffer);
        sendDataByte(Command.ESC_Init);
        sendDataByte(Command.LF);
        sendDataByte(data);
        remove this line // sendDataByte(PrinterCommand.POS_Set_PrtAndFeedPaper(30));
        remove this line // sendDataByte(PrinterCommand.POS_Set_Cut(1));
        remove this line // sendDataByte(PrinterCommand.POS_Set_PrtInit());
    }
}

source: gharchive/issue

authors: LeanPerez21 elemanjan feras-merwas zhietan

license: MIT


text:
Install clang on the windows environments

I was trying to use cross for compiling to the x86_64-pc-windows-gnu target, however because one of my crates runs bindgen as part of a build.rs script, it fails.
$ cross build --target x86_64-pc-windows-gnu
...
error: failed to run custom build command for `litecad-sys v0.1.0 (file:///project/litecad-sys)`
process didn't exit successfully: `/target/debug/build/litecad-sys-a9c3850875a197e1/build-script-build` (exit code: 101)
--- stdout
rerun-if-changed=wrapper.h
rerun-if-changed=LiteCAD.h

--- stderr
thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any of [\'libclang.so\', \'libclang.so.*\', \'libclang-*.so\'], set the LIBCLANG_PATH environment variable to a path where one of these files can be found (skipped: [])"', libcore/result.rs:916:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Would it be a good idea for the underlying docker image windows builds run on to have clang installed?

@Michael-F-Bryan please feel free to make a PR against https://github.com/japaric/cross/blob/master/docker/x86_64-pc-windows-gnu/Dockerfile

authors: Michael-F-Bryan jamesmunns

repo: japaric/cross


text:
Parse  elements

In looking at https://github.com/japaric/svd2rust/issues/191 and https://github.com/japaric/svd2rust/issues/16 I thought that this might help, so here's the trivial patch.

https://github.com/japaric/svd/pull/51 for rustfmt, I'll amend this one independently from that for now

(force pushed with your suggested changes; you'll probably need to hard refresh the PR page)

Thank you!
bors r+

authors: Emilgardis wez

repo: japaric/svd


text:
Rust Based Regression Tester

In order to make running CI tests easier (and faster), I'd like to show you a bit of a hacky PoC I am working on.
This would replace the Bash based CI scripts with a small Rust program. This is largely to take advantage of rayon, since compilation of crates during CI is generally single-CPU bound when compiling a single large lib.rs generated by svd2rust.
This is not ready to merge, but I am mostly looking for feedback from @japaric and @Emilgardis whether this is something you would consider merging.

Seems good to me, in principle.
Replacing the bash script with a Rust program also makes it easier to run the test suite on Windows.

This is largely to take advantage of rayon, since compilation of crates during CI is generally single-CPU bound when compiling a single large lib.rs generated by svd2rust.

The Travis builders have 1 VCPU, though, so this would only make local builds faster.
I think while doing this we could also move from testing a whole vendor in a single CI build to more evenly split all the devices across several CI builds.
I'd like to hear what others think.

re: travis and 1VCPU, I am hoping to later offer my GitLab CI builders, which have 16 VCPUs, so once that is implemented, it should help with those builds. Either way, it definitely could help with local builds, where it is typical to have 2-8+ threads available.
I am really open to other possible options for CI options, including specifying specific targets or vendors, maybe tagging targets (e.g. "these SVDs have clusters, and should be tested when anything regarding clusters is changed").

Seems good. Obviously there needs to be more done but the idea is better imo than having it scripted

I may also add one more commit that adds a per-test retry threshold to prevent spurious failures (at an individual crate level) from causing a whole-ci failure. I am open to thoughts on this :)

Also Also here is an example of a full regression test build using my CI servers: https://gitlab.onevariable.com/james/svd2rust/-/jobs/72

It seems that some of my spurious failures (mentioned above) are due to out of memory conditions, as some crates take upward of 3.2G of memory to compile (particularly the freescale chips).
I don't know how to work around this, other than document that the testing will require significant amounts of CPU and memory, and hope that people have swap[file] configured.

Hey all, I'd like to get this merged if possible. Is there anything additional needed before merging this? Should it be mentioned in the main README?

I think a small mention wouldn't hurt.

LGTM.

I think a small mention wouldn't hurt.

Yeah, it should be mention that svd2rust-regress can be used to run the test suite faster on a local machine.

@japaric @Emilgardis added a mention in the main README. Okay to merge?

authors: Emilgardis jamesmunns japaric


text:
package.json error

Hi. I'm trying to build an binary that has var xray = require('x-ray'); in the node script.
It is giving me some errors so in trying to do what the README tells me to.
I'm on point Browserify Require Issues but is giving me some errors. This is what I did:
I tried to create a package.json and then I executed nexe on the command line. It shows me this error:

module.js:590
throw err;
^
SyntaxError: C:\Users\danny\dev\MeusProgramas\horoscopo\package.json: Unexpected token : in JSON at position 6
at Object.parse (native)
at Object.Module._extensions..json (module.js:587:27)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.exports.package (C:\Users\danny\AppData\Roaming\npm\node_modules\nexe\lib\exe.js:962:16)
at Object. (C:\Users\danny\AppData\Roaming\npm\node_modules\nexe\bin\nexe:84:22)
at Module._compile (module.js:570:32)

This is my package.json:
"nexe": {
    "input": "horos.js",
    "output": "horos^$",
    "temp": "src",
    "browserify": {
        "requires": [],
        "excludes": [],
        "paths": []
    },
    "runtime": {
        "framework": "node",
        "version": "6.9.0",
        "js-flags": "--use_strict",
        "ignoreFlags": true
    }
}

What should I do?

By the error message it looks like you have a typo in your package.json

But I have copied the json from the README example as you can see

if that's the whole contents of your package.json you need to add braces around it. e.g.:
{
"nexe": {
...
}
}

Of course. I'm really a beginner :)
Obrigado @anmonteiro

It can be made more explicit in the README for beginners like me to don't fall under this issue

Now I'm trying add x-ray module, and I'm trying to do what is in  Browserify Require Issues.
Should my package.json be like this?
{
    "nexe": {
        "input": "horos.js",
        "output": "horos^$",
        "temp": "src",
        "browserify": {
            "requires": [
                {
                    "file": "horos.js",
                    "expose": "x-ray"
                },
                "x-ray.js"
            ],
            "excludes": [],
            "paths": []
        },
        "runtime": {
            "framework": "node",
            "version": "latest",
            "js-flags": "--use_strict",
            "ignoreFlags": true
        }
    }
}

repo: jaredallard/nexe

license: mit

license_source: bigquery


text:
No more search functionality

Continuation from https://github.com/jarrodek/ChromeRestClient/issues/510#issuecomment-211823979
I can only see a search option in history and cmd+f does not open up the default chrome search

Hi,
Thanks for issue report.
Chrome apps do not have Chrome's search bar.
It is working in request screen so you can search for a string in the response.
I'm not sure if you refer to any other search functionality in the app.

hmm not seeing it, where should that search be?

As in previous version it is working under ctrl/command + F shortcut. Is it what you mean?

Ok this is what I see after a request and pressing command + f
http://puu.sh/ow9k8/22844250b8.png

@AdriVanHoudt is it working now? There was several fixes in this matter.

@jarrodek this seems fixed now thanks!

authors: AdriVanHoudt jarrodek

repo: jarrodek/ChromeRestClient


text:
FIX: Растягивание изображения во flexbox в Safari

На iOS в Safari картинки растягивались. Данный PR фиксит это
Было / Стало

#142


text:
Should stopListening call off aswell?

Just discovers, that stopListening actually clears only child listeners.
If view listens some other objects (ie models/collections), it would be cleared.
But if i have some custom controller, that listens view, that listener would not be cleaned. Is it intended behaviour?
function FooController(options) {
  this.init(options);
}

FooController.prototype.init = function(options) {
  this.listenTo(options.view, 'foo', 'do some stuff');
};

Object.assign(FooController.prototype, Backbone.Events);

var view = new Backbone.View();
var ctrl = new FooController({view: view});

view.remove(); // At this point `ctrl` still have references to `view`

https://jsfiddle.net/ogonkov/08k3mecr/1/
I should somehow call FooController#stopListening manually, when view get destroyed?
I was sure that one of the advantages of using listenTo is automatic cleaning up of all listeners from object, when it gets removed. o_O

What's this in your controller? listenTo and stopListening are only called "automatically" for views because of their lifecycle. listenTo itself does not know when it should stop listening again, the view explicitly calls stopListening when it is destroyed. Your controller does no such thing

I have updated my example, to make it more clear.
The question is: why removed object didn't clean it listeners in parent object? I thought that it should work this way, but it's clean only listeners to objects, that it listen to.

view.remove only removes event listeners that the view itself made (through view.listenTo), not the event listeners other objects made on that view. If you want to remove the event listeners that are attached to the controller, you need to call ctrl.stopListening() before view.remove().

You are mixing up the .on and .listenTo methods. Use .on if the Listening object outlives the triggering object. Use .listenTo if the triggering object outlives the listening object. If you follow this rule, event bindings will be automatically cleaned up in all cases.

authors: jaapz jgonggrijp ogonkov

repo: jashkenas/backbone


text:
Allow nowait for status(), and split message parsing into separate function

I have a single-threaded application where I handle the socket reading (via select.select() and buffering the data) and needed status() to not block.  Once I get a message I then need to parse it, so I moved the parsing part of _send_receive() into its own function to make it easier to call.

Logical. I can't think of any dependency issue for this change so I will rev the version as a minor patch, v1.9.2.

authors: jasonacox uzlonewolf

repo: jasonacox/tinytuya


text:
Upgrading ink to version 0.11.0 breaks proto-repl

Probably the root cause of Issues #326 and #325
After upgrading I've got an error Uncaught TypeError: Cannot read property 'info' of undefined when trying to start proto-repl. Downgrading ink to v0.10.12 using apm (apm install ink@0.10.12) solves the issue.

Same here.

Note, anyone who installed Atom with proto-repl gets confused and must investigate quite a lot of time

Downgrading Ink at least makes the REPL work, but it doesn't autocomplete (Parinfer doesn't work either).
For some reason autocomplete/Parinfer only work in the text-based REPL.

authors: danielpyon haraldpusch mdzaebel mzuther

repo: jasongilman/proto-repl


text:
How to convert a NameExpr to Type?

I want to feed a NameExpr into convertToUsage(), but there is no getType() in nameExpr, what can I do?

Hi! Can you move this to https://github.com/javaparser/javaparser ? The projects have been integrated.

@matozoid sure but actually I've solved this problem, so should I just close this issue?

Sure, go ahead!

repo: javaparser/javasymbolsolver


text:
Allow imports from a given nested folder

Hello,
Is it possible to write such a rule?

Feature cannot import files from other features unless they are in the features/shared folder.

I tried this configuration but unfortunately it doesn't work.
 "settings": {
        "boundaries/elements": [
            {
                "type": "features",
                "pattern": "features/*",
                "mode": "folder"
            },
            {
                "type": "featuresShared",
                "pattern": "features/shared/*",
                "mode": "folder"
            }
        ],
        "import/resolver": {
            "typescript": {
                "alwaysTryTypes": true
            }
        }
    },
    "rules": {
        "boundaries/element-types": [
            2,
            {
                "default": "disallow",
                "rules": [
                    {
                        "from": "features",
                        "allow": [
                            "featuresShared"
                        ]
                    }
                ]
            }
        ],
    }

.
├── ...
└── 📂 src
    └── 📂 features
        ├── 📂 shared
        ├── 📂 Feature1
        └── 📂 Feature2

Hi @Igorkowalski94 , could you please provide more details? You can enable the debug mode in order to see which element type the plugin is assigning to each file by using the ESLINT_PLUGIN_BOUNDARIES_DEBUG environment variable.
ESLINT_PLUGIN_BOUNDARIES_DEBUG=1 npm run lint

I have the following structure:
.
├── ...
└── 📂 src
    ├── ...
    └── 📂 features
        ├── ...
        ├── 📂 Feature1
        │   ├── 📄 Feature1.tsx
        │   ├── 📄 feature1.types.ts
        │   ├── 📂 helpers             // Helpers only for Feature1 folder
        │   └── 📂 components          // Components only for Feature1 folder
        │        ├── ...
        │        ├── 📂 Child1         // Same structure as Child2
        │        └── 📂 Child2
        │            ├── 📄 Child2.tsx
        │            ├── 📄 child2.types.ts
        │            ├── 📂 helpers           // Helpers only for Child2 folder
        │            └── 📂 components       // Components only for Child2 folder
        │
        └── 📂 Feature2 // Same structure as Feature1

I would like to achieve the following rules:

The Feature1 can import Feature2.tsx and feature2.types.tsx but cannot import their components and helpers.
The Feature2 can import Feature1.tsx and feature1.types.tsx but cannot import their components and helpers.
Feature1.tsx can import Child1.tsx and Child2.tsx but cannot import their components and helpers.
Child1 folder can import Child2.tsx and  child2.types.ts but cannot import  Child2  components and helpers.
Child2 folder can import Child1.tsx and  child1.types.ts but cannot import  Child1  components and helpers.
The entire components and helpers folder can import feature1.types.ts

Yes, it is possible, but you should try to debug your configuration in order to know if your elements are being categorized properly. I suspect that maybe all of them are being categorized as features because they match first the features pattern, but I'm not sure. Could you please provide logs?

@Igorkowalski94 were you able to resolve this? I am having a similar issue.

@rishitank Yes, I created my own solution eslint-plugin-project-structure. I'm closing the issue.

authors: Igorkowalski94 javierbrea rishitank

repo: javierbrea/eslint-plugin-boundaries


text:
🛑 Ofelia Nieto, 57 is down

In 5c1063c, Ofelia Nieto, 57 (http://159.65.204.200:7022/) was down:

HTTP code: 502
Response time: 18514 ms

Resolved: Ofelia Nieto, 57 is back up in 898e956 after 13 minutes.

repo: javisu/monitor


text:
🛑 Valderrebollo, 30 is down

In 472d296, Valderrebollo, 30 (http://159.65.204.200:7050/) was down:

HTTP code: 502
Response time: 18713 ms

Resolved: Valderrebollo, 30 is back up in a2207e4.


text:
🛑 Norma, 357 is down

In d5ea1e5, Norma, 357 (http://159.65.204.200:7044/) was down:

HTTP code: 502
Response time: 18814 ms

Resolved: Norma, 357 is back up in 79ca131.


text:
🛑 Rodriguez Marin, 88 is down

In 0113cfa, Rodriguez Marin, 88 (http://159.65.204.200:7057/) was down:

HTTP code: 502
Response time: 18645 ms

Resolved: Rodriguez Marin, 88 is back up in 39495c2.


text:
🛑 Norma, 357 is down

In a26c5dd, Norma, 357 (http://159.65.204.200:7044/) was down:

HTTP code: 502
Response time: 18653 ms

Resolved: Norma, 357 is back up in 1ee9c5a.


text:
All flags look like booleans in -h output

$ ./foocli -h

Usage: foocli [-n] [-f config_file]

Options:
  -n                  No-op mode.
  -f                  Path to the config file.
$

In this example, -n is a boolean but -f is not (it takes a string). It would be clearer if -f was rendered as -f string. One could also borrow the back quote idea from the flag package, see https://godoc.org/flag#PrintDefaults.

Alternative to back quotes would be also to add Metavar to the *Opt structs, acting similar as in Python's argparse.
Yet another alternative would be reusing names from Spec in this  -h output.
That would be actually super helpful, as mow.cli is already more advanced than most of cli parsers, this one area seems to ask for improvement.

@wkhere Thank you for your suggestions !
Could you clarify a bit the following points ?

argparse's metavar: just a string, e.g. bool  or true|false which when help is printed would render as:   -n (bool)                 No-op mode. ?
reusing names from Spec: not sure I understood this one

@jawher thank you for a swift reply!

Metavar is a concrete name representing flag value (or arg value). In argparse it is displayed in usage headline (well, we seem to have Spec for that) and in usage lines describing each option.
Following an example from the original doc:

>>> parser.add_argument('--foo', metavar='YYY')
>>> parser.add_argument('bar', metavar='XXX')
>>> parser.parse_args('X --foo Y'.split())
Namespace(bar='X', foo='Y')
>>> parser.print_help()
usage:  [-h] [--foo YYY] XXX

positional arguments:
 XXX

optional arguments:
 -h, --help  show this help message and exit
 --foo YYY

Hope this example explains.
Here, I think, we could define Metavar in Opt struct, defaulting to Opt type, and print it in usage text.
In Go world this has been a bit different, flag has the mechanism that if you use back quotes in option's description then it is also used like metavar above - see the doc

Several other projects incl. pflag/cobra copied that behaviour

By reusing names from Spec I meant,
if an option requires value and we're writing the Spec, then we must refer this value somehow, ie. -x=<foo>.

Then we could print this also in Options details instead of just -x + description.

I am sorry for somewhat chaotic style of writing, in a hurry a bit, hope this is little clearer.

authors: jawher masiulaniec wkhere


text:
GAM 6.12 - cryptography error on macOS arm64

The issue tracker is for reporting product deficiencies. "How do I?" questions should be posted to the discussion forum at https://groups.google.com/group/google-apps-manager. When in doubt, start at the discussion forum and return here only when instructed to do so.
Please confirm the following:
[x] I have upgraded to the latest GAM release from https://git.io/gamreleases and I still have this issue.
[x] I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/gam/wiki
Full steps to reproduce the issue:

Fresh install of, or upgrade to GAM 6.12 on Apple M1 computer (arm64) [running macOS 12.1] using recommended method
Try to create new project, or rotate service account keys using gam rotate sakey

Expected outcome (what are you trying to do?):
GAM executes command without error. Specifically, it succeeds in generating a new private key as part of the process.
Actual outcome (what errors or bad behavior do you see instead?):
Command fails with error:
Generating new private key...
Traceback (most recent call last):
  File "gam/__main__.py", line 50, in <module>
  File "gam/__main__.py", line 45, in main
  File "gam/__init__.py", line 11905, in ProcessGAMCommand
  File "gam/__init__.py", line 7945, in doCreateOrRotateServiceAccountKeys
  File "gam/__init__.py", line 7770, in _generatePrivateKeyAndPublicCert
  File "cryptography/hazmat/backends/__init__.py", line 14, in default_backend
  File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
  File "cryptography/hazmat/backends/openssl/__init__.py", line 6, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
  File "cryptography/hazmat/backends/openssl/backend.py", line 113, in <module>
  File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
  File "cryptography/hazmat/bindings/openssl/binding.py", line 14, in <module>
ImportError: dlopen(/var/folders/35/5hfq7vfx5_nbx34xrmz_9pyr0000gn/T/_MEIspB51F/cryptography/hazmat/bindings/_openssl.abi3.so, 0x0002): tried: '/var/folders/35/5hfq7vfx5_nbx34xrmz_9pyr0000gn/T/_MEIspB51F/cryptography/hazmat/bindings/_openssl.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_openssl.abi3.so' (no such file), '/usr/lib/_openssl.abi3.so' (no such file), '/private/var/folders/35/5hfq7vfx5_nbx34xrmz_9pyr0000gn/T/_MEIspB51F/cryptography/hazmat/bindings/_openssl.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_openssl.abi3.so' (no such file), '/usr/lib/_openssl.abi3.so' (no such file)
[23869] Failed to execute script '__main__' due to unhandled exception!

Workaround:
GAM 6.11 still works fine, and downgrading to v6.11 using bash <(curl -s -S -L https://git.io/install-gam) -l -v 6.11 works as a temporary workaround.
I'm assuming this bug is something to do with the change 'ARM and ARM64 binaries reintroduced.' in v6.12.
Thanks Jay, Ross & co for your great work!

Just wanted to confirm this bug is happening to me as well.
Thank you all for your hard work.

I'm seeing this on Apple silicon. The install runs fine on an older Intel Mac. (Both systems are running macOS 12.1)

The biggest challenge in troubleshooting this one is I don't have an Apple M1 device to reproduce this with and can't really justify the expense right now. If anyone cares though I'm happy to setup some sort of go fund me or I can take PayPal and Venmo.

Jay, A go fund me might not be a bad idea. The M1 MBA is very high value. Fully loaded with AppleCare getting 100 people to donate $20 each would cover it. Easier said than done I suppose.
I did get GAM going on on older intel system I have. Thanks for all of your work on this. - pew

@jay0lee, I and no doubt many others would be glad to chip in to an M1 fund if you feel it's important for the ongoing development of GAM for Mac. An M1 Mac mini could be another economical route to having an M1 system for testing.
In the meantime, I can offer to set you up an SSH connection to a blank-install network-isolated M1 Mac for a block of hours in the next week or two for debugging purposes, if you'd like. Let me know if interested and I can email you to arrange it, if not no worries.

Can someone with an M1 test the build below and see if it has the same issues
gam-macos-m1-fixed-take1.zip
?

The executable fails, running from source works.
./gam rotate sakey
Generating new private key...
Traceback (most recent call last):
File "gam/main.py", line 50, in
File "gam/main.py", line 45, in main
File "gam/init.py", line 11907, in ProcessGAMCommand
File "gam/init.py", line 7945, in doCreateOrRotateServiceAccountKeys
File "gam/init.py", line 7770, in _generatePrivateKeyAndPublicCert
File "cryptography/hazmat/backends/init.py", line 14, in default_backend
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/hazmat/backends/openssl/init.py", line 6, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/hazmat/backends/openssl/backend.py", line 113, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/hazmat/bindings/openssl/binding.py", line 14, in
ImportError: dlopen(/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEI1YyxtW/cryptography/hazmat/bindings/_openssl.abi3.so, 0x0002): tried: '/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEI1YyxtW/cryptography/hazmat/bindings/_openssl.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_openssl.abi3.so' (no such file), '/usr/lib/_openssl.abi3.so' (no such file), '/private/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEI1YyxtW/cryptography/hazmat/bindings/_openssl.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_openssl.abi3.so' (no such file), '/usr/lib/_openssl.abi3.so' (no such file)
[93655] Failed to execute script 'main' due to unhandled exception!

What does
gam version extended
Show for these devices?
Jay
On Mon, Jan 10, 2022, 5:59 PM Ross Scroggs @.***> wrote:

The executable fails, running from source works.
./gam rotate sakey
Generating new private key...
Traceback (most recent call last):
File "gam/main.py", line 50, in
File "gam/main.py", line 45, in main
File "gam/init.py", line 11907, in ProcessGAMCommand
File "gam/init.py", line 7945, in doCreateOrRotateServiceAccountKeys
File "gam/init.py", line 7770, in _generatePrivateKeyAndPublicCert
File "cryptography/hazmat/backends/init.py", line 14, in default_backend
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/hazmat/backends/openssl/init.py", line 6, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/hazmat/backends/openssl/backend.py", line 113, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/hazmat/bindings/openssl/binding.py", line 14, in
ImportError:
dlopen(/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/MEI1YyxtW/cryptography/hazmat/bindings/
openssl.abi3.so, 0x0002): tried:
'/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/MEI1YyxtW/cryptography/hazmat/bindings/
openssl.abi3.so' (mach-o file, but is an incompatible architecture (have
'x86_64', need 'arm64e')), '/usr/local/lib/_openssl.abi3.so' (no such
file), '/usr/lib/_openssl.abi3.so' (no such file),
'/private/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/MEI1YyxtW/cryptography/hazmat/bindings/
openssl.abi3.so' (mach-o file, but is an incompatible architecture (have
'x86_64', need 'arm64e')), '/usr/local/lib/_openssl.abi3.so' (no such
file), '/usr/lib/_openssl.abi3.so' (no such file)
[93655] Failed to execute script 'main' due to unhandled exception!
—
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/1465#issuecomment-1009428751, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDIZMHCEH7PQ6NCNOAHY33UVNQD3ANCNFSM5LK3LRYQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

$ ./gam.py version extended
GAM 6.12 - https://git.io/gam - pythonsource
Jay Lee jay0lee@gmail.com
Python 3.10.1 64-bit final
google-api-python-client 2.33.0
MacOS Monterey 12.0.1 arm64
Path: /Users/ross/Downloads/GAM-main/src
Your system time differs from admin.googleapis.com by less than 1 second
OpenSSL 1.1.1l  24 Aug 2021
cryptography 36.0.0
filelock 3.4.0
google-auth-httplib2 0.1.0
google-auth-oauthlib 0.4.6
google-auth 2.3.3
httplib2 0.20.2
passlib 1.7.4
python-dateutil 2.8.2
admin.googleapis.com (142.251.32.234) connects using TLSv1.3 TLS_AES_256_GCM_SHA384

That's sort of surprising, at one point it was always showing x86_64 even
on M1s. So it looks like PyInstaller and python are running as arm64 but
cryptography module included is x86_64 only. Hmmm....
Jay
On Mon, Jan 10, 2022, 6:13 PM Ross Scroggs @.***> wrote:

$ ./gam.py version extended
GAM 6.12 - https://git.io/gam - pythonsource
Jay Lee @.***
Python 3.10.1 64-bit final
google-api-python-client 2.33.0
MacOS Monterey 12.0.1 arm64
Path: /Users/ross/Downloads/GAM-main/src
Your system time differs from admin.googleapis.com by less than 1 second
OpenSSL 1.1.1l 24 Aug 2021
cryptography 36.0.0
filelock 3.4.0
google-auth-httplib2 0.1.0
google-auth-oauthlib 0.4.6
google-auth 2.3.3
httplib2 0.20.2
passlib 1.7.4
python-dateutil 2.8.2
admin.googleapis.com (142.251.32.234) connects using TLSv1.3
TLS_AES_256_GCM_SHA384
—
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/1465#issuecomment-1009437944, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDIZMGZKKQYMH3X6DV3IJDUVNRZZANCNFSM5LK3LRYQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

OK, another day another build. Can someone test this one on a M1 and report back here?
gam-mac-m1-fix-take2.zip

$ ./gam version
Traceback (most recent call last):
File "gam/main.py", line 29, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "gam/init.py", line 47, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/x509/init.py", line 6, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/x509/certificate_transparency.py", line 10, in
ImportError: dlopen(/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEIU9WfVr/cryptography/hazmat/bindings/_rust.abi3.so, 0x0002): tried: '/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEIU9WfVr/cryptography/hazmat/bindings/_rust.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_rust.abi3.so' (no such file), '/usr/lib/_rust.abi3.so' (no such file), '/private/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEIU9WfVr/cryptography/hazmat/bindings/_rust.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_rust.abi3.so' (no such file), '/usr/lib/_rust.abi3.so' (no such file)
[4130] Failed to execute script 'main' due to unhandled exception!

Once more for the day. Can someone test the below and let me know?
gam-m1-fix-3s-a-charm.zip

3s-a-charm
$ ./gam version check
Traceback (most recent call last):
File "gam/main.py", line 28, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "gam/init.py", line 47, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/x509/init.py", line 6, in
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "cryptography/x509/certificate_transparency.py", line 10, in
ImportError: dlopen(/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEI0QUiju/cryptography/hazmat/bindings/_rust.abi3.so, 0x0002): tried: '/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEI0QUiju/cryptography/hazmat/bindings/_rust.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_rust.abi3.so' (no such file), '/usr/lib/_rust.abi3.so' (no such file), '/private/var/folders/n4/gdj8f3dj2mqckqxdnvxq9q480000gp/T/_MEI0QUiju/cryptography/hazmat/bindings/_rust.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_rust.abi3.so' (no such file), '/usr/lib/_rust.abi3.so' (no such file)
[4986] Failed to execute script 'main' due to unhandled exception!

OK, I've turned off universal2 for now and GAM on MacOS M1 should just use x86_64 emulation. GAM 6.13 is out with this fix.

I've verified, thanks
Ross
@.***

On Jan 12, 2022, at 9:38 AM, Jay Lee @.***> wrote:
OK, I've turned off universal2 for now and GAM on MacOS M1 should just use x86_64 emulation. GAM 6.13 is out with this fix.
—
Reply to this email directly, view it on GitHub https://github.com/jay0lee/GAM/issues/1465#issuecomment-1011293320, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL3ILRK3ILUBW2HVBO3UVW4C7ANCNFSM5LK3LRYQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.


text:
Not refreshing when URL changes

I have a CacheableImage component in my view. When the URL changes (via a redux reducer), the image is not getting updated. I've confirmed that the view itself is getting re-rendered with the new URL. If I replace CacheableImage with Image, it works as expected.
I checked the code and see that you are handling the source change via componentWillReceiveProps so I'm confused as to why it's not working. Any thoughts or suggestions?

Does your image is rendered inside a ListView ? If yes, see this issue https://github.com/facebook/react-native/issues/1417

@ryanhomer I experienced the same issue and after adding a key prop with the image URI it worked.

@Crash-- @eneskaya Thanks for the responses. I ended up using react-native-cached-image instead which fixed the issue for me but I was not using the key property so, good to know.

The solution of the key worked for me

authors: Crash-- eneskaya mekoahdd ryanhomer

repo: jayesbe/react-native-cacheable-image


text:
Visual Studio functions not created

The Visual Studio Functions (vs, vsadmin, and Install-VSExtension) are not registered when running PoSh. If you run the functions file a second time, they will be created.

Fixed in 2f95f1865ddda8f50109c24aeafec513abf8bcf4

repo: jayharris/dotfiles-windows


text:
Fix spaces, change let to const

(only use let if the variable will be reassigned)

@jayhyllie approve pliz!

repo: jayhyllie/hr-cheatsheet


text:
@FanhuaandLuomu 输入为拼音的声母、韵母序列； 之前由于担心插入blank，会使输入序列变成2倍长度，导致工程实现中耗时变长，从而影响首包延时以及RTF。现在补上blank，没有出现发音问题了，加上blank后首包延迟为100ms，整体rtf为0.03的样子，还好。

          >  > @FanhuaandLuomu 输入为拼音的声母、韵母序列； 之前由于担心插入blank，会使输入序列变成2倍长度，导致工程实现中耗时变长，从而影响首包延时以及RTF。现在补上blank，没有出现发音问题了，加上blank后首包延迟为100ms，整体rtf为0.03的样子，还好。

@hermanseu 是的，我之前也是加了blank 改善了吞音现象。你是用gpu 推理的吗？还是改成了流式

@FanhuaandLuomu

其实还是没搞明白吞音的根本原因在哪里。有检查过预测的隐变量的均值方差，均值特别小，方差看着有点大；只用均值作为隐变量的话，依然会有吞音的问题，想着是不是loss控制的不好导致均值学的有点偏，后面忙其他的事情就没继续做实验了。有思路的话，能否分享下~~
我这有逻辑会把训练得到的模型dump成二进制，然后c/c++读取二进制模型，在cpu上推理，流式输出。

Originally posted by @hermanseu in https://github.com/jaywalnut310/vits/issues/2#issuecomment-1396587418

@15755841658 解决了吞音问题，https://github.com/PlayVoice/vits_chinese

是训练时候没加blank，训练好的模型会有吞音问题吗

是不是拼音序列中空格已经编码过的话，就不用加blank了？

是不是拼音序列中空格已经编码过的话，就不用加blank了？

要的吧，训练的时候默认输入音素序列每个元素后面插入个0

我刚开始跑，现在的版本没有插入Blanks，现在训练15Ksteps了，听者效果还行。没有啥变音乱调的。

我的当前版本不是生韵律编码，是单字符编码的。

是不是拼音序列中空格已经编码过的话，就不用加blank了？

要的吧，训练的时候默认输入音素序列每个元素后面插入个0

我刚开始跑，现在的版本没有插入Blanks，现在训练15Ksteps了，听者效果还行。没有啥变音乱调的。

那没事了

是不是拼音序列中空格已经编码过的话，就不用加blank了？

要的吧，训练的时候默认输入音素序列每个元素后面插入个0

我刚开始跑，现在的版本没有插入Blanks，现在训练15Ksteps了，听者效果还行。没有啥变音乱调的。

那没事了

@dzcmingdi 我碰到的问题是：不加blank的情况下，大部分字发音是都非常好，少量的字的音会发成相近的音，总之不是当前字的音，加了blank就好了；不知道你那遇到这样的问题没？

    我们目前合成带噪，主要发生在输入音素序列保持标点的情况下。本来预计它有助于提升效果，比如句末的问号，叹号，句号是代表不同语气的嘛，但事实不是，合成结果个别音带噪。 我们正在试验的三组： 拼音序列带标点， 拼音序列带韵律， 拼音序列带标点和韵律。 结果 第二组效果最好，第一组效果最差。
   感觉标点符号是不发音字符，把它融进来可能会不小心学到一些奇怪的发音片段，不但没有学到情感，反而造成噪音效果。

弱弱问一下? 声韵母表，都是按照 贝壳的标注方法吗？ 比如 wu， 贝壳标法是空声母带一个韵母。 一般我们可以认为w是声母，u是韵母。 这两种标法哪种效果好?

是不是拼音序列中空格已经编码过的话，就不用加blank了？

要的吧，训练的时候默认输入音素序列每个元素后面插入个0

我刚开始跑，现在的版本没有插入Blanks，现在训练15Ksteps了，听者效果还行。没有啥变音乱调的。

那没事了

@dzcmingdi 我碰到的问题是：不加blank的情况下，大部分字发音是都非常好，少量的字的音会发成相近的音，总之不是当前字的音，加了blank就好了；不知道你那遇到这样的问题没

请问您是怎么做这种覆盖测试的？测试每个汉字的发音？中间加韵律吗？


text:
JsonPath#parse(URL) Is Treated Like JsonPath#parse(String)

I updated from 1.2.0 to 2.2.0 and saw the issue below.
JsonPath#parse(URL) used to parse the URL's content. Now it parses the actual URL.
Java
// 1.2.0
System.out.println("1.2.0: " + JsonPath.parse(new URL("http://ip.jsontest.com/")).json());
// 2.2.0
System.out.println("2.2.0: " + JsonPath.parse(new URL("http://ip.jsontest.com/")).json());

Console
1.2.0: {ip=192.168.1.1} # parses the content
2.2.0: http://ip.jsontest.com/ # parse the actual URL

As a workaround, Apache Commons can be used to convert a web page's content to a string using a one-liner: JsonPath.parse(org.apache.commons.io.IOUtils.toString(urlObject))

I generally do not think a URL is quite enough to get a content.
I suggest to remove this overloaded method JsonPath.parse(Url)
There are to many questions open.
Cheers
Jan

On 06 Apr 2016, at 18:16, ryanlevell notifications@github.com wrote:
As a workaround, Apache Commons can be used to convert a web page's content to a string using a one-liner: JsonPath.parse(org.apache.commons.io.IOUtils.toString(urlObject))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/jayway/JsonPath/issues/218#issuecomment-206446815

I agree with you @jlolling  There probably was a reason why URL stopped being used in the JsonContext and the HttpProvider (and Factory) were removed. Keeping them just creates inconsistent behavior like this issue.

The API was actually broken. URL was accepted as input but was not handeled as one. It now works in simplest possible way but the method has been deprecated.

authors: jlolling kallestenflo pointwisefixed ryanlevell

repo: jayway/JsonPath


text:
Make use of org.json

Hi,
I just strumbled upon this library so don't blame me if I didn't see anything obvious.
I'm just wondering why the library has no interface to the popular classes of org.json.*.
Have a nice day
Hubert Grzeskowiak

Hi,
you are actually the first to ask about org.json support. I think it will be similar to the GsonProvider. Feel free to have a look. :-)

Thanks, I am interested in a JsonProvider for JSON-Java unit testing, so will have a look.

I have actually started to implement this feature. Not sure when it will be ready but it's in the pipe.

Great, let me know if there is anything I can do to assist.

A JsonOrgJsonProvider is part of 2.1 release.

Nice, thanks!

authors: hubertgrzeskowiak kallestenflo nemesis13 stleary


text:
Hyphens on list items cause issues with XmlPath

From winter.k...@gmail.com on June 08, 2015 21:05:54
What steps will reproduce the problem? 1.  Try to create a body expression for a list whose name has a hyphen
Example:
RestAssured.when().get().then().body("root.some-item[0]", equalTo("")); What is the expected output? What do you see instead? It should look for the first "some-thing" entry and match it (and in the above case fail on matching), instead it throws an exception because it thinks that 'item' is a parameter.  This happens for both JSON and XML. What version of the product are you using? On what operating system? 2.4.1 Please provide any additional information below. It seems to be ok for the root element, and only fail for the second one on, as:
RestAssured.when().get().then().body("some-item[0]", equalTo(""));
does not throw the same exception.
Stracktrace:
java.lang.IllegalArgumentException: The parameter "item" was used but not defined. Define parameters using the XmlPath.params(...) function
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:232)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:252)
at com.jayway.restassured.assertion.XMLAssertion.getResult(XMLAssertion.groovy:75)
at com.jayway.restassured.assertion.XMLAssertion$getResult.callCurrent(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:151)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:179)
at com.jayway.restassured.assertion.XMLAssertion.getResult(XMLAssertion.groovy:107)
at com.jayway.restassured.internal.assertion.Assertion$getResult.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:110)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:130)
at com.jayway.restassured.assertion.BodyMatcher.validate(BodyMatcher.groovy:94)
at com.jayway.restassured.assertion.BodyMatcher$validate$0.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:110)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:138)
at com.jayway.restassured.assertion.BodyMatcherGroup$_validate_closure2.doCall(BodyMatcherGroup.groovy:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:292)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1016)
at groovy.lang.Closure.call(Closure.java:423)
at groovy.lang.Closure.call(Closure.java:439)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.collect(DefaultGroovyMethods.java:3167)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.collect(DefaultGroovyMethods.java:3137)
at org.codehaus.groovy.runtime.dgm$66.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:110)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:122)
at com.jayway.restassured.assertion.BodyMatcherGroup.validate(BodyMatcherGroup.groovy:47)
at com.jayway.restassured.assertion.BodyMatcherGroup$validate$3.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:110)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:138)
at com.jayway.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:560)
at com.jayway.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:110)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:122)
at com.jayway.restassured.internal.ResponseSpecificationImpl.validateResponseIfRequired(ResponseSpecificationImpl.groovy:731)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:207)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:151)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:163)
at com.jayway.restassured.internal.ResponseSpecificationImpl.content(ResponseSpecificationImpl.groovy:227)
at com.jayway.restassured.specification.ResponseSpecification$content$2.callCurrent(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49)
at org.codehaus.groovy.runtime.cal...
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=409

From johan.ha...@gmail.com on June 27, 2015 10:01:24
Thanks for reporting. I think a workaround would be to escape it with single quotes.
Status: Accepted

From johan.ha...@gmail.com on June 27, 2015 10:54:31
I started to implement this but it turns out that it's quite tricky and I'm not sure it's worth the effort. For example in JSON you could define properties like this:
{ "some-list[0]" : "one" }
and of course
{ "some-list" : [ "one", "two" ] }
Currently the implementation don't have a reference to the actual property name in the JSON structure while escaping "keys" in the path. This make is very difficult to determine if path "some-list[0]" should be escaped as "'some-list[0]'" or "'some-list'[0]".
One thing that I could do is of course to assume that it'll be escape as "'some-list'[0]" (i.e. a list) and if you name your property "some-list[0]" it'll fail and you'll have to manually escape it (i.e. I will need to break backward compatibility). But I suppose that people naming their properties like "some-list[0]" would be quite rare..
What do you think?
Labels: -Priority-Medium Priority-Low

Fixed in master

repo: jayway/rest-assured


text:
Add DaVinci Resolve

NOTE: A similar PR may already be submitted! Please search among the Pull request before creating one.
Types of Changes
What types of changes does your PR introduce? Put an x in all boxes that apply

[x] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list

Proposed Changes
Describe each of your changes here to communicate to the maintainers why we should accept this pull request.

If you're adding something to the list, be sure to explain why it should be added.
If you're fixing a bug or resolving a feature request, be sure to link to that issue.

PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[x] I have added necessary documentation (if appropriate)

Further Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

DaVinci Resolve is a great free tool for video and audio postproduction used by industry professionals.

@marcinlesek  thx!

authors: jaywcjlove maticbasle

repo: jaywcjlove/awesome-mac


text:
Deadlock when using concurrency in async views

Hi folks,
First of all thanks for maintaining this amazing project! I've recently started migrating an existing project to asynchronous views and noticed that the view gets deadlocked when tasks are executed concurrently and the Debug Toolbar is installed.
If no tasks run concurrently (ie. using a sequence of awaits) or the Debug Toolbar is removed, everything seems fine.
Below is an example that hangs forever on await asyncio.gather:
async def get(request):
    (one_thing, another_thing) = await asyncio.gather(
        Thing.objects.filter(pk=1).afirst(),
        Thing.objects.filter(pk=2).afirst()
    )

    return HttpResponse(content=f"Hello {one_thing.pk} {another_thing.pk}")

I'm relatively new to Python asyncio and have therefore no idea what's going on. I see the ongoing async issues in this issue tracker but I am not sure what's the state of Django async support (or lack of it) is here. (Something that might be worth documenting on the Readme.)
These are the dependencies in use:
$ poetry show -T
daphne               4.0.0   Django ASGI (HTTP/WebSocket) server
django               4.2.4   A high-level Python web framework that encourages rapid development and clean, pragmatic design.
django-debug-toolbar 4.2.0   A configurable set of panels that display various debug information about the current request/response.
psycopg2-binary      2.9.7   psycopg2 - Python-PostgreSQL Database Adapter

I can share a minimal test project if someone wants to have a look.

The toolbar is sync only at this time. If you'd like to open a PR to call that out explicitly in the Readme and installation docs, that would be helpful. There was another idea to log a message or not fail too. If you can help, it'd be appreciated.

The toolbar is sync only at this time. If you'd like to open a PR to call that out explicitly in the Readme and installation docs, that would be helpful. There was another idea to log a message or not fail too. If you can help, it'd be appreciated.

@tim-schilling Something like this? https://github.com/jazzband/django-debug-toolbar/pull/1829
How big of an undertaking would be to add async support? (Full or partial). Looking at these issues, I have no idea: https://github.com/jazzband/django-debug-toolbar/issues?q=is%3Aissue+project%3Ajazzband%2F9+is%3Aopen
I'd be motivated to help, even with small contributions but am not familiar with the Toobar's internals (moderately familiar with Django internals, noob at Python async). Let me know if there are low hanging fruits to tackle.

@salomvary Thank you for that PR and the offer to help.
The project for async compatibility is here: https://github.com/orgs/jazzband/projects/9
The main thing that you can help with that doesn't require much effort on my part is implementing tests that the toolbar would need to pass to be considered "working". This is issue https://github.com/jazzband/django-debug-toolbar/issues/1819

I guess it does not make sense to keep this issue open then.

As I recently discovered, async or not, concurrent ORM queries are not yet a thing in Django, therefore this issue is even less of an issue in practice.

authors: salomvary tim-schilling

repo: jazzband/django-debug-toolbar


text:
Cannot resolve keyword 'history' into field.

the bug
Model with two managers does not seem to detect the history field.
class BookMark(models.Model):
    created_at = models.DateTimeField("Created at", auto_now_add=True)
    history = HistoricalRecords()

    objects = models.Manager()
    table_manager = BookMarkManager()

Expected behavior
When calling this I'm supposed to get the results
queryset=BookMark.objects\
                    .filter(history__history_date__gt=last_week)

error received
Cannot resolve keyword 'history' into field. Choices are: created_at
Environment (please complete the following information):

OS: UBUNTU 20
Django Simple History Version: 3
Django Version: 2.2
Database Version: MySQL 8

I'm facing the same issue, how did you solve it ?

in my model : history = HistoricalRecords() + a manager
when doing a simple Model.objects.filter(history__history_user=1) I get this error : Cannot resolve keyword 'history' into field

authors: alvarolloret raphodn

repo: jazzband/django-simple-history


text:
Add list method aliases to FeatureCollection

Implements support for the + operator to FeatureCollections, as well as the clear(), append(), extend(), and insert() methods
Closes #154
To do:

[ ] Update documentation
[ ] Determine right-side addition behavior

Right side addition
How should right-side addition to generic Collection be handled?
When doing something like FeatureCollection([feature1]) + [feature2], it makes sense to me that a FeatureCollection would be returned. But what about the reverse, [feature1] + FeatureCollection([feature2])? As of right now, a list will be returned, but maybe that's not very Pythonic behavior? Should a TypeError be raised instead?

Closing as out-of-scope per discussion on #154

repo: jazzband/geojson


text:
pip==23.3 breaking "extras" behavior

Using pip==23.3.x can result in invalid requirements.txt for projects that declare extras.
A change in pip==23.3.0 introduced the "canonicalization" of extras names:

https://github.com/pypa/pip/pull/12002/files

The canonicalization leads to this outcome:

 requirements.in: sqlalchemy[postgresql_psycopg2binary]
requirements.txt: sqlalchemy[postgresql-psycopg2binary]

For many cases, this probably isn't an issue.
psycopg2-binary still makes it into requirements.txt as an individual entry.
For more "niche" cases, the extras still carry some significance.
eg. When using rules_python under the Bazel build system, the extras must properly resolve to build out a dependency graph.
Environment Versions

OS Type: Linux
Python version: 3.10.9
pip version: 23.3.0
pip-tools version: 7.3.0

Steps to replicate

Create a simple requirements.in file.

sqlalchemy[postgresql_psycopg2binary]==1.4.47

Create a virtual environment, install pip-tools and the previous major pip version, run pip-compile.

python -m venv .venv
. ./.venv/bin/activate
pip install pip-tools==7.3.0 pip==22.3.1
pip-compile --no-strip-extras

Observe that the resulting requirement.txt file lists sqlalchemy[postgresql_psycopg2binary] (with an underscore).

greenlet==3.0.0
    # via sqlalchemy
psycopg2-binary==2.9.9
    # via sqlalchemy
sqlalchemy[postgresql_psycopg2binary]==1.4.47
    # via -r requirements.in

On the same virtual environment, upgrade to pip>=23.3, run pip-compile.

pip install pip==23.3.0
pip-compile --no-strip-extras

Observe that the resulting requirement.txt file lists sqlalchemy[postgresql-psycopg2binary] (with a hyphen).

  WARNING: sqlalchemy 1.4.47 does not provide the extra 'postgresql-psycopg2binary'

greenlet==3.0.0
    # via sqlalchemy
psycopg2-binary==2.9.9
    # via sqlalchemy
sqlalchemy[postgresql-psycopg2binary]==1.4.47
    # via
    #   -r requirements.in
    #   sqlalchemy

Expected result
The valid input extras should still be valid in the output.
Actual result
The output extras will not resolve.

Just a quick note:
pip==23.3.0 will attempt to look up the canonical extra postgresql-psycopg2binary before falling back to postgresql_psycopg2binary.
The simple answer to this issue may just be that the sqlalchemy extras should list the canonical variants in their package.

Oof, in my local test, it comes out as
sqlalchemy[postgresql-psycopg2binary,postgresql_psycopg2binary]==2.0.22

Using the legacy resolver, it's just
sqlalchemy[postgresql_psycopg2binary]==2.0.22

I tried adding a simple
if ireq.extras:
    ireq.extras = set(map(canonicalize_name, ireq.extras))

to the start of format_requirement, but it seems that the str function on a req/ireq still has the old, repeated extra names somewhere....

@AndydeCleyre I think that the normalization should happen whenever an instance of InstallRequirement or InstallationCandidate is first encountered/constructed. By doing so, all other parts of the depresolver would work with the normalized stuff...

So another place we can get at this is in pip_compat.parse_requirements:
diff --git a/piptools/_compat/pip_compat.py b/piptools/_compat/pip_compat.py
index 6409fbc..6972f03 100644
--- a/piptools/_compat/pip_compat.py
+++ b/piptools/_compat/pip_compat.py
@@ -14,6 +14,7 @@ from pip._internal.network.session import PipSession
 from pip._internal.req import InstallRequirement
 from pip._internal.req import parse_requirements as _parse_requirements
 from pip._internal.req.constructors import install_req_from_parsed_requirement
+from pip._vendor.packaging.utils import canonicalize_name
 from pip._vendor.packaging.version import parse as parse_version
 from pip._vendor.pkg_resources import Requirement

@@ -74,7 +75,10 @@ def parse_requirements(
     for parsed_req in _parse_requirements(
         filename, session, finder=finder, options=options, constraint=constraint
     ):
-        yield install_req_from_parsed_requirement(parsed_req, isolated=isolated)
+        ireq = install_req_from_parsed_requirement(parsed_req, isolated=isolated)
+        if ireq.req.extras:
+            ireq.req.extras = set(map(canonicalize_name, ireq.req.extras))
+        yield ireq

 def create_wheel_cache(cache_dir: str, format_control: str | None = None) -> WheelCache:

But things I don't know include:

do we need to manipulate the ireq.extras as well here?
will this fix the issue when sqlalchemy[postgresql_psycopg2binary] is a dep of something else?
do we need to do similar adjustments in all the other places we use install_req_from_* functions?
should we converge on the canonicalized extras names, even though this report expresses an expectation for the non-canonicalized form used by the package (sqlalchemy)?

Some extras are getting duplicated. It doesn't appear to impact the resolver or pip's use of the requirements file but it is an unexpected change when updating to pip 23.3.x. This is pip 23.3.1 and pip-tools 7.3.0:
$ cat test.in
sentry_sdk[pure_eval]

$ pip-compile --output-file test.txt test.in --upgrade --allow-unsafe
WARNING: --strip-extras is becoming the default in version 8.0.0. To silence this warning, either use --strip-extras to opt into the new default or use --no-strip-extras to retain the existing behavior.
#
# This file is autogenerated by pip-compile with Python 3.12
# by the following command:
#
#    pip-compile --allow-unsafe --output-file=test.txt test.in
#
asttokens==2.4.1
    # via sentry-sdk
certifi==2023.7.22
    # via sentry-sdk
executing==2.0.0
    # via sentry-sdk
pure-eval==0.2.2
    # via sentry-sdk
sentry-sdk[pure-eval,pure_eval]==1.32.0
    # via -r test.in
six==1.16.0
    # via asttokens
urllib3==2.0.7
    # via sentry-sdk

do we need to manipulate the ireq.extras as well here?

Maybe? Given it's not possible at some earlier stage...

will this fix the issue when sqlalchemy[postgresql_psycopg2binary] is a dep of something else?

Why not? Wouldn't “something else” also go through normalization?

do we need to do similar adjustments in all the other places we use install_req_from_* functions?

Probably. I'd expect us to be consistent across the codebase.

should we converge on the canonicalized extras names, even though this report expresses an expectation for the non-canonicalized form used by the package (sqlalchemy)?

I'd say yes. Canonicalization is well-defined now and as the time passes, more people will use newer pip versions that do this. At some point, we'll EOL support for pip versions that don't do such conversion and then, we'd just differ for no good reason. Maybe, we'd need to leave the original dep names in the comments, though.

Maybe we should shadow all the install_req_from_* functions, or pursue getting the upstream functions to canonicalize, in pip?

Does pip not normalize in all places? I think it may make sense there too.

Does pip not normalize in all places? I think it may make sense there too.

Yeah we're getting non-normalized extras via pip._internal.req.constructors.install_req_from_parsed_requirement, pip._internal.req.constructors.parse_req_from_line, and the main InstallRequirement constructor, at least.

It doesn't appear to impact the resolver or pip's use of the requirements file but it is an unexpected change when updating to pip 23.3.x.

I just wanted to share that in my experience, the duplicate extras DO impact the resolution, although it's possible that I'm misattributing the behavior. Some clarifications would help me understand if I should report an issue with pip instead.
In my case, having pyhive[hive_pure_sasl,presto]==0.7.0 in my requirements.in file using pip==23.3.1 and pip-tools==7.3.0 with --resolver=legacy results in the hive_pure_sasl requirements thrift-sasl and pure-sasl being removed/omitted from the resulting lockfile, but including the mash-up of pyhive[hive-pure-sasl,hive_pure_sasl,presto]==0.7.0.
It's odd that the extra dependencies ARE included when using --resolver=backtracking.
One additional tidbit: To work around this, we are explicitly listing thrift-sasl in requirements.in, which surprisingly results in pip-compile correctly including a via pyhive comment. This is despite the fact that without explicitly listing thrift-sasl as a direct dependency, pip-compile would have removed its entry entirely.
Do the via comments use a different mechanism to determine which packages are required by which than actual dependency resolution does?

One other thing that seems related to this:
It's odd, and I think unexpected, that listing a package is listed in the via comments of itself when any extras are provided and the backtracking resolver is used. For example, when a requirement is listed as sqlalchemy[postgresql-psycopg2binary], via sqlalchemy will show up alongside the source requirements file in the comments. When using the legacy resolver, packages are not listed in the via comments of their own package specifier.
I'm also happy to make that its own issue, if you feel is distinct enough. Thanks!

@tboddyspargo I don't think I can reproduce the self-via issue.
$ pip-compile --version
pip-compile, version 7.3.0
$ <<<'sqlalchemy[postgresql-psycopg2binary]' pip-compile --no-header - -o - 2>/dev/null
greenlet==3.0.1
    # via sqlalchemy
sqlalchemy[postgresql-psycopg2binary]==2.0.23
    # via -r -
typing-extensions==4.8.0
    # via sqlalchemy

And with my PR #2013:
$ pip-compile --version
pip-compile, version 7.3.1.dev65
$ <<<'sqlalchemy[postgresql-psycopg2binary]' pip-compile --no-header - -o - 2>/dev/null
greenlet==3.0.1
    # via sqlalchemy
sqlalchemy[postgresql-psycopg2binary]==2.0.23
    # via -r -
typing-extensions==4.8.0
    # via sqlalchemy

Apologies if this is implied by the ticket elsewhere, but pip==24.0 and pip-tools==7.4.0 emits a warning I don't think I saw before:
WARNING: sentry-sdk 1.40.5 does not provide the extra 'pure-eval'

The name of the extra in the package and in my requirements.in is pure_eval with an underscore.

@dgilmanAIDENTIFIED
I can't reproduce that here on Linux with Python 3.11, with the versions you specified.
Can you test if it still happens with #2013 ?

Testing it out with that branch I don't get the warning. My output is:
root@3d945b95eb1f:/# pip-compile --output-file foo.txt foo.in --upgrade --allow-unsafe
WARNING: --strip-extras is becoming the default in version 8.0.0. To silence this warning, either use --strip-extras to opt into the new default or use --no-strip-extras to retain the existing behavior.
#
# This file is autogenerated by pip-compile with Python 3.11
# by the following command:
#
#    pip-compile --allow-unsafe --output-file=foo.txt foo.in
#
certifi==2024.2.2
    # via sentry-sdk
sentry-sdk[pure-eval]==1.40.5
    # via -r foo.in
urllib3==2.2.1
    # via sentry-sdk

Note that the underscore in pure_eval is replaced by a dash. I'd also expect the packages pure_eval, asttokens and executing to be pinned in the file but they aren't in there at all.

Note that the underscore in pure_eval is replaced by a dash.

This is currently intentional.

I'd also expect the packages pure_eval, asttokens and executing to be pinned in the file but they aren't in there at all.

Uh oh. Thanks!

authors: AndydeCleyre dgilmanAIDENTIFIED mattoberle tboddyspargo webknjaz

repo: jazzband/pip-tools


text:
Fix wrong grid item sorting in responsive mode

Fixes #298
Example case:
[
  { i: 1, x: 0, y: 0, w: 1, h: 2 },
  { i: 2, x: 0, y: 0, w: 1, h: 2 },
]

was sorted (depending on browser algorithm) into:
[
  { i: 2, x: 0, y: 0, w: 1, h: 2 },
  { i: 1, x: 0, y: 0, w: 1, h: 2 },
]

With this PR, the order of grid items with the same x, y values won't be changed.

Next time please don't submit the built files

authors: gmsa pieterbeulque

repo: jbaysolutions/vue-grid-layout


text:
panic: No Auth Provider found for name "gcp"

just finished catching up on the last TGIK (timezone...) - really enjoyed that one - thanks! :-)
trying to follow along with a controller from the "initial point" (commit 13db5aa), running it as is on my MacBook against my k8s cluster on GKE, I get an error about GCP Auth:
>KUBECONFIG=~/.kube/config go run *.go
2017/08/12 11:51:17 tgik-controller version UNKNOWN
panic: No Auth Provider found for name "gcp"

goroutine 1 [running]:
github.com/jbeda/tgik-controller/vendor/k8s.io/client-go/kubernetes/typed/admissionregistration/v1alpha1.NewForConfigOrDie(0xc4200ff880, 0xc4200a91e0)
	/Users/itamar/go/src/github.com/jbeda/tgik-controller/vendor/k8s.io/client-go/kubernetes/typed/admissionregistration/v1alpha1/admissionregistration_client.go:63 +0x62
github.com/jbeda/tgik-controller/vendor/k8s.io/client-go/kubernetes.NewForConfigOrDie(0xc4200ff880, 0x0)
	/Users/itamar/go/src/github.com/jbeda/tgik-controller/vendor/k8s.io/client-go/kubernetes/clientset.go:519 +0x49
main.main()
	/Users/itamar/go/src/github.com/jbeda/tgik-controller/tgik-controller.go:39 +0x233
exit status 2

Am I missing something?

ok, figured it out.
added the following line the the imports in controller.go (line 12):
_ "k8s.io/client-go/plugin/pkg/client/auth/gcp"

this triggered an error with log_dir flag redefinition, so I removed vendor/github.com/golang/glog (since I already have glog under $GOPATH).
then the "No Auth provider found" error came back, so I removed also vendor/k8s.io (since I have up-to-date client-go & apimachinery under $GOPATH).
now it's working :-)

Sorry I missed this bug report! Too many github emails flying around.

Sorry I missed this bug report! Too many github emails flying around.

understandable :-)
btw, what is the recommended way to deal with issues with duplicate dependencies between my $GOPATH and the vendor dir?

I believe that the vendor dir will win for any dependency.  Generally, however, it is bad form for libraries to also vendor dependecies. This stuff is super complicated at the limit and none of the tools are there yet.  Lots of people are coalescing around dep as the solution but client-go isn't there yet.

authors: itamaro jbeda

repo: jbeda/tgik-controller


text:
Having problems installing from a local layout

HI Jakub,
first, thanks for the work you've put into these packages, they are well crafted and I'm keen to leverage them if I can.
What I'm trying to do is to use them in an enterprise "on-prem" context, to avoid pulling down the installation binaries from the internet (this is an enterprise context).  The solution I hit upon was to create a "layout" of all workloads as one big zip (17Gb for VS2017), and have created my own little choco package "VS2017InstallFiles" that basically downloads that zip from our own on-prem Nexus so that once this package is installed I have a layout on my C: drive under c:\programdata\chocolatey\lib\vs2017installfiles.  So far, so good.
What I am struggling with is how to then install VS2017 specifying the layout path.  Using your docs at https://github.com/jberezanski/ChocolateyPackages/blob/master/chocolatey-visualstudio.extension/EXAMPLES.md I have come up with:
cinst visualstudio2017enterprise --params "--bootstrapperPath c:\programdata\chocolatey\lib\vs2017installfiles\VS-2017-BT-15.7.0\vs_BuildTools.exe --noWeb"
However this fails with very little to go on (logs just say returned 1).
Any clues how to debug this would be very much appreciated...?

Hi Dan,
Your solution seems sound and the command line appears to be correct.
The VS Installer generates a lot of log files which usually quickly point to the cause of the problem. When installation is done by choco, these files end up in $Env:TEMP\chocolatey (and are named dd_*.log).
Apart from the log files, I'd check:

whether VS installs successfully from your layout if you invoke it interactively (without choco) - this may detect some issues with the layout,
whether VS installs successfully via choco without using your layout (pulling files from the internet) - this may detect some obstacles in the configuration of your workstations.

One disclaimer, though. It seems you are installing a very old VS 2017 version (15.7.0 was released in May 2018). There had been numerous changes to the VS installer behavior over the years, even breaking changes, to which I had to adapt the package scripts. I always intended to preserve backward compatibility, but I generally only test the packages with the latest versions of VS 2017, 2019 and 2022. So it should work, but then, it might not.

Hi Jakub,
Many thanks for the quick reply and for these hints.  I haven't had the
chance yet to try out the debugging, but I'll post back here once I do.
On the topic of the old VS2017, actually I am working with the latest, I
just copied-n-pasted that snippet from a README doc in your repo.
Thanks again, will let you know.
Dan
On Sat, 6 Nov 2021 at 12:35, Jakub Bereżański @.***>
wrote:

Hi Dan,
Your solution seems sound and the command line appears to be correct.
The VS Installer generates a lot of log files which usually quickly point
to the cause of the problem. When installation is done by choco, these
files end up in $Env:TEMP\chocolatey (and are named dd_*.log).
Apart from the log files, I'd check:

whether VS installs successfully from your layout if you invoke it
interactively (without choco) - this may detect some issues with the layout,
whether VS installs successfully via choco without using your layout
(pulling files from the internet) - this may detect some obstacles in the
configuration of your workstations.

One disclaimer, though. It seems you are installing a very old VS 2017
version (15.7.0 was released in May 2018). There had been numerous changes
to the VS installer behavior over the years, even breaking changes, to
which I had to adapt the package scripts. I always intended to preserve
backward compatibility, but I generally only test the packages with the
latest versions of VS 2017, 2019 and 2022. So it should work, but then, it
might not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jberezanski/ChocolateyPackages/issues/121#issuecomment-962445242,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH33SLXCYXPINCI6GJHLSLUKUOJBANCNFSM5HPLSWDA
.

Closing due to inactivity.

authors: danhaywood jberezanski

repo: jberezanski/ChocolateyPackages


text:
Add hyperbolic tangent initial conditions back

These initial conditions are more used in DNS diffusive convection models as the interface thickness is important. With hyperbolic tan initial conditions it is more straightforward to set initial conditions that have the same thickness over the interface.

Closed with #25

Closed with #25


text:
[Question] Decopuling queue receiver logic from application/domain logic

Hi,
I have a worker that dequeues messages from a queue and executes some logic.
I would like to use MediatR to decopule the queue receiver logic from the application/domain logic.
Example:
New message dequeued-> Execute receiver logic (eg: deadletter when invalid etc.)-> Send a MediatR request-> Handle MediatR Request-> Execute app/domain logic
Do you think that this is a valid use case for this library?
Thank you

Ahhhhh probably not. It's not really for durable messages. I think you
might look at tools like Rebus or Mass Transit instead. There'll be a TON
of missing things you'll run into.
On Mon, Mar 30, 2020 at 3:14 PM luca-esse notifications@github.com wrote:

Hi,
I have a worker that dequeues messages from a queue and executes some
logic.
I would like to use MediatR to decopule the queue receiver logic from the
application/domain logic.
Example:
New message dequeued->Deserialize the message->Send a MediatR
request->Handle MediatR Request->Execute app/domain logic
Do you think that this is a valid use case for this library?
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jbogard/MediatR/issues/505, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZQMR5QCGBESHPNU6EKFTRKD4SPANCNFSM4LW4GDCA
.

Hi, i'm already using MassTransit, here is proof of concept of what i want to do:
sbc.ReceiveEndpoint(host, "my_queue", endpoint => 		{ 			endpoint.Handler<MyMessage>(async context => 			{ 				await mediator.Send(new MyRequest { [...] }); 			}); 		});
There reason is we have multiple sources for requests, eg: queue messages, gRPC API and REST API.
By using MediatR we would have a nice and consistent layer of IRequestHandlers regardless of the type of application.
Do you still think that this is not a valid use case?

You can try, but it might be a bit annoying to translate external messages
to internal requests. I use NServiceBus a lot, and its handlers already
look like MediatR ones (minus return values), and that's the biggest win.
Those bus libraries have their own middleware, and I'd rather use that
instead of the MediatR stuff.
On Tue, Mar 31, 2020 at 3:29 AM luca-esse notifications@github.com wrote:

Hi, i'm already using MassTransit, here is proof of concept of what i want
to do:
sbc.ReceiveEndpoint(host, "my_queue", endpoint => {
endpoint.Handler(async context => { await mediator.Send(new
MyRequest { [...] }); }); });
There reason is we have multiple sources for requests, eg: queue messages,
gRPC API and REST API.
By using MediatR we would have a nice and consistent layer of
IRequestHandlers regardless of the type of application.
Do you still think that this is not a valid use case?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jbogard/MediatR/issues/505#issuecomment-606467224,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZQMTBECPKQKTYZSMU423RKGPXXANCNFSM4LW4GDCA
.

We do this a bit today and we just serialize and deserialize the message to JSON with JsonSerializerSettings.TypeNameHandling = TypeNameHandling.Objects and it seems to work pretty well.

authors: jbogard lilasquared luca-esse

repo: jbogard/MediatR


text:
bumped several dependency versions and fixed vulnerabilities

Signed-off-by: Lars Heinemann lhein.smx@gmail.com

please precise in the message commit the "bumped versions", it will make it easier to read the history.
Also, at first I thought it was to bump the version of the porject, not of the dependencies

it was a change of only a few versions which are easily recognizable in the package.json diff.

It is not configured for this repo yet it seems. I will add it later.

it was configured: https://github.com/jboss-fuse/vscode-datavirt/pull/93

authors: apupier lhein

repo: jboss-fuse/vscode-datavirt


text:
🛑 https://jbowdre.lol is down

In 8491a64, https://jbowdre.lol (https://jbowdre.lol) was down:

HTTP code: 502
Response time: 473 ms

Resolved: https://jbowdre.lol is back up in f6b7ba2 after 8 minutes.

repo: jbowdre/upptime


text:
🐛 fix(provider-verification): allow empty tags when using pending pacts

Solves #520
Enabling pending pacts now requires to have either tags or branch set for the provider (but one of them can be undefined).
As the providerBranch is already set when calling verifyPacts, I didn't add it as a parameter to the PactBrokerWithSelectors class like the providerTags currently are. I'm not entirely sure if this matches the desired code architecture or not.
I took this opportunity to flag as deprecated all methods referring to the providerTags in PactBrokerWithSelectors.

@gaeljw could you try repushing this to see if the workflow triggers

Look's it's working now. Thanks @jbwheatley

authors: gaeljw jbwheatley


text:
[BUGish] Remove ethers as project dependency

Description
ethers is responsible for a hefty 296KB of the bundle size. I think we might be able to remove it and replace it with the @ethersproject/<module> sub-modules and save a bunch of bundle space.

Proposal
Possible approach:

Run yarn analyze to get a baseline bundle size.

Grep the codebase for string from 'ethers'

Replace each import with the corresponding submodule import.
- import { constants } from 'ethers'
+ import * as constants from '@ethersproject/constants'

Remove the ethers dependency (e.g. yarn remove ethers)

Run yarn analyze again and compare.

i didn't understood the grep part?

@RishiKumarRay one way to do that is "find all" in your code editor:

@aeolianeth

getting these warnings for these sub modules

@aeolianeth  getting these warnings for these sub modules

@RishiKumarRay ah, looks like the utils is broken up across many modules. For example:
- import { utils } from 'ethers'
+ import { formatBytes32String } from '@ethersproject/strings'
// ...
- utils.formatBytes32String('')
+ formatBytes32String('')

This file might help you find which modules to import for various util functions: https://github.com/ethers-io/ethers.js/blob/master/packages/ethers/src.ts/utils.ts

@aeolianeth one more thing in some places there are two functions together then what to implement like big number and constant are together then should i write their submodule together?

@aeolianeth one more thing in some places there are two functions together then what to implement like big number and constant are together then should i write their submodule together?

@RishiKumarRay  In that case, we can import them separately:
- import { BigNumber, constants } from 'ethers'
+ import * as constants from '@ethersproject/constants'
+ import { BigNumber } from '@ethersproject/bignumber'

Is anyone still working on this issue? I'd be happy to submit a PR.

@benschac thanks for your interest! I gave this a crack in https://github.com/jbx-protocol/juice-interface/pull/639, and it looks good, although it doesn't appear to have a massive impact on chunk JS loaded (about 100kb, which is still quite good).
Going to investigate further 👍 . let me know if you have any thoughts.

Nice, I was looking at the PR and had a quick question. I'll comment there.

authors: RishiKumarRay aeolianeth benschac

repo: jbx-protocol/juice-interface


text:
JB-483 - Increase tiny nfts images in NFTs & Rewards card to 56px as per design

What does this PR do and why?
Closes JB-483
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3815   👈

This comment was auto-generated by Graphite.

@wraeth-eth started a stack merge that includes this pull request via Graphite.

@wraeth-eth merged this pull request with Graphite.


text:
No Error Handling on Core

REF:
https://github.com/jccultima123/MyPHP/blob/master/classes/Core.php
https://github.com/jccultima123/MyPHP/blob/master/classes/Init.php

So far, i am unable to update this issue and it's been fixed few weeks ago so i am gonna close this


text:
[Help] Compile jcefmaven with custom fork of java-cef

First, thanks for this project - I'm currently switching my application from jxbrowser to java-cef and this project has made the transition much easier.
I have the need to compile custom versions of java-cef as there are several bug fixes which I need to apply to get my own application in production. These bugs have been reported, but of course I cannot expect those changes to propagate through the pipeline in a timeline which meets my needs.  I was wondering if you could help with instructions on how to create the necessary packages for the jcefmaven project with my custom fork of java-cef.

Hey there - sorry for the late reply. You can simply fork the jcefbuild and jcefmaven repositories from github and run the github actions scripts using your own repository urls. But beware: You will need to supply some secrets - for example a macos developer secret if you want to deploy for macos. You can of course also remove these steps from the build as you please. The required secrets can be found in the readme of jcefbuild.

Thanks I give it a try!

Will close this issue - feel free to reply if you have any issues with building! :)

authors: FriwiDev ghedlund

repo: jcefmaven/jcefmaven


text:
"Could not load file or assembly"

Dear,
When running this:
l_udp = new UdpEndpoint(Computer.ThisComputer_IP(), l_DevicePort.IpPort);
where  =172.30.0.150 and the device port is 4446, so pretty straightforward Ip and port
We get the error:
Could not load file or assembly 'Caching, Version=1.3.4.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
However, we can't seem to find where exactly in the code the file error comes from.
Looking forward to your reply!

Hi @Sippelberg sorry, for some reason Github didn't send me a notification on this (or any!) issues in this repo.  Caching.dll is a dependency of the library, did you install it?  If you use NuGet it should automatically.

authors: Sippelberg jchristn

repo: jchristn/SimpleUdp


text:
Configurable OpenID/Authentication in the MS

Don't hardcode this.  Make an object in the MS for this, and make it selectable.

This is fixed in the syndicate2 branch.  Gateways use helper programs to fetch user keys, volume certs, gateway certs, and cert bundles, and verify that they are authentic.  The MS does not run OpenID anymore; it just denies requests that aren't signed by gateways it doesn't trust.

Currently fixed.

repo: jcnelson/syndicate


text:
Add intersections_with_shape method from rapier

During the Bevy Jam we needed intersections_with_shape functionality from rapier, but it was unavailable, so we made a quick hack to add it.
Now i have made a proper implementation and want to share it.

I was implementing a pulsing mechanic and the main idea was that some object (for example explosive barrel) will have a zone attached to it and it will "pulse" periodically (or once). And instead of checking collision events and record entities that are near the object I thought of using intersections_with_shape to get get all entities in the area at once.

Ah, interesting. Thanks for sharing.
I am wondering, what if #216 was available? I guess that, with that feature, you could make the barrel a sensor. And instead of reacting on collision event as they happen, simply grab the list of collided entities from the CollisionEntities component at each pulse?
Would that work? Would it be better or less good?

hmm..  I think that would have worked for our case. Definitely would be a bit less code. But i can think of one example, where intersections are better: if we need to check the layers for possible interactions, like a fire area should not interact with walls but should interact with player and enemies.

if we need to check the layers for possible interactions, like a fire area should not interact with walls but should interact with player and enemies.

The CollisionEntities component contains only entities that are collided according to the defined layers. So if the fire area is configured to collide with players only, then the CollisionEntities will contain player entities, not walls.
And even for potentially more complex cases (that I don't even visualize yet), because we anyway need to query the referenced entities, we can simply use query filters.
example:
fn pulse_fire_aoe(
  mut players: Query<&mut Health, With<Player>>,
  mut fire: Query<(&mut Timer, &CollitionEntities), FireArea>,
  time: Res<Time>,
) {
  for (mut timer, collisions) in fire.iter_mut() {
    timer.tick(time.delta());
    if timer.finished() {
      for entitiy in collisions.collided_entities() {
        if let Ok(mut health) = players.get_mut(entity) {
          health.0 -= 10;
        }
      }
    }
  }
}

Would intersections_with_shape make it simpler? And if yes, how?

Ok, for some reason i thought that CollisionEntities will contain all entities in the area, my bad.
Then intersections_with_shape seems kinda useless for this use case, unless the area is created and checked in one frame, so there are no colliders to take intersecting entities from. But right now I can not think of a game mechanic that needs this.
Also intersections_with_shape might be easier to use, because you don't need to keep the sensor area around and manage it.
Also as I remember if a new sensor is created in place, where there are other colliders already exists, then there would be no collision events, until these colliders go out of the area and enter it again.

Also intersections_with_shape might be easier to use, because you don't need to keep the sensor area around and manage it.

Keeping a sensor area seems quite cheap and easy to me. And I feel like we'd anyway some way to keep track of where the detection area should be.
Anyway, that's too theoric to lead anywhere IMO. Better wait until someone actually has a use-case to share.

Also as I remember if a new sensor is created in place, where there are other colliders already exists, then there would be no collision events, until these colliders go out of the area and enter it again.

That would be annoying indeed. But I that's the case, then we may instead try to fix that problem directly.

Then intersections_with_shape seems kinda useless for this use case, unless the area is created and checked in one frame, so there are no colliders to take intersecting entities from. But right now I can not think of a game mechanic that needs this.

Okay, thanks for the feedback. Then I think I close this issue as "wontfix". If someone bumps into a use-case that would be better solved with intersections_with_shape then we can re-open this issue and re-consider it.
Thanks for sharing ;-)

authors: ShadowCurse jcornaz

repo: jcornaz/heron


text:
🛑 syntax is down

In b49ead9, syntax (https://syntax-systems.com) was down:

HTTP code: 503
Response time: 481 ms

Resolved: syntax is back up in f3d6a38.

repo: jcruse-erw/UptimeReport


text:
🛑 audience is down

In 015082b, audience (https://www.audience-soest.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: audience is back up in 9f7ca75.


text:
Investigate proper completion support

Investigate proper completion support, ala: https://twitter.com/Jeff__Ward/status/1014891629612707842

repo: jcward/haxe-seoverload


text:
Update zio, zio-streams, zio-test, ... to 2.0.0-RC4

Updates

dev.zio:zio
dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-junit
dev.zio:zio-test-magnolia
dev.zio:zio-test-sbt

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

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

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #106.

repo: jczuchnowski/zio-pulsar


text:
Bug : Bold is not working 🔴

Another Bug  I found is that Bold is not working. Here is the screecast.
https://user-images.githubusercontent.com/28984548/137823647-2744c37f-3afe-44e4-8e8c-fa3c3bed37d4.mov

Thank you for reporting it so soon! Try updating the theme, it should be working now. ;)

I've just installed it and this bug persist
https://user-images.githubusercontent.com/1221474/138018737-bcfc7c57-b557-432f-b8c0-a940d38d6c07.mp4

Do me a favor, and open Style Settings, and change the editor/preview font to one you have installed on your computer (a system font is fine). See if the bold is displayed or not.

Yep, I changed the preview and editor fonts in this way :
--font-preview: -apple-system, sans-serif;
--font-editor: -apple-system, sans-serif;

and bold works

Make sure to update the theme, as I've uploaded the new file just a minute ago

Can you change the font same as @lavaldi , @ujjwal3067 , and see if bold works for you, then?

@jdanielmourao  Works with different font.

That's because it's a variable font, where they've fused regular and bold together, but didn't incorporate italic/slant parameters in it, hence why is has 2 variants. iA Writer Quattro S is not a variable font, so they need to divide every weight and style into separate font files. I actually forgot about the S variant. You could set that as your font, and have pretty much the same experience. Sorry, long day today!

authors: jdanielmourao lavaldi ujjwal3067

repo: jdanielmourao/obsidian-sanctum


text:
fix twitch.tv url

changed from account deactivation page to account deletion page

Confirmed, thanks for your contribution!

authors: Nightfirecat olumby

repo: jdm-contrib/jdm


text:
Add arcor.de

as requested by https://github.com/justdeleteme/justdelete.me/pull/676

@rugk Thanks for the hint! I changed it to https. The https version redirected to https, though :)

Thank you @guerda and @rugk

authors: guerda tupaschoal


text:
Feature request: Add auto copy when plain text bitcoin address is clicked.

User clicks Address Actions > View Address > clicks the displayed Bitcoin address and it automatically copies that address.  Would be dank on xchain too!  Thanks JDog

added a 'Copy' button to the 'View Address' page to make copying address to system clipboard easier.
commit d858463

authors: ShawnLeary jdogresorg

repo: jdogresorg/freewallet-desktop


text:
Remove deprecated methods

Modify the deprecated .hover() method in src/deprecated/event.js so that it does not rely on other deprecated methods: .mouseenter() & .mouseleave(). Use .on() instead.

Pulled Repository content

Identified the files that needs to be modified and solution plan is created

authors: jdoodle-ai lucashakewill

repo: jdoodle-ai/jquery


text:
Confusing output of mise doctor regarding plugins

Describe the bug
mise doctor told me:

3 warnings found:

plugin java overrides a core plugin
plugin node overrides a core plugin
plugin python overrides a core plugin

No problems found

So I uninstalled those plugins, and how I get errors:

mise WARN  Error listing bin paths for vfox:node@22.11.0: Invalid version: node: relative URL without a base
mise WARN  Error listing bin paths for vfox:node@23.3.0: Invalid version: node: relative URL without a base
1 warning found:

plugin node overrides a core plugin

2 problems found:

plugin node is not installed
unused shims are present, run mise reshim to remove them
Unused shims: corepack, node, npm, npx

At the same time, I can't re-install the plugin:
 ❯ mise plugins install node
mise ERROR node is a core plugin and does not need to be installed

It's not clear to me what I should do to get a clean setup.
To Reproduce
Not sure about the starting state; here is what I did:
mise self-update
# v2024.11.29 --> v2024.11.36
mise list
mise up
mise doctor
# 3 warnings
mise plugins uninstall java
mise plugins uninstall node
mise plugins uninstall python
mise doctor
# 3 warnings, 2 problems

Expected behavior
mise doctor tells me how to mitigate warnings/problems
mise doctor output
version: 2024.11.36 linux-x64 (0461143 2024-11-29)
activated: yes
shims_on_path: no

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Fri, 29 Nov 2024 10:31:35 +0000
  Rust Version: rustc 1.82.0 (f6e511eec 2024-10-15)
  Profile: release

shell:
  /usr/bin/fish
  fish, version 3.7.1

dirs:
  cache: ~/.cache/mise
  config: ~/.config/mise
  data: ~/.local/share/mise
  shims: ~/.local/share/mise/shims
  state: ~/.local/state/mise

config_files:
  ~/.config/mise/config.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
  maven   https://github.com/mise-plugins/asdf-maven.git#c872214
  poetry  https://github.com/mise-plugins/mise-poetry.git#c1aea14
  usage   https://github.com/jdx/mise-usage.git#fe3888a
  uv      https://github.com/asdf-community/asdf-uv.git#8155fc5

toolset:
  asdf:usage@1.3.3
  asdf:uv@0.5.5
  core:python@3.13.0
  core:ruby@3.3.6

env_vars:
  MISE_SHELL=fish

settings:
  experimental  true ~/.config/mise/config.toml
  pipx_uvx      true ~/.config/mise/config.toml

1 warning found:

1. plugin node overrides a core plugin

2 problems found:

1. plugin node is not installed

2. unused shims are present, run mise reshim to remove them
   Unused shims: corepack, node, npm, npx

Additional context
 ❯ mise list
java    temurin-21.0.3+9.0.LTS
java    11.0.2
java    21.0.2
maven   3.9.9
node    22.11.0
node    23.3.0
poetry  1.8.4
python  3.12.7
python  3.13.0                  ~/.config/mise/config.toml 3.13
ruby    3.3.6                   ~/.config/mise/config.toml 3.3
usage   1.3.3                   ~/.config/mise/config.toml latest
uv      0.5.5                   ~/.config/mise/config.toml latest

Apparently, re-installing all node versions is a workaround:
 ❯ mise uninstall node --all
 ❯ cd some/dir/with/node/in/mise/config
 ❯ mise up
# mise node@22.11.0 ✓ installed
 ❯ mise doctor
# ✅

there was a bug around this that has been reported several times

Ah, sorry, I saw some similar issues but didn't realize they were in fact the same. Thanks!

authors: jdx reitzig

repo: jdx/mise


text:
Bundle libsodium

Proof of concept. However this is blocked by https://github.com/jean-airoldie/zeromq-src-rs/pull/9 which is blocked by https://github.com/sodiumoxide/sodiumoxide/pull/344.

We also document this feature and benchmark performance.

Turns out tweetnacl is not meant to be used for production. So we have to bundle libsodium.

Closed un favor of #120

repo: jean-airoldie/libzmq-rs