Forcing a scheduled CRON pipeline

I have a pipeline that's currently set to "daily" and I want to force it to trigger ad-hoc.
What is the goal / desired outcome?
Enable forcing of a scheduled pipeline
If there is a way to accomplish this today via workaround, what does that require?
update them to have a timestamp that triggers right now, you can also call run pipeline on a previous commit, but unfortunately there's not quite a good way to trigger it now
(Optional) What is your proposal for a feature to solve this?

Environment?:

Kubernetes version (use kubectl version):
Pachyderm CLI version (use pachctl version): 1.9.3
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s): N/A
OS (e.g. from /etc/os-release): N/A
Others:

Are users able to manually create a tick file to do an ad-hoc trigger or do we prevent writing to the cron repo? They'd have to be careful to maintain the file format and either overwrite (or not) to match the semantics of the cron input.

We do not restrict users from writing to the cron repo, so that will work as a way to manually trigger the pipeline, it's not super friendly though, because you have to correctly format the file name or the cron pipeline will break in a fairly confusing way. It'll actually trigger regardless of what you name the file, but it will then try to parse this file to figure out the next time it should trigger, which is where things will break.
I think a user friendly solution to this would be to fold this functionality into run pipeline, it could just as easily be its own command (trigger pipeline maybe?), but I think whatever we name it would get conflated with run pipeline, and they're conceptually very similar even though what's going on behind the scenes is a bit different. I'm thinking something like this would be nice:
$ pachctl run-pipeline <pipeline-name> --trigger-cron [other commits...]

This would error when called on pipelines that don't have cron inputs, when called on those that do it'll create a new commit on each of the cron inputs (having multiple cron inputs is pretty uncommon but technically supported) with the current time as the time stamp. It would also have the existing semantics for the specified commits, specifying a commit from the cron input and passing --trigger-cron should error, if there are multiple cron inputs I think it works so long as one of them isn't specified.

I am facing the same issue. Since crons have name couldn't it just be:
$ pachctl run-cron <cron-name>


Fix tensor read (device->host path)

Currently, we're calling to_memory_config to get tensor from device to host. This isn't correct, so we're changing to the approach used in ttnn lib, which is to call FromDevice + ToLayout ops, as can be seen in the to_torch method in third_party/tt-metal/src/tt-metal/ttnn/ttnn/operations/core.py:
    if ttnn.is_tensor_storage_on_device(tensor):
        tensor = ttnn.from_device(tensor, cq_id=cq_id)

    if tensor.layout != ttnn.ROW_MAJOR_LAYOUT:
        tensor = tensor.to(ttnn.ROW_MAJOR_LAYOUT, device)

This PR updates the conversion of ToLayout op from TTIR to TTNN. It also adds the FromDevice op.

@svuckovicTT assuming you're getting this from core.py, I think there's a fix going in that flips these two operations: essentially untilize on device first before moving to host.

@svuckovicTT assuming you're getting this from core.py, I think there's a fix going in that flips these two operations: essentially untilize on device first before moving to host.

Oh awesome, thanks for the heads up! I'll test it and update accordingly. Do you happen to have a link to their issue/PR?

@svuckovicTT assuming you're getting this from core.py, I think there's a fix going in that flips these two operations: essentially untilize on device first before moving to host.

Oh awesome, thanks for the heads up! I'll test it and update accordingly. Do you happen to have a link to their issue/PR?

This is the PR AFAIK: https://github.com/tenstorrent/tt-metal/pull/12001


Send confirmation email on event registration

To stop spamming, user must also confirm their email address via a HMAC link.  API and mail server to come

@TexasHODL need some copy here too for the registration email.  I guess include the TG link.


[Machine Learning] Time Series analysis and forecasting of stock prices using TensorFlow

Proposal Submission
Proposed title of article
[Machine Learning] Time Series analysis and forecasting of stock prices using TensorFlow
Proposed article introduction
Stock market prediction is used to determine the future value of company stock or other financial instruments traded on an exchange. The successful prediction of a stock's future price could yield significant profit. Time series analysis comprises methods for analyzing time-series data in order to extract meaningful statistics and other characteristics of the data.
In investing companies, a time series tracks the movement of the chosen data points, such as a security’s price, over a specified period of time with data points recorded at regular intervals. Time series forecasting fits a model on a historical dataset, that is, the training set, and then using it to predict a future occurrence, which is the test set.
The performance of the time series model is rated based on its future prediction. We will use TensorFlow to build a Sequential Model with multiple input and hidden layers.  The trained model will be used to predict Apple's future stock prices.
Key takeaways

Time series analysis and decomposition of Apple stock data.
Initializing the Sequential model.
Adding LSTM layers. (multiple hidden layers)
Adding Dense Layers.
Plotting the actual and prediction prices using Matplotlib

Article quality
In this article, we build the time series model using stacked LSTM layers which are more efficient. A Stacked LSTM architecture is an LSTM model that has multiple hidden LSTM layers with each layer containing multiple cells. LSTM models are able to store information over a period of time, this makes them more efficient when training a time series model which is memory intensive.
References
Please list links to any published content/research that you intend to use to support/guide this article.
Conclusion
Finally, remove the Pre-Submission advice section and all our blockquoted notes as you fill in the form before you submit.
We look forwarding to reviewing your topic suggestion.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. Please feel free to suggest an alternate topic to explore. 🚀


allow datalist to do static search using formOptions

i think there are other locations where we are using datum (like on removing a value) can you apply the same get Datum function anywhere where datum is being used


RSZ: setup repair on asap7 dies with "unsupported path type" error

When testing a design with the ASAP7 PDK, I hit an error when doing setup repair:
Repair setup violations...
[CRITICAL STA-0259] unsupported path type

This also reproduces with the gcd test in ORFS. An issue tarball: cts_gcd_asap7_base_2022-06-25_06-25.tar.gz

I ran scripts/cts.tcl with the latest OR and it does not reproduce this issue. I honestly don't see any way the code could get to that line since it is inside a debugging function that isn't called by any user commands.

@jjcherry56 sorry for that, I was sure I rebuilt from pristine upstream source but obviously one of my debug patches was still applied.


Subtract months from a string date using moment library

Describe the bug
Unable to subtract months from a string date using moment library
https://stackoverflow.com/questions/70794840/javascript-subtract-months-from-a-string-date-using-moment-library
To Reproduce
https://stackoverflow.com/questions/70794840/javascript-subtract-months-from-a-string-date-using-moment-library
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information if applicable):

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

Moment-specific environment

The time zone setting of the machine the code is running on
The time and date at which the code was run
Other libraries in use (TypeScript, Immutable.js, etc)

Please run the following code in your environment and include the output:
console.log((new Date()).toString())
console.log((new Date()).toLocaleString())
console.log((new Date()).getTimezoneOffset())
console.log(navigator.userAgent)
console.log(moment.version)

Additional context
Add any other context about the problem here.

your issue is solved on SO. I think this should be closed as it's working as expected and most of this issue is just the template.


Remove word

Take down word noose.

Why? It's a perfectly normal English word.

A noose is not just a knot in a rope but one specifically used to hang
people.
[image: Screen Shot 2022-03-02 at 9.11.03 PM.png]
On Wed, Mar 2, 2022 at 9:05 PM Chris @.***> wrote:

Why? It's a perfectly normal English word.
—
Reply to this email directly, view it on GitHub
https://github.com/octokatherine/word-master/issues/121#issuecomment-1057670155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXM2ZX23UT5GEVX6P7IXYDTU6BCC5ANCNFSM5OS3VMAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

So...? How does that make it an invalid word?

It's not invalid.
On Wed, Mar 2, 2022 at 9:21 PM Chris @.***> wrote:

So...? How does that make it an invalid word?
—
Reply to this email directly, view it on GitHub
https://github.com/octokatherine/word-master/issues/121#issuecomment-1057677408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXM2ZX6PNYMW3EKDIPMYNQLU6BD6NANCNFSM5OS3VMAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

If the mere appearance of a 5-letter word in a letter puzzle traumatizes somebody, they should probably not be in the Internet.
There's a lot of words that may or may not be associated with some level of irritation to some. But the reality is that those things and words do exist.

And then all words that can remind you of drugs?

drugs
snort
...

I don't know - it seems to be a rabbit hole without bottom.

Although it might be a compromise to remove it from the list of answers only. Then it is still in the game, but unless you type it yourself it won't be imposed on you to think of it.

Although it might be a compromise to remove it from the list of answers only. Then it is still in the game, but unless you type it yourself it won't be imposed on you to think of it.

@LWChris I believe that is what they meant. When I get requests for words being removed I always remove only from the answer list. I've never had a complaint for a word being an acceptable guessing word because, well, just don't guess it lol

Yes makes sense!

On Mar 4, 2022, at 3:10 PM, Katherine Peterson @.***> wrote:

Although it might be a compromise to remove it from the list of answers only. Then it is still in the game, but unless you type it yourself it won't be imposed on you to think of it.
@LWChris I believe that is what they meant. When I get requests for words being removed I always remove only from the answer list. I've never had a complaint for a word being an acceptable guessing word because, well, just don't guess it lol
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.


feat(Morpho): adding 7 vaults related to Morpho & updating social

Adding 7 ERC4626 compliant vaults, living on Morpho Blue. ✅
Updating the social as well. ✅

❌ I can't specify a content label
Thanks

@vikramarun is it possible for us to implement a small
script that would fetch our API, indexing all ERC4626 vaults, created by what we call MetaMorpho Factory.
The factory is creating ERC4626-compliant vaults.
I added manually the data so far, and wouldl love to automatize this, on Base and on Eth Mainnet!


Error 400 (OAuth2 Error) when launching for first time

Looking forward to using this app, however when I launched it for the first time I got the attached error. I'm on Mac OS 10.11.6.

which version did you install? 1.3.1 is broken and has that known bug since google changed something.
Try: https://github.com/yakyak/yakyak/releases/tag/v1.3.2
If it is not then crap, and try to put the output of the console as well.

I must've installed 1.3.1, because I was unable to unzip 1.3.2. However I
downloaded an app to unzip it now and was able to install successfully.
On Tue, Sep 13, 2016 at 12:49 PM André Veríssimo<EMAIL_ADDRESS>wrote:

which version did you install? 1.3.1 is broken and has that known bug
since google changed something.
Try: https://github.com/yakyak/yakyak/releases/tag/v1.3.2
If it is not then crap, and try to put the output of the console as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yakyak/yakyak/issues/373#issuecomment-246764783, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVJiLiD9mi5cQcYdLgOWJBK5ZzO8Xot9ks5qpuISgaJpZM4J72fN
.

cool, so can you close the issue? :)


Add system fees to docs

You should remove the extra pluses in front of each line.

I've gone ahead and done it, please check.

👍 looks good.


want to export the references

when exporting the paper, there are not references of the paper in the the metadate, and so it can't be bilinked in roam. but it is important for roam.
references is mapped by the title of paper, so they can be linked in roam

Zotero doesn't store paper references in fields that can be easily exported. This add-on is for exporting data that's already in Zotero. The functionality you want isn't appropriate for this add-on.
You could potentially highlight the references list in the paper's pdf and use the add-on Zotfile to extract those references to a Zotero note. Zotero-roam-export will then include that note text in its export. Finally, if you have Roam pages for those papers, they will show up in "Unlinked references" on the papers' Roam pages, and you can link them there.

Thanks, highlight is a good solution, and scholarcy(a chrome extension) is also useful.


update bower.json to real version

fixes "bower lunr.js#2.1 mismatch Version declared in the json (1.0.0) is different than the resolved one (2.1.0)"  warning when installing.
Bower is not a thing of the future any more, but will stick around long enough to support it.   This is just a cosmetic fix (bower is still fetching the right version).

Bower is not a thing of the future any more

Ha! 🔥
Anyway, I've updated both the bower.json and component.json files for the latest release. I'm going to spend a bit of time updating the build system for the project so hopefully in upcoming releases this will happen automatically.
Thanks for the report.

hey, it's not my fault that the bower maintainers drop their own product  :-(


[Fix #11631] Fix an incorrect autocorrect for Style/ArgumentsForwarding

Fixes #11631.
This PR fixes an incorrect autocorrect for Style/ArgumentsForwarding when using arguments forwarding for .() call.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!

Beautifu! :green_heart:


[Feature] Display taming/growth/breeding status of animals

The only feature from WALIA that I'm missing in TheOneProbe is the way WALIA shows information about breeding and growth of animals. So now I"m running both, with WALIA pared down to just the mob info, but this isn't ideal :P

Show time left to grow to adulthood for baby animals

Bonus: Show time left to growth for baby villagers

Show if a mob is breedable through the animal breeding mechanism

Showing things using funky villager-like systems would be a bonus

Show food required to breed
Show "cooldown" time until animal can be bred again
Show if a mob is tameable
Show food required to tame

This would go particularly well with issue #136

I think TOP Addons adds some of these. Check it out

I'm afraid not; I use TOP Addons :)


User Expiration

Overview
At some point the app will be loaded will users and will need to remove old user.  The method for expirtation that is already implemnted in navgiation/index.tsx.
We should consider disabling them or deleting their account

We will play it out during the deployment of the application and as the year continues.
If the Membership system works well than we will simply use that as our expiration method.
Then whenever we need to we will only display or retrieve users that are members
In member directory, any officer admin action that require using list (member of the month selection, )
Full member directory list for officer


Make DevOps as a separate Application from KubeSphere core

Backgroud
Currently, the DevOps backend is part of KubeSphere Core. It's impossible to upgrade the DevOps component independently if a specific version has a crucial bug exist. Also, users cannot install DevOps as an application on Kubernetes.
Proposal
I'd like to suggest that make DevOps be a separate application. Please see also the following points:

Install DevOps application as a Helm charts
Has no dependency on KubeSphere

Only as a regular k8s application
Advanced features could be an enhancement in KubeSphere

What things do we need to do?

[x] Move the DevOps controller-manager and APIServer into a separate repo
[ ] Move the DevOps frontend into a separate repo
[x] Have a Helm chart for the DevOps application
[x] Have a KubeSphere DevOps plugin that contains the connection between KubeSphere and DevOps

Some features should belong to the DevOps project, such as multi-cluster support, enterprise workspace, etc.

/area devops
/kind proposal
/stage alpha

/milestone v3.2

/milestone v3.2


CC upgrade policy

Closes #6520

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5d1b0063b9b3e9a3a1ff7f3a622c5ec940937434/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md

OK here are my thoughts:

OK here are my thoughts:
Minor version section:

let's write out "generally available" instead of GA
Changed it to "major" instead to maintain consistency.
"before" can be more specific -- maybe "when the upgrade begins and again once it's fully applied" or something
The complete statement reads "before and after their clusters are upgraded..."
remove "via email" -- we are hoping to provide the notification in the UI soon, so worth just saying "notify" without being so specific.
Done.

Major version section:

"if you are a CockroachCloud Admin, you will receive an email notifying you when a new major release is available."
Reworded it to make it less clunky.
I'm thinking we don't need to explain the email this much -- most of the info will end up in the email itself. I would just abbreviate to say "customers will be able to opt-in to the new release and will be upgraded within 3 business days of opting in. If you decide not to opt-in, you will remain on the lowest supported version of CRDB until it reaches EOL"
I think the explanation is important for now since this is a new process and we are educating the users about it.

EOL section

"if you are running the lowest supported version" instead of "If you are running older, supported versions" --> there is only 1 version that reaches EOL at a time
Reworded
I would use "to the subsequent" instead of "to the latest"; I found it confusing to read since this relates to when there is an even newer version being introduced, and we are just upgrading them by one release. (so if you are running 19.1, we will email to get you to upgrade to 19.2, not to 20.1)
Ahh..I didn't know that. I assumed you'd be upgraded to the latest release.
Can they ask to be upgraded to the latest version though?

"no later than" --> "at least" . idk why this sounds more forgiving to me :)
Yeah, that sounded weird to me as well but thought it might be necessary legalese. Fixed.
"the older version" --> "that version"
Fixed.

Rollbacks

i would make this header the same size as the EOL, since it only applies to major upgrades
Good point. Fixed.
We should indicate that 7 days is the default (for 20.1 we will have to let people change the finalization period to deal with a schema change issue, so the 7 day time frame won't be enforced for now)
Can you open a ticket and assign it to me about revisiting this section after 20.1 is released and we start upgrading clusters?
LMK if any of this doesn't make sense!

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/64624973ec0f185cf831f17a947c9d3e3ff2a4cf/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md

Everything lgtm except for the section on major upgrade actions!
I do want to educate users, but I don't think I feel comfortable with the description of the options because we don't know for sure yet that these are the options delivered in this specific manner. Could we reframe it so that we can make it clear what the user actions are without specifically calling out what the email will look like & what actions will be called in the email? My concern is that it won't be ready to work the way we want and people will be even more confused having read this beforehand.
Here's what I'm thinking:
"CC admins will be notified when a new major release becomes available, and will be able to take one of the following actions:

opt in to the new release -- [same text as 'upgrade me now']
request a reminder -- [same text as 'remind me']
opt in to the release for when the first point release is available -- [same text as 'wait for point release']
Do nothing -- [same text as 'ok got it'] "

We can update the policy to be more specific when we build out the UI side of the upgrades work, which we will definitely want to provide more guidance on!

Everything lgtm except for the section on major upgrade actions!
I do want to educate users, but I don't think I feel comfortable with the description of the options because we don't know for sure yet that these are the options delivered in this specific manner. Could we reframe it so that we can make it clear what the user actions are without specifically calling out what the email will look like & what actions will be called in the email? My concern is that it won't be ready to work the way we want and people will be even more confused having read this beforehand.
Here's what I'm thinking:
"CC admins will be notified when a new major release becomes available, and will be able to take one of the following actions:

opt in to the new release -- [same text as 'upgrade me now']
request a reminder -- [same text as 'remind me']
opt in to the release for when the first point release is available -- [same text as 'wait for point release']
Do nothing -- [same text as 'ok got it'] "

We can update the policy to be more specific when we build out the UI side of the upgrades work, which we will definitely want to provide more guidance on!

Ahhh..that's good to know. I assumed this was the finalized implementation and will be live before 20.1. Okay, in that case, we can keep it vague and just remove the table/actions for now. Once we implement it, I can add it back. What do you think?

Ah sorry that's my bad, I should have been more clear about the customer communication stuff being WIP.
I think as long as we make it clear that major upgrades are opt-in and the customer will need to act to get upgraded that is sufficient for now to share publically.

Ah sorry that's my bad, I should have been more clear about the customer communication stuff being WIP.
I think as long as we make it clear that major upgrades are opt-in and the customer will need to act to get upgraded that is sufficient for now to share publically.

No worries! Can you check and LMK if if looks okay now?

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/63ee33c3e46f41618c7e7e47f07ec2b2cb0cd28c/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md

LGTM! Thanks Amruta 😃
I'll create an issue about changes to the policy (specifically for major upgrades and rollbacks) for us to track as we nail down more details.

I'm concerned about merging this now, since we are committing to features we haven't implemented yet. To be more specific, I'm concerned about committing to two biz days for minor releases + to having email notifications ready by April. These are certainly our goals, but can we wait until we have the features built to document? I'm not sure I understand docs workflows well; maybe merging this doesn't lead to it being visible to customers right away?

I'm concerned about merging this now, since we are committing to features we haven't implemented yet. To be more specific, I'm concerned about committing to two biz days for minor releases + to having email notifications ready by April. These are certainly our goals, but can we wait until we have the features built to document? I'm not sure I understand docs workflows well; maybe merging this doesn't lead to it being visible to customers right away?

Once this PR is merged, it will be visible to the customers. I share your concerns -- I am not sure why we want to publish the policy before we implement it. I just know internal stakeholders have been asking for it. But I would be totally okay with publishing a non-specific policy for now and then adding the specifics in a follow-up PR. @emily-horing, thoughts?

Yeah, I can understand the concern. Frankly the most important piece to me is the EOL stuff because that notification needs to be done ASAP with 20.1 coming in April or we can't reasonably enforce it.
If we want to generalize the policy further until we have more concrete capabilities I am ok with that, though I do think it would be great if we could put a cap on the minor version upgrades window (maybe 4 days instead of 2? @joshimhoff you can lmk what might make sense here) since that has already come up with a customer when I spoke with them about the policy.

Frankly the most important piece to me is the EOL stuff because that notification needs to be done ASAP with 20.1 coming in April or we can't reasonably enforce it.

Can we just publish the note about only supporting two major versions at a time now? And add the rest in a month or so? I still feel we shouldn't have an external SLA on minor version upgrade timeline until we have the automation. We are close to having the automation, so I don't see why we can't wait a bit longer.
Happy to tak in person too.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/67b182abce78b973e73d3f362f8a3ed3c2d09118/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md

Re: EOL - yes, the major release date is roughly the same as the EOL date but the difference is that we support the last TWO versions of CRDB, not one. So on April 6, 20.1 will be released and 19.1 will reach EOL. Customers already on 19.2 have the option to opt into 20.1, but if you were running 19.1 you will be forced to upgrade to 19.2.
Re: rollback - finalization period is basically limbo between being on one version and another. So if you upgrade from 19.2 --> 20.1, with a 7 day finalization period, your upgrade will complete (all nodes will be running 20.1) and then you have 7 days in which you can rollback (ie. there is a path to downgrade). After the finalization happens, you cannot rollback. You would have to restore from a 19.2 backup to get back on 19.2. CRL cannot roll you back either, so it's not a self-service v. support ticket question.
Hope this clarifies!

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f2950116e7fb6cf1ca28892a354951b0c913d2df/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/cae6dc77363af48f34e8935e6882743319829256/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md

"Auto upgrades after current version EOL" title --> let's remove "current" because it implies that the recent version is reaching EOL. We can replace with "running" or something or just remove the adjective.
With that fix this LGTM!
In the v2 when we update this we should maybe link to the SLA on "high availability" in the 1 node downtime warning. Not a blocker.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/0ed7b95cc8008bee71b3c0cefe0f1f5f3e87c367/
Edited pages:

v19.2/cockroachcloud-cluster-management.md
v19.2/cockroachcloud-upgrade-policy.md
v20.1/cockroachcloud-cluster-management.md
v20.1/cockroachcloud-upgrade-policy.md


Program hanging when trying to connect to gmail.

My program will often hang at client.login when connecting to gmail. I have tested this with multiple gmail accounts. I haven't had a chance to test this with any other imap servers to see if there's a difference. This doesn't happen all the time, but it does happen more often than not.
How could i help to address or work out where the issue is coming from? Btw, I'm new to rust, but not to open source or programming haha.

Huh, that's very weird indeed! I would recommend enabling the debug boolean flag so that the library will print all of the interactions with the server, which should hopefully give some indication of where the hang occurs!

I enabled the debug flag for the session (i think thats where you meant), and when it hangs, it still doesn't output anything, but when it does succeed, it prints out the debug of any commands that are sent once the connection is made. I can also confirm that the error occurs in the imap_login function.

Whoops, imap_login was my code, imap::connect was where it appears to be hanging

That's very suspicious. I think you might have to open up Wireshark or something like it to see what packets are being sent and where the delay actually comes from. We don't really do anything very magical in connect — it just connects to the server and sends the login command.


Make sure we describe the anonymous bit defined in the Blueprints.

Signed-off-by: Josep M. Blanquer<EMAIL_ADDRESS>

LGTM


[Request-For-External] codeunit 90 "Purch.-Post" - Procedure from Internal to Global

Hello, we need the following currently Internal procedure to be set as Global. Can you please check this? Thank you!
[Request-For-External] codeunit 90 "Purch.-Post" - Procedure from Internal to Global
    local procedure DecrementPrepmtAmtInvLCY(PurchLine: Record "Purchase Line"; var PrepmtAmountInvLCY: Decimal; var PrepmtVATAmountInvLCY: Decimal)
    begin
        TempPrepmtDeductLCYPurchLine.Reset();
        if TempPrepmtDeductLCYPurchLine.Get(PurchLine."Document Type", PurchLine."Document No.", PurchLine."Line No.") then begin
            PrepmtAmountInvLCY := PrepmtAmountInvLCY - TempPrepmtDeductLCYPurchLine."Prepmt. Amount Inv. (LCY)";
            PrepmtVATAmountInvLCY := PrepmtVATAmountInvLCY - TempPrepmtDeductLCYPurchLine."Prepmt. VAT Amount Inv. (LCY)";
        end;
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11024.


MIAD-64 Prisoner merge logic change

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.33%. Comparing base (4de8a4e) to head (a8f0895).
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #129      +/-   ##
============================================
+ Coverage     95.23%   95.33%   +0.09%
- Complexity      556      570      +14
============================================
  Files            90       90
  Lines          1741     1778      +37
  Branches         85       92       +7
============================================
+ Hits           1658     1695      +37
  Misses           65       65
  Partials         18       18

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


[WIP] Bump master wait timeout for multi-master clusters

test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3901/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3909/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3912/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3913/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3914/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3915/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3939/
Test PASSed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3941/
Test PASSed.

Jenkins, test this again

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3942/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3943/
Test PASSed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3945/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3946/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3947/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3948/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3949/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3986/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3989/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3990/
Test PASSed.


Spaces (misprints) in column names in scenarios, measurements and parameters tables

Now we simply ignore columns with misprints.
The case with spaces in column names can be simply addressed. I propose to automatically remove space characters in a column name and inform the user by displaying a warning. We may also think of solving a general misprint.

Agreed to automatically remove both leading and trailing whitespaces (trim) and also check reg expressions.

Fixed by https://github.com/hetalang/HetaSimulator.jl/commit/acf9556c7eb23dc6fff83e85ae82b71632d8c3c1


Add Panda 2

Thank you for your contribution! Since you're submitting a closed source app, please include evidence of it being built with Electron. (See submission guidelines or refer to #386 for ways you can show it's an electron app)

@vanessayuenn


Infinite types can cause stack overflow

Other Examples: #707, #663, #349, #956, #983, #820, #987
The following code produces an infinite type that isn't detected.
foo b =
    if | True -> b b
       | 0 >= b -> False

This originated from this issue: https://github.com/elm-lang/elm-repl/issues/45
This is the smallest I could get the example while still producing a stack overflow.
Changing the order of the branches causes a type error (as expected).
It looks like the 0 >= b causes b :: comparable this doesn't rule out it being a function type. When we then hit b b, it seems to infer comparable -> (comparable -> (comparable -> .... which results in a stack overflow.
This explanation it purely based of intuition as I'm not at all familiar with what is actually going on with the type inference.

Just a "me too" on this ... I have hit a variation of this a couple of times where the compiler goes into some infinite loop (but I don't get a stack overflow). I reported the 1st one on the list and was told it was from an incorrect second import statement:
module Reverse where

import Html
import StartApp

main : Signal Html.Html
main =
  StartApp.start { model = 0, view = view, update = update }

view addr m = Html.text "Hello"

update x m = m

I did not record the second one, but it was not related to a faulty import.  treatment.


Remove sourceMappingURL comment even when Stylus compress is true.

The RegExp that removed the sourceMappingURL comment only looked for a comment on its own single line. That caused the RegExp not to match with Stylus option compress: true and the comment not to be removed since all output is on a single line.
That led to multiple sourceMappingURL comments being added with possibly wrong file names.
That caused Firefox Developer Tools to ignore source maps if the first sourceMappingURL was wrong.
The updated RegExp will not match at the beginning of a line, instead it will match any characters, non greedy, until end of comment.

:+1:

pub 2.5.0


Dashboard updates

Updated dashboards and various panels to reflect Cortina changes in the metrics

Looks like the bytes saved from compression metric is broken.
The metric name now includes the compression type.
e.g.
avalanche_network_codec_gzip_accepted_compress_time_count

or
avalanche_network_codec_zstd_accepted_compress_time_count

I'm ok leaving this as a TODO and merging this PR as is


docs: oracle example update

Description
Small change to the oracle docs to be inline with the default slashing params

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added appropriate labels to the PR
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

@adamewozniak since it is changes only in the docs, it doesn't need to be in changelogs?

@adamewozniak since it is changes only in the docs, it doesn't need to be in changelogs?

@RafilxTenfen our changelog guiding principals didn't have a type for it, so I don't think we need to include it.
For larger docs updates it might make sense, but this is just a two-character swap


Windows 10 build issues

having issues building this on Win 10 w/ Qt 5.2.1.  this is probably just an environment config issue, but need to clarify in the setup instructions the process of running cmake / make / etc. on Windows.  can this be built with Visual Studio?  I did compile with VS, but then had VTK DLL linking issues w/ the executable.

I think that I have figured this out.  My PATH was not looking for the VTK DLLs in bin/Release; updated that and all was happy (I think).

commit ce99ae3168e2d9d3030cdd42544b23b8608919cb


Restart Script?

Good afternoon, is there a script that restarts all servers at the same time? Instead of recursively as it already does. Because it takes too long to reboot all servers and I've searched around here, but I can't find anything.
Thanks!

Something like:
for i in $(arkmanager list-instances --brief); do
    arkmanager restart @$i &
done
wait

Thanks @klightspeed!


[Bug]: Monitors with missing Model / MCCS version fields are not detected

Steps for reproducing the issue
Having a bad monitor with unspecified Model and MCCS version :/
What is the buggy behavior?
Wluma does not detect one of my two monitors. See logs.
What is the expected behavior?
Even with broken/missing information, this monitor is able to change brightness and other parameters over DDC. Wluma should be able to support those partially broken monitors as well.
Logs
$ RUST_LOG=debug wluma
[2022-02-13T19:48:56Z DEBUG wluma] Using Config {
        als: Time {
            thresholds: {
                11: "normal",
                0: "night",
                7: "dark",
                16: "normal",
                20: "night",
                9: "dim",
                18: "dark",
                13: "bright",
            },
        },
        output: [
            DdcUtil(
                DdcUtilOutput {
                    name: "1908FP",
                    capturer: None,
                    min_brightness: 1,
                },
            ),
            DdcUtil(
                DdcUtilOutput {
                    name: "W2443",
                    capturer: None,
                    min_brightness: 1,
                },
            ),
        ],
    }
[2022-02-13T19:48:58Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["W2443 "]
[2022-02-13T19:48:58Z WARN  wluma] Skipping '1908FP' as it might be disconnected: Unable to find display
[2022-02-13T19:49:00Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["W2443 "]
[2022-02-13T19:49:00Z DEBUG wluma::brightness::ddcutil] Using display 'W2443 ' for config 'W2443'
[2022-02-13T19:49:00Z INFO  wluma] Continue adjusting brightness and wluma will learn your preference over time.

Version
wluma 4.1.2-1 from AUR
Environment
Still sway on Arch Linux.

Readable features declared in capabilities string: 02 0b 0c 0e 10 12 14 16 18 1a 1e 20 30 3e 52 6c 6e 70 ac ae b2 b6 c0 c8 c9 ca d6 df

MCCS (VCP) version reported by capabilities: Unqueried
MCCS (VCP) version reported by feature 0xDf: 2.0
Versions do not match!!!

All readable features declared in capabilities were found by scanning.

Features found by scanning but not declared as capabilities:
   Feature x60 - Input Source
   Feature x68 - Unknown feature
   Feature x9b - 6 axis hue control: Red
   Feature x9d - 6 axis hue control: Green
   Feature x9f - 6 axis hue control: Blue
   Feature xff - Manufacturer Specific

Color temperature increment (x0b) = 184 degrees Kelvin
Color temperature request   (x0c) = 2
Requested color temperature = (3000 deg Kelvin) + 2 * (184 degrees Kelvin) = 3368 degrees Kelvin

Could you please add the following log:

    ddc_hi::Display::enumerate()
        .into_iter()
        .for_each(|mut display| {
            log::debug!(
                "update_capabilities result: {:?}",
                display.update_capabilities()
            );
        });

before this line:
https://github.com/maximbaz/wluma/blob/0c49755fdcf19b22841844df6508f29c31975ce2/src/brightness/ddcutil.rs#L82
and show the output here?

The full log is now:
[2022-02-13T21:24:12Z DEBUG wluma] Using Config {
        als: Time {
            thresholds: {
                7: "dark",
                20: "night",
                16: "normal",
                9: "dim",
                0: "night",
                13: "bright",
                18: "dark",
                11: "normal",
            },
        },
        output: [
            DdcUtil(
                DdcUtilOutput {
                    name: "1908FP",
                    capturer: None,
                    min_brightness: 1,
                },
            ),
            DdcUtil(
                DdcUtilOutput {
                    name: "W2443",
                    capturer: None,
                    min_brightness: 1,
                },
            ),
        ],
    }
[2022-02-13T21:24:15Z DEBUG wluma::brightness::ddcutil] update_capabilities result: Ok(())
[2022-02-13T21:24:16Z DEBUG wluma::brightness::ddcutil] update_capabilities result: Err(Failed to parse MCCS capabilities

    Caused by:
        [255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 97, 115, 115, 101, 116, 95, 101, 101, 112, 40, 52, 48, 41, 0, 255, 255, 109, 99, 99, 115, 95, 118, 101, 114, 40, 50, 46, 48, 41, 0, 255, 255, 9, 0, 0, 22, 161, 30, 0, 0, 23, 161, 30, 30, 0, 23, 161, 30, 60, 97, 115, 115, 101, 116, 95, 101, 101, 112, 40, 52, 48, 41, 109, 99, 99, 115, 95, 118, 101, 114, 40, 50, 46, 48, 41]:Eof)
[2022-02-13T21:24:16Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["W2443 "]
[2022-02-13T21:24:16Z WARN  wluma] Skipping '1908FP' as it might be disconnected: Unable to find display
[2022-02-13T21:24:20Z DEBUG wluma::brightness::ddcutil] update_capabilities result: Ok(())
[2022-02-13T21:24:21Z DEBUG wluma::brightness::ddcutil] update_capabilities result: Err(Failed to parse MCCS capabilities

    Caused by:
        [255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 97, 115, 115, 101, 116, 95, 101, 101, 112, 40, 52, 48, 41, 0, 255, 255, 109, 99, 99, 115, 95, 118, 101, 114, 40, 50, 46, 48, 41, 0, 255, 255, 9, 0, 0, 22, 161, 30, 0, 0, 23, 161, 30, 30, 0, 23, 161, 30, 60, 97, 115, 115, 101, 116, 95, 101, 101, 112, 40, 52, 48, 41, 109, 99, 99, 115, 95, 118, 101, 114, 40, 50, 46, 48, 41]:Eof)
[2022-02-13T21:24:21Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["W2443 "]
[2022-02-13T21:24:21Z DEBUG wluma::brightness::ddcutil] Using display 'W2443 ' for config 'W2443'
[2022-02-13T21:24:21Z INFO  wluma] Continue adjusting brightness and wluma will learn your preference over time.

Cool, thanks!
Could you please try ddcutil-add-id branch, and provide debug logs once more if it still doesn't work? It should hopefully allow you to also use DDC ID field (whatever that is, you will see what wluma detects in debug logs), if getting name and models fails, instead of skipping that monitor as before.

update_capabilities result: Err(Failed to parse MCCS capabilities

This is what I was afraid of... In order to populate the name and model, so that we can use it for matching, we call update_capabilities from the library, which fills this info, and it fails for one of your monitors.
The library also has update_from_ddc function, but that one only fills in mccs version and database, not any of the identifying information about the monitor which we could use to match against....
However it looks like ID field is always present. So in the branch I added it to the string that you can match in your config, and ignoring the error from update_capabilities function.
This could be problematic though, @cyrinux and I saw some ghost entries (the same monitor would be listed twice, and only one of them was actually usable, the one for which update_capabilities function succeeded), so I'm not sure yet if this would be a viable fix to merge in the current form, even if it solves your problem...

Thanks! This solves the detection problem for me.
I modified your change and the ID is not even needed! I guess ddcutil throws an error, so the ok() function stops the handling of this monitor. If you ignore the result value, the model name and serial number are available.
The relevant section is now:
    let displays = ddc_hi::Display::enumerate()
        .into_iter()
        .filter_map(|mut display| {
            let _ignored = display.update_capabilities();
            let empty = "".to_string();
            let merged = format!(
                "{} {}",
                display.info.model_name.as_ref().unwrap_or(&empty),
                display.info.serial_number.as_ref().unwrap_or(&empty)
            );
            Some((merged, display))
        })
        .collect_vec();

And the debug log is now:
[2022-02-14T12:48:21Z DEBUG wluma] Using Config {
        als: Time {
            thresholds: {
                18: "dark",
                9: "dim",
                0: "night",
                16: "normal",
                7: "dark",
                11: "normal",
                13: "bright",
                20: "night",
            },
        },
        output: [
            DdcUtil(
                DdcUtilOutput {
                    name: "1908FP",
                    capturer: None,
                    min_brightness: 1,
                },
            ),
            DdcUtil(
                DdcUtilOutput {
                    name: "W2443",
                    capturer: None,
                    min_brightness: 1,
                },
            ),
        ],
    }
[2022-02-14T12:48:23Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["W2443 ", "DELL 1908FP G314H86D7UFA"]
[2022-02-14T12:48:23Z DEBUG wluma::brightness::ddcutil] Using display 'DELL 1908FP G314H86D7UFA' for config '1908FP'
[2022-02-14T12:48:25Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["W2443 ", "DELL 1908FP G314H86D7UFA"]
[2022-02-14T12:48:25Z DEBUG wluma::brightness::ddcutil] Using display 'W2443 ' for config 'W2443'
[2022-02-14T12:48:25Z INFO  wluma] Continue adjusting brightness and wluma will learn your preference over time.

Maybe you can write up some smart detection if update_capabilities fails, but the values are still available?
This might be a cleaner approach, which is better to merge and maintain.
I did not experience duplicate monitor entries.
Another idea: I believe ddcutil detect gets monitor info from EDID, so you could get manufacturer/model/serial nr. from there.
The next problem I experience: I2C errors. Wluma spam-reports [ERROR wluma::brightness::controller] Unable to get brightness value: DDC/CI I2C error: No such device or address (os error 6), the kernel log contains some kernel: i2c i2c-0: sendbytes: NAK bailout. i2c-0 is the other monitor, so not related with this issue.

Cool, thanks for confirming!
I think we'll have to keep IDs because this is what I'm getting when only one external monitor is connected, if we don't ignore update_capabilities errors (as in main branch):
Discovered displays: ["22794 DELL P2317H 9KFDW67326GB", "22793  ",  "22796 DELL P2317H 9KFDW67326GB"]

As you can see it's actually generating 3 entries, one of which has no info (and failed update_capabilities run), two others have exactly the same make and model, but different ID, and only for one of them the update_capabilities succeeded.
If wluma picks the wrong one in the list above, then it will not be able to control brightness...
However before thinking how to solve it, do I understand it correctly that wluma is still unable to get/set brightness for your screen? In other words, I2C errors are not just fake errors, but actually screen is not being managed by wluma? If that's the case, it sounds like the library we are using is simply unable to deal with weird monitors, for which update_capabilities fails...

diff --git a/src/brightness/ddcutil.rs b/src/brightness/ddcutil.rs
index 09a5108..eb8fd77 100644
--- a/src/brightness/ddcutil.rs
+++ b/src/brightness/ddcutil.rs
@@ -69,10 +69,12 @@ fn find_display_by_name(name: &str) -> Option {
.filter_map(|mut display| {
display.update_capabilities().ok().map(|_| {
let empty = "".to_string();

           let empty_int = 0;
           let merged = format!(

               "{} {}",

               "{} {} {}",
               display.info.model_name.as_ref().unwrap_or(&empty),

               display.info.serial_number.as_ref().unwrap_or(&empty)

               display.info.serial_number.as_ref().unwrap_or(&empty),

               display.info.serial.as_ref().unwrap_or(&empty_int)
           );
           (merged, display)
       })

I'm not a rust programmer, but this works for me :)

Could you explain some more, what was your issue and how does the patch help? I'm still at a loss whether it's possible for wluma to control brightness of these "weird" monitors or the patches are just to hide the errors...

It would be great if we could have a manual override for the i2c address to get around this. For example, I have two identical monitors which actually have identical EDID data. Running ddcutil detect results in:
Display 1
   I2C bus:  /dev/i2c-6
   DRM connector:           card0-DP-1
   EDID synopsis:
      Mfg id:               ACR - Acer Technologies
      Model:                ED273UR
      Product code:         1682  (0x0692)
      Serial number:
      Binary serial number: 0 (0x00000000)
      Manufacture year:     2018,  Week: 17
   VCP version:         2.1

Display 2
   I2C bus:  /dev/i2c-7
   DRM connector:           card0-DP-2
   EDID synopsis:
      Mfg id:               ACR - Acer Technologies
      Model:                ED273UR
      Product code:         1682  (0x0692)
      Serial number:
      Binary serial number: 0 (0x00000000)
      Manufacture year:     2018,  Week: 17
   VCP version:         2.1

But wluma only sees:
[2023-03-07T19:16:56Z DEBUG wluma::brightness::ddcutil] Discovered displays: ["ED273UR ", "ED273UR "]

This makes it impossible to initialize both displays or even one of them.

Closing due to lack of activity, please leave a comment or open a new issue if this is still relevant.


feat: Model App [WIP]

TODO:

Doesn't support Select Existed feature even though I wrote the UI already. Going to implement.
url and name of a ModelApp can be unique. It depends on our product logic, but a note to user is required at least to clarify what's going on when user wanted to create an app, while we have the same existed.
The UI of a model's details page can be improved.
The lack of automatically deploy app. This must be implemented to use this feature as a demo.

LGTM


Fix description for 'pack install' Alias (v2.1)

See original https://github.com/StackStorm/st2/pull/3066
(cherry picked from commit 928f240) for inclusion in v2.1 branch.

Current coverage is 77.56% (diff: 100%)

Merging #3067 into v2.1 will increase coverage by 0.26%

@@               v2.1      #3067   diff @@
==========================================
  Files           430        430
  Lines         22017      22017
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          17020      17077    +57
+ Misses         4997       4940    -57
  Partials          0          0

Powered by Codecov. Last update 7a8a8c7...62560b0


Roli Seaboard Rise 25: gate intermittent

Gate only seems to be outputting on certain notes.   I can pitch track fine once I've found a note that registers a gate, so that part seems ok.  The pressure and axis tracking seems to work as expected too.
I've set the pitch tracking to match my roli dashboard, and MPE is on etc.  All the context menu settings are set to ROLI stds.  MIDI Channel is 2 (set to 2-16 on the roli dashboard).

Can you set to channel two only? It's likely going through all channels instead of just one.

In MPE mode, you can only set a range.  The smallest being 2..3
If I set it to that, I can't seem to find any key that produces a gate.
On Tue, Feb 6, 2018 at 10:52 PM, Bruno Afonso<EMAIL_ADDRESS>wrote:

Can you set to channel two only? It's likely going through all channels
instead of just one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bafonso/MPE/issues/1#issuecomment-363592821, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AgdqaFvkCOCwpBK4fg7ZwvT4-sF45O2Fks5tSNelgaJpZM4R7oRo
.

Can you use the program midi monitor and save the output from rise?

Good idea!  I'll send you a report if I get chance tomorrow (getting late
here!)
On Tue, Feb 6, 2018 at 11:23 PM, Bruno Afonso<EMAIL_ADDRESS>wrote:

Can you use the program midi monitor and save the output from rise?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bafonso/MPE/issues/1#issuecomment-363600482, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AgdqaIXApEXMZZsHen4nE9RECgP6sCLoks5tSN7zgaJpZM4R7oRo
.

Hi there.   I've attached the output from MIDI-OX.
The first note (F2) was the only one that produced a gate.   I held it a short time, then pressed some other random notes for a similar length.
Also I've noticed another slight possible bug - the global channel selection in the context menu seems to revert back to 16 - Haken Continuum whenever I reload the patch.  Not a major thing, and it didn't actually seem to stop what is working from working, but thought you might want to know.
MIDI debug info:
midioutdbg.txt
Regards

This is a monophonic MPE converter so you will need to set your channel to single and select only channel 2. I will probably create an option where I will parse all channels 2-16 and just pick the last note played.

I will add the menu settings to be recalled once you reload the project, I forgot to do that to the monophonic version.

Put this down to user error!   Switched off the MPE mode and it works.


Rename .travis.yml to circle.yml

The .yml file was names as .travis.yml which should be named as circle.yml . if the yml file is changes then it should be possible to run the code test on CircleCi.

We are using Travis CI, so file is properly named.


Service 'workspace' failed to build : Build failed

try docker compose --no-cache --pull build workspace


the live traffic not show in the panel

the live traffic not show in the panel
https://www.dropbox.com/s/wyv2xzxwd61v30j/2018-08-29_1-38-38.png
https://www.dropbox.com/s/mcwe0gtlcjengxj/2018-08-29_1-41-46.png
how to fix this please

are you sure you have the right config ?

Iam geting down and server refusing conection

i have same issue too ! please help me


Pbrmaterial corrections

Things corrected:

create a function for repeated calculation in point and spot lights.
correction on the kd variable following the Helmholtz Reciprocity rule.
correct the alpha on outColor variable.
reestructuration of the material struct and added location layout.
binding textures with a fixed binding point in the shader.

Task linked: CU-865btp3x5 Code


Overflow menu Option URL does not open a browser on mobile (Android)

Description
I apologize if this is unrelated to BoltJS specifically, but I discovered a bug while testing my application.
When I use a URL in an Option object (https://api.slack.com/reference/block-kit/composition-objects#option) in an Overflow menu (https://api.slack.com/reference/block-kit/block-elements#overflow) - it works fine on desktop (it opens the URL in the browser, after triggering the action callback).
Unfortunately same button does not work on mobile (Android) - I can see the action callback being hit, but the URL is not being loaded in the browser, it just does nothing.
My speculation is that it could be a bug in the Android app itself, but I thought I post it here too, maybe I'm doing something wrong?
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 3.6.0
node version: v14.16.0
OS version(s):
Steps to reproduce:

Create an Overflow Menu with an Option that has a URL
Observe the URL being opened in the browser when the Option is clicked in a Desktop App
Observe the URL not being opened in the Android app

Hi @timurso, thanks for taking the time to write in.
Since I myself do not own any Android devices, I haven't checked the behavior with Android OS yet. That being said, the URL property does work for me with Desktop, web browser, and iOS clients. The issue that you encountered might be due to the Slack Android client's lack of feature support or something specific to your device settings.
As you mentioned, we are not using this issue tracker for tracking the issues for mobile clients here. I am sorry for bothering you but could you contact our customer support agents instead? You can submit an inquiry to them either via /feedback command in your Slack workspace or https://my.slack.com/help/requests/new. It'd be appreciated if you could understand this.


fix(ui): More Advanced Filters Fixes

Description
This PR fixes a few Advanced Filters bugs:

Change text to autocomplete for Image Operating System (jira)
Remove Image Created Time and Image Scan Time (jira)
Remove the term Image from Image CVE (jira)
Fix issue with unchecking an option in the Checkbox Select (jira)
When using the condition-number type for a search, it should not display undefined if the condition is not changed at least once (jira 1) (jira 2)
Should be able to clear CVE Snoozed values from dropdown (jira)

Also, the tests needed to be updated because of a few changes.

/retest

/retest


namespace not specified on android

Hi,
I'm trying to update my build to Gradle 8 and Android Build Plugin to 8.1.3 but this plugin isn't specifying it's namespace, leading to a compile error:
* What went wrong:
Failed to query the value of property 'buildFlowServiceProperty'.
> Could not isolate value org.jetbrains.kotlin.gradle.plugin.statistics.BuildFlowService$Parameters_Decorated@192fc78d of type BuildFlowService.Parameters
   > A problem occurred configuring project ':flutter_osm_plugin'.
      > Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
         > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

           If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

It would be nice if you could specify the namespace in your android configuration 😊

Tried that, the issue is still there

i will try to update from my side and tell you what should dl

I also encountered a similar error, tried to correct it but by adding namespace myself but failed.

i will publish fix for it

0.70.1 fixes the issue, thanks 👍


[Сhild Information] The "Зберегти" button works several times, and returns the browser pages back when you quickly click the "Зберегти" button several times.

Environment: Windows 10, 64-bit, Google Chrome 117.0.5938.88,
Windows 10, 64-bit, Microsoft Edge 114.0.1823.67.
Reproducible: always.
Description
When you quickly press the "Save" button, it works several times and returns the browser pages several pages back.
Preconditions

Go to (https://oos.dmytrominochkin.cloud/)
The user is authorized as a parent.
At least 1 child must be created.

Steps to reproduce

Go to the "Інформація про дітей" tab.
Select a child from the list and Click on the "Редагувати" button.
Quickly press the "Зберегти" button several times.

Actual result
The information is saved, the user returns several pages back.
VIDEO - https://app.screencast.com/eHZPgprOZmTn6
Expected result
The information is saved, the user returns to the "Особиста інформація" page.
Labels to be added
"Bug", Priority ("pri: High"), Severity ("severity: High").

The error is still there. The defect continues to reproduce.

Bug fixed in #2257 pull request


Oracle Versions supported

I'm sorry if I missed this information - which versions of Oracle are supported with this connector? We have Oracle 11g2 and looking to test this connector shortly.
Also, please correct me if I'm wrong; but Golden Gate license is not required to use this connector, right?
Thanks

Hi,
All versions are supported. With last developments  last version of Oracle which has some desupport feature are also supported.
No Golden Gate license is required . Connector is based on logminer utility .
Thanks


Hypervisor max guest limit

ISSUE TYPE

Improvement Request

COMPONENT NAME
Hypervisor / Management Server

CLOUDSTACK VERSION
master

CONFIGURATION
Max Guest Limit
SUMMARY
We currently enforce the number of Guests / Instances which can be run on a hypervisor. This is a fixed number not tied to RAM or CPU.
This limit should be removed. If the hypervisor has enough RAM and CPU we should think the HV is capable.
There should be no limit on the amount of Instances on a hypervisor

I think that for XenServer it might still be needed. However, if a user tries to deploy in XenServer, more VMs than it allows to, an exception is thrown, and the exception handling in ACS would catch it. So, it might also not be needed, because the host would be then put in avoid state, and the VM deployment would be retried somewhere else.

tnx @rafaelweingartner , if you say the error handling is good enough to deal with it, we should go for it, it is not for ACS to decide what a hypervisor can, just to deal with it.

one more remark in hindsight, @wido @rafaelweingartner . trying and failing is a big roundtrip from the deployment planner to the hypervisor. In the case of xen one might still want the ability to set a max if it is known anyway.

Hi @wido is there any work on this issue?

Hi @wido is there any work on this issue?

There has not been any work on this issue

We need the docs to be updated on per hypervisor basis for example;
VMware and XenServer - specifies in the docs no. of max hosts in a cluster in release notes (version-specific)
KVM - likely no concept of pool or cluster, so pratically as many no. of processes you can run on Linux
cc @nvazquez

@wido @rhtyd @nvazquez I've created a PR to skip guest limit check for KVM in code.
Do you guys suggest we also skip check for Xenserver?
We also have a default limit for maximum data volumes for a VM (used 6), should we make any changes there as well?
https://github.com/apache/cloudstack/blob/main/server/src/main/java/com/cloud/storage/VolumeApiServiceImpl.java#L3446-L3450

@wido @rhtyd @nvazquez I've created a PR to skip guest limit check for KVM in code.
Do you guys suggest we also skip check for Xenserver?

I don't work with Xenserver, so I can't comment on that.

We also have a default limit for maximum data volumes for a VM (used 6), should we make any changes there as well?
https://github.com/apache/cloudstack/blob/main/server/src/main/java/com/cloud/storage/VolumeApiServiceImpl.java#L3446-L3450

I don't see any reason why 6 should be the limit. I always thought the limit was 10.
https://rwmj.wordpress.com/2017/04/25/how-many-disks-can-you-add-to-a-virtual-linux-machine/
That seems to imply that with KVM you can add 256 disks if you want.

For KVM, it may always end up 32 as the default version for KVM in hypervisor_capabilities table is set to 32,
MariaDB [cloud]> select * from hypervisor_capabilities where hypervisor_Type='KVM';
+----+------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| id | uuid | hypervisor_type | hypervisor_version | max_guests_limit | security_group_enabled | max_data_volumes_limit | max_hosts_per_cluster | storage_motion_supported | vm_snapshot_enabled |
+----+------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| 13 | 13   | KVM             | default            |               50 |                      1 |                     32 |                  NULL |                        1 |                   1 |
+----+------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+

For KVM, it may always end up 32 as the default version for KVM in hypervisor_capabilities table is set to 32,
MariaDB [cloud]> select * from hypervisor_capabilities where hypervisor_Type='KVM';
+----+------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| id | uuid | hypervisor_type | hypervisor_version | max_guests_limit | security_group_enabled | max_data_volumes_limit | max_hosts_per_cluster | storage_motion_supported | vm_snapshot_enabled |
+----+------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+
| 13 | 13   | KVM             | default            |               50 |                      1 |                     32 |                  NULL |                        1 |                   1 |
+----+------+-----------------+--------------------+------------------+------------------------+------------------------+-----------------------+--------------------------+---------------------+

I personally don't see any reason why somebody would go over 32 disks attached to a single VM. For now I think we can maintain that limit.


Compile error on Windows 10.

Hello I am trying to compile fsm on Windows.
Everything is fine with cmake
but I have errors with msbuild such as :
"error C2039: 'iota' n'est pas membre de 'std' [C:\Users\march\Barnes2020-FillSpillMerge\build\submodules\dephier
submodules\richdem\richdem.vcxproj]"
This is not documented so I am not sure it can be compiled on Windows.
Thanks for your help.

What compiler version and compiler version are you using?

I am using Microsoft (R) Build Engine version 17.2.1+52cd2da31 pour .NET Framework
Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.32.31326


Add prestart/poststop hooks to the spec

Related to #34
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

On Fri, Jul 24, 2015 at 12:04:06PM -0700, Mrunal Patel wrote:

Related to #34

Why not just add this to #34?  I don't see a need to land the docs and
spec changes in independent PRs ;).

In fact I think we should land docs and spec code at the same time. Makes it easier to read the git history and understand what/why together.


Issue 45857: Add header locking for dataset security page table

Rationale
https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=45857
Changes

Add CSS for position: sticky to table header row for study dataset security page

Closing in favor of PRs targeting 22.7.


RFC: Having similar behaviour for useQuery and useMutation (react)

Summary
useQuery and useMutation have very different behaviours specifically w.r.t the tuples they return. I like the way useMutation works. It returns [result, executeMutation] when called. useMutation does not automatically make an initial request unlike useQuery which makes an api call automatically unless specified otherwise using the pause option. The other thing is executeQuery returned from useQuery does not return a promise which makes it difficult to work with especially when queries need to be executed when say a button is pressed and things need to be handled from there on based on the response from that query.

Proposed Solution
executeQuery should work exactly like executeMutation, meaning it should return a promise which resolves to the response of that query. Also, I would personally prefer useQuery to not execute automatically because that seems more logical to me and there should be an option to execute automatically. Basically the default behaviour should be opposite of what it is right now because the current behaviour is not at all intuitive.

Requirements

Are you using GraphQL Code Generator? Because if so you could switch to generating TypedDocumentNodes which work with any of our APIs where you pass queries. https://www.graphql-code-generator.com/docs/plugins/typed-document-node

I have pause: true and I tried calling executeQuery "manually". It does not seem to work the first time, but calling it again seems to work. Any idea about this or should I open a separate issue for this?

It's possible that something isn't quite right there; either in usage or something else, so feel free ❤

Hi guys! Is there any docs on how to use https://www.graphql-code-generator.com/docs/plugins/typed-document-node with https://www.graphql-code-generator.com/docs/plugins/typescript-urql?

@frederikhors
If you'd like to use typed-document-node, you don't need to use typescript-urql plugin.
All you need to do is just passing generated TypedDocumentNode to useQuery:
import { useQuery } from 'urql'
import { GetPostDocument } from './generated/graphql'

const [res, executeQuery] = useQuery({
  query: GetPostDocument,
  variables: { id: "1" },
})

@kitten
Sorry for cutting in, but what is the desired behavior of pause: true and calling executeQuery situation?
It doesn't seem to be "executed" in that situation unless set pause: false manually as it uses the same context.

Copying this over from #1982, since it belongs here:

@Miraj98: "Urql really needs to have a separate useLazyQuery hook. I know pause: true achieves that but it's not good api design and is frustrating to use. The perfect solution is having a separate hook for this which returns executeLazyQuery. We can have this function accept the query variables directly instead of passing them through the hook. This will also be more efficient because useQuery runs a few checks every time the inputs to the hook change. Hence a separate lazy hook will have a simpler implementation and will be more performant.
@Miraj98: "I know there have been previous discussions around adding useLazyQuery but there seems to be a lack of intent to add that api. Mostly the reason given is pause: true works just fine. But honestly it's not a great way to implement it given a better approach is possible."

And my reply:

I honestly don't think that's accurate, sorry 😅 In any case, what it's always been is a one-switch solution to toggle between the two modes. That's an important distinction, since it also enables you to pause any ongoing changes as you see fit, meaning that the hook enables a lot more use cases than two separate ones.
You can feed it changing inputs and it will reactively change what query it actively provides results for. When you combine that with pause you can declaratively ignore certain inputs, e.g. for a search form with a minimum length inputs, or form validation.
You can enable pause and imperatively feed it inputs and trigger the hook with executeQuery.
You can defer the query either by setting pause to false later on or calling the executeQuery function as a one-off.
I could go on, but basically, it enables all use-cases that you could throw at it, while remaining a declarative and reactive hook. For all imperative-only patterns (if I press a button, then something happens, and only then) we'd always recommend the client methods. That's what a lazy hook would otherwise often be used for, which would be redundant 😅
Anyway, I can hope you come around to this API design, however, a note on the bug is, just because we regressed on a feature or API — while it obviously alters trust and perception to it temporarily — doesn't make it redundant in my opinion

Closing it as pause delivers the functionality of useLazyQuery

@kitten I think it is fairly common to load data based on user action. In that case generated client.query(GetSomeDocument, { data: here }).toPromise(); would make to improve the type safety. e.g in my case I'm loading upload url when user selects file. I don't want to tie it to component lifecycle since that would be unnecessary and increase complexity. It is cleaner and easier to understand to do it directly in a callback.
I don't think that hook is needed for that kind of case, instead it could be totally react agnostic.

Adding a bit more on what @villesau  has mentioned, here's some example of what useLazyQuery can be:
`import { TypedDocumentNode } from '@graphql-typed-document-node/core';
import { CombinedError, OperationContext, RequestPolicy } from '@urql/core';
import { DocumentNode } from 'graphql';
import { useClient } from 'urql';
export interface UseLazyQueryState<Data = any> {
data?: Data;
error?: CombinedError;
}
export interface UseLazyQueryArgs<Variables = object, Data = any> {
query: string | DocumentNode | TypedDocumentNode<Data, Variables>;
variables?: Variables;
requestPolicy?: RequestPolicy;
context?: Partial;
}
const useLazyQuery = <Data = any, Variables = object>(
args: UseLazyQueryArgs<Variables, Data>,
) => {
const client = useClient();
return async (): Promise<UseLazyQueryState> => {
const query = args.query;
const variables = args.variables ?? {};
const { data, error } = await client.query(query, variables).toPromise();
return { data, error };
};
};
export default useLazyQuery;
`


Submit https request using http1.1  protocol

Hello, I'm a newcomer to Krakend.
I've configured an endpoint that has a backend that utilizes https with client certificates.
However, I get this error when making the request to the endpoint.
[GIN] 2019/09/19 - 00:37:55 | 500 | 558.632168ms | ##.###.##.## | GET    /dev
Error #01: Get https://###########/thunder/kale: stream error: stream ID 3; HTTP_1_1_REQUIRED
It seems like Krakend will only submit https requests with http2 protocol.
Is there a way we can configure which http protocol a request can use?

I've moved this issue to krakend repo, instead of krakend-ce.
https://github.com/devopsfaith/krakend/issues/285


Hide the action coloumn in the "user edit colulmn" modal of the new list component

In the new list component we allow users to hide/show and change the order of columns,
the "actions" should not be allowed to be changed, the action should be hidded in this modal

Fixed in https://github.com/kubev2v/forklift-console-plugin/pull/189

:cake:


Font class missing

The build is failing because org.egordorichev.lasttry.graphics.Fonts no longer exists

Where is it missing? I mean, witch file fails to build? Font class was replaced with Assets.

UIButton.java


Menus/sections under "Staged files" and "Unstaged files" disappeared.

Mentioned sections disappeared and I can't find a way for them to appear.

Hi,
just hover on the right border until the mouse pointer changes to a horizontal arrow. Then click and pull to the left.

This is a good first issue to implement a button/Checkbox to show hide the Treeview. So it is more intuitive to get it back

Hi,
just hover on the right border until the mouse pointer changes to a horizontal arrow. Then click and pull to the left.

i don't get it because it reduces the window if do that on MacOS

Hi,
just hover on the right border until the mouse pointer changes to a horizontal arrow. Then click and pull to the left.

i don't get it because it reduces the window if I do that on MacOS

Make it fullscreen and then pull.


Provide a "reasonable" way for early adopters to integrate into a Gradle build

IIRC, the existing instructions at https://github.com/jspecify/nullness-checker-for-checker-framework/releases/tag/v0.0.1 are not absolutely definitively unacceptable, but:

They would have to be updated for a new release published to GitHub.
The "Ivy" settings that our current hack uses look like they may be global, so anyone who really uses Ivy (or who uses a similar hack!) would likely run into problems with our setup.
Things would just be nicer if we actually uploaded to Maven Central.

So the main thing here is "upload to Maven Central." We already have permissions for org.jspecify there. That might be enough to upload artifacts under a new artifact ID? The other part of the process is to figure out how to actually upload the relevant jars, poms, manifests, or whatever that our own build process may or may not automatically spit out. Since we're distributing both a Checker Framework fork and a plugin, that might actually mean a couple new artifacts, or else we need to find a way to merge them.
Then there's the smaller matter of producing an updated copy of the written instructions.
We could in theory go further by making our checker always automatically apply the -AassumePure, -AcheckImpl, and -AsuppressWarnings flags that we currently force people to add themselves, but we'll quite possibly not bother for these early days of testing.

If you want early adopters I think that this (and the Maven counterpart) needs to be resolved sooner than later. Expecting users to build the library themselves is a big hinderance to its usage.


transactionInfo.pinpoint throws NPE

What version of pinpoint are you using?
1.6.2
Describe your problem**
most application trace dose not work normally.web ui shows an ERROR.the ERROR shows java.lang.NullPointerException.It happened in our product enviroment,so I can not debug normally,I print log to trace the error,but the code throws exception looks normally,I don't know why.
What have you done?
Steps you have taken to trigger the problem, for example:

Launched application with agent
web ui shows that collector trace application normally
when I want see the detail transactionInfo,web ui show ERROR.

Screenshots

RecordFactory:156

It has print out record info normally

@yale2
We do not  technical support for past versions.
Please update to the latest version (1.8.3), if encounter the same problem, please ask us again.


Extract PluginAuthorServices from plugins project

Removes the PluginAuthorServices class from the plugins project and distribute it's components to more appropriate JVM platform projects.
This allows for removing further dependencies from plugins and should make these services easier to locate.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedbackLinux build

@bot-gradle test QFL

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedbackLinux build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge


[8.x] Using a different composer file

For now, users should only use composer.json file with no choice.
Even though the official Composer documentation - https://getcomposer.org/doc/03-cli.md#composer allows it.
Multiple composer files are required if a project has multiple configurations. For example, composer-dev.json specifies the dependencies for the latest (develop) versions, and composer.json specifies the dependencies for specific versions.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Update install instructions to match stellar-docs

What
Update install instructions to match stellar-docs
Why

https://github.com/stellar/stellar-docs/pull/1045

The e2e build is broken because quickstart was updated with the new rpc api that contained breaking changes.


Worker jobs getting lost since they can not download storm conf file

I launched my first topology and seems like the worker processes can not come up since they can not download the conf file. Here is what I see in the logs.
I0901 00:16:35.558715 19563 fetcher.cpp:214] Fetching URI 'http://hdfs-nn.myhost.com:50070/webhdfs/v1/binaries/storm-mesos/storm-mesos-0.9.3.tgz?op=OPEN'
I0901 00:16:35.558866 19563 fetcher.cpp:125] Fetching URI 'http://hdfs-nn.myhost.com:50070/webhdfs/v1/binaries/storm-mesos/storm-mesos-0.9.3.tgz?op=OPEN' with os::net
I0901 00:16:35.558888 19563 fetcher.cpp:135] Downloading 'http://hdfs-nn.myhost.com:50070/webhdfs/v1/binaries/storm-mesos/storm-mesos-0.9.3.tgz?op=OPEN' to '/mesos/workLogs/slaves/20150730-232738-4076896266-5050-228496-S3/frameworks/20150825-011215-4076896266-5050-231386-0000/executors/SchemaChangeNotificationTopology-1-1441066588/runs/331c3f07-464a-4767-bdb2-4360fe9ce4d6/storm-mesos-0.9.3.tgz?op=OPEN'
I0901 00:16:36.660876 19563 fetcher.cpp:214] Fetching URI 'http://nimbus.myhost.com:39163/conf/storm.yaml'
I0901 00:16:36.660948 19563 fetcher.cpp:125] Fetching URI 'http://nimbus.myhost.com:39163/conf/storm.yaml' with os::net
I0901 00:16:36.660975 19563 fetcher.cpp:135] Downloading 'http://nimbus.myhost.com:39163/conf/storm.yaml' to '/mesos/workLogs/slaves/20150730-232738-4076896266-5050-228496-S3/frameworks/20150825-011215-4076896266-5050-231386-0000/executors/SchemaChangeNotificationTopology-1-1441066588/runs/331c3f07-464a-4767-bdb2-4360fe9ce4d6/storm.yaml'
E0901 00:16:36.726596 19563 fetcher.cpp:141] Error downloading resource, received HTTP/FTP return code 404
Failed to fetch: http://nimbus.myhost.com:39163/conf/storm.yaml
Failed to synchronize with slave (it's probably exited)

The command I use to deploy: ./storm jar ~/Desktop/mytopology.jar com.chinthaka.org.MyAwesomeTopology
~/.storm/storm.yaml file
storm.zookeeper.servers:
- zk.myhost.com
storm.zookeeper.port: 2181
nimbus.host: nimbus.myhost.com

May be this is minor but the worker process is marked as LOST instead of KILLED or FAILED in mesos UI.

found the reason for this issue. Seems like when it is setting up a local file server to serv conf files to workers, it passed in the serving directory simply as conf. This might be troublesome if the startup scripts are being called from else where.
protected void setupHttpServer() throws Exception {
      _httpServer = new LocalFileServer();
      _configUrl = _httpServer.serveDir("/conf", "conf", _localFileServerPort);

      LOG.info("Started HTTP server from which config for the MesosSupervisor's may be fetched. URL: " + _configUrl);
  }

The fix here would be to have a configuration parameter to point to the correct conf directory path in these situations.  I fixed this locally and will submit a PR later.

@echinthaka's has sent a PR with a proposed fix:  https://github.com/mesos/storm/pull/57

#57 had 2 separate changes embedded in it:

the 1st change was intended to fix this issue (#56) with serving the config file and that never got merged because of the 2nd change:
the 2nd change is more impactful, using wget to download the executor tarball.  This change is more involved and more questionable, and shouldn't have been clubbed together with the 1st change.  That issue is still outstanding and deserves its own full-fledged GitHub "issue" in this project.

Notably, the "config file serving" problem is supposedly fixed by #65 per @brndnmtthws comment in #56:

This might no longer be needed since merging #65. From that PR, the config is generated at runtime and then served up to the supervisors.


Converting from HSL to RGB or LAB gets odd results

If I try to convert from HSL I get some weird outputs:
For example:
from colormath.color_objects import LabColor, HSLColor, sRGBColor

color = HSLColor(89, 19, 90)
rgb = convert_color(color, sRGBColor)
lab = convert_color(color, LabColor)
print(color)
print(rgb)
print(lab)

Output looks like this:
HSLColor (hsl_h:89.0000 hsl_s:19.0000 hsl_l:90.0000)
sRGBColor (rgb_r:33.6333 rgb_g:-1601.0000 rgb_b:1781.0000)
LabColor (lab_l:18430.3065 lab_a:30243.3421 lab_b:-41190.8731)

As you can see this is obviously wrong, and when I use a tool such as this: http://colormine.org/color-converter I get results of:
# results are rounded
L*A*B* = (92.23, -3.27, 4.14)
RGB = (229, 234, 224)

After more playing around I've found I need to be dividing my HSL values, but I'm still getting weird results; when compare to colorsys conversion (where I get the correct result).
For example:
from colormath.color_conversions import convert_color
import colorsys
from colormath.color_objects import LabColor, HSLColor, sRGBColor

h = 89
s = 19
l = 90

color = HSLColor(h/360, s/100, l/100)
lab1 = convert_color(color, LabColor)
print(lab1)

r, g, b = colorsys.hls_to_rgb(h/360, l/100, s/100)
lab2 = convert_color(sRGBColor(r, g, b), LabColor)

print(r, g, b)
print(lab2)

Output is:
LabColor (lab_l:90.1623 lab_a:3.2667 lab_b:1.1810)
0.9006333333333334 0.919 0.881
LabColor (lab_l:92.2324 lab_a:-3.2794 lab_b:4.1440)

So when converting through colorsys.hls_to_rgb first then i get a correct output, but just using only convert_color I do not.
I've tried using through_rgb_type=sRGBColor but still does not give correct results.


storage - fix requester pays region tag

Region tag for requester pays is get_requester_pays_status but should be storage_get_requester_pays_status
https://github.com/googleapis/google-cloud-java/blob/739d519e14649f8b7612631d90eed97a614bf93a/google-cloud-examples/src/main/java/com/google/cloud/examples/storage/snippets/StorageSnippets.java#L1027-L1037

(I'm J-team rotation) I added p2 but feel free to label it appropriately.

This was fixed as part of the sample migration done by @JesseLovelace in https://github.com/googleapis/java-storage/pull/1258 — looks like the region tag is now correctly showing storage_get_requester_pays_status here: https://github.com/googleapis/java-storage/blob/a2024322ffd7c4d3bfa17abd72a680b56ca8d875/samples/snippets/src/main/java/com/example/storage/bucket/GetRequesterPaysStatus.java#L19


Adjust DeployAccount transaction to V3 changes in starknet-api.

This change is

Codecov Report

Merging #865 (dfdddd1) into barak/v3_adj/declare (551d0d3) will decrease coverage by 0.45%.
The diff coverage is 18.88%.

@@                   Coverage Diff                    @@
##           barak/v3_adj/declare     #865      +/-   ##
========================================================
- Coverage                 69.38%   68.93%   -0.45%
========================================================
  Files                        42       42
  Lines                      5726     5772      +46
  Branches                   5726     5772      +46
========================================================
+ Hits                       3973     3979       +6
- Misses                     1383     1423      +40
  Partials                    370      370

Files Changed
Coverage Δ

...lockifier/src/transaction/transaction_execution.rs
2.75% <0.00%> (ø)

crates/native_blockifier/src/errors.rs
0.00% <ø> (ø)

crates/native_blockifier/src/py_transaction.rs
0.00% <0.00%> (ø)

crates/blockifier/src/transaction/transactions.rs
62.73% <70.00%> (-0.20%)
:arrow_down:

.../blockifier/src/transaction/account_transaction.rs
93.58% <100.00%> (+0.02%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

crates/blockifier/src/test_utils.rs line 421 at r1 (raw file):
Previously, elintul (Elin) wrote…
Is this how it's done in the rest of the code (for declare and invoke test utils)?

Not precisely, but notice that this function returns DeployAccountTransaction while the invoke and declare return specific version of some transaction. So, I left it as is to not break other places that use it.

Merged in the following PRs: 1, 2, 3.


feeled confused about the speed compared in table 4

In PSENET, speed statistics are computed from images of long side equaling to 1280.
In PAN, speed statistics are computed from images of short side equaling to 640.
Is it fair or proper to compre them in this way?

It is a trade-off between accuracy and speed. So it is ok to compare the speeds of models with similar accuracy.


Can webcamjs support live detection ?

Can webcamjs support live detection ?
Using camera to capture the face photos, including a live detection function (by shaking his head left and right to get photos or something like this) .

This might do it:

Get the data URI of the current image.
Somehow without saving, convert it into a numpy array.

And that shoud be it.


Change Flag Variable Pass through

Create Global Functions that return the variable and use those so I don't get stuck passing so many freaking variables.

This is not super important and may not be needed plus cause more problems. Revisit in say two weeks or maybe sooner and come back when more is done so that way a choice can be made to test in a branch.

Bring up in weekly meeting see if creating the global grab variables is dumb.


Experimental Join operation

Codecov Report

Merging #5 into master will decrease coverage by 1.68%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
- Coverage   99.16%   97.48%   -1.69%
==========================================
  Files           1        1
  Lines         120      159      +39
==========================================
+ Hits          119      155      +36
- Misses          1        4       +3

Impacted Files
Coverage Δ

dist/kefir.atom.cjs.js
97.48% <0%> (-1.69%)
:arrow_down:

Continue to review full report at Codecov.

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