Revised Battery Monitoring

Okay so finally here we go..
This PR is regarding https://github.com/PX4/Firmware/issues/2529
I have spent quite some time about the best way to tackle this problem, especially the one that arises from voltage drop of older batteries. I think that the solution I came up with is the best deal between comfort for inexperienced users and experienced users who want to get the last mah out of their batteries.
First off, the flight pilot has (so far) no need to know what kind of battery is powering the system, as  we do not make different calculations or assumptions on this information in the code. Therefore the FC SHOULDN'T make any assumption either. It may be a LiPo powering the system, a car battery or  even a power lead. Therefore I removed the BAT_N_CELLS and BAT_V_LOADDROP parameters.
I chose the remaining battery parameters with the following thought in my mind: The parameters should directly be backed by functionality, i.e. the actual algo of the battery monitoring system. Any helping parameter "translations" can be done by the GroundStation, because an inexperienced user will usually rely on the setup wizard instead of changing parameters directly. The experienced user however will be able to directly tweak the monitoring system using the given parameters.
The new parameters used for battery monitoring are:
BAT_V_FULL - The total full battery voltage.
BAT_V_LOW - The voltage at which the low battery alarm will be triggered.
BAT_V_CRIT - The voltage at which the critical battery alarm will be triggered.
BAT_CAPACITY - The total capacity of the battery.
BAT_PERC_LOW - The percentage capacity left at which the low battery alarm will be triggered.
BAT_PERC_CRIT - The percentage capacity left at which the critical battery alarm will be triggered.
This might seem confusing at first.. why absolute voltage levels for low and critical but percentage values for capacity? I will come back to that during my explanation of the battery monitoring algorithm. The main advantage of these parameters are, that an experienced users who knows what his batteries can handle, can directly include the max. voltage drop under load into the BAT_V_LOW and BAT_V_CRIT parameters, thus saving the hazzle of implementing complex, resource intensive and probably not very robust models of the battery (which would again rely on the type of battery in use).
Inexperienced users should be guided through the setup process by the GS. If they run into problems, they should be directed to a battery guide  explaining how to setup the parameters directly.
Now to the actual battery monitoring system. During coding the algo, I came across two variants, and both are included in the source code (one as comment).
In any case, we want to rely on coulomb-counting, as it will give us a better estimate (as it doesn't suffer from something like drop under load). However if the battery voltage enters critical levels, we want those estimations to "take over".
The coulomb-counting estimation is pretty straight forward and is not elaborated further.
	/* VOLTAGE BASED ESTIMATION - Optimistic Voltage / Discrete Approximation */
	if (voltage < bat_v_crit) {
		bat_status_v = bat_perc_crit;
	} else if (voltage < bat_v_low)	{
		bat_status_v = bat_perc_low;
	} else {
		bat_status_v = 1.0f;
	}

The voltage estimation "in use" is a discrete "optimistic" voltage estimation. This means, that the current voltage is compared against the low and critical thresholds and will then set the battery_remaining variable to the according percentage threshold. A "pessimistic" estimation would set the estimation to just above the next threshold (i.e. for critical instead to bat_perc_crit to 0)
The other possible voltage estimation is the linear approximation. In this case, the voltage will be mapped to the bat_remaining value like this:
(bat_v_full, bat_v_low) -> (1.0, bat_perc_low)
(bat_v_low, bat_v_crit) -> (bat_perc_low, bat_perc_crit)
(bat_v_crit, 0.0) -> (bat_perc_crit, 0.0)
here, the pessimistic case would map the last mapping to constant zero, as technically bat_v_critical is already fully empty. so the algo has a little flaw here.
Below you will find a few graphs illustrating the behavior.
So which of the two should be preferred? This is something that the userbase will have to decide, I personally prefer the discrete version, because it "interferes" less with the coulomb-counting approach.
Neither of the two have been fully flight tested, however a slightly modified version of the discrete one has, and both should work fine.
If anybody is interested in the MATLAB script simulation that creates the graph below (the simulation should be clearly distinguishable from the real data plots), I can post this as well.
That is it for now, I hope I didn't forget anything..
EDIT 1: I'm aware that the code is not optimized in any way, that is on purpose. First of, I hope the optimizer will do its work and secondly, this is much better for illustrating the algo.

Although number of cells doesn't make sense in all cases. It allows you to put in per-cell voltage defaults which will work for lipos as good defaults (since that is a very high use case). And then the user can just update cell counts and still use the voltage defaults as is. If your using something odd, you can just set cell count to 1 and adjust all the values yourself.
Also it may make sense to trigger a required setup in QGC. So for example, you could set cell count and/or capacity to default values which indicate not yet set. Then QGC uses that as a trigger for the Power config requiring them to be changed by the user to valid values before first flight.

I see your point, however since it is of no interest to the actual monitoring system I would put the "shadowing" parameters cell count etc to the battery setup of qgroundcontrol, which then translates it to the actual parameters. Also I don't think that it's very common to use batteries with different cell counts in the same UAV.

however since it is of no interest to the actual monitoring system

I think it's of important interest to the flight stack. Good/Bad parameter defaults affect the usability of the overall system. The reason being, most people don't know they need to change defaults in order for the right thing to happen. Since the voltages are defaulted to specific values it will work incorrectly for a decent percentage of users. Unless they realize they need to change the defaults. QGC is not always used. The firmware should be able to stand alone and do the right thing as much as possible.
I'd suggest either one of these:

Use a cell count parameter which is not set as a trigger and then voltages which are appropriate for a single lipo cell.
Set voltages to "not set" by default.

That way you are not getting strange results by accident. And then QGC can also use these are triggers for required setup on Power config.

Right, the second option is basically how i intended it to be. My main part was to think of a suitable monitoring algo, I didn't yet think about how to achieve good default behaviour.
Point stilll is, that - either way - the firmware has no direct advantage of knowing the cell count, it just adds more terms to the equation. However sensible default values are of course required and since it would be as fatal to assume a wrong cell count as it would be to assume a wrong empty voltage, I'd say: set the voltages to unset and force their configuration either by a GS wizzard or direct parameter setting.
I will make another commit to update the parameters tomorrow. Any thoughts on the actual monitoring algo?

Since you are removing parameters this is a breaking change to the parameter specification. When that happens you need to bump the SYS_PARAM_VER default. This signals QGC of the breaking change. QGC side is not fully implemented, but it's a good practice to get started with.

I'm happy to merge this if you bring the cell count back. There is no need to make it harder for users, and they almost never change the voltage thresholds, but they have to change the cell count for a number of airframes.
This is also important for smart batteries (which we already support) so that we can set the threshold correctly based on the reported number of cells. Not setting the cell count results in missing info.

Could you summarize again in one sentence what you feel the main improvement here is? This looks largely equivalent to what is in place, plus configurable percentages for warn and critical.

@DonLakeFlyer Thanks for the advice :+1:
@LorenzMeier really? I searched through the project for source that actually uses the BAT_N_CELLS parameter, but couldn't find any except the estimation method which just uses it as a multiplication factor. I can of course bring it back if you need it - in this case would you like all the other parameters to be "per cell" as well?
The main improvement indeed is little, I opted for a simple model with maximum flexibility. The old voltage drop estimation was incomplete in the sense that it was neglecting hysteresis properties of the battery, leading to way to early battery warnings. This solution puts more focus on the coulomb-counting approach, avoiding this problem.
I will put more effort into developing a better monitoring system - this PR is mostly about making it work for everybody (by not forcing an incomplete battery model on them).

I'm happy to merge this if you bring the cell count back.

I agree since as Lorenz says, for most users they will just need to tweak cell counts. If would set the cell count to 0 as default. This can then trigger QGC to require that param be set as required. Then the code doesn’t run if cell count and mAh are not set. This prevents bad information if they haven’t been changed. I’d probably default mAh to 0 as well as the not set indicator as well instead of -1.

On Jul 23, 2015, at 12:58 AM, Lorenz Meier<EMAIL_ADDRESS>wrote:
I'm happy to merge this if you bring the cell count back. There is no need to make it harder for users, and they almost never change the voltage thresholds, but they have to change the cell count for a number of airframes.
This is also important for smart batteries (which we already support) so that we can set the threshold correctly based on the reported number of cells. Not setting the cell count results in missing info.
—
Reply to this email directly or view it on GitHub https://github.com/PX4/Firmware/pull/2591#issuecomment-124011493.

Yes, I see how having a cell parameter is more comfortable, however I am convinced that everything that makes configuration more comfortable should be part of the configuration in the GS, and that the px4 parameters should strictly back the algorithm which they are used in.
However if Lorenz says that he has some code for smart batteries that actually relies on the number of cells - that's a different story.
I have added 3 Commits.
Commit 1 fixes the parameters as suggested (i assume "not set" is achieved by setting to zero)
Commit 2 brings back the cell count parameter but the voltage parameters are still for total voltage
Commit 3 changes the voltage parameters to be per cell.
NOTE: bypassing coloumb-counting is still achieved by setting capacity to -1, not 0 and default cell count is still 1.
Please let me know if you want any further changes / manual optimization if you think that the optimizer won't take care of it.

however I am convinced that everything that makes configuration more comfortable should be part of the configuration in the GS, and that the px4 parameters should strictly back the algorithm which they are used in.

That is way wrong. You should not assume that a ground station even exists and design your parameters for ease of use when all you have is parameter editing capability. Even if you have QGC, the majority of parameters have no custom ui on top of them and are only available through the parameter editor interface. If parameters (there are 500+) were not designed with end user usability in mind then I'd spend the rest of my life writing custom ui to make the flight stack usable. That is not feasible, nor does 100 different custom configuration screens provide end user usability. A parameter is an end user facing thing and requires end user facing thought put into it towards usability. You need to consider that end user to not be a developer. If we keep thinking that all parameters are just developer only facing knobs, the PX4 Flight Stack will never be more than something usable by rocket scientists only.

Okay if that is the general design idea behind parameters I'll stick to that. My impression was just based on my first experience with the px4 flight stack - which would have been impossible to configure without the calibration wizards of the GS. The second thought was that userfriendly parameters lead to unnecessary calculations in the flight stack, which is just adds extra load to the RT system.. however i guess that was not a valid thought because the conversion technically just needs to be run once, thus not affecting the timing / performance of the RT system.

do not merge, latest commit seems not to be working, investigating now.

The latest commit fixes a some bugs, adjust the parameters as discussed and will also ensure  that battery parameters are updated when they are changed. It should be all good now, I will do some flight testing tomorrow and probably write a guide about checking voltage and current scaling parameters as well as tweaking the parameters. If I have time I might also look into updating QGC to deal with the new system.

That would be awesome!

On Jul 23, 2015, at 3:31 PM, orangelynx<EMAIL_ADDRESS>wrote:
If I have time I might also look into updating QGC to deal with the new system.

Passed flight testing.

Reviewed. A little sad to see the voltage drop feature go because it worked for me but I agree that setting the capacity should actually be encouraged.

@banisiesta interesting to see that voltage drop estimation worked fine for you... how much drop did you encounter? When I come to revising the Power screen of QGC, I'll probably add a "fixed voltage drop" field there.
@LorenzMeier From my side its all clear for merge, or do you want to wait till a PR for QGC is ready as well?

@orangelynx I seemed to get less "false positives" if I increased the paramter BAT_V_LOAD_DROP. This is the only thing I remember.

What was the state of the matching QGC PR?

It’s not there. Has this pull gone through? If so I probably have enough time to put in a version check to disable battery config on new version.

On Aug 17, 2015, at 3:50 AM, Lorenz Meier<EMAIL_ADDRESS>wrote:
What was the state of the matching QGC PR?
—
Reply to this email directly or view it on GitHub https://github.com/PX4/Firmware/pull/2591#issuecomment-131716465.

No, its still pending and we might need a call to settle the discussion here.

Let me know on gitter if this ever goes through so I can do the version check.

Sorry currently have exams at ETH, so I have absolutely no spare time to work on this.. I will work on it full time starting september 1st.

@orangelynx Did you find some time to work on this?

Closing for now, this needs a wider discussion and a fresh look.

@tumbili unfortunately not. Allthough I had zero problems so far with the modified firmware so far, I'm also doing an internship this semester and didn't find enough time to work through Qt to add the QGroundcontrol view for my revised system.
@LorenzMeier I'm always open to participate in another tackle at this. I hope I could at least show that the current implementation has its issues. I know that you see the ultimate solution in smart batteries, however I doubt that they will experience a breakthrough in the pixhawk user base any time soon.


Upgrade to work with Rails 5 and the latest Stripe API SDK

The latest Stripe API SDK changed how event.data.object is exposed. It's now returned as a key in the event.data "Hash" instead of as a property. I created EventDispatch#extract_stripe_target to safely obtain the value.
I made a few other minor changes while working to get the test suite passing.

This fixed the stripe webhooks for me on my Rails5 app, thanks @hopsoft!
Any chance somebody could review/merge this?

Looks good, although the build is broken on the latest version of rails. I'm fine running this only on ruby 2.2.2 though. If you want to bump the travis.yml to only support that ruby version

Awesome work here guys. Looking forward to seeing this released 🎉

I think we can pass params as hash instead of action controller object.
retrieve_stripe_event(params.to_unsafe_h) do |evt|
   target = evt.data.object
   ::Stripe::Callbacks.run_callbacks(evt, target)
end

Hi @hopsoft , thanks for the pull request!
I'm having trouble reproducing this problem with the latest stripe gem and fixtures (3.0.2). I have a feeling this eventually got fixed by Stripe.
I'm going to close this unless there's a way to reproduce this with a test.
The update to the events is still great though! So I'm going to have that on another PR. Thanks!


Feature Request: by.exactOptions locator

Feature Request
Can we have  by.exactOptions  similar to by.exactRepeater  in protractor....

I think this makes sense. Could you provide a usage example as well, just to make sure I understand?

Hi @NickTomlin,
I have a form which contains multiple ng-option tags in a list sequence. So thought of having  exactOptions similar to exactRepeater so that i can select an option exactly by its name.

Could this be generalized somehow? If many of the selector strategies that accept a string instead supported regular expressions, they could be as vague or specific as a user might need (see https://github.com/angular/protractor/issues/1360).

Agreed, I'm a bit worried about the # of locators exploding if everything has an exact and non-exact form.

This would be a breaking change though (unless we renamed locators), so probably in the icebox for now.


cmd/go: list reports packages as stale immediately after their "go get"

What version of Go are you using (go version)?
go version devel +c52e27e68d Sun Feb 11 20:41:48 2018 +0000 linux/amd64
Does this issue reproduce with the latest release?
This doesn't happen on Go 1.9.4.
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOOS="linux"

What did you do?
Here is a simple reproduction, showing a just fetched and built command package being reported as stale due to a stale dependency.
$ export GOPATH=/tmp/gp
$ mkdir $GOPATH
$ go get mvdan.cc/sh/cmd/shfmt
$ go list -f '{{.ImportPath}} - {{.Stale}} - {{.StaleReason}}' mvdan.cc/sh/cmd/shfmt
mvdan.cc/sh/cmd/shfmt - true - stale dependency: mvdan.cc/sh/fileutil

This appears to happen for anything that has dependencies outside of the core packages, including dependencies to golang.org/x packages.

Seems related to whether or not go install was called on the dependencies directly:
$ go install -v mvdan.cc/sh/cmd/shfmt
$ go list -f '{{.ImportPath}} - {{.Stale}} - {{.StaleReason}}' mvdan.cc/sh/cmd/shfmt
mvdan.cc/sh/cmd/shfmt - true - stale dependency: mvdan.cc/sh/fileutil
$ go install -v mvdan.cc/sh/fileutil
$ go list -f '{{.ImportPath}} - {{.Stale}} - {{.StaleReason}}' mvdan.cc/sh/cmd/shfmt
mvdan.cc/sh/cmd/shfmt - false -

go build -v mvdan.cc/sh/fileutil does not seem to fix it, though.

Seems like the .a file for the library isn't being written to by go install when called on the package that imports the library. But, if go install is called directly on the library, it does write the .a file.
useCache on the library package also returns different results on both of these cases - it's returns true only when go install was called on the library directly.
I've tried debugging this further and possible fixes, but I'm not sure how this is supposed to behave. @rsc, thoughts?

I'll actually promote this to Go 1.10 because it involves the new build cache (potentially). I'll let Russ decide whether it's important for 1.10.

We decided in the release meeting to think about this for Go 1.10.1.

Bumping to 1.10.2 as there doesn't appear to be a fix yet.

Duplicate of #23818, #24558.


add math.sinh support

proceeding after issue

Thanks! I've merged in your change. :)

Thanks apart from that
I really like this project can you guide me any which part requires more attention then i will work on it !!!

There are many unimplemented native methods in the src/natives/*.ts files. You could start by looking into some that interest you! Write tests that use them, figure out how they work, implement them, get the tests passing, and, finally, submit a PR to merge it in. :)


Broken link in guides

In this readme link to Exercise 4 - Roles: Making your playbooks reusable points to non-existing folder 4-roles, while the correct name is 4-role.
Same errors are present at https://network-automation.github.io/lightbulb/workshops/ansible_engine/:

https://network-automation.github.io/lightbulb/workshops/ansible_engine/4-runplaybook  contains trailing space
https://network-automation.github.io/lightbulb/workshops/ansible_engine/5-roles contains trailing s

Thanks @webknjaz. We'll look into correcting that or feel free to submit a PR yourself that references this issue.


Error when trying to stake

Issue description
App Version: 1.3.0
platform: win32
platformVersion: 10.0.19041
platformArchitecture: x64
cpuCount: 6
totalMem: 15742.2 MB
freeMem: 8155.5 MB
Error Type: Main Unhandled Promise Rejection
Error: Uncaught Error: net::ERR_NAME_NOT_RESOLVED
Firefly version
1.3.0
OS details
Windows 10 Pro
Can the issue be reliably reproduced?
No
Steps to reproduce the issue

I want to be able to stake but I have a message saying staking not detected

...
 Would also be worth to try to run Firefly as admin

@DPF64 Were you able to solve your issue?

Yes.  Thank you very much.
It was our firewall that was causing the problem.
Donald P Flanagan
Partner
HFK McRae & Wilson
630 Riverbend Drive, Suite 100
Kitchener, Ontario  N2K 3S2
Phone<PHONE_NUMBER> x215
Fax<PHONE_NUMBER>
[hfkmw6]
From: MiKeF05 @.>
Sent: December 30, 2021 10:50 AM
To: iotaledger/firefly @.>
Cc: Don Flanagan @.>; Mention @.>
Subject: Re: [iotaledger/firefly] Error when trying to stake (Issue #1869)
@DPF64https://github.com/DPF64 Were you able to solve your issue?
—
Reply to this email directly, view it on GitHubhttps://github.com/iotaledger/firefly/issues/1869#issuecomment-1003084608, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXA6GBPXB5N3DLQILHMLEV3UTR5SPANCNFSM5KVIW6IQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Fix TSLint warnings in msbot-export.ts

Related to #313
Proposed Changes
Fix the following warnings in the file msbot-export.ts:

typedef
no-any

Testing
Travis will no longer report this issue.

Pull Request Test Coverage Report for Build 585

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

Totals

Change from base Build 574:
0.0%

Covered Lines:
2836

Relevant Lines:
3526

💛  - Coveralls


python310Packages.yalexs-ble: 2.1.1 -> 2.1.2

Diff: https://github.com/bdraco/yalexs-ble/compare/refs/tags/v2.1.1...v2.1.2
Changelog: https://github.com/bdraco/yalexs-ble/blob/v2.1.2/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

6 packages built:

home-assistant-component-tests.august
home-assistant-component-tests.yalexs_ble
python310Packages.yalexs-ble
python310Packages.yalexs-ble.dist
python311Packages.yalexs-ble
python311Packages.yalexs-ble.dist

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

6 packages built:

home-assistant-component-tests.august
home-assistant-component-tests.yalexs_ble
python310Packages.yalexs-ble
python310Packages.yalexs-ble.dist
python311Packages.yalexs-ble
python311Packages.yalexs-ble.dist


Create airflow image

Is your feature request related to a problem? Please describe.
We may need to pip install extra core packages for airflow service. The recommendation is to extend the base docker image.
Describe the solution you'd like
https://github.com/airflow-helm/charts/blob/main/charts/airflow/docs/faq/configuration/extra-python-packages.md
Describe alternatives you've considered
We can build an env every time a container is spun up, but that can lead to unexpected breaking.
Additional context
Add any other context or screenshots about the feature request here.

Closed by https://github.com/AllenNeuralDynamics/aind-docker-images/pull/19


About handling topics

I'm gonna make RPC calls using emqttd. The pattern is:

Subscribe to the topic which name is a generated uuid
Publish a message to a service subscribing solely to /service/check.
When the service finishes its job, it publishes the result to topic  uuid

So, for every call, we will use one-time topics. How will emqttd handle such topics? If there's a large number of such topics, what consequences may be?


Deploy a default budget on all subscriptions under the assigned scope fails when setting an Action group parameter

What happened? Provide a clear and concise description of the bug, including deployment details.
This custom policy deploys ok when an action group isnt set. When an action group is set in the parameters at time of assignment it fails.
Please provide the correlation id associated with your error or bug.
Resource
/subscriptions/xxxxxx/providers/Microsoft.Consumption/budgets/budget-set-by-policy
Operation name
Create and update budgets
Time stamp
Wed Apr 24 2024 10:24:23 GMT+0100 (British Summer Time)
Event initiated by
6223b87e-5c7e-4767-bf85-f2fbcfaa95f1
Error code
400
Message
Bad Request. Request ID: b082aee9-fc42-45f3-9a33-0e0fb4870334
What was the expected outcome?
The Action group should eithe rbe cerated or use an existing Action group tha has already been created in the Subscription and can be referenced by name
Relevant log output
No response
Check previous GitHub issues

[X] I have searched the issues for this item and found no duplicate

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for reporting. Moving this the Enterprise Scale repo as this is the source of truth for our policies and needs fixing there first and it'll roll down to Bicep & TF 👍
tagging @springstone also


Refresh button clears the form

Open a form from the list.  You'll see the data in the fields, as you should.  You'll see the URL ends with something like "#/Form/ItemID=50".  If you click the browser's refresh button, the page reloads and the URL loses the "ItemID=50" and only ends with "#/Form/".  All the data in the form's fields disappear.

This also seems to affect trying to reach a form with a direct URL.  For example, a link in an email to a specific record.  The form section loads appropriately, but the URL loses the ID parameter and no data is loaded into the form.

Wasn’t the case previously. Sounds like a bug got introduced somewhere. I’ll have to take a look.

From: TomJLynch<EMAIL_ADDRESS>Sent: Friday, March 23, 2018 10:04:54 AM
To: metronical/metron
Cc: Subscribed
Subject: Re: [metronical/metron] Refresh button clears the form (#120)
This also seems to affect trying to reach a form with a direct URL. For example, a link in an email to a specific record. The form section loads appropriately, but the URL loses the ID parameter and no data is loaded into the form.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmetronical%2Fmetron%2Fissues%2F120%23issuecomment-375675450&data=02|01||0adeb24400f54a7e35df08d590c71358|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636574107048643921&sdata=h7apbJ3HcLgzb%2BKYLOBRK5RQEN23%2FxR10JleD%2F4Brsg%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAi9f5DtOn9bes8-XLH--HEA93w8xXvrks5thQEGgaJpZM4Sz153&data=02|01||0adeb24400f54a7e35df08d590c71358|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636574107048643921&sdata=ZWouGNifmcbHS%2B6hSW9dbz1iLkWj40IEk2CyAYUVZnQ%3D&reserved=0.


Colonist in starting card display.

I had a game where I saw the colonist in the first few cards of the display. I’m pretty sure colonist is not in deck I.

Never mind. I think it is in deck I.

Never mind. I think it is in deck I.


Add app information in Diagnose Request File

Currently the app information in the diagnose request file that gets generated via the SQL-Console / Groovy-Console do not write information about the version, the appName and the producer into the manifest file.
Since the attributes are checked in the diagnose wizard, the files cannot be used.
TODO:

add dialog when generating the request file where the developer can enter the information

blocked by https://youtrack.cuba-platform.com/issue/PL-9022 (which will be released in CUBA 6.6)

fixed through the usage of CUBA 6.6s BuildInfo bean


Error when generating new service

Steps to reproduce
To reproduce for me, all I have to do is run feathers generate service at the top level folder of my application and then give it a name, select generic, and say yes or no to if it needs auth.
Expected behavior
I expect to produce a baseline service file and the associated baseline test.
Actual behavior
I'm using the latest version of the cli but when I try to generate a new service I get the error as follows:
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: No function expression found after module.exports
    at Object.exports.addLastInFunction (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\generator-feathers\lib\transform.js:81:11)
    at importService (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\generator-feathers\generators\service\index.js:16:15)
    at module.exports.generators.Base.extend.writing (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\generator-feathers\generators\service\index.js:171:5)
    at Object.<anonymous> (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\yeoman-generator\lib\base.js:439:23)
    at C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\run-async\index.js:26:25
    at new Promise (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\core-js\modules\es6.promise.js:191:7)
    at C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\run-async\index.js:25:19
    at C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\yeoman-generator\lib\base.js:440:9
    at processImmediate [as _immediateCallback] (timers.js:383:17)

Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
feathers-cli 1.2.7
NodeJS version:
4.6.0
Operating System:
Windows 10 Pro
Module Loader:
Node

Did you change any of the code the generator normally modifies? services/index.js should look similar to https://github.com/feathersjs/feathers-chat/blob/master/src/services/index.js

Hm, I did, ok. I thought it would just build a skeleton service but I didn't think it would add it to the services index.


Missing fcitx icons for Asian languages

I'm using the Flatabulous theme with the Ultra Flat Icons on Unity of Ubuntu 14.04.
I found that the panel indicator icons of fcitx input method are missing (or not correctly displayed) when using ultra-flat-icons*.
As far as I have confirmed, the icons for fcitx-hangul (Korean) and fcitx-pinyin (Chinese) are incorrectly substituted for the Text Entry icon in the System Settings (i. e. the icon of the 'A' key). Each of them should be the unique icon symbolizing yin yang (for Korean) and the Chinese character 拼 (for Chinese).
Because the same icon is used for two different input methods, it is somehow difficult to distinguish which IM I am using.
FYI, the indicator icons I mentioned are displayed correctly with the default Ubuntu Mono icon theme.
I hope that the missing icons will be appropriately displayed through the further updates. Thank you.

You should report to the maintainer of ultra-flat-icons. This repository does nothing with these icons except for this repository recommends them.

Thank you for your advice, @Defman21 . I misunderstood that, sorry.


Improve debugging experience by having Vespa C++ processes dump stack trace on crash

If a Vespa C++ process terminates unexpectedly (i.e. from raising SIGSEGV, SIGABRT etc.) and core dumps are disabled on the host, very little information is left for debugging the root cause. Additionally, visibility of the crash itself is limited—it has to be inferred from inspecting Cluster Controller events (nodes going down in the cluster state), local config sentinel events or the host's /var/log/messages (and/or system journal).
The most fundamental piece of information we want to have for any crash (including explicitly triggered assertion failures) is the symbolized stack trace at the crash site.
Printing this information requires installing signal handlers for the relevant signals and tracing/symbolizing the stack frames. Some likely requirements:

Stack frame tracing and symbolizing should be async signal safe.
To be able to deal with a SIGSEGV caused by exhausting stack space (and subsequently hitting a guard page) we'd need an alternate signal handler stack.
The signal handler should keep track of any previously installed handler and call it after it's done. This chaining is necessary to properly defer to handlers implicitly installed by AddressSanitizer et al.

Doing this the Right Way(tm) is a bit of work, so if we end up with a transitive dependency on Abseil once we upgrade our C++ protobuf library dependencies, we might want to consider using its failure handler utility, which satisfies the above requirements.
// InstallFailureSignalHandler()
//
// Installs a signal handler for the common failure signals `SIGSEGV`, `SIGILL`,
// `SIGFPE`, `SIGABRT`, `SIGTERM`, `SIGBUG`, and `SIGTRAP` (provided they exist
// on the given platform). The failure signal handler dumps program failure data
// useful for debugging in an unspecified format to stderr. This data may
// include the program counter, a stacktrace, and register information on some
// systems; do not rely on an exact format for the output, as it is subject to
// change.
void InstallFailureSignalHandler(const FailureSignalHandlerOptions& options);

Considering this issue closed, as the core C++ daemons (vespa-proton-bin, vespa-distributord-bin) now dump stack to stderr upon fatal signals, as described in the original comment. Assertion failures and explicit aborts will have truncated stacks until we're on glibc version that no longer omits frame pointers, which should hopefully happen within a reasonable timeframe.


Add tracing spans to promql

@tomwilkie @bboreham This'll help in prometheus when we add proper tracing support, but currently we'd like to use this for Cortex.

:+1: Thanks.
(I think in the long it'd make sense to move the promql-specific timer names back to the promql package, but keep the generic timer code in a separate package)


add Cloudflare playbook

Adds a Cloudflare playbook

We have some docs on cloudflare here, https://github.com/artsy/potential/wiki/Platform-FAQ#enabling-ddos-protection-for-a-subdomain-via-cloudflare
It might make sense to combine these or cross-link them.

I agree that this should be combined with the items in the Potential wiki, since that includes our support-oriented playbooks and this seems to match.


Add ability to append text to featues

Resolved in PR #719.  Text values have been added as a first-class feature.  The annotation layer shows how these can be used as a subfeature or sublayer for other features.


✨ handle escaped table name

Closes #8

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (4fd0474) 70.27% compared to head (7db184b) 70.42%.

Files
Patch %
Lines

SurrealDb.Net/Models/Thing.Methods.cs
98.46%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #54      +/-   ##
==========================================
+ Coverage   70.27%   70.42%   +0.15%
==========================================
  Files         108      108
  Lines        3566     3588      +22
  Branches      358      361       +3
==========================================
+ Hits         2506     2527      +21
  Misses        882      882
- Partials      178      179       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Unable to authenticate with UK phone number

Environment

Xcode version: 10.2.1
Firebase SDK version: 6.6.0
Firebase Component: Auth
Component version: 6.2.2

Problem
When attempting to authenticate via a UK phone number using verifyPhoneNumber method in PhoneAuthProvider.provider(), the method throws the following error:

The format of the phone number provided is incorrect. Please enter the phone number in a format that can be parsed into E.164 format. E.164 phone numbers are written in the format [+][country code][subscriber number including area code].

When investigating the network requests, I found that the SDK calls to http://www.googleapis.com/identitytoolkit/v3/relyingparty/sendVerificationCode, with recaptchaToken and phoneNumber. I've double-confirmed here that the phoneNumber passed into this request, is indeed, in E.164 format. The request throws the following error:
{
    "error": {
        "code": 400,
        "message": "INVALID_PHONE_NUMBER",
        "errors": {
            "message": "INVALID_PHONE_NUMBER",
            "domain": "global",
            "reason": "invalid"
        }
    }
}

If you pass in +441234512345 as phoneNumber, the SDK will still throw the same E.164 formatting error message, even though it is correctly formatted.
Adding +441234512345 as one of the "Phone numbers for testing" on Firebase console resolves this issue for that particular number.
There are two things I'm thinking about:

The SDK is displaying an incorrect error message. It may somehow be an invalid phone number, but it is not incorrectly formatted.
We have no indicator of why the phone number might be invalid. We are testing with real UK phone numbers (+441234512345 is a dummy example).

To be clear, it is not affecting our USA phone number authentications, just UK.
Any help/thoughts would be appreciated.

@junhohong It seems a project-specific issue. Please submit a ticket on https://firebase.google.com/support so we can more details of your project.


Support interleaved qubit ordering

What should we add?
Currently, all methods which map from spin orbitals to qubits assume a block-ordered arrangement of the qubit register. That means that the first half of the qubits encodes the alpha- and second half the beta-spin orbitals.
It can make sense to specifically want to use an interleaved ordering where odd indices encode alpha- and even indices encode the beta-spin registers. Supporting this via a global configuration setting would be ideal since this can ensure consistent behavior across the various components affected by this (mappers, circuits, etc.)
Alternatively, it may be possible to centralize this configuration via the mappers (since our initial state and ansatz circuits also use mappers). If doing this, the 2-qubit reduction in the case of the ParityMapper would also need to be able to handle this, giving another argument for extracting this qubit reduction functionality out of Terra and back into Nature (see also this comment).

Julia code for doing this is in this file. I may also have python code for this, but I am unable to find it at the moment.

I think that indeed the last suggestion in the issue description seems like the most feasible approach for this. Especially now that QubitMapper objects can be used by themselves (i.e. without being wrapped into a QubitConverter; see also #967). On top of that, the planned TaperedQubitMapper (see #974) already proposes the idea of a "wrapped mapper" in the sense that any mapper can be taken and wrapped to apply the tapering as a secondary step.
This kind of "mapper chaining" could also be used to implement an interleaved ordering, for example along the lines of this:
class InterleavedMapper:

    def __init__(self, mapper: QubitMapper):
        self.mapper = mapper

    def map(self, operator: SparseLabelOp) -> SparsePauliOp:
        block_ordered_op = self.mapper.map(operator)

        # perform operations to convert the block-ordered qubit operator into interleaved
        # maybe Terra has some utilities for qubit-reordering?
        # Otherwise some sort of string-translation could be used
        interleaved_op = ...

        return interleaved_op

This would allow seamless integration into the existing workflow.
Furthermore, this automatically deals with cases like our classically-inspired ansatze (UCC, UVCC) since these first build second-quantized operators and then subsequently map them into qubit space, before evolving them to yield the actual QuantumCircuit building blocks.


#38 Disable click during animation

I look into it this weekend ;)
Sorry but I don't have the time atm


Add maintainers to the project.

I see there are 10 open pull requests for a while now, so I assume @desandro has not had enough time to work on this lately. Is there someone who you think would be up to help maintaing this project?

Thank you for your interest in Draggabilly. For 2500+ GitHub stars, I'd say 15 open issues and 10 open PR's are pretty good. I'm a bit persnickity with how I deal with new features being added to libraries. Growing complexity makes my job as a maintainer harder.
If and when I'm ready to pass this project on to others I'll consider this request. Until then, I'm okay handling this repo.

Please don't take this personally, it was not meant like that. More stars, means more people interested and more benefit from having the project well maintained.
If pull requests remain open, and issues unanswered, it usually means that no one had time or interest to take care of them.


Bring Go current in GHA

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Build-related changes
[ ] Other, please describe:

The PR fulfills these requirements:

[ ] All tests are passing?
[ ] New/updated tests are included?
[ ] If any static assets have been updated, has ui/bindata.go been regenerated?
[ ] Are there doc blocks for functions that I updated/created?

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

@hound-search please approve workflow run


Fix error reading concatenated pdfs

This fixes issue #5909

It's great that you've included a test-case in the patch, but looking at it I'm not sure that we're actually allowed to include (and redistribute) the PDF file in the PDF.js repo. At the top of the pages, it says:

This document is being provided for the exclusive use of HONG YUN YONG at [FIRM]. Not for redistribution."

Would you be able to create a reduced test-case, without any potentially private data?

I tried to and didn't manage to create quite the same problem - I created one which exhibited the same behavior in PDF.js, but it caused Adobe Reader to segfault (whereas Adobe reads the one I attached fine). I think it has to do with the object IDs in the two files, and if they are overlapping.
I'll try again to create one which has the same behavior, perhaps taking the current PDF and removing some of the streams.

I've replaced it with a new test file. It's got the same structure, but I've snipped out the content streams.

Updated the test to just a load test.

/botio test

Looks like the windows failure is false, some file locking issue?

@jordan-thoms Yes, that is not your fault. It has to be corrected on the Windows bot.

/botio test

/botio test

/botio-linux preview

/botio test

Nice, thank you!


Project/Settings Editor rich-text tooltips look weird

Godot version:
cfcb6e11f25adb13177ba08777263288a5ec6f61
Issue description:
They don't have a uniform colour and are not correctly formatted:

i dont think i changed the formatting, so that probably is related to something else..
also, that border is likely not very fit (i just used the tooltip style and put an editorhelp thing inside)

We should add a style override for the help i side. And give it a style box empty.
Should be the cleanest fix.

Fixed by #22423.


Add test for 'Abs' functions for PostgreSQL

#222

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

closing since this commit is in your work under #306


All arguments are dropped, breaking downstream images

It looks like #13 broke this image pretty badly. Prior to that being merged:
docker run --rm renovate/buildpack:1@sha256:e2e416bf17d2e58a8a6042a15dcb559048b11bc5e3143b7c7a33d38e01d8236a bash -c 'echo hello'
hello

And after that being merged:
docker run --rm renovate/buildpack:1@sha256:10e98460170e2ed4ea5150f5baefe0589c60bd8c63bf1f06fac5b8a61b61040d bash -c 'echo hello'

In the second example, bash runs but there is no output. All arguments are silently dropped. This breaks things like the renovate/go image.

Thanks for the fix


Trouble forwarding intercepted packets from TUN interface to default gateway

I'm on Mac, which I'm realizing is much harder to configure packet forwarding than Linux.
I created a TUN device and brought it up and assigned it an IP. I also configured the TUN as the default route on my machine. I can successfully intercept packets as expected. However, I want to be able to forward the original packet off to my router so I can still browse the web, etc.
How might something like this work/look using water?
I've tried something like
package main

import (
	"log"
	"net"

	"github.com/songgao/water"
	"golang.org/x/net/ipv4"
)

func main() {
	ifce, err := water.New(water.Config{
		DeviceType: water.TUN,
	})
	if err != nil {
		log.Fatal(err)
	}

	log.Printf("Interface Name: %s\n", ifce.Name())

	packet := make([]byte, 2000)

	// Replace "en0" with your internet-facing network interface name
	internetInterface, err := net.InterfaceByName("en0")
	if err != nil {
		log.Fatal(err)
	}

	conn, err := net.ListenPacket("ip4:4", "<IP_ADDRESS>") // Listen for IPv4 packets
	if err != nil {
		log.Fatal(err)
	}
	defer conn.Close()

	rawConn, err := ipv4.NewRawConn(conn)
	if err != nil {
		log.Fatal(err)
	}

	for {
		n, err := ifce.Read(packet)
		if err != nil {
			log.Fatal(err)
		}

		header, err := ipv4.ParseHeader(packet[:n])
		if err != nil {
			log.Printf("Error parsing IPv4 header: %v", err)
			continue
		}

		cm := &ipv4.ControlMessage{
			IfIndex: internetInterface.Index,
		}

		err = rawConn.WriteTo(header, packet[header.Len:n], cm)
		if err != nil {
			log.Printf("Error writing packet to raw socket: %v", err)
		}
	}
}

I’m not sure simply forwarding the IP packet to a different interface will work because the source IP address would be the one on your TUN. It may also complicated handling any incoming packets. Depending on what you’re trying to do it might be possible to have your user space program act as a NAT router between the TUN consumer and your local gateway, and modify the IP header on the fly accordingly.

@songgao Any ideas on how this should work on Mac? It seems Mac only supports these point-to-point TUN devices.
IE:
sudo ifconfig utun5 <IP_ADDRESS> <IP_ADDRESS> up

If the first IP is the IP of the TUN device, what would the second IP be?
Also, regarding your suggestion, how would this look like using water? I'm really struggling to get this working.
I'm messing with something I think is aligned with what you're saying below, but not getting anywhere.
package main

import (
	"fmt"
	"log"
	"net"

	"github.com/songgao/water"
)

const (
	// TUN interface configuration
	ifaceName = "utun5"
	ifaceIP   = "<IP_ADDRESS>/32"
	routerIP  = "<IP_ADDRESS>"
)

func main() {
	// Create and configure TUN device
	iface, err := water.New(water.Config{
		DeviceType: water.TUN,
	})
	if err != nil {
		log.Fatal(err)
	}
	log.Printf("TUN interface: %s", iface.Name())

	// Configure the TUN device with IP address and bring it up
	// (You need to set the IP address using external commands or libraries)

	// Create a connection to the router
	conn, err := net.Dial("ip4:icmp", routerIP)
	if err != nil {
		log.Fatal(err)
	}
	defer conn.Close()

	// Read packets from TUN device and forward them to the router
	go func() {
		buf := make([]byte, 1600)
		for {
			n, err := iface.Read(buf)
			if err != nil {
				log.Fatal(err)
			}

			fmt.Printf("Writing packet to router: %d bytes\n", n)

			packet := buf[:n]
			_, err = conn.Write(packet)
			if err != nil {
				log.Fatal(err)
			}
		}
	}()

	// Receive response from the router and write it back to the TUN device
	go func() {
		buf := make([]byte, 1600)
		for {
			n, err := conn.Read(buf)
			if err != nil {
				log.Fatal(err)
			}

			fmt.Printf("Recieved %d bytes from router\n", n)

			packet := buf[:n]
			_, err = iface.Write(packet)
			if err != nil {
				log.Fatal(err)
			}
		}
	}()

	// Prevent the main function from exiting
	select {}
}

Ok, I got this working finally.
I created 2 TUN network interfaces on my machine to emulate what you'd typically do in standard VPN implementation, but I'm only testing on a single machine and only using ICMP as an example.
I have my userspace program read off tun0 IP as expected. I then swap the IP headers for ICMP requests and recompute the checksum:
func checkSum(data []byte) uint16 {
	var (
		sum    uint32
		length int = len(data)
		index  int
	)
	for length > 1 {
		sum += uint32(data[index])<<8 | uint32(data[index+1])
		index += 2
		length -= 2
	}
	if length > 0 {
		sum += uint32(data[index])
	}
	sum = (sum >> 16) + (sum & 0xffff)
	sum += (sum >> 16)
	return uint16(^sum)
}

Persisting back to tun in my program has a dest. IP of the other end of the point to point tun and my ping application properly receives the response packet.
I can also simulate a 5 second delay as requested in another Github issue (in my case I simulate a 5 second delay)


Entering the change difficulty menu if all 3 difficulties aren`t in the data folder will crash the game.

Describe your bug here.
If the easy, normal, and hard difficulties dont all exist when you open the change difficulty menu on the pause screen, the game will crash.
Most annoying thing ever.
Command Prompt/Terminal logs (if existing)
E

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Nothing changed.

this only happens when it wants to it has happened to me

Yus

Made a new issue about this lol...

It appears to be fixed now :D


Migration complete with no errors but nothing's migrated

I'm using the migrator.exe by

Migrate.exe /provider sqlserver2008 /assembly "...\UDAF.DB.Migrations.dll" /connectionString "Data Source=database;Initial Catalog=UDAF_Dev;Persist Security Info=True;User ID=user;Password=pass" /verbose true

i'm running
Alter.Column("Contract_FK")
                .OnTable("CONTRIBUTORS")
                .InSchema("user")
                .AsGuid()
                .Nullable();

and nothing happens. The version information was written to the table but nothing else. Our dba made the change and the table needed to be dropped and re-added but the migrator.exe made no fuss about running this and making it look like all is well.
I just tried to do something a little simpler
Alter.Table("CONTRIBUTORS")
               .InSchema("user")
               .AddColumn("Bogus")
               .AsString(20)
               .Nullable();

and nothing happens.
Does the migrator swallow all the sql errors or do I have other issues?

I had our dba profile the database and the alter statements started working. He stopped profiling and the alter statements stopped working. What is going on?

It's the Schrödingbug

yeah you know it!


add kevinnel.com

Hi, I'd like to have my site added to the webring.

I see now from reading some other pull requests that blog posts aren't counted as pages. I don't think my site qualifies then. I will open another pull request once I have added some more independantly standing content on my website.


Caused by: com.github.shyiko.mysql.binlog.event.deserialization.MissingTableMapEventException: No TableMapEventData has been found for table id:116. Usually that means that you have started reading binary log 'within the logical event group' (e.g. from WRITE_ROWS and not proceeding TABLE_MAP

Describe the bug
A clear and concise description of what the bug is.
Environment :

Flink version :  1.13.2
Flink CDC version: 2.0.0
Database and version: mysql  5.7.28

https://github.com/ververica/flink-cdc-connectors/issues/276


Helper & Component?

When are you planning to write the component and helper for this plugin?

A start of a auth helper can be found at luukau's fork.


Invalid Grant when handleAuthorizationCodeRequest is called

For some reason, when attempting to access the token URL generated by the app, I get an invalid_grant error triggered in access.go line 181, right after loading authorized data from the provided code.
This doesn't happen all the time. When I restart my goapp server it accesses the token fine after refreshing the web page once. I really want to be able to download this token after the url is generated however this inconsistency is blocking me.
This is how I download the token:
	ctx := appengine.NewContext(r)
	client := urlfetch.Client(ctx)
	req, err := http.NewRequest("GET", fmt.Sprintf("http://localhost:8080%s", aurl), nil)
	if err != nil {
		w.Write([]byte("error forming req"))
	}
	ba := &osin.BasicAuth{"<client username>", "<client password>"}
	req.SetBasicAuth(ba.Username, ba.Password)
	res, err2 := client.Do(req)
	defer res.Body.Close()
	if err2 != nil {
		w.Write([]byte("error forming res"))
	}
	jdec := json.NewDecoder(res.Body)
	jdec.Decode(&jr)

^that only works sometimes as mentioned before. Can anyone please help? I've been stuck on this for days :(

I am having same problem. Same error message for this part of code:
ret.AuthorizeData, err = w.Storage.LoadAuthorize(ret.Code)
	if err != nil {
		w.SetError(E_INVALID_GRANT, "")
		w.InternalError = err
		return nil
	}
ret.Code is ok (code exists).

To would be great if you explain hot this parts works:
 var err error
ret.AuthorizeData, err = w.Storage.LoadAuthorize(ret.Code)
if err != nil {
	w.SetError(E_INVALID_GRANT, "")
	w.InternalError = err
	return nil
}

@goors did you check your timestamps? I ran into a similar issue for handling access requests and it was because osin uses time.Now()
https://github.com/RangelReale/osin/blob/master/authorize.go#L68


Add a 30s timeout to archive download request

See https://semgrep.dev/orgs/commonjava/findings

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.399%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hermes/utils/archive.py
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1082

Relevant Lines:
1282

💛  - Coveralls


Remove fexecvpe from Haiku and MacOS/IOS where it's not implemented

I was going to remove the skip-check from build.rs to see if we might be able to enable the function check on at least some platforms, but I'll assume it doesn't work on any as has been suggested.
Closes #732.

@bors: r+

:pushpin: Commit e41975a has been approved by alexcrichton

:hourglass: Testing commit e41975a2b2fa968318f938f5e1f1da1182551078 with merge 7fd1f9d39bd7a2d40bbe02933e098eabe7310667...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 7fd1f9d39bd7a2d40bbe02933e098eabe7310667 to master...


fix(native-filters): Overhead when changing the filter name

SUMMARY
Fixes the overhead when changing the filter name by using a debounced function.
@junlincc @jinghua-qa
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/70410625/135147468-ee528db5-19ba-469c-ad8b-64c4e9138eee.mov
https://user-images.githubusercontent.com/70410625/135147602-a7c49f53-df42-4ed5-9de0-b2e09dd077ab.mov
TESTING INSTRUCTIONS
Check the videos for instructions.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up FEATURE_DASHBOARD_NATIVE_FILTERS=true FEATURE_DASHBOARD_CROSS_FILTERS=true FEATURE_DASHBOARD_NATIVE_FILTERS_SET=true FEATURE_DASHBOARD_FILTERS_EXPERIMENTAL=true

, 100, 200, 250, 300, 500, 600, 1000, 2000 (maybe something for the style guide

That's a great point. I don't think we have a guideline yet.


Calvar'ion & Calvar'ion Reborn need adding to the Menu Entry Swapper Lists

Type
Other
Operating System
None
OS Version
No response
Bug description
Calvar'ion & Calvar'ion Reborn need adding to IsDying() & onNpcChanged() by the looks of things, currently when he hits 0 Hp he's counted as dead.
Screenshots or videos
No response
RuneLite version
Current Build
Logs
No response

I have the IDs for Calvar'ion ready to go, if someone could confirm the first and second phase NPC IDs for Vet'ion as well, that would be great. I assume they are 6611 and 12002, but cannot currently confirm that.

Phase 2 being the form in the middle which is used only for the transformation animation?

Fixed in 900af027d9571085aa288174f7e2f2ee3be49929 and applied for runtime config to apply until that's released in runelite/static.runelite.net@4e48dfc445f5d115aa5558655a78af21c247f060


Travis CI re-configuration

Moved all bash commands to script out of the .travis.yml file

obsolete PR


Triggers in resources.

Introduced triggers for all resources in YAML.

(I shared these in chat, but putting them out here publicly as well.)
I'd like to start with customer scenarios. I don't have enough context about the customer problem and existing solutions, etc. to appropriately judge a design. These functional requirements are helpful but not enough.
Also, there's been some confusion about the keys under resources. My belief is that we need to make that extensible, so that instead of:
resources:
  builds:
  - build: foo
    type: jenkins

instead we can directly offer:
resources:
  jenkins:
  - definition: foo  # or whatever key makes sense here

(These are new, not the ones I shared via chat.)
It would also help to begin with a short, functional discussion of the general problem "triggers" solve. (Likewise "tracking", once we get to that concept.)
How should we think about the existing, pipeline-wide self repository triggers? They offer a lot of convenience for simple cases, but aren't flexible enough for multi-stage pipelines.
My sense is that we need to say more about the variables and context available to task authors and scripters, too. That's not strictly a concern of triggers, but it does get faulted in. Today, depending on the exact trigger, we inject things like:

Build.TriggeredBy.BuildId
Build.Reason
System.PullRequest.PullRequestId

and I imagine RM has some of the same.

@ericsciple @patrickcarnahan @bryanmacfarlane please take a look when you can. @ashokirla is going to factor out triggers into its own doc for clarity.

Thanks for the comments @vtbassmatt.
Regarding the categories under resources, I will get back to you with the customer scenarios and how we can achieve them with the design we currently closed on and also evaluate the alternatives.
However, I would like to have that discussion separate so that we can close on trigger spec for pipelines, repositories and containers which is our priority now.
I will move the triggers spec into a separate doc and also share the scenarios we are going enable with triggers as suggested.
And yes, we push resource variables including trigger specific variables which can be consumed by pipeline stages, jobs and tasks. In RM today, we provide the details about the artifact source that triggered (Release.TriggeringArtifact.Alias) the release and bunch of source specific info including the version, commit sha etc. I will mention about this in the doc.

Created another PR for Triggers: https://github.com/Microsoft/azure-pipelines-yaml/pull/91


Timeout Error Depending On Tensor Sizes

This single linear layer test code causes an error as below. It works fine if the input_tensor shape is [1, 32] or [1, 32, 32]. However, when the input is [32, 32] it gets a timeout error when reading output (linear.output_add_2).
Could you help me find the solution?
Test code
import pybuda
import torch
import time

class Linear(torch.nn.Module):
	def __init__(self):
		super(Linear, self).__init__()
		self.linear = torch.nn.Linear(32, 32)

	def forward(self, x):
		x = self.linear(x)
		return x

if __name__ == '__main__':
	# Create a TT device
	tt0 = pybuda.TTDevice("tt0", num_chips=1)

	# Create a PyTorch module with PyBuda Wrapper
	tt0.place_module(pybuda.PyTorchModule("linear", Linear()))

	# Create an input tensor
	input_tensor = torch.randn(1, 32)

	# # Compile and run inference
	start = time.time()
	output_queue = pybuda.run_inference(inputs=[input_tensor])
	outputs = output_queue.get()
	print(">>> Inference time: ", time.time() - start)
	print(outputs)

Error Log
2024-09-12 17:12:28.179 | INFO     | Runtime         - running: '/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/budabackend/umd/device/bin/silicon/x86/create-ethernet-map /home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/budabackend//cluster_desc.yaml' with timeout 120s
  Detecting chips (found 2)
2024-09-12 17:12:28.346 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:28.380 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:31.103 | INFO     | Backend         - initialize_child_process called on pid 6405
/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/flax/struct.py:132: FutureWarning: jax.tree_util.register_keypaths is deprecated, and will be removed in a future release. Please use `register_pytree_with_keys()` instead.
  jax.tree_util.register_keypaths(data_clz, keypaths)
/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/flax/struct.py:132: FutureWarning: jax.tree_util.register_keypaths is deprecated, and will be removed in a future release. Please use `register_pytree_with_keys()` instead.
  jax.tree_util.register_keypaths(data_clz, keypaths)
2024-09-12 17:12:34.873 | DEBUG    | pybuda.tvm_to_python:_determine_node_dtype:1713 - Node 'linear.weight' does not have a framework dtype specified. Using TVM generated dtype.
2024-09-12 17:12:34.873 | DEBUG    | pybuda.tvm_to_python:_determine_node_dtype:1713 - Node 'linear.bias' does not have a framework dtype specified. Using TVM generated dtype.
2024-09-12 17:12:34.916 | DEBUG    | pybuda.ttdevice:_create_input_queue_device_connector:1408 - Creating input queue connector on TTDevice 'tt0'
2024-09-12 17:12:34.916 | DEBUG    | pybuda.ttdevice:_create_intermediates_queue_device_connector:1418 - Creating fwd intermediates queue connector on TTDevice 'tt0'
2024-09-12 17:12:34.916 | DEBUG    | pybuda.ttdevice:_create_forward_output_queue_device_connector:1398 - Creating forward output queue connector on TTDevice 'tt0'
2024-09-12 17:12:39.053 | INFO     | Runtime         - running: '/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/budabackend/umd/device/bin/silicon/x86/create-ethernet-map /home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/budabackend//cluster_desc.yaml' with timeout 120s
  Detecting chips (found 2)
2024-09-12 17:12:39.192 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:39.227 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:40.648 | INFO     | pybuda.device_connector:pusher_thread_main:148 - Pusher thread on <pybuda.device_connector.InputQueueDirectPusherDeviceConnector object at 0x7f1e3cfce070> starting
2024-09-12 17:12:40.649 | INFO     | Backend         - initialize_child_process called on pid 6618
2024-09-12 17:12:40.650 | DEBUG    | pybuda.device:run_next_command:455 - Received COMPILE command on TTDevice 'tt0' / 6618
2024-09-12 17:12:40.650 | DEBUG    | pybuda.ttdevice:compile_for:785 - Compiling for Inference mode on TTDevice 'tt0'
2024-09-12 17:12:40.710 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:chips_with_mmio
2024-09-12 17:12:40.725 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:40.741 | INFO     | Runtime         - Found cluster descriptor file at path=/tmp/jaehwan/3ab2f8d6c3b9/cluster_desc.yaml
2024-09-12 17:12:40.743 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:chip_locations
2024-09-12 17:12:40.743 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:ethernet_connections
2024-09-12 17:12:40.743 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:chips_with_mmio
2024-09-12 17:12:40.743 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:chip_locations
2024-09-12 17:12:40.743 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:ethernet_connections
2024-09-12 17:12:40.743 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage init_compile
2024-09-12 17:12:40.747 | INFO     | pybuda.ci:initialize_output_build_directory:98 - Pybuda output build directory for compiled artifacts: /tmp/jaehwan/3ab2f8d6c3b9
2024-09-12 17:12:40.758 | INFO     | pybuda.ci:create_symlink:89 - Symlink created from /home/n4/jaehwan/research/tenstorrent/buda-tests/torch-module/tt_build/test_out to /tmp/jaehwan/3ab2f8d6c3b9
2024-09-12 17:12:40.794 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:chips_with_mmio
2024-09-12 17:12:40.794 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:chip_locations
2024-09-12 17:12:40.794 | INFO     | Backend         - Lookup contexts -- arch:system scope:device name:ethernet_connections
2024-09-12 17:12:40.794 | INFO     | pybuda.compile:init_compile:511 - Device architecutre: wormhole_b0
2024-09-12 17:12:40.794 | INFO     | pybuda.compile:init_compile:512 - Device grid size: r = 8, c = 8
2024-09-12 17:12:40.794 | INFO     | pybuda.compile:init_compile:522 - Using chips: [0]
2024-09-12 17:12:40.794 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage generate_initial_graph
2024-09-12 17:12:40.816 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage post_initial_graph_pass
2024-09-12 17:12:40.872 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage consteval_graph
2024-09-12 17:12:40.905 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage optimized_graph
2024-09-12 17:12:40.975 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage post_autograd_pass
2024-09-12 17:12:40.993 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage pre_lowering_pass
2024-09-12 17:12:41.011 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage buda_graph_pre_placer
2024-09-12 17:12:41.015 | INFO     | GraphCompiler   - Running with Automatic Mixed Precision Level = 0.
2024-09-12 17:12:41.033 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage balancer_pass
2024-09-12 17:12:41.033 | INFO     | Always          - Running Balancer with Policy: PolicyType::NLP
2024-09-12 17:12:41.052 | INFO     | Balancer        - Based on NLP matmul analysis, target cycle count is set to 45000
2024-09-12 17:12:41.052 | INFO     | Balancer        - Balancing 100% completed!
2024-09-12 17:12:41.053 | INFO     | Balancer        - Balancer perf score : 2314814.8
2024-09-12 17:12:41.053 | INFO     | Backend         - Lookup contexts -- arch:system scope:device0 name:harvesting_mask
2024-09-12 17:12:41.053 | INFO     | Placer          - Running DRAM allocator for device 0
2024-09-12 17:12:41.061 | INFO     | PerfModel       - Running performance model...
2024-09-12 17:12:41.079 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage pre_netlist_pass
2024-09-12 17:12:41.097 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage generate_netlist
2024-09-12 17:12:41.097 | INFO     | pybuda.compile:generate_netlist:1075 - Generating Netlist
2024-09-12 17:12:41.165 | INFO     | pybuda.ci:create_symlink:89 - Symlink created from /home/n4/jaehwan/research/tenstorrent/buda-tests/torch-module/linear_netlist.yaml to /tmp/jaehwan/3ab2f8d6c3b9/linear_netlist.yaml
2024-09-12 17:12:41.206 | INFO     | pybuda.compile:pybuda_compile_from_context:239 - Running compile stage backend_golden_verify
2024-09-12 17:12:41.207 | DEBUG    | pybuda.tensor:consteval_tensor:1233 - ConstEval graph: linear.weight
2024-09-12 17:12:41.208 | INFO     | Runtime         - Running tt_runtime on host: 'c1'
2024-09-12 17:12:41.208 | INFO     | PerfInfra       - Backend profiler is disabled
2024-09-12 17:12:41.208 | INFO     | PerfInfra       - Memory profiler is enabled
2024-09-12 17:12:41.212 | WARNING  | Runtime         - Config.soc_descriptor_path='/tmp/jaehwan/3ab2f8d6c3b9/device_descs/wormhole_b0_2064_0x0.yaml' doesn't exist, defaulting to '/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/budabackend/device/wormhole_b0_8x10.yaml'
2024-09-12 17:12:41.231 | INFO     | SiliconDriver   - Detected 1 PCI device : {0}
2024-09-12 17:12:41.233 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:41.370 | INFO     | Runtime         - Compiling Firmware for TT device
2024-09-12 17:12:42.118 | INFO     | SiliconDriver   - Software version 6.0.0, Ethernet FW version 6.9.0 (Device 0)
2024-09-12 17:12:42.230 | INFO     | Runtime         - Starting device status monitor with TIMEOUT=500s
2024-09-12 17:12:42.230 | INFO     | Loader          - Waiting for 30 seconds for NCRISC Firmware to start running on 1 device(s)
2024-09-12 17:12:42.243 | INFO     | pybuda.backend:feeder_thread_main:149 - Feeder thread on <pybuda.backend.BackendAPI object at 0x7f1e3cfce1f0> starting
2024-09-12 17:12:42.243 | DEBUG    | pybuda.backend:push_constants_and_parameters:491 - Pushing to parameter linear.weight
2024-09-12 17:12:42.244 | DEBUG    | pybuda.backend:push_constants_and_parameters:491 - Pushing to parameter linear.bias
2024-09-12 17:12:42.273 | INFO     | SiliconDriver   - Detected 1 PCI device : {0}
2024-09-12 17:12:42.274 | WARNING  | SiliconDriver   - NumHostMemChannels: 2 used for device_id: 0x401e less than target: 4. Workload will fail if it exceeds NumHostMemChannels. Increase Number of Hugepages.
2024-09-12 17:12:42.302 | DEBUG    | pybuda.run.impl:_run_forward:644 - Running concurrent device forward: TTDevice 'tt0'
2024-09-12 17:12:42.304 | DEBUG    | pybuda.device:run_next_command:429 - Received RUN_FORWARD command on TTDevice 'tt0' / 6618
2024-09-12 17:12:42.305 | DEBUG    | pybuda.ttdevice:forward:906 - Starting forward on TTDevice 'tt0'
2024-09-12 17:12:42.305 | DEBUG    | pybuda.backend:feeder_thread_main:171 - Run feeder thread cmd: fwd
2024-09-12 17:12:42.306 | INFO     | Runtime         - Running program 'run_fwd_0' with params [("$p_loop_count", "1")]
2024-09-12 17:12:42.307 | DEBUG    | pybuda.backend:read_queues:345 - Reading output queue linear.output_add_2
2024-09-12 17:12:42.308 | DEBUG    | pybuda.device_connector:pusher_thread_main:163 - Pusher thread pushing tensors
2024-09-12 17:12:42.309 | DEBUG    | pybuda.backend:push_to_queues:452 - Pushing to queue input
2024-09-12 17:12:43.309 | DEBUG    | pybuda.backend:read_queues:362 - 0 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:44.310 | DEBUG    | pybuda.backend:read_queues:362 - 1 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:45.311 | DEBUG    | pybuda.backend:read_queues:362 - 2 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:46.312 | DEBUG    | pybuda.backend:read_queues:362 - 3 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:47.313 | DEBUG    | pybuda.backend:read_queues:362 - 4 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:48.315 | DEBUG    | pybuda.backend:read_queues:362 - 5 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:49.316 | DEBUG    | pybuda.backend:read_queues:362 - 6 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:50.317 | DEBUG    | pybuda.backend:read_queues:362 - 7 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:51.318 | DEBUG    | pybuda.backend:read_queues:362 - 8 Reading output queue linear.output_add_2 timed out after 1
2024-09-12 17:12:52.319 | DEBUG    | pybuda.backend:read_queues:362 - 9 Reading output queue linear.output_add_2 timed out after 1
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/pybuda/device.py", line 577, in dc_transfer_thread
    self.dc_transfer(direction)
  File "/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/pybuda/device.py", line 591, in dc_transfer
    self.forward_dc.transfer(blocking=True)
  File "/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/pybuda/device_connector.py", line 441, in transfer
2024-09-12 17:12:52.321 | DEBUG    | pybuda.device:dc_transfer_thread:581 - Ending dc transfer thread intermediates on TTDevice 'tt0' due to shutdown event
    data = self.read()
  File "/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/pybuda/device_connector.py", line 348, in read
    ret = BackendAPI.read_queues(self.direct_pop_queues, self.original_shapes, self.runtime_tensor_transforms, requires_grad=self.requires_grad, single_output=False, shutdown_event=self.shutdown_event, clone=False)
  File "/home/n4/jaehwan/research/tenstorrent/pybuda/pybuda-env/lib/python3.8/site-packages/pybuda/backend.py", line 369, in read_queues
2024-09-12 17:12:52.322 | DEBUG    | pybuda.device:dc_transfer_thread:581 - Ending dc transfer thread forward_input on TTDevice 'tt0' due to shutdown event
    raise RuntimeError("Timeout while reading " + outq.name)
RuntimeError: Timeout while reading linear.output_add_2
2024-09-12 17:12:52.324 | DEBUG    | pybuda.device_connector:pusher_thread_main:156 - Ending pusher thread on <pybuda.device_connector.InputQueueDirectPusherDeviceConnector object at 0x7f1e3cfce070> due to shutdown event
2024-09-12 17:12:53.319 | DEBUG    | pybuda.device:get_next_command:360 - Ending process on TTDevice 'tt0' due to shutdown event

Based on this line RuntimeError: Timeout while reading linear.output_add_2 it looks like the device is in a bad state.
Can you do a card reset using the tt-smi tool? or just doing a system reboot. Then try again.

Both tt-smi -r 0 and sudo reboot didn't work. I don't understand why the input_tensor = torch.randn(32, 32) causes an error. However, it works fine when it's input_tensor = torch.randn(1, 32, 32). Should I just use the latter as a workaround? (Even though this problem should be fixed.)

pybuda expects a batch dimension, that's why including the extra (1, 32, 32) is required.

@jhlee508 any follow up on the above?

It makes sense that pybuda expects a batch dimension, but seems still weird that how does pybuda know which dimension is the batch dimension. For example, if an input with the shape [3, 128, 128] is provided, how does the model determine whether the '3' represents the batch size or not?
I have tried a few input shapes and couldn't figure out how pybuda determines which dimension is the batch dimension, since it doesn't seem that always for example 3rd dimension is the batch dimension.

Inputs with these shapes work fine: [1, 32], [4, 32], [1, 32, 32]
Inputs with these shapes does not work: [32, 32]

Thanks for the additional context @jhlee508. What seems to be happening then is that this particular input shape [32, 32] is causing a hang in the software. Fair to label this as a bug.
We've just released a new version of Buda: https://github.com/tenstorrent/tt-buda/releases/tag/v0.19.3
I would suggest that you try that one to see if there is any change. Otherwise, let's keep this bug open and we'll take a look at it.

Closing issue for now. Please reopen if there are any outstanding items.


VM mutating webhook fails on error

What this PR does / why we need it:
VM mutating webhook now fails on error.
Release note:
None

Code looks good. However if that webhook is not yet tested it probably should be!

/retest

@jean-edouard can you take another look?

/retest

/cc @lyarwood

/lgtm


"Docker not found" using Lima on Apple Silicon

Hi, I have an issue initialising Dapr on my machine.
I cannot use Docker Desktop due to company restrictions, therefore I am using Lima as a Docker alternative.
My docker context is set to lima-docker  and it runs perfectly fine.
The only issue I have is that when I run dapr init, it cannot find my docker
⌛  Making the jump to hyperspace...
❌  could not connect to Docker. Docker may not be installed or running
docker info:
client:
Context:    lima-docker
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.9.1)
compose: Docker Compose (Docker Inc., 2.14.0)
Server:
Containers: 20
Running: 0
Paused: 0
Stopped: 20
Images: 27
Server Version: 20.10.21
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: false
userxattr: true
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: a05d175400b1145e5e6a735a6710579d181e7fb0
runc version: v1.1.4-0-g5fd4c4d
init version: de40ad0
Security Options:
seccomp
Profile: default
rootless
cgroupns
Kernel Version: 5.15.0-60-generic
Operating System: Ubuntu 22.04.1 LTS
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 3.816GiB
Name: lima-docker
ID: redacted
Docker Root Dir: /home/lima.linux/.local/share/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Is there a way to make this work?

@dapr/maintainers-cli can you move this to the CLI repo please?

@Hodacco docker host variable needs to point to [co]lima socket file, something like:
For lima:
export DOCKER_HOST=unix://${HOME}/.lima/docker/sock/docker.sock

For colima:
export DOCKER_HOST="unix://${HOME}/.colima/default/docker.sock"

Afterwards, dapr init should work


Something went wrong while installing Helm Tiller in Gitlab

This is happening very specific with Gitlab,I have enterprise gitlab and when trying to set K8 cluster ,i filled out all mandatory information for existing K8 cluster and after integration while trying to install Helm Tiller ,get this strange issue of
Something went wrong while installing Helm Tiller
No logs at all
Output of helm version:
vagrant@ubuntu-xenial:~$ helm version
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
vagrant@ubuntu-xenial:~$
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:43:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS

Can you perhaps provide a set of instructions you are trying to follow when installing tiller? With no logs and no instructions, I have no information to figure out the issue. Thanks.

I have a canonical Kubernetes cluster developed by juju charms which i built using below article
juju deploy kubernetes-core
https://jujucharms.com/kubernetes-core/
Then I connected this cluster to Gitlab by providing below detaills
Kubernetes gitlab integrations steps
https://docs.gitlab.com/ee/user/project/clusters/
API URL, run kubectl cluster-info | grep 'Kubernetes master' | awk '/http/ {print $NF}'.
Token:
List the secrets by running: kubectl get secrets. Note the name of the secret you need the token for.
Get the token for the appropriate secret by running: kubectl get secret <SECRET_NAME> -o jsonpath="{['data']['token']}" | base64 -d
CA certificate, run kubectl get secret  -o jsonpath="{['data']['ca.crt']}" | base64 -d.
But Gitlab shows below error with Helm Tiller

Oh... So this is a problem with gitlab itself, not necessarily helm. I'm afraid there's nothing we can do for you here. I suggest following up with the gitlab team directly.
Because this isn't an issue on our end (at least not until more logs can be shown), I'm going to close this and ask that you follow up with the gitlab team. Thanks!

Someone had resolve this problem ? I'm facing the same issue, and the error is not detailed enough for me to understand :(

@BobLamarley same for us as well. The error is not specific enough to determine the issue, but it's coming from gitlab, not Helm. I'd suggest opening a ticket with the gitlab team. We have no clue what would cause the error.

@bacongobbler I was using the certificate .pem but i wasn't including "-----BEGIN CERTIFICATE-----" at the beggining and "-----END CERTIFICATE-----" at the end. Now my error has changed ^^

I will create a ticket with the gitlab team anymay :)

For those wo've the same problem, I've managed the problem with this docs
https://docs.gitlab.com/ee/user/project/clusters/#adding-an-existing-kubernetes-cluster
I was missing a gitlab service account in the default namespace and a cluster role binding to give the gitlab service account cluster-admin privileges :)


HDDS-11154. Improve Overview Page UI

What changes were proposed in this pull request?
This PR will add a new Overview page which contains a better implementation for the UI
Please describe your PR in detail:

This PR adds a new Overview Page with improved layout and design.
The new page would help to eventually improve the overall look and feel for Recon
Currently the page is disabled to the user so as to not affect any existing functionality
Apart from this it also contains the initial setup for a few components that will be used in the future PR as a part of the improvement effort.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11154
How was this patch tested?
This patch was tested manually via both localhost and building and running Ozone via docker
Screenshot:

How to test this new UI?
Currently the UI is disabled and hidden via using a switch so that users are not able to access it accidentally.
In order to switch to the new UI please follow the below steps:

Remove the disable property from the AntDSwitch component in app.tsx
(For testing after build) Make sure to build after removal of the disable property in the above step
Click on the switch in the top right corner of the UI
This should take you to the new page
Please Note: Currently the links for the cards point to blank pages as those have not been implemented yet

Hi @smitajoshi12, could you take a look at this PR as well?
Thanks

If we get Storage Report from Cluster API is blank or null then UI is breaking Can u check

@devabhishekpal
On E Charts Libraray Can we add label or text show green and red color indicates what properties.

@devabhishekpal
On E Charts Libraray Can you add label or text show green,red  and blue color on hovering indicates what properties on gauge chart.

So this was actually disabled as suggested by the design since we are already showing the label/legend in the sidebar. This card would only be overview level hence need to avoid extra features

Further error handling is currently not being done, as error pages are still under progress, and we want to wrap component in Error Boundary instead of individually handling error scenarios in code.

Thanks for the patch @devabhishekpal
LGTM +1

@devabhishekpal It looks like there's an error in the build on your fork. You can check it out here: https://github.com/devabhishekpal/ozone/actions/runs/10279094710/job/28443877043. Could you please take a look?

Thanks for indicating this issue @ArafatKhan2198 , removed it in the latest commit

Thanks for working on the improvement @devabhishekpal
Thanks @devmadhuu @smitajoshi12 for the review.


Unclear how what exactly is returned by kv.put-

Which Cloudflare product(s) does this pertain to?
KV
Subject Matter
worker kv binding put
Content Location
Unclear how what exactly is returned
https://github.com/cloudflare/cloudflare-docs/blob/cd3f02d391ce643ef651d373ae116f1fa27164ba/content/kv/api/write-key-value-pairs.md?plain=1#L30
It's unclear if I need to consider anything special
maybe something like
a void promise is returned the resolving of this signified a successful write and this local worker can now get
this should never fail but if it does it will throw an error so you should catch that.
or maybe this never throws and simply will not resolve.
is kv.put GARUNTEED to resolve. can the end developer omit the .catch(retry) logic?
aka by example
let putReturn = await kv.put("mykey", "mydata")
// ok we are 100% good this code canot fail

//or do we need .catch(retryLogicHere)

//or do we need if(putReturn != 0) {retryLogicHere}

Thanks, happy coding
Additional information
No response

@syonfox are you asking What the put() method returns?

yes in a sense. IM asking if put implements retry logic and is guaranteed to not throw an error and eventually resolve the promise or if there is a possibility of it failing and the end developer needing to do some retry logic.
as far as I can tell it resolves an empty promise aka return 0 / falsy if you are a c person.
I would like to know if there are any failure modes to this or if its safe to assume any resolve means a succesfull push/put

an a documentation level it would be nice to know A: what is resolved explicitly resolve(0) maybe
and B: if it is possible for put to throw an error

an a documentation level it would be nice to know A: what is resolved explicitly resolve(0) maybe
and B: if it is possible for put to throw an error

PUT operations can fail. If you need to ensure that the operation succeeds, then you will need to retry.
Does this answer all your questions and concerns? Let me know!

How does it fail by throwing or returning a non-falsy exit code?

Im also sort of wondering why and how put may fail
my curent understanding is
[worker] ->[edge] -> [central]
put===================> insert
get=======[cache or]====select

@syonfox because workerd is open source you can see the behavior yourself here: https://github.com/cloudflare/workerd/blob/main/src/workerd/api/kv.c%2B%2B#L21-L29

Thanks by the looks of that kV will
Resolve undefined on successful key insert
And throw an exception on non 200 network response
Therefore perhaps the documents should say somthing along those lines
If resolve continue
Catch -> retry with back off

On Mon., Oct. 23, 2023, 19:19 aplunk, @.***> wrote:

@syonfox https://github.com/syonfox because workerd is open source you
can see the behavior yourself here:
https://github.com/cloudflare/workerd/blob/main/src/workerd/api/kv.c%2B%2B#L21-L29
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/cloudflare-docs/issues/11267#issuecomment-1775243770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHJVDPKYI5TTX4GH7GPHDDYAZYV5AVCNFSM6AAAAAA56KZZT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVGI2DGNZXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Photoshop color picker addenda

Edited Photoshop color picker to add more control over labels and an optional 'reset' button

update Photoshop add more props ?

I indeed edited Photoshop.vue in order to add several props (and edited the vue template accordingly) that would allow more control from the user :

acceptLabel : Allows to customize the text on the validation button (defaulted to OK)
cancelLabel : Allows to customize the text on the cancel button (defaulted to Cancel)
hasResetButton : If true, would display a reset button below the input fields
resetLabel : Allows to customize the text on the reset button (defaulted to Reset)


cannot find vsock device

cannot find vsock device
scan /sys/class/virtio-ports/ failed: No such file or directory
cannot find ctl channel
fail to setup hyper serial channel

vsock device probing is adaptive and its failure does not affect hyperstart starting up. The issue here is missing serial port.
@gogolxdong can you please describe a bit how you got the error? Namingly,

Which hypervisor are you using?
Are you running with runv directly or using hyperd?
Please paste all console logs

Using default qemu hypervisor with hyperd ,whole console logs is the result of running hyperstart.
It seems working now , don't know where is the trick. Another concern is the tty console allocated seems fixed height and width not adjusting to the host console enough.

@gogolxdong are you running without kvm support? We used to see a similar issue on travis and it was related to guest clock drifting.

With kvm support. I found another issue which result in hyperctl ERROR: Error from daemon's response: hyperstart closed once specified cpu exceed 8 cores and performance test via wrk -t12 -c400 -d30s http://<IP_ADDRESS> didn't improve linearly as cpu cores increased from 4 to 8 and memory from 8192 to 10240 as expected.

@gogolxdong Current max cpu is 8 and it is hard coded in both hyperstart and runv right now.

Is it necessary to set CONFIG_NR_CPUS=8 ,will it be unlimited and how ?

also DefaultMaxCpus in runv. Then you'll need to build your self a kernel and build hyperd.
Performance depends on many things not just cpu and memory. More CPU can mean more lock contentions and cache line bouncing for your test program.


Update README with links to charts

A minor update to link other charts with README

@povilasv the CI is failing unrelated to this PR.  I will submit a PR to fix it.

@povilasv please rebase


Add .heic extension

.heic is a compressed image format used on Apple devices.
https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format

thanks @john-terenzio


Currently there is no way to pass multiple audiences

https://github.com/PHP-Open-Source-Saver/jwt-auth/blob/794160d66153a75cad14c973635cd7c57dc61387/src/Providers/JWT/Lcobucci.php#L209C1-L210C1
should verify if $value is an array and use the spread operator in that case.

@zoltankeresztes can you check if #235 works for you?

yes, thanks a lot!


Unable to validate against any security context constraint

Dropping all capabilities and setting securityContext.seccompProfile to RuntimeDefault causes errors on OpenShift 4.10:
capabilities:
  drop:
  - ALL
  seccompProfile:
    type: RuntimeDefault

85s         Warning   FailedCreate        replicaset/amq-broker-controller-manager-d4cd556b9   Error creating: pods "amq-broker-controller-manager-d4cd556b9-5xdvv" is forbidden: unable to validate against any security context constraint: [pod.metadata.annotations.container.seccomp.security.alpha.kubernetes.io/manager: Forbidden: seccomp may not be set provider "anyuid": Forbidden: not usable by user or serviceaccount provider "nonroot": Forbidden: not usable by user or serviceaccount provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount provider "machine-api-termination-handler": Forbidden: not usable by user or serviceaccount provider "hostnetwork": Forbidden: not usable by user or serviceaccount provider "hostaccess": Forbidden: not usable by user or serviceaccount provider "node-exporter": Forbidden: not usable by user or serviceaccount provider "privileged": Forbidden: not usable by user or serviceaccount]

This issue will be fixed in v1.0.14 reverting the fix for #616


Readme update to base64 encoding to avoid line breaks

Description of the change:
Fix for downstream ACM 2.x instructions to use base64 -w 0 instead of just base64 this will ensure there are no line breaks when doing a base64 encoding on the QUAY_TOKEN.
Motivation for the change:
Was causing issues when the base64 encoded value is broken up into different lines when deploying a downstream build.

@chrisahl Hmm, on Fedora it seems to need that, however, I'll make another revision to note that in that case. Thanks!

@chrisahl can you review this again? Thanks!

@chrisahl Could you merge this? I don't have the permission to.

@harryli256 I typically leave the merges to @gurnben but maybe @Kyl-Bempah can also merge in this repo?

@harryli256 I typically leave the merges to @gurnben but maybe @Kyl-Bempah can also merge in this repo?

@chrisahl I can merge to every repo

Alright thanks @Kyl-Bempah!


Remove/correct dead TRE links

Is there an existing issue for this?

[X] I have searched the existing issues

Issue summary
There are references in the documenation to a now non-existent branch of AzureTRE:
o	https://github.com/microsoft/AzureTRE/tree/features/InnerEyeAMLPLDeployment/InnerEyeAMLPLDeployment
These need to be removed or corrected to an active branch.
What documentation should be provided?
Working links to the TRE
AB#7144

This is the Azure TRE documentation for the InnerEye Workspace Service - https://microsoft.github.io/AzureTRE/tre-templates/workspace-services/inner-eye/


Removed special handling for onnx sqrt

@caffe2bot test this please

@jspisak sqrt now doesn't require special treatment?

https://github.com/caffe2/caffe2/blob/master/caffe2/operators/sqrt_op.cc
@yinghai yeah, we have it now :-) Thanks to @jspisak's great work!

@caffe2bot retest this please

@caffe2bot retest this please


Create Auto Materials with TerrainMagic

Well, this is not about creating auto materials. But get the same effect with TerrainMagic.
This will provide more control & easy use.

Implemented. See: https://youtu.be/O4GJVljxdag


Cosmetic: Update styling of image captions in WP image block

Update styling of caption when adding a caption to an image block in WP.
Current style:

Desired style:

See Figma design

@wrendo This issue needs a dev owner still

Unassigning myself for this issue.
@kkoryaka
As you have probably seen here and there, we have some wp-block styles coming from Gutenberg.
This caption is one. You should be able to look at the markup generated by WordPress and apply your CSS styles. Putting in the manual CSS is fine - we can do a CSS merge later & I can duplicate into the build code when we are ready.

Done, closing.