Entity Shadows

For #2594
Continuation of https://github.com/AnalyticalGraphicsInc/cesium/pull/3928 now that the shadows branch is gone.

I added castShadows and receiveShadows properties to all the applicable entity types. It supports changing these properties at runtime. Batching based on shadows is handled in GeometryVisualizer. Each batch, besides the dynamic batch, is now an array of 4 batches (cast+receive, cast, receive, none). This was the cleanest solution for now, but could get unwieldy if we continue to add more bucket types. I tried and gave up on a unified solution for batching so that we wouldn't need StaticOutlineGeometryBatch, StaticGeometryColorBatch, and in StaticGeometryPerMaterialBatch. Maybe this is worth revisiting in a future rewrite.

We talked about potentially using just shadows instead of castShadows and receiveShadows.

[x] Deprecate castShadows and receiveShadows
[x] Performance testing

Entities now have a single shadows property. I am seeing some problems with the checkered entity in the Sandcastle demo, but otherwise this is ready for review.

We talked about potentially using just shadows instead of castShadows and receiveShadows.

I am all for less code in the higher-level layers, but are we sure about this?  If so, why didn't we just do this in the Primitive API?
Separate cast/receive are standard and support all use cases.
The other option is to make this an enum.

Yeah, we talked offline and Dan mentioned some use cases where you would want both.  An enum definitely sounds like the right call (perhaps that should have been done at the Primitive layer as well?)

perhaps that should have been done at the Primitive layer as well?

It will be easy to deprecate if we go this route.

Given the uncertainty about the properties in this PR I am going to omit the CZML model shadow property merged with #3856 until we have an API that won't change.

An enum doesn't really seem intuitive from the user's perspective.
I'm ok with reverting back to castShadows and receiveShadows.

An enum doesn't really seem intuitive from the user's perspective.

Why not, it makes the most sense to me and is what we do elsewhere in Cesium.  How is this different?

It just seems overly complicated for the entity api, remembering the enum names is harder than just setting some booleans.

They would not be names, we would have a new enum type.  We already do this everywhere else in the Entity API (HorizontalOrigin, VerticalOrigin, etc..) no one has ever complained.

I am fine with the enum or without it I suppose; it just seems like a lot more plumbing without it.
I agree the enum names are a bit awkward, but could be simple enough:
ENABLED
DISABLED // same as being undefined
CAST_ONLY
RECEIVE_ONLY

@lilleyse perhaps see what is most common in game engines.

Ok, I'll go with the enum approach. Hopefully today or tomorrow I'll have time to get this ready before the release.

@lilleyse I see you pushed three new commits.  Is this ready or should it wait until 1.24?

This is ready for review at least. I'm still seeing issues with the checkered box though which I hope to fix soon.

Let's finish this for 1.24 since 1.23 is on Friday.

This is ready for review, though the Sandcastle demo may crash in certain cases until https://github.com/AnalyticalGraphicsInc/cesium/pull/4099 is merged.

Given the uncertainty about the properties in this PR I am going to omit the CZML model shadow property merged with #3856 until we have an API that won't change.

@shunter Are there any additional czml changes that I need to make besides what's already here?

This is ready for review, though the Sandcastle demo may crash in certain cases until #4099 is merged.

It should be fine to merge that into this branch.

@lilleyse there are test failures in CI - https://travis-ci.org/AnalyticalGraphicsInc/cesium/builds/143447829

@mramato did you want to review this before merging?

Yes, I plan on reviewing/merging a bunch of Cesium stuff later today.

Can we generate some performance numbers that compares both load time of vienna.geojson and memory usage after load with master"?  It doesn't have to be super rigorous, but the Entity visualization architecture is already long overdue for an overhaul and I just want to make sure we didn't make things substantially worse here.

Sure I can do that.

What is the plan here?  Will this make 1.24 on Monday?

Would it be possible to squeeze this into the release, or should we just wait for the next? The last major change is to add back the castShadows and releaseShadows for certain types just for deprecation purposes.

You would have to code this now, right?  If so, let's not hold up the release (but go ahead and still make the change now so we can get it into master early for the 1.25 release).

Ok

@mramato where can I find vienna.geojson?

In terms of performance:

The load time is roughly the same, about 7 seconds each (I didn't get super accurate, just used a stopwatch).
The memory difference is around 12MB (the Chrome process used 742MB then 754MB). This is hard to get an accurate reading for by the time you change branches, rebuild, etc, but 12MB was the biggest difference I saw.

I added back the deprecated properties and updated CHANGES.md. This is ready for a look now.

@mramato please merge when ready.

Merge in master and this is ready.  Thanks @lilleyse!

In terms of performance:

Thanks, I think if there were any major issues, they would have been obvious.

Did anything change lately with trackedEntity? After merging the view starts out pretty far away in the Shadows demo:

This is also noticeable in the 3D Models demo. @tfili the commit is https://github.com/AnalyticalGraphicsInc/cesium/commit/934828e1d74e3383f9925c39fb9cf9c35822781e when something changed.
The correct start view changed to the one below:

No that I know of, but I can take a quick look.  Does this happen in master?

Yeah it's also in master.

Yeah it's also in master.

OK, then I'll merge this and we can look at this later.  Can you write up a separate issue so that we don't forget?  Thanks!

OK, then I'll merge this and we can look at this later. Can you write up a separate issue so that we don't forget? Thanks!

Sure


Bat theme not working

When trying to use bat to preview a file, for instance, the bat theme generated by stylix appears to error, falling back to its default theme:
~/.config/bat
$ bat themes/base16-stylix.tmTheme
[bat warning]: Unknown theme 'base16-stylix', using default.

Is this still an issue for you? fish autocompletes bat --theme base16-stylix for me. base16 also works.

Can't test right now, gonna have to spin up a vm.

This was a bug in home-manager that I fixed a while ago: https://github.com/nix-community/home-manager/pull/3886

Oh yes, I forgot this was open, still. Closing as solved.


Twilio numeric fields cast as strings

          @raphaelvarieras that is a good callout, but would you mind creating a new issue for that? I'd prefer to tackle in it another release to ensure we have ample time to figure out each field we'd want to (and logically should) cast as an integer, as I see that other tables have quite a few numeric fields cast as strings (ex: `duration` and `price` in `CALL` and `count` and `usage` in `USAGE_RECORD`)

Originally posted by @fivetran-jamie in https://github.com/fivetran/dbt_twilio_source/issues/6#issuecomment-2108454742

thank you 🙌

so, we need to investigate the following tables' fields, which are coming in from the connector as varchars/strings but sound (and look) like they should be numeric types:

message:

num_segments
num_media
price

call:

duration
price
queue_time

usage_record:

count
price
usage

i'll talk to the data PMs to understand why this might be the case from the connector-side of things, but otherwise this would be straightforward to implement ion the package. in the final CTE of each staging model we'd wanna cast each of these fields as a {{ dbt.type_int() }} or {{ dbt.type_numeric() }} or float or whatever is most appropriate for the field

I already got some answers from Fivetran support. Apparently this is because the specifications provided by Twilio for their API is that these are provided as strings. So it seems maybe there are circumstances under which the API might return non-numeric answers?? I'm just not sure that is enough of a reason to compromise the ease with which to perform analysis using these models. I imagine many will need to add a casting operator in their project if it's not part of this package.

Yeah I do see that Twiliio lists these fields as strings in the API Docs, but I completely agree with you that the fields are really only valuable as actual numerics. Going to investigate some more and will report back 🫡

@raphaelvarieras We're currently trying to get in contact with Twilio to get some clarification on these fields, but it could be helpful for you to open a case with Twilio directly as well, as they might prioritize getting to customer questions over partner ones.

So finally got some answers (somewhat) from Twilio:

GENERAL ADVICE ON TREATING STRING FIELDS AS NUMBERS
When dealing with API responses, it's common to encounter fields that are represented as strings but contain numerical data. This often happens for several reasons, including but not limited to:
Ensuring precision for very large numbers that might exceed the limits of numerical types in some programming languages.
Maintaining compatibility across different systems where the interpretation of numerical types might vary.

With this, I think the package can safely apply the below updates in the relevant staging models:

Scrub out non-numeric characters (it doesn't sound like there will typically be any but just in case)
Cast each of the fields as {{ dbt.type_numeric() }}

@raphaelvarieras We'll plan ot take this on next sprint, which starts 6/13, but if you have availability to open a PR we will happily review and merge before then!

Thanks @fivetran-jamie and @raphaelvarieras  for the context and scoping, will start working on an update to the package

Thanks @raphaelvarieras! This has been addressed in our latest release.


Adding new dependency logging

#185

I signed it!

Ok doing so has increased speed drastically. Though the way Ive written it not sure it needs to be a closure.

My reasoning behind making it a closure was reuse - there are a couple more places from which it needs to be called. Right now, only the part of the code dealing with direct dependencies is instrumented. Look down in the dft closure - that's the depth-first explorer which transitively visits all dependencies. Everything discovered through there needs to be treated, as well.

Im still analyzing the code to make sure the new goroutine to call the closure always has a chance to complete.

They're all guaranteed to complete and print, but not by anything directly visible in the code here. All of those SyncSourceFor() calls are blocked on actions that are necessarily also called elsewhere (either in Solve(), or in a blocking manner by the txn writer); they'll complete and print as soon as the other calls do.
This approach doesn't guarantee we'll see everything printed - for example, transitive deps of deps that aren't in GOPATH won't ever get visited, so a printing goroutine will never be run for them. But I'm not even sure that's really solvable, so this is still a substantial improvement over what we have today.

@sdboyer Is there anything else needed here for this issue to close?

@xmattstrongx i think some feedback from @peterbourgon would be useful, as it was his note that motivated putting this up in the first place. i'm adding him as a reviewer.

@peterbourgon We decided to make each call happen in a new goroutine because the underlying call to gps.SourceMgr.SyncSourceFor was eating up about 1.5-1.8 seconds each.
As far as the output verbage @sdboyer and I went back and forth a couple times on what it should display. I do like the Cached dep

ditto what @xmattstrongx said re: separate goroutines.

What about just "Fetched dep" or "Cached dep"?

Ooh yeah, I liked "Cached dep" even more. I was trying to come up with something to avoid saying "cloned," as that's git/hg-specific, and also isn't the action it's performing if the dep is already present in the cache. So, definitely, this is better.

@xmattstrongx Thanks for the explanation. Is SyncSourceFor the bit that's actually doing the work of init?

per a previous slack conversation with @sdboyer

this'll (SyncSourceFor) all be reused by the solver or exporter when it comes time to do their job, so there's no duplication of work happening

I'm sorry, that doesn't answer my question.

@peterbourgon I guess that depends on what "the work of init" means? I'm not sure what you're asking by that.
SyncSourceFor just brings the local cached instance of a source's repository up to date (or clones/checks it out initially). We're choosing to target it as the operation to report because it's intuitive and also the one that tends to be expensive, and so is the most likely to give user incremental and comprehensible feedback.
The same action is performed implicitly by both solving and exporting the dep tree to vendor. We're just promoting that action to happen out here, so that we can effectively signal when it's complete. When it happens implicitly, from within either of those two calls, there's signaling mechanism to let us know when that operation is complete.

OK. Calling the closure printNewDep belies its importance; it's doing more than just printing! I suggest syncDep.

Single Responsibility... makes sense to me. Gonna make the change to the function name to syncDep and output to read

Cached dep

OK, I think we're good to merge this now. Thanks!


keylime is setting owner auth

Is your an issue a feature request? If so, please raise it as an enhancement
Environment

OS / version: RHEL
Processor architecture: x86
TPM Manufacturer: N/A
Keylime version: master

Description
This has a dependency on #684.  keylime is setting owner auth.  In general, owner auth is set in a pre-OS menu, so this process will fail.  Some Linux applications require it to be empty, so keylime will break those applications.
Owner auth is needed in keylime (apparently) only for the evictcontrol to persist the EK.  Issue #684 suggests that the EK should not be persisted.  If that dependency is removed, perhaps keylime can avoid trying to set owner auth.
Expected behavior vs. actual behavior
Expect keylime to not change owner auth.
Steps to reproduce problem
Relevant logs
Attach any relevant log files that can help to debug your issue.

I think we will not change this for the Python agent. The Rust does not persist the EK and does not set the owner auth.
@mpeters any other opinion?

Agreed.


Refs #26796 -- Fixed ManyToManyField's limit_choices_to warning without a through model.

https://code.djangoproject.com/ticket/26796
per discussion https://github.com/django/django/commit/ba53da894fc713629ae4d3fbdd14eff98c808389#commitcomment-18263905

buildbot, add to whitelist.

merged in 17a0a6667c3f77908f9427f6489e298c828133e2, thanks!


sharing: bring back sharing via studio api

Thanks for all the great work on #3574 and #3781 to consolidate the sharing actions and make them all rely on dvc exp push, but I may have pushed it too far 😬 . Maybe it makes sense to keep two sharing actions like:

Push to share full experiment (dvc exp push)
Share metrics/experiment summary (studio api)

Reasons:

Pushing the full experiment takes too long when pushing to the dvc remote and isn't always needed. We could have another option to push only the Git ref, but what's the benefit over the lighter studio api?
Live sharing from anywhere. Now, you can only use live sharing in the extension if you have pipelines and run experiments through the extension. Since the extension collects all the info for each experiment as it runs, it could auto-share experiments run from notebooks or elsewhere outside the extension.
Sharing any experiment anytime. Now, you can only share via the studio api by checking a box globally before running experiments. Again, since the extension already collects all the needed info, users could choose individual experiments and choose to share before, during, or after it runs.

@mattseddon @shcheklein @daavoo Would be great to hear your thoughts (and others).

Pushing the full experiment takes too long when pushing to the dvc remote and isn't always needed. We could have another option to push only the Git ref, but what's the benefit over the lighter studio API?

The benefit is that the Git remote isn't out of sync with Studio. We could bring the --no-cache option in but I think we should avoid that because we are trying to help users with reproducibility (the same reason Thoughtworks moved DVC to adopt). Information (data) that is only available locally for one team member does not make an experiment reproducible for the team.

Live sharing from anywhere. Now, you can only use live sharing in the extension if you have pipelines and run experiments through the extension. Since the extension collects all the info for each experiment as it runs, it could auto-share experiments run from notebooks or elsewhere outside the extension.

Is this really needed? Is the hypothesis that users will come with a notebook and try to connect to Studio straight away? I would assume that it is more likely they would investigate that route after they've graduated to pipelines and don't we want to nudge users in that direction?

Sharing any experiment anytime. Now, you can only share via the studio api by checking a box globally before running experiments. Again, since the extension already collects all the needed info, users could choose individual experiments and choose to share before, during, or after it runs.

I think this will cause the same issues as the first point but if it is important why wouldn't this be available via the CLI?
I also think that we need to take into account the cognitive load that we'll be adding to the UX. They will have to juggle which option to use and when, whether or not they need to later update a "partially shared" experiment. How to tell whether or not an experiment is partially shared.
Maybe we will need to implement this functionality in the future but I do not think we should rush into throwing the kitchen sink at the experience until we get some user feedback.

(just to explore this a bit and brainstorm)

but what's the benefit over the lighter studio api?

I think to have at least one type of workflow. Having two types of experiments in Studio is also not very good to be honest. It will be hard to explain to users I'm afraid.

Live sharing from anywhere.

Like sharing even from a different language (not Python) as an extreme example? Sounds like a good scenario, doesn't feel like a major item to me to prioritize now. Or do you mean even sharing things that are not even DVCLive instrumented?

to share before

what does it mean? could you clarify please?

@mattseddon

The benefit is that the Git remote isn't out of sync with Studio. We could bring the --no-cache option in but I think we should avoid that because we are trying to help users with reproducibility (the same reason Thoughtworks moved DVC to adopt). Information (data) that is only available locally for one team member does not make an experiment reproducible for the team.

Agreed, but IMO that's how we differentiate -- studio api for typical experiment tracking/visibility, exp push for full experiment sharing/reproducibility.

Is this really needed? Is the hypothesis that users will come with a notebook and try to connect to Studio straight away? I would assume that it is more likely they would investigate that route after they've graduated to pipelines and don't we want to nudge users in that direction?

We have increasing evidence that users are happy to use dvc experiment tracking from notebooks and pipelines aren't always a next step. We even have users who already have pipelines say they want to use the dvclive experiments for when they do more lightweight exploration.

I think this will cause the same issues as the first point but if it is important why wouldn't this be available via the CLI?

It probably should be, but it just feels like a better workflow in VS Code, so I decided to start here. It's harder for me to imagine how to do this from the CLI, but open to ideas.

@shcheklein

I think to have at least one type of workflow. Having two types of experiments in Studio is also not very good to be honest. It will be hard to explain to users I'm afraid.

👍 Need to keep thinking about this. My worry is that the studio api, which IMO is more obvious/intuitive/expected way to share, feels more hidden and less flexible. Exp push is more powerful and unique to us but has a steeper learning curve, more setup/moving pieces, and is slower.

Like sharing even from a different language (not Python) as an extreme example? Sounds like a good scenario, doesn't feel like a major item to me to prioritize now. Or do you mean even sharing things that are not even DVCLive instrumented?

I mostly mean from notebooks or python scripts without pipelines. Agree those others don't feel like major priorities to me. This issue partly came from setting up live sharing in a notebook and realizing how awkward it is in the extension (I already saved my token, but now I have to get it again and manually set an env var in my notebook).

to share before

what does it mean? could you clarify please?

I partly wrote that just because it sounded good, but I think it sort of makes sense 😄. For a queued experiment, we could mark ahead of time that we want to share it and then it would be shared once it starts.

My worry is that the studio api, which IMO is more obvious/intuitive/expected way to share, feels more hidden and less flexible. Exp push is more powerful and unique to us but has a steeper learning curve, more setup/moving pieces, and is slower.

I feel like I am missing the reasons behind the descriptions of each option.
IMO, studio API for completed experiments could/should be replaced by exp push --no-cache in a totally transparent way for users. How would people notice that we are pushing a git ref vs a POST request.
The reason we don't currently follow this approach is that, during the early implementations of live experiments, there was a pushback against adding support for git refs in Studio (as it was not prioritized at that time and Studio backend estimated that it would introduce significant overhead).


Add a suggested Books for DSA webpage under More on nav bar

Is your feature request related to a problem? Please describe.
Along with tons of online material, learners often search for list of books on to get a clearer idea of DSA

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A specified page designated for a list of books.

A clear and concise description of what you want to happen.
Add a link to another webpage which will include list of suggested books and on hovering over each item on the list, we can add a few lines on how that particular book can help. The webpage will require a very simplistic design, just using HTML CSS containing list of books, I have 3 books in mind right now.

YOU CAN WORK ON IT @sohini3062


Python: simple implementation of token usage

Motivation and Context

Added token usage tracking to the OpenAI classes, similar to how that is done in dotnet.
Similar approach as #2526 but for Python
TODO: add a similar construct to python for the SKContext.LastResult.
Description

Added three fields to the OpenAI Chat and Text completion classes.
After doing a call, check if 'usage" is in the response and then update the fields, can be read through properties.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Created a new issue to track future work for this to extend the functionality to other ai services https://github.com/microsoft/semantic-kernel/issues/2858

@shawncal @alexchaomander could you approve again?

@awharrison-28 can you start the integration tests again, I think it is now solved


Screenshots and notes of prominent similar games UI

In order to compare different UI, add screenshots with notes of goods and bads

Games:

Duskers


Append type hinting to the class

Following this discussion I finally realized what I had in mind, even though I have to admit it might not work exactly in the way I wish it would.
For this class:
from dataclasses import dataclass
from typing import Annotated

@dataclass
class Pizza:
    price: Annotated[float, "money"]
    size: Annotated[float, "dimension"]

    @dataclass
    class Topping:
        sauce: Annotated[str, "matter"]

I get the following behaviour:
from uniton.converter.append_types

append_types(Pizza)

print(Pizza)
print(Pizza.Topping)
print(Pizza.size)
print(Pizza.price)
print(Pizza.Topping.sauce)

Output:
<class '__main__.Pizza'>
<class '__main__.Pizza.Topping'>
typing.Annotated[float, 'dimension']
typing.Annotated[float, 'money']
typing.Annotated[str, 'matter']

The only one problem is that the default value is lost when there is one and it's accessed without instantiating the class, i.e.
@dataclass
class Pizza:
    size: Annotated[float, "dimension"] = 10

print(Pizza.size)
append_types(Pizza)
print(Pizza.size)

Output:
10
typing.Annotated[float, 'dimension']

But it doesn't really interfere with any functionality if it's instantiated. This being said, I would have loved to do it without overwriting the class, but I couldn't find any viable solution other than this one.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

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

Files with Coverage Reduction
New Missed Lines
%

converter.py
2
93.55%

Totals

Change from base Build<PHONE_NUMBER>4:
-2.3%

Covered Lines:
70

Relevant Lines:
74

💛  - Coveralls


Hope minisnip add selection region

this plugin  https://github.com/mbbill/code_complete is good and tiny, But not good for building our language snip libs and not update now.
Maybe minisnip can borrow its advantages

https://github.com/Jorengarenar/miniSnip/pull/35
Like it!

https://github.com/Jorengarenar/miniSnip/pull/37
Add selection region now :)

Please, update the issue with proper description - few paragraphs, not few words

I'm a newbie T. T
I can only look forward to the author's update
Hope minisnip will be better in the future .


The link is too fat, you can create a slimmer one

The link is too fat, you can create a slimmer one

Similar to the following

这款可以满足需求吗？
https://remixicon.com/icon/link


Getting inverted question mark crashes in Send tab

Traceback (most recent call last):
File "morse_trainer/morse_trainer.py", line 295, in send_thread_finished
File "morse_trainer/utils.py", line 149, in char2morse
KeyError: '¿'
Need to handle return char from thread differently.

Made attempt to fix the problem, but now Send display is getting out of whack, with error tooltips not correct.  That is, expected char and received char wrong, but displayed chars not in same column and error tooltip located on expected char (top row).

Closed by returning (char, morse) from read_morse.read() method.  Different handling in morse_trainer.py.


Auth bastion

This PR adds a mode for bloop to work as a Github App installation that's limited in scope to a single organization.
The base assumption is that the only entity that controls the Github App keys is the auth bastion server (auth_server_url command line/config option), while only the bloop instances hold the users' OAuth keys.
This PR holds an initial bloop client implementation that talks to an emergent auth bastion specification (TBD).
Current status:

the main addition is webserver/aaa.rs to hold AAA-related functionality
there are lot of corner cases not covered here, I tried to document these in the code as I went
wiring up bloop to an auth bastion should work, and syncing repos should be possible (not tested, though)
users should be able to sign up with the correct Github App setup, and an auth bastion
token issuance
key rotation, check for expiry, upstream revokation

Not implemented

setting up a root admin user (should send a /private/hello to the auth bastion to see who asked for the deployment?)
persistence of user oauth keys (this forces users to re-login every time we restart the service)
there are a few DoS opportunities
error handling, nice HTTP responses
TODO comments in the PR code, todo!() macros
the auth bastion server itself

As noted in #115, this PR has been superseded. The new PR rebased all commits here against master, and added additional work to adjust the implementation strategy as discussed offline. Closing this for now, we can reference this for fine-grained authentication in a future PR.

@calyptobai we're better off implementing the changed deployment model here, we should continue with this branch.


Component scheduler

Created a new PR so that we can discuss the component.
I'm thinking maybe each event listener should have a state card? So that we can show the next time the event is scheduled.

We can add a new api call now that the http component is split up.
I am currently working on restructuring the Home Assistant interface so
that we can have  multiple screens, one for states, history and scheduling.
On Mon, Feb 2, 2015, 00:52 Gustav Ahlberg<EMAIL_ADDRESS>wrote:

Created a new PR so that we can discuss the component.
I'm thinking maybe each event listener should have a state card? So that
we can show the next time the event is scheduled.
You can view, comment on, or merge this pull request online at:
https://github.com/balloob/home-assistant/pull/25
Commit Summary

Refactered event listeners so that they can be part of a component
instead of having to be stand alone components
Make sure that components isn't loaded multiple times
fixed flake8 E302 expected 2 blank lines, found 1

File Changes

M homeassistant/components/scheduler/init.py
https://github.com/balloob/home-assistant/pull/25/files#diff-0 (34)
D homeassistant/components/scheduler/sun.py
https://github.com/balloob/home-assistant/pull/25/files#diff-1 (114)
M homeassistant/components/scheduler/time.py
https://github.com/balloob/home-assistant/pull/25/files#diff-2 (2)
M homeassistant/components/sun.py
https://github.com/balloob/home-assistant/pull/25/files#diff-3 (111)

Patch Links:

https://github.com/balloob/home-assistant/pull/25.patch
https://github.com/balloob/home-assistant/pull/25.diff

—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/pull/25.

that sounds like a great solution!

Should we try to merge this and update the component when the multiple screens are done? Or should we wait until we can add everything?

Let's merge it.
On Tue, Feb 3, 2015, 00:10 Gustav Ahlberg<EMAIL_ADDRESS>wrote:

Should we try to merge this and update the component when the multiple
screens are done? Or should we wait until we can add everything?
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/pull/25#issuecomment-72610148.

Great, I'll try to fix the errors after work today.
On Tue Feb 03 2015 at 9:29:01 AM Paulus Schoutsen<EMAIL_ADDRESS>wrote:

Let's merge it.
On Tue, Feb 3, 2015, 00:10 Gustav Ahlberg<EMAIL_ADDRESS>wrote:

Should we try to merge this and update the component when the multiple
screens are done? Or should we wait until we can add everything?
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/pull/25#issuecomment-72610148.

—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/pull/25#issuecomment-72611998.

Coverage increased (+0.7%) to 56.32% when pulling 39485e75838659c6cff3675d975d13828bbea9d7 on component-scheduler into fbae2ef7254411252a9f177e5af82b211b4fc513 on dev.

Looks good :+1:


In iOS13 cannot normal show

In iOS13, it only show once and will be impact status bar

@zx1262111739 I have the same issue. How do you fix it?

No fix, myself custom one

@zx1262111739 Could you please reopen this issue or maybe you can create a new pull request based on your solution?

@zx1262111739 Could you please reopen this issue or maybe you can create a new pull request based on your solution?

I just simple create one can show text widget

@zx1262111739 thanks.

@zx1262111739 @derekcoder
Sorry for my late reply.
Please try ios-13 branch!

@krimpedance Got it. Thanks for your reply.

not working with Xcode 11 GM Seed :( @krimpedance

@ahmedsafadii
Sorry, use 3.4.2.


Unable to get real-time html working on subdomain with Ghost

Hi there,
I'm running Ghost on Ubuntu 20.04 with Digital Ocean's doplet and NGINX. I installed GoAccess with success and I'm able to launch it with the command
goaccess access.log --log-format=COMBINED
However, I'm unable to get real-time html working while generating it with
goaccess access.log -o report.html --log-format=COMBINED
and move it to /var/www/html/ then parses the access log and displays the stats in a real-time HTML report with
goaccess access.log -o /var/www/html/report.html --log-format=COMBINED --real-time-html
I'm using HTTPS so I'm wondering if I should add anything else?

Am I supposed to put the html file anywhere else than /var/www/html/ ? I'm a bit confused so your help will be much appreciated :) I love the concept tho, thanks for this amazing work!

Hello. Not familiar with ghost but it seems like you can run:
# ghost ls

It should output where your site lives. As far as https, you will need to pass  --ssl-key=<path/priv.key>  and --ssl-cert=<path/cert.crt>.
Please let me know if that helps.

If you’re running goaccess on the same server, I’d reuse your site existing certificate and key and pass those paths to goaccess. If you’re running nginx, take a look at your site’s config file.

If you’re running goaccess on the same server, I’d reuse your site existing certificate and key and pass those paths to goaccess. If you’re running nginx, take a look at your site’s config file.

I checked on NGINX and the ssl info are located

Hi there!
Is anyone knows how to solve this issue? I'm still blocked :(
Thanks!

It does not recognize the ssl option
goaccess: unrecognized option '--ssl-key=/etc/letsencrypt/blog.arfy.ca/blog.arfy.ca.key

Please make sure to build using --with-openssl

Closing this. Feel free to reopen it if needed.


Could not find specification for target "xtensa-esp32-espidf"

I followed the instructions in the README file, but I get this:
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --target xtensa-esp32-espidf --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit code: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "xtensa-esp32-espidf". Run `rustc --print target-list` for a list of built-in targets

I believe that this is related to the fact that rustup toolchain show does not list an esp toolchain:
$ rustup toolchain list
stable-x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-msvc (default)

I did follow the directions on how to install this toolchain, and indeed the toolchain zipfile did get extracted to the correct place:
$ ls C:\Users\me\.rustup\toolchains\

    Directory: C:\Users\me\.rustup\toolchains

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----           9/15/2021 12:26 PM                esp
d----            5/5/2021  8:28 AM                stable-x86_64-pc-windows-msvc
-a---          10/13/2021  5:41 PM      105402674 rust-1.55.0-dev-x86_64-pc-windows-msvc.zip

However, that directory being there is not enough to cause rustup default esp to succeed:
$ rustup default esp
error: toolchain 'esp' is not installed

@georgik I followed those exact instructions, with the same result:
$ cargo +esp build
error: toolchain 'esp' is not installed

@georgik yes, just Windows Defender. I think the problem here is that simply extracting the files doesn't lead rustup to believe that the toolchain is "installed". For example, in install-rust-toolchain.sh, we have the line:
./${RUST_DIST}/install.sh --destdir=${TOOLCHAIN_DESTINATION_DIR} --prefix="" --without=rust-docs

... and there is no equivalent line in Install-RustToolchain.ps1. I assume that whatever install.sh is doing is "registering" the toolchain with rustup?

@godefroi Interesting. It seems that some kind of setup is leaking from previous installation. I've already noticed it with cargo and older version of toolchainn.
May I ask you just try to rename or delete  ~/.cargo and ~/.rustup.
Then download latest version of the install PowerShell script and run it. I've added speed up of download to the latest version.

By the way  the esp-idf windows setup has an option to install the experimental rust support. I think my esp toolchain came from there even though I might have later run that ps1 script from repo above.

@godefroi Thank you for the log information. I see what might be the problem.
Right now the installation script assumes that rustup is installed in user's home. You're probably using different location.
What's the output of (Get-Command rustup).path ?
@pekkah Yep, I'm working on this feature in the idf-installer. Basically the PS1 script is right now the more advanced version of installation script. I plan to add some corrections to the Rust installer.

As a suggestion it might be an idea to add a file to the root of the project called rust-toolchain.toml
with the following in
[toolchain]
channel = "esp"

For others to install the toolchain under windows one idea would be to look here

https://github.com/esp-rs/rust-build/releases/tag/v<IP_ADDRESS>
https://github.com/esp-rs/rust-build/releases/download/v<IP_ADDRESS>/rust-<IP_ADDRESS>-x86_64-pc-windows-msvc.zip

extract the zip then use
rustup toolchain link esp <extractedpath>

To register the toolchain as "esp" in the list of available toolchains

I'm not sure - is this fixed now, or is there a workaround? @godefroi ?

I haven't been working on this recently, sorry. I didn't find a workaround, and I'm out of town for some time.

Closing this as there is no activity on this topic, and hopefully the issue is resolved in the latest Espressif Rust 1.58 build. If it is not, please reopen the issue here: https://github.com/esp-rs/rust-build

I had the same error, but on linux (Ubuntu 23.04).  Installed w/:

sudo apt install -y git curl gcc clang ninja-build cmake libudev-dev unzip xz-utils python3 python3-pip python3-venv libusb-1.0-0 libssl-dev pkg-config
sudo snap install rustup --classic
rustup install stable
cargo install espup
espup install
. $HOME/export-esp.sh

Version: rustup 1.24.3 (ce5817a94 2021-05-31)
$ cargo build
error: failed to run 'rustc' to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/derek/snap/rustup/common/rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --target xtensa-esp32-espidf --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "xtensa-esp32-espidf". Run `rustc --print target-list` for a list of built-in targets

$ rustup default esp
error: toolchain 'esp' is not installed
$ rustup toolchain list
stable-x86_64-unknown-linux-gnu (default)
nightly-x86_64-unknown-linux-gnu

~/.rustup/toolchains/esp exists, so ran: rustup toolchain link esp ~/.rustup/toolchains/esp
This worked.  Ex:
~/projects/rust-esp32-std-demo$ cargo build
   [...]
    Finished dev [optimized + debuginfo] target(s) in 3m 42s

Did anyone have this issue on MacOS (Sonoma 14.4.1)? I have esp in my toolchains however cannot get it to work, tried runnig above command and get the error that the toolchain is not installable. Don't really know how to proceed here.


Feature/log

Codecov Report

Merging #6 (8f28e1e) into main (2115d25) will increase coverage by 1.10%.
The diff coverage is 97.19%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   93.85%   94.96%   +1.10%
==========================================
  Files          13       15       +2
  Lines         456      656     +200
==========================================
+ Hits          428      623     +195
- Misses         19       24       +5
  Partials        9        9

Impacted Files
Coverage Δ

mizugo/logs/zap.go
96.70% <96.70%> (ø)

mizugo/logs/define.go
100.00% <100.00%> (ø)

mizugo/logs/empty.go
100.00% <100.00%> (ø)

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


FEATURE REQUEST - Allow switching to Testnet mode via UI

Sparrow has been my go to recommendation for desktop for a long while now and I often urge people to try it out in testnet mode first to get comfortable. It would be great if users could achieve this from the preferences pane in the UI rather than needing to follow these instructions, which, although well documented, can be a little daunting for newer Bitcoiners.

Implemented in c981cf3. If Sparrow is running in mainnet, there will be a Tools menu item to 'Restart in Testnet'. This will change to 'Restart in Mainnet' if Sparrow is not running mainnet.

Can confirm this is working well in 1.6.4 on Ubuntu Linux. Commenting here as it may be worthwhile updating the docs at https://sparrowwallet.com/docs/faq.html to describe the new way of connecting to testnet.

Thanks for the nudge - updated the FAQ.


identifies tetragon pod managing a pod

Thanks for contributing! Please ensure your pull request adheres to the following guidelines:

[ ] All commits contain a well written commit message and are signed-off (see Submitting a pull request).
[ ] All code is covered by unit and/or end-to-end tests where feasible.
[ ] All generated files are updated if needed (see Making changes).
[ ] Provide a title or release-note blurb suitable for the release notes (see guidelines).
[ ] Update documentation and write an upgrade note if needed (see guidelines).
[ ] Are you a user of Tetragon? Please add yourself to the Users doc in the Cilium repository.

This is slightly modified script of https://raw.githubusercontent.com/cilium/cilium/main/contrib/k8s/k8s-get-cilium-pod.sh . This script helps user to identify tetragon pod running on the same node as a pod.
Fixes: #issue-number
<!-- Enter the release note text here if needed or remove this section! -->

This is just a script so no need to run CI, we can just merge.


Read-only List type

It would be really useful to have a List type that is read-only.
Sometimes your Model contains properties that should only be modified by other processes or with sync, only by the server. It would be really nice to be able to specify that in the type system, so that can't accidentally end up writing to them.
With regular properties you can do that by specifying them as dynamic private(set) var myproperty = "", but that does not work with List.

This would certainly be useful, but I'd rather consider the problem in the general case before coming up with individualized solutions, like this case for List.
For example, even with the private setter approach you mention above (which is also possible to do in Objective-C), Realm still doesn't know if the property should be settable via other means, such as setValue(_:forKey:).
We should design a system in which we don't cause an explosion of types (mutable & immutable variants for each property type).

Yes, do you have any ideas for how this could be implemented? We could obviously do our own totally separate annotation, like we do for ignored properties. But since that does not involve the type system, it will only give runtime errors.

I have some ideas that would require making List & RealmOptional a struct (still backed by a class), in which mutating operations would be marked as mutating, offering the compile-time validation you're looking for.
Another (longer term) idea would rely on Swift's work-in-progress property behaviors to add compile-time mutability annotations to Realm types.


Fix grammar and spelling in agentchat_groupchat_vis.ipynb

Why are these changes needed?
Improve readability.

Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

@shruti222patel thank you for the language fixes. Did you run the notebook post these spelling changes especially cuz they changed the system prompts? Were there any differences?


Terminate the Finder if so desired

Along with blockedApplicationBundleIDs, attemptToBlockApplicationLaunches and terminateApplicationsOnLaunch it would help drive the point home if we could quit the Finder.
Unfortunately adding "com.apple.finder" to blockedApplicationBundleIDs causes a loop where launchd relaunches Finder.app and Nudge ends it.
It's achievable to end the Finder by AppleEvents using /usr/bin/osascript -e 'tell app "Finder" to quit' or more involved launchctl commands. Either way it seems to require special consideration to suppress the Finder not currently doable with Nudge.

I would leave that bundle ID out and ask if you can document this behavior on the wiki.


gz-cmake3 ➡  main

➡  Forward port
Port gz-cmake3  ➡  main
Branch comparison: https://github.com/gazebosim/gz-cmake/compare/main...gz-cmake3
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

LGTM, but note that we don't have particularly complete CI here.

nothing is using gz-cmake4 yet, so it would take a bit of work to test this further


Update emoji-uz.php

I removed emojis that Uzbeks don't use at all so that bytes are not wasted

This repository is a subtree split, and PR must be open on symfony/symfony.

This file is autogenerated from official sources, we cannot tweak it "by hand".
Also, as @lyrixx noted, changes should be submitted to https://github.com/symfony/symfony/


feat(multi_object_tracker): increase max-area for truck and trailer

Signed-off-by: yukke42<EMAIL_ADDRESS>Description
There are trucks about 18 m length and they are filtered by the max-area gate of multi-object-tracker. I have changed not to filtered large vehicles, and the 70 value is 20 m (large vehicle length with a margin) x 3.5 m (maximum width of general road in Japan).
Blue: /perception/object_recognition/detection/objects
Red: /perception/object_recognition/tracking/objects
before:
https://user-images.githubusercontent.com/24660808/187078134-89f64845-0da5-4c06-b7d7-e2e8baa7d4b3.mp4
after:
https://user-images.githubusercontent.com/24660808/187078136-32baedee-b444-4f93-a4ec-8e92d98ab744.mp4
Related links

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@yukke42 I have two questions.

Can you show the size data? because the large truck size is defined as within 12m x 2.5m in Japan.
Is it a trailer, not a truck?

A single grid is 1 m long. The longest vehicle is a trailer, but others are truck, but our model classifies truck and trailer as a same label.

Is it better for the model to classify these vehicles as trailer and should I change data-association matrix of the trailer?

I think it is better to make a trailer for anything over 12m in post-process of CenterPoint and apollo instance segmentation.
Also, about width, 2.5m maybe too strict, it seems to be good to 3.0m

@yukkysaito
I have changed the params of truck and trailer in this 86aa161.

@yukkysaito
updated max-area matrix values as you advised.

@yukkysaito Sorry for the late, I have updated the params as you said.


Errors with $util.time when mocking locally

Describe the bug
Noticed two errors when working with the $util.time utility functions.

$util.time.nowFormatted("yyyy-MM-dd") is giving minutes instead of the month for the MM value. I dug into the source code a bit, and it looks like the Node.js time library that is being used for this has slightly different formatting rules than AppSync's. In dateformat lib, MM represents minutes. In AppSync, mm is supposed to represent minutes. Not sure which one is the correct UTC/ISO implementation, but this causes some confusion when testing locally.

$util.time.epochMilliSecondsToISO8601() does not work locally. In this case it will throw an error: "Cannot read property 'first_line' of undefined"

To Reproduce
Steps to reproduce the behavior:

Edit any VTL template.
Add a line including the above time utilities and store in a variable.
"Log" the variable out with $util.error()
Run amplify mock and hit the resolver you edited

Expected behavior
Time utils should work locally

@chrisco255 thanks for reporting the issue, it seems that formatting is different as you described, we'll look into it.


Compass

Hi
Would you know if this chip can calculate compass angle like most magnetometer and would you have any example code to calculate rotation count? Example if i rotate the gyro on a table? (Example: 2 counter clockwise ration)
Thanks

Hi @minhanh1234,  you can use the magnetometer data to make a compass out of it. You would need to determine the max and min values for the x- and y-axes and then interpolate your measured values to determine the direction. However, the magnetic field strength depends on your location (e.g. inside and outside of buildings) or other factors like electric devices which are near to the module. Another factor to consider is that if you vary the z-angle, it will also influence the magnetic measurements. I tried a bit, the it became too complex and I gave up. The other option to determine the direction of the x- and y-direction (yaw-angle) is to constantly measure gyroscope data:
angle/time * time = angle.
Of course, you will have certain error when using this method and the errors can add up over time.
So, in summary, basically it's possible, but I do not have plans to implement this as a feature. Hope this helps a bit.


Templating and References

I'm trying to create 2 different complex objects based on the same template. My goal is to write a unit test, that makes sure that only specific properties can be updated by a function.
The problem is that Autofixture seems to create References instead of new objects. Here's a sample:
var template = _fixture.Build<Foo>()
                      .With(m => m.Id, 100)
                      .With(m => m.Prop2, "123")
                      .Without(m => m.FooContent)
                      .Create();

_fixture.Register<Foo>(() => template);

var subject= _fixture.Create<Foo>();
var expected = _fixture.Create<Foo>();

subject.Prop3 = 300;

if (expected.Prop3 == 300)
            throw new Exception("BOOM");

As AutoFixture user I would expect to receive a real object instead of references onto the my given template.
Am I doing something wrong, or doesn't AutoFixture support this behaviour?
Edit: After giving it a second thought I guess this isn't easy. The main problem will be the deep copy, Still is there a way I could achieve this with Autofixture?

I would expect to receive a real object instead of references onto the my given template.

Why?
Let's try to take AutoFixture out of the picture:
var template = new Foo { Id = 100, Prop2 = "123" };

var sublect = template;
var expected = template;

subject.Prop3 = 300;

In this case, what would you say the value of expected.Prop3 is?

My point is that I would expect that AF gives me a new object on a Create<> call instead of a reference to my template.
How it is currently implemented the Register<> call works only for structs.
Please don't get my wrong - i really like AutoFixture. It saves a lot of time. I just wanted to bring this issue to your attention/ ask if there's a way to supply templates to AF that result in new Objects. Maybe I'm using it wrong.

As AutoFixture user I would expect to receive a real object instead of references onto the my given template.

No, it would be a POLA violation if AutoFixture didn't behave this way, since you are specifying explicitly that your object should be created in a particular way:
_fixture.Register<Foo>(() => template);

That is, you are specifying that, for all Foo, you need the template instance back.

Point taken.
Is there another way to make AF always return an object that has the same values set for consecutive calls to Create<>? Best without having to set up every property in advance.
If not would that be a use-case for AF?
Please feel free to close this issue if you don't see such requirement...

Does Customize do what you want to do?
fixture.Customize<Foo>(c => c
    .With(m => m.Id, 100)
    .With(m => m.Prop2, "123")
    .Without(m => m.FooContent));

Customize is not the thing I'm looking for. When I've to call it for every property on my model I'd opt for writing less code by instantiating a new object with new.
My goal was to create a spec for a repository that has an Update method. The spec was supposed to make sure that the repository is only able to update a predefined set of properties. The model is expected to grow in the number of properties and I didn't want to go back to edit that test every time I add a new property.
My Idea was to have AF create a template of my model. The template is then provided to AF to generate clones of exactly that setup. But I guess this is an edge case for which AF was never meant (maybe its even a stupid thing to do).
Now I'm using serialization to create clones of my template.
Thank you for all your feedback. If you like you can close this issue.

a predefined set of properties

Where is this set predefined?
(I'm going to close the issue, because I don't think it belongs in the realm of AutoFixture, but feel free to keep the discussion going if you'd like.)


Animate retractaction of the switch + pedestal in chamber 11

Version of the game
current master
What is the enhancement?
In chamber 11, the switch and it's pedestal should retract into the ground after the ballcatcher is triggered.
Screenshots
https://github.com/mwpenny/portal64-still-alive/assets/2451901/45447cf9-1ffe-4037-b8b6-22ebd3780108

This will be some more nice polish. You'll need to use a @dynamic_box instead of static @collision, and create an @anim object to animate everything.


testing/ltp: split the ltp source include to 2 part

Signed-off-by: nietingting<EMAIL_ADDRESS>Summary
testing/ltp: split the ltp source include to 2 part
Impact
no
Testing
test on local

Why not just make the underlying build infrastructure support longer lists of files which is what I did.

I agree, it is better to fix the underlying problem. This can occur again with other projects.

I will submit a PR that uses a max args function split the calls for clean and archive. That way they are chunked on  20 files or something reasonable.

Great, I was going to suggest that. That way we can still have some efficiency when this problem does not occur.

This should be resolved with this https://github.com/apache/incubator-nuttx/pull/3510

Ok, let's close this PR.


WIP: Languages Support

Working on adding language support.
To do:
UI:

[x] Login
[x] Forgot Password
[x] Reset Password
[x] Dashboard
[x] Project

[x] Add
[x] Edit
[x] View

[x] Users

[x] Add
[x] Edit
[x] Edit Profile
[x] View

[x] Settings
[x] Builds

[x] List
[x] View

[x] Plugins

Command Line Tools:

[x] Install
[x] Update
[x] Poll
[x] Create Admin
[x] Run Builds
[x] Builder

[x] Build Plugins

Languages

[x] English
[x] German (Provided by @thormeier)
[x] Dutch (Provided by @matthiasmullie and @tvbeek)
[x] Russian (Provided by @corpsee, @xboston, @ViGo5190)
[x] French (Provided by @shulard)
[x] Danish (Provided by @NamelessCoder)
[x] Greek
[x] Polish
[ ] Arabic
[ ] Spanish (Looking for volunteers)
[x] Italian (Provided by @mavimo)
[ ] Ukrainian (Provided by @borales)
[ ] Brazilian Portuguese (Provided by @gustavoheinriq)
[ ] Chinese (Looking for volunteers)
[ ] Japanese (Looking for volunteers)

Brazilian Portuguese already available?


Graph line extrapolates graph top limit when fps is over 60

This probably is a known issue but I'll open a ticket for this to stay as a reminder.
I found this when testing 120 fps video. Graph line goes up so much that ended in the middle of the screen.
Probably it is more interesting to develop a gui so no hurry to fix this.

Yes, this is a known issue. So far, only videos up to 60fps are properly supported. We will fix this at a later stage but it's not a priority right now. Thanks for the reminder though :)

I really find this software awesome! I'll keep helping reporting anything I find :D

This is now fixed in the GUI version, as we now support any framerate.


CFE failover incorrectly counts IPv6 addresses per interface in AWS ipv6 failover

Do you already have an issue opened with F5 support?
No.
Description
CFE failover in AWS with IPv6 addresses. CFE appears to "count" each IPv6 address multiple times, thereby incorrectly reporting
Function error, retrying: Address count 17 per interface exceeds the limit for m5.xlarge. Retries left: 0

In this case I have only 1x IPv4 addr, and 4x IPv6 addresses, but CFE appears to count this as 17 addresses to move. This can be seen all through the logs and from what I can tell it is not dependent on the number of VS's a virtual address has. Ie., if I have 2 VIPs with different ports and same IP, the address looks like it's still counted 4 or 5 times. If I have 1 VIP, it's still counted 4 or 5 times.
Very simple replication of issue

Deploy our supported 2-NIC CFT, set up for IPv6 failover by editing IAM role and Security Group accordingly
See CFT issue 153 to make sure you can fail over IPv6 addresses
Successfully fail over a VS with IPv6. You will need a VS with IPv4 also, and you can fail over 2x VS with IPv6.
Watch CFE logs and notice that for each IPv6 address, it is counted multiple times. Example:

Wed, 30 Jun 2021 13:53:29 GMT - fine: [f5-cloud-failover] associating ipv6 addresses: {"NetworkInterfaceId":"eni-033bf289856441e7c","Ipv6Addresses":["2600:1f18:43ea:1101:cb86:6603:447f:f069","2600:1f18:43ea:1101:c89:614f:cd7:65c6","2600:1f18:43ea:1101:245f:ff1e:e7dc:20d0","2600:1f18:43ea:1101:cb86:6603:447f:f069","2600:1f18:43ea:1101:c89:614f:cd7:65c6","2600:1f18:43ea:1101:548b:857:8926:30eb","2600:1f18:43ea:1101:c89:614f:cd7:65c6","2600:1f18:43ea:1101:548b:857:8926:30eb","2600:1f18:43ea:1101:245f:ff1e:e7dc:20d0","2600:1f18:43ea:1101:cb86:6603:447f:f069","2600:1f18:43ea:1101:548b:857:8926:30eb","2600:1f18:43ea:1101:245f:ff1e:e7dc:20d0","2600:1f18:43ea:1101:cb86:6603:447f:f069","2600:1f18:43ea:1101:c89:614f:cd7:65c6","2600:1f18:43ea:1101:548b:857:8926:30eb","2600:1f18:43ea:1101:245f:ff1e:e7dc:20d0"]}
Wed, 30 Jun 2021 13:53:29 GMT - finest: [f5-cloud-failover] Function error, retrying: Address count 17 per interface exceeds the limit for m5.xlarge Retries left: 0

Now, create 4 total IPv6 addresses and 1 IPv4 address, and make associated VIPs. Attempt failover again, and you should see that CFE incorrectly believes the number of addresses to moves exceeds AWS's limits.

Environment information
For bugs, enter the following information:

Cloud Failover Extension Version: 1.8
BIG-IP version: 16.0.1
Cloud provider: AWS

Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 2
I have created this as Sev 2 because it's blocking a prod migration for this customer, who has already reported multiple issues with IPv6 and CFE in AWS. However this one looks like a show stopper for their migration.

It appears the incorrect address count may the square of the true IPv6 addr count, plus the IPv4 addr count.
During testing with AWS m5.xlarge, it appears that logs are showing that CFE is counting each IPv6 address:
-5 times when 5 Virtual Addresses are configured
-4 times when 4 Virtual Addresses are configured
-3 times when 3, etc
So in my test, CFE function error/failure occurs after 4x IPv6 VIPs are configured (+1 IPv4 = 17 addresses, as shown in logs above). However in customer test they could deploy extremely large VM to get a few more VIPs (not an acceptable workaround, and they need more VIPs still).

This issue is being tracked internally with ID AUTOSDK-555.

@shyawnkarim  - unfortunately we need this issue re-opened and addressed. This was supposed to be fixed in CFE v1.9.0 and I even successfully tested a pre-release that was provided to me by a developer. However, I did not download and test the official release, once 1.9 was released, and now the customer is hitting this same issue with 1.9.0
Please prioritize if possible as this customer has been waiting over 6 months for this bug fix that is delaying production implementation.

Thanks Shyawn for updating me. For anyone following the issue, this bug was fixed shortly after CFE v1.9.0 was released, so the fix is planned to be released with the next release of CFE and we don't have a ETA for that release at this moment.

Closing.
This issue was addressed with Release 1.10.


Vimscript colorization doesn't support non matching parenthesis in the pattern section of the substitute command

Steps to reproduce

Create a Vimscript with the following content:

substitute /(/a/
substitute /a/b/

The first substitute is identified as a vimSubst where the second is identified as vimVar

Expected behaviour
Both substitute call should be identified and colorized as vimSubst
Remark: If the pattern contains a closing parenthesis the problem is not present:
substitute /()/a/
substitute /a/b/

Version of Vim
9.1.432
Environment
OS: Windows 10
Vim Flavor: gVim
Logs and stack traces
No response

Thanks for your quick answer.
Indeed if I remove the space between substitute and the first / the highlighting is correct.
Thanks for your support.

I confirm that it solve the reported problem :-).
Thanks for the support!


Make the inference server exit gracefully in case of errors instead of hanging

Currently, the inference server waits for the results from child processes indefinitely, which leads to hanging if one of these processes dies. There are at least two ways to reliably trigger this:
(1) Pass in an invalid SMILES for encoding (tracked in #15)
(2) Initialize the inference server after having initialized tensorflow (which poisons the context of the forked child processes)
We could handle (1) better, and this is further described in #15, but I didn't find a way to detect (2) other than let the child process die and then try to recover from that.
In this PR, I make the experience a bit smoother by making the parent process exit gracefully in case a child process dies.

Hello,
I am currently using the latest version of molecule-generation (0.4.1) and am encountering an issue similar to one that was previously discussed and resolved. Here is the error message I'm receiving:

[08:48:42] Explicit valence for atom # 22 N, 4, is greater than permitted
[08:48:45] Explicit valence for atom # 22 N, 4, is greater than permitted
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/molecule_generation/utils/moler_inference_server.py", line 272, in try_collect_results
result_id, result = self._output_queue.get(timeout=10)
File "/usr/lib/python3.8/multiprocessing/queues.py", line 108, in get
raise Empty
_queue.Empty
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "notebooks/create_bindingdb_moler.py", line 37, in
setup(drug_featurizer=featurizer, _device=device)
File "notebooks/create_bindingdb_moler.py", line 31, in setup
drug_featurizer.preload(all_drugs)
File "/ConGen/src/featurizers/molecule.py", line 96, in preload
self.write_to_disk(seq_list, verbose=verbose)
File "/ConGen/src/featurizers/molecule.py", line 73, in write_to_disk
feats_list = self.transform_list(seq_list)
File "/ConGen/src/featurizers/molecule.py", line 53, in transform_list
feats_batch = model.encode(batch)
File "/usr/local/lib/python3.8/dist-packages/molecule_generation/wrapper.py", line 113, in encode
return self._inference_server.encode(
File "/usr/local/lib/python3.8/dist-packages/molecule_generation/utils/moler_inference_server.py", line 310, in encode
return self.try_collect_results(num_results)
File "/usr/local/lib/python3.8/dist-packages/molecule_generation/utils/moler_inference_server.py", line 281, in try_collect_results
raise RuntimeError("Worker process died")
RuntimeError: Worker process died

My current environment where the code is running includes:
Python 3.8.10
TensorFlow 2.9.3
CUDA 11.8
Single GPU: NVIDIA GeForce RTX 2060
Despite the solution provided here, I am still encountering an error. Any assistance for solving or understanding the problem I am encountering would be greatly appreciated. Thank you.

@cankobanz The PR you posted in made it so that MoLeR no longer hangs on errors, and instead exists gracefully. Your logs indeed show it has done so, thus it's handling the error as expected - the only question is, why is it encountering the error 🙂
From your logs, I assume this happens during encoding (not decoding) of a potentially long sequence of SMILES. Is that correct? If so, do you see the error always or only at scale (which could suggest it's being triggered by outliers)? Are all of the SMILES you're encoding valid (i.e. can they be parsed by rdkit)?

@kmaziarz, thank you for the quick and detailed response. Now, I understand the fix that was applied here. I can easily identify and remove the invalid SMILES molecules from my dataset.


mountpoint not found when building docker

Hi
I cloned docker master and run make command, error "mountpoint not found" came up. What should I do the pass the building. Here are the logs
docker$ git branch
* master

and docker daemon output
~$ sudo docker -d
2014/06/10 16:13:15 WARNING: You are running linux kernel version 3.2.0-4-amd64, which might be unstable running docker. Please upgrade your kernel to 3.8.0.
2014/06/10 16:13:15 docker daemon: 0.11.1 fb99f99; execdriver: native; graphdriver:
[59d5d416] +job serveapi(unix:///var/run/docker.sock)
[59d5d416] +job initserver()
[59d5d416.initserver()] Creating server
2014/06/10 16:13:15 Listening for HTTP on unix (/var/run/docker.sock)
[59d5d416] +job init_networkdriver()
[59d5d416] -job init_networkdriver() = OK (0)
2014/06/10 16:13:15 WARNING: mountpoint not found
Loading containers: ..............: done.
[59d5d416.initserver()] Creating pidfile
[59d5d416.initserver()] Setting up signal traps
[59d5d416] -job initserver() = OK (0)
[59d5d416] +job acceptconnections()
[59d5d416] -job acceptconnections() = OK (0)
2014/06/10 16:13:22 POST /build?rm=1&t=docker%3Amaster
[59d5d416] +job build()
[59d5d416] +job allocate_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b)
[59d5d416] -job allocate_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b) = OK (0)
[error] container.go:455 Error running container: mountpoint not found
[59d5d416] +job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b)
[59d5d416] -job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b) = OK (0)
[59d5d416] +job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b)
[59d5d416] -job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b) = OK (0)
mountpoint not found
[59d5d416] -job build() = ERR (1)

hmmmm can anyone reproduce this anymore

To myself, I upgraded kernel and everything is ok since several weeks. Anyway I will remove my LXC containers (that I'm translating to docker containers)

I'm using linux mint LMDE based on Debian 8. Kernel version - 3.16. Here is some info:

docker info:

Containers: 15
Images: 35
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 65
 Dirperm1 Supported: true
Execution Driver: native-0.2
Kernel Version: 3.16.0-4-amd64
Operating System: Linux Mint LMDE
CPUs: 2
Total Memory: 3.83 GiB
Name: harry.home
ID: K2OV:F3SS:NGXA:6BP2:HK2Z:6IC5:4TDK:X2SZ:VNIL:UOHR:QJX3:KP6E
WARNING: No memory limit support
WARNING: No swap limit support

docker version:

Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.3.3
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.3.3
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

lxc-chconfig:

--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled
Multiple /dev/pts instances: enabled

--- Control groups ---
Cgroup: enabled
Cgroup clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled

--- Misc ---
Veth pair device: enabled
Macvlan: enabled
Vlan: enabled
File capabilities: enabled

But when i'm trying to run any docker - i'm getting:

FATA[0000] Error response from daemon: Cannot start container %container_id%: [8] System error: mountpoint for devices not found

Came across the same issue, Reboot fixed them


Add explanation for exclamation point in man brew-cask

As per https://github.com/caskroom/homebrew-cask/issues/13160 , there's no explanation in the official docs for what an exclamation point means in the output of brew cask list.  It would be great to get that added.

This issue will be looked at once https://github.com/caskroom/homebrew-cask/issues/14058 is completed.
Thank you for your suggestion, though.


Add section to README about slack and irc channels

This commit adds a section to the bottom of the README that mentions our
slack and irc channels for retworkx if people would like to reach out
about the library.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10679

Relevant Lines:
10849

💛  - Coveralls

I wanted to note that when joining the Slack space, one does not automatically join the #retworkx channel as well. For a new user, it appears that this space is only about Qiskit, as none of the channels displayed on the left seem to concern retworkx. At first, I did not realize that there are additional channels that I need to search for and join manually.


Is it possible to cancel an async query?

Is there any way of cancel an async run?
mMyQuery.runAsync(new QueryCompleteListener() {
          @Override
          public void completed(QueryEnumerator rowsEnum, Throwable error) {
               //some-stuff
          }
});

and if i'm not anymore interest in the result, ask this query to cancel itself, calling something like:
mMyQuery.cancel();

this pattern follows the AsyncTask class from Android

Hi @condesales,
Query.runAsync() returns Future. You can try to call Future.cancel(). I have never tried to cancel Query. Please share the test result if this works!
https://github.com/couchbase/couchbase-lite-java-core/blob/81d3662b10149725481555b570e3697124e0a202/src/main/java/com/couchbase/lite/Query.java#L414-L417
@InterfaceAudience.Public
public Future runAsync(final QueryCompleteListener onComplete) {
   return runAsyncInternal(onComplete);
}

I will close this ticket. If above solution does not work, please reopen the ticket.
Have a nice weekend!

That's exactly what I was looking for. Thanks @hideki


Use buffer_tobytes on non-object types in test

Pulled out from PR ( https://github.com/zarr-developers/numcodecs/pull/121 )
When running the check_backwards_compatibility test, make sure not to call buffer_tobytes on object arrays from fixture data. Casting these to bytes doesn't really make sense as it will return representation of pointers in the underlying buffer. Not only are the pointers things we do not want to be comparing, but it is also internal spec to NumPy and Python that really isn't reliable either. So make sure to pass through the object arrays as is.
[Description of PR]
TODO:

[ ] Unit tests and/or doctests in docstrings
[ ] tox -e py37 passes locally
[ ] tox -e py27 passes locally
[ ] Docstrings and API docs for any new/modified user-facing classes and functions
[ ] Changes documented in docs/release.rst
[ ] tox -e docs passes locally
[ ] AppVeyor and Travis CI passes
[ ] Test coverage to 100% (Coveralls passes)

Thanks for the review. :)


tour: [REPLACE WITH SHORT DESCRIPTION]

Context: https://tour.golang.org/methods/4
Change the title above to describe your issue and add your feedback here, including code if necessary

Can probably be closed now @adg @broady @rakyll @askumbhani66


How to disable browser-sync? (to lose its Py/C++ dependencies on Windows)

I'd rather not remove it entirely, thats destructive. Right now i dont actually use browser-sync, but at build it requires having Python and the Visual Studio C++ compiler installed on the Windows dev machine.
Is there a way to disable browser-sync at build to drop the Python / Visual Studio dependencies?
I did not have this problem until yesterday, when my Windows machine (that already had Python and VS installed for other reasons) decided to stop auto-magically working ..for no apparent reason. Apparently stuff on my Windows dev machine is colliding, and i wasted enough hours on that to take my loss and move on.

Hi Barry - Sorry to hear. Unfortunately, there's currently no way to simply disable it. You'd have to go into srcServer.js and simply utilize webpack's server without browser-sync's.
We have a number of Windows machines at work using browser-sync just fine. Are you getting an error? Are you running Python 2.7? Might also check the browser-sync issues/forum to see if your issue is covered there.

I didn't install python until just last week, but even prior to that I had no major issues with browser-sync.

Interesting. I thought it was browser-sync that required it, but it appears I was mistaken. Their docs only mention the C++ requirement on Windows, so your experience makes sense. It sounds like I can remove the Python requirement from the setup.

If you're looking for a way to host without browser-sync, I created a simplified version of react-slingshot that uses Webpack's dev server directly - so no browser-sync is required. I created it for my upcoming React with Redux Pluralsight course and it's still changing daily, but the Webpack dev server setup is complete and works.
So now that we have an example to reference for those interested in dumping browser-sync, closing.

hi please tell me how can I generate a new react-slingshot app without browser-sync or how can I remove browser-sync from the installed one?


inschek chokes with <100K observations

Another small issue with automatically setting up PST from flopy model. inschek chokes with >100K observations, so can't use it to populate starting values for observations. In my example, I just removed some potential obs from HYDMOD, but might want to figure a way around that...

I've seen that too. For hydmod, smp or hob, we can fix this by loading the output files with pandas and replacing values. But for other arbitrary instruction files...

kewl. should we just detect if NOBS for a given INS file is 100K or greater and, if so, warn about no INSCHEK run and populate with some dummy obs value like -9999 or 1.0 or something?

i think it does populate with dummy Vals now. Let me know if it doesn't...
I'll prob just recompile inschek to process more obs.

since inschek bombed, pyemu didn't get the chance to write values. I think either we fix inschek or trap for large number of vars prior to calling inschek

Would be nice to rewrite inscheck so that it allocates more memory if needed, instead of hardwiring an upper limit.

Ok, Mike - we should trap for that, at least for hymod, hob and smp files since we have knowledge of the output file structure.
Chris - I agree, but In fortran, that's not so fun. I guess you would have to read through the instruction file once to get the number of observations, then rewind it and process?  I haven't looked at the inschek code closely, but I can foretell a wicked nest of goto statements :)

Lately, we've been dynamically reallocating arrays on the fly, unless we now the size up front.

Finally this has a solution - Pst now has a process_output_files() method that uses pure python instruction file processing.  Its def not as robust as INSCHEK but it removes the need to run a pre-compiled binary (and so far it is orders of magnitude faster than INSCHEK)


stackblitz.com Polymer projects don't work after update of libs

Description
After updating libs to latest in stackblitz or reinstalling libs with same version the app breaks.
Live Demo

https://stackblitz.com/edit/lit-element-example?file=index.js
Steps to Reproduce

Expected Results
working app
Actual Results
Can't find modules:
@polymer/polymer/lib/mixins/properties-mixin (@3.0.5)
@polymer/polymer/lib/utils/case-map (@3.0.5)
Check your import statements & ensure you're importing the correct module names.
Browsers Affected

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari 11
[ ] Safari 10
[ ] IE 11

Versions

lit-element: v0.5.2 or v0.4.0 (have been tested)
webcomponents: v2.0.2 or v2.1.1

your lit-element version is out of date.

did you try it with 0.6.0-dev.6 ? In 'Stackblitz' it isn't working. Also, 0.5.2 should work but isn't. I guess it has something to do with stackblitz... but not sure.

Try jsbin or CodePen

Thanks for pointing this out. Just based on a quick look this seems related to the Symbol polyfill being used and the fact that it looks like StackBlitz always compiles in these polyfills (maybe?). We'll try to get this sorted out.

@sorvell FYI stackblitz also seems to transpile down to ES5 on node_modules, incorrectly.
If you load lit-element, this line:
https://github.com/Polymer/lit-element/blob/b4c5f517655fae936293ae4d6c57350378751716/src/lib/updating-element.ts#L162
Gets turned into (roughly):
for (var i = 0; i < this._classProperties.length; i++) {
But of course maps don't have a length... so no properties work on stackblitz at the min.

@EricSimons stackblitz transpiles code incorrectly.
Here is demo https://stackblitz.com/edit/web-components-zero-to-hero-part-three?file=to-do-app.js

Fyi the transpilation problem is fixed by adding a tsconfig with esnext as target: https://twitter.com/ericsimons40/status/1065351604298113024


optimize variable naming

optimize variable naming

I am neutral on this one.

According to the code specification, constant（static final） naming should be uppercase + underline combination

'constant' and 'static final' are not equal.
Please see the following SO answer.
https://stackoverflow.com/a/12069687/1261766
Those variables you modified are not constants (because they are followed by 'dot') and hence should be in lower case.
I myself don't care about the ancient convention very much, so I usually just 'follow what others are doing'. 🥳

Hi @slievrly ,
Looking at your reaction to my previous comment, I assume you agreed to close this PR.
Please let me know if I misunderstood you.
And thank you for your contribution!


Add the "colors" keyword

Would be handy to have colors aliased with :art:. :grin:

:100: Thanks!

@muan You're welcome! Happy holidays! :sparkler:


Update rnm-getting-started.md to recommend using 0.75

Description
Update rnm-getting-started.md to recommend using react-native 0.75
Why
This documentation has been outdated for quite a while now and it's still recommending react-native 0.71. Now that 0.75 is out we should recommend that instead
Screenshots
N / A
Microsoft Reviewers: Open in CodeFlow

+@Saadnajmi, can you take a look at this?

Hey @gabrieldonadel Thanks for the PR. For transparency: I often forget to update this repo as it's mostly outside of my view (partially evidenced by the fact it's in react-native-windows-samples). We (the macOS team) had been focused on getting 0.74 shipped and 0.75 shipped faster, which meant we missed a few of the steps we usually go back and do, like:

Update this repo
Update the upgrade-helper

I'm currently on vacation, but I'll be sure to take a look at both next week when I'm back.


Ability to load additional idris packages

Hi
thanks for your work on this. This looks great and I'm trying to integrate it into the atom plugin.
I hope it's okay if I open some issues on things that would be nice to have.
I'm happy to help resolve them.

I need this for the atom plugin. I'll try to do something as a package that we can both reuse like you did :)
I'll try to keep it simple.

I changed the title because this project only needs the ability to load additional idris packages from the libdir (idris --libdir)
Pull request incoming

this won't be needed after #7


Clarify Framing Layout

I have received feedback from some that the layout of frames such as this are somewhat confusing:
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           Stream ID                           |
    +-----------+-+-+-+-+-+---------+-------------------------------+
    |Frame Type |0|R|M|L|S|  Flags  |
    +-----------+-+-+-+-+-+---------+-------------------------------+
    |         Major Version         |        Minor Version          |
    +-------------------------------+-------------------------------+

The part that is confusing is after FLAGS. To the right, with no vertical bar, that means we are skipping to the next line. It does NOT mean we are padding with 0s.
Is there a better way of us communicating that?

I am not sure how best to make this clearer. This is how HTTP/2 framing also lays out the fact that things are not aligned as well.

@fiorix any suggestions on how to make this clearer?

I'm fine with it now, but suspect that others might have the same question. We can probably close this and if it comes up again we can put more thought on it.

Also, QUIC layout is using this technique also... not saying it is great or even OK. Just noting the usage.


feat: Initialize dbt logging when running task

airflow-dbt-python was not initializing dbt logging when running. Although logs should still be output to stdout, this was causing the log file to be missing. To allow subclasses of dbt operators to manipulate and export logs, this PR intializes dbt logging when running a task by calling the dbt.events.functions.setup_event_logger function.
Users that wish to operate on dbt logs should either:

Subclass a dbt operator class, update log-path to any absolute path, and operate on the log file after calling super().execute().
Subclass a dbt operator class, implement a custom dbt_directory method that operates on the log file before the temporary directory is deleted.

This call may help with the long standing bug of duplicate log lines #60, but we'll have to see.

Closes #77

Closes #73


Cannot release

1) System.Exception: Could not run "git clone -b gh-pages --single-branch git@github.com:fsprojects/VisualFSharpPowerTools.git temp/gh-pages".
Error:
Cloning into 'temp/gh-pages'...
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
   at Fake.Git.CommandHelper.runSimpleGitCommand@89-2.Invoke(String message) in C:\code\fake\src\app\FakeLib\Git\CommandHelper.fs:line 89
   at Fake.Git.CommandHelper.runSimpleGitCommand(String repositoryDir, String command) in C:\code\fake\src\app\FakeLib\Git\CommandHelper.fs:line 89
   at Fake.Git.Repository.cloneSingleBranch(String workingDir, String repoUrl, String branchName, String toPath) in C:\code\fake\src\app\FakeLib\Git\Repository.fs:line 25
   at FSI_0001.Build.clo@187-17.Invoke(Unit _arg6) in D:\git\VisualFSharpPowerTools\build.fsx:line 190
   at Fake.TargetHelper.runSingleTarget(TargetTemplate`1 target) in C:\code\fake\src\app\FakeLib\TargetHelper.fs:line 411

@forki any ideas?

No sorry.

@forki could you try to release?

Try 'git blame' on Release target in build.fsx. Revert the related commit I made some time ago.

@dungpa Reverted the commit
@forki switched to https for git push
============> success until it tried to release on github:
Created draft release id 1942429
Running build failed.
Error:
System.OperationCanceledException: The operation was canceled.
   at Microsoft.FSharp.Control.AsyncBuilderImpl.commit[a](Result`1 res)
   at Microsoft.FSharp.Control.CancellationTokenOps.RunSynchronously[a](CancellationToken token, FSharpAsync`1 computation, FSharpOption`1 timeout)
   at Microsoft.FSharp.Control.FSharpAsync.RunSynchronously[T](FSharpAsync`1 computation, FSharpOption`1 timeout, FSharpOption`1 cancellationToken)
   at Fake.TargetHelper.runSingleTarget(TargetTemplate`1 target) in C:\code\fake\src\app\FakeLib\TargetHelper.fs:line 411

Uploaded the VSIX by hand to github and to VS Gallery. The remaining problem is that VS does not show that there is an update :( Any ideas?

VS gallery shows correct version. It may take a while. You can search the extension in VS to verify new the version.

ah, I've installed the new version, that's why no notification :)

Where is the announcement tweet for me to retweet? ;-)
On Oct 11, 2015 6:32 PM, "Vasily Kirichenko"<EMAIL_ADDRESS>wrote:

ah, I've installed the new version, that's why no notification :)
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/VisualFSharpPowerTools/issues/1150#issuecomment-147216511
.

Done :)


fix(chat): hide copy and download buttons for code block and table if last message is being generating (Issue #1085)

Description:
hide copy and download buttons for code block and table if last message is being generating
Issues:

Issue #1085

UI changes

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


Major versions

Feature:
Fixes: https://github.com/ai/browserslist/issues/169
Add two new query types which allow users to specify which major versions of a browser/all browsers to allow.  Examples:

last 2 major versions: all minor/patch releases of the current and previous major versions
last 2 iOS major versions: all minor/patch releases of the current and previous major versions of iOS Safari

Changes:

Added a getLastMajorVersions utility function for filtering the released versions of a browser to only include the last two major versions.
Added and used a curryMapName utility method to keep the file size down.  There were plenty of select functions that ended by mapping over the resulting version numbers to prefix them with the browser name.  curryMapName accepts the browser name and curries the a function which can be passed to map in order to do the prefixing.
Tests
README update

cc: @ai

Looks good. I right now preparing for talk. Will check it in Sunday.


Task schedule

coverage: 80.51% (-0.02%) from 80.533% when pulling 4ceb199bed67da01638011c823e7357f5172d648 on dissoupov into 3f6f0fa090c9138516f92a152a60d36c8e07ad66 on main.


Fixes - Implemented DistributedLock.Redis

Added into
Administration
Identity
Ordering
Payment

I've applied your advice to the code.


Update 2i dtest for CASSANDRA-7771

+1

We need to wait until 7771 is committed, yes?

yes, which will hopefully be later today
On Fri, Aug 21, 2015 at 4:25 PM Philip Thompson<EMAIL_ADDRESS>wrote:

We need to wait until 7771 is committed, yes?
—
Reply to this email directly or view it on GitHub
https://github.com/riptano/cassandra-dtest/pull/481#issuecomment-133462404
.


'restrict' for dropdown and dropdownToggle

Why was this removed?  Broke my code during upgrade.  Manually went in the minified code and added restrict:'AC' for both, so that I didn't have to edit every instance of popover in my app.   Using  0.13.0 stable.

See https://github.com/angular-ui/bootstrap/blob/master/CHANGELOG.md#breaking-changes
It was removed based on the discussion in #2156

BTW: having directives matching CSS classes (C) is discouraged in AngularJS, generally speaking.

I could go wrong, but I don't thnk this is mentioned on the changelog either.

@djvs I've linked to an entry to a CHANGELOG.....

Ah sorry, still waking up.


fix: dropping of bb inside a container with auto height enabled

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test<EMAIL_ADDRESS>@tag.Templates"
:mag: Cypress test results

[!CAUTION]
🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9318957196
Commit: 3c6be812f436624ca53bff321c23d33288124b8c
Cypress dashboard:  Click here!
The following are new failures, please fix them before merging the PR:
cypress/e2e/Regression/ClientSide/ExplorerTests/Drag_Drop_Building_Blocks_spec.ts
To know the list of identified flaky tests - Refer here

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-tests=true

Not needed anymore.


Add a way to easily explore the syntactic parser results

Stanford NLP provides a easy way to explore the results of their dependency parser, through Semgrex (http://nlp.stanford.edu/nlp/javadoc/javanlp/edu/stanford/nlp/semgraph/semgrex/SemgrexPattern.html) and Tokenregex (http://nlp.stanford.edu/software/tokensregex.shtml).
It allows to match syntactic patterns in a very concise way, and avoids boilerplate code.
I didn't find anything similar in spaCy, is there other easy ways to explore dependencies ?
And if not, would you consider implementing such pattern recognition algorithms in spaCy?

Agreed. Would love to see graphics for it too.


UI FIX

Feature description
if you need reference will send link but this theme is not good use nord onedark any there are many other
Additional information
No response

anyone if you can add onedark or github rather than catppuccin it will be great

You can fork this repository and then add onedark or github according to the wiki.

You can add it on your own.


clr-datagrid does't resize column width after we update the model

[ x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
column width should be updated properly after we update the model
Actual behavior
column width is not affected if we update the model and it ends with a broken result.
Reproduction of behavior
Click on "add user" to add a user with a long name
https://plnkr.co/edit/1bW0DD?p=preview
Environment details

Angular version: 4.2.5

Clarity version: "0.9.11

OS and version: windows 10

Browser: [all]

Unfortunately, this is expected behavior. We had complaints that columns were "jumping around" when we resized on every single model change. In particular, each page change is a model change, so users would move from page to page and the columns would change width every time. The UX recommendation is now that column widths are set "smartly" based on the initial models, and that we keep the same width as long as the columns are preserved.
In your case, if you have such disparity between the models present in a single column, I can see 3 solutions:

Force a resize by calling datagrid.resize() after updating the model: https://plnkr.co/edit/w1p7eDuf4Xumqky9H3jE?p=preview
Note that in this plunker, I had to wrap the resize in a timeout because I had to wait for the datagrid to actually go through change detection before resizing, otherwise the new row would simply not be in the DOM yet.
Truncate the text in these cells with extreme variance with an ellipsis. Just add a class on the corresponding cells and use something like:

.name-cell {
  overflow: hidden;
  white-space: nowrap;
  text-overflow: ellipsis;
}

If you know in advance the typical length of the data in this column, you can try to assign it a width from the beginning. Just put a class on the column header and give it a width in CSS: https://plnkr.co/edit/1e2DJRjNVriMyTZ0YVpa?p=preview
This works great when the long data is a paragraph of text, because you can give an approximate width and it will wrap if it's too long. But in your case with long unbreakable words, this solution would require perfect knowledge of the data in the column.

I'm closing this as wontfix since it's the expected behavior, but I hope the various solutions I offered (especially the first one) address your use case.


Expose HTTP headers in the response

This PR gives access to the mailchimp admin URLs which are available in the Link header for certain API endpoints.
For the implementation I left the headers key as it was (for backwards compatibility) but as it contains the curl option values from curl_getinfo() the key name is a bit misleading.
All the headers from the response are now available under a new httpHeaders key. The Link header (whenever provided) is parsed into an array of rel-name => url pairs.
This can then be used from the outside as e.g.:
$url = $MailChimp->getLastResponse()['httpHeaders']['Link']['dashboard'];

Looks good - thanks!


Allow LSP clients to be ignored by name.

Addresses #33

Thanks for the PR @dsully ! This is a really great idea.
However, I have some things I'd like changed, and some things I'd like to add. Is it ok if I take over this PR and make a few changes of my own?

Go for it!

Superceded by #34