Semi transparent upper border border - is this by intention?

The most recent VS Code version displays a semi transparent upper border:

I feel it quite irritating when I open VS Code. It raises a feeling in me of a brittle, unstable version, rendering outside its intended rendering buffer memory.
Is this upper semitransparent border by intention?

VS Code/OS Version:

Version: 1.58.2 (user setup)
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Datum: 2021-07-14T22:10:15.214Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
Betriebssystem: Windows_NT x64 10.0.19043

@SetTrend can you confirm if this is still happening?
@deepak1556 electron related perhaps?

@SetTrend can you share your display arrangement and configuration.

@sbatten:
Yes, I can confirm it's still happening:

@deepak1556:
I'm running Windows 10x64, 1920*1200 pixels, single screen.
Here's a (truncated) DxDiag log file from my machine:
DxDiag.txt

This is addressed in recent versions, unable to repro with latest stable 1.74


agent: timestamp task status on update

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>cc @aluzzardi

LGTM

[Current coverage][cc-pull] is 55.10%

Merging [#1197][cc-pull] into [master][cc-base-branch] will increase coverage by 0.06%

@@             master      #1197   diff @@
==========================================
  Files            77         77
  Lines         12189      12125    -64
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6708       6681    -27
+ Misses         4562       4529    -33
+ Partials        919        915     -4

[][cc-pull]

Powered by Codecov. Last updated by [38857c0...3674e93][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/38857c06dafcf939a56d2650d8e0011b5aace384...3674e9330c0d78076c20849b71b74fb26133439b?src=pr
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/1197?src=pr


Compile python requirements

Automated changes by create-pull-request GitHub action

Actual breaking changes!
pyarrow-stubs update, with no pyarrow update. A little odd looking. I'll poke around


Outlined text field on top of bottom nav

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Bottom navigation should top of the Input label outlined
Current Behavior
Input label outlined is on top of bottom navigation. I think this is just zIndex issue

Your Environment

Tech
Version

Material-UI
v3.2.1

React
v16.5

Browser
chrome

@stefensuhat I think that we can apply the same fix as in #13122 to the FormControl component. Do you want to give it a try? :)

@stefensuhat @oliviertassinari, I would be happy to tackle this if you would like

@drkohlipk that will be great! :D . I'm in the middle of project so can't PR and test at the moment.

👍

I tested setting the z-index: -1 for the TextField component and it works.
Although, when you read the spec of the BottomNavigation component, you don't see the option of using it fixed in the page.
When the user fixes the BottomNavigation on the page, they are changing the way this component was designed to be used. So I wonder if the user shouldn't also be responsible for making sure this component is going to cover all the other components rendered behind it.
What do you think?

@nicolasiensen I was thinking of using z-index: 0, in order to minimize the impact of the component in the stacking context.

Just created a PR to fix this issue, apologies for it taking me about a week!

This issue is still happening for me


for_each_field_impl: use fold expressions if possible

This makes empty structs work with MSVC in that case.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
338

Relevant Lines:
338

💛  - Coveralls

Many thanks for the PR!


Add rel="noopener noreferrer" for tab nabbing

As explained here: https://www.owasp.org/index.php/Reverse_Tabnabbing

Codecov Report

Merging #1161 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop   #1161   +/-   ##
=======================================
  Coverage       71%     71%
=======================================
  Files           62      62
  Lines         3032    3032
  Branches       424     424
=======================================
  Hits          2153    2153
  Misses         731     731
  Partials       148     148

Continue to review full report at Codecov.

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

Bump, a simple and tiny security improvement...

thank you very much for the contribution @simonweil

Thank you!


"Can not read property 'join' of undefined" when using Inputmask.format

I'm getting the error "Can not read property 'join' of undefined" when using Inputmask.format with the following configuration:
{
    alias: 'currency',
    digits: 3,
    digitsOptional: false,
    integerDigits: 4,
    prefix: '',
    groupSeparator: '.',
    radixPoint: ',',
    groupSize: 3,
    unmaskAsNumber: true,
    autoUnmask: true
}

Example in: https://stackblitz.com/edit/js-tbdmxj. Typing a value such as 5000.100 the above error occurs.
This error occurs on this line. During the debug, I realized that the "buffer" property of the "maskSet" object has an array, unlike the "_buffer" property, which is undefined. Is this right?
I did some testing by changing the above line to use "buffer" instead of "_buffer" and the example code worked as expected.

@salvadormarcos ,
Can you try again with the latest beta

It's working fine, thanks!


param_size of searched model is too heavy

@quark0  hi, firstly, thanks for your work , I'm really interested in Darts.
But I have some confusion about my reproduce result. I found that the network I searched was too big compared to the network released in Darts. The param_size of my result model are generally 8M， while released mode‘s is nearly 3M.
Could you tell me the reason why the results are different. Or I just should continue to search for more networks.
Thanks

@xingyueye : can you teach me how to run DART from the bigining?


Layer Panel (Opacity)

Fixes #283
Adds a new MediaStyle panel which allows setting opacity.

Any thoughts on if opacity for Media should be displayed in edit mode as well?
Currently an image in edit mode looks like this:

As can be seen then the area around the visible box already has opacity, not sure how applying opacity to the visible area would work out and if it would look OK.
Thoughts?
cc @dvoytenko @pbakaus @samitron7

@miina It's a very edge case thing. We probably don't expect users to change the opacity of the image/video in edit mode but if they wanted to we should allow it (let's do this to avoid applying additional rules to edit mode). Double click on an image in Google Slides or Keynote. Once you're in edit note, you can also change the opacity to the image. Essentially, this will down the opacity of the entire image and in the mask.

Should be ready for re-review with new style applied to Media opacity specifically.

@barklund @dvoytenko @swissspidy This should be ready for review (again).

@miina Could you perhaps resolve the newly popped up merge conflicts?

@swissspidy Done!


Upgrading VisualStudio Extension -.vsix files not created

Describe the bug
When trying to upgrade a Visual Studio Extension the .vsix file is not created.
To Reproduce

I cloned the directory tree containing Lee01MacrosEX.csproj  before running the upgrade.

I upgraded the project Lee01MacrosEX.original.csproj (attached in csproj.zip) successfully creating Lee01MacrosEX.upgraded.csproj (attached in csproj.zip
csproj.zip.
(Note that I added '.original' and .'upgraded' for submitting this issue.)
The 2 files are identical as regards which files are included in the project. The directory structure is very unorthodox and is the reason for the large number of 'Remove="..."' elements in the .upgrade version.

I compiled the upgraded project (BuildLog.txt contains 'detailed' build-output) and noticed that the .vsix file is missing from the dir specified in
d:\tools\vscommon\bin
It is also missing from the bin\release\net7.0-windows under the .csproj-file (shown in dirnet70.txt).
The dll IS the upgraded version.

Further technical details
BuildLog.txt
dirnet70.txt
dirvscommon.txt
sdks.txt

Windows version: Windows 10 1909 64-bit
Include the output of dotnet --list-sdks (sdks.txt)
upgrade-assistant --version -I downloaded the VS extension via Visual Studio on 4/1 @7am Hong Kong time (I think that is 4pm 3/31 US Pacific time.)

Attached is a file that I should have attached to the original message - BuildLog-PreNet70.txt - with the 'detailed' MSBuild output from the original project (not upgraded) that clearly shows all the .vsix processing including the .vsix-file creation.
Two things I think I should have mentioned in my original message.

Because I cloned the project before I ran the upgrade I did an 'in place' upgrade - but I don't think that has any bearing on the problem
BuildLog-PreNet70.txt.

After I posted my original message I realized that possibly doing a Build by doing a Rebuild would fix the problem. I did so with the same results - no .vsix-file - and the Log is substantially the same as the BuildLog.txt file I attached in my original message, so I did not upload a new one.

On further examination of BuildLog.txt I noticed that there was no mention of 'VSCTCompiler' or 'VSCT' as there is in BuildLog-PreNet70.txt.
It looks like the upgraded .csproj-file is missing a PropertyGroup item or (I hope unlikely) the SDK-version doesn't support building Visual Studio Extensions.

it can build them but you may need something like this at the end of the csproj file:
<Import Sdk="Microsoft.NET.Sdk" Project="Sdk.targets" />
<Import Project="$(VSToolsPath)\VSSDK\Microsoft.VsSDK.targets" Condition="Exists('$(VSToolsPath)\VSSDK\Microsoft.VsSDK.targets')" />
<PropertyGroup>
	<GetVsixSourceItemsDependsOn>$(GetVsixSourceItemsDependsOn);IncludeNuGetResolvedAssets</GetVsixSourceItemsDependsOn>
</PropertyGroup>
<Target Name="IncludeNuGetResolvedAssets" AfterTargets="GetVsixSourceItems">
	<ItemGroup>
		<VSIXCopyLocalReferenceSourceItem Include="@(ReferenceCopyLocalPaths)" />
	</ItemGroup>
</Target>

It is worth noting while you can build vsix packages you lose some of the other integrated VSIX debugging and project property UI.


Add LiteDb.Migration to readme

Hey, i have created the "LiteDB.Migration", it makes schema changes easier. Hope you like it :)
https://github.com/JKamsker/LiteDB.Migration/

Thanks @JKamsker, nice work!


Parsing Error: DeprecationError: orginalKeywordKind

Hi, After installing ESLint and following the steps mentioned in ionic-team/eslint-config, an unexpected error message is displayed.
error message:

[!WARNING]
Parsing error: DeprecationError: originalKeywordKind has been deprecated since v5.0.0 and can no longer be used. Use identifierToKeywordKind(identifier) instead.

Hi, After installing ESLint and following the steps mentioned in ionic-team/eslint-config, an unexpected error message is displayed.
error message:
Warning
Parsing error: DeprecationError: originalKeywordKind has been deprecated since v5.0.0 and can no longer be used. Use identifierToKeywordKind(identifier) instead.

Exact same issue atm.

After creating new Issue as Is there possible to support "eslint >= 8". I found the problem.
I understand that TypeScript v5 deprecated the usage of originalKeywordKind. On the other hand, the @ionic/eslint-config version v0.3.0 supports @typescript-eslint/eslint-plugin and @typescript-eslint/parser version v4.33.0, with ESLint peer dependency being<EMAIL_ADDRESS>You may need to update your ESLint configurations to align with the new TypeScript and ESLint versions for compatibility.


Missing a Logger.httpRoutes for AuthedRoutes[F]

I have predominantly AuthedRoutes in my HttpApp and would like to selectively toggle certain logging flags (logBody, most importantly) on and off for specific routes.
val logHeaderOnly = Logger.httpRoutes( // ...
val logAll = Logger.httpRoutes( // ...

val r1 = HttpRoutes.of[F] { // ...
val r2 = HttpRoutes.of[F] { // ...

logHeaderOnly(r1) <+> logAll(r2)`

works perfectly, but only becauser1 and r1 are HttpRoutes. However, I cannot plug in an r1 or r2 of type AuthedRoutes since the methods in the org.https.server.middleware.Logger object only take HttpApp or HttpRoutes as arguments. Supplying a Kleisli[OptionT[F, *], ContextRequest[F], Response[F]] yields a type error, since the methods expect Kleisli[OptionT[F, *], Request[F], Response[F]]. I tried working around this issue, but I couldn't find a solution that doesn't have me re-implement Logger.httpRoutes for ContextRequest inputs.
Hence, I figured I am going to post a feature request as suggested in the Gitter channel. Logger.authedRoutes would be immensely useful, as long as I haven't overlooked a straight-forward way to compose the HttpRoutes logging middleware with AuthedRoutes.
I would also love to have a look at it myself, I suppose it would be a good first issue. I can check out the existing implementations and try to implement the authed version with the least amount of duplication, a nice exercise.

It would be an interesting game of type tetris to see if we can do something generic, but I'd start concretely on the Logger.  If the innards take a function that narrows from input type to Request[F], I think it can be done without too much surgery.


chore(buildkitd): use buildkit v0.13.0 by default

Thanks! We've actually done it in https://github.com/wiremind/wiremind-helm-charts/commit/48fbbb919cc93aa692ee7390bf5c20adc4dab8ee !


No way to access previous steps variables - other than immediate predecessor, and that only works sporadically

Describe the Bug with repro steps
Go to workflow that was editable before new editor rolled out.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using Preview Designer or GA Designer
Generally Available
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Chrome
Additional context
No response

Hi Travis. It appears that in the last day or two the UI of the Azure Logic Apps standard designer has changed, and there's no way to reference variables or output properties of prior steps. In the previous designer UI this was easy. This makes the new UI almost unusable.
Is there some way to revert to the old UI?
Thanks
Mark
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Travis Harris @.>
Sent: Tuesday, May 16, 2023 1:28:22 PM
To: Azure/LogicAppsUX @.>
Cc: Mark Gerow @.>; Author @.>
Subject: Re: [Azure/LogicAppsUX] No way to access previous steps variables - other than immediate predecessor, and that only works sporadically (Issue #2399)
** EXTERNAL EMAIL **
Hello, thanks for reporting. Can you give some more details on your workflow and how you repro the issue. Just the generic title and description here is not something we’re able to reproduce.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/LogicAppsUX/issues/2399#issuecomment-1550315389, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6F57C3FDUTNMLBIBAMIWCLXGPPONANCNFSM6AAAAAAYECEDOA.
You are receiving this because you authored the thread.Message ID: @.***>

Hey Mark, yes we've made the new preview UI GA and it's now fully replaced the old UI which is being deprecated. Can you give us more information about what you're workflow looks like though. The issue you're describing is not something we're able to repro. Here is my attempt.

Hi Travis,
The problem may be related to your handling of SQL connector. When I created a very simple flow similar to yours, I could see step variables, but many of our flows start with a SQL trigger. I've attached a representative example. What I've observed is that the SQL trigger is inconsistent in displaying parameters (which we use for server and database name), will not resolve the tables in the table property so I need to manually enter the table name. Also, when I use a SQL step to get a row, no data from that step is available in future steps.
I spot-checked some other flows, and outputs from the Teams connector likewise does not seem to be available in later steps.
I have not tested with other kinds of connectors.
This is a HUGE problem for us, as we have hundreds of flows like this, which we now cannot edit through the designer.
Mark
[cid:39d1fd72-0f83-4942-9ce9-50ab6a6064db]
[cid:6a85284e-45cf-4e90-8eb6-21f3f05bda38]
[cid:c4223e68-9e84-4adb-aa9b-a60e92bf529c]
[cid:8f2ed426-e19d-449e-9c90-6e779da128a8]

From: Travis Harris @.>
Sent: Tuesday, May 16, 2023 10:46 PM
To: Azure/LogicAppsUX @.>
Cc: Mark Gerow @.>; Author @.>
Subject: Re: [Azure/LogicAppsUX] No way to access previous steps variables - other than immediate predecessor, and that only works sporadically (Issue #2399)
** EXTERNAL EMAIL **
Hey Mark, yes we've made the new preview UI GA and it's now fully replaced the old UI which is being deprecated. Can you give us more information about what you're workflow looks like though. The issue you're describing is not something we're able to repro. Here is my attempt.
[CleanShot 2023-05-16 at 22 45 @.***https://user-images.githubusercontent.com/13208452/238845549-ef4e4457-e62d-4158-a214-b67cbae0b433.png
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/LogicAppsUX/issues/2399#issuecomment-1550774055, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6F57C3NEIZM7PEXNDEFVH3XGRQ2LANCNFSM6AAAAAAYECEDOA.
You are receiving this because you authored the thread.Message ID: @.***>

I would also point out that this problem is occurring for other developers on my team. As I said, this is a HUGE problem for us. If you could give us access to the old UI until it can be fixed I would greatly appreciate it. If you need to get on a call to see what we're seeing, I will gladly do so.

From: Mark Gerow @.>
Sent: Wednesday, May 17, 2023 8:50 AM
To: Azure/LogicAppsUX @.>; Azure/LogicAppsUX @.>
Cc: Author @.>
Subject: Re: [Azure/LogicAppsUX] No way to access previous steps variables - other than immediate predecessor, and that only works sporadically (Issue #2399)
Hi Travis,
The problem may be related to your handling of SQL connector. When I created a very simple flow similar to yours, I could see step variables, but many of our flows start with a SQL trigger. I've attached a representative example. What I've observed is that the SQL trigger is inconsistent in displaying parameters (which we use for server and database name), will not resolve the tables in the table property so I need to manually enter the table name. Also, when I use a SQL step to get a row, no data from that step is available in future steps.
I spot-checked some other flows, and outputs from the Teams connector likewise does not seem to be available in later steps.
I have not tested with other kinds of connectors.
This is a HUGE problem for us, as we have hundreds of flows like this, which we now cannot edit through the designer.
Mark
[cid:39d1fd72-0f83-4942-9ce9-50ab6a6064db]
[cid:6a85284e-45cf-4e90-8eb6-21f3f05bda38]
[cid:c4223e68-9e84-4adb-aa9b-a60e92bf529c]
[cid:8f2ed426-e19d-449e-9c90-6e779da128a8]

From: Travis Harris @.>
Sent: Tuesday, May 16, 2023 10:46 PM
To: Azure/LogicAppsUX @.>
Cc: Mark Gerow @.>; Author @.>
Subject: Re: [Azure/LogicAppsUX] No way to access previous steps variables - other than immediate predecessor, and that only works sporadically (Issue #2399)
** EXTERNAL EMAIL **
Hey Mark, yes we've made the new preview UI GA and it's now fully replaced the old UI which is being deprecated. Can you give us more information about what you're workflow looks like though. The issue you're describing is not something we're able to repro. Here is my attempt.
[CleanShot 2023-05-16 at 22 45 @.***https://user-images.githubusercontent.com/13208452/238845549-ef4e4457-e62d-4158-a214-b67cbae0b433.png
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/LogicAppsUX/issues/2399#issuecomment-1550774055, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6F57C3NEIZM7PEXNDEFVH3XGRQ2LANCNFSM6AAAAAAYECEDOA.
You are receiving this because you authored the thread.Message ID: @.***>

please send me an email at<EMAIL_ADDRESS>and I'll give you a link to the old designer while we work to fix the issue you mentioned.

@preetriti1 - All databases are Azure SQL-hosted. Also fails for Teams connectors
Travis - I did send you screenshots earlier this morning, did you not get those?

From: preetriti1 @.>
Sent: Wednesday, May 17, 2023 10:33 AM
To: Azure/LogicAppsUX @.>
Cc: Mark Gerow @.>; Mention @.>
Subject: Re: [Azure/LogicAppsUX] No way to access previous steps variables - other than immediate predecessor, and that only works sporadically (Issue #2399)
** EXTERNAL EMAIL **
@fw-mgerowhttps://github.com/fw-mgerow - Could you confirm what type of connection you are using? Is it a gateway connection?
This seems like a dynamic data issue where we use connection to resolve the parameters and get outputs.
Can you just try adding a new sql action with a different connection and see if that populates your data? Do you happen to see any error ot warning in the UI and if not in the console?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/LogicAppsUX/issues/2399#issuecomment-1551802846, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6F57C6CEY5OM5ON3K2X7Q3XGUDWRANCNFSM6AAAAAAYECEDOA.
You are receiving this because you were mentioned.Message ID: @.***>

@fw-mgerow just went back and checked to make sure, no screenshots made it to me


fix(nuxt): build script

this pr fixes #2471 by update the build script that has a missing && between pnpm dev:prepare and nuxt-module-build build.

ahh great catch!


APNs push notifications severely delayed

Description
Seeking assistance / advice on resolving a APNs VOiP push notification issue (delayed delivery).
TL;DR - Calls are being received, notified via APNs notifications however they seem to be severely delayed (being received on 'opponents' device, up to 120s). After the first call is successfully received and reported, subsequent calls (mostly) go through almost instantly (accounting for network delay), usually around 3-5s.
I suspect it may have something to do with Pushkit device token being registered to possibly too many users access tokens / users, however upon logout I call unregister(deviceToken, accessToken)that should resolve this.
Context:
A user can login (request access token and register with device token). A user can call another user. A user can logout, login as a different user and make/receive calls meant for the new user (user based, not device based).
Steps to Reproduce

Use sample project (adapted for user-based project, i.e. login/logout)
Place call (caller)
Expect & answer call (opponent/recipient)

Code
Only code adaption (since this is modified into a Flutter package) is: upon launching, the device's push token is cached regardless of TwilioVoiceSDK.register() is successful - this allows for users to login/logout. Upon logout, th
Expected Behavior
Upon first install & login (caller & recipient), first call (possibly slight delay for init, etc) but nothing more than 10s wait time for recipient to be notified of incoming call.
Actual Behavior
Upon first install & login (caller & recipient), first 1-2 (up to around 5) calls are missed/no-answer (on recipient side). After a period of time, the recipient's device console output shows the APNs push notification is received and code handles the (delayed notification) as it should (reporting as missed only, not reported as new incoming call).
Log outputs
On both devices, I get:
LOG|Successfully registered for VoIP push notifications.
flutter: Successfully registered for VoIP push notifications.

Log output correlation to sample iOS swift app
Log outputs which originates from calling register(deviceToken, accessToken) (after user authentication & new access token for user is generated with adapted sample of incoming.js)
Reproduces How Often
Often (min 80% - app breaking)
Twilio Call SID(s)
Sample of delayed workflow as described above. All Call SID's are from the recipient.

Failed, timeout. CA3522338e615b3fd3f4b25254e5d767ac
Failed, timeout CA81a444c2cd9f6e6fd567ea560ad6543f
Failed, timeout CAe3ff825264825b79aa723d6a0ea208e8
Failed, timeout CA5bd89cf8ce6be17ab7dd4307c0010e3c
Received, after ~23s since starting call CAc26200cff057e5082e07012fd16070c0

During these calls, devices are active & have app open with no interaction besides repeat calling until call is received. (both have background & mic permissions, have voice & push notification capabilities, etc)
Voice iOS SDK
6.3.0 (via Podfile.lock)
Xcode
Version 13.3.1 (13E500a)
iOS Version
15.5 (Caller & recipient)
iOS Device
iPhone 7 (Caller & recipient)
iPhone 6s (Caller & recipient)

Additional question/request
Where are APNs push notifications stored for Twilio, it would be extremely helpful during developement to see which push notifications were sent, for what call and if they were successfully delivered. I can't find such a page/information on the Twilio Console.

Hi @cybex-dev
Thanks for the detailed description and Call SIDs. I did check the Call SIDs and found that Twilio actually sent out push notification delivery requests to APNS almost immediately when the calls were made to the receiving client, and all the request response were successful.
Please make sure the PushKit instance is initialized in the frontmost component of the iOS app, preferably the AppDelegate. That way the app can handle the incoming VoIP push timely, on the main thread, especially when the app is in the background or not running.

@bobiechen-twilio
Thanks for the rapid response.
I had another look at the Flutter implementation for user-sessions (specifically for iOS).
Upon logging out by calling unregister(accessToken, deviceToken), the cached token wasn't being cleared (as a result from credentialsInvalidated())
During logout, the following is called.
    public func pushRegistry(_ registry: PKPushRegistry, didInvalidatePushTokenFor type: PKPushType) {
        self.sendPhoneCallEvents(description: "LOG|pushRegistry:didInvalidatePushTokenForType:", isError: false)

        if (type != .voIP) {
            return
        }

        self.unregister()
    }

    func unregister() {

        guard let deviceToken = deviceToken, let token = accessToken else {
            return
        }

        self.unregisterTokens(token: token, deviceToken: deviceToken)
    }

    func unregisterTokens(token: String, deviceToken: Data) {
        TwilioVoiceSDK.unregister(accessToken: token, deviceToken: deviceToken) { (error) in
            if let error = error {
                self.sendPhoneCallEvents(description: "LOG|An error occurred while unregistering: \(error.localizedDescription)", isError: false)
            } else {
                self.sendPhoneCallEvents(description: "LOG|Successfully unregistered from VoIP push notifications.", isError: false)
            }
        }
        UserDefaults.standard.removeObject(forKey: kCachedDeviceToken)

        // Remove the cached binding as credentials are invalidated
        UserDefaults.standard.removeObject(forKey: kCachedBindingDate)
    }

This has allowed login & logout as various users with calls reporting successfully each time.
@bobiechen-twilio for future reference, does Twilio provide an interface to view sent push notifications (via APNs or to other push notification services)?

The unregister() method won't invalidate the PushKit device token. The token is only invalidated by Apple under a handful of scenarios. Please check out the Apple developer documentation.

does Twilio provide an interface to view sent push notifications

Currently only when the delivery requests are unsuccessful (invalid device token, mismatch APN environment and etc.) then Twilio will log an error notification in your developer console with error description and possible solution.

To clarify.
In the scenario of an authenticated user with an access token attached to their device token (pushkit token), calling unregister() will ask Twilio to dissociate the device & access tokens (i.e. all subsequent calls to the attached identity results in  'Temporarily Unavailable').
If that is the case, the deviceToken remains across user sessions.

Oops, got the wrong snipper above. The deviceToken and binding should not be cleared.
This is correct.
    public func pushRegistry(_ registry: PKPushRegistry, didInvalidatePushTokenFor type: PKPushType) {
        self.sendPhoneCallEvents(description: "LOG|pushRegistry:didInvalidatePushTokenForType:", isError: false)

        if (type != .voIP) {
            return
        }

        self.unregister()
    }

    func unregister() {

        guard let deviceToken = deviceToken, let token = accessToken else {
            return
        }

        self.unregisterTokens(token: token, deviceToken: deviceToken)
    }

    func unregisterTokens(token: String, deviceToken: Data) {
        TwilioVoiceSDK.unregister(accessToken: token, deviceToken: deviceToken) { (error) in
            if let error = error {
                self.sendPhoneCallEvents(description: "LOG|An error occurred while unregistering: \(error.localizedDescription)", isError: false)
            } else {
                self.sendPhoneCallEvents(description: "LOG|Successfully unregistered from VoIP push notifications.", isError: false)
            }
        }
        // UserDefaults.standard.removeObject(forKey: kCachedDeviceToken)

        // Remove the cached binding as credentials are invalidated
        // UserDefaults.standard.removeObject(forKey: kCachedBindingDate)
    }

TL;DR Retain binding & cached token.


Sub Directory entry points

I am using multiple entry points to create my modules.  My index.html files for each entry point are in different paths.  I did not want to separate my modules into new webpack projects, but I need them to be able to stand alone later as their own root entry.
The entries are setup like the following:

./main.js (./index.html)
./admin/main.js (./admin/index.html)
./anotherentry/main.js (./anotherentry/index.html)

I have actually solved any public path issues during webpack-dev-server by setting

output.publicPath = '/' when running the webpack-dev-server
output.publicPath = '' when running webpack

The problem I have with file-loader now is that it always emits the file to a relative path to the context and also sets the url to the path from the context root which means the path points to the incorrect place for the entry points in the sub directories.
Here is how I think file-loader should handle the path of the url's.

have an emitUrl based on the options.context
have a url based on query.context || this.options.context as the root and pass context in parameters if in a sub directory. I am not sure there is a way to know if your entry is in your current directory.
if the public path is absolute (i.e. this.options.output.publicPath.substr(0,1) === '/') then the emitUrl and url are the same and paths do not need to be different

If you think I am going down the wrong road with this, please let me know.  Otherwise, I think I could put together a PR to show you what I mean.

Thank you @sokra. Your reply helped me greatly!

Closing since it looks like the root problem has been solved now. If there's still a problem, please make a new issue.


Use likely() in PtrToArg<T *> when checking for null Object *s

In https://github.com/godotengine/godot-cpp/pull/1405, @reduz requested that likely() be added to PtrToArg<T *> when checking for null Object *s in godot-cpp.
This is doing the same thing for the equivalent code in Godot, so that we are consistent between Godot and godot-cpp.
I also switched to using a ternary to match the godot-cpp code. I'd be fine going the other way and switching godot-cpp to use an if-statement, but however we do it, it'd be nice to be somewhat consistent. (Unfortunately, the casts can't be made consistent due to other differences.)

Thanks!


Add improved docs

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
View rendered
Related-to: unifiedjs/unified#168.
/cc @nemo-omen @remcohaszing @ChristianMurphy @Murderlon @with-heart @joostdecock @mgan59

Codecov Report

Merging #12 (3aeccbd) into main (838006a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          641       641
=========================================
  Hits           641       641

Continue to review full report at Codecov.

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


db-postgres: relationship field filterOptions returning unexpected results

Link to reproduction
https://github.com/JPrisk/payload-minimal-reproduction/compare/90c03c8652bba7a3f555517cd0d6eebee2b73ca5...HEAD
Issue
When using the relationship field with the Postgres adapter, filterOptions is returning unexpected results.
When the field is empty the filterOptions works as expected, but when the dropdown has a value selected it acts differently (sometimes requires a page refresh to bust cache).
It seems as though when the not_in clause gets appended, the filterOption clauses aren't being merged correctly.

❌ filterOptions not working
✔ filterOptions working (unpopulated field)

To Reproduce
Prerequisites: run Payload locally, seed db

Log in to the dashboard<EMAIL_ADDRESS>/ password
Navigate to 'Pages / Example page'
Focus on the 'Featured News' dropdown
👀 Look at the results

Payload Version
2.11.2
Adapters and Plugins
db-postgres

I think, this could be the same issue as https://github.com/payloadcms/payload/issues/5151

Hey @JPrisk - thanks for adding a reproduction, this helps a lot in the debugging process.
After using your steps to try and reproduce, I was unable to reproduce the behavior. The Featured News relationship filter dropdown is showing me the correct results.
Can you give this another shot on latest to confirm? Thank you!

@JPrisk Going to close this for now, if you can still reproduce this in the near future, we can open this issue back up and I'll take a look into this!

Hey @PatrikKozak  - i've been out of action 🤒 hence the delay getting back to you.
Just tried updating to the latest version of payload + @payloadcms/db-postgres in the project where I encountered it and the problem still persists.
One important thing to note:
When testing, the issue arises once a value is selected and the user is making additional selections.


Add echo for end of each build phase

It is hard to find out what failed when trolling Travis logs.  This makes it easier, you can just skip to /// and scroll back looking for error messages.
After reviewed, I'll do similar PR's for master and 1.0.2

If you grep for 'exited', you'll find the ends that you look for already.

Travis red cross is relevant. It complains about not knowing how to 'make echo'. As for searching for "exited". It's valid point, but many of them are not directly related, so you still kind of want "own" markers...

Added the semicolon and pushed an updated commit.

Do you know what would be more useful? If it resulted in unique hit per search. I mean how looking for say '///' gives thee hits, one in "starting this", then echo itself and finally "this exited". And what would be even more useful if first '///' would take you to first check-point, '////' - to second, etc. This way if you have travis log open in firefox, you'd be able to advance to next checkpoint by simply adding '/' to find dialogue...

three hits

I mean echo "\057\057\057" would do the trick...

Ehhhh, I just realised I must disagree with this PR, as it will change useful exit codes.
$ (exit 1); echo foo; echo $?
foo
0

So, errr, -1

as it will change useful exit codes.

Good catch! But it should still be possible to add markers as separate lines or if clauses. For example not
    - if [ -n "$CHECKDOCS" ]; then
          $make doc-nits;
          echo "something"
      fi

but two ifs, second is specifically for echo marker...

My use-case is that I do control-F and then /// in the browser to jump to the end of each section to see if there are any failures.  So I removed the trailing ///  Does this make sense?

I could replace each of the added echo lines with this:
case $? in
0) echo '/// MAKE UPDATE OK' ;;
*) echo '/// MAKE UPDATE FAILED' ; /bin/false ;;
esac

But that seems too much.  I'll see if searching for "exited" works well enough for me.


Use flutter test instead of flutter drive

flutter test currently doesn't allow for using custom bindings. See https://github.com/flutter/flutter/issues/113097.
We have our own custom binding, PatrolBinding. The only things it does is setting the source of every pointer event (tap, slide, etc) to test instead of device.
It lets native automators tap on our Flutter app (the most common use case for this is a WebView).
Without our custom bindings, when we $.native.tap() on some widget, no tap is performed, instead we only get the following output in the console:
Some possible finders for the widgets at Offset(195.0, 779.0):
  find.text('Open webview screen')
  find.widgetWithText(Align, 'Open webview screen')
  find.widgetWithText(Padding, 'Open webview screen')
  find.widgetWithText(GestureDetector, 'Open webview screen')
  find.widgetWithText(MouseRegion, 'Open webview screen')
  find.widgetWithText(InkWell, 'Open webview screen')
  find.byType(SliverList)
  find.byType(SliverPadding)
  find.byType(Viewport)
  find.byType(Scrollable)
  find.byKey(const Key('listViewKey'))
  find.byType(NotificationListener<ScrollNotification>)
  find.byKey(const Key('scaffold'))
  find.byElementType(InheritedModelElement<Object>)

Replacing flutter drive with flutter test should also fix #425 (source).

We won't need PatrolBinding at all when https://github.com/flutter/flutter/pull/108430 lands on the stable channel.

graph TD
  fluttertest[flutter test + JUnit #421, #495] --> flutter3.5
  host_features[screenshots, scripts] --> host_server[vmservice #593]
  host_server --> custom_bindings[requires PatrolBinding] --> blocked_by_flutter[blocked by flutter #113097]

This is superseded by #661.


Publish only on release and update node version

publishing is failing because of the node version
and with push we are publishing when someone raises a PR as well, so should be published when there is a new release

https://github.com/snapshot-labs/actions/pull/5 was merged, see https://github.com/snapshot-labs/actions#usage-4 for how the new workflow content. And rename the file to publish-npm to follow the other repo naming


fix: handle properly np.cross() - 2d ops deprecated in Numpy 2.X

Description
As title says - once Numpy 1.X is not used anymore we can remove this.
Issue linked
None
Checklist

[X] I have tested my changes locally.
[X] I have added necessary documentation or updated existing documentation.
[X] I have followed the coding style guidelines of this project.
[X] I have added appropriate unit tests.
[X] I have reviewed my changes before submitting this pull request.
[X] I have linked the issue or issues that are solved to the PR if any.
[X] I have assigned this PR to myself.
[X] I have added the minimum version decorator to any new backend method implemented.
[X] I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

LGTM, it's wild that we need to do the cross operation that way. I see that they are going to implement a proper operation soon, can we add a TODO or some reminder to change this when np.linalg.cross2d is implemented?

Sure - though I am not sure they will even implement it... they have preferred documenting it over implementing https://github.com/numpy/numpy/pull/26692 and https://github.com/numpy/numpy/issues/26620#issuecomment-2163209159
More importantly... see this https://github.com/numpy/numpy/pull/26640 and especially https://github.com/numpy/numpy/pull/26640#issuecomment-2184184464 and https://github.com/numpy/numpy/pull/26640#issuecomment-2192324341
I don't think it'll ever be implemented honestly...

LGTM, it's wild that we need to do the cross operation that way. I see that they are going to implement a proper operation soon, can we add a TODO or some reminder to change this when np.linalg.cross2d is implemented?

Sure - though I am not sure they will even implement it... they have preferred documenting it over implementing numpy/numpy#26692 and numpy/numpy#26620 (comment)
More importantly... see this numpy/numpy#26640 and especially numpy/numpy#26640 (comment) and numpy/numpy#26640 (comment)
I don't think it'll ever be implemented honestly...

Forget about the reminder then 😄

Forget about the reminder then 😄

Haha! 😄 good then - thanks for pointing it out though! It would've been the way to proceed (if they had decided to eventually implement it... but I think it's not the case - I'll keep an eye on NumPy though and the issues)

@AlejandroFernandezLuces - I just pushed @MaxJPRey's suggestion to typehint it as well. Can you approve?

@AlejandroFernandezLuces - I just pushed @MaxJPRey's suggestion to typehint it as well. Can you approve?

Done @RobPasMue


Selector regression with upgrade from 3.5.8 to 3.5.11

I encountered several regressions when trying to upgrade codeceptjs from 3.5.8 to 3.5.11. Selector that worked with 3.5.8 do not work with 3.5.11.
What do you get instead?

ERROR! Unsupported pseudo :last-of-type. Example selector that is now broken:
lastInputRow: '[data-testid="field-definitions-container"] > *:last-of-type',

I looked through the dependencies. The dependency convert-cssxpath/src/converter.js: throws the error. Likely the same issue as mentioned in slack.

`locator.all: DOMException: Failed to execute 'evaluate' on 'Document': The string '[contains(., 'Delete')]' is not a valid XPath expression. The selector is:
  deleteModal: {
    deleteButton: locate(".p-confirm-popup:last-of-type button").withText("Delete")
  },

Once I remove :last-of-type: the selector works again, so this may just be the same as the first with a different point of failure.

locator.all: DOMException: Failed to execute 'evaluate' on 'Document': The string '//li[@role="option"]//*[@data-testid="date"][ancestor::]' is not a valid XPath expression.. Locator is:
locate(`li[role="option"] [data-testid="${type}"]`).inside('[data-testid="field-definitions-container"] > *:last-of-type')

Likely also the same issue, but I can't fully verify because this is needed for the suite to continue.

@kobenguyent could you tag an alpha (or nightly) release for npm? i'll happily take it for a test drive. :)

Thank you very much! @kobenguyent. Is "last-of-type" somewhat cursed for xpath conversion? Now i'm getting this:
Error: Could not include object examplePo from module '/dev-local/e2e_tests/pageObjects/examplePo.js'
*-of-type pseudos require a tag context
SyntaxError: *-of-type pseudos require a tag context

Selector is still
  deleteModal: {
    deleteButton: locate('.p-confirm-popup:last-of-type button').withText('Delete')
  },

@kobenguyent Nice, wouldn't have thought of that ^^
Oddly, it still goes down the code path to the new lib for this locator:
deleteButton: locate('.p-confirm-popup:last-of-type button').withText('Delete')

Leading to:
SyntaxError: *-of-type pseudos require a tag context

Yes, that locator works with 3.5.8.

yes, just tested this in isolation

After some layer 8 errors on my side, I'm positively certain that this PR fixes the regression. Thank you, @kobenguyent, for your patience.


wlroots 0.15.0 issue

I am following this tutorial to install Sway on my Ubuntu machine.
But I am running into a problem where I am unable to meson build sway because I get this error:
meson.build:74:1: ERROR: Invalid version of dependency, need 'wlroots' ['>=0.15.0'] found '0.12.0'.
I used 0.12.0 because that is what the tutorial used, but when I tried to git checkout to the latest version I saw that 0.15.0 is still unreleased.
So how can I carry on with the installation? Am I doing something wrong?

The master branch of sway requires the master branch of wlroots. If you want to build the master branch of sway you'll need to build the master branch of wlroots from source as well.

Sorry, I am under the implession I did just that though. Should I have git cloned another repo other than https://github.com/swaywm/wlroots?
I did build version 0.12.0. But to build sway, it says, I need 0.15.0. which doesn't exist.

The master branch of this repository is the not yet released wlroots 0.15.0. It appears that "tutorial" you linked instructed you to check out the 0.12.0 tag for some unknown reason. Run git checkout master in the wlroots repo and try again.
Also, I'd recommend not blindly trusting tutorials for this reason, instead refer to the official docs :)

I think that worked. Now I must figure out the error about meson not being in /usr/bin/
Thank you, it is the first time I compile from source. Checking out the official docs now. Again thanks for your help though!


docs(migration): move params.version to end

moving the params.version to the end fixes the search boxes not showing up

Preview looks good


add TransportDirect transport

The TransportDirect transport allows to tweak outgoing SMTP connexions to remote servers. Currently, it only allows to select network IP family (ipv4, ipv6 or both).
For example, to disable ipv6 for all outgoing SMTP connexions:

add these lines in mox.conf to create a new transport named "disableipv6":

Transports:
  disableipv6:
    Direct:
      DisableIpv6: true

then add these lines in domains.conf to use this transport:

Routes:
  -
    Transport: disableipv6

fix #149

@mjl- this is my second attempt to fix #149. This time by adding a new transport for direct connexions as we talked https://github.com/mjl-/mox/issues/149#issuecomment-2041007381


special character retrieval in item data

hi,
in my workflow I create new operations views based on a template AGOL item. In run into an issue where special characters are encoded while reading the json.
When I create the new operations view object based on the template, I would like to store the euro-sign in the json data like the snippet below. Not in encoded form.
The encoded character storage will lead to problems in windows dashboard application.
This is how the euro-sign is stored in my template operations view definition:
{
"caption": "Kosten (€)",
"clickFeatureAction": {
"type": "highlightAction",
"updateExtent": "pan"
},  ( ... )
Any way to get this approach working in ArcRest?
I have been able to resolve this by retrieving the template item data (using requests library) and uploading the item data with json.dumps(data, ensure_ascii=False).
Would be nice to get this integrated in ArcRest as well.
Best Regards,
Laurens

This is something I will look into and try to put it in the next release.  Thank you for the suggestion.

@ python 2.x use the urllib to sanitize your text values:
Example:
>>> import urllib
>>> print urllib.quote_plus("äöüßáà")
     '%C3%A4%C3%B6%C3%BC%C3%9F%C3%A1%C3%A0'


SHA comparison is case sensitive

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.
Please always follow these steps:

[x] Confirmed this is a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at the relevant tap e.g. for Homebrew/homebrew-core https://github.com/Homebrew/homebrew-core/issues/new
[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed all issues and retried your prior step?
[x] Ran brew config and brew doctor and included their output with your issue?

[17:52] ~ % brew config
HOMEBREW_VERSION: 1.3.7
ORIGIN: https://github.com/Homebrew/brew
HEAD: 441c212f2dd70f053ee21eac8398c5fe5dfd0551
Last commit: 7 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 8fc59d0ab240a8c46d862c491200f1bb62a76b26
Core tap last commit: 17 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_GEM_HOME: /Users/thom/.gem/ruby/2.4.2
HOMEBREW_GEM_PATH: /Users/thom/.gem/ruby/2.4.2:/Users/thom/.rubies/ruby-2.4.2/lib/ruby/gems/2.4.0
HOMEBREW_GIT_CONFIG_FILE: /usr/local/Homebrew/.git/config
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.3.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 9.0 build 900
Git: 2.15.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /Users/thom/.rubies/ruby-2.4.2/bin/ruby
Java: N/A
macOS: 10.13.1-x86_64
Xcode: 9.1
CLT: <IP_ADDRESS>.1.1508540944
X11: N/A
[17:53] ~ % brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
  /Users/thom/.cargo/bin/cargo-install-update-config

When trying to install the hab package from the habitat-sh/habitat cask, it tells me that the checksum is invalid:
brew tap habitat-sh/habitat
brew install hab
==> Installing hab from habitat-sh/habitat
==> Downloading https://bintray.com/habitat/stable/download_file?file_path=darwi
Already downloaded: /Users/thom/Library/Caches/Homebrew/hab-0.39.0.zip
Error: SHA256 mismatch
Expected: 2A81E7DA6F75CF0923924FFF11DC78ACF8F0C4ED389B41F6742622601F1293CB
Actual: 2a81e7da6f75cf0923924fff11dc78acf8f0c4ed389b41f6742622601f1293cb
Archive: /Users/thom/Library/Caches/Homebrew/hab-0.39.0.zip
To retry an incomplete download, remove the file above.

Note that these are the same checksum, just that one is upcase and one is lower case. Is it expected that all checksums must be specified lower case?

Is it expected that all checksums must be specified lower case?

yes.


feat: Enable Hubble Relay in Cilium deployment via CAAPH

What problem does this PR solve?:
Relay is required for network visibility of a cluster as a whole. See https://docs.cilium.io/en/stable/gettingstarted/hubble_intro/.
Which issue(s) this PR fixes:
Fixes #
How Has This Been Tested?:

Special notes for your reviewer:

@dlipovetsky Please can you add a test to e2e to ensure the necessary hubble components are running? This will also help us know what to expect in-cluster when Hubble is enabled.

@dlipovetsky Force pushed after editing last commit message to pass gitlint.

Added e2e test in 56a583c7187cdb7390e233966a90fb3823d517c6 (while also taking the opportunity to tidy up "kube-system" consts).


PackedScene metadata is not saved

Godot version
4.0.2
System information
Windows 10 x64
Issue description
var ps = load("res://scene.tscn")
ps.set_meta("test", 1111)
ResourceSaver.save(ps)

When you open the file in text editor, there's no trace of what you just assigned.
I get that PackedScene is a special resource, but if it's not going to be supported (although implementing it is possible), it should at least be documented.
Steps to reproduce

Create a scene
Run the code above
Open tscn file in text editor and look for the meta property

Minimal reproduction project
N/A

I just ran into this issue, Godot 4.1.rc2

After some digging, I found that the code did not handle meta data when it's a packed scene. Do we need to add support for it ?

Well I'd expect the metadata to be serialized properly regardless of the resource.

Let me try to fix this :）


DataArray doesnt use bottleneck implementation on rolling variance

It appears that the DataArray is not using the bottleneck move_var when calling var on a rolling object but it does for std. I have attached some simple benchmarks to demonstrate.
python version 3.6
pandas version 0.19.2
xarray version 0.9.1
bottleneck version 1.2.0
import numpy as np
import xarray as xr
import bottleneck
import pandas as pd

data = np.random.rand(10000)

# xarray setup
ar = xr.DataArray(data, dims=['time'])
xrol = ar.rolling(time=30)

# pandas setup
df = ar.to_pandas()
prol = df.rolling(30)

# xray std profile
%time _ = xrol.std()

CPU times: user 0 ns, sys: 0 ns, total: 0 ns
Wall time: 209 µs

# xray var profile
%time _ = xrol.var()

CPU times: user 8.69 s, sys: 132 ms, total: 8.82 s
Wall time: 8.52 s

# pandas std profile
%time _ = prol.std()

CPU times: user 0 ns, sys: 0 ns, total: 0 ns
Wall time: 1.13 ms

# pandas var profile
%time _ = prol.var()

CPU times: user 0 ns, sys: 0 ns, total: 0 ns
Wall time: 617 µs

# bottleneck std profile
%time _ = bottleneck.move_std(data, 30)

CPU times: user 0 ns, sys: 0 ns, total: 0 ns
Wall time: 138 µs

# bottleneck var profile
%time _ = bottleneck.move_var(data, 30)

CPU times: user 0 ns, sys: 0 ns, total: 0 ns
Wall time: 143 µs

Indeed, var is not in the list of ops for which we use bottleneck:
https://github.com/pydata/xarray/blob/7e0abe5542168b2aafbda18fe5db62f39b5df498/xarray/core/ops.py#L53-L55
Looks like median would also be a good one to add.
Maybe @jhamman recalls why we don't use bottleneck for these?

@shoyer and @d-chambers -
Take a look at #1278. The issue here was that we had not kept up with bottleneck's improvements and in 1.1, they added move_var. I think my PR should remedy this.


Menu issue after installing this package

After installing this package, all menus can't be clicked and this error occurred
(in promise) TypeError: Cannot read properties of undefined (reading 'toString')

@Algeneralo
My guess is it's either caused by a conflict with another package or because of a recent Nova update. Can you please try disabling other packages and let me know which one is causing the conflict, if any?
Also what Nova version are you using?

I don't know why this error occurs, but at least for me it works again after removing the translation in the group function:
public static function group()
{
    // return __('nova-permission-tool::navigation.sidebar-label');
    return 'Roles & Permissions';
}

Laravel Framework: 9.17.0
Laravel Nova: 4.8.1
I've started testing this package and can confirm this issue does not happen to me. Maybe I'm missing the issue defined here or it's no longer an issue? 😄
btw: @kiritokatklian thanks a lot for this fork.


Eliminate preprocessor warnings due to undefined "GNUC" with ClangCL

When building some code against mimalloc with C inside Visual Studio
with ClangCL, the compiler complains about __GNUC__ being undefined.
Reported by Mojca Miklavec.
Close #422

@mojca , Could you please help review this pull request?

The patches all look fine to me, and the software that uses the library seems to build and work fine and these warnings seem to be gone (there are other compiler warnings, but that's for a separate ticket). Thank you.

Awesome -- thanks Jim :-)


Investigate transport features

For example, Quick ack could be a nice-to-have.

Personally not interested so I'll be closing this, but happy to approve PRs if others are.


GOG Skyrim SE/AE Support

Will your epic Elysium Remastered modlist have GOG support when WJ finally fully supports this version? Thank you.

Would really like to see this too, and Wabbajack currently supports GOG Skyrim SE/AE as of <IP_ADDRESS> -> https://github.com/wabbajack-tools/wabbajack/releases/tag/<IP_ADDRESS>

Many mods in the list don't support GOG yet. So no plans for GOG support atm.


Home Assistant Cloud URL used as Redirect URL for OAuth instead of user's configured external URL

Version of the custom_component
v0.8.3
Configuration
Failure occurs during UI Integration Configuration
Describe the bug
The integration seems to use my Home Assistant Cloud URL (via a Nabu Casa subscription) instead of the external URL that I have configured in Configuration > Settings > General (/config/core). When I am redirected I get sent to a page with this error:
{"status":false,"errorCode":4700,"errorMessage":"Invalid redirect: https://<unique id>.ui.nabu.casa/auth/external/callback","result":null}

I was able to fix this by manually changing the redirect URL parameter in the URL, but I think the external URL that the user specifies in their configuration is what this integration should be using. The installation documentation even specifies that you should use the

...URL you configured inside of Home Assistant as the external URL...

I assume this could also be worked around by specifying the HA Cloud URL for the Redirect URL for OAuth while going through the installation steps.
Debug log
No relevant logs occur

I needed to get verification by my company to get the app approved. After approving it, it turns out that my fix doesn't actually work and I get an error. I think it may be similar to the issue mentioned in #18.
The other workaround I mentioned of adding my HA Cloud URL did seem to work. However, the root cause of this problem still needs to be resolved.

that seems like an upstream bug, the cloud URL should be able to get back to your instance and everything should work. Is there a reason why you think or know that the Nabu Casa URL above should not work?

I think the problem was that the docs say to specify the external URL the user has configured for HA. However, the integration ends up using the Nabu Casa URL which is different. So I feel like the docs should be updated to mention this. What do you think?
I actually also think that the user's specified external URL should be preferred over the Nabu Casa URL, but I see what you're saying where HA could be feeding your integration the wrong URL to use.


Add German localization

This is a German-language localization file, created by kruemel in the Discord.
I am unaware as to the legitimacy and/or accuracy of the translation, so some review may be needed, though I am not bilingual. If you can, please point out any errors.

Hello, my name is Locher and I reviewed the german localization attempt of my peers.
I used gbstudio extensively for the last weeks and therefore have enough contextual information to be confident in my proposed changes. I have used most if not all script functions that gbstudio offers and I am familiar with the different side windows within gbstudio.
My proposes are double-checked in the situations and contexts they were used for and I respected the conformity of how the Script functions are titled in the english version so that german users have an easier time searching for them via searchbar. Many terms were ambiguous and my peers seem to have misunderstood their use contexts so I took the liberty to correct them.
I am sure that german users of gbstudio will have an enjoyable time with gbstudio with these changes implemented.

Thanks for the review @LocherGit! It's been implemented into the file.


ZAP scan results upload to dojo resulting in server error (500)

Please use the following template when submitting issues: (If this is a security issue, then review the disclosure policy and submit via our security reporting program.
Issue Template
Issue Type

[X] Bug
[ ] Enhancement

Description
Receiving a Server Error (500) when I am trying to upload the scan results from the ZAP tool under 'ZAP Scan' scan type.
If the issue is a bug, please also include the following:
Operating System
Oracle Linux 7.5
Install

[X] setup.bash
[ ] docker

DefectDojo Version
1.5.2
Steps to Reproduce

Go to Product -> Engagement -> Import Scan Results
Provide the required fields data and click 'Choose File' (select a ZAP results xml)
Click 'Upload File' button

Sample Scan File (if applicable)
Screenshots (optional)
Console Logs (optional)
/dojo/django-DefectDojo/dojo/tools/zap/parser.py:227: FutureWarning: The behavior of this method will change in future versions.  Use specific 'len(elem)' or 'elem is not None' test instead.
item = {'uri': n.text, 'param': n2.text if n2 else "", 'host': host, 'protocol': protocol, 'port': port}
Internal Server Error: /engagement/5/import_scan_results
Traceback (most recent call last):
File "/dojo/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner
response = get_response(request)
File "/dojo/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response
response = self._get_response(request)
File "/dojo/lib/python2.7/site-packages/django/core/handlers/base.py", line 187, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/dojo/lib/python2.7/site-packages/django/core/handlers/base.py", line 185, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/dojo/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view
return view_func(request, *args, **kwargs)
File "/dojo/django-DefectDojo/dojo/engagement/views.py", line 543, in import_scan_results
item.save(dedupe_option=False)
File "/dojo/django-DefectDojo/dojo/models.py", line 1191, in save
if self.reporter.usercontactinfo.block_execution:
File "/dojo/lib/python2.7/site-packages/django/utils/functional.py", line 239, in inner
return func(self._wrapped, *args)
File "/dojo/lib/python2.7/site-packages/django/db/models/fields/related_descriptors.py", line 407, in get
self.related.get_accessor_name()
RelatedObjectDoesNotExist: User has no usercontactinfo.
[02/Oct/2018 15:49:14] "POST /engagement/5/import_scan_results HTTP/1.0" 500 27

Actually, this bug got resolved when I added phone numbers in the User's Profile and the scan results were imported fine.

The same error while importing ZAP scan result.
Docker-compose version of django-DefectDojo.


Error on running az bicep version

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az bicep version
Errors:
The command failed with an unexpected error. Here is the traceback:
type object 'datetime.datetime' has no attribute 'fromisoformat'
Traceback (most recent call last):
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 657, in execute
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 720, in _run_jobs_serially
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 691, in _run_job
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 328, in call
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/init.py", line 807, in default_command_handler
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/custom.py", line 3302, in show_bicep_cli_version
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 63, in run_bicep_command
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 152, in _load_bicep_version_check_result_from_cache
AttributeError: type object 'datetime.datetime' has no attribute 'fromisoformat'
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az bicep version

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.22.0

Extensions:
account 0.2.1
interactive 0.4.4

Additional Context
This happened after upgrading "az cli" to latest version and then updating az bicep

route to service team

Even when installing fresh Azure CLI for windows OS, i see the same error when running az bicep version command.
Please, escalate asap.

After updating to the latest Azure CLI (2.22.0) for Windows 10, I am now seeing the same error as others have reported:
Any command such as "az bicep version" is producing the following error:
The command failed with an unexpected error. Here is the traceback:
type object 'datetime.datetime' has no attribute 'fromisoformat'
Traceback (most recent call last):
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 657, in execute
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 720, in _run_jobs_serially
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 691, in _run_job
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 328, in call
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/init.py", line 807, in default_command_handler
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/custom.py", line 3294, in build_bicep_file
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 63, in run_bicep_command
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 152, in _load_bicep_version_check_result_from_cache
AttributeError: type object 'datetime.datetime' has no attribute 'fromisoformat'

FYI - I uninstalled Azure CLI 2.22.0 and installed 2.21.0 and confirmed that the 2.21.0 version did not have the problem reported.

Just to complement what @davidschlum mentioned check the links for installation.
Check following sources to get your 2.21.0 version below:

https://github.com/Azure/azure-cli/releases
https://community.chocolatey.org/packages/azure-cli/2.21.0

I just installed 2.22.1 and this fixes this issue, at least for me. 👍

My Azure Shell is broken now as it was upgrade and bicep does not work.  I can fix this by installing on premise.

Just encountered this one, rollback to version 2.22.1 works as expected.

Ran in to this issue as well on the mentioned versions, after upgrading to 2.24.2 it's working fine here again.

any final solution?

If you run this issue, try the following steps as solution:

Update your AZ CLI version
Upgrade the az bicep version
Downgrade the az bicep version if "Step 2" did not help you 👍

Hope this instructions will help you to troubleshoot the similar error that you have.


Does it work on distributed environments?

Hi, awesome looking project.
I looked through the documentation/examples and through the code and it doesn't seem to address distributed environments use cases. (eg. when we want a function execution to be exclusive not only on a single instance but across many instances of node which may or may not be running on the same machine).
If it does work on distributed environments, how can it be done?
If it does not, is it included in the roadmap? What are the data-structures which would have to be made distributed-safe and how can I help ?
Thanks

Hey,
Thank you for the feedback.
No, it's currently not supported but I can definitively see the use case.
Implementing it would require toasting everything but the core API design though...
I think the better approach would be to solve the problem at a lower level in a different project that would be like DirtyHairy/async-mutex and then use this project as a dependency for run-exclusive.
To keep it platform agnostic the subproject should define an interface like:
type DistributedMutex= {
    aquireLock(onLockAquired: (releaseLock: ()=> void)): void;
    isLocked(): boolean;
};
//PS: Callback instead of promises to allow for syncronously releasing the lock whenever possible.

And use this interface as dependency injection.
A bit like express session where you have to provide your own store.
I can see two main implementations of DistribudedMutexone relying on a database connection to be 100% distributed across node process AND across hosts.
And another implementation based on UNIX socket that would be easier to set up but would only enforce the lock across node process running on a single host.
Unfortunately, I have too much on my hands right now to undertake this. It would be very dope though and if it existed I would use it.
Of course, I will merge any PR that would be backward compatible.
Cheers


added inspector-metrics as peer dependencies

I added inspector-metrics as peer dependencies to let the host install inspector-metrics.

published in version 2.2.1


Doesn't load

When app opens... all that is seen is white screen

I am facing the same issue since today

I am facing the same issue, went to the dev screen and saw this error. Has it got something to do with it?

There are 159 open issues without an answer. :(
Looks like we need to find another local solution for Evernote.

Faced the same issue just now

Same issue since yesterday. Same error in dev console.

Looks like Evernote for web made an update which is not compatible with Tusk.

is there any way I can downgrade my evernotes version?

I think we must update Chrome version to 85 or up. Anyone knows how to rebuild it using another chrome version?

Well, the version of Chrome reported by About->Tusk shows 69.0.3497.128, but the version reported by the installed Chrome browser itself is 88.0.4324.150 (the latest build on linux). Something is afoot there.

Well, the version of Chrome reported by About->Tusk for me shows 69.0.3497.128, but the version reported by the installed Chrome browser itself is 88.0.4324.150 (the latest build on linux). Something is afoot there.

Electron apps come with it own version of Chrome. You have to rebuild/update the app to change electron version -> chrome version. But i don't know how to do it.

Ok, I found how to upgrade to latest version of electron (I never work on electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .

Thanks. I'll try it soon.
On Wed, Feb 10, 2021 at 2:42 PM David Pérez Serrada <
<EMAIL_ADDRESS>wrote:

Ok, I found how to upgrade to latest version of electron (I never work on
electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start
And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/klaussinani/tusk/issues/308#issuecomment-777084435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEEJMDP54W5HXE7UPZA5O3S6MDU7ANCNFSM4XLEAZCA
.

That does indeed work. I'll use this for now and leave the package fixing
to the experts.
Thank you, David!
On Wed, Feb 10, 2021 at 2:42 PM David Pérez Serrada <
<EMAIL_ADDRESS>wrote:

Ok, I found how to upgrade to latest version of electron (I never work on
electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start
And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/klaussinani/tusk/issues/308#issuecomment-777084435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEEJMDP54W5HXE7UPZA5O3S6MDU7ANCNFSM4XLEAZCA
.

Ok, I found how to upgrade to latest version of electron (I never work on electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .

It works!!! Thank you, @dserrada !
My versions:

I can confirm thanks Guys !

This isn't a permanent fix to the porblem. Whenever I want to start Tusk I need to go into the Tusk directory and use the command 'npm start' for Tusk to work. if I start it anyother way, I still get the white screen issue.
Can anyone else confirm?

Ok, I found how to upgrade to latest version of electron (I never work on electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .

I can confirm this works on macOS Big Sur 11.2 with Tusk 0.23.0 (<IP_ADDRESS>0).
It is a workaround, but not a solution. To make it work i followed dserrada's instructions. Had to install npm though (brew install npm). Whenever i stop the terminal running npm start Tusk goes back to white screen.
But thanks for the workaround! 👍

Ok, I found how to upgrade to latest version of electron (I never work on electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .

I can confirm this works on macOS Big Sur 11.2 with Tusk 0.23.0 (<IP_ADDRESS>0).
It is a workaround, but not a solution. To make it work i followed dserrada's instructions. Had to install npm though (brew install npm). Whenever i stop the terminal running npm start Tusk goes back to white screen.
But thanks for the workaround!

Thanks for confirming.

I was able to build and package Tusk:
Ubuntu 16.04
npm 7.5.3
node 15.8.0

Start with the steps from @dserrada

git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install

You may need to update some dependencies with npm, or even npm itself.
I got the latest (7.5.3) and the package.json for Tusk must be edited for npm7, perhaps stick to npm6?

Edit package.json (npm7)
-Find the "scripts" node
--Find the "release" node, and edit:

"release": "electron-builder build --publish never",

You can also remove some of the nodes under build->linux->target.
I ran into errors in step 3 when it tried to build for pacman/Arch.

In the readme:

Build binaries and installers: npm run release or yarn release

This will generate the package/snap you want in dist/
At this point I was able to install the snap as if I had downloaded an official one

git clone https://github.com/klaussinani/tusk.git cd tusk git checkout dependabot/npm_and_yarn/electron-9.4.0 npm install electron@latest npm install npm start
This works for me on ubuntu 20.04.02 LTS

Ok, I found how to upgrade to latest version of electron (I never work on electon, so i suppose this not the best solution, and more work is needed)
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

And it works..... (I only made a simple smoke test).
But if i try to run the tests or try to package, it fails :-( .

This solution works on Ubuntu 20.04.02 LTS!
But every time I npm start, I have to log-in again despite I have clicked the option to remember my login info
Is there anyway to auto save my login info?
Also, how could I replace this new Tusk with my old Tusk in applications search window?

Thanks for the tip @lfant9412 i was able to build packages with your solution.

npm didn't work properly  - having errors with nmp install command.
Can anybody suggest how and when the issue with Tusk will be fixed permanently, please!

I was able to build and package Tusk:
Ubuntu 16.04
npm 7.5.3
node 15.8.0

Start with the steps from @dserrada

git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install

You may need to update some dependencies with npm, or even npm itself.
I got the latest (7.5.3) and the package.json for Tusk must be edited for npm7, perhaps stick to npm6?

Edit package.json (npm7)
-Find the "scripts" node
--Find the "release" node, and edit:

"release": "electron-builder build --publish never",

You can also remove some of the nodes under build->linux->target.
I ran into errors in step 3 when it tried to build for pacman/Arch.

In the readme:

Build binaries and installers: npm run release or yarn release

This will generate the package/snap you want in dist/

Using this, I was able to Build .deb and AppImage, I've changed the version to 0.24.0 and Done, Evernote working Again.

I was able to build and package Tusk:
Ubuntu 16.04
npm 7.5.3
node 15.8.0

Start with the steps from @dserrada

git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install

You may need to update some dependencies with npm, or even npm itself.
I got the latest (7.5.3) and the package.json for Tusk must be edited for npm7, perhaps stick to npm6?

Edit package.json (npm7)
-Find the "scripts" node
--Find the "release" node, and edit:

"release": "electron-builder build --publish never",

You can also remove some of the nodes under build->linux->target.
I ran into errors in step 3 when it tried to build for pacman/Arch.

In the readme:

Build binaries and installers: npm run release or yarn release

This will generate the package/snap you want in dist/

Using this, I was able to Build .deb and AppImage, I've changed the version to 0.24.0 and Done, Evernote working Again.

Work very well Thank You @allanfreitas
But I have problem with 'Exit' Tusk. Not responding.
You too?

Hello,
can you try to deactivate /Exit Confirmation options /it was sufficient
for me to fix this issue.
Regards,
Gregory.
Le lun. 15 févr. 2021 à 13:34, mmati8<EMAIL_ADDRESS>a
écrit :

I was able to build and package Tusk:
Ubuntu 16.04
npm 7.5.3
node 15.8.0
Start with the steps from @dserrada https://github.com/dserrada

git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
You may need to update some dependencies with npm, or even npm
itself.
I got the latest (7.5.3) and the package.json for Tusk must be
edited for npm7, perhaps stick to npm6?

Edit package.json (npm7)
-Find the "scripts" node
--Find the "release" node, and edit:

"release": "electron-builder build --publish never",
You can also remove some of the nodes under build->linux->target.
I ran into errors in step 3 when it tried to build for pacman/Arch.

In the readme:

Build binaries and installers: npm run release or yarn release
This will generate the package/snap you want in dist/

Using this, I was able to Build .deb and AppImage, I've changed the
version to 0.24.0 and Done, Evernote working Again.

Work very well Thank You @allanfreitas
https://github.com/allanfreitas
But I have problem with 'Exit' Tusk. Not responding.
You too?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/klaussinani/tusk/issues/308#issuecomment-779457543,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBHXXES4EWNHJXH6GAOQOTS7GHPLANCNFSM4XLEAZCA.

@GregDuhamel thank you, work great :+1:

for those who can make it work, I just upgraded all packages and put the .deb files here. All credits for klaussinani
https:// github.com/Trip09/tusk/releases/tag/v1.0.0

@Trip09, many thanks! It is so simple for customers and save many time!

I have bad luck on my Mint:
dpkg: dependency problems prevent configuration of tusk:i386:
 tusk:i386 depends on libgtk-3-0.
 tusk:i386 depends on libnotify4.
 tusk:i386 depends on libnss3.
 tusk:i386 depends on libxss1.
 tusk:i386 depends on libxtst6.
 tusk:i386 depends on libatspi2.0-0.
 tusk:i386 depends on libuuid1.
 tusk:i386 depends on libappindicator3-1.
 tusk:i386 depends on libsecret-1

dpkg: error processing package tusk:i386 (--install):
 dependency problems - leaving unconfigured

```-0.
and these dependencies won't resolve when trying to install one of those libs:
The following packages have unmet dependencies:

tusk:i386 : Depends: libgtk-3-0:i386 but it is not going to be installed
Depends: libnotify4:i386 but it is not going to be installed
Depends: libnss3:i386 but it is not going to be installed
Depends: libxss1:i386 but it is not going to be installed
Depends: libxtst6:i386 but it is not going to be installed
Depends: libatspi2.0-0:i386 but it is not going to be installed
Depends: libuuid1:i386 but it is not going to be installed
Depends: libappindicator3-1:i386 but it is not going to be installed
Depends: libsecret-1-0:i386 but it is not going to be installed

hi @akvilonBrown are you sure it's i386 ? if so you can run
-> sudo apt-get -f install
this will install the required deps and Tusk.  Stay well

Actually, I have Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz,  it is i386, right?
But I see many system files with  -amd64- title, can it be so ?

This isn't a permanent fix to the porblem. Whenever I want to start Tusk I need to go into the Tusk directory and use the command 'npm start' for Tusk to work. if I start it anyother way, I still get the white screen issue.
Can anyone else confirm?
same situation here. is quite annoying actually.

@ricardovmr Just build some packages using this and install it using .deb/.rpm or AppImage package.

@akvilonBrown I'would say you have a x64 because 32-bit processors are rare today. Also because you have so many deps missing. But you can run lscpu  or uname -a
eg, run uname -a and check if you have x86_64
@ricardovmr you can compile the package as @GregDuhamel, this means instead of running npm run start run npx electron-builder --linux go to dist folder and install your package .
@ricardovmr Also if you need a .deb you can go https://github.com/Trip09/tusk/releases/tag/v1.0.0 and download the package without the need to complite.

npm start

The page is still blank

For those who prefer a linux deb package now you can get a BETA version by evernote itself at this link: https://evernote.com/intl/en/b1433t1422.
Disclaimer: I don't work for Evernote, use this software at your own risk.

For those who prefer a linux deb package now you can get a BETA version by evernote itself at this link: https://evernote.com/intl/en/b1433t1422.
Disclaimer: I don't work for Evernote, use this software at your own risk.

Amazing! It works! Thank you!


Bluetooth: controller: Fixes for CIG with two CISes and separate ACLs

Bluetooth: controller: Fixes for CIG with two CISes and separate ACLs
Prevent referencing inactive CISes by clearing state variables
after teardown. This was seen as necessary when having CISes on
different ACLs, and disconnecting ACLs in random order.
Signed-off-by: Morten Priess<EMAIL_ADDRESS>

@cvinayak, can I get your approval? - question answered.


Merge main to 2.x

Description
This PR lifts 2.x with commit history from main
Issues Resolved
#122
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

looks good to me!


Add isInteger polyfill for IE11

Object doesn't support property or method 'isInteger'

This error happens in IE11. Number.isInteger is ES6 which is not supported in IE11.
CanIUse
Number.isInteger Polyfill

Thanks @lmachens


bcbio server

Hi Brad,
while rummaging through the code, I encountered a 'hidden' server module. Is this this code still functional and for what was it used? It would help us TREMENDOUSLY is we could start bcbio as a server to which we can send analysis requests. If this code has aged, which steps need to be taken to revive this?
Example: our plan is to (eventually) package everything into a docker image, which we would run on Marathon. It would be great to be able to send an HTTP request to the running container to start an analysis. Include full iRODS integration into that (down- and upload), and some JSON api compliance and we're golden.
Thanks! And thanks for keeping gems like that in your code!
M

Arvados is an alternative.

Yes, we know, but we've already deployed several services to Marathon, and would eventually like to be able to dynamically schedule bcbio runs on our Mesos cluster. As far as I know, Arvados does not support Mesos and we don't have the resources to run both side by side. Tempting as it may be from my point of view, currently Arvados isn't an option for us =(

The best move for us would be to be able to move completely to CWL and run it on Mesos using Toil, but all of our tries so far to do that have failed, sadly

@matthdsm Sorry for the issues you are having. What you mention regarding CWL/Toil is what we're moving towards, for instance, I'll be testing Toil/AWS/bcbio relatively soon.
Could you describe a bit more what have you tried with CWL/Mesos/Toil and how it failed? Did you file any of the issues you had to BD2kGenomics (https://github.com/BD2KGenomics/toil/issues)?

hi @brainstorm,
It's been a while since we first tried, and we didn't have the time to test very thoroughly. Our main issue started with the way the mesos plugin needs to be installed and the mesos version against which it was tested (very old). We put it on the back burner for future reference and focused on added functions to bcbio first

Matthias;
Thanks for starting this discussion. I'd recommend not using the internal server, which don't really do too much beyond dispatching local jobs. I'm not sure it provides the functionality you'd need and I don't think building Mesos/Marathon support into bcbio is the right direction to go.
CWL/Toil/Mesos support seems to be a better path to getting the support you'd need. Roman is taking a look at it now and I think working through that will provide a more useful long term solution for you. If there are blockers in terms of mesos plugins/versions it would be worth raising those with the Toil team and then make decisions about suitability.
Sorry to be pushing back on your good ideas, but my experience is that to support and maintain these type of complex external interactions the best plan is to collaborate with external communities doing this work rather than trying to create everything needed inside bcbio.

Hi Brad,
I totally agree that CWL is the way to go, and collaboration is key. I took this conversation to Toil in BD2KGenomics/toil#1432.
I seems there's still some work to be done on the Toil side. I'll close this issue and take this further with the people there.
M


Visual CSS Can't be saved after resetting a color/background-color

After resetting a element's custom configuration, the visual CSS can no longer be saved because it calls an error on any line with empty values.
E.G. Here it said can't save because of line 24.

Removing the entire line instead of only the value could fix this.

Thanks for report, the issue is fixed now in version 1.2.18


Scale box drawing glyphs to fit cells for visual bliss

Summary of the Pull Request
Identifies and scales glyphs in the box and line drawing ranges U+2500-U+259F to fit their cells.
PR Checklist

[x] Closes #455
[x] I work here.
[x] Manual tests. This is all graphical.
[x] Metric ton of comments
[x] Math spreadsheet included in PR.
[x] Double check RTL glyphs.
[x] Why is there the extra pixel?
[x] Scrolling the mouse wheel check is done.
[x] Not drawing outline?
[x] Am core contributor. Roar.
[x] Try suppressing negative scale factors and see if that gets rid of weird shading.

Detailed Description of the Pull Request / Additional comments
Background

We want the Terminal to be fast at drawing. To be fast at drawing, we perform differential drawing, or only drawing what is different from the previous frame. We use DXGI's Present1 method to help us with this as it helps us compose only the deltas onto the previous frame at drawing time and assists us in scrolling regions from the previous frame without intervention. However, it only works on strictly integer pixel row heights.
Most of the hit testing and size-calculation logic in both the conhost and the Terminal products are based on the size of an individual cell. Historically, a cell was always dictated in a COORD structure, or two SHORT values... which are integers. As such, when we specify the space for any individual glyph to be displayed inside our terminal drawing region, we want it to fall perfectly inside of an integer box to ensure all these other algorithms work correctly and continue to do so.
Finally, we want the Terminal to have font fallback and locate glyphs that aren't in the primary selected font from any other font it can find on the system that contains the glyph, per DirectWrite's font fallback mechanisms. These glyphs won't necessarily have the same font or glyph metrics as the base font, but we need them to fit inside the same cell dimensions as if they did because the hit testing and other algorithms aren't aware of which particular font is sourcing each glyph, just the dimensions of the bounding box per cell.

How does Terminal deal with this?

When we select a font, we perform some calculations using the design metrics of the font and glyphs to determine how we could fit them inside a cell with integer dimensions. Our process here is that we take the requested font size (which is generally a proxy for height), find the matching glyph width for that height then round it to an integer. We back convert from that now integer width to a height value which is almost certainly now a floating point number. But because we need an integer box value, we add line padding above and below the glyphs to ensure that the height is an integer as well as the width. Finally, we don't add the padding strictly equally. We attempt to align the English baseline of the glyph box directly onto an integer pixel multiple so most characters sit crisply on a line when displayed.
Note that fonts and their glyphs have a prescribed baseline, line gap, and advance values. We use those as guidelines to get us started, but then to meet our requirements, we pad out from those. This results in fonts that should be properly authored showing gaps. It also results in fonts that are improperly authored looking even worse than they normally would.

Now how does block and line drawing come in?

Block and Line drawing glyphs are generally authored so they will look fine when the font and glyph metrics are followed exactly as prescribed by the font. (For some fonts, this still isn't true and we want them to look fine anyway.)
When we add additional padding or rounding to make glyphs fit inside of a cell, we can be adding more space than was prescribed around these glyphs. This can cause a gap to be visible.
Additionally, when we move things like baselines to land on a perfect integer pixel, we may be drawing a glyph lower in the bounding box than was prescribed originally.

And how do we solve it?

We identify all glyphs in the line and block drawing ranges.
We find the bounding boxes of both the cell and the glyph.
We compare the height of the glyph to the height of the cell to see if we need to scale. We prescribe a scale transform if the glyph wouldn't be tall enough to fit the box. (We leave it alone otherwise as some glyphs intentionally overscan the box and scaling them can cause banding effects.)
We inspect the overhang/underhang above and below the boxes and translate transform them (slide them) so they cover the entire cell area.
We repeat the previous two steps but in the horizontal direction.

Validation Steps Performed

See these commments:

https://github.com/microsoft/terminal/issues/455#issuecomment-620248375
https://github.com/microsoft/terminal/issues/455#issuecomment-621533916
https://github.com/microsoft/terminal/issues/455#issuecomment-622585453

Also see the below one with more screenshots:

https://github.com/microsoft/terminal/pull/5743#issuecomment-624940567

nit: imperative

I know this is all supposed to be vertical metrics, and I hate to be such a one-note Charlie here, but can you just run a quick check that RTL is still fine with this? It just touches a lot of the previous trouble spots

Unless RTL glyphs happens to fall in the range [U+2500, U+259F], this won’t impact them. It plugs into the same run-splitting and text analysis machinery that we already had, and which you helped ensure works with RTL.

(Thanks for keeping us honest!)

 Fascinating!

I know this is all supposed to be vertical metrics, and I hate to be such a one-note Charlie here, but can you just run a quick check that RTL is still fine with this? It just touches a lot of the previous trouble spots

@schorrm, Lookin' good to me (from that old utf82.txt file):

Screenshots (with don't scale to below 1.0f)

Font Name
https://github.com/microsoft/terminal/pull/5743/commits/9e42fc4ef4fa114c99af680cce8d3bba0f5c3492

Cascadia Code

Cascadia Patched

Cascadia MetricsTest

Consolas

Lucida Console

Anonymous Pro

DejaVu Sans Mono

Envy Code R

Fira Code

IBM 3270

Iosevka

monofur

Source Code Pro

OK, so, there's actually still one more thing:

[ ] Minor banding shows up at some font sizes (and in Anonymous Pro)

But I'm going to pull that into a new issue that may come post 1.0. This is so much better than it was for a majority of cases that I don't want to hold it up any longer.


update too bevy 0.12, updates sub plugins too newest versions

just updated the cargo.toml

I will update it soon I think, but I have a bit of a backlog since I was travelling. I was waiting on bevy_ecs_tilemap to have an in-progress 0.12 branch, and it looks like they do StarArawn/bevy_ecs_tilemap#489

Alright, it's updated on main


Websockets

There is a fix for #52 in this PR

I expect this PR to address #29, #50, #51, #52 once done

Merging this even though it's far from finished because I reorganized and fixed a bunch of stuff


GroboIL is nice

GroboIL (now called GrEmit) not only have a nice name, but also offers a nice wrapper around ILGenerator with additional type safety and validation. We definitely want to use that in both Assembler and Compiler.

LGBT


Don't show snackbar messages when working normally

If working normally, we should not show snackbar messages as they are visually distracting.
We should show messages if we cannot create a backup instead.

Similar to https://github.com/OpenEnergyTools/scl-validating/issues/1


Update address.json

Add one more bad url musk-in[.]com, tied to same wallet as another known scam getpolkadot[.]us added today as well.
Both are tied to this wallet 12rpYzbZHLmM83UcAuudQWr4cdb6xVCCe2brMQeno5isbSwK
The bad domain has also been put on a blacklist:

PS: If you have a DOT address, would be worth-while adding it to your site as well, would love to open tips for your efforts since this adds a lot of value.

I do have some DOTs stacked on a centralized exchange for some returns, but until now I had no actual true DOT wallet of mine.
Mistake corrected! And added the DOT addy to my site, thanks sincerely!
(not your keys not your crypto)

@jacogr
Actually was I supposed to add my newly created DOT wallet in the polkadot website under treasury - propose tips] section or to my own blog?

I tried to do it but I don't think it is possible as my wallet is empty to cover fees
Thanks and sorry for the trouble!

I'll submit a tip :)


add new recipe aws-cli-v2

this is not just a simple upgrade of aws-cli, this require new package system pep517 etc.

Dunfell does not support pep517 - decide not to backport this