Auth - Setting Trigger Destroys Verification Settings

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
5.1.2
What operating system are you using?
Windows
Amplify Categories
auth
Amplify Commands
update
Describe the bug
This issue is for both the Amplify and Cognito service teams, related to https://github.com/aws-amplify/amplify-cli/issues/7833, https://github.com/aws-amplify/amplify-cli/issues/7666 and https://github.com/aws-amplify/amplify-js/issues/2906
If you set a trigger (console or CLI), it removes the verification settings (e.g. resets "Which attributes do you want to verify?" to "No verification"). Setting it back to "Email only" then resets the trigger.
The only workaround AFAIK is to call the CLI with cognito-idp update-user-pool to set the desired properties all at once. Unfortunately, this will like keep popping up as the CLI will probably trigger a reset on future pushes.
Please prioritize these issues, makes Cognito unusable out of the box for common use cases and it was never this bad over the past few years. Thanks.
Expected behavior
You should be able to set a trigger and/or verification settings without one affecting the other.
Reproduction steps
If you set a trigger (console or CLI), it removes the verification settings (e.g. resets "Which attributes do you want to verify?" to "No verification"). Setting it back to "Email only" then resets the trigger.
GraphQL schema(s)
N/A
Log output
N/A
Additional information
No response

Hey @iyz91 :wave: I was able to reproduce the behavior of the attribute switching from "Email" to "No verification" by updating my auth resource with a trigger. However, I was not able to reproduce the trigger resetting. Can you elaborate on that behavior?
Reproduction steps:

amplify add auth
Manual config Do you want to use the default authentication and security configuration? Manual configuration
 Select the authentication/authorization services that you want to use: User Sign-Up, Sign-In, connected with AWS IAM controls (Enables per
 -user Storage features for images or other content, Analytics, and more)
 Please provide a friendly name for your resource that will be used to label this category in the project: 7839cognitoattrverifb45afcb8b45a
 fcb8
 Please enter a name for your identity pool. 7839cognitoattrverifb45afcb8_identitypool_b45afcb8
 Allow unauthenticated logins? (Provides scoped down permissions that you can control via AWS IAM) No
 Do you want to enable 3rd party authentication providers in your identity pool? No
 Please provide a name for your user pool: 7839cognitoattrverifb45afcb8_userpool_b45afcb8
 Warning: you will not be able to edit these selections.
 How do you want users to be able to sign in? Email
 Do you want to add User Pool Groups? No
 Do you want to add an admin queries API? No
 Multifactor authentication (MFA) user login options: OFF
 Email based user registration/forgot password: Enabled (Requires per-user email entry at registration)
 Please specify an email verification subject: Your verification code
 Please specify an email verification message: Your verification code is {####}
 Do you want to override the default password policy for this User Pool? No
 Warning: you will not be able to edit these selections.
 What attributes are required for signing up? Email
 Specify the app's refresh token expiration period (in days): 30
 Do you want to specify the user attributes this app can read and write? No
 Do you want to enable any of the following capabilities?
 Do you want to use an OAuth flow? No
 ? Do you want to configure Lambda Triggers for Cognito? No

amplify push -y, Observe email is set as expected

amplify update auth, add some Cognito Trigger (ex: email allowlist filtering)
amplify push -y, observe "no verification" is now set

NOTE: I was able to re-enable email verification in the Cognito console (after enabling MFA due to configured SMS role), and confirmed it was unaffected by subsequent pushes

I just called 'aws cognito-idp update-user-pool --user-pool-id= --account-recovery-setting "RecoveryMechanisms=[{Priority=1,Name=verified_email}]"' and it reset the trigger field.
The only way that currently works is to call update-user-pool with all the fields specified at once.

Thanks for the information! Just wanted to verify to make sure it wasn't reset by the Amplify CLI 🙂

My pleasure and thank you as well. I'll comment back here if the CLI does reset it as well but it seems its some config issue within Cognito itself on top of the CLI issues.

@josefaidt I am able to reproduce the issue by setting the Add users to group in the Post Confirmation trigger via the client

Thank you for confirming you are also experiencing this issue and for providing those details, @ninjaKris!

This pull request seems to suggest that it is an Amplify CLI fix, and an easy one. I believe this pull request is the fix, right?
https://github.com/aws-amplify/amplify-cli/pull/7671

Closing in favour of https://github.com/aws-amplify/amplify-cli/pull/7671


UMap support

Hello,
First of all, I want to thank you for this library. I've been looking for a library that I can use to integrate dimensionality reduction techniques into our tool for our paper, and this is perfect for that. (I make sure to cite  :))
I would like to ask about the current situation with the UMAP. Is it ready to use?
Also, as a side question, Are you guys aware of any good library for the K-NN classifier?

Hello @MohammadFakhreddin,
Thank you for the interest and nice to read you are finding the library useful.
I might be able to help with the k-NN question. Even though tapkee already includes tree data structures for it as several dimensionality reduction techniques are based on nearest neighbors, you could take a look at Shogun. This notebook should help to get a quick idea of how you can do k-NN in Shogun using the Python interface. Even though the notebook is about LMNN (you can think of it as an extension to k-NN), see e.g. code cell [14] for an example applying k-NN in a metagenomics dataset.
So :)
if you are already using tapkee and are attracted to the diving in its code a bit, you will find the NN code and eventually be able to modify to get a k-NN classifier from it and you won't need any other library;
if you want a more readily available solution where you can call a k-NN classifie, Shogun could help better, but it may require some effort getting it work, which can widely vary depending on what system you are using (OS, package manager, compiler, ...) and what version of Shougn you would like to use.

@iglesias Thanks a lot!  I look into it and try to implement something based on that.
At the moment, I'm trying to keep the build as simple as possible, so I do my best to avoid a complex library. One of our goals is the project's accessibility. We have some prototypes in Python using Scikit Learn, but currently, my aim is the project's longevity and ease of build.
As a side note, I think the cmake minimum version is too high :)
Let me know if anyone knows about the current state of the UMAP library.

Hi @MohammadFakhreddin
thanks for reaching out! The UMAP should be a good addition to the library but none of us two have got enough time recently to implement it. As of now there is no implementation even in a branch.

Indeed. On Open Source, I am with the CodeQl stuff and making contributions to GitHub’s coding-standards repo. Would I look into something in tapkee atm, I’d be more interested in some topic related to that (even widely, such as safety with Circle or just even trying the new clang real-time sanitizer on it).
I recalled on umap there was already this https://github.com/lisitsyn/tapkee/pull/95
The umap python repo on github looks quite popular, and there’s also a c++ repo. What would be the goal of adding a new method DR now to tapkee? I wondered and I couldn’t think of any besides completeness in tapkee.

So, I integrated Tapkee into my project and fed it the dataset I used for testing PCA using OpenCV. Strangely, it took 3-4 seconds for OpenCV PCA, while for Tapkee, it took 4-5 minutes. I noticed that OpenCL was present in the cmake. Are you guys using OpenCL for optimization? Can it be that by not including OpenCL in my project, I made Tapkee much slower than OpenCV?
(I used the Passiflora dataset, which is a very large dataset. It worked well with smaller datasets :))
cmake_minimum_required (VERSION 3.16)

project (Tapkee  LANGUAGES CXX)

set (CMAKE_CXX_STANDARD 23)
set (TAPKEE_INCLUDE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/include")

include_directories("${TAPKEE_INCLUDE_DIR}")

add_library(tapkee_library INTERFACE)
target_include_directories(tapkee_library INTERFACE "${TAPKEE_INCLUDE_DIR}")

Hello @MohammadFakhreddin,
assuming I understood your message and questions correctly after reading them a few times, a comparison between OpenCV with GPU acceleration and Tapkee without, providing that PCA is amenable to data-parallelism, would obviously result in a large difference in a large dataset.


Data source tab content

This PR adds the approve language to the data source tab and fixes a type in the quickstart right rail.

@bradleycamacho for a review of this language.


Design system workflow card

#712

Uses determinate progress bar #622

@LibbyUX Please review and let me know if everything looks good. I've added a progress bar to the data and color map upload cards in the create vis page, so you can test that out as well.

Also @edlu77 I just want to mention that the progress bar is exquisite!!! Thank you!

@LibbyUX A lot of these issues are addressed in PR #773, which has the updated Delete File Button component and updates to color and styling in the app. It would probably make sense to import some of those changes here though.

@edlu77, thanks for pointing me in the right direction for #773. The delete button hover state and the tooltip cards look great over there.
Also, please disregard anything about the text field inputs/selects at the moment! I will submit a design system update when this is ready, so it's irrelevant for this review right now.
Per our conversation just now at my desk, I'll wait for you to ping me when this one is ready for review again!
Thanks so much for everything!


Make moduleVisitor extendable by plugins

Hello,
This is a feature request (kind of a continuation of #906),
Some modules require module paths for some calls (like the jest.mock() in Jest). As a developer, I would like eslint-plugin-import to apply its rules to paths to modules in other places different than require() or import calls so that I can quickly catch possible issues with such calls (i.e. the path in some call is pointing to an unresolved module).
Given this requirement is out of the scope of eslint-plugin-import (it shouldn't/can't keep track of paths used in calls other different modules), it can instead provide an interface for other modules to extend the scope of the default moduleVisitor (like the one for custom resolvers).
For instance, As a module author, I should be able to write an eslint-import-visitor-jest module that exports a function such as:
function checkJestMocks(visitors, checkSourceValue) {
    const currentCallExpression = visitors['CallExpression'];
    visitors['CallExpression'] = function (call) {
        if (currentCallExpression) currentCallExpression(call)
        if (call.callee.type !== 'MemberExpression') return
        if (call.callee.object.name !== 'jest') return
        if (call.callee.property.name !== 'mock') return
        if (call.arguments.length !== 1 || call.arguments.length !== 2) return
        const modulePath = call.arguments[0]
        if (modulePath.type !== 'Literal') return
        if (typeof modulePath.value !== 'string') return

        checkSourceValue(modulePath, call)
    }
}
module.exports.visitor = checkJestMocks;

Then a developer can include my module and point eslint-plugin-import to use the exported visitor via a setting.
I would like to write this new feature if you consider and accept a PR for this.

I'm trying to understand the ask here.
eslint rules do not typically expose AST node information (except for no-unrestricted syntax). Additionally, "what the rule does with a node" depends highly on what kind of node it is. There's no generic way to "handle a node", if only you had a way to point to it.
Is your goal here so that jest.mock calls are treated the same as require calls, for the purpose of a specific rule? (seems like no-unresolved?)

Yes, one application of this feature is to get jest.mock treated as a require for rules like no-unresolved, no-restricted-paths, no-absolute-path, no-useless-path-segments, etc, in general rules that target the path being imported. All those rules depend on moduleVisitor if I'm not wrong.
Since all those rules can be applied to a jest.mock call, As a module author, I don't want to reinvent the wheel. If you provide an interface for other module authors to extended what is treated as module then I will only have to care about my plugin is compliant with the interface. And, in exchange, you will only need to care about getting the interface working.
Review your codebase I see you do something similar with custom resolvers, a developer can include a module that adds a new resolver and then link it to eslint-plugin-import via the eslint settings. In the same way, a developer should be able to include a module that adds a new "visitor" and then link it to eslint-plugin-import via the settings.

A new resolver, yes, but not a new resolution API.
What you want seems fine for jest.mock, but I don't think it would be at all a good idea to basically open the floodgates and allow anyone to treat any arbitrary AST node as if it had require or import semantics.
I do see how it's technically feasible, if by "visitor" you mean something that would provide an AST node name, and a function that returns some kind of generic container that can indicate, explicitly, the specifier to look at.
What other use case could this have? Jest is, thankfully, the only thing I know of that's invented completely non-standard and impossible-to-standardize semantics for module loading. Are there others?

For now, the most popular use case would be jest.mock but I know there are other libraries that provide alternative ways of importing modules such as rewire. Both of them are used to make testing easier.
As for the interface, what I'm thinking is something like the example I provided in the first post. The interface would be function extendVisitor(visitors, checkSourceValue), so eslint-plugin-import exposes the list of visitors and the function that triggers the visit.
You can alternatively provide something more restricted like function extendVisitor(node): string, so you expose the node itself and expect as return the string literal that needs to be visited, but I believe such version is a bit more complicated to implement,  My first proposal is based on already existing logic.

Hmm.
jest.mock, rewire, and proxyquire are indeed three such use cases.
I would definitely want something maximally restrictive - so that these three cases, or something exactly like them, are all that's permitted.

I'd be more than happy to review a draft PR implementing it :-) it's hard to commit to accepting it before seeing the implementation.
Unless you already have some, don't worry about tests until we can be sure it's not going to be a waste of effort.


Add 'Avatar Change' to wrist feed filters / VRCX notifications

Seeing as VRCX's wrist feed and notifications already covers most things from the Feed and Game Logs, figured it'd make sense to include avatar change in there as well. At least for the ones VRCX can see anyway provided someone isn't using a custom profile picture.

do you mean by seeing if a user changes an avatar in public, or if they are friends?
both could be possible, but might not be cause of mods.
i would feel like trying to request everyones avatar data in larger instances could cause lots of api requests and flag accounts....

Would take more time than it's worth to add.


Update System.IdentityModel.Tokens.Jwt to 5.0.0-rc1-211161024

You are depending on two different versions of this dependency (5.0.0-rc1-211161024 for .NET Core and <IP_ADDRESS>250711 for .NET 4.5.1) and this is causing conflicts.
I have noticed that most APIs on ASPNET5 RC1 are on v5. You should try to use only that version.

BTW, bellow you can find the error I am getting when running on .NET 4.5.1. It works perfectly with .NET Core (dnxcore50). I am assuming the version difference on System.IdentityModel.Tokens.Jwt to be the problem.
=> RequestId:0HKOT6M4ABETF RequestPath:/connect/authorize
      An unhandled exception has occurred while executing the request
      System.TypeLoadException: Could not load type 'System.IdentityModel.Tokens.Serializer' from assembly 'System.IdentityModel.Tokens.Jwt, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
         at IdentityServer4.Core.Services.Default.DefaultTokenSigningService..cctor()
      --- End of stack trace from previous location where exception was thrown ---
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.TransientCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.TransientCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.TransientCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.TransientCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.TransientCallSite.Invoke(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.<>c__DisplayClass12_0.<RealizeService>b__0(ServiceProvider provider)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
         at IdentityServer4.Core.Hosting.EndpointRouter.Find(HttpContext context)
         at IdentityServer4.Core.Hosting.IdentityServerMiddleware.<Invoke>d__3.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at IdentityServer4.Core.Hosting.BaseUrlMiddleware.<Invoke>d__2.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.AspNet.Cors.Infrastructure.CorsMiddleware.<Invoke>d__7.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.AspNet.IISPlatformHandler.IISPlatformHandlerMiddleware.<Invoke>d__8.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at Microsoft.AspNet.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()

We can't do that right now because of a bug in the v5 version. We will at RC2.

Ok.
Do you have a workaround for this specific problem I just posted om the error log?

Not sure what your problem is, works for us.
Sent from my iPhone

On 15.01.2016, at 12:43, Giovanni Bassi<EMAIL_ADDRESS>wrote:
Ok.
Do you have a workaround for this specific problem I just posted om the error log?
—
Reply to this email directly or view it on GitHub.

The conflict came from using Microsoft.AspNet.Authentication.OpenIdConnect version 1.0.0-rc1-final on the same host. After removing, the problem was solved. I think it is using version 5 of System.IdentityModel.Tokens.Jwt and that is conflicting. I have solved the conflict, but this is still an issue. Let's wait for RC2, then.

I am having the exact same issue. Is there something we can do to get unblocked?

@leastprivilege I see that System.IdentityModel.Tokens.Jwt is still in different versions on the latest project.json. This was closed as not going to be fixed, or is it being fixed some other way?

Quoting my above answer

We can't do that right now because of a bug in the v5 version. We will at RC2.

If the bug is not fixed, the issue shouldn't be closed. This is unexpected behavior, it is an open bug.

There is an open todo issue for upgrading to the new jwt library. Feel free to re open if that helps.
Sent from my iPhone

On 26.01.2016, at 10:59, Giovanni Bassi<EMAIL_ADDRESS>wrote:
If the bug is not fixed, the issue shouldn't be closed. This is unexpected behavior, it is an open bug.
—
Reply to this email directly or view it on GitHub.

#27, right? I assume that that will fix this one, so I will follow that one. Tks.

this one
https://github.com/IdentityServer/IdentityServer4/issues/24

I have the same situation with having a client (webapi) and host in the same project. The problem was that package"Microsoft.AspNet.Authentication.JwtBearer": "1.0.0-rc1-final" uses System.IdentityModel.Tokens.Jwt (5.0.0-rc1-211161024) whereas "IdentityServer4": "1.0.0-beta1" depends on "System.IdentityModel.Tokens.Jwt": "<IP_ADDRESS>250711" like giggio said.
So I set a dependency for 4.0 in my project and load the JwtBearer package normally like so:
"dependencies": {
   ...
   "Microsoft.AspNet.Authentication.JwtBearer": "1.0.0-rc1-final",
   ...
},
"frameworks": {
    "dnx46": {
      "dependencies": {
        "System.IdentityModel.Tokens.Jwt": "<IP_ADDRESS>250711"
      }
    }
  },

However, I am not able to call this in my Startup.cs:
System.IdentityModel.Tokens.JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();
Since DefaultInboundClaimTypeMap does not exists.
What would be a workaround for this?

yes - you have to wait for RC2 for this to get fixed.

First, this is still an issue.  We're at 1.5 years on this one...
Also, I was able to downgrade to System.IdentityModel.Tokens.Jwt <IP_ADDRESS>3061554 and that seems to be working.

@mmulhearn thanks you saved me.


[Bug] Ambiguous name of Operation as a atomic term ^name or statement name(args)

Describe the bug
This issue is come from PR #37:

According to NAL (2012):
An atomic operation is represented as an operator (a
special term whose name starts with ‘⇑’) followed by an argument list (a
sequence of terms, though can be empty). (P146)
an operation is a special type of event that is realizable by the system. (P150)
So I think "Operation as an atomic term" (e.g. ^op) in pynars\Narsese_py\operation.py might need to be renamed Operator to distinguish it from "Operation as an statement". (e.g. f(x, y) or <(*, x, y) --> ^f>)

To Reproduce
See pynars/Narsese/_py/Operation.py
Expected behavior
This is a conceptional issue, It only affects the development of code

An atomic operation is represented as "an operator followed by an argument list". As I understood, name(args) is an atomic operation. By contrast, a compound operation is a sequential/concurrent compound of operations, like (op1(args1), op2(args2), op3(args3)).

An atomic operation is represented as "an operator followed by an argument list". As I understood, name(args) is an atomic operation. By contrast, a compound operation is a sequential/concurrent compound of operations, like (op1(args1), op2(args2), op3(args3)).

Yeah, you're right. I understand what you say.
In Narsese, The "atomic operation" of the form "name(args)" is actually the syntactic sugar of the Narsese statement of the form "<(*, args) --> ^name>" - which is the original meaning of "an operator followed by an argument list".
But now, what I see in the class Operation is that it actually corresponds to "an operator" in the sentence rather than "an operator followed by an argument list".
So based on this, I think the class Operation in pynars/Narsese/_py/Operation.py should be renamed Operator to clarify its meaning, which is exactly what you said in your reply as 'Operator'.

That make sense. ^name is an operator. we can change the class name in the code.

fixed by https://github.com/bowen-xu/PyNARS/pull/46


BooleanRegularExpression Spec

Added spec for BooleanRegularExpression

Just those trivial comments.  Very nice work here!

Updated!

Nice!


Separate the e2e from component test coverage

Save the intermediate coverage into own folders, probably by using Cypress.testingType (e2e or component) as a suffix

They combine together out of the box. Maybe this enhancement isn't needed and the issue is convenient to have.


hive Partition location does not exist:

How do I ignore partitions without data

@qianmoQ you can add this to your catalog properties file:
hive.ignore-absent-partitions=true

Also, i invite you to our slack. it's a more interactive place for how-to questions.
See you there!


changed JobFiltet.latest to non primitive Boolean to handle null valu…

…es. Also changed return type for getLatestJob api to a list.

The getLatest api is now returning a list of jobs instead of a job. I made this change since jersey was complaining about returning a null job in case of no jobs returned for the user. instead of returning a dummy job instance and adding checks in the servlets, i am returning a empty arraylist like in the getalljobs method and there was code in the servlets previously to handle the empty arraylist.


Nodes using Flipbook Frame Blend Type Lerp do not render

When using an EffekseerEmitter (3D type) to play an effect that uses "Lerp" as its "Flipbook Frame Blend Type" do not render in Godot 3 engine.

That feature does not work with Godot3.
I apologize for this limitation, which was not documented.
If you want to use flipbook frame blending, you have the option of using Godot4 or creating it in Material.

Thank you for the info! I will find a work-around.


Warzone VK_KHR_surface not supported

apitrace log was blank
Software information
Call Of Duty: Warzone (Modern Warfare 2019)
System information

GPU: GTX 1050
Driver: <IP_ADDRESS>89
Windows 10
DXVK version: v1.8

Log files

d3d11.log: No log

dxgi.log:
ModernWarfare_dxgi.log

info:  Required Vulkan extension VK_KHR_surface not supported

That indicates that there's an issue with your graphics driver. It's not installed correctly.
Also, CoD MW (and Warzone) uses D3D12.

Yeah, wrong API + also it's a setup issue on your end, not a bug.

You can force run on DX11 on the launch arguments.

Yeah, wrong API + also it's a setup issue on your end, not a bug.

You can force the game to run on DX11 on the launch arguments.
cant see whats wrong with my setup, updated driver and everything.


uninitialized constant ActionController::TestRequest

Hi all
I have NameError (uninitialized constant ActionController::TestRequest) at draper/lib/draper/view_context/build_strategy.rb:41. Decorator called from Grape API
I think this error happens because of this commit 5d9e6919c4736fa
Adding require 'action_controller/test_case' solves error, but it looks like a bad idea to require test code to solve issues
gem 'rails', '5.0.0'
gem 'draper', '3.0.0.pre1'
gem 'grape', '0.16.2'

Looks like duplicate of https://github.com/drapergem/draper/issues/755


swiftpm2nix: fix prefetch regression by downgrading nix

Ref: https://github.com/NixOS/nix/issues/11681
I tested multiple Nix versions and 2.19 seems to be the latest working one.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

2.19 is not supported by the Nix team, so this feels a bit iffy to me. Can we fix the issue in swiftpm2nix or Nix instead?


Review Toolbar.Item and Toolbar.PopoverItem

We should check which props we want to expose for each of those 2 components.
Right now we are exposing too many props and we should have an intermediate private component which exposes those.
Example: isPopover should not be exposed.

We shouldn't expose isPopover, and popoverInteractionKind is unnecessary for Toolbar.Item. It should be moved to the Toolbar.PopoverItem level.

popoverInteractionKind is unnecessary for Toolbar.Item

it is on the toolbar and that is fine IMO. I don't think a toolbar should mix different interaction kind together. It should be documented that it only affects the popover items.


Inconsistency of permission code

When I was using ths ACL, I found that the Permission code was inconsistent. Can I remove 'Permision.ANY' to make it consistent with the permission code in tools?
rocketmq-acl module

rocketmq-tools module

topic.json

IMO, class Permission is used for client, class UpdateTopicPermSubCommand is used for server.


Update Traditional Chinese

Update Text Translation
Grammatical reorganisation
Correcting typos

Thank you so much, will merge after I'm done with some features and it will be available next release.


Add storybook logo

:tada: This issue has been resolved in version 0.12.26 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ESLint + Typescript results in dependency errors since v9.0.0 inclusion on svelte@latest

Describe the bug
When using TypeScript syntax and ESLint with svelte@latest, dependencies cannot be resolved.
Reproduction
npm create svelte@latest example-project

Skeleton project
Yes, using TypeScript syntax
Add ESLint
cd example-project
npm install

Logs
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/eslint
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/typescript-eslint
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

# npm resolution error report

While resolving<EMAIL_ADDRESS>Found<EMAIL_ADDRESS>node_modules/eslint
  dev<EMAIL_ADDRESS>from the root project

Could not resolve dependency:
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/typescript-eslint
  dev<EMAIL_ADDRESS>from the root project

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
    Memory: 21.00 GB / 31.92 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 123.0.6312.107
    Edge: Chromium (123.0.2420.81)
    Internet Explorer: 11.0.19041.3636

Severity
blocking an upgrade
Additional Information
No response

I have the same issue, seems to be a major bug.

This issue seems to have been introduced in https://github.com/sveltejs/kit/pull/12089
typescript-eslint does not yet support ESLint v9 ( https://github.com/typescript-eslint/typescript-eslint/issues/8211 )
When running npm create svelte@latest and selecting both ESLint and typescript it currently adds both ESLint v9 and typescript-eslint as a dependency causing the conflict
https://github.com/sveltejs/kit/blob/main/packages/create-svelte/shared/%2Beslint%2Btypescript/package.json
https://github.com/sveltejs/kit/blob/main/packages/create-svelte/shared/%2Beslint/package.json

Ah, it seems we may have upgraded too early. Despite the version warnings and the libraries not being officially compatible it should still work: https://github.com/typescript-eslint/typescript-eslint/issues/8211#issuecomment-2044094079
I wonder how long it will take for a new version to roll out though and if we need to rollback in the meantime :thinking:

I guess the other potential solution would just be to leave the typescript-eslint rules in place, but comment them out and add a note that you should install typescript-eslint and uncomment the rules once https://github.com/typescript-eslint/typescript-eslint/issues/8211 is fixed. This might provide an easier upgrade path for people since it's a bit complicated to upgrade from v8 to v9

Thank you for both the temp workaround advice and subsequent quick resolve @benmccann  ❤.

ts-lint v8 will support eslint v9
Until it is the main version, you have to use the alpha: https://github.com/typescript-eslint/typescript-eslint/issues/8211#issuecomment-2106427365


Added 502 Bad Gateway to Status enum

As-per RFC7231 section 6.6.3.

Usually I would ask you how many times were people be using that in order to justify adding it, but it's quite small and doesn't really harm performance, so I'll give you a pass. However, just adding a bunch of stuff because it's on the RFC (unless it's absolutely required, i.e. something the client may send you and you have to interpret) is not taken lightly here as one of the main goals is to keep NanoHTTPD lean.
This being said, I'll accept your commit as soon as I verify where that error comes from.

Given how little impact it would have, I'd suggest including all commonly-known status codes.  E.g., I was just looking for 504 Gateway Timeout which is likewise missing.  Not a big deal, but probably worth including that as well.  Either that, or an implementation of IStatus that allows for custom codes and messages, so they can be added easily by the end user.


new: add support for kernel side simple consumers

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
/area driver-kmod
/area driver-ebpf
/area libscap
/area libsinsp
What this PR does / why we need it:
The PR introduces kernel side support (both kmod and eBPF) for filtering syscalls; right now, simple consumer mode can be enabled directly kernel side, instead of filtering in userspace.
In details:

a new dep was added for linux builds: libaudit. It is needed to fetch syscall number given syscall name
kmod g_events_mask is now per-consumer
eBPF will mark syscalls as uninteresting while building the shared syscall map
libsinsp expose a new API sinsp::set_simple_consumer() to enable kernel side simple consumer
falco will be updated using the new api

The changes should help falco users to reduce number of drops in syscalls-intensive environment;
some benchmarks using stress-ng.
Note that baseline (ie: abscissa) means "same benchmark run without falco", and benchmark values are intended as performance hit from baseline; thus the lower the better!
Falco with kmod:

Drops:

Falco with eBPF:

Drops:

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

new: added a simple consumer mode with kernel side filtering.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @FedeDP. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/cc @gnosek @leogr

/ok-to-test

@FedeDP: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs

build-libs-bundled-deps
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs

build-libs-bundled-deps
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-bundled-deps

build-libs-with-chisels
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

It seems like libaudit is failing to build; i'm gonna try and fix it!

It seems like our build-libs image is missing automake package that provides the aclocal executable.

/retest

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs

build-libs-with-chisels
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-with-chisels

build-libs-bundled-deps
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-with-chisels
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-with-chisels

build-libs-bundled-deps
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-bundled-deps

build-libs
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-bundled-deps
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-bundled-deps

build-libs
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs

build-libs-with-chisels
37e41100889e11a4aa66bed6c16922669f5c423e
link
true
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@FedeDP: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
ab6f05a1dd4a3cd26aafbe1ccbff85085d0128b8
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Maybe for the initial version there's a full array of skip/no-skip syscalls at the libscap level, but the only choice you can make at the sinsp level is to skip EF_DROP_SIMPLE_CONS events. I think letting a user pick-and-choose the specific syscalls they want will lead to a lot of confusion, as the filterchecks often depend on other events in unpredictable ways. For example, the process and container filterchecks require clone/fork/execve events in order to work, but if a user only selected open events, they would lose this process/container information.
The most complete solution would involve creating a map of dependencies between events and requiring dependent events (as you started to do in sinsp::set_event_of_interest), but honestly I think it's not required for now.
This would also skip the dependency on libaudit, btw, which I'm a bit wary of--is that going to be truly portable across all linux kernel versions? (Think centos, where they have really old kernels and keep pulling back patches).

I think letting a user pick-and-choose the specific syscalls they want will lead to a lot of confusion, as the filterchecks often depend on other events in unpredictable ways.

I agree!

The most complete solution would involve creating a map of dependencies between events and requiring dependent events (as you started to do in sinsp::set_event_of_interest), but honestly I think it's not required for now.

+1 on this too; i didn't want to create yet another map for this; but if we are going to allow eg: a conf-based syscall selection, the map will be mandatory.

This would also skip the dependency on libaudit, btw, which I'm a bit wary of--is that going to be truly portable across all linux kernel versions? (Think centos, where they have really old kernels and keep pulling back patches).

I think it is; libaudit is a pretty old piece of code (RHEL-4 already had it): https://people.redhat.com/sgrubb/audit/

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please ask for approval from mstemm after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test build-libs

/retest

LGTM label has been added.  Git tree hash: 961921cb3d1d3f6ceca29b5fc9d6fb5bdade1ee1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Following a discussion with @gnosek , and given that @mstemm too was not happy with libaudit, i decided to drop it entirely.
It now goes as follow: sinsp does not nothing about real syscalls number (ie: it has no access to either g_syscall_table nor g_syscall_routing_table); so, the right choice is to let sinsp fill the syscalls_of_interest set (now named m_ppm_sc_of_interest) using PPM_SC_x indexes; then is up to scap to convert the m_ppm_sc_of_interest to its internal syscall_nr based representation.
With this change, we are not able to kill libaudit :)

Squashed and cleanup up history a bit. Moreover, rebased on master.

LGTM label has been added.  Git tree hash: b4a8e38fabeeb2d715d5d1bb066451a0a59dd6ba

It seems like build-libs-bundled-deps failed (timed out?).

/retest

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

@gnosek @leogr had to rebase on master because of conflicts.
Can you re-approve? Thanks!

LGTM label has been added.  Git tree hash: 949930d81535f66b7a1b12a57e1fc779a96376d0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


undefined document links on query result

I have the following template query to list notes with a specific tag:
{{{csharp select name render [[Library/Core/Query/Page]]}}}

The result includes a note with the name undefined that points to nowhere:

This happens in some queries and not in all of them; I could not see an obvious pattern as well.

Do you have anything tagged with csharp that is not a page? An item? A paragraph? Likely you do. You can work around this by using page where tags = "csharp" instead.

Do you have anything tagged with csharp that is not a page? An item? A paragraph? Likely you do. And those objects don't have a name attribute. You can select only pages by using page where tags = "csharp" instead.

Well it looks like you nailed it. I did not know that you can tag paragraphs or items, and I have no idea how that is done, but apparently I have done it.
Thanks!


Develop

Coverage increased (+0.4%) to 85.034% when pulling 34b3703856c58a544a95a0e4391003966fbde3a1 on develop into 75e5245fa334e9c7b6df5c82c7c1eb5705b43d2a on qa.


Copy change

Copy change to better reflect what the squirrel button does. Just a small annoyance of mine since the new behavior of the release notes/upgrade path isn't to jump to the release notes but to go to the "about" page where you can click another button to get to the release notes.
Maybe there's better copy still, but I figured I could at least get the ball rolling!

Merged this change in with #29. Thanks for the contribution!

No thank YOU for all your hard work, @lee-dohm!


Scala Gears using AsyncHttpClient

The Gears folks seem to prefer using an asynchronous HTTP client:

Note though that it should generally be avoided to have such long-running, not awaiting (especially: blocking) code, because it occupies a carrier thread. You should instead try to wrap the async API which does lend more to our idioms:

(Source)
The reason is unclear to me though, as Gears uses Loom threads, and requires Java 21 to run.

That is bizarre as I thought the whole point of Loom was to use blocking libraries.  But thanks for investigating!


Initial commit etcd certs

@enxebre we were talking about providing per-node certs for etcd the other day (i think?) - Might want to build that in here?

Yep, we can probably add the deploy bit here and then create follow ups for supporting loop over multiple machines


self is not defined

ReferenceError: self is not defined
at Object. (/node_modules/.pnpm/qrcode-vue3@1.4.17_vue@3.2.26/node_modules/qrcode-vue3/lib/index.js:1:248)

Any update on this? I have the same issue...

same here on ssr.

Same here. We're running the project locally as an SPA but it'll be SSR when it hits prod. The person who initially did the work has devved it with no issues but when we check out their branch and try to run the project, we see this error.

I added the following to nuxt.config.ts:
export default defineNuxtConfig({
  plugins: [
    { src: '~/plugins/qrcode-vue3', ssr: false, mode: 'client' },
  ],
  ...
})

While my plugins/qrcode-vue3.ts looks like this:
import QRCodeVue3 from "qrcode-vue3";

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.vueApp.component("QRCodeVue3", QRCodeVue3);
})

It works for me.
(stole solution from here)

I added the following to nuxt.config.ts:
export default defineNuxtConfig({
  plugins: [
    { src: '~/plugins/qrcode-vue3', ssr: false, mode: 'client' },
  ],
  ...
})

While my plugins/qrcode-vue3.ts looks like this:
import QRCodeVue3 from "qrcode-vue3";

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.vueApp.component("QRCodeVue3", QRCodeVue3);
})

It works for me. I'm guessing it does not work with SSR, but it's good enough for me. (stole solution from here)

This looks promising! I'll try and give it a go when I can, thanks :)

I noticed it gives a warning. Don't know how to remove it :/


'videoQuality' feature is not working.

I have only tested in Android, 'videoQuality' feature is not working. I recorded a video of 10 seconds with videoQuality 'low' and it gives me a size of 51 MB and BitRate is 41921 kbps.
As well as 'durationLimit' is also not working. I set it to '5' but it is exceeding to 5.

+1


feat: More InertialStatus stuff

Describe the changes this PR makes. Why should it be merged?
Adds the ability to fetch calibration orientation and auto calibration flags from the IMU.
Additional Context
None

I keep putting these in the wrong repo :/


Asserting application exit

From<EMAIL_ADDRESS>on March 23, 2012 06:53:46
Is it possible to assert that the application exited itself, after giving it a KeyEvent.KEYCODE_BACK for example?
If not, it might be useful.
Cheers,

Jarno

Original issue: http://code.google.com/p/robotium/issues/detail?id=238

From<EMAIL_ADDRESS>on March 26, 2012 14:10:02
No that is not possible. You can however assert that the last activity has lost focus.
Status: Invalid


CLN polish logreg PR

Codecov Report

Merging #58 (6e4d00d) into master (b8ce7d3) will increase coverage by 9.25%.
The diff coverage is 68.41%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
+ Coverage   56.19%   65.44%   +9.25%
==========================================
  Files          12       11       -1
  Lines        1098      738     -360
  Branches      242      115     -127
==========================================
- Hits          617      483     -134
+ Misses        406      224     -182
+ Partials       75       31      -44

Impacted Files
Coverage Δ

andersoncd/tests/test_docstring_parameters.py
73.91% <ø> (-0.73%)
:arrow_down:

andersoncd/penalties.py
44.76% <44.76%> (ø)

andersoncd/datafits.py
52.23% <52.23%> (ø)

andersoncd/solver.py
68.27% <68.27%> (ø)

andersoncd/data/synthetic.py
72.41% <69.23%> (-18.50%)
:arrow_down:

andersoncd/estimators.py
92.39% <92.39%> (ø)

andersoncd/__init__.py
100.00% <100.00%> (ø)

andersoncd/data/__init__.py
100.00% <100.00%> (ø)

andersoncd/tests/test_estimators.py
100.00% <100.00%> (ø)

andersoncd/utils.py
28.76% <0.00%> (-4.11%)
:arrow_down:

... and 7 more

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 e298026...6e4d00d. Read the comment docs.


[HOLD] Add snmp tcpdump doc

What does this PR do?
Add snmp tcpdump doc
Motivation
Can help troubleshooting

@kayayarai Do you mind having a look again at the PR ? I think I addressed the feedbacks.


Add volunteer Tuhin Bar

Got some issues with the previous PR. So made a new one.

Awesome. Thank you!


[Huge] Alternative File-Type extension for typescript files (.ts = mpeg-2 video)

Suggestion
Huge request. One thing that I don't like about typescript is the file extension itself. ".ts" was already reserved for mpeg-2 video long before anyone thought about shipping JS apps with the complexity we see today.
This causes a lot of problems:

backup tools consider them as videos and handle them differently
nearly every file management/operation tool think it's a video (file recovery, search, remote access, ...)
file explorers think it's a video (tested on windows and macOS)

it opens the file in a video player per default <=> changing the default makes no sense as proper .ts (actual videos) would open up in a text editor
os specific features like code-preview (quicklook) stop working (see https://github.com/microsoft/TypeScript/issues/25945)
wrong icons

file patterns (e.g. web servers, custom apps) that are not optimised for the existence of typescript send typescript files with wrong mime type or apply the wrong handling per default <=> again changing this manually breaks handling of actual video files
even vscode is confused (see https://github.com/microsoft/TypeScript/issues/21136)

I think giving typescript the extension ".ts" was a mistake.
As there is just no simple solution, we could introduce an alternative file extension like ".reallynotavideo", ".tscript", ".tsc", ... (I really don't care).
🔍 Search Terms

video
mpeg-2

Somewhat related issue: https://github.com/microsoft/TypeScript/issues/25945
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

=> However, it would still be a breaking change and could also require a lot of reconfiguration (e.g. file-patterns).
⭐ Suggestion
Introduce an "official" alternative file extension that can be used ootb for typescript files (e.g. ".tsc", ".tscript", ...).
📃 Motivating Example
See above
💻 Use Cases
See above

How does an alternative file extension benefit you?  If you're consuming other people's work that uses the normal extension, you'll still have the same issues.

@nmain True, to really fix this problem the whole community must adopt a new file extension. I just don't understand why they went with .ts in the first place. This is a huge problem as a file extension should tell the system or other software what the file is about. Confusing one text format with another is not that bad but creating ambiguity between a common media/video format and a code-file is (see linked issues above).

This is a huge problem as a file extension should tell the system or other software what the file is about.

I can count the amount of times I encountered .ts mpeg files on one hand. Haven't heard of anyone struggling with this either. I would say this problem is rather niche, definitely not huge.

You can use .tsx even if you're not using JSX syntax. Think of it as the "TypeScript eXtension" if that helps 😉

While using tsx is definitely an option to circumvent the problems mentioned above it breaks semantic consistency. Using tsx in a context without jsx-elements will certainly lead to confusion when sharing code as the assumption is: tsx will contain jsx elements so it‘s probably code for the view.

If it makes you feel any better, even if we did add a brand new file extension (which we won't), we'd almost certainly eschew the ts/tsx distinction and just have it only be tsx grammar. The <T>expr syntax has largely fallen out of favor.

Thanks for the statement. I just wanted to raise awareness that file extension ambiguity is a thing (and it‘s annoying).

This isn't a huge problem day-to-day, but it can cause problems when opening a folder full of .ts files in Windows Explorer - the file manager thinks they're all video files and often spends several seconds trying to load their thumbnails, during which time the Explorer window is unresponsive.  Sometimes it even crashes.  It can be fixed by switching the folder to Details view, but that setting isn't always remembered.
macOS Finder sometimes stumbles in the same way.

If you're going to make something that implicitly opens every single file and scans every single one of them for content, it has to be bulletproof for both performance concerns and security concerns. File explorers should be incapable of crashing or performing slowly regardless of the inputs.

I definitely agree, but sadly we don't live in a perfect world. 😞  That being said, I was a bit surprised to find out that Finder was affected by this, since I always thought macOS used file content to determine the types of files in addition to their extensions.

Cost me a few hours wondering why MacOS Spotlight finds text in [compiled] .js files but not in [source] .ts files.
And there's no way to tell Spotlight to override/disable the mpeg interpretation of the '.ts' extension.
Can you say what potential conflict from renaming my *.ts -> *.tsx?
Where/How does the expr syntax apply?

I was quite annoyed by Windows explorer's sluggishness with .ts and .d.ts files and found a solution that involves remapping their "file kind" to document instead of video.
More info here: https://superuser.com/questions/1304114/windows-explorer-hangs-creating-thumbnails-for-typescript-files/1733384#1733384

I fully agree.
I also have a huge problem with this because I have to choose whether I want to associate .ts files with a text editor or a video player. And 'open with' is not an option when dealing with archives, etc. I don't know why they would pick an extension that is already in use by another file type. It is unprofessional and extremely annoying.

+1
I would also like to see something done that doesn't involve renaming .ts to .tsx.  .tsc seems like it would be the ideal extension name as well as a HUGE help, especially in regards to CPUs hitting 100% in VSCode.

Is it just too late for this extension violation (blunder) to be changed? is it like the www sub-domain misunderstanding from 1994?

This already got the label declined from @RyanCavanaugh a year ago. I think a 'no' is not a great answer here tbh.
The web-dev world is changing super fast. Improvements can always be made. Would like to see this considered again.

even if we did add a brand new file extension (which we won't), we'd almost certainly eschew the ts/tsx distinction and just have it only be tsx grammar.

Making and promoting tsx as the default would definitely be one possible solution. What holds you back?

i think the problem goes much deeper: metadata meant for consumption by the OS should not be part of the file name - the file name should cater for human users, and only them. other operating systems like mac os classic and amiga os got this right, it's just windows that didn't...

I don't know what anyone expects us to do here beyond what's already available. There are 10 years of TypeScript files out there; we can't unring that bell. You can write .tsx, .mts, or .cts depending on what you're doing. It's extremely realistic to switch your code over to those extensions today, and unrealistic to expect everyone else in the world to rename their files because you somehow have actual real transport stream files as part of your daily routine.
I tried to write a .reg file to completely unassociated .ts from video, but only got this far before giving up (this stuff is pretty buried these days). Anyone able to make it work faster than just choosing "Open With" -> VS Code -> Always?
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.ts]
@=-
"Content Type"=-
"PerceivedType"="text"

[-HKEY_CLASSES_ROOT\.ts\OpenWithProgids]
[-HKEY_CLASSES_ROOT\.ts\ShellEx]

[HKEY_CLASSES_ROOT\.ts\OpenWithProgids]
"VSCode.ts"=""

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.TS\OpenWithProgids]
"WMP11.AssocFile.TTS"=-

[HKEY_CLASSES_ROOT\Applications\wmplayer.exe\SupportedTypes]
".ts"=-

[-HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\PackageRepository\Extensions\windows.fileTypeAssociation\.ts]

[-HKEY_CLASSES_ROOT\SystemFileAssociations\.ts]

[HKEY_CURRENT_USER\Software\Classes\.ts\OpenWithProgids]
"VSCode.ts"=""

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.TS\OpenWithList]
"a"="Code.exe"
"MRUList"="a"

You can write .tsx, .mts, or .cts

For the record, .mts is also reserved for video files. And .cts is falling out of favor. My only issue with using .tsx is that its reserved for React and can be confusing if your app doesn't use React. Plus, TypeScript will do additional, unnecessary parsing if you use .tsx.
I'm in favor of switching to .tsc and .tscx. You can keep .ts and .tsx as legacy extensions and still support them.

MS Teams always treat TS files as video, and it shows error when it contains text.


Adaptivity to other dynamic datasets

Dear authors,
Thank you for your excellent work.
I have tested the method on several outdoor scenes involving high ego-motion; however, the results are not entirely satisfactory. Do you believe there might be a gap in adapting to this type of data, or are there adjustments I could make to achieve better separation in such scenarios?
I also played with the hyperparameters but this is the best I can get.

Hi,
Thx for your interest in our work. Decoupling of outdoor scenes might be quite challenging due to global brightness changes. You might be able to get better results by tweaking the skewness hyperparameters, but know that this is a relatively old work and you might want to try some newer methods such as https://omnimatte-rf.github.io/ first to see if it gives better results.
Best


minifix(GUI): improve unsafe mode setting dialog

Change dialog message to "Are you sure you want to turn this on? You
will be able to overwrite your system drives if you're not careful."

Remove "CANCEL" button and put a cross at the top right corner.

Change dialog button label from "YES, CONTINUE" to "ENABLE UNSAFE
MODE"

In order to adapt to changes described above:

WarningModalService.display() now takes an object including
description, and confirmationLabel

Fixes: https://github.com/resin-io/etcher/issues/729
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

As advised as the correct approach, UX wise, by @konmouz

I wonder if the small X in the top-right corner is an obvious-enough cancel method for new and/or nervous users? *shrug*

Yeah, I think this might be a regression over what was there previously. If you are presenting a dialog telling the user they are about to destroy their data, having them take the "passive" action of closing the dialog doesn't feel right. Does closing the dialog actually preserve my data? Or do I have to take a separate action to reset it?
In the end, so much time has been spent debating this that it really isn't worth continuing, but it's important to make sure that whatever is produced is usable.

I also disagree that this is good UX. You are asking "are you sure?" but only give one option. It seems rather strange and uncomfortable to me as a user.

A few things:

We chose the 'X' button for consistency purposes. It has already been used in other modals, so makes sense to have it here as well. Anyway, this is a standardised CTA these days.
@dlech Reforming the question or just informing the user about the current actions might help (e.g. By enabling Unsafe Mode, you will be able to overwrite your system drives if you are not careful.)
I checked the comments history and indeed this topic is over discussed. For instance 'cancel/dismiss' button works well as well, as long as it is consistent with the rest of the UI.
UX-wise both solutions work fine. Just thought current one looks a bit cleaner, while with the dual buttons there is a lot of text squeezed in a small space. This can be solved by replacing 'ENABLE UNSAFE MODE' with 'GO AHEAD', 'ENABLE', etc., however it might not be as clear as current.


[Event Request] Codeunit 1103 - CA Jnl.-Post Batch - Code

Could you please create an Integration event in Codeunit 1103 CA Jnl.-Post Batch, in function Code?
LOCAL Code()
WITH CostJnlLine DO BEGIN
  ....
  IF NOT CostReg.FINDLAST OR (CostReg."No." <> CostRegNo) THEN
    CostRegNo := 0;
  INIT;
  "Line No." := CostRegNo;
  // >>>
  OnAfterAssignCostRegNo(CostJnlLine,CostReg,CostRegNo);
  // <<<
  ....
END;

Event signature:
LOCAL [IntegrationEvent] OnAfterAssignCostRegNo(VAR CostJnlLine : Record "Cost Journal Line";VAR CostReg : Record "Cost Register";CostRegNo : Integer)

It is similar to function OnProcessLinesOnAfterAssignGLNegNo in Codeunit 13 Gen. Jnl.-Post Batch.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[130] Issue #130 - March 21, 2019

To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.
The current draft for this issue in _drafts/. If you want to contribute directly, feel free to open a pull request.

https://www.youtube.com/watch?v=s65BigoMV_I&t=9s

https://twitter.com/slava_pestov/status/1103415204795346945

In 2015, a bug was fixed and the commit included this innocent-looking change: https://github.com/apple/swift/commit/cd492d96b59915f1adef0ff0bf83292d566b01a2#diff-69306f7b0822cf52e8c0639307ad7407R550

https://forums.swift.org/t/feedback-server-metrics-api/21353

https://forums.swift.org/t/march-7th-2019/21340
March 7 server workgroup meeting
Sent with GitHawk

https://forums.swift.org/t/pitch-introduce-custom-attributes/21335
Pitch: Introduce custom attributes
Sent with GitHawk

SwiftNIO 2 is upon us:
https://forums.swift.org/t/swiftnio-2-repository-convergence-plan/21387
https://github.com/apple/swift-nio/blob/master/docs/migration-guide-NIO1-to-NIO2.md
https://github.com/apple/swift-nio/blob/master/docs/public-api.md

https://forums.swift.org/t/map-sorting/21421
Map Sorting pitch with implementation

https://instabug.com/blog/test-driven-development-tutorial/

instabug.com/blog/test-driven-development-tutorial

@Kmohamed I think it's a really good article, just here we gather more Swift language news which covers it's open source aspects. There are multiple iOS tailored newsletters where this article fit more.
I hope you would understand.

@fassko totally understand

Review of SE-0246: Generic Math(s) Functions begins now and runs through March 20
https://forums.swift.org/t/se-0246-generic-math-s-functions/21479

Review of SE-0247: Contiguous Strings begins now and runs through Monday, March 18th, 2019
https://forums.swift.org/t/se-0247-contiguous-strings/21483

Proposal SE-0242 has been accepted.
https://forums.swift.org/t/accepted-se-0242-synthesize-default-values-for-the-memberwise-initializer/21475

Proposal Accepted SE-0242 is accepted, with a request that the original proposal be amended for clarification of actual behavior. The Core Team felt that the proposal should more explicitly illustrate the actual behavior in a few specific cases, as this was the crux of some of the back-and-forth in the review thread. Note: the proposal has been updated to include more details in the “proposed solution” section, as requested by the Core Team. There was some concern in the review thread about…

Review of SE-0245: Add an Array Initializer with Access to Uninitialized Storage begins now and runs through March 18, 2019
https://forums.swift.org/t/se-0245-add-an-array-initializer-with-access-to-uninitialized-storage/21469

https://twitter.com/slava_pestov/status/1105664532356231175

This PR eliminates memory allocations from code making heavy use of generics, protocols with associated types, conditional conformances and various other language features: https://github.com/apple/swift/pull/23249

thread

Pitch: Unicode Equivalence for Swift Source
A deep dive with pitch about Unicode in Swift.
https://forums.swift.org/t/pitch-unicode-equivalence-for-swift-source/21576

Pitch: Key-Path Member Lookup by @DougGregor
https://forums.swift.org/t/pitch-key-path-member-lookup/21579

As @tkremenek hinted that he will be the review manager for Swift Code Style Guidelines and Formatter and it starts on March 18.
intriguing :P
https://github.com/apple/swift-evolution/pull/994#issuecomment-472602507

Review of Key Path Expressions as Functions by @stephencelis will start on March 18 and @airspeedswift will manage it.
Great stuff.
https://github.com/apple/swift-evolution/pull/977#issuecomment-472559484

@gregomni did most of the work! I just cobbled a proposal together :)

The review of SE-0248: String Gaps and Missing APIs begins now and runs through March 22, 2019
https://forums.swift.org/t/se-0248-string-gaps-and-missing-apis/21588

Extensive deep dive about SE-0244: Opaque Result Types
https://forums.swift.org/t/reverse-generics-and-opaque-result-types/21608

https://www.apple.com/newsroom/2019/03/apple-to-host-annual-worldwide-developers-conference-june-3-7-in-san-jose/
Sent with GitHawk

https://twitter.com/slava_pestov/status/1106760323883827200

SE-0068 was accepted almost 3 years ago but we never implemented it. Now it finally has an implementation thanks to contributor John Holdsworth! https://github.com/apple/swift/pull/22863

Extended pitch of "Persistent Sequence"
https://forums.swift.org/t/persistent-sequence/21722

Property Behavior
https://github.com/apple/swift/pull/23362

https://twitter.com/jckarter/status/1107669949990895616

A detailed description by @Ilseman of the Swift String ABI, what it exposes, and what it's capable of doing: https://forums.swift.org/t/piercing-the-string-veil/21700

Swift-log is open
@weissi

After the SSWG accepted this proposal to the 'sandbox' stage, we finally followed through and opened the repository. So we can now officially kick off the open-source swift-log project!

https://forums.swift.org/t/swift-log-is-open/21750

Calling all the Unicode enthusiasts to unite

The standard library provides lots of functionality through things like the Unicode namespace and Unicode Scalar Properties. String should continue to expand on this to deliver functionality to those unfortunate enthusiastic developers who interact with Unicody details on a frequent basis.

https://forums.swift.org/t/unicode-enthusiasts-unite/21754

Pitch: Introduce (static) callables

This proposal introduces callables to Swift. Values that behave like functions can take advantage of this syntactic sugar, to look like a function call when they are called.

https://forums.swift.org/t/pitch-introduce-static-callables/21732

https://twitter.com/jckarter/status/1107757174661341185

Another great Swift internals writeup from Michael Munday, who summarizes the implementation of enum layout pretty well here: https://forums.swift.org/t/fixing-enums-on-big-endian-systems/21730

The review of SE-0249: Key Path Expressions as Functions begins now and runs through March 27, 2019.
https://forums.swift.org/t/se-0249-key-path-expressions-as-functions/21780

The review of SE-0250: Swift Code Style Guidelines and Formatter begins now and runs through April 10, 2019.
https://forums.swift.org/t/se-0250-swift-code-style-guidelines-and-formatter/21795

Property Delegate

https://twitter.com/slava_pestov/status/1108482948129533952


Removes unreferenced bounding boxes from all existing files

Nice! All check passed @napulen

Yay! Looking good. Thanks @dchiller!


Examples cpp

There's still issues with these examples.  They basically function, but in the ode_occurrence_4rtsp_start_record_tap_action.cpp example, most of the time (not always), the app locks up in the dsl_delete_all() function during an exit.  Recordings seem to be captured just fine, but there's some strange behavior (all of which could be on me):
1 - the RecordingStarted function doesn't appear to be called
2 - the RecordingCompleted callback function doesn't appear to be called, particularly because the trigger_reset() doesn't appear to be happening (can't seem to get multiple recordings from the same stream...maybe I don't understand how this works).
This all may be because I am not setting things up properly, but it's a start.

@rbgreenway thanks so much for this, I really appreciate it.  Everything is merged into the v0.20.alpha branch, and I'll look into your items above.  Thanks again!


DM21 density functional approximation in PySCF for periodic systems

I'm interested in running DM21 for some simple periodic systems. Initially some elemental transition metals. It seems the code is currently limited to Gamma point only calculations, which might limit me in the long run, but I'd still like to understand how far I can go with it regardless.
I have successfully installed DM21 and have reproduced the simple methane calculation from the README.md, so it seems everything is configured.
I'm hitting some problems trying to extend this to a periodic system.
Taking a simple hydrogen chain lattice I have the PySCF script:
import density_functional_approximation_dm21 as dm21
from pyscf.pbc import gto, scf, dft
import numpy as np

cell = gto.Cell()
cell.atom = '''H  0 0 0; H  1 1 1'''
cell.basis = 'gth-dzvp'
cell.pseudo = 'gth-pade'
cell.a = np.eye(3)*2.0
cell.build()

kmf = dft.RKS(cell)
kmf._numint = dm21.NeuralNumInt(dm21.Functional.DM21)

kmf.kernel()

This fails with the error:
  File "/home/jfurness/anaconda3/envs/dm21/lib/python3.9/site-packages/pyscf/dft/numint.py", line 2027, in _gen_rho_evaluator
    if not hermi:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

Is there any advice for using DM21 with periodic systems?

dm21.NeuralNumInt is only compatible with molecular systems. The PySCF NumInt class for periodic systems has a different interface. As arguments are passed by position rather than keyword (e.g. in https://github.com/pyscf/pyscf/blob/master/pyscf/pbc/dft/rks.py#L92), this results in the kind of error you're seeing.
It should not be too hard write a similar NeuralNumInt interface for periodic systems -- only block_loop, nr_rks, and nr_uks would need to change (I think), and all they do is cache a few variables we need access to when evaluating the functional and then forward the call to the parent class.
However, the local Hartree-Fock features also need to be computed using the appropriate periodic potential.

Thanks for the information. Re-reading your excellent paper I see that the hydrogen chains you ran were finite. Previously I had jumped to the conclusion it was an infinite hydrogen chain, and that simple extended systems were already possible.
It seems like the plumbing would be relatively straight forwards then, but I expect implementation of local exact exchange for PBC would be quite an involved bit of work?

Yes, that's probably a reasonable assessment.


UN85TU7000FXZC - Error log for first time connect

Hi there, running companion 3.1.2 on a Companion-PI. Can anyone shed light on this error? I have the TV ready and no notification ever pop up. The mac address gets discovered in a weird way. I remove it and put the actual mac address and no change.
any guidance would be super awesome!
error:
error: /opt/companion-module-dev/companion-module-samsung-smarttv-main/node_modules/samsung-tv-control/lib/samsung.js:65
throw new Error('Error send Key');
^
Error: Error send Key
at /opt/companion-module-dev/companion-module-samsung-smarttv-main/node_modules/samsung-tv-control/lib/samsung.js:65:23
at WebSocket. (/opt/companion-module-dev/companion-module-samsung-smarttv-main/node_modules/samsung-tv-control/lib/samsung.js:302:17)
at WebSocket.emit (node:events:514:28)
at WebSocket.emit (node:domain:489:12)
at Receiver.receiverOnError (/opt/companion-module-dev/companion-module-samsung-smarttv-main/node_modules/ws/lib/websocket.js:1189:13)
at Receiver.emit (node:events:514:28)
at Receiver.emit (node:domain:489:12)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v18.17.1
Starting up module class: ModuleInstance
Sentry disabled
No token found in config, establishing first time connection?
Attempting connection to tv
Connection established
Samsung {
IP: '<IP_ADDRESS>',
MAC: ') at 00:09:0f:09:',
PORT: 8002,
APP_STRING: 'iphone..iapp.samsung',
TV_APP_STRING: 'iphone.UE40NU7400.iapp.samsung',
TOKEN: '',
NAME_APP: 'Qml0Zm9jdXMgQ29tcGFuaW9u',
LOGGER: Logger { DEBUG: false, LogFile: [] },
SAVE_TOKEN: false,
TOKEN_FILE: '/opt/companion-module-dev/companion-module-samsung-smarttv-main/node_modules/samsung-tv-control/lib/token.txt',
WS_URL: 'wss://<IP_ADDRESS>:8002/api/v2/channels/samsung.remote.control?name=Qml0Zm9jdXMgQ29tcGFuaW9u'
}

Hi @mrhhats!
I haven't tested this module with the Companion-PI system image... perhaps I should do so!
Something strange is going on with MAC address discovery... but that may be a separate issue from the connectivity problem (as the MAC is only needed to turn the TV when connected via Ethernet with Wake-on-lan)... actually it does seem like the module believes that it is establishing a healthy connection with the TV (so perhaps the issue is just the access prompt is not showing up?).
Have you verified that your Samsung TV has Access Notifications enabled? (This is off by default on some TVs). The setting can probably be found under Settings > General > External Device Manager > Device Connect Manager > Access Notification is set to "First Time Only". If this setting was already enabled, try adding a token to the token field (something like 123457 will work just fine), and that may force the TV to show the access prompt again.
It might also be helpful to know what Samsung TV you're testing with... I've only tested with a few models (listed in the HELP.md file) so perhaps there's some incompatibility between other ones.
Cheers!

Hey! I got it going! my issue was more of an internal subnet problem. Thank you!


Skew transform

Description
Typst currently has https://typst.app/docs/reference/layout/rotate/ and https://typst.app/docs/reference/layout/scale/, but no skew transform. While it can be expressed using a combination of the former, it's not trivial to get right
#let skew(angle,vscale: 1,body) = {
  let (a,b,c,d)= (1,vscale*calc.tan(angle),0,vscale)
  let E = (a + d)/2
  let F = (a - d)/2
  let G = (b + c)/2
  let H = (c - b)/2
  let Q = calc.sqrt(E*E + H*H)
  let R = calc.sqrt(F*F + G*G)
  let sx = Q + R
  let sy = Q - R
  let a1 = calc.atan2(F,G)
  let a2 = calc.atan2(E,H)
  let theta = (a2 - a1) /2
  let phi = (a2 + a1)/2

  set rotate(origin: bottom+center)
  set scale(origin: bottom+center)

  rotate(phi,scale(x: sx*100%, y: sy*100%,rotate(theta,body)))
}

(The vscale parameter is strictly speaking unnecessary)
Use Case
A couple of trivial examples are fake italic text and shadows
#let fake-italic(body) = skew(-12deg,body)

#let shadowed(body) = box(place(skew(-50deg, vscale: 0.8, text(fill:luma(200),body)))+place(body))

#fake-italic[This is fake italic text]

#shadowed[This is some fancy text with a shadow]

Hello, I would like to use the skew transform implementation code in this issue to add fake italics support to cuti, a package released under the MIT license. Would it be possible for me to utilize this code for that purpose?

Hello, I would like to use the skew transform implementation code in this issue to add fake italics support to cuti, a package released under the MIT license. Would it be possible for me to utilize this code for that purpose?

Feel free

Resolved by https://github.com/typst/typst/pull/4803


topic/apply btreemap storage to comps

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 63.357%

Files with Coverage Reduction
New Missed Lines
%

../../../.cargo/registry/src/index.crates.io-6f17d22bba15001f/serde-1.0.203/src/private/de.rs
1
55.92%

../../../.cargo/registry/src/index.crates.io-6f17d22bba15001f/serde_json-1.0.118/src/de.rs
2
34.72%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
4677

Relevant Lines:
7382

💛  - Coveralls


Print feature

Thanks for creating this simple and easy to use library.
The original pdf.js library has print feature.

Is there any possibility to include this feature in this library?

Hi,
You can use the print-js library (https://printjs.crabbly.com/), as it enables to easily print a pdf file printJS('docs/printjs.pdf'). The next code is a working example for this pdfjs-viewer library:
// Create the viewer
let pdfViewer = new PDFjsViewer($('.pdfjs-viewer'));

// Load the PDF document
await pdfViewer.loadDocument("test.pdf");

// ... do things with the document

// Print the data
let pdfData = await pdfViewer.pdf.getData();
let b64Pdf=btoa(String.fromCharCode.apply(null, pdfData));
printJS({printable: b64Pdf, type: 'pdf', base64: true});

Regards.

Awesome, thank you!
Just a little thing.
I was getting "Maximum call stack size exceeded" error while converting pdfData to base64 string on second last line of your code.
To fix this, just replace
let b64Pdf=btoa(String.fromCharCode.apply(null, pdfData));
With
`let uint8Array = new Uint8Array(pdfData);
let CHUNK_SIZE = 0x8000; // Arbitrary chunk size, adjust as needed
let chunks = [];
for (let i = 0; i < uint8Array.length; i += CHUNK_SIZE) {
chunks.push(uint8Array.subarray(i, i + CHUNK_SIZE));
}
let blob = new Blob(chunks, { type: 'application/pdf' });
let b64Pdf = await new Promise((resolve) => {
let reader = new FileReader();
reader.onloadend = function () {
resolve(reader.result.split(',')[1]);
};
reader.readAsDataURL(blob);
});`
Regards
Usma Farooq

Hi,
yes, I just wanted to make it easy for the example.
Thank you for the full example. I will include in the new examples.
Regards.


Concatenating only SOME files

THink about an implementation that would concatenate some files together but not all.
Right now, if the concat feature is activated, all files are concatenated alphabetically.

Closing this in favor of https://github.com/OraOpenSource/apex-frontend-boost/issues/179 which will allow to handle partial concatenation


Scripts update for keywordselector

Docs Build status updates of commit bd81864:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Advertising/scripts/reference/KeywordSelector.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Syntax highlighting breaks inside typescript files when type casting

When using <Foo>bar type casts, syntax highlighting and indentation completely break.

I initially thought this might be an issue with typescript-vim but upon further investigation I can confirm this only happens when both vim-jsx-pretty and typescript-vim are enabled.
Minimal .vimrc to reproduce (with vim-plug)
call plug#begin()
Plug 'leafgarland/typescript-vim'
Plug 'MaxMEllon/vim-jsx-pretty'
call plug#end()

Additional discussion
See https://github.com/leafgarland/typescript-vim/issues/134 for previous discussion which prompted me to create this issue.

Please let me know if I'm missing something obvious or if you need any extra info :+1:

Thanks for your reporting. This is a known issue and it's difficult to fix, but I'll try it later.

@pbondoer For now, I recommend you to use the as syntax to cast the type. That is:
const foo = bar as string

https://basarat.gitbooks.io/typescript/docs/types/type-assertion.html#as-foo-vs-foo

I looked into vim-jsx-typescript as an alternative but it seems to suffer from the same issue. I've opened an issue on their tracker:
https://github.com/peitalin/vim-jsx-typescript/issues/21
However, I've chosen to use that plugin instead for now, as vim-jsx-pretty with TypeScript support on (using g:vim_jsx_pretty_disable_tsx = 1) breaks even non JSX files, whereas the other plugin is scoped to files with the .tsx extension.
Perhaps it should be considered doing the same, as it seems the extension is required, as per TypeScript docs.

@pbondoer I came up with a solution for this issue, you can update this plugin and test it.
For the extension problem, I will update it soon.

@yuezk It seems to work on my simple test case and on complex files that used to have issues. I'll let you know if anything weird pops up.
However, brackets are not getting any highlight. Though I'm willing to live with that:

Thank you! :heart:

I noticed that and just committed a change, you update it again.

@yuezk It now highlights string, none on the brackets though. Is it intentional? I would expect them to stand out in the same way as stands out or parametric angle brackets stand out in Promise<FooBar>.

@pbondoer Added the highlight for brackets. Update it again.

Seems to work good on a large test file! I'll close this issue. Feel free to re-open if needed :tada:


How to change ratio?

Help please. How to change ratio in croping image?

Please see #37 and #56.


Refactor Type Name resolver when overloaded

Description

Currently the prefixes of type names are filtered instead of allow listed.
This actually can cause unnecessarily boilerplate. The avoidance of collisions can be done when an error occurs by a consumer.
Acceptance Criteria:

Add 2 new fields to the Extension - one as a feature flag/switch between the already implemented version and the new to avoid a breaking change. One for the allowList.

Deprecated the existing flag.

Processor implements the switch as well as the new behaviour for the FunctionGenerator/MethodGenerator

Done with release 0.2.0-rc01


Improved MOE support in SharedLibraryLoader

This should not be necessary, because the isIos variable should be set for robovm-ios and moe-ios.
Maybe moe-ios is detected as android, since it's based on Android ART.

Yes, it is recognized as Android. In MOE 1.3.0-beta-1, we changed the behavior of System.loadLibrary to be compliant with VM specs, which introduced this issue. Would you like us to change the isIos variable instead of creating an isMoe?

Would be better to fix that moe is recognized as Android, so changing https://github.com/libgdx/libgdx/pull/4519/files#diff-02298d26f3a99802c7af1ef20425088fL51 to
// MOE is recognized as Android, since it's based on ART, so check that it's really Android
if (vm != null && vm.contains("Android Runtime") && !isMOE) {

and changing the check isIos || isMOE back to isIos should work, but ultimately @badlogic has to decide.
Just my 2 cent :)

Please ignore this pull request, we are working on a new one with propert Multi-OS Engine 1.3.0 (currently beta) support.


CheckedAdd should probably not extend Add

...and more generally, checked operation traits should not extend their unchecked counterparts.
I'd like to contribute a PR to implement CheckedAdd for the NonZero___ types in std::num, but it is not possible since they do not implement core::ops::Add (for good reason). The way to unblock my desired change is to make CheckedAdd not extend Add.
I suspect that removing the relationship between CheckedAdd and Add might be a breaking change, so I figured I'd propose the idea before I start a PR for it.
The presence of an unchecked add implies that a checked add is possible, but a checked add does not imply that an unchecked add is possible. I think that, if anything, Add should extend CheckedAdd (though I realize the practical difficulties of that). Given the relationship between them, I wonder if the real "right" solution also involves getting checked operations into core::ops. If it is, then I am willing to pursue that course of action instead of making changes to num-traits.

I suspect that removing the relationship between CheckedAdd and Add might be a breaking change,

Yes, that is a breaking change, sorry.

I wonder if the real "right" solution also involves getting checked operations into core::ops.

Those traits are all related to built-in language operators, so you can impl Add to get a working + operator on your own types. It's not impossible to think of having core traits for more numeric methods, but there's not any current precedent for that. Most of these num traits were in the standard library before Rust 1.0, and were kicked out to live here instead.

Most of these num traits were in the standard library before Rust 1.0, and were kicked out to live here instead.

Do you know where I can find any of the history of that decision?

I found the commit history, but not much discussion. For this particular trait:

It was removed with its methods transferred to trait Int in https://github.com/rust-lang/rust/commit/e51cc089da7f5a067d348ee48f494c5bca662f95
trait Int was deprecated in https://github.com/rust-lang/rust/commit/232424d9952700682373ccf2d578109f401ff023
trait Int was removed in https://github.com/rust-lang/rust/commit/eeb94886adccb3f13003f92f117115d17846ce1f

and backported before 1.0.0 in https://github.com/rust-lang/rust/commit/0372484acc0270585479caf8cdccc6eb0106d8be


WIP UI updates for patient view

Partial work done to get the patient detail view back working
(Sorry this isn't further along!)

Looks good.


feat: Let protocols define a no-fly zone

(Migrated from an internal wiki page)
Use Case
Some users request never moving over a certain area on the deck due to contamination concerns.
Current Workaround
Determining where on the deck the pipette is before a possible conflict of moving over the “no fly” zone, and hard-coding in an intermediate movement to ensure the zone is not interfered with.

Alternatively, I wonder if we could put this in the protocol author's control by defining a good set of safe points, like:

The center of a deck slot (at some arbitrary safe height)
Exactly in between two deck slots (at some arbitrary safe height)

And then the protocol author could plan the route themselves with a series of move_to()s.
# Suppose this happens in slot 1.
pipette.aspirate(100, plate['A1'])
pipette.dispense(100, plate['B1')

# Now we want to drop the tip in the trash, but we want to avoid passing over slot 4.
pipette.move_to(center_of_slot(3))  # Move to the right.
pipette.drop_tip()  # Automatically takes the direct path to the trash bin,
                    # which now avoids slot 4 because we moved to the right beforehand.

@SyntaxColoring this is exactly how we have solved the issue for our own system. We have a set of 'safe' points where we know we will not collide with our uncapping machine. We add fake microplates as labware and then use the well position to give us more granular positioning without modding the SDK.


Skip unnecessary ops in embedding_lookup_sparse

Skips the unique + embedding_lookup calls when possible and instead passes the embedding parameters directly to the sparse segment reduction op (or the corresponding ops for the weighted case), which is significantly more efficient.
This same optimization is already done in the Grappler SimplifyEmbeddingLookupStage pass, but that does not apply in Eager mode or when weights are used.

cc @nluehr

The test failures have brought to light the fact that the gradient is no longer sparse, because sparse_segment_mean_grad returns a dense tensor. A sparse-output version of the gradient op may need to be added before this PR is viable.
If you agree, then this PR can be closed for now.

Closing this due to the non-sparse gradients issue.
I'll investigate whether a sparse-output version of sparse segment reduce grad is viable (additional motivation for this is the fact that
Grappler cannot fully elide the Unique op because it's still needed for the backward graph).


support podman

include the parameter in the .env file to use podman as container manager
SAIL_CONTAINER_MANAGER=podman

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

Hey, @taylorotwell, hope you're doing good!
I've forked Sail's repository and made a few changes based on this PR (and published in https://github.com/Startap/sail-podman). Right now, what I need to know are related to license and compatibility.

Can I just keep updating my fork with your code and distribute it with changes to run Podman? All that I did was change bin/sail to recognize Podman instead of Docker.
Do you suggest updating binary package's name to other than Sail to increase compatibility and avoid any legal/tech issues?
Can I keep distributing this modification as Sail Podman or you have any other concern about anything related to it?