universal-cookie ESM support

universal-cookie is the dependency of @nuxtjs/apollo which uses the latest version 4.0.4.
Due to a change to ESM in Nuxt 3, universal-cookie now has to be transpiled, see: https://github.com/nuxt-community/apollo-module/issues/435
Going forward it would be great if universal-cookie would be ESM-compatible.

The latest version should be ESM compatible. If you're still having issues, feel free to re-open this.


[AI] [Inference] Add image file sample and test for chat completions

Packages impacted by this PR
@azure-rest/ai-inference
Issues associated with this PR
Describe the problem that is addressed by this PR
Adds image file sample and test for chat completions
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


basecli AppTx - Signer should be added when reading flags

Plugins sometimes require the signer address to function properly. This address should be returned in the TxInput of AppTx when returned from AppTx Helper command ReadAppTxFlags(). Right now signers are added later before broadcast in the BroadcastAppTx as a part of the AddSigner function. This can simply removed after its been added to ReadAppTxFlags()
https://github.com/tendermint/basecoin/blob/develop/cmd/basecli/commands/cmds.go#L148

Please show me the code in trackomatron where this is causing a problem.
The signer comes from checking the key manager, tried to handle that all in one step, but I guess I could split it up in two parts if it's better.  Just want to see a concrete problem with the current structure.

https://github.com/tendermint/trackomatron/blob/f257a5d3f146c5c8d6097a129f19bc5a402a6a9d/cmd/trackocli/tx/profile.go#L67-L102
        gas, fee, txInput, err := bcmd.ReadAppTxFlags()
	if err != nil {
		return err
	}

	// Retrieve the app-specific flags/args
	var name string
	if TBTx == invoicer.TBTxProfileOpen {
		if len(args) != 1 {
			return trcmn.ErrCmdReqArg("name")
		}
		name = args[0]
	}

	//TODO get the address here from txInput once changed in basecoin
	data := profileTx(TBTx, txcmd.GetSigner().Address(), name)

	// Create AppTx and broadcast
	tx := &btypes.AppTx{
		Gas:   gas,
		Fee:   fee,
		Name:  invoicer.Name,
		Input: txInput,
		Data:  data,
	}
	res, err := bcmd.BroadcastAppTx(tx)
	if err != nil {
		return err
	}

Within any trackomatron profile is linked to a basecoin pubkey address, aka this information needs to be sent in with the transaction in order to be interpreted used on the server-side processing. Right now, as shown in the above code, we generate the txInput before we generate the custom plugin tx bytes (which need the address). Within the txInput there is a field for the address and the pubkey however, they are left empty at generation and only filled in later in the AddSigner function which is a part of BroadcastAppTx which is called here... but this is after generating the txInput... I have a workaround right now which is to just the signer directly as I've done here, it's just unnecessary we should only need to call the function once.. not to mention that it's confusing that those fields exist but they're just not filled in... Makes sense?

Yeah, I figured all this info could be filled in at the last step.
Now I realize, we need to actually build some opaque []byte for the app, which will need this info.  So this doesn't work.
Sure, pull it out.
My thought was a bit that light-client needs to support unsigned tx to work with dummy / merkleeyes / other example apps.  So I didn't make the signing name fully required from the get-go. But clearly in basecoin, it is always required. I just didn't change my thinking.
Yes, please do the Signer / sig stuff early on here, as it is always needed.

Closed with #140


Doesn't respect folded code

Screenshot should be self explanatory, but basically it looks like swackets isn't seeing the closing bracket when it's folded and changes the color of the next opening bracket.

Same goes with soft wrap.


Performance issue due to tooltips

Hi there 👋
Thanks for this great player!
Current Behavior:
On a website I am working on, I have pages with around 10 vidstack instances and I noticed a drop of frames while scrolling. I'm using 1.12.5
After recording the performance tab, I could see that functions are triggered on scroll event. Functions coming from floating-ui, a dependency of vidstack. More specifically, the autoUpdate function in use here.
Floating UI's docs recommends to call the cleanup function returned by autoUpdate whenever the handled element is removed (understand "is not visible"?) to avoid severe performance degradation.
In vidstack, it seems like this cleanup function is called by the onDispose hook. I'm not familiar with maverick.js but my guess is this is only called when the tooltip is removed from the dom and this would explain the performance drop on scroll.

Expected Behavior:
Could it be possible to change how things are handled?
To sum up:

call autoUpdate on show
call cleanup on hide

If so, both tooltip-content and menu-item components are concerned by this matter.
Steps To Reproduce:

Instantiate a vidstack player
Record performance tab
Scroll
See that floating-ui functions (detectOverflow, getClippingRect, etc.) are called even when tooltips are not visible

Thank you so much for reading me. :)

I can't believe I missed that, thank you so much for catching it and the detailed report! Fixed and the release will be rolling out momentarily.

Just checked. It's so much better now!
Thank you so much for fixing the issue this fast! 🚀


Add information about the resources defined by every policy-group (QoS)

Is your feature request related to a problem? Please describe.
We would like to have the QoS policy-group information in the database that information we will give us the possibility of alerting when the file are reaching the limit of IOPS assigned for that workload. Additionally, it is possible to create a percentage of the use of every workload?
Describe the solution you'd like
The query from ONTAP CLI for get the information requested is:
qos policy-group show

For the "Throughput" would be desirable to have split this field in two, one for mininum IOPS assigned (it is the first number) and the another for the maximum IOPS assigned (it is the second number after the hyphen)

hi @faguayot yes, we'll add that and yes, the xput and iops will be separated into their own fields. Can you add more details on what you mean by

it is possible to create a percentage of the use of every workload?

What are the numerator and denominator of this percentage?
This object requires a bit more work than some of the others because of how qos polices are split between adaptive and fixed. Harvest will handle both, but we may deliver the changes in stages. If we do deliver in stages - does fixed, adaptive, or both best match you current needs?
Here's our current thinking. On the ZAPI side, there are two different ZAPIs: qos-policy-group-get-iter and qos-adaptive-policy-group-get-iter. REST combines both of those together into qos/policies. Adaptive and fixed SLOs are mutually exclusive on the ONTAP side.
Harvest will export two metrics: qosp_fixed and qosp_adaptive. There will be two ZAPI templates with a plugin to format the xput and iops, and there will be one REST template that publishes identical metrics.

Hello @cgrinds,
I'm going to use an example to explain you how we would like to have the field "Throughput"  splitted in two fields. Take a look of my previous image and see the first qos policy-group named openstack-059... if you check the field "Throughput" will be the following value: 0-9600IOPS and my question was if it is possible to split that value into two for example like this: mininumIOPS = 0 and maxixumIOPS = 9600.  (don't use my horribles names for that purpose :))
Related to my other question about the calculation of percentage QOS used, the way to obtain the % is using the qos_ops metric (get when we activate the workload objects in harvest) and the qos defined in the policy applied to that workload which we will get with: qos policy-group show.
Percentage calculation =  currentiops_byworkload x 100 / maxiops_byworkload
If it is possible to have the percentage of workload use, in which metric do you think it will better to have? Because in my mind, it will be easier to have for future use in the same metric that qos_ops.
For us I guess that both qos are useful but maybe in a first step we were thinking on the qosp_fixed.
Let me know if I explained better or if you need any other clarification by my side. Thanks so much for you continue help and your open mind for the new integrations.

Thanks! That helps.
In terms of splitting, I don't think that's necessary since ZAPI and REST return a min-throughput and a max-throughput. My guess is the CLI output chose a different format to communicate the same thing. Just checked, and yeah, that seems to be the case if you ask for min and max individually.
ocum-infinity::> qos policy-group show -fields "policy-group,class,min-throughput,max-throughput,throughput-policy"
policy-group           class        max-throughput min-throughput throughput-policy
---------------------- ------------ -------------- -------------- -------------------
NSLM_LUN_1579633498796 user-defined 61388IOPS      14400IOPS      14400IOPS-61388IOPS
NSLM_LUN_1579633499146 user-defined 57062IOPS      13945IOPS      13945IOPS-57062IOPS
NSLM_VOL_1571973651802 user-defined 601IOPS        0              0-601IOPS

Either way, we'll make it work and align ZAPI and REST. The plan is to use the same "shape" as REST (pasted below).
The ZAPI collector will use the same shape and names as the REST collector, that way Harvest will export the exact same metric.
Appreciate the details on % calculation, that makes sense, and yeah I like qos_ops too. We'll need to take a look. Since this calculation requires several ZAPI calls to calculate, we'll probably need to build a plugin that does that.
# Adaptive Example
{
      "svm": {
        "name": "vs5_nfs_cifs"
      },
      "name": "NSLM_vs5_nfs_cifs_Value_17_0",
      "adaptive": {
        "expected_iops": 128,
        "peak_iops": 512,
        "absolute_min_iops": 59,
        "block_size": "any",
        "expected_iops_allocation": "allocated_space",
        "peak_iops_allocation": "used_space"
      },
      "object_count": 6,
      "policy_class": "user_defined",
      "scope": "svm",
}

# Fixed Example
{
      "svm": {
        "name": "vs3_cifs"
      },
      "name": "pg_nfs_17",
      "fixed": {
        "max_throughput_iops": 56808,
        "min_throughput_iops": 15126,
      },
      "object_count": 0,
      "policy_class": "user_defined",
      "scope": "svm",
}

Hello @cgrinds,
I would like to add some example that we have in our storage array, if you see the first line appear the throughput and the IOPS
qos policy-group show -fields min-throughput,max-throughput,throughput-policy,pgid,num-workloads,policy-group,class
policy-group  class        pgid max-throughput     min-throughput num-workloads throughput-policy
------------- ------------ ---- ------------------ -------------- ------------- --------------------
extreme-fixed user-defined 557  50000IOPS,1.53GB/s 0              0             0-50000IOPS,1.53GB/s
openstack-059790fd-36e5-4648-91b8-fbe69d3f30ec user-defined 9178 9600IOPS 0 1   0-9600IOPS
openstack-07e3d197-d3be-4f20-aaef-03f7f12b92d6 user-defined 593 2880IOPS 0 0    0-2880IOPS
openstack-0a99711a-ea01-4059-8951-060b4e86f1a8 user-defined 9112 960IOPS 0 1    0-960IOPS
openstack-0b2d71c0-70fa-4358-a7ad-5a4366fd5d2c user-defined 10886 6144IOPS 0 1  0-6144IOPS
openstack-0b6d365f-dea0-4399-8a7e-7e8da4bbbaa5 user-defined 13002 1200IOPS 0 1  0-1200IOPS

We don't use that but it is possible to have a qos-policy taking into account both parameters. Only as a informational, maybe it is helpful for you when you can work in this.
Thank you Chris.

hi @faguayot yes we'll handle both forms and align with REST

Hello @cgrinds,
How this issue is going?
I want to ask you if there is the adaptative qos policies enabled on the last release 23.02 or how can we enable to have values from this metric?

hi @faguayot these changes did not make the 23.02 release, but will be included in 23.05. If you're able to try a nightly, we can get you something sooner. Would that work?

Hello @cgrinds,
Yes, I could try with the nightly deployment in a machine dedicate for the previous environment (development). Let me know when you have the implementation available and I will try it.
Thanks for your quick response.

@faguayot changes for fixed QoS policy groups are delivered in #1831 - this includes the parsing and publishing of fixed as discussed above.
These changes will be included in nightly after 2023-03-21 1am EDT. When you get a chance, please take a look. This does not yet include any percentage calculation.

Hello @cgrinds
I am testing the nightly release, it is appear a new metric: qos_policy_fixed_labels and on the other hand existing metrics:  qos_ops, qos_total_data and qos_detail_volume_resource_latency are collecting new information (policy-group, worload,wid,etc).
Fixed QoS

Adaptative QoS

This is the new metric information for this example:

It looks great in general (thanks @cgrinds, @rahulguptajss and the rest of the team), but I am missing information from some clusters which have enabled the adaptative QoS but I can't find the information in qos_policy_fixed_labels for those clusters. The differences between the other cluster which are working and those are the ONTAP version 9.7 vs 9.10.1 (in the cluster which are working). Do I have to make any additional modification?

I have another doubt related with the REST and ZAPI, I would prefer to use REST when it is possible instead of ZAPI on every cluster. Do I have to put the collectors in my harvest.yml right?
cluster-1:
    datacenter: dc-1
    addr: <IP_ADDRESS>
    collectors:
        - Zapi
        - Rest

Ohhh you are right, sorry I didn't realize about the fixed that you mentioned. My fault becauseI was happy and excited with the news that I didn't read correctly.
Thanks for clarify me, I read that in the documentation but I wanted to be sure abour the "Collectors" section since I didn't have that information in my previous harvest.yml file.
Related with the adaptative-qos, we aren't collecting yet the limits for every policy but with the new  nightliy version we are gathering the adaptative-policies or these were working from previous version? Because I am not sure now what were the changes here? There was any additional implementation to the new metric "qos_policy_fixed_labels"?
Thank you for your help.

Yes chris, that is what I understood in the last message but I wanted to be sure. Thanks.
Please, when you have prepared the same metrics por the adaptative QoS advice me and I will deploy again the version with the changes for trying.

Hello @cgrinds ,
These information for us it's very valuable, but now I am trying to display on a Grafana dashboard.

I don't know how to join the information of qos_ops with the information of the qos_policy_adaptive_labels or qos_policy_fixed_labels in a table and a graph. My intention is to look for the top workloads and draw the behaviour for those workloads and with the limit. With this graph I can check if any workload  exceeds the load allowed by the limit (qos). Additionally I would like to have in a table the max values for the top workloads and the maximum value allow for that workload. This information is neccesary to check if we are falling short with the QoS allocation or the opposite. With this feature we can adjust a new workload in accurate way.
Thanks.

hi @faguayot @rahulguptajss took a look at this join yesterday and came up with this. Can you give this a try?
qos_ops * on(svm,cluster,policy_group) group_left(max_throughput_iops,max_throughput_mbps,min_throughput_iops,min_throughput_mbps) label_replace(qos_policy_fixed_labels, "policy_group", "$1", "name", "(.*)")

Another thing to try since you mentioned top workloads. We recently added (March 22) a Workload dashboard that includes top workloads.

Hello @cgrinds,
Thanks for your help, I was struggling with the query because I've never used union of two different metric which additionally have to replace a label by the policy to fint the match between both metrics. I was really close of the success, so with your help I could draw a table with all the information. I need to check in more detail, because probably I am not sure which information will be more useful to use for filter and to show (peak, avg,etc).
Also, I would like to have the topk for some file or lun with the limit by every file or lun in a graph.
Related to the workload: Yes, I have the Delay Center dashboard that I think it is the same that Workload.

hi @faguayot were you able to make progress on the join or any other thoughts on the functionality provided so far? I think everything is included except for the percentage calculation. Do you see any other gaps?

Hi @cgrinds
I didn't do anything else because I didn't have time to review this. I would like to check when I can, how can I get a query which show the peak information for a workload and its maximum performance assign in the policy for the specific workload.
Thanks.

Hi @faguayot
We do have all the required labels in qos_ops and qos_policy_adaptive_labels metric for QoS calculations which you are interested for. And all the arithmetic operations on labels are working in Grafana.
Just for example of arithmetic operations in Grafana by applying transformations, I have used expected_iops and peak_iops labels for calculation. And yes, we can change the formula as per the use-case and need.
qos_ops{datacenter=~"$Datacenter", cluster=~"$Cluster", svm=~"$SVM"} * on(cluster,svm,policy_group) group_left(peak_iops,expected_iops) label_replace(qos_policy_adaptive_labels{datacenter=~"$Datacenter", cluster=~"$Cluster", svm=~"$SVM"}, "policy_group", "$1", "name", "(.*)")

Screenshot1: Query with result

Screenshot2: Transformations detail

If you would like to check this example changes in your system, then Here is the panel json changes for that.

Hello @rahulguptajss,
Sorry I was out of office. I was checking with my colleague and I think your proposal is good for achieve the information that we required to draw in graphs.
Let me know when you can implemented to have the chance to try and show you the information.
Thanks so much for your comprenhension.
Best regards!

I am trying to test the new metrics in qos, here an example of the qos_ops for different workloads (files), in the graph you can see a workload with exceeds the maximum limit for a while.
EXAMPLE:

This type of behaviour are that we want to find with these parameters. We will continue testing and creating new dashboard with relevant information for us, but we need time to think how we can watch the information.

Hello @rahulguptajss
Sorry, I didn't have time to work in this recently so I couldn't design new dashboards with value for us to share. Apologize for that.
Today, I was checking and it came a doubt to me, it is possible to have the file name in the new metrics created like we have the policy_group (called name)? This request is because in our use case sometimes we managed migrations of the files (cinder volumes) that trigger a change and the matching between the policy_group and the file stop to exist.
a so the policy_group and the file name don't match.
Let me show you an example:

If you review both files (the lines in the screenshot), in one case the name for the file/volume is the same that the policy openstack-... and in the other no. So if we don't have the equivalence between file and policy_group in the same metric, we can't use it. In our plafform we require to use the file instead the policy_group to filter or find the behavior for the resource.
Excuse me if I extended
Thanks.

@rahulguptajss The problem is we need to filter the queries using the file information and that information doesn't exist on the qos_policy_fixed_max_throughput_iops.

If you check the name for the cinder-volume (is an alias for the file) and the policy, it should be the same ID in all the cases but it isn't like that in many because different reasons, so it would be helpful if you add the file information in the new metrics like qos_policy_fixed_max_throughput_iops. Sorry because maybe I am not explaining very well.

Hello @rahulguptajss
I understood what you said, sorry I was thinking in our current scenary which the relationship of a qos_policy is one per resource/workload (1:1) and I didn't realize that wasn't the norm for every use.
Now I achieved what I was looking for (thanks for your help)

Table for fixed and adaptative (I need some help for improve the gauge, if you see the dashboard doesn't fill the area correspondant with the percent used)

Example of fixed qos for a file with infinitive qos, another with a specific qos and the last a file which the name for the file and policy doesn't match.

Example of adaptative qos

Take a look and let me know if this information could be helpful for you since it is something customized for our env and use. If you want the dashboard, how can I share with you?

Great. I have sent the email with the dashboard.

We'll open a separate issue for incorporating the dashboard @faguayot contributed. This issue can be closed

Hello    @rahulguptajss
As you can appreciate in this image, we get the result that we were looking for. We have found and instance (VM) which is consuming the whole provisioned policy of IOPS (QoS).

Furthermore in this graph we can see during how long time was occurring that event since the percentage of image is an average right?

Additionally we were taking a look at the other graphs and we have a doubt what it is "Service Latency by resource"? What kind of metric is that and what does it measure? I don't know how can I find the measure in the harvest to get information about that.
Thanks so much.


[20.09] steam/fhsenv: Add LD_LIBRARY_PATH (and hence OpenGL driver library path) to output of --print-steam-runtime-library-paths

Motivation for this change
Backport of https://github.com/NixOS/nixpkgs/pull/106843.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Tested on stable with DoD: Source and L4D2

Please cherry pick from master using git cherry-pick -x so the commit message contains the githash of the original commit.

Please cherry pick from master using git cherry-pick -x so the commit message contains the reference to the original commit (see CONTRIBUTING.md where this is described).

Fixed, thanks.


More Details Please

I'd love to get some more details - if this page is to be a true deep dive. Here are some deep dive things that could be useful:
With respect to Heuristics - How is memory pressure measured and over what duration? How are memory pressure and CPU used to determine a host's load? And how are the loads on the VMs calculated?
The article mentions that memory is a key issue - can the page add a note as to what best practice is wrt memory?
Regarding aggressiveness - what are the formulae used to determine when to move a VM? How aggressive is high and how passive is low?
Does this feature need VM Resource Metering? If not. how is VM load calculated with respect to overall load on the node?
In terms of moving a VM. how does the algorithm determine which VM is to be moved?  Is it possible to specify which VMs to move?
If this page is to be just about the configuration of VM load balancing, can we re-title it to Configuring VM Load Balancing in Hyper-V?  In which case, the page is good as it is! :-)

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

ID: 31050d7b-9898-505b-4394-71ec40c7968c
Version Independent ID: 090c4d01-c609-d937-bbe9-f1aab4e2240d
Content: Virtual Machine Load Balancing deep-dive
Content Source: WindowsServerDocs/failover-clustering/vm-load-balancing-deep-dive.md
Product: windows-server
Technology: storage-failover-clustering
GitHub Login: @bhattacharyaz
Microsoft Alias: subhatt

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Replaces LazyCythonizingList and our janky pre_setup function that
shells out to pip with a custom build_ext class that lazily accesses
numpy and Cython.  This means that we no longer depend on Cython and
numpy until after those modules have been installed by setuptools
because they're specified as part of setup_requires.
This currently still fails because bcolz imports numpy at module scope
in their setup.py.

A version of this was merged already.


mgradm: Implement Start Stop and Restart command in k8s

mgradm: Implement Start Stop and Restart command in k8s

this should be rebase once https://github.com/uyuni-project/uyuni-tools/pull/123 it's merged


Internal Server Error.

Describe the bug
Traceback (most recent call last):
  File "/var/task/app.py", line 150, in get_episode
    data = TechZApi.gogo_episode(f"{anime}-episode-{episode}")
  File "/var/task/utils/techzapi.py", line 65, in gogo_episode
    data = requests.get(
  File "/var/task/requests/models.py", line 975, in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To Reproduce
Steps to reproduce the behavior:
Trying to watch Dragon Ball Super: Super Hero
Expected behavior
Watch the anime
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [Android 11]
Browser [Chrome]
Version [ 114.0.5735.60]

Smartphone (please complete the following information):

Device: [Vivo Y12s]
OS: [Android 11]
Browser [Chrome]
Version [ 114.0.5735.60]

Additional context
Add any other context about the problem here.

send url of the episode

send url of the episode

https://animedex.ordinaryender.my.eu.org/anime/super-dragon-ball-heroes-ultra-god-mission


plugins/none-ls: add typos

Adds typos to none-ls

Just found out there is a real lsp, gonna have a crack at adding that too, but I suppose it doesn't hurt to have both?
https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#typos_lsp

Just found out there is a real lsp, gonna have a crack at adding that too, but I suppose it doesn't hurt to have both?

You will see, adding a language server is super easy. Look for recent PRs that have done it.
Sure we can have both.

Yeah, looks pretty straightforward! Will give it a go, but first I'll have to get typos-lsp upstreamed. Wish me luck!

Yeah, looks pretty straightforward! Will give it a go, but first I'll have to get typos-lsp upstreamed. Wish me luck!

If you need some help for upstreaming the language server, tag me on your PR :)


[BUG] Redis Backed Chat Memory Error - "Cannot read private member from an object whose class did not declare it"

Describe the bug
When using Redis Backed Memory Store in a Conversational QA Retriever Chain I get the following error:
TypeError: Cannot read private member from an object whose class did not declare it
    at __classPrivateFieldGet (/usr/local/lib/node_modules/flowise/node_modules/@redis/client/dist/lib/client/index.js:4:94)
    at get isReady [as isReady] (/usr/local/lib/node_modules/flowise/node_modules/@redis/client/dist/lib/client/index.js:86:16)
    at RedisChatMessageHistory.ensureReadiness (/usr/local/lib/node_modules/flowise/node_modules/langchain/dist/stores/message/redis.cjs:48:26)
    at RedisChatMessageHistory.getMessages (/usr/local/lib/node_modules/flowise/node_modules/langchain/dist/stores/message/redis.cjs:54:20)
    at BufferMemory.loadMemoryVariables (/usr/local/lib/node_modules/flowise/node_modules/langchain/dist/memory/buffer_memory.cjs:40:49)
    at ConversationalRetrievalQAChain.call (/usr/local/lib/node_modules/flowise/node_modules/langchain/dist/chains/base.cjs:80:49)
    at ConversationalRetrievalQAChain_Chains.run (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/chains/ConversationalRetrievalQAChain/ConversationalRetrievalQAChain.js:161:37)
    at App.processPrediction (/usr/local/lib/node_modules/flowise/dist/index.js:723:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /usr/local/lib/node_modules/flowise/dist/index.js:427:13

To Reproduce
Steps to reproduce the behavior:

Go to Marketplace and choose "Conversational Retrieval QA Chain".
Click on 'Use Template'
Add a Redis Backed Chat Memory and plug it into the memory slot of the "Conversational Retrieval QA Chain" card.
Configure the redis card to point to a valid Redis instance.
Save
Run chat as normal and you will see an error.

Expected behavior
Chat should function normally without error.
Screenshots

Setup

Installation docker on Portainer instance
Flowise Version 1.2.16
OS: Linux
Browser Brave

does it work if you use the conversation chain:

Yes. Works just fine there.

I'm hitting this same error with redis with an OpenAI function agent.  The odd thing - it works fine if I query from the Flowise UI.  If it send a query via API, it throws the "Cannot read private member from an object whose class did not declare it".

Hello, I have the same return.
Using the Flowise UI chat, there is feedback. If you use the API the error happens.

Hello, I'm having the same problem with the Conversational Retrieval QA Chain.

I have the same issue with the Conversational Retrieval QA Chain as well.

@HenryHengZJ or  @chungyau97 - Can you help fix this issue please?

I personally used the "Upstash Redis backed chat memory" to resolve this issue.
Please tag me if the issue with Redis backed chat memory gets resolved.
--
Aleksanteri Halonen
Junior DevOps Engineer
+358 50 463 0572
Avanio
From: vijaykammili @.>
Sent: perjantai 20. lokakuuta 2023 23.32
To: FlowiseAI/Flowise @.>
Cc: Aleksanteri Halonen @.>; Comment @.>
Subject: Re: [FlowiseAI/Flowise] [BUG] Redis Backed Chat Memory Error - "Cannot read private member from an object whose class did not declare it" (Issue #614)
@HenryHengZJhttps://github.com/HenryHengZJ or @chungyau97https://github.com/chungyau97 - Can you help fix this issue please?

Reply to this email directly, view it on GitHubhttps://github.com/FlowiseAI/Flowise/issues/614#issuecomment-1773357356, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A32PKJQVV7XJBIQC7XJSQOTYALNS7AVCNFSM6AAAAAA2XCFOHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGM2TOMZVGY.
You are receiving this because you commented.Message ID: @.***>

This PR will be fixing the issue - https://github.com/FlowiseAI/Flowise/pull/1118

Fixed in Release 1.3.9


Update New-NetEventSession.md

added description for As Job

Docs Build status updates of commit 0a14a62:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/neteventpacketcapture/New-NetEventSession.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@get-itips @tseward
Peer review needed for this PR. Thanks.


Can't upgrade to latest version

I first searched here and in the readme.md why I couldn't upgrade from v8.5x to v9.5.1 and didn't find any answer.
Then I tried to uninstall and reinstall and got same version, VScode didn't warn for a new version of GitLens.
The reason seems due to the fact I was running VScode v1.2.1. Once I upgraded VScode to current v<IP_ADDRESS> it offered me to upgrade GitLens.
Sorry if I make the Question and the Answer but it's weird and thought it may help another one that me to now the solution ;-)

Yeah, this isn't GitLens specific. It is just way vscode handles extension versioning -- an extension says what the minimum version of vscode that is needed (because of apis or features) and vscode will only allow you to install the latest version of an extension compatible with your vscode version. It would indeed be nice if vscode made that more clear in the UI as to why you might not have the latest version (and could be an opportunity for them to suggest upgrading 😄). Would you might opening an issue on the vscode repo with your experience?

I anticipate what they will tell me, you're the first one that ask, nobody change default settings:

Extensions:Auto Update
Update:Enable Windows Background Updates
Update:Channel
;-)

@localhost61 thanks for reporting that -- I added my 2c too ;)

5000 pending issues in VScode !!! Wahoo ! I didn't had heart to add one :-/


Simplify diolinux-team-bot main logic for later updates

Hello,
I watched the latest Diolinux video,
and decided as a quick exercise to help simplify the basic logic of the bot.
If you are happy with the changes, I sent it to you as a pull request.
If it becomes necessary, I suggest using SlashCommands instead of this method via prefixes.
Sincerely, Gabriel Almir (@galmirpr).

And I think the author could prefer contributions to be written in portuguese, I'm writing the review in English just because that pull request was written in English too.

LGTM


Add support for Python 3.9-3.10 and Django 3.2

Test/CI
Description
Add support for Python 3.9-3.10 and Django 3.2 to CI test matrix.
Why should this be added
These are the latest supported versions of Python and Django users are using
Checklist

[ ] Tests are passing
[ ] Documentation has been added or amended for this feature / update

@jonathan-s Current version in master supports Django 4.0, but is not yet released. Is there any way to push out a minor revision?

Please see #399 where @ZuluPro is considering adding another maintainer to allow this to happen.


R program to convert a string to an integer #3323-by-shounak-kulkarni

📑 Description
I have written a program in R to convert a string to an integer.
🐞 Related Issue
use Issue Number like => Closes #3323

#📑 Description
I have written a program in Dart program to add two matrices.
program/program/add-two-matrices/add_two_matrices.dart
#🐞 Related Issue
use Issue Number => #3438


Possible memory leak in Ap_sort

Hi,
The following test input (input.js) causes the possible memory leaks.
$cat input.js
c = 30000;
a = [];
for (i = 0; i < 2 * c; i += 1) {
  a.push(i%c);
}
a.sort(function (x, y) { return_x -=y; });
print(a[2 * c - 2]);

$./mujs input.js
ReferenceError: 'return_x' is not defined
	at input.js:6
	at Array.prototype.sort (native)
	at input.js:6

=================================================================
==26067==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 1440000 byte(s) in 1 object(s) allocated from:
    #0 0x7ffff6ef6b40 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb40)
    #1 0x7ffff64825af in qsort_r (/lib/x86_64-linux-gnu/libc.so.6+0x425af)
    #2 0x555555568f47 in Ap_sort /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsarray.c:313
    #3 0x5555555ad432 in jsR_callcfunction /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsrun.c:1249
    #4 0x5555555adf31 in js_call /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsrun.c:1299
    #5 0x5555555b297d in jsR_run /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsrun.c:1810
    #6 0x5555555ad18a in jsR_callscript /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsrun.c:1230
    #7 0x5555555adde6 in js_call /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsrun.c:1295
    #8 0x5555555b5455 in js_dofile /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/jsstate.c:249
    #9 0x555555567b9d in main /home/haoxin/disk-smu/research/structured-fuzz/experiments/mujs-1.3.5/main.c:363
    #10 0x7ffff6461c86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)

SUMMARY: AddressSanitizer: 1440000 byte(s) leaked in 1 allocation(s).

Compilation command: add -fsanitize=address into CFLGAS in Makefile.
Compiler version: gcc-7.5.0.
System: ubuntu 18.04.
Thanks.

I don't think I see the leak at the code.
Ap_sort does make an allocation which the VM is not aware or, but it's inside try/catch, and it's freed at the catch part, and the pointer variable is appropriately volatile. So it's not immediately obvious to me why it would leak.
Which version of mujs are you testing? Can you try with current master if you were testing with an older version? (I don't have the bandwidth to look into it myself, so these are just thoughts)

The leak happens because the callback throws an exception, which longjmps out of the qsort function.
On GNU libc, qsort is implemented as a mergesort with temporary storage allocated with malloc.
When the callback jumps out with an exception, libc leaks that storage.
We can replace the use of system qsort with our own implementation of an in-place sorting algorithm,
such as heapsort (which is approx 2x slower than gnu libc's mergesort on a large arrays).

libc leaks that storage.

Interesting.
Long while ago I experimented with different sorts.
I think this is a minimal implementation of heap sort, and as far as I recall it was on par with glibc - not slower than x1.3 or some such, but there could be classes of input which I didn't test. (I also have similar code with other "base" sort functions, like quicksort and other types, some surprisingly tiny).
It has two siftdown functions, and I don't recall which is better/faster (I'm pretty sure both work, and I have few more which I didn't copy here, some faster than others, and other variables).
Hopefully it's complete, but I extracted it manually from an old large file with lots of experiments, so hopefully I got the right parts. Maybe it can be reused. I didn't try to compile it now:

heap sort for mujs
// compatible with qsort_r (linux/bsd libc)
static int sortcmp_r(const void *va, const void *vb, void *ctx)
{
        // if (va == vb || memcmp(va, vb, sizeof(js_Value)) == 0)
        //      return 0;

        js_State *J = ctx;
        const js_Value *a = va, *b = vb;
        const char *sx, *sy;
        double v;
        int c;

        int unx = (a->type == JS_TUNDEFINED);
        int uny = (b->type == JS_TUNDEFINED);
        if (unx) return !uny;
        if (uny) return -1;

        if (js_iscallable(J, 1)) {
                js_copy(J, 1); /* copy function */
                js_pushundefined(J);
                js_pushvalue(J, *a);
                js_pushvalue(J, *b);
                js_call(J, 2);
                v = js_tonumber(J, -1);
                c = (v == 0) ? 0 : (v < 0) ? -1 : 1;
                js_pop(J, 1);
        } else {
                js_pushvalue(J, *a);
                js_pushvalue(J, *b);
                sx = js_tostring(J, -2);
                sy = js_tostring(J, -1);
                c = strcmp(sx, sy);
                js_pop(J, 2);
        }
        return c;
}

#define JS_VSWAP(a, b) do { js_Value tmp__ = a; a = b; b = tmp__; } while (0)

// parent/left-child of i in array-as-heap. i/end are [unsigned] integrals
// PARENT expects i>0, LCHILD expects end>0 and evaluates to 0 if no l-child
// RCHILD(i) exists and is LCHILD(i)+1 if and only if (0 < LCHILD(i) < end)
#define PARENT(i)       (((i) - 1) / 2)
#define LCHILD(i, end)  ((i) <= PARENT(end) ? (i) * 2 + 1 : 0)

// expects end > 0  ("bottom-up"/bounce sift down)
static void xsiftdown(js_State *J, js_Value *arr, size_t i, size_t end)
{
        size_t j = i, lc;

        // seek down a leaf j at the end of a path-of-biggest-siblings from i
        while ((lc = LCHILD(j, end)))
                j = lc < end && sortcmp_r(arr+lc, arr+lc+1, J) <= 0
                    ? lc + 1 : lc;  // right if have both and L<=R, else left

        // seek up to target position j
        while (i < j && sortcmp_r(arr+i, arr+j, J) > 0)
                j = PARENT(j);

        // rotate the branch a[i]...a[j] one level up (and a[i] to j)
        while (i < j) {
                JS_VSWAP(arr[i], arr[j]);
                j = PARENT(j);
        }
}
static void siftdown(js_State *J, js_Value *arr, size_t i, size_t end)
{
        js_Value arri = arr[i];
        size_t j = i, x;

        // move up by 1 level a path-of-biggest-siblings from i to a leaf j
        for ( ; (x = LCHILD(j, end)); j = x) {
                if (x < end && sortcmp_r(arr+x, arr+x+1, J) <= 0)
                        ++x;  // right if have both L,R and L<=R
                arr[j] = arr[x];
        }

        // if needed, move back down nodes smaller than a[i] on our path
        for ( ; x = PARENT(j), i < j && sortcmp_r(&arri, arr+x, J) > 0; j = x)
                arr[j] = arr[x];

        arr[j] = arri;  // in the hole
}

static void js_heapsort(js_State *J, js_Value *arr, size_t n)
{
        size_t i;

        for (i = PARENT(n - 1); i; --i)  // sans sift(0, n-1)
                siftdown(J, arr, i, n - 1);

        for (i = n - 1; i; --i) {  // starts with sift(0, n-1)
                siftdown(J, arr, 0, i);
                JS_VSWAP(arr[0], arr[i]);
        }
}

static void Ap_sort(js_State *J)
{
        int i, n, len;
        len = js_getlength(J, 0);
        if (len < 2)
                goto done;

        n = 0;
        js_newarray(J);  // flat array copy which we'd sort
        for (i = 0; i < len; ++i)
                if (js_hasindex(J, 0, i))
                        js_setindex(J, -2, n++);

        js_Value *v = js_tovalue(J, -1);
        assert (v->type == JS_TOBJECT && v->u.object->type == JS_CARRAY);
        if (!v->u.object->u.a.simple)
                js_rangeerror(J, "array is too large to sort");

        js_Value *arr = v->u.object->u.a.array;
        sort_r(arr, n, sizeof *arr, sortcmp_r, J);

        for (i = 0; i < n; ++i) {
                js_pushvalue(J, arr[i]);
                js_setindex(J, 0, i);
        }
        for (i = n; i < len; ++i) {
                js_delindex(J, 0, i);
        }

done:
        js_copy(J, 0);
}

I found some of our old sorting experiments on various branches (including your heapsort, and an in-place quicksort implementation). I'll see if I can revive one of those to fix this issue.

Added to the code above a missing tiny intermediate function:
static void sort_r(void *arr, size_t n, size_t size, cmp_ft cmp, void *J)
{
        // size assumed of js_Value, cmp hardcoded
        if (n > 1)
                js_heapsort(J, arr, n);
}

It has two siftdown functions, and I don't recall which is better/faster (I'm pretty sure both work

I think I remember now. The xsiftdown function is more generic and uses only swaps, while the siftdown function is (more?) mujs-specific and assigns arrays elements directly from place to place, and therefore should be faster.

Fixed in 02147f5a9f52bd6016c735ccaf1179eee08e2192.
All my tests put the heapsort as measurably slower than the quicksort, but I've left an implementation of heapsort in place (to enable set the JS_HEAPSORT=1 predefine) in case you want to use that instead.

All my tests put the heapsort as measurably slower than the quicksort,

I presume this includes my implementation?
The issue with your current code is that swap can be very expensive, but in my code it uses a flat array so that swaps are effectively instant.

Yes, this is the same algorithm with the same number of compares and swaps.
The current code uses a flat array too.


Bug? Binding a model to a transaction

Hi
In the documentation https://vincit.github.io/objection.js/guide/transactions.html#using-a-transaction, it suggests that the following pattern can be used for binding models to transactions.
const { transaction } = require('objection');

try {
  const scrappy = await transaction(Person, Animal, async (Person, Animal) => {
    // Person and Animal inside this function are bound to a newly
    // created transaction. The Person and Animal outside this function
    // are not! Even if you do `require('./models/Person')` inside this
    // function and start a query using the required `Person` it will
    // NOT take part in the transaction. Only the actual objects passed
    // to this function are bound to the transaction.

    await Person
      .query()
      .insert({firstName: 'Jennifer', lastName: 'Lawrence'});

    return Animal
      .query()
      .insert({name: 'Scrappy'});
  });
} catch (err) {
  console.log('Something went wrong. Neither Jennifer nor Scrappy were inserted');
}

However, adding models as parameters before the callback which then passes copies of those models doesn't seem to work. It does seem to clash with the 'standard' approach of
const { transaction } = require('objection');
// You can access `knex` instance anywhere you want.
// One way is to get it through any model.
const knex = Person.knex();

try {
  const scrappy = await transaction(knex, async (trx) => {
(...)

I am quite new to the Objection world, so I wondered if I am misunderstanding something.

It works. trx is always the last argument passed to the callback.

If you think this is a bug you found, it must mean that literally nobody is using this library since you are the first one to find it. In that case you shouldn't be using the library either. The other option is that it isn't a bug. Objection has 4000 tests.

As I said, I am quite new to objection. I am not sure what you mean about "library"? This is code directly from the Objection documentation and I am using the Objection library.
I have found that the below works
    const knex = Booking.knex();
    if (has(Booking, 'jsonSchema.properties.user_id')) {
      req.body.user_id = req.user.schema_user_id;
    }
    const bookingResults = await transaction(knex, async trx => {

but the below doesn't. According the documentation they are synonymous.
const bookingResults = await transaction(Booking, async BoundBooking => {

😄 Both of those eork, but they are in no way synonymous. Please read the docs a little better.


Fix hosted sandcastle

Fixes #3838
Also updates the rectangle CZML example for the new image material property

:+1: As soon as the deployment is ready I'll merge this.


altered the prompts to be a bit more clear

Added the cloud provider to the example and altered the prompt for the file path to make clear it will use the default by just pressing enter.
Should any of this go into the prerequisites, or is it best left as a lab step since they'd be assigned their snowflake resources in the lab?

thinking maybe we could add andy's connection script into your app, to verify configuration. I'll look at doing that

thinking maybe we could add andy's connection script into your app, to verify configuration. I'll look at doing that

You'd want to move the guts of Andy's script into a function with a name, then call that function from the configure script.


Build and push Docker image on tag

Thank you for this awesome project! This PR adds support for docker image build&publish to the Github image registry, when a tag is pushed.
If e.g. tagging a commit as v1.3.0, this workflow will make the image available as:

ghcr.io/rhasspy/wyoming-satellite:1.3.0
ghcr.io/rhasspy/wyoming-satellite:1.3
ghcr.io/rhasspy/wyoming-satellite:latest

I had built the 1.2.0 image for myself (can be inspected with docker pull ghcr.io/mvitale1989/wyoming-satellite:1.2.0-1, with a slightly different tagging scheme) to use it in my k8s cluster, but it'd be great if this is done in the project repo itself.
The additional dependencies are useful client tools to record/play sound against the most common sound servers.

Did you build one image and use it for all different containers?

If you're referring to my Kubernetes deployment, I only built the wyoming-satellite image. The other containers use other images which were already publicly available (e.g. wyoming-piper, wyoming-whisper and wyoming-openwakeword are all on Docker Hub already)

I improved your work a bit (i hope).
See https://github.com/florian-asche/wyoming-satellite/tree/feat-add-ghr-support
I added a build job for the main branch so we also have the latest image for testing and i added a build for the 2mic_hat led. Need to clean that up and add a proper docker-compose file, the one that was there got me confused.
I also played with some deps and i added a arm64 based image for my pi zero 2w with 2mic_hat.


Unable to solve: git checkout fails

dep cache (sources)
When using dep i suddenly got an error, saying it failed a command. This happend only with the package from github.com/grpc-ecosystem/go-grpc-middleware. I thought it would be a mismatch of constraints, so i removed the .lock and .toml and used dep init to start over. This didn't work either.
I do not exactly know how or why this happened, and don't know exactly how to reproduce.
I fixed this issue by clearing dep's cache. A copy of the malfunctioning cache is attached to this issue. The error occurs using that cache. So reproduction can probably be done using that cache.
What version of dep are you using (dep version)?
dep:
version     : devel
build date  :
git hash    :
go version  : go1.9.1
go compiler : gc
platform    : darwin/amd64
What dep command did you run?
dep ensure -v:
`found 375 errors in the package tree:
import root "" is not a prefix for the package's declared canonical path ""
Root project is "github.com/xxx"
420 transitively valid internal packages
338 external packages imported from 55 projects
(0)   ✓ select (root)
(1)     ? attempt cloud.google.com/go with 27 pkgs; at least 1 versions to try
(1)         try<EMAIL_ADDRESS>(1)     ✓ select<EMAIL_ADDRESS>w/38 pkgs
(2)     ? attempt github.com/davecgh/go-spew with 2 pkgs; at least 1 versions to try
(2)         try<EMAIL_ADDRESS>(2)     ✓ select<EMAIL_ADDRESS>w/2 pkgs
(3)     ? attempt github.com/dgrijalva/jwt-go with 3 pkgs; at least 1 versions to try
(3)         try<EMAIL_ADDRESS>(3)     ✓ select<EMAIL_ADDRESS>w/3 pkgs
(4)     ? attempt github.com/golang/protobuf with 17 pkgs; at least 1 versions to try
(4)         try github.com/golang/protobuf@130e6b02ab059e7b717a096f397c5b60111cae74
(4)     ✓ select github.com/golang/protobuf@130e6b02ab059e7b717a096f397c5b60111cae74 w/17 pkgs
(5)     ? attempt github.com/googleapis/gax-go with 1 pkgs; at least 1 versions to try
(5)         try<EMAIL_ADDRESS>(5)     ✓ select<EMAIL_ADDRESS>w/1 pkgs
(6)     ? attempt github.com/golang/mock with 9 pkgs; at least 1 versions to try
(6)         try<EMAIL_ADDRESS>(6)     ✓ select<EMAIL_ADDRESS>w/9 pkgs
(7)     ? attempt github.com/grpc-ecosystem/grpc-gateway with 15 pkgs; at least 1 versions to try
(7)         try<EMAIL_ADDRESS>(7)     ✓ select<EMAIL_ADDRESS>w/15 pkgs
(8)     ? attempt github.com/pmezard/go-difflib with 1 pkgs; at least 1 versions to try
(8)         try<EMAIL_ADDRESS>(8)     ✓ select<EMAIL_ADDRESS>w/1 pkgs
(9)     ? attempt github.com/grpc-ecosystem/go-grpc-middleware with 15 pkgs; at least 1 versions to try
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@master
(9)     ✗   unable to update checked out version: : command failed: [git checkout fa8fef87dcecac0bda02d36abb3c790ab9e0030b]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@master
(9)     ✗   unable to update checked out version: : command failed: [git checkout d0c54e68681ec7999ac17864470f3bee6521ba2b]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@better_docs
(9)     ✗   unable to update checked out version: : command failed: [git checkout 63e69ea2fcaa6764e67826381756e528db9203ab]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@bugfix/37-panic-on-err
(9)     ✗   unable to update checked out version: : command failed: [git checkout b9814e2370c8552db05c796c139b76a6ca45b34f]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@bugfix/extract_logging_suits
(9)     ✗   unable to update checked out version: : command failed: [git checkout 43906efc49b0f6465d83b82a5083de0e7761dcdf]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@bugfix/logrus
(9)     ✗   unable to update checked out version: : command failed: [git checkout 9b733b364a9f8926acac421f892fbbe27d29aa74]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@docs/improv
(9)     ✗   unable to update checked out version: : command failed: [git checkout 56777f3d037598a80b78a32e5d5419e41899a69a]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@docs_examples
(9)     ✗   unable to update checked out version: : command failed: [git checkout f057644d01535d424d9f5b80bf564f5b93b0cd84]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_and_backoff
(9)     ✗   unable to update checked out version: : command failed: [git checkout 5869908ce3233659416c7f62a52729b45ac4c68e]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_middleware
(9)     ✗   unable to update checked out version: : command failed: [git checkout bb477492c0f80291204bfb24ecdc04c237a34668]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/clieant-stream-chain
(9)     ✗   unable to update checked out version: : command failed: [git checkout 9eb2156738af2ed8cae4d60b9f7a14894b0df6c2]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/client-streaming-chain
(9)     ✗   unable to update checked out version: : command failed: [git checkout bdf4b13226548014a7a7e2b6e45d6ebb8744192b]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/client-unary-chain
(9)     ✗   unable to update checked out version: : command failed: [git checkout 20678db999746215e1b55b092bf966e28c012276]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/client_logging
(9)     ✗   unable to update checked out version: : command failed: [git checkout e55adc978a72e06d9dda1f0acca1cf8dfe205bb5]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/client_payload_logging
(9)     ✗   unable to update checked out version: : command failed: [git checkout 5a08330966336de29b298af4e3687b1d613ead3b]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/client_retry
(9)     ✗   unable to update checked out version: : command failed: [git checkout b2b0a065ba58db4980748433b08a001a91601119]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/generic-loggign
(9)     ✗   unable to update checked out version: : command failed: [git checkout df447e6c7750cf3f70aa82abfbb1eb6825312a1c]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/logging_zap
(9)     ✗   unable to update checked out version: : command failed: [git checkout 42fc6b4063d8512830d84c84af84b5c8751c01a7]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/metadata_helpers
(9)     ✗   unable to update checked out version: : command failed: [git checkout 5e56df3f097d4d25eeda1a52edcf90dbdea256fe]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/new_nicemd
(9)     ✗   unable to update checked out version: : command failed: [git checkout 4fdae8e41278557cf6996d66ab442c3d7fda61bf]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing-both
(10)  ✗   github.com/grpc-ecosystem/go-grpc-middleware at feature/opentracing-both has problem subpkg(s):
(10)            github.com/grpc-ecosystem/go-grpc-middleware/recovery is missing; required by (root).
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing_tags
(10)  ✗   github.com/grpc-ecosystem/go-grpc-middleware at feature/opentracing_tags has problem subpkg(s):
(10)            github.com/grpc-ecosystem/go-grpc-middleware/recovery is missing; required by (root).
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/repo-move
(9)     ✗   unable to update checked out version: : command failed: [git checkout f4c5d7b716c44e51234f4cb882feffc08d97e465]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/tags
(10)  ✗   github.com/grpc-ecosystem/go-grpc-middleware at feature/tags has problem subpkg(s):
(10)            github.com/grpc-ecosystem/go-grpc-middleware/recovery is missing; required by (root).   github.com/grpc-ecosystem/go-grpc-middleware/tracing/opentracing is missing; required by (root).
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@feature/validator-middlewre
(9)     ✗   unable to update checked out version: : command failed: [git checkout 105b5b49a527cb458ae589571e1db98a54fae9d2]: exit status 1
(9)         try github.com/grpc-ecosystem/go-grpc-middleware@goimports-scripts
(9)     ✗   unable to update checked out version: : command failed: [git checkout ca9398dd0aa1c233b201166416a6b3070ee80948]: exit status 1
(9)       ← no more versions of github.com/grpc-ecosystem/go-grpc-middleware to try; begin backtrack
(8)     ← backtrack: no more versions of github.com/pmezard/go-difflib to try
(7)     ← backtrack: no more versions of github.com/grpc-ecosystem/grpc-gateway to try
(6)     ← backtrack: no more versions of github.com/golang/mock to try
(5)     ← backtrack: no more versions of github.com/googleapis/gax-go to try
(4)     ← backtrack: no more versions of github.com/golang/protobuf to try
(3)     ← backtrack: no more versions of github.com/dgrijalva/jwt-go to try
(2)     ← backtrack: no more versions of github.com/davecgh/go-spew to try
(1)     ← backtrack: no more versions of cloud.google.com/go to try
✗ solving failed
Solver wall times by segment:
b-list-versions: 5.650483366s
b-source-exists: 5.116897429s
b-list-pkgs: 2.623378458s
b-gmal: 1.198886643s
select-root:  24.015724ms
satisfy:   4.247408ms
unselect:   2.897358ms
select-atom:   2.592615ms
new-atom:   1.207286ms
b-deduce-proj-root:    214.166µs
backtrack:     88.214µs
other:     39.111µs
TOTAL: 14.624947778s
ensure Solve(): No versions of github.com/grpc-ecosystem/go-grpc-middleware met constraints:
master: unable to update checked out version: : command failed: [git checkout fa8fef87dcecac0bda02d36abb3c790ab9e0030b]: exit status 1
master: unable to update checked out version: : command failed: [git checkout d0c54e68681ec7999ac17864470f3bee6521ba2b]: exit status 1
better_docs: unable to update checked out version: : command failed: [git checkout 63e69ea2fcaa6764e67826381756e528db9203ab]: exit status 1
bugfix/37-panic-on-err: unable to update checked out version: : command failed: [git checkout b9814e2370c8552db05c796c139b76a6ca45b34f]: exit status 1
bugfix/extract_logging_suits: unable to update checked out version: : command failed: [git checkout 43906efc49b0f6465d83b82a5083de0e7761dcdf]: exit status 1
bugfix/logrus: unable to update checked out version: : command failed: [git checkout 9b733b364a9f8926acac421f892fbbe27d29aa74]: exit status 1
docs/improv: unable to update checked out version: : command failed: [git checkout 56777f3d037598a80b78a32e5d5419e41899a69a]: exit status 1
docs_examples: unable to update checked out version: : command failed: [git checkout f057644d01535d424d9f5b80bf564f5b93b0cd84]: exit status 1
feature/auth_and_backoff: unable to update checked out version: : command failed: [git checkout 5869908ce3233659416c7f62a52729b45ac4c68e]: exit status 1
feature/auth_middleware: unable to update checked out version: : command failed: [git checkout bb477492c0f80291204bfb24ecdc04c237a34668]: exit status 1
feature/clieant-stream-chain: unable to update checked out version: : command failed: [git checkout 9eb2156738af2ed8cae4d60b9f7a14894b0df6c2]: exit status 1
feature/client-streaming-chain: unable to update checked out version: : command failed: [git checkout bdf4b13226548014a7a7e2b6e45d6ebb8744192b]: exit status 1
feature/client-unary-chain: unable to update checked out version: : command failed: [git checkout 20678db999746215e1b55b092bf966e28c012276]: exit status 1
feature/client_logging: unable to update checked out version: : command failed: [git checkout e55adc978a72e06d9dda1f0acca1cf8dfe205bb5]: exit status 1
feature/client_payload_logging: unable to update checked out version: : command failed: [git checkout 5a08330966336de29b298af4e3687b1d613ead3b]: exit status 1
feature/client_retry: unable to update checked out version: : command failed: [git checkout b2b0a065ba58db4980748433b08a001a91601119]: exit status 1
feature/generic-loggign: unable to update checked out version: : command failed: [git checkout df447e6c7750cf3f70aa82abfbb1eb6825312a1c]: exit status 1
feature/logging_zap: unable to update checked out version: : command failed: [git checkout 42fc6b4063d8512830d84c84af84b5c8751c01a7]: exit status 1
feature/metadata_helpers: unable to update checked out version: : command failed: [git checkout 5e56df3f097d4d25eeda1a52edcf90dbdea256fe]: exit status 1
feature/new_nicemd: unable to update checked out version: : command failed: [git checkout 4fdae8e41278557cf6996d66ab442c3d7fda61bf]: exit status 1
feature/opentracing-both: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing-both, as its subpackage github.com/grpc-ecosystem/go-grpc-middleware/recovery is missing. (Package is required by (root).)
feature/opentracing_tags: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing_tags, as its subpackage github.com/grpc-ecosystem/go-grpc-middleware/recovery is missing. (Package is required by (root).)
feature/repo-move: unable to update checked out version: : command failed: [git checkout f4c5d7b716c44e51234f4cb882feffc08d97e465]: exit status 1
feature/tags: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/tags due to multiple problematic subpackages:
Subpackage github.com/grpc-ecosystem/go-grpc-middleware/recovery is missing. (Package is required by (root).)   Subpackage github.com/grpc-ecosystem/go-grpc-middleware/tracing/opentracing is missing. (Package is required by (root).)
feature/validator-middlewre: unable to update checked out version: : command failed: [git checkout 105b5b49a527cb458ae589571e1db98a54fae9d2]: exit status 1
goimports-scripts: unable to update checked out version: : command failed: [git checkout ca9398dd0aa1c233b201166416a6b3070ee80948]: exit status 1`
dep init -v:
`Getting direct dependencies...
Checked 1104 directories for packages.
Found 55 direct dependencies.
Root project is "github.com/xxx/xxx"
420 transitively valid internal packages
338 external packages imported from 55 projects
(0)   ✓ select (root)
(1)     ? attempt github.com/golang/glog with 1 pkgs; 1 versions to try
(1)         try github.com/golang/glog@master
(1)     ✓ select github.com/golang/glog@master w/1 pkgs
(2)     ? attempt github.com/xeipuuv/gojsonschema with 1 pkgs; 1 versions to try
(2)         try github.com/xeipuuv/gojsonschema@master
(2)     ✓ select github.com/xeipuuv/gojsonschema@master w/1 pkgs
(3)     ? attempt github.com/rogpeppe/fastuuid with 1 pkgs; 1 versions to try
(3)         try github.com/rogpeppe/fastuuid@master
(3)     ✓ select github.com/rogpeppe/fastuuid@master w/1 pkgs
(4)     ? attempt github.com/xxx/xxx with 1 pkgs; 1 versions to try
(4)         try github.com/xxx/xxx@master
(4)     ✓ select github.com/xxx/xxx@master w/1 pkgs
(5)     ? attempt github.com/xeipuuv/gojsonreference with 1 pkgs; 1 versions to try
(5)         try github.com/xeipuuv/gojsonreference@master
(5)     ✓ select github.com/xeipuuv/gojsonreference@master w/1 pkgs
(6)     ? attempt github.com/tomasen/realip with 1 pkgs; 1 versions to try
(6)         try github.com/tomasen/realip@master
(6)     ✓ select github.com/tomasen/realip@master w/1 pkgs
(7)     ? attempt golang.org/x/time with 1 pkgs; 1 versions to try
(7)         try golang.org/x/time@master
(7)     ✓ select golang.org/x/time@master w/1 pkgs
(8)     ? attempt github.com/xeipuuv/gojsonpointer with 1 pkgs; 1 versions to try
(8)         try github.com/xeipuuv/gojsonpointer@master
(8)     ✓ select github.com/xeipuuv/gojsonpointer@master w/1 pkgs
(9)     ? attempt golang.org/x/oauth2 with 5 pkgs; 1 versions to try
(9)         try golang.org/x/oauth2@master
(9)     ✓ select golang.org/x/oauth2@master w/5 pkgs
(10)  ? attempt google.golang.org/genproto with 32 pkgs; 1 versions to try
(10)      try google.golang.org/genproto@master
(10)  ✓ select google.golang.org/genproto@master w/32 pkgs
(11)  ? attempt golang.org/x/build with 3 pkgs; 1 versions to try
(11)      try golang.org/x/build@master
(11)  ✓ select golang.org/x/build@master w/3 pkgs
(12)  ? attempt golang.org/x/crypto with 7 pkgs; 1 versions to try
(12)      try golang.org/x/crypto@master
(12)  ✓ select golang.org/x/crypto@master w/9 pkgs
(13)  ? attempt golang.org/x/debug with 2 pkgs; 1 versions to try
(13)      try golang.org/x/debug@master
(13)  ✓ select golang.org/x/debug@master w/8 pkgs
(14)  ? attempt google.golang.org/api with 30 pkgs; 2 versions to try
(14)      try google.golang.org/api@master
(14)  ✓ select google.golang.org/api@master w/32 pkgs
(15)  ? attempt golang.org/x/text with 29 pkgs; 1 versions to try
(15)      try golang.org/x/text@master
(15)  ✓ select golang.org/x/text@master w/37 pkgs
(16)  ? attempt gopkg.in/inf.v0 with 1 pkgs; 1 versions to try
(16)      try<EMAIL_ADDRESS>(16)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(17)  ? attempt github.com/golang/protobuf with 17 pkgs; 2 versions to try
(17)      try github.com/golang/protobuf@master
(17)  ✓ select github.com/golang/protobuf@master w/17 pkgs
(18)  ? attempt github.com/golang/mock with 9 pkgs; 2 versions to try
(18)      try<EMAIL_ADDRESS>(18)  ✓ select<EMAIL_ADDRESS>w/9 pkgs
(19)  ? attempt golang.org/x/sync with 3 pkgs; 1 versions to try
(19)      try golang.org/x/sync@master
(19)  ✓ select golang.org/x/sync@master w/3 pkgs
(20)  ? attempt github.com/xxx/xxx with 3 pkgs; 2 versions to try
(20)      try github.com/xxx/xxx@development
(20)  ✓ select github.com/xxx/xxx@development w/3 pkgs
(21)  ? attempt github.com/xxx/xxx with 11 pkgs; 3 versions to try
(21)      try github.com/xxx/xxx@development
(21)  ✓ select github.com/xxx/xxx@development w/11 pkgs
(22)  ? attempt golang.org/x/tools with 2 pkgs; 9 versions to try
(22)      try golang.org/x/tools@master
(22)  ✓ select golang.org/x/tools@master w/3 pkgs
(23)  ? attempt github.com/stretchr/objx with 1 pkgs; 2 versions to try
(23)      try<EMAIL_ADDRESS>(23)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(24)  ? attempt google.golang.org/appengine with 14 pkgs; 3 versions to try
(24)      try<EMAIL_ADDRESS>(24)  ✓ select<EMAIL_ADDRESS>w/18 pkgs
(25)  ? attempt golang.org/x/sys with 7 pkgs; 1 versions to try
(25)      try golang.org/x/sys@master
(25)  ✓ select golang.org/x/sys@master w/7 pkgs
(26)  ? attempt gopkg.in/check.v1 with 1 pkgs; 1 versions to try
(26)      try gopkg.in/check.v1@v1
(26)  ✓ select gopkg.in/check.v1@v1 w/1 pkgs
(27)  ? attempt github.com/davecgh/go-spew with 2 pkgs; 3 versions to try
(27)      try<EMAIL_ADDRESS>(27)  ✓ select<EMAIL_ADDRESS>w/2 pkgs
(28)  ? attempt golang.org/x/net with 8 pkgs; 5 versions to try
(28)      try golang.org/x/net@master
(28)  ✓ select golang.org/x/net@master w/10 pkgs
(29)  ? revisit golang.org/x/text to add 2 pkgs
(29)    ✓ include 14 more pkgs from golang.org/x/text@master
(29)  ? attempt github.com/grpc-ecosystem/grpc-gateway with 15 pkgs; 18 versions to try
(30)      try<EMAIL_ADDRESS>(30)  ✓ select<EMAIL_ADDRESS>w/15 pkgs
(30)  ? attempt github.com/googleapis/gax-go with 1 pkgs; 3 versions to try
(31)      try<EMAIL_ADDRESS>(31)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(31)  ? attempt github.com/gorilla/mux with 1 pkgs; 14 versions to try
(32)      try<EMAIL_ADDRESS>(32)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(32)  ? attempt github.com/xxx/xxx with 11 pkgs; 49 versions to try
(33)      try github.com/xxx/xxx@development
(33)  ✓ select github.com/xxx/xxx@development w/11 pkgs
(33)  ? attempt github.com/pmezard/go-difflib with 1 pkgs; 3 versions to try
(34)      try<EMAIL_ADDRESS>(34)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(34)  ? attempt github.com/gorilla/context with 1 pkgs; 2 versions to try
(35)      try<EMAIL_ADDRESS>(35)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(35)  ? attempt gopkg.in/gemnasium/logrus-airbrake-hook.v2 with 1 pkgs; 4 versions to try
(36)      try<EMAIL_ADDRESS>(36)  ✓ select<EMAIL_ADDRESS>w/1 pkgs
(36)  ? attempt github.com/xxx/xxx with 1 pkgs; 63 versions to try
(37)      try<EMAIL_ADDRESS>(38)  ✗   github.com/xxx/xxx at 1.0.0 has problem subpkg(s):
(38)            github.com/xxx/xxx/client is missing; required by (root).
(37)      try github.com/xxx/xxx@development
(37)  ✓ select github.com/xxx/xxx@development w/1 pkgs
(37)  ? attempt github.com/google/pprof with 1 pkgs; 3 versions to try
(38)      try github.com/google/pprof@master
(38)  ✓ select github.com/google/pprof@master w/1 pkgs
(38)  ? attempt gopkg.in/asaskevich/govalidator.v4 with 1 pkgs; 1 versions to try
(39)      try gopkg.in/asaskevich/govalidator.v4@v4
(39)  ✓ select gopkg.in/asaskevich/govalidator.v4@v4 w/1 pkgs
(39)  ? attempt github.com/grpc-ecosystem/go-grpc-middleware with 15 pkgs; 25 versions to try
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@master
(40)  ✗   unable to update checked out version: : command failed: [git checkout d0c54e68681ec7999ac17864470f3bee6521ba2b]: exit status 1
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@better_docs
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@better_docs not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@bugfix/37-panic-on-err
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@bugfix/37-panic-on-err not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@bugfix/extract_logging_suits
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@bugfix/extract_logging_suits not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@bugfix/logrus
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@bugfix/logrus not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@docs/improv
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@docs/improv not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@docs_examples
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@docs_examples not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_and_backoff
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_and_backoff not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_middleware
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_middleware not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/clieant-stream-chain
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/clieant-stream-chain not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/client-streaming-chain
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/client-streaming-chain not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/client-unary-chain
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/client-unary-chain not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/client_logging
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/client_logging not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/client_payload_logging
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/client_payload_logging not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/client_retry
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/client_retry not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/generic-loggign
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/generic-loggign not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/logging_zap
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/logging_zap not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/metadata_helpers
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/metadata_helpers not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/new_nicemd
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/new_nicemd not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing-both
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing-both not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing_tags
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing_tags not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/repo-move
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/repo-move not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/tags
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/tags not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@feature/validator-middlewre
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@feature/validator-middlewre not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)      try github.com/grpc-ecosystem/go-grpc-middleware@goimports-scripts
(41)  ✗   github.com/grpc-ecosystem/go-grpc-middleware@goimports-scripts not allowed by constraint master:
(41)      master from github.com/xxx/xxx@development
(40)    ← no more versions of github.com/grpc-ecosystem/go-grpc-middleware to try; begin backtrack
(39)  ← backtrack: no more versions of gopkg.in/asaskevich/govalidator.v4 to try
(38)  ← backtrack: no more versions of github.com/google/pprof to try
(37)  ← backtrack: no more versions of github.com/xxx/xxx to try
(36)  ← backtrack: no more versions of gopkg.in/gemnasium/logrus-airbrake-hook.v2 to try
(35)  ← backtrack: no more versions of github.com/gorilla/context to try
(34)  ← backtrack: no more versions of github.com/pmezard/go-difflib to try
(33)  ← backtrack: no more versions of github.com/xxx/xxx to try
(32)  ← backtrack: no more versions of github.com/gorilla/mux to try
(31)  ← backtrack: no more versions of github.com/googleapis/gax-go to try
(30)  ← backtrack: no more versions of github.com/grpc-ecosystem/grpc-gateway to try
(29)  ← backtrack: popped 14 pkgs from golang.org/x/text
(28)  ← backtrack: no more versions of golang.org/x/net to try
(27)  ← backtrack: no more versions of github.com/davecgh/go-spew to try
(26)  ← backtrack: no more versions of gopkg.in/check.v1 to try
(25)  ← backtrack: no more versions of golang.org/x/sys to try
(24)  ← backtrack: no more versions of google.golang.org/appengine to try
(23)  ← backtrack: no more versions of github.com/stretchr/objx to try
(22)  ← backtrack: no more versions of golang.org/x/tools to try
(21)  ← backtrack: no more versions of github.com/xxx/xxx to try
(21)    ? continue github.com/xxx/xxx with 11 pkgs; 2 more versions to try
(21)      try github.com/xxx/xxx@master
(22)  ✗   github.com/xxx/xxx at master has problem subpkg(s):
(22)            github.com/xxx/xxx/xxx is missing;  required by:
(22)                    github.com/xxx/xxx at
(22)                    github.com/xxx/xxxt at development
(21)      try<EMAIL_ADDRESS>(22)  ✗   github.com/xxx/xxx at go-1.6 has problem subpkg(s):
(22)            github.com/xxx/xxx/xxx is missing;  required by:
(22)                    github.com/xxx/xxx at
(22)                    github.com/xxx/xxx at development    github.com/xxx/xxx/xxx is missing; required by (root).    github.com/xxx/xxx/grpc/client/interceptor is missing; required by (root).       github.com/xxx/xxx/grpc/server/interceptor is missing; required by (root).    github.com/xxx/xxx/xxx is missing;  required by:
(22)                    github.com/xxx/xxx at
(22)                    github.com/xxx/xxx at development
(21)  ← backtrack: no more versions of github.com/xxx/xxx to try
(20)  ← backtrack: no more versions of github.com/xxx/xxx to try
(19)  ← backtrack: no more versions of golang.org/x/sync to try
(18)  ← backtrack: no more versions of github.com/golang/mock to try
(17)  ← backtrack: no more versions of github.com/golang/protobuf to try
(16)  ← backtrack: no more versions of gopkg.in/inf.v0 to try
(15)  ← backtrack: no more versions of golang.org/x/text to try
(14)  ← backtrack: no more versions of google.golang.org/api to try
(13)  ← backtrack: no more versions of golang.org/x/debug to try
(12)  ← backtrack: no more versions of golang.org/x/crypto to try
(11)  ← backtrack: no more versions of golang.org/x/build to try
(10)  ← backtrack: no more versions of google.golang.org/genproto to try
(9)     ← backtrack: no more versions of golang.org/x/oauth2 to try
(8)     ← backtrack: no more versions of github.com/xeipuuv/gojsonpointer to try
(7)     ← backtrack: no more versions of golang.org/x/time to try
(6)     ← backtrack: no more versions of github.com/tomasen/realip to try
(5)     ← backtrack: no more versions of github.com/xeipuuv/gojsonreference to try
(4)     ← backtrack: no more versions of github.com/xxx/xxx to try
(3)     ← backtrack: no more versions of github.com/rogpeppe/fastuuid to try
(2)     ← backtrack: no more versions of github.com/xeipuuv/gojsonschema to try
(1)     ← backtrack: no more versions of github.com/golang/glog to try
✗ solving failed
Solver wall times by segment:
b-list-versions: 49.794262112s
b-list-pkgs:  7.595724709s
b-gmal:   5.97556533s
satisfy:   21.564804ms
unselect:   21.430624ms
select-atom:   19.311555ms
select-root:   14.374147ms
new-atom:    1.602801ms
b-deduce-proj-root:      576.24µs
backtrack:     492.824µs
b-pair-rev:      326.43µs
b-matches:     180.698µs
b-source-exists:     126.747µs
other:      92.077µs
b-pair-version:      43.811µs
add-atom:      13.538µs
TOTAL: 1m3.445688447s
No versions of github.com/grpc-ecosystem/go-grpc-middleware met constraints:
master: unable to update checked out version: : command failed: [git checkout d0c54e68681ec7999ac17864470f3bee6521ba2b]: exit status 1
better_docs: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@better_docs, as it is not allowed by constraint master from project github.com/xxx/xxx
bugfix/37-panic-on-err: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@bugfix/37-panic-on-err, as it is not allowed by constraint master from project github.com/xxx/xxx
bugfix/extract_logging_suits: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@bugfix/extract_logging_suits, as it is not allowed by constraint master from project github.com/xxx/xxx.
bugfix/logrus: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@bugfix/logrus, as it is not allowed by constraint master from project github.com/xxx/xxx.
docs/improv: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@docs/improv, as it is not allowed by constraint master from project github.com/xxx/xxx.
docs_examples: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@docs_examples, as it is not allowed by constraint master from project github.com/xxx/xxx.
feature/auth_and_backoff: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_and_backoff, as it is not allowed by constraint master from project github.com/xxx/xxx.
feature/auth_middleware: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/auth_middleware, as it is not allowed by constraint master from project github.com/xxx/xxx.
feature/clieant-stream-chain: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/clieant-stream-chain, as it is not allowed by constraint master from project github.com/xxx/xxx.
feature/client-streaming-chain: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/client-streaming-chain, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/client-unary-chain: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/client-unary-chain, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/client_logging: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/client_logging, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/client_payload_logging: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/client_payload_logging, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/client_retry: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/client_retry, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/generic-loggign: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/generic-loggign, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/logging_zap: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/logging_zap, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/metadata_helpers: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/metadata_helpers, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/new_nicemd: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/new_nicemd, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/opentracing-both: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing-both, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/opentracing_tags: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/opentracing_tags, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/repo-move: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/repo-move, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/tags: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/tags, as it is not allowed by constraint master from project github.com/xxx/xxx
feature/validator-middlewre: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@feature/validator-middlewre, as it is not allowed by constraint master from project github.com/xxx/xxx
goimports-scripts: Could not introduce github.com/grpc-ecosystem/go-grpc-middleware@goimports-scripts, as it is not allowed by constraint master from project github.com/xxx/xxx`

What did you expect to see?
I expected no errors. dep init should've just created a .toml and .lock + a vendor. dep ensure should've just updated the .lock and vendor
What did you see instead?
These errors, saying a dep command failed: `git checkout d0c54e68681ec7999ac17864470f3bee6521ba2b
. This only happened with the package from github.com/grpc-ecosystem/go-grpc-middleware`.
How did you fix it?
I fixed it by clearing the dep cache (i've got a copy of it attached to this issue).
Steps to reproduce

Download the dep cache attached to this issue.
Replace the downloaded cache with your original (make a backup of your old one):
$GOPATH/pkg/dep.
Create a Golang project, using the package from: github.com/grpc-ecosystem/go-grpc-middleware.
Run dep init.

this bug report seems to be related to https://github.com/golang/dep/issues/1682

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


STAR-25093: Add JS message signing example

Adds a message signing example in JavaScript, due to demand on the Developer Slack. Also hopefully having it in more than one language will help others figure out how to do it in their languages too 🤞
Have tested locally and against sandbox. Have replaced the uids and token for configuration with placeholder values. Have intentionally left the request body data pointing at a valid (at least for now) sandbox account so people don't get stuck there.

Looks good, my only worry is having the config in the code as this isn't how anyone would recommend doing it, at the very least have a big disclaimer comment where you've embedded the config saying something like "production code should use environment vars to pass config" and a link to https://12factor.net/config


feat: add perf counter for backup request size

What problem does this PR solve?
add perf counter for backup request size
Checklist
Tests

Unit test

This pull requests add partition's backup request bytes, how about adds an app level counter aggerating all partitions in info_collector.h using marco INIT_COUNTER(backup_request_byte)?

This pull requests add partition's backup request bytes, how about adds an app level counter aggerating all partitions in info_collector.cpp using marco INIT_COUNTER(backup_request_byte);?

good idea :-)


adding file of joseph ki zerbo domaine name

University of Ouagadougou name changed to Joseph Ki ZERBO University, so it's for me to update the domaine univ-ouaga up to here recognized by JetBrains for free licence

@Wendkouny I am sorry, the university website looks suspicious. It lacks significant materials. I cannot verify the authenticity of the domain. I have to close this request without merging.
Please apply for a free educational license with an official document that proves that you are a student. You can do it using the "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.

Okay, I'll report that to the web master of the university and hope they
change the site to make it non suspicious.
Best regards !
       Dieudonné OUEDRAOGO

--------------------------------
_________ IT consultant _______
Mobile and Web Developer
On Fri, Sep 3, 2021, 13:49 Philip Torchinsky @.***>
wrote:

@Wendkouny https://github.com/Wendkouny I am sorry, the university
website looks suspicious. It lacks significant materials. I cannot verify
the authenticity of the domain. I have to close this request without
merging.
Please apply for a free educational license with an official document that
proves that you are a student. You can do it using the "OFFICIAL DOCUMENT"
tab at https://www.jetbrains.com/shop/eform/students.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/12330#issuecomment-912554085, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJANSFMAIFDFCSLDGS3QJM3UADG43ANCNFSM5C7DAK6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Fix multiple async refresh call for same value

BUG DESCRIPTION: If many calls for the same key appear before the value
is calculated, then the same calculation is triggered for each call.

Looks good.  :)


(individual-page-wrapper) pages: add PageWrapper, params type and more

Current dependencies on/for this PR:

main

PR #458   👈

This stack of pull requests is managed by Graphite.

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


Global resource limits

Tell us about your request
The ability to configure resource limits (CPU\GPU) on a global level that will be enforced\applied to all provisioners in the cluster.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
In certain use cases, I need to enable a mix of several CPU and GPU instance types that are configured in separate provisioners (because of different taints that are added to the nodes). Without a global limit for resources, I cannot limit the overall capacity of nodes created by Karpenter in the cluster.
Are you currently working around this issue?
No.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

/remove-lifecycle stale

@njtran have there been any more discussions about this? My understanding is that part of the Karpenter v1 process is to achieve parity with CA and this functionality would be required for that? This is also a significant feature in the context of multi-role cluster operations where there should be central controls in place to support constraining self-service capabilities.

My understanding is that part of the Karpenter v1 process is to achieve parity with CA

I'm not sure that this is 100% correct here. Our goal here isn't necessarily to have 100% parity with CA but to provide a complete set of features and stable APIs that we believe are sufficient for all users to handle their node provisioning and lifecycle handling. Whether there is cross-over with CA or not is somewhat immaterial to whether we decide to scope a feature into GA for Karpenter v1.

This is also a significant feature in the context of multi-role cluster operations where there should be central controls in place to support constraining self-service capabilities

As for multi-role cluster operations, I'm curious how you are thinking about how the self-service aspect of this would work, considering NodePools aren't namespaced at all today. If you have a user that has permission to update a NodePool, then you most likely also have permission to edit or delete other NodePools. Are you thinking that you would have some sort of policy engine in place that would allow you to determine whether someone does or doesn't have permission to do certain things on a certain set of NodePools?
In either case, I could see a policy engine-based solution where you could reject a NodePool being updated or added if you took the sum of all the limits values on various NodePools and then saw that the sum of those limits is beyond what you would allow. In either case, you probably want a selector or namespaced-based approach to sum these limits across these NodePools.

For the multi-role implementation, I'd expect the cluster owner to be able to configure constraints that even users with node pool rights couldn't override; much like how the CA model works today. On top of that I'd expect to layer admission control constraints to manage workloads and pools, but that's not really important in this context.
The most basic model here is for a cluster to be provisioned with a number of complimentary pools and then an upper resource limit to be made up from any combination of nodes.

I guess I'm trying to understand the utility of that. It's not self-service in the sense that you would have a multi-tenant cluster. It's self-service tenancy so you pretty much own the cluster except for the actual stand-up of the cluster. So someone comes in and pre-creates the EKS cluster and pre-installs Karpenter and let you have your way with what kind of instances you can launch. Did I get that right?
I'm also curious if there are AWS control-plane controls over resource totals associated with a particular tag or particular user agent.
There may be ways to solve this at two different levels.

@jonathan-innis yes that is the basic pattern. We're always running multiple pools and some of these overlap, so the current pool level limits aren't sufficient.
In the context of a single cloud we might be able to use cloud controls for this, but as Karpenter is multi -cloud I think this functionality should be Karpenter native.


Some errors on Mac

Hello! I am quite new to VBA but found your profile on SO since I also need to use a specific encoding. However, when I run the module on Mac (on Apple Silicon) with updated Excel I get an issue I don't seem to be able to surpass.
Using the function call:
Dim theString As String
theString = "abcd"
Dim b() As Byte: b = Encode(theString, cpIBM437)

I get stuck at the following line:
Static replacementChars As Collection
If replacementChars Is Nothing Then replacementChars = New Collection

Here, I get the error message that there is a compiling error: the variable isn't optional.
Assuming I'm understanding the syntax of VBA correctly, it is supposed to add a Set:
Static replacementChars As Collection
If replacementChars Is Nothing Then Set replacementChars = New Collection

Using this as an assumed fix, I then get a type error at the line:
SetApiErrorNumber = 0
Looking at other parts of the script, this might be meant to say
SetApiErrorNumber 0
However, after this (again presumed) fix which let's the function continue, I then run into another type error with regards to the iconv() function at the very next line:
irrevConvCount = iconv(cd, inBuf, inBytesLeft, outBuf, outBytesLeft)
Here, I don't really understand what's going wrong. Since VBA isn't very verbose in its error messaging, at least by default, I'm unsure what the cause is – you might have a better idea. Any help would be greatly appreciated – I'm happy to assist with testing if I can, although my schedule is somewhat busy in the coming days. I would in any case like to thank you for creating the software and hope that this is the right way of contacting/reporting these errors. Otherwise, please let me know and I'll redo it some other (better) way.
Best regards,
sjogr3n

Hi @sjogr3n, thanks for raising the issue!
It's funny because I noticed some of the things you brought up a few days ago and worked on a fix which led me down a rabbit hole that overwhelmed me a bit and prevented me from pushing anything in the end. Now you are motivating me to look into it again!
You are absolutely right about the missing Set and about the wrong use of SetApiErrorNumber. I have written a bunch of code there that I forgot to test on Mac because that is always a hassle for me.
I have already looked into the rest aswell, and I think I know how to fix everything, I'll push it as soon as I have time!

Thanks for the response, and thanks for looking further into it! Please let me know if I can assist in testing in any way. Have a nice weekend!

Hi @sjogr3n, I finally got to look into this.
I now pushed an extensive rework of the Encode, Decode and Transcode API wrapper functions (5e20a51) and I hope that should resolve this issue.
Please let me know if the current version still causes issues or if this is now resolved :)

Hi @sjogr3n , any chance you'll get to test the new implementation for your usecase? Did you manage to solve your problem in some way? Are you still working on this? I'd appreciate some feedback, otherwise I'll eventually close this issue :)

Thanks for the info! I'll close it in the meantime :)
If you get to test it eventually that would be great and all feedback is much appreciated!