Snippet cursor placement

Describe the feature and the current behavior/state.
Would be nice, when creating a snippet, one could choose where to place the cursor, after snippet has been expanded.
Alfred 4 has this feature, which is the only reason I'm hesitating to switch.
Right now, cursor is always at the end of the expanded snippet.
Will this change the current API? How?
Snippet editor needs a way to tell where the cursor should go. Like in Alfred 4, one could write {cursor} inside the snippet so it nows exactly where to go.
eg.
snippet keywoard: ;cl
snippet: console.log({cursor});
-> places the cursor inside parentheses after expansion
Who will benefit from this feature?
Everyone ;)
Any Other info.

Hey @MishaFrenkman – could you report this through Raycast's feedback command? (It's unrelated to the API...)

@MishaFrenkman I second that request, it should be part of snippets as well as {clipboard}

@aurawindsurfing it's shipped in the latest updated

nice one!


The author is great, the current GPT3.5api has been released, please trouble to adapt the interface

The author is great, the current GPT3.5api has been released, please trouble to adapt the interface

@lmuiotctf Thanks for your info.
Just pushed new version.
Please check

Node openai-api doesn't support GPT3.5 yet. Will push new version again once it's ready.

Hello author, currently you use the model created by node, the current GPT3.5 request interface address is https://api.openai.com/v1/chat/completions
So using openai.createCompletion you can't find codex and gpt3.5 models, so you will report the error "Rate limit reached for default-gpt-3.5-turbo in organization org-

Yeah, Just implemented.


Update diagnostic-tools.md

Pull Request Template
What are you trying to address
There is a very minute correction which I came across while reading the doc, Hyperlink for Windows Debug tools is misspelled , proposing this change to rectify the same.
Original ==> WinDdg and WinDgbNext
Rectified ==> WinDbg and WinDgbNext
Description of new changes

This is a very small correction on the document to spelling it correct.

For all pull requests
I am a non CSE member and creating this pull request for the first time.

Thank you for the fix, the link-check will go through as soon as PR #775 is merged


Error occurs when installing openapiart with test requirements

Version information
main branch
Describe the bug
After building the distribution for python, when installing it using python do.py install, I keep getting following error:
ERROR: Could not find a version that satisfies the requirement openapiart.egg; extra == "testing" (from openapiart[testing]) (from versions: none)
ERROR: No matching distribution found for openapiart.egg; extra == "testing"

To Reproduce
python do.setup
python do.py init
python do.py dist
python do.py install

Expected behavior
Error shouldn't be seen

Fixed in snappi=0.7.37


fix(Laucnher): do not detach child process on windows

Fixes #2053.

@alixaxel @JoelEinbinder can you guys please check if this works for you on win? Process management is not a well-tested area of ours.

@aslushnikov I'm not a windows user.

@alixaxel oops, sorry for the noize.
cc @vsemozhetbyt

@aslushnikov Can you provide some code I could test on Windows to be sure this fix the issue?

@vsemozhetbyt Try running the following script and then terminate running node.js program differently:

via taskmanager
via Ctrl-C
via closing the terminal

In all the cases, the spawned chromium instance should be closed.
var pptr = require('puppeteer');
(async() => {
  const browser = await pptr.launch();
  console.log('Launched!');
})();

@aslushnikov I can confirm that with this patch all three terminations of the running node.js program also close the spawned chromium instance.

@vsemozhetbyt: Thank you.
@JoelEinbinder, let's merge this?

@vsemozhetbyt: Thank you.
@JoelEinbinder, let's merge this?

I still get some errors when closing things on windows, but it actually closes things now so I'd say this is better.


Update tour tip and hint titles to be more descriptive

On second thought, I think they're fine how they are.


Improve processor parking strategy

Right now Processors will wait forever in its own channel until got notified by ProcMessage. So it won't try to steal jobs from the other Processors!
So we have to add something to achieve:

Processor won't spin itself when it has nothing to do.
Processor can process the ProcMessages in time.
Processor can steal jobs from the other Processors.

Please add comments below :)

We might want to thread::park()/unpark() the current thread and add it's handle to a processor wait list on the Scheduler...
This thread get's unparked whenever Scheduler::ready() is called with a preferred_processor which is currently parked, or when a Processor determines that it has a big amount (>N) of coroutines in it's deque and would like to have some help by another Processor.
Well something like that I guess should solve this...
But I'm quite sure that the Processors have to have a certain level of "cooperation".

But every time the ready() is called, you would have to check the parked list and wake one thread up. Please try to implement it and do a simple benchmarking on it.

Ah, I was accidentally merged this branch to master by hand. My fault. We could keep on discussing in the issue.


issue running tree example

I'm having issue running command command
python tree.py 88:0F:10:92:A0:39
Attempting to connect to 88:0F:10:92:A0:39
Traceback (most recent call last):
  File "tree.py", line 36, in <module>
    device.connect()
  File "/usr/local/lib/python2.7/dist-packages/bleep/device.py", line 154, in connect
    self.requester.connect(True, "random")
RuntimeError: Channel or attrib not ready

while using pygattlib/example I don't have isseu running the examples
/pygattlib/examples# python discover_primary.py  88:0F:10:92:A0:39
Connecting...
{'start': 1, 'end': 11, 'uuid': '00001800-0000-1000-8000-00805f9b34fb'}
{'start': 12, 'end': 15, 'uuid': '00001801-0000-1000-8000-00805f9b34fb'}
{'start': 16, 'end': 24, 'uuid': '0000180a-0000-1000-8000-00805f9b34fb'}
{'start': 25, 'end': 35, 'uuid': '0000181d-0000-1000-8000-00805f9b34fb'}
{'start': 36, 'end': 50, 'uuid': '00001530-0000-3512-2118-0009af100700'}
Done.

Allah başka dert, tasa vermesin. Olur öyle.

On 25 Jul 2017, at 23:33 , gesaleh<EMAIL_ADDRESS>wrote:
I'm having issue running command command
python tree.py 88:0F:10:92:A0:39
Attempting to connect to 88:0F:10:92:A0:39
Traceback (most recent call last):
File "tree.py", line 36, in
device.connect()
File "/usr/local/lib/python2.7/dist-packages/bleep/device.py", line 154, in connect
self.requester.connect(True, "random")
RuntimeError: Channel or attrib not ready
while using pygattlib/example I don't have isseu running the examples
/pygattlib/examples# python discover_primary.py  88:0F:10:92:A0:39
Connecting...
{'start': 1, 'end': 11, 'uuid': '00001800-0000-1000-8000-00805f9b34fb'}
{'start': 12, 'end': 15, 'uuid': '00001801-0000-1000-8000-00805f9b34fb'}
{'start': 16, 'end': 24, 'uuid': '0000180a-0000-1000-8000-00805f9b34fb'}
{'start': 25, 'end': 35, 'uuid': '0000181d-0000-1000-8000-00805f9b34fb'}
{'start': 36, 'end': 50, 'uuid': '00001530-0000-3512-2118-0009af100700'}
Done.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/matthewelse/bleep/issues/12, or mute the thread https://github.com/notifications/unsubscribe-auth/AYhNLwJqLEdUxgcNdNMc66f1gu2rACg9ks5sRlEVgaJpZM4OjF1P.


libusb1: 1.0.21 -> 1.0.22

Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/libusb/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.0.22 with grep in /nix/store/5wk75f6zd7ha7vhm4y3pd9p1qbc3vmgd-libusb-1.0.22
directory tree listing: https://gist.github.com/ceccc2a897849afc2956de19e751995f

Success on x86_64-linux (full log)
Attempted: libusb1
Partial log (click to expand)
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/5wk75f6zd7ha7vhm4y3pd9p1qbc3vmgd-libusb-1.0.22/lib
patching script interpreter paths in /nix/store/5wk75f6zd7ha7vhm4y3pd9p1qbc3vmgd-libusb-1.0.22
checking for references to /build in /nix/store/5wk75f6zd7ha7vhm4y3pd9p1qbc3vmgd-libusb-1.0.22...
shrinking RPATHs of ELF executables and libraries in /nix/store/1pnhnr6hjvd97928ygnmcgv2mck9ci5c-libusb-1.0.22-dev
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
/nix/store/5wk75f6zd7ha7vhm4y3pd9p1qbc3vmgd-libusb-1.0.22
stripping (with command strip and flags -S) in /nix/store/1pnhnr6hjvd97928ygnmcgv2mck9ci5c-libusb-1.0.22-dev/lib
patching script interpreter paths in /nix/store/1pnhnr6hjvd97928ygnmcgv2mck9ci5c-libusb-1.0.22-dev
checking for references to /build in /nix/store/1pnhnr6hjvd97928ygnmcgv2mck9ci5c-libusb-1.0.22-dev...

Success on aarch64-linux (full log)
Attempted: libusb1
Partial log (click to expand)
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/lxn51gam8irnj8qj4bb07bkan51gzdwf-libusb-1.0.22/lib
patching script interpreter paths in /nix/store/lxn51gam8irnj8qj4bb07bkan51gzdwf-libusb-1.0.22
checking for references to /build in /nix/store/lxn51gam8irnj8qj4bb07bkan51gzdwf-libusb-1.0.22...
shrinking RPATHs of ELF executables and libraries in /nix/store/n2y7x20ar50pahlddn08gjngv05swl65-libusb-1.0.22-dev
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/n2y7x20ar50pahlddn08gjngv05swl65-libusb-1.0.22-dev/lib
patching script interpreter paths in /nix/store/n2y7x20ar50pahlddn08gjngv05swl65-libusb-1.0.22-dev
checking for references to /build in /nix/store/n2y7x20ar50pahlddn08gjngv05swl65-libusb-1.0.22-dev...
/nix/store/lxn51gam8irnj8qj4bb07bkan51gzdwf-libusb-1.0.22

Success on x86_64-darwin (full log)
Attempted: libusb1
Partial log (click to expand)
post-installation fixup
Patching '/nix/store/jhrh88wljpmh7bmjjnisn8944dg4c3m6-libusb-1.0.22-dev/lib/pkgconfig/libusb-1.0.pc' includedir to output /nix/store/jhrh88wljpmh7bmjjnisn8944dg4c3m6-libusb-1.0.22-dev
strip is /nix/store/vb6mgjqgd9h11nbv60fvrp1ls9nxck2y-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/0kdyd0ak13lpgqjf1xrwf9z9rp9ivgng-libusb-1.0.22/lib
patching script interpreter paths in /nix/store/0kdyd0ak13lpgqjf1xrwf9z9rp9ivgng-libusb-1.0.22
/nix/store/0kdyd0ak13lpgqjf1xrwf9z9rp9ivgng-libusb-1.0.22/lib/libusb-1.0.0.dylib: fixing dylib
strip is /nix/store/vb6mgjqgd9h11nbv60fvrp1ls9nxck2y-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/jhrh88wljpmh7bmjjnisn8944dg4c3m6-libusb-1.0.22-dev/lib
patching script interpreter paths in /nix/store/jhrh88wljpmh7bmjjnisn8944dg4c3m6-libusb-1.0.22-dev
/nix/store/0kdyd0ak13lpgqjf1xrwf9z9rp9ivgng-libusb-1.0.22

Success on x86_64-linux (full log)
Attempted: libusb1
Partial log (click to expand)
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zd1v0gx800glyrx97rhr398v8c8kj87m-libusb-1.0.22/lib
patching script interpreter paths in /nix/store/zd1v0gx800glyrx97rhr398v8c8kj87m-libusb-1.0.22
checking for references to /build in /nix/store/zd1v0gx800glyrx97rhr398v8c8kj87m-libusb-1.0.22...
shrinking RPATHs of ELF executables and libraries in /nix/store/cawr9lkhw5hgsbzv12axf1knw8l47ibi-libusb-1.0.22-dev
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/cawr9lkhw5hgsbzv12axf1knw8l47ibi-libusb-1.0.22-dev/lib
patching script interpreter paths in /nix/store/cawr9lkhw5hgsbzv12axf1knw8l47ibi-libusb-1.0.22-dev
checking for references to /build in /nix/store/cawr9lkhw5hgsbzv12axf1knw8l47ibi-libusb-1.0.22-dev...
/nix/store/zd1v0gx800glyrx97rhr398v8c8kj87m-libusb-1.0.22

Success on x86_64-darwin (full log)
Attempted: libusb1
Partial log (click to expand)
post-installation fixup
Patching '/nix/store/mf03x4vbg2hvpjvxg3g56s310fqgspmc-libusb-1.0.22-dev/lib/pkgconfig/libusb-1.0.pc' includedir to output /nix/store/mf03x4vbg2hvpjvxg3g56s310fqgspmc-libusb-1.0.22-dev
strip is /nix/store/5fc1zygrlgfdzkfk1hajdw81czs5v9y9-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/cs0kzj6ip4x3pjdx8aczr7gn24w0si3v-libusb-1.0.22/lib
patching script interpreter paths in /nix/store/cs0kzj6ip4x3pjdx8aczr7gn24w0si3v-libusb-1.0.22
/nix/store/cs0kzj6ip4x3pjdx8aczr7gn24w0si3v-libusb-1.0.22/lib/libusb-1.0.0.dylib: fixing dylib
strip is /nix/store/5fc1zygrlgfdzkfk1hajdw81czs5v9y9-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/mf03x4vbg2hvpjvxg3g56s310fqgspmc-libusb-1.0.22-dev/lib
patching script interpreter paths in /nix/store/mf03x4vbg2hvpjvxg3g56s310fqgspmc-libusb-1.0.22-dev
/nix/store/cs0kzj6ip4x3pjdx8aczr7gn24w0si3v-libusb-1.0.22

Failure on aarch64-linux (full log)
Attempted: libusb1
Partial log (click to expand)
[524/1461] Compiling C object<EMAIL_ADDRESS>[525/1461] Compiling C object<EMAIL_ADDRESS>[526/1461] Compiling C object<EMAIL_ADDRESS>[527/1461] Compiling C object<EMAIL_ADDRESS>[528/1461] Compiling C object<EMAIL_ADDRESS>[529/1461] Compiling C object<EMAIL_ADDRESS>ninja: build stopped: subcommand failed.
builder for '/nix/store/nhsk0sjbx5cn02jprnbydc6ix5sxd1w0-systemd-238.drv' failed with exit code 1
cannot build derivation '/nix/store/hqjp16ix3vhzkk1c4n2h64dd63nm0agb-libusb-1.0.22.drv': 1 dependencies couldn't be built
error: build of '/nix/store/hqjp16ix3vhzkk1c4n2h64dd63nm0agb-libusb-1.0.22.drv' failed


Add NeuroVault extraction

Might be helpful to automate the NV link extraction based on regex pattern matching on links

why not -- do you mean like having separate PMCID x neurovault collection ID and PMCID x neurovault image ID files besides the links.csv?

indeed

@adelavega  can you confirm that all image links will look like .*neurovault.org/images/(\d+).* and all collections like .*neurovault.org/collections/(\d+).*, where the captured group is the ID?

Two changes to that:

First, there are these two aliases: identifiers.org/neurovault.collection:(\w*) and identifiers.org/neurovault.image:(\d*)
Also note that I used \w for collection, as private links are actually alphanumeric. This is not actually the collection id, but it can be resolved to one

thanks!


[ENG-4566] refactor status updates for multi-platform builds

Checklist

[x] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Closes https://linear.app/expo/issue/ENG-4566/provide-queue-position-and-estimated-wait-time-when-running-builds-for
Follow-up to https://github.com/expo/eas-cli/pull/1049
We want to display queue position + estimated wait time when running multiplatform builds.
How
Use multiline spinner for reporting status.
Test Plan

iirc, there's also a status when you have exceeded the number of builds you can submit to the queue. Is that one we need to handle (I remember a status 'unknown' before)?

@kbrandwijk

There's also a status when you have exceeded the number of builds you can submit to the queue.

Yes, but the limit is 15 builds per platform. It's hard to reach it.
See https://github.com/expo/universe/blob/main/server/www/src/data/entities/turtlebuild/TurtleBuildUtils.ts#L117

Is that one we need to handle?

I think you're right and we should handle the error when one exceeds the number of pending builds in queue. I'm afraid we never handled this case properly. I mean this error is thrown when creating a build with the build mutation. This will never be thrown when checking the build's status (because the build does not get created if the build mutation throws an error). When running a single-platform build this isn't a problem.
What we should fix is the behavior when running multiplatform builds and one of the builds exceeds the queue limit. It's not the scope of this PR.


An option to disable default-features crate and workspace wide

Problem
I see value in minimizing the dependency tree - only bring in what I actually use.
The problem is that, between me using workspaces and features being additive, this creates a lot of noise in my manifest files, making them much harder to read.
As an example:
A small project I'm working on now, a set of three connected libraries in a workspace. There is a total of seven external non-dev dependencies, plus one or two intra-workspace ones. A total of around three thousand lines of Rust. default-features = false is found an astonishing twenty six times among the four manifest files.
I am most definitely not the only person doing this, as cargo-deny has a ban for default-features
To show what it looks like:
[dependencies]
bytes = { workspace = true, default-features = false }
num_enum = { workspace = true, default-features = false }
thiserror = { workspace = true, default-features = false }

futures = { workspace = true, default-features = false, optional = true }
tokio = { workspace = true, default-features = false, features = ["macros"], optional = true }
tokio-util = { workspace = true, default-features = false, optional = true }
valuable = { workspace = true, default-features = false, optional = true }

Proposed Solution
I would like an option that would allow me to, in one place, set default-feature = false for every dependency in the file manifest. Ideally, this would be three switches: separately for regular, dev and build dependencies.
The big issue I see with such an addition is that it does not fit within the existing structure of the manifest file - the obvious place to put it would be under dependencies, but that would create a precedent of Cargo itself reserving crate names, which I do not think is a good idea.
Other top level keys have their own roles, and adding this feature to them would not be suitable.
Just about the only option I see is adding a new top-level key to the manifest, perhaps one generally involved with governing default features. This option would be added under it.
Notes
#3126 may be relevant to this discussion.

I've long wanted this ability too, syntax I've considered in the past was
[dependencies]
"*" = { default-features = false }

* is not a XID compatible identifier so shouldn't cause any conflicts, and should be relatively obvious (though it doesn't look great with the quoting).


Set-Metadata HTTP filter

Commit Message: HTTP filter that can set or update dynamic metadata.
Additional Description:
This extension simply allows to add user-defined dynamic metadata. This is intended to be used with matchers, so that the "result" of a matching process can imply specific metadata.
See issue #16266
Risk Level: Medium
Testing: Unit tests for the extension are added
Docs Changes: A small documentation for the extension is added in docs/root/configuration/http/http_filters
Release Notes: N/A
Platform Specific Features: N/A
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

@htuch it looks like this conflicts with main. Should I be rebase on main and resquash into two commits? (one for StructUtil::update and one for the extensions)

@aguinet in general, you should have a flow that you never rebase after creating a PR. Instead do local merges from origin/main.

Thanks. The merging now makes more sense. One question I have is how this extension relates to the header_to_metadata filter? https://github.com/envoyproxy/envoy/blob/main/api/envoy/extensions/filters/http/header_to_metadata/v3/header_to_metadata.proto
It seems that really we want both to behave similarly, and if we were designing from scratch they would be somewhat unified. We also have other filters, e.g. ext_authz, that set dynamic metadata base on return values from remote servers. Ideally these have aligned merge semantics.
We don't need to boil the ocean here, but having some explanation and game plan to get consistent behaviors would be helpful.

These are good questions I tried to resolve before starting this. Let me first explain my use case. What we'd like to do is leverage the matching engine to add "tags", and log this tag and/or take decisions according to these tags. This is configurable by the user in the end, and would be transformed to an envoy configuration file.
As an example, I could add the tag "tag0" if the cookie "mycookie" matches a given regular expression, and another tag "tag1" if the IP comes from AS3215. I would like these two tags to be logged, and let's say block the request if the two of them are there.
In order to reuse the matching engine, we would configure HTTP filters like this:
# Wrapped into a first matcher
- filter0:
    @type: set_metadata
    namespace: mynamespace
    value:
      tags:
       tag0: 1
#  Wrapped into a second matcher
- filter1:
    @type: set_metadata
    namespace: mynamespace
    value:
      tags:
        tag1: 1

In order to get the two tags, I need the current merging strategy.
Now about header_to_metadata. From my understanding, it's just setting strings (potentially base64 ones) or integers values, taken from headers. There are no issue of potentially merging two different recursive structures. But I might be missing something here.
I just checked ext_authz, the only place I found it setting metadata is here: https://github.com/envoyproxy/envoy/blob/1f4ca4c0d395360845d0453a949f6c53acb147cb/source/extensions/filters/http/ext_authz/ext_authz.cc#L211-L214 . This looks like there are no merging strategy involved, but I don't know the use cases enough to know if that even makes sens!

@aguinet in general, you should have a flow that you never rebase after creating a PR. Instead do local merges from origin/main.

Okay. So I'll end up with a merge commit, right? Should I squash all of this before merging?

Thanks for the explanation. I agree this makes sense. @envoyproxy/api-shepherds I'd like us to think about adopting this as the standard merge strategy going forward, so we don't have inconsistent merging when filters are performing dynamic metadata update.

Okay. So I'll end up with a merge commit, right? Should I squash all of this before merging?

Yes, add a merge commit. You can't squash (since this is a rebase) once a PR has started. We will squash everything prior to the main merge once approved.

LGTM modulo nits and a main merge for conflict.

@phlax do you know what is going on with this glint failure?

https://dev.azure.com/cncf/envoy/_build/results?buildId=76293&view=logs&j=c5dd2866-6ab3-5f3c-3a44-4cef0ec909b5&t=a9eb66d6-8944-5769-b3f7-476949dadcb8&l=60

https://dev.azure.com/cncf/envoy/_build/results?buildId=76293&view=logs&j=c5dd2866-6ab3-5f3c-3a44-4cef0ec909b5&t=a9eb66d6-8944-5769-b3f7-476949dadcb8&l=60

Should be fixed with 0469f862691473bdc1e0630ea4e043f16b7b5871 . Added a configuration to my vim to highlight these...

Added a configuration to my vim to highlight these...

i have my editor (emacs) automatically remove/fix on save

@aguinet the clang-tidy failures seem legit, see https://dev.azure.com/cncf/envoy/_build/results?buildId=76440&view=logs&j=430ab721-bbba-5b3a-3c7b-ff111cc657fe&t=b6238472-0f30-5195-100c-623a3015b9ef

@htuch yep, I've just pushed https://github.com/envoyproxy/envoy/pull/16400/commits/d82b20ab3239f5118b45a3aec2fc94fa5f49550c to fix it!

\o/ Thanks a lot for the merge @htuch !


[PE-D][Tester E] Message for viewleave command when there are no employees has a minor typo

The message should rephrase "no employee" to "no employees". Minor grammatical issue.

Labels: type.FeatureFlaw severity.VeryLow
original: wui-hong/ped#6

Edited the error message


Enhanced existing API generator to use the OpenAPI spec as the input format

Description
Enhanced existing API generator to use the OpenAPI spec as the input format
Issues Resolved
Closes #348
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #376 (88b97a6) into main (83be2cd) will increase coverage by 1.28%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #376      +/-   ##
==========================================
+ Coverage   70.72%   72.01%   +1.28%
==========================================
  Files          77       77
  Lines        7157     7190      +33
==========================================
+ Hits         5062     5178     +116
+ Misses       2095     2012      -83

see 29 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

+1 for not checking in spec files and importing them, otherwise looks good!

@VachaShah The OpenAPI specs on opensearch-api-specification repo currently doesn't have the extra metadata needed for generate the client code. This PR and its follow-up will have to be merged first before we can use the specs there for client generation.


Make contributors section on website

Make a page on the frontend (or a section) to display the contributors to this repository to give them credit
To contribute, read the contribution docs Contribution docs

Hi, I'm taking a stab at this.

okay great, im assigning you.


Reddit bz2 to data format?

Hi,
This is great~! This will save me so much time, formatting some bz2 files.
In the documentation, it says that the conversations in the Reddit threads are till October 2018. I was wondering where is the script to convert from .bz2 files from pushshift.io to a corpus object?

Hi @debajyotidatta, glad you're finding ConvoKit useful for your work!
We have the script and the infrastructure for converting it in a separate repository since the size of Reddit means that more careful engineering is required for conversion. For most datasets, we generate the Corpus with converted Utterances and then dump it to create the distributable dataset. This first approach may be unfeasible for Reddit depending on your computing resources and the size of what you're trying to convert. In our case, we wrote out the individual component files (i.e. conversations.json, utterances.jsonl, etc) directly.
Here is a gist of our main conversion file: https://gist.github.com/calebchiam/711e47ce836f29c0ff889c903747c91f.
This was written in 2018, so some parts may need to be updated depending on how Pushshift has changed its own data format. Feel free to tweak it to your purposes and let us know if you have any further questions!


Initiate connection to neo4j in Vuejs main.js script

Hi,
In your README you are building the connection in one of the components, with hardcoded data.
Is there a way to initiate this connection directly in main.js, right after Vue.use(VueNeo4j) ?
Vue.use(VueNeo4j)

// ?
$neo4j.connect('bolt', 'localhost', 7687, 'user', 'password')

This way i would just have to use const session = this.$neo4j.getSession() in my methods to get an instance of neo4j  driver.
Is it possible ?
I'm not very familiar with VueJS, nor Javascript in general.
Thanks !

You can't do this at the moment - the quickest way would be to connect in the created() method in your App.vue component.
export default {
  name: 'App',
  // ...
  created() {
    this.$neo4j.connect('bolt', 'localhost', 7687, 'user', 'password')
  }
}

Then you could use this.$neo4j.getSession() elsewhere in the application


Queries beginning with as throw exceptions

Using the default config that points to rdap.org, you can run the utility as such:

rdap astound.ai -- An exception will be thrown

Traceback (most recent call last):
  File "/Users/smarpo/.local/share/virtualenvs/check-invalid-apps-btF75AhN/bin/rdap", line 8, in <module>
    sys.exit(main())
  File "/Users/smarpo/.local/share/virtualenvs/check-invalid-apps-btF75AhN/lib/python3.9/site-packages/rdap/cli.py", line 77, in main
    obj = client.get(each)
  File "/Users/smarpo/.local/share/virtualenvs/check-invalid-apps-btF75AhN/lib/python3.9/site-packages/rdap/client.py", line 231, in get
    return self.get_asn(qstr[2:])
  File "/Users/smarpo/.local/share/virtualenvs/check-invalid-apps-btF75AhN/lib/python3.9/site-packages/rdap/client.py", line 278, in get_asn
    asn = int(asn)
ValueError: invalid literal for int() with base 10: 'tound.ai'

Looks like if your query begins with as, you strip it off per: https://github.com/20c/rdap/blob/master/rdap/client.py#L230
Let me know if I'm using your RDAP client incorrectly, but seems like a legit bug to me. Thanks!

Definitely a bug, good catch, thanks!

Definitely a bug, good catch, thanks!

@seanmarpo was hoping to get to it today, feel free to PR -- otherwise will get it fixed and released by Monday :)

@seanmarpo was hoping to get to it today, feel free to PR -- otherwise will get it fixed and released by Monday :)

@grizz, thanks for patching this up. Can confirm the latest version works as expected. 👍

@grizz, thanks for patching this up. Can confirm the latest version works as expected. 👍


RFE: please provide update for httpcore 0.17

https://github.com/romis2012/httpx-socks/blob/271b5f2d11b12ab16841a7402536a1f6e0c41af2/requirements.txt#L2
https://github.com/romis2012/httpx-socks/blob/271b5f2d11b12ab16841a7402536a1f6e0c41af2/setup.py#L39-L42

The latest version of httpx (0.23.3) depends on httpcore<0.17.0,>=0.15.0, so we have the same dependencies

FYI: in unreleased commit that requirement has been changed https://github.com/encode/httpx/commit/46a5d38bd73caa31827c7da15e4fa30ad60b925f and looks like except formal requrement none of actual code changes was necessary to add.

...unreleased commit...

So we are waiting for the release

So in mean time you may add simillar commit 😋
Looks like none httpcore 0.17 changes makes adds API changes ..

It makes absolutely no sense right now

So we are waiting for the release

And it happened .. 😋

Updated in v0.7.6


Issue on Eclipse

Hi Simon
I am trying to use this parser inside a java codenameone app (https://www.codenameone.com/index.html) but when I run this app from eclipse the parser fail with the following error message:
java.lang.IllegalArgumentException: [c@68bd1b55 is not a valid WeekDay
	at org.tomlab.myapp.common.openinghours.WeekDayRange.setEndDay(WeekDayRange.java:205)
	at org.tomlab.myapp.common.openinghours.OpeningHoursParser.weekday_range(OpeningHoursParser.java:484)
	at org.tomlab.myapp.common.openinghours.OpeningHoursParser.weekday_selector(OpeningHoursParser.java:590)
	at org.tomlab.myapp.common.openinghours.OpeningHoursParser.rule(OpeningHoursParser.java:1214)
	at org.tomlab.myapp.common.openinghours.OpeningHoursParser.rules(OpeningHoursParser.java:1265)
	at org.tomlab.myapp.common.openinghours.OpeningHours.parseOpeningHours(OpeningHours.java:43)
	at org.tomlab.myapp.MyApplication.start(MyApplication.java:76)
	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:498)
	at com.codename1.impl.javase.Executor$1$1.run(Executor.java:134)
	at com.codename1.ui.Display.processSerialCalls(Display.java:1129)
	at com.codename1.ui.Display.mainEDTLoop(Display.java:924)
	at com.codename1.ui.RunnableWrapper.run(RunnableWrapper.java:120)
	at com.codename1.impl.CodenameOneThread.run(CodenameOneThread.java:176)

what is really weird is that, if I run the same project from inside netbeans, everything went fine....
So I don't really know what is going on with eclipse
I tried to debug the parser and here is the output for the Mo-Fr 10:00-24:00; input string:
Call:   rules
  Call:   rule
    Call:   comment(LOOKING AHEAD...)
<DEFAULT>Current character : M (77) at line 1 column 1
   No string literal matches possible.
   Starting NFA to match one of : { <HYPHEN>, <MINUTES>, <WS>, <MONTH>,
     <MODIFIER>, <AM>, <PM>, <NUMBER>, <WEEKDAY>,
     <HOLIDAYS>, <WEEKDAY3> }
<DEFAULT>Current character : M (77) at line 1 column 1
   Possible kinds of longer matches : { <WEEKDAY>, <WEEKDAY3>, <WEEKDAYDE>, <MONTH>,
     <HOLIDAYS>, <EVENTS> }
<DEFAULT>Current character : o (111) at line 1 column 2
   Currently matched the first 2 characters as a <WEEKDAY> token.
   Possible kinds of longer matches : { <WEEKDAY3> }
<DEFAULT>Current character : - (45) at line 1 column 3
   Currently matched the first 2 characters as a <WEEKDAY> token.
   Putting back 1 characters into the input stream.
****** FOUND A <WEEKDAY> MATCH (Mo) ******

      Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <"\"">
    Return: comment(LOOKAHEAD FAILED)
    Call:   year_selector(LOOKING AHEAD...)
<DEFAULT>Current character : - (45) at line 1 column 3
   No string literal matches possible.
   Starting NFA to match one of : { <HYPHEN>, <MINUTES>, <WS>, <MONTH>,
     <MODIFIER>, <AM>, <PM>, <NUMBER>, <WEEKDAY>,
     <HOLIDAYS>, <WEEKDAY3> }
<DEFAULT>Current character : - (45) at line 1 column 3
   Currently matched the first 1 characters as a <HYPHEN> token.
****** FOUND A <HYPHEN> MATCH (-) ******

      Call:   year_range(LOOKING AHEAD...)
        Call:   year(LOOKING AHEAD...)
        Return: year(LOOKAHEAD FAILED)
      Return: year_range(LOOKAHEAD FAILED)
    Return: year_selector(LOOKAHEAD FAILED)
    Call:   week_selector(LOOKING AHEAD...)
      Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <"week">
    Return: week_selector(LOOKAHEAD FAILED)
    Call:   date_selector(LOOKING AHEAD...)
    Return: date_selector(LOOKAHEAD FAILED)
    Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <":">
    Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <"24/7">
    Call:   weekday_selector(LOOKING AHEAD...)
      Call:   weekday_range(LOOKING AHEAD...)
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
        Visited token: <<HYPHEN>: "-" at line 1 column 3>; Expected token: <<HYPHEN>>
        Call:   weekday(LOOKING AHEAD...)
<DEFAULT>Current character : F (70) at line 1 column 4
   No string literal matches possible.
   Starting NFA to match one of : { <HYPHEN>, <MINUTES>, <WS>, <MONTH>,
     <MODIFIER>, <AM>, <PM>, <NUMBER>, <WEEKDAY>,
     <HOLIDAYS>, <WEEKDAY3> }
<DEFAULT>Current character : F (70) at line 1 column 4
   Possible kinds of longer matches : { <WEEKDAY>, <WEEKDAY3>, <WEEKDAYDE>, <MONTH> }
<DEFAULT>Current character : r (114) at line 1 column 5
   Currently matched the first 2 characters as a <WEEKDAY> token.
   Possible kinds of longer matches : { <WEEKDAY3> }
<DEFAULT>Current character :   (32) at line 1 column 6
   Currently matched the first 2 characters as a <WEEKDAY> token.
   Putting back 1 characters into the input stream.
****** FOUND A <WEEKDAY> MATCH (Fr) ******

          Visited token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
      Return: weekday_range(LOOKAHEAD SUCCEEDED)
<DEFAULT>Current character :   (32) at line 1 column 6
   Currently matched the first 1 characters as a " " token.
   Possible string literal matches : { " to " }
<DEFAULT>Current character : 1 (49) at line 1 column 7
   No string literal matches possible.
   No more string literal token matches are possible.
   Starting NFA to match one of : {  }
<DEFAULT>Current character : 1 (49) at line 1 column 7
   Currently matched the first 1 characters as a " " token.
   Putting back 1 characters into the input stream.
****** FOUND A " " MATCH ( ) ******

<DEFAULT>Current character : 1 (49) at line 1 column 7
   No string literal matches possible.
   Starting NFA to match one of : { <HYPHEN>, <MINUTES>, <WS>, <MONTH>,
     <MODIFIER>, <AM>, <PM>, <NUMBER>, <WEEKDAY>,
     <HOLIDAYS>, <WEEKDAY3> }
<DEFAULT>Current character : 1 (49) at line 1 column 7
   Currently matched the first 1 characters as a <NUMBER> token.
   Possible kinds of longer matches : { <HYPHEN>, <MINUTES>, <WS>, <MONTH>,
     <MODIFIER>, <AM>, <PM>, <NUMBER>, <WEEKDAY>,
     <HOLIDAYS>, <WEEKDAY3> }
<DEFAULT>Current character : 0 (48) at line 1 column 8
   Currently matched the first 2 characters as a <NUMBER> token.
   Possible kinds of longer matches : { <HYPHEN>, <MINUTES>, <WS>, <MONTH>,
     <MODIFIER>, <AM>, <PM>, <NUMBER>, <WEEKDAY>,
     <HOLIDAYS>, <WEEKDAY3> }
<DEFAULT>Current character : : (58) at line 1 column 9
   Currently matched the first 2 characters as a <NUMBER> token.
   Putting back 1 characters into the input stream.
****** FOUND A <NUMBER> MATCH (10) ******

      Visited token: <<NUMBER>: "10" at line 1 column 7>; Expected token: <",">
    Return: weekday_selector(LOOKAHEAD SUCCEEDED)
    Visited token: <<NUMBER>: "10" at line 1 column 7>; Expected token: <",">
    Call:   holiday_sequence(LOOKING AHEAD...)
      Call:   holiday(LOOKING AHEAD...)
        Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <<HOLIDAYS>>
      Return: holiday(LOOKAHEAD FAILED)
    Return: holiday_sequence(LOOKAHEAD FAILED)
    Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <",">
    Call:   weekday_selector(LOOKING AHEAD...)
      Call:   weekday_range(LOOKING AHEAD...)
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
        Visited token: <<HYPHEN>: "-" at line 1 column 3>; Expected token: <<HYPHEN>>
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
      Return: weekday_range(LOOKAHEAD SUCCEEDED)
      Visited token: <<NUMBER>: "10" at line 1 column 7>; Expected token: <",">
    Return: weekday_selector(LOOKAHEAD SUCCEEDED)
    Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <",">
    Call:   weekday_selector(LOOKING AHEAD...)
      Call:   weekday_range(LOOKING AHEAD...)
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
        Visited token: <<HYPHEN>: "-" at line 1 column 3>; Expected token: <<HYPHEN>>
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
      Return: weekday_range(LOOKAHEAD SUCCEEDED)
      Visited token: <<NUMBER>: "10" at line 1 column 7>; Expected token: <",">
    Return: weekday_selector(LOOKAHEAD SUCCEEDED)
    Call:   weekday_selector
      Call:   weekday_range
        Call:   weekday
          Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <<WEEKDAY>>
          Consumed token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>
        Return: weekday
        Visited token: <<HYPHEN>: "-" at line 1 column 3>; Expected token: <<HYPHEN>>
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
        Visited token: <<HYPHEN>: "-" at line 1 column 3>; Expected token: <<HYPHEN>>
        Call:   weekday(LOOKING AHEAD...)
          Visited token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>; Expected token: <<WEEKDAY>>
        Return: weekday(LOOKAHEAD SUCCEEDED)
        Visited token: <<HYPHEN>: "-" at line 1 column 3>; Expected token: <<HYPHEN>>
        Consumed token: <<HYPHEN>: "-" at line 1 column 3>
        Call:   weekday
          Visited token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>; Expected token: <<WEEKDAY>>
          Consumed token: <<WEEKDAY>: "[c@68bd1b55" at line 1 column 4>
        Return: weekday
      Return: weekday_range
    Return: weekday_selector
  Return: rule
Return: rules

You can see that after the ****** FOUND A <WEEKDAY> MATCH (Mo) ****** debug line, the Mo weekday token is converted into what seems to be an object reference ([c@6f80f69) in the token.image of the next debugged function (the jj_scan_token function that prints the Visited token: <<WEEKDAY>: "[c@6f80f69" at line 1 column 1>; Expected token: <"\"">  line).
The problem seems to occur into the getNextToken() function of the generated OpeningHoursParserTokenManager class but I really don't understand what might cause this and why the exact same code is working into netbeans and not into eclipse (I copy pasted the files from eclipse to netbeans and didn't regenerate them with javaCC so they are exactly the same).
Do you have any idea of what might cause this issue (this is kind of turning me crazy so I would really appreciate any sugestion ;) )

Ok found the source of the issue. Was due to codenameone not handeling StringBuilder.append(char[]) (that default into StringBuilder.append(Object), hence the issue...). Still don't know why it was working into netbeans and not into eclipse but at least I could fix the issue ;)


Crash when pane/(v)split widthe is smaller than ruler size

Description of the problem or steps to reproduce

Open two bufpanes in split mode
Set ruler enabled for at least one of them
Drag the divider line to the side

When width of the pane is smaller than it is ruler size it crashes. If the pane doesn't have the ruler everything works good
Specifications

Commit hash: v2.0.13 68d88b5
OS: Debian 12
Terminal: foot

Hm, strange. I can't reproduce this.
Do you receive a backtrace?
Can you please try a different terminal?

Ok. I just tried with gnome terminal with the same result. And I understood my mistake in describing the issue. Did you tried to move the divider line to both sides?

I'm at a Debian testing with gnome console (kgx), opened an empty micro, used vsplit to create the splits, both of them have the ruler enabled (by default due to ´settings.json´) and moved the divider to the left and to the right.
The only issue I can currently see is, that in the moment the divider is on the top left position the starting character of the file name will be removed.

When you said backtrace you meant this?
Micro encountered an error: runtime.errorString runtime error: makeslice: cap out of range
runtime/slice.go:33 (0x450305)
runtime/slice.go:33 (0x4502ed)
github.com/zyedidia/micro/v2/internal/display/bufwindow.go:605 (0x88d910)
github.com/zyedidia/micro/v2/internal/display/bufwindow.go:788 (0x8901dc)
github.com/zyedidia/micro/v2/cmd/micro/micro.go:407 (0x8ecad4)
github.com/zyedidia/micro/v2/cmd/micro/micro.go:394 (0x8ec212)
runtime/proc.go:250 (0x43af12)
runtime/asm_amd64.s:1594 (0x46a961)

I tried to understand where it is but it was just in front of me

Ok. I just tried to open with empty micro because didn't do it earlier. Opened empty micro, vsplit, but crash

Yeah they are active. You are right I just disabled them and they work


Multiple options with the same name within the same section

Patrick C. reported that configparser was missing the ability to parse multiple options with the same name and offered a patch.  I went ahead and integrated his changes and handled another edge case where the same section could appear multiple times (I chose a merge strategy for that).
The patch is now applied in 0.1.7 and has been released as a Rubygem.

Fixed in 0.1.7


"I Want to Volunteer" button is broken

The volunteer button on https://www.techlahoma.org/get-involved/ redirects to the same page.

Fixed.


[Azure][GCP] Change all test/example OS images to Ubuntu

GCP integration test is failing for #401 merge due to Debian 10 reaching its end of life. This doesn't affect Azure tests because those use Ubuntu 22.04.
I updated everything (i.e., GCP tests, GCP docs, and Azure docs) to use Ubuntu 22.04. Azure tests require Ubuntu 22.04 due to the network watcher extension, so I figured it's best if we make it clean and make everything use Ubuntu 22.04. I believe IBM already uses it as well.

Closing as this is included in #414.


Mark GitHub repo "releases" for significant changes to the handbook

When significant changes are made to the handbook, can it be tagged as a new release/version? For added goodness, have the creation of the new release be posted to slack so people know to look for the changes.
I ask because right now, there is no way to know when (like say the changing to the current-events channel or more recently, the new tech reimbursement policy). I've found out about some changes that were officially live in the handbook only after being verbally told of them... even though I had already heard in AHC that they were "being worked on". This has happened to me multiple times, most recently this week about the tech stipend.
Following the GitHub repo for changes is too noisy, as there are so many other changes for typos and smaller non-significant changes. In GitHub, when following a repo, you can choose to only be notified of "releases". This would be perfect. But it requires a human to tag a new release - and it looks like we have not done this.
Not sure who to ask, hence creating this issue to track.

I made an initial v1.0 release and configured Slack to post (only) these to #announcements


Logging activity in terminal when unauthorized consumes a lot of CPU.

octant: stable 0.9.1
Because of the excellence of Octant, I solved the problem I was troubleshooting with my CRDs quite quickly, but neglected to terminate Octant. I have temporary credentials with this cluster, so eventually Octant started complaining about access. The first indication of this was excessive fan noise from my laptop. A survey of processes showed multiple log entries per second in the Octant terminal tab to the effect of: E1114 19:39:36.368682   27217 reflector.go:125] github.com/vmware-tanzu/octant/internal/objectstore/informer.go:63: Failed to list *unstructured.Unstructured: Unauthorized
Terminating Octant terminated the fan noise.

This is a problem we need to some up the a good solution for.
@bryanl and @GuessWhoSamFoo We will probably end up having to vendor the part of the code that logs out the error. Currently we pass off control to this reflector code and if our authorization fails/goes away, we have no way of interrupting the control flow.
related #207


Consuming Faults does not fire in .net core 2

Is this a bug report?
yes
Can you also reproduce the problem with the lastest version?
yes
Environment

Operating system: Windows 10
Visual Studio version: 2017
Dotnet version: .net core 2

Steps to Reproduce

Register mass transit consumers:

Bus.Factory.CreateUsingRabbitMq(cfg =>
            {
                var host = cfg.Host(new Uri(this.GetUriString()), h =>
                {
                    h.Username("Test");
                    h.Password("Test");
                });
                cfg.ReceiveEndpoint(host, "TestQueue", e =>
                {
                    e.LoadFrom(serviceProvider);
                });
            });

Register consumers in .net core service provider:

services.AddMassTransit(c =>
            {
                c.AddConsumer<TestConsumer>();
                c.AddConsumer<BaseFaultConsumer<TestConsumer>>();
            });

Throw exception in TestConsumer.

Expected Behavior
Fault consumer fires after retry policies.
Actual Behavior
Seems like fault consumer does not exist and its consume method is not fired.

Nah, it works as expected! It was my fault passing consumer, but not the consumer message object.


Remove default CSS

Ember Shepherd comes with a lot of CSS.
Is it possible prevent this css to be added to the DOM?

@cbou I believe you'll need most of it or Shepherd will not function as intended. Can you say more about your use case please?


[core]Decompile error, missing a lot of code

link:https://drive.google.com/file/d/1w3ZTTSDu54qrSfao7KfDlmffId3MKTWO/view?usp=sharing
class:com.meituan.android.common.mtguard.wtscore.plugin.sign.core.a
method:private static URI a(Context context, URI uri, boolean z, byte[] bArr, String str, String str2, Map<String, String> map, String str3, Map<String, String> map2)
jadx decompile error, by comparing, you can find a lot of missing code.

Which Jadx version do you use?

Which Jadx version do you use?

https://github.com/skylot/jadx/commit/b50706505f3f5ea562239b68710f9ab34e55a570
openjdk8

@bhwxha No, I was simply asking because you forgot to mention it. As you may have noticed there quite a few Jadx issue reports open. Unfortunately I don't have the experience to help skylot with the decompiler core system, thus I am trying to focus on checking issues are relevant and e.g. do not refer an outdated Jadx version.
Regarding the code snippets you have posted I have to admit that I don't see some invocations both versions have in common.  So the only outcome I can derive from them is that there might be something wrong with the decompiled code of the mentioned method.

@skylot You can search for "System.arraycopy" in this class and you will find the following.
    /* JADX WARN: Code restructure failed: missing block: B:45:0x0171, code lost:
        r0 = r0.getBytes();
        r3 = java.lang.Math.min(r1.b.c().length, 16200);
        r4 = new byte[r0.length + r3];
        java.lang.System.arraycopy(r0, 0, r4, 0, r0.length);
        java.lang.System.arraycopy(r1.b.c(), 0, r4, r0.length, r3);
        r0 = r4;
     */

jeb

This, shows that the pseudo-code is indeed missing quite a bit.


Schoology Integration (again)

Desolee pour les shenanigans.

Bumping some previous comments from the old PR:
KNOWN ISSUES:

[ ] (important) Sgy data loses state and attempts to refetch when switching from then to the classes tab. This is a major problem that will probably involve moving the sgy context from classes to layout
[ ] The "next school day" issue still exists. Checking classes during an ongoing school day will insist the next school day started some hours ago. Perhaps either only display the next school day or have some text that school is in progress, started x hours ago.


UNet for non-square input images?

When I train a model with square input size, all goes well. However, when I train a model with an input layer of, for example, 512x768, the training loss increases to up to 97% but the output is almost completely empty.
Anybody succeeded using UNet with a non-square input size?

yes, you can. But you need to know that the u net output is actually probability rather than pixel value. So what I did was multiply a constant and take threshold to get the segmentation result

Turns out it was a matter of unbalanced data, had nothing to do with the input ratio.

Hi @Attila94
Are you also making predictions on non-square images?  This is something I'm struggling with right now.  If I want to make a prediction, I need to segment my image into square subsamples, and I don't like that.

Could you solve it? I am struggling to train a UNET CNN with rectangular images 512x896

I'm not sure what the issue is but it has probably nothing to do with the input shape - UNet works for all input sizes.


snapshot: add idempotency of create and backup

PR at: https://github.com/rancherio/cattle/pull/400 and https://github.com/rancherio/python-agent/pull/116


[REQ]Slash Commands For Horace

Horace needs to be integrated with the slash commands newly introduced by discord

Thanks for the request. We've intentionally decided not to use slash commands on Horace for now.


CASMCMS-9118: Improve BOS resiliency by using requests_retry_session module

This updates BOS to use the new requests_retry_session Python module, rather than duplicating the code.
Backports:
1.5.3: https://github.com/Cray-HPE/csm/pull/3603
1.4.5: https://github.com/Cray-HPE/csm/pull/3604
node-images PR:
https://github.com/Cray-HPE/node-images/pull/1140

Folding this into https://github.com/Cray-HPE/csm/pull/3595


Flashing tuya zigbee Gateway

Hi,
I was trying do dump their gateway flash to be able to root it at accedently erased it, maybe someone has this type of device and can dump his flash it's simple 16Mb SPI flash chip, reset it before dumping thanks.

Hi @RomSand
Could you please clarify? It's not clear what you did and what you're asking for. Is this a tuya-convert issue?

If I understand correctly, you did not use tuya-convert (because it does not simply erase your flash) in which case this is not the right place to ask. This issue tracker is for issues with tuya-convert only.
I'm also not sure what you mean by "root" your Tuya device as it's not running *nix.
Lastly I should warn you that if you try using stock firmware from another device it will not work, as each device is assigned a unique auzKey.

I have Tuya smart gateway TYGWZ-01 it's based on ralink chip and runing Linux,
I tried to dump SPI flash that soldered on the board but accedently erased it. need a good dump so I can recover my device and continue my work... Thanks.
I think there is account information in the gateway that's how it authenticates on the server that's why after receting the device it suposed to be erased...
Thanks.

This issue tracker is for tuya-convert issues only so I kindly request that you move this to a more appropriate forum. I will however repeat my warning for emphasis, you cannot use the stock firmware from another device as each device is programmed with a unique auzKey at the factory, and thus you will not be able to authenticate.


Fix state change problems.  Fix typo in logout code.

Overall
This fixes the state change success problems by issuing a $timeout with $apply.
This also fixes the typo in logout.

Fixes: https://github.com/angularjs-oauth/oauth-ng/issues/118

Fixes: https://github.com/angularjs-oauth/oauth-ng/issues/117

@bramski Good catches. Thanks!


Reverts mac specific coverage hacks

Reverts mac specific hacks to tests and adds instructions on how to install supported Python versions on Mac.
cc @odelalleau - Please try to follow the instructions and make sure you can make it work before I land this.
I got it to work and it's actually quiet nice.

Reverts mac specific hacks to tests and adds instructions on how to install supported Python versions on Mac.
cc @odelalleau - Please try to follow the instructions and make sure you can make it work before I land this.

I'm afraid I was unable to get it to work the way I'd want it to. I used pyenv to install a 3.6.11 Python, then pyenv local system 3.6.11, but unfortunately python3.6 is still using my system Python (3.6.2), so nox -s coverage-3.6 fails. Interestingly, it even fails with pyenv local 3.6.11 (and same thing for pyenv global 3.6.11), even though python3.6 correctly points to 3.6.11... I'm a bit confused (and I deleted my .nox folder before each test)


Update client-config.md

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "vikstrous-patch-1" git@github.com:docker/notary.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

thanks for copying to change to the docs repo before I even made it :P

LGTM, thanks again for noticing and fixing this :)
And yeah, I just went ahead and made the change since it was so quick -- edited my original comment above with the PR link


vllm应该已经支持lora了吧

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
Traceback (most recent call last):
  File "/hy-tmp/llama-factory-1/LLaMA-Factory-main/src/api_demo.py", line 16, in <module>
    main()
  File "/hy-tmp/llama-factory-1/LLaMA-Factory-main/src/api_demo.py", line 9, in main
    chat_model = ChatModel()
  File "/hy-tmp/llama-factory-1/LLaMA-Factory-main/src/llmtuner/chat/chat_model.py", line 21, in __init__
    model_args, data_args, finetuning_args, generating_args = get_infer_args(args)
  File "/hy-tmp/llama-factory-1/LLaMA-Factory-main/src/llmtuner/hparams/parser.py", line 265, in get_infer_args
    raise ValueError("vLLM engine does not support LoRA adapters. Merge them first.")

在参数解析的时候直接把lora给挡住了
Expected behavior
No response
System Info
No response
Others
No response

没有对所有模型支持

没有对所有模型支持

我想知道，如何做这个 merge 操作呢

合并模型权重，可以参考这篇文章：https://zhuanlan.zhihu.com/p/689333581

@JieShenAI https://github.com/hiyouga/LLaMA-Factory/blob/main/examples/merge_lora/merge.sh

@JieShenAI https://github.com/hiyouga/LLaMA-Factory/blob/main/examples/merge_lora/merge.sh

Thank you, it work.


Component: Supply HTML string

There's currently no way to append HTML directly in a component's render method. We should have a .html() method, like in jQuery:
var el = $$('div').addClass('html-container').html('foo');

Not sure if this should work only for HTML constructors or also for custom components. This could potentially conflict with a component's render method. E.g. when you do
var el = $$(MyComponent).html('foo');

Will MyComponent.render be called then? And then overridden? It seems like a bad idea to allow that, but on the other hand the Component API should be consistent.

Yeah. Consistency first.. if the user does this, it would overwrite anything appended before. That is also what $().html() does, isn't it?

@michael to you know a cool way to make this 'safe' against script injection?

This looks reasonable: https://github.com/cure53/DOMPurify

But actually, this should be done by the app.
$$('div').html(dompurify(unsafeHtmlString))

First iteration done. fc3f46149b32d4aca0e6a0d89094adb3de0621d3

Works for me. Will write tests tomorrow.


no patrol files generated if on livonia map

We are running a Livonia map and although the AI work as intended there are no patrol files to change the dynamic patrols or to initially set them up

Having same problem


Fix bug in BernoulliDropout

Divide activations by (1-weight) rather than weight

Can you explain why this is the correct scaling factor instead of just weight?

Consider the case where weight = 0.1. This means that 0.9 of the
activations remain, while 0.1 are zeroed out. In order for the total
activation to be on average the same as before, the remaining activations
are scaled up. The current code would scale it up by 10 times (i.e. 1 /
weight), which is wrong, since 0.9 of the activations remain -- the total
activation would now be on average 9 times the original. The correct
scaling is by 1 / 0.9, so you should be dividing by (1 - weight), not
weight.
In addition, I have been testing with the new (1 - weight) scaling in my
own application using my own fork, and I get much better performance both
in and out of sample.
Regards,
David Khoo
On 20 March 2016 at 12:46, Leif Johnson<EMAIL_ADDRESS>wrote:

Can you explain why this is the correct scaling factor instead of just
weight?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/lmjohns3/theanets/pull/123#issuecomment-198846229

Ok, fantastic, thanks for the explanation!


Add Sam-HQ support?

MobileSAM & FastSAM are "fast", but there is also another direction: https://github.com/SysCV/sam-hq — it would be wonderful if you could add support for it as well :)

Thank you! I'll give it a try to add support for HQ-SAM.

HQ-SAM is now supported in v1.5


test, tsp on eventgrid

target PR https://github.com/Azure/azure-rest-api-specs/pull/23539
commit e4d61a94c7a996c91c2c632874926a9b7135c31a
only for preview of 0.6.1 typespec-java
conflict files is skipped, including module-info.java and ServiceVersion.java
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-messaging-eventgrid


Precompile fomantic-ui files

We rarely change fomantic-ui or its configuration so it's kind of a waste to have it rebuild on every CI run. These changes remove the fomantic files from the build and instead add the relevant output files to the git index, which should shave of 2-3 minutes on every CI run.
make fomantic should still work and should be ran whenever fomantic is updated or its configuration is changed.

Codecov Report

Merging #13332 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #13332      +/-   ##
==========================================
- Coverage   42.13%   42.11%   -0.02%
==========================================
  Files         689      689
  Lines       75845    75845
==========================================
- Hits        31956    31942      -14
- Misses      38658    38668      +10
- Partials     5231     5235       +4

Impacted Files
Coverage Δ

modules/indexer/stats/db.go
52.17% <0.00%> (-8.70%)
:arrow_down:

modules/charset/charset.go
68.53% <0.00%> (-4.50%)
:arrow_down:

modules/git/utils.go
73.77% <0.00%> (-3.28%)
:arrow_down:

modules/queue/workerpool.go
58.77% <0.00%> (-1.23%)
:arrow_down:

modules/git/repo.go
46.19% <0.00%> (-0.51%)
:arrow_down:

services/pull/pull.go
40.78% <0.00%> (-0.50%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7dfb2fc...34a0949. Read the comment docs.

Oddly, the fomantic build still seem to have ran on the master build https://drone.gitea.io/go-gitea/gitea/31821/1/7 but not on the PR build https://drone.gitea.io/go-gitea/gitea/31812/1/7.


Mark Id as ResourceIdentifier or Guid

Find a way like using format or swagger extension to mark an Id property as a ResourceIdentifier or Guid.
Take the ResourceId in CosmosDB as an example (check this PR) for test, currently it's generated as string.
References:

TypeFactory generates different types based on schema type, if it's extensible, we can add a new one like "format":"armId" in swagger and update the logic here: https://github.com/Azure/autorest.csharp/blob/7b745f268dc9280af120e5b165f796d563b1681d/src/AutoRest.CSharp/Common/Generation/Types/TypeFactory.cs#L153-L171
Data types for the format: https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#data-types

format only supports a known list of values, so in #2051 I used x-ms-format to support other values including arm-id for ResourceIdentifier.


Added all text ops to functional

Description

Added all text ops to functional.py along with doc strings showcasing usage

Testing
pytest torcharrow/test/transformation/test_text_ops.py

Thanks! These docs are nice!

@wenleix @parmeet thanks for the feedback! I should have resolve your PR comments. @wenleix just wanted to see if you could give the changes one more pass before I merge this in 😄

Also make sure to squash commits into one before merge :)

Also make sure to squash commits into one before merge :)

I enabled the "squash and merge" option on github so hopefully we don't need to run squash commands anymore :D


fix: mime type string deprecation

mime-types 3.6.0 warns "MIME::Type.MIME::Type.new when called with a String is deprecated."
change introduced in and syntax borrowed from:
https://github.com/mime-types/ruby-mime-types/commit/8512c1544e9b4a292284865c4d0c2b04e126fcc7

@avk Thank you for this PR! While we're here, I added a commit which bumps the minimum version of the mime-types gem to 3.3.0, which is the first version that supports Ruby 2.7+.

Released in https://github.com/sparklemotion/mechanize/releases/tag/v2.12.2


Continuous connection question

I had the same question as Shayo, but his thread is ignored because it isn't according to the template.
Original question:

This is a question, not a real issue.
What are the rules regarding ConnectToKnownDeviceAsync ?
When does it fail / time out?
How do I use the cancellation token to indicate to stop this operation?
I basically want to have a thread that continuously searches for a known device and tries to maintain connectivity with it. What's the best way to achieve this?
(i.e., try to connect, if fail after some predefined amount of time, try again).

The rest of the template is from my own project.
Steps to reproduce

No steps, it's just a question

See step 1

See step 2

Expected behavior Tell us what should happen:
I want to connect to a device, when connected I expect to also see it in the settings as connected.
Actual behavior Tell us what happens instead:
It seems my device isn't really connected to my phone. When I check the bluetooth in settings there is no connection
Crashlog
No crash
Configuration
Version of the Plugin: e.g. 1.3.0
Platform: Xamarin.Forms Android 7.0
Device: e.g. Samsung Galaxy S6 Edge

#273


Update Pull Request

Description
Hi, I Have Update My Pull Request For Doing Your Task About Dart Easy Challange,
I also add new challange for your repo on dart easy. Please Accept And Give Me Label Hacktoberfest, Thanks You
Additional Context

Iam doing this task https://github.com/nikohoffren/fork-commit-merge/issues/601

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Add support for using route or service as target endpoints in the test suite

The issue resolved by this Pull Request:
Resolves partially RHOAIENG-10212
Description of your changes:
This PR introduces enhancements to the test suite by allowing the use of either a route or a Kubernetes service as the target endpoint for interacting with the Data Science Pipelines Operator (DSPO).

New --endpointType Flag:

A new --endpointType flag is introduced in the test suite configuration, which specifies whether the test should use a Kubernetes service (service) or an OpenShift route (route) as the target endpoint for DSPO.

Infrastructure Cleanup Option:

The --cleanup flag is renamed to --clean-infra. This option allows automated cleanup of infrastructure before rerunning tests.

Modifications in Test Scripts:

Updated the shell scripts and Go test files to accommodate the new endpoint selection mechanism.
The HTTP client in the tests is now initialized with custom transport to support token-based authentication when necessary.
Various test functions now rely on the Clientmgr.httpClient to perform HTTP requests, decoupling from the standard Go http package.

New Test Resources:

Two new DSPA (Data Science Pipelines Application) YAML resources (dspa.yaml and dspa-external.yaml) are added for testing RHOAI.

Test Case Improvements:

Improved the pod listing logic by retrieving only running pods, ensuring the test suite can be rerun multiple times without issues.

Testing instructions
No manual testing required.

kind it is done by GHA
rhoai: a new PR will be added soon to allow passing: -endpointType via test.sh. If you wish to test RHOAI ( please call me first ) do the following:
** Modify Makefile and append -endpointType=route in the integrationtest
** Checkout https://github.com/diegolovison/ods-ci/tree/e2e
** From your local machine:
*** oc login ....
*** sh run_robot_test.sh --set-urls-variables true --extra-robot-args '-L DEBUG -i ODS-2632' --skip-oclogin

Checklist

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work

@diegolovison will provide a follow up pr to address the changes
/lgtm
/approve


Make ccd_nmatch more meaningful?

Or add another column, per Eddie's suggestion, of the number of stars photometered to have flux > 5 sigma.

It turns out that ccd_nmatch actually counts the number of stars that pass a sigma-clip before we compute ccdzpt_rms, here:
https://github.com/legacysurvey/legacyzpts/blob/master/py/legacyzpts/legacy_zeropoints.py#L1285
so it actually is useful, along with the photometric scatter.


[request] Old layout for cast

IMDb now forcefully brings the old layout https://www.imdb.com/name/nmXXXXXXX/fullcredits to the new layout, which is messy and cluttered.
Would it somehow be possible to make the script force the old fullcredits layout for cast when https://www.imdb.com/name/nmXXXXXXX/ is visited?

Would it somehow be possible to make the script force the old fullcredits layout for cast when https://www.imdb.com/name/nmXXXXXXX/ is visited?

There is already this option implemented in the script to force "fullcredits".

IMDb now forcefully brings the old layout https://www.imdb.com/name/nmXXXXXXX/fullcredits to the new layout, which is messy and cluttered.

Nothing I can do if they removed "fullcredits" page, ask them to bring it back there:
https://community-imdb.sprinklr.com/conversations/imdbcom/add-a-contributor-text-view-for-name-credits


Fix hyperlink error

Description

Urgency

[ ] Blocker
[ ] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

Can one of the admins verify this patch?

@Romathonat this link actually works fine in the rendered output of the site: https://dcos.io/docs/1.9/overview/high-availability/, but not directly form GH. it's a known issue that we have to format our links that end in parenthesis like this. see the README for more info: https://github.com/dcos/dcos-docs#styling-and-formatting-your-contribution.


building out to device

Hello,   so I’m getting a "no file error for QRCodeDynamic. framework" in the DerivedData folder when I build the app to my device, it builds fine using the simulator..  Packages are installed fine.
Also, It builds fine to my device using your repository file.
Any ideas?
Thanks,

Are you sure your project is copying (embedding) the QRCodeDynamic.framework into your frameworks folder of your app?

Hi @dagronf , that worked (:   Apparently it wasn't embedded when the packages was installed.  hmm.  I guess it's a manual process, unless my project was a one off that didn't do it.    btw, awesome job on this app you built..  Thank you!

Hi @omendez11 , glad to hear that fixed your issue.  Xcode can be a little scatterbrained at times!  I've bumped into a similar issue on another project where I was sure I'd marked the embed framework to copy but for some reason Xcode 'forgot' to add the stage.
Many thanks mate.  Have a great weekend!


[3462] Map other gender from DTTP to other in register

Context
The current implementation was mapping a value of "other" gender in DTTP to "gender_not_provided" in register.
Changes proposed in this pull request
Prefer :other if gendercode is 389040000. This conversion is lossless in this context, since any update to dttp would map it to the same gendercode.
Important business

~Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?~
~Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?~

 [] Decision on mapping ambiguous trainee gender


'NoneType' object is not subscriptable

When I'm trying to start bot I get this error

Solved wrong discord token


Parallel deploy app to cf platform with pipeline,happened cf login problem

when i parallel deploy my app to cf,it's occured following problem occasionally:
Warning: Error read/writing config: unexpected end of JSON input for /root/.cf/config.json
i've tried something method as follow:
1)change CF_HOME to another folder
2)chmod 755  ~/.cf/config.json
3)and login in every parallel stage
but still not work.
The cf version and cli version is latest.
i hope someone can give a solution, the problem already troubled me for a long time

Hi @bad2cat thanks. Could you provide details on the operating system you are using. Also, please review, if you haven't already, closed issues which might be a related issue. For example: https://github.com/cloudfoundry/cli/issues/1199

Hi @abbyachau thanks for reply.I've already review the related issue.
And i've tried methods which mentioned in related issue,but still not resolved this problem.
I use k8s cluster,the CLI is run in pods which pulled cli image from private repo every time.

Hey @bad2cat this is going to be difficult for us to help you debug unfortunately; the quickest way to get help is to perhaps go on Slack #cloudfoundry and see if anyone can help you with your specific question. It is a good place for the Community to ask questions and to see if anybody else has a similar issue. I'm closing this issue, thank you.


Remove tolerance on pointInPolylines to fix boolean line-type flipping

As described in issue #420, checking if a point is within a very small epsilon of of a polyline's border and counting it as outside if so leads to inside-segments with points very close to the border registering as outside segments in cutcover (test case). Deleting it doesn't seem to have any adverse effects and fixes it.

In case the share link expires, here's the test case:
const width = 125;
const height = 125;

setDocDimensions(width, height);

let a = [[[69.99990000000001,65.00000],[57,65]]]
let b = [[[53,70],[70,70],[70,53],[53,53],[53,70]]]

bt.cover(a, b)
bt.join(a, b)

drawLines(a)

To clarify this behavior is wrong since because we're using cover we'd expect this line to be covered by the square but it's not because of this bug

Let's merge it and see what happens. Looking forward to seeing your town.


InMemoryDatabase provider not persisting data in test method.

I'm trying to write an integration test using the InMemoryDatabase, however I'm finding the data not persisting from the context resolved by the container in the repository and the one I resolve in my test.
I can see that when SaveChanges() is executed the database contains the entity. But then it is empty in the test method when I want to verify the dbset contains at least one record.
Steps to reproduce
Test Method:
        [Fact]
        public async Task TestMethod()
        {
            var entryPoint = Server.Host.Services.GetService<IEntryPoint>();

            using (var scope = Server.Host.Services.CreateScope())
            {
                var context = scope.ServiceProvider.GetService<MyDbContext>();
                await entryPoint.Start();
                Assert.True(await context.EntityTable.CountAsync() > 0);
            }
        }

IntegrationTests Base Class:
I use this class to setup the test server and register all services with container.
public class IntegrationTests
    {
        protected TestServer Server;

        protected IntegrationTests()
        {
            Server = new TestServer(new WebHostBuilder()
                .UseStartup<Startup>()
                .UseEnvironment("IntegrationTests"));
        }
    }

Startup:
        public void ConfigureServices(IServiceCollection services, IHostingEnvironment hostingEnvironment)
        {
            services.AddTransient<IEntryPoint, EntryPoint>();
            services.AddScoped<IMyRepository, MyRepository>();

            if (hostingEnvironment.IsEnvironment("IntegrationTests"))
            {

                services.AddDbContext<MyDbContext>(options =>
                    options.UseInMemoryDatabase("IntegrationTestDatabase"));
            }
            else
            {
                services.AddDbContext<MyDbContext>(options => options.UseSqlServer(ConnectionString));
            }
        }

Repository Class:
public class MyRepository : IMyRepository
    {
        private readonly MyDbContext _myDbContext;

        public MyRepository(MyDbContext myDbContext)
        {
            _myDbContext = myDbContext;
        }

        public async Task Create(MyEntity myEntity)
        {
            _myDbContext.EntityTable.Add(myEntity);
            await _myDbContext.SaveChangesAsync();
        }
    }

Further technical details
EF Core version: 2.0.3
Test Framework: xUnit 2.3.1
IDE: Visual Studio 2017 15.6.7

@JakeFrancis The usual cause of issues like this is a different internal service provider being used where the DbContext instance is created to insert the data compared to where it is created to read the data. This matters because the in-memory data is rooted in the service provider.
#9613 is the issue for this. Things to try:

Make sure that the DbContext is added to and resolved from the service provider in the same way everywhere. That is, don't mix AddDbContext with using new in other places.
Make sure that anything like Loggers are configured exactly the same, since changes in these between context instances can cause EF to rebuild it's service provider.

If this doesn't help, then please post a runnable project/solution, github repo, or code listing that demonstrates the behavior you are seeing so that we can investigate.

Having looked at issue #9613 and the merge into 2.1.0-rc1-final: https://github.com/aspnet/EntityFrameworkCore/commit/c1bf9cc33d0b9b3b2b1f4c74a65daa202c3bd06c
I was able to get it working by updating to 2.1.0 rc1 a passing the in InMemoryDatabaseRoot object when registering the DbContext in Startup.


WebBasket: more robust tmpl_create_pseudo_item()

Originally on 2011-03-02
Function webbasket_templates.tmpl_create_pseudo_item() does fail when it is trying to extract the information to display from the DB-stored HB representation. The following can occur when the HB output does not have the expected format (i.e. not on 3 lines, with title, abstract and URL)
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/invenio/webinterface_handler.py", line 376, in _handler
    return root._traverse(req, path, False, guest_p)
  File "/usr/lib64/python2.4/site-packages/invenio/webinterface_handler.py", line 224, in _traverse
    return obj._traverse(req, path, do_head, guest_p)
  File "/usr/lib64/python2.4/site-packages/invenio/webinterface_handler.py", line 237, in _traverse
    result = _check_result(req, obj(req, form))
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket_webinterface.py", line 1271, in display_public
    ln=argd['ln'])
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket.py", line 136, in perform_request_display_public
    ln)
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket.py", line 232, in __display_public_basket
    ln)
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket_templates.py", line 2957, in tmpl_public_basket
    ln)
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket_templates.py", line 3108, in tmpl_public_basket_content
    ln=ln)
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket_templates.py", line 3199, in __tmpl_public_basket_item
    out = out % {'count': count,
  File "/usr/lib64/python2.4/site-packages/invenio/webbasket_templates.py", line 3713, in tmpl_create_pseudo_item
    (es_title, es_desc, es_url) = tuple(item.split('\n'))
ValueError: need more than 1 value to unpack
Locals by frame, innermost last

The function should at least be more robust, if not smarter.

Fix has been proposed in the past. Closing for 5 years inactivity. cc @inveniosoftware/triagers


fix: Fix the problem of cookie invalidation caused by leetcode_china changing domain name

leetcode-cn.com to leetcode.cn

@tenfyzhong PTAL

ERROR: Leetcode session cookie not found. Please login in browser

Hi, this repository is no longer maintained. I recommend you to submit this commit into my repository - https://github.com/mbledkowski/neuleetcode.vim

I merged it within https://github.com/mbledkowski/neuleetcode.vim


Fix greedy regex matching too much

Fixes asottile/seed-isort-config#40.
Build succeeded in my private Azure DevOps pipeline (I can't make that project public, as I have private repos there).
Tests against https://github.com/jmknoble/testcase-seed-isort-config perform as expected.

thanks again!


Refactor size constant as a SizeStrategy

This refactor introduces the SizeStrategy that will allow slices in the next step.

Addressed your comments and rebased to fix the conflict

Addressed issues and squashed

Great, thanks. :)


Additional back end enpoints/ views on entities

Now that we are in full api call mode we might find out we want more information when getting a certain entitiy or that we want an additional search method. If that's the case, please request it within this issue. Kasper and I will then implement that feature asap. I also assigned our API manager Thomas.

It became clear in #361 that a user by edition search is needed. https://github.com/SELab-2/OSOC-6/pull/361#discussion_r862470341

Can you add an endpoint to filter the students by their status?

Woeps, this should not have been closed?

@andpuydt requested an endpoint to get all skillTypes

We need an assignment endpoints that only gets the valid assignments.

Same as above but looking at it from the project. And also just remove the isSuggestion.

We are done, so I'm closing this.


Ubuntu 24.04 howdy 3.0.0 beta installation

I found many issues related to Ubuntu 24.04. However, they are messing up different howdy versions and don't solve the problem. So, I decided to create this issue and post my working solution.

Clone the project with version 3.0.0 beta
Edit meson.options and modify option('install_pam_config', type: 'boolean', value: true, description: 'Install pam config file (for Debian/Ubuntu)'). Build and install as mentioned in README. I have no idea why this isn't a default behavior.
sudo howdy add. It might give errors. Most python modules can be installed using apt except dlib.
sudo pip3 install dlib --break-system-packages. Try to add face again. It will ask you to run a script to download models. Chinese users may have network problems. Check the script and manually do that.
Config the camera https://github.com/boltgolt/howdy/wiki/Common-issues#error-when-trying-to-add-a-face-model
Now, you can add and test the face. Authentication for sudo should work now.
The login face recognition still has a problem. You need to manually modify /usr/local/lib/x86_64-linux-gnu/howdy/compare.py. Add sys.path.append('/usr/local/lib/python3.12/dist-packages') after the import sys line.
The new version has a GUI utility howdy-gtk. Python module elevate is needed which is also not provide by apt. sudo pip3 install elevate --break-system-packages. With sudo howdy-gtk, you get the following GUI:

Thank you so much!  Personally I also had to add the following to the top of /etc/pam.d/common-auth in order to get the PAM integration to work.
auth sufficient /usr/local/lib/x86_64-linux-gnu/security/pam_howdy.so

I think you posted this somewhere else, but it's here for reference.

I thought step 2 would do this (Install pam config file). Sorry for not testing this step. I found a file named /usr/share/pam-configs/howdy (Maybe created by previous install) and I modified it with the following content:
Name: Howdy
Default: yes
Priority: 512
Auth-Type: Primary
Auth:
	[success=end default=ignore]        /usr/local/lib/x86_64-linux-gnu/security/pam_howdy.so

Maybe you will have to run sudo pam-auth-update and enable Howdy there.
After this, the common-auth is automatically modified with the following line:
auth	[success=3 default=ignore]        /usr/local/lib/x86_64-linux-gnu/security/pam_howdy.so

The meson build default prefix (for me) seems to be /usr/local, so the howdy pam config ends up in /usr/local/share/pam-configs/howdy, and so pam-auth-update does not detect it.
Sym linking /usr/local/share/pam-configs/howdy to /usr/share/pam-configs/howdy seems to work for me.


Support Java 16

Starting with version 21.1.0, GraalVM offers experimental Java 16 support. Can support for these builds be added?
Edit: It looks like these builds are supported when installing, but not when listing all available versions

JDK16 is no longer supported but there's now a GraalVM JDK17.

Does https://github.com/halcyon/asdf-java/ work for you with GraalVM?
It lists the correct versions of Java for a given GraalVM release.


feat: Add support for specific GCP format for build-vm-image task

Add supporty for specific GCP disk image format in build-vm-image task
Original support from BIB was made in this PR: https://github.com/osbuild/bootc-image-builder/pull/646
Edit: I also checked the release pipeline, it should be ok to have a .tgz: https://github.com/hacbs-release/app-interface-deployments/blob/main/internal-services/catalog/pulp-push-disk-images-task.yaml#L180-L182

/ok-to-test

I'm anticipating this change in BIB: https://github.com/osbuild/images/pull/987 and use right away the .tar.gz file suffix. (As of today it's .tgz)

/retest


Documentation out dated

Example 1: Error message: [Init failed: Galleria could not find the element ".galleria".] is not included in the documentation.
Example 2: In the Beginners Guide the complete code example includes [] but seems to refer to an older version of the min.js file which is not included anywhere in the current version download. Thus this code doesn't work.
Recommendation 1: Update the documentation to be complete and accurate.
Recommendation 2: Include in the current download a fully working demo with folder structure and sample photos such that the only steps required are to unzip the download and open the demo.html file to see a working demonstration.

Additionally the jquery URL given in beginners guide etc is no longer valid. So following those instructions will not lead to a successful jquery installation. (you should use [] as an alternative.


[Feature Request] core下依赖版本号更好的维护方式

Checklist

[X] I searched exising issues and no one else requests similar feature.
[X] I think that 25%+ users are positive towards this feature.

Describe the feature
maven插件
Additional context
No response

没什么好的方式


Fix possible bug when remove asset files/dirs

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
✔/❌

Fixed issues
#91

Add count source dir files to base dir hash and raise minimum php version

Need a line for changelog.

Done

Should be updated to match changes in yiisoft/files, right?

Should be updated to match changes in yiisoft/files, right?

Yes

We'll tag its release soon.

👍


Added docs in storeProtectLoadUtils.js file, Docs added for loadProtector() reducer function

I have added few lines of documentation for loadProtector reducer function for having the a clear understanding for contributors about what does this reducer function is doing in middlerware.

@rabahalishah you need to sign the Plone Contributor Agreement to merge this pull request.
Learn about the Plone Contributor Agreement: https://plone.org/foundation/contributors-agreement


Year does not change date

when a date is selected and only the year is changed, the display does not update

Same here, any ideas?

@randybondsjr I found the problem!
TL;DR: Add the y in format parameter so the text input shows it.
The picker reads the Year from the text input so when you don't display the year in your input, it will not detect the selected year.
In my case, I had this (in the input textbox it displayed as 12 Oct 10:00):
	format: 'M d H:i',
	formatDate: 'M d',

I added the year (displays as 2/Oct/2016 10:00):
	format: 'j/M/y H:i',
	formatDate: 'j/M/y',


entql: uuid support

Hello there!
We're currently trying to integrate Ent into our project while making use of the new privacy layer. We want to implement a rule that is similar to the FilterTenantRule in the privacytenant example. This rule uses the Filter interface provided by the entql extension. However, when enabling the entql extension in our project, it turned out that it fails on UUID fields. The generated entql.go file is invalid since the UUID type gets filled in as [16]byte in the template.
// WhereID applies the entql [16]byte predicate on the id field.
func (f *OrganisationFilter) WhereID(p entql.[16]byteP) {
	f.Where(p.Field(organisation.FieldID))
}

It would seem to me that entql/types.go needs to be extended with the proper types for UUID/[16]byte fields.
Would be great if anyone could give some advice on how to proceed/work around this, since this is quite blocking to us at the moment.

I realise that the entql extension is still experimental, but creating a Filtering privacy rule seems to rely on it.

Hey @BrentChesny and thanks for reporting this.
I’ll give it a look in the upcoming hour and update you.

@a8m Made a pull request that I believe fixes the issue. Let me know if I missed something :)

Wow, that was fast @BrentChesny, but I actually came up with a little bit different fix for this in #1004 (I saw yours after I created mine).
I think UUID fields should be type driver.Valuer because this is what we accept in the schema/field package (field.UUID), and we don't care about the underlying Go type. WDYT?
I know that the popular solutions outside for UUID types use [16]byte, but I'm afraid that someone uses a different type for it, and it won't support this.
Anyway, let me know what do you think, and if you'd like to change your PR and we can abandon #1004.

I think UUID fields should be type driver.Valuer because this is what we accept in the schema/field package (field.UUID), and we don't care about the underlying Go type. WDYT?

I think yours is indeed the better solution. I have just one remark on #1004. Other than that it looks good, and we can abandon my PR.

Fixed with https://github.com/facebook/ent/pull/1004.
Thanks for your contribution @BrentChesny, it's really appreciated.

Thanks @a8m for your quick response to this! 🙏🏻

Great, closing! Feel free to reopen if you still have troubles with it.


Both upgrade and uninstall buttons were loading

Tried to uninstall an app that has a newer version, and found both uninstall and upgrade showing loading indicator

not a bug


Readme small text correction

Codecov Report

Merging #42 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #42   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         187    187
  Branches       30     30
=====================================
  Hits          187    187

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 49c0132...ab6d732. Read the comment docs.


Suggestion: Add Nullable and Optional to lib.d.ts

There have been a number of issue threads discussing  adding nullable types (most notably #7426 and #7488) and the idea of adding them to the core TypeScript Language was ultimately rejected.
However, it was also suggested in that issue that type mappings could be added to lib.d.ts
type Nullable<T> = T | null;
type Optional<T> = T | undefined.

But then the issue was closed and the suggestion seems to have been dropped.   (see https://github.com/Microsoft/TypeScript/issues/7426#issuecomment-196500331 by @mhegazy )
Nullable<T> is even mentioned in https://www.typescriptlang.org/docs/handbook/advanced-types.html alongside Partial<T>, as well as Readonly<T>, Pick<T, K extends keyof T>, and Record<K extends string, T>.  It is confusing when reading that document that Nullable<T> isn't in the core library and needs to be added to your project if you would like to use it.
To me it seems like it should be a logical and uncontroversial choice to add these type mappings.  They are tiny additions to the library, and they provide a nicer syntax (IMHO) than explicitly using T | null or T | undefined.

I'm still not sure I see a huge benefit to adding it for everyone. Here's a few reasons why

If it's an argument of fewer characters, then null | T is already shorter than Nullable<T>.
Using the term Optional is a layer of cognitive indirection for differentiating between | null and | undefined. Being explicit is more helpful here.
It's arguable whether there should be a T | null | undefined alias as well, so if you want another alias to satisfy that, you've exacerbated the previous point.
Problems with find-all-refs and the like can be fixed.

Nullable<T> is even mentioned in https://www.typescriptlang.org/docs/handbook/advanced-types.html

Note that Nullable on that page is not the same as the Nullable that you've described, and it's probably a poor name to use in the documentation.
I do understand a general desire to have these coming from other languages that have a core set of utility types built in, but overall, I don't think think the lack of these aliases has been a major problem in TypeScript.

It isn't about fewer characters, and I would agree that the lack of these aliases is not a major problem.
To me it just seems that Nullable<T> and Optional<T> are a more intuitive way of expressing these types than as an explicit union....  "It's type T but it doesn't have to have a value" vs "It's type T, or else it could also be undefined".
Idunno, maybe it is just a bias coming from other languages but it just feels like these are missing things that should be there.

I think part of the challenge though would be that some people would assume that if you use Nullable<T> or Optional<T> that TypeScript would guard you against that, when in fact it would only do so if you were using --strictNullChecks.  So by default, they wouldn't actually do anything.

The conclusion a while back in https://github.com/Microsoft/TypeScript/issues/7426 was that  | null and | undefined explicitly was the best way forward. Our experience since has validated that conclusion. the two extra types are not too long to write, nor they are hard to understand; and thus the additional layer of indirection using a type alias seems to be unwarranted here.
Again, if you find these aliases helpful, you are more than welcome to define them locally and use them. our experience however does not suggest there is a need for them in the wider community at the time being.


[Feature Request]:  pydantic v2 support

Describe the problem
pydantic v2 support
Describe the proposed solution
pydantic v2 support
Alternatives considered
pydantic v2 support
Importance
i cannot use Chroma without it
Additional Information
pydantic v2 support

tracked here, https://github.com/chroma-core/chroma/issues/893 thanks!


Fix help messages in CLI

Hi. Found some misleading/wrong messages in prisma2 CLI. You may want to fix it.
It asks me to use prisma2 lift create but there is no such command - I guess you meant prisma2 lift save

In the below example, it gives me prisma2 lift as one of the suggested commands but it is missing an option. I guess you meant prisma lift up

Thanks.

Internal note: candidate from bug triaging meeting


Fix typo in the API docs of brightness

There is a typo in the API docs of https://api.flutter.dev/flutter/material/AppBar/brightness.html as  showing blow:

Determines the brightness of the [SystemUiOverlayStyle]: for [Brightness.dark], [SystemUiOverlayStyle.light] is used and fo [Brightness.light], [SystemUiOverlayStyle.dark] is used.

Fixed in #92713


Add modal for error messages

I've added useErrorModal() to any components which has console.error() in it, so I probably missed some

LGTM


Error in ts file when lauch the app

What I did :
$ ionic start conf conference --v2 --ts
$ cd conf
$ ionic serve --lab

Here is the error I got in the console :
ERROR in [default] /Users/Thoms/Desktop/ionic/conf/node_modules/ionic-framework/animations/animation.d.ts:48:50
A 'this' type is available only in a non-static member of a class or interface.

ERROR in [default] /Users/Thoms/Desktop/ionic/conf/node_modules/ionic-framework/animations/animation.d.ts:54:50
A 'this' type is available only in a non-static member of a class or interface.

These errors will be fixed in the next release (beta.2). They shouldn't be breaking anything. Thanks for the issue!


Where is documentation and minified files

I was wondering were the minified js files are
What about documentation and usage examples?

Then how do i get the data programmatically?
I need to know the API, and how to export the data
Without proper documentation or examples this library will be useless

const x = xspreadsheet(document.getElementById('#id'))
x.change = (data) => {
console.log('data:', data)
}
// edit
// data is param in the change method
xspreadsheet(document.getElementById('#id'), {d: data})


NO-JIRA: fix SDK <-> API github action

As it describes in github action. I have run:
scripts]$ ./fetch_openapi.sh
scripts]$ ./generate_openapi_client.sh

And I have commit all changes.

As the CI build shows, it is not as simple as regenerating the files as it can (and does in this case) lead to a need to refactoring the UI too.

Removing my approval reading @manstis comment above. Thank you for spotting.

@manstis uff ... I can see it now :(

I close this PR request because the fix of the compatibility of SDK and Openapi requires more changes.