Material UI Datepicker Validation

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

The validation for dates fails on the datepickers

Expected Behavior 🤔

Valid dates are accepted. Invalid dates are red.
Steps to Reproduce 🕹

Tested local and on the page
https://next.material-ui.com/components/date-picker/
If you are changing the months on the mobile picker the validation is always accepted.
If you are just entering normal dates, sometimes it works... Sometimes not.
Your Environment 🌎

`npx @material-ui/envinfo`
  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 15.5.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.3.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 89.0.4389.90
    Edge: Spartan (44.19041.423.0), Chromium (89.0.774.63)
  npmPackages:
    @emotion/react: ^11.1.5 => 11.1.5
    @emotion/styled: ^11.1.5 => 11.1.5
    @material-ui/core: ^5.0.0-alpha.28 => 5.0.0-alpha.28
    @material-ui/icons: ^4.9.1 => 4.11.2
    @material-ui/lab: ^5.0.0-alpha.28 => 5.0.0-alpha.28
    @material-ui/pickers: ^3.2.10 => 3.3.10
    @material-ui/styled-engine:  5.0.0-alpha.25
    @material-ui/styles:  5.0.0-alpha.28
    @material-ui/system:  5.0.0-alpha.28
    @material-ui/types:  5.1.7
    @material-ui/unstyled:  5.0.0-alpha.28
    @material-ui/utils:  5.0.0-alpha.28
    @types/react: ^16.9.41 => 16.14.5
    react: 17.0.0 => 17.0.0
    react-dom: ^16.14.0 => 16.14.0
    typescript: ^3.9.6 => 3.9.9

And I have a question for the localization for datepickers...

Why is there in the german culture just one 'y' and not 4 'yyyy'?

About the localization for datepickers, there is just one 'y' and not 4 'yyyy' because of date-fns (https://github.com/date-fns/date-fns/blob/master/src/locale/de/_lib/formatLong/index.js#L8). Indeed, date formats are strange over there 👍

About the issue itself, there is minDate={new Date('2017-01-01')} on the DesktopDatePicker, disableFuture on DatePicker and they all use the same value/setValue so when you change somewhere the date value, the Responsive isn't valid for future dates and the For desktop one isn't valid for date before 2017-01-01. Maybe minDate/maxDate shouldn't be used in this demo?

But that we can enter 0 for the month or 13 and larger values and the picker show's that the date is valid is still wrong, or is that on purpose?

Strange, are you sure you respect the date format 'mm/dd/yyyy'?
Because it looks good to me:

Except that the last picker, the Responsive one, doesn't clear the old accepted value when a new one is invalid (filled from the second picker, For Desktop). It continues to display the last accepted value whereas the internal value is invalid.

Yes, I mean for the mobile picker within the pop up Dialog. You can see it in the uploaded picture

Indeed, there is no validation within the pop up Dialog for the mobile picker 🎯
It seems that's on purpose: https://github.com/mui-org/material-ui/blob/d520cfcbe9a8bdb3dfb12224a9183fbc4814e235/packages/material-ui-lab/src/internal/pickers/Picker/Picker.tsx#L148

@antoine-moquereau thanks for exploring this. @eps1lon seems like we are always ignoring the invalid inputs on the mobile pickers. Do we want to keep this, or re-consider to allow adding validation if developers wants to?

intuitively I would expect validation to work the same on mobile or desktop. But there might be some UX reasons why this is not the case.
But it's clear that others are confused by this as well so either we find out why the current behavior exists and document it. Or we fix it.

How can I get a date displayed as "yyyy-mm-dd"? The closest localization that I can find is the "zh-CN", but the problem with that is that it uses a format of "yy-mm-dd". There is no way to account for the century if there is only "yy". In the screen shot below, is that 1921 or 2021? The weird thing is, if I use the date picker and specify which century (1921 or 2021), the control manages to remember so somewhere internally it can differentiate them so why not show "yyyy" to avoid confusion?

Would be nice if I can have the same as a regular textfield - so maybe just a same attribute like "required".

I am also seeing this behavior when changing the DatePicker values for month or day using a keyboard in a browser. Exceeding the maxDate I set does properly trigger onError, but setting an invalid month or day does not.


dismember: init at 0.0.1

Description of changes
Tool to scan memory for secrets
https://github.com/liamg/dismember
Related to https://github.com/NixOS/nixpkgs/issues/81418

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 191760 run on x86_64-linux 1

1 package built:

dismember

@ofborg eval


Updates Needed on YML File

In addition to the current YML, we'll need to also add:
jcamp
peakutils
pickle

this is now taken care of.


Parser - Black Duck Binary Analysis

Description
Describe the feature / bug fix implemented by this PR.
This PR is a new Black Duck Binary Analysis parser.
Test results
Unit tests included per: https://defectdojo.github.io/django-DefectDojo/contributing/how-to-write-a-parser/
Documentation
Documentation included per: https://defectdojo.github.io/django-DefectDojo/contributing/how-to-write-a-parser/
Checklist
This checklist is for your information.

[ X] Make sure to rebase your PR against the very latest dev.
[ X] Features/Changes should be submitted against the dev.
[ X] Bugfixes should be submitted against the bugfix branch.
[ X] Give a meaningful name to your PR, as it may end up being used in the release notes.
[ X] Your code is flake8 compliant.
[ X] Your code is python 3.11 compliant.
[X ] If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
[X ] Model changes must include the necessary migrations in the dojo/db_migrations folder.
[ X] Add applicable tests to the unit tests.
[ X] Add the proper label to categorize your PR.

@ninp0 Looks like other PRs that have been merged have conflicts with this PR. It's got the approvals so do you mind fixing that conflict so it can be merged?  Thanks :+1:

@mtesauro - merge complete.  Thanks!


Extending Tina: Add validation checks to Tina defineSchema

Validate the schema
We were previously validating the schema, but as changes were in flux that proved to be a bit tricky. Now that our primitive types have stabilized this should be easier to do. Note that this work is probably very closely related to the type work.
Expected Results:

Change to use ZOD
Things we will validate (for now):
reference field collections array is empty or doesn't match any collections in the schema.
object includes fields and templates arguments, can only have 1

Notes:
This will be an additional ticket

defaultValue and defaultItem should match the shape of their respective fields. We may be able to type some of this, but I think ideally this is caught during compilation if possible.

Originally posted by @jeffsee55 in https://github.com/tinacms/product-roadmap/issues/11#issuecomment-1071714517

PR: https://github.com/tinacms/tinacms/pull/2771


About examples of solutions that existed before

I've read some of your conversations and learned that the new code removes some of the solution's implementation code and uses native calls.
I would like to know where to find some information about the codebase that the old version of the sample code can run, because I feel that the latest version of the sample code seems to take a long time to implement, or what can I do to help this codebase.

The solutions class were introduced back in 0.8.9, you can start there.

Almost forgot to say, there's more info around #56 too if you want more context.


Translations updated and BOM deleted

A few sentences have been updated.
On save/update, I had a blank screen caused by a BOM on the translation
file.

Tthank you!


add an IsLess constraint

it would be nice to be able to restrict the argument of the ln in privacy loops to be strictly larger than 0, also the gauss parameters eps and del are supporsed to be >0 and <1 (see https://en.wikipedia.org/wiki/Additive_noise_mechanisms#Gaussian_Mechanism)

done in 959f6f3f79f74fd59fabc89334536e485896b016


support for serving static files

Hi, is there an equivalent of
app.use(express.static(`${root}/dist/client`, { index: false }))

in h3? Thanks

@mirabledictu
You can use the serve-static package.
import serveStatic from 'serve-static'

// Available from /
app.use(serveStatic(`${root}/dist/client`))

// Available from /prefix
app.use('/prefix', serveStatic(`${root}/dist/client`))

Please try using https://github.com/unjs/nitro/ instead for supporting static asset serving.
h3 aims to be a platform-independent framework and it is not easy to provide a solution that works out of the box without depending on node fs.
Thinking about integration with unstorage for static asset support (pending for https://github.com/unjs/unstorage/issues/21).

For people stumbling upon this issue, here is the current way to leverage serve-static:
import { createApp, fromNodeMiddleware } from 'h3'
import serveStatic from 'serve-static'

const app = createApp()

// Available from /
app.use(fromNodeMiddleware(serveStatic(`${root}/dist/client`)))

// Available from /prefix
app.use('/prefix', fromNodeMiddleware(serveStatic(`${root}/dist/client`)))

I was able to use the built-in serveStatic like this-
let staticHandler = h3.eventHandler(async (event) => {
    let dir = import.meta.resolve('./static')
    await h3.serveStatic(event, {
        fallthrough: true,
        indexNames: undefined,
        getContents: (id) => readFile(new URL(dir + id)),
        getMeta: async (id) => {
            const stats = await stat(new URL(dir + id)).catch(console.warn);
            if (!stats || !stats.isFile()) {
                return;
            }
            return {
                size: stats.size,
                mtime: stats.mtimeMs,
            };
        },
    });
})

app.use("/", staticHandler)

app.use doesn't work indeed, but luckily there is a workaround:
import serveStatic from "serve-static"

export default defineNitroPlugin((nitroApp) => {
  nitroApp.h3App.stack.unshift({
    route: "/uploads",
    handler: fromNodeMiddleware(serveStatic("./uploads", { immutable: true })),
  })
})

app.use doesn't work indeed, but luckily there is a workaround:
import serveStatic from "serve-static"

export default defineNitroPlugin((nitroApp) => {
  nitroApp.h3App.stack.unshift({
    route: "/uploads",
    handler: fromNodeMiddleware(serveStatic("./uploads", { immutable: true })),
  })
})

Why does this work? I am confused as to what is happening? I copy&paste your code and it worked


Feature Request: Optimize swift_debug_settings.py

Similar to #1020.

[ ] In BwX mode, only set settings for top-level targets that have unfocused dependencies. Currently it will generate for all top-level targets if there are any unfocused targets anywhere in the build graph.
[x] Generate this file over in Starlark. Has the same requirement as moving link.params over there: FilePathResolver and related logic (mainly xcodeGeneratedFiles) needs to migrate over to Starlark. (https://github.com/buildbuddy-io/rules_xcodeproj/pull/1670)
[ ] Consider splitting the file per top-level target. The main file can load the file for the required top-level target. For some projects with lots of dependencies (and even more so if those dependencies are Objective-C) the settings for each top-level target is quite large. This should speed up module loading.
[ ] Generate the file(s) on-demand, as part of the xl/bl output groups

The remaining items can be tackled post-1.0, if ever.


Duplicate link

[Enter feedback here]
The last two links on this page (in the "for more info" section, point to the same place

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

ID: 16d91022-0ff5-2a0e-4711-217fd9568018
Version Independent ID: cd30c087-06e7-f947-cf6a-262001d574a3
Content: Intelligent query processing - SQL Server
Content Source: docs/relational-databases/performance/intelligent-query-processing.md
Product: sql
Technology: performance
GitHub Login: @joesackmsft
Microsoft Alias: josack

Thanks Kalen - good catch. Looks like two issues opened for this, but I'll comment on both.  I removed the redundant link as all scripts in the AQP topic are in the IQP topic now.  PR submitted and will be reflected by this afternoon.
#please-close

Thanks for getting back to me!
I was doing final edits on a new Learn course containing info on AQP and IQP and wanting to see what the correct capitalization was. It was looking like Adaptive Query Processing is not even used as a term anymore. Is that correct?
Kalen Delaney, Global Technical Learning -  Data & AI, World Wide Learning
kadelane<EMAIL_ADDRESS>| twitter: @sqlqueen
From: Joe Sack<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 6:09 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Kalen Delaney<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] Duplicate link (#5259)
Thanks Kalen - good catch. Looks like two issues opened for this, but I'll comment on both. I removed the redundant link as all scripts in the AQP topic are in the IQP topic now. PR submitted and will be reflected by this afternoon.
#please-close
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F5259%23issuecomment-665653352&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=SAn4s3eK9OjpGJUVpRxW693MhO%2BAtNFDsDTe4X54n3U%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHIQUCWEREAQSVSV6WN5PTTR6ANPRANCNFSM4PLBAE6Q&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=GExXWFXjq7FFILoegZNO8nHmOZ8XM76xsQfm1RZ%2BfjA%3D&reserved=0.

"Adaptive Query Processing" is really a subset of the overall Intelligent
Query Processing feature family.  We had to expand the terminology, because
not everything is adaptive by definition.  We still plan on adding more
adaptive mechanisms, so you'll still see AQP as a sub-tree in the overall
IQP tree.
On Wed, Jul 29, 2020 at 11:44 AM kalendelaney<EMAIL_ADDRESS>wrote:

Thanks for getting back to me!
I was doing final edits on a new Learn course containing info on AQP and
IQP and wanting to see what the correct capitalization was. It was looking
like Adaptive Query Processing is not even used as a term anymore. Is that
correct?
Kalen Delaney, Global Technical Learning - Data & AI, World Wide Learning
kadelane<EMAIL_ADDRESS>| twitter:
@sqlqueen
From: Joe Sack<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 6:09 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Kalen Delaney<EMAIL_ADDRESS>Author <
<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] Duplicate link (#5259)
Thanks Kalen - good catch. Looks like two issues opened for this, but I'll
comment on both. I removed the redundant link as all scripts in the AQP
topic are in the IQP topic now. PR submitted and will be reflected by this
afternoon.
#please-close
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F5259%23issuecomment-665653352&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=SAn4s3eK9OjpGJUVpRxW693MhO%2BAtNFDsDTe4X54n3U%3D&reserved=0>,
or unsubscribe<
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHIQUCWEREAQSVSV6WN5PTTR6ANPRANCNFSM4PLBAE6Q&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=GExXWFXjq7FFILoegZNO8nHmOZ8XM76xsQfm1RZ%2BfjA%3D&reserved=0>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/5259#issuecomment-665775621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD277KDXZ3G2V43SDCBNBQDR6BGXBANCNFSM4PLBAE6Q
.

Yes, I know it’s a subset … but is the term ever really used or should we just talk about Intelligent Query Processing instead?
Kalen Delaney, Global Technical Learning -  Data & AI, World Wide Learning
kadelane<EMAIL_ADDRESS>| twitter: @sqlqueen
From: Joe Sack<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 9:50 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Kalen Delaney<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] Duplicate link (#5259)
"Adaptive Query Processing" is really a subset of the overall Intelligent
Query Processing feature family. We had to expand the terminology, because
not everything is adaptive by definition. We still plan on adding more
adaptive mechanisms, so you'll still see AQP as a sub-tree in the overall
IQP tree.
On Wed, Jul 29, 2020 at 11:44 AM kalendelaney <notifications<EMAIL_ADDRESS>wrote:

Thanks for getting back to me!
I was doing final edits on a new Learn course containing info on AQP and
IQP and wanting to see what the correct capitalization was. It was looking
like Adaptive Query Processing is not even used as a term anymore. Is that
correct?
Kalen Delaney, Global Technical Learning - Data & AI, World Wide Learning
kadelane@microsoft.com<mailto:kadelane@microsoft.commailto:kadelane<EMAIL_ADDRESS>| twitter:
@sqlqueen
From: Joe Sack <notifications<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 6:09 AM
To: MicrosoftDocs/sql-docs <sql-docs<EMAIL_ADDRESS>Cc: Kalen Delaney <Kalen.Delaney<EMAIL_ADDRESS>Author <
author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] Duplicate link (#5259)
Thanks Kalen - good catch. Looks like two issues opened for this, but I'll
comment on both. I removed the redundant link as all scripts in the AQP
topic are in the IQP topic now. PR submitted and will be reflected by this
afternoon.
#please-close
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F5259%23issuecomment-665653352&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=SAn4s3eK9OjpGJUVpRxW693MhO%2BAtNFDsDTe4X54n3U%3D&reserved=0>,
or unsubscribe<
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHIQUCWEREAQSVSV6WN5PTTR6ANPRANCNFSM4PLBAE6Q&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=GExXWFXjq7FFILoegZNO8nHmOZ8XM76xsQfm1RZ%2BfjA%3D&reserved=0>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/5259#issuecomment-665775621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD277KDXZ3G2V43SDCBNBQDR6BGXBANCNFSM4PLBAE6Q
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F5259%23issuecomment-665778686&data=02|01|Kalen.Delaney%40microsoft.com|8be322c4258640dcc17708d833df7903|72f988bf86f141af91ab2d7cd011db47|1|0|637316382189569084&sdata=PCdzqNGHb3kfhgsnUaNRJhqt7t7TcLI3WZGOcGU%2FPhc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHIQUCXTYQSRDZGRDGCPQL3R6BHMRANCNFSM4PLBAE6Q&data=02|01|Kalen.Delaney%40microsoft.com|8be322c4258640dcc17708d833df7903|72f988bf86f141af91ab2d7cd011db47|1|0|637316382189569084&sdata=15Hlpg597uhtX0rjToVn7LqqRXTqzqE1TsG3WxtsZv4%3D&reserved=0.

Feel free to use Intelligent Query Processing (IQP) moving forward.  AQP is
valid terminology still, but you achieve the same high-level aim by talking
about IQP.
On Wed, Jul 29, 2020 at 11:53 AM kalendelaney<EMAIL_ADDRESS>wrote:

Yes, I know it’s a subset … but is the term ever really used or should we
just talk about Intelligent Query Processing instead?
Kalen Delaney, Global Technical Learning - Data & AI, World Wide Learning
kadelane<EMAIL_ADDRESS>| twitter:
@sqlqueen
From: Joe Sack<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 9:50 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Kalen Delaney<EMAIL_ADDRESS>Author <
<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] Duplicate link (#5259)
"Adaptive Query Processing" is really a subset of the overall Intelligent
Query Processing feature family. We had to expand the terminology, because
not everything is adaptive by definition. We still plan on adding more
adaptive mechanisms, so you'll still see AQP as a sub-tree in the overall
IQP tree.
On Wed, Jul 29, 2020 at 11:44 AM kalendelaney<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

Thanks for getting back to me!
I was doing final edits on a new Learn course containing info on AQP and
IQP and wanting to see what the correct capitalization was. It was
looking
like Adaptive Query Processing is not even used as a term anymore. Is
that
correct?
Kalen Delaney, Global Technical Learning - Data & AI, World Wide
Learning
kadelane<EMAIL_ADDRESS>kadelane<EMAIL_ADDRESS>| twitter:
@sqlqueen
From: Joe Sack <notifications<EMAIL_ADDRESS>

Sent: Wednesday, July 29, 2020 6:09 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS><EMAIL_ADDRESS>Cc: Kalen Delaney<EMAIL_ADDRESS><EMAIL_ADDRESS>Author <
author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] Duplicate link (#5259)
Thanks Kalen - good catch. Looks like two issues opened for this, but
I'll
comment on both. I removed the redundant link as all scripts in the AQP
topic are in the IQP topic now. PR submitted and will be reflected by
this
afternoon.
#please-close
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F5259%23issuecomment-665653352&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=SAn4s3eK9OjpGJUVpRxW693MhO%2BAtNFDsDTe4X54n3U%3D&reserved=0>,

or unsubscribe<

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHIQUCWEREAQSVSV6WN5PTTR6ANPRANCNFSM4PLBAE6Q&data=02|01|Kalen.Delaney%40microsoft.com|a7040dd2001441a94cad08d833c096aa|72f988bf86f141af91ab2d7cd011db47|1|0|637316249539209653&sdata=GExXWFXjq7FFILoegZNO8nHmOZ8XM76xsQfm1RZ%2BfjA%3D&reserved=0>.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/MicrosoftDocs/sql-docs/issues/5259#issuecomment-665775621>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AD277KDXZ3G2V43SDCBNBQDR6BGXBANCNFSM4PLBAE6Q>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F5259%23issuecomment-665778686&data=02|01|Kalen.Delaney%40microsoft.com|8be322c4258640dcc17708d833df7903|72f988bf86f141af91ab2d7cd011db47|1|0|637316382189569084&sdata=PCdzqNGHb3kfhgsnUaNRJhqt7t7TcLI3WZGOcGU%2FPhc%3D&reserved=0>,
or unsubscribe<
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHIQUCXTYQSRDZGRDGCPQL3R6BHMRANCNFSM4PLBAE6Q&data=02|01|Kalen.Delaney%40microsoft.com|8be322c4258640dcc17708d833df7903|72f988bf86f141af91ab2d7cd011db47|1|0|637316382189569084&sdata=15Hlpg597uhtX0rjToVn7LqqRXTqzqE1TsG3WxtsZv4%3D&reserved=0>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/5259#issuecomment-665780437,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD277KB4P4FWCPFGPKTZCW3R6BHYPANCNFSM4PLBAE6Q
.


Minimal insecure impersonation proxy

Purpose This will allow Pinniped to work on more kinds of clusters. Today, the concierge only provides access to a cluster if it can access the cluster signing key, which is not possible on many cloud providers' clusters. An impersonation proxy will allow the user to provide a JWT token to make calls to the kube api server without the concierge having to issue a cluster specific certificate.
Given that I have a GKE cluster configured with Pinniped
And given that I have configured my kubeconfig to use the impersonation proxy as the kube API server
And given that I have configured my kubeconfig to use the Pinniped CLI with an OIDC provider
When I run kubectl commands
Then my commands execute as my identity from the OIDC provider
And my commands are effected by the RBAC settings for my identity
Notes: Additional scope will be part of later stories.

#67 was a draft version that we can look at for reference.
Configuration of the proxy is out of scope.
Group membership is out of scope.
JWT validation is out of scope.
Assume that the username will always be at the claim username.
Do the simplest possible thing to get kubectl to accept our TLS configuration (or lack thereof)

Some notes about this and possible followup stories (brainstorming with @cfryanr):

Assume manually-created kubeconfig, don't really validate the tokens at all, disable behind a feature gate. Add basic token validation using the JWT/webhook token authenticator cache, impersonate the right username and groups. This is basically this current issue, but with a little additional scope to make sure we can safely merge to main without opening any serious security issues, and avoids us having to build some other mechanism to disable/enable the code dynamically.
Wire in some configuration via Credentialssuer spec for whether/how to start the proxy, including manually specified TLS certificates (in a Secret)
Publish status about the proxy into the CredentialIssuer status.
Add a flag to the pinniped login oidc/pinniped login static commands like --enable-concierge-proxy which skips the TokenCredentialRequest exchange and instead returns the token in the right format to pass to the proxy. The name/type of token authenticator should be embedded in the bearer token somehow.
Add code to the pinniped get kubeconfig that allows it to detect the "proxy mode" and output an appropriate kubeconfig.

Possible future stories (might be out of scope of the main requirements):

Add code to automatically create a LoadBalancer service if requested in the CredentialIssuer (e.g., "mode: auto")
Add code to automatically generate a CA and sign the proxy certs.

Some notes about this and possible followup stories (brainstorming with @cfryanr):

Assume manually-created kubeconfig, don't really validate the tokens at all, disable behind a feature gate. Add basic token validation using the JWT/webhook token authenticator cache, impersonate the right username and groups. This is basically this current issue, but with a little additional scope to make sure we can safely merge to main without opening any serious security issues, and avoids us having to build some other mechanism to disable/enable the code dynamically.
Wire in some configuration via Credentialssuer spec for whether/how to start the proxy, including manually specified TLS certificates (in a Secret)
Publish status about the proxy into the CredentialIssuer status.
Add a flag to the pinniped login oidc/pinniped login static commands like --enable-concierge-proxy which skips the TokenCredentialRequest exchange and instead returns the token in the right format to pass to the proxy. The name/type of token authenticator should be embedded in the bearer token somehow.
Add code to the pinniped get kubeconfig that allows it to detect the "proxy mode" and output an appropriate kubeconfig.

Possible future stories (might be out of scope of the main requirements):

Add code to automatically create a LoadBalancer service if requested in the CredentialIssuer (e.g., "mode: auto")
Add code to automatically generate a CA and sign the proxy certs.


Feature request: Ability to post custom timestamps with metrics

Use case
I've setup a cron job to log daily costs from cost explorer to cloudwatch metrics (i.e. looking at the previous day's data for each invocation). I realised today that it might not be possible to assign the correct timestamp using powertools for this use case, as I think it assumes the timestamp is the time of publishing?
Related to this, I could not see any documentation on https://docs.powertools.aws.dev/lambda/typescript/latest/core/metrics/ for how the timestamp is determined (is it time of addMetrics() or time of .flush()?
Solution/User Experience
Allow specification of timestamp with the addMetric() call
Alternative solutions
In the mean time, I think I'll need to use https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/cloudwatch/command/PutMetricDataCommand/
I notice this feature seems to already be available in the Python toolkit: https://docs.powertools.aws.dev/lambda/python/latest/core/metrics/#changing-default-timestamp and maybe not in Java
Acknowledgment

[x] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[x] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

Hi @bml1g12, thanks for opening this feature request!
I think it's more than valid since as you pointed out, the feature itself already present in another version of Powertools for AWS.
In terms of DX, we'll most likely align with the one introduced in the Python version rather than adding a new parameter to the method to add a metric.
I'll add this to the backlog and mark it as open for contributors. If anyone is interested to take it, please leave a comment so we can assign it you. Feel free to ask any questions.
If it's not picked up, we'll prioritize it to be worked on within the team as time allows it.

That makes sense, thanks

Also, @bml1g12, I missed your other question about the timestamp.
The timestamp is generated here, which is called during the publishStoredMetrics() method.

I will work on this ✋


uAgents: E2E encryption between agents

Investigate adding noise (or similar) support for encrypting messages between agents

Duplicate of https://github.com/fetchai/uAgents/issues/61.


Date Analysis with Python: fcc-medical-data-visualizer error

Describe your problem and how to reproduce it:
Pressing run brings up an error that appears to be unrelated to the user-written code, and related to the package dependency files:
Repl.it: Updating package configuration

--> python3 -m poetry lock

[RuntimeError]
The Poetry configuration is invalid:
  - 'description' is a required property

exit status 1

Repl.it: Package operation failed.

Add a Link to the page with the problem:
<EMAIL_ADDRESS>Tell us about your browser and operating system:

Browser Name: Mozilla Firefox
Browser Version: 78.0.2
Operating System: Windows 7

Closed as dupe of https://github.com/freeCodeCamp/freeCodeCamp/issues/39175


Assertion failure in hexTriplet

unfortunately I got a
Assertion failure in hexTriplet::hexTriplet(NSString *__strong)(), /Users/jpm/Desktop/PocketSVG-master/SVGEngine.mm:888
that's in
hexTriplet::hexTriplet(NSString *str)
...
NSCParameterAssert([str hasPrefix:@"#"]);
Could be due to a gradient?  Bummer...

Could you please provide steps to reproduce this?

will do, I'll get an example file, thanks!

@arielelkin , thanks, there's the test file.  I have found another one that throws the same error (it;'s a corporate logo, I could email it if you wish)
not sure what the issue could be!  the TIGER does indeed have gradients so I guess that is not the problem as such.

Thanks for sending this through. I suspect it's because the colours are expressed as RGB values rather than hex.  Can you try this format:fill="#cc7226" rather than rgb(0, 38, 245)

Closing as I haven't heard back, but feel free to reopen if the problem persists.

Sorry, so busy, will get to it !!!!!!!!

Hi I have some strange crash
*** Assertion failure in hexTriplet::hexTriplet(NSString *__strong)(), SVGEngine.mm:904
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: [str hasPrefix:@"#"]'

this is probably due to a colour being expressed as an RGB value rather than hex.


RuntimeError: Expected a 'cuda' device type for generator but found 'cpu'

Hello, bro. Great work!
When I tried to run the code, I got this following:

python train.py --model_name dkt --dataset_name ASSIST2009

Traceback (most recent call last):
  File "train.py", line 163, in <module>
    main(args.model_name, args.dataset_name)
  File "train.py", line 92, in main
    train_dataset, test_dataset = random_split(
  File "/home/yuwei/Studio/env_ervin/lib/python3.8/site-packages/torch/utils/data/dataset.py", line 386, in random_split
    indices = randperm(sum(lengths), generator=generator).tolist()
RuntimeError: Expected a 'cuda' device type for generator but found 'cpu'

I have torch  "1.10.0+cu113" on 2080Ti and Ubuntu20.
Appreciate your help, bro.

Note: There are some bugs in the pytorch.utils.data module on the PyTorch version 1.9.0. If you want to run this repository safely, you need to install the PyTorch version 1.7.0 or 1.8.0.


Test exported genesis

Let's add this kind of info to readme:

This repository automatically tests x, y, z
Using GH actions we test upgrades with fresh state – badge
On a remote VM we test upgrades with actual exported genesis files from Cosmos Hub mainnet – links to the log


Error On Join

When i try to join the server i get the error below
[ Native Stack ]
[INVALID ERROR CODE](0xe06d7363)
at 0x00007FF80703478C KERNELBASE.dll!RaiseException+0x6c
at 0x00007FFFF39564C0 VCRUNTIME140.dll!CxxThrowException+0x90
at 0x00007FFFF38FB162 MSVCP140.dll!std::_Xlength_error+0x22
at 0x00007FF774207150 bedrock_server.exe!std::vector<char,std::allocator >::_Xlength+0x10
at 0x00007FF774F17608 bedrock_server.exe!std::vector<std::shared_ptr,std::allocator<std::shared_ptr > >::_Resize_reallocatestd::_Value_init_tag+0x198
at 0x00007FF774FC9A36 bedrock_server.exe!std::vector<std::shared_ptr,std::allocator<std::shared_ptr > >::resize+0x76
at 0x00007FF774F86F21 bedrock_server.exe!GridArea<std::shared_ptr >::move+0xd1
at 0x00007FF774F8721A bedrock_server.exe!ChunkViewSource::move+0x13a
at 0x00007FF774F8731C bedrock_server.exe!ChunkViewSource::move+0xac
at 0x00007FF7746CC4BF bedrock_server.exe!NetworkChunkPublisher::moveRegion+0x15f
at 0x00007FF774675BA4 bedrock_server.exe!ServerPlayer::_updateChunkPublisherView+0x64
at 0x00007FF77469B664 bedrock_server.exe!ServerPlayer::tickWorld+0x74
at 0x00007FF774FDC6B7 bedrock_server.exe!std::_Func_impl_no_alloc<<lambda_eda4c29ff908d78561661109fb4bc890>,bool,Player &>::_Do_call+0x37
at 0x00007FF774FECACD bedrock_server.exe!Level::forEachPlayer+0x7d
at 0x00007FF774FFC573 bedrock_server.exe!Level::tick+0x433
at 0x00007FF77469B3E6 bedrock_server.exe!ServerLevel::tick+0x26
at 0x00007FF774BA1285 bedrock_server.exe!Minecraft::update+0xa55
at 0x00007FF7746756F3 bedrock_server.exe!ServerInstance::_update+0xe3
at 0x00007FF77466D9B8 bedrock_server.exe!<lambda_5d63f534eeadf9e385a3ddce5663beb8>::operator()+0x3c8
at 0x0000014C2B3D04A2 (asm) gameThreadEntry+0x17
at 0x00007FFF5FB7DB0D VCRUNTIME140_1.dll!AsyncTask::open'::5'::<lambda_1>::operator()+0x10d (bdsx-core\nodegate.cpp:198)
at 0x00007FFF5FBA7042 VCRUNTIME140_1.dll!uv_process_reqs+0x29a (node\uv\src\win\req-inl.h:195)
at 0x00007FFF5FBA7B68 VCRUNTIME140_1.dll!uv_run+0xc8 (node\uv\src\win\core.c:519)
at 0x00007FFF5FBD9365 VCRUNTIME140_1.dll!node::Start+0x3d5 (node\node.cc:2172)
at 0x00007FFF5FBD9D9F VCRUNTIME140_1.dll!node::Start+0x2f6 (node\node.cc:2425)
at 0x00007FFF5FB6BCC9 VCRUNTIME140_1.dll!nodeStart+0x9 (bdsx-core\main.cpp:71)
at 0x00007FF7756827E0 bedrock_server.exe!__scrt_common_main_seh+0x10c
at 0x00007FF808CF54E0 KERNEL32.DLL!BaseThreadInitThunk+0x10
at 0x00007FF8097A485B ntdll.dll!RtlUserThreadStart+0x2b
[ JS Stack ]
RuntimeError: [INVALID ERROR CODE](0xE06D7363)
Exited with code 0xffffffff

does it occur for pure bdsx?
it seems your own scripts affect.

does it occur for pure bdsx? it seems your own scripts affect.

its a fresh install of bdsx

Its a brand new install of bdsx i launch the bdsx.bat and when i try to join i get an error and the server restarts

Thanks for reporting it.
the test had the error about setting the invalid spawn point. Sorry for not confirming for sure.
it's fixed on the latest commit.


add missed offline_access

without offline_access, the result won't return refresh token

Docs Build status updates of commit 43d98e4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-InsufficientPermissionOnRepo] User eric-urban does not have sufficient permission on https://github.com/MicrosoftDocs/Advertising-docs repository. Hint: required permission 'Read', actual permission 'None'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Merged in another PR to unblock. I'll investigate the validation errors next week.


Teams DLP scopping for SG/DL now GA

Teams DLP scopping for SG/DL seem now GA, so no more in Public Preview: https://techcommunity.microsoft.com/t5/security-compliance-identity/microsoft-further-extends-unified-data-loss-prevention/ba-p/2166321

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@chrfox Please merge this PR. Thanks


Grid problem fixed

Grid problem is fixed (issue #1004 )
Added md5 encode to utils

Please do not submit in the pull requests files from /dist/* directory. Those are generated by grunt and always create merge conflicts.


Remove need to set type and id on a resource class

At the moment, if you have a resource class e.g. PostResource, you have to set the type and id if they do not follow the conventions of dash-casing the class name and using the Model::getRouteKey() method. This duplicates configuration that is held on the Schema - i.e. the schema already knows what the type and id are.
If we always inject the schema into the resource class, then this would remove the need to set these two things because the resource could delegate to the schema.
The consequence of this is it means resources cannot be returned by a developer - as they would always need to be constructed with a schema - i.e. the resource container always needs to be used. However this isn't a problem because if the developer wants to return an arbitary resource they should be using DataResponse instead.

Implemented, will be in 1.0.0-alpha.2


KAFKA-9922:Update examples README

Class kafka.examples.SimpleConsumerDemo was removed. But the java-simple-consumer-demo.sh
was not removed and README was not updated.
Change-Id: Iff057ce91454b493859ace6c6959e674048e9678
Signed-off-by: Jiamei Xie<EMAIL_ADDRESS>More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji @guozhangwang Call for review

ok to test


Gradient

Your question
Can we set the default value of Pickr o Gradient? If yes, can you please guide. Thanks

Your environment:
Version (see Pickr.version):
Used bundle (es5 or normal one):
Used theme (default is classic):
Browser-version:
Operating-system:

I figured it out with custom CSS but is there any possibility to achieve this through the picker object? That would be better, right?

Or later on, set the preview/default color to the selected color. Is this possible?

Sorry, won't do that. Pickr itself is already difficult enough to maintain due to its age and setup. Pickr with gradients was a project a while ago though, you might want to checkout gpickr.
I'm considering working on a v2 with plugin support were that could be possible.


merge Navigation branch

Added information about the path_planner, path_manager, and path_follower nodes.
@iandareid We still need to replace that image on the path_manager with a nice image of a flight-test loop (showing what a fillet does). Would you be able to do that with your ROSbag -> Python plotting script?

I certainly will.


Move RenderableNode and DetailedNode into render/

A continuation of #228

Gimme another poke when those are resolved...

Sorry about that; the origin tests were originally using the report fixture from report/report_fixture_test.go, but I changed them to use the one from render_test.go.
I'll canonicalise a report fixture for the render module in a future changeset.

Thanks for making it more comprehensive. LGTM!


The address generated by Sparrow is now missing, along with funds

I run Sparrow through Bitcoin Core.
On April 17, I sent funds from my Coinomi wallet to one of my Sparrow software wallets. On that same day, I did another tx from that same Coinomi wallet to my Sparrow-connected Trezor for cold storage.
Today, April 19, I wanted to withdraw funds from the Sparrow software wallet. When I opened it, the balance with the recent deposit was displayed for a second, but then immediately reverted back to the previous balance after syncing was completed. Fearing the worse, I checked my larger Trezor balance, and I was relieved to see the recent tx was still there.
Blockchain explorers and my own Bitcoin Core node confirm the tx. What's strange is that the Sparrow-generated address is no longer found in the Receive Addresses.
I tried importing the wallet on other clients, but to no avail.
This seems to be similar to issue #125
Thanks in advance for your help.

Can you try to determine the index of the address you used, and check it against the sequential address indexes in Sparrow? Indexes start at zero and count upwards, and are shown in a tooltip when hovering over the address.
I would also consider recreating the Sparrow wallet (reimporting the Trezor) and testing against a public server.

> Can you try to determine the index of the address you used, and check it against the sequential address indexes in Sparrow? Indexes start at zero and count upwards, and are shown in a tooltip when hovering over the address.
Thanks for your reply, very much appreaciated. The issue is that the address I used is no longer found in the wallet's Addresses list.
> I would also consider recreating the Sparrow wallet (reimporting the Trezor) and testing against a public server.
No issues with the Trezor wallet, it's with the wallet I created with Sparrow.
I also recreated the Sparrow wallet on another computer, but to no avail.

Thanks for your reply, very much appreaciated. The issue is that the address I used is no longer found in the wallet's Addresses list.

What we are trying to determine here is if there is a numerical break in sequential address indexes. Assuming you used the next unused address, you should be able to determine this from the address tooltips.
Are you using a passphrase with this Trezor?

What we are trying to determine here is if there is a numerical break in sequential address indexes. Assuming you used the next unused address, you should be able to determine this from the address tooltips.

Got it. I checked and there is no break in the sequence.
Now regarding the Trezor setup: I tried to open the wallet and I got an error. Immediately I suspected a deeper issue, and found the log file. This is not my expertise but there seems to be a lot of error messages. Would seeing the log help?

Yes you can go ahead and attach it here. What error did you get?

From the log file it appears that the wallet file is locked, which can happen if Sparrow is already running in a different process. Try to determine if there are multiple Sparrows open, and close them all before retrying. As a last resort, rebooting the computer can help.

Thanks for your continued input, very much appreaciated.
 Now when I try to open the wallet in question, I get the following error (see screenshot).
Thoughts?

I need to clarify: I have a SOFTWARE wallet, as well as a TREZOR-CONNECTED wallet with Sparrow.
It's the software wallet that has the issue, not the Trezor wallet.
If the software wallet is corrupted, can I use the "recovery tool" that's mentioned in the error message?

Ah, that makes it much clearer.
Re recovery, it will be easiest to recover from the seed words you wrote down when you created the software wallet.

When I opened it, the balance with the recent deposit was displayed for a second, but then immediately reverted back to the previous balance after syncing was completed.

Did you add a passphrase? This behaviour you have described happens when you use a different passphrase when opening your wallet. Every passphrase creates a different, valid wallet with different addresses.

Yes I did have been using the same passphrase since the creation of that wallet (Feb 20).

Incorrect passphrases are almost always responsible for these kind of issues, especially given the behaviour you have described. Consider if there are any other variations of your passphrase you may have entered, and try them out.

Already tried several variations, but to no avail

Take it slow and keep trying - it is very likely a typo. I'm going to close this issue off as passphrase related. Good luck with the search!


Loop

Hello.
Is it possible to play a video in loop?

Looks like I found some solution:
calling "resume" of videoview in "onPlaybackStopped" method.
Not sure that this is correct way, but it works anyway.

In Strategy I prepared a allowsImmediateReplay for that purpose (actually it is a bad method naming, and I will change it anyway, in the future release). For now, Toro doesn't support this method yet. Because it is not that straightaway to determine when a playback properly complete. Some new Player API may not follow current MediaPlayer API and then onCompletion may not be called. So I would like to research a bit more to provide better support.
For now your workaround could work in your case. So keep it. I will try to add the support as soon as possible.

I see. Thank you for your reply.
If we started talking about future releases I have question:
Why you decided don't give access to Media Player from ToroVideoView?
In my case I was needed to mute sound or unmute. Or you have some another ways how to make it?

@Apisov You mean the built-in im.ene.lab.toro.widget.ToroVideoView class? I think the story is opposite: you have control to the MediaPlayer (here: it is the android.media.MediaPlayer). In ToroVideoViewHolder class (which holds a ToroVideoView as its Video player widget), you can see that I implemented many callbacks from MediaPlayer's interfaces. From there, If you use my built-in ViewHolder, you can override onPrepared method to have the control of the MediaPlayer object which has the responsibility to play your video. Note that this instance will be available after your Video is prepared (i.e onPrepared is the best place where you should access to it). And in my experience, you can control the Audio from there. Hope this help.

Thank you a lot for such a detailed answer. I missed this possibility to control MediaPlayer. This is what I was looking, yes.

@eneim hi , i have the same problem .. but the difference is that in my view holder the method "onPlaybackStopped" never called .. i don't know what is the problem ?

@AmrMohammed89 Hey can you make this as a new issue? And if it is possible please post your part of code where you use the widget too. Thanks!

I am using im.ene.toro2:toro-extended:2.1.0. I cannot find neither onVideoPrepared(MediaPlayer) nor isLoopAble(). Finally, I need to extend ExtVideoViewHolder and override getNextTarget()
@Override         public Target getNextTarget() {             return Target.THIS_PLAYER;         }


Allow for transaction steps without an input argument

Currently, each step in a sequence is expected to have a single input argument. I ran into a scenario today where I didn't the first step to accept any arguments as its job was to prepare data for the next step in my transaction.
Below is the code for what I was aiming to achieve:
  t.define "main.transactions.my_transaction" do
    step :prepare_data, with: "main.operations.prepare_data"
    step :process_data, with: "main.operations.process_data"
  end

# prepare_data.rb
class PrepareData
  def call
     # prepare data here
     Right(data)
  end
end

# process_data.rb
class ProcessData
  def call(data)
    # do stuff with data here
  end
end

And then I would call it like so: Main::Container["main.transactions.my_transaction"].()
When I do this, I get the following error:
ArgumentError: wrong number of arguments (given 0, expected 1..2)
from /Users/daniel/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/dry-transaction-0.7.0/lib/dry/transaction/sequence.rb:45:in `call'

as dry-transaction is expecting an argument for the first step in the sequence.
To get around it I have defined the call method in PrepareData like so: def call(_)
and am calling the transaction like so: Main::Container["main.transactions.my_transaction"].(nil)
Ideally we would be able to call a transaction without having to pass in an arg if nothing is required.
Thanks! ❤

Yep, we should totally support this. Thanks for the report, @dNitza. We'll probably do it after the work in #58, which is what we're actively developing atm.

Fixed in #69


How to pass params to widget?

I have a widget that will open a new tab upon click to google search the word user input in the chatbot message field but I can’t seem to find a way to pass the chatbot message as a param to the widget function

I know this is closed but if anyone else has a similar issue about passing data to a widget then I found you can use the payload  as in the ActionProvider class
const botMessage = createChatBotMessage(" ", {
      widget: MyWidget,
      payload: result.content,
    });

you can then access this in the widget
const MyWidget = (message) => {
  return (
    <div >
      {message.payload}
    </div>
  );
};


Fix README example

It's really a tragedy that we're in 2024 and code snippets in Markdown aren't easily compilable as part of standard CI workflows >.<


pedant modification

hopefully travis stays happy

Codecov Report

Merging #480 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #480   +/-   ##
=======================================
  Coverage   89.31%   89.31%
=======================================
  Files          52       52
  Lines        7423     7423
=======================================
  Hits         6630     6630
  Misses        793      793

Impacted Files
Coverage Δ

ophyd/device.py
90.99% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

haha yes!


[CT-1344] Unhandled error while executing test - 252005: Failed to convert current row, cause: [Snowflake Exception] unknown arrow internal data type(252732072) for FIXED data

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I tried running some dbt generic tests (unique, not_null, ..etc) for dbt-snowflake. I got the below errors
Unhandled error while executing test
252005: Failed to convert current row, cause: [Snowflake Exception] unknown arrow internal data type(252732072) for FIXED data
Expected Behavior
The generic tests should pass without any internal/abnormal errors.
Steps To Reproduce

dbt test -s (model_name)

Relevant log output
1 of 2 START test not_null_(model details) ....................... [RUN]
Unhandled error while executing test.(project name).not_null_(model details).4160c5e7fe
252005: Failed to convert current row, cause: [Snowflake Exception] unknown arrow internal data type(160100344) for      FIXED data

2 of 2 START test unique_(model details) ......................... [RUN]
03:31:21  Unhandled error while executing test.(project name).unique_(model details).9b30087e69
252005: Failed to convert current row, cause: [Snowflake Exception] unknown arrow internal data type(160100344) for FIXED data

Environment
dbt-core       1.2.1
dbt-snowflake  1.2.0
snowflake-connector-python   2.7.8
Python 3.9.12

Additional Context
No response

Closing as a duplicate of https://github.com/dbt-labs/dbt-snowflake/issues/288. From conversation on that issue, it sounds like the root cause here was a behavior change in a recent Snowflake release, which they're working to roll back.

Is there any update on this case? I just got the same error while trying to run dbt test


Adding of features to be GDPR compliant

Added deletion of user, ticket and tickets:

https://developer.zendesk.com/rest_api/docs/core/users#permanently-delete-user
https://developer.zendesk.com/rest_api/docs/core/tickets#delete-tickets-permanently
https://developer.zendesk.com/rest_api/docs/core/tickets#delete-multiple-tickets-permanently

@danielzimmermann looks good to me, thanks!

@danielzimmermann given this pull request is for GDPR, would you have time to also implement this endpoint? https://developer.zendesk.com/rest_api/docs/core/users#show-compliance-deletion-statuses

@johnou i can do that: https://developer.zendesk.com/rest_api/docs/core/users#show-compliance-deletion-statuses but i need a couple of days for that, because i am a bit under stress right now :)

LGTM. Good work @danielzimmermann Thx a lot


Tail kms logs instead of /dev/null

For context. There will be a PR from Ronny improving the logging. In order to check that it doesn't do anything unexpected we need to be able to view the logs generated by the CI. This PR allows for that.


Use our own init scripts

This replaces the init scripts shipped with CDAP with our own. These scripts are based on the original scripts, but only do kerberos configuration when configured. They, also, will source the Chef-delivered /etc/profile.d/jdk.sh to set JAVA_HOME for the services.

LGTM


Move README images to gh-pages

Move pngs out of repo so users aren't pulling the pngs on every clone. (Saves 4.3 MB, which is more than half of the repo's size. I think worth removing.)
Also requires my gh-pages branch commit 8a34ebc4aa4df92507c612fa691096c97c08dacf! (I don't know how to do a PR since you don't have a gh-pages branch.)
You can see that it works by browsing at my test commit (that used my repo's gh-pages): https://github.com/idbrii/ale/tree/no-img-in-repo-test
(I modeled this setup after what OmniSharp/vim-omnisharp does.)
Maybe we'd want to add the logo psd from 071c04da3d6cd5fa1a9f4d2d3d38448bf9ea0e1e to gh-pages?
Only three png links changed because README references to issues.png and no_issues.png were removed in ed8f79987d5a64c41f8b5c1c244243babde45d25. As far as I can tell (git log -S issues.png), they were not added anywhere else.

We've decided that we can't do this for now.  Removing images from the repository, such that the size of git clone is smaller requires rewriting the entire commit log, as if those files were never committed. That will cause a large number of problems that take more time to deal with than we have right now.
I do want the size of the repo to eventually be smaller.

This change doesn't rewrite the commit log and would provide a place outside of the repo to put images. Commits with new images would be more likely to follow the out-of-repo pattern.
While I understand why you wouldn't want to rewrite history, why not apply this change now to prevent further repo bloat?
Additionally, if someone wanted a tiny checkout, they could use git clone --depth 20  and so long as there were 20 commits after this one, the images should not be included in their checkout.
Also, by this comment:

Saves 4.3 MB, which is more than half of the repo's size. I think worth removing.)

I meant the size of the images themselves and not their storage in git history.

The PR would only make the download size smaller of you used --depth, and the PR can't be merged until the second repository for the images is created. I don't think it's worth the hassle at the moment.

It should be noted that ALE does have a separate repository already - the wiki itself is a separate repo. Further images or other documents that should not be involved in ALE itself can be put there.


Readme issues

The following links are not working:

I've setup three alerts configuration files:
Monitoring services alerts targets.rules
Docker Host alerts host.rules
Docker Containers alerts containers.rules

There are specified rules for Jenkins but Jenkins is not part of the installation. Is this only to show how failed alerts will look like? Maybe a comment about this would be nice in the Readme.

You are absolutely correct in regards to the file reference issue in the README.md I'm about to correct that.
Regarding the alert groups, they are intended to be used as examples.
Most people nowadays have multicore CPUs so they would want to change the node_load1 value from 1.5 to something more appropriate to the hardware they are running.
Likewise can be said for the Jenkins container example, you should adjust these in accordance with whatever alerts you would like to receive.


Cannot set previous tag. Create release notes from [old latest till new latest]

how to just create release notes based on release.yml containing only the info from the last latest release till the new one and not including everything from branch ? in simple terms how to set previous tag when creating release notes ?

Having this issue as well, every time a tag is created it includes the release notes from every previous version, makes this plugin unusable.

@waeljammal there is a pr opened https://github.com/softprops/action-gh-release/pull/372 but not merged yet. Also on the pr comemts there is a way to do that, while using another action to create proper release notes, and parse them as body on this action. Ill give it a try.


Disabling notification and sounds doesn't work

By pressing the "disable all notifications" button shaped like a bell, the sounds keep popping up when using WhatsApp within Franz.
Also, by right clicking de WhatsApp service, the text indicates all notifications should be disabled, but still sounds keep popping up when new messages arrive. Going to edit and disabling the service has the same effect.
There currently is no consistent way of disabling notification sounds from WhatsApp, not sure of other services.
Running on Franz 5.0.0.-beta.16.762

I also have this problem. It affects all of my services. I switch it off and next time I launch Franz it is re-enabled. Does my head in.

I have the same problem, also macOS 10.13.3 / Franz 5.0.0-beta.16.762.

Same here, I use Hangouts only and couldn't find any working way to mute the notifications
macOS 10.13.3 / Franz 5.0.0-beta.16.762

Same here, the mute does not mute telegram, not sure about the others. I'm using windows and 5.0.0-beta.16 version.  Does anyone know a fix for this, it might really turn me off using the service at all, even though otherwise I like it very much.

Same here - seems to be worst with WhatsApp
macOS 10.13.3 / Franz 5.0.0-beta.17.834

I have the same problem on Linux running Gnome and with Telegram as Service in Franz. Both options to disable Sounds (Settings in Service and in left toolbar) are enabled. There are still sounds on incoming messages.
Version: 5.0.0-beta.18
Release: 1.8.4 / linux / x64
Thanks for solving this issue.

Same problem here, my workaround was disabling sounds inside each service.
Version: 5.0.0-beta.18
Release: 1.8.4 / win32 / x64

#900

I have the same problem, on mac and windows. It seems to be for all applications as slack also can't be muted

Still having this issue on the latest MacOS High Sierra 10.13.6 and running Franz version: 5.0.0-beta.18

I have the same problem. the weird thing is that I had been using Franz on my old computer for a few weeks already without any problems. I have a new computer, which has the same OS (Windows 10) and
using the same version of Franz (5.0.0 beta 18) and now I am experiencing this issue.

I'm still having this problem in April of 2020. I turn all sounds off and still get notifications. Making matters worse, the sound upset my Westie, who freaks out. Is there a workaround? Thank you!


[release-1.3] VirtualInbound: dont modify filter chains in place

This is an automated cherry-pick of #16451

This needs to go in for the RC as it fixes a data race issue caused by the virtual inbound code.

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

istio-pilot-multicluster-e2e-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-pilot-multicluster-e2e-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

istio-pilot-multicluster-e2e-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-pilot-multicluster-e2e-release-1.3

integ-security-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-security-k8s-presubmit-tests-release-1.3

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

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

istio-pilot-multicluster-e2e-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-pilot-multicluster-e2e-release-1.3

integ-security-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-security-k8s-presubmit-tests-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

istio-pilot-multicluster-e2e-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-pilot-multicluster-e2e-release-1.3

integ-security-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-security-k8s-presubmit-tests-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

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.

/test istio-codecov-release-1.3

/test integ-pilot-local-presubmit-tests-release-1.3

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-pilot-multicluster-e2e-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-pilot-multicluster-e2e-release-1.3

integ-security-k8s-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-security-k8s-presubmit-tests-release-1.3

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

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.

Both integ-pilot-local-presubmit-tests-release-1.3 and istio-codecov-release-1.3 consistently with the same test failure:
https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/16672/integ-pilot-local-presubmit-tests-release-1.3/125
--- FAIL: TestEnvoyFilterHTTPFilterInsertBefore (5.56s)
    main_test.go:253: invalid http connection manager: invalid HttpConnectionManager.StatPrefix: value length must be at least 1 bytes
FAIL
FAIL	istio.io/istio/tests/integration/pilot/envoyfilter	5.597s

https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/16672/istio-codecov-release-1.3/185
--- FAIL: TestEnvoyFilterHTTPFilterInsertBefore (5.95s)
    main_test.go:253: invalid http connection manager: invalid HttpConnectionManager.StatPrefix: value length must be at least 1 bytes
FAIL
coverage: 8.1% of statements in istio.io/istio/...
FAIL	istio.io/istio/tests/integration/pilot/envoyfilter	6.153s

@rshriram please take a look and address the issue.

Yes I am fixinng these

After some investigation, this failure is expected. This PR depends on https://github.com/istio/istio/pull/16428.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

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.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-codecov-release-1.3
0f6ad3ec1cca008dc3e2a998acc80ba111152e73
link
/test istio-codecov-release-1.3

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.

/test integ-pilot-local-presubmit-tests-release-1.3

/test istio-codecov-release-1.3


Add ability to prevent ghosting

About the PR
Adds the ability to prevent a mind from ghosting. Perfect for admins who want to stop people they're admin abusing from escaping their fate.
Media

Please don't make me add a video ;-;

[X] I have added screenshots/videos to this PR showcasing its changes ingame
[ ] This PR does not require an ingame showcase

Can they still suicide? And if they do so, will they just be stuck in a dead body? This will also probably break cloning if enabled.


Introduce a script that checks the validity of a dataset before training

Motivation for the feature
Before training with a dataset, we might want to make sure that, e.g., the ground truth are the same size as the associated image, the ground truth exists, having an overview of the distribution of image sizes across subjects, etc.
@uzaymacar came up with this script, which notably checks the following:

resolutions and sizes for each subject image for data exploration,
performs basic shape checks for images and ground-truths (GTs),
checks if there are non-null GT in the associated image (because some pre-processing could crop the GT, leaving it empty)

The script is tuned for a specific project but we could potentially generalize it to any BIDS dataset.

Very interesting, I think it could be a great addition to the loader!
Currently, a lot of the function from the script are performed during the loading process in ivadomed, and we should be able to re-use them to generalize the script.
e.g.:

BidsDataframe for file indexing of an entire dataset, which includes function to check whether derivatives are available or not.
There is also a get_pair_shapes function in segmentation_pair.py that performs shape checks for images and ground-truth:

It could be useful to perform some of those checks outside/before the loading process to ensure validity and/or, have a more verbose loading process to detect errors.


assert_exception: Assert Exception head_block_num() == 0: last block ID does not match current chain state

./eosd/eosd --skip-transaction-signatures
2032328ms thread-0   chain_plugin.cpp:76           plugin_initialize    ] initializing chain plugin
2032328ms thread-0   chain_plugin.cpp:114          plugin_initialize    ] Setting skip_transaction_signatures
2032328ms thread-0   chain_plugin.cpp:123          plugin_initialize    ] Setting skip_transaction_signatures

                               *

-- EOSD IGNORING SIGNATURES --   *

    TEST MODE          -   *

------------------------------   *

                               *

2032328ms thread-0   http_plugin.cpp:109           plugin_initialize    ] host: <IP_ADDRESS> port: 8888
2032328ms thread-0   http_plugin.cpp:112           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
2032329ms thread-0   producer_plugin.cpp:133       plugin_initialize    ] Public Key: EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
2032329ms thread-0   net_plugin.cpp:773            plugin_initialize    ] Initialize net plugin
2032329ms thread-0   net_plugin.cpp:779            plugin_initialize    ] host: <IP_ADDRESS> port: 9876
2032332ms thread-0   block_log.cpp:88              open                 ] Opening block log at /Users/newworld/dev/eos/build/programs/data-dir/blocks/blocks.log
2032332ms thread-0   block_log.cpp:116             open                 ] Log is nonempty
2032332ms thread-0   block_log.cpp:124             open                 ] Index is nonempty
2032339ms thread-0   main.cpp:37                   main                 ] 10 assert_exception: Assert Exception
head_block_num() == 0: last block ID does not match current chain state
{"last_block->id":"0000060018f2f6edb136c19ca38a97c1d285bee9da3ac397d0c13695648331ca","head_block_num":1537}
thread-0  chain_controller.cpp:1151 spinup_fork_db
{"my->genesis_file.generic_string()":"/Users/newworld/dev/eos/genesis.json"}
thread-0  chain_plugin.cpp:169 plugin_startup

my bad,sorry.


File privacy

Allow the user to choose between "Only me", "Only with link", "Password protected"?

Also maybe some kind of encryption that the files actually be accessed without a logged in user session? (nice to have but maybe a selling point in the future)


Feature Form - Comments

The comments entered in Notes do not clear when you submit a change. So the next change you create has the same notes as you previously entered.
This should clear upon submit.

Workaround would be to manually clear this out.

Please retest in 0.8.1

Tested 0.8.1
Comments cleared out.


#include <swift/bridging> does not work on Windows

Windows is missing the bridging header in the toolchain distribution.  Furthermore, the header search paths would not be included by default.

CC: @hyp

https://github.com/apple/swift-installer-scripts/pull/260 should package that up.


YCSB mysql test always show low throughput and connections are in sleep mode

I am running YCSB benchmark testing against MySql database. With 1 thread, and 1000 batch size, 100% write/update, I am able to see 60ops/sec. That is way too low.
I used workloada, here is the parameters:
recordcount=1000000
operationcount=1000000
workload=com.yahoo.ycsb.workloads.CoreWorkload
readallfields=true
readproportion=0
updateproportion=1
scanproportion=0
insertproportion=0
fieldcount=1
fieldlength=4000
#requestdistribution=zipfian
requestdistribution=latest
The command that I use is:
./bin/ycsb load jdbc -P workloads/workloada -p db.driver=com.mysql.jdbc.Driver -p db.url=xxx -p db.user=xxx -p db.passwd=xxx -s -threads 5 -p db.batchsize=1000 -p jdbc.fetchsize=1000 -p jdbc.autocommit=false -p jdbc.batchsize=1000
When I look at mysql process list in mysql database, I see that all connections are in sleep mode.  What could be wrong?

The time for each operation is not just the time to process the query on the server. It includes the time to:

The YCSB client to prepare the select query.
The client to parse the select statement in the mysql driver,
The client to marshall the query to bytes and send the message to the server,
The message to transfer over the network from the client to the server
The server to decode and execute the query,
The server to marshal the result back to the client,
The results to transfer from the server to the client,
The client mysql driver to decode the response,
The YCSB client driver to process the results and return the status.

In my experience steps 4 and 7 (network latency) will take the lion share of the request time. The only way to combat that is to:

move the client closer to the server and
create more client threads which will keep more requests in flight at one time.

You will want to experiment with gradually increasing the number of threads to determine the optimal value.

Hi Allan,
Thanks for replying my question.  When I am monitoring the mysql process list, 99.9% of the time, YCSB mysql thread is in sleeping mode, that probably means that the client is busy preparing the data to load to the database.  This doesn't make sense to me, since the purpose of YCSB is to stress test the MySql database, I would expect the client is fast enough to stress the DB.

Is the client running on the same machine as the MySQL server? If not what is the ping time between the two machines?

The client machine is not running on the same machine as MySQL server. The ping time between two machines is about 15ms.

I think there may be a couple things going on here.
First the 15ms ping time means that the maximum operation rate that you can possibly see is ~67 (1000ms/15ms) operations/thread. You are using 5 threads to that gives a upper bound of 355. There is some overhead in MySQL and the client but those should be much smaller than the network latency. If we assume 1 ms on each side (17ms total) we are down to 295 operations per second.
Since you are only seeing 60 ops/sec there is something else still going on.
I also noticed that you have specified to use batching (db.batchsize=1000) but you have not turned on batching via the JDBC Batch API (jdbc.batchupdateapi). I think that means that the 1000 insert statement are being sent to the MySQL server one at a time to be added to a single batch transaction. There is then another round trip to the MySQL server to commit the transaction. I think that adds to the lack of load on the server.
Can you try turning on "-p jdbc.batchupdateapi=true" and see if that improves the performance? I would also be interested to see what the performance is without batching...

closing as stale. if you're still facing issues please reopen and address the questions above.


Horseman exiting when PhantomJS has an error

We're running a fairly complicated set of tests and the last few days for some reason they've been failing. Most of the time it prints the following error:
{ [HeadlessError: Error parsing JSON from phantom: SyntaxError: Unexpected token E
Data from phantom was: Error 403: Directory Listing Denied
Directory listing denied]
  name: 'HeadlessError',
  message: 'Error parsing JSON from phantom: SyntaxError: Unexpected token E\nData from phantom was: Error 403: Directory Listing Denied\nDirectory listing denied' }

... and then exits. But sometimes it just plain exits with no logging (odd).
I'm wondering if there is a specific reason for this behavior, or maybe an undocumented option that can cause horseman to behave differently when something goes wrong in phantom?
Our ideal here is to have our series of tests continue even if one has an issue (and we'd like to log the issue we're having with as much info as possible). But the major hangup is the script exiting.
(note: I'm aware this could be user error, but I'm not 100% familiar with the script or horseman yet so any help is appreciated).

When you say horseman exits, do you mean the node process dies or that the horseman instance stops working but node is still running?

Entire process dies. Sometimes it's the error above and sometimes it's 100% silent. Just trying to figure out my best course of action to debug/try+catch/something. Any direction is appreciated!

Have you tried running it with the environment variables DEBUG=horseman and BLUEBIRD_DEBUG=1? I would see what that gives you.

Is there a specific page you're hitting that causes this? I wonder if the error is in horseman or node-phantom-simple.

Well, it's more complicated I ear @johntitus

We're running on AWS, so it would seem many sites we scrape block AWS IP's by default
If they don't block AWS by default, they surely block it as DDoS if we run it too many times an hour ;)

The script SEEMS to be exiting when scraping a URL similar to: https://www.airbnb.com/users/show/148984
I'll try and reproduce, and @ThePatShea might be able to chime in as well.

I am also getting this issue, is there a work around for it?

https://github.com/baudehlo/node-phantom-simple/issues/109

Any progress on this @framerate? I did some things in v3 that might help with this, but I'm not sure since I cannot reproduce this.

Testing v3... will give feedback soon

Okay... So I couldn't use the WIP v3 due to a few bugs, but I found a way to reproduce the bug.
Run the code for 20 mins and you should see it come up
const Horseman = require("node-horseman");

var browserIsReady = true;

function reachPage() {

  var horseman = new Horseman();
  console.log("Starting...");

  horseman
  .viewport(800, 600)
  .open("https://www.facebook.com/bbcnews")
  .status()
  .then(function (status) {
    if (Number(status) != 200) {
      console.log("Couldn't load page, trying again...");
      return horseman.close();
    }
  })
  .wait(1e4)
  .log("Stepping out...") // prints out the durl
  .wait(3e3)
  .finally(function() {
    horseman.close();
    setTimeout(reachPage, 3e3);
    return
  });

}

reachPage();

Thanks for the script @ohenepee, I should have time to try it myself this weekend.
Also, if you want to make issues for what you found wrong with v3 that'd be appreciated (though not necessary).

I've been running it for about a day now at it has yet to stop working for me...

Wow!... On Ubuntu or Windows?

Ubuntu

I just accidentally restarted the machine running it, but it hadn't had an error.

I met this kind of error too, randomly. I will set debug flag and capture to see what happens.
I think, sometime's phantomjs or node-phantom-simple get error, this is acceptable.
What I concern is, there should be a way to catch it, skip this failing crawl and go on. The situation is: we can't catch it, the while node process died.

fix is required in node-phantom-simple.js, request_queue function. Add 403 to the error codes.

@mato75 ，You mean？
433       var req = http.request(http_opts, function (res) { 434         var err = res.statusCode === 500 ? true : false; 435         var data = '';

var errorsCodes = [403, 500];
      var req = http.request(http_opts, function (res) {
        var err = errorsCodes.indexOf(res.statusCode) !== -1;
        var data = '';

        res.setEncoding('utf8');

        res.on('data', function (chunk) {
          data += chunk;
        });

        res.on('end', function () {
          phantom.POSTING = false;

          if (!data) {
            // If method is exit - response may be empty, because server could be stopped while sending
            if (method === 'exit') {
              next();
              callback();
              return;
            }

            next();
            callback(new HeadlessError('No response body for page.' + method + '()'));
            return;
          }

          var results;

          try {
            results = JSON.parse(data).data;
          } catch (error) {
            // If method is exit - response may be broken, because server could be stopped while sending
            if (method === 'exit') {
              next();
              callback();
              return;
            }

            next();
            callback(new HeadlessError('JSON parse on req with data: ' + data + ', error: ' + error + ', method: ' + method));
            return;
          }

          if (err) {
            next();
            callback(results);
            return;
          }

          if (method === 'createPage') {
            var id = results.page_id;
            var page = setup_new_page(id);

            next();
            callback(null, page);
            return;
          }

          // Not createPage - just run the callback
          next();
          callback(null, results);
        });
      });

Thanks @mato75 ，I will try
@awlayton I met this problem again, node process exit silently without any ... notice
The last log I got:

Start : http://www.amazon.com/gp/product/B00DQYX9ZK amazon.com 1863
horseman .setup() creating phantom instance on 13155 +7ms
horseman setting viewport() to width 1280 height 2048 +2ms
horseman phantom created. +110ms
horseman page created +8ms
horseman .open http://www.amazon.com/gp/product/B00DQYX9ZK +4ms

As for the 403, I have created an express server that responds with it. However I am still unable to reproduce the error @mato75 and @zhaorenjie (node does not exit and nothing is printed about an unhandled rejection).
Also @zhaorenjie, are you describing two difference errors with the two logs you posted? I am not entirely clear on what you are trying to report.

@awlayton They are two different errors I believe, all connected to this topic "HM exit when PhantomJS error".
One is, it seems PhantomJS always exit silently after a 30 secs  downloading, then HM exit, node exit with no further error / debug info reported.
The other is, after applied @mato75 's mod to node-phantom-simple, I still get 403 errors and exits, but less often.

Could you post the output of npm ls @zhaorenjie? I am still unable to reproduce the 403 error, and I am trying to figure out what is different. Thanks.

30s timeout is a watchdog_clear timeout in bridge.js (node-phantom-simple). You need to comment out process.exit(0);
This is used, when a page doesnt get any responses for 30s, phantomjs instance is closed. This is not ok, for when when you are running multiple pages in one phantomjs instance.

Perhaps make a request to node-phantom-simple to allow changing the watchdog timeout @mato75? That is not something to be fix from horseman unless such an option exists.

https://github.com/baudehlo/node-phantom-simple/issues/124

Can anyone verify if the original issue is still present in v3, and if so please post code to reproduce it. I have yet to be able to produce this bug myself.

I'm having a similar issue: I am scraping URLs and I am trying to make it gracefully handle URLs that timeout. Even after wrapping the code with a try/catch and adding an on error handler, the code still grinds to a halt fatally:
var Horseman = require('node-horseman');
var horseman = new Horseman();

try {
	horseman.on('error', function() {
		console.log('error event triggered');
	})

	horseman
		.userAgent("Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0")
		.open('http://<IP_ADDRESS>:1234')
		.then(function() {
			console.log('URL Loaded');
		})
		.finally(function(){
	    horseman.close();
		});
} catch (e) {
	console.log("Caught error");
}

Unhandled rejection Error: Failed to GET url: http://<IP_ADDRESS>:1234
    at checkStatus (/home/stephen/Downloads/communistcast/node_modules/node-horseman/lib/actions.js:78:16)
    at PassThroughHandlerContext.finallyHandler (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/finally.js:56:23)
    at PassThroughHandlerContext.tryCatcher (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/promise.js:502:31)
    at Promise._settlePromise (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/promise.js:559:18)
    at Promise._settlePromise0 (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/promise.js:604:10)
    at Promise._settlePromises (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/promise.js:683:18)
    at Promise._fulfill (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/promise.js:628:18)
    at /home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/nodeback.js:42:21
    at /home/stephen/Downloads/communistcast/node_modules/node-phantom-simple/node-phantom-simple.js:60:18
    at IncomingMessage.<anonymous> (/home/stephen/Downloads/communistcast/node_modules/node-phantom-simple/node-phantom-simple.js:645:9)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:905:12)
    at nextTickCallbackWith2Args (node.js:441:9)
    at process._tickCallback (node.js:355:17)

Unhandled rejection Error: Failed to load url
    at checkStatus (/home/stephen/Downloads/communistcast/node_modules/node-horseman/lib/index.js:276:16)
    at tryCatcher (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/util.js:16:23)
    at Function.Promise.attempt.Promise.try (/home/stephen/Downloads/communistcast/node_modules/bluebird/js/release/method.js:39:29)
    at Object.loadFinishedSetup [as onLoadFinished] (/home/stephen/Downloads/communistcast/node_modules/node-horseman/lib/index.js:274:43)
    at /home/stephen/Downloads/communistcast/node_modules/node-phantom-simple/node-phantom-simple.js:636:30
    at Array.forEach (native)
    at IncomingMessage.<anonymous> (/home/stephen/Downloads/communistcast/node_modules/node-phantom-simple/node-phantom-simple.js:617:17)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:905:12)
    at nextTickCallbackWith2Args (node.js:441:9)
    at process._tickCallback (node.js:355:17)

A try/catch won't handle rejections @stephen304, they handle things being thrown. Did you try .catch on the Promise chain? That is how you handle rejections.

.catch can handle the first error, but it still exits with the second error, maybe I'm missing an extra place I need to .catch?

It's possible that a promise inside horseman somewhere is having an unhandled rejection. I can' think of one, but it's possible. If that is the case you can't .catch it as a user of horseman.
Also, your stack traces are not too useful. You need to have BLUEBIRD_DEBUG=1 for them to be very helpful @stephen304.

@awlayton What's the specs of your test/development machine... this question might be too invasive but I realized that the PhantomJS executable actually crashes as a result of CPU max'ing (100%) upon a random launch or resource-intensive processing... I can confidently say from experience that no one should be getting this error on a quadcore with 4GB+ RAM... @awlayton you can create a virtual instance to test this... try a single core with 1-2GB RAM, then move up gradually with the number of cores and RAM size after some minutes of tests using the script I posted some time ago

I was running it on the machine at my desk which I recently rebuilt @ohenepee , so it's pretty powerful:
6 core i7 CPU
64 GB ram

So if the issue happen when running out processor power, I guess that won't happen on that computer. I have some deadline coming up at work, but some point in the future I should be able to test in a VM or something.

@stephen304 just place .catch in node-horseman/lib/index.js:273

To what version are you referring @Gazaret? In the current version, line 273 is this:
        function loadFinishedSetup(status) {

@awlayton in this function, on line 280 reject. After reject need place .catch

That would defeat the purpose of the .reject() @Gazaret. Inside that if is an error condition. A .catch at the end of the chain of horseman actions should catch that reject.


Draft pr for load-testing

Generated from main.tsp https://github.com/MaryGao/azure-rest-api-specs/blob/loadtesting-sync-mary/specification/loadtestservice/LoadTestService/tspconfig.yaml
Breaking change
1. properties in model TestRun are removed
https://github.com/Azure/azure-sdk-for-js/pull/26166#discussion_r1231796844
2. The return type of ListMetricDimensionValues changed
https://github.com/Azure/azure-sdk-for-js/pull/26166#discussion_r1231808739
3. New supported features
Compared with last gen we introduced new features which caused codegen-side breaking and we can't avoid to mitigate. And I would suggest to respect these changes.

readonly/@visibility("read")
patch method
error response def moved to core
paged def moved to core

Closed as resolved


S16-io/eof.t broken on WSL from run-with-tty/script command

The script command is dodgy on WSL (windows subsystem for linux) and breaks testing in different ways depending on your version.  On ubuntu 16.04 the test correctly skips but before skipping it tries to run the 'script command' which messes up the terminal.   'stty sane' works for me.  This problem seems scheduled to be fixed and is documented here https://github.com/Microsoft/WSL/issues/2053 and here https://github.com/Microsoft/WSL/issues/129 .  S16-io/eof.t depends on run-with-tty from Test::Util and thus the 'script' command.  I no longer have ubuntu 14 but remember that the same test hung in that wsl version because of different problems with the script command.
I am suggesting that the test be fudged to skip for wsl and later we can look for a way to test for a wsl version/release that supports the script command properly.

:+1: on fudging for wsl


HC-436: Add Exponential Backoff when downloading assets

related ticket:

https://hysds-core.atlassian.net/browse/HC-436

change(s):

added exponential backoff to download_asset.py
adde status code checking, will raise http Exception if code in range not in range [200, 400)

@pymonger  what are the status codes we are expecting, i included 300 status codes because the function name is called handle_redirects
also what is the best way to test these functions
can't seem to find download_asset.py in our jenkins build logs

@pymonger @mcayanan was able to test it with pele's rate limiter, i changed the /test/echo endpoint's limiter to 1/minute to force a 465 error
was able to test it more thoroughly
(mozart) hysdsops@ip-###-##-##-###:/tmp$ for i in {1..1000}; do python ~/mozart/ops/hysds-framework/download_asset.py http://###.##.##.###:8877/api/v0.1/test/echo?echo_str=hfdjkfhkj /tmp/foo; echo $i; done
1
429 {"message": "1 per 1 minute"}

2
429 {"message": "1 per 1 minute"}

429 {"message": "1 per 1 minute"}

3
429 {"message": "1 per 1 minute"}

429 {"message": "1 per 1 minute"}

429 {"message": "1 per 1 minute"}

429 {"message": "1 per 1 minute"}

429 {"message": "1 per 1 minute"}

Traceback (most recent call last):
  File "/export/home/hysdsops/mozart/ops/hysds-framework/download_asset.py", line 55, in <module>
    handle_redirects(args.url, args.path, args.token)
  File "/export/home/hysdsops/mozart/lib/python3.9/site-packages/backoff/_sync.py", line 105, in retry
    ret = target(*args, **kwargs)
  File "/export/home/hysdsops/mozart/ops/hysds-framework/download_asset.py", line 41, in handle_redirects
    raise requests.exceptions.HTTPError(r.status_code, r.text)
requests.exceptions.HTTPError: [Errno 429] {"message": "1 per 1 minute"}

what do you think the backoff values should be, i set max_tries to 5 and max_value to 32`, should this be increased?

I think this looks good, but will wait for @pymonger to chime in. Regarding the backoff, I see this set up in osaka:
https://github.com/hysds/osaka/blob/981b57602d8e4adb02aa49a6d6e18715d12f9dde/osaka/utils.py#L126-L128
I'm wondering if the same set up should be made here. Specifically, I'm wondering if using jitter and factor is sort of the best practice way of using backoff.

@DustinKLo @mcayanan: I'm back from the NITT-19 testing hole. ;)
This looks good to me as well and should be enough to throttle down on our github rate limit issue. If it persists then we can create another ticket to tweak the backoff knobs.