outstanding read operations don't notice that the underneath fd change

I am not sure if it is a problem but I have been surprised by the result. So I am sharing it here.

Establish a TCP connection.
Submit a IORING_OP_READ on the TCP socket fd.
Detect at the application level that the connection is dead. Close the socket and reopen a new one to create a fresh new connection with the server that ends up with the exact fd value as the previous connection

Expected result:
The pending read operation would notice that the fd is gone and returns back an error.
Result:
io_uring never noticed that the old connection is gone. When data will become available on the new connection, the read operation launched for the previous connection will complete.
I guess that the correct way to handle this situation would be to submit a IORING_OP_ASYNC_CANCEL request but I wish the kernel would be smart enough to cancel the pending operations when a file get closed...

There could be so many things that could have gone wrong or not accounted for!

Keep and internal track of socket fd and check its close state on every call.
use shutdown SHUT_RDWR to make sure closed connection doesn't send/recv
it could be that socket was set to SO_KEEPALIVE
even if its using the same fd the port might be different.
...

Even though people think socket is asynchronous, its not truly asynchronous, there is a slight delay in connection where one or both ends of the connection doesn't know what is happening.
I could be totally mistaken in thinking its not io_uring fault :)

I am not sure if it is a problem but I have been surprised by the result. So I am sharing it here.
1. Establish a TCP connection.

2. Submit a IORING_OP_READ on the TCP socket fd.

3. Detect at the application level that the connection is dead. Close the socket and reopen a new one to create a fresh new connection with the server that ends up with the exact fd value as the previous connection

Expected result:
The pending read operation would notice that the fd is gone and returns back an error.
Result:
io_uring never noticed that the old connection is gone. When data will become available on the new connection, the read operation launched for the previous connection will complete.
I guess that the correct way to handle this situation would be to submit a IORING_OP_ASYNC_CANCEL request but I wish the kernel would be smart enough to cancel the pending operations when a file get closed...

I believe recv(2) works in the same way, it grabs a file ref and the actual file (not a particular fd) will be alive until the request is interrupted anyhow. Same for io_uring registered files, it will keep it alive until unregistered. There is little can be done about it.
The right way is to do shutdown() first, it will cut connection and so any request (including inflight and recv(2)/etc.) will be aborted.

thx Pavel for your suggestion.
FYI, after having read it, I went to look into the WebSocket library that I am using (not my code) to see how it was handling the socket closing.
I have found out that it did call shutdown(SHUT_WR)
I did change that for shutdown(SHUT_RDWR) as you suggested. This could maybe trigger a read completion indicating EOF.
If not, I guess that adding an extra IORING_OP_ASYNC_CANCEL should really solve my issue in the worst-case scenario...

It's hard to tell what you are doing at this point.
You should be using io_uring_prep_shutdown + io_uring_prep_close, at this point it should finishes in success or error. Either case there should be no reason to be calling io_uring_prep_cancel (IORING_OP_ASYNC_CANCEL) since both of those task have completed.
One of the gotcha for shutdown is you need to check if fd is still alive if fd: # do shutdown so you need to track socket fd state, throughout your socket class/application.

YoSTEALTH,
This is a very interesting exchange... My brain hasn't fully made the switch to fully think in terms of io_uring operations. This didn't occur to me to perform the shutdown and close calls through io_uring.
TBH, the effort to complete the transition to io_uring might not be worth the necessary effort. What attracted me to io_uring in the first place was the performance gain that I could get when my connection is in the connected state... Initiating and shutting down the connection represent only a very small negligible part of the whole execution time...
io_uring_prep_cancel might not be necessary but since io_uring operations are made from a library, I suppose that it is a good idea to not make any assumption about how its users are using it and I'll keep it for when it is notified that async reading is not desired anymore.
I am touching wood but I think that I have finally found out my issue. I am using an event loop (libev). Upon receiving the connection error event, the code was: 1. shutting down the current connection and initiating a new connection.
This was leading to the variable containing the read bid being overwritten. What I had to do was give back the control between the shutdown and the reconnection to the event loop so that io_uring completion events generated by shutting down the socket had the opportunity to be processed before moving on to the reconnection..

Joke is socket programing and brain damage go hand in hand :)
If you already had software written using libev, it makes sense to stick with it. Looks like they did add support for io_uring http://cvs.schmorp.de/libev/ev_iouring.c?revision=1.25&view=markup though they should have wrote it on top of liburing
As long as you have access to fd you should still be able to use liburing functions and use libev to submit that sqe
Just to clarify further, you can actually call shutdown multiple times!
As an example say you are a "server"
connection-1 = you recv clients request, you can call shutdown(SHUT_RD) this will stop any more reading.
connection-2 = a new connection/fd/port would be created if clients makes another request.
connection-1 = is still able to send data back to client and you can call shutdown(SHUT_WR) + close.

you have to put yourself in the shoes of a multiplatform library creator. He doesn't want to bring in more dependencies on his users. therefore he took the decision to replicate the boilerplate code. I cannot criticize the decision.
However, because my application was already using the libev lightweight abstraction allowing the application to easily switch backends and I do really value this feature, I did substantially modify libev (using liburing to keep my sanity was one of those changes) to be able to do async i/o over just polling and keep around the option to switch backend.
For your clarification, yes. I already kinda know this stuff. My only problem was that I had to find a way to cancel the pending read when the connection gets closed (either remotely or locally and for the records, my app is a client not a server). Giving back control to the loop between completing the socket close and reopening the connection did the thing. My app has been running for the last 2 days and so far, not a single buffer ha been lost despite hundreds of reconnection!


feat: Add dataflow capture in support bundle and update mqtt common label

Update mqttbroker common label
Add dataflow capture in support bundle
Fix int failure for previous PR

Issue found on service side:

mqttbroker missing common label for aio-mq-fluent-bit pod
dataflow missing common label for aio-dataflow operator
1 pending on response, 2 will be fixed later. before the decision made I will capture them using other label/field

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.
Thank you for contributing to Azure IoT Operations tooling!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production

[ ] It is expected that pull requests made to default or core branches such as dev or main are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.

Basic expectations

[ ] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
[ ] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
[ ] Have all the relevant unit and integration tests pass? i.e. pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set.
[ ] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
[ ] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
[ ] Have you made an entry in HISTORY.rst which concisely explains your user-facing feature or change?

Azure IoT Operations CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).

IT runs


Make file information more prominent in File.tsx

Added a header, icon, and increased the size of the filename on the file page. Also began to customize the page more based on whether you're uploading or downloading. (I think it'll be fine to explain on the download page, that people might also be downloading for you.)

Is this is actually a link to download the file (save to disk)? If so, I don't need to do this if I am a seeder ( I just uploaded the file). And I can't do it if I am still downloading or yet to start downloading.
Or is it just a header?

It's just a header. The terminology here is a bit confusing, as in the app uploading ~= seeding, and downloading ~= leaching, but you are talking about downloading as being the step getting the file out of the browser and onto your hard drive. Would it be worth calling that saving or something? Does it happen automatically once the download is complete?

Agreed on terminology, and I think "saving" is certainly less ambiguous for that step. It does not happen automatically, but I believe the button for doing so appears automatically.
Similarly "Seed" would be more accurate instead of "Upload" for the buttons.

I do wonder if the icons are cementing those approximate relations you mention, and if that is a helpful thing to do? Perhaps they could be moved to the ChannelsList component, where the relations are exact?


Error for uncertified user trying to submit metadata

@milen-sage I think there is a way to programmatically check if a user is certified (there's a REST call that looks promising: https://docs.synapse.org/rest/PUT/user/id/certificationStatus.html). I know some user status items are restricted to admins/governance folks only and this might be the case.
We can follow up with the Synapse team to see if there's a python call for it.

@milen-sage I think there is a way to programmatically check if a user is certified (there's a REST call that looks promising: https://docs.synapse.org/rest/PUT/user/id/certificationStatus.html). I know some user status items are restricted to admins/governance folks only and this might be the case.
We can follow up with the Synapse team to see if there's a python call for it.

From Jordan:

while there is not a helper method for this the API can be invoked e.g.:

response = syn.restGET(f'/user/{user_id}/certifiedUserPassingRecord')
print(response['passed'])

Provided that you have the user's profile id

From Jordan:

while there is not a helper method for this the API can be invoked e.g.:

response = syn.restGET(f'/user/{user_id}/certifiedUserPassingRecord')
print(response['passed'])

Provided that you have the user's profile id

oh nice! @sujaypatil96 and @xdoan where do you see this functionality live?
My first instinct is to

incorporate it as a check on schematic's side when calling the store.py associateMetadata... method
have the method return an error that can be displayed in a user friendly way on the front-end data curator app side

@BrunoGrandePhD this might be relevant when thinking about imCORE SOPs as well (i.e. ensuring users are certified when trying to submit metadata). @ychae had already added language around that in the data ingress docs.

oh nice! @sujaypatil96 and @xdoan where do you see this functionality live?
My first instinct is to

incorporate it as a check on schematic's side when calling the store.py associateMetadata... method
have the method return an error that can be displayed in a user friendly way on the front-end data curator app side

@BrunoGrandePhD this might be relevant when thinking about imCORE SOPs as well (i.e. ensuring users are certified when trying to submit metadata). @ychae had already added language around that in the data ingress docs.

Function from @jaeddy :
synGetCertificationStatus <- function(owner_ids) {
  get_certification_status <- function(owner_id) {
    request <- str_glue("/user/{id}/certifiedUserPassingRecord", id = owner_id)
    res <- list(passed = FALSE)
    try(res <- synRestGET(request), silent=TRUE)
    res$passed
  }
  if (is_vector(owner_ids)) {
    map_lgl(owner_ids, get_certification_status)
  } else {
    get_certification_status(owner_id)
  }
}

Function from @jaeddy :
synGetCertificationStatus <- function(owner_ids) {
  get_certification_status <- function(owner_id) {
    request <- str_glue("/user/{id}/certifiedUserPassingRecord", id = owner_id)
    res <- list(passed = FALSE)
    try(res <- synRestGET(request), silent=TRUE)
    res$passed
  }
  if (is_vector(owner_ids)) {
    map_lgl(owner_ids, get_certification_status)
  } else {
    get_certification_status(owner_id)
  }
}

And a python version from @thomasyu888 located here: https://github.com/Sage-Bionetworks/challengeutils/pull/204/files

And a python version from @thomasyu888 located here: https://github.com/Sage-Bionetworks/challengeutils/pull/204/files

Thanks for sending the snippets above @ychae.

My first instinct is to
incorporate it as a check on schematic's side when calling the store.py associateMetadata... method
have the method return an error that can be displayed in a user friendly way on the front-end data curator app side

Yup, that makes sense @milen-sage. We should incorporate the check on schematic side, but instead of associateMetadataWithFiles() we should probably do it in the constructor itself? It's important that all users by Synapse-certified.

Thanks for sending the snippets above @ychae.

My first instinct is to
incorporate it as a check on schematic's side when calling the store.py associateMetadata... method
have the method return an error that can be displayed in a user friendly way on the front-end data curator app side

Yup, that makes sense @milen-sage. We should incorporate the check on schematic side, but instead of associateMetadataWithFiles() we should probably do it in the constructor itself? It's important that all users by Synapse-certified.

Yeah we might even be able to show it at the beginning landing page? like "! you are not certified"

Yeah we might even be able to show it at the beginning landing page? like "! you are not certified"

Tom just submitted code for this feature in the Python client: https://github.com/Sage-Bionetworks/synapsePythonClient/pull/801/files

Tom just submitted code for this feature in the Python client: https://github.com/Sage-Bionetworks/synapsePythonClient/pull/801/files


Help extensions adopt asWebviewUri

Background
Back when webviews first shipped with VS Code, we used  vscode-resource: uris to load local resources. For example:
<img src="vscode-resource:/Users/matb/path/to/cats.gif">

The vscode-resource format however has a few important issues:

It does not specify the scheme used to load the resources.
This prevents vscode-resrouce from being used to read resources from custom VS Code file systems.

vscode-resource: does not work on web.
VS Code has to rewrite vscode-resource uris. This rewriting is not complete.

vscode-resource will also not work with new builds of VS Code that that replace vscode-resource with a new protocol: #97777
We again have to rewrite uris.

To fix these issues, a while back we introduced the Webview.asWebviewUri helper function. This function takes a local uri and returns a uri that can be used inside a webview to load that resource.
However a number of extensions are still using hardcoded vscode-resoruce: uris. We have already added a warning if you use vscode-resource:: https://github.com/microsoft/vscode/issues/81685
Fix
If your extension is using vscode-resource: to load resources—scripts, css, images, ...—switch to instead use the Webview.asWebviewUri function.
If your extension is using vscode-resource: in a content security policy, replace vscode-resource: with Webview.cspSource
Make sure your code always calls asWebviewUri and cspSource when generating html. These values may change between VS Code version, so it is import that you do not cache these values
If you see issues after making these changes, please file a new issue against VS Code and I'll take a look.

wow @mjbvz I see you had a busy Friday night :)
I wonder if it's time we create webview channel in vscode ext. devs slack for you to join and make major announcements on these api changes to keep us in the loop, or some email subscription list.
There must be a better way to do this without so much effort on your part in addition to resolving those issues.
In any case, I appreciate you looking into this and updating us with a recipe to fix it. Thanks!

Appreciate that you took the time to notify so many extensions.
I just looked at the API and found out that asWebviewUri and cspSource were introduced to stable in v1.38. Hopefully that will be helpful for other authors when planning for update.

@dzhavat Yes sorry I got the year wrong when writing the message.
To clarify, here's what is required to get asWebveiwUri to show up as a known API while writing your extension:
If your extension gets vscode.d.ts  from the vscode package

In your package.json set:  "engines": { "vscode": "^1.38" }
Run npm install again (or just the post install script so that the vscode package pulls in new typings)

If your extension gets vscode.d.ts  from the @types/vscode package

In your package.json set:  "engines": { "vscode": "^1.38" }
Also update: "@types/vscode": "^1.38"
Run npm install again to pull in the new vscode.d.ts

In both cases, you should be able to safely update your extension to require VS Code 1.38+ without leaving many users behind. A very high percentage of VS Code users are on either current stable release or the previous release. We on VS Code also only support current release

Hi @mjbvz ,
Just out of curiosity, is there any ETA for #97777 to be released?
I mean, the PR itself has no milestone assigned, an the issue which it fixes (#89038) is still on Backlog.
Thank you

Closing this issue since there's not much more to do from the VS Code side.
All of our examples and documentation should now be using asWebviewUri. Additionally using an old style URI in a webview will generate a warning


Fix eid and dtm being incorrectly added to screen_view and timing context

The EID is currently being added inside the context by accident.

What's the impact of this bug on users?
On 4 Sep 2015 8:53 am, "Josh"<EMAIL_ADDRESS>wrote:

The EID is currently being added inside the context by accident.
—
Reply to this email directly or view it on GitHub
https://github.com/snowplow/snowplow-android-tracker/issues/163.

I believe Screen Views and Timings wont be able to be validated.  I was going to a 0.5.1 bug fix for this as its a pretty bad one.


[Docs] provided link on meshkit/errors/errors.go to see doc command for errorutil gives 404 error

Current State:
On path meshkit/errors/errors.go provided link to see more commands about errorutil gives 404 error
link- https://docs.meshery.io/project/contributing-error

Desired State:
It should not give 404 error

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Can I work on this issue? @Yashsharma1911


Update intersphinx mapping and sphinx-gallery-conf

Links in tutorials should be fixed now. Fixes #2471, #2507

mmh, for some reason the readthedocs build didn't trigger in the last push...

Thanks for the help & comments!


Not Working

this one is not suitable to access mobile Came

i need to access Mobile also ,but in this one not working mobile,
so , kindly give a positive reply


Rename Packet to Equinix Metal in existing Documentation.

This PR  replaces the name Packet with Equinix Metal in all the existing documentation resources under docs/
Fixes: #1060
This PR only takes care of renaming on the documentation side, more work and careful thought process would be required in migrating from Packet terraform provider to Equinix Metal terraform provider, such that there is little or no effect on existing clusters during upgrade.
More specifically, this migration guide will need to be followed
https://registry.terraform.io/providers/equinix/metal/latest/docs/guides/migration_guide_packet

@invidian @rata @knrt10
The user facing documentation is whats visible to the end user more so that any other piece of code/config.
I understand your concern however, making it part of the single PR would have meant a possible delay of getting the user documentation changes merged, which was top priority anyway.
Hence I closed the original issue #1060 , created another issue #1546 that tracks the code and config related changes from Packet to Equinix Metal.
#1545 tries to address #1546


Fix: replace os.getenv with posix.getenv

There was a recent Zig update, removing a lot of the generic std.os.* functions, meaning we have to use std.posix.getenv.
I don't know if this will work on Windows, but from what I can tell, it should actually work.

Change looks good. Thank you for contributing!


Update SwiftSyntax to support Swift 5.7 & Xcode 14.0

Fixes #201
Proposed Changes

Update swift-syntax version to 0.50700.0

@tete1030 Thank you for this. Merging and making a new release now!


Succesful brute force attack

I was successfully able to perform a brute force attack of seed.

@pk74 Could you explain more about the detail of the attack? How can you execute it and what is the result?. Currently, our wallet following BIP-39 so it means that the complexity of brute-force attack is the same as BIP-39 passphrase be cracked

The attack was very simple i generated few keys which were related to my
key!
It was a complex process.
But my start was simple
I had my key i just changed a word and i was in another account. I knew how
a key is created and the last word is checksum but some how it went right.
So this was the base to create few more keys.
If you want to simulate the same
Try creating keys with 1028 wordlist with a program to match the checksum.
You will succeed very easily.
On Fri, Jun 5, 2020, 12:27 PM Steve Duong<EMAIL_ADDRESS>wrote:

@pk74 https://github.com/pk74 Could you explain more about the detail
of the attack? How can you execute it and what is the result?. Currently,
our wallet following BIP-39 so it means that the complexity of brute-force
attack is the same as BIP-39 passphrase be cracked
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KyberSwap/android-app/issues/109#issuecomment-639295939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOLCFHGS3OZHQCNBAXMT6ZTRVCJNHANCNFSM4NAEDUKA
.

@pk74 your process looks like creating a new wallet (it already built-in app), you have to try 2^128 times to generate a new key that collision with existing and the algorithm was proved safe


Adding Features

How would I go about adding my own offsets and using them to make a RCS (Recoil Control System)
I have no idea how to use manual mapping so this is all new to me.

Would I use like hazedumper to get offsets can I even use offsets?

https://github.com/a2x/cs2-dumper/

https://github.com/a2x/cs2-dumper/

I tried that it didn't work


Attempting to merge public master

$ git checkout recogni
$ git rebase master
$ git checkout -b brett/dev/master_merge
...tweak some files
$ git commit ...
$ git push origin brett/dev/master_merge
Tested to verify functionality.
Not 100% sure this is proper sequence.   This PR cannot be automaticly merged.

hmm wellll ...
we are gonna have to force merge the branch b/c it was rebased so there will be conflicts.


Added missing modules  'react-addons-update' and 'react-addons-css-transition-group'

When I tried to build and run the latest react-toolbox docs it failed due to missing react-addons-update and react-addons-css-transition-group
lib/tabs/Tabs.js had been updated at some point but not rebuilt.

Can you release patch with this fix? this breaks projects which uses react-toolbox.
Thanx

Sure


Unable to get metric-server running on minikube: unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"

Installed metric-server and edited the metric-server-deployment.yaml to be
command:
- /metrics-server
- --kubelet-insecure-tls
- --kubelet-preferred-address-types=InternalIP

Now after deploying the yaml, when i saw the log on the metric server, returns me the below ,
I0709 20:46:19.227480       1 serving.go:312] Generated self-signed cert (apiserver.local.config/certificates/apiserver.crt, apiserver.local.config/certificates/apiserver.key)
I0709 20:46:20.019419       1 secure_serving.go:116] Serving securely on [::]:443
E0709 20:46:50.026338       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:47:20.012837       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:47:50.012634       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:48:20.018062       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:48:25.385831       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/coredns-fb8b8dccf-rgw2r: no metrics known for pod
E0709 20:48:25.385873       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/coredns-fb8b8dccf-h7mpl: no metrics known for pod
E0709 20:48:25.385879       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/kubernetes-dashboard-d7c9687c7-bzmbh: no metrics known for pod
E0709 20:48:25.385882       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/kube-scheduler-minikube: no metrics known for pod
E0709 20:48:25.385886       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/kube-proxy-sjvbt: no metrics known for pod
E0709 20:48:25.385889       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/kube-apiserver-minikube: no metrics known for pod
E0709 20:48:25.385892       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/kube-controller-manager-minikube: no metrics known for pod
E0709 20:48:25.385895       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/etcd-minikube: no metrics known for pod
E0709 20:48:25.385898       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/kube-addon-manager-minikube: no metrics known for pod
E0709 20:48:25.385901       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/storage-provisioner: no metrics known for pod
E0709 20:48:25.385904       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/metrics-server-7c75b846d7-n7l57: no metrics known for pod
E0709 20:48:50.011607       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:49:20.014409       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:49:50.010978       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 20:50:20.015859       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:12:20.141479       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:12:50.139621       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:13:20.135741       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:13:50.131265       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:14:20.134107       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:14:50.133109       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:15:20.135469       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:15:50.139727       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:16:20.132495       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:16:50.140797       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:17:20.134256       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:17:50.135647       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:18:20.140981       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:18:50.135625       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:19:20.141984       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:19:50.130230       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:20:20.139924       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:20:50.139738       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:21:20.137848       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:21:50.130790       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:22:20.135447       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:22:50.141213       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:23:20.136766       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:23:50.137981       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:24:20.141322       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:24:50.136991       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:25:20.136083       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:25:50.133412       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:26:20.135417       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:26:50.134275       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:27:20.134628       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:27:50.134141       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:28:20.138379       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:28:50.135268       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:29:20.140689       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:29:50.131130       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:30:14.494165       1 reststorage.go:128] unable to fetch node metrics for node "minikube": no metrics known for node
E0709 21:30:20.139412       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"
E0709 21:30:50.132132       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"

Can someone help me here?

Hi
Did you resolved the problem ? I encountered the same issue . and don't know how to solve it .
following is my error log :
E0723 02:50:10.459125       1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:minikube: unable to fetch metrics from Kubelet minikube (<IP_ADDRESS>): request failed - "403 Forbidden", response: "Forbidden (user=system:anonymous, verb=get, resource=nodes, subresource=stats)"

the same, :(
why metric-server using system:anonymous to communicate with kube-apiserver or kubelet?

same

I had resolved this issue . but i don't know yours issue is the same with me . but you can try . As i know ,minikube now use heapster replaced metric-server . so you should disable metric-server ,and enable heapster . then reinstall minikube .then kubectl top command can use.


Bump identity-oauth-addons version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/8818046367

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/8818046367
Status: success


Text describing Sections in Documentation Generator page inaccurate

Andre Artus reported this on 2013-08-07T01:30:24Z
Transferred from https://issues.dlang.org/show_bug.cgi?id=10769
CC List

Nick Treleaven (@ntrel)

Description
The text describing Sections in Documentation Generator page (http://dlang.org/ddoc.html) is not accurate.

> Sections

> The document comment is a series of Sections. A Section is a name that is the first non-blank character > on a line immediately followed by a ':'. This name forms the section name. The section name is not case > sensitive.

1. A section is not a name. It has a name (except when it doesn't). May I propose:
" A section is a block of text that is given special meaning by the document generator based on either position or a{n} [predefined?] (identifier|name|label|keyword). Details of each kind of section follow"

2. A name can be more than one character. I believe all the standard sections have names longer than 1 character.

3. Some sections do not end their identifiers with a colon (':') to wit "Escapes=".

4. The wording leaves the impression that arbitrary named sections are possible, is this the case? Or are the named sections predefined (i.e. those listed as standard and special sections)?

nick (@ntrel) commented on 2022-08-07T16:34:06Z
> 3. Some sections do not end their identifiers with a colon (':') to wit "Escapes=".

That seems to be the only one.
https://github.com/dlang/dlang.org/pull/3367


Keypad input integration

Hi! I have been using the 2048 app with Zephyr RTOS on a board with keypad buttons.
In order to make it work, I had to add an object group (lv_group_t ), as mentionned in LVGL Readme . Then I put the 2048 button matrix in it:
lv_group_add_obj(btn_matrix_group, game_2048->btnm);
and then link it to the keypad input object:
lv_indev_set_group(lvgl_input_get_indev(lvgl_keypad), btn_matrix_group);
The whole commit is here.
Do you think it could be missing in your lvgl port too?

hi,
You need to register your input device. For 2048 games, you need to register keypads:
static lv_indev_drv_t keypad_driver;
lv_indev_drv_init(&keypad_driver);      /*Basic initialization*/
keypad_driver.type =LV_INDEV_TYPE_KEYPAD;                 /*See below.*/
keypad_driver.read_cb =you_read_cb ;             /*See below.*/
/*Register the driver in LVGL and save the created input device object*/
lv_indev_t * keypad_indev = lv_indev_drv_register(&keypad_driver);

Then:
lv_group_t * g = lv_group_create();
lv_group_set_default(g);
lv_indev_set_group(keypad_indev, g);

Reference:

https://gitee.com/weidongshan/lvgl_100ask_course_materials/blob/master/02_程序源码/01_课堂代码/lv_100ask_teach_demos/src/lv_100ask_demo_course_3_3_1/lv_100ask_demo_course_3_3_1.c#L48
https://docs.lvgl.io/8.3/porting/indev.htmlhttps://docs.lvgl.io/8.3/overview/indev.html
https://docs.lvgl.io/8.3/overview/indev.html


Test Cases and Code Snippets.

          As far as I know, this repo does not follow point 5 of that guide as no Gherkin or test cases are provided as required. PR#79 was an attempt to remedy this. As per @jlurien "HTML file as part of the documentation is not the way to manage them."

As per API-DocumentationTemplate, code snippets are also encouraged and this commit also provides that.
Originally posted by @questsin in https://github.com/camaraproject/DeviceLocation/issues/79#issuecomment-1625435152
As a provider implementor from 5GFF and Rogers Communications, contributions from our Compliance and Conformance test bed fulfill the minimum readiness criteria w.r.t API test cases and documentation, including in the Gherkin Style.
This can be easily translated to any language and framework of the day. It's just a start, but based on our real-life implementations and inspired by TMForum conformance and compliance tests in the same framework.
It's also self-contained and includes all the bells and whistles, batteries included, and can run anywhere 😀
Suggest we provide these tests covering all major languages, including code snippets of their use.

Discussed during last meeting.
Not to be covered yet for current releases v0.x, but have to be aligned with the outcome of commonalities before v1.0


Move qier222.yesplaymusic 0.2.2 to qier222.YesPlayMusic 0.2.2

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/pull/156289#issuecomment-2146097791

https://github.com/microsoft/winget-pkgs/pull/156289#issuecomment-2146097791

[Policy] Reset Labels


Add ES7 react, redux, javascript snippets from vscode extension

These snippets are ported from vscode-react-javascript-snippets and all seem unique from existing snippets in snippets/javascript/*.json

Good call! I was a little iffy on keeping javascript and typescript in the default language list. The filetype_extend trick above is handy and definitely feels like a better approach. 👍


Serendipity plug: random notes

Sometimes we just need randomness. Commands that may be useful:

Random page
Random page with tag (either using existing tags in the current page, or by asking for a tag)
Random page based on search

Implemented by @m1lt0n https://github.com/m1lt0n/silverbullet-serendipity


Clean up documentation

Describe the problem you're trying to solve
There are a number of little typos, grammar mistakes, and other minor issues throughout the docs. Fixing these mistakes will help readers see that the project is being professionally handled and thoroughly reviewed / used.
Describe the solution you'd like
Correction of the various issues across the README and primary docs (getting started, next steps, etc...)

@Jwilliamsr is this correctly labelled so that @FarukhS52 can get credit for the linked PR?

@bmicklea yes, looks good to me.

@FarukhS52 please assign this issue to yourself otherwise you might not get credit. I can't assign it to you.

Hmmm...ok - can you create a new issue with this in the body:
Describe the problem you're trying to solve
There are a number of little typos, grammar mistakes, and other minor issues throughout the docs. Fixing these mistakes will help readers see that the project is being professionally handled and thoroughly reviewed / used.
Describe the solution you'd like
Correction of the various issues across the README and primary docs (getting started, next steps, etc...)


Improve error when Yggdrasil isn't working

Currently, a user who hasn't added peers to their Yggdrasil config won't get any hint that this is the issue, either from Yggdrasil (out of our scope) or from Terraform (we can improve). This is the current error from our plugin:
grid_network.net1: Creating...
grid_network.net1: Still creating... [10s elapsed]
grid_network.net1: Still creating... [20s elapsed]
grid_network.net1: Still creating... [30s elapsed]
╷
│ Error: failed to get node free wg port: failed to list wg ports: could not send request and all retries done

Suggest: add some reference to Yggdrasil, or even suggest to the user to check that it's running and properly configured with peers.

An initial check was added with a link to the troubleshooting page with yggdrasil and other issues that faced new users.


[Feature] Expose MQTT 5.0 properties on received messages

Motivation
There are very few public GUI MQTT 5.0 clients, this is a very nice one.  However, it appears to just use an MQTT 5.0 library, but doesn't expose any additional functionality over MQTT 3.1  It would be GREAT to see various 5.0 properties/metadata that are available in received messages... either in the GUI, or via the logs / debug console.
Detailed design
When receiving a message via client.on('message', function (topic, message, packet) {  , which is specified in method onMessageArrived in views/connections/ConnectionsDetail.vue, line 1051... very little of the "packet" variable is used.  Only a small portion of the map is extrapolated, and stored in some data structure called SubscriptionModel: topic, qos, and optional alias, retain bit, and colour.  Similarly, the standard message bits and pieces are extracted and stored in the type MessageModel (line 156 of types/global.d.ts), specifically:
  interface MessageModel {
    id?: string
    createAt: string
    out: boolean
    payload: string
    qos: QoS
    retain: boolean
    topic: string
    color?: string
  }

In the MQTT.js library, the message object/packet you get from the broker has a bunch of cool 5.0 stuff:  (https://github.com/mqttjs/mqtt-packet#publish)
{
  cmd: 'publish',
  messageId: 42,
  qos: 2,
  dup: false,
  topic: 'test',
  payload: Buffer.from('test'),
  retain: false,
  properties: { // optional properties MQTT 5.0           <------------- new in 5.0
      payloadFormatIndicator: true,
      messageExpiryInterval: 4321,
      topicAlias: 100,
      responseTopic: 'topic',
      correlationData: Buffer.from([1, 2, 3, 4]),      <---- useful!
      userProperties: {                           <---- very useful!!
        'test': 'test'
      },
      subscriptionIdentifier: 120, // can be an Array in message from broker, if message included in few another subscriptions
      contentType: 'test'
   }
}

It would be great if this additional metadata and user properties are displayed or at least visible somewhere..?
Thank you!!

@aaron-613 Hey! 👋
Thank you for your super careful explanation and suggestions, I find your suggestions very useful and we will implement them in future versions.

Hello @ysfscream and @oceanlvr ..!  Thank you for the responses, and apologies for the delayed reply.
That is super excellent to hear that you plan to support the new MQTT 5.0 properties / metadata.  I was planning to try to hack/update the code myself, just to see if I could get it working, but I do not know JS that well.
I'm really excited to try this when it's available... as far as I know, you're the only open-source project that specifically would support 5.0 functionality.  I used to use Eclipse Paho JS utility (now gone: https://www.eclipse.org/paho/clients/js/utility ) but that was only 3.1.1, and also the HiveMQ test client is ok (http://www.hivemq.com/demos/websocket-client/) (also only 3.1), but yours is much prettier and if you have this additional 5.0 capability that would be a game changer.
Please let me know if there's anything I can do to help.  I work for a company called Solace and our broker supports MQTT 5.0.  I'm sure some of our field team would be happy to test this and maybe share with customers.  👍🏼

@aaron-613
Thank you for your support, we are now in the step-by-step combing and design of theMQTT5 attributes that need to be supported, and we can build a design discussion about MQTT5 before we release it, and we are happy to receive feedback from users.

Hey! We are excited about the release of https://github.com/emqx/MQTTX/releases/tag/v1.7.0, which supports adding and displaying User Properties, and more. Thanks and welcome to download.


Document that reader is implemented as a consumer

Motivation
I would have found it helpful to know earlier that a reader is implemented in terms of a consumer.

run cpp tests


Make use of relaxed*() methods in PoolThreadCache.MemoryRegionCache when possible

Motivation:
This is inspired by https://github.com/netty/netty/pull/11960.
We should be able to make use of MessagePassingQueue.relaxedPoll() methods in PoolThreadCache.MemoryRegionCache to reduce the overhead.
Modification:
Use MessagePassingQueue.relaxedPoll(...).
Result:
Less overhead.

Let me close this for now.. Please reopen if you think this is still worthwhile

@normanmaurer @franz1981  Sorry for let this hang... I made a benchmark, and it seems there is no obvious difference between relaxedPoll and poll in this scenario. So it's ok to close this.
The following is the benchmark code, in case anyone is interested:
@Warmup(iterations = 3)
@Measurement(iterations = 3)
public class MemoryRegionCacheBenchmark extends AbstractMicrobenchmark {
    private final PooledByteBufAllocator allocator = new PooledByteBufAllocator();
    private final ByteBuf[] byteBufs = new ByteBuf[259];

    @Setup
    public void setup() throws InterruptedException {
        // Allocate some byteBuf.
        for (int i = 0 ; i < byteBufs.length; i++) {
            byteBufs[i] = allocator.heapBuffer();
        }
        // Release these byteBuf to cache in another thread.
        Thread t0 = new Thread(new Runnable() {
            @Override
            public void run() {
                for (int i = 0 ; i < byteBufs.length; i++) {
                    byteBufs[i].release();
                }
            }
        });
        t0.start();
        t0.join();
    }

    @Benchmark
    @BenchmarkMode(Mode.Throughput)
    public void allocateFromCache(Blackhole blackhole) {
        // Allocate some byteBuf from cache.
        for (int i = 0 ; i < byteBufs.length; i++) {
            byteBufs[i] = allocator.heapBuffer();
            blackhole.consume(byteBufs[i]);
        }
    }

    @TearDown(Level.Invocation)
    public void release() throws InterruptedException {
        // Release these byteBuf to cache in another thread.
        Thread t1 = new Thread(new Runnable() {
            @Override
            public void run() {
                for (int i = 0 ; i < byteBufs.length; i++) {
                    byteBufs[i].release();
                }
            }
        });
        t1.start();
        t1.join();
    }
}


Implement unit_of_account Pallet

We need to implement a new pallet. This pallet draws inspiration from this totem doc
STORAGE

This pallet will introduce a storage called CurrencyBasket which can be a StorageMap of a particular currency to it's issuance which is a LedgerBalance and the weight(w) that will be calculated.

This pallet will also introduce another storage called Neer(Nominal Effective Exchange Rate) which is the actual Unit of Account and which will be a StorageValue

This pallet will also introduce another storage for whitelisted accounts that are allowed to send extrinsics to update the basket of currencies maintained

EXTRINSICS

This pallet will introduce an extrinsic for adding whitelisted account

This pallet will introduce an extrinsic for removing whitelisted account

This pallet will introduce an extrinsic for adding a new Currency to the CurrencyBasket storage. When a new Currency is added to the basket/pool, we calculate the  weight(w) for that currency and also re-calculate and update the Neer(Nominal Effective Exchange Rate) for the pallet, as this will change.

This pallet will introduce an extrinsic for removing a Currency from the CurrencyBasket storage. When a  Currency is removed from the basket/pool, we re-calculate and update the Neer(Nominal Effective Exchange Rate) for the pallet, as this will change.

TODOS

[x] Add related storages as explained
[ ] Add related extrinsics as explained
[ ] Write Tests
[ ] Benchmark Extrinsics

Here is a table of test data:
Weighting per currency = Inverse Issuance / Total Inverse Issuance
Unit of Account per currency unit = Price / (100 * Unit of Account)

Symbol
Total Issuance
Inverse Issuance
Weighting per currency
Price
Weight adjusted price (for Unit of Account calc only)
Unit of Account per currency unit

CNY
203080000000000
0.00000000000000492417
0.000693859246235965
$0.14
0.0000978362008771359
0.00261216547787458

USD
15646926171000
0.00000000000006391032
0.009005534645313300
$1.00
0.0090055346453133000
0.01852560865275010

EUR
12141252300000
0.00000000000008236383
0.011605799158427800
$1.08
0.0125213275644432000
0.01998700917578100

JPY
1381664000000000
0.00000000000000072376
0.000101984951280195
$0.01
0.0000009335163936936
0.00016957363967336

GBP
2889575000000
0.00000000000034607165
0.048764588469100100
$1.23
0.0599569675118472000
0.02277758002272410

KRW
4147954000000000
0.00000000000000024108
0.000033970708384326
$0.00
0.0000000276252556365
0.00001506517524051

INR
163700230000000
0.00000000000000610873
0.000860774207376494
$0.01
0.0000113059188514640
0.00024332632914309

HKD
14816427000000
0.00000000000006749266
0.009510318224872960
$0.13
0.0012266664811812900
0.00238948294268190

CAD
2623583000000
0.00000000000038115813
0.053708586968889400
$0.71
0.0379834314115889000
0.01310155834163480

TWD
46610991000000
0.00000000000002145417
0.003023083884348220
$0.03
0.0000999863125741122
0.00061272110475324

AUD
2164200000000
0.00000000000046206450
0.065109017524073500
$0.61
0.0394104957988599000
0.01121355304909310

BRL
6748881540000
0.00000000000014817270
0.020878857465558600
$0.19
0.0039026380942576900
0.00346277310273300

CHF
1074324000000
0.00000000000093081789
0.131160558384249000
$1.02
0.1340108806726950000
0.01892819885136210

RUB
50622900000000
0.00000000000001975391
0.002783501848483590
$0.01
0.0000364605586142105
0.00024266340635466

THB
20862030000000
0.00000000000004793397
0.006754325237074240
$0.03
0.0002054292610286960
0.00056344667484354

SAR
1948798000000
0.00000000000051313682
0.072305562570158500
$0.27
0.0192247009959278000
0.00492561394251128

AED
1693700000000
0.00000000000059042333
0.083195923555293000
$0.27
0.0226502222965908000
0.00504362637293833

SGD
656021000000
0.00000000000152434145
0.214793330892761000
$0.70
0.1496416541090850000
0.01290637242158680

MYR
1961429700000
0.00000000000050983219
0.071839911328761800
$0.23
0.0164437464095326000
0.00424040627464005

MXN
10756098566000
0.00000000000009297051
0.013100376020261900
$0.04
0.0005215518782401990
0.00073754111892977

TRY
2668539727000
0.00000000000037473679
0.052803761660318700
$0.15
0.0077898346674402500
0.00273297628769263

VND
9211848050000000
0.00000000000000010856
0.000015296489364650
$0.00
0.0000000006472876744
0.00000078393138820

SEK
3757952000000
0.00000000000026610239
0.037496204242523500
$0.10
0.0036834625288696500
0.00181987448264219

PLN
1557781600000
0.00000000000064193851
0.090454872316889500
$0.24
0.0213682357059139000
0.00437632116599172

Total Inverse Issuance

Unit of account (sum of all)

0.00000000000709678201

0.5397933308126690000

The storage should contain:
Symbol (up to 7 alpha numeric)
Total Issuance
Price
Unit of Account per Currency Unit
In other storage store the Unit of Account as a simple value.
Since we normally use u64 the floats should be converted for storage by multiplying by 1_000_000_000_000_000_000


Missing 32 x 8, 32 x16 sizes

Also abaility to specify "full screen".

@riknoll do we plan to add these? If not please close this issue.


Broken link

Fixed the link to https://code.msdn.microsoft.com/SharePoint-2013-workflow-41e5c0f9

Q
A

content fix?
yes

New article?
no

Related issues?

What's in this Pull Request?
Fixed the link to https://code.msdn.microsoft.com/SharePoint-2013-workflow-41e5c0f9
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/general-development/how-to-build-and-deploy-workflow-custom-actions.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.

thx @PiotrekKrakowiak, appreciated.


Nested footnotes or references no longer open!

An example here:
https://myst-tools.org/docs/mystjs/quickstart-myst-markdown#links-cross-references

This is particularly sad that this is no longer working in the spec documentation!

This is fixed by an update to the dependency.


Compact Machines - Ghost Block issue

SpongeForge: 3716
Compact Machines: b267
Grief Prevention: 662
I originally thought this might be a spongeforge issue but after testing further it only seems occur inside griefprevention claim areas
Essentially a ghost block is being left behind when trying to use the compact machine projectors to create blocks.
Full details are listed here:
https://github.com/SpongePowered/SpongeForge/issues/2762

This was annoying me too, but I managed to make it work.
The fieldprojectors has to be able to break the blocks used for the recipes.
When it's crafting a "crafting hologram" block is placed for rendering the crafting animation. This block should break after the animation is done, though.
So, you have to add both of those tot he blacklist.
block-break="compactmachines3:tileentityfieldprojector","compactmachines3:tileentitycraftinghologram"]

GP <IP_ADDRESS>9+ requires SpongeForge 7.1.6 RC3610+(Or SpongeVanilla 7.1.6-RC156+). As of this post, SpongeForge 7.1.6 RC3616(Or SpongeVanilla 7.1.6-RC156) is what we recommend using, and like always the latest GP version available.
You are 27 builds behind on GP, and the version of GP you are using does not work correctly on newer Spongeforge builds.

@kencinder Apologies, seems i had an old http://files.minecraftforge.net/maven/me/ryanhamshire/griefprevention/ link bookmarked, i'll try version 689


Type-safety with ts-rest

Referrence source: https://github.com/ts-rest/ts-rest/blob/main/libs/ts-rest/fastify/src/lib/ts-rest-fastify.ts

Could considering refactoring the repo to hono, which seems to be faster and already have an adapter for both ts-rest and tRPC


build: Update Github workflows

Create cleanup-cache.yml
Switch build to Yarn
Update continuous-deployment.yml

Bump actions/checkout
Switch to --immutable with yarn (this is the new command)
Fix deprecated set-output command

Add heap memory management
Update continuous-integration.yml

Use a consistent runner
Fix set-output issues
Switch to setup-node

Update lint-pr.yml
Update repolinter.yml
Update cleanup-cache.yml
Update codeql-analysis.yml
Create dependabot.yml
Update dependabot.yml
Update .dockerignore
Update Dockerfile
Remove accidental --immutable
build: test large builders
Add setup functions to CodeQL
Update codeql-analysis.yml
Delete local setup-node
Update continuous-integration.yml
Change to larger runners

@TimoGlastra please see this as an attempt to fix the merge conflicts in #1428

Codecov Report

Merging #1500 (db66068) into main (002be4f) will decrease coverage by 4.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1500      +/-   ##
==========================================
- Coverage   85.79%   81.78%   -4.02%
==========================================
  Files         943      943
  Lines       22588    22588
  Branches     3685     3685
==========================================
- Hits        19380    18473     -907
- Misses       3200     4108     +908
+ Partials        8        7       -1

see 27 files with indirect coverage changes

Thanks @ryjones ! Could you fix the prettier errors?

done - @hyperledger/aries-framework-javascript-committers thoughts?


update README.md in obstacle avoidance planner

Description
translate README.md in English
Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read pull request guidelines
[ ] Code follows coding guidelines
[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the guidelines.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@TakaHoribe I just translated README.md to English, and add "Comparison to other methods". I'm not sure if I explained well.


fix(versions): update Activiti/activiti-cloud-example-chart-modeling versions into master

UpdateBot pushed helm dependency: activiti-cloud-modeling to: 7.1.71

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-modeling 7.1.71

 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.jenkins-x-bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


enquiry about a difference between the paper and the code implementation

Thanks for your great work!
I have a question related to the derivation of $\sigma_t$ and $\alpha_t$.
As stated in Equation (24) of the paper, the coefficient of $\epsilon_t$ is $\frac{{\sigma_t}^2}{\alpha_t}$. However, in the code implementation,
alpha_vec = 1./np.sqrt(1+emlv_sq)
sigma_vec = 1./np.sqrt(1+np.exp(2*lambda_vec_ext))
data_err_vec = (sigma_vec**2)/alpha_vec

it seems that the alpha_vec and sigma_vec here do not correspond to the definition of $\sigma_t$ and $\alpha_t$ in Equation (24).
Could you please explain the underlying reasons of the code implementation? Does it share the same intuition with the original paper?
Looking forward to your reply!

Hi RacerK,
$\lambda_t = \log{(\frac{\alpha_t}{\sigma_t})}$ is the 1/2 of log-SNR as in line 155.
emlv_sq is $\exp{(-2\lambda_t)} = \frac{\sigma_t^2}{\alpha_t^2}$ as in line 238.
Thus $\frac{1}{\sqrt{1+\text{emlv sq}}} = \frac{1}{\sqrt{1+\text{emlv sq}}} = \alpha_t$.
$\frac{1}{\sqrt{1+\exp{(2\lambda_t)}}} = \sigma_t$.


add support for cortex

moving forward we want to be able to support using both metrictank and cortex as a backend TSDB.
This allows us to continue to use tsdb-gw for handling auth, then allow metrics and queries through to either backend.

cortex expects a "X-Scope-OrgID" header with requests. We should set this orgId to a HostedMetrics instance id, retrieved from grafana.com.
Users currently authenticate via basicAuth, where the username is 'api_key' and the password is a grafana.com api key.  We need to change this so that the username is the instance name instead.
When authenticating the user, we just need to make a call to
curl -s -H "Authorization: Bearer <API_KEY>" https://grafana.com/api/hosted-metrics?name=<name>

using the apiKey provided by the user to authenticate.
If the key is valid, a 200 response will be returned, else a 401 error will be returned.
If the instance name is valid, the response json will have an array "items: []" with an item in it.  If the array is empty, then the user does not have an instance with the request name and we should reject the auth attempt.
Response for valid instance
statusCode=200
{
  "items": [
    {
      "id": 29,
      "orgId": 5000,
      "orgSlug": "grafana",
      "orgName": "Grafana Labs",
      "clusterId": 2,
      "clusterSlug": "us-east",
      "clusterName": "us-east",
      "name": "hg",
      "url": "https://tsdb-5000-hg.hosted-metrics.grafana.net",
      "description": null,
      "createdAt": "2017-04-25T21:59:43.000Z",
      "createdBy": "dcech",
      "updatedAt": null,
      "updatedBy": "",
      "links": [
        {
          "rel": "self",
          "href": "/hosted-metrics/29"
        },
        {
          "rel": "org",
          "href": "/orgs/grafana"
        }
      ]
    }
  ],
  "orderBy": "name",
  "direction": "asc",
  "links": [
    {
      "rel": "self",
      "href": "/hosted-metrics"
    }
  ]
}

response when instance doesnt exist
statusCode=200
{
  "items": [],
  "orderBy": "name",
  "direction": "asc",
  "links": [
    {
      "rel": "self",
      "href": "/hosted-metrics"
    }
  ]
}

response when apiKey is invalid
statusCode=401
{
  "code": "InvalidCredentials",
  "message": "Token could not be parsed"
}

@tomwilkie @DanCech

That will work, since I have to update the API anyway to discriminate between MT and cortex instances we can also easily add a dedicated endpoint to make it easier to handle the result in tsdb-gw

@jtlisi mentioned he was working on this.

@woodsaj Working on the new workflow. One question, if an admin user queries the endpoint. If two orgs have a instance with the same name there is no way to specify which backend to set the header for. Also why can't we use the instance Id as the user in basic auth?

Also why can't we use the instance Id as the user in basic auth

If that makes it easier to implement, i am all for it.


Doubts regarding installation of SkyAPM-php agent

I am new to skywalking and am trying to install the Skywalking php agent. i am following the given document in the SkyAPM-php-sdk. However after cloning the repository when i try to execute the command - " phpize && ./configure && make && make install " it give the following error :-
/home/indraneel/SkyAPM-php-sdk/src/greeter_client.cc:25:10: fatal error: grpc/register/Register.grpc.pb.h: No such file or directory
#include "grpc/register/Register.grpc.pb.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
I installed gRPC as per the instructions given in the installation documents. I can't seem to find the Register.grpc.pb.h file anywhere. Please can someone help me get a clearer idea of what exactly this file is and where can i find it?

@goerzh

Hi,
Trying to create and install Skywalking PHP agent and I've got exactly the same problem as mentionned by indraneelbaronia. The file "Register.grpc.pb.h" can not be found ...
Searching for this file on the web returns no result and I can't find any way to continue the installation
(RHEL 7.5 / PHP 7.2.17)

Is there a protoc command?

Indeed, there is no "protoc" command found :
configure: creating ./config.status
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing default-1 commands
./config.status: line 1057: protoc: command not found
./config.status: line 1058: protoc: command not found
./config.status: line 1059: protoc: command not found
which: no grpc_cpp_plugin in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
./config.status: line 1060: protoc: command not found
which: no grpc_cpp_plugin in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
./config.status: line 1061: protoc: command not found
which: no grpc_cpp_plugin in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
./config.status: line 1062: protoc: command not found
config.status: executing default-2 commands
mv: cannot stat 'src/grpc/common/common.grpc.pb.cc': No such file or directory
mv: cannot stat 'src/grpc/register/Register.grpc.pb.cc': No such file or directory
mv: cannot stat 'src/grpc/language-agent-v2/trace.grpc.pb.cc': No such file or directory
mv: cannot stat 'src/grpc/register/InstancePing.grpc.pb.cc': No such file or directory
mv: cannot stat 'src/grpc/common/trace-common.grpc.pb.cc': No such file or directory
config.status: executing libtool commands
/bin/sh /tmp/SkyAPM-php-sdk/libtool --mode=compile g++ -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I. -I/tmp/SkyAPM-php-sdk -DPHP_ATOM_INC -I/tmp/SkyAPM-php-sdk/include -I/tmp/SkyAPM-php-sdk/main -I/tmp/SkyAPM-php-sdk -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -I/tmp/SkyAPM-php-sdk/src/grpc -I/tmp/SkyAPM-php-sdk/src  -DHAVE_CONFIG_H  -std=c++11 -Isrc/report/deps/boost -DDEBUG   -c /tmp/SkyAPM-php-sdk/src/greeter_client.cc -o src/greeter_client.lo
libtool: compile:  g++ -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I. -I/tmp/SkyAPM-php-sdk -DPHP_ATOM_INC -I/tmp/SkyAPM-php-sdk/include -I/tmp/SkyAPM-php-sdk/main -I/tmp/SkyAPM-php-sdk -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -I/tmp/SkyAPM-php-sdk/src/grpc -I/tmp/SkyAPM-php-sdk/src -DHAVE_CONFIG_H -std=c++11 -Isrc/report/deps/boost -DDEBUG -c /tmp/SkyAPM-php-sdk/src/greeter_client.cc  -fPIC -DPIC -o src/.libs/greeter_client.o
/tmp/SkyAPM-php-sdk/src/greeter_client.cc:25:44: fatal error: grpc/register/Register.grpc.pb.h: No such file or directory
#include "grpc/register/Register.grpc.pb.h"
^
compilation terminated.
make: *** [src/greeter_client.lo] Erreur 1

Need preinstall grpc_cpp_plugin and protoc
see: github.com/grpc/grpc

okay thanx

Retry last release


[Enhancement] Multiple Damage rolls right click functionality implemented in the Token Action HUD

I'd like to suggest implementing the rick click multiple damage functionality in the Token Action HUD damage buttons, if possible.

I enhanced the GURPS TAH support for this feature.   This is the PR:   https://github.com/Drental/fvtt-tokenactionhud/pull/200


Is PAM_CLOSE_SESSION missing?

Hi @ifreund,
we plan to use dumb_runtime_dir for CRUX upcoming release. Ideally I would want to place it in our common-session file, but it appears that PAM_CLOSE_SESSION(3) instructions are missing. I get an error with every service that uses pam when it tries to deconstruct a session:
❯ sudo echo foo
foo
doas: pam_close_session: Module is unknown

Is this something that can be added to this project?

This seems to be a issue with your PAM configuration, make sure you've spelled pam_dumb_runtime_dir.so properly and your pam.d config files have the correct syntax. Also ensure that pam_dumb_runtime_dir.so is in the correct directory alongside your other PAM modules.

I double checked spelling and pam_dumb_runtime_dir.so is correctly placed in /lib/security, as this is where CRUX stores them.
I haven't had the same problem with rundird.
These are the steps taken to generate a package:
make -C $name-$version PREFIX=""
make -C $name-$version DESTDIR=$PKG PREFIX="" install

Do you see anything wrong that maybe?

Hmm, seems that PAM requires modules to define all functions even if they are a noop:
https://github.com/linux-pam/linux-pam/blob/b872b6e68a60ae351ca4c7eea6dfe95cd8f8d130/libpam/pam_dispatch.c#L102-L105

Should be fixed by 11d0c5215107b9823f88afd364d29eae77582eef. Let me know if that solves your issue and I'll tag a release.

This works perfectly fine over here, thank you!

Thanks for testing, just tagged 1.0.4: https://github.com/ifreund/dumb_runtime_dir/releases/tag/v1.0.4


having trouble completing from cargo crates

Hi, first of all thanks so much for creating racer!
I'm trying to use racer from Emacs with a Cargo project. My understanding is that Cargo dependencies are now supported. However, I've been having trouble with it. As an example, I edited src/main.rs in the racer project itself, added use toml:: to the top level scope of the file and asked Company for a completion. I got this:
Company: Back-end racer-company-complete error "/home/tom/.local/bin/racer exited with status 101" with args (candidates )

If I run racer complete use toml:: from inside that src directory of my Racer repo I see nothing printed and racer exits with a 0 error code.
Completions for std all work just as one would expect, so I think that RUST_SRC_PATH is set up and racer is otherwise happy.

Hi @tomjakubowski, What does your Cargo.toml look like?

Cargo.toml
[package]

name = "racer"
version = "0.0.1"
license = "MIT"
description = "Code completion for Rust"
authors = ["Phil Dawes<EMAIL_ADDRESS>
[[bin]]
name = "racer"
path = "src/main.rs"

[profile.release]
debug = true

[dependencies]
log = "*"
syntex_syntax = "*"
toml = "*"

[features]
nightly = []

Cargo.lock
[root]
name = "racer"
version = "0.0.1"
dependencies = [
 "log 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
 "syntex_syntax 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
 "toml 0.1.20 (registry+https://github.com/rust-lang/crates.io-index)",
]

[[package]]
name = "bitflags"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"

[[package]]
name = "kernel32-sys"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
 "winapi 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
]

[[package]]
name = "libc"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"

[[package]]
name = "log"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
 "libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
]

[[package]]
name = "rustc-serialize"
version = "0.3.14"
source = "registry+https://github.com/rust-lang/crates.io-index"

[[package]]
name = "syntex_syntax"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
 "bitflags 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
 "libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
 "log 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
 "rustc-serialize 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
 "term 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
 "unicode-xid 0.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
]

[[package]]
name = "term"
version = "0.2.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
 "kernel32-sys 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
 "winapi 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
]

[[package]]
name = "toml"
version = "0.1.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
 "rustc-serialize 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
]

[[package]]
name = "unicode-xid"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"

[[package]]
name = "winapi"
version = "0.1.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
 "libc 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
]

Are you using multirust by any chance? If so, you'll need to symlink ~/.cargo to ~/.multirust/toolchains/stable/cargo or the like.
@phildawes: Perhaps the location of the cargo registry could be passed as an environment variable till https://github.com/rust-lang/cargo/issues/1098 is sorted out?

@4xrsJCr9 yes that might be the easiest way. Or maybe racer should interrogate the .multirust directory to back out the directory. (i.e. look in .multirust/overrides and .multirust/default).
(n.b. I'm not sure this is something a cargo lib can support easily without help from multirust)

@tomjakubowski Is @4xrsJCr9 correct about multirust? (Completing toml:: in the racer source works for me.) Thanks!

Yep, I've got multirust installed and that seems like a probable explanation. I'll give it a try with a workaround soon.

I added some multirust support last night. It currently doesn't do overrides, but it should look in the current multirust 'default' cargo directory now. You have to delete your ~/.cargo dir for the new functionality to kick in. Hope this helps!


IE10: required fields error message takes precedence of number type validation

Environment:

jQuery 1.11.0
jQuery Validation 1.13.0
Windows 7
Internet Explorer 10

Minimum test case: http://jsfiddle.net/cvp41zk4/
In IE 10 I've found that a required number field will continue to display "This field is required." instead of "Please enter a valid number." if alpha characters are inserted instead of numeric characters. If I add numbers that exceed min/max rules then the required field error is replaced by the min/max error.
In the minimum test case follow these steps to reproduce:

Click submit to trigger validation
Type "aaa" in the field, notice that the message does not ask you to enter a number, but rather complains that it is required.

I've only observed this behavior in IE10. It seems to work as desired in other browsers including IE8 and IE9.

Is there any headway on this?

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


Enable autoscale policies for gateways

Purpose

Enable autoscaling support for gateway.

Codecov Report

Merging #64 into master will increase coverage by 0.12%.
The diff coverage is 96.66%.

@@            Coverage Diff             @@
##           master      #64      +/-   ##
==========================================
+ Coverage   93.63%   93.75%   +0.12%
==========================================
  Files          27       28       +1
  Lines        1366     1426      +60
==========================================
+ Hits         1279     1337      +58
- Misses         71       72       +1
- Partials       16       17       +1

Impacted Files
Coverage Δ

...g/controller/gateway/resources/autoscale_policy.go
96.66% <96.66%> (ø)

Continue to review full report at Codecov.

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


[Task]: Fix send drawer

Description
Currently the content can be horizontal scrolled, we need to fix that. Details: https://trello.com/c/v26iWPJW
Replace animation by static image as figma design.
Requirements

[ ] Works on Android
[ ] Works on iOS

@amadeu2 Should I set an image instead of the animation as well, to improve the drawer fps?

You right, I've updated the description 👌


Docs: Minor fixes for some misprint in Boosted

Commits can be split of course, but here is what's taken into account:

mixin changes for doc comprehension
tables minor fixes
navbar default border-color value
spacing between nav and form in navbar offcanvas example
third-level list
hide .display-5 and .display-6
spacing for submit buttons in forms
Primary for primary buttons
image overlays in cards look like the v4 one
add links to carousel captions
Carousel doc reorder to get closer to Bootstrap
Vertical center toasts' custom content
Add different variant for close button (without .btn-close)

@louismaximepiton Could you please split it in different PRs so that it will be easier to track the modification in https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/issues/1429?


Determine whether remove "Tough As Nails" and "Serene Seasons" mods

Duo to the mod has a bug that shows a wrong GUI for the thirst and temperature when you travel to different dimensions. Also, the mod has been abandoned to maintenance the mod of version 1.12.2. Now evaluate to drop "Tough As Nails" and "Serene Seasons" mods in our Modpack.
https://user-images.githubusercontent.com/48656764/127853301-fbaabe73-a06e-4ec9-8232-c9af554ac1d7.mp4

I agree that "Tough As Nails" and "Serene Seasons" should be removed.
Apart from the thirst bug, the mod lacks a better way to purify water (e.g. water purification machine), so obtaining purified water requires repetitive manual crafting. Also, the hydration level drops rapidly in nether, so this mod is adding much difficulty in exploring nether without providing a reasonable way to tackle it.
On the other hand, the mod "Serene Seasons" limits crops to be only able to fertile in specific seasons, and each season lasts for 8 in-game days, so it would slow down players' progress in crafting different foods significantly.
Despite several measures that can be taken to ignore the season restrictions (e.g. greenhouse glasses, planting at y < 48), it is still adding too much difficulty in terms of obtaining stable food sources at early game.
"Serene Seasons" mod is also probably one of the reasons causing #6 .

Dangerous ar ma


Feature/roles

Good work! Seems like all the changes will ease deployment procedure, since we destroyed unnecessary groups.
Code is clean from my prospect, so it can be merged.

@jenkins test this please


Adds input_check_tapped

Returns whether an input value crossed a threshold within a duration. Useful for checking “tapped” input on analogue sources such as a Smash attack.

#377

refactor to use constants and move into verb class for ease of config/use


Adding logs to debug why flows are getting stuck in PREPARING state for some usecases

We have seen couple of usecases where executions are stuck in PREPARING state. To unblock these executions, we had to change executor_id to null in database. I am adding these logs to debug the same issue as there was no exception in executor logs for the failure.

Pull Request Test Coverage Report for Build 5184

2 of 7 (28.57%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.006%) to 40.554%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowPreparer.java
2
7
28.57%

Files with Coverage Reduction
New Missed Lines
%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractProcessJob.java
2
52.58%

Totals

Change from base Build 5180:
-0.006%

Covered Lines:
12989

Relevant Lines:
32029

💛  - Coveralls


Merit::MissingLoadProfileError: /var/www/etengine/releases/20160204145936/tmp/etsource/datasets/nl/load_profiles/curtailment.csv is not known. Please add.

https://quintel.airbrake.io/projects/35333/groups/1613093128873467531/notices/1613093123761157710
[GEM_ROOT]/bundler/gems/merit-e26097c7fbb2/lib/merit/load_profile.rb:97 in rescue in read
[GEM_ROOT]/bundler/gems/merit-e26097c7fbb2/lib/merit/load_profile.rb:94 in read
[GEM_ROOT]/bundler/gems/merit-e26097c7fbb2/lib/merit/load_profile.rb:115 in read
[GEM_ROOT]/bundler/gems/merit-e26097c7fbb2/lib/merit/load_profile.rb:82 in load
[GEM_ROOT]/bundler/gems/atlas-8111964f4118/lib/atlas/dataset.rb:195 in load_profile
app/models/api/v3/merit_config_presenter.rb:46 in block in as_json
app/models/api/v3/merit_config_presenter.rb:45 in each
app/models/api/v3/merit_config_presenter.rb:45 in as_json
/gems/activesupport-4.1.5/lib/active_support/json/encoding.rb:34 in encode
/gems/activesupport-4.1.5/lib/active_support/json/encoding.rb:21 in encode
/gems/activesupport-4.1.5/lib/active_support/core_ext/object/json.rb:37 in to_json_with_active_support_encoder
/gems/actionpack-4.1.5/lib/action_controller/metal/renderers.rb:96 in block in <module:Renderers>
/gems/actionpack-4.1.5/lib/action_controller/metal/renderers.rb:39 in block in _handle_render_options
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/set.rb:263 in each_key
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/set.rb:263 in each
/gems/actionpack-4.1.5/lib/action_controller/metal/renderers.rb:36 in _handle_render_options
/gems/actionpack-4.1.5/lib/action_controller/metal/renderers.rb:32 in render_to_body
/gems/actionpack-4.1.5/lib/abstract_controller/rendering.rb:25 in render
/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:16 in render
/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:41 in block (2 levels) in render
/gems/activesupport-4.1.5/lib/active_support/core_ext/benchmark.rb:12 in block in ms
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/benchmark.rb:294 in realtime
/gems/activesupport-4.1.5/lib/active_support/core_ext/benchmark.rb:12 in ms
/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:41 in block in render
/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:84 in cleanup_view_runtime
/gems/activerecord-4.1.5/lib/active_record/railties/controller_runtime.rb:25 in cleanup_view_runtime
/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:40 in render
app/controllers/api/v3/scenarios_controller.rb:24 in merit
/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4 in send_action
/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189 in process_action
/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10 in process_action
/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:20 in block in process_action
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113 in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113 in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149 in block in halting_and_conditional
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149 in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149 in block in halting_and_conditional
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166 in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166 in block in halting
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166 in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:166 in block in halting
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86 in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:86 in run_callbacks
/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:19 in process_action
/gems/actionpack-4.1.5/lib/action_controller/metal/rescue.rb:29 in process_action
/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:31 in block in process_action
/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159 in block in instrument
/gems/activesupport-4.1.5/lib/active_support/notifications/instrumenter.rb:20 in instrument
/gems/activesupport-4.1.5/lib/active_support/notifications.rb:159 in instrument
/gems/actionpack-4.1.5/lib/action_controller/metal/instrumentation.rb:30 in process_action
/gems/actionpack-4.1.5/lib/action_controller/metal/params_wrapper.rb:250 in process_action
/gems/activerecord-4.1.5/lib/active_record/railties/controller_runtime.rb:18 in process_action
/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:136 in process
/gems/actionview-4.1.5/lib/action_view/rendering.rb:30 in process
/gems/actionpack-4.1.5/lib/action_controller/metal.rb:196 in dispatch
/gems/actionpack-4.1.5/lib/action_controller/metal/rack_delegation.rb:13 in dispatch
/gems/actionpack-4.1.5/lib/action_controller/metal.rb:232 in block in action
/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82 in call
/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:82 in dispatch
/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:50 in call
/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:71 in block in call
/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59 in each
/gems/actionpack-4.1.5/lib/action_dispatch/journey/router.rb:59 in call
/gems/actionpack-4.1.5/lib/action_dispatch/routing/route_set.rb:678 in call
/gems/newrelic_rpm-<IP_ADDRESS>/lib/new_relic/rack/agent_hooks.rb:32 in call
/gems/warden-1.2.3/lib/warden/manager.rb:35 in block in call
/gems/warden-1.2.3/lib/warden/manager.rb:34 in catch
/gems/warden-1.2.3/lib/warden/manager.rb:34 in call
/gems/rack-1.5.2/lib/rack/etag.rb:23 in call
/gems/rack-1.5.2/lib/rack/conditionalget.rb:25 in call
/gems/rack-1.5.2/lib/rack/head.rb:11 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/params_parser.rb:27 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/flash.rb:254 in call
/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225 in context
/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/cookies.rb:560 in call
/gems/activerecord-4.1.5/lib/active_record/query_cache.rb:36 in call
/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:621 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:29 in block in call
/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:82 in run_callbacks
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/callbacks.rb:27 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/remote_ip.rb:76 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/debug_exceptions.rb:17 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/show_exceptions.rb:30 in call
/gems/railties-4.1.5/lib/rails/rack/logger.rb:38 in call_app
/gems/railties-4.1.5/lib/rails/rack/logger.rb:20 in block in call
/gems/activesupport-4.1.5/lib/active_support/tagged_logging.rb:68 in block in tagged
/gems/activesupport-4.1.5/lib/active_support/tagged_logging.rb:26 in tagged
/gems/activesupport-4.1.5/lib/active_support/tagged_logging.rb:68 in tagged
/gems/railties-4.1.5/lib/rails/rack/logger.rb:20 in call
/gems/actionpack-4.1.5/lib/action_dispatch/middleware/request_id.rb:21 in call
/gems/rack-1.5.2/lib/rack/methodoverride.rb:21 in call
/gems/rack-1.5.2/lib/rack/runtime.rb:17 in call
/gems/activesupport-4.1.5/lib/active_support/cache/strategy/local_cache_middleware.rb:26 in call
/gems/rack-1.5.2/lib/rack/sendfile.rb:112 in call
/gems/railties-4.1.5/lib/rails/engine.rb:514 in call
/gems/railties-4.1.5/lib/rails/application.rb:144 in call
/gems/railties-4.1.5/lib/rails/railtie.rb:194 in public_send
/gems/railties-4.1.5/lib/rails/railtie.rb:194 in method_missing
/gems/rack-cors-0.2.9/lib/rack/cors.rb:54 in call
/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:572 in process_client
/gems/gctools-0.2.3/lib/gctools/oobgc/unicorn_middleware.rb:13 in process_client
/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:666 in worker_loop
/gems/newrelic_rpm-<IP_ADDRESS>/lib/new_relic/agent/instrumentation/unicorn_instrumentation.rb:22 in call
/gems/newrelic_rpm-<IP_ADDRESS>/lib/new_relic/agent/instrumentation/unicorn_instrumentation.rb:22 in block (4 levels) in <top (required)>
/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:521 in spawn_missing_workers
/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:140 in start
/gems/unicorn-4.8.2/bin/unicorn_rails:209 in <top (required)>
[GEM_ROOT]/bin/unicorn_rails:23 in load
[GEM_ROOT]/bin/unicorn_rails:23 in <main>

Problem arises from Jeroen van der Logt's LES on etmoses beta.

Should be fixed by fb56e041.