Cutover to CNCF Slack

Motivation
In an effort to improve vendor independence can we please start using the CNCF slack as our official source of truth for Slack?

Feature
We can use the following slack feature to begin the migration so that no disruption is caused to our existing slack: https://slack.com/resources/slack-for-admins/shared-channels-in-slack

Alternatives
One alternative would be to do a cold-cutover (maybe over the holiday?) to make this as seamless as possible.

Additional context
We will be discussing this during the OSS call today: https://github.com/falcosecurity/community/issues/64

Dup of #888

/triage duplicate

Let's close #888 since this has more context?

Good for me.

/remove-triage duplicate

Should we make the channel on the sysdig Slack read only after writing a message about the migration?

Works for me - I think we just need an owner here - do you want to take this one @fntlnz?

/assign @kris-nova
@caniszczyk do you know if the CNCF will let us do shared slack channels?
We talked about this on the Falco call today, and we think this approach would be the best so we aren't forcing everyone to leave/re-join a new slack channel. The CNCF would be the source of truth and the currently slack channel just mirror that.
https://slack.com/resources/slack-for-admins/shared-channels-in-slack

@kris-nova no due to the privacy policy implications, the CNCF channel needs to be source of truth

Ah sorry - that is what I was trying to get to. Having the CNCF be the source of truth, and then sharing the channel with other slacks. If it's not possible we can just use the CNCF slack - just trying to be as disruptive as possible.
CC @caniszczyk

Hey all,
I know we had a conversation going about doing this around KubeCon, but we should look to tackling this in April.
Rough timeline:

Announce that we're moving to the CNCF channel week of April 6th?
-- Cutoff of April 30th for move?
-- May 15th turn to read only?

Does that sound like a reasonable timeline?

@kris-nova: does the above seem like a reasonable timeframe?

AFAIK @kris-nova is handling this but she’s out this week.
On Tue, 7 Apr 2020 at 20:39, Amye Scavarda Perrin<EMAIL_ADDRESS>wrote:

@kris-nova https://github.com/kris-nova, @fntlnz
https://github.com/fntlnz, checking back in here - can we look to doing
this this week?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/983#issuecomment-610553844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5J44GRYPC56RJJLVHPF3RLNXNBANCNFSM4J4KVZHQ
.

--
L.

Good to know! I'll check back in on Monday.

Hey @kris-nova! I know we're past the early April timeline, here's updated:

Announce that we're moving to the CNCF channel week of April 13th?
Cutoff of April 24th for move?
April 30th read only

With the recent security concerns with zoom - can we revisit this for open source comms?
We have mentioned possibly adopting a tool like matrix. Let's bring this up on the next weekly call (which I am leading).

New timeline as promised in April 22nd Falco call
Steps:

Which channels are being actively used that need to be created in CNCF Slack?
-- Finalize by EOD April 27
Announce that we're moving to the CNCF channel week of April 27th
Cutoff of May 8th for move
May 11th for read-only date with topics pointing to where discussion is happening

Hey all, checking in on this timeline again from the April 22nd call: @kris-nova
What channels need to be created in the CNCF Slack to make this seamless?

A better update from the Slack team: https://slack.com/help/articles/217872578-Import-data-from-one-workspace-to-another is possible!

Let us know when you want to do the export/import dance, we've submitted a PR to fix Slack references on the website, I don't know if there are others in .md files but couldn't find any.
https://github.com/falcosecurity/falco-website/pull/193

Hey thanks for reaching out. In a perfect world we could get this done ASAP - I think we are all ready to have this knocked out at this point.
During the call @amye mentioned that projects like Kubernetes and OPA were able to get a dedicated slack org, that was under the cncf umbrella.
I went ahead and created falcosecurity.slack.com and made a handful of Falco maintainers, @caniszczyk, @amye, and Ihor all owners.
Is there anything else we can do so that this new org is "under the CNCF umbrella"? Then we can do the import/export dance and move all the Falco channels over to this new org?

@kris-nova we have enterprise accounts for Kubernetes and CNCF which retain all message history, CNCF won't cover the costs for new Slack enterprise given our contract with Slack, this is why we encourage folks to move to either the Kubernetes slack (like KEDA) or CNCF (most other projects).
For projects like OPA we still have to migrate them somewhere.

So we have never had any issues with slack content history in the past. This is the first anyone has ever brought it up to my knowledge.
Can we just use the free plan and have the CNCF be owners/admins with as well as the Falco community? I believe the enterprise slack plans let you do an export of public/private channels as well as DMs https://slack.com/help/articles/201658943-Export-your-workspace-data
So if we move the slack over to an enterprise org I would like to inform the community (we are a security community after all) that the new workspace will not have the same privacy guarantees as to the old one.

@kris-nova we don't prefer that route as what eventually happens is communities want to upgrade to a pro plan to retain history and make it searchable, this has happened with multiple CNCF projects in the past along with Kubernetes.  We also have slack admins staffed in both the Kubernetes and CNCF Slacks to deal with any major issues.

Is there a path forward where we can retain the community's sense of privacy while still satisfying the concerns of having a slack under the CNCF umbrella?
If that is not an option - and this is a mandate - I would still like to be very clear about the privacy concern here for our community members. Having a safe place to work/collaborate is very important in driving adoption and creating a sense of safety within the community.
I can't help but wonder if there is a path forward that satisfies all these cases:

Getting real-time comms in a place that addresses for the CNCFs concerns
Preserving our communities sense of privacy
Being as non-disruptive as possible for end-users and contributors

If we have to take the privacy hit - then so be it - we should just make it well known that all conversation is to be considered readily available by the CNCF.
As security-focused community privacy is our top priority and we wouldn't want to jeopardize any of our end users leaking trade secrets or sensitive detail about their stack. We have real production users who at times need to share sensitive detail about their stack with owners in the Falco project for guidance. If there is a risk of that sensitive detail being leaked without their knowledge we as an open-source community owe them a warning.

We require everyone to abide by the LF/CNCF Privacy Policy which has I think has stronger guarantees than what is currently offered by Sysdig or most companies for that matter (couldn't find your privacy policy online):
https://www.linuxfoundation.org/privacy/
There's also a track record of the Kubernetes and CNCF Slacks over the last 5 or so years to consider with nearly 100,000 users in slack.
I think offering end users a heads up when they join that this privacy policy applies https://www.linuxfoundation.org/privacy/ and the code of conduct would be great.

Okay so path forward:

Update the documentation on falco.org with the new slack workspace.
Add a warning to falco.org website that references the LF privacy policy. Specifically this bit:

Communications. When you communicate with us (via email, phone, through the Sites or otherwise), we may maintain a record of your communication.

Do the import/export dance once the website changes go live.

Sound like a plan to everyone?

Also regarding the import/export - should we offer the community time to opt-out before we add users to a new workspace with a presumed privacy policy? I have never done this before so I am learning as I go here. I am just asking myself -- what would I want as a user.
I think I would want to understand what is happening - and how that would impact me - and have an easy way to opt-out.

The plan sounds great, when Amye is back from vacation next week she can
take the lead to work on this with you.
re: user opting out timeframe sounds like an awesome idea, we should make
that as part of the announcement and say that here is the timeline, when
the transition will happen and if you want to opt you, do it before this
date (and here is how to do it).
On Fri, May 8, 2020 at 12:36 PM Kris Nova<EMAIL_ADDRESS>wrote:

Also regarding the import/export - should we offer the community time to
opt-out before we add users to a new workspace with a presumed privacy
policy? I have never done this before so I am learning as I go here. I am
just asking myself -- what would I want as a user.
I think I would want to understand what is happening - and how that would
impact me - and have an easy way to opt-out.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/983#issuecomment-625931503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSINTWS74WW5B7E75JHTRQQ7JXANCNFSM4J4KVZHQ
.

--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1<PHONE_NUMBER>

Sounds great - I think I speak for all of us when I say how excited we are to have support for Falco from the CNCF like this.
I will bring this thread up during out next community call and as soon as we have everything in place we can merge the changes to the website.

Hey @kris-nova, what do you think about this timeline?
Which channels are being actively used that need to be created in CNCF Slack?

Finalize by EOD May 15
Announce that we're moving to the CNCF channel with user-opt out
May 18
Cutoff of May 22nd for move
May 26th for read-only date with topics pointing to where discussion is happening (accounts for US Holiday)

Yeah this looks good - We are announcing the changes this week and will have updates to the website and github repositories to work in concert with them as they go live
We should see a warm cutover before next week's community call next wednesday, and a deprecation model put in place before permanently archiving our current slack
I will post updates here as they happen, and will not close the issue until we are completely cutover

thanks for being patient with us :)

oh this is excellent news! Thank you!
On Tue, May 19, 2020 at 10:51 AM Kris Nova<EMAIL_ADDRESS>wrote:

Yeah this looks good - We are announcing the changes this week and will
have updates to the website and github repositories to work in concert with
them as they go live
We should see a warm cutover before next week's community call next
wednesday, and a deprecation model put in place before permanently
archiving our current slack
I will post updates here as they happen, and will not close the issue
until we are completely cutover
thanks for being patient with us :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/983#issuecomment-630980624,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2FGJNDPBEWRDPEM3FO23RSLBJXANCNFSM4J4KVZHQ
.

--
Amye Scavarda Perrin | Program Manager |<EMAIL_ADDRESS>

Following up on the weekly call that just happened.
The community seems to agree that we would like to move to the Kubernetes slack officially.
Some links and resources to share the good news:

Pull Request to Falco.org
Pull Request to Kubernetes community
Notes from the call

These are subject to change and will ultimately be documented in the community repo

The next steps

[ ] Announce in the existing falco slack
[ ] Set the existing slack to read-only and point to Kubernetes
[ ] Announce on the mailing list
[ ] Begin using the Kubernetes slack
[ ] Send the Falco maintainers wine and cheese to say thank you for their hard work

Community call notes (+ YT video) for today call are here: https://github.com/falcosecurity/community/blob/master/meeting-notes/2020-05-20.md

Also, this PR updates the slack URL in the organization-wide CONTRIBUTING.md file (so that all the other Falco projects will have it into their inherited CONTRIBUTING.md file).
PR: https://github.com/falcosecurity/.github/pull/9

@kris-nova @leodido Could you please fill in some blanks as to why between yesterday and today this appears to have pivoted from CNCF Slack and Kubernetes Slack? I think there may have been some discussion on your side that is not recorded here so the reasoning is not obvious :)

What blanks are you missing?
Following this thread above :point_up: there was a strong encouragement to move to a slack under "the CNCF umbrella". @caniszczyk let us know that there would not be funding available in the case a newly created slack wanted to move from the free version to enterprise.
This left the Falco community with 3 options.

Migrate to our newly created workspace https://falcosecurity.slack.com/#/ (0 users)
Migrate the CNCF slack workspace https://slack.cncf.io/ (16k users)
Migrate to the Kubernetes workspace https://slack.k8s.io/ (100k users)

We picked slack.k8s.io.

The decision was made on our weekly call

Ultimately there a few things I would like to remind everyone of.

This was a disruption and a nuisance to the Falco end-users, as well as the maintainers. We did this out of good faith and chose the path that we felt would be the best for everyone. Slack exists as a convenience tool so that a community can thrive. We were (and still are) happy to hand over root access to slack.sysdig.com. This transition was driven by the CNCF for reasons I don't completely understand.

Conversations will always happen in places we can not control. Part of being a good manager and a healthy leader is sharing context, not control. We will never be able to completely control the conversation and where they happen. There is a reason that there are falco channels in the following places.

slack.k8s.io
slack.sysdig.com
slack.cncf.io
github.com/falcosecurity
freenode channel #falco
reddit
etc

We see this same pattern with Kubernetes.

We are here to share and build healthy software. The Falco community was forced with a difficult decision for reasons our community did not understand, and given the constraints of the decision we picked one of our 3 options. So far the community seems to welcome and embrace the change in a warm way.

I think the fact that the community is welcoming this change in a warm way, and that the constraints defined above were met -- is a sign of success.

If you do not agree with this decision.
If you do not like this decision.
If you do not understand this decision.

We would love to see you on one of our weekly calls or in the mailing list where we are happy to discuss other avenues and disrupt our community yet again if you are interested in driving this change.


Unhandled 'error' event

Hi, I'd like to use your tool but can't figure out what's the problem .
I installed it and ran the commande, here is what I have :
λ webpack-init
? Enter the file name for your webpack config webpack.config.js
? Enter the filename for your entry ./index.js
? Enter the output path, this is where your images and js will be output at ./dist
? Enter the output filename bundle.js
? Is your output in a different directory? Yes
? Enter the path to where you will point to in your index.html e.g. /static/
? What loaders would you like to include?
              Note some loaders may require extra configuration. See
              https://webpack.github.io/docs/list-of-loaders.html  babel,  sass
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at exports._errnoException (util.js:907:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)

It happens when I select babel & sass loaders then push the enter key.
Could you help me ?
thank you in advance

Hi @benavern thanks for letting me know. Will take a look.

Hi @benavern I published a new version to make install a bit more user friendly. Which should give some more visibility into where in the install process this is happening.
Also, what version of Node & NPM are you using? I tested this out on Node 6.7.0 and NPM 3.10.3 and I'm not getting this error.

Hi @benavern closing this as I've not heard back in a few weeks as I was unable to replicate. Feel free to reopen, if you have experienced this again.


Help Command not working

Version of Komada
0.21.1
Are core files modified?
Nope
Describe the problem
When I try the help command it says
"":x: | You have DMs disabled, I couldn't send you the commands in DMs."
but if i try eval message.author.send(something) is working
and is working to send messages to the bot too
I have like 45 commands + System commands
Expected Behaviour
To be sending me all the commands
Actual Behaviour
It sends me nothing
Steps to Reproduce.
I used help
didn't work
i used eval message.author.send(something)
worked
i messaged the bot
worked
i used help again
didn't work

Due to the nature of the command (and how old it is really..) it's probably due to another error. You can confirm this by transfering the help command and console.log()'ing the error that's being returned.

I changed a bit the command and it says in DM that i have DMs disabled

You still didn't do what i said though. You need to log the actual error that's being thrown.. obviously it's not that you have DMs disabled..
Change the .catch() to log the exception instead of saying "You have DM's disabled"

This is the error i got

Apparently your message is too long to send. You'll have to edit the formatting of the command or split more.

aaaand how do i do that? (im new in programming ;-;)

categories

Now is working, i made 2 help messages and sends me every command
  const helpMessage = [];
  const helpMessage2 = [];
  for (let cat = 0; cat < categories.length/2; cat++) {
    helpMessage.push(`**${categories[cat]} Commands**: \`\`\`asciidoc`);
    const subCategories = Object.keys(help[categories[cat]]);
    for (let subCat = 0; subCat < subCategories.length; subCat++) helpMessage.push(`= ${subCategories[subCat]} =`, `${help[categories[cat]][subCategories[subCat]].join("\n")}\n`);
    helpMessage.push("```\n\u200b");
  }
  for (let cat = categories.length/2; cat < categories.length; cat++) {
    helpMessage2.push(`**${categories[cat]} Commands**: \`\`\`asciidoc`);
    const subCategories = Object.keys(help[categories[cat]]);
    for (let subCat = 0; subCat < subCategories.length; subCat++) helpMessage2.push(`= ${subCategories[subCat]} =`, `${help[categories[cat]][subCategories[subCat]].join("\n")}\n`);
    helpMessage2.push("```\n\u200b");
  }
  return msg.author.send(helpMessage, { split: { char: "\u200b" } })
    .then (() => { msg.author.send(helpMessage2, {split: { char: "\u200b"}})})```


Update toolbar to use PF DataToolbarChipGroup interface

Replace workarounds for PatternFly's DataToolbarFilter with the new DataToolbarChipGroup interface.
https://github.com/project-koku/koku-ui/issues/1523

Codecov Report

Merging #1524 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1524   +/-   ##
=======================================
  Coverage   76.26%   76.26%
=======================================
  Files         199      199
  Lines        3590     3590
  Branches      685      685
=======================================
  Hits         2738     2738
  Misses        762      762
  Partials       90       90

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 048f9cf...78a9c54. Read the comment docs.


Printable tuple-likes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 99.429%

Totals

Change from base Build<PHONE_NUMBER>1:
0.005%

Covered Lines:
1045

Relevant Lines:
1051

💛  - Coveralls


False-postitive anaysis of the the multi-line PostgreSQL functions

Function definition:
Function(
    "on_update_timestamp",
    """
    BEGIN
        NEW.updated_at = CLOCK_TIMESTAMP();
        RETURN NEW;
    END
    """,
    returns="trigger",
    language="plpgsql",
)

Generated Alembic command:
op.execute("""CREATE FUNCTION on_update_timestamp() RETURNS trigger LANGUAGE plpgsql AS $$
    BEGIN
        NEW.updated_at = CLOCK_TIMESTAMP();
        RETURN NEW;
    END
    $$;""")

The statement is correct and is successfully applied.

But when trying to generate a new migration, the function is incorrectly considered to be modified:
def upgrade() -> None:
    # ### commands auto generated by Alembic - please adjust! ###
    op.execute("""CREATE OR REPLACE FUNCTION on_update_timestamp() RETURNS trigger LANGUAGE plpgsql AS $$
        BEGIN
            NEW.updated_at = CLOCK_TIMESTAMP();
            RETURN NEW;
        END
        $$;""")
    # ### end Alembic commands ###

def downgrade() -> None:
    # ### commands auto generated by Alembic - please adjust! ###
    op.execute("""CREATE OR REPLACE FUNCTION on_update_timestamp() RETURNS trigger LANGUAGE plpgsql AS $$
            BEGIN
                NEW.updated_at = CLOCK_TIMESTAMP();
                RETURN NEW;
            END
            $$;""")
    # ### end Alembic commands ###

As you can see, the only difference is in the number of leading spaces.
This is most probably caused by the indentation of the Alembic code and the way Python handles multi-line strings.

To mitigate that on my side I have a custom function:
def oneliner(multiliner: str) -> str:
    return " ".join(map(str.strip, multiliner.split("\n"))).strip()

that I use to wrap function definitions:
Function(
    "on_update_timestamp",
    oneliner(
        """
        BEGIN
            NEW.updated_at = CLOCK_TIMESTAMP();
            RETURN NEW;
        END
        """
    ),
    returns="trigger",
    language="plpgsql",
)

The resulting Alembic command looks like that:
op.execute("""CREATE FUNCTION on_update_timestamp() RETURNS trigger LANGUAGE plpgsql AS $$BEGIN NEW.updated_at = CLOCK_TIMESTAMP(); RETURN NEW; END$$;""")

As the final function has no new lines and no indentation, trying to generate a new migration does not cause false-positive changes.

The potential fix would be to use the same oneliner() function to pre-process both the Python definition and the returned PostgreSQL definition before comparing them and making a decision on whether the function has to be re-created.

Thanks for the report! The Function/Trigger implementations are under utilized in comparison to some of the other features, so much appreciated.
Fix should be released in v0.6.5

@DanCardin The release seems to work fine.
No false-positive migrations generated. Even if I reformat the multi-line function code to make it look prettier (as long as the relative indentation of the function body is maintained).
But if I change the relative indentation in the function definition, a re-create command is generated as expected.
Thanks a lot!


Please am new here, i want to know more about coding!

please i don't really know how to convert and edit this code below, and please i really want to know what is inside the script

@aoegold How is this related to the JerryScript project?

am sorry @akosthekiss i dont where to post, but i have said it before that am new here

@aoegold I'm not sure what "here" means in this context. Are you new to the JerryScript project, are you new to the JavaScript language, are you new to the GitHub platform, are you new to programming, or ...? If your question is not related to the project, I'd suggest you post it to the appropriate platform (e.g., StackOverflow).

This question is out of the project's scope. Please use the mentioned platforms suggested by @akosthekiss .


fix: Update screen design

Related Issue:
#334
Summary:
Improve reinstall loading screen status message UI
Screenshots/GIFs:
First version

Updated version (backdrop + conditional rendering)

@joao-alberto just want to touch base and see how things are coming on your end. If you wouldn't mind just dropping a comment to let us know you're still interested in working on completing this PR and getting it merged, that would be much appreciated!
If you don't have the availability to finish it up, that's no problem, we'll open it up for community contributions. I'll update the PR if we still haven't heard back from you in a few days.

@melanieseltzer @superhawk610 OK, I've comandeered this PR. I hope that's OK @joao-alberto.
I've addressed the review comments (backdrop & usage during delete). Please let me know what you think.
The conditional rendering based on progress >0 is the easiest way to use the LoadingScreen for reinstalling Deps & deleting project. I think it's OK to first show with-out progress bar and then display it once there is the first update.


Docker?

I'm wondering if running our website as a docker or singularity container is an option. Because our installattion instructions are a bit complicated, and they could be fully automated using docker.
This could be a starting point:
https://dev.to/paschalogu/how-i-deployed-my-website-as-a-container-3fje

I've learnt a bit about docker configuration, but I'm currently experiencing some logic bugs on the searchresultpage, and when I'm done with that will try to build our site on docker!

We can assume a time plan to deploy it on docker :)

auto make all the installation

Check how to give or share the docker container to others


fix(sizeme): turn off placeholders

turning off placeholders allows downstream consumers to use these components in their testcases

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

npm package (@release-1.x dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[TODO] A comman list about what harborctl will support

a scratch about what harborctl will support.

command list:

[x] login
[x] logout
[x] search
[x] project

[x] check
[x] create
[x] delete
[x] get
[x] list
[x] update (https://github.com/moooofly/harborctl/issues/1)
[x] member

[x] create
[x] delete
[x] get
[x] list
[x] update

[x] metadata

[x] create (https://github.com/moooofly/harborctl/issues/3)
[x] delete
[x] get
[x] list
[x] update (https://github.com/moooofly/harborctl/issues/4)

[x] log (https://github.com/moooofly/harborctl/issues/2)

[x] statistics
[x] user

[x] list
[x] create (https://github.com/moooofly/harborctl/issues/7, https://github.com/moooofly/harborctl/issues/9)
[x] current
[x] get
[x] update (https://github.com/moooofly/harborctl/issues/10)
[x] delete
[x] password (https://github.com/moooofly/harborctl/issues/11)
[x] sysadmin

[x] repository

[x] top
[x] get (https://github.com/moooofly/harborctl/issues/13)
[x] delete
[x] update
[x] label

[x] get
[x] add (https://github.com/moooofly/harborctl/issues/20, rely on "/labels" API)
[x] delete

[x] tag

[x] get
[x] delete
[x] list (rely on "/labels" API)
[x] retag (https://github.com/moooofly/harborctl/issues/17)
[x] label

[x] get
[x] add (https://github.com/moooofly/harborctl/issues/21, rely on "/labels" API)
[x] delete

[x] manifest
[x] scan (https://github.com/moooofly/harborctl/issues/18)
[x] vulnerability

[x] signature (https://github.com/moooofly/harborctl/issues/15)
[x] scanall (https://github.com/moooofly/harborctl/issues/16)

[x] log (https://github.com/moooofly/harborctl/issues/6)
[x] scan

[x] log (https://github.com/moooofly/harborctl/issues/29)

[x] replication

[x] list (https://github.com/moooofly/harborctl/issues/28)
[x] update
[x] delete
[x] policy

[x] list
[x] get
[x] create (https://github.com/moooofly/harborctl/issues/30, https://github.com/moooofly/harborctl/issues/31)
[x] update (https://github.com/moooofly/harborctl/issues/33)
[x] delete (https://github.com/moooofly/harborctl/issues/32)

[x] trigger
[x] log

[x] label

[x] list
[x] create (https://github.com/moooofly/harborctl/issues/22)
[x] get
[x] update (https://github.com/moooofly/harborctl/issues/25)
[x] delete
[x] resource

[x] target

[x] list
[x] get
[x] delete
[x] create
[x] update
[x] policy
[x] ping (https://github.com/moooofly/harborctl/issues/34)

[x] internal

[x] syncregistry (https://github.com/moooofly/harborctl/issues/27)

[x] systeminfo

[x] get
[x] volume
[x] getcert

[x] usergroup

[x] list
[x] create
[x] get
[x] update
[x] delete

[x] chartrepo

[x] health
[x] chart

[x] list
[x] upload - 500 error
[x] get
[x] delete (https://github.com/moooofly/harborctl/issues/43)
[x] version

[x] get
[x] delete

[x] label

[x] get (https://github.com/moooofly/harborctl/issues/44)
[x] delete (https://github.com/moooofly/harborctl/issues/45)
[x] attach (https://github.com/moooofly/harborctl/issues/46)

[x] prov

[x] upload - 500 error

[x] library

[x] upload (https://github.com/moooofly/harborctl/issues/47)

Some comments:

Move system gc out of the base release(V1.6) as it's released in V1.7 and create an issue to track that work
Move configuration and email related out of the base release as it's the priority is low, and create an issue to track that work
Move ldap related out of the base release as it can be counted in the configuration part, and create an issue to track that work
Suggest move the complicated commands likestatistic and tag retention policy out of the base release, those features can be supported as plugins of CLI in future. Issues should be created for tracking
Suggest change target to registry
Suggest use replication instead of job: harborctl replication policy * / harborctl replication run * / harborctl replication log * etc.
Suggest use vulnerability instead of job for the scanning-related commands

Suggest use vulnerability instead of job for the scanning-related commands

After discussion with @steven-zou , the suggest above will not be considered right now.

All APIs are support now, hooray @steven-zou


Problems compiling latest example

I'm seeing problems when I try to build the example in the latest update:
! Undefined control sequence.
\DndCRExp code #1->\str_case_e:nnF
                                   {#1}{{0}{#1 (0 \xpname )}{1/10}{0 (10 \xp...
l.121   ]

…and several:
! Undefined control sequence.
\DndMonsterSpellLevel code ...par}\str_case_e:nnF
                                                  {#1}{{1}{\spellfirstleveln...
l.135 ...e ward, fire bolt, light, shocking grasp}

It looks like it's having a problem with \str_case_e:nnF, but to my eye that usage is correct, and the function was renamed from str_case:ee(TF) to str_case_e:nn(TF) back in 2015. I've updated everything I can find that's relevant (xstring, l3*) and I'm still seeing a problem. Right now I'm running an 'update all' across my entire MacTeX distribution to see if that turns up the issue.
Any suggestions or recommendations would be much appreciated.

Hi, i've loaded the example file in Overleafe after I couldn't compile it without error on my laptop. And I get the same error in both cases.
<argument> \str_if_in:NnTF {fog cloud, rope trick}{,}{\__dnd_caption:nn {\nu... l.129 ...nnateSpellLevel[3]{fog cloud, rope trick}
I've found the issue in dndmonster.sty.
\NewDocumentCommand {\DndInnateSpellLevel} { O{\innateatwillname} m}
  {
    \smallskip
    \begin{hangingpar}
      \IfInteger{#1}
      {
        \str_if_in:NnTF {#2} {,}
        { \__dnd_caption:nn { \numberperdayeachname } { #1 } }
        { \__dnd_caption:nn { \numberperdayname     } { #1 } }
      }
      {#1}
      :~\DndEmphSpellString{#2}
    \end{hangingpar}
  }```

But I'm overwhelmed with Latex3 and can not get it compiling. The output doesn't look wright either.
![screenshot at 2019-02-19 17-57-54](https://user-images.githubusercontent.com/40068804/53032984-4c253880-3470-11e9-9abe-bdb2346836bb.png)

Hi @Doibur,
Please open a new issue with the problem along with a MWE*, and I will take a look at it.
*MWE: Minimum working example. A bare-bones file that only contains the essentials to demonstrate the problem. In this case, you could probably strip out everything between \begin{document} and \end{document} in example.tex, put in your call to \DndInnateSpellLevel that is breaking, and if it still breaks, post that in a code block.


Unicode

Thanks for putting this together.
Do you think that Unicode/UTF8/UTF16 etc deserves a section?

Well, I think that work with Unicode in JavaScript are a nice concept to know but I don't think that are really necessary right now. Maybe add some links in the future could be good.

Ok, thanks.


can not transfer success

I build a simple transfer like transfer_test.go but i can not success.
The example put 5 transaction into the bundle but it has only one output like this "https://thetangle.org/bundle/YXCQVBAUX9ISLJPQWEFGHCKKZFBHAPCFAFHOIVVWVAGFFHJPSNSVHFOAKNUYDC9BSSLGPRAHTLKHUVVXZ".
I get nothing when I findTransaction by bundle. its ok when i use java-lib or js-lib with the same node.
this is my code, please help me.  i change many seed which have iota but i can not success.
package main

import (
	"fmt"
	"net/http"
	"time"

	"github.com/iotaledger/giota"
)

func main() {
	trytesFrom := "BBHCNPZOZNIFOXQZ9AAAAAAA99XUVPMYQEYERUVWBZXUBWWBPTJXVYUSHWFNJROGZPZUUJQQXAYGDI99A"
	seed, err := giota.ToTrytes(trytesFrom)
	if err != nil {
		fmt.Printf("err: %v\n", err)
		return
	}

	//api
	httpClient := &http.Client{
		Timeout: 600 * time.Second,
	}
	//api := giota.NewAPI("http://ioTaUser:HqCUpHfVGxyBD5PRaiibseMQ1qmGXRMcxsvH9d@<IP_ADDRESS>:14625", httpClient)
	api := giota.NewAPI("http://<IP_ADDRESS>:14600", httpClient)

	//send transaction
	trs := []giota.Transfer{
		giota.Transfer{
			Address: "LWADKFFFRNLGLQVILXUTIZIZVNNAJRWOIAHGLDAGGEFTIUGKBYSHPQDNMAIAFJZ9XQUSCEKGZYEQ9CTLC",
			Value:   10,
			Tag:     "TAGTEST",
			Message: "MSGTEST",
		},
	}
	bundle, err := giota.Send(api, seed, 3, trs, 14, nil)
	if err != nil {
		fmt.Printf("send err: %v\n", err)
		return
	}

	//print bundle result
	fmt.Printf("bundle: %s\n", bundle.Hash())
	for _, tx := range bundle {
		PrintTx(&tx)
	}
	fmt.Printf("send success")
}

func PrintTx(tx *giota.Transaction) {
	fmt.Printf("\nHash: %s\n", tx.Hash())
	fmt.Printf("SignatureMessageFragment: %s\n", tx.SignatureMessageFragment)
	fmt.Printf("Address: %s\n", tx.Address)
	fmt.Printf("Value: %d\n", tx.Value)
	fmt.Printf("Timestamp: %v\n", tx.Timestamp)
	fmt.Printf("CurrentIndex: %d\n", tx.CurrentIndex)
	fmt.Printf("LastIndex: %d\n", tx.LastIndex)
	fmt.Printf("Bundle: %s\n", tx.Bundle)
	fmt.Printf("TrunkTransaction: %s\n", tx.TrunkTransaction)
	fmt.Printf("BranchTransaction: %s\n", tx.BranchTransaction)
	fmt.Printf("Tag: %s\n", tx.Tag)
	fmt.Printf(":AttachmentTimestamp %s\n", tx.AttachmentTimestamp)
	fmt.Printf(":AttachmentTimestampLowerBound  %s\n", tx.AttachmentTimestampLowerBound)
	fmt.Printf(":AttachmentTimestampUpperBound %s\n", tx.AttachmentTimestampUpperBound)
	fmt.Printf(":Nonce: %s\n", tx.Nonce)
}

I have the same issue.

Please have a look at the next branch and the example in the readme for value transfer.


Fix type of useLoader first param

Examples and a constructor call in useLoader body suggest that useLoader accepts a Loader class, not an instance.
// one of the examples
useLoader(GLTFLoader, url, loader => {
  const dracoLoader = new DRACOLoader()
  dracoLoader.setDecoderPath('/draco-gltf/')
  loader.setDRACOLoader(dracoLoader)
})

Initially, I wanted to go with new () => THREE.Loader, but THREE.Loader doesn't have a load method (lol).
DRACOLoader, GLTFLoader and TextureLoader have similar load methods, so I have added a generic type that fits all of them and may provide some inference 👇

TLDR:

oohhh, that's super nice. i didn't know about interface, this could be perfect for cameras and renderers as well.


Error 401 from tydom mediation

Hello,
I am new user of tydom 1.0.
I use your app with docker but i have a problem.
The connexion with MQTT is OK but just after, when it tries to connect to the tydom 1.0 i have an 401 error.
I am sure of the password cause i just entered it on the tydom.
I can"t connect with a browser, user = mac address and password : tydom password.
Is it an update?
Thanks

Hi,
Have you read this part of the documentation?
The password needed here is not the same as the password you're using on the Tydom app.
It' already been discussed here, here, here, here, here and here 😀
You likely need to install an old Tydom app version to be able to set/reset the tydom hardware appliance password.

ah d'accord,
j'essaie cet aprés midi et je vous redis quoi.
Merci pour la réponse

tout fonctionne,
Merci beaucoup


feature: add Melodic Minor option + jam tracks for all keys

Summary

adds melodicMinor option to the Mode enum
adds melodicMinor pattern to the ModePatterns constant
adds  jam tracks for Melodic Minor in all keys

Please close in favor of #107.


Auto indentation broken when return keyword involved

From @jarshwah on July 17, 2017 2:56
Environment data
VS Code version:  1.14.0
Python Extension version:  0.6.7
Python Version:   2.7.13
OS and version:    OSX 10.12.5 (16F73)
Actual behavior
Auto indentation of function arguments fails when the function is preceded by the return keyword. The closing paren is put on the first column along with the cursor. Removing the return keyword fixes the issue.
# | represents cursor

def failing():
    return arg(|)  # hit enter

def failing():
    return arg(
|)

def works():
    arg(|)  # hit enter

def works():
    arg(
        |
    )

Expected  behavior
def failing():
    return arg(|)  # hit enter

def failing():
    return arg(
        |
    )

Steps to reproduce:
See expected and actual behaviour above
Settings
Your settings.json:
// Place your settings in this file to overwrite the default settings
{
  "extensions.autoUpdate": true,
  "editor.autoIndent": true,
  "editor.fontSize": 13,
  "editor.fontFamily": "Source Code Pro",
  "editor.minimap.enabled": false,
  "editor.wordWrap": "off",
  "editor.rulers": [
  79, 99, 119
],
"editor.renderIndentGuides": true,
"editor.renderLineHighlight": "all",
"editor.dragAndDrop": false,
"emmet.useNewEmmet": true,
  "files.insertFinalNewline": true,
  "python.pythonPath": "python3",
  "python.formatting.provider": "yapf",
  "python.formatting.autopep8Args": ["--max-line-length=119"],
  "python.linting.pylintEnabled": false,
  "python.linting.flake8Args": ["--max-line-length=119"],
  "python.linting.enabled": true,
  "python.linting.pep8Enabled": false,
  "python.linting.flake8Enabled": true,
  "python.workspaceSymbols.exclusionPatterns": [
    "**/site-packages/**",
    ".tox/**"
  ],
  "workbench.editor.showTabs": true,
  "editor.renderWhitespace": "all",
  "files.trimTrailingWhitespace": true,
  "window.zoomLevel": 0,
  "vsicons.projectDetection.autoReload": true,
  "workbench.colorTheme": "Atom One Dark",
  "workbench.iconTheme": "vscode-icons",
  "workbench.editor.enablePreview": true,
  "workbench.editor.revealIfOpen": true,
  "sync.host": "",
  "sync.pathPrefix": "",
  "typescript.tsserver.log": "verbose",
  "search.useRipgrep": false // todo: remove once global search fixed
}

Logs
Output from Python output panel
No Relevant Logs

Output from Console window (Help->Developer Tools menu)
No Relevant Logs

I see the same behaviour by switching the "editor.autoIndent": true, to false. Only began happening with 1.14.0 from memory.
Copied from original issue: DonJayamanne/pythonVSCode#1087

From @jarshwah on July 17, 2017 4:53
@DonJayamanne hopefully this short screencast will demonstrate the issue more clearly. I don't think my bug report got the issue across properly.
https://drive.google.com/file/d/0B5cRNkuMQpuYSDl6b1d1VWFiYjA/view?usp=sharing
You'll see that auto indentation works correctly when the return keyword isn't preceding the function call. I'm fairly sure this worked correctly until version 1.14.0 of VScode.

Auto indentation for arguments (with braces), is not supported

From @jarshwah on July 19, 2017 1:16
@DonJayamanne did you get a chance to look at the linked video showing the problem? I believe the issue is supported, but happy to hear otherwise once you've seen the issue demonstrated.

Will look into this

I'm sorry for not getting back to you any sooner. I can confirm this is a bug in the extension.


Font Request: Manjaro Linux Logo.

Manjaro is quickly becoming a popular Linux distribution that builds on the power of Arch. Would you please add the Manjaro logo to the font?
https://github.com/manjaro/artwork-logo
Thanks in advance!

Added in v0.8.


Update Error

When i am trying to update Quartz v4.0.10  to recent version , it does not update and i am getting this.
Quartz v4.0.10

Backing up your content
Pulling updates... you may need to resolve some `git` conflicts if you've made changes to components or plugins.
From https://github.com/jackyzha0/quartz
 * branch              v4         -> FETCH_HEAD
fatal: refusing to merge unrelated histories
Ensuring dependencies are up to date

up to date, audited 460 packages in 3s

160 packages are looking for funding
  run `npm fund` for details

1 moderate severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
Done!

I dont know what to do with Pulling updates... you may need to resolve some `git` conflicts if you've made changes to components or plugins.

the problem is with fatal: refusing to merge unrelated histories, did do anything weird in git?

I did not do anything git.

did you clone/fork from this quartz repository? it wont work unless you do that
i can't find your Quartz repository in your public repos

Yep I cloned it from my private repository using GitHub desktop.

can you do git log and post the output here?

Closing due to inactivity, please redirect troubleshooting to discord


3.0.7 - Mismatched anonymous define() with r.js compilation

Using pixi (3.0.7) with r.js (2.1.20) produces the following error when running from compiled source ::

<= 3.0.6 works fine.

Hmm, not sure what could be causing this. We bumped our browserify version, maybe that is causing it?
https://github.com/pixijs/pixi.js/commit/3dcc484df13930527a455329708c200d4e7b1644
We've updated again since then, do you still get the error if you build the latest dev branch manually?

Indeed, I pulled down dev and cleaned out the node_modules before rebuilding and still get exactly the same issue :( Struggling to find the exact issue here...

Does just downgrading the browserify version to what it was in 3.0.6 solve the problem?

Yo! I have had this issue for quite a while - it comes from  a 'define' definition that happens in the async class that gets used. Removing the line fixes the issue. It would be good to figure out a way to fix this properly though.

Haven't checked the code but it can sometimes be fixed simply by naming the define function.
e.g.
define("foo/title",
["my/cart", "my/inventory"],
function(cart, inventory) {
//Define foo/title object in here.
}
);
http://requirejs.org/docs/errors.html#mismatch
and
http://requirejs.org/docs/api.html#modulename
Cheers

this has now been addressed in the latest dev branch 👍

Still seeing this issue with the latest dev branch, any chance of an update? :)


Merge with xnemogcm?

Hi,
before hearing of xorca I developed my own package to open NEMO files and make them compatible with xgcm, xnemogcm. I feel that it is not much usefull to develop twice the same tool. I propose that you maybe have a look at my package and see if you would be interested that I try to merge some properties. The doc is not written, but every function should have a proper docstring.
The mentality is quite different, with no hardcoding of the variables position, instead the name of the file is used to set the proper position (e.g. grid_T files for T points, etc).
I opened this issue to open the discussion, of course 1) no hurry to discuss this proposition and 2) maybe nothing appropriated for the development of xorca has been written in xnemogcm.
Best,
Romain

I'd be very interested in a joint effort!
The next two weeks are quite busy for me. But let's try and get together some time in March and discuss this?

Perfect, you can just send me an email when you have more time. My address is in my github profile.


joystickd does not run in openpilot docker

Describe the bug
Attempting to start joystickd in the openpilot docker results in the following error message:
root@fd93966ced36:/home/batman/openpilot# export ZMQ=1
root@fd93966ced36:/home/batman/openpilot# tools/joystick/joystickd.py

Using joystick, make sure to run bridge on your device if running over the network!
python: cereal/messaging/impl_zmq.cc:22: int get_port(std::string): Assertion `port >= 0' failed.
Aborted (core dumped)

How to reproduce or log data

Checkout master branch (commit b13f5e632814c6ebb159a325331fd74da3a68066) and pull submodules.
Build docker container using Dockerfile.openpilot:

# symlink Dockerfile -> Dockerfile.openpilot
ln -s Dockerfile.openpilot Dockerfile
docker build -t openpilot .

Start the docker container

docker run -it openpilot bash

Follow instructions on tools/joystick/README.md:

# in the docker container
export ZMQ=1
tools/joystick/joystickd.py

Additional context

Operating system: Arch 5.12.14. Docker version 20.10.7, build f0df35096d

This should be fixed by https://github.com/commaai/cereal/commit/9327e4fbec1a1b4e0658a18db4a6f332c1f53688. Let me know if you still have issues.


Sync reverse-string

#740
also added missing test cases

@mk-mxp
Need help
I have added 3 new test cases with the below string and it failed.
子猫
Würstchenstand
ผู้เขียนโปรแกรม

I even tried to update the example code with grapheme_extract and mb_substr but still no success tests.

@fejan92 I'm too busy today. Thanks for your patience!

Yeah, no problem.
There is no rush at all.


Bridge: Add checkbox to set the sendStarted flag

User Story
As a user, I would like my integration via WebHook to return the *.started event.
Technical Details
The Bridge should provide a checkbox to allow to configure this behavior for the WebHook integration.
The status of the checkbox should be saved in the webhook configuration, which looks like the following:
apiVersion: webhookconfig.keptn.sh/v1alpha1
kind: WebhookConfig
metadata:
  name: webhook-configuration
spec:
  webhooks:
    - type: sh.keptn.event.deployment.triggered
      subscriptionid: my-sub-id
      sendFinished: false
      sendStarted: false         # <- new field
      envFrom:
        - name: "secretKey"
          secretRef:
            name: "slack-secret"
            key: "endpoint"
      requests:
        - "curl -X POST -H 'Content-type: application/json' --data '{\"text\":\"Test triggered in {{.data.stage}}\"}' https://hooks.slack.com/services/{{.env.secretKey}}"

The flag has the following behavior:

If sendStarted is true, the WebHook-service will send the started event (default)
If sendStarted is false, the WebHook-service will not send the started event

This should be documented on hover. Mind to explain that if unchecked, the integration must provide the respective started event.
DoD

[ ] UI Test
[ ] Feature implemented
[ ] On hover, present a small description of the feature

Dependencies

[ ] TBD backend implementation

I feel this feature is important and upvote its priority.


Colour of "Rebuild Packages"-button

Description
Sometimes a packages needs to be rebuilt and Atom opens a tab listing all such packages. The button to let Atom rebuilt all these packages is hardly visible (see first screenshot). It looks fine though when hovered (see second screenshot).

Steps to Reproduce

You need a package in need of recompiling.
Click on the red bug in the status panel at the bottom.
A new tab opens displaying the dialog seen in the screenshot.

Expected behavior:
Let the background stand out to some degree or change the font colour to make it more visible.
Actual behavior:
There is hardly any contrast between the background and the colour of the font when not hovered.
Reproduces how often:
Every time.
Versions
❯ atom-beta --version
Atom    : 1.52.0-beta0
Electron: 6.1.12
Chrome  : 76.0.3809.146
Node    : 12.4.0

@delta-one I haven't really used Atom for a couple years other than for looking at bugs in these themes. If you open PRs in here, I'm highly likely to approve.
This issue may actually be in clear-night-ui

Ok, will investigate and open a PR if I can fix it.


Simplify Concatenation (and subsequent bug)

Describe the bug
The model wasn't being simplified as no simplification was implemented for a NumpyConcatenation, when this is added there is a dimension error with matrices being multiplied. It seems that the original tree in the model was
Matrix (9,8) * (vector (8,) * Matrix(8,9)  ---> Matrix(9,8) * Matrix(8,9) ---> Matrix(9,9)

but this gets changed to
(Matrix (9,8) * vector (8,)) * Matrix(8,9)  ---> Vector(9,) * Matrix(8,9) ---> Error

To Reproduce
Steps to reproduce the behaviour:

Go to branch issue-253-simplify-bug
Run python3 -m tests.test_models.test_lead_acid.test_lead_acid_newman_tiedemann
ipdb starts in MatrixMultiplication.evaluate(), type self.children[0].evaluate(t,y).shape (returns (9,)), self.children[0].evaluate(t,y).shape (returns (8,9))

@tinosulzer, do you mean the original tree was
Matrix (9,8)   ( vector (8,) @ Matrix(8,9) )

But vector (8,) @ Matrix(8,9) gives vector(9,)?

Sorry that wasn't clear, there is a mix of matrix multiplications and elementwise multiplications:
original:
Matrix (9,8) @ (vector (8,) * Matrix(8,9))  ---> Matrix(9,8) @ Matrix(8,9) ---> Matrix(9,9)

after simplification:
(Matrix (9,8) @ vector (8,)) * Matrix(8,9)  ---> Vector(9,) * Matrix(8,9) ---> Error

but vector (8,) is a row vector, so  vector (8,) * Matrix(8,9)  shouldn't work? should be vector (8,1)?
In [1]: import numpy as np

In [2]: v = np.ones(8)

In [3]: m = np.ones((8,9))

In [4]: v*m
---------------------------------------------------------------------------
ValueError    Traceback (most recent call last) <ipython-input-4-c1d8335750dc> in <module>
----> 1 v*m

ValueError: operands could not be broadcast together with shapes (8,) (8,9)

so if you were to expand out the brackets in m2@(v*m), what would you get mathematically? I'm not sure..

It looks like the * operator does matrix multiplication by default for scipy matrices, so we should use A.multiply(B) instead:
In [13]: sparse.coo.coo_matrix((8,9))*sparse.coo.coo_matrix((8,9))
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-13-c73b5d00c9d5> in <module>()
----> 1 sparse.coo.coo_matrix((8,9))*sparse.coo.coo_matrix((8,9))

~/.local/lib/python3.6/site-packages/scipy/sparse/base.py in __mul__(self, other)
    476         if issparse(other):
    477             if self.shape[1] != other.shape[0]:
--> 478                 raise ValueError('dimension mismatch')
    479             return self._mul_sparse_matrix(other)
    480

ValueError: dimension mismatch

In [14]: sparse.coo.coo_matrix((8,9))*sparse.coo.coo_matrix((9,8))
Out[14]:
<8x8 sparse matrix of type '<class 'numpy.float64'>'
	with 0 stored elements in Compressed Sparse Row format>

In [15]: sparse.coo.coo_matrix((8,9))@sparse.coo.coo_matrix((9,8))
Out[15]:
<8x8 sparse matrix of type '<class 'numpy.float64'>'
	with 0 stored elements in Compressed Sparse Row format>

In [16]: sparse.coo.coo_matrix((8,9))@sparse.coo.coo_matrix((8,9))
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-16-ce8641f5818e> in <module>()
----> 1 sparse.coo.coo_matrix((8,9))@sparse.coo.coo_matrix((8,9))

~/.local/lib/python3.6/site-packages/scipy/sparse/base.py in __matmul__(self, other)
    557             raise ValueError("Scalar operands are not allowed, "
    558                              "use '*' instead")
--> 559         return self.__mul__(other)
    560
    561     def __rmatmul__(self, other):

~/.local/lib/python3.6/site-packages/scipy/sparse/base.py in __mul__(self, other)
    476         if issparse(other):
    477             if self.shape[1] != other.shape[0]:
--> 478                 raise ValueError('dimension mismatch')
    479             return self._mul_sparse_matrix(other)
    480

ValueError: dimension mismatch

In [17]: sparse.coo.coo_matrix((8,9)).multiply(sparse.coo.coo_matrix((8,9)))
Out[17]:
<8x9 sparse matrix of type '<class 'numpy.float64'>'
	with 0 stored elements in Compressed Sparse Row format>

ok. But this doesn't relate to this bug? probably better to open that as a separate issue

so if you were to expand out the brackets in m2@(v*m), what would you get mathematically? I'm not sure..

It looks like this isn't possible in general

ok. But this doesn't relate to this bug? probably better to open that as a separate issue

Ok will open separate issue and hope nothing breaks ...  We might be ok because the original case should actually be
div(D(c)*grad(c))
---> Matrix (9,8) @ (vector (8,) * (Matrix(8,9) @ vector(9,)))
---> Matrix (9,8) @ (vector (8,) * vector(8,))
---> Matrix(9,8) @ vector(8,)
---> vector(9,)

I've fixed the bug so that m2@(v*m).simplify() will not try to expand the brackets around the *, but still getting dimension errors for the model tests. I've had a look at the model equations, but they are too long to see what the problem is. How did you manage to find the problem earlier @tinosulzer, any tips?

Try putting a try-except block around the operation that is giving a dimension error, then you can have a look at what the children evaluate to and why it's giving an error

ok, think I might have figured out the problem, when I fixed the issue you described above with the sparse multiplication the error message became much more meaningful. The statevector is being put in during the solve as a row vector, rather than a column vector, so at some point there is something like:
vector(99,) * sparse_matrix(99,100)
this was getting treated like a matrix multiplication, which is fine, but then I fixed it so that it was treated as a broadcasting scalar multiply, it started complaining the dimensions didn't agree, which is also right, it should be
vector(99,1) * sparse_matrix(99,100)
Does that sound right?

That sounds right but even with the sparse multiplication fixed there are no errors like this on the non-simplified model, and I am guessing that this is because there are never any vector-matrix multiplications, only matrix-vector (e.g. grad(c) or div(grad(c)) or vector-vector (e.g. c*grad(c))

I think the problem is that there are things like:
vector(99,) * ( sparse_matrix(99,100) @ statevector(99,) )

if you just evaluate that, you do the inner matrix-vector multiply which gives you a vector, then multiply that by the outer vector. All good. But if you try to simplify by doing the vector(99,) * sparse_matrix(99,100) to give you a sparse_matrix(99,100),  then you run into problems
I've pushed a hacky fix to pybamm.Multiplication which takes into account 1d numpy vectors, and a few other misc fixes that arose after that one. All the tests pass now, which is good. Is the original bug you found in this issue fixed?

Have added (but not tested) simplification of DomainConcatenation, which required removing the line in symbol.simplify that removed domain (DomainConcatenation needs to know the domains).
Good news is it runs and simplifies the tree, bad news is we don't get much speed gain :confounded:
In dae_solver.py:
In [2]: %timeit concatenated_rhs.evaluate(0,y0)
1.72 ms ± 14.4 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [3]: %timeit model.concatenated_rhs.evaluate(0,y0)
1.93 ms ± 85.9 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

It could be the reshapes in Multiplication slowing things down in the simplified tree (more reshapes needing to happen there than in the original tree)

that is a shame :( I've been doing the simplify for domain concatentation as well, without the domain information, this should pass all the tests now.


Request: additional autohide on title

Hi,
in advance - sorry for abusing the issue-tracker for a feature request.
An additional autohide for the footer/title would be really great.
Sometime there are elements in the picture which are been covered of the footer-bar/title.
Thx :)
Regards.

That's a good suggestion. I will add this to the list of feature requests.

This is now supported by the new version 0.7.3, just set the option autohide to the value "all" instead of true/false. Great suggestion, thanks.


Publish JSON schema for meltano.yml on schemastore.org

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2211
Originally created by @DouweM on 2020-07-31 17:48:41

This will add validation and autocompletion functionality to various editors: https://www.schemastore.org/json/#editors, https://json-schema-everywhere.github.io/yaml
To do:

[x] Create schema: https://gitlab.com/meltano/meltano/-/merge_requests/1804
[ ] Publish on SchemaStore.org https://github.com/SchemaStore/schemastore/blob/master/CONTRIBUTING.md#adding-to-catalog

[x] Created PR using new Meltano fork (https://github.com/Meltano/schemastore): https://github.com/SchemaStore/schemastore/pull/2020
[x] PR review and approval

View 29 previous comments from the original issue on GitLab


Running create_test fails with v1.9.0

If I have the latest e3sm_unified environment loaded on perlmutter, I get failures running create_test that I don't get when I do not have that environment loaded.  Is this expected from how e3sm_unified was put together?
I am using 2236937c71ab0c4ef67c2574e58e01a0e46714d8 hash for the E3SM code and am running
./create_test SMS_Ln5.ne4pg2_oQU480.F2010 from cime/scripts/
If I have not loaded e3sm_unified, everything passes.
If I load e3sm_unified v1.9.0, I get the following
Using project from config_machines.xml: e3sm
create_test will do up to 1 tasks simultaneously
create_test will use up to 320 cores simultaneously
Creating test directory /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz
RUNNING TESTS:
  SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel
Starting CREATE_NEWCASE for test SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel with 1 procs
Finished CREATE_NEWCASE for test SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel in 1.424639 seconds (PASS)
Starting XML for test SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel with 1 procs
copying /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz/env_run.xml -> /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz/LockedFiles/env_run.orig.xml
Finished XML for test SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel in 0.518013 seconds (PASS)
Starting SETUP for test SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel with 1 procs
Finished SETUP for test SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel in 7.509040 seconds (FAIL). [COMPLETED 1 of 1]
    Case dir: /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz
    Errors were:
        ERROR: Command: '/pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/components/elm/bld/build-namelist -infile /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz/Buildconf/elmconf/namelist  -csmdata /global/cfs/cdirs/e3sm/inputdata -inputdata /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz/Buildconf/elm.input_data_list -ignore_ic_year -namelist " &elm_inparm  start_ymd=00010101  /" -use_case 2010_CMIP6_control  -res ne4np4.pg2  -clm_start_type default -envxml_dir /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz -l_ncpl 24 -r_ncpl 6 -lnd_frac /global/cfs/cdirs/e3sm/inputdata/share/domains/domain.lnd.ne4pg2_oQU480.200527.nc -glc_nec 0 -co2_ppmv 388.717 -co2_type diagnostic  -ncpl_base_period day  -config /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz/Buildconf/elmconf/config_cache.xml -bgc sp -mask oQU480' failed with error 'Can't locate XML/LibXML.pm in @INC (you may need to install the XML::LibXML module) (@INC contains: /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/components/elm/bld /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/components/elm/bld /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/cime/utils/perl5lib /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/cime/utils/perl5lib/Config/ /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/components/elm/bld /global/cfs/cdirs/e3sm/perl/lib/perl5-only-switch/x86_64-linux-thread-multi /global/cfs/cdirs/e3sm/perl/lib/perl5-only-switch /global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.9.0_login/lib/perl5/5.32/site_perl /global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.9.0_login/lib/perl5/site_perl /global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.9.0_login/lib/perl5/5.32/vendor_perl /global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.9.0_login/lib/perl5/vendor_perl /global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.9.0_login/lib/perl5/5.32/core_perl /global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.9.0_login/lib/perl5/core_perl .) at /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/cime/utils/perl5lib/Config/SetupTools.pm line 5.
        BEGIN failed--compilation aborted at /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/cime/utils/perl5lib/Config/SetupTools.pm line 5.
        Compilation failed in require at /pscratch/sd/b/beharrop/temp/e3sm_code/20231016/E3SM/components/elm/bld/ELMBuildNamelist.pm line 440.' from dir '/pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz/Buildconf/elmconf'

Waiting for tests to finish
FAIL SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel (phase SETUP)
    Case dir: /pscratch/sd/b/beharrop/e3sm_scratch/pm-cpu/SMS_Ln5.ne4pg2_oQU480.F2010.pm-cpu_intel.20231016_140619_w61kkz
Due to presence of batch system, create_test will exit before tests are complete.
To force create_test to wait for full completion, use --wait
test-scheduler took 10.824334383010864 seconds

Just for fun, I checked if I could run this with e3sm_unified v1.8.1, and everything passes again.  Was this an expected change going from v1.8.1 to v1.9.0?
Also, for my own best practice cheat sheet, should we not have the unified environment loaded to setup or build the model?

@beharrop, my recommendation would be not to try to do anything with E3SM itself using E3SM-Unified.  E3SM-Unified is meant for pre- and post-processing of E3SM output, not for interacting with CIME.  I suggest using the simpler system python environment you get on Perlmutter by doing module load python.

I believe the specific issue is that the version of perl in E3SM-Unified is not compatible with CIME, but that's just a hunch.

Also, for my own best practice cheat sheet, should we not have the unified environment loaded to setup or build the model?

Yes, that's exactly right.

Just for fun, I checked if I could run this with e3sm_unified v1.8.1, and everything passes again. Was this an expected change going from v1.8.1 to v1.9.0?

Not exactly an expected change but it doesn't seem surprising that there would be differences -- a lot of packages are involved in E3SM-Unified (~1000) and a lot of them change between versions.  It seems like perl might have been one of them.

Thanks @xylar .  I'll go ahead and just stick with the default python module moving forward.


Week number

Hi!
I've seen that it is not possible to get the week number. So I wondering if its possible to get something like Oct week 41 :)
Thanks!

Hi.
Sorry, I don't get it. Can u explain?

Hi,
Oh sorry it's my bad, I want to know how to get the week number and show like this "October 12 - 18  (week 42)"... I don't know if I'm clair, you can check this exemple : http://www.calendar-365.com/week-number.html

U mean week of year for some date ?

yeah exactly ^^

Well you can use NSDateComponents to get the week of year of NSDate.
Or you can
#import "NSDate+FSExtension.h"

and
NSInteger weekOfYear =  date.fs_weekOfYear;

This is what fs_weekOfYear doing internally:
- (NSInteger)fs_weekOfYear
{
    NSCalendar *calendar = [NSCalendar fs_sharedCalendar];
    NSDateComponents *component = [calendar components:NSCalendarUnitWeekOfYear fromDate:self];
    return component.weekOfYear;
}

Oh thanks but how can I use with headerDateFormat ?

U mean the header shows the week of year of the first day of the month?

Yes like this : http://f.cl.ly/items/240q0Q322C1d3t0U1H3N/IMG_0072.PNG

Does this help?

Oh yeah :+1:
Thanks dude !

U r welcome.

Hey @WenchaoD, can we make it show the selected date by default?

Is there a way I can the header date format and store it in a text to show anywhere on the calendar

Hi @WenchaoD ,
I want to show week number against each row of month. How can i show the week number?
Like this (https://user-images.githubusercontent.com/61501065/82529342-71639380-9b58-11ea-99b8-93f63c927726.png)
Thanks in advance!!

Hi @WenchaoD Please let me know this is possible or not.


user story

Please get rid of questions on user story

I have done this. Please see the updated version.


Generator for individual fields

Currently, the generator allows specifying CRUD methods for all types globally.
It will be better to support CRUD methods per each type.

@model directove canbe used here


[Feature Request] List of Planned Features

Not really an issue, but this seems to be the easiest way to communicate with you.
I think there are many devs (including me) that would like to contribute, but there isn't a clear vision or path.  What are some features or annoyances that you'd like to be addressed?  I'd like to get some experience under my belt while contributing to this project

Great! Help is helpful. Here are a few things that I'd like done, I'll update that list as I think of more things (and as they're completed).
And feel free to join us on Discord if you haven't already.


🛠 [TASK] : Upload test coverage for Dart code to codecov

Description

[ ] In #373 flutter packages started to generate coverage reports, upload them to codecov once the company account is configured.

Notes

Inspect test-report script in melos.yaml to learn about the coverage generation.

@minikin Here is the task for codecov, will you be working on the the codecov replacement tool?

@dtscalac,feel free to pick it up. However, instead of codecov we will be using https://coveralls.io/. L


Make Calendar functional

Load the slots from the server
Make the slots interactable
Think about overflow in a day
Switch between month view, week view and day view

Fixed with 4a536bbde86f90a6f4e9e93a4404cf369e0ba264


Google node driver cluster creation option available

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
On rancher server --> Add cluster --> Google node driver cluster option is available

Expected Result:
This should NOT be available
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head commit id: cf376738e4
Installation option (single install/HA): single

Moving this to 2.5.8, as it appears there. We will forwardport to both branches.

Google button disappeared from all fresh rancher installs.
I tried to reproduce on 2.5.5, 2.5.7, 2.5-head, master-head, Google infrastructure provider is not available anywhere.
Button is visible only on rancher UI that was created yesterday.


How to restart the countdown clock when it stops

Hi
I would like the countdown timer to restart when the timer stops, executes code in the stop callback and then restarts the timer.

Old thread, but in the new version of the library this would be done like so:
const clock = new FlipClock(el, 0);
// Do something...
clock.stop(() => clock.reset())


Revert "improvements to fanout"

Reverts apache/beam#5768
Breaks post-commit tests: https://builds.apache.org/view/A-D/view/Beam/job/beam_PostCommit_Python_Verify/5447/
estimate_pi.py (which uses CombineGlobally is failing)
cc: @katsiapis
R: @pabloem

Run Python PostCommit


⚠ GitLab Server has degraded performance

In a70a692, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11747 ms

Resolved: GitLab Server performance has improved in c4b7e5d.


Missing "approval_prompt" in authorization_uri

I wrote a Rails app synching with Google Calendar. I'm currently trying to obtain new refresh_tokens from the API as a bug prevented me from saving them in the first place.
I am using approval_prompt: force (or prompt: consent I have tried both), the code is:
google_client = Signet::OAuth2::Client.new({
     client_id: ENV.fetch('GOOGLE_CLIENT_ID'),
     client_secret: ENV.fetch('GOOGLE_CLIENT_SECRET'),
     authorization_uri: 'https://accounts.google.com/o/oauth2/auth',
     scope: Google::Apis::CalendarV3::AUTH_CALENDAR_READONLY,
     redirect_uri: 'http://localhost:8000/google_calendar',
     access_type: "offline",
     approval_prompt: "force"
  })

URI = google_client.authorization_uri.to_s

The URI does not contain the approval_prompt that I would expect (and when I add it manually, I do get prompted for consent). Am I missing something?

Sorry for the delayed response. I'm having difficulty reproducing. Is this still giving you issues?


Fix handling of "empty" types

There are a number of these that are due to conversion from Swagger where all of the fields of a type are read-only:
For example:

https://schema.management.azure.com/schemas/2019-03-01/Microsoft.Compute.Galleries.json

GalleryProperties.Identifier

https://schema.management.azure.com/schemas/2019-07-01/Microsoft.Compute.json

VirtualMachineIdentity.UserAssignedIdentities
Both of the above are types that are entirely readonly

This causes at least a few errors when controller-gen runs that come out looking like this:
/home/matthchr/work/github/k8s-infra/hack/generator/apis/microsoft.compute.galleries/v20180601/galleries_types.go:75:15: unsupported AST kind *ast.InterfaceType

@porges suggests that we could possibly limit our interpretation of what constitutes an allowable generic object to ones that are used with a field of tags or something (@matthchr note: I would've thought tags would just be a map[string]string though)

GalleryIdentifier doesn’t even have a type so that is something we can’t generate properly (I assume it is meant to be string).

It's a complex type with a single read-only property according to Swagger.
It looks like the JSON schema code generator just makes it out to be a really weird object because it's all readonly.

This isn't exactly fixed by #203 but is side-stepped a little - we exclude all of the packages that generate interface{}. That lets us generate and controller-gen the other packages into something that builds successfully.

This was un-fixed with the introduction of support for map[string]v1.JSON types. Unfortunately I am not sure how to differentiate between "this type is empty because all of its properties are readonly" and "this type is empty because we accept anything"
We may need the Swagger data.


Fix to #12249 - Ordering by a boolean column twice after an outer join results in invalid SQL

Problem was that our expression comparison mechanism wasn't doing good job comparing extension nodes. Since the ExpressionEqualityComparer resides in Core it has no knowledge of custom expressions defined in Relational or providers. Those expressions should know how to compare themselves to one another, but in many cases they were using Equals method, rather than ExpressionEqualityComparer.Equals.
Fix is to use ExpressionEqualityComparer instead.

Any other custom expression we want to consider? Like AliasExpression/InExpression? We can defer it till we hit issues with them.


Option for namespace to be declared after using statements

Minor polish issue, would be great is this could be configurable

Good suggestion - will add 👍

@CoenraadS - version 0.76 is out now - that adds an option to generate the usings outside the namespace 🎉

Just tried it, works great!

Thanks for the feedback, appreciate it!


MIDIInput not responding to trigger when Control is assigned by an input value in Tooll v3.9

In Toolls 3.9.1 the  operator is not sending any trigger value (bool output) if the value for the "Control" parameter is assigned from an imput Integer. This works properly on v <IP_ADDRESS>
You can see it in this vídeo:
https://github.com/tooll3/t3/assets/161488670/21072135-55ca-42c1-9189-bda35c0976fe
Please complete the following information):

OS: Windows
Version: 3.9.1
Graphics card and resolution: N/A

To Reproduce
Steps to reproduce the behavior:

Use  MIDIInput operator
After configuring it (controller name, Control number, etc.) check that bool output is sending the trigger signal
Now, create an intValue and connect it to Control paramenter
Now, the MIDIInput is not triggering anumore.

Expected behavior
The behavior should be the same in the Control values is assigned inside or as a input value.

I looked into this and it appears that I misunderstood how the NAudio.Midi package is supposed to be used.
I adjusted the implementation accordingly and pushed the fix to the dev branch which will be available with the next release of T3.
Thanks for pointing this out.


perf: Various optimizations

Closes #1407, closes #1408

This PR:

cleans up some of the code related to the map chart,
removes unnecessary mesh computation,
optimizes dimensions values fetching by using Promise.all instead of for ... await,
refactors geo-related queries to remove resolver chains,
updates several packages.

Merging after running and passing the E2E tests locally. We might need to look into why they keep failing (maybe still some tests are affected by filters panel loading) – or introduce some retrials? The problem seems to mostly appear when several tests are run together (yarn run e2e) – when running single tests locally (yarn run e2e e2e/tooltip.spec.ts), they usually work without failures.
cc @ptbrowne


fix otel tracing

Issues associated with this PR
修复 Otel 在注入 Span 信息到 Http Header 时 Span ID 重复的问题
Solutions
Change add To set
UT result
no need for UT
Benchmark
Already tested
Code Style

Make sure Goimports has run
Show Golint result

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...


Better explanation

On readme and store
Share WiFi or Mobile Data
Avoid hotspot data caps
Avoid hotspot data throttling
Run a hotspot without a hotspot plan
Create a local network between devices
Potentially share your VPN connection if VPN app allows (TailScale and Mullvad possibly confirmed)

Additional use case: bypass device limit on network

Readme
486d81ad94b54b22b2aebb180457746a523cd23e


[Bug]: In edit mode, Multiple issues are coming w.r.t Modal UI

Is there an existing issue for this?

[X] I have searched the existing issues

Description
issues with modal in EDIT MODE:

If my widget on which I have configured Modal is below the fold , then on click the screen is moving to the top and then displaying modal
with modal, the entire is NOT getting blocked like it used to work before and also the scroll canvas is appearing which is disturbing the UI

Steps To Reproduce

open modal widget in edit mode

Public Sample App
No response
Issue video log
https://www.loom.com/share/c51d0f433ca444f5811bb511ef9bb560
Version
release

Hey @somangshu Can we get this assigned to someone from the team? Seems to be pretty bad experience with modal

@hetunandu @rahulramesha is this related to context switching? I see when the modal is opened in the edit mode, some identifier is added to the URL, that is what probably causes the issue. Can you shed some light here.
There are no changes directly made to modal otherwise

Setting this to medium as this accounts to poor UX and does not block users in any ways

To Add more context to the Issue, From git Bisect it seems to be introduced from the Multi pane changes to the layout in https://github.com/appsmithorg/appsmith/pull/19261. This could most likely be the result of DOM structure changes as part of the project.

@hetunandu Are we prioritising this issue ? I understand this is not a blocker however its creating confusion if we initiate the modal action from below the fold widgets giving an illusion that modal is not working. LOOM


Will you be migrating this to use docker cloud?

If you don't feel like it, would you mind if I did it?  I think some environment variables need changing.

Check this pull request https://github.com/sillelien/tutum-cron/pull/3


[api-docs] Document GET Invite with_expiration query param

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/2c9f17887a8e5c95d48b93901f4543beda4c09be

Done


Serverless functions cannot decode POST requests when running in Dev

- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
Serverless functions used to handle POST data from a form do not work locally under Netlify Dev while they work correctly when deployed as Netlify Functions.
Netlify dev seems unable to parse the POST data like so:
 const params = querystring.parse(event.body);

- If the current behavior is a bug, please provide the steps to reproduce.
Create an HTML form with action of ./netlify/functions/parseParams and a method of POST
Include an input field of firstname in the form.
Create a Netlify Function of parseParams.js to handle the form submissions
Use code such as the following code in parseParams.js:
const querystring = require('querystring');
exports.handler = async (event, context) => {
  const params = querystring.parse(event.body);
  const name = params.firstname || "World";
  return {
    statusCode: 200,
    body: `Hello, ${name}`
  };
};

Run the site locally using netlify dev
Post data using the form
- What is the expected behavior?
The function should return the value of your input posted in the form. As it does when this code is deployed on Netlify.
- Please mention your node.js, and operating system version.
netlify-cli/2.12.0 darwin-x64 node-v10.15.3

Working in the latest version!


run error

venv "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\Scripts\Python.exe"
Initializing Model..
Running on local URL:  http://<IP_ADDRESS>:7860
To create a public link, set share=True in launch().
Traceback (most recent call last):
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\gradio\routes.py", line 384, in run_predict
output = await app.get_blocks().process_api(
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\gradio\blocks.py", line 1024, in process_api
result = await self.call_function(
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\gradio\blocks.py", line 836, in call_function
prediction = await anyio.to_thread.run_sync(
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\anyio\to_thread.py", line 31, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\anyio_backends_asyncio.py", line 937, in run_sync_in_worker_thread
return await future
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\anyio_backends_asyncio.py", line 867, in run
result = context.run(func, *args)
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\modules\model_Inference.py", line 34, in transcribe_file
audio = whisper.load_audio(fileobj.name)
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\whisper\audio.py", line 42, in load_audio
ffmpeg.input(file, threads=0)
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\ffmpeg_run.py", line 313, in run
process = run_async(
File "D:\Downloads\SOFTWARE\Whisper\Whsiper-WebUI-master\venv\lib\site-packages\ffmpeg_run.py", line 284, in run_async
return subprocess.Popen(
File "C:\Program Files\Python\lib\subprocess.py", line 969, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python\lib\subprocess.py", line 1438, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] 系统找不到指定的文件。

Hello, Are you sure that FFmpeg is installed on your computer?
As mentioned in the Readme, FFmpeg can be installed from the following link:
https://ffmpeg.org/download.html

Hello, Are you sure that FFmpeg is installed on your computer? As mentioned in the Readme, FFmpeg can be installed from the following link: https://ffmpeg.org/download.html

ought I had it installed before. One more question, Why doesn't it support multiple video import?

It would be helpful to handle multiple files at once, so I may work on adding this functionality.
As for the timestamp in the file name, it is used to prevent file overwriting, but it may be useful to include an option to disable it?
Additionally, the error you encountered previously may have been due to the FFmpeg\bin folder not being added to your system PATH.
I added information to the README about adding the FFmpeg\bin folder to the system PATH.

If you want to generate multiple subtitles, it is not possible to add time stamps, because later you have to change back very troublesome, you can set the output directory to solve this problem.
FFmpeg This error message is indeed because I did not install it, I ignored it and thought I had installed it before.

Thanks for bringing this to my attention. If there is a significant demand for the option to disable adding timestamps in filenames, I will definitely consider adding it in the future.
In the meantime, I have confirmed that there are no remaining issues with the execution of FFmpeg, so I will be closing this issue.

Thanks for bringing this to my attention. If there is a significant demand for the option to disable adding timestamps in filenames, I will definitely consider adding it in the future. In the meantime, I have confirmed that there are no remaining issues with the execution of FFmpeg, so I will be closing this issue.

OKay


Autorest Regen Preview to 3.0.0-alpha.20231026.1 by Chun Yu from refs/pull/3869/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3869

API change check
API changes are not detected in this pull request.