[Feature]: automatic mockClear prototype methods inside automatically mocked Class

🚀 Feature Proposal
I was wondering if, when creating an automatic mock of a class, it would be possibile to clear automatically also the prototype of the mocked class when calling the Class mockClear method. See example.
Motivation
I think this would be a great enhancement since every time I mock automatically a Class I get for free the mockClear on the constructor and the static methods but, while I can monitor each method called in any instance of the class, I should call each method mockClear in order to reset each method call. When I do not want to worry about which method I'm testing in each test suite it can be frustrating to call mockClear each time on the prototype and on each involved method. This way calling mockClear on the automatic mocked class allows me to spy on the prototype without worrying abount resetting each time the prototype functions.
Example
jest.mock('../MyClass')
const MyClass = require('../MyClass')

// ...
beforeEach(() => {
     // this would clear the prototype too
     MyClass.mockClear()
     // I should be able to avoid this (for each method of the class):
     MyClass.prototype.start.mockClear();
})

// already working:
it('should have been cleared', () => {
    const instance = new MyClass()
    instance.start()
    expect(MyClass).toHaveBeenCalledTimes(1)
    expect(MyClass.prototype.start).toHaveBeenCalledTimes(1)
})

// not working if not executed alone:
it('should have been cleared', () => {
    const instance = new MyClass()
    instance.start()
    expect(MyClass).toHaveBeenCalledTimes(1)
    // it's not cleared: MyClass.prototype.start
    expect(MyClass.prototype.start).toHaveBeenCalledTimes(1)
})

Pitch
Since it involves the jest.mock implementation.

Not stale..


Steps do not work

I followed the steps displayed here but my persistent volume claim is not binding. I'm using kubernetes 1.10.5

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a57e48b4-dc33-0b9d-b773-42ce7d2bffd0
Version Independent ID: e912ac2d-cf6a-0b54-4697-1940b1270874
Content: Use Azure File with AKS
Content Source: articles/aks/azure-files-dynamic-pv.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Never mind i found it storage account was in the wrong resource group

Thanks for the update @YvonneArnoldus


Fix an issue where JsonUtils produces a bad error message

CascadiaSettings relies on getting a JsonUtils::DeserializationException from the various JSON Utility functions, and then formatting that into an error message. Well, DeserializationException tries to include an object representation in its what() message . . . and generates an exception trying to do so. CascadiaSettings never gets the DeserializationException, and displays a weird message.
Fixes #14373

Before: bad
After:

@msftbot merge this in 7 minutes

@msftbot merge this in 10 minutes


Cannot resolve module 'preact-compat/lib/ReactMount'

When I try preact-compat with https://github.com/freddyrangel/playing-with-react-and-d3/tree/master/finished I got
ERROR in ./src/index.jsx
Module not found: Error: Cannot resolve module 'preact-compat/lib/ReactMount' in /Users/katopz/git/playing-with-react-and-d3/finished/src
 @ ./src/index.jsx 1:338-369

Maybe it's not support?

Yup, one of my todo list items :)


[WIP] Station hierarchy

Resolves #292

bbox for testing: http://localhost:4200/#/stops?bbox=-122.39740490913391%2C37.78669932495591%2C-122.38633275032042%2C37.792659800376455

Icons defined in components/stop-map/component.js
var stopStationIcon = L.icon({
   iconUrl: 'assets/images/search-active.png',
   iconSize: [36, 54],
   iconAnchor: [18, 54],
   popupAnchor: [0, -54]
 });


Disable returning source document

related-to: https://github.com/astronomer/ask-astro/issues/80

why don't we just hide these from the UI?

I think we won't be going ahead with the PR as we want to include sources in 28th Nov release


🚀 Link improvements

(No issue)
Adds a few improvements for link insertion.

Sanitises links
Toggles a link so that if there are existing links in the selected text it removes them.

Coverage remained the same at 75.035% when pulling 0f6cb8813f247cab685bb975806767354e62f32b on disordinary:link-improvements into 9adb99058c0731fe1e50f5e57006058e86d1c47b on TryGhost:master.


[OCM] sharee cannot access the federation shares via normal webdav paths

Steps to reproduce

Create a federation share of a folder (remoteFolder)
as sharee, try to do PROPFIND

curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/files/admin/Shares/remoteFolder' -uadmin:admin -vk

curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/spaces/{shares-space-id}/remoteFolder' -uadmin:admin -vk

< HTTP/1.1 404 Not Found

But the share is accessible using mount-point-id and remote-item-id
# mount-point-id
curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/spaces/89f37a33-858b-45fa-8890-a1f2b27d90e1$6953d7bc-1c57-4f2a-8977-10bdfbcb2ff6' -uadmin:admin -vk

# remote-item-id
curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/spaces/89f37a33-858b-45fa-8890-a1f2b27d90e1$6953d7bc-1c57-4f2a-8977-10bdfbcb2ff6!Lw%3D%3D' -uadmin:admin -vk

< HTTP/1.1 207 Multi-Status

Since this is a remote share, maybe the behaviour is expected.
Related: https://github.com/owncloud/web/issues/11753
Web using remote id: https://github.com/owncloud/web/pull/11758

I can confirm. cc @rhafer

curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/files/admin/Shares/remoteFolder' -uadmin:admin -vk

curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/spaces/{shares-space-id}/remoteFolder' -uadmin:admin -vk

Both of these can only work for "normal" user and group shares. As requests to these paths are handled by the sharestorageprovider. Federated shares are handled by a different storageprovider.
AFAICS there is currently no way to list received ocm shares via webdav (or access them by mount path). You can get the id via sharedWithMe on  the graph service (like web does)
curl -k -u moss:vista  'https://ocis-federation.owncloud.test/graph/v1beta1/me/drive/sharedWithMe'

Then take the id values of  the embedded remoteItem.

yes, remoteItem id from sharedWithMe and mount-point id from me/drives both works.
If this is expected and there will be no furtuher improvements/changes regarding this then we can close this one.


ESM target that is compatible with node

💡 Feature description
I maintain several libraries (one big one in particular), with the following constraints:
We publish a single ESM build that runs directly without any further transformation in the following environments:

All modern browsers
node
bun and similar environments that implement most browser APIs
bundlers (i.e. can be transformed by bundlers into code that stays compatible with the above environments)

... given the following two assumptions:

Package imports are supported (e.g. using import maps or a mapping to node_modules)
new URL(…, import.meta.url)[^1] is correctly resolved or transformed for relative source files (particularly, for worker entry points and WASM entry files).

To this end, we are happy to include dynamic workarounds and imports for node compatibility, but we do not want to publish separate builds for different environments[^2]. In the past, it was reasonable to make assumptions like "require means node, import means browser", but this is not the case anymore and all environments are converging on compatible functionality.
[^1]: In the future, this should be import.meta.resolve(…). Browsers have supported this for the better part of a year, but most bundlers still need to. As far as I'm concerned here, new URL(…, import.meta.url) is a backwards-compatible version of import.meta.resolve(…).
[^2]: I've learned the hard way that I'd much rather deal with the challenge of maintaining a single published build like this, compare to publishing multiple builds and having to figure out which one to debug for a given report issue.
To that end, could I ask for an ESM target that works both in browsers and node directly? I believe this is possible in node using e.g. createRequire.
I'd be happy to contribute code to support this, if someone would indicate that it would be appropriate for a PR.

I'd be happy to contribute code to support this, if someone would indicate that it would be appropriate for a PR.

I found that I was able to modify the output of --target web by replacing:
        input = fetch(input);

… with:
        try {
            input = await fetch(input);
        } catch (e) {
            if (!(e instanceof TypeError)) {
                throw e;
            }
            input = await (await import("node:fs/promises")).readFile(input);
        }


Permission issue on logger file

Today i got

error.

I have currently solve this issue by granting access to local user access by:
chmod +x ngrok_logger.txt  and one more file so i don't get this error for ttgo logger by
chmod +x logs.txt


add ArchLinux steps

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

Hi, @noraj. Though I appreciate the PR, I'm not going to merge this. Arch user are probably already familiar with how to search and install Arch packages, and I'm hesitant to point to a package repro that we don't maintain or support.


Support tensordot and reduce for SwizzleArray

Issue #474
Hi @willow-ahrens,
This PR contains support for tensordot and reduce operations for SwizzleArrays.
Should FiberOrBroadcast be renamed to also indicate that is considers SwizzleArrays?

Exactly - CI should be green now. Could you make a new release once we merge it? Then in finch-tensor I should have elem-wise and reduction ops running for eager and lazy mode.
Note to myself, and what you mentioned last week - I need to revisit handling scalars. Should there be a Tensor(scalar) or should we keep it as just Julia/numpy scalars?

Could you bump the version?—WillowOn Mar 18, 2024, at 3:45 PM, Mateusz Sokół @.***> wrote:
Exactly - CI should be green now. Could you make a new release once we merge it? Then in finch-tensor I should have elem-wise and reduction ops running for eager and lazy mode.
Note to myself, and what you mentioned last week - I need to revisit handling scalars. Should there be a Tensor(scalar) or should we keep it as just Julia/numpy scalars?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Secure cookie not working.

How do you set a secure cookie?
When I inspect the cookie in Cookie Inspector it says the cookie is not secure. This is the call.
this.cookieService.put("username", username, {secure: true})

Why was this issue closed? I have the same issue!

How did you solve the problem?
When I put {secure: true} it simply does not generate the cookie.

Hey man,
I can't remember since I'm not working on that project anymore but fairly certain I went to a new library.
Sent from my iPhone

On Feb 28, 2017, at 5:22 PM, Yuri Fontella<EMAIL_ADDRESS>wrote:
How did you solve the problem?
When I put {secure: true} it simply does not generate the cookie.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Does not build in Release Mode: ../../third_party/dart/runtime/vm/compiler/backend/il.h: 999: error: unreachable code

Hi,
I'm having an issue after upgrading to moor_ffi 0.6.0 on the current stable version of flutter.
I cannot build my app in release mode. Debug mode works fine. I also happens on a very basic project and can be reproduced in the integrations tests of moor.
To reproduce, navigate to:
moor/extras/integration_tests/flutter_db
And try to build the app in release mode:
flutter build apk --release -t lib/moor_ffi.dart
! moor 3.1.0 from path ../../../moor
! moor_flutter 3.0.0 from path ../../../moor_flutter
Running "flutter pub get" in flutter_db...                          0.6s
You are building a fat APK that includes binaries for android-arm, android-arm64, android-x64.
If you are deploying the app to the Play Store, it's recommended to use app bundles or split the APK to reduce the APK size.
    To generate an app bundle, run:
        flutter build appbundle --target-platform android-arm,android-arm64,android-x64
        Learn more on: https://developer.android.com/guide/app-bundle
    To split the APKs per ABI, run:
        flutter build apk --target-platform android-arm,android-arm64,android-x64 --split-per-abi
        Learn more on:  https://developer.android.com/studio/build/configure-apk-splits#configure-abi-split
[!] Your app isn't using AndroidX.
    To avoid potential build failures, you can quickly migrate your app by following the steps on https://goo.gl/CP92wY.
../../third_party/dart/runtime/vm/compiler/backend/il.h: 999: error: unreachable code
Dart snapshot generator failed with exit code -6
../../third_party/dart/runtime/vm/compiler/backend/il.h: 999: error: unreachable code
Dart snapshot generator failed with exit code -6
Target android_aot_release_android-arm64 failed: Exception: AOT snapshotter exited with code -6
Target android_aot_release_android-x64 failed: Exception: AOT snapshotter exited with code -6
build failed.

FAILURE: Build failed with an exception.

* Where:
Script '/Users/kami/development/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 882

* What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.
> Process 'command '/Users/kami/development/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 23s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                      24.8s
Gradle task assembleRelease failed with exit code 1

The iOS build fails with a similar error.
flutter doctor:
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.1, on Mac OS X 10.15.4 19E287, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.6)
[!] IntelliJ IDEA Ultimate Edition (version 2019.1.2)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.45.0)
[✓] Connected device (1 available)

I also tried it in the current flutter beta version, same error.
I'm not quite sure if that's really an issue with moor or a bug in the build system - Do you have any clues why this might happen? If not, I'll open an issue in the flutter project.

I can reproduce this by running dart2native test/vm_test.dart, so it's not a Flutter bug. It's definitely a bug in Dart, I'll try to come up with a smaller repro.

I tried to poke around a bit, but I couldn't find a much smaller repro. Interestingly, aot-compiling some test files inside moor_ffi doesn't fail, only the whole integration test. https://github.com/dart-lang/sdk/issues/41971

Confirm the issue.

I am running into this as well, 2 apps don't build any more so I have to stay on 3.0.0 for now.

Same here, actually solved by downgrading to moor_ffi: "0.5.0".

I was scratching my head for a while with this one too.  moor_ffi 0.5.0 still works.

Had this issue for 2 days and finally realised it's because of moor_ffi 0.6.0... After downgrading to 0.5.0 everything works fine.

Same issue, fixed by downgrading moor_ffi to 0.5.0

Same issue here, fixed by downgrading moor_ffi to 0.5.0

This is now fixed on the flutter master branch

Hopefully they pick this into stable.

I requested it in https://github.com/flutter/flutter/issues/58631 . If this gets enough thumbs up, maybe thell'l hotfix it.

This is now fixed on flutter beta branch, only one more branch to go.

I meet the same problem. But how to downgrade moor version in linux flutter sdk ?

If I'm also having https://github.com/simolus3/moor/issues/420, the only solution is to use beta, correct?

@szotp Yes

Steps to fix them as of today with latest update on Jul 29, 2020:

Update Moor Package to v3.3.0
Update Moor_Generator to v3.3.0
Install 'sqlite3_flutter_libs' package (as updated in the docs)
Remove moor_ffi package as it is deprecated now.
Change imports from moor_ffi to package:moor/ffi.dart.
Check installed versions for path, path_provider and build_runner using flutter pub outdated

Clear build cache and build runner cache.
Build production app now without any errors.

Dart 2.9 or Flutter 1.20 contains the fix.


implement will_topic configuration capablity

Now you can set any strings as a will topic.
Unless specified within broker clause of configuration file, default value is set as /{gateway name}/will

To make commit log readable, this PR is closed.


ListsApi and FoldersApi Implementation

Hello,
There was some reason to remove FoldersApi and ListsApi classes from Init files?
Both implementation are still on master branch:
https://github.com/sendinblue/APIv3-python-library/blob/master/sib_api_v3_sdk/api/folders_api.py
https://github.com/sendinblue/APIv3-python-library/blob/master/sib_api_v3_sdk/api/lists_api.py
The 7.6.0 update have broken some of our pipelines.

Any update ?


Feature/eslint config package

adds shared .eslintrc.js and tsconfig.json to the monorepo root for the packages to extend and use. The only additional configuration is in frontend that also extends eslint react plugins and rules.
removes unused packages ipfs-worker/, and sdk-demo-api/ (in favor of api/ which is basically the same thing)
most of the modified files are due to eslint --fix changes
merges PR 541 into this one

@shanefontaine quick update; the feedback has been implemented (ie hoisting root files), and now figuring out the broken builds

Is it expected that when building core, with npm run clean && npm run build, it doesn't generate the top level dirs networks/, addresses/, metadata/, etc? Would not having those dirs break path imports, such as const { networks } = require( '@hop-protocol/core/networks')

Remove custom type definitions (our own types dirs). Simplifies tsconfig.json by removing the need to define them but also needing to redefine the defaults, like node_modules/types. Most updated packages have correct types. Added // @ts-expect-error to a few imports that did need it. In theory, IMO if something doesn't have types we should be hesitant to use it as that means it is unmaintained and can cause headaches elsewhere.

In public packages (core, sdk), use the files option in package.json as an NPM allowlist (published files must be included in files and not excluded in .npmignore).

Use rm -rf for NPM scripts instead of rimraf. Removes possible debugging steps at the cost of compatibility.

I recognize that this breaks compatibility with non-Unix machines. However, (1) my understanding is that WSL is used by a decent amount of people on Window's these days (even more-so in OS world) and (2) I believe many other parts of the packages would not work with non-Unix, such as paths and env vars. I think npx rimraf makes sense for a lifecycle script, but can be reintroduced if/when we non-Unix-ify the repo.
I hit a case where rimraf wasn't working because I had stopped an install halfway through. node_modules knew about rimraf but didn't have all of its deps. In this case, npx used my node_modules rimraf instead of global, but it was corrupted. npx wouldn't ever try global because it still "saw" it locally. Error message that was difficult to understand.

@miguelmota final commits have been pushed:

Updated to pnpm
Simplify/standardize scripts and deps + general cleanup

@miguelmota final round of changes. Ready to merge at any time now.

Remove binary from hop-node. Replaced with ts-node for local build/test and node for prod and docker.

IIUC binaries let someone run hop-node without a node env and w/o docker. I am under the impression that nobody does this (at this time). Current options to run hop-node is either:

Pull repo, build, run
Pull docker, run (build was already completed by CI prior to pushing to dockerhub)

IIUC the current bin calls into the build dir but instead should be using a fully compiled bin instead. If reintroduced, consider using nexe or some package that builds an executable bin.
Fun fact: I believe the latest version of node has experimental binary support built-in (though likely won’t be stable for many years)

Use swc for hop-node compile instead of Native Typescript for a 3.7x increase (5.39s → 1.46s) in hop-node build time (useful during dev and testing).

Generally goes against the goal of using natives/defaults, but feels practical in this case:

Meaningful speed increase (3.7x vs native transpileOnly and 6.7x vs how we were doing it)
Suggested as a main option by ts-node when using ts-node
No config (only an NPM package to download)

RM hop-node and stats-worker package_check.sh since I believe they are now unused

(Can be reverted) (SDK only) Use esbuild instead of babel for bundling + CDN

Gets rid of 65% of devDeps in SDK (40% of total deps) for faster / safer / easier installs & builds.

Remove binary from hop-node. Replaced with ts-node for local build/test and node for prod and docker.

That seems fine. I think the Dockerfiles need to be updated to reflect that change.

IIUC the current bin calls into the build dir but instead should be using a fully compiled bin instead. If reintroduced, consider using nexe or some package that builds an executable bin.

I think that the bin/ folder in node apps are a convention to denote the entrypoint for the cli.
For example, the lodestar client has bin/lodestar.js and in package.json they have "bin": {"loadestar": "bin/loadstar.js"}} for global command. In their Dockerfile they have the bin path as the entrypoint; ENTRYPOINT ["node", "./packages/cli/bin/lodestar"].
In linux, the /bin folder means it contains executables and doesn't necessarily have to be compiled binary code. For example, /bin/pip is a readable python interpreted program (starts with #!/usr/bin/python) and it's not complied binary.

Use swc for hop-node compile instead of Native Typescript for a 3.7x increase (5.39s → 1.46s) in hop-node build time (useful during dev and testing).

Is swc only used during start script and not pnpm build?

(Can be reverted) (SDK only) Use esbuild instead of babel for bundling + CDN

I see that you removed the sdk CDN docs from README and the sdk build (pnpm build at the root) isn't generating packages/sdk/hop.js which would break existing cdn links. Is that expected? I think it's important to make the sdk as widely available as possible to stay competive. For example, ethers has cdn links/examples in docs

I think the Dockerfiles need to be updated to reflect that change.

Updated with 9768d45da4759be33f811fdc4a38a7870b158b4f. I believe that works, but plan on doing a quick pass on the Docker stuff today, most just for my understanding.

bin

That is interesting and I did not know that. I thought bin 100% implied only binary files but see now I was incorrect. Thanks for the info 🙏

Is swc only used during start script and not pnpm build? Seeing tsc being used instead of swc on build.

Good catch, I didn't realize this. I just went to add it but then realized that it (understandably) completely ignores tsconfig and uses its own config that can be modified. I'm not too stoked on the mental overhead of "every package in Hop follows tsconfig except hop-node". But now also don't love that our local build/test is different than prod build 🤔 . Let me think about this but if you have thoughts I'm down.
One note is that there is a native way to do this too. Our develop branch builds are ~9.5s and our swc builds are 1.46s. However, our develop branch with --transpileOnly (i.e. don't look for type errs during build) takes 5.39s. Don't think that is a better solution, but think it is interesting.

I see that sdk CDN docs from README were removed

I had removed bundling completely for a bit and removed from the README at that time. I dove in a bit and now have a better understanding so I added the bundle back but forgot to reintroduce to the README.

swc

Maybe there's a way to autogenerate the swc config from tsconfig, such as creating a small script to map tsconfig options to swc config options and output to .swcrc. I like the speed improvements and wouldn't be opposed for hop-node to use a different build system.


[HELP] The localhost with the port does not work for me.

Hello, excuse my ignorance but I have tried to put the Alpha 3 in Docker-compose but it does not work for me, I would like to know if there is another way to install it, when installing it I enter with the port localhost:5690 but it does not enter, any help please, best regards.
CONTAINER ID   IMAGE                                  COMMAND                  CREATED              STATUS                          PORTS     NAMES
3af07d4d1a66   ghcr.io/wizarrrr/wizarr:v3-alpha-vue   "sh -c 'nginx && gun…"   About a minute ago   Exited (3) About a minute ago             agitated_banach

Could you get it to work?

Please use ghcr.io/wizarrrr/wizarr:v3-beta

Please use ghcr.io/wizarrrr/wizarr:v3-beta

2.6 GB? 💀

Wait I messed something, didn't I

We have had some issues with dialing in the right Github Actions Workflow for building out images, we are also trying to get image sizes down aswell

This is fixed in the latest ghcr.io/wizarrrr/wizarr:latest build


Pages or stores?

In the screenshot below, there is a screen listing "Pages". At the same time, I'm prompted to search for "stores". What is the difference between pages and stores? Can a store have many pages? (It seems that on my personal store I only have one page, labelled "My Page".)

I think the idea is to be able to view the pages of users besides just stores (ex buyers). Problem is there isn't any good way to get a list of everyone in the network. It would probably be better just being labeled stores IMO.

Agreed. Stores feel more semantically meaningful than pages.

Some nodes will only offer "Moderator services", some will be "Stores", others will be "basic users" and some will be all 3. We need a single high level term that can reference all 3 different types. "Stores" doesn't work here because there are other pages in the network that need to be accessible in discover mode.
Also, "check out my Page on OpenBazaar" — is something a store, moderator or basic user could say to their friends.
As of now, we use the term "Page" all over the place:

@drwasho please chime in, I know you've put a lot of thought to this as well.
Also, it appears that a recent change messed up the filter drop down on the "Pages" tab. The options should be "Stores", "Moderator services" and "Basic users", not "Stores I follow" and "All stores".

@morebrownies: That makes sense. I imagine that, over time, clients will specialise to cater for one specific population: buyers, sellers or moderators. At this stage, having all three together is understandable, but somewhat awkward.

My thinking is that most users will not want to see other buyers (there's almost nothing there to look at and the list will be woefully incomplete and most will be offline anyway).
They might want to see moderators, but there are also other parts of the app where they can find moderators.
And they definitely want to see stores.
So the term pages lumps all three together whereas the weight of what it's used for is only stores.

Agreed. I had the select dropdown defaulted to "stores" because of the same logic. If they do not care to see the other types, they could just ignore the dropdown. No harm in having them in there though.

We're also future proofing here because the role of users that have a permanent online presence but aren't stores will emerge as we roll out the Feed and other social features.
I agree with Wolf that defaulting to Stores is a must to fit with the most popular use case.


Various errors are thrown that are uncatchable at the call site of nats.ws/connect

Hi,
I noticed that nats.ws sometimes throws an error that cannot be caught at the call site.
For example, when I call connect with parameters reconnect: false and timeout: 5 to force a timeout error, I get an error log despite wrapping connect in try-catch:
Unhandled Promise rejection: TIMEOUT ; Zone: <root> ; Task: Promise.then ; Value: NatsError: TIMEOUT

Notably, if I wrap the connect call like this:
catchConnect = async () => {
    try {
        nats.connect({ reconnect: false, timeout: 5 })
    } catch (err) {
        console.log('caught an error')
    }
}

I get both, the Unhandled Promise rejection and the log caught an error in the console.
This kind of unhandle promise rejection occurs for example in:

https://github.com/nats-io/nats.deno/blob/07405ec3f88ff8a84c0b3a6b8e91c5cfd4a1e671/nats-base-client/util.ts#L132
https://github.com/nats-io/nats.deno/blob/07405ec3f88ff8a84c0b3a6b8e91c5cfd4a1e671/nats-base-client/protocol.ts#L271

@cuddlecake what version are you using? Can you please try with 119? npm install nats.ws@latest.
The issue with the error being thrown in an unhandled context was solved here:
https://github.com/nats-io/nats.deno/pull/91
Also, the timeout of 5ms is really not right, as the client will never finish the connection that fast.
Finally, yes there's another issue lurking here: https://github.com/nats-io/nats.ws/issues/80

We are using 1.0.0-119 (recently upgraded from 1.0.0-17.
Ever since the update, these errors occur.
We're not actually using 5ms timeout in production, I have omitted other config parameters for brevity, but here's the full connect call parameters that we use:
nats.connect({
     servers: endpoints.updateUri,
     name: this.connectionName(this.viewerId),
     authenticator: nats.jwtAuthenticator(token),
     pingInterval: 30_000, // default: 120_000
     maxPingOut: 5, // default: 2
     reconnect: false,
     maxReconnectAttempts: 0, // default:10
})

Might it also be possible that those errors also occur during NatsConnection.subscribe? I can't really tell from the stacktrace whether it's from connect or subscribe (we only use connect and subscribe) because neither is mentioned in the stack trace.

@cuddlecake the error is always a timeout?

can you await nc.closed() and see what error you get there?

One more - can you run nats-server -DV on the server you are connecting to and see if the log exposes something interesting?

Is the scenario, you connect once, and then on reconnect, and then the timeout surfaces unhandled?
You can track what the client is doing with:
(async () => {
  console.info(`connected ${nc.getServer()}`);
  for await (const s of nc.status()) {
    console.info(`${s.type}: ${JSON.stringify(s.data)}`);
  }
})().then();

not seeing the unhandled - perhaps I am missing something, but:
dialLoop is called from connect: (https://github.com/nats-io/nats.deno/blob/main/nats-base-client/protocol.ts#L342).
which if it triggers rejects the connection.
And from disconnected (https://github.com/nats-io/nats.deno/blob/main/nats-base-client/protocol.ts#L229), which also handles it if fails.
dial, could also toss, but that is awaited: https://github.com/nats-io/nats.deno/blob/main/nats-base-client/protocol.ts#L314.
I am going to try adding some of the options you are using...

@cuddlecake the error is always a timeout?

The types of errors we find in Sentry that are related to nats.ws are:

Unhandled Promise rejection: An invalid or illegal string was specified, this one occurs only on Firefox
Unhandled Promise rejection: Failed to construct 'WebSocket': The URL '<redacted>:4222' is invalid., this is the Chromium variant of the first error. I have redacted the string, but it's basically just ip-address:port, without the wss:// scheme. I'm not sure why this error occurs because the URI we insert is shaped like this: ${protocol}://${window.location.host}/api/update, where protocol is "wss:" or "ws:". (This might also be a completely different issue, since we're using a reverse proxy)
Unhandled Promise rejection: TIMEOUT, I am not sure where this originates, because I don't receive a good stack trace here
Unhandled Promise rejection: undefined ; Zone: <root> ; Task: Promise.then ; Value: NatsError NatsError, this usually occurs  after a couple of unhandled TIMEOUT errors. This originates in the socket error callback.

I assume the timeout errors occur in low-connectivity environments or when the device is going offline (it's used extensively with mobile devices).

can you await nc.closed() and see what error you get there?

Not sure where I should await this, because the NatsConnection handle is only returned when the connection succeeds. The timeout error occurs during the connection attempt. Same for tracking nc.status()`
Some other things about how we use nats.ws:

We use nats.ws with Angular, so we also use zone.js which patches the global Promise. I will try to implement the connect outside of the Angular zone, that might just be the fix.
We do not listen to .closed() and do not listen on error events. Instead, we check every 4 seconds if the connection isClosed() and open a new one (this was the more reliable approach for 1.0.0-17 on iOS because the 'closed' event was not handled when the app was in the background).

If running the connect outside of ngZone doesn't work, I'll try to create a reproduction repository, but I won't be able to reproduce our entire stack (including distributed nats, websocket proxy, reverse proxy)

@cuddlecake the error is always a timeout?

The types of errors we find in Sentry that are related to nats.ws are:

Unhandled Promise rejection: An invalid or illegal string was specified, this one occurs only on Firefox

Unhandled Promise rejection: Failed to construct 'WebSocket': The URL '<redacted>:4222' is invalid., this is the Chromium variant of the first error. I have redacted the string, but it's basically just ip-address:port, without the wss:// scheme. I'm not sure why this error occurs because the URI we insert is shaped like this: ${protocol}://${window.location.host}/api/update, where protocol is "wss:" or "ws:". (This might also be a completely different issue, since we're using a reverse proxy)

If this issue happened before a connect, the client didn't have an URL and defaulted - this is the issue fixed in #80. I believe you have a client that is trying to connect without specifying a server - the base library was adding default host without going through the motions of converting to an URL. This is fixed in nats.ws@latest. - unless you are actually running your ws server on 4222, that is the issue fixed.

Unhandled Promise rejection: TIMEOUT, I am not sure where this originates, because I don't receive a good stack trace here
Unhandled Promise rejection: undefined ; Zone: <root> ; Task: Promise.then ; Value: NatsError NatsError, this usually occurs  after a couple of unhandled TIMEOUT errors. This originates in the socket error callback.

I assume the timeout errors occur in low-connectivity environments or when the device is going offline (it's used extensively with mobile devices).

Wondering if the device is not properly populating the event message - or is simply calling it without an argument?
https://github.com/nats-io/nats.ws/blob/master/src/ws_transport.ts#L133

can you await nc.closed() and see what error you get there?

Not sure where I should await this, because the NatsConnection handle is only returned when the connection succeeds. The timeout error occurs during the connection attempt. Same for tracking nc.status()`
Some other things about how we use nats.ws:

We use nats.ws with Angular, so we also use zone.js which patches the global Promise. I will try to implement the connect outside of the Angular zone, that might just be the fix.

interesting isn't the reason for zone.js to give you a stack trace - surprised that it is not providing more info.
So one interesting bit, not sure if this is related - the connection process has several promises that must resolve. Some of them are negative (such as the client took too long to handshake), the other is positive, where the PONG protocol message from the server was received and processed. These are used in a Promise.race() which results in either the timeout or the pong resolving. Wondering if the timeout you are logging is simply the timeout failing to resolve AFTER the connection resolved. Since the connection code takes the race, it works correctly, but there are two microtasks that are being queued, and it is possible that one resolves as the other is fails...

We do not listen to .closed() and do not listen on error events. Instead, we check every 4 seconds if the connection isClosed() and open a new one (this was the more reliable approach for 1.0.0-17 on iOS because the 'closed' event was not handled when the app was in the background).

OK - was just clarifying that this is just a first connect issue.

If running the connect outside of ngZone doesn't work, I'll try to create a reproduction repository, but I won't be able to reproduce our entire stack (including distributed nats, websocket proxy, reverse proxy)

One more if you are running via a reverse proxy, is your client ignoring server gossip?
Since you didn't specify whether you were setting one or more servers on your connect, I am wondering if you are also trying to connect to servers that are gossiped but not reachable.
On connect, the server will send information about the cluster. If the client is behind a proxy, the information that is gossiped is NOT reachable (it is however parsed correctly). Likely you'll want to set the option ignoreClusterUpdates https://github.com/nats-io/nats.ws#connection-options.

Thank you for your advice and help, by the way.

Likely you'll want to set the option ignoreClusterUpdates

I set ignoreClusterUpdates to true now, so I think the problem with bad WebSocket URLs will go away. Will observe whether the issue is still getting logged in Sentry.
FYI, for the connect parameter servers I only supplied the reverse-proxy URL like this:
connect({ servers: 'wss://my-url/path' , /* not the actual URL, and omitted other params for brevity */ })

interesting isn't the reason for zone.js to give you a stack trace - surprised that it is not providing more info.

It does provide a stacktrace, the formatting is just bad and sourceMaps are not applied properly, so it's difficult to inspect. Off-topic: I rue the day I ever decided to use Angular for anything.
In any case, when I run the connect code outside of zone.js using NgZone.runOutsideAngular, I get less of those uncatchable errors, so I assume for now that zone is the culprit. I still get an error for the very first connection attempt when I set timeout to 5 milliseconds, but the others are fine. Might also have to do with the fact that I'm using RxJS to manage reconnects (since I'm not using the nats.ws reconnect options), and RxJS is not entirely compatible with zone.js.

So one interesting bit, not sure if this is related - the connection process has several promises that must resolve. Some of them are negative (such as the client took too long to handshake), the other is positive, where the PONG protocol message from the server was received and processed.

It's hard to debug these issues on my end due to them mainly appearing on end-user's devices in production, so for now, I think this issue can be closed, since it seems to be Angular specific. I will create new issues when I find a way to isolate and reproduce problems.

The 5ms timeout should be rejecting the connection should be a given, and that should be rejecting the connection properly.
I would like you to verify if the devices are generating some possible unsafe conditions on the error handler for the clients. If that is the case I can protect it further (possibly just add additional assertions on the error event handling.
I do think that you should rely on the promises for closed() and the reconnect behavior of the client - but you know your environment better that me :)

I do think that you should rely on the promises for closed() and the reconnect behavior of the client

I would prefer to use the reconnect behaviour of the client, but my problem is that we use a JWT for authorization (accessToken with limited lifespan) that is provided by a Promise, ensuring that it always resolves to a valid accessToken (either from local storage, which is the usual case, or from remote if a refresh is required). But, the authenticator option does not allow async (https://github.com/nats-io/nats.ws/issues/69) so I can't use that.
I could keep a local accessToken in my socket code, which I try to keep fresh by requesting a token periodically, but if the connect attempt is made with an invalid token even once, I think reconnect will also stop, and I'd have to restart reconnects manually anyway.

yes the authenticator cannot really do an async for that - because the authenticator is supposed to return quickly (before the server closes the connection). But that doesn't prevent your client from initializing pulling a JWT and then creating a timer that refreshes the JWT before it expires. If you get a rejection more than once the client will close, so then at that point you go through your startup sequence. Your JWTs shouldn't expire that frequently.


Password NZBs

I've attempted to add into my nyuu.private.json
    " *** NZB Options *** ":0,
    "out":                "{filename}.nzb",
    "overwrite":          true,
    "nzb-subject":        "[{filenum}/{files}] - \"{filename}\" yEnc ({part}/{parts}) {filesize}",
    "nzb-password":       "${rand(15)}",

But checking the header of the NZB it just shows it as pure text and not a randomly generated password, other functions of the generation worked fine.
<!DOCTYPE nzb PUBLIC "-//newzBin//DTD NZB 1.1//EN" "http://www.newzbin.com/DTD/nzb/nzb-1.1.dtd">
<nzb xmlns="http://www.newzbin.com/DTD/2003/nzb">
	<head>
		<meta type="password">${rand(15)}</meta>
	</head>

two attempted names of nzb-password but if I tried just doing "password" nyuu thought it was part of the NNTP login so got
[2024-04-17 12:16:01.999][WARN] NNTP connection failed: Unexpected response to auth pass (code: 502): Authentication Failed, reconnecting after 15 second(s)... (attempt 1/1)
[2024-04-17 12:16:01.999][WARN] NNTP connection failed: Unexpected response to auth pass (code: 502): Authentication Failed, reconnecting after 15 second(s)... (attempt 1/1)
[2024-04-17 12:16:02.000][WARN] NNTP connection failed: Unexpected response to auth pass (code: 502): Authentication Failed, reconnecting after 15 second(s)... (attempt 1/1)
[2024-04-17 12:16:02.000][WARN] NNTP connection failed: Unexpected response to auth pass (code: 502): Authentication Failed, reconnecting after 15 second(s)... (attempt 1/1)

This isn't a juicenet thing. That's entirely nyuu's doing. Nyuu doesn't support the ${rand(N)} token in nzb-password


[Popup] Arrow doesn't match position

Describe the bug
When a popup is open but there is not enough space for displaying in the corner where it was set to open, it is opening on the opposite side. The arrow is not following the "new" side taken.
To Reproduce
Steps to reproduce the behavior:

Go to 'vivid storybook'
Open the popup
Reduce the page size till the popup is showing in the upper side instead of the bottom
See error

Expected behavior
The arrow should always point to anchor
Screenshots

Thank you for bringing the issue to our attention @dvelluto. The fix has been merged.
https://github.com/Vonage/vivid/pull/1387

@rinaok is this going to be in 2.39 ? I see the behavior is fixed on dev storybook, but it's not yet live


Change FIAM internal symbol causing App Store warnings

Fix #10276

Cocoapods-10.0.0 tags have been updated to include this commit.

Zip being built at https://github.com/firebase/firebase-ios-sdk/actions/runs/3144589094


[Bitmap font] Assume outline size is 1 if it's not set, but channel for outline is defined.

Fixes https://github.com/godotengine/godot/issues/74200

Thanks!

Cherry-picked for 4.0.1.


Merge refactoring

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

130 of 246 (52.85%)  changed or added relevant lines in 12 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-8.9%) to 78.746%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repository/IngSoft2-Model/DrawCardSquare.class.st
0
1
0.0%

repository/IngSoft2-Model/CancellationCard.class.st
17
21
80.95%

repository/IngSoft2-Model/PlayedCardStack.class.st
19
23
82.61%

repository/IngSoft2-Model/PlayedCard.class.st
15
23
65.22%

repository/IngSoft2-Model/RedoCard.class.st
8
21
38.1%

repository/IngSoft2-Model/RepeatCard.class.st
8
21
38.1%

repository/IngSoft2-Model/AccelerationCard.class.st
8
25
32.0%

repository/IngSoft2-Model/OverloadCard.class.st
8
26
30.77%

repository/IngSoft2-Model/SpeedCard.class.st
8
26
30.77%

repository/IngSoft2-Model/TrenchRunGame.class.st
17
37
45.95%

Totals

Change from base Build<PHONE_NUMBER>:
-8.9%

Covered Lines:
804

Relevant Lines:
1021

💛  - Coveralls


Added the Xamarin platforms to the NuGet

Added the 3 Xamarin platforms to the NuGet:

Xamarin.iOS (Unified)
Xamarin.Android
MonoTouch (Xamarin.iOS Classic)

Have you tested that both these builds work on iOS and Android? For example Newtonsoft.Json.Portable uses dynamic which traditionally has broken in iOS.

No reply, no merge.


Context Selector - aria refinements

A couple of refinements can be made to the context selector:

include a reference to the hidden span from the toggle
use the label on the search button as the label for the input

Details:

pf-c-context-selector__toggle should have an id and an aria-labelledby that references the ids of the hidden span and pf-c-context-selector__toggle.
The search input can be labelled by the button label, as shown below. Note that I removed the id and name attributes from the <input>. I'm not sure that those are needed or not.

<input class="pf-c-form-control" type="search" placeholder="Search" aria-labelledby="search-button">
<button class="pf-c-button pf-m-tertiary" id="search-button" aria-label="Search menu items">
  <i class="fas fa-search" aria-hidden="true"></i>
</button>

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Basic Freeswitch Functionality

This code contains updates and modifications to the Freeswitch module present in Halcyon.  The module has been pulled out into a library and refactored to mirror the Vivox module.  It enables those with the inclination or requirement to host their own voice solution to use Freeswitch.
This module enables only basic functionality:  Multiple avatars in a region can connect, and talk/hear using the normal client interface.  Moving between regions switches the avatar to a new channel for that region.  Audio is not directional, there is no active speakers list, and users can only see their own voice dot above their avatar's head.  It is in active use on the MOSES grid for weekly office hours.

This is a really great addition to have. Also to have the old Freeswitch code cleaned out.  Looks good to me, @ddaeschler ready for merge (and inclusion in the 0.9.33 release).


Allow pipx run --pypackages to function again.

[x] I have added an entry to docs/changelog.md

Summary of changes
Closes #623 .
Due to a regression with PR #252 in order to fix Issue #233, using pipx with pythonloc (using the local __pypackages__ folder) stopped working.
To use packages in the local __pypackages__ folder with pipx run --pypackages, pipx adds the appropriate folders to PYTHONPATH.  Unfortunately the code from the previous PR removes PYTHONPATH before running it, nullifying the effect of pipx's own code.
This PR selectively allows only the two paths added by the pypackages code in pipx to PYTHONPATH to remain, removing PYTHONPATH or other directories in PYTHONPATH otherwise.
The code got a little less clean, but we should support operation of our own features (!)
Test plan

Tested by running
From report in Issue #623:
pipx install piploc
piploc install flask
pipx run --pypackages flask

pipx <IP_ADDRESS> shows error, this PR runs as expected.

The repeated PYTHONPATH string manipulation makes me nervous. Would it be better for exec_app to accept an additional extra_sys_path: list[str] and perform the PYTHONPATH addition only once, right before the app is executed?

The repeated PYTHONPATH string manipulation makes me nervous. Would it be better for exec_app to accept an additional extra_sys_path: list[str] and perform the PYTHONPATH addition only once, right before the app is executed?

Sure, that sounds cleaner to me.

@uranusjr how does it look now?  I left in the code that accommodates an intact PYTHONPATH in case we ever change our code and stop completely deleting it.


Enable gofumpt and gosec

Fixes #11
This also enables gosec now that the false positives have been tuned down a bit.

@mmlb - no, but considering it more after your other code review, I felt like the consistency is more important than the output.
The best we can do with gofumpt is show output that says "There is a diff", which is effectively what this linter does today. What I would rather it say is "There is an unnecessary empty line: run gofumpt to fix it".
The nice part about integrating it here is that golangci-lint run --fix will now fix gofumpt issues.


Inconsitent documentation of  and

For all the tags on this page we see that they are documented by means of XML wit the exception of the of <see> and <seealso> that has been documented as C#:
/// <see cref="member"/>
// or
/// <see cref="member">Link text</see>
// or
/// <see href="link">Link Text</see>
// or
/// <see langword="keyword"/>

and
/// <seealso cref="member"/>
// or
/// <seealso href="link">Link Text</seealso>

I think it would be better to document this also as XML

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3bcb925f-ef72-9a64-3762-c0b4a96f9dc4
Version Independent ID: d135d0a6-53d2-1567-0b1b-7aae5e07739f
Content: Recommended XML documentation tags for a class and its members
Content Source: docs/csharp/language-reference/xmldoc/recommended-tags.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

That's also a great suggestion @albert-github


Column names case insensitivity and quotes

According to http://docs.datastax.com/en/cql/3.3/cql/cql_reference/ucase-lcase_r.html
Troy's CQL Parser should

[ ] support double quoted identifiers (especially column names in select clause and create table)
[ ] lower case identifiers, unless they are double quoted.

Specs added (but ignored) here https://github.com/cassandra-scala/troy/pull/129


The result is not good as online website text2image

The generated image with same prompt is not as good as the website version: https://stablediffusionweb.com/.
Pretained model: https://huggingface.co/stabilityai/stable-diffusion-2-1.
GPU: MSI RTX4090
Is there any more pretained model and config for text2image? I want to have a try.

Come on, Its free source, how can it be better than those online AI if it designed for less strong computer


Fix Swift warning

When using this library in a full Xcode project, I am getting the Swift warning on this line:
xctest-dynamic-overlay/Sources/XCTestDynamicOverlay/XCTFail.swift:89:11: warning: string interpolation produces a debug description for an optional value; did you mean to make this explicit?

I went ahead and fixed it using the Xcode suggestion, but not sure if you'd rather:

Provide a default value
Force unwrap Bundle.main.bundleIdentifier
Go with what I have here.

Or perhaps you don't care about the warning. Regardless, thought I'd give this PR a shot.

@michaelmcguire Thanks for digging into this! We actually had a fix on main but it had made it into a release yet. I just cut 0.8.4. Can you confirm that the warnings go away for you?

@michaelmcguire Thanks for digging into this! We actually had a fix on main but it had made it into a release yet. I just cut 0.8.4. Can you confirm that the warnings go away for you?

@stephencelis Sorry for dropping off the planet there. I just upgraded and the warning is gone. Thanks!


Update tabindex support for Android browsers

Added Chrome on Android and Firefox on Android support for tabindex.
This can be verified using either a bluetooth keyboard or by using a virtual keyboard that exposes tab keys (e.g. Gboard exposes the forward tab on forms).

Haven't tried it myself, but that does make sense. Thanks!


Rename Obj Palette selector to Monochrome Palette

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Small silly improvement, I guess

What is the current behavior? (You can also link to an open issue here)

The tile palette selector in the sprite editor is called Obj Palette and OBP0 and OBP1 which are terms that don't mean much without good understanding of how the GB works.

What is the new behavior (if this is a feature change)?

Rename Obj Palette to Monochrome Palette and OBP0 and OBP1 to Palette 1: OBP0 and Palette 2: OBP1 also added a palette preview to both options in the dropdown.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

Other information:

Not sure how needed is this, but it was annoying me a bit :)

This is good because I originally thought you could use this to make sprites choose the darker color on GBC. I think this clears up any possible confusion


feat[cartesian]: Feedback when a bad backend is selected

Description
Recent work with new user showed that basic mistake can lead to pretty gnarly stack trace instead of a clean error message. This fixes one of the most common: a bad backend name required.
Requirements

[x] All fixes and/or new features come with corresponding tests.

cscs-ci run


feat(platform)!: masternode voting based conflict resolution

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
[ ] I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Closing this PR as it was superseded by https://github.com/dashpay/platform/pull/1878


As an inspector, I want a “Notes/Comments” section added to the label inspection form

Description
We need a solution for inspectors to add relevant notes or comments to the label inspection data. A section for free-text input will be added.
Acceptance Criteria

[ ] Add a section to the inspection schema for free-form notes or comments.
[ ] Name the section appropriately.

Additional Information
Ensure the section aligns with the schema as per https://github.com/ai-cfia/fertiscan-pipeline/issues/22.

I suggest adding a field into the inspection JSON like the following:
{
  "inspection_id": "uuid",
 "inspection_comment": "some comment/ user feedback in text",
  "verified": false,
  "product": {
...

After testing, submission crashes the app. Reopening this.


Aplication does not work without Internet connection

Hello, I download your application, everything works great - this app is what I was looking for.
However is there a way to run this app without internet connection? Some stand alone version perhaps?
At the moment application require network connection to be run.

Hi,
Thank you for answer.
I'm using launcher dowloaded from you webpage. Here is what I get after turning off WiFi and click on the lanuncher. Every time it tries to download some content. If I have access to the internet there is no issue, but without I get this:

In details log I can find this:

ERROR DETAILS
Following errors were detected during this operation.
* [7/30/2018 8:48:10 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://precisiongazemouse.com/install/PrecisionGazeMouse.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState, X509Certificate2 clientCertificate)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Net.WebException
- The remote name could not be resolved: 'precisiongazemouse.com'
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

Oh that is only the first time you install it because it downloads it from precisiongazemouse.com. I suppose you do have internet since you were able to download the program? You don't need an Internet connection to use the program. I think if you installed it and then turned off your Wi-Fi you would see that it works fine. Does that work for you? If not, could you explain why you need it a different way?

Ok, I now see my mistake. I though that this launcher was actual application. I didn't noticed that something was installed on computer. For future it would be nice if some shortcut was creadted on desktop after installation. :)
Thank you for help.
If I may I will open new topic with some question regarding configuration.

Ok great I'm glad you figured it out! It adds an item to the start menu but I'll keep your desktop icon idea in mind. Closing this issue.

Oh and yes feel free to open another issue if you have a question about configuration


Change the style in admin notice content view from  to

That's because many notic have more than one lines. So I think pre is more better to used in here than p
from:

to:

wow this was fast :)
didnt come to test it


$refs within items don't get added to list of schemas when isRemovingUnreferencedDefinitions

When the schema has an arraySchema that has items that are in turn a $ref, that ref doesn't get followed to add all of its children refs. In fact, I think this happens anytime there are refs of refs. This logic only goes one ref level deep. I was able to work around this in a PR I will post and link to this issue.

Tried to make the PR through GH's online edit tool, but it got mangled. Trying again now through git.

OK, I changed the branch to adhere to the contribution guidelines and cleaned up the code. Hopefully it'll pass now!

Please let me know if I am missing anything in the way of style or logic!

Thanks for reporting this, fixed in #3317 (which includes #3305)

@frantuma thanks for taking care of this so quickly! And thanks for helping with a great product 😄


Environment mapping for repositories in project

I can map repository with environment (DEV or PROD) in Artifactory Project UI. How could I do this in the terraform provider?
Maybe you have any plans to implementation this feature.
In project resource I seen only one point to map repositories repos = local.all_repos_list
My code example:
## Projects
resource "project" "terraform-project" {
  key          = var.art_project_key
  display_name = "${upper(var.art_base)} Project"
  description  = "Business unit: ${upper(var.business_unit)}, Responsobility person: ${var.responsibility_person}"
  admin_privileges {
    manage_members   = false
    manage_resources = false
    index_resources  = true
  }
  max_storage_in_gibibytes   = var.art_repos_size
  block_deployments_on_limit = false
  email_notification         = true

  repos = local.all_repos_list

  dynamic "group" {
    for_each = var.art_env
    content {
      name  = "sec_artifactory_${var.art_base}_${group.value}_rw"
      roles = group.value == "prod" ? ["Release Manager", "Viewer"] : ["Contributor"]
    }
  }

  dynamic "group" {
    for_each = var.art_env
    content {
      name  = "sec_artifactory_${var.art_base}_${group.value}_read"
      roles = ["Viewer"]
    }
  }

  depends_on = [
    artifactory_local_generic_repository.terraform-local-generic-repo,
    artifactory_local_nuget_repository.terraform-local-nuget-repo,
    artifactory_local_docker_v2_repository.terraform-local-docker-repo,
    artifactory_local_npm_repository.terraform-local-npm-repo,
    artifactory_local_pypi_repository.terraform-local-pypi-repo,
    artifactory_local_maven_repository.terraform-local-maven-repo,
    artifactory_local_conan_repository.terraform-local-conan-repo,
    artifactory_local_debian_repository.terraform-local-debian-repo,
    artifactory_local_gitlfs_repository.terraform-local-gitlfs-repo,
    artifactory_local_go_repository.terraform-local-go-repo,
    artifactory_local_helm_repository.terraform-local-helm-repo,
    artifactory_group.adsync_user_group,
    artifactory_group.adsync_user_group_read
  ]
}

@ADSapozhnikov The repo environment is set as part of the repo's attributes. See the JSON schema. However, the Environment attribute is currently not supported in the Artifactory provider.
After We add support to Artifactory provider, then you update the repo's Environment attribute separately.


Cannot read property '__useDefault' of undefined

Hi,
I am having a typescript based aurelia cli project. The issue is when I try to load the Aurelia-Configuration plugin I get the following error

DEBUG [aurelia] Loading plugin aurelia-configuration.
vendor-bundle.js:21077 Uncaught TypeError: Cannot read property '__useDefault' of undefined

Not sure if I am doing anything wrong as I do not see any error on the cli console. I have added the dependency of aurelia-configuration in aurelia.json

I had some problems aswell. I think this one was gone, after i put the deep-extend.js in my src folder. You also might need to go into your aurelia.json, and set stub-property in build.loader[0].plugins to false.
And last but not least, you need to add aurelia-configuration to your dependencies in your aurelia.json like so`
{
      "name": "aurelia-configuration",
      "path": "../node_modules/aurelia-configuration/dist/commonjs",
      "main": "index"
}

Thank you for the above @heiko5 this should resolve the issue people are having. The CLI being AMD based means sometimes you need to manually supply a different route.

@heiko5 when you run into "cannot find" with aurelia-cli, you don't need to copy the file to your src folder. You just need to add another bundle reference for that file. In this case it is a dependency of aurelia-configuration so it is already installed. This should suffice in your aurelia.json:
{
  "name": "aurelia-configuration",
  "path": "../node_modules/aurelia-configuration/dist/commonjs",
  "main": "index"
},
"deep-extend"


Tasks stuck in "waiting" or "scheduled"

Information

Onefuzz version: onefuzz 1.11.0
OS: 18.04.5 LTS (Bionic Beaver)

Provide detailed reproduction steps (if any)
After following the setup instructions for Onefuzz, including creating a pool of VMs, we are able to create example jobs, like libfuzzer or AFL, but each task for the jobs are stuck in either "scheduled" or waiting. The jobs never run. We tried deleting all jobs and even creating a new pool of VMs, but no success.

There is a known-issue in 1.11.0 that causes idle VMs from not being able to request tasks (PR #459), which is compounded by the dead-node detection was not functioning (PR #458).
These will be fixed in the next release, which I hope to publish today.

There is a known-issue in 1.11.0 that causes idle VMs from not being able to request tasks (PR #459), which is compounded by the dead-node detection was not functioning (PR #458).
These will be fixed in the next release, which I hope to publish today.

Thanks!

Thanks!

@T-S-A , we identified and fixed a bug that would cause a deadlock in the supervisor (PR #603)
With this change combined with the previous issues, I believe this to be corrected.  If you upgrade, you may need to recreate your scalesets to get this change.

Please let us know if you continue to have this issue.


Add a mutex to silences.go:gossipData

This should fix silence/silence.go #982

I'm not super happy about naming.
It needs to be carefully reviewed too, mutex can get hard.

Thanks for the quick PR! I'll look at it this weekend

This got deployed on a setup with ~2000 silences and 7 alertmanagers. Seems stable.


Upgrade: when deleting a frame, pop confirmation dialog with all fram…

…e children, delete all children with the frame

bors merge


Horizontal scroll in ipynb files via Shift+mouse wheel doesn't work

Originally from Oleksandr Marmaliuk on marketplace:

horizontal scroll in ipynb files via Shift+mouse wheel stopped working after recent update

I've also confirmed it doesn't work on my machine
Environment data

VS Code version: 1.94.0-insider
Jupyter Extension version (available under the Extensions sidebar): v2024.9.2024092001 (pre-release)
Python Extension version (available under the Extensions sidebar): v2024.15.2024092301 (pre-release)
OS (Windows | Mac | Linux distro) and version: Windows 11 Pro 23H2

Expected behaviour
Hold Shfit key while using mousewheel to scroll horizontally
Actual behaviour
Does nothing

Repro steps for me:

Turn off word wrap ("editor.wordWrap": "off")
Write a long line of code that goes beyond visible area
Try scrolling horizontally while pressing Shift


⚠ Turnos 24x7 has degraded performance

In b9a1b02, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 874 ms

Resolved: Turnos 24x7 performance has improved in a9208a1.


Mistake in the koa v2 examples

The koa v2 example used in the README and the Koa 2.0.0 issue looks wrong.
// uses async arrow functions
app.use(async (ctx, next) => {
  try {
    await next() // next is now a function
  } catch (err) {
    ctx.body = { message: err.message }
    ctx.status = err.status || 500
  }
})

app.use(async ctx => {
  const user = await User.getById(this.session.userid) // await instead of yield
  ctx.body = user // ctx instead of this
})

this.session.userid is used, but it's used inside of an arrow function, where this should refer to the global object, not something related to the request.

Oops yeah. Should be ctx. Would you like to make a PR? :)

#641 merged, issue should be closed.

oh, i guess i said "solves" not "resolves", bleh