Text drop shadow is now the right colour, even with blur enabled

Fixes: https://github.com/pixijs/pixi.js/issues/3960
Don't see why it was set to ignore the shadow colour before when blur was enabled... that behaviour goes back to v3 days. But it feels like incorrect behaviour to me which this PR fixes

fiddle to demonstrate the fix: https://jsfiddle.net/themoonrat/zmt1ojph/


the example doesn't work anymore

Hi, thank you for the example but i tried this example on new xcode 16 it doesn't work anymore. if can guide me how to make it work again that would be super helpful.

made it work using this
  override func application(_ application: NSApplication, open urls: [URL]) {
        if let url = urls.first {
            FileOpenHandlerPlugin.instance.handleFileOpen(pathname: url.path);
        }
  }


Add a suffix to the stacks to easily identify Python stacks

@alonbentamar can this be merged? Make sure to squash and merge, and rebase on 0.3.7g1.

@alonbentamar can this be merged? Make sure to squash and merge, and rebase on 0.3.7g1.

Can be merged, the backend is ready. The branch is already up-to-date.

Your commit is based on 0a1f4ca330a2dad98f10db9f198da9ce5187af48 and in any case should not be merged to "master" but to a branch based on v0.3.7g1 which is 3837a0a76ccf2d3328100f9e47a25de3b5d9e9eb.

@Jongy Changed it, is this okay now?


README update for repository

Updated README to reflect the repository better. Let me know if anything should be added/removed

Also added some miscellaneous housekeeping edits to close some issues


Where is @Html.Action() in RC 1?

Is @Html.Action() supposed to be in RC1?

Child actions, which is the feature Html.Action surfaced, aren't being brought forward in Mvc 6. View Components are a replacement for them but work a bit differently. http://www.davepaquette.com/archive/2016/01/02/goodbye-child-actions-hello-view-components.aspx has a write up about the differences and the usage.

Thanks Pranav. Perhaps this discussion has already taken place and I missed
it. For that I apologize. But View Components are not a replacement. A
kludge can be made but it is less elegant and powerful than the original
@Html.Action. Is there some reason why both can't be implemented?
On Thu, Jan 7, 2016 at 9:35 PM, Pranav K<EMAIL_ADDRESS>wrote:

Child actions, which is the feature Html.Action surfaced, aren't being
brought forward in Mvc 6. View Components are a replacement for them but
work a bit differently.
http://www.davepaquette.com/archive/2016/01/02/goodbye-child-actions-hello-view-components.aspx
has a write up about the differences and the usage.
—
Reply to this email directly or view it on GitHub
https://github.com/aspnet/Mvc/issues/3888#issuecomment-169872666.

I can't find the relevant design notes for why child actions were dropped, but it's unlikely we would revive it. What would be valuable feedback is if you could list specific scenarios that don't work with view components.

I've got a modal SCRUD scaffolder I've been using with MVC4 which I would
like to move to MVC6. This scaffolder creates views with code for multiple
scenarios, where I subtract the code I don't need, since it is much easier
to delete code than it is to write code. Especially if the scaffolder uses
all the correct types. But at the same time I'm trying to keep the code as
DRY as I can. I only want to access the actions if the user is
authenticated and authorized. A sample scenario would be a view that is
used for a modal search crud interface, but the same view could appear in
the index itself as a partial view. The view generation does not need more
than few parameters such as dialog ID and and post refresh function to call.
@Html.Action() is perfect for this. Compared to just the one line, I've
implemented a far more verbose and contorted solution using a view
component, but it seems like reaching around my head to scratch my nose. If
you would like some code let me know. I can try to get you the nuget
package for the MVC4 scaffolder.

@gkochanowsky Yes, please show us the code you are trying to migrate to MVC 6 and we will take a look.

I have an example of how I'm trying to work around the issue with MVC 6 - [https://github.com/gkochanowsky/SCRUD].
Do you need to see an example of how it's implemented in MVC4 using @Html.Action()?

Do you need to see an example of how it's implemented in MVC4 using @Html.Action()?

Yes

@davidfowl you can find a freshly scaffolded version @ [https://github.com/gkochanowsky/SCRUD_MVC4].
You will need to attach the mdb file to your local instance of SQL Server and fix the connection string.

The code you have should be fairly easy to convert to use view components by first converting your child actions to be view components and then calling @Component.InvokeAsync instead of @Html.Action. For any child actions that you still want to still be accessible as public endpoints you can refactor them to call into your view components using the ViewComponent() helper method on Controller. The nice thing about this model is that local calls don't have to fake any HTTP-isms and your public endpoints are explicit.

I've already done it, Please see the SCRUD codebase [https://github.com/gkochanowsky/SCRUD].
There are several concerns with this approach. First, it's a lot more lines of code. Second, the view component context is not the same as the controller contexts, for example the Identity components are not the same. Third, the view component as far as I can tell does not support cross cutting concerns such as security in the same manner as controllers. It is a mess if one is trying to keep the code DRY. Very good at solving the problems it was meant to solve, but does not replace @Html.Action.

What kinds of things are you trying to do in your view component that you need the controller context for?
I looked at the updated code, but it looks like the controller actions are not calling your view component (by calling the ViewComponent() helper method). The controller actions still duplicate the view component code, which I think you can avoid by calling the view component from your actions.
Security as a cross cutting concern should only be relevant for your public endpoints. You can implement your public endpoints using your view components (by calling ViewComponent()) and then use all the standard controller infrastructure for handling these cross cutting concerns.

In MVC 4 I could do things like line 20. A single line to call an action at line 39. Just one line of code to generate the action HTML.
To do the same thing in MVC6 I've had to write all of the following: view component, view component view, common interface. All of this to use the same search view and same search linq
In the first case I can implement the security for that action in one place. In the second case I've got to do it twice.
If you have a better way of doing this in MVC 6 please show me in code. Because that is a lot of trouble to go through in MVC 6 for something that was done easily with one line of code in MVC 4.

@gkochanowsky:

In MVC 4 I could do things like line 20. A single line to call an action at line 39. Just one line of code to generate and insert into a view, with no model, the action HTML.

This has not changed: you would just write @Component.Invoke("MyComponent") as opposed to @Html.Action("MyAction").

To do the same thing in MVC6 I've had to write all of the following: call to view component, view component, view component view, common interface. All of this to use the same search view and same search linq

Instead of calling @Html.Partial("Search") in your view component view, your Search.cshtml view should actually become the view component view. Then, everywhere you have been calling @Html.Partial("Search"), you would instead call @Component.Invoke("Search").
As for the 'common interface' thing, why not set up your Repository_Person so that it gets injected into controllers and components with everything it needs? I believe you can get ModelState one way or another through DI and I know you can get the HttpContext to get the IPrincipal from it. This seems orthogonal to the issue of child actions versus view components.

In the first case I can implement the security for that action in one place. In the second case I've got to do it twice.

You should only need to implement it once: in the view component.
I believe @danroth27 explained it fairly well, but I know sometimes I learn better with a visual, so here is a tabular comparison between MVC5 child actions and MVC6 view components:

MVC5
MVC6

Declare a model class for the partial view to use
Declare a model class for the view component view to use

Put your logic into a controller action
Put your logic into a view component

Put your Search.cshtml view into the Views/Shared folder
Put your Search.cshtml view into the Views/Shared/Components folder

Invoke the child action from a view with @Html.Action("MyAction")
Invoke the view component from a view with @Component.Invoke("MyComponent")

Decorate the controller action with [ChildActionOnly] if you don't want to expose the action
Return a ViewComponentResult from a 'thin' controller action if you do want to expose the view component

A code example please that implements SCRUD as demonstrated in the code I made available implemented as you suggest.

I don't mean to be rude, it's just that we've told you exactly what changes need to be made and where. While they are few, it is your code base and I don't think I will find the time to work on it though I cannot speak for anyone else.
A quick, final bit of advice based on the code you posted:

Your problem is that you still have calls to the Search.cshtml partial.
Copy/paste the contents of Search.cshtml into your component's view file
Ditch Search.cshtml
Change any Html.Partial and PartialView calls for the Search partial Into Component.Invoke and ViewComponent calls for the view component
You may need to move some of your other partials into the Shared folder

Sorry if I was rude. I only thought that since I supplied code quickly upon request there might be some reciprocation. So I will make the changes as you recommend.
You allude to the ability to get ModelState through DI. Can you point me to exactly how I would do this. And does the app have only one instance of ModelState, or are they created per instance of controller or component view? If they are created per instance of controller/component view exactly how would DI work when adding an error to a particular controller instance?
I am new to DI. And percolating errors up to the controller/component views from lower levels is important functionality.

I've tried to apply security to a view component, but it doesn't appear to be working. Is it not yet implemented?

I think you may be able to get ModelState from the ActionContext (try ScopedInstance from DI or something like that, you can also poke around in the debugger inspector tooltip to browse what's available.)
As for security, what is the scenario you are trying to accomplish and what have you tried that is not working?

@tuespetre , I've already retrieved ModelState. You described it as "the 'common interface' thing". I was particularly interested in your comment ("I believe you can get ModelState one way or another through DI"). So I was wondering if you could point me in the right direction on how to do that.
Right now I'm trying to implement Windows Authentication. If I decorate the controller and the view component with the [Authorize] attribute it seems to work, since I am an authenticated user on my local domain. However when I try to add a role [Authorize(Roles = "role-i-am-in")] then I get a 403. Not the result I was expecting.

@tuespetre, I've updated the SCRUD project with my attempt to get Windows Authentication using AD groups working. The changes to project.json, Startup, View Component Decoration, Person Controller Decoration.

I see. I don't know that the AuthorizeAttribute is truly applied to ViewComponents. If you think about it, the only way to get to a ViewComponent is through some controller action anyways, so it is kind of redundant. Now, within a ViewComponent one might make use of the request's current identity to shape behaviors or conditionally render controls and so forth.
As for the 403 you are now getting, I believe that is to be expected with ASP.NET 5. If you have the AuthorizeAttribute applied to a controller action (via global-, controller-, or action-level decoration) and the attribute detects an authorization failure, it calls Challenge on your configured authentication provider. That can result in a 403 if you are authenticated but do not meet the criteria of the specified policy or role, which is a bit different than in MVC5, where the attribute just seemed to automatically redirect to the login page regardless of the fact that the user may already be logged in.
I prefer this new behavior, although like yourself, I spent a little time picking up on the differences in operation.

Hmmm... looking over the rest of your code, it seems you are applying your authorization policy globally in the Startup class as well. So any request will need to be authenticated, which may not be what you intended.
I also recommend checking out this question on StackOverflow: http://stackoverflow.com/questions/28542141/windows-authentication-in-asp-net-5

As @tuespetre stated:

I don't know that the AuthorizeAttribute is truly applied to ViewComponents. If you think about it, the only way to get to a ViewComponent is through some controller action anyways, so it is kind of redundant. Now, within a ViewComponent one might make use of the request's current identity to shape behaviors or conditionally render controls and so forth.

So am I correct in assuming that a view component is not on the same level as a controller action? So is there an implicit call to a controller? Other than the placement of the component view, how is that determined? Do I loose action level security by using view components?

Thank you @tuespetre for the link to the StackOverflow post. Are future versions of NET5 going to make that less painful?

@gkochanowsky:

So am I correct in assuming that a view component is not on the same level as a controller action? So is there an implicit call to a controller? Other than the placement of the component view, how is that determined? Do I lose action level security by using view components?

Looking again at the table I posted earlier, I will answer your questions like so:

Correct, a view component is not the same as a controller action. A view component receives the benefits of dependency injection and can run some developer-defined code and logic before returning what is essentially a partial view.
There is no implicit call to a controller involved. When you invoke Component.Invoke from a view or return ViewComponent("MyComponent") from a controller action, you're basically saying the same thing as Html.Partial or return PartialView("MyPartial"), except the arguments you pass in get run through the view component's code, which then produces the partial.
See (2).
No. In your case, you would have one controller action that returns a view, which in turn invokes the view component, and another controller action that directly invokes the view component. In both scenarios you would apply the 'action-level security' to these controller actions, just like when they invoked 'plain old partial views' instead of view components.

So it may help if you tell yourself, "View components are basically partials with a little layer of code on top of them." The layers of security have not changed.
@gkochanowsky:

Thank you @tuespetre for the link to the StackOverflow post. Are future versions of NET5 going to make that less painful?

The ASP.NET team has been working hard on tightening up the IIS-hosted story and whatever else related to it. Some big changes are yet to come in February with the dotnet-cli per my understanding, plus it sounds like a new version of HttpPlatformHandler is going to come out to address some of the bumps that were hit after beta8 was released.
Just so we're clear, too, let me explicitly state that I'm not a part of the ASP.NET team or Microsoft at all, I'm just personally invested in the community and helping the team answer questions on GitHub because I want them to have more time to focus on their work :stuck_out_tongue:

It seems that the big questions here have been answered so I'm closing this.
If there are further questions please log new issues on them.

 Aurelia vs Angular — a Feature by
Feature Comparisonh
y
Connections In The News
Rob Eisenberg
sitepoint.com · 15 hours ago
Aurelia vs Angular — a Feature by Feature Comparison
Primarily created by Rob Eisenberg of Durandal Inc., Aurelia targets the
same problem space as AngularJS. However, Aurelia uses a modern approach to
ease development and solve a lot of the problems that plagued AngularJS. In
this article, we’ll take a detailed look at AngularJS and ...
Message Rob
·
Share
·
Wrong Person?
You are receiving Connections in the News emails. Learn more about this
feature. Unsubscribe.
This email was intended for Gene Kochanowsky (DBA, Data Analyst, FSU
College of Medicine, Claude Pepper Datauh Center). Learn why we included
this.
If you need assistance or have questions, please contact LinkedIn
Customer Service.
© 2016 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA
9404hu3. LinkedIn and the LinkedIn logo are registered trademarks of
LinkedIn.
LinkedIn does not guarantee that news articles are accurate or about the
correct person.

Did you ever totally resolve this issue?  ViewCOmponents are not made to process requests and do model binding.  I need the ability to execute an action with the sames results that Html.Action did.
I'm not sure I understand how ViewComponents are helpful with this.  I have used ViewComponents in several places now, though, but this type of use doesn't apply.
Example:
I have a site where the same controller and action is loaded on every page of this site, but based on the requested page, different view components are loaded.
One of these viewcompoents is a form.  I need to be able to submit the form to the same controller/action, but the view component loaded should be the results of submitting the form.  (i.e. a search page and search results)
A viewcomponent is not ideal for this as that is not what it's designed to do.

rsimmermon, not really. But I haven't been doing any core development for
awhile. Still working in classic .NET. It does what I need.
On Wed, Sep 27, 2017 at 3:06 PM, rsimmermon<EMAIL_ADDRESS>wrote:

Did you ever totally resolve this issue? ViewCOmponents are not made to
process requests and do model binding. I need the ability to execute an
action with the sames results that Html.Action did.
I'm not sure I understand how ViewComponents are helpful with this. I have
used ViewComponents in several places now, though, but this type of use
doesn't apply.
Example:
I have a site where the same controller and action is loaded on every page
of this site, but based on the requested page, different view components
are loaded.
One of these viewcompoents is a form. I need to be able to submit the form
to the same controller/action, but the view component loaded should be the
results of submitting the form. (i.e. a search page and search results)
A viewcomponent is not ideal for this as that is not what it's designed to
do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Mvc/issues/3888#issuecomment-332624161, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABv2s-5WNRFSlrHuCZV6V0pWdSpyC6eEks5smpzDgaJpZM4HA3Cs
.


[TS-3648] Desire support for client TLS cipher in custom log format

Took @acaciocenteno's original PR here and updated it a bit: https://github.com/apache/trafficserver/pull/122

added docs and changed log tags to be more in line with ats conventions
removed some accessor methods and reordered where log tags are set to happen at the same time @fpesce was already grabbing some SSL info
made other changes suggested in the original PR

Looks good to me.   A straightforward reworking of acacio's original PR in the face of the other SSL logging changes that have been made.


HA 0.62 Docker edition. Problem with philips xiaomi light.

Have a philips xiaomi light.
I upgrade homeassistant to 0.62 version.
My log:
2018-01-27 06:24:56 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform xiaomi_miio
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_component.py", line 189, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
result = coro.send(None)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 212, in coro
res = func(*args, **kw)
File "/usr/src/app/homeassistant/components/light/xiaomi_miio.py", line 64, in async_setup_platform
from miio import Device, DeviceException
File "/config/deps/lib/python3.6/site-packages/miio/init.py", line 2, in
from miio.protocol import Message, Utils
File "/config/deps/lib/python3.6/site-packages/miio/protocol.py", line 190, in
Const(Int16ub, 0x2131),
File "/usr/local/lib/python3.6/site-packages/construct/core.py", line 1277, in init
super(Const, self).init(subcon)
File "/usr/local/lib/python3.6/site-packages/construct/core.py", line 287, in init
raise TypeError("subcon should be a Construct field")
TypeError: subcon should be a Construct field

This device properly work on HA 0.59

With the combination python-miio 0.3.4 + construct  2.9.27, I got following error:
2018-02-04 14:47:55 INFO (MainThread) [homeassistant.components.vacuum.xiaomi_miio] Initializing with host <IP_ADDRESS> (token 12345...) 2018-02-04 14:47:55 ERROR (MainThread) [homeassistant.components.vacuum] xiaomi_miio: Error on device update! Traceback (most recent call last):   File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 397, in _async_add_entity     yield from entity.async_device_update(warning=False)   File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 308, in async_device_update     yield from self.hass.async_add_job(self.update)   File "/usr/local/lib/python3.6/asyncio/futures.py", line 331, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/local/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup     future.result()   File "/usr/local/lib/python3.6/asyncio/futures.py", line 244, in result     raise self._exception   File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/local/lib/python3.6/site-packages/homeassistant/components/vacuum/xiaomi_miio.py", line 368, in update     state = self._vacuum.status()   File "/config/deps/lib/python3.6/site-packages/miio/vacuum.py", line 108, in status     return VacuumStatus(self.send("get_status")[0])   File "/config/deps/lib/python3.6/site-packages/miio/device.py", line 216, in send     m = Message.build(msg, ctx) TypeError: build() takes 2 positional arguments but 3 were given

@RiRomain see the comments above, especially the one from @kabturek.

The patch was integrated in hass 61.2, still doesn't work (as zamzas pointed out).
I check in the source, the modification from the patch are there.

Following this too, now that I finally manage to get my vacuum token...

I use HA as an official docker container on x64 architecture.
I do not install additional libraries, and do not delete them.
Philips lamp was working fine in 59.1.
When the container is updated to a new version, the lamp stops working.
I see errors in the log.

HA 62.1 - philips xiaomi light does not work.

The fix will be part of HA 63.0! Please check the release notes carefully.

Update HA to 0.62.1.
Successfully installed python-miio-0.3.5
Installed construct (2.9.24)
Log:
2018-02-05 10:35:09 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform xiaomi_miio
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_component.py", line 189, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
result = coro.send(None)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 212, in coro
res = func(*args, **kw)
File "/usr/src/app/homeassistant/components/light/xiaomi_miio.py", line 76, in async_setup_platform
device_info = light.info()
File "/config/deps/lib/python3.6/site-packages/miio/device.py", line 271, in info
return DeviceInfo(self.send("miIO.info", []))
File "/config/deps/lib/python3.6/site-packages/miio/device.py", line 216, in send
m = Message.build(msg, ctx)

Individual components update must coincide with HA major/minor update, even if individual components have already updated for sometime. Which may take weeks.
Only workaround is manual modification of the python files, but with hassio/docker it seems rather unconvenient or near-impossible. With Hassbian and other distributions it’s not as tiresome.

I'm not sure this will fix the issue, I applied the change from https://github.com/home-assistant/home-assistant/commit/137933a774625ef901904f14335dca6eb957915d and made sure I had the latest construct.
Name: construct Version: 2.9.27
Name: python-miio Version: 0.3.5
By start I still got an error for the vacuum component (I only have a vacuum from xiaomi)

2018-02-05 11:52:56 ERROR (MainThread) [homeassistant.components.vacuum] xiaomi_miio: Error on device update!
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 397, in _async_add_entity
yield from entity.async_device_update(warning=False)
File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 308, in async_device_update
yield from self.hass.async_add_job(self.update)
File "/usr/local/lib/python3.6/asyncio/futures.py", line 331, in iter
yield self  # This tells Task to wait for completion.
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
future.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 244, in result
raise self._exception
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/vacuum/xiaomi_miio.py", line 368, in update
state = self._vacuum.status()
File "/config/deps/lib/python3.6/site-packages/miio/vacuum.py", line 108, in status
return VacuumStatus(self.send("get_status")[0])
File "/config/deps/lib/python3.6/site-packages/miio/device.py", line 216, in send
m = Message.build(msg, ctx)
TypeError: build() takes 2 positional arguments but 3 were given

@RiRomain This line isn't part of python-miio 0.3.5 anymore: m = Message.build(msg, ctx)
It's obviously you aren't using python-miio 0.3.5. Do you know the command line parameter "--skip-pip"? If you start homeassistant (bin/hass) it will retrieve all requirements. The requirements are pinned to a specific version number (cp. https://github.com/home-assistant/home-assistant/blob/dev/requirements_all.txt). If you update python-miio manually a startup of homeassistant (<=0.62.1) will downgrade the requirement again! Please update homeassistant to the "dev" version. It will fix the issue properly.


Update virtual-machines-create-custom.md

Updated a line to include that users are able to add a VM to use an existing storage account, which cannot be done in the Quick Create method (only the custom create).

Hi @mmccrory, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


👨💻fix argocd routes🔨

Route parts are changed like it is shown in the argocd-operator spec example:
https://github.com/argoproj-labs/argocd-operator/blob/master/examples/argocd-route.yaml

Yeah. Since I know the shortcut now, I can put those like everywhere😈🤗


Template substitutions without braces have incorrect ranges

Currently the grammar is able to pick up a template substitution using "${example}" syntax however using "$example" syntax returns an incorrect range and does not pick up example as an identifier.
The tree shows (for the ${} syntax)
template_substitution [14, 78] - [33, 78])
  identifier [16, 78] - [32, 78])

and for $value
template_substitution [14, 78] - [16, 78])
  identifier_dollar_escaped [15, 78] - [16, 78])

@akinsho the regex for identifier_dollar_escaped looks really suspicious. It works when you just use identifier but this would not consider that you can escape dollar characters.
        identifier: $ => /[a-zA-Z_$][\w$]*/,
        identifier_dollar_escaped: $ => /([a-zA-Z_]|(\\\$))([\w]\\\$)*/,

I'll experiment a bit with the regex.

Found a fix.
This would also work:         identifier_dollar_escaped: $ => seq(choice(/\$/, /[a-zA-Z_]/), repeat(choice(/\$/, /\w/))),


CF SDK: Set the SDK to call audio-only by default

Description
Please include a summary of the change and which issue is fixed.
Type of change

[x] Internal refactoring
[ ] Bug fix (bugfix - non-breaking)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Code snippets
In case of new feature or breaking changes, please include code snippets.

All the suggestions are related to the toURL which has been removed in this PR.
The reason is that the address:/public/room-1?channel=video is not a valid URL expected by the JS URL constructor: https://developer.mozilla.org/en-US/docs/Web/API/URL/URL
It is missing the host and the "address:" scheme is invalid.
Let me know if that looks okay, @jpsantosbh


Multiple Videos on one Page -> ngYoutubeEmbedService does not play both videos

Having an issue with multiple videos on a page, and with the ability to play the videos via the ngYoutubeEmbed service.
HTML:

             <ng-youtube-embed                  video="aboutIfThenVideoURL"                 videoid="aboutIfThen"                 width="595px"                 height="300px"                 autoplay="false"                 color="red"                 enablejsapi="true"                 disablekb="true">             </ng-youtube-embed>

                 <button class="btn btn-sm btn-default" ng-click="playAboutVideo()">Watch now!</button>

About IfThen: Overview

2:22

             <ng-youtube-embed                  video="captainInfoVideoURL"                 videoid="captainInfo"                 width="595px"                 height="300px"                 autoplay="false"                 color="red"                 enablejsapi="true"                 disablekb="true">             </ng-youtube-embed>

                 <button class="btn btn-sm btn-default" ng-click="playCaptainVideo()">Watch now!</button>

Captain Informational Video

3:47

Here is the js:
$scope.playAboutVideo = function() {
var player = ngYoutubeEmbedService.getPlayerById('aboutIfThen');
player.playVideo(); // Play video
};
$scope.playCaptainVideo = function() {
var player1 = ngYoutubeEmbedService.getPlayerById('captainInfo');
player1.playVideo(); // Play video
};
It appears that I am able to find both videos on both button clicks, however, it seems like only one video will play no matter what I try - when I try to play the second video, I get the following error:

TypeError: player.playVideo is not a function

Can you please let me know what I'm missing here? Thanks.

Hi, can you please provide a working example, like on codepen or jsfiddle.


Archive this un-maintained repo

Hello,
It looks like you stopped updating this repo. Instead of leaving it as is and exposing your users to bit-rot, you should archive it and point towards a fork which is being maintained (e.g: https://github.com/WhoIsSethDaniel/lualine-lsp-progress.nvim).

Another alternative: https://github.com/linrongbin16/lsp-progress.nvim


WASM file after wasm-gc still very large

Thanks! Can you gist the input files and what the expected size is?

I'm gonna close this for now, but if the big wasm file shows up I can help debug it!


decker: 1.39 -> 1.41

Description of changes

https://github.com/JohnEarnest/Decker/compare/v1.39..v1.41
035a6b0 is called out as a breaking change:

introduce a 'like' primitive to Lil, loosely mirroring SQL's glob-matching operator. Since this is a new keyword it is a minor breaking change, and there is some functional overlap with parse pattern matching, but overall I think this addition will make a wide range of common use-cases simpler and more straightforward.

Things done

Bumped version / updated hash

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

[x] Tested basic functionality of all binary files (usually in ./result/bin/)

24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

decker


Enable instrumentation for TagHelpers.

Removed old code that disabled instrumentation for TagHelper bodies. Instrumentation will throw out sections for begin/end context that don't make it to the final output.
Added instrumentation around WriteTagHelperAsync. Any content inside of the TagHelper will get sub-mapped via begin/end context.
Hand verified BasicTagHelpers.cs begin/end context tests to ensure correctness.

#172

/cc @pranavkm

:shipit:


Add Bundler support to make handling dependencies easier

Bundler makes dependency management easier. Now anyone can clone the repo, execute bundle and know they have exactly the same set of gems and gem versions as everyone else contributing.

Thank you! :sparkle:


Fixed syntax errors

Glancing over some of the questions, i noticed some weren't very clear because of the grammar. This should help at least a little. /shrug

thx


Missing device configuration:

Checklist

[X] It is not in the configuration DB

[X] It was not merged recently or has a pending PR

[X] The device was interviewed completely and has no missing or undefined IDs

Which device is missing?
Ezlo Thermostat
Manufacturer ID
0x025b
Product Type
0x8102
Product ID
0x5900
Firmware Version
1.12.0
Is the device listed on the Z-Wave Alliance website?
No response
Do you have a manual?
https://shop.ezlo.com/wp-content/uploads/Ezlo_Thermostat_Full_Manual_11052024.pdf

I'm working on a config file to contribute, but running into a couple of issues documenting some weird behavior.  I'd appreciate any advice at https://github.com/zwave-js/node-zwave-js/discussions/7508.


Add support for Crystal

Crystal, for those who don't know, is a statically typed and compiled language with a syntax very similar to Ruby. For dependencies it uses a file called shard.yml, the spec for which can be found here. Hopefully adding support won't be overly difficult.

Totally 👍 on adding Crystal support.

No need to close it. It's still relevant. 😉

Agreed. We need to get some more community support behind this though

👋 The Dependabot team is swamped scaling for GitHub at the moment, so it will, unfortunately, be a while before we can get to adding enhancements like this.  If someone wants to submit a PR adding support for this, we'll be happy to take review it as soon as we can.

I figured that would be the case. Hopefully someone looking for a project to help the Crystal community out will be willing to jump in and give it a go

I've setup a test repository with outdated dependencies in case you need something to test.
I created it for the corresponding renovatebot issue but dependabot folks naturally can work with it as well.

Any progress on this? I'd be happy to attempt to contribute!

Appreciate the offer @caspiano but we've currently put a pause on adding new ecosystems to dependabot-core as we beef up support for the current offering.

Bummer! Nonetheless, I can't wait 😊

It's been awhile since the beef up, if there's anything I can do to help out please do reach out :)

Hi there, still no news about Crystal support? :)

I have the feeling that it's more likely to have Renovate being able to handle Crystal.
But let's see :crossed_fingers:

In light of https://github.com/dependabot/dependabot-core/pull/8844, does that imply a PR would be accepted to support shards?


Should it be
 <PackageReference Include="Microsoft.Win32.Registry" Version="6.0.0" /> instead of <PackageReference Include="Microsoft.Win32.Registry" Version="5.0.0" />
Thanks.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 76bc889a-e3e1-65b3-f3c3-8597d30300db
Version Independent ID: d70af595-d281-da13-a5d9-e7a8f369c59d
Content: Upgrade Windows Forms apps to .NET 6 - .NET Core
Content Source: docs/core/porting/upgrade-assistant-winforms-framework.md
Product: dotnet-fundamentals
GitHub Login: @adegeo
Microsoft Alias: dotnetcontent

Hi @rajnishc8 the 6.0.0 package is still in preview, 5.0.0 is the latest: https://www.nuget.org/packages/Microsoft.Win32.Registry/5.0.0


Performance Improvement and possibility to add a start date to task

better performance if re-reading files:
When updating the TodoReview window only changed files are read newly - this makes the work flow very nice as you can change your todos and quickly update your TodoReview window even if you have thousands of files in your project

adding the possibiliy to specify a start date with @start(yyyy-mm-dd) in the TODO item
results will then be grouped into: (1) Now, (2) Important, (3) Someday and (4) Future by following rules

(1) Now: start-date of today or older
(2) Important: above defined priority - default < 80
(3) Someday: all items with below defined priority - default >= 80
(4) Future: start-date in the future
This gives a system similar to what is described by https://www.michaellinenberger.com/mywn-book.html
http://blog.clearcontext.com/WindowsLiveWriter/conveyorIdeal2.png

For people who may interest, I have my performance improvement on my fork too.

perf: great speed up by mergin regexes into one
perf: use set() to gain some speed up

For people who may interest, I have my performance improvement on my fork too.

perf: great speed up by merging regexes into one (this one results in a dramatic performance improvement)
perf: use set() to gain some speed up

If using set, seen_paths is not needed anymore I believe.


CI using GitHub Actions

Close #14
Close #24
Close #28 (as I removed Gemfile.lock, it doesn't make sense to have in a gem/plugin repo)

Ran here: https://github.com/dentarg/gem-compare-1/actions/runs/2605486453

@dentarg thanks a lot for your contributions!


Tabs are not clickable on iOS after click on active tab

Current behavior
When I click on currently active tab, all tabs are stopped to work. Nothing happens, when I click other tabs. But swipe is still working, for example. Only tab clicks stop working. And only on iOS device and iOS Simulator (android works fine).
Reproduction is superminimal – just fresh react-native with two dependencies and full code from example.
Also there is a video demo – https://github.com/chshanovskiy/tabview/blob/develop/tabview.gif
Expected behavior
Tabs are still clickable on iOS after click on active tab
Reproduction
https://github.com/chshanovskiy/tabview
Platform

[ ] Android
[X] iOS
[ ] Web
[ ] Windows
[ ] MacOS

Environment

package
version

react-native-tab-view
3.1.1

react-native-pager-view
5.4.11

react-native
0.67.3

node
16.13.1

yarn
1.22.17

same issue, when use react-native-pager-view v5.4.11.

@chshanovskiy Hi!
The reason for this problem is react-native-pager-view.
I fixed it, You can see PR https://github.com/callstack/react-native-pager-view/pull/527.
Or you could try my fork lib, yarn add git+https://github.com/alantoa/react-native-pager-view.

@alantoa looks great, I'll try it

The fix of @alantoa fixes this issue, but brings back an old issue that crashes the app after rapid switching. I have created another solution that solves this issue and also makes sure the app doesn't crash when doing rapid switching between the tabs. You can find it here:
https://github.com/callstack/react-native-pager-view/pull/529

@jixt You are right!
Ty!

https://github.com/callstack/react-native-pager-view/releases/tag/v5.4.12

https://github.com/callstack/react-native-pager-view/releases/tag/v5.4.12

Works great!


fix: split the lint job back out again

For some reason @ajaypratap003 merged the lint into the main build - this splits it back out again and adds the formatting checking back in

https://github.com/redhat-developer/app-services-ui/actions/runs/1577612168

LGTM


⚠ Site ANTS has degraded performance

In f1cb9eb, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 4435 ms

Resolved: Site ANTS performance has improved in 647c04f.


QuantityFhirValueProcessor fails with multiple measurment data

When multiple data inside the same measurment with a ValueQuantity FHIR mapping is proccessed, an exception is thrown.
QuantityFhirValueProcessor is assuming only a value is present. We would like to choose between some strategies (first, last or some aggregation).
https://github.com/microsoft/iomt-fhir/blob/4390667cc8e77216dc93e8b397efe5ed008911f4/src/lib/Microsoft.Health.Fhir.R4.Ingest/Template/QuantityFhirValueProcessor.cs#L15-L30

The failure is by design but spinning is not.  Spinning was addressed in this commit https://github.com/microsoft/iomt-fhir/commit/a134481872bd85894f01df6b88843312e6030109


First pass fixing lint errors.

Added pylint and cleaned up errors
Various other bits of tidy up, mostly driven by lint.
PTAL

The were errors from pylint not black.
I fixed manually... but it syntax highlights so once done I imagine it'll stay fixed.

Finished first pass. PTAL.
(Will add return types separately)


Add regularisers notebook

Add an example notebook showing the state of the art regularisers implemented in torchbearer

Closed by #602


Distinguish lists of arrays from tuples of arrays

Case in point: np.gradient, which changed from returning a list of arrays to a tuple of arrays in numpy 2.0, cf https://github.com/numpy/numpy/pull/26538

I'd like to give it a go. Any hints?
Should I create a new test file?
Maybe this strict iterable verification will create many errors in the libraries that depend on this

Would be great @luxedo !
The logic which does not tell a tuple of arrays from a list of arrays is here:
https://github.com/scipy/scipy_doctest/blob/main/scipy_doctest/impl.py#L329
Test cases could be added to tests/module_tests.py, see https://github.com/scipy/scipy_doctest/pull/157 for an example.

I feel that this is a little more complicated. How strict should the library be with iterables? I got some errors like the following testing SciPy's doctests:
343
344     Finally, the problem states that both decision variables must be integers:
345
346     >>> integrality = np.ones_like(c)
347
348     We solve the problem like:
349
350     >>> from scipy.optimize import milp
351     >>> res = milp(c=c, constraints=constraints, integrality=integrality)
352     >>> res.x
Expected:
    [2.0, 2.0]
Got:
    array([2., 2.])

This always worked and should keep working, I'd say.

Okay, so this check must be made exclusively when both Expected and Got are tuples and lists.
I added more tests and SciPy's tests now pass


How to pass attribute from live UX component into ux-autocomplete element

My live component looks like this

    {% set foundCount = this.count %}

        <form>

                Company
                <select id="ffCompanyId" class="form-control form-control-sm input"
                        data-receivables-target="companyId"
                        value="{{ companyId }}"
                        data-model="companyId"
                        data-live-ignore
                >
                </select>

                Purchaser
                <select id="ffPurchaser" class="form-control form-control-sm" data-item-company-id="{{ companyId }}"
                        data-receivables-target="purchaserId"
                        data-model="purchaserId"
                        value="{{ purchaserId }}"
                        data-live-ignore
                        {{ stimulus_controller('symfony/ux-autocomplete/autocomplete', {
                            url: path('flexi_partners_autocomplete', {companyId: companyId}),  <-- this attribute value i want to use in ajax call, but this only works, when constant is used {companyId: 1}
                            preload:'',
                            min_characters:3
                        }) }}
                >
                </select>

Excerpt from live component
    #[LiveProp(writable: true)]
    public ?string $companyId = null;
    #[LiveProp(writable: true)]
    public ?int $purchaserId = null;

And finally excerpt from  controller
   public function flexiAutocomplete(Request $request): JsonResponse
    {
        $searchString = $request->get('query');
        $companyId = $request->get('companyId');
        // call for result
        // but $companyId is null
        ...
        return new JsonResponse($results);
    }

Can somebody help me achieve this goal?
Thanks

I think you need to remove the data-live-ignore from the <select id="ffPurchaser". Basically, here is how you want the flow to work:
A) The component does the initial load.
B) The user changes the company from id 5 to id 8.
C) This causes the component to re-render, including the entire <select id="ffPurchaser", which will now render with a new url value passed into the symfony/ux-autocomplete/autocomplete controller.
Try this :). The result is, basically, that, when the component re-renders, the url data- attribute for the controller will update. That's perfect... except that I don't think the autocomplete controller is smart enough to SEE that and completely reinitialize what URL to use. If I'm correct, you'll see the DOM update with the new url data- attribute, but the autocomplete controller will still make AJAX requests to the previous URL. If that's true, try adding this to the <select id="ffPurchaser" element:
<select id="ffPurchaser" data-live-id="ffPurchase-{{ companyId }}" ...

This will give the element a unique data-live-id attribute for each company. The result is that when this changes from ffPurchase-5 to ffPurchase-8, that will signal to LiveComponents to completely remove the old element and add the new element (instead of just trying to update the existing element's HTML). And that should completely reinitialize the autocomplete controller.
Let me know how it goes :)

@weaverryan
it partially works, but autocomplete component duplicates on companyId change
It seems that original element is not removed on rerender

symfony/ux-autocomplete              v2.10.0

Any other idea?
Cheers

@weaverryan
After clearing caches, yarn --force it's working now.  Hope this is not only some temporary phenomenon.
So thanks for clear guidance

@weaverryan
Premature joy (: Autocomplete is not visible as duplicated, but DOM node for autocomplete component is. On companyId change, new AC element is inserted, whereas old one is not removed.
Where can be cause?  symfony/ux-live-component, symfony/ux-autocomplete ?? Where could I search for...


Hitting the mount button continuously doesn't work for me.

I've tried this many times.

i anything being done to fix this?

Yes, The author of the program (yoichiro) is working with Google to
find out what may have occurred with a ChromeOS update to cause the
problem.
-------Original Message-------
From: marshameine<EMAIL_ADDRESS>To: yoichiro/chromeos-filesystem-dropbox
<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [yoichiro/chromeos-filesystem-dropbox] Hitting the mount
button continuously doesn't work for me. (#122)
Sent: Feb 05 '20 8:47pm
i anything being done to fix this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Im having the same issue with this - is there any update on it?

-------Original Message-------
From: andychambers30<EMAIL_ADDRESS>To: yoichiro/chromeos-filesystem-dropbox
<EMAIL_ADDRESS>Cc: Robert Cowan<EMAIL_ADDRESS>Comment
<EMAIL_ADDRESS>Subject: Re: [yoichiro/chromeos-filesystem-dropbox] Hitting the mount
button continuously doesn't work for me. (#122)
Sent: Feb 12 '20 4:27am
Im having the same issue with this - is there any update on it?
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yoichiro, Is a solution on the way? It worked so well before these
issues...
Thanks!
Robert
-------Original Message-------
From: andychambers30<EMAIL_ADDRESS>To: yoichiro/chromeos-filesystem-dropbox
<EMAIL_ADDRESS>Cc: Robert Cowan<EMAIL_ADDRESS>Comment
<EMAIL_ADDRESS>Subject: Re: [yoichiro/chromeos-filesystem-dropbox] Hitting the mount
button continuously doesn't work for me. (#122)
Sent: Feb 12 '20 4:27am
Im having the same issue with this - is there any update on it?
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Duplicated issue: #120


Handle upcast and downcast of JSON Schemas with multiple types

In OpenAPI 3.1, JSON Schema can have a type that is an array.

If the array has only one value that is not null, treat as if the type was just a string
If the array has only one value that is null, in v3/v2 emit as nullable/x-nullable and emit no type
If the array has two values where one is null, then in v3/v2 emit as nullable/x-nullable and convert type to string of other value.
If the array has two values where neither is null, or more than two values, then in v3/v2 do not emit the type field.  By omitting the type field we keep the schema from creating false negatives and it is more likely that downstream tooling will flag the issue.

Remove Nullable and represent it as a member of the type array