Set the jobs running

We need to set the ~1700 jobs running on legion. I will allocate different amounts of memory to each group of process based on how large the DEM input is.

RAM
No of Tiles

64GB
<=15

128GB
16 -> 60

1TB
> 60

All jobs have been sent to legion and are now in the queue.

All jobs in the first pass have been successfully run.


Update NuGet dependencies

[X] Have you signed the Contributor License Agreement?

Some of these dependencies are years out of date
Microsoft Reviewers: Open in CodeFlow

/azp run

For updating all the package dependencies, we may need some internal reviews to determine which versions to use. For example, we may prefer versions with long term support instead of the latest. For Target Device Family, we choose 22000 to align with other  tools winget shipped with, etc.

Thank you for the contribution @AtariDreams;
This pull request has unfortunately become quite outdated and has several merge conflicts. I'm confident that the team will continue evaluating the NuGet dependencies as new versions become available or moved into Long Term Support. As @yao-msft mentioned, there are several considerations around which version to use. If you have a specific package you believe needs to be updated outside of the normal cadence, I would encourage you to open an issue so that the consideration by the team can be tracked and documented.

Close with reason: PR is outdated by more than a year;


[DO NOT MANUAL MERGE] Release Qualification

Trigger release qualification jobs
none

@silverdev: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-cluster_wide-auth.sh
fec2e617c841eafb0076aee940bba41f3a171ec1
link
/test daily-e2e-cluster_wide-auth

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.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-cluster_wide-auth.sh
fec2e617c841eafb0076aee940bba41f3a171ec1
link
/test daily-e2e-cluster_wide-auth

prow/daily-e2e-cluster_wide-auth-default.sh
fec2e617c841eafb0076aee940bba41f3a171ec1
link
/test daily-e2e-cluster_wide-auth-default

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.


Use react-table in Information

Information panel should also use react-table
There could be the following improvements:

Value should have fixed length font and preformatted ()
If parameter name is too long we can limit with '...' using style 'ellipsis' css property: https://css-tricks.com/snippets/css/truncate-string-with-ellipsis/
There could be a visual info (background grey ?) to separate meta information from info information

Try the coffee. There is a crash if you click on the spectrum that is in the category NA

@lpatiny
i know that, this because coffe7 does not contain nucleus.

Yes I saw this but it should still not crash. NA is perfectly ok

But clicking in this category should just show this spectrum

For solvent please apply the following regexp and make a dangerously html
value=value.replace(/([0-9]+)/g,'<sub>$1<sub>');


How to calculate the max size of buy or sell?

Hi,Just like the website, how to calculate max size(usdc) of buy or sell? Any functions? thanks.

solved.


FIX: ensures chat notifications have a URL

rely on default notification item behavior
provides a URL and uses data-auto-route
adds tests
renames chat-mention-notification-item file

Im working on the failing tests


DEV-850 Implemented functionality for deleting uploaded data resource

SonarQube analysis reported 1 issue

 1 critical

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 2 issues

 2 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 critical

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 UploadServiceImpl.java#L67: The Cyclomatic Complexity of this method "addChunk" is 11 which is greater than 10 authorized.


Updated email to be a link

Fixes #58

Awesome, First pull request, Thanks! I'll double check and merge it in later today.


Display language that caused error when uploading metadata to iTunes Connect

Issue Description
During the Deliver phase when uploading metadata of multiple languages to iTunes Connect, if there is an error, the associated language is not displayed.  It would be useful to know which language caused the error.
Some items that can cause errors include, Name is already taken, App name is too long, keywords are too long, etc.
Complete output when running fastlane, including the stack trace and command used
deliver --skip_screenshots --skip_binary_upload --force
...
[14:50:47]: Activating languages da, de-DE, el, en-US, es-ES, es-MX, fi, fr-CA, fr-FR, id, it, ja, ko, ms, nl-NL, no, pt-BR, pt-PT, ru, sv, th, tr, vi, zh-Hans, zh-Hant...
[15:17:21]: Uploading metadata to iTunes Connect

[!] The request could not be completed because:
	App Name cannot be longer than 50 characters. App Name cannot be longer than 50 characters.

Environment
fastlane version (run fastlane -v): fastlane 1.104.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? no
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? rvm

Thanks for the suggestion, that's something we actually have lined up to work on next. However if you feel like it, feel free to submit a pull request adding the language to the error message 👍


AlertDialog (with EditText) Appearance Inconsistent with app

Are you a part of GSSOC' 21?

[x] Yes
[ ] No

Describe the bug
AlertDialog box used to create folder, or rename them looks inconsistent with app.
To Reproduce
Steps to reproduce the behavior:

Go to 'Notes'
Click on Add Folder button
AlertDialog to enter folder name looks odd.

Expected behavior
It should be same as the alertdialog used to add link.
Additional context
If appropiate, I can work on it.
Screenshots

Original
Updated Look

Go ahead with the changes @codeDamon
If required -

Bold the heading
improve the color combination of CANCEL button

Also, the add link alert dialog looks a bit weird at the bottom. See if you fix that.

@codeDamon are you still working on this issue?

@codeDamon are you still working on this issue?

Yeah, I am.
Most probably it will be done by tomorrow.


Possibly switch from Geckolib

@Alexander3847575 Think we could do this?
Im realizing now that Geckolib was kinda a bad idea with how unoptimized it is and im thinking we could switch to something to something else but its up for debate tbh

We made the decision
Geckolib for now :)


Can't download model again!

Hi, I can't download this model from: https://alexa-saif-bort.s3.amazonaws.com/bort.params, it says "Access Denied". It seems the same error as the first error(Closed now).

Looks like when I updated the backend, I forgot to make the model public again. Derp.
It should work now, but thank you for letting me know!
(sorry)


lua5_1: Properly name CVE patch

If the CVE identifier is in the patch name, vulnix knows, that this
package is not affected by the CVE anymore.
fyi @ckauhaus @bhipple

Should be backported to 19.09.

@JohnAZoidberg It matters in that respect that people run vulnix on their own systems. There they do obviously not have the global Vulnerability Roundup whitelist. Naming patches correctly helps to get better results on clean runs.
So I encourage you to rebase this PR so that it can be cleanly merged.

Looks like it was already done in #70274.


WIP load strings dynamically

The changes here have either been merged or are in non-draft PRs, so no more need for this.


The ReductiveTreePruner is not able to prune some anyOf profiles.

Bug Report
The Problem:
The ReductiveTreePruner is not able to prune all trees anyOf statements. An example is
{
  "schemaVersion": "0.1",
  "fields": [
    {
      "name": "A"
    },
    {
      "name": "B"
    }
  ],
  "rules": [
    {
      "rule": "Rule 1",
      "constraints": [
        {
          "anyOf": [
            {
              "field": "A",
              "is": "null"
            },
            {
              "field": "A",
              "is": "null"
            }
          ]
        }
      ]
    }
  ]
}

The pruner should be able to prune it to the equivalent of:
{
  "schemaVersion": "0.1",
  "fields": [
    {
      "name": "A"
    },
    {
      "name": "B"
    }
  ],
  "rules": [
    {
      "rule": "Rule 1",
      "constraints": [
          {
            "field": "A",
            "is": "null"
          }
      ]
    }
  ]
}

Additional Context:
Related to #1090

there is no reductive walker any more so closing


Fail screenshots are taken too late

I'm working with a test suite where we login to a web app in our before and logout in after. When a test fails we're seeing that the screenshot that gets taken is taken after the after function is run, not right after the test failed. That means every single screenshot we get after a test has failed is of the login screen as we have just logged out.
After a little exploratory debugging the problem seems to be here. The finally block is run before the pattern match that runs fail which takes the screenshot.
I wrote a little user story too, in case my explanation above wasn't clear enough. :smiley:
As a tester. When a test fails I want a screenshot of the condition the browser is in at the closest possible moment to the test failing. So that I can debug the failing test.

Thank you for filling the issue.  I will look at it as soon as I can.  Hopefully tonight.

This is fixed and available https://www.nuget.org/packages/canopy/0.9.31
Let me know if you have any other issues.  Thanks for opening this issue!

Wow great work! :smile:
Hopefully I'll get confident enough with the project that I'll submit a PR right away myself next time.


Clean up Agent head Missing page

it doesn't look like we finished styling this page.

Closed by https://github.com/samtecspg/articulate/commit/55754d2f1b0bbf8b8a278155ed1fa5c9bfbe606f


Downgrade Illuminate support?

Hi, why did you downgrade
illuminate/support
in newer versions (I will now get an older version 1.0.3 in a newer Laravel)

The project I built this for is running an old version of Laravel.
When I get time, I can create a version of IEXTrading that uses current versions.


node-fetch vulnerability issue (denial of service)

I'm using recompose which is great! And in my opinion far more useful than hooks (sorry about that).
Laslty snyk reported that recompose has one of its dependency as vulnerable :
<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>node-fetch is an A light-weight module that brings window.fetch to node.js

Affected versions of this package are vulnerable to Denial of Service. Node Fetch did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure.

https://app.snyk.io/vuln/SNYK-JS-NODEFETCH-674311
What should we do for addressing this issue?
I see no occurrences of<EMAIL_ADDRESS>in the package.json :/

Hi, as I can see there was a commit to remove the fbjs related stuffs: https://github.com/acdlite/recompose/commit/68c560b216f2530796147bee07f45bf2b9bf0412
But the latest version (v0.30.0) was released before the fbjs removement, so I think that a new release could fix this vulnerability. (If a new release is possible.)

Thank you @ridesz, yes that would be great!
What do you think @acdlite ?

Could we have an update on this? Or should we consider this project is dead?

I am looking for a fix as well.

This project seems totally dead...
What a pity, it was one of the great projet for react.
Hooks are destroying everything. I will never work with spaghetti code like hooks. This is such a regression, I don't even understand what facebook is doing... Code for kids?
Anyway, I will fork this project and create a new lib for being able to still work with clean and optimised code.

Would love to have a fix for this as well.

If anybody wants to download a version of recompose with the packages updated, see:
https://github.com/shakacode/recompose
https://www.npmjs.com/package/@shakacode/recompose
I just updated the dependencies other than FBJS and FBJS is removed.

@justin808 The NPM release of @shakacode/recompose seems to be missing a large number of files (e.g. pure.js) that are present in the GitHub sources and the upstream's NPM release, but not in the fork's release 🙁


Failed to bypass Cloudflare

Source information
KissAnime 13.5
Source language
English
Steps to reproduce

Install KissAnime extension.
Open the extension.
See error Failed to bypass Cloudflare.

Expected behavior
Should bypass Cloudflare.
Actual behavior
Can't bypass Cloudflare.
Aniyomi version
<IP_ADDRESS>
Android version
10
Other details
I don't think if KissAnime extension needs an update. I tried all the troubleshooting, open WebView browser and bypass the Cloudflare there, clearing browser cookies, change web string, reinstall extension, I also tried to reinstall the aniyomi app but the problem still there. The extension works on past few days but suddenly the error appeared and all my libraries on the extension gone.

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Follow the cloudflare section in the troubleshooting guide that you acknowledged that you've read, if it doesn't help wait until they lower protection or migrate to other sources.

@Secozzi I tried all the troubleshoot that I read and I don't read. I can't migrate cause all the libraries from the extension are all gone.


String.get_slice return Raw String

Godot version
v4.1.beta2.official [a2575cba4]
System information
Windows 10, 64bit
Issue description

String.get_slice() returns an raw string if the slice does not exist, but the docs say:

Steps to reproduce
/
Minimal reproduction project
/

The documentation is arguably ambiguous here, it doesn't exactly state that it will return empty if no entry matches, only if the specific slice doesn't exist, so it's a matter of interpretation here, and arguably changing the code breaks compatibility, depending on the interpretation, so we can either clarify the documentation or update the code, the former is easier and safer

get_slice() was an internal method and exposed later in #54453. The behavior is the same at that time, so it's the documentation that's wrong.

It's been the same since before open source
Will update the documentation


threadscope: modernize formula and fix the build

threadscope: modernize formula and fix the build

modernize the formula by using install_cabal_package
avoid unnecessary reinstalls so that it doesn't attempt to install gtk without the have-quartz-gtk flag, leading to build failure

Expecting to see
[ 22 of 209] Compiling Graphics.UI.Gtk.Embedding.Plug ( dist/dist-sandbox-bc2c08c6/build/Graphics/UI/Gtk/Embedding/Plug.hs, dist/dist-sandbox-bc2c08c6/build/Graphics/UI/Gtk/Embedding/Plug.o )

Graphics/UI/Gtk/Embedding/Plug.chs:120:6: error:
    • Couldn't match expected type ‘Ptr ()’
                  with actual type ‘Maybe DrawWindow’
    • In the first argument of ‘gtk_plug_new’, namely
        ‘(fromNativeWindowId (fromMaybe nativeWindowIdNone socketId))’
      In the second argument of ‘($)’, namely
        ‘gtk_plug_new
           (fromNativeWindowId (fromMaybe nativeWindowIdNone socketId))’
      In the second argument of ‘($)’, namely
        ‘liftM (castPtr :: Ptr Widget -> Ptr Plug)
         $ gtk_plug_new
             (fromNativeWindowId (fromMaybe nativeWindowIdNone socketId))’

Graphics/UI/Gtk/Embedding/Plug.chs:137:6: error:
    • Couldn't match expected type ‘Ptr ()’
                  with actual type ‘Maybe DrawWindow’
    • In the second argument of ‘\ (Display arg1) arg2
                                   -> withForeignPtr arg1
                                      $ \ argPtr1 -> gtk_plug_new_for_display argPtr1 arg2’, namely
        ‘(fromNativeWindowId (fromMaybe nativeWindowIdNone socketId))’
      In the second argument of ‘($)’, namely
        ‘(\ (Display arg1) arg2
            -> withForeignPtr arg1
               $ \ argPtr1 -> gtk_plug_new_for_display argPtr1 arg2)
           display
           (fromNativeWindowId (fromMaybe nativeWindowIdNone socketId))’
      In the second argument of ‘($)’, namely
        ‘liftM (castPtr :: Ptr Widget -> Ptr Plug)
         $ (\ (Display arg1) arg2
              -> withForeignPtr arg1
                 $ \ argPtr1 -> gtk_plug_new_for_display argPtr1 arg2)
             display
             (fromNativeWindowId (fromMaybe nativeWindowIdNone socketId))’

Graphics/UI/Gtk/Embedding/Plug.chs:151:3: error:
    • Couldn't match type ‘Ptr ()’ with ‘Maybe DrawWindow’
      Expected type: IO (Maybe DrawWindow)
        Actual type: IO (Ptr ())
    • In the second argument of ‘($)’, namely
        ‘(\ (Plug arg1)
            -> withForeignPtr arg1 $ \ argPtr1 -> gtk_plug_get_id argPtr1)
           (toPlug self)’
      In the expression:
        liftM toNativeWindowId
        $ (\ (Plug arg1)
             -> withForeignPtr arg1 $ \ argPtr1 -> gtk_plug_get_id argPtr1)
            (toPlug self)
      In an equation for ‘plugGetId’:
          plugGetId self
            = liftM toNativeWindowId
              $ (\ (Plug arg1)
                   -> withForeignPtr arg1 $ \ argPtr1 -> gtk_plug_get_id argPtr1)
                  (toPlug self)
cabal: Leaving directory '/var/folders/w6/9r0nb9011glb8fdz__srd78c0000gq/T/cabal-tmp-10126/gtk-0.14.3'
cabal: Error: some packages failed to install:
gtk-0.14.3 failed during the building phase. The exception was:
ExitFailure 1

Filed an upstream issue report here: https://github.com/haskell/ThreadScope/issues/57

@MikeMcQuaid @DomT4 I think this actually broke due to some changes in the behavior of Cabal 1.24, not anything to do with GHC 8, but I've fixed it now.

👍

Downstream build seems to fail both with "retry" and "rebuild", so not sure what's up with that.

http://bot.brew.sh/job/Homebrew Bottles/50702/

@ilovezfs Bintray API failure. Might get more luck running it locally.

Seems to be in https://github.com/BrewTestBot/homebrew-gui/commits/master and not in https://github.com/BrewTestBot/homebrew-gui/tree/pr-10, which doesn't exist.
https://github.com/BrewTestBot/homebrew-gui/compare/homebrew:master...pr-10 is indeed a bogus link

Looks like this may be happening with http://bot.brew.sh/job/Homebrew Bottles/50690/console as well from dupes. Wonder if related to the recent switch to JSON or related to the ridiculous CI fun lately (Hard to tell due to the limited number of bottle builds we keep).
Same situation in science as well, by the looks of it.

Seems likely to be a regression due to https://github.com/Homebrew/brew/commit/6ba466f5d858c5e6f9d162c11ec03134df6e686e

I think I see the problem.
bintray":{"package":"homebrew/gui/threadscope","repository":"bottles-gui"}}}

It's using homebrew/gui/threadscope to construct the URL.
https://api.bintray.com/packages/homebrew/bottles-gui/homebrew/gui/threadscope
but I think the URL is supposed to be
https://api.bintray.com/packages/homebrew/bottles-gui/threadscope


Npm push access

Hey @Jimexist, could you please give me npm push access? I'm doing some codemod in the community and would like to push new versions for certain packages, including this one. Likewise for bs-moment please.

@chenglou done, please take a look.


Will the AREA Research Agenda have "pure" use cases as research topics?

On March 1, a use case was suggested as a research topic. Specifically, it is the visualization of data from sensors on a connected tool.
The use case was captured because the source was a valued AREA member, however, in my mind this is a specific example of a bigger topic of visualization of data from any sensors. There's another example of the same problem in a topic written about Oil and Gas industry in which the user is able to visualize data from chemical and/or radiation sensors. The research topic is here.
This will be difficult to avoid entirely, so maybe we actually should go the other way and embrace it?
Would love to hear others think and proposed resolution for management of use cases and this issue?

I tend to agree. You would find the same use case in metals and mining, and I'm sure other parallel industries, as well. I think this once again makes a case for multi-tagging.


PR Review Guidelines

Please describe the task that needs to be done
Create short and to-the-point PR Review Guidelines, which should discuss the following:

Reference to the Contribution Guidelines, since there we discuss protocol for partially implemented features, Testing Guidelines, and definition of "Done"
Discuss concept of collaboration teams
Primary things to look for
What NOT to look for in a PR
PR Templates

@apupier maybe we can help out here with what we defined in the tooling team?

rules that were used in Fuse Tooling team were:
→ Small reviews: helps for SRP (Single Responsibility Principle), minimize complexity, avoid big bang
→ Address all comments: agree or not, all comments need to be addressed/discussed
→ Review all at once: avoids back and forth, if no time to finish review, need to tell it explicitly (but with small reviews it should not happen often)
→ Giving context
→ 24 hours: try to review PR of others in the 24 hours, watch repositories to receive mail notification
→ Optional/For Another Review comments: sometimes things can be improved but they are not critical or requires a separate task/PR and they will not block the merge of the PR
→ test locally: for complicated PR, by developer for now, have in mind to include QE on a regular basis


How to add device to cognito user?

I want to add device to my cognito user. If i set CognitoDevice to cognito user and call RememberThisDeviceAsync on CognitoDevice, i got exception:

Amazon.CognitoIdentityProvider.Model.ResourceNotFoundException: Device does not exist. ---> Amazon.Runtime.Internal.HttpErrorResponseException: Exception of type 'Amazon.Runtime.Internal.HttpErrorResponseException' was thrown.

Expected Behavior
Device must be added to user's devices?
Current Behavior
Exception with following stack trace:

at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(IExecutionContext executionContext, HttpErrorResponseException exception)
at Amazon.Runtime.Internal.ErrorHandler.ProcessException(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.d__51.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 Amazon.Runtime.Internal.CallbackHandler.<InvokeAsync>d__91.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 Amazon.Runtime.Internal.CredentialsRetriever.d__71.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 Amazon.Runtime.Internal.RetryHandler.<InvokeAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Amazon.Runtime.Internal.RetryHandler.d__101.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 Amazon.Runtime.Internal.CallbackHandler.<InvokeAsync>d__91.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 Amazon.Runtime.Internal.CallbackHandler.d__91.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 Amazon.Runtime.Internal.ErrorCallbackHandler.<InvokeAsync>d__51.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 Amazon.Runtime.Internal.MetricsHandler.d__1`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---

Possible Solution

Steps to Reproduce (for bugs)
Try this code
var currentUser = m_cognitoUserPool.GetUser("user_email");
var authRequest = new InitiateSrpAuthRequest {
    Password = password
};

var authResponse = await CurrentUser.StartWithSrpAuthAsync(authRequest);

CurrentUser.Device = new CognitoDevice("win_234124", new Dictionary<string, string>(), DateTime.Now, DateTime.Now, DateTime.Now, CurrentUser);
await CurrentUser.Device.RememberThisDeviceAsync();

Your Environment

AWSSDK.Core: <IP_ADDRESS>
AWSSDK.Extensions.CognitoAuthentication: 0.9.4
Operating System and version: Windows 10 17134.165
Visual Studio version: Community 2017 15.7.6
Targeted .NET platform: Microsoft.NETCore.UniversalWindowsPlatform 5.4.0

I have same question. How do we use Cognito Extension to enable device tracking feature?

@niraj-bpsoftware
I've work on that feature in our project, but now it planned for next days. As i can see, when user Authentificate throught StartWithSrpAuthAsync, afterf success authentification(with empty device key), in auth response you receive NewDeviceMetadata(not empty). And as i can see, you can use DeviceKey and DeviceGroupKey for call ConfirmDeviceAsync(AmazonCognitoIdentityProviderClien). After that Cognito  remember this device. Also, this method required DeviceSecretVerifierConfigType with Salt and  PasswordVerifier. How to generate it, you can see in another sdk sources.


Using blank queue name results in error on reconnection

When using an auto named queue it seems that it creates it fine first time but on a reconnect the RabbitMQ server issues the following error.
Client error: Exception (403) Reason: "ACCESS_REFUSED - queue name 'amq.gen-zOW_J2f1kRwrKFY-DvZBGw' contains reserved prefix 'amq.*'"
Client error: Exception (504) Reason: "channel/connection is not open"
Client error: Exception (504) Reason: "channel/connection is not open"
Consumer error: Exception (404) Reason: "NOT_FOUND - no previously declared queue"

Then no messages are received and it won't work again until a restart.  I presume it is trying to use the name it connected with on the first connection and try to recreate that queue but due to the name it is not allowed.

@leearmstrong hey, thanks for report. It's fixed now, please update.

No problem at all.  I've just started with Go and cony is awesome!


bash-completion: avoid unnecessary tilde expansion

When connected to an Active Directory (a variant of LDAP), tab completion
becomes very slow because the tilde is expanded all the time, even if
completing paths that do not contain a tilde at all. This developer
observed delays of several seconds at a time.
This is completely unnecessary, so let's do not do that.
The patch was provided by Ove Risberg with a bug report to the original
bash-completion project:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1390061

Since it fixes code introduced by another add-on patch, that add-on patch
was modified instead of adding yet another patch.
This fixes https://github.com/git-for-windows/git/issues/377
Signed-off-by: Johannes Schindelin<EMAIL_ADDRESS>

Any issues with this patch?


bedrock.tar download is very slow

it seems I can get only 0.01% per 30 mins with 500mbps internet
simple-optimism-node-bedrock-init-1  | Bedrock node needs to be initialized...
simple-optimism-node-bedrock-init-1  | Initializing via download...
simple-optimism-node-bedrock-init-1  | Fetching download link...
simple-optimism-node-bedrock-init-1  | Downloading bedrock.tar...
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.00%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%
simple-optimism-node-bedrock-init-1  | Download Progress: 0.01%

just download from here then modify the script
https://op.datadirs.xyz/mainnet-bedrock.tar


[Documentation] UX Issues in tutorial "Creating a Simple Siddhi Application"

Description:
In the "Creating a Simple Siddhi Application" tutorial it is suggested to write the Siddhi Application > Run Editor > Open a new file > and copy paste the Siddhi Application.
Instead, we should promote users to write the Siddhi Application in the Editor itself.
https://docs.wso2.com/display/SP420/Creating+a+Simple+Siddhi+Application
Suggested Labels:
Documentation, Editor, Improvement, UX
Suggested Assignees:
@RukshiW
Affected Product Version:
4.2.0-rc2
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Updated this tutorial to instruct the user to compose the Siddhi application in the Stream Processor Studio itself.


Fp16 Matmul on cpu doesn't match golden output.

What happened?
AssertionError:
Not equal to tolerance rtol=0.01, atol=0.001

Mismatched elements: 84242 / 589824 (14.3%)
Max absolute difference: 0.1895
Max relative difference: 171.4
 x: array([[-2.539e-01, -9.515e-02, -1.392e-01, ...,  9.409e-01,  1.569e+00,
         2.360e-01],
       [ 2.194e-01, -1.346e-01, -1.409e-01, ...,  5.474e-01,  2.559e-01,...
 y: array([[-2.563e-01, -9.259e-02, -1.366e-01, ...,  9.380e-01,  1.585e+00,
         2.369e-01],
       [ 2.218e-01, -1.348e-01, -1.405e-01, ...,  5.483e-01,  2.495e-01,...

Steps to reproduce your issue
Python code for testing: https://storage.googleapis.com/shark-public/prashant/bug_fp16_matmul/fp16_matmul.py
Input1: https://storage.googleapis.com/shark-public/prashant/bug_fp16_matmul/inp1.npy
Input2: https://storage.googleapis.com/shark-public/prashant/bug_fp16_matmul/inp2.npy
Run the command: python fp16_matmul.py (make sure that inp1.npy and inp2.npy are present in the working directory)
What component(s) does this issue relate to?
Compiler
Version information
No response
Additional context
No response

Ill ask the first obvious question if the difference is too big to be a product of associative re-ordering in the golden output. This can be very hard to track down cause the difference is really small.

@pashu123 Any response on this one?

@pashu123 Checking in on this again, any response?

Hi @pashu123 changing the data type for the inputs (ip1.npy, ip2.npy) to float32 and forward function to f32, the AssertionError isn't raised. Can you check if this resolves the issue?
`LINALG_IR_32 = '''
module attributes {torch.debug_module_name = "MHA"} {
ml_program.global private mutable @global_seed(dense<0> : tensor) : tensor
func.func @forward(%arg0: tensor<144x4096xf32>, %arg1: tensor<4096x4096xf32>) -> tensor<144x4096xf32> {
%cst = arith.constant 0.000000e+00 : f32
%0 = tensor.empty() : tensor<144x4096xf32>
%1 = linalg.fill ins(%cst : f32) outs(%0 : tensor<144x4096xf32>) -> tensor<144x4096xf32>
%2 = linalg.matmul ins(%arg0, %arg1 : tensor<144x4096xf32>, tensor<4096x4096xf32>) outs(%1 : tensor<144x4096xf32>) -> tensor<144x4096xf32>
return %2 : tensor<144x4096xf32>
}
}
'''
inp1 = np.float32(inp1)
inp2 = np.float32(inp2)
`

As --iree-llvmcpu-skip-intermediate-roundings defaults to true, it is by design that our f16 matmul results wouldn't match goldens. You can set  --iree-llvmcpu-skip-intermediate-roundings=false to see if it's the only thing at play. If it is, then you know that the discrepancy is not an inaccuracy and you can leave the default true, enjoy the higher performance and relax the test's requirements.
https://github.com/openxla/iree/blob/07a854cac43adf1e120d0e459497f8216568a747/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp#L69-L77

Ill ask the first obvious question if the difference is too big to be a product of associative re-ordering in the golden output. This can be very hard to track down cause the difference is really small.

Sicne we are not distribution-tiling on the K dimension on CPU, that would only come into play if the vectorization or data-tiling had a K0>1 tile size, which is not the case on CPU for f32 or f16 (but it would be the case for bf16 though). So not the case here.


how to prepare a pocket that is not the example in colab?

Hello,
I am trying to use your colab notebook to generate some molecules for a given PDB ID. I added both sdf and pdb of this in place of example but i receive an error. I assume there must be some way i should prepare the pocket so it is within the 10Angstroms used in the paper. However, i cannot find example of how to do this
Please see the error.
Best wishes
#############################################################################################
IndexError                                Traceback (most recent call last)
 in <cell line: 2>()
1 #@title Run Sampling
----> 2 out_sdf = ligand_generation(outdir='test_1', test_file=tmp2, checkpoint='checkpoints/best_model.ckpt', save=True)
2 frames
/content/DiffInt/equivariant_diffusion/en_diffusion.py in (.0)
997         c = n2 if n2 is not None else n1
998
--> 999         return torch.tensor([m[i].sample() for i in c], device=c.device)
1000
1001     def log_prob(self, batch_n_nodes_1, batch_n_nodes_2):
IndexError: list index out of range

Thank you for your interest in our research.
If you are using data from the Protein Data Bank, please share the PDB ID you used.
The PDB file(1a2g_A_rec.pdb) used in the example was downloaded from the Protein Data Bank, with non-protein elements (water and ligand molecules) removed. You can construct PDB file using MDAnalysis, Biopython, or manually.
So, no distance cutoff is applied to this file.
For ligands, we are using downloaded files in SDF format from the Protein Data Bank.
You don't need to prepare the cut-out PDB file for the sample generation code in Colab because the process_data() function internally handles the data extraction.

Many thanks for your response, this has solved my issue.


[Feature] Integrate data from purse seine

trackPoints.json or similar to get the locations of purse seine
catch composition graphs will change
effort map
...

working on it in commi e742bbcb4f1afc01152e421961d55ab9d027c853
Files where the paths were modified:

AppLengthFreq.vue
FishingEffort.vue
HaulInfo.vue
Map.vue
PiechartSection.vue

Now working on this files and creating reactivity from the modalities menu

@jordi-ribera The ranges for the effort maps of purse seine are missing. I could extract 140 h per km2 and 28K kg/km2 from the word document.
Visualization of purse seine sampling.docx

I also changed the paths of the fishing efforts, the hauls etc... This will have to be updated in the VISAPI repositori (nodejs api)

@jordi-ribera The ranges for the effort maps of purse seine are missing. I could extract 140 h per km2 and 28K kg/km2 from the word document. No range for the euros?
Visualization of purse seine sampling.docx

Now I see I have some images showing the legends with the ranges. I will use these

purse seine hauls:
21901.json --> classification = null
22009.json --> empty json
18413.json --> empty json

map section mostly working with commit 7f84aa4e7f88b1c784f9484ef20fc526804c7dd3. There are some internal processings that could be optimized, but the map is working now for trawling and purse-seine.

catch composition (overview) loaded with the two modalities
commit 5bc85fb

Change units of the pie chart?
Numbers are too big to understand (should be expressed in tonnes or kilotonnes?)

purse seine hauls: 21901.json --> classification = null 22009.json --> empty json 18413.json --> empty json

I have checked the empty jsons and these are hauls where they released the catch. I will discuss it with the PS team to evaluate if we filter these hauls.

hauls released where filtered in commit f8a98a1


Custom elements are not initialized until they are appended to the DOM

When a custom element is instantiated outside the DOM, the polyfill fails to run these callbacks.
They are only called when the element is inserted into the DOM.
Native implementations run these callbacks even outside the document.
document.registerElement('my-element', {
    prototype: Object.create(
        HTMLElement.prototype, {
            createdCallback: {
                value: function () {
                    console.log('created');
                }
            },
            attachedCallback: {
                value: function () {
                    console.log('attached');
                }
            }
        })
});

var div = document.createElement("div");
var myElement = document.createElement("my-element");
// nothing
div.innerHTML = "<my-element></my-element>";
// nothing
document.body.appendChild(div);
// created
// attached

that's actually expected and I've no idea why native would do that, if the node is not live.
Unfortunately there's also no way I am going to replace all DOM methods, getters, and setters, to support such edge/rare case, specially because I would need to place mutators in every DOM node.
There are ways to workaround this "issue", but I'd like to understand what's your use case.

Had the same issue I believe, that was during testing of Backbone views.
Testing of the is views is best done without adding them to the DOM for a
couple of reasons, mainly performance and ensuring isolation of code.
On Wed, May 13, 2015 at 7:02 PM, Andrea Giammarchi<EMAIL_ADDRESS>
wrote:

that's actually expected and I've no idea why native would do that, if the
node is not live.
Unfortunately there's also no way I am going to replace all DOM methods,
getters, and setters, to support such edge/rare case, specially because I
would need to place mutators in every DOM node.
There are ways to workaround this "issue", but I'd like to understand
what's your use case.
—
Reply to this email directly or view it on GitHub
https://github.com/WebReflection/document-register-element/issues/21#issuecomment-101747424
.

adding mutators to every node that is not live will kill real-world/production performance ... which one would you pick? ;-)
Like I've said, there are workarounds, like invoking createdCallback manually after feature detecting that is not invoked otherwise, then you have the attached and detached that might not work as well.
Actually, I am not sure how native does when nodes are not live, regarding attribute changes and other two callbacks. If it's just a matter of asynchronous createdCallback invocation, then I might put back the ugly rAF/timer when nodes were created non live.

I believe they should be called no matter if the parent is live or not. The created callback at the very least would make sense, because the element did get just instantiated after all.
If you create a new instance with the constructor:
new MyElement()
// created

var div = document.createElement("div");
div.appendChild(new MyElement())
// created
// no attached callback was fired

but native calls the attached callback even outside the document too.
Real world use case:
There's a custom element which is being displayed periodically for the user. This element has an initial state that's need to be re-set every time it's shown, but the values of its state is dynamic each time. The element's state is managed with the element's API. The element can't be added to the DOM before it's re-set, but it can't be initialized outside of the DOM either, because the element's API is not available until it's inserted.
I understand the performance implications.
The quick and dirty workaround I used was to insert and immediately remove the element to and from the DOM so it gets initialized, because I didn't want to implement flags just for checking if the element is native or not.
So as I understand, until widespread native support, we have to keep this in mind.

do you know if webcomponents.js works as you would expect?
I need to double check the code because it was there and got removed at some point when somebody pointed out it should not have initialized the node if not live.
I also would like to understand if this is the entry point for problems: attribute changes without initialization, attached without having control over all possible node if not via overwrite of all possible methods in order to trigger checks, etc etc ... if it's as it is, it's a caveat that should be documented but a consistent one. Meaning until the node goes live, nothing happens.
This is IMO better than "just init happens" then nothing else work offline, what do you think?

also relevant ... since partially already discussed:
https://github.com/WebReflection/document-register-element/pull/15#issuecomment-78125168
it turned out that innerHTML overrides cause also tons of problems, so even fixing createElement gotcha, it's hard to fix all the things that could happen via innerHTML
Moreover, innerHTML is still used only because it's faster, wrapping it in not so fast/updatede browsers would result in perfromance problems.
IIRC Polymer had already faced performance issues with real world apps, I really would like to avoid to find this polyfill there too, and I'd like to understand if there's a design to improve in your logic.
What I mean is the following:

why do you track and change states of nodes that might never been showed?
why cannot you do the same and make the createdCallback the activator of the rest of the logic?
since you want to register offline nodes, why would you need an attachedCallback anyway?

Don't get me wrong, I understand this is how native behaves, but if there is an alternative, let's say webcomponents, that is closer to native but slower and bigger than this, I rather suggest developers that need offline features to move in there and leave a choice, instead of two slower, bigger, less compatible, more problematic, also identical polyfills.
https://github.com/WebComponents/webcomponentsjs
Thanks for your patience

I'll check webcomponents.js again today, but if I remember correctly I had the same issue there with attachedCallbacks not firing. But I'll take a look again later.
Regarding your questions about the design:
I think there sure are alternatives, and I'll look into them.
I'm happy that at least I have a better understanding of the situation.

It might never shown, but the first time its shown, it needs to be initialized offline.
The problem is that the element's api is not available at the time, not just createdCallback
The attachedCallback may contain logic that initializes the element according to it's parent's state

Consider this:
document.registerElement('my-element', {
    prototype: Object.create(
        HTMLElement.prototype, {
            createdCallback: {
                value: function () {
                    // set default values..
                }
            },
            attachedCallback: {
                value: function () {
                    if (this.parentNode.hasAttribute("custom-attribute")) {
                        // set values depending on the parent's state
                    }
                }
            },
            customApi: {
                value: function (values) {
                    // set element's state dynamically
                }
            }
        })
});

var div;
var myElement;

function showElement (dynamicValues) {
    if (!div) {
        // initialize a widget the first time it's requested
        // save references because they won't change,
        // just internal state like texts and attributes
        div = document.createElement("div");
        // imagine this is coming from a complex string template
        div.innerHTML = "<my-element></my-element>";
        myElement = div.getElementsByTagName("my-element")[0];
    }
    // set the state of the element according to dynamic values
    // it's expected that the element has the custom API methods here
    myElement.customApi(dynamicValues);
    // insert the element into the dom
    document.body.appendChild(div);
}

// when not needed, hide the element
function hideElement () {
    if (div) {
        div.remove();
    }
}

I think consistency's better, even when it comes with limitations.
If overriding methods to provide this behavior would introduce performance drops I vote for a documented caveat + possible workarounds.
Thank you for your reply.

Wait a second ... if you put console.log in the prototype you'll have this sequence on a natively supported browser: created, custom, attached
This means that attached is indeed invoked only once the node is live, as specs say, not when is appended or created inside other nodes. This also means that your customApi method does different things accordingly with the node parent attributes, as example, you might have surprises.
You are also probably trusting a synchronous createdCallback which is not actually necessarily the case, specially when the polyfill uses observers to avoid performance issue, as discussed in the other bug I've liked before.
What I think is that you should detach custom API live interactions with the node itself if this has not been created, and eventually verify all the things at runtime when the live DOM knows the element.
This should not compromise your logic, and guard against polyfill with asynchronous behavior. Please bear in mind both polyfills and some early implementation might have an asynchronous behavior too so it's good to create components that react accordingly with these methods, and not the other way round.
As example, here is how I'd solve your problem if you really need to use innerHTML
// keep the custom element constructor reference
var MyElement = document.registerElement('my-element', {
    prototype: Object.create(
        HTMLElement.prototype, {
            createdCallback: {
                value: function () {
                    if (this._values) {
                        // do things values related
                    }
                }
            },
            attachedCallback: {
                value: function () {
                    if (this.parentNode.hasAttribute("custom-attribute")) {
                        // set values depending on the parent's state
                    }
                }
            },
            customApi: {
                value: function (values) {
                    this._values = values;
                }
            },
            _values: {
                writable: true,
                value: null // or defaults values
            }
        })
});

var div;
var myElement;

function showElement (dynamicValues) {
    if (!div) {
        // initialize a widget the first time it's requested
        // save references because they won't change,
        // just internal state like texts and attributes
        div = document.createElement("div");
        // imagine this is coming from a complex string template
        div.innerHTML = "<my-element></my-element>";
        myElement = div.getElementsByTagName("my-element")[0];
    }
    // set the state of the element according to dynamic values
    // it's expected that the element has the custom API methods here
    // be sure the method is correct one through the prototype
    MyElement.prototype.customApi.call(myElement, dynamicValues);
    // insert the element into the dom
    document.body.appendChild(div);
}

// when not needed, hide the element
function hideElement () {
    if (div) {
        div.remove();
    }
}

Moreover
If you ditch innerHTML when you create your DOM at runtime you would have the API directly exposed and the created directly invoked.
document.registerElement('my-element', {
    prototype: Object.create(
        HTMLElement.prototype, {
            createdCallback: {
                value: function () {
                    console.log('created');
                }
            },
            attachedCallback: {
                value: function () {
                    console.log('attached');
                    if (this.parentNode.hasAttribute("custom-attribute")) {
                        // set values depending on the parent's state
                    }
                }
            },
            customApi: {
                value: function (values) {
                    console.log('custom');
                }
            }
        })
});

var div;
var myElement;

function showElement (dynamicValues) {
    if (!div) {
        // initialize a widget the first time it's requested
        // save references because they won't change,
        // just internal state like texts and attributes
        div = document.createElement("div");
        // imagine this is coming from a complex string template
        div.innerHTML = "<my-element></my-element>";
        myElement = div.querySelector("my-element");
        if (!myElement.customApi) {
            myElement.replaceWith(
              myElement = document.createElement('my-element')
            );
        }
    }
    // set the state of the element according to dynamic values
    // it's expected that the element has the custom API methods here
    myElement.customApi(dynamicValues);
    // insert the element into the dom
    document.body.appendChild(div);
}

// when not needed, hide the element
function hideElement () {
    if (div) {
        div.remove();
    }
}

On non native browsers, this will log created, custom, and then attached
It's a workaround, but also a preferred solution compared to an innerHTML based one.
Please note that you can make the check generic via
function isCustomElement(el) {
  return 'createdCallback' in el            ||
         'attachedCallback' in el           ||
         'detachedCallback' in el           ||
         'attributeChangedCallback' in el;
}

and verify with same code shown before ...
        myElement = div.querySelector("my-element");
        if (!isCustomElement(myElement)) {
            myElement.replaceWith(
              myElement = document.createElement('my-element')
            );
        }

About complex templates
This is the most tricky part and what you basically need is an array of registered elements, and an helper to set innerHTML.
You might find better or more elegant solutions but this is the hint, you wrap upfront once document.registerElement and you use innerHTML(el, html) instead of el.innerHTML = html.
// right after this poly, before any other script you have in place
var innerHTML = (function (document) {
    // feature detect the problem
    var
        register = document.registerElement,
        div = document.createElement('div'),
        dre = 'document-register-element',
        initialize,
        registered
    ;
    register.call(
        document,
        dre,
        {prototype: Object.create(
            HTMLElement.prototype,
            {createdCallback: {value: Object}}
        )}
    );
    div.innerHTML = '<' + dre + '></' + dre + '>';
    // if natively supported, nothing to do
    if (div.querySelector(dre).createdCallback) {
        // return just an innerHTML wrap
        return function (el, html) {
            el.innerHTML = html;
            return el;
        };
    }
    // in other cases
    registered = [];
    initialize = function (el) {
        if (
            'createdCallback' in el         ||
            'attachedCallback' in el        ||
            'detachedCallback' in el        ||
            'attributeChangedCallback' in el
        ) return;
        for (var
            type = el.getAttribute('is'),
            name = el.nodeName,
            node = document.createElement.apply(
                document,
                type ? [name, type] : [name]
            ),
            attributes = el.attributes,
            i = 0,
            length = attributes.length,
            attr;
            i < length; i++
        ) {
            attr = attributes[i];
            node.setAttribute(attr.name, attr.value);
        }
        el.replaceWith(node);
    };
    // augment the document.registerElement method
    document.registerElement = function registerElement(name, info) {
        var type = info.extends;
        name = (type ? (type + '[is=' + name + ']') : name).toLowerCase();
        if (registered.indexOf(name) < 0) registered.push(name);
        return register.apply(document, arguments);
    };
    return function (el, html) {
        el.innerHTML = html;
        registered.forEach.call(
            el.querySelectorAll(
                registered.join(',')
            ),
            initialize
        );
        return el;
    };
}(document));

Now we've gone full circle, and we can go back to your initial example just changing one switch.
document.registerElement('my-element', {
    prototype: Object.create(
        HTMLElement.prototype, {
            createdCallback: {
                value: function () {
                    console.log('created');
                }
            },
            attachedCallback: {
                value: function () {
                    console.log('attached');
                    if (this.parentNode.hasAttribute("custom-attribute")) {
                        // set values depending on the parent's state
                    }
                }
            },
            customApi: {
                value: function (values) {
                    console.log('custom');
                    // set element's state dynamically
                }
            }
        })
});

var div;
var myElement;

function showElement (dynamicValues) {
    if (!div) {
        // initialize a widget the first time it's requested
        // save references because they won't change,
        // just internal state like texts and attributes
        div = document.createElement("div");
        // imagine this is coming from a complex string template
        innerHTML(div, "<my-element></my-element>"); // <=== there !
        myElement = div.getElementsByTagName("my-element")[0];
    }
    // set the state of the element according to dynamic values
    // it's expected that the element has the custom API methods here
    myElement.customApi(dynamicValues);
    // insert the element into the dom
    document.body.appendChild(div);
}

The result will be identical in both native and polyfilled.
I hope this helps at least a little bit.

Not just a little bit! I really appreciate your effort.
Wrapping innerHTML into a helper and patching elements is clever. I can go on with it from here.
Also, your suggestion not to rely on synchronous callbacks is a good warning too.
Thanks for the reply and the workaround solution!

Please have a look at the new README, specifically this section related to a better and tested version of the function I've written in here.
Full helper source code and its minified version
Once again that should be placed after the poly, and before the rest of the logic.
Here new tests and please note Webkit based browsers will invoke createdCallback asynchronously, be carefull with custom APIs used before an element has been created.
If this works, please close this bug as it will remain, at this point, a won't fix.

@tunderdomb I havent tried it but it should work:
var docfrag = document.createDocumentFragment();
var myElement = document.createElement("my-element");
docfrag.appendChild(myElement);
// created
// attached

Checked webcomponents.js, does the same thing; same problem: not calling callbacks outside the DOM.
A note regarding attachedCallback:

Unless specified otherwise, this callback must be enqueued whenever custom element is inserted into a document and this document has a browsing context.

Yes, it doesn't say it should be called on offline nodes.
I tried the innerHTML helper, and found two issues with it:

replaceWith is not a standard method
innerHTML doesn't handle nested custom elements

<custom-element>
  <another-element>

  </another-element>
</custom-element>

The helper you provided creates a new element for every custom element it finds in the string provided (node = document.createElement.apply). It ignores the innerHTML of those elements. In the above example the innerHTML value of the newly created node will be empty. But it should contain a span. Also, if you run it on the above string template, it returns an empty custom-element too, which should contain another custom element with a span.
So I tweaked it a little and added recursion to it.
Didn't find contribution notes in the readme, so I paste it here, but if you'd prefer a pr I'd do that too when I find time for it.
var
        register = document.registerElement,
        div = document.createElement('div'),
        dre = 'document-register-element',
        innerHTML = register.innerHTML,
        initialize,
        registered
        ;

    // avoid duplicated wrappers
    if (innerHTML) return innerHTML;

    // feature detect the problem
    register.call(
        document,
        dre,
        {prototype: Object.create(
            HTMLElement.prototype,
            {createdCallback: {value: Object}}
        )}
    );

    div.innerHTML = '<' + dre + '></' + dre + '>';

    // if natively supported, nothing to do
    if ('createdCallback' in div.querySelector(dre)) {
        // return just an innerHTML wrap
        return (register.innerHTML = function (el, html) {
            el.innerHTML = html;
            return el;
        });
    }

    // in other cases
    registered = [];
    initialize = function (el) {
        if (
            'createdCallback' in el         ||
            'attachedCallback' in el        ||
            'detachedCallback' in el        ||
            'attributeChangedCallback' in el
        ) return;
        for (var
                 type = el.getAttribute('is'),
                 name = el.nodeName,
                 node = document.createElement.apply(
                     document,
                     type ? [name, type] : [name]
                 ),
                 attributes = el.attributes,
                 i = 0,
                 length = attributes.length,
                 attr;
             i < length; i++
        ) {
            attr = attributes[i];
            node.setAttribute(attr.name, attr.value);
        }
        // run the createdCallback so it can work with the correct attributes
        node.createdCallback();
        // initialize children too
        innerHTML(node, el.innerHTML);
        // swap nodes
        el.parentNode.replaceChild(node, el);
    };

    innerHTML = function (el, html) {
        el.innerHTML = html;

        var children = el.children;
        var i = -1;
        var l = children.length;

        while (++i < l) {
            if (registered.indexOf(children[i].nodeName.toLocaleLowerCase()) !== -1) {
                initialize(children[i])
            }
        }

        return el;
    };

    var registerElement = function(type, options) {
        var name = (options.extends ?
            (options.extends + '[is="' + type + '"]') : type
        ).toLowerCase();
        if (registered.indexOf(name) < 0) registered.push(name);
        return register.apply(document, arguments);
    };

    document.registerElement = registerElement;
    // augment the document.registerElement method
    registerElement.innerHTML = innerHTML;

replaceWith is not a standard method

it is standard, and there's more standard you might want to use (like append, that's new DOM4 stuff too)
I use dom4 since quite ever, I strongly suggest you to do the same. Tests have it in too.
I should probably specify it as dependency or maybe just use replaceChild, but I believe if you want to use Custom Elements you want to use modern DOM in all its glory.

innerHTML doesn't handle nested custom elements

I'll check that ... your code won't work anyway, there are 2 ways to register elements, via node name and via extends.
Please read more about this here:
https://github.com/WebReflection/document-register-element#htmltablerowinputselectotherselement
Thanks for the report

Sorry about that, I just noticed that it was undefined in Chrome, so immediately assumed it wasn't standard. My apologies.
With the modifications I did, it worked for me. Elements registered correctly, even a template with nested custom elements. Anyway, thank you for your suggestion, it helped me a great deal.

it won't work if you have <input is="x-date"> as example, 'casue nodeName will be input, but you register x-date instead ;-)
I'll have a look as soon as I can and try to figure out how to solve "all the things"
Cheers

Now that I didn't try, and you're right it won't work.
The loop might check for the is attribute of the node at hand, and use it to see if it's a registered custom element. Like:
if (
  registered.indexOf(children[i].nodeName.toLowerCase()) !== -1
  || (registered.indexOf(children[i].getAttribute("is")||"").toLowerCase() !== -1
) {
  initialize(children[i])
}

Just improvised.
"All the thing" shall come when browsers implement standards :3

so, I haven't pushed/bumped new version yet, but could you please verify the current innerHTML.js version works as expected? (there's still need for dom4 here, but nested nodes should be just fine)

Is this really standard (innerHTML/NestedElements/createdCallback/etc) ? where the specified?

@SerkanSipahi I am not sure I understand your question ... innerHTML is a helper function to avoid problems when you use innerHTML instead of creating nodes via DOM.
Nested elements is something that needs to be solved within the helper.
createdCallback is part of Custom Elements standard together with others

@WebReflection Thanks so much for providing the innerHTML workaround. Would you please bump up the version with the newest fix so that we could point to that?

@WebReflection  Thanks for you quick response! However, when we were trying to use the innerHTML function, there is an error "el.replaceWith is not a function". Do you have any idea on what is causing that? Thanks!

you should upgrade your DOM ... and I should mention this somewhere

actually, you know what? never mind, I've updated using good old replaceChild instead, however I still strongly suggest you to upgrade your DOM ;-)

@WebReflection Thanks. And another question, we notice that the sequence is a little different. In this innerHTML function, the createdCallback function is called before binding the attributes. Our tests are failing since we are testing in createdCallback whether the attributes have already been bound. And in Chrome, looks like it also binds the attributes first. Any thoughts on that?

not sure I udnerstand what you mean ... if it's not created, how can it has attributes? any little example to verify?

OK @smilland I see what you mean ... so here the thing: in order to copy over attributes I need a node. In order to have a node I need to create one and when I create a node, the createdCallback triggers.
For the current logic it's expected, but I understand is not ideal in your case because you expect everything to be there.
Please bear in mind this innerHTML helper is some sort of "magic wrap" but the underlying logic is not touched. These are two different files indeed, and I need to think carefully how to do what you expect without causing troubles to the rest of the logic that is not based to innerHTML
Meanwhile, I wonder if in your case you could simply move the attributes related logic to attachedCallback instead of createdCallback as temporary work around until we find a better solution?

I believe 0.3.5 should work as expected ... is a bit hacky solution, but this whole poly is some sort of big hack so probably I won't care much. Please let me know if latest works, thanks.

P.S. you need to update both files, document-register-element and innerHTML

Thanks so much for all your help. We tried it out, it definitely works! We appreciate all your efforts.

no problem ... btw, who is "we", if I might? :-)

added enhancement label, will close still as won't fix since I've provided a work around. Feel free to reopen if you find something wrong. Will try to push again to the CDN so 0.3.6 will have everything in.
Cheers

@WebReflection What's the difference between appendChild and append from DOM4?

It's in standards , append accepts strings too and doesn't return the
appended child. WebKit has it already
On Sunday, 11 September 2016, Joseph Orbegoso Pea<EMAIL_ADDRESS>wrote:

@WebReflection https://github.com/WebReflection What's the difference
between appendChild and append from DOM4?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/WebReflection/document-register-element/issues/21#issuecomment-246202098,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFO9Y-PvCtPoXJXYqnJym4FU7LG3RfEks5qpGLWgaJpZM4EZYEI
.

So it's effectively the same as innerHTML and appendChild combined into a single shortcut method. Cool!
Not returning the child could possibly be unhelpful in the case of strings. Would be nice to do like jQuery:
let div = someEl.append('
blah
')
console.log(div.innerHTML) // blah

That's not what specs were written. It's not going to change.
On Wednesday, 14 September 2016, Joseph Orbegoso Pea <
<EMAIL_ADDRESS>wrote:

So it's effectively the same as innerHTML and appendChild combined into a
single shortcut method. Cool!
Not returning the child could possibly be unhelpful in the case of
strings. Would be nice to do like jQuery:
let div = someEl.append('blah')console.log(div.innerHTML) // blah
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/WebReflection/document-register-element/issues/21#issuecomment-246887853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFO9eLnmGBTlG_wRTKgQFTHeuV0pSvdks5qp1yfgaJpZM4EZYEI
.

BTW, append() is more like appendChild and textContent, not innerHTML
You should've tried it first ;-)
It use to be on specs, it has been put on hold but it shipped regardless in WebKit so it's already adopted.
This, together with prepend and remove, replaceWith, before and after

What's the advantage of having both appendChild and append? When would we rather use append than appendChild?

legacy will keep appendChild around forever. Other shortcuts have been around for years but for some reason commented out recently.
This poly, for legacy reasons, won't drop these. You can use whatever you want if dom4 is included.
Bear in mind this is CustomElements polyfill, not the DOM4 one.


Use cats-effect for file module

Scraps all of the hacky suspendable / non-suspendable business; we've got IO now.

Codecov Report

Merging #240 into master will decrease coverage by 0.34%.
The diff coverage is 79.01%.

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


Chapter 13: Trying to extract text with pybabel causes AttributeError

OS: Windows 11 22H2
Python: v3.11.0
Flask: v2.2.2
Jinja2: 3.1.2
Babel: 2.11.0
Flask-Babel: 2.0.0
After marking needed text for translation and adding babel.cfg, trying to extract the text with pybabel extract -F babel.cfg -k _l -o messages.pot . results in the following error
AttributeError: module 'jinja2.ext' has no attribute 'autoescape'

Looking at Jinja documentation, it looks like both jinja2.ext.autoescape and jinja2.ext.with_ extensions were removed in Jinja 2.9, as they are now built-in:
https://jinja.palletsprojects.com/en/3.1.x/extensions/#with-statement
https://jinja.palletsprojects.com/en/3.1.x/extensions/#autoescape-extension
In fact, removing extensions=jinja2.ext.autoescape,jinja2.ext.with_ line from babel.cfg fixes text extraction

Correct, this is a recent change that I haven't updated here, but it's on my list of updates to make also on the text of the tutorial.

I still am unable to fix this issue, 8 already removed the extensions line from babel.cfg but I'm still getting the error "ValueError: Unknown extraction method 'jinja2'" when I run the pybabel command

@NicolasTfile this is how the babel.cfg file should be with current versions of pybabel: https://github.com/miguelgrinberg/microblog/blob/2023/babel.cfg

Thank you, that is also what I did before but I have fixed my issue now. I had to upgrade my setuptools which fixed the issue for me.
For others the command to upgrade setuptools is
pip install --upgrade setuptools

Thank you, that is also what I did before but I have fixed my issue now. I had to upgrade my setuptools which fixed the issue for me. For others the command to upgrade setuptools is pip install --upgrade setuptools

still working

i ran into the identical issue and error: "ValueError: Unknown extraction method 'jinja2'".
upgrading setuptools with pip install --upgrade setuptools also resolved the issue for me.


Adjust default flying camera curve

Smoother, longer arcs.
Before Merge:

[ ] Add curve option to constructor or keys

Pull Request Test Coverage Report for Build 916454804

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

Totals

Change from base Build 849161526:
0.0%

Covered Lines:
2

Relevant Lines:
2

💛  - Coveralls


[ discussion, code style ] Arrows in vertical function signatures

Beware of bikeshedding!
When contributing to pack, I try to preserve existing code style. But there is one thing that makes this annoying and hard for me: it is the placement of arrows at verticalised function signatures. I.e., existing
findInAllParentDirs :  HasIO io
                    => (Body -> Bool)
                    -> Path Abs
                    -> EitherT PackErr io $ List $ File Abs

vs.
findInAllParentDirs : HasIO io =>
                      (Body -> Bool) ->
                      Path Abs ->
                      EitherT PackErr io $ List $ File Abs

For me, arrow belongs to the parameter on the left, because it really-really changes the meaning of it. For me, cognitive load of understanding the latter formatting is sufficiently less. Also, when adding a new parameter to an existing function, again, it's much less work to understand what to do and how to not to mess up what's already there.
So, the question is: @stefan-hoeck is it important to you that the current styling is used, or it is an arbitrary choice (or, maybe, a Haskeller habit) that can be revisited?

I think the same style should be used throughout the code base. I have accustomed myself to using the style you see in the code, which is used in all/most of my Idris packages, so I'm afraid I'm not going to change that (unless there are very strong reasons convincing to do otherwise).

I think the same style should be used throughout the code base.

If we are talking about whole pack, it's not a problem to have the same style throughout, see https://github.com/buzden/idris2-pack/commit/6c265bfa2c8c2ed37f53aeca249ce7fe612e2059

so I'm afraid I'm not going to change that.

Okay, that's anyway about personal preference and experience. So, closing, then.

Sorry, I probably was too negative in my last comment, especially since I just now realized what the actual difficulty is: We can't see, whether an argument is an auto-implicit without looking at the arrow on the next line. That's indeed something I haven't considered before. Let's do the following: Since everybody likes some decent bikeshedding from time to time, I'll post on the Idris discord asking the community about people's favorite style for lengthy function signatures. If we can agree on a solution, it probably makes sense to adapt to this newly established best practice.

I have thought again about this after all the talk on Discord. Here's my suggestion:
module Style

import Data.IORef
import Data.SortedMap

foo :
     HasIO io
  => {auto ref : IORef (SortedMap String Nat)}
  -> String
  -> Nat
  -> io ()

Core ideas:

Long type signatures should be safe under function renaming : Start them on a new line.
Prefix each line with an arrow, but use plain except for interfaces, which should be listed at the very beginning of the signature
Use {auto ...} syntax plus single errors for auto implicits that are not interfaces

@buzden: What do you think?

Thanks for the detailed answer. I was asking for your opinion in particular because you started this discussion by opening this issue. I can see your points - they are all valid, but they are also very much a matter of taste and personal preference. The opinions in the discussion on discord varied quite a bit, and I perceived no clear favorite there.
About interfaces going first: I'm aware this is not always possible, so there might be exceptions.
Personally, for me arrows coming last just don't look right and make the line harder to read than aligned arrows at the beginning of the line. At the same time - as was mentioned by other people on discord - using {auto ...} -> instead of the more concise => makes auto-implicits stand out more.
Perhaps one day, we as a community will come up with some best practice and automatic linter. Until such times, I think I'll stick to the style mentioned above. I'll close this for now, as its an opinionated matter, and we are unlikely to come to an agreement here, which is not a bad thing.


Usage of built in SoftDelete

I've been enjoying the 3.x releases!
I am currently using the built in SoftDelete and was curious if there was a best practices or suggested method for overriding the trigger through Django and doing hard deletes?
Also how much are the built in Triggers like SoftDelete intended to be examples vs a set of "batteries included" tools?  For example, I am adding the delete time via SoftDelete and was wondering if things like this would be something that should be submitted back to the project with a PR with relevant tests and doc updates?
class SoftDeleteWithDatetime(Trigger):
    """Sets a field to a value when a delete happens.

    Supply the trigger with the "field" that will be set
    upon deletion and the "value" to which it should be set.
    The "value" defaults to ``False``.

    .. note::

        This trigger currently only supports nullable ``BooleanField``,
        ``CharField``, and ``IntField`` fields.
    """

    when = Before
    operation = Delete
    field = None
    value = False

    def __init__(self, *, name=None, condition=None, field=None, value=_unset, field_datetime=None):
        self.field_datetime = field_datetime
        self.field = field or self.field
        self.value = value if value is not _unset else self.value

        if not self.field:  # pragma: no cover
            raise ValueError('Must provide "field" for soft delete')

        super().__init__(name=name, condition=condition)

    def get_func(self, model):
        soft_field = model._meta.get_field(self.field).column
        soft_field_datetime = model._meta.get_field(self.field_datetime).column
        pk_col = model._meta.pk.column

        def _render_value():
            if self.value is None:
                return 'NULL'
            elif isinstance(self.value, str):
                return f"'{self.value}'"
            else:
                return str(self.value)

        if self.field_datetime is not None:
            return f'''
            UPDATE {_quote(model._meta.db_table)}
            SET
            {soft_field} = {_render_value()},
            {soft_field_datetime} = NOW()
            WHERE {_quote(pk_col)} = OLD.{_quote(pk_col)};
            RETURN NULL;
        '''

        return f'''
            UPDATE {_quote(model._meta.db_table)}
            SET {soft_field} = {_render_value()}
            WHERE {_quote(pk_col)} = OLD.{_quote(pk_col)};
            RETURN NULL;
        '''

@jzmiller1 thanks for your feedback.
To answer your questions:

The best practice for ignoring the trigger in your application so that you can do a hard delete is using pgtrigger.ignore. See this section of the docs for more details.
pgtrigger is intended to include a set of "batteries included" tools for some very common use cases. I'm open to extending the default triggers to support more use cases or adding other default triggers. I believe there is a case for adding triggers that update timestamps on events.

Your use case can be solved by using two different trigger definitions:
class SoftDelete(models.Model):
    is_active = models.BooleanField(default=True)
    deleted_at = models.DateTimeField(null=True)

    class Meta:
        triggers = [
            pgtrigger.SoftDelete(name='soft_delete', field='is_active'),
            pgtrigger.Trigger(
                name='set_deleted_at',
                when=pgtrigger.Before,
                operation=pgtrigger.Update,
                func="NEW.deleted_at = NOW(); RETURN NEW;",
                condition=pgtrigger.Q(old__is_active=True, new__is_active=False)
            )
        ]

In the above, the deleted_at time is set whenever is_active changes, whether it is the soft delete trigger OR a user that's manually setting the is_active flag. This is in contrast to baking it into the soft delete trigger, which only fires when you try to actually delete the model.
Hope that helps! Let me know if you have any issues, otherwise I will close this (FYI I tested out the trigger above and it worked for me)

Thanks for the tips!
For some reason I was too focused on having a single trigger and missed the idea of just having another trigger set the time. Thanks, that is a better approach.


Broken Link

Hey, I appreciate you creating this list, it's very helpful, however, I have a broken link here.
Discord Servers
The Ratio Community of seedbox enthusiasts. Buying advice, application setup, and automation help.

Removed.


SW-6282 Added create ad-hoc plot function

#2684  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 12, 5:50 PM EST: A user merged this pull request with Graphite.


How to switch camera

How to switch between front and back camera in android with this bar code reader?
Any help will be appreciated.
Thank you,

Project not supported anymore (Here)

Attention: Non-Delivery Report
This report is generated by the email server at:
   gophygital.io

The message with subject:
   "Re: [kefniark/UnityBarcodeScanner] How to switch camera (#49)"

and attached to this report was not delivered to
the following recipients:
Address: @.***
Reason:  User not found (550)


Support spark 1.5.1

can you try to merge into another branch, instead of master?

@chenghao-intel we can review here, and directly push to a new branch

And another 2 issues in high level:

Split the PR into 2 (one for removing the sbt, and another for the migration of Spark 1.5.1)
I am wondering if we have some trick way to avoid copying the SqlParser code directly.

Build finished. No test results found.

https://github.com/Intel-bigdata/spark-streamingsql/pull/22 has been created to replace this one.


JSRuntime.InvokeVoidAsync not found

There's no  JSRuntime.InvokeVoidAsync method in the latest release.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: eef47457-c8cf-74a4-b884-c1fe5c2ef52d
Version Independent ID: 09a02d10-2834-467d-d8c2-3fd19ceb3863
Content: ASP.NET Core Blazor forms and validation
Content Source: aspnetcore/blazor/forms-validation.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @nicholasyin ... Inject a JS runtime instance for it at the top of the component file: @inject IJSRuntime JSRuntime. I'll update the section to call that out. Thanks for the issue. Leave this open, as it will close automatically when the PR merges.

The point is that InvokeVoidAsync is not under JSRuntime, not JSRuntime itself. There're only several InvokeAsync method overloads.

@nicholasyin ... I don't follow. It should be an extension ...
https://docs.microsoft.com/en-us/dotnet/api/microsoft.jsinterop.jsruntimeextensions.invokevoidasync?view=aspnetcore-6.0
Post a repro project to GH so that I can see the full app + component.

See your point now. The method is an extension for IJSRuntime. Adding the @inject has cleared the error.


Clarifiying a Winning Role

Would be great if some more information on determining a winning role. Eg If I grant Person A Contributor rights at the subscription, but reader rights to a resource group what role would win?

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

ID: 1e21d4b9-f574-e01d-8676-fb23d6a4ab67
Version Independent ID: 85e74a1b-3bb3-8bdd-8fca-38256c8a46c1
Content: What is role-based access control (RBAC) in Azure?
Content Source: articles/role-based-access-control/overview.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@john-louden Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.


Clean up the line placement of some template declarations in io-context

I'm not sure how just these got messed up without any of the other template declarations in the file being similarly affected, but these are the only ones I noticed. I haven't checked any other files for something similar.
Looks like these got affected by the comment cleanup in d3f25fc1e6f073155ee6bf5c7656c153f241be80

Yeah, I had originally tried a script to automate updates in this file but gave up because it was problematic. Looks like I missed part of the revert locally. Thank you!


Notice Choice web component fine tuning

Related Ticket(s)
Noitce & Choice w3 Publisher
Description
Notice & Choice is a legally required component to create a form where IBM collects its customer information.
This section shows the specific product's legal links, terms, and conditions. Along with this, it collects users' consent regarding communication preferences.
Changelog
New
Changed

Notice Choice web component fine tuned.

Removed

I have read the DCO document and I hereby sign the DCO.


[SP-2786] Backport of PDI-15120 - Export Linked Resources to XML fails if Text File Input contains empty row (6.1 Suite)

Adding null-checks before obtaining File Object from filename, that can be null.

Summary:
After this fix behavior is the following:

When exporting trans with empty filenames, they are kept empty and not converted to related path

More details:
Situation is the following here:
In transformation's xml fileNames with empty strings are stored as  and extracted as nulls when transformation is loaded.
First I wanted to store and load them as empty strings. But it was a bad idea - it leads us to some problems that are hard to overcome with such storing. Here the pitfall of this approach: when exporting trans with empty (non-null) strings in file name - they are converted into related path (root of kettle in this case). And in 99 % cases it's not what user expects.
So what we want here is exporting empty strings as they are, without converting them to related path.
We should also do this with empty strings for keeping consistency. Try running trans with textFileInput step with empty file name. It won't be treated as related path. But when exporting if with empty string it becomes related, that is not expected.

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputMeta.java
  engine/test-src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputMetaTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 1.64%
Line Change:  + 1.97%

org.pentaho.di.repository.kdr.KettleDatabaseRepositoryCreationHelper

Branch Change: -1.64%:small_red_triangle_down:
Complexity Change: -.69%:small_red_triangle_down:
Instruction Change: -2.43%:small_red_triangle_down:
Line Change: -2.95%:small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change:  + 1.28%
Complexity Change:  + .79%
Instruction Change:  + .08%

org.pentaho.di.trans.steps.fileinput.text.TextFileInputMeta

Branch Change:  + 3.46%
Complexity Change:  + 2.60%
Instruction Change:  + .97%
Line Change:  + .86%
Method Change:  + 1.11%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 2.35%
Complexity Change:  + 2.70%

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -.18%:small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.33%:small_red_triangle_down:
Complexity Change: -1.85%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/test-src/org/pentaho/di/trans/steps/fileinput/text/TextFileInputMetaTest.java

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Matchers.anyString. at Line: 33

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Matchers.eq. at Line: 34

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Mockito.verify. at Line: 35

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Mockito.mock. at Line: 36

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Mockito.spy. at Line: 37

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Mockito.doReturn. at Line: 38

:heavy_exclamation_mark: Using a static member import should be avoided - org.mockito.Mockito.never. at Line: 39

@pamval, @mchen-len-son  could you please review this PR?
It is a backport of https://github.com/pentaho/pentaho-kettle/pull/2675.
Checked it localy.


Correctly publish artifacts on JitPack

The Gradle install target produces invalid POM files that are missing
the dependencyManagement section and versions for some dependencies.
Instead, we directly tell JitPack to run the correct Gradle target.
This reverts the change in #310.

This should be helpful for testing the latest changes easily in downstream projects. Thanks for fixing it!


[BUG] Privacy Policy: validateDOMNesting(...):  cannot appear as a descendant of .

In the /privacy-policy route, I am getting this in the console:
Warning: validateDOMNesting(...): <ul> cannot appear as a descendant of <p>.
ul
p
span
div
PrivacyPolicy
RenderedRoute@http://localhost:3000/static/js/bundle.js:103136:7
Outlet@http://localhost:3000/static/js/bundle.js:103620:3
div
UserAuthenticated@http://localhost:3000/static/js/bundle.js:228:56
RenderedRoute@http://localhost:3000/static/js/bundle.js:103136:7
Routes@http://localhost:3000/static/js/bundle.js:103705:7
Router@http://localhost:3000/static/js/bundle.js:103647:7
BrowserRouter@http://localhost:3000/static/js/bundle.js:101820:7
App
StyledEngineProvider@http://localhost:3000/static/js/bundle.js:34995:7 [localhost:3000:2367:25](http://localhost:3000/)
    overrideMethod (index):2367
    React 15
    setState index.tsx:328
    push history.ts:650
    navigate hooks.tsx:238
    navigateToPrivacyPolicy Dropdown.js:63
    React 32
    workLoop scheduler.development.js:266
    flushWork scheduler.development.js:239
    performWorkUntilDeadline scheduler.development.js:533
    (Async: EventHandlerNonNull)
    js scheduler.development.js:571
    js scheduler.development.js:633
    factory react refresh:6
    Webpack 24
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        fn
        js
        js
        factory
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        <anonymous>
        <anonymous>

It's an HTML issue, just modify the document tree. I'll be able to help with this, please assign me to this issue.

ok @KitaPDev Thank you! Will assign you.


[besu] create tls cert using Cert-manager for besu network

Signed-off-by: Ravi Kiran Janjanam<EMAIL_ADDRESS>Added cert-manager chart to shared/charts folder
Added configuration to create ambassador default tls certificate by cert-manager using lets-encrypt prod CA, as of now this is implemented only for besu network
Reviewed by
@sownak @suvajit-sarkar @jagpreetsinghsasan
Linked issue
#2036

Can you remove the non inclusive word as per the lint error


OsmBuildings display issue

Sandcastle example: none
Browser: all
Operating System: all

When there are multiple Cesium views on a single page, OsmBuildings is displayed incorrectly. This issue is particularly severe in single-page frameworks such as React and Vue, their route transitions do not refresh the page, and it generates a unique ID every time, however, the problem still persists,is there any way to solve this problem?
单页面存在多个cesium视图时，OsmBuildings显示错乱，这个问题在React、Vue等单页面框架中尤其严重，它们的路由切换是不刷新页面的，并且每次都会重新生成一个唯一的ID，但问题依旧存在，是否有办法解决这个问题呢？

Thanks for bringing up this issue! I beleive we're already tracking it in https://github.com/CesiumGS/cesium/issues/11484. I'm going to close your issue to keep the discussion in one place. If you have any further input on this, please post it there instead.


[I2S] Add an option to run i2s with passing only bclk and dout

I was testing the esp-hal's i2s module and I had a ESP32-C3-Lyra V2.0 board with JST PH 2.0 2-Pin plug (check attached photo) and noticed, that actual initialising function asks user for ws pin also, which is not used in this type of connection.
Actual initialising of i2s_tx (after creating of an i2s object) looks like this:
    let i2s_tx = i2s.i2s_tx.with_pins(PinsBclkWsDout {
        bclk: io.pins.gpio1,
        ws: io.pins.gpio20,
        dout: io.pins.gpio3,
    });

, where:

bclk  => NS_PA_CTRL pin from board's schematic
dout  => PDM_TX_DATA pin from board's schematic

ws may be absolutely every existing pin, since it's unused in this type of connection
So, maybe we should let user select his connection type and then suggest an appropriate initialisation option

Is that really I2S? I don't think that should work correctly.
I2S needs to toggle WS to indicate a new word, which in I2S may be a variable number of bits. You can't know that every 16 bits is a new value starting from MSB again. So Clock & data alone are not enough.
That is labeled PDM, eg https://en.wikipedia.org/wiki/Pulse-density_modulation - which you could probably get close enough from high frequency PWM output. (Or I've done proper PDM before on a different uC using a frequent timer interrupt (like ~1MHz) - add the desired output value to an accumulator of the same size and set the output pin to the result of the carry - just a couple lines of assembly. Then in the main loop or another interrupt, change the target value.)

Thanks! The peripheral supports PDM but our current driver doesn't yet. We'll add support for it in future depending on the demand for those features but we are always happy to receive pull-requests adding missing features

Closed by #983


Make current node in Discovery immutable

It should never change, and this callsite is highly contended.

looks good


RNCCheckbox was not found in the UIManager

After running npm install --save @react-native-community/checkbox and import <CheckBox />, it threw an error as below:-
[Unhandled promise rejection: Invariant Violation: requireNativeComponent: "RNCCheckbox" was not found in the UIManager.]
at node_modules/react-native/Libraries/ReactNative/getNativeComponentAttributes.js:28:11 in getNativeComponentAttributes
at node_modules/react-native/Libraries/Renderer/shims/ReactNativeViewConfigRegistry.js:116:25 in exports.get
at node_modules/@react-navigation/native/src/useThenable.tsx:26:18 in resolve

PS. I'm using expo.
Anyone encountered the same issue? Any solutions? Thanks.

I faced the same problem now, just restart the project and it works

@ayoub-rouani May I know which version of this library are you using?

@neerajdembla212   "@react-native-community/checkbox": "^0.5.12",

@ayoub-rouani Can I have a glimpse of your package.json please? the version 0.5.12 is giving same error to me. I guess it is some other package version which is incompatible.
Following is my package.json

cd ios/ && pod install

If you are using Expo :  expo install expo-checkbox

try installing the pods  npx pod-install

Rebuild your current app after installing this library.

The problem has been solved, please close the problem. @neerajdembla212

@gutwenger Please close the issue. Thanks!

this solution didn't work for me. I'm using React Native version 0.63.4

If you are using Expo : expo install expo-checkbox it will work

this works for me. Thanks

Anyone still struggling with this thing. I suffered for 6 hours and this is the solution I got that worked it's magic.
🖱 Using Expo
Run: 🖱 expo install expo-checkbox
Then in your project import like this: 🖱 import CheckBox from "expo-checkbox";

cd ios & run npx pod install
Close your application and metro and restart the application by npx react-native run-ios

Hopefully it will work.


MongoDB: Introspection works, and migration is possible via db push

Possibly we want to keep some information that Migrate works differently or something - but the current admonition is just wrong.

I suggest we move the creation of new wording into a new PR so we can get the misleading "Introspection is not supported" removed here.


UI_REACT: Add filtered search dropdown to expression box

If a user types '@' then that should trigger a source field search.

@pleacu I think it's better to switch to new expression #1604 before implement field completion.

Hey @igarashitm - I was originally going to complete support using the old style expression location but I'll tackle 1604 first.  Thkx for the heads up.

@igarashitm - just to be clear - there was no Angular UI support for the new expression location correct?  (i.e. expression.component.ts)

nope, angular UI only supports earlier expression (as a transformation). It's incompatible and the earlier version of expression support will be discontinued in React UI.


Make Animated Value persist its value after reattaching

TBD
Fill description

related: https://github.com/kmagiera/react-native-reanimated/issues/85

@kmagiera
Now I am not convinced at all about this change. I'm afraid of blinking with some edge cases like this one which Eric has shown

@kmagiera Why use a callback instead of returning a promise?


Completion unavailable for abstract properties

 Environment data

Language Server version: 2021.3.1
OS and version: linux x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: basic

 Problem
No completion seems to be provided for abstract properties (new issue as asked in #1050):

If you need additional information, please feel free to ask!

Thanks for the report. This looks like a bug and will investigate

Thanks for the bug report. This will be fixed in the next release.

This issue has been fixed in version 2021.3.2, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202132-17-march-2021