Allow noServerMethods option and otherwise throw error upon loading…

… store names which conflict with db.js methods; add test and docs
To address issue #136

I've added a commit to handle the case that you suggested (and I was mistakenly checking for conflicts against the db name instead of against the object store). I did still think it was useful (via the second commit) to have a check to confirm that query was a function (as opposed to an object) as it ensures that query is still available as a server method (and not an object store), but I also added a test specifically to check that a valid store name was not present with noServerMethods added.
The first commit also changes things to self-close the connection since otherwise the db might remain blocked.
Let me know if you want me to revert the other changes in the first commit to reject instead of throw--I thought it might provide a clearer flow.

Are you ok with my further modifications here?


Correct unit test & add upload via Stream

Thanks!

Hello, thank you for your PR! We would love to include this example. However, we just released a major version that updated a lot of the examples. If you wouldn't mind rebasing and updating, I would love to merge this in.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: navispeed:x: pran1990You have signed the CLA already but the status is still pending? Let us recheck it.


Upgrade V2 API's to V3 API's

Which at_widget package you want to add enhancement?
at_onboarding_flutter
On what platforms do you want to add enhancement?
Android, iOS, Windows, MacOS, Linux
Is your feature request related to a problem?
At present, the onboarding widget communicates with the registrar API using V2 APIs. Upgrade to utilize V3 APIs.

Code that interacts with RegistrarAPI on CLI side and Apps side is being consolidated into a single package which will be called "AtRegister". This package is almost ready and has code that has been upgraded to Registrar V3. When the package is published it needs to be consumed into RegisterCLI and OnboardingFlutter. @sachins-geekyants will be handling the onboarding_flutter side of things as discussed.
Issue link for AtRegister: https://github.com/atsign-foundation/at_libraries/issues/468

@srieteja Let me know, If AtRegister can be used for testing in onboarding_flutter.

Backloggin this until https://github.com/atsign-foundation/at_libraries/pull/508 is successfully merged.


Hitting o to open config hangs

Describe the bug
Hitting o while on the status pane to view my config hangs the app.
To Reproduce
Steps to reproduce the behavior:

Go to status pane
Hit o

Expected behaviour
Config displays
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Arch Linux
Lazydocker Version 0.3.0

Additional context
nvim seems to be the app xdg-open chooses to view the config.yml file.  I can run xdg-open ~/.config/jesseduffield/lazydocker/config.yml (which seems to be the command lazydocker runs) in a shell to open the config file in nvim successfully.  I can also hit e in lazydocker to edit the config and it opens for edit successfully.  When I'm not on work hours I can play around with a development build and see if I can determine what is happening.

Root of the issue is my xdg-open is choosing vim, and lazydocker by default routes the output to /dev/null.  Running the command sh -c "xdg-open '/home/REDACTED/.config/jesseduffield/lazydocker/config.yml' >/dev/null" (which is what lazydocker chooses to run) causes the output:
Vim: Warning: Output is not to a terminal
Changing lazydocker's config to either remove the redirect to /dev/null or just open nvim {{filename}} results in the same.  To get this to work I'd have to use the runSyncOrAsyncCommand similarly to gui.editFile.


Show percentile value used for result colormapping in UI

Currentlyit says "Maximum value in MSP area" in the scenario detail view, while actually it is a configurable percentile value that is used (95th in the default configuration). The UI should reflect this.
Plan:

Add endpoint /calibration/percentile-value which simply returns the configured percentile value
Add fetching of value in calculation service on frontend
Pass this value to normalization-selection-component and display it in the template

Hello there @RichardSabol, thank you for showing interest in this project! 😄
I'm afraid this specific issue is already sort of pipelined as part of internal planning at SWaM, which means we might actually need to manage its delivery ourself.
It appears that this was tagged with "good first issue" (especially encouraging public collaboration) due to some slight miscommunication.
For this reason I'll assign this issue to myself now instead, we sincerely hope you won't be discouraged to contribute otherwise!


MapVersionedODataRoute or MapVersionedODataRoutes always throws an exception

I've been trying to add versioning to our OData API for the last couple of days but despite working off the samples here I find that my call to MapVersionedODataRoute or MapVersionedODataRoutes (depending on which sample I based my code on) inevitably results in the following exception:
System.MissingMethodException was unhandled by user code
  HResult=-2146233069
  Message=Method not found: 'Void System.Web.OData.Routing.ODataPathRouteConstraint..ctor(System.Web.OData.Routing.IODataPathHandler, Microsoft.OData.Edm.IEdmModel, System.String, System.Collections.Generic.IEnumerable'1<System.Web.OData.Routing.Conventions.IODataRoutingConvention>)'.
  Source=Microsoft.AspNet.OData.Versioning

It's been difficult to troubleshoot as I can't tell what method it can't find. In case it matters, the stack trace is basically identical in each case, aside from the name of the method that I invoked in my code.
StackTrace:
       at System.Web.Http.HttpConfigurationExtensions.MapVersionedODataRoutes(HttpConfiguration configuration, String routeName, String routePrefix, IEnumerable'1 models, IODataPathHandler pathHandler, IEnumerable'1 routingConventions, ODataBatchHandler batchHandler)
       at System.Web.Http.HttpConfigurationExtensions.MapVersionedODataRoutes(HttpConfiguration configuration, String routeName, String routePrefix, IEnumerable'1 models, ODataBatchHandler batchHandler)
       at VersionedAPI.Startup.Configuration(IAppBuilder appBuilder)

or
StackTrace:
       at System.Web.Http.HttpConfigurationExtensions.MapVersionedODataRoute(HttpConfiguration configuration, String routeName, String routePrefix, IEdmModel model, ApiVersion apiVersion, IODataPathHandler pathHandler, IEnumerable'1 routingConventions, ODataBatchHandler batchHandler)
       at System.Web.Http.HttpConfigurationExtensions.MapVersionedODataRoute(HttpConfiguration configuration, String routeName, String routePrefix, IEdmModel model, ApiVersion apiVersion)
       at VersionedAPI.Startup.Configuration(IAppBuilder appBuilder)

Do I possibly need to include another package? Is there a bug in the current release?

Which version of the OData package are you using? I'm guessing you are upgrading a project or creating a new project which is using 6.0.0.  There were some pretty significant changes to API and runtime behaviors in 6.0 (see OData 6.x Features for more details).  There were a few places where I had to beat the OData APIs into submission, which required nasty, but unavoidable Reflection use. I suspect you are either encountering an incompatible binding redirect from the changes in the APIs or some internal piece of Reflection code is now broken.
Assuming this is your case, then my suggestion would be to use a previous release of the OData package - for now. All of the examples in this project are written against 5.9.1, but I suspect things will work all the way back to at least 5.6 (untested).  That should unblock you.
If you can indeed confirm you are using 6.0, then I'll also file a bug that the library is incompatible with 6.0.  I haven't dug deep into the changes for 6.0 yet, so I'm not sure how much work it will be; presumably minor. Until I've had some time to look into it, I can't say whether the fix will take a few days or a few weeks.  Regardless, I'll start taking a look and get a fix out as soon as possible.
Thanks for reporting the issue. Apologies for the inconvenience.

Thanks, I appreciate the quick response. I can confirm that I've been using version 6.0.0 of the package. I was planning to try starting fresh with an earlier version of the package to see if that made a difference, but I got hung up in meetings and hadn't had the time to try it yet. Thanks for your help.

Changing this to an enhancement rather than a bug, since the latest, published API versioning package for OData now indicates that it's not compatible with the OData 6.0.0+ package.


Add tests

All open source projects should have tests.
You should check how other Remark plugins test themselves.

Added tests


Dev

I began to commit on dev branch to add noexcept garantees but these features aren't finished yet (next I'll try to update travis-ci c++ library to have noexcept std::string moves).
You did not comment the pull request, is it a miss click ?


Ability to rearrange widgets

Is your feature request related to a problem? Please describe.
As more widgets come in the future it'd be nice if users had the ability to rearrange them
Describe the solution you'd like
Ability to rearrange widgets in the Widgets settings

@d2dyno1 considering the fact that no additional widgets are on the roadmap, I think we can close this issue.


add basic message function to starter-bot

I think display more basic function will help newbie

how about I create another bot but starter-bot with message receive and send?
I know less is more, but I think there are two points: Puppets will confuse newbie; Someone only want to try basic message sender/receiver;

as @zixia already change a lot of things of example, I closed this

+1, for fullstack developers, it's critical that a platform has a workable and easy-to-setup example.


Show file history not work in wsl

GitLens Version:v10.2.2

VSCode Version:1.49.2
OS Version:Windows_NT x64 10.0.19041

Steps to Reproduce:

open workspacce in wsl
right click one source file, select 'Show File History'
then it show some message 'unable to show file history, See output channel for more details'
message "[2020-09-28 03:58:51:089] ShowQuickFileHistoryCommand
Error: cannot open vscode-remote://wsl%2Bcentos8/mnt/e/code/work/YuYouGame/src/branches/dev/Server2.0-Git/connserver/mnt/e/Code/Work/YuYouGame/src/branches/dev/Server2.0-Git/connserver/ActivityMgr.h. Detail: 无法读取文件'vscode-remote://wsl+centos8/mnt/e/code/work/YuYouGame/src/branches/dev/Server2.0-Git/connserver/mnt/e/Code/Work/YuYouGame/src/branches/dev/Server2.0-Git/connserver/ActivityMgr.h' (Error: 无法解析不存在的文件"vscode-remote://wsl+centos8/mnt/e/code/work/YuYouGame/src/branches/dev/Server2.0-Git/connserver/mnt/e/Code/Work/YuYouGame/src/branches/dev/Server2.0-Git/connserver/ActivityMgr.h")"

Does this still happen in GitLens 11?

thanks, it never happened again.
| |
肖永利
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 11/16/2020 15:32，Eric<EMAIL_ADDRESS>wrote：
Does this still happen in GitLens 11?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Documentation including Storybook

Documentation
See the new CONTRIBUTIONS.md for getting started. This will be the new central / launching area for getting started and even can include FAQs and links to Product information (e.g. the InvisionApp work)
CLI
To encourage code over written word and rapid feature development for new comers, I am proposing a custom CLI (that leverages Gluegun)
Accelerating Project Startup
Instead of documenting in english all the steps to get start on the app, web, or "functions" (Firebase), do this in code. Doing so also helps the developers

To quickly spin up the project (right now only focusing on the Native App)
Having a proving ground for our documentation instead of doing "oh yeah that doesn't actually work"

Component, Screen, and More generators
Further more by having a CLI we can introduce generators (pull request coming soon!).
yarn make:screen and yarn mark:component
In doing so we can further help keep consistency and yet drive change by emphasizing changing standards in the generator templates.
New React Developers Welcome!
By taking an automation or assisted CLI approach we can help new engineers (including Jr. Developers) to be welcome in contributing as they'll have a guide through the CLI prompts and generators.
TODO
I didn't complete the tests yet :( As there is some scaffolding and mocking you must implement and those that I have from other projects are in TypeScript. I need to either convert them to regular JS or simply make the kuka/cli use TypeScript for the tests (which the later would be far easier).

Totally happy to block this PR without the tests.

Component Documentation (Product and Development)
By using Storybook we'll encourage Component Driven Development and Design with increased isolation. This gives the added benefit of not having to wait for a page to develop and see components!
To use Storybook see the Storybook section in the CONTRIBUTION.md document.

@davidrideout and @johnkmzhou Happy to rip out Storybook if the rest of this makes sense.


Error happens when building the hostpath driver

git clone https://github.com/kubernetes-csi/drivers.git
enter into the drivers folder
# make hostpath show below error:

if [ ! -d ./vendor ]; then dep ensure; fi
/bin/sh: 1: dep: not found
Makefile:35: recipe for target 'hostpath' failed
make: *** [hostpath] Error 127

Try to # go get github.com/golang/dep, but it fails at:
# github.com/golang/dep/vendor/github.com/boltdb/bolt
flag provided but not defined: -goversion
usage: compile [options] file.go...
...

@arm64b does https://stackoverflow.com/questions/46241177/in-gogland-i-get-flag-provided-but-not-defined-goversion-using-go-run help?

Hello @pohly , yes, it's help. I messed up my go environment in my local machine (GOPATH), and after that, we need to go get this git repo, then it should be OK. Thanks for the information 👍

This issue can be closed now.


How to authenticate users in nestjs

Checklist

Please note that in case of below checklist not updated accordingly, the maintainers have the right to immediately close your pull request.

[ x ] You created a branch from dev branch.
[ x ] You PR is raised on dev branch and not onmaster.
[ x ] Blog follows Blog Guidelines.
[ x ] You have read the Contribution Guidelines before creating this PR.
[ x ] Checked for any duplicate blog entry.
[ x ] Checked for all grammatical errors in the blog.
[ x ] You have not published the blog content anywhere else on the internet on platforms like medium, dev.to etc.
[x ] The content is not copy-pasted from anywhere else on the Internet.

Description of change
A tutorial on how to authenticate users using the Authentication API provided by LoginRadius in NestJS.

Hi @gathoni-k We're moving your PR to Phase - II.
For facilitating easier reference for readers, please add the sample/example code used in the following repo by creating a separate pull request: https://github.com/LoginRadius/engineering-blog-samples

Hey!
Okay, I will.
On Tue, 15 Feb 2022, 14:11 Raghunath Reddy, @.***>
wrote:

Hi @gathoni-k https://github.com/gathoni-k We're moving your PR to
Phase - II.
For facilitating easier reference for readers, please add the
sample/example code used in the following repo by creating a separate pull
request: https://github.com/LoginRadius/engineering-blog-samples
—
Reply to this email directly, view it on GitHub
https://github.com/LoginRadius/engineering-portal/pull/976#issuecomment-1040145533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMMBYTX4PCTC5FCHEHZU7CLU3IYFPANCNFSM5OCZ5ZHQ
.
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 were mentioned.Message ID:
@.***>


Add Dockerfiles for Elasticsearch, Logstash, Kibana, Zookeeper

These should take parameters, and be flexible to interact with the other Traffic Control Dockerfiles, or with non-Docker CDN components.
This is actually about half done. I have Dockerfiles for these components, but they aren't finished or pushed to Github yet.
As far as I know, our configuration for ELK is still being finalized, so this probably needs to wait until the ordinary installation is nailed down.

This refers to the old ELK prototype, not any components currently in use.


⚠ Samsung has degraded performance

In c8f124b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2882 ms

Resolved: Samsung performance has improved in af497c3.


(mp3tag) Add support 64-bit installer and update AU version detection

Description
This updates the package to include the new 64-bit installer.
Additionally, the update posts changed format recently as well, this updates the regex to work with the new format.
Motivation and Context
Fixes #1895
An up-to-date package with all installer architectures is desirable.
How Has this Been Tested?
Ran update.ps1 locally, it updated the package no issues. Installed and uninstall 32 and 64 bit versions in the test environment.
Screenshot (if appropriate, usually isn't needed):
N/A
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

@TheCakeIsNaOH your changes have been merged, thanks for your contribution 👍


Ensure ECR repository image scans are enabled

aws_ecr_repository should enforce that ECR repository image scans are enabled.
https://www.terraform.io/docs/providers/aws/r/ecr_repository.html#image_scanning_configuration

Believe this can be closed, given the PR has been merged


skip_changelog: Add community.docker collection

Add Ansible community.docker collection to the requirements to make sure it gets installed with git. Fixes install breakage due to Galaxy API changes.

#241


Eliminate deprecation warnings about 'dsl_name'.

Fixes #288.

Closing this because we now set the resource_name via https://github.com/chef/chef-provisioning-aws/commit/da93c3316d381998a9f2dc4d11f6746af885bdf3


Current implementation of poll_ready is not very useful

This elaborates on https://github.com/alexcrichton/futures-rs/issues/213#issuecomment-255400509

Would you be able to elaborate on "I don't think it can be useful in the current form"?

Sure. I think we discussed that in chat, but let me summarize my opinion.
If you're implementing a client:

There is no way for client implementation to notify caller that service is ready again

There is no guarantee that poll_ready() is called before call(), so you end up with two options, both render poll_ready() useless (i.e. you can do the same with SinkError and without poll_ready()):
a) arrange your call method to be able to accept requests anyway (i.e. queue it internally)
b) always return an error when your service is not ready, so caller repeats request on its own

My own use case at the moment of the last discussion was: I have a pool of connection to the database and I want to send my next request to a less loaded connection. It might be implemented using different traits like:
trait InFlight { fn get_requests(&self) -> u64; }
trait BufferSizes { fn get_bytes_buffered(&self) -> u64; }

And I might implement a connection pool with different load-balancing strategies:
struct DistributeByNumberOfInflightRequests<S: Service + InFlight>(S);
struct DistributeByBytesBuffered<S: Service + BufferSizes>(S);
struct DistributeRoundRobin<S: Service>(S); // for any service

If you're implementing a server, it's unclear when a transport might call poll_ready(), I can see two options:

Before accepting a connection
Before reading next portion of bytes from the socket

Still, when we already read a request there is no guarantee that poll_ready() returns true, so transport layer have to be prepared to queue at least this one request.
At a glance, it's still cool to stop accepting connection on heavy load, but the fact that there is no notification of when the service is ready again makes it's very error-prone. I.e. the most obvious way to handle NotReady is to timeout and try again, but if you look at the system that is able to process 100k requests per second at a steady rate, it may have their queues filled up 100 times a second. Which means just adding a timeout of anything larger than 10 ms may starve service usage for an arbitrarily large period of time. I mean such a system is very unpredictable, it may stop accepting connections  using 10% CPU or alike.
Just adding a notification mechanism to poll_ready() is not useful too, because it's just an equivalent of the queueing requests somewhere.
On the other hand, it's possible to make a pushback mechanism based on statistics. I.e. create a middleware that counts the fraction of requests which got SinkErrors and applies a rate-limit for a number of accepted connections per second if there were more than 10% of errors in the last second.
And a per-connection pushback is usually handled by tracking the number of in-flight requests.

Sorry for the long write-up, but at the end of the day:

There are alternatives to explore, before making a standard
There are no known good strategies both for implementing and for using poll_ready()
poll_ready() can be added later with a default implementation that is always ready, like it currently is in every example out there

cc @aturon

FWIW I share some of these concerns, and think we should remove poll_ready for the 0.1 release. As you say, it can be added later, and I think we need to take more comprehensive steps for backpressure in future releases.

cc https://github.com/tokio-rs/tokio-service/pull/6

Closing as resolved for 0.1. We'll be revisiting the backpressure more generally soon.


Losing Mass Cell per second as feature

Hello Dev!
Can you build the script which can calculate losing mass per second? because on agar.io the cells losing their mass per second and if you are really big cell, you will loosing quicker and  much much more mass. Do We have point when map is resetted? at Agar.io you have to reach goal 20k points as one cell.
Best Regards
Mateusz

If nobody does it by the next time I start working, I'll put this in my next PR. Does anybody have an estimate of the rate of mass loss?


Don't print 'convenience' on protocol extension initializers

We model them that way in the compiler, but that's not part of the user-level language.
rdar://problem/32067077

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 6cad19eeba07ee2bbfa6d83caa83c700bf14332b

@swift-ci Please test Linux

@swift-ci Please smoke test

@swift-ci Please smoke test


SEX is used with SDV definition

change SEX to SDV

I think it may be worth keeping both since the former is increasingly of importance in different use cases.

I don't disagree, but the SAMSHA valuesets more clearly cover SDV than SEX. I have no valueset that covers SEX.


Feature request: Sync cask version to the current installed version

where:

there are auto-update version
they never in sync with the installed version

what i expect:

some check command which reads the current version and update the info for brew cask

what i see instead:

always apps are outdated, also if they updated in app

Hey @muescha ,
Thank you for your suggestion, not not sure if that is easily possible. Do you have a hint how to get (in general) a version of installed software? Theoretically might be possible to get that from Info.plist file, but is that consistently achievable?

Also one issue is that how the installation folder looks like:
/usr/local/Caskroom/{cask}/{version}/

But not something that is not achievable, just re-symlinking to a different folder might work 🤔

i don't know how MacUpdater solved this :(

Hey @muescha , I also don't know how they solved it but also I guess they have much more resources. I've tried to look into this and the problem is that not all casks are installed the same way.
Currently it is fairly "easy" to guess the version - even though there are multiple versions in the Info.plist file within the app, let's say i will "correctly" guess the updated all version. The "problem" here is, that the app doesn't always have a "link" back to the cask.
There are currently two ways:

I know what casks are installed so I can go through them
"Scan" the whole Applications folder and get all the versions

In both cases I still have the problem that there is no link between them guaranteed (i.e. some casks are installed via .pkg therefore I have no clue what is the app name and where exactly it is installed). I can potentially start rolling out some experimental features in this matter, which means it will only work with some of the apps but right now I really can't guarantee that it will work without any issues and for all apps.

Was just wondering the same thing and found this issue. Perhaps another way to approach it might be to simply hide versions of unmanaged software?
       Cask                                  Current       Latest        A/U    Result
 1/73  adobe-air                             <IP_ADDRESS>    <IP_ADDRESS>         [   OK   ]
 2/73  appcleaner                            Unmanaged     3.5            Y   [  PASS  ]
 3/73  apptivate                             latest        latest             [   OK   ]
 4/73  atom                                  Unmanaged     1.52.0         Y   [  PASS  ]
 5/73  backblaze                             Unmanaged     <IP_ADDRESS>0      Y   [  PASS  ]
 6/73  betterzipql                           latest        latest             [   OK   ]
 7/73  chromedriver                          86.0.4240.22  86.0.4240.22       [   OK   ]
 8/73  cyberduck                             Unmanaged     <IP_ADDRESS>520    Y   [  PASS  ]
 9/73  docker                                Unmanaged     <IP_ADDRESS>        Y   [  PASS  ]

It just feels a little unsettling to see the incorrect current version, but hiding it seems to restore the peace of mind. 🤔 What are your thoughts?

Hey @maxim , thanks for stopping by 😉  The issue I see with your proposal is how do you know, which are managed and which are not? For example I turn auto-update for the apps off and 99% of the times I update them through brew cu. Other people are using auto update on the apps and then ignoring them on brew cu (i.e don't pass --all argument or pinning them).
So what would be the use case for showing the Unmanaged current version?

Ah makes sense, this wouldn't work then. Trying to see if there's any way to indicate that "current version" is not actually correct in some cases.

My proposal was simply to have brew cu say "if i'm not the one updating the app, then I don't know what version it is" in any way we'd like.

Hello,
A very simple first step would be to offer the possibility to the user to tell that he has migrated outside brew. For example:
brew updated [--version version] cask. Without the version, it changes the recorded version to the current latest available and with the version it changes to the specified version.
In my point of view, it would make it easier for the user that sometimes use outside upgrades to keep track of its current state.

I think this issue is out of scope of brew cu, which is in the end just a plugin to HBC and not a complete software management solution. To hyperbolize this issue, one may request cu to discover all manually installed software and map them to corresponding casks in order to make it manageable. This is also technically possible, but is practically hard. A paid version of Chocolatey, a pro one, is doing this on Windows.

@fdagnat have to agree here with @yurikoles . Even though it sounds like a "easy task", the way casks are generally managed is complicated. There are installation metadata that we would need to update, symlinks that would need to be fixed, etc. That has a huge potential for breaking if any internal implementation changes.

I too think it useful if the versions of auto-updated applications are synced. The current application version can be obtained using AppleScript. Is this not sufficient? This seems to work for most of the apps.
osascript -e 'version of app "Slack"'

Good idea. This works for every app? This script need an "special" app name?

I don't think getting the actual version is a big problem. The main challenge here actually reflect all the necessary changes.
Let's take a signal cask as an example. Currently in version 6.1.0.
That means following:

Installation path contains the version:

/usr/local/Caskroom/signal/6.1.0/Signal.app -> /Applications/Signal.app

Metadata for the cask contains the version of the cask file itself (and version in the path)

/usr/local/Caskroom/signal/.metadata/6.1.0/20221225203223.651/Casks/signal.rb

> cat signal.rb
───────┬───────────────────────────────────────────────────────────────────────────
       │ File: signal.rb
───────┼───────────────────────────────────────────────────────────────────────────
   1   │ cask "signal" do
   2   │   arch arm: "arm64", intel: "x64"
   3   │
   4   │   version "6.1.0"
   5   │   sha256 arm:   "32f2bcd01dd06dabc3b6ab68857cd6716690daa703912190db65b1af6a002eda",
   6   │          intel: "b1a2ab77c99dce19ec46e207b100cbb45fdc32eff6eb65e61403a09d860f7da1"
   7   │
   8   │   url "https://updates.signal.org/desktop/signal-desktop-mac-#{arch}-#{version}.dmg"
   9   │   name "Signal"
  10   │   desc "Instant messaging application focusing on security"
  11   │   homepage "https://signal.org/"
  12   │
  13   │   livecheck do
  14   │     url "https://updates.signal.org/desktop/latest-mac.yml"
  15   │     strategy :electron_builder
  16   │   end
  17   │
  18   │   auto_updates true
  19   │
  20   │   app "Signal.app"
  21   │
  22   │   zap trash: [
  23   │     "~/Library/Application Support/Signal",
  24   │     "~/Library/Preferences/org.whispersystems.signal-desktop.helper.plist",
  25   │     "~/Library/Preferences/org.whispersystems.signal-desktop.plist",
  26   │     "~/Library/Saved Application State/org.whispersystems.signal-desktop.savedState",
  27   │   ]
  28   │ end
───────┴───────────────────────────────────────────────────────────────────────────

Which means all those paths needs to updated, App re-symlinked, metadata file patched, otherwise the installation itself might break.
And I'm not even sure if it's all the things that need to be updated.
Which means that it's not really feasible to "update" the app based on its auto-updated version.
Yes, we can potentially report different version in the output and have a difference in "undateable" applications, however the application would still be reported as outdated when using standard brew outdated command and would be upgraded when running brew upgrade.
IMO I believe this inconsistency & confusion would not be worth the effort.
Maybe there is a practical solution to this issue that I don't see, if yes, please explain it 🙂

I don't think getting the actual version is a big problem.

I might have underestimated this, it actually is a problem because of the comment above - the osascript takes the value from Info.plist which is the only reliable source for that. Meaning that won't also be compatible with the versioning scheme brew is using as that's separated from the version itself - it's more the version string used for downloading the app then the version itself.

The brew cu gets and displays the current installed versions of the auto-update apps instead of the last homebrew installed versions. Then, in the Result column, it displays OK if those are up-to-date, and OUTDATED if they are not. In the bottom section, "Found outdated apps," auto-update apps are not displayed even if they are OUTDATED. It may be less confusing if the section name is Found updatable apps.

thats somehow was my original intention for this issue. to see if there is some action needed also for the autoupdate apps. just now the lines for autoupdate apps are useless because they never show me real data.
i don't need some fixing in the casts receipes and all others - only a information

I too think it useful if the versions of auto-updated applications are synced. The current application version can be obtained using AppleScript. Is this not sufficient? This seems to work for most of the apps.
osascript -e 'version of app "Slack"'

This won't unfortunately work as the apps don't report the version in the same versioning scheme that brew is using. Example:
> brew info plex
==> plex: <IP_ADDRESS>13,533a7645 (auto_updates)
https://www.plex.tv/
/usr/local/Caskroom/plex/<IP_ADDRESS>13,533a7645 (118B)
From: https://github.com/Homebrew/homebrew-cask/blob/HEAD/Casks/plex.rb
==> Name
Plex
==> Description
Home media player
==> Artifacts
Plex.app (App)
==> Analytics
install: 521 (30 days), 1,600 (90 days), 6,185 (365 days)

However, the osascript reports differently:
> osascript -e 'version of app "plex"'
1.60.1

in this case <IP_ADDRESS>13,533a7645 starts with 1.60.1 so it can be equal. maybe in the case if it is not 100% equal but the starting is the same then the result for the column if there is an update needed can be "MAYBE"

However, the osascript reports differently:
> osascript -e 'version of app "plex"'
1.60.1

in this case <IP_ADDRESS>13,533a7645 starts with 1.60.1 so it can be equal. Mybe in the case if it is not 100% equal (it also can match for <IP_ADDRESS>13,533a7645 - maybe it is possible to strip down the receipe version to 1.60.11 so we can compare the version up to the 3rd level) but the starting is the same then the value for the column Result if there is an update needed can be "[MAYBE]" and it is up to the user to check if there is an update needed or not

I know, but that's just one of the examples. It also happens that the "build number" (or whatever is in the version) is changed but the version itself doesn't. Which means even in that case the startsWith won't work all the time.
We might not be looking for a perfect solution, true, but there are definitely cases where it won't work and we should call that out.
I wonder if that should be some sort of experimental feature enabled only in certain cases 🤔  (i.e. yet another option).

behind an experimental option it would be ok
maybe: with some description that the user should report to an issue here the edge cases of version compare where it should equal

i found also this edge case:
osascript -e 'version of app "jetbrains toolbox.app"'
<IP_ADDRESS>01

cask "jetbrains-toolbox" do
  arch arm: "-arm64"

  version "1.27.2,<IP_ADDRESS>01"

This would be really cool to implement in some way, even if there are some edge case apps who's auto-updated version can't be discerned.

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
dsky1990, @squanto, @mariajdab, @alec-c4, @betterjun, @stephenkaraga, @sstoner, @couturecraigj, @lorenzoli, @Sid1057, @naveen-appoets, @lucill851, @pesho, @kernelsoe, @ZTjack, @teman198, @orangeflame, @super-bobo, @dothin, @vunb

GitHub Recruitment Team

LOL!!! Swindler detected https://who.is/whois/githubtalentcommunity.online


🎈 7.5.0

🎈 Release
Preparation for 7.5.0 release.
Comparison to 7.4.0: https://github.com/gazebosim//compare/gz-sim7_7.4.0...gz-sim7
Needed by @bperseghetti
Checklist

[x] Asked team if this is a good time for a release
[x] There are no changes to be ported from the previous major version
[x] No PRs targeted at this major version are close to getting in
[x] Bumped minor for new features, patch for bug fixes
[x] Updated changelog

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

LGTM! Thanks!


Same sha on different branches not generating build correctly

We have been using a model in gitlab and gitlab-ci where we have devel and master branches. Typically, the master branch is considered "stable" and is only updated when a release is being put together. Most commits end up in the devel branch.
When we merge from devel into master it is sometimes done so a fast-forward is performed which means devel and master have the same sha. This is where the problem comes in. It appears gitlab-ci will attribute the merge/commits made to master when doing a new release back to the devel branch because the sha's match. Thus when doing the build the proper ref name is not used.
Note that when doing tagged builds they seem to work a little bit better. They get the proper ref name during the build.
Previous verisions of gitlab-ci seemed to handle this without issue but after updating to gitlab-ci 5.4.x it no longer does.
My guess is the problem is in the following:
https://github.com/gitlabhq/gitlab-ci/blob/master/app/services/create_commit_service.rb#L22-L48
The commit is only looked up based on the sha (which can be the same across different branches) and then creates the build with that information. Tags seem to go through their own build process logic which is probably why they work a bit better. Ideally, commits would get looked up by both their sha and ref name.

Summary: See above.
Steps to reproduce: Create two branches in gitlab, devel and master for example for a project with gitlab-ci support. Make some test commits to devel and push to gitlab. Now, gitlab-ci should build for devel. Merge those commits into master using fast-forward. Ensure devel and master have the same sha. Push changes to master to gitlab. Now gitlab-ci will do the build but with devel as the ref name.
Expected behavior:  When committing to a different branch, even if the sha already exists as a commit in gitlab-ci, it should build from that branch and not any branches seen previously.
Observed behavior: The build will be done using the branch seen in the first commit matching the same sha.
Relevant logs and/or screenshots: None.
Possible fixes: https://github.com/gitlabhq/gitlab-ci/blob/master/app/services/create_commit_service.rb#L22-L48 Look up commits by both sha and ref name.

+1. Same issue here.

/cc @vsizov

:+1:

@awiddersheim We will have descussion with @randx  about this problem. But I want to say that it is good practic to create merge commit all the time with --no-ff flag. That how GitLab does it. We always create Merge Request for merging branch in GitLab B.V.
Some links about this practic
http://stackoverflow.com/questions/9069061/what-is-the-difference-between-git-merge-and-git-merge-no-ff
http://blog.jonathanoliver.com/my-new-best-friend-git-merge-no-ff/
http://nvie.com/posts/a-successful-git-branching-model/

@vsizov Thanks for looking into it. I agree, in most cases having a merge commit is a good thing and considered "best practice" by a lot of people.
However, the nice thing about Git, Gitlab and Gitlab-CI has been their ability to be flexible enough to allow us to create work flows that make sense in our scenarios.

I agree. The pretty common workflow in Git is to use rebase instead of
merge. Some people don't like merges :)
Kamil
On Tue, Mar 3, 2015 at 1:29 PM, Andrew Widdersheim<EMAIL_ADDRESS>
wrote:

@vsizov https://github.com/vsizov Thanks for looking into it. I agree,
in most cases having a merge commit is a good thing and considered "best
practice" by a lot of people.
However, the nice thing about Git, Gitlab and Gitlab-CI has been their
ability to be flexible enough to allow us to create work flows that make
sense in our scenarios.
—
Reply to this email directly or view it on GitHub
https://github.com/gitlabhq/gitlab-ci/issues/546#issuecomment-76936620.

--
Kamil Trzciński
<EMAIL_ADDRESS>www.ayufan.eu

@ayufan  of course you can use rebase. I use it every day. I'm talking about allowing to do fast-forward merge.

We scheduled the fix to the coming release

@vsizov Great news! Much appreciated.

@vsizov I can do it.
My idea is to store in builds.ref not only name, but full reference (refs/heads/branch or refs/heads/tags). Which later be used as REF_NAME. It will also resolve the issue with showing builds as tagged when they got created from branch.

@ayufan Thanks but it is already done.

Can you point me where it is?

It is on the our internal GitLab instance yet. I added ref name to commit url and also I've made appropriate change to GitLab side so it will pass this ref name.

You mean CI?

I mean I did two MRs, for GitLab  and GitLab CI sides. Because GitLab's MR is referring to CI, so I had to change this links as well.

Ok. Thanks. Did you had time to fix tags as well? There are at least two issues related to tags which I know.

What issues do you mean?

https://gitlab.com/gitlab-org/gitlab-ci/issues/86 https://gitlab.com/gitlab-org/gitlab-ci/issues/90

BTW, your firast message is not about current bug. It can fix another issue but not this. This issue is about finding commit by both ref name and sha

Ok

No, I had no time to fix those issues yet.

Ran into this problem a couple days ago, glad you guys are already on it! Thanks!

@vsizov when do you guys plan to push it to master?

We don't know yet. Sorry. We are busy with more important tasks.

@ayufan You asked me to update you about this fix - 3d7eb9d9151773e01c34cf53dfc91e6bfc2207b3
@awiddersheim Unfortunatelly it would be available in 7.10 only.

@vsizov Thanks for the fix. Just so I'm clear I have to wait at least one more release before this will be included?

yes, it is in master branch now. So you have to wait :(

@vsizov Thanks - i'll prepare fixes for other issues we were discussing.


Allow skipping a callback when reforming

Description
This adds a method to the callback, similar to Rust's filter_map, which allows to reform a callback, but also suppress the emit in case the reform function returns None.
Checklist

[x] I have reviewed my own code
[x] I have added tests

CI should now be fixed by #2866 and #2867. Could you please rebase from / merge the latest master branch?


Cannot find module

For some reason I cannot install node-sass with:
npm install node-sass

Here is the output:
><EMAIL_ADDRESS>install /root/shelterstyle/node_modules/node-sass
> node scripts/install.js

module.js:333
    throw err;
          ^
Error: Cannot find module '/root/shelterstyle/node_modules/node-sass/scripts/install.js'
    at Function.Module._resolveFilename (module.js:331:15)
    at Function.Module._load (module.js:273:25)
    at Function.Module.runMain (module.js:490:10)
    at startup (node.js:124:16)
    at node.js:807:3
npm ERR<EMAIL_ADDRESS>install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.2.0-23-virtual
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "node-sass"
npm ERR! cwd /root/shelterstyle
npm ERR! node -v v0.11.13-pre
npm ERR! npm -v 1.4.6
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/shelterstyle/npm-debug.log
npm ERR! not ok code 0

You're using the unstable node v0.11 branch. We only support stable released. You'll need to switch to 0.10 or 0.12 to use node-sass.

Thanks for the very quick reply @xzyfer! I'm going to switch over to v0.12.2 now :+1:

Great that worked like a charm! Would it be worth adding this to the README?
As I was pretty lost until your advice :)


Add singleton to load reference

Add singleton to load reference
Description
I add the line 13, 23, 52, 70 and 71.
The reference's loading is cancel if a promise, for the same reference, already exists. If not, the behaviour is not changed. After the promise response, the cache is used for the time set. When the cache is too old only one request will be send and a new cycle begin.
Before :

After :

It should not break anything, since the reference behaviour is still gonna have at least one dispatch to the reference store.

@JohnnP As discussed together this is a great idea, can you add in the PR detail the problem it solves (ie) the cache request is only used after the first response.

@JohnnP is it sorking on your project cc @Hartorn

Yes, no issues

@JohnnP  can you rebase on develop

I'm gonna do it when i go back

It's done


Check if url exists before adding cookies

Hello Jozsef,
I had a problem trying to generating documentation from my insomnia files. I'm not really aware of the reasons but it was failing trying to load insomnia.json file which was instead available.
I was serving it with 'npx serve'.
The code was crashing on the line I edited because the url was null when you check the domain for cookies.
I added an existence check on the url and it started working but I don't know if something can be broken now. Apparentely not.
Thanks for this awesome project

Thank you for this 🙏


enable opt-in to redact Secret data from Object status

Description of your changes

Fixes https://github.com/crossplane-contrib/provider-kubernetes/issues/178

Adds a new flag --sanitize-secrets  when set in controllerConfig/deploymentRuntimeConfig of provider-kubernetes, redacts the Secret data from Object status.atProvider.manifest.

the new redact behavior is off by default so as to not break any existing compositions relying on status.atProvider.manifest.data for patches.  Usages meant to shuttling observed secret data to/from remote/control-plane clusters can be updated to use  spec.references[].patchesFrom or spec.connectionDetails and avoid leaking secret data to Object MR status resources.

I have:

[X] Read and followed Crossplane's contribution process.
[X] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

make test and make e2e

Updating the provider-kubernetes's deploymentRuntimeConfig with below additional arg:
         args:
           ......
+          - '--sanitize-secrets'

$ kubectl get provider.pkg provider-kubernetes
NAME                  INSTALLED   HEALTHY   PACKAGE
provider-kubernetes   True        True      ravilr/provider-kubernetes:v0.11.6

will reconcile any existing and new Object resources managing Secrets to have their status.atProvider.manifest.data redacted:
apiVersion: kubernetes.crossplane.io/v1alpha2
kind: Object
metadata:
  annotations:
    crossplane.io/composition-resource-name: credential-secret
    crossplane.io/external-create-pending: "2024-02-07T07:29:20Z"
    crossplane.io/external-create-succeeded: "2024-02-07T07:29:20Z"
    crossplane.io/external-name: provider-token-nkm7s-9wlpl
  creationTimestamp: "2024-02-07T07:29:21Z"
  finalizers:
  - finalizer.managedresource.crossplane.io
  generateName: provider-token-nkm7s-
  generation: 2
  labels:
    crossplane.io/claim-name: provider-token
    crossplane.io/claim-namespace: awsuswest2-admin
    crossplane.io/composite: provider-token-nkm7s
  name: provider-token-nkm7s-9wlpl
  ownerReferences:
  - apiVersion: security.example.com/v1
    blockOwnerDeletion: true
    controller: true
    kind: XCredential
    name: provider-token-nkm7s
    uid: 1569a117-9227-4567-8db3-259e18171da5
  resourceVersion: "86940719"
  uid: 7ce9094d-f06a-4c9d-8e66-3f1a41544893
spec:
  deletionPolicy: Delete
  forProvider:
    manifest:
      apiVersion: v1
      kind: Secret
      metadata:
        name: provider-token
        namespace: awsuswest2-admin
      stringData:
        createdBy: provider-token-nkm7s
      type: Opaque
  managementPolicies:
  - '*'
  providerConfigRef:
    name: example
  readiness:
    policy: SuccessfulCreate
status:
  atProvider:
    manifest:
      apiVersion: v1
      data:
        redacted: null      #<<<<<<<<<======== this is the impact of this change.
      kind: Secret
      metadata:
        ......
      type: Opaque
  conditions:
  - lastTransitionTime: "2024-02-07T07:29:21Z"
    reason: Available
    status: "True"
    type: Ready
  - lastTransitionTime: "2024-02-07T07:29:21Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced

@lsviben @bobh66  PTAL.

Yes, I think I forgot it in my previous PR. It would be great if you could do it here 🙏

Yes, I think I forgot it in my previous PR. It would be great if you could do it here 🙏

Done.


Only add a media query event listener where supported

This change fixes an issue in safari 13 where an unhandled error from ThemeProvider would cause blank pages. This approach has limitations:

In Safari 13 we aren't updating the system color mode
This PR doesn't attempt to fix error handling or lint for calls to APIs unsupported in Safari 13

Closes #1366
Screenshots
Please provide before/after screenshots for any visual changes
Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Tested in Chrome
[ ] Tested in Firefox
[x] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

Looks good! If you confirmed that this fixes the bug in Safari 13, go ahead and merge it 👍


[SR-14363] FixedPoint.swift.gyb slowed down with -Onone copy propagation

Previous ID
SR-14363

Radar
rdar://problem/75481278

Original Reporter
@atrick

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s
Compiler

Labels
Bug

Assignee
@atrick

Priority
Medium

md5: f7b045122f6cf22af9065d2b61bb66fe

Issue Description:
Copy propagation itself massively speeds up code, however, at -Onone we also emit extra stores for lldb support. That might be slowing down some cases. See if there's a way to limit the amount of "poison" we emit in pathological cases to avoid the problem.
We really don't want any slowdown ever with copy propagation, even though it's not designed to actually remove copies–it's only trying to mimic object lifetimes at -O
When this is fixed, move FixedPoint.swift.gyb back into the non-long-tests

Copy propagation is no longer enabled at -Onone. The test still takes too long, but that's a type checker issue:
https://github.com/apple/swift/pull/59308


Feature request: temporarily disable automated tasks

It should be possible to temporarily disable automated tasks. I have not found a way to accomplish this, except the delete them entirely. But when I would need it later, I would have to configure all settings again (e.g. key strokes).
Suggested solution: add an "active" option to all tasks, which is true by default.
Additional issue:
The table of all automated tasks is sortable. I don't think that should be possible, because the order of tasks is relevant.
Additional question:
What is the meaning of the colors of each row? I added a key stroke task which is display with a green background, even though I have not configured that color.

I added a checkbox both in the table and in the Edit window to enable the tasks.
Old tasks (from previous version of the app) and newer tasks (when creating them) will be set to enabled by default.

(Wording may change, but I think that "Enable" is a bit better)
I removed the possibility to sort the table, as it was indeed something that should not be possible.
The table style uses a different color for alternate rows, you can find the same style in the Recent Projects table.

Dear developer guy, you are soooo awesome! 😄


Kaccardi/topic/storage

The PR introduces a new ciao package, qemu, that provides a set of methods and types for launching and managing qemu instances.  This code is a re-write of the qemu management code originally written for launcher.  ciao-launcher now uses the new qemu package in preference to its old qemu code.  A nice side effect of this change is that the volume detach now works properly as the qemu package correctly implements this function.

Coverage increased (+0.07%) to 65.509% when pulling 699fc536424a53048dcbf8e830a3c5651632aa6a on markdryan:kaccardi/topic/storage into 1deb0170e8b4fac0514c84245ef0039d5120e089 on 01org:kaccardi/topic/storage.


provide Python code example for how to use a prodictive endpoint

Please also write the existing example using python code.

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

ID: 021ecbd2-8976-64a4-ca95-0009a1c02692
Version Independent ID: 47011e64-0198-6fac-cd07-0334f350f59c
Content: Use prediction endpoint to programmatically test images with classifier - Custom Vision - Azure Cognitive Services
Content Source: articles/cognitive-services/Custom-Vision-Service/use-prediction-api.md
Service: cognitive-services
Sub-service: custom-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@agribot2 we'll review your feedback and get back to you shortly. Thanks.

@agribot2 we'll review your feedback and get back to you shortly. Thanks.

Thanks, @PatrickFarley Could you please help with the doc for python example.

Thanks, @PatrickFarley Could you please help with the doc for python example.

@agribot2 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@agribot2 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update translation in  assign-pod-node.md

Update translation in  assign-pod-node.md

/lgtm
/approve


General Z-Wave Instability with 2.2.0 and Later

Problem/Motivation

After upgrading from 2.1.2 to 2.2.0 and subsequently 2.2.1, my Z-Wave network has been unstable. Nodes will randomly go dead frequently.  The prior to these updates, the network was reliable. (From a user perspective...things behind the scenes may have been different, but there were no negative functionality observations.)

Expected behavior

Stability in the network. Node stay "alive."

Actual behavior

After updating, there were nodes that just started to "die." Toggling the node on and off (the nodes that were noted as dead are all powered) brings the node back online for a period of time. I have performed network repairs through the ZW UI to see if that helped. It did not.

Steps to reproduce

Update to 2.2.0 or 2.2.1. Observe node status or set up an automation to notify when a node's status changes from "alive" to dead.

Proposed changes

No thoughts on this. I did read the release notes and saw that there were changes that were made to mark nodes as dead under certain circumstances.
zwave-js-ui-store (1).zip
zwave-js-ui-store.zip

same error

+1
During the day there also seem to be quite a few random restarts of the add-on during the day.
I'd also like to add, don't know if relevant to the case, that some more complex devices like the Quibino ZMNHXD (3-phase meter) lost a lot of entities that became unavailable and seems to have renamed a few others. Re-query won't solve the problem.
I started by renaming the entities back to their original names since many of my automations were obviously now failing, till I noticed the unavailable ones and just gave up.
I came here to see if anyone had already reported it and there were good news already, but that does not seem to be the case.
I'm reverting back to the standard z-wave add-on hopping things work there.

I came here to see if anyone had already reported it and there were good news already, but that does not seem to be the case.
I'm reverting back to the standard z-wave add-on hopping things work there.

It will be interesting to hear your success with that. My belief is that it is the driver, which I believe is shared by both add-ons. What Z-Wave controller are you using? I'm using a Zooz 800 Series. I specifically selected this one recently after seeing the problems (another issue) with 500 Series controllers, and some firmware version problems with tee 700 Series controllers.
With all of the problems I have had over the past two months with Z-Wave, I'm looking to migrate away from it completely. I don't know what changes started in August, but it seems to be a series of ongoing problems now versus the past.

I'm using the aeotec gen7+ stick and 2.2.x is basically unusable. I rolled back to 2.1.2 and it's working again.

It will be interesting to hear your success with that.

You guess it right.
All the same with the standard/default add-on.
What a disappointment!
I personally had a stable z-wave system for over 1 year, perhaps 2.
I agree with you, someone has done more harm to z-wave users on HASS over these last few weeks than years before summed up.
I understand this is freeware software, I understand this is open source, we can't complain for something we did not pay a cent, I understand all of that.
However, I should also point out there are a lot of users using this code, so the first rule should always be test, the second rule should be test again, and the third rule must be test once more, out of respect for those end-users.
We come to expect enhancements on each release, not in a million chances we ever expect new releases to render our systems unusable.
Sorry for the rant.
I'm available to assist solving this mess, but I would much rather prefer this mess would not take occur in the first place.

I'm using the aeotec gen7+ stick and 2.2.x is basically unusable. I rolled back to 2.1.2 and it's working again.

I don't know if I have backups from 2.1.2, I'll check, thanks for the info!

I don't know if I have backups from 2.1.2, I'll check, thanks for the info!

Would be great if there was an option in HA to rollback the image to a specific version. I keep all my addon backups for a month because of all the zwave issues lately :(

Well, for a few minutes all was well, I had voltage and amps values again, I was about to come here to thank you @davidcoulson , then they went away again. STRANGE!
I'm starting to suspect the problem is in the definition of the device, perhaps someone edited the properties for the device and broke it. Somehow it seems shortly after the rollback the device properties were updated automatically and once again I lost attributes that became unavailable again.
What a mess.
Next I'll try to remove the device from the network and add it back with the same name to see if it works.
Let me tell you, the next time I get this thing working I'll immediately disable updates and never update it again!

I don't know if I have backups from 2.1.2, I'll check, thanks for the info!

Would be great if there was an option in HA to rollback the image to a specific version. I keep all my addon backups for a month because of all the zwave issues lately :(

I'm using "Home Assistant Google Drive Backup" add-on and it gives you just that, try it out, it works like a charm!

I'm starting to suspect the problem is in the definition of the device, perhaps someone edited the properties for the device and broke it. Somehow it seems shortly after the rollback the device properties were updated automatically and once again I lost attributes that became unavailable again.

Did you try reinterviewing the node?

Yeah that is what i am using too, but you have to make sure it doesn't remove the backup otherwise it's impossible to roll back.

Another possible hint on the problem... from all the 33 devices I had, in one of the more recent z-wave updates I suddenly gained the notification of having 20 repairs to perform on those devices... quoting one paragraph:
"Z-Wave JS discovers a lot of device metadata by interviewing the device. However, some of the information has to be loaded from a configuration file. Some of this information is only evaluated once, during the device interview."
Something tells me those configuration files got beaten up pretty well and that's the root cause of all our issues... worth investigating IMHO, it's definitely not normal to have 20 repairs to do on almost all of my z-wave devices!

I'm starting to suspect the problem is in the definition of the device, perhaps someone edited the properties for the device and broke it. Somehow it seems shortly after the rollback the device properties were updated automatically and once again I lost attributes that became unavailable again.

Did you try reinterviewing the node?

yeah, the attributes are still there, but unavailable... a small cut from the properties:

Update: After excluding and including the Qubino devices (I have 2 of them), all entities are back available and reporting values.

The only thing strange is that firmware versions are way different, when both devices are the same bought at the same time.
Quite hard to imagine they have firmware versions that different, but I guess it can happen... and they both report being up to date... :-/

I'd say it's the update/upgrade/repair process that messes up with the device altogether, I don't know, I'm just reporting what happened to me hopping it will help other users or even the developers.
Cheers,

I've opened this issue under HAS Core as well, as I'm not sure if I was right to open it here directly. (I'd used the link in the Add-on documentation.)
When I first installed the 2.2.0, I was also presented with several "repairs" by HA Core. Each of the repairs said it was necessary to interview several devices. I performed this for each device. I didn't think much about it at the time, as it was conceivable that the add-on was fixing issues that earlier versions caused or didn't address themselves.
I echo the frustration noted above, but also balance that with the knowledge that the developers volunteer their time here, and do not have a means by which they can test every conceivable configuration. They also have their "day jobs/activities." I think there was a driver architecture change/reconciliation that started in July/August, and since that time some latent problems might have come up. Pure conjecture on my part.
For those who have not created and uploaded logs, I'd encourage you to do so. This is what helps the developers the most.

developers volunteer their time here, and do not have a means by which they can test every conceivable configuration. They also have their "day jobs/activities."

You are absolutely correct, I think we all understate, appreciate, and value that!
However, that has always been the case, and never in the past, at least that I recall, z-wave got to damaged as these last weeks.
It's not just z-wave, signal add-on is literally unusable now as well, perhaps it's just a sign of times, or a passing phase to quote Pink Floyd, but it's worth signaling our disappointment I guess, so that developers realize we're going down hill here.
I'll stop commenting now, I just realized we're on github, not on HASS Community... apologies to all for this.

I don't know if I have backups from 2.1.2, I'll check, thanks for the info!

Would be great if there was an option in HA to rollback the image to a specific version. I keep all my addon backups for a month because of all the zwave issues lately :(

I'm using "Home Assistant Google Drive Backup" add-on and it gives you just that, try it out, it works like a charm!

I've never had luck restoring ZWave addons. Every time, after restoring the backup, I get : Image ghcr.io/hassio-addons/zwave-js-ui/amd64:2.1.2 does not exist for addon_a0d7b954_zwavejs2mqtt. Is there a process outside of restoring the backup to make this work? (I usually just restore a VM snapshot.)

I've never had luck restoring ZWave addons. Every time, after restoring the backup, I get : Image ghcr.io/hassio-addons/zwave-js-ui/amd64:2.1.2 does not exist for addon_a0d7b954_zwavejs2mqtt. Is there a process outside of restoring the backup to make this work? (I usually just restore a VM snapshot.)

Usually you just need to wait longer for it to restore. Or just run the restore again.

https://github.com/home-assistant/core/issues/102477 for reference

Piling on here.  Current version: 2.2.3 and this morning every single device is "Dead".  I use this primarily for my iBlinds and a couple other ancillary items but the blinds are kinda critical.

Any update on this? Any fixes in the last days?

+1
2023-10-22 12:48:59.245 INFO Z-WAVE: [Node 063] Is dead
2023-10-22 12:48:59.292 INFO Z-WAVE: [Node 054] Is alive
2023-10-22 12:48:59.371 INFO Z-WAVE: [Node 039] Is alive
2023-10-22 12:48:59.499 INFO Z-WAVE: [Node 038] Is alive
2023-10-22 12:48:59.611 INFO Z-WAVE: [Node 053] Is alive
2023-10-22 12:48:59.660 INFO Z-WAVE: [Node 044] Is alive
2023-10-22 12:48:59.807 INFO Z-WAVE: [Node 055] Is alive
2023-10-22 12:48:59.849 INFO Z-WAVE: [Node 065] Is alive
2023-10-22 12:48:59.895 INFO Z-WAVE: [Node 064] Is alive
2023-10-22 12:48:59.943 INFO Z-WAVE: [Node 048] Is alive
2023-10-22 12:49:07.942 INFO Z-WAVE: [Node 026] Is dead
2023-10-22 12:49:20.319 INFO APP: GET /health/zwave 301 2.076 ms - 191
2023-10-22 12:49:38.483 INFO Z-WAVE: Controller status: Controller is unresponsive
2023-10-22 12:49:50.472 INFO APP: GET /health/zwave 301 5.830 ms - 191

Has anyone tried the 3.0.0 Add-On update yet? I'll give it a go tomorrow, but wasn't sure if anyone had beat me to it :)

Has anyone tried the 3.0.0 Add-On update yet? I'll give it a go tomorrow, but wasn't sure if anyone had beat me to it :)

I installed it yesterday and haven't had any issues. I was on 2.1.2 before due to issues I was having with later versions, with devices moving to a "dead" status randomly. Though after installation of 3.0.0 I was still presented with several repairs that were necessary (all tied to my motion sensors), I executed those and everything has been stable.
I can't speak, of course, to issues others were having. Mine, for the moment, seems to have been resolved.

Has anyone tried the 3.0.0 Add-On update yet? I'll give it a go tomorrow, but wasn't sure if anyone had beat me to it :)

I updated immediately and for a few days everything was fine.  Now I'm right back to 12-15/17 devices going dead and requiring everything from a simple "ping" to bring them back to completely removing/repairing.... which is a major PITA because it means retouching every single automation rule they were in.
I wish someone involved in this would bother to acknowledge this issue.

Update to 3.0.1 does not resolve the problem - after HA reboot the status "Controller is unresponsive"

Update to 3.0.2 and Home Assistant to 2023.11.2 resolve a priblem. 12 hours after update - all is ok

I can also confirm that 3.0.2 is working for me after lots of issued with the earlier versions. Running 500-series stick in a Proxmox VM. I am still running Home Assistant 2023.9.1 in case I needed to roll back the z-wave driver.
After disabling the soft reset, I have been running for 72 hours without problems so far.

so bad news. =(
after few hours have a problem instability Wave again
reboot entire node resolve problem, but appears again after few hours (
                             n 100 ms.

2023-11-15T18:36:47.667Z DRIVER » [REQ] [GetPriorityRoute]
node ID: 44
2023-11-15T18:36:47.671Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-11-15T18:36:48.774Z DRIVER » [REQ] [GetPriorityRoute]
node ID: 44
2023-11-15T18:36:48.779Z CNTRLR   Retrieving priority route failed: Failed to send the message after 3 attempts
(ZW0202)
2023-11-15T18:36:48.785Z DRIVER » [REQ] [GetPriorityRoute]
node ID: 54
2023-11-15T18:36:48.787Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-11-15T18:36:48.889Z DRIVER » [REQ] [GetPriorityRoute]
node ID: 54
2023-11-15T18:36:48.892Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.

self-enabled soft-reset after reboot& Disable it's again solve problems. Thanks a lot @Wiigian !
Soft-Reset is disabled at the software interface, the Z-Stick Gen5 does not support soft reset which is why this can cause issues. If you have ZWaveJS UI

Open ZWaveJS UI
Open the Menu -> Settings -> Z-Wave
disable / grey out the switch next to Soft Reset:

Funny the bot bumped this.  Updated to HA 12.3 last night and my ZWaveJS lost 13/15 devices.  My other automation system initiated a ping to no avail.  Manually restarting ZWaveJS brought all but one back.  I got that one back this morning by manually intervening.


Fix ctrl+enter in chat input when a codeblock is visible (#199717)

This could use a chat codeblock-scoped context key to be a little more precise. Fix #199692

This is porting https://github.com/microsoft/vscode/pull/199717 to the release branch, since it was left out when the branch happened


feat: global filter support

Adding support for global filters for resources, resolves #25

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

Comparison is base (b935d12) 95.13% compared to head (f621018) 94.74%.

Files
Patch %
Lines

pkg/filter/filter.go
75.00%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #37      +/-   ##
==========================================
- Coverage   95.13%   94.74%   -0.39%
==========================================
  Files          14       14
  Lines         842      857      +15
==========================================
+ Hits          801      812      +11
- Misses         26       30       +4
  Partials       15       15

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

:tada: This pull request is included in version 0.10.0 :tada:
The release is available on GitHub release :rocket:


Added support for importing images from public buckets

/cc @Prajyot-Parab @bkhadars

/lgtm
/hold for @mkumatag review


Seperate canvideo and canvideo web

Canvideo should not have the web features built in. This would just be extra, useless dependencies and files for people who want just canvideo.

Awaiting Issues
These are the list of issues that this issue is waiting for.

#106 - Then we don't have to worry about where the common/type/ folder goes


Deployment to netlify is broken

Deployment to netlify via Deploy button produce a faulty website.
The error message is

Function log from Netlify dashboard
Jan 9, 01:00:43 PM: INIT_START Runtime Version: nodejs:18.v18	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:d949ec0248c1b8fbc8cbc6df1c986e05fb933506b51d53be82d46f9a37125bea
Jan 9, 01:00:43 PM: 93c2447f ERROR  Invoke Error 	{"errorType":"Error","errorMessage":"unable to determine transport target for "pino-pretty"","stack":["Error: unable to determine transport target for "pino-pretty"","    at fixTarget (/var/task/node_modules/pino/lib/transport.js:144:13)","    at transport (/var/task/node_modules/pino/lib/transport.js:114:22)","    at normalizeArgs (/var/task/node_modules/pino/lib/tools.js:316:16)","    at pino (/var/task/node_modules/pino/pino.js:87:28)","    at file:///var/task/.netlify/server/chunks/logger.js:2:16","    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)"]}
Jan 9, 01:00:43 PM: 93c2447f Duration: 99.59 ms	Memory Usage: 79 MB	Init Duration: 207.71 ms

Thank you for the information. Issue has been fixed


Support LF linebreaks

Only recognizes linebreak with CRLF atm.
Should support LF due to more common use with cross-platform scripts.

@fflaten, as a stopgap, you can patch a current installation of the module as follows:
In ShowPSAst.psm1, as currently available via the gallery, replace:
            $text = [string]$InputObject
            if (Test-Path -LiteralPath $text)
            {
                $path = Resolve-Path $text
                $InputObject = [System.Management.Automation.Language.Parser]::ParseFile($path.ProviderPath, [ref]$null, [ref]$null)
            }
            else
            {
                $InputObject = [System.Management.Automation.Language.Parser]::ParseInput($text, [ref]$null, [ref]$null)
            }

with:
            $text = [string]$InputObject
            if (Test-Path -LiteralPath $text)
            {
                # To also support LF-only files, read the file in full and normalize the newlines to CRLF,
                # which the WinForms textbox control requires for proper display.
                $text = (Get-Content -Raw -LiteralPath $text) -replace '(?<!\r)\n', "`r`n"
            }
            $InputObject = [System.Management.Automation.Language.Parser]::ParseInput($text, [ref]$null, [ref]$null)

Given the unknown status of this project (as you know), I'm  not submitting a PR.
Generally, it would be nice if a cross-platform, console-based re-implementation were to be come part of the Microsoft.PowerShell.ConsoleGuiTools tools (which currently provide Out-GridConsoleView and Show-ObjectTree) - see:

https://github.com/PowerShell/GraphicalTools/issues/244

@mklement0 - I just don't have much extra time these days.
I should probably just archive the project and hope that someone starts something that works better cross-platform, but I could also consider handing off maintaining this project if someone offered.


ghost buffer communication using persistent MPI

Purpose
Add a ghost buffer communication implementation using persistent MPI
Content

[x] I have read and checked the items on the review checklist.

bors r+


Document the hover modes 'vline' and 'hline'

Support for these modes has been added a while ago but never documented.
It works by passing 'vline'/'hline' to hover or in the list of tools:
import hvplot.pandas  # noqa
from bokeh.sampledata.degrees import data as deg

deg.hvplot.line(x='Year', y=['Business', 'Computer Science'], hover='vline')  # or tools=['vline']

That is a nice one that I have been missing compared to HighCharts that I am also using.


Use php8.1, support symfony  6

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-4.1%) to 84.091%

Files with Coverage Reduction
New Missed Lines
%

src/Services/AppStatusCollector.php
1
87.8%

Totals

Change from base Build<PHONE_NUMBER>:
-4.1%

Covered Lines:
37

Relevant Lines:
44

💛  - Coveralls


Try to plug memory leak.

ping @gnprice These changes might be worth trying to see if they affect how quickly memory grows in our server.  The presence codepath is heavily used on our production servers, and if the leak is related to presence, the code here seemed the mostly plausible as being related.  I haven't done any actual stress tests or measurement, though.

Looking forward to see the result.

I think this is unlikely to be the cause of the problem (and I'm a little skeptical of that inlining, in that there's a good chance we'll want to add further callers later).
Far more likely, since this is a recent regression, is that the recent work @showell did with presence perf optimization has a cursor it's not garbage-collecting properly.

Yeah, this change is probably a reach, since I agree that Python should release the UserProfile objects that are closure variables in the lambda.
These are my recently merged commits, if some one wants to audit it for possible leaks:
https://github.com/zulip/zulip/commits?author=showell
On September 20th I committed lots of stuff related to caches.
Earlier in the month (September 10th) I committed this raw-SQL speedup:
https://github.com/zulip/zulip/commit/7fbffb8e30bfa4f463e896814c4913b3d7bd9118
On September 8th there was this commit, which led to some postrgres-related discussion with @gnprice:
https://github.com/zulip/zulip/commit/730da55bf89dfa4d27ae444b2814d577117cab26


About pretraining with Mapillary Vistas

Hi, thanks for you codes. And I have a question about pretrain on Mapillary Vistas.
It is general to pretrain with Mapillary Vistas and fine-tune on Cityscapes. The thing and stuff categories are quite different for these two data sets, is there some special treatment required?
Especially, some things (e.g. traffic lights, poles) in Mapillary Vistas are marked as stuff in Cityscapes, how you deal with such categories?

Hi pingjun18-li,
Thanks for the question.
For the Mapillary Vistas pretraining, we do not do anything special, except that we resize the image's longest side to either 2177 (as the Panoptic-DeepLab paper) or 2049 (as the SWideRNet paper), in order to handle the large resolution variation in Mapillary Vistas images.
The resizing can be done in the codebase by setting min_resize_value = max_resize_value = 2177 (or 2049).
When fine-tuning on the Cityscapes, the last prediction layer is removed and randomly initialized.
What you proposed there to specially handle the classes may benefit the fine-tuning. But, we have not explored that.
Cheers,

Closing the issue, as it has nothing to do with the library itself.
Please feel free to open a new one if you have questions about the DeepLab2 library.
Thanks.


Subscriber emotes from some channels don't show when I'm the one using them

Describe the bug:

Emotes from 2 of the 3 channels I am subscribed to remain in text form when I send them, and can't be found in the Alt+e menu.
Emotes from these 2 channels show correctly when sent by other people.
Emotes from these 2 channels show correctly in twitch-tui, when I send them through the twitch.tv chat (see screenshot)

To Reproduce:
I don't have reliable steps since it's my specific situation. The best I can suggest is:

Be subscribed to at least 2 channels.
Attempt to send messages containing the related subscriber emotes: emotes from one channel may remain in text form when sent.
Attempt to find the subscriber emotes in the popup menu: emotes from one channel may not be found.

Expected behavior:

I expect emotes to display as images when sent, and to show up in the popup menu when searched.

Screenshots:

System:

Twitch-tui version: 2.6.11

Operating System: Linux 6.9.5-arch1-1

Terminal: kitty 0.35.1

Shell: bash 5.2.26(1)-release

config.toml:

[twitch]
username = "Luky75"
channel = "luky75"
server = "irc.chat.twitch.tv"
token = "redacted"

[terminal]
delay = 30
maximum_messages = 500
verbose = false
first_state = "Dashboard"

[storage]
channels = false
mentions = false

[filters]
enabled = false
reversed = false

[frontend]
show_datetimes = true
datetime_format = "%T"
username_shown = true
palette = "pastel"
title_shown = true
margin = 0
badges = true
theme = "dark"
username_highlight = true
state_tabs = false
cursor_shape = "user"
blinking_cursor = true
inverted_scrolling = false
show_scroll_offset = false
twitch_emotes = true
betterttv_emotes = true
seventv_emotes = false
frankerfacez_emotes = true
favorite_channels = []
recent_channel_count = 5
border_type = "plain"
hide_chat_border = true
right_align_usernames = false
show_unsupported_screen_size = true

Additional context:

If this issue is hard to diagnose on your own because you're not subscribed to multiple channels, feel free to ask me to do "technical" stuff. I don't know much about Rust, therefore I'd be happy to have an excuse to get into it.

Hello, and thanks for the issue! Before actual diagnosis of code or anything, how did you generate your token?

Oops, I see that you're the same author as #611. I don't think additional scopes are needed, so you did generate your token properly.

Might be an issue between the current and previous minor versions of twitch-tui. Could you remove the cache located at ~/.cache/twt? 2.6.11 requires a cleared cache for subscriber emotes to work properly.

I actually generated a different token since. When I noticed the issue I am describing here, I suspected that https://twitchapps.com/tmi/ wasn't giving me enough scopes, so I generated another one with https://twitchtokengenerator.com instead, with the following scopes: chat:edit, chat:read, user:read:chat, user:read:emotes, user:read:emotes, user:read:follows, user:read:subscriptions, user:write:chat. This is the token used for this bug report, and that I currently use in my config.
I also made sure $TWT_TOKEN wasn't set to some old token (it is unset).

Could you remove the cache located at ~/.cache/twt? 2.6.11 requires a cleared cache for subscriber emotes to work properly.

I quit twt, did rm -r ~/.cache/twt/, started twt, and tried to send dekillKermit and search it in the popup menu: the issue persists.

Alright, looks like I'll have to dig deeper then.

@Nogesma I think #591 might be the cause of this problem, but I'm not 100% sure. If you could give any insight, I'd very much appreciate it.
Besides that, @LukyLurks have you tried other recent versions, such as 2.6.10?

with 2.6.12: seemingly the same behavior as with 2.6.11 except I didn't check what happens when others send subscriber emotes (let me know if you'd like me to check).
with 2.6.10: subscriber emotes always show as text in twitch-tui when I send them, even when I send them from twitch.tv. Again I didn't check what happens when other people send them.

Could you do the check for seeing what happens when others send subscriber emotes? Thanks.

I also noticed in your config that you have seventv_emotes set to false. I'm not certain that this would fix your issue, but have you tried setting it to true?

Before 2.6.11 there wasn't any checks for if users actually could send those emotes, so twt displayed subscriber emotes from the current channel for everyone.
I'll try to see if I'm using the wrong api to get subscriber emotes. I'll let you know if I need any more info figuring that one out.

I just pushed a draft PR with what I think fixes it, could you please try it?

@Nogesma It seems to be working. The emotes appear in the popup search, and they show correctly when sent. People's subscriber emotes (both from the current channel and different channels) seem to be showing correctly as well.
@Xithrius

Toggling seventv_emotes seemingly did nothing with versions 2.6.10, 2.6.11, 2.6.12, Nogesma's PR #616.
Regarding other people sending subscriber emotes: with 2.6.10 if the emotes are from the current channel they show correctly, and if they're from a different channel they don't. 2.6.12 behaves like 2.6.11.

Thank you both!

Thank you so much for going through each version for testing. I'll be testing the PR myself later today, and if all is good then I'll do a release as soon as I can once it's merged.

Fix available in https://github.com/Xithrius/twitch-tui/releases/tag/v2.6.13

Thank you @LukyLurks for the issue, and @Nogesma for the fix!


Issue#8788 Ciscoumbrella Repackaging with Data connector fix

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@v-rbajaj , please update the zip file of the connector package. Thanks.

Closing this PR as same we have open in - https://github.com/Azure/Azure-Sentinel/pull/9608


Migrate code for exporting CSV to the overview-filters component

This PR does the relatively straightforward migration of code for exporting data to CSV from the overview-page to the overview-filters, as outlined in #517.

I added a draft PR that addresses some of this to help inspire some of the test stuff: https://github.com/GoogleChrome/webstatus.dev/pull/651
Feel free to take a look. It doesn't address all of the comments though.


How to record the order of kernel and automatically launch them?

Hi, everyone!
We are currently working on implementing our simulator using Taichi AOT. We can dump the shaders according to the demo code of implicit_fem.py. However, it seems that we cannot record the calling order of each kernel and we have to manually launch the kernels, which is not very productive. Is it possible to dump the launch order of the kernels and automatically launch them?
Thanks in advance!

You can check out the compute graph work we have been doing. We decided to go with a graph API instead of a tracing API, as capturing a series of kernels is very hard to implement correctly. @ailzhang knows more about this

@Hanke98 You can checkout a cgraph version of implicit fem here https://github.com/taichi-dev/Taichi-UnityExample/blob/main/scripts/implicit_fem.cgraph.py. With this you'll be able to encode the calling order of kernels and simplify the calling code inside deployment environment. https://github.com/taichi-dev/Taichi-UnityExample/blob/main/Assets/Scripts/ImplicitFem.cs#L218-L244 Please note this feature is WIP so API/implementation details might change, but we'll keep the demos in UnityExample repo up to date.


[SPARK-21479][SQL] Outer join filter pushdown in null supplying table when condition is on one of the joined columns

What changes were proposed in this pull request?
Added TransitPredicateInOuterJoin optimization rule that transits constraints from the preserved side of an outer join to the null-supplying side. The constraints of the join operator will remain unchanged.
How was this patch tested?
Added 3 tests in InferFiltersFromConstraintsSuite.

Test build #88215 has started for PR 20816 at commit ac17976.

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/testing-k8s-prb-make-spark-distribution/1494/
Test PASSed.

Test build #88215 has finished for PR 20816 at commit ac17976.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/88215/
Test FAILed.

Merged build finished. Test PASSed.

Test build #88216 has started for PR 20816 at commit 1c5dedb.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1495/
Test PASSed.

Test build #88216 has finished for PR 20816 at commit 1c5dedb.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/88216/
Test FAILed.

How does it look now, @gatorsmile? Please let me know if there's anything I can improve.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1514/
Test PASSed.

Merged build finished. Test PASSed.

Test build #88242 has started for PR 20816 at commit b10879f.

Test build #88242 has finished for PR 20816 at commit b10879f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/88242/
Test PASSed.

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/testing-k8s-prb-make-spark-distribution/1632/
Test PASSed.

Test build #88405 has started for PR 20816 at commit 7fe9329.

Test build #88405 has finished for PR 20816 at commit 7fe9329.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/88405/
Test FAILed.

Ping @gatorsmile

retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1765/
Test PASSed.

Merged build finished. Test PASSed.

Test build #88601 has started for PR 20816 at commit 7fe9329.

Test build #88601 has finished for PR 20816 at commit 7fe9329.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/88601/
Test FAILed.

Test build #88994 has started for PR 20816 at commit 7fe9329.

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/testing-k8s-prb-make-spark-distribution/2049/
Test PASSed.

Test build #88994 has finished for PR 20816 at commit 7fe9329.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/88994/
Test FAILed.

retest this please

Test build #89022 has started for PR 20816 at commit 7fe9329.

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/testing-k8s-prb-make-spark-distribution/2070/
Test PASSed.

Test build #89022 has finished for PR 20816 at commit 7fe9329.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/89022/
Test FAILed.

Test build #89420 has started for PR 20816 at commit 194e6e7.

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/testing-k8s-prb-make-spark-distribution/2362/
Test PASSed.

Test build #89420 has finished for PR 20816 at commit 194e6e7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89420/
Test PASSed.

Merged build finished. Test PASSed.

cc @cloud-fan

since this does fix the problem in a reasonable way, I'm merging it and will clean it up in https://github.com/apache/spark/pull/21083

thanks, merging to master!

Thank you, @cloud-fan and @gatorsmile !


Unknown problem with tag!

Hey everyone,
I'm pretty new to Rust and I wanted to start working with the nom library. I can get this basic example to work: Output [97, 98, 99, 100]
#[macro_use]
extern crate nom;

use std::str;
use nom::IResult::{Done, Error, Incomplete};
use nom::AsBytes;

fn main() {
    named!(x, tag!("abcd"));
    let msg = "abcdefghi";
    let r = x(msg.as_bytes());
    match r {
        Done(I, O) => println!("Output {:?}", O),
        Error(err) => println!("Error {:?}", err),
        Incomplete(n) => println!("Incomplete {:?}", n),
        _ => println!("something went wrong"),
    }
}

But once I change the sequence tag looks for, and the msg I get an error: Error Tag
#[macro_use]
extern crate nom;

use std::str;
use nom::IResult::{Done, Error, Incomplete};
use nom::AsBytes;

fn main() {
    named!(x, tag!("type"));
    let msg = "abcdetypefghi";
    let r = x(msg.as_bytes());
    match r {
        Done(I, O) => println!("Output {:?}", O),
        Error(err) => println!("Error {:?}", err),
        Incomplete(n) => println!("Incomplete {:?}", n),
        _ => println!("something went wrong"),
    }
}

This really has me confused, and after looking through the documentation I can't get anything out of the error "Tag", other than I assume the error has to do with the tag! macro. If someone could provide any guidance that would be great

hello,
tag is trying to find the token (here, "type") at the beginning of the input you pass it. It does not scan the whole input to find it.
Which format are you trying to parse? There might be a more appropriate way for what you want to do.

Thank you for the help!
I am trying to parse a file type similar to Google's protobuf format. Basically I want to scan a txt document for types and then use the name that comes after the type keyword, and the fields inside the curly braces to build a rust equivalent of the object. Here's an example:
type foo {
        int32 bar;
}

And from there determine there is a type foo named bar, that has an int32 as a field.


Use next published revocation registry when no active registry is available

Changes in this PR ensure the next published revocation registry is enabled and used if there are no active revocation registries.
Please note tests have not (yet) been updated, and the code may benefit from additional cleanup/refactoring - out of scope for the moment, happy to take it on if it seems like a good idea.
I am using the latest version of black 20.8b1, not sure if that is the reason for all the formatting changes and if those are expected: please let me know if/how I should be amending them.

This is the right idea, where the next update was going. But just setting the state shouldn't work because there still is no first entry in the ledger: it should use the activation logic. I will take a real look first thing in the morning.

See next update


Improve API

This PR improves on the API in the following ways:

Docstrings are added for open/close. The boolean return value can be confusing in terms of what it actually means, so the docstrings are helpful.
TreeItem::{child, child_mut}() accessors are introduced. I need this for a downstream project

Should be good to merge now 🙂

Awesome! Thanks again for sharing your improvements!

Its included in v0.5.0 now.