crashing on sequoia beta

when I open the app, it is crashing, with the below error.
Termination Reason:    Namespace DYLD, Code 1 Library missing
Library not loaded: /usr/local/opt/mesa/lib/libGL.1.dylib
Referenced from: <0ECD963C-3A8F-38D5-978C-E427502C4EDA> /Applications/mrv2.app/Contents/Resources/bin/mrv2
Reason: tried: '/Applications/mrv2.app/Contents/Resources//lib/libGL.1.dylib' (no such file), '/libGL.1.dylib' (no such file), '/usr/local/opt/mesa/lib/libGL.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/mesa/lib/libGL.1.dylib' (no such file), '/usr/local/opt/mesa/lib/libGL.1.dylib' (no such file), '/Applications/mrv2.app/Contents/Resources//lib/libGL.1.dylib' (no such file)
(terminated at launch; ignore backtrace)
Desktop (please complete the following information):

OS: Sequoia Beta 6
Version MRV2 1.2.5 Darwin amd64

I mistakenly misconfigured my macOS Intel machine and lead to a bad compilation with the mesa libraries.
Please download again mrv2 v1.2.5 macOS amd64 from either github or sourceforge.

Thank you. Even 1.2.4 has same issue.

Thank you. Even 1.2.4 has same issue.

Oh well.  I am sorry that noone reported this previously.

Tried the updated version and got this error. This time with a different path to library.
Crashed Thread:        0
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Termination Reason:    Namespace DYLD, Code 1 Library missing
Library not loaded: /opt/X11//libGL.1.dylib
Referenced from:  /Applications/mrv2.app/Contents/Resources/bin/mrv2
Reason: tried: '/Applications/mrv2.app/Contents/Resources//lib/libGL.1.dylib' (no such file), '/libGL.1.dylib' (no such file), '/opt/X11//libGL.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/X11//libGL.1.dylib' (no such file), '/opt/X11//libGL.1.dylib' (no such file), '/Applications/mrv2.app/Contents/Resources//lib/libGL.1.dylib' (no such file)
(terminated at launch; ignore backtrace)

Please try this beta of v1.2.6.  I will be fixing v1.2.5 and v1.2.4 afterwards:
https://mega.nz/file/SHhEBC5I#MUyfvVW9gLXhqwBMLNEg_SCfF9-0gWgiZMqI_bDDuRw

I've update v1.2.4 and v1.2.5.  They should all be fine now.

beta 1.2.6 is working. Thank you.


Atom feed: support titles with implicit type.

According to the Atom spec, text constructs such as title may have
a type attribute, but if they don't, processors must behave as
though it were present with a value of "text".
YQL treats these two cases differently:
"title": {"type": "html", "content": "HTML content"}
"title": "Text content with unspecified type."

With this change, we use the content property if title is an
object, and otherwise use title as-is.

@eostrom do you have an example of a feed that breaks? Might be good for reference purposes

All I have offhand is my brand new blog's feed: http://notebook.erikostrom.com/feed.xml

@eostrom thanks!


Keep walproposer alive until shutdown checkpoint is safe on safekepeers

The walproposer pretends to be a walsender in many ways. It has a WalSnd slot, it claims to be a walsender by calling MarkPostmasterChildWalSender() etc. But one different to real walsenders was that the postmaster still treated it as a bgworker rather than a walsender. The difference is that at shutdown, walsenders are not killed until the very end, after the checkpointer process has written the shutdown checkpoint and exited.
As a result, the walproposer always got killed before the shutdown checkpoint was written, so the shutdown checkpoint never made it to safekeepers. That's fine in principle, we don't require a clean shutdown after all. But it also feels a bit silly not to stream the shutdown checkpoint. It could be useful for initializing hot standby mode in a read replica, for example.
Change postmaster to treat background workers that have called MarkPostmasterChildWalSender() as walsenders. That unfortunately requires another small change in postgres core.
After doing that, walproposers stay alive longer. However, it also means that the checkpointer will wait for the walproposer to switch to WALSNDSTATE_STOPPING state, when the checkpointer sends the PROCSIG_WALSND_INIT_STOPPING signal. We don't have the machinery in walproposer to receive and handle that signal reliably. Instead, we mark walproposer as being in WALSNDSTATE_STOPPING always.
In commit 568f91420a, I assumed that shutdown will wait for all the remaining WAL to be streamed to safekeepers, but before this commit that was not true, and the test became flaky. This should make it stable again.

I can't check the changes made in the various PG versions due to what seems to be GitHub UI error

Looks like PG change push is missing in the repo.

So I can't yet check out the core changes, but I wonder why postmaster treated walproposer as bgw prevously. Looking at SignalSomeChildren/CountChildren it checks only bkend_type, which is set to BACKEND_TYPE_WALSND soon after MarkPostmasterChildWalSender...

Looks like PG change push is missing in the repo.

Created branches for those and pushed, should be visible now.

So I can't yet check out the core changes, but I wonder why postmaster treated walproposer as bgw prevously. Looking at SignalSomeChildren/CountChildren it checks only bkend_type, which is set to BACKEND_TYPE_WALSND soon after MarkPostmasterChildWalSender...

The postgres changes show that, but in a nutshell, because walproposer is marked as  BACKEND_TYPE_BGWORKER, postmaster never calls IsPostmasterChildWalSender() on it. Postmaster expects that a BACKEND_TYPE_NORMAL process can morph into a walsender, but not a bgworker.

There several more things to do:

Check currently is in wrong place, it won't fire until latch is set.
We need to wait not only for flush_lsn on the quorum, but commit_lsn -- safekeepers don't advance commit position in the absense of compute.
Also commit_lsn should be not only recorded, but persisted on safekeepers (otherwise their restart would pull it back); they do that periodically, but we want here that ASAP.
Add test.

I'll try to finish it.

Interesting, locally it already works without any fixes. Checked, this is because after checkpoint is flushed postmaster kills walproposer with SIGUSR2, which sets the latch, and walproposer manages to commit (and send commit_lsn) to safekeeper before this.

In https://github.com/neondatabase/neon/pull/6751 I'm reverting the previous change that appears to have made test_pg_regress less stable -- would probably make sense to revert the revert in this PR, along with the walproposer changes.  Hopefully together they make the test stable.

In case this is useful: a failure on a branch where I had an explicit wait_for_flush_lsn before compute stop and logged the before + after LSNs, where it looks like the safekeeper has seen the post-stop LSN, but the pageserver hasn't https://github.com/neondatabase/neon/pull/6752#issuecomment-1943752039

There several more things to do:

Mostly did them, now need to merge PG PRs and then this one. @hlinnaka please have a look, I can't request your review :)


Add feature list to README

There are many orthodox file managers out there. I'm looking for one that supports launching external tools to compare files.
Would be informative to list the application features in the README, in addition to the nice screenshots 🙏

I agree, I did want to compile a list of features, especially since some are not discoverable from the menus and other GUI elements.
There is no support for external tools that receive two files (rather than one), but it would be pretty simple to add. There is a built-in file comparison tool, but it only says whether or not the files are equal.

If you get to it, you might add a section about the important differences from TC (apart from being cross-platform), if any. (That could be efficient also for you, allowing to spare listing all the bog standard features TC also have.) I don't mean wasting effort on a detailed "formal" comparison, just an overview.


Shisui Weekly Meeting #7

Meeting Info

Nov 23th, 2024, 9:30 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Dev/Issue progress

fix utp memory leak


Connect-IPPSSession as App Registration

Hi,
Does Connect-IPPSSession Support App Only Authentication? We want to use SCC Powershell for creating labels within multiple tenants and not creating a user on each tenant for doing this.
Thanks for feedback.
Best regards

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

ID: 945ab2ea-22ae-814f-8898-fe84b7f29870
Version Independent ID: 5383d152-988d-b1ee-4957-db5fb6213754
Content: Connect-IPPSSession (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Connect-IPPSSession.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@pheeling, it does not. I would suggest opening a support case and asking about it, which will get the issue in front of people who can make decisions.

@pheeling Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@pheeling we would appreciate any comment, if you were able to get any answer from Microsoft support, because we are considering similar approach to use app-only access to the SCC PowerShell to make some automations.

@mbratukha unfortunately not. The support engineer stated to me it's by design but the request is still open. So my goal is either to get an understanding if there are cmdlet's which could be used with another connections option. Till now we still use username, password and exclude it from our CA policies.

@pheeling thank you for the quick response!
We have analyzed this situation a bit deeply and have figured out that the cmdlet Connect-IPPSSession is capable to kind of "re-use" an existing access token after sign-in via Connect-AzAccount (from  the Az PS-module) or Connect-AzureAD (from the AzureAD PS-module).
The trick is to provide the property UserPrincipalName. Here is an example that has worked for us:
Connect-AzureAD -TenantId {tenant-id} -AccountId {upn}

Connect-IPPSSession -UserPrincipalName {upn}

The cmdlet Connect-AzureAD is capable to be initialized via an access token by providing the property AadAccessToken or MsAccessToken.
We've tested it, but the cmdlet Connect-IPPSSession does not see an existing access token and prompts a user to provide the credentials.
Also, we have tried to use the properties AccessToken, GraphAccessToken and MicrosoftGraphAccessToken of the cmdlet Connect-AzAccount - it does not work too.
Our investigations show, that the cmdlet Connect-IPPSSession seems to rely on a data cached in a local browser after signing in. The execution of the command Connect-AzureAD or Connect-AzAccount with a valid access token does not keep anything in the local browser.
Does anybody know another approach to force the cmdlet Connect-IPPSSession to use an existing access token (with user context)?
Any working approach would make it possible to use a refresh token in the automation scenarios.

@pheeling Thank you very much for the contribution and sharing this explanation. Here, we are limited to documentation fixes and improvements only. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@pheeling, it's seems to be possible even via app-only context: https://github.com/MicrosoftDocs/office-docs-powershell/issues/6716#issuecomment-1045114219
@yogkumgit, would it be possible to extend the official documentation, that this approach is also mentioned there?

Version 2.0.6-Preview5 of the EXO V2 Module is now available, so the various Credential parameters are now available on Connect-IPPSSession, so certibicate-based/app-oly authentication is now fully available in Security & Compliance Center PowerShell.

Version 2.0.6-Preview5 of the EXO V2 Module is now available, so the various Credential parameters are now available on Connect-IPPSSession, so certibicate-based/app-oly authentication is now fully available in Security & Compliance Center PowerShell.

thanks @chrisda amazing work


Simplify steps in plan/build action

Move output gathering to the provider
add 'caching' of outputs & stacks on provider (hope this will help w/
#54)
got rid of _completion_func & _skip_func on steps
removed passing of 'results' dictionary on Plan.execute
broke out _single_run from _execute on Plan for testability

:ship:


Run on Save not functioning

Run on save feature does not autoprefix css file.

Does running the autoprefixing manually work?

Closing as Atom is abandoned.


[microtvm] Add TVMC test for Arduino and Zephyr

This PR adds TVMC test for Arduino and Zephyr platforms and fixes few issues with project API and API servers.
cc @areusch @guberti @gromero

@mehrdadh think the following two tags to the PR (and to the commit if you're going to push force - if multiple commits exist the commit tile that lands is the PR's title, otherwise if it's a single commit the commit's title is used for landing): [microTVM] and [TVMC], case sensitive.


update generated proto bindings.

Running build/get-protoc.sh gave me an updated proto/dish.protoset. My router is running 2022.01.0.mr8624-prod and my dish is running 992cafb5-61c7-46a3-9ef7-5907c8cf90fd.uterm.release.
Afterwards running build/regen.sh fails when compiling spacex/api/device/dish.proto due to a missing reference to
a DishConfig message type. The solution is simple: add another protoc line to pull spacex/api/device/dish_config.proto out of the descriptor set as well. Now everything builds nicely :-)
Before updating these protos running the companion starlink-cli (after fixing https://github.com/starlink-community/starlink-cli/issues/1) would result in output that had a number of "/* 2 unknown bytes */" type comments.
After updating these protos and fixing starlink-cli's go.mod to point to this branch I was able to get complete data dumps from my router and dish without any unknown bytes being reported.

I opened a draft PR on the starlink-cli repo to demonstrate this update in practice: https://github.com/starlink-community/starlink-cli/pull/3


Kosmos2 model

CVS-124888

Also, my Gradio interface does not show a snowman image. Can someone confirm?

View entire conversation on ReviewNB

Added

View entire conversation on ReviewNB

Added saving in jpg to avoid this problem. Looks like it depends on version of libraries and platform.

View entire conversation on ReviewNB

done

View entire conversation on ReviewNB


Remove or replace catch blocks that handle ApplicationException

Remove or replace catch blocks that handle ApplicationException
See #4870 on the use of Exception in catch blocks.
The handling of Exception is particularly widespread in legacy code (that is, examples written for .NET Framework 1.0, 1.1, and 2.0 that have not been revised subsequently). The problems are:

Exception handling with ApplicationException may be used when no exception handling is needed. - Exception handling with ApplicationException is used instead of handling more specific exceptions. As a general rule, catching ApplicationException rather than more derived exceptions is not recommended.

To address the issue of incorrect exception handling:

Work in the dotnet/samples repo.
Find the line of code that handles ApplicationException.
Determine whether exception handling is needed at all. If not, simply delete the try statement and the catch block.
Identify the methods in the try block that are candidates for throwing an exception derived from ApplicationException, and replace that particular catch statement with one or more catch statements that handle the appropriate exception.

The following are C# code examples that handle ApplicationException. In almost call cases, there is a parallel Visual Basic example in the corresponding snippets/visualbasic directory, and in some cases, there is a parallel C++ example in the corresponding snippets/cpp directory.

[ ] snippets\csharp\VS_Snippets_CFX\CFX_CompensationExample\cs\Program.cs

[ ] snippets\csharp\VS_Snippets_CFX\cfx_workflowapplicationexample\cs\program.cs

[ ] snippets\csharp\VS_Snippets_CFX\wfs_compensationcancellation\cs\program.cs

[ ] snippets\csharp\VS_Snippets_CLR\CodeTryCatchFinallyExample\CS\codetrycatchfinallyexample.cs

[ ] snippets\csharp\VS_Snippets_CLR\conceptual.interlocked\cs\source2.cs

[ ] snippets\csharp\VS_Snippets_CLR\HookUpDelegate\cs\source.cs

[ ] snippets\csharp\VS_Snippets_CLR\PropertyInfo.SetValue\cs\Example.cs

[ ] snippets\csharp\VS_Snippets_CLR_System\system.lazy`1.ctorfunc\cs\example.cs

[ ] snippets\csharp\VS_Snippets_CLR_System\system.lazy`1.ctorfuncbool\cs\example.cs

[ ] snippets\csharp\VS_Snippets_CLR_System\system.lazy`1.ctorfuncltsm\cs\example.cs

[ ] snippets\csharp\VS_Snippets_CLR_System\system.Threading.ReaderWriterLock\CS\source.cs

[ ] snippets\csharp\VS_Snippets_CodeAnalysis\fxcop.design.exceptionsshouldbepublic.ca1064\cs\ca1064 - exceptionsshouldbepublic.cs

[ ] snippets\csharp\VS_Snippets_Data\DP EntityObject Concepts\CS\SalesObjects.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria custom feeds\cs\iupdatable.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria linq provider\cs\northwind.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria northwind client\cs\customerorderscustom.xaml.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria northwind client\cs\program.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria northwind client\cs\source.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria northwind service\astoriasnippetscs\sourcetest.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria northwind service\astoriasnippetsvb\sourcevbtest.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria northwind service\cs\northwind2.svc.cs

[ ] snippets\csharp\VS_Snippets_Misc\astoria reflection provider\cs\iupdatable.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifcustomtokenst\cs\passivests\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifcustomtokensts\cs\passivests\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifissuernameregistry\cs\passivests\app_code\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifrccustomtoken\cs\passivests\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifrcfederationforwebapps\cs\fpsts\app_code\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifrcfederationforwebapps\cs\ipsts1\app_code\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifrcfederationforwebapps\cs\ipsts2\app_code\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Misc\wifsigninmessage\cs\webapplication1\certificateutil.cs

[ ] snippets\csharp\VS_Snippets_Remoting\FileWebRequest_ReqBeginEnd\CS\filewebrequest_reqbeginend.cs

[ ] snippets\csharp\VS_Snippets_Remoting\NclCodeGroup\CS\sample.cs

[ ] snippets\csharp\VS_Snippets_Remoting\NCLWebClientUserAgent\CS\useragent.cs

[ ] snippets\csharp\VS_Snippets_Remoting\Socket_Sync_Send_Receive\CS\source.cs

[ ] snippets\csharp\VS_Snippets_Remoting\System.Runtime.Remoting.Channels.Ipc.IpcClientChannel\CS\client2.cs

[ ] snippets\csharp\VS_Snippets_Remoting\System.Runtime.Remoting.Channels.Ipc.IpcServerChannel\CS\server2.cs

[ ] snippets\csharp\VS_Snippets_Remoting\TransactionScope\cs\ScopeWithSQL.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\toolwindowsearch\cs\testtoolwindowsearch_integrationtests\integrationtest library\utils.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterAddNew\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterAllowAdd\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterAllowDelete\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterAlternateBackColor\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterAppearance\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterCancelEdit\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterColor\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterCurrentItem\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterDataError\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VBPowerPacksDataRepeaterDeletingItems\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterDisableAddDelete\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterDisplayedCount\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterFirstDisplayed\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterHeaderVisible\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterHeaderVisibleChanged\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterIsCurrent\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterItemCloned\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterItemCount\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterItemHeader\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterItemIndex\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterItemsAdded\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterLayout\CS\NorthwindDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterRemoveAt\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterScroll\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterSearch\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterSelectionColorChanged\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterVirtualMode\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterVirtualProperty\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VbPowerPacksDataRepeaterWalkthrough\CS\northwndDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_VBCSharp\VSProDataOrcasEndEditOnAll\CS\NorthwindDataSet.Designer.cs

[ ] snippets\csharp\VS_Snippets_Winforms\Classic DataGridColumnStyle.CheckValidDataSource Example\CS\source.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid1\csharp\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_autogencolumns\cs\datagrid_autogencolumns\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_cellselection\cs\datagrid_cellselection\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_checkboxcolumn\CS\adventureworkslt2008dataset1.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_columnsmanipulation\cs\datagrid_columnsmanipulation\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_comboboxcolumnsample2\CS\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_customcolumns\csharp\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\datagrid_frozencolumn\cs\adventureworkslt2008dataset.designer.cs

[ ] snippets\csharp\VS_Snippets_Wpf\GeometryDesigner\CSharp\Window1.xaml.cs

[ ] snippets\csharp\VS_Snippets_Wpf\UIAAutomationID_snip\CSharp\FindByAutomationID.xaml.cs

I'll take care of this once I've gotten feedback from https://github.com/dotnet/samples/pull/377 to make sure I'm doing it right.


[MM-35595] Stop the search shortcut from triggering full screen view on Mac

Summary
When using the Ctrl+Cmd+F shortcut on the Mac desktop app to full screen, the search shortcut would take over as it didn't check for the Ctrl key on Mac.
This PR checks for the Ctrl key so that the shortcut doesn't interfere.
Ticket Link
https://mattermost.atlassian.net/browse/MM-35595
Release Note
Fixed an issue where using `Ctrl+Cmd+F` on the Mac Desktop App opens the search instead of full-screens the app.

@stevemudie You can test this using the webapp SpinWick and the latest version of the Desktop App. There are no Desktop App changes for this ticket.


Consider adding CRM specific types as TS definitions

It would be nice to have CRM specific types be defined more strictly.
For example, OptionSetValue, Money or EntityReference, etc.

It would also be nice to have more strict rules on Guid type, which is not CRM specific, but there are some bugs in turbo forms that causes validations fire twice if Guid to lookup filed was not supplied in uppercase! So it would be nice to ensure that Guids are always in uppercase, have right length, no braces, etc.

I added Guid, Entity and generic Attribute type for now. I'll have to think about how to add the other types, especially EntityReference, since the Web API expects certain formats for those in Create/Update.

Regarding Attribute, you can actually reuse this definition. And that file actually contains more specific attribute types, as well as attribute values.

Maybe is not good idea... it's better to have less dependencies as possible...

That library has a different definition of Attribute since it's form the Xrm.Page attributes. My library is really only for calling the Web API. It's a good idea to use that in your form scripts though for helping build your Web API requests,


refactor(levm): opcode DIV

There’s a redundant check that returns early if the divisor is 0. This is already handled in checked_div.

Closed in #1398


Running installer on clean Rails 5.2 fails with TypeError: no implicit conversion of nil into String

Bug Report
I'm trying to add Futurism to a legacy Rails app running Rails 5.2, and I'm running into problems. Trying to recreate in a new 5.2 app has the same issues.
Describe the bug
Running bin/rails futurism:install --trace gives this error:
Trace
** Invoke futurism:install (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute futurism:install
yarn add v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved 1 new dependency.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
└─<EMAIL_ADDRESS>Done in 2.67s.
Updating
rails aborted!
TypeError: no implicit conversion of nil into String
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/futurism-1.1.0/lib/tasks/futurism_tasks.rake:19:in `initialize'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/futurism-1.1.0/lib/tasks/futurism_tasks.rake:19:in `open'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/futurism-1.1.0/lib/tasks/futurism_tasks.rake:19:in `block (2 levels) in <main>'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `block in execute'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `each'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/task.rb:281:in `execute'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/home/user/.rbenv/versions/2.6.9/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/task.rb:199:in `invoke_with_call_chain'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/task.rb:188:in `invoke'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:160:in `invoke_task'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `each'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block in top_level'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:125:in `run_with_threads'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:110:in `top_level'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/rake/rake_command.rb:20:in `perform'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/command.rb:48:in `invoke'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:18:in `<main>'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/bootsnap-1.10.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/home/user/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/bootsnap-1.10.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:4:in `<main>'
Tasks: TOP => futurism:install

To Reproduce
Create a new Rails 5.2 install with actioncable, then bundle add futurism and bin/rails futurism:install
Expected behavior
I expected it to install, or to give an error message with more information on what went wrong.
Screenshots or reproduction
[see above]
Versions
Futurism

Gem: 1.1.0
Node package: 1.2.0-pre9

External tools

Ruby: 2.6.9
Rails: <IP_ADDRESS>
CableReady: 4.5.0
Node: 14.19.0

Browser
[not applicable]

@julianrubisch Hey! Did you found out what happened? (Trying to solve it)

https://github.com/stimulusreflex/futurism/blob/master/lib/tasks/futurism_tasks.rake#L8-L13
This is not covering all of the possible locations the file could be, it either needs more paths or simply ask for user input if no file was found.

In fairness, this was all written before importmaps-rails, jsbundling-Rails etc.
we‘re just in the process of streamlining all StimulusReflex and CableReady installers, futurism will come next 🤞

Nice find @SpaYco, I was looking in the wrong place. I guess this is the root of my issue? Rails 5.2 didn't use Webpacker by default, so app/javascript doesn't exist unless you install it manually. And my legacy Rails app actually has been retrofitted to use vite_rails, which encourages using app/frontend/entrypoints. Any chance this gem's installer could be less opinionated about this, @julianrubisch? I'm not asking that you should cover every edge case, but maybe a prompt if the standard locations aren't found? Thanks!

It definitely should and will. We’re just trying to reuse as much as possible between CR, SR, futurism and others
cc @marcoroth


Refactoring the scripts

and change the model architecture to fewer Conv layers

Readme file status: WIP

Readme

Readme file For review


ZHA - Conbee USB working sporadically 0.91.2

Intel NUC / Ubuntu 18.04.2 / Docker / Hass.io
ConBee USB using Native ZHA
Last working reasonably well was on 0.91.0 which I had to restore to.
I have a ticket open in zigpy/zigpy-deconz for what is probably a related issue but thought this may belong here.
No error's posted so here is what I have...
Upgrade from 0.91.0 to 0.91.1 went but was trouble (see open ticket in zigpy/zigpy-deconz) and things slowly got worse until it streamed errors, rebooting fixed them for awhile so I stayed and hoped 0.91.2 was going to fix things.
0.91.1 to 0.91.2 upgrade initially broke Samjin motion sensors, they would not react at all. Restored from a snapshot to 0.91.0 and re-ran the upgrade. Had to do a power down reset to get everything to come online. So first walk through motion sensors worked, Cree lights came on but then never went off as they should after 5 minutes. The motion sensors and the Cree lights work sporadically at best. Never generates any error other than those at startup, log is attached.
Here is the log anyway.
home-assistant.zip
Personally I'm starting to think ConBee USB should be remove from the native ZHA compatibility list until more development is done it is very problematic. I would use deCONZ if they had support for my motion sensors.

Samjin devices take a bit to reconnect to the network after a restart (most devices do, especially if you haven’t interacted with them in a bit: buttons, switches etc.) any chance you were just trying them right after a restart?

They had time... it wasn't as if they did not show as available, they did, they just did nothing. I watched the GUI and they never changed state so either the GUI was wrong or it wasn't responding / being recognized. I pulled the battery on one to clear it and waited, still nothing.
Scenario...
1: Upgraded from .1 to .2
2: All looked good, Wife left the house triggered all 3 samjin sensors
3: Lights cam on thru automation as they should
4: Lights never turned off after 5 minutes of no motion
5: Samjin's, all 3, would not respond but looked fine in GUI
6: Pulled a battery on one to try and reset... nothing
7: Could control Cree lights from GUI, on & off no problem
8: Did a power down reset of the system
9: Samjins worked, automation turned lights on
10: After 5 minutes of no motion automation should turn off lights but did not
11: I could control lights in GUI. System acted as if it never got the state change from on to off from Samjins, all 3 of them.
Similar scenario's show that It is like they will report the first state change but never report another.
Running same automation for months...
id: '1549212180185'
alias: Bsmnt Util Motion On
trigger:

entity_id: binary_sensor.samjin_motion_0101aceb_1_1280
from: 'off'
platform: state
to: 'on'
condition: []
action:
data:
entity_id: light.cree_connected_a_19_60w_equivalent_fe0996d2_10, light.cree_connected_a_19_60w_equivalent_fe099b32_10
service: light.turn_on
id: '1549212235358'
alias: Bsmnt Util Motion Off
trigger:

entity_id: binary_sensor.samjin_motion_0101aceb_1_1280
for: 00:05:00
from: 'on'
platform: state
to: 'off'
condition:
condition: state
entity_id: binary_sensor.samjin_motion_0101aceb_1_1280
state: 'off'
action:
data:
entity_id: light.cree_connected_a_19_60w_equivalent_fe0996d2_10, light.cree_connected_a_19_60w_equivalent_fe099b32_10
service: light.turn_off

Just to clarify 1 thing: they’ll show as available no matter what now after a restart if HA last communicated with the device within 120 minutes of the restart. I’ll look into the rest of this though!

I'll keep the restart timing and GUI in mind, I saw that in one of the updates. I did try upgrading from 0.91.1 to .2 and then from from 0.91.0 to .2 with the same result. On 0.91.1 I was starting to get all kinds of errors after running for some time and would have to restart to clean things up. 0.91.0 has been the best so far and is what I am running now.

@vinmar1 are you running firmware 262F or later? I've seen comments the zigpy-deconz expects that

Just downgraded to 262f0500 from 26320500 because of the last set of issues.

what is wrong with that firmware? i also have the issue that sometimes my Xiaomi PIR sensos stay in "not detected" state
is that because of the firmware?

@pergolafabio xiaomi devices are sensible through what "parent" device they are joined to the network. This may cause the device to become unavailable.
As about firmware, AFAIK people have been reporting issues with zigpy-deconz and 26320500 firmware, so official recommendation was to downgrade to 262f0500 firmware version.

I'm going to close this for now...
I played with this today and it appears to be something with the ConBee not the code from what I can tell. If it's just mine or ConBee in general I'm sure I'll figure out eventually. Everything appears to finally be working but as I said I had to play with it. Below is what I finally did.
Upgrade from 0.91.0 to 0.91.1 still sporadic even after giving ample time for everything to come back online and a couple of NUC re-boots.
Upgrade from 0.91.0 to 0.91.2 to see if it fixed it but it was pretty much the same thing.
Restored to 0.91.0 and then did a complete power down including removing the ConBee from the USB Port to be sure power was cut. Restarted and checked everything out, all good.
Upgraded to 0.91.2 from .0 and as soon as it came back up did another complete power down again removing the ConBee from the USB port and restarted. Waited about 10 minutes and checked everything out and it all appears to be fine.  It has been about an hour and I have cycled everything on and off a few times.
So from what I can tell the ConBee did not like the upgrade process. After thinking about it I recall it to seemingly get "stuck" gong back several upgrades and do remember doing a power down reset then. I don't recall exactly the circumstance then but going forward if there are no errors in the log I won't open a ticket period  knowing this ConBee can be a temperamental thing. Apologies if I wasted anyones time, doing all I can on this end with the hardware.
As an FYI I have a HUSBZB-1 I used in my Pi but when I went to the NUC decided to go with an Aeotec and ConBee thinking that there would be better support going forward and I wanted to separate the devices. I still think it was a good move but as with anything new there will always bee growing pains. Thanks a million for all the support I know I won't give up on what I see as the best platform out there.

@Adminiuga
when i first add the devices to phoscon, i always keep them verry close to the conbee stick
so you are saying then that its possible they are link to another router?

i always thought, that the end device will seek for best route and will switch to another router if another router is out of range or disconnected? so you are saying, that if i link it, that device (router) must be always on?
second question see below, i have a verry simple mesh, basicly only end devices and smart plugs, no lights, there is always 1 device coming back, it doesnt have node info (one in red circle), also i dont see it in phoscon web app, if i delete the node, it just comes back
i have no idea what it is?

https://www.dropbox.com/s/l6ant656clm7z5l/nodeinfo.JPG?dl=0

@pergolafabio
for #1 your assumptions are correct. When a few devices are  in close vicinity, there won't be significant signal difference, so it could pick a random device. About re-joining the network, you are also correct, but with xiaomi all bets are off. Sometimes I've seen them moving to new "router", but usually they just stop communicating with parent device because of the timeout expiration.
for #2 not only lights are "routers", usually any mains powered devices are "routers" (exception I know of are King of Fan Wing fan controller and Sengled bulbs). Per your screenshot looks like it used the plug as its parent device. I think it just dropped and need to be rejoined, but depending on what it would use as its parent, it may drop again. Check the thread on home-assistant forum about Zigbee tested devices. There was a few time link posted to Hubitat? forum which lists devices "compatible" being routers for xiaomi sensors.

Ok, thnx for answer, just need to find out what that strange node is on my network, seems difficult

Per MAC address it is a "Silicon Laboratiories", must be something based on Silabs chips.
Are those circles on each device represent an endpoint? If so, it is really strange that chip has only ZDO endpoint.

what circles do you mean? also where do you find info about the mac address?

These circles

For MAC address, google "mac address lookup" and it would come with quite a few links to lookup vendor based on the MAC address, eg https://www.wireshark.org/tools/oui-lookup.html

ah thnx for info
here screenshot
yes, that node is ALWAYS linked to that Xiaomi Smart plug, if i delete the node, its back after a few seconds
unplugging the xiaomi smart plug als doesnt help
https://www.dropbox.com/s/qidgasjezs0hyzq/nodeissue.JPG?dl=0
i have no clue what it is


docs(i18n): New Crowdin updates

:tada: This PR is included in version 4.14.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


build: Include version, os and arch in binaries

Previously the binaries were just named according to their name.
To allow users to see what arch and OS they target, this patch is adding
version, OS, and arch to the filename of the cmds.
Before: virtctl
After:  virtctl-v0.0.1-alpha.6-linux-amd64
This filename is used inthe cmd// directories only, the names in bin/*
are left untouched to keep a friendly usability.
The change is mainly intended to keep the version, OS, and arch
informations in case that the binaries get published (like during
releases).
Signed-off-by: Fabian Deutsch<EMAIL_ADDRESS>

On Fri, Aug 25, 2017 at 11:46 AM, Fabian Deutsch<EMAIL_ADDRESS>wrote:

Previously the binaries were just named according to their name.
To allow users to see what arch and OS they target, this patch is adding
version, OS, and arch to the filename of the cmds.
Before: virtctl
After: virtctl-v0.0.1-alpha.6-linux-amd64

It'd be great to build for multiple platforms as soon as we can.
Y.

This filename is used inthe cmd// directories only, the names in bin/*
are left untouched to keep a friendly usability.
The change is mainly intended to keep the version, OS, and arch
informations in case that the binaries get published (like during
releases).
Signed-off-by: Fabian Deutsch<EMAIL_ADDRESS>You can view, comment on, or merge this pull request online at:
https://github.com/kubevirt/kubevirt/pull/384
Commit Summary

build: Include version and arch in binaries

File Changes

M .travis.yml
https://github.com/kubevirt/kubevirt/pull/384/files#diff-0 (3)
M hack/build-go.sh
https://github.com/kubevirt/kubevirt/pull/384/files#diff-1 (6)

Patch Links:

https://github.com/kubevirt/kubevirt/pull/384.patch
https://github.com/kubevirt/kubevirt/pull/384.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/pull/384, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcJ6S2Iz3fs8RUbrRy4bPXZiGWgR6nFks5sbon6gaJpZM4PCYm-
.

Building the client side tools for other arches/platforms should not be to much of an issue:
https://golang.org/doc/install/source#environment
For true multiarch support on the server side we need to investigate the common denominator of the whole stack .
Also - Which platforms do you have in mind?

On Mon, Aug 28, 2017 at 10:50 AM, Fabian Deutsch<EMAIL_ADDRESS>wrote:

Building the client side tools for other arches/platforms should not be to
much of an issue:
https://golang.org/doc/install/source#environment
For true multiarch support on the server side we need to investigate the
common denominator of the whole stack .
Also - Which platforms do you have in mind?

arm64 and ppc64le
Y.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/pull/384#issuecomment-325285021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcJ6Xpd1kPn-24fwSscMrJ2pENQr4Doks5scnEwgaJpZM4PCYm-
.


irmin-pack: refactor high-level gc implementation

This PR does several things

Moves stats tracking to the internal gc process instead of just at the high-level api boundary
Introduces a promise for a running gc that can be used for callbacks and waiting
Fixes an issue previously discovered with wait (see #1984) but by binding to the gc promise instead of using a polling loop
Fixes issue with run (see #1985) but by attaching a callback to the gc promise instead of using a combination of Lwt.async and Lwt.pause. (I have a local version of the tree benchmark working correctly with the changes introduced here that I will PR later)
To ensure finalisation happens (since we have removed an explicit waiting finalisation through a mechanism like Lwt.async), a non-blocking finalisation is called on every commit (similar to some previous code)
A few small clean up tasks (code, renames, and docs)

This PR can be reviewed all as one or commit-by-commit. The only note on commit-by-commit is that some of the changes introduced in the stats commit were removed in subsequent commits.

LGTM
Could you rebase on master to fix the CI?

Codecov Report

Merging #1994 (e41d0b7) into main (ab8f5ea) will increase coverage by 0.05%.
The diff coverage is 53.70%.

@@            Coverage Diff             @@
##             main    #1994      +/-   ##
==========================================
+ Coverage   63.75%   63.80%   +0.05%
==========================================
  Files         129      129
  Lines       15507    15513       +6
==========================================
+ Hits         9886     9898      +12
+ Misses       5621     5615       -6

Impacted Files
Coverage Δ

src/irmin-pack/mem/irmin_pack_mem.ml
55.81% <0.00%> (ø)

src/irmin-pack/unix/ext.ml
64.87% <55.76%> (+1.32%)
:arrow_up:

src/irmin-fs/unix/irmin_fs_unix.ml
67.74% <0.00%> (-1.30%)
:arrow_down:

src/irmin/watch.ml
80.98% <0.00%> (+2.11%)
:arrow_up:

src/irmin-pack/unix/io.ml
61.42% <0.00%> (+2.14%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[Question] Is there a way to test sideeffects of a method

As an example I have a method that:

Receives some Input
Prepares the data, for example bulids a query
calls a dependecy, for example execute a query

the call could be considered an indirect output. Is there a way to intercept the indirect output to ensure that a refactored version of the method still does the same call?

Right now Scientist requires some kind of output in order to do comparisons.  If the query has some kind of output, then Scientist could be used to compare the results.  For example the query could return an object representation of a SELECT, or it could inspect the total number of rows modified from an UPDATE.
I can provide some more guidance with some more concrete examples.


Can we make this library Cassandra 3.0 Compatible?

I have forked and will try to update it to use a more recent cassandra-driver-core. I will update you when something is ready.

That's something I need to work on.  There is someone who may be doing it in a fork - I'll see if he has code I can use.

Any update on this at all? Little bit of a bummer that we can't use this to connect to our cassandra instances for testing.

Any update on this? Do we have any support for the latest datastax driver? Looks like the failures are with the type casting.

There is one with 3.0 support here:
https://github.com/valchkou/jmeter-cassandra


curl --fail prevents error messages being displayed in logs

I am trying to get CF/TCP routing enabled, but bosh deploy errors saying Review logs for failed jobs: kubernetes-api-route-registrar. So I look at the logs but there are no error messages:
==> /var/vcap/sys/log/kubernetes-api-route-registrar/trace_announce_route.log <==
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:7): main(): PATH=/var/vcap/packages/jq/bin/:/bin:/usr/bin:/sbin:/usr/sbin
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:10): main(): UAA_API_URL=https://uaa.18-220-96-60.sslip.io
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:11): main(): UAA_CLIENT_ID=routing_api_client
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:12): main(): UAA_CLIENT_SECRET=xxx
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:13): main(): CLOUD_FOUNDRY_API_URL=https://api.18-220-96-60.sslip.io
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:14): main(): BACKEND_PORT=8443
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:15): main(): BACKEND_IP=<IP_ADDRESS>
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:16): main(): KUBO_PORT=8443
++22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:19): main(): curl --fail --max-time 10 -s -k -X POST https://uaa.18-220-96-60.sslip.io/oauth/token --data 'client_id=routing_api_client&client_secret=xxx&grant_type=client_credentials&response_type=token'
+22:46:22 (/var/vcap/jobs/kubernetes-api-route-registrar/bin/announce_route:19): main(): UAA_REQUEST=

This comes from https://github.com/cloudfoundry-incubator/kubo-release/blob/master/jobs/kubernetes-api-route-registrar/templates/bin/announce_route.erb#L19-L20
I understand the use of curl --fail so we can nicely get the output into the $UAA_REQUEST variable. But on the downside, we are throwing away the error message.
Since the instructions for configuring the UAA client are manual in https://docs-cfcr.cfapps.io/installing/cf-routing/#step-3-configure-cfcr-for-cloud-foundry-routing there is a high chance of humans getting this wrong (e.g. me).
I would like to strongly advocate for us returning the UAA API error into the logs if there is one.
Perhaps run curl --max-time 10 -s -k -X POST https://uaa.18-220-96-60.sslip.io/oauth/token --data 'client_id=routing_api_client&client_secret=xxx&grant_type=client_credentials&response_type=token without the --fail first, harmlessly printing the output to the logs if its successful, but helpfully printing the logs if its an error. And then run it again inside UAA_REQUEST=$(curl --fail ...).

This has been done. Closing.


Problem downloading some crops of some images in Chrome, or something

From Ariel:
Here’s a couple examples. No problems making the 16x9 crop, but won’t save using the original crop. Chrome Version 45.0.2454.93 (screenshots attached). Worked fine in Firefox. Just an out-of-date browser?

Seems like this is no longer an issue. Can't replicate it.


Support dependencies file

Is your feature request related to a problem? Please describe.
Having the requirements part of the core app code is an uncommon practice.
Describe the solution you'd like
Nitro to be able to install dependencies from a separate txt file.
Suggestion solution
Was thinking something like:
nitro run https://raw.githubusercontent.com/h2oai/nitro/main/py/examples/hello.py --requirements https://raw.githubusercontent.com/h2oai/nitro/main/py/examples/requirements.txt

(or something better) would be quite useful.
Additional comments
It could immediately enable Nitro to be used for existing projects in conjunction with existing workflows (like a pip package/library).

Having the requirements part of the core app code is an uncommon practice.

I agree it's uncommon, but that's probably because there's no way to do it :-)
The primary purpose of nitro run is to make single-file Python apps possible. A friend pointed out yesterday there's one in the Java world as well. Link  .
nitro run makes it possible to have N apps in the same directory, each self-contained with its own requirements, like this directory: https://github.com/h2oai/nitro/tree/main/py/examples.

It could immediately enable Nitro to be used for existing projects in conjunction with existing workflows (like a pip package/library).

That should already be possible. For example, this can run Wave apps:
# ===
# Setup:
# RUN python -m pip install h2o-wave
# START python -m h2o_wave run wave_todo_list.py
# ===

For external requirements, use:
# ===
# Setup:
# GET https://raw.githubusercontent.com/foo/bar/requirements.txt
# RUN python -m pip install -r requirements.txt
# START python -m h2o_wave run wave_todo_list.py
# ===

Real example:
nitro run https://gist.githubusercontent.com/lo5/fb1609c162c9c20da01fab3501cd7cab/raw/wave_todo_list.py

GET works, thanks!


Settings menu option spawns multiple windows

It doesn’t know one is already open.

Whow...this is an old report...and it's true. I'll look into it with the next release.


Conda doesn't have scanpy>=1.4.5?

https://bioconda.github.io/recipes/scanpy/README.html
Also, slightly related but it seems like Rapids has dropped pip support.

Seems this has been fixed in https://github.com/bioconda/bioconda-recipes/pull/21423.
1.4.6 is available again.


Can I communicate with zookeeper from a wasm filter?

Title: Can I communicate with zookeeper from a wasm filter?
Description:
I want to create an ephemeral node on envoy bootstrap so using a wasm singleton context and do it on proxy_on_context_create seems a good place.
But the ABI only allow me to send http requests to a cluster and zookeeper seems to have a binary protocol over TCP.
Is there any way I could communicate to the zookeeper cluster from the wasm filter?
Also, I saw this example configuration for the zookeeper proxy but I don't understand why the cluster is configured with http
    typed_extension_protocol_options:
      envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
        "@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
        explicit_http_config:
          http2_protocol_options: {}

By the way, how did you implemented the zookeeper proxy? Just looking at source code from the zk client? I couldn't find the protocol documented anywhere in zk docs.

cc @snowp @JuniorHsu
@adamkotwasinski any ideas on this ?

I'm not too familiar with ZK proxy but:

protocol appears to be defined in some spec files (link), also there's some C code generated for client AFAICT
the http stuff could be a mistake :) or actually it could only affect filters that use http (what is not the case in this example, and why would http want to go to zk port)
re original question: I guess either Zookeeper API needs to be translated into WASM layer? might be somehow related to https://github.com/envoyproxy/envoy/issues/15113

@adamkotwasinski

I guess either Zookeeper API needs to be translated into WASM layer

Do you mean adding functions speficic to zookeeper to the proxy-wasm abi? Wouldn't that make the ABI much more complex? If tomorrow we want to talk to Redis from a wasm filter then we would have to add this as well.
Wouldn't be enough with a function at the TCP level instead of HTTP level and then configure the proxies in the listeners?

@adamkotwasinski The ABI seems something much more complex to change but where could I start a conversation about it to see if it is something that makes sense or not?


add Vaadin.Router into the PWA Starter Kit

As a developer using the PWA Starter Kit, I want to get Vaadin.Router in my app by default (instead of pwa-helpers/router.js) so that I have a solid baseline for building production-ready apps with complex routing structures.
DoD:

there is a PR for the PWA Starter Kit repo to use Vaadin.Router
the PR shows that Vaadin.Router makes the code simpler and opens lots of possibilities

The PR is here for internal review before submitting it to the Polymer/pwa-starter-kit repo:
https://github.com/vlukashov/pwa-starter-kit/pull/1


[FEATURE REQUEST] Underfunded category filter or toggle

It would be really helpful to be able to hide all categories that are not underfunded.  It would act as a "needs attention" filter and be very helpful for users who have lots of categories.

+1
I was just thinking of this. It would help us focus on what else needs budgeting whenever we get a paycheck

+feature

We use Trello to track Feature Requests so that users can vote on what they'd like to see next. This is crucial for us since there are so many requests and so little time amongst those of us who work on the Toolkit.
Your feature request has been added here and will need to be manually sorted.
This issue can now be closed.


Decorated class .name is broken in class properties

Follow-up to #1279
Describe the bug
When decorating class, property initalizers get wrong class name.
Input code
@Injectable()
export class TestClass {
	private readonly property = TestClass.name;
	private unitializedProperty;

	constructor() {
		const constructorVariable = TestClass.name;
		this.unitializedProperty = TestClass.name;
	}
}

Output
"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
exports.TestClass = void 0;
var _class1;
var _dec = typeof Reflect !== "undefined" && typeof Reflect.metadata === "function" && Reflect.metadata("design:paramtypes", []), _dec1 = typeof Reflect !== "undefined" && typeof Reflect.metadata === "function" && Reflect.metadata("design:type", Function), _dec2 = Injectable();
let TestClass2 = _class1 = _dec2(_class1 = _dec1(_class1 = _dec((_class1 = class TestClass {
    constructor(){
        this.property = _class.name;
        const constructorVariable = TestClass.name;
        this.unitializedProperty = TestClass.name;
    }
}) || _class1) || _class1) || _class1) || _class1;
exports.TestClass = TestClass2;

Config
{
	"jsc": {
		"parser": {
			"syntax": "typescript",
			"decorators": true
		},
		"transform": {
			"decoratorMetadata": true,
			"legacyDecorator": false
		},
		"target": "es2020",
		"keepClassNames": true,
	},
	"module": {
		"type": "commonjs",
		"strict": false,
		"strictMode": true,
		"lazy": false,
		"noInterop": false
	}
}

Expected behavior
I expect TestClass.name to stay as TestClass.name. Instead, in case of initialized class property, I get _class.name, which throws error at runtime. Initializing property in constructor works as expected. Note that this is happening only if the class is decorated.
Version
The version of @swc/core: 1.2.85

Adding playground link to replicate: https://play.swc.rs/?version=1.2.138&code=H4sIAAAAAAAAA22OQQrCMBBF180pZtlueoFSEVy5cyHux3TASEzCZFqsJXc3arGC3Q1%2FHu9%2F7V0U2LsracGzJWihrKDdwJQapbbLo6wU3YNnAW0xRjhSlN37mlQR2AwoBEzYeWdHCOwDsYxZ9wVrhzdqFrh3Rgxa86DuMOO5stCvRdxr8ZyXZPkngZ%2F8hGzmsX%2F2Qi4m1ivuNTip9ARhTK4pAQEAAA%3D%3D&config=H4sIAAAAAAAAA0XOQQ7DIAwEwL%2F4zAu4Jtf2Dxa4VVPAyHakoIi%2FNyhNe9vD7mh3WDSA36GiKMlI2orhBh6sVdIgr2rgIFJgQWNR8CYrOTDdztgdvInqlFD1jpn%2BDcGiD5Y82ERPDG2%2BmKvzc29kGNHwax5o5rgmGtvx5DgUOGcui0LvH6Z1WjO4AAAA

As far as I can tell this is a faulty integation between Strip and decorators::Lazy.
Without decorators, Strip will be going through visit_mut_stmt_like which preserves the original class name.
https://github.com/swc-project/swc/blob/8a651bc449e077ad0e9c9d87379775d734d11421/crates/swc_ecma_transforms_typescript/src/strip.rs#L620-L623
With decorators, it goes through handle_expr which creates a new _class identifier to name the class.
https://github.com/swc-project/swc/blob/8a651bc449e077ad0e9c9d87379775d734d11421/crates/swc_ecma_transforms_typescript/src/strip.rs#L695-L697
Once inside fold_class_as_decl, it will rename ClassProp right-side identifiers matching the class name.
https://github.com/swc-project/swc/blob/8a651bc449e077ad0e9c9d87379775d734d11421/crates/swc_ecma_transforms_typescript/src/strip.rs#L413-L415
Therefore it will be replaced with _class. I'm not sure why it does that yet.


How to improve multilingual singing voice conversion?

The performance of speaking conversion is good, and the singing conversion  is not ideal. If I do singing voice conversion, can you teach me how to use hifigan, hififan also has a pre-model with the same parameters. Do you have any plans to upgrade the singing conversion next?

Sorry for the late reply. I was pretty busy at the end of my semester. I'm interested in singing conversion with the same architecture, especially with Hifi-GAN. Actually, I already have some idea of how to improve the results. Hifi-GAN does significantly improve the results especially if you fine-tune it. The pre-trained Hifi-GAN likely won't work because the preprocessing is different. I will make my pre-trained HifiGAN available soon with the same preprocessing as this repo.

The pretrained model's preprocessing is different,does it work ?

pretrained hifigan model:
24k | 80-7600 | 2048 / 300 / 1200
my StarGANv2 config preprocess params
preprocess_params:
  sr: 24000
  spect_params:
    n_fft: 2048
    win_length: 1200
    hop_length: 300

Actually after fine tuning for 50k steps from pretrained model I realised something amiss and decided to train Hifigan from the scratch just on my dataset.

What changes have you made to train hifigan, such as config, and the proprecessing of hifigan? @skol101

Guys, it would be best if you'd discuss matters that are about the vocoder training on the appropriate repo, which is https://github.com/kan-bayashi/ParallelWaveGAN and not repurpose closed issues for this. Or you know, discord each other.
Regarding preprocessing changes you can read some of the older issues such as #8 as this is a question that cropped up a few times.


[SPARK-4991][CORE] Worker should reconnect to Master when Master actor restart

When Master akka actor encounter an exception, the Master will restart (akka actor restart not JVM restart) (like the case in SPARK-4989). And all old information are cleared on Master (including workers, applications, etc). However, the workers are not aware of this at all. The state of the cluster is that: the master is on, and all workers are also on, but master is not aware of the exists of workers, and will ignore all worker's heartbeat because all workers are not registered. So that the whole cluster is not available.
In this PR, master will tell worker the connection is disconnected, so that worker will register to master again.

@markhamstra From that page:

Depending on the nature of the work to be supervised and the nature of the failure, the supervisor has a choice of the following four options:

Resume the subordinate, keeping its accumulated internal state
Restart the subordinate, clearing out its accumulated internal state
Stop the subordinate permanently
Escalate the failure, thereby failing itself

It sounds like we want approach 1, resuming the subordinate without losing its state, so I'd be in favor of reworking this PR to use that type of supervision strategy.  I don't think that extending our actors to support restart necessarily makes sense, since it adds a lot of complexity (for instance, I don't think that this PR handles loss of the appInfo or driverInfo data structures).

@JoshRosen your thinking is that Master will be in good shape even though an exception has been thrown?  If you can guarantee that, then resuming the actor while keeping the accumulated state should do the job.  Otherwise, things get more complicated.  Within the lengthy process of handling exceptions thrown within the DAGScheduler (https://github.com/apache/spark/pull/186), we ended up taking the conservative approach of restarting the whole system instead of trying to restart the DAGScheduler actor with fixed or reconstructed state.  I haven't dug into the details of this PR yet, so I can't say for certain, but there are probably lessons to be learned from that DAGScheduler epic PR.
Something else that we'll need to consider at some point if other actors start requiring supervision strategies other than the default is what the overall structure of the supervision hierarchy should be.  Right now, only the DAGScheduler has another level of supervision, but perhaps Spark actors from outside the DAGScheduler should also be handled under one or more levels of common supervision.

@JoshRosen , If we want to use the supervision mechanism. We need to add another actor level as parent of the current Master actor. I don't know if that is suitable.

@liyezhang556520 That's been done already in the DAGScheduler.  If we need another level of supervision for Master or other actors, we should consider whether these actors need separate Supervisors or whether they can be combined in the supervision hierarchy.

@markhamstra , thanks for reminder, I'll update this PR by making a try to introduce the supervision.

I think this has timed out. Would you close this PR for now?


added cursor-pointer

Related Issue

Information about the related issue

Closes: #
Describe the changes you've made

Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update.
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Original
Updated

original screenshot
updated screenshot

Code of Conduct

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

@ayushsgithub I am not able to see any issue you are resolving and I can't see any detail about the pr that you are creating. I would highly suggest to get assigned the issue then commit the changes and create the pr.


Exception 1536

Hello, i have an error exception :
" Exception reçue : Security handler not authenticated, so no encryption key is known. Authenticate first!. N° d'exception : 1536 "
Could you help me to find the error? Missing library on the server?
Thx

This looks like you are trying to import an encrypted PDF document?
What is your code and what do you want to do exactly?

hello,
error of value of password. It's works.
Le sam. 6 juin 2020 à 13:56, Jan Slabon<EMAIL_ADDRESS>a écrit :

This looks like you are trying to import an encrypted PDF document?
What is your code and what do you want to do exactly?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Setasign/SetaFPDF/issues/22#issuecomment-640047938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL6LGGLAQ4VZEFAC7MJGLLRVIVF5ANCNFSM4NV2GOGQ
.

--
Cordialement,
ARMAND Arthur


Replaces the plain ProfilingKey type forward with a process node

Replaces the plain ProfilingKey type forward with a process node which manages the lifetime of the key through the resource pool per application entry point. Creating instances of the type directly immediately leads to a potential memory leak as they get added to an internal static hash set. Just exposing the process node will prevent that from happening all together.
Related issues
#476

As they are static in stride, we could also have them in a static pool, as they are just strings, really. unfortunately, they don't have a dispose, so they will always be in the static HashSet, once created. the easiest way would be to get access to the HashSet with reflection and just add a GetOrAdd extension method. that would also make it stateless again.


two question want to ask , thank you.

quesion1 :
i created a new volume and attach to vm which OS is ubuntu, i can see it create and attach
to vm successful from web_ui, but i login in the vm and use 'fdisk -l' to see all the
volume , i can't see the volume , but after a moment i can see it , why?
quesion 2:
How the manager cluster work? The manage cluster suport HA?
I installed a zstack cluster which have two manager node in accordance with your instructions,  I think the multi management node is to increase the reliability of the cluster, so i login in web_ui by manager node2 ip and port , but i can't login in, the log info on manager node2 is like this :
log_path :  /var/log/zstack/zstack-ui.log
add request[id:dd04a6920eea45078db39ded43f8a5fc]
DEBUG:zstack_dashboard.web:add request[id:dd04a6920eea45078db39ded43f8a5fc]
sent message: {"org.zstack.header.identity.APILogInByAccountMsg": {"headers": {"replyTo": "zstack.ui.message.c7c8dde46f73462ba3ea06ae6d17ae20", "noReply": "false", "correlationId": "dd04a6920eea45078db39ded43f8a5fc"}, "serviceId": "api.portal", "password": "b109f3bbbc244eb82441917ed06d618b9008dd09b3befd1b5e07394c706a8bb980b1d7785e5976ec049b46df5f1326af5a2ea6d103fd07c95385ffab0cacbc86", "id": "dd04a6920eea45078db39ded43f8a5fc", "accountName": "admin"}}
DEBUG:zstack_dashboard.web:sent message: {"org.zstack.header.identity.APILogInByAccountMsg": {"headers": {"replyTo": "zstack.ui.message.c7c8dde46f73462ba3ea06ae6d17ae20", "noReply": "false", "correlationId": "dd04a6920eea45078db39ded43f8a5fc"}, "serviceId": "api.portal", "password": "b109f3bbbc244eb82441917ed06d618b9008dd09b3befd1b5e07394c706a8bb980b1d7785e5976ec049b46df5f1326af5a2ea6d103fd07c95385ffab0cacbc86", "id": "dd04a6920eea45078db39ded43f8a5fc", "accountName": "admin"}}

github is not a good place to ask questions. If you speak Chinese, please join the QQ group 410185063 where people dicuss ZStack. If you only speak English, please ask questions in Google group https://groups.google.com/forum/#!forum/zstack


Move tonic into the Flutter engine.

Tonic was moved into its own repository because it is used by some Fuchsia targets. However, it seems to have no current owner. Also, because of its location outside of the Flutter buildroot, none of the test harnesses in Flutter can be used to test Tonic. Due to this and the lack of clear ownership of the codebase, all current test targets are disabled. Existing files in tonic containing a few tests are never compiled and contain references to code that has long gone away or been refactored. This lack of clarity has also made it so that new code that ought to go into tonic has found its way in other targets that have clearer code ownership and well defined test harnesses (usually //flutter/runtime and includes stuff like launching the VM and interacting with isolates).
We should consider moving Tonic back into Flutter and make //flutter/runtime deal with just the specific Flutter bits of interacting with Dart. Existing targets in Fuchsia can use tonic from Flutter. If this is not desirable, Tonic can remain as is and the Flutter engine can fork it (//flutter/tunic?)

@jason-simmons, @cbracken, @zanderso, @abarth: Thoughts, go/no-go?

What about moving it into the Dart VM?

Putting it in Dart VM would work for all the scenarios we are currently considering for Flutter-related code in Fuchsia.

I am assuming the premise here is that all embedders of the Dart VM would need a library like this to access to the Dart API surface area. Does it have to be tonic or is it just sufficient to have a C++ library that exposes the Dart API surface? We can discuss this offline.

From my perspective, it wouldn't need to be tonic.  It would just need to be sufficient to satisfy all current clients of tonic so that we could delete tonic in favor of it.

Has there been any progress on this issue either way? I think I found an issue in tonic, but the lack of a clear home for it means I'm not sure what issue tracker to file it under.
My 2c: I think moving tonic into Dart makes sense.
(FWIW, issue is that I think the memmove call in DartConverter<Uint16List>::ToDart is mixing up element counts with byte counts, because it was copied from the Uint8List implementation that didn't have to distinguish that.)

https://github.com/flutter/engine/pull/15895
Looks like we could close this issue?

Indeed we can. Thanks!


Remove styles.marker from Marker and MarkerLeft styles

styles.marker does not exist
The inclusion of this causes unpredictable behaviour when setting the markerStyle prop

Thank you! Will confirm and merge ASAP


Intermittent connect "ETIMEDOUT" error in DownloadPackage task v0.1.10

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server -  TFS onprem

If using TFS on-premises, provide the version: Task version 0.1.10

Agent - Private agent

Issue Description
DownloadPackage build task fails around 1% of the time where it raises a fatal "Error: connect ETIMEDOUT" message and thus causes the deployment job to fail and not complete. Here is a sample log.
2018-08-30T18:14:59.3183565Z ##[error]Error: connect ETIMEDOUT <IP_ADDRESS>:443
2018-08-30T18:14:59.3200227Z ##[section]Finishing: Download artifact - MyDevOps (Package Management)
How to reproduce:

Create a build to create a NuGet package and upload it to your organization's "Package Management" feed.
Create a Release Pipeline and configure an Artifact using this NuGet package from your organization's "Package Management" feed.
Run releases and see intermittent exceptions. I can provide some specific examples in our organization.

DownloadPackage task needs to handle these intermittent failure from server by implementing a retry logic around the network calls.
Task logs
Logs:
2018-08-30T18:14:37.1732569Z ##[section]Starting: Download artifact - MyDevOps (Package Management)
2018-08-30T18:14:37.1739572Z ==============================================================================
2018-08-30T18:14:37.1739897Z Task : Download Package
2018-08-30T18:14:37.1740208Z Description : Download a package from a Package Management feed in VSTS or TFS. Requires the Package Management extension.
2018-08-30T18:14:37.1740521Z Version : 0.1.10
2018-08-30T18:14:37.1740725Z Author : ms-vscs-rm
2018-08-30T18:14:37.1740984Z Help : Needs Package Management extension to be installed
2018-08-30T18:14:37.1741274Z ==============================================================================
2018-08-30T18:14:38.0775702Z SYSTEMVSSCONNECTION exists true
2018-08-30T18:14:59.3183565Z ##[error]Error: connect ETIMEDOUT <IP_ADDRESS>:443
2018-08-30T18:14:59.3200227Z ##[section]Finishing: Download artifact - MyDevOps (Package Management)
Error logs
[Insert error from the logs here for a quick overview]

@omeshp  This is the bug reported by a customer. Looks like the task needs some retry logic around network calls.

Thanks @shubham90 we will take care of adding retries.


feat: add center to/in anchored region horizontal and vertical position

🙋 Feature Request
We are running in to a problem where it the enum value seems to be missing for centering the fluent anchored region.

🤔 Expected Behavior
For our usecase, we would want to have the HorizontalPosition to include HorizontalPosition.Center as well as VerticalPosition to include VerticalPosition.Center

😯 Current Behavior
Today this value does not exist.

💁 Possible Solution
It seems to me that it should be a simple enum to be updated from in the horiztonal position file
and the vertical position file

🔦 Context
We have solved this issue today by invoking a javascript method doing the following:
element.setAttribute("horizontal-default-position", "center");

💻 Examples

This will be available in v3 release (not in RC1 yet).
See 'Open callout 2' in the Popover examples and 'Toggle position and size' in the AnchoredRegion examples for usage.


Add support for CORS

Was hoping to use affirmations.dev as a test API in an upcoming Angular article. Please consider merging this PR.
Thanks!

@annthurium any way we could get this PR merged? Would be greatly appreciated! Thanks 💟

Hi @bekahlundy 👋, I think you can install this directly via the my fork. See https://stackoverflow.com/a/17509764/2993077 for more info.


Please implement internal chproxy url for health checks

Hi,
checking if chproxy is still alive would be much easier if it would have an internal status/healph page, which returns 200 if everything is okay. Like clickhouse anwers with 200 on / and /ping.
Thanks,
bernd

Hi @bzed
The common way to check app health is to query /metrics endpoint.
Also if you use Prometheus for your application monitoring you can get more insights of chproxy state. See this link for details.

Oh thanks a lot, somehow I completely failed to see /metrics in the documentation. Sorry for the noise!


Update Slimmer and breadcrumbs from Slimmer::GovukComponents

The feeback app currently uses set_slimmer_dummy_artefact to make the
contact page show breadcrumbs.
This behaviour is deprecated in favour of using the breadcrumbs
component: http://govuk-component-guide.herokuapp.com/components/breadcrumbs
Trello:
https://trello.com/c/6Km63K2Z/402-feedback-app-use-component-for-breadcrumbs-and-upgrade-slimmer
render_views is a workaround for a known issue https://github.com/alphagov/slimmer/issues/170

👍 nice


no window

just now I installed Eqmac, but I realized that sometimes principal window doesn't appear.
I click on icon on my bar but window doesn't get out. If I click with right button, appear option, but sometimes with left click doesn't appear principal window to set up eq.

I'm sorry, I uninstalled it cause music don't work no more. Music was locked or silenced. I uninstalled.

facepalm

Hey everyone. Excuse me for the lack of updates. I have been really busy on the new version of eqMac. I am happy to announce an open beta release.
You can download it here: https://eqmac.app
There are a lot of known bugs that I could not fix just yet:

Driver not installing from the first try. Sometimes need to restart eqMac a couple times.
Complex Device switching logic is not perfect (for example when switching off the device that's currently playing, plugging in new device etc.)
UI takes long to load (a lot can be done to improve that)
UI dimensions are not synching properly
There's a noticeable audio delay in the playback, so not suitable for video yet (I know where the problem lies just haven't had the time to fix yet)
Sometimes the playback doesn't start, in that case please try to switch the output to the device you want and eqMac should try and build the audio pipeline again.

So as you can see there's still some work to be done but at least it's a completely modern tech stack that I am fully willing to work on: 100% Swift, User Space driver and a Web UI, instead of C++, Kernel Drivers. As I said, should work on Catalina and should not have any pesky ear drum blasting volume bugs (at least I didn't come across any).
I'm open to feedback and issue reports here: https://github.com/bitgapp/eqmac
That repo will become the main repo for eqMac and this repo will be archived eventually.
And yes it's called just eqMac, not eqMac3 :) And it will stay that way forever.

Hey everyone 👋
I will be open sourcing the new version of eqMac, therefore, I am closing this issue and repository as I will be transfering nodeful/eqMac2 repo to bitgapp/eqMac
Please bear with me for the next couple of days as I setup that new repo. The eqMac2 code will be living in the old-eqMac2 branch if anyone is interested in referencing it for whatever reason.
Please try out the new version and report bugs to the new repo.
Thanks for using eqMac.


crash when an interface has a null address

IPFinder::getIPs will segfault if any of the interfaces has a null ifa_addr pointer. I ran into this when running with a tunnel device; after trying to figure out why one of the tunnel devices had a null ifa_addr, I noticed that the getifaddrs man page says that it indeed can be null. In any case it is easy to guard against. With this fix, it runs as expected with the tunnel device.
@@ -120,6 +120,9 @@ bool IPFinder::getIPs(std::vector<info_IP>* vec_name )

        for (ifa = ifaddr; ifa != NULL; ifa = ifa->ifa_next)
        {
+               if (ifa->ifa_addr == NULL)
+                       continue;
+
                family = ifa->ifa_addr->sa_family;

                if (family == AF_INET)

For reference, here are the interfaces when it fails (this is from a little program that calls getifaddrs and prints the list returned). This network namespace has only a loopback and one tunnel device.
ifa=0x14d6ad0 ifa_name=lo ifa->flags=0x00010049
 ifa_addr=0x14d6b08 sa_family=AF_PACKET
 ifa_netmask=(nil)
 ifa_dstaddr=0x14d6b50 sa_family=AF_PACKET
 ifa_data=0x14d6e68 ifa_next=0x14d6b88

ifa=0x14d6b88 ifa_name=tun1 ifa->flags=0x000110d1
 ifa_addr=(nil)
 ifa_netmask=(nil)
 ifa_dstaddr=(nil)
 ifa_data=0x14d6ec4 ifa_next=0x14d6c40

ifa=0x14d6c40 ifa_name=lo ifa->flags=0x00010049
 ifa_addr=0x14d6c78 sa_family=AF_INET
 ifa_netmask=0x14d6c9c sa_family=AF_INET
 ifa_dstaddr=0x14d6cc0 sa_family=AF_INET
 ifa_data=(nil) ifa_next=0x14d6cf8

ifa=0x14d6cf8 ifa_name=tun1 ifa->flags=0x000110d1
 ifa_addr=0x14d6d30 sa_family=AF_INET
 ifa_netmask=0x14d6d54 sa_family=AF_INET
 ifa_dstaddr=0x14d6d78 sa_family=AF_INET
 ifa_data=(nil) ifa_next=0x14d6db0

ifa=0x14d6db0 ifa_name=lo ifa->flags=0x00010049
 ifa_addr=0x14d6de8 sa_family=AF_INET6
 ifa_netmask=0x14d6e0c sa_family=AF_INET6
 ifa_dstaddr=(nil)
 ifa_data=(nil) ifa_next=(nil)

Thanks for the heads up John, your fix is coming with the next release :)

Here you go @2e8eb48b9b9b4da5d97e488cce8be79f67265532


[FEATURE] MathML Core Parsing

Are there any plans to support MathML Core (https://www.w3.org/TR/mathml-core/) as a possible input for MathLive?
Also, sorry if this isn't the right place to put this.
Thanks!

At the moment there are no concrete plans for this, but this is something that could be supported in the future. If someone were interested in contributing this to the project they should get in touch.
Could you share more about your specific use case for this feature?

@aMadReason What would be the use-case for this?
In case anyone needs it and wants a relatively simple solution, one option would be to intercept a paste event and run the MathML through an off-the-shelf MathML to LaTeX converter.


feat: qr code in presentation mode

Description
This PR resolves MOPLAT-445

PR Checklist

[x] I tested my changes on iOS and Android.
[x] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Need help with something? Have a look at our docs, or get in touch with us.

nice. i only had one other thought: obviously non-blocking, but how about we slap our logo in the middle of that QR code? 🤩

ha! No possible with this library, I don't think

if you wanna try, we could totally just overlay the artsy logo on top, in the middle ;), that's what the QR redundancy data is for :D

I'll go ahead and make a PR to revert these changes as it is breaking the tests. Context here:
https://artsy.slack.com/archives/C02NAJ2CGLW/p1664965136471759


Updated OpenAI model to GPT-4 and introduced new rules

Do not mention SQL in your response, you are an AI expert, you don't need to mention SQL.
There is no REGISTRATION activity type, you can use the USER_ID column to find the number of registrants.
Do not use the word "query" in your response, you are an AI expert, you don't need to mention query.

right response form both sides


istanbul-lib-instrument v1.3.1 breaking change

The istanbul-lib-instrument last release (v1.3.1) affected the istanbul-instrumenter-loader package with the error message (No changes in my codebase):
PhantomJS 2.1.1 (Linux 0.0.0) ERROR
SyntaxError: Cannot declare a parameter named 'area'  in strict mode
Removed the package from postLoaders in Webpack configuration.
Was working perfectly on istanbul-lib-instrument v1.3.0 release

nuff said... please report this to them. I think it's related to some specific peace of code that you have, because the only changes were in src/visitor.js

I already reported to them. There is definitely ZERO changes in my source code.
Thanks

so what was the bug?

I didn't receive anything yet, and don't use it in the meanwhile because it's breaking a lot in my TypeScript projects.
But I assume they figure it out from the discussion out there :smiley:


finding the team's position in the leaderboard

possible solutions :

adding a search functionality in leaderboard page can help folks search their team's position easily
highlight one's team in the table
scroll to one's own team when leaderboard page is opened.

Implementing one of the above solution can easily let folks find their team position in the leaderboard.

Can you work on it? :)

Yes. I will, please assign to me @nevo-david

Can you please assign me this issue.

yeah finding it quite difficult to search our team position

I think this issue has never been worked on. I want to work on this @nevo-david, as a part of HackSquad 2023.


Fix layout issues on Safari

On Safari some componets are not the right size.

find out if this is needed for Milestone v1.0


partitioned table "copy from" performance issue

CrateDB version: 2.3.0
JVM version: 1.8.0_151
OS version / environment description: CentOS Linux release 7.4.1708 (Core)
Problem description:
When I use "copy from" query for bulk inserting on partitioned table, there is big performance gaps compare to normal table.
with bulk_size option on normal table, there is big performance improvement. (case 1, 3)
but on partitioned table, inserting performance is almost equals. (case 2, 4)
I think there is some problem. for example, bulk_size option is not working on partitioned table.
To improve inserting performance on partitioned table, I tested many ES options.
But there is nothing outstanding, even there are enough resources(CPU/MEM).
Please check this out, and let me know some options to improve.
Thanks.
My test cases

Case 1: normal table without bulk_size (elapsed: 63.3s)

Case 2: partitioned table without bulk_size (elapsed: 56.4s)

Case 3: normal table with bulk_size=30000 (elapsed: 40.5s)

Case 4: partitioned table with bulk_size=30000 (elapsed: 55.1s)

Steps to reproduce:

Use case:
Feature description:

hi @nicetip, thanks for reporting. we'll look into that.

I think the performance difference you're seeing is because with partitioned
tables the partitions have to be created if they don't exist already, that
takes up some time as well.
How many partitions are being created in your case? One option might be to tune
the schema to have less partitions.
If you've more than 1 node, another option would be to set number_of_replicas to
0 for the import (if this is an initial import)

I tested it with single node environment. So I think number_of_replicas is not matter to me.
And Following is my hardware specs.
CPU: 2 CPU of "Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz" (20 cores/40 threads)
Memory: 128GB
Disk: SSD 1TB
Crate: 2.3.0 (last week version)
And last test case (Case 4) was just 1 partition.

So I tested it again by pre-inserting a record to create partition, before bulk inserting.
Twice test elapsed 52.8s, 57.4s. it is almost equal to "Case 4" result.

So, I think partition creating time is not a matter for me.
And Next is screenshot of "top" command while bulk inserting.
there are enough resources. So I hope it could comsume more eagerly.
Thanks.

So I hope it could comsume more eagerly.

Managing the resources can be a bit tricky. We also have to make sure that a
COPY FROM doesn't exhaust a cluster too much so that other operations like
SELECT, INSERT, etc. become unresponsive.

I think there is some problem. for example, bulk_size option is not working on partitioned table.

The bulk_size is definitely used correctly. I've double checked that.

To improve inserting performance on partitioned table, I tested many ES options.

Did you also try to adjust the thread_pool.bulk.size ? (See https://crate.io/docs/crate/reference/en/latest/configuration/cluster.html#settings-for-fixed-thread-pools)
Changing the number of the shards could also help (though make sure not to
create too many shards - that will affect performance badly, especially if you
will end up with many partitions in the long run)
Also, I'd recommend to stick to 2.1 or 2.2 for now. Master currently has a
performance regression that we were able to observe with COPY FROM.

I've done test with thread_pool options also.
And I did it again to recheck.
Look Followings.

thread_pool.bulk.size: 33  // 32 (maximum processors limit) + 1

thread_pool.bulk.size: 33
thread_pool.bulk.queue_size: 200

thread_pool.bulk.size: 33
thread_pool.bulk.queue_size: 2000

processors: 80
thread_pool.bulk.size: 80

processors: 80
thread_pool.bulk.size: 80
thread_pool.bulk.queue_size: 200

processors: 80
thread_pool.bulk.size: 80
thread_pool.bulk.queue_size: 2000

And I did with these options and system configs.

index.refresh_interval: 30s
indices.memory.index_buffer_size: 30%
multiple data.path on SSD
ZFS on SSD

Every test's performance improvement is smaller than using bulk_size on normal table. (Case 1, 3)
As I did test before, I think partition creating time is not takes so much.
And I think It takes not so much time to guess which partition should be used.
So I thought some bug exists when bulk inserting on partitioned table.
If you think it's not a issue, you can close case. it's ok.
Thank you for your concern.

If you think it's not a issue, you can close case. it's ok.

I doubt that it is, but just to be sure - could you maybe provide us with the data file you used so that we can take a closer look?

OK. After config some firewall rules, I will send you login info of our test sever at tomorrow morning. Now I am offline. Thank you.

Please let me know your private email address.

Email is mathias {at} crate.io
The data file would be sufficient - no need for any server access.

Actually nevermind - I've run into the same/similar issue while investigating something else

I think I've figured out the cause of the performance difference.
For partitioned table we're doing some extra work that involves removing the
partitioned values from the source data because they shouldn't be indexed.
I think that's currently more expensive than it has to be, so I've marked this
as performance enhancement for now.

Good to hear that.
Then, I think I don't need to send data file.
In fact, that's code generated duplicated records. nothing worth.
Then, good luck and thank you.


[v2.7.0] twister: Miss sn option to stm32cubeprogrgammer runner

Describe the bug
To run CI test on v2.7.0 branch with nucleo_wb55rg and b_u585i_iot02a boards, a stm32cubeprogrammer option is missing in matching twister runner.
It was added on v3.0.0 (https://github.com/zephyrproject-rtos/zephyr/pull/41115)

#44322 merged


fix: add a count around the deprecation notice for var.service_endpoints so it only triggers if variable is used

Description
add a count around the deprecation notice for var.service_endpoints so it only triggers if variable is used
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[x] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

[ ] The PR references a GitHub issue.
[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

I think I just bumped into the issue this PR has on another branch.
I think you need to add this to resolve the issue:
diff --git a/examples/complete/main.tf b/examples/complete/main.tf
index cc26c9e..e513500 100644
--- a/examples/complete/main.tf
+++ b/examples/complete/main.tf
@@ -101,7 +101,6 @@ module "cbr_zone" {

 # Create COS instance and Key protect instance.
 # Create COS bucket-1 with:
-# - Retention
 # - Encryption
 # - Monitoring
 # - Activity Tracking
@@ -118,6 +117,7 @@ module "cos_bucket1" {
   key_protect_key_crn                = module.key_protect_all_inclusive.keys["${local.key_ring_name}.${local.key_name}"].crn
   sysdig_crn                         = module.observability_instances.sysdig_crn
   activity_tracker_crn               = local.at_crn
+  retention_enabled                  = false
   bucket_cbr_rules = [
     {
       description      = "sample rule for bucket 1"
@@ -178,7 +178,6 @@ module "cos_bucket1" {

 # We will reuse the COS instance, Key Protect instance and Key Protect Key Ring / Key that were created in cos_bucket1 module.
 # Create COS bucket-2 with:
-# - Retention
 # - Cross Region Location
 # - Encryption
 # - Monitoring
@@ -196,6 +195,7 @@ module "cos_bucket2" {
   create_cos_instance      = false
   existing_cos_instance_id = module.cos_bucket1.cos_instance_id
   key_protect_key_crn      = module.key_protect_all_inclusive.keys["${local.key_ring_name}.${local.key_name}"].crn
+  retention_enabled        = false
   bucket_cbr_rules = [
     {
       description      = "sample rule for bucket 2"

To avoid creating the buckets with retention, to enable the key to be deleted.
They will still be encrypted with the key, they will just be deletable and the dependancy tree should make sure the buckets are deleted before the key.

:tada: This PR is included in version 5.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


One login implementation

Context
This is a POC, this PR won't be merged in main but a lot of the code here will be split out in different PRs once we get the green light from product.
This adds one login integration for the candidate path. The magic link implementation is not visible to the candidate.
The candidate will be redirected to one login test env where they can create an account and we will log them in apply. They can also recover their old account if their previous candidate email doesn't match the one login email.
Agreed technical flow(bottom diagram), this can change though
https://lucid.app/lucidspark/3647e5d9-5075-45d4-abd3-088ee4323fc9/edit?invitationId=inv_8027d1a6-8607-4cb9-a43e-7dc1a8975f38&page=0_0#
Changes proposed in this pull request

New columns and tables.
Candidate will only have 1 OmniAuthLogin and 1 AccountRecoveryRequest
They are used to auth the user and to allow them to recover their account
The OmniAuthLogin holds the information coming back from one login
recovered and dismiss_recovery columns are there mostly for the Recover account banner

erDiagram
    Candidate ||--o{ OmniAuthLogin : has_one
    Candidate ||--o{ AccountRecoveryRequest : has_one
    Candidate {
      string email_address
      boolean recovered
      boolean dismiss_recovery
    }
    OmniAuthLogin {
      string token
      string email
      id candidate_id
    }
    AccountRecoveryRequest {
      int code
      string previous_account_email
      id candidate
    }

https://github.com/user-attachments/assets/d6dc9fc9-8530-4088-8f7d-f3cfbfb21d38
Guidance for review
Go on review app and try to login as a candidate.
Create a one login account and login.
Click on Recover account
Add your email gov/dfe address with a +1 before the @ so<EMAIL_ADDRESS>You should get an email with a unique code
Enter that code.
You should be logged in.
Try to break this, I have created 3 emails for our team members to recover, so +1,+2,+3
Try putting +100
Put the wrong or a bad email address
Create a new one login account and try to claim it after.
Go nuts
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault
[ ] Inform data insights team due to database changes
[ ] Make sure all information from the Trello card is in here
[ ] Rebased main
[ ] Cleaned commit history
[ ] Tested by running locally
[ ] Add PR link to Trello card

 Spike the one login technical flow


Upgrade black

Black 20.8b1 broke when click removed an internal function it relied on.
Switching to the latest stable release fixes this.

Thanks you!


Snap application window to fancyzone closes application

Environment
Windows build number: [run "ver" at a command prompt]
version 10.0.18363.720
PowerToys version:
PowerToy module for which you are reporting the bug (if applicable):
v0.17.0

# Steps to reproduce
When trying to snap a window of a application to fancyzones it closes the application (CaseView)
<!-- A description of how to trigger this bug. -->

# Expected behavior
The expected behavior --> window snap to selected fancyzone
<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

# Actual behavior
The application closes completely
<!-- What's actually happening? -->

# Screenshots

<!-- If applicable, add screenshots to help explain your problem. -->

What application?

Does this still happen on a newer version of PowerToys such as .19 or .20?

The problem got resolved in version .18/.19.
Thanks!