Wrong analyzer warning on self-assignment

See this snippet (dartpad with warning: https://dartpad.dartlang.org/4c353a7cf8726b4336ab)
class Base {}
class A implements Base {
  Base member;
}
void main() {
  A a = new A();
  wrong(a);
}
void wrong(Base base) {
  if (base is A)   base = base.member;
}
void right(Base base) {
  Base anotherBase = base;
  if (base is A) anotherBase = base.member;
}

Dart analyzer is not inferring in the 'wrong' function that base is actually of type A, so it says that there is no such thing as base.member. However, if you assign it to a different variable of the same type, instead of doing a self-assignment, then it knows that base is of type A, and can access the member field.

This is what the language specification requires.
The "type promotion" of base to be A insider the statement guarded by base is A only applies if there is no assignment to base inside the statement.
That means that the static type of the second base in base = base.member is still Base - it's not promoted to A because of the assignment. The language specification requires a warning here.

But but... shouldn't the inferred types only be dismissed after the assignment? The language specification should maybe be worded differently then? Ie what is the intention here?


Add Windows secrets support

Signed-off-by: John Stephens<EMAIL_ADDRESS>This change implements secrets support for Windows by writing to persistent files on the host, due to the lack of a RAM disk driver built in to Windows. A separate change will add RAM disk support later.
@jhowardmsft @PatrickLang @ehazlett @diogomonica @cyli

+1 to get to a ramdisk (or similar) backend so we don't have to persist these on disk.  as long as we ensure the permissions and access is limited this sgtm as a start.
design LGTM

@ehazlett Since secrets are stored in the Docker runtime root (%ProgramData%\Docker by default), the secrets directories inherit those permissions, only granting administrators and system access:
$ icacls %ProgramData%\Docker
C:\ProgramData\Docker BUILTIN\Administrators:(OI)(CI)(F)
                      NT AUTHORITY\SYSTEM:(OI)(CI)(F)

Successfully processed 1 files; Failed processing 0 files

However, for a custom runtime root (e.g. --graph A:\docker), security is based on that custom root directory. We could explicitly force stricter permissions on each secrets directories.

We need a commitment on the timeline for the RamFS before we merge this
We need the docs to reflect that secrets will not be as secure on windows as they are on Linux.

+1 for documenting differences between Windows and Linux
@johnstep

We could explicitly force stricter permissions on each secrets directory.

Yes +1.  I say we do this regardless of the Docker root to be sure nothing would accidentally leak and to make sure at minimum the secrets directory has the proper access restrictions.

Can we disable docker commit when secret is mounted on the rootfs rather than on RAM disk?

@AkihiroSuda Windows does not support commit of a running container, and Docker deletes secrets when stopping a container. If the daemon terminates abnormally, it deletes the secrets on restarting.

@mstanleyjones We need to document that secrets for Windows will be persisted on the host, in the container directory. The secrets directory is deleted when the container is stopped, or when the daemon is restarted, in the case of abnormal termination. In the short term, customers can mitigate this concern by enabling BitLocker on the volume containing the Docker runtime root.
Separately, we are working on a RAM disk driver for consistency with Linux.

Updated to always secure secrets directories explicitly, and enabled integration tests.

@johnstep needs a rebase

It's much closer, but I'd still like a few changes. I'd also like to see some docs here explaining the nuances of what all this implies before giving a 'LGTM'

I will work on the documentation. This Windows differences will definitely be documented for 17.06.

@johnstep ^^ differences sounds good.

Thanks for reviewing @jhowardmsft
And whoop, @johnstep, happy to see this merged!


Add Haskell Library reference

Add reference to Haskell Library to v3 SendGrid API in thiry party library documentation. The library is also published on hackage.

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

Hello @marcelbuesing,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Fix #1459: SunEditor prevent HTML manipulation

Fix #1459: SunEditor prevent HTML manipulation
cc @jepsar @mkomko @stolp

Was thinking whether to make this optional, but I guess most Faces users would want to clean-up the HTML at the server side.

That is what I was thinking too.  He really shouldn't be touching the HTML in our case we can choose to do what we want with it.


WASI or WASM?

The docs state that Lapce plugins rely on WASI technology. This makes me confused.
The purpose of WASI (WebAssembly System Interface) is to port code of traditional applications (i.e. command-line programs) to the web (or any sandbox runtime). The host interacts with WASI programs via CLI arguments and stdio (stdin, stdout, stderr).
Whilst a WASI program is just a WASM module, not every WASM module is a WASI program. A WASM module can be thought of as a shared library that exports functions for the host to call. The host can also provide APIs to the WASM module via an "import object".
So which is it? Do Lapce plugins actually run on WASI or just WASM?

If it was actually WASI. What is the reason behind this choice? Do you have any plan for a WASM API? In my opinion, interacting with a WASM module via function calls is faster than interacting with a WASI program via CLI and stdio.
If it wasn't actually WASI. Please correct your documentation.

It is WASI. The runtime for it is https://wasmer.io/

@dzhou121 Wasmer can run any WASM module, not just WASI. It doesn't have to be WASI.

See this. We currently hook into stdout/stdin for passing messages to/from the plugin, primarily.

Do you guys have any plan to implement a (non-WASI) WASM API? I think there would be limitation with WASI sooner or later.

It is WASI. The runtime for it is https://wasmer.io/

Hello, what is the main reason of choosing wasmer over wasmtime?

I've given some thought to the WASM api recently, and the issue I ran into is that there doesn't seem to be a 'nice' way of passing serialized bytes (messages) to/from WASM. (Though, I could be mistaken about this, and I'd love to be):
We don't seem to be able to 'claim' a specific area of memory, and then pass a wasm-ptr to a function. While you could potentially expand/grow the memory, that doesn't tell the allocator inside the WASM about it. Then, that allocator could just use that space since it has no knowledge and overwrite it.
Thus, to get a specific region of memory (within WASM) to write a message to, you'd need some way of telling it "I need a chunk of memory of n bytes". This can be done by exporting an alloc/dealloc function, which just allocates from within the WASM's world. This is what something like wasm_bindgen does for JS <-> Rust.
However, this requires exporting those functions in a standardized way. For Rust/C/C++ this is pretty easy to implement and export, and could be done in a basic plugin-api file that we make. However, I'm unsure if it can be implemented in something like Python or AssemblyScript or various other languages that don't typically have a way of defining a function that returns a pointer to memory that you can then pass into other code. I think it'd still be possible to get around this, and I imagine they expose something, but I'm uncertain if there's a relatively nice general way of doing that.
There's things like (docs: https://github.com/WebAssembly/component-model / using guide: https://radu-matei.com/blog/intro-wasm-components/) but they seem relatively young/non-final.

I don't know much about how WASM functions in details, so feel free to correct me if I'm wrong.
I assume that exporting/importing functions between the host and the WASM binary is similar to FFI in the native world. After all, alloc and dealloc are provided by libc.
I think that CPython always have ways to call FFI functions. It is up to Python users to create a wrapper around them. Meaning, you the API provider don't have to worry about Python API wrapper. Even if you can spare your effort into it, I think it is not worthwhile regardless, because users typically don't want slow and heavy plugins. Regarding allocation, I think the Python runtime (CPython for native, Pyodide for WASM) also uses libc functions. And Python users don't allocate memory manually.
AssemblyScript already has some allocation functions. Pointer in AssemblyScript seems to just be a usize number. AssemblyScript also have plan to support reference types. Again, I think AssemblyScript is not your responsibility.
Also, in the docs of AssemblyScript, they seem to consider WASI harmful:

One advantage of WASI is perhaps the code don't look that different from a native code. WASI users are free to use println!, eprintln!, dbg! to debug for example. So the best of both worlds can be acheived by either:

Adding imports to WASI, allowing the WASI plugin to invoke the API "directly" (via extern "C") without going through JSON-RPC. Or, ...
Adding wasi-core interface to the WASM API, allowing the WASM plugin to access traditional resources (such as stdin/stdout/stderr, filesystem, environment variable, etc.) using traditional methods (println!, std::fs, std::env, etc.)

Your worry seems to be that there is no single, agreed upon way to pass a massive chunk of data of variable length (streaming) between the host and the plugin. Hence, I have a proposal: Instead of passing/return a whole string to/from a function, why don't we pass/return single characters over multiple calls to a single function, similar to Iterator::next?
WebAssembly is a young, incomplete, and evolving standard, and the component model is nowhere near final, but then even WASI itself is nowhere near final (the context object of a WASI import is named wasi_snapshot_preview1).

However, I'm unsure if it can be implemented in something like Python or AssemblyScript or various other languages that don't typically have a way of defining a function that returns a pointer to memory that you can then pass into other code

AssemblyScript as well as Rust provides allocation and deallocation functions for the host. In fact, probably all languages that have an interop between Wasm and host do similarly. AS export __new, __pin and __unpin functions for such proposes.
But yes, each language has different methods for doing this, which makes it difficult to write a unified bridge between the host and some language-specific plugin. Perhaps a component model would improve this, but I have my doubts about it.

AssemblyScript as well as Rust provides allocation and deallocation functions for the host. In fact, probably all languages that have an interop between Wasm and host do similarly. AS export __new, __pin and __unpin functions for such proposes.

Thanks for the information about AS, and other languages!

as well as Rust provides allocation and deallocation functions for the host.

For Rust do you know if you have to enable those explicitly? I've used wasm2wat on a Rust plugin, (for Lapce) but the only exports I've seen are:
  (export "memory" (memory 0))
  (export "__heap_base" (global 1))
  (export "__data_end" (global 2))
  (export "_start" (func $_start.command_export))
  (export "initialize" (func $initialize.command_export))
  (export "main" (func $main.command_export))

While there is an allocator in the code, it doesn't appear to export it automatically. (Though, its easy to just include an alloc impl for our Rust plugin lib, so even if this isn't available 'by default' it is easy to implement)

I guess it would require different methods for different languages. We could just require the plugin.toml to include a language_kind = "assemblyscript" (/ "pyodide" / "rust" / etc), then the plugin-manager calls the expected functions for allocation/deallocation/pinning-if-needed.

For exporting __new, __pin, __rtti_base and __unpin you should add --exportRuntime flag for asc. See playgound


console.log buffering while debugging is confusing

Describe the bug
While debugging a Vitest test case using the VSCode plugin's "Debug Test" functionality, output generated by the test case using console.log does not show up in the Test results pane immediately when the console.log call is performed; it only shows up at some later time. This is very confusing and hinders debugging.
Reproduction
The repro is here. To reproduce, put a breakpoint on the console.log line in index.test.mjs. Then choose Debug Test in the Testing view. Then choose Step Over. Notice no output appears in the Test results pane.
Output
[INFO 13:38:16] [v1.6.9] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 13:38:19] [API] Running Vitest v2.1.5 (vitest-repro/vitest.config.js) with<EMAIL_ADDRESS>/Users/bartj/.nvm/versions/node/v22.9.0/bin/node
[INFO 13:38:21] [API] Vitest v2.1.5 (vitest-repro/vitest.config.js) child process 36769 created
[INFO 13:38:21] [VSCODE] Watching vitest-repro with pattern **/*
[INFO 13:38:21] [API] Collecting tests: index.test.mjs
[13:38:21] Not starting the runner because tests are being collected for index.test.mjs
[13:38:22] [VSCODE] File deleted: vitest.config.js.timestamp-1732019901325-e73096b854411.mjs
[13:38:24] There is no test run for "index.test.mjs"
[13:38:24] No test run to finish for index.test.mjs
[13:38:25] [VSCODE] Ignoring file: node_modules/.vite/vitest/results.json
[INFO 13:38:30] [DEBUG] Starting debugging session /Users/bartj/.nvm/versions/node/v22.9.0/bin/node
[INFO 13:38:31] [DEBUG] Debugging started
[13:38:32] Initiating deferred test run
[INFO 13:38:32] Running 1 file(s) with name pattern: ^\s?Test Suite hello world!$
[13:38:32] The runner is starting because tests index.test.mjs were started due to a file change
[13:38:32] Enqueuing "hello world!"
[13:38:32] [VSCODE] File deleted: vitest.config.js.timestamp-1732019912764-b342c42c65b0d.mjs
[13:38:33] No task result for "index.test.mjs", ignoring
[13:38:33] No task result for "Test Suite", ignoring
[13:38:33] Enqueuing "hello world!" because it was just collected
[13:38:47] No errors found for "index.test.mjs"
[13:38:47] No errors found for "Test Suite"
[13:38:47] Marking "hello world!" as passed
[13:38:47] Ending test run index.test.mjs
[13:38:48] [VSCODE] Ignoring file: node_modules/.vite/vitest/results.json
[13:38:48] [API] Vitest WebSocket connection closed, cannot call RPC anymore.
[13:38:48] Disposing test runner
[13:38:48] Ending test run <none>

Version
1.6.10
Validations

[X] Check that you are using the latest version of the extension
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I found a workaround: add disableConsoleIntercept: true to the test object in vitest.config.js; then console.log output appears in the Debug console immediately.
export default defineConfig({
  test: {
    environment: 'node',
    disableConsoleIntercept: true,
  },
});


Add UPTIME tests to valid tests

As described here: https://mmonit.com/monit/documentation/monit.html#PROCESS-UPTIME-TESTING
I'd like to be able to monitor process uptime and restart as required so that processes don't become stale, as they sometimes do. Unless I'm missing something, this isn't supported by the puppet module right now.
Cheers!

PRs welcome!


Tracker Expense Caclulator added

🛠 Fixes Issue #758
👨💻 Changes proposed

I have added my project to your repository.

✅ Check List (Check all the applicable boxes)

[x] My code doesn't break any part of the project (Zero Octave-Javascript-Projects).
[x] This PR does not contain plagiarized content.
[x] My Addition/Changes works properly and matches the overall repo pattern.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

This project will help learners to learn Js functions and other concepts.
This project will help learners to implement responsiveness using CSS and Bootstrap.

📷 Screenshots

Your project is not running properly on my side. You have pushed so many unnecessary files. I conveyed the same in previous conversations.  Still, the same files exist here.
One of our mentors asked you if your project has any prerequisites to run on a local machine. Your project is not running properly at my side. You have pushed so many unnecessary files. I convey the same in previous conversations.  Still same files exists here.

Okay, I have finally figured out the problem, give few minutes. i am updating it.

Kindly check it now.

Give me a moment.

You have pushed some unnecessary files like ds store, extra folders and lots of minify files. may be removing these files will solve the errors. lots of conflicts coming in my local.
Tell me if your project has any prerequisites to run on a local machine.

No, they don't have any prerequisites. Actually, there are problems with file linking, but I'm fixing them.

@Astrodevil I have fixed all the problems, kindly check it now.✨

it's working fine now, just update your forked repo and resolve the issue in readme (only need to change the project number)

@Astrodevil I have fixed all the problems, kindly check it now.✨

project is now working fine, just update your forked repo and resolve the conflict in readme(just change the project number after updating)


"Error: Error not specified" on insertRecords

Describe the bug
I've managed to initialize and requestPermission, but when calling insertRecords it throws [Error: Error not specified.].
Please advise if there's any way to debug this from my end.
To Reproduce
Steps to reproduce the behavior:

Add

<uses-permission android:name="android.permission.health.WRITE_EXERCISE"/>

Call

await initialize()

Call

await requestPermission([{accessType: 'write', recordType: 'ExerciseSession'}]);

Call

await insertRecords([
    {
      recordType: 'ExerciseSession',
      exerciseType: 8,
      startTime: '2023-09-12T09:30:13.982Z',
      endTime: '2023-09-12T09:39:49.241Z',
    },
  ]);

Expected behavior
insertRecords should resolve without errors
Environment:

Health Connect Version: 1.2.0
React Native Version: 0.69.9
New architecture enabled: No

Thank you for a nice and well written library ☺

That's sort of the issue, it doesn't give any other clues.

I believe so, installed it today

I'm running it in Android emulator. Could that be an issue?

I'm running it in Android emulator. Could that be an issue?

No, I don't think so.
It seems it's an internal error from the health connect itself.

Oh nice! Then I seem to have an old version. Will try to get the latest then.
Do you know if there's an official developer forum or issue tracker for the health connect project? Also noticed that EXERCISE_TYPE_MEDITATION is completely missing - but should probabaly be there since the refer a lot to those kinds of apps.
https://developer.android.com/reference/androidx/health/connect/client/records/ExerciseSessionRecord#summary
And thanks for the quick support, really appreciate it 🙌

Try to bump the androidx.health.connect:connect-client manually in your node_modules and see if that resolves the problem. Then I will create another release for that.

Sure will do!

Yes works like a charm!


Let user can append url path to show different page in the markdown mode.

add a parameter named "additionalUrl", so it can embed specific page, not only the home page of the web site.

Hi! Thanks so much for this pull request. As you can see, I implemented something very similar, inspired by your code.


Genprog remove ast comp supp

Ast based comparing adds a lot of false positives, more than the false negatives it solves.

Rebased. Right diff.

Thanks!


ADD Github Contributors page to the web application

@shubhagarwal1 duplicate

hey @RamakrushnaBiswal can you please tell me some tasks which i can work on, i would be a great opportunity for me .

@shubhagarwal1 check old issues and comment there i will assign


syncronize the clock on your host

when i am trying to bootstrap i am getting the below error

Hi Satya,
Can you please restart the both local machine where chef-server(Hosted-chef) installed and also EC2 virtual machine CHEF-NODE you have configured
and execute the same  knife boot strap command again

is this resolved ???

is this resloved

hi satya ,
change your local machine time zone and  try again boot strap ,i am sending u the screenshot check below


differentiate context for start and wait

context that pass to Start() will determinate task lifetime
context that pass to Wait() will not impact task lifetime

Codecov Report

Merging #7 into master will decrease coverage by 2.81%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##            master       #7      +/-   ##
===========================================
- Coverage   100.00%   97.18%   -2.82%
===========================================
  Files            1        1
  Lines           74       71       -3
===========================================
- Hits            74       69       -5
- Misses           0        1       +1
- Partials         0        1       +1

Impacted Files
Coverage Δ

async_task.go
97.18% <100.00%> (-2.82%)
: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 88c464b...040f6f8. Read the comment docs.


Azure SignalR - Adding new api-version 2023-03-01-preview

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

        "$ref": "#/parameters/SubscriptionIdParameter"

Recommend SubscriptionIdParameter from v5 common types. Comment applies throughout this PR.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1260 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

        "$ref": "#/parameters/ResourceGroupParameter"

Recommend ResourceGroupNameParameter from v5 common types. Comment applies throughout this PR.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1263 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

        "$ref": "#/parameters/ApiVersionParameter"

Recommend ApiVersionParameter from v5 common types. Comment applies throughout this PR.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1269 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

        "$ref": "#/parameters/ResourceName"

resourceName is too generic. Recommend including the type in the name, e.g. signalRName. Comment applies throughout this PR.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1266 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

          "$ref": "../../../../../common-types/resource-management/v2/types.json#/definitions/ErrorResponse"

Move to current common types (v5).  Comment applies throughout this PR.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1282 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

      "$ref": "#/definitions/TrackedResource"

Should use TrackedResource from v5 common types.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:2554 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

  }

You can get rid of this if you move to v5 common types for TrackedResource.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:2569 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

      "201": {

Async status is 202.

Refers to: specification/webpubsub/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/webpubsub.json:1734 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

        "$ref": "#/parameters/SubscriptionIdParameter"

Get this from common types

Refers to: specification/webpubsub/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/webpubsub.json:1480 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

        "$ref": "#/parameters/ResourceName"

Should use a more specific name than resourceName, e.g. webPubSubName.

Refers to: specification/webpubsub/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/webpubsub.json:1486 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

          "$ref": "../../../../../common-types/resource-management/v2/types.json#/definitions/ErrorResponse"

Move to newer common types (v5)

Refers to: specification/webpubsub/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/webpubsub.json:1502 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

        "$ref": "#/parameters/SubscriptionIdParameter"

Recommend SubscriptionIdParameter from v5 common types. Comment applies throughout this PR.
Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1260 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

The apiVersion, subscriptionId, resourceGroup are switched to use common types in V5 now

        "$ref": "#/parameters/ResourceName"

resourceName is too generic. Recommend including the type in the name, e.g. signalRName. Comment applies throughout this PR.
Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1266 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

Since the resourceName is used for the primary for all existing apis, we hope to keep consistent when adding a new replica api.  :smiley:

          "$ref": "../../../../../common-types/resource-management/v2/types.json#/definitions/ErrorResponse"

Move to newer common types (v5)
Refers to: specification/webpubsub/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/webpubsub.json:1502 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

The errorResponse in using v5 now

        "description": "Created or updated. The response describes the new replica and contains a Location header to query the operation result.",

201 is created, 200 is updated.
Refers to: specification/webpubsub/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/webpubsub.json:1618 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

The description is updated according to comments

      "$ref": "#/definitions/TrackedResource"

Should use TrackedResource from v5 common types.
Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:2554 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

Use trackedResource in common type v5 now. The one in the swagger file is deleted.

      "201": {

Async response for PATCH is 202. Ref: https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#updating-using-patch.
Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1514 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

Changed to 202 for patch as commented

Hi @mentat9 . Looks the modification is targeted as a breaking change after I switched to use types defined in common v5.
https://github.com/Azure/azure-rest-api-specs/pull/22948/checks?check_run_id=11950071162
Is it a false alarm :sweat_smile:

There still seem to be a large number of RPC violation lintDiff errors, I assume these should all be fixed.
https://github.com/Azure/azure-rest-api-specs/pull/22948/checks?check_run_id=11950071397

Hi @TimLovellSmith . Fixed the 202 issue and location header issue in LintDiff.
And according to @raych1 , the remaining issues in LintDiff  for patch operation could be skipped if they are from common types.

    "systemData": {

I forget but is systemData not already included in v5 ProxyResource definition? Probably the upgrade from v2-v5 types could be causing redundancy in the definition.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1951 in d2ab42a. [](commit_id = d2ab42ad085584c707dd12894531174504f0f4b6, deletion_comment = False)

    "systemData": {

Same question about upgrading common types and systemData

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:2029 in d2ab42a. [](commit_id = d2ab42ad085584c707dd12894531174504f0f4b6, deletion_comment = False)

    "systemData": {

Yes, its already inherited, from v5 'Resource' (ProxyResource inherits it)

In reply to:<PHONE_NUMBER>

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1951 in 0a47055. [](commit_id = 0a4705500e4648dede8428e8b61627ca6fbf373a, deletion_comment = False)

},

Do you still need this, or are you now inheriting TrackedResource/ProxyResource everywhere instead?

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:2696 in d2ab42a. [](commit_id = d2ab42ad085584c707dd12894531174504f0f4b6, deletion_comment = False)

},

Would you be able to use the definitions of these from common-types instead? (is it nonbreaking?)
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v4/privatelinks.json

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:2492 in d2ab42a. [](commit_id = d2ab42ad085584c707dd12894531174504f0f4b6, deletion_comment = False)

        "name": "privateEndpointConnectionName",

Would you be able to use the definition of this from
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v4/privatelinks.json#Parameters
instead?

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1007 in d2ab42a. [](commit_id = d2ab42ad085584c707dd12894531174504f0f4b6, deletion_comment = False)

Hi @TimLovellSmith . Looks replacing all modesl with common-types is a big change. Maybe I can submit a seperate PR to upgrade them and make this PR focus on the new Apis introduced by our replica feature?

Hi @TimLovellSmith . Looks replacing all modesl with common-types is a big change. Maybe I can submit a seperate PR to upgrade them and make this PR focus on the new Apis introduced by our replica feature?

Looks not that big. Let me do it in this PR

Yes, to be clear, its ok to punt the common types changes if they are making it too hard. We are just trying to gently nudge people in that best pratices direction.

Hi @TimLovellSmith . Now the trackedResource, proxyResource, privateEndpointConnectionParameter are using models from common.
Since our privateEndpointConnection model is different from the one in Common, I switched back to use our olde model.

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1229 in 44cc5a9. [](commit_id = 44cc5a9ee17389b8e1bddea7497109b296d1c4ce, deletion_comment = False)

      "202": {

Don't you also have to spec the final '200' success response?

Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1511 in 44cc5a9. [](commit_id = 44cc5a9ee17389b8e1bddea7497109b296d1c4ce, deletion_comment = False)

      "202": {

Don't you also have to spec the final '200' or '204' success response?
Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1511 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

I didn't quite get the point. There is a 200 response for this api. Is there anything else that is missed?

Don't you also have to spec the final '200' or '204' success response?
Refers to: specification/signalr/resource-manager/Microsoft.SignalRService/preview/2023-03-01-preview/signalr.json:1511 in 0a47055. [](commit_id = 0a47055, deletion_comment = False)

I didn't quite get the point. There is a 200 response for this api. Is there anything else that is missed?

Yes, my mistake, sorry!

hi @raych1 , can we get merged now?

@live1206 , can you have a look at dotnet sdk track2 error?

Some clarifications about breaking changes:

We migrate to common models( The proxyResource, trackedResouce...).
A pattern is added to resource name. This limit exists in server side too.

@live1206 , can you have a look at dotnet sdk track2 error?

There are two kinds of errors here:

Breaking change due to migration to common types, which is expected
In common types v5, subscription id is Guid instead of string, this is causing problem for many RPs we are looking into a proper solution, we can ignore them in this PR

@live1206 @raych1
So the breaking changes are false alarms. Can we move on ?

/pr RequestMerge


[Feature] Add in-place loading method to QuantumModel

Fixes #484
This PR proposes a new method in QuantumModel, load_params_from_dict() which allows to load the parameters from a dictionary directly to the current model. There is already a similar method .from_dict() but that one is a class method that initializes a new instance from the configuration saved in the state dictionary. Adding load_params_from_dict() fixes the bug mentioned in #484 as it allows to load the parameters from the dict 'in-place' without initializing a new instance. This is especially important in case the optimizer is defined before loading a checkpoint (as in the qadence's train() function) otherwise the optimizer will point to the old model and the parameters of the newly instantiated model won't be updated.
Aside from this, I also reworked the tests so that we properly test loading and saving ckpts. The main contribution here is that now the models are always modified after being saved, so that when they are loaded again the tests won't pass if the loading is not successful (this was not the case before).
Lastly, I also modified the line below so that it also works with torch modules with no .device() method. This assumes that all parameters in the module are saved in the same device but I think it's a pretty safe guess
https://github.com/pasqal-io/qadence/blob/d478f8a7d9c2b3dd1f011099beb2c00af23fe20f/qadence/ml_tools/saveload.py#L75

@chMoussa I added the missing/unexpected keys check and an additional argument in the method to enforce that the parameter keys of the dictionary strictly match the param keys in the model. I also added a test for the method in test_quantum_model.py


Add base16-spacemacs theme

Adds a base16-spacemacs theme. It follows the same primary mode colours as molokai {normal:blue, insert:green, visual:yellow/orange, replace:red} but with the colour palette of the spacemacs variant of the base16 themeset.
Mode run-through:

Normal mode with trailing whitespace:

Normal mode with unwritten file modification:

Insert mode:

Visual mode:

Replace mode:

Inactive mode:

thanks.


Does GPUHaishinKit compatible with BradLarson/GPUImage2?

BradLarson/GPUImage isn't maintained anymore, so I plan to migrate to BradLarson/GPUImage2.
Is it possible ?

No. I focused BradLarson/GPUImage.
GPUHaishinKit2 project is here. https://github.com/shogo4405/GPUHaishinKit2.swift
But, project is under suspension. Because GPUImage2 is not released. And I'm not familiar with GPUImage2.


Error: Cannot parse content. No Content-Type defined.

Bug Report

Version
1.22.0

1.22.0

Platform

Darwin MacBook-Pro.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:25 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6030 arm64
Description
I tried this code:
svixClient.eventType.list({ includeArchived: true })

I expected to see this happen:

Listing me the event types.

Instead, this happened:
Error: Cannot parse content. No Content-Type defined.
    at Function.parse (/Users/user/Documents/project/node_modules/.pnpm/svix@1.22.0/node_modules/svix/src/openapi/models/ObjectSerializer.ts:602:19)
    at EventTypeApiResponseProcessor.<anonymous> (/Users/user/Documents/project/node_modules/.pnpm/svix@1.22.0/node_modules/svix/src/openapi/apis/EventTypeApi.ts:1208:34)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/user/Documents/project/node_modules/.pnpm/svix@1.22.0/node_modules/svix/dist/openapi/apis/EventTypeApi.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

The libraries return this when the server returns a malformed response. Which server are you working against?


feature: add proxy dns server

支持harbor https private public
docker run -d --name dfclient1 -p 65001:65001 -v /etc/dragonfly.conf:/etc/dragonfly.conf dfclient:wp --registry https://x.x.x --resolver <IP_ADDRESS>
supornode 使用 host 网络模式
docker run -d --name supernode --restart=always --net host     dragonflyoss/supernode:0.3.0 -Dsupernode.advertiseIp=<IP_ADDRESS>
在echo "nameserver <IP_ADDRESS>" >>/etc/resolv.conf
[root@localhost ~]# docker logout   http://<IP_ADDRESS>:65001
Removing login credentials for <IP_ADDRESS>:65001
[root@localhost ~]# docker pull   <IP_ADDRESS>:65001/library/python
Using default tag: latest
Error response from daemon: pull access denied for <IP_ADDRESS>:65001/library/python, repository does not exist or may require 'docker login'
[root@localhost ~]# docker login   http://<IP_ADDRESS>:65001
Username: admin
Password:
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
[root@localhost ~]# docker pull   <IP_ADDRESS>:65001/library/python
Using default tag: latest
latest: Pulling from library/python
Digest: sha256:ce2b6fbe7d9dc28bbd332a6b9349b7040f0ffde81f1f14e121085eacfc4c0c3c
Status: Image is up to date for <IP_ADDRESS>:65001/library/python:latest
[root@localhost ~]# curl http://<IP_ADDRESS>:65001/env
map[dfPattern:[] home:/root/ param:{DfPath:/dfclient/dfget DFRepo:/root/.small-dragonfly/dfdaemon/data/ RateLimit:20M CallSystem:com_ops_dragonfly URLFilter:Signature&Expires&OSSAccessKeyId Notbs:true HostIP:<IP_ADDRESS> Registry:https://x.x.x TrustHosts:map[] Resolver:<IP_ADDRESS>}]

Codecov Report

Merging #510 into 0.3.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            0.3.x     #510   +/-   ##
=======================================
  Coverage   58.93%   58.93%
=======================================
  Files          56       56
  Lines        2793     2793
=======================================
  Hits         1646     1646
  Misses       1069     1069
  Partials       78       78

Impacted Files
Coverage Δ

dfdaemon/global/global.go
92.3% <ø> (ø)
:arrow_up:

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 e804cc4...cd606e6. Read the comment docs.

@upengs Could you please describe what problem this PR is trying to solve？ In my opinion, it allows users to customize the DNS resolver server and avoid DNS Spoofing problems, etc?

在echo "nameserver <IP_ADDRESS>" >>/etc/resolv.conf

In addition, there's the question, should this command be executed on the client or supernnode?

@Starnop When using internal harbor, HTTPS domain names need to specify a well-configured DNS server, otherwise dfdaemon will fail in reverse proxy. Supernode also needs to set up a DNS server. Execute echo "nameserver <IP_ADDRESS>" >/etc/resolv.conf in supernode

Could you help to sign the DCO which fails in the integration test? @upengs

Today's test did not find this problem.


Issue 1115:  Optimize sequence comprehension 'Head

Closes #1115

@kanigsson you can run the failing test with
python -m pytest 'tests/integration/feature_test.py::test_provability[session_comprehension_on_sequence]' -vv


remove locale "sd" (not supported by ICU/CLDR); unify localizations script options

Remove locale "sd", which is not supported by ICU/CLDR (see the banner at the top of this page: http://demo.icu-project.org/icu-bin/locexp?d_=en&_=sd)
Unify the CLI options for gen_localizations.dart and gen_date_localizations.dart.

LGTM modulo a few nits and --overwrite :-)

@HansMuller did you forget to send the nits?


EPIC v2 multiple IlmnID per CpG Name behavior

Dear Dr. Suderman,
Thank you so much for adding EPIC v2 support to {meffil} so quickly.
It looks like there are now multiple IlmnID for a cpg Name in the manifest. Because of this, the CpG name in the beta matrix returned by {meffil} is no longer unique as in EPIC v1. For example, cg00002033 is replicated twice. In the manifest, the IlmnID would be
cg00002033_TC11 and cg00002033_TC12 and the Name column would be 2 values of cg00002033.
I was just wondering how this duplication is handled by {meffil}? QCing my data with the current version of {meffil}, it looks like the beta values for a duplicated cpg have the same exact value. For example, cg00002033 is duplicated twice. cg00002033(1) and cg00002033(2) are the same for each individual in my data.

I'm not sure if this is an intended behavior since I would expect the values would be close but not the same. Even if we get back different values for each repeat, I'm not sure if averaging across the repeats is valid either. Do you have a recommendation?
Sincerely,
Hung

Hi Hung,
There seem to be ~5000 duplicated probes.  You are correct, a duplicated probe should be similar but not exactly the same!  Thank you for pointing this out. I've now changed the behavior of meffil to something more sensible.  Each CpG site with duplicated probes will have the first probe named as usual and all remaining duplicates named using IlmnID values.  For example, you should now see probes named "cg00002033" and "cg00002033_TC12". They should be highly correlated but not identical.  There are a few options for EWAS interpretation.  The easiest is just to omit association testing for probes with IlmnID names (in R, just grep for "_").  These could be removed before or after the EWAS is performed. Alternatively, as you mentioned, you could replace the duplicates with the mean or median across all duplicates. My guess is that the resulting probe will have less technical noise.  A third alternative is to calculate the correlations between all pairs of duplicates and take the one with strongest overall correlation with the other duplicates.  My guess is that the best option is the second option with the median. I could add this an option (probably default) to the normalization pipeline if that would be useful.
Best,
Matt

Dear Matt,
Thank you for your answer. Your answer makes a lot of sense to me. May I ask a follow-up question regarding R?, I'm still relatively inexperienced.
Do you think this "dup handling" option should be a separate function? Or should it be part of meffil.normalize.samples()? Because a relatively clean strategy that I see is to:

Let meffil.normalize.samples() return a matrix with IlmnID instead of Name as rownames. This helps subsetting easier.
Write meffil.EPICv2.format() as something along the lines of the following

library(data.table)
manifest # The manifest as a data.table object with just `IlmnID` and `Name`
str(manifest)
# Classes ‘data.table’ and 'data.frame':	937055 obs. of  2 variables:
#  $ IlmnID: chr  "cg25324105_BC11" "cg25383568_TC11" "cg25455143_BC11" "cg25459778_BC11" ...
#  $ Name  : chr  "cg25324105" "cg25383568" "cg25455143" "cg25459778" ...

# Filter to only Cpg that are dups
manifest_dup_only <- manifest[, N := .N, by = "Name"][N > 1]

# Most CpGs are duplicates, one has 10 replicates for some reason
unique(manifest_dup_only[, list(Name, N)])[, table(N)]
# N
#    2    3    4    5    6   10
# 4188  962   23   48    3    1

# Store the dup_only cpgs as an internal object because the size is small enough
manifest_dup_only$N <- NULL
lobstr::obj_size(manifest_dup_only)
# 1.27 MB

str(manifest_dup_only)
# Classes ‘data.table’ and 'data.frame':	11622 obs. of  2 variables:
#  $ IlmnID: chr  "cg09085639_BC11" "cg15034763_TC11" "cg20651681_TC11" "cg20029347_TC11" ...
#  $ Name  : chr  "cg09085639" "cg15034763" "cg20651681" "cg20029347" ...

# This object holds all the unique _BC11, _TC11, etc. combination of suffixes of
# IlmnID. This is a safe way to handle the renaming of the beta matrix
all_unique_suffix <-
  tstrsplit(manifest$IlmnID, split = "_", fixed = TRUE,keep = 2)[[1]] |>
  unique()

# Possibly also an internal object
suffix_grep <- paste(paste0("_", all_unique_suffix), collapse = "|")
all_unique_suffix |> head()
# [1] "BC11" "TC11" "BO11" "TO11" "BC12" "TC12"
suffix_grep
# [1] "_BC11|_TC11|_BO11|_TO11|_BC12|_TC12|

#' Format EPICv2 beta matrix
#'
#' Convert the output of [meffil.normalize.samples()] using EPICv2 chip into
#' typical format with cpg names as row names.
#'
#' @inheritParams meffil.normalize.quantiles
#' @param method which method to handle repeated cpg? Default to "median"
#'
#' @return a beta matrix with cpg `Name` as row names
#' @export
meffil.EPICv2.format <- function(beta, method = c("median", "mean", "cor")) {
  require(data.table)
  # Assuming beta is not a GDS filename
  method <- match.arg(method)
  if(method == "median") {
    ag_fns <- median # ag stands for aggregate
  }

  sample_names <- colnames(beta)

  # Convert to data.table because we are only working with ~11k CpGs
  ## get just the dupped CpGs from the input beta matrix using the internal
  ## object manifest_dup_only
  dups_dt <- beta[manifest_dup_only$IlmnID, ] |>
    as.data.table(keep.rownames = "IlmnID") |> # Convert to data.table, keep row names as "IlmnID"
    merge(manifest_dup_only, by = "IlmnID") # Merge with the manifest_dup_only again to get "Name"

  # Do column wise aggregation.
  ag_dt <- dups_dt[, lapply(.SD, ag_fns, na.rm = TRUE), .SDcols = sample_names, by = "Name"] |>
    as.matrix(rownames = "Name") # Convert back to matrix. This is the dupped part of beta

  # Renaming beta matrix
  ### Removing all the suffixes using the `suffix_grep` object
  row.names(beta) <- sub(pattern = suffix_grep, replacement = "", row.names(beta))
  return(
    rbind(
      beta[!row.names(beta) %in% row.names(ag_dt), ], # The part without the dups
      ag_dt # The aggregated dups
      )
    )
}

Sincerely,
Hung

Hi Hung,
I spent a bit of time trying out different solutions and have come up with the following (which is quite similar to what you suggested, thank you!):

meffil.normalize.samples() has a new argument "dup.fun" which is used to 'collapse' duplicate probes. The default is 'median' but any function that takes a vector of numbers and returns a single number can be used.  If "dup.fun" is NULL, then duplicates are not collapsed.
a new function meffil.collapse.dups() can be used to collapse duplicate probes if they were not collapsed by meffil.normalize.samples().   It has two arguments, methylation matrix and the function "dup.fun" for collapsing duplicates.  The default is 'median'.

Hopefully that makes sense!  Do let me know if you think this could be improved or if you notice a problem.
Best,
Matt

This is great. Thank you so much Matt. I will test out the new function with my data and get back to you if I find any other issues.
Sincerely,
Hung

Dear Dr Suderman,
I am not sure whether I should have started a new issue, but since I found the above conversation helpful I decided to continue here. Firstly, I greatly appreciate that meffil.normalize.samples collapses duplicate values to median. However, now that there is only one row per beta, I am not sure how to know which annotation row to use from the "EPICv2.hg38.manifest.tsv".
As far as I see, I could 1) not collapse the replicates, using meffil.normalize.samples(dup.fun=NULL), select the median value for each probe myself and store the full probeID (containing the prefixes_suffix) for later, or 2) use, for instance, the mean of the replicate values, which I would do with meffil.normalize.samples(dup.fun = function(x) mean(x, na.rm = T)) if I have understood correctly.
However I was wondering, is there any way within meffil to know to which row of the annotation file the collapsed probe values correspond to?
Thank you already in advance,
Mikaela


Use versioning in composer

Hi!
I suggest to use versioning inside composer. Since you are using the official clash of clan api, make it as the first revision (1.0.0), to remplace the following line in composer :
"toniperic/php-clash-of-clans": "dev-master",

to
"toniperic/php-clash-of-clans": "1.0.*",

This morning, I updated my composer.json for a multidomain site, and the gaming part of the site crashed after a unwanted update for this package :-(
Thanks for the API implementation.

It's on my to-do list, it's just that I've been very busy lately.


Naughty behavior?

App seems to be janky and laggy when scrolling.
Also (this may not be a issue caused by Amethyst) if you edit your profile (display & username, bio, website, lightning address) none of it seems to carry over when signing in with a different client.

It is true @vitorpamplona
Just scrolling on this makes Snapdragon 8 Gen 1 cry.

I think you might be on to something with the unlimited profile image sizes you mentioned in Nostr. A lazy loading cache of compressed copies (resized thumbnails) of the images could possibly help, possibly worse if not also optimized? Low priority background thread might work out.
This seems like a big challenge.


Upgrade to Flyway 6.5.0 with the ability to read Flyway configuration files.

The most important changes:

Flyway 6.5.0 (bootique-flyway 1.1 version uses Flyway 5.2.0) which is needed to access Oracle 19.
Added configuration option configFiles to read Flyway configuration files enabling you to use ALL Flyway parameters.
bootique 2.0 ready.

I have also updated the unit tests and documentation.

Merged. Much appreciated!!


tag gpu compilers cache with version

Tagging GPU, CUDA and HIP backends with versions, so kernels are recompiled with new versions of compilers.
Updates #2588

Is something like this any better? I am not really sure if compile functions looks nice, but we can compile for the target device as well as cache with details of device/api version.

Does it look any better? This way it allows to compile/search cache for a device passed to compile function.
With compiler_kwrags isn't it harder to pass device.context in ops_gpu with diskcache?


Add an "options" or "args" input to the task

Hello,
I added the task on a pipeline but it fails after 5 minutes on agents that have not run the task previously due to slow download time of the DB and unable to set the "--timeout" to prevent that.
Would it be possible to add an "options" or "args" to customise the command line executed ?

Yep. Can't use this without the ability to specify the config.

Hi, I opened a pull request to support any additional args to pass to the trivy cli.
I don't know who and especially when will validate it


The header (Sec-WebSocket-Protocol) is not returned to the client on the real device

v0.18, websocketserver module. client: chrome
It's all right on the emulator, but it's going to go wrong on the real device, getting Sec-WebSocket-Protocol headers empty strings on the client side
error:

WebSocket connection to 'ws://<IP_ADDRESS>:9001/asdf' failed: Error during WebSocket handshake: 'Sec-WebSocket-Protocol' header value '' in response does not match any of sent values

request:

Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.9,en;q=0.8,zh-TW;q=0.7
Cache-Control: no-cache
Connection: Upgrade
Host: <IP_ADDRESS>:9001
Origin: http://localhost:63342
Pragma: no-cache
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Sec-WebSocket-Key: Nj31L7B8S9YgQmorv/Zi8Q==
Sec-WebSocket-Protocol: sub
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 11_0 like Mac OS X) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Mobile/15A372 Safari/604.1

response:

Connection: Upgrade
Date: Thu, 01 Nov 2018 06:38:37 GMT
Sec-WebSocket-Accept: N872DmYyQlTZNYZnTzQEzOhWWZs=
Sec-WebSocket-Protocol:
Upgrade: websocket

That is indeed a bug. I've fixed it in the latest commit. You can use the master version if you want to test it out. I'll release a new version (0.19) later today.
Another workaround is to not set a Sec-WebSocket-Protocol (if that is possible).

Version 0.19 has been released 🎉


gNMI-1.10 updates

Update TestHardwarePort function to accomodate vendor-specific component naming
Update TestSoftwareVersion() to retrieve SW versions from Supervisors instead of CPUs

This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia’s intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.292%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1181

Relevant Lines:
2098

💛  - Coveralls

/gcbrun

Per offline chat, the cpuType update will be a separate PR for discussion.

Updated per the comment above

The other change moved into #1279

/gcbrun

All changes are about one vendor. Merging this PR upon my own LGTM.


NIFI-12572 Refactor components in azure bundle using current API methods

Summary
Refactor tests and components in azure bundle to use updated APIs from NIFI-12452.
Additionally, makes use of newer Java APIs, e.g. List.of and Set.of for declaration of relationships and properties.
NIFI-12572
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Thank you for your reviews of this and the other PRs @exceptionfactory. Also for taking on the merge process.


Inverted join support in 21.1

Fixes #9114

This change is

Just realized we don't even link to the Joins page on this page. Should probably add one here.

Done.

Also at the end of the file, under "See also"

Done.

Should the INVERTED join hints be listed as well?

Done.

See my comment on joins.md about wording here.

Done.

This is a nice example, but it seems a bit out-of-place on this page, since none of the other, more popular types of joins have examples here.
IDK - I'm sure it'll be fine to keep here. It might just make more sense on the "Inverted Indexes" page (inverted-indexes.md) or the "JOIN expressions" page (joins.md).

I made it an include, and it's now in both inverted-indexes.md and cost-based-analyzer.md.

On the Cost-based Optimizer page (cost-based-optimizer.md), we list "Inverted joins" under "Supported join algorithms". But it's not listed here. If inverted join is an algorithm type at the level of a merge, hash, or lookup join, then we should def also have it here. If it's not, then maybe we should change the title of the "Supported join algorithms" section on the Cost-based Optimizer page to "Supported join types" or something?

Moved it under "Supported join algorithms", as that is what it actually is.

TFTR, Eric and Becca!


Multiple assertions in the integration suite

DNS Policy tests use one huge g.Expect block for validation. It makes it hard to debug. The better approach would be to use a single g.Expect per value. [example]
This issue was created based on this discussion . It is a small task but would refactor all of the DNS-related integration tests so better to be put in a separate issue

covered in #799


split restapi.NewServer

NewServer no longer configures the API but instead relies on
ConfigureAPI call to do it.
Also add a new ConfigureFlags method so that we can add command line
flags from the handlers.
This way we can get additional flags from the handlers and initialize
them once
Signed-off-by: S.Çağlar Onur<EMAIL_ADDRESS>

this needs an update

lgtm


cargo-geiger: 0.9.1 -> 0.10.2

Motivation for this change
Bump cargo-geiger from 0.9.1 to 0.10.2
Closes #106142
Things done

Remove cargo-lock.patch

Upstream crate now compiles fine without patch

Use cargo-insta for testing

Using cargo-insta for testing, we can now run the test suite without
skipping any tests

Excerpt of output for cargo-geiger-0.10.2 build
cargo-geiger>    Compiling cargo-geiger v0.10.2 (/build/source/cargo-geiger)
cargo-geiger>     Finished test [unoptimized + debuginfo] target(s) in 51.15s
cargo-geiger>      Running target/debug/deps/cargo_geiger-6e7cda00618c9c3a
cargo-geiger> running 0 tests
cargo-geiger> test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
cargo-geiger>      Running target/debug/deps/mod-a96760f21b696cb8
cargo-geiger> running 7 tests
cargo-geiger> .......
cargo-geiger> test result: ok. 7 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
cargo-geiger>      Running target/debug/deps/geiger-1fa18bfc535415eb
cargo-geiger> running 0 tests
cargo-geiger> test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
cargo-geiger>    Doc-tests geiger
cargo-geiger> running 0 tests
cargo-geiger> test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
cargo-geiger> info: 6 snapshots to review
cargo-geiger> use `cargo insta review` to review snapshots
cargo-geiger> installing
cargo-geiger> post-installation fixup
cargo-geiger> shrinking RPATHs of ELF executables and libraries in /nix/store/crq68p0a97pa96dfnzalccz53smh59al-cargo-geiger-0.10.2
cargo-geiger> shrinking /nix/store/crq68p0a97pa96dfnzalccz53smh59al-cargo-geiger-0.10.2/bin/cargo-geiger
cargo-geiger> strip is /nix/store/cqxfi2q7d7k6y0q91wcx2cbkj4xsak63-binutils-2.31.1/bin/strip
cargo-geiger> stripping (with command strip and flags -S) in /nix/store/crq68p0a97pa96dfnzalccz53smh59al-cargo-geiger-0.10.2/bin
cargo-geiger> patching script interpreter paths in /nix/store/crq68p0a97pa96dfnzalccz53smh59al-cargo-geiger-0.10.2
cargo-geiger> checking for references to /build/ in /nix/store/crq68p0a97pa96dfnzalccz53smh59al-cargo-geiger-0.10.2...

cc @marsam @8573

Result of nixpkgs-review pr 106258 run on x86_64-linux 1

1 package built:

cargo-geiger

Result of nixpkgs-review pr 106258 run on x86_64-darwin 1

1 package built:

cargo-geiger

That was quick! Thanks!


Module for data retrieval - Sweden

Description
Trello card : (https://trello.com/c/BzbubYVR)

Create a module that retrieves data about confirmed cases and deaths in Sweden on regional - county level.  Suggested data source: https://github.com/elinlutz/gatsby-map/tree/master/src/data/time_series

This will be approached in the similar way to France module (https://github.com/CoronaWhy/task-geo/tree/master/task_geo/data_sources/covid/fr_covidata)

I've started looking at this. The most important help I need at the moment is to agree on data source.

 Create a module for data retrieval: Swedish data

New pull request: https://github.com/CoronaWhy/task-geo/pull/74


Schedules CRUD

Feature Summary
We need to build out CRUD functionality for Schedules as well as their UI.
Intended Outcome of the feature
Once completed, we will be able to list, view, update, add and delete Schedules.
PHP basics that must be included

[ ] Schedule Controller
[ ] Schedule Model that manipulates Schedule Entries
[ ] Validation rules
[ ] Basic test cases

React basics that must be included
Note: Schedules was partially built out and will need to be updated to the current structure.

[ ] Schedules module to list, add, and edit Schedules
[ ] Schedules Form (dynamic or manual?)

Questions we need to answer

https://user-images.githubusercontent.com/106413051/172964700-0af9bd2b-3870-4f94-a119-b7dedac9b355.MOV


fixed indentation bug

This ensures that the specified branch is in fact checked out. It was only a problem with the indentation. The copulpy test fail as I fixed them in copulpy/peisenha_edits but this is not merged into copulpy/felix. I suggest you only merge the changes that make all copulpy tests pass into the copulpy/felix branch and then we made a big step forward.

copulpy/felix branch was merged with your edits to make travis and pytest work. Thanks a lot!


another ordering bug with shortcut refinement

These are the bane of my existence.
void test() {
    I&J ij = Bottom().thing; //error: specified expression must be assignable to declared type of 'ij': 'Object' is not assignable to 'I&J'

}

class Bottom() satisfies Mid1&Mid2<J> {
    thing = object satisfies I&J{};
}

interface I {} interface J {}

interface Top {
    shared formal Object thing;
}

interface Mid1 satisfies Top {
    shared actual formal I thing;
}

interface Mid2<T>
        satisfies Top
        given T satisfies Object {
    shared actual formal T thing;
}

Works fine if I move the test() function to after the declarations.

Looks like I've fixed it.


Use apiextensions-application to remove CAPI dependency

Towards https://github.com/giantswarm/giantswarm/issues/19819
Checklist

[x] Update changelog in CHANGELOG.md.

Tested on gauss


Enabled doxygen validation in CI pipeline.

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

My only concern is that all changes in auto-generated file rest_client.hpp will be discarded next time we update protocol layer.
Some of the changes were caused by missing docs in swagger, which we could fix.

Could we update these comments into the swagger readme transform for storage, so they are retained on re-gen, while we wait for the swagger itself to be fixed and description fields added?

Could we update these comments into the swagger readme transform for storage, so they are retained on re-gen, while we wait for the swagger itself to be fixed and description fields added?

Sure, we can. This is less of a problem and I'm not worried about this.
But docs for enumerations requires updating codeGen. Do you know who maintains codeGen now? or it's not maintained anymore?

Changes to storage SDK LGTM.
My only concern is that all changes in auto-generated file rest_client.hpp will be discarded next time we update protocol layer. Some of the changes were caused by missing docs in swagger, which we could fix. The others, however, require code change in codeGen to fix.

I was worried about this as I was making the changes. But IMHO having up-to-date documentation for everything in the SDK is a bigger deal - there were a LOT of fields that had absolutely no documentation, and while some of them were relatively obvious, others were not.

Could we update these comments into the swagger readme transform for storage, so they are retained on re-gen, while we wait for the swagger itself to be fixed and description fields added?

Sure, we can. This is less of a problem and I'm not worried about this.
But docs for enumerations requires updating codeGen. Do you know who maintains codeGen now? or it's not maintained anymore?

Btw, doxygen is configured to ignore types in the _internal and _detail namespace, would it be possible to leverage that in some way in the codegen (putting the generated types in a _detail namespace and creating human written wrappers for the types we want to expose?)

Noticed in a lot of places you removed the anchor tag on the Azure::Core::Context. Why?

Because doxygen can't resolve anchor tags in other packages without an explicit link. Annoying, but I can understand it.

Fixes #4691


No module named 'im2mesh.utils.libkdtree.pykdtree.kdtree'

Hi, I have some problems with code's configuration.I google it but not found a proper solution.I also follow 'conda env create -f environment.yaml ', but there's something wrong with my network that i can't download.Do you know how to fix this?

Hi @MASTERCHIEF343 ,
could you please provide more details to reproduce your problem? What did you try to achieve? What is the error message? ...

(mesh_funcspace) D:\TF_GPU\occupancy_networks-master>python generate.py configs/demo.yaml
Traceback (most recent call last):
File "generate.py", line 10, in
from im2mesh import config
File "D:\TF_GPU\occupancy_networks-master\im2mesh\config.py", line 4, in
from im2mesh import onet, r2n2, psgn, pix2mesh, dmc
File "D:\TF_GPU\occupancy_networks-master\im2mesh\onet_init_.py", line 1, in
from im2mesh.onet import (
File "D:\TF_GPU\occupancy_networks-master\im2mesh\onet\config.py", line 5, in
from im2mesh.encoder import encoder_dict
File "D:\TF_GPU\occupancy_networks-master\im2mesh\encoder_init_.py", line 1, in
from im2mesh.encoder import (
File "D:\TF_GPU\occupancy_networks-master\im2mesh\encoder\conv.py", line 4, in
from im2mesh.common import normalize_imagenet
File "D:\TF_GPU\occupancy_networks-master\im2mesh\common.py", line 3, in
from im2mesh.utils.libkdtree import KDTree
File "D:\TF_GPU\occupancy_networks-master\im2mesh\utils\libkdtree_init_.py", line 1, in
from .pykdtree.kdtree import KDTree
ModuleNotFoundError: No module named 'im2mesh.utils.libkdtree.pykdtree.kdtree'
Sorry, i didn't make myself clear.This is my error,i don't know how to fix it.

Did anyone find the answer to this?

pykdtree should be automatically built when running
python setup.py build_ext --inplace

Can you verify that the build step was successful?

I am having a similar problem. After doing
python setup.py build_ext --inplace
i am seeing:
running build_ext
building 'im2mesh.utils.libkdtree.pykdtree.kdtree' extension
gcc -pthread -B /home/mat/anaconda3/envs/mesh_funcspace/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/mat/anaconda3/envs/mesh_funcspace/include/python3.6m -c im2mesh/utils/libkdtree/pykdtree/kdtree.c -o build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o -std=c99 -O3 -fopenmp -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=kdtree -D_GLIBCXX_USE_CXX11_ABI=0
im2mesh/utils/libkdtree/pykdtree/kdtree.c:525:10: fatal error: numpy/arrayobject.h: No such file or directory
#include "numpy/arrayobject.h"
^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
error: command 'gcc' failed with exit status 1
Here is how i fixed this:
first you check in python where is your numpy:
import numpy
numpy.get_include()
and then before installing you do:
export CFLAGS=-I/<path_to_include>
in my case it was:
export ### CFLAGS=-I/home/jeremy/anaconda3/envs/mesh_funcspace/lib/python3.6/site-packages/numpy/core/include/

Thanks to @JeremyFisher's fix, I get past the same error that he's having, but then I'm immediately met with another error:
gcc -pthread -B /home/chulabhaya/anaconda3/envs/mesh_funcspace/compiler_compat -Wl,--sysroot=/ -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/chulabhaya/anaconda3/lib/python3.7/site-packages/numpy/core/include -fPIC -I/home/chulabhaya/anaconda3/envs/mesh_funcspace/include/python3.6m -c im2mesh/utils/libkdtree/pykdtree/_kdtree_core.c -o build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/_kdtree_core.o -std=c99 -O3 -fopenmp -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=kdtree -D_GLIBCXX_USE_CXX11_ABI=0
gcc -pthread -shared -B /home/chulabhaya/anaconda3/envs/mesh_funcspace/compiler_compat -L/home/chulabhaya/anaconda3/envs/mesh_funcspace/lib -Wl,-rpath=/home/chulabhaya/anaconda3/envs/mesh_funcspace/lib -Wl,--no-as-needed -Wl,--sysroot=/ -I/home/chulabhaya/anaconda3/lib/python3.7/site-packages/numpy/core/include build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/_kdtree_core.o -o build/lib.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.cpython-36m-x86_64-linux-gnu.so -lgomp
/home/chulabhaya/anaconda3/envs/mesh_funcspace/compiler_compat/ld: build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o: unable to initialize decompress status for section .debug_info
/home/chulabhaya/anaconda3/envs/mesh_funcspace/compiler_compat/ld: build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o: unable to initialize decompress status for section .debug_info
/home/chulabhaya/anaconda3/envs/mesh_funcspace/compiler_compat/ld: build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o: unable to initialize decompress status for section .debug_info
/home/chulabhaya/anaconda3/envs/mesh_funcspace/compiler_compat/ld: build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o: unable to initialize decompress status for section .debug_info
build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o: file not recognized: file format not recognized
collect2: error: ld returned 1 exit status
error: command 'gcc' failed with exit status 1
Any ideas as to what might be causing this, and how to fix it? Thanks in advance!

I managed to solve a similar problem simply by running:
conda install pytorch torchvision cudatoolkit=9.0 -c pytorch

I am having a similar problem. After doing
python setup.py build_ext --inplace
i am seeing:
running build_ext
building 'im2mesh.utils.libkdtree.pykdtree.kdtree' extension
gcc -pthread -B /home/mat/anaconda3/envs/mesh_funcspace/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/mat/anaconda3/envs/mesh_funcspace/include/python3.6m -c im2mesh/utils/libkdtree/pykdtree/kdtree.c -o build/temp.linux-x86_64-3.6/im2mesh/utils/libkdtree/pykdtree/kdtree.o -std=c99 -O3 -fopenmp -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=kdtree -D_GLIBCXX_USE_CXX11_ABI=0
im2mesh/utils/libkdtree/pykdtree/kdtree.c:525:10: fatal error: numpy/arrayobject.h: No such file or directory
#include "numpy/arrayobject.h"
^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
error: command 'gcc' failed with exit status 1
Here is how i fixed this:
first you check in python where is your numpy:
import numpy
numpy.get_include()
and then before installing you do:
export CFLAGS=-I/<path_to_include>
in my case it was:
export CFLAGS=-I/home/jeremy/anaconda3/envs/mesh_funcspace/lib/python3.6/site-packages/numpy/core/include/

I have the exact same problem now but when I run this command in python I get an error. See below. Any hints? thanks!
export CFLAGS=-I/home/user/anaconda3/envs/mesh_funcspace/lib/python3.6/site-packages/numpy/core/include
            ^

SyntaxError: invalid syntax

I found a solution when I build this on windows platform. You can simply add include_dirs=[numpy_include_dir] to each module definition in the setup.py instead of calling anything from the command-line tool.


Add conflict of interest guideline to README

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md

I am:

[ ] Suggesting edits to an existing Topic page
[ ] Curating a new Topic page
[x] Other

This adds a guideline around avoiding conflicts of interest.

Avoid conflicts of interest. If a topic is popular enough to warrant inclusion, someone else will add or improve it.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Thanks for this @johndbritton!


Update youtube.html

Youtube now loads via http or https to fix mixed content errors on https sites

LGTM.


Certain non-text output from launched commands hangs parallel

The following command works with GNU parallel but hangs Rust parallel:
echo testcase.gz | parallel cat '{}' > /dev/null
The testcase file is attached: testcase.gz

I'll have the test case added as a unit test and I'll try to see what's causing the hang.

I know what's causing it. I'm handling outputs by line-buffering them, but because the binary file does not contain newlines, it is hung waiting to read a newline that will never appear.

I'll have a fix released later today. I submitted a pull request for redox's ion shell to support brace expansion and variable brace expansion yesterday, so today I'm working on getting this fixed.

The 0.5.1 update that I've just merged should fix this problem.


Query: Move processing of aggregate functions inside SqlTranslator

This allows us to use those methods to translate aggregates after GroupBy
Resolves #15718

Re-targeting to preview7. This is pre-requisite for SQL GroupBy work.


ide: parallel prime caches

cache priming goes brrrr... the successor to #10149

this PR implements a parallel cache priming strategy that uses a topological work queue to feed a pool of worker threads the crates to index in parallel.
todo

[x] should we keep the old prime caches?
[x] we should use num_cpus to detect how many cpus to use to prime caches. should we also expose a config for # of worker CPU threads to use?
[x] something is wonky with cancellation, need to figure it out before this can merge.

What's left to merge this? I've been dogfooding this for almost 2 weeks now with no issue.

I'll merge it a bit later unless there are objections.

Yeah, this seems good!
bors r+

I have to say, this makes a huge difference for me when working in projects with more dependencies (like in my case, docs.rs)
Thanks! ❤

@syphar maybe you can give "rust-analyzer.cache.warmup": false a try, which completely disables cache priming. I'd be curious to find out how people feel about that.

@syphar maybe you can give "rust-analyzer.cache.warmup": false a try, which completely disables cache priming. I'd be curious to find out how users feel about that.

I will give it a try, thanks! Didn't know about the option.


Sllz.CompressStandard might produce output that cannot be decompressed with ParTool

Describe the bug
YakuzaCommon.Converters.Sllz.CompressStandard always sets the first flag to 0x00, where it is sometimes supposed to be different. The resulting par cannot be unpacked with ParTool, and causes the game to crash when loading it.
Note that this does not always happen. Some pars compressed with the same converter do not have this issue.
To Reproduce
Par that caused this issue is wdr_par/wdr.par from Kenzan. The vanilla files were repacked with compression enabled for all of them (in the game script). The DotRoot writer parameter was false, to replicate ParTool alternative mode.
When comparing the repacked par with the one repacked by ParTool (with compression enabled), it can be seen that the first byte after the SLLZ header (0x10) is always 0x00, where in the ParTool repacked par it was 0x19. The rest of the compressed bytes were identical, however.
Exceptions
Here is the ParTool stack trace when unpacking the par:
Extracting /wdr.par/wdr.par/encount/bugeisha00000000.msg...
Unhandled Exception: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at ParLibrary.Sllz.Decompressor.DecompressV1(DataStream inputDataStream, Int32 compressedSize, Int32 decompressedSize)
   at ParLibrary.Sllz.Decompressor.Convert(ParFile source)
   at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
   at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2)
   at Yarhl.FileFormat.ConvertFormat.With[TConv](Object src)
   at Yarhl.FileSystem.Node.TransformWith[TConv]()
   at ParTool.Program.Extract(Node parNode, String outputFolder)
   at ParTool.Program.Extract(Extract opts)
   at CommandLine.ParserResultExtensions.WithNotParsed[T](ParserResult`1 result, Action`1 action)
   at ParTool.Program.Main(String[] args)

Additionally, Sllz.CompressStandard allows compressing some streams that ParLibrary would not compress. This is probably because an exception would be thrown when compressing with ParTool, which causes the file to not be compressed. With Sllz.CompressStandard, those files are compressed regardless (and still have the same issue with the first flag as described above). I am not sure if this would cause any issues, but thought I should mention it.

Hello!
About the "first flag issue", could you send me your recompressed wdr.par to make some tests with it?
And, about the last paragraph, the original par files have some conditions when the files are not compressed... One of them is that the compressed file size is bigger than the uncompressed one (this may happen if the file is already compressed). I've replicated this condition in Partool and Sllz.CompressStandard with the exceptions thrown while compressing. But there is also other condition: the file won't be compressed if the difference between the original and compressed size is less than 2048 bytes. I put that condition in ParTool, but not in Sllz.CompressStandard, so it may cause the different behaviour between the 2 tools.

Here is the file: wdr.zip
I used the 010 editor template to compare between the two files, so I was able to find the flag difference easily.

I put that condition in ParTool, but not in Sllz.CompressStandard, so it may cause the different behaviour between the 2 tools.

I see. So it will not cause any issues since the game should be able to read it, right?


KeyError: 'cr' when loading a circuit containing c_if using qpy

Environment

Qiskit version: 1.0.2
Python version: 3.11.8
Operating system: Ubuntu

What is happening?
Running the below circuit resulted in a key error. I would expect it to run without error.
How can we reproduce the issue?
from qiskit import QuantumCircuit, ClassicalRegister, QuantumRegister
from qiskit.circuit.library.standard_gates import RZXGate

qr = QuantumRegister(2, name='qr')
cr = ClassicalRegister(2, name='cr')
qc = QuantumCircuit(qr, cr, name='qc')
qc.append(RZXGate(0).c_if(cr, 0).repeat(1), qargs=qr, cargs=qc)

from qiskit import qpy
with open('circuit.qpy', 'wb') as fd:
    qpy.dump(qc, fd)
with open('circuit.qpy', 'rb') as fd:
    qc = qpy.load(fd)[0]

What should happen?
Traceback (most recent call last):
  File "/mnt/tests/reproduction/reproduce_cr_1003.py", line 13, in <module>
    qc = qpy.load(fd)[0]
         ^^^^^^^^^^^^
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/interface.py", line 333, in load
    loader(
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/binary_io/circuits.py", line 1263, in read_circuit
    custom_operations = _read_custom_operations(file_obj, version, vectors)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/binary_io/circuits.py", line 516, in _read_custom_operations
    definition_circuit = common.data_from_binary(
                         ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/common.py", line 262, in data_from_binary
    obj = deserializer(container, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/binary_io/circuits.py", line 1265, in read_circuit
    _read_instruction(
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/binary_io/circuits.py", line 216, in _read_instruction
    _loads_register_param(condition_register, circuit, registers),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/anaconda3/envs/qiskit1.0.2/lib/python3.11/site-packages/qiskit/qpy/binary_io/circuits.py", line 185, in _loads_register_param
    return registers["c"][data_bytes]
           ~~~~~~~~~~~~~~^^^^^^^^^^^^
KeyError: 'cr'

Any suggestions?
No response

Fixed by #11940.

Sorry, that last comment was a bit short.  The problem you're seeing should have been fixed by #11940, due to be released in Qiskit 1.1.0 in May - I didn't want to backport it, because it's a bit too much of a change to an existing method for me to feel safe backporting it to stable patch release - but you can install from the main branch if you need it sooner.
Thanks for the report, and please feel free to re-open this if there's more problems I missed.

Thank you for your quick response! Yeah I will try Qiskit 1.1.0 in May and see if it got fixed.


rclone fails to work under windows...

running in a "administrator" cmd window on win7-64:
rclone is 1.33
C:>dir
Volume in drive C is OS
Volume Serial Number is F603-C5EB
Directory of C:\
18/09/2012  02:20              dell
28/08/2012  21:17              Drivers
06/12/2013  01:05              inetpub
28/08/2012  13:01              Intel
13/07/2009  20:20              PerfLogs
06/07/2016  10:14              PKI-SERVICE
05/10/2016  16:54              Program Files
28/07/2016  17:16              Program Files (x86)
18/12/2013  04:21              Users
21/09/2015  12:50              Windows
0 File(s)              0 bytes
10 Dir(s)  94,459,953,152 bytes free
C:>Users\Operetta\Desktop\rclone-v1.33-windows-amd64\rclone.exe sync Users Amazon:rclone/oprt
2016/10/06 11:08:33 amazon drive root 'rclone/oprt': Waiting for checks to finish
2016/10/06 11:08:33 amazon drive root 'rclone/oprt': Waiting for transfers to finish
2016/10/06 11:08:34 amazon drive root 'rclone/oprt': not deleting files as there were IO errors
2016/10/06 11:08:34 Attempt 1/3 failed with 0 errors and: failed to open directory "\?\C:\Users\Default User": open ?\C:\Users\Default User: Access is denied.
2016/10/06 11:08:34 amazon drive root 'rclone/oprt': Waiting for checks to finish
2016/10/06 11:08:34 amazon drive root 'rclone/oprt': Waiting for transfers to finish
2016/10/06 11:08:40 amazon drive root 'rclone/oprt': not deleting files as there were IO errors
2016/10/06 11:08:40 Attempt 2/3 failed with 0 errors and: failed to open directory "\?\C:\Users\Default User": open ?\C:\Users\Default User: Access is denied.
2016/10/06 11:08:40 amazon drive root 'rclone/oprt': Waiting for checks to finish
2016/10/06 11:08:40 amazon drive root 'rclone/oprt': Waiting for transfers to finish
2016/10/06 11:08:40 amazon drive root 'rclone/oprt': not deleting files as there were IO errors
2016/10/06 11:08:40 Attempt 3/3 failed with 0 errors and: failed to open directory "\?\C:\Users\Default User": open ?\C:\Users\Default User: Access is denied.
2016/10/06 11:08:40 Failed to sync: failed to open directory "\?\C:\Users\Default User": open ?\C:\Users\Default User: Access is denied.
C:>

Is this related to this issue that was closed?
https://github.com/ncw/rclone/issues/692
"c:\Users\Default User" is a a junction point for
"c:\Users\Default"
rclone.exe sync "c:\Users\Default User" Amazon:rclone/testdefault
rclone.exe sync "c:\Users\Default" Amazon:rclone/testdefault
Do these do anything different?
Also do you really need to backup your default profile :P

@justusiv good thinking.  That was merged to master so will be in the latest beta: http://beta.rclone.org/v1.33-55-g98804cb/
(Not a windows expert so help much appreciated!)

I'm going to assume this is fixed now - please re-open if not.


Custom filters for organisations

Motivation
Users that are not super users have the same image filter like the Lunes staff. This is functionality is obsolete since normal users don't have confirmed and unconfirmed images.
Proposed Solution
Implement a custom filter for non-superusers to filter regarding the amount of images a document has.
Alternatives
Alternatively delete this filter for non-superusers.

Fixed :)

No fixed :(


Add pty support (cannot use ExpectIt with qemu)

qemu fails with "We need a terminal output" if running with display curses
How to reproduce:
Step 1: Download the OS image:
curl https://download.freebsd.org/ftp/releases/VM-IMAGES/12.0-RELEASE/amd64/Latest/FreeBSD-12.0-RELEASE-amd64.qcow2.xz | xz --decompress >freebsd-original.qcow2
Step 2: Run this:
	public static void main(String[] args) throws Exception {
		File currentDir = new File("../qemu/install/bin").getCanonicalFile();
		System.out.println ("cd " + currentDir);
		String[] cmd = {
				"qemu-system-x86_64", // Change this to match your distro's conventions
				"-display", "curses",
				"-snapshot",
				"freebsd-original.qcow2"
		};
		System.out.println (String.join(" ", cmd));

		Process process = new ProcessBuilder(cmd)
				.directory(currentDir)
				.inheritIO()
				.start();

		try (Expect expect = new ExpectBuilder()
				.withInputs(process.getInputStream(), process.getErrorStream())
				.withOutput(process.getOutputStream())
				.withTimeout(90, TimeUnit.SECONDS)
//				.withExceptionOnFailure()
				.withCharset(StandardCharsets.US_ASCII)
				.withEchoInput(System.out)
				.withEchoOutput(System.out)
				.build())
		{
			expect.expect(exact("Autoboot in"));
		};
	}

The error originates from static void curses_display_init(DisplayState *, , DisplayOptions *) in ui/curses.c, line 714: https://git.qemu.org/?p=qemu.git;a=blob;f=ui/curses.c;h=fb63945188b2affe70ed23c76231456af07afd36;hb=HEAD#l714
    if (!isatty(1)) {
        fprintf(stderr, "We need a terminal output\n");
        exit(1);
    }

i.e. qemu checks if stdout (file descriptor 1) is a tty and refuses to start if not.
This can be avoided by using a pty, see https://en.wikipedia.org/wiki/Pseudo_terminal for an introduction.
I did a bit of digging around and found several JNA-based libraries that give access to ptys, with code for different operating systems; I didn't take notes but I can find them again if you are interested.

I'm not sure that the Expect java library should deal with direct PTY access. Have you tried to combine ExpectIt with Pty for Java  from JetBrains? Looks like to should work just fine since it gives the access to standard output streams.

I seem to have taken a look at it: the browser still remembers it, even though I don't.
I can't recall what exactly failed with it; I guess either qemu wouldn't recognize the pty anyway, or it didn't occur to me to try and combine Expectit with pty4j.
The readme mentions that Java has issues with forking, and that pty4j uses forking. Today, I wouldn't want to use code like that, tough obviously YMMV.
Generally speaking:

I do think that any expect-like library should offer using ptys; after all, expect does, and the very purpose of expect is to make interactive software scriptable; pty-using software is just one (important) kind of interactive. That's in favor of implementing it, be it in the form of making a pty4j-expect library that pulls in both pty4j and ExpectIt and offers whatever glue code may be necessary, be it in the form of new code.
My personal use case has vanished, since I have given up on qemu anyway. So feel free to close this :-)
I have come to the conclusion that getting ptys right may be a lot of effort, so that's another reason for you to close the request ;-)

Oops, misclick. Feel free to reopen if you want to do implementing anyway.


Refactor for parallel processing that using CUDA at model-based Rerankers

From now, all rerankers put a query to reranker model ‘one by one’
It uses ‘async’, but it is not effective since the key to the parallize using model is putting model itself.
So, we have to refactor all rerankers that supports ‘real parralell’ processing. Put enough batch size ‘query and context’ set to model, and gather the results at once.

[x] #304
[x] #305
[x] #306
[x] #307
[x] #308
[x] #309

Close this since we parallel processing all rerankers


Bumps botframework-config in the main package to 4.4.0

Coverage decreased (-0.004%) to 57.196% when pulling 17159a93bfe565dbb2f15fbc9a242804bb1e0761 on cwhitten/bump-botframework-config into 7b28956fe942957d012dca79fabbd68e5e37ac73 on master.


Force Bazel to use our CROSSTOOL [phab:D547]

Created by schroederc at 2015-10-12 18:46:49:
This bypasses the breakage caused by #788

schroederc wrote at 2015-10-12 18:47:31:
Add TODO

shahms accepted this revision at 2015-10-12 19:36:47

schroederc closed via commit a7fa47eec427e2bb9bd5071d08e3e2c712351b31 at 2015-10-12 19:37:12