Slow response time (API vs Playground)

Bug Description
It's a lot slower to trigger chats via API than in Playground.
In Playground, it will say it takes <2 seconds, however through the API.. it takes a lot longer.
Reproduction

Trigger chat via API

Expected behavior
Expecting the same response time, as in Playground.
Who can help?
No response
Operating System
MacOS
Langflow Version
1.1.1
Python Version
3.10
Screenshot
No response
Flow File
No response

you can refer my finding
https://github.com/langflow-ai/langflow/issues/4394


Poc ee test

There were the following issues with your Pull Request

Commit: 471a018afc6319cb00bcbc09bec08c2352685e02
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

@ldimaggi snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1416-fabric8-ui.int.rdu2c.fabric8.io


Change behavior of Import form: when the db already has Nexus data, don't close the form

The current behavior is the Import form would close and go back to main form, when the existing database already contained Nexus imported data.
Changing the behavior to stay on same form now. The reason is that most frequently the user wants to drop the existing db as a choice and does not need to back back to main form. This saves several clicks to have to open the import form again
Also, make the Close button visible.

To test, try to import data in an existing SQL Nexus db that has prior data imported into it. You will be told that there is already data but the Import diaglog will not close like it used to do.


Setof test

Draft until #46 is merged. Test is currently broken.

I hear @workingjubilee fixed this. :) Feel free to push directly to this branch if you want!

Yessss


Using operation Id to overload HTTP methods or passing an array of operations to HTTP methods

Current openapi 3.0.0 basic structure :
{
  	"openapi": "3.0.0",
  	"servers": [ ],
  	"info": { },
  	"tags": [ ],
  	"paths": {
		"<http method type>" : {
        			"tags": [ ],
                                "summary": " ",
                                "description": " ",
                                "operationId": "<unique operation id>",
                                "parameters":[ ],
        			"requestBody": { },
                                "responses": { }
		}
  	}
}

This structure forces to have single method of its kind per path which is not suitable when there are multiple operations of same method type that can be performed on the single path. Openapi 3.0.0 gives us the option of using oneOf in both request body and responses but does not provide a query parameter overloading or scenario where there are two required query parameters that are mutually exclusive. Regardless of anything mentioned above restricting single method type for each path puts restrictions on lot of real world api uses cases from being handled.
Two ways to resolve, changes that I'm suggesting:

Given openapi specification requires operationId to be unique throughout the spec file we can use it one layer below the path itself instead of method types to provide possibility of using multiple operations for same method under same path.

{
  	"openapi": "3.0.0",
  	"servers": [ ],
  	"info": { },
  	"tags": [ ],
  	"paths": {
		"<unique operation id>" : {
        			"tags": [ ],
                                "summary": " ",
                                "description": " ",
                                "method": "<http method type>",
                                "parameters":[ ],
        			"requestBody": { },
                                "responses": { }
		}
  	}
}

or

we can provide operations with same method type as an array to the method type key

{
  	"openapi": "3.0.0",
  	"servers": [ ],
  	"info": { },
  	"tags": [ ],
  	"paths": {
		"<http method type>" : [
  			{
        			"tags": [ ],
                                "summary": " ",
                                "description": " ",
                                "operationId": "operation 1",
                                "parameters":[ ],
        			"requestBody": { },
                                "responses": { }
  			},
  			{
        			"tags": [ ],
                                "summary": " ",
                                "description": " ",
                                "operationId": "operation 2",
                                "parameters":[ ],
        			"requestBody": { },
                                "responses": { }
  			}
		]
  	}
}

Related Issues:
https://github.com/OAI/OpenAPI-Specification/issues/182
https://github.com/OAI/OpenAPI-Specification/issues/791
https://github.com/OAI/OpenAPI-Specification/issues/298
https://github.com/OAI/OpenAPI-Specification/issues/868
https://github.com/OAI/OpenAPI-Specification/issues/1500

operationId is not a first class HTTP concept and therefore shouldn't be used to distinguish between logical operations.  If we are to allow query parameters to discriminate between logical operations then we need to promote query parameters up into the "paths" keys.  That makes "paths" the wrong name but conceptually that's where the differentiation should be made.
We have discussed this in the past and there are a number of people who would like to see this capability added.  However, currently this is one of the few remaining opinionated parts of OpenAPI.  Today only the path portion of the URL can define the operation.


ERROR! ERROR!! ERROR!

When I try to run "./emulationstation" in terminal, I get the following errors:
lv10:          Error creating SDL window!
Could not get EGL display
lv10:          Renderer failed to initialize!
lv10:          Window failed to initialize!
Also, I am running "./emulationstation" while it is selected onto the directery "/opt/retropie/supplementary/emulationstation"
I hope that I can get some help from you.

Do you try to compile EmulationStation in Raspbian or in RetroPie?

I forgot about this this thread and figured it out by myself and it works! I will close this thread.


tab switching in other tabs besides editor tabs.

Typing gtor gT doesn't switch tabs when in the settings tab, or other non-editor tabs.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


stream processing blocking

This is really annoying.... The creator of rpc streams has to take care that they don't deadlock each other. This means: a caller needs to drain the whole stream and not start new rpc calls while reading that stream and block for that new answer before reading more of the other stream... Sounds convoluted but imagine this:
src, err:= client.Source(/* call with lot's of replies*/)

for {
  v, err := src.Next(ctx)
  if eof { break }

  // process v

  // if the backlog of objects in the pipe for src is too big, the reply for this call does not arrive.
  resp, _ := client.Async()

}

A work around for this can be to read all messages from source into ram and then process them as a next step, like this:
var msgs []interface{}
snk := luigi.NewSliceSink(msgs)

src, err:= client.Source(/* call with lot's of replies*/)
// check(err)

err = luigi.Pump(ctx, snk, src)
// check(err)

for _, v:= range msgs {
  // process v

  resp, _ := client.Async()
}

An increased bufSize just hides the problem in the garbage collector.
https://github.com/cryptoscope/go-muxrpc/blob/b76bb2cd2c270b2ab6964926d167b97806586a5d/rpc.go#L54
This can be especially nasty in the case of ssb-blobs requests where whole files can hide in this area.

a bit more background: there is a single read-loop (rpc.Serve) that reads new packets, spawns requests and pours packets to existing requests via luigi.Pipe()s. These have a buffer size, the bufSize above. This size is not in bytes but in messags, which can be codec.Bodys with quite large bodies.


keepa 1.0.0 async keepa

I'm starting to turn keepa full async + sync version

So you know I started to work on it ;)

Ok code looks ok, you can now use keepa like this :.AsyncKeepa

There is another problem with azure pipeline, don't understand what's going on yet.

It's just that the hidden variables (the testing key for keepa) are not being added to external branches.  let me add you as a developer and you can push a branch right to this repo for testing.


Is possible to known when a Sneakers worker has a job done?

I need to know if a Sneakers worker has done your job or not, its possible?

You could do this with the ack! method.

You could even publish another method to denote raising a semantic event that a specific work is done:
class AnotherSweetWorker
  include Sneakers::Worker
  def work(msg)
    ack!
  end

  def ack!
    publisher.publish 'well done!', to_queue: 'another_sweet_job_completed'
  end
end

Nice! Thank you for clarify


string formatting in views.py

Fix the standard connection error message:
conn_err_msg = """\
Pyramid is having a problem using your SQL database.  The problem
might be caused by one of the following things:
1.  You may need to run the "initialize_app_db" script
    to initialize your database tables.  Check your virtual
    environment's "bin" directory for this script and try to run it.
...

No longer an issue - was deleted.


prw2.0: Added support for "custom" layouts for native histogram proto

Result of the discussions:

https://github.com/prometheus/prometheus/issues/13475#issuecomment-1931496924
https://cloud-native.slack.com/archives/C02KR205UMU/p1707301006347199

cc @krajorama @beorn7 @zenador

Addressed all and fixed tests. Thanks @beorn7 for patience!

Yea, this might get replaced with new protobuf (+gogo removal)


Error - ReactDOM.render is no longer supported in React 18, when using _

Describe the bug
When i try to create a custom Component in react using the _ function, the following error appears -
app-index.js:31  Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createroot
To Reproduce
Steps to reproduce the behavior:

Add a custom component like so -

const columns = [{
  name: 'Status',
  id: 'status',
  formatter: (cell: any) => _(<StatusBadge status={cell} />)
}, {
  name: 'Frequency',
  id: 'recurring'
}]

Expected behavior
The library should be compatible with React 18
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS 14
Browser chrome, edge
Version 118

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

i also get the same error.

Fixed.


ASDK-2591

ASDK-2556

Coverage decreased (-0.09%) to 8.4% when pulling 42cd328b89093b4e79dce46c693b0daa7a912034 on dev_2556_2591_2625 into 237b21d6fed04adca0ad852758ed57da7a5eca58 on development.


Compatibility with hashid libraries in other languages

Hi @ivanakimov, apologies for n00b question. I was hoping to use hashids on both server (Rails-API) and client (Javascript). I am fairly new to hashing and I wasn't sure if I would get reliably consistent results on both server-side and client-side when encoding/decoding the hashids. Should that be the case?
Thank you!

Yes, as listed on the main site under "compatibility", all the different libraries should work fine with each other as long as they are the same version, and you're using the same salt value.
http://hashids.org/#compatibility
Javascript only supports numbers up to 2^53 - 1 though so if you're going to use 64-bit integers than you need to split them up or handle them some other way for the client/js side.

Yes, should be compatible, if not please open an issue in either repo w/ examples.


Create Github action for CI

maybe we could remove .travis.yml as well?

maybe we could remove .travis.yml as well?


Add Migration complex issue

I have not distilled this down to a simple example from my model, but I have traced the problem to a point in the code.
The basic gist is that I have three entity types that all inherit from a base type, have a complex type property mapped to the same table, and point to similar tables (separated by database schema, basically TPT).
Adding a fourth table in a new migration will, instead of creating the new table, rename the first table to the new schema, append the new columns to it, rename the second table to the first schema, rename the third table to the second, and then recreate the third table with the first tables schema.
Via debugging and stepping through I have narrowed down the problem to https://github.com/aspnet/EntityFrameworkCore/blob/rel/2.0.1/src/EFCore.Relational/Migrations/Internal/MigrationsModelDiffer.cs#L435
Mainly the problem is that the TableMapping of the types includes both the entity type and the complex type. The new table also has its entity type, and the same complex type, and is considered a match, since an Any comparison is used. This causes the migration code to think that the table is being moved (changing schema).
I understand that this is an edge case and I will see if I can overload the differ and come up with a workable solution for myself, but I think this may also be an oversight of the addition of the owned relational code (it is very likely that complex types will be shared).
Further technical details
EF Core version: 2.0
Database Provider: SqlServer
Operating system: Win10
IDE: Visual Studio 2017

I got a variant that works for me, thought I have not refactored or optimized it, just broke it out and made it as verbose as possible to step through.
WARNING: UGLY CODE
`
foreach (var se in s.EntityTypes)
foreach (var te in t.EntityTypes)
if (string.Equals(se.Name, te.Name, StringComparison.OrdinalIgnoreCase)
&& string.Equals(se.DefiningNavigationName, te.DefiningNavigationName, StringComparison.OrdinalIgnoreCase))
{
var dse = se.DefiningEntityType;
var dte = te.DefiningEntityType;
while(string.Equals(dse?.Name, dte?.Name, StringComparison.OrdinalIgnoreCase))
{
dse = dse?.DefiningEntityType;
dte = dte?.DefiningEntityType;
if (dse == null || dte == null)
break;
}
if (string.Equals(dse?.Name, dte?.Name, StringComparison.OrdinalIgnoreCase))
return true;
}
            return false;

`
This recursively follows the defining navigation if present to compare the tree instead of just the first set of names.
Better ways could be to filter out the complex in the type mapping, or a better way to get the identity of a complex, but this works for my needs.

Dupe of #9873?

Didn't see that one... Yes I would say their problem is the same as mine. I wonder if my "fix" would work for them.

We're happy to accept a PR on this if you're willing to write a few tests 😁

I do not have the time right now to create any tests and my model is fairly complex and not a good candidate. I am not working with the checked out source on my system but I did find new problems with the last preview release (2.1.0-preview1-27377) so I cleaned up my code, and created a commit for it. I created it by creating a custom class, modeling your source and then working out the changes. (for me this was simpler than downloading the whole repo and building a source version and then binding it.)
If you want I can submit the fix as a PR but it is only the fix, no tests and I would like it if someone else who is having this issue (and has made some test code) could patch it in and test it.

I encoutered the same problem. Adding a migration that should generate a new table caused a bad migration when this new table owned a complex type property.
Ex: I had 2 entities, Member & Business, wich both have a complex type Address
I created a 3rd one, Entrepreneur, also with a complex type property (owned property).
The generated migration renamed Member-->Entrepreneur, Business-->Member and created the Business. And also adjusting properties for each modified Table.
My work around is to add a migration with this new table without the complex type property first, so basicly an empty table in my case. And then add another migration with the complex type. This way the generated migration won't be messed up.
Ex: If you have Member & Business, wich both have a complex type Address
Create the new entity Entrepreneur without Address, Add-Migration.
Add the Address property to Entrepreneur, Add-Migration.
It should generate the migration as expected.

I encountered this issue last night, I believe. Should I open a new issue or post here? Thanks!

@kjbetz Please post a new issue, including a runnable project/solution or complete code listing that demonstrates the behavior you are seeing.

Got it @ajcvickers, Thanks!


[205] support for non-state jinja files?

Describe the bug
Not sure this is a bug. Is salt-lint meant to support linting of jinja template files that are not salt state files, e.g. sourced templated files used in file.managed states, for instance?
To Reproduce
Steps to reproduce the behavior:

Run salt-lint on any file named like <name[.jinja|.j2]>
Get result [205] Use ".sls" as a Salt State file extension

Expected behavior
Return lint result for jinja template that's not a salt state, not 205.
Desktop (please complete the following information):

Version 0.9.2

Additional context
https://github.com/warpnet/salt-lint/commit/1c2aa5c62ac0eeeaaa6710c0380a92f825351a2a added support to run rules against different file types, namely  LANGUAGE_SLS and LANGUAGE_JINJA. However, the file extension rule doesn't specify a languages configuration, but that's presumably on purpose to avoid running into a chicken-and-egg problem.
But, if (pure) jinja linting is meant to be supported, shouldn't the (state file) extension check ignore files that bear a jinja extension only, i.e. without sls anywhere in front of it?

Any update on this issue ? Cause I had to rename a map.jinja file of an official formulae: https://github.com/saltstack-formulas/dovecot-formula/pull/27
and this is not recommended by Salt.


Delete manifests/j/JanDeDobbeleer/OhMyPosh/7.59.4 directory

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run


feat: add daisy slider component

What is it?

[x] Feature / enhancement

Description
This PR closes #191.

Expanded the headless slider component to allow customization
Implemented daisy version

Screenshots/Demo

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation

That's great 👏


Adjusted minimum requested cpu and memory resources for deployment tiers

Uprev'd chart version to 2.1.1

Changes summary:
Robustness Improvements

Updated minimum cpu and mem resource requirements
Added additional checkpoints to ensure config-sync success
Improved bringup logging


Rewrite and improve lb_short_result()

Do a proper function where user can set 'ok' and 'failed' labels and where exit code option can be set.

Done in commit d482482d0adc7e17395c4cd179800de78965af43


Merge the commit that removes ? from libsyntax

https://github.com/rust-lang/rust/pull/34312
@erickt if you haven't started working on this already, I can take care of it.

I plan to do 3 separate merges: 9de2de1^, 9de2de1, 5522e678b where 9de2de1 is the ? commit and 5522e678b is nightly 2016-06-20. This isolates ?-related conflicts and makes the other two easier.


How to download the data from multiple FDSN clients?

How to download the data from multiple FDSN clients? The ConfigParameters().client_url_key seems not to support the list input.

Hi @LevCarlo, this argument is actually passed to obspy.clients.fdsn.Client(), which doesn't support multiple argument. A network code could be hosted by multiple data center, which creates ambiguities. So I would recommend you to download separately if the data you want is hosted by different data center.


Integrating lodash

Can someone help me with an example how to add lodash
I did this
 typings install lodash --save --ambiant
but
 import * as _ from 'lodash'
doesn't work

works fine here. Only installing the typings will not work, you need the library as well:
npm install --save lodash
typings install lodash --save --ambiant
import * as _ from 'lodash'

Thanks

typings install lodash --save --ambient
typings ERR! deprecated The "ambient" flag is deprecated. Please use "global" instead
?

npm i @types/lodash --save-dev
npm i lodash --save
when i import lodash in my code
import * as _ from "lodash";
_ is empty - what i'm doing wrong?


 I took it as a personal challenge -- and I have some other extension ideas, and wanted to delve into it a bit anyhow.
We now have a single test case, but it's a nominally useful one: prove that formatting works.
Not sure how actually-useful this is, especially if it isn't hooked into CI, but it's perhaps a bit easier than testing things by hand. Especially if we can use the APIs to inspect overlays, this should be sufficient to test basic functions, settings, and commands.
If you like the idea, I can look into adding a GitHub job for CI coverage. (I'm sure it will be pure joy getting Ruby, Node, Electron and all of the bells and whistles crammed into a container; at least Microsoft has some examples to get us started.)

Yeah I think this will work. Shouldn't be too bad to integrate it into GitHub actions. I had to set up something similar with prettier which is here: https://github.com/prettier/plugin-ruby/blob/main/.github/workflows/main.yml#L23-L32 should get you close to what you need.

Here's something that runs, but hangs. Works locally on my Mac laptop.
https://github.com/xeger/vscode-syntax-tree/tree/tests
The dbus warnings are probably harmless but the "socket got disposed" stuff is suspect; something's not running right.

@xeger looks like this is maybe working now? what's the status?

It's not quite working; I can get VS Code running in CI, but it hangs when we issue the command to format code. Need to SSH in and add tons of printf debugging. Thrilling!
The test suite is runnable in local dev; if you'd prefer, we could merge it now and hold off on the CI stuff. (Just merge everything except the .github changes in that case.)

Nah let’s keep the PR open. I’ve worked in code bases with tests that are
local-only and they almost always go stale.
On Thu, Jul 7, 2022 at 8:33 PM Tony Spataro @.***>
wrote:

It's not quite working; I can get VS Code running in CI, but it hangs when
we issue the command to format code. Need to SSH in and add tons of printf
debugging. Thrilling!
The test suite is runnable in local dev; if you'd prefer, we could merge
it now and hold off on the CI stuff. (Just merge everything except the
.github changes in that case.)
—
Reply to this email directly, view it on GitHub
https://github.com/ruby-syntax-tree/vscode-syntax-tree/pull/15#issuecomment-1178403373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABG3P3QPWJFYYO27VG6V2Z3VS5ZN5ANCNFSM52OJ2O3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ugh! This is truly mysterious. Here's what happens when I trace RPCs to the language server.  The integer is the PID.
So:

VS Code spawns two copies of the LS?!?
We never even receive the RPC to format the document (yet the executeCommand call that our test makes to Code, hangs anyway?!)
the only exception we throw in Ruby is the Interrupt when I ctrl+C out of the parent process

TL;DR this is mysterious and I'm not sure where to go next. If I could debug the node process that actually runs the tests, I could step into executeCommand and try to make sense of it, but that way lies madness.
Perhaps I'll instrument LanguageClient and see if I can prove that Code is dispatching to the right thing... not looking good here. If you know of any other extensions that have test coverage, or have any bright ideas, I'm all ears!
ST 8513 request initialize 0
ST 8513 request initialized
ST 8514 request initialize 0
ST 8514 request initialized
ST 8513 request textDocument/didOpen
ST 8514 request textDocument/didOpen
ST 8513 request textDocument/inlayHint 1
ST 8513 WILL inlayHint
ST 8513 DID inlayHint
ST 8514 request textDocument/inlayHint 1
ST 8514 WILL inlayHint
ST 8514 DID inlayHint
!! Interrupt
!! Interrupt

Well damn @kddnewton - there's some double-registration glitch that's blocking the tests in CI.

Okay @kddnewton: I have something of little worth that is merge-able; suggest we merge it just to get some CI coverage, and then I can iterate on test coverage. Boy, do we have some issues to overcome!
= Too Slow
The biggest issues with testing are performance and visibility: stuff is just slow; in CI, it's very slow, and extremely difficult to understand what has happened when things fail. I spent Friday evening hacking Xvfb and ffmpeg to grab videos of the Code window during test execution, which was the key to understanding. I'd like to make this more elaborate in future (e.g. new video for every test case) but as-is, our extension is probably in the top 1% of usability among all extensions test suites. I will probably turn the initialization/video stuff into an action at some point because it's useful with other extensions.
= Too self-referential
Another significant issue with testing is circularity: often we need to inspect the output channel to verify the extension is doing what we want, but Code's API makes it impossible to interact with output channels unless you're the owner -- so we need to use commands like "Show Output Channel" and then rely on hacks (e.g. the channel is a TextDocument while it is visible) to inspect. And, we have no way to clear the channel so we can't distinguish new output from old.
If I add a Clear Output Channel command, that ought to be sufficient to reset the IDE to a clean initial state after every test case, which will let us add meaningful coverage for the rest of the commands (start/stop/etc).
We need to do other obnoxious things (e.g. "close all the windows, focus on file tree")  to get the IDE back to an initial state but it's a solved problem and takes just a few hundred ms per test case.
= Too many language clients!
My hunch about the hang I was seeing with "Format Document" is: the extension is getting activated twice in a row! We have no guard against this, so we happily spawn two language servers and that explains why we have two options for Syntax Tree when we issue the format-document command. (There is no API for interacting with those modal popups so once one is visible, it's game over.)
I'd like to fix the test coverage for the basic commands first, and then (realistically) I need to add a couple more options to make this extension suitable for my developer teams, then coax you into shipping a new build to the marketplace. After I've got my devs using it, however, I think I have enough information now to get to the bottom of the reentrancy issue and prevent it or work around it, to add test coverage for Visualize and Format.
TL;DR - I am happy with this; it's a good start, and I'm very proud of the video stuff. Merge away!

@xeger sorry but do you mind rebasing? Then I'll merge!


US 01.02.01

As an owner, I want to view an item and its details.
Requirements/Prerequisites:

US 01.01.01, must have functionality to add items before completing this story
Transition to view/edit activity from inventory activity by clicking an item
Display all information associated with the item

Just need date selection from add item story

Actually we will call this one finished for now, we can add a separate viewing fragment later if we decide we want one


Fix parallel build limiter

Wait for builds when they are pendning after starting
Change-type: patch
Signed-off-by: fisehara<EMAIL_ADDRESS>

@balena-ci  I self-certify!


Feature request: Add principle field to TxContext

Description
This feature adds a principal field to the TxContext field in the Move contract. The principal field specifies the address of the entity that should execute a given transaction. For example, in a coin swap, the swapped token is sent to the principal address rather than the signer address.
Note that the recipient address can be either an account address or an object ID when the transfer-to-object feature is implemented.
Rationale
In some scenarios, the signer of a transaction may be different from the entity that actually executes the transaction. For example, in a multi-sig wallet, one of the owners submits the transaction, but the multi-sig wallet itself executes the transaction. In this case, the signer acts as a proxy for the multi-sig wallet, which is the actual principal.
By adding a principal field to the TxContext, this feature decouples two concepts:

Proxy - Transaction sender / signer.
Principal - The entity that actually executes the transaction.

Proposed Solution
This feature proposes the following changes:

Add a principal field to the TxContext.
By default, the principal field is set to the same address as the signer field.
User can optionally set the principle value when submitting a transaction.
The principal field can be either an account address or an object address or UID.
Applications should use the principal address as the address that actually executes the transaction.

Non of it yet


Update push-kaggle-dataset action

This action is currently broken due to a requirement import error. v3 Is the bugfix
See error at https://github.com/jerrychong25/malaysia-map-data/runs/5248841396?check_suite_focus=true
Untill merged, the synch between your repo and kaggle wont work.
Disclaimer: I am the author of the action.

Thanks for your great contribution on fixing mentioned GitHub Action issue!


Glob option?

I would love to use ur project like this: imageoptim images/**/*.{png,jpg,jpeg,gif} --lint --tolerance=0.8 --reporter=flat --reporter=html
So I can select files by its extension with regex. This would be handier:)

Is there any update on this? It would be great!


A question about extracting word representations

Hi! I have a question about extracting word representations.
If the sentence has two target words, for example, "There are two books. One is mine, the other one is yours.", when using model.extract_representation(['There are two books. The red one is mine, and the other one is yours.', 'one'], layer = 12), which representation in extracted? Is the representation of the first "one"?
Many thanks!

It will default to the first one indeed. But you can circumvent this by providing the character-span of the word you want! for instance, if you want the most recent occurrence of 'one', you could do this by:
import re

sentence = 'There are two books. The red one is mine, and the other one is yours.'

span = list(re.finditer(r'one', sentence))[-1].span()

print(span)

#> (56, 59)

# extract reps:
model.extract_representation(['There are two books. The red one is mine, and the other one is yours.', span], layer = 12)

does this help/make sense?

I asked around a bit and found the following:
In this paper the authors found that the middle layers of bert base are best at predicting word similarity. that is, paradigmatic (wordnetlike) relations between words. https://aclanthology.org/2020.conll-1.17/
And this kind of echoes that the middle layers are better at semantics and the later layers better at syntax, e.g. https://arxiv.org/abs/1905.05950
Unsure if these help, but you could perhaps also determine this empirically on your data! Try with multiple layers if you can!


Implement the basic SDK and backend support for dynamic k8s integration

Describe your changes and why you are making these changes
This PR implements the basics for supporting dynamic k8s integration. This is a big PR and I recommend reviewing in the following order:
Golang backend:

connect_integration.go to see how the AWS cloud integration is registered and how the implicit dynamic k8s integration entry is created.
lib/dynamic/engine.go this contains the low-level invocation using terraform to create and teardown the k8s cluster.
see how these low-level functions are used in aq_engine.go.
start with StartDynamicTeardownJob in aqueduct_server.go to see how the teardown cron job works. This is mostly boilerplate code that makes use of DeleteDynamicEngine in lib/dynamic/engine.go.
The two new routes (handler/engine.go, handler/get_engine_status.go) added for SDK to query the dynamic engine status and issue request to explicitly create or delete the cluster.

Then take a look at the SDK side to see how it issues requests to the two routes above, together with the new DynamicK8sIntegration and AWSIntegration classes added.
Related issue number (if any)
Loom demo (if any)
Checklist before requesting a review

[ ] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[ ] I have performed a self-review of my code.
[ ] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[ ] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[ ] All features on the UI continue to work correctly.
[ ] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@kenxu95 addressed all comments. Ready for another review.


Various core features not functional: e.g. format, intellisense, code navigation

VSCode Version: Code 1.17.2 (b813d12980308015bcd2b3a2f6efa5c810c33ba5, 2017-10-16T13:59:46.104Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.4.0

vscode-babel-coloring
dza
0.0.4

auto-close-tag
for
0.5.2

code-runner
for
0.8.2

vscode-cdnjs
Jak
0.14.3

docthis
joe
0.6.0

code-beautifier
mic
1.7.2

LiveServer
rit
3.0.0

autoimport
ste
1.2.2

open-in-browser
tec
1.1.0

vscode-js-console-utils
wht
0.7.0

JavaScriptSnippets
xab
1.5.0

ReactSnippets
xab
1.4.0

Steps to Reproduce:

React, redux project (but I believe also other projects) inside of .js files:
hover over a function call, intellisense doesn't load, says "Loading.."
hit CTRL and hover over something that previously got styled to look like a link upon CTRL+Mouseover, but now it doesn't get the link-style, and when CTRL+Clicking on it, rather than jumping to the respective file or function, a never previously seen progress bar appears, an animation where a very small blue stripe moves from left to right, right underneath my tabs:

right-click, Format Document doesn't do anything. Same with the corresponding shortcut.

Do note, that I've only been coding seriously for a couple of months and there may be something that I am doing wrong.

Reproduces without extensions: Yes/No

A few questions:

Does this reproduce in VS Code insiders
Does this reproduce if you disable all of your installed extensions?
Does this happen for any js project you open?
Does your project have  a jsconfig.json project definition file?

Maybe related: after upgrading to vscode 1.17, I seem to have lost the ability to "Go to Definition" by Ctrl+Click. Instead, a new cursor is added at the place I do a Ctrl+Click.

Closing as not actionable without more information


godot fails to export on ios

Tested versions
4.2.1, 4.2.2 .NET
System information
macOS Sonoma version 14.3, M1 chip macbook pro 14inch from 2021
Issue description
when exporting on ios I keep getting
MSB3073: The command ""clang" some paths
I tried to fix it like you said in the documentation
xcode-select -p (to check) sudo xcode-select -switch /Applications/Xcode.app (to fix)
I did setup xcode, the SDK is in the right place as I checked by going in that directory and the command above, the path is
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk
I tried to run the app anyway on my ipad but it doesn't work
am I missing something or is it a bug?
Steps to reproduce
N/A
Minimal reproduction project (MRP)
N/A

The actual error for this is:
ld: Assertion failed: (false && "compact unwind compressed function offset doesn't fit in 24 bits"), function operator(), file Layout.cpp, line 6026.
It is related to newer versions of XCode (15.1 and newer) that requires the "-ld64" or "-ld_classic" flags in the linker flags.
Same issue here:
https://github.com/ChainSafe/web3.unity/issues/686
I'm having the same issue so I'm downgrading to XCode 15.0 since we can't edit the commandline used by godot when building the xcode project.

thanks @LeonardoDemartino

Could you please share your full error log @maurosorrentino ?

@LeonardoDemartino I don't have it anymore, it was a long time ago. There is also an issue when exporting to Android which I raised, will go back to Godot hopefully in a few months. I would like to thank you though for your hard work, is very much appreciated!! :)

Without further details this is not likely to be possible to fix, closing and if you provide necessary information this can be reopened


convert youtube links to music.youtube

See if it is possible to use the API to get a music.youtube link instead of youtube videos

closed by https://github.com/sjdonado/idonthavespotify/pull/18


[Question] Key path id != defined property Id

Hello,
I have some problems with the key path to my identifier.
All data converted to json with: JsonConvert.SerializeObject
Store
 {"DbVersion":null,"Name":"People","PrimaryKey":{"Name":"Id","KeyPath":"Id","Unique":false,"Auto":true},"Indexes":[{"Name":"FirstName","KeyPath":"FirstName","Unique":false,"Auto":false},{"Name":"LastName","KeyPath":"LastName","Unique":false,"Auto":false}]}
Model
public long Id { get; set; }
public string FirstName { get; set; }
public string LastName { get; set; }

Will store
{id: 0, firstName: "a", lastName: "b", Id: 6}
And will resolve (getAll) object
{"Id":0,"FirstName":"a","LastName":"b"}
Am I doing something wrong, any clues?
C# Code to set PK
schema.PrimaryKey = new IndexSpec { Name = "Id", KeyPath = "Id", Auto = true };

Oh well...
First char to lower case fixed it... c:


Add ZeroBed operation

One thing I noticed that I don't know how to "fix" is that I had to use my Code Signing Identity as I didn't have access to your. If you apply this change and that has changed then you can simply change it back.
What the new code does it add an Operation button to run "G30". I followed what M3D does and warm the head to 150° first then run G30 then park the head at Y:90 Z:10.  The operation can be Stopped except that once G30 starts it takes two to three minutes to complete but the routine will eventually stop if you wait.

Thank you Bill! Seems to work well. Merged!
I wonder if it might be more logical if the Find Zero thing was in the Calibration window instead of Tools?

Ah! Good point! I was thinking that I should have also added it to the CLI
and was going to do that. I will move it to the calibration window when I
do that. It should be easy as I can reuse the code for the most part.
Bill
On Sat, Aug 1, 2015 at 4:57 PM, Tomas Franzén<EMAIL_ADDRESS>wrote:

Thank you Bill! Seems to work well. Merged!
I wonder if it might be more logical if the Find Zero thing was in the
Calibration window instead of Tools?
—
Reply to this email directly or view it on GitHub
https://github.com/tomasf/microprint/pull/3#issuecomment-126953271.


Prevent display of horizontal scroll bar

REDMINE-17688

Coverage remained the same at 99.208% when pulling 9082cec3ba2017745277bf24fe6eab4a090cbb1b on tf:no-h-scroll into e3a9718f22fec70c429ae484b2c95aeaab696029 on codevise:master.


Greek translation

Hi ! I have translated the English files into Greek language.

That is awesome. Thanks.


Notification icon button sends onUnknownRoute exception

From home screen.
App not crash still no action is performed. Probably something in routing is not set as expected. I do not know what should happen after button click.
From other screens Another exception was thrown: Could not find a generator for route "/task-form" in the _WidgetsAppState.

══╡
EXCEPTION CAUGHT BY GESTURE ╞═══════════════════════════════════════════════════════════════════
I/flutter (17082): The following assertion was thrown while handling a gesture:
I/flutter (17082): Could not find a generator for route "/task-form" in the _WidgetsAppState.
I/flutter (17082): Generators for routes are searched for in the following order:
I/flutter (17082):  1. For the "/" route, the "home" property, if non-null, is used.
I/flutter (17082):  2. Otherwise, the "routes" table is used, if it has an entry for the route.
I/flutter (17082):  3. Otherwise, onGenerateRoute is called. It should return a non-null value for any valid route not
I/flutter (17082):     handled by "home" and "routes".
I/flutter (17082):  4. Finally if all else fails onUnknownRoute is called.
I/flutter (17082): Unfortunately, onUnknownRoute was not set.
I/flutter (17082): When the exception was thrown, this was the stack:
I/flutter (17082): #0      _WidgetsAppState._onUnknownRoute.
package:flutter/…/widgets/app.dart:774
I/flutter (17082): #1      _WidgetsAppState._onUnknownRoute
package:flutter/…/widgets/app.dart:787
I/flutter (17082): #2      NavigatorState._routeNamed
package:flutter/…/widgets/navigator.dart:1440
I/flutter (17082): #3      NavigatorState.pushNamed
package:flutter/…/widgets/navigator.dart:1473
I/flutter (17082): #4      BaseAppBar.actions.
package:thingstodo/…/app_bar/base_app_bar.dart:27
I/flutter (17082): #5      _InkResponseState._handleTap
package:flutter/…/material/ink_well.dart:507

Thank you for submiting the issue, I will check it in the near future

hi  did you fix this bug?


ifvisible.idle callback being called when user is active

Hi,
I think I found a little glitch in your awesome lib.
Tested in Chrome 46.0.2490.86 m

Hit 'http://serkanyersen.github.io/ifvisible.js/demo.html'
Open Chrome's console
Type 'ifvisible.idle(function() { console.log('idle') });' in the console
Let the application sleep by reaching 30s of inactivity
Wake up the application by moving the mouse into it. Move the mouse for 30s, without performing any clicks. After 30s of movement, the application will briefly change state to 'idle' and get back to 'active'. That can be verified by the callback registered in step 3, which will be invoked.

It seems that when ifvisible transitions from 'idle' to 'active', wakeup() is invoked twice. I thought that would pose no problem as JS is mostly singlethreaded, but it seems that my assumptions are wrong.

This issue has been fixed in master now


Setup starting projects for Next.js UI & Clarity smart contract

this initialises lerna & sets up the UI Next.js project & smart contracts NodeJS project. closes #11.

LGTM

A green light from me.

Did we decide @primer/components is going to be our component library of choice? I'm not opinionated on this, but might want to loop in @marbiano @MarianoArg on this decision to see what their preference is :)

Hey @pxydn , any reason we picked Chai and Mocha for tests? I'd suggest using Jest (the official testing suite for React by Facebook) and react testing library for unit testing, and cypress for E2E.
PS: May I suggest renaming ui to frontend, I think it's more accorded for what we are doing here.
Btw, good job with the setup!

hey @MarianoArg!
we're not using Mocha for testing the UI/Next.js project. Mocha & Chai are used for testing the smart contract, not the UI. they are separate projects.
and for the UI name change, i could sort this :)

Awesome, all clear. :shipit:

Looks good  to  me

I have few my understanding queries. I will clarify those from you on Discord.


vrcompositor_wrapper: Disable all Vulkan layers

For Vulkan loader < 1.3.234 there is a blacklist of layers
to disable.
For Vulkan loader >= 1.3.234 there is a whitelist of layers
to enable.

merging.

@Vixea the PR was not ready, it failed rustfmt.


Wrong example url given

The URL referenced in 1.6.1 is:
GET https://api.securitycenter.microsoft.com/api/machines/BaselineComplianceAssessmentByMachine
This does not appear to be correct url for certificate assessment.
Perhaps should be https://api.securitycenter.microsoft.com/api/machines/CertificateAssessmentByMachine based on the given response in 1.6.2?

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

ID: 29ca9c58-1c3f-6da6-ad14-464e98553f3a
Version Independent ID: 29ca9c58-1c3f-6da6-ad14-464e98553f3a
Content: Certificate assessment methods and properties per device
Content Source: microsoft-365/security/defender-endpoint/export-certificate-inventory-assessment.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @siosulli
Microsoft Alias: siosulli

Thanks @imnota for finding this!
@yogkumgit @imnota is correct and this should be updates to:
https://api.securitycenter.microsoft.com/api/machines/CertificateAssessmentByMachine
Thanks,
Sinead

@imnota Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/11024
Once the author approves, the changes will be live.
Thanks
Sri

PR with change has been merged. Closing issue.


az interactive

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az version
Errors:

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az version

Expected Behavior
Environment Summary
Linux-5.4.0-1094-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.13
Installer: RPM

azure-cli 2.41.0

Extensions:
interactive 0.4.5
ai-examples 0.2.5
ml 2.10.0
ssh 1.1.2

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

az interactive
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
The command failed with an unexpected error. Here is the traceback:
No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 663, in execute
raise ex
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 726, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 697, in _run_job
result = cmd_copy(params)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 333, in call
return self.handler(*args, **kwargs)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
return op(**command_args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/interactive/custom.py", line 41, in start_shell
azext_interactive.start_shell(cmd, style=style)
File "/home/dinctuba/.azure/cliextensions/interactive/azext_interactive/init.py", line 10, in start_shell
from .azclishell.app import AzInteractiveShell
File "/home/dinctuba/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 33, in
from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

What does this mean?

Duplicate of https://github.com/Azure/azure-cli/issues/24213


Lacks instructions

"Your repo so good, I love it"
I did not type this
Khuzaib edited it to make it look like I did, lol

Still working on this project, will update it once done.

Ok

Still working on this project, will update it once done.
Bro if you can include a proper instruction or description then I can help you with this


Better error messages from additionalResolvers

Is your feature request related to a problem? Please describe.
When using additionalResolvers in a declarative way, it is easy to may a typo in a targetSource or targetMethod. At the moment, the error messages due to that are not user-friendly.
For example:

if I will specify a wrong targetSource name, the message will be "message": "Cannot read property 'api' of undefined".;
if I'll specify a wrong targetMethod -> "message": "Cannot read property 'type' of undefined".

Describe the solution you'd like:
It would be great to give more user-friendly error messages in that context, i.e.:

for an incorrect targetSource: additionalResolver error: unknown targetSource ${additionalResolver.targetSource};
for an incorrect targetMethod: additionalResolver error: targetMethod ${additionalResolver.targetMethod} does not exist on targetSource ${additionalResolver.targetSource}.

Example of an implementation
In packages/config/src/utils.ts
return {
  [additionalResolver.type]: {
    [additionalResolver.field]: {
      selectionSet: additionalResolver.requiredSelectionSet,
      resolve: async (root: any, args: any, context: any, info: any) => {
        const resolverData = { root, args, context, info };
        const methodArgs: any = {};
        for (const argPath in additionalResolver.args) {
          set(methodArgs, argPath, stringInterpolator.parse(additionalResolver.args[argPath], resolverData));
        }

        // >>>>>>>>>>>>>>>
        // Basic validation of additionalResolver's parameters
        if (!(additionalResolver.targetSource in context))
          throw new Error(`additionalResolver error: unknown targetSource '${additionalResolver.targetSource}'`);
        if (!(additionalResolver.targetMethod in context[additionalResolver.targetSource].api))
          throw new Error(`additionalResolver error: targetMethod ${additionalResolver.targetMethod} does not exist on targetSource ${additionalResolver.targetSource}`);
        // >>>>>>>>>>>>>>>

        const result = await context[additionalResolver.targetSource].api[additionalResolver.targetMethod](
          methodArgs,
          {
            selectedFields: additionalResolver.resultSelectedFields,
            selectionSet: additionalResolver.resultSelectionSet,
            depth: additionalResolver.resultDepth,
          }
        );
        return additionalResolver.returnData ? get(result, additionalResolver.returnData) : result;
      },
    },
  },
  };

This is available in the newer versions! Thanks for the feedback!


stream: replace ECONNRESET with EOF if already closed on AIX

We have been getting a lot of failures on AIX when node-gyp tries to download from https://nodejs.org/download/, an issue has been created with more details on the problem:
https://github.com/nodejs/node-addon-api/issues/522
There has been two attempts to fix similar issues on libuv a few years ago:
https://github.com/libuv/libuv/commit/05a003a3f78d07185b7137601fe8e93561855a8d (which is reverted) and https://github.com/libuv/libuv/commit/c7c8e916b86d2b168e97b04d7b4c8913322c8329 .
This PR uses UV_DISCONNECT introduced in the second commit above, and adds an error check similar to the first commit (only on AIX) to emit EOF when a read returns ECONNRESET after a UV_DISCONNECT event.

/cc @libuv/aix

There has been two attempts to fix similar issues on libuv a few years ago:
05a003a (which is reverted) and c7c8e91 .

FYI (since it took me a while to find this) the revert of https://github.com/libuv/libuv/commit/05a003a3f78d07185b7137601fe8e93561855a8d is https://github.com/libuv/libuv/commit/01544d861b9e11f844d482a80bc557dd9b803c8c.

The revert (01544d8) was because a Node.js test failed (nodejs/node#2310 (comment)) so we should have a libuv-in-node CI run to check if the regression reoccurs.

Apparently I can start these 😄: https://ci.nodejs.org/view/libuv/job/libuv-in-node/106/

libuv CI run: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/
libuv in node CI run: https://ci.nodejs.org/view/libuv/job/libuv-in-node/  (earlier one had failure on arm, but don't think that can be related. this will show if it recreates. If so we should run one without the change to exclude the possibility of it being related)

@mhdawson You link to the overarching jobs, not the runs. :-)
It's https://ci.nodejs.org/view/libuv/job/libuv-in-node/107/ (looks okay) and I started a fresh one for the libuv CI because yours had jenkins failures all over the place: https://ci.nodejs.org/job/libuv-test-commit/1560/

@bnoordhuis oops.  Thanks for restarting/digging up the right links.

In libuv run:

osx1011 failure looks pre-existing
windows failures look pre-existing as well
linux failure looks unrelated.

I am starting to wonder if the intermittent failures we seem on win10 might be related as well: https://ci.nodejs.org/view/x - Abi stable module API/job/node-test-node-addon-api-new/nodes=win10/552/console.  In any case still good to get this landed and possibly investigate that later.

Thanks Milad, landed in ca08b482.

@bnoordhuis not a problem, would you know when this libuv patch will be merged with the latest nodejs nightly builds?

@miladfarca see https://github.com/libuv/libuv/issues/2457. I'll cut the release next week, and it will land in Node's master branch ~2 days after that if all goes smoothly.

@cjihrig thanks!

thanks @cjihrig, will recheck by next week.


AMD and CommonJS Support + Misc Fixes

Added AMD and CommonJS support.
Fixed broken move_relative(). Instead of moving forwards or backwards based on its argument, it was always moving forward by one frame.
Fixed a bug in which passing a number to move_to() greater or less than the amount of animation frames would throw an error.
putFrame() now ensures the current animation frame index is always an integer.

This is what this library needs to stay alive (+ npm package spec)
hope it'll be merged soon


(Nodes & Validators) Some basic edits & additional commands

revised:
simple additions

start node with systemd
Using regex to add peers
additional helpful commands

Please let me know any points that i missed, or that you think should not be.

Hi @Errorist79! Thanks for contributing.
Some workflows of the CI has failed. if you don't mind, could you please:

fix the commits messages to respect the conventional commit formalism (see okp4/wiki/Naming-rules#commit-messages),
check that the markdown files follows the standard enforced by markdownlint. You can invoke yarn lint to verify that the linter passes. And the yarn lint:fix command should fix the majority of the issues.

We can assist you if needed. Thx :relaxed:

Hi @Errorist79! Thanks for contributing.
Some workflows of the CI has failed. if you don't mind, could you please:

fix the commits messages to respect the conventional commit formalism (see okp4/wiki/Naming-rules#commit-messages),
check that the markdown files follows the standard enforced by markdownlint. You can invoke yarn lint to verify that the linter passes. And the yarn lint:fix command should fix the majority of the issues.

We can assist you if needed. Thx ☺
Thanks! sorry for that.
hating conventional commit formalisms 😄

@ccamel
What about this PR?
I think we shouldn't leave PRs open for too long, let me know 😌

Yes, we agree 😌 We shouldn't make the PR open for too long.
For this one, the PR now conflits. And we have to check with @amimart for the content. Some things may have changed since the launch of Nemeton.


Fix HPX-Qt interaction in Qt example.

GUI objects must not be manipulated from threads other than the GUI thread. This rule was violated in the qt example. Now it is fixed.

@andreasbuhr Please fix the remaining inspect errors: https://8914-4455628-gh.circle-artifacts.com/0/tmp/circle-artifacts.ljsPnLm/hpx_inspect_report.html

On 12/05/2017 10:58 PM, Hartmut Kaiser wrote:

@andreasbuhr https://github.com/andreasbuhr Please fix the remaining
inspect errors:
https://8914-4455628-gh.circle-artifacts.com/0/tmp/circle-artifacts.ljsPnLm/hpx_inspect_report.html

When searching for coding guidelines, I found a ".clang-format" inside
of the hpx repository. However, neither clang-format-3.6 nor
clang-format-4.0 is able to parse it. clang-format-3.6 says:
YAML:23:24: error: invalid boolean
AlignAfterOpenBracket: DontAlign
^~~~~~~~~
clang-format-4.0 says:
YAML:26:23: error: unknown key 'AlignEscapedNewlines'
AlignEscapedNewlines: Right
^~~~~
How is clang-format supposed to be used?

@andreasbuhr  yes, the .clang-format file in our repo relies on a recent version of the tool (clang 5 or better)

I updated the code to have no more than 80 characters per line and explicitly use Qt::QueuedConnection to be more readable.


"Installation directory not found" when distro installed with wsl --import in a custom location

I have a Debian WSL distro on my old computer and move it to my new PC with the following process:
:: On the source computer
wsl.exe --export debain Debian-Export.tar

:: On the destination computer
wsl.exe --import debian D:\some\path Debian-Export.tar

Everything is OK but the official Debian launcher app is not installed on destination. So I want to use this launcher app instead.
Launcher's run and config commands are run successfully. But launching the distro with renamed launcher.exe failed with the following error:
C:>debian.exe
Installation directory not found: .
Make sure it exists or reinstall.

I perfomed the some steps but could not confirm the same problem...
on wsldl 19031901,Win10 1903
What versions are you using?
Please note that the excuteble file name and instance name is case sensitive.

I found the problem: the code compares registry value for distro name with executable name as case-sensitive. My distro name is Debian and executable is debian.exe.
Look at this line:
if((subKeySz == UUID_SIZE) && (wcscmp(regDistName,DistributionName)==0))

Change it as below solves the problem:
if((subKeySz == UUID_SIZE) && (_wcsicmp(regDistName,DistributionName)==0))

Oh! I post the comment before reading your comment! Is there any reason for case-sensitivity?

The official launcher hardcodes the name.
wsldl isn't so.

Ok,I'll fix it.

fixed on f74ad77.
Thank you!🙇
If you need the latest test build, you can download it here:
https://ci.appveyor.com/project/yuk7/wsldl


Update AboutUs.md

Codecov Report

Merging #25 (6e63c7a) into master (07698a7) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6e63c7a differs from pull request most recent head 8e19c7c. Consider uploading reports for the commit 8e19c7c to get more accurate results

@@            Coverage Diff            @@
##             master      #25   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 07698a7...8e19c7c. Read the comment docs.


raftstore: increase batch for raftlog-gc-worker

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close https://github.com/tikv/tikv/issues/11404
What is changed and how it works?
Batch more deleted keys together. As we all know ,the deleted key must be much small than the entry which has been put. So 256 is too small for every writebatch in raftlog-gc-worker.
And the gc tasks of most of regions are small. They are often smaller than 100. So I batch the keys of multiple regions and write them together.
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
None

/run-all-tests

/merge

/merge

/merge

Does this PR need to be picked to other release branches?

It was picked to 5.1, but it should also be picked to 5.2 and 5.3.


Fees Contract Page - When edit per project billing tax is not showing correctly by Vinod Sir

Describe the bug
https://www.berrycast.com/conversations/a31f1b61-7deb-5a3d-a016-d3ec12d6c3cc

https://www.berrycast.com/conversations/e7fa7084-abf5-5321-b55f-a55c3aa5ca06


Syntax updates from pgourlain/vscode_erlang

Erlang.plist was copied from textmate/erlang.tmbundle [1] similarly as
it was copied to pgourlain/vscode_erlang [2] earlier. vscdoe_erlang had
several updates to resolve some issues in syntax highlighting before
switched to this repository as a submodule. This commit merges all of
those syntax updates here.
By Daniel Finke (commit 921bb3e [3]):

Comma is not needed in '-define' on the same line as macro name

By Kornel Horvath (commit 921bb3e [3]):

Allow comment between '}' and ').' in record definitions
Allow variables as module or function names in implicit function
expressions
Distinguish function type in type specification and explicit function
expression
Assign file extensions to Erlang mode: escript, yrl, xrl

By Kornel Horvath (commit db9ef8b [4]):

'$' is a valid ASCII number
Escape sequences '^a'..'^z' are valid (and same as '^A'..'^Z')
Escape sequences '\xXY' (where XY are hexadecimal digits) are valid
'utf8', 'utf16' and 'utf32' are valid type specifiers in binary
Binary unit type specifier has a mandatory parameters as
'unit:<pos_integer>' (where <pos_integer> is in range 1..256)
Single underscore (_) can be inserted between digits as a visual
separator (since OTP 23)
Highlight 'true', 'false' and 'undefined' language constants. Well,
technically 'undefined' is not that but traditionally used like that.

[1] https://github.com/textmate/erlang.tmbundle
[2] https://github.com/pgourlain/vscode_erlang
[3] https://github.com/pgourlain/vscode_erlang/commit/921bb3edd4b984de0c41d94fe5269a0160005a0a
[4] https://github.com/pgourlain/vscode_erlang/commit/db9ef8b1ebcf9bce86fba459ca1a4730d6d724d1

Awesome job! @danielfinke can we assume you are ok with porting your contributions to this repository (and therefore back to pgourlain/vscode_erlang` via a submodule)?

@robertoaloi yes definitely!

Thanks!


Fix the mem statistics bug of page cache

for #703
When the Cache memory reaches the upper limit, some items will be eliminated, so the memory release is not necessarily triggered by insert, but may also be in the user's execution thread

run starrocks_clang-format


Refactor browsochrones

Current coverage is 53.19% (diff: 30.76%)

Merging #194 into dev will increase coverage by 1.23%

@@                dev       #194   diff @@
==========================================
  Files           155        155
  Lines          3231       3235     +4
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1679       1721    +42
+ Misses         1552       1514    -38
  Partials          0          0

Powered by Codecov. Last update c71d18c...46a9b60

@mattwigway changed it from e to value


no instructions for API applications

when reading the readme, it looks to me like this could be used for an API apllication as well, altough i cannot find instructions on how to do so.
Now my question before i lose a lot of my time in testing out:

Is this possible?
if yes, how?
Can you add this to the readme and help even more application developers?

@mithom it's pretty easy with api, you just need to check lib/switch_user/provider/* to see how to switch user internally.

tnx, i will give it a glance, and if good I'll see if i can add a wiki page about it (implemented something quickly myself already, but i like using gems that are designed for the purpose)


Update pkg.txt to add timeplus-io/proton

Thanks for the tool. I'd like to add https://github.com/timeplus-io/proton

Thanks for the PR!


[Doc] misunderstanding in test proxy

in https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/test_proxy_migration_guide.md#fetch-environment-variables, it indroduces EnvironmentVariableLoader but there is no sample to show how to use it. And the link contains nothing about it.

This issue causes confusion of customer:

So we hope to update the doc to improve usage experience of customers

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.586399,Docs:0.14190735,Tables:0.049852945'

Thank you for opening an issue, @msyyc! I agree that the documentation here is unfortunately sparse; the Tables preparers that are linked to in that section do use the EnvironmentVariableLoader, but they use its outdated alias (PowerShellPreparer). That's a bit confusing, so I'll leave this issue open to track using a better example.
As for documentation about the EnvironmentVariableLoader itself, rather than generally linking to the TestResources script documentation, I have a separate tracking issue: https://github.com/Azure/azure-sdk-for-python/issues/24934


panic: overflow depth reached

rust-analyzer reliably panics when compiling linkerd2-proxy@main:
:; /home/ver/.vscode-server/data/User/globalStorage/matklad.rust-analyzer/rust-analyzer-linux analysis-stats ./linkerd/service-profiles
Database loaded 396.672681ms
Crates in this dir: 61
Total modules found: 257
Total declarations: 3295
Total functions: 1826
Item Collection: 18.686780996s, 0b allocated 0b resident
thread 'main' panicked at 'overflow depth reached', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/chalk-solve-0.15.0/src/recursive/stack.rs:51:13
stack backtrace:
   0: <unknown>
   1: core::fmt::write
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: std::panicking::rust_panic_with_hook
   6: <unknown>
   7: chalk_solve::recursive::stack::Stack::push
  ..: <unknown>
 100: <unknown>
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I also see intermittent assertion failures:
:; /home/ver/.vscode-server/data/User/globalStorage/matklad.rust-analyzer/rust-analyzer-linux analysis-stats .
Database loaded 391.930197ms
Crates in this dir: 61
Total modules found: 257
Total declarations: 3295
Total functions: 1826
Item Collection: 18.588868086s, 0b allocated 0b resident
197/1826 10% processing: tests::first_datathread 'main' panicked at 'assertion failed: `(left == right)`
  left: `^1`,
 right: `^0`', /rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7/src/libstd/macros.rs:16:9
stack backtrace:
   0: <unknown>
   1: core::fmt::write
  ..: <unknown>
   5: std::panicking::rust_panic_with_hook
   6: rust_begin_unwind
   7: std::panicking::begin_panic_fmt
  ..: <unknown>
  37: ra_hir_ty::traits::trait_solve_query
  ..: <unknown>
  44: ra_hir_ty::autoderef::deref
  ..: <unknown>
  48: ra_hir_ty::method_resolution::iterate_method_candidates_impl
  ..: <unknown>
  64: ra_hir_ty::infer::infer_query
  ..: <unknown>
  70: rust_analyzer::cli::analysis_stats::analysis_stats
  ..: <unknown>
  73: std::rt::lang_start_internal
  74: <unknown>
  75: __libc_start_main
  76: <unknown>
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

:; rustc --version
rustc 1.44.1 (c7087fe00 2020-06-17)

Is there anything I can tune to try to get this working properly?

cc @flodiebold

On master:
% ~/dev/rust-analyzer/target/release/rust-analyzer analysis-stats .
Database loaded 37.783599992s
Crates in this dir: 64
Total modules found: 281
Total declarations: 3641
Total functions: 1957
Item Collection: 17.595072484s, 0b allocated 0b resident
44/1957 2% processing: certify::daemonthread 'main' panicked at 'overflow depth reached', /home/cynecx/.cargo/registry/src/github.com-1ecc6299db9ec823/chalk-recursive-0.17.0/src/stack.rs:51:13
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1076
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1537
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:198
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:217
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:526
  11: std::panicking::begin_panic
  12: chalk_recursive::stack::Stack::push
  13: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  14: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  15: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  16: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  17: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  18: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  19: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  20: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  21: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  22: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  23: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  24: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  25: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  26: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  27: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  28: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  29: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  30: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  31: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  32: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  33: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  34: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  35: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  36: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  37: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  38: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  39: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  40: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  41: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  42: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  43: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  44: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  45: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  46: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  47: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  48: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  49: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  50: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  51: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  52: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  53: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  54: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  55: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  56: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  57: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  58: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  59: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  60: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  61: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  62: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  63: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  64: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  65: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  66: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  67: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  68: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  69: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  70: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  71: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  72: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  73: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  74: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  75: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  76: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  77: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  78: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  79: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  80: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  81: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  82: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  83: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  84: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  85: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  86: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  87: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  88: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  89: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  90: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  91: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  92: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  93: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  94: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  95: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  96: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
  97: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  98: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  99: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
 100: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
 101: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
 102: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
 103: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
 104: chalk_recursive::recursive::Solver<I>::solve_new_subgoal
 105: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

For what it's worth, this project now encounters a not implemented exception instead:
:; RUST_BACKTRACE=full ~/.vscode-server/data/User/globalStorage/matklad.rust-analyzer/rust-analyzer-linux analysis-stats .
Database loaded 362.54ms, 439mi
Crates in this dir: 56
Total modules found: 287
Total declarations: 3500
Total functions: 1922
Item Collection: 17.93s, 131056mi
37/1922 1% processing: requests::layer::poll_readythread 'main' panicked at 'not implemented', /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/macros.rs:13:23
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1076
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1537
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:198
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:217
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:526
  11: std::panicking::begin_panic
  12: chalk_solve::clauses::push_auto_trait_impls
  13: chalk_solve::clauses::builder::ClauseBuilder<I>::push_binders
  14: chalk_solve::clauses::program_clauses_that_could_match
  15: chalk_solve::clauses::program_clauses_for_goal
  16: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  17: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  18: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  19: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  20: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  21: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  22: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  23: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  24: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  25: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  26: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  27: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  28: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  29: <chalk_recursive::recursive::RecursiveSolver<I> as chalk_solve::solve::Solver<I>>::solve_limited
  30: hir_ty::traits::trait_solve_query
  31: salsa::runtime::Runtime::execute_query_implementation
  32: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  33: salsa::derived::slot::Slot<Q,MP>::read
  34: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  35: salsa::QueryTable<Q>::get
  36: <DB as hir_ty::db::HirDatabase>::trait_solve::__shim
  37: <DB as hir_ty::db::HirDatabase>::trait_solve
  38: hir_ty::infer::InferenceContext::resolve_ty_as_possible
  39: hir_ty::infer::path::<impl hir_ty::infer::InferenceContext>::infer_path
  40: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  41: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  42: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr
  43: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_method_call
  44: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  45: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr
  46: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_method_call
  47: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  48: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_coerce
  49: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_inner
  50: hir_ty::infer::expr::<impl hir_ty::infer::InferenceContext>::infer_expr_coerce
  51: hir_ty::infer::infer_query
  52: salsa::runtime::Runtime::execute_query_implementation
  53: salsa::derived::slot::Slot<Q,MP>::read_upgrade
  54: salsa::derived::slot::Slot<Q,MP>::read
  55: <salsa::derived::DerivedStorage<Q,MP> as salsa::plumbing::QueryStorageOps<Q>>::try_fetch
  56: <DB as hir_ty::db::HirDatabase>::infer_query::__shim
  57: hir_ty::db::infer_wait
  58: rust_analyzer::cli::analysis_stats::AnalysisStatsCmd::run
  59: rust_analyzer::main
  60: std::rt::lang_start::{{closure}}
  61: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
  62: std::panicking::try::do_call
             at src/libstd/panicking.rs:348
  63: std::panicking::try
             at src/libstd/panicking.rs:325
  64: std::panic::catch_unwind
             at src/libstd/panic.rs:394
  65: std::rt::lang_start_internal
             at src/libstd/rt.rs:51
  66: main
  67: __libc_start_main
  68: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Which version are you running? This should have been fixed by https://github.com/rust-analyzer/rust-analyzer/pull/6161.

@lnicola ah hah. i was on rust-analyzer e5f252a. after updating i'm back to an overflow depth reached error:
252/1929 13% processing: do_sendthread 'main' panicked at 'overflow depth reached', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/chalk-recursive-0.33.0/src/stack.rs:51:13
stack backtrace:
   0: std::panicking::begin_panic
   1: chalk_recursive::stack::Stack::push
   2: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
   3: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
   4: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
   5: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
   6: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
   7: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
   8: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
   9: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  10: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  11: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  12: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  13: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  14: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  15: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  16: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  17: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  18: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  19: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  20: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  21: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  22: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  23: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  24: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  25: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  26: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  27: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  28: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  29: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  30: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  31: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  32: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  33: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  34: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  35: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  36: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  37: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  38: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  39: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  40: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  41: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  42: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  43: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  44: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  45: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  46: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  47: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  48: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  49: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  50: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  51: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  52: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  53: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  54: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  55: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  56: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  57: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  58: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  59: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  60: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  61: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  62: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  63: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  64: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  65: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  66: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  67: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  68: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  69: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  70: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  71: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  72: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  73: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  74: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  75: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  76: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  77: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  78: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  79: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  80: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  81: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  82: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  83: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  84: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  85: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  86: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  87: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  88: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  89: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
  90: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::prove
  91: chalk_recursive::fulfill::Fulfill<I,Solver,Infer>::solve
  92: <chalk_recursive::recursive::Solver<I> as chalk_recursive::solve::SolveDatabase<I>>::solve_goal
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I looked into this a bit. It seems Chalk tries to solve usize: Sized via environment, because it knows Into implies Sized and that GrpcService::Error implements Into, and then later it gets into trying to prove Sync for further and further nested types involving GrpcService::Error. I'm not sure why the type size limit doesn't happen before the overflow limit; it might just be that the types grow too slowly. I think the syntactic equality change in Chalk should probably prevent this from happening because Chalk should notice faster that this path won't work.

I no longer see this error on recent versions of rust-analyzer! 🎉 Thanks for fixing ;)


Location data not being loaded properly

I think that the recent update to the Kijiji App came with a change to mapping/location services or at least the way the data are being read into the app.  When I post an ad through Kijiji-Manager, my location is now incorrect (it has been working great for over a year now).  I then tried posting through the regular Kijiji app on my browser and my location is correct.
I've tried changing my postal code in Kijiji-Manager with no luck.  I've also tried adding more info to the open text location field in Kijiji-Manager, but that didn't work either.
Any thoughts?

Location coordinates for an ad are derived from the postal code provided, and no other input field.
The pgeocode package is supposed to do this lookup so if there is a problem I would suspect it relating to that.

Personally I am able to still post new ads using my own postal code and it is able to get the correct location coordinates for it to appear on the ad itself.


python311Packages.dirty-equals: 0.5.0 -> 0.6.0

Diff: https://github.com/samuelcolvin/dirty-equals/compare/refs/tags/v0.5.0...v0.6.0
Changelog: https://github.com/samuelcolvin/dirty-equals/releases/tag/v0.6.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

19 packages built:

baserow
baserow.dist
dmarc-metrics-exporter
dmarc-metrics-exporter.dist
paperless-ngx
python310Packages.dirty-equals
python310Packages.dirty-equals.dist
python310Packages.pytest-examples
python310Packages.pytest-examples.dist
python310Packages.watchfiles
python310Packages.watchfiles.dist
python311Packages.dirty-equals
python311Packages.dirty-equals.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.watchfiles
python311Packages.watchfiles.dist
strictdoc
strictdoc.dist


Filter: Create filter context and extract filters from tables (so graph and table could be connected by one filter)

Done.


Fix symlink to absolute dir

This is supposed to be fix the symlink to absolute directory

Thanks for finding and resolving this issue!


Add support for RapidWright

The target is to be able to measure the performance of various routing algorithms done with the help of RapidWright.
However, first we need to integrate RW with the fpga-tool-perf.

@clavin-xlnx could you please update the description and add more details and describe which algorithms you would like to add?

RapidWright has a router called RWRoute.  It only supports UltraScale+ devices and can be run in both timing-driven and non-timing-driven modes and depends on the design being fully placed (and intra-site nets are routed).  From what I remember, nextpnr-interchange does not yet have the ability to output a placed (but not routed) design yet.  So, to run RWRoute, the design would need to be unrouted first.  For example, if a from nextpnr-interchange was placed and routed and saved as an Interchange fileset, RWRoute could be run with the following RapidWright code:
        EDIFNetlist netlist = LogNetlistReader.readLogNetlist(logNetlistFileName);
        Design design = PhysNetlistReader.readPhysNetlist(physNetlistFileName, netlist);

        // TODO - Remove once nextpnr can export placed-only design
        design.unrouteDesign();

        RWRoute.routeDesignFullNonTimingDriven(design);
        // Timing-driven option: RWRoute.routeDesignFullTimingDriven(design);


Sentinel aware

Hi,
Are there plans to make node_redis sentinel aware? I'm thinking about being able to use a list of sentinels at startup, then discover and connect to the masters, and subscribing to sentinels message to take into account masters changes. If not, would be happy to start working on it!
Tanguy

Sorry for the me-too... What's the progress on this? It looks like there's no active development on this module right now.

Native sentinel support in node_redis  +1

@blainsmith wut?

@blainsmith Could you let us know what changed? I'd like to know if this a won't-fix or something, so some explanation would be appreciated.

Oops. I forgot to paste in my canned response to this. I was going through and cleaning up really old issues. Sorry about that. I will reopen this and tag it accordingly!

@blainsmith Ah, I see. Thanks for the update. :)

Are there any news on Sentinel? Do you know of any drop-in replacements that do support Sentinel?

Any news? :(

Is there any chances that the most popular Redis client, will get (probably) the most wanted feature (specially for clouds) in any future, after 8 years? 🤔
Or can anyone tell what is the issue with it, to get it implemented? 🧐

I switched to ioredis .. it is a kind of drop in replacement

https://github.com/luin/ioredis/wiki/Migrating-from-node_redis

Guess we will switch to ioredis, this effort appears to have died.

So... after more than 10 years, I'm starting to work on that now... :tada: NEVER say never :P

So... after more than 10 years, I'm starting to work on that now... 🎉 better late than never 😆

Great to hear that, it would be so nice if we have an optimistic eta for that @leibale ?

@nguyenpc I'm not too sure how much time it's gonna take, but the current roadmap is:
V5 with support for RESP3 + some more features
Sentinel
V5 should be ready "soon" (a month or so), then I'll start working on Sentinel :)

Is it now implemented?

Its in the v5 branch waiting for some tests and last minute changes, then we will release a "next"/beta version with it

Hope this comes soon to the main. :)

How this redis sentinel support will work on kubernetes where the redis pod ips may change in time? In the current helm chart it looks like I need to add the IP addresses of the redis sentinel nodes. or I can configure a service targeting the redis pods?

Hi @leibale! I'd to know if there are any plans to release version V5 soon. I've noticed that the working branch is quite active, but I was wondering if there's a target date for releasing a stable or a beta version that includes the Sentinel package?  :)

Hi @leibale! I'd to know if there are any plans to release version V5 soon. I've noticed that the working branch is quite active, but I was wondering if there's a target date for releasing a stable or a beta version that includes the Sentinel package? :)

Hi again, my team have been closely following the development of the V5 version and is very interested in using the new features you are implementing.
Additionally, our team is willing to work with you to speed up the development process so we can use the new version as soon as possible. If we can help, please let us know. We are open to performing tests, providing feedback, or contributing in any other way you find useful.
Thank you in advance

@gianDiazM ATM we are working on:

Client-side caching
Finishing sentinel
Aliging the commands
If you guys want to help with one of those, do performance tests, or just play around with the client, that would be very helpful.
Do you need sentinel specifically to try it out? Can you try it directly from git or do you need an "npm version"?

@gianDiazM first, sorry for the huge delay, I've complement missed your message from 2 weeks ago.. ATM we are working on:

Client-side caching
Finishing sentinel
Aliging the commands

If you guys want to help with one of those, do performance tests, or just play around with the client, that would be very helpful. Do you need sentinel specifically to try it out? Can you try it directly from git or do you need an "npm version"?

Hi @leibale no worries and thank you for getting back to me. We will try to address the points you mentioned. A Redis npm version that includes the client/sentinel package to integrate into our development would be great.
Thanks =)

@leibale we are in a very similar situation as @gianDiazM
what exactly means "finishing" sentinel?

hey, is there any workaround? How can I use my sentinel configuration? redis-sentinel is a good way?

Hi, we also need to use sentinel mode for Redis. Can you give us some information when the version will be release ?